[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100125111948.493B.A69D9226@jp.fujitsu.com>
Date: Mon, 25 Jan 2010 11:37:25 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: "A. Boulan" <arnaud.boulan@...ertysurf.fr>
Cc: kosaki.motohiro@...fujitsu.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [Bug #14933] OOM killer unexpectedly called
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14933
> Subject : OOM killer unexpectedly called
> Submitter : A. Boulan <arnaud.boulan@...ertysurf.fr>
> Date : 2009-12-24 23:42 (32 days old)
> References : http://marc.info/?l=linux-kernel&m=126169821317492&w=4
Boulan, Can you please help our debugging?
can you disable following config option at once?
1. CONFIG_DRM_I915
2. CONFIG_RELAY
3. CONFIG_MSPEC
4. VIDEOBUF_DMA_SG
I mean
- if anyone return VM_FAULT_OOM, this issue occur.
- very few subsys can return VM_FAULT_OOM in their own fault handler.
- I hope investigate this is core mm issue or not.
(unfortunatelly, I haven't find any dubious recent mm change..)
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists