tvheadend 4.2 on beaglebone black

Bram de Greve

Hi all,

Has anyone tried running tvheadend 4.2 on a beaglebone black? I'm having issues with the cpu getting totally blocked ...

For several years, I've been running tvheadend 4.0 on a beaglebone black with Debian Wheezy, without any problems.

But, today, I tried to upgrade to 4.2 with Ubuntu Xenial (as that's the only one for which tvheadend has armhf support), still on that same beaglebone black. And it's not going well ... Currently, I'm using the 4.14.6-ti-r17 kernel.

At first, it went all right, but as soon as I pressed record, it totally blocked the cpu.

But it happens randomly too.

Any advice appreciated.

Best,
Bram.

mpmc

Apart from [[Debugging]] & [[Traces]] this is going to be a hard one.. If you can get a log of some kind please open an issue, but..

What thread does

top -p <pid of tvh> -H

show as using 100% cpu usage?

Bram de Greve

I didn't know you could do that with top! nice ...

I get something like this:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2343 hts 20 0 69328 8704 4800 R 91.7 1.8 0:04.03 tvheadend 2348 hts 20 0 69328 8704 4800 S 0.3 1.8 0:00.09 tvh:mtick 2384 hts 20 0 69328 8704 4800 S 0.3 1.8 0:00.01 tvh:avahi 2344 hts 20 0 69328 8704 4800 S 0.0 1.8 0:00.03 tvh:log 2345 hts 20 0 69328 8704 4800 S 0.0 1.8 0:00.00 tvh:notify 2346 hts 20 0 69328 8704 4800 S 0.0 1.8 0:00.01 tvheadend

Not very helpfull I guess.

I attached a log file I could generate with "--debug +all", is that correct? I tried to apt-get install tvheadend-dbg, but that package is missing for at least xenial armhf. So I couldn't make traces.

Now, it just halts even before I can go to http://tristania:9981. Maybe because it tries to start a autorec recording, but I'm not sure.

Interestingly enough, it go runs all the epggrab modules while only the OTA EIT DVB Grabber should be enabled. Now I must confess that I tried to reuse the existing ~/.hts/tvheadend configuration. I shall try with fresh install as well...

Also, here's two of the stall messages, if that's at all usefull:


[ 3141.467510] INFO: rcu_sched self-detected stall on CPU
[ 3141.473910]  0-...: (5250 ticks this GP) idle=532/140000000000002/0 softirq=50525/50525 fqs=0
[ 3141.482929]   (t=5250 jiffies g=37261 c=37260 q=1)
[ 3141.488516] rcu_sched kthread starved for 5250 jiffies! g37261 c37260 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=0
[ 3204.482254] INFO: rcu_sched self-detected stall on CPU
[ 3204.488405]  0-...: (20976 ticks this GP) idle=532/140000000000002/0 softirq=50525/50525 fqs=0
[ 3204.497514]   (t=21003 jiffies g=37261 c=37260 q=1)
[ 3204.503163] rcu_sched kthread starved for 21003 jiffies! g37261 c37260 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=0

Saen Acro

Disable EPG modules and see is there a difference.

Next time invest your money in "jaguarboard" ;)

Bram de Greve

Update: starting with fresh configuration didn't help. It halts already during scanning of the muxes

Bram de Greve

saen acro wrote:
> Disable EPG modules and see is there a difference.
>

> Next time invest your money in "jaguarboard" ;)

Any help on how to disable the EPG modules without access to the web UI?

I have already way too many rpis/beaglebones/... minicomputes laying around :-) but I guess a x86 would be a nice addition.

mpmc

I think you should open an issue. Those

2017-12-18 22:50:54.683 [  ERROR]:main: time value out of range (10143003829) of time_t

don't look very promising.

Bram de Greve

I've created this issue: http://tvheadend.org/issues/4805

I've also flashed the beaglebone back to the backup I prudently made before. I'm back to tvheadend 4.0.8 on debian wheezy, which for the time being works perfectly fine.

mpmc

Bram de Greve wrote:
> I've created this issue: http://tvheadend.org/issues/4805 >

>I've also flashed the beaglebone back to the backup I prudently made before. I'm back to tvheadend 4.0.8 on debian wheezy, which for the time being works perfectly fine.

Is the kernel the same by any chance? Or is it older?

Kali Mero

i have got the similar issue with ubuntu, switched to debian with raspbian repo and stable-4.2 work fine

http://beagleboard.org/latest-images

https://tvheadend.org/projects/tvheadend/wiki/AptRepository

not sure if is kernel related as debian use 4.4 kernel and on ubuntu i have tested 4.9 and 4.14

Bram de Greve

Mark Clarkstone wrote:
>

> Is the kernel the same by any chance? Or is it older?

Sorry, I was away.

No, the working installation has a much older kernel: 3.8.13-bone20 #1 SMP Wed May 29 03:11:01 UTC 2013 armv7l GNU/Linux.

Bram de Greve

Kali Mero wrote:
> i have got the similar issue with ubuntu, switched to debian with raspbian repo and stable-4.2 work fine
>
> http://beagleboard.org/latest-images > https://tvheadend.org/projects/tvheadend/wiki/AptRepository >

> not sure if is kernel related as debian use 4.4 kernel and on ubuntu i have tested 4.9 and 4.14

I could give it another try with the 4.4 kernel as well, I don't think I tried that one (The debian and ubuntu distros both use the same kernel builds, I believe)

Could you tell me exactly what kernel you're running? Mainline or TI? with or without RT?

Kali Mero

I have just upgraded kernel to 4.14.10-ti-r21 and all works fine.
Looks to be something in ubuntu 16.04 for beagleboard

Bram de Greve

I can now confirm this works with debian stretch

I've used "RobertCNelson's image for console" , more precisely the one of "7th January" , running kernel 4.9.74-ti-r90

On top, I've installed the raspbianstretch build of tvheadend:

deb https://dl.bintray.com/mpmc/deb/ raspbianstretch stable-4.2

So far, it's been operating within the parameters :-)

mpmc

Bram de Greve wrote:

> So far, it's been operating within the parameters :-)

Glad to hear it :)

Bram de Greve

One more question though:

An armhf build of tvheadend is only officially available for ubuntu xenial. What is the reason this one has been choosen over debian stretch (which is the officially supported OS for both beaglebone and raspberry pi - in the form of raspbian).

I'm guessing it's because someone on the tvheadend team has a use for it :-) but I'm wondering for what target device ...

Thanks,
Bram.

Kali Mero

the only reason can be, ubuntu is much popular
anyway ubuntu derivatives from debian, not much different

mpmc

Bram de Greve wrote:
> One more question though:
>
> An armhf build of tvheadend is only officially available for ubuntu xenial. What is the reason this one has been choosen over debian stretch (which is the officially supported OS for both beaglebone and raspberry pi - in the form of raspbian).
>
> I'm guessing it's because someone on the tvheadend team has a use for it :-) but I'm wondering for what target device ...
>
> Thanks,

> Bram.

4.2 was released before those builds were added to Doozer. This is why there's raspbian jessie/stretch for 4.3 but not 4.2. When 4.4 is released this should be resolved.