public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Andronikos Nedos <nedosa@cs.tcd.ie>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hci_usb bug on 2.6 kernels?
Date: Fri, 27 Aug 2004 13:14:54 +0200	[thread overview]
Message-ID: <1093605294.2581.88.camel@pegasus> (raw)
In-Reply-To: <412EF0FF.4070200@cs.tcd.ie>

Hi Andronikos,

> When I recently migrated to a 2.6 kernel, my TDK USB bluetooth adapter
> stopped working. I could load all the modules fine, but as soon as I
> start hcid I got the following error:
> 
> Aug 12 10:23:33 mulligans hci_usb_intr_rx_submit: hci0 intr rx submit
> failed urb f744f5ec err -28
> 
> I've tried a few of the latest kernels, mainly 2.6.7 and the 2.6.8-rc
> series and the problem remained.
> 
> Yesterday though, I switched my TDK from the USB2 controller to a USB1.1
> ~ controller and it worked.

this is weird, because error code 28 means ENOSPC (No space left on
device) and this is because of a bandwidth problem. May you wanna try to
disable CONFIG_USB_BANDWIDTH and see if it works then. Please report
this problem to the USB mailing list (no cross post), because I can't
really help here.

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-08-27 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27  8:29 [Bluez-devel] hci_usb bug on 2.6 kernels? Andronikos Nedos
2004-08-27 11:14 ` 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=1093605294.2581.88.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=nedosa@cs.tcd.ie \
    /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