FWIW:
Program received signal SIGINT, Interrupt.
0xb644f73c in seqlock_read_retry (sl=0xb6b2acc8 <timers_state+16>, start=0)
at /tmp/qemu/include/qemu/seqlock.h:69
69 return unlikely(atomic_read(&sl->sequence) != start);
(gdb) bt
#0 0xb644f73c in seqlock_read_retry (sl=0xb6b2acc8 <timers_state+16>, start=0)
at /tmp/qemu/include/qemu/seqlock.h:69
#1 0xb644fa3c in cpu_get_icount () at /tmp/qemu/cpus.c:182
#2 0xb644f518 in cpu_get_host_ticks () at /tmp/qemu/include/qemu/timer.h:1006
#3 0xb644fcc4 in cpu_enable_ticks () at /tmp/qemu/cpus.c:252
#4 0xb658a9ec in vm_start () at vl.c:764
#5 0xb6597200 in main (argc=5, argv=0xbecfa6b4, envp=0xbecfa6cc) at vl.c:4651
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
Confirmed
Status in Linaro QEMU:
New
Bug description:
If you apply some workarounds for bug 870990, bug 883133 and bug
883136 QEMU still cannot boot the i386
debian_squeeze_i386_standard.qcow2 image from
http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot
but something causes the system to reset just before display of the
blue-background grub menu, so we go round in a loop forever. This
image boots OK on i386 hosted qemu so this indicates some kind of ARM-
host specific bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
