public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Harald Dunkel <harri@afaics.de>, linux-usb@vger.kernel.org
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3.0.3 + Bluetooth USB Dongle: no success without noapic
Date: Thu, 1 Sep 2011 08:01:21 +0200	[thread overview]
Message-ID: <201109010801.22009.oliver@neukum.org> (raw)
In-Reply-To: <4E5F19CA.7080909@afaics.de>

Am Donnerstag, 1. September 2011, 07:36:10 schrieb Harald Dunkel:
> On 08/28/11 12:07, Oliver Neukum wrote:
> > Am Sonntag, 28. August 2011, 11:49:57 schrieb Harald Dunkel:

Hi,

> >> [   91.589073] usb 2-5: new full speed USB device number 8 using ohci_hcd [   91.709067] usb 2-5: device descriptor read/64, error -62 [   91.930059] usb 2-5: device descriptor read/64, error -62 [   92.144054] usb 2-5: new full speed USB device number 9 using ohci_hcd [   92.264073] usb 2-5:
> >> device descriptor read/64, error -62 [   92.485064] usb 2-5: device descriptor read/64, error -62 [   92.699091] usb 2-5: new full speed USB device number 10 using ohci_hcd [   93.103040] usb 2-5: device not accepting address 10, error -62 [   93.216102] usb 2-5: new full speed USB device
> >> number 11 using ohci_hcd [   93.620038] usb 2-5: device not accepting address 11, error -62 [   93.620072] hub 2-0:1.0: unable to enumerate USB device on port 5
> >>
> >> Booting with noapic fixes this problem.
> >
> > Do any other USB devices work on that OHCI?
> >
> 
> Sorry for the delay.
> 
> It seems that this problem comes up by chance (with or without
> noapic). If I move the dongle to another USB slot then the problem
> is gone. By now the Bluetooth dongle is the only device showing this
> problem.
> 
> Here is the output of lsusb with all devices plugged in and
> working:
> 
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 002: ID 04fc:0c15 Sunplus Technology Co., Ltd SPIF215A SATA bridge
> Bus 001 Device 007: ID 046d:c525 Logitech, Inc. MX Revolution Cordless Mouse
> Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> Bus 001 Device 009: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
> 
> Removing the usb drive or the keyboard doesn't make the bluetooth
> dongle more stable.

Voodoo. Does anybody have any ideas?

	Regards
		Oliver

  reply	other threads:[~2011-09-01  5:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-28  9:49 3.0.3 + Bluetooth USB Dongle: no success without noapic Harald Dunkel
2011-08-28 10:07 ` Oliver Neukum
2011-09-01  5:36   ` Harald Dunkel
2011-09-01  6:01     ` Oliver Neukum [this message]
2011-09-01 14:47       ` Alan Stern

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=201109010801.22009.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=harri@afaics.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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