Bug 770797 - BSOD 0x101 found when running SVVP stress job
Summary: BSOD 0x101 found when running SVVP stress job
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xenpv-win
Version: 5.8
Hardware: x86_64
OS: Windows
medium
medium
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 807971
TreeView+ depends on / blocked
 
Reported: 2011-12-29 07:14 UTC by Qin Guan
Modified: 2012-04-12 15:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-11 13:16:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Qin Guan 2011-12-29 07:14:30 UTC
Description of problem:
BSOD with stopcode 0x101 always happen when running the SVVP stress related jobs, such as:
"Disk Stress [System LOGO]" or
"System - Common Scenario Stress With IO"

Version-Release number of selected component (if applicable):
kernel-xen-2.6.18-300.el5
xen-3.0.3-135.el5
xenpv-win-1.3.12-3.el5

How reproducible:
Always

Steps to Reproduce:
1. Steps RHEL5.8 xen SUTs (1 max and 4 multiples) for SVVP environment
2. Submit "Disk Stress [System LOGO]" on all of the SUTs
3. BSOD found on all the SUTs (1 max and 4 multiples) when the job "Disk Stress" running

Note that it's not a block problem, as the jobs can still finish without error after the SUTs destroyed and re-created .
 
Actual results:
BSOD with stop code 0x101

Expected results:
No BSOD on SUT

Additional info:
Refer to the attachment and the dump core file.

Comment 2 RHEL Program Management 2012-04-02 10:37:24 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 3 Paolo Bonzini 2012-04-11 13:16:02 UTC
This happens when the system is (even lightly) overcommitted.  There is nothing that can be done (backporting Viridian extensions to RHEL-5 is not a possibility).


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