From: Matt Porter <mporter@kernel.crashing.org>
To: Glenn Burkhardt <glenn@aoi-industries.com>
Cc: mlei30@yahoo.com, linuxppc-embedded@ozlabs.org
Subject: Re: kernel BUG at page_alloc.c:225 on PPC440GP
Date: Tue, 26 Apr 2005 09:47:22 -0700 [thread overview]
Message-ID: <20050426094722.A11404@cox.net> (raw)
In-Reply-To: <200504260828.03985.glenn@aoi-industries.com>; from glenn@aoi-industries.com on Tue, Apr 26, 2005 at 08:28:03AM -0400
On Tue, Apr 26, 2005 at 08:28:03AM -0400, Glenn Burkhardt wrote:
> I know it's been a year and a half since you submitted this report to the
> mailing list, but was this problem ever resolved? I think I'm seeing
> something similar in the 2.4.23 kernel.
Hi Glenn,
If you are seeing an oops with PPC440 on 2.4, please post the details.
-Matt
next prev parent reply other threads:[~2005-04-26 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 12:28 kernel BUG at page_alloc.c:225 on PPC440GP Glenn Burkhardt
2005-04-26 16:47 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-29 2:04 ming lei
2003-08-22 21:43 ming lei
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=20050426094722.A11404@cox.net \
--to=mporter@kernel.crashing.org \
--cc=glenn@aoi-industries.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mlei30@yahoo.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;
as well as URLs for NNTP newsgroup(s).