Follow me down the rabbit hole of Fuel PIMM repair.
#11
RE: Follow me down the rabbit hole of Fuel PIMM repair.
(11-28-2021, 09:27 AM)fleedwood Wrote:  
(11-28-2021, 12:47 AM)weblacky Wrote:  
(11-27-2021, 01:38 PM)jan-jaap Wrote:  Did you measure the actual voltage it complains about?
[...]

In this case the answer is, no...I did not actually measure them...but that's because the DS1780 onboard the PIMM is what is reporting that for me

I have a O3K PIMM module where the DS1780 reports 3.2V while measuring showed 3.3V. Temperature is also off, which makes sense as everything is measured by the same ADC.

From where did you measure the 3.3v, exactly?  My base point being that it's local voltage...not PSU voltage.  Similar to how your car's battery may be at say 12.4v at the terminals but your cig lighter voltage is more like 12.3v at no load.

If you used the PCB test point just to the edge of the PIMM DS1790 3.3v sensor pin and got a higher voltage, then I'd say you have something.  If you measured at the PSU, then you're not accounting for voltage drop (due to incorrect placement of the test probe), and the PIMM is very likely correct.

Also given that the the DS1780 had assigned pins for each major voltage (by the datasheet) I've not heard of a single voltage sensor among all the sensors in a DS1780 IC failing that way (I assumed the voltage sensors shared a functional block and just used various different resistances for proper limiting internally, so they all go odd if it's damaged).

At least on Fuel, the PIMM DS1780 monitors : PIMM0 12v Bias, PIMM0 1.5v, PIMM0 3.3v Aux & PIMM0 5v Aux....perhaps even Fuel CPU...but I don't know that for certain.

However, until ALL values are within ENV stable, I won't be able to query it to validate that with the PIMM under repair.

My point being, at this time, for this size of traces, unless I wanted to contaminate the a test point with solder, permanently, to temporarily solder a test wire to measure from, I'm not going to chance a hand-probe measurement during power-on for the CPU...not happening.  A single slip of the probe and I bridge two things that then destroy all my work.

I normally NEVER do power-on testing accept with higher-level items that given me the room for it.  Since we have this wonderful env system...I'm using it.  And to be fair even if each DS1780 has a tolerance of say +-0.2 voltages...that's fine...I'm talking about a short that loses me nearly 3 volt,s now!  So I'm look at a real issue, not a "false" sensor glitch.

Even in a car I'd trust the sensor and check the part before I immediately claimed the sensor was bad...because odds are...the sensor is right :-)
weblacky
I play an SGI Doctor, on daytime TV.

Trade Count: (10)
Posts: 1,716
Threads: 88
Joined: Jan 2019
Location: Seattle, WA
Find Reply
11-28-2021, 09:56 AM
#12
RE: Follow me down the rabbit hole of Fuel PIMM repair.
I had a prof back in university that used to say 'to measure is to know'. Don't assume things. Measure, simplify the problem, solve it.

The DS1780 doesn't have a stellar reputation, so I wouldn't assume it's flawless after 20 years. You're probably right about the short, though.

In my case, I've got several IO4's, several system controllers, and the different combinations result in different erratic behavior. Exactly what gives the Onyx it's well deserved reputation. There are measurement points on the boards, but they're not accessible when the card is in the cardcage and the system is live, so I installed wires:

[Image: onyx_measurements2.jpg]

This proved that the blame was on the system controller (environmental monitoring) and not the IO4. There are some test points on the system controller too, but not on the feedback pin of the regulator so I soldered a wire. More measurements, again narrowing down the source of the problem, and hopefully a solution. But that will be a post of it's own.

[Image: onyx_measurements1.jpg]
jan-jaap
SGI Collector

Trade Count: (0)
Posts: 1,048
Threads: 37
Joined: Jun 2018
Location: Netherlands
Website Find Reply
11-28-2021, 11:44 AM
#13
RE: Follow me down the rabbit hole of Fuel PIMM repair.
(11-28-2021, 09:56 AM)weblacky Wrote:  
(11-28-2021, 09:27 AM)fleedwood Wrote:  
(11-28-2021, 12:47 AM)weblacky Wrote:  
(11-27-2021, 01:38 PM)jan-jaap Wrote:  Did you measure the actual voltage it complains about?
[...]

In this case the answer is, no...I did not actually measure them...but that's because the DS1780 onboard the PIMM is what is reporting that for me

I have a O3K PIMM module where the DS1780 reports 3.2V while measuring showed 3.3V. Temperature is also off, which makes sense as everything is measured by the same ADC.

From where did you measure the 3.3v, exactly?  My base point being that it's local voltage...not PSU voltage.  Similar to how your car's battery may be at say 12.4v at the terminals but your cig lighter voltage is more like 12.3v at no load.

pin 17 of the DS1780 against the ground on the DS1780, which should give me what the DS1780 should see. I already replaced the other DS1780 on this PIMM and and second bugger will follow as soon the replacement chip arrives.

Challenge L Indy Indigo2 Indigo2 R10000/IMPACT O2 Octane Origin2000 Deskside Fuel Challenge S Origin 200 Origin 2000 Rack Origin 2000 Rack Origin 3200 Origin 350
fleedwood
O2

Trade Count: (0)
Posts: 24
Threads: 1
Joined: Dec 2020
Location: Germany
Find Reply
11-28-2021, 10:44 PM
#14
RE: Follow me down the rabbit hole of Fuel PIMM repair.
Ah, well assuming your GNDA (pin 13) and PCB GND are tied together then that’s the correct path (also assuming you don’t have any ground differential by measuring you PCB ground and GNDA in something that will display hundredth’s of a volt). However the data sheet hints that it only advertises a ~5% accuracy on the voltage AD converter and a couple tenths isn’t an issue unless your close to your 10% or 20% env triggers.

For me, I fixed a single, localized, short and now another short (I did say I thought there had to be several, due to several decoupling caps registering short while clearly on different rails) is dominate and pulling 12v PIMM voltage down. I’m still confident in the relative accuracy of my env system.
weblacky
I play an SGI Doctor, on daytime TV.

Trade Count: (10)
Posts: 1,716
Threads: 88
Joined: Jan 2019
Location: Seattle, WA
Find Reply
11-28-2021, 11:09 PM
#15
RE: Follow me down the rabbit hole of Fuel PIMM repair.
Well...Well...I may owe Jan-Jaap and others an apology. They may have been right about the DS1780...Maybe. Here is what I know right now.

I was reassembling my Fuel from the bottom panel tear out and mainboard fan header replacement procedure, when I stopped because it was going to be the time to put a PIMM in...I said to myself...well either I do more testing now or I likely don't get to it (now of course I DO NEED to assemble my Fuel as it was to show that it still works after total disassembly! Then I'd "play" with these other parts. But I'd have to place my working PIMM into it...and I need it on my bench for comparison testing (so not in the Fuel, right now). So, I decided to stop assembly and do more work.

I just finished up another testing go-around with my tools. I've come to an interesting finding which MAY suggest that the on-board DS1780 is slightly damaged, but functional. I'm not 100% sure until I take it out and compare it out of circuit with another DS1780 IC to know for sure!

Here's what I did find:

Using my Huntron 3200S (yeah, I'm going to keep plugging it, it's my cheater-tool) I compared points around BOTH my working 700Mhz PIMM and this unon-working 600Mhz PIMM's DS1780. Layout appears identical in all respects I'd care about for voltage. I probed the 5V line and 12V line sensor positions on the DS1780, on both PIMMs.

For those that aren't aware, part of the magic of newer huntron curve tracers (versus the competition) is their ability to go to EXTREMELY low test voltages. One reason you want to go very low is both A. to be gentle on low-voltage circuits and B. to be able to separate "composite signatures" related to semiconductors.

I'll explain B: Curve tracers produce a deflection graph of voltage/current for a set AC test voltage setting, AC Hz setting, and internal (and display) impedance/resistance. However, most semiconductors need a minimum threshold of voltage to actually "turn on" or conduct ANYTHING. Most of the time (not all) that threshold is ~500mV or 0.5V. It's at this level and higher that semiconductors actually turn on (or have completely turned on...remember threshold). Modern Huntron curve tracers can do 200mV, 300mV, 500mv, and then steps in 100mV increments until 1V, then it goes 1v-20V (I have mine limited to 10v... but in reality I never use past 3V!).

When you have the voltage equal to or higher than semiconductor threshold voltages, your scan (graph) is going to include ANY passives (coils, resistors, cap, AND semiconductors in the path of your probes (unless they are diodes, then I'll see that as a change in the graph's deflection).

But what happens if you're scanning in-circuit (power off of course, power is off using this method) and you go from PCB ground to say the leg of a semiconductor. You may end up getting a graph that has characteristics of BOTH a capacitor, a resistor, a diode, and a semiconductor all in one graph because you went through all those things. Well if I want to STOP at the semiconductor (assuming there is another trace to ground that doesn't HAVE TO go through that semiconductor, somewhere around the cap or resistor (to compete the probing circuit), I can turn down the test voltage to BELOW the semiconductor's threshold which will cause it not to conduct the test signal, thereby removing it's effect/influence on the deflection graph by its "removal" from test (while still being in-circuit). You can also do something similar to remove the effect of capacitors by changing the frequency of your test voltage to diminish or erase their response on the graph to reveal other signature attributes (I almost never do this though).

So, using this little trick, I decided to probe both PIMMs, using on-screen (human visual) comparison, at once by overlay compare. Things were looking pretty similar, until I got to the 12V sensor leg (Pin 15) and its neighbor the 5V sensor leg (Pin 16) on the PIMM's DS1780 IC. These appear to be the only only real variations between the two PIMMs (in-circuit of course).

In BOTH instances (but varied values) the working PIMM has greater impedance (resistance) then the non-working PIMM on BOTH these lines!

While a curve tracer is very poor display of exact impedance, the difference was so great that it was a change of like 15+ degrees on the signatures, very telling!!

Now the question is...is that IN the chip, or outside the chip!? After all a problem between the two rails will of course show up on any points along those rails to the DS1780's legs. So, I just used the threshold trick again to attempt to "exclude" the DS1780 from its own measurement.

When I lowered the test voltage to 300mV, I got (roughly, not exact but close enough in real life) the same signatures for PCB ground to leg 15 and PCB ground to leg 16 on BOTH PIMMs (so similar leg to ground connections on BOTH PIMMs). I forgot what I did between the two legs (directly) but I think was something I thought was fine. When I performed the SAME test again with 800mV test voltage I once again observed the noticeable resistance different between the two.

Now if this was some other resistance along the voltage rail, that I was seeing, it SHOULD have shown up on ultra-low testing! A shorted semiconductor (static short) is now a resistor and looks like one too. So, any shorted external component SHOULD have shown itself on BOTH tests (ultra-low and normal tests). It didn't, so I can only conclude that the test is saying the change in impedance is INSIDE THE DS1780 IC. While it's possible it's a damaged but not shorted semiconductor on the same rails as the DS1780 sensor legs, I cannot be 100% until I remove the DS1780 and scan it out of circuit. If the scan still shows as different from another same (new) IC...then it's the chip.

So, I'd say there is an 80% chance the DS1780 suffered small internal damage which changes its internal impedance on the two sensor inputs but did not short it out (thereby altering measurements!). However, I really did find a bad diode in the VRM signaling though, so it's still possible these legs were exposed to a reverse polarity spike (though PCB ground) due to lack of diode clamping?

Anyway, now the plan is to remove the DS1780 from the PIMM and scan it out of circuit, if it tests okay then it is something external on the voltage rails I haven't located yet. If it does test different, then it really is the DS1780 and I'll replace it and we'll see if that solves the two voltage rail issues in ENV (and the cache failure issues I say before any of my repairs).
(This post was last modified: 12-03-2021, 01:59 AM by weblacky.)
weblacky
I play an SGI Doctor, on daytime TV.

Trade Count: (10)
Posts: 1,716
Threads: 88
Joined: Jan 2019
Location: Seattle, WA
Find Reply
12-02-2021, 11:42 PM
#16
RE: Follow me down the rabbit hole of Fuel PIMM repair.
Wow!  That's a fascinating write-up of a very detailed and thorough analysis.  I wish I understood more of it, LOL! 

It's write-ups like these that are my favourite part of the forum because I can learn from them now, and may need them for reference in the future.

Great work.  It is much appreciated.

SGI:  Indigo, Indigo2, Octane, Origin 300
Sun:  SPARCstation 20 (x4), Ultra 2, Blade 2500, T5240
HP:  9000/380, 425e, C8000
Digital: DECstation 5000/125, PWS 600au
jpstewart
Developer

Trade Count: (1)
Posts: 444
Threads: 6
Joined: May 2018
Location: SW Ontario, CA
Find Reply
12-03-2021, 12:10 AM
#17
RE: Follow me down the rabbit hole of Fuel PIMM repair.
(12-03-2021, 12:10 AM)jpstewart Wrote:  Wow!  That's a fascinating write-up of a very detailed and thorough analysis.  I wish I understood more of it, LOL! 

It's write-ups like these that are my favourite part of the forum because I can learn from them now, and may need them for reference in the future.

Great work.  It is much appreciated.

Funny,
I cannot fit all that hexadecimal work from the Fuel POD PIMM flashing work in my head..not used to it and cannot hold that much in a mental image.  I think those among us from technical fields (especially in IT or the like) share a common knowledge and then each other's experience sort of creeps out of the venn diagram into being unique.  But it's the unique experiences that are most valuable when we come together as a group.

But I take the time to write these because that's how I learned (reading or watching people's troubleshooting mindset and systematic steps).

That being said (without going off on a tangent), I wish we had more of this going on.  Because as much as I like making sure we have all the software we want and people willing to work on that front...not enough people are working on the machines themselves.  Perhaps the idea is once MAME is all awesome...you don't need or want an SGI anymore to run SGI stuff.  I hope that's not going to be the dominant case but it might be.  Right now SGIs have worth for two real reasons: 1. They look cool and have serious history and 2. They've not been fully emulated to be able to run the dedicated software applications performantly (yet).  So if you want to run an SGI, you need an SGI.  They are also much more rare than normal 80's/90's machines, so there is scarcity.

We have systems coming out of storage broken and part prices rising, we need to work now while parts are affordable to be used for training.  I didn't do any of this 4 years ago...but after needing to start fixing household appliances and cars recently I purposely dove into this topic (after getting turn off in my teens/20's years due to the math involved with teaching electrical engineering (which you don't need at all for general repair, by the way) again.  I realize people have lives, I've just aligned my life to this work for silver lining.  But just like vintage cars and such, people have to raise their hands and start tackling/learning new stuff, otherwise we all end up riding a slow train into the ditch as system after system fails and people are priced out of this hobby (or after something they had breaks, they just give up after all that time and dump it all in frustration).

I'm not telling anyone to steal food out your children's mouths but invest in yourself (which really does help you whole family in some ways).  I'm not a schooled/trained engineer for hardware or even microprocessors/firmware.  But I've read stuff and still read and I try what I can within acceptable risk (I think) because I have just great memories of these and fixing them up run like new gives me the ability to enjoy them all over again, in a new way!
weblacky
I play an SGI Doctor, on daytime TV.

Trade Count: (10)
Posts: 1,716
Threads: 88
Joined: Jan 2019
Location: Seattle, WA
Find Reply
12-03-2021, 01:56 AM
#18
RE: Follow me down the rabbit hole of Fuel PIMM repair.
Okay,
I found time to pull the DS1780 off the bad PIMM and replace it.  Results are good, but testing was odd...

So everything came off cleanly...no problems
    .

After I attached a new chip, both PIMMs' in-circuit scans came back very similar to basically identical for the sensor regions.  Also I did a quick scan of the bare PCB before installing the new chip...what I found is that ALL the sensor legs do have a 1kOhm protective resistor (somewhere) and all the pads (with chip out) showed 1K readings...so protection resistors are good and values are the same all the way to PCB ground (consistent...that's good).

But when I probed the old (now removed) chip...the internal impedance doesn't show up.  But the IC protection diodes are GOOD and look EXACTLY like other DS1780 ICs (even have nearly identical voltage drops).  So out of circuit, I'd have told you this was good!  

However I cannot reasonably explain why in-circuit measurements showed internal resistance changes, a new/installed IC has the CORRECT resistances now, but the old IC shows good protection diodes and no issues during outside probing?!?!?  It is possible I was dealing with a loose leg or some kind of base soldering issue before?  I was probing using the test pads on the PCB) not the IC legs.  But to be connected (for having readings) but be missing like 1K of additional resistance (while installed) doesn't make any sense to me.  The protection diode graphs do no indicate leaking either...else I'd say leaking was going on to change resistance.  Nope, clean diode graphics on the old DS1780!

however it's very possible that some unique combination of leg connections would reveal the issue out of circuit, as when it's installed in-circuit you can have several paths going and maybe the route taken shows something that the direct ground to sensor leg route does not.  I also tried VCC to sensor legs, same results with working DS1780 ICs.

Again, out of circuit, this old DS1780 looks fine!  But new installed DS1780 no longer has observed resistance differences on sensor legs for 12V and 5V monitoring!

So you'd have to say the old chip is damaged, but I cannot confirm it with other tools...which is frustrating.

   
weblacky
I play an SGI Doctor, on daytime TV.

Trade Count: (10)
Posts: 1,716
Threads: 88
Joined: Jan 2019
Location: Seattle, WA
Find Reply
12-04-2021, 02:42 AM
#19
RE: Follow me down the rabbit hole of Fuel PIMM repair.
Okay, I'll admit it, I'm scared. I don't really know where to move from here. So I'd like to test if my voltage issue is resolved..but I really don't feel good reflashing my board for lower speed. My gut says...you're pushing your chances too hard! I was thinking about at LEAST placing the PIMM in (like I did before) and seeing if the voltage errors resolve. I think the cache issues I saw could have been due to the incorrect speed (programmed currently at a faster access speed).

If I just place it in and do a POD stop then that should give me a place to check the 5V and 12V PIMM voltages (which did instantly appear when I did this before). That should be very telling! But it won't really "test" the CPU definitively.

If I already had a 600Mhz system I'd have no issues just swapping. Maybe if my voltage test works there might be a Fuel 600Mhz owner who'd be willing to swap this PIMM into their system and see if it runs?

I'll probably do the voltage test as that at least will settle the voltage/shorted issue right away.
weblacky
I play an SGI Doctor, on daytime TV.

Trade Count: (10)
Posts: 1,716
Threads: 88
Joined: Jan 2019
Location: Seattle, WA
Find Reply
12-13-2021, 10:05 AM
#20
RE: Follow me down the rabbit hole of Fuel PIMM repair.
Okay, before I buttoned up my Fuel (see long fuel thread...still more minor works...uggh) I did place this PIMM in it and let it try to start.  I DO NOT reflash, I did not prepare the system in anyway.  

Also I since I've never seen what happens when you place a working, slower, PIMM in a Fuel flashed for a working, faster, PIMM so I don't know if what I'm seeing it normal or not.  

Assistance/experience of others is very welcome here!

Okay the good news is...all voltages are now 100%!  There is NO PIMM 5V error, nor any 12V PIMM errors...but cache errors..yes.  I have (programmed for) a 700Mhz PIMM and placed a repaired 600Mhz PIMM in to the mainboard.  They do (I think) have the same cach sizes (unlike 500Mhz).  However the 700Mhz has a faster cache access speed, I was hoping this error is due to the fact that the 600Mhz needs a slower speed and the data errors are due to that...but I don't know.  Anyone have any ideas if this is due to not programming the flash or likely a real error?

Code:
SGI SN1 L1 Controller

Firmware Image B: Rev. 1.48.1, Built 01/22/2007 11:34:20

001a01-L1>INFO: 001a01 will power up system in  5 seconds...

INFO: 001a01 powering up the system.

env

Environmental monitoring is enabled and running.



Description    State       Warning Limits     Fault Limits       Current

-------------- ----------  -----------------  -----------------  -------

           12V    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.063

        12V IO    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.063

            5V    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    5.070

          3.3V    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.354

          2.5V    Enabled  10%   2.25/  2.75  20%   2.00/  3.00    2.470

          1.5V    Enabled  10%   1.35/  1.65  20%   1.20/  1.80    1.466

        5V AUX    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    5.018

      3.3V AUX    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.302

PIMM 12V BIAS    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.063

          SRAM    Enabled  10%   2.25/  2.75  20%   2.00/  3.00    2.522

          VCPU    Enabled  10%   1.44/  1.76  20%   1.28/  1.92    1.607

     PIMM 1.5V    Enabled  10%   1.35/  1.65  20%   1.20/  1.80    1.495

PIMM 3.3V AUX    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.285

   PIMM 5V AUX    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    5.018

  XIO 12V BIAS    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.000

        XIO 5V    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    5.070

      XIO 2.5V    Enabled  10%   2.25/  2.75  20%   2.00/  3.00    2.483

  XIO 3.3V AUX    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.302


001a01-L1>
entering console mode  001a01 CPU0, <CTRL_T> to escape to L1
.......        DONE

Copying PROM code to memory ...............        DONE

SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa8000000000037f0 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 70  5555555555555555 0000000000000000  155
   Received     : 70  5555557555555555 0000000000000000  155
   Syndrome     : 70  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa8000000000037b1 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 30  cccccccccccccccc 0000000000000000  0cc
   Received     : 30  cccccceccccccccc 0000000000000000  0cc
   Syndrome     : 30  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa800000000003771 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 70  0f0f0f0f0f0f0f0f 0000000000000000  30f
   Received     : 70  0f0f0f0f4f0f0f0f 0000000000000000  30f
   Syndrome     : 70  0000000040000000 0000000000000000  000

   Failing Bits
     SCData<94>
       Asterix R14K   CPU  C3D1 [Pin  AK1]   SRAM C8B7  [Pin D1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  0000000000000000 0000000000000000  000
   Received     : 00  0000000040000000 0000000000000000  000
   Syndrome     : 00  0000000040000000 0000000000000000  000

   Failing Bits
     SCData<94>
       Asterix R14K   CPU  C3D1 [Pin  AK1]   SRAM C8B7  [Pin D1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Brother Double Word Not Zero
   Address      : 0x0000000000002008 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  0000000000000000 5555555555555555  155
   Received     : 00  0000000040000000 5555555555555555  155
   Syndrome     : 00  0000000040000000 0000000000000000  000

   Failing Bits
     SCData<94>
       Asterix R14K   CPU  C3D1 [Pin  AK1]   SRAM C8B7  [Pin D1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  aaaaaaaaaaaaaaaa 0000000000000000  2aa
   Received     : 00  aaaaaaaaeaaaaaaa 0000000000000000  2aa
   Syndrome     : 00  0000000040000000 0000000000000000  000

   Failing Bits
     SCData<94>
       Asterix R14K   CPU  C3D1 [Pin  AK1]   SRAM C8B7  [Pin D1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000400 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  aaaaaaaaaaaaaaaa 0000000000000000  2aa
   Received     : 00  aaaaaaaaeaaaaaaa 0000000000000000  2aa
   Syndrome     : 00  0000000040000000 0000000000000000  000

   Failing Bits
     SCData<94>
       Asterix R14K   CPU  C3D1 [Pin  AK1]   SRAM C8B7  [Pin D1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Brother Double Word Not Zero
   Address      : 0x0000000000000009 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  0000000000000000 5555555555555555  155
   Received     : 00  0000000040000000 5555555555555555  155
   Syndrome     : 00  0000000040000000 0000000000000000  000

   Failing Bits
     SCData<94>
       Asterix R14K   CPU  C3D1 [Pin  AK1]   SRAM C8B7  [Pin D1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa800000000003771 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 70  5555555555555555 0000000000000000  155
   Received     : 70  5555557555555555 0000000000000000  155
   Syndrome     : 70  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000002000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000800 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa800000000003830 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 30  5555555555555555 0000000000000000  155
   Received     : 30  5555557555555555 0000000000000000  155
   Syndrome     : 30  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000002000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000800 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000200 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000010 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 10  5555555555555555 0000000000000000  155
   Received     : 10  5555557555555555 0000000000000000  155
   Syndrome     : 10  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa800000000003830 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 30  5555555555555555 0000000000000000  155
   Received     : 30  5555557555555555 0000000000000000  155
   Syndrome     : 30  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000400 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000200 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000020 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 20  5555555555555555 0000000000000000  155
   Received     : 20  5555557555555555 0000000000000000  155
   Syndrome     : 20  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa800000000003771 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 70  5555555555555555 0000000000000000  155
   Received     : 70  5555557555555555 0000000000000000  155
   Syndrome     : 70  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000002000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000800 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000020 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 20  5555555555555555 0000000000000000  155
   Received     : 20  5555557555555555 0000000000000000  155
   Syndrome     : 20  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa800000000003791 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 10  5555555555555555 0000000000000000  155
   Received     : 10  55555d7555555555 0000000000000000  155
   Syndrome     : 10  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000002000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000200 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000080 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa800000000003791 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 10  5555555555555555 0000000000000000  155
   Received     : 10  55555d7555555555 0000000000000000  155
   Syndrome     : 10  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000002000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000800 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa8000000000037b1 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 30  5555555555555555 0000000000000000  155
   Received     : 30  5555557555555555 0000000000000000  155
   Syndrome     : 30  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000002000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000800 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000020 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 20  5555555555555555 0000000000000000  155
   Received     : 20  5555557555555555 0000000000000000  155
   Syndrome     : 20  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa8000000000037b1 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 30  5555555555555555 0000000000000000  155
   Received     : 30  5555557555555555 0000000000000000  155
   Syndrome     : 30  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000002000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000001000 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000400 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Walking Address: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000200 (Way 0)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  55555d7555555555 0000000000000000  155
   Syndrome     : 00  0000082000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]
     SCData<107>
       Asterix R14K   CPU  C3D1 [Pin AA27]   SRAM C8E6  [Pin H1]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Base + Walk/Inv: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Short March: DATA
   Failure      : Data Miscompare
   Address      : 0x0000000000000001 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 00  5555555555555555 0000000000000000  155
   Received     : 00  5555557555555555 0000000000000000  155
   Syndrome     : 00  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]





SECONDARY CACHE DATA FAILURE: Module 001c01 CPU A
   Subtest      : Full March: DATA
   Failure      : ECC Miscompare
   Address      : 0xa800000000003791 (Way 1)

                  Off ---------     Data     ----------  ECC
   Expected     : 10  5555555555555555 0000000000000000  155
   Received     : 10  5555557555555555 0000000000000000  155
   Syndrome     : 10  0000002000000000 0000000000000000  000

   Failing Bits
     SCData<101>
       Asterix R14K   CPU  C3D1 [Pin AG33]   SRAM C8E6  [Pin H8]


scache_test: FAILED
Attempting to clear up scache failure with power cycle #1...

escaping to L1 system controller

001a01-L1>l1

Due to message limits on this forum I had to remove additional output, but it's duplicated during the second boot attempt so you're not missing anything.

I so see the H1 and H8 pin similarities and the mask of the errors is well defined.  I guess this could be a connection problem...thought I'm unsure where to pin that down...also the cache modules are BGA...so I'd be heating blind and praying (not really my style).  But thoughts on that info would be good as well!  If there is some kind of protection beforehand on that pin/line, that could be a place to look?

I wished I had another Fuel mainboard (maybe one that needs repair) that I could program for 500Mhz and use as a testing board.  I don't have the funds or wants to risk my working (repaired) board (since I only have one).

I placed my PIMM (700Mhz) into the system and booted fine.  Anyway thoughts?
(This post was last modified: 12-16-2021, 12:39 AM by weblacky. Edit Reason: Specific Pins mentioned. )
weblacky
I play an SGI Doctor, on daytime TV.

Trade Count: (10)
Posts: 1,716
Threads: 88
Joined: Jan 2019
Location: Seattle, WA
Find Reply
12-16-2021, 12:35 AM


Forum Jump:


Users browsing this thread: 1 Guest(s)