Share via

Sleep Stress with IO

  • Article

Type: Automated Test

Overview

The Sleep Stress with IO job ensures that the Device under test permits the system to be cycled through all supported sleep states. Additionally, it ensures that the device is still functional after these state changes through SimpleIO stress testing.

Details

The Sleep Stress with IO job is the "Driver Reliability" version of the Sleep_Stress_with_IO automated scenario.

The test directs the underlying scenario to target the Device under test via its service name or device instance ID.

The script has the following command line parameters:

Devices – The device(s) to run stress on. By default, the test runs IO stress on all media, network, and disk devices.

MinutesToRun – The amount of time the script will run.

SleepPeriod – The RTC timer will be set to this value (in minutes) each time the machine goes into sleep mode.

MinIOPeriod and MaxIOPeriod specify the time (in milliseconds) that IO tests will be running between subsequent sleep cycles.

ResumeDelay – The delay time (in milliseconds) after the machine resumes from sleep mode and before next IO cycle starts. The delay time is necessary to allow devices to restore their working state (renew IP address for network card and so on).

The script runs IO tests for a random amount of time between minimum and maximum values. Then it pauses the SimpleIO, picks up the next supported sleep state, and sends the computer into sleep mode with an RTC wake timer set to automatically wake the computer. After the computer wakes up, these actions are repeated until MinutesToRun minutes pass.

Run Time: 40 minutes
Log File:
System Restart Required: No
Test Category:
Supported operating systems for Logo or Signature testing:

  • Windows 7
  • Windows Server 2008 R2
  • Windows Vista
  • Windows Server 2003
  • Windows XP

Program: 

Requirements

Software Requirements

The test tool requires the following software:

  • Supported operating system (see list above)
  • Software components included with the device that is being tested
  • Windows Device Testing Framework components

Hardware Requirements

The test tool requires the following hardware:

  • Device to be tested
  • Computer that meets the minimum software requirements
  • Windows keyboard
  • Two-button pointing device
  • Color display monitor capable of at least 1024 by 768 resolution, 32-bits per pixel, 60 Hz
  • Hard drive with a minimum of 20 GB available on partition C:

Processor

The test tool runs on the following processor architectures:

  • x86
  • x64
  • Itanium

Running Sleep Stress with IO

Prerequisite: Before you can run Sleep Stress with I/O, install the device and driver on the test client. Next, install and configure DTM.

To Run Sleep Stress with I/O Test

  1. Start DTM Studio.
  2. Open or switch to the Device Console window, and then select the machine pool that contains the computer where you want to run the test.
  3. In the Available Devices pane, expand the type of device that is associated with your driver, and then click the specific device on which to run the test.
  4. In the Available Jobs pane, click the Sleep Stress with I/O job.
  5. Click Add Selected in the lower-left corner of the Device Console window to add the jobs to the schedule of jobs to be run.
  6. Click Schedule Jobs.
  7. Follow the progress of the Sleep Stress with I/O job by using Job Monitor. Use the Result Explorer to examine the results of jobs that have completed. The test creates additional log files that contain detailed information about what the test is doing. You can use these log files to help you determine why a test failed.

Troubleshooting

The underlying scenario was developed using the new Windows Device Testing Framework (WDTF). The WDK contains extensive documentation for using and extending this framework in your own driver development process. Search the WDK help documentation for "Windows Device Testing Framework" for more information. You can also find this information in the table of contents in the WDK documentation under Windows Driver Kit > Other Tools > Windows Device Testing Framework > Automated Scenarios.

You may receive an error message similar to the following: "SimpleIOStress Failed! -> IcmpSendEcho() had too many consecutive timeouts. Win32=1214 - The format of the specified network name is invalid." This failure can be caused by network latency, which can be improved by trying one or more of the following steps:

  • Disable DHCP and use static IP addressing.
  • Place a router or switch directly between the controller and client.
  • For redundant network paths, add an additional NIC connected to the network.

Send feedback on this topic
Built on December 10, 2009