Bug 957326

Summary: [virtio-win][scsi]Hibernate failed due to BSOD[9f] after block resize data disk on win7-64 guest
Product: Red Hat Enterprise Linux 6 Reporter: Min Deng <mdeng>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: acathrow, bcao, bsarathy, jguo, juzhang, lersek, lijin, michen, rhod, virt-bugs
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-02 02:50:42 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:
Attachments:
Description Flags
dump none

Description Min Deng 2013-04-27 07:37:25 UTC 
Description of problem:
Guest will get a bsod while hibernating after block resize data disk.

Version-Release number of selected component (if applicable):
virtio-win-prewhql-59

How reproducible:
1 times

Steps to Reproduce:
1.boot up guest with 
/usr/libexec/qemu-kvm -m 4G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet0,mac=00:1c:3f:21:46:31 -uuid cccc6a20-2351-4762-a654-b7990c16d720 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-R2-blk-scsi,server,nowait -mon chardev=111a,mode=readline -vnc :1 -rtc base=localtime,clock=host,driftfix=slew -chardev socket,id=seabios_debug,path=/tmp/monitor-seabios,server,nowait -device isa-debugcon,iobase=0x402,chardev=seabios_debug -drive file=win7-64-run.qcow2,if=none,media=disk,format=qcow2,rerror=stop,werror=stop,cache=none,aio=native,id=scsi-disk0 -drive file=disk1.qcow2,if=none,media=disk,format=qcow2,rerror=stop,werror=stop,cache=none,aio=native,id=scsi-disk1 -drive file=disk3.raw,if=none,media=disk,format=raw,rerror=stop,werror=stop,cache=none,aio=native,id=scsi-disk3 -drive file=disk4.raw,if=none,media=disk,format=raw,rerror=stop,werror=stop,cache=none,aio=native,id=scsi-disk4 -device virtio-scsi-pci,id=bus1 -device scsi-hd,bus=bus1.0,drive=scsi-disk0,id=disk,serial=test,bootindex=1 -device scsi-hd,bus=bus1.0,drive=scsi-disk1,id=disk1,serial=test1 -device scsi-hd,bus=bus1.0,drive=scsi-disk3,id=disk3,serial=test3,scsi-id=2,lun=3 -device scsi-hd,bus=bus1.0,drive=scsi-disk4,id=disk4,serial=test4,scsi-id=1,lun=4 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -M rhel6.4.0 -spice port=5931,disable-ticketing -vga qxl -qmp tcp:0:4444,server,nowait -monitor stdio -device virtio-scsi-pci,id=bus2 -device scsi-hd,bus=bus2.0,drive=scsi-disk2,id=disk2 -drive file=disk2.raw,if=none,media=disk,format=raw,rerror=stop,werror=stop,cache=none,aio=native,id=scsi-disk2,serial=test2
2.block_resize scsi-disk4 to 15G [original is about 2G]
  Login to guest and check/format the new added disk.
3.do Hibernate 
  
Actual results:
It took a long time to hibernate and the guest got BSOD finally.

Expected results:
The guest can hibernate 

Additional info:
*******************************************************************************
*                                                                             *
*                        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: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800407b060, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80039f37d0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  vioscsi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  516ea910

MODULE_NAME: vioscsi

FAULTING_MODULE: fffff88000c54000 vioscsi

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0274cb52 : 00000000`0000009f 00000000`00000003 fffffa80`0407b060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`026ec062 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`026ebf06 : fffffa80`036e5c68 fffffa80`036e5c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`026ebdee : 00000008`7a643188 fffff800`00b9cc58 00000000`00038e54 fffff800`02855d08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`026ebbd7 : 00000003`08f8abc2 00000003`00038e54 00000003`08f8abcf 00000000`00000054 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`026d836a : fffff800`02852e80 fffff800`02860cc0 00000000`00000000 fffff800`026e785c : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_vioscsi.sys

BUCKET_ID:  X64_0x9F_3_disk_IMAGE_vioscsi.sys

Followup: MachineOwner
---------
Comment 2 Min Deng 2013-04-27 07:43:55 UTC 
Created attachment 740734 [details]
dump
Comment 5 Mike Cao 2013-07-31 09:43:11 UTC 
jguo, Pls retest this bug on RHEL6.5 hosts with seabios-28
Comment 6 lijin 2013-08-02 05:09:56 UTC 
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:
 Could hibernate and resume successfully without BSOD happened.

Based on the above this issue has been fixed already.
Comment 7 Vadim Rozenfeld 2013-08-31 10:03:01 UTC 
can we close it, based on comment #6?
Comment 8 Mike Cao 2013-09-02 02:50:42 UTC 

*** This bug has been marked as a duplicate of bug 876250 ***
Comment 9 Laszlo Ersek 2013-09-02 07:40:15 UTC 
fixing up the dupe bug

*** This bug has been marked as a duplicate of bug 846912 ***