Hi to all,
So today after a few months without updating i decided to run an manual apt-get update etc... and everything worked fine, no warning no nothing...
So machine reboots and i got the "starting Kodi" splash screen stuck for a while then it dropped to command line asking for user/pass (not the 1st time it happens so i was not worried), but then i tried "start xbmc" (like i do everytime this happens ) and the splash screen dropped back to CLI after 2 or 3 minutes... Rebooted, tested the file system (no problems found) and again the same thing (tried several times now).
Any ideas on how to solve this?
Pi 1 B , no changes have been made on the config (so OC@ 1Ghz)
Dmesg paste
here
Terminal
uname -r
4.14.58+
Terminal
cat /etc/issue
XBian GNU/Linux 9 \n \l
Thank you to all.
Please remove /var/log/upstart/xbmc.log - reboot - and then post
Kodi's logfile and /var/log/upstart/xbmc.log
(30th Jul, 2018 03:37 AM)Nachteule Wrote: [ -> ]Please remove /var/log/upstart/xbmc.log - reboot - and then post
Kodi's logfile and /var/log/upstart/xbmc.log
Also reboot or shutdown -r command now just shutdowns the unit.... Will post the file in a few minutes.
Thanks.
(30th Jul, 2018 03:37 AM)Nachteule Wrote: [ -> ]Please remove /var/log/upstart/xbmc.log - reboot - and then post
Kodi's logfile and /var/log/upstart/xbmc.log
File content:
Code:
1159 (process ID) old priority 0, new priority 3
1232 (process ID) old priority 0, new priority 3
start: Job failed to start
xbmc stop/post-start, process 1208
post-start process 1209
Still missing Kodi's log file
(30th Jul, 2018 04:01 AM)Nachteule Wrote: [ -> ]Still missing Kodi's log file
Sorry. Here it is and is quite small....
Code:
18:47:14.252 153.643967 T:2985961984 NOTICE: special://profile/ is mapped to: special://masterprofile/
18:47:14.643 154.034897 T:2985961984 NOTICE: -----------------------------------------------------------------------
18:47:14.992 154.383438 T:2985961984 NOTICE: Starting Kodi (17.6 Git:2017-11-18-433b93a). Platform: Linux ARM 32-bit
18:47:14.992 154.383774 T:2985961984 NOTICE: Using Release Kodi x32 build (version for Raspberry Pi)
18:47:14.992 154.384003 T:2985961984 NOTICE: Kodi compiled Nov 19 2017 by GCC 6.3.0 for Linux ARM 32-bit version 4.9.34 (264482)
18:47:18.267 157.659195 T:2985961984 NOTICE: Running on XBian 1.0 (knockout), kernel: Linux ARM 32-bit version 4.14.58+
18:47:18.509 157.900269 T:2985961984 NOTICE: FFmpeg version/source: ffmpeg-3.1-kodi
18:47:18.509 157.900833 T:2985961984 NOTICE: Host CPU: ARMv6-compatible processor rev 7 (v6l), 1 core available
18:47:18.509 157.901047 T:2985961984 NOTICE: ARM Features: Neon disabled
18:47:18.646 158.037766 T:2985961984 NOTICE: special://xbmc/ is mapped to: /usr/local/share/kodi
18:47:18.646 158.038101 T:2985961984 NOTICE: special://xbmcbin/ is mapped to: /usr/local/lib/kodi
18:47:18.647 158.038300 T:2985961984 NOTICE: special://xbmcbinaddons/ is mapped to: /usr/local/lib/kodi/addons
18:47:18.647 158.038498 T:2985961984 NOTICE: special://masterprofile/ is mapped to: /home/xbian/.kodi/userdata
18:47:18.647 158.038696 T:2985961984 NOTICE: special://envhome/ is mapped to: /home/xbian
18:47:18.647 158.038879 T:2985961984 NOTICE: special://home/ is mapped to: /home/xbian/.kodi
18:47:18.647 158.039078 T:2985961984 NOTICE: special://temp/ is mapped to: /home/xbian/.kodi/temp
18:47:18.648 158.039276 T:2985961984 NOTICE: special://logpath/ is mapped to: /home/xbian/.kodi/temp
18:47:18.954 158.345810 T:2985961984 NOTICE: The executable running is: /usr/local/lib/kodi/kodi.bin
18:47:24.004 163.396194 T:2985961984 NOTICE: Local hostname: xbianQuarto
18:47:26.442 165.833847 T:2985961984 NOTICE: Log File is located: /home/xbian/.kodi/temp//kodi.log
18:47:27.530 166.921967 T:2985961984 NOTICE: -----------------------------------------------------------------------
18:47:51.048 190.439819 T:2985961984 NOTICE: load settings...
Yes, indeed. Never seen such a small log file. And no error there, very strange.
Maybe enabling DEBUG messages brings some light into the dark
Please add
to file /etc/default/xbmc, start Kodi again and look into logfile if some more messages come after
load settings...
And, this
Code:
493.122392] kworker/u2:1: page allocation stalls for 12680ms, order:0, mode:0x1400840(GFP_NOFS|__GFP_NOFAIL), nodemask=(null)
[ 493.122451] CPU: 0 PID: 76 Comm: kworker/u2:1 Tainted: G C 4.14.58+ #1
[ 493.122458] Hardware name: BCM2835
[ 493.122486] Workqueue: btrfs-endio-write btrfs_endio_write_helper
[ 493.122538] [<c0016920>] (unwind_backtrace) from [<c00141a0>] (show_stack+0x20/0x24)
[ 493.122569] [<c00141a0>] (show_stack) from [<c07de694>] (dump_stack+0x20/0x28)
[ 493.122599] [<c07de694>] (dump_stack) from [<c0118b2c>] (warn_alloc+0xb8/0x17c)
does not look nice in dmesg, please keep an eye on dmesg if that appears always after boot
I was updating and rebooting my Pi1 one hour ago, and that does not appear here
(30th Jul, 2018 04:50 AM)Nachteule Wrote: [ -> ]Yes, indeed. Never seen such a small log file. And no error there, very strange.
Maybe enabling DEBUG messages brings some light into the dark
Please add
to file /etc/default/xbmc, start Kodi again and look into logfile if some more messages come after load settings...
And, this
.......
does not look nice in dmesg, please keep an eye on dmesg if that appears always after boot
I was updating and rebooting my Pi1 one hour ago, and that does not appear here
Ok, done that, also ran Badblocks with the following output (i have no idea if it helps but...)
Code:
badblocks -v -s /dev/mmcblk0p2
Checking blocks 0 to 7440383
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
Reboot now command now just "shutdowns" the pi (the SDCARD LED is not blinking so i assume is off... but it can be crashed...) (also btw yesterday before i ran the update Kodi and everything else were running fine :/ )
So new Dmesg file
Here
New xbmc.log:
Code:
1159 (process ID) old priority 0, new priority 3
1232 (process ID) old priority 0, new priority 3
start: Job failed to start
xbmc stop/post-start, process 1208
post-start process 1209
1160 (process ID) old priority 0, new priority 3
1236 (process ID) old priority 0, new priority 3
start: Job failed to start
xbmc stop/post-start, process 1209
post-start process 1210
New Kodi.log
Here
All other OS functions appear to be working... I do not have anything else installed on this Pi besides vanilla Xbian and the updates.
Hmmm, your system seems incredible slow
20:34:19.453 161.818741 T:2985646592 NOTICE: load settings...
Code:
161.818741 is the uptime, mine system uptime at the same place is 87.689980 seconds
So, the question is, why is your system sooooo sloooooooowww
It seems that Kodi starts so slow, that startup watchdog (2mins) is killing Kodi before Kodi can tell system that I'm up
Can you try revert kernel from 4.14 to 4.9 (I suppose you ran .4.9 before) to see if that makes a difference
And/or, can you comment out dtoverlay=gpio-ir... in /boot/config.txt if you do not need lirc
(30th Jul, 2018 06:12 AM)Nachteule Wrote: [ -> ]It seems that Kodi starts so slow, that startup watchdog (2mins) is killing Kodi before Kodi can tell system that I'm up
Can you try revert kernel from 4.14 to 4.9 (I suppose you ran .4.9 before) to see if that makes a difference
And/or, can you comment out dtoverlay=gpio-ir... in /boot/config.txt if you do not need lirc
Can you help me reverting? I have no idea how to do that :/
Also thanks for the Lirc tip. I don't use any IR hardware.
(30th Jul, 2018 06:12 AM)Nachteule Wrote: [ -> ]It seems that Kodi starts so slow, that startup watchdog (2mins) is killing Kodi before Kodi can tell system that I'm up
Can you try revert kernel from 4.14 to 4.9 (I suppose you ran .4.9 before) to see if that makes a difference
And/or, can you comment out dtoverlay=gpio-ir... in /boot/config.txt if you do not need lirc
Also just found out that i have now 2 boot folders (???)... one /boot and the other /boot.new created today... is this expected?
Code:
sudo apt-cache policy xbian-package-kernel
gives you a list of available kernel packages
Code:
sudo apt-get install xbian-package-kernel="version you want"
installs desired kernel version
(30th Jul, 2018 06:20 AM)Nachteule Wrote: [ -> ]
Code:
sudo apt-cache policy xbian-package-kernel
gives you a list of available kernel packages
Code:
sudo apt-get install xbian-package-kernel="version you want"
installs desired kernel version
Thanks you
About the /boot.new folder... is that expected? This folder contains only:
