From: Ingo Molnar <mingo@elte.hu>
To: Bruce Duncan <bwduncan@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <srostedt@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git pull] ftrace for v2.6.27
Date: Wed, 13 Aug 2008 09:19:05 +0200 [thread overview]
Message-ID: <20080813071905.GA18529@elte.hu> (raw)
In-Reply-To: <200808130248.58216.bwduncan@gmail.com>
* Bruce Duncan <bwduncan@gmail.com> wrote:
> Hi Ingo, Steven, everyone,
>
> [ Please CC me in replies ]
>
> I have just tracked down a regression in 2.6.27-rc2 wrt 2.6.26. Commit
> 77a2b37d227483fe52aead242652aee406c25bf0 (ftrace: startup tester on
> dynamic tracing.) causes my laptop to fail to resume from S3 (it
> simply reboots about a second after the resume starts and the display
> never shows anything).
>
> The patch doesn't revert with patch -R (I don't know if there's a
> cleverer way to ask git to revert it), but the problem goes away if I
> turn off CONFIG_DYNAMIC_FTRACE.
>
> The commit and bisect log are attached. Please can you help me to
> debug this?
could you please send your .config file as well?
Suspend+resume bugs are notoriously hard to debug (there's no console
output in most cases), so i guess the best way to debug this is for
Steve or me to try to reproduce it. Could you send the output of this
script:
http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh
that will tell us what kind of hw you have.
and could you perhaps try the patch below? The patch disables on the fly
dynamic code patching - which is the primary suspect here. If it makes a
difference on your box then a theory would be that ftraced runs too soon
after suspend+resume.
Ingo
----------------------->
Subject: ftrace: debug
From: Ingo Molnar <mingo@elte.hu>
Date: Wed Aug 13 09:17:12 CEST 2008
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/trace/ftrace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/kernel/trace/ftrace.c
===================================================================
--- linux.orig/kernel/trace/ftrace.c
+++ linux/kernel/trace/ftrace.c
@@ -811,7 +811,7 @@ static int ftraced(void *ignore)
/* check once a second */
schedule_timeout(HZ);
- if (unlikely(ftrace_disabled))
+ if (1)
continue;
mutex_lock(&ftrace_sysctl_lock);
next prev parent reply other threads:[~2008-08-13 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 14:22 [git pull] ftrace for v2.6.27 Ingo Molnar
2008-08-13 1:48 ` Bruce Duncan
2008-08-13 7:19 ` Ingo Molnar [this message]
2008-08-13 15:11 ` Steven Rostedt
2008-08-13 15:18 ` Ingo Molnar
2008-08-13 19:53 ` Andi Kleen
2008-08-13 17:15 ` Steven Rostedt
2008-08-13 18:08 ` Bruce Duncan
2008-08-15 9:29 ` Ingo Molnar
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=20080813071905.GA18529@elte.hu \
--to=mingo@elte.hu \
--cc=bwduncan@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.