On 2021-02-17 3:56 p.m., Hans de Goede wrote:
Hi All, Fedora has a (opt-in) system to automatically collect backtraces from software crashing on users systems. This includes collecting kernel backtraces (including once triggered by WARN macros) while looking a the top 10 of the most reported backtrace during the last 2 weeks report from ABRT: https://retrace.fedoraproject.org/faf/problems/ I noticed the following backtrace: https://retrace.fedoraproject.org/faf/problems/13904/ which has been reported 160000 times by Fedora users who have opted-in during the last 14 days.
Given these numbers, the lack of response is puzzling. Adding some DC folks, in case they missed it before.
The ABRT symbol resolution points to amdgpu_dm_backlight_update_status: 1 amdgpu_dm_backlight_update_status amdgpu 0xb4 2 amdgpu_dm_backlight_update_status amdgpu 0xb4 3 amdgpu_dm_backlight_update_status amdgpu 0xb4 4 amdgpu_dm_backlight_update_status amdgpu 0xb4 5 ? amdgpu_dm_backlight_update_status amdgpu 0xb4 6 amdgpu_dm_backlight_update_status amdgpu 0xb4 7 amdgpu_dm_backlight_update_status amdgpu 0xb4 8 drm_sched_job_timedout gpu_sched drivers/gpu/drm/scheduler/sched_main.c 289 But the backtrace from dmesg points to something else: RIP: 0010:dcn10_get_dig_frontend+0x76/0xb0 [amdgpu] Code: 39 44 89 c0 48 83 c4 08 c3 41 b8 05 00 00 00 83 f8 20 74 ed 41 b8 06 00 00 00 83 f8 40 74 e2 41 b8 04 00 00 00 83 f8 10 74 d7 <0f> 0b 41 b8 ff ff ff ff 48 83 c4 08 44 89 c0 c3 45 31 c0 83 f8 01 RSP: 0018:ffffa376c2dffca8 EFLAGS: 00210297 RAX: 0000000000000000 RBX: ffff8ecf6b760000 RCX: 0000000000000008 RDX: 0000000000000000 RSI: 000000000000596f RDI: ffff8ecf6db20000 RBP: ffff8ecf6a187000 R08: 0000000000000000 R09: ffff8ecf6f88fc00 R10: 0000000000000001 R11: 0000000000000006 R12: ffff8ecf727ec200 R13: 0000000000000006 R14: ffff8ecf6f982800 R15: ffff8ecf6e749200 FS: 0000000000000000(0000) GS:ffff8ecf7e9c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb5fb4a8000 CR3: 0000000356446000 CR4: 00000000003506e0 Call Trace: dcn10_init_hw+0x6ed/0x930 [amdgpu] dc_set_power_state+0xf5/0x140 [amdgpu] dm_resume+0x328/0x500 [amdgpu] amdgpu_device_ip_resume_phase2+0x52/0xb0 [amdgpu] ? amdgpu_device_fw_loading+0x9f/0x110 [amdgpu] amdgpu_device_gpu_recover.cold+0x8c1/0xf62 [amdgpu] amdgpu_job_timedout+0x11c/0x140 [amdgpu] drm_sched_job_timedout+0x72/0xf0 [gpu_sched] process_one_work+0x1b4/0x370 There also is this bugzilla about this: https://bugzilla.redhat.com/show_bug.cgi?id=1929746 from today
This one seems to have restricted access.
And a whole bunch of others: https://bugzilla.redhat.com/buglist.cgi?quicksearch=amdgpu_dm_backlight_update_status
https://gitlab.freedesktop.org/drm/amd/-/issues/1337 looks related as well. -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer _______________________________________________ amd-gfx mailing list amd-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/amd-gfx
