From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, support@artenumerica.com,
ngalamba@fc.ul.pt, Jens Axboe <axboe@suse.de>
Subject: Re: oom-killer: gfp_mask=0xd1 with 2.6.15.4 on EM64T [previously 2.6.12]
Date: Sun, 05 Mar 2006 02:55:25 +0000 [thread overview]
Message-ID: <440A531D.9050009@artenumerica.com> (raw)
In-Reply-To: <20060304161519.6e6fbe2c.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Andrew Morton wrote:
> We have a candidate fix at
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc5/2.6.16-rc5-mm2/broken-out/x86_64-mm-blk-bounce.patch.
> Could you test that? (and don't alter the Cc: list!). The patch is
> against 2.6.16-rc5.
Thanks! I'll test it in a few hours, after a short "barbaric" test
inspired (perhaps naively) by those call traces: running with a 2.6.15.4
without SCSI cd-rom support (with multiple Gaussian processes, no
oom-killings until now (3 hours)).
Best regards
J Esteves
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-03-05 2:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 17:01 oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T J M Cerqueira Esteves
2006-03-02 9:17 ` Andrew Morton
2006-03-03 15:50 ` J M Cerqueira Esteves
2006-03-04 15:57 ` oom-killer: gfp_mask=0xd1 with 2.6.15.4 on EM64T [previously 2.6.12] J M Cerqueira Esteves
2006-03-05 0:15 ` Andrew Morton
2006-03-05 2:55 ` J M Cerqueira Esteves [this message]
2006-03-05 10:07 ` J M Cerqueira Esteves
2006-03-06 8:47 ` J M Cerqueira Esteves
2006-03-06 9:02 ` Andrew Morton
2006-03-06 18:03 ` Jun'ichi Nomura
2006-03-17 9:47 ` J M Cerqueira Esteves
2006-03-06 9:19 ` J M Cerqueira Esteves
2006-03-06 9:28 ` Andrew Morton
2006-03-06 10:45 ` J M Cerqueira Esteves
2006-03-06 15:56 ` Randy.Dunlap
2006-03-05 0:12 ` oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T Andrew Morton
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=440A531D.9050009@artenumerica.com \
--to=jmce@artenumerica.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ngalamba@fc.ul.pt \
--cc=support@artenumerica.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 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.