All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 04 Jul 2018 22:55:09 +0000	[thread overview]
Message-ID: <bug-107065-502-tYBLi1QyLd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107065-502@http.bugs.freedesktop.org/>


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

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

--- Comment #16 from dwagner <jb5sgc1n.nya@20mm.eu> ---
(In reply to Andrey Grodzovsky from comment #15)
> We have only minor differences but I can't reproduce it. Maybe the resume
> failure is indeed due the eviction failure during suspend. Is S3 failure is
> happening only when you switch to CPU update mode ?

No, when I boot amd-staging-drm-next with amdgpu.vm_update_mode=0
and suspend to S3 then resuming does also crash, but with different
messages - _not_ with
 "BUG: unable to handle kernel paging request at 0000000000002000"
like in the vm_update_mode=3 case.

In the journal, I can see see after a vm_update_mode=0 S3 resume attempt: 

Jul 05 00:41:59 ryzen kernel: [TTM] Buffer eviction failed
Jul 05 00:41:59 ryzen kernel: ACPI: Preparing to enter system sleep state S3
...
Jul 05 00:42:00 ryzen kernel: [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR*
amdgpu: ring 0 test failed (scratch(0xC040)=0xC>
Jul 05 00:42:00 ryzen kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]]
*ERROR* resume of IP block <gfx_v8_0> failed -22
Jul 05 00:42:00 ryzen kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR*
amdgpu_device_ip_resume failed (-22).
Jul 05 00:42:00 ryzen kernel: dpm_run_callback(): pci_pm_resume+0x0/0xa0
returns -22
Jul 05 00:42:00 ryzen kernel: PM: Device 0000:0a:00.0 failed to resume async:
error -22
...
Jul 05 00:42:00 ryzen kernel: amdgpu 0000:0a:00.0: couldn't schedule ib on ring
<sdma0>
Jul 05 00:42:00 ryzen kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error
scheduling IBs (-22)
Jul 05 00:42:00 ryzen kernel: amdgpu 0000:0a:00.0: couldn't schedule ib on ring
<sdma0>
Jul 05 00:42:00 ryzen kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error
scheduling IBs (-22)
Jul 05 00:42:00 ryzen kernel: amdgpu 0000:0a:00.0: couldn't schedule ib on ring
<sdma0>
Jul 05 00:42:00 ryzen kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error
scheduling IBs (-22)
Jul 05 00:42:00 ryzen kernel: amdgpu 0000:0a:00.0: couldn't schedule ib on ring
<sdma0>
... many more of this... but no kernel BUG or Oops.

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

[-- Attachment #1.2: Type: text/html, Size: 3237 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

  parent reply	other threads:[~2018-07-04 22:55 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 [this message]
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

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-tYBLi1QyLd@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.