Re: [gem5-users] fs.py --generate-dtb Linux kernel boot simulation fails for aarch64 with "Exiting @ tick because simulate() limit reached"

2018-05-17 Thread Ciro Santilli
Sorry, copy pasted wrong error message above, here is the right one:

```
 REAL SIMULATION 
warn: Existing EnergyCtrl, but no enabled DVFSHandler found.
info: Entering event queue @ 0.  Starting simulation...
warn: SCReg: Access to unknown device dcc0:site0:pos0:fn7:dev0
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
Exiting @ tick 18446744073709551615 because simulate() limit reached
```

On Thu, May 17, 2018 at 3:34 PM, Ciro Santilli  wrote:
> https://github.com/cirosantilli-work/gem5-issues/issues/18
>
> I had both aarch64 and arm working with --dtb-file using:
> https://github.com/cirosantilli/linux-kernel-module-cheat/tree/0678bd82ac61f0decce3480fef798bd5edbfd0c3#gem5
>
> But now I've learnt about the awesome --generate-dtb option, which
> would make my setup simpler, and I'd like to use it.
>
> If I replace my --dtb-file with --generate-dtb on an arm simulation,
> it all worked fine and Linux booted.
>
> However, for a very analogous boot of aarch64 nothing shows on the
> terminal and gem5 exits with an error.
>
> gem5 revision: 49f96e7b77925837aa5bc84d4c3453ab5f07408e (current master)
>
> full gem5 command line:
>
> ```
> M5_PATH='/work/linux-kernel-module-cheat/out/common/gem5/system' \
>  '/work/linux-kernel-module-cheat/out/common/gem5/build/ARM/gem5.opt' \
> --debug-file=trace.txt \
>  -d '/work/linux-kernel-module-cheat/out/aarch64/gem5/m5out' \
> '/work/linux-kernel-module-cheat/gem5/gem5/configs/example/fs.py' \
> --disk-image='/work/linux-kernel-module-cheat/out/aarch64/buildroot/images/rootfs.ext2'
> \
> --kernel='/work/linux-kernel-module-cheat/out/aarch64/buildroot/build/linux-custom/vmlinux'
> \
> --mem-size='256MB' \
> --num-cpus='1' \
> --script='/work/linux-kernel-module-cheat/data/readfile' \
>  --command-line='earlyprintk=pl011,0x1c09 console=ttyAMA0
> lpj=19988480 rw loglevel=8 mem=256MB root=/dev/sda
> console_msg_format=syslog nokaslr norandmaps printk.devkmsg=on
> printk.time=y' \
> --generate-dtb \
> --machine-type=VExpress_GEM5_V1 \
> ```
>
> It boots correctly however I use instead of --generate-dtb:
>
> ```
> --dtb-file='/work/linux-kernel-module-cheat/out/common/gem5/system/arm/dt/armv8_gem5_v1_1cpu.dtb'
> \
> ```
>
> Error message:
>
> ```
>  REAL SIMULATION 
>│<6>[0.226602] ata1.00: 1048576
> sectors, multi 0: LBA
> warn: Existing EnergyCtrl, but no enabled DVFSHandler found.
>│<6>[0.226628] ata1.00:
> configured for UDMA/33
> info: Entering event queue @ 0.  Starting simulation...
>│<5>[0.226686] scsi 0:0:0:0:
> Direct-Access ATA  M5 IDE Disk  n/a  PQ: 0 ANSI: 5
> warn: SCReg: Access to unknown device dcc0:site0:pos0:fn7:dev0
>│<5>[0.226844] sd 0:0:0:0:
> Attached scsi generic sg0 type 0
> warn: Tried to read RealView I/O at offset 0x60 that doesn't exist
>│<5>[0.226937] sd 0:0:0:0:
> [sda] 1048576 512-byte logical blocks: (537 MB/512 MiB)
> warn: Tried to read RealView I/O at offset 0x48 that doesn't exist
>│<5>[0.226952] sd 0:0:0:0:
> [sda] Write Protect is off
> warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
>│<7>[0.226959] sd 0:0:0:0:
> [sda] Mode Sense: 00 3a 00 00
> warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
>│<5>[0.226983] sd 0:0:0:0:
> [sda] Write cache: disabled, read cache: enabled, doesn't support DPO
> or FU
> warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
>│A
> warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
>│<5>[0.227343] sd 0:0:0:0:
> [sda] Attached SCSI disk
> warn: Tried to read RealView I/O at offset 0x8 that doesn't exist
>│<3>[0.227397] EXT4-fs (sda):
> couldn't mount as ext3 due to feature incompatibilities
> warn: Tried to read RealView I/O at offset 0x48 that doesn't exist
>│<6>[0.227441] EXT4-fs (sda):
> mounting ext2 file system using the ext4 subsystem
> c ^CExiting @ tick 261128433047797500 because user interrupt received
> ```
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

[gem5-users] fs.py --generate-dtb Linux kernel boot simulation fails for aarch64 with "Exiting @ tick because simulate() limit reached"

2018-05-17 Thread Ciro Santilli
https://github.com/cirosantilli-work/gem5-issues/issues/18

I had both aarch64 and arm working with --dtb-file using:
https://github.com/cirosantilli/linux-kernel-module-cheat/tree/0678bd82ac61f0decce3480fef798bd5edbfd0c3#gem5

But now I've learnt about the awesome --generate-dtb option, which
would make my setup simpler, and I'd like to use it.

If I replace my --dtb-file with --generate-dtb on an arm simulation,
it all worked fine and Linux booted.

However, for a very analogous boot of aarch64 nothing shows on the
terminal and gem5 exits with an error.

gem5 revision: 49f96e7b77925837aa5bc84d4c3453ab5f07408e (current master)

full gem5 command line:

```
M5_PATH='/work/linux-kernel-module-cheat/out/common/gem5/system' \
 '/work/linux-kernel-module-cheat/out/common/gem5/build/ARM/gem5.opt' \
--debug-file=trace.txt \
 -d '/work/linux-kernel-module-cheat/out/aarch64/gem5/m5out' \
'/work/linux-kernel-module-cheat/gem5/gem5/configs/example/fs.py' \
--disk-image='/work/linux-kernel-module-cheat/out/aarch64/buildroot/images/rootfs.ext2'
\
--kernel='/work/linux-kernel-module-cheat/out/aarch64/buildroot/build/linux-custom/vmlinux'
\
--mem-size='256MB' \
--num-cpus='1' \
--script='/work/linux-kernel-module-cheat/data/readfile' \
 --command-line='earlyprintk=pl011,0x1c09 console=ttyAMA0
lpj=19988480 rw loglevel=8 mem=256MB root=/dev/sda
console_msg_format=syslog nokaslr norandmaps printk.devkmsg=on
printk.time=y' \
--generate-dtb \
--machine-type=VExpress_GEM5_V1 \
```

It boots correctly however I use instead of --generate-dtb:

```
--dtb-file='/work/linux-kernel-module-cheat/out/common/gem5/system/arm/dt/armv8_gem5_v1_1cpu.dtb'
\
```

Error message:

```
 REAL SIMULATION 
   │<6>[0.226602] ata1.00: 1048576
sectors, multi 0: LBA
warn: Existing EnergyCtrl, but no enabled DVFSHandler found.
   │<6>[0.226628] ata1.00:
configured for UDMA/33
info: Entering event queue @ 0.  Starting simulation...
   │<5>[0.226686] scsi 0:0:0:0:
Direct-Access ATA  M5 IDE Disk  n/a  PQ: 0 ANSI: 5
warn: SCReg: Access to unknown device dcc0:site0:pos0:fn7:dev0
   │<5>[0.226844] sd 0:0:0:0:
Attached scsi generic sg0 type 0
warn: Tried to read RealView I/O at offset 0x60 that doesn't exist
   │<5>[0.226937] sd 0:0:0:0:
[sda] 1048576 512-byte logical blocks: (537 MB/512 MiB)
warn: Tried to read RealView I/O at offset 0x48 that doesn't exist
   │<5>[0.226952] sd 0:0:0:0:
[sda] Write Protect is off
warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
   │<7>[0.226959] sd 0:0:0:0:
[sda] Mode Sense: 00 3a 00 00
warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
   │<5>[0.226983] sd 0:0:0:0:
[sda] Write cache: disabled, read cache: enabled, doesn't support DPO
or FU
warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
   │A
warn: Tried to write RVIO at offset 0xa8 (data 0) that doesn't exist
   │<5>[0.227343] sd 0:0:0:0:
[sda] Attached SCSI disk
warn: Tried to read RealView I/O at offset 0x8 that doesn't exist
   │<3>[0.227397] EXT4-fs (sda):
couldn't mount as ext3 due to feature incompatibilities
warn: Tried to read RealView I/O at offset 0x48 that doesn't exist
   │<6>[0.227441] EXT4-fs (sda):
mounting ext2 file system using the ext4 subsystem
c ^CExiting @ tick 261128433047797500 because user interrupt received
```
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users