public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: rostedt@goodmis.org
Cc: "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: Tue, 09 Mar 2010 11:38:23 +0800	[thread overview]
Message-ID: <4B95C2AF.7010508@cn.fujitsu.com> (raw)
In-Reply-To: <1268101394.10871.1861.camel@gandalf.stny.rr.com>

Steven Rostedt wrote:
> On Tue, 2010-03-09 at 10:11 +0800, Li Zefan wrote:
>> Steven Rostedt wrote:
>>> On Mon, 2010-03-08 at 15:32 +0800, Li Zefan wrote:
> 
>>> This sounds like the compiler may have screwed up again. Can you compile
>>> with this patch and see if it catches anything?
>>>
>> But I was using a x86_64 machine, and this patch won't do anything on
>> x86_64?
> 
> I wonder if this issue has crept to x86_64. What kind of dump do you
> get? And if this segfault is in the kernel, could you see (using gdb on
> a vmlinux) if any of the stack frame setups look peculiar?
> 

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]

  reply	other threads:[~2010-03-09  3:37 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 [this message]
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=4B95C2AF.7010508@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --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