public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alistair John Strachan <alistair@devzero.co.uk>
To: "Ray Lee" <ray-lk@madrabbit.org>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
	sbs <gexlie@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: high %CPU values after upgrading to the last stable kernel
Date: Thu, 23 Oct 2008 01:55:48 +0100	[thread overview]
Message-ID: <200810230155.48344.alistair@devzero.co.uk> (raw)
In-Reply-To: <2c0942db0810221540l4da55d92n2b55124908d08d3@mail.gmail.com>

On Wednesday 22 October 2008 23:40:54 Ray Lee wrote:
> On Wed, Oct 22, 2008 at 2:04 PM, Frédéric Weisbecker <fweisbec@gmail.com> 
wrote:
> > 2008/10/22 sbs <gexlie@gmail.com>:
[snip]
> >> should i upgrade procps or downgrade kernel then to get proper values
> >> back? :) or is it a feature of the new kernel?
> >>
> >> thank you
> >
> > Hi,
> >
> > It really depends on what your box is doing at the time you capture
> > the cpu usage.
> > And it really depends too of your kernel config...
>
> It really shouldn't, we're talking about /proc which is supposed to be
> a stable userspace interface.
>
> Try upgrading your procps, there's a chance it's just so ancient that
> it accidentally got broken. However, if that fixes your problem, then
> please report back with a subject line of "/proc API breakage" or
> somesuch, to get the proper attention to the issue.

This is a known kernel bug that for some reason wasn't fixed before 2.6.27 was 
released. See http://bugzilla.kernel.org/show_bug.cgi?id=11209 for details.

It would probably be useful if the OP added himself to the CC list, so Peter 
can get some more details about the box.

-- 
Cheers,
Alistair.

  reply	other threads:[~2008-10-23  1:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 19:37 high %CPU values after upgrading to the last stable kernel sbs
2008-10-22 21:04 ` Frédéric Weisbecker
2008-10-22 22:40   ` Ray Lee
2008-10-23  0:55     ` Alistair John Strachan [this message]
2008-10-23 14:55       ` sbs

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=200810230155.48344.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --cc=fweisbec@gmail.com \
    --cc=gexlie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-lk@madrabbit.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