Thanks. It works. On Tue, Oct 21, 2014 at 3:59 PM, Anthony Gutierrez via gem5-users < [email protected]> wrote:
> Because of some of the recent changes to aarch64 in gem5, you need to use > a newer kernel and dtb file. Instructions for how to obtain them are here: > > http://gem5.org/ARM_Linux_Kernel > > I think we will be releasing tarballs with newer kernels/images soon. > > > Anthony Gutierrez > http://web.eecs.umich.edu/~atgutier > > On Tue, Oct 21, 2014 at 3:29 PM, Meng Wang via gem5-users < > [email protected]> wrote: > >> Hello, >> I tried to run full system simulation for arm64 architecture. I used the >> latest gem5 simulator and downloaded prebuilt full system image from gem5 >> website. The command line I used is: >> >> $ ../gem5/build/ARM/gem5.opt ../gem5/configs/example/fs.py >> --machine-type=VExpress_EMM64 --kernel=vmlinux-3.14-aarch64-vexpress-emm64 >> --disk-image=linaro-minimal-armv8.img --dtb-filename=rtsm_ve-aemv8a.dtb >> ... >> Global frequency set at 1000000000000 ticks per second >> info: kernel located at: >> /home/wmeng/workspace/livesp/m5_images/binaries/vmlinux-3.14-aarch64-vexpress-emm64 >> warn: Highest ARM exception-level set to AArch32 but bootloader is for >> AArch64. Assuming you wanted these to match. >> Listening for system connection on port 5900 >> Listening for system connection on port 3456 >> 0: system.cpu.isa: ISA system set to: 0x4a0e540 0x4a0e540 >> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7001 >> info: Using bootloader at address 0x10 >> info: Using kernel entry physical address at 0x80080040 >> info: Loading DTB file: >> /home/wmeng/workspace/livesp/m5_images/binaries/rtsm_ve-aemv8a.dtb at >> address 0x88000000 >> **** REAL SIMULATION **** >> warn: Existing EnergyCtrl, but no enabled DVFSHandler found. >> info: Entering event queue @ 0. Starting simulation... >> warn: SCReg: Writing 0 to dcc0:site0:pos0:fn7:dev0 >> 4101426500: system.terminal: attach terminal 0 >> warn: Tried to read RealView I/O at offset 0x60 that doesn't exist >> warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist >> 10133760032500: system.cpu.break_event: break event panic triggered >> 10133760033000: system.cpu.break_event: break event panic triggered >> 10133760033500: system.cpu.break_event: break event panic triggered >> 10133760034000: system.cpu.break_event: break event panic triggered >> >> I set up the M5_PATH environment variable, and put the kernel and dtb >> files in <m5_path>/binaries/, put rootfs image file in <m5_path>/disks/. >> Thus I only specify file name instead of full path in command line. >> >> m5term shows the following error: >> ... >> [ 0.047510] TCP: cubic registered >> [ 0.047511] NET: Registered protocol family 17 >> [ 0.642521] input: AT Raw Set 2 keyboard as >> /devices/smb.2/motherboard.3/iofpga.7/1c060000.kmi/serio0/input/input0 >> [ 2.542532] input: PS/2 Generic Mouse as >> /devices/smb.2/motherboard.3/iofpga.7/1c070000.kmi/serio1/input/input2 >> [ 2.542570] VFS: Cannot open root device "sda1" or unknown-block(0,0): >> error -6 >> [ 2.542571] Please append a correct "root=" boot option; here are the >> available partitions: >> [ 2.542572] Kernel panic - not syncing: VFS: Unable to mount root fs >> on unknown-block(0,0) >> [ 2.542573] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.0-rc2+ #1 >> [ 2.542574] Call trace: >> [ 2.542575] [<ffffffc000087d5c>] dump_backtrace+0x0/0x12c >> [ 2.542576] [<ffffffc000087e9c>] show_stack+0x14/0x1c >> [ 2.542577] [<ffffffc0004943a0>] dump_stack+0x78/0xc4 >> [ 2.542578] [<ffffffc0004912dc>] panic+0xe8/0x208 >> [ 2.542579] [<ffffffc000645d68>] mount_block_root+0x1d8/0x278 >> [ 2.542580] [<ffffffc000645f20>] mount_root+0x118/0x134 >> [ 2.542582] [<ffffffc00064607c>] prepare_namespace+0x140/0x188 >> [ 2.542583] [<ffffffc0006459bc>] kernel_init_freeable+0x1b8/0x1d8 >> [ 2.542584] [<ffffffc00048f5b4>] kernel_init+0x10/0xd4 >> >> Kernel panics on VFS mounting. >> >> When I changed dtb file to either rtsm_ve-aemv8a-2core.dtb or >> rtsm_ve-aemv8a-4core.dtb, the kernel hangs after outputing following: >> >> ... >> [ 0.000000] Virtual kernel memory layout: >> [ 0.000000] vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 >> (245759 MB) >> [ 0.000000] vmemmap : 0xffffffbc01c00000 - 0xffffffbc02300000 ( >> 7 MB) >> [ 0.000000] modules : 0xffffffbffc000000 - 0xffffffc000000000 ( >> 64 MB) >> [ 0.000000] memory : 0xffffffc000000000 - 0xffffffc020000000 ( >> 512 MB) >> [ 0.000000] .init : 0xffffffc000645000 - 0xffffffc000687f40 ( >> 268 kB) >> [ 0.000000] .text : 0xffffffc000080000 - 0xffffffc000644104 ( >> 5905 kB) >> [ 0.000000] .data : 0xffffffc000688000 - 0xffffffc0006e3618 ( >> 366 kB) >> [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 >> [ 0.000000] Preemptible hierarchical RCU implementation. >> [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2. >> [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, >> nr_cpu_ids=2 >> [ 0.000000] NR_IRQS:64 nr_irqs:64 0 >> [ 0.000000] Architected cp15 timer(s) running at 100.00MHz (phys). >> [ 0.007706] sched_clock: 56 bits at 100MHz, resolution 10ns, wraps >> every 2748779069440ns >> [ 0.000012] Console: colour dummy device 80x25 >> [ 0.000013] Calibrating delay loop (skipped) preset value.. 3997.69 >> BogoMIPS (lpj=19988480) >> [ 0.000014] pid_max: default: 32768 minimum: 301 >> [ 0.000026] Mount-cache hash table entries: 256 >> [ 0.000086] hw perfevents: no hardware support available >> >> Could anyone help me? >> >> _______________________________________________ >> 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 >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
