ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap

[Talha Can Havadar]

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): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:04:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:04:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:05:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:05:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:06:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:06:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:07:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:07:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:08:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:08:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:09:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:09:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:10:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:10:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:11:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:11:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:12:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:12:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:13:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:13:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
Apr 8 10:14:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument
Apr 8 10:14:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
```

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7.22.04.4
ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136
Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/mmcblk1p1)
Date: Mon Apr 8 10:15:18 2024
ProcEnviron:
 TERM=vt220
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2023-09-20T10:06:31

Issue is reproduced on Kria KV260, please wait up to 1 minutes to see the flooding error messages.

[Daniel van Vugt (vanvugt)]

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.

[Talha Can Havadar (tchavadar)]

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 even after that I can still see the same error message popping up. I also attached the additional information from my last run so please check them.

[Daniel van Vugt (vanvugt)]

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.

[Talha Can Havadar (tchavadar)]

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
```

But I can still see the same error. But I am not connecting board to a display this is all being done through tty. I am not sure this might be the reason I see this errors but it should work without these error messages even without a display connected right?

[Daniel van Vugt (vanvugt)]

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 ever made it into jammy updates.

[Talha Can Havadar (tchavadar)]

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?

[Daniel van Vugt (vanvugt)]

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/ ?

[amit nagal (amitnxlnx)]

hi canonical team ,

can you please update the target on which this issue is reproduced and the release image information to the bug description.