From: Jakub Jermar <jakub@jermar.eu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [sparc64] qemu crashes after the "OpenBIOS for Sparc64" banner is printed
Date: Thu, 28 Aug 2008 14:55:17 +0200 [thread overview]
Message-ID: <48B6A035.2090105@jermar.eu> (raw)
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.
Cheers,
Jakub
next reply other threads:[~2008-08-28 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 12:55 Jakub Jermar [this message]
2008-08-28 15:57 ` [Qemu-devel] [sparc64] qemu crashes after the "OpenBIOS for Sparc64" banner is printed Blue Swirl
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=48B6A035.2090105@jermar.eu \
--to=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).