mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org, Marek Szyprowski <m.szyprowski@samsung.com>,
	Andrew Morton <akpm@linux-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)
Date: Mon, 15 Dec 2014 16:28:05 +0900	[thread overview]
Message-ID: <20141215072804.GA4898@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <1418284830.5745.72.camel@intel.com>

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?

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.


  reply	other threads:[~2014-12-15  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  8:00 Huang Ying
2014-12-15  7:28 ` Joonsoo Kim [this message]
2014-12-15  7:29   ` Huang Ying
2014-12-16  2:38 ` Joonsoo 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=20141215072804.GA4898@js1304-P5Q-DELUXE \
    --to=iamjoonsoo.kim@lge.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mingo@kernel.org \
    --cc=ying.huang@intel.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
all inboxes | Powered by JetHome®