linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: J M Cerqueira Esteves <jmce@artenumerica.com>
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: Sat, 4 Mar 2006 16:15:19 -0800	[thread overview]
Message-ID: <20060304161519.6e6fbe2c.akpm@osdl.org> (raw)
In-Reply-To: <4409B8DC.9040404@artenumerica.com>

J M Cerqueira Esteves <jmce@artenumerica.com> wrote:
>
> Still on the same dual EM64T machine with a Tyan Tiger i7525 (S2672)
>  motherboard and 4 GB RAM for which I reported 2.6.12 oom killings a few
>  days ago:
> 
>  I upgraded to Ubuntu Dapper and installed its latest 2.6.15 kernel,
>  which incorporates 2.6.15.4.  Started with the original "binary"
>  linux-image-2.6.15-16-amd64-xeon package,
>  and got a few oom killings even without running the same large test
>  programs as before.  Then recompiled the kernel with
>  CONFIG_PREEMPT_NONE, CONFIG_SCHED_SMT, no CONFIG_PREEMPT_BKL,
>  and the dump_stack() call suggested by Andrew Morton for
>  mm/oom_kill.c [in out_of_memory()].
> 
>  Repeated tests with Gaussian... and got oom-killer events similar to
>  those found with 2.6.12.   At
>  http://jmce.artenumerica.org/en/tmp/linux-2.6.15-oom_killings/kern.log
>  are the kernel messages from the killing of two Gaussian runs;
>  I just show below the beginning, until the first killing.
> 
>  Any suggestions on patches or some pre-2.6.16 version I should try?
> 
> 
>  Call Trace:<ffffffff8015efcb>{out_of_memory+23}
>  <ffffffff80130465>{__wake_up+56}
>         <ffffffff80161177>{__alloc_pages+572}
>  <ffffffff8017fc25>{bio_copy_user+219}
>         <ffffffff801debbf>{blk_rq_map_user+133} <ffffffff801e1b61>{sg_io+351}
>         <ffffffff801e1ff8>{scsi_cmd_ioctl+494}
>  <ffffffff80130465>{__wake_up+56}
>         <ffffffff80265aac>{sock_def_readable+52}
>  <ffffffff802c5d68>{unix_dgram_sendmsg+1085}
>         <ffffffff88077e35>{:sd_mod:sd_ioctl+371}
>  <ffffffff801e0058>{blkdev_driver_ioctl+93}
>         <ffffffff801e0726>{blkdev_ioctl+1613}
>  <ffffffff8018ce76>{do_select+1137}
>         <ffffffff8026321e>{sys_sendto+251} <ffffffff8018c941>{__pollwait+0}
>         <ffffffff801813d2>{block_ioctl+27} <ffffffff8018c091>{do_ioctl+33}
>         <ffffffff8018c36c>{vfs_ioctl+643} <ffffffff8018c3e0>{sys_ioctl+91}
>         <ffffffff8010fa46>{system_call+126}
>  oom-killer: gfp_mask=0xd1, order=0

Yup, that looks like the same bug.

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.

  reply	other threads:[~2006-03-05  0:16 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 [this message]
2006-03-05  2:55         ` J M Cerqueira Esteves
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=20060304161519.6e6fbe2c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=jmce@artenumerica.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).