FS#72786 - On Lenovo T450s DBus reports 'No adapter found' after quick reboot of machine.

Attached to Project: Arch Linux
Opened by kameron ospen (kameron0) - Friday, 19 November 2021, 11:52 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 06 June 2023, 04:14 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: From Linux kernel upgrade 5.15.0 to current kernel version bluetooth manager reports 'No adapter(s) found after quick rebooting the machine. :% bbOnly solution is to cold boot i.e. shutdown and disconnect the power cord for 20 secs and reboot. Problem appears not to be a power management issue. I have been through the kernel downgrades and the last kernel where problem did not occur is 5.14.16. The problem has also occurred occasionally with a USB 3 port; again a cold boot solves this.


Additional info:
* package version(s) Problem kernel versions: 5.15.0 to current; last working version 5.14.16, blueman 1:1.2.11-4
Machine: Lenovo T450s; proprietary Intel Corp. Bluetooth wireless interface. ATTR{vendor}==0x8087, ATTR[device}==0x0a2a

* config and/or log files etc.
journalctl log extract:
'''
Nov 18 22:51:32 archer2 blueman-applet[2113]: blueman-applet 22.51.32 WARNING PluginManager:147 __load_plugin: Not loading PPPSupport because its conflict has higher priority
Nov 18 22:51:32 archer2 dbus-daemon[637]: [system] Activating via systemd: service name='org.blueman.Mechanism' unit='blueman-mechanism.service' requested by ':1.52' (uid=1000 pid=2113 comm="/usr/bin/python /usr/bin/blueman-applet ")
Nov 18 22:51:32 archer2 systemd[1]: Starting Bluetooth management mechanism...
Nov 18 22:51:32 archer2 dbus-daemon[637]: [system] Successfully activated service 'org.blueman.Mechanism'
Nov 18 22:51:32 archer2 systemd[1]: Started Bluetooth management mechanism.
Nov 18 22:51:32 archer2 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 18 22:51:32 archer2 kernel: audit: type=1130 audit(1637275892.258:269): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 18 22:51:32 archer2 blueman-applet[2113]: blueman-applet 22.51.32 WARNING TransferService:213 _make_share_path: Failed to get Download dir from XDG
Nov 18 22:51:32 archer2 blueman-applet[2113]: blueman-applet 22.51.32 WARNING PluginManager:147 __load_plugin: Not loading DhcpClient because its conflict has higher priority
Nov 18 22:51:32 archer2 dbus-daemon[1461]: [session uid=1000 pid=1461] Successfully activated service 'org.blueman.Applet'
Nov 18 22:51:32 archer2 systemd[1439]: Started Bluetooth management applet.
Nov 18 22:51:32 archer2 dbus-daemon[1461]: [session uid=1000 pid=1461] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.23' (uid=1000 pid=2113 comm="/usr/bin/python /usr/bin/blueman-applet ")
Nov 18 22:51:32 archer2 systemd[1439]: Starting Bluetooth OBEX service...
Nov 18 22:51:32 archer2 obexd[2124]: OBEX daemon 5.62
Nov 18 22:51:32 archer2 dbus-daemon[1461]: [session uid=1000 pid=1461] Successfully activated service 'org.bluez.obex'
Nov 18 22:51:32 archer2 systemd[1439]: Started Bluetooth OBEX service.
Nov 18 22:51:32 archer2 blueman-applet[2113]: blueman-applet 22.51.32 WARNING DiscvManager:119 update_menuitems: warning: Adapter is None
Nov 18 22:52:03 archer2 systemd[1]: blueman-mechanism.service: Deactivated successfully.
Nov 18 22:52:03 archer2 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
```
Steps to reproduce: Power on and quick reboot - adapter not detected! Solution: power off and pull out cable, Reconnect latter, then reboot - adapter detected!
This task depends upon

Closed by  Toolybird (Toolybird)
Tuesday, 06 June 2023, 04:14 GMT
Reason for closing:  No response
Additional comments about closing:  Old and stale...and clearly an upstream issue. If still happening, please report upstream to the kernel folks.
Comment by Magnus (DeArchDev) - Sunday, 06 March 2022, 14:46 GMT

Loading...