Hi Have you modified the code in a way to create new addresses? You should note that the unmapped address is in the range of 4GB< < 8GB. If you increase the memory to 8GB, that specific address will be resolved but you may see another error for addresses larger than 8GB!!
Hope that helps On 2/18/14, Siddharth Nilakantan <sn...@drexel.edu> wrote: > Hi All, > > I'm using Gem5's SE mode with Splash-2 compiled for m5threads. When running > the Cholesky, water-spatial and ocean benchmarks I noticed the "panic: > Tried to read unmapped address" error. Based on previous questions of the > same type, I made sure to try testing the executables under Valgrind. There > are no memory leaks, so I'm not sure what is happening. > > build/X86_MESI_CMP_directory/gem5.opt configs/example/se.py > --garnet-network=fixed --topology=Mesh --ruby > --cmd=~/benchmarks/splash2_gem5se/splash2/codes/kernels/cholesky/CHOLESKY > --options="-p8 > ~/benchmarks/splash2_gem5se/splash2/codes/kernels/cholesky/inputs/tk23.O" > --num-cpus=8 --num-dirs=8 --num-l2caches=8 --l1d_size=64kB --l1d_assoc=4 > --l1i_size=64kB --l1i_assoc=4 --l2_size=4096kB --l2_assoc=8 > . > . > . > > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(0, 7020308, ...) > warn: ignoring syscall futex(1, 7020308, ...) > warn: ignoring syscall futex(1, 7020308, ...) > *panic: Tried to read unmapped address 0x140495a85.* > @ cycle 143932527000 > [invoke:build/X86_MESI_CMP_directory/arch/x86/faults.cc, line 160] > Memory Usage: 4599016 KBytes > Program aborted at cycle 143932527000 > > The system is configured to have 4GB of Physical memory and the memory > usage is still higher. It always dies at the same address and the same > cycle number. > > Can anyone help me figure out why this is happening? What flags should I > turn on to get more useful information? > > Regards, > Sid > -- Regards, Mahmood _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
