From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107065] "BUG: unable to handle kernel paging request at 0000000000002000" in amdgpu_vm_cpu_set_ptes at amdgpu_vm.c:921
Date: Thu, 19 Jul 2018 16:42:26 +0000 [thread overview]
Message-ID: <bug-107065-502-ajLiGt5Ltu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107065-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107065
Andrey Grodzovsky <andrey.grodzovsky@amd.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|dri-devel@lists.freedesktop |andrey.grodzovsky@amd.com
|.org |
--- Comment #27 from Andrey Grodzovsky <andrey.grodzovsky@amd.com> ---
Created attachment 140715
--> https://bugs.freedesktop.org/attachment.cgi?id=140715&action=edit
0001-drm-amdgpu-Fix-S3-resume-failre.patch
Please try the attached patch for the S3 issue, it's might still not be the
final fix but still. It's not a fix for your CPU page table updates fault.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2619 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
prev parent reply other threads:[~2018-07-19 16:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 19:33 [Bug 107065] "BUG: unable to handle kernel paging request at 0000000000002000" at amdgpu_vm_cpu_set_ptes at S3 resume bugzilla-daemon
2018-06-28 19:42 ` bugzilla-daemon
2018-06-28 19:52 ` bugzilla-daemon
2018-06-28 20:49 ` bugzilla-daemon
2018-06-28 22:50 ` bugzilla-daemon
2018-06-29 0:37 ` bugzilla-daemon
2018-06-29 16:16 ` bugzilla-daemon
2018-06-29 19:10 ` bugzilla-daemon
2018-06-29 19:10 ` [Bug 107065] "BUG: unable to handle kernel paging request at 0000000000002000" in amdgpu_vm_cpu_set_ptes at amdgpu_vm.c:921 bugzilla-daemon
2018-06-29 19:17 ` bugzilla-daemon
2018-06-29 19:21 ` bugzilla-daemon
2018-07-02 3:11 ` bugzilla-daemon
2018-07-02 11:03 ` bugzilla-daemon
2018-07-02 19:48 ` bugzilla-daemon
2018-07-02 22:55 ` bugzilla-daemon
2018-07-03 20:42 ` bugzilla-daemon
2018-07-03 22:58 ` bugzilla-daemon
2018-07-04 22:55 ` bugzilla-daemon
2018-07-06 23:03 ` bugzilla-daemon
2018-07-09 18:16 ` bugzilla-daemon
2018-07-11 22:04 ` bugzilla-daemon
2018-07-11 22:23 ` bugzilla-daemon
2018-07-13 21:01 ` bugzilla-daemon
2018-07-13 23:45 ` bugzilla-daemon
2018-07-14 4:28 ` bugzilla-daemon
2018-07-14 13:15 ` bugzilla-daemon
2018-07-14 13:16 ` bugzilla-daemon
2018-07-16 13:52 ` bugzilla-daemon
2018-07-19 16:42 ` bugzilla-daemon [this message]
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-107065-502-ajLiGt5Ltu@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;
as well as URLs for NNTP newsgroup(s).