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.
Created attachment 473479[details]
BSOD for DPWDK_Hotreplace_RunHotReplace
Description of problem:
Sub job of "Quiesce system" (under "DPWDK-HotReplace-Device Test-Verify driver support for D3 power state" -> "RunJob-DP-Run Hot-Replace-Device Test(Lib Job) -> "DP-Run HotReplace-Device Test(Lib Job)") fails with getting BSOD.
Version-Release number of selected component (if applicable):
virtio-win-1.1.17
qemu-kvm-0.12.1.2-2.129.el6
kernel-2.6.32-95.el6
How reproducible:
100%
Steps to Reproduce:
1.Start guest with following command:
/usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usbdevice tablet -drive file=win2k8-R2-blk.raw,if=none,id=drive-virtio0,boot=on,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio0,id=virtio-blk-pci0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=00:10:40:3F:21:01,bus=pci.0,addr=0x4 -boot c -uuid ce38b536-49d7-442a-a3c5-c2fc87937211 -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -name win2k8-R2-blk -vnc :1 -drive file=disk1.raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.raw,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.raw,if=none,id=drive-virtio3,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.raw,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4
2.Run job "DPWDK-HotReplace-Device Test-Verify driver support for D3 power state"
Actual results:
Sub job of "Quiesce system" (under "DPWDK-HotReplace-Device Test-Verify driver support for D3 power state" -> "RunJob-DP-Run Hot-Replace-Device Test(Lib Job) -> "DP-Run HotReplace-Device Test(Lib Job)") fails with getting BSOD.
No dump file due to bug 669314, please refer to screen shot in the attachment.
Expected results:
Job should pass without error.
Additional info:
This job only exist on windows 64 and windsow R2.
Verified this issue with the latest driver 1.1.18, it does not reproduce, job of "DPWDK-HotReplace-Device Test-Verify driver support for D3 power state" passed without any error.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0782.html