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: Fri, 13 Apr 2018 00:25:02 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0356566158==" 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 304786E23F for ; Fri, 13 Apr 2018 00:25:02 +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 --===============0356566158== Content-Type: multipart/alternative; boundary="15235791010.59fC6ef.20451" Content-Transfer-Encoding: 7bit --15235791010.59fC6ef.20451 Date: Fri, 13 Apr 2018 00:25:01 +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 #30 from L.S.S. --- EDIT 2: I couldn't reproduce the issue on 4.17 this time even after 2 wakeu= ps. However, the issue I encountered was similar (system apparently froze when trying to wake up the screen).=20 After looking into it, I found that along with the errors that showed up li= ke that in Comment 16 (which did not crash the system), there was an additional "kernel BUG" related to dm_update_crtcs_state which was called by amdgpu_dm_atomic_check, but the log appeared to have been cut (the log entr= ies between the two errors were apparently unrelated to the error so I did not include them, and the new error began with a "--[ cut here ]--"). This additional error (not 100% reproducible) might be what actually crashed the system that time. --=20 You are receiving this mail because: You are the assignee for the bug.= --15235791010.59fC6ef.20451 Date: Fri, 13 Apr 2018 00:25:01 +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 # 30 on bug 10501= 8 from L.S.S. 
EDIT 2: I couldn't reproduce the issue on 4.17 this time even =
after 2 wakeups.
However, the issue I encountered was similar (system apparently froze when
trying to wake up the screen).=20

After looking into it, I found that along with the errors that showed up li=
ke
that in Comment 16 (which did =
not crash the system), there was an additional
"kernel BUG" related to dm_update_crtcs_state which was called by
amdgpu_dm_atomic_check, but the log appeared to have been cut (the log entr=
ies
between the two errors were apparently unrelated to the error so I did not
include them, and the new error began with a "--[ cut here ]--").=
 This
additional error (not 100% reproducible) might be what actually crashed the
system that time.

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