Bug 215776

Summary:	Unable to reconnect Bluetooth keyboard after disconnection
Product:	Drivers	Reporter:	Marco Zaccheria (zacmarco)
Component:	Bluetooth	Assignee:	linux-bluetooth (linux-bluetooth)
Status:	CLOSED DOCUMENTED
Severity:	normal	CC:	aros
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	5.13.0-37	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	attachment-23310-0.html

Description Marco Zaccheria 2022-03-30 10:49:32 UTC

Good morning,

kernel 5.13.0-37.

zacmarco@ZacBuild:~$ uname -a
Linux ZacBuild 5.13.0-37-generic #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

I have a bluetooth keyboard that goes automatically in power save mode after a few minutes IDLE (I think 3). After this happens, a key press is enough to wake the keyboard up again. In these conditions, I am not able to reconnect the keyboard, I see the bluetooth subsystem trying to connect, but it keeps disconnecting immediately, without even a chance of typing a single char.
Whenever this happens, I see the following in the kernel logs:

[ 1004.980840] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 1009.107227] evdi: [I] (card0) Connector state: connected
[ 1009.107297] evdi: [I] (card0) Edid property set

Matter of fact, the only way I have to restore normal functionality is to pair the keyboard again, like it was connected for the first time.

The issue appears in all the following cases:

- I don't use the keyboard for a few minutes (going to power-save mode)
- I do a keyboard power cycle
- I reboot the PC

Looking at existing issues, this seems similar to the following:

https://bugzilla.kernel.org/show_bug.cgi?id=204765

That however has been resolved a couple of years back.

I use this keyboard on a Windows PC as well, and there I don't have any issues (so it should not be a keyboard problem).

Please let me know if you need additional debug information.
Thank you

  Marco

Comment 1 Artem S. Tashkinov 2022-03-30 13:50:38 UTC

Please try something fresh, e.g. 5.17.1.

There's been a ton of commits in the BT stack after 5.13. This kernel is extremely outdated.

Comment 2 Marco Zaccheria 2022-03-30 16:11:56 UTC

Hi Artem,

thanks for the quick reply, the problem I have is that 5.17.1 seems to tricky to get precompiled for my distro (Ubuntu 20.04 LTS), because of unmet dependencies (libssl3).

Being a work PC, I would avoid going through the process of manually compiling the kernel or external packages, or doing a full system upgrade unless strictly necessary (for example, if I'm sure this would resolve my keyboard issue).

Said that, is there anyone in he BT support team that could try such a configuration? To be honest, it seems to be a very common issue out there as there are plenty of forums covering (with no final answer) the same topic, so it doesn't seem strictly related to my current keyboard.

Could you please advice?

Thank you

   Marco

Comment 3 Artem S. Tashkinov 2022-03-30 16:17:06 UTC

> Could you please advice?

Since you're using the Ubuntu Linux kernel, you'll be better served by Ubuntu developers.

https://wiki.ubuntu.com/Kernel/Bugs
https://bugs.launchpad.net/ubuntu/+source/linux/+bugs

This bugzilla is for the vanilla kernel which you can trivially compile from sources if needed.

Kernel developers are very unlikely to help you because they primarily work with the mainline kernel. It's not humanly possible to keep track of billions of kernels by various Linux distros.

Comment 4 newjuerlee 2022-04-08 05:51:46 UTC

Created attachment 300717 [details]
attachment-23310-0.html

help

<bugzilla-daemon@kernel.org> 于2022年3月31日周四 10:51写道：

> https://bugzilla.kernel.org/show_bug.cgi?id=215776
>
> --- Comment #2 from Marco Zaccheria (zacmarco@gmail.com) ---
> Hi Artem,
>
> thanks for the quick reply, the problem I have is that 5.17.1 seems to
> tricky
> to get precompiled for my distro (Ubuntu 20.04 LTS), because of unmet
> dependencies (libssl3).
>
> Being a work PC, I would avoid going through the process of manually
> compiling
> the kernel or external packages, or doing a full system upgrade unless
> strictly
> necessary (for example, if I'm sure this would resolve my keyboard issue).
>
> Said that, is there anyone in he BT support team that could try such a
> configuration? To be honest, it seems to be a very common issue out there
> as
> there are plenty of forums covering (with no final answer) the same topic,
> so
> it doesn't seem strictly related to my current keyboard.
>
> Could you please advice?
>
> Thank you
>
>    Marco
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are the assignee for the bug.