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: Mon, 30 May 2011 04:48:29 +0200 [thread overview]
Message-ID: <1306723709.4895.4.camel@marge.simson.net> (raw)
In-Reply-To: <20110529162738.GA7832@black.transpect.com>
On Sun, 2011-05-29 at 12:27 -0400, Whit Blauvelt wrote:
> Hi,
>
> This isn't a most-recent kernel, so we should upgrade the systems with it,
> but it could also be useful to know why the fault occurred. If someone here
> can easily decode the final messages when the system froze....
>
> This is vanilla 2.6.35.5, built from source, running with Ubuntu Server
> 10.04.2. Two similar systems have been running stably for months, then
> yesterday and today both froze up - one twice. On the one where I was able
> to get a remote console before rebooting the final messages are in a screen
> capture at
>
> http://www.transpect.com/jpg/sb2crash.jpg
>
> The final lines are
>
> [3521437.065988] RIP [<ffffffff81054ddc>] set_next_entity+0xc/0xa0
> [3521437.065993] RSP <ffff8801b60b1748>
> [3521437.065994] CR2: 0000000000000038
> [3521437.065997] ---[ end trace 5a40c5f226029029 ]---
> [3521437.065999] Fixing recursive fault but reboot is needed!
>
> These are basically file servers running NFS, samba, and some Python. I know
> there are recent improvements to the kernel's NFS functions. Does this point
> in that direction as the cause of the recursive fault?
No, you've been bitten by an annoyingly elusive load balancing bug.
-Mike
next prev parent reply other threads:[~2011-05-30 2:48 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 [this message]
2011-05-31 14:24 ` Whit Blauvelt
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=1306723709.4895.4.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