Re: [Gems-users] failed Simics session upon Ruby init

[Dan Gibson <degibson@xxxxxxxx>]

Before I fly off the hinge and assume the worst (like I did with the 
last gems-users segfault), can you verify the following for me?
1) your checkpoint has only one processor (I've done it before)
2) you modified the files in the Gems 1.3 release appropriately for 
Simics 3.0. These should include:
$GEMS/common/Makefile.simics_version -- set the version string to 3.0
$GEMS/common/Makefile.common -- set the CC for your chosen compiler, 
update the path for SIMICS_INCLUDE_ROOT to point to your Simics 3.0 
installation's include/ directory.
$GEMS/ruby/module/Makefile -- set the runtime library path (not 
necessary if using native compiler), and use the Simics-3.0-appropriate 
definition of GEMS_ROOT.
$GEMS/opal/module/Makefile -- Use the Simics-3.0-appropriate definition 
of GEMS_ROOT.
Regards,
Dan

Adam Kaplan wrote:
> Hello all.  I'm trying to get Gems-1.3 running with Simics-3.0.18.  After
> successfully building Opal and Ruby, as per the online wiki
> documentation, I tried a simple simulation from a booted-Solaris
> checkpoint (as per the QuickStart guide).  Here is the output of that
> Simics session, which died when Ruby was initialized.  I built Ruby to
> use the MOSI_SMP_bcast protocol, as per the guide.  I tried again
> (with memory sizes of 256MB, 512MB, 1 GB, and the default of 4 GB), but
> to no avail.  I'm under the impression that the checkpoint has a memory
> size of 256MB, as per its map (see below).  Any ideas or additional
> things to try would be most appreciated.  Thanks for your time!
>
> simics> read-configuration ../../targets/serengeti/kap-abisko-sol8-afterboot.conf
>
> simics> phys_mem.map
> base               object               fn offs               length
> 0x0000000000000000 memory                0 0x0                0x10000000
> 0x000007fff07ffff0 simicsfs              0 0x0                0x10
>
> simics> instruction-fetch-mode instruction-fetch-trace
> [cpu0 info] Note that on this cpu, instruction-fetch-trace is implemented
> using instruction-cache-access-trace with a suitable cache line size.
>
> simics> istc-disable
> Turning I-STC off and flushing old data
>
> simics> dstc-disable
> Turning D-STC off and flushing old data
>
> simics> load-module ruby
> successful installation of the ruby timing model.
>
> simics> load-module opal
> Queue registration cpu0
> successful installation of the opal queue.
> hfa_init_local done:
>
> simics> ruby0.setparam g_NUM_PROCESSORS 1
>
> simics> ruby0.setparam g_MEMORY_SIZE_BYTES 268435456
>
> simics> ruby0.init
> Ruby Timing Mode
> Warning: optimizations not enabled.
> Creating event queue...
> Creating event queue done
> Creating system...
>   Processors: 1
> Creating system done
> Ruby: ruby-opal link established. removing timing_model.
> Segmentation fault (SIGSEGV) in main thread
> The simulation state has been corrupted. Simulation cannot continue.
> Please restart Simics.
>
> 					-Adam
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>
>
>