Subject: Re: Patch for recent ncr.c lossage / not just ncr.c
To: Erik Bertelsen <erik@mediator.uni-c.dk>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: current-users
Date: 10/17/1999 08:52:24
On Sat, 16 Oct 1999 23:44:42 +0200 
 Erik Bertelsen <erik@mediator.uni-c.dk> wrote:

 > esp0 at obio0 (quick): address 0x8b0000: NCR53C96, 16MHz, SCSI ID 7
 > [NCR_INIT(1)] <cmd:0x2><cmd:0x0><cmd:0x3>scsibus0 at esp0: 8 targets, 8 luns per target
 > ...
 >    several lines about zsc0 and zstty0 and 1
 > ...
 > nubus0 at mainbus0
 > fpu0 at mainbus0 (mc68040)
 > scsibus0: waiting for 2 seconds for devices to settle...
 > [ncr53c9x_scsi_cmd] [0x0, 6]->0 
 > 
 > and that's it -- here the machine hangs still.

that's *it*?  Well, that's *very* odd.  the chip should be idle at this point
and should call ncr53c9x_sched() to actually get the operation going.  Could
you sprinkle some additional printfs() in ncr53c9x_scsi_cmd() to dump out
the driver state, etc?

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>