Description of problem: 1.run qemu-system-i386 with "-sound all" in CentOS5. 2.crash during booting CentOS5. Version-Release number of selected component: qemu-system-x86-1.6.2-1.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: qemu-system-i386 -enable-kvm -smp 2 -hda centOS5-vbox.vdi -vga qxl -m 1G -soundhw all -boot menu=on -spice port=5901,password=*** crash_function: portio_read executable: /usr/bin/qemu-system-i386 kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 portio_read at /usr/src/debug/qemu-1.6.2/ioport.c:176 #5 memory_region_read_accessor at /usr/src/debug/qemu-1.6.2/memory.c:407 #6 access_with_adjusted_size at /usr/src/debug/qemu-1.6.2/memory.c:477 #7 memory_region_dispatch_read1 at /usr/src/debug/qemu-1.6.2/memory.c:944 #8 memory_region_dispatch_read at /usr/src/debug/qemu-1.6.2/memory.c:966 #9 io_mem_read at /usr/src/debug/qemu-1.6.2/memory.c:1742 #10 address_space_rw at /usr/src/debug/qemu-1.6.2/exec.c:2009 #11 address_space_read at /usr/src/debug/qemu-1.6.2/exec.c:2042 #12 cpu_inw at /usr/src/debug/qemu-1.6.2/ioport.c:105 #13 kvm_handle_io at /usr/src/debug/qemu-1.6.2/kvm-all.c:1508
Created attachment 885663 [details] File: backtrace
Created attachment 885664 [details] File: cgroup
Created attachment 885665 [details] File: core_backtrace
Created attachment 885666 [details] File: dso_list
Created attachment 885667 [details] File: environ
Created attachment 885668 [details] File: limits
Created attachment 885669 [details] File: maps
Created attachment 885670 [details] File: open_fds
Created attachment 885671 [details] File: proc_pid_status
Created attachment 885672 [details] File: var_log_messages
Hmm, doesn't seem to reproduce here with x86 kvm. Is this regularly reproducible for you? If so, you can see the output of 'qemu-system-i386 -soundhw' and try each soundcard until you find the out that causes the crash? Also, would be interesting to know if qemu from fedora-virt-preview reproduces the issue as well: https://fedoraproject.org/wiki/Virtualization_Preview_Repository
(In reply to Cole Robinson from comment #11) > Hmm, doesn't seem to reproduce here with x86 kvm. > > Is this regularly reproducible for you? > > If so, you can see the output of 'qemu-system-i386 -soundhw' and try each > soundcard until you find the out that causes the crash? > > Also, would be interesting to know if qemu from fedora-virt-preview > reproduces the issue as well: > > https://fedoraproject.org/wiki/Virtualization_Preview_Repository I think thar I am using regularly reproducible. If I replace '-soundhw all' with '-device AC97', then it will work well. Below is soundcard list I tested. ac97 Intel 82801AA AC97 Audio adlib Yamaha YM3812 (OPL2) cs4231a CS4231A es1370 ENSONIQ AudioPCI ES1370 gus Gravis Ultrasound GF1 hda Intel HD Audio pcspk PC speaker sb16 Creative Sound Blaster 16 Finally, I found with gus soundcard will cause centso5 crash.
Can you try the virt preview repository? Install it, sudo yum update qemu-system-i386, and try to reproduce the issue.
I have try the virt preview repository. But it still crash. And show the error message 'qemu-system-i386: /builddir/build/BUILD/qemu-2.0.0/ioport.c:182: portio_read: Assertion `mrp' failed.'
(In reply to Cole Robinson from comment #13) > Can you try the virt preview repository? Install it, sudo yum update > qemu-system-i386, and try to reproduce the issue. I have try the virt preview repository. But it still crash. And show the error message 'qemu-system-i386: /builddir/build/BUILD/qemu-2.0.0/ioport.c:182: portio_read: Assertion `mrp' failed.'
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Chen_Min_Chin does this still reproduce on F22?
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days