bug#102: [kernel] bug#102: second SCSI on C3000 doesn't work
X-PA-RISC Linux-PR-Message: report 102
X-PA-RISC Linux-PR-Package: kernel
Received: via spool by email@example.com id=B102.9871189496218
(code B ref 102); Thu, 12 Apr 2001 23:48:01 GMT
Date: Fri, 13 Apr 2001 00:43:08 +0100
From: Richard Hirst <firstname.lastname@example.org>
To: Paul Bame <email@example.com>, firstname.lastname@example.org
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0us
In-Reply-To: <no.id>; from email@example.com on Thu, Apr 12, 2001 at 11:05:41PM +0000
On Thu, Apr 12, 2001 at 11:05:41PM +0000, firstname.lastname@example.org wrote:
> The second (actually the first) SCSI controller on C3000 doesn't work.
> This one's hooked to the narrow SCSI connector on the back, which had
> a disk and proper termination at the time of the test, which the boot
> rom saw just fine. This boot log is with terminator but no disk, and
> I think it's the same as when the disk is attached:
> sym53c896-0: suspicious SCSI data while resetting the BUS.
> sym53c896-0: dp1,d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o = 0x4000100, expecting 0x100
> sym53c896-0: FATAL ERROR: CHECK SCSI BUS - CABLES, TERMINATION, DEVICE POWER etc.!
> sym53c896-0: giving up ...
It is complaining about dp1, parity for the top half of the bus, which
is interesting if it is only narrow out of the box.
If you boot with sym53c8xx=buschk:2 it should just warn about the
error and carry on. See drivers/scsi/README.ncr553c8xx for options.