> > This is true. What I suppose would be the solution is that if faulty > > hardware is found, a reduction in performance should be made. > > Finding out if you've got bad RAM might take a few hours running mem86. Not > exactly what I have in mind to do each boot... Even if memtest doesn't find anything you can't be sure the box is fine. I've seen boxed which passed memtest just fine, but compiling kernels in a endless loop with "make -j" still bombed after some time with gcc sig11. Gerd -- Wirtschaftsinformatiker == Leute, die zwar die aktuellen Aktienkurse jedes Softwareherstellers kennen, aber keines der Produkte auch nur ansatzweise bedienen können. -- Benedict Mangelsdorff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Defective Red Hat Distribution poorly represents... Charles Turner, Ph.D.
- Re: Defective Red Hat Distribution poorly repre... John Jasen
- Re: Defective Red Hat Distribution poorly r... Mohammad A. Haque
- Re: Defective Red Hat Distribution poorly r... Horst von Brand
- Re: Defective Red Hat Distribution poor... David Riley
- Re: Defective Red Hat Distribution ... David Lang
- Re: Defective Red Hat Distribu... David Riley
- Re: Defective Red Hat Distribu... David Lang
- Re: Defective Red Hat Distribu... Horst von Brand
- Re: Defective Red Hat Distribu... Dan Hollis
- Re: Defective Red Hat Distribu... Gerd Knorr
- Re: Defective Red Hat Distribution ... Gérard Roudier
- Re: Defective Red Hat Distribution ... Bob Lorenzini
- Re: Defective Red Hat Distribution ... Jeff Epler
- Re: Defective Red Hat Distribu... David Riley
- Re: Defective Red Hat Distribu... Richard Torkar
- Re: Defective Red Hat Distribu... David Riley
- Re: Defective Red Hat Distribu... Jeff Epler
- Re: Defective Red Hat Distribu... David Riley
- Re: Defective Red Hat Distribu... Richard Torkar
- Re: Was:Defective Red Hat Dist... Richard.Reynolds