Linux bluetooth development
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	BlueZ mailing list <bluez-devel@lists.sourceforge.net>,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [BUG] hci_usb + uhci vs. usb-uhci
Date: Mon, 15 Sep 2003 09:20:22 -0700	[thread overview]
Message-ID: <20030915162022.GA14793@bougret.hpl.hp.com> (raw)
In-Reply-To: <20030912183251.G18890@sventech.com>

On Fri, Sep 12, 2003 at 06:32:51PM -0400, Johannes Erdfelt wrote:
> On Fri, Sep 12, 2003, Jean Tourrilhes <jt@bougret.hpl.hp.com> wrote:
> > 	I just spent some time tracking a problem with hci_usb (BlueZ
> > USB driver) and uhci. This happens on 2 different PCs with different
> > hardware and 2.4.X kernels, I describe one here.
> > 
> > UHCI Hardware :
> > 	00:07.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01)
> > BlueTooth hardware :
> > 	HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1 (0x1) LMP Subver: 0x1bb
> > 	Manufacturer: Cambridge Silicon Radio (10)
> > Kernel : 2.4.22 UP
> > 
> > 	What happens :
> > 	Start BNEP session (i.e. TCP/IP over BT). Start intensive TCP
> > app (web download, netperf, X-Window). After a few seconds, on the
> > transmitter the hardware just stops :
> > --------------------------------------------------------
> > < ACL data: handle 0x0029 flags 0x01 dlen 192
> > < ACL data: handle 0x0029 flags 0x01 dlen 192
> > < ACL data: handle 0x0029 flags 0x01 dlen 192
> > < ACL data: handle 0x0029 flags 0x01 dlen 192
> > < ACL data: handle 0x0029 flags 0x01 dlen 192
> > --------------------------------------------------------
> > 	The "Number of Completed Packets" event never comes back. I
> > have to physically unplug the USB dongle to recover. I could not see
> > any error messages in the log, except after a few seconds some BNEP
> > and ACL timeouts (which are expected).
> > 
> > 	I initially though that it was a BlueTooth problem. However,
> > I've never seen it happening with my OHCI hardware on SMP (which is
> > what I normally use). And, if I replace uhci.o with usb-uhci.o on the
> > same hardware, the problem goes away completely.
> > 	So, there is definitely something about uhci.o...
> 
> Did you enable zero packet when you compiled the BT driver?
> 
> JE

	Nope. The compilation of hci_usb was exactly the same for uhci
and for usb-uhci/ohci.

	Jean

      reply	other threads:[~2003-09-15 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12 21:51 [BUG] hci_usb + uhci vs. usb-uhci Jean Tourrilhes
2003-09-12 22:32 ` [Bluez-devel] " Johannes Erdfelt
2003-09-15 16:20   ` Jean Tourrilhes [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=20030915162022.GA14793@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=johannes@erdfelt.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=maxk@qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox