Nekonomicon - Indigo2 ECC panic... FIXED

chicaneuk
Who joined July 10, 2012, 2:48 a.m.
and authored 44 notes

Wrote the following at April 18, 2013, 11:26 a.m...

Help!

I'm a bit of an SGI newbie. I currently own an Indigo 2 and it hasn't wanted to boot for some time.. I finally got around to sourcing the correct serial cable from Amazon and a USB to serial adaptor and got it all hooked up tonight. The system powers on, gives me a little menu and when I ask it to boot the system after about 5 seconds of disk access it dumps the following:

Code:

  ecc_panic initiated! (for cpu 0)
  
  ECC PANIC: Uncorrectable HARDWARE ECC error, in kernel mode
  
  CPU SysAD bus: |?!Syndrome at addr 0x10000008 normal!
  
  CacheErr 0xe400000f<ER,EC,ED,EE,SIDX=0x882c51f8,PIDX=0x882c51f8>
  
  Status 0xff05<IM8,IM7,IM6,IM5,IM4,IM3,IM2,IM1,IPL=0,MODE=KERNEL,ERL,IE>
  
  ErrorEPC 0x8801a88c, Exception Frame 0xa834bde0, ECC Frame 0xa834bf88
  
  PhysAddr 0x10000008, VirtAddr 0x7008
  
  cpu_err_stat: 0x3a0, cpu_err_addr: 0x10000000
  
  gio_err_stat: 0x0, gio_err_addr: 0x1fbd9023
  
  hpc3_buserr_stat: 0xbfbb0010
  
  ECC cbits 0x0 data_lo 0x0 data_hi 0x0
  
  sbe dblwrds 0x0 mbe dblwrds 0x0
  
  s_taglo 0x10003cd<paddr=0x882c5358,INVAL,vind=0x882c5358,ecc=0x882c5358>
  
  PANIC: Uncorrectable cache ecc/parity error
  
  Kernel/Interrupt Stack Overflow @0x881ba988 sp:0x88317e28 k1:0x23001f
  
  ra:0x881bd2b0 stkflag:1
  
  DOUBLE PANIC: stack underflow/overflow

The system is fully populated with RAM and my gut is telling me this is a memory error... am I right? If so is it time to start swapping out SIMM's one at a time until I find the culprit(s)?

Thanks in advance!

_________________

robespierre
Who joined Sept. 12, 2011, 1:28 p.m.
and authored 318 notes

Wrote the following at April 18, 2013, 3:24 p.m...

it looks like a broken PIMM. you should try blowing out/cleaning the connectors between the processor module and the mainboard, but likely it's toast. Indigo2 processor modules are still relatively common on the used market.

_________________
:PI:

SGI_Ben
Who joined July 9, 2009, 11:05 a.m.
and authored 8 notes

Wrote the following at April 18, 2013, 4:56 p.m...

If you have an sgi machine and the graphics settings (refresh rate) for the irix desktop are higher than a new monitor supports, can you change the settings from the maintenance command prompt ?

SGI_Ben
Who joined July 9, 2009, 11:05 a.m.
and authored 8 notes

Wrote the following at April 18, 2013, 5:06 p.m...

The best way to come out of this situation is, go to prom monitor by pressing esc key when the
Sorry guys think I might of found the answer -

system shows the initial screen. Type single at >>> prompt.
Once you enter into single user mode, goto /usr/gfx/ucode/CRM/vof or /usr/gfx/ucode/CRIME/vof.
Copy the file 1024x768_60 to 1280x1024_96.

OR

go to /etc/rc2.d

vi S99setmonx

/usr/gfx/setmon -n 1024x768_60.

write and close.

Reboot.

cris_adder
Who joined Jan. 13, 2010, 12:10 a.m.
and authored 152 notes

Wrote the following at April 18, 2013, 7:01 p.m...

Have seen this type of error caused by the CPU but also sometimes this type of error can be caused by faulty RAM too... have seen this error occur on an Indigo, which was giving cache errors, and it turned out to be the RAM... so it may be worth checking that out also...

foetz
Who joined April 14, 2003, 3:34 a.m.
and authored 4732 notes

Wrote the following at April 18, 2013, 7:14 p.m...

definitely clean and reseat everything before trashing it

_________________
r-a-c.de

foetz
Who joined April 14, 2003, 3:34 a.m.
and authored 4683 notes

Wrote the following at April 18, 2013, 7:16 p.m...

yup single user mode and change the settings. or put the disk in another machine and change it from there.

_________________
r-a-c.de

chicaneuk
Who joined July 10, 2012, 2:48 a.m.
and authored 44 notes

Wrote the following at April 18, 2013, 11:54 p.m...

Thanks for the feedback guys - much appreciated. I'm thinking a can of compressed air to blow dust out of the nooks and crannies, and perhaps alcohol wipes to clean connectors and so forth - or is that dangerous and likely to induce a static charge? Not really owned equipment old enough to need this sort of cleaning before so unsure how to proceed!

(and don't want to make the situation worse!)

_________________

jan-jaap
Who joined June 17, 2004, 10:35 a.m.
and authored 3658 notes

Wrote the following at April 19, 2013, 12:13 a.m...

I've never seen a bad contact between a CPU and mainboard.

If the CPU module goes bad, it's almost always the cache memory, and IRIX should complain about uncorrectable cache errors.

I have to clean the memory of my Indigo2's every once in a couple of years. Especially the R10K Indigo2 with 1024MB RAM because the 'gigaram' chips don't have gold contact fingers.

Validate your cleaning with the diagnostics tests (press ESC to interrupt the boot process when prompted and select 'run diagnostics).

_________________
Now this is a deep dark secret, so everybody keep it quiet

It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service:

(2x)

In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)

smj
Who joined Nov. 12, 2007, 7:54 p.m.
and authored 935 notes

Wrote the following at April 19, 2013, 1:43 a.m...

SGI_Ben wrote:

Once you enter into single user mode, goto /usr/gfx/ucode/CRM/vof or /usr/gfx/ucode/CRIME/vof.
Copy the file 1024x768_60 to 1280x1024_96.

I may be missing something, but surely not this! Looks to me (while sleep-deprived) like you're wiping out the old definition for 1280x1024_96 - that way lies madness! Use x setmon instead. You don't want to be that guy posting in a few years, "I have a new monitor, but every setting I try displays 1024x768_60..."

Kudos on finding your own answer, though, and following up in your thread!

Edit : Yeah yeah, "setmon" not "xsetmon". Sheesh, I said I was sleep deprived...

_________________
Then? :IRIS3130:

... Now?

+MLA

... Other: DEC :BA213:

Sun , DG AViiON , NeXT :Cube:

hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8449 notes

Wrote the following at April 19, 2013, 3:43 a.m...

smj wrote:

SGI_Ben wrote:

Once you enter into single user mode, goto /usr/gfx/ucode/CRM/vof or /usr/gfx/ucode/CRIME/vof.
Copy the file 1024x768_60 to 1280x1024_96.

I may be missing something, but surely not this! Looks to me (while sleep-deprived) like you're wiping out the old definition for 1280x1024_96 - that way lies madness! Use xsetmon instead.

Damn good eyes ! I just whooshed over the top without reading, it's such a faq. SMJ is quadruple correct, this method is a big fat NO WAY !!!

btw - have to use < setmon >, xsetmon won't run without the graphics up.

You can also do it from the prom, < setenv gfx low > but I am not sure that all SGI kompewters will recognize that.

_________________
lemon tree very pretty and the flower very sweet ...

SGI_Ben
Who joined July 9, 2009, 11:05 a.m.
and authored 8 notes

Wrote the following at April 20, 2013, 11:49 a.m...

Thanks for the help guys and pointing out the no no !

guardian452
Who joined Aug. 21, 2007, 9:12 p.m.
and authored 2601 notes

Wrote the following at April 20, 2013, 5:17 p.m...

jan-jaap wrote:

I've never seen a bad contact between a CPU and mainboard.

If the CPU module goes bad, it's almost always the cache memory, and IRIX should complain about uncorrectable cache errors.

Almost, but not always... viewtopic.php?f=3&t=16724371&p=7334288

_________________
:Onyx:

(Maradona) :Octane:

(DavidVilla) A1186 (Xavi) d800 (Pique) d820 (Neymar)
A1370 (Messi) dp43tf (Puyol) A1387 (Abidal) A1408 (Guardiola)

chicaneuk
Who joined July 10, 2012, 2:48 a.m.
and authored 44 notes

Wrote the following at April 20, 2013, 11:56 p.m...

Hm - can't remember what CPU it has in it. I don't think it's particularly high-end though.

_________________

SAQ
Who joined July 19, 2006, 7:37 a.m.
and authored 5632 notes

Wrote the following at April 24, 2013, 6:43 a.m...

Try stripping it to one quad of memory and seeing if the problem disappears. If it's still around then try a different single quad.

The error does specify cache ECC error, so it's likely a processor module (PM) fault. You can try touching up the solder connections if you're good.

_________________
Damn the torpedoes, full speed ahead!

There are those who say I'm a bit of a curmudgeon. To them I reply: "GET OFF MY LAWN!"

:Indigo:

(single-CM)

chicaneuk
Who joined July 10, 2012, 2:48 a.m.
and authored 44 notes

Wrote the following at July 24, 2013, 2:54 a.m...

Just to bump this to a conclusion, can confirm it's one bank of memory that's duff. Spent a bit of time last night pulling the system apart, reseating stuff and was still running into problems. Then started to rotate taking one bank of memory out and lo and behold with one set of 4x32MB SIMM's removed the system boots and runs perfectly time after time. With these modules installed the system hangs on booting, sometimes won't even power on properly... obviously there's a very unhappy module in there.

At some point I'll rotate all four through one of the banks of good modules and see if I can isolate the faulty one.

Thanks for the tips! Was great to get it running again.

_________________

SGI: Hardware

Indigo2 ECC panic... FIXED