> If it was hardware, say one of the two processors was flaky, wouldn't I
> expect to see corrupted pointers being dereferenced in other sections
> of code or is the dcache data structure particular susceptible?
The dcache has long chains of pointers and tends to show up on things like
memory are
Hi,
Alan Cox wrote:
> > I'd like to find more detail of the rare corruption so I can see if
> > it matches what we're experiencing, is it more likely with an SMP
> > machine, etc. Is there an archive of patches that go into a
> > particular version anywhere?
>
> No but all pre releases can be
Hi,
> > A two processor SMP machine has been crashing recently, sometimes it
> > manages to Oops before hand. Below is the klogd output with assembly
> > from gdb. The do_generic_file_read+347 Oops occurred once, the dput+77
> > Oops has occurred five times; all five are below.
> >
> > Does
Hi,
> A two processor SMP machine has been crashing recently, sometimes it
> manages to Oops before hand. Below is the klogd output with assembly
> from gdb. The do_generic_file_read+347 Oops occurred once, the dput+77
> Oops has occurred five times; all five are below.
>
> Does anyone recog
4 matches
Mail list logo
