At 15:07 Uhr 16.07.1996, "The Great Mr. Kurtz [David A. Gatwood]"
<davagatw@mars.utm.edu wrote:
>Here is the crash transcript:
>
>
># mount -a
>sbc0: can not transfer more data
>sbc0: aborting, but phase=DATA_OUT (reset)
>sbc0: reset SCSI bus for TID=0 LUN=0
>panic: ncr5380_scsi_cmd: polled request, abort failed
>Stopped at      _Debugger+0x6:  unlk    a6
>db> cont
>syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up
>NetBSD/mac68k does not trust itself to update the RTC on shutdown.
>
>dumping to dev 401, offset 28680
>dump panic: ncr5380_scsi_cmd: polled request, abort failed
>Stopped at      _Debugger+0x6:  unlk    a6
>db> cont
>
>dumping to dev 401, offset 28680
>dump device not ready
>
>
><SYSTEM REBOOTS HERE>


So I am / my MO drive is not alone with this one 8-/
Next time you see this type 't' at the db> prompt and let's see if it looks
the same as:


## 7 Jul, 01h10
#
# -current sbc kernel of 25 Jun, splimp() = 2
# NetBSD 1.2_ALPHA (EIBE) #5: Tue Jun 25 19:11:57 GMT 1996
# booted to serial console
#
# Action: sup kernel sources to /dev/sd2g (Fujitsu M2512)

sbc0: can not transfer more data
sbc0: aborting, but phase=DATA_OUT (reset)
sbc0: reset SCSI bus for TID=2 LUN=0
panic: ncr5380_scsi_cmd: polled request, abort failed
Stopped at      _Debugger+0x6:  unlk    a6
db> t
_Debugger(19600,7ab8,8e0c58,1013,8e0c70) + 6
_panic(7ab8,0,7,2,3) + 34
_ncr5380_scsi_cmd(6c06f80) + 80
_scsi_done(6c06f80,79d0,6c048ac,6c04800,6c048ac) + 6a
_ncr5380_scsi_cmd(6c04800) + 352
_ncr5380_scsi_cmd(6c04800) + 1950
_ncr5380_scsi_cmd(6c04800) + 650
_ncr5380_scsi_cmd(6c06f80) + 110
_scsi_execute_xs(6c06f80) + 28
_scsi_scsi_cmd(6c05de0,8e0d8c,6,7099000,2000,4,2710,764a18,1001) + 8a
_sdstart(6c02200,6c022a6,764a18) + 1ca
_sdstrategy(764a18,8e0df0,283e2,8e0de8,0) + b4
_spec_strategy(8e0de8) + 24
_bwrite(764a18,6c73900,1,1,0) + d8
_ffs_update(8e0e44) + 182
_ufs_setattr(8e0e7c) + 234
_sys_utimes(6c73900,8e0f88,8e0f80) + 162
_syscall(8a) + 10a
_trap0() + e
db>



	hauke

---
"It's never straight up and down"     (DEVO)