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 02:33:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0652923519==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0743F6E21C for ; Tue, 13 Jun 2017 02:33:38 +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 --===============0652923519== Content-Type: multipart/alternative; boundary="14973212171.3aA460B9c.7638"; charset="UTF-8" --14973212171.3aA460B9c.7638 Date: Tue, 13 Jun 2017 02:33:37 +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 #2 from Michel D=C3=A4nzer --- Looks like amdgpu_atombios_crtc_powergate_init scribbles over the stack. (In reply to Carlo Caione from comment #1) > If I recompile the kernel forcing CONFIG_CC_STACKPROTECTOR_NONE =3D=3D no= ne I don't > have the panic anymore (of course) but I can still see the corruption at = boot > (and weird artifacts on plymouth). What kind of artifacts in plymouth? Does e.g. X work correctly? --=20 You are receiving this mail because: You are the assignee for the bug.= --14973212171.3aA460B9c.7638 Date: Tue, 13 Jun 2017 02:33:37 +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 # 2 on bug 10138= 7 from Michel D=C3=A4nzer 
Looks like amdgpu_atombios_crtc_powergate_init scribbles over =
the stack.

(In reply to Carlo Caione from comm=
ent #1)
> If I recompile the kernel forcing CONFIG_CC_STAC=
KPROTECTOR_NONE =3D=3D none I don't
> have the panic anymore (of course) but I can still see the corruption =
at boot
> (and weird artifacts on plymouth).

What kind of artifacts in plymouth? Does e.g. X work correctly?

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