Crash on new install

Help and Support
1

Hi all,

Previously I was running RASPBMC on RPi B+ v1.2, had some free time over xmas so figured it was time to upgrade…

I wiped the SD card and did a new install using qt_host_installer from OS-X. I selected English, Raspberry Pi, 2015-11-1 version, and WiFi credentials.

SD card booted OK, but got a sad face at startup.

Logging in via SSH, I can see kodi failing with exit code 132

After installing gdb I see SIGILL during startup.

I did “apt-get update; apt-get upgrade” to pull down the latest and greatest, still no luck.

Below is the crash log, I’ve also shown the disassembly at the end.

Any idea what happened here? I’m not familiar with ARM opcodes, so unsure what is going on. My hunch is that it’s trying to use arm7 opcodes on the arm6 RPi-1 but surely someone else would have noticed that before me.

thanks.

############## Kodi CRASH LOG ###############

################ SYSTEM INFO ################
 Date: Mon Dec 28 02:31:16 UTC 2015
 Kodi Options: 
 Arch: armv6l
 Kernel: Linux 4.3.0-10-osmc #1 PREEMPT Sun Nov 29 17:03:54 UTC 2015
 Release: OSMC December 2015
############## END SYSTEM INFO ##############

############### STACK TRACE #################
=====>  Core file: /home/osmc/core (2015-12-28 02:31:16.690087353 +0000)
        =========================================
[New LWP 1409]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `/usr/lib/kodi/kodi.bin'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0x00459ea0 in CGUIListItem::CGUIListItem() ()

Thread 1 (Thread 0xb4479230 (LWP 1409)):
#0  0x00459ea0 in CGUIListItem::CGUIListItem() ()
#1  0x00a63788 in CFileItem::CFileItem() ()
#2  0x00a2c584 in CApplication::CApplication() ()
#3  0x0037ef58 in xbmcutil::GlobalsSingleton::getInstance() ()
#4  0x00318134 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
############# END STACK TRACE ###############

################# LOG FILE ##################

Logfile not found in the usual place.
Please attach it seperately.
Use pastebin.com or similar for forums or IRC.

############### END LOG FILE ################

############ END Kodi CRASH LOG #############


Core was generated by `/usr/lib/kodi/kodi.bin'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0x00459ea0 in CGUIListItem::CGUIListItem() ()
(gdb) disass
Dump of assembler code for function _ZN12CGUIListItemC2Ev:
   0x00459e98 <+0>:	svcls	0x00bd502d
   0x00459e9c <+4>:	svcpl	0x00d569dc
=> 0x00459ea0 <+8>:	orrsvc	r9, pc, #252	; 0xfc
   0x00459ea4 <+12>:	ldmdblt	r5, {r0, r2, r3, r5, r7, r9, r12, sp, pc}
   0x00459ea8 <+16>:	svccs	0x00d36d56
   0x00459eac <+20>:	ldrbpl	sp, [pc, #203]!	; 0x459f7f
2

Provide full logs via grab-logs -A and post the URL

3

Here’s the link, thanks.

http://paste.osmc.io/afesosihuc

4

Nothing obvious wrong in the Log file (other that Kodi is not being started).
Assuming your SD card is a quality card and your power supply also working fine?
What does a reinstall of mediacenter gives you?

sudo apt-get remove rbp1-mediacenter-osmc
sudo apt-get install rbp1-mediacenter-osmc

5

Thanks, that fixed it.

Power supply is a 2 amp, it’s been rock solid up to now so I doubt that’s the issue.
The flash card is new, but it’s a genuine Kingston 8GB so should be reliable too.

Very strange…

6

That’s really odd. Maybe you want to try another fresh install with the installer to avoid that maybe any other packages are corrupted two.

7

Installing to a different SD via NOOBS it worked fine. I will go back to the OS-X installer tomorrow and try to see if I can reproduce the failure using that method again.

8

Check the image you downloaded has the same md5sum as shown on the blog

9

md5sum of the image on OS-X was correct

I tried two more SD installs this morning from the same image, but I could not reproduce the failure. Very strange, oh well its working now. Thanks.

10

Just reading around the other threads, as I am using a Kingston SD maybe this is a side effect of the SDhost changes. I’ve just ordered one of your pre-loaded 16G cards to replace it.

11

The sdhost driver was only made the default in the December update and there are no December disk images yet so you were installing the November version of OSMC - therefore unrelated.

It sounds to me like the sdcard is a bit iffy and some corruption occurred during the install. I am not a fan of Kingston cards…

SIGILL is illegal instruction so assuming you weren’t trying to run armv7 code on the armv6 processor it would almost certainly be random corruption of kodi.bin (or an imported .so) generating invalid instructions.

12

Hi,
I have the same problem : having just upgraded to the latest version of "December " , KODI crash constantly .
My logs are : http://paste.osmc.io/imitojinir

Before updating OSMC to latest version there was no problem .

I tried with the commands
sudo apt-get remove rbp1-mediacenter-osmc sudo apt-get install rbp1-mediacenter-osmc
but the problem has not been solved

13

Please define “crash”. Do you mean a blue screen with a sad face ? Or does it spontaneously reboot ?

Also, your overclock settings are rather excessive to say the least:

force_turbo=1
over_voltage_sdram=4
over_voltage=8
core_freq=550
initial_turbo=0
sdram_freq=600
arm_freq=1100

Please comment out all your custom overclock lines and see if your system is then stable.

14

it spontaneously reboot.

ok, I removed “force_turbo=1” and now works.

15

Force turbo only forces it to always run at the clock frequencies you have specified even when the CPU is idle.

However when the CPU is busy it will go back to your excessively high overclock settings and may still crash.

I would drop your overclock frequencies as well, they are all too high to be stable.

16

running that high in a rpi1 is just reckless

1 Like