All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86891] AMD/ATI Tahiti XT 7970 - long lags/stutters in games
Date: Thu, 30 Oct 2014 22:29:31 +0000	[thread overview]
Message-ID: <bug-86891-2300-MLhsjOMzIG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86891-2300@https.bugzilla.kernel.org/>

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

--- Comment #15 from Michael Mair-Keimberger <bu9zilla@gmail.com> ---
Created attachment 155911
  --> https://bugzilla.kernel.org/attachment.cgi?id=155911&action=edit
picture

I've made a few other benchmarks and tried to take some screenshots.
Unfortunately vally doesn't include GALLIUM_HUD when i'm taking screenshot's.
As a workaround i've made photos with my mobile. Hope that's ok :)

On a side-note: I've got other kernel msg's with the unchanged kernel. Don't
know if it's relevant but it looks like that:

[ 2915.586345] radeon 0000:01:00.0: GPU fault detected: 146 0x00139004
[ 2915.586350] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00004B00
[ 2915.586353] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x13090004
[ 2915.586357] VM fault (0x04, vmid 9) at page 19200, write from CB (144)
[ 2915.586362] radeon 0000:01:00.0: GPU fault detected: 146 0x00339004
[ 2915.586365] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00004B07
[ 2915.586367] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x13090004
[ 2915.586370] VM fault (0x04, vmid 9) at page 19207, write from CB (144)
[ 2915.586374] radeon 0000:01:00.0: GPU fault detected: 146 0x00539004
[ 2915.586377] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00004B02
[ 2915.586379] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x13090004
[ 2915.586382] VM fault (0x04, vmid 9) at page 19202, write from CB (144)
[ 2915.586386] radeon 0000:01:00.0: GPU fault detected: 146 0x00739004
.
.
.

I don't know if i would get them with the changed kernel as-well, but with my
stable kernel (3.16) i never see such messages.

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

  parent reply	other threads:[~2014-10-30 22:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 15:28 [Bug 86891] New: AMD/ATI Tahiti XT 7970 - long lags/stutters in games bugzilla-daemon
2014-10-26 18:48 ` [Bug 86891] " bugzilla-daemon
2014-10-27 18:26 ` bugzilla-daemon
2014-10-27 20:25 ` bugzilla-daemon
2014-10-27 20:30 ` bugzilla-daemon
2014-10-27 22:45 ` bugzilla-daemon
2014-10-28  8:04 ` bugzilla-daemon
2014-10-29  8:46 ` bugzilla-daemon
2014-10-29 17:10 ` bugzilla-daemon
2014-10-29 17:26 ` bugzilla-daemon
2014-10-29 19:34 ` bugzilla-daemon
2014-10-29 22:04 ` bugzilla-daemon
2014-10-29 22:06 ` bugzilla-daemon
2014-10-30  3:17 ` bugzilla-daemon
2014-10-30 19:33 ` bugzilla-daemon
2014-10-30 22:29 ` bugzilla-daemon [this message]
2014-10-30 22:30 ` bugzilla-daemon
2014-10-31  3:28 ` bugzilla-daemon
2014-11-01 17:27 ` bugzilla-daemon
2014-11-01 19:45 ` bugzilla-daemon
2014-11-02 10:33 ` bugzilla-daemon
2014-11-02 10:41 ` bugzilla-daemon
2014-12-10 17:55 ` 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-86891-2300-MLhsjOMzIG@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.