Bug 1911727 - [abrt] kernel_queue_uninit: BUG: kernel NULL pointer dereference, address: 0000000000000000 [amdgpu]
Summary: [abrt] kernel_queue_uninit: BUG: kernel NULL pointer dereference, address: 00...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:736505cca14db2c28c1d3a3ae18...
: 1962192 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-30 20:59 UTC by Adam Batkin
Modified: 2021-11-30 18:48 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 18:48:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (107.17 KB, text/plain)
2020-12-30 21:00 UTC, Adam Batkin
no flags Details

Description Adam Batkin 2020-12-30 20:59:57 UTC
Description of problem:
No idea what happened - walked away for a bit and came back to an unresponsive system.

Additional info:
reporter:       libreport-2.14.0
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 0 P4D 0 
Oops: 0010 [#1] SMP NOPTI
CPU: 10 PID: 9600 Comm: kworker/10:1 Not tainted 5.9.16-200.fc33.x86_64 #1
Hardware name: Micro-Star International Co., Ltd. MS-7C91/MPG B550 GAMING EDGE WIFI (MS-7C91), BIOS 1.53 12/24/2020
Workqueue: events drm_sched_job_timedout [gpu_sched]
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffa538c5f07d50 EFLAGS: 00010292
RAX: 0000000000000000 RBX: ffff9447b785a800 RCX: 0000000080800079
RDX: ffffce959a669780 RSI: ffffce959a6697c0 RDI: ffffffffc0bbf710
RBP: ffff9447b919d800 R08: 0000000000000001 R09: 0000000000000000
R10: ffffce959a6697c0 R11: 0000000000000000 R12: ffff9447b785a8d0
R13: ffff9447b93a0000 R14: ffff9447c947d000 R15: ffff9447c947d0b0
FS:  0000000000000000(0000) GS:ffff9447cec80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000057b77e000 CR4: 0000000000750ee0
PKRU: 55555554
Call Trace:
 kernel_queue_uninit+0x36/0xf0 [amdgpu]
 stop_cpsch+0xa2/0xc0 [amdgpu]
 kgd2kfd_suspend.part.0+0x2f/0x40 [amdgpu]
 kgd2kfd_pre_reset+0x35/0x50 [amdgpu]
 amdgpu_device_gpu_recover.cold+0x1ef/0xf62 [amdgpu]
 ? amdgpu_device_ip_check_soft_reset+0x26/0xa0 [amdgpu]
 amdgpu_job_timedout+0x11c/0x140 [amdgpu]
 drm_sched_job_timedout+0x72/0xf0 [gpu_sched]
 process_one_work+0x1b4/0x370
 worker_thread+0x53/0x3e0
 ? process_one_work+0x370/0x370
 kthread+0x11b/0x140
 ? __kthread_bind_mask+0x60/0x60
 ret_from_fork+0x22/0x30
Modules linked in: rfcomm nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter cmac bnep snd_hda_codec_realtek snd_hda_codec_generic sunrpc iwlmvm ledtrig_audio snd_hda_codec_hdmi snd_hda_intel vfat snd_intel_dspcfg edac_mce_amd mac80211 fat snd_hda_codec libarc4 snd_hda_core snd_hwdep iwlwifi kvm snd_seq btusb btrtl btbcm snd_seq_device btintel sp5100_tco bluetooth irqbypass cfg80211 wmi_bmof pcspkr k10temp snd_pcm i2c_piix4 joydev snd_timer snd ecdh_generic ecc soundcore rfkill acpi_cpufreq gpio_amdpt gpio_generic zram ip_tables hid_microsoft hid_steam ff_memless amdgpu iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper cec drm crct10dif_pclmul crc32_pclmul crc32c_intel nvme
 ccp ghash_clmulni_intel r8169 nvme_core wmi pinctrl_amd fuse
CR2: 0000000000000000

Comment 1 Adam Batkin 2020-12-30 21:00:00 UTC
Created attachment 1743332 [details]
File: dmesg

Comment 2 Adam Batkin 2021-01-04 18:24:50 UTC
Description of problem:
No idea what happened. Walked away and when I came back, system was unresponsive (monitor in powersave, numlock/capslock unresponseive, but ctrl+alt+sysrq+s appears to work since I see messages in the journal about that)

Version-Release number of selected component:
kernel-core-5.9.16-200.fc33

Additional info:
reporter:       libreport-2.14.0
cmdline:        BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.9.16-200.fc33.x86_64 root=UUID=dba50f9f-109e-4c68-b4e8-94ea56b849e4 ro rootflags=subvol=root rhgb quiet
crash_function: kernel_queue_uninit
kernel:         5.9.16-200.fc33.x86_64
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 0 P4D 0 
Oops: 0010 [#1] SMP NOPTI
CPU: 11 PID: 6744 Comm: kworker/11:2 Not tainted 5.9.16-200.fc33.x86_64 #1
Hardware name: Micro-Star International Co., Ltd. MS-7C91/MPG B550 GAMING EDGE WIFI (MS-7C91), BIOS 1.53 12/24/2020
Workqueue: events drm_sched_job_timedout [gpu_sched]
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffaa0bc5937d50 EFLAGS: 00010212
RAX: 0000000000000000 RBX: ffff98bb36d70400 RCX: 0000000080800077
RDX: ffffd29d185b9680 RSI: ffffd29d185b96c0 RDI: ffffffffc09be710
RBP: ffff98bb3d35c0c0 R08: 0000000000000001 R09: 0000000000000000
R10: ffffd29d185b96c0 R11: 0000000000000000 R12: ffff98bb36d704d0
R13: ffff98bb382a0000 R14: ffff98bb49969000 R15: ffff98bb499690b0
FS:  0000000000000000(0000) GS:ffff98bb4ecc0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000007b1e28000 CR4: 0000000000750ee0
PKRU: 55555554
Call Trace:
 kernel_queue_uninit+0x36/0xf0 [amdgpu]
 stop_cpsch+0xa2/0xc0 [amdgpu]
 kgd2kfd_suspend.part.0+0x2f/0x40 [amdgpu]
 kgd2kfd_pre_reset+0x35/0x50 [amdgpu]
 amdgpu_device_gpu_recover.cold+0x1ef/0xf62 [amdgpu]
 ? amdgpu_device_ip_check_soft_reset+0x26/0xa0 [amdgpu]
 amdgpu_job_timedout+0x11c/0x140 [amdgpu]
 drm_sched_job_timedout+0x72/0xf0 [gpu_sched]
 process_one_work+0x1b4/0x370
 worker_thread+0x53/0x3e0
 ? process_one_work+0x370/0x370
 kthread+0x11b/0x140
 ? __kthread_bind_mask+0x60/0x60
 ret_from_fork+0x22/0x30
Modules linked in: snd_seq_dummy snd_hrtimer rfcomm uinput md4 nls_utf8 cifs dns_resolver fscache libdes nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter cmac bnep sunrpc snd_hda_codec_realtek snd_hda_codec_generic iwlmvm ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg vfat squashfs edac_mce_amd mac80211 fat snd_hda_codec snd_hda_core btusb snd_hwdep btrtl loop snd_seq btbcm libarc4 snd_seq_device btintel iwlwifi snd_pcm bluetooth kvm snd_timer sp5100_tco irqbypass cfg80211 pcspkr wmi_bmof k10temp ecdh_generic i2c_piix4 ecc snd joydev soundcore rfkill gpio_amdpt acpi_cpufreq gpio_generic zram ip_tables hid_microsoft ff_memless amdgpu iommu_v2 gpu_sched
 i2c_algo_bit ttm drm_kms_helper cec drm crct10dif_pclmul crc32_pclmul nvme crc32c_intel ghash_clmulni_intel ccp r8169 nvme_core wmi pinctrl_amd fuse
CR2: 0000000000000000

Comment 3 ochal 2021-05-19 13:37:17 UTC
*** Bug 1962192 has been marked as a duplicate of this bug. ***

Comment 4 Ben Cotton 2021-11-04 13:59:32 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 5 Ben Cotton 2021-11-04 14:28:48 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 6 Ben Cotton 2021-11-04 15:26:31 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 7 Ben Cotton 2021-11-30 18:48:45 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.


Note You need to log in before you can comment on or make changes to this bug.