[mythtv-users] Firewire P2P connection stops sending input after end of recording

Kevin Worth kworth at gmail.com
Thu Aug 1 17:42:15 UTC 2013


I thought that fixing n_p2p_connections=1 at startup might have
resolved the issue I was seeing (as it made firewire_tester much
happier), but it appears it's something else/different, as the issue
persists and when looking through my logs, the below messages exist
prior to my adding plugctl commands to my startup script. It appears
something doesn't go well after a recording finishes...

"dmesg | grep -i firewire" shows nothing but the firewire ohci and
core module init messages.

Any other ideas of things to try in terms of software/configuration?
(I'm not at the point where I'm entertaining hardware solutions)

After a reboot I can enter/exist live TV just fine and the first
recording always (usually?) scheduled after that seems to work.

mythbackend.log just after end of recording:

W LinuxController linuxfirewiredevice.cpp:646 (run)
LFireDev(002374FFFE366CE7): No Input in 50 msec...
W LinuxController linuxfirewiredevice.cpp:646 (run)
LFireDev(002374FFFE366CE7): No Input in 100 msec...

...logs every 50msec increment...

W LinuxController linuxfirewiredevice.cpp:646 (run)
LFireDev(002374FFFE366CE7): No Input in 1000 msec...
W LinuxController linuxfirewiredevice.cpp:646 (run)
LFireDev(002374FFFE366CE7): No Input in 1050 msec...
I LinuxController linuxfirewiredevice.cpp:778 (ResetBus)
LFireDev(002374FFFE366CE7): ResetBus() -- begin
I LinuxController linuxfirewiredevice.cpp:792 (ResetBus)
LFireDev(002374FFFE366CE7): ResetBus() -- end

(and this series repeats continuously until the next time MythTV tries
to use the tuner and fails)

E TVRecEvent firewiredevice.cpp:124 (GetPowerState)
FireDev(002374FFFE366CE7): Power cmd failed (no response)


More information about the mythtv-users mailing list