From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Subject: Re: Qemu-PPC problems (was [Qemu-devel] Just to add one single point)
Date: Wed, 18 Apr 2007 17:34:14 -0400 [thread overview]
Message-ID: <200704181734.15658.rob@landley.net> (raw)
In-Reply-To: <461E551E.9030803@windriver.com>
On Thursday 12 April 2007 11:49 am, Jason Wessel wrote:
> J. Mayer wrote:
> > On Wed, 2007-04-11 at 17:49 -0400, Rob Landley wrote:
> >
> >> qemu-system-ppc -M prep -nographic -kernel zImage-powerpc -append \
> >> "console=/dev/ttyS0"
...
> While I am sure folks have the objective to be able to boot something
> that is not modified, my objective was to modify the kernel to work with
> qemu until that first objective is met. If you use a 2.6.21rc candidate
> you can use the attached patches to boot. I provided a .config file as
> well. The frame buffer is definitely broken, but I had not really
> looked into why because I was more interested in simply using the ppc
> instruction sets.
Ok, using a qemu CVS snapshot from this morning, I built 2.6.20.6 for powerpc
using the config you attached to the message I'm replying to (ran make
oldconfig on it and hit "enter", and then removed CONFIG_LOCALVERSION_AUTO,
then built with "make ARCH=ppc CROSS_COMPILE=powerpc-" using the cross
compiler I pointed to earlier which is configured for powerpc-unknown-linux.)
Then ran the above qemu line, and qemu segfaulted trying to decompress the
Linux kernel. (Is qemu supposed to segfault? I can reproduce this quite
easily...)
Thinking this might be the "decompresses to >4 megs" problem (your config
produces a HUGE krenel), I then applied your patches to the kernel (the
second is already there in .6, the first needed one hunk fixed up by hand)...
Nope, still segfaults.
> Note I startup with the following and it works perfectly fine with my
> modified kernels:
> qemu-system-ppc -nographic -kernel zImage.prep -s -M prep -append
> "console=ttyS0 ip=dhcp root=/dev/nfs nfsroot=10.0.2.2:/export/ppc rw
> netdev=9,0x300,eth0"
>
> There is a new regression between Apr 9 and Apr 10 in the QEMU CVS HEAD
> where tcp checksums are failing again. :-(
>
> If it would help, I can certainly provide some of my zImage files which
> run with several different 2.6.x kernels.
This seems to be a qemu issue. (It really shouldn't segfault, no matter what
the code it's emulating does.)
What qemu version are you using to run this with?
Rob
--
Penguicon 5.0 Apr 20-22, Linux Expo/SF Convention. Bruce Schneier, Christine
Peterson, Steve Jackson, Randy Milholland, Elizabeth Bear, Charlie Stross...
next prev parent reply other threads:[~2007-04-18 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 10:00 [Qemu-devel] Just to add one single point J. Mayer
2007-04-08 14:11 ` Thiemo Seufer
2007-04-08 16:03 ` J. Mayer
2007-04-08 23:19 ` Paul Brook
2007-04-09 1:22 ` Mike Frysinger
2007-04-09 10:06 ` J. Mayer
2007-04-09 21:26 ` Rob Landley
2007-04-09 22:32 ` J. Mayer
2007-04-11 21:49 ` Rob Landley
2007-04-12 7:56 ` Re:Qemu-PPC problems (was [Qemu-devel] Just to add one single point) J. Mayer
2007-04-12 15:49 ` Qemu-PPC " Jason Wessel
2007-04-12 16:34 ` Jason Wessel
2007-04-12 20:20 ` J. Mayer
2007-04-12 21:23 ` Jason Wessel
2007-04-14 21:28 ` Rob Landley
2007-04-18 21:34 ` Rob Landley [this message]
2007-04-14 19:50 ` 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=200704181734.15658.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).