All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: nfs@lists.sourceforge.net
Subject: Re: 2.6.6 lockupy
Date: Wed, 26 May 2004 17:55:56 -0400	[thread overview]
Message-ID: <20040526215555.GI2827@fieldses.org> (raw)
In-Reply-To: <20040526214435.GK6931@polop.usc.edu>

On Wed, May 26, 2004 at 02:44:36PM -0700, Garrick Staples wrote:
> You didn't misunderstand... but I was at a complete loss with production
> machines suddenly dropping like flies.  I'm now at the stage where I just try
> random things =P

OK.  May as well send us what information you have on the lockups, and
maybe your .config while you're at it....

(Also, you mention 2.6.6 in your subject line but it sounds like this
happens to you under earlier kernels as well?  Are there any kernels
that are OK?)

--Bruce Fields


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-05-26 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 21:11 2.6.6 lockup Garrick Staples
2004-05-26 21:37 ` 2.6.6 lockupy J. Bruce Fields
2004-05-26 21:44   ` Garrick Staples
2004-05-26 21:55     ` J. Bruce Fields [this message]
2004-05-26 22:26       ` Garrick Staples
2004-05-27  4:39       ` Garrick Staples

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=20040526215555.GI2827@fieldses.org \
    --to=bfields@fieldses.org \
    --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.