David Maxwell wrote on 8 June 1999:
> 
> 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.

Well, I just got something similar? with a kernel compiled yesterday.
(Hadn't happened before, same machine)

uvm_fault(0xf6367d5c, 0xb1a00000, 0, 1) -> 1
kernel: page fault trap, code=0
Stopped in cron at      amap_wipeout+0x19:      movl    0(%eax,%edx,4),%eax
db> trace
amap_wipeout(f647002c,f64866e0,f64866e0,0,f649eed4) at amap_wipeout+0x19
amap_unref(f64866e0,0) at amap_unref+0x1a
uvm_unmap_detach(f6486c08,0,f6367d5c,f646ab44,f6486c08) at uvm_unmap_detach+0x31
uvm_unmap(f6367d5c,0,efbfe000,f6367d5c,f649ef34) at uvm_unmap+0xaf
uvm_deallocate(f6367d5c,0,efbfe000) at uvm_deallocate+0x38
exit1(f646ab44,0,f649efa8,f01ea565,f646ab44) at exit1+0x13e
sys_exit(f646ab44,f649ef88,f649ef80,0,8140) at sys_exit+0x14
syscall() at syscall+0x149
--- syscall (number 1) ---
0x4007cc2f:

Just FYI.

Cheers,

Patrick