Linaro Image Tools

qemu fatal cp15 message report and image creation block

Bug #694059 reported by Spring Zhang
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Linaro Image Tools
Invalid
Undecided
Unassigned
qemu-kvm (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Won't Fix
Undecided
Unassigned

Bug Description

1. qemu version is 0.12.2, after updating to qemu 0.12.3, the issue still exists.
2. Change a former daily build image, linaro image tools can work.

Log:
Installing (apt-get) ../dailybuild/20101224/hwpack_linaro-imx51_20101223-0_armel_unsupported.tar.gz in target rootfs.
qemu: fatal: cp15 insn ee1d6f70

R00=4009f960 R01=42084850 R02=0d696914 R03=00014d3c
R04=0001d118 R05=00000000 R06=0001f291 R07=42084870
R08=000a305c R09=00000000 R10=4009f000 R11=00000000
R12=0001502c R13=4007f7e8 R14=4008f398 R15=4008ae2c
PSR=20000030 --C- T usr32

image:
hwpack_linaro-imx51_20101223-0_armel_unsupported.tar.gz
linaro-natty-headless-tar-20101224-0.tar.gz

See original description
Spring Zhang (qzhang)
description: updated
Revision history for this message
Peter Maydell (pmaydell) wrote :

This is the Thumb2 instruction MRC p15, 0, r6, c13, c0, 3 (which is accessing a thread / process ID register)

This is fixed in qemu 0.13 by this commit:
http://git.qemu.org/qemu.git/commit/?id=f101cd885ec148761738638ae42f7c5162b6d445

You need to use a newer qemu.

Revision history for this message
Spring Zhang (qzhang) wrote :

After update to 0.13, there is no that error message

Guilherme Salgado (salgado)
Changed in linaro-image-tools:
status: New → Invalid
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

This also happens with Maverick, as we're using 0.12.5+noroms-0ubuntu7.1. Would be good to have it fixed in order to create natty rootfs with rootstock.

Steve Langasek (vorlon)
Changed in qemu-kvm (Ubuntu):
status: New → Fix Released
Changed in qemu-kvm (Ubuntu Maverick):
status: New → Triaged
Revision history for this message
Tully (tully.foote) wrote :

I still get this when running 0.13.91 on lucid from the Nova Core PPA https://launchpad.net/~nova-core/+archive/trunk?field.series_filter=lucid

tfoote@bis:/tmp/qemu$ sudo build-arm-chroot natty /tmp/arm_natty3
.......
I: Running command: chroot /tmp/arm_natty3 /debootstrap/debootstrap --second-stage
qemu: fatal: cp15 insn ee1d6f70

R00=4009f960 R01=420822e8 R02=0d696914 R03=000086a8
R04=00008ef0 R05=00000000 R06=000097c9 R07=42082308
R08=00020040 R09=00000000 R10=4009f000 R11=00000000
R12=00008b88 R13=4007f868 R14=4008f450 R15=4008aea0
PSR=20000030 --C- T usr32
^C^C^C^C^Z
[1]+ Stopped sudo build-arm-chroot natty /tmp/arm_natty3
tfoote@bis:/tmp/qemu$ sudo killall build-arm-chroot
[sudo] password for tfoote:
tfoote@bis:/tmp/qemu$ fg
sudo build-arm-chroot natty /tmp/arm_natty3
Terminated
tfoote@bis:/tmp/qemu$ qemu --version
QEMU emulator version 0.13.91 (qemu-kvm-0.14.0-rc1), Copyright (c) 2003-2008 Fabrice Bellard
tfoote@bis:/tmp/qemu$ sudo build-arm-chroot lucid /tmp/arm_lucid

Revision history for this message
Peter Maydell (pmaydell) wrote :

The 'qemu' binary (which is for x86 and kvm) is not always the same version as the one used for ARM user-mode emulation (and in particular it is in a different package for newer Ubuntu releases). What is the output of:
 qemu-arm-static -h | grep version

?

Revision history for this message
Steve Langasek (vorlon) wrote :

> I still get this when running 0.13.91 on lucid from the Nova Core PPA
> https://launchpad.net/~nova-core/+archive/trunk?field.series_filter=lucid

Well, please report the issue to the maintainers of that ppa. This is a bug report about the Ubuntu package, where the issue has been fixed by the inclusion of an up-to-date qemu version.

Revision history for this message
Tully (tully.foote) wrote :

Indeed it is using the older version of qemu-arm, see below. I'll work on upgrading that to get around this.

$ qemu-arm-static -h | grep version
qemu-arm version 0.12.3 (qemu-kvm-0.12.3), Copyright (c) 2003-2008 Fabrice Bellard

Revision history for this message
Rolf Leggewie (r0lf) wrote :

maverick has seen the end of its life and is no longer receiving any updates. Marking the maverick task for this ticket as "Won't Fix".

Changed in qemu-kvm (Ubuntu Maverick):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.