Christos Zoulas wrote:
> In article <l03102803b299e3fb6401@[192.168.1.4]> hauke@Espresso.Rhein-Neckar.DE (Hauke Fath) writes:
> >At 18:53 Uhr +0100 12.12.1998, Space Case wrote:
> >
> >>Just as an update, I'm now running a kernel built yesterday from Dec. 10
> >>sources, still accessing two disks with no problems.  If anyone else wants
> >>to give it a try, it's at:
> >>
> >>  ftp://ftp.eskimo.com/u/w/wormey/netbsd/kernels/netbsd.g91.gz
> >>
> >
> >I tried your kernel, and it said to me [single user]:
> >
> ># disklabel sd1
> >panic: fstat
> >Stopped in disklabel at _Debugger+0x6:  unlk    a6
> >db> t
> >_Debugger(128,7b4f88,7b4f44,20718,206a6) + 6
> >_panic(206a6,7a04d0,1a1ec,0,0) + 50
> >_sys___fstat13(7a04d0,7b4f88,7b4f80) + 66
> >_syscall(117) + 146
> >_trap0() + e
> 
> The only panic in fstat it when the file is not a vnode or a socket...
> What the hell is it then?

something that got corrupted via interaction with the scsi code and the
pool allocator perhaps?  there's definitely been something slightly screwy 
going on in that area for several months now given the reports that i've
seen here...

later.

colin