locked
WLK DTM CHAOS failure - Pagefile not found - WHY? RRS feed

  • Question

  • I came across this DTM test job failure when running DTM USB device unclassified test for WHQL driver signature.

    Please advise.

    Windows Logo Kit (WLK) 1.6.8367.000
    USB Class INF device
    Windows 7 32-bit DTM client
    WHQL Driver signature Unclassified DTM
    Driver Reliability
    CHAOS - Concurrent Hardware And OS Test
    Pagefile was not found on "USB\VID_xxxx" or any child devices.
    USB\VID_xxx is not on the paging path, excluding
    One instance of the device must be on the paging path
    Result:   Fail

    Thanks,

    Charles

    Thursday, June 7, 2012 10:57 PM

Answers

  • Sounds to me your device does not set DO_POWER_PAGABLE and the test check and see that it does not have the paging file.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Thursday, June 7, 2012 11:19 PM

All replies

  • Sounds to me your device does not set DO_POWER_PAGABLE and the test check and see that it does not have the paging file.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Thursday, June 7, 2012 11:19 PM
  • No, I did set DO_POWER_PAGABLE in AddDevice fdo flag:

    // Set power management flags in the device object

    fdo->Flags |= DO_POWER_PAGABLE;

    Thursday, June 7, 2012 11:43 PM
  • If you are sure the DO_POWER_PAGABLE is set, is there any change you change its value in response to IRP_MN_DEVICE_USAGE_NOTIFICATION?  And if you do, do you handle things correctly on a potential failure lower in the stack?


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Friday, June 8, 2012 12:31 PM
  • Don,

    In PnP dispatch function, we only handle IRP_MN_SURPRISE_REMOVAL and IRP_MN_REMOVE_DEVICE, we do not explicitly handle IRP_MN_DEVICE_USAGE_NOTIFICATION. Do we have to handle this IRP?

    I traced the code, and I don't see the DO_POWER_PAGABLE is ever changed and is always set properly.

    Friday, June 8, 2012 8:34 PM
  • Yes you need to support it, see http://msdn.microsoft.com/en-us/library/windows/hardware/ff558807(v=vs.85).aspx


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Friday, June 8, 2012 8:46 PM
  • Is this true for a KMDF driver? or only for WDM?  I am getting WHQL errors around this same area.  My driver is a software only KMDF driver, and I do not have a callback defined  for EvtDeviceUsageNotification since we do not use any special file handling.
    Thursday, July 26, 2012 3:35 AM
  • you should not need to explicitly handle special usage notifications in a kmdf driver. you only need to handle them in the storage stacks and some other niche areas.

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, July 26, 2012 4:34 AM
  • Doron, Thanks for the reply.  Would you be able to shed any light on why I am getting the above errors for a KMDF software only driver?  I do make use of D0 Entry/Exit PnP notifications.

    This is one of the errors I am getting:

    Start Test 7/25/2012 11:45:29.952 PM One instance of the device must be on the paging path 

    Message 7/25/2012 11:45:29.952 PM Checking device "{B2683C6A-6445-4030-A3BE-BEEE68CA23B7}\VSCNODE\1&79F5D87&0&01" 
    Message 7/25/2012 11:45:29.952 PM Enumerating child devices. 
    Message 7/25/2012 11:45:29.952 PM Pagefile was not found on "{B2683C6A-6445-4030-A3BE-BEEE68CA23B7}\VSCNODE\1&79F5D87&0&01" or any child devices. 
    Message 7/25/2012 11:45:29.952 PM {B2683C6A-6445-4030-A3BE-BEEE68CA23B7}\VSCNODE\1&79F5D87&0&01 is not on the paging path, excluding 
    End Test 7/25/2012 11:45:29.952 PM One instance of the device must be on the paging path 
    Result:   Fail 
    Repro:   Pagepath, Version=6.1.0.0, Culture=neutral, PublicKeyToken=null /device {B2683C6A-6445-4030-A3BE-BEEE68CA23B7}\VSCNODE\1&79F5D87&0&01 

    Pretty much the same as the OP.

    Thursday, July 26, 2012 2:32 PM
  • The fix for this issue, for me, was that I installed QFE 2,5, and 6.  I have a feeling QFE 6 (the one related to DTM) was what fixed it.
    Tuesday, July 31, 2012 3:59 PM