1) I tried running the stable version of gem5. I used the latest ARM
images to see if full system simulation is happening. These images are
unmodified.
I use the following command -
/research/uthakker/gem5/gem5-stable/build/ARM/gem5.opt
configs/example/fs.py --caches --cpu-type=DerivO3CPU --num-cpus=1
/_--machine-type=VExpress_EMM64_////_--disk-image=/research/uthakker/gem5/arm_october_2014/disks/aarch64-ubuntu-trusty-headless.img_////_--kernel=vmlinux.aarch64.20140821
--dtb-filename=vexpress.aarch64.20140821.dtb_/ --mem-size=2GB
I get the following error while booting -
/fatal: Unable to find destination for addr 0x2f001002 on bus system.iobus
@ tick 12550512894000
[findPort:build/ARM/mem/bus.cc, line 353]
Last few lines of system.terminal are
[ 3.139624] pci 0000:00:10.0: reg 0x14: [io 0x0000-0x0003]
[ 3.139633] pci 0000:00:10.0: reg 0x18: [io 0x0000-0x0007]
[ 3.139643] pci 0000:00:10.0: reg 0x1c: [io 0x0000-0x0003]
[ 3.139652] pci 0000:00:10.0: reg 0x20: [io 0x0000-0x000f]
[ 3.139661] pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
[ 3.139695] pci_bus 0000:00: fixups for bus
[ 3.139703] pci_bus 0000:00: bus scan returning with max=00
[ 3.139713] pci 0000:00:00.0: calling quirk_e100_interrupt+0x0/0x1cc
[ 3.139729] pci 0000:00:00.0: fixup irq: got 33
[ 3.139737] pci 0000:00:00.0: assigning IRQ 33
[ 3.139746] pci 0000:00:10.0: fixup irq: got 34
[ 3.139753] pci 0000:00:10.0: assigning IRQ 34
[ 3.139762] pci 0000:00:00.0: BAR 0: assigned [mem 0x40000000-0x4001ffff]
[ 3.139773] pci 0000:00:00.0: BAR 6: assigned [mem
0x40020000-0x400207ff pref]
[ 3.139784] pci 0000:00:10.0: BAR 6: assigned [mem
0x40020800-0x40020fff pref]
[ 3.139795] pci 0000:00:10.0: BAR 4: assigned [io 0x1000-0x100f]
[ 3.139805] pci 0000:00:10.0: BAR 0: assigned [io 0x1010-0x1017]
[ 3.139815] pci 0000:00:10.0: BAR 2: assigned [io 0x1018-0x101f]
[ 3.139826] pci 0000:00:10.0: BAR 1: assigned [io 0x1020-0x1023]
[ 3.139836] pci 0000:00:10.0: BAR 3: assigned [io 0x1024-0x1027]
[ 3.140559] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 3.140871] ata_piix 0000:00:10.0: version 2.13
[ 3.140880] ata_piix 0000:00:10.0: enabling device (0000 -> 0001)
/_How do I start debugging this issue?
_//
2) I am also trying to debug the instruction count > 1500 error while
running the modified arm image on gem5-dev codebase.
This issue is also reached while the boot process is still on.
The gem5 codebase is the latest one.
I will try and see where the instructions are getting clogged and see if
I could debug this issue.
On 11/07/14 12:54, Ali Saidi wrote:
Are you using the latest gem5 code? How long does it take for you to
reach this issue?
The issue is that these instructions have been created, but they
haven't been deleted. This means that some resource in the pipeline is
holding a reference to the instruction and it's not being deleted, the
question is why and which resource. If you run the debug version of
gem5 you'll get a list of which instructions haven't been deleted and
then you can use those instruction serial numbers to see where they've
gone in the pipeline and how the got "lost."
Thanks,
Ali
On 06.11.2014 20:17, Urmish Ajit Thakker via gem5-users wrote:
Hi,
I was running the full system simulation for the newly released arm 64
kernel and image. While running the simulation I encountered the
following error -
gem5.opt: build/ARM/cpu/base_dyn_inst_impl.hh:123: void BaseDynInst<
<template-parameter-1-1> >::initVars() [with Impl = O3CPUImpl]:
Assertion `cpu->instcount <= 1500' failed.
The number of CPUs I use for simulation is only one (I use the dtb file
part of the download package).
I have seen some related issues on the gem5 mailing list but from what I
gathered they seem to be for multicore scenario.
This is the command that I give to run the simulation -
build/ARM/gem5.opt configs/example/fs.py --caches --cpu-type=DerivO3CPU
--num-cpus=1 --machine-type=VExpress_EMM64
--disk-image=/research/uthakker/gem5/arm_october_64/disks/arm_8gb
--kernel=vmlinux.aarch64.20140821
--dtb-filename=vexpress.aarch64.20140821.dtb
--script=/research/uthakker/gem5/gem5/configs/boot/openCV.rcs
Any pointers as to why is this happening or how should I start debugging
this isssue?
Regards,
Urmish
_______________________________________________
gem5-users mailing list
[email protected] <mailto:[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
