From owner-freebsd-current Mon Jan 26 00:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23062 for current-outgoing; Mon, 26 Jan 1998 00:12:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (tc1-dialin10.nanospace.com [205.199.198.210]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA23057 for ; Mon, 26 Jan 1998 00:12:06 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 526 invoked by uid 100); 26 Jan 1998 08:13:35 -0000 Message-ID: <19980126001331.05717@top.worldcontrol.com> Date: Mon, 26 Jan 1998 00:13:31 -0800 To: Randy Terbush , current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? References: <19980125093559D.randy@covalent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.15i In-Reply-To: <19980125093559D.randy@covalent.net>; from Randy Terbush on Sun, Jan 25, 1998 at 09:35:59AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On %M %N, Randy Terbush wrote: > I have a dual P6 machine with a Cy-16Ye running the latest > current. > > The Hylafax faxgetty and faxq processes spin out of control > chewing up nearly 100% CPU. The same configuration ran without > problems on a single P5 machine running 2.2-STABLE. > > As I begin to dig deeper into this, are there any know problems > with this mix? Just thought you'd like to know you are not alone. faxq on my SMP system does the same thing. -- Brian Litzinger