Xorg with EVDI can't start with Mesa 21.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mesa (Ubuntu) |
New
|
High
|
Unassigned | ||
xorg-server (Ubuntu) |
New
|
High
|
Unassigned |
Bug Description
As I indicated in a bug report I filed earlier today, https:/
But I can't, because when I boot with the 5.10 kernel this is what shows up in /var/log/Xorg.0.log when gdm3 tries to start up the login screen (note: I have an NVIDIA graphics card, which is why (I believe) Wayland isn't being used here):
[ 857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy
[ 857.957] (EE)
Fatal server error:
[ 857.957] (EE) AddScreen/
[ 857.957] (EE)
[ 857.957] (EE)
Please consult the The X.Org Foundation support
at http://
for help.
[ 857.957] (EE) Please also check the log file at "/var/log/
[ 857.957] (EE)
[ 858.144] (EE) Server terminated with error (1). Closing log file.
This is probably not what you will see in the Xorg.0.log (if any) attached automatically to this bug because I've completely wiped the evdi kernel module from my system since that was the only way I could get a display manager up so I could use ubuntu-bug to submit this bug.
Here's what I updated today:
2021-03-18 15:03:26 upgrade sysvinit-
2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2
2021-03-18 15:03:28 upgrade gpg-wks-
2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:29 upgrade gpg-wks-
2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1
2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6
2021-03-18 15:03:33 install linux-modules-
2021-03-18 15:03:35 install linux-image-
2021-03-18 15:03:36 install linux-modules-
2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12
2021-03-18 15:03:40 upgrade linux-image-
2021-03-18 15:03:41 install linux-headers-
2021-03-18 15:03:44 install linux-headers-
2021-03-18 15:03:47 upgrade linux-headers-
2021-03-18 15:03:47 upgrade linux-libc-
2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0
2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 2:21.0.
2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3
At first glance I don't understand how any of these could be causing this behavior.
Potentially relevant: I had to recompile and reinstall the evdi kernel module while booted into 5.10 because when I install the 5.11 kernel dkms removed the module from 5.10 and then failed to rebuild it because the 5.11 build failed (or something I don't really understand why dkms does what it does *sigh*). I don't see how that should matter because the recompiled version of the module should have been identical, but *shrug*.
As noted above, when I remove the evdi kernel modules from /lib/modules and reboot with 5.10 the problem goes away, so this does appear to be an evdi issue.
In short: despite the fact that it's not clear how upgrading any of the modules listed above would cause evdi that used to work to suddenly stop working, that appears to be the case. Any advice would be appreciated because now I can't use the displays connected to my DisplayLink hub with either 5.10 or 5.11 kernels, despite the fact that they worked with the 5.10 kernel before today.
Please let me know if there's any other info you need here.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xserver-xorg 1:7.7+22ubuntu1
ProcVersionSign
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.141 Mon Dec 28 16:21:32 UTC 2020
GCC version: gcc version 10.2.1 20210220 (Ubuntu 10.2.1-20ubuntu1)
.tmp.unity_
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckR
CompizPlugins: No value set for `/apps/
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 18 16:32:16 2021
DistUpgraded: 2021-02-21 12:14:33,907 DEBUG Running PostInstallScript: './xorg_
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller])
Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
InstallationDate: Installed on 2019-01-02 (806 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Acer Predator G6-710
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: Upgraded to hirsute on 2021-02-21 (25 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmerican
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.14.
version.libdrm2: libdrm2 2.4.104-1build1
version.
version.
version.
version.
version.
version.
version.
version.
affects: | xorg (Ubuntu) → xorg-server (Ubuntu) |
Changed in xorg-server (Ubuntu): | |
status: | New → Incomplete |
status: | Incomplete → New |
tags: | added: regression-release |
summary: |
- Somehow today's Hirsute updates have broken evdi with Xorg even when I - boot with the 5.10 kernel + Xorg with EVDI can't start with Mesa 21.0 |
Changed in mesa (Ubuntu): | |
importance: | Undecided → High |
Changed in xorg-server (Ubuntu): | |
importance: | Undecided → High |
I debugged this further and discovered that one of the following updates caused evdi with kernel 5.10 to start failing as described above:
2021-03-18 21:55:45 upgrade libegl-mesa0:amd64 20.3.4-1 21.0.0-1 mesa-dri: i386 20.3.4-1 21.0.0-1 mesa-dri: amd64 20.3.4-1 21.0.0-1
2021-03-18 21:55:45 upgrade libgbm1:amd64 20.3.4-1 21.0.0-1
2021-03-18 21:55:45 upgrade libgl1-
2021-03-18 21:55:46 upgrade libgl1-
2021-03-18 21:55:47 upgrade libglx-mesa0:i386 20.3.4-1 21.0.0-1
2021-03-18 21:55:48 upgrade libglx-mesa0:amd64 20.3.4-1 21.0.0-1
2021-03-18 21:55:48 upgrade libglapi-mesa:amd64 20.3.4-1 21.0.0-1
2021-03-18 21:55:48 upgrade libglapi-mesa:i386 20.3.4-1 21.0.0-1
When I downgraded all of the listed debs to the old version indicated (20.3.4-1) and rebooted, evdi with kernel 5.10 started working again. So I guess this is a mesa bug?