linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: Yan Burman <yanb@mellanox.com>
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org,
	linux-rdma@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>,
	Tom Tucker <tom@opengridcomputing.com>
Subject: Re: NFS over RDMA crashing
Date: Wed, 06 Feb 2013 09:58:41 -0600	[thread overview]
Message-ID: <51127DB1.6070804@opengridcomputing.com> (raw)
In-Reply-To: <51127B3F.2090200@mellanox.com>

On 2/6/2013 9:48 AM, Yan Burman wrote:
> When I moved to commit 79f77bf9a4e3dd5ead006b8f17e7c4ff07d8374e I was 
> no longer getting the server crashes,
> so the reset of my tests were done using that point (it is somewhere 
> in the middle of 3.7.0-rc2).
>

+tom tucker

I'd try going back a few kernels, like to 3.5.x and see if things are 
more stable.  If you find a point that works, then git bisect might help 
identify the regression.

  reply	other threads:[~2013-02-06 16:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 15:48 NFS over RDMA crashing Yan Burman
2013-02-06 15:58 ` Steve Wise [this message]
2013-02-06 17:06   ` Jeff Becker
2013-02-07 15:54     ` Yan Burman
2013-02-06 22:24 ` J. Bruce Fields
2013-02-06 22:28   ` Steve Wise
2013-02-08  5:37     ` Tom Tucker
2013-02-07 16:41   ` J. Bruce Fields
2013-02-11 15:19     ` Yan Burman
2013-02-11 18:13       ` J. Bruce Fields
2013-02-15 15:27       ` J. Bruce Fields
2013-02-18 11:44         ` Yan Burman
2014-03-07 16:59     ` Steve Wise
2014-03-07 20:41       ` Steve Wise
2014-03-08 16:39         ` Steve Wise
2014-03-08 19:20           ` Steve Wise
2014-03-08 20:13             ` Steve Wise
2014-03-12 13:33               ` Jeff Layton
2014-03-12 14:05                 ` Trond Myklebust
2014-03-12 14:22                   ` Tom Tucker
2014-03-12 14:28                   ` Jeffrey Layton
2014-03-12 15:03                     ` Trond Myklebust
2014-03-12 15:29                       ` Jeffrey Layton

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=51127DB1.6070804@opengridcomputing.com \
    --to=swise@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=tom@opengridcomputing.com \
    --cc=yanb@mellanox.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;
as well as URLs for NNTP newsgroup(s).