Hi,
I hit some problems when running WHQL common scenario test for network
device on my windows pv network driver, and my windows pv network driver
is based on Xen. The WLK version i use is 1.5.7565.000, the windows
virtual guest is Srv2008 R2 x64 with 4G memory, 4cpus and 50G system disks.
After the Srv2008 R2 vm is hibernated/waked up for several times, it
BSOD with error code 0x3B, or 0x19 caused by ntkrnlmp.exe, or NTFS.sys
etc. I tried to debug this issue with windbg and found all devices on
the vm were resumed successfully, and the network cards started to
send/receive packets properly, and then the VM BSOD suddenly before this
test case start to disable/enable network cards.
However, it seems test result is connected with cpu type and cpu number.
I run this test in both AMD and Intel environment installed with Oracle
VM Server 2.2.x, and got different results. Following is the test results:
machines 1cpu 4cpu
AMD pass pass
Intel pass BSOD
Furthermore, Srv2008 R1 x64 with 4G memory, 4cpus passed this test case
successfully.
I have worked on this issue for several days, but failed to figure out
the root cause. So would you like to help me on this issue? Any help is
appreciated.
Following is the dump information:
*** Fatal System Error: 0x0000003b
(0x00000000C0000005,0xFFFFF800014D0105,0xFFFFF88004FEDE00,0x0000000000000000)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
Connected to Windows 7 7600 x64 target at (Wed Apr 21 10:53:42.890 2010
(GMT-7)), ptr64 TRUE
Loading Kernel Symbols
…
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol
loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.
…
Loading User Symbols
…
Loading unloaded module list
…
SYMSRV:
c:\windows\websymbols*http"//msdl.microsoft.com/download/symbols needs a
downstream store
Unable to enumerate user-mode unloaded modules, Win32 error 0n30
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800014d0105, fffff88004fede00, 0}
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe (
nt!ExpInterlockedPopEntrySListFault16+0 )
Followup: MachineOwner
nt!DbgBreakPointWithStatus:
fffff800`014c4f60 cc int 3
3: kd> .load
No extension DLL name provided
3: kd> .reload
Connected to Windows 7 7600 x64 target at (Wed Apr 21 12:13:02.812 2010
(GMT-7)), ptr64 TRUE
Loading Kernel Symbols
…
…
Loading User Symbols
…
Loading unloaded module list
…Unable to enumerate user-mode unloaded modules,
Win32 error 0n30
3: kd> !thread
THREAD fffffa8004d2c680 Cid 02a4.0dfc Teb: 000007fffffd6000
Win32Thread: 0000000000000000 RUNNING on processor 3
Not impersonating
DeviceMap fffff8a000d98960
Owning Process fffffa8004de95f0 Image: svchost.exe
Attached Process N/A Image: N/A
Wait Start TickCount 156102 Ticks: 0
Context Switch Count 9
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address ntdll!TppWorkerThread (0x00000000778a8f00)
Stack Init fffff88004feedb0 Current fffff88004fee7d0
Base fffff88004fef000 Limit fffff88004fe9000 Call 0
Priority 9 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2
PagePriority 5
Child-SP RetAddr : Args to
Child : Call Site
fffff88004fecdc8 fffff800015c26d2 : 00000000c0000005 fffffa8004d2c680 0000000000000065 fffff8000150b314 :
nt!DbgBreakPointWithStatus
fffff88004fecdd0 fffff800015c34be : fffff88000000003 0000000000000000 fffff80001507ee0 000000000000003b :
nt!KiBugCheckDebugBreak+0x12
fffff88004fece30 fffff800014cd004 : fffffa8000000008 fffffa80050b6b40 fffffa80050b6b40 0000000000000000 : nt!KeBugCheck2+0x71e
fffff88004fed500 fffff800014cc469 : 000000000000003b 00000000c0000005 fffff800014d0105 fffff88004fede00 :
nt!KeBugCheckEx+0x104
fffff88004fed540 fffff800014cbdbc : fffff88004fee5a8 fffff88004fede00 0000000000000000 fffff800014fb450 :
nt!KiBugCheckDispatch+0x69
fffff88004fed680 fffff800014f2bed : fffff800016d5d18 fffff8000161388c fffff8000145b000 fffff88004fee5a8 :
nt!KiSystemServiceHandler+0x7c
fffff88004fed6c0 fffff800014fa250 : fffff8000161b1e8 fffff88004fed738 fffff88004fee5a8 fffff8000145b000 :
nt!RtlpExecuteHandlerForException+0xd
fffff88004fed6f0 fffff800015071b5 : fffff88004fee5a8 fffff88004fede00 fffff88000000000 0000000000000001 :
nt!RtlDispatchException+0x410
fffff88004feddd0 fffff800014cc542 : fffff88004fee5a8 000000000000000c fffff88004fee650 fffff88001ee2900 :
nt!KiDispatchException+0x135
fffff88004fee470 fffff800014cae4a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 :
nt!KiExceptionDispatch+0xc2
fffff88004fee650 fffff800014d0105 : 000000000000000c fffff800015ff646 fffff8a001984030 0000000000000008 :
nt!KiGeneralProtectionFault+0x10a (TrapFrame @ fffff88004fee650) fffff88004fee7e0 fffff800015ff646 : fffff8a001984030
0000000000000008 fffff88004fee8e0 fffffa800337fa00 : nt!ExpInterlockedPopEntrySListFault16 fffff88004fee7f0 fffff8000179dd47 : fffff8a000000003
000000000000000c 0000000000000293 fffff8000195fdfe : nt!ExAllocatePoolWithTag+0x276 fffff88004fee8e0 fffff80001496419 : 0000000000000000
0000000000020001 fffffa8000000001 fffff88004feeaa0 : nt!SeCaptureSecurityDescriptor+0x502 fffff88004fee9c0 fffff80001496b17 : 00000000002a6530
0000000000000000 0000000000000574 fffff8a000020000 : nt!SeAccessCheckByType+0x368 fffff88004feeb40 fffff800014cc153 : 0000000000000000
0000000001dde240 0000000000000011 00000000002a6530 : nt!NtAccessCheck+0x57 fffff88004feebb0 00000000778e04fa : 000007fefdb55cbb
0000000000217ea0 0000000000217cf0 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff88004feec20)
000000000190eab8 000007fefdb55cbb : 0000000000217ea0 0000000000217cf0 0000000000000000 0000000000000000 :
ntdll!NtAccessCheck+0xa
000000000190eac0 000007fefdc818a6 : 00000000002102a8 00000000778dcef4 0000000000000000 000007fefdf1fa51 :
KERNELBASE!AccessCheck+0x3b
000000000190eb20 000007fefb1b229c : 0000000000000000 0000000000000001 0000000000000000 00d50104100000d4 :
ADVAPI32!AccessCheckStub+0x36
000000000190eb70 000007fefb1b21e1 : 0000000000000000 000000000190ec88 0000000000000574 00000000778be65a :
mpssvc!FwAPIsIsAccessGranted+0x6c
000000000190ec00 000007fefb1b2343 : 0000000000000000 0000000000000000 0000000000000001 0000000001d56b70 :
mpssvc!FwRpcAPIsIsAccessGranted+0x7d
000000000190ec40 000007fefb1b3a9c : 0000000000000000 0000000000000000 0000000000000009 0000000001d56b70 :
mpssvc!FwRpcAPIsSecModeAccessCheckForClient+0x64
000000000190ec80 000007fefb1b3a0f : 0000000000000009 000000000190eda0 000000000190f198 000007fefdf1f7a1 :
mpssvc!RPC_Hlp_FWGetConfig+0x7c
000000000190ecf0 000007fefdf2c7f5 : 0000000001d56b70 0000000001dde240 0000000000000011 0000000000000001 :
mpssvc!RPC_FWGetConfig+0x4f
000000000190ed50 000007fefdfdb62e : 0000000000000009 000000000000000a 000007fefb240450 0000000001d56cc0 : RPCRT4!Invoke+0x65
000000000190ede0 000007fefdf24070 : 0000000000000000 0000000000000000 0000000001dc6e60 0000000089090080 :
RPCRT4!Ndr64StubWorker+0x61b
000000000190f3a0 000007fefdf29c24 : 0000000000000001 00000000778b537e 0000000000000000 0000000000000000 :
RPCRT4!NdrServerCallAll+0x40
000000000190f3f0 000007fefdf29d86 : 00000000002104e8 000000000021026c 000000000190f5a0 00750000000280a8 :
RPCRT4!DispatchToStubInCNoAvrf+0x14
000000000190f420 000007fefdf2a479 : 0000000000000000 000007fefdf2445d 0000000000000073 0000000001d56b70 :
RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x146
000000000190f540 000007fefdf2a11d : 00000000002de120 0000000001d0d800 000007fefdf00000 00000000002c8240 :
RPCRT4!LRPC_SCALL::DispatchRequest+0x149
000000000190f620 000007fefdf37ddf : 0000000000030000 0000000000297580 0000000000000000 0000000000000003 :
RPCRT4!LRPC_SCALL::HandleRequest+0x20d
000000000190f750 000007fefdf37995 : 0000000000000000 0000000000000000 0000000000297680 0000000000000000 :
RPCRT4!LRPC_ADDRESS::ProcessIO+0x3bf
000000000190f890 00000000778ab43b : 0000000000000000 0000000000000000 0000000001d38788 0000000000000000 :
RPCRT4!LrpcIoComplete+0xa5
000000000190f920 00000000778a923f : 0000000000000000 0000000000000000 000000000000ffff 0000000000000000 :
ntdll!TppAlpcpExecuteCallback+0x26b
000000000190f9b0 000000007768f56d : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 :
ntdll!TppWorkerThread+0x3f8
000000000190fcb0 00000000778c3281 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 :
kernel32!BaseThreadInitThunk+0xd
000000000190fce0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 :
ntdll!RtlUserThreadStart+0x1d
Thanks
Annie.