AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
- Jammy (22.04)
- Bug #2068738
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Matthew Ruffell |
Bug Description
BugLink: https:/
[Impact]
On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is enabled, the system fails to boot correctly, and all users see is a black screen.
This is caused by a null pointer dereference when enabling the IOMMU after the device has been initialised. It should happen the other way around.
AMD-Vi: AMD IOMMUv2 loaded and initialized
...
amdgpu: Topology: Add APU node [0x15d8:0x1002]
kfd kfd: amdgpu: added device 1002:15d8
kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
...
amdgpu 0000:06:00.0: amdgpu: amdgpu_
amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
...
BUG: kernel NULL pointer dereference, address: 000000000000013c
...
CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
...
RIP: 0010:amdgpu_
...
Call Trace:
<TASK>
? srso_return_
? show_trace_
? show_trace_
? dm_hw_fini+
? show_regs.
? __die_body.
? __die+0x2b/0x37
? page_fault_
? srso_return_
? do_user_
? srso_return_
? __free_
? exc_page_
? asm_exc_
? amdgpu_
dm_hw_
amdgpu_
amdgpu_
amdgpu_
amdgpu_
amdgpu_
local_
? srso_return_
pci_device_
really_
__driver_
driver_
__driver_
? __device_
bus_for_
driver_
bus_add_
? srso_return_
driver_
__pci_
amdgpu_
? 0xffffffffc0e0b000
do_one_
? srso_return_
? kmem_cache_
do_init_
load_module+
__do_sys_
__x64_
x64_sys_
do_syscall_
...
entry_
A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" to GRUB_CMDLINE_
[Fix]
The regression was caused by the following commit that landed in 5.15.0-112-generic, and 5.15.150 upstream:
commit 3c7e53c0d4b43ff
Author: Yifan Zhang <email address hidden>
Date: Tue Sep 28 15:42:35 2021 +0800
Subject: drm/amdgpu: init iommu after amdkfd device init
Link: https:/
The fix is to revert this patch, as it was not suppose to be backported to 5.15 stable.
The mailing list discussion with AMD developers is:
https://<email address hidden>/
The fix hasn't been acknowledged by Greg KH or Sasha Levin yet, so sending as a Ubuntu SAUCE patch. If the upstream status changes, we can NAK and resend.
[Testcase]
You need a system with an AMD Picasso/Raven 2 device. It will likely be an APU, and not a discrete graphics card, but any AMD Picasso/Raven 2 device is affected.
Install the kernel and boot. Make sure full modesetting is enabled.
There is a test kernel available in the ppa below:
https:/
If you install the test kernel, your system should boot successfully.
[Where problems could occur]
We are reverting a problematic patch and going back to how it was before 5.15.0-112-generic. This should not cause any issues for users.
If a regression were to occur, users can set "nomodeset" or "amd_iommu=off" to GRUB_CMDLINE_
The impact of a regression would be high, as users displays could be blank.
[Other Info]
User reports:
https:/
https:/
https:/
https:/
https:/
https:/
https:/
As bizarre as it is, this commit was actually originally included in 5.15-rc5:
commit 714d9e4574d5459
Author: Yifan Zhang <email address hidden>
Date: Tue Sep 28 15:42:35 2021 +0800
Subject: drm/amdgpu: init iommu after amdkfd device init
Link: https:/
It seems to have caused issues back then too, and was removed in the following fixups, in 5.16-rc1:
commit 93cec184788b0cf
Author: James Zhu <email address hidden>
Date: Tue Nov 2 21:33:50 2021 -0400
Subject: drm/amdgpu: remove duplicated kfd_resume_iommu
Link: https:/
commit 9f4f2c1a35248f5
Author: shaoyunl <email address hidden>
Date: Fri Nov 5 12:34:14 2021 -0400
Subject: drm/amd/amdgpu: fix the kfd pre_reset sequence in sriov
Link: https:/
I'm not exactly in favor of rewriting history twice, so I think we should just revert the upstream stable patch and move on.
CVE References
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #1 |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rfc (rfc0) wrote : | #2 |
I have similar symptom: after upgrading to linux-image-
The issue is recurring, repeated attempts to boot using linux-image-
Restarting and using grub to boot using linux-image-
processor: AMD® Ryzen 3 2200g with radeon vega graphics × 4
graphics: AMD® Radeon vega 8 graphics
os name: Ubuntu 22.04.4 LTS
gnome version: 42.9
windowing system: wayland
Additional reports:
https:/
One of the folks impacted in the above reddit thread reported that their although their display was black, the machine booted and they were able to interact with it normally over SSH.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fred Jupiter (fredjupiter) wrote : | #3 |
Try this ("Temporary" first to gain access to the computer again), if you want to use the new kernel:
It worked for me.
Workaround:
Temporary:
Add "nomodeset" before "quiet splash" via editing of GRUB menu.
Permanent:
Edit /etc/default/grub: the line "GRUB_CMDLINE_
- Run "sudo update-grub"
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
berni123 (bernd-bernd--zimmermann) wrote : | #4 |
@Fred: setting nomodeset is only a small workaround, it disables full graphic support, no multi display usage, no high resolution ...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
berni123 (bernd-bernd--zimmermann) wrote : | #5 |
Quick-Fix: GRUB_CMDLINE_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Lin Manfu (linmanfu) wrote : | #6 |
I am also affected by this bug. Booting to kernel 5.15.0-112 produces a black screen. Kernel 5.15.0-107 works correctly. Here is information about my system:
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-107-generic (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 11 Graphics
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rfc (rfc0) wrote : | #7 |
additional reports of this issue: https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Lin Manfu (linmanfu) wrote (last edit ): | #8 |
- syslog-for-broken-kernel-112 Edit (2.0 MiB, text/html)
Attached is an annotated copy of my system log with the relevant update from 107 to 112, the failed boots with 112, a successful boot with the last good kernel 107, and a boot with 112 using the workaround. Search for BOOT in capital letters to find the start of each boot. I hope this might be helpful.
I am no expert, but perhaps these lines might be relevant, as they only seem to occur on the failed boots with 112:
Jun 8 19:17:56 paul kernel: [ 3.190269] amdgpu: Topology: Add APU node [0x15d8:0x1002]
Jun 8 19:17:56 paul kernel: [ 3.190273] kfd kfd: amdgpu: added device 1002:15d8
Jun 8 19:17:56 paul kernel: [ 3.190280] kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
Jun 8 19:17:56 paul kernel: [ 3.190287] amdgpu 0000:27:00.0: amdgpu: amdgpu_
Jun 8 19:17:56 paul kernel: [ 3.190292] amdgpu 0000:27:00.0: amdgpu: Fatal error during GPU init
Jun 8 19:17:56 paul kernel: [ 3.190296] amdgpu 0000:27:00.0: amdgpu: amdgpu: finishing device.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
berni123 (bernd-bernd--zimmermann) wrote : | #9 |
Some more info on booting -112 related to amdgpu, which is crashing:
Jun 7 09:29:22 enterprise kernel: [ 2.809882] AMD-Vi: AMD IOMMUv2 loaded and initialized
Jun 7 09:29:22 enterprise kernel: [ 2.979171] amdgpu: Topology: Add APU node [0x0:0x0]
Jun 7 09:29:22 enterprise kernel: [ 2.979234] checking generic (d0000000 300000) vs hw (d0000000 10000000)
Jun 7 09:29:22 enterprise kernel: [ 2.979341] amdgpu 0000:06:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
Jun 7 09:29:22 enterprise kernel: [ 3.002476] amdgpu 0000:06:00.0: amdgpu: Fetched VBIOS from ROM BAR
Jun 7 09:29:22 enterprise kernel: [ 3.002478] amdgpu: ATOM BIOS: 113-PICASSO-117
Jun 7 09:29:22 enterprise kernel: [ 3.002608] amdgpu 0000:06:00.0: vgaarb: deactivate vga console
Jun 7 09:29:22 enterprise kernel: [ 3.002653] amdgpu 0000:06:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
Jun 7 09:29:22 enterprise kernel: [ 3.002656] amdgpu 0000:06:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
Jun 7 09:29:22 enterprise kernel: [ 3.002659] amdgpu 0000:06:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
Jun 7 09:29:22 enterprise kernel: [ 3.003052] amdgpu 0000:06:00.0: amdgpu: PSP runtime database doesn't exist
Jun 7 09:29:22 enterprise kernel: [ 3.004269] amdgpu: hwmgr_sw_init smu backed is smu10_smu
Jun 7 09:29:22 enterprise kernel: [ 3.004404] amdgpu 0000:06:00.0: amdgpu: Will use PSP to load VCN firmware
Jun 7 09:29:22 enterprise kernel: [ 3.088846] amdgpu 0000:06:00.0: amdgpu: RAS: optional ras ta ucode is not available
Jun 7 09:29:22 enterprise kernel: [ 3.093879] amdgpu 0000:06:00.0: amdgpu: RAP: optional rap ta ucode is not available
un 7 09:29:22 enterprise kernel: [ 3.186429] amdgpu: HMM registered 2048MB device memory
Jun 7 09:29:22 enterprise kernel: [ 3.186503] amdgpu: Topology: Add APU node [0x15d8:0x1002]
Jun 7 09:29:22 enterprise kernel: [ 3.186508] kfd kfd: amdgpu: added device 1002:15d8
Jun 7 09:29:22 enterprise kernel: [ 3.186516] kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
Jun 7 09:29:22 enterprise kernel: [ 3.186530] amdgpu 0000:06:00.0: amdgpu: amdgpu_
Jun 7 09:29:22 enterprise kernel: [ 3.186535] amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
Jun 7 09:29:22 enterprise kernel: [ 3.186545] amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
Jun 7 09:29:22 enterprise kernel: [ 3.194967] BUG: kernel NULL pointer dereference, address: 000000000000013c
Jun 7 09:29:22 enterprise kernel: [ 3.194971] #PF: supervisor read access in kernel mode
Jun 7 09:29:22 enterprise kernel: [ 3.194975] #PF: error_code(0x0000) - not-present page
Jun 7 09:29:22 enterprise kernel: [ 3.194978] PGD 0 P4D 0
Jun 7 09:29:22 enterprise kernel: [ 3.194983] Oops: 0000 [#1] SMP NOPTI
Jun 7 09:29:22 enterprise kernel: [ 3.194987] CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
Jun 7 09:29:22 enterprise kernel: [ 3.194993] Hardware name: Gigabyte Technology Co., Ltd. B450 AORUS ELITE/B450 AORUS ELITE, BIOS F60c 10/29/2020
Jun 7 09:29...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Carrington Institute (symbolize) wrote : | #10 |
I had the same issue, similar hardware I have had to revert back to the previous kernel version 5.15.0.-107 there was some errors in the log that pointed at the AMD GPU
if you need to boot from the previous kernel you will need to tap shift when the device boots, go into advanced options and select
kernel .107 generic
I then changed my grub menu
sudo nano /etc/default/grub
changed
GRUB_DEFAULT=0
to
GRUB_DEFAULT="1>2" (this tells grub to boot into advanced options and then the second linux kernel image, .107 at least for me ) save the file
sudo update-grub
sudo reboot
The device then booted successfully into the working .107
then i removed the .112 kernel
sudo apt remove linux-image-
sudo apt remove linux-headers-
sudo update-grub
I also put a hold on .112
sudo apt-mark hold linux-image-
sudo apt-mark hold linux-image-
apt-mark showhold
I then changed grub back to
GRUB_DEFAULT=0
I have attached a full log for the developers perusal
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fenestrae, et vastata annis. (exfenestrae) wrote : | #11 |
Ditto @linmanfu:
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-107-generic (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mario Limonciello (superm1) wrote : | #12 |
AFAIK It's a bad backport to 5.15 stable. If it's what I think, here's the fix (IIRC).
https://<email address hidden>/
Try applying that to your 5.15 kernel.
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → High |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #13 |
Hi everyone,
Mario, that does indeed look like the relevant fix on the stable mailing list.
It reverts this commit:
commit 3c7e53c0d4b43ff
Author: Yifan Zhang <email address hidden>
Date: Tue Sep 28 15:42:35 2021 +0800
Subject: drm/amdgpu: init iommu after amdkfd device init
Link: https:/
It arrived in 5.15.150 stable, applied in 5.15.0-112-generic.
Interestingly enough, this was once applied during the 5.15 development cycle
in 2021, in 5.15-rc5:
commit 714d9e4574d5459
Author: Yifan Zhang <email address hidden>
Date: Tue Sep 28 15:42:35 2021 +0800
Subject: drm/amdgpu: init iommu after amdkfd device init
Link: https:/
Bizarre. It seems to have been removed back then as well.
Anyway, it seems it is on track to be once again reverted in the stable mailing list thread that Mario linked.
https://<email address hidden>/
To make sure this is the commit that is causing you issue, I have built you test kernels with the above revert commit applied.
There are builds for 22.04 and 20.04 HWE.
I only just uploaded them, so give them 3 hours from this message to build before trying to install. You can also check build status here:
https:/
Please note this package is NOT SUPPORTED by Canonical, and is for TESTING
PURPOSES ONLY. ONLY Install in a dedicated test environment.
Instructions to Install (On a focal or jammy system):
1) sudo add-apt-repository ppa:mruffell/
2) sudo apt update
3) sudo apt install linux-image-
4) sudo reboot
5) uname -rv
Look for "5.15.0-
Can you boot into this kernel and let me know if it fixes the problem? If it does, we will chime in upstream, and get this included, and we will land it in the next Ubuntu kernel release.
Just give the kernels about 3 hours to build first.
Thanks,
Matthew
Changed in linux (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → Matthew Ruffell (mruffell) |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #14 |
PS. Please remove the workaround "nomodeset" if you applied it before you try the test kernel. I really just want to know if the reverted patch fixes the issue.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tino (tinoh82) wrote : | #15 |
Same issue here.
My Grub file loks like this, any help?
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_
GRUB_TIMEOUT=10
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM=
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_
# Uncomment to get a beep at grub start
#GRUB_INIT_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tino (tinoh82) wrote : | #16 |
-it says fix released for linux (ubuntu). Where can i get it?
thanks
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fred Jupiter (fredjupiter) wrote : | #17 |
I had this problem, too, with a PC (I'm sorry, I can't access the PC; this is from my written/saved records):
CPU: AMD Ryzen 3 2200G, 4x 3.50GHz, boxed (YD2200C5FBBOX)
Graphics: AMD Vega 8
Kubuntu 22.04, fully updated today
Expected:
PC starts
Actual:
PC monitor stays black after logo of mainboard manufacturer.
Attempts at fixing this:
Because I had problems with startup where the addition of "nomodeset" in GRUB helped, I tried this. This time it did not help. The computer actually started - more than before - but got stuck at various stages of the boot process.
The PC would not fully start with kernel 5.15.0-112-generic.
I chose 5.15.0-107-generic in GRUB. 107 worked without a hitch.
At the moment the workaround is simply using 5.15.0-107-generic.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #18 |
Hi Tino,
It says Fix Released for Ubuntu, aka, the latest Ubuntu release, which is 24.10 Oracular, as it isn't affected. Maybe I should have marked it invalid in the first place.
Anyway, once someone tries the test kernel I built yesterday to see if it fixes the issue, I can go about getting the patch into Jammy's 5.15 kernel.
Thanks,
Matthew
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Simon (simonphillips762) wrote : | #19 |
This bug stopped my AMD 2200G booting and it stopped my HP thin client with AMD Embedded G-Series GX-420GI Radeon R7E cpu both running on the intergrated graphics.
Im trying to boot Lubuntu, i have reverted back to kernel 107 and all seems ok so far and found a redddit post on apt-mark hold and holding linux-image, linux-headers, linux-modules and linux-modules-
hope the extra info helps.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Xie Dongping (dongping-xie) wrote : | #20 |
Hi Matthew,
thanks for the quick fix. It works for me.
```
# uname -rv
5.15.0-112-generic #122+TEST206873
# inxi -G
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel
Device-2: Lite-On HP Webcam type: USB driver: uvcvideo
Display: server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetti
OpenGL: renderer: AMD Radeon Vega 3 Graphics (raven2 LLVM 15.0.7 DRM 3.42
5.15.
v: 4.6 Mesa 23.2.1-
```
Also tried `vkcube` and it also works. So I guess that this is fixed.
Thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #21 |
Hi Xie,
Thanks for trying the test kernel, and its great news that we have identified the fix. I'll write up a SRU template, and get the patch sent off to the kernel team today.
Thanks,
Matthew
summary: |
- Kernel update 5.15.0-112 might cause severe problems with specific AMD - GPUs + AMD GPUs fail with null pointer dereference when IOMMU enabled, leading + to black screen |
description: | updated |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #22 |
Hi everyone,
Patches are on the Ubuntu Kernel Team mailing list:
Cover letter:
https:/
Patch:
https:/
I will go talk to the kernel team now, I can't promise anything, but will try and get this prioritised.
I will write back with what they say.
Thanks,
Matthew
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Acru (aoellerer) wrote : | #23 |
Hey,
As of now, the update to 5.15.0-112 is still getting proposed in the update manager, meaning that with automatic updates your computer might fail from one boot to the next, would it be possible to pull it from there?
Best and thanks for all the work
Anton
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #24 |
Hi everyone,
An update:
Greg KH has picked up the patch and added it to upstream stable now:
https:/
https:/
I suppose we can drop the UBUNTU: SAUCE tags.
I talked to Stefan Bader on the Kernel Team. His current feeling is that they might respin the -generic kernels before the release of the current cycle (2024.06.10 as per https:/
I'll follow up with the Kernel Team in a couple days.
Thanks,
Matthew
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Orlando (peteola) wrote : Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen | #25 |
Hi Matthew, I have an Acer Aspire 5 and running Linux Mint 21.2 Victoria
base: Ubuntu 22.04 jammy with AMD Ryzen 7 3700U with Radeon Vega.
I get the Black screen on boot after installing updates about a week ago.
will there be an update
that will come through the normal update manager ? I don't have programming
skills like many users
of Linux so that would much appreciated. Thank You !
On Thu, Jun 13, 2024 at 8:25 PM Matthew Ruffell <email address hidden>
wrote:
> Hi everyone,
>
> An update:
>
> Greg KH has picked up the patch and added it to upstream stable now:
>
> https:/
> https:/
>
> I suppose we can drop the UBUNTU: SAUCE tags.
>
> I talked to Stefan Bader on the Kernel Team. His current feeling is that
> they might respin the -generic kernels before the release of the current
> cycle (2024.06.10 as per https:/
> unsure. They might see what else comes up this cycle before they decide.
>
> I'll follow up with the Kernel Team in a couple days.
>
> Thanks,
> Matthew
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> In Progress
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Frazer Ross (frazer-r) wrote : | #26 |
Today Update Manager updated my Kernel from 5.15.0-107 to 5.15.0-112. Unfortunately 5.15.0-112 is not compatible with the AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx x 4 graphics processor in my HP model 14-dk0011na laptop resulting in a black screen.
Via GNU GRUB menu booted into Linux 5.15.0-107-generic from the list, and once into the OS using Update Manager removed 5.15.0-112.
The laptop now boots correctly using Kernel 5.15.0-107.
Looking forward to a fixed version of 5.15.0-112
How will novices like myself know when the 5.15.0-112 kernel is corrected without having to go through the above cycle every few days please?
Changed in linux (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #27 |
Hi everyone,
I spoke with Stefan Bader of the Kernel Team again. They are planning to include
the patch in a respin of the current 2024.06.10 SRU cycle. https:/
I will let you know once the kernel has been built and placed into -proposed for
verification.
But at this stage, as long as the respin occurs, this should be released the
week of 8th July, give or take a few days, if anything else pops up.
Thanks,
Matthew
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #28 |
Thank you Matthew.
Sent with Proton Mail secure email.
On Tuesday, June 18th, 2024 at 2:41 AM, Matthew Ruffell <email address hidden> wrote:
> Hi everyone,
>
> I spoke with Stefan Bader of the Kernel Team again. They are planning to include
> the patch in a respin of the current 2024.06.10 SRU cycle. https:/
>
> I will let you know once the kernel has been built and placed into -proposed for
> verification.
>
> But at this stage, as long as the respin occurs, this should be released the
> week of 8th July, give or take a few days, if anything else pops up.
>
> Thanks,
> Matthew
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Committed
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> local_pci_
> ? srso_return_
> pci_device_
> really_
> __driver_
> driver_
> __driver_
> ? __device_
> bus_for_
> driver_
> bus_add_
> ? srso_return_
> driver_
> __pci_register_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Acru (aoellerer) wrote : | #29 |
Hey,
After disabling the kernel update via the update manager, it now got installed again, again resulting in a not working system.
Isn't it possible to just completely remove this one version from the repo?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Orlando (peteola) wrote : | #30 |
How do we fix this?
On Tue, Jun 18, 2024 at 9:40 AM Acru <email address hidden> wrote:
> Hey,
> After disabling the kernel update via the update manager, it now got
> installed again, again resulting in a not working system.
> Isn't it possible to just completely remove this one version from the repo?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Committed
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> local_pci_
> ? srso_return_
> pci_device_
> really_
> __driver_
> driver_
> __driver_
> ? __device_
> bus_for_
> driver_
> bus_add_
> ? srso_return_
> driver_
> __pci_register_
> amdgpu_
> ? 0xffffffffc0e0b000
> do_one_
> ? srso_return_
> ? kmem_cache_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Willem Dreyer (willemdreyer) wrote : | #31 |
Hi all,
Same problem: No problem on 5.15.0-107.117 and 5.15.0-112.122 shows black screen after GRUB.
Same hardware: AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx
It's both funny and disappointing that a clinfo fix caused my first crash in 5 years on my daily driver.
In my opinion 5.15.0-112.122 should be blocked since it prevents multiple generations of Laptop and Desktop APUs from booting.
Special thanks to Barry K. for bisecting!
Thanks Armin W. for driving the fix and everyone else for your inputs.
Take care,
Willem
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #32 |
I just loaded Linux Mint Kernel 5.15.0-113 and it is not recognized at all, I'm told to load a Kernel first, press any key and I have to go back to the index of Linux Kernels and choose 5.15.0-107 to power up.
Thanks, Ralph
Sent with Proton Mail secure email.
On Tuesday, June 18th, 2024 at 7:12 AM, Roger Ramjet <email address hidden> wrote:
> Thank you Matthew.
>
>
>
>
> Sent with Proton Mail secure email.
>
>
> On Tuesday, June 18th, 2024 at 2:41 AM, Matthew Ruffell <email address hidden> wrote:
>
> > Hi everyone,
> >
> > I spoke with Stefan Bader of the Kernel Team again. They are planning to include
> > the patch in a respin of the current 2024.06.10 SRU cycle. https:/
> >
> > I will let you know once the kernel has been built and placed into -proposed for
> > verification.
> >
> > But at this stage, as long as the respin occurs, this should be released the
> > week of 8th July, give or take a few days, if anything else pops up.
> >
> > Thanks,
> > Matthew
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (2069485).
> > https:/
> >
> > Title:
> > AMD GPUs fail with null pointer dereference when IOMMU enabled,
> > leading to black screen
> >
> > Status in linux package in Ubuntu:
> > Fix Released
> > Status in linux source package in Jammy:
> > Fix Committed
> >
> > Bug description:
> > BugLink: https:/
> >
> > [Impact]
> >
> > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> > enabled, the system fails to boot correctly, and all users see is a
> > black screen.
> >
> > This is caused by a null pointer dereference when enabling the IOMMU
> > after the device has been initialised. It should happen the other way
> > around.
> >
> > AMD-Vi: AMD IOMMUv2 loaded and initialized
> > ...
> > amdgpu: Topology: Add APU node [0x15d8:0x1002]
> > kfd kfd: amdgpu: added device 1002:15d8
> > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> > ...
> > amdgpu 0000:06:00.0: amdgpu: amdgpu_
> > amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> > amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> > ...
> > BUG: kernel NULL pointer dereference, address: 000000000000013c
> > ...
> > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> > ...
> > RIP: 0010:amdgpu_
> > ...
> > Call Trace:
> > <TASK>
> >
> > ? srso_return_
> > ? show_trace_
> > ? show_trace_
> > ? dm_hw_fini+
> > ? show_regs.
> > ? __die_body.
> > ? __die+0x2b/0x37
> > ? page_fault_
> > ? srso_return_
> > ? do_user_
> > ? srso_return_
> > ? __free_
> > ? exc_page_
> > ? asm_exc_
> > ? amdgpu_
> > dm_hw_fini+
> > amdgpu_
> > amdgpu_
> > amdgpu_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Filip Średnicki (fsrednicki) wrote : | #33 |
I have noticed one more consequence of this bug, which can be very painful for those who are running thier own servers. Regardless that it is possible to connect by SSH and operate server normally, in my case when I was trying to reboot it whole power down procedure is carried properly up to closing of journal, but server freezes at the end and is not restarting, so if one is far away from infrastructure, can be in trouble. Fix with nomodeset is solving this restart issue.
My server is on Ryzen 3 + Radeon Vega integrated GPU.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fred Jupiter (fredjupiter) wrote : | #34 |
Yes, I agree with https:/
I updated to -113 today on Kubuntu 22.04. There is no improvement on -112.
The only things that is a workaround for me is "nomodeset" in GRUB or using the -107 kernel.
Updating to -113 kernel leaves black screen, backlit, on restart.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tino (tinoh82) wrote : | #35 |
Same on 5.15.0-113, no improvement. I still select 5.15.0-107 manually on boot screen. I hope this won't be removed because the 5.15.0-112 is gone now from GRUB
I Have an AMD Ryzen as well
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Thomas Løcke (thomasmonadic) wrote : | #36 |
I can confirm the same problem with linux-image-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Filip Średnicki (fsrednicki) wrote : | #37 |
Confirmed also by myself - 5.15.0-113 is not solving the problem...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #38 |
Hi everyone,
The patch was not present in 5.15.0-113-generic, as this kernel only contained
CVE fixes.
It should be in the next kernel update. Still waiting on the Kernel team to
respin.
I will write back as soon as we have a kernel tagged and in -proposed to test.
Thanks,
Matthew
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Richard Durso (reefland) wrote : | #39 |
Tried to use "nomodeset" or "amd_iommu=off" to GRUB_CMDLINE_
PC: HP T740 Thin PC / AMD Ryzen V1756B
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU
Subsystem: Hewlett-Packard Company Raven/Raven2 IOMMU
Flags: bus master, fast devsel, latency 0, IRQ 25
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
Subsystem: Intel Corporation Ethernet Controller I225-V
Flags: bus master, fast devsel, latency 0, IRQ 30, IOMMU group 7
Memory at fe700000 (32-bit, non-prefetchable) [size=1M]
Memory at fe800000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at fe600000 [disabled] [size=1M]
Kernel driver in use: igc
Kernel modules: igc
$ journalctl -b | grep amdgpu
Jun 28 18:00:20 k3s03 kernel: [drm] amdgpu kernel modesetting enabled.
Jun 28 18:00:20 k3s03 kernel: amdgpu: Topology: Add APU node [0x0:0x0]
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: enabling device (0106 -> 0107)
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
Jun 28 18:00:20 k3s03 kernel: amdgpu: ATOM BIOS: 113-RAVEN-111
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: vgaarb: deactivate vga console
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 256M 0x000000F400000000 - 0x000000F40FFFFFFF (256M used)
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
Jun 28 18:00:20 k3s03 kernel: [drm] amdgpu: 256M of VRAM memory ready
Jun 28 18:00:20 k3s03 kernel: [drm] amdgpu: 3072M of GTT memory ready.
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist
Jun 28 18:00:20 k3s03 kernel: amdgpu: hwmgr_sw_init smu backed is smu10_smu
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
Jun 28 18:00:20 k3s03 kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Jun 28 18:00:20 k3s03 kernel: amdgpu 000...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel (treki) wrote : | #40 |
Did I understand correctly that this bug will be fixed after kernel 5.15.0-113?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Orlando (peteola) wrote : | #41 |
Still no fix as of July 1, 2024. Have to boot manually with the 107 to get
my Acer laptop up and running. Hope someone can fix this problem soon.
Thanks for all the hard work on this issue.
On Mon, Jul 1, 2024 at 8:10 AM Daniel <email address hidden> wrote:
> Did I understand correctly that this bug will be fixed after kernel
> 5.15.0-113?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Committed
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> local_pci_
> ? srso_return_
> pci_device_
> really_
> __driver_
> driver_
> __driver_
> ? __device_
> bus_for_
> driver_
> bus_add_
> ? srso_return_
> driver_
> __pci_register_
> amdgpu_
> ? 0xffffffffc0e0b000
> do_one_
> ? srso_return_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #42 |
This bug is awaiting verification that the linux/5.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #44 |
Hi everyone,
The Kernel Team have respun the latest 5.15 kernel with the fix, and have placed
it into -proposed for verification.
Could someone more technically minded help test it and let me know if it fixes
the problem?
Instructions to Install (On a jammy system):
1) cat << EOF | sudo tee /etc/apt/
# Enable Ubuntu proposed archive
deb http://
EOF
2) sudo apt update
3) sudo apt install linux-image-
4) sudo rm /etc/apt/
5) sudo apt update
6) sudo reboot
7) uname -rv
5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024
Can you let me know if you can boot to your desktop and have a working screen?
We are still on track for a release to -updates next week sometime.
Thanks,
Matthew
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mathias Weyland (launchpad-weyland) wrote : | #45 |
Hello. I ran these instructions and was able to boot the -116 kernel on a laptop that was subject to this bug, i.e. where the -113 kernel booted into a black screen (HP EliteBook 735 G5).
Thank you for your efforts and regards!
Matt
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
H A Killenbeck (akillenb) wrote : | #46 |
followed your instructions, and the kernel update seems to work fine on
my system
On 7/3/24 11:50 PM, Matthew Ruffell wrote:
> Hi everyone,
>
> The Kernel Team have respun the latest 5.15 kernel with the fix, and have placed
> it into -proposed for verification.
>
> Could someone more technically minded help test it and let me know if it fixes
> the problem?
>
> Instructions to Install (On a jammy system):
> 1) cat << EOF | sudo tee /etc/apt/
> # Enable Ubuntu proposed archive
> deb http://
> EOF
> 2) sudo apt update
> 3) sudo apt install linux-image-
> 4) sudo rm /etc/apt/
> 5) sudo apt update
> 6) sudo reboot
> 7) uname -rv
> 5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024
>
> Can you let me know if you can boot to your desktop and have a working
> screen?
>
> We are still on track for a release to -updates next week sometime.
>
> Thanks,
> Matthew
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Ruffell (mruffell) wrote : | #48 |
Thanks for testing Matt, H.A.
I marked the bug as verified. We should be all good for a release to -updates
early next week. I'll write a new message as soon as the kernel has been
released for everyone.
Thanks,
Matthew
tags: |
added: verification-done-jammy-linux removed: verification-needed-jammy-linux |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Orlando (peteola) wrote : | #49 |
problem still exists after running your instructions. I am still only able
to boot live by booting into the 107.
On Thu, Jul 4, 2024 at 3:20 PM Matthew Ruffell <email address hidden>
wrote:
> Thanks for testing Matt, H.A.
>
> I marked the bug as verified. We should be all good for a release to
> -updates
> early next week. I'll write a new message as soon as the kernel has been
> released for everyone.
>
> Thanks,
> Matthew
>
> ** Tags removed: verification-
> ** Tags added: verification-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Committed
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> local_pci_
> ? srso_return_
> pci_device_
> really_
> __driver_
> driver_
> __driver_
> ? __device_
> bus_for_
> driver_
> bus_add_
> ? srso_return_
> dri...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Arno Mayrhofer (azrael3000) wrote : | #50 |
Works for me as well Matthew. Thanks for the fix.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
berni123 (bernd-bernd--zimmermann) wrote : | #51 |
I can confirm, proposed image -116 works without disabling amd_iommu:
berni@enterprise:~$ uname -rv
5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rfc (rfc0) wrote : | #52 |
Thank you Matthew & the kernel team,
Proposed image 5.15.0-116-generic resolves the issue on my machine without the need for any workarounds (disabling amd_iommu,)
$ uname -r -v
5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Michael Leetz (michael-leetz) wrote : | #53 |
Thank you for your effort.
When the update will be available officially?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Orlando (peteola) wrote : | #54 |
Still waiting for update, July 12 2024.
On Wed, Jul 10, 2024 at 4:55 AM Michael Leetz <email address hidden>
wrote:
> Thank you for your effort.
>
> When the update will be available officially?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Committed
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> local_pci_
> ? srso_return_
> pci_device_
> really_
> __driver_
> driver_
> __driver_
> ? __device_
> bus_for_
> driver_
> bus_add_
> ? srso_return_
> driver_
> __pci_register_
> amdgpu_
> ? 0xffffffffc0e0b000
> do_one_
> ? srso_return_
> ? kmem_cache_
> do_init_
> load_module+
> __do_sys_
>...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Emanuele Cisbani (cisba) wrote : | #55 |
I am also affected by this bug. Booting to kernel 5.15.0-113 produces a black screen. Kernel 5.15.0-107 works correctly. Here is information about my system:
Operating System: Ubuntu 22.04.4 LTS
GNOME Version: 42.9
Kernel Version: 5.15.0-107-generic (64-bit)
Processors: AMD® Ryzen 3 3200u with radeon vega mobile gfx × 4
Memory: 8 GiB of RAM
Graphics Processor: AMD® Radeon vega 3 graphics
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #56 |
This bug was fixed in the package linux - 5.15.0-116.126
---------------
linux (5.15.0-116.126) jammy; urgency=medium
* jammy/linux: 5.15.0-116.126 -proposed tracker (LP: #2071603)
* idxd: NULL pointer dereference reading wq op_config attribute (LP: #2069081)
- SAUCE: dmaengine: idxd: set is_visible member of idxd_wq_
* AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen (LP: #2068738)
- SAUCE: Revert "drm/amdgpu: init iommu after amdkfd device init"
linux (5.15.0-115.125) jammy; urgency=medium
* jammy/linux: 5.15.0-115.125 -proposed tracker (LP: #2068396)
* Packaging resync (LP: #1786013)
- [Packaging] debian.
(
* Jammy update: v5.15.158 upstream stable release (LP: #2067974)
- smb: client: fix rename(2) regression against samba
- cifs: reinstate original behavior again for forceuid/forcegid
- HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev->devc
- HID: logitech-dj: allow mice to use all types of reports
- arm64: dts: rockchip: enable internal pull-up on Q7_USB_ID for RK3399 Puma
- arm64: dts: rockchip: fix alphabetical ordering RK3399 puma
- arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for RK3399 Puma
- arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts
- arm64: dts: mediatek: mt8183: Add power-domains properity to mfgcfg
- arm64: dts: mediatek: mt7622: add support for coherent DMA
- arm64: dts: mediatek: mt7622: introduce nodes for Wireless Ethernet Dispatch
- arm64: dts: mediatek: mt7622: fix clock controllers
- arm64: dts: mediatek: mt7622: fix IR nodename
- arm64: dts: mediatek: mt7622: fix ethernet controller "compatible"
- arm64: dts: mediatek: mt7622: drop "reset-names" from thermal block
- arm64: dts: mediatek: mt2712: fix validation errors
- ARC: [plat-hsdk]: Remove misplaced interrupt-cells property
- wifi: iwlwifi: mvm: remove old PASN station when adding a new one
- wifi: iwlwifi: mvm: return uid from iwl_mvm_
- vxlan: drop packets from invalid src-address
- mlxsw: core: Unregister EMAD trap using FORWARD action
- icmp: prevent possible NULL dereferences from icmp_build_probe()
- bridge/
- NFC: trf7970a: disable all regulators on removal
- ipv4: check for NULL idev in ip_route_use_hint()
- net: usb: ax88179_178a: stop lying about skb->truesize
- net: gtp: Fix Use-After-Free in gtp_dellink
- ipvs: Fix checksumming on GSO of SCTP packets
- net: openvswitch: Fix Use-After-Free in ovs_ct_exit
- mlxsw: spectrum_acl_tcam: Fix race during rehash delayed work
- mlxsw: spectrum_acl_tcam: Fix possible use-after-free during activity update
- mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash
- mlxsw: spectrum_acl_tcam: Rate limit error message
- mlxsw: spectrum_acl_tcam: Fix memory leak during rehash
- mlxsw: spectrum_acl_tcam: Fix warning during rehash
- mlxsw: spectrum_acl_tcam: Fix incorrect list API usage
...
Changed in linux (Ubuntu Jammy): | |
status: | Fix Committed → Fix Released |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #57 |
This bug is awaiting verification that the linux-lowlatenc
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-lowlatency-v2 verification-needed-jammy-linux-lowlatency |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #58 |
This bug is awaiting verification that the linux-hwe-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-focal-linux-hwe-5.15-v2 verification-needed-focal-linux-hwe-5.15 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #59 |
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
Not sure what to do now.
Thanks, Ralph Goe
Sent with Proton Mail secure email.
On Monday, July 15th, 2024 at 4:22 AM, Launchpad Bug Tracker <email address hidden> wrote:
> This bug was fixed in the package linux - 5.15.0-116.126
>
> ---------------
> linux (5.15.0-116.126) jammy; urgency=medium
>
> * jammy/linux: 5.15.0-116.126 -proposed tracker (LP: #2071603)
>
> * idxd: NULL pointer dereference reading wq op_config attribute (LP: #2069081)
> - SAUCE: dmaengine: idxd: set is_visible member of idxd_wq_
>
> * AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
> black screen (LP: #2068738)
> - SAUCE: Revert "drm/amdgpu: init iommu after amdkfd device init"
>
> linux (5.15.0-115.125) jammy; urgency=medium
>
> * jammy/linux: 5.15.0-115.125 -proposed tracker (LP: #2068396)
>
> * Packaging resync (LP: #1786013)
> - [Packaging] debian.
> (main/2024.06.10)
>
> * Jammy update: v5.15.158 upstream stable release (LP: #2067974)
> - smb: client: fix rename(2) regression against samba
> - cifs: reinstate original behavior again for forceuid/forcegid
> - HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev->devc
>
> - HID: logitech-dj: allow mice to use all types of reports
> - arm64: dts: rockchip: enable internal pull-up on Q7_USB_ID for RK3399 Puma
> - arm64: dts: rockchip: fix alphabetical ordering RK3399 puma
> - arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for RK3399 Puma
> - arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts
> - arm64: dts: mediatek: mt8183: Add power-domains properity to mfgcfg
> - arm64: dts: mediatek: mt7622: add support for coherent DMA
> - arm64: dts: mediatek: mt7622: introduce nodes for Wireless Ethernet Dispatch
> - arm64: dts: mediatek: mt7622: fix clock controllers
> - arm64: dts: mediatek: mt7622: fix IR nodename
> - arm64: dts: mediatek: mt7622: fix ethernet controller "compatible"
> - arm64: dts: mediatek: mt7622: drop "reset-names" from thermal block
> - arm64: dts: mediatek: mt2712: fix validation errors
> - ARC: [plat-hsdk]: Remove misplaced interrupt-cells property
> - wifi: iwlwifi: mvm: remove old PASN station when adding a new one
> - wifi: iwlwifi: mvm: return uid from iwl_mvm_
> - vxlan: drop packets from invalid src-address
> - mlxsw: core: Unregister EMAD trap using FORWARD action
> - icmp: prevent possible NULL dereferences from icmp_build_probe()
> - bridge/
> - NFC: trf7970a: disable all regulators on removal
> - ipv4: check for NULL idev in ip_route_use_hint()
> - net: usb: ax88179_178a: stop lying about skb->truesize
>
> - net: gtp: Fix Use-After-Free in gtp_dellink
> - ipvs: Fix checksumming on GSO of SCTP packets
> - net: openvswitch: Fix Use-After-Free in ovs_ct_exit
> - mlxsw: spectrum_acl_tcam: Fix race during rehash delayed work
> - mlxsw: spectrum_acl_tcam: Fix possible use-after-free during activity update
> - mlxsw: spectrum_acl_tcam: Fix possible use-a...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : Fw: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen | #60 |
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
If I can give you more info. let me know.
Thanks, Ralph Goe
Sent with Proton Mail secure email.
------- Forwarded Message -------
From: Roger Ramjet <email address hidden>
Date: On Monday, July 15th, 2024 at 8:33 AM
Subject: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
To: Bug 2068738 <email address hidden>
> Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
> error: file `/boot/' not found.
>
>
> Not sure what to do now.
>
> Thanks, Ralph Goe
>
>
>
>
> Sent with Proton Mail secure email.
>
>
> On Monday, July 15th, 2024 at 4:22 AM, Launchpad Bug Tracker <email address hidden> wrote:
>
> > This bug was fixed in the package linux - 5.15.0-116.126
> >
> > ---------------
> > linux (5.15.0-116.126) jammy; urgency=medium
> >
> > * jammy/linux: 5.15.0-116.126 -proposed tracker (LP: #2071603)
> >
> > * idxd: NULL pointer dereference reading wq op_config attribute (LP: #2069081)
> > - SAUCE: dmaengine: idxd: set is_visible member of idxd_wq_
> >
> > * AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
> > black screen (LP: #2068738)
> > - SAUCE: Revert "drm/amdgpu: init iommu after amdkfd device init"
> >
> > linux (5.15.0-115.125) jammy; urgency=medium
> >
> > * jammy/linux: 5.15.0-115.125 -proposed tracker (LP: #2068396)
> >
> > * Packaging resync (LP: #1786013)
> > - [Packaging] debian.
> > (main/2024.06.10)
> >
> > * Jammy update: v5.15.158 upstream stable release (LP: #2067974)
> > - smb: client: fix rename(2) regression against samba
> > - cifs: reinstate original behavior again for forceuid/forcegid
> > - HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev->devc
> >
> > - HID: logitech-dj: allow mice to use all types of reports
> > - arm64: dts: rockchip: enable internal pull-up on Q7_USB_ID for RK3399 Puma
> > - arm64: dts: rockchip: fix alphabetical ordering RK3399 puma
> > - arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for RK3399 Puma
> > - arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts
> > - arm64: dts: mediatek: mt8183: Add power-domains properity to mfgcfg
> > - arm64: dts: mediatek: mt7622: add support for coherent DMA
> > - arm64: dts: mediatek: mt7622: introduce nodes for Wireless Ethernet Dispatch
> > - arm64: dts: mediatek: mt7622: fix clock controllers
> > - arm64: dts: mediatek: mt7622: fix IR nodename
> > - arm64: dts: mediatek: mt7622: fix ethernet controller "compatible"
> > - arm64: dts: mediatek: mt7622: drop "reset-names" from thermal block
> > - arm64: dts: mediatek: mt2712: fix validation errors
> > - ARC: [plat-hsdk]: Remove misplaced interrupt-cells property
> > - wifi: iwlwifi: mvm: remove old PASN station when adding a new one
> > - wif...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #61 |
- List of Kernels.png Edit (55.6 KiB, image/png; name="List of Kernels.png")
I've attached a pic of Update Manager showing Kernels installed.
Sent with Proton Mail secure email.
------- Forwarded Message -------
From: Roger Ramjet <email address hidden>
Date: On Monday, July 15th, 2024 at 8:42 AM
Subject: Fw: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
To: Bug 2068738 <email address hidden>
> I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
>
> The Kernel is loaded and installed but "not found"
> Then another window opens and I must choose "Boot from next volume"
> Then I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
>
> If I can give you more info. let me know.
>
> Thanks, Ralph Goe
>
>
>
>
> Sent with Proton Mail secure email.
>
>
> ------- Forwarded Message -------
> From: Roger Ramjet <email address hidden>
>
> Date: On Monday, July 15th, 2024 at 8:33 AM
> Subject: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
> To: Bug 2068738 <email address hidden>
>
>
>
> > Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
> > error: file `/boot/' not found.
> >
> > Not sure what to do now.
> >
> > Thanks, Ralph Goe
> >
> > Sent with Proton Mail secure email.
> >
> > On Monday, July 15th, 2024 at 4:22 AM, Launchpad Bug Tracker <email address hidden> wrote:
> >
> > > This bug was fixed in the package linux - 5.15.0-116.126
> > >
> > > ---------------
> > > linux (5.15.0-116.126) jammy; urgency=medium
> > >
> > > * jammy/linux: 5.15.0-116.126 -proposed tracker (LP: #2071603)
> > >
> > > * idxd: NULL pointer dereference reading wq op_config attribute (LP: #2069081)
> > > - SAUCE: dmaengine: idxd: set is_visible member of idxd_wq_
> > >
> > > * AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
> > > black screen (LP: #2068738)
> > > - SAUCE: Revert "drm/amdgpu: init iommu after amdkfd device init"
> > >
> > > linux (5.15.0-115.125) jammy; urgency=medium
> > >
> > > * jammy/linux: 5.15.0-115.125 -proposed tracker (LP: #2068396)
> > >
> > > * Packaging resync (LP: #1786013)
> > > - [Packaging] debian.
> > > (main/2024.06.10)
> > >
> > > * Jammy update: v5.15.158 upstream stable release (LP: #2067974)
> > > - smb: client: fix rename(2) regression against samba
> > > - cifs: reinstate original behavior again for forceuid/forcegid
> > > - HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev->devc
> > >
> > > - HID: logitech-dj: allow mice to use all types of reports
> > > - arm64: dts: rockchip: enable internal pull-up on Q7_USB_ID for RK3399 Puma
> > > - arm64: dts: rockchip: fix alphabetical ordering RK3399 puma
> > > - arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for RK3399 Puma
> > > - arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts
> > > - arm64: dts: mediatek: mt8183: Add power-domains properity to mfgcfg
> > > - arm64: dts: mediatek: mt7622: add support for coherent DMA
> > > - arm64: dts: mediatek: ...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
73nlp (73nlp) wrote : | #62 |
- kernel 5.15.0-116.126.odt Edit (50.7 KiB, application/vnd.oasis.opendocument.text)
New kernel 5.15.0-116.126 booted nominally after using Mint update manager to install. Attachment screenshot and system details.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel (treki) wrote : | #63 |
It works for me too (Kernel 116).
Good work :D
My OS:
LinuxMint 21.3mate
CPU: AMD Ryzen 5 3400G with Radeon Vega Graphics × 8
Graphics: AMD Radeon Vega 11 Graphics (raven, LLVM 15.0.7, DRM 3.42, 5.15.0-116-generic)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #64 |
This bug is awaiting verification that the linux-ibm/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-ibm-v2 verification-needed-jammy-linux-ibm |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #65 |
This bug is awaiting verification that the linux-gkeop/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-gkeop-v2 verification-needed-jammy-linux-gkeop |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #66 |
This bug is awaiting verification that the linux-azure/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #67 |
This bug is awaiting verification that the linux-fips/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-fips-v2 verification-needed-jammy-linux-fips |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #68 |
This bug is awaiting verification that the linux-ibm-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-ibm-gt-v2 verification-needed-jammy-linux-ibm-gt |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #69 |
This bug is awaiting verification that the linux-kvm/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-kvm-v2 verification-needed-jammy-linux-kvm |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #70 |
This bug is awaiting verification that the linux-intel-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-intel-iotg-v2 verification-needed-jammy-linux-intel-iotg |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #71 |
This bug is awaiting verification that the linux-realtime/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-realtime-v2 verification-needed-jammy-linux-realtime |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #72 |
This bug is awaiting verification that the linux-riscv-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-focal-linux-riscv-5.15-v2 verification-needed-focal-linux-riscv-5.15 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : verification-failed-focal-linux-riscv-5.15 | #73 |
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
This new Kernel is not listed at this window, not sure why not, seems it should be.
If I can give you more info. let me know.
Ralph Goe
Sent with Proton Mail secure email.
On Tuesday, July 16th, 2024 at 7:13 AM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-
> riscv-5.
> problem. Please test the kernel and update this bug with the results. If
> the problem is solved, change the tag 'verification-
> riscv-5.15' to 'verification-
> problem still exists, change the tag 'verification-
> riscv-5.15' to 'verification-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_oops+...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #74 |
This bug is awaiting verification that the linux-gke/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-gke-v2 verification-needed-jammy-linux-gke |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : verification-failed-jammy-linux-gke | #75 |
Not sure if I'm replying correctly, this bug fix did not help me.
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
This new Kernel is not listed at this window, not sure why not, seems it should be.
If I can give you more info. let me know.
Ralph Goe
Sent with Proton Mail secure email.
On Tuesday, July 16th, 2024 at 9:56 AM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-gke/
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-
> linux-gke'. If the problem still exists, change the tag 'verification-
> needed-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #76 |
This bug is awaiting verification that the linux-nvidia/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-nvidia-v2 verification-needed-jammy-linux-nvidia |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen | #77 |
I don't know if you're getting my response but this fix has not fixed my computer.
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
This new Kernel is not listed at this window, not sure why not, seems it should be.
If I can give you more info. let me know.
Ralph Goe
Sent with Proton Mail secure email.
On Tuesday, July 16th, 2024 at 3:48 PM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-nvidia/
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-
> jammy-linux-
> 'verification-
> linux-nvidia'.
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : verification-failed-jammy- linux-nvidia | #78 |
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
This new Kernel is not listed at this window, not sure why not, seems it should be.
If I can give you more info. let me know.
Ralph Goe
Sent with Proton Mail secure email.
On Tuesday, July 16th, 2024 at 3:48 PM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-nvidia/
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-
> jammy-linux-
> 'verification-
> linux-nvidia'.
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_r...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #79 |
This bug is awaiting verification that the linux-gcp/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-gcp-v2 verification-needed-jammy-linux-gcp |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Erv Bendiks (erv-bendiks) wrote : Re: [Bug 2068738] verification-failed-jammy-linux-gke | #80 |
I just booted my AMD 3200G Linux Mint box with 5.15.0-116-generic and it
didn't hang with a blank screen. This box passed test.
On Tue, Jul 16, 2024 at 11:00 AM Roger Ramjet <email address hidden>
wrote:
> Not sure if I'm replying correctly, this bug fix did not help me.
>
> Unfortunately, I still have the same problem, after updating, I power down
> and restart, I get:
> error: file `/boot/' not found.
>
> I view the Kernels in the update manager, it shows 5.15.0-116 is
> "installed" and "supported until April 2027"
>
> The Kernel is loaded and installed but "not found"
> Then another window opens and I must choose "Boot from next volume"
> Then another window where I'm given the choice of booting from
> 5.15.0-107-generic (on /dev/sda5)
> This new Kernel is not listed at this window, not sure why not, seems it
> should be.
>
> If I can give you more info. let me know.
>
> Ralph Goe
>
>
>
> Sent with Proton Mail secure email.
>
> On Tuesday, July 16th, 2024 at 9:56 AM, Ubuntu Kernel Bot
> <email address hidden> wrote:
>
> > This bug is awaiting verification that the linux-gke/
> > kernel in -proposed solves the problem. Please test the kernel and
> > update this bug with the results. If the problem is solved, change the
> > tag 'verification-
> > linux-gke'. If the problem still exists, change the tag 'verification-
> > needed-
> >
> >
> > If verification is not done by 5 working days from today, this fix will
> > be dropped from the source code, and this bug will be closed.
> >
> >
> > See https:/
> > to enable and use -proposed. Thank you!
> >
> >
> > ** Tags added: kernel-
> verification-
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (2069485).
> > https:/
> >
> > Title:
> > AMD GPUs fail with null pointer dereference when IOMMU enabled,
> > leading to black screen
> >
> > Status in linux package in Ubuntu:
> > Fix Released
> > Status in linux source package in Jammy:
> > Fix Released
> >
> > Bug description:
> > BugLink: https:/
> >
> > [Impact]
> >
> > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> > enabled, the system fails to boot correctly, and all users see is a
> > black screen.
> >
> > This is caused by a null pointer dereference when enabling the IOMMU
> > after the device has been initialised. It should happen the other way
> > around.
> >
> > AMD-Vi: AMD IOMMUv2 loaded and initialized
> > ...
> > amdgpu: Topology: Add APU node [0x15d8:0x1002]
> > kfd kfd: amdgpu: added device 1002:15d8
> > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> > ...
> > amdgpu 0000:06:00.0: amdgpu: amdgpu_
> > amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> > amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> > ...
> > BUG: kernel NULL pointer dereference, address: 000000000000013c
> > ...
> > CPU: 1 PID: 223 Co...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #81 |
Why in my Update Manager when viewing the Kernels, 5.15.0-116 is shown as "Installed" but not "Active"?
And when powering up I get: "error: file `/boot/' not found"
Maybe this is the problem and not the new Kernel?
Thanks, Ralph
Sent with Proton Mail secure email.
On Tuesday, July 16th, 2024 at 7:02 PM, Erv Bendiks <email address hidden> wrote:
> I just booted my AMD 3200G Linux Mint box with 5.15.0-116-generic and it
> didn't hang with a blank screen. This box passed test.
>
> On Tue, Jul 16, 2024 at 11:00 AM Roger Ramjet <email address hidden>
>
> wrote:
>
> > Not sure if I'm replying correctly, this bug fix did not help me.
> >
> > Unfortunately, I still have the same problem, after updating, I power down
> > and restart, I get:
> > error: file `/boot/' not found.
> >
> > I view the Kernels in the update manager, it shows 5.15.0-116 is
> > "installed" and "supported until April 2027"
> >
> > The Kernel is loaded and installed but "not found"
> > Then another window opens and I must choose "Boot from next volume"
> > Then another window where I'm given the choice of booting from
> > 5.15.0-107-generic (on /dev/sda5)
> > This new Kernel is not listed at this window, not sure why not, seems it
> > should be.
> >
> > If I can give you more info. let me know.
> >
> > Ralph Goe
> >
> > Sent with Proton Mail secure email.
> >
> > On Tuesday, July 16th, 2024 at 9:56 AM, Ubuntu Kernel Bot
> > <email address hidden> wrote:
> >
> > > This bug is awaiting verification that the linux-gke/
> > > kernel in -proposed solves the problem. Please test the kernel and
> > > update this bug with the results. If the problem is solved, change the
> > > tag 'verification-
> > > linux-gke'. If the problem still exists, change the tag 'verification-
> > > needed-
> > >
> > > If verification is not done by 5 working days from today, this fix will
> > > be dropped from the source code, and this bug will be closed.
> > >
> > > See https:/
> > > to enable and use -proposed. Thank you!
> > >
> > > ** Tags added: kernel-
> > > verification-
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (2069485).
> > > https:/
> > >
> > > Title:
> > > AMD GPUs fail with null pointer dereference when IOMMU enabled,
> > > leading to black screen
> > >
> > > Status in linux package in Ubuntu:
> > > Fix Released
> > > Status in linux source package in Jammy:
> > > Fix Released
> > >
> > > Bug description:
> > > BugLink: https:/
> > >
> > > [Impact]
> > >
> > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> > > enabled, the system fails to boot correctly, and all users see is a
> > > black screen.
> > >
> > > This is caused by a null pointer dereference when enabling the IOMMU
> > > after the device has been initialised. It should happen the other way
> > > around.
> > ...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fred Jupiter (fredjupiter) wrote : | #82 |
Yes, 5.15.0-116-generic fixes my problem as well. Everything running perfectly without "nomodeset".
I had reported my problem here; this bug is fixed for me:
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tom Smith (uom) wrote : | #83 |
I tested 5.15.0-116 on a HP ProDesk 405 G6 Desktop running Mint 20.1 (using linux-hwe for the 5.15 kernel) and 5.15.0-116 resolved the problem. Thanks all :)
(Now I just have to wait for it to hit general release so I can update the other 20 or so I'm responsible for ;)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #84 |
This bug is awaiting verification that the linux-oracle/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-oracle-v2 verification-needed-jammy-linux-oracle |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #85 |
This bug is awaiting verification that the linux-raspi/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #86 |
This bug is awaiting verification that the linux-bluefield
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #87 |
This bug is awaiting verification that the linux-aws/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-aws-v2 verification-needed-jammy-linux-aws |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : verification-failed-jammy-linux-aws | #88 |
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
This new Kernel is not listed at this window, not sure why not, seems it should be.
If I can give you more info. let me know.
Ralph Goe
Sent with Proton Mail secure email.
On Wednesday, July 17th, 2024 at 11:29 PM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-aws/
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-
> linux-aws'. If the problem still exists, change the tag 'verification-
> needed-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : verification-needed-jammy-linux-bluefield | #89 |
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
This new Kernel is not listed at this window, not sure why not, seems it should be.
If I can give you more info. let me know.
Ralph Goe
Sent with Proton Mail secure email.
On Wednesday, July 17th, 2024 at 9:59 PM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-
> bluefield/
> test the kernel and update this bug with the results. If the problem is
> solved, change the tag 'verification-
> 'verification-
> change the tag 'verification-
> 'verification-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_oops+...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #90 |
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
This new Kernel is not listed at this window, not sure why not, seems it should be.
If I can give you more info. let me know.
Ralph Goe
Sent with Proton Mail secure email.
On Tuesday, July 16th, 2024 at 9:56 AM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-gke/
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-
> linux-gke'. If the problem still exists, change the tag 'verification-
> needed-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
>...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : verification-failed-jammy-linux-azure | #91 |
Unfortunately, I still have the same problem, after updating, I power down and restart, I get:
error: file `/boot/' not found.
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027"
The Kernel is loaded and installed but "not found"
Then another window opens and I must choose "Boot from next volume"
Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5)
This new Kernel is not listed at this window, not sure why not, seems it should be.
If I can give you more info. let me know.
Ralph Goe
Sent with Proton Mail secure email.
On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-azure/
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-
> linux-azure'. If the problem still exists, change the tag 'verification-
> needed-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_th...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Orlando (peteola) wrote : Re: [Bug 2068738] verification-failed-jammy-linux-azure | #92 |
Ok Black screen now fixed after "update Manger" sent new update on
7/17/2024. Thank You Linux team !
On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet <email address hidden>
wrote:
> Unfortunately, I still have the same problem, after updating, I power down
> and restart, I get:
> error: file `/boot/' not found.
>
> I view the Kernels in the update manager, it shows 5.15.0-116 is
> "installed" and "supported until April 2027"
>
> The Kernel is loaded and installed but "not found"
> Then another window opens and I must choose "Boot from next volume"
> Then another window where I'm given the choice of booting from
> 5.15.0-107-generic (on /dev/sda5)
> This new Kernel is not listed at this window, not sure why not, seems it
> should be.
>
> If I can give you more info. let me know.
>
> Ralph Goe
>
>
>
> Sent with Proton Mail secure email.
>
> On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot
> <email address hidden> wrote:
>
> > This bug is awaiting verification that the linux-azure/
> > kernel in -proposed solves the problem. Please test the kernel and
> > update this bug with the results. If the problem is solved, change the
> > tag 'verification-
> > linux-azure'. If the problem still exists, change the tag 'verification-
> > needed-
> >
> >
> > If verification is not done by 5 working days from today, this fix will
> > be dropped from the source code, and this bug will be closed.
> >
> >
> > See https:/
> > to enable and use -proposed. Thank you!
> >
> >
> > ** Tags added: kernel-
> verification-
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (2069485).
> > https:/
> >
> > Title:
> > AMD GPUs fail with null pointer dereference when IOMMU enabled,
> > leading to black screen
> >
> > Status in linux package in Ubuntu:
> > Fix Released
> > Status in linux source package in Jammy:
> > Fix Released
> >
> > Bug description:
> > BugLink: https:/
> >
> > [Impact]
> >
> > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> > enabled, the system fails to boot correctly, and all users see is a
> > black screen.
> >
> > This is caused by a null pointer dereference when enabling the IOMMU
> > after the device has been initialised. It should happen the other way
> > around.
> >
> > AMD-Vi: AMD IOMMUv2 loaded and initialized
> > ...
> > amdgpu: Topology: Add APU node [0x15d8:0x1002]
> > kfd kfd: amdgpu: added device 1002:15d8
> > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> > ...
> > amdgpu 0000:06:00.0: amdgpu: amdgpu_
> > amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> > amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> > ...
> > BUG: kernel NULL pointer dereference, address: 000000000000013c
> > ...
> > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> > ...
> > RIP: 001...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Orlando (peteola) wrote : Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen | #93 |
The 7/17/24 update fixed my problem. Thank You Linux Team !
On Wed, Jul 17, 2024 at 9:35 PM Ubuntu Kernel Bot <
<email address hidden>> wrote:
> This bug is awaiting verification that the linux-aws/
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-
> linux-aws'. If the problem still exists, change the tag 'verification-
> needed-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
> verification-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> local_pci_p...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : Re: [Bug 2068738] verification-failed-jammy-linux-azure | #94 |
Why does the updated kernel show installed but not active, I'm still having a problem?
Sent with Proton Mail secure email.
On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando <email address hidden> wrote:
> Ok Black screen now fixed after "update Manger" sent new update on
> 7/17/2024. Thank You Linux team !
>
>
> On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet <email address hidden>
>
> wrote:
>
> > Unfortunately, I still have the same problem, after updating, I power down
> > and restart, I get:
> > error: file `/boot/' not found.
> >
> > I view the Kernels in the update manager, it shows 5.15.0-116 is
> > "installed" and "supported until April 2027"
> >
> > The Kernel is loaded and installed but "not found"
> > Then another window opens and I must choose "Boot from next volume"
> > Then another window where I'm given the choice of booting from
> > 5.15.0-107-generic (on /dev/sda5)
> > This new Kernel is not listed at this window, not sure why not, seems it
> > should be.
> >
> > If I can give you more info. let me know.
> >
> > Ralph Goe
> >
> > Sent with Proton Mail secure email.
> >
> > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot
> > <email address hidden> wrote:
> >
> > > This bug is awaiting verification that the linux-azure/
> > > kernel in -proposed solves the problem. Please test the kernel and
> > > update this bug with the results. If the problem is solved, change the
> > > tag 'verification-
> > > linux-azure'. If the problem still exists, change the tag 'verification-
> > > needed-
> > >
> > > If verification is not done by 5 working days from today, this fix will
> > > be dropped from the source code, and this bug will be closed.
> > >
> > > See https:/
> > > to enable and use -proposed. Thank you!
> > >
> > > ** Tags added: kernel-
> > > verification-
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (2069485).
> > > https:/
> > >
> > > Title:
> > > AMD GPUs fail with null pointer dereference when IOMMU enabled,
> > > leading to black screen
> > >
> > > Status in linux package in Ubuntu:
> > > Fix Released
> > > Status in linux source package in Jammy:
> > > Fix Released
> > >
> > > Bug description:
> > > BugLink: https:/
> > >
> > > [Impact]
> > >
> > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> > > enabled, the system fails to boot correctly, and all users see is a
> > > black screen.
> > >
> > > This is caused by a null pointer dereference when enabling the IOMMU
> > > after the device has been initialised. It should happen the other way
> > > around.
> > >
> > > AMD-Vi: AMD IOMMUv2 loaded and initialized
> > > ...
> > > amdgpu: Topology: Add APU node [0x15d8:0x1002]
> > > kfd kfd: amdgpu: added device 1002:15d8
> > > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Erv Bendiks (erv-bendiks) wrote : | #95 |
@RogerRamjet> Do you have motherboard,CPU and OS information to share?
On Thu, Jul 18, 2024 at 6:45 PM Roger Ramjet <email address hidden>
wrote:
> Why does the updated kernel show installed but not active, I'm still
> having a problem?
>
>
>
> Sent with Proton Mail secure email.
>
> On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando
> <email address hidden> wrote:
>
> > Ok Black screen now fixed after "update Manger" sent new update on
> > 7/17/2024. Thank You Linux team !
> >
> >
> > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet <email address hidden>
> >
> > wrote:
> >
> > > Unfortunately, I still have the same problem, after updating, I power
> down
> > > and restart, I get:
> > > error: file `/boot/' not found.
> > >
> > > I view the Kernels in the update manager, it shows 5.15.0-116 is
> > > "installed" and "supported until April 2027"
> > >
> > > The Kernel is loaded and installed but "not found"
> > > Then another window opens and I must choose "Boot from next volume"
> > > Then another window where I'm given the choice of booting from
> > > 5.15.0-107-generic (on /dev/sda5)
> > > This new Kernel is not listed at this window, not sure why not, seems
> it
> > > should be.
> > >
> > > If I can give you more info. let me know.
> > >
> > > Ralph Goe
> > >
> > > Sent with Proton Mail secure email.
> > >
> > > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot
> > > <email address hidden> wrote:
> > >
> > > > This bug is awaiting verification that the linux-azure/
> > > > kernel in -proposed solves the problem. Please test the kernel and
> > > > update this bug with the results. If the problem is solved, change
> the
> > > > tag 'verification-
> 'verification-
> > > > linux-azure'. If the problem still exists, change the tag
> 'verification-
> > > > needed-
> > > >
> > > > If verification is not done by 5 working days from today, this fix
> will
> > > > be dropped from the source code, and this bug will be closed.
> > > >
> > > > See https:/
> documentation how
> > > > to enable and use -proposed. Thank you!
> > > >
> > > > ** Tags added: kernel-
> > > > verification-
> > > >
> > > > --
> > > > You received this bug notification because you are subscribed to a
> > > > duplicate bug report (2069485).
> > > > https:/
> > > >
> > > > Title:
> > > > AMD GPUs fail with null pointer dereference when IOMMU enabled,
> > > > leading to black screen
> > > >
> > > > Status in linux package in Ubuntu:
> > > > Fix Released
> > > > Status in linux source package in Jammy:
> > > > Fix Released
> > > >
> > > > Bug description:
> > > > BugLink: https:/
> > > >
> > > > [Impact]
> > > >
> > > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> > > > enabled, the system fails to boot correctly, and all users see is a
> > > > black screen.
> > > >
> > > > This is caused by a null pointer dereference when enabling the IOMMU
> > > > after the ...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #96 |
- System information.odt Edit (84.1 KiB, application/vnd.oasis.opendocument.text; name="System information.odt")
Good morning,
Yes I do, file is attached.
Thanks,
Ralph Goe
Sent with Proton Mail secure email.
On Thursday, July 18th, 2024 at 9:58 PM, Erv Bendiks <email address hidden> wrote:
> @RogerRamjet> Do you have motherboard,CPU and OS information to share?
>
>
>
> On Thu, Jul 18, 2024 at 6:45 PM Roger Ramjet <email address hidden>
>
> wrote:
>
> > Why does the updated kernel show installed but not active, I'm still
> > having a problem?
> >
> > Sent with Proton Mail secure email.
> >
> > On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando
> > <email address hidden> wrote:
> >
> > > Ok Black screen now fixed after "update Manger" sent new update on
> > > 7/17/2024. Thank You Linux team !
> > >
> > > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet <email address hidden>
> > >
> > > wrote:
> > >
> > > > Unfortunately, I still have the same problem, after updating, I power
> > > > down
> > > > and restart, I get:
> > > > error: file `/boot/' not found.
> > > >
> > > > I view the Kernels in the update manager, it shows 5.15.0-116 is
> > > > "installed" and "supported until April 2027"
> > > >
> > > > The Kernel is loaded and installed but "not found"
> > > > Then another window opens and I must choose "Boot from next volume"
> > > > Then another window where I'm given the choice of booting from
> > > > 5.15.0-107-generic (on /dev/sda5)
> > > > This new Kernel is not listed at this window, not sure why not, seems
> > > > it
> > > > should be.
> > > >
> > > > If I can give you more info. let me know.
> > > >
> > > > Ralph Goe
> > > >
> > > > Sent with Proton Mail secure email.
> > > >
> > > > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot
> > > > <email address hidden> wrote:
> > > >
> > > > > This bug is awaiting verification that the linux-azure/
> > > > > kernel in -proposed solves the problem. Please test the kernel and
> > > > > update this bug with the results. If the problem is solved, change
> > > > > the
> > > > > tag 'verification-
> > > > > 'verification-
> > > > > linux-azure'. If the problem still exists, change the tag
> > > > > 'verification-
> > > > > needed-
> > > > >
> > > > > If verification is not done by 5 working days from today, this fix
> > > > > will
> > > > > be dropped from the source code, and this bug will be closed.
> > > > >
> > > > > See https:/
> > > > > documentation how
> > > > > to enable and use -proposed. Thank you!
> > > > >
> > > > > ** Tags added: kernel-
> > > > > verification-
> > > > >
> > > > > --
> > > > > You received this bug notification because you are subscribed to a
> > > > > duplicate bug report (2069485).
> > > > > https:/
> > > > >
> > > > > Title:
> > > > > AMD GPUs fail with null pointer dereference when IOMMU enabled,
> > > > > leading to black screen
> > > > >
> > > > > Status in linux package in Ubuntu:
> > > > > Fix Released
> > > > > Status in linux source package in Jammy:
> > > > > Fix Release...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #97 |
- Missing firmware.jpg Edit (4.8 MiB, image/jpeg; name="Missing firmware.jpg")
I noticed when the new update Kernel was loading this information, don't know if it will help...
Thanks again,
Ralph
Sent with Proton Mail secure email.
On Thursday, July 18th, 2024 at 9:58 PM, Erv Bendiks <email address hidden> wrote:
> @RogerRamjet> Do you have motherboard,CPU and OS information to share?
>
>
>
> On Thu, Jul 18, 2024 at 6:45 PM Roger Ramjet <email address hidden>
>
> wrote:
>
> > Why does the updated kernel show installed but not active, I'm still
> > having a problem?
> >
> > Sent with Proton Mail secure email.
> >
> > On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando
> > <email address hidden> wrote:
> >
> > > Ok Black screen now fixed after "update Manger" sent new update on
> > > 7/17/2024. Thank You Linux team !
> > >
> > > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet <email address hidden>
> > >
> > > wrote:
> > >
> > > > Unfortunately, I still have the same problem, after updating, I power
> > > > down
> > > > and restart, I get:
> > > > error: file `/boot/' not found.
> > > >
> > > > I view the Kernels in the update manager, it shows 5.15.0-116 is
> > > > "installed" and "supported until April 2027"
> > > >
> > > > The Kernel is loaded and installed but "not found"
> > > > Then another window opens and I must choose "Boot from next volume"
> > > > Then another window where I'm given the choice of booting from
> > > > 5.15.0-107-generic (on /dev/sda5)
> > > > This new Kernel is not listed at this window, not sure why not, seems
> > > > it
> > > > should be.
> > > >
> > > > If I can give you more info. let me know.
> > > >
> > > > Ralph Goe
> > > >
> > > > Sent with Proton Mail secure email.
> > > >
> > > > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot
> > > > <email address hidden> wrote:
> > > >
> > > > > This bug is awaiting verification that the linux-azure/
> > > > > kernel in -proposed solves the problem. Please test the kernel and
> > > > > update this bug with the results. If the problem is solved, change
> > > > > the
> > > > > tag 'verification-
> > > > > 'verification-
> > > > > linux-azure'. If the problem still exists, change the tag
> > > > > 'verification-
> > > > > needed-
> > > > >
> > > > > If verification is not done by 5 working days from today, this fix
> > > > > will
> > > > > be dropped from the source code, and this bug will be closed.
> > > > >
> > > > > See https:/
> > > > > documentation how
> > > > > to enable and use -proposed. Thank you!
> > > > >
> > > > > ** Tags added: kernel-
> > > > > verification-
> > > > >
> > > > > --
> > > > > You received this bug notification because you are subscribed to a
> > > > > duplicate bug report (2069485).
> > > > > https:/
> > > > >
> > > > > Title:
> > > > > AMD GPUs fail with null pointer dereference when IOMMU enabled,
> > > > > leading to black screen
> > > > >
> > > > > Status in linux package in Ubuntu:
> > > > > Fix Released
> > > > > Stat...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : | #98 |
Hello Erv,
Just wanted you to know what I did and found out.
I tried the update grub command when I was in Linux mint OS, it did not have any effect.
Then I remembered reading somebody else has the same issue, no effect until they went into something else on their computer, it had 3-4 letters, I didn't understand, they said the update worked from there because they had loader that software before their Mint software.
So since I used to use UBUNTU, and still have it on my computer, before I loaded Mint, I figured I'd open my UBUNTU software and run the update grub command, then went back into Mint and it worked, I am now running 116 Kernel update. Good news, but my computer still shows that it cannot find that "boot" file, not sure but then I load the "next volume" and then I can choose to run either Windows, Ubuntu or Mint, so I'm good.
Thanks for your attempt to help Erv.
Ralph Goe
Sent with Proton Mail secure email.
On Thursday, July 18th, 2024 at 9:58 PM, Erv Bendiks <email address hidden> wrote:
> @RogerRamjet> Do you have motherboard,CPU and OS information to share?
>
>
>
> On Thu, Jul 18, 2024 at 6:45 PM Roger Ramjet <email address hidden>
>
> wrote:
>
> > Why does the updated kernel show installed but not active, I'm still
> > having a problem?
> >
> > Sent with Proton Mail secure email.
> >
> > On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando
> > <email address hidden> wrote:
> >
> > > Ok Black screen now fixed after "update Manger" sent new update on
> > > 7/17/2024. Thank You Linux team !
> > >
> > > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet <email address hidden>
> > >
> > > wrote:
> > >
> > > > Unfortunately, I still have the same problem, after updating, I power
> > > > down
> > > > and restart, I get:
> > > > error: file `/boot/' not found.
> > > >
> > > > I view the Kernels in the update manager, it shows 5.15.0-116 is
> > > > "installed" and "supported until April 2027"
> > > >
> > > > The Kernel is loaded and installed but "not found"
> > > > Then another window opens and I must choose "Boot from next volume"
> > > > Then another window where I'm given the choice of booting from
> > > > 5.15.0-107-generic (on /dev/sda5)
> > > > This new Kernel is not listed at this window, not sure why not, seems
> > > > it
> > > > should be.
> > > >
> > > > If I can give you more info. let me know.
> > > >
> > > > Ralph Goe
> > > >
> > > > Sent with Proton Mail secure email.
> > > >
> > > > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot
> > > > <email address hidden> wrote:
> > > >
> > > > > This bug is awaiting verification that the linux-azure/
> > > > > kernel in -proposed solves the problem. Please test the kernel and
> > > > > update this bug with the results. If the problem is solved, change
> > > > > the
> > > > > tag 'verification-
> > > > > 'verification-
> > > > > linux-azure'. If the problem still exists, change the tag
> > > > > 'verification-
> > > > > needed-
> > > > >
> > > > > If verification is not done by 5 working days from today, this fix
...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Ramjet (rogerramjet123) wrote : Re: [Bug 2068738] verification-done-jammy- | #99 |
Yes this kernel update did the trick after running the sudo update-grub command from my Ubuntu software and then going back into my Mint software.
Thanks Linux team.
Ralph Goe
Sent with Proton Mail secure email.
On Wednesday, July 17th, 2024 at 11:29 PM, Ubuntu Kernel Bot <email address hidden> wrote:
> This bug is awaiting verification that the linux-aws/
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-
> linux-aws'. If the problem still exists, change the tag 'verification-
> needed-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2069485).
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Erv Bendiks (erv-bendiks) wrote : Re: [Bug 2068738] verification-failed-jammy-linux-azure | #100 |
@Roger Ramjet> Glad you're making progress. GRUB can be a pain. I've been
there. The secure boot and BIOS/UEFI plus installing grub on multiple
drives but only one drive's GRUB is active.. sometimes makes kernel updates
on other drives two step chore, minimum.
You might try changing which volume is your primary boot drive in your BIOS
to your Mint drive? Have your backups up to date and volume-OS's
identified before that. Or not. Best luck and speedy recovery.
On Fri, Jul 19, 2024 at 4:20 PM Roger Ramjet <email address hidden>
wrote:
> Hello Erv,
>
> Just wanted you to know what I did and found out.
>
> I tried the update grub command when I was in Linux mint OS, it did not
> have any effect.
> Then I remembered reading somebody else has the same issue, no effect
> until they went into something else on their computer, it had 3-4 letters,
> I didn't understand, they said the update worked from there because they
> had loader that software before their Mint software.
> So since I used to use UBUNTU, and still have it on my computer, before I
> loaded Mint, I figured I'd open my UBUNTU software and run the update grub
> command, then went back into Mint and it worked, I am now running 116
> Kernel update. Good news, but my computer still shows that it cannot find
> that "boot" file, not sure but then I load the "next volume" and then I can
> choose to run either Windows, Ubuntu or Mint, so I'm good.
>
> Thanks for your attempt to help Erv.
>
> Ralph Goe
>
>
>
> Sent with Proton Mail secure email.
>
> On Thursday, July 18th, 2024 at 9:58 PM, Erv Bendiks
> <email address hidden> wrote:
>
> > @RogerRamjet> Do you have motherboard,CPU and OS information to share?
> >
> >
> >
> > On Thu, Jul 18, 2024 at 6:45 PM Roger Ramjet <email address hidden>
> >
> > wrote:
> >
> > > Why does the updated kernel show installed but not active, I'm still
> > > having a problem?
> > >
> > > Sent with Proton Mail secure email.
> > >
> > > On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando
> > > <email address hidden> wrote:
> > >
> > > > Ok Black screen now fixed after "update Manger" sent new update on
> > > > 7/17/2024. Thank You Linux team !
> > > >
> > > > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet
> <email address hidden>
> > > >
> > > > wrote:
> > > >
> > > > > Unfortunately, I still have the same problem, after updating, I
> power
> > > > > down
> > > > > and restart, I get:
> > > > > error: file `/boot/' not found.
> > > > >
> > > > > I view the Kernels in the update manager, it shows 5.15.0-116 is
> > > > > "installed" and "supported until April 2027"
> > > > >
> > > > > The Kernel is loaded and installed but "not found"
> > > > > Then another window opens and I must choose "Boot from next volume"
> > > > > Then another window where I'm given the choice of booting from
> > > > > 5.15.0-107-generic (on /dev/sda5)
> > > > > This new Kernel is not listed at this window, not sure why not,
> seems
> > > > > it
> > > > > should be.
> > > > >
> > > > > If I can give you more info. let me know.
> > > > >
> > > > > Ralph Goe
> > > > >
> > > > > Sent with Proton Mail secure email.
> > > > >
> > > > > On Monday, July 15th, 2024 at 11...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Carrington Institute (symbolize) wrote : | #101 |
All good here, thanks to everybody that made this happen.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #102 |
This bug is awaiting verification that the linux-xilinx-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #103 |
This bug is awaiting verification that the linux-aws-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #104 |
This bug is awaiting verification that the linux-gcp-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-focal-linux-gcp-5.15-v2 verification-needed-focal-linux-gcp-5.15 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Erv Bendiks (erv-bendiks) wrote : Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen | #105 |
So who's got auth to toggle the "change the tag
'verification-
aws-5.15' to 'verification-
"aws-5.
It's solved on my 3200G box.
On Wed, Jul 24, 2024 at 10:06 PM Ubuntu Kernel Bot <
<email address hidden>> wrote:
> This bug is awaiting verification that the linux-
> aws-5.15/
> Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-
> aws-5.15' to 'verification-
> still exists, change the tag 'verification-
> to 'verification-
>
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
>
> See https:/
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-
> verification-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Thomas Løcke (thomasmonadic) wrote : | #106 |
When do we get this new kernel? It seems to solve the problem.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #107 |
This bug is awaiting verification that the linux-nvidia-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #108 |
This bug is awaiting verification that the linux-nvidia-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Noah Wager (nwager) wrote (last edit ): | #109 |
Doesn't affect nvidia-tegra kernel use cases
tags: |
added: verification-done-jammy-linux-nvidia-tegra verification-done-jammy-linux-nvidia-tegra-igx removed: verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Orlando (peteola) wrote : | #110 |
Last update to my AMD Laptop boots ok now. Thank You.
On Mon, Aug 12, 2024 at 4:51 PM Noah Wager <email address hidden>
wrote:
> Doesn't affect nvidia-tegra kernel use cases
>
> ** Tags removed: verification-
> verification-
> ** Tags added: verification-
> verification-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> AMD GPUs fail with null pointer dereference when IOMMU enabled,
> leading to black screen
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> BugLink: https:/
>
> [Impact]
>
> On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is
> enabled, the system fails to boot correctly, and all users see is a
> black screen.
>
> This is caused by a null pointer dereference when enabling the IOMMU
> after the device has been initialised. It should happen the other way
> around.
>
> AMD-Vi: AMD IOMMUv2 loaded and initialized
> ...
> amdgpu: Topology: Add APU node [0x15d8:0x1002]
> kfd kfd: amdgpu: added device 1002:15d8
> kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8
> ...
> amdgpu 0000:06:00.0: amdgpu: amdgpu_
> amdgpu 0000:06:00.0: amdgpu: Fatal error during GPU init
> amdgpu 0000:06:00.0: amdgpu: amdgpu: finishing device.
> ...
> BUG: kernel NULL pointer dereference, address: 000000000000013c
> ...
> CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic
> #122-Ubuntu
> ...
> RIP: 0010:amdgpu_
> ...
> Call Trace:
> <TASK>
> ? srso_return_
> ? show_trace_
> ? show_trace_
> ? dm_hw_fini+
> ? show_regs.
> ? __die_body.
> ? __die+0x2b/0x37
> ? page_fault_
> ? srso_return_
> ? do_user_
> ? srso_return_
> ? __free_
> ? exc_page_
> ? asm_exc_
> ? amdgpu_
> dm_hw_fini+
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> amdgpu_
> local_pci_
> ? srso_return_
> pci_device_
> really_
> __driver_
> driver_
> __driver_
> ? __device_
> bus_for_
> driver_
> bus_add_
> ? srso_return_
> driver_
> __pci_register_
> amdgpu_
> ? 0xffffffffc0e0b000
> ...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : | #111 |
This bug is awaiting verification that the linux-nvidia-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 |
Status changed to 'Confirmed' because the bug affects multiple users.