[SOLVED] Something is subtly broken, Bluetooth can't connect

[sunset_sergal]

Hello world! First time posting in the forums but I've been using Gentoo for years now.

I use PlayStation 3 controllers over Bluetooth on my desktop, and I noticed that after a kernel rebuild, I can no longer use them. They try to connect and immediately disconnect again. PlayStation 4 controllers and a Bose speaker still work fine.

I turned on debugging output for Bluez and got this in daemon.log:

[netfab]

Hi,

Kernel huge regression. Have a look here :
https://bugs.gentoo.org/686758
https://bugzilla.kernel.org/show_bug.cgi?id=203643

[Ant P.]

Between May 8 and now, did you switch to GCC 9.1? Try the older one.

[sunset_sergal]

Thank you both for replying!

Ant P: I did try an older GCC but it didn't help. And the kernel that worked was also built with GCC 9.1 so I didn't think that was the problem.

netfab: I looked at the pages you linked and ended up applying the RFC patch from the kernel mailing list to =sys-kernel/gentoo-sources-5.1.4 which fixed the problem for that kernel. This is good enough for me until the fix is in a released kernel, so I'll see if I can mark this thread solved.

[joy95611]

I got
src/adapter.c:dev_disconnected() Device XX:XX:XX:XX:XX:XX disconnected, reason 3

I use gdb to digger into bluez, got below callstack

(gdb) bt
#0 dev_disconnected (adapter=0x1ac59c8, addr=0x1ac346e, reason=0 '\000')
at home/joy95611/bluez-5.54/src/adapter.c:7488
#1 0x0009ed04 in disconnected_callback (index=0, length=8, param=0x1ac346e, user_data=0x1ac59c8)
at home/joy95611/bluez-5.54/src/adapter.c:8384
#2 0x000e2534 in notify_handler (data=0x1ac8d00, user_data=0xbeb33934)
at home/joy95611/bluez-5.54/src/shared/mgmt.c:292
#3 0x000e0c84 in queue_foreach (queue=0x1ac1338, function=0xe2480 <notify_handler>, user_data=0xbeb33934)
at home/joy95611/bluez-5.54/src/shared/queue.c:220
#4 0x000e25d0 in process_notify (mgmt=0x1ac3420, event=12, index=0, length=8, param=0x1ac346e)
at home/joy95611/bluez-5.54/src/shared/mgmt.c:304
#5 0x000e28dc in can_read_data (io=0x1ac2d90, user_data=0x1ac3420)
at home/joy95611/bluez-5.54/src/shared/mgmt.c:370
#6 0x000fcc80 in watch_callback (channel=0x1ac1298, cond=G_IO_IN, user_data=0x1ac1350)
at home/joy95611/bluez-5.54/src/shared/io-glib.c:170
#7 0xb6e3eeb0 in g_io_unix_dispatch (source=0x1ac3670, callback=0xfcbe4 <watch_callback>, user_data=0x1ac1350)
at /common/hudson_slaves/sith/workspace/SmartTVOS_TV303_SDK_DailyBuild/DCP_SYS/3rdParty/glib2-2.52/glib/giounix.c:165
#8 0xb6de1e00 in g_main_dispatch (context=0x1abe608)
at /common/hudson_slaves/sith/workspace/SmartTVOS_TV303_SDK_DailyBuild/DCP_SYS/3rdParty/glib2-2.52/glib/gmain.c:3234
#9 0xb6de2f08 in g_main_context_dispatch (context=0x1abe608)
at /common/hudson_slaves/sith/workspace/SmartTVOS_TV303_SDK_DailyBuild/DCP_SYS/3rdParty/glib2-2.52/glib/gmain.c:3887
#10 0xb6de3120 in g_main_context_iterate (context=0x1abe608, block=1, dispatch=1, self=0x1abf400)
at /common/hudson_slaves/sith/workspace/SmartTVOS_TV303_SDK_DailyBuild/DCP_SYS/3rdParty/glib2-2.52/glib/gmain.c:3960
#11 0xb6de3510 in g_main_loop_run (loop=0x1abe700)
at /common/hudson_slaves/sith/workspace/SmartTVOS_TV303_SDK_DailyBuild/DCP_SYS/3rdParty/glib2-2.52/glib/gmain.c:4156
#12 0x000fd384 in mainloop_run () at home/joy95611/bluez-5.54/src/shared/mainloop-glib.c:79
#13 0x000fda9c in mainloop_run_with_signal (func=0x6abe8 <signal_callback>, user_data=0x0)
at home/joy95611/bluez-5.54/src/shared/mainloop-notify.c:201
#14 0x0006b284 in main (argc=1, argv=0xbeb33c24) at home/joy95611/bluez-5.54/src/main.c:770

I saw message is for src/shared/mgmt.c. Thus I think kernel net/bluetooth/mgmt block send callback to disconnect BT.

Thus I find I forget to run below command:
btmgmt power off && btmgmt le on && btmgmt bredr off && btmgmt power on

After add this command, issue is resolved.