Problems That Might Occur in Any Versions of Oracle Solaris and Workarounds
Problems That Might Occur in Any Versions of Oracle Solaris and Workarounds
The following table lists the problems that might occur in any versions of Oracle Solaris being supported and workarounds for them.
| Bug | 23025823 |
| Model | SPARC M12-2S, SPARC M10-4S |
| Description | The addboard command fails to revert the I/O devices which have been degraded with the deleteboard command. This phenomenon occurs when all of the following conditions are true: - There is/are root domain(s) with two or more root complexes. - The deleteboard command removes root complexes from the root domain(s). - At least one endpoint in one or more of the removed root complexes is either unassigned or assigned to another domain. - The addboard command restores the root complex(es). [Error message example] -------------------------------------------------------------------- XSCF> addboard -v -y -c configure -m bind=resource -p 0 00-0 PSB#00-0 will be configured into PPAR-ID 0. Continue?[y|n] :y Start connecting PSB to PPAR. [3600sec] 0./ (Omitted) Processing of the incoming DR request by the LDoms Manager is pending Incoming DR request is being processed by the LDoms ManagerDR sequence started (sequence#=2, message#=6) ...../ Restoring primary failed, it failed in the allocation of PCIE0 60../ Restoring primary failed, it failed in the allocation of PCIE1 .- Restoring primary failed, it failed in the allocation of PCIE2 ..\ Restoring primary succeeded, PCIE3 was assigned 90| Restoring ioroot failed, it failed in the allocation of PCIE4 ..| Restoring ioroot failed, it failed in the allocation of PCIE5 ./ Restoring primary failed, it failed in the allocation of PCIE6 .\ Restoring primary failed, it failed in the allocation of PCIE7 (Omitted) Restoring primary succeeded, 15 core(s) were assigned .| Restoring guest1 succeeded, 34896609280 byte memory were assigned DR sequence finished (sequence#=2, message#=6) end PSB#00-0 could not be configured into PPAR-ID 0 due to operating system or Logical Domains Manager error. XSCF> -------------------------------------------------------------------- Moreover, once this phenomenon occurs, retrying addboard fails and the ldmd daemon might dump core. |
| Workaround | Execute the addboard command with -m bind=none option and recover the I/O configuration manually. |
| Bug | - |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S, SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When a logical domain with a Dual 10Gigabit Ethernet card (SP1X7HF1F) for which the value of OpenBoot PROM environment variable diag-switch? is set to true, the console displays the following warning message and the error log records "Msg: Device error (FCode informed error)". WARNING: /pci@X,XXXXXX: FCODE mapin doesn't match decoded register type; Also, executing the showstatus(8) command may show "Degraded" for the FRU on which the relevant PCI card is mounted. |
| Workaround | Ignore all these outputs. To prevent these outputs, execute the following command on the ok prompt to change the value of the OpenBoot PROM environment variable diag-switch? to false. setenv diag-switch? false |
| Bug | - |
| Model | SPARC M12-2S, SPARC M10-4S |
| Description | If dynamic reconfiguration is performed on a physical partition which has a dual channel 10Gbps FCoE card (SP1X7FBR2F/SP1X7FBS2F/7101683 (7101684)+7101687 (7101688)) mounted on it, system panic may occur due to the processing of the emlxs driver. |
| Workaround | There is no effective workaround. Use Oracle Solaris 11.2 SRU 11.2.2.8.0 or later and Oracle Solaris 10 1/13 or later. If this specific card is mounted on a system, conduct any reconfiguration in deactivated state instead of dynamic reconfiguration. |
| Bug | - |
| Model | SPARC M12-2S, SPARC M10-4S |
| Description | If dynamic reconfiguration is performed on a physical partition which has a Dual Gigabit Ethernet card (MMF) (SP1X7GD1F/7100482 (7100481)), the connection is terminated. |
| Workaround | There is no effective workaround. If this specific card is mounted on a system, conduct any reconfiguration in deactivated state instead of dynamic reconfiguration. |
| Bug | - |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S, SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When "Oracle VM Server for SPARC 3.1.1.1" is installed on the control domain, messages like the following will be registered to the log file (/var/svc/log/ldoms-ldmd:default.log) of the ldoms/ldmd service. [Example of message] Get Device ID command failed: Unknown (0x7E) ERROR: Cannot connect to BMC |
| Workaround | There is no effective workaround. Ignore this message because there is no impact on system operation. |
| Bug | - |
| Model | SPARC M12-2S, SPARC M10-4S |
| Description | When physical partition dynamic reconfiguration (PPAR DR) is performed to replace a building block in a physical partition containing logical domains with the whole-core constraint and logical domains without the whole-core constraint, the number of CPUs and memory size of the whole-core constrained domains may not be restored correctly. With the ldm list-domain command, you can check whether the whole-core constraint is enabled for a logical domain. In the following example, the whole-core constraint is applied on the logical domain domain-A and not on the logical domain domain-B. primary# ldm list-domain -o resmgmt NAME domain-A CONSTRAINT cpu=whole-core max-cores=unlimited -------------------------------------------------------------------- NAME domain-B CONSTRAINT |
| Workaround | Enable the whole-core constraint for all logical domains in the physical partition, or disable it for all the logical domains. For details on how to set the whole-core constraint, see the Oracle VM Server for SPARC 3.4 Administration Guide. [How to restore] Execute the ldm command to manually restore the resources of the domain. |
| Bug | - |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| Description | When you start the SunVTS 7.0 ps19 tests on a SPARC M12 system, they may terminate with an error. |
| Workaround | There is no effective workaround. |
< Previous Page | Next Page >