OK I think I got what you said. However, I have to say that after about two hours, the simulation aborted with a panic related to VNC.
I have to say I didn't attach any vncviewer since the job was running in the background yesterday night. Have you seen that before? Global frequency set at 1000000000000 ticks per second warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (256 Mbytes) info: kernel located at: /home/mahmood/gem5/system/binaries/vmlinux.smp.mouse.arm Listening for system connection on port 5900 Listening for system connection on port 3456 0: system.remote_gdb.listener: listening for remote gdb on port 7000 info: Using bootloader at address 0x10 info: Using kernel entry physical address at 0x80008000 warn: DTB file specified, but no device tree support in kernel **** REAL SIMULATION **** warn: Existing EnergyCtrl, but no enabled DVFSHandler found. info: Entering event queue @ 0. Starting simulation... warn: Device system.membus.badaddr_responder accessed by write to address 0x10009000 size=1 data=0xa warn: Device system.membus.badaddr_responder accessed by read to address 0x10009018 size=4 warn: Device system.membus.badaddr_responder accessed by read to address 0x10009018 size=4 warn: Device system.membus.badaddr_responder accessed by write to address 0x10009000 size=1 data=0xd warn: Device system.membus.badaddr_responder accessed by read to address 0x10009018 size=4 info: VNC client attached warn: Malformed protocol version GET / HTTP/1 info: VNC client detached warn: Unsupported VNC client version... disconnecting panic: Vnc client not properly attached. @ tick 13301657326000 [write:build/ARM/base/vnc/vncserver.cc, line 331] Memory Usage: 531056 KBytes Program aborted at tick 13301657326000 --- BEGIN LIBC BACKTRACE --- build/ARM/gem5.fast(_Z15print_backtracev+0x1f)[0x11b2f2f] build/ARM/gem5.fast(_Z12abortHandleri+0x34)[0x11b3054] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f5a188e4cb0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f5a174110d5] /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7f5a1741483b] build/ARM/gem5.fast(_Z15__exit_epilogueiPKcS0_iS0_+0x2aa)[0x1319eda] build/ARM/gem5.fast(_Z22MachineType_base_countRK11MachineType+0x0)[0x1335e70] build/ARM/gem5.fast[0xa1ee20] build/ARM/gem5.fast[0x1769aff] build/ARM/gem5.fast(_ZN9VncServer9DataEvent7processEi+0x154)[0x176b174] build/ARM/gem5.fast(_Z9doSimLoopP10EventQueue+0x220)[0xf876d0] build/ARM/gem5.fast(_Z8simulatem+0x23f)[0x1612f6f] build/ARM/gem5.fast[0x1613d65] /usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x4f18)[0x7f5a184693b8] Regards, Mahmood On Sun, Dec 27, 2015 at 6:02 AM, Davesh Shingari <[email protected]> wrote: > Hi > > Which script are you using - bbench-ics.rcS? > You can see whether the checkpoint was created by checking the cpt created > and looking at the frame output to know whether bbench has started or not. > If you are using bbench-ics then it automatically creates a checkpoint and > then starts the bbench. So best way is to start the simulation in atomic > mode and then after checkpoint is created run the simulation in detailed > mode using the checkpoint created, if this is what you are looking for. > ᐧ > -- > Have a great day! > > Thanks and Warm Regards > Davesh Shingari > Master's in Computer Engineering [EE] > Arizona State University > > [email protected] > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
