** Description changed:
Hello,
I see the following messages keeps being logged in /var/log/syslog:
```
Apr 8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip
queue failed: Invalid argument
Apr 8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0):
hi canonical team ,
can you please update the target on which this issue is reproduced and
the release image information to the bug description.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060458
I didn't expect it to go that smoothly :D
Yes a bug should be logged against the DDX in that case. I don't know
where the code came from; maybe use https://github.com/Xilinx/mali-
userspace-binaries/issues/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi Daniel,
I started gdm with wayland by following the steps mentioned in the bug
1961563. It started successfully, and after wayland enabled I am not
seeing strange error messages flooding the logs.
So can we start suspecting DDX driver as you mentioned?
--
You received this bug notification
Any message with (WW) or (EE) means you're still using Xorg, not
Wayland.
Switching a Xilinx system to Wayland used to be a manual process as
mentioned in bug 1961563. I was just hoping it had been simplified since
then. I don't know because I had to return the hardware before Wayland
support
Just changed the `WaylandEnable=true` to check if thats changes anything
it was set to false before.
```
# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.
[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=true
Looks like the same problem. Either a bug in the DDX driver "ARMSOC", or
a bug in the kernel driver "xlnx". To figure out which I can only
recommend you try Wayland instead. Because if it's a kernel bug then
Wayland will display similar errors.
P.S. I no longer have the hardware to test.
--
You
Hi Daniel,
It seems you are right indeed, it looks like it is some kind of side
effect due to my debug efforts on some other issue, so I got rid of the
custom xorg to be sure.
But I did flash the image from scratch and did apt update and upgrade
and make sure that there is no custom mumbo jumbo
** Package changed: ubuntu => linux-xilinx-zynqmp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060458
Title:
ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
To manage
Those errors are coming from some custom Xorg driver ("ARMSOC"?), not
from the Ubuntu archive AFAICS. Perhaps from LP-PPA-tchavadar-xilinx
But we should be using Wayland on Xilinx now, since I implemented it a
couple of years ago... Please try Wayland and tell us if any similar
failures occur.
10 matches
Mail list logo
