Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Feb 2006 19:45:40 -0500
From:      Kris Kennaway <kris@obsecurity.org>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        Mike Jakubik <mikej@rogers.com>, Poul-Henning Kamp <phk@phk.freebsd.dk>, current@freebsd.org
Subject:   Re: [TEST/REVIEW] cpu time accounting patch, step 2
Message-ID:  <20060211004540.GA73169@xor.obsecurity.org>
In-Reply-To: <20060211002451.GA72714@xor.obsecurity.org>
References:  <43EC2C4C.5000709@rogers.com> <3725.1139560381@critter.freebsd.dk> <20060211002451.GA72714@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 10, 2006 at 07:24:51PM -0500, Kris Kennaway wrote:
> On Fri, Feb 10, 2006 at 08:33:01AM +0000, Poul-Henning Kamp wrote:
> > In message <43EC2C4C.5000709@rogers.com>, Mike Jakubik writes:
> > >Poul-Henning Kamp wrote:
> > >> 	http://phk.freebsd.dk/patch/cputime.patch=20
> > >>
> > >> This patch enables the new cpu time accounting method for i386 with
> > >> TSC, all amd64 and sparc64 (?) and i386 with Geode cpu.
> > >>  =20
> > >
> > >I got a bunch of these during the first bootup.
> > >
> > >--
> > >calcru: runtime went backwards from 1227916 usec to 1227883 usec for p=
id=20
> > >30 (pagezero)
> >=20
> > Yes, that will happen right now until the calibration of the TSC's
> > max frequency is completed.
> >=20
> > I'm analyzing various solutions to that.
>=20
> I'm getting it with your committed patch too..are you aware of it?

In addition to the continuous spam of these calcru messages on the
console (>10/sec), I'm getting the following:

Feb 11 09:41:00 dosirak kernel: pid 8831 (bsdtar), uid 0, was killed: excee=
ded maximum CPU limit
Feb 11 09:41:06 dosirak kernel: pid 8850 (bsdtar), uid 0, was killed: excee=
ded maximum CPU limit
Feb 11 09:41:09 dosirak kernel: pid 9479 (umount), uid 0, was killed: excee=
ded maximum CPU limit

which suggests CPU time limits are also hosed (these processes ran for
a few seconds at best, not an hour, which is the ulimit -t value).

Again, this is with the code you already committed to CVS.

Kris


--1yeeQ81UyVL57Vl7
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFD7TO0Wry0BWjoQKURApjRAJ4q48EGFZTJtD1cuE0Kqg6+yor0hwCg4FAu
JE0T4vo9DtxkLAA6BCPpFNk=
=y7cl
-----END PGP SIGNATURE-----

--1yeeQ81UyVL57Vl7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060211004540.GA73169>