none
CHAOS, One instance of the device must be on the paging path -- Fails RRS feed

  • Question

  • I posted in the "Windows Hardware Testing and Certification" forum but did not get any response. I thought that I try it here.

    I run the CHAOS test job multiple times, and occasionally, the "One instance of the device must be on the paging path" subtest fails.

    Again, this WLK1.6 with all of the latest QFE and filter installed in the controller. Any comments/hint/suggestion are welcomed.

    Here is the log:

    Start Test 2/27/2013 4:01:34.621 PM One instance of the device must be on the paging path
    Message 2/27/2013 4:01:34.621 PM Checking device "{91E7AF5C-8DE2-4342-806A-C87CD5541E9D}\{2B78B334-A58F-4E88-8926-74AECF3219E8}\HID#VID_0C2E&PID_0907&REV_00=1:6&29A8B1A9&0&0000"
    Message 2/27/2013 4:01:34.621 PM Enumerating child devices.
    Message 2/27/2013 4:01:34.621 PM Pagefile was not found on "{91E7AF5C-8DE2-4342-806A-C87CD5541E9D}\{2B78B334-A58F-4E88-8926-74AECF3219E8}\HID#VID_0C2E&PID_0907&REV_00=1:6&29A8B1A9&0&0000" or any child devices.
    Message 2/27/2013 4:01:34.621 PM {91E7AF5C-8DE2-4342-806A-C87CD5541E9D}\{2B78B334-A58F-4E88-8926-74AECF3219E8}\HID#VID_0C2E&PID_0907&REV_00=1:6&29A8B1A9&0&0000 is not on the paging path, excluding
    End Test 2/27/2013 4:01:34.621 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 {91E7AF5C-8DE2-4342-806A-C87CD5541E9D}\{2B78B334-A58F-4E88-8926-74AECF3219E8}\HID#VID_0C2E&PID_0907&REV_00=1:6&29A8B1A9&0&0000

    thanks,

    Kiet


    KAL

    Wednesday, February 27, 2013 9:49 PM

All replies

  • That subtask should not cause the overall test to fail. It's type is "Ignore fail and continue". Are you seeing any other tasks that are  failing?

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

    • Marked as answer by Doron Holan [MSFT] Wednesday, February 27, 2013 11:24 PM
    • Unmarked as answer by Kiet Ly Thursday, February 28, 2013 12:08 AM
    Wednesday, February 27, 2013 10:23 PM
  • Yes, this subtask does not cause the overall CHAOS test job to fail. The other task, "Run DevPathExer" fails with the below complaint from the log:

    Message 2/26/2013 9:58:52.804 AM Trying to open \Device\00000074 as NamedPipe
    Message 2/26/2013 9:58:52.804 AM Trying to open \Device\00000074 as Mailslot
    Message 2/26/2013 9:58:52.804 AM Trying to open \Device\00000074 with option FILE_CREATE_TREE_CONNECTION
    Message 2/26/2013 9:58:52.804 AM END TESTING: device 00000074, driver PTVD
    Error 2/26/2013 10:00:01.804 AM Invalid driver service name 'PTVD'? NtQueryVolumeInformationFile for FileFsDriverPathInformation failed
    Possible causes of this error are: Driver is not currently loaded, Mistyped Driver Service Name, etc
    File: Line: 0
    Error Type: HRESULT
    Error Code: 0xc0000034
    Error Text: Error 0xc0000034
    End Test 2/26/2013 10:00:01.804 AM Device Path Exerciser Test
    Result: Fail
    Repro: devpathexer.exe /hct /fu 4060 /dr "PTVD"

    The thing that bother me is that the test result is inconsistent. Sometimes it fails, sometimes it passes. Multiple runs on the exact same test setup (i.e. the same target machine, same device, same driver, ...). WHY? Any comments?

    Is this a timing issue? timing that test script execute and ping the device while it is still coming up ?

    Also, what is the purpose of having test task with type "Ignore fail and continue" ?

    thanks,


    KAL

    Thursday, February 28, 2013 10:10 PM
  • comments, anyone?

    KAL

    Friday, March 1, 2013 3:50 PM