From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206519] [amdgpu] kernel NULL pointer dereference on shutdown
Date: Fri, 14 Feb 2020 11:54:39 +0000 [thread overview]
Message-ID: <bug-206519-2300-8Bc1DYvgCA@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 #3 from Shlomo (shlomo@fastmail.com) ---
The bug first occurs in Arch Linux 5.5.arch1-1, which set
CONFIG_DRM_AMD_DC_HDCP=y [1].
Arch Linux 5.4.15.arch1-1 is good.
Arch Linux 5.4.15.arch1-1 with CONFIG_DRM_AMD_DC_HDCP=y set (and no other
changes) is bad.
Arch Linux 5.5.arch1-1 (and later) is bad. (CONFIG_DRM_AMD_DC_HDCP=y is set)
Testing the most recent Arch Linux kernel shows the same:
Arch Linux 5.5.3.arch1 is bad.
Arch Linux 5.5.3.arch1 with CONFIG_DRM_AMD_DC_HDCP unset is good.
This means that this bug was triggered by changes to the config, not kernel
changes, so I don't know if this is a regression or not.
[1]
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=019514c4cdff26addfd49db8a78a857cb03994d9
--
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
next prev parent reply other threads:[~2020-02-14 11:54 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 [this message]
2020-02-18 17:19 ` bugzilla-daemon
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-8Bc1DYvgCA@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.