Re: Observed AGL guest VM failure once migrated to xen 4.18 from 4.16

["Kumar1, Rahul via lists.automotivelinux.org" <Rahul.Kumar1=amd.com@xxxxxxxxxxxxxxxxxxxxxxxxx>]

[AMD Official Use Only - General]

Hi, 

Thanks for response, just update on this issue.
Upgrading mesa to 22.3.5 from poky master, resolves the issue.
So, for now we are unblocked on this.

Best Regards,
Rahul

-----Original Message-----
From: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx <agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx> On Behalf Of Marius Vlad via lists.automotivelinux.org
Sent: Friday, March 10, 2023 8:38 PM
To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Observed AGL guest VM failure once migrated to xen 4.18 from 4.16

Hi,

Judging by the logs it looks like all the clients die out due to providing invalid dmabuf attributes, more specifically the buffer stride seems to be rejected, which causes the Wayland connection to be terminated.

Specifically, these are the errors:

error 6: invalid stride 4320 for plane 0 error 6: invalid buffer stride or height for plane 0

This means the client attempted to specify some buffer dimensions that exceeds the buffer bounds, with the compositor rejecting it, and terminating the connection.

You can debug this further by setting WAYLAND_DEBUG=1 to /etc/default/agl-compositor and restart the user session. Then, take a look at the add_request parameters and compare them with the Xen version that works and the newer one. As to why would the update cause this, I have no idea at this point. I'd suggest opening a Jira task, and append those debug logs (working and no working) and continue there.


On 3/10/23 11:56, Kumar1, Rahul via lists.automotivelinux.org wrote:
> [AMD Official Use Only - General]
> 
> 
> Hi,
> 
> We are using AGL 14.0.1, as guest VM with xen environment, when we 
> used xen 4.16 we did not observe any issue.
> 
> After migrating xen to 4.18, we are seeing blank screen in boot. Agl 
> compositor and launcher are failing due to wayland client connection.
> 
> Below is snippet of error logs, also attaching complete log for this.
> 
> Error log:
> 
> ==============
> 
> Mar 09 19:44:36 amd-v2000 launcher[538]: Looking for icon 
> /usr/share/icons/hicolor/scalable/mediaplayer.svg
> 
> Mar 09 19:44:36 amd-v2000 launcher[538]: using icon 
> 'file:/usr/share/icons/hicolor/scalable/mediaplayer.svg'
> 
> Mar 09 19:44:36 amd-v2000 launcher[538]: Looking for icon 
> /usr/share/icons/hicolor/scalable/dashboard.svg
> 
> Mar 09 19:44:36 amd-v2000 launcher[538]: using icon 
> 'file:/usr/share/icons/hicolor/scalable/dashboard.svg'
> 
> Mar 09 19:44:36 amd-v2000 agl-compositor[452]: [19:44:36.629] Added 
> surface 0x55d2638ccfa0, app_id homescreen to pending list
> 
> Mar 09 19:44:36 amd-v2000 agl-compositor[452]: [19:44:36.663]
> libwayland: error in client communication (pid 538)
> 
> Mar 09 19:44:36 amd-v2000 agl-compositor[452]: [19:44:36.663] Removed 
> surface 0x55d2638ce470, app_id launcher, role NONE
> 
> Mar 09 19:44:36 amd-v2000 agl-compositor[452]: [19:44:36.663] Added 
> surface 0x55d2638ce470, app_id homescreen to pending list
> 
> Mar 09 19:44:36 amd-v2000 audit[538]: ANOM_ABEND auid=1001 uid=1001
> gid=1001 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0 pid=538 
> comm="launcher" exe="/usr/bin/launcher" sig=6 res=1
> 
> Mar 09 19:44:36 amd-v2000 launcher[538]: [destroyed object]: error 6: 
> invalid buffer stride or height for plane 0
> 
> Mar 09 19:44:36 amd-v2000 launcher[538]: The Wayland connection 
> experienced a fatal error: Protocol error
> 
> Mar 09 19:44:36 amd-v2000 systemd[441]: launcher.service: Main process 
> exited, code=killed, status=6/ABRT
> 
> Mar 09 19:44:36 amd-v2000 systemd[1]: kuksa-val.service: Scheduled 
> restart job, restart counter is at 4.
> 
> Mar 09 19:44:36 amd-v2000 systemd[441]: launcher.service: Failed with 
> result 'signal'.
> 
> Mar 09 19:44:36 amd-v2000 systemd[1]: Stopping 
> agl-service-audiomixer.service...
> 
> Mar 09 19:44:36 amd-v2000 systemd[1]: Stopping agl-service-hvac.service...
> 
> Mar 09 19:44:36 amd-v2000 systemd[1]: Stopping Eclipse KUKSA.val DBC 
> feeder...
> 
> Mar 09 19:44:36 amd-v2000 systemd[1]: kuksa-dbc-feeder.service: 
> Deactivated successfully.
> 
> Mar 09 19:44:36 amd-v2000 systemd[1]: Stopped Eclipse KUKSA.val DBC feeder.
> 
> Mar 09 19:44:36 amd-v2000 audit[1]: SERVICE_STOP pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0
> msg='unit=kuksa-dbc-feeder comm="systemd" exe="/usr/lib/systemd/systemd" 
> hostname=? addr=? terminal=? res=success'
> 
> Mar 09 19:44:36 amd-v2000 systemd[1]: Starting CAN interface helper...
> 
> Mar 09 19:44:36 amd-v2000 can-dev-helper.sh[560]: Checking can0
> 
> Mar 09 19:44:36 amd-v2000 systemd[1]: can-dev-helper.service: 
> Deactivated successfully.
> 
> ====================================
> 
> Appreciate if someone can help provide inputs on this.
> 
> Best Regards,
> 
> Rahul
> 
> 






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10459): https://lists.automotivelinux.org/g/agl-dev-community/message/10459
Mute This Topic: https://lists.automotivelinux.org/mt/97516362/2167316
Group Owner: agl-dev-community+owner@xxxxxxxxxxxxxxxxxxxxxxxxx
Unsubscribe: https://lists.automotivelinux.org/g/agl-dev-community/leave/4543822/2167316/883735764/xyzzy [list-automotive-discussions82@xxxxxxxxxxx]
-=-=-=-=-=-=-=-=-=-=-=-