From: Greg KH <greg@kroah.com>
To: Itai Nahshon <nahshon@actcom.co.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB-Storage in 2.4.19-pre
Date: Thu, 14 Mar 2002 13:25:05 -0800 [thread overview]
Message-ID: <20020314212505.GA22263@us.ibm.com> (raw)
In-Reply-To: <200203141432.g2EEWL628078@lmail.actcom.co.il>
In-Reply-To: <200203141432.g2EEWL628078@lmail.actcom.co.il>
On Thu, Mar 14, 2002 at 04:32:09PM +0200, Itai Nahshon wrote:
> I have used usb-storage with stock redhat kernels for some times. That is usable
> with just few problems. Recently I switched to 2.4.17, and then to 2.4.19-pre1.
>
> On the stock redhat kernels (up to the latest update 2.4.9-31) and on 2.4.17 I had to
> umount the disk before shutdown. Normal shutdown did not unmount the disk cleanly.
> It looks like the scsi layer lost access to the physical disk - maybe after unmouting
> of usbdevfs. (even when I unmount the disk I had some scsi errors reported).
>
> This problem was fixed with 2.4.19-pre1.
>
> Now I'm trying the latest changes. 2.4.19-pre2-ac{3.4} and 2.4.19-pre3 and I cannot
> use usb-storage at all. I get all kind of erros similar to these:
<snip>
Can you try either the patch at:
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=101588420909194
Or just renaming your usbmodules binary to something else and see if the
problem goes away?
The USB initialization timing changed between 2.4.19-pre1 and -pre2,
fixing a lot of problems with devices that had previously not worked on
Linux, but worked fine on Windows. Turned out we were wrong on the
timing issues :)
Let me know if this helps or not.
thanks,
greg k-h
next prev parent reply other threads:[~2002-03-14 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 14:32 USB-Storage in 2.4.19-pre Itai Nahshon
2002-03-14 21:25 ` Greg KH [this message]
2002-03-14 23:20 ` Itai Nahshon
2002-03-14 23:26 ` Greg KH
2002-03-15 0:50 ` Itai Nahshon
2002-03-15 18:26 ` Greg KH
2002-03-15 22:23 ` Itai Nahshon
2002-03-16 0:22 ` Itai Nahshon
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=20020314212505.GA22263@us.ibm.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nahshon@actcom.co.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.