Posts by mrvanes

    For those experimenting / using 3.17 or 3.18 and experiencing freezes: There seems to be a lockup problem in the kernel, currently discussed in lkml that I was experiencing as well. Although my problems were not caused by high load (I useVAAPI to decode HD H.264 content) all my problems went away after I downgraded to 3.16.7. MythTV + ddbridge are now solid as a rock!

    Hope this may help anyone looking at inexplainable freezes while watching TV (MythTV in my case).

    http://lkml.iu.edu/hypermail/linux/kernel/1412.0/00237.html

    I'm seeing I2C timeouts in ddbridge module (and linked tuners) with latest media_build_experimental:


    [49327.084218] DDBridge I2C timeout, card 0, port 0
    [49327.084233] ddbridge 0000:01:00.0: DDBridge IRS 00000301
    [49327.084237] cxd2843: i2c_read error
    [49327.084376] tda18212: i2c_write error
    [49537.146442] INFO: task kdvb-ad-0-fe-0:1895 blocked for more than 120 seconds.
    [49537.146451] Tainted: G O 3.17.2 #10
    [49537.146455] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [49537.146459] kdvb-ad-0-fe-0 D ffff8800ab76cd98 0 1895 2 0x00000000
    [49537.146469] ffff8800ab727c60 0000000000000002 ffff8800ab76c890 ffff8800ab727fd8
    [49537.146476] 0000000000013180 0000000000013180 ffffffff81c17480 ffff8800ab76c890
    [49537.146482] ffff8800b7041d20 ffff8800b7041d24 ffff8800ab76c890 00000000ffffffff
    [49537.146490] Call Trace:
    [49537.146504] [<ffffffff8161a409>] schedule_preempt_disabled+0x29/0x70
    [49537.146511] [<ffffffff8161bf72>] __mutex_lock_slowpath+0x152/0x1e0
    [49537.146518] [<ffffffff8161c01f>] mutex_lock+0x1f/0x2f
    [49537.146537] [<ffffffffa01c6dab>] gate_ctrl+0x2b/0x280 [cxd2843]
    [49537.146550] [<ffffffffa00adc0e>] locked_gate_ctrl+0x3e/0x90 [ddbridge]
    [49537.146559] [<ffffffffa01d861d>] set_params+0x3cd/0x910 [tda18212dd]
    [49537.146567] [<ffffffff8109e3df>] ? try_to_del_timer_sync+0x4f/0x70
    [49537.146577] [<ffffffffa01c57dc>] set_parameters+0x5c/0x1030 [cxd2843]
    [49537.146583] [<ffffffff8109cc10>] ? internal_add_timer+0xb0/0xb0
    [49537.146593] [<ffffffffa01c6879>] tune+0x49/0x70 [cxd2843]
    [49537.146608] [<ffffffffa007e366>] dvb_frontend_thread+0x3e6/0x710 [dvb_core]
    [49537.146617] [<ffffffff81083520>] ? prepare_to_wait_event+0x110/0x110
    [49537.146630] [<ffffffffa007df80>] ? dvb_frontend_release+0x110/0x110 [dvb_core]
    [49537.146638] [<ffffffff81066742>] kthread+0xd2/0xf0
    [49537.146645] [<ffffffff81066670>] ? kthread_create_on_node+0x170/0x170
    [49537.146652] [<ffffffff8161e16c>] ret_from_fork+0x7c/0xb0
    [49537.146659] [<ffffffff81066670>] ? kthread_create_on_node+0x170/0x170

    Hi Oliver,

    Thx for the updated media_build_experimental! One question though: why do you remove the mutex locks/unlocks in dvbdev.c:dvb_device_open? And, as someone else pointed out: we dvbloopback driver users need the extra unlock/lock around err = file->f_op->open(inode,file); to prevent tuner lockups. I agree with you this should be solved in the offending module, but I'm no kernel/module hacker and it seems noone wants to, or can pick up the task to fix this long standing bug in dvbloopback/ffdecsawrapper.
    Anyway, it's not a big problem to uncomment the (un)locks and add a couple of lines myself. I was just wondering why you deviate from the original code by commenting the existing lock/unlocks?

    Martin

    Excuse my English. My German is not very good and this is the only place I found with very recent activity around the ddbridge module for linux...
    I tried to compile media_build_experimental against vanilla 3.17.0 this morning and it failed.
    I renamed media_build_experimental to media_build_experimental-3.17 because I didn't want to break my working tree.