From: Marcel Holtmann <marcel@holtmann.org>
To: James Cameron <james.cameron@hp.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout
Date: Wed, 30 Jun 2004 14:43:39 +0200 [thread overview]
Message-ID: <1088599419.4540.24.camel@pegasus> (raw)
In-Reply-To: <20040630120249.GH30504@hp.com>
Hi James,
> > I can't give you a definitv answer for that problem, but it seems that
> > some Bluetooth dongles are not working very nice under heavy load. This
> > is actually not a chip problem, because I saw chips working in one
> > dongle and in another one it produces such timeouts.
>
> Thanks. I saw a load correlation before, but not with 2.6.6.
I really think this is buggy hardware in the USB dongle or in the USB
host controller. Maybe it is also only a software problem and related to
the USB subsystem. I don't know.
> > You can of course try to increase the ACL tx timeout and see if it still
> > occurs.
>
> Oh! How can I increase that? I've checked hcitool and hciconfig man
> pages, and found how to change MTU and buffer size.
Forget about that comment. I checked the kernel code and I don't think
that increasing the timeout to more than 45 seconds makes sense.
/* ACL tx timeout must be longer than maximum
* link supervision timeout (40.9 seconds) */
if (!hdev->acl_cnt && (jiffies - hdev->acl_last_tx) > (HZ * 45))
hci_acl_tx_to(hdev);
> > Do all of your dongles use the same Bluetooth chip?
>
> Both dongles were purchased from the same source, and both look
> identical apart from the ba.
>
> I'm not sure how to get the identity of the chip, but hciconfig -a says
> at the end ...
>
> Manufacturer: Cambridge Silicon Radio (10)
If it is CSR based you can try "hciconfig hci0 revision".
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-30 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 11:21 [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout James Cameron
2004-06-30 11:40 ` Marcel Holtmann
2004-06-30 12:02 ` James Cameron
2004-06-30 12:43 ` Marcel Holtmann [this message]
2004-06-30 13:09 ` James Cameron
2004-06-30 13:21 ` 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=1088599419.4540.24.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=james.cameron@hp.com \
/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.