hi,
actually we r working on the servers remotely.......
my task is to troubleshoot the problems......
so,our task is to investigate why these kind of errors messages were generating continuously.

I got the problem like "Bad memory module"

some log files inside /var/log/messages were generating continuously...like as below

[root@cnlx100 ~]# cat /etc/issue
Red Hat Enterprise Linux ES release 4 (Nahant Update 7)
Kernel \r on an \m


[root@cnlx100 ~]#tail /var/log/messages
Apr 15 10:24:04 cnlx100 kernel: EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
Apr 15 10:24:04 cnlx100 kernel: MC0: CE page 0x3c66, offset 0x1a0, grain 8, syndrome 0xd6b4, row 0, channel 0, label "": k8_edac

i think this is due to some h/w problem.

so please give me a solution how to solve this.
And is necessary to reconfigure the memory modele? If yes can u please give me the steps to reconfigure the memory module.

Hi,

I suggest that you test the hardware. You can use 'memtest86'. But this would require the server to be taken down and launched locally. Run the test as long as you can or until errors out. If it's a bad cell or stick then replacement is the best option.

The above link and others can be found at 'Slackware-Links'. More than just Slackware® links!

Gee, you think that a Bad Memory Module error could be because of a hardware problem?? Really??? The message is very, VERY obvious, as it was in your OTHER thread about the exact same thing.
We did, but you're obviously having problems understanding it. IF YOU HAVE BROKEN HARDWARE, YOU REPLACE THE BROKEN PARTS. There's nothing else you can do, no magical command, on any OS, is going to 'fix' a piece of broken hardware.
This is essentially the same thing you asked in your other thread. Don't know what you're expecting to get, but if you've got broken hardware, you have one choice: FIX IT.