I have successfully run PARSEC with this setup:
https://github.com/cirosantilli/linux-kernel-module-cheat/tree/29908dffb2726b0819fdf95240ae513dddb8af48#parsec-benchmark
and never encountered those problems.

Please also provide more detailed reproduction steps if you can.

On Fri, Mar 23, 2018 at 1:45 PM, Timon Evenblij
<[email protected]> wrote:
> Hi all,
>
> I have some issues regarding full-system simulation. I want to add some
> benchmarks to an image file so I can run them. I can resize an image file,
> mount it, add (cross)compiled benchmarks to it, e.g. parsec without
> problems. But when I boot gem5 on that disk image, trying to run a benchmark
> always result in some error that the inode/file cannot be read. Even a
> simple ls is a problem:
>
>
>
> root@gem5sim:/home/root/parsec-3.0# ll
> [    3.367737] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=430081, block=6881283
> ls: cannot access CONTRIBUTORS: Input/output error
> [    3.368723] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=430082, block=6881283
> ls: cannot access ext: Input/output error
> [    3.368878] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=430270, block=6881330
> ls: cannot access .parsec_uniquefile: Input/output error
> [    3.369019] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=434783, block=6955034
> ls: cannot access config: Input/output error
> [    3.369156] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=430271, block=6881330
> ls: cannot access LICENSE: Input/output error
> [    3.369297] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=435201, block=6963203
> ls: cannot access bin: Input/output error
> [    3.369434] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=430272, block=6881330
> ls: cannot access README: Input/output error
> [    3.369571] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=430273, block=6881331
> ls: cannot access CHANGELOG: Input/output error
> [    3.369709] EXT2-fs (vda1): error: ext2_get_inode: unable to read inode
> block - inode=430274, block=6881331
> ls: cannot access env.sh: Input/output error
>
> I tried changing permissions when copying the files, but that didn't work.
> Has anyone encountered a similar error and has some insight to share?
> Perhaps it is related to resizing the image and the partition in it, but I'm
> not sure.
>
> Best regards
>
> Timon
>
>
> _______________________________________________
> 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

Reply via email to