RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it here

**Digicrat** · June 8th, 2011

Distro and release (eg. Ubuntu 10.10, Fedora 13):
Mythbuntu 10.10

Full version of the MythTV Backend package (eg. dpkg -l mythtv-backend*):
||/ Name Version Description
+++-==============-==============-============================================
ii mythtv-backend 2:0.24.0+fixes A personal video recorder application (serve
ii mythtv-backend 2:0.24.0+fixes Metapackage to setup and configure a "Master

Where you get your mythtv packages from (standard repos, avenard repos, mythbuntu repos, compile from source, etc):
standard

Kernel Version (uname -a):
Linux mythtv 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux

Tuners you see the issue on:
I have 2 HDHomeRun Network-based Tuners - one configured for QAM, the other for ATSC. I've periodically seen 0-byte recordings on both.

I believe the issue is related to signal quality. My (unconfirmed) theory is that if there is weak or no signal in the first few seconds of a recording, the attempt fails and we get a 0-byte recording.

For example, in poor weather (when ATSC reception suffers), I tend to get 0-byte recordings with greater frequency.

The best confirmation of this may have been from the last time I got a 0-byte recording - turned out that the tuner card had actually been accidentally unplugged. The mythbackend apparently didn't detect this and attempted to record on the unavailable tuner anyway. This theory should be easy to test, though I haven't gotten around to doing so yet to confirm this wasn't just a coincidence.

In either case, I think these issues do illustrate a potential bug (lack of feature?) in the backend - If a tuner is not available, or if a recordings reception fails (size/length is 0, or significantly less than expected) the system should not flag the episode as recorded, and further delete the recording if the size is below some threshold. Ideally (or does it do this already?), if multiple tuners are available, it should treat a lack of signal-lock as a busy tuner allowing it to try any other free tuners which may or may not have better reception.

**ck102** · June 10th, 2011

Originally Posted by ck102

Distro and release (eg. Ubuntu 10.10, Fedora 13):
Ubuntu 10.10

Full version of the MythTV Backend package (eg. dpkg -l mythtv-backend*):
ii mythtv-backend 2:0.24.0+fixes A personal video recorder application (serve
ii mythtv-backend 2:0.24.0+fixes Metapackage to setup and configure a "Master

Where you get your mythtv packages from (standard repos, avenard repos, mythbuntu repos, compile from source, etc):

mythtv-updates repository (mythbuntu-repos)

Tuners you see the issue on:
HD-PVR

Other tuners on your system:
PVR-150

Firmware version version (eg. 'dmesg | grep hdpvr'):
[ 6.364704] hdpvr 1-4:1.0: untested firmware version 0x15, the driver might not work
[ 6.683368] hdpvr 1-4:1.0: device now attached to video0
[ 6.683481] usbcore: registered new interface driver hdpvr
[ 48.516849] hdpvr 1-4:1.0: device video0 disconnected
[ 54.637145] hdpvr 1-4:1.0: untested firmware version 0x15, the driver might not work
[ 54.950956] hdpvr 1-4:1.0: device now attached to video0

Kernel Version (uname -a):
Linux mytv 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64 GNU/Linux

Snippet of dmesg around the time the issue is happening:
Not available - issue is not currently happening.

Any other info you think is relevant:
When my HD-PVR becomes unusable, it corrupts the first recording about 10 minutes in and the blue halo remains off. It then gives me 0 byte recordings until the HDPVR is power cycled. I do not have to restart the backend. I had the problem on 10.04 as well. When I was using 10.04, I tried the installing the V4L/DVB from source. I wanted to test the changes that Alan Young had made (hoping it would fix the issue) This resulted in the blue halo remaining on when it corrupted. I power cycle the HD-PVR once a week to prevent loosing recordings.

About the time I posted this, I was experiencing the failed recordings about once a week. I changed the following to grub:

Code:

GRUB_CMDLINE_LINUX="acpi=off noapic"

Since making this change, I have not experienced any 0 byte recordings. If I undo this change, the failed recordings are back within the week.

**brianafischer** · June 10th, 2011

Distro and release (eg. Ubuntu 10.10, Fedora 13):
$ lsb_release -a

Code:

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 10.04.2 LTS
Release:        10.04
Codename:       lucid

Full version of the MythTV Backend package (eg. dpkg -l mythtv-backend*):
$ dpkg -l mythtv-backend*

Code:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                 Version              Description
+++-====================-====================-========================================================
ii  mythtv-backend       2:0.24.1+fixes.20110 A personal video recorder application (server)
ii  mythtv-backend-maste 2:0.24.1+fixes.20110 Metapackage to setup and configure a "Master Backend" pr

Where you get your mythtv packages from (standard repos, avenard repos, mythbuntu repos, compile from source, etc):
mythbuntu repos

Tuners you see the issue on:

Code:

Model: "Techsan Electronics B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card"
Device: pci 0x2103 "B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card"

Other tuners on your system:

HD-PVR
HDHomeRun

Firmware version version (eg. 'dmesg | grep hdpvr'):
$dmesg | grep -i dvb

Code:

[   25.261693] DVB: registering new adapter (FlexCop Digital TV device)
[   25.511208] DVB: registering adapter 1 frontend 0 (LG Electronics LGDT3303 VSB/QAM Frontend)...
[   25.891150] DVB: registering new adapter (cx18)
[   25.956338] DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
[   25.956389] cx18-0: DVB Frontend registered
[   25.956391] cx18-0: Registered DVB adapter0 for TS (32 x 32 kB)

Code:

$ dmesg | grep -i hdpvr
[   25.242828] hdpvr 1-5:1.0: untested firmware version 0x12, the driver might not work
[   25.546293] hdpvr 1-5:1.0: device now attached to /dev/video0
[   25.546308] usbcore: registered new interface driver hdpvr

Kernel Version (uname -a):
$ uname -a

Code:

Linux phenomhd 2.6.32-32-generic-pae #62-Ubuntu SMP Wed Apr 20 22:10:33 UTC 2011 i686 GNU/Linux

Snippet of dmesg around the time the issue is happening:
Unfortunately I do not have this...

Any other info you think is relevant:
Think it is related to SD recordings. Always happens when changing from SD to HD. This bug is filed under http://code.mythtv.org/trac/ticket/9177#comment:26

**ktmom** · June 30th, 2011

Distro and release (eg. Ubuntu 10.10, Fedora 13):
$ lsb_release -a

Code:

[No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 10.04.2 LTS
Release:	10.04
Codename:	lucid

Full version of the MythTV Backend package (eg. dpkg -l mythtv-backend*):
$ dpkg -l mythtv-backend*

Code:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                             Version                          Description
+++-================================-================================-================================================================================
ii  mythtv-backend                   2:0.24.1+fixes.20110624.572b95a- A personal video recorder application (server)
ii  mythtv-backend-master            2:0.24.1+fixes.20110624.572b95a- Metapackage to setup and configure a "Master Backend" profile of MythTV.

Where you get your mythtv packages from (standard repos, avenard repos, mythbuntu repos, compile from source, etc):
$ cat /etc/apt/sources.list

Code:

#deb cdrom:[Mythbuntu 10.04 LTS _Lucid Lynx_ - Release i386 (20100427.1)]/ lucid main multiverse restricted universe
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://us.archive.ubuntu.com/ubuntu/ lucid main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ lucid main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ lucid-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ lucid-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ lucid universe
deb-src http://us.archive.ubuntu.com/ubuntu/ lucid universe
deb http://us.archive.ubuntu.com/ubuntu/ lucid-updates universe
deb-src http://us.archive.ubuntu.com/ubuntu/ lucid-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ lucid multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ lucid multiverse
deb http://us.archive.ubuntu.com/ubuntu/ lucid-updates multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ lucid-updates multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://us.archive.ubuntu.com/ubuntu/ lucid-backports main restricted universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ lucid-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu lucid partner
# deb-src http://archive.canonical.com/ubuntu lucid partner

deb http://security.ubuntu.com/ubuntu lucid-security main restricted
deb-src http://security.ubuntu.com/ubuntu lucid-security main restricted
deb http://security.ubuntu.com/ubuntu lucid-security universe
deb-src http://security.ubuntu.com/ubuntu lucid-security universe
deb http://security.ubuntu.com/ubuntu lucid-security multiverse
deb-src http://security.ubuntu.com/ubuntu lucid-security multiverse

Tuners you see the issue on:
Hauppauge WinTV-HVR2250
$ dmesg | grep saa

Code:

[   18.107035] saa7164 driver loaded
[   18.107335] saa7164 0000:02:00.0: PCI INT A -> Link[LNK4] -> GSI 9 (level, low) -> IRQ 9
[   18.107668] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
[   18.107674] saa7164[0]/0: found at 0000:02:00.0, rev: 129, irq: 9, latency: 0, mmio: 0xce000000
[   18.107680] saa7164 0000:02:00.0: setting latency timer to 64
[   18.107684] IRQ 9/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[   18.388085] saa7164_downloadfirmware() no first image
[   18.388285] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
[   18.388290] saa7164 0000:02:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[   18.712804] saa7164_downloadfirmware() firmware read 3978608 bytes.
[   18.712808] saa7164_downloadfirmware() firmware loaded.
[   18.712819] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[   18.712825] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[   18.712827] saa7164_downloadfirmware() BSLSize = 0x0
[   18.712829] saa7164_downloadfirmware() Reserved = 0x0
[   18.712831] saa7164_downloadfirmware() Version = 0x51cc1
[   26.885575] saa7164_downloadimage() Image downloaded, booting...
[   26.988072] saa7164_downloadimage() Image booted successfully.
[   29.174407] saa7164_downloadimage() Image downloaded, booting...
[   30.836341] saa7164_downloadimage() Image booted successfully.
[   30.894020] saa7164[0]: Hauppauge eeprom: model=88061
[   31.854208] DVB: registering new adapter (saa7164)
[   34.931356] DVB: registering new adapter (saa7164)

Other tuners on your system:
HDHomeRun

Firmware version version (eg. 'dmesg | grep hdpvr'):
$ dmesg | grep -i dvb

Code:

[   30.894010] tveeprom 4-0000: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
[   31.854208] DVB: registering new adapter (saa7164)
[   31.854216] DVB: registering adapter 0 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
[   34.931356] DVB: registering new adapter (saa7164)
[   34.931361] DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...

Kernel Version (uname -a):
$ uname -a

Code:

Linux mythbox 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 21:54:21 UTC 2011 i686 GNU/Linux

Snippet of dmesg around the time the issue is happening:
not available - using mythwelcome but attached sys log around the failure.

Any other info you think is relevant:
Had the problem under 9.10 with the HVR2250 tuner. I think I turned off apic in grub and increased the tuner timeouts and forgot all about this. Recently upgraded to 10.04 and mythtv .24-fixes and now having the problem intermittently again.

Have tried GRUB_CMDLINE_LINUX="nolapic" and increased the tuning timeouts on all tuners.

The tuner most recently stopped recording 47 minutes into two shows and then didn't record anything after until the next reboot. There were slews (technical term) of these errors in the syslog:

Code:

Event timed out
saa7164_api_i2c_read() error, ret(1) = 0x32
s5h1411_readreg: readreg error (ret == -5)
Event timed out
saa7164_api_i2c_write() error, ret(1) = 0xc
s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)

I've attached text files of the sys.log (sunday the boot and around the failure - monday the boot after the failure where everything was ok again) and the mythbackend.log around the time of the failure. Card failure time stamp at about; 2011-06-26 21:48:18.855

$ lspci

Code:

00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev f3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev f2)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev f3)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9500 GT] (rev a1)
02:00.0 Multimedia controller: Philips Semiconductors Device 7164 (rev 81)
05:07.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 11)
05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
05:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
06:08.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
06:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)

**ian dobson** · July 6th, 2011

Hi,

OK I've had a look at my 0byte problems with the iptv recorder and have found something interesting:-

I see this when the recording works

Code:

2011-07-05 20:08:29.878 TVRec(5): ASK_RECORDING 5 29 0 0
2011-07-05 20:09:01.335 TVRec(5): Changing from None to RecordingOnly
2011-07-05 20:09:01.360 TVRec(5): HW Tuner: 5->5
Looking for data for Channel 90008 on 1
Opening /data/bin/itgate1.vlm for Channel 90008
Starting vlc1 -I telnet --telnet-port 4211 --vlm-conf /data/bin/itgate1.vlm  -v
Tuning to http://192.168.0.60/cgi-bin/zapTo?path=1:0:1:2721:2bd:7:0:0:0:0:
Countdown 4
Countdown 3
Countdown 2
Countdown 1
Connecting to vlc
sending password
starting playback
sending control 90008 play
quitting
2011-07-05 20:09:12.190 AutoExpire: CalcParams(): Max required Free Space: 252.0 GB w/freq: 7 min
2011-07-05 20:09:12.191 Started recording: "Numb3rs - Die Logik des Verbrechens": channel 93009 on cardid 5, sourceid 3
2011-07-05 20:09:12.192 scheduler: Started recording: "Numb3rs - Die Logik des Verbrechens": channel 93009 on cardid 5, sourceid 3
2011-07-05 20:09:12.377 ProgramInfo(93009_20110705200900.mpg), Error: GetPlaybackURL: '93009_20110705200900.mpg' should be local, but it can not be found.
2011-07-05 20:09:14.290 Updating status for "Numb3rs - Die Logik des Verbrechens" on cardid 5 (Tuning => Recording)
2011-07-05 20:09:14.347 TVRec(5): EIT scanning disabled for all sources on this card.
2011-07-05 20:09:14.359 TVRec(5): rec->GetPathname(): '/data/mythtv/recordings/93009_20110705200900.mpg'
2011-07-05 20:10:01.205 Reschedule requested for id -1.

And when it doesn't work:-

Code:

2011-07-06 12:43:29.807 TVRec(5): ASK_RECORDING 5 29 0 0
2011-07-06 12:44:01.675 TVRec(5): Changing from None to RecordingOnly
2011-07-06 12:44:02.095 TVRec(5): HW Tuner: 5->5
2011-07-06 12:44:02.166 TVRec(5): rec->GetPathname(): '/data/mythtv/recordings/93009_20110706124400.mpg'
2011-07-06 12:44:02.181 AutoExpire: CalcParams(): Max required Free Space: 252.0 GB w/freq: 14 min
2011-07-06 12:44:02.191 Started recording: "Numb3rs - Die Logik des Verbrechens": channel 93009 on cardid 5, sourceid 3
2011-07-06 12:44:02.217 scheduler: Started recording: "Numb3rs - Die Logik des Verbrechens": channel 93009 on cardid 5, sourceid 3
Looking for data for Channel 90008 on 1
Opening /data/bin/itgate1.vlm for Channel 90008
Starting vlc1 -I telnet --telnet-port 4211 --vlm-conf /data/bin/itgate1.vlm  -v
Tuning to http://192.168.0.60/cgi-bin/zapTo?path=1:0:1:2721:2bd:7:0:0:0:0:
Countdown 4
Countdown 3
Countdown 2
Countdown 1
Connecting to vlc
sending password
starting playback
sending control 90008 play
quitting
2011-07-06 12:45:01.980 MainServer::ANN Monitor
2011-07-06 12:45:02.009 MainServer::ANN Monitor
2011-07-06 12:45:02.260 adding: alpha2 as a client (events: 0)
2011-07-06 12:45:02.262 adding: alpha2 as a client (events: 0)
2011-07-06 12:45:08.190 EITScanner (1): Now looking for EIT data on multiplex of channel 153
2011-07-06 12:45:08.220 EITCache: Pruning all entries that ended before UTC 2011-07-05T12:50:28
2011-07-06 12:45:08.253 EITCache: Deleting old cache entries from the database
2011-07-06 12:45:10.298 EITScanner (1): Started passive scan.
2011-07-06 12:45:10.646 MainServer::ANN Monitor

Note the message Started recording and rec->GetPathname comming before the tuning script is called.

and here's a dump of the vlc output. Note the stream seems to be getting to mythtv, but mythtv just doesn't save it to disk (The first connect refused message appears when mythtv should stop the recording).

Code:

07-07-2011 02:31:01 ,\*ÉßVLC media player 1.1.9 The Luggage (revision exported)
07-07-2011 02:31:01 Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS")
07-07-2011 02:31:01 Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE")
07-07-2011 02:31:01 [0x941190] inhibit interface error: Failed to connect to the D-Bus session daemon: //bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
07-07-2011 02:31:01 
07-07-2011 02:31:01 [0x941190] main interface error: no suitable interface module
07-07-2011 02:31:01 [0x943250] main interface error: no suitable interface module
07-07-2011 02:31:01 [0x83d120] main libvlc error: interface "globalhotkeys,none" initialization failed
07-07-2011 02:31:01 [0x943600] [telnet] lua interface: Listening on host "localhost:4212".
07-07-2011 02:31:11 [0x965f80] [Media: 90008] main stream out warning: missing value for option mux
07-07-2011 02:31:11 Blocked: call to setenv("_PX_CONFIG_ORDER", "", 1)
07-07-2011 02:31:12 libdvbpsi error (PSI decoder): TS discontinuity (received 7, expected 0) for PID 0
07-07-2011 02:31:12 libdvbpsi error (PSI decoder): TS discontinuity (received 9, expected 0) for PID 222
07-07-2011 02:31:12 [0x96c500] [Media: 90008] ts demux warning: first packet for pid=223 cc=0xd
07-07-2011 02:31:12 [0x96c500] [Media: 90008] ts demux warning: first packet for pid=224 cc=0xb
07-07-2011 02:33:29 libdvbpsi error (PSI decoder): TS discontinuity (received 13, expected 12) for PID 222
07-07-2011 02:41:29 libdvbpsi error (PSI decoder): TS discontinuity (received 4, expected 3) for PID 222
07-07-2011 02:45:29 libdvbpsi error (PSI decoder): TS discontinuity (received 1, expected 0) for PID 222
07-07-2011 02:53:29 libdvbpsi error (PSI decoder): TS discontinuity (received 8, expected 7) for PID 222
07-07-2011 02:57:29 libdvbpsi error (PSI decoder): TS discontinuity (received 4, expected 3) for PID 222
07-07-2011 03:09:29 libdvbpsi error (PSI decoder): TS discontinuity (received 7, expected 6) for PID 222
07-07-2011 03:21:29 libdvbpsi error (PSI decoder): TS discontinuity (received 10, expected 9) for PID 222
07-07-2011 03:33:29 libdvbpsi error (PSI decoder): TS discontinuity (received 13, expected 12) for PID 222
07-07-2011 03:36:40 [0x968960] [Media: 90008] access_output_udp access out warning: send error: Connection refused
07-07-2011 03:37:29 last line repeated 4074 times
07-07-2011 03:37:29 libdvbpsi error (PSI decoder): TS discontinuity (received 10, expected 9) for PID 222
07-07-2011 03:37:29 [0x968960] [Media: 90008] access_output_udp access out warning: send error: Connection refused
07-07-2011 03:45:01 last line repeated 41677 times

So it looks like a mythtv timing problem.

Running 2:0.24.1+fixes.20110706.b491236-0ubuntu0mythbuntu3 on 64bit 11.04.

Regards
Ian Dobson

**ian dobson** · July 7th, 2011

Hi All,

A simple question: Is this thread going anywhere/is a dev actually looking at this? I don't expect a solution, I'd just like to know if anything's going on in the background.

Regards
Ian Dobson

**tgm4883** · July 7th, 2011

Originally Posted by ian dobson

Hi All,

A simple question: Is this thread going anywhere/is a dev actually looking at this? I don't expect a solution, I'd just like to know if anything's going on in the background.

Regards
Ian Dobson

Yep, there are developers looking at the info. Whether it proves fruitful or not remains to be seen though.

**ian dobson** · July 7th, 2011

Originally Posted by tgm4883

Yep, there are developers looking at the info. Whether it proves fruitful or not remains to be seen though.

OK Thanks, that all I wanted to know. I'll continue my search for the cause of 0byte recordings with IPTV tuners.

Regards
Ian Dobson

**ian dobson** · July 12th, 2011

Hi,

It's just happened again, and as I said in the last post the MythTV backend displays the following message before the channel change script starts when the recording doesn't work:-

scheduler: Started recording: "": channel XXX on cardid YYY, sourceid ZZZ

Code:

Recording worked
2011-07-12 10:33:30.172 TVRec(5): ASK_RECORDING 5 29 0 0
2011-07-12 10:34:01.766 TVRec(5): Changing from None to RecordingOnly
2011-07-12 10:34:01.851 TVRec(5): HW Tuner: 5->5
* Looking for data for Channel 90015 on 1
* Opening /data/bin/itgate1.vlm for Channel 90015
* Need to use CAM for channel 90015
* Tuning to http://192.168.0.62/cgi-bin/zapTo?path=1:0:1:c73d:26e:1:0:0:0:0:
* Starting vlc1 -I telnet --telnet-port 4211 --vlm-conf /data/bin/itgate1.vlm  -v
* Tuning to http://192.168.0.60/cgi-bin/zapTo?path=1:0:1:c73d:26e:1:0:0:0:0:
* Countdown 4
* Countdown 3
* Countdown 2
* Countdown 1
* Connecting to vlc
* sending password
* starting playback
* sending control 90015 play
* quitting
2011-07-12 10:34:16.556 AutoExpire: CalcParams(): Max required Free Space: 252.0 GB w/freq: 7 min
2011-07-12 10:34:16.593 Started recording: "Dr. G - Beruf: Gerichtsmedizinerin":"Medizinische Mysterien unter der Lupe": channel 93021 on cardid 5, sourceid 3
2011-07-12 10:34:16.594 scheduler: Started recording: "Dr. G - Beruf: Gerichtsmedizinerin":"Medizinische Mysterien unter der Lupe": channel 93021 on cardid 5, so$
2011-07-12 10:34:18.532 Updating status for "Dr. G - Beruf: Gerichtsmedizinerin":"Medizinische Mysterien unter der Lupe" on cardid 5 (Tuning => Recording)
2011-07-12 10:34:18.539 TVRec(5): EIT scanning disabled for all sources on this card.
2011-07-12 10:34:18.699 TVRec(5): rec->GetPathname(): '/data/mythtv/recordings/93021_20110712103400.mpg'
2011-07-12 10:35:01.842 MainServer::ANN Monitor



Recording didn't work
2011-07-12 10:36:30.069 TVRec(6): ASK_RECORDING 6 29 0 0
2011-07-12 10:37:01.547 TVRec(6): Changing from None to RecordingOnly
2011-07-12 10:37:01.614 TVRec(6): HW Tuner: 6->6
2011-07-12 10:37:01.717 TVRec(6): rec->GetPathname(): '/data/mythtv/recordings/93000_20110712103700.mpg'
2011-07-12 10:37:01.733 AutoExpire: CalcParams(): Max required Free Space: 252.0 GB w/freq: 4 min
2011-07-12 10:37:01.747 Started recording: "Einsatz in New York": channel 93000 on cardid 6, sourceid 3
2011-07-12 10:37:01.764 scheduler: Started recording: "Einsatz in New York": channel 93000 on cardid 6, sourceid 3
* Looking for data for Channel 90000 on 2
* Opening /data/bin/itgate2.vlm for Channel 90000
* Starting vlc2 -I telnet --telnet-port 4212 --vlm-conf /data/bin/itgate2.vlm  -v
* Tuning to http://192.168.0.61/cgi-bin/zapTo?path=1:0:1:2730:2bd:7:0:0:0:0:
* Countdown 4
* Countdown 3
* Countdown 2
* Countdown 1
* Connecting to vlc
* sending password
* starting playback
* sending control 90000 play
* quitting
2011-07-12 10:37:28.541 EITScanner (3): Added 249 EIT Events
2011-07-12 10:37:28.579 EITScanner: Rate limiting reschedules..
2011-07-12 10:38:54.715 AutoExpire: CalcParams(): Max required Free Space: 252.0 GB w/freq: 4 min
2011-07-12 10:40:01.305 MainServer::ANN Monitor

Note the data is grabbed from the settopbox/feed into VLC in both cases and vlc passes it onto MythTV but when the recording doesn't work it looks as if the backend just looses track of what should go where.

Regards
Ian Dobson

**ktmom** · July 22nd, 2011

I'm getting failures pretty regularly under 10.04.2 mythtv .24-fixes AMD 64-bit running 32-bit. In addition to my previous post, I am getting recordings which stop at some point into them. Today it was 8-ish minutes in. Then nothing recorded after until I rebooted the system.

I'm frustrated since I had exactly the same problem when I first installed the 2250 under 9.10. I have been racking my brain to remember all of the things I attempted (no I can't find my notes) and it seems that I think I played with increasing the latency for the card.

A lspci -v shows:

Code:

02:00.0 Multimedia controller: Philips Semiconductors Device 7164 (rev 81)
	Subsystem: Hauppauge computer works Inc. Device 8891
	Flags: bus master, fast devsel, latency 0, IRQ 9
	Memory at ce000000 (64-bit, non-prefetchable) [size=4M]
	Memory at ce400000 (64-bit, non-prefetchable) [size=4M]
	Capabilities: <access denied>
	Kernel driver in use: saa7164
	Kernel modules: saa7164

Does that latency 0 seem right? The trouble is, I can't remember how I went about telling the system to increase the latency. Should I bother chasing this?

mythbackend around the failure:

Code:

2011-07-21 19:07:39.655 DevRdB(/dev/dvb/adapter1/frontend0) Error: Poll giving up
2011-07-21 19:07:39.660 DVBSH(/dev/dvb/adapter1/frontend0) Error: Device error detected
2011-07-21 19:07:39.675 DevRdB(/dev/dvb/adapter0/frontend0) Error: Poll giving up
2011-07-21 19:07:39.679 DVBSH(/dev/dvb/adapter0/frontend0) Error: Device error detected
2011-07-21 19:08:09.700 DVBRec(5:/dev/dvb/adapter1/frontend0) Error: Stream handler died unexpectedly.
2011-07-21 19:08:09.700 DVBRec(4:/dev/dvb/adapter0/frontend0) Error: Stream handler died unexpectedly.
2011-07-21 19:08:09.724 TVRec(5): Changing from RecordingOnly to None
2011-07-21 19:08:09.726 Updating status for TMZ on cardid 5 (Recording => Recorder Failed)
2011-07-21 19:08:09.729 Reschedule requested for id 0.
2011-07-21 19:08:09.756 MainServer, Error: PREVIEW_SUCCESS but no receivers.
2011-07-21 19:08:10.291 TVRec(4): Changing from RecordingOnly to None
2011-07-21 19:08:10.325 Updating status for "Dr. Phil":"Accused of the Unthinkable" on cardid 4 (Recording => Recorder Failed)
2011-07-21 19:08:10.467 MainServer, Error: PREVIEW_SUCCESS but no receivers.
2011-07-21 19:08:11.047 Reschedule interrupted, will retry
2011-07-21 19:08:11.047 Reschedule requested for id 0.
2011-07-21 19:08:11.048 Reschedule requested for id 0.

and of course the syslog is full of these:

Code:

Jul 21 19:07:24 mythbox kernel: [108745.957028] Event timed out
Jul 21 19:07:24 mythbox kernel: [108745.957042] saa7164_api_i2c_read() error, ret(2) = 0x32
Jul 21 19:07:24 mythbox kernel: [108745.957049] s5h1411_readreg: readreg error (ret == -5)
Jul 21 19:07:25 mythbox kernel: [108747.076028] Event timed out
Jul 21 19:07:25 mythbox kernel: [108747.076041] saa7164_api_i2c_read() error, ret(1) = 0x32
Jul 21 19:07:25 mythbox kernel: [108747.076050] s5h1411_readreg: readreg error (ret == -5)
Jul 21 19:07:34 mythbox kernel: [108755.957030] Event timed out
Jul 21 19:07:34 mythbox kernel: [108755.957042] saa7164_api_i2c_read() error, ret(1) = 0x32
Jul 21 19:07:34 mythbox kernel: [108755.957050] s5h1411_readreg: readreg error (ret == -5)
Jul 21 19:07:35 mythbox kernel: [108757.076030] Event timed out
Jul 21 19:07:35 mythbox kernel: [108757.076043] saa7164_api_i2c_read() error, ret(1) = 0x32
Jul 21 19:07:35 mythbox kernel: [108757.076052] s5h1411_readreg: readreg error (ret == -5)
Jul 21 19:07:44 mythbox kernel: [108765.957026] Event timed out
Jul 21 19:07:44 mythbox kernel: [108765.957039] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:07:44 mythbox kernel: [108765.957048] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Jul 21 19:07:45 mythbox kernel: [108767.076028] Event timed out
Jul 21 19:07:45 mythbox kernel: [108767.076041] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:07:45 mythbox kernel: [108767.076050] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Jul 21 19:07:49 mythbox kernel: [108770.948026] Event timed out
Jul 21 19:07:49 mythbox kernel: [108770.948039] saa7164_api_transition_port() error, ret = 0x32
Jul 21 19:07:49 mythbox kernel: [108770.948045] saa7164_dvb_pause_tsport() pause transition failed, ret = 0x32
Jul 21 19:07:49 mythbox kernel: [108770.968022] Event timed out
Jul 21 19:07:49 mythbox kernel: [108770.968027] saa7164_api_transition_port() error, ret = 0x32
Jul 21 19:07:49 mythbox kernel: [108770.968032] saa7164_dvb_pause_tsport() pause transition failed, ret = 0x32
Jul 21 19:07:54 mythbox kernel: [108775.956037] Event timed out
Jul 21 19:07:54 mythbox kernel: [108775.956050] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:07:54 mythbox kernel: [108775.956059] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Jul 21 19:07:55 mythbox kernel: [108777.076029] Event timed out
Jul 21 19:07:55 mythbox kernel: [108777.076041] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:07:55 mythbox kernel: [108777.076050] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Jul 21 19:07:59 mythbox kernel: [108780.948050] Event timed out
Jul 21 19:07:59 mythbox kernel: [108780.948064] saa7164_api_transition_port() error, ret = 0x32
Jul 21 19:07:59 mythbox kernel: [108780.948070] saa7164_dvb_acquire_tsport() acquire transition failed, ret = 0x32
Jul 21 19:07:59 mythbox kernel: [108780.968052] Event timed out
Jul 21 19:07:59 mythbox kernel: [108780.968058] saa7164_api_transition_port() error, ret = 0x32
Jul 21 19:07:59 mythbox kernel: [108780.968063] saa7164_dvb_acquire_tsport() acquire transition failed, ret = 0x32
Jul 21 19:08:04 mythbox kernel: [108785.957029] Event timed out
Jul 21 19:08:04 mythbox kernel: [108785.957042] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:04 mythbox kernel: [108785.957051] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Jul 21 19:08:05 mythbox kernel: [108787.076028] Event timed out
Jul 21 19:08:05 mythbox kernel: [108787.076041] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:05 mythbox kernel: [108787.076050] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Jul 21 19:08:09 mythbox kernel: [108790.948028] Event timed out
Jul 21 19:08:09 mythbox kernel: [108790.948041] saa7164_api_transition_port() error, ret = 0x32
Jul 21 19:08:09 mythbox kernel: [108790.948047] saa7164_dvb_stop_tsport() stop transition failed, ret = 0x32
Jul 21 19:08:09 mythbox kernel: [108790.968026] Event timed out
Jul 21 19:08:09 mythbox kernel: [108790.968035] saa7164_api_transition_port() error, ret = 0x32
Jul 21 19:08:09 mythbox kernel: [108790.968041] saa7164_dvb_stop_tsport() stop transition failed, ret = 0x32
Jul 21 19:08:14 mythbox kernel: [108795.957069] Event timed out
Jul 21 19:08:14 mythbox kernel: [108795.957078] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:14 mythbox kernel: [108795.957083] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Jul 21 19:08:14 mythbox kernel: [108795.957087] tda18271_init: error -5 on line 826
Jul 21 19:08:14 mythbox kernel: [108795.957089] tda18271_tune: error -5 on line 904
Jul 21 19:08:14 mythbox kernel: [108795.957092] tda18271_set_params: error -5 on line 985
Jul 21 19:08:15 mythbox kernel: [108797.076042] Event timed out
Jul 21 19:08:15 mythbox kernel: [108797.076055] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:15 mythbox kernel: [108797.076065] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Jul 21 19:08:15 mythbox kernel: [108797.076072] tda18271_init: error -5 on line 826
Jul 21 19:08:15 mythbox kernel: [108797.076078] tda18271_tune: error -5 on line 904
Jul 21 19:08:15 mythbox kernel: [108797.076083] tda18271_set_params: error -5 on line 985
Jul 21 19:08:24 mythbox kernel: [108805.957055] Event timed out
Jul 21 19:08:24 mythbox kernel: [108805.957066] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:24 mythbox kernel: [108805.957075] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
Jul 21 19:08:25 mythbox kernel: [108807.076039] Event timed out
Jul 21 19:08:25 mythbox kernel: [108807.076052] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:25 mythbox kernel: [108807.076062] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
Jul 21 19:08:34 mythbox kernel: [108815.957026] Event timed out
Jul 21 19:08:34 mythbox kernel: [108815.957036] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:34 mythbox kernel: [108815.957044] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Jul 21 19:08:35 mythbox kernel: [108817.076058] Event timed out
Jul 21 19:08:35 mythbox kernel: [108817.076071] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:35 mythbox kernel: [108817.076080] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Jul 21 19:08:44 mythbox kernel: [108825.956041] Event timed out
Jul 21 19:08:44 mythbox kernel: [108825.956053] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:44 mythbox kernel: [108825.956061] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Jul 21 19:08:45 mythbox kernel: [108827.076038] Event timed out
Jul 21 19:08:45 mythbox kernel: [108827.076051] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:08:45 mythbox kernel: [108827.076060] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Jul 21 19:08:55 mythbox kernel: [108836.956039] Event timed out
Jul 21 19:08:55 mythbox kernel: [108836.956051] saa7164_api_i2c_read() error, ret(1) = 0x32
Jul 21 19:08:55 mythbox kernel: [108836.956059] s5h1411_readreg: readreg error (ret == -5)
Jul 21 19:08:56 mythbox kernel: [108838.076033] Event timed out
Jul 21 19:08:56 mythbox kernel: [108838.076045] saa7164_api_i2c_read() error, ret(1) = 0x32
Jul 21 19:08:56 mythbox kernel: [108838.076053] s5h1411_readreg: readreg error (ret == -5)
Jul 21 19:09:01 mythbox CRON[4043]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Jul 21 19:09:05 mythbox kernel: [108846.957028] Event timed out
Jul 21 19:09:05 mythbox kernel: [108846.957041] saa7164_api_i2c_read() error, ret(1) = 0x32
Jul 21 19:09:05 mythbox kernel: [108846.957048] s5h1411_readreg: readreg error (ret == -5)
Jul 21 19:09:06 mythbox kernel: [108848.076029] Event timed out
Jul 21 19:09:06 mythbox kernel: [108848.076043] saa7164_api_i2c_read() error, ret(1) = 0x32
Jul 21 19:09:06 mythbox kernel: [108848.076051] s5h1411_readreg: readreg error (ret == -5)
Jul 21 19:09:15 mythbox kernel: [108856.957028] Event timed out
Jul 21 19:09:15 mythbox kernel: [108856.957040] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:15 mythbox kernel: [108856.957049] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Jul 21 19:09:16 mythbox kernel: [108858.076057] Event timed out
Jul 21 19:09:16 mythbox kernel: [108858.076070] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:16 mythbox kernel: [108858.076079] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Jul 21 19:09:25 mythbox kernel: [108866.956033] Event timed out
Jul 21 19:09:25 mythbox kernel: [108866.956045] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:25 mythbox kernel: [108866.956053] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Jul 21 19:09:26 mythbox kernel: [108868.076034] Event timed out
Jul 21 19:09:26 mythbox kernel: [108868.076047] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:26 mythbox kernel: [108868.076056] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Jul 21 19:09:35 mythbox kernel: [108876.957027] Event timed out
Jul 21 19:09:35 mythbox kernel: [108876.957040] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:35 mythbox kernel: [108876.957049] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Jul 21 19:09:36 mythbox kernel: [108878.076038] Event timed out
Jul 21 19:09:36 mythbox kernel: [108878.076051] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:36 mythbox kernel: [108878.076061] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Jul 21 19:09:45 mythbox kernel: [108886.956032] Event timed out
Jul 21 19:09:45 mythbox kernel: [108886.956044] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:45 mythbox kernel: [108886.956053] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Jul 21 19:09:45 mythbox kernel: [108886.956061] tda18271_init: error -5 on line 826
Jul 21 19:09:45 mythbox kernel: [108886.956067] tda18271_tune: error -5 on line 904
Jul 21 19:09:45 mythbox kernel: [108886.956072] tda18271_set_params: error -5 on line 985
Jul 21 19:09:46 mythbox kernel: [108888.076046] Event timed out
Jul 21 19:09:46 mythbox kernel: [108888.076059] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:46 mythbox kernel: [108888.076069] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Jul 21 19:09:46 mythbox kernel: [108888.076076] tda18271_init: error -5 on line 826
Jul 21 19:09:46 mythbox kernel: [108888.076081] tda18271_tune: error -5 on line 904
Jul 21 19:09:46 mythbox kernel: [108888.076087] tda18271_set_params: error -5 on line 985
Jul 21 19:09:55 mythbox kernel: [108896.957026] Event timed out
Jul 21 19:09:55 mythbox kernel: [108896.957038] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:55 mythbox kernel: [108896.957047] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
Jul 21 19:09:56 mythbox kernel: [108898.076037] Event timed out
Jul 21 19:09:56 mythbox kernel: [108898.076050] saa7164_api_i2c_write() error, ret(1) = 0x32
Jul 21 19:09:56 mythbox kernel: [108898.076060] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)

Thread: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it here

Thread Tools

Display

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Re: RFH: Do you get 0-byte recordings? (Even infrequently) Please post info about it

Bookmarks

Bookmarks

Posting Permissions