From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] tx submit failed urb c4c6b014 type 3 err -19
Date: Fri, 04 Mar 2005 17:17:25 +0100 [thread overview]
Message-ID: <1109953045.8058.75.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.21.0503031418590.28800-100000@blomma.comm2000.it>
Hi Max,
> > this is weird. The first one is related to sysfs and actually these
> > should all be fixed by now. The others are also not quite clear.
> >
> > How many dongles are you using at the same time? I saw hci2 and hci1 in
> > the logs. What does "hciconfig -a" say about them?
>
> Yes, I'm using three dongles. See:
>
> http://cassandra.comm2000.it/~maxim/pub/bluez-oops/hciconfig.txt
>
> The reason I'm using multiple dongles is that I need to control more than
> one phone, and apparently I'm unable to open concurrent SCO links to
> different phones through the same dongle.
>
> Theoretically, this should be possible, shouldn't it? Nevertheless, if I
> connect through different dongles (by bind'ing each socket to the
> appropriate dongle address), everything works more or less as expected
> (except for occasional oops, and some infrequent errors during SCO
> connect's). If I try to use a single dongle, either not binding the
> sockets, or binding them to BDADDR_ANY, I always get "Too many links" on
> the second SCO connection I try to open. Am I possibly doing something
> wrong?
>
> Besides, warnings very often get logged mentioning SCO handle numbers
> which look bogus to me:
>
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 65023
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 63231
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 65535
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 65280
>
> See here for more messages like the above:
>
> http://cassandra.comm2000.it/~maxim/pub/bluez-oops/log-0.txt
I think the firmware of the dongles is too old. What does lsusb shows
you? Maybe it is possible to update them.
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
prev parent reply other threads:[~2005-03-04 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 16:09 [Bluez-users] tx submit failed urb c4c6b014 type 3 err -19 Max M.
2005-02-28 8:18 ` Marcel Holtmann
2005-03-01 18:05 ` Max M.
2005-03-01 18:45 ` Marcel Holtmann
2005-03-03 14:24 ` Max M.
2005-03-04 2:55 ` Marco Trudel
2005-03-04 16:19 ` Marcel Holtmann
2005-03-04 16:17 ` Marcel Holtmann [this message]
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=1109953045.8058.75.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.