Hi all,
I compiled the openfabrics driver nvme vers 1.3 for Win server 2003 bit 32 (checked build) and added
NEW storport.sys from win server 2003 to target XP SP3.
Then I connect a Toshiba RD400 nvme disk. Gives yellow questionmark in device manager.
With host XP SP3 connected via Null Modem cable and Windbg now I get the following:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\com1
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Sun Jun 24 13:56:38.484 2018 (UTC + 2:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 UP Free x86 compatible
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
System Uptime: not available
STORMINI: StorPortInitialize returns Status(0x0)
STORMINI: Access Range, VirtualAddr=0xB9D28000.
STORMINI: NVMeFindAdapter: Stride Size set to 0x4
STORMINI: NVMeEnumNumaCores: # of NUMA node(s) = 1.
STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x0 BTL 0 0 0
ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 5
Break instruction exception - code 80000003 (first chance)
*******************************************************************************
* *
* You are seeing this message because you pressed either *
* CTRL+C (if you run kd.exe) or, *
* CTRL+BREAK (if you run WinDBG), *
* on your debugger machine's keyboard. *
* *
* THIS IS NOT A BUG OR A SYSTEM CRASH *
* *
* If you did not intend to break into the debugger, press the "g" key, then *
* press the "Enter" key now. This message might immediately reappear. If it *
* does, press "g" and "Enter" again. *
* *
*******************************************************************************
nt!RtlpBreakWithStatusInstruction:
80527bdc cc int 3
kd> !analyze -v
Connected to Windows XP 2600 x86 compatible target at (Sun Jun 24 14:01:40.906 2018 (UTC + 2:00)), ptr64 FALSE
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
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
PROCESS_NAME: Idle
FAULTING_IP:
nt!RtlpBreakWithStatusInstruction+0
80527bdc cc int 3
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 80527bdc (nt!RtlpBreakWithStatusInstruction)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 8054ad4c
Parameter[2]: 000003f8
ERROR_CODE: (NTSTATUS) 0x80000003 - {AUSNAHME} Haltepunkt Im Quellprogramm wurde ein Haltepunkt erreicht.
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Mindestens ein Argument ist ung ltig.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 8054ad4c
EXCEPTION_PARAMETER3: 000003f8
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x0
STACK_TEXT:
80549bcc 8054109d 00000001 ff676902 00000030 nt!RtlpBreakWithStatusInstruction
80549bcc 806d772a 00000001 ff676902 00000030 nt!KeUpdateSystemTime+0x165
80549c50 80541af0 00000000 0000000e 00000000 hal!HalProcessorIdle+0x2
80549c54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!RtlpBreakWithStatusInstruction+0
80527bdc cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!RtlpBreakWithStatusInstruction+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlpa.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
BUCKET_ID: MANUAL_BREAKIN
Followup: MachineOwner
---------
From this I can only see, that ntkrnlpa.exe does not like to work with this nvme.sys.
But why? No error during compile.
I am happy, if someone here has an idea,
have a nice day
Dietmar
PS: With naked Win7 (very first version) this driver nvme.sys works fantastic.
PS:
kd> .trap 0xB9D28000
ErrCode = ffffffff
eax=ffffffff ebx=ffffffff ecx=ffffffff edx=ffffffff esi=ffffffff edi=ffffffff
eip=ffffffff esp=ffffffff ebp=ffffffff iopl=3 vip vif ov dn ei ng zr ac pe cy
cs=ffff ss=ffff ds=ffff es=ffff fs=ffff gs=ffff efl=ffffffff
ffff:ffff ?? ???
STORMINI: Access Range, VirtualAddr=0xB9D28000.
Can this be, because the nvme Toshiba RD400 is not seen in Bios?