mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: rostedt@goodmis.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.33: ftrace triggers soft lockup
Date: Fri, 5 Mar 2010 15:16:07 +0800	[thread overview]
Message-ID: <2375c9f91003042316g6e774d60n90dfc4784d3b66bf@mail.gmail.com> (raw)
In-Reply-To: <2375c9f91003042014y17588865g8f9110e666ac2456@mail.gmail.com>

On Fri, Mar 5, 2010 at 12:14 PM, Américo Wang <xiyou.wangcong@gmail.com> wrote:
> On Thu, Mar 4, 2010 at 9:54 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>> On Wed, 2010-03-03 at 14:04 +0800, Américo Wang wrote:
>>> I am not sure if this is ftrace's fault, but it is ftrace who triggers
>>> the soft lockup. On my machine, it is pretty easy, just run:
>>>
>>> echo function_graph > current_tracer
>>>
>>> I found this when 2.6.33-rc7, but forgot to report here. I just tried
>>> today's
>>> Linus tree, it still has this problem.
>>
>> So this is not present in 2.6.33-rc6? If you know approximately when it
>> appeared, would you be able to do a git bisect on it?
>>
>
> I can't say that because I didn't try -rc6.
>

Sigh, 2.6.33-rc6 doesn't work, even 2.6.32 doesn't work...

  reply	other threads:[~2010-03-05  7:16 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03  6:04 Américo Wang
2010-03-03 13:05 ` Steven Rostedt
2010-03-04  2:58   ` Américo Wang
2010-03-04  1:33 ` Li Zefan
2010-03-04  1:46 ` Frederic Weisbecker
2010-03-04  3:01   ` Américo Wang
2010-03-04  3:18     ` Steven Rostedt
2010-03-04  4:06       ` Frederic Weisbecker
2010-03-04  5:10       ` Américo Wang
2010-03-04  5:18         ` Frederic Weisbecker
2010-03-04 13:54 ` Steven Rostedt
2010-03-05  4:14   ` Américo Wang
2010-03-05  7:16     ` Américo Wang [this message]
2010-03-05 15:06       ` Steven Rostedt
2010-03-05 17:16         ` Frederic Weisbecker
2010-03-05 18:35           ` Steven Rostedt
2010-03-05 18:43             ` Frederic Weisbecker
2010-03-05 19:07               ` Steven Rostedt
2010-03-08  7:32           ` Li Zefan
2010-03-08 15:15             ` Steven Rostedt
2010-03-09  2:11               ` Li Zefan
2010-03-09  2:23                 ` Steven Rostedt
2010-03-09  3:38                   ` Li Zefan
2010-03-12 19:20                     ` Steven Rostedt
2010-03-12 21:38                       ` Steven Rostedt
2010-03-13  2:07                     ` Steven Rostedt
2010-03-13  5:37                       ` Américo Wang
2010-03-13  5:51                         ` Steven Rostedt
2010-03-14 16:55                         ` Steven Rostedt
2010-03-13 17:56                       ` Steven Rostedt
2010-03-15  1:46                         ` Li Zefan
2010-03-15 14:39                           ` Steven Rostedt
2010-03-15 16:16                             ` Steven Rostedt
2010-03-08  2:31         ` Américo Wang
2010-03-09  2:40           ` Américo Wang
2010-03-09  2:51             ` Steven Rostedt
2010-03-09  5:06               ` Américo Wang

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=2375c9f91003042316g6e774d60n90dfc4784d3b66bf@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®