From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105018] Kernel panic when waking up after screen goes blank. Date: Mon, 30 Apr 2018 14:55:54 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1063345483==" 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 7D70D6E365 for ; Mon, 30 Apr 2018 14:55:54 +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 --===============1063345483== Content-Type: multipart/alternative; boundary="15251001541.DFF42b02.6310" Content-Transfer-Encoding: 7bit --15251001541.DFF42b02.6310 Date: Mon, 30 Apr 2018 14:55:54 +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=3D105018 --- Comment #32 from L.S.S. --- So it seems there definitely is a regression on 4.17 on this issue (the pat= ches are not required as the lines were already there in 4.17). This time it isn= 't a kernel panic, but an "invalid opcode" error caused by dm_update_crtcs_state that was called by amdgpu_dm_atomic_check. The issue is not 100% reproducible, but still means going to standby with an AMD GPU and DC is still dangerous and may result in losses of unsaved work. --=20 You are receiving this mail because: You are the assignee for the bug.= --15251001541.DFF42b02.6310 Date: Mon, 30 Apr 2018 14:55:54 +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

Comme= nt # 32 on bug 10501= 8 from L.S.S. 
So it seems there definitely is a regression on 4.17 on this i=
ssue (the patches
are not required as the lines were already there in 4.17). This time it isn=
't a
kernel panic, but an "invalid opcode" error caused by dm_update_c=
rtcs_state
that was called by amdgpu_dm_atomic_check.

The issue is not 100% reproducible, but still means going to standby with an
AMD GPU and DC is still dangerous and may result in losses of unsaved work.=

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