From: Shiloh Heurich <shiloh@comtechmobile.com>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Ultra/160 SCSI
Date: Mon, 11 Dec 2000 11:39:58 -0500 [thread overview]
Message-ID: <B65A6D8D.4932%shiloh@ comtechmobile.com> (raw)
In-Reply-To: <200012110559.XAA04206@lists.linuxppc.org>
What is the current compatibility status of Linux (either 2.2.18 or 2.4.0)
with Ultra/160 SCSI hardware (both cards and hard drives)?
The question comes about because I am currently running Linux/PPC (Yellow
Dog CS 1.2.1 / Linux 2.4.0-test11 [rsync from penguinppc::linux-pmac-devel])
on a B/W G3/350 with an Adaptec AHA-29160 card and a Quantum Atlas V 9GB
Ultra/160 drive. I have used the same SCSI card with other drives (not
U160, but U2W drives) in the past with no problems; however, I have been
experiencing intermittent SCSI problems with this current setup.
(In case you are wondering, this is an x86 'PC' version of the Adaptec 29160
card. However, my experience has been that the x86 versions of the Adaptec
cards work fine in a PPC, with the exception that you can not boot from a
device on the card, since it does not have Open Firmware support. If my
logic or thinking in this matter is incorrect, please let me know.)
The messages log shows entries as follows:
----------------------------------------------------
Dec 11 10:48:51 stan kernel: scsi : aborting command due to timeout : pid 0,
scsi0, channel 0, id 0, lun 0 0x28 00 00 92 4f 80 00 00 0e 00
Dec 11 10:48:52 stan kernel: SCSI host 0 abort (pid 0) timed out - resetting
Dec 11 10:48:52 stan kernel: SCSI bus is being reset for host 0 channel 0.
Dec 11 10:48:53 stan kernel: SCSI host 0 channel 0 reset (pid 0) timed out -
trying harder
Dec 11 10:48:53 stan kernel: SCSI bus is being reset for host 0 channel 0.
Dec 11 10:48:56 stan kernel: (scsi0:0:0:0) Synchronous at 80.0 Mbyte/sec,
offset 63.
Dec 11 10:49:26 stan kernel: scsi : aborting command due to timeout : pid 0,
scsi0, channel 0, id 0, lun 0 0x2a 00 00 79 04 fe 00 00 02 00
----------------------------------------------------
When the machine starts encountering these errors, I am unable to initiate
disc activity or even run 'ps' on the machine (things start to hang). The
only recourse at that point is to physically reset the machine - not a
pleasant thing to do to a Linux box!
As an aside, you will notice that even though I am using an Ultra/160 card
and drive, the bus speed is given as 80.0 MB/s (although it is still a
pretty fast setup -- hdparm show read/write speeds of 28 MB/s).
Any thoughts?
--
Shiloh Heurich
Senior Software Engineer
Comtech Mobile Datacom Corporation
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-12-11 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200012110559.XAA04206@lists.linuxppc.org>
2000-12-11 16:39 ` Shiloh Heurich [this message]
2000-12-12 6:51 ` Ultra/160 SCSI Timothy A. Seufert
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='B65A6D8D.4932%shiloh@ comtechmobile.com' \
--to=shiloh@comtechmobile.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).