[mythtv] 0.21 Firewire bus reset every 60 seconds?

Eric Smith erictsmith at gmail.com
Tue Sep 30 13:49:42 UTC 2008


On Mon, Jun 16, 2008 at 10:49 AM, Derek Atkins <warlord at mit.edu> wrote:

> Hi,
>
> Derek Atkins <warlord at MIT.EDU> writes:
>
> > Here's an example of the backend log between the 60-second "okay period":
> >
> > 2008-06-11 08:43:37.498 LFireDev(000E5CFFFE5AF9A5): SignalReset(86->87)
> > 2008-06-11 08:43:37.553 LFireDev(000E5CFFFE5AF9A5): SignalReset(86->87):
> Updating device list -- begin
> > 2008-06-11 08:43:37.815 LFireDev(000E5CFFFE5AF9A5): SignalReset(86->87):
> Updating device list -- end
> > 2008-06-11 08:43:37.917 LFireDev(000E5CFFFE5AF9A5), Warning: No Input in
> 50 msec...
> > 2008-06-11 08:44:37.501 LFireDev(000E5CFFFE5AF9A5), Warning: No Input in
> 100 msec...
> > ...
>
> After updating libraw1394 from 1.2.1 to 1.3.0 this kind of error seems
> to have been reduced..  But it also seems to be a problem if the
> firewire broadcast bus isn't completely synched.  For example, the
> myth box was rebooted yesterday and then the first recording had
> this issue.  But then I reset the bus manually using firewire_tester
> (which, by the way, took two or three tries before it synced!)..
> and then my recording this morning was fine.
>
> So something weird is still going on, but at least the libraw upgrade
> seems to have helped.
>
> Any other suggestions?  My next step is to setup a script to run
> firewire_tester on boot-up to make sure the bus is stable before
> mythbackend runs.
>
> -derek
>

I also see this issue, somewhat infrequently, but enough to be a problem.
Does anyone have any suggestions on things I could check to resolve it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20080930/2d744c4f/attachment.htm 


More information about the mythtv-dev mailing list