All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75992] Display freezes & corruption with an r7 260x on 3.14-rc6
Date: Thu, 10 Apr 2014 18:37:18 +0000	[thread overview]
Message-ID: <bug-75992-502-xeKgI0lYal@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75992-502@http.bugs.freedesktop.org/>


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

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

--- Comment #24 from Ed Tomlinson <edt@aei.ca> ---
Just to see what happens with the latest drm fixes I built linux from git
(last commit 4ba85265790ba3681deeaf73f018c0eb829a7341).  I am still seeing
corruptions and eventually get stalls.  Lots of 

Apr 10 14:17:11 localhost kernel: [ 2390.829175] VM fault (0x00, vmid 0) at
page 0, read from '' (0x00000000) (0)
Apr 10 14:17:11 localhost kernel: [ 2390.829178] radeon 0000:01:00.0: GPU fault
detected: 147 0x049a4408
Apr 10 14:17:11 localhost kernel: [ 2390.829179] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Apr 10 14:17:11 localhost kernel: [ 2390.829180] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000

with a few like (maybe one for every 100 of the one above):

Apr 10 14:17:11 localhost kernel: [ 2390.828639] VM fault (0x08, vmid 13) at
page 0, read from 'TC3' (0x54433300) (68)
Apr 10 14:17:11 localhost kernel: [ 2390.828642] radeon 0000:01:00.0: GPU fault
detected: 147 0x049a0408
Apr 10 14:17:11 localhost kernel: [ 2390.828643] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Apr 10 14:17:11 localhost kernel: [ 2390.828644] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x1A008008

or

Apr 10 14:17:11 localhost kernel: [ 2390.805747] VM fault (0x08, vmid 13) at
page 31524, read from 'TC2' (0x54433200) (72)
Apr 10 14:17:11 localhost kernel: [ 2390.805749] radeon 0000:01:00.0: GPU fault
detected: 147 0x049a4808
Apr 10 14:17:11 localhost kernel: [ 2390.805749] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Apr 10 14:17:11 localhost kernel: [ 2390.805750] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000

or

Apr 10 13:42:44 localhost kernel: [  321.759360] VM fault (0x04, vmid 1) at
page 29021, read from 'TC3' (0x54433300) (68)
Apr 10 13:42:44 localhost kernel: [  321.759362] radeon 0000:01:00.0: GPU fault
detected: 146 0x0ba20404
Apr 10 13:42:44 localhost kernel: [  321.759363] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Apr 10 13:42:44 localhost kernel: [  321.759363] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000

interposed between the much more common message above.

These error happen with and without hyperz enabled
( via the following in .xinitrc
 export R600_HYPERZ=0
 export R600_DEBUG=nohyperz )

This is with ddx, glamor, mesa built from todays git (13:30 or so EDT)

Once I can get xorg rc to build with builtin glamor I'll try with it too.

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

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

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

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

  parent reply	other threads:[~2014-04-10 18:37 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 17:25 [Bug 75992] New: Display freezes & corruption with an r7 260x on 3.14-rc6 bugzilla-daemon
2014-03-10 17:25 ` [Bug 75992] " bugzilla-daemon
2014-03-10 17:28 ` bugzilla-daemon
2014-03-10 20:33 ` bugzilla-daemon
2014-03-23 20:04 ` bugzilla-daemon
2014-03-24 14:55 ` bugzilla-daemon
2014-03-25 13:00 ` bugzilla-daemon
2014-03-25 14:55 ` bugzilla-daemon
2014-03-26 17:33 ` bugzilla-daemon
2014-03-27 14:36 ` bugzilla-daemon
2014-03-27 18:53 ` bugzilla-daemon
2014-03-27 22:08 ` bugzilla-daemon
2014-03-28 12:13 ` bugzilla-daemon
2014-03-28 12:19 ` bugzilla-daemon
2014-03-28 14:12 ` bugzilla-daemon
2014-03-28 17:28 ` bugzilla-daemon
2014-03-28 18:18 ` bugzilla-daemon
2014-03-28 20:09 ` bugzilla-daemon
2014-03-28 23:07 ` bugzilla-daemon
2014-04-02 16:49 ` bugzilla-daemon
2014-04-02 22:31 ` bugzilla-daemon
2014-04-07 17:18 ` bugzilla-daemon
2014-04-10 15:19 ` bugzilla-daemon
2014-04-10 17:30 ` bugzilla-daemon
2014-04-10 17:35 ` bugzilla-daemon
2014-04-10 18:37 ` bugzilla-daemon [this message]
2014-04-10 18:44 ` bugzilla-daemon
2014-04-10 19:05 ` bugzilla-daemon
2014-04-10 19:10 ` bugzilla-daemon
2014-04-10 20:26 ` bugzilla-daemon
2014-04-10 20:36 ` bugzilla-daemon
2014-04-10 21:03 ` bugzilla-daemon
2014-04-10 21:30 ` bugzilla-daemon
2014-04-10 21:45 ` bugzilla-daemon
2014-04-10 21:47 ` bugzilla-daemon
2014-04-10 21:50 ` bugzilla-daemon
2014-04-10 22:09 ` bugzilla-daemon
2014-04-10 23:40 ` bugzilla-daemon
2014-04-11  0:59 ` bugzilla-daemon
2014-04-11  3:02 ` bugzilla-daemon
2014-04-11  3:11 ` bugzilla-daemon
2014-04-11  7:45 ` bugzilla-daemon
2014-04-11  8:57 ` bugzilla-daemon
2014-04-11  9:25 ` bugzilla-daemon
2014-04-11 11:17 ` bugzilla-daemon
2014-04-11 11:18 ` bugzilla-daemon
2014-04-11 11:58 ` bugzilla-daemon
2014-04-11 12:15 ` bugzilla-daemon
2014-04-11 22:10 ` bugzilla-daemon
2014-04-11 22:17 ` bugzilla-daemon
2014-04-11 22:32 ` bugzilla-daemon
2014-04-13  5:07 ` bugzilla-daemon
2014-04-13 13:03 ` bugzilla-daemon
2014-04-14  0:32 ` bugzilla-daemon
2014-05-08 16:23 ` bugzilla-daemon
2014-05-08 16:25 ` bugzilla-daemon
2014-05-14 11:30 ` bugzilla-daemon
2014-05-14 11:52 ` bugzilla-daemon
2014-05-14 21:36 ` bugzilla-daemon
2014-05-14 21:39 ` bugzilla-daemon
2014-05-14 21:45 ` bugzilla-daemon
2019-11-20  7:58 ` 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-75992-502-xeKgI0lYal@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.