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 95517] Constant GPU VM faults
Date: Thu, 20 Dec 2018 16:20:45 +0000	[thread overview]
Message-ID: <bug-95517-502-GLDBU12LGv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95517-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from Dima <mihailov-d-v@mail.ru> ---
I don't know if it's relevant or not, due my using amdgpu-pro driver, but I get
this massages sometime:
[14849.076326] gmc_v8_0_process_interrupt: 165 callbacks suppressed
[14849.076331] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[14849.076336] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001152FF
[14849.076338] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A07700C
[14849.076341] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 5, pasid 32770) at
page 1135359, read from 'SDM0' (0x53444d30) (119)
[14851.218731] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[14851.218736] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001152FF
[14851.218738] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0C07700C
[14851.218741] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 6, pasid 32770) at
page 1135359, read from 'SDM0' (0x53444d30) (119)
[14860.154325] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[14860.154330] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001152FF
[14860.154331] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0407700C
[14860.154334] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 2, pasid 32770) at
page 1135359, read from 'SDM0' (0x53444d30) (119)
[15073.787603] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[15073.787608] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001152FF
[15073.787610] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0C07700C
[15073.787612] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 6, pasid 32770) at
page 1135359, read from 'SDM0' (0x53444d30) (119)
[15095.908340] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[15095.908345] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001152FF
[15095.908347] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0607700C
[15095.908350] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 3, pasid 32770) at
page 1135359, read from 'SDM0' (0x53444d30) (119)
[15197.968706] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0cf8770c
[15197.968711] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0011D39F
[15197.968713] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A07700C
[15197.968715] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 5, pasid 32770) at
page 1168287, read from 'SDM0' (0x53444d30) (119)
[15710.487271] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[15710.487275] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001094FF
[15710.487277] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A07700C
[15710.487279] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 5, pasid 32770) at
page 1086719, read from 'SDM0' (0x53444d30) (119)
[15759.495971] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[15759.495978] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001094FF
[15759.495981] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0807700C
[15759.495985] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 4, pasid 32770) at
page 1086719, read from 'SDM0' (0x53444d30) (119)
[15768.854519] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[15768.854525] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001094FF
[15768.854526] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A07700C
[15768.854529] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 5, pasid 32770) at
page 1086719, read from 'SDM0' (0x53444d30) (119)
[15818.316441] amdgpu 0000:01:00.0: GPU fault detected: 146 0x07f8770c
[15818.316447] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001094FF
[15818.316448] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0207700C
[15818.316451] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 1, pasid 32770) at
page 1086719, read from 'SDM0' (0x53444d30) (119)

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

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

  parent reply	other threads:[~2018-12-20 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-95517-502@http.bugs.freedesktop.org/>
2016-05-24  6:49 ` [Bug 95517] Constant GPU VM faults bugzilla-daemon
2016-05-24 15:04 ` bugzilla-daemon
2016-05-25 23:11 ` bugzilla-daemon
2016-05-27 14:11 ` bugzilla-daemon
2016-05-27 19:31 ` bugzilla-daemon
2016-06-07 20:02 ` bugzilla-daemon
2016-08-23 23:14 ` bugzilla-daemon
2016-08-24 21:47 ` bugzilla-daemon
2018-09-20  1:30 ` bugzilla-daemon
2018-12-20 16:20 ` bugzilla-daemon [this message]
2019-01-14 22:41 ` bugzilla-daemon
2019-09-25 17:54 ` 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-95517-502-GLDBU12LGv@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