Bug #4805
time value out of range (10152318900) of time_t
0%
Description
I tried upgrading by install on a beaglebone black from tvheadend 4.0.8 on debian wheezy to tvheadend 4.2 on ubuntu xenial, armhf.
It doesn't properly work, as tvheadend very often hangs the cpu, see http://tvheadend.org/boards/5/topics/30242.
Mark suggested filing this issue, as this line from the log doesn't look very promising:
2017-12-18 22:50:54.683 [ ERROR]:main: time value out of range (10143003829) of time_t 2017-12-18 22:50:54.692 [ ERROR]:main: time value out of range (10150786795) of time_t 2017-12-18 22:50:54.700 [ ERROR]:main: time value out of range (10142318432) of time_t ...
The symptom is that tvheadend totally brings the system to a halt. Following messages are appear on the console:
[ 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
Files
History
Updated by Jaroslav Kysela almost 7 years ago
The time_t out of range messages are caused by the too high retention or removal settings in the DVR profile. The application cannot hang the system, it appears like another issue. You may try to use 'top -H' to see which thread causes the 100% CPU usage.
Updated by Mark Clarkstone almost 7 years ago
Jaroslav Kysela wrote:
The time_t out of range messages are caused by the too high retention or removal settings in the DVR profile. The application cannot hang the system, it appears like another issue. You may try to use 'top -H' to see which thread causes the 100% CPU usage.
Thanks for clarifying what those errors are, at least that can be ruled out :).