dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 112302] [kernel 5.4-rc7][amdgpu] kmemleak reports various leaks
Date: Sat, 16 Nov 2019 11:26:57 +0000	[thread overview]
Message-ID: <bug-112302-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2823 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=112302

            Bug ID: 112302
           Summary: [kernel 5.4-rc7][amdgpu] kmemleak reports various
                    leaks
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: All
            Status: NEW
          Severity: normal
          Priority: not set
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: erhard_f@mailbox.org

Created attachment 145972
  --> https://bugs.freedesktop.org/attachment.cgi?id=145972&action=edit
cat /sys/kernel/debug/kmemleak

[ 1306.389652] kmemleak: 28 new suspected memory leaks (see
/sys/kernel/debug/kmemleak)

Running X I get various kmemleak dumps for amdgpu:
[...]
unreferenced object 0xffffa2501f3374c0 (size 208):
  comm "Xorg", pid 694, jiffies 4294885609 (age 1870.427s)
  hex dump (first 32 bytes):
    50 75 33 1f 50 a2 ff ff a0 41 47 c0 ff ff ff ff  Pu3.P....AG.....
    b6 d7 06 a0 06 00 00 00 48 fe aa 8c b5 b1 ff ff  ........H.......
  backtrace:
    [<00000000502b8475>] drm_sched_fence_create+0x1d/0xc0 [gpu_sched]
    [<0000000067f89939>] drm_sched_job_init+0x5b/0xa0 [gpu_sched]
    [<0000000097e803db>] amdgpu_job_submit+0x1e/0x90 [amdgpu]
    [<000000008af66624>] amdgpu_copy_buffer+0x1ab/0x290 [amdgpu]
    [<000000005723dc17>] amdgpu_ttm_copy_mem_to_mem+0x25b/0x540 [amdgpu]
    [<000000009372cf45>] amdgpu_move_blit.constprop.0+0x85/0x1b0 [amdgpu]
    [<00000000b09834ab>] amdgpu_bo_move+0x168/0x2b0 [amdgpu]
    [<000000009f1ae718>] ttm_bo_handle_move_mem+0x126/0x5c0 [ttm]
    [<00000000d0c0e30f>] ttm_bo_validate+0x174/0x1b0 [ttm]
    [<00000000812e63d8>] amdgpu_bo_fault_reserve_notify+0xe2/0x130 [amdgpu]
    [<00000000340ebb51>] ttm_bo_vm_fault+0xa7/0x650 [ttm]
    [<00000000a9630d5e>] __do_fault+0x31/0xf0
    [<000000008cecfe93>] __handle_mm_fault+0xccc/0x1390
    [<00000000984b2f55>] handle_mm_fault+0x15b/0x2f0
    [<0000000053ca6a37>] __do_page_fault+0x1a2/0x420
    [<00000000c546a67a>] page_fault+0x31/0x40
unreferenced object 0xffffa24c4471b040 (size 72):
  comm "sdma0", pid 402, jiffies 4294885609 (age 1870.427s)
  hex dump (first 32 bytes):
    a0 c7 36 59 4c a2 ff ff e0 95 fd c0 ff ff ff ff  ..6YL...........
    a4 2b 08 a0 06 00 00 00 58 e4 2a 61 50 a2 ff ff  .+......X.*aP...
  backtrace:
    [<0000000078aa5208>] amdgpu_fence_emit+0x2b/0x270 [amdgpu]
    [<00000000a223cd76>] amdgpu_ib_schedule+0x311/0x540 [amdgpu]
    [<000000004db3d964>] amdgpu_job_run+0xfc/0x1e0 [amdgpu]
    [<00000000bfb92cc3>] drm_sched_main+0xf7/0x2e0 [gpu_sched]
    [<00000000a857f89f>] kthread+0xf6/0x130
    [<0000000046d81882>] ret_from_fork+0x27/0x50
[...]

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4409 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-11-16 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16 11:26 bugzilla-daemon [this message]
2019-11-16 11:27 ` [Bug 112302] [kernel 5.4-rc7][amdgpu] kmemleak reports various leaks bugzilla-daemon
2019-11-16 11:28 ` bugzilla-daemon
2019-11-19 10:01 ` 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-112302-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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;
as well as URLs for NNTP newsgroup(s).