On Tue, 23 Jan 2007 12:46:58 -0600, Bo opined:

> "William Dennen" wrote in message
> news:eopafk$s74$1@aioe.org...
>> Bo
>> I've an idea, if you've got sufficient hardware, that may shed some light
>> on where the problem is. You need 4 boards, 2 5100s and 2 anything VME.
>> Call the 5100s A & B, the others C & D. Set up C & D so they can
>> read/write each other's memory and also either A or B. NO shared memory
>> configured for these two. You've got A & B already set up. Create the
>> hang condition and then:
>> (1) can C & D still read/write each other?
>> (2) can either C or D read/write to either A or B?
>> (3) can either A or B read/write to either C or D?
>>
>> The essence of what you're trying to determine is whether the system
>> controller function is hosed or not. IF C & D can still read/write then
>> it is not and the hang condition is local to A/B.
>
> 1) C&D cannot read/write.
> 2) no
> 3) no
>
> ie it 'appears' to be an honest-to-God hardware lock-up--from which only a
> power cycle will recover. Scary, huh?
>
> Bo

Indeed it's scary and smells of an errata, it appears that the system
controller has left the scene. I would recommend getting Tundra to look
at the issue. I'm sure they'll want a dump of the Universe and a trace if
you've got the capability. You can initiate the dialog at
http://www.tundra.com/support.aspx?bid=481&id=962. Hopefully they can
simulate the sequence ...

Regards
--
>@<
Bill Dennen wdennen@gmail.com
Cluelessness: There are no stupid questions, but there are a LOT of inquisitive idiots.
(despair.com)