[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20111129212554.GA2955@mac.home>
Date: Tue, 29 Nov 2011 22:25:54 +0100
From: Tino Keitel <tino.keitel@...ei.de>
To: linux-kernel@...r.kernel.org
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
"Artem S. Tashkinov" <t.artem@...os.com>
Subject: Re: [REGRESSION] [Linux 3.2] top/htop and all other CPU usage
metering applications has gone crackers
On Mon, Nov 28, 2011 at 20:55:34 +0100, Tino Keitel wrote:
> 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@...e.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.
Hi,
looks fine so far with the git tree from commit
401d0069cb344f401bc9d264c31db55876ff78c0 and
a25cac5198d4ff2842ccca63b423962848ad24b2 reverted.
Regards,
Tino
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists