All of lore.kernel.org
 help / color / mirror / Atom feed
From: CAI Qian <caiqian@redhat.com>
To: xfs@oss.sgi.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: xfs deadlock on 3.9-rc5 running xfstests case #78
Date: Tue, 2 Apr 2013 02:08:49 -0400 (EDT)	[thread overview]
Message-ID: <247719576.438259.1364882929749.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1462091996.435156.1364882416199.JavaMail.root@redhat.com>

Saw on almost all the servers range from x64, ppc64 and s390x with kernel
3.9-rc5 and xfsprogs-3.1.10. Never caught this in 3.9-rc4, so looks like
something new broke this. Log is here with sysrq debug info.
http://people.redhat.com/qcai/stable/log

CAI Qian

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

WARNING: multiple messages have this Message-ID (diff)
From: CAI Qian <caiqian@redhat.com>
To: xfs@oss.sgi.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: xfs deadlock on 3.9-rc5 running xfstests case #78
Date: Tue, 2 Apr 2013 02:08:49 -0400 (EDT)	[thread overview]
Message-ID: <247719576.438259.1364882929749.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1462091996.435156.1364882416199.JavaMail.root@redhat.com>

Saw on almost all the servers range from x64, ppc64 and s390x with kernel
3.9-rc5 and xfsprogs-3.1.10. Never caught this in 3.9-rc4, so looks like
something new broke this. Log is here with sysrq debug info.
http://people.redhat.com/qcai/stable/log

CAI Qian

       reply	other threads:[~2013-04-02  6:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1462091996.435156.1364882416199.JavaMail.root@redhat.com>
2013-04-02  6:08 ` CAI Qian [this message]
2013-04-02  6:08   ` xfs deadlock on 3.9-rc5 running xfstests case #78 CAI Qian
2013-04-02  7:05   ` Loopback device hung [was Re: xfs deadlock on 3.9-rc5 running xfstests case #78] Dave Chinner
2013-04-02  7:05     ` Dave Chinner
2013-04-02  7:19     ` Jens Axboe
2013-04-02  7:19       ` Jens Axboe
2013-04-02  7:30       ` Jens Axboe
2013-04-02  7:30         ` Jens Axboe
2013-04-02  8:39         ` CAI Qian
2013-04-02  8:39           ` CAI Qian
2013-04-02  9:00           ` Jens Axboe
2013-04-02  9:00             ` Jens Axboe
2013-04-02  9:31             ` CAI Qian
2013-04-02  9:31               ` CAI Qian
2013-04-02  9:48               ` Jens Axboe
2013-04-02  9:48                 ` Jens Axboe
2013-04-03 11:41                 ` Jens Axboe
2013-04-03 11:41                   ` Jens Axboe
2013-04-03 15:41                   ` Phillip Susi
2013-04-03 15:41                     ` Phillip Susi
2013-04-04 20:30                     ` Phillip Susi
2013-04-04 20:30                       ` Phillip Susi
2013-04-09  6:55                       ` Dave Chinner
2013-04-09  6:55                         ` Dave Chinner
2013-04-09  7:01                         ` Jens Axboe
2013-04-09  7:01                           ` Jens Axboe
2013-04-09  7:08                           ` Dave Chinner
2013-04-09  7:08                             ` Dave Chinner
2013-04-10  7:24                             ` Jens Axboe
2013-04-10  7:24                               ` Jens Axboe
2013-05-28 14:51                       ` Phillip Susi
2013-05-28 14:51                         ` Phillip Susi

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=247719576.438259.1364882929749.JavaMail.root@redhat.com \
    --to=caiqian@redhat.com \
    --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 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.