Re: [Gems-users] running barnes-hut

[Luke Yen <lyen@xxxxxxxxxxx>]

Hi:

  I have noticed alot of "patches" also on our version of the barnes
workload.  However I don't recall seeing the decodeFails messages.  This
is displayed whenever Opal cannot properly decode an instruction.  The
best way to debug this is to go through the code in Opal where instructions are
decoded (opal/system/static.C, in the decodeInstructionInfo() function),
and track down which switch statements are causing the failures.
>From your output this seems to be isolated to a single instruction.

  FYI decodeFail() gets called whenever the FAIL macro gets invoked inside
decodeInstructionInfo().


  Hope this helps,
   Luke

On Wed, 1 Jun 2005 yilmazer@xxxxxxxxxxx wrote:

> Hello,
> When I was running splash benchmarks(fft,lu) first I got the warning messages
> below and after that operating system began to sync. What can be the problem?
>
>
>
> ### statici::decodeFails. line:877. inst=0x737472
>  0000 0000 0111 0011:0111 0100 0111 0010
> ### statici::decodeFails. line:877. inst=0x737472
>  0000 0000 0111 0011:0111 0100 0111 0010
> ### statici::decodeFails. line:877. inst=0x737472
>  0000 0000 0111 0011:0111 0100 0111 0010
> ### statici::decodeFails. line:877. inst=0x737472
>  0000 0000 0111 0011:0111 0100 0111 0010
> ### statici::decodeFails. line:877. inst=0x737472
>  0000 0000 0111 0011:0111 0100 0111 0010
> ### statici::decodeFails. line:877. inst=0x737472
>  0000 0000 0111 0011:0111 0100 0111 0010
> ### statici::decodeFails. line:877. inst=0x737472
>  0000 0000 0111 0011:0111 0100 0111 0010
> ### statici::decodeFails. line:877. inst=0x737472
>  0000 0000 0111 0011:0111 0100 0111 0010
> patch  NPC: 0xffffffffff3b3840 0xff3b3840
> patch  NPC: 0xffffffffff3b3840 0xff3b3840
> patch  NPC: 0xffffffffff3b3840 0xff3b3840
> patch  NPC: 0xffffffffff3b3840 0xff3b3840
> patch  PC: 0xff104fe8 0x1000400
> patch  NPC: 0xff104fec 0x1000404
> patch  PC: 0x1000480 0x1000820
> patch  NPC: 0x1000484 0x1000824
> patch  PC: 0x1000d00 0xf000d294
> patch  NPC: 0x1000d04 0xf000d298
> patch  PC: 0x1000d00 0xf000d294
> patch  NPC: 0x1000d04 0xf000d298
> patch  PC: 0x1000d00 0xf000d294
> patch  NPC: 0x1000d04 0xf000d298
> patch  PC: 0x1000d00 0xf000d294
> patch  NPC: 0x1000d04 0xf000d298
> patch  PC: 0x1000d00 0xf000d294
> patch  NPC: 0x1000d04 0xf000d298
> patch  PC: 0x1000d00 0xf000d294
> patch  NPC: 0x1000d04 0xf000d298
>
>
>
>
> Quoting Mike Marty <mikem@xxxxxxxxxxx>:
>
> > > This looks like an operating system issue. Make sure you have enough locks
> > > available specified in your OS. Different systems have different parameters
> > to
> > > set, usually in /etc/system, but you might want to check with your OS
> > reference
> > > manual.
> > >
> >
> > And be sure that it works without Ruby/Opal loaded.
> >
> > --Mike
> >
> >
> > _______________________________________________
> > Gems-users mailing list
> > Gems-users@xxxxxxxxxxx
> > https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> >
>
>
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>