From owner-freebsd-bugs@FreeBSD.ORG  Tue Mar 20 01:18:01 2012
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 8C4E0106566C
	for <freebsd-bugs@freebsd.org>; Tue, 20 Mar 2012 01:18:01 +0000 (UTC)
	(envelope-from rnoll.bsd@gmail.com)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com
	[209.85.210.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 5D7CA8FC0C
	for <freebsd-bugs@freebsd.org>; Tue, 20 Mar 2012 01:18:01 +0000 (UTC)
Received: by dald2 with SMTP id d2so11582693dal.13
	for <freebsd-bugs@freebsd.org>; Mon, 19 Mar 2012 18:18:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=GLF21HtEu5UjWQlWtG9x4HptoL9iA2pjbx4yYsDnl7Q=;
	b=s3PFztXGWClXWd5RnSCV+XtTAMQDqRdl0YWzg0WhnkX6WFt55itDYHvtykwwcqysLq
	uSd8ojL0IQhzzQhRkePIXPhlFR+3BXwEGNoPP4OHfnAVwYgN1N9qBjBa1/R4OY0xKPwb
	REE3YR+sv4WPx7Lv3nP7/5IiTAWpLDnZlWomWQEUstJvXvJPkwcbfAyPbRUE0Y+84Lfd
	OwUb6m42ougcVNK6d1/a7Ci99p0qDyssagDy0Os5dr9ULSkQmLuvezqZOZyy1mxhfcwO
	dPGiSzbwdnhUi6h7VFaZCgGkU/GqhtXurt6BdEhKxTIWlMGEJQmNhL1kgPP56h62owAV
	vkVg==
MIME-Version: 1.0
Received: by 10.68.223.42 with SMTP id qr10mr44762444pbc.127.1332206280911;
	Mon, 19 Mar 2012 18:18:00 -0700 (PDT)
Received: by 10.68.23.40 with HTTP; Mon, 19 Mar 2012 18:18:00 -0700 (PDT)
In-Reply-To: <201203140430.q2E4U1Wi036795@freefall.freebsd.org>
References: <201203140429.q2E4ToP6006281@red.freebsd.org>
	<201203140430.q2E4U1Wi036795@freefall.freebsd.org>
Date: Mon, 19 Mar 2012 18:18:00 -0700
Message-ID: <CAGzpdJAi9c_sn60T02A6Lbsh-c-GNq2UuEPsUoKvELb9gN_twA@mail.gmail.com>
From: Ryan Noll <rnoll.bsd@gmail.com>
To: freebsd-bugs@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Re: kern/166071: High CPU Utilization on HylaFAX processes
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2012 01:18:01 -0000

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