public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Peter Koellner <peter@asgalon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: usb storage device not working anymore in 2.6.17.5 and 2.6.17.6
Date: Tue, 25 Jul 2006 11:57:55 -0700	[thread overview]
Message-ID: <20060725185755.GA9727@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0607221735210.6065@noisydwarf>

On Sat, Jul 22, 2006 at 05:59:40PM +0200, Peter Koellner wrote:
> Hi! I noticed a problem with my usb storage device after upgrading
> from 2.6.17.4:
> 
> 
> problem: After updating the kernel from 2.6.17.4 to .5 and then .6 my 
> usb HDD drive does not work anymore. Any ideas?
> 
> symptoms: on plugging in the HDD, I get the following outpit in dmesg
> with kernel 2.6.17.6:
> 
> usb 4-1.4.1: new full speed USB device using ehci_hcd and address 11
> usb 4-1.4.1: device descriptor read/64, error -32
> usb 4-1.4.1: device descriptor read/64, error -32
> usb 4-1.4.1: new full speed USB device using ehci_hcd and address 12
> usb 4-1.4.1: device descriptor read/64, error -32
> usb 4-1.4.1: device descriptor read/64, error -32
> usb 4-1.4.1: new full speed USB device using ehci_hcd and address 13
> usb 4-1.4.1: device not accepting address 13, error -32
> usb 4-1.4.1: new full speed USB device using ehci_hcd and address 14
> usb 4-1.4.1: device not accepting address 14, error -32

That's really odd.  Can you do a 'git bisect' on the -stable kernel tree
to try to find out the problem that caused this?

Hm, I have a uhci patch around here that might help out, can you test it
out if I send it to you?

thanks,

greg k-h

      reply	other threads:[~2006-07-25 19:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22 15:59 PROBLEM: usb storage device not working anymore in 2.6.17.5 and 2.6.17.6 Peter Koellner
2006-07-25 18:57 ` Greg KH [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=20060725185755.GA9727@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@asgalon.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