Prev: [PATCH] gpiolib: Implement set_debounce for WM831x GPIOs
Next: [PATCH] Staging: cx25821: fix brace coding style issue in cx25821-audio-upstream.c
From: Daniel Mack on 4 Jul 2010 05:20
On Sun, Jul 04, 2010 at 10:03:03AM +0200, Paul Sheer wrote:
> I have a Samsung Story external USB-2.0 1.5TB drive that fails to
> detect as a device in more recent kernel versions. Full kmsg details
> are below. Note that a USB thumb drive works fine on my system.
> Older kernels work fine with the Samsung also. In terms of which
> version of the kernel this stopped working, this I don't know.
>

Can you bisect this problem maybe?

Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Paul Sheer on 4 Jul 2010 06:30

On Sun, 2010-07-04 at 11:11 +0200, Daniel Mack wrote:
> On Sun, Jul 04, 2010 at 10:03:03AM +0200, Paul Sheer wrote:
> > I have a Samsung Story external USB-2.0 1.5TB drive that fails to
> > detect as a device in more recent kernel versions. Full kmsg details
>
> Can you bisect this problem maybe?
>

I would love to but I don't have the time unfortunately.

If someone is interested in fixing this I can send them
a new Samsung Story by mail.

Any takers?

-paul





--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Alan Stern on 4 Jul 2010 09:10
On Sun, 4 Jul 2010, Paul Sheer wrote:

> Hi there,
>
> I have a Samsung Story external USB-2.0 1.5TB drive that fails to
> detect as a device in more recent kernel versions. Full kmsg details
> are below. Note that a USB thumb drive works fine on my system.
> Older kernels work fine with the Samsung also. In terms of which
> version of the kernel this stopped working, this I don't know.

Are you certain this is related to the kernel version and isn't just a
bad USB connection or something of that sort? Have you tried plugging
the Samsung drive into a different computer running a recent kernel?

> My kmsg output when plugging in the drive is as follows:
>
>
> <6>[ 244.624034] usb 1-10: new high speed USB device using ehci_hcd
> and address 3
> <3>[ 244.780033] usb 1-10: device descriptor read/64, error -32
> <3>[ 245.036030] usb 1-10: device descriptor read/64, error -32
> <6>[ 245.252038] usb 1-10: new high speed USB device using ehci_hcd
> and address 4
> <3>[ 245.862496] usb 1-10: unable to read config index 0
> descriptor/start: -71
> <3>[ 245.862615] usb 1-10: chopping to 0 config(s)
> <3>[ 245.979496] usb 1-10: string descriptor 0 read error: -71
> <4>[ 245.980413] usb 1-10: no configuration chosen from 0 choices

These -71 errors are what you typically get when a device stops
responding or the USB signals aren't transmitted properly.

> I will be unsubscribing from these lists after sending this bug
> report, so please contact me directly if you need more info at
> paulsheer at gmail

You know, it's not necessary to subscribe to the mailing lists before
posting messages on them.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] gpiolib: Implement set_debounce for WM831x GPIOs
Next: [PATCH] Staging: cx25821: fix brace coding style issue in cx25821-audio-upstream.c