SCSI near-crash - is this hardware or software?

SCSI near-crash - is this hardware or software?

Post by Michael B Her » Mon, 07 Aug 1995 04:00:00



Hmm...I had something very much like this.  It turned out to be that my
mach64 video card and BT946c were conflicting, and there was really no
way to resolve the conflict.  (I now have a #9GXE64 Pro.)  

I'd be interested to know if you have an ATI card, and otherwise, you
might want a new firmware revision for the Buslogic.

later,
mike

Excerpts from netnews.comp.os.linux.misc: 31-Jul-95 SCSI near-crash - is

Quote:> Jul 31 09:14:09 candle kernel: scsi : aborting command due to timeout
: pid 3069
> 52, scsi0, id 0, lun 0 0x08 09 0b b4 02 00
> Jul 31 09:14:10 candle kernel: BusLogic SCSI: buslogic_abort: 0 0
> Jul 31 09:14:10 candle kernel: BusLogic SCSI: buslogic_abort: timed
out command
> pending for 0802.
> Jul 31 09:14:10 candle kernel: BusLogic SCSI: buslogic_abort: other
pending comm
> and: 0802
> Jul 31 09:14:10 candle kernel: offset=0, inode=543978826,

rec_len=14130, name_le
Quote:> n=12576
> Jul 31 09:14:57 candle kernel: offset=0, inode=543978826,

rec_len=14130, name_le
Quote:> n=12576
> Jul 31 09:16:05 candle last message repeated 9 times
> Jul 31 09:17:07 candle last message repeated 4 times