All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107819] DRM radeon GPU fault detected (gem object lookup failed)
Date: Mon, 03 Sep 2018 17:43:03 +0000	[thread overview]
Message-ID: <bug-107819-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 107819
           Summary: DRM radeon GPU fault detected (gem object lookup
                    failed)
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: egdfree@opensuse.org

After plug two monitor i see this errors in dmesg (first monitor connected in
HDMI, second in DisplayPort):

kernel: [drm:radeon_cs_parser_relocs [radeon]] *ERROR* gem object lookup failed
0xa
kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to parse relocation -2!

kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ec35014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105B76
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03050014
kernel: VM fault (0x04, vmid 1) at page 1071990, write from CB (80)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0e835014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105B57
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014
kernel: VM fault (0x04, vmid 1) at page 1071959, write from CB (16)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ee36014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105C3E
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03020014
kernel: VM fault (0x04, vmid 1) at page 1072190, write from CB (32)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ec36014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105CC0
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014
kernel: VM fault (0x04, vmid 1) at page 1072320, write from CB (16)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ee35014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105D36
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060014
kernel: VM fault (0x04, vmid 1) at page 1072438, write from CB (96)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0e836014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105D9C
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03050014
kernel: VM fault (0x04, vmid 1) at page 1072540, write from CB (80)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ea35014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105E12
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014
kernel: VM fault (0x04, vmid 1) at page 1072658, write from CB (16)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x07435014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105B38
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014
kernel: VM fault (0x04, vmid 1) at page 1071928, write from CB (16)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x07035014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105BA3
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014
kernel: VM fault (0x04, vmid 1) at page 1072035, write from CB (16)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x07035014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105C26
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060014
kernel: VM fault (0x04, vmid 1) at page 1072166, write from CB (96)
kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x07236014
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105C23
kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03020014

installed:
kernel-default-4.18.5-1.6.x86_64
libdrm_radeon1-32bit-2.4.93-1.1.x86_64
libdrm_amdgpu1-2.4.93-1.1.x86_64
libdrm_nouveau2-2.4.93-1.1.x86_64
libva-drm2-2.2.0-1.1.x86_64
libdrm_nouveau2-32bit-2.4.93-1.1.x86_64
libdrm2-2.4.93-1.1.x86_64
libdrm_intel1-32bit-2.4.93-1.1.x86_64
libdrm_intel1-2.4.93-1.1.x86_64
libdrm_radeon1-2.4.93-1.1.x86_64
libdrm2-32bit-2.4.93-1.1.x86_64
libdrm_amdgpu1-32bit-2.4.93-1.1.x86_64
libdrm-devel-2.4.93-1.1.x86_64
Mesa-libGLESv2-2-18.1.6-207.1.x86_64
Mesa-dri-32bit-18.1.6-205.1.x86_64
libOSMesa8-18.1.6-207.1.x86_64
Mesa-libva-18.1.6-207.1.x86_64
Mesa-libEGL1-18.1.6-207.1.x86_64
Mesa-gallium-18.1.6-207.1.x86_64
Mesa-libEGL-devel-18.1.6-207.1.x86_64
Mesa-libEGL1-32bit-18.1.6-207.1.x86_64
Mesa-gallium-32bit-18.1.6-205.1.x86_64
Mesa-libGL1-18.1.6-207.1.x86_64
Mesa-libglapi0-18.1.6-207.1.x86_64
Mesa-libd3d-32bit-18.1.6-205.1.x86_64
Mesa-dri-18.1.6-207.1.x86_64
Mesa-libglapi0-32bit-18.1.6-207.1.x86_64
Mesa-libGL-devel-18.1.6-207.1.x86_64
Mesa-demo-x-8.4.0-1.3.x86_64
Mesa-libd3d-18.1.6-207.1.x86_64
Mesa-32bit-18.1.6-207.1.x86_64
libOSMesa8-32bit-18.1.6-207.1.x86_64
Mesa-libGL1-32bit-18.1.6-207.1.x86_64
Mesa-18.1.6-207.1.x86_64
xorg-x11-server-1.20.1-1.1.x86_64

hardware:
Radeon HD7770

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

[-- Attachment #1.2: Type: text/html, Size: 6570 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-09-03 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 17:43 bugzilla-daemon [this message]
2018-09-04  7:38 ` [Bug 107819] DRM radeon GPU fault detected (gem object lookup failed) 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-107819-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.