From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Kevin Locke <kevin@kevinlocke.name>,
linux-usb@vger.kernel.org,
Mathias Nyman <mathias.nyman@intel.com>
Subject: Re: Oops from xhci_configure_endpoint on resume from S3
Date: Tue, 12 Jan 2021 13:01:47 +0200 [thread overview]
Message-ID: <e4bdb222-db95-5311-e0ac-2adce2ea5b7e@linux.intel.com> (raw)
In-Reply-To: <X/elzOTOOJMAc+1e@kevinlocke.name>
On 8.1.2021 2.22, Kevin Locke wrote:
> On a ThinkPad T430 (2342-CTO) with an Intel 7 Series USB xHCI Host
> Controller (8086:1e31) running Linux 5.11-rc2 (or torvalds master
> 71c061d24438, or 4.19.0-13-amd64 from Debian stable), I can provoke a
> kernel Oops in code called from xhci_configure_endpoint by doing the
> following (performed after booting into single-user mode):
>
> 1. Connect USB3 UAS disk drive (Seagate Backup Plus Hub - 1180:e823)
> 2. When "Spinning up disk..." is logged by the kernel, initiate suspend
> to memory (`echo mem >/sys/power/state`).
> 3. Once suspended, disconnect the drive.
> 4. Initiate wake then immediately plug and unplug a USB2 device (Yubikey
> 1050:0406) in the same port repeatedly.
>
> This usually causes the system to freeze (unresponsive to Magic SysRq).
> If not, repeat the steps. Relevant (decoded) dmesg (from EFI pstore):
>
> kernel BUG at lib/list_debug.c:54!
This Panther Point xHCI was the only one that needed software bandwidth management.
Looks like the bandwidth management list is left in some bad state, I'll take a look at it.
...
>
> Let me know if there's anything else I can do to help diagnose/debug.
Thanks, I might need some help with testing patches
-Mathias
prev parent reply other threads:[~2021-01-12 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 0:22 Oops from xhci_configure_endpoint on resume from S3 Kevin Locke
2021-01-12 11:01 ` Mathias Nyman [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=e4bdb222-db95-5311-e0ac-2adce2ea5b7e@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=kevin@kevinlocke.name \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox