Fujitsu M10 Product Notes page 175

Table 3-22 Problems that might occur in any versions of Oracle Solaris and workarounds (continued)
SPARC M10-
Bug 1 4 4S
19074260 x
19310540 x
19310550 x
Description
The following messages may be output
in the log of ldoms/ldmd services
(/var/svc/log/ldoms-ldmd:default.log),
and the communication between ldmd
daemon and XSCF may be disconnected
during or after physical partition
dynamic reconfiguration (PPAR DR).
[Message example]
Sep 18 13:31:37 warning: Device busy:
open_ldc_channel: Open of/devices/
virtual-devices@100/channel-devices@
200/virtual-channel@3:spds failed
After that time, processes which need to
communicate with XSCF such as PPAR
DR or ldm list-spconfig command fail.
If the addboard(8) command is executed
in the "factory-default" configuration,
CPU cores may not be assigned to the
control domain.
On a physical partition, to which 8 or
more system boards have been assigned,
when collecting dump files of the
hypervisor which is executed as the
ldoms/ldmd service is started, the
following console messages is output by
the ldoms/ldmd service and it may fall
back to maintenance mode.
[Example of message]
Feb 28 16:19:39 svc.startd[11]: ldoms/
ldmd:default failed:
transitioned to maintenance (see 'svcs
-xv' for details)
Workaround
There is no effective workaround.
[How to restore]
Execute the svcadm(1M) command to
restart the ldoms/ldmd services.
# svcadm restart ldmd
This has been modified with SRU11.2.8
and Oracle VM Server for SPARC 3.2 for
Oracle Solaris 10.
[How to restore]
Add the CPU cores or threads which
were not added, using the "ldm
add-core" command or the "ldm
add-vcpu" command.
This has been modified with SRU11.2.8
and Oracle VM Server for SPARC 3.2 for
Oracle Solaris 10.
[How to restore]
Use the following process to change the
timeout value of starting the ldoms/ldmd
service to 600.
# svccfg -s ldmd listprop
:
start/timeout_seconds count 180
:
# svccfg -s ldmd setprop start/timeout_
seconds=600
# svccfg -s ldmd listprop
:
start/timeout_seconds count 600
:
# svcadm refresh ldmd
# svcadm restart ldmd
Chapter 3 Information on Software 161