Login

Recent searches

No recent searches

Search options

Only available when logged in.
godforsaken.website is one of the many independent Mastodon servers you can use to participate in the fediverse.
godforsaken.website is a uk-based mastodon instance boasting literally thousands of posts about bumholes and UNESCO world heritage sites

Administered by:

Server stats:

31
active users

godforsaken.website: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#linuxkernel

0 posts0 participants0 posts today
Public *
Steven Rosenberg

Is your Fedora system doing a lot of crashing/freezing lately?

It could be Linux kernel 6.13, which is affecting Flatpak and FUSE apps.

My Fedora Kinoite system was definitely suffering, especially with Flatpak browsers, until I rolled back to the 2/24 deployment.

This file tells you everything you need to know:

discussion.fedoraproject.org/t

Thanks @Rhababerbarbar

Fedora Discussion · Bug in Kernel 6.13 crashing Flatpak and FUSE appsKernel 6.13 introduced a very bad bug that causes “bad page states” when opening some flatpak apps. Symptoms can be freezing systems when opening Flatpak apps Flatpak apps filling up RAM crash logs like this or that uname -r shows if you use kernel 6.13 Upstream bug Upstream bug fix Solved? The bug was supposedly fixed upstream and the kernel package upgraded. We need to wait for the upgrades to arrive everywhere, and atomic images to be built. Just upgrade your system normally and you ...
#Fedora#LinuxKernel#Silverblue
Public
Thorsten Leemhuis (acct. 1/4)

Linus replied to Christoph about the Rust for #Linux DMA blockage:

lore.kernel.org/all/CAHk-=wgLb

'"Honestly, what you have been doing is basically saying "as a DMA maintainer I control what the DMA code is used for".

And that is not how *any* of this works […]

You are saying that you disagree with Rust - which is fine […]

I respect you technically, and I like working with you.

And no, I am not looking for yes-men, and I like it when you call me out on my bullshit. […]"'

#kernel#LinuxKernel
Replied in thread
Public *
Thorsten Leemhuis (acct. 1/4)

3/ Ohh, and if you haven't seen this, see also this post from @sima and the reply from @airlied about the #Rust for #Linux DMA drama:

lore.kernel.org/lkml/Z6OzgBYZN

'"The r4l team and drm maintainer team have this sort of thing in hand, it's not like we don't understand the community of the Linux kernel, and having this first reaction to blow shit up and dramatise it just isn't helpful."'

#Rustlang#LinuxKernel
Continued thread
Public
Thorsten Leemhuis (acct. 1/4)

2/ BTW, let me kinda repeat an impression I shared a few months ago[1] after participating in the #Rust for #Linux discussion on the invitation only #Kernel maintainer summit (lwn.net/Articles/991062/):

Many #LinuxKernel core maintainers including Linus really want Rust for Linux to succeed.

Sure, there are technical problems and hurdles that need to be solved – and humans to be motivated and convinced. But given such strong backing I'm pretty sure that will happen.

[1] fosstodon.org/@kernellogger/11

lwn.netCommitting to Rust in the kernel [LWN.net]
Public
Thorsten Leemhuis (acct. 1/4)

Do not worry about the #Rust for Linux DMA drama that is making the rounds in the news and on social media: disagreements like that happen every now and then in #LinuxKernel land – and almost always some solution is found sooner or later that everybody can live with somehow. Either by the community itself, or by Linus himself.

heise.de/en/news/Is-a-kernel-d #kernel #rustlang

heise online · Is a kernel developer blocking the success of Rust for Linux? Yes and no!By Thorsten Leemhuis
Continued thread
Public *
Thorsten Leemhuis (acct. 1/4)

3/ It got even stranger: it seems @tuxedocomputers provided the wrong license to the MODULE_LICENSE()[1] macro either by accident or on purpose. 🧐

@waldi pointed that out earlier today elsewhere in this thread; PWM maintainer Uwe Kleine-König a little later submitted a bug report asking this to be fixed:

gitlab.com/tuxedocomputers/dev

[1] they proclaim it's GPL, which according to the #Linux #kernel's docs means "GPLv2" (either -only or -or-later), when in fact the code is GPLv3

#LinuxKernel
Public *
Thorsten Leemhuis (acct. 1/4)

TIL: @tuxedocomputers released #Linux #kernel drivers for their machines under the #GPLv3, which makes it impossible for competitors and distros to ship them pre-compiled, as that license is incompatible with the #LinuxKernel's #GPLv2 only license.

They did this purposely, allegedly to "keep control of the upstream pacing" – and want to re-license the code while upstreaming.

github.com/tuxedocomputers/tux

gitlab.com/tuxedocomputers/dev

gitlab.com/tuxedocomputers/dev

gitlab.com/tuxedocomputers/dev

Public
Thorsten Leemhuis (acct. 1/4)

#VirtualBox and most likely also #VMware hypervisors do currently not work with the mainline #kernel / #Linux 6.12-pre, unless you boot with 'kvm.enable_virt_at_load=0' – and it looks like developers do not see any need to change this:

lore.kernel.org/all/ZwQjUSOle6 #LinuxKernel

"'And, no offence to VirtualBox or VMware, I care much more about not regressing KVM users than I care about inconveniencing out-of-tree hypervisors.'" 🤔 🧐

lore.kernel.orgRe: KVM default behavior change on module loading in kernel 6.12
Public
Thorsten Leemhuis (acct. 1/4)

After six years the 4.14.y #Linux #kernel series will soon be EOLed with its 336 release: lore.kernel.org/all/2024010814

Side note & general reminder: You should slowly migrate to the #LinuxKernel 6.6.y series in the next few weeks on any systems used for "general computing", e.g. "'"where you have untrusted users or virtual machines"'". If that's news to you, checkout this blog post from @gregkh: kroah.com/log/blog/2018/08/24/

Public
Thorsten Leemhuis (acct. 1/4)

"[…] Instead of accepting my [#LinuxKernel] patch or guiding me towards a better solution, he went ahead and implemented his own fix, giving me credit only for reporting the issue […]

My first contribution to the [#Linux] #kernel was a really frustrating and discouraging experience, dealing with people who do not think it’s important to get proper recognition for your work. […]"

ariel-miculas.github.io/How-I-

1/ Side note: I sometimes wonder if…

ariel-miculas.github.ioHow I got robbed of my first kernel contributionContext Around a year and a half ago, I’ve asked my former company for some time to work on an issue that was impacting the debugging capabilities in our project: gdbserver couldn’t debug multithreaded applications running on a PowerPC32 architecture. The connection to the gdbserver was broken and it couldn’t control the debug session anymore. Multiple people have already investigated this problem and I had a good starting point, but we still weren’t sure in which software component the issue lied: it could have been the toolchain, the gdbserver, the Linux kernel or the custom patches we applied on top of the kernel tree. We were quite far away from finding the root cause.
SearchLive feeds
About