From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, mdharm-kernel@one-eyed-alien.net,
torvalds@osdl.org
Subject: Re: scsi mode sense broken again
Date: Fri, 4 Jul 2003 22:52:21 +0200 (MEST) [thread overview]
Message-ID: <UTC200307042052.h64KqLA16451.aeb@smtp.cwi.nl> (raw)
> I just did some re-testing, and my self-powered Zip250 and Zip750 work.
> The 750 takes a few seconds to initialize, but nothing really bad.
> What Zip do you have that doesn't work?
2.5.72 or patched 2.5.74:
<4>imm: Version 2.05 (for Linux 2.4.0)
<4>imm: Found device at ID 6, Attempting to use EPP 32 bit
<4>imm: Found device at ID 6, Attempting to use SPP
<4>imm: Communication established at 0x378 with ID 6 using SPP
<6>scsi1 : Iomega VPI2 (imm) interface
<5> Vendor: IOMEGA Model: ZIP 100 Rev: P.05
<5> Type: Direct-Access ANSI SCSI revision: 02
<5>SCSI device sda: 196608 512-byte hdwr sectors (101 MB)
<5>sda: Write Protect is off
<5>sda: cache data unavailable
<6> sda: sda4
<5>Attached scsi removable disk sda at scsi1, channel 0, id 6, lun 0
An unpatched 2.5.74 says
<4>IMM: returned SCSI status b8
<4>sda: test WP failed, assume Write Enabled
<3>sda: asking for cache data failed
<5>sda : READ CAPACITY failed.
<4>sda: test WP failed, assume Write Enabled
<3>Buffer I/O error on device sda, logical block 0
<6> sda: unable to read partition table
and no I/O is possible.
Andries
next reply other threads:[~2003-07-04 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 20:52 Andries.Brouwer [this message]
2003-07-04 21:00 ` Matthew Dharm
-- strict thread matches above, loose matches on Subject: below --
2003-07-04 21:25 Andries.Brouwer
2003-07-04 21:08 Andries.Brouwer
2003-07-04 21:09 ` Matthew Dharm
2003-07-03 23:06 Andries.Brouwer
2003-07-04 0:10 ` Matthew Dharm
2003-07-04 19:52 ` Matthew Dharm
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=UTC200307042052.h64KqLA16451.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.net \
--cc=torvalds@osdl.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®