From owner-freebsd-bugs@FreeBSD.ORG Mon Apr 2 06:40:14 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 527DD106564A for ; Mon, 2 Apr 2012 06:40:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3058FC18 for ; Mon, 2 Apr 2012 06:40:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q326eEjZ065153 for ; Mon, 2 Apr 2012 06:40:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q326eEVo065152; Mon, 2 Apr 2012 06:40:14 GMT (envelope-from gnats) Date: Mon, 2 Apr 2012 06:40:14 GMT Message-Id: <201204020640.q326eEVo065152@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Mark Linimon Cc: Subject: Re: kern/166071: High CPU Utilization on HylaFAX processes X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2012 06:40:14 -0000 The following reply was made to PR kern/166071; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/166071: High CPU Utilization on HylaFAX processes Date: Mon, 2 Apr 2012 01:37:53 -0500 ----- Forwarded message from Ryan Noll ----- Date: Mon, 19 Mar 2012 18:18:00 -0700 From: Ryan Noll To: freebsd-bugs@freebsd.org Subject: Re: kern/166071: High CPU Utilization on HylaFAX processes The PR is available at: http://www.freebsd.org/cgi/query-pr.cgi?pr=166071. Below is some more information about this particular bug. I thought this could be a kernel bug, but maybe it could be a bug in the program that the 9.0-RELEASE kernel exposed. If the faxq and hfaxd processes are started (via their startup script) and then faxgetty is started all appears fine. However, while sending a fax the faxgetty process is again at 100%. The truss output for faxgetty is not included because it is the same as stated earlier. After the fax has completed, faxgetty remains at 100%. Should this still be considered a kernel bug or should I try contacting the HylaFAX maintainers? Note that the configuration is run in a jail with a USB (cuaU0, MultiTech MultiModem MT9234ZBA-USB-CDC) and serial modem (cuau0, MultiTech MultiModem MT9234ZBA-NAM). This configuration did work under 8.2-RELEASE-p6. Also, this message is shown during the initial setup probe: stty: stdout appears redirected, but stdin is the control descriptor. Thank you for your time. v/r, Ryan ----- End forwarded message -----