[Xen-devel] Re: Why do I get a blue screen when do chkdsk operation on GPL Windows PV Driver DomU?

[Huibin QIAN <qianhb@xxxxxxxxxx>]

Yes, In fact, This blue screen also appear in WLK Job " Disk Stress".

 

But I think it's the same as this one

----- Original Message -----

From: James Harper

To: Huibin QIAN ; xen-devel@xxxxxxxxxxxxxxxxxxx

Sent: Tuesday, December 29, 2009 5:18 PM

Subject: RE: Why do I get a blue screen when do chkdsk operation on GPL Windows PV Driver DomU?

Thanks for that - I can reproduce this easily by running a couple of
chkdsk's as you say. I must be leaking gref's somewhere -
/var/log/xen/qemu-dm-<domuname>.log contains lots of "XenPCI No free
grant refs".

From memory, chkdsk doesn't align its buffers the way blkback wants them
aligned so I have to double buffer them... that code path isn't used
particularly often so hopefully the problem lies there!

James

> -----Original Message-----
> From: Huibin QIAN [mailto:qianhb@xxxxxxxxxx]
> Sent: Tuesday, 29 December 2009 17:00
> To: James Harper; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: Why do I get a blue screen when do chkdsk operation on
GPL
> Windows PV Driver DomU?
>
> I download the newest version of code ,compile by myself, run it on
Windows XP
> SP2 x86.
>
> When I do chkdsk only once, It will NOT crash.
> But I do chkdsk twice it DO happend!
>
> Following is details:
>
>
------------------------------------------------------------------------
------
> ---------------------
> 1: kd> !analyze -v
>
************************************************************************
******
> *
> *
> *
> *                        Bugcheck Analysis
> *
> *
> *
>
************************************************************************
******
> *
>
> CRITICAL_OBJECT_TERMINATION (f4)
> A process or thread crucial to system operation has unexpectedly
exited or
> been
> terminated.
> Several processes and threads are necessary for the operation of the
> system; when they are terminated (for any reason), the system can no
> longer function.
> Arguments:
> Arg1: 00000003, Process
> Arg2: 820e2020, Terminating object
> Arg3: 820e2194, Process image file name
> Arg4: 805d215e, Explanatory message (ascii)
>
> Debugging Details:
> ------------------
>
> PEB is paged out (Peb.Ldr = 7ffd300c).  Type ".hh dbgerr001" for
details
> PEB is paged out (Peb.Ldr = 7ffd300c).  Type ".hh dbgerr001" for
details
>
> PROCESS_OBJECT: 820e2020
>
> IMAGE_NAME:  hardware_disk
>
> DEBUG_FLR_IMAGE_TIMESTAMP:  0
>
> FAULTING_MODULE: 00000000
>
> PROCESS_NAME:  csrss.exe
>
> EXCEPTION_RECORD:  f88e99d8 -- (.exr 0xfffffffff88e99d8)
> ExceptionAddress: 7c956bd1
>    ExceptionCode: c0000006 (In-page I/O error)
>   ExceptionFlags: 00000000
> NumberParameters: 3
>    Parameter[0]: 00000000
>    Parameter[1]: 7c9a9c20
>    Parameter[2]: c000009a
> Inpage operation failed at 7c9a9c20, due to I/O error c000009a
>
> EXCEPTION_CODE: (NTSTATUS) 0xc000009a - <Unable to get error code
text>
>
> DEFAULT_BUCKET_ID:  DRIVER_FAULT
>
> ERROR_CODE: (NTSTATUS) 0xc0000006 - "0x%08lx"
>
> IO_ERROR: (NTSTATUS) 0xc000009a - <Unable to get error code text>
>
> EXCEPTION_STR:  0xc0000006_c000009a
>
> FAULTING_IP:
> +7c956bd1
> 7c956bd1 ??              ???
>
> BUGCHECK_STR:  0xF4_IOERR_C000009A
>
> STACK_TEXT:
> f88e9520 805d1305 000000f4 00000003 820e2020 nt!KeBugCheckEx+0x1b
> f88e9544 805d2209 805d215e 820e2020 820e2194
nt!PspCatchCriticalBreak+0x75
> f88e9574 8054161c 820e2268 c0000006 f88e99b0
nt!NtTerminateProcess+0x7d
> f88e9574 805014d9 820e2268 c0000006 f88e99b0 nt!KiFastCallEntry+0xfc
> f88e95f4 804ff50a ffffffff c0000006 f88e99f8
nt!ZwTerminateProcess+0x11
> f88e99b0 80502c17 f88e99d8 00000000 f88e9d64
nt!KiDispatchException+0x3a0
> f88e9d34 80544ee7 005af22c 005af24c 00000000 nt!KiRaiseException+0x175
> f88e9d50 8054161c 005af22c 005af24c 00000000 nt!NtRaiseException+0x33
> f88e9d50 7c956bd1 005af22c 005af24c 00000000 nt!KiFastCallEntry+0xfc
> WARNING: Frame IP not in any known module. Following frames may be
wrong.
> 005af528 00000000 00000000 00000000 00000000 0x7c956bd1
>
>
> STACK_COMMAND:  kb
>
> FOLLOWUP_IP:
> +7c9a9c20
> 7c9a9c20 ??              ???
>
> FOLLOWUP_NAME:  MachineOwner
>
> MODULE_NAME: hardware_disk
>
> FAILURE_BUCKET_ID:  0xF4_IOERR_C000009A_IMAGE_hardware_disk
>
> BUCKET_ID:  0xF4_IOERR_C000009A_IMAGE_hardware_disk
>
> Followup: MachineOwner
> ---------
>
>
>
> ----- Original Message -----
> From: James Harper <mailto:james.harper@xxxxxxxxxxxxxxxx>
> To: Huibin QIAN <mailto:qianhb@xxxxxxxxxx>  ; xen-
> devel@xxxxxxxxxxxxxxxxxxx
> Sent: Tuesday, December 29, 2009 12:37 PM
> Subject: RE: Why do I get a blue screen when do chkdsk operation
on GPL
> Windows PV Driver DomU?
>
> >
> > Hey All,
> >
> > I get a blue screen when I do chkdsk operation on GPL Windows
PV
> Driver DomU.
> > The Error code is 0x0000000F4, Which mens "A process or thread
crucial
> to
> > system operation has unexpectedly exited or been terminated.".
> > From windbg, I seems that csrss.exe process exited.
>
> That shouldn't happen!
>
> Can you tell me what version of GPLPV, and what operating system
(eg
> Windows 2003 x32)
>
> Thanks
>
> James
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel