From: Minchan Kim <minchan.kim@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Norbert Preining <preining@logic.at>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: OOM killer, page fault
Date: Mon, 2 Nov 2009 15:35:00 +0900 [thread overview]
Message-ID: <20091102153500.78d4f862.minchan.kim@barrios-desktop> (raw)
In-Reply-To: <20091102140216.02567ff8.kamezawa.hiroyu@jp.fujitsu.com>
On Mon, 2 Nov 2009 14:02:16 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Mon, 2 Nov 2009 13:56:40 +0900
> Minchan Kim <minchan.kim@gmail.com> wrote:
>
> > On Mon, 2 Nov 2009 13:24:06 +0900 (JST)
> > KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> >
> > > Hi,
> > >
> > > (Cc to linux-mm)
> > >
> > > Wow, this is very strange log.
> > >
> > > > Dear all,
> > > >
> > > > (please Cc)
> > > >
> > > > With 2.6.32-rc5 I got that one:
> > > > [13832.210068] Xorg invoked oom-killer: gfp_mask=0x0, order=0, oom_adj=0
> > >
> > > order = 0
> >
> > I think this problem results from 'gfp_mask = 0x0'.
> > Is it possible?
> >
> > If it isn't H/W problem, Who passes gfp_mask with 0x0?
> > It's culpit.
> >
> > Could you add BUG_ON(gfp_mask == 0x0) in __alloc_pages_nodemask's head?
> >
>
> Maybe some code returns VM_FAULT_OOM by mistake and pagefault_oom_killer()
> is called. digging mm/memory.c is necessary...
I suspect GPU drivers related to X.
It seems many of them returs VM_FAULT_OOM.
If it happens by file map fault, following debug patch can show the culpit.
Norbert, Could you apply this patch and test again?
If you can get the address, you can find function symbol with System.map.
diff --git a/mm/memory.c b/mm/memory.c
index 7e91b5f..47e4b15 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -2713,7 +2713,11 @@ static int __do_fault(struct mm_struct *mm, struct vm_area_struct *vma,
vmf.page = NULL;
ret = vma->vm_ops->fault(vma, &vmf);
- if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE)))
+ if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE))) {
+ printk(KERN_DEBUG "vma->vm_ops->fault : 0x%lx\n", vma->vm_ops->fault);
+ WARN_ON(1);
+
+ }
return ret;
if (unlikely(PageHWPoison(vmf.page))) {
--
Kind regards,
Minchan Kim
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-11-02 6:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091030063216.GA30712@gamma.logic.tuwien.ac.at>
2009-11-02 4:24 ` KOSAKI Motohiro
2009-11-02 4:56 ` Minchan Kim
2009-11-02 5:02 ` KAMEZAWA Hiroyuki
2009-11-02 6:01 ` Minchan Kim
2009-11-02 16:26 ` Hugh Dickins
2009-11-02 23:28 ` Minchan Kim
2009-11-02 6:35 ` Minchan Kim [this message]
2009-11-02 14:19 ` Norbert Preining
2009-11-02 14:40 ` Minchan Kim
2009-11-05 13:21 ` Norbert Preining
2009-11-05 15:19 ` Minchan Kim
2009-11-05 15:26 ` Norbert Preining
2009-11-05 16:16 ` Norbert Preining
2009-11-05 20:37 ` Jody Belka
2009-11-05 22:18 ` Minchan Kim
2009-11-06 0:01 ` Norbert Preining
2009-11-06 13:38 ` Norbert Preining
2009-11-06 15:14 ` Minchan Kim
2009-11-06 15:18 ` Norbert Preining
2009-11-02 6:59 ` KOSAKI Motohiro
2009-11-02 7:00 ` Minchan Kim
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=20091102153500.78d4f862.minchan.kim@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=preining@logic.at \
/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