qemu-system-arm crashed with SIGSEGV in subpage_register()

Bug #571432 reported by sam tygier on 2010-04-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu-kvm (Ubuntu)

Bug Description

Binary package hint: qemu-kvm

i think this is the crash behind Bug #570588 not sure why apport did not trigger before

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: qemu-kvm-extras 0.12.3+noroms-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: openafs
Architecture: amd64
Date: Wed Apr 28 21:30:13 2010
ExecutablePath: /usr/bin/qemu-system-arm
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=52d7f930-7148-4978-825e-71fcb9243ac6 ro quiet splash
ProcCmdline: qemu-system-arm -M versatilepb -cpu cortex-a8 -kernel /tmp/tmp.B2CtSo2g2u/qemu-vmlinuz -no-reboot -nographic -pidfile /tmp/tmp.B2CtSo2g2u/qemu.pid -drive file=/tmp/tmp.B2CtSo2g2u/qemu-armel-201004282122.img,aio=native,cache=none -m 512 -append console=ttyAMA0,115200n8\ root=/dev/sda\ rw\ mem=256M\ devtmpfs.mount=0\ init=/bin/installer\ quiet
 Segfault happened at: 0x51058e <subpage_register+158>: cmpq $0x0,(%rdx)
 PC (0x0051058e) ok
 source "$0x0" ok
 destination "(%rdx)" (0x40cc28c0) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: qemu-kvm
 subpage_register (mmio=0x7f841b26d010, start=<value optimised out>,
 subpage_init (base=268500992, phys=0x1d47400,
 cpu_register_physical_memory_offset (
 smc91c111_init (nd=0xc41b60, base=1087121600,
 versatile_init (ram_size=<value optimised out>,
Title: qemu-system-arm crashed with SIGSEGV in subpage_register()

dmi.bios.date: 11/07/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: S2696
dmi.board.vendor: Tyan Computer Corporation
dmi.chassis.type: 6
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/07/2007:svn:pn:pvr:rvnTyanComputerCorporation:rnS2696:rvr:cvn:ct6:cvr:

sam tygier (samtygier) wrote :
visibility: private → public

 subpage_register (mmio=0x7f841b26d010, start=<value optimized out>,
 subpage_init (base=268500992, phys=0x1d47400,
 cpu_register_physical_memory_offset (
 smc91c111_init (nd=0xc41b60, base=1087121600,
 versatile_init (ram_size=<value optimized out>,

Changed in qemu-kvm (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Serge Hallyn (serge-hallyn) wrote :

I wonder whether this could be related to

http://<email address hidden>/msg31299.html

Serge Hallyn (serge-hallyn) wrote :

Does boot succeed if you add

    -net nic,model=rtl8139

to your qemu-system-arm arguments?

Changed in qemu-kvm (Ubuntu):
status: New → Incomplete
sam tygier (samtygier) wrote :

that did not seem to help:

I: linux-image- download complete
I: Setting up serial tty in image
I: Getting Virtual Machine kernel from the server
I: Switching to Virtual Machine for second stage processing
Adding `local diversion of /usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.rootstock'
modprobe: FATAL: Could not load /lib/modules/2.6.32-21-versatile/modules.dep: No such file or directory

eth0: ERROR while getting interface flags: No such device
E: Second stage build in Virtual Machine failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
./usr/bin/rootstock: line 54: 28811 Killed qemu-system-arm $QEMUOPTS -append "${APPEND}" > $QEMUFIFO 2>&1
I: A logfile was saved as /data/beagleboard/ubuntu-lucid/build/rootstock-201006261145.log
I: done ...
mkimage: Can't open ./vmlinuz-*: No such file or directory

sam tygier (samtygier) wrote :

the actual qemu output from:
qemu-system-arm -M versatilepb -cpu cortex-a8 -kernel qemu-vmlinuz -no-reboot -nographic -drive file=qemu-armel-201006261210.img,aio=native,cache=none -m 256 -net nic,model=rtl8139 -append "console=ttyAMA0,115200n8 root=/dev/sda rw mem=256M devtmpfs.mount=0 init=/bin/installer"

[ 5.269126] Freeing init memory: 152K
I: Starting basic services in VM
Adding `local diversion of /usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.rootstock'
modprobe: FATAL: Could not load /lib/modules/2.6.32-21-versatile/modules.dep: No such file or directory

eth0: ERROR while getting interface flags: No such device
[ 8.454660] Kernel panic - not syncing: Attempted to kill init!
[ 8.455793] [<c0035b38>] (unwind_backtrace+0x0/0xe4) from [<c03fd3b0>] (dump_stack+0x20/0x24)
[ 8.456087] [<c03fd3b0>] (dump_stack+0x20/0x24) from [<c03fd408>] (panic+0x54/0x124)
[ 8.456376] [<c03fd408>] (panic+0x54/0x124) from [<c005911c>] (forget_original_parent+0x94/0x264)
[ 8.456647] [<c005911c>] (forget_original_parent+0x94/0x264) from [<c005930c>] (exit_notify+0x20/0x14c)
[ 8.456925] [<c005930c>] (exit_notify+0x20/0x14c) from [<c00596a0>] (do_exit+0x268/0x2e4)
[ 8.457179] [<c00596a0>] (do_exit+0x268/0x2e4) from [<c00597a8>] (do_group_exit+0x8c/0xbc)
[ 8.457432] [<c00597a8>] (do_group_exit+0x8c/0xbc) from [<c00597f8>] (sys_exit_group+0x20/0x28)
[ 8.457713] [<c00597f8>] (sys_exit_group+0x20/0x28) from [<c002ea40>] (ret_fast_syscall+0x0/0x2c)

sam tygier (samtygier) wrote :

looks like i dont have much choice of nic on arm.

sam@oberon:/data/beagleboard/ubuntu-lucid/build/qemu-test2$ qemu-system-arm -net nic,model=?
qemu: Supported NIC models: smc91c111
sam@oberon:/data/beagleboard/ubuntu-lucid/build/qemu-test2$ qemu-system-x86_64 -net nic,model=?
qemu: Supported NIC models: ne2k_pci,i82551,i82557b,i82559er,rtl8139,e1000,pcnet,virtio

sam tygier (samtygier) wrote :

i had a try with qemu 0.12.4+noroms-0ubuntu3 but it did not help

cmchao (cmchao) wrote :

The base address is a little strange
By your StackTrace.log, the base address, passed into smc91c111_init, is 0x40CC28C0. But this address should be 0x1001000, hard-coded in source code.

Peter Maydell (pmaydell) wrote :

This bug doesn't seem to have any reproduction instructions, and at least some of the command lines seem to be asking for 512MB of RAM on a versatilepb model, which isn't supported and will crash the guest unhelpfully. I'm marking it 'incomplete' for QEMU...

Changed in qemu:
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.]

Changed in qemu-kvm (Ubuntu):
status: Incomplete → Expired
Peter Maydell (pmaydell) wrote :

Closing as invalid for QEMU because it's an Incomplete bug against an ancient QEMU version.

Changed in qemu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers