[mythtv-commits] Ticket #10414: HDHomeRun: Bad Recordings

[MythTV]

#10414: HDHomeRun: Bad Recordings
------------------------------------------------+--------------------------
 Reporter:  Billy Macdonald <billymacdonald@…>  |          Owner:  danielk
     Type:  Bug Report - General                |         Status:  closed
 Priority:  minor                               |      Milestone:  0.25
Component:  MythTV - Recording                  |        Version:
 Severity:  medium                              |  Unspecified
 Keywords:                                      |     Resolution:  Fixed
                                                |  Ticket locked:  0
------------------------------------------------+--------------------------

Comment (by spartacus06@…):

 Ok, scratch all of that.  I'm a moron and didn't really have two
 recordings going.  I'm still seeing this issue and found out that the
 discontinuity is due to UDP packet receive errors as reported by netstat
 -s --udp


 {{{
 $ mythbackend --version
 Please attach all output as a file in bug reports.
 MythTV Version : v0.25.1-39-geffb32b
 MythTV Branch : fixes/0.25
 Network Protocol : 72
 Library API : 0.25.20120506-1
 QT Version : 4.8.1
 }}}

 Each burst of UDP receive errors corresponds to a group of discontinuity
 warnings

 {{{
 Udp:
     977748 packets received
     40 packets to unknown port received.
     3134 packet receive errors <---
     647 packets sent

 2012-06-19 23:02:48.996735 W  DTVRec(2): A/V PID 0x31 discontinuity
 detected ((10+1)%16!=9)  0.04%
 2012-06-19 23:02:48.996989 W  DTVRec(1): A/V PID 0x31 discontinuity
 detected ((10+1)%16!=9)  0.01%
 2012-06-19 23:02:49.429389 I
 RingBuf(/var/lib/mythtv/livetv/1421_20120619230237.mpg): Waited 0.2
 seconds for data
                         to become available... 65536 < 393216
 2012-06-19 23:02:49.434635 W  DTVRec(2): A/V PID 0x31 discontinuity
 detected ((8+1)%16!=0)  0.04%
 2012-06-19 23:02:49.434705 W  DTVRec(2): A/V PID 0x34 discontinuity
 detected ((2+1)%16!=4)  0.04%
 }}}

 Not sure if the socket receive buffer is filling up or what... but it's
 still a problem.

 I'm doing two recordings and playing back another with a frontend.  CPU
 stats for mythbackend system in this state are 5% user, 20% sys, 75% idle,
 ~1% wait with 8% wait peak, 3202 int/s, 6613 cs/s.  So neither CPU nor
 disk saturation is the issue.

 System baseline with mythbackend running is 100% idle, 40 int/s, 65 cs/s.

 {{{
 $ hdhomerun_config XXXX get /sys/model
 hdhomerun3_atsc
 $ hdhomerun_config XXXX get /sys/version
 20120405
 }}}

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/10414#comment:12>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center