From: Itai Nahshon <nahshon@actcom.co.il>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: USB-Storage in 2.4.19-pre
Date: Thu, 14 Mar 2002 16:32:09 +0200 [thread overview]
Message-ID: <200203141432.g2EEWL628078@lmail.actcom.co.il> (raw)
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:
Mar 14 13:41:06 itai kernel: hub.c: USB new device connect on bus1/2, assigned device number 2
Mar 14 13:41:06 itai kernel: usb-uhci.c: interrupt, status 2, frame# 673
Mar 14 13:41:06 itai kernel: usb.c: USB device not responding, giving up (error=-84)
Mar 14 13:41:09 itai kernel: hub.c: USB new device connect on bus1/2, assigned device number 3
Mar 14 13:41:09 itai kernel: usb.c: USB device not responding, giving up (error=-84)
Switching back to 2.4.19-pre1 - It looks like the disk is reported too early. The Vendor-Model-Rev
fields are still empty. (Is it just cosmetics or a real problem?)
Mar 14 15:02:19 itai kernel: hub.c: USB new device connect on bus1/2, assigned device number 3
Mar 14 15:02:19 itai kernel: usb.c: USB device 3 (vend/prod 0x4e6/0x1) is not claimed by any active driver.
Mar 14 15:02:19 itai kernel: Initializing USB Mass Storage driver...
Mar 14 15:02:19 itai kernel: usb.c: registered new driver usb-storage
Mar 14 15:02:19 itai kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Mar 14 15:02:19 itai kernel: Vendor: Model: Rev:
Mar 14 15:02:19 itai kernel: Type: Direct-Access ANSI SCSI revision: 02
Mar 14 15:02:19 itai kernel: Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
Mar 14 15:02:20 itai kernel: SCSI device sdb: 33750865 512-byte hdwr sectors (17280 MB)
Mar 14 15:02:20 itai kernel: sdb: sdb1 sdb2 sdb4 < sdb5 >
Mar 14 15:02:20 itai kernel: USB Mass Storage support registered.
And from /proc/scsi/scsi:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: Maxtor 9 Model: 1728D8 Rev: GAS5
Type: Direct-Access ANSI SCSI revision: 02
-- Itai
next reply other threads:[~2002-03-14 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 14:32 Itai Nahshon [this message]
2002-03-14 21:25 ` Greg KH
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=200203141432.g2EEWL628078@lmail.actcom.co.il \
--to=nahshon@actcom.co.il \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®