Solaris Issues Fixed In Solaris 10 5/09 - Sun Microsystems SPARC Enterprise M3000 Product Notes

Solaris OS Issues and Workarounds for All Supported Releases (3 of 3)
TABLE 3-2
CR ID Description
6679370 The following message may be output on the
console during the system booting, the
External I/O Expansion Unit adding by
hotplug, or the FMEMA operating by DR.
SUNW-MSG-ID: SUN4-8000-75, TYPE:
Fault, VER: 1, SEVERITY: Critical
...
DESC:
A problem was detected in the
PCIExpress
subsystem.
Refer to http://sun.com/msg/SUN4-
8000-75 for more information.
...
6723202 The raidctl command cannot be used to
create a hardware RAID using the onboard
SAS/LSI controller on the M3000 server.
The raidctl command can be used to view
disk/controller status, and can be used on any
PCI Host Bus Adapter (HBA) installed in the
system.
6745410 Boot program ignores the Kadb option which
causes the system not to boot.

Solaris Issues Fixed in Solaris 10 5/09

TABLE 3-3
them in supported releases earlier than Solaris 10 5/09.
Solaris OS Issues and Workarounds Fixed in Solaris 10 5/09 (1 of 2)
TABLE 3-3
CR ID Description
6623226 The Solaris command lockstat(1M) or the
dtrace lockstat provider might cause a system
panic.
6680733 Sun Quad-port Gigabit Ethernet Adapter UTP
(QGC) & Sun Dual 10 GigE Fiber XFP Low
Profile Adapter (XGF) NICs might panic under
high load conditions.
lists issues that have been fixed in Solaris 10 5/09 OS. You might encounter
Workaround
Add the following to /etc/system and then
reboot the domain.
set pcie_expected_ce_mask = 0x2001
No workaround is available.
Use kmdb instead of kadb.
Workaround
Do not use the Solaris lockstat(1M)
command or the dtrace lockstat provider.
Chapter 3 Information About Software 19