All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108814] VMC page fault on POLARIS&RAVEN
Date: Tue, 20 Nov 2018 21:39:10 +0000	[thread overview]
Message-ID: <bug-108814-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 108814
           Summary: VMC page fault on POLARIS&RAVEN
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: domen.stangar@gmail.com

I tried it on two computers.


Linux (none) 4.20.0-rc1+ #8 SMP PREEMPT Tue Nov 20 00:24:49 CET 2018 x86_64 AMD
Athlon PRO 200GE w/ Radeon Vega Graphics AuthenticAMD GNU/Linux

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD RAVEN (DRM 3.27.0, 4.20.0-rc1+, LLVM 7.0.0) (0x15dd)
    Version: 18.2.5

[   80.221112] amdgpu 0000:38:00.0: [gfxhub] VMC page fault (src_id:0 ring:32
vmid:2 pasid:32768, for process roles pid 358 thread roles:cs0 pid 359)
[   80.221116] amdgpu 0000:38:00.0:   in page starting at address
0x0000800000a94000 from 27
[   80.221118] amdgpu 0000:38:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00240C40

Other computer.
Linux amd1.blue.org 4.19.2 #1 SMP PREEMPT Tue Nov 20 21:41:52 CET 2018 x86_64
AMD Ryzen 7 1700X Eight-Core Processor AuthenticAMD GNU/Linux

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.27.0, 4.19.2,
LLVM 7.0.0) (0x67ef)
    Version: 18.2.5

[ 1253.329906] amdgpu 0000:0e:00.0: GPU fault detected: 147 0x09004802 for
process roles pid 1119 thread roles:cs0 pid 1120
[ 1253.329910] amdgpu 0000:0e:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0000EB20
[ 1253.329911] amdgpu 0000:0e:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0C048002
[ 1253.329914] amdgpu 0000:0e:00.0: VM fault (0x02, vmid 6, pasid 32769) at
page 60192, read from 'TC0' (0x54433000) (72)

Is this llvm or mesa issue ?
I also tried older kernel 4.16 same thing.

What reports do you need ?

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

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

             reply	other threads:[~2018-11-20 21:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 21:39 bugzilla-daemon [this message]
2018-11-21 11:12 ` [Bug 108814] VMC page fault on POLARIS&RAVEN bugzilla-daemon
2018-11-21 11:13 ` bugzilla-daemon
2018-11-21 11:13 ` bugzilla-daemon
2018-11-21 11:14 ` bugzilla-daemon
2018-11-21 11:15 ` bugzilla-daemon
2018-11-23 17:37 ` bugzilla-daemon
2018-11-23 17:38 ` [Bug 108814] [radeonsi] page fault, umr dump bugzilla-daemon
2018-11-23 17:42 ` bugzilla-daemon
2018-11-25 14:13 ` bugzilla-daemon
2018-11-27  7:56 ` bugzilla-daemon
2018-11-27  7:58 ` bugzilla-daemon
2018-12-01  7:24 ` 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-108814-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 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.