Al Cho changed bug 1163025
What Removed Added
Flags   needinfo?(msuchanek@suse.com)

Comment # 13 on bug 1163025 from
(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:openSUSE-15.1/kernel-default/standard


You are receiving this mail because: