Bug 1985880 - [abrt] amdgpu_bo_unref: WARNING: CPU: 9 PID: 1 at drivers/gpu/drm/ttm/ttm_bo.c:437 ttm_bo_release+0x2c6/0x310 [ttm] [amdgpu]
Summary: [abrt] amdgpu_bo_unref: WARNING: CPU: 9 PID: 1 at drivers/gpu/drm/ttm/ttm_bo....
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
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:ef56025a25c5892f9178e973d5f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-26 07:15 UTC by max miliano
Modified: 2022-06-07 22:42 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 22:42:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (87.43 KB, text/plain)
2021-07-26 07:15 UTC, max miliano
no flags Details

Description max miliano 2021-07-26 07:15:12 UTC
Additional info:
reporter:       libreport-2.15.2
WARNING: CPU: 9 PID: 1 at drivers/gpu/drm/ttm/ttm_bo.c:437 ttm_bo_release+0x2c6/0x310 [ttm]
Modules linked in: snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nf_conntrack_tftp bridge stp llc nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast 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 rfkill nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter intel_rapl_msr intel_rapl_common binfmt_misc sunrpc snd_hda_codec_realtek snd_hda_codec_generic ppdev ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec edac_mce_amd snd_usb_audio snd_hda_core snd_usbmidi_lib kvm_amd snd_hwdep snd_rawmidi snd_seq uvcvideo snd_seq_device vfat fat kvm snd_pcm videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 irqbypass videobuf2_common snd_timer
 rapl wmi_bmof pcspkr k10temp i2c_piix4 videodev snd soundcore mc xpad joydev parport_pc ff_memless parport gpio_amdpt gpio_generic zram ip_tables hid_uclogic amdgpu drm_ttm_helper ttm iommu_v2 gpu_sched i2c_algo_bit drm_kms_helper cec crct10dif_pclmul crc32_pclmul crc32c_intel drm ghash_clmulni_intel ccp sp5100_tco r8169 wmi fuse
CPU: 9 PID: 1 Comm: systemd Not tainted 5.13.4-200.fc34.x86_64 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./A320M-HD, BIOS P5.40 07/09/2019
RIP: 0010:ttm_bo_release+0x2c6/0x310 [ttm]
Code: e8 ff 07 45 dc e9 c5 fd ff ff 49 8b 7e 98 b9 30 75 00 00 31 d2 be 01 00 00 00 e8 35 29 45 dc 49 8b 46 e8 eb 9e 48 89 e8 eb 99 <0f> 0b 41 c7 86 84 00 00 00 00 00 00 00 49 8d 76 08 31 d2 4c 89 ef
RSP: 0018:ffffb8ec0004fd70 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000246 RDI: ffff9c4591905ac0
RBP: ffff9c45919052b0 R08: ffff9c45eeb9b0a8 R09: ffff9c45caec8eb8
R10: ffff9c458e1a9ce8 R11: 0000000000000001 R12: ffff9c45d24c4620
R13: ffff9c45d24c4458 R14: ffff9c45d24c45b8 R15: ffff9c45cca1cf00
FS:  00007ff59e80e340(0000) GS:ffff9c488ec40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000557175bde170 CR3: 00000001041f2000 CR4: 00000000003506e0
Call Trace:
 amdgpu_bo_unref+0x1a/0x30 [amdgpu]
 amdgpu_gem_object_free+0x20/0x30 [amdgpu]
 drm_gem_object_release_handle+0x6b/0x80 [drm]
 ? drm_gem_object_handle_put_unlocked+0xd0/0xd0 [drm]
 idr_for_each+0x4e/0xc0
 drm_gem_release+0x1c/0x30 [drm]
 drm_file_free.part.0+0x1e3/0x250 [drm]
 drm_release+0x65/0x110 [drm]
 __fput+0x94/0x240
 task_work_run+0x65/0xa0
 exit_to_user_mode_prepare+0x237/0x240
 syscall_exit_to_user_mode+0x18/0x40
 do_syscall_64+0x4d/0x80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7ff59f48d9b7
Code: 00 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 33 fc ff ff
RSP: 002b:00007ffedb18a598 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 00007ff59e80e0f8 RCX: 00007ff59f48d9b7
RDX: 0000557175bde160 RSI: 0000557175845010 RDI: 0000000000000086
RBP: 0000000000000086 R08: 0000557175bdca40 R09: bb322438fdb365d2
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000557175730300 R14: 00005571756eb0f9 R15: 0000557175be17d0

Comment 1 max miliano 2021-07-26 07:15:19 UTC
Created attachment 1805768 [details]
File: dmesg

Comment 2 Ben Cotton 2022-05-12 15:49:59 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-07 22:42:30 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

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.