From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Can't connect RFCOMM channel: Resource temporarily unavailable
Date: Mon, 19 Dec 2005 13:05:04 +0100 [thread overview]
Message-ID: <1134993904.31688.6.camel@localhost> (raw)
In-Reply-To: <20051219120021.91668.qmail@web36101.mail.mud.yahoo.com>
Hi Swathi,
> My headset is in the pairing mode. Now i am getting a
> different set of message for the hcitool info. I tried
> executing this command many times. But still get the
> same message(below one). I no more get the previous
> msg which contained BD address and the Device name.
>
> Output obtained are as below
>
> hcitool info 00:08:C6:3E:54:2C
> ========================================================
> Requesting information ...
> Can't create connection: Connection timed out
> ========================================================
>
> hcidump -X -V
> ========================================================
> HCI sniffer - Bluetooth packet analyzer ver 1.28
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection (0x01|0x0005) plen 13
> bdaddr 00:08:C6:3E:54:2C ptype 0xcc18 rswitch 0x01
> clkoffset 0x0000
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> > HCI Event: Command Status (0x0f) plen 4
> Create Connection (0x01|0x0005) status 0x00 ncmd 1
> > HCI Event: PIN Code Request (0x16) plen 6
> bdaddr 00:08:C6:3E:54:2C
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x22 handle 41 bdaddr 00:08:C6:3E:54:2C
> type ACL encrypt 0x00
> Error: LMP Response Timeout
> =======================================================
make sure that hcid is running. Check the syslog for output about the
PIN helper if it still fails.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-12-19 12:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 3:32 [Bluez-users] Can't connect RFCOMM channel: Resource temporarily unavailable Swathi Mathur80
2005-12-19 8:54 ` Marcel Holtmann
2005-12-19 9:44 ` Swathi Mathur80
2005-12-19 10:00 ` Marcel Holtmann
2005-12-19 10:42 ` Swathi Mathur80
2005-12-19 11:07 ` Marcel Holtmann
2005-12-19 11:41 ` Swathi Mathur80
2005-12-19 11:43 ` Marcel Holtmann
2005-12-19 12:00 ` Swathi Mathur80
2005-12-19 12:05 ` Marcel Holtmann [this message]
2005-12-19 12:32 ` Swathi Mathur80
2005-12-19 12:45 ` Marcel Holtmann
2005-12-19 13:03 ` Swathi Mathur80
2005-12-19 13:39 ` Marcel Holtmann
2005-12-20 10:08 ` Swathi Mathur80
2005-12-20 12:02 ` Marcel Holtmann
2005-12-21 8:41 ` Swathi Mathur80
2005-12-21 11:11 ` Marcel Holtmann
2005-12-22 9:28 ` Swathi Mathur80
2005-12-27 8:39 ` Marcel Holtmann
2005-12-28 11:44 ` Swathi Mathur80
2005-12-28 12:16 ` Marcel Holtmann
2006-01-09 10:46 ` Swathi Mathur80
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=1134993904.31688.6.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).