Problems With Oracle Solaris And Workarounds - Fujitsu M10 Product Notes

Problems with Oracle Solaris and
Workarounds
This section describes problems with Oracle Solaris and workarounds for each version.
Problems relating to all the versions of Oracle
Solaris and their workarounds
The following table shows problems that might occur in any versions of Oracle
Solaris being supported and workarounds for them.
Table 3-4
Problems that might occur in any versions of Oracle Solaris and their workarounds
SPARC
CR ID M10-1
15813959 x
15813960
(7196117)
15814853
15822113 x
15956174
Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2043 ･ October 2013
40
SPARC SPARC
M10-4 M10-4S Description
x x When a PCI expansion unit is
added by hotplug(1M) in a
SPARC M10 system, devices on
the PCI expansion unit are not
recognized.
x If you try to access, via telnet or
ssh, a domain where 8000 GB
(about 7.8 TB) or greater
memory is mounted, the
following message appears on
the destination control domain
console and the access fails.
For ssh
■
error: /dev/ptmx: Not
enough space
error: session_pty_
req: session 0 alloc
failed
For telnet
■
telnetd: open /dev/
ptmx: Not enough space
x x If ldm add-vcpu and ldm
remove-vcpu are repeatedly
executed in a shell script, the
process that is being run may
cause a core dump and
abnormally terminate.
Workaround
Before you add a PCI
expansion unit by hotplug(1M),
add the following line in the
/etc/system file in advance and
restart Oracle Solaris.
set pcicfg:pcicfg_
slot_busnums = 4
This has been modified with
Solaris 11.1 SRU3.5.1.
[Workaround]
Execute the following
command to change
ptmx_ptymax:
[Example]
# echo "ptms_ptymax/Z
0x400000" | mdb -kw
ptms_ptymax: 0 =
0x400000
In this case, execute the
command again.
In addition, when executing
ldm remove-vcpu, execute it in
such a condition that the
process load is low.