Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Begin happens every boot after kernel upgrade to 5.7.0-0.rc0.git6.1.fc33.x86_64 Additional info: reporter: libreport-2.12.0 BUG: kernel NULL pointer dereference, address: 0000000000000026 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 5 PID: 667 Comm: uvd_enc_1.1 Not tainted 5.7.0-0.rc0.git6.1.2.fc33.x86_64 #1 Hardware name: System manufacturer System Product Name/ROG STRIX X570-I GAMING, BIOS 1405 11/19/2019 RIP: 0010:__kthread_should_park+0x5/0x30 Code: 00 e9 fe fe ff ff e8 ca 3a 08 00 e9 49 fe ff ff 48 89 df e8 dd 38 08 00 84 c0 0f 84 6a ff ff ff e9 a6 fe ff ff 0f 1f 44 00 00 <f6> 47 26 20 74 12 48 8b 87 88 09 00 00 48 8b 00 48 c1 e8 02 83 e0 RSP: 0018:ffffad8141723e50 EFLAGS: 00010246 RAX: 7fffffffffffffff RBX: ffff8a8d1d116ed8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000 RBP: ffff8a8d28c11300 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff8a8d1d152e40 R13: ffff8a8d1d117280 R14: ffff8a8d1d116ed8 R15: ffff8a8d1ca68000 FS: 0000000000000000(0000) GS:ffff8a8d3aa00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000026 CR3: 00000007e3dc6000 CR4: 00000000003406e0 Call Trace: drm_sched_get_cleanup_job+0x42/0x130 [gpu_sched] drm_sched_main+0x6f/0x530 [gpu_sched] ? lockdep_hardirqs_on+0x11e/0x1b0 ? drm_sched_get_cleanup_job+0x130/0x130 [gpu_sched] kthread+0x131/0x150 ? __kthread_bind_mask+0x60/0x60 ret_from_fork+0x27/0x50 Modules linked in: fjes(-) amdgpu(+) amd_iommu_v2 gpu_sched ttm drm_kms_helper drm crc32c_intel igb nvme nvme_core dca i2c_algo_bit wmi pinctrl_amd br_netfilter bridge stp llc fuse CR2: 0000000000000026 Potential duplicate: bug 1813629
Created attachment 1677841 [details] File: dmesg
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. NOTE: This is an automated mass update.