From: "John William" <jw2357@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: TMSCSIM module bug in 2.2.19?
Date: Sun, 02 Sep 2001 21:14:58 [thread overview]
Message-ID: <F22vtiy4jaxeQthTQ5n00005fc3@hotmail.com> (raw)
While playing around with the tmscsim.o driver included with 2.2.19, I have
the following problem.
One of my drives (Seagate Hawk) does not properly negotiate SYNC with the
driver on boot up. After the machine is booted, I have to issue an INQUIRY
command to the tmscsim driver to get it to recognize that the drive is SYNC
capable.
Today, I noticed that every time I issue the INQUIRY command (with a 'echo
"INQUIRY 0" > /proc/scsi/tmscsim/0") I get an error. Doing this on an
otherwise quiet machine (no other processes acessing the disk) gives me the
following:
Sep 2 16:13:54 cx kernel: DC390: Issue INQUIRY command to Dev(Idx)
0 SCSI ID 0 LUN 0
Sep 2 16:13:54 cx kernel: DC390: Queue INQUIRY command to dev ID 00
LUN 00
Sep 2 16:13:54 cx kernel: SCSI disk error : host 0 channel 0 id 0 lu
n 0 return code = 8000000
Sep 2 16:13:54 cx kernel: [valid=0] Info fld=0x0, Current sd08:06: s
ense key Aborted Command
Sep 2 16:13:54 cx kernel: Additional sense indicates Overlapped comm
ands attempted
Sep 2 16:13:54 cx kernel: scsidisk I/O error: dev 08:06, sector 3714
The sector number is not the same every time, but appears to be some sort of
remnant of the last disk access before the INQUIRY command was run. This is
repeatable on my machine (and, I suspect, may be why the module doesn't
properly negotiate SYNC on boot-up).
The interesting point is that even with this (apparent) failure, the driver
correctly sets the SYNC attribute for the drive.
This is on a stock 2.2.19 machine, i386 SMP (dual Pentium).
Any ideas?
- John
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
reply other threads:[~2001-09-02 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=F22vtiy4jaxeQthTQ5n00005fc3@hotmail.com \
--to=jw2357@hotmail.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®