linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herman Meerlo <herman@service2media.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problems with USB 2.0 hub and ehci_usb/hci_usb
Date: Tue, 21 Feb 2006 12:37:19 +0100	[thread overview]
Message-ID: <43FAFB6F.3040308@service2media.com> (raw)
In-Reply-To: <1140467939.7047.46.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Hi Marcel,

Marcel Holtmann wrote:
> Hi Herman,
>
>   
>> I hope one of you can help me... I am trying to use a USB 2.0 bluetooth 
>> dongle (Belkin F8T012) through a USB 2.0 hub. The problem I have is that 
>> whenever I insert the BT dongle the kernel reports the following error:
>>
>> hci_usb_intr_rx_submit: hci- intr rx submit failed urb df265514 err -28
>>
>> I have seen a conversation in which Marcel participated on the linux 
>> kernel mailing lists which referred to a similar problem, but the 
>> discussion was never really finished so no solution was given (see 
>> http://lkml.org/lkml/2004/8/20/62). The problem seems to appear only 
>> when using the ehci_hcd USB module. Because when I use the uhci_hcd 
>> module (by rmmod ehci_hcd) it works. Does anyone have any idea what the 
>> source of this problem is and how I might be able to solve it?
>>     
>
> and again this seems to be an USB issue and not a Bluetooth issue. Take
> it up with the USB guys and make sure you run the latest 2.6 kernel.
>
> Regards
>
> Marcel
>
>   
You are absolutely right off course. And upgrading the kernel did the 
trick. Sorry for bothering you with this.

Regards,
Herman

[-- Attachment #2: Type: text/html, Size: 1637 bytes --]

      reply	other threads:[~2006-02-21 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 10:44 [Bluez-devel] Problems with USB 2.0 hub and ehci_usb/hci_usb Herman Meerlo
2006-02-20 20:38 ` Marcel Holtmann
2006-02-21 11:37   ` Herman Meerlo [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=43FAFB6F.3040308@service2media.com \
    --to=herman@service2media.com \
    --cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).