From owner-freebsd-current Mon Jan 26 00:59:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27861 for current-outgoing; Mon, 26 Jan 1998 00:59:13 -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 AAA27856 for ; Mon, 26 Jan 1998 00:59:10 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 1214 invoked by uid 100); 26 Jan 1998 08:54:00 -0000 Message-ID: <19980126005356.16731@top.worldcontrol.com> Date: Mon, 26 Jan 1998 00:53:56 -0800 To: Amancio Hasty , brian@worldcontrol.com Cc: Randy Terbush , current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? References: <19980126001331.05717@top.worldcontrol.com> <199801260824.AAA02827@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.15i In-Reply-To: <199801260824.AAA02827@rah.star-gate.com>; from Amancio Hasty on Mon, Jan 26, 1998 at 12:24:27AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > > On %M %N, Randy Terbush wrote: > > > The Hylafax faxgetty and faxq processes spin out of control > > > chewing up nearly 100% CPU. Brian Litzinger wrote: > > Just thought you'd like to know you are not alone. faxq on > > my SMP system does the same thing. On %M %N, Amancio Hasty wrote: > Any clues as to where is spending its time?? The program gives no clues. Regretably it seems to perpetually be in the RUN state. However, I have a guess. I suspect that a select (poll?) call is returning with nothing set. The program is getting into an infinite loop calling select. I've found that the program does work. It is just consuming 100% of 1 CPU. I believe the problem is not SMP related. I.E. it will happen in uni-processor mode too. -- Brian Litzinger