On Tue, 2010-08-17 at 21:52 +1000, Dave Chinner wrote:
quoted text
> On Tue, Aug 17, 2010 at 04:37:44PM +0800, Lai Jiangshan wrote:
> > On 08/17/2010 03:37 PM, Dave Chinner wrote:
> > > Tracing folks,
> > > 
> > > I've got a machine stuck with a cpu spinning in a tight loop (the
> > > new writeback/sync livelock avoidance code is, well, livelocking),
> > > and I was trying to find out what triggered by using the writeback
> > > trace events. Unfortunately, I can't dump the trace events because
> > > it gets stuck here:
> > 
> > > 
> > > Given that the trace events are there mainly for debugging, this
> > > seems like a bit of an oversight - hanging a CPU in a tight loop is
> > > not an uncommon event during code development....
> > > 
> > 
> > You can try 'cat trace_pipe', if I did not miss you meaning.
> 
> I'll try it, but I'm really after the static event list which is why
> I'm using the trace file rather than trace_pipe. I want the history,
> not new events as they happen. 

When the systems locks up, I assume you want to see why? The trace_pipe
should show that without locking the system.

You could also try downloading trace-cmd and running the tracer with
that. That will save all traces to a file while running the trace.

-- Steve


--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/