Bug 1769281

Summary: WARNING: CPU: 3 PID: 380 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1452 dcn_bw_updat e_from_pplib.cold+0x73/0x9c [amdgpu]
Product: [Fedora] Fedora Reporter: Than Ngo <than>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved
Target Milestone: ---Flags: than: needinfo?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 17:00:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Than Ngo 2019-11-06 10:26:18 UTC
1. Please describe the problem:
on my  Gigabyte Technology Co., Ltd. B450M S2H/B450M S2H, BIOS F42f 10/18/2019 with AMD Ryzen 3 3200G with Radeon Vega Graphics with kernel-5.3.8-300.fc31.x86_64 the warning below is always shown.

[    5.310948] [drm] PSP loading VCN firmware
[    5.331610] [drm] reserve 0x400000 from 0xf400c00000 for PSP TMR
[    5.421229] [drm] DM_PPLIB: values for F clock
[    5.421230] [drm] DM_PPLIB:   0 in kHz, 3099 in mV
[    5.421231] [drm] DM_PPLIB:   0 in kHz, 3099 in mV
[    5.421231] [drm] DM_PPLIB:   0 in kHz, 3099 in mV
[    5.421231] [drm] DM_PPLIB:   1600000 in kHz, 4399 in mV
[    5.421232] ------------[ cut here ]------------
[    5.421332] WARNING: CPU: 3 PID: 380 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1452 dcn_bw_update_from_pplib.cold+0x73/0x9c [amdgpu]
[    5.421333] Modules linked in: amdgpu(+) amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper nvme drm crc32c_intel nvme_core r8169 wmi video pinctrl_amd fuse
[    5.421339] CPU: 3 PID: 380 Comm: systemd-udevd Not tainted 5.3.8-300.fc31.x86_64 #1
[    5.421340] Hardware name: Gigabyte Technology Co., Ltd. B450M S2H/B450M S2H, BIOS F42f 10/18/2019
[    5.421421] RIP: 0010:dcn_bw_update_from_pplib.cold+0x73/0x9c [amdgpu]
[    5.421423] Code: 48 8b 93 60 03 00 00 db 42 78 83 f9 02 77 37 b8 02 00 00 00 8d 71 ff e9 ba fd f3 ff 48 c7 c7 e8 0f 60 c0 31 c0 e8 3b 53 c0 cc <0f> 0b e9 34 fe f3 ff 48 c7 c7 e8 0f 60 c0 31 c0 e8 26 53 c0 cc 0f
[    5.421424] RSP: 0018:ffffb94ec04af618 EFLAGS: 00010246
[    5.421425] RAX: 0000000000000024 RBX: ffff9b39efe40000 RCX: 0000000000000006
[    5.421425] RDX: 0000000000000000 RSI: 0000000000000086 RDI: ffff9b3a006d7900
[    5.421426] RBP: ffff9b39f283be00 R08: 0000000000000001 R09: 00000000000003c7
[    5.421426] R10: 0000000000014424 R11: 0000000000000003 R12: ffffb94ec04af6b8
[    5.421427] R13: 0000000000000001 R14: 000000000000000a R15: ffffb94ec04af848
[    5.421428] FS:  00007f84f7a65940(0000) GS:ffff9b3a006c0000(0000) knlGS:0000000000000000
[    5.421429] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    5.421429] CR2: 00007fa8b3a9e000 CR3: 00000007f4026000 CR4: 00000000003406e0
[    5.421430] Call Trace:
[    5.421516]  dcn10_create_resource_pool+0x997/0xa40 [amdgpu]
[    5.421520]  ? _cond_resched+0x15/0x30
[    5.421522]  ? kmem_cache_alloc_trace+0x162/0x220
[    5.421603]  ? firmware_parser_create+0x17e/0x5f0 [amdgpu]
[    5.421681]  dc_create_resource_pool+0x1b2/0x1d0 [amdgpu]
[    5.421763]  ? dal_gpio_service_create+0x95/0xe0 [amdgpu]
[    5.421841]  dc_create+0x233/0x660 [amdgpu]
[    5.421844]  ? try_to_del_timer_sync+0x4f/0x80
[    5.421917]  ? amdgpu_cgs_create_device+0x23/0x50 [amdgpu]
[    5.421996]  amdgpu_dm_init+0x130/0x1b0 [amdgpu]
[    5.421999]  ? apic_timer_interrupt+0xa/0x20
[    5.422077]  dm_hw_init+0xe/0x20 [amdgpu]
[    5.422156]  amdgpu_device_init.cold+0x1508/0x173e [amdgpu]
[    5.422215]  amdgpu_driver_load_kms+0x58/0x1c0 [amdgpu]
[    5.422225]  drm_dev_register+0x111/0x150 [drm]
[    5.422283]  amdgpu_pci_probe+0xee/0x150 [amdgpu]
[    5.422285]  ? __pm_runtime_resume+0x58/0x80
[    5.422287]  local_pci_probe+0x42/0x80
[    5.422289]  pci_device_probe+0x107/0x1a0
[    5.422291]  really_probe+0xf0/0x380
[    5.422292]  driver_probe_device+0x59/0xd0
[    5.422293]  device_driver_attach+0x53/0x60
[    5.422295]  __driver_attach+0x8a/0x150
[    5.422296]  ? device_driver_attach+0x60/0x60
[    5.422297]  bus_for_each_dev+0x78/0xc0
[    5.422299]  bus_add_driver+0x14a/0x1e0
[    5.422300]  driver_register+0x6c/0xb0
[    5.422301]  ? 0xffffffffc0782000
[    5.422303]  do_one_initcall+0x46/0x1f4
[    5.422305]  ? _cond_resched+0x15/0x30
[    5.422306]  ? kmem_cache_alloc_trace+0x162/0x220
[    5.422307]  ? do_init_module+0x23/0x230
[    5.422308]  do_init_module+0x5c/0x230
[    5.422309]  load_module+0x27b1/0x2990
[    5.422312]  ? __do_sys_init_module+0x16e/0x1a0
[    5.422313]  ? _cond_resched+0x15/0x30
[    5.422313]  __do_sys_init_module+0x16e/0x1a0
[    5.422315]  do_syscall_64+0x5f/0x1a0
[    5.422317]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    5.422318] RIP: 0033:0x7f84f8abb09e
[    5.422320] Code: 48 8b 0d ed fd 0b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ba fd 0b 00 f7 d8 64 89 01 48
[    5.422320] RSP: 002b:00007ffcddec7b78 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[    5.422322] RAX: ffffffffffffffda RBX: 000055d743bee860 RCX: 00007f84f8abb09e
[    5.422322] RDX: 000055d743bec3e0 RSI: 0000000000843d06 RDI: 000055d7444a88b0
[    5.422323] RBP: 000055d7444a88b0 R08: 0000000000000006 R09: 00007ffcddec7726
[    5.422323] R10: 0000000000000007 R11: 0000000000000246 R12: 000055d743bec3e0
[    5.422324] R13: 0000000000000005 R14: 000055d743befae0 R15: 000055d743bee860
[    5.422325] ---[ end trace d280b2cb69d75546 ]---

Comment 1 Than Ngo 2019-11-06 10:27:30 UTC
similar issue is reported on https://bugs.freedesktop.org/show_bug.cgi?id=107296

Comment 2 Than Ngo 2020-02-05 11:30:10 UTC
The following upstream patches resolve the reported issue.

https://patchwork.freedesktop.org/patch/351172/
https://patchwork.freedesktop.org/patch/351173/
https://patchwork.freedesktop.org/patch/351174/

I tested the patches and confirmed that the patches are working as expected

Could you please include these patches in the next kernel build?

Thanks!

Comment 3 Ben Cotton 2020-11-03 15:45:09 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2020-11-24 17:00:14 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.