dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-100891-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2168 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100891

            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=131160&action=edit
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] 
                failed to send pre message 148 ret is 0 
[   17.543482] 
                failed to send message 148 ret is 0 

for a very long time, e.g. 10 min (see attachment for a full dmesg log). When
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 fans
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.

[-- Attachment #1.2: Type: text/html, Size: 3612 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-04-30 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 15:40 bugzilla-daemon [this message]
2017-04-30 15:41 ` [Bug 100891] failed to send pre message kernel output delays booting/suspending/resuming bugzilla-daemon
2017-05-01  8:41 ` bugzilla-daemon
2017-05-01  8:42 ` bugzilla-daemon
2017-05-14 15:55 ` bugzilla-daemon
2018-04-30 15:00 ` bugzilla-daemon
2018-04-30 15:00 ` bugzilla-daemon
2018-04-30 15:02 ` bugzilla-daemon
2018-08-22  9:37 ` bugzilla-daemon
2018-10-01 12:12 ` bugzilla-daemon
2019-11-19  8:15 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100891-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox