Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Jul 2014 01:24:54 +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:  <20140702222454.GA93733@kib.kiev.ua>
In-Reply-To: <53B3D254.20901@ksm.co.uk>
References:  <53B3D254.20901@ksm.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help

--SkORD/+6TY6lrvPo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 02, 2014 at 10:35:16AM +0100, Daren wrote:
> Hi
>=20
> I've tried installing Hylafax from ports on fresh FreeBSD 10.  We
> previously had it running on an 8.2 system without issue.
>=20
> 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.
>=20
> 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)
>=20
> 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.

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.

--SkORD/+6TY6lrvPo
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJTtIa2AAoJEJDCuSvBvK1BYUIP/RToL1HJMVPO+WMW6NJM7xO0
+h4ghevsnr++HBRGZITgfol3TmrZaDDhhN3csOh8Koq/6iWdi74nC8z7/gOodkEe
vQkXMMv2fT62gfthK0NVzanDRh3UPT8y3uRMGNmcmqftQwsFTdBT7OxHtTqhQWgw
eNTe/w4sRHhndHdv8NGMAPSDmGE39spEGOVnHHyFjguTZ+ibXNpnMJHwyVmh/ktP
M4xpwsjA9CqsJy+2N8d2quWVzwWUuGgIwxC+3o3FIlnRY6MNpHUWcHsBFcKOXGdK
+SOLOOmW6NW1Jg5eFaxIu7CvALia+mgCsaIvdVfPkHF7nMbQKM1dxawNLwg/mwCu
5pG9J6eiB2b1z3zgS7WsgKm4kp0jdcFMFjtHPL4muOq5rmyTCjIKu5kEG704q2Cg
txHAfda6nAHnoS43thiRUuoTAAJWhu5hA9lqGi6eZM18elF8UJAhry9M750USDuz
FLWpmXFKtyD7dpuy4s7Ww7D4LOxxcpaPLgWIrZnwMJ4tLZmUtmQu4+9wf2Fr4FBe
F71W+Nx5ho5IuvgLwkKQJCQaEWbd+GPHeKJxXwdkZiDJ0HRLRWVEjy9QVBvi9rH1
EoFUKOk/g+ag0+KwLOTSqOUK7/QBSDg+MWUDXRyA3morZgxhhzYAhuXXDgxxSEgQ
KjMYAjD2VL8z3UBwUwDo
=rk+u
-----END PGP SIGNATURE-----

--SkORD/+6TY6lrvPo--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140702222454.GA93733>