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: Tue, 09 May 2017 21:11:06 +0000 [thread overview]
Message-ID: <bug-100979-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2040 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100979
Bug ID: 100979
Summary: Radeon r4 on a6-6310(BEEMA) APU hard lockup on
hibernate and on second resume from suspend
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: soprwa@gmail.com
I'm using kernel 4.11 on gentoo with SI/CIK enabled on Lenovo G50-45 Notebook.
Machine has AMD APU A6 6130 with Radeon r4 graphics card (Beema/Mullins). This
CPU supports olny AMD IOMMU v1. There is no discrete graphic card on it, APU
only.
When I try to hibernate this notebook it doesn't turning off. I have to press
power button to reboot the machine. Similar situation is on "radeon" driver,
and I had submitted bug report about this on kernel's bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=191571
But in this situation I'm unable to bisect because as I remember correctly
problem always occur on amdgpu driver, so I think those two can correlate with
each other. (dmesg form hibernation process attached).
As for suspend.
I can suspend/resume machine successfully only once in a row. Second time
machine suspends correctly, but on resume I have hard lockup, fans are spinning
on full rpm's and I cannot do anything but pressing power button to reboot(cold
boot) the netbook.
Moreover in dmesg after first suspend I've got error messages:
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status
failed
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Attachments:
1. Log after clean start.
2. Kernel's config file.
3. Log after hibernation process.
4. Log after first suspend/resume.
5. Log after second suspend/resume.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3432 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:[~2017-05-09 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 21:11 bugzilla-daemon [this message]
2017-05-09 21:12 ` [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: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
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@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).