From owner-freebsd-current Mon Jan 26 02:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06165 for current-outgoing; Mon, 26 Jan 1998 02:14:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06155 for ; Mon, 26 Jan 1998 02:14:36 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id FAA00431; Mon, 26 Jan 1998 05:14:29 -0500 (EST) (envelope-from toor) Message-Id: <199801261014.FAA00431@dyson.iquest.net> Subject: Re: Cyclades/Hylafax/SMP select problems? In-Reply-To: <19980126001331.05717@top.worldcontrol.com> from "brian@worldcontrol.com" at "Jan 26, 98 00:13:31 am" To: brian@worldcontrol.com Date: Mon, 26 Jan 1998 05:14:28 -0500 (EST) Cc: randy@covalent.net, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk brian@worldcontrol.com said: > 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. > 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. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.