From: Dave Chinner <david@fromorbit.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: xfs@oss.sgi.com
Subject: Re: XFS hung on 2.6.33.3 kernel
Date: Thu, 5 Aug 2010 15:45:53 +1000 [thread overview]
Message-ID: <20100805054553.GB7362@dastard> (raw)
In-Reply-To: <AANLkTi=BA_spq8UoTR5HwDMWSFCp+qO54gTyVu2gdNBc@mail.gmail.com>
On Wed, Aug 04, 2010 at 11:40:02AM -0400, Ilia Mirkin wrote:
> On Wed, Aug 4, 2010 at 2:53 AM, Dave Chinner <david@fromorbit.com> wrote:
> > On Wed, Aug 04, 2010 at 12:39:08AM -0400, Ilia Mirkin wrote:
> >> On Wed, Aug 4, 2010 at 12:27 AM, Dave Chinner <david@fromorbit.com> wrote:
> >> > On Tue, Aug 03, 2010 at 09:15:53PM -0400, Ilia Mirkin wrote:
> >> >> On Tue, Aug 3, 2010 at 8:47 PM, Dave Chinner <david@fromorbit.com> wrote:
> >> >> > Ilia,
> >> >> >
> >> >> > Can you send me the output of this for your kernel that the
> >> >> > traces came from:
> >> >> >
> >> >> > $ gdb <path/to/vmlinux>
> >> >> > (gdb) l *( xfs_write+0x2cc)
> >> >> >
> >> >> > You can run it against the vmlinux file in the kernel build
> >> >> > directory. Basically I need to know which xfs_ilock() call in
> >> >> > xfs_write() one of the mysqld-test processes is stuck on.
....
> > OK, that doesn't help - it followed into the inline function
> > rather than telling me which of the two calls in the function it
> > was. I guess I'll need the disassembly output to work it out.
> > Can you send the output of "disass xfs_ilock" instead? Thanks.
>
> Looks like it's the first one.
Yup, that's what it looks like to me, too. That means it's the
XFS_IOLOCK_EXCL it is blocking trying to get, not the
XFS_ILOCK_EXCL. Well, that makes sense, and tells me that the
lockdep "held locks" output at the end also includes locks we are
trying to obtain. That clears up that confusion.
Ok, I'll work from there. Thanks, Ilia.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-05 5:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 4:01 XFS hung on 2.6.33.3 kernel Ilia Mirkin
2010-07-18 1:20 ` Dave Chinner
2010-07-18 1:35 ` Ilia Mirkin
2010-07-18 23:50 ` Dave Chinner
2010-08-03 22:30 ` Ilia Mirkin
2010-08-04 0:47 ` Dave Chinner
2010-08-04 1:15 ` Ilia Mirkin
2010-08-04 4:27 ` Dave Chinner
2010-08-04 4:39 ` Ilia Mirkin
2010-08-04 6:53 ` Dave Chinner
2010-08-04 15:40 ` Ilia Mirkin
2010-08-05 5:45 ` Dave Chinner [this message]
2010-08-05 6:25 ` Dave Chinner
2010-08-05 6:42 ` Ilia Mirkin
2010-08-07 10:08 ` Dave Chinner
2013-04-04 21:44 ` qiyansun
2010-07-18 4:57 ` Christoph Hellwig
2010-07-18 5:28 ` Ilia Mirkin
2010-07-18 20:17 ` Ilia Mirkin
2010-07-18 23:33 ` Dave Chinner
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=20100805054553.GB7362@dastard \
--to=david@fromorbit.com \
--cc=imirkin@alum.mit.edu \
--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