public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@tikei.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, "Artem S. Tashkinov" <t.artem@lycos.com>
Subject: Re: [REGRESSION] [Linux 3.2] top/htop and all other CPU usage metering applications has gone crackers
Date: Mon, 28 Nov 2011 20:55:34 +0100	[thread overview]
Message-ID: <20111128195533.GA26460@mac.home> (raw)
In-Reply-To: <201111271245.57772.rjw@sisk.pl>

On Sun, Nov 27, 2011 at 12:45:57 +0100, Rafael J. Wysocki wrote:
> On Sunday, November 27, 2011, Tino Keitel wrote:
> > On Thu, Nov 24, 2011 at 21:05:53 +0100, Tino Keitel wrote:
> > > On Thu, Nov 24, 2011 at 10:30:15 +0000, Artem S. Tashkinov wrote:
> > > > Hello,
> > > > 
> > > > I'd like to report a weird regression in Linux 3.2 (running rc3 now) - all CPU metering applications have gone terribly mad
> > > > under this kernel:
> > > 
> > > I get the same using top, htop and the gnome system monitor with kernel
> > > 3.2 on a Sandy Bridge quad core box, running Debian unstable.
> > 
> > I just tested 3.2-rc2, and see the same bug.
> 
> I'm seeing that too on one of my test boxes, but not all the time
> (i.e. there are periods in which the readings are correct).  The other boxes
> I've tested with 3.2-rc are fine in that respect.
> 
> Also, it seems that it shows 100%-(real load) when it is wrong.  So, it looks
> like there's an overflow somewhere in the CPU load measuring code, at least
> on some CPUs.

Hi,

I reverted this commit and so far it looks good:

commit a25cac5198d4ff2842ccca63b423962848ad24b2
Author: Michal Hocko <mhocko@suse.cz>
Date:   Wed Aug 24 09:40:25 2011 +0200

    proc: Consider NO_HZ when printing idle and iowait times

I'll report back tomorrow how the kernel behaves.

Regards,
Tino

  parent reply	other threads:[~2011-11-28 19:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 10:30 [REGRESSION] [Linux 3.2] top/htop and all other CPU usage metering applications has gone crackers Artem S. Tashkinov
2011-11-24 20:05 ` Tino Keitel
2011-11-27 11:04   ` Tino Keitel
2011-11-27 11:45     ` Rafael J. Wysocki
2011-11-27 11:45       ` Tino Keitel
2011-11-27 11:56         ` Rafael J. Wysocki
2011-11-27 11:57       ` Artem S. Tashkinov
2011-11-28 19:55       ` Tino Keitel [this message]
2011-11-28 20:19         ` Rafael J. Wysocki
2011-11-28 21:41           ` Michal Hocko
2011-11-28 21:43             ` Michal Hocko
2011-11-28 21:48             ` Michal Hocko
2011-11-29  8:14             ` Michal Hocko
2011-11-29 21:25         ` Tino Keitel
2011-11-29 21:16 ` Maciej Rutecki

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=20111128195533.GA26460@mac.home \
    --to=tino.keitel@tikei.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=t.artem@lycos.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