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: Sun, 01 Nov 2020 06:19:11 +0000	[thread overview]
Message-ID: <bug-209987-2300-xoXwmK6wFP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209987-2300@https.bugzilla.kernel.org/>

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

--- Comment #1 from Lee Starnes (lstarnes1024@gmail.com) ---
Created attachment 293343
  --> https://bugzilla.kernel.org/attachment.cgi?id=293343&action=edit
dmesg with oom-killer invocations

Note that the stack has amdgpu_dm_update_connector_after_detect+0x28d/0x330 >
drm_add_edid_modes+0x6e1/0x1860. This was recorded on Linux 5.9.1, but the
kmemleak was on linux 5.9.2.

-- 
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

  reply	other threads:[~2020-11-01  6:19 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 ` bugzilla-daemon [this message]
2020-11-09  4:24 ` [Bug 209987] " bugzilla-daemon
2020-11-09  6:14 ` bugzilla-daemon
2020-12-21 15:57 ` bugzilla-daemon
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-xoXwmK6wFP@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