All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204611] amdgpu error scheduling IBs when waking from sleep
Date: Mon, 16 Sep 2019 00:44:28 +0000	[thread overview]
Message-ID: <bug-204611-2300-rmJfnsOIZs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204611-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204611

--- Comment #3 from tones111@hotmail.com ---
I'm still working on trying to bisect the problem, but it's been challenging. 
Following the advice at
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
I turned on the initcall_debug and no_console_suspend boot options.

I then see the following messages in the boot log after bringing the system
back up.

> Sep 15 17:36:39 mobile kernel: [drm] reserve 0x400000 from 0xf400c00000 for
> PSP TMR SIZE
> ...
> Sep 15 17:36:39 mobile kernel: [drm] psp command failed and response status
> is (0)
> Sep 15 17:36:39 mobile kernel: [drm:psp_hw_start [amdgpu]] *ERROR* PSP load
> tmr failed!
> Sep 15 17:36:39 mobile kernel: [drm:psp_resume [amdgpu]] *ERROR* PSP resume
> failed
> Sep 15 17:36:39 mobile kernel: [drm:amdgpu_device_fw_loading [amdgpu]]
> *ERROR* resume of IP block <psp> failed -22
> Sep 15 17:36:39 mobile kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR*
> amdgpu_device_ip_resume failed (-22).
> Sep 15 17:36:39 mobile kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x90
> returns -22
> Sep 15 17:36:39 mobile kernel: amdgpu 0000:05:00.0: pci_pm_resume+0x0/0x90
> returned -22 after 19543535 usecs
> Sep 15 17:36:39 mobile kernel: PM: Device 0000:05:00.0 failed to resume
> async: error -22

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-09-16  0:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18 20:32 [Bug 204611] New: amdgpu error scheduling IBs when waking from sleep bugzilla-daemon
2019-08-24  0:33 ` [Bug 204611] " bugzilla-daemon
2019-08-26  3:16 ` bugzilla-daemon
2019-08-26 23:47 ` bugzilla-daemon
2019-09-16  0:44 ` bugzilla-daemon [this message]
2019-10-02  1:13 ` bugzilla-daemon
2019-10-06 13:20 ` bugzilla-daemon
2019-10-06 13:21 ` bugzilla-daemon
2020-04-08 14:52 ` bugzilla-daemon
2020-05-22 21:09 ` bugzilla-daemon
2020-05-24 11:41 ` bugzilla-daemon
2020-05-24 17:19 ` bugzilla-daemon
2020-06-14 18:27 ` bugzilla-daemon
2022-01-29 19:55 ` bugzilla-daemon
2022-01-29 19:59 ` bugzilla-daemon
2022-01-30  2:39 ` 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-204611-2300-rmJfnsOIZs@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.