From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100979] Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend
Date: Wed, 28 Mar 2018 10:54:14 +0000 [thread overview]
Message-ID: <bug-100979-502-l47PScSiDw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100979-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1887 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100979
--- Comment #13 from Przemek <soprwa@gmail.com> ---
Using the opportunity that I was working on another bug report with AMD DC
kernel driver, and have git cloned agd5f drm-next-4.17-wip branch, I have tried
to debug the situation on hibernate process with this experimental kernel also.
This time hibernation image is created, and laptop turns off after that.
But - during the hibernation process screen goes totally white, process take
approximately 15-20 seconds on ssd drive before netbook gets power-off.
During resume hibernation image is read (it is possible to see percentage) and
then screen goes white, and machine is in a locked-up state. I can do nothing
but press power button to hard-reset the netbook.
Moreover I foud only once an error message in kernel log:
"Mar 28 01:36:54 eclipse kernel: [ 86.665473]
[drm:drm_atomic_helper_wait_for_flip_done] *ERROR* [CRTC:39:crtc-0] flip_done
timed out
Mar 28 01:36:54 eclipse kernel: [ 86.828685] [drm:gfx_v7_0_ring_test_ring]
*ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD)
Mar 28 01:36:54 eclipse kernel: [ 86.828698]
[drm:amdgpu_device_ip_resume_phase2] *ERROR* resume of IP block <gfx_v7_0>
failed -22
Mar 28 01:36:54 eclipse kernel: [ 86.828703] [drm:amdgpu_device_resume]
*ERROR* amdgpu_device_ip_resume failed (-22).
Mar 28 01:36:54 eclipse kernel: [ 86.828718] dpm_run_callback():
pci_pm_restore+0x0/0xa0 returns -22
Mar 28 01:36:54 eclipse kernel: [ 86.828742] PM: Device 0000:00:01.0 failed
to restore async: error -22"
of course I am unable to reproduce it. I am not sure how much it is related but
this could be usefull, tough.
Kernel was booted up with amdgpu.dc=1.
Any help is appreciated.
Thanks,
Przemek.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2761 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 prev parent reply other threads:[~2018-03-28 10:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 21:11 [Bug 100979] Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend bugzilla-daemon
2017-05-09 21:12 ` bugzilla-daemon
2017-05-09 21:13 ` bugzilla-daemon
2017-05-09 21:14 ` bugzilla-daemon
2017-05-09 21:15 ` bugzilla-daemon
2017-05-09 21:17 ` bugzilla-daemon
2017-06-02 15:33 ` bugzilla-daemon
2017-06-28 8:58 ` bugzilla-daemon
2017-07-03 16:07 ` bugzilla-daemon
2018-01-31 10:55 ` bugzilla-daemon
2018-01-31 11:29 ` bugzilla-daemon
2018-01-31 12:12 ` bugzilla-daemon
2018-02-06 23:30 ` bugzilla-daemon
2018-03-28 10:54 ` bugzilla-daemon [this message]
2019-02-15 15:10 ` bugzilla-daemon
2019-02-16 9:20 ` 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-100979-502-l47PScSiDw@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).