All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204145] New: amdgpu video playback causes host to hard reset (checkstop) on POWER9 with RX 580
Date: Fri, 12 Jul 2019 02:43:41 +0000	[thread overview]
Message-ID: <bug-204145-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=204145

            Bug ID: 204145
           Summary: amdgpu video playback causes host to hard reset
                    (checkstop) on POWER9 with RX 580
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.1.15
          Hardware: PPC-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: shawn@anastas.io
        Regression: No

Created attachment 283635
  --> https://bugzilla.kernel.org/attachment.cgi?id=283635&action=edit
5.1.15 kconfig

On recent kernels (at least since 5.1.15), video playback will (sometimes) hard 
reset my POWER9 system with an AMD RX 580. Due to the nature of the crash, it
does not seem that any kernel logs are produced by the event. The system
Hostboot firmware does record the crash though, and it produces a GUARD event
which disables the CPU slice the crash occurred on for subsequent boots until 
it is cleared.

An upstream Hostboot issue has been submitted by another person who has
encountered this behavior as well:
https://github.com/open-power/hostboot/issues/180

I have been unable to reproduce the issue on kernel 5.0.9, indicating a 
regression somewhere in between.

Attached is my 5.1.15 kernel config, the output of lspci -vv, and the contents
of /proc/cpuinfo.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-07-12  2:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  2:43 bugzilla-daemon [this message]
2019-07-12  2:44 ` [Bug 204145] amdgpu video playback causes host to hard reset (checkstop) on POWER9 with RX 580 bugzilla-daemon
2019-07-12  2:44 ` bugzilla-daemon
2019-07-12  2:59 ` bugzilla-daemon
2019-07-13 13:40 ` bugzilla-daemon
2019-07-14 15:35 ` bugzilla-daemon
2019-07-16  0:13 ` bugzilla-daemon
2019-07-16  0:16 ` bugzilla-daemon
2019-07-16  9:49 ` bugzilla-daemon
2019-07-16 13:01 ` bugzilla-daemon
2019-07-16 18:54 ` bugzilla-daemon
2019-07-16 18:55 ` bugzilla-daemon
2019-07-16 20:18 ` bugzilla-daemon
2019-07-16 20:20 ` bugzilla-daemon
2019-07-16 20:26 ` bugzilla-daemon
2019-07-17  9:36 ` bugzilla-daemon
2019-07-17 19:12 ` bugzilla-daemon
2019-07-17 19:42 ` bugzilla-daemon
2019-07-17 20:02 ` bugzilla-daemon
2019-07-17 20:30 ` bugzilla-daemon
2019-07-17 22:09 ` bugzilla-daemon
2019-07-17 23:20 ` bugzilla-daemon
2019-07-17 23:58 ` bugzilla-daemon
2019-07-18  0:39 ` bugzilla-daemon
2019-07-18  0:49 ` bugzilla-daemon
2019-07-18  0:50 ` bugzilla-daemon
2019-07-22 23:11 ` bugzilla-daemon
2019-07-30  5:28 ` 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-204145-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.