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 104192] [amdgpu][VEGA10] regular lockups with VM_L2_PROTECTION_FAULT_STATUS
Date: Sun, 10 Dec 2017 13:13:56 +0000	[thread overview]
Message-ID: <bug-104192-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 104192
           Summary: [amdgpu][VEGA10] regular lockups with
                    VM_L2_PROTECTION_FAULT_STATUS
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: tomenglund26@gmail.com

i have been having somewhat unreproduceable lockups with my rx 56 vega all
going from 4.12 amd-staging up until 4.15-rc2 where its mainlined. but for some
reason i can reproduce it now with simply just open pavucontrol, and weirdly
enough only that.

i can properly play games, dirt rally, cs:go, run benchmarks or just leave the
computer on for days. but as fast as i open pavucontrol it lockups and this
happends in dmesg. and i dont seem to be all alone with it either, here is a
user with a rx 64 vega on archlinux having same issue/errors. 
https://bbs.archlinux.org/viewtopic.php?id=232519


amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu 0000:03:00.0:   at page 0x0000000000000000 from 27
amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:171 vm_id:4
pas_id:0)

System info:
Radeon RX Vega (VEGA10 / DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
Mesa 17.4.0-devel (git-4c7af87fb9)

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

[-- Attachment #1.2: Type: text/html, Size: 2903 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:[~2017-12-10 13:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 13:13 bugzilla-daemon [this message]
2017-12-10 19:17 ` [Bug 104192] [amdgpu][VEGA10] regular lockups with VM_L2_PROTECTION_FAULT_STATUS bugzilla-daemon
2017-12-10 22:58 ` bugzilla-daemon
2017-12-10 23:01 ` bugzilla-daemon
2017-12-10 23:16 ` bugzilla-daemon
2017-12-11  6:10 ` bugzilla-daemon
2017-12-11  7:16 ` bugzilla-daemon
2017-12-11  7:39 ` bugzilla-daemon
2017-12-11  7:54 ` bugzilla-daemon
2017-12-11 10:48 ` bugzilla-daemon
2017-12-11 12:52 ` bugzilla-daemon
2017-12-11 13:22 ` bugzilla-daemon
2017-12-12 16:57 ` bugzilla-daemon
2017-12-12 18:17 ` 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-104192-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