From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: KEXEC on ARM cortex-a15
Date: Mon, 19 Nov 2012 15:13:28 +0000 [thread overview]
Message-ID: <20121119151327.GG3205@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20121119144417.GH3290@n2100.arm.linux.org.uk>
On Mon, Nov 19, 2012 at 02:44:17PM +0000, Russell King - ARM Linux wrote:
> On Mon, Nov 19, 2012 at 07:57:10PM +0530, Naresh Bhat wrote:
> > I can see the below question on dmesg "No ATAGs ?"
> > ...........
> > ...............
> > CPU1: Unknown IPI message 0x1
> > Brought up 2 CPUs
> > SMP: Total of 2 processors activated (3981.31 BogoMIPS).
> > NET: Registered protocol family 16
> > No ATAGs?
>
> That is the procfs initialization of ATAGs producing that message. If
> you're not booting with ATAGs but instead using DT, then you will get
> this message, and it's harmless... in which case kexec should be passing
> the DT blob to the next kernel.
>
> If it isn't, then its a kexec bug.
Naresh, please try using a bleeding-edge copy of kexec tools. Support
for device-tree on ARM was only added there in the last month or so.
Will
next prev parent reply other threads:[~2012-11-19 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 14:27 KEXEC on ARM cortex-a15 Naresh Bhat
2012-11-19 14:44 ` Russell King - ARM Linux
2012-11-19 15:13 ` Will Deacon [this message]
2012-11-19 15:38 ` Naresh Bhat
2012-11-20 15:02 ` Naresh Bhat
2012-11-20 16:02 ` Will Deacon
2012-11-20 17:14 ` Naresh Bhat
2012-11-21 8:21 ` Naresh Bhat
2012-11-21 10:22 ` Will Deacon
2012-11-21 11:20 ` Naresh Bhat
2012-11-21 18:47 ` Naresh Bhat
2012-12-17 13:11 ` Naresh Bhat
2013-01-10 12:12 ` Naresh Bhat
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=20121119151327.GG3205@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).