http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c2 Al Cho changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek@suse.com Flags| |needinfo?(msuchanek@suse.co | |m) --- Comment #2 from Al Cho --- (In reply to Michal Suchanek from comment #1)

[Trust DONA]# info Device 5E:FD:E8:25:D8:87 (public) Name: Trust DONA Alias: Trust DONA Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)

Would you please attach more details of lspci or lsusb? and also use btmon to log from paring , connection and disconnects ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c4 --- Comment #4 from Michal Suchanek --- Created attachment 829679 --> http://bugzilla.suse.com/attachment.cgi?id=829679&action=edit lsusb -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c6 --- Comment #6 from Michal Suchanek --- Created attachment 829681 --> http://bugzilla.suse.com/attachment.cgi?id=829681&action=edit btmon log from headset connect -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c7 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msuchanek@suse.co | |m) | --- Comment #7 from Michal Suchanek --- Note: when headset is powered on it connects and immediately disconnects. It can be connected by hand. The device is trusted. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c9 --- Comment #9 from Al Cho --- (In reply to Michal Suchanek from comment #5)

Created attachment 829680 [details] btmon log from headset poweron

Would you please also attached the log from systemd log (journalctl) with debug mode for bluetoothd "#/usr/lib/bluetooth/bluetoothd -d" ? (If possible, please also attach log from headset connect) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c11 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msuchanek@suse.co | |m) | --- Comment #11 from Michal Suchanek --- (In reply to Al Cho from comment #8)

(In reply to Michal Suchanek from comment #7)

...

Note: when headset is powered on it connects and immediately disconnects. It can be connected by hand. The device is trusted.

So, do you mean the description of bluetooth device connected and disconnect immediately is during "bluetooth device power on" ? It's not during pairing and connecting , right ?

If so , may I know the "Trust DONA" type ? As says in the log. "Trust DONA" is Trust Dona Bluetooth Headset. and do you have any other headset to try the same trust paring, power on and connect ? ARCTIC P604

You can see both in the log. It should show certain delay when connecting the Trust headset because it won't connect automatically, must be connected by hand with bluetoothctl. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c13 Al Cho changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(msuchanek@suse.co | |m) --- Comment #13 from Al Cho --- (In reply to Michal Suchanek from comment #11)

(In reply to Al Cho from comment #8)

...

(In reply to Michal Suchanek from comment #7)

...

Note: when headset is powered on it connects and immediately disconnects. It can be connected by hand. The device is trusted.

So, do you mean the description of bluetooth device connected and disconnect immediately is during "bluetooth device power on" ? It's not during pairing and connecting , right ?

If so , may I know the "Trust DONA" type ? As says in the log. "Trust DONA" is Trust Dona Bluetooth Headset. and do you have any other headset to try the same trust paring, power on and connect ? ARCTIC P604

You can see both in the log. It should show certain delay when connecting the Trust headset because it won't connect automatically, must be connected by hand with bluetoothctl.

I think bluetooth device connect and immediately disconnect by some reason. In your poweron.log: < HCI Command: Disconnect (0x01|0x0006) plen 3 #23 [hci0] 15.660937 Handle: 12 Reason: Remote User Terminated Connection (0x13)

HCI Event: Command Status (0x0f) plen 4 #24 [hci0] 15.661445 Disconnect (0x01|0x0006) ncmd 1 Status: Success (0x00) HCI Event: Disconnect Complete (0x05) plen 4 #25 [hci0] 15.752460 Status: Success (0x00) Handle: 12 Reason: Connection Terminated By Local Host (0x16)

and in bluetooth spec: 1.REMOTE USER TERMINATED CONNECTION (0x13) The Remote User Terminated Connection error code indicates that the user on the remote device terminated the connection. 2. CONNECTION TERMINATED BY LOCAL HOST (0x16) The Connection Terminated By Local Host error code indicates that the local device terminated the connection. It's not really clearly reason for us, and there are no more information by blueZ daemon. So I think that may be some reason in kernel bluetooth driver, Would you please use #echo "module bluetooth +p" > /sys/kernel/debug/dynamic_debug/control ( or add options bluetooth dyndbg to /etc/modprobe.d/50-bluetooth.conf) to record journal log with your headset connection. And please also try my test kernel with your headset and enable bluetooth module dynamic debug. https://build.opensuse.org/package/binaries/home:acho:branches:Kernel:openSU... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c15 --- Comment #15 from Michal Suchanek --- (In reply to Al Cho from comment #13)

And please also try my test kernel with your headset and enable bluetooth module dynamic debug. https://build.opensuse.org/package/binaries/home:acho:branches:Kernel: openSUSE-15.1/kernel-default/standard

That kernel is broken. The last built binaries are from commit c3be355 which is not in the kernel-source repository. Is that the intended revision? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1163025 http://bugzilla.suse.com/show_bug.cgi?id=1163025#c17 --- Comment #17 from Michal Suchanek --- I extracted the debug patch and reapplied it to a new kernel but the headset is at the office which is not accessible due to coronavirus quarantine. -- You are receiving this mail because: You are on the CC list for the bug.