From: Dave Jones <davej@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [3.10-rc6] soft lockups from sync()
Date: Wed, 26 Jun 2013 10:27:40 -0400 [thread overview]
Message-ID: <20130626142739.GA23429@redhat.com> (raw)
In-Reply-To: <20130626134915.GA14102@quack.suse.cz>
On Wed, Jun 26, 2013 at 03:49:15PM +0200, Jan Kara wrote:
> On Mon 17-06-13 10:26:11, Dave Jones wrote:
> > Haven't seen this happen before.. 3.10-rc6 + a bunch of patches to
> > survive other trinity induced bugs + some debug 'helpers' (the
> > loadavg-at-oops for eg), but nothing that should be responsible for this.
> Hum, we are spinning on inode_sb_list_lock. I'm not aware of any recent
> changes in that area. Is this reproducible? Has anything changed with
> trinity so that it could start triggering this? Maybe using lockstat we
> could see who are the worst offenders using the lock...
The biggest change is that I got two new test machines (that I'm seeing this on).
They're both quad core haswell machines, so a lot faster than the previous
machines I've been running trinity on.
Dave
prev parent reply other threads:[~2013-06-26 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 14:26 [3.10-rc6] soft lockups from sync() Dave Jones
2013-06-26 13:49 ` Jan Kara
2013-06-26 14:27 ` Dave Jones [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=20130626142739.GA23429@redhat.com \
--to=davej@redhat.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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