Hi,
to finish that story:
The error was actually produced by a faulty motherboard. Tyan replaced
it without much trouble. Be advised that MEMTEST86+ couldn't find the
problem.
thanks for your immediate response. I will replace the board, but I am
wondering what the error message actually
Hi everybody,
thanks for your immediate response. I will replace the board, but I am
wondering what the error message actually means?
Oct 16 14:07:36 xenserver1 kernel: EDAC MC0: UE row 0, channel-a= 0
channel-b= 1 labels -: NON-FATAL recoverable (Branch=0 DRAM-Bank=0
Buffer ID = 0 RDWR=Read
Hi,
I updated a server yesterday from
kernel 2.6.18-128.7.1.el5xen to kernel 2.6.18-164.el5xen
After rebooting, my message log is flooded every second or so with this error
messages:
Oct 6 14:52:20 xenserver1 kernel: EDAC MC0: UE row 0, channel-a= 0 channel-b=
1 labels -: NON-FATAL
Run a memtest instead. If it fails, simply replace it.
On Tue, Oct 6, 2009 at 9:28 PM, Michael Schumacher
michael.schumac...@pamas.de wrote:
Hi,
I updated a server yesterday from
kernel 2.6.18-128.7.1.el5xen to kernel 2.6.18-164.el5xen
After rebooting, my message log is flooded every
On Tuesday 06 October 2009 09:28, Michael Schumacher wrote:
Question1: how many recoverable RAM errors are acceptable?
No errors are acceptable.
Being located in Germany makes the just return it to the dealer
proposal quite unattractive.
I don't understand why you can't return the memory
Am Dienstag, den 06.10.2009, 15:28 +0200 schrieb Michael Schumacher:
Hi,
I updated a server yesterday from
kernel 2.6.18-128.7.1.el5xen to kernel 2.6.18-164.el5xen
After rebooting, my message log is flooded every second or so with this error
messages:
Oct 6 14:52:20 xenserver1 kernel:
6 matches
Mail list logo