From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108781] 4.19 Regression - Hawaii (R9 390) boot failure - Invalid PCC GPIO / invalid powerlevel state / Fatal error during GPU init
Date: Wed, 21 Nov 2018 00:06:54 +0000 [thread overview]
Message-ID: <bug-108781-502-GY2nWnCOUB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108781-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1702 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #10 from jamespharvey20@gmail.com ---
Bisecting results are below.
This is an Asus model STRIX-R9390-DC3OC-8GD5-GAMING.
Don't think is relevant, oter than why someone was looking at this code, but
this commit immediately trails a bunch of the vkms commits, and the crash/to
black screen happens right when amdgpu is attempting to automatically switch to
kms.
0d99889109892396a8164bf6dd178e36d3fe3166 is the first bad commit
commit 0d99889109892396a8164bf6dd178e36d3fe3166
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date: Thu Jun 28 16:13:07 2018 +0300
drm/fb-helper: Eliminate the .best_encoder() usage
Instead of using the .best_encoder() hook to figure out whether a given
connector+crtc combo will work, let's instead do what userspace does and
just iterate over all the encoders for the connector, and then check
each crtc against each encoder's possible_crtcs bitmask.
v2: Avoid oopsing on NULL encoders (Daniel)
s/connector_crtc_ok/connector_has_possible_crtc/
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: Harry Wentland <harry.wentland@amd.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link:
https://patchwork.freedesktop.org/patch/msgid/20180628131315.14156-2-ville.syrjala@linux.intel.com
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3231 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-11-21 0:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 21:25 [Bug 108781] 4.19 Regression - Hawaii (R9 390) boot failure - Invalid PCC GPIO / invalid powerlevel state / Fatal error during GPU init bugzilla-daemon
2018-11-17 21:26 ` bugzilla-daemon
2018-11-17 21:26 ` bugzilla-daemon
2018-11-17 21:34 ` bugzilla-daemon
2018-11-19 15:01 ` bugzilla-daemon
2018-11-19 17:25 ` bugzilla-daemon
2018-11-20 2:26 ` bugzilla-daemon
2018-11-20 12:50 ` bugzilla-daemon
2018-11-20 14:35 ` bugzilla-daemon
2018-11-20 20:20 ` bugzilla-daemon
2018-11-21 0:06 ` bugzilla-daemon [this message]
2018-11-21 7:52 ` bugzilla-daemon
2018-11-21 9:48 ` bugzilla-daemon
2018-11-22 0:13 ` bugzilla-daemon
2018-11-22 0:15 ` bugzilla-daemon
2018-11-22 0:15 ` bugzilla-daemon
2018-11-22 0:48 ` bugzilla-daemon
2018-11-22 1:38 ` bugzilla-daemon
2018-11-22 17:01 ` bugzilla-daemon
2018-11-22 18:56 ` bugzilla-daemon
2018-11-23 9:42 ` bugzilla-daemon
2018-11-23 14:42 ` bugzilla-daemon
2018-11-23 21:46 ` bugzilla-daemon
2018-11-23 22:42 ` bugzilla-daemon
2018-11-23 22:43 ` bugzilla-daemon
2018-11-25 19:08 ` bugzilla-daemon
2018-11-27 17:11 ` bugzilla-daemon
2018-11-28 11:28 ` bugzilla-daemon
2018-11-28 11:45 ` bugzilla-daemon
2018-11-28 14:46 ` bugzilla-daemon
2018-12-02 6:34 ` bugzilla-daemon
2018-12-02 6:44 ` bugzilla-daemon
2018-12-02 15:53 ` bugzilla-daemon
2018-12-03 3:07 ` bugzilla-daemon
2018-12-03 13:16 ` bugzilla-daemon
2018-12-03 13:26 ` bugzilla-daemon
2018-12-30 22:55 ` bugzilla-daemon
2018-12-31 15:08 ` bugzilla-daemon
2019-01-05 13:28 ` bugzilla-daemon
2019-01-11 0:04 ` bugzilla-daemon
2019-11-19 9:04 ` 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-108781-502-GY2nWnCOUB@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