From: Philip Hands <phil@hands.com>
To: "Gérard Roudier" <groudier@free.fr>
Cc: linux-scsi@vger.kernel.org
Subject: Re: need help diagnosing sym53c1010-33/Fujitstu MAN3367MP/raid1 lockups
Date: 09 Jul 2002 10:32:44 +0100 [thread overview]
Message-ID: <1026207164.10874.8402.camel@palm> (raw)
In-Reply-To: <20020702035227.G3415-100000@localhost.my.domain>
[-- Attachment #1: Type: text/plain, Size: 1798 bytes --]
On Tue, 2002-07-02 at 03:00, Gérard Roudier wrote:
>
> Just quoting a couple of relevant error messages:
>
> > Jul 3 09:18:54 comet kernel: sym0:0: ERROR (0:48) (a-2c-0) (27/18/c0) @ (scripta 220:84000000).
>
> SIST=0x48 bit 0x8 means SCSI GROSS ERROR.
>
> > Jul 3 09:25:23 comet kernel: sym0:1: ERROR (81:0) (e-ae-0) (3e/18/80) @ (scripta 80:1e000000).
>
> DSTAT=0x81 bit 0x1 means ILLEGAL INSTRUCTION DETECTED
>
> Can be the result of the device asserting the SCSI REQ signal when the
> initiator is expecting it to release the SCSI BUS.
>
> Some other error messages indicate some bad relection which is extremally
> severe in SCSI.
>
> I would recommend you to check the SCSI BUS.. Switch cable and/or
> terminators for example, etc...
I've tried 3 cables, and two terminators, all bought brand-new, from
separate sources.
Is it really that common for SCSI cables to be defective?
If so, is there a better way of testing them than simply buying more &
more until something works?
What are the chances that either the controller or the drives could be
the problem? Is there some way of diagnosing them (other than buying
replacements, which seems like an expensive, and possibly fruitless
approach)?
Sorry for the trivial questions, but it seems strange to me that what is
supposed to be a broken setup could achieve almost theoretical maximum
transfer rates when TCQ is switched off, but starts spewing errors at an
enormous rate when TCQ is switched on.
Cheers, Phil.
--
Say no to software patents! http://petition.eurolinux.org/
|)| Philip Hands [+44 (0)20 8530 9560] http://www.hands.com/
|-| HANDS.COM Ltd. http://www.uk.debian.org/
|(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-07-09 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 10:53 need help diagnosing sym53c1010-33/Fujitstu MAN3367MP/raid1 lockups Philip Hands
2002-07-02 2:00 ` Gérard Roudier
2002-07-09 9:32 ` Philip Hands [this message]
2002-07-10 1:23 ` Gérard Roudier
2002-07-09 22:17 ` Philip Hands
2002-07-12 2:19 ` Gérard Roudier
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=1026207164.10874.8402.camel@palm \
--to=phil@hands.com \
--cc=groudier@free.fr \
--cc=linux-scsi@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