On Tue, Jun 08, 1999 at 10:59:45PM -0300, David Maxwell wrote:
> On Tue, Jun 08, 1999 at 08:12:53PM -0300, David Maxwell wrote:
> > Helping a friend install a new 1.4 box, in the middle of some
> > pkgsrc compiles (and just while switching between wscons) we got
> > this panic:
> > 
> > panic: amap_wipeout: corrupt amap
> > 
> > That's a new one on me.
> > 
> > Only thing different from usual installs I do is that this
> > hd is wd1, (wd0 will be used for NT later) and there's a 
> > DOS partition as partition 0 on wd1, partition 1 is NetBSD
> > which is the one marked active.
> 
> As a further datapoint, the machine has paniced twice more,
> with different panics, uvm_fault, and pmap-something.
> 
> cc1 also gets a lot of SEGVs. I'm going to try the hd in
> another machine to see if the problem moves or stays.

This sounds like a hardware problem. Memory or cache problems usually
have this kind of symptoms. Has any other system been run successfully
on this system? Windows may not trigger these problems as quickly, btw.

The disk shouldn't matter, unless NetBSD is paging to it and getting
corrupted pages back from it's swapspace. But "amap" panics is not
the first thing you'd expect there.

- Frank