public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Dietrich <marvin24@gmx.de>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	"Dr. J. Bruce Fields" <bfields@fieldses.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: NFSv4 poops itself
Date: Fri, 27 Jul 2007 20:29:48 +0200	[thread overview]
Message-ID: <200707272029.49521.marvin24@gmx.de> (raw)
In-Reply-To: <1185556178.6586.40.camel@localhost>


Hi,

Am Freitag, 27. Juli 2007 19:09 schrieb Trond Myklebust:
> On Fri, 2007-07-27 at 09:33 -0400, Trond Myklebust wrote:
> (...)
> Jeff and Bruce, could you please try to reproduce the problem after
> either applying patches 001 to 004 or just the single NFS_ALL patch
> from
>
>    http://client.linux-nfs.org/Linux-2.6.x/2.6.23-rc1/

as posted earlier, 001-002 does not fix it. Then I also applied 003+004 and it 
seems to be fixed now. kde boots up and I can start some programs, which I 
couldn't before. 

The "inconsistent lock state" error still exists, but it really seems to be 
unrelated.


> Cheers
>   Trond

thanks

Marc

  parent reply	other threads:[~2007-07-27 18:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 12:53 NFSv4 poops itself Jeff Garzik
2007-07-27 13:33 ` Trond Myklebust
2007-07-27 17:09   ` Trond Myklebust
2007-07-27 17:16     ` Jeff Garzik
2007-07-27 17:29       ` Trond Myklebust
2007-08-03 19:13         ` J. Bruce Fields
2007-08-06 13:40           ` J. Bruce Fields
2007-08-06 18:40             ` Trond Myklebust
2007-07-27 18:29     ` Marc Dietrich [this message]
2007-07-27 13:36 ` Marc Dietrich
2007-07-27 13:40   ` Jeff Garzik
2007-07-27 14:45     ` Trond Myklebust
2007-07-27 14:58   ` Satyam Sharma
2007-07-27 17:58     ` Marc Dietrich
2007-07-27 18:39       ` Trond Myklebust

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=200707272029.49521.marvin24@gmx.de \
    --to=marvin24@gmx.de \
    --cc=Trond.Myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.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