The 5.12.17 stable kernel update contains a (unusually large) number of fixes across the tree.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2021-a95108d156Please login to add feedback.
| -3 | 12 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This kernel, together with 5.13.2-300.fc34, has severly broken USB device detection for me.
All of the devices shown below have disappeared from my lsusb output:
Bus 003 Device 009: ID 08bb:29c3 Texas Instruments PCM2903C Audio CODEC Bus 003 Device 008: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 003 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 003 Device 005: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 003 Device 003: ID 0d8c:0135 C-Media Electronics, Inc. Q9-1 Bus 003 Device 006: ID 08bb:2901 Texas Instruments PCM2901 Audio Codec Bus 003 Device 004: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 003 Device 002: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub Bus 001 Device 002: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
In all honesty, with 800 odd patches from upstream, these kernels have had a huge number of opportunities to be broken.
This update's test gating status has been changed to 'passed'.
Looks like you lost the host controller, did you open a bug with an attached dmesg and such? I didn't see it.
Default & performance tests pass (KVM)
OK, this is the difference between the working and failing cases using lsusb
[bdm@deangelis ~]$ diff -u lsusb_5.12.15 lsusb_5.13.2 --- lsusb_5.12.15 2021-07-15 19:24:14.114924587 +0100 +++ lsusb_5.13.2 2021-07-15 23:22:52.491463122 +0100 @@ -1,13 +1,3 @@ -Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub -Bus 003 Device 009: ID 08bb:29c3 Texas Instruments PCM2903C Audio CODEC -Bus 003 Device 008: ID 10c4:ea60 Silicon Labs CP210x UART Bridge -Bus 003 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge -Bus 003 Device 005: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub -Bus 003 Device 003: ID 0d8c:0135 C-Media Electronics, Inc. Q9-1 -Bus 003 Device 006: ID 08bb:2901 Texas Instruments PCM2901 Audio Codec -Bus 003 Device 004: ID 10c4:ea60 Silicon Labs CP210x UART Bridge -Bus 003 Device 002: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub -Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 003: ID 0bda:4e22 Realtek Semiconductor Corp. Realtek USB2.0 Audio
Looks like the problem device is this:
0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
I will try to extract the relevant information from dmesg and file a bug.
This is the relevant bit of the dmesg from 5.12.17 and 5.13.2, it seems that it's a firmware load failure in the Renesas USB hub/controller
[ 0.722879] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 0.722900] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 [ 0.723973] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810 [ 0.724125] usb usb1: Manufacturer: Linux 5.13.2-300.fc34.x86_64 xhci-hcd [ 0.725294] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 0.725348] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 [ 0.725350] xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed [ 0.725380] usb usb2: Manufacturer: Linux 5.13.2-300.fc34.x86_64 xhci-hcd [ 0.966052] usb 1-5: new full-speed USB device number 2 using xhci_hcd [ 1.121074] xhci_hcd 0000:04:00.0: Direct firmware load for renesas_usb_fw.mem failed with error -2 [ 1.121079] xhci_hcd 0000:04:00.0: request_firmware failed: -2 [ 1.121085] xhci_hcd: probe of 0000:04:00.0 failed with error -2 [ 1.208092] usb 1-6: new high-speed USB device number 3 using xhci_hcd [ 1.766990] usb 1-9: new low-speed USB device number 4 using xhci_hcd [ 2.014988] usb 1-10: new low-speed USB device number 5 using xhci_hcd [ 2.374987] usb 1-12: new full-speed USB device number 6 using xhci_hcd
Does this need further reporting in bugzilla?
Now in bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1982893
This update has been pushed to testing.
Looks ok for me. Runs since it was ready in koji. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg). Regression test passed (paxtest, selinux-dac-controls and libhugetlbfs skipped).
This update can be pushed to stable now if the maintainer wishes
Works fine on Acer Aspire V3-571 v: V2.11 CPU: Quad Core Intel Core i7-3632QM GPU: Intel 3rd Gen Core processor Graphics Controller KDE Plasma. No regressions found
jforbes edited this update.
Default and performance tests passed with x570 chipset and Nvidia GP108 [GeForce GT 1030]
Works for me, no issues noticed..
The enabled Default and Performance tests pass OK. AMD 965, x86_64 work station, SSD's > RAID1. Plasma DE from Zawertun's COPR, X-org, nVidia GTX 650 (GK107) nVidia RPM's from RPMFusion (465.31)
works for me
LGTM
Tested on an AMD Ryzen 3 4300U APU. LGTM.
4 for 4 resumes tested. Currently both kernels starting with 5.12.15 pop out my disc tray on resume. I don't really want prank kernels. 5.12.14 and older doesn't pop it out.
Works, no issues for me.
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
Breaks Renesas USB controller: https://bugzilla.redhat.com/show_bug.cgi?id=1982893