From owner-freebsd-bugs@freebsd.org  Sun Apr  3 00:35:37 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6703ADE279
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun,  3 Apr 2016 00:35:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C9DBC1730
 for <freebsd-bugs@FreeBSD.org>; Sun,  3 Apr 2016 00:35:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u330ZaS1052844
 for <freebsd-bugs@FreeBSD.org>; Sun, 3 Apr 2016 00:35:37 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 166071] High CPU Utilization on HylaFAX processes
Date: Sun, 03 Apr 2016 00:35:37 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 9.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: rnoll.bsd@gmail.com
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-166071-8-34bTRwr7B3@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-166071-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-166071-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Apr 2016 00:35:38 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166071

--- Comment #9 from rnoll.bsd@gmail.com ---
I recently needed to reconfigure my system, and I ran in to this same probl=
em
in FreeBSD 10.2-p7. The configuration changed to FreeSwitch acting as the s=
oft
modem instead of a USB or serial modem (MultiTech).

However, I ran in to same difficulties with a HylaFax process utilizing 100%
CPU. The solution I found that was easiest is to use HylaFax+ instead of
HylaFax from ports. HylaFax+ does not require the use of
CONFIG_OPENFIFO=3D"O_RDWR" and CONFIG_FIFOBUG=3D"yes" compile flags.

If installing on system where GCC is not the default compiler, install GCC =
from
ports before running configure for HylaFax+.

Further, maybe a HylaFax+ port might be a good idea.

--=20
You are receiving this mail because:
You are the assignee for the bug.=