| Asset ID: |
1-72-1531443.1 |
| Update Date: | 2017-10-18 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1531443.1
:
All memory DIMMS have disabled status in prtdiag output
| Related Items |
- Sun Netra 1280 Server
- Sun Fire 3800 Server
- Sun Fire E2900 Server
- Solaris Operating System
- Sun Fire 4810 Server
- Sun Fire V1280 Server
- Sun Fire 4800 Server
- Sun Fire E4900 Server
- Sun Fire E6900 Server
|
| Related Categories |
- PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-x8x0/Ex900
|
In this Document
Created from <SR 3-4991826128>
Applies to:
Solaris SPARC Operating System - Version 10 10/09 U8 and later
Sun Fire V1280 Server - Version All Versions and later
Sun Fire E6900 Server - Version All Versions and later
Sun Fire 4810 Server - Version All Versions and later
Sun Netra 1280 Server - Version All Versions and later
Oracle Solaris on SPARC (64-bit)
Symptoms
All DIMMs are have a status of disabled in Fru Operational Status in prtdiag
============================== FRU Operational Status ==============================
-------------------------
Fru Operational Status:
-------------------------
Location Status
-------------------------
PS0 okay
PS1 okay
PS2 okay
PS3 okay
FT0 okay
FT0/FAN3 okay
FT0/FAN0 okay
FT0/FAN1 okay
FT0/FAN2 okay
FT0/FAN4 okay
FT0/FAN5 okay
FT0/FAN6 okay
FT0/FAN7 okay
RP0 okay
RP2 okay
SB4 okay
SB4/P0 okay
SB4/P0/B0/D0 disabled
SB4/P0/B0/D1 disabled
SB4/P0/B0/D2 disabled
SB4/P0/B0/D3 disabled
SB4/P0/B1/D0 disabled
SB4/P0/B1/D1 disabled
SB4/P0/B1/D2 disabled
SB4/P0/B1/D3 disabled
SB4/P1 okay
SB4/P1/B0/D0 disabled
SB4/P1/B0/D1 disabled
SB4/P1/B0/D2 disabled
SB4/P1/B0/D3 disabled
SB4/P1/B1/D0 disabled
SB4/P1/B1/D1 disabled
SB4/P1/B1/D2 disabled
SB4/P1/B1/D3 disabled
SB4/P2 okay
SB4/P2/B0/D0 disabled
SB4/P2/B0/D1 disabled
SB4/P2/B0/D2 disabled
SB4/P2/B0/D3 disabled
SB4/P2/B1/D0 disabled
SB4/P2/B1/D1 disabled
SB4/P2/B1/D2 disabled
SB4/P2/B1/D3 disabled
SB4/P3 okay
SB4/P3/B0/D0 disabled
SB4/P3/B0/D1 disabled
SB4/P3/B0/D2 disabled
SB4/P3/B0/D3 disabled
SB4/P3/B1/D0 disabled
SB4/P3/B1/D1 disabled
SB4/P3/B1/D2 disabled
SB4/P3/B1/D3 disabled
IB6 okay
IB6/FAN0 okay
IB6/FAN1 okay
Also getting errors in messages file.
# grep picl /var/adm/messages*
messages:Nov 22 03:01:32 hostname picld[3433]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
messages:Nov 22 03:20:25 hostname picld[7812]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
messages:Nov 22 03:31:19 hostname picld[9654]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
messages:Nov 22 03:32:11 hostname picld[9794]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
messages:Nov 22 03:49:54 hostname picld[12768]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
messages:Nov 22 03:50:08 hostname picld[12841]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
messages:Nov 22 04:04:58 hostname picld[16172]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
messages:Nov 22 04:05:03 hostname picld[16244]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
messages:Nov 22 04:05:53 hostname picld[16474]: [ID 537930 daemon.error] SUNW_piclmemcfg init mc failed!
Cause
The memory controller device links are incorrect on the host
When checking the /dev/mc directory this was either a symbolic link or the directory is empty
# ls -ld /dev/mc
lrwxrwxrwx 1 root root 52 Nov 8 21:05 mc -> ../devices/ssm@0,0/memory-controller@0,400000:mc-us3
or:
# ls -l /dev/mc
total 0
however, /dev/mc should be a directory containing a device link for each memory controller.
From LAB System
============
# ls -l /dev/mc
total 16
lrwxrwxrwx 1 root root 55 Dec 1 16:09 mc0 -> ../../devices/ssm@0,0/memory-controller@0,400000:mc-us3
lrwxrwxrwx 1 root root 55 Dec 1 16:09 mc1 -> ../../devices/ssm@0,0/memory-controller@1,400000:mc-us3
lrwxrwxrwx 1 root root 55 Dec 1 16:09 mc2 -> ../../devices/ssm@0,0/memory-controller@2,400000:mc-us3
lrwxrwxrwx 1 root root 55 Dec 1 16:09 mc3 -> ../../devices/ssm@0,0/memory-controller@3,400000:mc-us3
lrwxrwxrwx 1 root root 55 Dec 1 16:09 mc4 -> ../../devices/ssm@0,0/memory-controller@8,400000:mc-us3
lrwxrwxrwx 1 root root 55 Dec 1 16:09 mc5 -> ../../devices/ssm@0,0/memory-controller@9,400000:mc-us3
lrwxrwxrwx 1 root root 55 Dec 1 16:09 mc6 -> ../../devices/ssm@0,0/memory-controller@a,400000:mc-us3
lrwxrwxrwx 1 root root 55 Dec 1 16:09 mc7 -> ../../devices/ssm@0,0/memory-controller@b,400000:mc-us3
Solution
The fix for the problem is as follows.. No outage or reboot required.
**** If the /dev/mc is a symbolic link
bash-3.00# rm /dev/mc
bash-3.00# devfsadm -Cv -i mc-us3
bash-3.00# svcadm disable picl
bash-3.00# svcadm enable picl
wait one minute before verifying problem is fixed in prtdiag.
bash-3.00# prtdiag -v
**** If the /dev/mc directory is empty
bash-3.00# devfsadm -Cv -i mc-us3
bash-3.00# svcadm disable picl
bash-3.00# svcadm enable picl
wait one minute before verifying problem is fixed in prtdiag.
bash-3.00# prtdiag -v
Attachments
This solution has no attachment
