From: JP Freeley <jpf321@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Can't read local name on hci0: Connection timed out (110)
Date: Tue, 25 Jul 2006 18:15:27 -0400 [thread overview]
Message-ID: <44C697FF.3040702@gmail.com> (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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-07-25 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 22:15 JP Freeley [this message]
2006-07-28 1:55 ` [Bluez-devel] Can't read local name on hci0: Connection timed out (110) Marcel Holtmann
2006-07-28 2:48 ` JP Freeley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C697FF.3040702@gmail.com \
--to=jpf321@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.