dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66964] New: GPU fault detected
Date: Tue, 16 Jul 2013 14:12:23 +0000	[thread overview]
Message-ID: <bug-66964-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 66964
          Assignee: dri-devel@lists.freedesktop.org
           Summary: GPU fault detected
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: udovdh@xs4all.nl
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Hello,

See https://bugs.freedesktop.org/show_bug.cgi?id=62959 as reference.
I turned off RADEON_VA=0 and R600_DEBUG=nodma and after a while I got the
output below (and a reboot) while surfing the web, checking videos from
youtube, etc. I use git everything on A10-5800K which has ARUBA (Cayman) GPU
with kernel.org 3.9.9.
What is the cause? And how can we fix this?


Jul 16 16:00:01 surfplank2 kernel: [178650.498628] radeon 0000:00:01.0: GPU
fault detected: 147 0x0db67102
Jul 16 16:00:01 surfplank2 kernel: [178650.498633] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00001EDB
Jul 16 16:00:01 surfplank2 kernel: [178650.498635] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x06071002
Jul 16 16:00:01 surfplank2 kernel: [178650.498638] radeon 0000:00:01.0: GPU
fault detected: 147 0x0db67102
Jul 16 16:00:01 surfplank2 kernel: [178650.498640] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498643] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498645] radeon 0000:00:01.0: GPU
fault detected: 146 0x01f67104
Jul 16 16:00:01 surfplank2 kernel: [178650.498647] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498649] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498652] radeon 0000:00:01.0: GPU
fault detected: 146 0x02067104
Jul 16 16:00:01 surfplank2 kernel: [178650.498654] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498656] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498658] radeon 0000:00:01.0: GPU
fault detected: 146 0x02067104
Jul 16 16:00:01 surfplank2 kernel: [178650.498660] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498662] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498664] radeon 0000:00:01.0: GPU
fault detected: 147 0x03b67102
Jul 16 16:00:01 surfplank2 kernel: [178650.498667] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498669] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498671] radeon 0000:00:01.0: GPU
fault detected: 147 0x03c67102
Jul 16 16:00:01 surfplank2 kernel: [178650.498673] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498675] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498677] radeon 0000:00:01.0: GPU
fault detected: 147 0x03c67102
Jul 16 16:00:01 surfplank2 kernel: [178650.498679] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498681] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498683] radeon 0000:00:01.0: GPU
fault detected: 147 0x03c67102
Jul 16 16:00:01 surfplank2 kernel: [178650.498685] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498687] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498690] radeon 0000:00:01.0: GPU
fault detected: 146 0x02067104
Jul 16 16:00:01 surfplank2 kernel: [178650.498692] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498694] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x06071004
Jul 16 16:00:01 surfplank2 kernel: [178650.498711] radeon 0000:00:01.0: GPU
fault detected: 146 0x09767104
Jul 16 16:00:01 surfplank2 kernel: [178650.498713] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jul 16 16:00:01 surfplank2 kernel: [178650.498715] radeon 0000:00:01.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000

Kind regards,
Udo

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

[-- Attachment #1.2: Type: text/html, Size: 6222 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:[~2013-07-16 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 14:12 bugzilla-daemon [this message]
2013-07-16 15:24 ` [Bug 66964] GPU fault detected bugzilla-daemon
2013-07-16 15:25 ` [Bug 66964] GPU VM faults on ARUBA bugzilla-daemon
2019-09-18 19:04 ` 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-66964-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;
as well as URLs for NNTP newsgroup(s).