From: Linus Torvalds <torvalds@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: mbligh@aracnet.com, linux-kernel@vger.kernel.org,
Stephane LOEUILLET <bug-kernel@leroutier.net>
Subject: Re: [Bug 2773] New: kernel panic under medium load
Date: Wed, 26 May 2004 17:08:20 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0405261656370.1648@ppc970.osdl.org> (raw)
In-Reply-To: <20040526163029.10b5c88c.akpm@osdl.org>
On Wed, 26 May 2004, Andrew Morton wrote:
>
> Linus Torvalds <torvalds@osdl.org> wrote:
> >
> > What happens for you before? Can you do a "make mm/page_alloc.s" and post
> > the result (well, just __alloc_pages, not the rest).
> >
>
> Stephane had added page_alloc.s to
>
> http://bugme.osdl.org/show_bug.cgi?id=2773
Interesting. The load is right before the instruction:
** movl -36(%ebp), %eax ***
cmpl $99, 24(%eax)
jg .L241
and the only difference here is that it says "-36(%ebp)" instead of
"20(%esp)" because it's compiled with frame pointers.
(Well, there must be something else different on the stack frame too,
according to the earlier dump it really _should_ be 20%(%esp), but the
difference between %esp and %ebp here runs to 52, not 56, which makes me
suspect the thing is compiled with some different options. Anyway, that
bogus 0x00004000 value is not on the stack at either offset in the dump,
so it shouldn't matter).
Oh, I just notice that Stephane actually _says_ that he changed the config
options.
Anyway, the interesting part seems to be that %eax is corrupt, and it
really shouldn't be. It appears to be ok in memory, and was loaded from
there just before, so I'm wondering whether there is soem _serious_
problem with this machine?
Linus
prev parent reply other threads:[~2004-05-27 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 14:35 Martin J. Bligh
2004-05-26 16:51 ` Linus Torvalds
2004-05-26 23:30 ` Andrew Morton
2004-05-27 0:08 ` 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=Pine.LNX.4.58.0405261656370.1648@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=bug-kernel@leroutier.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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
all inboxes | Powered by JetHome®