dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
Date: Tue, 30 Oct 2018 23:17:33 +0000	[thread overview]
Message-ID: <bug-108585-502-yzOZH3n42b@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108585-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Benjamin Herrenschmidt <benh@kernel.crashing.org> ---
They may or may not be related ... Alex, kexec is how we boot these machines,
there's a Linux kernel in flash that runs a Linux based bootloader.

Until recently however, that didn't have an amdgpu driver. This might have
changed.

Dan... did you do some firmware changes here ? Could it have to do with the
versions differences between petitboot and the final kernel ?

Alex, whether we track it here or separately, we probably need to look into
kexec support. It's not just us, there's a bit of momentum around kexec based
bootloaders (google's on it too) as was seen at the recent OSFC (firmware
conf).

A workaround in the meantime (for kexec problems) could be to hot reset the
card during the transition I suppose.

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

[-- Attachment #1.2: Type: text/html, Size: 1755 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-10-30 23:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
2018-10-29 11:04 ` bugzilla-daemon
2018-10-29 12:58 ` bugzilla-daemon
2018-10-29 16:08 ` bugzilla-daemon
2018-10-30  3:39 ` bugzilla-daemon
2018-10-30 14:20 ` bugzilla-daemon
2018-10-30 23:17 ` bugzilla-daemon [this message]
2018-10-31  0:44 ` bugzilla-daemon
2018-10-31  7:40 ` bugzilla-daemon
2018-10-31  8:09 ` bugzilla-daemon
2018-10-31  8:12 ` bugzilla-daemon
2018-10-31  8:35 ` bugzilla-daemon
2018-10-31  9:31 ` bugzilla-daemon
2018-10-31 10:13 ` bugzilla-daemon
2018-10-31 15:13 ` bugzilla-daemon
2018-11-01  5:14 ` bugzilla-daemon
2018-11-01  9:49 ` bugzilla-daemon
2018-11-01 12:37 ` bugzilla-daemon
2018-12-14 20:46 ` bugzilla-daemon
2018-12-14 20:47 ` bugzilla-daemon
2019-01-08 13:43 ` 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-108585-502-yzOZH3n42b@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;
as well as URLs for NNTP newsgroup(s).