TBS 6281 Tuner Card fails after a few days: Solved!

The biggest issue I’ve had with my new Myth build is that after a few days all recordings would fail. There wasn’t much evidence in the mythbackend logs. All I got was something like this when trying to record:

Aug 28 10:40:18 ripley mythbackend: mythbackend[10907]: E DVBRead mpeg/mpegstreamdata.cpp:365 (AssemblePSIP) MPEGStream[3](0x7fcde016faa8): Error: offset>181, pes length & current cannot be queried

In the end, it turned out that the clue was the following crash shown in /var/log/syslog:

Aug 23 07:46:24 ripley kernel: [385041.373970] irq 17: nobody cared (try booting with the "irqpoll" option)
Aug 23 07:46:24 ripley kernel: [385041.373975] CPU: 0 PID: 0 Comm: swapper/0 Tainted: PF IO 3.13.0-30-generic #55-Ubuntu
Aug 23 07:46:24 ripley kernel: [385041.373977] Hardware name: Gigabyte Technology Co., Ltd. B85M-HD3/B85M-HD3, BIOS F7 03/11/2014
Aug 23 07:46:24 ripley kernel: [385041.373978] ffff88022f24a29c ffff88023e203e68 ffffffff8171a324 ffff88022f24a200
Aug 23 07:46:24 ripley kernel: [385041.373981] ffff88023e203e90 ffffffff810c19e2 ffff88022f24a200 0000000000000011
Aug 23 07:46:24 ripley kernel: [385041.373984] 0000000000000000 ffff88023e203ed0 ffffffff810c1e7c 000000003e203eb0
Aug 23 07:46:24 ripley kernel: [385041.373986] Call Trace:
Aug 23 07:46:24 ripley kernel: [385041.373988] [] dump_stack+0x45/0x56
Aug 23 07:46:24 ripley kernel: [385041.373997] [] __report_bad_irq+0x32/0xd0
Aug 23 07:46:24 ripley kernel: [385041.373999] [] note_interrupt+0x1ac/0x200
Aug 23 07:46:24 ripley kernel: [385041.374001] [] handle_irq_event_percpu+0xd9/0x1d0
Aug 23 07:46:24 ripley kernel: [385041.374003] [] handle_irq_event+0x3d/0x60
Aug 23 07:46:24 ripley kernel: [385041.374005] [] handle_fasteoi_irq+0x5a/0x100
Aug 23 07:46:24 ripley kernel: [385041.374009] [] handle_irq+0x1e/0x30
Aug 23 07:46:24 ripley kernel: [385041.374012] [] do_IRQ+0x4d/0xc0
Aug 23 07:46:24 ripley kernel: [385041.374015] [] common_interrupt+0x6d/0x6d
Aug 23 07:46:24 ripley kernel: [385041.374016] [] ? cpuidle_enter_state+0x52/0xc0
Aug 23 07:46:24 ripley kernel: [385041.374021] [] cpuidle_idle_call+0xb9/0x1f0
Aug 23 07:46:24 ripley kernel: [385041.374024] [] arch_cpu_idle+0xe/0x30
Aug 23 07:46:24 ripley kernel: [385041.374026] [] cpu_startup_entry+0xc5/0x290
Aug 23 07:46:24 ripley kernel: [385041.374030] [] rest_init+0x77/0x80
Aug 23 07:46:24 ripley kernel: [385041.374033] [] start_kernel+0x438/0x443
Aug 23 07:46:24 ripley kernel: [385041.374036] [] ? repair_env_string+0x5c/0x5c
Aug 23 07:46:24 ripley kernel: [385041.374038] [] ? early_idt_handlers+0x120/0x120
Aug 23 07:46:24 ripley kernel: [385041.374040] [] x86_64_start_reservations+0x2a/0x2c
Aug 23 07:46:24 ripley kernel: [385041.374042] [] x86_64_start_kernel+0x143/0x152
Aug 23 07:46:24 ripley kernel: [385041.374043] handlers:
Aug 23 07:46:24 ripley kernel: [385041.374050] [] saa716x_tbs6281_pci_irq [saa716x_tbs_dvb]
Aug 23 07:46:24 ripley kernel: [385041.374051] Disabling IRQ #17

There was some kind of IRQ issue with the TBS card. I found the solution to the problem here:

http://www.tbsdtv.com/forum/viewtopic.php?f=52&t=7631#p24903

It turns out to be an incompatibility between my up-to-date motherboard and the legacy interrupts the TBS card uses by default. The solution is to instruct the TBS driver to use the new MSI interrupts, which is very easy to do. Just create the following file:

/etc/modprobe.d/tbs.conf

Containing the following:

options saa716x_tbs-dvb int_type=1

After a reboot, run this command to check that it’s worked, you should see “PCI-MSI-edge”:

cat /proc/interrupts | grep SAA
45: 134857 0 PCI-MSI-edge SAA716x Core

My system has been fine since I did the above, so I’m pretty sure it’s fixed it for me. It’s nice to have a fully working Myth box again!

3 thoughts on “TBS 6281 Tuner Card fails after a few days: Solved!”

  1. Glad to see you got it working, I’m thinking of getting one of these myself. I’ve seen rumours that multirec doesn’t work with this card. Can you confirm whether this is the case or not? Thanks :)

  2. Hello site owner i see you put a lot of work in your website, i know how to make your blogging easier, do you know that you can copy any post from any site, make it 100% unique and pass copyscape test?
    For more details , just type in google – rewriter
    creates an unique article in a minute

  3. Thank you so much, this issue had been a major headache for me, with my mythbox working flawlessly for 3 or 4 days, then failing to record shows properly for a period. Reboot always fixed it, but the pattern would recur. I implemented this fix a couple of months ago now (after finding your article) and all is now well.
    Cheers.
    Neil.

Comments are closed.