qemu-system-arm crashed with SIGABRT in cpu_abort()

Bug #1062220 reported by Duzy Chan on 2012-10-05
This bug affects 6 people
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
qemu-linaro (Ubuntu)

Bug Description

-kernel u-boot.bin

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: qemu-system 1.2.0-2012.09-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 5 19:30:23 2012
ExecutablePath: /usr/bin/qemu-system-arm
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110804)
ProcCmdline: qemu-system-arm -M versatilepb -kernel u-boot.bin
Signal: 6
SourcePackage: qemu-linaro
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: qemu-system-arm crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-08-11 (54 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Duzy Chan (duzy) wrote :

 cpu_abort (env=env@entry=0x7f7603204b78, fmt=fmt@entry=0x7f7600a056f0 "Trying to execute code outside RAM or ROM at 0x%08x\n") at /build/buildd/qemu-linaro-1.2.0-2012.09/exec.c:1774
 get_page_addr_code (env1=0x7f7603204b78, env1@entry=0xffffffffffff4bc2, addr=addr@entry=4294903824) at /build/buildd/qemu-linaro-1.2.0-2012.09/cputlb.c:340
 tb_find_slow (flags=<optimized out>, pc=4294903824, env=0xffffffffffff4bc2, cs_base=<optimized out>) at /build/buildd/qemu-linaro-1.2.0-2012.09/cpu-exec.c:96
 tb_find_fast (env=0xffffffffffff4bc2) at /build/buildd/qemu-linaro-1.2.0-2012.09/cpu-exec.c:152
 cpu_arm_exec (env=0xffffffffffff4bc2, env@entry=0x7f7603204b78) at /build/buildd/qemu-linaro-1.2.0-2012.09/cpu-exec.c:569

Changed in qemu-linaro (Ubuntu):
importance: Undecided → Medium
summary: - qemu-system-arm crashed with SIGABRT in raise()
+ qemu-system-arm crashed with SIGABRT in cpu_abort()
tags: removed: need-amd64-retrace
tags: added: raring running-unity
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in qemu-linaro (Ubuntu):
status: New → Confirmed
information type: Private → Public
Serge Hallyn (serge-hallyn) wrote :

Marked as affecting Ubuntu's qemu package, as bug 1103405 (a dup of this one) happened with the new qemu, not qemu-linaro, package.

Changed in qemu (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Peter Maydell (pmaydell) wrote :

qemu-system-arm -M versatilepb -kernel u-boot.bin
Trying to execute code outside RAM or ROM

This almost always means that you tried to execute a guest binary which wasn't for the VersatilePB. Without more info about exactly what this u-boot.bin file was this bug report can't progress any further.

Serge Hallyn (serge-hallyn) wrote :

Marking incomplete pending more information about the origin of u-boot.bin per comment #8.

Changed in qemu (Ubuntu):
status: Confirmed → Incomplete
Changed in qemu-linaro (Ubuntu):
status: Confirmed → Incomplete
tags: added: trusty
tags: added: utopic
Kurt Huwig (k-huwig-f) wrote :

Also happens on wily when running

$ qemu-system-arm -machine realview-pb-a8

Peter Maydell (pmaydell) wrote :

#10: if that's your entire command line then that's expected behaviour, and is saying "we just executed a pile of zeros and fell off the end of RAM". You need to supply a kernel to run.

Peter Maydell (pmaydell) wrote :

In the upcoming QEMU 2.7 we've removed the abort() call in this code path, and instead will print an error message which hopefully is clearer at suggesting to users where they've gone wrong rather than implying that this is a QEMU bug:

qemu-system-arm: Trying to execute code outside RAM or ROM at 0x08000000
This usually means one of the following happened:

(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)
(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end
(3) Your guest kernel has a bug and crashed by jumping off into nowhere

This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.
If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.

Execution cannot continue; stopping here.


So I'm going to mark this bug as fix-committed, at least for upstream QEMU.

Changed in qemu:
status: New → Fix Committed
Thomas Huth (th-huth) on 2017-01-17
Changed in qemu:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers