Black screen [amdgpu: amdgpu_device_ip_init failed]

[Sophie Freeman]

Screen is black after opening laptop if it was closed - this did not happen before update. Can only boot in recovery mode, otherwise screen is black

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-113.123-generic 5.15.152
Uname: Linux 5.15.0-113-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Tue Jul 2 10:45:03 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c2) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Picasso [1025:1456]
InstallationDate: Installed on 2021-05-26 (1132 days ago)
InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: Acer Aspire A315-23
ProcEnviron:
 TERM=alacritty
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-113-generic root=UUID=037635b8-b46a-4acb-89b8-5ea035888b63 ro recovery nomodeset dis_ucode_ldr nvme_core.default_ps_max_latency_us=14000
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/27/2020
dmi.bios.release: 1.6
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Lotus_DA
dmi.board.vendor: DL
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.3
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd04/27/2020:br1.6:efr1.3:svnAcer:pnAspireA315-23:pvrV1.06:rvnDL:rnLotus_DA:rvrV1.06:cvnChassisManufacturer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Aspire 3
dmi.product.name: Aspire A315-23
dmi.product.sku: 0000000000000000
dmi.product.version: V1.06
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
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

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then 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.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Sophie Freeman (sophief)]

When running ubuntu-bug I get the message 'Ubuntu 22.04 has experienced an internal error'. The whoopsie-id file also appears to be empty...

[Daniel van Vugt (vanvugt)]

Please try:

  sudo cat /var/lib/whoopsie/whoopsie-id

[Daniel van Vugt (vanvugt)]

Although it sounds like the desktop is missing?!

Jul 03 09:17:21 loonix systemd[1238]: pam_unix(systemd-user:session): session opened for user zosia(uid=1000) by (uid=0)
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Configuration file /etc/xdg/autostart/org.kde.discover.notifier.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Exec binary 'klipper' does not exist: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Not generating service for XDG autostart <email address hidden>, error parsing Exec= line: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Exec binary 'xembedsniproxy' does not exist: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Not generating service for XDG autostart <email address hidden>, error parsing Exec= line: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Exec binary '/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd' does not exist: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Not generating service for XDG autostart <email address hidden>, error parsing Exec= line: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Exec binary 'gmenudbusmenuproxy' does not exist: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Not generating service for XDG autostart <email address hidden>, error parsing Exec= line: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Exec binary '/usr/bin/plasmashell' does not exist: No such file or directory
Jul 03 09:17:21 loonix systemd-xdg-autostart-generator[1243]: Not generating service for XDG autostart <email address hidden>, error parsing Exec= line: No such file or directory

[Sophie Freeman (sophief)]

Here is the whoopsie-id file: 71f80446dc8c0bcbf90280d95473e908b86066cfc89535044efc4d8199f387e4dc099301b04359b4d77198c881f1e591905d2593627c285987df6f1475e1bd2b

Also I use a window manager (i3) not desktop environment, is that what you mean?

[Daniel van Vugt (vanvugt)]

Thanks but that only shows polybar crashed, once, two days ago:
  https://errors.ubuntu.com/oops/0cde96dc-3960-11ef-9ead-fa163ec44ecd
It's probably not relevant.

Looking back at your journal.txt and prevjournal.txt, those are both from recovery mode. We need to see a boot attempt that wasn't from recovery mode so please do one of those, then reboot into recovery mode again and run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

[Daniel van Vugt (vanvugt)]

Thanks. It seems the issue is that the kernel graphics driver failed to initialize:

Jul 04 09:52:48 loonix kernel: amdgpu 0000:05:00.0: amdgpu: amdgpu_device_ip_init failed
Jul 04 09:52:48 loonix kernel: amdgpu 0000:05:00.0: amdgpu: Fatal error during GPU init
Jul 04 09:52:48 loonix kernel: amdgpu 0000:05:00.0: amdgpu: amdgpu: finishing device.

and then it crashed. So a black screen is expected...

The next thing to try is to choose a kernel version older than 5.15.0-113.123-generic at startup. You can do that by accessing the grub menu. Soon after you see the BIOS logo when rebooting, tap Escape once, and that should give you the grub menu. There you can select the previously installed kernel version.

Another thing to try is to change the machine over to the hardware enablement kernel. Assuming you have network access in recovery mode, run:

  sudo apt install linux-generic-hwe-22.04

Hopefully that will fix it.

[Sophie Freeman (sophief)]

Seems to have done the trick! Thanks for your help!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.