On Wed, Jan 20, 2021 at 8:28 AM Hans de Goede <hdegoede(a)redhat.com> wrote:
Hi All,
An old problem with the XHCI driver has resurfaced, likely this was fixed in the
Fedora branched kernels but not in rawhide / the ARK kernels.
So now we again have users reporting that none of their USB ports work
any longer after installing the 5.10 kernel, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1917000
I believe that this is a regression caused by the XHCI driver being built as a module
again, we had the same issue with 5.9 where we set CONFIG_USB_XHCI_PCI_RENESAS=m in the
kernel config, but CONFIG_USB_XHCI_PCI actually depends on CONFIG_USB_XHCI_PCI_RENESAS
(when the latter is not set to "n"), so selecting CONFIG_USB_XHCI_PCI_RENESAS=m
forces CONFIG_USB_XHCI_PCI=m.
Like with 5.9 I have no idea why having XHCI as a module completely breaks XHCI support
on some boards (*), but since we want it to be builtin anyways the fix is to set:
CONFIG_USB_XHCI_PCI=y
CONFIG_USB_XHCI_PCI_RENESAS=y
As we have in 5.9. I suspect that when this was fixed in 5.9, we forgot to port the fix
to rawhide / to the ARK configs.
Can we please get this fixed asap for 5.10 (which is being shipped to
normal Fedora users now) and also fix this for rawhide and the ARK configs ?
Regards,
Hans
*) I suspect some ACPI power-resource getting turned off before loading the initrd,
because it is not in use and this breaks XHCI support when the module loads later
Sorry, this has now been fixed for rawhide, and 5.10 stable kernels.
It will appear in Fedora stable starting with 5.10.10 kernels.
Justin