From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101387] amdgpu display corruption and hang on AMD A10-9620P
Date: Mon, 12 Jun 2017 10:21:41 +0000 [thread overview]
Message-ID: <bug-101387-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1308 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101387
Bug ID: 101387
Summary: amdgpu display corruption and hang on AMD A10-9620P
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: carlo@caione.org
Created attachment 131886
--> https://bugs.freedesktop.org/attachment.cgi?id=131886&action=edit
Trace/freeze on amdgpu modprobing
As reported by Daniel Drake in [0]
We are working with new laptops that have the AMD Bristol Ridge
chipset with this SoC:
AMD A10-9620P RADEON R5, 10 COMPUTE CORES 4C+6G
I think this is the Bristol Ridge chipset.
During boot, the display becomes unusable at the point where the
amdgpu driver loads. You can see at least two horizontal lines of
garbage at this point. We have reproduced on 4.8, 4.10 and linus
master (early 4.12).
Photo: http://pasteboard.co/qrC9mh4p.jpg
In attachment the log taken using netconsole on amdgpu modprobing.
[0] http://www.spinics.net/lists/dri-devel/msg140915.html
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2881 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-06-12 10:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 10:21 bugzilla-daemon [this message]
2017-06-12 11:13 ` [Bug 101387] amdgpu display corruption and hang on AMD A10-9620P bugzilla-daemon
2017-06-13 2:27 ` bugzilla-daemon
2017-06-13 2:27 ` bugzilla-daemon
2017-06-13 2:33 ` bugzilla-daemon
2017-06-13 7:49 ` bugzilla-daemon
2017-06-13 8:44 ` bugzilla-daemon
2017-06-13 8:49 ` bugzilla-daemon
2017-06-13 11:35 ` bugzilla-daemon
2017-06-13 13:13 ` bugzilla-daemon
2017-06-14 11:59 ` bugzilla-daemon
2017-06-15 14:44 ` bugzilla-daemon
2017-06-15 15:03 ` bugzilla-daemon
2017-06-15 15:17 ` bugzilla-daemon
2017-06-15 15:32 ` bugzilla-daemon
2017-06-15 15:40 ` bugzilla-daemon
2017-06-15 16:35 ` bugzilla-daemon
2017-06-15 16:59 ` bugzilla-daemon
2017-06-15 18:17 ` bugzilla-daemon
2017-06-15 18:40 ` bugzilla-daemon
2017-06-15 21:51 ` bugzilla-daemon
2017-06-16 14:43 ` bugzilla-daemon
2017-06-20 17:47 ` bugzilla-daemon
2017-06-21 1:08 ` bugzilla-daemon
2017-06-21 6:26 ` bugzilla-daemon
2017-06-21 6:49 ` bugzilla-daemon
2017-06-21 9:26 ` bugzilla-daemon
2017-06-22 8:27 ` bugzilla-daemon
2019-11-19 8:19 ` 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-101387-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).