Post B90CXqTDHpt1Cod4qm by wonka@chaos.social
(DIR) More posts by wonka@chaos.social
(DIR) Post #B8ve077UheUdvMNIA4 by IngaLovinde@embracing.space
0 likes, 1 repeats
People: Why did my PC/laptop with AMD graphics started crashing when I try to play a video, after a minute or so?Linux: oh yeah that's a bug we introduced in kernel 7.1 a couple of days ago :)People: okay I can just switch to LTS kernel, right?Linux: actually we backported the bug into LTS too :)People: but surely it will soon be patched?Linux: actually we won't backport the fix into LTS, because LTS is for important fixes only :)People: but at least the latest kernel wil be patched?Linux: maybe in a couple of months; for now the fix is just sitting there in its separate branch :)Linux: also did you hear we embrace Vibe Coding now? :)
(DIR) Post #B8venU3QDr1pF90lHs by IngaLovinde@embracing.space
0 likes, 0 repeats
Source for the fix: https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=52f650963d8825e97a0ccdd2b616f8a01d9d3d38The commit introducing the bug was merged into 6.18 (LTS) on June 19th, after the bug was already reported.The fix was made on June 24th, and merged into linux main branch on July 1st, there's been three stable kernel releases since the fix, and four LTS kernel releases; none of them included the fix.Truly, the year of linux on desktop (where your entire OS will crash when you try to play video on your desktop, both on stable and on LTS kernel, and it's not considered to be a large problem.)
(DIR) Post #B8vg0Z1FAsCoMOnFfU by IngaLovinde@embracing.space
0 likes, 0 repeats
And because my laptop keyboard broke just before I started experiencing this bug, I legit thought for some days that maybe my GPU is dying too.
(DIR) Post #B8vhIpkfnjCHQGJnJw by littlerao@chaos.social
0 likes, 0 repeats
@IngaLovinde but they MUST introduce those features, I mean bugs... so they remain competetive with microslop! how else will there ever be the year of linux desktop? /s
(DIR) Post #B8vhmHsGK0FF2Zudf6 by IngaLovinde@embracing.space
0 likes, 0 repeats
@littlerao tbh I've never, in my 25 years of using Windows (of NT flavor), had anything crashing on me when playing video, let alone the entire system crashing. (Although I did see my fair share of BSODs / bug checks; but still much less, especially when adjusted to usage, when on Linux.)Maybe that's just what you get with a macrokernel (although Linux is so large, I'm not even sure "macro" is the right word anymore).
(DIR) Post #B8vi2djSozhxSvavj6 by penny@eldritch.cafe
0 likes, 0 repeats
@IngaLovinde @littlerao I guess the progression would be “super”. Linux is the first super kernel
(DIR) Post #B8viF2VCYME3lNptlA by IngaLovinde@embracing.space
0 likes, 0 repeats
@penny @littlerao "super" in the meaning in which Homelander from "The Boys" is a "super"
(DIR) Post #B8vpuxTgK8YM1P3pUO by IngaLovinde@embracing.space
0 likes, 0 repeats
@brainwormqueen from what I see in the git logs, 6.12 does not include the commit that broke things.
(DIR) Post #B8vqK1BJgrDqkSQ6c4 by brainwormqueen@woof.tech
0 likes, 0 repeats
@IngaLovinde Debian win (lol)
(DIR) Post #B8vr8xynM3EFaPrDAu by IngaLovinde@embracing.space
0 likes, 0 repeats
@tweak7749 yeah I'm not saying this is new. Just one example I myself experienced this week.And also I wasn't saying anything about stable _distros_ (or distros at all); I was talking about stable and LTS _kernels_.
(DIR) Post #B8vz3RGcLoysJd4KHY by IngaLovinde@embracing.space
0 likes, 0 repeats
@mitsunee what you were experiencing was almost certainly some other bug, because this specific bug was introduced in a commit that was only merged to kernel on June 3rd (and originally only released as part of kernel 7.1): https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91250893cbaa
(DIR) Post #B8vzayOIDbQSbTeJNo by 401matthall@mastodon.xyz
0 likes, 0 repeats
@IngaLovinde So... Now I have to mitigate and monitor _linux_ OS updates, too.Thanks, Sam Altman.🙄
(DIR) Post #B8w1ruSKIkcREMjuoC by argv_minus_one@mastodon.sdf.org
0 likes, 0 repeats
@IngaLovinde The original bug https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91250893cbaa was written by a human, not AI. Can't blame vibe coding for this one.But yes, letting fixes for kernel-crashing bugs languish for a month seems not great.
(DIR) Post #B8w6AkLyUBh3DX0Rn6 by bhasic@mastodon.social
0 likes, 0 repeats
@IngaLovinde I have 7.1.4-1 on Tumbleweed and 6.12.0 on Leap. Neither one has any problems.
(DIR) Post #B8w9bORqKy5cxb9IKu by IngaLovinde@embracing.space
0 likes, 0 repeats
@argv_minus_one I'm not blaming vibe coding for this one, I just think that it's weird that linux seems to spend more time on vibe coding than on including fixes for serious bugs into releases (or than on not backporting these bugs into LTS after they're already known to be bugs).
(DIR) Post #B8xz7wHDO8tDxsPit6 by cai@thicc.horse
0 likes, 0 repeats
@IngaLovinde I'm pretty sure I experienced this exact bug within the last couple of weeks...I just assumed it was Mesa or indeed AMDGPU breaking something around video again.I just kinda expect breakage at this point...
(DIR) Post #B8yXdxIuV7ySrKe3lo by jaj@mastodon.social
0 likes, 0 repeats
@IngaLovinde Probably will play just fine on *BSD
(DIR) Post #B90CXqTDHpt1Cod4qm by wonka@chaos.social
0 likes, 0 repeats
@IngaLovinde 7.1.6 is out now and contains the fix
(DIR) Post #B90EhQmNrKEyKbIKYq by IngaLovinde@embracing.space
0 likes, 0 repeats
@wonka yay! So it stayed broken for just 1.5 months.
(DIR) Post #B9B964u97aYChNd00e by IngaLovinde@embracing.space
0 likes, 0 repeats
@rl_dane @wonka no, the fix made it to LTS too after all
(DIR) Post #B9Bg75fV42VVqPrrto by mirabilos@toot.mirbsd.org
0 likes, 0 repeats
@IngaLovinde yeah, that 🤬🤬🤬
(DIR) Post #B9BmQ5BDhgSTYa8zKq by commanderred@chaos.social
0 likes, 0 repeats
@IngaLovinde can have a kernel that's turning into shit, as a treat
(DIR) Post #B9BmeSTRtTSLr8Wcwy by commanderred@chaos.social
0 likes, 0 repeats
@IngaLovinde well clearly you are using it wrong. It is not intended to be used that way.
(DIR) Post #B9Bsa1ha5aaNOHPCNs by azonenberg@ioc.exchange
0 likes, 0 repeats
@IngaLovinde I have never been happier to run debian instead of bleeding edge lol.
(DIR) Post #B9CIABlQeal7sPXsfo by xavier@pony.social
0 likes, 0 repeats
@IngaLovinde relieved to know I'm not alone. amdgpu used to be rock-solid, but it's been plagued by recurrent bugs and regressions in the last two years. The fact that LTS does not protect one from these regressions is really infuriating
(DIR) Post #B9D0meW2bEE82IV0Gu by IngaLovinde@embracing.space
0 likes, 0 repeats
@RueNahcMohr I'm on Alpine, which typically means that I have two versions in my bootloader: LTS and stable. Upgrading previous stable to latest stable means that I cannot go to previous stable typically.
(DIR) Post #B9D1Neu87MYBxJPdJ2 by mcc@mastodon.social
0 likes, 0 repeats
@IngaLovinde Oh... this is exciting because I updated my Debian today
(DIR) Post #B9D6JU8Ej9839qq8Ey by IngaLovinde@embracing.space
0 likes, 0 repeats
@RueNahcMohr that's why I said typically. I'm just a not very power user, I know how to "apk update" and "apk upgrade"; compiling the kernel is more than that.
(DIR) Post #B9DFiGVbPiozjXez2W by IngaLovinde@embracing.space
0 likes, 0 repeats
@RueNahcMohr not on Alpine, it only has the latest versions of each package; the old versions are deleted from the package repository, so you cannot downgrade(but you can pin package versions to avoid upgrade)
(DIR) Post #B9Dqur6SsX9v0aliz2 by IngaLovinde@embracing.space
0 likes, 0 repeats
@RueNahcMohr > so, you just let your system do random software upgrades whenever it wants?Yes, I rely on my distro maintainers. > when there was a bad version of glibc that corrupted filesystemsAlpine is musl based 😅