From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: Thomas Molina <tmolina@cablespeed.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.6.0-test4-mm4
Date: Sun, 31 Aug 2003 11:44:32 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0308311142550.16584@montezuma.fsmlabs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308310926120.26483-100000@localhost.localdomain>
On Sun, 31 Aug 2003, Thomas Molina wrote:
> Thank you Adrew. I have been following a panic in store_stackinfo since
> it was introduced with CONFIG_DEBUG_PAGEALLOC (see bugzilla #973).
> 2.6.0-test4-mm4 was the first kernel version I have tested which didn't
> exhibit this failure mode.
>
> I do get a hang on boot in RedHat 8 if all the other "kernel hacking"
> options are enabled. This hang comes at the point in the boot sequence
> where the next message I would expect is the mounting of /proc. I've not
> looked into it too deeply since it sounded similar to what others have
> seen, and it wasn't my main focus. I'll go back later and look into it if
> the condition persists.
Well you appeared to have serio problems and there have been a number of
changes in the input department. Do you know which kernel hacking option
causes the new hang?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2003-08-31 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 23:15 2.6.0-test4-mm4 Andrew Morton
2003-08-31 14:41 ` 2.6.0-test4-mm4 Thomas Molina
2003-08-31 15:44 ` Zwane Mwaikambo [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.53.0308311142550.16584@montezuma.fsmlabs.com \
--to=zwane@linuxpower.ca \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tmolina@cablespeed.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