From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108685] Raven Ridge: VMC page fault on resume from suspend
Date: Wed, 07 Nov 2018 05:22:49 +0000 [thread overview]
Message-ID: <bug-108685-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4836 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108685
Bug ID: 108685
Summary: Raven Ridge: VMC page fault on resume from suspend
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: samantham@posteo.net
Created attachment 142395
--> https://bugs.freedesktop.org/attachment.cgi?id=142395&action=edit
kernel log with lockup on resume
This is using 4.20.0-rc1-2.g0587eb8. I believe this is the issue I have had in
the past where the system does not resume from suspend, or at least the
graphics are locked up when I do.
I am able to fix these resume from suspend gpu lockups by using a script to
disable C6 states on the CPU before suspend and then enabling C6 states on
resume (this uses zenstates.py to set MSR through a systemd sleep script).
Nov 06 20:26:29 kernel: gmc_v9_0_process_interrupt: 35 callbacks suppressed
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200135
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200135
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200135
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200134
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200134
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200134
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200134
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200134
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200134
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: [mmhub] VMC page fault (src_id:0
ring:154 vmid:2 pasid:32771, for process kwin_x11 pid 2792 thread amdgpu_cs:0
pid 2906)
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0: in page starting at address
0x0000800100aaa000 from 18
Nov 06 20:26:29 kernel: amdgpu 0000:05:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00200134
Nov 06 20:26:29 kernel: PM: suspend exit
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6290 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
next reply other threads:[~2018-11-07 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 5:22 bugzilla-daemon [this message]
2018-11-30 3:22 ` [Bug 108685] Raven Ridge: VMC page fault on resume from suspend 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-108685-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.