Debian on Netgear RN102
Posted by whitepawn
|
Re: Debian on Netgear RN102 September 30, 2020 05:35AM |
Admin Registered: 13 years ago Posts: 18,543 |
whitepawn,
To recap and make sure I start from the correct set of envs (this thread became too long to find outwhat's your current envs are :). Please verify.
The current booting envs are:
The new envs should be (on top of the above already set envs)
Of course, these envs are for test-booting eSATA. Once eSATA booting works, we'd want to to come back and incorporate both SATA and USB booting in the envs. So that when there is problem booting with eSATA, you can plug in the USB rootfs to "rescue" the box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
To recap and make sure I start from the correct set of envs (this thread became too long to find outwhat's your current envs are :). Please verify.
The current booting envs are:
Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x200000@0(u-boot),0x20000@0x00180000(u-boot-env),-(ubifs)' Marvell>> mtdparts=pxa3xx_nand-0:0x200000@0(u-boot),0x20000@0x00180000(u-boot-env) Marvell>> mtdids=nand0=pxa3xx Marvell>> partition=nand0,2 Marvell>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial' Marvell>> setenv load_uimage 'ext2load usb 0:1 0x2000000 /boot/uImage' Marvell>> setenv load_uinitrd 'ext2load usb 0:1 0x3000000 /boot/uInitrd' Marvell>> setenv usb_boot 'run load_uimage; if run load_uinitrd; then bootm 0x2000000 0x3000000; else bootm 0x2000000; fi' Marvell>> setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot' Marvell>> setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset' Marvell>> setenv fdt_skip_update yes Marvell>> boot
The new envs should be (on top of the above already set envs)
setenv sata_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial' setenv load_uimage 'ext2load ide 0:1 0x2000000 /boot/uImage' setenv load_uinitrd 'ext2load ide 0:1 0x3000000 /boot/uInitrd' setenv sata_boot 'run load_uimage; if run load_uinitrd; then bootm 0x2000000 0x3000000; else bootm 0x2000000; fi' setenv sata_bootcmd 'run sata_set_bootargs; run sata_boot' setenv bootcmd 'ide reset; run sata_bootcmd; reset' boot
Of course, these envs are for test-booting eSATA. Once eSATA booting works, we'd want to to come back and incorporate both SATA and USB booting in the envs. So that when there is problem booting with eSATA, you can plug in the USB rootfs to "rescue" the box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 30, 2020 06:42AM |
Registered: 4 years ago Posts: 73 |
Bodhi
I have tested with your envs it succeeded.Here is what i have done:
Also tested my stress command with this config; i am pretty sure it is solved.`Insert happy smile face emoji here.`
I also tested with my junkyard mSATA disk which is shinedisk branded JMF605 controller and Intel NAND based disk but it cannot detected by u-boot.Maybe better branded disks will work.
Even with my old SATA II drive it is way way more faster booting rather than USB.
Regards
Edit
Attached mSATA photos in post.
Edited 1 time(s). Last edit at 09/30/2020 06:52AM by whitepawn.
I have tested with your envs it succeeded.Here is what i have done:
BootROM 1.08
Booting from NAND flash
General initialization - Version: 1.0.0
High speed PHY - Version: 2.1.4 (COM-PHY-V20)
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0001
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **
U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1
06/23/2015 ReadyNAS-102 V2.0
Board: DB-88F6710-BP
SoC: MV6710 A1
CPU: Marvell PJ4B v7 UP (Rev 1) LE
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 200 [MHz]
DDR @ 600 [MHz]
DDR 16Bit Width, FastPath Memory Access
DRAM: 512 MiB
Map: Code: 0x1feef000:0x1ff9ef34
BSS: 0x1ffef0a0
Stack: 0x1f9eeef8
Heap: 0x1f9ef000:0x1feef000
NAND: (ID 0xf12c) 128 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
GBE0
SDIO
AUDIO
TDM
Modules/Interfaces Detected:
RGMII1 Phy
PEX0 (Lane 0)
PEX1 (Lane 1)
SATA0 (Lane 2)
SATA1 (Lane 3)
Net: , egiga1 [PRIME]
Power supply plug on, please press power button!
BootROM 1.08
Booting from NAND flash
l
General initialization - Version: 1.0.0
High speed PHY - Version: 2.1.4 (COM-PHY-V20)
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0000
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED
l
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **
U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1
06/23/2015 ReadyNAS-102 V2.0
Board: DB-88F6710-BP
SoC: MV6710 A1
CPU: Marvell PJ4B v7 UP (Rev 1) LE
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 200 [MHz]
DDR @ 600 [MHz]
DDR 16Bit Width, FastPath Memory Access
DRAM: 512 MiB
l
Map: Code: 0x1feef000:0x1ff9ef34
BSS: 0x1ffef0a0
Stack: 0x1f9eeef8
Heap: 0x1f9ef000:0x1feef000
NAND: (ID 0xf12c) 128 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
GBE0
SDIO
AUDIO
TDM
Modules/Interfaces Detected:
RGMII1 Phy
PEX0 (Lane 0)
PEX1 (Lane 1)
SATA0 (Lane 2)
SATA1 (Lane 3)
Net: , egiga1 [PRIME]
Power On!
FDT loaded successfully
Hit any key to stop autoboot: 0
Marvell>> <INTERRUPT>
Marvell>> <INTERRUPT>
Marvell>> <INTERRUPT>
Marvell>> <INTERRUPT>
Marvell>> printenv
AC_Power_fail_detect=open
CASset=min
HW_version=MVT
MALLOC_len=5
Manufacturer=NETGEAR
Product=ReadyNAS 102
SKUNum=RN102
SerialNum=MASKED
Startup=Normal
UUID=adaf7396-2c8f-11e5-81d4-e8fcafe67a08
Version=V1.0
autoload=no
bootargs=console=ttyS0,115200
bootargs_end=:10.4.50.254:255.255.255.0:KW40:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=usb start; run usb_bootcmd; usb stop; reset
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_ubi=ubi part ubifs; ubifsmount rootfs; ubifsload 0x2000000 kernel; ubifsload 0x3000000 initrd.gz; bootm 0x2000000 0x3000000 0x1000000
bootdelay=0
cacheShare=no
console=console=ttyS0,115200
disL2Cache=yes
disaMvPnp=no
eeeEnable=no
enaAutoRecovery=yes
enaClockGating=yes
enaExtDisk=no
enaFPU=no
enaMonExt=no
enaWrAllo=no
envver=3
eth1addr=MASKED
eth1mtu=1500
ethact=egiga1
ethaddr=MASKED
ethmtu=1500
ethprime=egiga1
fdt_skip_update=yes
fdtaddr=0x1000000
fdtfile=armada-370-db.dtb
image_name=uImage
initrd_name=uInitrd
load_addr=0x02000000
load_uimage=ext2load usb 0:1 0x2000000 /boot/uImage
load_uinitrd=ext2load usb 0:1 0x3000000 /boot/uInitrd
loadaddr=0x02000000
mtdids=nand0=armada-nand
mtdparts=mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)
mvNetConfig=mv_net_config=1,(00:50:43:11:11:11,0:1:2:3:4),mtu=1500
mv_pon_addr=MASKED
nandEcc=1bit
netbsd_en=no
netretry=no
pcieTune=no
pexMode=rc
pxe_files_load=:default.arm-armada370-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
rcvrip=169.254.100.100
sata_delay_reset=0
sata_dma_mode=yes
setL2CacheWT=no
standalone=fsload $load_addr $image_name;setenv bootargs $console $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm $load_addr;
stderr=serial
stdin=serial
stdout=serial
usb0Mode=host
usb1Mode=host
usb2Mode=device
usbActive=0
usb_boot=run load_uimage; if run load_uinitrd; then bootm 0x2000000 0x3000000; else bootm 0x2000000; fi
usb_bootcmd=run usb_set_bootargs; run usb_boot
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial init=/bin/systemd
vxworks_en=no
yuk_ethaddr=MASKED
Environment size: 2624/131068 bytes
Marvell>> ide reset
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Device 0 @ 0 0:
Model: ST940210AS Firm: 3.ALC Ser#: 5QX1VL4R
Type: Hard Disk
Supports 48-bit addressing
Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
Marvell>> setenv sata_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial'
Marvell>> setenv load_uimage 'ext2load ide 0:1 0x2000000 /boot/uImage'
Marvell>> setenv load_uinitrd 'ext2load ide 0:1 0x3000000 /boot/uInitrd'
Marvell>> setenv sata_boot 'run load_uimage; if run load_uinitrd; then bootm 0x2000000 0x3000000; else bootm 0x2000000; fi'
Marvell>> setenv sata_bootcmd 'run sata_set_bootargs; run sata_boot'
Marvell>> setenv bootcmd 'ide reset; run sata_bootcmd; reset'
Marvell>> boot
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Device 0 @ 0 0:
Model: ST940210AS Firm: 3.ALC Ser#: 5QX1VL4R
Type: Hard Disk
Supports 48-bit addressing
Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
Loading file "/boot/uImage" from ide device 0:1 ()
5418806 bytes read
Loading file "/boot/uInitrd" from ide device 0:1 ()
9576098 bytes read
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-5.8.5-mvebu-370xp-tld-1
Created: 2020-09-09 21:14:23 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5418742 Bytes = 5.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
Image Name: initramfs-5.8.5-mvebu-370xp-tld-
Created: 2020-09-09 21:45:01 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9576034 Bytes = 9.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020
[ 0.000000][ T0] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d
[ 0.000000][ T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: NETGEAR ReadyNAS 102
[ 0.000000][ T0] printk: bootconsole [earlycon0] enabled
[ 0.000000][ T0] Memory policy: Data cache writeback
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] Normal [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] HighMem empty
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] CPU: All CPU(s) started in SVC mode.
[ 0.000000][ T0] percpu: Embedded 20 pages/cpu s53068 r8192 d20660 u81920
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 130048
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102
[ 0.000000][ T0] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000][ T0] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000][ T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.000000][ T0] Memory: 493536K/524288K available (10240K kernel code, 1012K rwdata, 3072K rodata, 1024K init, 342K bss, 30752K reserved, 0K cma-reserved, 0K highmem)
[ 0.000000][ T0] random: get_random_u32 called from ____cache_alloc+0x338/0x794 with crng_init=0
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000][ T0] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[ 0.000000][ T0] Trampoline variant of Tasks RCU enabled.
[ 0.000000][ T0] Rude variant of Tasks RCU enabled.
[ 0.000000][ T0] Tracing variant of Tasks RCU enabled.
[ 0.000000][ T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000][ T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.000000][ T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000][ T0] L2C: DT/platform modifies aux control register: 0x12086300 -> 0x1a086302
[ 0.000000][ T0] Aurora cache controller enabled, 4 ways, 256 kB
[ 0.000000][ T0] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302
[ 0.000000][ T0] Switching to timer-based delay loop, resolution 53ns
[ 0.000007][ T0] sched_clock: 32 bits at 18MHz, resolution 53ns, wraps every 114537122277ns
[ 0.007875][ T0] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 101938038664 ns
[ 0.019296][ T0] Console: colour dummy device 80x30
[ 0.024014][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 37.49 BogoMIPS (lpj=187492)
[ 0.034144][ T0] pid_max: default: 32768 minimum: 301
[ 0.039208][ T0] LSM: Security Framework initializing
[ 0.044156][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.051484][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.060284][ T0] CPU: Testing write buffer coherency: ok
[ 0.065726][ T1] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.072050][ T1] Setting up static identity map for 0x100000 - 0x100060
[ 0.078739][ T1] mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1
[ 0.084170][ T1] mvebu-pmsu: Initializing Power Management Service Unit
[ 0.090695][ T1] rcu: Hierarchical SRCU implementation.
[ 0.098516][ T1] smp: Bringing up secondary CPUs ...
[ 0.103406][ T1] smp: Brought up 1 node, 1 CPU
[ 0.107703][ T1] SMP: Total of 1 processors activated (37.49 BogoMIPS).
[ 0.114020][ T1] CPU: All CPU(s) started in SVC mode.
[ 0.119562][ T1] devtmpfs: initialized
[ 0.128127][ T1] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[ 0.137058][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.146826][ T1] futex hash table entries: 256 (order: 2, 16384 bytes, linear)
[ 0.154039][ T1] xor: measuring software checksum speed
[ 0.258575][ T1] arm4regs : 1103.200 MB/sec
[ 0.358572][ T1] 8regs : 671.200 MB/sec
[ 0.458568][ T1] 32regs : 1062.400 MB/sec
[ 0.463020][ T1] xor: using function: arm4regs (1103.200 MB/sec)
[ 0.468783][ T1] prandom: seed boundary self test passed
[ 0.477386][ T1] prandom: 100 self tests passed
[ 0.481800][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.488927][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.489667][ T1] NET: Registered protocol family 16
[ 0.502527][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.510413][ T1] audit: initializing netlink subsys (disabled)
[ 0.516384][ T31] audit: type=2000 audit(0.490:1): state=initialized audit_enabled=0 res=1
[ 0.526685][ T1] cpuidle: using governor ladder
[ 0.532707][ T1] cpuidle: using governor menu
[ 0.537196][ T1] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.809557][ T1] raid6: int32x8 gen() 214 MB/s
[ 0.978936][ T1] raid6: int32x8 xor() 135 MB/s
[ 1.148652][ T1] raid6: int32x4 gen() 224 MB/s
[ 1.318713][ T1] raid6: int32x4 xor() 151 MB/s
[ 1.488583][ T1] raid6: int32x2 gen() 414 MB/s
[ 1.658576][ T1] raid6: int32x2 xor() 217 MB/s
[ 1.828603][ T1] raid6: int32x1 gen() 430 MB/s
[ 1.998588][ T1] raid6: int32x1 xor() 201 MB/s
[ 2.003120][ T1] raid6: using algorithm int32x1 gen() 430 MB/s
[ 2.008692][ T1] raid6: .... xor() 201 MB/s, rmw enabled
[ 2.013776][ T1] raid6: using intx1 recovery algorithm
[ 2.020116][ T1] vgaarb: loaded
[ 2.025092][ T1] SCSI subsystem initialized
[ 2.030360][ T1] usbcore: registered new interface driver usbfs
[ 2.036057][ T1] usbcore: registered new interface driver hub
[ 2.043251][ T1] usbcore: registered new device driver usb
[ 2.049960][ T1] mc: Linux media interface: v0.10
[ 2.055395][ T1] videodev: Linux video capture interface: v2.00
[ 2.061877][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 2.067046][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 2.076787][ T1] PTP clock support registered
[ 2.084612][ T1] clocksource: Switched to clocksource armada_370_xp_clocksource
[ 3.073711][ T1] VFS: Disk quotas dquot_6.6.0
[ 3.078094][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 3.112821][ T1] NET: Registered protocol family 2
[ 3.120382][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 3.129098][ T1] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 3.137145][ T1] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 3.144338][ T1] TCP: Hash tables configured (established 4096 bind 4096)
[ 3.151444][ T1] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 3.158263][ T1] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 3.165496][ T1] NET: Registered protocol family 1
[ 3.170872][ T1] RPC: Registered named UNIX socket transport module.
[ 3.177015][ T1] RPC: Registered udp transport module.
[ 3.181942][ T1] RPC: Registered tcp transport module.
[ 3.186889][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.193407][ T1] PCI: CLS 0 bytes, default 64
[ 3.198017][ T1] Trying to unpack rootfs image as initramfs...
[ 3.818332][ T1] Freeing initrd memory: 9352K
[ 3.822835][ T1] NetWinder Floating Point Emulator V0.97 (double precision)
[ 3.829784][ T1] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 3.840775][ T1] Initialise system trusted keyrings
[ 3.847601][ T1] Key type blacklist registered
[ 3.852132][ T1] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[ 3.858951][ T1] zbud: loaded
[ 3.863539][ T1] NFS: Registering the id_resolver key type
[ 3.869272][ T1] Key type id_resolver registered
[ 3.873728][ T1] Key type id_legacy registered
[ 3.878167][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 3.885058][ T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 3.891809][ T1] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 3.900090][ T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 3.907047][ T1] orangefs_init: module version upstream loaded
[ 3.989619][ T1] async_tx: api initialized (async)
[ 3.994251][ T1] Key type asymmetric registered
[ 3.998700][ T1] Asymmetric key parser 'x509' registered
[ 4.004136][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[ 4.011761][ T1] io scheduler bfq registered
[ 4.018830][ T1] armada-370-pinctrl d0018000.pin-ctrl: registered pinctrl driver
[ 4.035792][ T1] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00
[ 4.042558][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 4.048799][ T1] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[ 4.056089][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 4.062598][ T1] pci 0000:00:01.0: [11ab:6710] type 01 class 0x060400
[ 4.068956][ T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 4.076373][ T1] pci 0000:00:02.0: [11ab:6710] type 01 class 0x060400
[ 4.082523][ T1] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 4.090977][ T1] PCI: bus0: Fast back to back transfers disabled
[ 4.096932][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.105035][ T1] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.113354][ T1] pci 0000:01:00.0: [1b4b:9170] type 00 class 0x010601
[ 4.119721][ T1] pci 0000:01:00.0: reg 0x10: [io 0xfffffff8-0xffffffff]
[ 4.126200][ T1] pci 0000:01:00.0: reg 0x14: [io 0xfffffffc-0xffffffff]
[ 4.132564][ T1] pci 0000:01:00.0: reg 0x18: [io 0xfffffff8-0xffffffff]
[ 4.139022][ T1] pci 0000:01:00.0: reg 0x1c: [io 0xfffffffc-0xffffffff]
[ 4.145444][ T1] pci 0000:01:00.0: reg 0x20: [io 0xfffffff0-0xffffffff]
[ 4.151809][ T1] pci 0000:01:00.0: reg 0x24: [mem 0x40000000-0x400001ff]
[ 4.158234][ T1] pci 0000:01:00.0: reg 0x30: [mem 0xd0000000-0xd000ffff pref]
[ 4.165058][ T1] pci 0000:01:00.0: Enabling fixed DMA alias to 00.1
[ 4.171075][ T1] pci 0000:01:00.0: PME# supported from D3hot
[ 4.176984][ T1] pci 0000:00:01.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[ 4.215705][ T1] PCI: bus1: Fast back to back transfers disabled
[ 4.221444][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 4.228539][ T1] pci 0000:02:00.0: [1b73:1009] type 00 class 0x0c0330
[ 4.234893][ T1] pci 0000:02:00.0: reg 0x10: [mem 0x42000000-0x4200ffff 64bit]
[ 4.241739][ T1] pci 0000:02:00.0: reg 0x18: [mem 0x42010000-0x42010fff 64bit]
[ 4.248688][ T1] pci 0000:02:00.0: reg 0x20: [mem 0x42011000-0x42011fff 64bit]
[ 4.255692][ T1] pci 0000:02:00.0: supports D1
[ 4.259991][ T1] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold
[ 4.266947][ T1] pci 0000:00:02.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[ 4.305700][ T1] PCI: bus2: Fast back to back transfers disabled
[ 4.311437][ T1] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 4.318264][ T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff]
[ 4.325236][ T1] pci 0000:00:02.0: BAR 14: assigned [mem 0xf8100000-0xf81fffff]
[ 4.332150][ T1] pci 0000:00:01.0: BAR 13: assigned [io 0x10000-0x10fff]
[ 4.338636][ T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xf8200000-0xf82007ff pref]
[ 4.345888][ T1] pci 0000:00:02.0: BAR 6: assigned [mem 0xf8300000-0xf83007ff pref]
[ 4.353125][ T1] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8000000-0xf800ffff pref]
[ 4.360372][ T1] pci 0000:01:00.0: BAR 5: assigned [mem 0xf8010000-0xf80101ff]
[ 4.367227][ T1] pci 0000:01:00.0: BAR 4: assigned [io 0x10000-0x1000f]
[ 4.373587][ T1] pci 0000:01:00.0: BAR 0: assigned [io 0x10010-0x10017]
[ 4.379965][ T1] pci 0000:01:00.0: BAR 2: assigned [io 0x10018-0x1001f]
[ 4.386341][ T1] pci 0000:01:00.0: BAR 1: assigned [io 0x10020-0x10023]
[ 4.392700][ T1] pci 0000:01:00.0: BAR 3: assigned [io 0x10024-0x10027]
[ 4.399077][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 4.404246][ T1] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 4.410622][ T1] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff]
[ 4.417481][ T1] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8100000-0xf810ffff 64bit]
[ 4.424816][ T1] pci 0000:02:00.0: BAR 2: assigned [mem 0xf8110000-0xf8110fff 64bit]
[ 4.432131][ T1] pci 0000:02:00.0: BAR 4: assigned [mem 0xf8111000-0xf8111fff 64bit]
[ 4.439463][ T1] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 4.444651][ T1] pci 0000:00:02.0: bridge window [mem 0xf8100000-0xf81fffff]
[ 4.451601][ T1] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[ 4.457947][ T1] pcieport 0000:00:02.0: enabling device (0140 -> 0142)
[ 4.465448][ T1] mv_xor d0060800.xor: Marvell shared XOR driver
[ 4.535996][ T1] mv_xor d0060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 4.547014][ T1] mv_xor d0060900.xor: Marvell shared XOR driver
[ 4.615987][ T1] mv_xor d0060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 4.818368][ T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 4.829501][ T1] printk: console [ttyS0] disabled
[ 4.855745][ T1] d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 19, base_baud = 12500000) is a 16550A
[ 4.864765][ T1] printk: console [ttyS0] enabled
[ 4.864765][ T1] printk: console [ttyS0] enabled
[ 4.873748][ T1] printk: bootconsole [earlycon0] disabled
[ 4.873748][ T1] printk: bootconsole [earlycon0] disabled
[ 4.886615][ T1] ahci 0000:01:00.0: enabling device (0146 -> 0147)
[ 4.892862][ T1] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[ 4.901955][ T1] ahci 0000:01:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[ 4.913433][ T1] scsi host0: ahci
[ 4.918115][ T1] scsi host1: ahci
[ 4.922159][ T1] ata1: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010100 irq 42
[ 4.929953][ T1] ata2: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010180 irq 42
[ 4.938921][ T1] sata_mv d00a0000.sata: slots 32 ports 1
[ 4.946963][ T1] scsi host2: sata_mv
[ 4.951282][ T1] ata3: SATA max UDMA/133 irq 27
[ 4.957392][ T1] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xf1
[ 4.963893][ T1] nand: Micron MT29F1G08ABADAWP
[ 4.969282][ T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 4.977817][ T1] Bad block table found at page 65472, version 0x01
[ 4.984282][ T1] Bad block table found at page 65408, version 0x01
[ 4.990720][ T1] 5 cmdlinepart partitions found on MTD device pxa3xx_nand-0
[ 4.997475][ T1] Creating 5 MTD partitions on "pxa3xx_nand-0":
[ 5.003096][ T1] 0x000000000000-0x000000180000 : "u-boot"
[ 5.010606][ T1] 0x000000180000-0x0000001a0000 : "u-boot-env"
[ 5.018967][ T1] 0x000000200000-0x000000800000 : "uImage"
[ 5.027025][ T1] 0x000000800000-0x000000c00000 : "minirootfs"
[ 5.035382][ T1] 0x000000c00000-0x000008000000 : "ubifs"
[ 5.045226][ T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 5.053090][ T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[ 5.067584][ T1] libphy: Fixed MDIO Bus: probed
[ 5.077223][ T1] libphy: orion_mdio_bus: probed
[ 5.099800][ T1] mvneta d0074000.ethernet eth0: Using random mac address e6:55:af:58:54:99
[ 5.112311][ T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.119575][ T1] ehci-pci: EHCI PCI platform driver
[ 5.124545][ T1] ehci-orion: EHCI orion driver
[ 5.129602][ T1] orion-ehci d0050000.usb: EHCI Host Controller
[ 5.135535][ T1] orion-ehci d0050000.usb: new USB bus registered, assigned bus number 1
[ 5.143363][ T1] orion-ehci d0050000.usb: irq 25, io mem 0xd0050000
[ 5.174662][ T1] orion-ehci d0050000.usb: USB 2.0 started, EHCI 1.00
[ 5.181135][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[ 5.189480][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.196845][ T1] usb usb1: Product: EHCI Host Controller
[ 5.202034][ T1] usb usb1: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 ehci_hcd
[ 5.209075][ T1] usb usb1: SerialNumber: d0050000.usb
[ 5.215127][ T1] hub 1-0:1.0: USB hub found
[ 5.219621][ T1] hub 1-0:1.0: 1 port detected
[ 5.225479][ T1] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 5.231487][ T1] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 5.239937][ T1] xhci_hcd 0000:02:00.0: hcc params 0x200073a1 hci version 0x100 quirks 0x0000000000080010
[ 5.250066][ T1] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[ 5.258480][ T1] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.265858][ T1198] ata2: SATA link down (SStatus 0 SControl 300)
[ 5.271546][ T1194] ata1: SATA link down (SStatus 0 SControl 300)
[ 5.277229][ T1] usb usb2: Product: xHCI Host Controller
[ 5.282467][ T1] usb usb2: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 xhci-hcd
[ 5.289564][ T1] usb usb2: SerialNumber: 0000:02:00.0
[ 5.295539][ T1] hub 2-0:1.0: USB hub found
[ 5.299957][ T1] hub 2-0:1.0: 2 ports detected
[ 5.305441][ T1] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 5.310931][ T1] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
[ 5.318843][ T1] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed
[ 5.325737][ T1] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 5.334030][ T1] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08
[ 5.342436][ T1] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.349798][ T1] usb usb3: Product: xHCI Host Controller
[ 5.354984][ T1] usb usb3: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 xhci-hcd
[ 5.361960][ T1] usb usb3: SerialNumber: 0000:02:00.0
[ 5.367830][ T1] hub 3-0:1.0: USB hub found
[ 5.372227][ T1] hub 3-0:1.0: 2 ports detected
[ 5.378380][ T1] usbcore: registered new interface driver usblp
[ 5.385183][ T1] usbcore: registered new interface driver usb-storage
[ 5.392173][ T1] mousedev: PS/2 mouse device common for all mice
[ 5.400008][ T1] i2c /dev entries driver
[ 5.408793][ T1] rtc-ds1307 0-0068: 'wakeup-source' is set, request for an IRQ is disabled!
[ 5.422176][ T1] rtc-ds1307 0-0068: registered as rtc0
[ 5.428860][ T1] rtc-ds1307 0-0068: setting system clock to 2000-01-06T23:43:41 UTC (947202221)
[ 5.454694][ T1209] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[ 5.466381][ T1] orion_wdt: Initial timeout 229 sec
[ 5.471716][ T1209] ata3.00: ATA-7: ST940210AS, 3.ALC, max UDMA/100
[ 5.478760][ T1] device-mapper: uevent: version 1.0.3
[ 5.483813][ T1209] ata3.00: 78140160 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 5.491407][ T1] device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com
[ 5.500816][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 5.507901][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 5.514985][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 5.521811][ T1209] ata3.00: configured for UDMA/100
[ 5.526524][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 5.532781][ T1] device-mapper: raid: Loading target version 1.15.1
[ 5.546487][ T1] marvell-cesa d0090000.crypto: CESA device successfully registered
[ 5.554273][ T180] scsi 2:0:0:0: Direct-Access ATA ST940210AS C PQ: 0 ANSI: 5
[ 5.563269][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 5.571125][ T15] sd 2:0:0:0: [sda] 78140160 512-byte logical blocks: (40.0 GB/37.3 GiB)
[ 5.580889][ T1] usbcore: registered new interface driver usbhid
[ 5.587369][ T15] sd 2:0:0:0: [sda] Write Protect is off
[ 5.592594][ T1] usbhid: USB HID core driver
[ 5.597105][ T15] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5.606961][ T1] drop_monitor: Initializing network drop monitor service
[ 5.616171][ T1] NET: Registered protocol family 10
[ 5.622358][ T1] Segment Routing with IPv6
[ 5.626540][ T1] RPL Segment Routing with IPv6
[ 5.630959][ T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 5.639503][ T1] NET: Registered protocol family 17
[ 5.645332][ T1] 8021q: 802.1Q VLAN Support v1.8
[ 5.649918][ T1] Key type dns_resolver registered
[ 5.654924][ T1] ThumbEE CPU extension supported.
[ 5.659511][ T1] Registering SWP/SWPB emulation handler
[ 5.665168][ T1] registered taskstats version 1
[ 5.669592][ T1] Loading compiled-in X.509 certificates
[ 5.675147][ T1] zswap: loaded using pool lzo/zbud
[ 5.680267][ T1] Key type ._fscrypt registered
[ 5.684719][ T1] Key type .fscrypt registered
[ 5.688976][ T1] Key type fscrypt-provisioning registered
[ 5.697271][ T1] Key type big_key registered
[ 5.726126][ T1] Key type encrypted registered
[ 5.735234][ T1] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 5.775119][ T15] sda: sda1
[ 5.781769][ T15] sd 2:0:0:0: [sda] Attached SCSI disk
[ 5.789783][ T1] Freeing unused kernel memory: 1024K
[ 5.816904][ T1] Checked W+X mappings: passed, no W+X pages found
[ 5.822805][ T1] Run /init as init process
Loading, please wait...
Starting version 241
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[ 20.727998][ T1490] process '/usr/bin/fstype' started with executable stack
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext3 (1) -- /dev/sda1] fsck.ext3 -a -C0 /dev/sda1
[ 21.259049][ C0] random: fast init done
rootfs: clean, 28904/488640 files, 381661/1953536 blocks
done.
[ 21.442952][ T1500] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[ 21.829215][ T1500] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.93 booting
[info] Using makefile-style concurrent boot in runlevel S.
[ ok ] Starting hotplug events dispatcher: systemd-udevd.
[ ok ] Synthesizing the initial hotplug events (subsystems)...done.
[ ok ] Synthesizing the initial hotplug events (devices)...done.
[....] Waiting for /dev to be fully populated...[ 29.782256][ T1691] systemd-udevd[1691]: Using default interface naming scheme 'v240'.
[ 29.888383][ T1691] systemd-udevd[1691]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[ 30.032276][ T1691] systemd-udevd[1691]: Could not generate persistent MAC address for eth0: No such file or directory
[ 30.084046][ T1715] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 30.507011][ C0] random: crng init done
[ 30.531118][ T1695] systemd-udevd[1695]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[ 30.558662][ T1693] systemd-udevd[1693]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[ 30.576085][ T1692] systemd-udevd[1692]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[ 30.648419][ T1695] systemd-udevd[1695]: Could not generate persistent MAC address for ip6tnl0: No such file or directory
done.
[ ok ] Setting hostname to 'Neutron'...done.
[ ok ] Activating swap:.
[ 36.215097][ T1904] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[warn] Creating compatibility symlink from /etc/mtab to /proc/mounts. ... (warning).
[info] Will now check all file systems.
fsck from util-linux 2.33.1
Checking all file systems.
LABEL=rootfs is mounted
[....] Done checking file systems. A log is being saved in /var/log/fsck/checkfs[ ok hat location is writable..
[ ok ] Cleaning up temporary files...[....] Cleaning /tmp...done.
[ ok .
[ ok ] Will now mount local filesystems:.
[ ok ] Will now activate swapfile swap:done.
[ ok ] Checking minimum space in /tmp...done.
[ ok ] Cleaning up temporary files....
[ ok ] Starting Setting kernel variables: sysctl.
[ ok ] Initializing random number generator...done.
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
[ 42.825915][ T2457] mvneta d0074000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL)
[ 42.835945][ T2457] mvneta d0074000.ethernet eth0: configuring for phy/rgmii-id link mode
Listening on LPF/eth0/e6:55:af:58:54:99
Sending on LPF/eth0/e6:55:af:58:54:99
Sending on Socket/fallback
DHCPREQUEST for 192.168.2.112 on eth0 to 255.255.255.255 port 67
[ 44.905464][ T2458] mvneta d0074000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 44.913689][ T2458] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DHCPREQUEST for 192.168.2.112 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.2.112 from 192.168.2.1
bound to 192.168.2.112 -- renewal in 21332 seconds.
done.
[ ok ] Starting RPC port mapper daemon: rpcbind.
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
2677 (syslogd)
. ok
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
2704 (klogd)
. ok
[ ok ] Starting fan speed regulator: fancontrol.
[ ok ] Starting Glances server: glances .
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting periodic command scheduler: cron.
[ ok ] Starting system message bus: dbus.
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[....] Running local boot scripts (/etc/rc.local)[ 67.116604][ T3178] Setting Persistent MAC address to 00:50:43:00:02:02
<13>Jan 6 15:42:06 root[3185]: Setting Persistent MAC address to 00:50:43:00:02:02
Killed old client process
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/e6:55:af:58:54:99
Sending on LPF/eth0/e6:55:af:58:54:99
Sending on Socket/fallback
DHCPRELEASE of 192.168.2.112 on eth0 to 192.168.2.1 port 67
[ 68.677847][ T2458] mvneta d0074000.ethernet eth0: Link is Down
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
[ 69.417490][ T3226] mvneta d0074000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL)
[ 69.437126][ T3226] mvneta d0074000.ethernet eth0: configuring for phy/rgmii-id link mode
Listening on LPF/eth0/00:50:43:00:02:02
Sending on LPF/eth0/00:50:43:00:02:02
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
[ 71.548518][ T2458] mvneta d0074000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 71.556747][ T2458] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 192.168.2.112 from 192.168.2.1
DHCPREQUEST for 192.168.2.112 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.2.112 from 192.168.2.1
bound to 192.168.2.112 -- renewal in 19205 seconds.
. ok
Debian GNU/Linux 10 Neutron ttyS0
Neutron login: root
Password:
Last login: Thu Feb 14 02:13:04 PST 2019 on ttyS0
Linux Neutron 5.8.5-mvebu-370xp-tld-1 #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Neutron
192.168.2.112
NETGEAR ReadyNAS 102
Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020
Debian 10.5
Thu Jan 6 15:42:22 PST 2000 up 1 minute
root@Neutron:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 37.3G 0 disk
`-sda1 8:1 0 37.3G 0 part /
mtdblock0 31:0 0 1.5M 0 disk
mtdblock1 31:1 0 128K 0 disk
mtdblock2 31:2 0 6M 0 disk
mtdblock3 31:3 0 4M 0 disk
mtdblock4 31:4 0 116M 0 disk
root@Neutron:~#
Also tested my stress command with this config; i am pretty sure it is solved.`Insert happy smile face emoji here.`
I also tested with my junkyard mSATA disk which is shinedisk branded JMF605 controller and Intel NAND based disk but it cannot detected by u-boot.Maybe better branded disks will work.
Even with my old SATA II drive it is way way more faster booting rather than USB.
Regards
Edit
Attached mSATA photos in post.
Edited 1 time(s). Last edit at 09/30/2020 06:52AM by whitepawn.
|
Re: Debian on Netgear RN102 September 30, 2020 01:40PM |
Registered: 6 years ago Posts: 157 |
|
Re: Debian on Netgear RN102 September 30, 2020 04:41PM |
Admin Registered: 13 years ago Posts: 18,543 |
whitepawn,
> Also tested my stress command with this config; i
> am pretty sure it is solved.`Insert happy smile
> face emoji here.`
Congrats :)
> I also tested with my junkyard mSATA disk which is
> shinedisk branded JMF605 controller and Intel NAND
> based disk but it cannot detected by u-boot.Maybe
> better branded disks will work.
That's not unusual. Old stock u-boots don't know about new SSDs. From time to time we see this. Even with new u-boot, some SSD can not be detected during boot by u-boot. In those cases, they still can be the rootfs, but the kernel files must either be on flash, USB, SD, NFS, TFTP, or other SATA disk.
OK. So I guess it is time to revise the u-boot envs for real. I'll extract my envs settings from Kirkwood u-boot and marry that to the current envs for this RN102. Will post that when I have some free time.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Also tested my stress command with this config; i
> am pretty sure it is solved.`Insert happy smile
> face emoji here.`
Congrats :)
> I also tested with my junkyard mSATA disk which is
> shinedisk branded JMF605 controller and Intel NAND
> based disk but it cannot detected by u-boot.Maybe
> better branded disks will work.
That's not unusual. Old stock u-boots don't know about new SSDs. From time to time we see this. Even with new u-boot, some SSD can not be detected during boot by u-boot. In those cases, they still can be the rootfs, but the kernel files must either be on flash, USB, SD, NFS, TFTP, or other SATA disk.
OK. So I guess it is time to revise the u-boot envs for real. I'll extract my envs settings from Kirkwood u-boot and marry that to the current envs for this RN102. Will post that when I have some free time.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 02, 2020 06:28AM |
Registered: 6 years ago Posts: 157 |
Hi bodhi and whitepawn,
I have modified my eSATAp to SATA adapter cable so that 5 V power is provided from an external power supply. 3.3 V and 12 V pins are unconnected. The disk is powered up before the box. A HGST 1 TB HDD from April 2017 spinned up immediately when powered up. Here is the log:
And here the same with an Intel 160 GB SSD from September 2011:
eSATA booting from this SSD succeeded, but not without hick-ups. I carefully followed the posted procedures, created a root file system, modified 6 U-Boot environment variables and tried booting from the SSD. Loading 'uImage' and 'uInitrd' succeeded, uncompressing Linux succeeded, but Linux consistently failed 5.8 s into kernel boot with the error message "Gave up waiting for root file system device', and then dropped to 'initramfs' shell:
Then a followed exactly the same procedure with another Intel SSD. It has half the capasity (80 GB) and is 18 months older (March 2010). With this SSD attached to the rear eSATA connector my box successfully booted!
With Debian still running on the box, I hot plugged the first SSD into slot 1 and did:
I shut down the box again, attached the SSD to my PC, expanded the primary partition from 80 to 160 GB with 'gparted', reattached it to the rear eSATA connector, updated the U-Boot environment and booted again. Success!
I verified that also my second RN102, which still runs non-tampered stock firmware, could boot from the second (80 GB) SSD when connected to the rear eSATA port. Then I tried with an SSD in slot 1, but even with the modified environment, stock U-Boot failed to find it. However, when the Linux 5.8.5 kernel after some 9 s swaps its 'initramfs' for a real root file system, it prefers the one in slot 1 over the one attached to the rear eSATA connector, if there is a partition labeled 'rootfs' in both places.
When booting from a disk attached to the rear eSATA disk, this disk becomes '/dev/sda' and the disks in the slots become '/dev/sdb' and, it there are two, '/dev/sdc'. As whitepawn observed, this requires a modification to the '/etc/rc.local' script to make the sata1 and sata2 LEDs indicate activity for the disks in slot 1 and slot 2.
I'm delighted that booting from an SSD attached to the rear eSATA port works. To me this is optimal. Root file system on SSD is faster than on any USB stick, the front USB connector is left free for other usages, and the front disk compartment door may be opened at any time to hot swap disks.
I look forward to flash bodhi's "official" RN102 U-Boot environment variables. Thanks a lot, both of you!
Regards,
Trond Melen
Quote
Also in u-boot console, attach an HDD to to eSATA port, and try both of these commands, one of them should initialize all the SATA disks in the system.
I have modified my eSATAp to SATA adapter cable so that 5 V power is provided from an external power supply. 3.3 V and 12 V pins are unconnected. The disk is powered up before the box. A HGST 1 TB HDD from April 2017 spinned up immediately when powered up. Here is the log:
Power On!
FDT loaded successfully
Hit any key to stop autoboot: 0
Marvell>> version
U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1
06/23/2015 ReadyNAS-102 V2.0
arm-marvell-linux-gnueabi-gcc (Linaro GCC branch-4.6.4. Marvell GCC Dev 201310-2126.3d181f66 64K MAXPAGESIZE ALIGN) 4.6.4
GNU ld (Linaro GCC branch-4.6.4. Marvell GCC Dev 201310-2126.3d181f66 64K MAXPAGESIZE ALIGN) 2.22.0.20120801
Marvell>> scsi reset
Reset SCSI
Error: SCSI Controller(s) 1B4B:9215 not found
scanning bus for devices...
Found 0 device(s).
Marvell>> ide reset
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Device 0 @ 0 0:
Model: HGST HTS721010A9E630 Firm: JB0OA3W0 Ser#: JR1000BN1TYGEE
Type: Hard Disk
Supports 48-bit addressing
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
Marvell>> ide info
IDE device 0: Model: HGST HTS721010A9E630 Firm: JB0OA3W0 Ser#: JR1000BN1TYGEE
Type: Hard Disk
Supports 48-bit addressing
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
Marvell>>
And here the same with an Intel 160 GB SSD from September 2011:
Power On!
FDT loaded successfully
Hit any key to stop autoboot: 0
Marvell>> scsi reset
Reset SCSI
Error: SCSI Controller(s) 1B4B:9215 not found
scanning bus for devices...
Found 0 device(s).
Marvell>> ide reset
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Device 0 @ 0 0:
Model: INTEL SSDSA2BW160G3L Firm: 4PC1LE04 Ser#: CVPR138505ZV160DGN
Type: Hard Disk
Supports 48-bit addressing
Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)
Marvell>> ide info
IDE device 0: Model: INTEL SSDSA2BW160G3L Firm: 4PC1LE04 Ser#: CVPR138505ZV160DGN
Type: Hard Disk
Supports 48-bit addressing
Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)
Marvell>>
So, stock U-Boot handles both HDDs and SSDs connected to rear the eSATA port as IDE devices. whitepawn succeeded in eSATA booting from a HHD, but his box failed to boot from a mSATA SSD.
eSATA booting from this SSD succeeded, but not without hick-ups. I carefully followed the posted procedures, created a root file system, modified 6 U-Boot environment variables and tried booting from the SSD. Loading 'uImage' and 'uInitrd' succeeded, uncompressing Linux succeeded, but Linux consistently failed 5.8 s into kernel boot with the error message "Gave up waiting for root file system device', and then dropped to 'initramfs' shell:
Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000][ T0] Booting Linux on physical CPU 0x0 [ 0.000000][ T0] Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020 [ 0.000000][ T0] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d [ 0.000000][ T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000][ T0] OF: fdt: Machine model: NETGEAR ReadyNAS 102 [ 0.000000][ T0] printk: bootconsole [earlycon0] enabled [ 0.000000][ T0] Memory policy: Data cache writeback [ 0.000000][ T0] Zone ranges: [ 0.000000][ T0] Normal [mem 0x0000000000000000-0x000000001fffffff] [ 0.000000][ T0] HighMem empty [ 0.000000][ T0] Movable zone start for each node [ 0.000000][ T0] Early memory node ranges [ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x000000001fffffff] [ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff] [ 0.000000][ T0] CPU: All CPU(s) started in SVC mode. [ 0.000000][ T0] percpu: Embedded 20 pages/cpu s53068 r8192 d20660 u81920 [ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 130048 [ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102 [...] [ 5.732569][ T1] Run /init as init process [ 5.776604][ T20] usb 1-1: New USB device found, idVendor=7825, idProduct=a2a4, bcdDevice=41.01 [ 5.789327][ T20] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Loading, please wait... [ 5.802693][ T20] usb 1-1: Product: Best USB Device [ 5.812793][ T20] usb 1-1: Manufacturer: ULT-Best [ 5.823081][ T20] usb 1-1: SerialNumber: 235678C218CA Starting version 241 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! LABEL=rootfs does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs)I disconnected power, disconnected the SSD and attched it to my PC using a USB to SATA adapter cable and did
# fsck.ext3 -v /dev/sdb1 e2fsck 1.45.5 (07-Jan-2020) rootfs: clean, 24109/9773056 files, 1076434/39072256 blocks'fsck' checked the filesystem and found nothing to repair.
Then a followed exactly the same procedure with another Intel SSD. It has half the capasity (80 GB) and is 18 months older (March 2010). With this SSD attached to the rear eSATA connector my box successfully booted!
# uname -a Linux debian 5.8.5-mvebu-370xp-tld-1 #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020 armv7l GNU/LinuxSo, I could reproduce whitepawn's result, even with SSD rather than HDD :-) . Boot time (with random MAC address) from 'boot' command to 'login' promt was 69 s.
With Debian still running on the box, I hot plugged the first SSD into slot 1 and did:
# dd if=/dev/sda1 of=/dev/sdb1 bs=64MB status=progress 80025223168 bytes (80 GB, 75 GiB) copied, 1618 s, 49.5 MB/s 1250+1 records in 1250+1 records out 80025223168 bytes (80 GB, 75 GiB) copied, 1618.33 s, 49.4 MB/sAfter half an hour, I could shut down the box, attach the first SSD to the rear eSATA connector, update the U-Boot environment and reboot. This time boot succeeded! The only explanation I can think of is that this disk may have been severely damaged by the stress test 2 weeks ago and that 'dd' repaired it, but to me this makes little sense.
I shut down the box again, attached the SSD to my PC, expanded the primary partition from 80 to 160 GB with 'gparted', reattached it to the rear eSATA connector, updated the U-Boot environment and booted again. Success!
I verified that also my second RN102, which still runs non-tampered stock firmware, could boot from the second (80 GB) SSD when connected to the rear eSATA port. Then I tried with an SSD in slot 1, but even with the modified environment, stock U-Boot failed to find it. However, when the Linux 5.8.5 kernel after some 9 s swaps its 'initramfs' for a real root file system, it prefers the one in slot 1 over the one attached to the rear eSATA connector, if there is a partition labeled 'rootfs' in both places.
When booting from a disk attached to the rear eSATA disk, this disk becomes '/dev/sda' and the disks in the slots become '/dev/sdb' and, it there are two, '/dev/sdc'. As whitepawn observed, this requires a modification to the '/etc/rc.local' script to make the sata1 and sata2 LEDs indicate activity for the disks in slot 1 and slot 2.
I'm delighted that booting from an SSD attached to the rear eSATA port works. To me this is optimal. Root file system on SSD is faster than on any USB stick, the front USB connector is left free for other usages, and the front disk compartment door may be opened at any time to hot swap disks.
I look forward to flash bodhi's "official" RN102 U-Boot environment variables. Thanks a lot, both of you!
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 October 02, 2020 10:58AM |
Registered: 6 years ago Posts: 157 |
Hi bodhi and whitepawn,
Not much of a mystery, actually. The size of the 'mtd0' partition is 1.5 MiB and more that the first 0x80000 B (512 KiB) are used by the U-Boot image:
Whithout the '-l' option, the full partition is stored and 'kwboot -p' works:
This image is larger than it have to be, but UART boot finished in 152 s, which I find acceptable. 'hexdump' may be used to find a good value for the '-l' (length) option:
'binwalk' can verify that the image is complete:
Regards,
Trond Melen
EDIT: Typos only. :TIDE
Edited 1 time(s). Last edit at 10/02/2020 11:01AM by tme.
Quote
myself
'backup.mtd0' was created by the command
nanddump --noecc --omitoob -l 0x80000 -f backup.mtd0 /dev/mtd0Why isn't this image suited for 'kwboot -p'?
Not much of a mystery, actually. The size of the 'mtd0' partition is 1.5 MiB and more that the first 0x80000 B (512 KiB) are used by the U-Boot image:
# cat /proc/mtd dev: size erasesize name mtd0: 00180000 00020000 "u-boot" mtd1: 00020000 00020000 "u-boot-env" mtd2: 00600000 00020000 "uImage" mtd3: 00400000 00020000 "minirootfs" mtd4: 07400000 00020000 "ubifs"
Whithout the '-l' option, the full partition is stored and 'kwboot -p' works:
# nanddump -f backup.mtd0 /dev/mtd0 ECC failed: 0 ECC corrected: 0 Number of bad blocks: 0 Number of bbt blocks: 0 Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x00180000... # ls -alFh backup.mtd0 -rw-r--r-- 1 root root 1.5M Oct 2 03:46 backup.mtd0
This image is larger than it have to be, but UART boot finished in 152 s, which I find acceptable. 'hexdump' may be used to find a good value for the '-l' (length) option:
# hexdump backup.mtd0 | tail 00d75e0 6c6c 702c 6963 2d65 6f70 7472 6d00 7261 00d75f0 6576 6c6c 702c 6963 2d65 616c 656e 6400 00d7600 6665 7561 746c 732d 6174 6574 6c00 6e69 00d7610 7875 632c 646f 0065 0a0a 0a0a 0a0a 0a0a 00d7620 0a0a 0a0a 0a0a 0a0a 0a0a 0a0a 0a0a 0a0a * 00d9f10 0a0a 0a0a 4783 d19c ffff ffff ffff ffff 00d9f20 ffff ffff ffff ffff ffff ffff ffff ffff * 0180000
'binwalk' can verify that the image is complete:
# apt install -y binwalk lzop # binwalk -Me backup.mtd0 Scan Time: 2020-10-02 03:53:32 Target File: /tmp/backup.mtd0 MD5 Checksum: 01d70962932cd5c0ebabc233b4d1bb08 Signatures: 386 DECIMAL HEXADECIMAL DESCRIPTION -------------------------------------------------------------------------------- 600340 0x92914 device tree image (dtb) 608589 0x9494D Certificate in DER format (x509 v3), header length: 4, sequence length: 1284 608705 0x949C1 Certificate in DER format (x509 v3), header length: 4, sequence length: 1288 662640 0xA1C70 CRC32 polynomial table, little endian 667340 0xA2ECC CRC32 polynomial table, little endian 671327 0xA3E5F LZO compressed data 868352 0xD4000 device tree image (dtb)
Regards,
Trond Melen
EDIT: Typos only. :TIDE
Edited 1 time(s). Last edit at 10/02/2020 11:01AM by tme.
|
Re: Debian on Netgear RN102 October 02, 2020 02:51PM |
Admin Registered: 13 years ago Posts: 18,543 |
Good works Trond!
This does not make sense, if I understood it correctly. The 2 internal SATA slots drive assignment should not have anything to do with the LEDs.
With all 3 disks inserted,
And also a question: is there a LED next to the eSATA port?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
When booting from a disk attached to the rear eSATA disk, this disk becomes '/dev/sda' and the disks in the slots become '/dev/sdb' and, it there are two, '/dev/sdc'. As whitepawn observed, this requires a modification to the '/etc/rc.local' script to make the sata1 and sata2 LEDs indicate activity for the disks in slot 1 and slot 2.
This does not make sense, if I understood it correctly. The 2 internal SATA slots drive assignment should not have anything to do with the LEDs.
With all 3 disks inserted,
lsblk cat /sys/class/leds/rn102:blue:sata1/trigger
And also a question: is there a LED next to the eSATA port?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 02, 2020 03:18PM |
Registered: 6 years ago Posts: 157 |
Hi bodhi,
You are right. I was right about the '/dev/sd?1', but wrong about the LEDs. Here, initially, the only disk is attached to the eSATA connector, then a HHD is hot inserted into slot 1, an then another one into slot 2:
What pushed me towards the wrong conclusion is that with no disks in slot 1 nor slot 2, the Sata1 LED is on during eSATA disk activity. Maybe the Backup LED should be given this task???
No, the only LEDs at the rear side of RN102 are the two on the Ethernet connector.
Regards,
Trond Melen
EDIT: Clearification. :TIDE
Edited 1 time(s). Last edit at 10/02/2020 03:21PM by tme.
You are right. I was right about the '/dev/sd?1', but wrong about the LEDs. Here, initially, the only disk is attached to the eSATA connector, then a HHD is hot inserted into slot 1, an then another one into slot 2:
root@debian:/tmp# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149.1G 0 disk `-sda1 8:1 0 149.1G 0 part / mtdblock0 31:0 0 1.5M 0 disk mtdblock1 31:1 0 128K 1 disk mtdblock2 31:2 0 6M 0 disk mtdblock3 31:3 0 4M 0 disk mtdblock4 31:4 0 116M 0 disk root@debian:/tmp# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149.1G 0 disk `-sda1 8:1 0 149.1G 0 part / sdb 8:16 1 1.8T 0 disk `-sdb1 8:17 1 1.8T 0 part mtdblock0 31:0 0 1.5M 0 disk mtdblock1 31:1 0 128K 1 disk mtdblock2 31:2 0 6M 0 disk mtdblock3 31:3 0 4M 0 disk mtdblock4 31:4 0 116M 0 disk root@debian:/tmp# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149.1G 0 disk `-sda1 8:1 0 149.1G 0 part / sdb 8:16 1 1.8T 0 disk `-sdb1 8:17 1 1.8T 0 part sdc 8:32 1 1.8T 0 disk `-sdc1 8:33 1 1.8T 0 part mtdblock0 31:0 0 1.5M 0 disk mtdblock1 31:1 0 128K 1 disk mtdblock2 31:2 0 6M 0 disk mtdblock3 31:3 0 4M 0 disk mtdblock4 31:4 0 116M 0 disk root@debian:/tmp# cat /sys/class/leds/rn102:blue:sata1/trigger none usb-gadget usb-host rc-feedback kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport timer oneshot disk-activity disk-read disk-write [ide-disk1] ide-disk2 mtd nand-disk heartbeat gpio default-on flash torch panic d0072004.mdio-mii:00:link d0072004.mdio-mii:00:1Gbps d0072004.mdio-mii:00:100Mbps d0072004.mdio-mii:00:10Mbps root@debian:/tmp# dd if=/dev/sdb1 of=/dev/null ^C 237757+0 records in 237756+0 records out 121731072 bytes (122 MB, 116 MiB) copied, 2.66043 s, 45.8 MB/s root@debian:/tmp# dd if=/dev/sdc1 of=/dev/null ^C 211617+0 records in 211617+0 records out 108347904 bytes (108 MB, 103 MiB) copied, 2.43362 s, 44.5 MB/sWhile 'dd' was running, the correct LED was activated.
What pushed me towards the wrong conclusion is that with no disks in slot 1 nor slot 2, the Sata1 LED is on during eSATA disk activity. Maybe the Backup LED should be given this task???
No, the only LEDs at the rear side of RN102 are the two on the Ethernet connector.
Regards,
Trond Melen
EDIT: Clearification. :TIDE
Edited 1 time(s). Last edit at 10/02/2020 03:21PM by tme.
|
Re: Debian on Netgear RN102 October 02, 2020 03:26PM |
Admin Registered: 13 years ago Posts: 18,543 |
Quote
What pushed me towards the wrong conclusion is that with no disks in slot 1 nor slot 2, the Sata1 LED is on during disk activity. Maybe the Backup LED should be given this task???
I see. That behavior is kind of make sense. That might be becasue the eSATA port triggered same activity internally as SATA1. If that is the case, then we cannot reassign. But let me reread the DTS again to see anything stand out.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 07, 2020 03:01AM |
Registered: 4 years ago Posts: 73 |
@tme,
In my case i soldered old SATA power connector 5v pins directly to front usb power lines.Since my HDD draws only 0.4 amps during load i think it will be fine.I also mounted disk inside case between CPU heatsink and box chasis I had to sandpaper heatsink because it is was very thight fit.I didn't want to apply unnecessary stress to heatsink and cpu.As mentioned before SATA data pins are directly soldered to daughter board.Also SATA data cable is wrapped with sticky aluminium tape and after that i wrapped it with masking tape to prevent short circuit.So bootdrive is inside the box.
Have a question for you:What file sharing protocol do you use?I have tried SMB and NFS but SMB gets 15-16 mb/s and NFS gets 19-20mb/s with gigabit cable connection and BTRFS file system with SATA III drive in bay 1.I think i must get minimum 80-85 mb/s.When i transfer files CPU gets 95-100 load and bottleneck i believe.I have checked it with nmon both NFS 3 and NFS 4 with async options no luck.
Regards.
Quote
tme
I have modified my eSATAp to SATA adapter cable so that 5 V power is provided from an external power supply. 3.3 V and 12 V pins are unconnected.
In my case i soldered old SATA power connector 5v pins directly to front usb power lines.Since my HDD draws only 0.4 amps during load i think it will be fine.I also mounted disk inside case between CPU heatsink and box chasis I had to sandpaper heatsink because it is was very thight fit.I didn't want to apply unnecessary stress to heatsink and cpu.As mentioned before SATA data pins are directly soldered to daughter board.Also SATA data cable is wrapped with sticky aluminium tape and after that i wrapped it with masking tape to prevent short circuit.So bootdrive is inside the box.
Have a question for you:What file sharing protocol do you use?I have tried SMB and NFS but SMB gets 15-16 mb/s and NFS gets 19-20mb/s with gigabit cable connection and BTRFS file system with SATA III drive in bay 1.I think i must get minimum 80-85 mb/s.When i transfer files CPU gets 95-100 load and bottleneck i believe.I have checked it with nmon both NFS 3 and NFS 4 with async options no luck.
Regards.
|
Re: Debian on Netgear RN102 October 07, 2020 09:14PM |
Admin Registered: 13 years ago Posts: 18,543 |
whitepawn,
Check the Wiki thread.
And then check your settings against:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Check the Wiki thread.
Quote
Benchmarks
Pogo ProV3 vs Pogo E02
Another Pogo Pro V3 benchmarks
Network performance - SAMBA - NFS (various protocols)
Pogo Pro V3 Network NFS benchmarks
Kirkwood vs OXNAS network performance (with flow control)
Kirkwood vs OXNAS network performance (flow control turned off )
OXNAS vs OXNAS network performance (flow control turned off)
And then check your settings against:
Quote
Samba
Samba smb.conf for a simple set up
HowTo setup Samba/CIFS shares
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 08, 2020 12:41PM |
Registered: 4 years ago Posts: 73 |
Bodhi,
I have tried some below:
Sysbench memory and CPU test:
Ethtool information both nas and linux client:
İperf results:
My connection scheme is like this:
I tried with different cables and different ports on router no effect at all.Also i freshly installed kernel and rootfs to test so i am completely stock just apt update and apt upgraded no openmediavault or something.
I think i have a network problem rather than HDD read or something, while doing iperf test CPU usage was 90-98 percent is this load normal with 200Mbits per second?
Any advice to test?
I have tried some below:
Sysbench memory and CPU test:
root@neutron:~# sysbench --test=memory --memory-block-size=512K --memory-total-size=512M run
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Doing memory operations speed test
Memory block size: 512K
Memory transfer size: 512M
Memory operations type: write
Memory scope type: global
Threads started!
Done.
Operations performed: 1024 ( 1508.34 ops/sec)
512.00 MB transferred (754.17 MB/sec)
Test execution summary:
total time: 0.6789s
total number of events: 1024
total time taken by event execution: 0.6741
per-request statistics:
min: 0.63ms
avg: 0.66ms
max: 4.52ms
approx. 95 percentile: 0.68ms
Threads fairness:
events (avg/stddev): 1024.0000/0.00
execution time (avg/stddev): 0.6741/0.00
root@neutron:~#
root@neutron:~# sysbench --test=cpu --cpu-max-prime=2000 --num-threads=2 run
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 2
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 2000
Test execution summary:
total time: 21.6869s
total number of events: 10000
total time taken by event execution: 43.3416
per-request statistics:
min: 2.12ms
avg: 4.33ms
max: 52.40ms
approx. 95 percentile: 12.18ms
Threads fairness:
events (avg/stddev): 5000.0000/0.00
execution time (avg/stddev): 21.6708/0.00
Ethtool information both nas and linux client:
jigsaw@whitepawn:~$ sudo ethtool enp8s0 [sudo] password for jigsaw: Settings for enp8s0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: d Wake-on: d Current message level: 0x000060e4 (24804) link ifup rx_err tx_err hw wol Link detected: yes jigsaw@whitepawn:~$ root@neutron:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: yes root@neutron:~#
İperf results:
jigsaw@whitepawn:~$ iperf -c 192.168.5.7 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to 192.168.5.7, TCP port 5001 TCP window size: 144 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.9 port 32990 connected with 192.168.5.7 port 5001 [ ID] Interval Transfer Bandwidth [ 5] 0.0-10.0 sec 214 MBytes 180 Mbits/sec ^Cjigsaw@whitepawn:~$ iperf -c 192.168.5.7 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to 192.168.5.7, TCP port 5001 TCP window size: 230 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.9 port 33018 connected with 192.168.5.7 port 5001 [ ID] Interval Transfer Bandwidth [ 5] 0.0-10.0 sec 214 MBytes 180 Mbits/sec root@neutron:~# iperf -c 192.168.5.9 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.7 port 5001 connected with 192.168.5.9 port 32990 connect failed: Operation now in progress [ ID] Interval Transfer Bandwidth [ 5] 0.0- 9.2 sec 214 MBytes 196 Mbits/sec root@neutron:~# iperf -c 192.168.5.9 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.7 port 5001 connected with 192.168.5.9 port 33018 connect failed: Operation now in progress [ ID] Interval Transfer Bandwidth [ 5] 0.0- 9.2 sec 214 MBytes 196 Mbits/sec root@neutron:~#
My connection scheme is like this:
Quote
Netgear RN102----Cat6 ethernet cable----Huawei Gigabit Router----Cat6 ethernet cable----Linux Mint Client
I tried with different cables and different ports on router no effect at all.Also i freshly installed kernel and rootfs to test so i am completely stock just apt update and apt upgraded no openmediavault or something.
I think i have a network problem rather than HDD read or something, while doing iperf test CPU usage was 90-98 percent is this load normal with 200Mbits per second?
Any advice to test?
|
Re: Debian on Netgear RN102 October 08, 2020 05:43PM |
Admin Registered: 13 years ago Posts: 18,543 |
whitepawn,
> I think i have a network problem rather than HDD
> read or something, while doing iperf test CPU
> usage was 90-98 percent is this load normal with
> 200Mbits per second?
Exactly. You do have a network problem, according to iperf tests.
Partly, this is something I forgot to complete in this MVEBU kernel/rootfs. As I recall, the NIC is running with flow control turned on. And that slows down the network speed substantially. Somehow in the mainline code, this is the default (unlike the Kirkwood kernel, which is always flow control off).
Thanks to you now I remmeber this issue :). I will look into this in the next MVEBU kernel release.
=====
The work around to get a better network speed is to turn flow control off using ethtool after the system has started.
(Adjust your network name below if necessary, i.e. eth0 or some other name ):
And rerun iperf tests. You should get better speed (such as 700Mbs), like in this benchmark:
https://forum.doozan.com/read.php?2,33321,33390#msg-33390
And then from there, if the network speed is significantly slower than 700 Mbs, you can track down other possible problems.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I think i have a network problem rather than HDD
> read or something, while doing iperf test CPU
> usage was 90-98 percent is this load normal with
> 200Mbits per second?
Exactly. You do have a network problem, according to iperf tests.
Partly, this is something I forgot to complete in this MVEBU kernel/rootfs. As I recall, the NIC is running with flow control turned on. And that slows down the network speed substantially. Somehow in the mainline code, this is the default (unlike the Kirkwood kernel, which is always flow control off).
Thanks to you now I remmeber this issue :). I will look into this in the next MVEBU kernel release.
=====
The work around to get a better network speed is to turn flow control off using ethtool after the system has started.
(Adjust your network name below if necessary, i.e. eth0 or some other name ):
ethtool -A eth0 rx off tx off
And rerun iperf tests. You should get better speed (such as 700Mbs), like in this benchmark:
https://forum.doozan.com/read.php?2,33321,33390#msg-33390
And then from there, if the network speed is significantly slower than 700 Mbs, you can track down other possible problems.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 09, 2020 04:57AM |
Registered: 4 years ago Posts: 73 |
Bodhi,
I have disabled both ethernet devices flow control on client(Linux Mint) and server(RN102).Still getting 200mbps on Netgear.I also unplugged and plugged ethernet cable after turning off flow control on both server and client sides.
Turned off both client and RN102 flow controls, this is my client side log, same applied on Netgear but i forget to get log but outputs are the same:
Then just to test my cables and router setup i tried with my another Xeon E3-V3 Linux Server which have ip 192.168.5.3. I just unplugged ethernet cable from RN102 and plugged on my xeon server.Didn't change anything except unplugging network cable from Netgear and pluging to xeon server:
It seems my network setup works ok but I have some issues with netgear config.
Any advice?
Thank you.
Edited 1 time(s). Last edit at 10/09/2020 05:00AM by whitepawn.
I have disabled both ethernet devices flow control on client(Linux Mint) and server(RN102).Still getting 200mbps on Netgear.I also unplugged and plugged ethernet cable after turning off flow control on both server and client sides.
Turned off both client and RN102 flow controls, this is my client side log, same applied on Netgear but i forget to get log but outputs are the same:
jigsaw@whitepawn:~$ sudo ethtool -a enp8s0 Pause parameters for enp8s0: Autonegotiate: on RX: on TX: on jigsaw@whitepawn:~$ sudo ethtool -A enp8s0 rx off tx off jigsaw@whitepawn:~$ sudo ethtool -a enp8s0 Pause parameters for enp8s0: Autonegotiate: on RX: off TX: off Same results: jigsaw@whitepawn:~$ iperf -c 192.168.5.7 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to 192.168.5.7, TCP port 5001 TCP window size: 204 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.9 port 51040 connected with 192.168.5.7 port 5001 [ ID] Interval Transfer Bandwidth [ 5] 0.0-10.0 sec 219 MBytes 184 Mbits/sec ^Cjigsaw@whitepawn:~$ iperf -c 192.168.5.7 -r connect failed: Connection refused ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ^Cjigsaw@whitepawn:~$ iperf -c 192.168.5.7 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to 192.168.5.7, TCP port 5001 TCP window size: 178 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.9 port 51048 connected with 192.168.5.7 port 5001 [ ID] Interval Transfer Bandwidth [ 5] 0.0-10.0 sec 230 MBytes 193 Mbits/sec
Then just to test my cables and router setup i tried with my another Xeon E3-V3 Linux Server which have ip 192.168.5.3. I just unplugged ethernet cable from RN102 and plugged on my xeon server.Didn't change anything except unplugging network cable from Netgear and pluging to xeon server:
Quote
Xeon Server----Cat6 ethernet cable----Huawei Gigabit Router----Cat6 ethernet cable----Linux Mint Client
jigsaw@whitepawn:~$ iperf -c 192.168.5.3 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to 192.168.5.3, TCP port 5001 TCP window size: 289 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.9 port 60754 connected with 192.168.5.3 port 5001 [ ID] Interval Transfer Bandwidth [ 5] 0.0-10.0 sec 1.09 GBytes 933 Mbits/sec ^Cjigsaw@whitepawn:~$ iperf -c 192.168.5.3 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to 192.168.5.3, TCP port 5001 TCP window size: 416 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.9 port 60756 connected with 192.168.5.3 port 5001 [ ID] Interval Transfer Bandwidth [ 5] 0.0-10.0 sec 1.09 GBytes 932 Mbits/sec ^Cjigsaw@whitepawn:~$
It seems my network setup works ok but I have some issues with netgear config.
Any advice?
Thank you.
Edited 1 time(s). Last edit at 10/09/2020 05:00AM by whitepawn.
|
Re: Debian on Netgear RN102 October 09, 2020 05:55AM |
Admin Registered: 13 years ago Posts: 18,543 |
whitepawn,
Let me do the test with my Thecus N2350 tomorrow and come back.
In the mean time, after turn off flow control on RN102, relist the settings :
ethtool eth0
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Let me do the test with my Thecus N2350 tomorrow and come back.
In the mean time, after turn off flow control on RN102, relist the settings :
ethtool eth0
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 09, 2020 03:05PM |
Registered: 4 years ago Posts: 73 |
Bodhi,
I gathered logs with dmesg:
In dmesg it automaticly disables flow control i guess.
Regards.
I gathered logs with dmesg:
root@neutron:~# ethtool -a eth0 Pause parameters for eth0: Autonegotiate: on RX: off TX: off RX negotiated: off TX negotiated: off root@neutron:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: yes root@neutron:~# iperf -c 192.168.5.9 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.3 port 5001 connected with 192.168.5.9 port 53920 connect failed: Operation now in progress [ ID] Interval Transfer Bandwidth [ 5] 0.0- 9.2 sec 233 MBytes 213 Mbits/sec root@neutron:~# iperf -c 192.168.5.9 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.3 port 5001 connected with 192.168.5.9 port 53934 connect failed: Operation now in progress [ ID] Interval Transfer Bandwidth [ 5] 0.0- 9.2 sec 221 MBytes 202 Mbits/sec root@neutron:~# iperf -c 192.168.5.9 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.5.3 port 5001 connected with 192.168.5.9 port 53950 connect failed: Operation now in progress [ ID] Interval Transfer Bandwidth [ 5] 0.0- 9.2 sec 218 MBytes 199 Mbits/sec root@neutron:~# root@neutron:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020 [ 0.000000] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] OF: fdt: Machine model: NETGEAR ReadyNAS 102 [ 0.000000] printk: bootconsole [earlycon0] enabled [ 0.000000] Memory policy: Data cache writeback [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x000000001fffffff] [ 0.000000] HighMem empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x000000001fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff] [ 0.000000] On node 0 totalpages: 131072 [ 0.000000] Normal zone: 1024 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 131072 pages, LIFO batch:31 [ 0.000000] CPU: All CPU(s) started in SVC mode. [ 0.000000] percpu: Embedded 20 pages/cpu s53068 r8192 d20660 u81920 [ 0.000000] pcpu-alloc: s53068 r8192 d20660 u81920 alloc=20*4096 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial init=/bin/systemd mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102 [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] Memory: 493132K/524288K available (10240K kernel code, 1012K rwdata, 3072K rodata, 1024K init, 342K bss, 31156K reserved, 0K cma-reserved, 0K highmem) [ 0.000000] random: get_random_u32 called from ____cache_alloc+0x338/0x794 with crng_init=0 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Rude variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C: DT/platform modifies aux control register: 0x12086300 -> 0x1a086302 [ 0.000000] Aurora cache controller enabled, 4 ways, 256 kB [ 0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302 [ 0.000000] Switching to timer-based delay loop, resolution 53ns [ 0.000007] sched_clock: 32 bits at 18MHz, resolution 53ns, wraps every 114537122277ns [ 0.007874] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 101938038664 ns [ 0.019295] Console: colour dummy device 80x30 [ 0.024015] Calibrating delay loop (skipped), value calculated using timer frequency.. 37.49 BogoMIPS (lpj=187492) [ 0.034144] pid_max: default: 32768 minimum: 301 [ 0.039208] LSM: Security Framework initializing [ 0.044156] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.051483] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.060280] CPU: Testing write buffer coherency: ok [ 0.065722] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.072050] Setting up static identity map for 0x100000 - 0x100060 [ 0.078740] mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1 [ 0.084172] mvebu-pmsu: Initializing Power Management Service Unit [ 0.090696] rcu: Hierarchical SRCU implementation. [ 0.098515] smp: Bringing up secondary CPUs ... [ 0.103405] smp: Brought up 1 node, 1 CPU [ 0.107701] SMP: Total of 1 processors activated (37.49 BogoMIPS). [ 0.114020] CPU: All CPU(s) started in SVC mode. [ 0.119564] devtmpfs: initialized [ 0.128171] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 [ 0.137094] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.146867] futex hash table entries: 256 (order: 2, 16384 bytes, linear) [ 0.154078] xor: measuring software checksum speed [ 0.258575] arm4regs : 1103.200 MB/sec [ 0.358572] 8regs : 671.200 MB/sec [ 0.458568] 32regs : 1062.400 MB/sec [ 0.463021] xor: using function: arm4regs (1103.200 MB/sec) [ 0.468786] prandom: seed boundary self test passed [ 0.477389] prandom: 100 self tests passed [ 0.481803] pinctrl core: initialized pinctrl subsystem [ 0.488939] thermal_sys: Registered thermal governor 'step_wise' [ 0.489679] NET: Registered protocol family 16 [ 0.502561] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.510456] audit: initializing netlink subsys (disabled) [ 0.516426] audit: type=2000 audit(0.490:1): state=initialized audit_enabled=0 res=1 [ 0.526700] cpuidle: using governor ladder [ 0.532720] cpuidle: using governor menu [ 0.537232] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.809516] raid6: int32x8 gen() 214 MB/s [ 0.978935] raid6: int32x8 xor() 135 MB/s [ 1.148650] raid6: int32x4 gen() 224 MB/s [ 1.318703] raid6: int32x4 xor() 151 MB/s [ 1.488587] raid6: int32x2 gen() 414 MB/s [ 1.658568] raid6: int32x2 xor() 217 MB/s [ 1.828600] raid6: int32x1 gen() 430 MB/s [ 1.998593] raid6: int32x1 xor() 201 MB/s [ 2.003124] raid6: using algorithm int32x1 gen() 430 MB/s [ 2.008696] raid6: .... xor() 201 MB/s, rmw enabled [ 2.013781] raid6: using intx1 recovery algorithm [ 2.020115] vgaarb: loaded [ 2.025084] SCSI subsystem initialized [ 2.030023] libata version 3.00 loaded. [ 2.030355] usbcore: registered new interface driver usbfs [ 2.036053] usbcore: registered new interface driver hub [ 2.043248] usbcore: registered new device driver usb [ 2.049968] mc: Linux media interface: v0.10 [ 2.055395] videodev: Linux video capture interface: v2.00 [ 2.061879] pps_core: LinuxPPS API ver. 1 registered [ 2.067048] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 2.076795] PTP clock support registered [ 2.084632] clocksource: Switched to clocksource armada_370_xp_clocksource [ 3.073726] VFS: Disk quotas dquot_6.6.0 [ 3.078110] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 3.115581] NET: Registered protocol family 2 [ 3.121514] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) [ 3.130283] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear) [ 3.138252] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 3.145541] TCP: Hash tables configured (established 4096 bind 4096) [ 3.152536] UDP hash table entries: 256 (order: 1, 8192 bytes, linear) [ 3.159350] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear) [ 3.166589] NET: Registered protocol family 1 [ 3.171980] RPC: Registered named UNIX socket transport module. [ 3.178123] RPC: Registered udp transport module. [ 3.183051] RPC: Registered tcp transport module. [ 3.187998] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 3.194515] PCI: CLS 0 bytes, default 64 [ 3.199133] Trying to unpack rootfs image as initramfs... [ 3.842552] Freeing initrd memory: 9756K [ 3.847182] NetWinder Floating Point Emulator V0.97 (double precision) [ 3.854077] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available [ 3.865145] Initialise system trusted keyrings [ 3.869884] Key type blacklist registered [ 3.876466] workingset: timestamp_bits=30 max_order=17 bucket_order=0 [ 3.883108] zbud: loaded [ 3.887808] NFS: Registering the id_resolver key type [ 3.893086] Key type id_resolver registered [ 3.898011] Key type id_legacy registered [ 3.902333] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 3.909259] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 3.916125] jffs2: version 2.2. (NAND) (SUMMARY) \xc2\xa9 2001-2006 Red Hat, Inc. [ 3.924299] orangefs_debugfs_init: called with debug mask: :none: :0: [ 3.931262] orangefs_init: module version upstream loaded [ 4.008836] async_tx: api initialized (async) [ 4.013467] Key type asymmetric registered [ 4.017915] Asymmetric key parser 'x509' registered [ 4.023348] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 4.030976] io scheduler bfq registered [ 4.038028] armada-370-pinctrl d0018000.pin-ctrl: registered pinctrl driver [ 4.054958] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00 [ 4.061725] pci_bus 0000:00: root bus resource [bus 00-ff] [ 4.067921] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff] [ 4.075199] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff] [ 4.081561] pci_bus 0000:00: scanning bus [ 4.081710] pci 0000:00:01.0: [11ab:6710] type 01 class 0x060400 [ 4.088062] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref] [ 4.095497] pci 0000:00:02.0: [11ab:6710] type 01 class 0x060400 [ 4.101648] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref] [ 4.110118] pci_bus 0000:00: fixups for bus [ 4.110139] PCI: bus0: Fast back to back transfers disabled [ 4.116080] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0 [ 4.116089] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 4.124040] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0 [ 4.124047] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 4.132120] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1 [ 4.132424] pci_bus 0000:01: scanning bus [ 4.132476] pci 0000:01:00.0: [1b4b:9170] type 00 class 0x010601 [ 4.138841] pci 0000:01:00.0: reg 0x10: [io 0xfffffff8-0xffffffff] [ 4.145318] pci 0000:01:00.0: reg 0x14: [io 0xfffffffc-0xffffffff] [ 4.151682] pci 0000:01:00.0: reg 0x18: [io 0xfffffff8-0xffffffff] [ 4.158141] pci 0000:01:00.0: reg 0x1c: [io 0xfffffffc-0xffffffff] [ 4.164505] pci 0000:01:00.0: reg 0x20: [io 0xfffffff0-0xffffffff] [ 4.170929] pci 0000:01:00.0: reg 0x24: [mem 0x40000000-0x400001ff] [ 4.177355] pci 0000:01:00.0: reg 0x30: [mem 0xd0000000-0xd000ffff pref] [ 4.184130] pci 0000:01:00.0: Enabling fixed DMA alias to 00.1 [ 4.190203] pci 0000:01:00.0: PME# supported from D3hot [ 4.195663] pci 0000:01:00.0: PME# disabled [ 4.196113] pci 0000:00:01.0: ASPM: current common clock configuration is inconsistent, reconfiguring [ 4.235716] pci_bus 0000:01: fixups for bus [ 4.235731] PCI: bus1: Fast back to back transfers disabled [ 4.241458] pci_bus 0000:01: bus scan returning with max=01 [ 4.241470] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 4.248231] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1 [ 4.248530] pci_bus 0000:02: scanning bus [ 4.248570] pci 0000:02:00.0: [1b73:1009] type 00 class 0x0c0330 [ 4.254922] pci 0000:02:00.0: reg 0x10: [mem 0x42000000-0x4200ffff 64bit] [ 4.261768] pci 0000:02:00.0: reg 0x18: [mem 0x42010000-0x42010fff 64bit] [ 4.268716] pci 0000:02:00.0: reg 0x20: [mem 0x42011000-0x42011fff 64bit] [ 4.275721] pci 0000:02:00.0: supports D1 [ 4.280020] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold [ 4.286518] pci 0000:02:00.0: PME# disabled [ 4.286980] pci 0000:00:02.0: ASPM: current common clock configuration is inconsistent, reconfiguring [ 4.325708] pci_bus 0000:02: fixups for bus [ 4.325723] PCI: bus2: Fast back to back transfers disabled [ 4.331449] pci_bus 0000:02: bus scan returning with max=02 [ 4.331461] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02 [ 4.338215] pci_bus 0000:00: bus scan returning with max=02 [ 4.338287] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff] [ 4.345260] pci 0000:00:02.0: BAR 14: assigned [mem 0xf8100000-0xf81fffff] [ 4.352173] pci 0000:00:01.0: BAR 13: assigned [io 0x10000-0x10fff] [ 4.358660] pci 0000:00:01.0: BAR 6: assigned [mem 0xf8200000-0xf82007ff pref] [ 4.365913] pci 0000:00:02.0: BAR 6: assigned [mem 0xf8300000-0xf83007ff pref] [ 4.373150] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8000000-0xf800ffff pref] [ 4.380399] pci 0000:01:00.0: BAR 5: assigned [mem 0xf8010000-0xf80101ff] [ 4.387253] pci 0000:01:00.0: BAR 4: assigned [io 0x10000-0x1000f] [ 4.393613] pci 0000:01:00.0: BAR 0: assigned [io 0x10010-0x10017] [ 4.399990] pci 0000:01:00.0: BAR 2: assigned [io 0x10018-0x1001f] [ 4.406367] pci 0000:01:00.0: BAR 1: assigned [io 0x10020-0x10023] [ 4.412726] pci 0000:01:00.0: BAR 3: assigned [io 0x10024-0x10027] [ 4.419103] pci 0000:00:01.0: PCI bridge to [bus 01] [ 4.424272] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff] [ 4.430649] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff] [ 4.437508] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8100000-0xf810ffff 64bit] [ 4.444843] pci 0000:02:00.0: BAR 2: assigned [mem 0xf8110000-0xf8110fff 64bit] [ 4.452158] pci 0000:02:00.0: BAR 4: assigned [mem 0xf8111000-0xf8111fff 64bit] [ 4.459490] pci 0000:00:02.0: PCI bridge to [bus 02] [ 4.464677] pci 0000:00:02.0: bridge window [mem 0xf8100000-0xf81fffff] [ 4.471612] pcieport 0000:00:01.0: assign IRQ: got 0 [ 4.471630] pcieport 0000:00:01.0: enabling device (0140 -> 0143) [ 4.477876] pcieport 0000:00:01.0: enabling bus mastering [ 4.477966] pcieport 0000:00:02.0: assign IRQ: got 0 [ 4.477980] pcieport 0000:00:02.0: enabling device (0140 -> 0142) [ 4.484188] pcieport 0000:00:02.0: enabling bus mastering [ 4.484240] pci 0000:00:02.0: enabling bus mastering [ 4.485457] mv_xor d0060800.xor: Marvell shared XOR driver [ 4.556029] mv_xor d0060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 4.567044] mv_xor d0060900.xor: Marvell shared XOR driver [ 4.636011] mv_xor d0060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 4.839102] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 4.850781] printk: console [ttyS0] disabled [ 4.877042] d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 19, base_baud = 12500000) is a 16550A [ 4.886118] printk: console [ttyS0] enabled [ 4.895175] printk: bootconsole [earlycon0] disabled [ 4.907820] ahci 0000:01:00.0: assign IRQ: got 41 [ 4.907842] ahci 0000:01:00.0: version 3.0 [ 4.907864] pci 0000:00:01.0: enabling bus mastering [ 4.907879] ahci 0000:01:00.0: enabling device (0146 -> 0147) [ 4.914119] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode [ 4.923083] ahci 0000:01:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs [ 4.934580] scsi host0: ahci [ 4.939249] scsi host1: ahci [ 4.943293] ata1: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010100 irq 42 [ 4.951081] ata2: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010180 irq 42 [ 4.959470] sata_mv d00a0000.sata: version 1.28 [ 4.959685] sata_mv d00a0000.sata: slots 32 ports 1 [ 4.968069] scsi host2: sata_mv [ 4.972391] ata3: SATA max UDMA/133 irq 27 [ 4.978494] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xf1 [ 4.986037] nand: Micron MT29F1G08ABADAWP [ 4.990386] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 4.998912] Bad block table found at page 65472, version 0x01 [ 5.005558] Bad block table found at page 65408, version 0x01 [ 5.011822] 5 cmdlinepart partitions found on MTD device pxa3xx_nand-0 [ 5.018576] Creating 5 MTD partitions on "pxa3xx_nand-0": [ 5.024197] 0x000000000000-0x000000180000 : "u-boot" [ 5.031696] 0x000000180000-0x0000001a0000 : "u-boot-env" [ 5.040068] 0x000000200000-0x000000800000 : "uImage" [ 5.048112] 0x000000800000-0x000000c00000 : "minirootfs" [ 5.056525] 0x000000c00000-0x000008000000 : "ubifs" [ 5.066449] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. [ 5.074312] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved. [ 5.088681] libphy: Fixed MDIO Bus: probed [ 5.098330] libphy: orion_mdio_bus: probed [ 5.120742] mvneta d0074000.ethernet eth0: Using random mac address d6:0c:3a:f6:8f:4a [ 5.133214] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 5.140478] ehci-pci: EHCI PCI platform driver [ 5.145956] ehci-orion: EHCI orion driver [ 5.150511] orion-ehci d0050000.usb: EHCI Host Controller [ 5.156536] orion-ehci d0050000.usb: new USB bus registered, assigned bus number 1 [ 5.164362] orion-ehci d0050000.usb: irq 25, io mem 0xd0050000 [ 5.194689] orion-ehci d0050000.usb: USB 2.0 started, EHCI 1.00 [ 5.201174] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08 [ 5.209542] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.216911] usb usb1: Product: EHCI Host Controller [ 5.222101] usb usb1: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 ehci_hcd [ 5.229141] usb usb1: SerialNumber: d0050000.usb [ 5.235181] hub 1-0:1.0: USB hub found [ 5.239673] hub 1-0:1.0: 1 port detected [ 5.245436] xhci_hcd 0000:02:00.0: assign IRQ: got 43 [ 5.245513] xhci_hcd 0000:02:00.0: enabling bus mastering [ 5.245525] xhci_hcd 0000:02:00.0: xHCI Host Controller [ 5.251537] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2 [ 5.259995] xhci_hcd 0000:02:00.0: hcc params 0x200073a1 hci version 0x100 quirks 0x0000000000080010 [ 5.269297] xhci_hcd 0000:02:00.0: enabling Mem-Wr-Inval [ 5.270104] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08 [ 5.278517] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.285917] usb usb2: Product: xHCI Host Controller [ 5.291109] usb usb2: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 xhci-hcd [ 5.298185] ata2: SATA link down (SStatus 0 SControl 300) [ 5.303853] usb usb2: SerialNumber: 0000:02:00.0 [ 5.309967] hub 2-0:1.0: USB hub found [ 5.314387] hub 2-0:1.0: 2 ports detected [ 5.319899] xhci_hcd 0000:02:00.0: xHCI Host Controller [ 5.325832] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3 [ 5.333307] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed [ 5.339996] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM. [ 5.348641] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08 [ 5.356981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.364277] usb usb3: Product: xHCI Host Controller [ 5.369466] usb usb3: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 xhci-hcd [ 5.376487] usb usb3: SerialNumber: 0000:02:00.0 [ 5.382314] hub 3-0:1.0: USB hub found [ 5.386798] hub 3-0:1.0: 2 ports detected [ 5.392874] usbcore: registered new interface driver usblp [ 5.399565] usbcore: registered new interface driver usb-storage [ 5.406797] mousedev: PS/2 mouse device common for all mice [ 5.414504] i2c /dev entries driver [ 5.423134] rtc-ds1307 0-0068: 'wakeup-source' is set, request for an IRQ is disabled! [ 5.436533] rtc-ds1307 0-0068: registered as rtc0 [ 5.442548] rtc-ds1307 0-0068: setting system clock to 2020-10-09T19:43:55 UTC (1602272635) [ 5.474690] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 5.481102] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl F300) [ 5.489278] orion_wdt: Initial timeout 229 sec [ 5.495568] ata1.00: supports DRM functions and may not be fully accessible [ 5.502865] ata3.00: ATA-7: ST940210AS, 3.ALC, max UDMA/100 [ 5.509526] device-mapper: uevent: version 1.0.3 [ 5.514961] ata3.00: 78140160 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 5.521895] ata1.00: ATA-8: ST33000651NS, G009, max UDMA/133 [ 5.528347] device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com [ 5.537180] ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32) [ 5.544115] ata3.00: configured for UDMA/100 [ 5.549352] device-mapper: multipath round-robin: version 1.2.0 loaded [ 5.556153] device-mapper: multipath queue-length: version 0.2.0 loaded [ 5.562944] ata1.00: ATA Identify Device Log not supported [ 5.568726] device-mapper: multipath service-time: version 0.3.0 loaded [ 5.575518] ata1.00: Security Log not supported [ 5.580448] device-mapper: dm-log-userspace: version 1.3.0 loaded [ 5.586808] device-mapper: raid: Loading target version 1.15.1 [ 5.593026] ata1.00: supports DRM functions and may not be fully accessible [ 5.605789] ata1.00: ATA Identify Device Log not supported [ 5.611497] ata1.00: Security Log not supported [ 5.617688] ata1.00: configured for UDMA/133 [ 5.623035] marvell-cesa d0090000.crypto: CESA device successfully registered [ 5.631244] hid: raw HID events driver (C) Jiri Kosina [ 5.637361] scsi 0:0:0:0: Direct-Access ATA ST33000651NS G009 PQ: 0 ANSI: 5 [ 5.646926] usbcore: registered new interface driver usbhid [ 5.652707] usbhid: USB HID core driver [ 5.659241] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) [ 5.668418] scsi 2:0:0:0: Direct-Access ATA ST940210AS C PQ: 0 ANSI: 5 [ 5.677480] sd 0:0:0:0: [sda] Write Protect is off [ 5.682547] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 5.684213] sd 2:0:0:0: [sdb] 78140160 512-byte logical blocks: (40.0 GB/37.3 GiB) [ 5.693721] drop_monitor: Initializing network drop monitor service [ 5.700751] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.710034] sd 2:0:0:0: [sdb] Write Protect is off [ 5.715739] NET: Registered protocol family 10 [ 5.721111] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 5.721289] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.732972] Segment Routing with IPv6 [ 5.737838] RPL Segment Routing with IPv6 [ 5.742279] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 5.753040] NET: Registered protocol family 17 [ 5.758873] 8021q: 802.1Q VLAN Support v1.8 [ 5.763437] Key type dns_resolver registered [ 5.769515] ThumbEE CPU extension supported. [ 5.774320] Registering SWP/SWPB emulation handler [ 5.780676] sda: sda1 [ 5.783858] registered taskstats version 1 [ 5.790316] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 5.797195] sdb: sdb1 [ 5.802245] sd 2:0:0:0: [sdb] Attached SCSI disk [ 5.807565] Loading compiled-in X.509 certificates [ 5.812802] zswap: loaded using pool lzo/zbud [ 5.818568] Key type ._fscrypt registered [ 5.822912] Key type .fscrypt registered [ 5.827410] Key type fscrypt-provisioning registered [ 5.835682] Key type big_key registered [ 5.865147] Key type encrypted registered [ 5.874073] input: gpio-keys as /devices/platform/gpio-keys/input/input0 [ 5.885716] Freeing unused kernel memory: 1024K [ 5.916603] Checked W+X mappings: passed, no W+X pages found [ 5.922485] Run /init as init process [ 5.926581] with arguments: [ 5.926586] /init [ 5.926591] with environment: [ 5.926595] HOME=/ [ 5.926599] TERM=linux [ 5.926603] reason=normal [ 5.926607] bdtype=rn102 [ 7.781750] random: fast init done [ 18.977118] process '/usr/bin/fstype' started with executable stack [ 22.086942] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem [ 22.764729] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 26.037202] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 26.058811] systemd[1]: Detected architecture arm. [ 26.154878] systemd[1]: Set hostname to <neutron>. [ 27.917959] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. [ 27.934559] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.) [ 28.466495] random: crng init done [ 29.139824] systemd[1]: /lib/systemd/system/rpc-statd.service:13: PIDFile= references path below legacy directory /var/run/, updating /var/run/rpc.statd.pid \xe2\x86\x92 /run/rpc.statd.pid; please update the unit file accordingly. [ 29.313609] systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. [ 29.478252] systemd[1]: Listening on RPCbind Server Activation Socket. [ 29.515948] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 29.561238] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 30.835146] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro [ 31.087038] systemd[1]: Starting Load/Save Random Seed... [ 31.206480] systemd[1]: Starting Create System Users... [ 31.280510] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [ 31.346124] systemd[1]: Activating swap /swapfile... [ 31.450672] systemd[1]: Started Apply Kernel Variables. [ 31.488821] systemd[1]: Started pNFS block layout mapping daemon. [ 31.745161] systemd[1]: Started Load/Save Random Seed. [ 31.874946] systemd[1]: Started Create System Users. [ 31.924083] systemd[1]: Starting Create Static Device Nodes in /dev... [ 32.525103] systemd[1]: Started Create Static Device Nodes in /dev. [ 33.129145] systemd-journald[1564]: Received request to flush runtime journal from PID 1 [ 38.392258] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 38.569707] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 39.214872] Adding 1048572k swap on /swapfile. Priority:-2 extents:17 across:18278744k FS [ 41.424898] Btrfs loaded, crc32c=crc32c-generic [ 41.436277] BTRFS: device label Sea4 devid 1 transid 5265 /dev/sda1 scanned by systemd-udevd (1586) [ 42.900127] BTRFS info (device sda1): disk space caching is enabled [ 42.934867] BTRFS info (device sda1): has skinny extents [ 59.948168] mvneta d0074000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL) [ 59.969996] mvneta d0074000.ethernet eth0: configuring for phy/rgmii-id link mode [ 63.146088] mvneta d0074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 63.164871] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 81.513031] Setting Persistent MAC address to "MASKED MAC" [ 83.199731] mvneta d0074000.ethernet eth0: Link is Down [ 83.380669] NFSD: Using UMH upcall client tracking operations. [ 83.403598] NFSD: starting 90-second grace period (net f0000021) [ 85.263723] mvneta d0074000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL) [ 85.334370] mvneta d0074000.ethernet eth0: configuring for phy/rgmii-id link mode [ 88.509179] mvneta d0074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 88.517087] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 108.630075] fbcon: Taking over console
In dmesg it automaticly disables flow control i guess.
Regards.
|
Re: Debian on Netgear RN102 October 09, 2020 03:35PM |
Registered: 6 years ago Posts: 157 |
Hi whitepawn,
The RN102 is a file server, so I think the only performance measure that really counts is the bandwidth into and out of the box. For the tests below, both the RN102 and my laptop were cabled to the same gigabit router. I have 2 mirroring 2 TB HDDs in the box (RAID-1). I copied the file 'film.mp4' back and forth. Its size is 1 GB and it contains a 3+ hour movie. Session transcript below.
I normally use 'sftp' so I don't have to do things differently at home and in the wild. Pulling the file out of the box took 2:30 minutes at 6.6 MB/s as reported by 'scp'. The bottleneck was CPU power for the encryption with 'sshd' using over 80%. Only the Sata1 LED was active, so there was no benefit from reading every second cylinder from each disk.
Pushing the file back again took 2:37 minutes at 6.3 MB/s. The bottleneck was CPU power for the decryption with 'sshd' using over 70%.
Pulling the same file over 'http' took 30 seconds at 35 MB/s as reported (278 Mb/s) by 'wget'. The bottleneck was CPU power with 'minidlna' using over 90%. Only the Sata1 LED was active.
I haven't configured the box for 'samba' nor 'nfs', so it cannot receive unencrypted data.
Internally, copying 1 GiB from '/dev/null' to the mirror took 28 seconds at 38,3 MB/s as reported by 'dd'. The bottleneck was CPU power with 'dd' using about 80%. The Sata LEDS were not steady on, but blinking.
Copying the file to '/dev/null' took 9 seconds at about 112 MB/s. Even here the bottleneck was CPU power with 'cp' using about 85%. Still only the Sata1 LED was active.
Based on these tests, I conclude that the RN102 is under-powered with its one core Arm7 SoC. I plan to use SSDs rather than HDDs in my second RN102. Apparently, this will not increase the bandwidth for large files, but I expect it to reduce latency as well as increase bandwidth for large bunches of smaller files.
Regards,
Trond Melen
The RN102 is a file server, so I think the only performance measure that really counts is the bandwidth into and out of the box. For the tests below, both the RN102 and my laptop were cabled to the same gigabit router. I have 2 mirroring 2 TB HDDs in the box (RAID-1). I copied the file 'film.mp4' back and forth. Its size is 1 GB and it contains a 3+ hour movie. Session transcript below.
I normally use 'sftp' so I don't have to do things differently at home and in the wild. Pulling the file out of the box took 2:30 minutes at 6.6 MB/s as reported by 'scp'. The bottleneck was CPU power for the encryption with 'sshd' using over 80%. Only the Sata1 LED was active, so there was no benefit from reading every second cylinder from each disk.
Pushing the file back again took 2:37 minutes at 6.3 MB/s. The bottleneck was CPU power for the decryption with 'sshd' using over 70%.
Pulling the same file over 'http' took 30 seconds at 35 MB/s as reported (278 Mb/s) by 'wget'. The bottleneck was CPU power with 'minidlna' using over 90%. Only the Sata1 LED was active.
I haven't configured the box for 'samba' nor 'nfs', so it cannot receive unencrypted data.
Internally, copying 1 GiB from '/dev/null' to the mirror took 28 seconds at 38,3 MB/s as reported by 'dd'. The bottleneck was CPU power with 'dd' using about 80%. The Sata LEDS were not steady on, but blinking.
Copying the file to '/dev/null' took 9 seconds at about 112 MB/s. Even here the bottleneck was CPU power with 'cp' using about 85%. Still only the Sata1 LED was active.
Based on these tests, I conclude that the RN102 is under-powered with its one core Arm7 SoC. I plan to use SSDs rather than HDDs in my second RN102. Apparently, this will not increase the bandwidth for large files, but I expect it to reduce latency as well as increase bandwidth for large bunches of smaller files.
Regards,
Trond Melen
$ time scp debian:tmp/film.mp4 copy.mp4 tme@debian's password: film.mp4 100% 972MB 6.6MB/s 02:28 real 2m29,836s user 0m16,576s sys 0m15,625s $ ls -alF copy.mp4 -rw-r--r-- 1 tme tme 1019494944 okt. 9 20:29 copy.mp4 $ time scp copy.mp4 debian:tmp/ tme@debian's password: copy.mp4 100% 972MB 6.3MB/s 02:34 real 2m36,557s user 0m13,227s sys 0m5,631s $ time wget --report-speed=bits http://debian:8200/MediaItems/205.mp4 --2020-10-09 21:00:51-- http://debian:8200/MediaItems/205.mp4 Resolving debian (debian)... 192.168.1.109 Connecting to debian (debian)|192.168.1.109|:8200... connected. HTTP request sent, awaiting response... 200 OK Length: 1019494944 (972M) [video/mp4] Saving to: ‘205.mp4’ 205.mp4 100%[=========================================================>] 972,27M 278Mb/s in 30s 2020-10-09 21:01:22 (270 Mb/s) - ‘205.mp4’ saved [1019494944/1019494944] real 0m30,283s user 0m1,542s sys 0m7,383s $ ssh debian.localdomain $ time dd if=/dev/zero of=null.dat count=8192 bs=131072 status=progress 1072037888 bytes (1,1 GB, 1022 MiB) copied, 28 s, 38,3 MB/s 8192+0 records in 8192+0 records out 1073741824 bytes (1,1 GB, 1,0 GiB) copied, 28,0498 s, 38,3 MB/s real 0m28,068s user 0m0,135s sys 0m22,005s $ time cp film.mp4 /dev/null real 0m8,821s user 0m0,059s sys 0m6,999s
|
Re: Debian on Netgear RN102 October 09, 2020 08:25PM |
Admin Registered: 13 years ago Posts: 18,543 |
Trond,
Please run the same iperf tests as whitepawn did.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Please run the same iperf tests as whitepawn did.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 10, 2020 02:28AM |
Admin Registered: 13 years ago Posts: 18,543 |
Network Benchmarks for Thecus N2350 (Armada 385) and Zyxel NSA325 (Kirkwood 6820).
Both connected to a Gbit switch. The N2350 has flow-control enabled. The NSA325 has flow-control disabled.
192.168.0.224
Thecus N2350
Linux version 5.8.5-mvebu-tld-1
Debian 10.5
192.168.0.227
ZyXEL NSA325
Linux version 5.8.3-kirkwood-tld-1
Debian 10.0
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Both connected to a Gbit switch. The N2350 has flow-control enabled. The NSA325 has flow-control disabled.
192.168.0.224
Thecus N2350
Linux version 5.8.5-mvebu-tld-1
Debian 10.5
iperf -n2000M -i 3 -c 192.168.0.227 ------------------------------------------------------------ Client connecting to HomeBackup.local, TCP port 5001 TCP window size: 43.8 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.0.224 port 51508 connected with 192.168.0.227 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 3.0 sec 322 MBytes 900 Mbits/sec [ 3] 3.0- 6.0 sec 322 MBytes 899 Mbits/sec [ 3] 6.0- 9.0 sec 322 MBytes 900 Mbits/sec [ 3] 9.0-12.0 sec 322 MBytes 902 Mbits/sec [ 3] 12.0-15.0 sec 323 MBytes 903 Mbits/sec [ 3] 15.0-18.0 sec 322 MBytes 901 Mbits/sec [ 3] 0.0-18.6 sec 1.95 GBytes 901 Mbits/sec
192.168.0.227
ZyXEL NSA325
Linux version 5.8.3-kirkwood-tld-1
Debian 10.0
iperf -s -i 3 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.0.227 port 5001 connected with 192.168.0.224 port 51508 [ ID] Interval Transfer Bandwidth [ 4] 0.0- 3.0 sec 321 MBytes 896 Mbits/sec [ 4] 3.0- 6.0 sec 322 MBytes 900 Mbits/sec [ 4] 6.0- 9.0 sec 322 MBytes 900 Mbits/sec [ 4] 9.0-12.0 sec 322 MBytes 901 Mbits/sec [ 4] 12.0-15.0 sec 323 MBytes 902 Mbits/sec [ 4] 15.0-18.0 sec 323 MBytes 902 Mbits/sec [ 4] 0.0-18.6 sec 1.95 GBytes 900 Mbits/sec
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 10, 2020 02:36AM |
Admin Registered: 13 years ago Posts: 18,543 |
Network Benchmarks for Zyxel NSA310S (Kirkwood 6281) and GTI Mirabox (Armada 370).
Both connected to a Gbit switch (I need to verify this, ie. both might be in a Gbit network but not the same switch). THe NSA310S has flow control disabled, the Mirabox has flow control enabled.
192.168.0.220
Zyxel NSA310S
Linux version 5.8.3-kirkwood-tld-1
Debian 10.4
192.168.0.252
Globalscale Mirabox
Linux version 5.8.5-mvebu-370xp-tld-1
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/10/2020 02:45AM by bodhi.
Both connected to a Gbit switch (I need to verify this, ie. both might be in a Gbit network but not the same switch). THe NSA310S has flow control disabled, the Mirabox has flow control enabled.
192.168.0.220
Zyxel NSA310S
Linux version 5.8.3-kirkwood-tld-1
Debian 10.4
iperf -n2000M -i 3 -c 192.168.0.252 ------------------------------------------------------------ Client connecting to 192.168.0.252, TCP port 5001 TCP window size: 43.8 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.0.220 port 35290 connected with 192.168.0.252 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 3.0 sec 178 MBytes 499 Mbits/sec [ 3] 3.0- 6.0 sec 178 MBytes 497 Mbits/sec [ 3] 6.0- 9.0 sec 178 MBytes 497 Mbits/sec [ 3] 9.0-12.0 sec 179 MBytes 500 Mbits/sec [ 3] 12.0-15.0 sec 176 MBytes 494 Mbits/sec [ 3] 15.0-18.0 sec 179 MBytes 502 Mbits/sec [ 3] 18.0-21.0 sec 178 MBytes 497 Mbits/sec [ 3] 21.0-24.0 sec 177 MBytes 495 Mbits/sec [ 3] 24.0-27.0 sec 175 MBytes 490 Mbits/sec [ 3] 27.0-30.0 sec 177 MBytes 494 Mbits/sec [ 3] 30.0-33.0 sec 178 MBytes 498 Mbits/sec [ 3] 0.0-33.8 sec 1.95 GBytes 497 Mbits/sec
192.168.0.252
Globalscale Mirabox
Linux version 5.8.5-mvebu-370xp-tld-1
iperf -s -i 3 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.0.252 port 5001 connected with 192.168.0.220 port 35290 [ ID] Interval Transfer Bandwidth [ 4] 0.0- 3.0 sec 177 MBytes 494 Mbits/sec [ 4] 3.0- 6.0 sec 178 MBytes 498 Mbits/sec [ 4] 6.0- 9.0 sec 178 MBytes 497 Mbits/sec [ 4] 9.0-12.0 sec 178 MBytes 499 Mbits/sec [ 4] 12.0-15.0 sec 177 MBytes 496 Mbits/sec [ 4] 15.0-18.0 sec 178 MBytes 499 Mbits/sec [ 4] 18.0-21.0 sec 178 MBytes 497 Mbits/sec [ 4] 21.0-24.0 sec 177 MBytes 496 Mbits/sec [ 4] 24.0-27.0 sec 176 MBytes 491 Mbits/sec [ 4] 27.0-30.0 sec 176 MBytes 493 Mbits/sec [ 4] 30.0-33.0 sec 178 MBytes 498 Mbits/sec [ 4] 0.0-33.8 sec 1.95 GBytes 496 Mbits/sec
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/10/2020 02:45AM by bodhi.
|
Re: Debian on Netgear RN102 October 10, 2020 02:48AM |
Admin Registered: 13 years ago Posts: 18,543 |
Mirabox network settings.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
root@Mirabox:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII FIBRE ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: yes
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 10, 2020 03:21AM |
Registered: 6 years ago Posts: 157 |
Quote
Trond, Please run the same iperf tests as whitepawn did. -bodhi
Sure bodhi,
$ iperf -n2000M -i 3 -c 192.168.1.128 ------------------------------------------------------------ Client connecting to 192.168.1.128, TCP port 5001 TCP window size: 43.8 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.109 port 42516 connected with 192.168.1.128 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 3.0 sec 151 MBytes 422 Mbits/sec [ 3] 3.0- 6.0 sec 155 MBytes 433 Mbits/sec [ 3] 6.0- 9.0 sec 144 MBytes 402 Mbits/sec [ 3] 9.0-12.0 sec 146 MBytes 410 Mbits/sec [ 3] 12.0-15.0 sec 151 MBytes 423 Mbits/sec [ 3] 15.0-18.0 sec 153 MBytes 427 Mbits/sec [ 3] 18.0-21.0 sec 149 MBytes 417 Mbits/sec [ 3] 21.0-24.0 sec 152 MBytes 426 Mbits/sec [ 3] 24.0-27.0 sec 151 MBytes 422 Mbits/sec [ 3] 27.0-30.0 sec 150 MBytes 419 Mbits/sec [ 3] 30.0-33.0 sec 150 MBytes 418 Mbits/sec [ 3] 33.0-36.0 sec 150 MBytes 418 Mbits/sec [ 3] 36.0-39.0 sec 150 MBytes 420 Mbits/sec [ 3] 0.0-40.0 sec 1.95 GBytes 419 Mbits/sec $ sudo ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d420 Mb/s corresponds to 52 MB/s and 50 MiB/s which is a lot more than the 35 MB/s I achieved with 'http' from 'minidlna' using 'wget'. Maybe 'samba' or 'nfs' is slightly faster, but to me, network bandwidth does not seem to be the box' limiting factor. Of course, any performance increase is still highly welcome!
Attempting to run 'sysbench' failed:
$ cat /etc/debian_version 10.6 $ sudo apt install -y sysbench Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package sysbench $ sudo apt list -a sysbench Listing... Done $ apt-cache search sysbench $
In Debian Buster, 'sysbench' appearantly is currently avaliable for 'amd64', 'arm64', 'i386' and 'ppc64el' only, and not for 'armhf' nor 'armel'. So, I downloaded the Sid 'deb' file from this page and installed it manually, but I got some complaints and it refused to run:
$ wget http://ftp.debian.org/debian/pool/main/s/sysbench/sysbench_1.0.20+ds-1_armhf.deb $ ls -alF sysbench_1.0.20+ds-1_armhf.deb -rw-r--r-- 1 tme tme 106612 juni 7 02:43 sysbench_1.0.20+ds-1_armhf.deb $ sudo dpkg --install sysbench_1.0.20+ds-1_armhf.deb Selecting previously unselected package sysbench. (Reading database ... 25650 files and directories currently installed.) Preparing to unpack sysbench_1.0.20+ds-1_armhf.deb ... Unpacking sysbench (1.0.20+ds-1) ... dpkg: dependency problems prevent configuration of sysbench: sysbench depends on libaio1 (>= 0.3.93); however: Package libaio1 is not installed. sysbench depends on libc6 (>= 2.29); however: Version of libc6:armhf on system is 2.28-10. sysbench depends on libluajit-5.1-2 (>= 2.0.4+dfsg); however: Package libluajit-5.1-2 is not installed. sysbench depends on libmariadb3 (>= 3.0.0); however: Package libmariadb3 is not installed. sysbench depends on libpq5; however: Package libpq5 is not installed. dpkg: error processing package sysbench (--install): dependency problems - leaving unconfigured Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: sysbench $ sysbench --test=memory --memory-block-size=512K --memory-total-size=512M run sysbench: error while loading shared libraries: libmariadb.so.3: cannot open shared object file: No such file or directory $
I removed it again and tried the same with the version from Debian Stretch:
$ sudo dpkg --remove sysbench (Reading database ... 25672 files and directories currently installed.) Removing sysbench (1.0.20+ds-1) ... Processing triggers for man-db (2.8.5-2) ... $ wget http://ftp.debian.org/debian/pool/main/s/sysbench/sysbench_0.4.12-1.2_armhf.deb $ sudo dpkg --install sysbench_0.4.12-1.2_armhf.deb Selecting previously unselected package sysbench. (Reading database ... 25650 files and directories currently installed.) Preparing to unpack sysbench_0.4.12-1.2_armhf.deb ... Unpacking sysbench (0.4.12-1.2) ... dpkg: dependency problems prevent configuration of sysbench: sysbench depends on libmariadbclient18 (>= 5.5.36); however: Package libmariadbclient18 is not installed. dpkg: error processing package sysbench (--install): dependency problems - leaving unconfigured Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: sysbench $ sysbench --test=memory --memory-block-size=512K --memory-total-size=512M run sysbench: error while loading shared libraries: libmariadbclient.so.18: cannot open shared object file: No such file or directory $
Giving up for now.
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 October 10, 2020 04:23AM |
Registered: 6 years ago Posts: 157 |
Hi whitepawn,
To assist in debugging your network issue, here are some more output from 'ethtool' that you may compare to yours:
Regards,
Trond Melen
EDIT: Typo only. :TIDE
Edited 1 time(s). Last edit at 10/10/2020 05:10AM by tme.
To assist in debugging your network issue, here are some more output from 'ethtool' that you may compare to yours:
$ sudo ethtool --show-pause eth0
Pause parameters for eth0:
Autonegotiate: on
RX: off
TX: off
RX negotiated: on
TX negotiated: on
$ sudo ethtool --show-coalesce eth0
Coalesce parameters for eth0:
Adaptive RX: off TX: off
stats-block-usecs: 0
sample-interval: 0
pkt-rate-low: 0
pkt-rate-high: 0
rx-usecs: 100
rx-frames: 32
rx-usecs-irq: 0
rx-frames-irq: 0
tx-usecs: 0
tx-frames: 0
tx-usecs-irq: 0
tx-frames-irq: 0
rx-usecs-low: 0
rx-frame-low: 0
tx-usecs-low: 0
tx-frame-low: 0
rx-usecs-high: 0
rx-frame-high: 0
tx-usecs-high: 0
tx-frame-high: 0
$ sudo ethtool --show-features eth0 | awk -F: '{printf "%-30s: %s\n", $1, $2}'
Features for eth0 :
rx-checksumming : on
tx-checksumming : on
tx-checksum-ipv4 : on
tx-checksum-ip-generic : off [fixed]
tx-checksum-ipv6 : on
tx-checksum-fcoe-crc : off [fixed]
tx-checksum-sctp : off [fixed]
scatter-gather : on
tx-scatter-gather : on
tx-scatter-gather-fraglist : off [fixed]
tcp-segmentation-offload : on
tx-tcp-segmentation : on
tx-tcp-ecn-segmentation : off [fixed]
tx-tcp-mangleid-segmentation : off
tx-tcp6-segmentation : off [fixed]
udp-fragmentation-offload : off
generic-segmentation-offload : on
generic-receive-offload : on
large-receive-offload : off [fixed]
rx-vlan-offload : off [fixed]
tx-vlan-offload : off [fixed]
ntuple-filters : off [fixed]
receive-hashing : off [fixed]
highdma : off [fixed]
rx-vlan-filter : off [fixed]
vlan-challenged : off [fixed]
tx-lockless : off [fixed]
netns-local : off [fixed]
tx-gso-robust : off [fixed]
tx-fcoe-segmentation : off [fixed]
tx-gre-segmentation : off [fixed]
tx-gre-csum-segmentation : off [fixed]
tx-ipxip4-segmentation : off [fixed]
tx-ipxip6-segmentation : off [fixed]
tx-udp_tnl-segmentation : off [fixed]
tx-udp_tnl-csum-segmentation : off [fixed]
tx-gso-partial : off [fixed]
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation : off [fixed]
tx-esp-segmentation : off [fixed]
tx-udp-segmentation : off [fixed]
tx-gso-list : off [fixed]
fcoe-mtu : off [fixed]
tx-nocache-copy : off
loopback : off [fixed]
rx-fcs : off [fixed]
rx-all : off [fixed]
tx-vlan-stag-hw-insert : off [fixed]
rx-vlan-stag-hw-parse : off [fixed]
rx-vlan-stag-filter : off [fixed]
l2-fwd-offload : off [fixed]
hw-tc-offload : off [fixed]
esp-hw-offload : off [fixed]
esp-tx-csum-hw-offload : off [fixed]
rx-udp_tunnel-port-offload : off [fixed]
tls-hw-tx-offload : off [fixed]
tls-hw-rx-offload : off [fixed]
rx-gro-hw : off [fixed]
tls-hw-record : off [fixed]
rx-gro-list : off
macsec-hw-offload : off [fixed]
$ sudo ethtool --show-priv-flags eth0
No private flags defined
$ sudo ethtool --show-permaddr eth0
Permanent address: 00:00:00:00:00:00
$
If everything is the same on your box, I suggest Reset to factory defaults and Reinstall OS, both from the Bootmenu. You may have to modify the 'bootcmd' environment variable in U-boot first, and you only want disk(s) without valuable data in the box when you try. Good luck!
Regards,
Trond Melen
EDIT: Typo only. :TIDE
Edited 1 time(s). Last edit at 10/10/2020 05:10AM by tme.
|
Re: Debian on Netgear RN102 October 10, 2020 08:27AM |
Registered: 6 years ago Posts: 157 |
Hi bodhi and whitepawn,
I was curious how the Netgear Stora released in 2009 with a Marvell 88F6281 Kirkwood Feroceon SoC compares to the 4 years newer ReadyNAS RN102 with a Marvell 88F6710 Armada 370 SoC. Transcript of test session below.
My observations:
The relevant differences compared to RN102 are:
Regards,
Trond Melen
I was curious how the Netgear Stora released in 2009 with a Marvell 88F6281 Kirkwood Feroceon SoC compares to the 4 years newer ReadyNAS RN102 with a Marvell 88F6710 Armada 370 SoC. Transcript of test session below.
My observations:
- Pulling a 1 GB file over 'sftp' took 2:43 min (10% slower).
- Pushing a 1 GB file over 'sftp' took 6:37 min (2.5 times slower). Performance was limited alternatingly by CPU power and memory.
- Pulling a 1 GB file over 'http' from 'minidlna' with 'wget' took 19 s (37% faster).
- Internally, writing 1 GiB of zeros to disk with 'dd' took 23 s (18% faster).
- Internally, reading 1 GB from disk with 'cp' took 10 s (15% slower).
- Ethernet bandwitdh measured by 'iperf' was about 530 Mb/s in both directions (26% faster).
The relevant differences compared to RN102 are:
- 128 MiB 800 MHz DDR2 RAM, rather than 512 MiB 1333 Mhz DDR3.
- 1.0 GHz CPU clock, rather than 1.2 GHz.
- ARMv5 architecture, rather than ARMv7.
- SoC internal SATA II 3 Gb/s controller, rather than a separate Marvell 88SE9170 PCI-e SATA III 6 Gb/s controller.
- 256 KiB 333 MHz L2 cache, rather than same size 600 MHz.
- Debian root file system on USB stick, rather than on eSATA SSD.
- Linux kernel 4.10.9-kirkwood-tld-1, rather than 5.8.5-mvebu-370xp-tld-1.
- Debian 9.13, rather than Debian 10.6.
Regards,
Trond Melen
$ time scp stora:tmp/film.mp4 copy.mp4 tme@stora's password: film.mp4 100% 972MB 5.9MB/s 02:43 real 2m46,278s user 0m15,560s sys 0m14,096s $ time scp copy.mp4 stora:tmp/ tme@stora's password: copy.mp4 100% 972MB 2.5MB/s 06:37 real 6m39,938s user 0m12,062s sys 0m4,786s $ time wget --report-speed=bits http://192.168.1.100:8200/MediaItems/22.mp4 --2020-10-10 13:05:06-- http://192.168.1.100:8200/MediaItems/22.mp4 Connecting to 192.168.1.100:8200... connected. HTTP request sent, awaiting response... 200 OK Length: 1019494944 (972M) [video/mp4] Saving to: ‘22.mp4’ 22.mp4 100%[=========================================================>] 972,27M 409Mb/s in 19s 2020-10-10 13:05:25 (423 Mb/s) - ‘22.mp4’ saved [1019494944/1019494944] real 0m19,303s user 0m1,009s sys 0m5,254s $ ssh stora $ uname -a Linux stora 4.10.9-kirkwood-tld-1 #1 PREEMPT Sun Apr 9 23:40:29 PDT 2017 armv5tel GNU/Linux $ cat /etc/debian_version 9.13 $ time dd if=/dev/zero of=null.dat count=8192 bs=131072 status=progress 1029439488 bytes (1.0 GB, 982 MiB) copied, 22 s, 46.8 MB/s 8192+0 records in 8192+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 22.812 s, 47.1 MB/s real 0m22.827s user 0m0.090s sys 0m13.230s $ time cp film.mp4 /dev/null real 0m10.070s user 0m0.080s sys 0m8.010s $ iperf -n 2G -i 3 -c 192.168.1.128 -r ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to 192.168.1.128, TCP port 5001 TCP window size: 118 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.100 port 36306 connected with 192.168.1.128 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 3.0 sec 165 MBytes 461 Mbits/sec [ 3] 3.0- 6.0 sec 197 MBytes 551 Mbits/sec [ 3] 6.0- 9.0 sec 202 MBytes 564 Mbits/sec [ 3] 9.0-12.0 sec 192 MBytes 538 Mbits/sec [ 3] 12.0-15.0 sec 179 MBytes 499 Mbits/sec [ 3] 15.0-18.0 sec 188 MBytes 525 Mbits/sec [ 3] 18.0-21.0 sec 183 MBytes 511 Mbits/sec [ 3] 21.0-24.0 sec 201 MBytes 561 Mbits/sec [ 3] 24.0-27.0 sec 202 MBytes 564 Mbits/sec [ 3] 27.0-30.0 sec 187 MBytes 522 Mbits/sec [ 3] 0.0-32.3 sec 2.00 GBytes 532 Mbits/sec [ 5] local 192.168.1.100 port 5001 connected with 192.168.1.128 port 35380 [ 5] 0.0- 0.0 sec 0.00 Bytes 0.00 bits/sec $
|
Re: Debian on Netgear RN102 October 10, 2020 04:33PM |
Admin Registered: 13 years ago Posts: 18,543 |
whitepawn,
I don't think your network problem can be fixed going back to stock and back to Debian again. Go back to stock and see the network performance improvement: then it meant the sstock OS has some special patch that deal with this box.
Since Trond got about 500 Mbs on a RN102, this is most likely the problem in either your rootfs, or in the router. My suggestion:
1. Boot back to sysvinit. don't use systemd until you figure out what the problem was.
2. Log in the router and check the settings. IOW, do you have QoS or any preferences set for certain port or type of activities (streaming, http, or something specific).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
Trond
> If everything is the same on your box, I suggest
> Reset to factory defaults and Reinstall OS,
I don't think your network problem can be fixed going back to stock and back to Debian again. Go back to stock and see the network performance improvement: then it meant the sstock OS has some special patch that deal with this box.
Since Trond got about 500 Mbs on a RN102, this is most likely the problem in either your rootfs, or in the router. My suggestion:
1. Boot back to sysvinit. don't use systemd until you figure out what the problem was.
2. Log in the router and check the settings. IOW, do you have QoS or any preferences set for certain port or type of activities (streaming, http, or something specific).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 October 11, 2020 12:02AM |
Registered: 6 years ago Posts: 157 |
Hi whitepawn,
I agree with bodhi that your limited Ethernet bandwidth could be caused by the QoS (Quality of Service) settings in the router.
If disabling QoS does not help, you may completely remove the router from the test and connect the RN102 directly to your PC. Either both parties should be configured for static IP addresses in the same range (e.g. 192.168.5.xxx), or one of the two may be configured as a DHCP server. Very strange things happen with two DHCP servers on the same network, so remember to disable it again before reconnecting to the router.
Some 6 or 10 weeks ago, the network interface on one of my RN102 boxes got stuck somehow. Even 'ping' from the "Marvel>>" prompt in U-Boot failed. Resetting to factory settings in the Netgear bootmenu magically fixed the issue. I don't understand how or why. To me it made little sense, but it worked. Your issue is a different one, though.
Next week I will to run performance tests on RN102 with stock firmware and compare.
Regards,
Trond Melen
I agree with bodhi that your limited Ethernet bandwidth could be caused by the QoS (Quality of Service) settings in the router.
If disabling QoS does not help, you may completely remove the router from the test and connect the RN102 directly to your PC. Either both parties should be configured for static IP addresses in the same range (e.g. 192.168.5.xxx), or one of the two may be configured as a DHCP server. Very strange things happen with two DHCP servers on the same network, so remember to disable it again before reconnecting to the router.
Some 6 or 10 weeks ago, the network interface on one of my RN102 boxes got stuck somehow. Even 'ping' from the "Marvel>>" prompt in U-Boot failed. Resetting to factory settings in the Netgear bootmenu magically fixed the issue. I don't understand how or why. To me it made little sense, but it worked. Your issue is a different one, though.
Next week I will to run performance tests on RN102 with stock firmware and compare.
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 October 11, 2020 11:36AM |
Registered: 4 years ago Posts: 73 |
|
Re: Debian on Netgear RN102 October 11, 2020 04:09PM |
Admin Registered: 13 years ago Posts: 18,543 |
Trond,
> Some 6 or 10 weeks ago, the network interface on
> one of my RN102 boxes got stuck somehow. Even
> 'ping' from the "Marvel>>" prompt in U-Boot
> failed. Resetting to factory settings in the
> Netgear bootmenu magically fixed the issue. I
> don't understand how or why. To me it made little
> sense, but it worked. Your issue is a different
> one, though.
Perhaps the DTS does not cover all the quirks that stock OS does for this this box. Some time you can find out some extra steps that stock OS performs (running some script) by examining the serial boot log.
Case in point, with the NSA325 box. Stock OS executes a network PHY psequence during boot up that is quite quirky. My NSA325 DTS version does try to mimic that in the registers initialization but it did not quite work out, so I have a patch in the kernel to execute the sequence.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Some 6 or 10 weeks ago, the network interface on
> one of my RN102 boxes got stuck somehow. Even
> 'ping' from the "Marvel>>" prompt in U-Boot
> failed. Resetting to factory settings in the
> Netgear bootmenu magically fixed the issue. I
> don't understand how or why. To me it made little
> sense, but it worked. Your issue is a different
> one, though.
Perhaps the DTS does not cover all the quirks that stock OS does for this this box. Some time you can find out some extra steps that stock OS performs (running some script) by examining the serial boot log.
Case in point, with the NSA325 box. Stock OS executes a network PHY psequence during boot up that is quite quirky. My NSA325 DTS version does try to mimic that in the registers initialization but it did not quite work out, so I have a patch in the kernel to execute the sequence.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 November 14, 2020 03:55AM |
Registered: 5 years ago Posts: 180 |
There has been some development which may improve the RN102 performance. See info in the following topic.
https://forum.doozan.com/read.php?2,110849
https://forum.doozan.com/read.php?2,110849
|
Re: Debian on Netgear RN102 November 22, 2020 07:51AM |
Registered: 6 years ago Posts: 157 |
Hi bodhi,
If you build it for RN102 too, I'll be happy to test it.
If you have any idea on how to fix the outstanding fan control issue, please add your best guess for me to test as well. It works with stock firmware, but I haven't figured out how. The package 'libsensors4' is installed, but 'fancontrol' is not:
Regards,
Trond Melen
Quote
I will build the new kernel 5.9.3 with danitool patch, and see if that will make up for the difference.
If you build it for RN102 too, I'll be happy to test it.
Quote
whitepawn
Driver of g762 fan control chip seems not included in kernel i guess.
If you have any idea on how to fix the outstanding fan control issue, please add your best guess for me to test as well. It works with stock firmware, but I haven't figured out how. The package 'libsensors4' is installed, but 'fancontrol' is not:
root@rn102:~# dpkg -l | grep fan ii libsensors4:armel 1:3.4.0-4.netgear1 armel library to read temperature/voltage/fan sensors
Regards,
Trond Melen
