[nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works)

Bug #1971202 reported by enorrmann
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

happens with both xorg and wayland

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30
Uname: Linux 5.15.0-27-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Mon May 2 18:20:07 2022
DistUpgraded: 2022-03-26 15:56:50,280 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-27-lowlatency, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU106M [GeForce RTX 2060 Max-Q] [1043:1e11]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e11]
MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-03-26 (37 days ago)
dmi.bios.date: 12/30/2020
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GA502IV.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GA502IV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.13
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.211:bd12/30/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Zephyrus G15
dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
enorrmann (enorrmann) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [nouveau][amdgpu] Freeze

Thanks for the bug report. Next time a freeze happens please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Also check for crashes by following https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

summary: - Xorg freeze
+ Freeze
tags: added: amdgpu hybrid nouveau
summary: - Freeze
+ [nouveau][amdgpu] Freeze
affects: xorg (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also open the 'Additional Drivers' app to install/reinstall the Nvidia driver because the one you have installed in the past is not working.

Revision history for this message
enorrmann (enorrmann) wrote :

After reinstalling nvidia 510, the issue remains

Revision history for this message
enorrmann (enorrmann) wrote :

another prev boot log

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. I can't see any crashes or reasons for a freeze there. But having an unsupported extension installed might be the problem:

  /<email address hidden>

Please:

  cd ~/.local/share/gnome-shell
  rm -rf extensions

and then log in again. Does the problem still happen?

Also your log is mentioning there was a historical crash in gnome-shell and Xwayland so please look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Revision history for this message
enorrmann (enorrmann) wrote :

I've deleted the extensions and I'm testing again.
Also, I don't see any crash report with the date of the events in errors.ubuntu

Revision history for this message
enorrmann (enorrmann) wrote :

I removed the extensions, and the issue is still present

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. Please try some older (like 5.13) and newer kernels (like 5.17.5) to see if the problem was recently introduced or fixed already:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

Changed in ubuntu:
status: Incomplete → New
status: New → Incomplete
Revision history for this message
enorrmann (enorrmann) wrote :

I'm running 5.17.6 now, but I can't install the nvidia drivers using ubuntu-drivers because "version 'unsigned-5.17.6-051706' has bad syntax: version number does not start with digit"

Revision history for this message
enorrmann (enorrmann) wrote (last edit ):

EDIT: after a while running ok with 5.17.6, the system crashed again

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
summary: - [nouveau][amdgpu] Freeze
+ [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
enorrmann (enorrmann) wrote :

after clean install the bug is no longer present

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.