these kinds of error are almost always flaky hardware, usually memory.
if it happens persistently, try replacing the machine's memory and
see if that makes the messages go away.  if that doesn't help,
post here again and we'll try to figure out what's going on.

-Chuck


On Mon, Feb 21, 2000 at 04:36:43PM +0800, Chan Yiu Wah wrote:
> Hello,
> 
> My system (i386) sudenly hanged up with the following error . Does anyone
> know what is mean?  system works after reboot.  This is the 2nd times.
> Any idea ?
> 
> Clarence 
> 
> 
> ======= Error =======
> Feb 21 16:10:41 lts159 /netbsd: Data modified on freelist: word 0 of
> object 0xf0
> 6ba800 size 1024 previous type ??? (invalid addr 0xff0300e0)
> Feb 21 16:10:41 lts159 /netbsd: Data modified on freelist: word 0 of
> object 0xf0
> 6ba800 size 1024 previous type ??? (0xf000fc0 != 0xdeadbeef)
> Feb 21 16:10:41 lts159 /netbsd: Data modified on freelist: word 0 of
> object 0xf0
> 6ba800 size 1024 previous type ??? (invalid addr 0xff80ff1f)
> Feb 21 16:10:41 lts159 /netbsd: Data modified on freelist: word 0 of
> object 0xf0
> 6ba800 size 1024 previous type ??? (0x57 != 0xdeadbeef)
> Feb 21 16:10:41 lts159 /netbsd: Data modified on freelist: word 0 of
> object 0xf0
> 6ba800 size 1024 previous type free (0x0 != 0xdeadbeef)
> Feb 21 16:10:41 lts159 /netbsd: Data modified on freelist: word 0 of
> object 0xf0
> 6ba800 size 1024 previous type ??? (invalid addr 0x70006000)
> Feb 21 16:10:41 lts159 /netbsd: Data modified on freelist: word 0 of
> object 0xf0
> 6ba800 size 1024 previous type ??? (0xe0006007 != 0xdeadbeef)
> ======================================================