On Thu, 13 Jun 1996, Hauke Fath wrote:

> ...after the following crash on
> 
> >NetBSD 1.2_ALPHA (EIBE) #0: Thu Jun  6 17:13:08 GMT 1996
> >    hauke@se30:/usr/src/sys/arch/mac68k/compile/EIBE
> >Apple Macintosh SE/30  (68030)
> 
> [...]
> >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(195c8,7ab8,8c4af0,1013,8c4b08) + 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,8c4c24,6,6e21000,2000,4,2710,760770,1001) + 8a
> >_sdstart(6c02200,6c022a6,760770) + 1ca
> >_sdstrategy(760770,8c4c84,2830a,8c4c7c,0) + b4
> >_spec_strategy(8c4c7c) + 24
> >_bwrite(760770,6c54500,0,1,fffff7f3) + b8

Hmm.  I've made some changes in the last couple of days that may (or may
not) be related.  In particular, this problem looks similar to some of the
interrupt difficulties I've had.  I should also see if my timeouts are
reasonable, especially with MO disks.

> >se30/hauke:~ {3} fsck /dev/rsd2g
> >sd2(sbc0:2:0): illegal request, data = 80 20 01 00 00 00 c4 1b 10 00 00 00
> >22 60
> > 6d b6 db 6d b6 db 1a 00 04 00
> >sd2: could not mode sense (4); using fictitious geometry
> >** /dev/rsd2g
> >panic: pmap_alloc_pv: pgi_nfree inconsistent
> >Stopped at      _Debugger+0x6:  unlk    a6
> >db> t
> >_Debugger(195c8,8851d,898d70,1,898d74) + 6
> >_panic(8851d,12f928,898da8,88dd6,7529000) + 34
> >_pmap_init(7529000,1,7529000,33000,ffffffff) + 484
> >_pmap_enter(a0e00,7529000,bb7000,3,1) + 156
> >_vmapbuf(75d830,2000,33000,2000,6c72a00) + bc
> >_physio(7e3e8,0,d16,100000,7e736) + 176
> >_sdread(d16,898f28,0) + 1c
> >_spec_read(898ed8,898eec,30a1a,898ed8,e8) + a6

This is odd, to say the least.  I'm not sure what could be happening here.
It's apparently not the driver, but I wouldn't bet my life on it.

> >sd2(sbc0:2:0): medium error, info = 328392 (decimal), data = 18 00 23 20
> >23 00 6
> >0 00 00 00 00 00 8a 21 6d b6 db 6d b6 db 08 05 02 c8
> >THE FOLLOWING DISK SECTORS COULD NOT BE READ: 328256, 328257, 328258, 328259,
> 
> 
> -- PHYSICAL errors! Can a crash damage media physically?

Not that I'm aware of.

[With ncrscsi:]

> >sd2: could not mode sense (4); using fictitious geometry
> >panic: pmap_alloc_pv: pgi_nfree inconsistent
> >Stopped at      _Debugger+0x6:  unlk    a6
> >db> t
> >_Debugger(16c28,87895,99dd64,1,99dd68) + 6
> >_panic(87895,12ac58,99dd9c,8814e,7329000) + 34
> >_pmap_init(7329000,1,7329000,33000,ffffffff) + 484
> >_pmap_enter(9ec64,7329000,9d9000,3,1) + 156
> >_vmapbuf(95b830,2000,33000,2000,7cd380) + bc
> >_physio(7b850,0,d16,100000,7bb9e) + 18c
> >_sdread(d16,99df28,0) + 1c

Looks like the same crash.

You might try updating your sources and see if the -current code helps you
at all.

--scott