speed improvement with kernel 4.2.5 / 4.3.3 / 4.6.6

[wd9895]

UIMAGE-433-KIRKWOOD-7.zip is also applicable for NWS2 ?

[fvdw]

UIMAGE-433-KIRKWOOD-7.zip is also applicable for NWS2 ?

Yes

[Jocko]

Caution: modules for version 4.3.3 are in this post : viewtopic.php?f=4&t=2345&start=20#p21362

[wd9895]

Got it already.
Thx.

[fvdw]

attached a new kernel

it seems the the mv643xx driver in the 4.3.3 has a bug
On heavy load you see these errors in dmesg
mv643xx_eth_port mv643xx_eth_port.0 eth0: failed to linearize skb with tiny unaligned fragment
It happens mainly when using rsync as experienced by some users of the new kernel.
It causes data corruption so without a fix this kernel cannot be used

Attached a new kernel
This new kernel contains this patch which should solve this problem
net: mv643xx_eth: fix packet corruption with TSO and tiny unaligned packets

please test

[moonshadow88]

Hi,

i'm trying to load the 4.3.3 kernel with fvdw-sl-console-6-16-1-9feb2016-32bits (option "external kerne, load and start").

I have untared the modules:

Code: Select all

root@MooNNAS:/lib/modules/4.3.3 # ls
block2mtd.ko  ehci-orion.ko      isofs.ko         mtdram.ko       scsi_transport_iscsi.ko  u_ether.ko       usb_f_ecm.ko           usb-storage.ko
bonding.ko    ehci-pci.ko        libcomposite.ko  mv_udc.ko       sg.ko                    ums-alauda.ko    usb_f_ecm_subset.ko    videobuf-core.ko
btrfs.ko      ftdi-elan.ko       libiscsi.ko      pktgen.ko       sisusbvga.ko             ums-datafab.ko   usb_f_mass_storage.ko  videobuf-vmalloc.ko
cdrom.ko      ftdi_sio.ko        libiscsi_tcp.ko  pl2303.ko       squashfs.ko              ums-freecom.ko   usb_f_rndis.ko         wire.ko
configfs.ko   g_ether.ko         mdc800.ko        r8712u.ko       sr_mod.ko                ums-jumpshot.ko  usbhid.ko              xhci-hcd.ko
cramfs.ko     g_mass_storage.ko  michael_mic.ko   rtc-m41t80.ko   udc-core.ko              ums-sddr09.ko    usblp.ko               xhci-pci.ko
ehci-hcd.ko   iscsi_tcp.ko       modules.dep      rtc-pcf8563.ko  udf.ko                   ums-sddr55.ko    usbserial.ko           zr364xx.ko
root@MooNNAS:/lib/modules/4.3.3 #


I run the command "poweroff" from ssh console, start fvdw-sl-console, action => "esternal kernel, load and start", select the "UIMAGE-433-KIRKWOOD-8" file and tft and cmd windows shows up. I start the nwsp2 and the only thing it does is a brief blue/red blink (like 3 times) and ir doesn't do anything else.

if I shutdown the nas and the fvdw console (also the tft server and everything) and powerup the nas again it boots fine.

what i'm doing wrong?

my computer is a win10 x64, firewall disabled. IP's (pc and nas) are ok on fvdw console.

ok here it is, the zip archive contains the 4.2.5 kirkwood kernel, the tar archive the modules

To install:
Put the the tar archive with the modules in the system root (/) and extract the tar archive
Now you should have a directory /lib/modules/4.2.5 containing the modules


For the kernel you have two options (of course first extract the zip archive):

(1) use the fvdw-sl console to load an external kernel
(2) write it directly to /dev/sda6 (dd if=uImage-4.2.5-kirkwood-11 of=/dev/sda6)

The advantage of option 1 is that in case the kernel will not run then you simple reboot the nas and it will come up with the old kernel.
The disadvantage of option 1 that you will need to do step 2 anyhow if you wan that your nas after reboot automatically uses this new kernel. If you don't do this then you will need to load the kernel via the console at every boot
Option 2 should be save the kernel runs on my system, and with the fvdw-sl console you can always restore the old kernel.

Please post speed tests !!

remember this is beta test.

--edit, kernel removed, seems unstable when transferring many files

[Jocko]

Hi moonshadow88,

Indeed,it had to work :scratch

So I see only two explanations:
- You use a wireless connection on your laptop and the uploaded kernel image was corrupted when fvdw-sl console loaded it.
- kernel image is corrupted in the tftp folder (or your dowloaded file is corrupted from plugout);

So tried again to download the kernel image and unzip it.

[moonshadow88]

network connectios was wired and downloaded kernel file about 3 times ...

Hi moonshadow88,

Indeed,it had to work :scratch

So I see only two explanations:
- You use a wireless connection on your laptop and the uploaded kernel image was corrupted when fvdw-sl console loaded it.
- kernel image is corrupted in the tftp folder (or your dowloaded file is corrupted from plugout);

So tried again to download the kernel image and unzip it.

[Jocko]

Anyhow I'd rather you check the kernel file:
its md5sum is

Code: Select all

e41661e97c70f7f7747155a6788fca8d  UIMAGE-433-KIRKWOOD-8

Note: Nswp2 loads modules only for USB drivers, the issue is on the kernel image side.

[moonshadow88]

Problem solved. Checksum was ok. My nas is a NWS2.

The problem was the stupid McAfee blocking connections ...

Here my speeds: