Hi Leonid, I have to ask for your patience, as I'm not at all a windows developer and have no familiarity with WinDbg, so I may not be doing this correctly.
When I attach to the kernel in WinDbg, this is output: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Connected to Windows 7 7601 x64 target at (Fri Nov 22 08:08:41.274 2013 (UTC - 5:00)), ptr64 TRUE Symbol search path is: SRV*c:\WINDOWS\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: Server, suite: TerminalServer SingleUserTS Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 Machine Name: Kernel base = 0xfffff800`01804000 PsLoadedModuleList = 0xfffff800`01a47670 Debug session time: Fri Nov 22 08:08:41.960 2013 (UTC - 5:00) System Uptime: 0 days 0:10:02.022 Here is a part of ntbtlog: ... Loaded driver \SystemRoot\System32\drivers\tcpipreg.sys Loaded driver \SystemRoot\System32\DRIVERS\srv2.sys Loaded driver \SystemRoot\system32\DRIVERS\ibiou.sys Loaded driver \SystemRoot\system32\DRIVERS\ibsrp.sys ... From: Leonid Keller [mailto:[email protected]] Sent: Friday, November 22, 2013 3:52 AM To: John Carbone; [email protected] Subject: RE: SRP debugging level Don't you see the debug output in windbg ? From: John Carbone [mailto:[email protected]] Sent: Friday, November 22, 2013 12:14 AM To: Leonid Keller; [email protected] Subject: RE: SRP debugging level Hi all, I downloaded and installed WinDbg, set the debug level to 4, set "bcdedit /debug on" and rebooted but I do not know where to locate the debug output. I cannot determine if the targets are being enumerated and just not being reported to windows. However, I tried setting one of the LUNs on the SAN filer to 1, and Windows maps the drive correctly every time now. So, I suspect that because the diskpart is reporting that all the targets are zero Window is indeed getting confused as to which drive is which as I had suspected. Leonid, is this something you could please help with? From: Leonid Keller [mailto:[email protected]] Sent: Wednesday, November 20, 2013 10:55 AM To: John Carbone; [email protected] Subject: RE: SRP debugging level Did you try to install checked drivers and look into debug prints ? (DbgView or Windbg) Re to debug level: Many years ago you could have done it by setting DebugLevel/DebugFlags DWORD-32bit parameters in Registry (under Services\srp\parameters). By default, DebugLevel was then 2 and DebugFlags 0xffff. You can try to set DebugLevel to 3 or 4 and see what happen. (All this is relevant only for checked drivers). From: John Carbone [mailto:[email protected]] Sent: Wednesday, November 20, 2013 5:08 PM To: [email protected] Cc: Leonid Keller Subject: SRP debugging level Hi all, I'm trying to determine why SRP is not assigning target numbers with WinOF. Is there a way to change the debug level without compiling? Where can the output of SRP_PRINT be found? Any help would be greatly appreciated. Thank you. Kind regards, John. John Carbone | Quantum Logic Corporation 1225 Franklin Avenue, Suite 325 | Garden City, NY 11530 p: 800.482.2105 | f: 516.873.8881 [email protected] _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
