update [Solved] White Cube eOS 2.5 Upgrade: development status

Know absolutely nothing about Linux, but could this help?

https://unix.stackexchange.com/questions/427241/what-might-cause-a-single-rcu-sched-detected-stall-on-cpu-warning-in-syslog

Could this help with the error

"rcu_sched self-detected stall on CPU armbian"

https://www.kernel.org/doc/Documentation/RCU/stallwarn.txt

or with that

https://forum.armbian.com/topic/9331-pine64-on-41913-sunxi64-rcu_sched-self-detected-stall-on-cpu/

"The problem is solved by locking the frequency scaling. 

# WARNING: this file will be replaced on board support package (linux-root-...) upgrade
ENABLE=true
MIN_SPEED=120000
MAX_SPEED=1400000
#MAX_SPEED=500000
GOVERNOR=conservative
"

regards Sven

@calimero THX!

@bpr PLS check post above...

@random @bpr @benne

I could verify the issue with downloading much data, the white cube hangs/crashes and I had many issues in my network 🙂 Rebooting and the game starts again.

Now I've implemented the "frequency scaling lock" and my white cube is running 2 days without any issues...    

regards Sven

@calimero @all We have taken a different approach (core issue rather seams RAM frequency and board version depended) and we are currently pre-alpha testing this approach. We hope to broaden the test among the active eBlocker supporters over the weekend.

If this proves to be stable, public beta might come next week, but this is very optimistic...

@calimero Try pumping massive data >100 GB thru your freq locked eBlocker. Under normal circumstances my eBlocker also worked fine for over a week but stressing it shows the issue (usually within the first 20GB download). BTW: If you‘ve upgraded within the past two days anew - chances are high you’ve already caught a new pre-alpha from @bpr s internal tests... Version number shown has not yet been increased - but it‘s all new... 😊 😉 

Hi @calimero,

on the latest test image with Linux kernel 5.7.15 the default settings are:

# cat /etc/default/cpufrequtils 
ENABLE=true
MIN_SPEED=480000
MAX_SPEED=1400000
GOVERNOR=ondemand

Could you post your new settings?

Thanks!

@bpr

ENABLE=true
MIN_SPEED=912000
MAX_SPEED=1200000
GOVERNOR=ondemand

regards Sven

@calimero, @benne

curl -O  http://ftp.de.debian.org/debian/pool/main/m/memtester/memtester_4.3.0-4+b1_armhf.deb 
dpkg -i memtester_4.3.0-4+b1_armhf.deb

Now open four SSH shells and in each shell run the memtester on a different CPU core:

taskset -c 0 memtester 10M      # shell 1
taskset -c 1 memtester 10M      # shell 2
taskset -c 2 memtester 10M      # shell 3
taskset -c 3 memtester 10M      # shell 4

Most of my test boards could handle this, but on one board there were errors:

• Core 0 and 1 show no errors at all
• Core 2 shows up to 10 errors per loop
• Core 3 shows up to 3 errors per loop

@bpr @benne

I'm actually running the test with armbian sd 

Linux bananapim2plus 5.7.15-sunxi #20.08 SMP Sun Aug 16 23:54:33 CEST 2020 armv7l armv7l armv7l GNU/Linux

And I am not running in errors...

# cat /etc/default/cpufrequtils 
ENABLE=true
MIN_SPEED=480000
MAX_SPEED=1400000
GOVERNOR=ondemand

I will also tests the update with the "new" image and report back

cheers Sven

@calimero Well, @bpr has tested 8 boards (all similar serial range) and they worked fine with 1.4 Ghz armbian defaut.

But I have a board that shows the issue discussed above, if over 1.2 Ghz. Especially when downloading.

So I guess "overclocking" is OK for some boards but not all 😉 

As it's about stability for all boards ("white cubes") we have to play nicely at 1.2 and hope this works out for everyone...

@all We are currently alpha testing eOS 2.5.5 which hopefully fixes the issues discussed above. If everything goes well, we'll start public beta testing mid/end next week.

Keep fingers crossed 😉 

Beta test for eOS 2.5.x will start tomorrow, Friday 9/11. Please signup to the newsletter if you want to be the first who knows 😉 

Bugs are collected here

This thread will be updated until 2.5 is final.

Please find the upgrade instructions here: German /English 

Hello,

at the moment I use 2.5.3 (Beta) für the M2+. 

I tried with the URL Upgrade :3000/settings/#!/upgrade  but nothings happens (I only go to device list).

I searched for the nes Image but only found 2.5.2

Can you help to upgrade to 2.5.4 (beta) ?

Thank you

Regards

  Thorsten

@guny74 Please read the instructions (and thread subject) carefully. The current beta is for original white cubes only. They boot from eMMC, not from SD 🤔

Once everything is stable, we'll supply an update and/or a new SD image for M2+ board users.

THX!

Hello,

ohh, sorry missunderstanding from my site. I thought that the hardware base od the white cube would be a m2+. 

So I will wait and hope my problems will be solved in the next version for the m2+.

Regards

Posted by: @guny74

my problems will be solved

It's fine to share the issues you are experiencing to make sure it's on our list 😉 

The major changes are linux core updates (kernel, libs, configs) but the eBlocker core is mostly untouched. 

As a brief update: Beta test is running all stable. We are wrapping things up already. Update is due within October for sure. We‘ll inform by newsletter asap.

eOS 2.5 is final for all supported devices. YEAH!

We'll inform tomorrow by newsletter how to upgrade.

THX!

Hello, I did the update. Looks great so far.

But now I cannot scroll down in the list of VPN providers anymore. It jumps to the first entry all the time. It is fine when I choose the VPN via dashboard on each device. Only via eBlocker settings seams to be a problem.

@mcmoin THX for the good feedback. 😀 😎 

Did you clear the bowser cache? 

If issue persists please state eBlocker device, OS, browser etc. as well as how many VPN connections are configured, so we can reproduce it.

THX!

I tried different browsers and devices, iOS as well and deleted the cache. It did not solve the issue. I had round about 20 VPN connections configured. Meanwhile I deleted all except four and there is no need for scrolling anymore... The issue occurs when you add more than four configurations.

eBlockerOS 2.5 is now available.

Please post 2.5 bugs in the above linked thread.

This topic is closed.