Prev: WDF supplied functions send reset packet twice through USB
Next: Modification to msvad "virtual Audio device"
From: Steve U on 8 Feb 2007 18:22
I'm working on a port of a ScsiPort driver to StorPort and have run into a
wall. After doing some minor changes to get the old ScsiPort driver working
as a StorPort, I'm seeing a bugcheck in storport.sys at boot time. My
driver is not in the stack, so I'm having trouble sorting out what storport
is choking on. Is there a way of getting a source code license for
storport.sys? I'm building with the DDK 3790.1830, testing on 32bit x86
Windows 2003 Server SP1.

(Background info: Effectively I've taken my old ScsiPort driver and rebuilt
it using the StorPort headers and the STOR_USE_SCSI_ALIASES option to
establish a baseline from which I can make further changes to support full
duplex mode and BuildIo. I can see that it starts up and initializes fine
via the debug messages I'm seeing. But after initialization of the driver
completes successfully that there's a pause and then this bugcheck. )

Call stack:

STACK_TEXT:
f789e5bc ba990eb9 f789e7b0 f789e628 8a5b5fc0
storport!RaidBusEnumeratorIssueSynchronousRequest+0x56
f789e5e0 ba99105e 8a5b5fc0 00000000 f789e628
storport!RaidBusEnumeratorIssueReportLuns+0x3d
f789e604 ba991104 f789e7b0 00000000 f789e628
storport!RaidBusEnumeratorGetLunListFromTarget+0x24
f789e654 ba98e337 f789e7b0 00000000 f789e694
storport!RaidBusEnumeratorGetLunList+0x36
f789e798 ba98e401 8a54ab70 ba990f9c f789e7b0
storport!RaidAdapterEnumerateBus+0xbd
f789e7f4 ba99b469 8a54ab70 8a5b2cb8 8a54abf8
storport!RaidAdapterRescanBus+0x49
f789e81c ba99badc 8a54ab70 8a5b2cb8 8a5b2d70
storport!RaidAdapterQueryDeviceRelationsIrp+0x5f
f789e838 ba99be47 8a54ab70 8a5b2cb8 f789e85c storport!RaidAdapterPnpIrp+0x11c
f789e848 8081dce5 8a54aab8 8a5b2cb8 f789e8cc storport!RaDriverPnpIrp+0x33
f789e85c 8090caac 8a4b3008 00000000 8a4b30e8 nt!IofCallDriver+0x45
f789e888 8082349b 8a54aab8 f789e8a8 8a4b30e8 nt!IopSynchronousCall+0xbe
f789e8d0 80908ea9 00000000 8a5434b0 00000000 nt!IopQueryDeviceRelations+0x45
f789e8e8 8090c167 8a4b3008 00000000 00000000 nt!PipEnumerateDevice+0x23
f789eb40 80822ec0 8a590910 00000000 00000000 nt!PipProcessDevNodeTree+0x21b

From: Steve U on 23 Feb 2007 12:13
This turned out to be a bug in the storport class driver... see:

http://support.microsoft.com/kb/916048

-Steve

"Steve U" wrote:

> I'm working on a port of a ScsiPort driver to StorPort and have run into a
> wall. After doing some minor changes to get the old ScsiPort driver working
> as a StorPort, I'm seeing a bugcheck in storport.sys at boot time. My
> driver is not in the stack, so I'm having trouble sorting out what storport
> is choking on. Is there a way of getting a source code license for
> storport.sys? I'm building with the DDK 3790.1830, testing on 32bit x86
> Windows 2003 Server SP1.
>
> (Background info: Effectively I've taken my old ScsiPort driver and rebuilt
> it using the StorPort headers and the STOR_USE_SCSI_ALIASES option to
> establish a baseline from which I can make further changes to support full
> duplex mode and BuildIo. I can see that it starts up and initializes fine
> via the debug messages I'm seeing. But after initialization of the driver
> completes successfully that there's a pause and then this bugcheck. )
>
> Call stack:
>
> STACK_TEXT:
> f789e5bc ba990eb9 f789e7b0 f789e628 8a5b5fc0
> storport!RaidBusEnumeratorIssueSynchronousRequest+0x56
> f789e5e0 ba99105e 8a5b5fc0 00000000 f789e628
> storport!RaidBusEnumeratorIssueReportLuns+0x3d
> f789e604 ba991104 f789e7b0 00000000 f789e628
> storport!RaidBusEnumeratorGetLunListFromTarget+0x24
> f789e654 ba98e337 f789e7b0 00000000 f789e694
> storport!RaidBusEnumeratorGetLunList+0x36
> f789e798 ba98e401 8a54ab70 ba990f9c f789e7b0
> storport!RaidAdapterEnumerateBus+0xbd
> f789e7f4 ba99b469 8a54ab70 8a5b2cb8 8a54abf8
> storport!RaidAdapterRescanBus+0x49
> f789e81c ba99badc 8a54ab70 8a5b2cb8 8a5b2d70
> storport!RaidAdapterQueryDeviceRelationsIrp+0x5f
> f789e838 ba99be47 8a54ab70 8a5b2cb8 f789e85c storport!RaidAdapterPnpIrp+0x11c
> f789e848 8081dce5 8a54aab8 8a5b2cb8 f789e8cc storport!RaDriverPnpIrp+0x33
> f789e85c 8090caac 8a4b3008 00000000 8a4b30e8 nt!IofCallDriver+0x45
> f789e888 8082349b 8a54aab8 f789e8a8 8a4b30e8 nt!IopSynchronousCall+0xbe
> f789e8d0 80908ea9 00000000 8a5434b0 00000000 nt!IopQueryDeviceRelations+0x45
> f789e8e8 8090c167 8a4b3008 00000000 00000000 nt!PipEnumerateDevice+0x23
> f789eb40 80822ec0 8a590910 00000000 00000000 nt!PipProcessDevNodeTree+0x21b
>
 | 
Pages: 1
Prev: WDF supplied functions send reset packet twice through USB
Next: Modification to msvad "virtual Audio device"