* Hemmann, Volker Armin <[email protected]> wrote:
> Ok, so after the holidays I will do the following:
>
> let memtest86+ run several hours. do a full backup&restore to switch
> to r3 and build an unpatched kernel. see if I can reproduce the oops
> with .21 and .22 (because AFAIR no oops with 21.. but I might be
> wrong).
>
> Not exactly in that order.
yeah, that would help. But generally it a big PITA to figure out such
bugs where there's no specific 'smoking gun' in the oopses themselves.
What usually happens is that people try to figure out a faster way of
triggering the bug - and then bisection can be done. But the hardware
must be eliminated first as the cause of the bug. Taking out half of the
RAM (i know it's painful ...) can help too in isolating RAM problems.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
