From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at page_alloc.c:190!
Date: 5 Feb 2001 11:54:29 -0800 [thread overview]
Message-ID: <95n0dl$uhk$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0102051942040.875-100000@wasyl.dom.pl>
In article <Pine.LNX.4.31.0102051942040.875-100000@wasyl.dom.pl>,
Jakub Wasielewski <wasyl@infoland.com.pl> 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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-05 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 18:53 PROBLEM: kernel BUG at page_alloc.c:190! Jakub Wasielewski
2001-02-05 19:54 ` Linus Torvalds [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='95n0dl$uhk$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox