From: William Lee Irwin III <wli@holomorphy.com>
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: Erik McKee <camhanaich99@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUGREPORT] kernel BUG in page_alloc.c:141!
Date: Fri, 21 Jun 2002 13:26:31 -0700 [thread overview]
Message-ID: <20020621202631.GD22961@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206211521130.14251-100000@chaos.physics.uiowa.edu>
On Fri, Jun 21, 2002 at 12:15:28PM -0700, Erik McKee wrote:
>>> Booted 2.5.24, and it ran fine for sometime, before it dead(live) locked,
>>> causing a reboot. Attempts to reboot were met with the following bug
>>> immediatly after calibrating delay loop, which equates out to an
>>> if(bad_range(buddy1,zone)) BUG; in __free_pages_ok:
On Fri, 21 Jun 2002, William Lee Irwin III wrote:
>> This looks odd. Can you by any chance disassemble the parts before this?
>> Or better yet, reproduce it with a kernel compiled with -g and objdump
>> --source --disassemble vmlinux to get the disassembly of __free_pages_ok()?
On Fri, Jun 21, 2002 at 03:23:13PM -0500, Kai Germaschewski wrote:
> "make mm/page_alloc.lst" may simplify this task. However, the usage of the
> various macros seems to confuse gcc -g / objdump somewhat, so the output
> isn't as clear as it could be.
> --Kai
I've had to work around that before, I'll probably still be able to
recognize it. It's still a royal PITA.
Cheers,
Bill
prev parent reply other threads:[~2002-06-21 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 19:15 [BUGREPORT] kernel BUG in page_alloc.c:141! Erik McKee
2002-06-21 20:06 ` William Lee Irwin III
2002-06-21 20:10 ` William Lee Irwin III
2002-06-21 20:23 ` Kai Germaschewski
2002-06-21 20:26 ` William Lee Irwin III [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=20020621202631.GD22961@holomorphy.com \
--to=wli@holomorphy.com \
--cc=camhanaich99@yahoo.com \
--cc=kai-germaschewski@uiowa.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.