[mythtv-users] Lirc "pauses" ?

[Phil Bridges]

On 4/27/07, David Frascone <dave at frascone.com> wrote:
>
>
> Michael T. Dean wrote:
> > On 04/27/2007 01:28 PM, David Frascone wrote:
> >
> >> Michael T. Dean wrote:
> >>
> >>
> >>> On 04/27/2007 12:57 PM, David Frascone wrote:
> >>>
> >>>
> >>>> For some reason, lirc takes 30s to 1 minute pauses now and then.  So,
> >>>> the remote will work fine -- then it wont -- for a long period.  Then,
> >>>> it will suddenly work again.
> >>>>
> >>>> I've straced it a bit, and it seems to still receive the IR signal --
> >>>> but it doesn't write anything to the application.  (In other words, the
> >>>> device sends out data, lircd receives it, but lircd does *not* send the
> >>>> data to mythfrontend).
> >>>>
> >>>> Has anyone else seen this behavior?  I'm using lircd_serial.
> >>>>
> >>>>
> >>>> If not, I'll head over to the lircd lists.
> >>>>
> >>> http://svn.mythtv.org/trac/ticket/3047 , and specifically
> >>> http://svn.mythtv.org/trac/ticket/3047#comment:3 , perhaps.  I'm pretty
> >>> sure the same will apply for lircd.
> >>>
> >> They do look similar, but my frontend does *not* hang.  And, from doing
> >> an strace, lircd doesn't seem to hang either -- unless you think a
> >> particular thread (the lirc receiver thread) is hanging. . .
> >>
> >> When it happnes, irw does *not* work either.  But -- the frontend is
> >> still playing TV recordings, etc, and the keyboard works fine.
> >>
> >
> > The only reason mythfrontend was "hanging" there was because it is
> > written to wait for the channel change script to complete.  The
> > important part is to ensure the lircd process has access to the real
> > time clock (including permissions).
> >
> >
> The lircd process runs as root -- so it has access to everything.  I'm
> assuming that rtc support is built in and working, since this works:
>
> root at myth-fe:/proc# cat /proc/driver/rtc
> rtc_time        : 18:35:26
> rtc_date        : 2007-04-27
> rtc_epoch       : 1900
> alarm           : 00:00:20
> DST_enable      : no
> BCD             : yes
> 24hr            : yes
> square_wave     : no
> alarm_IRQ       : no
> update_IRQ      : no
> periodic_IRQ    : yes
> periodic_freq   : 1024
> batt_status     : okay
>
>
> Anything else I should check?
>
> -Dave

Did you ever solve this?  I get the same problem on my frontend-only machine.