From owner-freebsd-ports@FreeBSD.ORG Thu Jul 3 09:44:55 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B4435E38 for ; Thu, 3 Jul 2014 09:44:55 +0000 (UTC) Received: from mailhost.madaboutcable.com (mailhost.madaboutcable.com [88.96.254.164]) (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 4ECCA218E for ; Thu, 3 Jul 2014 09:44:54 +0000 (UTC) Received: from ws-w702-dr.ksm.pri ([192.168.5.50] helo=[127.0.0.1]) by mailhost.madaboutcable.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from ) id 1X2dZC-000Amo-OV; Thu, 03 Jul 2014 10:44:45 +0100 Message-ID: <53B52602.5080708@ksm.co.uk> Date: Thu, 03 Jul 2014 10:44:34 +0100 From: Daren Organization: KSM Limited User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Konstantin Belousov Subject: Re: Hylafax on FreeBSD 10 and 100% CPU References: <53B3D254.20901@ksm.co.uk> <20140702222454.GA93733@kib.kiev.ua> In-Reply-To: <20140702222454.GA93733@kib.kiev.ua> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 140702-1, 02/07/2014), Outbound message X-Antivirus-Status: Clean X-Spam-Score: -1.0 (-) Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2014 09:44:55 -0000 On 02/07/2014 23:24, Konstantin Belousov wrote: > On Wed, Jul 02, 2014 at 10:35:16AM +0100, Daren wrote: >> Hi >> >> I've tried installing Hylafax from ports on fresh FreeBSD 10. We >> previously had it running on an 8.2 system without issue. >> >> After starting faxgetty creeps up to and stays on 100% cpu. I did find >> a previous PR for this >> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166071) which has the >> status of resolved fixed although people have requested it be re-opened >> as the problem is still occurring for them as well. >> >> I can add another comment to this if it helps get it noticed again, but >> my knowledge with C etc is non-existent to be able to help with it, >> although searching has come up with a similar/same issue on dragonflybsd >> (http://bugs.dragonflybsd.org/issues/2028) >> >> Does anyone know if this is being looked at? >> > > I once looked at the source code of the program, and the ktrace reports > in the mentioned PR 166071 are consistent with what I remember I saw in > code, as well as what was discussed at that time. > > If you look at the kdump, you note the series of read(2) syscalls on the > same FIFO, which return 0, the indicator of the EOF. AFAIR, the Hylafax > code does not check for the EOF condition and just spins trying to > read more data. Select(2) returns the fd for EOF'ed FIFO ready, because > the read(2) indeed does not block at EOF. > > My decision at that time was that the issue is the program bug. > I do not use the program, and cannot set it up locally to even try > coding the fix. > Thanks for the answer. Unfortunately I know nothing about these sorts of things so it doesn't mean much to me! I'll try posting to the hylafax list with this, but I'm sure I came across this previously mentioned to them on a search and they made out it was an OS bug - although now I cannot find it again. Cheers Daren