qemu-system-x86_64 crashed with SIGSEGV

Bug #925065 reported by Micah Gersten
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu-kvm (Ubuntu)
New
Undecided
Unassigned

Bug Description

I got this trying to upgrade Firefox in my oneiric VMs on precise.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: qemu-kvm 1.0+noroms-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Jan 31 21:56:30 2012
ExecutablePath: /usr/bin/qemu-system-x86_64
ExecutableTimestamp: 1327348412
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
KvmCmdLine:
 UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
 115 17522 1 0 258884 567872 0 Jan31 ? 00:04:36 /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name sec-natty-amd64 -uuid 5235c533-f314-8cfd-897f-8d9d074befd4 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/sec-natty-amd64.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/opt/vms/kvm/sec-natty-amd64/tmpJLgAVt.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=writeback -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=18,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:36:ee:e4:a4,bus=pci.0,addr=0x3 -usb -vnc 127.0.0.1:2 -vga vmware -device AC97,id=sound0,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
 115 17990 1 0 232271 545592 1 Jan31 ? 00:02:37 /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name sec-natty-i386 -uuid fb3679ec-a39e-4edf-b5a0-5cec30d201ba -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/sec-natty-i386.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/opt/vms/kvm/sec-natty-i386/tmpiy1VvU.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=writeback -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=18,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:36:4e:51:d2,bus=pci.0,addr=0x3 -usb -vnc 127.0.0.1:3 -vga vmware -device AC97,id=sound0,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
MachineType: System76, Inc. Gazelle Professional
ProcCmdline: /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name sec-oneiric-amd64 -uuid 3435fc6c-02f8-2319-27f9-20bbd804ae27 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/sec-oneiric-amd64.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/opt/vms/kvm/sec-oneiric-amd64/disk0.qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=writeback -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=18,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:88:5d:a7,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:0 -vga vmware -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
ProcCwd: /
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic root=UUID=198e494b-64d5-4269-97bc-b08c411b8b60 ro recovery
SegvAnalysis:
 Segfault happened at: 0x7f68012c59ff: or %rbp,(%rsi,%rax,8)
 PC (0x7f68012c59ff) ok
 source "%rbp" ok
 destination "(%rsi,%rax,8)" (0x20007f67d4678f68) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: qemu-kvm
StacktraceTop:
 set_bit (addr=<optimized out>, nr=-4) at ./bitops.h:122
 vnc_dpy_update (ds=<optimized out>, x=-64, y=<optimized out>, w=10, h=<optimized out>) at ui/vnc.c:427
 dpy_update (s=0x7f6802b44780, h=28, w=12, y=160, x=-66) at /build/buildd/qemu-kvm-1.0+noroms/console.h:240
 vmsvga_update_rect (h=28, w=12, y=160, x=-66, s=0x7f6802f42b70) at /build/buildd/qemu-kvm-1.0+noroms/hw/vmware_vga.c:325
 vmsvga_update_rect_flush (s=0x7f6802f42b70) at /build/buildd/qemu-kvm-1.0+noroms/hw/vmware_vga.c:358
Title: qemu-system-x86_64 crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-01-29 (2 days ago)
UserGroups:

dmi.bios.date: 03/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Not Applicable
dmi.board.name: Gazelle Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: gazp6
dmi.chassis.asset.tag: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: gazp6
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd03/21/2011:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp6:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp6:cvnSystem76,Inc.:ct10:cvrgazp6:
dmi.product.name: Gazelle Professional
dmi.product.version: gazp6
dmi.sys.vendor: System76, Inc.

Revision history for this message
Micah Gersten (micahg) wrote :
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for filing this bug. This is a duplicate of 918791, I'll mark it as such.

Note that a workaround is to not use the vmware vga driver, though for some people that is not an acceptable workaround.

I believe this mainly shows up when the unity bar auto-unhides. Perhaps you could avoid it by making the unity bar always visible.

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.