dri-devel Archive on 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, 13 Sep 2021 19:57:12 +0000	[thread overview]
Message-ID: <bug-214029-2300-T1ines93YG@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 #8 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 298783
  --> https://bugzilla.kernel.org/attachment.cgi?id=298783&action=edit
output of kmemleak (kernel 5.15-rc1, AMD FX-8370)

Seems unchanged in kernel 5.15-rc1.

 # cat /sys/kernel/debug/kmemleak
unreferenced object 0xffff88810830b400 (size 1024):
  comm "lxdm-greeter-gt", pid 624, jiffies 4294887923 (age 1566.300s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 b4 30 08 81 88 ff ff  ..........0.....
    08 b4 30 08 81 88 ff ff 30 f5 10 9b 81 88 ff ff  ..0.....0.......
  backtrace:
    [<ffffffffc1352a88>] amdgpu_job_alloc+0x38/0x2f0 [amdgpu]
    [<ffffffffc1352d67>] amdgpu_job_alloc_with_ib+0x27/0xf0 [amdgpu]
    [<ffffffffc0f37323>] amdgpu_copy_buffer+0x1d3/0x700 [amdgpu]
    [<ffffffffc0f37e4a>] amdgpu_ttm_copy_mem_to_mem+0x5fa/0xf00 [amdgpu]
    [<ffffffffc0f39586>] amdgpu_bo_move+0x356/0x2050 [amdgpu]
    [<ffffffffc06fa897>] ttm_bo_handle_move_mem+0x1c7/0x620 [ttm]
    [<ffffffffc06fe403>] ttm_bo_validate+0x2b3/0x3b0 [ttm]
    [<ffffffffc0f3fa84>] amdgpu_bo_fault_reserve_notify+0x2a4/0x640 [amdgpu]
    [<ffffffffc0f4f903>] amdgpu_gem_fault+0x123/0x2d0 [amdgpu]
    [<ffffffff97568963>] __do_fault+0xf3/0x3e0
    [<ffffffff9757a5f5>] __handle_mm_fault+0x16e5/0x2aa0
    [<ffffffff9757bada>] handle_mm_fault+0x12a/0x490
    [<ffffffff9708e449>] do_user_addr_fault+0x259/0xb70
    [<ffffffff988137a5>] exc_page_fault+0x55/0xb0
    [<ffffffff98a00acb>] asm_exc_page_fault+0x1b/0x20
unreferenced object 0xffff8881fe3ca4c0 (size 216):
  comm "lxdm-greeter-gt", pid 624, jiffies 4294887923 (age 1566.300s)
  hex dump (first 32 bytes):
    50 a5 3c fe 81 88 ff ff 20 ab 74 c0 ff ff ff ff  P.<..... .t.....
    e0 ea 04 ac 08 00 00 00 50 fd c5 08 00 c9 ff ff  ........P.......
  backtrace:
    [<ffffffffc07471df>] drm_sched_fence_create+0x1f/0x1d0 [gpu_sched]
    [<ffffffffc07424de>] drm_sched_job_init+0x10e/0x240 [gpu_sched]
    [<ffffffffc13538a5>] amdgpu_job_submit+0x25/0x100 [amdgpu]
    [<ffffffffc0f375ee>] amdgpu_copy_buffer+0x49e/0x700 [amdgpu]
    [<ffffffffc0f37e4a>] amdgpu_ttm_copy_mem_to_mem+0x5fa/0xf00 [amdgpu]
    [<ffffffffc0f39586>] amdgpu_bo_move+0x356/0x2050 [amdgpu]
    [<ffffffffc06fa897>] ttm_bo_handle_move_mem+0x1c7/0x620 [ttm]
    [<ffffffffc06fe403>] ttm_bo_validate+0x2b3/0x3b0 [ttm]
    [<ffffffffc0f3fa84>] amdgpu_bo_fault_reserve_notify+0x2a4/0x640 [amdgpu]
    [<ffffffffc0f4f903>] amdgpu_gem_fault+0x123/0x2d0 [amdgpu]
    [<ffffffff97568963>] __do_fault+0xf3/0x3e0
    [<ffffffff9757a5f5>] __handle_mm_fault+0x16e5/0x2aa0
    [<ffffffff9757bada>] handle_mm_fault+0x12a/0x490
    [<ffffffff9708e449>] do_user_addr_fault+0x259/0xb70
    [<ffffffff988137a5>] exc_page_fault+0x55/0xb0
    [<ffffffff98a00acb>] asm_exc_page_fault+0x1b/0x20
unreferenced object 0xffff8881cdbb7000 (size 1024):
  comm "mate-session-ch", pid 722, jiffies 4294890054 (age 1559.204s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 70 bb cd 81 88 ff ff  .........p......
    08 70 bb cd 81 88 ff ff 30 f5 10 9b 81 88 ff ff  .p......0.......
  backtrace:
    [<ffffffffc1352a88>] amdgpu_job_alloc+0x38/0x2f0 [amdgpu]
    [<ffffffffc1352d67>] amdgpu_job_alloc_with_ib+0x27/0xf0 [amdgpu]
    [<ffffffffc0f37323>] amdgpu_copy_buffer+0x1d3/0x700 [amdgpu]
    [<ffffffffc0f37e4a>] amdgpu_ttm_copy_mem_to_mem+0x5fa/0xf00 [amdgpu]
    [<ffffffffc0f39586>] amdgpu_bo_move+0x356/0x2050 [amdgpu]
    [<ffffffffc06fa897>] ttm_bo_handle_move_mem+0x1c7/0x620 [ttm]
    [<ffffffffc06fe403>] ttm_bo_validate+0x2b3/0x3b0 [ttm]
    [<ffffffffc0f3fa84>] amdgpu_bo_fault_reserve_notify+0x2a4/0x640 [amdgpu]
    [<ffffffffc0f4f903>] amdgpu_gem_fault+0x123/0x2d0 [amdgpu]
    [<ffffffff97568963>] __do_fault+0xf3/0x3e0
    [<ffffffff9757a5f5>] __handle_mm_fault+0x16e5/0x2aa0
    [<ffffffff9757bada>] handle_mm_fault+0x12a/0x490
    [<ffffffff9708e449>] do_user_addr_fault+0x259/0xb70
    [<ffffffff988137a5>] exc_page_fault+0x55/0xb0
    [<ffffffff98a00acb>] asm_exc_page_fault+0x1b/0x20
[...]

-- 
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-13 19:57 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 [this message]
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
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-T1ines93YG@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox