On Wed, 31 Mar 1999, Tony Wildish wrote: > > Try booting with the 'mem=xxxM' option to limit yourself to a small > amount of RAM. If you are lucky then the problem is high enough in the > memory that you can limit yourself to a good region and it will work. There's also a memtest86 utility that compiles under Linux to produce a disk you can boot your system with and test the memory--I've find some bad memory with that before. Compiling a kernel a bunch of times is also a good way to test if you've got bad memory. Brian
- Linux 2.2.4 & RAID - success report Richard Jones
- Filesystem corruption (was: Re: Linux 2.2.4 & ... Richard Jones
- Re: Filesystem corruption (was: Re: Linux 2.2.... Richard Jones
- Re: Filesystem corruption (was: Re: Linux 2.2.... Tony Wildish
- Re: Filesystem corruption (was: Re: Linux ... D. Lance Robinson
- Re: Filesystem corruption (was: Re: Li... Richard Jones
- Re: Filesystem corruption (was: R... Alvin Oga
- Re: Filesystem corruption (was: Re: Linux ... Brian Leeper
- Re: Filesystem corruption (was: Re: Li... Robert Siemer
- Re: Filesystem corruption (was: Re: Linux 2.2.... Brian Leeper
- Re: Filesystem corruption (was: Re: Linux 2.2.... Stephen C. Tweedie
- Re: Filesystem corruption (was: Re: Linux ... Richard Jones
- Re: Filesystem corruption (was: Re: Li... Stephen C. Tweedie
