From: sbs <gexlie@gmail.com>
To: "Alistair John Strachan" <alistair@devzero.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: high %CPU values after upgrading to the last stable kernel
Date: Thu, 23 Oct 2008 18:55:23 +0400 [thread overview]
Message-ID: <53cc795f0810230755q4eac0111y4d2366d1ac99b741@mail.gmail.com> (raw)
In-Reply-To: <200810230155.48344.alistair@devzero.co.uk>
thank you
will be waiting until it gets fixed
On Thu, Oct 23, 2008 at 4:55 AM, Alistair John Strachan
<alistair@devzero.co.uk> wrote:
> 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.
>
prev parent reply other threads:[~2008-10-23 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 19:37 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
2008-10-23 14:55 ` sbs [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=53cc795f0810230755q4eac0111y4d2366d1ac99b741@mail.gmail.com \
--to=gexlie@gmail.com \
--cc=alistair@devzero.co.uk \
--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
all inboxes | Powered by JetHome®