All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103100] Image corruptions, instability and performance regression in drm-next-wip Kernel
Date: Wed, 04 Oct 2017 16:38:21 +0000	[thread overview]
Message-ID: <bug-103100-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 103100
           Summary: Image corruptions, instability and performance
                    regression in drm-next-wip Kernel
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: gr.muench@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Im running current drm-next-4.15-wip Kernel and I use AMDGPU with Radeon HD
7970
DC disabled.

The following is wrong:
-Performance in Shadow of Mordor internal benchmark decreases from 68 to 61 fps
-also other games see a small decrease of 1-2 fps
-I see random screen corruptions on my desktop
-after I exit from a game, the system is unstable, screen corruptions are even
more visible and the systems randomly hangs 

I bisected this to:
fd8bf087dffc0bce047c5aea2afcb8f821e48db1 is the first bad commit
commit fd8bf087dffc0bce047c5aea2afcb8f821e48db1
Author: Christian König <christian.koenig@amd.com>
Date:   Tue Aug 29 16:14:32 2017 +0200

    drm/amdgpu: bump version for support of local BOs

    Signed-off-by: Christian König <christian.koenig@amd.com>
    Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

:040000 040000 440c9b026e802e50b6a25ae3b402ea57ef58a891
d31d8e8b93060b11e88f95d4d3bdcf081c77e4e2 M      drivers

This is probably not making any sense, I guess one of the previous commits
related to BOs are faulty. To double checked things I used git checkout between
those commits and make clean during the steps. Its still very unusual but maybe
a dev know whats going on.

log:

amdgpu 0000:01:00.0: GPU fault detected: 146 0x030f3d14
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0010CD18
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0F03D014
kernel: amdgpu 0000:01:00.0: VM fault (0x14, vmid 7) at page 1101080, write
from '' (0x00000000) (61)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f073d14
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0010E178
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0703D014
kernel: amdgpu 0000:01:00.0: VM fault (0x14, vmid 3) at page 1106296, write
from '' (0x00000000) (61)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x0e0a3d0c
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0010E670
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A03D00C
kernel: amdgpu 0000:01:00.0: VM fault (0x0c, vmid 5) at page 1107568, read from
'' (0x00000000) (61)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x0e0a3d0c
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0010E673
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A03D00C
kernel: amdgpu 0000:01:00.0: VM fault (0x0c, vmid 5) at page 1107571, read from
'' (0x00000000) (61)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x0e0e440c
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00104670
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E04400C
kernel: amdgpu 0000:01:00.0: VM fault (0x0c, vmid 7) at page 1066608, read from
'' (0x00000000) (68)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x0c0f3d14
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00101960
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0F03D014
kernel: amdgpu 0000:01:00.0: VM fault (0x14, vmid 7) at page 1055072, write
from '' (0x00000000) (61)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x0e0b3d14
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001017F0
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0B03D014
kernel: amdgpu 0000:01:00.0: VM fault (0x14, vmid 5) at page 1054704, write
from '' (0x00000000) (61)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x02073d14
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00112F90
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0703D014
kernel: amdgpu 0000:01:00.0: VM fault (0x14, vmid 3) at page 1126288, write
from '' (0x00000000) (61)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x08073d14
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00110E40
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0703D014
kernel: amdgpu 0000:01:00.0: VM fault (0x14, vmid 3) at page 1117760, write
from '' (0x00000000) (61)

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

[-- Attachment #1.2: Type: text/html, Size: 6515 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-10-04 16:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 16:38 bugzilla-daemon [this message]
2017-10-12  6:52 ` [Bug 103100] Image corruptions, instability and performance regression in drm-next-wip Kernel bugzilla-daemon
2017-10-15 18:57 ` bugzilla-daemon
2017-11-21 20:35 ` [Bug 103100] Performance regression with various games in drm-next-amd-staging Kernel bugzilla-daemon
2017-11-22 10:40 ` bugzilla-daemon
2017-11-22 11:42 ` bugzilla-daemon
2017-11-22 11:56 ` bugzilla-daemon
2017-11-22 20:58 ` bugzilla-daemon
2017-11-22 20:59 ` bugzilla-daemon
2017-11-22 21:02 ` bugzilla-daemon
2017-12-02 19:32 ` bugzilla-daemon
2017-12-12 13:02 ` bugzilla-daemon
2017-12-12 19:51 ` 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-103100-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.