[Bug 222091] Regression 7.1.10→7.2.x: poweroff hangs after Lenovo USB4 dock (40BF) connected during session; state persists after unplug

[bugzilla-daemon@kernel.org]

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

--- Comment #4 from AlexTLDR (abadragan@gmail.com) ---
(In reply to Artem S. Tashkinov from comment #3)
> Guesses aren't really accepted here.
> 
> Fetch 7.2.9, revert the patch, confirm everything's working fine.

Follow up on the test. Fresh install, 7.2.9-200.fc44.

First boot, clean command line, no thunderbolt.host_reset. Dock connected
during the session, router 0-3 (17ef:118d) and the retimer enumerated
fine. Poweroff hung again, stuck on the firmware splash, needed a hard
power off. The journal from that boot ends at

systemd-shutdown[1]: Syncing filesystems and block devices.
systemd-shutdown[1]: Sending SIGTERM to remaining processes...
systemd-journald[789]: Journal stopped

so userspace finished cleanly (poweroff.target reached, filesystems
synced) and the hang happens after journald is gone. pstore caught
nothing (Fedora has CONFIG_PSTORE_CONSOLE off, and a hang is not a panic
anyway), so the last kernel messages are not recoverable from disk. I
kept the full kernel log of that session, can attach it if useful.

Then booted the same 7.2.9 kernel with thunderbolt.host_reset=0, dock
connected for the whole session, and poweroff works cleanly again.

Summary: stock 7.2.9 hangs on poweroff once the 40BF dock has been
connected, same 7.2.9 with thunderbolt.host_reset=0 powers off fine. So
the parameter still fully works around the issue on 7.2.9, same behavior
as 7.2.5 to 7.2.8.

If it helps I can set up netconsole to a second machine and capture the
console during the hanging poweroff, that should show exactly where the
shutdown path stops. Also happy to test any patch or scratch build.

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

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