Project

General

Profile

Bug #2621

tbs6982 broken

Added by Oliver Kleinecke almost 10 years ago. Updated almost 10 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
General
Target version:
-
Start date:
2015-01-17
Due date:
% Done:

0%

Estimated time:
Found in version:
3.6-3.9
Affected Versions:

Description

Hi!
Up to version 3.4 I was able to use two TBS6982 (Dual-Sat-TunerCards) together with tvheadend. But it was extremely unstable, crashing multiple times a day.
So I renewed the server completely and did a full major system upgrade of all packages to current stable. Re-pulled that modified driver from git, that tbs6982 users shall use with tvheadend (or is that info outdated?), recompiled + installed.
I have been working with tvheadend a long time, using TeVii USB2.0 Sat Tuner, and it had never been that problematic.. being a professional that is used to compiling stuff and obey deps. Currently I am struggling for days to get it up and running, to no avail.
Any info WHICH version can be REALLY considered stable ?
And no. Its not a drivers prob. 3.4 works, but crashes pretty often, other (git) versions arent even able to use the dvb-frontends.
Please anyone. Is there someone that can aid me by passing me some info, which version together with which driver version for tbs6982 may be used in a stable way. I DONT need any shiny new features. It shall just be STABLE.
Best regards, Oliver

History

#1

Updated by Mark Clarkstone almost 10 years ago

Oliver Kleinecke wrote:

Hi!
Up to version 3.4 I was able to use two TBS6982 (Dual-Sat-TunerCards) together with tvheadend. But it was extremely unstable, crashing multiple times a day.
So I renewed the server completely and did a full major system upgrade of all packages to current stable. Re-pulled that modified driver from git, that tbs6982 users shall use with tvheadend (or is that info outdated?), recompiled + installed.
I have been working with tvheadend a long time, using TeVii USB2.0 Sat Tuner, and it had never been that problematic.. being a professional that is used to compiling stuff and obey deps. Currently I am struggling for days to get it up and running, to no avail.
Any info WHICH version can be REALLY considered stable ?
And no. Its not a drivers prob. 3.4 works, but crashes pretty often, other (git) versions arent even able to use the dvb-frontends.
Please anyone. Is there someone that can aid me by passing me some info, which version together with which driver version for tbs6982 may be used in a stable way. I DONT need any shiny new features. It shall just be STABLE.
Best regards, Oliver

3.4.27 is the only current stable, also what driver are you using? AIUI there are bugs in the TBS official drivers, have you tried ljalves open drivers? Your card is apparently supported, see here https://github.com/ljalves/linux_media/wiki

If you can get a gdb backtrace and post it here.

#2

Updated by Oliver Kleinecke almost 10 years ago

Yes, I tried different versions of ljalves open drivers and different versions of the original tbs drivers

#3

Updated by Oliver Kleinecke almost 10 years ago

Jan 11 18:37:44 localhost kernel: [ 1216.172290] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
Jan 11 18:37:44 localhost kernel: [ 1216.172317] IP: [<ffffffff816b5269>] i2c_del_mux_adapter+0x9/0x30
Jan 11 18:37:44 localhost kernel: [ 1216.172330] PGD 7a8ff067 PUD 7a77b067 PMD 0
Jan 11 18:37:44 localhost kernel: [ 1216.172343] Oops: 0000 [#2] SMP
Jan 11 18:37:44 localhost kernel: [ 1216.172351] Modules linked in: av201x(O) saa716x_budget(O-) tas2101(O) cxd2820r(O) mb86a16(O) cx24117(O) saa716x_core(O) bridge stp llc tun dcdbas dm_raid raid10 dm_snapshot$
Jan 11 18:37:44 localhost kernel: [ 1216.172405] CPU: 0 PID: 9765 Comm: rmmod Tainted: G D O 3.17.7-gentoo #1
Jan 11 18:37:44 localhost kernel: [ 1216.172413] Hardware name: Dell Inc. Vostro 410/0J584C, BIOS 1.0.3 06/20/2008
Jan 11 18:37:44 localhost kernel: [ 1216.172421] task: ffff8800c1c311c0 ti: ffff8800901f8000 task.ti: ffff8800901f8000
Jan 11 18:37:44 localhost kernel: [ 1216.172428] RIP: 0010:[<ffffffff816b5269>] [<ffffffff816b5269>] i2c_del_mux_adapter+0x9/0x30
Jan 11 18:37:44 localhost kernel: [ 1216.172439] RSP: 0018:ffff8800901fbd48 EFLAGS: 00010296
Jan 11 18:37:44 localhost kernel: [ 1216.172445] RAX: 0000000000000000 RBX: ffff8800c1f77400 RCX: 0000000000000567
Jan 11 18:37:44 localhost kernel: [ 1216.172451] RDX: ffffffffa00a5567 RSI: ffffea00032a3b80 RDI: 0000000000000000
Jan 11 18:37:44 localhost kernel: [ 1216.172458] RBP: ffff8800901fbd58 R08: ffff8800ca8ee810 R09: 00000001810000c7
Jan 11 18:37:44 localhost kernel: [ 1216.172465] R10: ffffea00032a3b80 R11: ffffffffa00a50b8 R12: ffffffffa0094070
Jan 11 18:37:44 localhost kernel: [ 1216.172472] R13: 0000000000000000 R14: ffff8800c1e04000 R15: 000000000089c010
Jan 11 18:37:44 localhost kernel: [ 1216.172478] FS: 00007f5dfdf89700(0000) GS:ffff88012fc00000(0000) knlGS:0000000000000000
Jan 11 18:37:44 localhost kernel: [ 1216.172486] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jan 11 18:37:44 localhost kernel: [ 1216.172492] CR2: 0000000000000018 CR3: 00000000903ad000 CR4: 00000000000007f0
Jan 11 18:37:44 localhost kernel: [ 1216.172498] Stack:
Jan 11 18:37:44 localhost kernel: [ 1216.172502] 0000000000000000 ffff8800c1f77400 ffff8800901fbd78 ffffffffa0094089
Jan 11 18:37:44 localhost kernel: [ 1216.172515] ffff8800901fbd98 ffff88012624e020 ffff8800901fbd98 ffffffff816d4dc0
Jan 11 18:37:44 localhost kernel: [ 1216.172533] ffff8800c1e05350 0000000000000000 ffff8800901fbdc8 ffffffffa00711b1
Jan 11 18:37:44 localhost kernel: [ 1216.172548] Call Trace:
Jan 11 18:37:44 localhost kernel: [ 1216.172557] [<ffffffffa0094089>] tas2101_release+0x19/0x40 [tas2101]
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff816d4dc0>] dvb_frontend_detach+0x70/0x80
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffffa00711b1>] saa716x_dvb_exit+0xa1/0x140 [saa716x_core]
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffffa009c888>] saa716x_budget_pci_remove+0x18/0x40 [saa716x_budget]
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff81454b61>] pci_device_remove+0x41/0xc0
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff815eb5ba>] __device_release_driver+0x7a/0xf0
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff815ebeb0>] driver_detach+0xb0/0xc0
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff815eb3fb>] bus_remove_driver+0x4b/0xa0
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff815ec619>] driver_unregister+0x29/0x60
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff81454790>] pci_unregister_driver+0x20/0x90
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffffa009cf26>] saa716x_budget_exit+0x10/0x12 [saa716x_budget]
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff810fbd78>] SyS_delete_module+0x158/0x1d0
Jan 11 18:37:44 localhost kernel: [ 1216.173238] [<ffffffff8192ccd2>] system_call_fastpath+0x16/0x1b
Jan 11 18:37:44 localhost kernel: [ 1216.173238] Code: 00 00 55 48 8b 47 18 48 89 e5 48 8b b8 a0 03 00 00 48 8b 47 10 ff 50 10 5d c3 0f 1f 84 00 00 00 00 00 55 48 89 e5 53 48 83 ec 08 <48> 8b 5f 18 e8 8e c8 ff $
Jan 11 18:37:44 localhost kernel: [ 1216.173238] RIP [<ffffffff816b5269>] i2c_del_mux_adapter+0x9/0x30
Jan 11 18:37:44 localhost kernel: [ 1216.173238] RSP <ffff8800901fbd48>
Jan 11 18:37:44 localhost kernel: [ 1216.173238] CR2: 0000000000000018
Jan 11 18:37:44 localhost kernel: [ 1216.194640] ---[ end trace 8a026ba7f3fe00c5 ]---
Jan 11 18:40:22 localhost kernel: [ 1374.922752] kvm: exiting hardware virtualization

This is current version of ljalves drivers, together with tvheadend 3.4-patch1

:(((((((((((((

#4

Updated by B C almost 10 years ago

kvm + BIOS from 2008??? the only thing I can tell that tvh + TBS is running fine for me on native, kvm and vSphere. The only thing to do is switch to MSI interrupt handling and disable C6/C7 in BIOS to avoid discontinuities

#5

Updated by Jaroslav Kysela almost 10 years ago

  • Status changed from New to Invalid

I do not think that this bug belongs to tvheadend... Use forum to ask users, or report bug to the driver's author.

Also available in: Atom PDF