RE: 2.4.14 Oops during boot (KT133A Problem?)

	the memory check in bios is designed mostly for testing if (detected
memory chips == present memory chips).
	Safe comprehensive checking can be done by memtest86, and virtualy
unsafe testing can be cyclic kernel compilation (if you notice strange
compile errors at same kernel config but at different moments, you can
suspect that your hardware is rotten). 

	To: Sven
	are you sure that ALL your memory chips are bad? how about memory
latency and other bios settings, overclocking, etc.? try to setup your box
to run at slowest memory configuration as possible. It's hard to believe
that all of your chips are gone. 

	Regards
	Petr

	----- previous message follows:
> Congratulations!
> 
> [e-mail] wrote:
> > Well, the problem got solved (although not in a way I'd consider
> > satisfactory). After my machine started random segfaulting the day
> > before yesterday, I memcheck86'ed it again (the last check is a mere two
> > months ago), and lo - all three RAM chips were broken. Unfortunately, I
> > discovered this, after this broken RAM caused my /usr partition to go
> > fubar, resulting in me spending yesterday with a nice little reinstall.
> > After the reinstall, 2.4.14 booted fine off the harddisk. No more
> > oopses.
> 
> During this holidays, I guessed, and I thought it because of
> harddisk or PCI chip erro. Memory error! Was it found when booting
> matherboard by BIOS? I think motherboard always check memories when
> booting.  
> 
> -- 
> -=-=-=-=  SHINKO ELECTRIC INDUSTRIES CO., LTD.           =-=-=-=-
> =-=-=-=-    Core Technology Research & Laboratory,       -=-=-=-=
> -=-=-=-=      Infomation Technology Research Dept.       =-=-=-=-
> =-=-=-=-  Name:Hisakazu Nakai          TEL:[phone]  -=-=-=-=
> -=-=-=-=  Mail:[e-mail]  FAX:[phone]  =-=-=-=-
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/