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 9/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 9/04 operating environment. Remove these packages: SICGbdcdr, SICGc3des, SICGcdes, SICGcrc2, SICGcrc4, SICGcsafe, SICGes, SICGkdsup, SICGkeymg, SICGkisup

SunVTS 5.1 Patch Set 6 (PS6) Issues

The following issues apply to the SunVTStrademark 5.1 PS6 product.

New Features and Tests for This Release

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:

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:

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 PS6 are documented in the SunVTS 5.1 Patch Set 6 Documentation Supplement (817-6318-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 6 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.

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.

Possible Runtime Issues

Using netlbtest (Bug ID 5054858)

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.

Using dtlbtest (Bug ID 5056704)

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.

Workaround: None.

The SunVTS User Interface and Kernel Could Core Dump (Bug ID 5056719)

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.

Error and Warning Messages on Sun Fire 280R Internal Disks (Bug ID 5064664)

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:

WARNING c1t0d0
 (/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e0106dca31,0: ): 
"Read link soft errors detected during the test
SunVTS5.1ps5: VTSID 6019 disktest.1.ERROR c1t1d0(/pci@8,
600000/SUNW,qlc@4/fp@0,0/ssd@w500000e01068d881,0: ): "Disk
 Internal Self Test Failed on device /dev/rdsk/c1t1d0s0
"Probable_Cause(s): <Faulty disk> <system error> 
Recommended_Action(s): <Replace the faulty disk.>

Using sptest (Bug ID 5066197)

When performing sptest, the test might not pass or provide error messages for a long time.

Using fwcamtest (Bug ID 5062974)

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.

Using env5test (Bug ID 5066195)

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.

Version Information Missing in Some Verbose Messages (Bug ID 5048886)

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.

Using pfbtest (Bug ID 4938281)

pfbtest could intermittently fail when performed on Sun XVR-100 graphics accelerators in the GNOME desktop environment.

Using sutest (Bug ID 5069490)

The SunVTS user interfaces (vtsui and vtstty) could fail to come up and hang at probe on Netra T1 servers.

Adding Boards With Dynamic Reconfiguration (DR) to Sun Fire 15K Systems (Bug ID 4959606)

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

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.

Using sutest and disktest Simultaneously (Bug ID 4858028)

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.

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

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.

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

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

Sun Remote System Control

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:



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 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 9/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 9/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:


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.


  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.


  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 9/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:

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

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

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 9/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.


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.


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.


  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 9/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.

Patch Obsoleted For Firmware Upgrade (Bug ID 5053382)

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.