gem5 arm starter_fs.py fails to boot aarch-system-20170616//disks/linaro-minimal-aarch64.img with "simulate() limit reached @ 18446744073709551615"

[damon-liush]

command line: ./build/ARM/gem5.opt configs/example/arm/starter_fs.py --cpu=minor --num-cores=1 --disk-image=/home/liush/wkplace/life/gem/aarch-system-20170616//disks/linaro-minimal-aarch64.img

Global frequency set at 1000000000000 ticks per second
warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (2048 Mbytes)
info: kernel located at: /home/liush/wkplace/life/gem/aarch-system-20170616/binaries/vmlinux.vexpress_gem5_v1_64.20170616
warn: Bootloader entry point 0x10 overriding reset address 0
warn: Highest ARM exception-level set to AArch32 but bootloader is for AArch64. Assuming you wanted these to match.
system.vncserver: Listening for connections on port 5900
system.terminal: Listening for connections on port 3456
0: system.remote_gdb: listening for remote gdb on port 7000
info: Using bootloader at address 0x10
info: Using kernel entry physical address at 0x80080000
info: Loading DTB file: /home/liush/wkplace/life/gem/gem5/m5out/system.dtb at address 0x88000000
warn: Existing EnergyCtrl, but no enabled DVFSHandler found.
info: Entering event queue @ 0. Starting simulation...
warn: ClockedObject: Already in the requested power state, request ignored
warn: SCReg: Access to unknown device dcc0:site0:pos0:fn7:dev0
3132832250: system.terminal: attach terminal 0

warn: Tried to read RealView I/O at offset 0x60 that doesn't exist
warn: Tried to read RealView I/O at offset 0x48 that doesn't exist
warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
simulate() limit reached @ 18446744073709551615

[cirosantilli2]

Thanks for the report Damon,

I'm not sure what happened there I'm afraid, would require some debugging, but I don't have time right now.

One thing you can try, is to use the fs.py setup described at: https://github.com/cirosantilli/linux-kernel-module-cheat/tree/4943c9ed2ed63856b461cf3d883c26bee0b36df6#gem5-buildroot-setup-getting-started with --arch aarch64. I have tested it and can guarantee it to work.

Then we can try to diff things up to understand the RVIO problem.