Tvheadend constantly crashing

Raymond Paulsen

Iam having some issues with tvh after last code changes,

my tvheadend servere constantly crashing after around 5 min.

the hts process is still running but tvh stops working.

no log errors is produced either this is the only stuff i can find in the logs

Mar 11 04:08:39 tv kernel: [ 2782.835743] DVB: adapter 2 frontend 0 frequency 9399990 out of range (950000..2150000)
Mar 11 04:13:08 tv kernel: [ 3052.504473] DVB: adapter 2 frontend 0 frequency 9399990 out of range (950000..2150000)
Mar 11 04:13:08 tv kernel: [ 3052.504916] DVB: adapter 1 frontend 0 frequency 9399990 out of range (950000..2150000)
Mar 11 04:13:08 tv kernel: [ 3052.577376] DVB: adapter 0 frontend 0 frequency 9399990 out of range (950000..2150000)
Mar 11 04:24:10 tv kernel: [ 3714.039255] DVB: adapter 1 frontend 0 frequency 9399990 out of range (950000..2150000)
Mar 11 04:26:35 tv kernel: [ 3858.835831] DVB: adapter 0 frontend 0 frequency 9399990 out of range (950000..2150000)
Mar 11 04:37:19 tv kernel: [ 4503.348766] DVB: adapter 1 frontend 0 frequency 9640010 out of range (950000..2150000)
Mar 11 04:38:52 tv kernel: [ 4596.267150] DVB: adapter 0 frontend 0 frequency 9640010 out of range (950000..2150000)
Mar 11 06:25:06 tv rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2203" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar 11 08:04:12 tv kernel: [16915.958777] DVB: adapter 2 frontend 0 frequency 9640010 out of range (950000..2150000)
Mar 11 08:04:17 tv kernel: [16920.972708] DVB: adapter 2 frontend 0 frequency 9399990 out of range (950000..2150000)
Mar 11 22:10:51 tv kernel: [67715.185940] timeshift_reade[23092]: segfault at 8 ip 080bba37 sp 2f5cf160 error 4 in tvheadend[8048000+b3000]
Mar 11 22:17:47 tv kernel: [68131.596371] linuxdvb_fronte[23209]: segfault at 8 ip 0809c279 sp a34ec6e0 error 6 in tvheadend[8048000+b3000]
Mar 11 22:17:50 tv kernel: [68134.100045] cx8802_start_dma() Failed. Unsupported value in .mpeg (0x00000001)
Mar 12 01:09:21 tv kernel: [78425.037248] linuxdvb_fronte[26487]: segfault at 8 ip 0809c279 sp 6297b6e0 error 6 in tvheadend[8048000+b3000]
Mar 12 01:15:24 tv kernel: [78788.703278] htsp_write_sche[26884]: segfault at 0 ip 0806e819 sp 8a9fd200 error 6 in tvheadend[8048000+b3000]
Mar 12 01:20:50 tv kernel: [79114.253544] linuxdvb_fronte[27328]: segfault at 8 ip 0809c279 sp a06f36e0 error 6 in tvheadend[8048000+b3000]
Mar 12 01:23:40 tv kernel: [79284.531196] htsp_write_sche[27792]: segfault at 0 ip 0806e819 sp a70f2200 error 6 in tvheadend[8048000+b3000]
Mar 12 06:25:06 tv rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2203" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

ProfYaffle

Not sure where you got tvheadend from, but I suggest you build it with debug symbols or install the .dbg deb file if your OS supports it. Switch on as much debugging as possible and see what the log look like then.

It might be helpful to run it as gdb, but I'd have to defer to a developer for that... let's get as much information as possible.

Also, what does "last code" mean... I'd suggest you try an earlier version and/or a later one to help isolate the code changes that caused this, if any. Again, debugging should help isolate teh specific code.

Raymond Paulsen

it seems the cause of this issues is related to the dvb-s/s2 signals, i noticed the recent weather has moved the antenna a little and the signals is way to low.

this is causing the issues, it seems that tvh / fw cant handle the increased BER or something.

anyway i adjusted the antenna and magically the server was working ok again.. there is no logs produced by the firmware, tvheadend or the kernel even in debug mode

Raymond Paulsen

i have further investigated this problem and there seems to be a bug in newer linux kernels.

kernel 2.6 is working flawless but later one after 3.2 is broken

cx8802_start_dma() Failed. Unsupported value in .mpeg (0x00000001)

so that was the end of the hauppage nova s2 cards

ProfYaffle

FWIW, I use PCTV S2 USB sticks on kernel 3.5 with no problem:

ian@Server:~$ uname -a

Linux Server 3.5.0-47-generic #71~precise1-Ubuntu SMP Wed Feb 19 22:02:52 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

... so it's not all Hauppauge stuff.

How much more recent than 3.2 did you try? I ask because there's some Fedora stuff out there that saw this problem in later 3.3 kernels... I wonder if that's true for other distros (you don't say what you're running).

Raymond Paulsen

iam sorry for the lack of information.

Iam running 3 x hauppage nova s2 PCI cards on a dell poweredge 2650

iam using debian wheezy i386 (32 bit)

Linux 3.2.0-4-686-pae on i686

is there any options to upgrade this?

ProfYaffle

I'd guess you have to search for Wheezy backports - maybe there's a PPA that includes later kernels.

EDIT

http://www.neowin.net/forum/topic/1162482-debian-backport-kernel/

Use at your own risk!

Raymond Paulsen

Great stuff.

i did apply the backport and updated kernel to 3.13, this seems to fix the issue with the firmware.

for now the servere runs fine with no issues. to be honest this is the weirdest shit i have seen with debian stable.

what can be the couse for this?

as it stands for now hauppage nova s2 pci cards and debian wheezy is not compatible without modifications.

ProfYaffle

I think it's simply a specific kernel - and that's the one that Wheezy is using.

https://packages.debian.org/wheezy/kernel/

I always thought that 'buntu and Debian were really close relatives... the more I see about Debian, though, the more I scratch my head. It seems to be more hassle than it's worth. I'm sure someone would give me the good reason to use it, though, but I'll stick with Xubuntu/Lubuntu!

Raymond Paulsen

It seems that its a specific kernel. Currently the wheezy stable 3.2.

The weird stuff is i have used this kernel sins it become stable and the problem seems to come gradualy, at first the firmware worked flawless. Could it be apt security updates later on affecting the kernel cousing this unstability?

In general i use only debian for my serveres. I dont like how things is layed down in ubuntu.

debian framework is very good and i have never had any big problems with it..

ubuntu has to frequent updates and a short lifespan then debian. That is a real issue for me..

Debian is also a more lightweight distro then ubuntu it tends to run with a better performance the ubuntu.

But dont get me wrong ubuntu is a good distro but for desktop use.

by the way i dont use any gui like kde or gnome so for me that is not important.

Dioni Rodriguez

I have the same problem.

My kernel is 3.2.0-4-amd64 with whezzy but I can not update the kernel.

I followed the steps in the link backports, but not if I do bad, I change some parameter, or leave the iwlwifi?

(1-4/4)

Raymond Paulsen

there is no problem in adding the backport repo, should be a easy, if you get any problems you can revert the kernel to.

follow the steps in the guide carefully and you will be fine.

Dioni Rodriguez

I followed the exact steps of this url

http://www.neowin.net/forum/topic/1162482-debian-backport-kernel/

I have not changed any command or anything, but does not change the kernel version

Raymond Paulsen

You dont tell anything about your system. Please describe it.

you are aware sudo is not added default in debian. If you dont have added it you should remove all sudo from the commands.

Dioni Rodriguez

Hello

My system is Debian amd 64 Whezzy.

My card is a Hauppauge 4000 DVB-T and DVB-S/S2. The DVB-T working properly.

The firmware of the card I think is CX24116/CX24118C

Greetings and thanks

Dioni Rodriguez

Ok, since I have upgraded to 3.13 kernel

My satellite is Astra 19.2 and according TVHeadend has only 1 mux.

I'll have to do it manually ... As I see that the card already this ok?

Greetings and thanks