Hi,
first, u should had putted a subject to make easier to retreive related mail then - u perhaps have a problem on your mother board - or the memory chipsets - or a problem on ur scsi disks
- first : check ur disks (overall if they are old (4Mb disks)), de-insert then reinsert them, makje the same for cables and personality modules if there are some; also check to had downloded the bootblock on all disks (to ensure so type "downlod" by telnet) (i had one case where the problem was related to disk); - second : u could run diag floppy for ur particular filer in order to isolate the hardware problem on the mother board - third : reboot your filer and look at changes if any :)
----- Original Message ----- From: "Jordan Share" iso9@phantasticant.com To: "'Toasters@Mathworks.Com'" toasters@mathworks.com Sent: Friday, September 21, 2001 3:49 AM
We have gotten several messages of the following type:
Mon Sep 17 10:25:59 PDT [raid_xor_server:CRITICAL]: 206 CORR SYS ERR 201
eia:1146dc058b20000 fs:254f400 eis:0 isr:80000001 SYS ECC error on DIMM J27 at address=0x1146dc0, bit=31.
Mon Sep 17 10:37:28 PDT [idle_thread0:CRITICAL]: 207 CORR SYS ERR 201
eia:f71874058b20000 fs:2b1f400 eis:0 isr:80000001 SYS ECC error on DIMM J27 at address=0xf718740, bit=31.Wed Sep 19 01:03:53 PDT [GbE-II/e8:CRITICAL]: 212 CORR SYS ERR 201 eia:1dc7590058b20000 fs:256f400 eis:0 isr:80000001 SYS ECC error on DIMM J30 at address=0x1dc75900, bit=31.
Wed Sep 19 01:25:09 PDT [idle_thread0:CRITICAL]: 213 CORR SYS ERR 201
eia:11149bc058b20000 fs:2b4f400 eis:0 isr:80000001 SYS ECC error on DIMM J30 at address=0x11149bc0, bit=31.
Wed Sep 19 01:40:22 PDT [idle_thread0:CRITICAL]: 214 CORR SYS ERR 201
eia:19c54f8058b30000 fs:2b0f400 eis:0 isr:80010001 SYS ECC error on DIMM J30 at address=0x19c54f80, bit=31.
Wed Sep 19 07:01:22 PDT [ispfc_main:CRITICAL]: 216 CORR SYS ERR 201
eia:1ecda80058b20000 fs:2d7f400 eis:0 isr:80000001 SYS ECC error on DIMM J30 at address=0x1ecda800, bit=31.
As near as I can tell, this indicates that a DIMM (or 2) has gone bad. Is
that the case? Or is some level of these errors considered to be normal?
Here's the output of "grep -c "CORR SYS ERR" over the last few messages
files:
messages.5:0 messages.4:3 messages.3:6 messages.2:16 messages.1:160 messages.0:17 messages:14
So, it looks to me like this developed somewhat recently. Should I be
worried about this?
Thanks, Jordan