Solved System shutdown / hybernate after 20min running kodi
#1
Hi, so here is my setup a ubuntu 16.04 minimal with Xorg and LightDM on a computer with an Asrock motherboard with a baytrail cpu
and autologin for kodi session

The computer is running well 24/7, but when I start reading a video (whatever it is) or TV then after 15/20min the system just shutdown or hibernate with no reasons
I tryied and search the logs, but there is no kodi crashlog, nothing in system.log or Xsession.log or Lightdm.log appear at the time of the shutdown

So I'm lost with that thing,
Did somebody has the same issue?
Maybe I'm not searching in the right place so any help is welcome
thanks
best regards
Reply
#2
well it happens again yesterday and I managed to get a log file

http://pastebin.com/TtDDa9z1

I thought it was due to HW acceleration so I disabled VAAPI (and let VDPAU on) but still it happens again
thanks a lot
Reply
#3
try this

http://askubuntu.com/questions/291135/ho...ter-10-min

add the following line

xset s off && xset -dpms

to the end of the file .profile (located at /home/{yourusernamehere}/.profile)
Reply
#4
thanks but it's not about this

my 2 guess are smb or hardware acceleration
for smb the sources are well added and for pvr I also add timeshift/recordings shared folder as source and it seems to work as TV doesn't crash kodi today
but as I was watching an mkv h264 video kodi crashed and I got this

http://pastebin.com/UVxL7Tzn

and this tells me it's something about VAAPI so I will deactivate it to see what happens
Reply
#5
Nobody can help you with a cut Debug Log ... turn on debugging and wait until it shutsdown ... then post the log.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#6
ok thanks I will, I thought that was a debug log
Reply
#7
so first I tried this
Ubuntu 14.04 LTS:
Code:
sudo apt-add-repository ppa:wsnipex/vaapi
sudo apt-add-repository ppa:wsnipex/mesa

Ubuntu 16.04 LTS:
Code:
sudo apt-add-repository ppa:wsnipex/vaapi

For both afterwards:
Code:
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install i965-va-driver

sudo reboot

and thought it was good because it runs for 3h without a problem
but it happend again
here is the debug log

http://pastebin.com/cmsGai6X

this sequence
Code:
22:02:42.991 T:139651801147136   DEBUG: ffmpeg[7F0337FFE700]: [h264] nal_unit_type: 1, nal_ref_idc: 0
22:02:43.079 T:139651801147136   DEBUG: ffmpeg[7F0337FFE700]: [h264] nal_unit_type: 1, nal_ref_idc: 2
22:02:43.158 T:139651801147136   DEBUG: Previous line repeats 1 times.
22:02:43.158 T:139651801147136   DEBUG: ffmpeg[7F0337FFE700]: [h264] nal_unit_type: 1, nal_ref_idc: 0
22:02:43.199 T:139651801147136   DEBUG: ffmpeg[7F0337FFE700]: [h264] nal_unit_type: 5, nal_ref_idc: 3
just repeat over and over until the computer just freeze or shutdown

thanks a lot for helping
Reply
#8
Does it freeze? or does it shutdown?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#9
Quote:21:55:16.323 T:139652465535360 NOTICE: Host CPU: Intel® Celeron® CPU J1900 @ 1.99GHz, 4 cores available

Ah! tell that right away next time, this is your issue: https://bugzilla.kernel.org/show_bug.cgi?id=109051 - in short, add: intel_idle.max_cstate=1 to the kernel commandline
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#10
well I guess it crash or shutdown because computer is not reachable from putty after that

I saw that on the link you posted

"same here on an Asrock Q1900-ITX (Intel Celeron J1900): random freezes in X session"

got the exact same motherboard, but it's also said it's a workaround that help improve time before crash but don't fix it

anyway i'll give it a try of course but I don't know how to add that to kernel , i'll go search for that

and is there something to be done in the bios too??

and also is it only happening with ubuntu or it will with debian too?

thanks a lot fritsch
Reply
#11
Add what I said via /etc/default/grub behind the quiet splash afterwards run sudo update-grub and reboot.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#12
ok thank u
I'm trying to understand so I'm reading comments
would this be better or change anything ?
Code:
I, too, can confirm this issue on systems that use an Intel Celeron [email protected] or an Intel Celeron [email protected]. While adding "intel_idle.max_cstate=1" to kernel command-line fixed the issue, the regression in GPU performance wasn't acceptable. Bumping it to "intel_idle.max_cstate=2" seems to make it run with adequate GPU performance while presenting no more hard lock-ups.
Reply
#13
well I also found a patch

https://github.com/endlessm/linux/commit...1d56f91441

https://bugzilla.kernel.org/attachment.c...ction=edit

but don't know how to apply ??
Reply
#14
(2017-02-16, 10:25)salora Wrote: ok thank u
I'm trying to understand so I'm reading comments
would this be better or change anything ?
Code:
I, too, can confirm this issue on systems that use an Intel Celeron [email protected] or an Intel Celeron [email protected]. While adding "intel_idle.max_cstate=1" to kernel command-line fixed the issue, the regression in GPU performance wasn't acceptable. Bumping it to "intel_idle.max_cstate=2" seems to make it run with adequate GPU performance while presenting no more hard lock-ups.

there is no regression in gpu performance. All this setting does is to not let the CPU go into lower sleep states.

If you want to use the patch, you must recompile the kernel yourself.
Reply
#15
or thanks a lot wsnipex
I will do as fritsch said then
and wait for the patch to be include in next kernel Wink
Reply

Logout Mark Read Team Forum Stats Members Help
System shutdown / hybernate after 20min running kodi0