I tested with memtest86, and luckily found no problems (and good, because
this RAM is new!).
> Decoding the oops is always useful, especially if you can find
> a pattern after you've decoded a few. And if you don't manage
> to find any pattern in them, you know the suspicion lies with
> the hardware ...
I decoded the oops, from /var/log/messages, but I'm not sure how to read
it. Do you have any pointers? Where should I be looking for patterns? Do I
just wait until the next time it happens, get a second log, and diff them?
>
-
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/