From: Mike Galbraith <mgalbraith@suse.de>
To: Christoph Bartoschek <ponto@pontohonk.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange behaviour after uptime of 208-209 days
Date: Mon, 07 May 2012 06:22:11 +0200 [thread overview]
Message-ID: <1336364531.7272.7.camel@marge.simpson.net> (raw)
In-Reply-To: <iaej79-g6o.ln1@homer.bruehl.pontohonk.de>
On Mon, 2012-05-07 at 01:33 +0200, Christoph Bartoschek wrote:
> Hi,
>
> we run kernel 2.6.37.6 from opensuse 11.4. All machines with uptimes more
> than 208 days show strange behaviour. The scheduler seems to avoid some
> cores. For example on a 12 core machine only 3 cores are used. I see the
> following messages in the logfiles
Ah, 208 day bugfixes went to stable, but not to 2.6.37. Dunno if that
kernel is still being maintained, but please file a bug with opensuse.
-Mike
prev parent reply other threads:[~2012-05-07 4:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 23:33 Strange behaviour after uptime of 208-209 days Christoph Bartoschek
2012-05-07 4:22 ` 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=1336364531.7272.7.camel@marge.simpson.net \
--to=mgalbraith@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ponto@pontohonk.de \
/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