From: Geoff Levand <geoffrey.levand@am.sony.com>
To: kexec@lists.infradead.org
Cc: cbe-oss-dev@ozlabs.org
Subject: kexec trouble with gcc-4.3
Date: Thu, 2 Apr 2009 11:40:59 -0700 [thread overview]
Message-ID: <49D506BB.9030409@am.sony.com> (raw)
Hi,
I tried building kexec with gcc-4.3 from the cell sdk-3.1
and the resulting binary didn't work correctly. It works
OK with the gcc-4.1 from the same (sdk-3.1).
Here is the last thing seen, then the system hangs:
Starting new kernel
kexec: waiting for cpu 1 (physical 1) to go down
Invalid tag 26 scanning flattened device tree !
Invalid tag 26 scanning flattened device tree !
Invalid tag 26 scanning flattened device tree !
Does anyone have any ideas?
-Geoff
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2009-04-02 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 18:40 Geoff Levand [this message]
2009-04-03 0:04 ` [Cbe-oss-dev] kexec trouble with gcc-4.3 Michael Ellerman
2009-04-03 2:08 ` Geoff Levand
2009-04-03 2:47 ` Michael Ellerman
2009-06-22 22:08 ` Geoff Levand
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=49D506BB.9030409@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=cbe-oss-dev@ozlabs.org \
--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