[mythtv-users] Recording Functionality Breaks Regularly Since Upgrading to 0.25
mike at rochestervball.com
Fri Jun 8 23:26:21 UTC 2012
On Friday, June 08, 2012 07:10:30 PM Brian and Lisa wrote:
> On 6/7/2012 11:21 PM, Nick Rout wrote:
> > On Fri, Jun 8, 2012 at 7:30 AM, Brian and Lisa<brian.n.lisa at gmail.com>
> >> Greetings (and apologies for original message which included html, I hope
> >> this is better),
> >> Ever since upgrading to 0.25 from 0.24 my system spontaneously fails to
> >> make recordings.
> >> Generally 12 hours or so after the last reboot, after having made
> >> scheduled
> >> recordings normally in the interim, the system will attempt to make
> >> scheduled TV recording(s) but fail. After a reboot, the system will
> >> resume
> >> recording scheduled programs but once the backend breaks, it will remain
> >> broken until the host is reboot (stopping/restarting the backend makes no
> >> difference). The recordings menu (Watch Recording-->All Programs) will
> >> display normal menu entries for all recordings which were attempted
> >> (successful or not), but no HDD recording will have been made once the
> >> backend breaks and of course, no thumbnail image will be evident in the
> >> menu. Aside from the regular breaks in recording capability, the system
> >> performs more or less identically to when it was running 0.24.
> >> Whether the recording functions are working or not, there is no issue
> >> with
> >> playback of successful recordings (suggesting this is not a harddrive I/O
> >> issue).
> >> I followed Mike's advice to another user with a similar issue
> >> (http://www.mythtv.org/pipermail/mythtv-users/2012-May/333505.html):"'Del
> >> ete all capture cards' (not 'Delete all capture cards on<hostname>'),
> >> then re-create cards and re-connect inputs" but this made no difference.
> >> I've also physically reseated my digitizer card after cleaning the
> >> contacts.
> >> Portions of my backend.log during a failure are attached.
> > Sorry if I missed it, but what capture device?
> Sorry I left this out - it's a tried and true Hauppauge WinTV PVR-150.
> mythtv-users mailing list
> mythtv-users at mythtv.org
As someone wrestling with the same problem (using a PVR150 and PVR350) I have
a cron job set up to unload/load the ivtv modules as a temporary workaround
(and save a bunch of rebooting). I now average only 2 or 3 failed recordings
modprobe -r ivtv
modprobe ivtv debug=0x4f
More information about the mythtv-users