lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 23 Oct 2008 01:55:48 +0100
From:	Alistair John Strachan <alistair@...zero.co.uk>
To:	"Ray Lee" <ray-lk@...rabbit.org>
Cc:	"Frédéric Weisbecker" <fweisbec@...il.com>,
	sbs <gexlie@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: high %CPU values after upgrading to the last stable kernel

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@...il.com> 
wrote:
> > 2008/10/22 sbs <gexlie@...il.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.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ