From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100891] failed to send pre message kernel output delays booting/suspending/resuming Date: Sun, 30 Apr 2017 15:40:24 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1465766437==" 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 62B5589BA1 for ; Sun, 30 Apr 2017 15:40:24 +0000 (UTC) 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 --===============1465766437== Content-Type: multipart/alternative; boundary="14935668240.eba8.31942"; charset="UTF-8" --14935668240.eba8.31942 Date: Sun, 30 Apr 2017 15:40:24 +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=3D100891 Bug ID: 100891 Summary: failed to send pre message kernel output delays booting/suspending/resuming Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: harn-solo@gmx.de Created attachment 131160 --> https://bugs.freedesktop.org/attachment.cgi?id=3D131160&action=3Dedit dmesg output (kernel 4.9) Starting with kernel version 4.9 the boot process, s3 suspend and s3 resume= is delayed by kernel messages like the following [ 17.322912]=20 failed to send pre message 148 ret is 0=20 [ 17.543482]=20 failed to send message 148 ret is 0=20 for a very long time, e.g. 10 min (see attachment for a full dmesg log). Wh= en the system is fully booted everything else seems to be fine. I'm not sure if it is related at all, but I did a quick bisection: between 4.9-rc2 and 4.9-rc3, with the introduction of commit 3b496626ee8f07919256a4e99cddf42ecd4ba891 I had to supply a new firmware file (topaz_k_smc.bin) otherwise my screen remains black. After supplying the missing firmware-file from from linux-firmware.git I noticed the long boot delay and the messages. Kernel series 4.11-rcX reduces the delays drastically, down to around 1-2 minutes but after a resume from s3 the GPUs gets hot very quickly without f= ans kicking in until it reaches some sort of emergency mode with short bursts of jet engine like fans. This happens on the kernels 4.9-rc3 up to the latest 4.11-rc, always tested with the latest set of firmware files. My GPU-hardware is a Sapphire R9 380X: 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Amethyst XT [Radeon R9 M295X Mac Edition] (rev f1) 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aad8 --=20 You are receiving this mail because: You are the assignee for the bug.= --14935668240.eba8.31942 Date: Sun, 30 Apr 2017 15:40:24 +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
Bug ID 100891
Summary failed to send pre message kernel output delays booting/suspe= nding/resuming
Product DRI
Version unspecified
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter harn-solo@gmx.de 

Created attachment 131=
160 [details]
dmesg output (kernel 4.9)

Starting with kernel version 4.9 the boot process, s3 suspend and s3 resume=
 is
delayed by kernel messages like the following

[   17.322912]=20
                failed to send pre message 148 ret is 0=20
[   17.543482]=20
                failed to send message 148 ret is 0=20

for a very long time, e.g. 10 min (see attachment for a full dmesg log). Wh=
en
the system is fully booted everything else seems to be fine.


I'm not sure if it is related at all, but I did a quick bisection: between
4.9-rc2 and 4.9-rc3, with the introduction of commit
3b496626ee8f07919256a4e99cddf42ecd4ba891 I had to supply a new firmware file
(topaz_k_smc.bin) otherwise my screen remains black. After supplying the
missing firmware-file from from linux-firmware.git I noticed the long boot
delay and the messages.

Kernel series 4.11-rcX reduces the delays drastically, down to around 1-2
minutes but after a resume from s3 the GPUs gets hot very quickly without f=
ans
kicking in until it reaches some sort of emergency mode with short bursts of
jet engine like fans.

This happens on the kernels 4.9-rc3 up to the latest 4.11-rc, always tested
with the latest set of firmware files.

My GPU-hardware is a Sapphire R9 380X:

05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Amethyst XT [Radeon R9 M295X Mac Edition] (rev f1)
05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aad8

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