public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 4 Aug 2010 10:47:46 +1000	[thread overview]
Message-ID: <20100804004746.GT7362@dastard> (raw)
In-Reply-To: <AANLkTi=EzePfBRdEFQo2BRtKy=464Ci6zPG=UyYJiwNp@mail.gmail.com>

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.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-08-04  0:47 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 [this message]
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
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=20100804004746.GT7362@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