Bug 885952
| Summary: | [whql][scsi][wlk][9F]BSOD occurs when running Sleep Stress With IO job | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Cao <bcao> | ||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.4 | CC: | acathrow, bcao, bsarathy, ddumas, jguo, juzhang, lijin, michen, pbonzini, rhod, virt-bugs | ||||
| Target Milestone: | rc | Keywords: | Reopened, TestBlocker | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Windows | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-08-04 08:44:50 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 896495 | ||||||
| Attachments: |
|
||||||
|
Description
Mike Cao
2012-12-11 06:44:32 UTC
0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time (usually 10 minutes). Arguments: Arg1: 00000003, A device object has been blocking an Irp for too long a time Arg2: 871f72e8, Physical Device Object of the stack Arg3: 82765ae0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: 8c2a2f00, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: vioscsi.sys DEBUG_FLR_IMAGE_TIMESTAMP: 50b73b32 MODULE_NAME: vioscsi FAULTING_MODULE: 849f4000 vioscsi DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: 82765a94 82704637 0000009f 00000003 871f72e8 nt!KeBugCheckEx+0x1e 82765b00 827046b0 82765ba0 00000000 82772380 nt!PopCheckIrpWatchdog+0x1f5 82765b38 826b6799 827806e0 00000000 d182bbda nt!PopCheckForIdleness+0x73 82765b7c 826b673d 82768d20 82765ca8 00000001 nt!KiProcessTimerDpcTable+0x50 82765c68 826b65fa 82768d20 82765ca8 00000000 nt!KiProcessExpiredTimerList+0x101 82765cdc 826b478e 000101bf 845bfb50 82772380 nt!KiTimerExpiration+0x25c 82765d20 826b45b8 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb 82765d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0x9F_VRF_3_disk_IMAGE_vioscsi.sys BUCKET_ID: 0x9F_VRF_3_disk_IMAGE_vioscsi.sys Followup: MachineOwner --------- We suggest the same as https://bugzilla.redhat.com/show_bug.cgi?id=876033#c5 (In reply to comment #3) > We suggest the same as https://bugzilla.redhat.com/show_bug.cgi?id=876033#c5 should be virtio-scsi bug introduced recently . win7 32/64bit win2k8 32/64/R2 guest all affected ,We never pass it in this round Need to mention that Common Scenario Stress with IO job also failed w/ BSOD Mike Can you try it 3/4 times more? If it fails under Windows only (not Linux), could it be a bug in the generic virtio implementation? (In reply to comment #5) > There is a brief summary for most (if not all) 9F BSOD and system stalls > happening during viostor and vioscsi drivers WHQL testing on Win7/W2K8R2 > systems: > fsFsdWrite and second is trying to perform NtfsCopyWrite operation. > > I believe that if we want to narrow down the problem, we should try > reproducing this problem on different setups, like diffent cache options - > none vs. writeback, different disk image formats - raw vs. qcow2, and in > case of > virtio-scsi, try testing on a real drive vs. qemu. Vadim ,I tried cache=writeback the job stuck at Start B(2).5 .Referring to the screendump .Any idea about why it happen ? Created attachment 666497 [details]
screendump
(In reply to comment #14) > (In reply to comment #13) > > (In reply to comment #12) > > > Hi Mike, > > > Could you try reproducing the problem on qcow2 volume, just to get the full > > > picture? > > > > > > Thank you, > > > Vadim. > > > > Vadim ,With cache=none or cache=writeback ? > > If it 's possible - with both. If not, then only writeback. > Thank you, > Vadim. Hi, Vadim Tried qcow2 image both with cache=none & cache=writethougth BSOD during job running (In reply to comment #15) > (In reply to comment #14) > > (In reply to comment #13) > > > (In reply to comment #12) > > > > Hi Mike, > > > > Could you try reproducing the problem on qcow2 volume, just to get the full > > > > picture? > > > > > > > > Thank you, > > > > Vadim. > > > > > > Vadim ,With cache=none or cache=writeback ? > > > > If it 's possible - with both. If not, then only writeback. > > Thank you, > > Vadim. > > Hi, Vadim > > Tried qcow2 image both with cache=none & cache=writethougth > BSOD during job running Thank you, Vadim. QE, Please re-test with the latest SeaBIOS. Anyhow postponed to 6.6 QE tested this issue on rhel6.5 host with seabios-28
Package version:
* kernel-2.6.32-393.el6.x86_64
* qemu-img-rhev-0.12.1.2-2.377.el6.x86_64
* virtio-win-prewhql-0.1-65
* seabios-0.6.1.2-28.el6.x86_64
* vgabios-0.6b-3.7.el6.noarch
* sgabios-0-0.3.20110621svn.el6
Steps as comment #0
Actual result:
Sleep Stress With IO job could pass without any error.
Based on the above, this issue has been fixed already.
|