Problems Resolved In Oracle Solaris 11.2 - Fujitsu M10 Product Notes

Table 3-23 Problems that might occur with Oracle Solaris 11 and workarounds (continue d)
SPARC M10-
Bug 1 4 4S
19680186 x
Problems that might occur with Oracle Solaris 10
and workarounds
The following table lists the problems that might occur with Oracle Solaris 10 and
workarounds for them.
Table 3-24 Problems that might occur with Oracle Solaris 10 and workarounds
SPARC M10-
Bug 1 4 4S
15738030 x x x

Problems resolved in Oracle Solaris 11.2

The following table lists the problems resolved in Oracle Solaris 11.2. You might
encounter them in supported releases earlier than Oracle Solaris 11.2.
Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240 ･ March 2015
168
Description
If Oracle Solaris 11.2 and later is running
and the system board is deleted by
dynamic reconfiguration of physical
partitions (PPAR DR), Oracle Solaris may
panic.
Description
If both of the following conditions are
satisfied, a control domain panic may
occur with "BAD TRAP: type=31".
- The operating system of the control
domain is Oracle Solaris 10.
- As a result of executing ldm
list-domain -o memory primary, the
RA (real address) is greater than
0x200000000000 (32 TB).
Workaround
Add the following line to /etc/system and
restart Oracle Solaris:
set lgrp_topo_levels=1
Workaround
This has been modified with the patch
148888-03 for Solaris 10.
Perform the following procedure:
1. Execute ldm list-domain -o memory
primary to display the value of SIZE.
2. Execute ldm start-reconf primary to
enter the delayed reconfiguration mode.
3. Execute ldm remove-memory 256M
primary to reduce the assigned memory.
4. Execute ldm set-memory primary to
return the assigned memory back to the
original size.
5. Restart the Oracle Solaris of the control
domain.
6. Execute ldm list-domains -o memory
primary to confirm that the RA is
smaller than 0x200000000000.
7. Execute ldm add-spconfig to save the
configuration information to the XSCF.