From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101387] amdgpu display corruption and hang on AMD A10-9620P
Date: Tue, 13 Jun 2017 07:49:53 +0000 [thread overview]
Message-ID: <bug-101387-502-qXEwJLeedJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101387-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1555 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #3 from Carlo Caione <carlo@caione.org> ---
> Looks like amdgpu_atombios_crtc_powergate_init scribbles over the stack.
Yeah, and while this is causing the panic this is not related to the display
corruption.
The garbage lines we see at boot seem to be displayed at the same time when in
the log we have:
[drm] amdgpu atom DIG backlight initialized
[drm] AMDGPU Display Connectors
[drm] Connector 0:
[drm] eDP-1
[drm] HPD1
[drm] DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b
[drm] Encoders:
[drm] LCD1: INTERNAL_UNIPHY
[drm] Connector 1:
[drm] HDMI-A-1
[drm] HPD2
[drm] DDC: 0x486c 0x486c 0x486d 0x486d 0x486e 0x486e 0x486f 0x486f
[drm] Encoders:
[drm] DFP1: INTERNAL_UNIPHY
[drm] amdgpu atom DIG backlight initialized
[drm] AMDGPU Display Connectors
[drm] Connector 0:
[drm] eDP-1
[drm] HPD1
[drm] DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b
[drm] Encoders:
[drm] LCD1: INTERNAL_UNIPHY
[drm] Connector 1:
[drm] HDMI-A-1
[drm] HPD2
[drm] DDC: 0x486c 0x486c 0x486d 0x486d 0x486e 0x486e 0x486f 0x486f
[drm] Encoders:
[drm] DFP1: INTERNAL_UNIPHY
> What kind of artifacts in plymouth?
https://pasteboard.co/hWu18yPj0.jpg
> Does e.g. X work correctly?
Yes, disabling the stack protection xorg works fine (no panic, but I still have
the display corruption at boot and on poweroff/reboot)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2482 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:[~2017-06-13 7:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 10:21 [Bug 101387] amdgpu display corruption and hang on AMD A10-9620P bugzilla-daemon
2017-06-12 11:13 ` 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 [this message]
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-qXEwJLeedJ@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).