13d3:3362 IMC Networks Atheros AR3012 stops working

Speranskiy · 2016-03-27 06:08:26

Hi guys!
I'm tired. This issue makes my bluetooth controller completely unusable. The problem is it's not just doesn't work. The controller is recognizable by the system but in some time of running connected to some bluetooth device (audio sink) it starts continuously reconnecting to the device. It could take couple of minutes or hours to lock up.

[speranza@mbox ~]$ lsusb|grep Blue
Bus 002 Device 007: ID 13d3:3362 IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter

T:  Bus=02 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=13d3 ProdID=3362 Rev=00.02
S:  Manufacturer=Atheros Communications
S:  Product=Bluetooth USB Host Controller
S:  SerialNumber=Alaska Day 2006
C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

I see that the AR3012 support has been added to the kernel long ago and only thing I've found on the Internet is blacklisting btusb device and modprobing it manually but it doesn't help.
I use bluetoothctl only to eliminate any GUI tools' bugs.
What's going on in bluetoothctl after the lock up is (around 3 minutes log)

[speranza@mbox ~]$ bluetoothctl 
[NEW] Controller 54:27:1E:04:E6:68 mbox [default]
[NEW] Device 88:C6:26:0D:B9:93 Logitech BT Adapter
[CHG] Device 88:C6:26:0D:B9:93 Connected: no
[CHG] Device 88:C6:26:0D:B9:93 Connected: yes
[CHG] Device 88:C6:26:0D:B9:93 Connected: no
[CHG] Device 88:C6:26:0D:B9:93 Connected: yes
[CHG] Device 88:C6:26:0D:B9:93 Connected: no
[CHG] Device 88:C6:26:0D:B9:93 Connected: yes
[CHG] Device 88:C6:26:0D:B9:93 Connected: no
[CHG] Device 88:C6:26:0D:B9:93 Connected: yes
[CHG] Device 88:C6:26:0D:B9:93 Connected: no
[CHG] Device 88:C6:26:0D:B9:93 Connected: yes

Power on/off in bluetoothctl makes the controller connects to the device, so it's fixing the issue (until the next lock up).

[speranza@mbox ~]$ hciconfig
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 54:27:1E:04:E6:68  ACL MTU: 1022:8  SCO MTU: 183:5
	UP RUNNING 
	RX bytes:220172 acl:119 sco:0 events:29152 errors:0
	TX bytes:23789466 acl:28230 sco:0 commands:403 errors:0

[speranza@mbox ~]$ sudo rfkill list
[sudo] password for speranza: 
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: asus-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: asus-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
4: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

[speranza@mbox ~]$ dmesg|grep Bluetooth
[    3.607462] Bluetooth: Core ver 2.21
[    3.607477] Bluetooth: HCI device and connection manager initialized
[    3.607480] Bluetooth: HCI socket layer initialized
[    3.607482] Bluetooth: L2CAP socket layer initialized
[    3.607487] Bluetooth: SCO socket layer initialized
[    4.714480] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.714485] Bluetooth: BNEP filters: protocol multicast
[    4.714492] Bluetooth: BNEP socket layer initialized
[   43.087527] Bluetooth: RFCOMM TTY layer initialized
[   43.087547] Bluetooth: RFCOMM socket layer initialized
[   43.087558] Bluetooth: RFCOMM ver 1.11
[ 1097.075769] Bluetooth: hci0 link tx timeout
[ 1097.075775] Bluetooth: hci0 killing stalled connection 88:c6:26:0d:b9:93

sudo journalctl -u bluetooth.service
Mar 27 07:53:37 mbox bluetoothd[521]: Endpoint unregistered: sender=:1.27 path=/MediaEndpoint/A2DPSource
Mar 27 07:53:37 mbox bluetoothd[521]: Endpoint unregistered: sender=:1.27 path=/MediaEndpoint/A2DPSink
Mar 27 07:53:43 mbox bluetoothd[521]: Failed to obtain handles for "Service Changed" characteristic
Mar 27 07:53:43 mbox bluetoothd[521]: Not enough free handles to register service
Mar 27 07:53:43 mbox bluetoothd[521]: Error adding Link Loss service
Mar 27 07:53:43 mbox bluetoothd[521]: Not enough free handles to register service
Mar 27 07:53:43 mbox bluetoothd[521]: Not enough free handles to register service
Mar 27 07:53:43 mbox bluetoothd[521]: Not enough free handles to register service
Mar 27 07:53:43 mbox bluetoothd[521]: Current Time Service could not be registered
Mar 27 07:53:43 mbox bluetoothd[521]: gatt-time-server: Input/output error (5)
Mar 27 07:53:43 mbox bluetoothd[521]: Not enough free handles to register service
Mar 27 07:53:43 mbox bluetoothd[521]: Not enough free handles to register service
Mar 27 07:53:43 mbox bluetoothd[521]: Sap driver initialization failed.
Mar 27 07:53:43 mbox bluetoothd[521]: sap-server: Operation not permitted (1)
Mar 27 07:53:43 mbox bluetoothd[521]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource
Mar 27 07:53:43 mbox bluetoothd[521]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSink
Mar 27 07:53:47 mbox bluetoothd[521]: /org/bluez/hci0/dev_88_C6_26_0D_B9_93/fd0: fd(21) ready
Mar 27 08:10:48 mbox bluetoothd[521]: No reply to Suspend request

Despite the errors in the journal nothing is adding when it locks up.

[speranza@mbox ~]$ pacman -Qs bluez
local/bluez 5.38-1
    Daemons for the bluetooth protocol stack
local/bluez-firmware 1.2-8
    Firmwares for Broadcom BCM203x and STLC2300 Bluetooth chips
local/bluez-hid2hci 5.38-1
    Put HID proxying bluetooth HCI's into HCI mode
local/bluez-libs 5.38-1
    Deprecated libraries for the bluetooth protocol stack
local/bluez-tools 0.1.38-4
    A set of tools to manage bluetooth devices for linux from the cli
local/bluez-utils 5.38-1
    Development and debugging utilities for the bluetooth protocol stack
local/python-pybluez 0.20-4
    Python wrapper for the BlueZ Bluetooth stack

And the last thing is as far as I remember it didn't do that with gnome-bluetooth and gnome-shell installed (but I'm already not sure)
Please help me to fix this annoying issue!

Last edited by Speranskiy (2016-03-27 06:13:24)

Speranskiy · 2016-03-27 06:12:16

During collecting all these listings just found out that some time it's not the bluetooth controller disconnecting but just the Audio Sink dies. That's probably why I didn't get anything in the journal last time. Maybe the pulseaudio is a culprit?

[Logitech BT Adapter]# info
Device 88:C6:26:0D:B9:93
	Name: Logitech BT Adapter
	Alias: Logitech BT Adapter
	Class: 0x240414
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)

Last edited by Speranskiy (2016-03-27 06:13:38)

Speranskiy · 2016-03-27 06:16:19

The errors in the journal mentioned in the first post appear during

modprobe -r btusb
modprobe btusb

Speranskiy · 2016-04-12 16:36:43

Seems like disabling TLP helped me to have it working. But it works only if I use Blueman. It keeps locking up if I use bare bluetoothctl. Could be there something else disabling USB devices? I'd like to use bluetoothctl only.

asg1448 · 2016-06-28 03:16:09

Hi, have you found any trick yet, how to bring it to order? I have "13d3:3395 IMC Networks" adapter and it keeps dropping bluetooth mouse after 5 minutes of use or so. Reloading bluetooth service fixes the problem for another 5 min. It is very annoying

Speranskiy · 2016-08-05 02:57:06

asg1448 wrote:

Hi, have you found any trick yet, how to bring it to order? I have "13d3:3395 IMC Networks" adapter and it keeps dropping bluetooth mouse after 5 minutes of use or so. Reloading bluetooth service fixes the problem for another 5 min. It is very annoying

Yes, see post #4 here.

Arch Linux

#1 2016-03-27 06:08:26

13d3:3362 IMC Networks Atheros AR3012 stops working

#2 2016-03-27 06:12:16

Re: 13d3:3362 IMC Networks Atheros AR3012 stops working

#3 2016-03-27 06:16:19

Re: 13d3:3362 IMC Networks Atheros AR3012 stops working

#4 2016-04-12 16:36:43

Re: 13d3:3362 IMC Networks Atheros AR3012 stops working

#5 2016-06-28 03:16:09

Re: 13d3:3362 IMC Networks Atheros AR3012 stops working

#6 2016-08-05 02:57:06

Re: 13d3:3362 IMC Networks Atheros AR3012 stops working

Board footer