New: [REGRESSION] Kernel panic in ucsi_reset_ppm on 6.1.0-42 after HP USB-C Dock G5 firmware update
https://bugzilla.kernel.org/show_bug.cgi?id=221022
Bug ID: 221022
Summary: [REGRESSION] Kernel panic in ucsi_reset_ppm on
6.1.0-42 after HP USB-C Dock G5 firmware update
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: low
Priority: P3
Component: USB
Assignee: [email protected]
Reporter: [email protected]
Regression: No
Created attachment 309280
--> https://bugzilla.kernel.org/attachment.cgi?id=309280&action=edit
dmesg
I'm experiencing a kernel panic during boot on kernel 6.1.0-42-amd64 that does not occur on 6.1.0-35-amd64. The issue appeared immediately after updating the HP USB-C Dock G5 firmware from 1.0.18.0 to 1.0.24.0 via fwupd.
## System Information
- **Hardware**: ASUS Zephyrus M GU502GV (Intel Core i7-9750H, RTX 2060 Mobile)
- **Distribution**: Debian 12 (Bookworm)
- **Working Kernel**: 6.1.0-35-amd64 (6.1.137-1)
- **Broken Kernel**: 6.1.0-42-amd64 (6.1.159-1)
- **Dock**: HP USB-C Dock G5 (firmware 1.0.24.0)
## Problem Description
After updating the dock firmware, kernel 6.1.0-42 hangs during boot at the UCSI driver initialization. The system becomes completely unresponsive and never reaches the login screen. Kernel 6.1.0-35 boots successfully with the same firmware.
## Error Messages
**Kernel 6.1.0-42** (boot hangs after this):
``` WARNING: CPU: 5 PID: 107 at drivers/usb/typec/ucsi/ucsi.c:918 ucsi_reset_ppm+0x210/0x220 [typec_ucsi] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-70) ```
**Kernel 6.1.0-35** (boots successfully with warning):
``` WARNING: CPU: 10 PID: 117 at drivers/usb/typec/ucsi/ucsi.c:917 ucsi_reset_ppm+0x210/0x220 [typec_ucsi] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-70) typec port0: bound usb1-port4 (ops connector_ops [usbcore]) typec port0: bound usb2-port1 (ops connector_ops [usbcore]) [boot continues successfully] ```
The same UCSI error occurs in both kernels, but 6.1.0-42 treats it as fatal while 6.1.0-35 logs the warning and continues.
## Reproduction
1. Update HP USB-C Dock G5 firmware to 1.0.24.0 via fwupd
2. Boot system with dock connected
3. System hangs at UCSI initialization on 6.1.0-42
4. Boot with kernel 6.1.0-35 - system boots normally
## Additional Information
**UCSI driver status on working kernel (6.1.0-35):**
``` $ lsmod | grep ucsi ucsi_acpi 16384 0 typec_ucsi 53248 1 ucsi_acpi roles 20480 1 typec_ucsi typec 94208 1 typec_ucsi ```
**USB-C port status:**
``` $ cat /sys/class/typec/port0/data_role [host] device $ cat /sys/class/typec/port0/power_role source [sink] $ cat /sys/class/typec/port0/supported_accessory_modes none ```
**Dock detection (working kernel):**
``` $ lsusb | grep HP Bus 002 Device 004: ID 03f0:066b HP, Inc HP USB-C Dock G5 Bus 001 Device 009: ID 03f0:046b HP, Inc HP USB-C Dock G5 Bus 001 Device 007: ID 03f0:056b HP, Inc USB Audio Bus 001 Device 006: ID 03f0:036b HP, Inc HP USB-C Dock G5 ```
## Expected Behavior
Kernel 6.1.0-42 should handle the UCSI error the same way as 6.1.0-35 - log the warning and continue boot rather than hanging.
## Workaround
Booting kernel 6.1.0-35 works perfectly. All dock functionality (USB devices, Ethernet) works correctly, though DisplayPort Alt Mode fails to initialize on both kernels.
## Attachments
I can provide:
- Full dmesg output from both kernels
- Complete /sys/class/typec/ directory contents
- Detailed lsusb -v output for the dock
- Kernel config differences between versions
Let me know if you need any additional information.
Thanks
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 221022] [REGRESSION] Kernel panic in ucsi_reset_ppm on 6.1.0-42 after HP USB-C Dock G5 firmware update
https://bugzilla.kernel.org/show_bug.cgi?id=221022
The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) --- Could you please bisect and check if mainline is affected, too? See
https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html for
details. And a more complete stack trace when things hang would be helpful (and
might avoid the need for a bisection if you are lucky).
Without these details nobody might look into this.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.