public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.33: ftrace triggers soft lockup
Date: Sat, 13 Mar 2010 00:51:18 -0500	[thread overview]
Message-ID: <1268459478.3366.5.camel@localhost> (raw)
In-Reply-To: <20100313053733.GD3704@hack>

On Sat, 2010-03-13 at 13:37 +0800, Américo Wang wrote:
> On Fri, Mar 12, 2010 at 09:07:29PM -0500, Steven Rostedt wrote:
> >
> >Americo,
> >
> >I still do not know why the function graph tracer is making your system
> >unusable. I'll look more into that when I get a chance. So far, I have
> >not had any issues on any of my boxes.
> >
> 
> Oh, in fact, I just tried 2 x86_64 machines, both of them have this
> problem.
> 
> Sorry that I don't have much time to do bisect, the last kernel that
> I tried is 2.6.32-rc6, it is bad too. I will try some older kernels
> if I have time.

It may be a config problem. I'll analyze your config again and see if I
can find something with it. But this will need to wait till next week.

Thanks,

-- Steve


  reply	other threads:[~2010-03-13 13:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03  6:04 2.6.33: ftrace triggers soft lockup 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
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 [this message]
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=1268459478.3366.5.camel@localhost \
    --to=rostedt@goodmis.org \
    --cc=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=xiyou.wangcong@gmail.com \
    /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