[Spice-devel] A sever bug found in 64-bit WIndows 7 VM
Charles.Tsai-蔡清海-研究發展部
charles.tsai at cloudena.com
Tue May 29 02:44:41 PDT 2012
Vadim,
It is very easy to reproduce the bug.
Memory dump and PDB file must go in pair.
Let me know if you need my memory dump file and PDB file.
-----Original Message-----
From: Vadim Rozenfeld [mailto:vrozenfe at redhat.com]
Sent: Tuesday, May 29, 2012 5:23 PM
To: Alon Levy
Cc: Charles.Tsai-蔡清海-研究發展部; spice-devel at lists.freedesktop.org; Jonah.Wu-吳君勉-研究發展部
Subject: Re: A sever bug found in 64-bit WIndows 7 VM
On Tuesday, May 29, 2012 10:42:08 AM Alon Levy wrote:
> On Tue, May 29, 2012 at 02:58:19AM +0000, Charles.Tsai-蔡清海-研究發展部 wrote:
>
> Hi Vadim,
>
> Could you have a look?
>
> Thanks,
> Alon
Sure.
Is the crashdump available somewhere?
Cheers,
Vadim.
>
> > Bug description:
> > A sever bug was found on 64-bit Windows 7 VM which crashed after
> > running idle for a while(~ 2-3 hours). When we checked the kvm
> > process, it was killed from the system.
> >
> > Drivers installed:
> > Qxl,
> > Virtioserail
> > Vdagent
> >
> > Qemu & Spice:
> > Hans’s Qemu + "spice-0.10.tar.gz"
> >
> > Steps to reproduce:
> >
> > 1. Create a 64-bit Windows 7 VM image
> >
> > 2. Install qxl, virioserai driver and vdagent
> >
> > 3. Launch the VM and let it run idle
> >
> > 4. After a couple of hours, the VM will crash
> >
> >
> > Memory demp information:
> >
> >
> >
> > 0: kd> !analyze -v
> >
> > ********************************************************************
> > *****
> > ******
> >
> > *
> > *
> >
> > * Bugcheck Analysis
> > *
> >
> > *
> > *
> >
> > ********************************************************************
> > *****
> > ******
> >
> >
> >
> > DRIVER_POWER_STATE_FAILURE (9f)
> >
> > A driver is causing an inconsistent power state.
> >
> > Arguments:
> >
> > Arg1: 0000000000000003, A device object has been blocking an Irp for
> > too long a time
> >
> > Arg2: fffffa8003bb24b0, Physical Device Object of the stack
> >
> > Arg3: fffff80003bd3518, Functional Device Object of the stack
> >
> > Arg4: fffffa80025e9510, The blocked IRP
> >
> >
> >
> > Debugging Details:
> >
> > ------------------
> >
> >
> >
> >
> >
> > DRVPOWERSTATE_SUBCODE: 3
> >
> >
> >
> > IRP_ADDRESS: fffffa80025e9510
> >
> >
> >
> > DEVICE_OBJECT: fffffa8003bb24b0
> >
> >
> >
> > DRIVER_OBJECT: fffffa8003a1ac70
> >
> >
> >
> > IMAGE_NAME: vioser.sys
> >
> >
> >
> > DEBUG_FLR_IMAGE_TIMESTAMP: 4fc31b19
> >
> >
> >
> > MODULE_NAME: vioser
> >
> >
> >
> > FAULTING_MODULE: fffff88003670000 vioser
> >
> >
> >
> > DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
> >
> >
> >
> > BUGCHECK_STR: 0x9F
> >
> >
> >
> > PROCESS_NAME: System
> >
> >
> >
> > CURRENT_IRQL: 2
> >
> >
> >
> > LAST_CONTROL_TRANSFER: from fffff80002930e53 to fffff800028c3040
> >
> >
> >
> > STACK_TEXT:
> >
> > fffff800`03bd34c8 fffff800`02930e53 : 00000000`0000009f
> > 00000000`00000003
> > fffffa80`03bb24b0 fffff800`03bd3518 : nt!KeBugCheckEx
> >
> > fffff800`03bd34d0 fffff800`028cf0e6 : fffff800`03bd3600
> > fffff800`03bd3600
> > 00000000`00000001 00000000`00000000 : nt! ??
> > ::FNODOBFM::`string'+0x28e30
> >
> > fffff800`03bd3570 fffff800`028ce396 : fffff800`02a72700
> > 00000000`00034df1
> > 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
> >
> > fffff800`03bd35e0 fffff800`028cf00e : 00000007`ddaba240
> > fffff800`03bd3c58
> > 00000000`00034df1 fffff800`02a410a8 :
> > nt!KiProcessExpiredTimerList+0xc6
> >
> > fffff800`03bd3c30 fffff800`028ce707 : 00000059`a9892fc1
> > 00000059`00034df1 00000059`a9892fbb 00000000`000000f1 :
> > nt!KiTimerExpiration+0x1be
> >
> > fffff800`03bd3cd0 fffff800`028cb77a : fffff800`02a3ce80
> > fffff800`02a4ac40
> > 00000000`00000000 fffff880`00c3ef44 : nt!KiRetireDpcList+0x277
> >
> > fffff800`03bd3d80 00000000`00000000 : fffff800`03bd4000
> > fffff800`03bce000
> > fffff800`03bd3d40 00000000`00000000 : nt!KiIdleLoop+0x5a
> >
> >
> >
> >
> >
> > STACK_COMMAND: kb
> >
> >
> >
> > FOLLOWUP_NAME: MachineOwner
> >
> >
> >
> > FAILURE_BUCKET_ID: X64_0x9F_IMAGE_vioser.sys
> >
> >
> >
> > BUCKET_ID: X64_0x9F_IMAGE_vioser.sys
> >
> >
> >
> > Followup: MachineOwner
> >
> > ---------
> >
> >
> >
> > 0: kd> lmvm vioser
> >
> > start end module name
> >
> > fffff880`03670000 fffff880`03680000 vioser (private pdb symbols)
> > d:\localsymbols\vioser.pdb
> >
> > Loaded symbol image file: vioser.sys
> >
> > Image path: \SystemRoot\system32\DRIVERS\vioser.sys
> >
> > Image name: vioser.sys
> >
> > Timestamp: Mon May 28 14:28:41 2012 (4FC31B19)
> >
> > CheckSum: 0000F577
> >
> > ImageSize: 00010000
> >
> > Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
> >
> > 0: kd> !devobj fffffa8003bb24b0 f
> >
> > Device object (fffffa8003bb24b0) is for:
> >
> > vport0p1 \Driver\VirtioSerial DriverObject fffffa8003a1ac70
> >
> > Current Irp 00000000 RefCount 1 Type 0000001b Flags 0000304c
> >
> > Dacl fffff9a100232a11 DevExt fffffa8003badbc0 DevObjExt
> > fffffa8003bb2620 DevNode fffffa8003bbfb30
> >
> > ExtensionFlags (0000000000)
> >
> > Device queue is not busy.
> >
> >
> >
> > 0: kd> !irp fffffa80025e9510
> >
> > Irp is active with 2 stacks 1 is current (= 0xfffffa80025e95e0)
> >
> > No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
> >
> > cmd flg cl Device File Completion-Context
> > >
> > >[ 16, 2] 0 e1 fffffa8003bb24b0 00000000
> > >fffff800028ad990-fffffa8002b61ce0 Success Error Cancel pending
> > >
> > \Driver\VirtioSerial nt!IopUnloadSafeCompletion
> >
> > Args: 00014400 00000001 00000004
> > 00000002
> >
> > [ 0, 0] 0 0 00000000 00000000 00000000-fffffa80027e32e0
> >
> > Args: 00000000 00000000 00000000
> > 00000000
More information about the Spice-devel
mailing list