You should be able to move that around any other patches ahead of it, right? It's so simple I wouldn't expect it to really depend on the intervening patches.
Gabe Beckmann, Brad wrote: > Hi Nilay, > > Yes, I am aware of this problem and one of the patches > (http://reviews.m5sim.org/r/381/) I'm planning to check in does fix this. > Unfortunately, those patches are being hung up because I need to do some more > work on another one of them and right now I don't have any time to do so. > As you can see from the patch, it is a very simple fix, so you may want to do > it locally if it blocking you. > > Brad > > > >> -----Original Message----- >> From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] >> On Behalf Of Nilay Vaish >> Sent: Thursday, January 20, 2011 6:16 AM >> To: m5-dev@m5sim.org >> Subject: [m5-dev] Error in Simulating Mesh Network >> >> Brad, I tried simulating a mesh network with four processors. >> >> ./build/ALPHA_FS_MOESI_hammer/m5.prof ./configs/example/ruby_fs.py - >> -maxtick 200000000000 -n 4 --topology Mesh --mesh-rows 2 --num-l2cache 4 >> --num-dir 4 >> >> I receive the following error: >> >> panic: FIFO ordering violated: [MessageBuffer: consumer-yes [ [71227521, >> 870, 1; ] ]] [Version 1, L1Cache, triggerQueue_in] >> name: [Version 1, L1Cache, triggerQueue_in] current time: 71227512 delta: >> 1 arrival_time: 71227513 last arrival_time: 71227521 >> @ cycle 35613756000 >> [enqueue:build/ALPHA_FS_MOESI_hammer/mem/ruby/buffers/MessageB >> uffer.cc, >> line 198] >> >> Do you think that the options I have specified should work correctly? >> >> Thanks >> Nilay >> _______________________________________________ >> m5-dev mailing list >> m5-dev@m5sim.org >> http://m5sim.org/mailman/listinfo/m5-dev >> > > > _______________________________________________ > m5-dev mailing list > m5-dev@m5sim.org > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
