All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206519] [amdgpu] kernel NULL pointer dereference on shutdown
Date: Tue, 18 Feb 2020 17:19:41 +0000	[thread overview]
Message-ID: <bug-206519-2300-cTzE2dGCBA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206519-2300@https.bugzilla.kernel.org/>

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

--- Comment #4 from Shlomo (shlomo@fastmail.com) ---
I bisected the bug.

The first bad commit is 96a3b32e67236f547cc8acd69d5a3cef125b2295
(drm/amd/display: only enable HDCP for DCN+) with
ea268870d6f548d0661e896e9746673210c1fa79 (drm/amd/display: Add hdcp to Kconfig)
cherry-picked on top of it.

(The previous commit da3fd7ac0bcf372cc57117bdfcd725cca7ef975a with
ea268870d6f548d0661e896e9746673210c1fa79 cherry-picked on top of it is good.)

The call trace for this bug is the same as I posted above.

-- 
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-02-18 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 16:07 [Bug 206519] New: [amdgpu] kernel NULL pointer dereference on shutdown bugzilla-daemon
2020-02-13 16:09 ` [Bug 206519] " bugzilla-daemon
2020-02-13 16:20 ` bugzilla-daemon
2020-02-14 11:54 ` bugzilla-daemon
2020-02-18 17:19 ` bugzilla-daemon [this message]
2020-02-18 17:19 ` [Bug 206519] [amdgpu] kernel NULL pointer dereference on shutdown when CONFIG_DRM_AMD_DC_HDCP=y bugzilla-daemon
2020-02-18 18:25 ` bugzilla-daemon
2020-02-19  8:32 ` bugzilla-daemon
2020-04-07 17:20 ` 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-206519-2300-cTzE2dGCBA@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.