[Gems-users] livelock/deadlock after loading opal.


Date: Wed, 21 Sep 2005 11:02:42 -0600
From: Liqun Cheng <liqun.cheng@xxxxxxxxx>
Subject: [Gems-users] livelock/deadlock after loading opal.
Hi

The splash2 benchmarks can't not finish after I load the opal module. I have also tried a tiny "Hello world" program, but the problem remains. I add two magic instructions: one before printf, and one after printf. Opal and Ruby are loaded at the callback of the first magic instruction, everything is performed accordingly to the quickstart page, but the simics still hasn't reached the second magic instruction after a whole night on a dual-core  Xeon 2.0G box with 4G memory. So I suspust there is something wrong with opal.

BTW, everything is fine on simics and simics+ruby, although I did have some warnings at opal0.init(),
pstate_t: warning: control register #0 == "(null)" has simics name "g0".
pstate_t: warning: control register #1 == "(null)" has simics name "g1".
pstate_t: warning: control register #2 == "(null)" has simics name "g2".
.....................
Is this the problem?

What's more, the opal continuously reports something like
patch  PC: 0x44c7e0 0x409800
patch  NPC: 0x533764 0x409804
patch  PC: 0x533768 0x409800
patch  NPC: 0x44c678 0x409804
patch  PC: 0x44c6dc 0x409800
patch  NPC: 0x44c4c4 0x409804
[Turbo] Trampoline found at block start.
[Turbo] Trampoline found at block start.
[Turbo] Trampoline found at block start.
[Turbo] Trampoline found at block start.
[Turbo] Trampoline found at block start.
[Turbo] Trampoline found at block start.
[Turbo] Trampoline found at block start.
............

Advices are appreciated!
Legion


[← Prev in Thread] Current Thread [Next in Thread→]