lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 25 Jul 2006 11:57:55 -0700
From:	Greg KH <greg@...ah.com>
To:	Peter Koellner <peter@...alon.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: usb storage device not working anymore in 2.6.17.5 and 2.6.17.6

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ