All of lore.kernel.org
 help / color / mirror / Atom feed
From: Garrick Staples <garrick@usc.edu>
To: nfs@lists.sourceforge.net
Subject: Re: 2.6.6 lockupy
Date: Wed, 26 May 2004 14:44:36 -0700	[thread overview]
Message-ID: <20040526214435.GK6931@polop.usc.edu> (raw)
In-Reply-To: <20040526213732.GG2827@fieldses.org>

[-- Attachment #1: Type: text/plain, Size: 783 bytes --]

On Wed, May 26, 2004 at 05:37:32PM -0400, J. Bruce Fields alleged:
> On Wed, May 26, 2004 at 02:11:16PM -0700, Garrick Staples wrote:
> > I tried Trond's 2.6.6 patches at his website, but those brokes things
> > considerably.  Since I don't have any actual Oops messages, anyone have any
> > experimental deadlock-fixing patches they want me to test? :)
> 
> Note that Trond's patches are client-side only, so shouldn't affect your
> servers one way or another (unless I'm misunderstanding what your
> setup).--b.

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


-- 
Garrick Staples, Linux/HPCC Administrator
University of Southern California

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-26 21:44 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 [this message]
2004-05-26 21:55     ` J. Bruce Fields
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=20040526214435.GK6931@polop.usc.edu \
    --to=garrick@usc.edu \
    --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.