Discussion:
[Bug 637] faxq 100% CPU usage
b***@hylafax.org
2005-03-09 13:41:13 UTC
Permalink
http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=637





------- Additional Comments From ***@ifax.com 2005-03-09 08:41 -------
So, what else is writing to the FIFO? lsof or fuser should be able to tell you.

What kernel version are you running?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

____________________ HylaFAX(tm) Developers Mailing List ____________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-devel-***@hylafax.org < /dev/null
b***@hylafax.org
2005-03-09 13:41:35 UTC
Permalink
http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=637

***@ifax.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@ifax.com





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

____________________ HylaFAX(tm) Developers Mailing List ____________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-devel-***@hylafax.org < /dev/null
b***@hylafax.org
2005-03-10 08:54:08 UTC
Permalink
http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=637





------- Additional Comments From ***@alt001.com 2005-03-10 03:54 -------
No other processes are accessing the FIFO. There is a FIFO.faxCAPI, which is accessed (only) by c2faxrecv, from capi4hylafax-01.02.02.
Kernel is stock 2.4.28, with a few patches (linux-default-bsd-mppe, i2c-2.8.8, lm_sensors-2.8.8, bcm5700-7.3.5, pptp-conntrack-nat and ea+acl+nfsacl+sec-2.4.25-0.8.71)



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

____________________ HylaFAX(tm) Developers Mailing List ____________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-devel-***@hylafax.org < /dev/null
b***@hylafax.org
2005-03-10 13:15:05 UTC
Permalink
http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=637





------- Additional Comments From ***@ifax.com 2005-03-10 08:15 -------
Any chance you can try it on a stock kernel, without all the extra patches.

The reason I'm driving this way is because faxq is clearly doing things
correctly, as it's been programmed to.

Your strace shows that:

1) faxq uses select to request of the kernel if data is available for
reading.
2) The kernel returns that yes, there is data available.
3) We read it and act on any messages.
4) Repeat

There is something with this setup which is causing the kernel to
continuously tell us there is something to read, but nothing is read.

Is your spool over NFS? Any funky EA, or ACL on the FIFO?




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

____________________ HylaFAX(tm) Developers Mailing List ____________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-devel-***@hylafax.org < /dev/null
b***@hylafax.org
2005-03-10 15:22:40 UTC
Permalink
http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=637





------- Additional Comments From ***@alt001.com 2005-03-10 10:22 -------
Stock kernel 2.4.28 without patches shows identical behaviour. The spool is on ext3, no special things. Would etc/config* or the kernelconfig be of any use?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

____________________ HylaFAX(tm) Developers Mailing List ____________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-devel-***@hylafax.org < /dev/null
b***@hylafax.org
2005-03-10 16:16:26 UTC
Permalink
http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=637





------- Additional Comments From ***@alt001.com 2005-03-10 11:16 -------
It turns out faxq only starts looping after running "faxmodem faxCAPI" or after starting c2faxrecv.
I suspect an old version of capi4hylafax (currently version 01.02.02). I'll try to find a newer version
and see if that changes anything and i'll post the results here.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

____________________ HylaFAX(tm) Developers Mailing List ____________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-devel-***@hylafax.org < /dev/null
Loading...