From: Steven Rostedt <rostedt@goodmis.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: "Lai Jiangshan" <laijs@cn.fujitsu.com>,
"Frederic Weisbecker" <fweisbec@gmail.com>,
"Américo Wang" <xiyou.wangcong@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 12:56:16 -0500 [thread overview]
Message-ID: <1268502976.4471.798.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1268446049.4471.787.camel@gandalf.stny.rr.com>
On Fri, 2010-03-12 at 21:07 -0500, Steven Rostedt wrote:
> On Tue, 2010-03-09 at 11:38 +0800, Li Zefan wrote:
>
> > The segfault is from userspace. This is a segfault I just got:
> >
> > ftrace_stack_ma[14989]: segfault at fe2e ip 00000000004474c0 sp 00007fffb97e38c0 error 4 in bash[400000+d1000]
>
> Li and Lai,
>
> Thanks a lot for reporting all this, and writing the ftrace_stress_test.
> I've fixed all the bugs that it has reported (to my knowledge) and after
> a little more testing I will soon be sending a patch series out.
Li,
I ran your test for 13 hours on three different machines. I did not hit
any more errors. Although I see a lockdep warning (not a locking problem
but the WARN_ON in fork.c is triggering). I'll look into that on Monday.
Please take the new patches that Ingo just pushed to Linus, if you find
any more bugs, please let me know right away.
Thanks!
-- Steve
next prev parent reply other threads:[~2010-03-13 17:56 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
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 [this message]
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=1268502976.4471.798.camel@gandalf.stny.rr.com \
--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
all inboxes | Powered by JetHome®