[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #11 from Rogério Brito (rbr...@ime.usp.br) --- Dear Michel and other people, Since the last time that I reported this bug, the lock ups have not happened anymore. OTOH, the messages on the dmesg log persist. I can include newer logs

[Bug 210123] drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] - flip_done time out with vmwgfx

https://bugzilla.kernel.org/show_bug.cgi?id=210123 --- Comment #2 from Michel Dänzer (mic...@daenzer.net) --- (In reply to Stefan Mayr from comment #1) > #208373 seems simliar but for us it started with an older kernel version It's about amdgpu, unlikely to be directly related. -- You are recei

[Bug 209457] AMDGPU resume fail with RX 580 GPU

https://bugzilla.kernel.org/show_bug.cgi?id=209457 fawz (f...@negentropy.io) changed: What|Removed |Added CC||f...@negentropy.io --- Commen

[Bug 209457] AMDGPU resume fail with RX 580 GPU

https://bugzilla.kernel.org/show_bug.cgi?id=209457 --- Comment #15 from fawz (f...@negentropy.io) --- Hi all, I'm not sure if I'm experiencing the same bug, but the outcome and some of the log messages seem to be the same. For me, resuming from suspend is broken with kernel 5.9.0-2 and works wh

[Bug 209457] AMDGPU resume fail with RX 580 GPU

https://bugzilla.kernel.org/show_bug.cgi?id=209457 --- Comment #16 from fawz (f...@negentropy.io) --- Created attachment 293629 --> https://bugzilla.kernel.org/attachment.cgi?id=293629&action=edit dmesg output when booting with kernel 5.9, suspending, then resuming -- You are receiving this ma

[Bug 210201] New: [amdpgu] crash when playing after suspend/resume

https://bugzilla.kernel.org/show_bug.cgi?id=210201 Bug ID: 210201 Summary: [amdpgu] crash when playing after suspend/resume Product: Drivers Version: 2.5 Kernel Version: 5.9.8, 5.6.19, 5.8.18 Hardware: x86-64 OS: Linux

[Bug 208205] [amdgpu] System hang / freeze

https://bugzilla.kernel.org/show_bug.cgi?id=208205 --- Comment #6 from Andrea Borgia (and...@borgia.bo.it) --- Running linux-image-5.9.0-1-amd64 for quite some time now and it looks stable. AFAIK this was the fix: https://lkml.org/lkml/2020/7/27/64 -- You are receiving this mail because: You are

[Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"

https://bugzilla.kernel.org/show_bug.cgi?id=210263 Bug ID: 210263 Summary: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" Product: Drivers Version: 2.5 Kernel Version: 5.9.8 H

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

https://bugzilla.kernel.org/show_bug.cgi?id=201763 Vadim Yanitskiy (vyanits...@sysmocom.de) changed: What|Removed |Added CC||vyanits...@sysm

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #13 from Vadim Yanitskiy (vyanits...@sysmocom.de) --- Here we go: [ 582.721066] amdgpu: iceland_populate_all_memory_levels(): mclk_table has 3 entries [ 582.721081] amdgpu: iceland_populate_all_memory_levels(): dpm_levels[0] is 3000

[Bug 210201] [amdpgu] crash when playing after suspend/resume

https://bugzilla.kernel.org/show_bug.cgi?id=210201 --- Comment #1 from Artur Bac (arturbac...@gmail.com) --- What is interesting people report similar case ~1h on windows, does amdgpu is sharing code with windows driver ? https://www.reddit.com/r/AMDHelp/comments/jx4660/crash_rx5700xt -- You ar

[Bug 210123] drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] - flip_done time out with vmwgfx

https://bugzilla.kernel.org/show_bug.cgi?id=210123 --- Comment #3 from Stefan Mayr (stefan+ker...@mayr-stefan.de) --- Did some more test with Kernel versions provided by SUSE: Kernel 5.0.13 - 6 days without issues Kernel 5.2.14 - 2 days until we got the error message Today I installed 5.1.16 and

[Bug 210123] drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] - flip_done time out with vmwgfx

https://bugzilla.kernel.org/show_bug.cgi?id=210123 --- Comment #4 from Stefan Mayr (stefan+ker...@mayr-stefan.de) --- I had another look at bug 208373: the inital reporter also uses vmwgfx and amdgpu is only mentioned in bug 208373, comment 2 -- You are receiving this mail because: You are watch

[Bug 208373] drm:drm_atomic_helper_wait_for_dependencies - drm_kms_helper - flip_done timed out

https://bugzilla.kernel.org/show_bug.cgi?id=208373 --- Comment #6 from Michel Dänzer (mic...@daenzer.net) --- The original report here is about the vmwgfx driver; issues with amdgpu should be tracked elsewhere. sander44, are you seeing any problem other than the messages? -- You are receiving t

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 swebwaer (gosesen...@tjuln.com) changed: What|Removed |Added CC||gosesen...@tjuln.com --

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #6 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286167 https://gitlab.com/gitlab-org/gitlab/-/issues/286168 https://gitlab.com/gitlab-org/gitlab/-/issues/286169 https://gitlab.com/gitlab-org/gi

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #7 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286167 https://gitlab.com/gitlab-org/gitlab/-/issues/286168 https://gitlab.com/gitlab-org/gitlab/-/issues/286169 https://gitlab.com/gitlab-org/gi

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #8 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286240 https://gitlab.com/gitlab-org/gitlab/-/issues/286241 https://gitlab.com/gitlab-org/gitlab/-/issues/286242 https://gitlab.com/gitlab-org/gi

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #9 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286267 https://gitlab.com/gitlab-org/gitlab/-/issues/286268 https://gitlab.com/gitlab-org/gitlab/-/issues/286269 https://gitlab.com/gitlab-org/gi

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #10 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286267 https://gitlab.com/gitlab-org/gitlab/-/issues/286268 https://gitlab.com/gitlab-org/gitlab/-/issues/286269 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #11 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286386 https://gitlab.com/gitlab-org/gitlab/-/issues/286387 https://gitlab.com/gitlab-org/gitlab/-/issues/286389 https://gitlab.com/gitlab-org/g

[Bug 210301] New: *ERROR* IB test failed on gfx (-110) on Ryzen 4750u

https://bugzilla.kernel.org/show_bug.cgi?id=210301 Bug ID: 210301 Summary: *ERROR* IB test failed on gfx (-110) on Ryzen 4750u Product: Drivers Version: 2.5 Kernel Version: 5.9.8 Hardware: Intel OS: Linux Tree

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #12 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286503 https://gitlab.com/gitlab-org/gitlab/-/issues/286504 https://gitlab.com/gitlab-org/gitlab/-/issues/286505 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #13 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286588 https://gitlab.com/gitlab-org/gitlab/-/issues/286589 https://gitlab.com/gitlab-org/gitlab/-/issues/286590 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #14 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286634 https://gitlab.com/gitlab-org/gitlab/-/issues/286635 https://gitlab.com/gitlab-org/gitlab/-/issues/286636 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #15 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286634 https://gitlab.com/gitlab-org/gitlab/-/issues/286635 https://gitlab.com/gitlab-org/gitlab/-/issues/286636 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #16 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286709 https://gitlab.com/gitlab-org/gitlab/-/issues/286710 https://gitlab.com/gitlab-org/gitlab/-/issues/286711 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #17 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286743 https://gitlab.com/gitlab-org/gitlab/-/issues/286745 https://etienne-yahriel.medium.com/usually-in-reference-to-your-current-interest-1e6

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #18 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286778 https://gitlab.com/gitlab-org/gitlab/-/issues/286779 https://gitlab.com/gitlab-org/gitlab/-/issues/286780 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #19 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286778 https://gitlab.com/gitlab-org/gitlab/-/issues/286779 https://gitlab.com/gitlab-org/gitlab/-/issues/286780 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #20 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286834 https://gitlab.com/gitlab-org/gitlab/-/issues/286835 https://gitlab.com/gitlab-org/gitlab/-/issues/286835 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #21 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286915 https://gitlab.com/gitlab-org/gitlab/-/issues/286916 https://gitlab.com/gitlab-org/gitlab/-/issues/286917 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #22 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/286988 https://gitlab.com/gitlab-org/gitlab/-/issues/286989 https://gitlab.com/gitlab-org/gitlab/-/issues/286990 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #23 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/287043 https://gitlab.com/gitlab-org/gitlab/-/issues/287044 https://gitlab.com/gitlab-org/gitlab/-/issues/287045 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #24 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/287072 https://gitlab.com/gitlab-org/gitlab/-/issues/287073 https://gitlab.com/gitlab-org/gitlab/-/issues/287074 https://gitlab.com/gitlab-org/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #25 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/287105 https://gitlab.com/gitlab-org/gitlab/-/issues/287106 https://gitlab.com/gitlab-org/gitlab/-/issues/287107 https://gitlab.com/gitlab-org/g

[Bug 210303] New: Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 Bug ID: 210303 Summary: Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table Product: Drivers Version: 2.5 Kernel Version: 5.9.9 Hardware: IA-64 O

[Bug 210303] Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 --- Comment #1 from mkkot (marcin2...@gmail.com) --- Created attachment 293767 --> https://bugzilla.kernel.org/attachment.cgi?id=293767&action=edit xrandr -- You are receiving this mail because: You are watching the assignee of the bug. __

[Bug 210303] Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 --- Comment #2 from mkkot (marcin2...@gmail.com) --- Created attachment 293769 --> https://bugzilla.kernel.org/attachment.cgi?id=293769&action=edit glxgears info -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 210303] Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 --- Comment #3 from mkkot (marcin2...@gmail.com) --- Created attachment 293771 --> https://bugzilla.kernel.org/attachment.cgi?id=293771&action=edit xorg log (not from the time when it happened) -- You are receiving this mail because: You are w

[Bug 210303] Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 --- Comment #4 from mkkot (marcin2...@gmail.com) --- Created attachment 293773 --> https://bugzilla.kernel.org/attachment.cgi?id=293773&action=edit lsmod -- You are receiving this mail because: You are watching the assignee of the bug. ___

[Bug 210303] Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 --- Comment #5 from mkkot (marcin2...@gmail.com) --- Created attachment 293775 --> https://bugzilla.kernel.org/attachment.cgi?id=293775&action=edit lspci -- You are receiving this mail because: You are watching the assignee of the bug. ___

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #26 from swebwaer (gosesen...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/287175 https://gitlab.com/gitlab-org/gitlab/-/issues/287176 https://gitlab.com/gitlab-org/gitlab/-/issues/287177 https://gitlab.com/gitlab-org/g

[Bug 210303] Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 --- Comment #6 from mkkot (marcin2...@gmail.com) --- Xorg configuration files have nothing to do with this problem, but currently I have: /etc/X11/xorg.conf.d/10-monitor.conf Section "Monitor" Identifier "HDMI-1" Option "Primary" "False"

[Bug 210303] Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 --- Comment #7 from mkkot (marcin2...@gmail.com) --- Created attachment 293777 --> https://bugzilla.kernel.org/attachment.cgi?id=293777&action=edit dmesg -- You are receiving this mail because: You are watching the assignee of the bug. ___

[Bug 210303] Ryzen 3 PRO 4350G GPU Failed to updateMST allocation table

https://bugzilla.kernel.org/show_bug.cgi?id=210303 --- Comment #8 from mkkot (marcin2...@gmail.com) --- Created attachment 293779 --> https://bugzilla.kernel.org/attachment.cgi?id=293779&action=edit DDC proble of monitor and TV -- You are receiving this mail because: You are watching the assig

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 All Event Live Here (fasix52...@tjuln.com) changed: What|Removed |Added CC||fasix52...@tj

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #28 from All Event Live Here (fasix52...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/287301 https://gitlab.com/gitlab-org/gitlab/-/issues/287302 https://gitlab.com/gitlab-org/gitlab/-/issues/287303 https://gitlab.com/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #29 from All Event Live Here (fasix52...@tjuln.com) --- https://www.pexels.com/@broncos-vs-dolphins-live-free-nfl-2020-online-6230764 https://www.pexels.com/@dolphin-vs-broncos-live-free-nfl-2020-6230776 https://www.pexels.com/@charger

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #30 from All Event Live Here (fasix52...@tjuln.com) --- https://www.pexels.com/@live-broncos-vs-dolphins-livestream-free-6230961 https://www.pexels.com/@live-chargers-vs-jets-livestream-free-6230973 https://www.pexels.com/@live-colts-v

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #31 from All Event Live Here (fasix52...@tjuln.com) --- https://gitlab.com/gitlab-org/gitlab/-/issues/287479 https://gitlab.com/gitlab-org/gitlab/-/issues/287481 https://gitlab.com/gitlab-org/gitlab/-/issues/287482 https://gitlab.com/g

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #32 from All Event Live Here (fasix52...@tjuln.com) --- https://www.pexels.com/@live-raiders-vs-chiefs-livestream-free-6231452 https://www.pexels.com/@live-chiefs-vs-raiders-livestream-free-nfl-6231462 https://www.pexels.com/@live-raid

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #33 from All Event Live Here (fasix52...@tjuln.com) --- https://www.cwu.edu/ce/sites/cts.cwu.edu.ce/files/webform/Raiders-v-Chiefs-liv-hd-tv-01_0.html https://www.cwu.edu/ce/sites/cts.cwu.edu.ce/files/webform/Raiders-v-Chiefs-liv-hd-tv

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #34 from All Event Live Here (fasix52...@tjuln.com) --- https://www.cwu.edu/ce/sites/cts.cwu.edu.ce/files/webform/Chiefs-v-Raiders-live-50.html https://www.cwu.edu/ce/sites/cts.cwu.edu.ce/files/webform/Chiefs-v-Raiders-live-51.html htt

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #35 from All Event Live Here (fasix52...@tjuln.com) --- https://www.cwu.edu/ce/sites/cts.cwu.edu.ce/files/webform/Chiefs-v-Raiders-live-61.html https://www.cwu.edu/ce/sites/cts.cwu.edu.ce/files/webform/Chiefs-v-Raiders-live-62.html htt

[Bug 205675] Display locks up. AMDGPU timeout

https://bugzilla.kernel.org/show_bug.cgi?id=205675 --- Comment #36 from All Event Live Here (fasix52...@tjuln.com) --- https://www.cwu.edu/ce/sites/cts.cwu.edu.ce/files/webform/Chiefs-v-Raiders-live-61.html https://www.cwu.edu/ce/sites/cts.cwu.edu.ce/files/webform/Chiefs-v-Raiders-live-62.html htt

[Bug 215669] New: [drm:gfx_v10_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream

https://bugzilla.kernel.org/show_bug.cgi?id=215669 Bug ID: 215669 Summary: [drm:gfx_v10_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream Product: Drivers Version: 2.5 Kernel Version: 5.10.103-1-MANJARO x

[Bug 215669] [drm:gfx_v10_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream

https://bugzilla.kernel.org/show_bug.cgi?id=215669 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

[Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125

https://bugzilla.kernel.org/show_bug.cgi?id=205089 --- Comment #33 from Alex Deucher (alexdeuc...@gmail.com) --- Please try newer or older mesa drivers if you can repro this with a particular game like dota2. The kernel driver is just the messenger. -- You may reply to this email to add a comme

[Bug 215669] [drm:gfx_v10_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream

https://bugzilla.kernel.org/show_bug.cgi?id=215669 --- Comment #2 from Andreas Polnas (andreas.polna...@hotmail.com) --- Thanks Alex, I have posted it on the mesa gitlab as an issue shown below: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6113 -- You may reply to this email to add a comme

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #8 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300550 --> https://bugzilla.kernel.org/attachment.cgi?id=300550&action=edit kernel dmesg (kernel 5.17-rc7, CONFIG_DRM_RADEON=m, Talos II) Seems this is issue already fi

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #9 from Alex Deucher (alexdeuc...@gmail.com) --- Only the person that filed the bug can close it. If it's fixed for you, please close it. Thanks! -- You may reply to this email to add a comment. You are receiving this mail because

[Bug 215648] amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=215648 Philipp Riederer (pr_ker...@tum.fail) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed

https://bugzilla.kernel.org/show_bug.cgi?id=211807 notsyncing (song...@gmail.com) changed: What|Removed |Added CC||song...@gmail.com --- Co

[Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125

https://bugzilla.kernel.org/show_bug.cgi?id=205089 Christine Lemmer-Webber (cweb...@dustycloud.org) changed: What|Removed |Added CC||cweb...

[Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125

https://bugzilla.kernel.org/show_bug.cgi?id=205089 --- Comment #35 from Christine Lemmer-Webber (cweb...@dustycloud.org) --- Here's the dmesg output that appears to be associated with when everything broke: [ 51.645260] amdgpu :05:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vm

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED Resol

[Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125

https://bugzilla.kernel.org/show_bug.cgi?id=205089 Joris L. (commandl...@protonmail.com) changed: What|Removed |Added CC||commandl...@proton

[Bug 215727] New: drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout when using firefox, chrome or icaclient

https://bugzilla.kernel.org/show_bug.cgi?id=215727 Bug ID: 215727 Summary: drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout when using firefox, chrome or icaclient Product: Drivers Version: 2.5

[Bug 215727] drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout when using firefox, chrome or icaclient

https://bugzilla.kernel.org/show_bug.cgi?id=215727 --- Comment #1 from Wojciech Krol (scal...@poczta.fm) --- Created attachment 300600 --> https://bugzilla.kernel.org/attachment.cgi?id=300600&action=edit Partial umr -R gfx_0.0.0 -- You may reply to this email to add a comment. You are receivi

[Bug 215727] drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout when using firefox, chrome or icaclient

https://bugzilla.kernel.org/show_bug.cgi?id=215727 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 213983] WARNING: CPU: 3 PID: 520 at drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x7a/0x803 [ttm]

https://bugzilla.kernel.org/show_bug.cgi?id=213983 François Cami (f...@fcami.net) changed: What|Removed |Added CC||f...@fcami.net --- Comme

[Bug 213983] WARNING: CPU: 3 PID: 520 at drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x7a/0x803 [ttm]

https://bugzilla.kernel.org/show_bug.cgi?id=213983 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- While this being true this one is the older bug (2021-08-06) and the duplicate is the later one (2021-10-04) in timeline. Also the bugs being linked you can have a look at the other bugs da

[Bug 215631] New: Some Desktop oriented mode setting drivers are missing DRM PRIME support

https://bugzilla.kernel.org/show_bug.cgi?id=215631 Bug ID: 215631 Summary: Some Desktop oriented mode setting drivers are missing DRM PRIME support Product: Drivers Version: 2.5 Kernel Version: 5.14 Hardware: Intel

[Bug 201957] amdgpu: ring gfx timeout

https://bugzilla.kernel.org/show_bug.cgi?id=201957 --- Comment #66 from Randune (randyk...@gmail.com) --- So I've been running for about 2.5 weeks now using the amdgpu.runpm=0 kernel parameter and I've had no crashes or freezes so far. I'm cautiously optimistic that for me at least this may have s

[Bug 201957] amdgpu: ring gfx timeout

https://bugzilla.kernel.org/show_bug.cgi?id=201957 --- Comment #67 from Alex Deucher (alexdeuc...@gmail.com) --- (In reply to Randune from comment #66) > > I understand that amdgpu.runpm=0 is related to power management but I don't > know the specifics. Possibly Alex Deucher can chime in and spec

[Bug 215511] Dual monitor with amd 5700 causes system to hang at startup.

https://bugzilla.kernel.org/show_bug.cgi?id=215511 Philipp Riederer (pr_ker...@tum.fail) changed: What|Removed |Added CC||pr_ker...@tum.fail

[Bug 215511] Dual monitor with amd 5700 causes system to hang at startup.

https://bugzilla.kernel.org/show_bug.cgi?id=215511 --- Comment #8 from Alex Deucher (alexdeuc...@gmail.com) --- (In reply to Philipp Riederer from comment #7) > Hi! > > My Lenovo T14s (AMD) crashes with a panic (https://imgur.com/a/P6Twvov) when > I unplug/replug any monitor. This also happens wh

[Bug 215511] Dual monitor with amd 5700 causes system to hang at startup.

https://bugzilla.kernel.org/show_bug.cgi?id=215511 --- Comment #9 from Philipp Riederer (pr_ker...@tum.fail) --- Certainly. Thank you! -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

[Bug 215648] New: amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=215648 Bug ID: 215648 Summary: amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic Product: Drivers Version: 2.5 Kernel Version: 5.15.12 Ha

[Bug 215648] amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=215648 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

[Bug 215648] amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=215648 --- Comment #2 from Philipp Riederer (pr_ker...@tum.fail) --- Hey, this is the log I could recover: > <4>[ 70.829010] RSP: 0018:ad060ad67838 EFLAGS: 0202 > <4>[ 70.829013] RAX: RBX: 92c82ff28000 RCX: > 00

[Bug 215648] amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=215648 --- Comment #3 from Alex Deucher (alexdeuc...@gmail.com) --- Thanks. Can you get the dmesg output from boot prior to the hang? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee

[Bug 215648] amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=215648 --- Comment #4 from Philipp Riederer (pr_ker...@tum.fail) --- Created attachment 300517 --> https://bugzilla.kernel.org/attachment.cgi?id=300517&action=edit dmesg from boot using kernel 5.15.12@94ba5b0fb52d6dbf1f200351876a839afb74aedd -- You m

[Bug 215648] amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=215648 --- Comment #5 from Philipp Riederer (pr_ker...@tum.fail) --- Hey, Thank you for working on this! I added the dmesg as attachment to the bug. Please note that this is from the working kernel (commit 94ba5b0fb52d6dbf1f200351876a839afb74aedd) as t

[Bug 215652] New: kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 Bug ID: 215652 Summary: kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)" Produ

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300521 --> https://bugzilla.kernel.org/attachment.cgi?id=300521&action=edit kernel dmesg (kernel 5.17-rc5, CONFIG_DRM_RADEON=y, Talos II) -- You may reply to this emai

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300522 --> https://bugzilla.kernel.org/attachment.cgi?id=300522&action=edit kernel .config (kernel 5.17-rc5, CONFIG_DRM_RADEON=m, Talos II) -- You may reply to this em

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- No I don't use an initrd. The kernel to boot the Talos is on a boot partition, modules are loaded from root partition. Which worked in 5.16 and before. Now I am getting this "could not inser

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- Ok, changed my config to include the firmware via CONFIG_EXTRA_FIRMWARE="radeon/R520_cp.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" With CONFIG_DRM_RADEON=y the machine boots now as expe

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #6 from Alex Deucher (alexdeuc...@gmail.com) --- (In reply to Erhard F. from comment #5) > > With CONFIG_DRM_RADEON=m radeon does not load and I still get "modprobe: > ERROR: could not insert 'radeon': Unknown symbol in module, or unk

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- (In reply to Alex Deucher from comment #6) > You need to make sure the firmware is in your initrd. When the kernel > loads, it loads from the initrd. There is no filesystem mounted yet whe

[Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125

https://bugzilla.kernel.org/show_bug.cgi?id=205089 zccrs (zc...@live.com) changed: What|Removed |Added CC||zc...@live.com --- Comment #32 f

[Bug 214197] [Asus G713QY] RX6800M not usable after exiting Vulkan application

https://bugzilla.kernel.org/show_bug.cgi?id=214197 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

[Bug 214197] [Asus G713QY] RX6800M not usable after exiting Vulkan application

https://bugzilla.kernel.org/show_bug.cgi?id=214197 --- Comment #2 from Alex Deucher (alexdeuc...@gmail.com) --- Does this patch fix the issue? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=202ead5a3c589b0594a75cb99f080174f6851fed -- You may reply to this email to

[Bug 211425] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 20secs aborting

https://bugzilla.kernel.org/show_bug.cgi?id=211425 Andreas (icedragon...@web.de) changed: What|Removed |Added Kernel Version|5.13.11 |5.13.13 -- You may reply

[Bug 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed

https://bugzilla.kernel.org/show_bug.cgi?id=211807 Nils Tonnätt (nils.tonna...@posteo.de) changed: What|Removed |Added CC||nils.tonna...@pos

[Bug 214207] New: Nouveau crash after play youtube video from surf browser

https://bugzilla.kernel.org/show_bug.cgi?id=214207 Bug ID: 214207 Summary: Nouveau crash after play youtube video from surf browser Product: Drivers Version: 2.5 Kernel Version: 5.10.0-8-amd64 Hardware: x86-64

[Bug 214207] Nouveau crash after play youtube video from surf browser

https://bugzilla.kernel.org/show_bug.cgi?id=214207 Alexey Boldyrev (ne-vleza...@yandex.ru) changed: What|Removed |Added Keywords||opw

<    2   3   4   5   6   7   8   9   10   11   >