On Tue, Sep 08, 2020 at 10:51:17AM +0200, Hans de Goede wrote: > Hi, > > On 9/7/20 9:57 AM, Hans de Goede wrote: > <snip> > > > > > Are there any logs of this? > > > > > > Yes, sorry I should have included a bugzilla link, the bugzilla has > > > lsusb -t and dmesg out from both users with both kernels: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1874300 > > > > > > But it seems that at least part of the problem is the xhci driver > > > being built as a module with the Fedora 5.8 kernels where as 5.7 > > > had it builtin, so first let me investigate that angle further before > > > you spend more time on this. > > > > Ok, so having the xhci driver moved to being builtin again (it became a > > module by accident because of the new XHCI_RENESAS Kconfig option) > > resolves the issue for both users reporting this issue. > > > > For 1 user this makes sense, because he needed the kbd in the initrd > > and the xhci module was not being included. > > > > For the other user, the original reporter of: > > https://bugzilla.redhat.com/show_bug.cgi?id=1874300 > > > > this is not expected though, he does not need his kbd/mouse to boot, > > and once at the gdm login screen then if xhci is a module or not > > should not matter. > > > > Upon re-reading his comments I think I got one part of this bug-report > > wrong. He ran "lsusb -t" with his mouse + kbd in the non-working XHCI > > ports, but he did so with a working kernel (if I'm reading the report > > correctly this second reading). So I think that his mouse/kbd might > > actually be not detected at all when plugged into xhci ports and > > xhci is build as a module. To me that seems to make more sense > > then interrupt-transfers not working. > > > > My theory is that the ports are being turned off by the kernel when it > > turns of unused ACPI power-resources before switching to the initrd; > > and that for some reason they are not turned back-on when the XHCI > > module loads. > > > > Anyways for now building in the xhci module worksaround this, but > > IMHO it would be good to get to the bottom of this issue. > > Ok, so I got this bug completely wrong, their are 2 different issues: > > 1. xhci built as module, xhci module not available in initrd -> not a kernel bug > > 2. xhci built as module, while using a renesas xhci controller (these were > quite poplar for a while when Intel chipsets didn't have a builtin XHCI yet). > When this happens users (2 users so far) are seeing the following errors: > > Sep 01 10:47:36 kernel: xhci_hcd 0000:05:00.0: FW has invalid version :8216 > Sep 01 10:47:36 kernel: xhci_hcd 0000:05:00.0: Direct firmware load for renesas_usb_fw.mem failed with error -2 > Sep 01 10:47:36 kernel: xhci_hcd 0000:05:00.0: request_firmware failed: -2 > Sep 01 10:47:36 kernel: xhci_hcd: probe of 0000:05:00.0 failed with error -2 > > Which is fixed by this upstream commit: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d66a57be2f9a315fc10d0f524f670fec903e0fb4 > > Which has also been added to 5.8.6, so I believe that this is fully resolved now, > sorry for the wrong bug report. No problem, glad it's all now working properly, thanks for the follow-up. greg k-h
