All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98189] [amdgpu SI] "gpu fault detect" in Left 4 Dead 2
Date: Mon, 10 Oct 2016 14:25:16 +0000	[thread overview]
Message-ID: <bug-98189-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 98189
           Summary: [amdgpu SI] "gpu fault detect" in Left 4 Dead 2
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: arek.rusi@gmail.com

Created attachment 127170
  --> https://bugs.freedesktop.org/attachment.cgi?id=127170&action=edit
kernel log

Hi, 
kernel - drm-next-4.9-wip + drm/amdgpu: disable CRTCs before teardown
mesa,libdrm,amdgpu,llvm form git/svn
This is not regression, this happened since dpm is workable. 

GPU/VM faults appears everywhere and everytime: gameplay, loading all the time. 
This is log from loading game and less than 1min of gameplay :)

I don't see any performance regression.

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

[-- Attachment #1.2: Type: text/html, Size: 2454 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:[~2016-10-10 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 14:25 bugzilla-daemon [this message]
2016-10-10 14:48 ` [Bug 98189] [amdgpu SI] "gpu fault detect" in Left 4 Dead 2 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-98189-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.