From: Shuah Khan <shuahkh@osg.samsung.com>
To: Andrew Morton <akpm@linux-foundation.org>,
vbabka@suse.cz, mgorman@techsingularity.net, mhocko@suse.com,
hannes@cmpxchg.org, iamjoonsoo.kim@lge.com,
izumi.taku@jp.fujitsu.com
Cc: LKML <linux-kernel@vger.kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>,
linux-mm@kvack.org
Subject: Linux 4.10-rc2 arm: dmesg flooded with alloc_contig_range: [X, Y) PFNs busy
Date: Tue, 17 Jan 2017 17:23:03 -0700 [thread overview]
Message-ID: <6c67577e-8b72-c958-40af-2096d8840fbe@osg.samsung.com> (raw)
Hi,
dmesg floods with PFNs busy messages.
[10119.071455] alloc_contig_range: [bb900, bbc00) PFNs busy
[10119.071631] alloc_contig_range: [bba00, bbd00) PFNs busy
[10119.071762] alloc_contig_range: [bbb00, bbe00) PFNs busy
[10119.071940] alloc_contig_range: [bbc00, bbf00) PFNs busy
[10119.072039] alloc_contig_range: [bbd00, bc000) PFNs busy
[10119.072188] alloc_contig_range: [bbe00, bc100) PFNs busy
[10119.072301] alloc_contig_range: [bbf00, bc200) PFNs busy
[10119.072403] alloc_contig_range: [bc000, bc300) PFNs busy
[10119.072549] alloc_contig_range: [bc100, bc400) PFNs busy
[10119.072584] [drm:exynos_drm_gem_create] *ERROR* failed to allocate buffer.
I think this is triggered when drm tries to allocate CMA buffers.
I might have seen one or two messages in 4.9, but since 4.10, it
just floods dmesg.
Is this a known problem? I am seeing this on odroid-xu4
Linux odroid 4.10.0-rc2-00251-ge03c755-dirty #12 SMP PREEMPT
Wed Jan 11 23:12:52 UTC 2017 armv7l armv7l armv7l GNU/Linux
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com
--
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 reply other threads:[~2017-01-18 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 0:23 Shuah Khan [this message]
2017-01-20 13:34 ` Vlastimil Babka
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=6c67577e-8b72-c958-40af-2096d8840fbe@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/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