All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: RedHat Rawhide Kernels
Date: 08 Aug 2002 22:16:18 +0200	[thread overview]
Message-ID: <shs65ylm7hp.fsf@charged.uio.no> (raw)
In-Reply-To: <20020808153331.F28223@redhat.com>

>>>>> " " == Benjamin LaHaise <bcrl@redhat.com> writes:

     > For the sake of spreading the knowledge around, I've also got a
     > couple of reports of -5 (which has an earlier set of Trond's
     > client patches) and vanilla 2.4.18 getting D state stuck
     > processes in lock_page on NFS mounts.  There's no useful data
     > point beyond that, but it looks like a request is getting lost
     > somewhere.

Do you know offhand which set of patches are included?

Cheers,
  Trond


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2002-08-08 20:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 19:21 RedHat Rawhide Kernels Jeremy Sanders
2002-08-08 19:33 ` Benjamin LaHaise
2002-08-08 20:16   ` Trond Myklebust [this message]
2002-08-08 20:23     ` Benjamin LaHaise
2002-08-08 20:31       ` Trond Myklebust
2002-08-08 20:57         ` Benjamin LaHaise
2002-08-08 21:16           ` Trond Myklebust
2002-08-08 21:27             ` Benjamin LaHaise
2002-08-08 21:35               ` Trond Myklebust
2002-08-09  1:04                 ` Thomas Langås
2002-08-09  4:51                   ` Trond Myklebust
2002-08-08 20:21 ` Trond Myklebust
2002-08-12 10:41 ` Jeremy Sanders

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=shs65ylm7hp.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=bcrl@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    /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.