From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] error on connect
Date: Sun, 17 Apr 2005 03:46:03 +0200 [thread overview]
Message-ID: <1113702363.18450.26.camel@pegasus> (raw)
In-Reply-To: <4261BCFB.8040204@gmx.ch>
Hi Marco,
> >>Yes. Broadcom dongles cause the problem.
> >>Actually it's only the slave (listening dongle).
> >
> > what kind of Broadcom dongle is this?
>
> I sent you pretty exactly one week ago the data from two broadcom 1.2
> dongles (ednet and acer). Inform me if you need the informations again.
> both dongles now make the problem...
include them again, because my mailboxes are a little bit bigger ;)
> >>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.
> >
> >
> > Send in the "hcidump -X -V" for it.
>
> I attached a successfull and a failed attemp from the listening acer dongle.
> Hope they are informative...
These dumps gives no information about why you should receive a data
packet with an invalid connection handle. However maybe the change of
the packet types confuses the Broadcom dongle.
With what programs do you tested these things? I must try to reproduce
it reliable.
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
next prev parent reply other threads:[~2005-04-17 1:46 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
2005-04-16 20:09 ` Marcel Holtmann
2005-04-17 1:33 ` Marco Trudel
2005-04-17 1:46 ` Marcel Holtmann [this message]
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=1113702363.18450.26.camel@pegasus \
--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