T4-2 - Memory DIMM issue - ldom config resets to factory-default Post: 303015482

Sponsored Content

Operating Systems Solaris T4-2 - Memory DIMM issue - ldom config resets to factory-default Post 303015482 by jim mcnamara on Thursday 5th of April 2018 09:27:06 AM

04-05-2018

Registered User

What does

Code:

fmadm faulty

show? If replacement is needed, then do it. Once the system "thinks" a certain way about errors it is really hard to try to operate the system like the problem does not exist. As you are seeing. And in fact, doing so may cover up even more serious issues.

I'm not sure what you are actually seeing. Your response seems to me like you have no support contract more than anything else. Which is understandable, but very hard to work around sometimes.

I don't recommend this, but if you are truly desperate try using the

Code:

fmadm repair

command. I do not recommend it except as a last ditch desperation approach to getting a box going for a short time. Once the error occurs again, you are back to square one.

EDIT: let me put this another way - I had a system which showed bad memory, but when the tech search the fmadm information, he found it was a PCI-e problem. But at first blush the system "thought" it was a DIMM. Let Oracle look at it. Don't decide on your own. My first take was wrong.

Last edited by jim mcnamara; 04-05-2018 at 10:39 AM..

jim mcnamara

View Public Profile for jim mcnamara

Find all posts by jim mcnamara

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

memory config - need to get it

Hi, Im in need to get the mem config on a sun sparq Can some one please helpe me? (im not a unixperson)

2. HP-UX

Memory dimm status

Hi, How to check the memory dimm status from OS leavel!! My system model HP N4000. Thanks, ARumugam.

3. Solaris

Understanding memory config with prtdiag -v

Hi. I have 2 SunFire V490 servers running Solaris 10. We may have to upgrade with more memory on one of them to make it compatible with the other. Here's the one with 12GB of RAM: Memory size: 12288 Megabytes ========================= CPUs =============================================== ...

4. Solaris

Network Config on Zone in a Guest LDOM

Solaris for Sparc 11.1 with the latest patches. Created a Guest LDOM with two vnet's net0 and net1, installed a guest whole root, ip exclusive zone that I want to be able to utilize DHCP. I have been able to create the zone but unable to get it to boot because I am unable to assign an anet to it....

5. Solaris

T4 replaced motherboard - recovering LDOM config?

T4-2 issues meant replacing motherboard. I thought the ldom config was automatically saved? Got the oracle document here. At the moment, unable to get ldoms back - here is the output from a few commands:- ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME...

LEARN ABOUT DEBIAN

wd_keepalive

WD_KEEPALIVE(8) 					      System Manager's Manual						   WD_KEEPALIVE(8)

NAME

       wd_keepalive - a simplified software watchdog daemon

SYNOPSIS

       wd_keepalive [-c filename|--config-file filename]

DESCRIPTION

       This is a simplified version of the watchdog daemon. If configured so it only opens
	.IR  /dev/watchdog  ,  and keeps writing to it often enough to keep the kernel from resetting, at least once per minute. Each write delays
       the reboot time another minute. After a minute of inactivity the watchdog hardware will cause a reset. In the case of the software watchdog
       the ability to reboot will depend on the state of the machines and interrupts.

       The wd_keepalive daemon can be stopped without causing a reboot if the device /dev/watchdog is closed correctly, unless your kernel is com-
       piled with the CONFIG_WATCHDOG_NOWAYOUT option enabled.

       Under high system load wd_keepalive might be swapped out of memory and may fail to make it back in in time. Under these	circumstances  the
       Linux  kernel will reset the machine. To make sure you won't get unnecessary reboots make sure you have the variable realtime set to yes in
       the configuration file watchdog.conf.  This adds real time support to wd_keepalive: it will lock itself into memory and there should  be no
       problem even under the highest of loads.

       On  system  running  out of memory the kernel will try to free enough memory by killing process. The wd_keepalive daemon itself is exempted
       from this so-called out-of-memory killer.

OPTIONS

       Available command line options are the following:

       -c config-file, --config-file config-file
	      Use config-file as the configuration file instead of the default /etc/watchdog.conf.

FILES

       /dev/watchdog
	      The watchdog device.

       /var/run/wd_keepalive.pid
	      The pid file of the running wd_keepalive.

SEE ALSO

       watchdog.conf(5)

       watchdog(8)

4th Berkeley Distribution					   January 2005 						   WD_KEEPALIVE(8)