All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 222091] Regression 7.1.10→7.2.x: poweroff hangs after Lenovo USB4 dock (40BF) connected during session; state persists after unplug
Date: Tue, 06 Oct 2026 18:47:21 +0000	[thread overview]
Message-ID: <bug-222091-208809-SmWiVLDhWa@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222091-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=222091

--- Comment #2 from AlexTLDR (abadragan@gmail.com) ---
(In reply to Artem S. Tashkinov from comment #1)
> Could you please bisect?
> 
> Any LLM can guide you through it.

Follow-up: I found that the regression is resolved by the kernel
parameter thunderbolt.host_reset=0. With it, the machine powers off
cleanly even after the dock has been connected during the session.

Looking at what changed in drivers/thunderbolt between the last good
(7.1.x) and first bad (7.2.x) kernels, the suspect is commit
5f40cba7d4 "thunderbolt: Assert downstream port reset on shutdown",
merged for v7.2-rc1. That commit forces the host_reset path in the
PCI ->shutdown callback and asserts PORT_CS_19.DPR on each connected
downstream port before tearing down the router tree. This matches all
observations on this machine:

- the hang only occurs once the dock (router 17ef:118d) has been
  connected in the session, i.e. once a connected downstream port
  exists to assert the reset on
- the fault is latched (later unplugging does not help)
- host_reset=0 skips exactly this new shutdown-time reset sequence
  and the poweroff hang disappears
- "modprobe -r thunderbolt" deadlocks in the same teardown path

So the regression appears to be in the new downstream-port-reset
(SBTX-low) sequence: on this hardware (Insyde BIOS 1.07.03dTPCS,
Intel Core Ultra 200V, NHI 8086:a833) the assertion against the
Lenovo 40BF dock router never completes and the machine hangs at
firmware handoff.

Since that commit fixed a real issue elsewhere (60 s polling of a
dead link / warm reset on some platforms), a plain revert is probably
not the answer - perhaps the DPR assertion needs a timeout or a
quirk. Happy to test a patch or a scratch build with the revert to
confirm the identification.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-10-06 18:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 16:33 [Bug 222091] New: Regression 7.1.10→7.2.x: poweroff hangs after Lenovo USB4 dock (40BF) connected during session; state persists after unplug bugzilla-daemon
2026-10-05 11:28 ` [Bug 222091] " bugzilla-daemon
2026-10-06 18:47 ` bugzilla-daemon [this message]
2026-10-07  7:47 ` bugzilla-daemon
2026-10-08 17:23 ` bugzilla-daemon

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=bug-222091-208809-SmWiVLDhWa@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.