<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - amdgpu display corruption and hang on AMD A10-9620P"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101387#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - amdgpu display corruption and hang on AMD A10-9620P"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101387">bug 101387</a>
from <span class="vcard"><a class="email" href="mailto:carlo@caione.org" title="Carlo Caione <carlo@caione.org>"> <span class="fn">Carlo Caione</span></a>
</span></b>
<pre><span class="quote">> That could be a plymouth bug. I've noticed that it doesn't seem to call
> drmModeCrtcSetGamma to make sure the display CLUTs are initialized to
> appropriate values.</span >
Yeah, it could be, I'll investigate the plymouth issue later, right now the
kernel panic situation is the top priority on my list :D
Any idea what's triggering the stack corruption? I'm still investigating but
right now my bet is on casting args to (uint32_t *) in
amdgpu_atom_execute_table(adev->mode_info.atom_context, index, (uint32_t
*)&args);</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>