From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100058] NULL pointer dereference when blacklisting radeon
Date: Sat, 04 Mar 2017 13:19:34 +0000 [thread overview]
Message-ID: <bug-100058-502-HugoRPZ98Z@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100058-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 358 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100058
--- Comment #2 from Edward O'Callaghan <funfunctor@folklore1984.net> ---
OK so we narrowed the problem down to dpm.
(12:17:01 AM) mulander: yep, blacklisted radeon, amdgpu.dpm=0 and booted to X
properly without a crash
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1155 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-04 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 12:45 [Bug 100058] NULL pointer dereference when blacklisting radeon bugzilla-daemon
2017-03-04 13:09 ` bugzilla-daemon
2017-03-04 13:19 ` bugzilla-daemon [this message]
2017-03-04 13:20 ` bugzilla-daemon
2017-03-04 13:59 ` [Bug 100058] amdgpu/dpm: NULL pointer dereference bugzilla-daemon
2017-03-06 2:31 ` bugzilla-daemon
2017-03-06 10:41 ` bugzilla-daemon
2017-03-06 14:11 ` bugzilla-daemon
2017-03-07 1:13 ` bugzilla-daemon
2017-03-07 12:54 ` bugzilla-daemon
2017-03-07 15:13 ` bugzilla-daemon
2017-03-08 1:38 ` bugzilla-daemon
2017-03-25 13:51 ` bugzilla-daemon
2017-04-21 1:16 ` bugzilla-daemon
2017-04-21 11:46 ` bugzilla-daemon
2017-04-21 12:43 ` bugzilla-daemon
2019-11-19 8:14 ` 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-100058-502-HugoRPZ98Z@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).