Hi,
I recently salvaged an SGI Fuel from being disposed. The system does not power up and I get a whole bunch of ALERT messages when connected to the L1 port on the system board:
ALERT: NODE EEPROM read error, no acknowledge
ALERT: Error initializing the NODE 0 monitor, no acknowledge
ALERT: Error initializing the NODE 1 monitor, no acknowledge
ALERT: Error initializing the NODE 2 monitor, no acknowledge
ALERT: Error initializing the PIMM monitor, no acknowledge
ALERT: Error initializing the ODYSSEY monitor, no acknowledge
ALERT: Error initializing the BEDROCK monitor, no acknowledge
and so on, complaining on voltages, fan speeds, temperature sensors etc. Then, after many lines:
****************************************
controller firmware panic! resetting...
****************************************
IMAGE B: Rev. 1.30.16
[thread ID 300013cc stack]
TR: ffecb6e4 ffec85dc ffedc4c4 ffedc710 ffedc87e ffedaaa0 ffedb41a
TR: ffedb604 ffeb8918 ffeb8a5e ffec41ec ffe805cc ffeb1728 00000000
(if you see this, please email ssh@sgi.com and include
the output from the 'log' command and a description of
what caused the problem)
ALERT: Running Flash image A because image B failed during boot and is probably corrupt.
The same ALERT messages then repeat in semi-random order for flash image A. It does not drop to a prompt at any point.
Does anyone know what might be causing this? I think it's unlikely both flash images are corrupted. Is it a PSU problem?
Thanks for any hints!
John
I recently salvaged an SGI Fuel from being disposed. The system does not power up and I get a whole bunch of ALERT messages when connected to the L1 port on the system board:
ALERT: NODE EEPROM read error, no acknowledge
ALERT: Error initializing the NODE 0 monitor, no acknowledge
ALERT: Error initializing the NODE 1 monitor, no acknowledge
ALERT: Error initializing the NODE 2 monitor, no acknowledge
ALERT: Error initializing the PIMM monitor, no acknowledge
ALERT: Error initializing the ODYSSEY monitor, no acknowledge
ALERT: Error initializing the BEDROCK monitor, no acknowledge
and so on, complaining on voltages, fan speeds, temperature sensors etc. Then, after many lines:
****************************************
controller firmware panic! resetting...
****************************************
IMAGE B: Rev. 1.30.16
[thread ID 300013cc stack]
TR: ffecb6e4 ffec85dc ffedc4c4 ffedc710 ffedc87e ffedaaa0 ffedb41a
TR: ffedb604 ffeb8918 ffeb8a5e ffec41ec ffe805cc ffeb1728 00000000
(if you see this, please email ssh@sgi.com and include
the output from the 'log' command and a description of
what caused the problem)
ALERT: Running Flash image A because image B failed during boot and is probably corrupt.
The same ALERT messages then repeat in semi-random order for flash image A. It does not drop to a prompt at any point.
Does anyone know what might be causing this? I think it's unlikely both flash images are corrupted. Is it a PSU problem?
Thanks for any hints!
John