From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104611] [fiji, polaris10] BUG: unable to handle kernel NULL pointer dereference when waking up displays with amdgpu.dc=1
Date: Thu, 18 Jan 2018 08:38:59 +0000 [thread overview]
Message-ID: <bug-104611-502-BoGmsQgOcL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104611-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 475 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104611
--- Comment #6 from Vedran Miletić <vedran@miletic.net> ---
(In reply to Roman Li from comment #5)
> So what was the repro rate for the issue?
> Can you try to reproduce on the latest rawhide
> 4.15.0-0.rc8.git0.1.fc28.x86_64 and/or collect dmesg with amdgpu.dc_log=1
> for the bad case? Thank you.
I can do that over the weekend.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1466 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:[~2018-01-18 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 22:38 [Bug 104611] [fiji] BUG: unable to handle kernel NULL pointer dereference when waking up displays with amdgpu.dc=1 bugzilla-daemon
2018-01-12 22:48 ` bugzilla-daemon
2018-01-15 16:02 ` bugzilla-daemon
2018-01-16 21:55 ` bugzilla-daemon
2018-01-17 15:27 ` bugzilla-daemon
2018-01-17 15:38 ` bugzilla-daemon
2018-01-17 15:39 ` [Bug 104611] [fiji, polaris10] " bugzilla-daemon
2018-01-18 0:07 ` bugzilla-daemon
2018-01-18 8:38 ` bugzilla-daemon [this message]
2018-01-29 16:20 ` bugzilla-daemon
2018-07-12 14:11 ` bugzilla-daemon
2018-07-12 14:14 ` bugzilla-daemon
2019-04-23 11:16 ` bugzilla-daemon
2019-04-23 11:17 ` bugzilla-daemon
2019-11-19 8:28 ` 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-104611-502-BoGmsQgOcL@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 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.