• 1
  • 11
  • 12
  • 13(current)
  • 14
  • 15
  • 86
v19 LibreELEC Testbuilds for RaspberryPi (Kodi 19.0)
Regarding memory consumption since #0530, nobody has answered this:
(2019-06-07, 23:04)Milhouse Wrote: What add-ons do you have installed? Can you test with a "clean" .kodi (ie. without addons)?

(2019-06-08, 20:46)germa18 Wrote: can you do a build #0608 with no megabump PR? i will be able to check if it's the problem like i think so.

There's not much else in #0530 other than the package bump, so #0529 is a good enough test without the package bump.

(2019-06-08, 20:46)germa18 Wrote: I'm on RBPI3, when i launch your command "bcmstat.sh" i don't have all the details with mem free  / used

bcmstat.sh xgpd10

Clearly this memory issue is not affecting everybody, so at this point I have to conclude it is specific to your environment - something else you have installed or enabled that is not default.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Hi Millhouse! Thank you for your great work.
I've to report a problem: Since #0606 wifi doesn't connect automatically and in #0607 it doesn't work anymore and leads to a shutdown when trying to connect manually.
#0605 works fine.
Tested on RPI3B (no log atm, sorry)
(2019-06-09, 20:38)surfnturf Wrote: Millhouse

Sorry, typo Milhouse ;-)
(2019-06-09, 20:38)surfnturf Wrote: I've to report a problem: Since #0606 wifi doesn't connect automatically and in #0607 it doesn't work anymore and leads to a shutdown when trying to connect manually.
#0605 works fine.
Tested on RPI3B (no log atm, sorry)

What wifi are you using - the built-in RPi3B WiFi or a USB WiFi dongle? Can you provide the output of [inline]journalctl -a | pastebinit[/url] from #0605?

What do you mean by "shutdown" - you mean the device powers off? Or Kodi crashes? Or...?

Fortunately there's only one change in #0606, which should not have made any difference to RPi (theoretically...).

In #0607 the only LibreELEC OS-specific change is the bump for curl-7.65.1.

If Kodi is crashing then a Kodi crash log (uploaded from LE Settings addon) could be useful.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2019-06-09, 22:51)Milhouse Wrote:
(2019-06-09, 20:38)surfnturf Wrote: I've to report a problem: Since #0606 wifi doesn't connect automatically and in #0607 it doesn't work anymore and leads to a shutdown when trying to connect manually.
#0605 works fine.
Tested on RPI3B (no log atm, sorry)

What wifi are you using - the built-in RPi3B WiFi or a USB WiFi dongle? Can you provide the output of [inline]journalctl -a | pastebinit[/url] from #0605?

What do you mean by "shutdown" - you mean the device powers off? Or Kodi crashes? Or...?

Fortunately there's only one change in #0606, which should not have made any difference to RPi (theoretically...).

In #0607 the only LibreELEC OS-specific change is the bump for curl-7.65.1.

If Kodi is crashing then a Kodi crash log (uploaded from LE Settings addon) could be useful. 
Hi, thanks for your fast reply. I'm sorry for not providing enough details,
- Using builtin wifi
- Kodi does crash

I downgraded to #605, hence its late in my country, I'll test it tomorrow and try posting a log.
New LibreELEC.tv Matrix build #0609: RPi / RPi2
(Supercedes previous build)

SHA256 Checksum: b9d2e17f8f894b1ad3396b33ddc844bcced46f15e18924cc4844b82c585f53c1 (RPi)
SHA256 Checksum: 677b02c87134c15aebc5b5b08fdc35f48a5ed3eb33a49edec0f881989ada2b1a (RPi2)

text:
# uname -a
Linux rpi512 5.1.7 #1 Sun Jun 9 22:09:33 BST 2019 armv6l GNU/Linux

# vcgencmd version
May 28 2019 16:24:29
Copyright © 2012 Broadcom
version f37252430f9659d04032b6e0123d7950e3f9d92c (clean) (release) (start_x)

# lsb_release
LibreELEC (Milhouse): devel-20190609220858-#0609-g41c5cd2 [Build #0609]

# Kodi version
Kodi (19.0-ALPHA1 Git:312fe31). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (41c5cd2, changelog) and tip of XBMC master (312fe31, changelog) with the following modifications: Build Highlights:
  1. cleanup: Remove code related to kernels 3.14 and 3.10 on WiFi drivers.
Build Details:
  1. LibreELEC.tv:
    • Allwinner: Various updates (PR:3545, 6 commits, 31 files changed)
    • cleanup: Remove code related to kernels 3.14 and 3.10 on WiFi drivers. (PR:3539, 2 commits, 4 files changed)
  2. XBMC:
    • [iOS] remove some legacy code (PR:16017, 5 commits, 8 files changed)
    • [PVR] rework includes (PR:16248, 3 commits, 122 files changed)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Updated: [env] PR:3540 (perma): linux (RPi/Generic/Allwinner): update to linux-5.1.8
    • Added: [env] PR:3548 (perma): config/functions: ln -sf is not always thread safe
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2019-06-09, 23:08)surfnturf Wrote: Hi, thanks for your fast reply. I'm sorry for not providing enough details,
- Using builtin wifi
- Kodi does crash

I downgraded to #605, hence its late in my country, I'll test it tomorrow and try posting a log.

I've dug out my own RPi3B and WiFi (2.4GHz) is connecting normally with my own ISP router when booting #0607.

I think I will need to see the #0607 hardware logs from your device, in order to try and understand the failures - if you can, allow the device to boot into #0607 (and for WiFi to try and connect), then plug in a wired ethernet cable and download the latest Zip archive from the Logfiles Samba share, and then upload this file to Dropbox/Googledrive and paste the link.

At the moment however I don't see anything obvious in #0606/#0607 that would be the cause of these problems.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2019-06-09, 12:31)Milhouse Wrote: garding memory consumption since #0530, nobody has answered this:
(2019-06-07, 23:04)Milhouse Wrote: What add-ons do you have installed? Can you test with a "clean" .kodi (ie. without addons)?
(2019-06-08, 20:46)germa18 Wrote: can you do a build #0608 with no megabump PR? i will be able to check if it's the problem like i think so.

There's not much else in #0530 other than the package bump, so #0529 is a good enough test without the package bump.
(2019-06-08, 20:46)germa18 Wrote: I'm on RBPI3, when i launch your command "bcmstat.sh" i don't have all the details with mem free  / used
bcmstat.sh xgpd10

Clearly this memory issue is not affecting everybody, so at this point I have to conclude it is specific to your environment - something else you have installed or enabled that is not default.           
Ok, i made some extra test and it seems that the GUI in kodi is not displaying the good memory usage value

In #0529 build :
Image
Image

In Kodi GUI (system information), memory used reported is ~28/30%, so it's correct

----------
Starting the #0530 build to the latest #0609 build :

ImageImageImage

You see that with the command "bcmstat.sh xgpd10"  the memory free/ mem used is OK like before (like in #0529)
The one thing change, is that the report with the "top" command was in KiB before and now we have MiB but i'm not sure if it's a big change here

But the biggest problem is that in the GUI you see the system memory usage at 66% while with bcmstat it show only 29% used, it's likely that the GUI takes the free memory percentage and show it like memory used, very weird ...
(2019-06-10, 14:45)germa18 Wrote: But the biggest problem is that in the GUI you see the system memory usage at 66% while with bcmstat it show only 29% used, it's likely that the GUI takes the free memory percentage and show it like memory used, very weird ...

Thanks! I can see the same issue with the GUI, so yes this seems to be a Kodi issue with the way it interprets the output from the latest procps-ng. I'll have a dig around in procps-ng and Kodi to see what has changed.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
BTW that latest top supports the -E command line option to select memory scaling - the default is -Em (for Megabytes) but -Ek would restore the pre-#0530 behaviour showing memory in Kilobytes.

It won't fix the Kodi GUI though, that's under investigation...
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
The GUI memory information issue is not due to the package bump - those changes (top memory scaling) are unrelated and an unfortunate coincidence as it landed at the same time as the following Kodi change:
(2019-05-31, 00:01)Milhouse Wrote: Build Details:
  1. XBMC:
    • PlatformDefs.h remove _MEMORYSTATUSEX struct (PR:16181, 1 commit, 27 files changed)

This seems to be misreporting free memory - it's being investigated. Thanks for reporting!
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2019-06-10, 00:03)Milhouse Wrote:
(2019-06-09, 23:08)surfnturf Wrote: Hi, thanks for your fast reply. I'm sorry for not providing enough details,
- Using builtin wifi
- Kodi does crash

I downgraded to #605, hence its late in my country, I'll test it tomorrow and try posting a log.

I've dug out my own RPi3B and WiFi (2.4GHz) is connecting normally with my own ISP router when booting #0607.

I think I will need to see the #0607 hardware logs from your device, in order to try and understand the failures - if you can, allow the device to boot into #0607 (and for WiFi to try and connect), then plug in a wired ethernet cable and download the latest Zip archive from the Logfiles Samba share, and then upload this file to Dropbox/Googledrive and paste the link.

At the moment however I don't see anything obvious in #0606/#0607 that would be the cause of these problems. 
Hi! Thank you for your reply and for testing. I tested #609 and the problem has solved itself, so no further intervention necessary. I'll post a log immediately if this problem might reoccure in newer versions.
Using latest versions I detect problems using external wifi USB.
Occurs sporadically.

Logs: http://ix.io/1LqX

Seems a kernel problem:
Quote:Jun 10 21:27:36 LibreELEC kernel: ------------[ cut here ]------------
Jun 10 21:27:36 LibreELEC kernel: WARNING: CPU: 3 PID: 209 at net/wireless/sme.c:756 __cfg80211_connect_result+0x42c/0x4b8 [cfg80211]
Jun 10 21:27:36 LibreELEC kernel: Modules linked in: ipt_MASQUERADE nf_conntrack_netlink nfnetlink rfcomm iptable_nat xt_addrtype hci_uart btbcm serdev iptable_filter bluetooth ip_tables ecdh_generic xt_conntrack x_tables nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc overlay rc_dib0700_rc5 mt2060 dib7000p fuse dvb_usb_dib0700 dib3000mc dib7000m dib0090 dib0070 dvb_usb snd_bcm2835© rc_core dibx000_common snd_pcm dvb_core brcmfmac brcmutil snd_timer snd bcm2835_gpiomem 8812au(O) cfg80211 fixed rfkill
Jun 10 21:27:36 LibreELEC kernel: CPU: 3 PID: 209 Comm: kworker/u8:2 Tainted: G C O 5.1.7 #1
Jun 10 21:27:36 LibreELEC kernel: Hardware name: BCM2835
Jun 10 21:27:36 LibreELEC kernel: Workqueue: cfg80211 cfg80211_event_work [cfg80211]
Jun 10 21:27:36 LibreELEC kernel: Backtrace:
Jun 10 21:27:36 LibreELEC kernel: [<8010e9ac>] (dump_backtrace) from [<8010ed10>] (show_stack+0x20/0x24)
Jun 10 21:27:36 LibreELEC kernel: r7:ffffffff r6:00000000 r5:600e0013 r4:812911d8
Jun 10 21:27:36 LibreELEC kernel: [<8010ecf0>] (show_stack) from [<8096563c>] (dump_stack+0xcc/0x110)
Jun 10 21:27:36 LibreELEC kernel: [<80965570>] (dump_stack) from [<80121bd4>] (__warn.part.3+0xcc/0xe8)
Jun 10 21:27:36 LibreELEC kernel: r10:00000100 r9:00000200 r8:ab437e54 r7:000002f4 r6:00000009 r5:00000000
Jun 10 21:27:36 LibreELEC kernel: r4:00000000 r3:95605ed5
Jun 10 21:27:36 LibreELEC kernel: [<80121b08>] (__warn.part.3) from [<80121d70>] (warn_slowpath_null+0x54/0x5c)
Jun 10 21:27:36 LibreELEC kernel: r7:81208c88 r6:7f0563f4 r5:000002f4 r4:7f07e488
Jun 10 21:27:36 LibreELEC kernel: [<80121d1c>] (warn_slowpath_null) from [<7f0563f4>] (__cfg80211_connect_result+0x42c/0x4b8 [cfg80211])
Jun 10 21:27:36 LibreELEC kernel: r6:00000000 r5:88d1960c r4:ab4c0c00
Jun 10 21:27:36 LibreELEC kernel: [<7f055fc8>] (__cfg80211_connect_result [cfg80211]) from [<7f0247c4>] (cfg80211_process_wdev_events+0x104/0x160 [cfg80211])
Jun 10 21:27:36 LibreELEC kernel: r8:ab4c0c8c r7:ab4c0c24 r6:ab4c0c94 r5:ab4c0c00 r4:88d19600
Jun 10 21:27:36 LibreELEC kernel: [<7f0246c0>] (cfg80211_process_wdev_events [cfg80211]) from [<7f024860>] (cfg80211_process_rdev_events+0x40/0x98 [cfg80211])
Jun 10 21:27:36 LibreELEC kernel: r10:00000000 r9:ab7f20e8 r8:00000000 r7:ad32a600 r6:ad844400 r5:ab7f2430
Jun 10 21:27:36 LibreELEC kernel: r4:ab4c0c00
Jun 10 21:27:36 LibreELEC kernel: [<7f024820>] (cfg80211_process_rdev_events [cfg80211]) from [<7f01e2d8>] (cfg80211_event_work+0x24/0x2c [cfg80211])
Jun 10 21:27:36 LibreELEC kernel: r5:ace18e80 r4:ab7f20e4
Jun 10 21:27:36 LibreELEC kernel: [<7f01e2b4>] (cfg80211_event_work [cfg80211]) from [<8013d9e4>] (process_one_work+0x23c/0x51c)
Jun 10 21:27:36 LibreELEC kernel: r5:ace18e80 r4:ab7f20e4
Jun 10 21:27:36 LibreELEC kernel: [<8013d7a8>] (process_one_work) from [<8013ea8c>] (worker_thread+0x60/0x5b8)
Jun 10 21:27:36 LibreELEC kernel: r10:ad844400 r9:81203d00 r8:ad844418 r7:00000088 r6:ad844400 r5:ace18e94
Jun 10 21:27:36 LibreELEC kernel: r4:ace18e80
Jun 10 21:27:36 LibreELEC kernel: [<8013ea2c>] (worker_thread) from [<80144430>] (kthread+0x168/0x170)
Jun 10 21:27:36 LibreELEC kernel: r10:acc09e74 r9:8013ea2c r8:ace18e80 r7:ab436000 r6:00000000 r5:ac810940
Jun 10 21:27:36 LibreELEC kernel: r4:ac810980
Jun 10 21:27:36 LibreELEC kernel: [<801442c8>] (kthread) from [<801010ac>] (ret_from_fork+0x14/0x28)
Jun 10 21:27:36 LibreELEC kernel: Exception stack(0xab437fb0 to 0xab437ff8)
Jun 10 21:27:36 LibreELEC kernel: 7fa0: 00000000 00000000 00000000 00000000
Jun 10 21:27:36 LibreELEC kernel: 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jun 10 21:27:36 LibreELEC kernel: 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
Jun 10 21:27:36 LibreELEC kernel: r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:801442c8
Jun 10 21:27:36 LibreELEC kernel: r4:ac810940
Jun 10 21:27:36 LibreELEC kernel: ---[ end trace e2c83fd2cb019908 ]---
Quote: 
(2019-06-10, 21:39)ezar Wrote: Using latest versions I detect problems using external wifi USB.
Occurs sporadically.

Do you know when this started, or can identify when it started? It could be a kernel bump (5.1.7, 5.1.5 etc.). There's going to be a new 5.1.8 kernel tonight.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
New LibreELEC.tv Matrix build #0610: RPi / RPi2
(Supercedes previous build)

SHA256 Checksum: 008c1d22a944c276d73a9806055180f06cae0dcfc5efb96ea8e5020b80ba5064 (RPi)
SHA256 Checksum: eeea6bfe491bb4f7c4d2ba0f1268fc8b3e76a613a2cb026101642f52abbadd61 (RPi2)

text:
# uname -a
Linux rpi512 5.1.8 #1 Mon Jun 10 22:08:58 BST 2019 armv6l GNU/Linux

# vcgencmd version
May 28 2019 16:24:29
Copyright © 2012 Broadcom
version f37252430f9659d04032b6e0123d7950e3f9d92c (clean) (release) (start_x)

# lsb_release
LibreELEC (Milhouse): devel-20190610220717-#0610-g9a3c66c [Build #0610]

# Kodi version
Kodi (19.0-ALPHA1 Git:3466dc5). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (9a3c66c, changelog) and tip of XBMC master (3466dc5, changelog) with the following modifications: Build Highlights:
  1. New 5.1.8 kernel
  2. procps-ng: free from busybox doesn't match top
  3. MemUtils: breakup into platform specific files
  4. Require OpenSSL 1.0.2 and manage thread ids consistently on all platforms.
Build Details:
  1. LibreELEC.tv:
    • xf86-video-nvidia: update to xf86-video-nvidia-430.14 (PR:3543, 1 commit, 2 files changed)
  2. XBMC:
    • Require OpenSSL 1.0.2 and manage thread ids consistently on all platforms. (PR:16249, 4 commits, 4 files changed)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Updated: [env] PR:3540 (perma): linux (RPi/Generic/Allwinner): update to linux-5.1.8
    • Added: [env] PR:3549 (perma): xf86-video-nvidia: update to xf86-video-nvidia-430.26
    • Added: [env] PR:3550 (perma): procps-ng: free from busybox doesn't match top
    • Added: [pkg] PR:16223 (perma): MemUtils: breakup into platform specific files
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
  • 1
  • 11
  • 12
  • 13(current)
  • 14
  • 15
  • 86

Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for RaspberryPi (Kodi 19.0)8