Public bug reported:
After updated an old laptop to Ubuntu Cosmic (was running Xenial before)
the graphic hangs at startup, nothing is displayed but a grey screen
(grub residual), note that the recovery boot option using `nodmodeset`
displays a text console and I'm still able to log-in over a seri
Can you provide a new dmesg output from 4.18 kernel since you discovered
you are able to boot on recovery mode? Just dump it somewhere so you can
recover it once booted graphically with another kernel.
Basically once you are in front of the recovery screen, select the
option to enable network, not
@paed808 see my comment on that thread, as a dmesg from the faulty
kernel would be useful to compare. By the way I would be surprised the
bugs are the same because you really use a very far more recent hardware
(mine is perhaps four years older than yours), but if the bug is in a
shared component i
This bug seems to not affect Ubuntu 20.04 stock kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1813509
Title:
[i915] NULL pointer on Linux 4.18.0-14-generic / cosmic
Stat
Public bug reported:
This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July
2020).
There is two kernels available on this system:
- 5.4.0-47-generic
- 5.4.0-48-generic
With kernel 5.4.0-47-generic:
- GNOME shell loads properly on Radeon X1950 PRO,
- Unvanquished game runs on ATI
** Description changed:
This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July
2020).
There is two kernels available on this system:
- 5.4.0-47-generic
- 5.4.0-48-generic
With kernel 5.4.0-47-generic,
- GNOME shell loads properly on Radeon X1950 PRO,
- Un
I forgot to mention:
After switching from the 5.4.0-47-generic kernel to the 5.4.0-48-generic
one, it becomes very very slow for the game to load the levels and
related assets from filesystem (textures, etc.), so the issue is likely
to no be only about graphical performance.
--
You received this
I tested with another ATI GPU, the Radeon HD 4670 (AGP) one, an high-end
TeraScale 1 generation card. The computer did not manage to display the
desktop, the dmesg was full of errors about GPU lockup, and I did not
managed to reboot properly the computer (had to uses magic SysRq keys).
I tested wi
** Attachment added: "dmesg on linux 5.4.0-48 and ATI Radeon HD 4670 (AGP)
experiencing GPU lockup"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5421055/+files/dmesg.linux-5.4.0-48-generic.ati-radeon-hd4670-agp.gpu-lockup.txt
--
You received this bug notification
** Summary changed:
- Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME
Shell never finishes to load, GNOME desktop unusable
+ Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop
fail to start and games going from 70fps to 7fps, slow file load
I forgot to say that when I manage to get a non-composited LXDE desktop
running on Radeon X1950 PRO, started by hand using `startx`, and I run
the Unvanquished game, more than 51% of the CPU time is spent on OpenAL
thread, i.e. the audio thread, which is wrong. This thread is usually
really lightwe
** Attachment added: "Screen photo of display garbage on Linux 5.4.0-48 with
Nvidia GeForce 8400 GS rev.2 (PCI)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5421058/+files/20201011-231213-000.display-garbage-on-nvidia-geforce-8400gs2-pci.jpg
--
You received this
** Attachment added: "Screen photo of GNOME Shell hanging on Linux 5.4.0-48
with ATI Radeon X1950 PRO (AGP)."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5421057/+files/20201011-014117-000.gnome-shell-hang-on-ati-radeon-x1950pro-agp.jpg
--
You received this bug n
I reproduce the bug with the 5.4.0-49-generic kernel from `proposed`
when running the Radeon X1950 PRO.
Note: I previously joined a dmesg log file about GPU lockup, such lockup
is not always logged but the GNOME Shell session is stuck anytime it is
started.
--
You received this bug notification
I reproduce the bug with 5.4.0-51-generic and 5.4.0-52-generic.
The 5.4.0-47-generic one is the last known kernel to work on that system.
** Summary changed:
- Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop
fail to start and games going from 70fps to 7fps, slow file
I reproduce the bug on another computer, using 5.4.0-52-generic kernel:
Motherboard: Asrock AM2NF3 VSTA
CPU: AMD Phenom II X4 970 (Quad core)
RAM: 16GB DDR2 800MHz (4×4 GB)
GPU: ATI Radeon HD 4670 AGP
VRAM: 1GB DDR3
Of course the same computer works flawlessly with 5.4.0-47-generic
kernel.
I not
Here is another photo of display glitch happening when the computer
hangs. I got it with both the Radeon X1950 and the Radeon HD 4670.
What happens it at startup, the GNOME Shell desktop makes an animation,
expanding itself from the center of the screen. In such screenshot, we
see the computer han
Hi, thank you for your answer and your attention,
This issue is confirmed again.
1. 5.10.0-rc1 does not fix the problem introduced in 5.4.0-48 regarding ATI/AMD
AGP GPU.
2. PCI GPUs are broken on AMD K8/K10 platform since years but they work on
Intel platform, GPU being ATI/AMD or Nvidia doesn'
I built the v5.5.0 version from torvalds's branch and it works.
So, if it does not work on Ubuntu's 5.4.0-48 I can assume it's was
broken by some Ubuntu custom patch or some backports, making it harder
for me to identify what may have introduced the regression.
I'll try to find the vanilla versio
Public bug reported:
This is an issue I found while investigating #1899304
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304
The big concern is that if AGP is disabled, there is no fallback display
option on those platforms.
After having discovered some K8 and K10 computers running AG
Hmm, minor issues in the host list, fixed:
- K10 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU
(quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI
- K8 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual
core), Nvidia C51 bridge, 6GB DD
** Attachment added: "dmesg on Linux 5.10-rc1 on Ubuntu 20.04, K10 platform,
ATI Radeon HD 4350 PCI"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430838/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4350-PCI.txt
--
** Attachment added: "dmesg on Linux 4.8.0-36 on Ubuntu 16.04, K8 platform,
Nvidia Geforce 8400GS rev.2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430841/+files/dmesg.ubuntu-16.04.linux-4.8.0-36-generic_MSI-MS-6702E+K8_Nvidia-Geforce-8400GSr2-PCI.txt
--
You re
** Attachment added: "dmesg on Linux 4.8.0-36 on Ubuntu 16.04, K8 platform, ATI
Radeon HD 4350 PCI"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430840/+files/dmesg.ubuntu-16.04.linux-4.8.0-36-generic_MSI-MS-6702E+K8_ATI-Radeon-HD-4350-PCI.txt
--
You received thi
** Attachment added: "dmesg on Linux 5.10-rc1 on Ubuntu 20.04, K10 platform,
Nvidia Geforce 8400GS rev.2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430839/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_Nvidia-Geforce-8400GSr2-PCI
The interesting thing on Nvidia GS 8400GS rev.2 may be:
[ 20.107995] nouveau :03:00.0: DRM: GPU lockup - switching to software
fbcon
[ 20.180130] nouveau :03:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[ 20.195263] [drm] Initialized nouveau 1.3.1 20120801 for :03:00.0 on
** Attachment added: "Screenshot of graphical issues on Nvidia Geforce 8400GS
rev.2 PCI on K8 AGP host"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430842/+files/20201103-002441-000.nvidia-geforce-8400gsr2-pci+k8.jpg
--
You received this bug notification because
** Attachment added: "Screenshot of graphical issues on Nvidia Geforce 8400GS
rev.2 PCI on K10 AGP host"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430843/+files/20201102-174932-000.nvidia-geforce-8400gsr2-pci+k10.jpg
--
You received this bug notification becau
I added two screenshots (screen photos) of graphical glitches taken
while running the Nvidia Geforce 8400GS rev.2 PCI on K8 AGP and K10 AGP
hosts. That's the last thing an user can see (it remains on screen), the
desktop never displays. In those case I get dmesg logs through SSH.
On the K8 PCie ho
** Attachment added: "Screenshot of GNOME desktop frozen on ATI Radeon HD 4350
PCI on K8 AGP host"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430844/+files/20201103-001858-000.ati-radeon-hd4350pci+k8.jpg
--
You received this bug notification because you are a m
I've added a screenshot (screen photo) of the GNOME desktop being stuck
and unresponsive while running the ATI Radeon 4350 PCI on the K8 AGP
host.
You'll notice this is the exact same symptom I get with ATI Radeon AGP cards on
this host starting with kernel 5.4.0-48-generic and later (while that
Here may be the interesting dmesg part when running the ATI Radeon 4350
PCI card on the K10 AGP host with Ubuntu 20.04 Focal and Linux 5.10-rc1
kernel. Note that those messages repeats infinitely and very quickly in
a way the whole journal becomes full rapidly (dropping earlier entries):
```
[ 4
** Summary changed:
- PCI graphics seems to be broken since years on AMD K8/K10 platform (work on
Intel)
+ PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified
from Linux 4.4 to 5.10-rc1
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902795
Title:
PCI graphics broken on AMD K8/K10 platform (while it wo
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1899304
Title:
Linux 5.4.0-48 (and later) causes GPU lockup, huge perf
For some reason I was able to compile v5.4 and v5.5 from torvalds
branchs with `make -j$(nproc) deb-pkg` but starting with v5.6 I had to
use `make -j$(nproc) bindeb-pkg`, in the end I lacked some modules (like
my network driver, that did not helped me) but radeon one was there so
tests could have b
** Attachment added: "dmesg on Linux 5.10.0-051000rc1-generic on Ubuntu 20.04,
K10 platform, ATI Radeon HD 4670 AGP"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430875/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-46
** Attachment added: "dmesg on Linux 5.9 vanilla on Ubuntu 20.04, K10 platform,
ATI Radeon HD 4670 AGP"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430874/+files/dmesg.ubuntu-20.04.linux-5.9-vanilla_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.txt
--
You receiv
Related and similar issue with PCI graphic cards (not AGP ones):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795
While PCI graphic cards are broken on AMD K8/K10 platform for years
(I've reproduced on Linux 4.4, 4.8 and 4.15 from Ubuntu 16.04 Xenial),
AGP cards started to break on Ubu
** Attachment added: "dmesg on Linux 5.4.0-48-generic on Ubuntu 20.04, K10
platform, ATI Radeon HD 4670 (truncated because it was weighting 62MB)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430878/+files/dmesg.ubuntu-20.04.linux-5.4.0-48-generic_ASRock-AM2NF3-VS
So, the 5.4.0-48 error is the same as the one that appears with 5.9 (and
the one we see with PCI GPUs):
```
[0.00] Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc
version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC
2020 (Ubuntu 5.4.0-48.52-generic
I noticed a similar bug was reported on 3.2 kernel in year 2012:
https://bugzilla.redhat.com/show_bug.cgi?id=785375
At the time the bug was fixed by switching the PCI DMA bit mask from 40-bits to
32-bits:
https://bugzilla.redhat.com/attachment.cgi?id=603278
The initial patch was testing against
** Attachment added: "dmesg on Linux 5.8 with 32bit dma patch on K10 host
running the HD 4350 PCI GPU, demonstrating some errors being workarounded (not
all)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431288/+files/dmesg.linux-5.8-dma32fix_ASRock-AM2NF3-VSTA+K1
** Attachment added: "dmesg on Linux 5.8 vanilla on K10 host running the HD
4350 PCI GPU"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431287/+files/dmesg.linux-5.8-vanilla_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4350-PCI.txt
--
You received this bug notification be
Here is a dmesg log from september, running the PCI Nvidia 8400GS rev.2
with nouveau on a K8 non-AGP host with Nvidia C51 PCI Express bridge.
The GPU is driven by nouveau. So at this time I at least managed to
connect through SSH while there was no display. The dmesg log reports a
GPU lockup.
Yet
Here is a dmesg log from september, running the PCI Nvidia 8400GS rev.2
with nouveau on a K8 non-AGP host with Nvidia C51 PCI Express bridge.
The GPU is driven by proprietary non-free closed nvidia driver.
Yet again, this PCI GPU is known to work with nvidia driver when plugged
into an Intel platf
Just a reupload of the previously posted patch, fixing some typos.
** Patch removed: "PATCH: drm/radeon: make all PCI GPUs use 32 bits DMA bit
mask (not enough to fix the issue and ATI specific)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431266/+files/0001-drm-
** Summary changed:
- Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes
GNOME desktop fail to start and games going from 70fps to 7fps, slow file
loading, audio issues
+ Linux 5.4.0-48 (and later) causes AGP GPU lockup, huge performance drop,
makes GNOME desktop fail to
Public bug reported:
This bug is to track specific issues faced by AGP GPUs when running as
PCI devices (when AGP support is disabled at kernel build time), unless
otherwise proven it is believed fixing #1902795 (PCI GPUs support being
broken) may not fix all issues for AGP GPUs running as PCI one
** Summary changed:
- Linux 5.4.0-48 (and later) causes AGP GPU lockup, huge performance drop,
makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file
loading, audio issues
+ AGP disablement leaves GPUs without working alternative (PCI fallback is
broken), makes very-cap
As a reminder, this is a dmesg captured when running ATI Radeon HD 4670
AGP on a K10 host on Linux 5.9 (vanilla).
The ATI Radeon HD 4670 AGP (RV730 XT) is a very capable TeraScale GPU,
supporting OpenGL 3.3 (Directx 10 on Windows) and OpenCL 1.0, and
featured HDMI output and 1GB of VRAM. The host
When applying patch from https://bugs.launchpad.net/bugs/1902795
-
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431335/+files/0001
-drm-radeon-make-all-PCI-GPUs-use-32bits-DMA-bit-mask.patch
which reduces the breakage (but not fix completely) the issues faced
with PCI
To get a better picture of such top-of-the-line AGP GPU performance,
when comparing to others GPUs on Unvanquished GPU compatibility matrix:
https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix
we can see the ATI Radeon HD 4670 AGP (RV730 XT, TeraScale 1) performs:
- better than the PCI Ex
It looks like comment #3 had been truncated, the interesting part of the
dmesg log that is missing is:
```
[ 66.755306] radeon :01:00.0: ring 0 stalled for more than 31248msec
[ 66.755317] radeon :01:00.0: GPU lockup (current fence id
0x0001 last fence id 0x00
On a side note, because we see a clear behaviour difference when
applying the PCI patch we can assume the driver catch the `rdev->flags &
RADEON_IS_PCI` test instead of the `rdev->flags & RADEON_IS_AGP` one
when running an AGP GPU with AGP disabled in kernel at build time.
** Changed in: linux (Ub
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1899304
Title:
AGP disablement leaves GPUs without working alternative (PCI fallback
is broken), makes very-cap
** Tags added: amd64 focal
** Tags added: kernel-bug
** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902795
Title:
PCI graphics broken on AMD K8/K10 platform (whi
** Summary changed:
- AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail
on K8 and K10 platforms
+ AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are
known to fail on K8 and K10 platforms
--
You received this bug notification because you are
Before bisecting, I investigated the PCI issue:
https://bugs.launchpad.net/bugs/1902795
I've faced the PCI issue before the AGP one, but it was less critical.
I've submitted a patch that may fix some issues (with drawback of being
non-optimal on platforms were PCI graphics are known to already wor
This reverts commit ba806f98f868ce107aa9c453fef751de9980e4af.
Disabling AGP leaves some hardware without working alternative
on some platforms. For example, PCI GPUs are known to be broken
on K8 and K10 platforms since years: the breakage was reproduced
from Linux 4.4 on Ubuntu 16.04 Xenial to Lin
** Description changed:
- This is an issue I found while investigating #1899304
+ This is an issue I faced before #1899304 but becomes more critical with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304
The big concern is that if AGP is disabled, there is no fallback display
o
See patch and comments on https://lkml.org/lkml/2020/11/5/307
Patch was rewritten in a way the message is shorter and comment uses
better language.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
See patch and comments on https://lkml.org/lkml/2020/11/5/308
Patch was rewritten in a way the message is shorter.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1899304
Title:
AGP disa
I've reproduced the issue on Piledriver platform with AMD 9590 CPU, with
both ATI and Nvidia PCI GPUs.
With the ATI GPU, I get the usual symptom of the computer freezing
display while the GNOME desktop is partially loaded. It's possible to
open a TTY console by switching consoles but once returned
** Summary changed:
- PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on
Intel) verified from Linux 4.4 to 5.10-rc1
+ PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on
Intel) verified from Linux 4.4 to 5.10-rc2
--
You received this bug notification
Public bug reported:
Since I upgraded from lunar to mantic I get a load of those errors (41
on a fresh boot) in dmesg:
```
[4.277343] UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
[4.277728] index 4 is out of range for type 'btree_ite
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2018470
Title:
Linux 5.19 amdgpu: NULL pointer on GCN
Why should we test an Nvidia kernel for a bug affecting AMD GPUs?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2018470
Title:
Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load o
Should we really test that Nvidia kernel for a bug affecting AMD GPUs,
otherwise the already verified fix would be dropped?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2018470
Title:
Will the patch be dropped if the Nvidia kernel is not tested on AMD
GPUs?
Rebooting the computer affected by the bug will cost me 1 or 2 hours of
work so that's a very high cost for a patch I already marked as
verified.
--
You received this bug notification because you are a member of Kernel
Pac
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2018470
Title:
Linux 5.19 amdgpu: NULL pointer on GCN2 an
I tested linux-nvidia 5.19.0-1014.14 from jammy-proposed on my kinetic
install. Both GCN1 and GCN2 displays work. I get the ASAN debug message
but everything works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Public bug reported:
I can't get any desktop, neither with Xorg, neither with Wayland (it
even does not fallback on llvmpipe).
The dmesg reports a null pointer dereference in nouveau kernel module.
This makes Ubuntu 23.10 not working at all on this computer.
lspci:
```
Slot: 00:02.0
Class:
I tested the linux-image-6.8.0-40-generic kernel on Ubuntu noble.
It fixed the bcache errors, but graphics were unusable, I had to revert
to linux-image-6.8.0-39-generic to get GDM on Wayland working (I haven't
tested GDM on Xorg).
--
You received this bug notification because you are a member o
As said there: https://lkml.org/lkml/2021/5/13/752
The bug was also reproduced on Intel Kentsfield platform (Core 2 Quad
Q6600 (with VIA PT880/VT82xx) with R300 and TeraScale GPUs.
** Summary changed:
- AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are
known to fail on
Public bug reported:
The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to
stick on Linux 5.15 because 5.19 was not working with my computer. The
last two days I spent time to find a way to run Linux 5.19, and found
one version working: 5.19.0-23.
Here are the versions I tested:
So, in the end I spent some times to do more dmesg logs, just producing
6 of them took me multiple hours because of how slow such kind of
computer BIOS is to boot, and also because of how complicated it can be
to get a shell when everything goes wrong with those bugs.
Something I forgot to mention
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5670999/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu.txt
--
You received this bug notification because you are a member of
** Attachment added:
"dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5670998/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt
--
You received this bug notification because you are
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-radeon.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671000/+files/dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-radeon.txt
--
You received this bug notification because you are a member of
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-radeon.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671001/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-radeon.txt
--
You received this bug notification because you are a member of
** Attachment added:
"dmesg.linux-5.19.0-23-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671008/+files/dmesg.linux-5.19.0-23-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt
--
You received this bug notification because you are
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2018470
Title:
Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2
Status in linux package in Ubuntu:
Confirmed
Bug descrip
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-amdgpu.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671007/+files/dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-amdgpu.txt
--
You received this bug notification because you are a member of
So to summarize:
with Linux 5.19.0-42-generic amdgpu on GCN1: kernel NULL pointer
dereference
- no display
- stuck boot requiring SysRq+K to continue
- errors in dmesg
- reboot requiring SysRq+B to continue
with Linux 5.19.0-42-generic amdgpu on CGN2: kernel UBSAN invalid load,
load of value 8 i
** Summary changed:
- Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2
+ Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
I've reported the issues upstream on drm side:
- https://gitlab.freedesktop.org/drm/amd/-/issues/2540
Linux 5.19 amdgpu: NULL pointer on GCN2 (R9 390X Hawaii/Grenada)
- https://gitlab.freedesktop.org/drm/amd/-/issues/2541
Linux 5.19 amdgpu: invalid load on GCN1 (R7 240 Oland)
For the NULL po
This is the patch by Alex Deucher that is believed to fix the NULL
pointer dereference. I have not tested it but the issue looks very
close. It is needed anyway.
> Guchun Chen
> Regarding the NULL pointer access, it should be duplicated of #2388. And the
> fix is "63a9ab264a8c drm/amd/pm/smu7: mo
I'm on 5.19.0-44.45 right now.
What 5.19.0-44.45 is expected to fix?
- The computer boots properly, I have both R7 240 and R9 390X displaying
something fine, so that error is fixed.
- I still have an error message in dmesg:
```
[7.609329]
===
I now see the original message was edited, with this words added:
> [Test case]
> Install the update, check that display works again on amdgpu
I confirm display works again on amdgpu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
90 matches
Mail list logo
