Hi all!
Somehow bluetooth stopped working on my Devuan jessie machines. In february I
set up rfcomm connection from my embedded system via rfcomm to my desktop.
Pairing went smoothly, I set up the rfcomm connetion with
# rfcomm bind 0 00:00:62:81:B4:24 1
$ cat /dev/rfcomm0
and out came the data. Now 4 months and some updates later the very same
hardware is not able to keep/craeate a rfcomm connection.
The used USB BT dongles are:
0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
# uname -a
Linux t61 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64
GNU/Linux
[bluetooth]# paired-devices
Device 00:00:62:81:B4:24 MS_MD-0000000010
[bluetooth]# show
Controller 00:1B:DC:06:32:2B
Name: thinkpad
Alias: thinkpad
Class: 0x00010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0517
Discovering: no
[bluetooth]# info 00:00:62:81:B4:24
Device 00:00:62:81:B4:24
Name: MS_MD-0000000010
Alias: MS_MD-0000000010
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
[bluetooth]# connect 00:00:62:81:B4:24
Attempting to connect to 00:00:62:81:B4:24
[CHG] Device 00:00:62:81:B4:24 Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 00:00:62:81:B4:24 Connected: no
The moment the connection error appears, I get in /var/log/messages:
Jun 23 16:37:53 t61 kernel: [ 1465.300298] CPU: 1 PID: 7399 Comm: kworker/u5:1
Tainted: G W 3.16.0-4-amd64 #1 Debian 3.16.7-ckt25-2
Jun 23 16:37:53 t61 kernel: [ 1465.300303] Hardware name: LENOVO
88986DG/88986DG, BIOS 7LETC9WW (2.29 ) 03/18/2011
Jun 23 16:37:53 t61 kernel: [ 1465.300321] Workqueue: hci0 hci_conn_timeout
[bluetooth]
Jun 23 16:37:53 t61 kernel: [ 1465.300327] 0000000000000000 ffffffff8150e835
0000000000000000 0000000000000009
Jun 23 16:37:53 t61 kernel: [ 1465.300335] ffffffff810677f7 ffff8801363018b8
00000000ffffffff ffff880136301800
Jun 23 16:37:53 t61 kernel: [ 1465.300342] ffff880136ec5100 0000000000000000
ffffffffa05b7c7a ffff8800ba217b80
Jun 23 16:37:53 t61 kernel: [ 1465.300349] Call Trace:
Jun 23 16:37:53 t61 kernel: [ 1465.300364] [<ffffffff8150e835>] ?
dump_stack+0x5d/0x78
Jun 23 16:37:53 t61 kernel: [ 1465.300374] [<ffffffff810677f7>] ?
warn_slowpath_common+0x77/0x90
Jun 23 16:37:53 t61 kernel: [ 1465.300393] [<ffffffffa05b7c7a>] ?
hci_conn_timeout+0x4a/0x280 [bluetooth]
Jun 23 16:37:53 t61 kernel: [ 1465.300402] [<ffffffff810817c2>] ?
process_one_work+0x172/0x420
Jun 23 16:37:53 t61 kernel: [ 1465.300409] [<ffffffff81081e53>] ?
worker_thread+0x113/0x4f0
Jun 23 16:37:53 t61 kernel: [ 1465.300415] [<ffffffff81081d40>] ?
rescuer_thread+0x2d0/0x2d0
Jun 23 16:37:53 t61 kernel: [ 1465.300423] [<ffffffff8108809d>] ?
kthread+0xbd/0xe0
Jun 23 16:37:53 t61 kernel: [ 1465.300431] [<ffffffff81087fe0>] ?
kthread_create_on_node+0x180/0x180
Jun 23 16:37:53 t61 kernel: [ 1465.300439] [<ffffffff81514958>] ?
ret_from_fork+0x58/0x90
Jun 23 16:37:53 t61 kernel: [ 1465.300447] [<ffffffff81087fe0>] ?
kthread_create_on_node+0x180/0x180
Jun 23 16:37:53 t61 kernel: [ 1465.300452] ---[ end trace 206e8915664ac1e5 ]---
Does anybody know what to do about this?
Nik
--
Please do not email me anything that you are not comfortable also sharing with
the NSA.
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
