You are not logged in.

#1 2019-01-10 10:04:55

deisi
Member
Registered: 2015-10-21
Posts: 44

T480 Bluetooth Unreliable

I sometimes have issues with the Bluetooth on my T480. Wen I try to activate it in the gnome system settings, it will just never do it. Instead it will be shown as active, but never actually find anything. A reboot fixes the problem temporary.
Here is a journalctl log of the process:

Jan 10 10:54:18 mtop org.gnome.Shell.Extensions.GSConnect[1411]: fusermount: entry for /run/user/1000/gsconnect/5632a81c39161ef8 not found in /etc/mtab
Jan 10 10:54:19 mtop systemd[1]: Starting Load/Save RF Kill Switch Status...
Jan 10 10:54:19 mtop systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 10 10:54:19 mtop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 10:54:19 mtop kernel: audit: type=1130 audit(1547114059.989:3843): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 10:54:20 mtop kernel: usb 1-7: new full-speed USB device number 6 using xhci_hcd
Jan 10 10:54:20 mtop kernel: usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.10
Jan 10 10:54:20 mtop kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 10 10:54:20 mtop kernel: Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
Jan 10 10:54:20 mtop kernel: Bluetooth: hci0: Device revision is 16
Jan 10 10:54:20 mtop kernel: Bluetooth: hci0: Secure boot is enabled
Jan 10 10:54:20 mtop kernel: Bluetooth: hci0: OTP lock is enabled
Jan 10 10:54:20 mtop kernel: Bluetooth: hci0: API lock is enabled
Jan 10 10:54:20 mtop kernel: Bluetooth: hci0: Debug lock is disabled
Jan 10 10:54:20 mtop kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Jan 10 10:54:20 mtop kernel: Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
Jan 10 10:54:20 mtop systemd[1]: Reached target Bluetooth.
Jan 10 10:54:22 mtop kernel: Bluetooth: hci0: Waiting for firmware download to complete
Jan 10 10:54:22 mtop kernel: Bluetooth: hci0: Firmware loaded in 1865429 usecs
Jan 10 10:54:22 mtop kernel: Bluetooth: hci0: Waiting for device to boot
Jan 10 10:54:22 mtop kernel: Bluetooth: hci0: Device booted in 11660 usecs
Jan 10 10:54:22 mtop kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
Jan 10 10:54:22 mtop kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Jan 10 10:54:23 mtop dbus-daemon[661]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.26828' (uid=973 pid=748 comm="/usr/lib/colord-sane ")
Jan 10 10:54:23 mtop dbus-daemon[661]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jan 10 10:54:25 mtop dbus-daemon[661]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.26829' (uid=973 pid=748 comm="/usr/lib/colord-sane ")
Jan 10 10:54:25 mtop dbus-daemon[661]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jan 10 10:54:25 mtop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 10:54:25 mtop kernel: audit: type=1131 audit(1547114065.952:3844): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Jan 10 10:54:46 mtop systemd[1]: Starting Load/Save RF Kill Switch Status...
Jan 10 10:54:46 mtop systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 10 10:54:46 mtop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 10:54:46 mtop kernel: audit: type=1130 audit(1547114086.176:3845): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 10:54:46 mtop kernel: usb 1-7: USB disconnect, device number 6
Jan 10 10:54:46 mtop systemd[1]: Stopped target Bluetooth.
Jan 10 10:54:48 mtop dbus-daemon[661]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.26832' (uid=973 pid=795 comm="/usr/lib/colord-sane ")
Jan 10 10:54:48 mtop dbus-daemon[661]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jan 10 10:54:50 mtop dbus-daemon[661]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.26833' (uid=973 pid=795 comm="/usr/lib/colord-sane ")
Jan 10 10:54:50 mtop dbus-daemon[661]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jan 10 10:54:51 mtop org.gnome.Shell.desktop[1445]: libinput error: client bug: timer event18 debounce: offset negative (-31ms)
Jan 10 10:54:51 mtop org.gnome.Shell.desktop[1445]: libinput error: client bug: timer event18 debounce short: offset negative (-44ms)
Jan 10 10:54:51 mtop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 10:54:51 mtop kernel: audit: type=1131 audit(1547114091.272:3846): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

I put a blank line where I clicked the bluetooth toggle button again to turn it off. Interesting is, that if I don't turn it off manually, the next time I open bluetooth settings, it will show as off but upon turning it on, nothing happens.

Kernel is

Linux mtop 4.20.0-arch1-1-ARCH #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 x86_64 GNU/Linux

This is my wifi device. I think it also handles bluetooth.

03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)

I also use tlp with default configuration.


This is the journalctl after a reboot with sucesfull activation

Jan 10 11:17:27 mtop systemd[1]: Starting Load/Save RF Kill Switch Status...
Jan 10 11:17:27 mtop systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 10 11:17:27 mtop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 11:17:27 mtop kernel: audit: type=1130 audit(1547115447.087:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 11:17:27 mtop kernel: usb 1-7: new full-speed USB device number 4 using xhci_hcd
Jan 10 11:17:27 mtop kernel: usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.10
Jan 10 11:17:27 mtop kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 10 11:17:27 mtop kernel: Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
Jan 10 11:17:27 mtop kernel: Bluetooth: hci0: Device revision is 16
Jan 10 11:17:27 mtop kernel: Bluetooth: hci0: Secure boot is enabled
Jan 10 11:17:27 mtop kernel: Bluetooth: hci0: OTP lock is enabled
Jan 10 11:17:27 mtop kernel: Bluetooth: hci0: API lock is enabled
Jan 10 11:17:27 mtop kernel: Bluetooth: hci0: Debug lock is disabled
Jan 10 11:17:27 mtop kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Jan 10 11:17:27 mtop kernel: Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
Jan 10 11:17:28 mtop systemd[1]: Reached target Bluetooth.
Jan 10 11:17:29 mtop kernel: Bluetooth: hci0: Waiting for firmware download to complete
Jan 10 11:17:29 mtop kernel: Bluetooth: hci0: Firmware loaded in 1929135 usecs
Jan 10 11:17:29 mtop kernel: Bluetooth: hci0: Waiting for device to boot
Jan 10 11:17:29 mtop kernel: Bluetooth: hci0: Device booted in 11872 usecs
Jan 10 11:17:29 mtop kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
Jan 10 11:17:29 mtop kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Jan 10 11:17:29 mtop kernel: Bluetooth: RFCOMM TTY layer initialized
Jan 10 11:17:29 mtop kernel: Bluetooth: RFCOMM socket layer initialized
Jan 10 11:17:29 mtop kernel: Bluetooth: RFCOMM ver 1.11
Jan 10 11:17:29 mtop NetworkManager[773]: <info>  [1547115449.5449] bluez5: NAP: added interface 48:A4:72:DC:26:D3
Jan 10 11:17:29 mtop bluetoothd[771]: Endpoint registered: sender=:1.136 path=/MediaEndpoint/A2DPSource
Jan 10 11:17:29 mtop bluetoothd[771]: Endpoint registered: sender=:1.136 path=/MediaEndpoint/A2DPSink
Jan 10 11:17:29 mtop NetworkManager[773]: <info>  [1547115449.5829] keyfile: add connection /var/run/NetworkManager/system-connections/OnePlus 5T Network.nmconnection (07e9136f-b127-45dc-8273-df68c75829d8,"OnePlus 5T Network")
Jan 10 11:17:29 mtop NetworkManager[773]: <info>  [1547115449.5851] bluez: BT device OnePlus 5T (94:65:2D:C3:61:E1) added (DUN NAP)
Jan 10 11:17:29 mtop NetworkManager[773]: <info>  [1547115449.5861] manager: (94:65:2D:C3:61:E1): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/4)
Jan 10 11:17:29 mtop NetworkManager[773]: <info>  [1547115449.5873] device (94:65:2D:C3:61:E1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 10 11:17:29 mtop NetworkManager[773]: <info>  [1547115449.6282] device (94:65:2D:C3:61:E1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 10 11:17:29 mtop geoclue[1470]: Service not used for 60 seconds. Shutting down..
Jan 10 11:17:29 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 11:17:30 mtop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 11:17:30 mtop kernel: audit: type=1131 audit(1547115450.010:72): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 11:17:30 mtop dbus-daemon[772]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.336' (uid=973 pid=2096 comm="/usr/lib/colord-sane ")
Jan 10 11:17:30 mtop dbus-daemon[772]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jan 10 11:17:32 mtop dbus-daemon[772]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.337' (uid=973 pid=2096 comm="/usr/lib/colord-sane ")
Jan 10 11:17:32 mtop dbus-daemon[772]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jan 10 11:17:33 mtop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 11:17:33 mtop kernel: audit: type=1131 audit(1547115453.030:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

It does not seem to be related with suspend. I quickly tested by suspending the pc once with bluetooth on and once with Bluetooth off. After both cases Bluetooth was still working.

Last edited by deisi (2019-01-10 10:31:11)

Offline

#2 2019-01-11 20:27:36

deisi
Member
Registered: 2015-10-21
Posts: 44

Re: T480 Bluetooth Unreliable

Currently the laptop is running since yesterday and I don't see this issue yet. In the meantime I searched my logs a little more and found these kind of events:

Jan 10 19:25:10 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:25:26 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:25:42 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:25:58 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:26:15 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:26:31 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:26:47 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:27:03 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:27:19 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:27:35 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
Jan 10 19:27:51 mtop kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)

and a lot more of them. Could this be related? Any Idea where else I could look/report?

Offline

Board footer

Powered by FluxBB