From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101387] amdgpu display corruption and hang on AMD A10-9620P Date: Tue, 13 Jun 2017 08:49:08 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2045460528==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id F276E6E25A for ; Tue, 13 Jun 2017 08:49:07 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============2045460528== Content-Type: multipart/alternative; boundary="14973437470.675Faaa8.16668"; charset="UTF-8" --14973437470.675Faaa8.16668 Date: Tue, 13 Jun 2017 08:49:07 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D101387 --- Comment #5 from Carlo Caione --- > 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. 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); --=20 You are receiving this mail because: You are the assignee for the bug.= --14973437470.675Faaa8.16668 Date: Tue, 13 Jun 2017 08:49:07 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 5 on bug 10138= 7 from = Carlo Caione 
> 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.

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);

You are receiving this mail because:
  • You are the assignee for the bug.
= --14973437470.675Faaa8.16668-- --===============2045460528== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============2045460528==--