Andreas Hansson <Andreas.Hansson <at> arm.com> writes: > > > Hi Xing, > > I know what is causing the issue, and I’ll make sure it is fixed. As the patch is under review, the best way to feedback on the patch is through the review board (something to consider in the future). > > Thanks, > > Andreas > > > > From: Xing Niu <xniu7 <at> hawk.iit.edu>Reply-To: gem5 users mailing list <gem5-users <at> gem5.org>Date: Sunday, 1 December 2013 08:00To: gem5 users mailing list <gem5-users <at> gem5.org>Subject: [gem5-users] --mem- type=dramsim2 and checkpoint-restore=1 error (gem5+dramsim2) > > > > > > Hi all, > > I use --take-checkpoint to create the checkpoint and when I use checkpoint-restore=1 to re-run it, it works well. But my gem5 is integrated with the Dramsim2, so if I add the --mem-type=dramsim2 option with checkpoint-restore=1 option together, I got the > following error. > Anyone can give some advice? > > Listening for system connection on port 3456 > 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000 > 0: system.remote_gdb.listener: listening for remote gdb #1 on port 7001 > 0: system.remote_gdb.listener: listening for remote gdb #2 on port 7002 > 0: system.remote_gdb.listener: listening for remote gdb #3 on port 7003 > 0: system.remote_gdb.listener: listening for remote gdb #4 on port 7004 > 0: system.remote_gdb.listener: listening for remote gdb #5 on port 7005 > 0: system.remote_gdb.listener: listening for remote gdb #6 on port 7006 > 0: system.remote_gdb.listener: listening for remote gdb #7 on port 7007 > 0: system.remote_gdb.listener: listening for remote gdb #8 on port 7008 > 0: system.remote_gdb.listener: listening for remote gdb #9 on port 7009 > 0: system.remote_gdb.listener: listening for remote gdb #10 on port 7010 > 0: system.remote_gdb.listener: listening for remote gdb #11 on port 7011 > 0: system.remote_gdb.listener: listening for remote gdb #12 on port 7012 > 0: system.remote_gdb.listener: listening for remote gdb #13 on port 7013 > 0: system.remote_gdb.listener: listening for remote gdb #14 on port 7014 > 0: system.remote_gdb.listener: listening for remote gdb #15 on port 7015 > Switch at curTick count:10000 > info: Entering event queue <at> 10000. Starting simulation... > writing vis file to ext/dramsim2/DRAMSim2//results//DDR3_micron_32M_8B_x8_sg15/2 GB.1Ch.1R.scheme2.open_page.32TQ.32CQ.RtB.pRank.vis > Switched CPUS <at> tick 20000 > switching cpus > **** REAL SIMULATION **** > info: Entering event queue <at> 20000. Starting simulation... > m5.opt: build/ALPHA/mem/dramsim2.cc:291: void DRAMSim2::readComplete(unsigned in t, uint64_t, uint64_t): Assertion `cycle == divCeil(curTick(), wrapper.clockPeri > od() * SimClock::Int::ns)' failed. > Program aborted at cycle 134500 > > > thanks, > Xing > > > > -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents > to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. > ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 > ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782 > > > _______________________________________________ > gem5-users mailing list > gem5-users <at> gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
Hi Andreas, I also have the same problem. Can I know if the patch has been finished? Since I search the review board and use the latest dramsim2 patch but the problem still exist. Thanks _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
