Hi Pedro

> -----Original Message-----
> From: Pedro Becker via gem5-users <[email protected]>
> Sent: 22 March 2021 16:29
> To: [email protected]
> Cc: Pedro Becker <[email protected]>
> Subject: [gem5-users] Re: Cannot boot full-system aarch64
>
> Hi Giacomo,
>
> Just re-build gem5 from scratch (after `rm -rf` the build folder).
> Also, thanks for the info about the --bare-metal. I was posting for
> completeness, but won't use it any further.
>
> I've re-downloaded the guest binary. Executing:
>
> $  readelf -e -s $M5_PATH/binaries/vmlinux.arm64
>
> returns:
>
>
> ELF Header:
>   Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
>   Class:                             ELF64
>   Data:                              2's complement, little endian
>   Version:                           1 (current)
>   OS/ABI:                            UNIX - System V
>   ABI Version:                       0
>   Type:                              EXEC (Executable file)
>   Machine:                           AArch64
>   Version:                           0x1
>   Entry point address:               0xffffff8008080000
>   Start of program headers:          64 (bytes into file)
>   Start of section headers:          137210936 (bytes into file)
>   Flags:                             0x0
>   Size of this header:               64 (bytes)
>   Size of program headers:           56 (bytes)
>   Number of program headers:         4
>   Size of section headers:           64 (bytes)
>   Number of section headers:         36
>   Section header string table index: 35
> readelf: Error: Reading 2304 bytes extends past end of file for section
> headers
>
> Program Headers:
>   Type           Offset             VirtAddr           PhysAddr
>                  FileSiz            MemSiz              Flags  Align
>   LOAD           0x0000000000010000 0xffffff8008080000 0xffffff8008080000
>                  0x00000000006bb3e0 0x00000000006bb3e0  R E    0x10000
>   LOAD           0x00000000006d0000 0xffffff8008740000 0xffffff8008740000
>                  0x0000000000331008 0x00000000003674b0  RWE    0x10000
>   NOTE           0x0000000000914260 0xffffff8008984260 0xffffff8008984260
>                  0x0000000000000024 0x0000000000000024  R      0x4
>   GNU_STACK      0x0000000000000000 0x0000000000000000
> 0x0000000000000000
>                  0x0000000000000000 0x0000000000000000  RW     0x10
>
>
> Which seems to be a pretty short output compared to other files. Indeed,
> there are no symbols reported. But this happens for both downloaded
> kernels (downloaded now and before). Running this on gem5 does not
> change anything.
>
>
>
> So I went after a previous version of the pre-built kernels to see what their
> readelf output would be like. Downloaded
> http://dist.gem5.org/dist/current/arm/aarch-system-20180409.tar.xz
> because it seems to be of 2018, so not that old.
>
> readelf for one of the kernels in there (I ran over the
> vmlinux.vexpress_gem5_v1_64 file) shows a lot of symbols! So I though ok,
> let's try gem5 with that.
>
> changed the M5_PATH to this older guest binary folder
>    export M5_PATH=/home/pedro/Projects/gem5/fs_files/aarch-system-
> 20180409
>
> Ran gem5 again:
>   $ ./build/ARM/gem5.opt  configs/example/arm/starter_fs.py --kernel
> $M5_PATH/binaries/vmlinux.vexpress_emm64 --disk-image
> /home/pedro/Projects/gem5/fs_files/ubuntu-18.04-arm64-docker.img --
> root /dev/vda
>

Unrelated, could you use vmlinux.vexpress_gem5_v1_64 instead?

>
> So two main things:
>
> 1) Could the most up-to-date kernel in the website be broken
> (http://dist.gem5.org/dist/current/arm/aarch-system-201901106.tar.bz2)? I
> had problematic readelf outputs after two different download attempts.
>

I am actually tempted to say the problem is in your binutils; consider that we 
use that kernel image in our CI system to run Arm regressions; the image has 
been staying there
For a while and this is the first time AFAIK a user is reporting such a problem.

Or at least there are some incompatibilities between the prebuilt kernel and 
your binutils. What's your readelf version?

($readelf -v)

> 2) Let's say it works (or I stick with the older, working version). There is 
> also a
> panic with the "root" option. I am using the one you told me, but panic'd
> when trying to show me the available partitions.
> Could the image be corrupted as well? Or I'm just using a wrong parameter?
>

Apologies, remove the --root=/dev/vda option (or alternative, use /dev/vda1)

>
> Sorry for the very long response and thanks for the help.
>
> Pedro.
> _______________________________________________
> gem5-users mailing list -- [email protected] To unsubscribe send an
> email to gem5-users-
> [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Kind Regards

Giacomo
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to