Date: Wed, 19 Aug 1998 16:35:14 +0000 From: Mike Smith <mike@smith.net.au> To: Pierre Beyssac <Pierre.Beyssac@hsc.fr> Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Subject: Re: Unwanted sig24 problems? Message-ID: <199808191635.QAA03487@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 19 Aug 1998 17:31:49 %2B0200." <19980819173149.A21323@mars.hsc.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, Aug 18, 1998 at 09:05:03PM +0000, Mike Smith wrote: > > An odd one here; I recently reinstalled -current on my laptop, and with > > a kernel built this morning I am getting (important) processes killed > > with SIGXCPU. (eg. the X server). I start the server by hand, and I'm > > Many (maybe half a dozen) persons have reported similar problems > on this list since about June; I'm having it sometimes in make > world, and it's not a resource limit problem. I'm running xntpd; > somehow it seems the problem occur less frequently when stopping > xntpd. I haven't tried recent kernels yet. > > > So I'm fairly happy this isn't a resource configuration problem. Any > > ideas? (Very irritating this is. 8( ) > > IIRC, it was because the process CPU time becomes negative. Since > it's an unsigned integer, it's over even the "unlimited" limit and > the process is killed. Nobody seems to know exactly _why_ it becomes > negative though. Ah. This sounds like the 'calcru: negative...' message. Looks like Poul has some more work to do still. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808191635.QAA03487>