qemu-system-x86_64 crashed with SIGABRT

Bug #1717227 reported by Jean-Baptiste Lallement
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

It crashed when I was running an Ubuntu artful desktop and exited a wayland session

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: qemu-system-x86 1:2.10+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Thu Sep 14 11:52:04 2017
Disassembly: => 0x7fbca727f7af: Cannot access memory at address 0x7fbca727f7af
ExecutablePath: /usr/bin/qemu-system-x86_64
InstallationDate: Installed on 2013-09-03 (1471 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND
MachineType: ASUSTeK COMPUTER INC. UX32VD
ProcCmdline: /usr/bin/qemu-system-x86_64 -m 2G -smp 2 -localtime -no-reboot -cpu core2duo -enable-kvm -drive file=/home/username/tmp.notshared/uefi/disk.img,if=ide,media=disk -boot menu=on -soundhw all -display sdl -vga qxl -enable-kvm -monitor stdio -cdrom /home/username/iso/ubuntu/artful-desktop-amd64.iso
ProcEnviron:
 TERM=screen
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
Signal: 6
SourcePackage: qemu
Stacktrace:
 #0 0x00007fbca727f7af in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7fbc96e22288
StacktraceTop: ?? ()
Title: qemu-system-x86_64 crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32VD.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!

Changed in qemu (Ubuntu):
status: New → Invalid
tags: removed: need-amd64-retrace
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.