From: Harry Wentland <harry.wentland@amd.com>
To: linux-usb@vger.kernel.org, mathias.nyman@linux.intel.com
Cc: regressions@lists.linux.dev, "Limonciello,
Mario" <Mario.Limonciello@amd.com>,
mika.westerberg@linux.intel.com, Raju.Rangoju@amd.com,
Sanath.S@amd.com, Greg KH <gregkh@linuxfoundation.org>
Subject: [REGRESSION] usb: acpi: add device link between tunneled USB3 device and USB4 Host Interface
Date: Wed, 2 Oct 2024 13:42:29 -0400 [thread overview]
Message-ID: <cf45e722-144f-4d06-8dd9-2f7f54283fbc@amd.com> (raw)
I was checking out the 6.12 rc1 (through drm-next) kernel and found
my system hung at boot. No meaningful message showed on the kernel
boot screen.
A bisect revealed the culprit to be
commit f1bfb4a6fed64de1771b43a76631942279851744 (HEAD)
Author: Mathias Nyman <mathias.nyman@linux.intel.com>
Date: Fri Aug 30 18:26:29 2024 +0300
usb: acpi: add device link between tunneled USB3 device and USB4 Host Interface
A revert of this single patch "fixes" the issue and I can boot again.
The system in question is a Thinkpad T14 with a Ryzen 7 PRO 6850U CPU.
It's running Arch Linux but I doubt that's of consequence.
lspci output:
https://gist.github.com/hwentland/59aef63d9b742b7b64d2604aae9792e0
acpidump:
https://gist.github.com/hwentland/4824afc8d712c3d600be5c291f7f1089
Mario suggested I try modprobe.blacklist=xhci-hcd but that did nothing.
Another suggestion to do usbcore.nousb lets me boot to the desktop
on a kernel with the faulty patch, without USB functionality, obviously.
I'd be happy to try any patches, provide more data, or run experiments.
Thanks,
Harry
next reply other threads:[~2024-10-02 17:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 17:42 Harry Wentland [this message]
2024-10-02 19:39 ` [REGRESSION] usb: acpi: add device link between tunneled USB3 device and USB4 Host Interface Mario Limonciello
2024-10-03 5:47 ` Mika Westerberg
2024-10-03 13:10 ` Mario Limonciello
2024-10-03 13:27 ` Mika Westerberg
2024-10-03 13:42 ` Mario Limonciello
2024-10-03 13:47 ` Mika Westerberg
2024-10-03 18:23 ` Harry Wentland
2024-10-03 18:51 ` Harry Wentland
2024-10-03 19:09 ` Mario Limonciello
2024-10-03 19:41 ` Harry Wentland
2024-10-04 6:20 ` Mika Westerberg
2024-10-03 19:48 ` Michał Pecio
2024-10-03 20:43 ` Harry Wentland
2024-10-03 21:42 ` Michał Pecio
2024-10-09 21:52 ` Mathias Nyman
2024-10-10 2:23 ` Mario Limonciello
2024-10-10 12:01 ` Mathias Nyman
2024-10-16 19:48 ` Harry Wentland
2024-10-21 10:56 ` Mathias Nyman
2024-10-22 12:33 ` 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=cf45e722-144f-4d06-8dd9-2f7f54283fbc@amd.com \
--to=harry.wentland@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Raju.Rangoju@amd.com \
--cc=Sanath.S@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=regressions@lists.linux.dev \
/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.