Page 1 of 2 12 LastLast
Results 1 to 10 of 79

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

Hybrid View

  1. #1
    Join Date
    Nov 2006
    Location
    Oregon
    Beans
    4,401
    Distro
    Ubuntu Development Release

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

    There have been a number of people saying they are getting 0-byte recordings. Fortunately the issue appears uncommon, and happens infrequently on user systems. Unfortunately, since it is so infrequent it is difficult to gather information to resolve the issue. This thread is an attempt to try and gather as much information as we can in the hopes that if MythTV can provide a fix for it they will.

    The issue appears to happen across all Distros and MythTV versions. Post in this thread if you see this issue regardless of what Distro and/or MythTV version you are using.

    I myself have only seen it personally on an HD-PVR, but others have reported it on DVB cards of all kinds.

    If this happens to you, please post here with the following information:

    Distro and release (eg. Ubuntu 10.10, Fedora 13):
    Full version of the MythTV Backend package (eg. dpkg -l mythtv-backend*):
    Where you get your mythtv packages from (standard repos, avenard repos, mythbuntu repos, compile from source, etc):
    Tuners you see the issue on:
    Other tuners on your system:
    Firmware version version (eg. 'dmesg | grep hdpvr'):
    Kernel Version (uname -a):
    Snippet of dmesg around the time the issue is happening:
    Any other info you think is relevant:
    Last edited by tgm4883; February 15th, 2011 at 03:35 AM.
    *Don't PM me directly for support, open a new thread
    *Looking for a MythTV quick start guide?

  2. #2
    Join Date
    Nov 2006
    Location
    Oregon
    Beans
    4,401
    Distro
    Ubuntu Development Release

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

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

    Full version of all MythTV packages (eg. dpkg -l mythtv-backend):
    ii mythtv-backend 2:0.24.0+fixes.20110213.3d55e51-0ubu A personal video recorder application (server)
    ii mythtv-backend-master 2:0.24.0+fixes.20110213.3d55e51-0ubu 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):
    mythtv-updates repository (mythbuntu-repos)

    Tuners you see the issue on:
    HD-PVR

    Other tuners on your system:
    pcHDTV 5500

    Firmware version version (eg. 'dmesg | grep hdpvr'):
    [ 7.955363] hdpvr 1-3:1.0: untested firmware version 0x15, the driver might not work
    [ 8.283460] hdpvr 1-3:1.0: device now attached to /dev/video0
    [ 8.283494] usbcore: registered new interface driver hdpvr

    Kernel Version (uname -a):
    Linux ares 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 23:42:43 UTC 2011 x86_64 GNU/Linux

    Snippet of dmesg around the time the issue is happening:
    N/A, issue is not happening at this moment.

    Any other info you think is relevant:
    In my case, the blue "halo" on the HD-PVR remains on and I get a 0-byte recording. The blue halo remains on and 0-byte recordings happen for all following recordings on that tuner until I power cycle the HD-PVR and restart the backend service.
    Last edited by tgm4883; February 15th, 2011 at 03:40 AM.
    *Don't PM me directly for support, open a new thread
    *Looking for a MythTV quick start guide?

  3. #3
    Join Date
    Feb 2011
    Beans
    16

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

    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.

  4. #4
    Join Date
    Mar 2010
    Beans
    7

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

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


    Full version of the MythTV Backend package (eg. dpkg -l mythtv-backend*):
    ii mythtv-backend 2:0.24.0+fixes.20110215.72b7 A personal video recorder application (server)
    ii mythtv-backend-master 2:0.24.0+fixes.20110215.72b7 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):
    Mythbuntu repos

    Tuners you see the issue on:
    myth@mythtv:~$ dmesg | grep dvb
    [ 5.238720] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware
    [ 5.238725] usb 1-4: firmware: requesting dvb-usb-dib0700-1.20.fw
    [ 6.538725] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
    [ 7.248025] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
    [ 7.248093] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
    [ 7.308750] cx88/2: cx2388x dvb driver version 0.0.7 loaded
    [ 7.308753] cx88/2: registering cx8802 driver, type: dvb access: shared
    [ 7.678871] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected.
    [ 7.679029] usbcore: registered new interface driver dvb_usb_dib0700


    Other tuners on your system:

    Firmware version version (eg. 'dmesg | grep hdpvr'):
    dvb-usb-dib0700-1.20.fw'

    Kernel Version (uname -a):
    Linux mythtv 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 21:21:01 UTC 2011 i686 GNU/Linux

    Snippet of dmesg around the time the issue is happening:
    Don't have anything in dmesg logs from when it happens


    Any other info you think is relevant:
    I changed the tuning timeout in mythtv-setup a few days ago. It hasn't happened since, although it only ever happened every few months or so.

    It has only happened since upgrading to MythTv .24 via the Mythbuntu autobuilds.

  5. #5
    Join Date
    Feb 2011
    Location
    Canada
    Beans
    2
    Distro
    Ubuntu 10.10 Maverick Meerkat

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

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

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

    ii mythtv-backend 2:0.24.0+fixes.20110206.1a69c92 A personal video recorder application (server)
    ii mythtv-backend-master 2:0.24.0+fixes.20110206.1a69c92 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):

    mythtv-updates repository (mythbuntu-repos)

    Tuners you see the issue on:

    HD-PVR
    (using SPDIF input)

    Other tuners on your system:
    none


    Firmware version version (eg. 'dmesg | grep hdpvr'):
    [ 3.130840] hdpvr 1-6:1.0: untested firmware version 0x15, the driver might not work
    [ 3.466100] hdpvr 1-6:1.0: device now attached to video0
    [ 3.466171] usbcore: registered new interface driver hdpvr

    Kernel Version (uname -a):

    Linux McMyth 2.6.35-25-generic-pae #44-Ubuntu SMP Fri Jan 21 19:01:46 UTC 2011 i686 GNU/Linux

    Snippet of dmesg around the time the issue is happening:
    from syslog dated last occurence -

    Feb 10 20:59:51 McMyth lircd-0.8.7-pre3[1039]: accepted new client on /var/run/lirc/lircd
    Feb 10 20:59:51 McMyth lircd-0.8.7-pre3[1039]: removed client
    Feb 10 20:59:52 McMyth lircd-0.8.7-pre3[1039]: accepted new client on /var/run/lirc/lircd
    Feb 10 20:59:52 McMyth lircd-0.8.7-pre3[1039]: removed client
    Feb 10 20:59:52 McMyth lircd-0.8.7-pre3[1039]: accepted new client on /var/run/lirc/lircd
    Feb 10 20:59:52 McMyth lircd-0.8.7-pre3[1039]: removed client
    Feb 10 21:01:14 McMyth lircd-0.8.7-pre3[1751]: MCU top is now: 50953 (a change of: 30)
    Feb 10 21:01:14 McMyth lircd-0.8.7-pre3[1751]: USB received: 63, expectingBytes: 60. Hex data (headers: 134 60 0):#011
    Feb 10 21:01:26 McMyth lircd-0.8.7-pre3[1751]: MCU top is now: 51247 (a change of: 5
    Feb 10 21:01:26 McMyth lircd-0.8.7-pre3[1751]: USB received: 63, expectingBytes: 61. Hex data (headers: 140 61 0):#011
    Feb 10 21:01:28 McMyth lircd-0.8.7-pre3[1751]: MCU top is now: 53297 (a change of: 5
    Feb 10 21:01:28 McMyth lircd-0.8.7-pre3[1751]: USB received: 63, expectingBytes: 61. Hex data (headers: 184 61 0):#011

    saw problem at this point and stopped recording

    Feb 10 21:01:41 McMyth lircd-0.8.7-pre3[1039]: accepted new client on /var/run/lirc/lircd
    Feb 10 21:01:49 McMyth lircd-0.8.7-pre3[1751]: MCU top is now: 54613 (a change of: 42)
    Feb 10 21:01:49 McMyth lircd-0.8.7-pre3[1751]: USB received: 63, expectingBytes: 60. Hex data (headers: 213 60 0):#011

    Snippet of MythWelcome log around the time the issue is happening:
    2011-02-10 20:58:51.113 MythWelcome received a SCHEDULE_CHANGE event
    2011-02-10 20:59:52.431 MythWelcome received a recording list change event
    2011-02-10 20:59:52.431 MythWelcome received a recording list change event
    2011-02-10 20:59:52.431 [deferred to pending handler]
    2011-02-10 20:59:52.431 MythWelcome received a SCHEDULE_CHANGE event
    saw problem at this point and stopped recording
    2011-02-10 21:01:39.116 Locking input devices

    2011-02-10 21:01:40.011 mythfrontend version: fixes/0.24 [v0.24-151-g1a69c92]

    Any other info you think is relevant:
    This has happened on more than one occasion, always when recording Grays Anatomy or Private Practice on a HD channel. Recording same from non-HD works. Recording other programs on same HD channel works.

    I believe it may be sound related – listings (Schedules Direct) show these 2 programs in particular as stereo. Actual satellite provided listing shows them as 5.1 Dolby (I don't have precise details available at the moment) while all other successfully recorded shows from same station list merely as stereo.

    After the problem occurs and another show records (hit or miss), it will have no sound. Only fix is a reboot of myth box and a power-cycle of HD-PVR.

  6. #6
    Join Date
    Jul 2008
    Beans
    102

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

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

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

    mythtv-backend 0.21.0+fixes21768
    mythtv-backend-mas 0.21.0+fixes21768

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

    Tuners you see the issue on:
    hauppauge 1600, pchdtv 5500

    Other tuners on your system:
    see above

    Firmware version version (eg. 'dmesg | grep hdpvr'):
    sorry, don't know what to replace hdpvr with

    Kernel Version (uname -a):
    what ever was the last issued for 9.04

    Snippet of dmesg around the time the issue is happening:
    sorry, no longer have the issue, so can't provide the info

    Any other info you think is relevant:
    It's been several months since this problem occurred. When it was happening, it varied from once per week, to 2-3 times per night (on either tuner).

    Both my digital tuners take a long time to lock in a channel, so I thought it might be related. So I extended the signal timeout, it's currently at 5500. This seemed to improve things but I think I maxed out the adjustment.

    ***After setting "quick tune" (for both tuners) to "Always", the problem has never reoccurred.***

    I wish I could provide more complete info, but as it's been at least 4-5 months since the problem occurred, I just don't remember the issues fully.

  7. #7
    Join Date
    Feb 2011
    Beans
    16

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

    Quote Originally Posted by ck102 View Post
    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.

  8. #8
    Join Date
    Mar 2008
    Beans
    78

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

    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

  9. #9
    Join Date
    Mar 2009
    Beans
    116
    Distro
    Ubuntu 12.04 Precise Pangolin

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

    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)
    Attached Files Attached Files
    Out of the ashes of disaster grow the roses of success

    Are you for Linux? Is Linux for you?

  10. #10
    Join Date
    May 2006
    Beans
    Hidden!

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

    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.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •