<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [radeonsi] Tahiti LE: GFX block is not functional, CP is okay"
href="https://bugs.freedesktop.org/show_bug.cgi?id=60879#c163">Comment # 163</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [radeonsi] Tahiti LE: GFX block is not functional, CP is okay"
href="https://bugs.freedesktop.org/show_bug.cgi?id=60879">bug 60879</a>
from <span class="vcard"><a class="email" href="mailto:elektorronikci@gmail.com" title="Ayhan <elektorronikci@gmail.com>"> <span class="fn">Ayhan</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=128452" name="attach_128452" title="dmesg for linux 4.9 amdgpu driver">attachment 128452</a> <a href="attachment.cgi?id=128452&action=edit" title="dmesg for linux 4.9 amdgpu driver">[details]</a></span>
dmesg for linux 4.9 amdgpu driver
The attachment is dmesg of linux 4.9 and AMDGPU driver is in use. After startx,
the colorful scrambled screen happened again, but it stayed still, not
resetting screen for every 5-6 seconds like radeon driver. I issued a reboot
command via SSH shell, it returned into old framebuffer correctly and rebooted
succesfully, unlike the radeon driver case.
Dmesg file is the original one, not the journalctl capture, journalctl
sometimes omits some messages.
This line was written after startx:
[drm] xxxx: dce_v6_0_afmt_setmode ----no impl !!!!!!!!
Also that line was omitted by journalctl...</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>