From: Joe Minor <joe@alujoe.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Problem: xhci: devices can not be enumerated due to bandwidth issues
Date: Tue, 11 Jan 2022 20:44:17 +0100 [thread overview]
Message-ID: <Yd3eESRmmlic71q7@trivial> (raw)
In-Reply-To: <4c944b85-06a4-dd90-27df-71f35190f189@linux.intel.com>
Hi
On Mon, Jan 10, 2022 at 11:39:10PM +0200, Mathias Nyman wrote:
> > I bisected the issue to commit 2847c46c6148 ('Revert "USB: xhci: fix U1/U2 handling for hardware with XHCI_INTEL_HOST quirk set"'), which also mentions xhci bandwidth issues.
>
> This change will enable xhci USB Link power management for some devices.
> It adds a few more items to do during enumeration for them.
Is this introducing the problem a sign of an issue with hardware or setup?
> If you could boot with usb core and xhci dynamic debugging enabled it could show more.
> Add "usbcore.dyndbg=+p xhci_hcd.dyndbg=+p" to your kernel cmdline
Here is the output of dmesg | grep -i "usb\|xhci": https://gist.github.com/alujoe/8539793d755ed818da50bac5b2e960a5
(I did not apply the patch below before capturing the output)
Does the log include something useful?
>
> Also, could be worth checking if removing XHCI_LPM_SUPPORT from your kernel helps:
>
>
> diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
> index 5c351970cdf1..7434406be452 100644
> --- a/drivers/usb/host/xhci-pci.c
> +++ b/drivers/usb/host/xhci-pci.c
> @@ -202,7 +202,6 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)
> xhci->quirks |= XHCI_BROKEN_D3COLD;
>
> if (pdev->vendor == PCI_VENDOR_ID_INTEL) {
> - xhci->quirks |= XHCI_LPM_SUPPORT;
> xhci->quirks |= XHCI_INTEL_HOST;
> xhci->quirks |= XHCI_AVOID_BEI;
> }
>
The change did help! This might be a viable workaround.
Thanks
Joe
prev parent reply other threads:[~2022-01-11 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 15:03 Problem: xhci: devices can not be enumerated due to bandwidth issues Joe Minor
2022-01-10 21:39 ` Mathias Nyman
2022-01-11 19:44 ` Joe Minor [this message]
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=Yd3eESRmmlic71q7@trivial \
--to=joe@alujoe.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.