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.

Description of problem:
BSOD happened after S4 when running sub job "CHOAS-Concurrent Hardware And OS Test" -> "RunJob-Pnpdtest with concurrent IO in parallel with DevPathExer-Library Job" ->"Run Pnpdtest"/"Run pwrtest"/"Run DevPathExer".

Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1-23
kernel-2.6.32-232.el6.x86_64
qemu-kvm-0.12.1.2-2.227.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Run job "CHOAS-Concurrent Hardware And OS Test" -> "RunJob-Pnpdtest with concurrent IO in parallel with DevPathExer-Library Job" ->"Run Pnpdtest"/"Run pwrtest"/"Run DevPathExer".

Actual results:
BSOD happened after S4 when running sub job "Run Pnpdtest".
Please refer to the attached cpk file "win7-32-blk-23-fail-CHAOS.cpk" and pic "win7-32-BSOD-CHAOS.png" and "Win7-32-CHOAS-details.png" for details.

Expected results:
Job should passed without any error.

Additional info:
No any DTM logs and dump files can be available for dump file collecting work stopped at the beginning and have to reboot manually to continue the left tasks.

Created attachment 567025 [details]
win7-32-blk-23-fail-WG-CHAOS.cpk

Created attachment 567026 [details]
win7-32-BSOD-CHAOS.png

Created attachment 567027 [details]
Win7-32-CHOAS-details

Have more tries for investigation:

1.I have tried doing S4 after hot unplugging manually, this BSOD will happen. and it will work well when doing S3 after hot unplugging.

2.Job "Common Scenario Stress with DiskIO" also has the same issue with the same BSOD happened after S4 when doing Pnpdtest related task.


It works well on virtio-win-prewhql-0.1-22.

Best Regards,
Dawn

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0751.html