From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99387] Kernel 4.9: Kaveri + Hainan choked on boot using amdgpu
Date: Fri, 24 Feb 2017 18:22:33 +0000 [thread overview]
Message-ID: <bug-99387-502-d718C8Ihf0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99387-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1054 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99387
--- Comment #19 from Luya Tshimbalanga <luya@fedoraproject.org> ---
Following up this week with current patched kernel 4.9.11 from Mystro256 COPR
repository based on Alex's branch.
The South Island part of hybrid GPU.e. Hainan and its derivative (Sun PRO) runs
smoothly without noticeable bug using via Applications "Launch with Dedicated
Graphic Card" on Gnome Shell 3.22.
Looking at the journalctl report sorted by amdgpu:
kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link
status failed
kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery
failed
Not sure if that part is fixed as it does not appear affect the whole
functionality. If all South Island support works fine with amdgpu module,
perhaps will be time to enable it by default on future kernel release. If Marco
agree, perhaps this report can be closed as fixed.
Thanks for the hard work.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1866 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:[~2017-02-24 18:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 19:05 [Bug 99387] Kernel 4.9: Kaveri + Hainan choked on boot using amdgpu bugzilla-daemon
2017-01-12 19:47 ` bugzilla-daemon
2017-01-12 22:50 ` bugzilla-daemon
2017-01-12 22:53 ` bugzilla-daemon
2017-01-13 0:57 ` bugzilla-daemon
2017-01-13 3:12 ` bugzilla-daemon
2017-01-13 3:59 ` bugzilla-daemon
2017-01-13 6:00 ` bugzilla-daemon
2017-01-27 15:34 ` bugzilla-daemon
2017-01-28 19:08 ` bugzilla-daemon
2017-02-04 4:47 ` bugzilla-daemon
2017-02-04 4:59 ` bugzilla-daemon
2017-02-04 6:10 ` bugzilla-daemon
2017-02-10 22:20 ` bugzilla-daemon
2017-02-10 22:24 ` bugzilla-daemon
2017-02-10 23:13 ` bugzilla-daemon
2017-02-11 17:28 ` bugzilla-daemon
2017-02-15 1:29 ` bugzilla-daemon
2017-02-21 21:39 ` bugzilla-daemon
2017-02-24 18:22 ` bugzilla-daemon [this message]
2017-03-07 4:27 ` bugzilla-daemon
2017-03-07 14:55 ` 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-99387-502-d718C8Ihf0@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;
as well as URLs for NNTP newsgroup(s).