From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: James Harper <james.harper@bendigoit.com.au>
Subject: Re: State of GPLPV and Windows 8
Date: Tue, 12 Feb 2013 16:01:11 +0100 [thread overview]
Message-ID: <511A5937.3020101@hfp.de> (raw)
In-Reply-To: <511A45D0.4030806@hfp.de>
Maybe the WinDbg log may be helpful. Sees to have some connection to
hibernation?
1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff803c5e81400, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
READ_ADDRESS: ffffffffffffffff
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx
referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!memcpy+240
fffff803`c5e81400 f30f6f440af0 movdqu xmm0,xmmword ptr [rdx+rcx-10h]
EXCEPTION_PARAMETER2: ffffffffffffffff
BUGCHECK_STR: 0x1E_c0000005_R
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
TAG_NOT_DEFINED_c000000f: FFFFF88003622FB0
EXCEPTION_RECORD: fffffa8003398e10 -- (.exr 0xfffffa8003398e10)
ExceptionAddress: fffffa8003398e18
ExceptionCode: 000e0002
ExceptionFlags: 00000001
NumberParameters: 93528968
Parameter[0]: fffffa8005932388
Parameter[1]: 0000000000000000
Parameter[2]: 0000000000000100
Parameter[3]: 0000000200000001
Parameter[4]: 0000000000000001
Parameter[5]: fffffa8003398e70
Parameter[6]: 0000000fa1662b9d
Parameter[7]: 0000000fa1662b9d
Parameter[8]: fffffa8003398f00
Parameter[9]: fffffa8003398f80
Parameter[10]: 0000000000000000
Parameter[11]: 0000000000000000
Parameter[12]: 0000000000000000
Parameter[13]: 0000000000000000
Parameter[14]: 0000000000000000
LAST_CONTROL_TRANSFER: from fffff803c5f7ddf2 to fffff803c5e86340
STACK_TEXT:
fffff880`0361a308 fffff803`c5f7ddf2 : 00000000`0000001e
ffffffff`c0000005 fffff803`c5e81400 00000000`00000000 : nt!KeBugCheckEx
fffff880`0361a310 fffff803`c5ee68ad : fffff803`c658ac0e
00000000`00000000 fffff880`0361a480 00000000`00000000 :
nt!KiFatalExceptionHandler+0x22
fffff880`0361a350 fffff803`c5ee8633 : 00000000`00000000
fffff880`03616000 00000000`00003990 fffff880`0361c000 :
nt!RtlpExecuteHandlerForException+0xd
fffff880`0361a380 fffff803`c5f04abe : fffff880`0361b288
fffff880`0361afc0 fffff880`0361b288 00000000`00000000 :
nt!RtlDispatchException+0x44b
fffff880`0361aa90 fffff803`c5e85742 : fffffa80`03398e10
fffffa80`04bd2101 fffffa80`04bd2190 00000000`00000103 :
nt!KiDispatchException+0x455
fffff880`0361b150 fffff803`c5e83c4a : fffffa80`00000006
56530701`00000000 00000000`00000003 00000000`00000000 :
nt!KiExceptionDispatch+0xc2
fffff880`0361b330 fffff803`c5e81400 : fffff803`c6170a31
00000000`00000003 00000000`00010000 fffff880`000001b9 :
nt!KiGeneralProtectionFault+0x10a
fffff880`0361b4c8 fffff803`c6170a31 : 00000000`00000003
00000000`00010000 fffff880`000001b9 fffff803`c617084f : nt!memcpy+0x240
fffff880`0361b4d0 fffff803`c61709a7 : fffffa80`05e00080
fffff880`009c3101 fffffa80`047665a0 fffff880`0361b590 :
nt!PopAddPagesToCompressedPageSet+0x5d
fffff880`0361b540 fffff803`c6173b8b : fffff880`0361b779
fffff803`c5ebd2d6 fffffa80`05430680 fffffa80`047665a0 :
nt!PopCompressHiberBlocks+0x87
fffff880`0361b6f0 fffff803`c658ac0e : fffffa80`03477340
00000000`00000bb2 fffff880`009c3180 00000000`00000000 :
nt!PopSaveHiberContext+0x7c
fffff880`0361b980 fffff803`c616b0a4 : fffffa80`04276510
00000000`00000000 00000000`00000000 00000003`00000000 :
hal!HaliAcpiSleep+0x54f
fffff880`0361ba10 fffff803`c616b26b : fffff803`c6093410
fffff880`0361bbf0 fffff880`06a61b90 00000000`00f7fc98 :
nt!PopHandleNextState+0x125
fffff880`0361ba60 fffff803`c5e7b6a8 : fffff880`009c5f00
fffff880`009c3180 fffffa80`0410b118 fffff880`0361bca0 :
nt!PopInvokeStateHandlerTargetProcessor+0x3c
fffff880`0361baf0 fffff803`c5ead1b0 : fffffa80`055f6980
00000000`ffffffff fffffa80`055f6c58 00000000`00000000 :
nt!KiExecuteAllDpcs+0x198
fffff880`0361bc30 fffff803`c5eb167a : fffff880`009c3180
fffff880`009c3180 00000000`00000000 fffff880`009cedc0 :
nt!KiRetireDpcList+0xd0
fffff880`0361bda0 00000000`00000000 : fffff880`0361c000
fffff880`03616000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiFatalExceptionHandler+22
fffff803`c5f7ddf2 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiFatalExceptionHandler+22
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 50ab0e64
BUCKET_ID_FUNC_OFFSET: 22
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!KiFatalExceptionHandler
BUCKET_ID: 0x1E_c0000005_R_nt!KiFatalExceptionHandler
Followup: MachineOwner
---------
next prev parent reply other threads:[~2013-02-12 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 13:38 State of GPLPV and Windows 8 Andreas Kinzler
2013-02-12 15:01 ` Andreas Kinzler [this message]
2013-02-12 19:15 ` Marc Dahlhaus
2013-02-12 22:19 ` James Harper
2013-02-13 14:08 ` Andreas Kinzler
2013-02-12 22:19 ` James Harper
2013-02-13 8:24 ` Paul Durrant
2013-02-19 12:09 ` James Harper
2013-02-20 9:57 ` Paul Durrant
2013-02-20 10:25 ` James Harper
2013-02-20 11:15 ` Paul Durrant
2013-02-13 14:54 ` Andreas Kinzler
2013-02-13 22:52 ` James Harper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=511A5937.3020101@hfp.de \
--to=ml-xen-devel@hfp.de \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.