lkml.org 
[lkml]   [2004]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: File system cache corruption in 2.6?
From
Date
On Mon, 2004-01-05 at 14:19, Jens Axboe wrote:
> On Mon, Jan 05 2004, Nathaniel W. Filardo wrote:
> > Hi all,
> > I'm trying to work out the cause of a series of issues I've seen
> > on my 2.6 machine. It appears as though files (specifically libraries) in
> > memory can get corrupted, resulting in strangeness like segfaults and
> > things like "relocation error: can't find symbol ...-VOMD-POINTER" instead
> > of "...-VOID-POINTER".
>
> That's a single bit error.
>
> > I don't believe it's actual hardware failure for a few reasons: memtest86
> > passes all tests, GCC doesn't crash (it's a Gentoo system, so gcc and I
> > are well acquainted - and before I get jumped on, I've installed udev ;)
> > ), and most importantly, sometimes thrashing the file system or engaging a
> > kernel compile will rectify the situation, as just happened with emacs.
> > It crashed, I killed it, it wouldn't load - I started a kernel compile,
> > waited a bit, and lo', it works again. No messages of relevance appear in
> > dmesg.
>
> It looks _extremely_ much like bad memory, or bad hardware. Sometimes
> memtest just doesn't catch all errors (how long did you run it? needs
> several days often).

Also, go to the options, and turn on caching, as well as all memory
addresses and tests ... (keys pressed if I can remember, is:

c->1->2->2->3->3->3

should turn on above options for memtest).


--
Martin Schlemmer
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2005-03-22 13:59    [W:0.036 / U:1.596 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site