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 209987] Memory leak in amdgpu_dm_update_connector_after_detect
Date: Mon, 21 Dec 2020 15:57:53 +0000	[thread overview]
Message-ID: <bug-209987-2300-vnFepn7bJj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209987-2300@https.bugzilla.kernel.org/>

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

youling257@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |youling257@gmail.com

--- Comment #4 from youling257@gmail.com ---
I have the same memory leak.

android_x86:/ # echo scan >  /sys/kernel/debug/kmemleak
android_x86:/ # cat /sys/kernel/debug/kmemleak
android_x86:/ # echo scan >  /sys/kernel/debug/kmemleak
android_x86:/ # cat /sys/kernel/debug/kmemleak
unreferenced object 0xffff8edad8208580 (size 128):
  comm "ueventd", pid 1498, jiffies 4294676333 (age 65.106s)
  hex dump (first 32 bytes):
    22 16 04 00 00 0a 30 0a 50 0a a0 0a 00 00 40 06  ".....0.P.....@.
    43 06 48 06 69 06 00 00 05 00 00 00 00 00 00 00  C.H.i...........
  backtrace:
    [<0000000080ce8e0b>] do_detailed_mode+0x27c/0x520 [drm]
    [<000000000427e646>] drm_for_each_detailed_block.part.0+0x35/0x110 [drm]
    [<00000000566583b3>] drm_add_edid_modes+0x22b/0x1880 [drm]
    [<00000000f63b328b>] amdgpu_dm_update_connector_after_detect+0x385/0x4f0
[amdgpu]
    [<000000009f1bbb4c>] dm_helpers_read_local_edid+0xaa/0x170 [amdgpu]
    [<0000000005f6f065>] dc_link_detect_helper+0x29b/0xd70 [amdgpu]
    [<00000000a096d0f5>] dc_link_detect+0x31/0x50 [amdgpu]
    [<000000009a977098>] amdgpu_dm_init.isra.0.cold+0xf81/0x1297 [amdgpu]
    [<00000000cfd3da50>] dm_hw_init+0xe/0x20 [amdgpu]
    [<00000000128bd3d5>] amdgpu_device_init.cold+0x13c7/0x16b5 [amdgpu]
    [<0000000039b2a07d>] amdgpu_driver_load_kms+0x2b/0x200 [amdgpu]
    [<000000009b370228>] amdgpu_pci_probe+0x129/0x1b0 [amdgpu]
    [<0000000066485d99>] pci_device_probe+0xd2/0x150
    [<00000000c858be29>] really_probe+0x232/0x460
    [<00000000f84cda17>] driver_probe_device+0x5d/0x150
    [<00000000103f2cc3>] device_driver_attach+0xa1/0xb0
unreferenced object 0xffff8edad828f280 (size 128):
  comm "ueventd", pid 1498, jiffies 4294676333 (age 65.107s)
  hex dump (first 32 bytes):
    14 44 02 00 80 07 d8 07 04 08 98 08 00 00 38 04  .D............8.
    3c 04 41 04 65 04 00 00 0a 00 00 00 00 00 00 00  <.A.e...........
  backtrace:
    [<0000000017977f42>] drm_mode_duplicate+0x1f/0x90 [drm]
    [<00000000c4367b7e>] drm_mode_std+0x1fe/0x5e0 [drm]
    [<00000000d7555cdd>] drm_add_edid_modes+0x2c7/0x1880 [drm]
    [<00000000f63b328b>] amdgpu_dm_update_connector_after_detect+0x385/0x4f0
[amdgpu]
    [<000000009f1bbb4c>] dm_helpers_read_local_edid+0xaa/0x170 [amdgpu]
    [<0000000005f6f065>] dc_link_detect_helper+0x29b/0xd70 [amdgpu]
    [<00000000a096d0f5>] dc_link_detect+0x31/0x50 [amdgpu]
    [<000000009a977098>] amdgpu_dm_init.isra.0.cold+0xf81/0x1297 [amdgpu]
    [<00000000cfd3da50>] dm_hw_init+0xe/0x20 [amdgpu]
    [<00000000128bd3d5>] amdgpu_device_init.cold+0x13c7/0x16b5 [amdgpu]
    [<0000000039b2a07d>] amdgpu_driver_load_kms+0x2b/0x200 [amdgpu]
    [<000000009b370228>] amdgpu_pci_probe+0x129/0x1b0 [amdgpu]
    [<0000000066485d99>] pci_device_probe+0xd2/0x150
    [<00000000c858be29>] really_probe+0x232/0x460
    [<00000000f84cda17>] driver_probe_device+0x5d/0x150
    [<00000000103f2cc3>] device_driver_attach+0xa1/0xb0

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

You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-12-21 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-01  6:15 [Bug 209987] New: Memory leak in amdgpu_dm_update_connector_after_detect bugzilla-daemon
2020-11-01  6:19 ` [Bug 209987] " bugzilla-daemon
2020-11-09  4:24 ` bugzilla-daemon
2020-11-09  6:14 ` bugzilla-daemon
2020-12-21 15:57 ` bugzilla-daemon [this message]
2020-12-21 16:29 ` bugzilla-daemon
2020-12-21 16:47 ` bugzilla-daemon
2020-12-21 17:17 ` bugzilla-daemon
2020-12-24 15:01 ` bugzilla-daemon
2021-01-05 14:14 ` bugzilla-daemon
2021-01-10 19:47 ` 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-209987-2300-vnFepn7bJj@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