Unexpected driver verifier message"The previously-set IRP_MJ_POWER status has been converted to STATUS_NOT_SUPPORTED"
in [Device Drivers]
|
Prev: Unexpected driver verifier message"The previously-set IRP_MJ_POWER status has been converted to STATUS_NOT_SUPPORTED"
Next: Device properties registry permissions
From: Don Burn on 22 Jun 2010 16:47 Did you indicate the device could do wait wake from the IRP_MN_QUERY_CAPABILITES request, if so I beliew you will see what you are getting. Why someone would have a WDM bus driver these days unless it already existing and the changes are not too major is beyond me, KMDF is definitely the way to go here. Don Burn (MVP, Windows DKD) Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr > -----Original Message----- > From: rwielica [mailto:rwielica(a)gmail.com] > Posted At: Tuesday, June 22, 2010 4:14 PM > Posted To: microsoft.public.development.device.drivers > Conversation: Unexpected driver verifier message"The previously-set > IRP_MJ_POWER status has been converted to STATUS_NOT_SUPPORTED" > Subject: Unexpected driver verifier message"The previously-set IRP_MJ_POWER > status has been converted to STATUS_NOT_SUPPORTED" > > Hi All, > I'm working on the WDM bus driver that cooperates with UMDF client drivers > (FDOs) under Win7. During the testing with verifier on I found driver verifier > to stop debugger with a message "The previously-set IRP_MJ_POWER status has > been converted to STATUS_NOT_SUPPORTED." > The problem occurs when UMDF FDO driver sends WAIT_WAKE IRP which I'm > completing with STATUS_NOT_SUPPORTED. > I traced the IRP from the beginning and I don't understand why verifier is > complaining this way - as per MSDN bus driver is allowed to complete the > WAIT_WAKE IRP with STATUS_NOT_SUPPORTED (as WaitWake is disabled by policy on > my bus). I'm returning STATUS_NOT_SUPPORTED in a Power dispatch routine as > well. > Did anyone noticed similar situation ? What is the triggering verifier > complain in this case ? > Regards R > > > __________ Information from ESET Smart Security, version of virus signature > database 5219 (20100622) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > |