From: Michal Pecio <michal.pecio@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Phani Kumar <phanigudipally@gmail.com>, linux-usb@vger.kernel.org
Subject: Re: [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays
Date: Fri, 20 Nov 2026 11:30:15 +0100 [thread overview]
Message-ID: <20261120113015.30edfd66.michal.pecio@gmail.com> (raw)
In-Reply-To: <20261120071202.GH229695@black.igk.intel.com>
On Fri, 20 Nov 2026 08:12:02 +0100, Mika Westerberg wrote:
> > 3. Should r8152 back off after -EPROTO instead of resubmitting
> > immediately? That seems to be what pushes the xHC over in case 1.
>
> For this I hope Mathias has an answer :)
FYI, Microsoft asks drivers to check if the device still exists before
attempting any recovery (and also to cancel all URBs and reset the pipe
before submitting more URBs, but that's unrelated).
https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/how-to-recover-from-usb-pipe-errors
This may be the reason why I have observed Windows in QEMU reading the
root hub port register before performing endpoint reset. And xhci-hcd
does similar checks, but it only detects root hub disconnection.
It seems that Intel HW either assumes that unreachable endponts won't
be restarted, or it has some general problems with restars that weren't
happening in other circumstances often enough to be noticed.
I wonder what happens if the same devices is disconnected from the same
or similar Intel HC, but behind an ordinary USB3 hub?
We also have that case of repeated UVC operations and/or isochronous
stream restarts (?) on some USB3 cameras crashing some Intel HCs.
I don't have any Intel HW to play with, only AMD.
Regards,
Michal
prev parent reply other threads:[~2026-11-20 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMcR36+hWzhS_Pytej3uoDvOU6160v5vtuWXSnyFb=zEoRFQJQ@mail.gmail.com>
2026-11-04 12:10 ` xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays Mika Westerberg
2026-11-10 9:08 ` Mathias Nyman
[not found] ` <CAMcR36LCr0RFrHsLFPaPziPS=1CMbEnO3GcDk=3Oe33S8uZFpw@mail.gmail.com>
2026-11-12 14:55 ` Mathias Nyman
[not found] ` <CAMcR36KcP7cMZ2D1pu_bC-R0uPn2chd_1jEzp4FBBq-jZz=D3A@mail.gmail.com>
2026-11-20 7:12 ` [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: " Mika Westerberg
2026-11-20 10:30 ` Michal Pecio [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=20261120113015.30edfd66.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=phanigudipally@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox