From: Minchan Kim <minchan.kim@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: Jody Belka <jody+lkml@jj79.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: OOM killer, page fault
Date: Sat, 7 Nov 2009 00:14:26 +0900 [thread overview]
Message-ID: <28c262360911060714h16cf55dfibbecc090c76341ab@mail.gmail.com> (raw)
In-Reply-To: <20091106133833.GA23151@gamma.logic.tuwien.ac.at>
On Fri, Nov 6, 2009 at 10:38 PM, Norbert Preining <preining@logic.at> wrote:
> Hi Kim,
>
> On Fr, 06 Nov 2009, preining wrote:
>> Recompiling already and trying to recreate the oom-killer boom.
>
> Well, after rebooting into that kernel I get *loads*, every few seconds,
> of warnings in the log. Hard to sort out what is real. Is that expected?
I guess it is VM_FAULT_NOPAGE of i915_gem or somethings.
It's not of our concern but VM_FAULT_OOM.
I couldn't expect that. So let's change debug patch following as.
Most important thing is "Who return VM_FAULT_OOM".
It it return VM_FAULT_OOM, OOM killer will kill any process who have a
high score. In case of you, it was 'X'.
If you don't see it until 2.6.32-rc5, It should be regression in somewhere.
If we can know it, we can pass the problem to maintainer of it.
Could you try it again below patch?
If you reproduce it, you can match function address of log with
function address
of your System.map. Pz, let me know it. :)
diff --git a/mm/memory.c b/mm/memory.c
index 7e91b5f..97a6fcb 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -2713,8 +2713,13 @@ 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))) {
+ if (ret & VM_FAULT_OOM) {
+ printk(KERN_DEBUG "fault handler : 0x%lx\n", vma->vm_ops->fault);
+
+ }
return ret;
+ }
if (unlikely(PageHWPoison(vmf.page))) {
if (ret & VM_FAULT_LOCKED)
>
> Excerpt from the log:
> [ 2077.753841] vma->vm_ops->fault : 0xffffffff811df4bd
> [ 2077.753842] ------------[ cut here ]------------
> [ 2077.753845] WARNING: at mm/memory.c:2722 __do_fault+0x89/0x382()
> [ 2077.753847] Hardware name: VGN-Z11VN_B
> ...
> [ 2077.753880] Pid: 4892, comm: Xorg Tainted: G W 2.6.32-rc6 #5
> [ 2077.753881] Call Trace:
> [ 2077.753884] [<ffffffff8108c6cc>] ? __do_fault+0x89/0x382
> [ 2077.753887] [<ffffffff8108c6cc>] ? __do_fault+0x89/0x382
> [ 2077.753889] [<ffffffff8103ae54>] ? warn_slowpath_common+0x77/0xa3
> [ 2077.753892] [<ffffffff8108c6cc>] ? __do_fault+0x89/0x382
> [ 2077.753895] [<ffffffff81341a82>] ? _spin_unlock+0x23/0x2f
> [ 2077.753898] [<ffffffff8108e5d0>] ? handle_mm_fault+0x2b9/0x608
> [ 2077.753900] [<ffffffff810af792>] ? do_vfs_ioctl+0x443/0x47b
> [ 2077.753903] [<ffffffff81026759>] ? do_page_fault+0x25f/0x27b
> [ 2077.753906] [<ffffffff81341e8f>] ? page_fault+0x1f/0x30
> [ 2077.753908] ---[ end trace d3324ef5061f0136 ]---
>
> hundreds/thousands of them.
>
> And even without starting anything else. Is that what you want?
> My syslog file has grown to some hundred megabytes ...
>
>
> Best wishes
>
> Norbert
>
> -------------------------------------------------------------------------------
> Dr. Norbert Preining Associate Professor
> JAIST Japan Advanced Institute of Science and Technology preining@jaist.ac.jp
> Vienna University of Technology preining@logic.at
> Debian Developer (Debian TeX Task Force) preining@debian.org
> gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
> -------------------------------------------------------------------------------
> LARGOWARD (n.)
> Motorists' name for the kind of pedestrian who stands beside a main
> road and waves on the traffic, as if it's their right of way.
> --- Douglas Adams, The Meaning of Liff
>
--
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-06 15:16 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
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 [this message]
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=28c262360911060714h16cf55dfibbecc090c76341ab@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=jody+lkml@jj79.org \
--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