dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84614] New: radeon gpu crash /kernel crash when using dynamic light in borderlands 2
Date: Fri, 03 Oct 2014 00:37:22 +0000	[thread overview]
Message-ID: <bug-84614-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 84614
           Summary: radeon gpu crash /kernel crash when using dynamic
                    light in borderlands 2
           Product: DRI
           Version: DRI CVS
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: paulo.miguel.dias@gmail.com

if i activate dynamic light in borderlands 2, it works and it quite beautiful,
that is , till i start running with my char. then the kernel/gpu crashes with a
lot of:

Oct  2 21:14:40 kerberos kernel: [  717.282422] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a820801
Oct  2 21:14:40 kerberos kernel: [  717.282429] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00854
Oct  2 21:14:40 kerberos kernel: [  717.282432] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:40 kerberos kernel: [  717.282435] VM fault (0x01, vmid 1) at page
196085844, read from TC (8)
Oct  2 21:14:40 kerberos kernel: [  717.358511] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a420801
Oct  2 21:14:40 kerberos kernel: [  717.358518] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00852
Oct  2 21:14:40 kerberos kernel: [  717.358520] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:40 kerberos kernel: [  717.358523] VM fault (0x01, vmid 1) at page
196085842, read from TC (8)
Oct  2 21:14:40 kerberos kernel: [  717.808432] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a420801
Oct  2 21:14:40 kerberos kernel: [  717.808439] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00852
Oct  2 21:14:40 kerberos kernel: [  717.808441] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:40 kerberos kernel: [  717.808444] VM fault (0x01, vmid 1) at page
196085842, read from TC (8)
Oct  2 21:14:40 kerberos kernel: [  717.897558] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a420801
Oct  2 21:14:40 kerberos kernel: [  717.897564] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00852
Oct  2 21:14:40 kerberos kernel: [  717.897566] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:40 kerberos kernel: [  717.897568] VM fault (0x01, vmid 1) at page
196085842, read from TC (8)
Oct  2 21:14:40 kerberos kernel: [  717.897610] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a420801
Oct  2 21:14:40 kerberos kernel: [  717.897612] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00852
Oct  2 21:14:40 kerberos kernel: [  717.897614] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:40 kerberos kernel: [  717.897616] VM fault (0x01, vmid 1) at page
196085842, read from TC (8)
Oct  2 21:14:42 kerberos kernel: [  719.466784] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a420801
Oct  2 21:14:42 kerberos kernel: [  719.466790] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00852
Oct  2 21:14:42 kerberos kernel: [  719.466793] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:42 kerberos kernel: [  719.466796] VM fault (0x01, vmid 1) at page
196085842, read from TC (8)
Oct  2 21:14:42 kerberos kernel: [  719.466822] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a420801
Oct  2 21:14:42 kerberos kernel: [  719.466824] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00852
Oct  2 21:14:42 kerberos kernel: [  719.466827] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:42 kerberos kernel: [  719.466829] VM fault (0x01, vmid 1) at page
196085842, read from TC (8)
Oct  2 21:14:42 kerberos kernel: [  719.635386] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a620801
Oct  2 21:14:42 kerberos kernel: [  719.635393] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00853
Oct  2 21:14:42 kerberos kernel: [  719.635395] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:42 kerberos kernel: [  719.635398] VM fault (0x01, vmid 1) at page
196085843, read from TC (8)
Oct  2 21:14:42 kerberos kernel: [  719.635416] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a820801
Oct  2 21:14:42 kerberos kernel: [  719.635418] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00854
Oct  2 21:14:42 kerberos kernel: [  719.635420] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:42 kerberos kernel: [  719.635421] VM fault (0x01, vmid 1) at page
196085844, read from TC (8)
Oct  2 21:14:42 kerberos kernel: [  719.975165] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a420801
Oct  2 21:14:42 kerberos kernel: [  719.975172] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00852
Oct  2 21:14:42 kerberos kernel: [  719.975175] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Oct  2 21:14:42 kerberos kernel: [  719.975178] VM fault (0x01, vmid 1) at page
196085842, read from TC (8)
Oct  2 21:14:42 kerberos kernel: [  719.975227] radeon 0000:03:00.0: GPU fault
detected: 147 0x0a420801
Oct  2 21:14:42 kerberos kernel: [  719.975230] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0BB00852
Oct  2 21:14:42 kerberos kernel: [  719.975232] radeon 0000:03:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001

llvm 5.2, kernel 3.17 rc7, latest microcode, mesa 10.4 git from oibaf ppa, same
for radeon driver.

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

[-- Attachment #1.2: Type: text/html, Size: 6915 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

             reply	other threads:[~2014-10-03  0:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03  0:37 bugzilla-daemon [this message]
2014-10-03  1:01 ` [Bug 84614] radeon gpu crash /kernel crash when using dynamic light in borderlands 2 bugzilla-daemon
2014-10-03  3:48 ` bugzilla-daemon
2014-10-04  9:22 ` bugzilla-daemon
2014-10-06  6:54 ` bugzilla-daemon
2014-10-06 16:46 ` bugzilla-daemon
2014-10-07  1:45 ` bugzilla-daemon
2014-10-07 15:13 ` bugzilla-daemon
2014-10-08  0:46 ` bugzilla-daemon
2014-10-08  0:47 ` bugzilla-daemon
2014-10-08  1:04 ` bugzilla-daemon
2014-10-10  5:05 ` bugzilla-daemon
2014-10-10  5:19 ` bugzilla-daemon
2014-10-10  8:26 ` bugzilla-daemon
2014-10-10 10:17 ` bugzilla-daemon
2014-10-10 16:30 ` bugzilla-daemon
2014-10-10 19:00 ` bugzilla-daemon
2014-10-11 20:36 ` bugzilla-daemon
2014-10-14  3:07 ` bugzilla-daemon
2015-08-24 22:17 ` bugzilla-daemon
2015-08-26 14:08 ` bugzilla-daemon
2015-08-28 15:26 ` 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-84614-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox