No issue spotted so far, using it for 3 days now

@soeiro that's my personal experience, I had a previous desktop with GTX1060 and every other kernel update it either fails to boot on reboot or driver is not loaded, or resolution is messed up, all kind of things. I've built a new one with AMD GPU and had no issues whatsoever as far as kernel update goes. I've put 3070 this week to test something and at first update it failed to boot into graphical target (tty was working fine). It's mostly solved by another reboot, but why is it always like that. Sorry for the spam.

Works fine on my Ryzen 5900X + nVidia RTX 3070 (460.56 driver from rpmfusion). As mostly every time for as long as I remember, screen output does not work after grub menu, which is solved by reboot, but that was always the case with nVidia (it's a temporary card right now). Whole 5.11.x series worked from day-1 with zero issues.

Works fine on Lenovo P1 gen.2

Works well and stable. No regressions spotted.

Works fine, but it broke fluent boot screen, there is a boot log shown before the luks password prompt and right before the login screen on KDE. Happens both on my Ryzen Desktop and Intel laptop.

Works well, no regression spotted over the course of the day

Default test suite Pass. No regressions spotted.

CPU: Ryzen 5900X MB: MSI X570 Tomahawk RAM: G.Skill 32 Gb (2 x 16) 3600Mhz/CL16 GPU: Aorus RX 5700 XT Storage: - WD Black SN850 NVMe - Samsung 970 EVO Plus NVMe - Samsung 860 Pro SATA3

No regressions spotted so far, btrfs performance indeed is restored

Works well

No regressions spotted

No regression spotted, works well with WebRender enabled on X11/Plasma amdgpu

Works fine on Ryzen 5900X. Passed default kernel test.

Getting these messages during the boot: [ 0.317688] __common_interrupt: 1.55 No irq handler for vector [ 0.535767] #2 [ 0.317688] __common_interrupt: 2.55 No irq handler for vector [ 0.536768] #3 [ 0.317688] __common_interrupt: 3.55 No irq handler for vector [ 0.537767] #4 [ 0.317688] __common_interrupt: 4.55 No irq handler for vector [ 0.539765] #5 But looks like it's caused by recent AGESA (BIOS).

Had two restarts at random point 1 day apart after which I had this message during the boot: [ 0.540745] mce: [Hardware Error]: Machine check events logged [ 0.540746] mce: [Hardware Error]: CPU 5: Machine Check: 0 Bank 5: bea0000001000108 [ 0.540747] mce: [Hardware Error]: TSC 0 ADDR ffffff970589a4 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 [ 0.540749] mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1608050668 SOCKET 0 APIC a microcode a201009 [ 0.540767] #6 [ 0.541743] mce: [Hardware Error]: Machine check events logged [ 0.541744] mce: [Hardware Error]: CPU 6: Machine Check: 0 Bank 5: bea0000000000108 [ 0.541744] mce: [Hardware Error]: TSC 0 ADDR ffffff97b8de6a MISC d012000100000000 SYND 4d000000 IPID 500b000000000 [ 0.541746] mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1608050668 SOCKET 0 APIC 10 microcode a201009

But afterwards the system looks stable.

Works great, no regression spotted.

Works great on Lenovo P1 gen2 w/ Intel graphics, including Wayland session. On desktop with nVidia graphics (2080 Super) x.org works great, but wayland hangs the GPU and generally unstable with lots of visual glitches. Most likely nVidia's fault, not Plasma's, but still worth mentioning.