[gem5-users] Page table fault when accessing virtual address 0x7ffffffe00
Hi All,
I am trying to run a basic program of memcpy for which I am seeing the
following error.
"build/ARM/sim/faults.cc:104: panic: panic condition !handled &&
!tc->getSystemPtr()->trapToGdb(SIGSEGV, tc->contextId()) occurred: Page
table fault when accessing virtual address 0x7ffe00"
Below is the program that was cross compiled (I used -static flag when
compiling):
*void memCpy(void *d, void *s, size_t n){char *csrc = (char *)s;
char *cdest = (char *)d;for(int i=0; i___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
[gem5-users] Page Table Fault When Accessing Virtual Address
Hi all, I am trying to run a simulation with se.py. It works perfectly fine on my machine but when I try to run it on a workstation I am getting this error: panic: Page table fault when accessing virtual address 0x7f8ff900 I am using RISCV isa and the latest version of gem5. This is the command that I use: gem5/build/RISCV/gem5.opt gem5/configs/example/se.py -c pr -o '-g 12' --caches --l1d_size=2kB --l1i_size=2kB --cpu-type=DerivO3CPU -n 4 --mem-size=512MB --l2cache --l2_size=4kB This is the gdb report: [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". command line: gem5/build/RISCV/gem5.debug --debug-break=2000 configs/example/se.py -c gem5/gapbs/pr -o '-g 16' --caches --l1d_size=2kB --l1i_size=2kB --cpu-type=DerivO3CPU -n 4 --mem-size=512MB --l2cache --l2_size=256kB warn: need to stop all queues Global frequency set at 1 ticks per second warn: failed to generate dot output from m5out/config.dot warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (512 Mbytes) 0: system.remote_gdb: listening for remote gdb on port 7001 0: system.remote_gdb: listening for remote gdb on port 7002 0: system.remote_gdb: listening for remote gdb on port 7003 0: system.remote_gdb: listening for remote gdb on port 7004 REAL SIMULATION info: Entering event queue @ 0. Starting simulation... Program received signal SIGTRAP, Trace/breakpoint trap. 0x762f1187 in kill () at ../sysdeps/unix/syscall-template.S:78 78 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) c Continuing. panic: Page table fault when accessing virtual address 0x7f8ff900 Memory Usage: 705620 KBytes Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) c Continuing. Program aborted at tick 183884000 --- BEGIN LIBC BACKTRACE --- gem5/build/RISCV/gem5.debug(_Z15print_backtracev+0x2e)[0x564a203a] gem5/build/RISCV/gem5.debug(_Z12abortHandleri+0x71)[0x564b3e98] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7764b890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x762f0e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x762f2801] gem5/build/RISCV/gem5.debug(_ZN5Stats10InfoAccessC1Ev+0x0)[0x560b9b22] gem5/build/RISCV/gem5.debug(_ZN21GenericPageTableFault6invokeEP13ThreadContextRK14RefCountingPtrI10StaticInstE+0xc8)[0x564d8ee2] gem5/build/RISCV/gem5.debug(_ZN9FullO3CPUI9O3CPUImplE4trapERKSt10shared_ptrI9FaultBaseEsRK14RefCountingPtrI10StaticInstE+0x61)[0x56626f0f] gem5/build/RISCV/gem5.debug(_ZN13DefaultCommitI9O3CPUImplE10commitHeadERK14RefCountingPtrI13BaseO3DynInstIS0_EEj+0xa9a)[0x56615ea0] gem5/build/RISCV/gem5.debug(_ZN13DefaultCommitI9O3CPUImplE11commitInstsEv+0x4cf)[0x56614769] gem5/build/RISCV/gem5.debug(_ZN13DefaultCommitI9O3CPUImplE6commitEv+0xb9f)[0x5661240d] gem5/build/RISCV/gem5.debug(_ZN13DefaultCommitI9O3CPUImplE4tickEv+0x295)[0x56611165] gem5/build/RISCV/gem5.debug(_ZN9FullO3CPUI9O3CPUImplE4tickEv+0x1a7)[0x56623c57] gem5/build/RISCV/gem5.debug(_ZZN9FullO3CPUI9O3CPUImplEC4EP16DerivO3CPUParamsENKUlvE_clEv+0x1b)[0x5662a4e9] gem5/build/RISCV/gem5.debug(_ZNSt17_Function_handlerIFvvEZN9FullO3CPUI9O3CPUImplEC4EP16DerivO3CPUParamsEUlvE_E9_M_invokeERKSt9_Any_data+0x20)[0x5662f15a] gem5/build/RISCV/gem5.debug(_ZNKSt8functionIFvvEEclEv+0x32)[0x561fb28a] gem5/build/RISCV/gem5.debug(_ZN20EventFunctionWrapper7processEv+0x1c)[0x561fa9aa] gem5/build/RISCV/gem5.debug(_ZN10EventQueue10serviceOneEv+0xe9)[0x564b0d77] gem5/build/RISCV/gem5.debug(_Z9doSimLoopP10EventQueue+0x20e)[0x564bbaf2] gem5/build/RISCV/gem5.debug(_Z8simulatem+0x339)[0x564bb71d] gem5/build/RISCV/gem5.debug(+0xf13828)[0x56467828] gem5/build/RISCV/gem5.debug(+0xf11834)[0x56465834] gem5/build/RISCV/gem5.debug(+0xf0e0eb)[0x564620eb] gem5/build/RISCV/gem5.debug(+0xf0e152)[0x56462152] gem5/build/RISCV/gem5.debug(+0xd2a7de)[0x5627e7de] /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5f82)[0x77905522] /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x77a37bf8] /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x77905904] /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x77a37bf8] /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x77905904] /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x77a37bf8] /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x77905904] --- END LIBC BACKTRACE --- Program received signal SIGABRT, Aborted. __pthread_kill (threadid=, signo=6) at ../sysdeps/unix/sysv/linux/pthread_kill.c:57 57 ../sysdeps/unix/sysv/linux/pthread_kill.c: No such file or directory. I don't really understand why it works on my
Re: [gem5-users] Page table fault when accessing virtual address 0x98
Thanks for the reply. But I don't know how to get to the trace around the warning lines. (only the terminated tick printed) How to find the tick at which warning appears? jiakunli2010，jiakunli2...@gmail.com 2014/5/8 ___ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
Re: [gem5-users] Page table fault when accessing virtual address 0x98
--debug-flags=Exec --debug-start=some number of ticks before crashes Ali On 08.05.2014 02:13, jiakunli2010 via gem5-users wrote: Thanks for the reply. But I don't know how to get to the trace around the warning lines. (only the terminated tick printed) How to find the tick at which warning appears? jiakunli2010，jiakunli2...@gmail.com 2014/5/8 ___ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users [1] Links: -- [1] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users ___ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
[gem5-users] Page table fault when accessing virtual address 0x98
Hello All! I am running SPEC2006 (4 workloads on 4-core) using gem5 classic memory, timing cpu model. The error message are pasted below. However, when I applied one workload to the same 4-core system, I got no errors for any of the four workloads. The system could also run some other mixes of SPEC2006 workloads and the Hello world! example. I searched the debug file but did not find any clues. I made considerable modification to the source code of cache system, I suppose it was bugs there. Does anyone have any idea about where the errors may come from or any suggestion on the debugging method? info: Increaseing stack size by one page. info: Increaseing stack size by one page. Warning line 7126: Column C918 for row R10193 ignored Warning line 7189: Column C932 for row 1. ignored Warning line 7834: Column C1084 for row 8 ignored info: Increaseing stack size by one page. Warning line 8824: Column C1306 for row 1. ignored Warning line 8827: Column C1306 for row 0 ignored Syntax error in line 8829 panic: Page table fault when accessing virtual address 0x98 @ cycle 32812561593 [invoke: build/ARM/sim/faults.cc, line 70] Memory Usage: 2884000 KBytes jiakunli2010，jiakunli2...@gmail.com 2014/5/7 ___ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
Re: [gem5-users] Page table fault when accessing virtual address 0x98
The page fault you're seeing below is what you would see on a normal system as a segmentation fault. You're likely referencing a null pointer plus some offset. You need to look at a trace of the instructions and memory system, see how that address is generated and assuming it's the problem I mentioned, why a previous write disappeared or got lost in your cache modifications. Thanks, Ali On 07.05.2014 09:27, jiakunli2010 via gem5-users wrote: Hello All! I am running SPEC2006 (4 workloads on 4-core) using gem5 classic memory, timing cpu model. The error message are pasted below. However, when I applied one workload to the same 4-core system, I got no errors for any of the four workloads. The system could also run some other mixes of SPEC2006 workloads and the Hello world! example. I searched the debug file but did not find any clues. I made considerable modification to the source code of cache system, I suppose it was bugs there. Does anyone have any idea about where the errors may come from or any suggestion on the debugging method? info: Increaseing stack size by one page. info: Increaseing stack size by one page. Warning line 7126: Column C918 for row R10193 ignored Warning line 7189: Column C932 for row 1. ignored Warning line 7834: Column C1084 for row 8 ignored info: Increaseing stack size by one page. Warning line 8824: Column C1306 for row 1. ignored Warning line 8827: Column C1306 for row 0 ignored Syntax error in line 8829 panic: Page table fault when accessing virtual address 0x98 @ cycle 32812561593 [invoke: build/ARM/sim/faults.cc, line 70] Memory Usage: 2884000 KBytes jiakunli2010，jiakunli2...@gmail.com 2014/5/7 ___ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users [1] Links: -- [1] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users ___ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
