Subject: Re: Crashes in 1.3.3 indicate faulty hardware?
To: None <port-i386@netbsd.org>
From: Bernd Sieker <bsieker@techfak.uni-bielefeld.de>
List: port-i386
Date: 01/28/1999 01:07:13
On 27.01.99, 17:11:56, Manuel Bouyer wrote:
> > 
> > vm_fault(0xf02a6000, f09b5000, 3, 0) -> 1
> > fatal page fault in supervisor mode
> > trap type 6 code 2 eip f0193837 cs 8 eflags 10206 cr2 f09b51fc cpl 0
> > panic: trap
> > 
> > Could this indicate a bad or unstable hardware configuration?

> [...]
> (these are cyrix p166+ based boxes with asus motherboard, edo RAM).
> An extensive memory test for 3 full days didn't show any problems.
> I changed the EDO for a 64Mb SDRAM module, this didn't solve the problem.

Well, I now removed the two EDO modules and inserted one 128 MB
'PC100' SDRAM module. I'll see whether things change.

> So there are many other things that can be bad (motherboard, cache, CPU, ...).

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

-- 
Bernd Sieker

Windows. Just say No.