Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Reporter,
Could I please ask you to provide a priority assessment (set the priority field to one of urgent/high/medium/low) for the impact of this issue? This will help us prioritize this issue with our other outstanding bugs for the current release cycle ...
Regards,
Brock
Created attachment 482688[details]
abrt-generated log
I got a similar crash today with qemu-kvm-0.12.1.2-2.149.el6.x86_64 when trying to switch guest from X to console.
Looks like a duplicate, both should be fixed by the latest scratch build with locking fixes (because they remove dropping the global lock when calling the dispatcher, preventing the backtrace present during the crash). For locking fixes see 678208
*** This bug has been marked as a duplicate of bug 674055 ***
Created attachment 480734 [details] backtrace Description of problem: Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.147.el6.x86_64 How reproducible: didn't try to reproduce Additional info: * RHEL 6 x86_64 nightly host / RHEL 6 i386 nightly guest * qemu-kvm cli: qemu-kvm -smp 2 -m 1024 -name rhel6_32 -enable-kvm -spice port=3001,disable-ticketing -soundhw ac97 -vga qxl -device virtio-serial -chardev spicevmc,id=vdagent,debug=0,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 /dev/root_vg/q-rhel6_32 * last messages in CL before crash: handle_dev_destroy_surfaces: red_wait_outgoing_item: blocked handle_dev_destroy_surfaces: red_create_surface: panic surface->context.canvas Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen])