Ubuntu
linux-oem-5.17 package

  1. Jammy (22.04)
  2. Bug #1967067
  3. Comment #7

Comment 7 for bug 1967067

Revision history for this message
Yao Wei (medicalwei) wrote (last edit ):

With linux-oem-5.14/5.14.0-1033.36, this issue is not reproducible within 20 cold reboots.

A script is used to run rtcwake to cold boot 20 times and attach `bluetoothctl scan on` result to a log file. If the bluetooth device cannot be probed, the scan should output "No default controller available". There was no such error when using 5.14.0-1033.36 kernel.