On Mon, Jan 24, 2000 at 12:23:59PM -0500, Mason Loring Bliss wrote:
>[...]
> On coming back up, I get:
> 
> Jan 23 15:04:28 acheron savecore: reboot after panic: trap
> 
> Now, something which MAY be unrelated:
> 
> Jan 23 23:29:01 acheron /netbsd: Data modified on freelist: word 0 of object 0xf05b0550 size 4 previous type UVM amap (0xfeadbeef != 0xdeadbeef)
> Jan 23 23:29:54 acheron /netbsd: Data modified on freelist: word 0 of object 0xf05b0550 size 4 previous type UVM amap (0xfeadbeef != 0xdeadbeef)
> Jan 23 23:29:55 acheron /netbsd: Data modified on freelist: word 0 of object 0xf05b0550 size 8 previous type UVM amap (0xfeadbeef != 0xdeadbeef)
> Jan 23 23:32:53 acheron /netbsd: Data modified on freelist: word 0 of object 0xf05b0550 size 4 previous type UVM amap (0xfeadbeef != 0xdeadbeef)
> Jan 23 23:34:40 acheron /netbsd: Data modified on freelist: word 0 of object 0xf05b0550 size 4 previous type UVM amap (0xfeadbeef != 0xdeadbeef)
> 
> Is it possible that this last is the consequence of bad RAM? The RAM in

It's likely the problem: note that there is only one bit which changes, always
at the same adress.

> question has lived through a system which died as a consequence of my
> zapping it with static. However, the memory test when the system boots
> up doesn't indicate problems. Today (or something) I'm going to whip

This test is not extensive; and often doesn't catch problems.
There are memory test programs available (lost urls, sorry) which are better
for this.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--