SD Paging Tests

  • Article

This test validates paging functionality by reading and writing a buffer of physical memory size under stress conditions.

Test details

   
Specifications
  • Device.Storage.Hd.EMMC.BasicFunction
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows Server 2016 (x64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
Expected run time (in minutes) 120
Category Development
Timeout (in minutes) 7200
Requires reboot false
Requires special configuration false
Type automatic

 

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

Running the test

Before you run the test, complete the test setup as described in the test requirements: WDTF System Fundamentals Testing Prerequisites.

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

Check the WTT Trace by performing the following steps:

  • View Task Log of Run SDBus Paging Test.

  • Open the log file SoCBootTest.wtl.

  • Check for messages that may solve the issue.

For additional troubleshooting information, see Troubleshooting System Fundamentals Testing.

More information

This test will enable paging with Driver Verifier's Force Pending I/O Requests and Low Resources Simulation set. This will test two things:

  • The ability of a driver to accomplish forward progression (failed allocations simulate that) and to ensure that the driver cannot page itself out.

  • Force Pending I/O Requests will attempt to page the entire driver, thus producing an immediate stop error if the driver cannot protect against that.

Command usage

Command Description

SocBootTest.exe MemoryChokeIO

Runs the MemoryChokeIO scenario of the SoCBootTest.

SocBootTest.exe DiskStress

Runs the DiskStress scenario of the SoCBootTest.

SocBootTest.exe MemoryStress

Runs the MemoryStress scenario of the SoCBootTest.

 

Command syntax

Command option Description

MemoryChokeIO

Runs MemoryChoke and BigFile in parallel.

DiskStress

Runs DiskStress.

MemoryStress

Runs MemoryStress.

Note

   For command-line help for this test, type /?.

 

File list

File Location

autocom.dll

<[testbinroot]>\nttest\driverstest\storage\

autocomManaged.dll

<[testbinroot]>\nttest\driverstest\storage\managed\

BigFile.exe

<[testbinroot]>\nttest\driverstest\storage\disk\

DiskStress.exe

<[testbinroot]>\nttest\driverstest\storage\sd\SDBoot\

MemoryChoke.exe

<[testbinroot]>\nttest\driverstest\storage\sd\SDBoot\

MemoryStress.exe

<[testbinroot]>\nttest\driverstest\storage\sd\SDBoot\

SocBootTest.exe

<[testbinroot]>\nttest\driverstest\storage\sd\SDBoot\SoCBootTest\

SDHelper.dll

<[testbinroot]>\nttest\driverstest\storage\sd\Tools\SDHelper\

etwprocessor.dll

<[taefbinroot]>\

wex.common.dll

<[testbinroot]>\wextest\cue\testexecution\wlk\

wex.communication.dll

<[testbinroot]>\wextest\cue\testexecution\

ntlog.dll

<[osbinroot]>\NTTEST\commontest\ntlog\

ntlogger.ini

<[osbinroot]>\NTTEST\commontest\ntlog\

stresslog.dll

<[testbinroot]>\nttest\basetest\core_file_services\shared_libs\

fbslog.dll

<[testbinroot]>\nttest\basetest\core_file_services\shared_libs\fbslog\

rapidfile.exe

<[testbinroot]>\nttest\basetest\core_file_services\shared_tests\wdk\

 

Parameters

Parameter name Parameter description
LLU_NetAccessOnly User account for accessing test fileshare.
LLU_LclAdminUsr User account for running the test.