From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199157] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
Date: Fri, 23 Mar 2018 03:52:12 +0000 [thread overview]
Message-ID: <bug-199157-2300-CZvROSk3Vh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199157-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199157
--- Comment #3 from Kyle De'Vir (kyle.devir@mykolab.com) ---
GPU-wise, I have an RX580 8GB. This morning, I started to wonder whether the
issue was not even be a driver bug, but actually related to the whole
"Performance Marginality Problem", as my AMD 1600X is one of the CPUs affected
by Ryzen hardware bug. A while ago, I started getting random MCEs, which I
suspected were related to the Ryzen bug. They stopped a while later,
mysteriously... then it was occasional hard-lockups, then this issue.
I'm trying to save up money for Ryzen 2, so hopefully this issue won't pop up
again.
--
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:[~2018-03-23 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 7:19 [Bug 199157] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 bugzilla-daemon
2018-03-22 15:08 ` [Bug 199157] " bugzilla-daemon
2018-03-23 3:41 ` bugzilla-daemon
2018-03-23 3:52 ` bugzilla-daemon [this message]
2018-03-23 14:49 ` bugzilla-daemon
2018-03-24 3:33 ` 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-199157-2300-CZvROSk3Vh@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