From: Rudici Cazeao <rudici.cazeao@litepoint.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Running kexec, kernel gets stuck at "Starting new kernel"
Date: Fri, 28 Apr 2017 01:50:57 +0000 [thread overview]
Message-ID: <1fafe0dceb744c8587c3b3a398b46321@LPHQEX2013.litepoint.internal> (raw)
I am running kexec in consecutive loops on 4 different dual-core arm processors. On 3 of these processors, usually, somewhere between the 500th and the 5000th loop, the kernel gets stuck at "Starting new kernel". On the remaining processor, kexec is run over and over without running into this issue. And this appears to be pretty consistent. Any ideas?
Also, on rare occasions, the kernel gets stuck at " Uncompressing Linux... done, booting the kernel".
The SoC is Cortex-A9 (ARMv7-A)
The kernel version is 3.0.51-rt75
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2017-04-28 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 1:50 Rudici Cazeao [this message]
2017-05-01 10:53 ` Running kexec, kernel gets stuck at "Starting new kernel" Pratyush Anand
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=1fafe0dceb744c8587c3b3a398b46321@LPHQEX2013.litepoint.internal \
--to=rudici.cazeao@litepoint.com \
--cc=kexec@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox