I’ve run across a problem using wdfUsbTargetDeviceCyclePortSynchronously()
in KMDF10.
I’ve never tried using this particular command on the OSR USB Dev Kit and
wasn’t sure if this is supported, so I expected 50/50 chance of it failing.
The command did fail but not in a manner I expected.
Output from winDBG;
IOCTL decode failed 0x81f7d81c
RTL: RtlNtStatusToDosError(0x81f7d81c): No Valid Win32 Error Mapping
RTL: Edit ntos\rtl\generr.c to correct the problem
RTL: ERROR_MR_MID_NOT_FOUND is being returned
The first line is a KdPrint from the driver, the rest was printed in winDBG
automatically.
The most confusing thing is the NTSTATUS value 0x81f7d81c that doesn’t
appear in <ntstatus.h>.
Without the an NTSTATUS code I’m not sure if I can debug this further.
Has anyone else encountered this?
I’m a bit of noob so forgive me if this is something really simple!
Chris</ntstatus.h>
So this is a lesson in trying to debug before my first cup of coffee.
I wasn’t even calling the function, just returning a garbage status.
Chris
wrote in message news:xxxxx@ntdev…
> I’ve run across a problem using wdfUsbTargetDeviceCyclePortSynchronously()
> in KMDF10.
> I’ve never tried using this particular command on the OSR USB Dev Kit and
> wasn’t sure if this is supported, so I expected 50/50 chance of it
> failing.
>
> The command did fail but not in a manner I expected.
> Output from winDBG;
>
> IOCTL decode failed 0x81f7d81c
> RTL: RtlNtStatusToDosError(0x81f7d81c): No Valid Win32 Error Mapping
> RTL: Edit ntos\rtl\generr.c to correct the problem
> RTL: ERROR_MR_MID_NOT_FOUND is being returned
>
> The first line is a KdPrint from the driver, the rest was printed in
> winDBG automatically.
> The most confusing thing is the NTSTATUS value 0x81f7d81c that doesn’t
> appear in <ntstatus.h>.
> Without the an NTSTATUS code I’m not sure if I can debug this further.
>
> Has anyone else encountered this?
> I’m a bit of noob so forgive me if this is something really simple!
>
> Chris
>
>
></ntstatus.h>