168 replies to this topic

[A.A.]

I am now building an hybrid using kernel and kodi + tools recipes of OE-A in the OpenPLi image but getting the same sigbus error.

 

I have now to verify other buses:

- audio (there is only alsa but kodi config looks for sndio and pulseaudio as well)

- video (maybe I must really install libvugles ?? DESCRIPTION = "shared library for E2 animation")

 

The launcher itself differs a bit (/usr/bin/kodi) and the one in OpenPLi doesn't look at the hdd.

 

I'll spend a bit more work on it.

A.A.

[Erik Slagter]

Did you already use strace to check the signal always happens at the same location in the code?

[A.A.]

Erik,

yes, strace, valgrind, gdb.

It always goes crazy in libc_init/mips_start -> SIGBUS at unknow addresses.

 

Anyway I did some progress because adding dependencies on

glib-2.0 \
gstreamer1.0 \
gstreamer1.0-plugins-base \

 

i get now Segmentation Fault SIGSEGV

I'll work on it this weekend in the free-time, I'll check the platforms again

Cheers

A.A.

 

P.S. it's 1GB unstripped...

Edited by A.A., 18 September 2020 - 22:22.

[A.A.]

Erik,

 

here the strace of kodi in  OpenPLi and OpenSPA (working). The problem is in OpenPLi Gles_Init does not start.

I am even using the very same OE-A kernel but the rest is abit different so are the locale and timezone accesses.

What base-differences do other distros have? Maybe these dvb-proxy drivers need some kind of servers/configuration in userland?

 

I did not add yet bluetooth and pulseaudio because that would be a distro change and I have read in the sources these are kodi's optional configuration options.

Besides, apparently the same kodi recipe runs on other models so the runtime deps should be there.

 

Long read...

 

 

OpenPLi  https://pastebin.com/L9TtpDBM

 

OpenSPA https://pastebin.com/Fw3pichZ

 

A.A.

[Erik Slagter]

DVB proxy indeed is the glue between the drivers and userland.

[A.A.]

For the dvb-proxy drivers there is indeed another layer, the vuplus-platform.

 

I thought that with these BSP changes all necessary pieces are now in place to add dvbproxy to the machine features:

  https://tinyurl.com/yxmfh4ex

 

But as in my tedious posts above there is still something missing.

 

I've ruled out that the issue is not in:

- kernel (same sources)

- kodi recipe (98% the same)

- vuplus platform (fixed)

 

So it could be some module not loaded or some other OE-A initscript (creating devices, symlinks, daemons,...)

Or maybe there is still something about the private libs and these are not correctly linked, but these appear just fine in strace.

[Erik Slagter]

Can you make sure the bus error is not generated inside a system call (which is very unlikely but not impossible)? If it is, all bets are off, then it most likely is a driver bug. No mentionings in the dmesg I guess?

 

There exists a tool called ltrace, it's in OE but I don't think we build it currently. Also I am afraid you do need debug symbol version of the relevant libs, which we probably don't have.

 

Just brainstorming here...

[A.A.]

Heh, adding more deps transformed the sigbus in sigsegv...

 

Anyway I have maybe another hint:

 

OpenPLi:  getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=4*1024}) = 0

OpenSPA: getrlimit(RLIMIT_NOFILE, {rlim_cur=16*1024, rlim_max=16*1024}) = 0

[Erik Slagter]

If the limit isn't handled gracefully, yeah, possible. So I guess you could try settings the limits considerately higher, all of them, to start with.

[peti]

I tried again with the current dev on my Zgemma H7S and got the same issue. After I install Kodi, E2 is not starting:

OpenPLi Enigma2 crash log

crashdate=Thu Jan  1 01:00:43 1970
compiledate=Oct 28 2020
skin=Default Skin
sourcedate=2020-10-26
branch=develop
rev=0f2a96e
component=enigma2

kernelcmdline=root=/dev/mmcblk0p3 rootsubdir=linuxrootfs1 kernel=/dev/mmcblk0p2 rw rootwait h7_4.boxmode=1 brcm_cma=440M@328M brcm_cma=192M@768M console=ttyS0,115200
imageissue=openpli homebuild %h


[Avahi] avahi_timeout_new
[Avahi] avahi_watch_new(3 0x1)
[Avahi] avahi_timeout_update
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free
[Avahi] client state: 2
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free
[eInit] + (1) Background File Eraser
[eInit] + (5) Tuxtxt
[eInit] + (8) graphics acceleration manager
[bcm] /dev/fb0 No such file or directory
[eInit] + (9) GFBDC
[fb] /dev/fb0 No such file or directory
[fb] framebuffer /dev/fb0 not available
[gFBDC] no framebuffer available


dmesg

Any idea where to start? If I only uninstall enigma2-plugin-extensions-kodi and kodi packages it's still not starting. I have to uninstall everything with --autoremove

[WanWizard]

This doesn't seem Kodi related:

[fb] /dev/fb0 No such file or directory
[fb] framebuffer /dev/fb0 not available
[gFBDC] no framebuffer available

This means the drivers haven't loaded.

[peti]

this is always happening after I install Kodi. E2 starts only after I remove it with all its dependencies

[WanWizard]

Nothing in dmesg?

[peti]

Nothing in dmesg?

 

I cannot see anything unusual. 

Attached Files

•  dmesg.txt   15.38KB   5 downloads

[peti]

the kernel-module-cdc-acm-4.10.12 package is causing the issue which is a dependency of Kodi 18

[WanWizard]

Why would Kodi need a modem driver? Odd...

[ntj]

One humble question:

Following this thread and now RC Openpli 8.0 is out, i was hoping that KODI for MIPS (in my case VU+ DUO2) should be working but there are no KODI in plugin downloads.

Anyone want to comment on status on KODI for mips ?

 

Regards

[Erik Slagter]

More specific KODI on MIPS for VU+. It's not a generic thing made by OpenPLi if you were under that impression.

[ntj]

Yes, i am aware of the fact that KODI is not made by OpenPLi team.

 

In this thread it seams like some tests has been done to have it working on Zeus, hence the question.

I think there are many that will be happy if it would work and could be in the download section.

[A.A.]

Hello,

 

I am now back and I plan to restart the testings very soon.

I somehow suspect the issue could be fmt/libfmt: the funny thing is that I was using the same versions as latest OE-A then doing strace I discovered that both OpenSPA and OpenATV do not link with an external libfmt!

So the kodi recipes on github are not used for the current 4.4 releases? Strange...

 

I'll investigate

Cheers

A.A.

Edited by A.A., 1 December 2020 - 11:26.