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:46:07 +0400 [thread overview]
Message-ID: <4187494F.5090009@wasp.net.au> (raw)
In-Reply-To: <4187468E.3050709@yahoo.com.au>
Nick Piggin wrote:
>> 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).
>>
>
> OK fair enough.
>
> Here is a rollup of the 3 patches that are supposed to help with
> the problem. It is diffed against 2.6.10-rc1-bk8, which you probably
> wouldn't want to run either.
>
> Not sure how cleanly it will apply onto 2.6.9... shouldn't be too bad
> I think.
>
I'm actually running a reasonably recent BK pull of 2.6.10-rc1 as of a couple of days ago, but I did
some pretty severe testing and evaluation with my raid disks removed and replaced with spares before
I let it loose on the real media. I have applied those patches and I'll beat on it for a few hours
and see how it goes. I have some pretty defined cron jobs that make it easy to reproduce.
Regards,
Brad
prev parent reply other threads:[~2004-11-02 8:46 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
[not found] ` <4187468E.3050709@yahoo.com.au>
2004-11-02 8:46 ` Brad Campbell [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=4187494F.5090009@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.