public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Zwell <dzwell@gmail.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Tino Keitel <tino.keitel@gmx.de>,
	David Brownell <david-b@pacbell.net>,
	linux-kernel@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: 2.6.23-rc1: USB hard disk broken
Date: Thu, 09 Aug 2007 12:58:49 -0400	[thread overview]
Message-ID: <46BB47C9.3030609@gmail.com> (raw)
In-Reply-To: <200708051746.32439.oliver@neukum.org>

Oliver Neukum wrote:
> Am Sonntag 05 August 2007 schrieb Tino Keitel:
>> On Thu, Jul 26, 2007 at 10:06:40 +0200, Oliver Neukum wrote:
>>> Am Mittwoch 25 Juli 2007 schrieb Tino Keitel:
>>>> On Wed, Jul 25, 2007 at 10:24:36 +0200, Oliver Neukum wrote:
>>>>> Am Mittwoch 25 Juli 2007 schrieb Tino Keitel:
>>>>>> Hi,
>>>>>>
>>>>>> I just tried 2.6.23-rc1 and shortly after the boot my external USB hard
>>>>>> disk went mad.
>>>> [...]
>>>>
>>>>> Please recompile with CONFIG_USB_DEBUG set.
>>>>>
>> I tried again -rc1 without USB_DEBUG, and was able to reproduce the
>> bug 2 times. At the second time, the kernel log shows this:
>>
>> 2007-08-05_10:30:27.75572 kern.err: ehci_hcd 0000:00:1d.7: dev 6 ep1in scatterli
>> st error 0/-121
>> 2007-08-05_10:30:27.86576 kern.info: usb 1-6: reset high speed USB device using ehci_hcd and address 5
>> 2007-08-05_10:30:55.95293 kern.info: usb 1-6: USB disconnect, address 5
>> 2007-08-05_10:30:55.95300 kern.err: ehci_hcd 0000:00:1d.7: dev 6 ep1in scatterlist error -108/-108
> 
> David, does this error say anything to you?
> 
> 	Regards
> 		Oliver

Hi,

I just completed a git bisect, and commit 
8dfe4b14869fd185ca25ee88b02ada58a3005eaf was the commit that introduced 
this problem. This is "usb-storage: implement autosuspend". I don't 
think there have been many changes in drivers/usb since I last verified 
this problem, so I'm pretty sure this is still happening in the latest 
kernel.

The first thing I am going to do is pull the latest sources, attempt to 
revert this patch, and see whether the kernel compiles and works 
properly with my USB hard drive. Please let me know of anything I can do 
to help.

Dan

  parent reply	other threads:[~2007-08-09 17:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25  7:23 2.6.23-rc1: USB hard disk broken Tino Keitel
2007-07-25  8:24 ` Oliver Neukum
2007-07-25 18:13   ` Tino Keitel
2007-07-26  8:06     ` Oliver Neukum
2007-08-05 11:09       ` Tino Keitel
2007-08-05 11:41         ` Tino Keitel
2007-08-05 15:46         ` Oliver Neukum
2007-08-05 19:11           ` David Brownell
2007-08-09 16:58           ` Dan Zwell [this message]
2007-08-09 20:00             ` Alan Stern
2007-08-09 20:25               ` Tino Keitel
2007-08-09 22:20               ` Dan Zwell
2007-08-10 14:18                 ` Alan Stern
2007-08-10 20:30                   ` Dan Zwell
2007-08-10 20:43                     ` Alan Stern
2007-09-12 21:57                     ` 2.6.23-rc1: USB hard disk broken (REGRESSION) Mark Lord
2007-09-12 22:40                       ` Mark Lord

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=46BB47C9.3030609@gmail.com \
    --to=dzwell@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tino.keitel@gmx.de \
    /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