public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Mischke <survivor@uni-paderborn.de>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] L2CAP: One failing connection hurts others?
Date: Tue, 14 Sep 2004 17:20:57 +0200	[thread overview]
Message-ID: <41470C59.2050909@uni-paderborn.de> (raw)

Hello!

I'm observing the following issue: I have 3 BT devices. 2 in listening 
state, the 3rd is connecting to both of them repeatingly via L2CAP 
(polling some data). If one of the listening devices is almost of the 
range and makes connection attempts fail, this also causes the 
connection attempts to the other device (which is good in range) to fail 
with errno 16 "Device or ressource busy". The (almost) out of range 
device fails as expected with errno 110 "Connection timed out" (since I 
set a timeout) or 112 "Host is down".

Now my question: Is there a way to circumvent this errno 16, so that I 
can further connect to in range devices even if one device is getting 
out of range and thus producing errors? What makes L2CAP failing with 
errno 16? How can I prevent it?

Regards
Stefan

P.S.: Funnily enough, 110 and 112 are the telephone numbers for police 
and fire department in Germany. I wonder if there's any connection. :)



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2004-09-14 15:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 15:20 Stefan Mischke [this message]
2004-09-14 18:34 ` [Bluez-devel] L2CAP: One failing connection hurts others? Marcel Holtmann
2004-09-14 19:11   ` Stefan Mischke
2004-09-14 19:24     ` Marcel Holtmann
2004-09-14 19:37       ` Stefan Mischke
2004-09-14 19:49         ` Marcel Holtmann
2004-09-14 20:10           ` Stefan Mischke
2004-09-14 21:12             ` Marcel Holtmann
2004-09-14 23:37               ` Stefan Mischke
2004-09-15  7:46                 ` Marcel Holtmann
2004-09-15 14:00                   ` Stefan Mischke
2004-09-15 21:09                     ` Marcel Holtmann
2004-09-15 22:26                       ` Stefan Mischke
2004-09-16 10:30                       ` Stefan Mischke
2004-09-16 10:34                         ` Marcel Holtmann
2004-09-16 10:39                           ` Stefan Mischke
2004-09-16 11:00                             ` Marcel Holtmann
2004-09-16 11:10                               ` Stefan Mischke
2004-09-16 16:41                               ` Stefan Mischke
2004-09-15 20:37                   ` Stefan Mischke
2004-09-15 21:06                     ` Marcel Holtmann
2004-09-15 22:13                       ` Stefan Mischke

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=41470C59.2050909@uni-paderborn.de \
    --to=survivor@uni-paderborn.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox