[AMD Official Use Only - General]
Hi Marius,
Below are my details
Name - Rahul Kumar
email ID - rahul.kumar1@xxxxxxx
Feel free to tag me for "Tested-by" option.
Rahul
On Fri, Mar 31, 2023 at 07:57:38PM +0300, Marius Vlad via lists.automotivelinux.org wrote:
> On Fri, Mar 31, 2023 at 10:59:34AM +0000, Kumar1, Rahul via lists.automotivelinux.org wrote:
> > [AMD Official Use Only - General]
> >
> > Hi Marius,
> >
> > I checked at my end, xen is working with "virgl resource" change after taking below changes
> >
> > https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/28580
> Hi Rahul,
>
> Thanks a lot for giving it a go. I can't seem to grab your official email as
> to tag the patch with a 'Tested-by: Your Name <your.email>'. Either the
> mailing list gets that obfuscated or there's somethig from your side
> (I only see Rahul.Kumar1=amd.com@xxxxxxxxxxxxxxxxxxxxxxxxx as sender)
>
> If you can't make it public it is no problem, but would've been nice to have
> it so I can reference in the patch.
Oh I just realized now it's actually an anti-spam thing from
lists.automotivelinux.org. I've updated the patch now.
>
> Thanks again!
>
> >
> > Best Regards,
> > Rahul
> >
> >
> >
> > On Mon, Mar 13, 2023 at 03:32:14AM +0000, Kumar1, Rahul via lists.automotivelinux.org wrote:
> > > [AMD Official Use Only - General]
> > >
> > > Hi,
> > Hi Rahul,
> > >
> > > 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.
> > Just a heads up, I think I've identified a fix that was introduced a while back with mesa 22.2.5 (much sooner than 22.3.5).
> >
> > It's at https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/28580
> > and if you have spare cycles I'd like to ask you to give this a try on your side with Xen and let me know if this works -- that is to try with latest Xen version you've tried initially.
> >
> > Just use our lastest master which you apply on top that change, rebuild and give it a go. With qemu I was able to get this working as is and I'm curios if this fixes for Xen as well.
> >
> > Thanks
> >
> > >
> > > 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
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
From: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx <agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx> on behalf of Marius Vlad via lists.automotivelinux.org <marius.vlad=collabora.com@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, 31 March, 2023, 22:32
To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx <agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Observed AGL guest VM failure once migrated to xen 4.18 from 4.16
Sent: Friday, 31 March, 2023, 22:32
To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx <agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Observed AGL guest VM failure once migrated to xen 4.18 from 4.16
On Fri, Mar 31, 2023 at 07:57:38PM +0300, Marius Vlad via lists.automotivelinux.org wrote:
> On Fri, Mar 31, 2023 at 10:59:34AM +0000, Kumar1, Rahul via lists.automotivelinux.org wrote:
> > [AMD Official Use Only - General]
> >
> > Hi Marius,
> >
> > I checked at my end, xen is working with "virgl resource" change after taking below changes
> >
> > https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/28580
> Hi Rahul,
>
> Thanks a lot for giving it a go. I can't seem to grab your official email as
> to tag the patch with a 'Tested-by: Your Name <your.email>'. Either the
> mailing list gets that obfuscated or there's somethig from your side
> (I only see Rahul.Kumar1=amd.com@xxxxxxxxxxxxxxxxxxxxxxxxx as sender)
>
> If you can't make it public it is no problem, but would've been nice to have
> it so I can reference in the patch.
Oh I just realized now it's actually an anti-spam thing from
lists.automotivelinux.org. I've updated the patch now.
>
> Thanks again!
>
> >
> > Best Regards,
> > Rahul
> >
> >
> >
> > On Mon, Mar 13, 2023 at 03:32:14AM +0000, Kumar1, Rahul via lists.automotivelinux.org wrote:
> > > [AMD Official Use Only - General]
> > >
> > > Hi,
> > Hi Rahul,
> > >
> > > 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.
> > Just a heads up, I think I've identified a fix that was introduced a while back with mesa 22.2.5 (much sooner than 22.3.5).
> >
> > It's at https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/28580
> > and if you have spare cycles I'd like to ask you to give this a try on your side with Xen and let me know if this works -- that is to try with latest Xen version you've tried initially.
> >
> > Just use our lastest master which you apply on top that change, rebuild and give it a go. With qemu I was able to get this working as is and I'm curios if this fixes for Xen as well.
> >
> > Thanks
> >
> > >
> > > 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 (#10493) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
_._,_._,_
