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.
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.
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
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.