SunVTS 6.0 Patch Set 1 Release Notes
The SunVTS 6.0 software is compatible with the Solaris 10 Operating System and future compatible releases.
For the latest version of this document, go to: http://www.sun.com/products-n-solutions/hardware/docs/Software/system_administration/tools/testing_valid/sunvts/index.html
ramtest now supports 64-bit x86 Solaris platforms through the Command Line Interface (CLI).
Starting with Solaris 10, the SunVTS infrastructure and a few core diagnostics are available for x86 Solaris platforms. The current x86 support is for the 32-bit operating system only.
SunVTS is supported and tested on the following Sun x86 platforms:
You must install the x86 version of the SunVTS packages to be able 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.
SunVTS x86 Solaris tests are primarily available in 32-bit mode. In addition, three SunVTS tests also support 64-bit mode for x86 Solaris for the AMD64 based Sun platforms. By default, these files are installed in the /bin/64 directory under the base SunVTS install location.
The following tests support 64-bit architecture on x86 Solaris.
Currently, SunVTS does not provide 64-bit infrastructure support for x86 Solaris. For 64-bit x86 support, these tests can be performed as standalone with the Command Line Interface (CLI) only. To view the command-line options use the -u (usage) option as follows:
Refer to the README.64 file for more information.
Use the following command to receive SunVTS 5.1 package information:
You can also use either of the following commands to receive additional SunVTS 5.1 package information:
In addition, you can use the SunVTS standard command line argument, -V, to recieve version information.
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.
The ECC Error Monitor in vmemtest and pmemtest is incorrectly enabled by default. The ECC Error Monitor will be disabled by default in the next release of SunVTS, and thus the memory ECC errors will be hidden. Do not replace DIMMs due to memory ECC errors unless the Solaris Fault Management Architecture (FMA) evaluates and suggests such an action.
sunpci2test now supports the SunPCi-3 cards. Solaris 10 supports SunPCi-3 Version 3.2.2 with Patch 118591-01 only. Solaris 10 does not support the SunPCi-2 card.
SAI/P and SPIF hardware is not currently supported on Solaris 10. The Serial Parallel Controller Test (spiftest) and Serial Asynchronous Interface (PCI) Test (saiptest) will be supported once the SAI/P and SPIF hardware is supported on Solaris 10. This support is expected to be available soon.
cddvdtest could possibly register readonly options for the DVD+RW media type. If the test is stopped during the writing operation for the DVD+RW media, the test could get registered with readonly options the next time SunVTS is invoked.
Workaround: Either replace the media with a blank copy or run the test only on the basis of pass counts. Do not stop the test during a pass.
cddvdtest could fail to test DVD+RW media. When cddvdtest is run on DVD+RW media, the test could cause media write failures. If this occurs, error messages similar to the following are displayed:
Workaround: Replace the media with a blank copy.
Performing usbtest on systems with audio cards could cause the test to report errors that are not incremented in the error count. Error messages similar to the following are displayed in the vtsk.err file.
Dec 10 18:43:40 npgfx-1 SunVTS6.0: [VTSID NONE usbtest.probe] Failed to open /dev/sound/2 (Invalid argument)." Probable_Cause(s): <Faulty USB device or motherboard hardware.> <System software problem.> Recommended_Action(s): <Examine system message files (/var/adm/messages) for other information.>
usbtest could fail with error messages in "Test Messages" and in the sunvts.err file, but "failures" does not get incremented and the test reports passes instead.
Additionally, usbtest could report error messages similar to the following on a system without a printer attached.
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.
The SunVTS 6.0 SUNWvtsmn package contains HTML files from the SunVTS 6.0 Test Reference Manual and User's Guide. However, updates were made to the SunVTS 6.0 Test Reference Manual that are not reflected in the version of the HTML files located in the SUNWvtsmn package.
Workaround: Use the SunVTS 6.0 Test Reference Manual available at http://docs.sun.com/app/docs/coll/1140.1
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.
32-bit SunVTS software performed with the x86 binary on a 64-bit Solaris Operating System causes a systest error. The SunVTS 6.0 x86 version supports the 32-bit SunVTS binary only. If a 32-bit SunVTS binary is used on a 64-bit Solaris Operating System and systest is performed with the vtsui or the vtstty interface, systest fails immediately. systest does not display the right error message, for example:
12/08/04 14:19:23 machinename SunVTS6.0: VTSID 8010 systest.FATAL system: "kvm_open() failed: Error 0."Probable_Cause(s): <Attempted to use a 32-bit version of the libkvm interfaces to open a 64-bit kernel image.> Recommended_Action(s): <Run the 64-bit version of the test.>
Workaround: for systest by using command line interface with option
env5test and i2ctest could fail due to a Solaris 10 Operating System PICL initialization issue. When PICL is stopped and started, the tests pass appropriately.
Workaround: Enter the following commands directly after the Solaris Operating System 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.
pptest could hang when performed in the Functional test mode with the Printer subtest enabled in the Test Parameter Options dialog box.
fwcamtest could hang with the following error message: "Termination of tests could be hung. Deselect tests to bring sunvts to an idle status." If dcamtest is deselected, all records regarding the test are removed. Display of the video does not go away after deselecting and quitting SunVTS. Black video output is seen from the video window.
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 and Solaris 8 HW 3/03 operating systems. If this failure occurs, you see an error message similar to the following:
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.