Hi everyone,

I have been using ARM FS mode of Gem5 recently, and I can boot the system 
successfully.However, when I run my benchmark, I encounter segmentation faults. 
Do you know what's going on?

My gem5 verison is 20.1.0.0 .

I compiled kernel,dtb file and bootloader following the tutorial of this 
website: 
http://www.gem5.org/documentation/general_docs/fullsystem/building_arm_kernel . 
And I download image from: 
http://dist.gem5.org/dist/current/arm/disks/linaro-minimal-aarch64.img.bz2

What I'm curious about here is that I set the number of cpus when I was running 
FS mode to be three, but why did the program only recognize one ?

I can run this benchmark successfully in SE mode, so I think the benchmark 
should be fine. I guess maybe the kernel, image or parameters I used are wrong.

I'm looking forward to your help! Thank you in advance !

The following are some message of gem5 during operation.

1086032148000: system.terminal: attach terminal 0
gem5 has encountered a segmentation fault!

--- BEGIN LIBC BACKTRACE ---
build/ARM_MESI_Three_Level_HTM/gem5.opt(_Z15print_backtracev+0x30)[0x5613bc840440]
build/ARM_MESI_Three_Level_HTM/gem5.opt(+0x159d7e5)[0x5613bc8547e5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7fae9bf593c0]
build/ARM_MESI_Three_Level_HTM/gem5.opt(_ZN15TimingSimpleCPU14completeIfetchEP6Packet+0x157)[0x5613bd789fb7]
build/ARM_MESI_Three_Level_HTM/gem5.opt(_ZN10EventQueue10serviceOneEv+0x13d)[0x5613bc84853d]
build/ARM_MESI_Three_Level_HTM/gem5.opt(_Z9doSimLoopP10EventQueue+0xf8)[0x5613bc869d68]
build/ARM_MESI_Three_Level_HTM/gem5.opt(_Z8simulatem+0xaed)[0x5613bc86ab5d]
build/ARM_MESI_Three_Level_HTM/gem5.opt(+0x14adf80)[0x5613bc764f80]
build/ARM_MESI_Three_Level_HTM/gem5.opt(+0xe5f8f7)[0x5613bc1168f7]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6372)[0x7fae9c07bff2]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7f8)[0x7fae9c075628]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6f81)[0x7fae9c07cc01]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7f8)[0x7fae9c075628]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6f81)[0x7fae9c07cc01]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7f8)[0x7fae9c075628]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6f81)[0x7fae9c07cc01]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7f8)[0x7fae9c075628]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7fae9c075b39]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6e76)[0x7fae9c07caf6]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7f8)[0x7fae9c075628]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6f81)[0x7fae9c07cc01]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7f8)[0x7fae9c075628]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7fae9c075b39]
/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76)[0x7fae9c04e846]
build/ARM_MESI_Three_Level_HTM/gem5.opt(_Z6m5MainiPPc+0x8b)[0x5613bc85275b]
build/ARM_MESI_Three_Level_HTM/gem5.opt(main+0x4c)[0x5613bbea522c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7fae9b5160b3]
build/ARM_MESI_Three_Level_HTM/gem5.opt(_start+0x2e)[0x5613bbed639e]
--- END LIBC BACKTRACE ---
./run-this.sh: line 28:     7 Segmentation fault     
 (core dumped) build/ARM_MESI_Three_Level_HTM/gem5.opt configs/example/fs.py 
--ruby --num-cpus=3 \
 --cpu-type=TimingSimpleCPU --kernel=../system/vmlinux 
--machine-type=VExpress_GEM5_V1 \
 --dtb-file=./system/arm/dt/armv8_gem5_v1_1cpu.dtb 
--disk-image=linaro-minimal-aarch64.img \
 --bootloader=./system/arm/bootloader/arm64/boot_v2.arm64
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to