Date: Thu, 3 Jul 2014 13:09:30 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Daren <daren.russell@ksm.co.uk> Cc: freebsd-ports@freebsd.org Subject: Re: Hylafax on FreeBSD 10 and 100% CPU Message-ID: <20140703100930.GC93733@kib.kiev.ua> In-Reply-To: <53B52602.5080708@ksm.co.uk> References: <53B3D254.20901@ksm.co.uk> <20140702222454.GA93733@kib.kiev.ua> <53B52602.5080708@ksm.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--+lyI8POnKyxW93e8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 03, 2014 at 10:44:34AM +0100, Daren wrote: > 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=3D166071) 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 dragonflyb= sd > >> (http://bugs.dragonflybsd.org/issues/2028) > >> > >> Does anyone know if this is being looked at? > >> > >=20 > > 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. > >=20 > > 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. > >=20 > > 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. > >=20 >=20 > Thanks for the answer. Unfortunately I know nothing about these sorts > of things so it doesn't mean much to me! >=20 > 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. I am happy to listen to the authors of this application, in particular, I am interested in exact description of what behaviour do they expect. --+lyI8POnKyxW93e8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJTtSvaAAoJEJDCuSvBvK1BrrgP/RQvKRMsLaudQTakqqPXz/XY aAsWaGEsyb9l0+uQj96c9MJayZvn2WW2NGRu52b7ZwdiTAqAYZaXLPEy3eRhxQ1c jWZp9/zEMLg3Od5Svw4yBkzLR1c3NcTGpYz2uVrQ4WI+CIa++yJwzIKmKpjI7r+B p+I+J9ZA/iwvpWS2LlwMntakQFT9M6m82iGBgglBIp8PoWHDKLdLE4fBxDoVXFCj KIvJXpMwHtbyYxkZohsH130bTLhLaeUDeM/T4UsZdA6OAOjeWf1QrEQr/vC31LQj 7U9Sp4G8U0RduCGG6csrIzCAqdqoNZPA0iO52uenaqWxLhZMIeDCz14N1n7LDzvf Dv0XU5KYztXHc1xtiLUU1PD9q4J5+g1y1jqFBgSvlSBT0JOQtZjdGX5HdQ5SvPl1 t8BdEbVRVYereFOzqN+7IHjhonYgJUiGtxZRgsb3EUNjhCyL3jc0rPG/Hl+Uq1kR Ue/WFvjM0A/TOvkW6V/1ifdSM0VPJ7f/cP5FDWVUXliK6/NB49jnbm7EDIaSw5sT POv9sbwZHuuystoDZxIXN2p7szbqp03z6yOZdgToB8/hSexWYWgUidjJ6REwli78 XaGsLsrsdzh8ZgnQExSmukkbBHljjTbJcEFq9QYir/M+7w56iSfNqyBWsRPRFPMj m9PotCfBlB0iIP6calIU =m9aY -----END PGP SIGNATURE----- --+lyI8POnKyxW93e8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140703100930.GC93733>