I just re-ran the ALPHA_FS O3 boot test with a 512kB L2 and it worked (the test of course failed, since the statistics change, but the simulated system booted fine).
Basically I made this change: diff --git a/tests/configs/tsunami-o3.py b/tests/configs/tsunami-o3.py --- a/tests/configs/tsunami-o3.py +++ b/tests/configs/tsunami-o3.py @@ -84,7 +84,7 @@ #connect up the l2 cache -system.l2c = L2(size='4MB', assoc=8) +system.l2c = L2(size='512kB', assoc=8) system.l2c.cpu_side = system.toL2Bus.port system.l2c.mem_side = system.membus.port then ran: scons build/ALPHA_FS/tests/opt/long/10.linux-boot/alpha/linux/tsunami-o3 and verified that the output in system.terminal matched the correct output, and that the simout and simerr output files didn't contain any errors. So I don't think the failure is due only to the cache size change. Steve On Mon, Jul 18, 2011 at 4:48 AM, Fabian Oboril <[email protected]> wrote: > Hi, > > when I use the actual version (the most recent unstable from today), > exactly the same error occurs! Can I upload somewhere my configuration > files? > > Best wishes > Fabian > > > Am 14.07.2011 16:19, schrieb Nilay: > > On Thu, July 14, 2011 8:02 am, Fabian Oboril wrote: >> >>> Hi guys, >>> >>> I have a problem with M5 and the FS mode with ALPHA. The version I am >>> using is based on a release in February which I modified for my own >>> purpose, so may be the problem I face is due to my additions. However, I >>> don't know this, I basically have no idea where the problem comes from, >>> right now. >>> >>> If I decrease the size of the L2-Cache (detailed mode with L1& >>> L2-Cache) from 2 MByte to 512 KByte I get an segmentation fault when >>> booting in FS mode. The last actions thereby are: >>> >>> init started: BusyBox v1.1.0 (2007.03.04-01:07+0000) multi-call binary >>> mounting filesystems... >>> >>> Has anyone seen such a behavior before or has an idea what my be the >>> root cause for the segmentation fault? With 2 MByte L2-Cache everything >>> is working fine... >>> >>> I do not expect booting of the operating system can be affected by the >> size of the cache. To figure out where the problem is, try booting with >> unmodified gem5 and 512kb of cache. >> >> -- >> Nilay >> >> ______________________________**_________________ >> gem5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/**mailman/listinfo/gem5-users<http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users> >> > ______________________________**_________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/**mailman/listinfo/gem5-users<http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users> >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
