Skip to contentSkip to conversation

Can't read local name on hci0: Connection timed out (110)

Bluez-devel JP Freeley 2 participants 3 messages Jul 25, 2006 – Jul 28, 2006 Bluetooth drivers

lore
Share & tools
lore

JP Freeley

author
#0 lore raw

OK.. so I built from source 3.1 source last night and everything was going well.

Today I come to find this pesky little error:
% hciconfig -a
......
before REOBOOT
Can't read local name on hci0: Out of available memory space (or
something close to that)
after REBOOT:
Can't read local name on hci0: Connection timed out (110)

ERROR ON CONSOLE:
hci_cmd_task: hci0 command tx timeout

RESULTS OF hcidump -X -V:
HCI sniffer - Bluetooth packet analyzer ver 1.31
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Read Local Name (0x03|0x0014) plen 0

So I unplugged/replugged the USB dongle

usb.c: USB disconnect on device 00:0f.4-1 address 2 hub.c: new USB device 00:0f.4-1, assigned address 3

and NOW everything is working fine again.

Can anyone shed any light on this?

Thanks,

jpf

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

maintainer
#1 lore raw

Hi,

Quoted 21 lines

OK.. so I built from source 3.1 source last night and everything was going well.

Today I come to find this pesky little error:
% hciconfig -a
......
before REOBOOT
Can't read local name on hci0: Out of available memory space (or
something close to that)
after REBOOT:
Can't read local name on hci0: Connection timed out (110)

ERROR ON CONSOLE:
hci_cmd_task: hci0 command tx timeout

RESULTS OF hcidump -X -V:
HCI sniffer - Bluetooth packet analyzer ver 1.31
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Read Local Name (0x03|0x0014) plen 0

Quoted 8 lines

So I unplugged/replugged the USB dongle

usb.c: USB disconnect on device 00:0f.4-1 address 2 hub.c: new USB device 00:0f.4-1, assigned address 3

and NOW everything is working fine again.

Can anyone shed any light on this?

looks like a strange and broken adapter (what was "hciconfig -a" saying again) or simply a bad day.

Regards

Marcel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

author
#2 lore raw

Everything seems dandy right now. I re-started everything with a completely clean install of debian sid. (Which now has the new bluez-utils 3.1-3)

I will try to not bother anyone again. Seems like it was my unkempt distro install.

Thanks,

jpf

Quoted 42 lines · Marcel Holtmann

Hi,

Quoted 20 lines

OK.. so I built from source 3.1 source last night and everything was going well.

Today I come to find this pesky little error:
% hciconfig -a
......
before REOBOOT
Can't read local name on hci0: Out of available memory space (or
something close to that)
after REBOOT:
Can't read local name on hci0: Connection timed out (110)

ERROR ON CONSOLE:
hci_cmd_task: hci0 command tx timeout

RESULTS OF hcidump -X -V:
HCI sniffer - Bluetooth packet analyzer ver 1.31
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Read Local Name (0x03|0x0014) plen 0

Quoted 9 lines

So I unplugged/replugged the USB dongle

usb.c: USB disconnect on device 00:0f.4-1 address 2 hub.c: new USB device 00:0f.4-1, assigned address 3

and NOW everything is working fine again.

Can anyone shed any light on this?

looks like a strange and broken adapter (what was "hciconfig -a" saying again) or simply a bad day.

Regards

Marcel

Quoted 11 lines

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel