qemu-system-x86_64 crashed with SIGSEGV

Bug #921961 reported by Michael Vogt
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
qemu-kvm (Ubuntu)
Confirmed
High
Unassigned
Precise
Won't Fix
High
Unassigned

Bug Description

This crash happens consitently on my precise amd64 system when using the auto-upgrade-tester.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: qemu-kvm 1.0+noroms-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Thu Jan 26 09:29:40 2012
ExecutablePath: /usr/bin/qemu-system-x86_64
ExecutableTimestamp: 1327348412
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100922)
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
MachineType: Gigabyte Technology Co., Ltd. EP41-UD3L
ProcCmdline: kvm -hda /var/cache/auto-upgrade-tester/test-image.server -monitor stdio -localtime -no-reboot -net nic,model=virtio -net user -redir tcp:54322::22 -vnc localhost:1 -m 1536
ProcCwd: /home/egon/devel/update-manager/trunk/AutoUpgradeTester
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=6e45e093-05ff-43e4-9525-4206e8840761 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fc23dd0cd00: cmp %rbx,0x28(%rax)
 PC (0x7fc23dd0cd00) ok
 source "%rbx" ok
 destination "0x28(%rax)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: qemu-kvm
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: qemu-system-x86_64 crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-01-13 (12 days ago)
UserGroups:

dmi.bios.date: 11/06/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: EP41-UD3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd11/06/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP41-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP41-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP41-UD3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 if_output (so=0x0, ifm=0x7fc24069d410) at slirp/if.c:80
 ip_output (so=0x0, m0=0x7fc24069d410) at slirp/ip_output.c:84
 bootp_reply (bp=0x7fc24069cdf8, slirp=<optimized out>) at slirp/bootp.c:309
 bootp_input (m=<optimized out>) at slirp/bootp.c:317
 udp_input (m=0x7fc24069cd90, iphlen=<optimized out>) at slirp/udp.c:126

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in qemu-kvm (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Michael Vogt (mvo) wrote :

Fwiw, when I don't run with virtio it appears to be working just fine.
I.e. removing "-net nic,model=virtio" and "-net user"

visibility: private → public
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. confirmed in Precise.

Changed in qemu-kvm (Ubuntu):
importance: Medium → High
status: New → Triaged
tags: added: rls-mgr-p-tracking
Changed in qemu-kvm (Ubuntu Precise):
status: Triaged → Confirmed
tags: added: qa-manual-testing
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

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

Other bug subscribers

Remote bug watches

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