Hide Forgot
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