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 104854] smu7_populate_single_firmware_entry fails to load powerplay firmware.
Date: Tue, 19 Jun 2018 09:06:13 +0000	[thread overview]
Message-ID: <bug-104854-502-ueLoV0SSBC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104854-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from José Pekkarinen <koalinux@gmail.com> ---
I'm afraid I reproduced this again using the kernel 4.17.2 where I see the
following commit:

commit 9ca5a2ae4259e7aec8efb0db0f6ec721a6854c54
Merge: bee797529d7c c62ec4610c40
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu May 24 08:49:56 2018 -0700

    Merge tag 'pm-4.17-rc7' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm

    Pull power management fix from Rafael Wysocki:
     "Fix a regression from the 4.15 cycle that caused the system suspend
      and resume overhead to increase on many systems and triggered more
      serious problems on some of them (Rafael Wysocki)"

    * tag 'pm-4.17-rc7' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      PM / core: Fix direct_complete handling for devices with no callbacks

I'll attach the boot process with the traceback soon.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1959 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

  parent reply	other threads:[~2018-06-19  9:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  8:32 [Bug 104854] smu7_populate_single_firmware_entry fails to load powerplay firmware bugzilla-daemon
2018-03-07  9:39 ` bugzilla-daemon
2018-03-08 20:22 ` bugzilla-daemon
2018-03-08 20:36 ` bugzilla-daemon
2018-03-09  7:36 ` bugzilla-daemon
2018-03-30 16:12 ` bugzilla-daemon
2018-03-31 17:51 ` bugzilla-daemon
2018-03-31 19:10 ` bugzilla-daemon
2018-06-15 15:33 ` bugzilla-daemon
2018-06-19  9:06 ` bugzilla-daemon [this message]
2018-06-19  9:15 ` bugzilla-daemon
2018-06-23 21:19 ` bugzilla-daemon
2018-06-23 21:22 ` bugzilla-daemon
2019-11-19  8:29 ` 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-104854-502-ueLoV0SSBC@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