Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

Well, surprise surprise... 🙄

 

[  966.810634] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 5
[  966.846025] CPU: 5 PID: 12045 Comm: containerd-shim Tainted: PF          O 3.10.108 #42214
[  966.886387] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019
[  966.921287]  ffffffff814a2759 ffffffff814a16b1 0000000000000010 ffff880409b48d60
[  966.957651]  ffff880409b48cf8 0000000000000000 0000000000000005 0000000000000001
[  966.994528]  0000000000000005 ffffffff80000001 0000000000000030 ffff8803f4d2ec00
[  967.030689] Call Trace:
[  967.042701]  <NMI>  [<ffffffff814a2759>] ? dump_stack+0xc/0x15
[  967.070638]  [<ffffffff814a16b1>] ? panic+0xbb/0x1df
[  967.094351]  [<ffffffff810a9eb8>] ? watchdog_overflow_callback+0xa8/0xb0
[  967.127712]  [<ffffffff810db7d3>] ? __perf_event_overflow+0x93/0x230
[  967.159748]  [<ffffffff810da612>] ? perf_event_update_userpage+0x12/0xf0
[  967.193069]  [<ffffffff810152a4>] ? intel_pmu_handle_irq+0x1b4/0x340
[  967.224060]  [<ffffffff814a9d06>] ? perf_event_nmi_handler+0x26/0x40
[  967.256031]  [<ffffffff814a944e>] ? do_nmi+0xfe/0x440
[  967.280802]  [<ffffffff814a8a53>] ? end_repeat_nmi+0x1e/0x7e
[  967.309035]  <<EOE>> 
[  967.319069] Rebooting in 3 seconds.. 

 

Actually, this is worse than it was on 6.2.4 now. It's panicking as soon as I start a different container this time (a linked pair of librenms and mysql containers). I've a suspicion as to what may be consistent between these containers that's different to the containers that are not causing crashes....watch this space...

 

...

 

Oh, this is ridiculous: just loading the docker app in the web UI is throwing a kernel panic now 🙄

Edited by WiteWulf
Link to comment
Share on other sites

Installed 7.0.1 RC on an Asrock J3455B-ITX, baremetal, all GOOD ! Running PI-Hole in Docker, no kernel panic.

 

Compiled the module on Debian 11, no compile errors.

 

All went smooth, set the cpu governor on powersave.

 

How to I make the powersaver script run at boot?

 

/usr/local/etc/rc.d/S99Powersaving.sh

 

It seems that it reverts to performance when I reboot.

 

root@Apollo:/usr/local/etc/rc.d# ls -la S99Powersaving.sh
-rwxr-xr-x 1 root root 295 Sep  8 15:32 S99Powersaving.sh
 

 

Thanks

Edited by ct85msi
Link to comment
Share on other sites

Hello again.

I've got question: how can I add additional param to kernel. I want to pass intel_iommu=off.

Is user_config.json a good place for that?

 

edit: unfortunatelly my DS918+ hangs up after adding photos to Photo app and after starting face recognition (I guess).

Edited by abesus
Link to comment
Share on other sites

33 minutes ago, ct85msi said:

It seems that it reverts to performance when I reboot.

 

root@Apollo:/usr/local/etc/rc.d# ls -la S99Powersaving.sh
-rwxr-xr-x 1 root root 295 Sep  8 15:32 S99Powersaving.sh
 

 

Thanks

 

you can create a task from interface to do it every 10'. so you are sure it is done 😜

or you can do it with crontab.

Capture.JPG

 

and dont forget to set it with root user

 

root.thumb.JPG.92786bc3400e3638e0f54ebcb723ac23.JPG

Edited by titoum
Link to comment
Share on other sites

Il y a 2 heures, haydibe a dit :

Are you sure that you executed `sudo su - root` to become root before the vi line?

 

Instead you could use `sudo -i` to become root.

 

Refactored to by dynamic:

Anyrhing else to do prior creating the script is needed ? 

 

/usr/local/etc/rc.d/S99Powersaving.sh: line 3: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor: No such file or directory

 

Link to comment
Share on other sites



Hello again.
I've got question: how can I add additional param to kernel. I want to pass intel_iommu=off.
Is user_config.json a good place for that?
 
edit: unfortunatelly my DS918+ hangs up after adding photos to Photo app and after starting face recognition (I guess).


my DS3615xs in a docker was same with u. hangs up after adding photos to Photo app and after starting face recognition.


Tapatalk を使用して私の ELS-NX9 から送信

Link to comment
Share on other sites

2 hours ago, haydibe said:

Are you sure that you executed `sudo su - root` to become root before the vi line?

 

Instead you could use `sudo -i` to become root.

 

My my fault. I was trying to set conservative same as @WiteWulf but my system is not supporting such parameter - powersave works ok.

Thanks for all

Link to comment
Share on other sites

 

20 hours ago, sebg35 said:

Just tried with my Gen10 plus (with Xeon E-2224) and 918+ loader with 7.0.1

 

  • NIC : Only 2 detected (4 set in grub)
    • I use a LAG (802.3ad of 2 nic : Working)
  • Install : No issue at all : It asked for migrating my OLD disk (No production disk has been used)
  • CPU : My Xeon E-2224 is only shown as one core (Same issue has in 6.2.3 with 918+ -> Need 3617xs loader to have all 4 cores used)
  • Info Center : Working
  • Applications :
    • Synology Photo / Drive:
      • Face detection not working 
      • Unable to play a video under File station (Video was uploaded with the backup feature using Synology photo for Android; Not working also on 6.2.3)
      • The rest seems to work fine
    • Surveillance Station : Working with one camera added
    • Active Backup For business : Working well. (backup with esxi 7.0 is working)
    • Plex : Working
    • Docker : Not tested.
  • Face detection Log :

2021-09-07T18:56:23+02:00 NAS synofoto-face-extraction[13956]: json_utils.cpp:147 Failed to parse json file [/tmp/VideoStation/enabled]
2021-09-07T18:56:24+02:00 NAS synofoto-face-extraction[13956]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-09-07T18:56:24+02:00 NAS synofoto-face-extraction[13956]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
  • /proc/cpuinfo :

cat /proc/cpuinfo | grep 'processor\|name\|cores'
processor       : 0
model name      : Intel(R) Xeon(R) E-2224 CPU @ 3.40GHz
cpu cores       : 1


I revert to my 6.2.3 with 3617xs loader from June. waiting for 3617xs support.

 

How can you see the face detection log? 

 

Thanks.

Link to comment
Share on other sites

1 hour ago, abesus said:

My my fault. I was trying to set conservative same as @WiteWulf but my system is not supporting such parameter - powersave works ok.

Thanks for all

Since migrating my system to 7.0.1-RC1 today I've found that conservative also no longer works. I think it's a change in the kernel or drivers.

 

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors


The above command will show you what frequency scaling governors are available. On my system (Xeon E3-1265L V2 on a bromolow ds3615xs image), I only have the following options available:

powersave performance userspace

 

And this will show you what governor is currently in use:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

 

Have a poke around in /sys/devices/system/cpu/cpu0/cpufreq/, there's all sorts of useful info in there.

 

On my system, 'powersave' seems to lock the core at 1600MHz, 'performance' at 2500MHz and 'userspace' allows processes to set the frequency manually. There do not appear to be governors that dynamically scale CPU frequency with load. In the past these included 'on demand' and 'conservative'.

 

Edited by WiteWulf
Link to comment
Share on other sites

I think the performance governor it`s fine, I also have a real DS918+ and it has performance governor by default. The powersave governor doesn`t increase the cpu freq even with load, it sits at 800 MHz. I`m removing all the scripts and rules, default is better with performance. With performance governor, the cpu frequency is 1500 MHz.

Link to comment
Share on other sites

14 minutes ago, MastaG said:

any idea where I can get the patched kernel sources for linux-3.10.108 used in 7.0.1-42214 ?
the toolchain only contains the pre-compiled kernel headers, not the full source...

I have the same issue, tried to compile some modules with generic sources & synoconfig file for bromolow but compiled modules are useless - segmentation faults etc...

Link to comment
Share on other sites

For two days in a row i'm trying to fix my microserver G7 test system, which stopped booting the loader, until i found out that C1E was enable in the BIOS after i found that the ten years lithium battery was dead. I changed back C1E to disabled and now everything is working again with 7.0.1.  I will now continue working on the mptsas issues. 

 

Anyone had any luck with that ? 

Link to comment
Share on other sites

Check post from pocopico on page 41 on how to compile

 

Link to kernel sources

 

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/snapshot/linux-3.10.108.tar.gz

 

3 hours ago, MastaG said:

any idea where I can get the patched kernel sources for linux-3.10.108 used in 7.0.1-42214 ?
the toolchain only contains the pre-compiled kernel headers, not the full source...

 

2 hours ago, ghtester said:

I have the same issue, tried to compile some modules with generic sources & synoconfig file for bromolow but compiled modules are useless - segmentation faults etc...

 

Link to comment
Share on other sites

On 9/6/2021 at 4:34 PM, pocopico said:

 

Not very difficult .. 

 

In order to compile your modules for 3.10.108 download standard kernel sources :

 

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/snapshot/linux-3.10.108.tar.gz

 

or just clone latest stable and 

 

# git checkout v3.10.108

 

copy the .config from the bromolow/apollolake sources to the folder you have the kernel sources that you downloaded, make menuconfig and select the modules you want to compile and the end run make modules.

 

Pay attention to the module dependencies (run modinfo xxx.ko ) as you might need modules to be loaded before that. e.g. module tg3.ko (tigon) depends on libphy.ko, so you need to first load libphy.ko and then tg3.ko. Not all modules have dependencies, but some do.

 

 

Do you know what kernel version you need for compile modules for 918+ apollolake?

Link to comment
Share on other sites

1 hour ago, ressof said:

Do you know what kernel version you need for compile modules for 918+ apollolake?

well running 

 

DiskStation> uname -a
Linux DiskStation 4.4.180+ #42214 SMP Sat Aug 28 02:41:15 CST 2021 x86_64 GNU/Linux synology_apollolake_918+
DiskStation>

 

reports kernel version v4.4.180

Link to comment
Share on other sites

Just for testing purposes, It looks that it is possible to install 918+ 7.0.1 in vmware. Steps include linking the detected SATA loader to /dev/synoboot like that 

 

# ln -s /dev/sdXX       /dev/synoboot
# ln -s /dev/sdXX1      /dev/synoboot1
# ln -s /dev/sdXX2     /dev/synoboot2
# ln -s /dev/sdXX3      /dev/synoboot3

 

where sdXX is your loader vmdk disk whose disk name can be found running

 

# fdisk -l 

 

Once you have it installed there will be no need to fake it again as md raid devices are discovered and mounted during boot and are not related to the loader. Anyway you may relink using the same commands. 
 

*** edit : you need to relink after boot, I will do some more testing 

 

Again, wait for developers to release a final version before installing on your production systems.

 

 

Edited by pocopico
  • Like 1
Link to comment
Share on other sites

1 hour ago, djvas335 said:

Check post from pocopico on page 41 on how to compile

 

Link to kernel sources

 

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/snapshot/linux-3.10.108.tar.gz

 

 

 

Unfortunately this is a generic source which did not work for me. Synology has patched kernel sources and they usually publish them with a huge delay. At the usual location ( https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/ ) I could not find the 7.0.1 sources so far.

Link to comment
Share on other sites

9 minutes ago, ghtester said:

Unfortunately this is a generic source

It’s only for kernel module compilation. Kernel itself will not build as it relies on unreleased - from Synology - code.

 

kernel modules were built using the described process. Which modules are you looking to build maybe I can provide. 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...