From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: Kernel 2.6.9 Page Allocation Failures w/TSO+rollup.patch
Date: Mon, 25 Oct 2004 21:33:47 +1000 [thread overview]
Message-ID: <417CE49B.4060308@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0410250645540.9868@p500>
Justin Piszcz wrote:
> I guess people who get this should just stick with 2.6.8.1?
>
Does it cause any noticable problems? If not, then stay with
2.6.9.
However, it would be nice to get to the bottom of it. It might
just be happening by chance on 2.6.9 but not 2.6.8.1 though...
Anyway, how often are you getting the messages? How many
ethernet cards in the system?
Can you run a kernel with sysrq support, and do `SysRq+M`
(close to when the allocation failure happens if possible, but
otherwise on a normally running system after it has been up
for a while). Then send in the dmesg.
Thanks,
Nick
next prev parent reply other threads:[~2004-10-25 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 10:48 Kernel 2.6.9 Page Allocation Failures w/TSO+rollup.patch Justin Piszcz
2004-10-25 11:33 ` Nick Piggin [this message]
2004-10-25 12:03 ` Justin Piszcz
2004-10-27 21:40 ` Kernel 2.6.9 Multiple Page Allocation Failures (Part 2) Justin Piszcz
2004-10-27 21:58 ` Andrew Morton
2004-10-27 21:55 ` Justin Piszcz
2004-10-27 22:19 ` Francois Romieu
2004-10-27 22:23 ` Justin Piszcz
2004-10-28 0:33 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2004-10-25 18:53 Kernel 2.6.9 Page Allocation Failures w/TSO+rollup.patch Chuck Ebbert
2004-10-25 19:03 ` Justin Piszcz
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=417CE49B.4060308@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=jpiszcz@lucidpixels.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 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.