From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198123] Console is the wrong color at boot with radeon 6670
Date: Tue, 12 Dec 2017 23:48:51 +0000 [thread overview]
Message-ID: <bug-198123-2300-JdIYKRmvZc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198123-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198123
--- Comment #6 from Felix Schwarz (felix.schwarz@oss.schwarz.eu) ---
Ideally you use Linus' git repo:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
As you mentioned in your first post you experienced problems when upgrading
from 4.13.16 -> 4.14.3 so most likely something changed in the main development
period of 4.14 for you. The merge commit 2040c473 you found supports that
theory.
Now you need to start actually bisecting. Just google for "git bisect". There
is a lot of blog posts, tutorials etc for it. (Maybe
https://stackoverflow.com/a/4714297/138526 helps you)
As a start you can mark the merge commit and its predecessor as bad/good and
git will take you from there. You will need to compile quite a few kernels and
test them (way more than 2, usually 10-20 kernels).
A common mistake is to mark a non-bootable or otherwise broken version as
"bad". Only mark kernels as "bad" if they clearly have the problem you
described in your report. If you can't test a specific version, use "git bisect
skip". Use "good" if you are sure that a version is ok.
Oh, btw: I recommend testing the most recent 4.15 rc (or even git master) to
check the problem is still present. If it is fixed in a the current development
version probably the easiest way for you is to ride the leading edge. Of course
you can bisect anyway, maybe the patch can be backported to 4.14.
Happy compiling.
--
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 prev parent reply other threads:[~2017-12-12 23:48 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 16:53 [Bug 198123] New: Console is the wrong color at boot with radeon 6670 bugzilla-daemon
2017-12-11 3:56 ` [Bug 198123] " bugzilla-daemon
2017-12-11 23:31 ` bugzilla-daemon
2017-12-12 23:11 ` bugzilla-daemon
2017-12-12 23:26 ` bugzilla-daemon
2017-12-12 23:33 ` bugzilla-daemon
2017-12-12 23:48 ` bugzilla-daemon [this message]
2017-12-13 0:59 ` bugzilla-daemon
2017-12-16 1:41 ` bugzilla-daemon
2017-12-18 11:37 ` Michel Dänzer
2017-12-18 13:50 ` Peter Rosin
2017-12-19 10:48 ` Michel Dänzer
2017-12-22 15:34 ` Michel Dänzer
2018-01-07 19:14 ` Deposite Pirate
2018-01-10 12:15 ` Daniel Vetter
2018-01-11 8:57 ` Daniel Vetter
2018-01-11 9:09 ` Michel Dänzer
2017-12-28 9:35 ` bugzilla-daemon
2018-01-11 10:11 ` bugzilla-daemon
2018-01-12 8:46 ` bugzilla-daemon
2018-01-12 9:50 ` bugzilla-daemon
2018-01-12 21:12 ` bugzilla-daemon
2018-01-13 6:50 ` bugzilla-daemon
2018-01-13 13:34 ` bugzilla-daemon
2018-01-14 18:32 ` bugzilla-daemon
2018-01-14 20:40 ` bugzilla-daemon
2018-01-16 16:54 ` bugzilla-daemon
2018-01-17 13:48 ` bugzilla-daemon
2018-01-18 5:15 ` bugzilla-daemon
2018-01-22 8:39 ` bugzilla-daemon
2018-01-22 8:40 ` bugzilla-daemon
2018-01-26 6:50 ` bugzilla-daemon
2018-01-26 17:54 ` bugzilla-daemon
2018-01-28 22:55 ` bugzilla-daemon
2018-01-31 10:36 ` bugzilla-daemon
2018-01-31 10:44 ` bugzilla-daemon
2018-01-31 11:14 ` bugzilla-daemon
2018-02-01 15:39 ` bugzilla-daemon
2018-02-19 8:20 ` bugzilla-daemon
2018-02-19 8:35 ` bugzilla-daemon
2018-02-19 15:19 ` bugzilla-daemon
2018-02-26 2:57 ` bugzilla-daemon
2018-02-26 2:59 ` bugzilla-daemon
2018-03-13 18:53 ` bugzilla-daemon
2018-03-14 9:10 ` bugzilla-daemon
2018-03-14 23:48 ` bugzilla-daemon
2018-03-15 9:20 ` bugzilla-daemon
2018-03-15 22:18 ` bugzilla-daemon
2018-03-16 9:29 ` bugzilla-daemon
2018-03-16 19:20 ` bugzilla-daemon
2018-03-17 18:57 ` bugzilla-daemon
2018-03-18 14:33 ` bugzilla-daemon
2018-03-19 9:40 ` bugzilla-daemon
2018-03-19 9:43 ` bugzilla-daemon
2018-03-19 13:55 ` bugzilla-daemon
2018-03-20 4:37 ` bugzilla-daemon
2018-03-20 6:03 ` bugzilla-daemon
2018-08-09 7:39 ` bugzilla-daemon
2018-09-05 13:59 ` bugzilla-daemon
2018-11-26 18:21 ` bugzilla-daemon
2019-03-05 1:12 ` bugzilla-daemon
2023-10-01 21:32 ` 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-198123-2300-JdIYKRmvZc@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 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).