From: Mike Galbraith <efault@gmx.de>
To: Whit Blauvelt <whit@transpect.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: recursive fault in 2.6.35.5
Date: Wed, 01 Jun 2011 04:01:46 +0200 [thread overview]
Message-ID: <1306893706.4791.12.camel@marge.simson.net> (raw)
In-Reply-To: <20110531142415.GA17781@black.transpect.com>
On Tue, 2011-05-31 at 10:24 -0400, Whit Blauvelt wrote:
> 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.
No earthly notion. I never figured out exactly how it happens. Setting
traps for the critter didn't worked out. I did receive some diagnostic
info from a group of ppc64 boxen that indicated that the clock went
backward, but when I zeroed in on it, it they went silent. All other
machines with traps set have been totally silent for months (that's a
lot of machines too).
Bug seems to be dead upstream, at least I haven't noticed any reports
with a recent kernel.
-Mike
prev parent reply other threads:[~2011-06-01 2:01 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
2011-06-01 2:01 ` Mike Galbraith [this message]
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=1306893706.4791.12.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=whit@transpect.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