#1036015 linux-image-6.3.0-0-amd64: Bluetooth mouse connect very delay after wake up from suspend

Package:
src:linux
Source:
src:linux
Submitter:
xiao sheng wen
Date:
2024-08-10 12:21:17 UTC
Severity:
normal
Tags:
#1036015#5
Date:
2023-05-13 01:02:50 UTC
From:
To:
Dear Maintainer,
   * What led up to the situation?
When I close my notebook lid, the notebook will suspend to memory,then I open
the lid, the notebook will wake up from suspend, but my Bluetooth mouse can't
use immediately, must wait almost a minute before Bluetooth mouse connect.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
When I use Debian 11.6, the kernel is linux-image-5.10.0-21-rt-amd64,
there is not this bug.
After I upgrade to Debian 11.7, the kernel is linux-image-5.10.0-22-rt-amd64,
this bug take place.
I also test the kernel linux-image-6.1.0-0.deb11.6-amd64, it has this bug.

   * What outcome did you expect instead?
I hope my Bluetooth mouse can connect my notebook immediately.
#1036015#10
Date:
2023-05-13 01:21:07 UTC
From:
To:
When I boot use linux-image-5.10.0-21-rt-amd64, there is not this bug,
dmesg is:

[Sat May 13 09:09:11 2023] CPU3 is up
[Sat May 13 09:09:11 2023] ACPI: Waking up from system sleep state S3
[Sat May 13 09:09:11 2023] pcieport 0000:00:1d.0: Intel SPT PCH root
port ACS workaround enabled
[Sat May 13 09:09:11 2023] sd 1:0:0:0: [sda] Starting disk
[Sat May 13 09:09:11 2023] usb 1-7: reset high-speed USB device number 3
using xhci_hcd
[Sat May 13 09:09:11 2023] ata1: SATA link down (SStatus 4 SControl 300)
[Sat May 13 09:09:11 2023] ata2: SATA link up 6.0 Gbps (SStatus 133
SControl 300)
[Sat May 13 09:09:11 2023] ata2.00: configured for UDMA/133
[Sat May 13 09:09:11 2023] ahci 0000:00:17.0: port does not support
device sleep
[Sat May 13 09:09:11 2023] usb 1-3: reset full-speed USB device number 2
using xhci_hcd
[Sat May 13 09:09:12 2023] OOM killer enabled.
[Sat May 13 09:09:12 2023] Restarting tasks ...
[Sat May 13 09:09:12 2023] Bluetooth: hci0: Bootloader revision 0.0
build 2 week 52 2014
[Sat May 13 09:09:12 2023] done.
[Sat May 13 09:09:12 2023] Bluetooth: hci0: Device revision is 5
[Sat May 13 09:09:12 2023] Bluetooth: hci0: Secure boot is enabled
[Sat May 13 09:09:12 2023] Bluetooth: hci0: OTP lock is enabled
[Sat May 13 09:09:12 2023] Bluetooth: hci0: API lock is enabled
[Sat May 13 09:09:12 2023] Bluetooth: hci0: Debug lock is disabled
[Sat May 13 09:09:12 2023] Bluetooth: hci0: Minimum firmware build 1
week 10 2014
[Sat May 13 09:09:12 2023] PM: suspend exit
[Sat May 13 09:09:12 2023] bluetooth hci0: firmware: direct-loading
firmware intel/ibt-11-5.sfi
[Sat May 13 09:09:12 2023] Bluetooth: hci0: Found device firmware:
intel/ibt-11-5.sfi
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Waiting for firmware
download to complete
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Firmware loaded in 1577026 usecs
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Waiting for device to boot
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Device booted in 11664 usecs
[Sat May 13 09:09:13 2023] bluetooth hci0: firmware: direct-loading
firmware intel/ibt-11-5.ddc
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-11-5.ddc
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Applying Intel DDC
parameters completed
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Reading supported features
failed (-16)
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Telemetry exception format
not supported
[Sat May 13 09:09:13 2023] Bluetooth: hci0: Firmware revision 0.0 build
14 week 44 2021
[Sat May 13 09:09:15 2023] input: RAPOO BT4.0 Mouse as
/devices/virtual/misc/uhid/0005:000E:3412.0003/input/input21
[Sat May 13 09:09:15 2023] input: RAPOO BT4.0 Mouse Consumer Control as
/devices/virtual/misc/uhid/0005:000E:3412.0003/input/input22
[Sat May 13 09:09:15 2023] hid-generic 0005:000E:3412.0003:
input,hidraw1: BLUETOOTH HID v67.01 Mouse [RAPOO BT4.0 Mouse] on
a0:c5:89:47:0c:10


Even there is one warning:
"[Sat May 13 09:09:13 2023] Bluetooth: hci0: Reading supported features
failed (-16)"
But my Bluetooth can use immediately.
#1036015#19
Date:
2023-05-13 09:09:46 UTC
From:
To:
Control: tag -1 moreinfo

You reported the issue against version 6.3.1-1, but that version isn't
mentioned in your bug report. What's the status with that version?

Does the same regression happen with the non-rt versions of those 5.10
kernels?
The best way to track down the cause of this regression is to do a `git
bisect` of the kernel between 5.10.162 and 5.10.178.
https://wiki.debian.org/DebianKernel/GitBisect has instructions for it.
#1036015#26
Date:
2023-05-13 09:25:24 UTC
From:
To:
I would normally advise against installing 'random' kernel versions on a
Debian Stable system, but as you already installed the kernel from
Experimental, can you also try 6.1.0-9?
Earlier today we had a user who reported that that version fixed a bluetooth
issue for them.
#1036015#31
Date:
2023-05-13 12:45:58 UTC
From:
To:
Hi,

在 2023/5/13 17:25, Diederik de Haas 写道:
This bug exist in version 6.3.1-1.
The dmesg Kernel log is come from 6.3.1-1 in bug report.
I install linux-image-6.1.0-9-amd64  6.1.27-1 and boot from it, this bug
still exist.

I had done several repeat test :

This test delay 6 seconds, from 19:52:53 to 19:52:59.
[Sat May 13 19:52:53 2023] Bluetooth: hci0: Applying Intel DDC
parameters completed
[Sat May 13 19:52:53 2023] Bluetooth: hci0: Firmware revision 0.0 build
14 week 44 2021
[Sat May 13 19:52:53 2023] Bluetooth: MGMT ver 1.22
[Sat May 13 19:52:53 2023] Bluetooth: hci0: Bad flag given (0x1) vs
supported (0x0)
[Sat May 13 19:52:57 2023] wlp1s0: authenticate with 44:f9:71:69:42:20
[Sat May 13 19:52:57 2023] wlp1s0: send auth to 44:f9:71:69:42:20 (try 1/3)
[Sat May 13 19:52:57 2023] wlp1s0: authenticated
[Sat May 13 19:52:57 2023] wlp1s0: associate with 44:f9:71:69:42:20 (try
1/3)
[Sat May 13 19:52:57 2023] wlp1s0: RX AssocResp from 44:f9:71:69:42:20
(capab=0x1011 status=0 aid=2)
[Sat May 13 19:52:57 2023] wlp1s0: associated
[Sat May 13 19:52:57 2023] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link
becomes ready
[Sat May 13 19:52:59 2023] input: RAPOO BT4.0 Mouse as
/devices/virtual/misc/uhid/0005:000E:3412.0004/input/input21
[Sat May 13 19:52:59 2023] input: RAPOO BT4.0 Mouse Consumer Control as
/devices/virtual/misc/uhid/0005:000E:3412.0004/input/input22
[Sat May 13 19:52:59 2023] hid-generic 0005:000E:3412.0004:
input,hidraw1: BLUETOOTH HID v67.01 Mouse [RAPOO BT4.0 Mouse] on
a0:c5:89:47:0c:10
[Sat May 13 19:53:04 2023] wlp1s0: Limiting TX power to 35 (35 - 0) dBm
as advertised by 44:f9:71:69:42:20
[Sat May 13 19:53:37 2023] wlp1s0: deauthenticating from
44:f9:71:69:42:20 by local choice (Reason: 3=DEAUTH_LEAVING)

This time, delay 34 seconds, from 20:38:53 to 20:39:27.
[Sat May 13 20:38:53 2023] Bluetooth: hci0: Applying Intel DDC
parameters completed
[Sat May 13 20:38:53 2023] Bluetooth: hci0: Firmware revision 0.0 build
14 week 44 2021
[Sat May 13 20:38:53 2023] Bluetooth: MGMT ver 1.22
[Sat May 13 20:38:53 2023] Bluetooth: hci0: Bad flag given (0x1) vs
supported (0x0)
[Sat May 13 20:38:55 2023] wlp1s0: authenticate with 32:e7:6c:92:45:ab
[Sat May 13 20:38:55 2023] wlp1s0: send auth to 32:e7:6c:92:45:ab (try 1/3)
[Sat May 13 20:38:55 2023] wlp1s0: authenticated
[Sat May 13 20:38:55 2023] wlp1s0: associate with 32:e7:6c:92:45:ab (try
1/3)
[Sat May 13 20:38:55 2023] wlp1s0: RX AssocResp from 32:e7:6c:92:45:ab
(capab=0x1531 status=0 aid=11)
[Sat May 13 20:38:55 2023] wlp1s0: associated
[Sat May 13 20:38:55 2023] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link
becomes ready
[Sat May 13 20:39:27 2023] input: RAPOO BT4.0 Mouse as
/devices/virtual/misc/uhid/0005:000E:3412.0007/input/input27
[Sat May 13 20:39:27 2023] input: RAPOO BT4.0 Mouse Consumer Control as
/devices/virtual/misc/uhid/0005:000E:3412.0007/input/input28
[Sat May 13 20:39:27 2023] hid-generic 0005:000E:3412.0007:
input,hidraw1: BLUETOOTH HID v67.01 Mouse [RAPOO BT4.0 Mouse] on
a0:c5:89:47:0c:10


Thanks!
#1036015#38
Date:
2023-05-13 14:14:17 UTC
From:
To:
在 2023/5/13 17:09, Diederik de Haas 写道:
Yes, in non-rt versions of 5.10 kernel, this bug exist.

uname -a
Linux atzlinux-d0 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22)
x86_64 GNU/Linux

This time ,it delay 35 seconds:
[Sat May 13 21:54:16 2023] Bluetooth: hci0: Applying Intel DDC
parameters completed
[Sat May 13 21:54:16 2023] Bluetooth: hci0: Reading supported features
failed (-16)
[Sat May 13 21:54:16 2023] Bluetooth: hci0: Telemetry exception format
not supported
[Sat May 13 21:54:16 2023] Bluetooth: hci0: Firmware revision 0.0 build
14 week 44 2021
[Sat May 13 21:54:51 2023] input: RAPOO BT4.0 Mouse as
/devices/virtual/misc/uhid/0005:000E:3412.0007/input/input29
[Sat May 13 21:54:51 2023] input: RAPOO BT4.0 Mouse Consumer Control as
/devices/virtual/misc/uhid/0005:000E:3412.0007/input/input30
[Sat May 13 21:54:51 2023] hid-generic 0005:000E:3412.0007:
input,hidraw1: BLUETOOTH HID v67.01 Mouse [RAPOO BT4.0 Mouse] on
a0:c5:89:47:0c:10
The change of the kernel module bluetooth perhaps is the reason of this bug.
I'm not a kernel developer, so I'm not familiar with GitBisect, but I'll
try GitBisect.

Thanks!
#1036015#45
Date:
2024-08-10 12:19:00 UTC
From:
To:
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore
#1036015#48
Date:
2024-08-10 12:19:00 UTC
From:
To:
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore