[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1418628591.5745.191.camel@intel.com>
Date: Mon, 15 Dec 2014 15:29:51 +0800
From: Huang Ying <ying.huang@...el.com>
To: Joonsoo Kim <iamjoonsoo.kim@....com>
Cc: Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, lkp@...org,
Marek Szyprowski <m.szyprowski@...sung.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [LKP] [mm] INFO: rcu_sched detected stalls on CPUs/tasks: { 1}
(detected by 0, t=10002 jiffies, g=945, c=944, q=0)
On Mon, 2014-12-15 at 16:28 +0900, Joonsoo Kim wrote:
> On Thu, Dec 11, 2014 at 04:00:30PM +0800, Huang Ying wrote:
> > FYI, we noticed the below changes on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> > commit 6a7d22008b2294f1dacbc77632a26f2142f2d4b0 ("mm: Fix boot crash with f7426b983a6a ("mm: cma: adjust address limit to avoid hitting low/high memory boundary")")
> >
> > The original boot failures are fixed, but there are some boot hang now.
> > Sometimes because of OOM for trinity test.
>
> CCing relevant people.
>
> Hmm... My fix is just work-around to avoid validation when VA to PA
> conversion. So, it would be irrelevant to this problem. Blaming
> original patch makes more sense to me.
>
> Anyway, I looked at the original commit f7426b983a6a and found that
> it doesn't have any effect after reserving CMA region. Attached dmesg
> say that reservation is successful. So I wonder what cause this stall.
> Could you share your config to help debug?
The config is attached.
Best Regards,
Huang, Ying
> And, dmesg log also say that 16 MB is reserved for CMA. Is there any
> possibility this memory reservation cause this stall? Possibly, your
> OOM report is related to this reservation.
>
> Thanks.
>
View attachment "config-3.18.0-02022-g6a7d220" of type "text/x-mpsub" (105534 bytes)
Powered by blists - more mailing lists