sudo systemctl restart etcd gives an error, the daemon will no longer start after this update

Now in bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1982893

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?

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 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.