From: Abdul Ahad <abdulahad@iwavesystems.com>
To: meta-freescale@yoctoproject.org
Subject: Page allocation error on bulk data transfer
Date: Wed, 18 Feb 2015 17:52:16 +0530 [thread overview]
Message-ID: <54E483F8.2040504@iwavesystems.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
Hi,
I am trying to do Bulk data transfer test with yocto file system,
running on i.mx6 dual-lite board with 512MB RAM.The file size is just
500MB.I ran the test for 24hrs but i am getting following error in the
terminal.
cp: page allocation failure: order:0, mode:0x200020
[2015-02-03 12:31:11.555] CPU: 1 PID: 2692 Comm: cp Not tainted
3.10.17-1.0.0_ga+g2a69800 #3
[2015-02-03 12:31:11.561] [<80014620>] (unwind_backtrace+0x0/0xf4) from
[<80011444>] (show_stack+0x10/0x14)
[2015-02-03 12:31:11.569] [<80011444>] (show_stack+0x10/0x14) from
[<8008e230>] (warn_alloc_failed+0xe0/0x118)
[2015-02-03 12:31:11.578] [<8008e230>] (warn_alloc_failed+0xe0/0x118)
from [<80091044>] (__alloc_pages_nodemask+0x634/0x890)
..
..
..
kworker/u4:1: page allocation failure: order:0, mode:0x200020
[2015-02-03 20:23:58.471] CPU: 1 PID: 9527 Comm: kworker/u4:1 Not
tainted 3.10.17-1.0.0_ga+g2a69800 #3
[2015-02-03 20:23:58.478] Workqueue: writeback bdi_writeback_workfn
(flush-8:0)
..
..
..
aiurdemux0:sink: page allocation failure: order:0, mode:0x200020
[2015-02-04 01:10:56.110] CPU: 0 PID: 23438 Comm: aiurdemux0:sink Not
tainted 3.10.17-1.0.0_ga+g2a69800 #3
[2015-02-04 01:10:56.117] [<80014620>] (unwind_backtrace+0x0/0xf4) from
[<80011444>] (show_stack+0x10/0x14)
..
..
Is there any way to prevent the page allocation error.
I have tried the work around specified in sabresd Linux release notes,
but with out any success.The work around suggested to run the below
command "echo1 > /proc/sys/vm/drop_caches".
Thank you,
Regards,
Abdul Ahad
[-- Attachment #2: Type: text/html, Size: 5039 bytes --]
reply other threads:[~2015-02-18 12:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54E483F8.2040504@iwavesystems.com \
--to=abdulahad@iwavesystems.com \
--cc=meta-freescale@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.