public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dick Hollenbeck <dick@softplc.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: 2.6.31.1 boot crash, compiled with ftrace
Date: Wed, 30 Sep 2009 09:57:10 -0500	[thread overview]
Message-ID: <4AC371C6.3050104@softplc.com> (raw)
In-Reply-To: <1254301761.7286.4.camel@frodo>

Steven Rostedt wrote:
> On Wed, 2009-09-30 at 04:03 -0400, Steven Rostedt wrote:
>   
>> On Tue, 2009-09-29 at 10:21 -0500, Dick Hollenbeck wrote:
>>     
>>> Please help with a kernel boot crash.  This is happening with ftrace 
>>> enabled.   (I have yet to try without ftrace.)  This same box runs 
>>> kernel 2.6.26 fine.
>>>
>>> While running 'make oldconfig' coming up from 2.6.26, the three most 
>>> significant changes were:
>>>
>>> 1) changed CPU from 486 to Pentium-Classic
>>>
>>> 2) Added "High Memory Support" 4 GB
>>>
>>> 3) Enabled various ftrace options, because I am on the hunt for some 
>>> insane latency problems.
>>>
>>>       
>> Hi Dick,
>>
>> Thanks for reporting this. Peter and I have been taking some look at it.
>> We are not sure that it is ftrace related. have you tried booting the
>> kernel without adding ftrace?
>>     
>
> Hi,
>
> I just booted your config a couple of times without any issues. How
> reproducible is this?
>
> Thanks,
>
> -- Steve
>   

Steve,

Thank you *very* much for your help.  *This* is what makes linux great, 
not just the code, and you are part of it.

The target is an embedded industrial box, and I'm booting from CF card 
via IDE.  I switched build computers, target box stayed the same and the 
CF card stayed the same.  With the switch, the compiler changed and the 
USB CF writer changed (used to create the root fs on the CF card before 
it is moved), as did some configuration options.  I am now booting.  I 
am most suspicious of the original CF card writer device at this point.  
Please do not spend any more time on it unless I come back for another 
plea for help, such as if its the config options change.  I need more 
time to narrow down the explanation for the failure to boot.

My real pursuit here is to find the reason for a nearly 1 second latency 
when running a SCHED_RR userspace process.  The filesystem is ext3 off 
the flash card via IDE. Linux is yanking the machine away from this 
process sporadically for up to 1 second, no disk file calls in this 
proces, only some serial port and networking (epoll) userspace calls in 
a loop.  It is insane.  So I have to get either LTT or FTRACE enabled, 
never used either before.  Its been a tough 2 weeks.  Just getting the 
LTT patches in sync with a decent kernel has been nearly unbearable.

Thanks again,

Dick



  reply	other threads:[~2009-09-30 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 15:21 2.6.31.1 boot crash, compiled with ftrace Dick Hollenbeck
2009-09-30  8:03 ` Steven Rostedt
2009-09-30  9:09   ` Steven Rostedt
2009-09-30 14:57     ` Dick Hollenbeck [this message]
2009-09-30 17:57       ` Steven Rostedt

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=4AC371C6.3050104@softplc.com \
    --to=dick@softplc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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