From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] svn 6658 broke powerpc.
Date: Tue, 17 Mar 2009 18:57:42 -0500 [thread overview]
Message-ID: <200903171857.42875.rob@landley.net> (raw)
Up through svn 6657, I could boot a powerpc kernel with -kernel. That commit
changed it so now it says:
invalid/unsupported opcode: 00 - 00 - 00 (00000000) fff18f00 1
invalid/unsupported opcode: 00 - 00 - 00 (00000000) fff18f04 1
invalid/unsupported opcode: 00 - 0c - 06 (00009198) 00009214 0
And dies.
You can grab a test kernel from http://landley.net/zImage-powerpc and try
booting it (out of the qemu source directory, this is assuming you've built it
but haven't installed it yet) via:
ppc-softmmu/qemu-system-ppc -kernel zImage-powerpc \
-append "console=ttyS0 panic=1" -nographic -no-reboot -L pc-bios
With svn 6657, it works. (You get kernel boot messages up until it panics and
dies because it can't find the root filesystem). With 6658 it dies
immediately with the above error message.
Unfortunately, this means that the 0.10.0 release doesn't work for powerpc for
me, but svn a couple days _before_ the release did.
Rob
next reply other threads:[~2009-03-17 23:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 23:57 Rob Landley [this message]
2009-03-18 8:41 ` [Qemu-devel] svn 6658 broke powerpc Alexander Graf
2009-03-18 18:28 ` Rob Landley
2009-03-18 19:11 ` Blue Swirl
2009-03-19 3:16 ` Rob Landley
2009-03-19 17:48 ` Blue Swirl
2009-03-19 19:30 ` Rob Landley
2009-03-19 19:41 ` Blue Swirl
2009-03-21 9:32 ` Blue Swirl
2009-03-21 18:44 ` Rob Landley
2009-03-22 15:14 ` Blue Swirl
2009-03-22 16:54 ` Blue Swirl
2009-03-25 2:30 ` Rob Landley
2009-03-25 2:39 ` Anthony Liguori
2009-03-25 2:50 ` Anthony Liguori
2009-03-25 4:26 ` M. Warner Losh
2009-03-27 18:59 ` Blue Swirl
2009-03-27 19:41 ` Anthony Liguori
2009-03-28 20:41 ` Rob Landley
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=200903171857.42875.rob@landley.net \
--to=rob@landley.net \
--cc=qemu-devel@nongnu.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).