2.6.33: ftrace triggers soft lockup
in [Kernel]
|
Prev: linux-next: build warning after merge of the mfd tree
Next: linux-next: build failure after merge of the driver-core tree
From: Américo Wang on 13 Mar 2010 00:40 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. Thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Steven Rostedt on 13 Mar 2010 08:30 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Steven Rostedt on 13 Mar 2010 13:00 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Steven Rostedt on 14 Mar 2010 13:00 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Li Zefan on 14 Mar 2010 21:50
Steven Rostedt wrote: > 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. > As I said in the offline mail, this warning is caused by global trace_clock, and I sent a fix sometime ago: http://lkml.org/lkml/2009/12/21/4 > Please take the new patches that Ingo just pushed to Linus, if you find > any more bugs, please let me know right away. > Thanks for the fixes! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |