On Fri, Feb 22, 2008 at 01:12:00PM -0500, John McSwain wrote:
> Wit wrote:
> >
> > In my first post, I asked about recent changes. No response.
> 
> There have been no changes to hardware or software.
> 
> >>
> >> A second guess would be to just fetch a new kernel version and try
> >> that one. In case your kernel is the problem.
> 
> Having been trying to compile a new kernel today and I keep getting 
> various errors no matter which kernel.  Just tried to compile the same 
> kernel still in use with same .config and get errors.
> 
> >
> > I still think it's hardware *unless* there have been recent changes in
> > software. Could even be file system corruption exposing a bug in
> > apps/kernel by corrupting data or code.
> 
> I'm beginning to think it is hardware also.  I opened the case this 
> morning, cleaned and checked but found nothing.
> 

 Have you tried memtest86 (or memtest86+ :http://www.memtest.org) ?
I once had a test box which suddenly started acting strangely,
including being unable to compile a kernel.  In that case, memtest
reported the first error in a few seconds, followed by a lot more -
some of the DRAM had failed.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to