SOLVED! corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels

Added by Paul M 7 months ago

This is SOLVED. You need to enable MSI interrupts - see my followup on page 2, or go direct to https://tvheadend.org/boards/5/topics/32496?r=34042#message-34042


About once a day TVH gets into a state where there's corrupted video, either HD or SD channels. It doesn't matter whether I play using the web player or kodi with the TVH add-on. https://imgur.com/a/AWvFDqI

Restarting TVH server doesn't fix it, I have to reboot. Sometimes when I ask nicely for a reboot, it locks up and I have to force a restart, and then TVH database files will be corrupted (e.g. no network, channels, etc) and any recording timers will be lost, and I have to piece together the config from the last backup so as not to orphan recordings.

My TVH server is a dedicated box, running headless. It's running 4.3-1236~g518d57b~xenial on ubuntu 16.04.04-lts-x64, kernel 4.4.0-116-lowlatency, on a core2quad q6600 with 4GB RAM and mirrored 750GB hard drives. I'm using a TBS twin port PCIe card.

When I was on 4.2.latest I used to find the TVH web UI would lock up hard with 100% of a CPU core pegged; that was with the ljalves driver.

After trying many things, I got to where I am now, running 4.3 latest, having installed the low latency kernel and switched to a freshly built new drivers from the tbsdriver git repo. I no longer get the hard UI lockups, but I do get occasional corruption of the configuration/db files.

When TVH is working for me, it's great, but sadly it's far too unreliable to replace my ageing Humax DVR which has a flakey HDMI port but is otherwise reliable :-(

thanks for any ideas.


Replies (43)

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by saen acro 7 months ago

FEMON status when this pixelization come

disable unused devices in BIOS/UEFI (sound card com/paralel ports)
update to latest bios/uefi

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

Hi, I did try updating the BIOS on the motherboard. I'll check for any unused devices I can disable, I presume that's to free up spare IRQs and DMAs (but I didn't think that mattered for PCIe?) to see if that helps.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

Ok, I had to wait until it happened again. This is what I saw when I ran femon and tailed dmesg:

# femon
FE: TurboSight TBS 6982SE DVB-S/S2 (DVBS)
status SCVYL | signal f8a1 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fb15 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fb15 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fb15 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fced | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fc50 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fb15 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fc50 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fc50 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f8a1 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f93e | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fd8a | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f93e | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f93e | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f93e | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fb15 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fc50 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fb15 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fc50 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fced | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fbb2 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fc50 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fb15 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal f9db | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fc50 | snr bc58 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal fa78 | snr bda0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
^C
# dmesg | tail
[50765.375029] demux_worker: called but nothing to do
[50765.575028] demux_worker: called but nothing to do
[50765.975028] demux_worker: called but nothing to do
[50778.975032] demux_worker: called but nothing to do

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

I then took a look at the tvheadend log, I had tuned to the first channel I saw in the EPG list which was BBC Parliament.

Apr 26 22:36:25 mcintyre tvheadend[1505]: mpegts: 10788V in 28E2 - tuning on TurboSight TBS 6982SE DVB-S/S2 #0 : DVB-S #0
Apr 26 22:36:25 mcintyre tvheadend[1505]: subscription: 0851: "HTTP" subscribing on channel "BBC Parliament", weight: 100, adapter: "TurboSight TBS 6982SE DVB-S/S2 #0 : DVB-S #0", network: "28E2", mux: "10788V", provider: "BSkyB", service: "BBC Parliament", profile="webtv-h264-aac-matroska", hostname="192.168.29.37", username="tvhadmin", client="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36" 
Apr 26 22:36:26 mcintyre tvheadend[1505]: TS: 28E2/10788V/BBC Parliament: MPEG2AUDIO @ #5101 Continuity counter error (total 1)
Apr 26 22:36:26 mcintyre tvheadend[1505]: TS: 28E2/10788V/BBC Parliament: MPEG2VIDEO @ #5100 Continuity counter error (total 1)
Apr 26 22:36:26 mcintyre tvheadend[1505]: TS: 28E2/10788V/BBC Parliament: TELETEXT @ #5103 Continuity counter error (total 1)
Apr 26 22:36:28 mcintyre tvheadend[1505]: transcode: 0001: 01:MPEG2VIDEO: ==> Using profile webtv-h264
Apr 26 22:36:28 mcintyre tvheadend[1505]: transcode: 0001: 02:MPEG2AUDIO: ==> Using profile webtv-aac
Apr 26 22:36:28 mcintyre tvheadend[1505]: transcode: 0001: 03:DVBSUB: ==> Filtered out
Apr 26 22:36:28 mcintyre tvheadend[1505]: transcode: 0001: 05:TEXTSUB: ==> Filtered out
Apr 26 22:36:31 mcintyre tvheadend[1505]: tbl-base: bat: 10788V in 28E2: invalid checksum (len 913, errors 1)
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 29 10
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 11 35
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 15
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: skipped MB in I-frame at 1 16
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: Invalid mb type in I-frame at 0 17
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 18
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 19
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: Invalid mb type in I-frame at 1 20
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 21
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: skipped MB in I-frame at 1 22
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 23
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 24
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 25
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 26
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 27
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 28
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 29
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: Invalid mb type in I-frame at 0 30
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 31
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 32
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 33
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 0 34
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 1 35
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: Warning MVs not available
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: concealing 1170 DC, 1170 AC, 1170 MV errors in I frame
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: using SAR=64/45
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64 SlowShuffle
Apr 26 22:36:32 mcintyre tvheadend[1505]: libav: AVCodecContext: profile High, level 2.1
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 23 25
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 16 17
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 18 18
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 11 19
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 1 20
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 13 21
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 16 22
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 7 23
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 8 24
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 24 26
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: invalid cbp -1 at 0 29
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 12 30
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: Warning MVs not available
Apr 26 22:36:33 mcintyre tvheadend[1505]: libav: AVCodecContext: concealing 561 DC, 561 AC, 561 MV errors in B frame
Apr 26 22:36:34 mcintyre tvheadend[1505]: libav: AVCodecContext: ac-tex damaged at 14 9
Apr 26 22:36:34 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 31 20

the log is pretty full with repeating lines after that and others like this:

Apr 26 22:36:35 mcintyre tvheadend[1505]: libav: AVCodecContext: Warning MVs not available
Apr 26 22:36:35 mcintyre tvheadend[1505]: libav: AVCodecContext: concealing 585 DC, 585 AC, 585 MV errors in B frame
Apr 26 22:36:36 mcintyre tvheadend[1505]: TS: 28E2/10788V/BBC Parliament: MPEG2VIDEO @ #5100 Continuity counter error (total 46)
Apr 26 22:36:36 mcintyre tvheadend[1505]: TS: 28E2/10788V/BBC Parliament: MPEG2AUDIO @ #5101 Continuity counter error (total 51)
Apr 26 22:36:36 mcintyre tvheadend[1505]: TS: 28E2/10788V/BBC Parliament: TELETEXT @ #5103 Continuity counter error (total 50)
Apr 26 22:36:36 mcintyre tvheadend[1505]: libav: AVCodecContext: Invalid mb type in P-frame at 19 11
Apr 26 22:36:36 mcintyre tvheadend[1505]: libav: AVCodecContext: Warning MVs not available
Apr 26 22:36:36 mcintyre tvheadend[1505]: libav: AVCodecContext: concealing 1080 DC, 1080 AC, 1080 MV errors in P frame
Apr 26 22:36:36 mcintyre tvheadend[1505]: libav: AVCodecContext: mb incr damaged
Apr 26 22:36:36 mcintyre tvheadend[1505]: libav: AVCodecContext: mb incr damaged
Apr 26 22:36:36 mcintyre tvheadend[1505]: libav: AVCodecContext: Invalid mb type in P-frame at 20 27
Apr 26 22:36:36 mcintyre tvheadend[1505]: libav: AVCodecContext: 00 motion_type at 0 29
Apr 26 22:36:36 mcintyre tvheadend[1505]: libav: AVCodecContext: slice mismatch

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Mark Clarkstone 7 months ago

Have you tried with just ONE tuner enabled (in tvh)?

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

I'll try just one tuner in a moment.

I restarted the TVH server and it didn't recover, this is the main screen. I got garbled sound and no image.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

I tried turning each tuner off for a little while, but it didn't fix the issue. So now I am rebooting, and hoping that the system won't have trashed the TVH config files.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

I'm using both munin and zabbix to monitor the box. The only interesting thing I see is CPU usage jumping up when I tune to and pause an HD channel in the web interface. An SD channel when paused uses about 25%. When streaming to a miniPC running Kodi, the cpu barely gets off 5%.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

I just noticed there's a new version of TVH, 4.3-1251~gf4ebe33~xenial, and I will try that and see.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Mark Clarkstone 7 months ago

I think your issue is the transcoding. When you notice the garbage output try playing a stream in VLC rather than the browser.

If you get garbage with VLC then yes there is something wrong, otherwise the machine is struggling to keep up with transcoding.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

the upgraded TVH application still went bad.

I can play the recordings directly from the .ts and they are corrupted, SD or HD. I can play live or recordings in the browser and they are corrupted too. I can try and play live on my phone using one of the android apps and they also show the stream is corrupted. So I am fairly sure that it's not the transcoding that is corrupt.

After a reboot, everything is fine. Recordings are fine. Live streaming, browser or kodi or android app is fine - HD or SD or radio.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

I have the TBS 6902 PCIe board; it was brand new and sealed when I bought it.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 7 months ago

The PC I am using was in use as my daughter's PC for a couple of years before I bought here a new core-i5 4th gen to replace it, so I am fairly confident that the machine itself is OK.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 4 months ago

I've now replaced the previous PC with a much newer one, it's a desktop again, Intel motherboard, core-i3 2nd gen (sandy bridge) with 4GB of RAM. A pretty well tested machine.

I was hopeful that this would cure my corruption problem, sadly, it still happens.

I'd left my TVH server completely turned off for two months because of this issue, there was no point in running it if recordings would be corrupted unpredictably, or the streams would be unwatchable without a reboot! Sadly, it looks like I'll be abandoning this project altogether.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Mark Clarkstone 4 months ago

Paul M wrote:

I've now replaced the previous PC with a much newer one, it's a desktop again, Intel motherboard, core-i3 2nd gen (sandy bridge) with 4GB of RAM. A pretty well tested machine.

I was hopeful that this would cure my corruption problem, sadly, it still happens.

I'd left my TVH server completely turned off for two months because of this issue, there was no point in running it if recordings would be corrupted unpredictably, or the streams would be unwatchable without a reboot! Sadly, it looks like I'll be abandoning this project altogether.

Have you tried enabling linked input? If you'd like I can take a look with you over teamviewer.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 2 months ago

Hi,
sorry, I didn't see your reply - the TVH forum's email sending function generates invalid email which doesn't get through to me.

I have powered up my TVH server, first time in months, and will try setting the linked adaptors/input.

I also contacted TBS in case the card is faulty.

thanks

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by saen acro 2 months ago

Is motherboard branded Gigabyte HP AsRock Lenovo.
Is IRQ usage increase when tuner is used?

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 2 months ago

I'm currently running this:

  • motherboard: Intel BEH6110H
  • RAM: 4GB
  • mirrored drives: Seagate Barracuda 7200.10 ST3750640AS
  • Ubuntu 16.04.04-LTS
  • kernel 4.4.0-116-lowlatency
  • CPU i3-2100, family 6, model 42, stepping 7, microcode 0x1a
$ lspci | grep SAA
03:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)

$ cat /proc/interrupts 
           CPU0       CPU1       CPU2       CPU3       
  0:         36          0          0          0   IO-APIC   2-edge      timer
  1:          3          0          0          0   IO-APIC   1-edge      i8042
  5:          0          0          0          0   IO-APIC   5-edge      parport0
  8:          1          0          0          0   IO-APIC   8-edge      rtc0
  9:          3          0          0          0   IO-APIC   9-fasteoi   acpi
 12:          4          0          0          0   IO-APIC  12-edge      i8042
 16:         25          0          0          0   IO-APIC  16-fasteoi   ehci_hcd:usb1
 18:    1301129          0          0          0   IO-APIC  18-fasteoi   SAA716x Core
 23:         29          0          0          0   IO-APIC  23-fasteoi   ehci_hcd:usb2
 24:          0          0          0          0   PCI-MSI 458752-edge      PCIe PME
 25:          0          0          0          0   PCI-MSI 462848-edge      PCIe PME
 26:      68205          0          0          0   PCI-MSI 512000-edge      0000:00:1f.2
 27:     277295          0          0          0   PCI-MSI 409600-edge      eno1
 28:          9          0          0          0   PCI-MSI 32768-edge      i915
 29:         13          0          0          0   PCI-MSI 360448-edge      mei_me
 30:        659          0          0          0   PCI-MSI 442368-edge      snd_hda_intel
NMI:         13         16         10         14   Non-maskable interrupts
LOC:    1090239    1224305     427905     533714   Local timer interrupts
SPU:          0          0          0          0   Spurious interrupts
PMI:         13         16         10         14   Performance monitoring interrupts
IWI:          0          0          0          0   IRQ work interrupts
RTR:          0          0          0          0   APIC ICR read retries
RES:       7579       7213      14845       4780   Rescheduling interrupts
CAL:        902        814       1031        888   Function call interrupts
TLB:        513        411        423        344   TLB shootdowns
TRM:          0          0          0          0   Thermal event interrupts
THR:          0          0          0          0   Threshold APIC interrupts
DFR:          0          0          0          0   Deferred Error APIC interrupts
MCE:          0          0          0          0   Machine check exceptions
MCP:         32         32         32         32   Machine check polls
ERR:          0
MIS:          0
PIN:          0          0          0          0   Posted-interrupt notification event
PIW:          0          0          0          0   Posted-interrupt wakeup event

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 2 months ago

I just dist-upgraded to 4.3-1292~g9b9ee68~xenial-amd64, same kernel but now Ubuntu-16.04.05-LTS

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by saen acro 2 months ago

you should see interrupts as graph /monintorix for example/

intel boards is also not so good /they stop production also/
disable all unused stuff
com port parallel port sound card etc.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 2 months ago

some time today, the server failed again, and when I tried to view a TV channel live, I got the usual scrambled mess. The PC was booted up about 1100BST, so it failed about 8 hours later.

I looked in /var/log/syslog and found this:

Sep  2 19:12:29 mcintyre kernel: [39238.047519] irq 18: nobody cared (try booting with the "irqpoll" option)
Sep  2 19:12:29 mcintyre kernel: [39238.047549] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           OE   4.4.0-116-lowlatency #140-Ubuntu
Sep  2 19:12:29 mcintyre kernel: [39238.047551] Hardware name:                  /DH61CR, BIOS BEH6110H.86A.0028.2011.0715.1815 07/15/2011
Sep  2 19:12:29 mcintyre kernel: [39238.047552]  0000000000000086 731cdad3b862bbf2 ffff88011fa03e60 ffffffff81409811
Sep  2 19:12:29 mcintyre kernel: [39238.047555]  ffff8800d6469600 ffff8800d64696d4 ffff88011fa03e88 ffffffff810e33c3
Sep  2 19:12:29 mcintyre kernel: [39238.047557]  ffff8800d6469600 0000000000000000 0000000000000012 ffff88011fa03ec0
Sep  2 19:12:29 mcintyre kernel: [39238.047559] Call Trace:
Sep  2 19:12:29 mcintyre kernel: [39238.047561]  <IRQ>  [<ffffffff81409811>] dump_stack+0x63/0x82
Sep  2 19:12:29 mcintyre kernel: [39238.047568]  [<ffffffff810e33c3>] __report_bad_irq+0x33/0xc0
Sep  2 19:12:29 mcintyre kernel: [39238.047570]  [<ffffffff810e3757>] note_interrupt+0x247/0x290
Sep  2 19:12:29 mcintyre kernel: [39238.047572]  [<ffffffff810e0772>] handle_irq_event_percpu+0xc2/0x210
Sep  2 19:12:29 mcintyre kernel: [39238.047574]  [<ffffffff810e08fc>] handle_irq_event+0x3c/0x60
Sep  2 19:12:29 mcintyre kernel: [39238.047577]  [<ffffffff810e3dbc>] handle_fasteoi_irq+0x9c/0x190
Sep  2 19:12:29 mcintyre kernel: [39238.047580]  [<ffffffff81032353>] handle_irq+0x23/0x30
Sep  2 19:12:29 mcintyre kernel: [39238.047583]  [<ffffffff8185fd2b>] do_IRQ+0x4b/0xe0
Sep  2 19:12:29 mcintyre kernel: [39238.047585]  [<ffffffff8185d3bf>] common_interrupt+0xbf/0xbf
Sep  2 19:12:29 mcintyre kernel: [39238.047586]  <EOI>  [<ffffffff816eae93>] ? cpuidle_enter_state+0x113/0x2f0
Sep  2 19:12:29 mcintyre kernel: [39238.047591]  [<ffffffff816eb0a7>] cpuidle_enter+0x17/0x20
Sep  2 19:12:29 mcintyre kernel: [39238.047594]  [<ffffffff810c9632>] call_cpuidle+0x32/0x60
Sep  2 19:12:29 mcintyre kernel: [39238.047596]  [<ffffffff816eb089>] ? cpuidle_select+0x19/0x20
Sep  2 19:12:29 mcintyre kernel: [39238.047598]  [<ffffffff810c991e>] cpu_startup_entry+0x2be/0x390
Sep  2 19:12:29 mcintyre kernel: [39238.047601]  [<ffffffff8184fee9>] rest_init+0x89/0x90
Sep  2 19:12:29 mcintyre kernel: [39238.047605]  [<ffffffff81f6402f>] start_kernel+0x496/0x4b7
Sep  2 19:12:29 mcintyre kernel: [39238.047607]  [<ffffffff81f63120>] ? early_idt_handler_array+0x120/0x120
Sep  2 19:12:29 mcintyre kernel: [39238.047609]  [<ffffffff81f63339>] x86_64_start_reservations+0x2a/0x2c
Sep  2 19:12:29 mcintyre kernel: [39238.047611]  [<ffffffff81f63485>] x86_64_start_kernel+0x14a/0x16d
Sep  2 19:12:29 mcintyre kernel: [39238.047613] handlers:
Sep  2 19:12:29 mcintyre kernel: [39238.047623] [<ffffffff810e0980>] irq_default_primary_handler threaded [<ffffffffc0828fa0>] saa716x_budget_pci_irq [saa716x_tbs_dvb]
Sep  2 19:12:29 mcintyre kernel: [39238.047669] Disabling IRQ #18
Sep  2 19:12:59 mcintyre kernel: [39267.747308] demux_worker: called but nothing to do
Sep  2 19:12:59 mcintyre kernel: [39267.847322] demux_worker: called but nothing to do
Sep  2 19:13:19 mcintyre kernel: [39287.747212] demux_worker: called but nothing to do
Sep  2 19:13:19 mcintyre kernel: [39287.847226] demux_worker: called but nothing to do
Sep  2 19:14:09 mcintyre kernel: [39337.846980] demux_worker: called but nothing to do

and many more demux workers log entries.

tried restarting TVH, still didn't work. had to reboot. immediately everything working again just fine.

I'll haul a monitor over and check that all unnecessary hardware is disabled, but it doesn't look as if the card is sharing its interrupt with anything.

RE: corrupted video with TBS twin port card on DVB-S or DVB-S2, HD or SD channels - Added by Paul M 2 months ago

looking at the /var/log/tvheadend.log file I saw this soon after the interrupts message in syslog

Sep  2 19:13:26 mcintyre tvheadend[2342]: mpegts: 12187.5H in 28E2 - scan timed out (1/0 tables)
Sep  2 19:13:26 mcintyre tvheadend[2342]: subscription: 04FB: "scan" unsubscribing
Sep  2 19:13:36 mcintyre tvheadend[2342]: mpegts: 12441V in 28E2 - tuning on TurboSight TBS 6982SE DVB-S/S2 #0 : DVB-S #0
Sep  2 19:13:36 mcintyre tvheadend[2342]: subscription: 04FC: "keep" unsubscribing
Sep  2 19:13:36 mcintyre tvheadend[2342]: subscription: 0505: "keep" subscribing to mux "12441V", weight: 1, adapter: "TurboSight TBS 6982SE DVB-S/S2 #0 : DVB-S #0", network: "28E2", service: "Raw PID Subscription" 
Sep  2 19:13:36 mcintyre tvheadend[2342]: subscription: 0504: "scan" subscribing to mux "12441V", weight: 2, adapter: "TurboSight TBS 6982SE DVB-S/S2 #0 : DVB-S #0", network: "28E2", service: "Raw PID Subscription" 
Sep  2 19:13:43 mcintyre tvheadend[2342]: linuxdvb: TurboSight TBS 6982SE DVB-S/S2 #1 : DVB-S #0 - poll TIMEOUT
Sep  2 19:13:43 mcintyre tvheadend[2342]: linuxdvb: TurboSight TBS 6982SE DVB-S/S2 #1 : DVB-S #0 - retune nodata
Sep  2 19:13:46 mcintyre tvheadend[2342]: mpegts: 12441V in 28E2 - scan no data, failed
Sep  2 19:13:46 mcintyre tvheadend[2342]: subscription: 0504: "scan" unsubscribing

It would seem then that somehow the card generates an interrupt which the driver fails to service, and after that the kernel driver or the card gets stuck and needs to be reset with a reboot.

1 2 (1-25/43)