From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105619] Kernel DC oops on dce81_create_resource_pool with kernel 4.15
Date: Tue, 20 Mar 2018 15:30:45 +0000 [thread overview]
Message-ID: <bug-105619-502-4atxonf38k@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105619-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 466 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105619
--- Comment #2 from freedesktop@kp-tech.hu ---
Thanks for your help! It may be a warning about the audio fuse, but the
functionality loss is real - no secondary display exists/detected.
The same problem (same oops and no secondary display) exists with 4.13 kernel +
ROCK/ROCM DKMS (https://github.com/RadeonOpenCompute/ROCm).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1315 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-03-20 15:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 9:43 [Bug 105619] Kernel DC oops on dce81_create_resource_pool with kernel 4.15 bugzilla-daemon
2018-03-20 13:55 ` bugzilla-daemon
2018-03-20 15:30 ` bugzilla-daemon [this message]
2018-03-20 15:46 ` bugzilla-daemon
2018-03-21 9:41 ` bugzilla-daemon
2018-03-21 9:48 ` bugzilla-daemon
2018-04-12 17:08 ` bugzilla-daemon
2018-04-12 17:11 ` bugzilla-daemon
2018-04-12 17:13 ` bugzilla-daemon
2018-05-06 17:19 ` bugzilla-daemon
2018-05-06 17:20 ` bugzilla-daemon
2018-05-06 17:34 ` bugzilla-daemon
2019-11-19 8:32 ` 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-105619-502-4atxonf38k@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