|
From: David F. <da...@fr...> - 2007-05-03 13:44:47
|
This is still happening with CVS version -- any ideas where to start debugging? -Dave David Frascone wrote: > So -- confirmation that I'm not alone -- at least that's something ;) > > I'll check out the cvs tree and build from source if that doesnt' fix > it, I'll start debugging. > > -Dave > > Jake Briggs wrote: > >> I am seeing this behaviour as well, using 0.8 >> >> captainspaulding ~ # lircd -v >> lircd 0.8.0 >> captainspaulding ~ # >> >> I see there is a new version of lirc :) Might have to try updating.... >> >> jake >> >> >> David Frascone wrote: >> >>> I'm using lirc_serial / lircd, and I'm seeing strange behavior. >>> Every once in a while, lircd stops sending remote events to apps. >>> This behavior lasts for a minute or so -- then it starts working >>> again. No logs, no errors, nothing in dmesg. >>> >>> I've run strace on it (strace -p <lircd pid>), and I can see that >>> lircd is getting data from /dev/lirc0 when a button is pressed on the >>> remote -- but it does *not* write any data out to applications >>> waiting for data. The machine is not particularly busy when this >>> happens. I'm running version 0.8.1. >>> >>> So -- the questions: >>> Has anyone else seen this behavior? >>> What would be the best way to debug? I didn't see anything in the >>> man pages about increasing the debug level. >>> Should I attempt to reproduce with code from CVS? >>> >>> Thanks in advance, >>> >>> >>> -Dave >>> >>> >>> > > |