From: Luke Nowakowski-Krijger <luke.nowakowskikrijger@canonical.com> To: linux-usb@vger.kernel.org Cc: hdegoede@redhat.com, mathias.nyman@linux.intel.com, chris.chiu@canonical.com, stern@rowland.harvard.edu, kishon@ti.com Subject: Deferring xhci primary roothub registration Date: Mon, 4 Apr 2022 09:38:39 -0700 [thread overview] Message-ID: <20220404163839.19102-1-luke.nowakowskikrijger@canonical.com> (raw) Hello, There have been some users using Ubuntu 5.4 based kernels with certain intel xHCI controllers that are experiencing USB devices not being detected during boot [4][5]. This problem seems to have been reintroduced after the patchset that deferred primary roothub registration to address device enumeration before xHC is running was reverted due to regressions [1][2]. My question is if there has been any efforts to reintroduce these patches or any other fixes that I am not aware of to address the original problem [3]? There seem to have been many bug fixes addressing the problems referenced in the original regression report [2] to do with this patch series, is there anything in the way of reintroducing these patches? From only looking at the mailing list discussions and various bug reports, I still am not exactly sure what the problems with these patches were in the first place. Anyways, these things seem pretty tricky and I would appreciate any insight on the matter :) Thanks, - Luke [1] https://lore.kernel.org/all/20211104141158.561738875@linuxfoundation.org/ [2] https://lore.kernel.org/all/42bcbea6-5eb8-16c7-336a-2cb72e71bc36@redhat.com/ [3] https://bugzilla.kernel.org/show_bug.cgi?id=214021 [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638 [5] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211
next reply other threads:[~2022-04-04 21:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-04 16:38 Luke Nowakowski-Krijger [this message] 2022-04-07 16:48 ` Mathias Nyman
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220404163839.19102-1-luke.nowakowskikrijger@canonical.com \ --to=luke.nowakowskikrijger@canonical.com \ --cc=chris.chiu@canonical.com \ --cc=hdegoede@redhat.com \ --cc=kishon@ti.com \ --cc=linux-usb@vger.kernel.org \ --cc=mathias.nyman@linux.intel.com \ --cc=stern@rowland.harvard.edu \ --subject='Re: Deferring xhci primary roothub registration' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).