[qxl] Desktop freezes 20.04

[Yuri Weinstein]

Not too much info yet, will add apport report, but see it very often on 20.04 (upgraded from 18.04)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-05-07 (759 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: gnome-shell 3.36.1-5ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
Tags: focal
Uname: Linux 5.4.0-33-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-05-07 (759 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: gnome-shell 3.36.1-5ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
Tags: focal
Uname: Linux 5.4.0-33-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yuriw 1143 F.... pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-05-07 (764 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
 ens8 no wireless extensions.

 lo no wireless extensions.

 ens3 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b5969aa-16c5-43c7-9a83-1c75e5e19363 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-33-generic N/A
 linux-backports-modules-5.4.0-33-generic N/A
 linux-firmware 1.187
RfKill:

Tags: focal
Uname: Linux 5.4.0-33-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-24 (46 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-05-07 (805 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: focal
Uname: Linux 5.8.0-050800rc5-lowlatency x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1881813/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Daniel van Vugt (vanvugt)]

Please remember the apport info.

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

the apport report was dine after desktop freeze.

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

and additional report after reboot

[Daniel van Vugt (vanvugt)]

1. In case gnome-shell (or Xorg) crashed please follow these instructions:

   https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

2. Please run this command on the machine:

   lspci -k > lspcik.txt

   and send us the resulting text file.

3. Please run one of these commands on the machine immediately after a freeze:

   journalctl -b0 > journal.txt # If you have not rebooted after the freeze
   journalctl -b-1 > prevjournal.txt # If you have rebooted after the freeze

   and attach the resulting text file here.

[Yuri Weinstein (yuri-weinstein)]

lspci -k > lspcik.txt
https://pastebin.com/na6MgB0h

00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
 Subsystem: Red Hat, Inc. Qemu virtual machine
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
 Subsystem: Red Hat, Inc. Qemu virtual machine
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
 Subsystem: Red Hat, Inc. Qemu virtual machine
 Kernel driver in use: ata_piix
 Kernel modules: pata_acpi
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
 Subsystem: Red Hat, Inc. Qemu virtual machine
 Kernel driver in use: piix4_smbus
 Kernel modules: i2c_piix4
00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04)
 Subsystem: Red Hat, Inc. QEMU Virtual Machine
 Kernel driver in use: qxl
 Kernel modules: qxl
00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
 Subsystem: Red Hat, Inc. Virtio network device
 Kernel driver in use: virtio-pci
00:04.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 01)
 Subsystem: Red Hat, Inc. QEMU Virtual Machine
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel
00:05.0 Communication controller: Red Hat, Inc. Virtio console
 Subsystem: Red Hat, Inc. Virtio console
 Kernel driver in use: virtio-pci
00:06.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
 Subsystem: Red Hat, Inc. QEMU Virtual Machine
 Kernel driver in use: uhci_hcd
00:06.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
 Subsystem: Red Hat, Inc. QEMU Virtual Machine
 Kernel driver in use: uhci_hcd
00:06.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
 Subsystem: Red Hat, Inc. QEMU Virtual Machine
 Kernel driver in use: uhci_hcd
00:06.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
 Subsystem: Red Hat, Inc. QEMU Virtual Machine
 Kernel driver in use: ehci-pci
00:07.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon
 Subsystem: Red Hat, Inc. Virtio memory balloon
 Kernel driver in use: virtio-pci
00:08.0 Ethernet controller: Red Hat, Inc. Virtio network device
 Subsystem: Red Hat, Inc. Virtio network device
 Kernel driver in use: virtio-pci

[Daniel van Vugt (vanvugt)]

Also, please try selecting 'Ubuntu on Wayland' from the login screen, if you can. Does that avoid the problem?

[Yuri Weinstein (yuri-weinstein)]

attaching both files

journal.txt got via ssh during the freeze
prevjournal.txt after force system down and reboot

[Daniel van Vugt (vanvugt)]

Perfect, thanks! The attachment in comment #19 confirms it's a kernel bug relating to the qxl driver:

Jun 09 16:22:59 bionic-vm kernel: INFO: task Xorg:1172 blocked for more than 120 seconds.
Jun 09 16:22:59 bionic-vm kernel: Not tainted 5.4.0-33-generic #37-Ubuntu
Jun 09 16:22:59 bionic-vm kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 09 16:22:59 bionic-vm kernel: Xorg D 0 1172 1170 0x00004004
Jun 09 16:22:59 bionic-vm kernel: Call Trace:
Jun 09 16:22:59 bionic-vm kernel: __schedule+0x2e3/0x740
Jun 09 16:22:59 bionic-vm kernel: schedule+0x42/0xb0
Jun 09 16:22:59 bionic-vm kernel: schedule_preempt_disabled+0xe/0x10
Jun 09 16:22:59 bionic-vm kernel: __ww_mutex_lock.isra.0+0x261/0x7f0
Jun 09 16:22:59 bionic-vm kernel: __ww_mutex_lock_slowpath+0x16/0x20
Jun 09 16:22:59 bionic-vm kernel: ww_mutex_lock+0x38/0x90
Jun 09 16:22:59 bionic-vm kernel: ttm_eu_reserve_buffers+0x1d0/0x2f0 [ttm]
Jun 09 16:22:59 bionic-vm kernel: qxl_release_reserve_list+0x5f/0x140 [qxl]
Jun 09 16:22:59 bionic-vm kernel: ? qxl_bo_pin+0xf4/0x1a0 [qxl]
Jun 09 16:22:59 bionic-vm kernel: qxl_cursor_atomic_update+0x1a4/0x2e0 [qxl]
Jun 09 16:22:59 bionic-vm kernel: ? qxl_bo_pin+0xf4/0x1a0 [qxl]
Jun 09 16:22:59 bionic-vm kernel: drm_atomic_helper_commit_planes+0xbd/0x220 [drm_kms_helper]
Jun 09 16:22:59 bionic-vm kernel: drm_atomic_helper_commit_tail+0x2c/0x70 [drm_kms_helper]
Jun 09 16:22:59 bionic-vm kernel: commit_tail+0xd7/0x110 [drm_kms_helper]
Jun 09 16:22:59 bionic-vm kernel: drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
Jun 09 16:22:59 bionic-vm kernel: drm_atomic_commit+0x4a/0x50 [drm]
Jun 09 16:23:00 bionic-vm kernel: drm_atomic_helper_update_plane+0xea/0x100 [drm_kms_helper]
Jun 09 16:23:00 bionic-vm kernel: __setplane_atomic+0xcc/0x110 [drm]
Jun 09 16:23:00 bionic-vm kernel: drm_mode_cursor_universal+0x13e/0x260 [drm]
Jun 09 16:23:00 bionic-vm kernel: drm_mode_cursor_common+0xcc/0x220 [drm]
Jun 09 16:23:00 bionic-vm kernel: ? drm_mode_cursor_ioctl+0x60/0x60 [drm]
Jun 09 16:23:00 bionic-vm kernel: drm_mode_cursor2_ioctl+0xe/0x10 [drm]
Jun 09 16:23:00 bionic-vm kernel: drm_ioctl_kernel+0xae/0xf0 [drm]
Jun 09 16:23:00 bionic-vm kernel: drm_ioctl+0x234/0x3d0 [drm]
Jun 09 16:23:00 bionic-vm kernel: ? drm_mode_cursor_ioctl+0x60/0x60 [drm]
Jun 09 16:23:00 bionic-vm kernel: ? timerqueue_add+0x68/0xb0
Jun 09 16:23:00 bionic-vm kernel: ? enqueue_hrtimer+0x3d/0x90
Jun 09 16:23:00 bionic-vm kernel: do_vfs_ioctl+0x407/0x670
Jun 09 16:23:00 bionic-vm kernel: ? fput+0x13/0x15
Jun 09 16:23:00 bionic-vm kernel: ? __sys_recvmsg+0x88/0xa0
Jun 09 16:23:00 bionic-vm kernel: ksys_ioctl+0x67/0x90
Jun 09 16:23:00 bionic-vm kernel: __x64_sys_ioctl+0x1a/0x20
Jun 09 16:23:00 bionic-vm kernel: do_syscall_64+0x57/0x190
Jun 09 16:23:00 bionic-vm kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 09 16:23:00 bionic-vm kernel: RIP: 0033:0x7faae89f937b
Jun 09 16:23:00 bionic-vm kernel: Code: Bad RIP value.
Jun 09 16:23:00 bionic-vm kernel: RSP: 002b:00007fff616d6b48 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jun 09 16:23:00 bionic-vm kernel: RAX: ffffffffffffffda RBX: 00007fff616d6b80 RCX: 00007...

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1881813

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

apport information

[Yuri Weinstein (yuri-weinstein)]

I’m glad, looking forward to the fix

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/

[Yuri Weinstein (yuri-weinstein)]

Installed v5.8 so far so good, but it's hard to say till it freezes or not during some use.

[Yuri Weinstein (yuri-weinstein)]

I did experience a complete lock of my system on the latest kernel and it was worse then before, in a way that I was not able even to ssh to my VM at all :(

[Yuri Weinstein (yuri-weinstein)]

Correction I was able to shh it took very long time.

Attaching log files

[Yuri Weinstein (yuri-weinstein)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Please file a bug here:
https://gitlab.freedesktop.org/drm/misc/-/issues