From owner-freebsd-current Mon Jan 26 03:20:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09770 for current-outgoing; Mon, 26 Jan 1998 03:20:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sierra.covalent.net (sierra.covalent.net [208.214.58.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09765; Mon, 26 Jan 1998 03:20:35 -0800 (PST) (envelope-from randy@covalent.net) Received: from localhost (localhost [127.0.0.1]) by sierra.covalent.net (8.8.8/8.8.2) with ESMTP id FAA21924; Mon, 26 Jan 1998 05:20:34 -0600 (CST) To: dyson@FreeBSD.ORG Cc: brian@worldcontrol.com, current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? In-Reply-To: Your message of "Mon, 26 Jan 1998 05:14:28 -0500 (EST)" <199801261014.FAA00431@dyson.iquest.net> References: <199801261014.FAA00431@dyson.iquest.net> X-Mailer: Mew version 1.92.4 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980126052032B.randy@covalent.net> Date: Mon, 26 Jan 1998 05:20:32 -0600 From: Randy Terbush X-Dispatcher: imput version 971024 Lines: 23 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk "John S. Dyson" wrote: > > > 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. > > > Sometimes the output of ktrace or truss can be useful. Also the > contents of /proc//map sometimes helps with hints as to > what is going on. Seems that a change to open the FIFO O_RDWR solves the problem. Apparently, select() is returning when it should not be. This must be a new bug in select().