I just got this panic, I think it's because of a faulty drive, but it's
the first one that has made a dump for me:

     bullbox# sd1(ncr0:1:0): soft error (corrected), info = 299494 (decimal), data =
     00 00 00 00 12 00 00 00 00 00
     sd1(ncr0:1:0): soft error (corrected), info = 300389 (decimal), data = 00 00 00
     00 12 00 00 00 00 00
     sd1(ncr0:1:0): soft error (corrected), info = 300389 (decimal), data = 00 00 00
     00 09 00 00 00 00 00
     ncr.c: timeout counter = 999943, len = 1024 count=2048 (count-len 1024).
     ncr_debug = 2,  1=out, 2=insd1(ncr0:1:0): soft error (corrected), info = 300390
     (decimal), data = 00 00 00 00 17 00 00 00 00 00
     /altroot/usr: bad dir ino 11160 at offset 1024: mangled entry
     panic: bad dir
     syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up
     
     dumping to dev 1, offset 98482
     dump 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 succeeded
     
     
     rebooting ...

Of course the fun part was when I got this on the reboot:

     checking for core dump...
     savecore: reboot after panic: bad dir
     Dec  7 01:34:21 bullbox savecore: reboot after panic: bad dir
     savecore: system went down at Thu Dec  7 01:29:22 1995
     .avecore: /var/crash/bounds: No such file or dirUehc-toohr.y.
       s anvcerc5o3r8e0:_ mwirnipthiynsg  sceotrtei ntgo  b/pv-a>rb/_cbrcaosuhn/tn e=
     t b1s0d0.000..c
     re
     Uh-oh...  ncr5380_minphys setting bp->b_bcount = 10000.
     Uh-oh...  ncr5380_minphys setting bp->b_bcount = 10000.
     Uh-oh...  ncr5380_minphys setting bp->b_bcount = 10000.
     Uh-oh...  ncr5380_minphys setting bp->b_bcount = 10000.
     Uh-oh...  ncr5380_minphys setting bp->b_bcount = 10000.
     Uh-oh...  ncr5380_minphys setting bp->b_bcount = 10000.
     Uh-oh...  ncr5380_minphys setting bp->b_bcount = 10000.

It kept printing that last line until I typed ^C.  Any suggestions on how
to get my machine to boot properly when there is a dump?

Jon Buller