From: Dave Chinner <david@fromorbit.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [tracing, hang] dumping events gets stuck in synchronise_sched
Date: Tue, 17 Aug 2010 21:52:43 +1000 [thread overview]
Message-ID: <20100817115243.GE7362@dastard> (raw)
In-Reply-To: <4C6A4A58.2030904@cn.fujitsu.com>
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.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2010-08-17 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 7:37 [tracing, hang] dumping events gets stuck in synchronise_sched Dave Chinner
2010-08-17 8:37 ` Lai Jiangshan
2010-08-17 11:52 ` Dave Chinner [this message]
2010-08-17 13:02 ` Steven Rostedt
2010-08-17 22:40 ` Dave Chinner
2010-08-17 23:07 ` Steven Rostedt
2010-08-18 0:55 ` Dave Chinner
2010-08-18 1:07 ` 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=20100817115243.GE7362@dastard \
--to=david@fromorbit.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.