RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

FWIW, this release (7.0.1-42218 with redpill-lkm 3474d9b) is very unstable for me. It's kernel panicking for Plex Media Server (which is essentially a big database) as well as my docker containers. I don't know if that's because of the move to 7.0.1-42218, or because I've also moved to 3474d9b again. I previously tried 3474d9b and found it very unstable on my system, so to went back to 021ed51, which crashed much less often.

 

I've disabled docker on my system now, but it's kernel panicking every few minutes as soon as Plex Media Server starts doing anything. Gonna have to try and build a 7.0.1-42218 image with that older redpill-lkm commit as this is completely unusable now.

Edited by WiteWulf
Link to post
Share on other sites
12 minutes ago, D.S said:

DS918+ 7.0.1-42218 is working good on my bare metal, but synology photo face recognition is still not working even with real SN & Mac

 

Are your SN and MAC address real DS918+ values ? or generated one ?

The SN and MAC must be real, and matching the running loader (DS918+ in your case).

 

what do you see in /var/log/messages and /var/log/synofoto.log ?

Edited by Orphée
Link to post
Share on other sites
55 minutes ago, WiteWulf said:

I've disabled docker on my system now, but it's kernel panicking every few minutes as soon as Plex Media Server starts doing anything. Gonna have to try and build a 7.0.1-42218 image with that older redpill-lkm commit as this is completely unusable now.

Okay, I'm now running a bit of a Frankenstein's monster :) :

  1. TTG's redpill-lkm master 021ed51
  2. jumkey's redpill-load dev 880c76b
  3. haydibe's script 0.7.4 (because 'redpill-lkm master 021ed51' won't compile with 0.11 due to missing build targets re. dev/prod/test)
  4. DSM 7.0.1-42218

 

Docker is still unstable when the system is under load: I need to wait a few minutes after boot to even start my containers that don't usually crash, but my influxdb container and data is still an instant crash. But at least on this set up it's not crashing when Plex Media Server is busy.

 

NB. with respect to instability under load, the docker crashes seem more likely to occur after a few reboots, when the server comes back up and starts disk scrubbing. My "stable" containers are more likely to crash the system if launched while disk scrubbing is running. This is purely a "feeling" on my part, though, and not backed up by empirical evidence.

Link to post
Share on other sites

@WiteWulf

 

On my baremetal N43L G7, i'm running 3615xs - 7.0.41222 and 3474d9b and looks a bit more stable for some reason. 

 

On 7.0.1.42214 & 42218 i had instant crash when i was searching with universal search (synoelasticd)

 

Traces lead to NMI

 

 <NMI>  [<ffffffff814a2759>] ? dump_stack+0xc/0x15
 [<ffffffff814a16b1>] ? panic+0xbb/0x1df
 [<ffffffff810a9eb8>] ? watchdog_overflow_callback+0xa8/0xb0
 [<ffffffff810db7d3>] ? __perf_event_overflow+0x93/0x230
 [<ffffffff810da612>] ? perf_event_update_userpage+0x12/0xf0
 [<ffffffff810152a4>] ? intel_pmu_handle_irq+0x1b4/0x340
 [<ffffffff814a9d06>] ? perf_event_nmi_handler+0x26/0x40
 [<ffffffff814a944e>] ? do_nmi+0xfe/0x440
 [<ffffffff814a8a53>] ? end_repeat_nmi+0x1e/0x7e
 <<EOE>>

 

Edited by pocopico
  • Like 1
Link to post
Share on other sites
17 minutes ago, Orphée said:

Are your SN and MAC address real DS918+ values ? or generated one ?

The SN and MAC must be real, and matching the running loader (DS918+ in your case).

 

what do you see in /var/log/messages and /var/log/synofoto.log ?

The SN & MAC are from real DS918+. I didn't see anything about the SN & MAC in /var/log/synofoto.log, and the information about the SN in /var/log/messages as below. 

 

Message in /var/log/messages:

2021-09-28T18:30:52+08:00 XXXX-NAS kernel: [   16.531414] Got empty serial number.                                                                                                                                                                                                                                              Generate serial number from product.
2021-09-28T18:30:52+08:00 XXXX-NAS kernel: [   16.665292] Got empty serial number.                                                                                                                                                                                                                                              Generate serial number from product.
2021-09-28T18:30:52+08:00 XXXX-NAS kernel: [   16.665295] drivers/usb/core/hub.c (                                                                                                                                                                                                                                             2940) Same device found. Change serial to ffffffccfffffffbffffffcbfffffff0

 

Link to post
Share on other sites
10 minutes ago, pocopico said:

@WiteWulf

 

On my baremetal N43L G7, i'm running 7.0.41222 and 3474d9b and looks a bit more stable for some reason. 

 

On 7.0.1.42214 & 42218 i had instant crash when i was searching with universal search (synoelasticd)

 

Traces lead to NMI

 

 <NMI>  [<ffffffff814a2759>] ? dump_stack+0xc/0x15
 [<ffffffff814a16b1>] ? panic+0xbb/0x1df
 [<ffffffff810a9eb8>] ? watchdog_overflow_callback+0xa8/0xb0
 [<ffffffff810db7d3>] ? __perf_event_overflow+0x93/0x230
 [<ffffffff810da612>] ? perf_event_update_userpage+0x12/0xf0
 [<ffffffff810152a4>] ? intel_pmu_handle_irq+0x1b4/0x340
 [<ffffffff814a9d06>] ? perf_event_nmi_handler+0x26/0x40
 [<ffffffff814a944e>] ? do_nmi+0xfe/0x440
 [<ffffffff814a8a53>] ? end_repeat_nmi+0x1e/0x7e
 <<EOE>>

 

maybe this fixes your issue ?

 

 

Screenshot_2021-09-28_14-27-07.png

Link to post
Share on other sites
22 minutes ago, pocopico said:

On 7.0.1.42214 & 42218 i had instant crash when i was searching with universal search (synoelasticd)

Interestingly, I've run a re-index of media folders (I use the Indexing Service to drive a UPnP music service via Media Service) and that's using postgresql.

 

Odd that they'd use postgresql for the built-in media indexing and elasticsearch for the Universal Search 🤔

Link to post
Share on other sites
17 hours ago, pocopico said:

DS918+ (4.4.180+) 的一些编译模块。大多数网络驱动程序已经过测试并且可以正常工作

 

https://github.com/pocopico/4.4.180plus-modules

 

 

Thank you for your offer. I tried to mount mptsas.ko in DS918, but it depends on scsi_ transport_ sas.ko, there is no such driver in GIT. Could you compile it?

Link to post
Share on other sites

I'm back on 7.0.1-42218 with redpill-lkm 3474d9b as that Franken-rig was just as unstable.

 

With Plex Media Server and Docker both stopped I now appear to have a pretty stable file and web server (that's not particularly useful) and not much else 🤣

Link to post
Share on other sites
3 minutes ago, stefauresi said:

Hi,

My motherboard have 2 NIC , if i try to inject atlantic.ko driver my ASUS 10Gb turn off , i need boot with disable nic (motherboard) but DSM 7 no load atlantic.ko driver when DSM start

Best regards

 

Due to its size, It will not be possible to have the atlantic.ko driver into loader, you will have to wait for RedPill beta release

Edited by pocopico
Link to post
Share on other sites
30 minutes ago, pocopico said:

 

Its there now.. Not sure though that SAS will work ATM 

Thank you very much, but it seems that there is no way to use it for my LSI2308 SAS controller. I think it might need mpt2sas.ko or mpt3sas.ko. At least on Ubuntu 20.04 LTS, it shows that it uses mpt3sas.ko. It's really sad.

 

Quote

0000:01:00.0 Class 0107: Device 1000:0086 (rev 05)
        Subsystem: Device 15d9:0691
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at e000 [size=256]
        Region 1: Memory at df140000 (64-bit, non-prefetchable) [size=64K]
        Region 3: Memory at df100000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at df000000 [disabled] [size=1M]
        Capabilities: [50] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [68] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 4096 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
                DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
                        RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
                        MaxPayload 256 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend-
                LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L0s, Exit Latency L0s <64ns
                        ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 8GT/s (ok), Width x8 (ok)
                        TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF Not Supported
                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
                         AtomicOpsCtl: ReqEn-
                LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+
                         EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
        Capabilities: [d0] Vital Product Data
                Unknown small resource type 00, will not decode more.
        Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [c0] MSI-X: Enable- Count=16 Masked-
                Vector table: BAR=1 offset=0000e000
                PBA: BAR=1 offset=0000f000
        Capabilities: [100 v2] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
                AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
                        MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
                HeaderLog: 04000001 00000003 01010000 d20fbf4a
        Capabilities: [1e0 v1] Secondary PCI Express
                LnkCtl3: LnkEquIntrruptEn-, PerformEqu-
                LaneErrStat: 0
        Capabilities: [1c0 v1] Power Budgeting <?>
        Capabilities: [190 v1] Dynamic Power Allocation <?>
        Capabilities: [148 v1] Alternative Routing-ID Interpretation (ARI)
                ARICap: MFVC- ACS-, Next Function: 0
                ARICtl: MFVC- ACS-, Function Group: 0
 

 

Link to post
Share on other sites
10 minutes ago, pocopico said:

@flybird08 I've uploaded the modules, you can to download the mpt3sas.ko and try, but again you will not be able to use the SAS drives.

Actually, just to "fix" words between SAS card and drives.

On my case, and I think on most of us, drives are SATA.

We have a LSI SAS HBA IT card, but with SAS to SATA cable

https://www.amazon.fr/CableDeconn-SFF-8087-Fanout-Wihout-Latch/dp/B00S7KU0VO/

image.png.2aaea678146c00a88ec8089b65299cb1.png

 

I just want to be clear on this. for @ThorGroup

Disks are detected as SAS whereas there are SATA drives on SAS card.

 

Thanks

Edited by Orphée
  • Like 1
Link to post
Share on other sites
9 minutes ago, Orphée said:

Actually, just to "fix" words between SAS card and drives.

On my case, and I think on most of us, drives are SATA.

We have a LSI SAS HBA IT card, but with SAS to SATA cable

https://www.amazon.fr/CableDeconn-SFF-8087-Fanout-Wihout-Latch/dp/B00S7KU0VO/

image.png.2aaea678146c00a88ec8089b65299cb1.png

 

I just want to be clear on this. for @ThorGroup

Disks are detected as SAS whereas there are SATA drives on SAS card.

 

Thanks

 

I know what you mean, problem is that mpt3sas module will name the devices in a way it cannot be interpreted correctly by DSM. Also not all synology models support SAS by default so here we are waiting for the RedPill magic

Edited by pocopico
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.