From: Marcel Holtmann <marcel@holtmann.org>
To: Steve Drew <steve.drew@empics.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] Problems connecting to multiple rfcomm sockets
Date: Wed, 27 Oct 2004 18:45:05 +0200 [thread overview]
Message-ID: <1098895505.6730.10.camel@pegasus> (raw)
In-Reply-To: <0DD4EA5DCF754A409C4E182C758C37F38205@tigris.i.empics.co.uk>
Hi Steve,
> At This point running hcitool con shows the following connections
>
> Connections:
> < ACL 00:02:EE:82:D9:29 handle 44 state 1 lm MASTER ENCRYPT
> < ACL 00:0E:6D:1A:9A:3F handle 41 state 1 lm MASTER ENCRYPT
>
> Running hcidump -x gives the output attached in hcidump.txt (hcidump is
> running from just before the 3rd connection is called, and until after
> the error (Host is down) is reported).
the error is a page timeout and you can try to put your other devices
into hold mode before trying to connect the third. Another option is to
increase the page timeout or simple update the firmware to a HCI 18.x
version.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&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:[~2004-10-27 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 16:32 [Bluez-users] Problems connecting to multiple rfcomm sockets Steve Drew
2004-10-27 16:45 ` Marcel Holtmann [this message]
[not found] <0DD4EA5DCF754A409C4E182C758C37F38231@tigris.i.empics.co.uk>
2004-11-04 18:01 ` Marcel Holtmann
2004-11-04 18:15 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 15:42 Steve Drew
2004-10-27 15:49 ` Marcel Holtmann
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=1098895505.6730.10.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=steve.drew@empics.com \
/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