| Solaris 9 9/04 Release Notes Supplement for Sun Hardware |    
|
| Solaris 9 9/04 Release Notes Supplement for Sun Hardware |
|
| C H A P T E R 3 |
|
Open Issues |
This chapter discusses:
If you have SunScreen
SKIP 1.1.1 software currently installed on your system, you should remove the SKIP packages before installing or upgrading to the
Solaris 9 9/04 operating environment. Remove these packages: SICGbdcdr, SICGc3des, SICGcdes, SICGcrc2, SICGcrc4, SICGcsafe, SICGes, SICGkdsup, SICGkeymg, SICGkisup
The following issues apply to the SunVTS 5.1 PS6 product.
The SunVTS 5.1 PS6 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, Solaris 9 4/04, and Solaris 9 9/04 operating systems. The following new features and tests are added to the SunVTS 5.1 PS6 release:
CD DVD Read Write Test (cddvdrwtest) - Tests write read and other supporting functions of CD and DVD RW drives.
Netra-CT 820 DMC Test (dmctest) - Verifies major components in the distributed management controller (DMC) board.
Netra-CT 820 IPMI Test (nipmitest) - Exercises and verifies the basic operation of the IPMI bus and communications between the CP2300 board to the DMC board.
Netra-CT 440 and Netra-CT 240 Alarm Test (nalmtest) - Verifies alarm LEDs,RELAYs, and FRU devices of the Netra-CT 440 and Netra-CT 240 systems. nalmtest replaces the n240atest that tests Netra-CT 240 system. However, the n240atest command-line interfaces are still supported in this test for backward compatibility.
In a future release of SunVTS, some of the existing SunVTS diagnostics might be consolidated into a single test binary. The existing test binaries for such consolidated tests will be removed and a new consolidated binary will be delivered. The likely candidates for consolidation include the following:Optical media tests: cdtest, dvdtest, cddvdrwtest
USB port tests: usbaudiotest, usbkbtest, usbppptest
Serial port tests: sptest, sutest
Parallel port tests: bpptest, ecpptest
The following tests will be discontinued in the next major release of SunVTS:
Advanced Frame Buffer Test (afbtest)
Alarm Card Test for Netra CT Systems (alarm2test)
Alarm Card Test (alarmtest)
Color Graphics Frame Buffer Test (cg14test)
Frame Buffer, GX, GXplus, and TurboGX Options Test (cg6test)
Sun StorEdge A5x00 Test (enatest)
Sun StorEdge 1000 Enclosure Test (enctest)
Environmental Test (env4test)
Frame Buffer Test (fbtest)
Fast Frame Buffer Test (ffbtest)
Graphics Frame Buffer Test (gfbtest)
PGX32 Frame Buffer Test (gfxtest)
Sun Enterprise Cluster 2.0 Network Hardware Test (scitest)
Environmental Sensing Card Test (sentest)
Soc+ Host Adapter Card Test (socaltest)
Sun Fire Link Interconnect Test (wrsmtest)
Sun XVR-4000 Graphics Accelerator Test (zulutest)
|
Note - The SunPCi |
Refer to the SunVTS 5.1 Patch Set 6 Documentation Supplement for details about the new features and tests offered in this release.
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 SunVTS is stopped, netlbtest might not exit properly when it is running in external loopback mode on a Gigabit Ethernet network interface.Workaround: Deselect netlbtest from SunVTS GUI and kill the netlbtest process manually.
On platforms with low memory, sometimes the dtlbtest fails with an error: "shmat: Invalid argument." This error is due to resource constraints within the tested system and it does not indicates faulty hardware.
The Trace Test of a test module in Connection test mode could cause the SunVTS user interface (vtsui) and kernel (vtsk) to core dump. This problem appears when empty newlines are processed in the trace output. A NULL pointer is passed for broadcast messages in such situations.
Incorrect error and warning messages might be reported on internal Sun Fire 280R disks. These messages do not warrant hardware swaps. These messages look similar to the following:
When performing sptest, the test might not pass or provide error messages for a long time.
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.
In rare occasions, env5test might hang when SunVTS is stopping. This causes SunVTS to not exit properly.Workaround: There are two workarounds for this problem: 1.) From the SunVTS GUI, deselect the test by unchecking the box next to the test entry. 2.) Choose a fixed number of passes for env5test to run.
When a test is made to run from the SunVTS GUI with verbose mode enabled, some of the verbose messages might not print the SunVTS version information.
pfbtest could intermittently fail when performed on Sun XVR-100 graphics accelerators in the GNOME desktop environment.
The SunVTS user interfaces (vtsui and vtstty) could fail to come up and hang at probe on Netra T1 servers.
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 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 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 sutest and disktest on Sun Blade 100 and 150 systems, you might see sutest report failures.
Workaround: Do not perform sutest and disktest simultaneously.
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.
This information on Sun Remote System Control (RSC) 2.2.2 hardware and software issues can be found in the RSC 2.2.2 Release Notes at:
SunForum video cannot be used in an environment that supports only 8 bits per pixel. In particular, video does not work when used on PGX8, PGX24, and PGX64 in defdepth 8 mode.
WDR cannot be configured to use a user-defined syslog facility, and is hard-coded to use syslog local0. When any program logs messages to the local0 syslog facility on the Sun Fire midrange midframe service processor, its messages appear in the WDR log.
When you use mcfgconfig to reconfigure WDR and change a domain configuration, you should be able to use the value -1 to indicate that there is no specified value. If a Sun Management Center configuration file exists, then the mcfgconfig utility ignores the -1 value, and uses the value that appears in the corresponding field in the Sun Management Center configuration file. If a Sun Management Center configuration file does not exist, then using a -1 value in the mcfgconfig utility has the desired effect.
Workaround: If Sun Management Center is installed and you want to change the configuration, make any configuration changes first in the Sun Management Center configuration file and then in the mcfgconfig utility.
On Sun Fire 6800/4810/4800/3800 systems, the getInstance() method sometimes displays the value of the Solaris_CHController class Referenced property incorrectly.
Workaround: Use the enumerateInstance() method instead to check the Solaris_CHController class Referenced property.
A client program that calls CIMClient's referenceNames() or references() with resultClass set to null causes an RMIERROR exception to be thrown.
Workaround: When calling referenceNames() or references(), make sure resultClass is set to a non-null value.
During a live upgrade, the postinstall script of the SUNWWDRcfg package attempts to add an entry into /var/spool/cron/crontabs/root instead of to the correct /a/var/spool/cron/crontabs/root.
CIMOM might improperly interpret the ID field of Solaris_SGDomain as a string instead of an integer on some MSP systems. The value returned is a quote-enclosed integer string instead of an int32.
Workaround: Modify the client to handle a returned string instead of an integer.
WDR is not compatable with SMS 1.4 and might cause problems that appear as memory corruption, resulting in WEBM hanging or crashing.
Some content from the documentation package for the OpenGL software installs incorrectly.
Workaround: Fix the affected link by typing the following:
To install the Solaris 9 9/04 operating environment on specific Sun Fire and Netra servers, you must first update the firmware on the server. If you do not update the firmware before you install the Solaris 9 9/04 software, the server panics. This problem affects the following servers:
If this problem occurs, the following error message is displayed:
Workaround: Update the firmware by applying the appropriate firmware patch.
For Sun Fire 3800, 4800, 4810 or 6800 servers, apply one of the following patches:
For Sun Fire V1280 or Netra 1280 servers, apply Patch ID 113751-03 (5.13.0013 firmware update).
Firmware update patches are available at:
Be sure to download and apply the most current version of the patch.
Some X1 systems require a PROM patch from Solaris 8 before running Solaris 9. When booting a Netra X1 in Solaris 9, the following error message might appear:
Check the system's PROM version.
If you have OpenBoot PROM version 4.0.9 or later, no action is needed.
If the OpenBoot PROM version is earlier than 4.0.9, boot the X1 system in Solaris 8.
Install patch 111092-02 or later (this is a prerequisite to Step 4). Do not reboot the system between Steps 3 and 4.
Install patch 111952-02 or later.
This problem only applies to Netra X1 systems, not to Sun Fire V100 systems.
Changing a target ID on a running Sun StorEdge T3 results in a missing LUN.
Workaround: Issue a LIP again using the vol unmount and vol mount commands. The host now sees the device.
A Sun StorEdge T3 system might panic if an application uses the HTTP interface to send tokens with out-of-range parameters.
When some utilities send IP packets to the network interface on a Sun StorEdge T3, the T3 might hang without its ssd/sf layer detecting I/O timeout correctly.
Workaround: Upgrade to 1.17a Sun StorEdge T3 firmware.
Under repeated stress using PCI hotplug, RCM fails with error code 7 on a Sun Fire V880 system.
A Sun Fire V880 might not automatically recognize the XVR-4000 graphics accelerator after a first-time fresh Solaris installation, resulting in a blank screen on monitors connected to the XVR-4000. This problem can also occur when re-installing a version of Solaris that does support the XVR-4000 (Solaris 9 4/03 or later, or other Solaris versions supported by a special installation DVD included with the XVR-4000), replacing a version of Solaris that does not support the XVR-4000.
Begin your Solaris installation using either a ttya or PCI-based graphics card with the console.
Install Solaris as usual.
Perform a power cycle.
The XVR-4000 should be recognized now as the new default screen.
The fix for Bug ID 4717004 removed the bbc and gptwo drivers. Even though these drivers have been deleted, the V880 software delivered with Solaris 9 9/04 still attempts to load these drivers, causing the following messages to appear during boot:
Workaround: These messages are benign and can safely be ignored.
The SUNWCXall software metacluster must be installed on a Sun Fire V250.
Running the trapstat command on a Sun Fire 6800 might result in a crash and error messages naming fatal conditions.
On a Sun Fire 4800 system, the command psrinfo -p might not return the correct number of CPUs. The command psrinfo -sp causes a segmentation fault. This problem might be masked if an UltraSPARC IV board is part of the system.
Workaround: use the command options psrinfo and psrinfo -s instead.
For domains containing CPU/MCPU boards flashed at LPOST level 5.13.3 or lower, an LPOST error might cause a failure to boot Solaris and/or cause a system to hang.Workaround: SMS 1.2 patch 112829-05 (or higher) contains an updated LPOST flash image. This patch is available at:
http://sunsolve.sun.com
This bug is fixed in SMS 1.3. Upgrading to SMS 1.2 or later, from previous versions, is recommended.To find out the LPOST level flashed on your system's CPU/MCPU boards, type:
Where X is the letter (A-R) of the domain.
To find out whether the patch already exists on your system, type:
If Patch 112829-05 is not installed, no data is returned. If this is true:
Apply patch 112829-05 to both System Controllers according to the instructions in the patch README file.
Use the flashupdate command to update the LPOST image on CPU/MCPU boards.
Refer to the flashupdate man page for specific command syntax.
On Sun Fire 15K/12K systems, SMS might return the unum string with an incorrect value. The string is in the form:
Where w is 0 - 17, x is 0 - 3, y is 0 - 1, and z is from one to four digits long. (All ranges are inclusive.) This bug might cause the P# number to be 0 - 7 instead of 0 - 3.
Workaround: If the P# is a value between 4 and 7, subtract 4 to get the correct value.
This bug affects Sun Blade 1000 or 2000 systems that have the XVR-1000 graphics accelerator installed. If Xsun dies or exits while the graphics bus is power managed, the system panics.
Workaround: Add the following line to the system's /etc/power.conf file:
The Solaris Installation CD automatically installs the network drivers from the Supplement CD. Drivers for the SunATM and SunHSI/P cards are now installed by default when the Solaris 9 9/04 operating environment is installed. Error messages might be displayed if you do not have some of the corresponding hardware installed. You can ignore these error messages.
This spc driver does not support Dynamic Reconfiguration features in the Solaris 9 9/04 operating environment.
Java SwingSet2, when used on a system with a PGX32 frame buffer, displays garbled images and crashes the X server. The X server is restarted after the user logs in.
Stop using the offscreen-cached pixmap by typing the command:
Stop using DGA for accessing pixmaps by typing the command:
After the setenv command, exit the CDE or OpenWindows interface and restart the X server.
After some errors, picld restarts itself without dumping core.
A failure in spec_open causes mount failure of points referenced in the vfstab entry.
Workaround: Type the following command:
This loads the ssd driver and attaches all device instances.
A dynamic reconfiguration operation on the last connection to a multipathed device can be detached without warning.
The device driver does not detect when the cable is disconnected from the port and pulled away from the connector edge of the dual-channel FC PCI card.
Workaround: Install Patch 111097-08 or later. Further information about this patch is available at the SunSolve web site at: http://sunsolve.sun.com
Pulling the fibre cable going to controller A0 on an A5000 causes any subsequent DR operation for detaching the system board to fail. Reconnecting the fibre cable does not enable a successful DR detach operation.
Power management of qlc causes the kernel to panic on an ASSERTION failure in the qlc driver code.
Workaround: Set the following in /etc/system to avoid the assertion:
qlc might remain offline, preventing devices appearing after boot.
Workaround: Generate a LIP on the link to get the port in an Online state. You can generate LIP on the HBA port by running the command luxadm -e forcelip.
A system using the kadb command to debug a live system can go into a repeating loop of incomplete error messages when the OpenBoot PROM's master CPU is changed. While a reset will restore the system to operation, the traces of the original failure are lost, resulting in an inability to perform the attempted diagnosis of a fatal reset.
Upgrade to the latest version of OpenBoot PROM.
Before switching, raise pil to f with the following command:
The Sun StorEdge network foundation software driver does not honor untagged commands, and allows overlapped untagged commands.
The default timeout value for the SCSI portion of the SunSwift PCI Ethernet/SCSI host adapter (X1032A) card does not meet the timeout requirements of Sun's SCSI DVD-ROM drive (X6168A). With marginal media, the DVD-ROM occasionally experiences timeout errors. The only exceptions are Sun Fire 6800, 4810, 4800, and 3800 systems, which overwrite the SCSI timeout value by means of OpenBoot PROM.
Workaround for other platforms: Use the on-board SCSI interfaces or DVD-ROM compatible SCSI adapters, such as X1018A (SBus: F501-2739-xx) or X6540A (PCI: F375-0005-xx).
When MPxIO is enabled during a Dynamic Reconfiguration operation, the qlc driver might suspend and cause a domain panic.
cPCI and dual-channel FC PCI cards might encounter a SCSI timeout or "giving up" error message due to a firmware problem.
On boot, multiple instances might not connect to their LANE instance if more than eight LANE instances are on a single adapter. This bug does not appear at multiuser level.
Verify the problem by issuing a lanestat -a command.
Instances that are not connected have VCI values of 0 to the LES and BUS.
Stop and restart your SunATM network by typing:
Reset netmasks or any other network setup for the SunATM interfaces.
Installation of the Solaris operating environment on drives with 96 GBytes or more might fail using some installation methods.
Workaround: Begin Solaris installation using the Solaris 9 9/04 Software 1 of 2 CD.
The OpenBoot PROM command probe-scsi or probe-scsi-all must be followed by the reset-all command on sun4u systems before booting. Otherwise, a subsequent boot or boot -v might hang.
The package SUNWfcbpl has been removed from the Supplement CD for this Solaris release to prevent installation problems on some systems. This package is no longer needed to upgrade Fibre Channel backplane firmware. Download Patch 117814 if an upgrade of Fibre Channel backplane firmware to version 922A or later is needed.
| Solaris 9 9/04 Release Notes Supplement for Sun Hardware | 817-6356-10 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.