Bug 1616338

[chris@f28h ~]$ hciconfig -a hci0
hci0:	Type: Primary  Bus: USB
	BD Address: 00:C2:C6:F0:52:57  ACL MTU: 1021:4  SCO MTU: 96:6
	UP RUNNING PSCAN 
	RX bytes:647412 acl:32014 sco:0 events:1058 errors:0
	TX bytes:9724 acl:162 sco:0 commands:398 errors:0
	Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH SNIFF 
	Link mode: SLAVE ACCEPT 
	Name: 'f28h.local'
	Class: 0x1c010c
	Service Classes: Rendering, Capturing, Object Transfer
	Device Class: Computer, Laptop
	HCI Version: 4.2 (0x8)  Revision: 0x100
	LMP Version: 4.2 (0x8)  Subversion: 0x100
	Manufacturer: Intel Corp. (2)

[chris@f28h ~]$ bluetoothctl
Agent registered
[mouses]# devices
Device 58:1F:AA:EB:B4:6A mouses
Device 04:52:C7:3E:7D:B3 Bose Color II SoundLink
[mouses]# 


The only relevant device is "mouses", the Bose is a ghost device (no idea where it is)

Created attachment 1476190 [details]
journal

bluetoothd debugging is enabled and is in this journal

The disconnect has no journal entry, but happens at about 9:40:50

The first journal entry related to bluetooth is:

09:41:26 f28h.local bluetoothd[649]: bluetoothd[649]: src/adapter.c:dev_disconnected() Device 58:1F:AA:EB:B4:6A disconnected, reason 1

That's 30 seconds after the disconnect has happened, and the mouse has already started to work again.

Created attachment 1476240 [details]
hcidump

I was running hcidump -t, to see if it would capture more information at the time of the problem. I noticed the mouse was unresponsive at 11:52 but I don't know the seconds and can't really infer it from either the journal or hcidump.

I think it happened about here:

2018-08-15 11:52:16.692255 > ACL data: handle 256 flags 0x02 dlen 19
    L2CAP(d): cid 0x0041 len 15 [psm 0]
2018-08-15 11:52:19.223115 > ACL data: handle 256 flags 0x02 dlen 11
    L2CAP(d): cid 0x0041 len 7 [psm 0]

Except that the loss of use was longer than 3 seconds.

This is also suspicious:

2018-08-15 11:52:24.607478 < HCI Command: Exit Sniff Mode (0x02|0x0004) plen 2
    handle 256
2018-08-15 11:52:24.608605 > HCI Event: Command Status (0x0f) plen 4
    Exit Sniff Mode (0x02|0x0004) status 0x00 ncmd 1
2018-08-15 11:52:24.893554 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 256 packets 1
2018-08-15 11:52:24.903667 > ACL data: handle 256 flags 0x02 dlen 7
    L2CAP(d): cid 0x0040 len 3 [psm 0]
2018-08-15 11:52:24.904187 < ACL data: handle 256 flags 0x00 dlen 6
    L2CAP(d): cid 0x0045 len 2 [psm 0]
2018-08-15 11:52:31.749607 > HCI Event: Mode Change (0x14) plen 6
    status 0x08 handle 256 mode 0x00 interval 0
    Error: Connection Timeout
2018-08-15 11:52:31.750806 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 256 reason 0x08
    Reason: Connection Timeout



And more after that. But I have no idea what it means. I'll attach the journalctl output for this time frame after this.

Created attachment 1476241 [details]
journalctl matching up with comment 3

This goes with the previous hcidump.

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Bluetooth mouse does not work. On the Gnome Desktop the Bluetooth icon flashes only briefly and disappears again. This behavior occurs from kernel vmlinuz-5.0.16-300.fc30.x86_64. I have waited for the new version vmlinuz-5.0.17-300.fc30.x86_64 but it doesn't work either. With version vmlinuz-5.0.14-300.fc30.x86_64 the mouse worked.

 dmesg | grep Logi | grep Mouse
[ 11.359082] input: Logitech Bluetooth Mouse M555b Mouse as /devices/pci0000:00/0000:00:08.1/0000:38:00.3/usb1/1-3/1-3.1/1-3.1:1.0/bluetooth/hci0/hci0:256/0005:046D:B009.0003/input/input15
[ 11.359559] hid-generic 0005:046D:B009.0003: input,hidraw2: BLUETOOTH HID v4.16 Mouse [Logitech Bluetooth Mouse M555b] on dc:8b:28:47:0a:4e

journalctl | grep Bluetooth | grep timeout
May 24 20:08:40 linux.fritz.box kernel: Bluetooth: hci0: command 0x0406 tx timeout
May 24 20:08:52 linux.fritz.box kernel: Bluetooth: hci0: command 0x0419 tx timeout
May 24 20:10:43 linux.fritz.box kernel: Bluetooth: hci0: command 0x0419 tx timeout

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.