From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199653] [AMDGPU][DC] BUG: unable to handle kernel NULL pointer dereference (trace decoded)
Date: Tue, 29 May 2018 12:25:04 +0000 [thread overview]
Message-ID: <bug-199653-2300-QUpYgLtHxI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199653-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199653
James Le Cuirot (chewi@gentoo.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chewi@gentoo.org
--- Comment #4 from James Le Cuirot (chewi@gentoo.org) ---
I have almost exactly the same hardware but the Ryzen 7 (2700U) version. I also
get multiple daily freezes. Many thanks for the additional info, I never
managed to get any. I did try kdump but it never triggers, even when forcing a
kernel panic. I'm now running OpenSUSE 15.0 with kernels from the "stable"
repository (currently 4.16.12-1.g39c7522) and recent Mesa 18.2 prerelease
builds.
--
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-05-29 12:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 9:09 [Bug 199653] New: [AMDGPU][DC] BUG: unable to handle kernel NULL pointer dereference (trace decoded) bugzilla-daemon
2018-05-08 9:10 ` [Bug 199653] " bugzilla-daemon
2018-05-08 9:13 ` bugzilla-daemon
2018-05-08 9:13 ` bugzilla-daemon
2018-05-29 12:25 ` bugzilla-daemon [this message]
2018-06-16 16:30 ` bugzilla-daemon
2018-06-16 18:23 ` bugzilla-daemon
2018-06-20 19:57 ` bugzilla-daemon
2018-07-13 20:03 ` bugzilla-daemon
2018-08-06 10:33 ` bugzilla-daemon
2018-08-06 11:05 ` bugzilla-daemon
2018-08-17 11:37 ` 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-199653-2300-QUpYgLtHxI@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;
as well as URLs for NNTP newsgroup(s).