From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Norbert Preining <norbert@preining.info>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Cc: Norbert Preining <norbert@preining.info>
Subject: Re: [5.12 - 5.15] xHCI controller dead - not renesas but intel
Date: Tue, 16 Nov 2021 00:37:14 +0200 [thread overview]
Message-ID: <8f752efb-e38e-b012-de98-e4b938dde7b7@linux.intel.com> (raw)
In-Reply-To: <YY3RIdKBbIL3Dw/q@bulldog.preining.info>
On 12.11.2021 4.27, Norbert Preining wrote:
> Dear all,
>
> (please Cc)
>
> I see quite some discussion here about hanging USB controls from
> Renesas. Interestingly, I see the very same behaviour with my Intel USB
> controller:
> 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
>
> It happens again and again that:
> Nov 12 10:57:58 bulldog kernel: xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
> Nov 12 10:57:58 bulldog kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
> Nov 12 10:57:58 bulldog kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
> Nov 12 10:57:58 bulldog kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
>
> and I loose all mouse/kbd access.
>
> I have the feeling that it happens more often/at all when I redirect my
> USB webcam to a virtual machine using virt-manager.
> Before the above happened, the log showed
> Nov 12 10:57:06 bulldog kernel: usb 1-12: reset high-speed USB device number 47 using xhci_hcd
> Nov 12 10:57:11 bulldog kernel: usb 1-12: device descriptor read/64, error -110
> Nov 12 10:57:27 bulldog kernel: usb 1-12: device descriptor read/64, error -110
> Nov 12 10:57:27 bulldog kernel: usb 1-12: reset high-speed USB device number 47 using xhci_hcd
> Nov 12 10:57:32 bulldog kernel: usb 1-12: device descriptor read/64, error -110
> Nov 12 10:57:48 bulldog kernel: usb 1-12: device descriptor read/64, error -110
> Nov 12 10:57:48 bulldog kernel: usb 1-12: reset high-speed USB device number 47 using xhci_hcd
>
> where
> HD Pro Webcam C920 as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/input/input40
>
> I am currently running 5.15.1.
>
> Is there anything (besides ssh-ing into the machine and unbind/bind the
> pci device) I can provide or do?
Patch in link below resolved another case with similar log.
Does it help in your case?
https://lore.kernel.org/linux-usb/20211115221630.871204-1-mathias.nyman@linux.intel.com/T/#u
-Mathias
next prev parent reply other threads:[~2021-11-16 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 2:27 [5.12 - 5.15] xHCI controller dead - not renesas but intel Norbert Preining
2021-11-15 22:37 ` Mathias Nyman [this message]
2021-11-15 23:48 ` Norbert Preining
2021-11-18 1:16 ` Norbert Preining
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=8f752efb-e38e-b012-de98-e4b938dde7b7@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=norbert@preining.info \
/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 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).