Also affected on 7.0.0-31-generic (not just -28), and I think I've narrowed down the trigger.
**Hardware:** ASUS ROG Strix G16 G615LW, BIOS G615LW.318 (05/12/2025), Ubuntu 24.04 with linux-image-generic-hwe-24.04 7.0.0-31.31~24.04.1. **Symptom:** identical reset storm on the N-KEY device. ``` usb 5-4: new full-speed USB device number 2 using xhci_hcd usb 5-4: New USB device found, idVendor=0b05, idProduct=19b6, bcdDevice= 3.18 usb 5-4: reset full-speed USB device number 2 using xhci_hcd <- repeats ~1x/sec ``` 1170 resets in 24 minutes of uptime. **The device is not re-enumerating.** The HID children are created once at boot and are never torn down: ``` /sys/bus/hid/devices/0003:0B05:19B6.0002 -> .../usb5/5-4/5-4:1.0/0003:0B05:19B6.0002 /sys/bus/hid/devices/0003:0B05:19B6.0003 -> .../usb5/5-4/5-4:1.1/0003:0B05:19B6.0003 ``` Both keep their original boot timestamps for the whole session. So these are USB-level resets from a control/feature-report timeout, not a failing probe followed by re-probe. **Trigger appears to be asusd (asusctl), not the kernel alone.** Stopping the daemon stops the storm immediately and completely: ``` Sep 11 21:44:44 kernel: usb 5-4: reset full-speed USB device number 2 using xhci_hcd <- last reset Sep 11 21:44:45 systemd[1]: Stopped asusd.service - ASUS Notebook Control. ``` Zero resets afterwards. Restarting asusd brings the storm straight back. asusd is v6.3.2, built from source. Its unit file already carries an `ExecStartPre=/bin/sleep 1` with the comment "required to prevent init issues with hid_asus and MCU", so there is a known-fragile interaction here that 7.0 seems to have made worse. It also lines up with the recent hid-asus work upstream around `QUIRK_ROG_NKEY_LEGACY` and the `-32` handshake failure — if the feature-report handshake now fails where it used to succeed, asusd's retry loop would produce exactly this pattern. **Workaround:** masking asusd keeps kernel 7.0 fully usable. Everything asusd managed except the RGB backlight is available natively (`platform_profile` + power-profiles-daemon, hwmon `pwm*_auto_point*` fan curves, `asus-armoury` firmware-attributes for TGP/MUX/panel overdrive). Only the battery charge threshold needs a small oneshot unit to be re-applied at boot. Happy to test a patched kernel or collect any further tracing that would help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2161269 Title: Internal keyboard (ASUS N-KEY Device 0b05:19b6) unusable on 7.0.0-28-generic — USB reset loop, works fine on 6.17.0-35-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-7.0/+bug/2161269/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
