On Fri, Oct 07, 2005 at 07:43:08PM -0000, MythTV wrote: > Comment (by [EMAIL PROTECTED]): > > Daniel, just a minute ago I saw the problem and happened to glimpse the > error on the backend console. It looks like a scheduler problem to me and > therefore is most likely a problem with gigem's commit on Wednesday > (7391).
I very highly doubt my scheduler change is at fault here. On Fri, Oct 07, 2005 at 08:02:31PM -0000, MythTV wrote: > Comment (by anonymous): > > Here is one of these events from last night from the logs for mb -v > record. I had never seen this until Thursday 10/6. On Wed 10/5 I had > several back to back recordings with no failures. > > Here "Mail Call: Hurricane Katrina" should have ended and 21:00 on card 2 > and "The Amazing Race" should have started. However, at 21:00:00.977 it > reported that it was starting overrecord time anyway and failed to start > "The Amazing Race" reporting rsTunerBusy. > > There were no log entries for 15 minutes before this point nor any > frontend events. I suspect one of the recent changes in tv_rec is at fault. Specifically, it appears TVR::StartRecording is not waiting for the state to change to kState_None if in overrecord before continuing on. David -- David Engel [EMAIL PROTECTED]
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
