Bug 719801 - [WHQL][Network] Guest got BSOD while running job named CHAOS-Concurrent Hardware and OS test job
Summary: [WHQL][Network] Guest got BSOD while running job named CHAOS-Concurrent Hardw...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.2
Hardware: Unspecified
OS: Windows
low
low
Target Milestone: rc
: ---
Assignee: Arkady Frenkel
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-08 03:15 UTC by Min Deng
Modified: 2011-09-07 13:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-07 13:26:26 UTC
Target Upstream Version:


Attachments (Terms of Use)
It is convenient for developer to catch the reason for BSOD (4.86 KB, application/octet-stream)
2011-07-08 03:17 UTC, Min Deng
no flags Details
change the correct file type (4.86 KB, text/plain)
2011-07-08 03:20 UTC, Min Deng
no flags Details

Description Min Deng 2011-07-08 03:15:04 UTC
Description of problem:
During whql testing,window 7 64bits hit blue screen issue with error code -
1E, {ffffffffc0000005, fffff80002915b09, 0, 900000051} while DTM executed 
CHAOS-Concurrent Hardware and OS test
Version-Release number of selected component (if applicable):


How reproducible:
Tester can reproduce the issue on window7 64 bits sometimes while running CHAOS-Concurrent Hardware and OS test job

Host&kvm version:
2.6.32-164.el6.x86_64
qemu-kvm-0.12.1.2-2.167.el6.x86_64


Steps to Reproduce:
1.Configure the WHQL testing ENV
2.Execute the CHAOs-Concurrent Hardware and OS test from DTM

  Expected results,The job can pass.
  Actual   results,The job lead to guest's BSOD

Additional info:
Tester can provide the related DMP file if necessary and any issues please let me know,thank you.

Comment 1 Min Deng 2011-07-08 03:17:01 UTC
Created attachment 511831 [details]
It is convenient for developer to catch the reason for BSOD

Comment 2 Min Deng 2011-07-08 03:20:40 UTC
Created attachment 511834 [details]
change the correct file type

Comment 4 Min Deng 2011-07-08 03:24:22 UTC
virtio-win verison:
virtio-win-1.2.0-1.el6

Comment 5 Yvugenfi@redhat.com 2011-07-09 11:04:36 UTC
Please attach dump or mini-dump file from the crash. Thanks!

Comment 7 Arkady Frenkel 2011-08-09 09:32:49 UTC
Please attach cpk file, so we can provide cpk and dmp file to Microsoft
TIA
Arkady

Comment 8 Min Deng 2011-08-25 07:50:22 UTC
The

Comment 9 Arkady Frenkel 2011-08-25 12:54:47 UTC
?

Comment 10 Min Deng 2011-08-26 02:02:18 UTC
Hi Arkady,

   The issue isn't reproduced via virtio-win-prewhql-0.1-15 so far.
Thanks
Min

Comment 11 Arkady Frenkel 2011-08-28 09:29:54 UTC
Great, Min!
As I saw the crash happened because of corrupted memory of device extension of stress driver itself. If you can't reproduce the problem, you can close this bug.
If that will happen again, please try that on the all 64 bit system (ws2003, win7, ws2008x because 32 bit systems have absolutely different set of API in this case : the crash happened during hibernating of the VM. And in new bz you'll describe each 64 bit system behaviour during this test.

TIA
Arkady

Comment 12 Ronen Hod 2011-09-07 13:26:26 UTC
Min,

Since it is not reproducible, we cannot do much. I am closing it. Please reopen it if it shows up again.

Thanks, Ronen.


Note You need to log in before you can comment on or make changes to this bug.