From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] error on connect
Date: Sat, 16 Apr 2005 21:07:33 +0200 [thread overview]
Message-ID: <42616275.1090103@gmx.ch> (raw)
In-Reply-To: <1113607202.16433.42.camel@pegasus>
Hello Marcel
Yes. Broadcom dongles cause the problem.
Actually it's only the slave (listening dongle).
I tested all combinations with a minimal slave and master (only
connects/accept connection and quit directly again).
the master (connecting one) doesn't care, csr and broadcom worked fine.
but the listening one gives the mentioned error (on more than 50% of the
tries) I tried with a acer and ednet broadcom dongle.
A csr works just perfectly fine...
after the error, the dongle keeps waiting for a slave but won't access any
more connections. so, basically the dongle is completly freezed.
can I do something against it?
regards
Marco
Marcel Holtmann wrote:
> Hi Marco,
>
>
>>When I connect from a pc to another (both running bluez, own programs), I
>>get sometimes this error:
>>hci_acldata_packet: hci0 ACL packet for unknown connection handle 6
>>
>>I can't reproduce it. sometimes it happen, sometimes not.
>>If the error occures, the connection breaks down else it works fine...
>>
>>What means this error?
>
>
> it actually means what it says. You receive a data packet for a closed
> connection. What manufacturer is it? Is is not CSR.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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-04-16 19:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 17:52 [Bluez-users] error on connect Marco Trudel
2005-04-15 23:20 ` Marcel Holtmann
2005-04-16 19:07 ` Marco Trudel [this message]
2005-04-16 20:09 ` Marcel Holtmann
2005-04-17 1:33 ` Marco Trudel
2005-04-17 1:46 ` Marcel Holtmann
2005-04-17 10:17 ` Marco Trudel
2005-04-18 18:13 ` Marco Trudel
2005-04-18 18:41 ` Marcel Holtmann
2005-04-19 14:48 ` Marco Trudel
2005-04-19 15:13 ` Marcel Holtmann
2005-04-19 15:24 ` Marco Trudel
2005-04-19 15:47 ` Marcel Holtmann
2005-04-19 16:00 ` Marco Trudel
2005-04-19 16:13 ` Marcel Holtmann
2005-04-19 16:32 ` Marco Trudel
2005-04-19 16:51 ` Marcel Holtmann
2005-04-19 22:11 ` Marco Trudel
2005-04-19 22:32 ` Marcel Holtmann
2005-04-20 12:17 ` Marco Trudel
2005-04-20 12:32 ` Marcel Holtmann
2005-04-20 12:44 ` Marco Trudel
2005-04-24 12:53 ` Marco Trudel
2005-04-24 14:48 ` 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=42616275.1090103@gmx.ch \
--to=mtrudel@gmx.ch \
--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).