SunVTS 6.1 Release Notes |
The SunVTS 6.1 software is designed for the Solaris 10 1/06 Operating System (OS) and is compatible with the Solaris 10 3/05 OS.
For the latest version of this document (819-2363), go to: http://www.sun.com/documentation
Starting with the Solaris 10 OS, the SunVTS infrastructure and core diagnostics are available for x86 platforms. Starting with Solaris 10 3/05 HW1, SunVTS diagnostics for x86 platforms are supported in the AMD 64-bit environment for the SunVTS kernel (vtsk). All diagnostics except the System Test (systest) are ported to 64-bit.
SunVTS is supported and tested on the following Sun x86 platforms:
You must install the x86 version of the SunVTS packages to perform SunVTS on x86 platforms. The software packages use the same names as in the SPARC® environment. The SunVTS packages delivered separately for both x86 and SPARC Solaris platforms are as follows:
The SunVTS components available for x86 Solaris platforms are as follows.
Use the following command to display SunVTS package information:
You can also use either of the following commands to display additional SunVTS package information:
Use either of the following commands to display SunVTS version information:
Install and Uninstall Using the Same Program
Use the same tool or utility for installation and removal of the SunVTS software. If you use pkgadd for installation, use pkgrm to uninstall; if you use Web Start for installation, use the Product Registry to uninstall.
When too many instances of SunVTS functional tests are run in parallel on UltraSPARC® T1 CMT CPU-based (sun4v) entry-level servers with low memory configurations, SunVTS tests might fail due to lack of system resources. For example, you could see an error message similar to the following:
Workaround: Decrease the number of SunVTS test instances or perform SunVTS functional tests separately. In addition, you can increase the delay value for CPU tests or increase the test memory reserve space.
The usbtest keyboard test might indicate a successful keyboard probe when a keyboard is not present.
Performing netlbtest on all ipge ports simultaneously in systems with Sun PCI-Express Dual Gigabit MMF/UTP adapters could fail. Performing netlbtest on one port per adapter, avoids this failure.
Workaround: Perform netlbtest on one port per Sun PCI-Express Dual Gigabit MMF/UTP adapter.
The netlbtest external loopback test could incorrectly report that the test passed when no loopback packets were transmitted or received by the ipge driver.
On dual-port host bus adapters (HBAs), testing both ports simultaneously could cause intermittent test failures.
Workaround: Test only one port of dual-port HBAs at a time.
audiotest on Sun Ultra 45 workstations currently supports the line-in/line-out external loopback test only.
Creating option files on Sun Enterprise and Sun Fire 15K servers (UltraSPARC III) with the SunVTS GUI could cause a core dump.
Workaround: Use the TTY user interface to create option files.
SunVTS memory tests might log a warning message similar to the following in rare cases when the ECC Error Monitor (errmon) option is enabled.
Workaround: Disable the errmon option. The errmon option is disabled by default.
Installing SunVTS x86 packages on a SPARC server to serve x86 clients with SunVTS images is not supported. Installing SunVTS SPARC packages on an x64 or x86 server to serve SPARC clients is supported.
In rare cases, repeated reuse of DVD+RW optical media on Sun Ultra 45 workstations could cause failures when performing high stress DVD+RW SunVTS tests.
Workaround: Replace the DVD+RW media upon failure, or use other types of media such as CD-RW.
cddvdtest might fail when used for testing CD/DVD RW drives with Read/Write media.
Workaround: Either use a blank media for testing, or insert a CD-ROM media into the drive and restart SunVTS. The user interface then invokes the test with read only options.
Sun Blade 100 and 150 systems with SunVTS can produce errors when the serial port controller (southbridge) is also handling other traffic as data access from and to the IDE hard disk. With SunVTS simultaneously running serialtest and disktest on Sun Blade 100 and 150 systems, you might see serialtest report failures.
Workaround: Do not perform serialtest and disktest simultaneously.
If processor sets are defined, you must first delete the processor sets before running SunVTS.
The Netra CT 820 server is not currently supported in Solaris 9 or Solaris 10 Operating Systems.
Performing qlctest with the default settings (Exclusive test mode and Online Selftest enabled) could fail with an error message similar to the following:
Workaround: Disable the Online Selftest.
env5test and i2ctest could fail due to a Solaris 10 OS PICL initialization issue. When PICL is stopped and started, the tests pass appropriately.
Workaround: Enter the following commands directly after the Solaris OS is booted:
On Sun Fire 15K systems, adding new boards with DR might cause some of the processor and memory related tests to perform ineffectively. Specifically, cmttest might fail to recognize the CMT processors on the new board. Similar failures might also occur in l2sramtest, l1dcachetest, dtlbtest, ramtest, bustest, mptest, and fputest.
Workaround: Reboot the system after adding a new board with DR.
pfbtest might fail when performed in the Gnome desktop environment on a Sun XVR-100 graphics accelerator if the test is performed in the default console window.
This failure does not occur in the Solaris 8 2/02 OS and the Solaris 8 HW 3/03 OS. If this failure occurs, an error message similar to the following is displayed:
Workaround: Most graphics tests fail when running under Gnome. Enter the xscreensaver-command -exit command before performing graphics test under the Gnome desktop environment to avoid these failures.
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.