Hi Tushar, Thanks for your quick reply. I was able to run the simulation with ruby_random_test.py + ALPHA_MOESI_hammer protocol without any error. At a glance, I thought the protocol used was a problem. However, after more tests, I found that the simulation failed with option to invoke garnet-network as like: * ./build/ALPHA_Network_test/gem5.debug ./configs/example/ruby_network_test.py --num-cpus=4 --num-dirs=4 --topology=Mesh --mesh-rows=2 --sim-cycles=1000 --injectionrate=0.01 --synthetic=0 --fixed-pkts --maxpackets=1 --garnet-network=fixed* Meanwhile, it worked fine if I drop the option "--garnet-nework=fixed" off the command like: * ./build/ALPHA_Network_test/gem5.debug ./configs/example/ruby_network_test.py --num-cpus=4 --num-dirs=4 --topology=Mesh --mesh-rows=2 --sim-cycles=1000 --injectionrate=0.01 --synthetic=0 --fixed-pkts --maxpackets=1*
Based on this observation, I wonder if you succeed in running a simulation with configs/example/ruby_network_test.py, especially invoking garnet network. I tested the ruby network tester with both g++ 4.3.2 and g++ 4.6.1, and checked with different garnet mode (i.e. flexible) as well. They had the same result "failure" (please see previous email). If you think this is related to c++ version issue, could you tell me which version of c++ you are using on your platform? (including other packages' version such as swig/python/zlib/m4 if possible). Can you give me more comment on this garnet invocation issue? Thanks. - Juyoung On Tue, May 8, 2012 at 12:08 PM, Tushar Krishna <[email protected]>wrote: > Hi Juyoung, > In future pls send the emails directly on gem5-users so that others who > experienced similar problems can help out as well? > I am cc:ing gem5-users > > > I just pulled out the latest version of gem5 and ran this exact command > and it worked fine. > Are you getting this error only with ruby and garnet and this particular > protocol? > > It seems to me that it might be some C++ version issue etc … > > Can you test it with another protocol too, without garnet. > Eg: > > scons build/ALPHA_MOESI_hammer/gem5.debug > > ./build/ALPHA_MOESI_hammer/gem5.debug configs/example/ruby_random_test.py > --num-cpus=4 --num-dirs=4 --topology=Mesh --mesh-rows=2 -l 1000 > > [The -l command in ruby_random_test specifies the number of cycles to > inject]. > > - Tushar > > > On May 8, 2012, at 1:31 PM, Juyoung Jung wrote: > > Hi Tushar, > > > I am trying to run Garnet simulator with gem5 following the documentation > found at http://www.gem5.org/Networktest. However, in my case, it failed > to running as it stand, even if other setup conditions have been met. I > tested both the most recent stable and dev gem5, and the same problem > happened. The followings are errors and warnings which I ran into. > > > #> ./build/ALPHA_Network_test/gem5.debug > ./configs/example/ruby_network_test.py --num-cpus=4 --num-dirs=4 > --topology=Mesh --mesh-rows=2 --sim-cycles=1000 --injectionrate=0.01 > --synthetic=0 --fixed-pkts --maxpackets=1 --garnet-network=fixed > > gem5 Simulator System. http://gem5.org > gem5 is copyrighted software; use the --copyright option for details. > > gem5 compiled May 8 2012 12:20:15 > gem5 started May 8 2012 13:15:56 > gem5 executing on panther > command line: ./build/ALPHA_Network_test/gem5.debug > ./configs/example/ruby_network_test.py --num-cpus=4 --num-dirs=4 > --topology=Mesh --mesh-rows=2 --sim-cycles=1000 --injectionrate=0.01 > --synthetic=0 --fixed-pkts --maxpackets=1 --garnet-network=fixed > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > warning: add_child('cls'): child 'credit_links0 credit_links1' already has > parent > Global frequency set at 1000000000 ticks per second > Traceback (most recent call last): > File "<string>", line 1, in <module> > File > "/home/juyoung/research/simulators/gem5-dev/gem5/src/python/m5/main.py", > line 357, in main > exec filecode in scope > File "./configs/example/ruby_network_test.py", line 131, in <module> > m5.*instantiate()* > File > "/home/juyoung/research/simulators/gem5-dev/gem5/src/python/m5/simulate.py", > line 90, in instantiate > for obj in root.descendants(): obj.*createCCObject()* > File > "/home/juyoung/research/simulators/gem5-dev/gem5/src/python/m5/SimObject.py", > line 1035, in createCCObject > self.*getCCParams()* > File > "/home/juyoung/research/simulators/gem5-dev/gem5/src/python/m5/SimObject.py", > line 994, in getCCParams > *setattr(cc_params, param, value)* > SystemError: NULL result without error in PyObject_Call > Segmentation fault > > > I am not sure but it seems to have a problem in setting C++ object's > attribute. > Even if I found some port-related issues posted by Pavan Poluri from old > mailing archive, this problem is likely related to more recent changes in > either Ruby, Garnet, or both. > Could you give me a hint how I can resolve the problem? > Thanks. > > > Regards, > > > Juyoung > > > -- ------------------------------------------------------------------------------------
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
