Helios64 - freeze whatever the kernel is.

SR-G · November 29, 2020

As stated in my comments here (but it seems no one is reading this blog post comments anymore ...) : https://blog.kobol.io/2020/10/27/helios64-software-issue/

- With 5.8.17 i have kernel panics.

- With 5.8.14 i have freeze.

So what to do in order to have a stable situation ?!

Quote

I installed armbian 20.08.21 with kernel 5.8.17 (and neither 5.8.14 nor 5.8.16 ), and i've just encountered the whole system being frozen (during a MDADM RAID5 array creation / after ~20h of rebuild ...), hence the need to power-down the NAS (first led was blinking red).

Linux helios64 5.8.17-rockchip64 #20.08.21 SMP PREEMPT Sat Oct 31 08:22:59 CET 2020 aarch64 GNU/Linux

I don't have any logs (as by default journalctl is persisted in ram) so i have no clue about what has happened (nothing in kern.log), but could this be linked to the issue described in this post ?
Or was this identified kernel crash only happening on 5.8.16 and is now corrected with 5.8.17 ?
So should i stay on 5.8.17, or is it adviced to revert to 5.8.14 ?

Quote

And today i just got (but without immediate freeze and without blinkind red light / but i still had to reboot after a few minutes due to weird behaviors, and even if ssh sessions were still online) (still with 5.8.17)

[Sat Nov 28 01:08:46 2020] Unable to handle kernel paging request at virtual address bfff800010c4132c
[Sat Nov 28 01:08:46 2020] Mem abort info:
[Sat Nov 28 01:08:46 2020] ESR = 0x86000004
[Sat Nov 28 01:08:46 2020] EC = 0x21: IABT (current EL), IL = 32 bits
[Sat Nov 28 01:08:46 2020] SET = 0, FnV = 0
[Sat Nov 28 01:08:46 2020] EA = 0, S1PTW = 0
[Sat Nov 28 01:08:46 2020] [bfff800010c4132c] address between user and kernel address ranges
[Sat Nov 28 01:08:46 2020] Internal error: Oops: 86000004 [#1] PREEMPT SMP
[Sat Nov 28 01:08:46 2020] Modules linked in: rfkill governor_performance snd_soc_hdmi_codec r8152 snd_soc_rockchip_i2s hantro_vpu(C) rockchip_rga rockchip_vdec(C) snd_soc_core rockchipdrm v4l2_h264 snd_pcm_dmaengine videobuf2_vmalloc videobuf2_dma_sg videobuf2_dma_contig snd_pcm dw_mipi_dsi v4l2_mem2mem dw_hdmi videobuf2_memops snd_timer analogix_dp videobuf2_v4l2 snd zstd panfrost videobuf2_common fusb302 pwm_fan leds_pwm drm_kms_helper soundcore gpio_charger tcpm videodev gpu_sched cec typec mc rc_core sg drm drm_panel_orientation_quirks cpufreq_dt gpio_beeper zram lm75 ip_tables x_tables autofs4 raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx md_mod realtek dwmac_rk stmmac_platform stmmac mdio_xpcs adc_keys
[Sat Nov 28 01:08:46 2020] CPU: 4 PID: 7457 Comm: sshd Tainted: G C 5.9.10-rockchip64 #20.11
[Sat Nov 28 01:08:46 2020] Hardware name: Helios64 (DT)
[Sat Nov 28 01:08:46 2020] pstate: 00000005 (nzcv daif -PAN -UAO BTYPE=--)
[Sat Nov 28 01:08:46 2020] pc : 0xbfff800010c4132c
[Sat Nov 28 01:08:46 2020] lr : simple_copy_to_iter+0x34/0x68
[Sat Nov 28 01:08:46 2020] sp : ffff8000132eba30
[Sat Nov 28 01:08:46 2020] x29: ffff8000132eba30 x28: 0000000000000000
[Sat Nov 28 01:08:46 2020] x27: ffff000043d97d00 x26: 00000000000005a8
[Sat Nov 28 01:08:46 2020] x25: 0000000000001228 x24: 00000000000005a8
[Sat Nov 28 01:08:46 2020] x23: ffff8000132ebcc8 x22: 0000000000000001
[Sat Nov 28 01:08:46 2020] x21: ffff8000132ebcc8 x20: ffff0000a0aa0882
[Sat Nov 28 01:08:46 2020] x19: 00000000000005a8 x18: 0000000000000000
[Sat Nov 28 01:08:46 2020] x17: 0000000000000000 x16: 0000000000000000
[Sat Nov 28 01:08:46 2020] x15: 0000000000000000 x14: 34d9ba8f70dd5728
[Sat Nov 28 01:08:46 2020] x13: abbcee5b1190622f x12: a4a3849f1551ce47
[Sat Nov 28 01:08:46 2020] x11: 9ce64aa033a6ddcb x10: 0000000000000882
[Sat Nov 28 01:08:46 2020] x9 : 908fce41edbdd9d6 x8 : 00000000f7e00000
[Sat Nov 28 01:08:46 2020] x7 : 0000000000000018 x6 : ffff800011a84510
[Sat Nov 28 01:08:46 2020] x5 : ffff800011a84510 x4 : 0000000000000000
[Sat Nov 28 01:08:46 2020] x3 : ffff800010010000 x2 : ffff80000de00000
[Sat Nov 28 01:08:46 2020] x1 : ffff000002210000 x0 : ffff000003040000
[Sat Nov 28 01:08:46 2020] Call trace:
[Sat Nov 28 01:08:46 2020] 0xbfff800010c4132c
[Sat Nov 28 01:08:46 2020] __skb_datagram_iter+0x144/0x240
[Sat Nov 28 01:08:46 2020] skb_copy_datagram_iter+0x50/0x110
[Sat Nov 28 01:08:46 2020] tcp_recvmsg+0x590/0x950
[Sat Nov 28 01:08:46 2020] inet_recvmsg+0x50/0x120
[Sat Nov 28 01:08:46 2020] sock_recvmsg+0x4c/0x60
[Sat Nov 28 01:08:46 2020] sock_read_iter+0x88/0xe0
[Sat Nov 28 01:08:46 2020] new_sync_read+0x16c/0x180
[Sat Nov 28 01:08:46 2020] vfs_read+0x148/0x1d8
[Sat Nov 28 01:08:46 2020] ksys_read+0xe0/0xf8
[Sat Nov 28 01:08:46 2020] __arm64_sys_read+0x1c/0x28
[Sat Nov 28 01:08:46 2020] el0_svc_common.constprop.0+0x70/0x188
[Sat Nov 28 01:08:46 2020] do_el0_svc+0x24/0x90
[Sat Nov 28 01:08:46 2020] el0_sync_handler+0x90/0x198
[Sat Nov 28 01:08:46 2020] el0_sync+0x158/0x180
[Sat Nov 28 01:08:46 2020] Code: bad PC value
[Sat Nov 28 01:08:46 2020] ---[ end trace 82cecfd63ab60ea2 ]---

Quote

So i switched back to 5.8.14 ... and i also have a lot of issues and kernel panic !!!

> Linux helios64 5.8.14-rockchip64 #20.08.10 SMP PREEMPT Tue Oct 13 16:58:01 CEST 2020 aarch64 GNU/Linux

From today (board frozen + red light blinking + had to reboot :

Message from syslogd@localhost at Nov 29 14:48:57 ...
kernel:[16987.580304] Internal error: Oops: 96000044 [#1] PREEMPT SMP

Message from syslogd@localhost at Nov 29 14:48:57 ...
kernel:[16987.601169] Code: aa0103e0 f9400422 f85f8403 f9000462 (f9000043)

Message from syslogd@localhost at Nov 29 14:48:58 ...
kernel:[16987.780586] Internal error: Oops: 96000004 [#2] PREEMPT SMP

Message from syslogd@localhost at Nov 29 14:48:58 ...
kernel:[16987.801529] Code: f2fbd5a7 d0008408 f9400f01 aa0103e0 (f9400422)

Message from syslogd@localhost at Nov 29 14:48:58 ...
kernel:[16987.807055] Internal error: Oops: 96000004 [#3] PREEMPT SMP

Message from syslogd@localhost at Nov 29 14:48:58 ...
kernel:[16987.833634] Code: f2fbd5a7 d0008408 f9400f01 aa0103e0 (f9400422)

So what to do to have a stable situation ?
Is it only possible ?
With which kernel ?

It seems to be "under load" (one freeze during RAID array being built, and several ones (with .14 or .17 kernels) while files were being copied through the 1Gb/s network interface).

- System newly installed and running on fresh SSD card.

- 5*3.5" WD HDD plugged in / RAID5 mdadm array (so no M.2, ...)

- nothing else done on the NAS (nothing has been installed on the OS, no processes in memory outside raid + rsync or scp file copying through SSH)

aprayoga · February 1, 2021

Hi @Seneca, @SR-G

Could you add following lines to the beginning of /boot/boot.cmd

regulator dev vdd_log
regulator value 930000
regulator dev vdd_center
regulator value 950000

run

mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

and reboot. Verify whether it can improve stability.

Spoiler

modified boot.cmd



# DO NOT EDIT THIS FILE
#
# Please edit /boot/armbianEnv.txt to set supported parameters
#
regulator dev vdd_log
regulator value 930000
regulator dev vdd_center
regulator value 950000

setenv load_addr "0x9000000"
setenv overlay_error "false"
# default values
setenv rootdev "/dev/mmcblk0p1"
setenv verbosity "1"
setenv console "both"
setenv bootlogo "false"
setenv rootfstype "ext4"
setenv docker_optimizations "on"
setenv earlycon "off"

echo "Boot script loaded from ${devtype} ${devnum}"

if test -e ${devtype} ${devnum} ${prefix}armbianEnv.txt; then
        load ${devtype} ${devnum} ${load_addr} ${prefix}armbianEnv.txt
        env import -t ${load_addr} ${filesize}
fi

if test "${logo}" = "disabled"; then setenv logo "logo.nologo"; fi

if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=tty1"; fi
if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "console=ttyS2,1500000 ${consoleargs}"; fi
if test "${earlycon}" = "on"; then setenv consoleargs "earlycon ${consoleargs}"; fi
if test "${bootlogo}" = "true"; then setenv consoleargs "bootsplash.bootfile=bootsplash.armbian ${consoleargs}"; fi

# get PARTUUID of first partition on SD/eMMC the boot script was loaded from
if test "${devtype}" = "mmc"; then part uuid mmc ${devnum}:1 partuuid; fi

setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}"

if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1"; fi

load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd
load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image

load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile}
fdt addr ${fdt_addr_r}
fdt resize 65536
for overlay_file in ${overlays}; do
        if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/rockchip/overlay/${overlay_prefix}-${overlay_file}.dtbo; then
                echo "Applying kernel provided DT overlay ${overlay_prefix}-${overlay_file}.dtbo"
                fdt apply ${load_addr} || setenv overlay_error "true"
        fi
done
for overlay_file in ${user_overlays}; do
        if load ${devtype} ${devnum} ${load_addr} ${prefix}overlay-user/${overlay_file}.dtbo; then
                echo "Applying user provided DT overlay ${overlay_file}.dtbo"
                fdt apply ${load_addr} || setenv overlay_error "true"
        fi
done
if test "${overlay_error}" = "true"; then
        echo "Error applying DT overlays, restoring original DT"
        load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile}
else
        if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/rockchip/overlay/${overlay_prefix}-fixup.scr; then
                echo "Applying kernel provided DT fixup script (${overlay_prefix}-fixup.scr)"
                source ${load_addr}
        fi
        if test -e ${devtype} ${devnum} ${prefix}fixup.scr; then
                load ${devtype} ${devnum} ${load_addr} ${prefix}fixup.scr
                echo "Applying user provided fixup script (fixup.scr)"
                source ${load_addr}
        fi
fi
booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

# Recompile with:
# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

You could also use the attached boot.scr

boot.scr

SR-G · February 1, 2021

Ok i just applyed the suggested modifications this morning (by modifying the boot.cmd file + regenerating the boot.scr file).

Reboot has been OK.

Let's see ...

+ what exactly are these values / are they related to the CPU speed and if yes, how are they different than what is applyed when modifying the CPU governance configuration through armbian-config ?

Previous armbianEnv.txt (for reference) (untouched) :

```

verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
```

Previous boot.cmd file, for reference (modified as requested with the 4 new lines) :

```

# DO NOT EDIT THIS FILE
#
# Please edit /boot/armbianEnv.txt to set supported parameters
#

setenv load_addr "0x9000000"
setenv overlay_error "false"
# default values
setenv rootdev "/dev/mmcblk0p1"
setenv verbosity "1"
setenv console "both"
setenv bootlogo "false"
setenv rootfstype "ext4"
setenv docker_optimizations "on"
setenv earlycon "off"

echo "Boot script loaded from ${devtype} ${devnum}"

if test -e ${devtype} ${devnum} ${prefix}armbianEnv.txt; then
load ${devtype} ${devnum} ${load_addr} ${prefix}armbianEnv.txt
env import -t ${load_addr} ${filesize}
fi

if test "${logo}" = "disabled"; then setenv logo "logo.nologo"; fi

if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=tty1"; fi
if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "console=ttyS2,1500000 ${consoleargs}"; fi
if test "${earlycon}" = "on"; then setenv consoleargs "earlycon ${consoleargs}"; fi
if test "${bootlogo}" = "true"; then setenv consoleargs "bootsplash.bootfile=bootsplash.armbian ${consoleargs}"; fi

# get PARTUUID of first partition on SD/eMMC the boot script was loaded from
if test "${devtype}" = "mmc"; then part uuid mmc ${devnum}:1 partuuid; fi

setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}"

if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1"; fi

load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd
load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image

load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile}
fdt addr ${fdt_addr_r}
fdt resize 65536
for overlay_file in ${overlays}; do
   if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/rockchip/overlay/${overlay_prefix}-${overlay_file}.dtbo; then
       echo "Applying kernel provided DT overlay ${overlay_prefix}-${overlay_file}.dtbo"
       fdt apply ${load_addr} || setenv overlay_error "true"
   fi
done
for overlay_file in ${user_overlays}; do
   if load ${devtype} ${devnum} ${load_addr} ${prefix}overlay-user/${overlay_file}.dtbo; then
       echo "Applying user provided DT overlay ${overlay_file}.dtbo"
       fdt apply ${load_addr} || setenv overlay_error "true"
   fi
done
if test "${overlay_error}" = "true"; then
   echo "Error applying DT overlays, restoring original DT"
   load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile}
else
   if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/rockchip/overlay/${overlay_prefix}-fixup.scr; then
       echo "Applying kernel provided DT fixup script (${overlay_prefix}-fixup.scr)"
       source ${load_addr}
   fi
   if test -e ${devtype} ${devnum} ${prefix}fixup.scr; then
       load ${devtype} ${devnum} ${load_addr} ${prefix}fixup.scr
       echo "Applying user provided fixup script (fixup.scr)"
       source ${load_addr}
   fi
fi
booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

# Recompile with:
# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
```

```

(...)

lrwxrwxrwx 1 root root 25 2021-01-10 14:30 uInitrd -> uInitrd-5.9.14-rockchip64
-rw-r--r-- 1 root root 3,2K 2021-02-01 09:13 boot.cmd
-rw-rw-r-- 1 root root 3,3K 2021-02-01 09:13 boot.scr
-rw-r--r-- 1 root root 166 2021-02-01 09:15 armbianEnv.txt
```

aprayoga · February 2, 2021

18 hours ago, SR-G said:

+ what exactly are these values / are they related to the CPU speed and if yes, how are they different than what is applyed when modifying the CPU governance configuration through armbian-config ?

It affect various subsystem. CPU governance work in higher level, algorithm, when to apply certain CPU speed from predefined table.

SR-G · February 3, 2021

So i applyed these parameters on 2021/02/01 and today (2 days later) i just got another freeze (this time i had IO but not a lot - was uploading files from NAS to cloud at 40MB/s - but it's of course not the first time i have some IO during hours, it's just that until now most freezes have happened without IO).

No RED LED blinking this time once freezed + all HDD leds are ON but are not blinking.

I had an opened SSH connection and nothing has been printed there, it's just frozen (ping from another host not answered, and so on).

Spoiler

Quote

[mer. févr. 3 17:45:32 2021] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[mer. févr. 3 17:45:32 2021] Linux version 5.9.14-rockchip64 (root@desktop) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020
[mer. févr. 3 17:45:32 2021] Machine model: Helios64
[mer. févr. 3 17:45:32 2021] efi: UEFI not found.
[mer. févr. 3 17:45:32 2021] cma: Reserved 128 MiB at 0x00000000ec800000
[mer. févr. 3 17:45:32 2021] NUMA: No NUMA configuration found
[mer. févr. 3 17:45:32 2021] NUMA: Faking a node at [mem 0x0000000000200000-0x00000000f7ffffff]
[mer. févr. 3 17:45:32 2021] NUMA: NODE_DATA [mem 0xf77d9100-0xf77dafff]
[mer. févr. 3 17:45:32 2021] Zone ranges:
[mer. févr. 3 17:45:32 2021] DMA [mem 0x0000000000200000-0x000000003fffffff]
[mer. févr. 3 17:45:32 2021] DMA32 [mem 0x0000000040000000-0x00000000f7ffffff]
[mer. févr. 3 17:45:32 2021] Normal empty
[mer. févr. 3 17:45:32 2021] Movable zone start for each node
[mer. févr. 3 17:45:32 2021] Early memory node ranges
[mer. févr. 3 17:45:32 2021] node 0: [mem 0x0000000000200000-0x00000000f7ffffff]
[mer. févr. 3 17:45:32 2021] Initmem setup node 0 [mem 0x0000000000200000-0x00000000f7ffffff]
[mer. févr. 3 17:45:32 2021] On node 0 totalpages: 1015296
[mer. févr. 3 17:45:32 2021] DMA zone: 4088 pages used for memmap
[mer. févr. 3 17:45:32 2021] DMA zone: 0 pages reserved
[mer. févr. 3 17:45:32 2021] DMA zone: 261632 pages, LIFO batch:63
[mer. févr. 3 17:45:32 2021] DMA32 zone: 11776 pages used for memmap
[mer. févr. 3 17:45:32 2021] DMA32 zone: 753664 pages, LIFO batch:63
[mer. févr. 3 17:45:32 2021] psci: probing for conduit method from DT.
[mer. févr. 3 17:45:32 2021] psci: PSCIv1.0 detected in firmware.
[mer. févr. 3 17:45:32 2021] psci: Using standard PSCI v0.2 function IDs
[mer. févr. 3 17:45:32 2021] psci: MIGRATE_INFO_TYPE not supported.
[mer. févr. 3 17:45:32 2021] psci: SMC Calling Convention v1.0
[mer. févr. 3 17:45:32 2021] percpu: Embedded 32 pages/cpu s93784 r8192 d29096 u131072
[mer. févr. 3 17:45:32 2021] pcpu-alloc: s93784 r8192 d29096 u131072 alloc=32*4096
[mer. févr. 3 17:45:32 2021] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5
[mer. févr. 3 17:45:32 2021] Detected VIPT I-cache on CPU0
[mer. févr. 3 17:45:32 2021] CPU features: detected: ARM erratum 845719
[mer. févr. 3 17:45:32 2021] CPU features: detected: GIC system register CPU interface
[mer. févr. 3 17:45:32 2021] Built 1 zonelists, mobility grouping on. Total pages: 999432
[mer. févr. 3 17:45:32 2021] Policy zone: DMA32
[mer. févr. 3 17:45:32 2021] Kernel command line: root=UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=21825e31-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[mer. févr. 3 17:45:32 2021] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[mer. févr. 3 17:45:32 2021] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[mer. févr. 3 17:45:32 2021] mem auto-init: stack:off, heap alloc:on, heap free:off
[mer. févr. 3 17:45:32 2021] software IO TLB: mapped [mem 0x3bfff000-0x3ffff000] (64MB)
[mer. févr. 3 17:45:32 2021] Memory: 3736004K/4061184K available (14464K kernel code, 2094K rwdata, 5980K rodata, 4224K init, 573K bss, 194108K reserved, 131072K cma-reserved)
[mer. févr. 3 17:45:32 2021] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
[mer. févr. 3 17:45:32 2021] rcu: Preemptible hierarchical RCU implementation.
[mer. févr. 3 17:45:32 2021] rcu:    RCU event tracing is enabled.
[mer. févr. 3 17:45:32 2021] rcu:    RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=6.
[mer. févr. 3 17:45:32 2021]    Trampoline variant of Tasks RCU enabled.
[mer. févr. 3 17:45:32 2021]    Rude variant of Tasks RCU enabled.
[mer. févr. 3 17:45:32 2021]    Tracing variant of Tasks RCU enabled.
[mer. févr. 3 17:45:32 2021] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[mer. févr. 3 17:45:32 2021] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6
[mer. févr. 3 17:45:32 2021] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[mer. févr. 3 17:45:32 2021] GICv3: GIC: Using split EOI/Deactivate mode
[mer. févr. 3 17:45:32 2021] GICv3: 256 SPIs implemented
[mer. févr. 3 17:45:32 2021] GICv3: 0 Extended SPIs implemented
[mer. févr. 3 17:45:32 2021] GICv3: Distributor has no Range Selector support
[mer. févr. 3 17:45:32 2021] GICv3: 16 PPIs implemented
[mer. févr. 3 17:45:32 2021] GICv3: CPU0: found redistributor 0 region 0:0x00000000fef00000
[mer. févr. 3 17:45:32 2021] ITS [mem 0xfee20000-0xfee3ffff]
[mer. févr. 3 17:45:32 2021] ITS@0x00000000fee20000: allocated 65536 Devices @f6d00000 (flat, esz 8, psz 64K, shr 0)
[mer. févr. 3 17:45:32 2021] ITS: using cache flushing for cmd queue
[mer. févr. 3 17:45:32 2021] GICv3: using LPI property table @0x00000000f6cb0000
[mer. févr. 3 17:45:32 2021] GIC: using cache flushing for LPI property table
[mer. févr. 3 17:45:32 2021] GICv3: CPU0: using allocated LPI pending table @0x00000000f6cc0000
[mer. févr. 3 17:45:32 2021] GICv3: GIC: PPI partition interrupt-partition-0[0] { /cpus/cpu@0[0] /cpus/cpu@1[1] /cpus/cpu@2[2] /cpus/cpu@3[3] }
[mer. févr. 3 17:45:32 2021] GICv3: GIC: PPI partition interrupt-partition-1[1] { /cpus/cpu@100[4] /cpus/cpu@101[5] }
[mer. févr. 3 17:45:32 2021] random: get_random_bytes called from start_kernel+0x698/0x850 with crng_init=0
[mer. févr. 3 17:45:32 2021] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[mer. févr. 3 17:45:32 2021] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[mer. févr. 3 17:45:32 2021] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[mer. févr. 3 17:45:32 2021] Console: colour dummy device 80x25
[mer. févr. 3 17:45:32 2021] printk: console [tty1] enabled
[mer. févr. 3 17:45:32 2021] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[mer. févr. 3 17:45:32 2021] pid_max: default: 32768 minimum: 301
[mer. févr. 3 17:45:32 2021] LSM: Security Framework initializing
[mer. févr. 3 17:45:32 2021] Yama: becoming mindful.
[mer. févr. 3 17:45:32 2021] AppArmor: AppArmor initialized
[mer. févr. 3 17:45:32 2021] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[mer. févr. 3 17:45:32 2021] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[mer. févr. 3 17:45:32 2021] rcu: Hierarchical SRCU implementation.
[mer. févr. 3 17:45:32 2021] Platform MSI: interrupt-controller@fee20000 domain created
[mer. févr. 3 17:45:32 2021] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created
[mer. févr. 3 17:45:32 2021] EFI services will not be available.
[mer. févr. 3 17:45:32 2021] smp: Bringing up secondary CPUs ...
[mer. févr. 3 17:45:32 2021] Detected VIPT I-cache on CPU1
[mer. févr. 3 17:45:32 2021] GICv3: CPU1: found redistributor 1 region 0:0x00000000fef20000
[mer. févr. 3 17:45:32 2021] GICv3: CPU1: using allocated LPI pending table @0x00000000f6cd0000
[mer. févr. 3 17:45:32 2021] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[mer. févr. 3 17:45:32 2021] Detected VIPT I-cache on CPU2
[mer. févr. 3 17:45:32 2021] GICv3: CPU2: found redistributor 2 region 0:0x00000000fef40000
[mer. févr. 3 17:45:32 2021] GICv3: CPU2: using allocated LPI pending table @0x00000000f6ce0000
[mer. févr. 3 17:45:32 2021] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[mer. févr. 3 17:45:32 2021] Detected VIPT I-cache on CPU3
[mer. févr. 3 17:45:32 2021] GICv3: CPU3: found redistributor 3 region 0:0x00000000fef60000
[mer. févr. 3 17:45:32 2021] GICv3: CPU3: using allocated LPI pending table @0x00000000f6cf0000
[mer. févr. 3 17:45:32 2021] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[mer. févr. 3 17:45:32 2021] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
[mer. févr. 3 17:45:32 2021] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[mer. févr. 3 17:45:32 2021] Detected PIPT I-cache on CPU4
[mer. févr. 3 17:45:32 2021] GICv3: CPU4: found redistributor 100 region 0:0x00000000fef80000
[mer. févr. 3 17:45:32 2021] GICv3: CPU4: using allocated LPI pending table @0x00000000f6d80000
[mer. févr. 3 17:45:32 2021] CPU4: Booted secondary processor 0x0000000100 [0x410fd082]
[mer. févr. 3 17:45:32 2021] Detected PIPT I-cache on CPU5
[mer. févr. 3 17:45:32 2021] GICv3: CPU5: found redistributor 101 region 0:0x00000000fefa0000
[mer. févr. 3 17:45:32 2021] GICv3: CPU5: using allocated LPI pending table @0x00000000f6d90000
[mer. févr. 3 17:45:32 2021] CPU5: Booted secondary processor 0x0000000101 [0x410fd082]
[mer. févr. 3 17:45:32 2021] smp: Brought up 1 node, 6 CPUs
[mer. févr. 3 17:45:32 2021] SMP: Total of 6 processors activated.
[mer. févr. 3 17:45:32 2021] CPU features: detected: 32-bit EL0 Support
[mer. févr. 3 17:45:32 2021] CPU features: detected: CRC32 instructions
[mer. févr. 3 17:45:32 2021] CPU features: detected: 32-bit EL1 Support
[mer. févr. 3 17:45:32 2021] CPU: All CPU(s) started at EL2
[mer. févr. 3 17:45:32 2021] alternatives: patching kernel code
[mer. févr. 3 17:45:32 2021] devtmpfs: initialized
[mer. févr. 3 17:45:32 2021] Registered cp15_barrier emulation handler
[mer. févr. 3 17:45:32 2021] Registered setend emulation handler
[mer. févr. 3 17:45:32 2021] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[mer. févr. 3 17:45:32 2021] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[mer. févr. 3 17:45:32 2021] xor: measuring software checksum speed
[mer. févr. 3 17:45:32 2021] 8regs : 2345.000 MB/sec
[mer. févr. 3 17:45:32 2021] 32regs : 2757.000 MB/sec
[mer. févr. 3 17:45:32 2021] arm64_neon: 2279.000 MB/sec
[mer. févr. 3 17:45:32 2021] xor: using function: 32regs (2757.000 MB/sec)
[mer. févr. 3 17:45:32 2021] pinctrl core: initialized pinctrl subsystem
[mer. févr. 3 17:45:32 2021] DMI not present or invalid.
[mer. févr. 3 17:45:32 2021] NET: Registered protocol family 16
[mer. févr. 3 17:45:32 2021] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations
[mer. févr. 3 17:45:32 2021] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[mer. févr. 3 17:45:32 2021] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[mer. févr. 3 17:45:32 2021] audit: initializing netlink subsys (disabled)
[mer. févr. 3 17:45:32 2021] audit: type=2000 audit(0.192:1): state=initialized audit_enabled=0 res=1
[mer. févr. 3 17:45:32 2021] thermal_sys: Registered thermal governor 'fair_share'
[mer. févr. 3 17:45:32 2021] thermal_sys: Registered thermal governor 'bang_bang'
[mer. févr. 3 17:45:32 2021] thermal_sys: Registered thermal governor 'step_wise'
[mer. févr. 3 17:45:32 2021] thermal_sys: Registered thermal governor 'user_space'
[mer. févr. 3 17:45:32 2021] cpuidle: using governor menu
[mer. févr. 3 17:45:32 2021] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[mer. févr. 3 17:45:32 2021] ASID allocator initialised with 65536 entries
[mer. févr. 3 17:45:32 2021] Serial: AMBA PL011 UART driver
[mer. févr. 3 17:45:32 2021] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[mer. févr. 3 17:45:32 2021] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[mer. févr. 3 17:45:32 2021] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[mer. févr. 3 17:45:32 2021] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[mer. févr. 3 17:45:32 2021] cryptd: max_cpu_qlen set to 1000
[mer. févr. 3 17:45:32 2021] raid6: neonx8 gen() 1665 MB/s
[mer. févr. 3 17:45:32 2021] raid6: neonx8 xor() 1224 MB/s
[mer. févr. 3 17:45:32 2021] raid6: neonx4 gen() 1688 MB/s
[mer. févr. 3 17:45:32 2021] raid6: neonx4 xor() 1267 MB/s
[mer. févr. 3 17:45:32 2021] raid6: neonx2 gen() 1506 MB/s
[mer. févr. 3 17:45:32 2021] raid6: neonx2 xor() 1161 MB/s
[mer. févr. 3 17:45:32 2021] raid6: neonx1 gen() 1177 MB/s
[mer. févr. 3 17:45:32 2021] raid6: neonx1 xor() 933 MB/s
[mer. févr. 3 17:45:32 2021] raid6: int64x8 gen() 997 MB/s
[mer. févr. 3 17:45:32 2021] raid6: int64x8 xor() 575 MB/s
[mer. févr. 3 17:45:33 2021] raid6: int64x4 gen() 990 MB/s
[mer. févr. 3 17:45:33 2021] raid6: int64x4 xor() 589 MB/s
[mer. févr. 3 17:45:33 2021] raid6: int64x2 gen() 927 MB/s
[mer. févr. 3 17:45:33 2021] raid6: int64x2 xor() 522 MB/s
[mer. févr. 3 17:45:33 2021] raid6: int64x1 gen() 724 MB/s
[mer. févr. 3 17:45:33 2021] raid6: int64x1 xor() 390 MB/s
[mer. févr. 3 17:45:33 2021] raid6: using algorithm neonx4 gen() 1688 MB/s
[mer. févr. 3 17:45:33 2021] raid6: .... xor() 1267 MB/s, rmw enabled
[mer. févr. 3 17:45:33 2021] raid6: using neon recovery algorithm
[mer. févr. 3 17:45:33 2021] vcc12v_dcin_bkup: supplied by vcc12v_dcin
[mer. févr. 3 17:45:33 2021] vcc12v_hdd: supplied by vcc12v_dcin_bkup
[mer. févr. 3 17:45:33 2021] vcc5v0_perdev: supplied by vcc12v_dcin_bkup
[mer. févr. 3 17:45:33 2021] pcie_power: supplied by vcc5v0_perdev
[mer. févr. 3 17:45:33 2021] vcc5v0_usb: supplied by vcc5v0_perdev
[mer. févr. 3 17:45:33 2021] vcc5v0_typec: supplied by vcc5v0_usb
[mer. févr. 3 17:45:33 2021] vcc5v0_hdd: supplied by vcc12v_dcin_bkup
[mer. févr. 3 17:45:33 2021] vcc5v0_sys: supplied by vcc12v_dcin_bkup
[mer. févr. 3 17:45:33 2021] vcc3v3_sys_s3: supplied by vcc5v0_sys
[mer. févr. 3 17:45:33 2021] vcc0v9_s3: supplied by vcc3v3_sys_s3
[mer. févr. 3 17:45:33 2021] avdd_1v8_s0: supplied by vcc3v3_sys_s3
[mer. févr. 3 17:45:33 2021] vcc3v0_sd: supplied by vcc3v3_sys_s3
[mer. févr. 3 17:45:33 2021] usblan_power: supplied by vcc5v0_usb
[mer. févr. 3 17:45:33 2021] iommu: Default domain type: Translated
[mer. févr. 3 17:45:33 2021] vgaarb: loaded
[mer. févr. 3 17:45:33 2021] SCSI subsystem initialized
[mer. févr. 3 17:45:33 2021] libata version 3.00 loaded.
[mer. févr. 3 17:45:33 2021] usbcore: registered new interface driver usbfs
[mer. févr. 3 17:45:33 2021] usbcore: registered new interface driver hub
[mer. févr. 3 17:45:33 2021] usbcore: registered new device driver usb
[mer. févr. 3 17:45:33 2021] pps_core: LinuxPPS API ver. 1 registered
[mer. févr. 3 17:45:33 2021] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[mer. févr. 3 17:45:33 2021] PTP clock support registered
[mer. févr. 3 17:45:33 2021] EDAC MC: Ver: 3.0.0
[mer. févr. 3 17:45:33 2021] NetLabel: Initializing
[mer. févr. 3 17:45:33 2021] NetLabel: domain hash size = 128
[mer. févr. 3 17:45:33 2021] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[mer. févr. 3 17:45:33 2021] NetLabel: unlabeled traffic allowed by default
[mer. févr. 3 17:45:33 2021] clocksource: Switched to clocksource arch_sys_counter
[mer. févr. 3 17:45:33 2021] VFS: Disk quotas dquot_6.6.0
[mer. févr. 3 17:45:33 2021] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[mer. févr. 3 17:45:33 2021] AppArmor: AppArmor Filesystem Enabled
[mer. févr. 3 17:45:33 2021] NET: Registered protocol family 2
[mer. févr. 3 17:45:33 2021] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[mer. févr. 3 17:45:33 2021] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[mer. févr. 3 17:45:33 2021] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)
[mer. févr. 3 17:45:33 2021] TCP: Hash tables configured (established 32768 bind 32768)
[mer. févr. 3 17:45:33 2021] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[mer. févr. 3 17:45:33 2021] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[mer. févr. 3 17:45:33 2021] NET: Registered protocol family 1
[mer. févr. 3 17:45:33 2021] NET: Registered protocol family 44
[mer. févr. 3 17:45:33 2021] PCI: CLS 0 bytes, default 64
[mer. févr. 3 17:45:33 2021] Trying to unpack rootfs image as initramfs...
[mer. févr. 3 17:45:34 2021] Freeing initrd memory: 19828K
[mer. févr. 3 17:45:34 2021] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[mer. févr. 3 17:45:34 2021] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
[mer. févr. 3 17:45:34 2021] kvm [1]: IPA Size Limit: 40bits
[mer. févr. 3 17:45:34 2021] kvm [1]: vgic-v2@fff20000
[mer. févr. 3 17:45:34 2021] kvm [1]: GIC system register CPU interface enabled
[mer. févr. 3 17:45:34 2021] kvm [1]: vgic interrupt IRQ10
[mer. févr. 3 17:45:34 2021] kvm [1]: Hyp mode initialized successfully
[mer. févr. 3 17:45:34 2021] Initialise system trusted keyrings
[mer. févr. 3 17:45:34 2021] Key type blacklist registered
[mer. févr. 3 17:45:34 2021] workingset: timestamp_bits=44 max_order=20 bucket_order=0
[mer. févr. 3 17:45:34 2021] zbud: loaded
[mer. févr. 3 17:45:34 2021] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[mer. févr. 3 17:45:34 2021] fuse: init (API version 7.31)
[mer. févr. 3 17:45:34 2021] integrity: Platform Keyring initialized
[mer. févr. 3 17:45:35 2021] Key type asymmetric registered
[mer. févr. 3 17:45:35 2021] Asymmetric key parser 'x509' registered
[mer. févr. 3 17:45:35 2021] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[mer. févr. 3 17:45:35 2021] io scheduler mq-deadline registered
[mer. févr. 3 17:45:35 2021] io scheduler kyber registered
[mer. févr. 3 17:45:35 2021] io scheduler bfq registered
[mer. févr. 3 17:45:35 2021] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[mer. févr. 3 17:45:35 2021] OF: /pcie@f8000000: Missing device_type
[mer. févr. 3 17:45:35 2021] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[mer. févr. 3 17:45:35 2021] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[mer. févr. 3 17:45:35 2021] dma-pl330 ff6d0000.dma-controller: Loaded driver for PL330 DMAC-241330
[mer. févr. 3 17:45:35 2021] dma-pl330 ff6d0000.dma-controller:    DBUFF-32x8bytes Num_Chans-6 Num_Peri-12 Num_Events-12
[mer. févr. 3 17:45:35 2021] dma-pl330 ff6e0000.dma-controller: Loaded driver for PL330 DMAC-241330
[mer. févr. 3 17:45:35 2021] dma-pl330 ff6e0000.dma-controller:    DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16
[mer. févr. 3 17:45:35 2021] vdd_log: supplied by regulator-dummy
[mer. févr. 3 17:45:35 2021] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[mer. févr. 3 17:45:35 2021] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 36, base_baud = 1500000) is a 16550A
[mer. févr. 3 17:45:35 2021] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 37, base_baud = 1500000) is a 16550A
[mer. févr. 3 17:45:35 2021] printk: console [ttyS2] enabled
[mer. févr. 3 17:45:35 2021] Serial: AMBA driver
[mer. févr. 3 17:45:35 2021] cacheinfo: Unable to detect cache hierarchy for CPU 0
[mer. févr. 3 17:45:35 2021] loop: module loaded
[mer. févr. 3 17:45:35 2021] libphy: Fixed MDIO Bus: probed
[mer. févr. 3 17:45:35 2021] tun: Universal TUN/TAP device driver, 1.6
[mer. févr. 3 17:45:35 2021] thunder_xcv, ver 1.0
[mer. févr. 3 17:45:35 2021] thunder_bgx, ver 1.0
[mer. févr. 3 17:45:35 2021] nicpf, ver 1.0
[mer. févr. 3 17:45:35 2021] e1000e: Intel(R) PRO/1000 Network Driver
[mer. févr. 3 17:45:35 2021] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[mer. févr. 3 17:45:35 2021] igb: Intel(R) Gigabit Ethernet Network Driver
[mer. févr. 3 17:45:35 2021] igb: Copyright (c) 2007-2014 Intel Corporation.
[mer. févr. 3 17:45:35 2021] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[mer. févr. 3 17:45:35 2021] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[mer. févr. 3 17:45:35 2021] sky2: driver version 1.30
[mer. févr. 3 17:45:35 2021] VFIO - User Level meta-driver version: 0.3
[mer. févr. 3 17:45:35 2021] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[mer. févr. 3 17:45:35 2021] ehci-pci: EHCI PCI platform driver
[mer. févr. 3 17:45:35 2021] ehci-platform: EHCI generic platform driver
[mer. févr. 3 17:45:35 2021] ehci-platform fe380000.usb: EHCI Host Controller
[mer. févr. 3 17:45:35 2021] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 1
[mer. févr. 3 17:45:35 2021] ehci-platform fe380000.usb: irq 30, io mem 0xfe380000
[mer. févr. 3 17:45:35 2021] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00
[mer. févr. 3 17:45:35 2021] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.09
[mer. févr. 3 17:45:35 2021] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[mer. févr. 3 17:45:35 2021] usb usb1: Product: EHCI Host Controller
[mer. févr. 3 17:45:35 2021] usb usb1: Manufacturer: Linux 5.9.14-rockchip64 ehci_hcd
[mer. févr. 3 17:45:35 2021] usb usb1: SerialNumber: fe380000.usb
[mer. févr. 3 17:45:35 2021] hub 1-0:1.0: USB hub found
[mer. févr. 3 17:45:35 2021] hub 1-0:1.0: 1 port detected
[mer. févr. 3 17:45:35 2021] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[mer. févr. 3 17:45:35 2021] ohci-pci: OHCI PCI platform driver
[mer. févr. 3 17:45:35 2021] ohci-platform: OHCI generic platform driver
[mer. févr. 3 17:45:35 2021] ohci-platform fe3a0000.usb: Generic Platform OHCI controller
[mer. févr. 3 17:45:35 2021] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 2
[mer. févr. 3 17:45:35 2021] ohci-platform fe3a0000.usb: irq 31, io mem 0xfe3a0000
[mer. févr. 3 17:45:35 2021] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.09
[mer. févr. 3 17:45:35 2021] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[mer. févr. 3 17:45:35 2021] usb usb2: Product: Generic Platform OHCI controller
[mer. févr. 3 17:45:35 2021] usb usb2: Manufacturer: Linux 5.9.14-rockchip64 ohci_hcd
[mer. févr. 3 17:45:35 2021] usb usb2: SerialNumber: fe3a0000.usb
[mer. févr. 3 17:45:35 2021] hub 2-0:1.0: USB hub found
[mer. févr. 3 17:45:35 2021] hub 2-0:1.0: 1 port detected
[mer. févr. 3 17:45:35 2021] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[mer. févr. 3 17:45:35 2021] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 3
[mer. févr. 3 17:45:35 2021] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000000002010010
[mer. févr. 3 17:45:35 2021] xhci-hcd xhci-hcd.0.auto: irq 228, io mem 0xfe900000
[mer. févr. 3 17:45:35 2021] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.09
[mer. févr. 3 17:45:35 2021] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[mer. févr. 3 17:45:35 2021] usb usb3: Product: xHCI Host Controller
[mer. févr. 3 17:45:35 2021] usb usb3: Manufacturer: Linux 5.9.14-rockchip64 xhci-hcd
[mer. févr. 3 17:45:35 2021] usb usb3: SerialNumber: xhci-hcd.0.auto
[mer. févr. 3 17:45:35 2021] hub 3-0:1.0: USB hub found
[mer. févr. 3 17:45:35 2021] hub 3-0:1.0: 1 port detected
[mer. févr. 3 17:45:35 2021] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[mer. févr. 3 17:45:35 2021] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 4
[mer. févr. 3 17:45:35 2021] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
[mer. févr. 3 17:45:35 2021] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[mer. févr. 3 17:45:35 2021] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.09
[mer. févr. 3 17:45:35 2021] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[mer. févr. 3 17:45:35 2021] usb usb4: Product: xHCI Host Controller
[mer. févr. 3 17:45:35 2021] usb usb4: Manufacturer: Linux 5.9.14-rockchip64 xhci-hcd
[mer. févr. 3 17:45:35 2021] usb usb4: SerialNumber: xhci-hcd.0.auto
[mer. févr. 3 17:45:35 2021] hub 4-0:1.0: USB hub found
[mer. févr. 3 17:45:35 2021] hub 4-0:1.0: 1 port detected
[mer. févr. 3 17:45:35 2021] usbcore: registered new interface driver usb-storage
[mer. févr. 3 17:45:35 2021] mousedev: PS/2 mouse device common for all mice
[mer. févr. 3 17:45:35 2021] i2c /dev entries driver
[mer. févr. 3 17:45:35 2021] pca953x 2-0020: using no AI
[mer. févr. 3 17:45:35 2021] rk808 0-001b: chip id: 0x0
[mer. févr. 3 17:45:35 2021] rk808-regulator rk808-regulator: there is no dvs0 gpio
[mer. févr. 3 17:45:35 2021] rk808-regulator rk808-regulator: there is no dvs1 gpio
[mer. févr. 3 17:45:35 2021] vdd_center: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vdd_cpu_l: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc_ddr_s3: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc1v8_sys_s3: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc1v8_dvp: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc3v0_touch: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc1v8_s3: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc_sdio_s0: Bringing 3300000uV into 3000000-3000000uV
[mer. févr. 3 17:45:35 2021] vcc_sdio_s0: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcca3v0_codec: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc1v5_s3: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcca1v8_codec: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc3v0_s3: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] vcc3v3_sys_s0: failed to get the current voltage(-517)
[mer. févr. 3 17:45:35 2021] vcc3v3_sys_s0: supplied by vcc3v3_sys_s3
[mer. févr. 3 17:45:35 2021] vcc3v3_s0: supplied by vcc3v3_sys_s3
[mer. févr. 3 17:45:35 2021] rk808-rtc rk808-rtc: registered as rtc0
[mer. févr. 3 17:45:35 2021] rk808-rtc rk808-rtc: setting system clock to 2021-02-03T16:45:36 UTC (1612370736)
[mer. févr. 3 17:45:35 2021] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
[mer. févr. 3 17:45:35 2021] vcc1v8_sys_s0: supplied by vcc1v8_sys_s3
[mer. févr. 3 17:45:35 2021] avdd_0v9_s0: supplied by vcc1v8_sys_s3
[mer. févr. 3 17:45:35 2021] vdd_cpu_b: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] fan53555-regulator 0-0041: FAN53555 Option[8] Rev[1] Detected!
[mer. févr. 3 17:45:35 2021] random: fast init done
[mer. févr. 3 17:45:35 2021] vdd_gpu: supplied by vcc5v0_sys
[mer. févr. 3 17:45:35 2021] dw_wdt ff848000.watchdog: No valid TOPs array specified
[mer. févr. 3 17:45:35 2021] sdhci: Secure Digital Host Controller Interface driver
[mer. févr. 3 17:45:35 2021] sdhci: Copyright(c) Pierre Ossman
[mer. févr. 3 17:45:35 2021] Synopsys Designware Multimedia Card Interface Driver
[mer. févr. 3 17:45:35 2021] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[mer. févr. 3 17:45:35 2021] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[mer. févr. 3 17:45:35 2021] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[mer. févr. 3 17:45:35 2021] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 28,32 bit host data width,256 deep fifo
[mer. févr. 3 17:45:35 2021] dwmmc_rockchip fe320000.mmc: Got CD GPIO
[mer. févr. 3 17:45:35 2021] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[mer. févr. 3 17:45:35 2021] sdhci-pltfm: SDHCI platform and OF driver helper
[mer. févr. 3 17:45:35 2021] mmc1: CQHCI version 5.10
[mer. févr. 3 17:45:35 2021] mmc1: SDHCI controller on fe330000.sdhci [fe330000.sdhci] using ADMA
[mer. févr. 3 17:45:35 2021] ledtrig-cpu: registered to indicate activity on CPUs
[mer. févr. 3 17:45:35 2021] hid: raw HID events driver (C) Jiri Kosina
[mer. févr. 3 17:45:35 2021] usbcore: registered new interface driver usbhid
[mer. févr. 3 17:45:35 2021] usbhid: USB HID core driver
[mer. févr. 3 17:45:35 2021] drop_monitor: Initializing network drop monitor service
[mer. févr. 3 17:45:35 2021] NET: Registered protocol family 10
[mer. févr. 3 17:45:35 2021] mmc_host mmc0: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)
[mer. févr. 3 17:45:35 2021] Segment Routing with IPv6
[mer. févr. 3 17:45:35 2021] NET: Registered protocol family 17
[mer. févr. 3 17:45:35 2021] 8021q: 802.1Q VLAN Support v1.8
[mer. févr. 3 17:45:35 2021] Key type dns_resolver registered
[mer. févr. 3 17:45:35 2021] registered taskstats version 1
[mer. févr. 3 17:45:35 2021] Loading compiled-in X.509 certificates
[mer. févr. 3 17:45:35 2021] Loaded X.509 cert 'Build time autogenerated kernel key: dccf44bd6a6a6c80c8ebb43ecbfc03e645b516d0'
[mer. févr. 3 17:45:35 2021] zswap: loaded using pool lzo/zbud
[mer. févr. 3 17:45:35 2021] Key type ._fscrypt registered
[mer. févr. 3 17:45:35 2021] Key type .fscrypt registered
[mer. févr. 3 17:45:35 2021] Key type fscrypt-provisioning registered
[mer. févr. 3 17:45:35 2021] mmc1: mmc_select_hs200 failed, error -110
[mer. févr. 3 17:45:35 2021] mmc1: error -110 whilst initialising MMC card
[mer. févr. 3 17:45:35 2021] Btrfs loaded, crc32c=crc32c-generic
[mer. févr. 3 17:45:35 2021] Key type encrypted registered
[mer. févr. 3 17:45:35 2021] AppArmor: AppArmor sha1 policy hashing enabled
[mer. févr. 3 17:45:35 2021] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[mer. févr. 3 17:45:35 2021] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[mer. févr. 3 17:45:35 2021] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[mer. févr. 3 17:45:35 2021] mmc1: mmc_select_hs200 failed, error -110
[mer. févr. 3 17:45:35 2021] mmc1: error -110 whilst initialising MMC card
[mer. févr. 3 17:45:35 2021] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[mer. févr. 3 17:45:35 2021] pci_bus 0000:00: root bus resource [bus 00-1f]
[mer. févr. 3 17:45:35 2021] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[mer. févr. 3 17:45:35 2021] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[mer. févr. 3 17:45:35 2021] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[mer. févr. 3 17:45:35 2021] pci 0000:00:00.0: supports D1
[mer. févr. 3 17:45:35 2021] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[mer. févr. 3 17:45:35 2021] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: [197b:0585] type 00 class 0x010601
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x10: [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x14: [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x18: [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x1c: [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x20: [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x00001fff]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: Max Payload Size set to 256 (was 128, max 512)
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: PME# supported from D3hot
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x2 link at 0000:00:00.0 (capable of 15.752 Gb/s with 8.0 GT/s PCIe x2 link)
[mer. févr. 3 17:45:35 2021] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[mer. févr. 3 17:45:35 2021] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01
[mer. févr. 3 17:45:35 2021] pci 0000:00:00.0: BAR 14: assigned [mem 0xfa000000-0xfa0fffff]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pref]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa011fff]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 0: no space for [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 0: failed to assign [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 1: no space for [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 1: failed to assign [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 2: no space for [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 2: failed to assign [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 3: no space for [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 3: failed to assign [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 4: no space for [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:01:00.0: BAR 4: failed to assign [io size 0x0080]
[mer. févr. 3 17:45:35 2021] pci 0000:00:00.0: PCI bridge to [bus 01]
[mer. févr. 3 17:45:35 2021] pci 0000:00:00.0: bridge window [mem 0xfa000000-0xfa0fffff]
[mer. févr. 3 17:45:35 2021] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[mer. févr. 3 17:45:35 2021] pcieport 0000:00:00.0: PME: Signaling with IRQ 239
[mer. févr. 3 17:45:35 2021] pcieport 0000:00:00.0: AER: enabled with IRQ 239
[mer. févr. 3 17:45:35 2021] ahci 0000:01:00.0: version 3.0
[mer. févr. 3 17:45:35 2021] ahci 0000:01:00.0: enabling device (0000 -> 0002)
[mer. févr. 3 17:45:35 2021] ahci 0000:01:00.0: SSS flag set, parallel bus scan disabled
[mer. févr. 3 17:45:35 2021] ahci 0000:01:00.0: AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f impl SATA mode
[mer. févr. 3 17:45:35 2021] ahci 0000:01:00.0: flags: 64bit ncq sntf stag pm led clo pmp fbs pio slum part ccc apst boh
[mer. févr. 3 17:45:35 2021] scsi host0: ahci
[mer. févr. 3 17:45:35 2021] scsi host1: ahci
[mer. févr. 3 17:45:35 2021] scsi host2: ahci
[mer. févr. 3 17:45:35 2021] scsi host3: ahci
[mer. févr. 3 17:45:35 2021] scsi host4: ahci
[mer. févr. 3 17:45:35 2021] ata1: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010100 irq 240
[mer. févr. 3 17:45:35 2021] ata2: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010180 irq 241
[mer. févr. 3 17:45:35 2021] ata3: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010200 irq 242
[mer. févr. 3 17:45:35 2021] ata4: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010280 irq 243
[mer. févr. 3 17:45:35 2021] ata5: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010300 irq 244
[mer. févr. 3 17:45:35 2021] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[mer. févr. 3 17:45:35 2021] of_cfs_init
[mer. févr. 3 17:45:35 2021] of_cfs_init: OK
[mer. févr. 3 17:45:35 2021] mmc1: mmc_select_hs200 failed, error -110
[mer. févr. 3 17:45:35 2021] mmc1: error -110 whilst initialising MMC card
[mer. févr. 3 17:45:35 2021] usb 3-1: New USB device found, idVendor=2109, idProduct=2815, bcdDevice= 7.04
[mer. févr. 3 17:45:35 2021] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[mer. févr. 3 17:45:35 2021] usb 3-1: Product: USB2.0 Hub
[mer. févr. 3 17:45:35 2021] usb 3-1: Manufacturer: VIA Labs, Inc.
[mer. févr. 3 17:45:35 2021] hub 3-1:1.0: USB hub found
[mer. févr. 3 17:45:35 2021] hub 3-1:1.0: 4 ports detected
[mer. févr. 3 17:45:35 2021] mmc1: mmc_select_hs200 failed, error -110
[mer. févr. 3 17:45:35 2021] mmc1: error -110 whilst initialising MMC card
[mer. févr. 3 17:45:35 2021] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[mer. févr. 3 17:45:35 2021] dwmmc_rockchip fe320000.mmc: Successfully tuned phase to 210
[mer. févr. 3 17:45:35 2021] mmc0: new ultra high speed SDR104 SDXC card at address 0001
[mer. févr. 3 17:45:35 2021] mmcblk0: mmc0:0001 ED4QT 119 GiB
[mer. févr. 3 17:45:35 2021] mmcblk0: p1
[mer. févr. 3 17:45:35 2021] usb 4-1: New USB device found, idVendor=2109, idProduct=0815, bcdDevice= 7.04
[mer. févr. 3 17:45:35 2021] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[mer. févr. 3 17:45:35 2021] usb 4-1: Product: USB3.0 Hub
[mer. févr. 3 17:45:35 2021] usb 4-1: Manufacturer: VIA Labs, Inc.
[mer. févr. 3 17:45:36 2021] hub 4-1:1.0: USB hub found
[mer. févr. 3 17:45:36 2021] hub 4-1:1.0: 4 ports detected
[mer. févr. 3 17:45:36 2021] usb 3-1.4: new high-speed USB device number 3 using xhci-hcd
[mer. févr. 3 17:45:37 2021] usb 4-1.4: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd
[mer. févr. 3 17:45:37 2021] usb 4-1.4: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=30.00
[mer. févr. 3 17:45:37 2021] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[mer. févr. 3 17:45:37 2021] usb 4-1.4: Product: USB 10/100/1G/2.5G LAN
[mer. févr. 3 17:45:37 2021] usb 4-1.4: Manufacturer: Realtek
[mer. févr. 3 17:45:37 2021] usb 4-1.4: SerialNumber: 000000001
[mer. févr. 3 17:45:45 2021] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[mer. févr. 3 17:45:45 2021] ata1.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:46 2021] ata1.00: ATA-9: WDC WD140EDFZ-11A0VA0, 81.00A81, max UDMA/133
[mer. févr. 3 17:45:46 2021] ata1.00: 27344764928 sectors, multi 0: LBA48 NCQ (depth 32), AA
[mer. févr. 3 17:45:46 2021] ata1.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:46 2021] ata1.00: configured for UDMA/133
[mer. févr. 3 17:45:46 2021] scsi 0:0:0:0: Direct-Access ATA WDC WD140EDFZ-11 0A81 PQ: 0 ANSI: 5
[mer. févr. 3 17:45:46 2021] sd 0:0:0:0: [sda] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
[mer. févr. 3 17:45:46 2021] sd 0:0:0:0: [sda] 4096-byte physical blocks
[mer. févr. 3 17:45:46 2021] sd 0:0:0:0: [sda] Write Protect is off
[mer. févr. 3 17:45:46 2021] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[mer. févr. 3 17:45:46 2021] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[mer. févr. 3 17:45:46 2021] sda: sda1
[mer. févr. 3 17:45:46 2021] sd 0:0:0:0: [sda] Attached SCSI disk
[mer. févr. 3 17:45:46 2021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[mer. févr. 3 17:45:46 2021] ata2.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:46 2021] ata2.00: ATA-9: WDC WD140EDFZ-11A0VA0, 81.00A81, max UDMA/133
[mer. févr. 3 17:45:46 2021] ata2.00: 27344764928 sectors, multi 0: LBA48 NCQ (depth 32), AA
[mer. févr. 3 17:45:46 2021] ata2.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:46 2021] ata2.00: configured for UDMA/133
[mer. févr. 3 17:45:46 2021] scsi 1:0:0:0: Direct-Access ATA WDC WD140EDFZ-11 0A81 PQ: 0 ANSI: 5
[mer. févr. 3 17:45:46 2021] sd 1:0:0:0: [sdb] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
[mer. févr. 3 17:45:46 2021] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[mer. févr. 3 17:45:46 2021] sd 1:0:0:0: [sdb] Write Protect is off
[mer. févr. 3 17:45:46 2021] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[mer. févr. 3 17:45:46 2021] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[mer. févr. 3 17:45:46 2021] sdb: sdb1
[mer. févr. 3 17:45:46 2021] sd 1:0:0:0: [sdb] Attached SCSI disk
[mer. févr. 3 17:45:47 2021] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[mer. févr. 3 17:45:47 2021] ata3.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:47 2021] ata3.00: ATA-9: WDC WD140EDFZ-11A0VA0, 81.00A81, max UDMA/133
[mer. févr. 3 17:45:47 2021] ata3.00: 27344764928 sectors, multi 0: LBA48 NCQ (depth 32), AA
[mer. févr. 3 17:45:47 2021] ata3.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:47 2021] ata3.00: configured for UDMA/133
[mer. févr. 3 17:45:47 2021] scsi 2:0:0:0: Direct-Access ATA WDC WD140EDFZ-11 0A81 PQ: 0 ANSI: 5
[mer. févr. 3 17:45:47 2021] sd 2:0:0:0: [sdc] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
[mer. févr. 3 17:45:47 2021] sd 2:0:0:0: [sdc] 4096-byte physical blocks
[mer. févr. 3 17:45:47 2021] sd 2:0:0:0: [sdc] Write Protect is off
[mer. févr. 3 17:45:47 2021] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[mer. févr. 3 17:45:47 2021] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[mer. févr. 3 17:45:47 2021] sdc: sdc1
[mer. févr. 3 17:45:47 2021] sd 2:0:0:0: [sdc] Attached SCSI disk
[mer. févr. 3 17:45:47 2021] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[mer. févr. 3 17:45:47 2021] ata4.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:47 2021] ata4.00: ATA-9: WDC WD140EDFZ-11A0VA0, 81.00A81, max UDMA/133
[mer. févr. 3 17:45:47 2021] ata4.00: 27344764928 sectors, multi 0: LBA48 NCQ (depth 32), AA
[mer. févr. 3 17:45:47 2021] ata4.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:47 2021] ata4.00: configured for UDMA/133
[mer. févr. 3 17:45:47 2021] scsi 3:0:0:0: Direct-Access ATA WDC WD140EDFZ-11 0A81 PQ: 0 ANSI: 5
[mer. févr. 3 17:45:47 2021] sd 3:0:0:0: [sdd] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
[mer. févr. 3 17:45:47 2021] sd 3:0:0:0: [sdd] 4096-byte physical blocks
[mer. févr. 3 17:45:47 2021] sd 3:0:0:0: [sdd] Write Protect is off
[mer. févr. 3 17:45:47 2021] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[mer. févr. 3 17:45:47 2021] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[mer. févr. 3 17:45:47 2021] sdd: sdd1
[mer. févr. 3 17:45:47 2021] sd 3:0:0:0: [sdd] Attached SCSI disk
[mer. févr. 3 17:45:48 2021] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[mer. févr. 3 17:45:48 2021] ata5.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:48 2021] ata5.00: ATA-9: WDC WD140EDFZ-11A0VA0, 81.00A81, max UDMA/133
[mer. févr. 3 17:45:48 2021] ata5.00: 27344764928 sectors, multi 0: LBA48 NCQ (depth 32), AA
[mer. févr. 3 17:45:48 2021] ata5.00: supports DRM functions and may not be fully accessible
[mer. févr. 3 17:45:48 2021] ata5.00: configured for UDMA/133
[mer. févr. 3 17:45:48 2021] scsi 4:0:0:0: Direct-Access ATA WDC WD140EDFZ-11 0A81 PQ: 0 ANSI: 5
[mer. févr. 3 17:45:48 2021] sd 4:0:0:0: [sde] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
[mer. févr. 3 17:45:48 2021] sd 4:0:0:0: [sde] 4096-byte physical blocks
[mer. févr. 3 17:45:48 2021] sd 4:0:0:0: [sde] Write Protect is off
[mer. févr. 3 17:45:48 2021] sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
[mer. févr. 3 17:45:48 2021] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[mer. févr. 3 17:45:48 2021] sde: sde1
[mer. févr. 3 17:45:48 2021] sd 4:0:0:0: [sde] Attached SCSI disk
[mer. févr. 3 17:45:48 2021] Freeing unused kernel memory: 4224K
[mer. févr. 3 17:45:48 2021] Run /init as init process
[mer. févr. 3 17:45:48 2021] with arguments:
[mer. févr. 3 17:45:48 2021] /init
[mer. févr. 3 17:45:48 2021] with environment:
[mer. févr. 3 17:45:48 2021] HOME=/
[mer. févr. 3 17:45:48 2021] TERM=linux
[mer. févr. 3 17:45:48 2021] ubootpart=21825e31-01
[mer. févr. 3 17:45:48 2021] cgroup_enable=memory
[mer. févr. 3 17:45:48 2021] cgroup_memory=1
[mer. févr. 3 17:45:48 2021] input: adc-keys as /devices/platform/adc-keys/input/input1
[mer. févr. 3 17:45:48 2021] rockchip-vop ff8f0000.vop: Adding to iommu group 2
[mer. févr. 3 17:45:48 2021] rockchip-vop ff900000.vop: Adding to iommu group 3
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: IRQ eth_wake_irq not found
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: IRQ eth_lpi not found
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: PTP uses main clock
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: clock input or output? (input).
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: TX delay(0x28).
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: RX delay(0x20).
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: integrated PHY? (no).
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: clock input from PHY
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: init for RGMII
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: User ID: 0x10, Synopsys ID: 0x35
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet:    DWMAC1000
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: DMA HW capability register supported
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: RX Checksum Offload Engine supported
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: COE Type 2
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: TX Checksum insertion supported
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: Wake-Up On Lan supported
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: Normal descriptors
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: Ring mode enabled
[mer. févr. 3 17:45:48 2021] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[mer. févr. 3 17:45:48 2021] panfrost ff9a0000.gpu: clock rate = 500000000
[mer. févr. 3 17:45:48 2021] panfrost ff9a0000.gpu: mali-t860 id 0x860 major 0x2 minor 0x0 status 0x0
[mer. févr. 3 17:45:48 2021] panfrost ff9a0000.gpu: features: 00000000,100e77bf, issues: 00000000,24040400
[mer. févr. 3 17:45:48 2021] panfrost ff9a0000.gpu: Features: L2:0x07120206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002830 AS:0xff JS:0x7
[mer. févr. 3 17:45:48 2021] panfrost ff9a0000.gpu: shader_present=0xf l2_present=0x1
[mer. févr. 3 17:45:49 2021] [drm] Initialized panfrost 1.1.0 20180908 for ff9a0000.gpu on minor 0
[mer. févr. 3 17:45:49 2021] libphy: stmmac: probed
[mer. févr. 3 17:45:49 2021] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[mer. févr. 3 17:45:49 2021] RTL8211F Gigabit Ethernet stmmac-0:01: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[mer. févr. 3 17:45:49 2021] random: crng init done
[mer. févr. 3 17:45:49 2021] async_tx: api initialized (async)
[mer. févr. 3 17:45:49 2021] md/raid:md0: device sde1 operational as raid disk 4
[mer. févr. 3 17:45:49 2021] md/raid:md0: device sdd1 operational as raid disk 3
[mer. févr. 3 17:45:49 2021] md/raid:md0: device sdc1 operational as raid disk 2
[mer. févr. 3 17:45:49 2021] md/raid:md0: device sdb1 operational as raid disk 1
[mer. févr. 3 17:45:49 2021] md/raid:md0: device sda1 operational as raid disk 0
[mer. févr. 3 17:45:49 2021] md/raid:md0: raid level 5 active with 5 out of 5 devices, algorithm 2
[mer. févr. 3 17:45:49 2021] md0: detected capacity change from 0 to 56001531215872
[mer. févr. 3 17:45:49 2021] dw-apb-uart ff1a0000.serial: forbid DMA for kernel console
[mer. févr. 3 17:45:56 2021] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
[mer. févr. 3 17:45:57 2021] systemd[1]: Inserted module 'autofs4'
[mer. févr. 3 17:45:57 2021] 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)
[mer. févr. 3 17:45:57 2021] systemd[1]: Detected architecture arm64.
[mer. févr. 3 17:45:57 2021] systemd[1]: Set hostname to <helios64>.
[mer. févr. 3 17:45:57 2021] systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
[mer. févr. 3 17:45:57 2021] systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
[mer. févr. 3 17:45:57 2021] systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid → /run/fancontrol.pid; please update the unit file accordingly.
[mer. févr. 3 17:45:58 2021] systemd[1]: Listening on udev Kernel Socket.
[mer. févr. 3 17:45:58 2021] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[mer. févr. 3 17:45:58 2021] systemd[1]: Created slice system-serial\x2dgetty.slice.
[mer. févr. 3 17:45:58 2021] systemd[1]: Listening on initctl Compatibility Named Pipe.
[mer. févr. 3 17:45:58 2021] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[mer. févr. 3 17:45:58 2021] lm75 2-004c: hwmon2: sensor 'lm75'
[mer. févr. 3 17:45:59 2021] input: beeper as /devices/platform/beeper/input/input2
[mer. févr. 3 17:45:59 2021] sd 0:0:0:0: Attached scsi generic sg0 type 0
[mer. févr. 3 17:45:59 2021] sd 1:0:0:0: Attached scsi generic sg1 type 0
[mer. févr. 3 17:45:59 2021] sd 2:0:0:0: Attached scsi generic sg2 type 0
[mer. févr. 3 17:45:59 2021] sd 3:0:0:0: Attached scsi generic sg3 type 0
[mer. févr. 3 17:45:59 2021] sd 4:0:0:0: Attached scsi generic sg4 type 0
[mer. févr. 3 17:45:59 2021] mc: Linux media interface: v0.10
[mer. févr. 3 17:45:59 2021] videodev: Linux video capture interface: v2.00
[mer. févr. 3 17:45:59 2021] rockchip-rga ff680000.rga: HW Version: 0x03.02
[mer. févr. 3 17:45:59 2021] rockchip-rga ff680000.rga: Registered rockchip-rga as /dev/video0
[mer. févr. 3 17:45:59 2021] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22
[mer. févr. 3 17:45:59 2021] rockchip_vdec: module is from the staging directory, the quality is unknown, you have been warned.
[mer. févr. 3 17:45:59 2021] rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops [rockchipdrm])
[mer. févr. 3 17:45:59 2021] [drm] unsupported AFBC format[3231564e]
[mer. févr. 3 17:45:59 2021] rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops [rockchipdrm])
[mer. févr. 3 17:45:59 2021] rockchip-drm display-subsystem: bound fec00000.dp (ops cdn_dp_component_ops [rockchipdrm])
[mer. févr. 3 17:45:59 2021] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[mer. févr. 3 17:45:59 2021] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 1
[mer. févr. 3 17:45:59 2021] rkvdec ff660000.video-codec: Adding to iommu group 1
[mer. févr. 3 17:45:59 2021] OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/otg-port
[mer. févr. 3 17:45:59 2021] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn
[mer. févr. 3 17:45:59 2021] xhci-hcd xhci-hcd.3.auto: xHCI Host Controller
[mer. févr. 3 17:45:59 2021] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 5
[mer. févr. 3 17:45:59 2021] xhci-hcd xhci-hcd.3.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000000002010010
[mer. févr. 3 17:45:59 2021] xhci-hcd xhci-hcd.3.auto: irq 227, io mem 0xfe800000
[mer. févr. 3 17:45:59 2021] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.09
[mer. févr. 3 17:45:59 2021] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[mer. févr. 3 17:45:59 2021] usb usb5: Product: xHCI Host Controller
[mer. févr. 3 17:45:59 2021] usb usb5: Manufacturer: Linux 5.9.14-rockchip64 xhci-hcd
[mer. févr. 3 17:45:59 2021] usb usb5: SerialNumber: xhci-hcd.3.auto
[mer. févr. 3 17:45:59 2021] hub 5-0:1.0: USB hub found
[mer. févr. 3 17:45:59 2021] hub 5-0:1.0: 1 port detected
[mer. févr. 3 17:45:59 2021] xhci-hcd xhci-hcd.3.auto: xHCI Host Controller
[mer. févr. 3 17:45:59 2021] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 6
[mer. févr. 3 17:45:59 2021] xhci-hcd xhci-hcd.3.auto: Host supports USB 3.0 SuperSpeed
[mer. févr. 3 17:45:59 2021] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[mer. févr. 3 17:45:59 2021] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.09
[mer. févr. 3 17:45:59 2021] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[mer. févr. 3 17:45:59 2021] usb usb6: Product: xHCI Host Controller
[mer. févr. 3 17:45:59 2021] usb usb6: Manufacturer: Linux 5.9.14-rockchip64 xhci-hcd
[mer. févr. 3 17:45:59 2021] usb usb6: SerialNumber: xhci-hcd.3.auto
[mer. févr. 3 17:45:59 2021] hub 6-0:1.0: USB hub found
[mer. févr. 3 17:45:59 2021] hub 6-0:1.0: 1 port detected
[mer. févr. 3 17:45:59 2021] hantro_vpu: module is from the staging directory, the quality is unknown, you have been warned.
[mer. févr. 3 17:45:59 2021] hantro-vpu ff650000.video-codec: Adding to iommu group 0
[mer. févr. 3 17:45:59 2021] hantro-vpu ff650000.video-codec: registered rockchip,rk3399-vpu-enc as /dev/video2
[mer. févr. 3 17:45:59 2021] hantro-vpu ff650000.video-codec: registered rockchip,rk3399-vpu-dec as /dev/video3
[mer. févr. 3 17:45:59 2021] usb 4-1.4: reset SuperSpeed Gen 1 USB device number 3 using xhci-hcd
[mer. févr. 3 17:45:59 2021] r8152 4-1.4:1.0 (unnamed net_device) (uninitialized): netif_napi_add() called with weight 256
[mer. févr. 3 17:45:59 2021] r8152 4-1.4:1.0 eth1: v2.14.0 (2020/09/24)
[mer. févr. 3 17:45:59 2021] r8152 4-1.4:1.0 eth1: This product is covered by one or more of the following patents:
        US6,570,884, US6,115,776, and US6,327,625.

[mer. févr. 3 17:45:59 2021] usbcore: registered new interface driver r8152
[mer. févr. 3 17:46:00 2021] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[mer. févr. 3 17:46:03 2021] EXT4-fs (md0): recovery complete
[mer. févr. 3 17:46:03 2021] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[mer. févr. 3 17:46:03 2021] systemd[1]: Mounted /mnt/internal/raid.
[mer. févr. 3 17:46:03 2021] systemd[1]: Reached target Local File Systems.
[mer. févr. 3 17:46:03 2021] systemd[1]: Starting Armbian ZRAM config...
[mer. févr. 3 17:46:03 2021] systemd[1]: Starting Set console font and keymap...
[mer. févr. 3 17:46:03 2021] systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
[mer. févr. 3 17:46:03 2021] systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
[mer. févr. 3 17:46:03 2021] systemd[1]: Condition check resulted in Mark the need to relabel after reboot being skipped.
[mer. févr. 3 17:46:03 2021] systemd[1]: Starting Raise network interfaces...
[mer. févr. 3 17:46:03 2021] systemd[1]: Started Set console font and keymap.
[mer. févr. 3 17:46:03 2021] systemd[1]: Received SIGRTMIN+20 from PID 373 (plymouthd).
[mer. févr. 3 17:46:03 2021] zram: Added device: zram0
[mer. févr. 3 17:46:03 2021] zram: Added device: zram1
[mer. févr. 3 17:46:03 2021] zram: Added device: zram2
[mer. févr. 3 17:46:03 2021] zram0: detected capacity change from 0 to 1992257536
[mer. févr. 3 17:46:03 2021] Adding 1945560k swap on /dev/zram0. Priority:5 extents:1 across:1945560k SSFS
[mer. févr. 3 17:46:04 2021] zram1: detected capacity change from 0 to 52428800
[mer. févr. 3 17:46:04 2021] EXT4-fs (zram1): mounted filesystem without journal. Opts: discard
[mer. févr. 3 17:46:04 2021] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff)
[mer. févr. 3 17:46:05 2021] vcc5v0_typec: disabling
[mer. févr. 3 17:46:07 2021] systemd-journald[795]: Received request to flush runtime journal from PID 1
[mer. févr. 3 17:46:09 2021] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL)
[mer. févr. 3 17:46:09 2021] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
[mer. févr. 3 17:46:09 2021] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
[mer. févr. 3 17:46:09 2021] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode
[mer. févr. 3 17:46:12 2021] broken atomic modeset userspace detected, disabling atomic
[mer. févr. 3 17:46:12 2021] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[mer. févr. 3 17:46:12 2021] Bridge firewalling registered
[mer. févr. 3 17:46:13 2021] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[mer. févr. 3 17:46:13 2021] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[mer. févr. 3 17:46:13 2021] Initializing XFRM netlink socket

dmesg -T (during reboot after freeze)

the MMC errors are new

I don't know for the error about voltage that can't be read

edit : to be noted, i was still in "performance" mode for CPU governance, with same min/max possible values (here : https://forum.armbian.com/topic/16944-crazy-instability/ it is suggested to not be in that mode -> have just reverted to min possible value / max possible + powersave mode)

Edited February 4, 2021 by aprayoga
move kernel log inside spoiler

SR-G · February 16, 2021

So i don't know if it's enough to say that everything is now under control, but for now my uptime is +12 days (before, i had at least one freeze per week, and often more than that).

Quote

uptime
15:56:12 up 12 days, 22:10, 3 users, load average: 4,24, 4,12, 3,64

So a little bit too soon to be sure.

+ for now i'm avoiding 5.10 kernel installation and corresponding reboot.

kabo · February 22, 2021

Is this the same issue I'm having over in this thread?

The armbianEnv.txt on my microSD card looked like this

verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x3322:u

I removed the last usbstoragequirks as that didn't seem to present in anyone else's example I've seen. Made no difference.

SR-G · February 23, 2021

About why your NAS has been frozen, maybe indeed (it's quite possible), but sadly in addition you are encountering some other issues during the reboot (that I haven't encountered on my side - crossing fingers on that topic ...). But of course these many freezes and reboots can't be good in any way for the operating system on disk or even for the hardware (hdd)...

I would suggest to try a fresh reinstall on a second scarf to see if everything boots up nicely, as a first step ...

SR-G · March 2, 2021

On 2/16/2021 at 4:27 PM, SR-G said:

So i don't know if it's enough to say that everything is now under control, but for now my uptime is +12 days (before, i had at least one freeze per week, and often more than that).

So a little bit too soon to be sure.

+ for now i'm avoiding 5.10 kernel installation and corresponding reboot.

So 26 days as uptime now - it seems better.

Quote

10:11:49 up 26 days, 16:26, 2 users, load average: 0,13, 0,14, 0,06

FloBaoti · March 4, 2021

Mine has running for 10+ days, and suddenly now it's rebooting every night (kernel panic).

gprovost · March 10, 2021

Could you guys update to latest kernel (linux-image-current-rockchip64_21.02.3_arm64 / LK 5.10.21) and revert to ondemand governor with the full range of frequency in case you were on performance mode.

Also remove any vdd voltage tweak you might have put in /boot/boot.cmd. If you had vdd tweak you will need to rebuild u-boot boot script after removing the lines in /boot/boot.cmd

mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

Let us know how the new kernel improves the stability.

Seneca · March 11, 2021

On 3/10/2021 at 6:13 AM, gprovost said:
Could you guys update to latest kernel (linux-image-current-rockchip64_21.02.3_arm64 / LK 5.10.21) and revert to ondemand governor with the full range of frequency in case you were on performance mode.

Also remove any vdd voltage tweak you might have put in /boot/boot.cmd. If you had vdd tweak you will need to rebuild u-boot boot script after removing the lines in /boot/boot.cmd
mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
Let us know how the new kernel improves the stability.

I did a dist-upgrade yesterday, and I've had two freezes since then due to high IO (probably). But I've reverted the cpufreq tweaks now (ondemand+min/max 400000/1800000), and I never enabled he vdd tweaks in boot.cmd, so there wasn't anything to revert. So we'll see how it goes, I'll try to put a lot of IO load on it the coming days.

5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

slymanjojo · March 12, 2021

@gprovost

Been Running stable since 21.02.3 Buster.

cat /etc/default/cpufrequtils
ENABLE=true
MIN_SPEED=408000
MAX_SPEED=1800000
GOVERNOR=ondemand

No VDD tweaks.

Seneca · March 12, 2021

Just an update from yesterday, no freezes or crashes yet, even though quite heavy IO and CPU.

jbergler · March 15, 2021

My system was stable for a long time (~3-4 weeks) and then the other day it soft locked with a panic (trace was in ZFS).

Rest of the system was still vaguely usable, great - this has happened before I thought, so I rebooted and could not get it to finish booting.

Every time, one of two things would happen as the zfs pool was mounted.

1) system would silently lock up, no red led, no panic on console, nothing

2) system would panic, red led started flashing.

The only way I've been able to get the system to boot is by unplugging the disks, waiting for the system to boot and then plugging the disks back in and mounting them.

Even then the system crashes again within a short period of time (maybe because the ZFS is trying to scrub following the crash)

I've upgraded to 21.02.3 / 5.10.21

I never had the vdd tweaks applied, but I've tried both with and without them.

I've explicitly run the boot-loader upload steps in armbian config (was Nov, now Mar 8)

I'm relatively confident the issue I'm seeing relates to the others here, more often than not the panics are page faults (null pointer, address between kernel and user space, could not execute from non-execute memory) which seems plausible given the focus on voltage tuning.

Any ideas?

I can make an effort to collect boot logs if that's helpful, but given the frequency of these reports it seems like this is a relatively widespread issue.

aprayoga · March 16, 2021

@jbergler could you modify /boot/armbianEnv.txt and add/modify following lines:

verbosity=7
console=serial
extraargs=earlyprintk ignore_loglevel

It should make the serial console more verbose and output the systemd services to serial.

Could you also post a step by step to set up and reproduce the crash?

maybe also the detail of ZFS pool and HDD model and size.

jbergler · March 16, 2021

@aprayoga verbosity was already up, but I've added the other args.

I'm not going to provoke the system since it's somewhat stable again and it's in use, but in terms of a repro here's the setup.

2x 8TB + 3x 12TB drives.

tank0 5x8TB raidz1

tank1 3x4TB raidz1 (this tank isn't mounted currently)

If I want to crash the box I can start a zfs scrub on tank0.
After some time (<~6 hours) the box crashes. On boot, if a scrub was in progress, box won't finish booting.

Spoiler

$ fdisk -l | grep model
Disk model: WDC WD120EMFZ-11
Disk model: WDC WD80EMAZ-00W
Disk model: WDC WD120EMFZ-11
Disk model: WDC WD120EMFZ-11
Disk model: WDC WD80EMAZ-00W

$ zpool status
pool: tank0
state: ONLINE
scan: scrub canceled on Mon Mar 15 20:26:12 2021
config:
   NAME                      STATE     READ WRITE CKSUM
   tank0                     ONLINE       0     0     0
      raidz1-0                ONLINE       0     0     0
        zfs-1b8007903f8d4b01 ONLINE       0     0     0
        zfs-946f51545d5dc02a ONLINE       0     0     0
        zfs-98b261f32fd8b393 ONLINE       0     0     0
        zfs-9b33bb254f272a96 ONLINE       0     0     0
        zfs-ff00f9d7b0840ce1 ONLINE       0     0     0

errors: No known data errors

pool: tank1
state: ONLINE
scan: scrub repaired 0B in 00:00:21 with 0 errors on Sun Mar 14 00:24:26 2021
config:
   NAME                      STATE     READ WRITE CKSUM
   tank1                     ONLINE       0     0     0
      raidz1-0                ONLINE       0     0     0
        zfs-e7174a8b87f51397 ONLINE       0     0     0
        zfs-ab22838b00580806 ONLINE       0     0     0
        zfs-c2dca7197e64a200 ONLINE       0     0     0

ShadowDance · March 16, 2021

@jbergler I recently noticed the armbian-hardware-optimization script for Helios64 changes the IO scheduler to `bfq` for spinning disks, however, for ZFS we should be using `none` because it has it's own scheduler. Normally ZFS would change the scheduler itself, but that would only happen if you're using raw disks (not partitions) and if you import the zpool _after_ the hardware optimization script has run.

You can try changing it (e.g. `echo none >/sys/block/sda/queue/scheduler`) for each ZFS disk and see if anything changes. I still haven't figured out if this is a cause for any problems, but it's worth a shot.

Seneca · March 16, 2021

On 3/12/2021 at 1:38 PM, Seneca said:

Just an update from yesterday, no freezes or crashes yet, even though quite heavy IO and CPU.

I've tried to provoke a system freeze with high cpu and IO, but it seems stable for now.

20:05:49 up 4 days, 23:47,  1 user,  load average: 0,14, 0,15, 0,11

I'll update this thread if the issue reoccurs.

SR-G · March 23, 2021

Okay so i got a freeze today, so even in my previous situation (as described in previous posts) it was not 100% stable (but still way better than at first).

SR-G · March 23, 2021

And a second freeze one hour after the first one (blinking red light), while upgrading the kernel. Now of course nothing boots up.

SR-G · March 25, 2021

And (after having lost 2 hours yesterday to reinstall the system), today : yet another freeze (this time with the latest image / kernel and default out-of-the-box configuration).

This really starts to be insane and nearly unusable.

SR-G · March 26, 2021

And another freeze this night (still with fresh install / latest kernel + modified boor.scr put back in place).

SR-G · March 28, 2021

Many additional freezes in the meanwhile.

Now (with latest kernel) i'm unable to have a stable situation whatever i do :

- latest kernel

- boot.scr put back

- same min and max freq

- governor on "performance" or "schedutil" or whatever

I always have freeze.

I'm at the point i'm about to be DISGUSTED by this NAS - i've never lost so much time with an electronic device.

What is the expected delay before having something stable for this NAS ?

Is it only worked on by KOBOL ?

How many people have a stable NAS versus an unstable NAS ?

Is my device faulty in any way ?

What is the refund policy on KOBOL ?

Seneca · March 28, 2021

I've had a 100% stable system for 16 days now, no cpufreq tweaks, only vanilla armbian config (+zram though).

17:32:07 up 16 days, 20:13,  1 user,  load average: 0,12, 0,17, 0,14

Using this kernel:

5.10.21-rockchip64

And I've _never_ gotten the red led blink when my system froze. Have you tried different or fewer drives?

flower · March 28, 2021

5 minutes ago, SR-G said:

What is the expected delay before having something stable for this NAS ?

Is it only worked on by KOBOL ?

How many people have a stable NAS versus an unstable NAS ?

Is my device faulty in any way ?

What is the refund policy on KOBOL ?

i gave up a few month ago.

however: i have a friend who is quite happy with his. omv/raid5 - nothing else.

i got mine somewhat stable by reducing cpu freq (same for min and max). but i do have huge stability requirements for my nas and also want it to run some services and so i have moved on.

sad for me. but i still think that there are good and working ones out there

SR-G · March 28, 2021

I've had a stable system (with previous kernel) for 30 days, then one freeze, then system corrupted, then reinstall everything, then now several freezes per day (at first with vanilla armbian config)

Same kernel than you :

Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux

I can't test different drives, i've 5 WD digital plugged in as a RAID5 array.

clostro · March 28, 2021

Mine has been pretty stable for the last 2 months. Last restart was to update to Armbian 21.02.2 Buster with 5.10.16 kernel 24 days ago. I applied the Cpu freq mod for the previous kernel, and upgraded with apt, no fresh install. Cpu freq mod is still in place I assume. Device has been completely stable since that mod, and I am not undoing it for the time being. Reliability > everything else.

I'm using the 2.5G port exclusively with a 2.5G switch.

There are 4 4TB Seagate Ironwolf drives and an old (very old) Sandisk Extreme SSD in there.

No OMV or ZFS. Just LVM Raid5 with SSD rw cache.

No docker or VMs running.

Cockpit for management.

Samba for file sharing.

Borg for backups.

gprovost · March 29, 2021

Honestly we don't know yet what the root cause of this difference of behavior.

Just to say we acknowledge that there are few boards that seems to not show improvement. We are not ignoring the issue and are still looking into it.

Vin · April 4, 2021

Mine is still crashing like a clockwork every 24 hours and leaves me generally with a corrupted OS and data.

I know you are a small team and you had to takle many obstacles to release the Helios64, believe me im a fan of your work, product and armbian in general, i m aware of the effort every involved person puts into this project.

But i would appreciate a bit more news about the current status of developement.

As far as i can see there is no status or developement overview on the current issues, not on your blog nor on twitter.

The only information we get are in various topics across the forum on armbian.

Is there a possibility to let us know more about the ongoing research and inform us about the progress and persued assumed solutions?

Also I wonder if those issues are genreal rk3399 gonvernor etc. problems, or if it applies specifically for the Helios64?

Thank you in advance for your reply.

gprovost · April 5, 2021

19 hours ago, Vin said:

I know you are a small team and you had to takle many obstacles to release the Helios64, believe me im a fan of your work, product and armbian in general, i m aware of the effort every involved person puts into this project.

But i would appreciate a bit more news about the current status of developement.

As far as i can see there is no status or developement overview on the current issues, not on your blog nor on twitter.

The only information we get are in various topics across the forum on armbian.

Yes sorry about the lack of centralized news on that stability improvement effort.

We don't want to confuse people by posting things when the effort is still ongoing, and that we still don't have a clear understanding why the instability issue only impact some of the boards.

19 hours ago, Vin said:

Also I wonder if those issues are genreal rk3399 gonvernor etc. problems, or if it applies specifically for the Helios64?

It is not an issue that impact all rk3399 boards. However same problems is impacting the NanoPi M4V2, and it's thanks to @piter75 work on the NanoPi that Helios64 stability has improved.

19 hours ago, Vin said:

Mine is still crashing like a clockwork every 24 hours and leaves me generally with a corrupted OS and data.

Are you running from eMMC or SDcard ?

Can you share some crash logs.

Sign In

Helios64 - freeze whatever the kernel is.

Question

Link to comment

Share on other sites

82 answers to this question

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Important Information