In article <[EMAIL PROTECTED]>,
Jakub Wasielewski <[EMAIL PROTECTED]> wrote:
>[1.] One line summary of the problem: kernel BUG at page_alloc.c:190!
I really need the symbolic oops information with the first oops piped
through ksymoops:
>kernel BUG at page_alloc.c:190!
This basically should happen only if the memory zone lists have become
nastily corrupted. But I'd need to see the decode of this:
>Call Trace: [<c012e465>] [<c0123807>] [<c0123884>] [<c0123a3a>] [<c0112e47>]
>[<c0112ce8>] [<c01137d4>]
> [<c011d99f>] [<c0113d7a>] [<c01090dc>] [<c010002b>]
to get an idea of what was going on at the time.. The other oopses are
not interesting, they're just more result of the corrupted memory maps.
>[7.7.] Other information that might be relevant to the problem:
>Well, as you can see the procs are overclocked (433@541) but that never
>caused me problems. If my bug is caused by overclocking please accept my
>apologies!
This is the likeliest explanation, though. A small amount of cache
corruption due to your quite radically overclocked CPU's can do
anything..
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
