No idea. I have not looked into storport in a long time, so I do not know the hot issues in it off the top of my head. Perhaps a debug version of it with the appropriate debug mask turned on will lead to more data.
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tarun Singh
Sent: Monday, April 07, 2008 3:07 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] Getting the NIC binding in Bus Driver
What could be the problem then? Any clue or it
requires storport stack to debug?
-Tarun
— Doron Holan wrote:
> A bus driver is the PPO for the FDO it creates in
> EvtDriverDeviceAdd. A bus driver is not the PPO
> (typically) for any of the PDOs it creates, the FDOs
> which load on your bus’s PDOs are the PPOs for those
> stacks.
>
> d
>
> -----Original Message-----
> From: Tarun Singh [mailto:xxxxx@yahoo.com]
> Sent: Monday, April 07, 2008 2:48 PM
> To: Windows System Software Devs Interest List
> Cc: Doron Holan
> Subject: RE: Re:[ntdev] Getting the NIC binding in
> Bus Driver
>
> We are using Bus driver (Virtual Bus), then I think
> it
> owns the power policy for it’s bus. Is that a
> problem?
>
> -Tarun
> — Doron Holan wrote:
>
> > I am not suggesting that you mark the PDO as raw
> or
> > as the power policy owner? You should keep the
> code
> > as is. The reason I asked is that sometimes when
> > there are 2 power policy owners in the stack,
> these
> > types of problems (power irps that are not
> > completed) occur.
> >
> > d
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On
> Behalf
> > Of Tarun Singh
> > Sent: Monday, April 07, 2008 1:51 PM
> > To: Windows System Software Devs Interest List
> > Subject: RE: Re:[ntdev] Getting the NIC binding in
> > Bus Driver
> >
> > I am using the Bus_CreatePdo() module as is to
> > create
> > the child PDO as described by the sample. In this
> I
> > don’t see this option for the CHILD PDO as raw or
> as
> > the power policy owner, I this should be for FDO.
> >
> > I am also using the Bus_EvtDeviceAdd() to create
> FDO
> > as is, and I don’t see that options specified
> here,
> > what call I need for this in the KMDF version for
> > dynamic Bus driver.
> >
> > -Tarun
> >
> > — Doron Holan wrote:
> >
> > > Are you marking the PDO as raw or as the power
> > > policy owner?
> > >
> > > -----Original Message-----
> > > From: Tarun Singh [mailto:xxxxx@yahoo.com]
> > > Sent: Monday, April 07, 2008 1:21 PM
> > > To: Windows System Software Devs Interest List
> > > Cc: Doron Holan
> > > Subject: RE: Re:[ntdev] Getting the NIC binding
> in
> > > Bus Driver
> > >
> > > Yeah \Driver\ifcoevm is my driver for a PDO
> > created
> > > by
> > > the bus driver. And \Device\RaidPort is system
> > > created, I think sortport owns it.
> > >
> > > This time I did hibernation, I have one instance
> > of
> > > my
> > > driver loaded in the system, so only IRP is
> > pending,
> > > Here is the dump:
> > >
> > > 0: kd> !irp 0x8a114200 ff
> > > Irp is active with 2 stacks 2 is current (=
> > > 0x8a114294)
> > > No Mdl: No System Buffer: Thread 00000000: Irp
> > > stack
> > > trace.
> > > Flags = 00000000
> > > ThreadListEntry.Flink = 8a114210
> > > ThreadListEntry.Blink = 8a114210
> > > IoStatus.Status = 00000000
> > > IoStatus.Information = 00000000
> > > RequestorMode = 00000000
> > > Cancel = 00
> > > CancelIrql = 0
> > > ApcEnvironment = 00
> > > UserIosb = 00000000
> > > UserEvent = 00000000
> > > Overlay.AsynchronousParameters.UserApcRoutine =
> > > 00000000
> > > Overlay.AsynchronousParameters.UserApcContext =
> > > 00000000
> > > Overlay.AllocationSize = 00000000 - 00000000
> > > CancelRoutine = 00000000
> > > UserBuffer = 00000000
> > > &Tail.Overlay.DeviceQueueEntry = 8a114240
> > > Tail.Overlay.Thread = 00000000
> > > Tail.Overlay.AuxiliaryBuffer = 00000000
> > > Tail.Overlay.ListEntry.Flink = 00000000
> > > Tail.Overlay.ListEntry.Blink = 00000000
> > > Tail.Overlay.CurrentStackLocation = 8a114294
> > > Tail.Overlay.OriginalFileObject = 00000000
> > > Tail.Apc = 00000000
> > > Tail.CompletionKey = 00000000
> > > cmd flg cl Device File
> > > Completion-Context
> > > [16, 0] 0 0 8a08fe58 00000000
> > ba634752-00000000
> > >
> > > \Driver\IFCoEProt
> > > storport!RaidAdapterSetSystemPowerCompletion
> > > Args: 00000000 00000000
> > > 00000000 00000003
> > > >[16, 2] 0 e0 8a0d6620 00000000
> > 809b0e62-84838a10
> > > Success Error Cancel
> > > \Driver\ifcoevm
> > > nt!PopCompleteSystemPowerIrp
> > > Args: 00000000 00000000
> > > 00000005 00000003
> > >
> > > -Tarun
> > > — Doron Holan
> wrote:
> > >
> > > > Is \Driver\ifcoevm your driver? What is
> > > > \Device\RaidPort0? A PDO or FDO? What is the
> > > > output of !irp ff for each of the irps
> > > listed
> > > > (e.g. !irp 89ff0c90 ff)
> > > >
> > > > d
> > > > -----Original Message-----
> > > > From: Tarun Singh
> [mailto:xxxxx@yahoo.com]
> > > > Sent: Monday, April 07, 2008 12:20 PM
> > > > To: Windows System Software Devs Interest List
> > > > Cc: Doron Holan
> > > > Subject: Re:[ntdev] Getting the NIC binding in
> > Bus
> > > > Driver
> > > >
> > > > Hi:
> > > >
> > > > I used the KMDF version of the dynamic bus
> > version
> > > > to
> > > > create the child PDO when driver notices a new
> > NIC
> > > > Binding, I loaded the virtual storage miniport
> > > > driver
> > > > on this newly created child PDO, which works
> > fine,
> > > > but
> > > > I am seeing a problem of system hang during
> > system
> > > > shutdown and hibernation. The system keep
> > > displaying
> > > > the following line,
> > > >
> > > > During shutdown it keeps displaying:
> > > > Waiting on: \Driver\ifcoevm \Device\RaidPort0
> > irp
> > > > (89ff0c90) SetPower-Shutdown status 0
> > > >
> > > >
> > > > During hibernation it keeps displaying:
> > > > Waiting on: \Driver\ifcoevm \Device\RaidPort0
> > irp
> > > > (89cc6cd8) SetPower-Hibernate status 0
> > > >
> > > > Is this is a known issue? If you have a fix,
> > where
> > > I
> > > > can get it from. I am using the W2K3 SP2 with
> > web
> > > > updates for the virtual storport available.
> > > >
> > > > -Tarun
> > > >
> > > > — Doron Holan
> > wrote:
>
=== message truncated ===
—
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