5 ms·

6.10 (TEN, the previous one) has been a very problematic release for me, with one desktop running into four major bugs in total: three separate amdgpu bugs resu

6.10 (TEN, the previous one) has been a very problematic release for me, with one desktop running into four major bugs in total: three separate amdgpu bugs resulting in video corruption, hangs and crashes, and now that I'm on 6.10.10 and those seem to be fixed, the system intermittently refuses to come up from sleep mode. Anyone else having similar experience? This is the first time something like that happened in a decade of using the latest stable kernel release (in my experience, it's actually been stable for all that time except for 6.10).

skerit 2y ago
6.10 broke my AMD 5700XT eGPU setup. Had to downgrade to 6.9 After I upgraded to a 7900XT it worked again.
mahkoh 2y ago
I've had a few hard crashes (system freezes completely, ssh does not work) over the last two weeks on 6.10.x kernels. I am hoping that it is https://gitlab.freedesktop.org/drm/amd/-/issues/3142 https://gitlab.freedesktop.org/drm/amd/-/issues/3142 (and not hardware failure) but I've been unable to capture the kernel panic if it does occur. Never had such an issue before.
- OvbiousError 2y ago
  Wow thanks for that link. I've had my machine crashing a couple of times as well the last couple of weeks, was absolutely stable before. I hope it's this and not hardware failure.
0xC0ncord 2y ago
I too have been having AMD GPU video artifacting lately, but so far that is the only regression I've noticed in 6.10.x. I am still on 6.10.8 so I'm not sure if 6.10.10 will contain a fix for me just yet.
shmerl 2y ago
What GPU?
TomK32 2y ago
Is that just AMD? On my thinkpad X270 playing videos in Firefox is just a mess. All sorts of problems while Chromium is just fine. It's also fine on a copy of my system that I run on a thinkcentre tiny.
- nine_k 2y ago
  Check the Firefox video settings in about:config maybe?
- tadfisher 2y ago
  I do believe Chromium still has to be patched to support HW decode via vaapi, while recent Firefoxen turn it on out of the box. So it's likely that Chromium is using software rendering, bypassing any driver-related bugs.
- PKop 2y ago
  Chromium doesn't support hardware decoded video though right? While Firefox does, so you're killing your battery life with extra cpu cycles.
  - Timber-6539 2y ago
    Chromium doesn't document this but they support hardware video decode on Linux. Works best on Intel iGPU. AMD needed some patches to get it working using Vulkan IIRC and Nvidia is Nvidia.
    - PKop 2y ago
      What did you have to do to get it to work for Intel iGPU? Passing all combinations of command line flags never made it work. intel_gpu_top showed both Video and VideoEnhance markers signaling hardware decode as inactive, and all commenters on message boards that I came across essentially came to the same conclusion, that it doesn't work at least at the time I as trying a few months ago. I think it was that Chromium devs don't support it and block it from functioning in the code because of this or that upstream dependency not being stable.
dsissitka 2y ago
I got bit twice. First there was the bug that broke Chromium based apps when using SELinux. https://lore.kernel.org/all/30fc5b38165e4eda57d640eca76b7df1@paul-moore.com/ https://lore.kernel.org/all/30fc5b38165e4eda57d640eca76b7df1... Then 6.10.6 didn't want to boot. Usually I run into issues two or three times a year. I guess this time around they just happened to be a little closer together.
_cenw 2y ago
Early 6.10 somehow broke bluetooth audio for me, only letting me use HSP.
globular-toast 2y ago
Yeah, same problems with 6.10 and amdgpu. Radeon Pro WX 3200 fwiw. I've been on 6.8.9 for several weeks now. Just today I booted 6.10.7 and it's been stable so far. I haven't tried to put the system to sleep yet, though. This isn't the first time I've had problems with the stable kernel, though. A while back I had problems, also graphics related, with Intel i915 (my onboard graphics that I used before I got the AMD card). It took a while but it eventually got fixed. I haven't looked to see if there's a bug tracked for the AMD problem.
IshKebab 2y ago
How does Linux handle testing? They don't seem to have a CI system as far as I know. Presumably there's no big lab with automated testing on real hardware. Does anyone know how releases are tested?
- Idesmi 2y ago
  As far as I remember, there is some automated testing before release but very limited in scope.
- leonheld 2y ago
  Several companies (including mine, Toradex) have setup board farms to deal with Kernel regressions and bugs during the `-rc` window, ie, the kernel that is going to be released is heavily tested. https://kernelci.org/ https://kernelci.org/ is a big one, Linaro has theirs https://lkft.linaro.org/ https://lkft.linaro.org/, Intel has multiple farms, Collabora works relentlessly with GitLab integration https://www.collabora.com/news-and-blog/news-and-events/patch-submitted-to-introduce-gitlab-ci-pipeline-for-kernel-testing.html https://www.collabora.com/news-and-blog/news-and-events/patc...... The kernel is very much tested before a release with gigantic automated labs on real hardware.
  - musicale 2y ago
    > The kernel is very much tested before a release with gigantic automated labs on real hardware. So what went wrong?
    - badsectoracula 2y ago
      I'd guess none of those labs are testing desktop environments playing videos and running 3D software on amdgpu.
- JSDevOps 2y ago
  Explain how you would deal with CI in a kernel?
davidlt 2y ago
I am really surprised with RNDA3 support. I have never seen so many issue with iGPU (APU). It started with VP9 decoder issue (e.g. just playing videos on YouTube was enough to trigger it), but that got fixed after a very long time (required a new firmware). Multiple constant [different] crashes, but you can workaround most of them by adding amdgpu.sg_display=0 to your bootargs. It's already listed in Arch Linux wiki, Gentoo wiki, etc. Again, I was surprised by the number of firmware and driver issues since RNDA1/2/3 have been around for years now.
- Idesmi 2y ago
  6.10.5 fixed all my amdgpu issues.
- deleted 2y ago
  [deleted]
lifeinthevoid 2y ago
amdgpu on my 6.10 kernel has been crashing constantly too. It makes me want to go back to Intel. My workaround has been to let the ryzen 7700 iGPU run at its max clockspeed of 2200 Mhz …
gigatexal 2y ago
6.10 broke my fedora gaming proton box and I was on holiday at the time and so upset I just nuked it and put windows on it to play games. Now it's only powered on on the weekends to play games and I've moved all my linux needs to a VM on my overspecc'd Mac. I also had an AMDGPU system. 5600X, AMD 6800 GPU, Fedora 40. -> now win11 (which has so much cruft out of the box I am considering nuking it and going back haha)
- anotherhue 2y ago
  Broke my nixos steam/proton setup also. Using game scope as the compositor. Switch to LTS (6.6 I think) solved it. Frustrating bug but they don’t call it nixos-unstable for nothing. 7900 GRE
- anthk 2y ago
  Try Fedora Bazzite. It's inmutable and you'll get rollbacks at the grub prompt.
  - atlas_hugged 2y ago
    +1 just installed this yesterday. Still kicking the tires
    - jhot 2y ago
      Been running it for 3 months, very pleased with my all AMD pc.
- abhinavk 2y ago
  In college, I used to run bleeding edge. But now...I will only run a bleeding edge system as an immutable distro or on a filesystem with quick rollbacks.
  - gigatexal 2y ago
    Yeah ... had I had an immutable system or something where rolling back was easy I would have ... I dunno Fedora/Linux + AMD hardware had been so rock solid I took it for granted.
mardifoufs 2y ago
The past few releases were more problematic for me yeah. It's super anecdotal since I never used Linux before the v5.xx kernels but in comparison to those yes it's a bit less stable.
wooque 2y ago
That's why I stick with Debian.
aseipp 2y ago
amdgpu is shit for me, my friend. Funny story: my headless server with a small Navi 1 workstation card (repurposed) couldn't be SSH'd into last week. Went and plugged in a monitor, rebooted, and the framebuffer got stuck during stage 1 while fsck'ing my disk. OK, I think to myself, it's probably taking a while to fsck after N boots, happens once every few months. Doesn't change for 48 hours. Turns out my machine had just run out its DHCP lease, so it had a new IP and I didn't realize it, which is why I couldn't log in. So I log in, and.. What was wrong? What actually happened was that on bootup, the amdgpu driver would panic and fault during boot exactly when fsck was happening, and the framebuffer would be stuck forever. So it just looked like a filesystem issue but in reality my graphics output was merely fubar; the system itself was otherwise fine tnough. This is reliable and reproducible for me; it always faults at almost the exact same spot at boot every time, for this kernel version at least. In reality amdgpu has been unreliable for me for 5+ releases at this point on a card less than like 7 years old. Really considering moving over to a small cheap nvidia card and just running Nouveau instead. At least then I might have a reliable framebuffer.
- dogben 2y ago
  you can just blacklist amdgpu and use EFI/VGA buffer provided by bios
trulyrandom 2y ago
Just to add a non-problematic experience report to the mix: I've been using 6.10 for months on two AMD machines with different hardware (one with a 7840U and one with a 5700XT) without any issues whatsoever.
mixmastamyk 2y ago
Doing well on a recent AMD, although I didn't upgrade until about 6.10.7 or so. There were problems on earlier kernels, but they were mostly fixed by a firmware update. Kernel already had support by that time.
sinker 2y ago
Kernel version 6.8 broke suspend ($ systemctl suspend) for me. I run two machines with near identical setups. I upgrade my "preview" machine first before updating my primary machine to test for defects. If I boot from kernel version 6.5, suspend works fine. Hold shift while your machine is booting and the grub menu will allow you to select a different kernel version.
nitinreddy88 2y ago
Ack. AMD gpus broke left and right with this version. Lot of issues reported : https://gitlab.freedesktop.org/drm/amd/-/issues https://gitlab.freedesktop.org/drm/amd/-/issues Even the latest Linux kernel 6.11 still have same issues (atleast for me)
daemonologist 2y ago
Yeah I've experienced a fair number crashes with 6.10 (multiple point releases) on my 680M. Earlier kernels were fine in my recollection although I didn't bother downgrading, and Windows remains rock solid on the same system.
WaffleIronMaker 2y ago
I was using a Fedora release with the 6.10 kernel, and I experienced frequent logouts and restarts, almost once per day. It's nice to see that others were having similarly poor experiences.
quicksilver03 2y ago
The amdgpu driver has been the main source of issues for me on 6.10, but I had issues on older 6.x versions as well: for example, on a desktop with 2 monitors, I had to turn on the 2 monitors simultaneously or the UI would freeze.
mnahkies 2y ago
No idea if related, but I had a really frustrating issue recently on fedora/similar kernel version. Resume from sleep stopped working, and boot started taking minutes. Going through logs I was able to figure out it was probably usb related, and that sleep worked if you were patient enough to wait for a timeout, but the issue persisted with all cables unplugged. The error code was something along the lines of failing to provide enough power for a device, I suspected my new speakers despite them having dedicated wall outlet power (usb audio despite being on the motherboard AFAIK) Long story short someone in a thread somewhere suggested unplugging from the wall for 10 min and to my surprise it worked - I guess it cleared the fault somehow and it hasn't reoccurred (yet). Might be worth a try.

skerit 2y ago

6.10 broke my AMD 5700XT eGPU setup. Had to downgrade to 6.9 After I upgraded to a 7900XT it worked again.

mahkoh 2y ago

I've had a few hard crashes (system freezes completely, ssh does not work) over the last two weeks on 6.10.x kernels. I am hoping that it is https://gitlab.freedesktop.org/drm/amd/-/issues/3142 https://gitlab.freedesktop.org/drm/amd/-/issues/3142 (and not hardware failure) but I've been unable to capture the kernel panic if it does occur. Never had such an issue before.

OvbiousError 2y ago
Wow thanks for that link. I've had my machine crashing a couple of times as well the last couple of weeks, was absolutely stable before. I hope it's this and not hardware failure.

0xC0ncord 2y ago

I too have been having AMD GPU video artifacting lately, but so far that is the only regression I've noticed in 6.10.x. I am still on 6.10.8 so I'm not sure if 6.10.10 will contain a fix for me just yet.

shmerl 2y ago

What GPU?

TomK32 2y ago

Is that just AMD? On my thinkpad X270 playing videos in Firefox is just a mess. All sorts of problems while Chromium is just fine. It's also fine on a copy of my system that I run on a thinkcentre tiny.

nine_k 2y ago
Check the Firefox video settings in about:config maybe?
tadfisher 2y ago
I do believe Chromium still has to be patched to support HW decode via vaapi, while recent Firefoxen turn it on out of the box. So it's likely that Chromium is using software rendering, bypassing any driver-related bugs.
PKop 2y ago
Chromium doesn't support hardware decoded video though right? While Firefox does, so you're killing your battery life with extra cpu cycles.
- Timber-6539 2y ago
  Chromium doesn't document this but they support hardware video decode on Linux. Works best on Intel iGPU. AMD needed some patches to get it working using Vulkan IIRC and Nvidia is Nvidia.
  - PKop 2y ago
    What did you have to do to get it to work for Intel iGPU? Passing all combinations of command line flags never made it work. intel_gpu_top showed both Video and VideoEnhance markers signaling hardware decode as inactive, and all commenters on message boards that I came across essentially came to the same conclusion, that it doesn't work at least at the time I as trying a few months ago. I think it was that Chromium devs don't support it and block it from functioning in the code because of this or that upstream dependency not being stable.

dsissitka 2y ago

I got bit twice. First there was the bug that broke Chromium based apps when using SELinux. https://lore.kernel.org/all/30fc5b38165e4eda57d640eca76b7df1@paul-moore.com/ https://lore.kernel.org/all/30fc5b38165e4eda57d640eca76b7df1... Then 6.10.6 didn't want to boot. Usually I run into issues two or three times a year. I guess this time around they just happened to be a little closer together.

_cenw 2y ago

Early 6.10 somehow broke bluetooth audio for me, only letting me use HSP.

globular-toast 2y ago

Yeah, same problems with 6.10 and amdgpu. Radeon Pro WX 3200 fwiw. I've been on 6.8.9 for several weeks now. Just today I booted 6.10.7 and it's been stable so far. I haven't tried to put the system to sleep yet, though. This isn't the first time I've had problems with the stable kernel, though. A while back I had problems, also graphics related, with Intel i915 (my onboard graphics that I used before I got the AMD card). It took a while but it eventually got fixed. I haven't looked to see if there's a bug tracked for the AMD problem.

IshKebab 2y ago

How does Linux handle testing? They don't seem to have a CI system as far as I know. Presumably there's no big lab with automated testing on real hardware. Does anyone know how releases are tested?

Idesmi 2y ago
As far as I remember, there is some automated testing before release but very limited in scope.
leonheld 2y ago
Several companies (including mine, Toradex) have setup board farms to deal with Kernel regressions and bugs during the `-rc` window, ie, the kernel that is going to be released is heavily tested. https://kernelci.org/ https://kernelci.org/ is a big one, Linaro has theirs https://lkft.linaro.org/ https://lkft.linaro.org/, Intel has multiple farms, Collabora works relentlessly with GitLab integration https://www.collabora.com/news-and-blog/news-and-events/patch-submitted-to-introduce-gitlab-ci-pipeline-for-kernel-testing.html https://www.collabora.com/news-and-blog/news-and-events/patc...... The kernel is very much tested before a release with gigantic automated labs on real hardware.
- musicale 2y ago
  > The kernel is very much tested before a release with gigantic automated labs on real hardware. So what went wrong?
  - badsectoracula 2y ago
    I'd guess none of those labs are testing desktop environments playing videos and running 3D software on amdgpu.
JSDevOps 2y ago
Explain how you would deal with CI in a kernel?

davidlt 2y ago

I am really surprised with RNDA3 support. I have never seen so many issue with iGPU (APU). It started with VP9 decoder issue (e.g. just playing videos on YouTube was enough to trigger it), but that got fixed after a very long time (required a new firmware). Multiple constant [different] crashes, but you can workaround most of them by adding amdgpu.sg_display=0 to your bootargs. It's already listed in Arch Linux wiki, Gentoo wiki, etc. Again, I was surprised by the number of firmware and driver issues since RNDA1/2/3 have been around for years now.

Idesmi 2y ago
6.10.5 fixed all my amdgpu issues.
deleted 2y ago
[deleted]

lifeinthevoid 2y ago

amdgpu on my 6.10 kernel has been crashing constantly too. It makes me want to go back to Intel. My workaround has been to let the ryzen 7700 iGPU run at its max clockspeed of 2200 Mhz …

gigatexal 2y ago

6.10 broke my fedora gaming proton box and I was on holiday at the time and so upset I just nuked it and put windows on it to play games. Now it's only powered on on the weekends to play games and I've moved all my linux needs to a VM on my overspecc'd Mac. I also had an AMDGPU system. 5600X, AMD 6800 GPU, Fedora 40. -> now win11 (which has so much cruft out of the box I am considering nuking it and going back haha)

anotherhue 2y ago
Broke my nixos steam/proton setup also. Using game scope as the compositor. Switch to LTS (6.6 I think) solved it. Frustrating bug but they don’t call it nixos-unstable for nothing. 7900 GRE
anthk 2y ago
Try Fedora Bazzite. It's inmutable and you'll get rollbacks at the grub prompt.
- atlas_hugged 2y ago
  +1 just installed this yesterday. Still kicking the tires
  - jhot 2y ago
    Been running it for 3 months, very pleased with my all AMD pc.
abhinavk 2y ago
In college, I used to run bleeding edge. But now...I will only run a bleeding edge system as an immutable distro or on a filesystem with quick rollbacks.
- gigatexal 2y ago
  Yeah ... had I had an immutable system or something where rolling back was easy I would have ... I dunno Fedora/Linux + AMD hardware had been so rock solid I took it for granted.

mardifoufs 2y ago

The past few releases were more problematic for me yeah. It's super anecdotal since I never used Linux before the v5.xx kernels but in comparison to those yes it's a bit less stable.

wooque 2y ago

That's why I stick with Debian.

aseipp 2y ago

amdgpu is shit for me, my friend. Funny story: my headless server with a small Navi 1 workstation card (repurposed) couldn't be SSH'd into last week. Went and plugged in a monitor, rebooted, and the framebuffer got stuck during stage 1 while fsck'ing my disk. OK, I think to myself, it's probably taking a while to fsck after N boots, happens once every few months. Doesn't change for 48 hours. Turns out my machine had just run out its DHCP lease, so it had a new IP and I didn't realize it, which is why I couldn't log in. So I log in, and.. What was wrong? What actually happened was that on bootup, the amdgpu driver would panic and fault during boot exactly when fsck was happening, and the framebuffer would be stuck forever. So it just looked like a filesystem issue but in reality my graphics output was merely fubar; the system itself was otherwise fine tnough. This is reliable and reproducible for me; it always faults at almost the exact same spot at boot every time, for this kernel version at least. In reality amdgpu has been unreliable for me for 5+ releases at this point on a card less than like 7 years old. Really considering moving over to a small cheap nvidia card and just running Nouveau instead. At least then I might have a reliable framebuffer.

dogben 2y ago
you can just blacklist amdgpu and use EFI/VGA buffer provided by bios

trulyrandom 2y ago

Just to add a non-problematic experience report to the mix: I've been using 6.10 for months on two AMD machines with different hardware (one with a 7840U and one with a 5700XT) without any issues whatsoever.

mixmastamyk 2y ago

Doing well on a recent AMD, although I didn't upgrade until about 6.10.7 or so. There were problems on earlier kernels, but they were mostly fixed by a firmware update. Kernel already had support by that time.

sinker 2y ago

Kernel version 6.8 broke suspend ($ systemctl suspend) for me. I run two machines with near identical setups. I upgrade my "preview" machine first before updating my primary machine to test for defects. If I boot from kernel version 6.5, suspend works fine. Hold shift while your machine is booting and the grub menu will allow you to select a different kernel version.

nitinreddy88 2y ago

Ack. AMD gpus broke left and right with this version. Lot of issues reported : https://gitlab.freedesktop.org/drm/amd/-/issues https://gitlab.freedesktop.org/drm/amd/-/issues Even the latest Linux kernel 6.11 still have same issues (atleast for me)

daemonologist 2y ago

Yeah I've experienced a fair number crashes with 6.10 (multiple point releases) on my 680M. Earlier kernels were fine in my recollection although I didn't bother downgrading, and Windows remains rock solid on the same system.

WaffleIronMaker 2y ago

I was using a Fedora release with the 6.10 kernel, and I experienced frequent logouts and restarts, almost once per day. It's nice to see that others were having similarly poor experiences.

quicksilver03 2y ago

The amdgpu driver has been the main source of issues for me on 6.10, but I had issues on older 6.x versions as well: for example, on a desktop with 2 monitors, I had to turn on the 2 monitors simultaneously or the UI would freeze.

mnahkies 2y ago

No idea if related, but I had a really frustrating issue recently on fedora/similar kernel version. Resume from sleep stopped working, and boot started taking minutes. Going through logs I was able to figure out it was probably usb related, and that sleep worked if you were patient enough to wait for a timeout, but the issue persisted with all cables unplugged. The error code was something along the lines of failing to provide enough power for a device, I suspected my new speakers despite them having dedicated wall outlet power (usb audio despite being on the motherboard AFAIK) Long story short someone in a thread somewhere suggested unplugging from the wall for 10 min and to my surprise it worked - I guess it cleared the fault somehow and it hasn't reoccurred (yet). Might be worth a try.