Gluon v2020.1 Auffälligkeiten

Jason · 22. Mai 2020 um 10:19

Update:
Github-Issue #2029 aufgenommen: fastd occasionally segfaults in Gluon 2020.1.x

github.com/freifunk-gluon/gluon

fastd occasionally segfaults in Gluon 2020.1.x

opened 01:39AM - 22 May 20 UTC

closed 08:56PM - 27 May 20 UTC

kpanic23

0. type: bug 9. meta: upstream issue 0. type: regression 1. severity: blocker

### Bug report **What is the problem?** fastd crashes with segfault, causing the node to lose gateway connection. ``` kern.info kernel: [80946.000734] fastd[5014]: segfault at 10 ip 00007f3c229823e9 sp 00007ffd2ce68f60 error 6 in libc.so[7f3c2297f000+49000] ```  **What is the expected behaviour?** - How do you think it should work instead? fastd running without crashing :o) - Did it work like that before? Yes, up until 2019.1.2. **Gluon Version:** 2020.1.2  **Site Configuration:** https://github.com/ff3l/site-ff3l  **Custom patches:** none

rotanid · 25. Mai 2020 um 23:59

github.com/freifunk-gluon/gluon

significantly increased memory usage after upgrade to Gluon v2020.1.x

opened 10:41PM - 25 May 20 UTC

closed 05:40PM - 28 May 20 UTC

rotanid

0. type: bug 0. type: regression 1. severity: blocker

After updating from v2019.1.2 to v2020.1.2 memory usage increased. The increase… in our network is from average ~60% to ~70% on an idle node and at least 5% more on an active node. (with 32M memory) On devices with only 32M memory, this leads to frequent reboots. On devices with more memory, the increase can mostly also be seen but is not problematic. Our firmware for these devices did not change in other ways with this Gluon version bump which could affect the memory usage. please find attached the memory graphs of 4 32M devices and 2 64M devices before and after the firmware upgrade. ![memory_v202012_18a6f7c5cdb6_841v11](https://user-images.githubusercontent.com/654617/82846449-3612ed00-9ee9-11ea-8bde-59b86797d31a.png) ![memory_v202012_18a6f7c5c3bc_841v11](https://user-images.githubusercontent.com/654617/82846452-37441a00-9ee9-11ea-99a5-ebefb10a9e55.png) ![memory_v202012_18a6f7c5aaec_841v11](https://user-images.githubusercontent.com/654617/82846455-37441a00-9ee9-11ea-9e54-c022370cbd5a.png) ![memory_v202012_60e3275773ac_841v9](https://user-images.githubusercontent.com/654617/82846456-37dcb080-9ee9-11ea-8e92-f3a7cd5ad9a7.png) ![memory_v202012_ec086ba4d066_1043v3](https://user-images.githubusercontent.com/654617/82846451-36ab8380-9ee9-11ea-87f4-22c17e17d294.png) ![memory_v202012_18d6c75152c2_1043v4](https://user-images.githubusercontent.com/654617/82846453-37441a00-9ee9-11ea-8b07-0883873a7110.png) as far as i know, others also observed the issues as reported on the Gluon IRC channel for weeks.

das hat oben auch schon jemand aufgenommen

Jason · 31. Mai 2020 um 23:20

Update:
OpenWrt-Commit aufgenommen:

Der Commit wird in Gluon v2020.1.3 enthalten sein.