From: Brad Campbell <brad@wasp.net.au>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-rc1-bk page allocation failure. order:2, mode:0x20
Date: Tue, 02 Nov 2004 12:18:06 +0400 [thread overview]
Message-ID: <418742BE.4040200@wasp.net.au> (raw)
In-Reply-To: <41873F38.7030609@yahoo.com.au>
Nick Piggin wrote:
> Brad Campbell wrote:
>
>> G'day all,
>>
>> I'm still getting quite a lot of these come up in the logs when the
>> system is under mild load.
>> I suspect it might have something to do with running an MTU of 9000 on
>> the main ethernet port which is directly feeding a workstation with an
>> NFS root (and thus gets quite a high load at times)
>>
>> It's not so much an issue but it does cause the workstation to stall
>> for up to a second while it waits for data every time it occurs.
>>
>> The loaded ethernet port is this one on an PCI card
>>
>> 0000:00:0d.0 Ethernet controller: Marvell Technology Group Ltd. Yukon
>> Gigabit Ethernet 10/100/1000Base-T Adapter (rev 12)
>>
>> This started rearing its ugly head when I moved from 2.6.5 to
>> 2.6.9-preX and persists with BK as of about 2 days ago.
>>
>
> There are patches in the newest -mm kernels that should help the
> problem. If you're willing to test them, the feedback would be
> welcome.
Always willing to test specific patches. Can I just grab the broken out patches, or pull some
specific csets from a bk tree? I'm not particularly keen on running an -mm kernel on this box if I
can avoid it (It's a server in 24hr use with 2.5TB of data where the backup media is 7,000km away).
Regards,
Brad
next prev parent reply other threads:[~2004-11-02 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 7:16 2.6.10-rc1-bk page allocation failure. order:2, mode:0x20 Brad Campbell
2004-11-02 8:03 ` Nick Piggin
2004-11-02 8:18 ` Brad Campbell [this message]
[not found] ` <4187468E.3050709@yahoo.com.au>
2004-11-02 8:46 ` Brad Campbell
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=418742BE.4040200@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.