Installed Memory 32GB but shows only 16GB Post: 303023409

Sponsored Content

Operating Systems AIX Installed Memory 32GB but shows only 16GB Post 303023409 by bakunin on Saturday 15th of September 2018 09:04:40 PM

09-15-2018

Registered User

Quote:

Originally Posted by filosophizer

2) Configured the deconfigured memory modules

I am glad that it worked out for you. Still, you should analyse how it came that the modules were deconfigured. There are only two reasons i can think of:

a) someone has done it
In this case there must have been some reason for it and you do yourself a big favour when you find out what that reason was. Otherwise it might come back to bite you.

b) the system has done it
This is entirely possible when some hardware problems related to this memory exist. This should have been noted in the logs you just cleaned. Yes, they are ridiculous to read and not very forthcoming but if there was (or maybe *is*) somehardware problem you sure want to know that. Better to have 16GB memory dactivated than to have a system crashing because some bit-stuck-type error.

I hope this helps.

bakunin

bakunin

View Public Profile for bakunin

Find all posts by bakunin

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to get amount of memory installed.

Hi! I'm not a UNIX fanatic but I like using it for the Oracle database since it's not stable in the Windows NT environment (what is?). Problem: Is there any command to show me the amount of installed physical-memory in the machine? Is there some other way to show the processes which uses...

2. Solaris

T5220 How to determine physical memory installed?

Hi, looking to upgrade memory on a pair of T5220's from 32GB to 64GB. Cannot determine current DIMM size and slots used. i.e. not sure if Qty 16 x 2GB or Qty 8 x 4GB. If there are no empty slots, i need to go with higher density DIMMs and retire exsisting the 2GB prtdiag follows. #...

LEARN ABOUT FREEBSD

intro

INTRO(9)						   BSD Kernel Developer's Manual						  INTRO(9)

NAME

     intro -- introduction to system kernel interfaces

DESCRIPTION

     This section contains information about the interfaces and subroutines in the kernel.

PROTOTYPES ANSI-C AND ALL THAT
     Yes please.

     We would like all code to be fully prototyped.

     If your code compiles cleanly with cc -Wall we would feel happy about it.	It is important to understand that this is not a question of just
     shutting up cc, it is a question about avoiding the things it complains about.  To put it bluntly, do not hide the problem by casting and
     other obfuscating practices, solve the problem.

INDENTATION AND STYLE

     Believe it or not, there actually exists a guide for indentation and style.  It is not generally applied though.

     We would appreciate if people would pay attention to it, and at least not violate it blatantly.

     We do not mind it too badly if you have your own style, but please make sure we can read it too.

     Please take time to read style(9) for more information.

NAMING THINGS

     Some general rules exist:

     1.   If a function is meant as a debugging aid in DDB, it should be enclosed in

		#ifdef DDB

		#endif /* DDB */

	  And the name of the procedure should start with the prefix DDB_ to clearly identify the procedure as a debugger routine.

SCOPE OF SYMBOLS

     It is important to carefully consider the scope of symbols in the kernel.	The default is to make everything static, unless some reason
     requires the opposite.

     There are several reasons for this policy, the main one is that the kernel is one monolithic name-space, and pollution is not a good idea
     here either.

     For device drivers and other modules that do not add new internal interfaces to the kernel, the entire source should be in one file if possi-
     ble.  That way all symbols can be made static.

     If for some reason a module is split over multiple source files, then try to split the module along some major fault-line and consider using
     the number of global symbols as your guide.  The fewer the better.

SEE ALSO

     style(9)

HISTORY

     The intro section manual page appeared in FreeBSD 2.2.

BSD
								 December 13, 1995							       BSD