From: Dave Chinner <david@fromorbit.com>
To: Dave Jones <davej@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: XFS / writeback invoking soft lockup.
Date: Sat, 14 Dec 2013 19:20:59 +1100 [thread overview]
Message-ID: <20131214082059.GS31386@dastard> (raw)
In-Reply-To: <20131213162228.GA29908@redhat.com>
On Fri, Dec 13, 2013 at 11:22:28AM -0500, Dave Jones wrote:
> On Fri, Dec 13, 2013 at 03:16:39AM -0800, Christoph Hellwig wrote:
> > On Fri, Dec 13, 2013 at 09:48:53PM +1100, Dave Chinner wrote:
> > > All I can say is that there doesn't look to be any obvious signs
> > > that this is a XFS or writeback problem fom the stack trace, and
> > > without more information or a reproducable test case I'm not going
> > > to be able to understand the cause.
> > >
> > > Is the problem reproducable, or is it just a one-off?
> >
> > If it's reproducable it would be good to enable the xfs_writepage
> > tracepoint and get a trace-cmd log of it.
>
> I hit it pretty reliably last night. I'll make a note to look into it
> on monday with that enabled.
You might want to grab the writeback tracepoints as well. Note that
you'll probably have to filter by device so you don't get noise from
all the other block devices, too.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2013-12-14 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 7:14 XFS / writeback invoking soft lockup Dave Jones
2013-12-13 10:48 ` Dave Chinner
2013-12-13 11:16 ` Christoph Hellwig
2013-12-13 16:22 ` Dave Jones
2013-12-14 8:20 ` Dave Chinner [this message]
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=20131214082059.GS31386@dastard \
--to=david@fromorbit.com \
--cc=davej@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.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