From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 190971] New: amdgpu (on Kabini) fails to resume, atombios stuck executing BA98
Date: Fri, 23 Dec 2016 10:00:40 +0000 [thread overview]
Message-ID: <bug-190971-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=190971
Bug ID: 190971
Summary: amdgpu (on Kabini) fails to resume, atombios stuck
executing BA98
Product: Drivers
Version: 2.5
Kernel Version: 4.9
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: blade@debian.org
Regression: No
Created attachment 248421
--> https://bugzilla.kernel.org/attachment.cgi?id=248421&action=edit
Kernel messages
Hardware:
Lenovo Thinkpad Edge E145
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor
Root Complex
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Kabini [Radeon HD 8240 / R3 Series]
This system works fine with the Radeon driver. With amdgpu
and CONFIG_DRM_AMDGPU_CIK=y , it works until the next suspend-to-ram cycle.
Then the system comes up but the screen remains dark.
See attachment for kernel logs. The same thing happened earlier when I tested
AMDGPU with 4.8.x kernels.
--
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
next reply other threads:[~2016-12-23 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 10:00 bugzilla-daemon [this message]
2017-02-10 5:42 ` [Bug 190971] amdgpu (on Kabini) fails to resume, atombios stuck executing BA98 bugzilla-daemon
2019-01-25 17:23 ` 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-190971-2300@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.