All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110971] GPU HANG: ecode 6:1:0xfffffffe, in spring-main [8656], hang on rcs0
Date: Sat, 22 Jun 2019 23:35:02 +0000	[thread overview]
Message-ID: <bug-110971-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 110971
           Summary: GPU HANG: ecode 6:1:0xfffffffe, in spring-main [8656],
                    hang on rcs0
           Product: Mesa
           Version: 19.1
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/DRI/i915
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: Chris.Rebischke@archlinux.org
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 144614
  --> https://bugs.freedesktop.org/attachment.cgi?id=144614&action=edit
crash dump from /sys/class/drm/card0/error

I get unspecified GPU hangs while playing games. It mostly occurs when my CPU
starts throttling:

[ 5838.889104] mce: CPU0: Package temperature above threshold, cpu clock
throttled (total events = 100749)
[ 5838.889108] mce: CPU2: Package temperature above threshold, cpu clock
throttled (total events = 100749)
[ 5838.889110] mce: CPU3: Package temperature above threshold, cpu clock
throttled (total events = 100749)
[ 5838.889112] mce: CPU1: Package temperature above threshold, cpu clock
throttled (total events = 100749)
[ 5900.819612] mce: CPU2: Core temperature above threshold, cpu clock throttled
(total events = 16235)
[ 5900.819613] mce: CPU3: Core temperature above threshold, cpu clock throttled
(total events = 16235)
[ 5900.827685] mce: CPU2: Core temperature/speed normal
[ 5900.827686] mce: CPU3: Core temperature/speed normal
[ 6138.891505] mce: CPU1: Package temperature above threshold, cpu clock
throttled (total events = 171156)
[ 6138.891506] mce: CPU0: Package temperature above threshold, cpu clock
throttled (total events = 171156)
[ 6138.891528] mce: CPU2: Package temperature above threshold, cpu clock
throttled (total events = 171156)
[ 6138.891529] mce: CPU3: Package temperature above threshold, cpu clock
throttled (total events = 171156)
[ 6176.479565] i915 0000:00:02.0: GPU HANG: ecode 6:1:0xfffffffe, in
spring-main [8656], hang on rcs0
[ 6176.479570] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 6176.479572] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 6176.479573] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 6176.479574] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 6176.479575] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 6176.479642] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 6422.644956] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 6438.888919] mce: CPU3: Package temperature/speed normal
[ 6438.888920] mce: CPU2: Package temperature/speed normal
[ 6438.888924] mce: CPU1: Package temperature/speed normal
[ 6438.888926] mce: CPU0: Package temperature/speed normal

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

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

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

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

             reply	other threads:[~2019-06-22 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-22 23:35 bugzilla-daemon [this message]
2019-09-18 19:41 ` [Bug 110971] GPU HANG: ecode 6:1:0xfffffffe, in spring-main [8656], hang on rcs0 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-110971-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 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.