amd issueshttps://gitlab.freedesktop.org/drm/amd/-/issues2023-08-23T20:36:22Zhttps://gitlab.freedesktop.org/drm/amd/-/issues/1513wrong colors & cursor gamma vs. modesetting/Wayland on RDNA22023-08-23T20:36:22Zaufkrawallwrong colors & cursor gamma vs. modesetting/Wayland on RDNA2Since I've swapped my RX 5700 XT with an RX 6800, some colors are very noticeably off with xf86-video-amdgpu. It is very noticeable with the top blue bar on GitHub where the last commit and the total number of commits are listed (Example...Since I've swapped my RX 5700 XT with an RX 6800, some colors are very noticeably off with xf86-video-amdgpu. It is very noticeable with the top blue bar on GitHub where the last commit and the total number of commits are listed (Example site: https://github.com/torvalds/linux ) . With xf86-video-amdgpu, the top bar's blue color is rather turquoise instead of the regular colder blue tone. This can't be captured in screenshots. When opening such a screenshot with xf86-video-amdgpu, it's still turquoise, whereas with modesetting DDX (or Wayland) it's the regular blue tone. For testing reasons, I forcefully deleted colord so no color adjustments could take place, but the issue was unchanged. It happens also in every browser and also with color calibration turned off (e.g. gfx.color_management.mode = 0 in Firefox).
Perhaps another aspect of the same issue: There seems to be a too dark gamma applied to the hardware cursor. This is not visible with many typical desktop cursor themes which are either black or white, but e.g. when games change the cursor theme this gets apparent. This also only occurs with xf86-video-amdgpu and only since the RDNA2 card is installed.
Tested with Linux 5.11 and 5.12-rc1* (*should not be used with swap). I've also tested without any kernel command line argument like custom EDID. Arch Linux, Xorg 1.20.10, xf86-video-amdgpu 19.1 & git-master.
[Xorg.0.log](/uploads/ca1510c07e57db5c3eaf540cd927378e/Xorg.0.log)Harry WentlandHarry Wentlandhttps://gitlab.freedesktop.org/drm/amd/-/issues/2354Flickering or constant solid white screen with kernel >=6.1.4 w/ 64GB+ RAM2024-03-17T18:14:11ZPetronio CoelhoFlickering or constant solid white screen with kernel >=6.1.4 w/ 64GB+ RAMAfter upgrading to kernel 6.1.4 or later I get either a strong flickering white screen or solid. Some details:
- Occurs after logging into Gnome, but not at the login screen
- Sometimes the full display is constant solid white and some...After upgrading to kernel 6.1.4 or later I get either a strong flickering white screen or solid. Some details:
- Occurs after logging into Gnome, but not at the login screen
- Sometimes the full display is constant solid white and sometimes it flickers solid white several times a second
- When solid white, cursor is still visible and moveable
- No sign of processes crashing or kernel backtrace in logs
- Occurs with both Wayland and X11 sessions
After going through the patchset in 6.1.4 and testing while reverting, I was able to locate the commit that introduced the issue: [drm/amdgpu: make display pinning more flexible (v2)](https://cgit.freedesktop.org/drm/drm/commit/?id=81d0bcf9900932633d270d5bc4a54ff599c6ebdb) . Reverting the commit eliminates the issue all the way through to 6.1.6 .
## Hardware description:
- CPU: AMD Ryzen 7950X
- GPU: Integrated `36:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1)`
- System Memory: 64GB DDR5
- Display: LG 27UL650
- Type of Display Connection: HDMI
## System information:
- Distro name and Version: Gentoo
- Kernel version: 6.1.6
- Custom kernel: Gentoo patches
- AMD official driver version: N/A
## How to reproduce the issue:
- Boot computer
- Login to Gnome sessionhttps://gitlab.freedesktop.org/drm/amd/-/issues/1271Screen flickering with ASUS TUF GAMING A15 laptop (FX506IV)2023-05-25T04:15:05ZJoonas CoataneaScreen flickering with ASUS TUF GAMING A15 laptop (FX506IV)Hi,
I'm currently experiencing a problem with the amdgpu driver that causes the screen to flicker (turn off and back on quickly) at a regular interval.
This also occurs with the modesetting driver.
Turning the screen off and back on agai...Hi,
I'm currently experiencing a problem with the amdgpu driver that causes the screen to flicker (turn off and back on quickly) at a regular interval.
This also occurs with the modesetting driver.
Turning the screen off and back on again using `xset dpms force off` fixes the issue, but the screen can start flickering again if it turns off and back on again afterwards (using `xset dpms force off` or due to inactivity).
Also, I get the following error in dmesg, whenever i use `xset dpms force off` to turn the screen off and back on again, or the screen turns off and back on again due to inactivity:
```
[ 2257.034515] [drm:dpcd_set_source_specific_data [amdgpu]] *ERROR* Error in DP aux read transaction, not writing source specific data
[ 2257.141722] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized.
[ 2257.141726] [drm] [Link 0] WARNING MOD_HDCP_STATUS_FAILURE IN STATE HDCP_UNINITIALIZED STAY COUNT 0
```
Here is my `Xorg.0.log` log file:
[https://pastebin.com/jDtEqj74](https://pastebin.com/jDtEqj74)
Here is my `dmesg` log:
[https://pastebin.com/E074CSsv](https://pastebin.com/E074CSsv)
In addition, here is a recording of the flickering:
[https://drive.google.com/file/d/1IIpwEVYmNsdKPkiB2042OZ7cvvJYqjob/view?usp=sharing](https://drive.google.com/file/d/1IIpwEVYmNsdKPkiB2042OZ7cvvJYqjob/view?usp=sharing)
System info:
Linux distribution: Arch Linux
Laptop name: ASUS TUF GAMING A15
Laptop model: FX506IV
CPU: AMD Ryzen 9 4900H with builtin Radeon graphics.
Discrete GPU: Nvidia Geforce RTX 2060
Screen: 144Hz screen with "adaptive sync" support (whether this is AMD's FreeSync or NVIDIA's GSYNC i am unsure)https://gitlab.freedesktop.org/drm/amd/-/issues/900[amdgpu/Navi] [powerplay] Failed to send message errors2020-04-17T20:35:41ZBugzilla Migration User[amdgpu/Navi] [powerplay] Failed to send message errors## Submitted by Shmerl `@shmerl`
Assigned to **Default DRI bug account**
**[Link to original bug (#111555)](https://bugs.freedesktop.org/show_bug.cgi?id=111555)**
## Description
I get periodic errors like this in dmesg, which coin...## Submitted by Shmerl `@shmerl`
Assigned to **Default DRI bug account**
**[Link to original bug (#111555)](https://bugs.freedesktop.org/show_bug.cgi?id=111555)**
## Description
I get periodic errors like this in dmesg, which coincides with intermittent system stalls:<br>
<br>
[Wed Sep 4 00:43:43 2019] amdgpu: [powerplay] Failed to send message 0x12, response 0xfffffffb param 0x6<br>
[Wed Sep 4 00:43:43 2019] amdgpu: [powerplay] Failed to export SMU metrics table!<br>
[Wed Sep 4 00:44:53 2019] amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, param 0x80<br>
[Wed Sep 4 00:44:53 2019] amdgpu: [powerplay] Failed to send message 0xf, response 0xfffffffb, param 0xa90000<br>
[Wed Sep 4 00:45:30 2019] amdgpu: [powerplay] Failed to send message 0x12, response 0xfffffffb, param 0x6<br>
[Wed Sep 4 00:45:35 2019] amdgpu: [powerplay] Failed to send message 0x12, response 0xfffffffb param 0x6<br>
[Wed Sep 4 00:45:35 2019] amdgpu: [powerplay] Failed to export SMU metrics table!<br>
<br>
I'm running kernel 5.3-rc7<br>
GPU: Sapphire Pulse RX 5700XT (Navi 10) with firmware from https://people.freedesktop.org/~agd5f/radeon_ucode/navi10/<br>
Distro: Debian testing / KDE.<br>
<br>
I noticed, that it starts happening often when I'm using ksysguard, which queries lm-sensors for amdgpu temperature and fan speed.https://gitlab.freedesktop.org/drm/amd/-/issues/929AMD Navi10 GPU powerplay issues when using two DisplayPort connectors2023-05-25T04:59:11ZBugzilla Migration UserAMD Navi10 GPU powerplay issues when using two DisplayPort connectors## Submitted by Timur Kristóf
Assigned to **Default DRI bug account**
**[Link to original bug (#111913)](https://bugs.freedesktop.org/show_bug.cgi?id=111913)**
## Description
I have a Sapphire AMD RX 5700XT graphics card (the refe...## Submitted by Timur Kristóf
Assigned to **Default DRI bug account**
**[Link to original bug (#111913)](https://bugs.freedesktop.org/show_bug.cgi?id=111913)**
## Description
I have a Sapphire AMD RX 5700XT graphics card (the reference design).<br>
<br>
When I use DisplayPort-0 and DisplayPort-1 connectors with two Dell U2718Q monitors, I get the following errors in dmesg.<br>
<br>
[ 39.270292] amdgpu: [powerplay] failed send message: TransferTableSmu2Dram (18) param: 0x00000006 response 0xffffffc2<br>
[ 39.270294] amdgpu: [powerplay] Failed to export SMU metrics table!<br>
[ 41.787785] amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14) param: 0x00000080 response 0xffffffc2<br>
[ 44.288882] amdgpu: [powerplay] failed send message: TransferTableSmu2Dram (18) param: 0x00000006 response 0xffffffc2<br>
[ 44.288883] amdgpu: [powerplay] Failed to export SMU metrics table!<br>
[ 46.822924] amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14) param: 0x00000080 response 0xffffffc2<br>
[ 49.237444] amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14) param: 0x00000080 response 0xffffffc2<br>
[ 49.353456] amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14) param: 0x00000080 response 0xffffffc2<br>
[ 49.353457] amdgpu: [powerplay] Failed to export SMU metrics table!<br>
[ 66.676957] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 69.095868] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 71.634371] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 74.166180] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 76.526822] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 78.804664] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 81.348866] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 83.881667] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 86.335097] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 88.763558] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 91.209310] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 93.740772] amdgpu: [powerplay] failed send message: NumOfDisplays (64) param: 0x00000002 response 0xffffffc2<br>
[ 128.174369] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00000000 response 0xffffffc2<br>
[ 130.597545] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00000000 response 0xffffffc2<br>
[ 133.135948] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00020000 response 0xffffffc2<br>
[ 135.676398] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00020000 response 0xffffffc2<br>
[ 138.213539] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00000000 response 0xffffffc2<br>
[ 140.753936] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00000000 response 0xffffffc2<br>
[ 143.034004] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00020000 response 0xffffffc2<br>
[ 145.313763] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00020000 response 0xffffffc2<br>
[ 151.255023] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00000000 response 0xffffffc2<br>
[ 153.531678] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00000000 response 0xffffffc2<br>
[ 156.054509] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00020000 response 0xffffffc2<br>
[ 156.054516] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00020000 response 0xfffffffb<br>
[ 156.057923] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00000000 response 0xfffffffb<br>
[ 156.057930] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00000000 response 0xfffffffb<br>
[ 156.057932] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00020000 response 0xfffffffb<br>
[ 156.057938] amdgpu: [powerplay] failed send message: GetMaxDpmFreq (31) param: 0x00020000 response 0xfffffffbhttps://gitlab.freedesktop.org/drm/amd/-/issues/926Navi "divide error" hang2023-05-25T04:59:12ZBugzilla Migration UserNavi "divide error" hang## Submitted by Doug Tyrrell `@DougTy`
Assigned to **Default DRI bug account**
**[Link to original bug (#111869)](https://bugs.freedesktop.org/show_bug.cgi?id=111869)**
## Description
Created attachment 145593<br>
divide-error_09-...## Submitted by Doug Tyrrell `@DougTy`
Assigned to **Default DRI bug account**
**[Link to original bug (#111869)](https://bugs.freedesktop.org/show_bug.cgi?id=111869)**
## Description
Created attachment 145593<br>
divide-error_09-20.txt<br>
<br>
Occasionally, usually while watching videos in Firefox, my GPU will hang and the screen will freeze -- sound and keyboard input still work in the background, and I need to use REISUB hotkeys to reboot. This is separate, in addition to the sdma and ring gfx_0.0.0 hangs.<br>
<br>
Upon rebooting, journalctl shows the attached "divide error". I've included logs from 3 instances of it happening. I'm currently using the Jul 14 firmware from Fedora's linux-firmware package as the hang appears to occur more often on the newer firmware from https://people.freedesktop.org/~agd5f/radeon_ucode/navi10/ however this may just be placebo.<br>
<br>
It occurs with or without the "0-sized IBs" kernel patch from https://bugs.freedesktop.org/show_bug.cgi?id=111481#c33 and on both PCIe 3.0 and 4.0. I'm not using a PCIe riser and the card works without issue on Windows 10 dual boot.<br>
<br>
CPU: 3700X<br>
GPU: Sapphire 5700XT (reference)<br>
Motherboard: Gigabyte X570-I (BIOS F4)<br>
Kernel: 5.3.0<br>
Mesa: mesa-git 1:19.3.0_devel.115682.3c966fd688c-1<br>
LLVM: llvm-git 10.0.0_r327425.63f6066b53d-1<br>
<br>
Please let me know if any more information would be helpful, or if there's anything I can do to troubleshoot. Thanks.<br>
<br>
**Attachment 145593**, "divide-error_09-20.txt": <br>
[divide-error_09-20.txt](/uploads/70260d90673d9661305110efaba34263/divide-error_09-20.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/914ring_gfx hangs/freezes on Navi gpus2023-05-25T05:00:13ZBugzilla Migration Userring_gfx hangs/freezes on Navi gpus## Submitted by Marko Popovic
Assigned to **Default DRI bug account**
**[Link to original bug (#111763)](https://bugs.freedesktop.org/show_bug.cgi?id=111763)**
## Description
I'm making this topic as a separate tracking of ring_gf...## Submitted by Marko Popovic
Assigned to **Default DRI bug account**
**[Link to original bug (#111763)](https://bugs.freedesktop.org/show_bug.cgi?id=111763)**
## Description
I'm making this topic as a separate tracking of ring_gfx related bugs since we should keep https://bugs.freedesktop.org/show_bug.cgi?id=111481 related to sdma0/1 type freezes since those are ones that seem to cause random "Out of the blue" hangs on the desktop.<br>
<br>
There is another type of freeze/hang happening when playing Starcraft II via D9VK. This one doesn't seem to be related to either ngg or dma because I have them both disabled by AMD_DEBUG=nodma and AMD_DEBUG=nongg and the hangs occur anyway, on exactly the same place every time.<br>
<br>
Error logs:<br>
sep 17 11:48:24 Marko-PC kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!<br>
sep 17 11:48:24 Marko-PC kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2361623, emitted seq=2361625<br>
sep 17 11:48:24 Marko-PC kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process SC2_x64.exe pid 20236 thread SC2_x64.exe pid 20236<br>
<br>
I will try and provide trace files by using renderdoc for described issues. They also happen in native games like Rise of the Tomb Raider and Vulkan etc. Will provide as much info as possible.<br>
<br>
Using Kernel 5.3, MESA 19.2 and llvm9.https://gitlab.freedesktop.org/drm/amd/-/issues/8265.0 kernel crash , drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't update ...2023-05-25T05:05:07ZBugzilla Migration User5.0 kernel crash , drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't update BO_VA (-2)## Submitted by wormwang
Assigned to **Default DRI bug account**
**[Link to original bug (#110887)](https://bugs.freedesktop.org/show_bug.cgi?id=110887)**
## Description
Env: kernel 5.0.13, AMD rx580 GPU 8GB<br>
<br>
<br>
We run a...## Submitted by wormwang
Assigned to **Default DRI bug account**
**[Link to original bug (#110887)](https://bugs.freedesktop.org/show_bug.cgi?id=110887)**
## Description
Env: kernel 5.0.13, AMD rx580 GPU 8GB<br>
<br>
<br>
We run about 32 game soft on the GPU concurrently and run a media <br>
encoder soft on VCE by vaapi at same time.<br>
<br>
We meet the kernel crash, after runing 3 to 7 days. . We meet such crash <br>
5 times. We had enabled kdump ,if you need other kernel dump info, we <br>
can upload them<br>
<br>
<br>
Log:<br>
<br>
[172936.893428] binder_dkms: binder_deferred_func, binder_index = 12<br>
[172937.052608] pci_generic_config_write32: 138 callbacks suppressed<br>
[172937.052615] pci_bus 000d:30: 2-byte config write to 000d:30:00.0 <br>
offset 0x4 may corrupt adjacent RW1C bits<br>
[172937.052633] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0x44 may corrupt adjacent RW1C bits<br>
[172937.054110] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.062690] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.069361] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0x78 may corrupt adjacent RW1C bits<br>
[172937.071029] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0x80 may corrupt adjacent RW1C bits<br>
[172937.071034] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0x8c may corrupt adjacent RW1C bits<br>
[172937.071038] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0x98 may corrupt adjacent RW1C bits<br>
[172937.071042] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0xa0 may corrupt adjacent RW1C bits<br>
[172937.071083] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0x44 may corrupt adjacent RW1C bits<br>
[172937.071091] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.071094] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0x44 may corrupt adjacent RW1C bits<br>
[172937.071110] pci_bus 000c:20: 2-byte config write to 000c:20:00.0 <br>
offset 0x4 may corrupt adjacent RW1C bits<br>
[172937.079477] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.087723] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.095955] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.104270] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.112418] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.120490] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.128525] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.136557] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.144446] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.152254] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.160039] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.167779] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.175490] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.176747] binder_dkms: binder_defer_work 12<br>
[172937.183035] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.183075] binder_dkms: binder_deferred_func, binder_index = 12<br>
[172937.355641] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.362028] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.368253] pcieport 0004:48:00.0: can't derive routing for PCI INT A<br>
[172937.368425] megaraid_sas 0004:49:00.0: PCI INT A: no GSI<br>
[172937.368585] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.370828] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.375070] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.375167] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.375190] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.381702] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.381732] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.387959] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.387990] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.394171] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.394186] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.400498] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.400523] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.406755] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.406775] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.412977] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.412998] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.419250] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.419273] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.422361] [drm] schedsdma0 is not ready, skipping<br>
[172937.422363] [drm] schedsdma1 is not ready, skipping<br>
[172937.422448] [drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't <br>
update BO_VA (-2)<br>
[172937.425437] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.425450] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.431814] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.431837] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.438038] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.438054] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.450635] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.454268] pcieport 0002:e8:00.0: can't derive routing for PCI INT B<br>
[172937.454272] ixgbe 0002:e9:00.1: PCI INT B: no GSI<br>
[172937.456923] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.456967] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.463122] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.463148] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.469428] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.469455] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.475705] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.475722] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.481928] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.481946] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.488092] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.488108] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.494407] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.494440] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.500663] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.500678] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.506909] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.506930] amdgpu 0005:01:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.511392] [drm] schedsdma0 is not ready, skipping<br>
[172937.511394] [drm] schedsdma1 is not ready, skipping<br>
[172937.511481] [drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't <br>
update BO_VA (-2)<br>
[172937.512346] Unable to handle kernel access to user memory outside <br>
uaccess routines at virtual address 0000000000000008<br>
[172937.512348] Mem abort info:<br>
[172937.512350]???? ESR = 0x96000004<br>
[172937.512352]???? Exception class = DABT (current EL), IL = 32 bits<br>
[172937.512353]???? SET = 0, FnV = 0<br>
[172937.512354]???? EA = 0, S1PTW = 0<br>
[172937.512355] Data abort info:<br>
[172937.512356]???? ISV = 0, ISS = 0x00000004<br>
[172937.512357]???? CM = 0, WnR = 0<br>
[172937.512359] user pgtable: 4k pages, 48-bit VAs, pgdp = 00000000fb340bc6<br>
[172937.512361] [0000000000000008] pgd=000000139dfe9003, <br>
pud=00000015d583a003, pmd=0000000000000000<br>
[172937.512367] Internal error: Oops: 96000004 [#1] SMP<br>
[172937.512370] Modules linked in: nfnetlink_log veth ipt_REJECT <br>
nf_reject_ipv4 xt_comment xt_mark xt_nat xt_tcpudp ipt_MASQUERADE <br>
nf_conntrack_netlink nfnetlink xfrm_user xt_conntrack br_netfilter <br>
bridge stp llc iptable_filter xt_addrtype iptable_nat nf_nat_ipv4 nf_nat <br>
bpfilter ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 <br>
nf_defrag_ipv4 overlay nls_iso8859_1 joydev input_leds snd_hda_intel <br>
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer ipmi_ssif snd <br>
ipmi_si soundcore ipmi_devintf ipmi_msghandler tcp_bbr sch_fq ib_iser <br>
rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi <br>
scsi_transport_iscsi binder_dkms(OE) ip_tables x_tables autofs4 btrfs <br>
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq <br>
async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath <br>
linear hibmc_drm hid_generic usbhid hid ses enclosure marvell aes_ce_blk <br>
aes_ce_cipher amdgpu chash i2c_algo_bit gpu_sched ttm crct10dif_ce <br>
drm_kms_helper ghash_ce syscopyarea sha2_ce<br>
[172937.512432]?? sysfillrect sysimgblt fb_sys_fops sha256_arm64 sha1_ce <br>
ixgbe drm hisi_sas_v2_hw hisi_sas_main megaraid_sas xfrm_algo libsas <br>
mdio ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio <br>
hnae aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64<br>
[172937.512448] Process RenderThread (pid: 1569015, stack limit = <br>
0x00000000349701c4)<br>
[172937.512451] CPU: 23 PID: 1569015 Comm: RenderThread Kdump: loaded <br>
Tainted: G???????????????????? OE???????? 5.0.13-1905061257-generic #appstream<br>
[172937.512453] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.58 <br>
10/24/2018<br>
[172937.512454] pstate: 80400005 (Nzcv daif +PAN -UAO)<br>
[172937.512531] pc : amdgpu_vm_bo_update_mapping+0x120/0x3a0 [amdgpu]<br>
[172937.512603] lr : amdgpu_vm_bo_update+0x2a4/0x6b8 [amdgpu]<br>
[172937.512604] sp : ffff0000c0e4b8c0<br>
[172937.512605] x29: ffff0000c0e4b8c0 x28: ffff801fd3010000<br>
[172937.512608] x27: 0000000000000001 x26: ffff80161d777000<br>
[172937.512610] x25: 0000000000100d1f x24: 0000000000100d00<br>
[172937.512612] x23: 0000000000000000 x22: ffff809533c54f00<br>
[172937.512614] x21: 0000000000000037 x20: ffff0000116cc000<br>
[172937.512616] x19: 000000000000000a x18: 0000000000000000<br>
[172937.512618] x17: 0000000000000000 x16: 0000000000000000<br>
[172937.512620] x15: 0000000000000000 x14: 00000003000000b0<br>
[172937.512623] x13: 0000000600000240 x12: 0000000000000000<br>
[172937.512624] x11: 000000060000018d x10: 0000000000000040<br>
[172937.512627] x9 : 0000000000000000 x8 : ffff0000c0e4b860<br>
[172937.512628] x7 : 0000000000000020 x6 : 000000000000001f<br>
[172937.512631] x5 : 0000000000100d1f x4 : 0000000000100d00<br>
[172937.512633] x3 : 0000000000000000 x2 : 000000000000000b<br>
[172937.512636] x1 : 0000000000000000 x0 : <br>
ffff80161d776000[172937.512638] Call trace:<br>
[172937.512711]?? amdgpu_vm_bo_update_mapping+0x120/0x3a0 [amdgpu]<br>
[172937.512784]?? amdgpu_vm_bo_update+0x2a4/0x6b8 [amdgpu]<br>
[172937.512857]?? amdgpu_cs_ioctl+0xcbc/0x14a8 [amdgpu]<br>
[172937.512882]?? drm_ioctl_kernel+0x90/0x100 [drm]<br>
[172937.512904]?? drm_ioctl+0x1ec/0x418 [drm]<br>
[172937.512977]?? amdgpu_drm_ioctl+0x58/0x90 [amdgpu]<br>
[172937.513055] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.513136]?? amdgpu_kms_compat_ioctl+0x40/0x68 [amdgpu]<br>
[172937.513140] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.513220] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.513235] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.513311] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.513323] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.513412] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.513421] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.513497] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.513513] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.513587] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.513603] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.513677] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.513687] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.513761] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.522750] amdgpu 000d:31:00.0: couldn't schedule ib on ring `<gfx>`<br>
[172937.522822] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling <br>
IBs (-22)<br>
[172937.525171]?? __arm64_compat_sys_ioctl+0x144/0x410<br>
[172937.525177]?? el0_svc_common+0x78/0x120<br>
[172937.525179]?? el0_svc_compat_handler+0x30/0x40<br>
[172937.525182]?? el0_svc_compat+0x8/0x34<br>
[172937.525187] Code: f9406b41 b966c793 f941e800 71002e7f (f9400421)<br>
[172937.525195] SMP: stopping secondary CPUs<br>
[172937.526945] Starting crashdump kernel...<br>
[172937.526952] Bye!https://gitlab.freedesktop.org/drm/amd/-/issues/2154Performance issues after suspend (DPM is becoming disabled on resume)2023-05-02T19:56:13ZAbrar AhmedPerformance issues after suspend (DPM is becoming disabled on resume)## Brief summary of the problem:
Suspending and resuming the system results in graphics performance that is almost 3x slower than what is seen after a clean boot.
The Witcher 3 went from around 48FPS down to 14FPS on my system.
I notic...## Brief summary of the problem:
Suspending and resuming the system results in graphics performance that is almost 3x slower than what is seen after a clean boot.
The Witcher 3 went from around 48FPS down to 14FPS on my system.
I noticed that there is this message that only appears after resuming,
```Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: dpm has been disabled```
This suggests that the gpu can not properly clock up during intensive workloads?
## Hardware description:
- CPU: AMD Ryzen 5 5500U (ASUS Vivobook M513U)
- GPU: 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2)
- System Memory: 8GB
- Display(s): Internal (1920x1080) (The issue can be seen with external displays as well)
- Type of Display Connection: Internal
## System information:
- Distro name and Version: Fedora Silverblue 37 Prerelease (Same issue can be noticed on the stable 36 image too)
- Kernel version: Linux abrar-laptop 5.19.6-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Aug 31 16:56:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
- Custom kernel: N/A
- AMD official driver version: N/A
## How to reproduce the issue:
1. Restart
2. Run a graphically intensive application
3. Note down the performance
4. Turn off all apps and suspend the system
5. Resume system
6. Run the same app and notice the drastically lower performance
## Attached files:
This is the output of ```journalctl -b 0 | grep -i amd > journalctl.log```
```
Sep 08 23:34:44 fedora kernel: RAMDISK: [mem 0x58020000-0x5c721fff]
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB395000 007229 (v02 AMD AmdTable 00000002 MSFT 04000000)
Sep 08 23:34:44 fedora kernel: ACPI: IVRS 0x00000000BB394000 0001A4 (v02 AMD AmdTable 00000001 AMD 00000000)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB390000 003A21 (v01 AMD AMD AOD 00000001 INTL 20190509)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB37A000 003E88 (v02 AMD AmdTable 00000001 AMD 00000001)
Sep 08 23:34:44 fedora kernel: ACPI: CRAT 0x00000000BB379000 000BA8 (v01 AMD AmdTable 00000001 AMD 00000001)
Sep 08 23:34:44 fedora kernel: ACPI: CDIT 0x00000000BB378000 000029 (v01 AMD AmdTable 00000001 AMD 00000001)
Sep 08 23:34:44 fedora kernel: ACPI: VFCT 0x00000000BB36A000 00D884 (v01 _ASUS_ Notebook 00000001 AMD 31504F47)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB367000 000149 (v01 AMD AmdTable 00000001 INTL 20190509)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB366000 0007CC (v01 AMD AmdTable 00000001 INTL 20190509)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB364000 00148E (v01 AMD AmdTable 00000001 INTL 20190509)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB362000 00151E (v01 AMD AmdTable 00000001 INTL 20190509)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB35E000 0036E9 (v01 AMD AmdTable 00000001 INTL 20190509)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB35B000 00008D (v01 AMD AmdTable 00000001 INTL 20190509)
Sep 08 23:34:44 fedora kernel: ACPI: SSDT 0x00000000BB35A000 00091F (v01 AMD AmdTable 00000001 INTL 20190509)
Sep 08 23:34:44 fedora kernel: AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR0, rdevid:160
Sep 08 23:34:44 fedora kernel: AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR1, rdevid:160
Sep 08 23:34:44 fedora kernel: AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR2, rdevid:160
Sep 08 23:34:44 fedora kernel: AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR3, rdevid:160
Sep 08 23:34:44 fedora kernel: smpboot: CPU0: AMD Ryzen 5 5500U with Radeon Graphics (family: 0x17, model: 0x68, stepping: 0x1)
Sep 08 23:34:44 fedora kernel: Performance Events: Fam17h+ core perfctr, AMD PMU driver.
Sep 08 23:34:44 fedora kernel: pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
Sep 08 23:34:44 fedora kernel: pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
Sep 08 23:34:44 fedora kernel: AMD-Vi: Extended features (0x206d73ef22254ade): PPR X2APIC NX GT IA GA PC GA_vAPIC
Sep 08 23:34:44 fedora kernel: AMD-Vi: Interrupt remapping enabled
Sep 08 23:34:44 fedora kernel: AMD-Vi: Virtual APIC enabled
Sep 08 23:34:44 fedora kernel: AMD-Vi: X2APIC enabled
Sep 08 23:34:44 fedora kernel: perf: AMD IBS detected (0x000003ff)
Sep 08 23:34:44 fedora kernel: amd_uncore: 4 amd_df counters detected
Sep 08 23:34:44 fedora kernel: amd_uncore: 6 amd_l3 counters detected
Sep 08 23:34:44 fedora kernel: perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
Sep 08 23:34:44 fedora kernel: input: ELAN1300:00 04F3:3104 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1300:00/0018:04F3:3104.0001/input/input5
Sep 08 23:34:44 fedora kernel: input: ELAN1300:00 04F3:3104 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1300:00/0018:04F3:3104.0001/input/input6
Sep 08 23:34:44 fedora kernel: input: ELAN1300:00 04F3:3104 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1300:00/0018:04F3:3104.0001/input/input7
Sep 08 23:34:44 fedora kernel: input: ELAN1300:00 04F3:3104 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1300:00/0018:04F3:3104.0001/input/input8
Sep 08 23:34:45 fedora kernel: AMD-Vi: AMD IOMMUv2 loaded and initialized
Sep 08 23:34:46 fedora kernel: [drm] amdgpu kernel modesetting enabled.
Sep 08 23:34:46 fedora kernel: amdgpu: Virtual CRAT table created for CPU
Sep 08 23:34:46 fedora kernel: amdgpu: Topology: Add CPU node
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: vgaarb: deactivate vga console
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
Sep 08 23:34:47 fedora kernel: amdgpu: ATOM BIOS: 113-LUCIENNE-016
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: PCIE atomic ops is not supported
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: MODE2 reset
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
Sep 08 23:34:47 fedora kernel: [drm] amdgpu: 512M of VRAM memory ready
Sep 08 23:34:47 fedora kernel: [drm] amdgpu: 3660M of GTT memory ready.
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Sep 08 23:34:47 fedora kernel: amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
Sep 08 23:34:48 fedora kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Sep 08 23:34:48 fedora kernel: amdgpu: sdma_bitmap: 3
Sep 08 23:34:48 fedora kernel: amdgpu: HMM registered 512MB device memory
Sep 08 23:34:48 fedora kernel: amdgpu: SRAT table not found
Sep 08 23:34:48 fedora kernel: amdgpu: Virtual CRAT table created for GPU
Sep 08 23:34:48 fedora kernel: amdgpu: Topology: Add dGPU node [0x164c:0x1002]
Sep 08 23:34:48 fedora kernel: kfd kfd: amdgpu: added device 1002:164c
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 7
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Sep 08 23:34:48 fedora kernel: [drm] Initialized amdgpu 3.47.0 20150101 for 0000:03:00.0 on minor 0
Sep 08 23:34:48 fedora kernel: fbcon: amdgpudrmfb (fb0) is primary device
Sep 08 23:34:48 fedora kernel: amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Sep 08 18:04:50 abrar-laptop systemd[1]: Starting systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0...
Sep 08 18:04:50 abrar-laptop systemd-backlight[789]: amdgpu_bl0: Saved brightness 2 is too low; increasing to 12.
Sep 08 18:04:50 abrar-laptop systemd[1]: Finished systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.
Sep 08 18:04:50 abrar-laptop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-backlight@backlight:amdgpu_bl0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 08 18:04:50 abrar-laptop kernel: snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Sep 08 18:04:51 abrar-laptop systemd[1]: mcelog.service - Machine Check Exception Logging Daemon was skipped because of a failed condition check (ConditionPathExists=!/sys/module/edac_mce_amd/initstate).
Sep 08 18:04:52 abrar-laptop gnome-shell[1095]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
Sep 08 18:04:59 abrar-laptop gnome-shell[1759]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
ELF object binary architecture: AMD x86-64
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: dpm has been disabled
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Sep 08 21:33:43 abrar-laptop kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Sep 08 21:33:44 abrar-laptop gnome-shell[84082]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
```https://gitlab.freedesktop.org/drm/amd/-/issues/883amdgpu kernel 5.2 blank display after resume from suspend2023-05-25T05:03:12ZBugzilla Migration Useramdgpu kernel 5.2 blank display after resume from suspend## Submitted by csp..@..on.net
Assigned to **Default DRI bug account**
**[Link to original bug (#111244)](https://bugs.freedesktop.org/show_bug.cgi?id=111244)**
## Description
Created attachment 144901<br>
kernel log<br>
<br>
Mode...## Submitted by csp..@..on.net
Assigned to **Default DRI bug account**
**[Link to original bug (#111244)](https://bugs.freedesktop.org/show_bug.cgi?id=111244)**
## Description
Created attachment 144901<br>
kernel log<br>
<br>
Model: Lenovo Ideapad S340 15"<br>
CPU: AMD Ryzen 5 3500U<br>
<br>
Starting with kernel 5.2, laptop has a blank display after resuming from suspend. Problem doesn't appear with recent kernels up to 5.1.16. Attached is a kernel log and git bisect logs.<br>
<br>
**Attachment 144901**, "kernel log": <br>
[kernel.log](/uploads/be0d514562bd4ed659e82a1bf81ceec6/kernel.log)<br>
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=111122https://gitlab.freedesktop.org/drm/amd/-/issues/628Enabling PP_OVERDRIVE_MASK with dual monitors causes artifacting2022-05-12T13:16:21ZBugzilla Migration UserEnabling PP_OVERDRIVE_MASK with dual monitors causes artifacting## Submitted by bou..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#108941)](https://bugs.freedesktop.org/show_bug.cgi?id=108941)**
## Description
Steps to reproduce:<br>
<br>
1) Have dual monitors<br>...## Submitted by bou..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#108941)](https://bugs.freedesktop.org/show_bug.cgi?id=108941)**
## Description
Steps to reproduce:<br>
<br>
1) Have dual monitors<br>
2) Enable PP_OVERDRIVE_MASK by flipping the appropriate bit in amdgpu.ppfeaturemask. (For my configuration I used: 0xfffd7fff)<br>
3) See artifacting.<br>
<br>
When using default featuremask, or when using a single monitor with the overdrive bit enabled behaves correctly. I heard multiple people who have the same issue, so it does not seem related to my setup.<br>
<br>
Setup:<br>
RX480<br>
Linux 4.20-rc5<br>
<br>
<br>
If additional information is needed please let me know.https://gitlab.freedesktop.org/drm/amd/-/issues/1673VAAPI is broken with 5.13.x linux2021-11-13T08:48:00ZPetar MargetićVAAPI is broken with 5.13.x linuxDescription:
With the Linux and Linux-zen packages updated to 5.13.x VAAPI acceleration stopped working on RX6700XT GPU, possibly on other NAVI2 GPUs
VAAPI is functional on 5.12.15.
Originally reported on arch forums here:
https://bbs.a...Description:
With the Linux and Linux-zen packages updated to 5.13.x VAAPI acceleration stopped working on RX6700XT GPU, possibly on other NAVI2 GPUs
VAAPI is functional on 5.12.15.
Originally reported on arch forums here:
https://bbs.archlinux.org/viewtopic.php?pid=1984257
Additional info:
* package version(s)
linux 5.12.15.arch1-1 (working)
linux 5.13.4.arch2-1 (broken)
mesa 21.1.5-1
libva 2.12.0-1
libva-mesa-driver 21.1.5-1
* config and/or log files etc.
output of 'vainfo' for Linux 5.12 and 5.13 respectively:
```
~ ▶ vainfo
vainfo: VA-API version: 1.12 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 21.1.5 for AMD Radeon RX 6700 XT (NAVY_FLOUNDER, DRM 3.40.0, 5.12.15-arch1-1, LLVM 12.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
```
5.13.4
```
~ ▶ vainfo
vainfo: VA-API version: 1.12 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 21.1.5 for AMD Radeon RX 6700 XT (NAVY_FLOUNDER, DRM 3.41.0, 5.13.4-arch1-1, LLVM 12.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
```
* link to upstream bug report, if any
N/A
Steps to reproduce:
Use Linux or Linux-zen 5.13.x packages and observe high CPU usage while video decoding on AMD RX6700 XT (and possibly other RX6x00 cards?)
Reportedly OBS fails to encode videos using GPU as well (kindly see reddit URLs in the aforementioned bbs topic) but that's not my use case so I cannot confirm this.https://gitlab.freedesktop.org/drm/amd/-/issues/1376Screen keeps being dark after reactivating from screensaver / powersaving2023-05-25T04:10:51ZFlorijan HamzicScreen keeps being dark after reactivating from screensaver / powersaving
### System information
```
System: Host: station Kernel: 5.9.4-arch1-1 x86_64 bits: 64 compiler: N/A Desktop: GNOME 3.38.1 tk: GTK 3.24.23
wm: gnome-shell dm: GDM, LightDM Distro: Arch Linux
CPU: Info: 16-Core (2-...
### System information
```
System: Host: station Kernel: 5.9.4-arch1-1 x86_64 bits: 64 compiler: N/A Desktop: GNOME 3.38.1 tk: GTK 3.24.23
wm: gnome-shell dm: GDM, LightDM Distro: Arch Linux
CPU: Info: 16-Core (2-Die) model: AMD Ryzen 9 3950X bits: 64 type: MT MCP MCM arch: Zen 2 L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 223679
Speed: 3591 MHz min/max: 2200/3500 MHz Core speeds (MHz): 1: 3589 2: 2048 3: 2195 4: 2196 5: 2192 6: 2195 7: 2196
8: 2196 9: 3594 10: 2046 11: 2054 12: 2051 13: 2052 14: 1981 15: 2862 16: 1983 17: 1872 18: 2194 19: 2195 20: 2193
21: 2192 22: 2193 23: 2197 24: 2050 25: 2196 26: 2191 27: 1895 28: 3199 29: 2026 30: 1992 31: 2195 32: 2196
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
vendor: Sapphire Limited driver: amdgpu v: kernel bus ID: 0d:00.0 chip ID: 1002:731f
Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: vfio-pci v: 0.2 bus ID: 0e:00.0
chip ID: 10de:1c82
Device-3: Intel ASM107x type: USB driver: uvcvideo bus ID: 2-4.1:4 chip ID: 8086:0aa5
Display: wayland server: X.Org 1.20.9 compositor: gnome-shell driver: nouveau resolution: 3440x1440~60Hz s-dpi: 96
OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.39.0 5.9.4-arch1-1 LLVM 12.0.0)
v: 4.6 Mesa 21.0.0-devel (git-dfd878f2ba) direct render: Yes
```
### Describe the issue
since a week or so screen keep to be dark after the system has put off the screen because of inactivity
mesa-git/mesa-git 1:21.0.0_devel.131002.dfd878f2bad-1
```
Nov 13 23:25:33 station gnome-shell[1251]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 13 23:25:33 station gnome-shell[1251]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 13 23:25:33 station kernel: ------------[ cut here ]------------
Nov 13 23:25:33 station kernel: WARNING: CPU: 0 PID: 1251 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:3241 dcn20_validate_bandwidth_fp+0x8d/0xd0 [amdgpu]
Nov 13 23:25:33 station kernel: Modules linked in: xt_nat veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT>
Nov 13 23:25:33 station kernel: snd k10temp pcspkr i2c_piix4 soundcore libphy rfkill ecc dca wmi evdev pinctrl_amd mac_hid acpi_cpufreq nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_def>
Nov 13 23:25:33 station kernel: CPU: 0 PID: 1251 Comm: gnome-shell Not tainted 5.9.4-arch1-1 #1
Nov 13 23:25:33 station kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 2802 10/21/2020
Nov 13 23:25:33 station kernel: RIP: 0010:dcn20_validate_bandwidth_fp+0x8d/0xd0 [amdgpu]
Nov 13 23:25:33 station kernel: Code: 00 7b 35 22 85 14 1f 00 00 75 2f 31 d2 f2 0f 11 85 58 26 00 00 48 89 ee 4c 89 e7 e8 3d f6 ff ff 89 c2 22 95 14 1f 00 00 75 30 <0f> 0b 48 89 9d 58 26 0>
Nov 13 23:25:33 station kernel: RSP: 0018:ffffabe402903ae8 EFLAGS: 00010246
Nov 13 23:25:33 station kernel: RAX: 0000000000000001 RBX: 4079400000000000 RCX: 000000000020c200
Nov 13 23:25:33 station kernel: RDX: 0000000000000000 RSI: d0f05f2b057e11b3 RDI: 00000000000311a0
Nov 13 23:25:33 station kernel: RBP: ffff88c804c80000 R08: ffff88c79beae000 R09: ffff88c7fd7b0000
Nov 13 23:25:33 station kernel: R10: ffff88c79beae000 R11: 0000000100000001 R12: ffff88c7fd7b0000
Nov 13 23:25:33 station kernel: R13: ffff88c7a1fe5688 R14: ffff88c7fc7da800 R15: ffff88c804c80000
Nov 13 23:25:33 station kernel: FS: 00007f4131af4cc0(0000) GS:ffff88c80ea00000(0000) knlGS:0000000000000000
Nov 13 23:25:33 station kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 13 23:25:33 station kernel: CR2: 0000238a6fd3d2a0 CR3: 0000000fc899a000 CR4: 0000000000350ef0
Nov 13 23:25:33 station kernel: Call Trace:
Nov 13 23:25:33 station kernel: dcn20_validate_bandwidth+0x24/0x40 [amdgpu]
Nov 13 23:25:33 station kernel: dc_validate_global_state+0x2f2/0x390 [amdgpu]
Nov 13 23:25:33 station kernel: ? preempt_count_add+0x68/0xa0
Nov 13 23:25:33 station kernel: ? _raw_spin_lock_irq+0x1a/0x40
Nov 13 23:25:33 station kernel: ? _raw_spin_unlock_irq+0x1d/0x30
Nov 13 23:25:33 station kernel: amdgpu_dm_atomic_check+0xf05/0x1080 [amdgpu]
Nov 13 23:25:33 station kernel: drm_atomic_check_only+0x57c/0x7f0 [drm]
Nov 13 23:25:33 station kernel: ? _raw_spin_unlock_irqrestore+0x20/0x40
Nov 13 23:25:33 station kernel: drm_atomic_commit+0x13/0x50 [drm]
Nov 13 23:25:33 station kernel: drm_atomic_connector_commit_dpms+0xda/0x100 [drm]
Nov 13 23:25:33 station kernel: drm_mode_obj_set_property_ioctl+0x196/0x3d0 [drm]
Nov 13 23:25:33 station kernel: ? drm_mode_obj_find_prop_id+0x40/0x40 [drm]
Nov 13 23:25:33 station kernel: drm_ioctl_kernel+0xb2/0x100 [drm]
Nov 13 23:25:33 station kernel: ? do_futex+0x89e/0xcb0
Nov 13 23:25:33 station kernel: drm_ioctl+0x215/0x390 [drm]
Nov 13 23:25:33 station kernel: ? drm_mode_obj_find_prop_id+0x40/0x40 [drm]
Nov 13 23:25:33 station kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Nov 13 23:25:33 station kernel: __x64_sys_ioctl+0x83/0xb0
Nov 13 23:25:33 station kernel: do_syscall_64+0x33/0x40
Nov 13 23:25:33 station kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Nov 13 23:25:33 station kernel: RIP: 0033:0x7f4135883f6b
Nov 13 23:25:33 station kernel: Code: 89 d8 49 8d 3c 1c 48 f7 d8 49 39 c4 72 b5 e8 1c ff ff ff 85 c0 78 ba 4c 89 e0 5b 5d 41 5c c3 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 0>
Nov 13 23:25:33 station kernel: RSP: 002b:00007ffe3fbb6928 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Nov 13 23:25:33 station kernel: RAX: ffffffffffffffda RBX: 00007ffe3fbb6960 RCX: 00007f4135883f6b
Nov 13 23:25:33 station kernel: RDX: 00007ffe3fbb6960 RSI: 00000000c01864ba RDI: 0000000000000009
Nov 13 23:25:33 station kernel: RBP: 00000000c01864ba R08: 0000000000000003 R09: 00000000c0c0c0c0
Nov 13 23:25:33 station kernel: R10: 0000000000000010 R11: 0000000000000246 R12: 00005608b9989b60
Nov 13 23:25:33 station kernel: R13: 0000000000000009 R14: 00005608b99dd650 R15: 00005608b9981c70
Nov 13 23:25:33 station kernel: ---[ end trace 95f0fc47698e1437 ]---
```https://gitlab.freedesktop.org/drm/amd/-/issues/997AMDGPU doesn't detect monitor 90% of the time2023-05-25T04:55:11ZTamara MacadamAMDGPU doesn't detect monitor 90% of the timeHi,
So I recently built a new computer with an AMD Radeon RX 570 graphics card in it. Unfortunately, I have been struggling quite considerably with getting it to work. 90% of the time, when I boot up Linux, the GPU doesn't detect the mo...Hi,
So I recently built a new computer with an AMD Radeon RX 570 graphics card in it. Unfortunately, I have been struggling quite considerably with getting it to work. 90% of the time, when I boot up Linux, the GPU doesn't detect the monitor at all and I have no clue what's going on. The BIOS is always visible, as is the GRUB menu, but after that point it just sorta stops. Fortunately, SSH access is enabled, so I have managed to hack away at the issue.
After troubleshooting on the Arch forums ([link](https://bbs.archlinux.org/viewtopic.php?pid=1878132)), we're pretty sure that this appears to be a kernel issue, unfortunately. When the boot option `amdgpu.dc=0` is enabled, I am always able to boot fine, with no issues whatsoever. When it's not enabled, the issue is extremely prevalent, so we can assume this is a DisplayCore problem. The issue appears to be from at least 4.19 (Debian Stable), but I have confirmed it still occurs on 5.5-rc2.
Attached are two dmesg logs, taken after just having boot up. Both include `drm.debug=0x1e log_buf_len=2M` as options, but one includes `amdgpu.dc=0` and the other does not. I'm still crossing my fingers that this is just me being very stupid with a config problem, but I'm not holding out too much hope for that.
Thank you!
[dmesg_with_amdgpu_boot_option](/uploads/9ab01a6a48c23d538b9d909b5f80c60a/dmesg_with_amdgpu_boot_option)
[dmesg_without_amdgpu_boot_option](/uploads/b7db53c00d37f9da0e46affa114e7487/dmesg_without_amdgpu_boot_option)https://gitlab.freedesktop.org/drm/amd/-/issues/960[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout causes system freeze2023-05-25T04:56:19ZBugzilla Migration User[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout causes system freeze## Submitted by saa..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#112304)](https://bugs.freedesktop.org/show_bug.cgi?id=112304)**
## Description
Created attachment 145975<br>
Xorg.log<br>
<br>
Descri...## Submitted by saa..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#112304)](https://bugs.freedesktop.org/show_bug.cgi?id=112304)**
## Description
Created attachment 145975<br>
Xorg.log<br>
<br>
Description:<br>
<br>
System go to freeze completely whenever during game play e.g Counter Strike global offensive ( Max setting). The hardware power reset is required. usually the system will freeze after 15~20 minutes of play.<br>
<br>
I noticed the frequency of my system freezing when playing games increases after my laptop goes to suspend mode and play after waking up. Also I noticed that the fan will keep spinning even after hardware power off cycling until I have unplug the laptop and remove the battery.<br>
<br>
Here my laptop configuration when running games:<br>
<br>
1. DRI_PRIME =1 is set to all steam games<br>
2. echo high > /sys/class/drm/card1/device/power_dpm_force_performance_level<br>
3. echo performance > /sys/class/drm/card1/device/power_dpm_state<br>
4. Performance governor is set <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Steps to reproduce<br>
<br>
**Attachment 145975**, "Xorg.log": <br>
[Xorg.0.log](/uploads/fd2861c3fd212496065eff76389d13c7/Xorg.0.log)<br>
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=105819https://gitlab.freedesktop.org/drm/amd/-/issues/956Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs2023-05-25T04:57:14ZBugzilla Migration UserBlank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs## Submitted by mor..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#112288)](https://bugs.freedesktop.org/show_bug.cgi?id=112288)**
## Description
Filing bug report here on request by Ubuntu bug team, ...## Submitted by mor..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#112288)](https://bugs.freedesktop.org/show_bug.cgi?id=112288)**
## Description
Filing bug report here on request by Ubuntu bug team, please see discussion on https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1848900<br>
<br>
My problem arose after upgrading Ubuntu 19.04 -> 19.10. The lighted welcome screen displays fine, but when I try to log in I get a black screen and the monitor appears to be frozen (can't switch to virtual terminal either). The machine is running normally and I can log on via ssh.<br>
<br>
Other users in the above mentioned bug on LP have different variations of the same problems, some have problems using the live DVD.https://gitlab.freedesktop.org/drm/amd/-/issues/743Need an option to set HDMI out to Full RGB 4:4:42023-06-06T22:19:07ZBugzilla Migration UserNeed an option to set HDMI out to Full RGB 4:4:4## Submitted by Heiko Lechner
Assigned to **Default DRI bug account**
**[Link to original bug (#110362)](https://bugs.freedesktop.org/show_bug.cgi?id=110362)**
## Description
Hi!<br>
<br>
I have an old tv that only works well with...## Submitted by Heiko Lechner
Assigned to **Default DRI bug account**
**[Link to original bug (#110362)](https://bugs.freedesktop.org/show_bug.cgi?id=110362)**
## Description
Hi!<br>
<br>
I have an old tv that only works well with FullRGB HDMI signals.<br>
If YCbCr is used then the tv interrupts the hdmi link every few minutes and after a new hdmi negotiation the screen turns greenish. So I have to switch to another hdmi input and switch back to force a new negotiation which maybe works- very annoying.<br>
<br>
Running Windows I can switch the output to FullRGB in AMD Radeon Software Adrenalin edition and everything is fine, so I assume that in Linux YCbCr is used by default (too).<br>
<br>
In X.Org log file I find "AMDGPU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4" so it seems to be possible.<br>
<br>
But X.Org config:<br>
<br>
Option "ColorRange""Full"<br>
Option "ColorSpace""RGB"<br>
<br>
Is ignored.https://gitlab.freedesktop.org/drm/amd/-/issues/729[amdgpu] Screen flickering when using a 75Hz monitor paired with an RX 480 GPU2023-05-25T05:07:15ZBugzilla Migration User[amdgpu] Screen flickering when using a 75Hz monitor paired with an RX 480 GPU## Submitted by Maxim Ivanov
Assigned to **Default DRI bug account**
**[Link to original bug (#110199)](https://bugs.freedesktop.org/show_bug.cgi?id=110199)**
## Description
My monitor is LG 24MP59G-P (75Hz, FreeSync) and my GPU i...## Submitted by Maxim Ivanov
Assigned to **Default DRI bug account**
**[Link to original bug (#110199)](https://bugs.freedesktop.org/show_bug.cgi?id=110199)**
## Description
My monitor is LG 24MP59G-P (75Hz, FreeSync) and my GPU is Sapphire Nitro+ RX 480 8GB.<br>
<br>
Basically, whenever there is movement on my screen (oddly though, cursor movement doesn't cause it), it would flicker very badly. <br>
<br>
Here is a video of what I am talking about: https://streamable.com/5eu7p<br>
<br>
Apart from trying different refresh rates, as seen in the video, I have also tried switching kernel versions, switching from DisplayPort to HDMI, changing compositor settings and turning off FreeSync from the monitor OSD, but nothing seems to resolve the bug.<br>
<br>
What works for me as a workaround is changing /sys/class/drm/card0/device/power_dpm_force_performance_level from auto to either low or high. When I do watch -n 1 "/sys/class/drm/card0/device/pp_dpm_mclk" with the performance level on auto, it normally stays on the lowest (300MHz) and when I move a window around, it constantly switches from 300MHz to 2000MHz (the max on my GPU). Apparently, that's what's causing it to behave this way.<br>
<br>
I should emphasize, that I observed the bug in Antergos, Debian 9 Buster (Stretch is good), Manjaro XFCE, Manjaro KDE, Ubuntu 18.10, KUbuntu 18.04 and KUbuntu 18.10. At first I thought it was only related to Arch Linux derivatives, since they all use bleeding-edge packages, but then I noticed, that after switching Debian 9 Stretch's (stable) sources to Buster (testing) and after updating KUbuntu 18.10, the bug appeared in both distros as well.<br>
<br>
Here is a link to a thread I created in the Manjaro forums, where I asked for help: https://forum.manjaro.org/t/manjaro-kde-screen-flickering-cant-seem-to-find-a-solution/78349 - You can find all kinds of different things I tried there, as well as more in-depth system information.https://gitlab.freedesktop.org/drm/amd/-/issues/702deadlock occurs during GPU reset2023-05-25T05:08:14ZBugzilla Migration Userdeadlock occurs during GPU reset## Submitted by Mikhail Gavrilov `@Mikhail`
Assigned to **Default DRI bug account**
**[Link to original bug (#109692)](https://bugs.freedesktop.org/show_bug.cgi?id=109692)**
## Description
Created attachment 143419<br>
dmesg<br>
<...## Submitted by Mikhail Gavrilov `@Mikhail`
Assigned to **Default DRI bug account**
**[Link to original bug (#109692)](https://bugs.freedesktop.org/show_bug.cgi?id=109692)**
## Description
Created attachment 143419<br>
dmesg<br>
<br>
Steps for reproduce:<br>
1. $ git clone git://people.freedesktop.org/~agd5f/linux -b amd-staging-drm-next<br>
2. $ make bzImage && make module<br>
3. # make modules_install && make install<br>
4. Launch "Shadow of the Tomb Raider"<br>
--- Here GPU hung occurs ---<br>
and after few time <br>
--- Here start GPU reset ---<br>
--- Here Deadlock occurs ---<br>
<br>
[ 291.746741] amdgpu 0000:0b:00.0: [gfxhub] no-retry page fault (src_id:0 ring:158 vmid:7 pasid:32774, for process SOTTR.exe pid 5250 thread SOTTR.exe pid 5250)<br>
[ 291.746750] amdgpu 0000:0b:00.0: in page starting at address 0x0000000000002000 from 27<br>
[ 291.746754] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0070113C<br>
[ 297.135183] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out.<br>
[ 302.255032] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out.<br>
[ 302.265813] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=13292, emitted seq=13293<br>
[ 302.265950] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process SOTTR.exe pid 5250 thread SOTTR.exe pid 5250<br>
[ 302.265974] amdgpu 0000:0b:00.0: GPU reset begin!<br>
<br>
[ 302.266337] ======================================================<br>
[ 302.266338] WARNING: possible circular locking dependency detected<br>
[ 302.266340] 5.0.0-rc1-drm-next-kernel+ #1 Tainted: G C <br>
[ 302.266341] ------------------------------------------------------<br>
[ 302.266343] kworker/5:2/871 is trying to acquire lock:<br>
[ 302.266345] 000000000abbb16a (&(&ring->fence_drv.lock)->rlock){-.-.}, at: dma_fence_remove_callback+0x1a/0x60<br>
[ 302.266352] <br>
but task is already holding lock:<br>
[ 302.266353] 000000006e32ba38 (&(&sched->job_list_lock)->rlock){-.-.}, at: drm_sched_stop+0x34/0x140 [gpu_sched]<br>
[ 302.266358] <br>
which lock already depends on the new lock.<br>
<br>
[ 302.266360] <br>
the existing dependency chain (in reverse order) is:<br>
[ 302.266361] <br>
-> #1 (&(&sched->job_list_lock)->rlock){-.-.}:<br>
[ 302.266366] drm_sched_process_job+0x4d/0x180 [gpu_sched]<br>
[ 302.266368] dma_fence_signal+0x111/0x1a0<br>
[ 302.266414] amdgpu_fence_process+0xa3/0x100 [amdgpu]<br>
[ 302.266470] sdma_v4_0_process_trap_irq+0x6e/0xa0 [amdgpu]<br>
[ 302.266523] amdgpu_irq_dispatch+0xc0/0x250 [amdgpu]<br>
[ 302.266576] amdgpu_ih_process+0x84/0xf0 [amdgpu]<br>
[ 302.266628] amdgpu_irq_handler+0x1b/0x50 [amdgpu]<br>
[ 302.266632] __handle_irq_event_percpu+0x3f/0x290<br>
[ 302.266635] handle_irq_event_percpu+0x31/0x80<br>
[ 302.266637] handle_irq_event+0x34/0x51<br>
[ 302.266639] handle_edge_irq+0x7c/0x1a0<br>
[ 302.266643] handle_irq+0xbf/0x100<br>
[ 302.266646] do_IRQ+0x61/0x120<br>
[ 302.266648] ret_from_intr+0x0/0x22<br>
[ 302.266651] cpuidle_enter_state+0xbf/0x470<br>
[ 302.266654] do_idle+0x1ec/0x280<br>
[ 302.266657] cpu_startup_entry+0x19/0x20<br>
[ 302.266660] start_secondary+0x1b3/0x200<br>
[ 302.266663] secondary_startup_64+0xa4/0xb0<br>
[ 302.266664] <br>
-> #0 (&(&ring->fence_drv.lock)->rlock){-.-.}:<br>
[ 302.266668] _raw_spin_lock_irqsave+0x49/0x83<br>
[ 302.266670] dma_fence_remove_callback+0x1a/0x60<br>
[ 302.266673] drm_sched_stop+0x59/0x140 [gpu_sched]<br>
[ 302.266717] amdgpu_device_pre_asic_reset+0x4f/0x240 [amdgpu]<br>
[ 302.266761] amdgpu_device_gpu_recover+0x88/0x7d0 [amdgpu]<br>
[ 302.266822] amdgpu_job_timedout+0x109/0x130 [amdgpu]<br>
[ 302.266827] drm_sched_job_timedout+0x40/0x70 [gpu_sched]<br>
[ 302.266831] process_one_work+0x272/0x5d0<br>
[ 302.266834] worker_thread+0x50/0x3b0<br>
[ 302.266836] kthread+0x108/0x140<br>
[ 302.266839] ret_from_fork+0x27/0x50<br>
[ 302.266840] <br>
other info that might help us debug this:<br>
<br>
[ 302.266841] Possible unsafe locking scenario:<br>
<br>
[ 302.266842] CPU0 CPU1<br>
[ 302.266843] ---- ----<br>
[ 302.266844] lock(&(&sched->job_list_lock)->rlock);<br>
[ 302.266846] lock(&(&ring->fence_drv.lock)->rlock);<br>
[ 302.266847] lock(&(&sched->job_list_lock)->rlock);<br>
[ 302.266849] lock(&(&ring->fence_drv.lock)->rlock);<br>
[ 302.266850] <br>
*** DEADLOCK ***<br>
<br>
[ 302.266852] 5 locks held by kworker/5:2/871:<br>
[ 302.266853] #0: 00000000d133fb6e ((wq_completion)"events"){+.+.}, at: process_one_work+0x1e9/0x5d0<br>
[ 302.266857] #1: 000000008a5c3f7e ((work_completion)(&(&sched->work_tdr)->work)){+.+.}, at: process_one_work+0x1e9/0x5d0<br>
[ 302.266862] #2: 00000000b9b2c76f (&adev->lock_reset){+.+.}, at: amdgpu_device_lock_adev+0x17/0x40 [amdgpu]<br>
[ 302.266908] #3: 00000000ac637728 (&dqm->lock_hidden){+.+.}, at: kgd2kfd_pre_reset+0x30/0x60 [amdgpu]<br>
[ 302.266965] #4: 000000006e32ba38 (&(&sched->job_list_lock)->rlock){-.-.}, at: drm_sched_stop+0x34/0x140 [gpu_sched]<br>
[ 302.266971] <br>
stack backtrace:<br>
[ 302.266975] CPU: 5 PID: 871 Comm: kworker/5:2 Tainted: G C 5.0.0-rc1-drm-next-kernel+ #1<br>
[ 302.266976] Hardware name: System manufacturer System Product Name/ROG STRIX X470-I GAMING, BIOS 1103 11/16/2018<br>
[ 302.266980] Workqueue: events drm_sched_job_timedout [gpu_sched]<br>
[ 302.266982] Call Trace:<br>
[ 302.266987] dump_stack+0x85/0xc0<br>
[ 302.266991] print_circular_bug.isra.0.cold+0x15c/0x195<br>
[ 302.266994] __lock_acquire+0x134c/0x1660<br>
[ 302.266998] ? add_lock_to_list.isra.0+0x67/0xb0<br>
[ 302.267003] lock_acquire+0xa2/0x1b0<br>
[ 302.267006] ? dma_fence_remove_callback+0x1a/0x60<br>
[ 302.267011] _raw_spin_lock_irqsave+0x49/0x83<br>
[ 302.267013] ? dma_fence_remove_callback+0x1a/0x60<br>
[ 302.267016] dma_fence_remove_callback+0x1a/0x60<br>
[ 302.267020] drm_sched_stop+0x59/0x140 [gpu_sched]<br>
[ 302.267065] amdgpu_device_pre_asic_reset+0x4f/0x240 [amdgpu]<br>
[ 302.267110] amdgpu_device_gpu_recover+0x88/0x7d0 [amdgpu]<br>
[ 302.267173] amdgpu_job_timedout+0x109/0x130 [amdgpu]<br>
[ 302.267178] drm_sched_job_timedout+0x40/0x70 [gpu_sched]<br>
[ 302.267183] process_one_work+0x272/0x5d0<br>
[ 302.267188] worker_thread+0x50/0x3b0<br>
[ 302.267191] kthread+0x108/0x140<br>
[ 302.267194] ? process_one_work+0x5d0/0x5d0<br>
[ 302.267196] ? kthread_park+0x90/0x90<br>
[ 302.267199] ret_from_fork+0x27/0x50<br>
[ 302.692194] amdgpu 0000:0b:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)<br>
[ 302.692234] [drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed<br>
[ 302.768931] amdgpu 0000:0b:00.0: GPU BACO reset<br>
[ 303.278874] amdgpu 0000:0b:00.0: GPU reset succeeded, trying to resume<br>
[ 303.279006] [drm] PCIE GART of 512M enabled (table at 0x000000F400900000).<br>
[ 303.279072] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is lost!<br>
[ 303.279234] [drm] PSP is resuming...<br>
[ 303.426601] [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE<br>
[ 303.572227] [drm] UVD and UVD ENC initialized successfully.<br>
[ 303.687727] [drm] VCE initialized successfully.<br>
[ 303.689585] [drm] recover vram bo from shadow start<br>
[ 303.722757] [drm] recover vram bo from shadow done<br>
[ 303.722761] [drm] Skip scheduling IBs!<br>
[ 303.722791] amdgpu 0000:0b:00.0: GPU reset(2) succeeded!<br>
[ 303.722811] [drm] Skip scheduling IBs!<br>
[ 303.722838] [drm] Skip scheduling IBs!<br>
[ 303.722846] [drm] Skip scheduling IBs!<br>
[ 303.722854] [drm] Skip scheduling IBs!<br>
[ 303.722863] [drm] Skip scheduling IBs!<br>
[ 303.722871] [drm] Skip scheduling IBs!<br>
<br>
**Attachment 143419**, "dmesg": <br>
[dmesg2.txt](/uploads/cfdec4fe9a3d2708d64eba229e58aa3e/dmesg2.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/695WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()2020-07-01T15:37:34ZBugzilla Migration UserWARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()## Submitted by Rafał Miłecki
Assigned to **Default DRI bug account**
**[Link to original bug (#109628)](https://bugs.freedesktop.org/show_bug.cgi?id=109628)**
## Description
I use HP EliteBook 745 G5 with Ryzen 5 PRO 2500U and ex...## Submitted by Rafał Miłecki
Assigned to **Default DRI bug account**
**[Link to original bug (#109628)](https://bugs.freedesktop.org/show_bug.cgi?id=109628)**
## Description
I use HP EliteBook 745 G5 with Ryzen 5 PRO 2500U and external monitor BenQ GW2260.<br>
<br>
Today after taking ~10 minutes break amdgpu had some problems with enabling my external monitor back (after putting it in sleep mode or something). It took it about half a minute I think.<br>
<br>
I checked dmesg immediately and found there a WARNING:<br>
[65984.999696] WARNING: CPU: 6 PID: 2081 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high+0x25/0x260 [amdgpu]<br>
<br>
I suspect it may be related to the issue I'm reporting.<br>
<br>
So far I was using kernels 4.19 and 4.20 (for the last 2 months) and never saw it. A day ago I've switched to the kernel 5.0.0-rc6. It may be either:<br>
1. A regression<br>
2. A very rare bug