All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 214029] [NAVI] Several memory leaks in amdgpu and ttm
Date: Mon, 20 Sep 2021 16:35:10 +0000	[thread overview]
Message-ID: <bug-214029-2300-sidSrNwruP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214029-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=214029

--- Comment #13 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 298897
  --> https://bugzilla.kernel.org/attachment.cgi?id=298897&action=edit
bisect.log

Verified that the issue still exists in latest v5.15-rc2 and v5.14.6 and did a
bisect:

# possible first bad commit: [355b60296143a090039211c5f0e1463f84aab65a] Merge
drm/drm-next into drm-misc-next
# possible first bad commit: [91185d55b32e7e377f15fb46a62b216f8d3038d4] drm:
Remove DRM_KMS_FB_HELPER Kconfig option
# possible first bad commit: [a50e74bec1d17e95275909660c6b43ffe11ebcf0]
drm/zte: Don't select DRM_KMS_FB_HELPER
# possible first bad commit: [13b29cc3a722c2c0bc9ab9f72f9047d55d08a2f9]
drm/mxsfb: Don't select DRM_KMS_FB_HELPER
# possible first bad commit: [5dbf2fc587cb79cb366bd6e79ac6b52269d64fc5]
drm/vmwgfx: Make console emulation depend on DRM_FBDEV_EMULATION
# possible first bad commit: [c777dc9e793342ecdfc95045d2127a3ea32791a0]
drm/ttm: move the page_alignment into the BO v2
# possible first bad commit: [65747ded86b4608387d5618d14f0fe9dc88e17ea]
drm/ttm: minor range manager coding style clean ups
# possible first bad commit: [d02117f8efaa5fbc37437df1ae955a147a2a424a]
drm/ttm: remove special handling for non GEM drivers
# possible first bad commit: [13ea9aa1e7d891e950230e82f1dd2c84e5debcff]
drm/ttm: fix error handling if no BO can be swapped out v4
# possible first bad commit: [ae053fa234f42b4abc582372af7410ad0e3e1dad] drm:
bridge: adv7511: Support I2S IEC958 encoded PCM format

I had to skip a few commits as kmemleak did not properly work for some commits
due to:
[...]
[    0.706509] kmemleak: Cannot insert 0xffff953c1ba02f40 into the object
search tree (overlaps existing)
[    0.706514] CPU: 0 PID: 6 Comm: kthreadd Not tainted 5.12.0-rc3-bdver2+ #24
[    0.706518] Hardware name: Gigabyte Technology Co., Ltd. To be filled by
O.E.M./970-GAMING, BIOS F2 04/06/2016
[    0.706521] Call Trace:
[    0.706524]  dump_stack+0x69/0x8e
[    0.706531]  create_object.isra.0.cold+0x3b/0x5d
[    0.706536]  ? kthread+0x35/0x130
[    0.706537]  kmem_cache_alloc+0x15a/0x4a0
[    0.706537]  ? rescuer_thread+0x380/0x380
[    0.706537]  kthread+0x35/0x130
[    0.706537]  ? __kthread_bind_mask+0x60/0x60
[    0.706537]  ret_from_fork+0x22/0x30
[    0.706537] kmemleak: Kernel memory leak detector disabled
[    0.706537] kmemleak: Object 0xffff953c1ba00000 (size 2097152):
[    0.706537] kmemleak:   comm "swapper", pid 0, jiffies 4294877296
[    0.706537] kmemleak:   min_count = 0
[    0.706537] kmemleak:   count = 0
[    0.706537] kmemleak:   flags = 0x1
[    0.706537] kmemleak:   checksum = 0
[    0.706537] kmemleak:   backtrace:
[    0.706537]      memblock_alloc_internal+0xb8/0x152
[    0.706537]      memblock_alloc_try_nid+0xa0/0xf3
[    0.706537]      kfence_alloc_pool+0x59/0xbf
[    0.706537]      start_kernel+0x2b3/0x61a
[    0.706537]      secondary_startup_64_no_verify+0xb0/0xbb

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-09-20 16:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 18:34 [Bug 214029] New: [NAVI] Several memory leaks in amdgpu and ttm bugzilla-daemon
2021-08-10 18:35 ` [Bug 214029] " bugzilla-daemon
2021-08-10 18:36 ` bugzilla-daemon
2021-08-30 13:45 ` bugzilla-daemon
2021-08-30 13:45 ` bugzilla-daemon
2021-08-30 13:49 ` bugzilla-daemon
2021-08-31  9:39 ` bugzilla-daemon
2021-08-31 10:20 ` bugzilla-daemon
2021-09-13 19:57 ` bugzilla-daemon
2021-09-13 19:58 ` bugzilla-daemon
2021-09-13 20:00 ` bugzilla-daemon
2021-09-20 16:29 ` bugzilla-daemon
2021-09-20 16:30 ` bugzilla-daemon
2021-09-20 16:35 ` bugzilla-daemon [this message]
2021-09-20 16:35 ` [Bug 214029] [bisected] " bugzilla-daemon
2021-09-22 22:05 ` bugzilla-daemon
2021-09-22 22:05 ` [Bug 214029] [bisected] [amdgpu] " bugzilla-daemon
2021-09-28 15:21 ` bugzilla-daemon
2021-09-28 15:25 ` bugzilla-daemon
2021-10-15 22:53 ` bugzilla-daemon
2021-10-15 22:55 ` bugzilla-daemon
2021-10-20 17:46 ` bugzilla-daemon
2021-10-21  7:37 ` bugzilla-daemon
2021-10-21  8:44 ` bugzilla-daemon
2021-10-21 12:39 ` bugzilla-daemon
2021-11-03  9:45 ` bugzilla-daemon
2021-11-03 15:07 ` bugzilla-daemon
2021-11-03 17:54 ` bugzilla-daemon
2021-11-04  7:16 ` bugzilla-daemon
2021-11-04  7:44 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-214029-2300-sidSrNwruP@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.