I am not a native English speaker and I am not very familiar with Linux, so I used AI and a translator to write this post. Thank you for your understanding.
I am on Ubuntu 24.04 HWE with kernel 6.17.0-22-generic.
Hardware:
- Motherboard: BIOSTAR B650MT-E PRO
- BIOS: American Megatrends / BIOSTAR version 5.35, release date 2025-09-26
- CPU/platform: AMD AM5/B650
- SSD: NVMe, SMART health passed
Problem:
When I try to use adb with my Android phone, my desktop hard reboots. This happened before with a wired USB connection, and now it also happened with wireless adb.
The sequence was roughly:
adb pair
adb connect
scrcpy failed with "could not ..." (I cannot remember the exact message)
adb devices
immediate reboot
adb works normally on my server:
The same phone and wireless adb setup works fine on my Ubuntu Server laptop, so the phone itself is probably not the issue.
Comparison machine where wireless adb works fine:
- Ubuntu Server 24.04.4 LTS
- Kernel: 6.8.0-101-generic
- Hardware: MSI Sword 17 A11UE laptop
- CPU: Intel Core i7-11800H
- BIOS: E17L1IMS.310, release date 2022-01-20
- adb: Android Debug Bridge 1.0.41, version 34.0.4-debian
- adb package: adb 1:34.0.4-1build3 from Ubuntu noble/universe
Logs:
last -x shows the previous session ended with crash.
journalctl has no useful kernel logs immediately before the reboot.
/sys/fs/pstore is empty.
/var/crash only has an unrelated VS Code crash.
After reboot, journal shows:
x86/amd: Previous system reset reason [0x00300800]: software wrote 0xE to reset control register 0xCF9
x86/amd: Previous system reset reason [0x00300800]: ACPI power state transition occurred
I also repeatedly see:
ACPI BIOS Error (bug): Failure creating named object [\_GPE._L02], AE_ALREADY_EXISTS
No MCE errors.
No PCIe AER errors.
NVMe SMART:
- overall health: PASSED
- media/data integrity errors: 0
- unsafe shutdowns: 15
Installed kernels:
- 6.17.0-20-generic
- 6.17.0-22-generic
Question:
Could this be a kernel regression, BIOS/ACPI issue, or adb triggering a USB/xHCI/ACPI bug?
What should I check next without repeatedly forcing hard reboots?