Debian on Netgear RN102
Posted by whitepawn
|
Re: Debian on Netgear RN102 September 04, 2020 04:25AM |
Admin Registered: 13 years ago Posts: 18,848 |
whitepawn,
bodhi Wrote:
-------------------------------------------------------
> There are quite a bit to digest here. So please
> remind me if I have not addressed any issue
> above.
>
> @whitepawn,
>
> Your log was cut off on the right so I could not
> see what capacity the Ultra Fit is.
>
> - The 32GB Ultra Fit has problems using as rootfs.
> This also likely has something to do with it is a
> USB 3.0 drive, plugged into a USB 2.0 port. I
> cannot prove it, but my hunch is the controller in
> the drive has some problem. I have seen this error
> with the Sandisk Ultra Fit 32GB. Just clone it to
> another USB drive is usually make things go
> smoother.
>
> - If you have not enable swap, do that and use
> swap file that is at least 4x the memory. So the
> swap file should be at least 2GB.
>
>
> Update: I can see it
> now by putting your post in edit mode. It is a 16
> GB Ultra Fit. A very good USB drive (this is what
> I use for rootfs in ~10 of my boxes). But to prove
> to yourself that the system does not have any
> problem, you could try to use a Sandisk USB 2.0
> thumb drive.
>
>
In addition to what I said in the post above. You should upgrade Debian before doing stress tests.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
bodhi Wrote:
-------------------------------------------------------
> There are quite a bit to digest here. So please
> remind me if I have not addressed any issue
> above.
>
> @whitepawn,
>
> Your log was cut off on the right so I could not
> see what capacity the Ultra Fit is.
>
> - The 32GB Ultra Fit has problems using as rootfs.
> This also likely has something to do with it is a
> USB 3.0 drive, plugged into a USB 2.0 port. I
> cannot prove it, but my hunch is the controller in
> the drive has some problem. I have seen this error
> with the Sandisk Ultra Fit 32GB. Just clone it to
> another USB drive is usually make things go
> smoother.
>
> - If you have not enable swap, do that and use
> swap file that is at least 4x the memory. So the
> swap file should be at least 2GB.
>
>
> Update: I can see it
> now by putting your post in edit mode. It is a 16
> GB Ultra Fit. A very good USB drive (this is what
> I use for rootfs in ~10 of my boxes). But to prove
> to yourself that the system does not have any
> problem, you could try to use a Sandisk USB 2.0
> thumb drive.
>
>
In addition to what I said in the post above. You should upgrade Debian before doing stress tests.
apt-get update apt-get upgrade
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 04, 2020 05:09AM |
Registered: 7 years ago Posts: 181 |
Hi bodhi,
I did some days ago and ended up with these results:
I also build a 'zImage':
What I couldn't figure out was how to assemble your tarball from these results, so the normal kernel installation procedures can be followed. I would appreciate you sharing the details, but maybe it's a "trick of the trade"?
Regards,
Trond Melen
Quote
Get the mainline kernel source tree for 5.8.5 from kernel.org (or clone Linux GitHub). Apply the patch. Copy the config to the source tree. And build.
I did some days ago and ended up with these results:
scripts/config --disable DEBUG_INFO make clean make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j $(nproc) bindeb-pkg ls -lF .. total 32836 drwxrwxr-x 25 tme tme 1240 aug. 31 08:34 linux-5.8.5/ -rw-rw-r-- 1 tme tme 5538 aug. 31 08:34 linux-5.8.5-mvebu-tld-1_5.8.5-mvebu-tld-1-2_armhf.buildinfo -rw-rw-r-- 1 tme tme 2097 aug. 31 08:34 linux-5.8.5-mvebu-tld-1_5.8.5-mvebu-tld-1-2_armhf.changes -rw-r--r-- 1 tme tme 7544856 aug. 31 08:34 linux-headers-5.8.5-mvebu-tld-1_5.8.5-mvebu-tld-1-2_armhf.deb -rw-r--r-- 1 tme tme 24979452 aug. 31 08:34 linux-image-5.8.5-mvebu-tld-1_5.8.5-mvebu-tld-1-2_armhf.deb -rw-r--r-- 1 tme tme 1081240 aug. 31 08:34 linux-libc-dev_5.8.5-mvebu-tld-1-2_armhf.deb
I also build a 'zImage':
time make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage cp arch/arm/boot/zImage ../linux-zImage-5.8.5-mvebu-tld-1_5.8.5-mvebu-tld-1
What I couldn't figure out was how to assemble your tarball from these results, so the normal kernel installation procedures can be followed. I would appreciate you sharing the details, but maybe it's a "trick of the trade"?
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 September 04, 2020 07:04AM |
Registered: 5 years ago Posts: 73 |
Bodhi,
I have also tried with Kingston and Toshiba drives which are USB3.0 same result happened so i went to store and bought new Sandisk 16 GB 2.0 flash disk and cloned my existing Sandisk USB3.0 to it.
Same results are happened with new Sandisk USB 2.0 also but more late then USB 3.0 Sandisk.(With USB 3.0 Lets say 2 minutes, wtih USB 2.0 15 minutes.Here is dmesg:
Here is error log from usb serial console:
I have updated Debian 10 Buster before making any tests:
Haven't tried swap yet. I am still investigating.
I have missed your patch file, sorry.
EDIT:
Tried these so far:
-Checked voltage of USB port 5.05v which is fine.
-Edited USB max_sectors size to 16 which fails and then to 8 also fails again:
-Tried 2 USB hubs which are USB2.0 didn't help.I cloned rootfs to Sandisk 16 GB microsd card and connected front usb via 3 different sd card readers, one sd reader even didn't boot.Didn't help.
-Tried with below usb sticks:
My first USB 3.0 Sandisk Cruzer Fit 16 GB same kernel error.
USB 3.0 Kingston DataTraveller 16GB same kernel error.
USB 3.0 Toshiba TransMemory16 GB same kernel error.
USB 2.0 Sandisk Cruzer Blade 16 GB same kernel error but lately.
-Tried to blacklist orion_ehci kernel module in:
blacklist orion_ehci
Didn't help also.But i am not sure it is properly blacklisted.
Tried with 1GB swap file on rootfs same issue.
Any suggestions are welcome.
By the way since i am a hardware guy more than software maybe i can add sdio interface to this device such as Buffalo LS421DE (Same SoC Armada 370 https://openwrt.org/toh/buffalo/ls421de ) but to find out which gpio pins are sdio pins on RN102 i need to probe them.I have a pretty good idea where they can be but i cannot test them without probing gpio pins.I have attached my guessed resistor area in attachment.
I needed a script like this:(https://openwrt.org/docs/techref/hardware/port.gpio)
Will this script works on this device bodhi?Also are sdio drivers included in kernel?
Edited 1 time(s). Last edit at 09/04/2020 02:15PM by whitepawn.
I have also tried with Kingston and Toshiba drives which are USB3.0 same result happened so i went to store and bought new Sandisk 16 GB 2.0 flash disk and cloned my existing Sandisk USB3.0 to it.
Same results are happened with new Sandisk USB 2.0 also but more late then USB 3.0 Sandisk.(With USB 3.0 Lets say 2 minutes, wtih USB 2.0 15 minutes.Here is dmesg:
root@debian:~# 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: 495144K/524288K available (10240K kernel code, 1012K rwdata, 3072K rodata, 1024K init, 342K bss, 29144K 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.024013] Calibrating delay loop (skipped), value calculated using timer frequency.. 37.49 BogoMIPS (lpj=187492)
[ 0.034143] pid_max: default: 32768 minimum: 301
[ 0.039209] LSM: Security Framework initializing
[ 0.044156] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.051484] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.060286] CPU: Testing write buffer coherency: ok
[ 0.065728] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.072061] Setting up static identity map for 0x100000 - 0x100060
[ 0.078749] mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1
[ 0.084181] mvebu-pmsu: Initializing Power Management Service Unit
[ 0.090705] rcu: Hierarchical SRCU implementation.
[ 0.098524] smp: Bringing up secondary CPUs ...
[ 0.103416] smp: Brought up 1 node, 1 CPU
[ 0.107712] SMP: Total of 1 processors activated (37.49 BogoMIPS).
[ 0.114031] CPU: All CPU(s) started in SVC mode.
[ 0.119576] devtmpfs: initialized
[ 0.128179] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[ 0.137105] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.146877] futex hash table entries: 256 (order: 2, 16384 bytes, linear)
[ 0.154088] 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.481802] pinctrl core: initialized pinctrl subsystem
[ 0.488936] thermal_sys: Registered thermal governor 'step_wise'
[ 0.489675] NET: Registered protocol family 16
[ 0.502532] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.510422] audit: initializing netlink subsys (disabled)
[ 0.516389] audit: type=2000 audit(0.490:1): state=initialized audit_enabled=0 res=1
[ 0.526684] cpuidle: using governor ladder
[ 0.532701] cpuidle: using governor menu
[ 0.537215] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.809650] raid6: int32x8 gen() 214 MB/s
[ 0.978895] raid6: int32x8 xor() 135 MB/s
[ 1.148656] raid6: int32x4 gen() 224 MB/s
[ 1.318719] raid6: int32x4 xor() 151 MB/s
[ 1.488580] raid6: int32x2 gen() 414 MB/s
[ 1.658563] raid6: int32x2 xor() 217 MB/s
[ 1.828602] raid6: int32x1 gen() 430 MB/s
[ 1.998591] raid6: int32x1 xor() 201 MB/s
[ 2.003122] raid6: using algorithm int32x1 gen() 430 MB/s
[ 2.008694] raid6: .... xor() 201 MB/s, rmw enabled
[ 2.013779] raid6: using intx1 recovery algorithm
[ 2.020110] vgaarb: loaded
[ 2.025077] SCSI subsystem initialized
[ 2.030001] libata version 3.00 loaded.
[ 2.030331] usbcore: registered new interface driver usbfs
[ 2.036028] usbcore: registered new interface driver hub
[ 2.043227] usbcore: registered new device driver usb
[ 2.049927] mc: Linux media interface: v0.10
[ 2.055347] videodev: Linux video capture interface: v2.00
[ 2.061824] pps_core: LinuxPPS API ver. 1 registered
[ 2.066993] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 2.076728] PTP clock support registered
[ 2.084555] clocksource: Switched to clocksource armada_370_xp_clocksource
[ 3.073697] VFS: Disk quotas dquot_6.6.0
[ 3.078083] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 3.112822] NET: Registered protocol family 2
[ 3.120351] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 3.129067] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 3.137123] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 3.144313] TCP: Hash tables configured (established 4096 bind 4096)
[ 3.151412] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 3.158222] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 3.165459] NET: Registered protocol family 1
[ 3.170836] RPC: Registered named UNIX socket transport module.
[ 3.176974] RPC: Registered udp transport module.
[ 3.181902] RPC: Registered tcp transport module.
[ 3.186850] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.193368] PCI: CLS 0 bytes, default 64
[ 3.197982] Trying to unpack rootfs image as initramfs...
[ 3.735348] Freeing initrd memory: 7744K
[ 3.739873] NetWinder Floating Point Emulator V0.97 (double precision)
[ 3.746804] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 3.757739] Initialise system trusted keyrings
[ 3.762477] Key type blacklist registered
[ 3.768997] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[ 3.775794] zbud: loaded
[ 3.780401] NFS: Registering the id_resolver key type
[ 3.786103] Key type id_resolver registered
[ 3.790560] Key type id_legacy registered
[ 3.794992] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 3.801752] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 3.808628] jffs2: version 2.2. (NAND) (SUMMARY) \xc2\xa9 2001-2006 Red Hat, Inc.
[ 3.816918] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 3.823639] orangefs_init: module version upstream loaded
[ 3.903317] async_tx: api initialized (async)
[ 3.908023] Key type asymmetric registered
[ 3.912398] Asymmetric key parser 'x509' registered
[ 3.917743] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[ 3.925434] io scheduler bfq registered
[ 3.932446] armada-370-pinctrl d0018000.pin-ctrl: registered pinctrl driver
[ 3.948391] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00
[ 3.956187] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 3.961836] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[ 3.969111] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 3.975658] pci_bus 0000:00: scanning bus
[ 3.975808] pci 0000:00:01.0: [11ab:6710] type 01 class 0x060400
[ 3.981960] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 3.989378] pci 0000:00:02.0: [11ab:6710] type 01 class 0x060400
[ 3.995751] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 4.004042] pci_bus 0000:00: fixups for bus
[ 4.004062] PCI: bus0: Fast back to back transfers disabled
[ 4.009917] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[ 4.009926] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.017964] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[ 4.017972] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.025994] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[ 4.026307] pci_bus 0000:01: scanning bus
[ 4.026360] pci 0000:01:00.0: [1b4b:9170] type 00 class 0x010601
[ 4.032512] pci 0000:01:00.0: reg 0x10: [io 0xfffffff8-0xffffffff]
[ 4.039075] pci 0000:01:00.0: reg 0x14: [io 0xfffffffc-0xffffffff]
[ 4.045538] pci 0000:01:00.0: reg 0x18: [io 0xfffffff8-0xffffffff]
[ 4.051903] pci 0000:01:00.0: reg 0x1c: [io 0xfffffffc-0xffffffff]
[ 4.058350] pci 0000:01:00.0: reg 0x20: [io 0xfffffff0-0xffffffff]
[ 4.064771] pci 0000:01:00.0: reg 0x24: [mem 0x40000000-0x400001ff]
[ 4.071136] pci 0000:01:00.0: reg 0x30: [mem 0xd0000000-0xd000ffff pref]
[ 4.077972] pci 0000:01:00.0: Enabling fixed DMA alias to 00.1
[ 4.083991] pci 0000:01:00.0: PME# supported from D3hot
[ 4.089455] pci 0000:01:00.0: PME# disabled
[ 4.089899] pci 0000:00:01.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[ 4.125634] pci_bus 0000:01: fixups for bus
[ 4.125649] PCI: bus1: Fast back to back transfers disabled
[ 4.131375] pci_bus 0000:01: bus scan returning with max=01
[ 4.131388] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 4.138141] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[ 4.138437] pci_bus 0000:02: scanning bus
[ 4.138477] pci 0000:02:00.0: [1b73:1009] type 00 class 0x0c0330
[ 4.144811] pci 0000:02:00.0: reg 0x10: [mem 0x42000000-0x4200ffff 64bit]
[ 4.151657] pci 0000:02:00.0: reg 0x18: [mem 0x42010000-0x42010fff 64bit]
[ 4.158601] pci 0000:02:00.0: reg 0x20: [mem 0x42011000-0x42011fff 64bit]
[ 4.165607] pci 0000:02:00.0: supports D1
[ 4.169905] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold
[ 4.176403] pci 0000:02:00.0: PME# disabled
[ 4.176858] pci 0000:00:02.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[ 4.215632] pci_bus 0000:02: fixups for bus
[ 4.215647] PCI: bus2: Fast back to back transfers disabled
[ 4.221373] pci_bus 0000:02: bus scan returning with max=02
[ 4.221385] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 4.228137] pci_bus 0000:00: bus scan returning with max=02
[ 4.228208] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff]
[ 4.235180] pci 0000:00:02.0: BAR 14: assigned [mem 0xf8100000-0xf81fffff]
[ 4.242092] pci 0000:00:01.0: BAR 13: assigned [io 0x10000-0x10fff]
[ 4.248578] pci 0000:00:01.0: BAR 6: assigned [mem 0xf8200000-0xf82007ff pref]
[ 4.255831] pci 0000:00:02.0: BAR 6: assigned [mem 0xf8300000-0xf83007ff pref]
[ 4.263068] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8000000-0xf800ffff pref]
[ 4.270317] pci 0000:01:00.0: BAR 5: assigned [mem 0xf8010000-0xf80101ff]
[ 4.277172] pci 0000:01:00.0: BAR 4: assigned [io 0x10000-0x1000f]
[ 4.283532] pci 0000:01:00.0: BAR 0: assigned [io 0x10010-0x10017]
[ 4.289909] pci 0000:01:00.0: BAR 2: assigned [io 0x10018-0x1001f]
[ 4.296286] pci 0000:01:00.0: BAR 1: assigned [io 0x10020-0x10023]
[ 4.302646] pci 0000:01:00.0: BAR 3: assigned [io 0x10024-0x10027]
[ 4.309022] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 4.314191] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 4.320567] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff]
[ 4.327425] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8100000-0xf810ffff 64bit]
[ 4.334759] pci 0000:02:00.0: BAR 2: assigned [mem 0xf8110000-0xf8110fff 64bit]
[ 4.342074] pci 0000:02:00.0: BAR 4: assigned [mem 0xf8111000-0xf8111fff 64bit]
[ 4.349405] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 4.354593] pci 0000:00:02.0: bridge window [mem 0xf8100000-0xf81fffff]
[ 4.361529] pcieport 0000:00:01.0: assign IRQ: got 0
[ 4.361546] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[ 4.367793] pcieport 0000:00:01.0: enabling bus mastering
[ 4.367880] pcieport 0000:00:02.0: assign IRQ: got 0
[ 4.367894] pcieport 0000:00:02.0: enabling device (0140 -> 0142)
[ 4.374102] pcieport 0000:00:02.0: enabling bus mastering
[ 4.374153] pci 0000:00:02.0: enabling bus mastering
[ 4.375403] mv_xor d0060800.xor: Marvell shared XOR driver
[ 4.445943] mv_xor d0060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 4.456936] mv_xor d0060900.xor: Marvell shared XOR driver
[ 4.525968] mv_xor d0060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 4.726531] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 4.737264] printk: console [ttyS0] disabled
[ 4.763120] d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 19, base_baud = 12500000) is a 16550A
[ 4.772133] printk: console [ttyS0] enabled
[ 4.781332] printk: bootconsole [earlycon0] disabled
[ 4.793974] ahci 0000:01:00.0: assign IRQ: got 41
[ 4.793996] ahci 0000:01:00.0: version 3.0
[ 4.794018] pci 0000:00:01.0: enabling bus mastering
[ 4.794032] ahci 0000:01:00.0: enabling device (0146 -> 0147)
[ 4.801136] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[ 4.809377] ahci 0000:01:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[ 4.820781] scsi host0: ahci
[ 4.825548] scsi host1: ahci
[ 4.829481] ata1: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010100 irq 42
[ 4.837301] ata2: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010180 irq 42
[ 4.845625] sata_mv d00a0000.sata: version 1.28
[ 4.845839] sata_mv d00a0000.sata: slots 32 ports 1
[ 4.854064] scsi host2: sata_mv
[ 4.858459] ata3: SATA max UDMA/133 irq 27
[ 4.864512] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xf1
[ 4.872061] nand: Micron MT29F1G08ABADAWP
[ 4.876638] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 4.885050] Bad block table found at page 65472, version 0x01
[ 4.891513] Bad block table found at page 65408, version 0x01
[ 4.897866] 5 cmdlinepart partitions found on MTD device pxa3xx_nand-0
[ 4.904522] Creating 5 MTD partitions on "pxa3xx_nand-0":
[ 4.910205] 0x000000000000-0x000000180000 : "u-boot"
[ 4.917710] 0x000000180000-0x0000001a0000 : "u-boot-env"
[ 4.926045] 0x000000200000-0x000000800000 : "uImage"
[ 4.933910] 0x000000800000-0x000000c00000 : "minirootfs"
[ 4.942280] 0x000000c00000-0x000008000000 : "ubifs"
[ 4.951993] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 4.961060] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[ 4.974347] libphy: Fixed MDIO Bus: probed
[ 4.983803] libphy: orion_mdio_bus: probed
[ 4.998546] mvneta d0074000.ethernet eth0: Using random mac address ba:95:3f:38:c4:f4
[ 5.011014] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.018230] ehci-pci: EHCI PCI platform driver
[ 5.023197] ehci-orion: EHCI orion driver
[ 5.028242] orion-ehci d0050000.usb: EHCI Host Controller
[ 5.033888] orion-ehci d0050000.usb: new USB bus registered, assigned bus number 1
[ 5.042010] orion-ehci d0050000.usb: irq 25, io mem 0xd0050000
[ 5.074607] orion-ehci d0050000.usb: USB 2.0 started, EHCI 1.00
[ 5.081109] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[ 5.089452] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.096818] usb usb1: Product: EHCI Host Controller
[ 5.102007] usb usb1: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 ehci_hcd
[ 5.109046] usb usb1: SerialNumber: d0050000.usb
[ 5.115082] hub 1-0:1.0: USB hub found
[ 5.119544] hub 1-0:1.0: 1 port detected
[ 5.125309] xhci_hcd 0000:02:00.0: assign IRQ: got 43
[ 5.125387] xhci_hcd 0000:02:00.0: enabling bus mastering
[ 5.125400] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 5.131382] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 5.139808] xhci_hcd 0000:02:00.0: hcc params 0x200073a1 hci version 0x100 quirks 0x0000000000080010
[ 5.149226] xhci_hcd 0000:02:00.0: enabling Mem-Wr-Inval
[ 5.150054] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[ 5.158452] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.165844] usb usb2: Product: xHCI Host Controller
[ 5.171035] usb usb2: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 xhci-hcd
[ 5.178114] usb usb2: SerialNumber: 0000:02:00.0
[ 5.184056] hub 2-0:1.0: USB hub found
[ 5.188311] ata3: SATA link down (SStatus 0 SControl F300)
[ 5.194373] hub 2-0:1.0: 2 ports detected
[ 5.199850] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 5.205766] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
[ 5.213241] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed
[ 5.219927] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 5.228430] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08
[ 5.236764] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.244060] usb usb3: Product: xHCI Host Controller
[ 5.249246] usb usb3: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 xhci-hcd
[ 5.256268] usb usb3: SerialNumber: 0000:02:00.0
[ 5.262087] hub 3-0:1.0: USB hub found
[ 5.266541] hub 3-0:1.0: 2 ports detected
[ 5.272594] usbcore: registered new interface driver usblp
[ 5.279231] usbcore: registered new interface driver usb-storage
[ 5.286435] mousedev: PS/2 mouse device common for all mice
[ 5.294124] i2c /dev entries driver
[ 5.302695] rtc-ds1307 0-0068: 'wakeup-source' is set, request for an IRQ is disabled!
[ 5.316081] rtc-ds1307 0-0068: registered as rtc0
[ 5.322093] rtc-ds1307 0-0068: setting system clock to 2020-09-04T09:37:54 UTC (1599212274)
[ 5.354612] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 5.361015] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 5.369098] orion_wdt: Initial timeout 229 sec
[ 5.376150] device-mapper: uevent: version 1.0.3
[ 5.381114] ata2.00: ATA-7: ST940210AS, 3.ALC, max UDMA/100
[ 5.387283] ata2.00: 78140160 sectors, multi 0: LBA48 NCQ (depth 32)
[ 5.394306] device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com
[ 5.403610] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 5.410519] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 5.417372] ata2.00: configured for UDMA/100
[ 5.422132] device-mapper: multipath service-time: version 0.3.0 loaded
[ 5.429013] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 5.435346] device-mapper: raid: Loading target version 1.15.1
[ 5.448738] marvell-cesa d0090000.crypto: CESA device successfully registered
[ 5.456764] hid: raw HID events driver (C) Jiri Kosina
[ 5.463384] usbcore: registered new interface driver usbhid
[ 5.469683] usbhid: USB HID core driver
[ 5.474939] drop_monitor: Initializing network drop monitor service
[ 5.482231] NET: Registered protocol family 10
[ 5.487127] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 5.495778] Segment Routing with IPv6
[ 5.499806] RPL Segment Routing with IPv6
[ 5.504259] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 5.512809] NET: Registered protocol family 17
[ 5.518555] 8021q: 802.1Q VLAN Support v1.8
[ 5.523150] Key type dns_resolver registered
[ 5.528132] ThumbEE CPU extension supported.
[ 5.532718] Registering SWP/SWPB emulation handler
[ 5.538338] registered taskstats version 1
[ 5.542763] Loading compiled-in X.509 certificates
[ 5.548351] zswap: loaded using pool lzo/zbud
[ 5.553471] Key type ._fscrypt registered
[ 5.557920] Key type .fscrypt registered
[ 5.562177] Key type fscrypt-provisioning registered
[ 5.570618] Key type big_key registered
[ 5.584463] Key type encrypted registered
[ 5.593491] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 5.687186] usb 1-1: New USB device found, idVendor=0781, idProduct=5567, bcdDevice= 1.00
[ 5.695462] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5.702732] usb 1-1: Product: Cruzer Blade
[ 5.707201] usb 1-1: Manufacturer: SanDisk
[ 5.711624] usb 1-1: SerialNumber: 4C530000260206220135
[ 5.718819] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 5.726706] scsi host3: usb-storage 1-1:1.0
[ 5.747997] ata1.00: HPA detected: current 231496650, native 234441648
[ 5.755246] ata1.00: ATA-7: TOSHIBA MK1234GSX, AH001D, max UDMA/100
[ 5.761681] ata1.00: 231496650 sectors, multi 16: LBA48 NCQ (depth 32), AA
[ 5.770674] ata1.00: configured for UDMA/100
[ 5.786417] scsi 0:0:0:0: Direct-Access ATA TOSHIBA MK1234GS 1D PQ: 0 ANSI: 5
[ 5.798013] sd 0:0:0:0: [sda] 231496650 512-byte logical blocks: (119 GB/110 GiB)
[ 5.807192] scsi 1:0:0:0: Direct-Access ATA ST940210AS C PQ: 0 ANSI: 5
[ 5.817173] sd 0:0:0:0: [sda] Write Protect is off
[ 5.822254] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 5.825893] sd 1:0:0:0: [sdb] 78140160 512-byte logical blocks: (40.0 GB/37.3 GiB)
[ 5.836230] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5.845589] sd 1:0:0:0: [sdb] Write Protect is off
[ 5.850669] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 5.851027] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5.918358] sda: sda1 sda2 < sda5 >
[ 5.928289] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 6.027568] GPT:Primary header thinks Alt. header is not at the end of the disk.
[ 6.035129] GPT:78140158 != 78140159
[ 6.039073] GPT:Alternate GPT header not at the end of the disk.
[ 6.045297] GPT:78140158 != 78140159
[ 6.049237] GPT: Use GNU Parted to correct GPT errors.
[ 6.054733] sdb: sdb1
[ 6.061468] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 6.070235] Freeing unused kernel memory: 1024K
[ 6.096853] Checked W+X mappings: passed, no W+X pages found
[ 6.102757] Run /init as init process
[ 6.107028] with arguments:
[ 6.107037] /init
[ 6.107043] with environment:
[ 6.107048] HOME=/
[ 6.107052] TERM=linux
[ 6.107056] reason=normal
[ 6.107061] bdtype=rn102
[ 6.335399] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 6.343949] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 6.362845] random: udevadm: uninitialized urandom read (16 bytes read)
[ 6.746625] scsi 3:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
[ 6.780272] sd 3:0:0:0: [sdc] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB)
[ 6.803972] sd 3:0:0:0: [sdc] Write Protect is off
[ 6.819262] sd 3:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 6.820586] sd 3:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 6.897805] sdc: sdc1
[ 6.912747] random: fast init done
[ 6.923252] sd 3:0:0:0: [sdc] Attached SCSI removable disk
[ 8.041642] usbcore: registered new interface driver uas
[ 21.094128] process '/bin/fstype' started with executable stack
[ 24.147528] EXT4-fs (sdc1): mounting ext3 file system using the ext4 subsystem
[ 24.193779] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[ 24.510161] random: crng init done
[ 24.513962] random: 7 urandom warning(s) missed due to ratelimiting
[ 25.303280] 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)
[ 25.331976] systemd[1]: Detected architecture arm.
[ 25.434036] systemd[1]: Set hostname to <debian>.
[ 26.763183] 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.
[ 26.780064] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[ 27.270584] 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.
[ 27.403876] systemd[1]: Listening on udev Control Socket.
[ 27.448826] systemd[1]: Created slice User and Session Slice.
[ 27.485178] systemd[1]: Reached target Slices.
[ 27.527173] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 28.679480] EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro
[ 30.375951] systemd[1]: Mounted /tmp.
[ 30.402053] systemd[1]: Reached target Local File Systems.
[ 30.444680] systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
[ 30.553440] systemd[1]: Starting Preprocess NFS configuration...
[ 30.635828] systemd[1]: Started udev Kernel Device Manager.
[ 30.691849] systemd[1]: Started Journal Service.
[ 31.342977] systemd-journald[1559]: Received request to flush runtime journal from PID 1
[ 35.344884] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 35.397823] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 35.503047] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 37.725354] Btrfs loaded, crc32c=crc32c-generic
[ 37.759865] BTRFS: device label seagate devid 1 transid 7 /dev/sdb1 scanned by systemd-udevd (1582)
[ 53.504998] mvneta d0074000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL)
[ 53.515027] mvneta d0074000.ethernet eth0: configuring for phy/rgmii-id link mode
[ 55.625399] mvneta d0074000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 55.633624] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 67.407297] NFSD: Using UMH upcall client tracking operations.
[ 67.413411] NFSD: starting 90-second grace period (net f0000021)
[ 68.638251] fbcon: Taking over console
Here is error log from usb serial console:
Last login: Fri Sep 4 00:21:18 PDT 2020 from 192.168.2.243 on pts/1 Linux debian 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. debian 192.168.2.110 NETGEAR ReadyNAS 102 eck resulted in Commit a transient machine-id on disk being skipped. 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 Fri Sep 4 04:37:52 PDT 2020 up 1 hour, 50 minutes root@debian:~# [ 7666.974668][ T1445] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 7672.174734][ T1445] usb 1-1: device descriptor read/64, error -110 [ 7687.534697][ T1445] usb 1-1: device descriptor read/64, error -110 [ 7687.804718][ T1445] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 7692.974658][ T1445] usb 1-1: device descriptor read/64, error -110 [ 7708.334659][ T1445] usb 1-1: device descriptor read/64, error -110 [ 7708.604707][ T1445] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 7713.707828][ T1445] usb 1-1: device descriptor read/8, error -110 [ 7718.907946][ T1445] usb 1-1: device descriptor read/8, error -110 [ 7719.174702][ T1445] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 7724.267820][ T1445] usb 1-1: device descriptor read/8, error -110 [ 7729.467821][ T1445] usb 1-1: device descriptor read/8, error -110 [ 7729.585149][ T1876] usb 1-1: USB disconnect, device number 2 [ 7729.624733][ T1495] blk_update_request: I/O error, dev sdc, sector 38984 op 0x1:(WRITE) flags 0x800 phys_seg 8 prio class 0 [ 7729.635372][ T1495] blk_update_request: I/O error, dev sdc, sector 25434728 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 7729.646083][ T1879] blk_update_request: I/O error, dev sdc, sector 18457880 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0 [ 7729.657023][ T1495] blk_update_request: I/O error, dev sdc, sector 29367416 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 7729.667622][ T1877] blk_update_request: I/O error, dev sdc, sector 29367416 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 7729.679410][ T1559] blk_update_request: I/O error, dev sdc, sector 18465584 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 [ 7729.690202][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308199) [ 7729.701025][ T1559] Buffer I/O error on device sdc1, logical block 2307942 [ 7729.707462][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308200) [ 7729.718277][ T1559] Buffer I/O error on device sdc1, logical block 2307943 [ 7729.724704][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308201) [ 7729.735510][ T1559] Buffer I/O error on device sdc1, logical block 2307944 [ 7729.741875][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308202) [ 7729.752686][ T1559] Buffer I/O error on device sdc1, logical block 2307945 [ 7729.759114][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308203) [ 7729.769922][ T1559] Buffer I/O error on device sdc1, logical block 2307946 [ 7729.776344][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308204) [ 7729.787165][ T1559] Buffer I/O error on device sdc1, logical block 2307947 [ 7729.793530][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308205) [ 7729.804375][ T1559] Buffer I/O error on device sdc1, logical block 2307948 [ 7729.810814][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308206) [ 7729.821624][ T1559] Buffer I/O error on device sdc1, logical block 2307949 [ 7729.828046][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308207) [ 7729.838852][ T1559] Buffer I/O error on device sdc1, logical block 2307950 [ 7729.845273][ T1559] EXT4-fs warning (device sdc1): ext4_end_bio:349: I/O error 10 writing to inode 522254 starting block 2308208) [ 7729.856081][ T1559] Buffer I/O error on device sdc1, logical block 2307951 [ 7729.862730][ T1737] blk_update_request: I/O error, dev sdc, sector 25171968 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 [ 7729.885304][ T1495] blk_update_request: I/O error, dev sdc, sector 29106072 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 7729.895887][ T1754] blk_update_request: I/O error, dev sdc, sector 19404800 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 [ 7729.906760][ T1737] EXT4-fs error (device sdc1): __ext4_find_entry:1537: inode #783361: comm ntpd: reading directory lblock 0 [ 7729.924827][ T1495] blk_update_request: I/O error, dev sdc, sector 18458120 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0 [ 7729.964871][ T1754] EXT4-fs error (device sdc1): __ext4_find_entry:1537: inode #603841: comm cron: reading directory lblock 0 [ 7729.993286][ T1737] Buffer I/O error on dev sdc1, logical block 0, lost sync page write [ 7730.024921][ T1754] EXT4-fs (sdc1): previous I/O error to superblock detected [ 7730.055703][ T1526] JBD2: Detected IO errors while flushing file data on sdc1-8 [ 7730.062490][ T1526] Aborting journal on device sdc1-8. [ 7730.074818][ T1754] Buffer I/O error on dev sdc1, logical block 0, lost sync page write [ 7730.082290][ T1737] EXT4-fs (sdc1): I/O error while writing superblock [ 7730.126972][ T1526] Buffer I/O error on dev sdc1, logical block 1436, lost sync page write [ 7730.144777][ T1526] JBD2: Error -5 detected when updating journal superblock for sdc1-8. [ 7730.152327][ T1737] EXT4-fs (sdc1): Remounting filesystem read-only [ 7730.158273][ T1754] EXT4-fs (sdc1): Remounting filesystem read-only [ 7730.296057][ T1842] EXT4-fs error (device sdc1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 64, block_bitmap = 2097152 [ 7730.658636][ T1842] Buffer I/O error on dev sdc1, logical block 0, lost sync page write [ 7730.718640][ T1842] EXT4-fs (sdc1): I/O error while writing superblock [ 7730.902237][ T1842] EXT4-fs error (device sdc1): ext4_discard_preallocations:4185: comm stress: Error -5 loading buddy information for 64 [ 7731.190649][ T1842] Buffer I/O error on dev sdc1, logical block 0, lost sync page write [ 7731.250022][ T1842] EXT4-fs (sdc1): I/O error while writing superblock [ 7731.356763][ T1842] EXT4-fs error (device sdc1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 64, block_bitmap = 2097152 [ 7731.518835][ T1526] JBD2: Detected IO errors while flushing file data on sdc1-8 [ 7731.634785][ T1842] EXT4-fs error (device sdc1): ext4_discard_preallocations:4185: comm stress: Error -5 loading buddy information for 64 [ 7731.804672][ T1876] usb 1-1: new high-speed USB device number 3 using orion-ehci [ 7731.894731][ T1842] EXT4-fs error (device sdc1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 64, block_bitmap = 2097152 [ 7732.054698][ T1842] EXT4-fs error (device sdc1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap for 64 [ 7732.234773][ T1842] EXT4-fs error (device sdc1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 70, block_bitmap = 2293760 [ 7732.394695][ T1842] EXT4-fs error (device sdc1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap for 70 [ 7734.303843][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 7734.311561][ T1] CPU: 0 PID: 1 Comm: systemd Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 7734.319016][ T1] Hardware name: Marvell Armada 370/XP (Device Tree) [ 7734.325066][ T1] [<c0115b10>] (unwind_backtrace) from [<c01106d8>] (show_stack+0x10/0x14) [ 7734.332859][ T1] [<c01106d8>] (show_stack) from [<c05f0d84>] (dump_stack+0x80/0x9c) [ 7734.340172][ T1] [<c05f0d84>] (dump_stack) from [<c0129088>] (panic+0xe4/0x2f0) [ 7734.347158][ T1] [<c0129088>] (panic) from [<c012c914>] (do_exit+0x1b4/0xa28) [ 7734.353977][ T1] [<c012c914>] (do_exit) from [<c012dde0>] (do_group_exit+0x58/0xb8) [ 7734.361281][ T1] [<c012dde0>] (do_group_exit) from [<c01391ac>] (get_signal+0x224/0x6d4) [ 7734.368981][ T1] [<c01391ac>] (get_signal) from [<c010fc1c>] (do_work_pending+0xd8/0x438) [ 7734.376759][ T1] [<c010fc1c>] (do_work_pending) from [<c01000cc>] (slow_work_pending+0xc/0x20) [ 7734.384931][ T1] Exception stack(0xdf487fb0 to 0xdf487ff8) [ 7734.390228][ T1] 7fa0: 00000007 0000003a 00000010 005a2d40 [ 7734.398403][ T1] 7fc0: 005dfbb8 00000000 b6ffc968 00503e09 bea39990 00000000 00000000 bea39ab0 [ 7734.406577][ T1] 7fe0: b6ed7b30 be23a158 b6effca1 0053cdfc 00000030 ffffffff [ 7734.413328][ T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
I have updated Debian 10 Buster before making any tests:
root@debian:~# hostnamectl
Static hostname: debian
Icon name: computer
Machine ID: 50b0e021e74b403c9865b8f1b7b764ad
Boot ID: efa14771da69438ab7113c7feb1fa058
Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 5.8.5-mvebu-370xp-tld-1
Architecture: arm
Haven't tried swap yet. I am still investigating.
I have missed your patch file, sorry.
EDIT:
Tried these so far:
-Checked voltage of USB port 5.05v which is fine.
-Edited USB max_sectors size to 16 which fails and then to 8 also fails again:
echo 16 > /sys/block/sdc/device/max_sectors echo 8 > /sys/block/sdc/device/max_sectors
-Tried 2 USB hubs which are USB2.0 didn't help.I cloned rootfs to Sandisk 16 GB microsd card and connected front usb via 3 different sd card readers, one sd reader even didn't boot.Didn't help.
-Tried with below usb sticks:
My first USB 3.0 Sandisk Cruzer Fit 16 GB same kernel error.
USB 3.0 Kingston DataTraveller 16GB same kernel error.
USB 3.0 Toshiba TransMemory16 GB same kernel error.
USB 2.0 Sandisk Cruzer Blade 16 GB same kernel error but lately.
-Tried to blacklist orion_ehci kernel module in:
/etc/modprobe.d/blacklist.confblacklist.conf doesn't exist so i made a new file with nano which contains:
blacklist orion_ehci
Didn't help also.But i am not sure it is properly blacklisted.
Tried with 1GB swap file on rootfs same issue.
Any suggestions are welcome.
By the way since i am a hardware guy more than software maybe i can add sdio interface to this device such as Buffalo LS421DE (Same SoC Armada 370 https://openwrt.org/toh/buffalo/ls421de ) but to find out which gpio pins are sdio pins on RN102 i need to probe them.I have a pretty good idea where they can be but i cannot test them without probing gpio pins.I have attached my guessed resistor area in attachment.
I needed a script like this:(https://openwrt.org/docs/techref/hardware/port.gpio)
#!/bin/sh
GPIOBASE=`cat /sys/class/gpio/gpiochip*/base | head -n1`
GPIOmin=`expr $1 + $GPIOBASE`
GPIOmax=`expr $2 + $GPIOBASE`
nums=`seq $GPIOmin $GPIOmax`
cd /sys/class/gpio
for i in $nums; do
echo $i > export; echo out >gpio$i/direction
done
while true; do
for i in $nums; do
echo 0 > gpio$i/value
done
sleep 1
for i in $nums; do
echo 1 > gpio$i/value
done
sleep
Will this script works on this device bodhi?Also are sdio drivers included in kernel?
Edited 1 time(s). Last edit at 09/04/2020 02:15PM by whitepawn.
|
Re: Debian on Netgear RN102 September 04, 2020 04:21PM |
Admin Registered: 13 years ago Posts: 18,848 |
whitepawn,
> -Tried 2 USB hubs which are USB2.0 didn't help.I
> cloned rootfs to Sandisk 16 GB microsd card and
> connected front usb via 3 different sd card
> readers, one sd reader even didn't boot.Didn't
> help.
Usually I would try to use a new USB 3.0 hub, and plug in USB 3.0 rootfs (to eliminate the controller problem in negotiating speed).
OK so looks like you have tried most of the possible solutions. There is one more I would do: remove systemd. Boot with sysvinit and see if the problem persists. systemd has bugs, from time to time they do surface. If you run with sysvinit and still see the problem, I would suspect the USB port (i.e. hardware).
If you could, use a spare HDD and fornat it as single Ext3 partition. Off-line, copy the rootfs over (as root, use cp -aR) (or create tarball backup and restore).
Most defitely, we could get the HDD rootfs boot with some minor changes in u-boot envs.
> Will this script works on this device bodhi?Also
> are sdio drivers included in kernel?
Yes for both.
The script looks similar to something I had used or wrote a long time ago. The trick is: this only work on GPIOs that have not been assigned a trigger by the kernel. In this case, it should work because this box DTS does not define the GPIOs that we don't know about (that are yet to be found).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> -Tried 2 USB hubs which are USB2.0 didn't help.I
> cloned rootfs to Sandisk 16 GB microsd card and
> connected front usb via 3 different sd card
> readers, one sd reader even didn't boot.Didn't
> help.
Usually I would try to use a new USB 3.0 hub, and plug in USB 3.0 rootfs (to eliminate the controller problem in negotiating speed).
OK so looks like you have tried most of the possible solutions. There is one more I would do: remove systemd. Boot with sysvinit and see if the problem persists. systemd has bugs, from time to time they do surface. If you run with sysvinit and still see the problem, I would suspect the USB port (i.e. hardware).
If you could, use a spare HDD and fornat it as single Ext3 partition. Off-line, copy the rootfs over (as root, use cp -aR) (or create tarball backup and restore).
Most defitely, we could get the HDD rootfs boot with some minor changes in u-boot envs.
> Will this script works on this device bodhi?Also
> are sdio drivers included in kernel?
Yes for both.
The script looks similar to something I had used or wrote a long time ago. The trick is: this only work on GPIOs that have not been assigned a trigger by the kernel. In this case, it should work because this box DTS does not define the GPIOs that we don't know about (that are yet to be found).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 04, 2020 04:26PM |
Admin Registered: 13 years ago Posts: 18,848 |
whitepawn,
> By the way since i am a hardware guy more than
> software maybe i can add sdio interface to this
> device such as Buffalo LS421DE (Same SoC Armada
> 370 https://openwrt.org/toh/buffalo/ls421de ) but
> to find out which gpio pins are sdio pins on RN102
> i need to probe them.I have a pretty good idea
> where they can be but i cannot test them without
> probing gpio pins.I have attached my guessed
> resistor area in attachment.
We love mods like this here :)
See the Wiki thread:
https://forum.doozan.com/read.php?2,23630
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/04/2020 04:33PM by bodhi.
> By the way since i am a hardware guy more than
> software maybe i can add sdio interface to this
> device such as Buffalo LS421DE (Same SoC Armada
> 370 https://openwrt.org/toh/buffalo/ls421de ) but
> to find out which gpio pins are sdio pins on RN102
> i need to probe them.I have a pretty good idea
> where they can be but i cannot test them without
> probing gpio pins.I have attached my guessed
> resistor area in attachment.
We love mods like this here :)
See the Wiki thread:
https://forum.doozan.com/read.php?2,23630
Quote
Under/Over the hood Modding
Pogoplug Pro / V3 Internal SSD Mod
Pogoplug Pro HW mods
USB Wireless Extender (homemade antenna)
Adding 2nd SATA to HP Thin Client T5325 - Mod 1
Adding 2nd SATA to HP Thin Client T5325 - Mod 2
Connect to external SATA drives (or eSATA enclosures) from a Pogoplug V4
Dual Wireless Antenna on Pogo V3
A quiet and movable fan for your desktop case
NSA320 mod for an additional usb port
Pogoplug Pro V3 Dual Antenna for Wifi
Sata DOM hardware mod to Canvio NAS
Reset button for Pogoplug V3 (OXNAS)
Pogo V3 Pro internal Dual SD Card (USB 2.0) using mPCIe slot
Make your inexpensive GoFLEX Home/Net SATA HDD cable
Dell Kace M300 internal HDD Mod, and SSD Mod.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/04/2020 04:33PM by bodhi.
|
Re: Debian on Netgear RN102 September 05, 2020 02:38AM |
Registered: 7 years ago Posts: 181 |
Hi bodhi,
Thanks! Here are my thoughts: The last line on the serial console before the box shuts down is
The first thing that stikes me when comparing my boot log with whitepawn's is that when my kernel shuts down, it has already been multi threading for half a second, while whitpawns kernel is still single threading (with the exception for 'audit' at 0.5 s for both). Why are the two identical kernels booting differently, and could it be that running sata and scsi initialization in parallel with Ethernet initialization makes the latter fail?
The answer to the why might be differences in the number of USB and sata-devices attched to the external connectors, as well as differences in their start up time. I will check if removing or swapping disks makes the failing kernel succeed. I will also clone my USB stick to one or two others and test.
Both 'uImage' and 'uInitrd' were build the same way in the succeeding and failing case:
The failing boot could in principle be due to a difference in the 'mkimage' version. I find this very unlikely, but, for reference, here is the version on my PC running Ubuntu 20.04 desktop:
@whitepawn, when my box is up and running again I will test if I can reproduce you findings.
Regards,
Trond Melen
Quote
Let me take a look at the boot logs to see why it was reset at 54 seconds.
Thanks! Here are my thoughts: The last line on the serial console before the box shuts down is
[ 5.695371][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.MDIO is about managing the Ethernet connection(s). I will check if the presence or absence of a Ethernet link during boot makes any difference, but that would come as a surprise.
The first thing that stikes me when comparing my boot log with whitepawn's is that when my kernel shuts down, it has already been multi threading for half a second, while whitpawns kernel is still single threading (with the exception for 'audit' at 0.5 s for both). Why are the two identical kernels booting differently, and could it be that running sata and scsi initialization in parallel with Ethernet initialization makes the latter fail?
The answer to the why might be differences in the number of USB and sata-devices attched to the external connectors, as well as differences in their start up time. I will check if removing or swapping disks makes the failing kernel succeed. I will also clone my USB stick to one or two others and test.
Both 'uImage' and 'uInitrd' were build the same way in the succeeding and failing case:
cp -a zImage-5.8.5-mvebu-370xp-tld-1 zImage.fdt cat dts/armada-370-netgear-rn102.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.8.5-mvebu-370xp-tld-1 -d zImage.fdt uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.8.5-mvebu-370xp-tld-1 -d initrd.img-5.8.5-mvebu-370xp-tld-1 uInitrdThe only significant differences I am aware of are that the images for the successful boot were build on the box, rather than on the PC, and that the deb-package was already installed on the box when the images were made:
dpkg -i linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.debCould this be decisive? It is straight forward, although time consuming, to try to redo the successful 5.8.5 install using 4.20.6 as a stepping stone, but leave out installing the deb-package before making the 5.8.5 images.
The failing boot could in principle be due to a difference in the 'mkimage' version. I find this very unlikely, but, for reference, here is the version on my PC running Ubuntu 20.04 desktop:
mkimage -V mkimage version 2019.07+dfsg-1ubuntu6I'll keep the forum updated.
@whitepawn, when my box is up and running again I will test if I can reproduce you findings.
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 September 05, 2020 03:32AM |
Admin Registered: 13 years ago Posts: 18,848 |
Trond,
I've looked at your log again and I can see the problem.
That was an important step that you did not do.
> The first thing that stikes me when comparing my
> boot log with whitepawn's is that when my kernel
> shuts down, it has already been multi threading
> for half a second, while whitpawns kernel is still
> single threading (with the exception for 'audit'
> at 0.5 s for both). Why are the two identical
> kernels booting differently,
Not likely this reason, whitepawn was running systemd for init. So the difference in behavior could be that.
====
During weekend, I'll update the installation procedure for Mirabox and will do that for RN102 too and you and whitepawn can proofread and verify it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I've looked at your log again and I can see the problem.
Quote
dpkg -i linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb
That was an important step that you did not do.
> The first thing that stikes me when comparing my
> boot log with whitepawn's is that when my kernel
> shuts down, it has already been multi threading
> for half a second, while whitpawns kernel is still
> single threading (with the exception for 'audit'
> at 0.5 s for both). Why are the two identical
> kernels booting differently,
Not likely this reason, whitepawn was running systemd for init. So the difference in behavior could be that.
====
During weekend, I'll update the installation procedure for Mirabox and will do that for RN102 too and you and whitepawn can proofread and verify it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 05, 2020 04:18AM |
Registered: 7 years ago Posts: 181 |
Hi bodhi,
Thanks!
I consciously postphoned this step until after the first boot (which never finished), convinced that this step on the PC would affect the PC and not the USB stick mounted on /mnt. I need to do a 'chroot' and activate 'qemu' before doing this step, right?
Regards,
Trond Melen
Quotedpkg -i linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.debThat was an important step that you did not do.
Thanks!
I consciously postphoned this step until after the first boot (which never finished), convinced that this step on the PC would affect the PC and not the USB stick mounted on /mnt. I need to do a 'chroot' and activate 'qemu' before doing this step, right?
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 September 05, 2020 06:46AM |
Registered: 7 years ago Posts: 181 |
Hi bodhi,
Test A: Boot with an Ethernet connection from 4 GB USB stick from Innodisk.
First boot: Shutdown after 62 seconds. Last serial console output:
Test B: Boot without any Ethernet connection from 4 GB USB stick from Innodisk.
First boot: Shut down after 62 seconds. Last serial console ouput:
Test C: Boot from 8 GB Patriot USB stick.
First boot: Shut down after 63 seconds. Last serial console output:
Test D: Boot from ScanDisk Ultra 16 GB USB 3.0 stick.
First boot: Shut down after 62 seconds. Last serial console output:
Test E: Boot with HDD in first disk compartment from 4 GB USB stick from Innodisk.
First boot: Shut down after 62 seconds. Last serial console output:
Test F: Boot with one HDD and one SSD in the disk compartments from 4 GB USB stick from Innodisk.
First boot: Shut down after 62 seconds. Last serial console output:
Dull results. The only interesting observations:
I now believe USB, scsi and Ethernet are initialized in parallel multi threaded every time, but that USB and scsi initialization have not yet reported anything on the console when the box shuts down. I believe the reason I got multi threaded output before is that the content of the SSD has changed. It used to have 3 raid partitions, now it has one 'ext4' partition. I cannot change this back right now, but will be able to verify later.
The boot log from the last boot is attached.
Next I will try to verify that
Regards,
Trond Melen
Edited 2 time(s). Last edit at 09/05/2020 06:49AM by tme.
Test A: Boot with an Ethernet connection from 4 GB USB stick from Innodisk.
First boot: Shutdown after 62 seconds. Last serial console output:
[ 5.091676][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.Second boot: Shutdown after 62 seconds. Last serial console output:
[ 5.093709][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.
Test B: Boot without any Ethernet connection from 4 GB USB stick from Innodisk.
First boot: Shut down after 62 seconds. Last serial console ouput:
[ 5.090576][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.Second boot: Shut down after 62 seconds. Last serial console ouput:
[ 5.090576][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.
Test C: Boot from 8 GB Patriot USB stick.
First boot: Shut down after 63 seconds. Last serial console output:
[ 5.092796][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.Second boot: Shut down after 63 seconds. Last serial console output:
[ 5.093619][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.
Test D: Boot from ScanDisk Ultra 16 GB USB 3.0 stick.
First boot: Shut down after 62 seconds. Last serial console output:
[ 5.082870][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.Second boot: Shut down after 62 seconds. Last serial console output:
[ 5.093536][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.
Test E: Boot with HDD in first disk compartment from 4 GB USB stick from Innodisk.
First boot: Shut down after 62 seconds. Last serial console output:
[ 5.092679][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.Second boot: Shut down after 62 seconds. Last serial console output:
[ 5.082392][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.
Test F: Boot with one HDD and one SSD in the disk compartments from 4 GB USB stick from Innodisk.
First boot: Shut down after 62 seconds. Last serial console output:
[ 5.094653][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.Second boot: Shut down after 62 seconds. Last serial console output:
[ 5.092296][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.
Dull results. The only interesting observations:
- The box now shuts down after 62-63 seconds, not after 54 seconds as before.
- There are no traces on the console of parallel initialization of USB, scsi and Ethernet.
I now believe USB, scsi and Ethernet are initialized in parallel multi threaded every time, but that USB and scsi initialization have not yet reported anything on the console when the box shuts down. I believe the reason I got multi threaded output before is that the content of the SSD has changed. It used to have 3 raid partitions, now it has one 'ext4' partition. I cannot change this back right now, but will be able to verify later.
The boot log from the last boot is attached.
Next I will try to verify that
dpkg -i linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.debon the box while running 4.20.6 was the decisive step.
Regards,
Trond Melen
Edited 2 time(s). Last edit at 09/05/2020 06:49AM by tme.
|
Re: Debian on Netgear RN102 September 05, 2020 09:53AM |
Registered: 7 years ago Posts: 181 |
Hi bodhi,
Confirmed. This worked:
I first tried this 'chroot' oneliner, but it failed. Would have been elegant if it worked, though:
Boot time is rougthly 129 seconds:
Attached a list of the 2446 files permanently modified by the steps above (2298 of them are kernel modules *.ko):
Great! Certainly. A pleasure and an honor.
Regards,
Trond Melen
Confirmed. This worked:
sudo su - apt install -y qemu lsblk | egrep -v '^loop' mount /dev/sdb1 /mnt cd /mnt/boot tar xf /tmp/linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2 tar xf linux-dtb-5.8.5-mvebu-370xp-tld-1.tar chroot .. bin/bash dpkg -i /boot/linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb Selecting previously unselected package linux-image-5.8.5-mvebu-370xp-tld-1. (Reading database ... 20007 files and directories currently installed.) Preparing to unpack .../linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb ... Unpacking linux-image-5.8.5-mvebu-370xp-tld-1 (1.0) ... Setting up linux-image-5.8.5-mvebu-370xp-tld-1 (1.0) ... update-initramfs: Generating /boot/initrd.img-5.8.5-mvebu-370xp-tld-1 W: Couldn't identify type of root file system for fsck hook exit cp -a zImage-5.8.5-mvebu-370xp-tld-1 zImage.fdt cat dts/armada-370-netgear-rn102.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.8.5-mvebu-370xp-tld-1 -d zImage.fdt uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.8.5-mvebu-370xp-tld-1 -d initrd.img-5.8.5-mvebu-370xp-tld-1 uInitrd sync && cd && umount /mnt && exitI think the warning from 'dpkg ' can safely be ignored?
I first tried this 'chroot' oneliner, but it failed. Would have been elegant if it worked, though:
chroot .. bin/bash /usr/bin/dpkg -i /boot/linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb /usr/bin/dpkg: /usr/bin/dpkg: cannot execute binary file
Boot time is rougthly 129 seconds:
- U-boot startup: 1 s
- U-boot delay: 3 s
- Copy uImage and uInitrd to RAM: 47 s
- Kernel self un-compress: 4 s
- Kernel boot: 10 s (until power LED steady on)
- Debian initialization: 64 s
Attached a list of the 2446 files permanently modified by the steps above (2298 of them are kernel modules *.ko):
rsync --archive --exclude /var --itemize-changes --dry-run /mnt/ /tmp/rootfs/ | egrep '^>' | sed 's/^............/\//' > /tmp/modified-files.lst
Quote
During weekend, I'll update the installation procedure for Mirabox and will do that for RN102 too and you and whitepawn can proofread and verify it.
Great! Certainly. A pleasure and an honor.
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 September 05, 2020 10:02AM |
Registered: 7 years ago Posts: 181 |
|
Re: Debian on Netgear RN102 September 05, 2020 07:19PM |
Registered: 7 years ago Posts: 181 |
Hi bodhi,
2298 of the permanently modified files are kernel modules *.ko, and 120 of them are device tree blobs *.dtb. The remaining 28 ones are:
The modules in the latest root file system 'Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2' matche kernel 5.2.9 and not 4.20.6, so I still don't understand why kernel 4.20.6 works without installing its deb package (with 'dpkg --install *.deb'), while kernel 5.8.5 doesn't. Is there a missing kernel 5.8.5 module that should have been compiled into the kernel, to make it independent of its module library?
Btw, if the deb-file for kernel 5.2.9 had be included in the root file system, its kernel modules and device tree blobs could have be removed with 'dpkg --remove *.deb' or maybe even with 'auto-remove'. Sounds tidy and clean to me. To be included in the next root file system?
Regards,
Trond Melen
2298 of the permanently modified files are kernel modules *.ko, and 120 of them are device tree blobs *.dtb. The remaining 28 ones are:
zcat /tmp/modified-files.lst.zip | egrep -v '.ko$|.dtb$' /boot/System.map-5.8.5-mvebu-370xp-tld-1 /boot/config-5.8.5-mvebu-370xp-tld-1 /boot/initrd.img-5.8.5-mvebu-370xp-tld-1 /boot/linux-5.8.5-mvebu-370xp-tld-1.patch /boot/linux-dtb-5.8.5-mvebu-370xp-tld-1.tar /boot/linux-headers-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb /boot/linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb /boot/uImage /boot/uInitrd /boot/vmlinuz-5.8.5-mvebu-370xp-tld-1 /boot/zImage-5.8.5-mvebu-370xp-tld-1 /boot/zImage.fdt /etc/apt/apt.conf.d/01autoremove-kernels /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.alias /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.alias.bin /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.builtin /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.builtin.bin /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.builtin.modinfo /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.dep /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.dep.bin /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.devname /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.order /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.softdep /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.symbols /lib/modules/5.8.5-mvebu-370xp-tld-1/modules.symbols.bin /root/.bash_history /usr/share/doc/linux-image-5.8.5-mvebu-370xp-tld-1/changelog.Debian.gz /usr/share/doc/linux-image-5.8.5-mvebu-370xp-tld-1/copyright
The modules in the latest root file system 'Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2' matche kernel 5.2.9 and not 4.20.6, so I still don't understand why kernel 4.20.6 works without installing its deb package (with 'dpkg --install *.deb'), while kernel 5.8.5 doesn't. Is there a missing kernel 5.8.5 module that should have been compiled into the kernel, to make it independent of its module library?
Btw, if the deb-file for kernel 5.2.9 had be included in the root file system, its kernel modules and device tree blobs could have be removed with 'dpkg --remove *.deb' or maybe even with 'auto-remove'. Sounds tidy and clean to me. To be included in the next root file system?
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 September 06, 2020 10:33AM |
Registered: 7 years ago Posts: 181 |
Hi whitepawn,
I tested your 'stress' command with the root file system on 4 different USB sticks:
The bandwidths above were reported by 'dd' when creating the swap files. The capacity of USB stick A was to small for a 2 GiB swap file, so the size was set to 1 GiB for all the tests. This was more than enough. In a separate terminal window, swap memory usage was monitored by 'htop' . At most 11 MiB swap space was used, i.e. about 1%. The swap file was created at first boot and activated by these lines in '/etc/rc.local':
Loged in as normal user 'tme', I did:
Test A:
After 2:19 minutes 2 lines of output appeared on the serial console:
Test B:
After 6:42 minutes 1 line of output appeared on the serial console:
Test C:
After 8:11 minutes the USB stick disconnected and everything broke down within half a minute:
Test D:
After 0:39 minutes, 1 line appeared on the serial console:
Observation summary:
Regards,
Trond Melen
Quote
Trond, may I ask you to try stress command on your box with front usb attached?
I tested your 'stress' command with the root file system on 4 different USB sticks:
- Test A: 4 GB industrial grade Innodisk (merited brand), thumb size, USB3, 11.9 MB/s.
- Test B: 8 GB commercial grade Tali (unmerited brand), mini, USB3(?), 4.5 MB/s.
- Test C: 16 GB commercial grade Lexar (unmerited brand), mini, USB2, 2.2 MB/s.
- Test D: 16 GB commercial grade Scandisk (merited brand) Ultra, thumb size, USB3, 17.4 MB/s.
The bandwidths above were reported by 'dd' when creating the swap files. The capacity of USB stick A was to small for a 2 GiB swap file, so the size was set to 1 GiB for all the tests. This was more than enough. In a separate terminal window, swap memory usage was monitored by 'htop' . At most 11 MiB swap space was used, i.e. about 1%. The swap file was created at first boot and activated by these lines in '/etc/rc.local':
# Create a new swap file if it does not exist or is not writable or is not owned by root if [ ! -w /swapfile ] || [ ! -O /swapfile ]; then echo $0: "Creating 'swapfile' in the root directory" swapoff --all rm --force /swapfile dd if=/dev/zero of=/swapfile count=8192 bs=131072 # Create 1 GiB swap file ((1024 * 8) * 128 kiB) chmod 600 /swapfile mkswap /swapfile sync echo $0: $(ls -lFh /swapfile) fi # Enable swapping if [ -w /swapfile ] && [ -O /swapfile ]; then swapon /swapfile fi
Loged in as normal user 'tme', I did:
ls -lFh /swapfile
-rw------- 1 root root 2,0G sep. 6 05:00 /swapfile
free -h
total used free shared buff/cache available
Mem: 492Mi 36Mi 409Mi 1,0Mi 46Mi 335Mi
Swap: 2,0Gi 0B 2,0Gi
sudo apt update && sudo apt upgrade -y
sudo apt install -y stress
time stress --cpu 1 --io 2 --vm 1 --hdd 1
Test A:
After 2:19 minutes 2 lines of output appeared on the serial console:
[ 2460.757819][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 2465.940393][ T1456] usb 1-1: device descriptor read/64, error -110After another 0:21 minutes the kernel panicked:
[ 2481.308117][ T1456] usb 1-1: device descriptor read/64, error -110 [ 2481.578244][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 2481.748300][ T1456] usb 1-1: device descriptor read/64, error -71 [ 2482.028470][ T1456] usb 1-1: device descriptor read/64, error -71 [ 2482.298609][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 2482.758798][ T1456] usb 1-1: device not accepting address 2, error -71 [ 2482.918926][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 2483.379142][ T1456] usb 1-1: device not accepting address 2, error -71 [ 2483.389299][ T3411] usb 1-1: USB disconnect, device number 2 [ 2483.419189][ T1484] blk_update_request: I/O error, dev sda, sector 913840 op 0x1:(WRITE) flags 0x800 phys_seg 11 prio class 0 [ 2483.429823][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114231) [ 2483.440589][ T1484] Buffer I/O error on device sda1, logical block 113974 [ 2483.446933][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114232) [ 2483.457735][ T1484] Buffer I/O error on device sda1, logical block 113975 [ 2483.464089][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114233) [ 2483.474877][ T1484] Buffer I/O error on device sda1, logical block 113976 [ 2483.481236][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114234) [ 2483.492021][ T1484] Buffer I/O error on device sda1, logical block 113977 [ 2483.498314][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114235) [ 2483.509049][ T1484] Buffer I/O error on device sda1, logical block 113978 [ 2483.515445][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114236) [ 2483.526183][ T1484] Buffer I/O error on device sda1, logical block 113979 [ 2483.532579][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114237) [ 2483.543319][ T1484] Buffer I/O error on device sda1, logical block 113980 [ 2483.549724][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114238) [ 2483.560463][ T1484] Buffer I/O error on device sda1, logical block 113981 [ 2483.566748][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114239) [ 2483.577533][ T1484] Buffer I/O error on device sda1, logical block 113982 [ 2483.583883][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 135468 starting block 114240) [ 2483.594670][ T1484] Buffer I/O error on device sda1, logical block 113983 [ 2483.601491][ T1502] JBD2: Detected IO errors while flushing file data on sda1-8 [ 2483.608276][ T1502] blk_update_request: I/O error, dev sda, sector 120000 op 0x1:(WRITE) flags 0x800 phys_seg 5 prio class 0 [ 2483.619210][ T1484] blk_update_request: I/O error, dev sda, sector 3472432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 2483.629799][ T1484] blk_update_request: I/O error, dev sda, sector 3472600 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 2483.640339][ T1484] blk_update_request: I/O error, dev sda, sector 3472432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 2483.650937][ T1484] blk_update_request: I/O error, dev sda, sector 3472600 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 2483.661474][ T1484] blk_update_request: I/O error, dev sda, sector 3472432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 2483.672064][ T1484] blk_update_request: I/O error, dev sda, sector 3472600 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 2483.682599][ T1484] blk_update_request: I/O error, dev sda, sector 3472432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 2483.693423][ T1484] blk_update_request: I/O error, dev sda, sector 3472600 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 2483.726234][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007 [ 2483.733954][ T1] CPU: 0 PID: 1 Comm: init Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 2483.741168][ T1] Hardware name: Marvell Armada 370/XP (Device Tree) [ 2483.747218][ T1] [<c0115b10>] (unwind_backtrace) from [<c01106d8>] (show_stack+0x10/0x14) [ 2483.755010][ T1] [<c01106d8>] (show_stack) from [<c05f0d84>] (dump_stack+0x80/0x9c) [ 2483.762321][ T1] [<c05f0d84>] (dump_stack) from [<c0129088>] (panic+0xe4/0x2f0) [ 2483.769305][ T1] [<c0129088>] (panic) from [<c012c914>] (do_exit+0x1b4/0xa28) [ 2483.776125][ T1] [<c012c914>] (do_exit) from [<c012dde0>] (do_group_exit+0x58/0xb8) [ 2483.783428][ T1] [<c012dde0>] (do_group_exit) from [<c01391ac>] (get_signal+0x224/0x6d4) [ 2483.791128][ T1] [<c01391ac>] (get_signal) from [<c010fc1c>] (do_work_pending+0xd8/0x438) [ 2483.798906][ T1] [<c010fc1c>] (do_work_pending) from [<c01000cc>] (slow_work_pending+0xc/0x20) [ 2483.807077][ T1] Exception stack(0xdf487fb0 to 0xdf487ff8) [ 2483.812373][ T1] 7fa0: 00000011 bee178d4 00000000 00000000 [ 2483.820550][ T1] 7fc0: bee17790 00000074 00000005 0000008e bee178d4 bee17790 bee17790 bee178d4 [ 2483.828725][ T1] 7fe0: 0000008e bee17438 b6dcaca1 004d01d0 00010030 ffffffff [ 2483.835475][ T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007 ]---
Test B:
After 6:42 minutes 1 line of output appeared on the serial console:
[ 1787.782799][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehciAfter another 4:14 minutes the same line appeared again:
[ 2041.989898][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehciThe next 33:18 minutes this same line was repeated another 9 times:
[ 2156.607259][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 2241.769787][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 2860.959389][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 3504.481174][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 3704.261071][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 3759.968954][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 3888.634852][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 3929.013438][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 4039.148534][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehciThen read errors appeared:
[ 4044.331074][ T1456] usb 1-1: device descriptor read/64, error -110 [ 4059.698791][ T1456] usb 1-1: device descriptor read/64, error -110 [ 4059.968909][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 4065.141513][ T1456] usb 1-1: device descriptor read/64, error -110 [ 4080.509213][ T1456] usb 1-1: device descriptor read/64, error -110 [ 4080.779330][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 4085.885028][ T1456] usb 1-1: device descriptor read/8, error -110 [ 4091.087671][ T1456] usb 1-1: device descriptor read/8, error -110 [ 4091.354593][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 4096.450307][ T1456] usb 1-1: device descriptor read/8, error -110 [ 4101.652897][ T1456] usb 1-1: device descriptor read/8, error -110 [ 4101.770225][T11724] usb 1-1: USB disconnect, device number 2And after another minute read errors on swap:
[ 4101.799876][ T1484] blk_update_request: I/O error, dev sda, sector 10462840 op 0x1:(WRITE) flags 0x4000 phys_seg 4 prio class 0 [ 4101.811040][ T1484] blk_update_request: I/O error, dev sda, sector 10463080 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0 [ 4101.823051][ T1669] blk_update_request: I/O error, dev sda, sector 6302176 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 [ 4101.849835][ T1669] Read-error on swap-device (8:0:6302184) [ 4101.855000][ T1669] Read-error on swap-device (8:0:6302192) [ 4101.869891][ T1669] Read-error on swap-device (8:0:6302200) [ 4101.875053][ T1669] Read-error on swap-device (8:0:6302208) [ 4101.890059][ T1484] blk_update_request: I/O error, dev sda, sector 10463320 op 0x1:(WRITE) flags 0x4000 phys_seg 4 prio class 0 [ 4101.901374][ T1484] blk_update_request: I/O error, dev sda, sector 10463560 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0 [ 4101.912677][ T1484] blk_update_request: I/O error, dev sda, sector 10463800 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0 [ 4101.923579][ T1484] blk_update_request: I/O error, dev sda, sector 10464040 op 0x1:(WRITE) flags 0x4000 phys_seg 4 prio class 0 [ 4101.934987][ T1484] blk_update_request: I/O error, dev sda, sector 10464280 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0 [ 4101.945880][ T1484] blk_update_request: I/O error, dev sda, sector 10464520 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0 [ 4101.956737][ T1484] blk_update_request: I/O error, dev sda, sector 10464760 op 0x1:(WRITE) flags 0x4000 phys_seg 4 prio class 0 [ 4101.971657][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1308339 ) [ 4101.982517][ T1484] Buffer I/O error on device sda1, logical block 1307059 [ 4101.988970][ T1484] Buffer I/O error on device sda1, logical block 1307060 [ 4101.995460][ T1484] Buffer I/O error on device sda1, logical block 1307061 [ 4102.002740][ T1484] Buffer I/O error on device sda1, logical block 1307062 [ 4102.009174][ T1484] Buffer I/O error on device sda1, logical block 1307063 [ 4102.015706][ T1484] Buffer I/O error on device sda1, logical block 1307064 [ 4102.022195][ T1484] Buffer I/O error on device sda1, logical block 1307065 [ 4102.028616][ T1484] Buffer I/O error on device sda1, logical block 1307066 [ 4102.035098][ T1484] Buffer I/O error on device sda1, logical block 1307067 [ 4102.042579][ T1484] Buffer I/O error on device sda1, logical block 1307068And the 'etx3' file system became inconsistent:
[ 4102.062534][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1308860 ) [ 4102.092475][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1309363 ) [ 4102.113259][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1310387 ) [ 4102.134121][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1310976 ) [ 4102.163161][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1313459 ) [ 4102.180905][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1314065 ) [ 4102.211034][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1314483 ) [ 4102.233062][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1315507 ) [ 4102.264277][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 163216 starting block 1316531 ) [ 4102.279383][ T1502] JBD2: Detected IO errors while flushing file data on sda1-8 [ 4102.294624][ T1502] Aborting journal on device sda1-8. [ 4102.299437][ T1502] Buffer I/O error on dev sda1, logical block 981, lost sync page write [ 4102.320368][T11710] Buffer I/O error on dev sda1, logical block 0, lost sync page write [ 4102.340178][ T1502] JBD2: Error -5 detected when updating journal superblock for sda1-8. [ 4102.420380][T11710] EXT4-fs (sda1): I/O error while writing superblock [ 4102.426420][T11710] EXT4-fs error (device sda1): ext4_journal_check_start:83: Detected aborted journal [ 4102.543771][ T1502] JBD2: Detected IO errors while flushing file data on sda1-8 [ 4102.632464][T11710] EXT4-fs (sda1): Remounting filesystem read-only [ 4102.674517][T11710] EXT4-fs error (device sda1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 34, block_bitmap = 1114112 [ 4102.750311][T11710] EXT4-fs error (device sda1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap fo r 34 [ 4102.780316][T11724] usb 1-1: new high-speed USB device number 3 using orion-ehci [ 4102.820361][T11710] EXT4-fs error (device sda1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 34, block_bitmap = 1114112 [ 4102.880343][T11710] EXT4-fs error (device sda1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap fo r 34 [ 4102.930410][T11710] EXT4-fs error (device sda1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 34, block_bitmap = 1114112 [ 4102.990431][T11710] EXT4-fs error (device sda1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap fo r 34 [ 4103.050519][T11710] EXT4-fs error (device sda1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 40, block_bitmap = 1310720 [ 4103.130504][T11710] EXT4-fs error (device sda1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap fo r 40 [ 4104.305445][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #212161: comm bash: reading directory lblock 0 [ 4104.316315][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #212161: comm bash: reading directory lblock 0 [ 4107.963016][T11724] usb 1-1: device descriptor read/64, error -110 [ 4121.065056][ T2767] EXT4-fs error: 6 callbacks suppressed [ 4121.065075][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 4121.081389][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 4121.092676][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89764: comm cron: reading directory lblock 0 [ 4121.104184][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 4121.115634][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 4121.127090][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 4121.138564][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89764: comm cron: reading directory lblock 0 [ 4123.330700][T11724] usb 1-1: device descriptor read/64, error -110 [ 4123.600836][T11724] usb 1-1: new high-speed USB device number 4 using orion-ehci [ 4128.773422][T11724] usb 1-1: device descriptor read/64, error -110 [ 4143.670818][ T2849] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm ntpd: reading directory lblock 0 [ 4143.681782][ T2849] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm ntpd: reading directory lblock 0 [ 4144.141105][T11724] usb 1-1: device descriptor read/64, error -110 [ 4144.261239][T11724] usb usb1-port1: attempt power cycle [ 4144.971523][T11724] usb 1-1: new high-speed USB device number 5 using orion-ehci [ 4146.679908][ T2849] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm ntpd: reading directory lblock 0 [ 4146.690858][ T2849] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm ntpd: reading directory lblock 0 [ 4150.077126][T11724] usb 1-1: device descriptor read/8, error -110 [ 4155.279736][T11724] usb 1-1: device descriptor read/8, error -110 [ 4155.546702][T11724] usb 1-1: new high-speed USB device number 6 using orion-ehci [ 4160.642410][T11724] usb 1-1: device descriptor read/8, error -110 [ 4165.845020][T11724] usb 1-1: device descriptor read/8, error -110 [ 4165.962032][T11724] usb usb1-port1: unable to enumerate USB device [ 4181.190411][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 4181.209658][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89764: comm cron: reading directory lblock 0 [ 4181.240051][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 4181.260081][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 4241.310298][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [...] [ 5682.380644][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 5742.430861][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 5742.450285][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89764: comm cron: reading directory lblock 0 [ 5742.480672][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0 [ 5742.500707][ T2767] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm cron: reading directory lblock 0When I tried to log in on the serial console, the kernel panicked:
[ 5824.119350][ T3059] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #285601: comm getty: reading directory lblock 0 [ 5824.141296][ T3059] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm getty: reading directory lblock 0 [ 5834.176496][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm init: reading directory lblock 0 [ 5834.196235][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm init: reading directory lblock 0 [ 5834.216287][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm init: reading directory lblock 0 [ 5834.239417][T11733] Read-error on swap-device (8:0:6299936) [ 5834.244603][T11733] Read-error on swap-device (8:0:6299944) [ 5834.266168][T11733] Read-error on swap-device (8:0:6299952) [ 5834.271362][T11733] Read-error on swap-device (8:0:6299960) [ 5834.296499][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm init: reading directory lblock 0 [ 5834.307181][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm init: reading directory lblock 0 [ 5834.336362][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm init: reading directory lblock 0 [ 5834.366546][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm init: reading directory lblock 0 [ 5834.386319][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm init: reading directory lblock 0 [ 5834.406417][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #138721: comm init: reading directory lblock 0 [ 5834.436624][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #89761: comm init: reading directory lblock 0 [ 5834.511013][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007 [ 5834.518733][ T1] CPU: 0 PID: 1 Comm: init Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 5834.525949][ T1] Hardware name: Marvell Armada 370/XP (Device Tree) [ 5834.531996][ T1] [<c0115b10>] (unwind_backtrace) from [<c01106d8>] (show_stack+0x10/0x14) [ 5834.539788][ T1] [<c01106d8>] (show_stack) from [<c05f0d84>] (dump_stack+0x80/0x9c) [ 5834.547099][ T1] [<c05f0d84>] (dump_stack) from [<c0129088>] (panic+0xe4/0x2f0) [ 5834.554084][ T1] [<c0129088>] (panic) from [<c012c914>] (do_exit+0x1b4/0xa28) [ 5834.560904][ T1] [<c012c914>] (do_exit) from [<c012dde0>] (do_group_exit+0x58/0xb8) [ 5834.568209][ T1] [<c012dde0>] (do_group_exit) from [<c01391ac>] (get_signal+0x224/0x6d4) [ 5834.575907][ T1] [<c01391ac>] (get_signal) from [<c010fc1c>] (do_work_pending+0xd8/0x438) [ 5834.583685][ T1] [<c010fc1c>] (do_work_pending) from [<c01000cc>] (slow_work_pending+0xc/0x20) [ 5834.591857][ T1] Exception stack(0xdf487fb0 to 0xdf487ff8) [ 5834.597154][ T1] 7fa0: 004832ec 00000025 bebe1840 bebe1094 [ 5834.605329][ T1] 7fc0: bebe1500 fbad8001 b6f644d0 bebe1010 004832ec 00000000 b6f6e968 b6e9b000 [ 5834.613502][ T1] 7fe0: 0049405c bebe0ff0 b6dd8bc5 b6e00a68 20010030 ffffffff [ 5834.620252][ T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007 ]---
Test C:
After 8:11 minutes the USB stick disconnected and everything broke down within half a minute:
[ 3072.502717][T12002] usb 1-1: USB disconnect, device number 2 [ 3072.524666][ T1484] blk_update_request: I/O error, dev sda, sector 9245520 op 0x1:(WRITE) flags 0x4800 phys_seg 30 prio class 0 [ 3072.535471][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155691 ) [ 3072.547743][ T1484] Buffer I/O error on device sda1, logical block 1155434 [ 3072.554130][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155692 ) [ 3072.565483][ T1484] Buffer I/O error on device sda1, logical block 1155435 [ 3072.571868][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155693 ) [ 3072.583118][ T1484] Buffer I/O error on device sda1, logical block 1155436 [ 3072.589673][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155694 ) [ 3072.600501][ T1484] Buffer I/O error on device sda1, logical block 1155437 [ 3072.607372][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155695 ) [ 3072.618221][ T1484] Buffer I/O error on device sda1, logical block 1155438 [ 3072.624741][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155696 ) [ 3072.635940][ T1484] Buffer I/O error on device sda1, logical block 1155439 [ 3072.642323][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155697 ) [ 3072.653244][ T1484] Buffer I/O error on device sda1, logical block 1155440 [ 3072.659690][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155698 ) [ 3072.670783][ T1484] Buffer I/O error on device sda1, logical block 1155441 [ 3072.677251][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155699 ) [ 3072.688131][ T1484] Buffer I/O error on device sda1, logical block 1155442 [ 3072.694505][ T1484] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 848653 starting block 1155700 ) [ 3072.705382][ T1484] Buffer I/O error on device sda1, logical block 1155443 [ 3072.712531][ T1484] blk_update_request: I/O error, dev sda, sector 9245768 op 0x1:(WRITE) flags 0x4000 phys_seg 4 prio class 0 [ 3072.723364][ T1484] blk_update_request: I/O error, dev sda, sector 9245760 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 [ 3072.734308][ T1669] blk_update_request: I/O error, dev sda, sector 3948104 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0 [ 3072.754837][ T1669] Read-error on swap-device (8:0:3948112) [ 3072.760001][ T1669] Read-error on swap-device (8:0:3948120) [ 3072.774760][ T1669] Read-error on swap-device (8:0:3948128) [ 3072.779921][ T1669] Read-error on swap-device (8:0:3948136) [ 3072.794708][ T1669] Read-error on swap-device (8:0:3948144) [ 3072.799861][ T1669] Read-error on swap-device (8:0:3948152) [ 3072.824781][ T1669] Read-error on swap-device (8:0:3948160) [ 3072.829943][ T1669] Read-error on swap-device (8:0:3948168) [ 3072.844889][ T1484] blk_update_request: I/O error, dev sda, sector 12592576 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 3072.855520][ T2672] blk_update_request: I/O error, dev sda, sector 9246008 op 0x1:(WRITE) flags 0x4000 phys_seg 5 prio class 0 [ 3072.866850][ T1484] blk_update_request: I/O error, dev sda, sector 9253960 op 0x1:(WRITE) flags 0x4800 phys_seg 30 prio class 0 [ 3072.878003][ T1484] blk_update_request: I/O error, dev sda, sector 9246248 op 0x1:(WRITE) flags 0x4000 phys_seg 6 prio class 0 [ 3072.889342][ T1484] blk_update_request: I/O error, dev sda, sector 9254200 op 0x1:(WRITE) flags 0x4800 phys_seg 30 prio class 0 [ 3072.900506][ T1484] blk_update_request: I/O error, dev sda, sector 9246488 op 0x1:(WRITE) flags 0x4000 phys_seg 4 prio class 0 [ 3073.252412][ T1502] JBD2: Detected IO errors while flushing file data on sda1-8 [ 3073.259557][ T1484] Buffer I/O error on dev sda1, logical block 1114112, lost async page write [ 3073.267958][ T1484] Buffer I/O error on dev sda1, logical block 3280112, lost async page write [ 3073.276796][ T1484] Buffer I/O error on dev sda1, logical block 3280113, lost async page write [ 3073.284771][ T1484] Buffer I/O error on dev sda1, logical block 3280114, lost async page write [ 3073.292934][ T1484] Buffer I/O error on dev sda1, logical block 3280115, lost async page write [ 3073.300993][ T1484] Buffer I/O error on dev sda1, logical block 3280116, lost async page write [ 3073.309090][ T1484] Buffer I/O error on dev sda1, logical block 3280117, lost async page write [ 3073.317129][ T1484] Buffer I/O error on dev sda1, logical block 3280118, lost async page write [ 3073.326463][ T1484] Buffer I/O error on dev sda1, logical block 3280119, lost async page write [ 3073.334879][ T1484] Buffer I/O error on dev sda1, logical block 3284720, lost async page write [ 3073.357327][ T1502] Aborting journal on device sda1-8. [ 3073.362172][ T1502] JBD2: Error -5 detected when updating journal superblock for sda1-8. [ 3073.370338][T12000] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5651: Journal has aborted [ 3073.395236][T12000] EXT4-fs (sda1): I/O error while writing superblock [ 3073.401277][T12000] EXT4-fs (sda1): Remounting filesystem read-only [ 3073.435086][T12000] EXT4-fs error (device sda1): ext4_dirty_inode:5853: inode #848653: comm stress: mark_inode_dirty error [ 3073.465262][T12000] EXT4-fs (sda1): I/O error while writing superblock [ 3073.471305][T12000] EXT4-fs error (device sda1) in ext4_dirty_inode:5855: Journal has aborted [ 3073.505176][T12000] EXT4-fs (sda1): I/O error while writing superblock [ 3073.511402][ T1502] JBD2: Detected IO errors while flushing file data on sda1-8 [ 3073.581277][T12000] EXT4-fs error (device sda1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 32, block_bitmap = 1048576 [ 3073.655252][T12000] EXT4-fs error (device sda1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap fo r 32 [ 3073.725238][T12000] EXT4-fs error (device sda1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 32, block_bitmap = 1048576 [ 3073.785267][T12000] EXT4-fs error (device sda1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap fo r 32 [ 3073.835329][T12000] EXT4-fs error (device sda1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 32, block_bitmap = 1048576 [ 3073.905288][T12000] EXT4-fs error (device sda1): ext4_discard_preallocations:4193: comm stress: Error -5 reading block bitmap fo r 32 [ 3073.945362][T12002] usb 1-1: new high-speed USB device number 3 using orion-ehci [ 3073.965608][T12000] EXT4-fs error (device sda1): ext4_wait_block_bitmap:521: comm stress: Cannot read block bitmap - block_group = 35, block_bitmap = 1146880 [ 3074.168204][T12002] usb 1-1: New USB device found, idVendor=05dc, idProduct=a01a, bcdDevice=11.00 [ 3074.185736][T12002] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3074.192967][T12002] usb 1-1: Product: Echo [ 3074.205535][T12002] usb 1-1: Manufacturer: Lexar [ 3074.209811][T12002] usb 1-1: SerialNumber: AAUXCPY6JQLMD4J6 [ 3074.235819][T12002] usb-storage 1-1:1.0: USB Mass Storage device detected [ 3074.245987][T12002] scsi host4: usb-storage 1-1:1.0 [ 3078.866488][ T1201] scsi 4:0:0:0: Direct-Access Lexar Echo 1100 PQ: 0 ANSI: 0 CCS [ 3078.877231][ T1201] sd 4:0:0:0: Attached scsi generic sg0 type 0 [ 3079.222168][ T3020] EXT4-fs error: 13 callbacks suppressed [ 3079.222188][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3079.238813][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3079.249952][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3079.261240][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3079.272362][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3079.283488][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3079.294612][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3079.308295][ T3020] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #816001: comm bash: reading directory lblock 0 [ 3079.325445][ T3013] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #538561: comm sshd: reading directory lblock 0 [ 3079.343295][ T3013] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #538561: comm sshd: reading directory lblock 0 [ 3082.277120][T11993] sd 4:0:0:0: [sdb] 31326208 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 3082.286236][T11993] sd 4:0:0:0: [sdb] Write Protect is off [ 3082.293277][T11993] sd 4:0:0:0: [sdb] No Caching mode page found [ 3082.298874][T11993] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 3085.628225][T11993] sdb: sdb1 [ 3085.636920][T11993] sd 4:0:0:0: [sdb] Attached SCSI removable disk [ 3104.349919][ T2849] EXT4-fs error: 3 callbacks suppressed [ 3104.349939][ T2849] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #816001: comm ntpd: reading directory lblock 0 [ 3109.124146][ T3099] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3109.153043][ T3099] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3109.173221][ T3099] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #344870: comm bash: reading directory lblock 0 [ 3109.193243][ T3099] EXT4-fs warning: 576 callbacks suppressed [ 3109.193261][ T3099] EXT4-fs warning (device sda1): dx_probe:768: inode #352986: lblock 0: comm bash: error -5 reading directory block [ 3109.233164][ T3099] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #65281: comm bash: reading directory lblock 0 [ 3109.253249][ T3099] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #261121: comm bash: reading directory lblock 0 [ 3109.278669][T12006] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3109.303371][T12006] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3109.323236][T12006] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3109.353230][T12006] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3109.373263][T12006] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3109.393280][T12006] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 [ 3109.413279][T12006] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #342721: comm bash: reading directory lblock 0 -bash: shutdown: command not found [ 3109.443837][ T3099] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #816001: comm bash: reading directory lblock 0 [ 3109.476293][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #816001: comm init: reading directory lblock 0 [ 3109.503340][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #816001: comm init: reading directory lblock 0 [ 3109.523445][ T1] EXT4-fs error (device sda1): __ext4_find_entry:1537: inode #538561: comm init: reading directory lblock 0Issuing the command 'shutdown -h now' caused the kernal to panic:
[ 3109.543419][ T1] Read-error on swap-device (8:0:3946024) [ 3109.548605][ T1] Read-error on swap-device (8:0:3946032) [ 3109.563279][ T1] Read-error on swap-device (8:0:3946040) [ 3109.568474][ T1] Read-error on swap-device (8:0:3946048) [ 3109.593306][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007 [ 3109.601023][ T1] CPU: 0 PID: 1 Comm: init Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 3109.608239][ T1] Hardware name: Marvell Armada 370/XP (Device Tree) [ 3109.614287][ T1] [<c0115b10>] (unwind_backtrace) from [<c01106d8>] (show_stack+0x10/0x14) [ 3109.622079][ T1] [<c01106d8>] (show_stack) from [<c05f0d84>] (dump_stack+0x80/0x9c) [ 3109.629390][ T1] [<c05f0d84>] (dump_stack) from [<c0129088>] (panic+0xe4/0x2f0) [ 3109.636374][ T1] [<c0129088>] (panic) from [<c012c914>] (do_exit+0x1b4/0xa28) [ 3109.643194][ T1] [<c012c914>] (do_exit) from [<c012dde0>] (do_group_exit+0x58/0xb8) [ 3109.650498][ T1] [<c012dde0>] (do_group_exit) from [<c01391ac>] (get_signal+0x224/0x6d4) [ 3109.658197][ T1] [<c01391ac>] (get_signal) from [<c010fc1c>] (do_work_pending+0xd8/0x438) [ 3109.665975][ T1] [<c010fc1c>] (do_work_pending) from [<c01000cc>] (slow_work_pending+0xc/0x20) [ 3109.674146][ T1] Exception stack(0xdf487fb0 to 0xdf487ff8) [ 3109.679443][ T1] 7fa0: 00000000 00000000 2893ab00 2893ab00 [ 3109.687618][ T1] 7fc0: 00459610 b6e92080 00000000 00000000 00459618 00000000 b6f59010 0000004e [ 3109.695793][ T1] 7fe0: 00456170 be89f808 b6e0f235 b6e3ddf6 60010030 ffffffff [ 3109.702542][ T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007 ]---
Test D:
After 0:39 minutes, 1 line appeared on the serial console:
[ 661.237401][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehciAfter another 0:30 minutes, the same line appeared again:
[ 692.192847][ T1456] usb 1-1: reset high-speed USB device number 2 using orion-ehci3:01 minutes after the first USB resets, the swapper timed out:
[ 858.506029][ T398] INFO: task kswapd0:600 blocked for more than 122 seconds. [ 858.512625][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 858.531165][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 858.550092][ T398] kswapd0 D 0 600 2 0x00000000 [ 858.555844][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 858.579017][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 858.597319][ T398] [<c0ab8740>] (io_schedule) from [<c056d270>] (blk_mq_get_tag+0x168/0x270) [ 858.605203][ T398] [<c056d270>] (blk_mq_get_tag) from [<c0569a34>] (__blk_mq_alloc_request+0xec/0x134) [ 858.634600][ T398] [<c0569a34>] (__blk_mq_alloc_request) from [<c056ab44>] (blk_mq_make_request+0xd0/0x4c8) [ 858.657221][ T398] [<c056ab44>] (blk_mq_make_request) from [<c0560790>] (generic_make_request+0xe8/0x1d8) [ 858.676873][ T398] [<c0560790>] (generic_make_request) from [<c05608bc>] (submit_bio+0x3c/0x1a4) [ 858.685084][ T398] [<c05608bc>] (submit_bio) from [<c02809e4>] (__swap_writepage+0x28c/0x2ac) [ 858.716118][ T398] [<c02809e4>] (__swap_writepage) from [<c02500f4>] (shmem_writepage+0x274/0x2b0) [ 858.724479][ T398] [<c02500f4>] (shmem_writepage) from [<c024af14>] (shrink_page_list+0x7bc/0xadc) [ 858.756127][ T398] [<c024af14>] (shrink_page_list) from [<c024c548>] (shrink_inactive_list+0x1c8/0x398) [ 858.764888][ T398] [<c024c548>] (shrink_inactive_list) from [<c024d178>] (shrink_node+0x728/0x7d8) [ 858.793366][ T398] [<c024d178>] (shrink_node) from [<c024da14>] (kswapd+0x528/0x798) [ 858.811475][ T398] [<c024da14>] (kswapd) from [<c014704c>] (kthread+0x13c/0x148) [ 858.827863][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 858.835176][ T398] Exception stack(0xdd8fbfb0 to 0xdd8fbff8) [ 858.856129][ T398] bfa0: 00000000 00000000 00000000 00000000 [ 858.864326][ T398] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 858.895189][ T398] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 858.916203][ T398] INFO: task scsi_eh_3:1454 blocked for more than 123 seconds. [ 858.923036][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 858.940262][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 858.966199][ T398] scsi_eh_3 D 0 1454 2 0x00000000 [ 858.971950][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 858.988322][ T398] [<c0ab82a0>] (schedule) from [<c0ab8680>] (schedule_preempt_disabled+0x14/0x20) [ 859.009232][ T398] [<c0ab8680>] (schedule_preempt_disabled) from [<c0ab9700>] (__mutex_lock.constprop.8+0x170/0x2e0) [ 859.032583][ T398] [<c0ab9700>] (__mutex_lock.constprop.8) from [<c07c99e8>] (device_reset+0x1c/0x48) [ 859.052395][ T398] [<c07c99e8>] (device_reset) from [<c06d51a4>] (scsi_try_bus_device_reset+0x24/0x48) [ 859.076265][ T398] [<c06d51a4>] (scsi_try_bus_device_reset) from [<c06d67e8>] (scsi_eh_ready_devs+0x378/0x990) [ 859.085588][ T398] [<c06d67e8>] (scsi_eh_ready_devs) from [<c06d7d24>] (scsi_error_handler+0x298/0x56c) [ 859.114314][ T398] [<c06d7d24>] (scsi_error_handler) from [<c014704c>] (kthread+0x13c/0x148) [ 859.136314][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 859.143629][ T398] Exception stack(0xc373dfb0 to 0xc373dff8) [ 859.166317][ T398] dfa0: 00000000 00000000 00000000 00000000 [ 859.174511][ T398] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 859.206320][ T398] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 859.213086][ T398] INFO: task usb-storage:1456 blocked for more than 123 seconds. [ 859.231752][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 859.246401][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 859.254277][ T398] usb-storage D 0 1456 2 0x00000000 [ 859.276596][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 859.283841][ T398] [<c0ab82a0>] (schedule) from [<c0aba530>] (schedule_timeout+0x24/0xe8) [ 859.328268][ T398] [<c0aba530>] (schedule_timeout) from [<c0ab8c34>] (do_wait_for_common+0xac/0x12c) [ 859.356455][ T398] [<c0ab8c34>] (do_wait_for_common) from [<c0ab8d1c>] (wait_for_common+0x30/0x48) [ 859.364820][ T398] [<c0ab8d1c>] (wait_for_common) from [<c079104c>] (usb_sg_wait+0x70/0x170) [ 859.416470][ T398] [<c079104c>] (usb_sg_wait) from [<c07ca3c0>] (usb_stor_bulk_transfer_sglist.part.2+0x80/0xc4) [ 859.425953][ T398] [<c07ca3c0>] (usb_stor_bulk_transfer_sglist.part.2) from [<c07ca664>] (usb_stor_bulk_srb+0x44/0x74) [ 859.469922][ T398] [<c07ca664>] (usb_stor_bulk_srb) from [<c07ca9e4>] (usb_stor_Bulk_transport+0x13c/0x350) [ 859.496550][ T398] [<c07ca9e4>] (usb_stor_Bulk_transport) from [<c07cadb4>] (usb_stor_invoke_transport+0x2c/0x438) [ 859.506193][ T398] [<c07cadb4>] (usb_stor_invoke_transport) from [<c07cbc7c>] (usb_stor_control_thread+0x1d8/0x224) [ 859.538294][ T398] [<c07cbc7c>] (usb_stor_control_thread) from [<c014704c>] (kthread+0x13c/0x148) [ 859.556584][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 859.563898][ T398] Exception stack(0xc3741fb0 to 0xc3741ff8) [ 859.587314][ T398] 1fa0: 00000000 00000000 00000000 00000000 [ 859.595511][ T398] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 859.624004][ T398] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 859.641200][ T398] INFO: task kworker/0:1:3061 blocked for more than 124 seconds. [ 859.666598][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 859.672313][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 859.689190][ T398] kworker/0:1 D 0 3061 2 0x00000000 [ 859.694928][ T398] Workqueue: events_freezable_power_ disk_events_workfn [ 859.726636][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 859.733878][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 859.750904][ T398] [<c0ab8740>] (io_schedule) from [<c056d270>] (blk_mq_get_tag+0x168/0x270) [ 859.770791][ T398] [<c056d270>] (blk_mq_get_tag) from [<c0569a34>] (__blk_mq_alloc_request+0xec/0x134) [ 859.796647][ T398] [<c0569a34>] (__blk_mq_alloc_request) from [<c0569ad8>] (blk_mq_alloc_request+0x5c/0xac) [ 859.805730][ T398] [<c0569ad8>] (blk_mq_alloc_request) from [<c055e960>] (blk_get_request+0x80/0xb0) [ 859.832115][ T398] [<c055e960>] (blk_get_request) from [<c06d8370>] (__scsi_execute+0x38/0x178) [ 859.856686][ T398] [<c06d8370>] (__scsi_execute) from [<c06d99ec>] (scsi_test_unit_ready+0x64/0xe8) [ 859.865131][ T398] [<c06d99ec>] (scsi_test_unit_ready) from [<c06e4134>] (sd_check_events+0xd0/0x124) [ 859.891011][ T398] [<c06e4134>] (sd_check_events) from [<c05713d0>] (disk_check_events+0x4c/0x14c) [ 859.916711][ T398] [<c05713d0>] (disk_check_events) from [<c0141dbc>] (process_one_work+0x210/0x358) [ 859.925266][ T398] [<c0141dbc>] (process_one_work) from [<c01426d4>] (worker_thread+0x228/0x2cc) [ 859.949238][ T398] [<c01426d4>] (worker_thread) from [<c014704c>] (kthread+0x13c/0x148) [ 859.967986][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 859.975300][ T398] Exception stack(0xdf495fb0 to 0xdf495ff8) [ 859.997633][ T398] 5fa0: 00000000 00000000 00000000 00000000 [ 860.005828][ T398] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 860.034957][ T398] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 860.056825][ T398] INFO: task stress:11694 blocked for more than 124 seconds. [ 860.063500][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 860.080342][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 860.098841][ T398] stress D 0 11694 11691 0x00000000 [ 860.104590][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 860.127240][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 860.134491][ T398] [<c0ab8740>] (io_schedule) from [<c056d270>] (blk_mq_get_tag+0x168/0x270) [ 860.164649][ T398] [<c056d270>] (blk_mq_get_tag) from [<c0569a34>] (__blk_mq_alloc_request+0xec/0x134) [ 860.186842][ T398] [<c0569a34>] (__blk_mq_alloc_request) from [<c056ab44>] (blk_mq_make_request+0xd0/0x4c8) [ 860.195924][ T398] [<c056ab44>] (blk_mq_make_request) from [<c0560790>] (generic_make_request+0xe8/0x1d8) [ 860.226434][ T398] [<c0560790>] (generic_make_request) from [<c05608bc>] (submit_bio+0x3c/0x1a4) [ 860.246876][ T398] [<c05608bc>] (submit_bio) from [<c02809e4>] (__swap_writepage+0x28c/0x2ac) [ 860.254850][ T398] [<c02809e4>] (__swap_writepage) from [<c02500f4>] (shmem_writepage+0x274/0x2b0) [ 860.286894][ T398] [<c02500f4>] (shmem_writepage) from [<c024af14>] (shrink_page_list+0x7bc/0xadc) [ 860.295256][ T398] [<c024af14>] (shrink_page_list) from [<c024c548>] (shrink_inactive_list+0x1c8/0x398) [ 860.323748][ T398] [<c024c548>] (shrink_inactive_list) from [<c024d178>] (shrink_node+0x728/0x7d8) [ 860.346924][ T398] [<c024d178>] (shrink_node) from [<c024d45c>] (do_try_to_free_pages+0x234/0x2c4) [ 860.355286][ T398] [<c024d45c>] (do_try_to_free_pages) from [<c024e080>] (try_to_free_pages+0x190/0x280) [ 860.386950][ T398] [<c024e080>] (try_to_free_pages) from [<c027ba18>] (__alloc_pages_nodemask+0x438/0xd48) [ 860.395963][ T398] [<c027ba18>] (__alloc_pages_nodemask) from [<c0265ae4>] (alloc_zeroed_user_highpage_movable+0x1c/0x44) [ 860.426966][ T398] [<c0265ae4>] (alloc_zeroed_user_highpage_movable) from [<c02692a4>] (handle_mm_fault+0x178/0x938) [ 860.436776][ T398] [<c02692a4>] (handle_mm_fault) from [<c01199c0>] (do_page_fault+0x18c/0x314) [ 860.469289][ T398] [<c01199c0>] (do_page_fault) from [<c0119ca4>] (do_DataAbort+0x38/0xb8) [ 860.487001][ T398] [<c0119ca4>] (do_DataAbort) from [<c01015dc>] (__dabt_usr+0x3c/0x40) [ 860.494475][ T398] Exception stack(0xc6dd9fb0 to 0xc6dd9ff8) [ 860.517739][ T398] 9fa0: 00000002 b67af008 0fa19000 00000000 [ 860.525935][ T398] 9fc0: a6d97008 00001000 10000000 00000000 b6e8ee54 00000002 00000000 004ccf3c [ 860.555175][ T398] 9fe0: 0000005a be829410 b6e2fea7 004bab22 80070030 ffffffff [ 860.577020][ T398] INFO: task stress:11695 blocked for more than 124 seconds. [ 860.583692][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 860.599419][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 860.619060][ T398] stress D 0 11695 11691 0x00000000 [ 860.624810][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 860.648608][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 860.655849][ T398] [<c0ab8740>] (io_schedule) from [<c0ab8ab4>] (bit_wait_io+0xc/0x30) [ 860.683568][ T398] [<c0ab8ab4>] (bit_wait_io) from [<c0ab8798>] (__wait_on_bit+0x48/0x88) [ 860.701005][ T398] [<c0ab8798>] (__wait_on_bit) from [<c0ab8858>] (out_of_line_wait_on_bit+0x80/0xa4) [ 860.727105][ T398] [<c0ab8858>] (out_of_line_wait_on_bit) from [<c0334be0>] (ext4_read_inode_bitmap+0x450/0x500) [ 860.736588][ T398] [<c0334be0>] (ext4_read_inode_bitmap) from [<c03357bc>] (__ext4_new_inode+0x674/0x10b0) [ 860.764116][ T398] [<c03357bc>] (__ext4_new_inode) from [<c0357fc0>] (ext4_create+0xb4/0x170) [ 860.787144][ T398] [<c0357fc0>] (ext4_create) from [<c02a7e30>] (path_openat+0x79c/0xa78) [ 860.794788][ T398] [<c02a7e30>] (path_openat) from [<c02a8148>] (do_filp_open+0x3c/0x9c) [ 860.818679][ T398] [<c02a8148>] (do_filp_open) from [<c0296d8c>] (do_sys_openat2+0x6c/0xd4) [ 860.826484][ T398] [<c0296d8c>] (do_sys_openat2) from [<c0296ed4>] (do_sys_open+0x3c/0x5c) [ 860.854280][ T398] [<c0296ed4>] (do_sys_open) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [ 860.877158][ T398] Exception stack(0xdf491fa8 to 0xdf491ff0) [ 860.882477][ T398] 1fa0: b6e8e000 b6f35968 ffffff9c be829434 000200c2 00000180 [ 860.907184][ T398] 1fc0: b6e8e000 b6f35968 b6e70144 00000142 00000000 0003a2f8 b6f2dfd0 be829434 [ 860.915378][ T398] 1fe0: 00000142 be729300 b6e26155 b6daf746At this point the console was not responding.
Observation summary:
- Both your and mine RN102 box shows very similar symptoms.
- All the tested USB sticks provoke the issue, both USB2 and USB3, both commercial and industrial grade.
- The time to first serial console message varied from 0:39 to 8:11 minutes.
- Fast USB sticks provoke the issue earlier than slower ones.
- For USB2 sticks, the first serial console message was "usb 1-1: USB disconnect, device number 2".
- For USB3 sticks, the first serial console message was "usb 1-1: reset high-speed USB device number 2 using orion-ehci".
- After some time, either the kernel panics or the 'ext3' file system becomes corrupted, or both.
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 September 06, 2020 02:59PM |
Admin Registered: 13 years ago Posts: 18,848 |
All,
If you could, run your stress test using one the these 2 configurations.
- With the swap file on HDD.
- Use HDD rootfs (i.e. the swap file is on the rootfs)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
If you could, run your stress test using one the these 2 configurations.
- With the swap file on HDD.
- Use HDD rootfs (i.e. the swap file is on the rootfs)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 06, 2020 05:27PM |
Admin Registered: 13 years ago Posts: 18,848 |
All,
I've updated the kernel release and installation post :
https://forum.doozan.com/read.php?2,92514,92514#msg-92514
I've tested the installation for the Mirabox.
If you could, run the installation for the RN102 (part II) as is. You should copy and paste every commands, like you have a pristine box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I've updated the kernel release and installation post :
https://forum.doozan.com/read.php?2,92514,92514#msg-92514
I've tested the installation for the Mirabox.
If you could, run the installation for the RN102 (part II) as is. You should copy and paste every commands, like you have a pristine box.
Quote
Installation
Please scrolldown to the installation section for your box below.
I. Mirabox Intsallation (06 Sept 2020)
II. Netgear RN102 Intsallation (06 Sept 2020)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 06, 2020 07:41PM |
Registered: 5 years ago Posts: 73 |
Hi Trond,
Thank you very much for testing USB stuff.I assume it is a flash controller (Inside of USB disk) issue because i investigated hardware USB data pins are soldered directly to CPU itself.USB to SATA seems good option too.If you have time please try with USB SSD Drive also.It seems our box is picky about flash drives.
I have found a USB which was old 8GB one sandisk branded seems ok for now, but i am not sure it works all stable because i disassembled unit with removed heatsink to find GPIO pins for SDIO and SPI Flash:)
To test GPIO test script works and testing SPI flash tomorrow i will try to solder SPI flash with 3 resistors and one capacitor to PCB.
Before soldering SPI flash i will check if GPIO script works on GPIO numbers 63-64-65.How can i know if SPI flash will recognized Bohdi?Will U-boot or kernel initiates SPI Flash?
I have tried to find SDIO pins with GPIO script but no luck so far.It's late in here and i have to sleep.Will try to probe 47 to 52 GPIO numbers.I have checked from pin information also another USB2.0 port modification possible.
Also i investigated mirabox SDIO solution if it was hardwired directly to CPU or not but it seems two USB to SD card controller (GL827) is soldered to box.So basicly its USB SD Reader which i don't prefer because of our USB reset problem.
Took pictures of PCB if someone interested.Can't post original photo because of attachment limit.
Attached pin information for 88F6707.
I will write here my findings.
Just saw your tutorial for RN102 awesome, I will try and give feedback soon.Thank you.
Regards.
Edited 2 time(s). Last edit at 09/06/2020 07:44PM by whitepawn.
Thank you very much for testing USB stuff.I assume it is a flash controller (Inside of USB disk) issue because i investigated hardware USB data pins are soldered directly to CPU itself.USB to SATA seems good option too.If you have time please try with USB SSD Drive also.It seems our box is picky about flash drives.
I have found a USB which was old 8GB one sandisk branded seems ok for now, but i am not sure it works all stable because i disassembled unit with removed heatsink to find GPIO pins for SDIO and SPI Flash:)
To test GPIO test script works and testing SPI flash tomorrow i will try to solder SPI flash with 3 resistors and one capacitor to PCB.
Before soldering SPI flash i will check if GPIO script works on GPIO numbers 63-64-65.How can i know if SPI flash will recognized Bohdi?Will U-boot or kernel initiates SPI Flash?
I have tried to find SDIO pins with GPIO script but no luck so far.It's late in here and i have to sleep.Will try to probe 47 to 52 GPIO numbers.I have checked from pin information also another USB2.0 port modification possible.
Also i investigated mirabox SDIO solution if it was hardwired directly to CPU or not but it seems two USB to SD card controller (GL827) is soldered to box.So basicly its USB SD Reader which i don't prefer because of our USB reset problem.
Took pictures of PCB if someone interested.Can't post original photo because of attachment limit.
Attached pin information for 88F6707.
I will write here my findings.
Just saw your tutorial for RN102 awesome, I will try and give feedback soon.Thank you.
Regards.
Edited 2 time(s). Last edit at 09/06/2020 07:44PM by whitepawn.
|
Re: Debian on Netgear RN102 September 06, 2020 10:23PM |
Admin Registered: 13 years ago Posts: 18,848 |
whitepawn,
> I have found a USB which was old 8GB one sandisk
> branded seems ok for now,
That's good to hear. I suspect that this box controller is running with quite old FW. Perhaps an old Sandisk USB flash drive would play well.
> To test GPIO test script works and testing SPI
> flash tomorrow i will try to solder SPI flash with
> 3 resistors and one capacitor to PCB.
> Before soldering SPI flash i will check if GPIO
> script works on GPIO numbers 63-64-65.How can i
> know if SPI flash will recognized Bohdi?Will
> U-boot or kernel initiates SPI Flash?
I'd doubt this u-boot would recognize the SPI flash. Usually they (NAS manufacturers) do just enough for the box to work. In this case it is NAND flash. However, if any Netgear box (with Armada SoC) has SPI flash, then there is a good chance this u-boot already has that built in. Let's check the listed commands in u-boot prompt that you posted again to see if there is a SPI (ie. sf) command.
The kernel for sure will recognize SPI. Some of the MVEBU boxes have SPI, so I've configured SPI in this kernel. But we also need to modify the DTS for the kernel to know it should probe SPI flash. Once the kernel boots successfully, it will show the SPI flash device as spi0.0 in boot log. Let me know when you think the hardware mod is done and I'll modify the DTS for that purpose.
> Also i investigated mirabox SDIO solution if it
> was hardwired directly to CPU or not but it seems
> two USB to SD card controller (GL827) is soldered
> to box.So basicly its USB SD Reader which i don't
> prefer because of our USB reset problem.
There is an internal SD port in the Mirabox. That should be a real MMC device. But there is some problem with spinning up, I still have not looked into this issue closely. If this special kernel is popular (I monitor the downloads using bitly.com) then I will revisit it. If not, I'll keep that tabled for some rainy days.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I have found a USB which was old 8GB one sandisk
> branded seems ok for now,
That's good to hear. I suspect that this box controller is running with quite old FW. Perhaps an old Sandisk USB flash drive would play well.
> To test GPIO test script works and testing SPI
> flash tomorrow i will try to solder SPI flash with
> 3 resistors and one capacitor to PCB.
> Before soldering SPI flash i will check if GPIO
> script works on GPIO numbers 63-64-65.How can i
> know if SPI flash will recognized Bohdi?Will
> U-boot or kernel initiates SPI Flash?
I'd doubt this u-boot would recognize the SPI flash. Usually they (NAS manufacturers) do just enough for the box to work. In this case it is NAND flash. However, if any Netgear box (with Armada SoC) has SPI flash, then there is a good chance this u-boot already has that built in. Let's check the listed commands in u-boot prompt that you posted again to see if there is a SPI (ie. sf) command.
The kernel for sure will recognize SPI. Some of the MVEBU boxes have SPI, so I've configured SPI in this kernel. But we also need to modify the DTS for the kernel to know it should probe SPI flash. Once the kernel boots successfully, it will show the SPI flash device as spi0.0 in boot log. Let me know when you think the hardware mod is done and I'll modify the DTS for that purpose.
> Also i investigated mirabox SDIO solution if it
> was hardwired directly to CPU or not but it seems
> two USB to SD card controller (GL827) is soldered
> to box.So basicly its USB SD Reader which i don't
> prefer because of our USB reset problem.
There is an internal SD port in the Mirabox. That should be a real MMC device. But there is some problem with spinning up, I still have not looked into this issue closely. If this special kernel is popular (I monitor the downloads using bitly.com) then I will revisit it. If not, I'll keep that tabled for some rainy days.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 07, 2020 09:36AM |
Registered: 5 years ago Posts: 73 |
Hi Bodhi,
You were right about bootloader it can't recognize SPI flash and sf command doesn't work.
Before reading your post i have already soldered parts to PCB so its shame about bootloader and me.
I have good news also before soldering flash I have tested GPIO numbers of 32,63,64 and 65 below script can enable high or low these pins.
From OpenWRT script "static":
chmod +x static.sh
Measure continuosuly the voltage of the pin where you suspect there is a GPIO wired, with a multimeter or another device.
If the pin changes the voltage about 3.3v you have just found GPIO 32
I have soldered 3 (R229 R228 and R257) resistors and 1 capacitor in order to work for SPI chip.Normally 10k resistors and 0.1uf capacitor will be fine.Missing R227 is not needed in our case.I am pretty sure it will work if bootloader has SPI feature but i don't want to mess with bootloader.
Here is my dropbox folder of modification and some pictures of PCB for those playing along at home
https://www.dropbox.com/sh/44vr77r4psy6gkg/AACnT025tiq-jTfBLsQU8A_Ma?dl=0
Here is my bootloader after SPI Chip soldered with sf command:
Also please excuse of my heatsink zip-tie redneck engineering.
Tonight i will work on SDIO GPIO pins.Wish me luck.
Regards.
You were right about bootloader it can't recognize SPI flash and sf command doesn't work.
Before reading your post i have already soldered parts to PCB so its shame about bootloader and me.
I have good news also before soldering flash I have tested GPIO numbers of 32,63,64 and 65 below script can enable high or low these pins.
From OpenWRT script "static":
#!/bin/sh
GPIOBASE=`cat /sys/class/gpio/gpiochip*/base | head -n1`
GPIOmin=`expr $1 + $GPIOBASE`
GPIOmax=`expr $2 + $GPIOBASE`
cd /sys/class/gpio
for i in `seq $GPIOmin $GPIOmax`; do
echo "[GPIO$i] Trying value $3"
echo $i > export; echo out >gpio$i/direction
echo $3 > gpio$i/value
echo $i > unexport
done
chmod +x static.sh
Measure continuosuly the voltage of the pin where you suspect there is a GPIO wired, with a multimeter or another device.
Put GPIO on HIGH state ./static.sh 32 32 1
If the pin changes the voltage about 3.3v you have just found GPIO 32
Put GPIOs on LOW state ./static.sh 32 32 0
I have soldered 3 (R229 R228 and R257) resistors and 1 capacitor in order to work for SPI chip.Normally 10k resistors and 0.1uf capacitor will be fine.Missing R227 is not needed in our case.I am pretty sure it will work if bootloader has SPI feature but i don't want to mess with bootloader.
Here is my dropbox folder of modification and some pictures of PCB for those playing along at home
https://www.dropbox.com/sh/44vr77r4psy6gkg/AACnT025tiq-jTfBLsQU8A_Ma?dl=0
Here is my bootloader after SPI Chip soldered with sf command:
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
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>> sf
Unknown command 'sf' - try 'help'
Marvell>> help
? - alias for 'help'
SatR - Sample At Reset sub-system
active_units- print Board units active
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
bootvx - Boot vxWorks from an ELF image
bootz - boot Linux zImage image from memory
bubt - bubt - Burn an image on the Boot Flash.
chpart - change active partition
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
date - get/set/reset date & time
ddrPhyRead- ddrPhyRead - Read DDR PHY register
ddrPhyWrite- ddrPhyWrite - Write DDR PHY register
dhcp - boot image via network using DHCP/TFTP protocol
diskboot- diskboot- boot from IDE device
dma - dma - Perform DMA using the XOR engine
echo - echo args to console
editenv - edit environment variable
eeprom - EEPROM sub-system
env - environment handling commands
exit - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fdt - flattened device tree utility commands
fsinfo - print information about filesystems
fsload - load binary file from a filesystem image
go - start application at address 'addr'
help - print command description/usage
i2c - I2C sub-system
ide - ide - IDE sub-system
iminfo - print header information for application image
imxtract- extract a part of a multi-image
ir - ir - reading and changing MV internal register values.
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loadx - load binary file over serial line (xmodem mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
ls - list files in a directory (default /)
map - map - Display address decode windows
md - memory display
me - me - PCI master enable
mm - memory modify (auto-incrementing address)
mmc - MMC sub system
mmcinfo - display MMC info
mp - mp - map PCI BAR
mtdparts- define flash/nand partitions
mtest - simple RAM read/write test
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
pci - list and access PCI Configuration Space
pciePhyRead- phyRead - Read PCI-E Phy register
pciePhyWrite- pciePhyWrite - Write PCI-E Phy register
phyRead - phyRead - Read Phy register
phyWrite- phyWrite - Write Phy register
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
pxe - commands to get and boot from pxe files
rcvr - rcvr - Satrt recovery process (Distress Beacon with TFTP server)
reset - Perform RESET of the CPU
resetenv- resetenv - Erase environment sector to reset all variables to default.
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
scsi - SCSI sub-system
scsiboot- boot from SCSI device
se - se - PCI Slave enable
setenv - set environment variables
sg - sg - scanning the PHYs status
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
sp - scan and detect all devices on mvPCI interface
switchCountersRead- switchCntPrint - Read switch port counters.
switchPhyRegRead- - Read switch register
switchPhyRegWrite- - Write switch register
switchRegRead- switchRegRead - Read switch register
switchRegWrite- switchRegWrite - Write switch register
temp - temp - Display the device temperature.
tempCmd0- tempCmd - This command allocated for monitor extinction
tempCmd1- tempCmd - This command allocated for monitor extinction
tempCmd2- tempCmd - This command allocated for monitor extinction
tempCmd3- tempCmd - This command allocated for monitor extinction
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
training- training - prints the results of the DDR3 Training.
true - do nothing, successfully
ts_report- ts_report - report touch screen coordinate
ts_test - ts_test - test touch screen
ubi - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version
whoAmI - - reading CPU ID
Also please excuse of my heatsink zip-tie redneck engineering.
Tonight i will work on SDIO GPIO pins.Wish me luck.
Regards.
|
Re: Debian on Netgear RN102 September 07, 2020 11:14AM |
Registered: 7 years ago Posts: 181 |
Hi bodhi,
In a chest of drawers I found a pile of old HDDs. Some where 3.5" and some 2.5". Some were 'ide' and some where 'sata'. I picked the smallest 'sata', a 100 GB Hitachi 7200 rpm HDD that was born in 2007 and spent its childhood in an Lenovo Thinkpad T60p (according to the post-it note attached to it). The HDD was mounted in in a Deltaco dual bay USB3 docking station (unboxing clip here), which was first connected to the PC to recreate the partition table with 'gparted'. The docking station powers the sata discs externally. Some details on the HDD:
Then the docking station was connected to the upper of the two rear USB3 connectors on the RN102. (I forgot to remove it, so the test today were done with a 2 GB HDD in disc compartment 1.) The root file system ran on the unaltered Scandisk Ultra USB3 thumb drive used in Test D above, so 'stress' was already installed:
Connected the docking station to the PC again, deleted the swap partition and created an single large 'ext3' partition labeled 'rootfs'. 'gparted' warned about "e2label: No such file or directory while trying to open /dev/sdb1. Couldn't find valid filesystem superblock.", but ignored this warning since the label sticked anyhow. Installed the latest Debian root file system and Linux kernel following the brand new installation procedure. Success! You nailed it. Thank you very much for your effort!
I skipped the serial console input since the u-boot environment was already up to date. This is the full log:
Bootlog from first boot attached. I contains this error message at the end:
My only comment to the brand new procedure is that the instructions in "Note1:" are easily overlooked when jumping from Linux kernel installation instructions to Debian file system instructions and back again. Luckily, I recalled:
I just realized that since 'apt update' regularly fails with "not valid yet", my habit of doing 'apt update && apt upgrade -y' is a bad one, and that the latest security patches and bugfixes may not all have been installed when I did some of my previous stress tests. From this day on I will always do 'apt update; apt upgrade -y' instead.
Proceeded with the "all HDD" test:
I noticed that the 1 GiB swap file was created at 21.0 MB/s on my oldest sata HDD compared to 17.4 MB/s on my fastest USB stick. A USB3 connector may have alter the competition, though, and latency is another matter. The boot time was roughly 129 seconds (with random mac address):
Since it may look like swapping on a USB stick causes the issue, I repeated test D in my previous post without swap space:
Using 'gparted', I shrinked the only partition on this USB stick and created a second one for swapping. Booted from the stick and repeated the stress test. This time there was one reset imideately when the test started, but there had been another one already. When trying login at the console the kernel panicked. At this point the test had already been terminated by Ctrl-C. The shell in another window was still alive and responsive, but either 'sudo' or 'shutdown' hang. Also not a solution. The serial console output:
Regards,
Trond Melen
Quote
If you could, run your stress test using one the these 2 configurations.
- With the swap file on HDD.
In a chest of drawers I found a pile of old HDDs. Some where 3.5" and some 2.5". Some were 'ide' and some where 'sata'. I picked the smallest 'sata', a 100 GB Hitachi 7200 rpm HDD that was born in 2007 and spent its childhood in an Lenovo Thinkpad T60p (according to the post-it note attached to it). The HDD was mounted in in a Deltaco dual bay USB3 docking station (unboxing clip here), which was first connected to the PC to recreate the partition table with 'gparted'. The docking station powers the sata discs externally. Some details on the HDD:
lsscsi [1:0:0:0] disk HTS72101 0G9SA00 MCZI /dev/sdb lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdc 8:16 0 93,2G 0 disk
Then the docking station was connected to the upper of the two rear USB3 connectors on the RN102. (I forgot to remove it, so the test today were done with a 2 GB HDD in disc compartment 1.) The root file system ran on the unaltered Scandisk Ultra USB3 thumb drive used in Test D above, so 'stress' was already installed:
sudo mkswap /dev/sdc1
mkswap: /dev/sdc1: warning: wiping old swap signature.
Setting up swapspace version 1, size = 93,2 GiB (100028903424 bytes)
no label, UUID=8e3b4ac7-2658-4735-891b-39da7abe25c4
sudo swapon /dev/sdc1
sudo swapon --summary
Filename Type Size Used Priority
/dev/sdc1 partition 97684476 0 -2
free -h
total used free shared buff/cache available
Mem: 492Mi 64Mi 375Mi 1,0Mi 51Mi 304Mi
Swap: 93Gi 0B 93Gi
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 1,8T 0 disk
└─sda1 8:1 1 1,8T 0 part
└─md0 9:0 0 1,8T 0 raid1 /home
sdb 8:16 1 14,6G 0 disk
└─sdb1 8:17 1 14,6G 0 part /
sdc 8:32 0 93,2G 0 disk
└─sdc1 8:33 0 93,2G 0 part [SWAP]
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
time stress --cpu 1 --io 2 --vm 1 --hdd 1
stress: info: [3415] dispatching hogs: 1 cpu, 2 io, 1 vm, 1 hdd
^C
real 18m20,499s
user 0m0,003s
sys 0m0,017s
After 20 minutes on my phone's stop watch the test was interrupted with Ctrl-C on the keybord. 'time' is buggy and reported 18:20 minutes only. Monitoring swap memory usage with 'htop' in a separate window showed that swap usage never exceeded 6 MiB, i.e. 6 ppm of the available space. No errors were reported on the terminal nor on the serial console, which last line througout the test remained
[ 342.820256][ T3140] Adding 97684476k swap on /dev/sdc1. Priority:-2 extents:1 across:97684476k FS
Quote
If you could, run the installation for the RN102 (part II) as is.
You should copy and paste every commands, like you have a pristine box.
Connected the docking station to the PC again, deleted the swap partition and created an single large 'ext3' partition labeled 'rootfs'. 'gparted' warned about "e2label: No such file or directory while trying to open /dev/sdb1. Couldn't find valid filesystem superblock.", but ignored this warning since the label sticked anyhow. Installed the latest Debian root file system and Linux kernel following the brand new installation procedure. Success! You nailed it. Thank you very much for your effort!
I skipped the serial console input since the u-boot environment was already up to date. This is the full log:
sudo su -
md5sum /tmp/* 2> /dev/null
ffa864878dd797241c0bea05d563239a /tmp/Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2
17c3e1784dea18b2a3587a6ebb7aa894 /tmp/linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2
lsblk | egrep -v '^loop'
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 93,2G 0 disk
└─sdb1 8:17 0 93,2G 0 part
nvme0n1 259:0 0 465,8G 0 disk
├─nvme0n1p1 259:1 0 260M 0 part /boot/efi
├─nvme0n1p2 259:2 0 16M 0 part
├─nvme0n1p3 259:3 0 116,1G 0 part
├─nvme0n1p4 259:4 0 1000M 0 part
└─nvme0n1p5 259:5 0 348,4G 0 part /
mkdir /media/sdb1
mount /dev/sdb1 /media/sdb1
cd /media/sdb1
tar xf /tmp/Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2
mkdir -p /media/sdb1/usr/src/kernel
cd /media/sdb1/usr/src/kernel
tar xf /tmp/linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2
tar xf linux-dtb-5.8.5-mvebu-370xp-tld-1.tar dts/armada-370-netgear-rn102.dtb
cp -a zImage-5.8.5-mvebu-370xp-tld-1 zImage.fdt
cat dts/armada-370-netgear-rn102.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.8.5-mvebu-370xp-tld-1 -d zImage.fdt uImage
Image Name: Linux-5.8.5-mvebu-370xp-tld-1
Created: Mon Sep 7 09:49:18 2020
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5418742 Bytes = 5291.74 KiB = 5.17 MiB
Load Address: 00008000
Entry Point: 00008000
cd /media/sdb1/boot
cp -a /media/sdb1/usr/src/kernel/uImage .
sync
sync
sync
cd
umount /media/sdb1
exit
ssh root@debian.local
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The ECDSA host key for debian.local has changed,
and the key for the corresponding IP address 192.168.1.195
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:MFcjMhGhd2ahQ9xDhil1p+LKnQGIt7Ayqb52VPEHWfc.
Please contact your system administrator.
Add correct host key in /home/tme/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/tme/.ssh/known_hosts:21
remove with:
ssh-keygen -f "/home/tme/.ssh/known_hosts" -R "debian.local"
ECDSA host key for debian.local has changed and you have requested strict checking.
Host key verification failed.
ssh-keygen -f "/home/tme/.ssh/known_hosts" -R "debian.local"
# Host debian.local found: line 21
/home/tme/.ssh/known_hosts updated.
Original contents retained as /home/tme/.ssh/known_hosts.old
ssh root@debian.local
root@debian.local's password:
Linux debian 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.
Last login: Thu Sep 5 01:58:44 2019 from 192.168.0.100
debian
192.168.1.195
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.0
Sun Sep 6 20:44:34 PDT 2020 up 2 minutes
root@debian:~# 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/Linux
root@debian:~# cat /proc/version
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
root@debian:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 1.8T 0 disk
`-sda1 8:1 1 1.8T 0 part
sdb 8:16 0 93.2G 0 disk
`-sdb1 8:17 0 93.2G 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@debian:~# cd /boot
root@debian:/boot# free -h
total used free shared buff/cache available
Mem: 492Mi 35Mi 403Mi 1.0Mi 53Mi 333Mi
Swap: 0B 0B 0B
root@debian:/boot# df -h
Filesystem Size Used Avail Use% Mounted on
udev 242M 0 242M 0% /dev
tmpfs 50M 1.2M 49M 3% /run
/dev/sdb1 92G 790M 86G 1% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 99M 0 99M 0% /dev/shm
tmpfs 247M 0 247M 0% /tmp
root@debian:/boot# cp -a uImage uImage.RN102.bak
root@debian:/boot# dpkg -i /usr/src/kernel/linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb
Selecting previously unselected package linux-image-5.8.5-mvebu-370xp-tld-1.
(Reading database ... 20007 files and directories currently installed.)
Preparing to unpack .../linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb ...
Unpacking linux-image-5.8.5-mvebu-370xp-tld-1 (1.0) ...
Setting up linux-image-5.8.5-mvebu-370xp-tld-1 (1.0) ...
update-initramfs: Generating /boot/initrd.img-5.8.5-mvebu-370xp-tld-1
root@debian:/boot# tar xf /usr/src/kernel/linux-dtb-5.8.5-mvebu-370xp-tld-1.tar
root@debian:/boot# cp -a /usr/src/kernel/zImage-5.8.5-mvebu-370xp-tld-1 .
root@debian:/boot# cp -a zImage-5.8.5-mvebu-370xp-tld-1 zImage.fdt
root@debian:/boot# cat dts/armada-370-netgear-rn102.dtb >> zImage.fdt
root@debian:/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.8.5-mvebu-370xp-tld-1 -d zImage.fdt uImage
Image Name: Linux-5.8.5-mvebu-370xp-tld-1
Created: Sun Sep 6 20:51:31 2020
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5418742 Bytes = 5291.74 KiB = 5.17 MiB
Load Address: 00008000
Entry Point: 00008000
root@debian:/boot# mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.8.5-mvebu-370xp-tld-1 -d initrd.img-5.8.5-mvebu-370xp-tld-1 uInitrd
Image Name: initramfs-5.8.5-mvebu-370xp-tld-
Created: Sun Sep 6 20:51:44 2020
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9504966 Bytes = 9282.19 KiB = 9.06 MiB
Load Address: 00000000
Entry Point: 00000000
root@debian:/boot# 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"
root@debian:/boot# echo "/dev/mtd1 0x00000 0x20000 0x20000" > /etc/fw_env.config
root@debian:/boot# fw_setenv test_xxxx yes
root@debian:/boot# fw_printenv test_xxxx
test_xxxx=yes
root@debian:/boot# fw_printenv
AC_Power_fail_detect=open
CASset=min
HW_version=MVT
MALLOC_len=5
Manufacturer=NETGEAR
Product=ReadyNAS 102
SKUNum=RN102
SerialNum=3ER135EM005C8
Startup=Normal
UUID=31774368-b4c7-11e2-bfbc-28c68e347394
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=3
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=12:34:56:78:90:AB
eth1mtu=1500
ethact=egiga1
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=00:50:43:00:00:02
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
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
ethaddr=12:34:56:78:90:AB
test_xxxx=yes
root@debian:/boot# sync
root@debian:/boot# sync
root@debian:/boot# sync
root@debian:/boot# reboot
Broadcast message from root@debian (pts/0) (Sun Sep 6 21:17:40 2020):
The system is going down for reboot NOW!
root@debian:/boot# Connection to debian.local closed by remote host.
Connection to debian.local closed.
Bootlog from first boot attached. I contains this error message at the end:
[....] Running local boot scripts (/etc/rc.local)Cannot read bad block mark: Invalid argument <13>Sep 6 20:43:05 root[2852]: Cannot read u-boot env ethaddr . okRebooted. The error dissapeared as expected. Here the last part of the reboot's bootlog:
[....] Running local boot scripts (/etc/rc.local)[ 65.861841][ T2915] Setting Persistent MAC address to 12.34.56:78:90:AB <13>Sep 6 21:19:52 root[2922]: Setting Persistent MAC address to 12.34.56:78:90:AB 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/fa:7e:7b:87:7d:e1 Sending on LPF/eth0/fa:7e:7b:87:7d:e1 Sending on Socket/fallback DHCPRELEASE of 192.168.1.195 on eth0 to 192.168.1.1 port 67 [ 67.162301][ T1379] 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/ [ 67.571419][ T2959] mvneta d0074000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL) [ 67.581483][ T2959] mvneta d0074000.ethernet eth0: configuring for phy/rgmii-id link mode Listening on LPF/eth0/12.34.56:78:90:AB Sending on LPF/eth0/12.34.56:78:90:AB Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 [ 70.748423][ T1379] mvneta d0074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 70.756489][ T1379] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPOFFER of 192.168.1.195 from 192.168.1.1 DHCPREQUEST for 192.168.1.195 on eth0 to 255.255.255.255 port 67 DHCPACK of 192.168.1.195 from 192.168.1.1 bound to 192.168.1.195 -- renewal in 42271 seconds. . ok Debian GNU/Linux 10 debian ttyS0 debian login: root Password: Last login: Sun Sep 6 21:23:29 PDT 2020 from 192.168.1.148 on pts/0 Linux debian 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. debian 192.168.1.195 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 l d (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020 Debian 10.0 Sun Sep 6 21:24:14 PDT 2020 up 5 minutes root@debian:~# ifconfig | grep eth eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 12.34.56:78:90:AB txqueuelen 1024 (Ethernet) root@debian:~#Magnifficent! This makes it even more mysterious to me that the box previously consistently shut down after 62 seconds, though. I see no important difference, but clearly there must be one.
My only comment to the brand new procedure is that the instructions in "Note1:" are easily overlooked when jumping from Linux kernel installation instructions to Debian file system instructions and back again. Luckily, I recalled:
rm /etc/ssh/ssh_host* ssh-keygen -A ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 apt-get update Get:1 http://security.debian.org buster/updates InRelease [65.4 kB] Get:2 http://ftp.us.debian.org/debian buster InRelease [122 kB] Get:3 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease [51.9 kB] Get:4 http://security.debian.org buster/updates/main Sources [137 kB] Get:5 http://security.debian.org buster/updates/non-free Sources [692 B] Get:6 http://security.debian.org buster/updates/main armhf Packages [221 kB] Get:7 http://security.debian.org buster/updates/main Translation-en [123 kB] Get:8 http://security.debian.org buster/updates/non-free Translation-en [344 B] Get:9 http://ftp.us.debian.org/debian buster/main Sources [7840 kB] Get:10 http://ftp.us.debian.org/debian buster/main armhf Packages [7698 kB] Get:11 http://ftp.us.debian.org/debian buster/main Translation-en [5968 kB] Reading package lists... Done N: Repository 'http://ftp.us.debian.org/debian buster InRelease' changed its 'Version' value from '10.0' to '10.5' E: Release file for http://http.debian.net/debian/dists/buster-updates/InRelease is not valid yet (invalid for another 3h 34min 50s). Updates for this repository will not be applied. apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: apt apt-transport-https apt-utils base-files bind9-host bzip2 cron dbus dirmngr e2fslibs e2fsprogs gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv initramfs-tools initramfs-tools-core iputils-ping libapt-inst2.0 libapt-pkg5.0 libbind9-161 libbz2-1.0 libcom-err2 libcomerr2 libcryptsetup12 libcurl3-gnutls libdbus-1-3 libdns-export1104 libdns1104 libexpat1 libext2fs2 libgnutls-openssl27 libgnutls30 libicu63 libidn2-0 libisc-export1100 libisc1100 libisccc161 libisccfg163 libjson-c3 libldap-2.4-2 libldap-common liblwres161 libncurses5 libncurses6 libncursesw5 libncursesw6 libperl5.28 libpython2.7-minimal libpython2.7-stdlib libsasl2-2 libsasl2-modules-db libss2 libssl1.1 libsystemd0 libtinfo5 libtinfo6 libudev1 ncurses-base ncurses-bin nfs-common nfs-kernel-server openssh-client openssh-server openssh-sftp-server openssl perl perl-base perl-modules-5.28 python2.7 python2.7-minimal rpcbind systemd tzdata udev 81 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 48.4 MB of archives. After this operation, 49.2 kB of additional disk space will be used. Do you want to continue? [Y/n] y
Quote
If you could, run your stress test using one the these 2 configurations.
- Use HDD rootfs (i.e. the swap file is on the rootfs)
I just realized that since 'apt update' regularly fails with "not valid yet", my habit of doing 'apt update && apt upgrade -y' is a bad one, and that the latest security patches and bugfixes may not all have been installed when I did some of my previous stress tests. From this day on I will always do 'apt update; apt upgrade -y' instead.
E: Release file for http://http.debian.net/debian/dists/buster-updates/InRelease is not valid yet (invalid for another 3h 34min 50s). Updates for this repository will not be applied.
Proceeded with the "all HDD" test:
sh
cat <<'EOF' > /etc/rc.local
# Create a new swap file if it does not exist or is not writable or is not owned by root
if [ ! -w /swapfile ] || [ ! -O /swapfile ]; then
echo $0: "Creating 'swapfile' in the root directory"
swapoff --all
rm --force /swapfile
dd if=/dev/zero of=/swapfile count=8192 bs=131072 # Create 1 GiB swap file ((1024 * 8) * 128 kiB)
chmod 600 /swapfile
mkswap /swapfile
sync
echo $0: $(ls -lFh /swapfile)
fi
# Enable swapping
if [ -w /swapfile ] && [ -O /swapfile ]; then
swapon /swapfile
fi
EOF
> > > > > > > > > > > > > > > > >
exit
/etc/rc.local
/etc/rc.local: Creating 'swapfile' in the root directory
8192+0 records in
8192+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 51.2032 s, 21.0 MB/s
Setting up swapspace version 1, size = 1024 MiB (1073737728 bytes)
no label, UUID=8fbb251d-d00a-42f5-8823-1a8a287a0f9a
/etc/rc.local: -rw------- 1 root root 1.0G Sep 6 22:20 /swapfile
ls -lFh /swapfile
-rw------- 1 root root 1.0G Sep 6 22:20 /swapfile
free -h
total used free shared buff/cache available
Mem: 492Mi 37Mi 96Mi 1.0Mi 358Mi 270Mi
Swap: 1.0Gi 0B 1.0Gi
apt update; apt upgrade -y
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.us.debian.org/debian buster InRelease
Get:3 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists... Done
E: Release file for http://http.debian.net/debian/dists/buster-updates/InRelease is not valid yet (invalid for another 2h 50min 6s). Updates for this repository will not be applied.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
apt install -y stress
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
stress
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 22.6 kB of archives.
After this operation, 50.2 kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian buster/main armhf stress armhf 1.0.4-4 [22.6 kB]
Fetched 22.6 kB in 1s (43.3 kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "nb_NO.UTF-8",
LC_MONETARY = "nb_NO.UTF-8",
LC_ADDRESS = "nb_NO.UTF-8",
LC_TELEPHONE = "nb_NO.UTF-8",
LC_NAME = "nb_NO.UTF-8",
LC_MEASUREMENT = "nb_NO.UTF-8",
LC_IDENTIFICATION = "nb_NO.UTF-8",
LC_NUMERIC = "nb_NO.UTF-8",
LC_PAPER = "nb_NO.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
Selecting previously unselected package stress.
(Reading database ... 22849 files and directories currently installed.)
Preparing to unpack .../stress_1.0.4-4_armhf.deb ...
Unpacking stress (1.0.4-4) ...
Setting up stress (1.0.4-4) ...
Processing triggers for man-db (2.8.5-2) ...
time stress --cpu 1 --io 2 --vm 1 --hdd 1
stress: info: [10968] dispatching hogs: 1 cpu, 2 io, 1 vm, 1 hdd
^C
real 18m19.968s
user 0m0.016s
sys 0m0.011s
Again, no errors were reported on the terminal nor on the serial console before I terminated the test with Ctrl-C after 20 minutes. So, I could not provoke the "USB disconnect/reset high-speed USB device" issue within 20 minutes when swapping to a HDD rather than a USB stick. You had a very good hunch there, bodhi!
I noticed that the 1 GiB swap file was created at 21.0 MB/s on my oldest sata HDD compared to 17.4 MB/s on my fastest USB stick. A USB3 connector may have alter the competition, though, and latency is another matter. The boot time was roughly 129 seconds (with random mac address):
- U-boot startup: 2 s
- U-boot delay: 3 s
- Copy uImage and uInitrd to RAM: 48 s
- Kernel self un-compress: 4 s
- Kernel boot: 6 s (until power LED steady on)
- Debian initialization: 66 s
Since it may look like swapping on a USB stick causes the issue, I repeated test D in my previous post without swap space:
sudo swapoff --all
[sudo] password for tme:
free -h
total used free shared buff/cache available
Mem: 492Mi 38Mi 406Mi 1,0Mi 46Mi 333Mi
Swap: 0B 0B 0B
sudo apt update; sudo apt upgrade -y
sudo apt upgrade -y
sudo apt install -y stress
time stress --cpu 1 --io 2 --vm 1 --hdd 1
stress: info: [3372] dispatching hogs: 1 cpu, 2 io, 1 vm, 1 hdd
After 2 and 3 minutes, there were messages about USB resets, possibly provoked by a 'ssh' login:
[ 798.586853][ T1462] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 872.863958][ T1462] usb 1-1: reset high-speed USB device number 2 using orion-ehciHmm. Not a solution.
Using 'gparted', I shrinked the only partition on this USB stick and created a second one for swapping. Booted from the stick and repeated the stress test. This time there was one reset imideately when the test started, but there had been another one already. When trying login at the console the kernel panicked. At this point the test had already been terminated by Ctrl-C. The shell in another window was still alive and responsive, but either 'sudo' or 'shutdown' hang. Also not a solution. The serial console output:
[ 185.238395][ T3106] Adding 1023996k swap on /dev/sdb2. Priority:-2 extents:1 across:1023996k FS [ 261.746448][ T1457] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 292.631983][ T1457] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 489.680558][ T398] INFO: task kworker/u2:5:1385 blocked for more than 122 seconds. [ 489.687633][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 489.693966][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 489.702327][ T398] kworker/u2:5 D 0 1385 2 0x00000000 [ 489.708071][ T398] Workqueue: writeback wb_workfn (flush-8:16) [ 489.714192][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 489.721957][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 489.729204][ T398] [<c0ab8740>] (io_schedule) from [<c056d270>] (blk_mq_get_tag+0x168/0x270) [ 489.737736][ T398] [<c056d270>] (blk_mq_get_tag) from [<c0569a34>] (__blk_mq_alloc_request+0xec/0x134) [ 489.746909][ T398] [<c0569a34>] (__blk_mq_alloc_request) from [<c056ab44>] (blk_mq_make_request+0xd0/0x4c8) [ 489.756506][ T398] [<c056ab44>] (blk_mq_make_request) from [<c0560790>] (generic_make_request+0xe8/0x1d8) [ 489.765939][ T398] [<c0560790>] (generic_make_request) from [<c05608bc>] (submit_bio+0x3c/0x1a4) [ 489.774645][ T398] [<c05608bc>] (submit_bio) from [<c0359c3c>] (ext4_io_submit+0x4c/0x58) [ 489.782797][ T398] [<c0359c3c>] (ext4_io_submit) from [<c035a050>] (ext4_bio_write_page+0x3f4/0x528) [ 489.791826][ T398] [<c035a050>] (ext4_bio_write_page) from [<c033c3a0>] (mpage_submit_page+0x6c/0x94) [ 489.800934][ T398] [<c033c3a0>] (mpage_submit_page) from [<c033c530>] (mpage_process_page_bufs+0x168/0x17c) [ 489.810013][ T398] [<c033c530>] (mpage_process_page_bufs) from [<c033c744>] (mpage_prepare_extent_to_map+0x200/0x234) [ 489.820623][ T398] [<c033c744>] (mpage_prepare_extent_to_map) from [<c034295c>] (ext4_writepages+0x4a8/0x804) [ 489.829908][ T398] [<c034295c>] (ext4_writepages) from [<c0243d34>] (do_writepages+0x34/0x68) [ 489.838524][ T398] [<c0243d34>] (do_writepages) from [<c02c2988>] (__writeback_single_inode+0xe4/0x4c4) [ 489.847809][ T398] [<c02c2988>] (__writeback_single_inode) from [<c02c32e4>] (writeback_sb_inodes+0x258/0x43c) [ 489.857641][ T398] [<c02c32e4>] (writeback_sb_inodes) from [<c02c352c>] (__writeback_inodes_wb+0x64/0xa0) [ 489.867055][ T398] [<c02c352c>] (__writeback_inodes_wb) from [<c02c37c0>] (wb_writeback+0x258/0x394) [ 489.876094][ T398] [<c02c37c0>] (wb_writeback) from [<c02c4568>] (wb_workfn+0x310/0x3e4) [ 489.884171][ T398] [<c02c4568>] (wb_workfn) from [<c0141dbc>] (process_one_work+0x210/0x358) [ 489.892565][ T398] [<c0141dbc>] (process_one_work) from [<c01426d4>] (worker_thread+0x228/0x2cc) [ 489.901277][ T398] [<c01426d4>] (worker_thread) from [<c014704c>] (kthread+0x13c/0x148) [ 489.908760][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 489.916700][ T398] Exception stack(0xc352ffb0 to 0xc352fff8) [ 489.922501][ T398] ffa0: 00000000 00000000 00000000 00000000 [ 489.931195][ T398] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 489.939388][ T398] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 489.946767][ T398] INFO: task scsi_eh_3:1455 blocked for more than 123 seconds. [ 489.954097][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 489.959810][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 489.968296][ T398] scsi_eh_3 D 0 1455 2 0x00000000 [ 489.974523][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 489.990838][ T398] [<c0ab82a0>] (schedule) from [<c0ab8680>] (schedule_preempt_disabled+0x14/0x20) [ 489.999202][ T398] [<c0ab8680>] (schedule_preempt_disabled) from [<c0ab9700>] (__mutex_lock.constprop.8+0x170/0x2e0) [ 490.030707][ T398] [<c0ab9700>] (__mutex_lock.constprop.8) from [<c07c99e8>] (device_reset+0x1c/0x48) [ 490.039351][ T398] [<c07c99e8>] (device_reset) from [<c06d51a4>] (scsi_try_bus_device_reset+0x24/0x48) [ 490.060668][ T398] [<c06d51a4>] (scsi_try_bus_device_reset) from [<c06d67e8>] (scsi_eh_ready_devs+0x378/0x990) [ 490.069990][ T398] [<c06d67e8>] (scsi_eh_ready_devs) from [<c06d7d24>] (scsi_error_handler+0x298/0x56c) [ 490.086954][ T398] [<c06d7d24>] (scsi_error_handler) from [<c014704c>] (kthread+0x13c/0x148) [ 490.095414][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 490.103226][ T398] Exception stack(0xc3737fb0 to 0xc3737ff8) [ 490.108543][ T398] 7fa0: 00000000 00000000 00000000 00000000 [ 490.117409][ T398] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 490.126602][ T398] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 490.133995][ T398] INFO: task usb-storage:1457 blocked for more than 123 seconds. [ 490.141806][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 490.147520][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.156025][ T398] usb-storage D 0 1457 2 0x00000000 [ 490.162319][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 490.169566][ T398] [<c0ab82a0>] (schedule) from [<c0aba530>] (schedule_timeout+0x24/0xe8) [ 490.177845][ T398] [<c0aba530>] (schedule_timeout) from [<c0ab8c34>] (do_wait_for_common+0xac/0x12c) [ 490.186908][ T398] [<c0ab8c34>] (do_wait_for_common) from [<c0ab8d1c>] (wait_for_common+0x30/0x48) [ 490.195787][ T398] [<c0ab8d1c>] (wait_for_common) from [<c079104c>] (usb_sg_wait+0x70/0x170) [ 490.204237][ T398] [<c079104c>] (usb_sg_wait) from [<c07ca3c0>] (usb_stor_bulk_transfer_sglist.part.2+0x80/0xc4) [ 490.214238][ T398] [<c07ca3c0>] (usb_stor_bulk_transfer_sglist.part.2) from [<c07ca664>] (usb_stor_bulk_srb+0x44/0x74) [ 490.224758][ T398] [<c07ca664>] (usb_stor_bulk_srb) from [<c07ca9e4>] (usb_stor_Bulk_transport+0x13c/0x350) [ 490.234354][ T398] [<c07ca9e4>] (usb_stor_Bulk_transport) from [<c07cadb4>] (usb_stor_invoke_transport+0x2c/0x438) [ 490.244813][ T398] [<c07cadb4>] (usb_stor_invoke_transport) from [<c07cbc7c>] (usb_stor_control_thread+0x1d8/0x224) [ 490.255064][ T398] [<c07cbc7c>] (usb_stor_control_thread) from [<c014704c>] (kthread+0x13c/0x148) [ 490.263904][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 490.271710][ T398] Exception stack(0xc3733fb0 to 0xc3733ff8) [ 490.277027][ T398] 3fa0: 00000000 00000000 00000000 00000000 [ 490.285886][ T398] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 490.294575][ T398] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 490.301927][ T398] INFO: task jbd2/sdb1-8:1513 blocked for more than 123 seconds. [ 490.308920][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 490.315489][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.323925][ T398] jbd2/sdb1-8 D 0 1513 2 0x00000000 [ 490.329674][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 490.337576][ T398] [<c0ab82a0>] (schedule) from [<c037c130>] (jbd2_journal_commit_transaction+0x32c/0x1838) [ 490.347190][ T398] [<c037c130>] (jbd2_journal_commit_transaction) from [<c03823d8>] (kjournald2+0xc8/0x274) [ 490.356787][ T398] [<c03823d8>] (kjournald2) from [<c014704c>] (kthread+0x13c/0x148) [ 490.364536][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 490.372342][ T398] Exception stack(0xc3775fb0 to 0xc3775ff8) [ 490.377661][ T398] 5fa0: 00000000 00000000 00000000 00000000 [ 490.386470][ T398] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 490.395158][ T398] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 490.402409][ T398] INFO: task kworker/0:3:2452 blocked for more than 123 seconds. [ 490.409402][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 490.415724][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.424085][ T398] kworker/0:3 D 0 2452 2 0x00000000 [ 490.429821][ T398] Workqueue: events_freezable_power_ disk_events_workfn [ 490.436739][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 490.444494][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 490.452252][ T398] [<c0ab8740>] (io_schedule) from [<c056d270>] (blk_mq_get_tag+0x168/0x270) [ 490.460137][ T398] [<c056d270>] (blk_mq_get_tag) from [<c0569a34>] (__blk_mq_alloc_request+0xec/0x134) [ 490.469467][ T398] [<c0569a34>] (__blk_mq_alloc_request) from [<c0569ad8>] (blk_mq_alloc_request+0x5c/0xac) [ 490.479057][ T398] [<c0569ad8>] (blk_mq_alloc_request) from [<c055e960>] (blk_get_request+0x80/0xb0) [ 490.488091][ T398] [<c055e960>] (blk_get_request) from [<c06d8370>] (__scsi_execute+0x38/0x178) [ 490.496720][ T398] [<c06d8370>] (__scsi_execute) from [<c06d99ec>] (scsi_test_unit_ready+0x64/0xe8) [ 490.505674][ T398] [<c06d99ec>] (scsi_test_unit_ready) from [<c06e4134>] (sd_check_events+0xd0/0x124) [ 490.514784][ T398] [<c06e4134>] (sd_check_events) from [<c05713d0>] (disk_check_events+0x4c/0x14c) [ 490.523658][ T398] [<c05713d0>] (disk_check_events) from [<c0141dbc>] (process_one_work+0x210/0x358) [ 490.532691][ T398] [<c0141dbc>] (process_one_work) from [<c01426d4>] (worker_thread+0x228/0x2cc) [ 490.541401][ T398] [<c01426d4>] (worker_thread) from [<c014704c>] (kthread+0x13c/0x148) [ 490.548885][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [ 490.556840][ T398] Exception stack(0xddc63fb0 to 0xddc63ff8) [ 490.562806][ T398] 3fa0: 00000000 00000000 00000000 00000000 [ 490.571671][ T398] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 490.579959][ T398] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 490.587347][ T398] INFO: task getty:3075 blocked for more than 123 seconds. [ 490.594354][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 490.600066][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.608556][ T398] getty D 0 3075 1 0x00000000 [ 490.614779][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 490.622532][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 490.630041][ T398] [<c0ab8740>] (io_schedule) from [<c056d270>] (blk_mq_get_tag+0x168/0x270) [ 490.638584][ T398] [<c056d270>] (blk_mq_get_tag) from [<c0569a34>] (__blk_mq_alloc_request+0xec/0x134) [ 490.647779][ T398] [<c0569a34>] (__blk_mq_alloc_request) from [<c056ab44>] (blk_mq_make_request+0xd0/0x4c8) [ 490.657376][ T398] [<c056ab44>] (blk_mq_make_request) from [<c0560790>] (generic_make_request+0xe8/0x1d8) [ 490.666807][ T398] [<c0560790>] (generic_make_request) from [<c05608bc>] (submit_bio+0x3c/0x1a4) [ 490.675518][ T398] [<c05608bc>] (submit_bio) from [<c035a5a0>] (ext4_mpage_readpages+0xd0/0x738) [ 490.684232][ T398] [<c035a5a0>] (ext4_mpage_readpages) from [<c02445c4>] (read_pages+0x50/0x130) [ 490.692955][ T398] [<c02445c4>] (read_pages) from [<c02447a8>] (page_cache_readahead_unbounded+0x104/0x1c4) [ 490.702553][ T398] [<c02447a8>] (page_cache_readahead_unbounded) from [<c0244c98>] (page_cache_sync_readahead+0x78/0x80) [ 490.713184][ T398] [<c0244c98>] (page_cache_sync_readahead) from [<c023cc9c>] (generic_file_buffered_read+0x130/0x574) [ 490.723648][ T398] [<c023cc9c>] (generic_file_buffered_read) from [<c02980d4>] (new_sync_read+0x74/0xb0) [ 490.732990][ T398] [<c02980d4>] (new_sync_read) from [<c02995f8>] (__kernel_read+0x74/0x12c) [ 490.741378][ T398] [<c02995f8>] (__kernel_read) from [<c02a040c>] (__do_execve_file+0x5e0/0xa0c) [ 490.749578][ T398] [<c02a040c>] (__do_execve_file) from [<c02a0a94>] (do_execve+0x24/0x2c) [ 490.757953][ T398] [<c02a0a94>] (do_execve) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [ 490.766068][ T398] Exception stack(0xddd1ffa8 to 0xddd1fff0) [ 490.771866][ T398] ffa0: bee1f740 00000000 004d8a1c bee1f740 bee21dfc b6fb4b94 [ 490.780064][ T398] ffc0: bee1f740 00000000 40000000 0000000b 0000000d bee1f6c8 bee1f784 bee1f7b0 [ 490.788875][ T398] ffe0: 004eaedc bee1f5f4 004d3c87 b6f323d8 [ 490.794681][ T398] INFO: task stress:3114 blocked for more than 123 seconds. [ 490.801768][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 490.807481][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.815962][ T398] stress D 0 3114 1 0x00000001 [ 490.822190][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 490.829432][ T398] [<c0ab82a0>] (schedule) from [<c0ab8680>] (schedule_preempt_disabled+0x14/0x20) [ 490.838432][ T398] [<c0ab8680>] (schedule_preempt_disabled) from [<c0ab9700>] (__mutex_lock.constprop.8+0x170/0x2e0) [ 490.848749][ T398] [<c0ab9700>] (__mutex_lock.constprop.8) from [<c02d3288>] (iterate_bdevs+0xc4/0xfc) [ 490.857953][ T398] [<c02d3288>] (iterate_bdevs) from [<c02c77a0>] (ksys_sync+0x5c/0xb0) [ 490.865941][ T398] [<c02c77a0>] (ksys_sync) from [<c02c77fc>] (sys_sync+0x8/0x10) [ 490.873449][ T398] [<c02c77fc>] (sys_sync) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [ 490.881497][ T398] Exception stack(0xdefb3fa8 to 0xdefb3ff0) [ 490.886817][ T398] 3fa0: 00000000 0042cf3c 00000000 00000000 3544ce00 00000000 [ 490.895632][ T398] 3fc0: 00000000 0042cf3c 00000001 00000024 b6edee54 00003a98 00000000 00000001 [ 490.904313][ T398] 3fe0: 0042cfcc beebb46c 004190f7 b6e7dc78 [ 490.909637][ T398] INFO: task stress:3116 blocked for more than 124 seconds. [ 490.916852][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 490.923045][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.930918][ T398] stress D 0 3116 1 0x00000001 [ 490.937286][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 490.945022][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 490.952755][ T398] [<c0ab8740>] (io_schedule) from [<c0ab8ab4>] (bit_wait_io+0xc/0x30) [ 490.960197][ T398] [<c0ab8ab4>] (bit_wait_io) from [<c0ab8798>] (__wait_on_bit+0x48/0x88) [ 490.968464][ T398] [<c0ab8798>] (__wait_on_bit) from [<c0ab8858>] (out_of_line_wait_on_bit+0x80/0xa4) [ 490.977570][ T398] [<c0ab8858>] (out_of_line_wait_on_bit) from [<c0322e1c>] (ext4_wait_block_bitmap+0x48/0xe8) [ 490.987389][ T398] [<c0322e1c>] (ext4_wait_block_bitmap) from [<c034a81c>] (ext4_mb_init_cache+0x1ac/0x4f8) [ 490.996996][ T398] [<c034a81c>] (ext4_mb_init_cache) from [<c034ac50>] (ext4_mb_init_group+0xe8/0x17c) [ 491.006185][ T398] [<c034ac50>] (ext4_mb_init_group) from [<c034cfcc>] (ext4_mb_regular_allocator+0x2a0/0x400) [ 491.016015][ T398] [<c034cfcc>] (ext4_mb_regular_allocator) from [<c034e704>] (ext4_mb_new_blocks+0x3d8/0xbdc) [ 491.025843][ T398] [<c034e704>] (ext4_mb_new_blocks) from [<c0337888>] (ext4_ind_map_blocks+0x58c/0x99c) [ 491.035195][ T398] [<c0337888>] (ext4_ind_map_blocks) from [<c033ee34>] (ext4_map_blocks+0x398/0x530) [ 491.044316][ T398] [<c033ee34>] (ext4_map_blocks) from [<c033f020>] (_ext4_get_block+0x54/0xc8) [ 491.052944][ T398] [<c033f020>] (_ext4_get_block) from [<c033d9f0>] (ext4_block_write_begin+0x1cc/0x3d4) [ 491.062300][ T398] [<c033d9f0>] (ext4_block_write_begin) from [<c0343ed8>] (ext4_write_begin+0x260/0x3ac) [ 491.071725][ T398] [<c0343ed8>] (ext4_write_begin) from [<c023b404>] (generic_perform_write+0xa8/0x1a8) [ 491.080492][ T398] [<c023b404>] (generic_perform_write) from [<c03314e0>] (ext4_buffered_write_iter+0xa8/0x130) [ 491.090544][ T398] [<c03314e0>] (ext4_buffered_write_iter) from [<c03316d8>] (ext4_file_write_iter+0x10c/0x850) [ 491.100457][ T398] [<c03316d8>] (ext4_file_write_iter) from [<c0298184>] (new_sync_write+0x74/0xb4) [ 491.109410][ T398] [<c0298184>] (new_sync_write) from [<c0299afc>] (vfs_write+0x140/0x148) [ 491.117632][ T398] [<c0299afc>] (vfs_write) from [<c0299c24>] (ksys_write+0x68/0xb4) [ 491.125363][ T398] [<c0299c24>] (ksys_write) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [ 491.133563][ T398] Exception stack(0xc3a65fa8 to 0xc3a65ff0) [ 491.138881][ T398] 5fa0: 00000074 00000003 00000003 bedbb3f8 000fffff 00000000 [ 491.147690][ T398] 5fc0: 00000074 00000003 00000000 00000004 00000000 00000000 000fffff 00000000 [ 491.156361][ T398] 5fe0: 00000004 bedbb3c8 b6e765b3 b6dff746 [ 491.162163][ T398] INFO: task stress:3117 blocked for more than 124 seconds. [ 491.168792][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [ 491.175115][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 491.183476][ T398] stress D 0 3117 1 0x00000001 [ 491.189224][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [ 491.197100][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [ 491.204857][ T398] [<c0ab8740>] (io_schedule) from [<c056d270>] (blk_mq_get_tag+0x168/0x270) [ 491.213245][ T398] [<c056d270>] (blk_mq_get_tag) from [<c0569a34>] (__blk_mq_alloc_request+0xec/0x134) [ 491.222443][ T398] [<c0569a34>] (__blk_mq_alloc_request) from [<c056ab44>] (blk_mq_make_request+0xd0/0x4c8) [ 491.232035][ T398] [<c056ab44>] (blk_mq_make_request) from [<c0560790>] (generic_make_request+0xe8/0x1d8) [ 491.240956][ T398] [<c0560790>] (generic_make_request) from [<c05608bc>] (submit_bio+0x3c/0x1a4) [ 491.249813][ T398] [<c05608bc>] (submit_bio) from [<c02cc984>] (submit_bh_wbc.constprop.24+0x188/0x198) [ 491.259100][ T398] [<c02cc984>] (submit_bh_wbc.constprop.24) from [<c02ced10>] (__block_write_full_page+0x288/0x3a4) [ 491.269416][ T398] [<c02ced10>] (__block_write_full_page) from [<c02cef2c>] (block_write_full_page+0x50/0xac) [ 491.279174][ T398] [<c02cef2c>] (block_write_full_page) from [<c02418b8>] (__writepage+0x14/0x58) [ 491.288188][ T398] [<c02418b8>] (__writepage) from [<c0243434>] (write_cache_pages+0x2d4/0x384) [ 491.296822][ T398] [<c0243434>] (write_cache_pages) from [<c0243530>] (generic_writepages+0x4c/0x80) [ 491.305848][ T398] [<c0243530>] (generic_writepages) from [<c0243d34>] (do_writepages+0x34/0x68) [ 491.314782][ T398] [<c0243d34>] (do_writepages) from [<c023c498>] (__filemap_fdatawrite_range+0x7c/0x9c) [ 491.324140][ T398] [<c023c498>] (__filemap_fdatawrite_range) from [<c023c61c>] (filemap_fdatawrite+0x24/0x2c) [ 491.333884][ T398] [<c023c61c>] (filemap_fdatawrite) from [<c02d32a0>] (iterate_bdevs+0xdc/0xfc) [ 491.342595][ T398] [<c02d32a0>] (iterate_bdevs) from [<c02c77a0>] (ksys_sync+0x5c/0xb0) [ 491.350074][ T398] [<c02c77a0>] (ksys_sync) from [<c02c77fc>] (sys_sync+0x8/0x10) [ 491.357717][ T398] [<c02c77fc>] (sys_sync) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [ 491.365753][ T398] Exception stack(0xdb42ffa8 to 0xdb42fff0) [ 491.371108][ T398] ffa0: 00000000 0042cf3c 00000000 00000000 3544ce00 00000000 [ 491.379910][ T398] ffc0: 00000000 0042cf3c 00000001 00000024 b6edee54 00000bb8 00000000 00000004 [ 491.388587][ T398] ffe0: 0042cfcc beebb46c 004190f7 b6e7dc78
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 September 07, 2020 11:31AM |
Registered: 7 years ago Posts: 181 |
Hi whitepawn,
As requested, I repeated the test with an SSD in the docking station. It was a 160 GB Intel 320 Series pulled out of a Lenovo Thinkpad X220 about 3 years ago which had not been used since then. I did the installation from scratch, following my own log above, so now I've tested and verified the procedure, both with HDD and SSD (with the exception of the serial console input). Success again!
Running the test for 20 minutes, 3 instances of USB resets were reported on the serial console, but nothing else, so I let the test continue. After 2 hours, this was the serial console output:
The boot time with the root file sytem on SSD was roughly 128 seconds (with persistent mac address). Apparently, the box hardly benefits form the bandwidth of an SSD when it is behind a slow USB2 connector:
Observation summary:
Finally, I tested if the box would boot with the SSD mounted in one of the two disc compartments. It did not. U-boot never found the disc.
Regards,
Trond Melen
As requested, I repeated the test with an SSD in the docking station. It was a 160 GB Intel 320 Series pulled out of a Lenovo Thinkpad X220 about 3 years ago which had not been used since then. I did the installation from scratch, following my own log above, so now I've tested and verified the procedure, both with HDD and SSD (with the exception of the serial console input). Success again!
/etc/rc.local /etc/rc.local: Creating 'swapfile' in the root directory 8192+0 records in 8192+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 50.8009 s, 21.1 MB/s Setting up swapspace version 1, size = 1024 MiB (1073737728 bytes) no label, UUID=33dd251d-8bab-461a-abfe-8db8b3922f39 /etc/rc.local: -rw------- 1 root root 1.0G Sep 7 01:40 /swapfile apt install -y stress time stress --cpu 1 --io 2 --vm 1 --hdd 1 stress: info: [3372] dispatching hogs: 1 cpu, 2 io, 1 vm, 1 hdd
Running the test for 20 minutes, 3 instances of USB resets were reported on the serial console, but nothing else, so I let the test continue. After 2 hours, this was the serial console output:
[ 1838.785852][T16896] Adding 1048572k swap on /swapfile. Priority:-2 extents:15 across:69114596k FS [ 2573.983300][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 2888.340477][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 2919.225888][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 3440.706678][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 3471.181908][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 3716.204414][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 4536.675134][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 5622.357493][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 5677.725145][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 5993.633112][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 6024.138352][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 6651.011796][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 6682.387520][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 6713.763208][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 6911.502045][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 8445.569070][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 8476.564604][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehciAt this point I had concluded that USB reset is an everyday thing, and that the issue is due to the box or device unable to handle them well. To get some fresh air, I made a short walk outside, just to find these lines added to the console as I returned:
[ 9412.712746][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9444.728694][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9475.464020][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9506.199438][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9536.934758][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9568.310462][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9600.966831][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9631.702174][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9662.437508][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9693.172879][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9723.908260][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9755.283934][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9788.580586][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9819.315989][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9850.691696][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9882.067327][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9912.802709][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9944.178382][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 9975.554122][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [10008.210414][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [10038.945809][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [10069.681166][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [10100.416560][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [10131.151876][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [10163.177882][ T1458] usb 1-1: reset high-speed USB device number 2 using orion-ehci [10324.998870][ T398] INFO: task scsi_eh_3:1456 blocked for more than 122 seconds. [10325.005708][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10325.028810][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10325.036687][ T398] scsi_eh_3 D 0 1456 2 0x00000000 [10325.058859][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10325.066104][ T398] [<c0ab82a0>] (schedule) from [<c0ab8680>] (schedule_preempt_disabled+0x14/0x20) [10325.088843][ T398] [<c0ab8680>] (schedule_preempt_disabled) from [<c0ab9700>] (__mutex_lock.constprop.8+0x170/0x2e0) [10325.098653][ T398] [<c0ab9700>] (__mutex_lock.constprop.8) from [<c07c99e8>] (device_reset+0x1c/0x48) [10325.128887][ T398] [<c07c99e8>] (device_reset) from [<c06d51a4>] (scsi_try_bus_device_reset+0x24/0x48) [10325.137571][ T398] [<c06d51a4>] (scsi_try_bus_device_reset) from [<c06d67e8>] (scsi_eh_ready_devs+0x378/0x990) [10325.159152][ T398] [<c06d67e8>] (scsi_eh_ready_devs) from [<c06d7d24>] (scsi_error_handler+0x298/0x56c) [10325.167917][ T398] [<c06d7d24>] (scsi_error_handler) from [<c014704c>] (kthread+0x13c/0x148) [10325.198922][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [10325.206237][ T398] Exception stack(0xc36dbfb0 to 0xc36dbff8) [10325.218909][ T398] bfa0: 00000000 00000000 00000000 00000000 [10325.227105][ T398] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [10325.258933][ T398] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [10325.265703][ T398] INFO: task jbd2/sdb1-8:1514 blocked for more than 123 seconds. [10325.278926][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10325.284639][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10325.308916][ T398] jbd2/sdb1-8 D 0 1514 2 0x00000000 [10325.314666][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10325.338996][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [10325.346240][ T398] [<c0ab8740>] (io_schedule) from [<c0ab8ab4>] (bit_wait_io+0xc/0x30) [10325.368965][ T398] [<c0ab8ab4>] (bit_wait_io) from [<c0ab8798>] (__wait_on_bit+0x48/0x88) [10325.376606][ T398] [<c0ab8798>] (__wait_on_bit) from [<c0ab8858>] (out_of_line_wait_on_bit+0x80/0xa4) [10325.399037][ T398] [<c0ab8858>] (out_of_line_wait_on_bit) from [<c037cce0>] (jbd2_journal_commit_transaction+0xedc/0x1838) [10325.419028][ T398] [<c037cce0>] (jbd2_journal_commit_transaction) from [<c03823d8>] (kjournald2+0xc8/0x274) [10325.428112][ T398] [<c03823d8>] (kjournald2) from [<c014704c>] (kthread+0x13c/0x148) [10325.459058][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [10325.466372][ T398] Exception stack(0xc373dfb0 to 0xc373dff8) [10325.479024][ T398] dfa0: 00000000 00000000 00000000 00000000 [10325.487219][ T398] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [10325.509050][ T398] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [10325.515828][ T398] INFO: task stress:16929 blocked for more than 123 seconds. [10325.539015][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10325.544723][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10325.569067][ T398] stress D 0 16929 16927 0x00000000 [10325.574816][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10325.599063][ T398] [<c0ab82a0>] (schedule) from [<c038181c>] (jbd2_log_wait_commit+0xc0/0xe8) [10325.607023][ T398] [<c038181c>] (jbd2_log_wait_commit) from [<c036afd4>] (ext4_sync_fs+0x180/0x1f4) [10325.629138][ T398] [<c036afd4>] (ext4_sync_fs) from [<c029cb20>] (iterate_supers+0x98/0xcc) [10325.636941][ T398] [<c029cb20>] (iterate_supers) from [<c02c7794>] (ksys_sync+0x50/0xb0) [10325.659144][ T398] [<c02c7794>] (ksys_sync) from [<c02c77fc>] (sys_sync+0x8/0x10) [10325.666145][ T398] [<c02c77fc>] (sys_sync) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [10325.689088][ T398] Exception stack(0xdd447fa8 to 0xdd447ff0) [10325.694398][ T398] 7fa0: 00000000 00502f3c 00000000 00000000 f659fc00 00000000 [10325.719123][ T398] 7fc0: 00000000 00502f3c 00000001 00000024 b6f03e54 00003a98 00000000 00000001 [10325.727313][ T398] 7fe0: 00502fcc bed5ea5c 004ef0f7 b6ea2c78 [10325.739166][ T398] INFO: task stress:16931 blocked for more than 123 seconds. [10325.745863][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10325.769134][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10325.777010][ T398] stress D 0 16931 16927 0x00000000 [10325.789201][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10325.796440][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [10325.819229][ T398] [<c0ab8740>] (io_schedule) from [<c0ab8ab4>] (bit_wait_io+0xc/0x30) [10325.826627][ T398] [<c0ab8ab4>] (bit_wait_io) from [<c0ab8798>] (__wait_on_bit+0x48/0x88) [10325.849186][ T398] [<c0ab8798>] (__wait_on_bit) from [<c0ab8858>] (out_of_line_wait_on_bit+0x80/0xa4) [10325.857792][ T398] [<c0ab8858>] (out_of_line_wait_on_bit) from [<c037aa00>] (do_get_write_access+0x2bc/0x460) [10325.889235][ T398] [<c037aa00>] (do_get_write_access) from [<c037abec>] (jbd2_journal_get_write_access+0x48/0x74) [10325.898799][ T398] [<c037abec>] (jbd2_journal_get_write_access) from [<c0325dc8>] (__ext4_journal_get_write_access+0x28/0x58) [10325.929256][ T398] [<c0325dc8>] (__ext4_journal_get_write_access) from [<c03419bc>] (ext4_reserve_inode_write+0x54/0x88) [10325.949298][ T398] [<c03419bc>] (ext4_reserve_inode_write) from [<c0341c6c>] (__ext4_mark_inode_dirty+0xe8/0x264) [10325.958857][ T398] [<c0341c6c>] (__ext4_mark_inode_dirty) from [<c034580c>] (ext4_dirty_inode+0x58/0x7c) [10325.989329][ T398] [<c034580c>] (ext4_dirty_inode) from [<c02c25c4>] (__mark_inode_dirty+0x174/0x454) [10325.997930][ T398] [<c02c25c4>] (__mark_inode_dirty) from [<c034e4e8>] (ext4_mb_new_blocks+0x1bc/0xbdc) [10326.019340][ T398] [<c034e4e8>] (ext4_mb_new_blocks) from [<c0337888>] (ext4_ind_map_blocks+0x58c/0x99c) [10326.028184][ T398] [<c0337888>] (ext4_ind_map_blocks) from [<c033ee34>] (ext4_map_blocks+0x398/0x530) [10326.059350][ T398] [<c033ee34>] (ext4_map_blocks) from [<c033f020>] (_ext4_get_block+0x54/0xc8) [10326.067470][ T398] [<c033f020>] (_ext4_get_block) from [<c033d9f0>] (ext4_block_write_begin+0x1cc/0x3d4) [10326.089300][ T398] [<c033d9f0>] (ext4_block_write_begin) from [<c0343ed8>] (ext4_write_begin+0x260/0x3ac) [10326.098216][ T398] [<c0343ed8>] (ext4_write_begin) from [<c023b404>] (generic_perform_write+0xa8/0x1a8) [10326.129368][ T398] [<c023b404>] (generic_perform_write) from [<c03314e0>] (ext4_buffered_write_iter+0xa8/0x130) [10326.138772][ T398] [<c03314e0>] (ext4_buffered_write_iter) from [<c03316d8>] (ext4_file_write_iter+0x10c/0x850) [10326.169377][ T398] [<c03316d8>] (ext4_file_write_iter) from [<c0298184>] (new_sync_write+0x74/0xb4) [10326.177817][ T398] [<c0298184>] (new_sync_write) from [<c0299afc>] (vfs_write+0x140/0x148) [10326.199569][ T398] [<c0299afc>] (vfs_write) from [<c0299c24>] (ksys_write+0x68/0xb4) [10326.206810][ T398] [<c0299c24>] (ksys_write) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [10326.229408][ T398] Exception stack(0xdb26dfa8 to 0xdb26dff0) [10326.234726][ T398] dfa0: 00000074 00000003 00000003 bec5e9e8 000fffff 00000000 [10326.259427][ T398] dfc0: 00000074 00000003 00000000 00000004 09efff61 00000000 09ffff60 00000000 [10326.267618][ T398] dfe0: 00000004 bec5e9b8 b6e9b5b3 b6e24746 [10326.279397][ T398] INFO: task stress:16932 blocked for more than 124 seconds. [10326.286064][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10326.309434][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10326.317307][ T398] stress D 0 16932 16927 0x00000000 [10326.329432][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10326.336673][ T398] [<c0ab82a0>] (schedule) from [<c038181c>] (jbd2_log_wait_commit+0xc0/0xe8) [10326.379533][ T398] [<c038181c>] (jbd2_log_wait_commit) from [<c036afd4>] (ext4_sync_fs+0x180/0x1f4) [10326.387984][ T398] [<c036afd4>] (ext4_sync_fs) from [<c029cb20>] (iterate_supers+0x98/0xcc) [10326.419560][ T398] [<c029cb20>] (iterate_supers) from [<c02c7794>] (ksys_sync+0x50/0xb0) [10326.427120][ T398] [<c02c7794>] (ksys_sync) from [<c02c77fc>] (sys_sync+0x8/0x10) [10326.469631][ T398] [<c02c77fc>] (sys_sync) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [10326.477184][ T398] Exception stack(0xde1fffa8 to 0xde1ffff0) [10326.506438][ T398] ffa0: 00000000 00502f3c 00000000 00000000 f659fc00 00000000 [10326.519527][ T398] ffc0: 00000000 00502f3c 00000001 00000024 b6f03e54 00000bb8 00000000 00000004 [10326.528456][ T398] ffe0: 00502fcc bed5ea5c 004ef0f7 b6ea2c78 [10447.940336][ T398] INFO: task scsi_eh_3:1456 blocked for more than 245 seconds. [10447.947171][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10447.970231][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10447.978104][ T398] scsi_eh_3 D 0 1456 2 0x00000000 [10447.990317][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10447.997558][ T398] [<c0ab82a0>] (schedule) from [<c0ab8680>] (schedule_preempt_disabled+0x14/0x20) [10448.030331][ T398] [<c0ab8680>] (schedule_preempt_disabled) from [<c0ab9700>] (__mutex_lock.constprop.8+0x170/0x2e0) [10448.040141][ T398] [<c0ab9700>] (__mutex_lock.constprop.8) from [<c07c99e8>] (device_reset+0x1c/0x48) [10448.060296][ T398] [<c07c99e8>] (device_reset) from [<c06d51a4>] (scsi_try_bus_device_reset+0x24/0x48) [10448.068973][ T398] [<c06d51a4>] (scsi_try_bus_device_reset) from [<c06d67e8>] (scsi_eh_ready_devs+0x378/0x990) [10448.120361][ T398] [<c06d67e8>] (scsi_eh_ready_devs) from [<c06d7d24>] (scsi_error_handler+0x298/0x56c) [10448.129126][ T398] [<c06d7d24>] (scsi_error_handler) from [<c014704c>] (kthread+0x13c/0x148) [10448.170487][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [10448.177801][ T398] Exception stack(0xc36dbfb0 to 0xc36dbff8) [10448.206326][ T398] bfa0: 00000000 00000000 00000000 00000000 [10448.230465][ T398] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [10448.238659][ T398] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [10448.260730][ T398] INFO: task jbd2/sdb1-8:1514 blocked for more than 246 seconds. [10448.268346][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10448.290452][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10448.298329][ T398] jbd2/sdb1-8 D 0 1514 2 0x00000000 [10448.310522][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10448.317796][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [10448.340462][ T398] [<c0ab8740>] (io_schedule) from [<c0ab8ab4>] (bit_wait_io+0xc/0x30) [10448.347863][ T398] [<c0ab8ab4>] (bit_wait_io) from [<c0ab8798>] (__wait_on_bit+0x48/0x88) [10448.370555][ T398] [<c0ab8798>] (__wait_on_bit) from [<c0ab8858>] (out_of_line_wait_on_bit+0x80/0xa4) [10448.379168][ T398] [<c0ab8858>] (out_of_line_wait_on_bit) from [<c037cce0>] (jbd2_journal_commit_transaction+0xedc/0x1838) [10448.408945][ T398] [<c037cce0>] (jbd2_journal_commit_transaction) from [<c03823d8>] (kjournald2+0xc8/0x274) [10448.430524][ T398] [<c03823d8>] (kjournald2) from [<c014704c>] (kthread+0x13c/0x148) [10448.437762][ T398] [<c014704c>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c) [10448.460529][ T398] Exception stack(0xc373dfb0 to 0xc373dff8) [10448.465846][ T398] dfa0: 00000000 00000000 00000000 00000000 [10448.490537][ T398] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [10448.498726][ T398] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [10448.520635][ T398] INFO: task syslogd:2681 blocked for more than 122 seconds. [10448.527309][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10448.540520][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10448.548385][ T398] syslogd D 0 2681 1 0x00000000 [10448.570564][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10448.577804][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [10448.600592][ T398] [<c0ab8740>] (io_schedule) from [<c056d270>] (blk_mq_get_tag+0x168/0x270) [10448.608474][ T398] [<c056d270>] (blk_mq_get_tag) from [<c0569a34>] (__blk_mq_alloc_request+0xec/0x134) [10448.630632][ T398] [<c0569a34>] (__blk_mq_alloc_request) from [<c056ab44>] (blk_mq_make_request+0xd0/0x4c8) [10448.639717][ T398] [<c056ab44>] (blk_mq_make_request) from [<c0560790>] (generic_make_request+0xe8/0x1d8) [10448.670650][ T398] [<c0560790>] (generic_make_request) from [<c05608bc>] (submit_bio+0x3c/0x1a4) [10448.678860][ T398] [<c05608bc>] (submit_bio) from [<c0280c74>] (swap_readpage+0x1f0/0x274) [10448.700675][ T398] [<c0280c74>] (swap_readpage) from [<c0281a58>] (swap_cluster_readahead+0x220/0x26c) [10448.709364][ T398] [<c0281a58>] (swap_cluster_readahead) from [<c024f61c>] (shmem_swapin+0x4c/0x6c) [10448.730626][ T398] [<c024f61c>] (shmem_swapin) from [<c0251094>] (shmem_swapin_page+0x94/0x420) [10448.738743][ T398] [<c0251094>] (shmem_swapin_page) from [<c025178c>] (shmem_getpage_gfp.constprop.5+0xc8/0x410) [10448.770678][ T398] [<c025178c>] (shmem_getpage_gfp.constprop.5) from [<c0251d10>] (shmem_fault+0x1b4/0x1f4) [10448.779769][ T398] [<c0251d10>] (shmem_fault) from [<c0265bdc>] (__do_fault+0x54/0x7c) [10448.800676][ T398] [<c0265bdc>] (__do_fault) from [<c02698c4>] (handle_mm_fault+0x798/0x938) [10448.808563][ T398] [<c02698c4>] (handle_mm_fault) from [<c01199c0>] (do_page_fault+0x18c/0x314) [10448.840711][ T398] [<c01199c0>] (do_page_fault) from [<c0119ca4>] (do_DataAbort+0x38/0xb8) [10448.848435][ T398] [<c0119ca4>] (do_DataAbort) from [<c01015dc>] (__dabt_usr+0x3c/0x40) [10448.870723][ T398] Exception stack(0xded53fb0 to 0xded53ff8) [10448.876040][ T398] 3fa0: b6e33fa4 00541dfc 0000002b 3037332d [10448.890702][ T398] 3fc0: 00541150 0001100b 00541d90 0000006f b6f85968 00000000 0054070c 00000000 [10448.898889][ T398] 3fe0: b6e34010 befccb98 004e108b b6ea227c 000b0010 ffffffff [10448.920787][ T398] INFO: task stress:16929 blocked for more than 246 seconds. [10448.927492][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10448.950710][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10448.958576][ T398] stress D 0 16929 16927 0x00000000 [10448.980811][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10448.988058][ T398] [<c0ab82a0>] (schedule) from [<c038181c>] (jbd2_log_wait_commit+0xc0/0xe8) [10449.010760][ T398] [<c038181c>] (jbd2_log_wait_commit) from [<c036afd4>] (ext4_sync_fs+0x180/0x1f4) [10449.019201][ T398] [<c036afd4>] (ext4_sync_fs) from [<c029cb20>] (iterate_supers+0x98/0xcc) [10449.040835][ T398] [<c029cb20>] (iterate_supers) from [<c02c7794>] (ksys_sync+0x50/0xb0) [10449.048394][ T398] [<c02c7794>] (ksys_sync) from [<c02c77fc>] (sys_sync+0x8/0x10) [10449.070788][ T398] [<c02c77fc>] (sys_sync) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [10449.078335][ T398] Exception stack(0xdd447fa8 to 0xdd447ff0) [10449.090841][ T398] 7fa0: 00000000 00502f3c 00000000 00000000 f659fc00 00000000 [10449.099033][ T398] 7fc0: 00000000 00502f3c 00000001 00000024 b6f03e54 00003a98 00000000 00000001 [10449.130865][ T398] 7fe0: 00502fcc bed5ea5c 004ef0f7 b6ea2c78 [10449.136192][ T398] INFO: task stress:16931 blocked for more than 246 seconds. [10449.150826][ T398] Not tainted 5.8.5-mvebu-370xp-tld-1 #1.0 [10449.156531][ T398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10449.180839][ T398] stress D 0 16931 16927 0x00000000 [10449.186585][ T398] [<c0ab810c>] (__schedule) from [<c0ab82a0>] (schedule+0xc0/0x120) [10449.200910][ T398] [<c0ab82a0>] (schedule) from [<c0ab8740>] (io_schedule+0x14/0x24) [10449.208150][ T398] [<c0ab8740>] (io_schedule) from [<c0ab8ab4>] (bit_wait_io+0xc/0x30) [10449.230891][ T398] [<c0ab8ab4>] (bit_wait_io) from [<c0ab8798>] (__wait_on_bit+0x48/0x88) [10449.238531][ T398] [<c0ab8798>] (__wait_on_bit) from [<c0ab8858>] (out_of_line_wait_on_bit+0x80/0xa4) [10449.270928][ T398] [<c0ab8858>] (out_of_line_wait_on_bit) from [<c037aa00>] (do_get_write_access+0x2bc/0x460) [10449.280170][ T398] [<c037aa00>] (do_get_write_access) from [<c037abec>] (jbd2_journal_get_write_access+0x48/0x74) [10449.301063][ T398] [<c037abec>] (jbd2_journal_get_write_access) from [<c0325dc8>] (__ext4_journal_get_write_access+0x28/0x58) [10449.331008][ T398] [<c0325dc8>] (__ext4_journal_get_write_access) from [<c03419bc>] (ext4_reserve_inode_write+0x54/0x88) [10449.350944][ T398] [<c03419bc>] (ext4_reserve_inode_write) from [<c0341c6c>] (__ext4_mark_inode_dirty+0xe8/0x264) [10449.360499][ T398] [<c0341c6c>] (__ext4_mark_inode_dirty) from [<c034580c>] (ext4_dirty_inode+0x58/0x7c) [10449.380977][ T398] [<c034580c>] (ext4_dirty_inode) from [<c02c25c4>] (__mark_inode_dirty+0x174/0x454) [10449.389576][ T398] [<c02c25c4>] (__mark_inode_dirty) from [<c034e4e8>] (ext4_mb_new_blocks+0x1bc/0xbdc) [10449.421047][ T398] [<c034e4e8>] (ext4_mb_new_blocks) from [<c0337888>] (ext4_ind_map_blocks+0x58c/0x99c) [10449.429894][ T398] [<c0337888>] (ext4_ind_map_blocks) from [<c033ee34>] (ext4_map_blocks+0x398/0x530) [10449.450979][ T398] [<c033ee34>] (ext4_map_blocks) from [<c033f020>] (_ext4_get_block+0x54/0xc8) [10449.459094][ T398] [<c033f020>] (_ext4_get_block) from [<c033d9f0>] (ext4_block_write_begin+0x1cc/0x3d4) [10449.491066][ T398] [<c033d9f0>] (ext4_block_write_begin) from [<c0343ed8>] (ext4_write_begin+0x260/0x3ac) [10449.499988][ T398] [<c0343ed8>] (ext4_write_begin) from [<c023b404>] (generic_perform_write+0xa8/0x1a8) [10449.521086][ T398] [<c023b404>] (generic_perform_write) from [<c03314e0>] (ext4_buffered_write_iter+0xa8/0x130) [10449.530487][ T398] [<c03314e0>] (ext4_buffered_write_iter) from [<c03316d8>] (ext4_file_write_iter+0x10c/0x850) [10449.561053][ T398] [<c03316d8>] (ext4_file_write_iter) from [<c0298184>] (new_sync_write+0x74/0xb4) [10449.569493][ T398] [<c0298184>] (new_sync_write) from [<c0299afc>] (vfs_write+0x140/0x148) [10449.591082][ T398] [<c0299afc>] (vfs_write) from [<c0299c24>] (ksys_write+0x68/0xb4) [10449.598321][ T398] [<c0299c24>] (ksys_write) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [10449.621105][ T398] Exception stack(0xdb26dfa8 to 0xdb26dff0) [10449.626423][ T398] dfa0: 00000074 00000003 00000003 bec5e9e8 000fffff 00000000 [10449.651070][ T398] dfc0: 00000074 00000003 00000000 00000004 09efff61 00000000 09ffff60 00000000 [10449.659258][ T398] dfe0: 00000004 bec5e9b8 b6e9b5b3 b6e24746So with the root file system on an SSD there was a USB reset about every 7th minute with no further observed consequences for 2 hours, but still the story ended badly. The root file system survived, and was repaired at next boot:
rootfs: Clearing orphaned inode 1466382 (uid=0, gid=0, mode=0100600, size=167735296) rootfs: Clearing orphaned inode 4735157 (uid=0, gid=0, mode=0100644, size=1449724) rootfs: Clearing orphaned inode 4735325 (uid=0, gid=0, mode=0100644, size=297548) rootfs: Clearing orphaned inode 238174 (uid=0, gid=0, mode=0100755, size=564060) rootfs: Clearing orphaned inode 4735175 (uid=0, gid=0, mode=0100644, size=198100) rootfs: Clearing orphaned inode 238733 (uid=0, gid=0, mode=0100755, size=145336) rootfs: Clearing orphaned inode 4735131 (uid=0, gid=0, mode=0100644, size=9528) rootfs: Clearing orphaned inode 4735264 (uid=0, gid=0, mode=0100644, size=116836) rootfs: Clearing orphaned inode 4735255 (uid=0, gid=0, mode=0100644, size=149048) rootfs: Clearing orphaned inode 239700 (uid=0, gid=0, mode=0100644, size=1708448) rootfs: Clearing orphaned inode 4735326 (uid=0, gid=0, mode=0100644, size=420720) rootfs: clean, 27067/9773056 files, 1395797/39072256 blocks
The boot time with the root file sytem on SSD was roughly 128 seconds (with persistent mac address). Apparently, the box hardly benefits form the bandwidth of an SSD when it is behind a slow USB2 connector:
- U-boot startup: 2 s
- U-boot delay: 3 s
- Copy uImage and uInitrd to RAM: 47 s
- Kernel self un-compress: 4 s
- Kernel boot: 7 s (until power LED steady on)
- Debian initialization: 64 s
Quote
All computers wait at the same speed.
Observation summary:
- No USB resets in 20 minutes with the root file system on HDD.
- No USB resets in 20 minutes with the root file system on USB stick and the swap file on HDD.
- 17 USB resets in 2 hours with root file system on SSD, but the resets appeared to be handled well. Still, after another 30 minutes or so, things went bad for the kernel.
- Always a USB reset within 10 minutes with root file system on any of my USB sticks, both with USB2 and USB3 sticks, both with commercial and industrial grade.
- Possibly no USB resets with your 16 GB Scandisk Ultra USB2 stick, but maybe you were not patient enough?
- Is it (A) the kernel, (B) the driver circuit or (C) the device that initiates a USB reset?
- Are USB resets an everyday thing that both boxes and devices should be able to handle well, or are they exceptional and should be eliminated?
- Is the USB standardization document unclear, or will a thorough investigation show which of A, B and C are to blame?
- Are any of A, B and C already off the hook as the guilty one based on the tests?
- What do you hope to find out by tracing the USB driver signals?
Finally, I tested if the box would boot with the SSD mounted in one of the two disc compartments. It did not. U-boot never found the disc.
Regards,
Trond Melen
|
Re: Debian on Netgear RN102 September 07, 2020 04:54PM |
Admin Registered: 13 years ago Posts: 18,848 |
Wow! good job to all. I enjoyed reading the posts!
Let me answer this first before I go back to each post and add commentary to each section.
Look like my theory was right, the USB controller in this box is probably very old. Rember the stress test before used swap space on USB. So a lot of thrashing went on to the same disk. And controller could not keep up with it, it just timed out too long and the driver reset the device.
When we use the swap space on HDD, the data were written to the HDD and so it happened a lot faster, resulting with no timed out.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Let me answer this first before I go back to each post and add commentary to each section.
Look like my theory was right, the USB controller in this box is probably very old. Rember the stress test before used swap space on USB. So a lot of thrashing went on to the same disk. And controller could not keep up with it, it just timed out too long and the driver reset the device.
When we use the swap space on HDD, the data were written to the HDD and so it happened a lot faster, resulting with no timed out.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 07, 2020 05:11PM |
Admin Registered: 13 years ago Posts: 18,848 |
whitepawn,
> Before reading your post i have already soldered
> parts to PCB so its shame about bootloader and
> me.
You're too fast :) but now we can move on to the DTS update to verify if the HW mod works. Once it does, we can think about rebuilding stock u-boot with SPI enabled. This u-boot looks very familiar, it is probably identical to the Thecus N2350 and Zyxel NAS326 stock u-boot. Or at least it came from the same source tree. If you can find the GPL for this, I can rebuild it.
Atm, rolling new 2020 u-boot from mainline is too time consuming for me.
> Here is my dropbox folder of modification and some
> pictures of PCB for those playing along at home
>
> https://www.dropbox.com/sh/44vr77r4psy6gkg/AACnT025tiq-jTfBLsQU8A_Ma?dl=0
You could reduce the resolution for the pictures to make them less than 1M, and attach them to post(s) here. Very cool to see HW mods.
> Also please excuse of my heatsink zip-tie redneck
> engineering.
:))
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Before reading your post i have already soldered
> parts to PCB so its shame about bootloader and
> me.
You're too fast :) but now we can move on to the DTS update to verify if the HW mod works. Once it does, we can think about rebuilding stock u-boot with SPI enabled. This u-boot looks very familiar, it is probably identical to the Thecus N2350 and Zyxel NAS326 stock u-boot. Or at least it came from the same source tree. If you can find the GPL for this, I can rebuild it.
Quote
U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1
Atm, rolling new 2020 u-boot from mainline is too time consuming for me.
> Here is my dropbox folder of modification and some
> pictures of PCB for those playing along at home
>
> https://www.dropbox.com/sh/44vr77r4psy6gkg/AACnT025tiq-jTfBLsQU8A_Ma?dl=0
You could reduce the resolution for the pictures to make them less than 1M, and attach them to post(s) here. Very cool to see HW mods.
> Also please excuse of my heatsink zip-tie redneck
> engineering.
:))
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 07, 2020 06:11PM |
Admin Registered: 13 years ago Posts: 18,848 |
Trond,
> Monitoring swap memory usage with 'htop' in a
> separate window showed that swap usage never
> exceeded 6 MiB, i.e. 6 ppm of the available space.
> No errors were reported on the terminal nor on
> the serial console, which last line througout
> the test remained
Cool! Let me see if I can suggest another interesting test later.
> Installed
> the latest Debian root file system and Linux
> kernel following
> the
> brand new installation procedure. Success!
> You nailed it. Thank you very much for your
> effort!
Awesome!
> Magnifficent! This makes it even more mysterious
> to me that the box previously consistently shut
> down after 62 seconds, though. I see no important
> difference, but clearly there must be one.
The possible explanation for that error was a messed up DTB. Note that it stopped at mdio enumeration. So somehow the devices characteristics are wrong and it caused a crash. If we do a closer reading of the log later, it might show where the cause is. My suggestion for dpkg previously was a brute force fix (so you will refresh the kernel files), but it did not explain the whole story.
>
> My only comment to the brand new procedure is that
> the instructions in "Note1:" are easily overlooked
> when jumping from Linux kernel installation
> instructions to Debian file system instructions
> and back again.
Right. I was going to revise the rootfs installation a little bit to make it more robust.
> I just realized that since 'apt update' regularly
> fails with "not valid yet", my habit of doing 'apt
> update && apt upgrade -y' is a bad one
Yes, I think it is better to run 2 commands.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Monitoring swap memory usage with 'htop' in a
> separate window showed that swap usage never
> exceeded 6 MiB, i.e. 6 ppm of the available space.
> No errors were reported on the terminal nor on
> the serial console, which last line througout
> the test remained
Cool! Let me see if I can suggest another interesting test later.
> Installed
> the latest Debian root file system and Linux
> kernel following
> the
> brand new installation procedure. Success!
> You nailed it. Thank you very much for your
> effort!
Awesome!
> Magnifficent! This makes it even more mysterious
> to me that the box previously consistently shut
> down after 62 seconds, though. I see no important
> difference, but clearly there must be one.
The possible explanation for that error was a messed up DTB. Note that it stopped at mdio enumeration. So somehow the devices characteristics are wrong and it caused a crash. If we do a closer reading of the log later, it might show where the cause is. My suggestion for dpkg previously was a brute force fix (so you will refresh the kernel files), but it did not explain the whole story.
>
> My only comment to the brand new procedure is that
> the instructions in "Note1:" are easily overlooked
> when jumping from Linux kernel installation
> instructions to Debian file system instructions
> and back again.
Right. I was going to revise the rootfs installation a little bit to make it more robust.
> I just realized that since 'apt update' regularly
> fails with "not valid yet", my habit of doing 'apt
> update && apt upgrade -y' is a bad one
Yes, I think it is better to run 2 commands.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 07, 2020 06:15PM |
Admin Registered: 13 years ago Posts: 18,848 |
Trond,
> Finally, I tested if the box would boot with the
> SSD mounted in one of the two disc compartments.
> It did not. U-boot never found the disc.
This happens a lot with old u-boot. They don't recognize some new SSDs in the SATA slot.
However, to verify that, you would insert an HDD or SSD into one of the 2 slots and in u-boot console, try to initialize it manually.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Finally, I tested if the box would boot with the
> SSD mounted in one of the two disc compartments.
> It did not. U-boot never found the disc.
This happens a lot with old u-boot. They don't recognize some new SSDs in the SATA slot.
However, to verify that, you would insert an HDD or SSD into one of the 2 slots and in u-boot console, try to initialize it manually.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 08, 2020 11:03AM |
Registered: 5 years ago Posts: 73 |
Hi all,
Trond thank you very much for your tests it is very useful for me.
I will try to boot from USB2.0 device with swap on HDD.
About SDIO GPIO pins i have found only GPIO 47 which is SD0_CLK but unable to find remaining 5 pins.Maybe Netgear didn't expose pins, the way i may understand this to x-ray this pcb.
Any suggestions anyone?
Regards.
Trond thank you very much for your tests it is very useful for me.
I will try to boot from USB2.0 device with swap on HDD.
About SDIO GPIO pins i have found only GPIO 47 which is SD0_CLK but unable to find remaining 5 pins.Maybe Netgear didn't expose pins, the way i may understand this to x-ray this pcb.
Any suggestions anyone?
Regards.
|
Re: Debian on Netgear RN102 September 08, 2020 11:21AM |
Registered: 5 years ago Posts: 256 |
They may be using those GPIOs for something else, I've noticed that with some buffalo devices. For some reason a lot of their boards have traces for a card reader but the actual SDIO pins are used for other things.
you could always set up a script to to toggle GPIO pins and a known rate and then monitor points on the board you are interested in with a logic analyzer or oscilloscope.
you could always set up a script to to toggle GPIO pins and a known rate and then monitor points on the board you are interested in with a logic analyzer or oscilloscope.
|
Re: Debian on Netgear RN102 September 08, 2020 05:51PM |
Registered: 5 years ago Posts: 73 |
Hi 1000001101000,
Thank you for your reply, nice information.I have just found GPIO 48 by the way and updated dropbox folder with my findings.
You may be right for unknown pins (49 50 51 52) as now but not for found ones:
-GPIO 63 64 65 and 48 are not pulled ground or vcc, they are not wired to anything.
-GPIO 32 47 are pulled to vcc via 4.7kohm resistor.They are not wired to anything except resistors.
Since i don't have oscilloscope or logic analyzer i have just used script "blink" with a poor mans multimeter:)
I am not sure but, I should get errors or weird behavior in software if unknown pins are used for something else right?Are there any methods to know this type of case?
Regards.
Thank you for your reply, nice information.I have just found GPIO 48 by the way and updated dropbox folder with my findings.
You may be right for unknown pins (49 50 51 52) as now but not for found ones:
-GPIO 63 64 65 and 48 are not pulled ground or vcc, they are not wired to anything.
-GPIO 32 47 are pulled to vcc via 4.7kohm resistor.They are not wired to anything except resistors.
Since i don't have oscilloscope or logic analyzer i have just used script "blink" with a poor mans multimeter:)
#!/bin/sh
GPIOBASE=`cat /sys/class/gpio/gpiochip*/base | head -n1`
GPIOmin=`expr $1 + $GPIOBASE`
GPIOmax=`expr $2 + $GPIOBASE`
nums=`seq $GPIOmin $GPIOmax`
cd /sys/class/gpio
for i in $nums; do
echo $i > export; echo out >gpio$i/direction
done
while true; do
for i in $nums; do
echo 0 > gpio$i/value
done
sleep 1
for i in $nums; do
echo 1 > gpio$i/value
done
sleep 1
done
I am not sure but, I should get errors or weird behavior in software if unknown pins are used for something else right?Are there any methods to know this type of case?
Regards.
|
Re: Debian on Netgear RN102 September 08, 2020 09:58PM |
Admin Registered: 13 years ago Posts: 18,848 |
whitepawn,
> I am not sure but, I should get errors or weird
> behavior in software if unknown pins are used for
> something else right?Are there any methods to know
> this type of case?
With the script and echo statements like that, it will give you an error when you try to export the assigned GPIO. If the GPIO was not defined in the DTS, then it's OK to export it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I am not sure but, I should get errors or weird
> behavior in software if unknown pins are used for
> something else right?Are there any methods to know
> this type of case?
With the script and echo statements like that, it will give you an error when you try to export the assigned GPIO. If the GPIO was not defined in the DTS, then it's OK to export it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Netgear RN102 September 09, 2020 10:32AM |
Registered: 5 years ago Posts: 256 |
It depends somewhat on how the various devices are defined, If the GPIOs are reserved via the DTB it won't let you export them. Some devices (I'm thinking specifically of NAND but I've seen it with others in the past) can be referenced by address without reserving the GPIO pins. In those cases it can be possible to trigger crashes or undesired behavior by messing with GPIO pins needed by those devices.
You can usually avoid this by only testing a few pins at a time and by looking at the pincrtl documentation for your SoC to get a sense of what pins to avoid.
You also want to make sure you're not reserving any pins for hardware that isn't actually in use. I remember for one device I couldn't find of the drive detect GPIOs until i realized it was actually one of the default i2c pins, I needed to remove the unused i2c bus from my DTB.
....This all reminds me, I have got some open questions about a kirkwood device where the default spi/uart and nand pins all seem to overlap in ways I haven't been able to untangle. When I get back around to that device I may need to pick Bohdi's brain about how to deal with that.
You can usually avoid this by only testing a few pins at a time and by looking at the pincrtl documentation for your SoC to get a sense of what pins to avoid.
You also want to make sure you're not reserving any pins for hardware that isn't actually in use. I remember for one device I couldn't find of the drive detect GPIOs until i realized it was actually one of the default i2c pins, I needed to remove the unused i2c bus from my DTB.
....This all reminds me, I have got some open questions about a kirkwood device where the default spi/uart and nand pins all seem to overlap in ways I haven't been able to untangle. When I get back around to that device I may need to pick Bohdi's brain about how to deal with that.
|
Re: Debian on Netgear RN102 September 09, 2020 04:31PM |
Admin Registered: 13 years ago Posts: 18,848 |
> ....This all reminds me, I have got some open
> questions about a kirkwood device where the
> default spi/uart and nand pins all seem to overlap
> in ways I haven't been able to untangle. When I
> get back around to that device I may need to pick
> Bohdi's brain about how to deal with that.
Kirkwood is a little bit easier because there are a lot of documentation. And the modern u-boot code, i.e 2017, made the pins assigment more readable than old Marvell source. When I built a new Kirkwood u-boot, the Marvell GPL source readability was a real problem.
If we are lucky, the vendor documented the pins assignment in their patch. OTOH, if they follow the same convention in the original source, then it is very annoying to read.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 09/09/2020 04:39PM by bodhi.
> questions about a kirkwood device where the
> default spi/uart and nand pins all seem to overlap
> in ways I haven't been able to untangle. When I
> get back around to that device I may need to pick
> Bohdi's brain about how to deal with that.
Kirkwood is a little bit easier because there are a lot of documentation. And the modern u-boot code, i.e 2017, made the pins assigment more readable than old Marvell source. When I built a new Kirkwood u-boot, the Marvell GPL source readability was a real problem.
If we are lucky, the vendor documented the pins assignment in their patch. OTOH, if they follow the same convention in the original source, then it is very annoying to read.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 09/09/2020 04:39PM by bodhi.
