public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: recursive fault in 2.6.35.5
Date: Tue, 31 May 2011 10:24:15 -0400	[thread overview]
Message-ID: <20110531142415.GA17781@black.transpect.com> (raw)
In-Reply-To: <1306723709.4895.4.camel@marge.simson.net>

On Mon, May 30, 2011 at 04:48:29AM +0200, Mike Galbraith wrote:

> No, you've been bitten by an annoyingly elusive load balancing bug.

Thanks Mike. Can that bug be avoided by leaving out some kernel option? The
system that happened on had it's identical twin fail the day before. For
both, it was a time of relatively more load (although not excessive). On the
twin we didn't look at the console before rebooting though.

On the other hand, we'd run for months with no problem up until this.

Regards,
Whit


  reply	other threads:[~2011-05-31 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29 16:27 recursive fault in 2.6.35.5 Whit Blauvelt
2011-05-30  2:48 ` Mike Galbraith
2011-05-31 14:24   ` Whit Blauvelt [this message]
2011-06-01  2:01     ` Mike Galbraith

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=20110531142415.GA17781@black.transpect.com \
    --to=whit@transpect.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /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