Date: Mon, 2 Apr 2012 06:40:14 GMT From: Mark Linimon <linimon@lonesome.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/166071: High CPU Utilization on HylaFAX processes Message-ID: <201204020640.q326eEVo065152@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/166071; it has been noted by GNATS. From: Mark Linimon <linimon@lonesome.com> 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 <rnoll.bsd@gmail.com> ----- Date: Mon, 19 Mar 2012 18:18:00 -0700 From: Ryan Noll <rnoll.bsd@gmail.com> 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 -----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204020640.q326eEVo065152>