From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103271] AMD R9 270X Flickering with DPM Enabled on Linux 4.1 with RadeonSI
Date: Sun, 06 Sep 2015 13:58:34 +0000 [thread overview]
Message-ID: <bug-103271-2300-uz0l4ZXZa9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-103271-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=103271
--- Comment #11 from Kevin McCormack <wittyman37@yahoo.com> ---
OK, so good news and bad news...the good news is that I finished the bisect and
seem to have definitely found a bad commit. However, the bad news is that when
I run this compiled kernel I can't even boot. I just get a black screen with no
response from caps lock or ctr+alt+F4. Here is the log...
$ git bisect log
git bisect start
# good: [39a8804455fb23f09157341d3ba7db6d7ae6ee76] Linux 4.0
git bisect good 39a8804455fb23f09157341d3ba7db6d7ae6ee76
# bad: [b953c0d234bc72e8489d3bf51a276c5c4ec85345] Linux 4.1
git bisect bad b953c0d234bc72e8489d3bf51a276c5c4ec85345
# bad: [c13dcf9f2d6f5f06ef1bf79ec456df614c5e058b] Linux 4.2-rc8
git bisect bad c13dcf9f2d6f5f06ef1bf79ec456df614c5e058b
# good: [6684d0c4c8284687d14904051e2f16d76e495fa4] staging: fbtft: reformat
hardcoded sequences
git bisect good 6684d0c4c8284687d14904051e2f16d76e495fa4
# good: [6684d0c4c8284687d14904051e2f16d76e495fa4] staging: fbtft: reformat
hardcoded sequences
git bisect good 6684d0c4c8284687d14904051e2f16d76e495fa4
# good: [0db9723cacf4d62bc3685fb15179b39ee4e17679] Merge branch 'next' of
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux
git bisect good 0db9723cacf4d62bc3685fb15179b39ee4e17679
# good: [0db9723cacf4d62bc3685fb15179b39ee4e17679] Merge branch 'next' of
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux
git bisect good 0db9723cacf4d62bc3685fb15179b39ee4e17679
# bad: [78c10e556ed904d5bfbd71e9cadd8ce8f25d6982] Merge branch 'upstream' of
git://git.linux-mips.org/pub/scm/ralf/upstream-linus
git bisect bad 78c10e556ed904d5bfbd71e9cadd8ce8f25d6982
# bad: [78c10e556ed904d5bfbd71e9cadd8ce8f25d6982] Merge branch 'upstream' of
git://git.linux-mips.org/pub/scm/ralf/upstream-linus
git bisect bad 78c10e556ed904d5bfbd71e9cadd8ce8f25d6982
# good: [22165fa79814e71e7a5974b3c37a5028ed16c8f9] Merge tag 'dm-4.2-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
git bisect good 22165fa79814e71e7a5974b3c37a5028ed16c8f9
# good: [fcbc1777ce8b5edf831c1eca16c1a63c1e4f39fb] Merge tag 'trace-fixes-4.1'
of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
git bisect good fcbc1777ce8b5edf831c1eca16c1a63c1e4f39fb
# bad: [8c7febe83915332276cab49e89f6580bb963fb9a] Merge tag 'tty-4.2-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect bad 8c7febe83915332276cab49e89f6580bb963fb9a
# bad: [8d7804a2f03dbd34940fcb426450c730adf29dae] Merge tag
'driver-core-4.2-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
git bisect bad 8d7804a2f03dbd34940fcb426450c730adf29dae
# good: [6fa45a22689722dac9f0e90c0931d4b34b334ede] parport: add device-model to
parport subsystem
git bisect good 6fa45a22689722dac9f0e90c0931d4b34b334ede
# good: [3dc196eae1db548f05e53e5875ff87b8ff79f249] mei: me: wait for power
gating exit confirmation
git bisect good 3dc196eae1db548f05e53e5875ff87b8ff79f249
# good: [3dc196eae1db548f05e53e5875ff87b8ff79f249] mei: me: wait for power
gating exit confirmation
git bisect good 3dc196eae1db548f05e53e5875ff87b8ff79f249
# bad: [e382608254e06c8109f40044f5e693f2e04f3899] Merge tag 'trace-v4.2' of
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
git bisect bad e382608254e06c8109f40044f5e693f2e04f3899
# bad: [e382608254e06c8109f40044f5e693f2e04f3899] Merge tag 'trace-v4.2' of
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
git bisect bad e382608254e06c8109f40044f5e693f2e04f3899
# bad: [5d6ad960a71f0b36d95d74ef93285733b9f62f59] tracing: Rename
FTRACE_EVENT_FL_* flags to EVENT_FILE_FL_*
git bisect bad 5d6ad960a71f0b36d95d74ef93285733b9f62f59
# bad: [645df987f7c1740bb1ba783ab907001720a20cf7] tracing: Rename
ftrace_print_*() functions ta trace_print_*()
git bisect bad 645df987f7c1740bb1ba783ab907001720a20cf7
# bad: [f267caab44451baa70d25fa3191a68bb79ad1b08] tracing: Remove unused
prototype ftrace_event_define_field()
git bisect bad f267caab44451baa70d25fa3191a68bb79ad1b08
# bad: [7e255d346c12888f7cce4b89a03a5fe5e9196ab1] tracing: Export tracing clock
functions
git bisect bad 7e255d346c12888f7cce4b89a03a5fe5e9196ab1
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-09-06 13:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 3:08 [Bug 103271] New: AMD R9 270X Flickering with DPM Enabled on Linux 4.1 with RadeonSI bugzilla-daemon
2015-08-22 3:10 ` [Bug 103271] " bugzilla-daemon
2015-08-22 21:22 ` bugzilla-daemon
2015-08-22 21:34 ` bugzilla-daemon
2015-08-24 5:10 ` bugzilla-daemon
2015-08-24 21:33 ` bugzilla-daemon
2015-08-24 21:38 ` bugzilla-daemon
2015-08-24 21:40 ` bugzilla-daemon
2015-08-25 1:38 ` bugzilla-daemon
2015-08-25 1:54 ` bugzilla-daemon
2015-08-25 1:56 ` bugzilla-daemon
2015-09-06 0:54 ` bugzilla-daemon
2015-09-06 13:58 ` bugzilla-daemon [this message]
2015-09-06 14:00 ` bugzilla-daemon
2015-09-08 6:38 ` bugzilla-daemon
2015-09-08 21:36 ` bugzilla-daemon
2015-09-09 2:32 ` bugzilla-daemon
2015-09-09 16:03 ` bugzilla-daemon
2015-09-14 22:31 ` bugzilla-daemon
2015-09-15 2:18 ` bugzilla-daemon
2015-09-15 13:35 ` bugzilla-daemon
2015-09-15 15:33 ` bugzilla-daemon
2015-09-15 15:40 ` bugzilla-daemon
2015-10-17 2:47 ` [Bug 103271] [regression bisected] " bugzilla-daemon
2016-04-15 20:35 ` 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-103271-2300-uz0l4ZXZa9@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