NYCPHP Meetup

[Jesse Callaway]

The dmidecode command will likely help in this case. I'm assuming you don't
have drac set up for remote hardware analysis, in the future it or its
little brother ipmi will be helpful.

This is likely not a php question.
On Jul 23, 2013 7:44 AM, "David Roth" <davidalanroth at gmail.com> wrote:

> I'm getting these in the log on CentOS 6.4 a couple of times a week:
>
> EDAC MC0: CE page 0x9521e, offset 0xb00, grain 128, syndrome 0x49, row 2,
> channel 1, label "": i3000 CE
> EDAC MC0: CE page 0x9521e, offset 0xb00, grain 128, syndrome 0x49, row 2,
> channel 1, label "": i3000 CE
> EDAC MC0: CE page 0x9521e, offset 0xb00, grain 128, syndrome 0x49, row 2,
> channel 1, label "": i3000 CE
> EDAC MC0: CE page 0x9521e, offset 0xb00, grain 128, syndrome 0x49, row 2,
> channel 1, label "": i3000 CE
>
> If I'm correct, this means there is a problem with a memory module. What
> I'm not clear on, is how to determine from this what row 2, channel 1
> refers to. The Dell server this is running on has four memory slots. Anyone
> have a way for me to equate this information from the logs to determine
> which memory slot this is referring to?
>
> The error message is intermittent so removing RAM in an attempt to isolate
> which memory stick or slot is having the problem hasn't been useful. Thanks!
>
> David Roth
>
>
>
>
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/show-participation
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20130723/0e6a9e05/attachment.html>