From owner-freebsd-current Wed Aug 19 20:01:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28819 for freebsd-current-outgoing; Wed, 19 Aug 1998 20:01:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28793 for ; Wed, 19 Aug 1998 20:01:05 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA17907; Wed, 19 Aug 1998 22:54:10 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808192154.WAA17907@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Unwanted sig24 problems? In-reply-to: Your message of "Tue, 18 Aug 1998 21:05:03 -0000." <199808182105.VAA03757@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Aug 1998 22:54:08 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The only way this can be happening AFAICT is if the value pointed at by the global ``timecounter'' is fluctuating (going backwards).... Does making ``struct timecounter *timecounter'' volatile in kern_clock.c help ? I can't tell 'cos the machine that I got this problem with was given back.... > 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 > also seeing user processes (emacs, exmh, anything long-lived and busy) > dying similarly. > > dingo:~>limit > cputime unlimited > filesize unlimited > datasize 524288 kbytes > stacksize 65536 kbytes > coredumpsize unlimited > memoryuse 32768 kbytes > descriptors 1024 > memorylocked unlimited > maxproc 64 > > So I'm fairly happy this isn't a resource configuration problem. Any > ideas? (Very irritating this is. 8( ) > > I managed to reproduce the problem quite quickly with 'top' running > with a refresh delay of 0 in an xterm, unfortunately it took the shell > with it at about 4 minutes. (Slightly over 4:15, unfortunately). > > -- > \\ 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 -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message