re: Debugging with NDISKD

ndisteam — Thu, 26 May 2011 17:26:20 GMT

> I have met a problem where "current OID" for a miniport is null, while "pending OID" for this miniport is "OID_GEN_CURRENT_PACKET_FILTER". Could you explain more on this?

When an OID is issued, it is first queued on the miniport. Then, if the miniport is ready to receive OID requests, the first OID is removed from the queue and delivered to the miniport. So there are two reasons that you might see no OID is pending while some OIDs are queued:

1. The OID was recently issued, and it hasn't had a chance to be sent to the miniport yet;

2. The miniport is not ready to receive OID requests (e.g., the miniport is currently being reset).

> And the Flags for the miniport has a "REQUEST_TIMEOUT" flag, could you explain when "REQUEST_TIMEOUT" will happen?

The "REQUEST_TIMEOUT" flag is not good. It means that the miniport has spent too long to process an OID request. NDIS detected the timeout and will attempt to reset the miniport. This would probably explain you first question -- NDIS isn't delivering new OIDs because your miniport is being reset.

re: Debugging with NDISKD

lao — Fri, 20 May 2011 10:00:33 GMT

Hello,

I have a question about "current OID" and "pending OID" for a miniport.

I have met a problem where "current OID" for a miniport is null, while "pending OID" for this miniport is "OID_GEN_CURRENT_PACKET_FILTER". Could you explain more on this?

And the Flags for the miniport has a "REQUEST_TIMEOUT" flag, could you explain when "REQUEST_TIMEOUT" will happen?

Thanks very much!