Hi all, I have a PCMCIA card driver and it hangs at the
irp after the IRP_MN_START_DEVICE. I believe it is some
irp that queries the interface but my driver just simply
pass these irp down to the lower drivers. So I wonder
what is causing the hang?

What the irps after IRP_MN_START_DEVICE for?

Thanks

Re: Driver hang after IRP_MN_START_DEVICE by Kirk

Kirk
Sun Nov 16 21:11:59 CST 2003

"Wei Wei" <anonymous@discussions.microsoft.com> wrote in message
news:06b801c3ab35$c3219440$a301280a@phx.gbl...
> Hi all, I have a PCMCIA card driver and it hangs at the
> irp after the IRP_MN_START_DEVICE. I believe it is some
> irp that queries the interface but my driver just simply
> pass these irp down to the lower drivers. So I wonder
> what is causing the hang?

You can try !stacks command in windbg to see where it hangs.

-Kirk



Re: Driver hang after IRP_MN_START_DEVICE by Wei

Wei
Mon Nov 17 02:38:39 CST 2003

Hi thanks, I step through the code and found out that the
driver actually did not return from my startdevice
function. I also found out that my driver actually hangs
at a WRITE_PORT_USHORT statement and once that statement
is removed, startdevice function returns successfully.

Now I guess WRITE_PORT_USHORT hangs because my PCMCIA card
actually makes use of the WAIT signal in its I/O reads and
writes and I wonder if there is a way to specify in the
driver that I require the i/o to use WAIT signal. I can
do this easily in WinCE driver but not in Win2k driver.

Any idea?
>-----Original Message-----
>"Wei Wei" <anonymous@discussions.microsoft.com> wrote in
message
>news:06b801c3ab35$c3219440$a301280a@phx.gbl...
>> Hi all, I have a PCMCIA card driver and it hangs at the
>> irp after the IRP_MN_START_DEVICE. I believe it is some
>> irp that queries the interface but my driver just simply
>> pass these irp down to the lower drivers. So I wonder
>> what is causing the hang?
>
>You can try !stacks command in windbg to see where it
hangs.
>
>-Kirk
>
>
>.
>

Re: Driver hang after IRP_MN_START_DEVICE by Maxim

Maxim
Mon Nov 17 18:04:07 CST 2003

> You can try !stacks command in windbg to see where it hangs.

"!process 0 7" is even better though slow a bit - lots of additional info is
printed. A usual way of dealing with bugs on sites you have no access to.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com



Re: Driver hang after IRP_MN_START_DEVICE by Kirk

Kirk
Wed Nov 19 02:38:04 CST 2003

"Wei Wei" <anonymous@discussions.microsoft.com> wrote in message
news:044201c3ace6$32c6f0e0$a501280a@phx.gbl...
> I also found out that my driver actually hangs
> at a WRITE_PORT_USHORT statement and once that statement
> is removed, startdevice function returns successfully.

Are you doing this before or after you send the IRP down to the PDO?
-Kirk