C H A P T E R  3

Open Issues

This chapter discusses:


Application-Specific Issues

SunScreen SKIP 1.1.1 Not Supported in Solaris 9 4/04 Operating Environment

If you have SunScreentrademark SKIP 1.1.1 software currently installed on your system, you should remove the SKIP packages before installing or upgrading to the
Solaris 9 4/04 operating environment. Remove these packages: SICGbdcdr, SICGc3des, SICGcdes, SICGcrc2, SICGcrc4, SICGcsafe, SICGes, SICGkdsup, SICGkeymg, SICGkisup

SunVTS 5.1 Patch Set 5 (PS5) Issues

The following issues apply to the SunVTStrademark 5.1 PS5 product.

New Features and Tests for This Release

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 SunPCitrademark II Test (sunpci2test) tests both the SunPCi II and SunPCi III cards in SunVTS 5.1 PS2.





Note - All new features, tests, and test enhancements that are released in SunVTS 5.1 PS5 are documented in the SunVTS 5.1 Patch Set 5 Documentation Supplement (817-4350-10). This document is included on the Solaris Software Supplement CD and is available at: http://docs.sun.com



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 name of the Remote System Control test (rsctest) has been changed to System Service Processor test (ssptest) in SunVTS 5.1 PS1. The reason for this change is that ssptest tests the Advanced Lights-Out Management (ALOM) hardware in addition to both Remote System Control 1.0 and 2.0 hardware.





Note - The SPARCstorage® Array Controller Test (plntest) is discontinued in Solaris 9 8/03.



Online Help Documentation

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.

SunVTS 5.1 Test Reference Manual Errata

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:

SunVTS 5.1 User's Guide Errata

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.

Possible Installation Issues

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:

pkgadd: ERROR: SUNWvts is already installed at /opt. Cannot create a duplicate installation.

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.

Installation Package Dependency Issue for Solaris 8 (RFE ID 4823716)

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.



Note - The additional XML packages are available on the Solaris 8 HW 12/02 through Solaris 8 2/04 Software Supplement CD-ROMs and not on the Solaris 8 2/02 Software Supplement CD-ROM. Although SunVTS 5.1 installation is supported on Solaris 8 2/02, the XML packages are not included in the Solaris 8 2/02 distribution.



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.



Note - SunVTS 4.6, which is delivered on the Solaris 8 2/02 Software Supplement CD-ROM, does not have the XML packages dependency and is supported on Solaris 8 2/02. SunVTS 5.1 is also supported on Solaris 8 2/02 if the XML packages are installed from the Solaris 8 HW 12/02 through Solaris 8 2/04 Software Supplement CD-ROM.



For Solaris 8 releases:

  1. Install the minimum End User Solaris Software Group.

  2. 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.



  3. 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.



    Note - The XML packages depend on the SUNWzlib(32 bit) and SUNWzlibx(64 bit) packages which are not part of 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, or Solaris 8 2/04.



  4. 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:

  1. 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.

  2. 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.

Installation Issue:
32-bit Only Systems and Web Start 2.0 (Bug ID 4257539)

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.

Installation Issue:
Security and Web Start 2.0 (Bug ID 4362563)

When you install SunVTS using Web Start 2.0, you are not prompted to enable the Sun Enterprise Authentication Mechanismtrademark (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.

Installation Issue:
The Installation Directory With Web Start 2.0 Is Not User-Definable (Bug ID 4243921)

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.

Installation Recommendation:
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.

Workaround: None.

Possible Runtime Issues

Patch for Testing CPUs on Sun Fire E15K Systems

When performing the following SunVTS tests on Sun Fire E15K systems with 72 UltraSPARC IV processors (144 CPU IDs), the following issues might occur:

Workaround: Look for the latest version of Patch ID 116042 at:

http://sunsolve.sun.com

qlctest Internal Loopback Failure (Bug ID 4704300)

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/

Using sutest (Bug ID 4995795)

sutest might fail immediately.

Workaround: None.

Using env3test (Bug ID 5007286)

env3test might fail immediately.

Workaround: None.

Adding Boards to Sun Fire 15K Systems (Bug ID 4959606)

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 Fails When Used in the Gnome Desktop Environment (Bug ID 4938281)

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:

pfb3(pfbtest)            passes: 26 errors: 12

Workaround: None.

Using ecpptest (Bug ID 4482992)

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.



Note - This driver issue exists only in Solaris 8 software.



Workaround: None.

Using sutest and disktest Simultaneously (Bug ID 4858028)

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:

07/11/03 16:35:58 dt214-175 SunVTS5.1ps2: VTSID 6003 sutest.ERROR su0: 
"data miscompare, cnt = 2910, exp = 0x5e, obs = 0x4e, receive device = 
/dev/term/a, source device = /dev/term/a, baud rate = 9600" 
Probable_Cause(s): <system load too heavy for selected baud rate> 
<loopback connection defective> <bad serial port hardware> <system 
software error> Recommended_Actions: <reduce system load> <lower baud 
rate> <check loopback connection> <if the problem persists, contact 
authorized Sun service provider>

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.

Using zulutest (Bug ID 4753578)

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:

/usr/openwin/bin/Xsun -dev /dev/fbs/device_name &

It takes 30 to 45 seconds before Xsun comes up. To kill the Xsun process, enter the following command:

pkill -KILL Xsun

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.

Workaround: None.

Using zulutest (Bug ID 4824491)

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.

Using pkginfo -c sunvts Command

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

# pkginfo -l SUNWvts SUNWvtsx SUNWvtsmn

:

You can also use either of the following commands to receive additional SunVTS 5.1 package information:

# pkginfo | grep vts
# showrev -p | grep vts

Workaround: None.

Using sutest (Bug ID 4750344)

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.

Using m64test in a Gnome Environment (Bug ID 4997460)

Performing m64test for Sun PGX64 in a default console winfow, might cause intermittent failures in a Gnome environment.

Workaround: None.

Using afbtest and m64test in a Gnome Environment (Bug ID 4996537)

Performing afbtest or m64test tests in a Gnome environment might cause intermittent failures.

Workaround: None.

Using jnifctest (Bug ID 4965226)

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.

Using disktest (Bug ID 4915233)

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.

Creating Schedules (Bug ID 4946695)

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.

Sun Remote System Control (RSC) 2.2.2 Release Notes

This section deals with Sun Remote System Control (RSC) 2.2.2 hardware and software issues.

What's New in RSC 2.2.2

Several new features not documented in the Sun Remote System Control (RSC) 2.2 User's Guide are available in RSC 2.2.2:

Before Installing Sun Remote System Control Software

RSC software is included as part of the default installation set for this Solaris release. You should install RSC server components on a compatible Solaris server only; you can install the client software on any computer that meets the Solaris or Windows software requirements. You must install and configure the RSC software before you can use RSC.

You can install the RSC 2.2.2 server software package, SUNWrsc, on:

You can install the RSC 2.2.2 client software package on:

Solaris client computers require Java 2 Standard Edition (SDK 1.4.0 Beta 3) Beta Release for the Solaris operating environment. RSC 2.2.1 software does not run using the J2SE Runtime Environment Version 1.3.1. You can download the appropriate Solaris Java version from the following Web site:

http://www.sun.com/solaris/java

On the Microsoft Windows platforms only, RSC supports the J2SE Runtime Environment version 1.3.1. It is available on the Supplemental CD or from the following Web site:

http://java.sun.com/j2se/1.3/

Before upgrading from a previous version of RSC or reinstalling the software, log in to the server as superuser and back up your configuration data using the following commands:

# rscadm show > remote-filename
# rscadm usershow >> remote-filename

Use a meaningful file name that includes the name of the server that RSC controls. After installation, you can refer to this file to restore your configuration settings.

Installation on the Solaris operating environment places the Sun Remote System Control (RSC) 2.2 User's Guide in the location /opt/rsc/doc/locale/pdf/user_guide.pdf. Installation on the Windows operating environment places the user's guide in the location C:\Program Files\Sun Microsystems\Remote System Control\doc\locale\pdf\user_guide.pdf.

The following sections describe Sun Remote System Control (RSC) 2.2.2 issues.

RSC General Issues

This section describes issues that affect RSC running on all platforms.

Note -

Removing or installing the RSC card while the system has the AC power cord connected could damage your system or your RSC card. Only qualified service personnel should remove or replace the RSC card. Contact your qualified service representative to perform this service operation.

To Remove and Install the RSC Card

Before you follow the procedures in the Sun Fire V480 Server Service Manual, Sun Fire 280R Server Service Manual, or Sun Fire V880 Server Service Manual to remove or install the RSC card, perform this procedure to ensure that there is no AC power present in the system.

1. Shut down and halt the system.

2. With the system at the ok prompt, turn the keyswitch to the Off position.

Standby power is still present in the system at this point.

3. Disconnect all AC power cords from their back panel receptacles.

This ensures that there is no standby power voltage present in the system.

4. Follow the procedure you require in your service manual.

RSC Console Sometimes Exits Unexpectedly (Bug ID 4388506)

The RSC console window sometimes exits when processing large amounts of text data, for instance when executing the ls -R command for a large file structure. This is an intermittent problem.

Workaround: Open another console window.

Locator LED Functions Not Documented in User's Guide (Bug ID 4445848, 4445844)

Sun Fire V480 servers include a new hardware feature, a Locator LED on the system's front panel. RSC client software enables you to toggle the state of this LED to help identify a particular system that might be located in a rack with other servers. The Toggle Locator LED command is available in the graphical user interface under Server Status and Control. The syntax of the command-line interface commands to toggle the LED state for this release are:

/* setlocator [on|off] turns the system locator LED on or off*/
/* showlocator shows the state of the system locator LED*/
rsc> setlocator on
rsc> showlocator
Locator led is ON
rsc> setlocator off
rsc> showlocator
Locator led is OFF

The status of the Locator LED is shown in the GUI display of the server front panel and in the output of the environment (env) and showenvironment commands.

rsc-console Switches to Tip Connection During Boot if diag-switch? Is Set to true (Bug ID 4523025)

If diag-switch? is set to true and you use the bootmode -u command to reboot your system, rsc-console reverts to the serial (Tip) connection after Solaris restarts, even if you have previously redirected the console to RSC.

Workaround: Manually redirect the console output to RSC again after the reboot operation has completed. Refer to the Sun Remote System Control (RSC) 2.2 User's Guide for more information.

Users Can Only Run RSC Client Once on Japanese Version of Microsoft Windows 98

An RSC client installed on the Japanese version of Microsoft Windows 98 does not start again once you exit from the client, unless you reboot the system. The javaw stack error appears. This occurs only on the initial version of Windows 98, and does not happen on the other versions of Windows (95, 98 Second Edition, NT).

Workaround: Download and install Microsoft IME98 Service Release 1 (IME98-SR1) from the Microsoft web site. The crash does not occur after IME98-SR1 has been installed.

RSC Issues for Sun Fire 280R and Sun Fire V880 Servers

This section describes issues that affect RSC running on Sun Fire 280R and Sun Fire V880 servers.

Additional RSC Alert

RSC generates the following alert on a Sun Fire 280R or Sun Fire V880 server when the RSC card begins battery use after a power interruption:

00060012: "RSC operating on battery power."

This alert is not documented in the Sun Remote System Control (RSC) 2.2 User's Guide.

RSC Issues for Sun Fire 280R Servers Only

This section describes issues that affect RSC running on Sun Fire 280R servers only. See the Sun Fire 280R Server Product Notes for other Sun Fire 280R server issues.

Boot Sequence Sometimes Bypasses RSC

In rare instances, the system might bypass the RSC card during startup.

Workaround: To check whether the system booted and is online, use the ping command to see if the card is alive, or log in using telnet or rlogin. If the system is not connected to the network, establish a Tip connection to the system. (Be sure that console I/O is not directed to the RSC card.) Use the Tip connection to view boot messages on the troubled system, or reboot the system. For help in diagnosing the problem, see your hardware owner's guide.

False Drive Fault Reported at Power On

When you power on the system, it might report a false internal drive fault that is recorded in the Sun Remote System Control (RSC) log history.

Workaround: Disregard the error reported by RSC if the system boots successfully to the Solaris operating environment. In most cases the erroneous fault does not reappear. You can verify the disk after the boot process by using the fsck utility.



Note - Any disk drive error message reported by the Solaris operating environment is a real disk drive error.



If a disk fault is reported at the ok prompt and the system fails to boot to the Solaris operating environment, there might be a problem with the disk drive. Test the disk drive with the OpenBoot Diagnostics tests documented in the "Diagnostics, Monitoring, and Troubleshooting" chapter in the Sun Fire 280R Server Service Manual.

RSC Command rscadm resetrsc Fails (Bug ID 4374090)

After a cold restart or after powering on the system, the RSC command rscadm resetrsc fails; this is a known condition. You need to reset the host system for the command to function correctly.

Workaround: Reset the host using one of the following commands:

The RSC rscadm resetrsc command now functions correctly.

RSC Issues for Sun Enterprise 250 Servers Only

This section describes issues that affect RSC running on Sun Enterprise 250trademark servers only. See the Sun Enterprise 250 Server Product Notes for other Sun Enterprise 250 server issues.

Do Not Run OpenBoot PROM fsck Command From the RSC Console

Do not issue the fsck command from the redirected RSC console.

Workaround: Reset the system's input-device and output-device settings to ttya. Then reboot the system and access the system through its local console or terminal and execute the OpenBoot PROM fsck command directly.

Do Not Run OpenBoot PROM boot -s Command From the RSC Console

The command boot -s does not work from the RSC console.

Workaround: Reset the system's input-device and output-device settings to ttya. Then reboot the system, access the system through its local console or terminal, and execute the boot -s command directly.

Changing the serial_hw_handshake Variable Requires a System Reboot

In order for changes to the RSC configuration variable serial_hw_handshake to take effect, the server must be rebooted. This also affects the Enable Hardware Handshaking check box in the RSC graphical user interface. This limitation is not stated in the documentation.

SunForum

SunForumtrademark 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 (WBEM-Based Dynamic Reconfiguration)

Open Bugs

Logging Supports Syslog local0 Facility Only (Bug ID 4643706)

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.

Workaround: None.

mcfgconfig Ignores Value -1 and Uses the Entry in the Sun Management Center config File (Bug ID 4700686)

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.

getInstance Shows Wrong Value for Referenced Property of Solaris_CHController (Bug ID 4635499)

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.

Solaris_VMConcatComponent Erroneously Throws Exception in References/Names Calls (BugID 4712814)

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.

Problem with Postinstall Script of SUNWWDRcfg with Live Upgrade (BugID 4753154)

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.

ID Field of Solaris_SGDomain Populated Inconsistently in Different MSP (BugID 4947446)

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 Does Not Work With SMS1.4 (BugID 4933314)

WDR is not compatable with SMS 1.4 and might cause problems that appear as memory corruption, resulting in WEBM hanging or crashing.

OpenGL

OpenGL Package SUNWgldoc Contains Broken Links (BugID 4706491)

Some content from the documentation package for the OpenGL software installs incorrectly.

Workaround: Fix the affected link by typing the following:

# cd /usr/openwin/share/man/man3gl
# mv gltexfilterfuncSGIS.3gl gltexfilterfuncsgis.3gl


Platform-Specific Issues

Upgrade Firmware on Sun Fire and Netra Servers Before Installation (BugID 4747307, 4799331)

To install the Solaris 9 4/04 operating environment on specific Sun Fire and Netratrademark servers, you must first update the firmware on the server. If you do not update the firmware before you install the Solaris 9 4/04 software, the server panics. This problem affects the following servers:

If this problem occurs, the following error message is displayed:

panic[cpu0]/thread=140a000: BAD TRAP: type=34 rp=147e9e0
addr=5586ee326973add3 mmu_fsr=0

The ok prompt 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:

http://sunsolve.sun.com

Be sure to download and apply the most current version of the patch.

Netra Servers

Error Message Appears for Netra X1 in Solaris 9 (BugID 4663358)

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:

WARNING: ds1287_attach: Failed to add interrupt.

Workaround:

  1. 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.

  2. Install patch 111092-02 or later (this is a prerequisite to Step 4). Do not reboot the system between Steps 3 and 4.

  3. Install patch 111952-02 or later.

    This installs OpenBoot PROM version 4.0.9 or later.

This problem only applies to Netra X1 systems, not to Sun Fire V100 systems.

Sun StorEdge Systems

LUN Missing After Changing Target ID (Bug ID 4399108)

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.

Incorrect Parameters Might Cause Panic in Sun StorEdge T3 (Bug ID 4319812)

A Sun StorEdge T3 system might panic if an application uses the HTTP interface to send tokens with out-of-range parameters.

I/O Timeout Incorrectly Detected (Bug ID 4490002)

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.

Sun Fire Systems

RCM Might Fail After Repeated Hot Plug Stress (Bug ID 4474058)

Under repeated stress using PCI hotplug, RCM fails with error code 7 on a Sun Fire V880 system.

XVR-4000 Might Not Be Recognized After Solaris Installation (BugID 4842377)

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.

Workaround:

  1. Begin your Solaris installation using either a ttya or PCI-based graphics card with the console.

  2. Install Solaris as usual.

  3. Perform a power cycle.

    The XVR-4000 should be recognized now as the new default screen.

Sun Fire V880 Shows Warning After Reboot (Bug ID 4717004)

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 4/04 still attempts to load these drivers, causing the following messages to appear during boot:

WARNING: Failed to install "bbc" driver.
WARNING: Failed to install "gptwo" driver.

Workaround: These messages are benign and can safely be ignored.

Sun Fire V250 Installation

The SUNWCXall software metacluster must be installed on a Sun Fire V250.

Sun Fire 6800 Might Crash When Running trapstat (BugIDs 4978865 and 4979012)

Running the trapstat command on a Sun Fire 6800 might result in a crash and error messages naming fatal conditions.

psrinfo -p Might Not Display All CPUs (BugID 4983696)

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.

Sun Fire 15K/12K Systems

Updated Flash Image for Sun Fire 15K/12K Systems Running SMS 1.2 (BugID 4728549)

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:

% flashupdate -d X -f /opt/SUNWSMS/hostobjs/sgcpu.flash -n

Where X is the letter (A-R) of the domain.

To find out whether the patch already exists on your system, type:

% showrev -p | grep 112829

If Patch 112829-05 is not installed, no data is returned. If this is true:

  1. Apply patch 112829-05 to both System Controllers according to the instructions in the patch README file.

    Note special installation instructions.

  2. Use the flashupdate command to update the LPOST image on CPU/MCPU boards.

    Refer to the flashupdate man page for specific command syntax.

SMS Error on Sun Fire 15K/12K (BugID 4979315)

On Sun Fire 15K/12K systems, SMS might return the unum string with an incorrect value. The string is in the form:

SBw/Px/Ey Jz

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.

Sun Blade Systems

System Panics When Xsun Dies With UPA Bus Off (Bug ID 4772013)

This bug affects Sun Bladetrademark 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:

device-thresholds     /upa@8,480000   always-on


Other Issues

Doc Errata: Solaris 9 4/04 Sun Hardware Platform Guide

Despite being listed in the Hardware Platform Guide, this release does not support the Sun Fire E7900 platform.

Network Drivers Installed by Default

The Solaris Installation CD automatically installs the network drivers from the Supplement CD. Drivers for the SunATMtrademark and SunHSI/Ptrademark cards are now installed by default when the Solaris 9 4/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.

Serial Parallel Controller Driver Does Not Support Dynamic Reconfiguration (Bug ID 4177805)

This spc driver does not support Dynamic Reconfiguration features in the Solaris 9 4/04 operating environment.

PGX32 DGA Pixmap With Java SwingSet2 Crashes X Server (Bug ID 4420220)

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.

Workaround:

picld Restarts Without Dumping Core (Bug ID 4459152)

After some errors, picld restarts itself without dumping core.

spec_open Failure Causes Point Mount Failure (Bug ID 4431109)

A failure in spec_open causes mount failure of points referenced in the vfstab entry.

Workaround: Type the following command:

# cat S55initfc
devfsadm -i ssd

This loads the ssd driver and attaches all device instances.

Last Connection to Subsystem Might Detach (Bug ID 4432827)

A dynamic reconfiguration operation on the last connection to a multipathed device can be detached without warning.

Pulled Cable on Dual-Channel FC PCI Card Is Undetected (Bug ID 4438711)

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

Pulled Cable on A5x00 Leaves System Board Undetachable (Bug ID 4452438)

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.

qlc Power Management Causes Kernel Panic (Bug ID 4446420)

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_enable_pm = 0

Devices Might Not Appear After Boot (Bug ID 4456545)

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.

System Might Loop When Master CPU Is Changed (Bug ID 4405263)

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.

Workaround:

Untagged Devices Incorrectly Supported (Bug ID 4460668)

The Sun StorEdge network foundation software driver does not honor untagged commands, and allows overlapped untagged commands.

Some DVD and CD-ROM Drives Fail to Boot Solaris (Bug ID 4397457)

The default timeout value for the SCSI portion of the SunSwifttrademark 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).

MPxIO Driver Causes Domain Panic During DR (Bug ID 4467730)

When MPxIO is enabled during a Dynamic Reconfiguration operation, the qlc driver might suspend and cause a domain panic.

scsi Times Out on cPCI and Dual-Channel FC PCI Cards (Bug ID 4424628)

cPCI and dual-channel FC PCI cards might encounter a SCSI timeout or "giving up" error message due to a firmware problem.

ATM LANE Subnets for IPv4/IPv6 Might Not Complete Initialization (Bug ID 4625849)

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.

Workaround:

  1. Verify the problem by issuing a lanestat -a command.

    Instances that are not connected have VCI values of 0 to the LES and BUS.

  2. Stop and restart your SunATM network by typing:

    # /etc/init.d/sunatm stop
    
    # /etc/init.d/sunatm start
    

  3. Reset netmasks or any other network setup for the SunATM interfaces.

    This process only reinitializes your SunATM network.

Installation Might Fail on Drives Above 96 Gbytes (BugID 4724529)

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 4/04 Software 1 of 2 CD.

probe-scsi-all OBP Command Must Be Followed by reset-all (BugID 4589231)

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.