[9187] in linux-scsi channel archive
Re: Feature in ncr53c8xx/sym53c8xx driver
daemon@ATHENA.MIT.EDU (Miquel van Smoorenburg)
Thu Jul 13 14:36:34 2000
From: miquels@cistron.nl (Miquel van Smoorenburg)
Date: 13 Jul 2000 18:29:17 GMT
Message-ID: <8kl1pt$pv9$1@enterprise.cistron.net>
In-Reply-To: <13037D3EF290D211B95F00A0C9EBECC4AF71E3@tungsten.bri.hp.com>
X-Complaints-To: abuse@cistron.nl
To: linux-scsi@vger.rutgers.edu
In article <cistron.13037D3EF290D211B95F00A0C9EBECC4AF71E3@tungsten.bri.hp.com>,
Falkinder, David <davidf@bri.hp.com> wrote:
> I think I may have a handle on some of the problems that have been
>seen with the sym53c8xx and ncr53c8xx driver.
What problems exactly? I tried to deploy quite a hefty new news server
today, but after 5-15 minutes the sym53c8xx driver locked up (box still
alive, but no more interrupts from both SCSI controller channels).
(I just mailed Gerard Roudier about this).
>So boiling it down, the core of the problem is that for SCSI 1 the LUN is
>set in byte 1 (zero indexed CDB) for the Test Unit Ready and Request Sense
>commands, where as these are reserved fields in SCSI 2 and 3 specs. A check
>condition causes a request sense, which provides an infinite loop.
Is that the driver locking up, or the on chip sequencer ? Would it
make sense that both channels (scsi0 & scsi1) stoped working ?
Mike.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
