From: Willem Riede <wriede@riede.org>
To: linux-kernel@vger.kernel.org
Subject: ide-scsi problem in 2.5.44
Date: Tue, 5 Nov 2002 20:25:06 -0500 [thread overview]
Message-ID: <20021106012506.GE3664@linnie.riede.org> (raw)
I realize Linus doesn't like ide-scsi, but while it exists I need it to work
:-)
In 2.5.44 ide-scsi doesn't work with my OnStream DI-30 IDE Tape Drive.
Works fine with 2.4.18 on the same hardware. It's not an osst (the driver
for these devices, which I maintain) problem, the error comes from the
scsi host (ide-scsi).
When I try it, I get the following errors:
Nov 5 17:54:58 fallguy kernel: osst :I: Tape driver with OnStream support
version 0.9.10
Nov 5 17:54:58 fallguy kernel: osst :I: $Id: osst.c,v 1.65 2001/11/11
20:38:56 riede Exp $
Nov 5 17:54:58 fallguy kernel: osst :I: Attached OnStream SC-30 tape at
scsi0, channel 0, id 0, lun 0 as osst0
Nov 5 17:54:58 fallguy kernel: osst :I: Attached OnStream DI-30 tape at
scsi4, channel 0, id 1, lun 0 as osst1
Nov 5 17:55:10 fallguy kernel: osst1:W: Warning 2 (sugg. bt 0x0, driver bt
0x0, host bt 0x0).
Nov 5 17:55:10 fallguy kernel: osst1:I: This warning may be caused by your
scsi controller,
Nov 5 17:55:10 fallguy kernel: osst1:I: it has been reported with some
Buslogic cards.
Nov 5 17:55:10 fallguy kernel: hdc: status error: status=0x50 { DriveReady
SeekComplete }
Nov 5 17:55:10 fallguy kernel: ide-scsi: Strange, packet command initiated
yet DRQ isn't asserted
Nov 5 17:55:10 fallguy kernel: osst1:W: Warning 2 (sugg. bt 0x0, driver bt
0x0, host bt 0x0).
Nov 5 17:55:10 fallguy kernel: osst1:W: Warning 2 (sugg. bt 0x0, driver bt
0x0, host bt 0x0).
Nov 5 17:55:10 fallguy kernel: osst1:I: Device did not become Ready in open
Nov 5 18:08:54 fallguy kernel: osst :I: Unloaded.
Note the "hdc:" and the "ide-scsi:" lines.
Does anyone know what ide-scsi's status is, and what might have gone wrong for
me?
Thanks, Willem Riede.
reply other threads:[~2002-11-06 1:18 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=20021106012506.GE3664@linnie.riede.org \
--to=wriede@riede.org \
--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®