Bug 907995 - Bluetooth discovery session fails to find discoverable devices
Summary: Bluetooth discovery session fails to find discoverable devices
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 15:57 UTC by Steve Adams
Modified: 2013-09-26 19:26 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-26 19:26:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
gzip tar containing some system diagnostics (dmesg, etc.) (36.90 KB, application/x-compressed-tar)
2013-02-05 15:57 UTC, Steve Adams
no flags Details

Description Steve Adams 2013-02-05 15:57:25 UTC
Created attachment 693457 [details]
gzip tar containing some system diagnostics (dmesg, etc.)

Description of problem:

Bluetooth discovery session fails to find discoverable devices.

Atheros AR9462 combined wifi/bluetooth module on a Dell XPS 15 L521X. Devices are discovered and paired no problem when running Windows.

Version-Release number of selected component (if applicable):

kernel-3.7.5-201.fc18.x86_64
bluez-cups-4.101-5.fc18.x86_64
bluez-libs-4.101-5.fc18.x86_64
bluez-4.101-5.fc18.x86_64
bluez-compat-4.101-5.fc18.x86_64
gnome-bluetooth-3.6.1-2.fc18.x86_64
gnome-bluetooth-libs-3.6.1-2.fc18.x86_64
pulseaudio-module-bluetooth-2.1-5.fc18.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. Set an external bluetooth device to be discoverable
2. Select 'Set up a New Device ...' in gnome-bluetooth applet menu
  
Actual results:

The 'Searching for devices ...' spinner in the 'Bluetooth New Device Setup' dialog spins indefinitely. No devices are found. No errors indicated in logs:

Feb  5 10:48:46 localhost bluetoothd[733]: bluetoothd[733]: Discovery session 0x7f2679f1b9b0 with :1.96 activated
Feb  5 10:48:46 localhost bluetoothd[733]: Discovery session 0x7f2679f1b9b0 with :1.96 activated

Expected results:

New discoverable device should appear in the 'Devices' list on the 'Bluetooth New Device Setup' dialog.

Additional info:

[root@localhost log]# rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

[root@localhost log]# lspci 
08:00.0 Network controller: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)

[root@localhost log]# lsusb
Bus 002 Device 003: ID 0cf3:e003 Atheros Communications, Inc. 

[root@localhost log]# lsmod
ath9k                 145352  0 
ath9k_common           13649  1 ath9k
ath9k_hw              399416  2 ath9k_common,ath9k
ath                    23143  3 ath9k_common,ath9k,ath9k_hw
mac80211              540054  1 ath9k
cfg80211              201717  3 ath,ath9k,mac80211
bluetooth             319586  22 bnep,btusb,rfcomm
rfkill                 21737  6 cfg80211,bluetooth
btusb                  23871  0 

[root@localhost log]# hciconfig
hci0:	Type: BR/EDR  Bus: USB
	BD Address: A4:17:31:0F:F5:3A  ACL MTU: 1022:8  SCO MTU: 183:5
	UP RUNNING PSCAN ISCAN INQUIRY 
	RX bytes:5564 acl:0 sco:0 events:960 errors:0
	TX bytes:6083 acl:0 sco:0 commands:775 errors:0

[root@localhost log]# hcitool inq
Inquiring ...
[root@localhost log]# hcitool scan
Scanning ...

[root@localhost log]# grep -i blue /var/log/messages
Feb  5 09:56:22 localhost kernel: [    7.809332] Bluetooth: Core ver 2.16
Feb  5 09:56:22 localhost kernel: [    7.809348] Bluetooth: HCI device and connection manager initialized
Feb  5 09:56:22 localhost kernel: [    7.809355] Bluetooth: HCI socket layer initialized
Feb  5 09:56:22 localhost kernel: [    7.809357] Bluetooth: L2CAP socket layer initialized
Feb  5 09:56:22 localhost kernel: [    7.809362] Bluetooth: SCO socket layer initialized
Feb  5 09:56:22 localhost bluetoothd[733]: bluetoothd[733]: Starting SDP server
Feb  5 09:56:22 localhost bluetoothd[733]: Starting SDP server
Feb  5 09:56:22 localhost kernel: [    9.081892] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb  5 09:56:22 localhost kernel: [    9.081895] Bluetooth: BNEP filters: protocol multicast
Feb  5 09:56:22 localhost kernel: [    9.081903] Bluetooth: BNEP socket layer initialized
Feb  5 09:56:22 localhost bluetoothd[733]: Bluetooth Management interface initialized
Feb  5 09:56:22 localhost kernel: [    9.087570] Bluetooth: RFCOMM TTY layer initialized
Feb  5 09:56:22 localhost kernel: [    9.087579] Bluetooth: RFCOMM socket layer initialized
Feb  5 09:56:22 localhost kernel: [    9.087580] Bluetooth: RFCOMM ver 1.11
Feb  5 09:56:22 localhost bluetoothd[733]: bluetoothd[733]: Bluetooth Management interface initialized
Feb  5 09:56:22 localhost bluetoothd[733]: bluetoothd[733]: Adapter /org/bluez/733/hci0 has been enabled
Feb  5 09:56:22 localhost bluetoothd[733]: Adapter /org/bluez/733/hci0 has been enabled
Feb  5 09:56:23 localhost systemd[1]: Started Bluetooth service.
Feb  5 09:56:23 localhost systemd[1]: Starting Bluetooth.
Feb  5 09:56:23 localhost systemd[1]: Reached target Bluetooth.
Feb  5 10:12:02 localhost bluetoothd[733]: bluetoothd[733]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/HFPAG
Feb  5 10:12:02 localhost bluetoothd[733]: bluetoothd[733]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/HFPHS
Feb  5 10:12:02 localhost bluetoothd[733]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/HFPAG
Feb  5 10:12:02 localhost bluetoothd[733]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/HFPHS
Feb  5 10:12:02 localhost bluetoothd[733]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource
Feb  5 10:12:02 localhost bluetoothd[733]: bluetoothd[733]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource
Feb  5 10:25:49 localhost bluetoothd[733]: bluetoothd[733]: Discovery session 0x7f2679f1b9b0 with :1.88 activated
Feb  5 10:25:49 localhost bluetoothd[733]: Discovery session 0x7f2679f1b9b0 with :1.88 activated
Feb  5 10:28:43 localhost bluetoothd[733]: bluetoothd[733]: Discovery session 0x7f2679f25440 with :1.90 activated
Feb  5 10:28:43 localhost bluetoothd[733]: Discovery session 0x7f2679f25440 with :1.90 activated
Feb  5 10:48:46 localhost bluetoothd[733]: bluetoothd[733]: Discovery session 0x7f2679f1b9b0 with :1.96 activated
Feb  5 10:48:46 localhost bluetoothd[733]: Discovery session 0x7f2679f1b9b0 with :1.96 activated

Comment 1 Steve Adams 2013-02-06 14:49:49 UTC
Update: picked up latest bluez packages, still unable to discover devices.

Feb 06 10:44:56 Updated: bluez-libs-4.101-6.fc18.x86_64
Feb 06 10:44:56 Updated: bluez-4.101-6.fc18.x86_64
Feb 06 10:44:58 Updated: bluez-compat-4.101-6.fc18.x86_64
Feb 06 10:44:58 Updated: bluez-cups-4.101-6.fc18.x86_64

Comment 2 Teo 2013-06-17 20:14:34 UTC
I have the same problem with kernel 3.9.5-201 64 bit.
But if I boot with and older kernel I have installed 3.9.2-200 it works without any problem.

Comment 3 Teo 2013-06-17 22:14:21 UTC
(In reply to kobe.bbgf from comment #2)
> I have the same problem with kernel 3.9.5-201 64 bit.
> But if I boot with and older kernel I have installed 3.9.2-200 it works
> without any problem.

Now after a reboot and booting with kernel 3.9.5-201 it seems to work, something has change because I've been booting in this kernel almost 3 days without bluetooth working, seems booting in the old kernel has done the trick for me.

Comment 4 Josh Boyer 2013-07-03 17:23:06 UTC
Steve, are you still having this issue with the 3.9 kernel?

Comment 5 Steve Adams 2013-07-03 17:48:48 UTC
Yes Josh, still having the same issue with 3.9.6-200.fc18.x86_64.

I tried booting to an older kernel and then back to the current one as described by kobe.bbgf above, but this did not work for me.

See some more diagostics below and let me know if there is any other info that may help.

Steve

Jul  3 14:35:39 localhost kernel: [    4.046373] Bluetooth: Core ver 2.16
Jul  3 14:35:39 localhost kernel: [    4.046389] Bluetooth: HCI device and connection manager initialized
Jul  3 14:35:39 localhost kernel: [    4.046395] Bluetooth: HCI socket layer initialized
Jul  3 14:35:39 localhost kernel: [    4.046397] Bluetooth: L2CAP socket layer initialized
Jul  3 14:35:39 localhost kernel: [    4.046402] Bluetooth: SCO socket layer initialized
Jul  3 14:35:39 localhost kernel: [    4.266684] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jul  3 14:35:39 localhost kernel: [    4.266687] Bluetooth: BNEP filters: protocol multicast
Jul  3 14:35:39 localhost kernel: [    4.266695] Bluetooth: BNEP socket layer initialized
Jul  3 14:35:39 localhost bluetoothd[713]: Starting SDP server
Jul  3 14:35:39 localhost kernel: [    4.273721] Bluetooth: RFCOMM TTY layer initialized
Jul  3 14:35:39 localhost kernel: [    4.273730] Bluetooth: RFCOMM socket layer initialized
Jul  3 14:35:39 localhost kernel: [    4.273731] Bluetooth: RFCOMM ver 1.11
Jul  3 14:35:39 localhost bluetoothd[713]: Bluetooth Management interface initialized
Jul  3 14:35:39 localhost systemd[1]: Started Bluetooth service.
Jul  3 14:35:39 localhost systemd[1]: Starting Bluetooth.
Jul  3 14:35:39 localhost systemd[1]: Reached target Bluetooth.
Jul  3 14:35:39 localhost bluetoothd[713]: Unknown command complete for opcode 19
Jul  3 14:35:39 localhost bluetoothd[713]: Adapter /org/bluez/713/hci0 has been enabled
Jul  3 14:35:39 localhost bluetoothd[713]: bluetoothd[713]: Bluetooth daemon 4.101
Jul  3 14:35:39 localhost bluetoothd[713]: bluetoothd[713]: Starting SDP server
Jul  3 14:35:39 localhost bluetoothd[713]: bluetoothd[713]: Bluetooth Management interface initialized
Jul  3 14:35:39 localhost bluetoothd[713]: bluetoothd[713]: Unknown command complete for opcode 19
Jul  3 14:35:39 localhost bluetoothd[713]: bluetoothd[713]: Adapter /org/bluez/713/hci0 has been enabled
Jul  3 14:35:51 localhost bluetoothd[713]: bluetoothd[713]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPAG
Jul  3 14:35:51 localhost bluetoothd[713]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPAG
Jul  3 14:35:51 localhost bluetoothd[713]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPHS
Jul  3 14:35:51 localhost bluetoothd[713]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource
Jul  3 14:35:51 localhost bluetoothd[713]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink
Jul  3 14:35:51 localhost bluetoothd[713]: bluetoothd[713]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPHS
Jul  3 14:35:51 localhost bluetoothd[713]: bluetoothd[713]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource
Jul  3 14:35:51 localhost bluetoothd[713]: bluetoothd[713]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink
Jul  3 14:36:42 localhost kernel: [    4.047058] Bluetooth: Core ver 2.16
Jul  3 14:36:42 localhost kernel: [    4.047076] Bluetooth: HCI device and connection manager initialized
Jul  3 14:36:42 localhost kernel: [    4.047083] Bluetooth: HCI socket layer initialized
Jul  3 14:36:42 localhost kernel: [    4.047085] Bluetooth: L2CAP socket layer initialized
Jul  3 14:36:42 localhost kernel: [    4.047091] Bluetooth: SCO socket layer initialized
Jul  3 14:36:42 localhost bluetoothd[725]: Bluetooth daemon 4.101
Jul  3 14:36:42 localhost kernel: [    4.257512] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jul  3 14:36:42 localhost kernel: [    4.257522] Bluetooth: BNEP filters: protocol multicast
Jul  3 14:36:42 localhost kernel: [    4.257529] Bluetooth: BNEP socket layer initialized
Jul  3 14:36:42 localhost bluetoothd[725]: Starting SDP server
Jul  3 14:36:42 localhost bluetoothd[725]: Bluetooth Management interface initialized
Jul  3 14:36:42 localhost bluetoothd[725]: bluetoothd[725]: Bluetooth daemon 4.101
Jul  3 14:36:42 localhost bluetoothd[725]: bluetoothd[725]: Starting SDP server
Jul  3 14:36:42 localhost bluetoothd[725]: bluetoothd[725]: Bluetooth Management interface initialized
Jul  3 14:36:42 localhost kernel: [    4.271857] Bluetooth: RFCOMM TTY layer initialized
Jul  3 14:36:42 localhost kernel: [    4.271866] Bluetooth: RFCOMM socket layer initialized
Jul  3 14:36:42 localhost kernel: [    4.271867] Bluetooth: RFCOMM ver 1.11
Jul  3 14:36:42 localhost systemd[1]: Started Bluetooth service.
Jul  3 14:36:42 localhost systemd[1]: Starting Bluetooth.
Jul  3 14:36:42 localhost systemd[1]: Reached target Bluetooth.
Jul  3 14:36:42 localhost bluetoothd[725]: bluetoothd[725]: Unknown command complete for opcode 19
Jul  3 14:36:42 localhost bluetoothd[725]: Unknown command complete for opcode 19
Jul  3 14:36:42 localhost bluetoothd[725]: Adapter /org/bluez/725/hci0 has been enabled
Jul  3 14:36:42 localhost bluetoothd[725]: bluetoothd[725]: Adapter /org/bluez/725/hci0 has been enabled
Jul  3 14:36:52 localhost bluetoothd[725]: bluetoothd[725]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPAG
Jul  3 14:36:52 localhost bluetoothd[725]: bluetoothd[725]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPHS
Jul  3 14:36:52 localhost bluetoothd[725]: bluetoothd[725]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource
Jul  3 14:36:52 localhost bluetoothd[725]: bluetoothd[725]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink
Jul  3 14:36:52 localhost bluetoothd[725]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPAG
Jul  3 14:36:52 localhost bluetoothd[725]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPHS
Jul  3 14:36:52 localhost bluetoothd[725]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource
Jul  3 14:36:52 localhost bluetoothd[725]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink
Jul  3 14:37:04 localhost bluetoothd[725]: bluetoothd[725]: Discovery session 0x7f06404c87f0 with :1.74 activated
Jul  3 14:37:04 localhost bluetoothd[725]: Discovery session 0x7f06404c87f0 with :1.74 activated

Comment 6 Steve Adams 2013-09-26 19:18:41 UTC
Fixed! Just updated (F18) and I can now connect bluetooth devices. Not sure which package fixed it but latest updates included kernel-3.10.12-100.fc18.x86_64 and many iwl*-firmware-228.61.2.24-25.fc18.noarch packages.

Steve

Comment 7 Josh Boyer 2013-09-26 19:26:17 UTC
Wonderful.  Thanks for letting us know.


Note You need to log in before you can comment on or make changes to this bug.