From: David Rientjes <rientjes@google.com>
To: Zhang Zhen <zhenzhang.zhang@huawei.com>
Cc: linux-mm@kvack.org, Wang Nan <wangnan0@huawei.com>
Subject: Re: Kernel panic related with OOM-killer
Date: Fri, 9 May 2014 03:33:08 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1405090329360.15089@chino.kir.corp.google.com> (raw)
In-Reply-To: <536C3FC7.2030402@huawei.com>
On Fri, 9 May 2014, Zhang Zhen wrote:
> Hi,
>
> We have a question about Kernel panic related with OOM-killer on an ARM-A15 board.
> But it reproduced randomly.
>
> Does anyone has some issues like this or some suggestion?
> Thank you so much.
>
> The Logs when kernel panic was occurred as follows.
>
> [59313.549221] Killed process 15479 (server) total-vm:9984kB, anon-rss:68kB, file-rss:0kB
> [59318.531080] Out of memory: Kill process 15485 (server) score 0 or sacrifice child
> [59318.618689] Killed process 15485 (server) total-vm:9984kB, anon-rss:68kB, file-rss:0kB
> [59321.839161] Out of memory: Kill process 1339 (portmap) score 0 or sacrifice child
> [59321.926735] Killed process 1339 (portmap) total-vm:1732kB, anon-rss:64kB, file-rss:0kB
> [59327.626410] Kernel panic - not syncing: Out of memory and no killable processes...
This is the key, there are no eligible processes available to kill on the
system. All processes on the system are either kthreads or oom disabled
(their /proc/<pid>/oom_score_adj is -1000), see section 3.1 of
Documentation/filesystems/proc.txt.
--
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>
prev parent reply other threads:[~2014-05-09 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 2:39 Zhang Zhen
2014-05-09 10:33 ` David Rientjes [this message]
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=alpine.DEB.2.02.1405090329360.15089@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=linux-mm@kvack.org \
--cc=wangnan0@huawei.com \
--cc=zhenzhang.zhang@huawei.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