Vladimir Budnev wrote:
2011/3/22 m.roth@5-cent.us
Vladimir Budnev wrote:
2011/3/22 m.roth@5-cent.us
Vladimir Budnev wrote:
2011/3/22 m.roth@5-cent.us
Vladimir Budnev wrote: > 2011/3/22 m.roth@5-cent.us >> Vladimir Budnev wrote: >> > 2011/3/21 m.roth@5-cent.us >> >> Vladimir Budnev wrote: >> >> > >> >> > We are running, Centos 4.8 on SuperMicro SYS-6026T-3RF
with
>> >> > 2xIntel Xeon E5630 and 8xKingston KVR1333D3D4R9S/4G >> >> >
The next thing you should do, if you don't have them, is go to http://www.supermicro.com/support/manuals/ and d/l the manual, and see what it says about DIMMs.
If you meaned to check whether those DIMM modules a compatible with mother board , its ok. Kingstin KVR1333D3D4R9S is in tested list http://www.supermicro.com/support/resources/memory/display.cfm?sz=4.0&ms...
No, what you need to see is a) whether what you did was valid (for the Supermicro m/b on the server I'm working on right now, the manual says the a-banks must *ALWAYS* be populated...), and b) you might find some troubleshooting info to help you identify which DIMMs are the problem.
And can you say something about cpu wild numbers and determing which dimms are bugged? didnt you mean some post ago that on x core system we must divide cpu value on core numbers to get DIMM slot? e.g. CPU 32/8 cores ->4 slot?
Nope. From your original post:
One more interesting thins is the following output:
[root@zuno]# cat /var/log/mcelog |grep CPU|sort|awk '{print $2}'|uniq 32 33 34 35 50 51 52 53
So with 2 4-core Xeons, I don't understand how you can get 3x and 5x. Could you post some raw messages, either from /var/log/message or from /var/log/mcelog?
mark