Hi windrvlearder,
Have you been able to get answers to your questions?
@All,
I have written a virtual storport miniport driver. Which serves the boot
disk hosted on network. We are using it to boot windows 2003. So far it does
not support SRB_FUNCTION_DUMP_POINTERS.
But when we tried to boot Vista with the same driver, during boot process we
got a bugcheck most probably after disk checking was finished. The bugehcek
was 0x19 {22,0,0,0} and the culprit shown in the bugcheck was storport’s
RaUnitScsiFreeDumpPointersIoctl. I guess this was because I reported
SRB_STATUS_BAD_FUNCTION in responce to SRB_FUNCTION_DUMP_POINTERS. Please
correct me if I am wrong. What should I fill in the MINIPORT_DUMP_POINTERS
structure?
Anyway, even if I support the SRB_FUNCTION_DUMP_POINTERS, as my miniport
depends on TCPIP networking stack, will it be possible to support crash
dumps?
Thanks,
Charan
On Wed, Mar 11, 2009 at 12:10 PM, wrote:
> Hi
>
> Im trying to implement the crashdump support for a “virtual miniport
> driver”. For this, Im handling the SRB, SRB_FUNCTION_DUMP_POINTERS, and
> filling the MINIPORT_DUMP_POINTERS structure.
>
> There are some members of MINIPORT_DUMP_POINTERS structures that im not
> sure as to what to fill with. These are
> 1. MappedRegisterBase: What is expected here in case of a miniport driver,
> and also in case of a virtual miniport driver?
> 2. NumberOfAccessRanges
> 3. AccessRanges
>
> Having left them as is with NULL, i get my vminiport driver’s driverentry
> called in dump mode, but my FindAdapter is not called. This made me feel
> that the registration is incomplete.
>
> Also, there is a bus driver below my vminipor driver which is getting
> loaded as “dump_…”. But how could we handle dumpmode for this driver. DDK
> talks about dump mode for only a storage miniport driver.
>
> Not sure how to handle this for a vminiport driver.
>
> Any information would be really helpful.
>
> Thanks
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
Hi,
As I did not know what to set in MINIPORT_DUMP_POINTERS, I just set its size
to sizeof(MINIPORT_DUMP_POINTERS) and set everything elso to 0 or NULL.
Now the bugcheck has gone but I got several other problems. almost each and
every service is reporting that it is failing to start. I can see that on my
disk hosting server regular IO is happening from this Client Vista machine
which uses my network backboned virtual storport miniport driver for
booting. Lots of svchost processes (svchost -k servicename) start failing
with status STATUS_REDIRECTOR_PAUSED or access violation. If I reboot,
sometimes I get no errors at all and I successfully can see the desktop and
run other applications. Sometimes I see no errors but I dont see the
desktop. Just a blank screen with the mouse cursor, and on disk server i can
see lots of IO going on from the client. In this case I can see in WinDbg
that all services have started on the windows vista machine. But still I
dont see the desktop.
Please not that these issues are only on Vista. We have successfully booted
Windows 2003 using same driver (just that on Win2003 I have not supported
SRB_FUNCTION_DUMP_POINTERS)
Request you to please help me as this is a BIG showstopper for us.
Thanks,
Charan
On Wed, Apr 29, 2009 at 10:34 PM, Charansing Rajput wrote:
> Hi windrvlearder,
>
> Have you been able to get answers to your questions?
>
> @All,
>
> I have written a virtual storport miniport driver. Which serves the boot
> disk hosted on network. We are using it to boot windows 2003. So far it does
> not support SRB_FUNCTION_DUMP_POINTERS.
>
> But when we tried to boot Vista with the same driver, during boot process
> we got a bugcheck most probably after disk checking was finished. The
> bugehcek was 0x19 {22,0,0,0} and the culprit shown in the bugcheck was storport’s
> RaUnitScsiFreeDumpPointersIoctl. I guess this was because I reported
> SRB_STATUS_BAD_FUNCTION in responce to SRB_FUNCTION_DUMP_POINTERS. Please
> correct me if I am wrong. What should I fill in the MINIPORT_DUMP_POINTERS
> structure?
>
> Anyway, even if I support the SRB_FUNCTION_DUMP_POINTERS, as my miniport
> depends on TCPIP networking stack, will it be possible to support crash
> dumps?
>
>
> Thanks,
> Charan
>
>
>
> On Wed, Mar 11, 2009 at 12:10 PM, wrote:
>
>> Hi
>>
>> Im trying to implement the crashdump support for a “virtual miniport
>> driver”. For this, Im handling the SRB, SRB_FUNCTION_DUMP_POINTERS, and
>> filling the MINIPORT_DUMP_POINTERS structure.
>>
>> There are some members of MINIPORT_DUMP_POINTERS structures that im not
>> sure as to what to fill with. These are
>> 1. MappedRegisterBase: What is expected here in case of a miniport driver,
>> and also in case of a virtual miniport driver?
>> 2. NumberOfAccessRanges
>> 3. AccessRanges
>>
>> Having left them as is with NULL, i get my vminiport driver’s driverentry
>> called in dump mode, but my FindAdapter is not called. This made me feel
>> that the registration is incomplete.
>>
>> Also, there is a bus driver below my vminipor driver which is getting
>> loaded as “dump_…”. But how could we handle dumpmode for this driver. DDK
>> talks about dump mode for only a storage miniport driver.
>>
>> Not sure how to handle this for a vminiport driver.
>>
>> Any information would be really helpful.
>>
>> Thanks
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
Sometimes I feel sorry for not able to help others while I know the answer to all questions being asked for non-tech reasons.
What I can tell you is it is do-able. There are mass shipping non-msft iscsi sw or hw initiator/crashdump drivers that do or do not rely on TCP/ndis.
Calvin Guan
NetXtreme Converged NIC
Broadcom Corp.
Connecting Everything(r)