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: Thu, 12 Apr 2018 17:08:58 +0000 [thread overview]
Message-ID: <bug-105619-502-SHOTG9z3M0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105619-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 629 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105619
--- Comment #6 from Michael Lange <linuxstuff@milaw.biz> ---
Running in the same problem, same error in dmesg.
I have two monitors (AOG AG272FCX), one connected via hdmi to the discrete gpu
(HD 8800) and the second one connected via hdmi to the integrated gpu (KAVERI).
On Windows 10 both working as expected, but in linux only the first monitor
(connected to HD8800) works.
Mainbord: Gigabyte G1.Sniper A88X-CF
CPU: A10-7850K
linux: 4.16.2
The dmesg and Xorg.0.log are attached
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1438 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-04-12 17:08 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
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 [this message]
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-SHOTG9z3M0@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