* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
@ 2024-01-24 23:39 ` bugzilla-daemon
2024-01-30 14:21 ` bugzilla-daemon
` (35 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-01-24 23:39 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Nickolas Gupton (nickolas@gupton.xyz) changed:
What |Removed |Added
----------------------------------------------------------------------------
Hardware|All |Intel
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
2024-01-24 23:39 ` [Bug 218416] " bugzilla-daemon
@ 2024-01-30 14:21 ` bugzilla-daemon
2024-01-30 17:05 ` bugzilla-daemon
` (34 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-01-30 14:21 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #1 from Nickolas Gupton (nickolas@gupton.xyz) ---
This issue is still present in kernel 6.7.2
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
2024-01-24 23:39 ` [Bug 218416] " bugzilla-daemon
2024-01-30 14:21 ` bugzilla-daemon
@ 2024-01-30 17:05 ` bugzilla-daemon
2024-02-04 10:31 ` bugzilla-daemon
` (33 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-01-30 17:05 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #2 from Dustin (dustin@falgout.us) ---
I'm also experiencing this issue. It started with kernel 6.5. Bluetooth has
been broken ever since. The issue was not present in earlier versions of the
kernel.
```
$ uname -a
Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
```
```
$ lsusb | grep -i bluetooth
Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
```
```
$ journalctl -b | egrep -i bluetooth
Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed
(-110)
```
```
linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all
[installed,automatic]
```
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (2 preceding siblings ...)
2024-01-30 17:05 ` bugzilla-daemon
@ 2024-02-04 10:31 ` bugzilla-daemon
2024-02-10 23:07 ` bugzilla-daemon
` (32 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-02-04 10:31 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #3 from Nickolas Gupton (nickolas@gupton.xyz) ---
This issue is still present in kernel 6.7.3
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (3 preceding siblings ...)
2024-02-04 10:31 ` bugzilla-daemon
@ 2024-02-10 23:07 ` bugzilla-daemon
2024-02-11 20:32 ` bugzilla-daemon
` (31 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-02-10 23:07 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #4 from Dustin (dustin@falgout.us) ---
I discovered that Bluetooth starts working again after a cold boot (shutdown,
disconnect power for 30 seconds, then boot normally).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (4 preceding siblings ...)
2024-02-10 23:07 ` bugzilla-daemon
@ 2024-02-11 20:32 ` bugzilla-daemon
2024-02-15 20:43 ` bugzilla-daemon
` (30 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-02-11 20:32 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #5 from Nickolas Gupton (nickolas@gupton.xyz) ---
Bluetooth still does not work with 6.7.4, however the logs have changed from
the error that was shown before:
$ journalctl -b | grep -E -i bluetooth
Feb 11 14:27:14 andromeda kernel: Bluetooth: Core ver 2.22
Feb 11 14:27:14 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Feb 11 14:27:14 andromeda kernel: Bluetooth: HCI device and connection manager
initialized
Feb 11 14:27:14 andromeda kernel: Bluetooth: HCI socket layer initialized
Feb 11 14:27:14 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Feb 11 14:27:14 andromeda kernel: Bluetooth: SCO socket layer initialized
Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Found device firmware:
intel/ibt-20-1-3.sfi
Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Firmware Version:
255-255.255
Feb 11 14:27:15 andromeda systemd[1]: Reached target Bluetooth Support.
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: FW download error recovery
failed (-19)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: sending frame failed (-19)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Reading supported features
failed (-19)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Error reading debug features
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit
is set, but its usage is not supported.
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: sending frame failed (-19)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-19)
Feb 11 14:27:15 andromeda systemd[1]: Stopped target Bluetooth Support.
Feb 11 14:27:15 andromeda NetworkManager[781]: <info> [1707683235.5366] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Bootloader revision 0.3
build 0 week 24 2017
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Device revision is 1
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Secure boot is enabled
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: OTP lock is enabled
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: API lock is enabled
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Debug lock is disabled
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Minimum firmware build 1
week 10 2014
Feb 11 14:27:15 andromeda systemd[1]: Reached target Bluetooth Support.
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Found device firmware:
intel/ibt-20-1-3.sfi
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Firmware Version:
255-255.255
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Waiting for firmware
download to complete
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Firmware loaded in 1386206
usecs
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Waiting for device to boot
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Device booted in 14608 usecs
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Malformed MSFT vendor event:
0x02
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-20-1-3.ddc
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Applying Intel DDC
parameters completed
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Firmware revision 0.3 build
249 week 27 2023
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit
is set, but its usage is not supported.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (5 preceding siblings ...)
2024-02-11 20:32 ` bugzilla-daemon
@ 2024-02-15 20:43 ` bugzilla-daemon
2024-03-09 16:52 ` bugzilla-daemon
` (29 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-02-15 20:43 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Jhon (vjstink@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vjstink@gmail.com
--- Comment #6 from Jhon (vjstink@gmail.com) ---
I have the same issue as Nickolas, turning off the computer does not help.
The device is also the same: Intel AX200 8087:0029. Mine is on a desktop
motherboard.
$ uname -r
6.7.4-arch1-1
$ lsusb | grep -i bluetooth
Bus 001 Device 006: ID 8087:0029 Intel Corp. AX200 Bluetooth
$ journalctl -b | grep -E -i bluetooth
----
Feb 15 09:06:07 home bluetoothd[948]: Bluetooth management interface 1.22
initialized
Feb 15 09:06:07 home systemd[1]: Started Bluetooth service.
Feb 15 09:06:07 home systemd[1]: Reached target Bluetooth Support.
Feb 15 09:06:07 home NetworkManager[1027]: <info> [1707980767.6232] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
Feb 15 09:06:08 home kernel: Bluetooth: hci0: Reading Intel version command
failed (-110)
Feb 15 09:06:08 home kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Same error was present on 6.7.3 and 6.7.2. I believe 6.6.9 was the last version
where it worked fine.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (6 preceding siblings ...)
2024-02-15 20:43 ` bugzilla-daemon
@ 2024-03-09 16:52 ` bugzilla-daemon
2024-03-25 9:38 ` bugzilla-daemon
` (28 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-03-09 16:52 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #7 from Nickolas Gupton (nickolas@gupton.xyz) ---
Bluetooth is still not working on boot with kernel 6.7.9 with linux-firmware
20240220
$ lsusb | grep -i bluetooth
Bus 001 Device 008: ID 8087:0029 Intel Corp. AX200 Bluetooth
$ journalctl -b | grep -E -i bluetooth
Mar 09 10:41:19 andromeda kernel: Bluetooth: Core ver 2.22
Mar 09 10:41:19 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Mar 09 10:41:19 andromeda kernel: Bluetooth: HCI device and connection manager
initialized
Mar 09 10:41:19 andromeda kernel: Bluetooth: HCI socket layer initialized
Mar 09 10:41:19 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Mar 09 10:41:19 andromeda kernel: Bluetooth: SCO socket layer initialized
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Found device firmware:
intel/ibt-20-1-3.sfi
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Firmware Version:
255-255.255
Mar 09 10:41:20 andromeda systemd[1]: Reached target Bluetooth Support.
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: FW download error recovery
failed (-19)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: sending frame failed (-19)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Reading supported features
failed (-19)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Error reading debug features
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit
is set, but its usage is not supported.
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: sending frame failed (-19)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-19)
Mar 09 10:41:20 andromeda systemd[1]: Stopped target Bluetooth Support.
Mar 09 10:41:20 andromeda NetworkManager[795]: <info> [1710002480.4767] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Bootloader revision 0.3
build 0 week 24 2017
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Device revision is 1
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Secure boot is enabled
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: OTP lock is enabled
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: API lock is enabled
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Debug lock is disabled
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Minimum firmware build 1
week 10 2014
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Found device firmware:
intel/ibt-20-1-3.sfi
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Firmware Version:
255-255.255
Mar 09 10:41:20 andromeda systemd[1]: Reached target Bluetooth Support.
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Waiting for firmware
download to complete
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Firmware loaded in 1393326
usecs
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Waiting for device to boot
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Device booted in 14610 usecs
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Malformed MSFT vendor event:
0x02
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-20-1-3.ddc
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Applying Intel DDC
parameters completed
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Firmware revision 0.3 build
249 week 27 2023
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit
is set, but its usage is not supported.
However, if I run this script (may take 2-3 runs sometimes) it will work:
$ cat reset_bluetooth.sh
modprobe -r btusb
modprobe -r btintel
sleep 2
modprobe btintel
modprobe btusb
sleep 1
systemctl restart bluetooth
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (7 preceding siblings ...)
2024-03-09 16:52 ` bugzilla-daemon
@ 2024-03-25 9:38 ` bugzilla-daemon
2024-03-29 8:52 ` bugzilla-daemon
` (27 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-03-25 9:38 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #8 from Jhon (vjstink@gmail.com) ---
(In reply to Nickolas Gupton from comment #7)
> Bluetooth is still not working on boot with kernel 6.7.9 with linux-firmware
> 20240220
> However, if I run this script (may take 2-3 runs sometimes) it will work:
>
> $ cat reset_bluetooth.sh
> modprobe -r btusb
> modprobe -r btintel
> sleep 2
> modprobe btintel
> modprobe btusb
> sleep 1
> systemctl restart bluetooth
Thanks for the script, it actually works after a couple of tries as you say,
really great.
I wonder, how did you enable these extra debug messages in journalctl? For
example, in mine it doesn't say anything about which firmware files it tries to
load.
I was trying to identify what it loads to replace them with some older versions
and see if I can make it work that way.
I also want to confirm again that the issue is still present in kernel 6.8.1
with the latest firmware update: 20240312
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (8 preceding siblings ...)
2024-03-25 9:38 ` bugzilla-daemon
@ 2024-03-29 8:52 ` bugzilla-daemon
2024-03-29 16:16 ` bugzilla-daemon
` (26 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-03-29 8:52 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Olivier Delierre (contact@odelierre.fr) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |contact@odelierre.fr
--- Comment #9 from Olivier Delierre (contact@odelierre.fr) ---
Had the same issue. Somehow, after a long power-off and turning on again,
Bluetooth managed to show up and the message was gone. Using an AX200 as well.
Currently using kernel 6.8.2
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (9 preceding siblings ...)
2024-03-29 8:52 ` bugzilla-daemon
@ 2024-03-29 16:16 ` bugzilla-daemon
2024-03-29 18:31 ` bugzilla-daemon
` (25 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-03-29 16:16 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #10 from Gurenko Alex (agurenko@protonmail.com) ---
(In reply to Olivier Delierre from comment #9)
> Had the same issue. Somehow, after a long power-off and turning on again,
> Bluetooth managed to show up and the message was gone. Using an AX200 as
> well.
>
> Currently using kernel 6.8.2
Wow, indeed, after upgrade powered off my desktop, flipped the PSU switch for a
few minutes and it worked on boot. This is very weird behavior.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (10 preceding siblings ...)
2024-03-29 16:16 ` bugzilla-daemon
@ 2024-03-29 18:31 ` bugzilla-daemon
2024-03-29 18:33 ` bugzilla-daemon
` (24 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-03-29 18:31 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #11 from Dustin (dustin@falgout.us) ---
(In reply to Gurenko Alex from comment #10)
> (In reply to Olivier Delierre from comment #9)
> > Had the same issue. Somehow, after a long power-off and turning on again,
> > Bluetooth managed to show up and the message was gone. Using an AX200 as
> > well.
> >
> > Currently using kernel 6.8.2
>
> Wow, indeed, after upgrade powered off my desktop, flipped the PSU switch
> for a few minutes and it worked on boot. This is very weird behavior.
Sadly, its short lived. Mine stopped working again after the first resume from
suspend that occurred after the cold boot.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (11 preceding siblings ...)
2024-03-29 18:31 ` bugzilla-daemon
@ 2024-03-29 18:33 ` bugzilla-daemon
2024-03-29 20:02 ` bugzilla-daemon
` (23 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-03-29 18:33 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #12 from Gurenko Alex (agurenko@protonmail.com) ---
(In reply to Dustin from comment #11)
> (In reply to Gurenko Alex from comment #10)
> > (In reply to Olivier Delierre from comment #9)
> > > Had the same issue. Somehow, after a long power-off and turning on again,
> > > Bluetooth managed to show up and the message was gone. Using an AX200 as
> > > well.
> > >
> > > Currently using kernel 6.8.2
> >
> > Wow, indeed, after upgrade powered off my desktop, flipped the PSU switch
> > for a few minutes and it worked on boot. This is very weird behavior.
>
> Sadly, its short lived. Mine stopped working again after the first resume
> from suspend that occurred after the cold boot.
Yes, same here, after normal reboot or shutdown (assuming it happens, because
it also hangs on shutdown/reboot now), it **only** works after PSU power cycle
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (12 preceding siblings ...)
2024-03-29 18:33 ` bugzilla-daemon
@ 2024-03-29 20:02 ` bugzilla-daemon
2024-03-30 13:44 ` bugzilla-daemon
` (22 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-03-29 20:02 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Gabriel (gabrielreisvelloso@proton.me) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gabrielreisvelloso@proton.m
| |e
--- Comment #13 from Gabriel (gabrielreisvelloso@proton.me) ---
(In reply to Gurenko Alex from comment #12)
> (In reply to Dustin from comment #11)
> > (In reply to Gurenko Alex from comment #10)
> > > (In reply to Olivier Delierre from comment #9)
> > > > Had the same issue. Somehow, after a long power-off and turning on
> again,
> > > > Bluetooth managed to show up and the message was gone. Using an AX200
> as
> > > > well.
> > > >
> > > > Currently using kernel 6.8.2
> > >
> > > Wow, indeed, after upgrade powered off my desktop, flipped the PSU switch
> > > for a few minutes and it worked on boot. This is very weird behavior.
> >
> > Sadly, its short lived. Mine stopped working again after the first resume
> > from suspend that occurred after the cold boot.
>
> Yes, same here, after normal reboot or shutdown (assuming it happens,
> because it also hangs on shutdown/reboot now), it **only** works after PSU
> power cycle
Can confirm here, did the test and only work with complete PSU power cycle.
Turn of, waited few seconds and then power on again.
Have a Intel AX200 chip and Linux archlinux 6.8.2-arch2-1 #1 SMP
PREEMPT_DYNAMIC Thu, 28 Mar 2024 17:06:35 +0000 x86_64 GNU/Linux
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (13 preceding siblings ...)
2024-03-29 20:02 ` bugzilla-daemon
@ 2024-03-30 13:44 ` bugzilla-daemon
2024-04-03 12:32 ` bugzilla-daemon
` (21 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-03-30 13:44 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Jugoslav Gacas (jugoslav.gacas@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jugoslav.gacas@gmail.com
--- Comment #14 from Jugoslav Gacas (jugoslav.gacas@gmail.com) ---
I can also confirm the issue. I tried using latest kernel 6.8.2.arch2-1 on arch
linux, and also LTS version 6.6.23-1 and on both I see same behavior.
$ lsusb | grep -i bluetooth
Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth
The behavior is exactly the same as other described.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (14 preceding siblings ...)
2024-03-30 13:44 ` bugzilla-daemon
@ 2024-04-03 12:32 ` bugzilla-daemon
2024-04-03 18:28 ` bugzilla-daemon
` (20 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-03 12:32 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Thomas Creutz (thomas.creutz@gmx.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thomas.creutz@gmx.de
--- Comment #15 from Thomas Creutz (thomas.creutz@gmx.de) ---
I also get:
~$ dmesg | grep -i blue
[ 13.838221] Bluetooth: Core ver 2.22
[ 13.838236] NET: Registered PF_BLUETOOTH protocol family
[ 13.838237] Bluetooth: HCI device and connection manager initialized
[ 13.838240] Bluetooth: HCI socket layer initialized
[ 13.838241] Bluetooth: L2CAP socket layer initialized
[ 13.838244] Bluetooth: SCO socket layer initialized
[ 14.329584] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.329588] Bluetooth: BNEP filters: protocol multicast
[ 14.329590] Bluetooth: BNEP socket layer initialized
[ 16.032582] Bluetooth: hci0: Reading Intel version command failed (-110)
[ 16.032583] Bluetooth: hci0: command 0xfc05 tx timeout
~$ modinfo btintel
filename:
/lib/modules/6.5.0-26-generic/kernel/drivers/bluetooth/btintel.ko
firmware: intel/ibt-12-16.ddc
firmware: intel/ibt-12-16.sfi
firmware: intel/ibt-11-5.ddc
firmware: intel/ibt-11-5.sfi
license: GPL
version: 0.1
description: Bluetooth support for Intel devices ver 0.1
author: Marcel Holtmann <marcel@holtmann.org>
srcversion: FDF2221B8ED4B01F8EADF85
depends: bluetooth
retpoline: Y
intree: Y
name: btintel
vermagic: 6.5.0-26-generic SMP preempt mod_unload modversions
~$ lsusb | grep -i bluetooth
Bus 001 Device 005: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (15 preceding siblings ...)
2024-04-03 12:32 ` bugzilla-daemon
@ 2024-04-03 18:28 ` bugzilla-daemon
2024-04-04 22:50 ` bugzilla-daemon
` (19 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-03 18:28 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Luiz Von Dentz (luiz.dentz@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luiz.dentz@gmail.com
--- Comment #16 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
Can you guys try with the following change:
https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201-1-luiz.dentz@gmail.com/
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (16 preceding siblings ...)
2024-04-03 18:28 ` bugzilla-daemon
@ 2024-04-04 22:50 ` bugzilla-daemon
2024-04-09 12:18 ` bugzilla-daemon
` (18 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-04 22:50 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Robert Holt (robert@robertholt.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |robert@robertholt.net
--- Comment #17 from Robert Holt (robert@robertholt.net) ---
(In reply to Luiz Von Dentz from comment #16)
> Can you guys try with the following change:
>
> https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201-
> 1-luiz.dentz@gmail.com/
I have the same issue and applied this patch to my kernel, but it seems to have
broken the btintel module. I get a null pointer deref on boot and bluetooth is
broken:
[ 2.317366] BUG: kernel NULL pointer dereference, address: 0000000000000070
[ 2.317699] #PF: supervisor read access in kernel mode
[ 2.317993] #PF: error_code(0x0000) - not-present page
[ 2.318280] PGD 0 P4D 0
[ 2.318283] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 2.318842] CPU: 3 PID: 185 Comm: kworker/u33:0 Not tainted
6.8.3-gentoo-dist #1
[ 2.318844] Hardware name: AZW SER/SER, BIOS SER7PRO_P5C8V30 09/15/2023
[ 2.318845] Workqueue: hci0 hci_alloc_dev_priv [bluetooth]
[ 2.319426] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel]
[ 2.320365] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06
00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70
0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44
[ 2.320691] RSP: 0018:ffffa215005cfd48 EFLAGS: 00010202
[ 2.321452] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
0000000080200006
[ 2.321760] RDX: 0000000080200007 RSI: ffffd3238404d700 RDI:
0000000000000000
[ 2.322437] RBP: ffff91a940ccc6c8 R08: 0000000080200007 R09:
0000000080200006
[ 2.322438] R10: 0000000000000001 R11: 0000000000000000 R12:
ffff91a940ccc6d0
[ 2.322439] R13: ffff91a947f50c00 R14: ffff91a940ccc000 R15:
ffff91a940ccca88
[ 2.322441] FS: 0000000000000000(0000) GS:ffff91af820c0000(0000)
knlGS:0000000000000000
[ 2.323737] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.323739] CR2: 0000000000000070 CR3: 000000010dfa2000 CR4:
0000000000f50ef0
[ 2.323740] PKRU: 55555554
[ 2.323740] Call Trace:
[ 2.323743] <TASK>
[ 2.326248] ? __die_body+0x68/0xb0
[ 2.326253] ? page_fault_oops+0x3a3/0x400
[ 2.326256] ? exc_page_fault+0x60/0xf0
[ 2.326265] ? asm_exc_page_fault+0x26/0x30
[ 2.326269] ? btintel_configure_setup+0x245/0x970 [btintel]
[ 2.328091] ? btintel_configure_setup+0x16c/0x970 [btintel]
[ 2.328093] ? __ia32_compat_sys_sysinfo+0x230/0x270
[ 2.329006] hci_dev_open_sync+0x166/0x1610 [bluetooth]
[ 2.329013] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329015] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329016] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329018] hci_alloc_dev_priv+0x164e/0x1bc0 [bluetooth]
[ 2.329023] process_scheduled_works+0x24b/0x450
[ 2.329026] worker_thread+0x2c3/0x420
[ 2.329028] ? __pfx_worker_thread+0x10/0x10
[ 2.329030] kthread+0xe8/0x110
[ 2.329032] ? __pfx_kthread+0x10/0x10
[ 2.329033] ret_from_fork+0x37/0x50
[ 2.329036] ? __pfx_kthread+0x10/0x10
[ 2.329038] ret_from_fork_asm+0x1b/0x30
[ 2.329043] </TASK>
[ 2.329043] Modules linked in: amdxcp(+) ac97_bus(+) iwlwifi(+)
snd_hda_codec(+) btusb snd_pcm_dmaengine gpu_sched vfat btbcm snd_pci_ps
drm_suballoc_helper btintel i2c_algo_bit fat snd_rpl_pci_acp6x kvm(+)
drm_ttm_helper snd_hda_core snd_acp_pci btrtl ttm snd_acp_legacy_common btmtk
snd_pci_acp6x irqbypass drm_exec snd_hwdep snd_pci_acp5x snd_pcm
drm_display_helper bluetooth snd_rn_pci_acp3x wmi_bmof cfg80211 snd_timer
snd_acp_config rapl cec snd_soc_acpi snd pcspkr drm_buddy soundcore i2c_piix4
k10temp snd_pci_acp3x rfkill amd_pmc fuse loop nfnetlink crct10dif_pclmul
crc32_pclmul crc32c_intel nvme polyval_clmulni polyval_generic
ghash_clmulni_intel thunderbolt sha512_ssse3 sha256_ssse3 sha1_ssse3 nvme_core
amd_sfh ccp sp5100_tco r8169 nvme_auth realtek video wmi i2c_hid_acpi i2c_hid
serio_raw
[ 2.329083] CR2: 0000000000000070
[ 2.329085] ---[ end trace 0000000000000000 ]---
[ 2.329087] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel]
[ 2.329089] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06
00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70
0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44
[ 2.329090] RSP: 0018:ffffa215005cfd48 EFLAGS: 00010202
[ 2.329091] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
0000000080200006
[ 2.329092] RDX: 0000000080200007 RSI: ffffd3238404d700 RDI:
0000000000000000
[ 2.329093] RBP: ffff91a940ccc6c8 R08: 0000000080200007 R09:
0000000080200006
[ 2.329093] R10: 0000000000000001 R11: 0000000000000000 R12:
ffff91a940ccc6d0
[ 2.329094] R13: ffff91a947f50c00 R14: ffff91a940ccc000 R15:
ffff91a940ccca88
[ 2.329095] FS: 0000000000000000(0000) GS:ffff91af820c0000(0000)
knlGS:0000000000000000
[ 2.329096] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.329096] CR2: 0000000000000070 CR3: 000000010dfa2000 CR4:
0000000000f50ef0
[ 2.329097] PKRU: 55555554
[ 2.329098] note: kworker/u33:0[185] exited with irqs disabled
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (17 preceding siblings ...)
2024-04-04 22:50 ` bugzilla-daemon
@ 2024-04-09 12:18 ` bugzilla-daemon
2024-04-09 13:04 ` bugzilla-daemon
` (17 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-09 12:18 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #18 from Jugoslav Gacas (jugoslav.gacas@gmail.com) ---
The issue has been fixed for me after upgrading to kernel 6.8.4-arch1-1 on
Arch-linux.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (18 preceding siblings ...)
2024-04-09 12:18 ` bugzilla-daemon
@ 2024-04-09 13:04 ` bugzilla-daemon
2024-04-09 13:45 ` bugzilla-daemon
` (16 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-09 13:04 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #19 from Olivier Delierre (contact@odelierre.fr) ---
(In reply to Jugoslav Gacas from comment #18)
> The issue has been fixed for me after upgrading to kernel 6.8.4-arch1-1 on
> Arch-linux.
Can confirm. Upgraded kernel to 6.8.4-arch1-1, removed btusb from the module
loading blacklist, powered-off the PC and powering it on again, bluetooth was
working.
Tried several things such as rebooting, rebooting on my Windows drive,
rebooting to Archlinux again, powering-off: no power-off hanging, and bluetooth
was working immediately after each start-up, without having to deal with
modprobe anyhow.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (19 preceding siblings ...)
2024-04-09 13:04 ` bugzilla-daemon
@ 2024-04-09 13:45 ` bugzilla-daemon
2024-04-09 13:46 ` bugzilla-daemon
` (15 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-09 13:45 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #20 from Nickolas Gupton (nickolas@gupton.xyz) ---
I am on kernel 6.8.4 and using firmware 20242312, but Bluetooth is still not
working for me:
$ uname -a
Linux andromeda 6.8.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 05 Apr 2024 00:14:23
+0000 x86_64 GNU/Linux
$ journalctl -b | grep -E -i bluetooth
Apr 09 07:01:20 andromeda kernel: Bluetooth: Core ver 2.22
Apr 09 07:01:20 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 09 07:01:20 andromeda kernel: Bluetooth: HCI device and connection manager
initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: HCI socket layer initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: SCO socket layer initialized
Apr 09 07:01:21 andromeda systemd[1]: Reached target Bluetooth Support.
Apr 09 07:01:21 andromeda NetworkManager[794]: <info> [1712664081.1498] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
Apr 09 07:01:23 andromeda kernel: Bluetooth: hci0: Reading Intel version
command failed (-110)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (20 preceding siblings ...)
2024-04-09 13:45 ` bugzilla-daemon
@ 2024-04-09 13:46 ` bugzilla-daemon
2024-04-09 14:31 ` bugzilla-daemon
` (14 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-09 13:46 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #21 from Nickolas Gupton (nickolas@gupton.xyz) ---
Sorry, a typo in my last comment, firmware 20240312 is what I meant.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (21 preceding siblings ...)
2024-04-09 13:46 ` bugzilla-daemon
@ 2024-04-09 14:31 ` bugzilla-daemon
2024-04-09 15:12 ` bugzilla-daemon
` (13 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-09 14:31 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #22 from Gurenko Alex (agurenko@protonmail.com) ---
(In reply to Nickolas Gupton from comment #21)
> Sorry, a typo in my last comment, firmware 20240312 is what I meant.
make sure you do full "power on - power off - power on" cycle **with fixed
kernel**, it's known that warm boot or older kernel somewhere in this cycle
prevent Bluetooth to recover.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (22 preceding siblings ...)
2024-04-09 14:31 ` bugzilla-daemon
@ 2024-04-09 15:12 ` bugzilla-daemon
2024-04-09 19:57 ` bugzilla-daemon
` (12 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-09 15:12 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #23 from Nickolas Gupton (nickolas@gupton.xyz) ---
Yeah, I turn my PC off every night. Have turned it on from a cold power off
every morning for the last year or so this hasn't been working. That doesn't
help at all, the only thing that works to get Bluetooth working after boot is
running the script I showed in a previous comment.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (23 preceding siblings ...)
2024-04-09 15:12 ` bugzilla-daemon
@ 2024-04-09 19:57 ` bugzilla-daemon
2024-05-23 14:54 ` bugzilla-daemon
` (11 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-04-09 19:57 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Warren Turkal (wt@penguintechs.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wt@penguintechs.org
--- Comment #24 from Warren Turkal (wt@penguintechs.org) ---
Does this have any relation to the message I am seeing in the journal logs
after warm boot? Namely this:
Bluetooth: hci0: command 0xfc00 tx timeout
I can confirm that I still get this message on a mainline kernel build.
I have started a thread on linux-bluetooth with the subject "QCA6390 bluetooth
doesn't work after warm boot or disable/reenable" if that helps.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (24 preceding siblings ...)
2024-04-09 19:57 ` bugzilla-daemon
@ 2024-05-23 14:54 ` bugzilla-daemon
2024-05-24 4:17 ` bugzilla-daemon
` (10 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-23 14:54 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #25 from Nickolas Gupton (nickolas@gupton.xyz) ---
kernel: 6.9.1
linux-firmware: 20240510
For me bluetooth still does not work on boot, the timeout error is no longer
shown in the logs but without running that reset script the journal will just
endlessly repeat these messages and the bluetooth will never work. I think the
'fix' that was put in for this simply hid the issue from the logs and wasn't
actually resolved.
$ lsusb | grep -i bluetooth
Bus 001 Device 007: ID 8087:0029 Intel Corp. AX200 Bluetooth
$ journalctl --since 2024-05-22 | grep -E -i bluetooth
May 23 07:21:03 andromeda kernel: Bluetooth: Core ver 2.22
May 23 07:21:03 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
May 23 07:21:03 andromeda kernel: Bluetooth: HCI device and connection manager
initialized
May 23 07:21:03 andromeda kernel: Bluetooth: HCI socket layer initialized
May 23 07:21:03 andromeda kernel: Bluetooth: L2CAP socket layer initialized
May 23 07:21:03 andromeda kernel: Bluetooth: SCO socket layer initialized
May 23 07:21:03 andromeda systemd[1]: Reached target Bluetooth Support.
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: Found device firmware:
intel/ibt-20-1-3.sfi
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: Firmware Version: 132-3.24
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: Firmware already loaded
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit
is set, but its usage is not supported.
May 23 07:21:03 andromeda NetworkManager[789]: <info> [1716466863.8963] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
May 23 07:24:04 andromeda kernel: Bluetooth: Core ver 2.22
May 23 07:24:04 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
May 23 07:24:04 andromeda kernel: Bluetooth: HCI device and connection manager
initialized
May 23 07:24:04 andromeda kernel: Bluetooth: HCI socket layer initialized
May 23 07:24:04 andromeda kernel: Bluetooth: L2CAP socket layer initialized
May 23 07:24:04 andromeda kernel: Bluetooth: SCO socket layer initialized
May 23 07:24:04 andromeda systemd[1]: Reached target Bluetooth Support.
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: Found device firmware:
intel/ibt-20-1-3.sfi
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: Firmware Version: 132-3.24
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: Firmware already loaded
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit
is set, but its usage is not supported.
May 23 07:24:05 andromeda NetworkManager[779]: <info> [1716467045.0155] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
May 23 07:28:33 andromeda kernel: Bluetooth: Core ver 2.22
May 23 07:28:33 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
May 23 07:28:33 andromeda kernel: Bluetooth: HCI device and connection manager
initialized
May 23 07:28:33 andromeda kernel: Bluetooth: HCI socket layer initialized
May 23 07:28:33 andromeda kernel: Bluetooth: L2CAP socket layer initialized
May 23 07:28:33 andromeda kernel: Bluetooth: SCO socket layer initialized
May 23 07:28:33 andromeda systemd[1]: Reached target Bluetooth Support.
May 23 07:28:33 andromeda kernel: Bluetooth: hci0: Found device firmware:
intel/ibt-20-1-3.sfi
May 23 07:28:33 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
May 23 07:28:33 andromeda kernel: Bluetooth: hci0: Firmware Version: 132-3.24
May 23 07:28:33 andromeda kernel: Bluetooth: hci0: Firmware already loaded
May 23 07:28:33 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit
is set, but its usage is not supported.
May 23 07:28:33 andromeda NetworkManager[779]: <info> [1716467313.7052] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (25 preceding siblings ...)
2024-05-23 14:54 ` bugzilla-daemon
@ 2024-05-24 4:17 ` bugzilla-daemon
2024-05-24 15:29 ` bugzilla-daemon
` (9 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-24 4:17 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmenzel+bugzilla.kernel.org
| |@molgen.mpg.de
--- Comment #26 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
@nickolas, from your bug description it’s unclear, if this is a regression, or
if Bluetooth never worked for you. Could you please clarify?
Please attach the output of `dmesg`.
Also, please run `bluetoothctl` and share all the output.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (26 preceding siblings ...)
2024-05-24 4:17 ` bugzilla-daemon
@ 2024-05-24 15:29 ` bugzilla-daemon
2024-05-24 20:41 ` bugzilla-daemon
` (8 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-24 15:29 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #27 from Dustin (dustin@falgout.us) ---
This is a regression. It has been broken since 6.5. It worked fine in prior
kernel versions.
dmesg:
```
[88870.532674] iwlwifi 0000:0f:00.0: WRT: Invalid buffer destination
[88870.672880] iwlwifi 0000:0f:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[88870.672897] iwlwifi 0000:0f:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[88870.672910] iwlwifi 0000:0f:00.0: WFPM_AUTH_KEY_0: 0x90
[88870.672921] iwlwifi 0000:0f:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[88870.698472] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[88870.698512] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[88871.304617] audit: type=1400 audit(1716388650.420:36): apparmor="DENIED"
operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=130211
comm="cupsd" capability=12 capname="net_admin"
[88871.626870] usb 3-1.1: new full-speed USB device number 9 using xhci_hcd
[88871.805974] usb 3-1.1: New USB device found, idVendor=18d1, idProduct=9470,
bcdDevice= 0.01
[88871.805977] usb 3-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[88871.805979] usb 3-1.1: Product: Titan Security Key v2
[88871.805980] usb 3-1.1: Manufacturer: Google
[88871.805981] usb 3-1.1: SerialNumber: 2
[88871.895114] hid-generic 0003:18D1:9470.000C: hiddev3,hidraw5: USB HID v1.11
Device [Google Titan Security Key v2] on usb-0000:13:00.3-1.1/input0
[88873.707802] wlp15s0: authenticate with 68:7f:f0:00:75:00
[88873.711729] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[88873.758100] wlp15s0: authenticate with 68:7f:f0:00:75:00
[88873.758108] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[88873.759975] wlp15s0: authenticated
[88873.762841] wlp15s0: associate with 68:7f:f0:00:75:00 (try 1/3)
[88873.767689] wlp15s0: RX AssocResp from 68:7f:f0:00:75:00 (capab=0x1011
status=0 aid=29)
[88873.772354] wlp15s0: associated
[88873.839960] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by
68:7f:f0:00:75:00
[90310.593408] Bluetooth: hci0: Hardware error 0x0c
[90310.622241] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[90810.448474] wlp15s0: disconnect from AP 68:7f:f0:00:75:00 for new auth to
68:7f:f0:00:74:ff
[90810.556380] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[90810.559334] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[90810.604710] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[90810.604716] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[90810.606524] wlp15s0: authenticated
[90810.607829] wlp15s0: associate with 68:7f:f0:00:74:ff (try 1/3)
[90810.612780] wlp15s0: RX ReassocResp from 68:7f:f0:00:74:ff (capab=0x1011
status=0 aid=31)
[90810.618033] wlp15s0: associated
[90810.799009] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by
68:7f:f0:00:74:ff
[91268.883979] wlp15s0: disconnect from AP 68:7f:f0:00:74:ff for new auth to
68:7f:f0:00:75:00
[91268.957741] wlp15s0: authenticate with 68:7f:f0:00:75:00
[91268.960512] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[91269.000877] wlp15s0: authenticated
[91269.003228] wlp15s0: associate with 68:7f:f0:00:75:00 (try 1/3)
[91269.017600] wlp15s0: RX ReassocResp from 68:7f:f0:00:75:00 (capab=0x1011
status=0 aid=20)
[91269.022231] wlp15s0: associated
[91269.028341] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by
68:7f:f0:00:75:00
[91546.454078] Bluetooth: hci0: Hardware error 0x0c
[91546.482974] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[93125.536286] Bluetooth: hci0: Hardware error 0x0c
[93125.565113] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[93450.737090] Bluetooth: hci0: Hardware error 0x0c
[93450.765934] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[93817.574022] Bluetooth: hci0: Hardware error 0x0c
[93817.602865] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[94390.961485] Bluetooth: hci0: Hardware error 0x0c
[94390.990308] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[95249.775745] input: Aeropex by AfterShokz (AVRCP) as
/devices/virtual/input/input17
[95652.176339] usb 2-4.1: current rate 16000 is different from the runtime rate
48000
[95893.488409] Bluetooth: hci0: Hardware error 0x0c
[95893.517269] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[95927.828934] input: Aeropex by AfterShokz (AVRCP) as
/devices/virtual/input/input18
[97938.322407] Bluetooth: hci0: Hardware error 0x0c
[97938.351273] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[97961.145815] input: Aeropex by AfterShokz (AVRCP) as
/devices/virtual/input/input19
[98398.282029] Bluetooth: hci0: Hardware error 0x0c
[98398.310866] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[100767.745384] Bluetooth: hci0: Hardware error 0x0c
[100767.774181] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[103333.287732] Bluetooth: hci0: Hardware error 0x0c
[103333.316590] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[103341.411753] Bluetooth: hci0: Hardware error 0x0c
[103341.440606] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[105266.379714] Bluetooth: hci0: Hardware error 0x0c
[105266.408621] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[106003.531592] Bluetooth: hci0: Hardware error 0x0c
[106003.560438] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[108346.230495] Bluetooth: hci0: Hardware error 0x0c
[108346.259336] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[108791.417617] Bluetooth: hci0: Hardware error 0x0c
[108791.446455] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[109008.534180] Bluetooth: hci0: Hardware error 0x0c
[109008.563027] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[111617.526748] Bluetooth: hci0: Hardware error 0x0c
[111617.555598] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[115482.826860] Bluetooth: hci0: Hardware error 0x0c
[115482.855717] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[115807.771740] Bluetooth: hci0: Hardware error 0x0c
[115807.800569] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[116491.387487] Bluetooth: hci0: Hardware error 0x0c
[116491.416328] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[116721.221113] Bluetooth: hci0: Hardware error 0x0c
[116721.249968] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[116833.759399] Bluetooth: hci0: Hardware error 0x0c
[116833.788235] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[117123.023176] Bluetooth: hci0: Hardware error 0x0c
[117123.052009] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[117726.380781] Bluetooth: hci0: Hardware error 0x0c
[117726.409617] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[118301.374381] Bluetooth: hci0: Hardware error 0x0c
[118301.403203] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[119143.135347] wlp15s0: deauthenticating from 68:7f:f0:00:75:00 by local
choice (Reason: 3=DEAUTH_LEAVING)
[119143.549669] PM: suspend entry (deep)
[119144.066184] Filesystems sync: 0.516 seconds
[119144.089948] Freezing user space processes
[119144.099250] Freezing user space processes completed (elapsed 0.009 seconds)
[119144.099254] OOM killer disabled.
[119144.099255] Freezing remaining freezable tasks
[119144.100571] Freezing remaining freezable tasks completed (elapsed 0.001
seconds)
[119144.100598] printk: Suspending console(s) (use no_console_suspend to debug)
[119144.101774] serial 00:04: disabled
[119144.149312] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[119144.149356] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[119144.150213] ata3.00: Entering standby power mode
[119144.150236] ata1.00: Entering standby power mode
[119144.615240] amdgpu 0000:03:00.0: amdgpu: MODE1 reset
[119144.615243] amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
[119144.615304] amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
[119145.189337] ACPI: PM: Preparing to enter system sleep state S3
[119145.529246] ACPI: PM: Saving platform NVS memory
[119145.529715] Disabling non-boot CPUs ...
[119145.532010] smpboot: CPU 1 is now offline
[119145.536461] smpboot: CPU 2 is now offline
[119145.539443] smpboot: CPU 3 is now offline
[119145.542236] smpboot: CPU 4 is now offline
[119145.544993] smpboot: CPU 5 is now offline
[119145.547300] smpboot: CPU 6 is now offline
[119145.551071] smpboot: CPU 7 is now offline
[119145.554737] smpboot: CPU 8 is now offline
[119145.558306] smpboot: CPU 9 is now offline
[119145.561958] smpboot: CPU 10 is now offline
[119145.565455] smpboot: CPU 11 is now offline
[119145.569175] smpboot: CPU 12 is now offline
[119145.570975] Spectre V2 : Update user space SMT mitigation: STIBP off
[119145.572533] smpboot: CPU 13 is now offline
[119145.575845] smpboot: CPU 14 is now offline
[119145.578904] smpboot: CPU 15 is now offline
[119145.582013] smpboot: CPU 16 is now offline
[119145.585216] smpboot: CPU 17 is now offline
[119145.588294] smpboot: CPU 18 is now offline
[119145.590955] smpboot: CPU 19 is now offline
[119145.593465] smpboot: CPU 20 is now offline
[119145.595730] smpboot: CPU 21 is now offline
[119145.598272] smpboot: CPU 22 is now offline
[119145.600594] smpboot: CPU 23 is now offline
[119145.601765] ACPI: PM: Low-level resume complete
[119145.601787] ACPI: PM: Restoring platform NVS memory
[119145.630414] AMD-Vi: Virtual APIC enabled
[119145.630574] AMD-Vi: Virtual APIC enabled
[119145.630585] LVT offset 0 assigned for vector 0x400
[119145.631173] Enabling non-boot CPUs ...
[119145.631198] smpboot: Booting Node 0 Processor 1 APIC 0x2
[119145.633770] ACPI: \_SB_.PLTF.C002: Found 3 idle states
[119145.634090] CPU1 is up
[119145.634102] smpboot: Booting Node 0 Processor 2 APIC 0x4
[119145.636428] ACPI: \_SB_.PLTF.C004: Found 3 idle states
[119145.636625] CPU2 is up
[119145.636648] smpboot: Booting Node 0 Processor 3 APIC 0x6
[119145.638966] ACPI: \_SB_.PLTF.C006: Found 3 idle states
[119145.639158] CPU3 is up
[119145.639171] smpboot: Booting Node 0 Processor 4 APIC 0x8
[119145.641484] ACPI: \_SB_.PLTF.C008: Found 3 idle states
[119145.641689] CPU4 is up
[119145.641709] smpboot: Booting Node 0 Processor 5 APIC 0xa
[119145.644017] ACPI: \_SB_.PLTF.C00A: Found 3 idle states
[119145.644235] CPU5 is up
[119145.644254] smpboot: Booting Node 0 Processor 6 APIC 0x10
[119145.646628] ACPI: \_SB_.PLTF.C00C: Found 3 idle states
[119145.646946] CPU6 is up
[119145.646967] smpboot: Booting Node 0 Processor 7 APIC 0x12
[119145.649324] ACPI: \_SB_.PLTF.C00E: Found 3 idle states
[119145.649568] CPU7 is up
[119145.649589] smpboot: Booting Node 0 Processor 8 APIC 0x14
[119145.651937] ACPI: \_SB_.PLTF.C010: Found 3 idle states
[119145.652209] CPU8 is up
[119145.652226] smpboot: Booting Node 0 Processor 9 APIC 0x16
[119145.654582] ACPI: \_SB_.PLTF.C012: Found 3 idle states
[119145.654863] CPU9 is up
[119145.654884] smpboot: Booting Node 0 Processor 10 APIC 0x18
[119145.657233] ACPI: \_SB_.PLTF.C014: Found 3 idle states
[119145.657528] CPU10 is up
[119145.657547] smpboot: Booting Node 0 Processor 11 APIC 0x1a
[119145.659894] ACPI: \_SB_.PLTF.C016: Found 3 idle states
[119145.660183] CPU11 is up
[119145.660199] smpboot: Booting Node 0 Processor 12 APIC 0x1
[119145.662502] ACPI: \_SB_.PLTF.C001: Found 3 idle states
[119145.662923] Spectre V2 : Update user space SMT mitigation: STIBP always-on
[119145.662927] CPU12 is up
[119145.662942] smpboot: Booting Node 0 Processor 13 APIC 0x3
[119145.665076] Spurious APIC interrupt (vector 0xFF) on CPU#13, should never
happen.
[119145.665275] ACPI: \_SB_.PLTF.C003: Found 3 idle states
[119145.665594] CPU13 is up
[119145.665610] smpboot: Booting Node 0 Processor 14 APIC 0x5
[119145.667726] Spurious APIC interrupt (vector 0xFF) on CPU#14, should never
happen.
[119145.667926] ACPI: \_SB_.PLTF.C005: Found 3 idle states
[119145.668248] CPU14 is up
[119145.668262] smpboot: Booting Node 0 Processor 15 APIC 0x7
[119145.670377] Spurious APIC interrupt (vector 0xFF) on CPU#15, should never
happen.
[119145.670591] ACPI: \_SB_.PLTF.C007: Found 3 idle states
[119145.670912] CPU15 is up
[119145.670928] smpboot: Booting Node 0 Processor 16 APIC 0x9
[119145.673047] Spurious APIC interrupt (vector 0xFF) on CPU#16, should never
happen.
[119145.673256] ACPI: \_SB_.PLTF.C009: Found 3 idle states
[119145.673609] CPU16 is up
[119145.673626] smpboot: Booting Node 0 Processor 17 APIC 0xb
[119145.675748] Spurious APIC interrupt (vector 0xFF) on CPU#17, should never
happen.
[119145.675955] ACPI: \_SB_.PLTF.C00B: Found 3 idle states
[119145.676322] CPU17 is up
[119145.676342] smpboot: Booting Node 0 Processor 18 APIC 0x11
[119145.678477] Spurious APIC interrupt (vector 0xFF) on CPU#18, should never
happen.
[119145.678695] ACPI: \_SB_.PLTF.C00D: Found 3 idle states
[119145.679121] CPU18 is up
[119145.679137] smpboot: Booting Node 0 Processor 19 APIC 0x13
[119145.681251] Spurious APIC interrupt (vector 0xFF) on CPU#19, should never
happen.
[119145.681463] ACPI: \_SB_.PLTF.C00F: Found 3 idle states
[119145.681849] CPU19 is up
[119145.681870] smpboot: Booting Node 0 Processor 20 APIC 0x15
[119145.684007] Spurious APIC interrupt (vector 0xFF) on CPU#20, should never
happen.
[119145.684232] ACPI: \_SB_.PLTF.C011: Found 3 idle states
[119145.684652] CPU20 is up
[119145.684674] smpboot: Booting Node 0 Processor 21 APIC 0x17
[119145.686813] Spurious APIC interrupt (vector 0xFF) on CPU#21, should never
happen.
[119145.687038] ACPI: \_SB_.PLTF.C013: Found 3 idle states
[119145.687476] CPU21 is up
[119145.687490] smpboot: Booting Node 0 Processor 22 APIC 0x19
[119145.689612] Spurious APIC interrupt (vector 0xFF) on CPU#22, should never
happen.
[119145.689843] ACPI: \_SB_.PLTF.C015: Found 3 idle states
[119145.690322] CPU22 is up
[119145.690344] smpboot: Booting Node 0 Processor 23 APIC 0x1b
[119145.692488] Spurious APIC interrupt (vector 0xFF) on CPU#23, should never
happen.
[119145.692730] ACPI: \_SB_.PLTF.C017: Found 3 idle states
[119145.693200] CPU23 is up
[119145.695865] ACPI: PM: Waking up from system sleep state S3
[119145.990743] [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
[119145.990774] [drm] PSP is resuming...
[119145.991390] [drm] PCIE GART of 512M enabled (table at 0x0000008001300000).
[119145.991430] [drm] PSP is resuming...
[119145.991677] serial 00:04: activated
[119145.992677] xhci_hcd 0000:10:00.0: xHC error in resume, USBSTS 0x401,
Reinit
[119145.992680] usb usb1: root hub lost power or was reset
[119145.992682] usb usb2: root hub lost power or was reset
[119146.012190] [drm] reserve 0xa00000 from 0xf41e000000 for PSP TMR
[119146.019583] nvme nvme1: 24/0/0 default/read/poll queues
[119146.029456] nvme nvme0: 24/0/0 default/read/poll queues
[119146.066897] [drm] reserve 0xa00000 from 0x80fd000000 for PSP TMR
[119146.076594] amdgpu 0000:13:00.0: amdgpu: RAS: optional ras ta ucode is not
available
[119146.082360] amdgpu 0000:13:00.0: amdgpu: RAP: optional rap ta ucode is not
available
[119146.082361] amdgpu 0000:13:00.0: amdgpu: SECUREDISPLAY: securedisplay ta
ucode is not available
[119146.082363] amdgpu 0000:13:00.0: amdgpu: SMU is resuming...
[119146.082365] amdgpu 0000:13:00.0: amdgpu: smu driver if version =
0x00000004, smu fw if version = 0x00000005, smu fw program = 0, smu fw version
= 0x00544fdf (84.79.223)
[119146.082367] amdgpu 0000:13:00.0: amdgpu: SMU driver if version not matched
[119146.084096] amdgpu 0000:13:00.0: amdgpu: SMU is resumed successfully!
[119146.084760] [drm] DMUB hardware initialized: version=0x05000500
[119146.085450] [drm] kiq ring mec 2 pipe 1 q 0
[119146.087448] [drm] VCN decode and encode initialized successfully(under DPG
Mode).
[119146.087488] [drm] JPEG decode initialized successfully.
[119146.087496] amdgpu 0000:13:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0
on hub 0
[119146.087498] amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1
on hub 0
[119146.087499] amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4
on hub 0
[119146.087500] amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5
on hub 0
[119146.087501] amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6
on hub 0
[119146.087501] amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7
on hub 0
[119146.087502] amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8
on hub 0
[119146.087503] amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9
on hub 0
[119146.087504] amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10
on hub 0
[119146.087505] amdgpu 0000:13:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng
11 on hub 0
[119146.087505] amdgpu 0000:13:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on
hub 0
[119146.087506] amdgpu 0000:13:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0
on hub 8
[119146.087507] amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1
on hub 8
[119146.087508] amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4
on hub 8
[119146.087509] amdgpu 0000:13:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on
hub 8
[119146.089772] amdgpu 0000:13:00.0: [drm] Cannot find any crtc or sizes
[119146.157143] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not
available
[119146.171828] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta
ucode is not available
[119146.171831] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
[119146.171833] amdgpu 0000:03:00.0: amdgpu: smu driver if version =
0x0000000d, smu fw if version = 0x0000000f, smu fw program = 0, version =
0x00491a00 (73.26.0)
[119146.171836] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[119146.171864] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
[119146.214380] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
[119146.215442] [drm] DMUB hardware initialized: version=0x0202000C
[119146.305831] ata2: SATA link down (SStatus 0 SControl 300)
[119146.305962] ata4: SATA link down (SStatus 0 SControl 300)
[119146.346523] usb 1-7: reset full-speed USB device number 6 using xhci_hcd
[119146.466520] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[119146.466530] ata1.00: Entering active power mode
[119146.466547] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[119146.466558] ata3.00: Entering active power mode
[119146.468082] ata3.00: configured for UDMA/133
[119146.503427] ata1.00: configured for UDMA/133
[119146.545607] [drm] kiq ring mec 2 pipe 1 q 0
[119146.548940] [drm] VCN decode and encode initialized successfully(under DPG
Mode).
[119146.548957] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0
on hub 0
[119146.548959] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1
on hub 0
[119146.548960] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4
on hub 0
[119146.548961] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5
on hub 0
[119146.548962] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6
on hub 0
[119146.548963] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7
on hub 0
[119146.548963] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8
on hub 0
[119146.548964] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9
on hub 0
[119146.548965] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10
on hub 0
[119146.548966] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng
11 on hub 0
[119146.548967] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on
hub 0
[119146.548968] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0
on hub 8
[119146.775245] usb 1-3: reset full-speed USB device number 3 using xhci_hcd
[119147.199089] usb 1-2: reset full-speed USB device number 2 using xhci_hcd
[119147.554710] usb 1-4: reset high-speed USB device number 4 using xhci_hcd
[119147.846666] usb 1-10: reset high-speed USB device number 7 using xhci_hcd
[119148.258836] usb 1-6: reset full-speed USB device number 5 using xhci_hcd
[119148.624016] usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
[119148.979540] usb 2-4.1: reset SuperSpeed USB device number 3 using xhci_hcd
[119149.011222] OOM killer enabled.
[119149.011224] Restarting tasks ...
[119149.016632] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build
38020
[119149.017229] done.
[119149.017296] random: crng reseeded on system resumption
[119149.017647] thermal thermal_zone1: failed to read out thermal zone (-61)
[119149.017652] PM: suspend exit
[119149.020747] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[119149.020758] Bluetooth: hci0: Boot Address: 0x100800
[119149.020760] Bluetooth: hci0: Firmware Version: 132-5.22
[119149.020761] Bluetooth: hci0: Firmware already loaded
[119149.226337] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-e00:00: attached PHY
driver (mii_bus:phy_addr=r8169-0-e00:00, irq=MAC)
[119149.292012] usb 3-1.1: USB disconnect, device number 9
[119149.305529] Bluetooth: MGMT ver 1.22
[119149.438305] r8169 0000:0e:00.0 enp14s0: Link is Down
[119149.484014] iwlwifi 0000:0f:00.0: WRT: Invalid buffer destination
[119149.624319] iwlwifi 0000:0f:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[119149.624336] iwlwifi 0000:0f:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[119149.624354] iwlwifi 0000:0f:00.0: WFPM_AUTH_KEY_0: 0x90
[119149.624366] iwlwifi 0000:0f:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[119149.662217] usb 3-1.1: new full-speed USB device number 10 using xhci_hcd
[119149.700490] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[119149.700538] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[119149.836781] usb 3-1.1: New USB device found, idVendor=18d1, idProduct=9470,
bcdDevice= 0.01
[119149.836787] usb 3-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[119149.836789] usb 3-1.1: Product: Titan Security Key v2
[119149.836791] usb 3-1.1: Manufacturer: Google
[119149.836792] usb 3-1.1: SerialNumber: 2
[119149.941978] hid-generic 0003:18D1:9470.000D: hiddev3,hidraw5: USB HID v1.11
Device [Google Titan Security Key v2] on usb-0000:13:00.3-1.1/input0
[119150.900516] audit: type=1400 audit(1716477597.264:37): apparmor="DENIED"
operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=169110
comm="cupsd" capability=12 capname="net_admin"
[119152.887950] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[119152.891928] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[119152.936313] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[119152.936317] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[119152.937855] wlp15s0: authenticated
[119152.938178] wlp15s0: associate with 68:7f:f0:00:74:ff (try 1/3)
[119152.943414] wlp15s0: RX AssocResp from 68:7f:f0:00:74:ff (capab=0x1011
status=0 aid=28)
[119152.948744] wlp15s0: associated
[119153.045300] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by
68:7f:f0:00:74:ff
[119969.309895] Bluetooth: hci0: Hardware error 0x0c
[119969.338670] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[120815.442243] Bluetooth: hci0: Hardware error 0x0c
[120815.471087] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[121110.620282] Bluetooth: hci0: Hardware error 0x0c
[121110.649114] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[122110.363149] Bluetooth: hci0: Hardware error 0x0c
[122110.391988] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[122400.714900] Bluetooth: hci0: Hardware error 0x0c
[122400.743744] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[122806.577935] Bluetooth: hci0: Hardware error 0x0c
[122806.606781] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[124135.739119] Bluetooth: hci0: Hardware error 0x0c
[124135.767950] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[125181.467711] Bluetooth: hci0: Hardware error 0x0c
[125181.496541] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[125819.515014] wlp15s0: disconnect from AP 68:7f:f0:00:74:ff for new auth to
68:7f:f0:00:75:00
[125819.570592] wlp15s0: authenticate with 68:7f:f0:00:75:00
[125819.573529] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[125819.618654] wlp15s0: authenticate with 68:7f:f0:00:75:00
[125819.618661] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[125819.620543] wlp15s0: authenticated
[125819.626052] wlp15s0: associate with 68:7f:f0:00:75:00 (try 1/3)
[125819.631590] wlp15s0: RX ReassocResp from 68:7f:f0:00:75:00 (capab=0x1011
status=0 aid=10)
[125819.636089] wlp15s0: associated
[125819.670561] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by
68:7f:f0:00:75:00
[126580.707255] Bluetooth: hci0: Hardware error 0x0c
[126580.736036] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[127985.442812] Bluetooth: hci0: Hardware error 0x0c
[127985.471641] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[129906.556864] Bluetooth: hci0: Hardware error 0x0c
[129906.585694] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[130550.774519] Bluetooth: hci0: Hardware error 0x0c
[130550.803354] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[145852.669134] wlp15s0: deauthenticating from 68:7f:f0:00:75:00 by local
choice (Reason: 3=DEAUTH_LEAVING)
[145853.298960] PM: suspend entry (deep)
[145855.434355] Filesystems sync: 2.135 seconds
[145857.465558] Bluetooth: hci0: Opcode 0x0c1a failed: -110
[145857.465585] Bluetooth: hci0: command 0x0c1a tx timeout
[145859.481635] Bluetooth: hci0: Opcode 0x2042 failed: -110
[145859.481638] Bluetooth: hci0: command 0x2042 tx timeout
[145859.481643] Bluetooth: hci0: Unable to disable scanning: -110
[145861.497574] Bluetooth: hci0: Opcode 0x0c1a failed: -110
[145861.497579] Bluetooth: hci0: command 0x0c1a tx timeout
[145863.513472] Bluetooth: hci0: Opcode 0x2042 failed: -110
[145863.513481] Bluetooth: hci0: Unable to disable scanning: -110
[145863.513484] Bluetooth: hci0: disable scanning failed: -110
[145863.513484] Bluetooth: hci0: command 0x2042 tx timeout
[145863.513486] Bluetooth: hci0: start background scanning failed: -110
[145863.513707] Freezing user space processes
[145863.522766] Freezing user space processes completed (elapsed 0.009 seconds)
[145863.522770] OOM killer disabled.
[145863.522771] Freezing remaining freezable tasks
[145863.524092] Freezing remaining freezable tasks completed (elapsed 0.001
seconds)
[145863.524119] printk: Suspending console(s) (use no_console_suspend to debug)
[145863.525510] serial 00:04: disabled
[145863.557238] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[145863.558159] ata1.00: Entering standby power mode
[145863.561235] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[145863.562027] ata3.00: Entering standby power mode
[145863.972594] amdgpu 0000:03:00.0: amdgpu: MODE1 reset
[145863.972599] amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
[145863.972653] amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
[145864.554852] ACPI: PM: Preparing to enter system sleep state S3
[145864.893739] ACPI: PM: Saving platform NVS memory
[145864.894211] Disabling non-boot CPUs ...
[145864.896611] smpboot: CPU 1 is now offline
[145864.900980] smpboot: CPU 2 is now offline
[145864.903865] smpboot: CPU 3 is now offline
[145864.906648] smpboot: CPU 4 is now offline
[145864.909284] smpboot: CPU 5 is now offline
[145864.911928] smpboot: CPU 6 is now offline
[145864.915532] smpboot: CPU 7 is now offline
[145864.919113] smpboot: CPU 8 is now offline
[145864.922742] smpboot: CPU 9 is now offline
[145864.926414] smpboot: CPU 10 is now offline
[145864.930082] smpboot: CPU 11 is now offline
[145864.933981] smpboot: CPU 12 is now offline
[145864.935615] Spectre V2 : Update user space SMT mitigation: STIBP off
[145864.937295] smpboot: CPU 13 is now offline
[145864.939864] smpboot: CPU 14 is now offline
[145864.942328] smpboot: CPU 15 is now offline
[145864.944797] smpboot: CPU 16 is now offline
[145864.947090] smpboot: CPU 17 is now offline
[145864.949334] smpboot: CPU 18 is now offline
[145864.952490] smpboot: CPU 19 is now offline
[145864.955785] smpboot: CPU 20 is now offline
[145864.959384] smpboot: CPU 21 is now offline
[145864.961876] smpboot: CPU 22 is now offline
[145864.964979] smpboot: CPU 23 is now offline
[145864.966365] ACPI: PM: Low-level resume complete
[145864.966386] ACPI: PM: Restoring platform NVS memory
[145864.998883] AMD-Vi: Virtual APIC enabled
[145865.005071] AMD-Vi: Virtual APIC enabled
[145865.005083] LVT offset 0 assigned for vector 0x400
[145865.005823] Enabling non-boot CPUs ...
[145865.005848] smpboot: Booting Node 0 Processor 1 APIC 0x2
[145865.008419] ACPI: \_SB_.PLTF.C002: Found 3 idle states
[145865.008739] CPU1 is up
[145865.008753] smpboot: Booting Node 0 Processor 2 APIC 0x4
[145865.011064] ACPI: \_SB_.PLTF.C004: Found 3 idle states
[145865.011267] CPU2 is up
[145865.011281] smpboot: Booting Node 0 Processor 3 APIC 0x6
[145865.013588] ACPI: \_SB_.PLTF.C006: Found 3 idle states
[145865.013768] CPU3 is up
[145865.013782] smpboot: Booting Node 0 Processor 4 APIC 0x8
[145865.016088] ACPI: \_SB_.PLTF.C008: Found 3 idle states
[145865.016291] CPU4 is up
[145865.016303] smpboot: Booting Node 0 Processor 5 APIC 0xa
[145865.018607] ACPI: \_SB_.PLTF.C00A: Found 3 idle states
[145865.018817] CPU5 is up
[145865.018831] smpboot: Booting Node 0 Processor 6 APIC 0x10
[145865.021201] ACPI: \_SB_.PLTF.C00C: Found 3 idle states
[145865.021514] CPU6 is up
[145865.021528] smpboot: Booting Node 0 Processor 7 APIC 0x12
[145865.023880] ACPI: \_SB_.PLTF.C00E: Found 3 idle states
[145865.024124] CPU7 is up
[145865.024138] smpboot: Booting Node 0 Processor 8 APIC 0x14
[145865.026481] ACPI: \_SB_.PLTF.C010: Found 3 idle states
[145865.026747] CPU8 is up
[145865.026763] smpboot: Booting Node 0 Processor 9 APIC 0x16
[145865.029113] ACPI: \_SB_.PLTF.C012: Found 3 idle states
[145865.029392] CPU9 is up
[145865.029407] smpboot: Booting Node 0 Processor 10 APIC 0x18
[145865.031744] ACPI: \_SB_.PLTF.C014: Found 3 idle states
[145865.032032] CPU10 is up
[145865.032048] smpboot: Booting Node 0 Processor 11 APIC 0x1a
[145865.034388] ACPI: \_SB_.PLTF.C016: Found 3 idle states
[145865.034671] CPU11 is up
[145865.034687] smpboot: Booting Node 0 Processor 12 APIC 0x1
[145865.037017] ACPI: \_SB_.PLTF.C001: Found 3 idle states
[145865.037422] Spectre V2 : Update user space SMT mitigation: STIBP always-on
[145865.037426] CPU12 is up
[145865.037441] smpboot: Booting Node 0 Processor 13 APIC 0x3
[145865.039554] Spurious APIC interrupt (vector 0xFF) on CPU#13, should never
happen.
[145865.039754] ACPI: \_SB_.PLTF.C003: Found 3 idle states
[145865.040072] CPU13 is up
[145865.040086] smpboot: Booting Node 0 Processor 14 APIC 0x5
[145865.042201] Spurious APIC interrupt (vector 0xFF) on CPU#14, should never
happen.
[145865.042400] ACPI: \_SB_.PLTF.C005: Found 3 idle states
[145865.042721] CPU14 is up
[145865.042734] smpboot: Booting Node 0 Processor 15 APIC 0x7
[145865.044852] Spurious APIC interrupt (vector 0xFF) on CPU#15, should never
happen.
[145865.045054] ACPI: \_SB_.PLTF.C007: Found 3 idle states
[145865.045372] CPU15 is up
[145865.045385] smpboot: Booting Node 0 Processor 16 APIC 0x9
[145865.047482] Spurious APIC interrupt (vector 0xFF) on CPU#16, should never
happen.
[145865.047707] ACPI: \_SB_.PLTF.C009: Found 3 idle states
[145865.048052] CPU16 is up
[145865.048065] smpboot: Booting Node 0 Processor 17 APIC 0xb
[145865.050189] Spurious APIC interrupt (vector 0xFF) on CPU#17, should never
happen.
[145865.050402] ACPI: \_SB_.PLTF.C00B: Found 3 idle states
[145865.050771] CPU17 is up
[145865.050784] smpboot: Booting Node 0 Processor 18 APIC 0x11
[145865.052917] Spurious APIC interrupt (vector 0xFF) on CPU#18, should never
happen.
[145865.053129] ACPI: \_SB_.PLTF.C00D: Found 3 idle states
[145865.053543] CPU18 is up
[145865.053557] smpboot: Booting Node 0 Processor 19 APIC 0x13
[145865.055693] Spurious APIC interrupt (vector 0xFF) on CPU#19, should never
happen.
[145865.055903] ACPI: \_SB_.PLTF.C00F: Found 3 idle states
[145865.056286] CPU19 is up
[145865.056301] smpboot: Booting Node 0 Processor 20 APIC 0x15
[145865.058438] Spurious APIC interrupt (vector 0xFF) on CPU#20, should never
happen.
[145865.058651] ACPI: \_SB_.PLTF.C011: Found 3 idle states
[145865.059076] CPU20 is up
[145865.059091] smpboot: Booting Node 0 Processor 21 APIC 0x17
[145865.061229] Spurious APIC interrupt (vector 0xFF) on CPU#21, should never
happen.
[145865.061455] ACPI: \_SB_.PLTF.C013: Found 3 idle states
[145865.061899] CPU21 is up
[145865.061913] smpboot: Booting Node 0 Processor 22 APIC 0x19
[145865.064057] Spurious APIC interrupt (vector 0xFF) on CPU#22, should never
happen.
[145865.064282] ACPI: \_SB_.PLTF.C015: Found 3 idle states
[145865.064754] CPU22 is up
[145865.064771] smpboot: Booting Node 0 Processor 23 APIC 0x1b
[145865.066918] Spurious APIC interrupt (vector 0xFF) on CPU#23, should never
happen.
[145865.067161] ACPI: \_SB_.PLTF.C017: Found 3 idle states
[145865.067632] CPU23 is up
[145865.070344] ACPI: PM: Waking up from system sleep state S3
[145865.363971] [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
[145865.364016] [drm] PSP is resuming...
[145865.365479] serial 00:04: activated
[145865.367003] xhci_hcd 0000:10:00.0: xHC error in resume, USBSTS 0x401,
Reinit
[145865.367006] usb usb1: root hub lost power or was reset
[145865.367007] usb usb2: root hub lost power or was reset
[145865.367096] [drm] PCIE GART of 512M enabled (table at 0x0000008001300000).
[145865.367114] [drm] PSP is resuming...
[145865.385456] [drm] reserve 0xa00000 from 0xf41e000000 for PSP TMR
[145865.391436] nvme nvme1: 24/0/0 default/read/poll queues
[145865.397935] nvme nvme0: 24/0/0 default/read/poll queues
[145865.442405] [drm] reserve 0xa00000 from 0x80fd000000 for PSP TMR
[145865.450366] amdgpu 0000:13:00.0: amdgpu: RAS: optional ras ta ucode is not
available
[145865.456207] amdgpu 0000:13:00.0: amdgpu: RAP: optional rap ta ucode is not
available
[145865.456208] amdgpu 0000:13:00.0: amdgpu: SECUREDISPLAY: securedisplay ta
ucode is not available
[145865.456210] amdgpu 0000:13:00.0: amdgpu: SMU is resuming...
[145865.456216] amdgpu 0000:13:00.0: amdgpu: smu driver if version =
0x00000004, smu fw if version = 0x00000005, smu fw program = 0, smu fw version
= 0x00544fdf (84.79.223)
[145865.456219] amdgpu 0000:13:00.0: amdgpu: SMU driver if version not matched
[145865.458112] amdgpu 0000:13:00.0: amdgpu: SMU is resumed successfully!
[145865.458772] [drm] DMUB hardware initialized: version=0x05000500
[145865.459969] [drm] kiq ring mec 2 pipe 1 q 0
[145865.462183] [drm] VCN decode and encode initialized successfully(under DPG
Mode).
[145865.462718] [drm] JPEG decode initialized successfully.
[145865.462727] amdgpu 0000:13:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0
on hub 0
[145865.462729] amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1
on hub 0
[145865.462730] amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4
on hub 0
[145865.462731] amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5
on hub 0
[145865.462731] amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6
on hub 0
[145865.462732] amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7
on hub 0
[145865.462733] amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8
on hub 0
[145865.462734] amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9
on hub 0
[145865.462734] amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10
on hub 0
[145865.462735] amdgpu 0000:13:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng
11 on hub 0
[145865.462736] amdgpu 0000:13:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on
hub 0
[145865.462737] amdgpu 0000:13:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0
on hub 8
[145865.462738] amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1
on hub 8
[145865.462739] amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4
on hub 8
[145865.462740] amdgpu 0000:13:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on
hub 8
[145865.466203] amdgpu 0000:13:00.0: [drm] Cannot find any crtc or sizes
[145865.534086] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not
available
[145865.548872] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta
ucode is not available
[145865.548874] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
[145865.548877] amdgpu 0000:03:00.0: amdgpu: smu driver if version =
0x0000000d, smu fw if version = 0x0000000f, smu fw program = 0, version =
0x00491a00 (73.26.0)
[145865.548879] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[145865.548907] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
[145865.590946] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
[145865.592006] [drm] DMUB hardware initialized: version=0x0202000C
[145865.679682] ata4: SATA link down (SStatus 0 SControl 300)
[145865.679797] ata2: SATA link down (SStatus 0 SControl 300)
[145865.732697] usb 1-4: reset high-speed USB device number 4 using xhci_hcd
[145865.840816] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[145865.840823] ata1.00: Entering active power mode
[145865.840833] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[145865.840840] ata3.00: Entering active power mode
[145865.842376] ata3.00: configured for UDMA/133
[145865.877430] ata1.00: configured for UDMA/133
[145865.919559] [drm] kiq ring mec 2 pipe 1 q 0
[145865.922908] [drm] VCN decode and encode initialized successfully(under DPG
Mode).
[145865.922924] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0
on hub 0
[145865.922926] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1
on hub 0
[145865.922927] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4
on hub 0
[145865.922928] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5
on hub 0
[145865.922928] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6
on hub 0
[145865.922929] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7
on hub 0
[145865.922930] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8
on hub 0
[145865.922931] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9
on hub 0
[145865.922932] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10
on hub 0
[145865.922933] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng
11 on hub 0
[145865.922934] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on
hub 0
[145865.922934] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0
on hub 8
[145866.024853] usb 1-10: reset high-speed USB device number 7 using xhci_hcd
[145866.436996] usb 1-7: reset full-speed USB device number 6 using xhci_hcd
[145866.796883] usb 1-6: reset full-speed USB device number 5 using xhci_hcd
[145867.296840] usb 1-3: reset full-speed USB device number 3 using xhci_hcd
[145867.652749] usb 1-2: reset full-speed USB device number 2 using xhci_hcd
[145868.010302] usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
[145868.362027] usb 2-4.1: reset SuperSpeed USB device number 3 using xhci_hcd
[145868.392153] OOM killer enabled.
[145868.392154] Restarting tasks ...
[145868.396280] usb 3-1.1: USB disconnect, device number 10
[145868.398117] done.
[145868.398186] random: crng reseeded on system resumption
[145868.398483] thermal thermal_zone1: failed to read out thermal zone (-61)
[145868.398489] PM: suspend exit
[145868.584283] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-e00:00: attached PHY
driver (mii_bus:phy_addr=r8169-0-e00:00, irq=MAC)
[145868.724456] usb 3-1.1: new full-speed USB device number 11 using xhci_hcd
[145868.792377] r8169 0000:0e:00.0 enp14s0: Link is Down
[145868.816654] iwlwifi 0000:0f:00.0: WRT: Invalid buffer destination
[145868.902963] usb 3-1.1: New USB device found, idVendor=18d1, idProduct=9470,
bcdDevice= 0.01
[145868.902970] usb 3-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[145868.902972] usb 3-1.1: Product: Titan Security Key v2
[145868.902974] usb 3-1.1: Manufacturer: Google
[145868.902976] usb 3-1.1: SerialNumber: 2
[145868.956956] iwlwifi 0000:0f:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[145868.956973] iwlwifi 0000:0f:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[145868.956985] iwlwifi 0000:0f:00.0: WFPM_AUTH_KEY_0: 0x90
[145868.957003] iwlwifi 0000:0f:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[145868.995154] hid-generic 0003:18D1:9470.000E: hiddev3,hidraw5: USB HID v1.11
Device [Google Titan Security Key v2] on usb-0000:13:00.3-1.1/input0
[145870.400184] Bluetooth: hci0: command 0xfc05 tx timeout
[145870.400186] Bluetooth: hci0: Reading Intel version command failed (-110)
[145872.137980] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[145872.141974] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[145872.187802] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[145872.187807] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[145872.189423] wlp15s0: authenticated
[145872.192260] wlp15s0: associate with 68:7f:f0:00:74:ff (try 1/3)
[145872.196950] wlp15s0: RX AssocResp from 68:7f:f0:00:74:ff (capab=0x1011
status=0 aid=11)
[145872.201545] wlp15s0: associated
[145872.277453] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by
68:7f:f0:00:74:ff
[146087.750408] wlp15s0: disconnect from AP 68:7f:f0:00:74:ff for new auth to
68:7f:f0:00:75:00
[146087.862444] wlp15s0: authenticate with 68:7f:f0:00:75:00
[146087.865472] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[146087.910977] wlp15s0: authenticate with 68:7f:f0:00:75:00
[146087.910982] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[146087.912359] wlp15s0: authenticated
[146087.917849] wlp15s0: associate with 68:7f:f0:00:75:00 (try 1/3)
[146088.025836] wlp15s0: associate with 68:7f:f0:00:75:00 (try 2/3)
[146088.133827] wlp15s0: associate with 68:7f:f0:00:75:00 (try 3/3)
[146088.237836] wlp15s0: association with 68:7f:f0:00:75:00 timed out
[146088.482522] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[146088.486045] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[146088.521911] wlp15s0: authenticated
[146088.525862] wlp15s0: associate with 68:7f:f0:00:74:ff (try 1/3)
[146088.527379] wlp15s0: RX AssocResp from 68:7f:f0:00:74:ff (capab=0x1011
status=30 aid=11)
[146088.527384] wlp15s0: 68:7f:f0:00:74:ff rejected association temporarily;
comeback duration 292 TU (299 ms)
[146088.527553] iwlwifi 0000:0f:00.0: Unhandled alg: 0x707
[146088.829816] wlp15s0: associate with 68:7f:f0:00:74:ff (try 2/3)
[146088.949803] wlp15s0: associate with 68:7f:f0:00:74:ff (try 3/3)
[146089.053974] wlp15s0: association with 68:7f:f0:00:74:ff timed out
[146089.691292] wlp15s0: authenticate with 68:7f:f0:00:75:01
[146089.691308] wlp15s0: 80 MHz not supported, disabling VHT
[146089.694380] wlp15s0: send auth to 68:7f:f0:00:75:01 (try 1/3)
[146089.738759] wlp15s0: authenticate with 68:7f:f0:00:75:01
[146089.738763] wlp15s0: send auth to 68:7f:f0:00:75:01 (try 1/3)
[146089.741258] wlp15s0: authenticated
[146089.741777] wlp15s0: associate with 68:7f:f0:00:75:01 (try 1/3)
[146089.748880] wlp15s0: RX AssocResp from 68:7f:f0:00:75:01 (capab=0x1431
status=0 aid=43)
[146089.755406] wlp15s0: associated
[146089.825778] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by
68:7f:f0:00:75:01
[149091.410380] iwlwifi 0000:0f:00.0: Unhandled alg: 0x703
[149179.529466] wlp15s0: deauthenticating from 68:7f:f0:00:75:01 by local
choice (Reason: 3=DEAUTH_LEAVING)
[149179.911595] PM: suspend entry (deep)
[149183.853348] Filesystems sync: 3.941 seconds
[149183.856089] Freezing user space processes
[149183.858844] Freezing user space processes completed (elapsed 0.002 seconds)
[149183.858847] OOM killer disabled.
[149183.858848] Freezing remaining freezable tasks
[149183.860090] Freezing remaining freezable tasks completed (elapsed 0.001
seconds)
[149183.860117] printk: Suspending console(s) (use no_console_suspend to debug)
[149183.861305] serial 00:04: disabled
[149183.908278] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[149183.910460] ata1.00: Entering standby power mode
[149183.916562] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[149183.917396] ata3.00: Entering standby power mode
[149184.326448] amdgpu 0000:03:00.0: amdgpu: MODE1 reset
[149184.326451] amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
[149184.326510] amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
[149184.908242] ACPI: PM: Preparing to enter system sleep state S3
[149185.248528] ACPI: PM: Saving platform NVS memory
[149185.249283] Disabling non-boot CPUs ...
[149185.251387] smpboot: CPU 1 is now offline
[149185.254559] smpboot: CPU 2 is now offline
[149185.257913] smpboot: CPU 3 is now offline
[149185.261367] smpboot: CPU 4 is now offline
[149185.264968] smpboot: CPU 5 is now offline
[149185.268391] smpboot: CPU 6 is now offline
[149185.271700] smpboot: CPU 7 is now offline
[149185.274820] smpboot: CPU 8 is now offline
[149185.278116] smpboot: CPU 9 is now offline
[149185.281419] smpboot: CPU 10 is now offline
[149185.284437] smpboot: CPU 11 is now offline
[149185.287676] smpboot: CPU 12 is now offline
[149185.288851] Spectre V2 : Update user space SMT mitigation: STIBP off
[149185.290401] smpboot: CPU 13 is now offline
[149185.292721] smpboot: CPU 14 is now offline
[149185.294954] smpboot: CPU 15 is now offline
[149185.297243] smpboot: CPU 16 is now offline
[149185.300086] smpboot: CPU 17 is now offline
[149185.302804] smpboot: CPU 18 is now offline
[149185.305190] smpboot: CPU 19 is now offline
[149185.307342] smpboot: CPU 20 is now offline
[149185.309776] smpboot: CPU 21 is now offline
[149185.311915] smpboot: CPU 22 is now offline
[149185.314139] smpboot: CPU 23 is now offline
[149185.315061] ACPI: PM: Low-level resume complete
[149185.315083] ACPI: PM: Restoring platform NVS memory
[149185.346774] AMD-Vi: Virtual APIC enabled
[149185.352012] AMD-Vi: Virtual APIC enabled
[149185.352023] LVT offset 0 assigned for vector 0x400
[149185.352594] Enabling non-boot CPUs ...
[149185.352621] smpboot: Booting Node 0 Processor 1 APIC 0x2
[149185.355632] ACPI: \_SB_.PLTF.C002: Found 3 idle states
[149185.355944] CPU1 is up
[149185.355958] smpboot: Booting Node 0 Processor 2 APIC 0x4
[149185.358268] ACPI: \_SB_.PLTF.C004: Found 3 idle states
[149185.358470] CPU2 is up
[149185.358483] smpboot: Booting Node 0 Processor 3 APIC 0x6
[149185.360790] ACPI: \_SB_.PLTF.C006: Found 3 idle states
[149185.360978] CPU3 is up
[149185.360992] smpboot: Booting Node 0 Processor 4 APIC 0x8
[149185.363297] ACPI: \_SB_.PLTF.C008: Found 3 idle states
[149185.363503] CPU4 is up
[149185.363516] smpboot: Booting Node 0 Processor 5 APIC 0xa
[149185.365823] ACPI: \_SB_.PLTF.C00A: Found 3 idle states
[149185.366037] CPU5 is up
[149185.366050] smpboot: Booting Node 0 Processor 6 APIC 0x10
[149185.368420] ACPI: \_SB_.PLTF.C00C: Found 3 idle states
[149185.368736] CPU6 is up
[149185.368750] smpboot: Booting Node 0 Processor 7 APIC 0x12
[149185.371131] ACPI: \_SB_.PLTF.C00E: Found 3 idle states
[149185.371373] CPU7 is up
[149185.371389] smpboot: Booting Node 0 Processor 8 APIC 0x14
[149185.373742] ACPI: \_SB_.PLTF.C010: Found 3 idle states
[149185.374013] CPU8 is up
[149185.374027] smpboot: Booting Node 0 Processor 9 APIC 0x16
[149185.376370] ACPI: \_SB_.PLTF.C012: Found 3 idle states
[149185.376649] CPU9 is up
[149185.376664] smpboot: Booting Node 0 Processor 10 APIC 0x18
[149185.379003] ACPI: \_SB_.PLTF.C014: Found 3 idle states
[149185.379292] CPU10 is up
[149185.379306] smpboot: Booting Node 0 Processor 11 APIC 0x1a
[149185.381642] ACPI: \_SB_.PLTF.C016: Found 3 idle states
[149185.381936] CPU11 is up
[149185.381951] smpboot: Booting Node 0 Processor 12 APIC 0x1
[149185.384275] ACPI: \_SB_.PLTF.C001: Found 3 idle states
[149185.384681] Spectre V2 : Update user space SMT mitigation: STIBP always-on
[149185.384686] CPU12 is up
[149185.384701] smpboot: Booting Node 0 Processor 13 APIC 0x3
[149185.386816] Spurious APIC interrupt (vector 0xFF) on CPU#13, should never
happen.
[149185.387013] ACPI: \_SB_.PLTF.C003: Found 3 idle states
[149185.387337] CPU13 is up
[149185.387350] smpboot: Booting Node 0 Processor 14 APIC 0x5
[149185.389466] Spurious APIC interrupt (vector 0xFF) on CPU#14, should never
happen.
[149185.389658] ACPI: \_SB_.PLTF.C005: Found 3 idle states
[149185.389982] CPU14 is up
[149185.389994] smpboot: Booting Node 0 Processor 15 APIC 0x7
[149185.392112] Spurious APIC interrupt (vector 0xFF) on CPU#15, should never
happen.
[149185.392312] ACPI: \_SB_.PLTF.C007: Found 3 idle states
[149185.392631] CPU15 is up
[149185.392644] smpboot: Booting Node 0 Processor 16 APIC 0x9
[149185.394761] Spurious APIC interrupt (vector 0xFF) on CPU#16, should never
happen.
[149185.394966] ACPI: \_SB_.PLTF.C009: Found 3 idle states
[149185.395315] CPU16 is up
[149185.395328] smpboot: Booting Node 0 Processor 17 APIC 0xb
[149185.397434] Spurious APIC interrupt (vector 0xFF) on CPU#17, should never
happen.
[149185.397649] ACPI: \_SB_.PLTF.C00B: Found 3 idle states
[149185.398026] CPU17 is up
[149185.398039] smpboot: Booting Node 0 Processor 18 APIC 0x11
[149185.400170] Spurious APIC interrupt (vector 0xFF) on CPU#18, should never
happen.
[149185.400383] ACPI: \_SB_.PLTF.C00D: Found 3 idle states
[149185.400806] CPU18 is up
[149185.400820] smpboot: Booting Node 0 Processor 19 APIC 0x13
[149185.402954] Spurious APIC interrupt (vector 0xFF) on CPU#19, should never
happen.
[149185.403172] ACPI: \_SB_.PLTF.C00F: Found 3 idle states
[149185.403560] CPU19 is up
[149185.403574] smpboot: Booting Node 0 Processor 20 APIC 0x15
[149185.405713] Spurious APIC interrupt (vector 0xFF) on CPU#20, should never
happen.
[149185.405936] ACPI: \_SB_.PLTF.C011: Found 3 idle states
[149185.406371] CPU20 is up
[149185.406385] smpboot: Booting Node 0 Processor 21 APIC 0x17
[149185.408504] Spurious APIC interrupt (vector 0xFF) on CPU#21, should never
happen.
[149185.408726] ACPI: \_SB_.PLTF.C013: Found 3 idle states
[149185.409169] CPU21 is up
[149185.409182] smpboot: Booting Node 0 Processor 22 APIC 0x19
[149185.411327] Spurious APIC interrupt (vector 0xFF) on CPU#22, should never
happen.
[149185.411556] ACPI: \_SB_.PLTF.C015: Found 3 idle states
[149185.412023] CPU22 is up
[149185.412037] smpboot: Booting Node 0 Processor 23 APIC 0x1b
[149185.414185] Spurious APIC interrupt (vector 0xFF) on CPU#23, should never
happen.
[149185.414424] ACPI: \_SB_.PLTF.C017: Found 3 idle states
[149185.414892] CPU23 is up
[149185.417561] ACPI: PM: Waking up from system sleep state S3
[149185.709144] [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
[149185.709184] [drm] PSP is resuming...
[149185.711294] serial 00:04: activated
[149185.712048] xhci_hcd 0000:10:00.0: xHC error in resume, USBSTS 0x401,
Reinit
[149185.712053] usb usb1: root hub lost power or was reset
[149185.712055] usb usb2: root hub lost power or was reset
[149185.712377] [drm] PCIE GART of 512M enabled (table at 0x0000008001300000).
[149185.712397] [drm] PSP is resuming...
[149185.730571] [drm] reserve 0xa00000 from 0xf41e000000 for PSP TMR
[149185.738192] nvme nvme1: 24/0/0 default/read/poll queues
[149185.743545] nvme nvme0: 24/0/0 default/read/poll queues
[149185.787680] [drm] reserve 0xa00000 from 0x80fd000000 for PSP TMR
[149185.794772] amdgpu 0000:13:00.0: amdgpu: RAS: optional ras ta ucode is not
available
[149185.800508] amdgpu 0000:13:00.0: amdgpu: RAP: optional rap ta ucode is not
available
[149185.800509] amdgpu 0000:13:00.0: amdgpu: SECUREDISPLAY: securedisplay ta
ucode is not available
[149185.800511] amdgpu 0000:13:00.0: amdgpu: SMU is resuming...
[149185.800514] amdgpu 0000:13:00.0: amdgpu: smu driver if version =
0x00000004, smu fw if version = 0x00000005, smu fw program = 0, smu fw version
= 0x00544fdf (84.79.223)
[149185.800516] amdgpu 0000:13:00.0: amdgpu: SMU driver if version not matched
[149185.802406] amdgpu 0000:13:00.0: amdgpu: SMU is resumed successfully!
[149185.803069] [drm] DMUB hardware initialized: version=0x05000500
[149185.803759] [drm] kiq ring mec 2 pipe 1 q 0
[149185.806134] [drm] VCN decode and encode initialized successfully(under DPG
Mode).
[149185.806630] [drm] JPEG decode initialized successfully.
[149185.806638] amdgpu 0000:13:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0
on hub 0
[149185.806640] amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1
on hub 0
[149185.806641] amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4
on hub 0
[149185.806642] amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5
on hub 0
[149185.806643] amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6
on hub 0
[149185.806644] amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7
on hub 0
[149185.806644] amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8
on hub 0
[149185.806645] amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9
on hub 0
[149185.806646] amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10
on hub 0
[149185.806647] amdgpu 0000:13:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng
11 on hub 0
[149185.806648] amdgpu 0000:13:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on
hub 0
[149185.806649] amdgpu 0000:13:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0
on hub 8
[149185.806649] amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1
on hub 8
[149185.806650] amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4
on hub 8
[149185.806651] amdgpu 0000:13:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on
hub 8
[149185.809093] amdgpu 0000:13:00.0: [drm] Cannot find any crtc or sizes
[149185.878177] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not
available
[149185.892862] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta
ucode is not available
[149185.892864] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
[149185.892867] amdgpu 0000:03:00.0: amdgpu: smu driver if version =
0x0000000d, smu fw if version = 0x0000000f, smu fw program = 0, version =
0x00491a00 (73.26.0)
[149185.892869] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[149185.892898] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
[149185.935257] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
[149185.936320] [drm] DMUB hardware initialized: version=0x0202000C
[149186.025471] ata2: SATA link down (SStatus 0 SControl 300)
[149186.025507] ata4: SATA link down (SStatus 0 SControl 300)
[149186.065903] usb 1-4: reset high-speed USB device number 4 using xhci_hcd
[149186.185908] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[149186.185915] ata3.00: Entering active power mode
[149186.185925] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[149186.185932] ata1.00: Entering active power mode
[149186.187298] ata3.00: configured for UDMA/133
[149186.222180] ata1.00: configured for UDMA/133
[149186.264719] [drm] kiq ring mec 2 pipe 1 q 0
[149186.268726] [drm] VCN decode and encode initialized successfully(under DPG
Mode).
[149186.268743] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0
on hub 0
[149186.268745] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1
on hub 0
[149186.268746] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4
on hub 0
[149186.268747] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5
on hub 0
[149186.268747] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6
on hub 0
[149186.268748] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7
on hub 0
[149186.268749] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8
on hub 0
[149186.268750] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9
on hub 0
[149186.268751] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10
on hub 0
[149186.268752] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng
11 on hub 0
[149186.268753] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on
hub 0
[149186.268754] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0
on hub 8
[149186.422419] usb 1-10: reset high-speed USB device number 7 using xhci_hcd
[149186.834049] usb 1-2: reset full-speed USB device number 2 using xhci_hcd
[149187.190425] usb 1-6: reset full-speed USB device number 5 using xhci_hcd
[149187.622508] usb 1-7: reset full-speed USB device number 6 using xhci_hcd
[149187.982476] usb 1-3: reset full-speed USB device number 3 using xhci_hcd
[149188.339631] usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
[149188.695128] usb 2-4.1: reset SuperSpeed USB device number 3 using xhci_hcd
[149188.726267] OOM killer enabled.
[149188.726269] Restarting tasks ...
[149188.727151] usb 3-1.1: USB disconnect, device number 11
[149188.733287] done.
[149188.733357] random: crng reseeded on system resumption
[149188.733641] thermal thermal_zone1: failed to read out thermal zone (-61)
[149188.733647] PM: suspend exit
[149188.853588] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-e00:00: attached PHY
driver (mii_bus:phy_addr=r8169-0-e00:00, irq=MAC)
[149189.041548] usb 3-1.1: new full-speed USB device number 12 using xhci_hcd
[149189.057671] r8169 0000:0e:00.0 enp14s0: Link is Down
[149189.078963] iwlwifi 0000:0f:00.0: WRT: Invalid buffer destination
[149189.219127] iwlwifi 0000:0f:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[149189.219144] iwlwifi 0000:0f:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[149189.219156] iwlwifi 0000:0f:00.0: WFPM_AUTH_KEY_0: 0x90
[149189.219173] iwlwifi 0000:0f:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[149189.224292] usb 3-1.1: New USB device found, idVendor=18d1, idProduct=9470,
bcdDevice= 0.01
[149189.224296] usb 3-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[149189.224298] usb 3-1.1: Product: Titan Security Key v2
[149189.224299] usb 3-1.1: Manufacturer: Google
[149189.224301] usb 3-1.1: SerialNumber: 2
[149189.308434] hid-generic 0003:18D1:9470.000F: hiddev3,hidraw5: USB HID v1.11
Device [Google Titan Security Key v2] on usb-0000:13:00.3-1.1/input0
[149189.969354] audit: type=1400 audit(1716563707.612:38): apparmor="DENIED"
operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=216640
comm="cupsd" capability=12 capname="net_admin"
[149190.753488] Bluetooth: hci0: command 0xfc05 tx timeout
[149190.753505] Bluetooth: hci0: Reading Intel version command failed (-110)
[149192.255262] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[149192.258778] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[149192.304143] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[149192.304148] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[149192.305829] wlp15s0: authenticated
[149192.309434] wlp15s0: associate with 68:7f:f0:00:74:ff (try 1/3)
[149192.313848] wlp15s0: RX AssocResp from 68:7f:f0:00:74:ff (capab=0x1011
status=0 aid=21)
[149192.318570] wlp15s0: associated
[149192.350228] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by
68:7f:f0:00:74:ff
```
bluetoothctl:
```
Agent registered
[bluetooth]#
```
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (27 preceding siblings ...)
2024-05-24 15:29 ` bugzilla-daemon
@ 2024-05-24 20:41 ` bugzilla-daemon
2024-05-24 21:01 ` bugzilla-daemon
` (7 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-24 20:41 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #28 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
@dustin, thank you, but please *attach* the full log next time.
[90310.622241] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
is different from this issue title. Please create a new issue, and attach all
the information there.
> This is a regression. It has been broken since 6.5. It worked fine in prior
> kernel versions.
That is actually a good thing. It’d be great if you bisected the commit
introducing the regression [1].
[1]:
https://www.kernel.org/doc/html/latest/admin-guide/verify-bugs-and-bisect-regressions.html
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (28 preceding siblings ...)
2024-05-24 20:41 ` bugzilla-daemon
@ 2024-05-24 21:01 ` bugzilla-daemon
2024-05-24 21:03 ` bugzilla-daemon
` (6 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-24 21:01 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #29 from Dustin (dustin@falgout.us) ---
That error is new. I've actually never seen it before now. The error I was
getting ever since I updated to 6.5+ was exactly the same as the error in this
bug's description. I see it's still in the logs I posted today in addition to
that new error.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (29 preceding siblings ...)
2024-05-24 21:01 ` bugzilla-daemon
@ 2024-05-24 21:03 ` bugzilla-daemon
2024-05-24 21:11 ` bugzilla-daemon
` (5 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-24 21:03 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #30 from Dustin (dustin@falgout.us) ---
Btw, I opened an issue with Ubuntu before I found this issue. You can find the
debug info I posted including logs there:
https://bugs.launchpad.net/linux/+bug/2051720
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (30 preceding siblings ...)
2024-05-24 21:03 ` bugzilla-daemon
@ 2024-05-24 21:11 ` bugzilla-daemon
2024-05-24 21:19 ` bugzilla-daemon
` (4 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-24 21:11 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #31 from Dustin (dustin@falgout.us) ---
It looks like that new error is from when I attempted to use my BT headphones
for a meeting the other day after doing a cold boot. It's unrelated. Sorry
about that. You can see at the end of the logs I posted where bluetooth stopped
working after waking from suspend and the error is the exact error from this
bug's description.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (31 preceding siblings ...)
2024-05-24 21:11 ` bugzilla-daemon
@ 2024-05-24 21:19 ` bugzilla-daemon
2024-05-25 5:22 ` bugzilla-daemon
` (3 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-24 21:19 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #32 from Nickolas Gupton (nickolas@gupton.xyz) ---
Created attachment 306340
--> https://bugzilla.kernel.org/attachment.cgi?id=306340&action=edit
dmesg log
(In reply to Paul Menzel from comment #26)
> @nickolas, from your bug description it’s unclear, if this is a regression,
> or if Bluetooth never worked for you. Could you please clarify?
>
> Please attach the output of `dmesg`.
>
> Also, please run `bluetoothctl` and share all the output.
The issue is still presenting the same as originally reported, bluetooth does
not work on boot and requires the reset script I provided before it will start
working. The only difference between then and now is that one log is missing.
Here are the extra logs you've asked for, the dmesg log was quite long so I
attached it as a file:
# dmesg
(see attached file)
(before running the reset script)
$ bluetoothctl
Waiting to connect to bluetoothd...
(after running the reset script)
$ bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# hci0 new_settings: powered bondable ssp br/edr le secure-conn
wide-band-speech
[bluetooth]# [CHG] Controller A4:B1:C1:D5:F5:24 Pairable: yes
[bluetooth]# AdvertisementMonitor path registered
[bluetooth]#
(In reply to Dustin from comment #27)
> This is a regression. It has been broken since 6.5. It worked fine in prior
> kernel versions.
I believe your issue is different than this one, this issue has been reported
starting in 5.16 on the original bug linked that they closed and asked for
someone to make a new issue if it was still present.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (32 preceding siblings ...)
2024-05-24 21:19 ` bugzilla-daemon
@ 2024-05-25 5:22 ` bugzilla-daemon
2024-06-12 0:58 ` bugzilla-daemon
` (2 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-05-25 5:22 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #33 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
(In reply to Nickolas Gupton from comment #32)
> this issue has been reported starting in 5.16 on the original bug linked that
> they closed and asked for someone to make a new issue if it was still
> present.
Bug 215167 [1] reports a regression in Linux 5.14, and the referenced openSUSE
report says at the end it should be fixed in 5.16.1.
Nickolas, thank you for attaching the full Linux logs. As the error from the
bug title is not present in the log, I recommend to close this issue, and
create a new one for your problem with a descriptive title like *Bluetooth only
starts working after reloading btusb and btintel*, attaching all the files
there. If you could bisect [3] the commit, that would even get you there
faster. The Bluetooth device can even be passed to a virtual machine, and if
the problem is reproducible there, bisection is quite fast [4][5].
I am sorry about this, but unfortunately, the comments by others on probably
different issues, make it very hard and time consuming to understanding the
actual issue. It looks like the maintainers are overworked and the subsystem
has not enough resources. Still if you buy a device with Intel hardware (and
even better a device with official GNU/Linux support), it’s valid to expect
that Intel hardware works also on GNU/Linux.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=215167
[2]: https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
[3]:
https://www.kernel.org/doc/html/latest/admin-guide/verify-bugs-and-bisect-regressions.html
[4]:
https://lore.kernel.org/linux-bluetooth/5891f0d5-8d51-9da5-7663-718f301490b1@molgen.mpg.de/
[5]:
https://lore.kernel.org/lkml/d7206e12-1b99-c3be-84f4-df22af427ef5@molgen.mpg.de/
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (33 preceding siblings ...)
2024-05-25 5:22 ` bugzilla-daemon
@ 2024-06-12 0:58 ` bugzilla-daemon
2024-06-12 1:06 ` bugzilla-daemon
2024-06-12 15:25 ` bugzilla-daemon
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-06-12 0:58 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Priit O. (priit@ww.ee) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |priit@ww.ee
--- Comment #34 from Priit O. (priit@ww.ee) ---
still present in kernel 6.9.3
dmesg | grep -i bluetooth
[ 4.466394] Bluetooth: Core ver 2.22
[ 4.466410] NET: Registered PF_BLUETOOTH protocol family
[ 4.466411] Bluetooth: HCI device and connection manager initialized
[ 4.466417] Bluetooth: HCI socket layer initialized
[ 4.466419] Bluetooth: L2CAP socket layer initialized
[ 4.466422] Bluetooth: SCO socket layer initialized
[ 5.405005] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.405007] Bluetooth: BNEP filters: protocol multicast
[ 5.405010] Bluetooth: BNEP socket layer initialized
[ 6.696883] Bluetooth: hci0: command 0xfc05 tx timeout
[ 6.696966] Bluetooth: hci0: Reading Intel version command failed (-110)
what's even more troublesome is that previously I was able to make it work with
(sometimes with couple of tries):
sudo rmmod btusb && sudo modprobe btusb
now with this kernel I get only this over and over:
[ 74.101494] usbcore: deregistering interface driver btusb
[ 74.279683] usbcore: registered new interface driver btusb
[ 76.457250] Bluetooth: hci0: command 0xfc05 tx timeout
[ 76.457268] Bluetooth: hci0: Reading Intel version command failed (-110)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (34 preceding siblings ...)
2024-06-12 0:58 ` bugzilla-daemon
@ 2024-06-12 1:06 ` bugzilla-daemon
2024-06-12 15:25 ` bugzilla-daemon
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-06-12 1:06 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #35 from Priit O. (priit@ww.ee) ---
And yes, it is regression. also it does not work with kernel 6.6 (LTS).
However it does work perfectly well with kernel 6.1.92.
Linux Zen 6.1.92-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon May 27 03:37:00 UTC 2024
x86_64 GNU/Linux
$ dmesg | grep -i bluetooth
[ 5.621856] Bluetooth: Core ver 2.22
[ 5.621877] NET: Registered PF_BLUETOOTH protocol family
[ 5.621878] Bluetooth: HCI device and connection manager initialized
[ 5.621881] Bluetooth: HCI socket layer initialized
[ 5.621883] Bluetooth: L2CAP socket layer initialized
[ 5.621887] Bluetooth: SCO socket layer initialized
[ 5.659250] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 5.661255] Bluetooth: hci0: Device revision is 1
[ 5.661259] Bluetooth: hci0: Secure boot is enabled
[ 5.661260] Bluetooth: hci0: OTP lock is enabled
[ 5.661262] Bluetooth: hci0: API lock is enabled
[ 5.661263] Bluetooth: hci0: Debug lock is disabled
[ 5.661264] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 5.663789] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 5.663805] Bluetooth: hci0: Boot Address: 0x24800
[ 5.663807] Bluetooth: hci0: Firmware Version: 132-3.24
[ 6.464952] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.464954] Bluetooth: BNEP filters: protocol multicast
[ 6.464957] Bluetooth: BNEP socket layer initialized
[ 7.025995] Bluetooth: hci0: Waiting for firmware download to complete
[ 7.026211] Bluetooth: hci0: Firmware loaded in 1330487 usecs
[ 7.026245] Bluetooth: hci0: Waiting for device to boot
[ 7.041215] Bluetooth: hci0: Device booted in 14630 usecs
[ 7.041217] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 7.041527] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-20-1-3.ddc
[ 7.047218] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 7.050221] Bluetooth: hci0: Firmware revision 0.3 build 132 week 3 2024
[ 7.217324] Bluetooth: MGMT ver 1.22
[ 18.841731] Bluetooth: RFCOMM TTY layer initialized
[ 18.841737] Bluetooth: RFCOMM socket layer initialized
[ 18.841740] Bluetooth: RFCOMM ver 1.11
sorry, but I have no time or will to install and test with every non-supported
kernel versions inbetween 6.1 and 6.6 to see where the error came back in.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread* [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
` (35 preceding siblings ...)
2024-06-12 1:06 ` bugzilla-daemon
@ 2024-06-12 15:25 ` bugzilla-daemon
36 siblings, 0 replies; 38+ messages in thread
From: bugzilla-daemon @ 2024-06-12 15:25 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #36 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
What now, CCP (aka AX201), is what I have in my laptop for ages and I never had
a single problem with it:
Linux 6.8.10-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 17 21:20:54 UTC
2024 x86_64 GNU/Linux
[ 5.935014] Bluetooth: hci1: Found device firmware: intel/ibt-20-1-3.sfi
[ 5.935118] Bluetooth: hci1: Boot Address: 0x24800
[ 5.935120] Bluetooth: hci1: Firmware Version: 132-3.24
Having 0xfc05 to timeout normally means the controller is not responding since
it is the very first command the btintel.c will send, most likely that is
because there is something at preventing any communication to work or
something, so Id be really surprised this is a regression at btusb/btintel
otherwise we would be consistently seeing this in our systems as well.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 38+ messages in thread