Mailing List Archive

Automotive Grade Linux over xen issues.
Hi,

Myself Arun working as a lead engineer at pathpartner technologies.
Currently i am working on odroid xu4 with xen. I am trying to install
Automotive Grade Linux (AGL) on odroid xu4 as dom0.
AGL has a kernel version of 4.19 and which is ported to the odroid xu4 and
booted successfully.But while trying to run it over xen it shows error "d0v0:
vGICD: unhandled word write 0xffffffff to ICACTIVER4". Then I tried
lowering the kernel versions to 3.10 which has xen odroid support but has
some issues with the AGL filesystem. tuning the AGL fs i am able to reach
at login prompt but failed to login successfully.
My xen version is 4.6. .

Can you please suggest a solution to overcome this issue.

--
*Thanks and Regards*
Arun K
Lead Engineer
Pathpartner

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.
Re: Automotive Grade Linux over xen issues. [ In reply to ]
Hi Arun,

> On 11 May 2020, at 05:55, Arun K <arun.k@pathpartnertech.com> wrote:
>
> Hi,
>
> Myself Arun working as a lead engineer at pathpartner technologies.
> Currently i am working on odroid xu4 with xen. I am trying to install Automotive Grade Linux (AGL) on odroid xu4 as dom0.
> AGL has a kernel version of 4.19 and which is ported to the odroid xu4 and booted successfully.But while trying to run it over xen it shows error "d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER4". Then I tried lowering the kernel versions to 3.10 which has xen odroid support but has some issues with the AGL filesystem. tuning the AGL fs i am able to reach at login prompt but failed to login successfully.

This is a warning that you can ignore.

> My xen version is 4.6. .

I would highly suggest to upgrade to a newer version of Xen.

>
> Can you please suggest a solution to overcome this issue.

The message is in fact a warning that some register accessed by Linux is not properly emulated by Xen.
In your version of Linux the register is not used by Linux out of boot phase so you can safely ignore the warning.

Regards
Bertrand

>
> --
> Thanks and Regards
> Arun K
> Lead Engineer
> Pathpartner
>
> This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.
>

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.
Re: Automotive Grade Linux over xen issues. [ In reply to ]
Hi Arun,
(Putting back Xen-users in destination)

> On 18 May 2020, at 15:36, Arun K <arun.k@pathpartnertech.com> wrote:
>
> Hi Bertrand,
> I have modified the xen source and turned the "unhandled word write" into a write_ignore.
> Now ICACTIVER4 error is not coming but it shows another error
>
> (XEN) d0v0: vGICD: unhandled write r4=ffffffff offset 0x000384
> (XEN) traps.c:2449:d0v0 HSR=0x93840047 pc=0xc05fa49c gva=0xf0800384 gpa=0x00000010481384.
>
> Able to bring up the CPU successfully. but hangs here.
>

You need to switch to a newer Xen version, 4.6 if far to old to be able to support you.
Also please stick with linux 4.19, Linux 3.10 is very very old

On my test I have xen master (but same is produced with 4.12) and Linux 5.4 (but also tested with 4.19) and I see the warning but I boot properly:

[ 33.065195] xenbr0: port 2(vif1.0) entered blocking state
[ 33.070503] xenbr0: port 2(vif1.0) entered disabled state
[ 33.076015] device vif1.0 entered promiscuous mode
root@n1sdp:~# (XEN) d1v0: vGICR: SGI: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d1v1: vGICR: SGI: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d1v2: vGICR: SGI: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d1v3: vGICR: SGI: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) grant_table.c:1801:d1v1 Expanding d1 grant table from 1 to 2 frames
(XEN) grant_table.c:1801:d1v1 Expanding d1 grant table from 2 to 3 frames
(XEN) grant_table.c:1801:d1v1 Expanding d1 grant table from 3 to 4 frames
(XEN) grant_table.c:1801:d1v1 Expanding d1 grant table from 4 to 5 frames
[ 34.646998] vif vif-1-0 vif1.0: Guest Rx ready
[ 34.651356] IPv6: ADDRCONF(NETDEV_CHANGE): vi
f1.0: link becomroot@n1sdp:~# es ready
[ 34.659358] xenbr0: port 2(vif1.0) entered blocking state
[ 34.664793] xenbr0: port 2(vif1.0) entered forwarding state
(XEN) gnttab_mark_dirty not implemented yet

root@n1sdp:~# xl console stresstest
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd0c0]
[ 0.000000] Linux version 5.4.0-yocto-standard (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Thu Mar 12 05:30:37 UTC 2020
[ 0.000000] Machine model: XENVM-4.14
[ 0.000000] Xen 4.14 support found
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 32 MiB at 0x00000000fdc00000
[ 0.000000] NUMA: No NUMA configuration found
[ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000003bfffffff]
[ 0.000000] NUMA: NODE_DATA [mem 0x3bebf2100-0x3bebf3fff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA32 [mem 0x0000000040000000-0x00000000ffffffff]
[ 0.000000] Normal [mem 0x0000000100000000-0x00000003bfffffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040000000-0x00000000ffffffff]
[ 0.000000] node 0: [mem 0x0000000200000000-0x00000003bfffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000003bfffffff]
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: Trusted OS migration not required
[ 0.000000] psci: SMC Calling Convention v1.1


Bertrand

>
>
>
>
> On Mon, May 18, 2020 at 1:09 PM Bertrand Marquis <Bertrand.Marquis@arm.com> wrote:
> Hi Arun,
>
> > On 11 May 2020, at 05:55, Arun K <arun.k@pathpartnertech.com> wrote:
> >
> > Hi,
> >
> > Myself Arun working as a lead engineer at pathpartner technologies.
> > Currently i am working on odroid xu4 with xen. I am trying to install Automotive Grade Linux (AGL) on odroid xu4 as dom0.
> > AGL has a kernel version of 4.19 and which is ported to the odroid xu4 and booted successfully.But while trying to run it over xen it shows error "d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER4". Then I tried lowering the kernel versions to 3.10 which has xen odroid support but has some issues with the AGL filesystem. tuning the AGL fs i am able to reach at login prompt but failed to login successfully.
>
> This is a warning that you can ignore.
>
> > My xen version is 4.6. .
>
> I would highly suggest to upgrade to a newer version of Xen.
>
> >
> > Can you please suggest a solution to overcome this issue.
>
> The message is in fact a warning that some register accessed by Linux is not properly emulated by Xen.
> In your version of Linux the register is not used by Linux out of boot phase so you can safely ignore the warning.
>
> Regards
> Bertrand
>
> >
> > --
> > Thanks and Regards
> > Arun K
> > Lead Engineer
> > Pathpartner
> >
> > This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.
> >
>
> 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.
>
>
> --
> Thanks and Regards
> Arun K
> Lead Engineer
> Pathpartner
>
> This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.
>