From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org, jakub@jermar.eu
Subject: Re: [Qemu-devel] [sparc64] qemu crashes after the "OpenBIOS for Sparc64" banner is printed
Date: Thu, 28 Aug 2008 18:57:16 +0300 [thread overview]
Message-ID: <f43fc5580808280857n2bddbc75td1c41a80b1bbdd50@mail.gmail.com> (raw)
In-Reply-To: <48B6A035.2090105@jermar.eu>
On 8/28/08, Jakub Jermar <jakub@jermar.eu> wrote:
> Hi,
>
> when I build qemu-system-sparc64 from trunk and attempt to
> boot the HelenOS iso image, I immediately get segmentation fault.
> Below is the output from a gdb session, show the place of
> crash:
>
> OpenBIOS for Sparc64
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb7b616b0 (LWP 16553)]
> change_pstate (new_pstate=21) at /home/jermar/install/qemu/target-sparc/op_helper.c:2676
> 2676 pstate_regs = env->pstate & 0xc01;
> (gdb) bt
> #0 change_pstate (new_pstate=21) at /home/jermar/install/qemu/target-sparc/op_helper.c:2676
> #1 0x0814d3b4 in do_interrupt (env=0x83d9bc8) at /home/jermar/install/qemu/target-sparc/helper.c:758
> #2 0x080d6510 in cpu_sparc_exec (env1=0x0) at /home/jermar/install/qemu/cpu-exec.c:320
> #3 0x08055cca in main_loop () at /home/jermar/install/qemu/vl.c:7545
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> 2676 pstate_regs = env->pstate & 0xc01;
> (gdb) print env
> $1 = (struct CPUSPARCState *) 0xbfdb97c8
> (gdb) print env->pstate
> Cannot access memory at address 0xbfdc717c
>
> Since I get this error so early, I think this is a generic issue.
> Anyone else has seen something similar?
>
> I built qemu using gcc-3.3. The arguments I used to run qemu:
> -cdrom image.iso -m 512 -boot d -nographic
>
> Please, respond to me directly as I am not subscribed to the list.
What host? On my amd64 and using the latest OpenBIOS I get this:
boot:
Allocated 8 Megs of memory at 0x40000000 for kernel
Kernel doesn't support loading to high memory, relocating...done.
Loaded kernel version 0.0.0
service close: argument count error (0 0)
HelenOS SPARC64 Bootloader
Release 0.2.0.5, revision exported
Built on 2007-06-18 23:55:43
Copyright (c) 2006 HelenOS project
System info
memory: 512M starting at 0x0000000000000000
Memory statistics
kernel entry point at 0x0000000000400000
0x0000000000008e78: boot info structure
0x00000000000092cc: kernel image (size 459416 bytes)
0x0000000000079564: ns image (size 221421 bytes)
0x00000000000af651: init image (size 221340 bytes)
0x00000000000e56ed: fb image (size 239587 bytes)
0x000000000011fed0: kbd image (size 254904 bytes)
0x000000000015e288: console image (size 404892 bytes)
0x00000000001c1024: tetris image (size 239492 bytes)
0x00000000001fb7a8: tester image (size 238840 bytes)
0x0000000000235ca0: klog image (size 204910 bytes)
Copying components
kernel...done.
ns...done.
init...done.
fb...done.
kbd...done.
console...done.
tetris...done.
tester...done.
klog...done.
Canonizing OpenFirmware device tree...done.
Checking for secondary processors...done.
Booting the kernel...
Using the version in pc-bios it does not get this far, but does not
crash either:
boot:
Allocated 8 Megs of memory at 0x40000000 for kernel
Kernel doesn't support loading to high memory, relocating...done.
Loaded kernel version 0.0.0
service close: argument count error (0 0)
HelenOS SPARC64 Bootloader
Release 0.2.0.5, revision exported
Built on 2007-06-18 23:55:43
Copyright (c) 2006 HelenOS project
Error: no memory detected, halting.
next prev parent reply other threads:[~2008-08-28 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 12:55 [Qemu-devel] [sparc64] qemu crashes after the "OpenBIOS for Sparc64" banner is printed Jakub Jermar
2008-08-28 15:57 ` Blue Swirl [this message]
2008-08-28 16:08 ` Jakub Jermar
2008-08-28 16:30 ` Blue Swirl
2008-08-28 16:59 ` Jakub Jermar
2008-08-28 17:16 ` Blue Swirl
2008-08-28 19:05 ` Blue Swirl
2008-08-29 18:37 ` Blue Swirl
2008-08-29 19:22 ` Paul Brook
2008-08-29 19:54 ` Blue Swirl
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=f43fc5580808280857n2bddbc75td1c41a80b1bbdd50@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=jakub@jermar.eu \
--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).