Return-Path: Subject: Re: [Bluez-devel] L2CAP: One failing connection hurts others? From: Marcel Holtmann To: Stefan Mischke Cc: BlueZ Mailing List In-Reply-To: <41470C59.2050909@uni-paderborn.de> References: <41470C59.2050909@uni-paderborn.de> Content-Type: text/plain Message-Id: <1095186861.5695.193.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 14 Sep 2004 20:34:21 +0200 Hi Stefan, > 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? run "hcidump -x" as root and show us the problematic parts. What kind of dongles are you using? Do you changed any of hcid.conf settings or do you set the master/rswitch on the listening L2CAP socket? Regards Marcel ------------------------------------------------------- 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