Fixed by 67494323f2c782fe3e65c60529fe9dfa613fc500.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818647
Title:
Getting segmentation fault when trying to boot FreeBSD
Status in QEMU:
Fix Committed
Bug description:
wkoszek@wkoszek:~/bin/qemu/qemu$ git log | head -1
commit c886edfb851c0c590d4e77f058f2ec8ed95ad1b5
wkoszek@wkoszek:~/o/freebsd/sys/boot/i386$ qemu-system-sparc64 --version
QEMU emulator version 0.15.50, Copyright (c) 2003-2008 Fabrice Bellard
wkoszek@wkoszek:~/o/freebsd/sys/boot/i386$ uname -a
Linux wkoszek 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:05:41 UTC 2011
i686 i686 i386 GNU/Linux
Qemu built with default settings (./configure --prefix=<path> && make
&& make install)
I run FreeBSD ISO image:
/home/wkoszek/bin/qemu-dynamic/bin/qemu-system-sparc64 -m 1024 -cdrom
~/Pulpit/iso/FreeBSD-7.4-RELEASE-sparc64-bootonly.iso -hda
~/Pulpit/iso/freebsd_sparc64.qcow2 -nographic -boot d
Configuration device id QEMU version 1 machine id 0
kernel cmdline
CPUs: 1 x SUNW,UltraSPARC-IIi
UUID: 00000000-0000-0000-0000-000000000000
Welcome to OpenBIOS v1.0 built on Jul 20 2011 21:17
Type 'help' for detailed information
Trying cdrom:f...
Not a bootable ELF image
Loading a.out image...
Loaded 7680 bytes
entry point is 0x4000
Jumping to entry point 0000000000004000 for type 0000000000000005...
switching to new context: entry point 0x4000 stack 0x00000000ffe86b49
>> FreeBSD/sparc64 boot block
Boot path: cdrom:f
Boot loader: /boot/loader
Consoles: Open Firmware console
Booting with sun4u support.
Boot path set to cdrom:a
FreeBSD/sparc64 bootstrap loader, Revision 1.0
(r...@warner.cse.buffalo.edu, Fri Feb 18 05:38:31 UTC 2011)
bootpath="cdrom:a"
Loading /boot/defaults/loader.conf
/boot/kernel/kernel data=0x8d1f48+0x82f88 syms=[0x8+0x88ec0+0x8+0x76966]
|
Unimplemented service milliseconds ([0] -- [1])
Hit [Enter] to boot immediately, or any other key for command prompt.
Unimplemented service milliseconds ([0] -- [1])
Unimplemented service milliseconds ([0] -- [1])
Unimplemented service milliseconds ([0] -- [1])
Unimplemented service milliseconds ([0] -- [1])
Unimplemented service milliseconds ([0] -- [1])
Unimplemented service milliseconds ([0] -- [1])
I press CTRL + C and I get out of the looped warning about
"unimplemented service". Then I see:
Type '?' for a list of commands, 'help' for more detailed help.
OK boot
jumping to kernel entry at 0xc0078000.
BOOTUnhandled Exception 0x0000000000000034
PC = 0x00000000c0637454 NPC = 0x00000000c0637458
I wanted to start FreeBSD debugging here - I pressed 'CTRL+A c', I was
dropped to the monitor.
FRom the monitor I typed:
Stopping execution
QEMU 0.15.50 monitor - type 'help' for more information
(qemu) x 0xc0078000
00000000c0078000: Cannot access memory
(qemu) x 0x00000000c0637454
00000000c0637454: Cannot access memory
(qemu) x 0x00000000c0637458
00000000c0637458: Cannot access memory
(qemu) xp 0xc0078000
Segmentation fault
IMO it shouldn't have crashed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/818647/+subscriptions
