TABLE 7 Specific Issues and Workarounds Concerning Solaris (Continued)
CR ID | Description | Workaround |
|
|
|
6539909 Do not use the following I/O cards for network access when you are using the boot net install command to install the Solaris
OS:
•
•
6542632 Memory leak in PCIe module if driver attach fails.
6545143 When kcage daemon is expanding the kcage area, if the user stack exists in the expanded area, its area is demapped and might cause a ptl_1 panic during the flushw handler execution.
6545685 If the following message displayed on the OS console, memory degradation or XSB deconfiguration may occur in the subsequent reboot.
When running Solaris 10 11/06, use an alternate type of network card or onboard network device to install the Solaris OS via the network.
There is no workaround.
This bug has been fixed in Solaris 10 8/07.
There is no workaround. Check for the availability of a patch for this defect.
Add the following to /etc/system and then reboot the domain:
set
Example:
6546188 The system panics when running hotplug (cfgadm(1M)) and DR operations (addboard(8) and deleteboard(8)) on the following cards:
•
•
6551356 The system panics when running hotplug (cfgadm(1M)) to configure a previously unconfigured card. The message "WARNING: PCI Expansion ROM is not accessible" will be seen on the console shortly before the system panic. The following cards are affected by this defect:
•
•
There is no workaround.
For Solaris 10 8/07, check for the patch 127741- 01 for this defect.
For Solaris 10 11/06, check for the patch
Note: See CR ID 6608404 regarding issues with
Perform cfgadm
Check for the patch
26 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1060 • November 2007