From owner-freebsd-current  Wed Aug 19 13:09:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA19796
          for freebsd-current-outgoing; Wed, 19 Aug 1998 13:09:04 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19777
          for <current@FreeBSD.ORG>; Wed, 19 Aug 1998 13:08:52 -0700 (PDT)
          (envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
	by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id VAA04654;
	Wed, 19 Aug 1998 21:08:11 +0100 (BST)
	(envelope-from rb@gid.co.uk)
Received: from localhost by seagoon.gid.co.uk; Wed, 19 Aug 1998 20:52:41 +0100 (BST)
Date: Wed, 19 Aug 1998 20:52:40 +0100 (BST)
From: Bob Bishop <rb@gid.co.uk>
X-Sender: rb@seagoon
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: Unwanted sig24 problems?
In-Reply-To: <199808182105.VAA03757@dingo.cdrom.com>
Message-ID: <Pine.BSF.3.96.980819204955.20130A-100000@seagoon>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 18 Aug 1998, 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. [etc]

I had a few days of spurious sig 24s a couple of months back. It went
away...


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message