From: Eero Volotinen <eero@ping-viini.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Adriaan Penning <a.penning@luon.net>,
Darsen Lu <darsen@micro.ee.nthu.edu.tw>,
Luben Tuikov <luben_tuikov@adaptec.com>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Handling erroneous READ CAPACITY response in sd.c
Date: Sun, 24 Oct 2004 15:34:58 +0300 [thread overview]
Message-ID: <417BA172.40203@ping-viini.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0410201130460.638-100000@ida.rowland.org>
Alan Stern wrote:
> People:
>
> We would like to test a method for determining automatically when the
> capacity value returned by a drive is too high. If this works it means
> that the unusual_devs.h entries for your devices can be removed, and we'll
> never be troubled by similarly broken devices again.
>
> Please try applying the patches below. The first one removes the existing
> unusual_devs entries and the second one includes the code we want to test.
> Test results are written to the system log, and you don't need to turn on
> the usb-storage verbose debugging. In your replies, include the dmesg
> output showing what happens when you plug in or turn on your drives.
Does not work on my machine. It detects disk and then it hangs.
usb 1-4: new high speed USB device using address 3
Initializing USB Mass Storage driver...
usb 1-4: control timeout on ep0in
usb 1-4: string descriptor 0 read error: -71
usb 1-4: string descriptor 0 read error: -71
usb 1-4: string descriptor 0 read error: -71
usb 1-4: string descriptor 0 read error: -71
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb 1-4: string descriptor 0 read error: -71
usb-storage: device found at 3
usb 1-4: string descriptor 0 read error: -71
usb-storage: waiting for device to settle before scanning
inserting floppy driver for 2.6.10-rc1alan
floppy0: no floppy controllers found
Vendor: HDS72808 Model: 0PLAT20 Rev: PF2O
Type: Direct-Access ANSI SCSI revision: 00
sd_read_true_cap: sda: spec behavior
sd_read_format_cap: sda: no media or unformatted media
SCSI device sda: 160836481 512-byte hdwr sectors (82348 MB)
sda: assuming drive cache: write through
sda:SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 160836480
Buffer I/O error on device sda, logical block 160836480
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 160836480
Buffer I/O error on device sda, logical block 160836480
sda1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
usb-storage: device scan complete
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 1
Buffer I/O error on device sda, logical block 1
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 2
Buffer I/O error on device sda, logical block 2
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 3
Buffer I/O error on device sda, logical block 3
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 4
Buffer I/O error on device sda, logical block 4
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 5
Buffer I/O error on device sda, logical block 5
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 6
Buffer I/O error on device sda, logical block 6
usb 1-4: USB disconnect, address 3
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 7
Buffer I/O error on device sda, logical block 7
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 8
Buffer I/O error on device sda, logical block 8
target0:0:0: Illegal state transition <NULL>->cancel
Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1713
--
Eero
next prev parent reply other threads:[~2004-10-24 12:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 19:19 Handling erroneous READ CAPACITY response in sd.c Alan Stern
2004-10-19 20:58 ` Luben Tuikov
2004-10-19 21:52 ` Alan Stern
2004-10-20 12:40 ` Luben Tuikov
2004-10-20 15:48 ` Alan Stern
2004-10-24 12:34 ` Eero Volotinen [this message]
2004-10-25 19:41 ` Alan Stern
2004-10-25 20:27 ` Luben Tuikov
2004-10-25 20:08 ` Luben Tuikov
[not found] ` <417D6123.4060902@ping-viini.org>
2004-10-25 20:55 ` Luben Tuikov
2004-11-05 16:18 ` Alan Stern
2004-11-05 18:06 ` Matthew Dharm
2004-11-05 18:34 ` Alan Stern
2004-11-05 18:44 ` [usb-storage] " Andries Brouwer
2004-11-05 21:38 ` Alan Stern
2004-11-05 21:59 ` Andries Brouwer
2004-11-08 18:55 ` Luben Tuikov
2004-11-08 21:03 ` Alan Stern
2004-11-08 21:35 ` Luben Tuikov
2004-11-08 22:04 ` Matthew Dharm
2004-11-08 22:08 ` Alan Stern
2004-10-20 13:28 ` Luben Tuikov
[not found] <417AFDA5.5080806@micro.ee.nthu.edu.tw>
2004-10-24 17:11 ` Alan Stern
2004-10-25 21:54 ` Darsen
2004-10-26 14:43 ` Alan Stern
[not found] <417F6412.90000@micro.ee.nthu.edu.tw>
2004-10-27 19:11 ` Alan Stern
2004-10-29 14:22 ` Darsen
2004-10-29 16:46 ` Alan Stern
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=417BA172.40203@ping-viini.org \
--to=eero@ping-viini.org \
--cc=a.penning@luon.net \
--cc=darsen@micro.ee.nthu.edu.tw \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).