dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 14:00:47 +0000	[thread overview]
Message-ID: <bug-103271-2300-fz1b5opiUA@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 #12 from Kevin McCormack <wittyman37@yahoo.com> ---
This might help as well...

$ git bisect view --stat
commit 7e255d346c12888f7cce4b89a03a5fe5e9196ab1
Author: Jerry Snitselaar <jsnitsel@redhat.com>
Date:   Thu Apr 30 08:10:24 2015 -0700

    tracing: Export tracing clock functions

    Critical tracepoint hooks should never call anything that takes a lock,
    so they are unable to call getrawmonotonic() or ktime_get().

    Export the rest of the tracing clock functions so can be used in
    tracepoint hooks.

    Background: We have a customer that adds their own module and registers
    a tracepoint hook to sched_wakeup. They were using ktime_get() for a
    time source, but it grabs a seq lock and caused a deadlock to occur.

    Link:
http://lkml.kernel.org/r/1430406624-22609-1-git-send-email-jsnitsel@redhat.com

    Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

:...skipping...
commit 7e255d346c12888f7cce4b89a03a5fe5e9196ab1
Author: Jerry Snitselaar <jsnitsel@redhat.com>
Date:   Thu Apr 30 08:10:24 2015 -0700

    tracing: Export tracing clock functions

    Critical tracepoint hooks should never call anything that takes a lock,
    so they are unable to call getrawmonotonic() or ktime_get().

    Export the rest of the tracing clock functions so can be used in
    tracepoint hooks.

    Background: We have a customer that adds their own module and registers
    a tracepoint hook to sched_wakeup. They were using ktime_get() for a
    time source, but it grabs a seq lock and caused a deadlock to occur.

    Link:
http://lkml.kernel.org/r/1430406624-22609-1-git-send-email-jsnitsel@redhat.com

    Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

 kernel/trace/trace_clock.c | 3 +++
 1 file changed, 3 insertions(+)

commit 755a27e7e4c817dd51ade41668b380f26026899c
Author: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
Date:   Sun May 3 18:18:02 2015 +0800

    tracing: remove unused ftrace_output_event() prototype

    The prototype of ftrace_output_event was added by commit 1d6bae966e90
    ("tracing: Move raw output code from macro to standalone function")
    but this function was not defined anywhere, and is still nowhere to be
    found.

    Link:
http://lkml.kernel.org/r/1430648282-25792-1-git-send-email-nicolas.iooss_linux@m4x.org

    Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

 include/linux/ftrace_event.h | 3 ---
 1 file changed, 3 deletions(-)

-- 
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

  parent reply	other threads:[~2015-09-06 14:00 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
2015-09-06 14:00 ` bugzilla-daemon [this message]
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-fz1b5opiUA@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