| SunVTS 5.1 Patch Set 5+ Release Notes |     |
| SunVTS 5.1 Patch Set 5+ Release Notes | |
|
SunVTS 5.1 Patch Set 5+ Release Notes |
SunVTS 5.1 PS5+ packages are intended for UltraSPARC IIIi processor based systems only.
The following issues apply to the SunVTS
5.1 PS5+ product.
The SunVTS 5.1 PS5+ software is compatible with the Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, Solaris 8 2/04, Solaris 9, Solaris 9 9/02, Solaris 9 12/02, Solaris 9 4/03, Solaris 9 8/03, Solaris 9 12/03, and Solaris 9 4/04 operating environments. The following new features and tests are added to the SunVTS 5.1 PS5+ release:
|
Note - The S24 Frame Buffer Test (tcxtest), the Level 2 Cache Test (l2cachetest), and the Cache Consistency Test (mpconstest) will be discontinued in a future release of SunVTS. |
|
Note - The SunPCi |
Refer to the SunVTS 5.1 Patch Set 5 Documentation Supplement for details about the new features and tests offered in this release.
|
Note - The SPARCstorage® Array Controller Test (plntest) is discontinued in Solaris 9 8/03. |
The online help documentation available with the SunVTS 5.1 software includes a chapter describing the RAM test (ramtest). This test is supported only in SunVTS 5.1 Patch Set 4 (PS4) onward.
This section lists corrections to errors in the Supported Test Modes tables of the following test chapters in the SunVTS 5.1 Test Reference Manual:
Compact Disk Test (cdtest)
CPU Test (cputest)
Disk and Floppy Drives Test (disktest)
DVD Test (dvdtest)
ECP 1284 Parallel Port Printer Test (ecpptest)
Sun StorEdge A5x00 Test (enatest)
Functional and Online test modes are supported in SunVTS 5.1.
Sun StorEdge 1000 Enclosure Test (enctest)
Environmental Test (env2test)
Online and Exclusive test modes are not supported in SunVTS 5.1.
Environmental Test (env4test)
Floating Point Unit Test (fputest)
Online and Exclusive test modes are supported in SunVTS 5.1.
Cache Consistency Test (mpconstest)
Multiprocessor Test (mptest)
Qlogic 2202 Board Test (qlctest)
Only Exclusive and Connection test modes are supported in SunVTS 5.1.
Serial Ports Test (sptest)
System Service Processor Test (ssptest)
SunHSI Board Test (sunlink)
System Test (systest)
Tape Drive Test (tapetest)
S24 Frame Buffer Test (tcxtest)
In Appendix A, SunVTS Window and Dialog Box Reference, Table A-11 indicates the incorrect default value of 0 (zero) for the Max Errors field of the example systest Test Parameter Options dialog box in Figure A-11. The correct default value of the Max Errors field of the systest Test Parameter Options dialog box is 1 (one) as indicated in Figure A-11.
Also in Appendix A, Table A-13 indicates the incorrect default value of 0 (zero) for the Max System Errors field of the example systest Threshold Options dialog box in Figure A-13. The correct default value of the Max System Errors field of the systest Threshold Options dialog box is 1 (one) as indicated in Figure A-13.
You might encounter an installation problem when you attempt to install SunVTS with an installation program other than the pkgadd command as described in the following subsections.
If SunVTS 5.1 software is installed in the default /opt directory, you cannot install a subsequent SunVTS 5.1 Patch Set release in a different directory on the same system. When this duplicate installation is attempted with pkgadd, the following error message occurs:
The reason for this error is that the base package revision is the same for both SunVTS 5.1 and any subsequent SunVTS 5.1 Patch Set release. When a SunVTS 5.1 Patch Set release is installed in the default /opt directory which already has SunVTS 5.1 software installed, the installation completes successfully with the following warning message:
This appears to be an attempt to install the same architecture and version of a package which is already installed. This installation will attempt to overwrite this package. |
From SunVTS 5.1, the SunVTS software depends on XML packages that are not included with the Solaris 8 2/02 distribution. For Solaris 9, all of the prerequisite packages are installed with the End User Solaris Software Group as a minimum.
You may install SunVTS 5.1 on Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW
5/03, Solaris 8 HW 7/03, or Solaris 8 2/04. If you choose to install SunVTS 5.1 or later on any of these releases, you must separately install the required XML packages (SUNWlxml[32-bit] and SUNWlxmlx[64-bit]) from either the Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, or Solaris 8 2/04 Software Supplement CD-ROM.
Install the minimum End User Solaris Software Group.
Install the XML packages SUNWlxml(32 bit) and SUNWlxmlx(64 bit) from either the Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, or Solaris 8 2/04 Software Supplement CD-ROM.
|
Note - These XML packages are not available in the Solaris 8 2/02 distribution. |
Install SUNWzlib(32 bit) and SUNWzlibx(64 bit) packages from the Entire Solaris Software Group from either the Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW
5/03, Solaris 8 HW 7/03, or Solaris 8 2/04 Software CD-ROM.
Install the optional SUNWcpc(x)/SUNWcpcu(x) packages only if you want to enable displaying certain performance counters for certain CPU and memory tests. Otherwise, these packages need not be installed.
The SUNWcpc(x)/SUNWcpcu(x) packages are included in the Entire Solaris Software Group for Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, and Solaris 8 2/04. These packages are not included in the End User Solaris Software Group for Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, nor Solaris 8 2/04.
To install SunVTS for Solaris 9 and later releases:
Install the End User Solaris Software Group (or any software group).
The XML packages (SUNWlxml[32-bit] and SUNWlxmlx[64-bit]) and the SUNWzlib packages (SUNWzlib[32 bit] and SUNWzlibx[64 bit]) are part of the End User Solaris Software Group (and Entire Solaris Software Groups) for Solaris 9 releases.
Install the optional SUNWcpc(x)/SUNWcpcu(x) packages only if you want to enable displaying certain performance counters for certain CPU and memory tests. Otherwise, these packages need not be installed.
The SUNWcpc(x)/SUNWcpcu(x) packages are part of the Entire Solaris Software Group and not the End User Solaris Software Group.
Web Start 2.0 may not install SunVTS on systems that do not have the Solaris 64-bit environment installed. Web Start 2.0 removes the SunVTS 32-bit packages when the SunVTS 64-bit packages cause the installation to suspend.
Workaround: Use the pkgadd command to install the 32-bit SunVTS packages as described in the SunVTS 5.1 User's Guide.
When you install SunVTS using Web Start 2.0, you are not prompted to enable the Sun Enterprise Authentication Mechanism (SEAM) Kerberos v5, SunVTS security feature. The installation defaults in a way that installs SunVTS without this high level of security. If you do not want the high-level security, there is no problem.
Workaround: To enable the high-level SEAM security, use the pkgadd command to install SunVTS packages as described in the SunVTS 5.1 User's Guide.
When you attempt to install SunVTS using Web Start 2.0, you are unable to change the directory where SunVTS is installed. SunVTS will be installed in /opt.
Workaround: Use the pkgadd -a none command to install SunVTS in the directory of your choice as described in the SunVTS 5.1 User's Guide.
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 performing the following SunVTS tests on Sun Fire E15K systems with 72 UltraSPARC IV processors (144 CPU IDs), the following issues might occur:
systest - A Bus Error (core dumped) error might occur (Bug ID 4981458)
mptest - The test could hang (Bug ID 4982924)
mpconstest - The test could fail because of too many CPU IDs (Bug ID 4982944)
cmttest - The test times out (Bug ID 4982948)
cmttest - The test fails (Bug ID 4981014)
Workaround: Look for the latest version of Patch ID 116042 at:
When running SunVTS on a system containing three graphics cards with two or more XVR-100 graphics cards, the pfbtest may fail with the error message "X connection broken" displayed on the console.
Workaround: The group concurrency for the Graphics Group must be set to 1. To do so, right-click on the Graphics test field, select "Schedule Options", and set the "Group Concurrency" to 1.
The gfbtest cliptrap test (Screen checksum) could fail with a message similar to the following.
| 09/28/04 15:53:41 ctech232 SunVTS5.1ps5: VTSID 6437 gfbtest.ERROR fbs/gfb0: Clip Trap Test (Screen checksum) error:Error in (R) plane, Total x/col errors = 88, Total y/row errors = 85First x/col checksum error at x = 293, Exp = 0x00027aad, Act = 0x00027aaeFirst y/row checksum error at y = 293, Exp = 0x00029b55, Act = 0x00029b56Probable_Cause(s): <Faulty FBC> <Faulty frame buffer memory.> Recommended_Action(s): <If the problem persists, contact your Sun Service provider.>09/28/04 15:53:41 ctech232 SunVTS5.1ps5: VTSID 7012 vtsk.INFO : *Failed test* gfb0(gfbtest) passes: 0 errors: 1 |
audiotest could fail with an "internal codec error" on Sun Blade 1500 and 2500. The errors could occur when performing functional testing after performing exclusive testing.
Workaround: This issue occurs only if a previous run of cpupmtest is aborted in such a manner that the CPU speed is not fully restored to the full speed. In this case, a system reboot will restore the speed back to the proper value. This is a corner case scenario that will most likely not be encountered in average circumstances.
The qlctest 10-bit/1-bit internal loopback subtests might fail when performed on Sun Fire V880 product line platforms. This problem is fixed in the latest SAN Foundation software.
Workaround: Install the Sun StorEdge SAN Foundation Software 4.2 or later from: http://www.sun.com/storage/san/
sutest might fail immediately.
On Sun Fire 15K systems, adding new boards 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.
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 environments. If this failure occurs, you see an error message similar to the following:
An ecpp/parallel port driver issue might cause ecpptest to fail. The failure rate is three out of 130 machines; the time to fail is about 10 hours.
Sun Blade 100 and 150 systems with SunVTS can produce data corruption errors when the serial port controller (southbridge) is also handling other heavy traffic such as data access from and to the IDE hard disk.
With SunVTS simultaneously running sutest and disktest on Sun Blade 100 and 150 systems, you might see sutest report failures similar to the following:
The difference between the expected (exp) and the observed (obs) values is always 0x10.
The long term technical fix for this problem will involve the installation of a patch or driver to be released in the near future. The root cause of this failure is still under investigation.
Workaround: Do not perform sutest and disktest simultaneously.
If you perform the Sun XVR-4000 Graphics Accelerator Test (zulutest) on a system that was powered on without running X-Windows, you must bring up X-Windows on the Sun XVR-4000 Graphics Accelerator device under test and kill the X-Windows process before performing zulutest. Otherwise, the Convolve subtest might fail, and other subtests might also fail.
|
Note - You must enable multisampling with the fbconfig command before performing the following workaround. To perform zulutest with X-Windows (CDE) the following workaround is not necessary. |
Workaround: To bring up X-Windows on the Sun XVR-4000 Graphics Accelerator device under test, enter the following command:
It takes 30 to 45 seconds before Xsun comes up. To kill the Xsun process, enter the following command:
Once the Xsun process is killed, the zulutest can be performed without the incorrect subtest errors.
The Sun XVR-4000 Graphics Accelerator cannot perform video read back in Interlaced and Stereo modes because the Convolve subtest cannot keep up.
For zulutest to be able to perform the Convolve subtest, multisampling must be enabled.
The console could become corrupted when performing zulutest from a console window if a Stop-A keyboard sequence is entered in the CDE environment.
Workaround: Do not use the Stop-A keyboard sequence when performing zulutest.
The command pkginfo -c sunvts does not produce any output in SunVTS 5.1. This situation correctly implements the -c option of the pkginfo command.
Workaround: 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:
Performing sutest on a port that is being used as console causes sutest to fail.
Workaround: Do not perform sutest on a port that is being used as a console.
Performing m64test for Sun PGX64 in a default console winfow, might cause intermittent failures in a Gnome environment.
Performing afbtest or m64test tests in a Gnome environment might cause intermittent failures.
An error might occur when jnifctest is performed on a system with 5 JNI ports. This error occurs on one card and the error can be seen using the data pattern 0x00000000. The value returned for the fcio_errno statistic is 65 (decimal).
Workaround: Turn off the self-test or perform the test on one port only.
When performing disktest, the test might probe and premount the Solstice DiskSuite (SDS) partitions as mirrors.Workaround: Set the BYPASS_FS_PROBE parameter to 0.
If the /var/opt/SUNWvts/sched_manage directory is not present, schedules cannot be created.
Workaround: Create the /var/opt/SUNWvts/sched_manage directory before creating schedules.
| SunVTS 5.1 Patch Set 5+ Release Notes | 819-1194-11 | |
Copyright © 2004, Sun Microsystems, Inc. All Rights Reserved.