Re: OOPS 2.4.19-pre7-ac4 (Was: strange things in kernel 2.4.19-pre7-ac4 + preempt patch)

Denis Vlasenko (vda@port.imtp.ilyichevsk.odessa.ua)
Mon, 13 May 2002 17:14:57 -0200


On 13 May 2002 08:28, Steve Kieu wrote:
> > pointer got
> > corrupted and now movzbl stumbles over it.
> >
> > Bad RAM? Consider memtest86 run overnight.
> > --
>
> I did use memtest86 and all test is passed, no errors.
> And problem still persists with 2.4.19-pre8-ac2 ; oops
> after exiting X
>
> Now I have to use 2.4.16 ; any way all kernel before
> 2.4.19-pre2 is normal, I did not test 2.4.19-preX>2
> but 2.4.19-pre7-ac4 and 2.4.19-pre8-ac2

When no one answers on lkml to your oops report, you
have basically the only choice: start looking at stack trace
yourself, insert printks here and there, recompile and give it a try.

In other words, the source is with you. You *can* do it.

--
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/