RlndVt Posted November 4, 2023 Share Posted November 4, 2023 Thanks. I went for armbian-firmware-full (and ran update-initramfs) using chroot. I'll have to see if my system boots tomorrow. I've noticed that the 'uboot' in armbian 23 throws an error about the unknown command `rm` IIRC. The 'uboot' used for armbian 22 does not show this message. Does anyone else recognise this? If the rebuilt 'uboot' throws that error again tomorrow I'll share the exact message here. 0 Quote Link to comment Share on other sites More sharing options...
RlndVt Posted November 5, 2023 Share Posted November 5, 2023 Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems registered: /dev/sdd registered: /dev/sdb registered: /dev/sde registered: /dev/sdc registered: /dev/sda done. Begin: Will now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 armbi_root: clean, 56356/1891776 files, 967727/7708672 blocks done. done. Begin: Running /scripts/local-bottom ... /scripts/local-bottom/mdadm: 2: /scripts/local-bottom/mdadm: rm: not found done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.8.3 bookworm! [...] Starting networking.service - Raise network interfaces... [ 16.458082] Internal error: Oops - Undefined instruction: 0000000002000000 [#1] PREEMPT SMP [ 16.458852] Modules linked in: ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_multiport xt_comment lz4hc nft_limit lz4 leds_pwm gpio_charger pwm_fan rockchip_vdec(C) hantro_vpu panfrost snd_soc_hdmi_codec snd_soc_rockchip_i2s v4l2_vp9 videobuf2_dma_contig v4l2_h264 rockchip_rga gpu_sched xt_limit drm_shmem_helper rockchip_rng snd_soc_core xt_addrtype videobuf2_dma_sg v4l2_mem2mem rng_core snd_compress videobuf2_memops snd_pcm_dmaengine xt_tcpudp videobuf2_v4l2 snd_pcm binfmt_misc videobuf2_common xt_conntrack videodev nf_conntrack snd_timer nf_defrag_ipv6 mc snd nf_defrag_ipv4 nft_compat soundcore nf_tables nfnetlink zram gpio_beeper cpufreq_dt sg ledtrig_netdev lm75 nfsd auth_rpcgss nfs_acl lockd grace dm_mod sunrpc ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod realtek fusb302 tcpm dwmac_rk stmmac_platform stmmac typec pcs_xpcs adc_keys [ 16.466751] CPU: 5 PID: 0 Comm: swapper/5 Tainted: G C 6.1.50-current-rockchip64 #3 [ 16.467567] Hardware name: Helios64 (DT) [ 16.467920] pstate: 200000c5 (nzCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 16.468542] pc : __this_cpu_preempt_check+0x24/0x40 [ 16.468996] lr : ct_nmi_exit+0x80/0x280 [ 16.469348] sp : ffff800009ef3be0 [ 16.469647] x29: ffff800009ef3be0 x28: ffff000000762d00 x27: 0000000000000000 [ 16.470292] x26: ffff000000762d00 x25: 0000000000000000 x24: 0000000000000000 [ 16.470934] x23: ffff0000f779e8f0 x22: ffff800009a3dc70 x21: ffff8000094ea818 [ 16.471575] x20: ffff800009766900 x19: ffff8000097668f0 x18: 0000000000000000 [ 16.472215] x17: ffff8000ee038000 x16: ffff800009d20000 x15: 0000000000000000 [ 16.472857] x14: 0000000000000000 x13: 0000000000000303 x12: 0000000000000000 [ 16.473501] x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000f77a1f80 [ 16.474142] x8 : 0000000000000005 x7 : ffff0000f77a28f8 x6 : 00000000ffffffff [ 16.474781] x5 : ffff80000959a7e0 x4 : 0000000000000001 x3 : ffff800009757008 [ 16.475422] x2 : ffff000000762d00 x1 : ffff8000094ea818 x0 : 0000000000000005 [ 16.476063] Call trace: [ 16.476286] __this_cpu_preempt_check+0x24/0x40 [ 16.476700] ct_irq_exit+0x10/0x80 [ 16.477014] exit_to_kernel_mode.isra.0+0x20/0x2c [ 16.477440] el1_interrupt+0x58/0x6c [ 16.477766] el1h_64_irq_handler+0x18/0x2c [ 16.478139] el1h_64_irq+0x64/0x68 [ 16.478450] arch_cpu_idle+0x18/0x2c [ 16.478778] default_idle_call+0x38/0x17c [ 16.479143] do_idle+0x23c/0x2b0 [ 16.479442] cpu_startup_entry+0x24/0x30 [ 16.479800] secondary_start_kernel+0x124/0x150 [ 16.480221] __secondary_switched+0xb0/0xb4 [ 16.480627] Code: 9115e040 97ffffa6 a8c17bfd d50323bf (d65f03c0) [ 16.481180] ---[ end trace 0000000000000000 ]--- [ 16.481594] Kernel panic - not syncing: Attempted to kill the idle task! [ 16.482189] SMP: stopping secondary CPUs [ 16.482555] Kernel Offset: disabled [ 16.482869] CPU features: 0x40000,20824084,0000421b [ 16.483308] Memory Limit: none [ 16.483592] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- No luck, see kernel panic above. The missing command can be seen below; `Unknown command 'kaslrseed' - try 'help'`: U-Boot 2022.07-armbian (Aug 22 2023 - 15:26:42 +0000) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 Core: 339 devices, 31 uclasses, devicetree: separate SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: dw_dm_mdio_init: mdio node is missing, registering legacy mdio busNo ethernet found. scanning bus for devices... Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3252 bytes read in 5 ms (634.8 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 166 bytes read in 4 ms (40 KiB/s) 24417797 bytes read in 1036 ms (22.5 MiB/s) 29792768 bytes read in 1264 ms (22.5 MiB/s) 86670 bytes read in 12 ms (6.9 MiB/s) 2698 bytes read in 8 ms (329.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=3f00000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 24417733 Bytes = 23.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f4794000, end f5edd5c5 ... OK Loading Device Tree to 00000000f4716000, end 00000000f4793fff ... OK Starting kernel ... 1 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 5, 2023 Author Share Posted November 5, 2023 44 minutes ago, RlndVt said: Unknown command 'kaslrseed' - try 'help' That is most likely a bug in that version of u-boot. The solution is to flash another bootloader as shown earlier in this thread. 0 Quote Link to comment Share on other sites More sharing options...
0x349850341010010101010100 Posted November 5, 2023 Share Posted November 5, 2023 @RlndVt that is actually the same kernel panic was getting at times. But I was also not able to apply the fix. So if it is really related to the realtek driver that makes sense. 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 5, 2023 Author Share Posted November 5, 2023 (edited) Using linux kernel 6.1.60 and linux-u-boot-current-helios64_21.08.9_arm64 (and rtl_nic firmware from git.kernel.org) such kernel panics cannot be reproduced here (booting from emmc). @RlndVt You are on Armbian 23.08.3 - 6.1.50 (dwc3-usb regression) without rtl_nic firmware from git.kernel.org and it is not stable. Does the problem also occur if you use Armbian 23.05.4 - 6.1.36 ? # cat /var/log/syslog | grep network 2023-11-05T08:40:06.350431+01:00 kernel: [ 2.161445] drop_monitor: Initializing network drop monitor service 2023-11-05T08:40:06.353126+01:00 systemd-networkd[449]: lo: Link UP 2023-11-05T08:40:06.353139+01:00 systemd-networkd[449]: lo: Gained carrier 2023-11-05T08:40:06.353149+01:00 systemd-networkd[449]: Enumeration completed 2023-11-05T08:40:06.353161+01:00 systemd-networkd[449]: end1: Configuring with /etc/systemd/network/end1.network. 2023-11-05T08:40:06.353177+01:00 systemd-networkd[449]: end0: Configuring with /etc/systemd/network/end0.network. 2023-11-05T08:40:06.353187+01:00 systemd-networkd[449]: end1: Link UP 2023-11-05T08:40:06.353197+01:00 systemd-networkd[449]: end0: Link UP 2023-11-05T08:40:06.353208+01:00 systemd-networkd[449]: end1: Link DOWN 2023-11-05T08:40:06.353247+01:00 systemd-networkd[449]: eth0: Interface name change detected, renamed to end1. 2023-11-05T08:40:06.353258+01:00 systemd-networkd[449]: end1: Configuring with /etc/systemd/network/end1.network. 2023-11-05T08:40:06.353268+01:00 systemd-networkd[449]: end1: Link UP 2023-11-05T08:40:06.356372+01:00 systemd-networkd[449]: end1: Gained carrier 2023-11-05T08:40:06.356496+01:00 systemd-networkd[449]: end1: DHCPv4 address 192.168.xx.xx/24, gateway 192.168.xx.xx acquired from 192.168.xx.xx 2023-11-05T08:40:06.430434+01:00 systemd[1]: Started vnstat.service - vnStat network traffic monitor. 2023-11-05T08:40:06.858858+01:00 systemd[1]: Starting helios64-heartbeat-led.service - Enable heartbeat & network activity led on Helios64... 2023-11-05T08:40:07.205052+01:00 systemd[1]: Finished helios64-heartbeat-led.service - Enable heartbeat & network activity led on Helios64. 2023-11-05T08:40:07.900568+01:00 systemd-networkd[449]: end1: Gained IPv6LL 2023-11-05T08:40:22.426376+01:00 systemd[2380]: Listening on dirmngr.socket - GnuPG network certificate management daemon. Edited November 6, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 6, 2023 Author Share Posted November 6, 2023 (edited) Helios64 archives (i.e. this one) have been wiped and the only image available is Armbian 23.08.1 - 6.1.50, the useless one with the dwc3-usb regression. @Igor Would you please revert the Armbian images linked on the Helios64 download page back to Armbian bookworm and jammy 23.05.4 - 6.1.36 ? The only place where I can still find those images for the ultimate ARM powered NAS is on this mirror. (I would help out doing that as well). Edited November 6, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 6, 2023 Author Share Posted November 6, 2023 (edited) The performance of the setup based on Armbian bookworm 23.05.4 is very impressive for a three year old NAS: using iperf3 measurements as a stress test, data transfer in both directions between server and client max out at 2.34 Gbit/s using the 2.5G interface (see the first and second iperf3 run below). This is currently not the case if data is transferred bidirectional at the same time (2.5G full duplex, see the third iperf3 run below). iperf3 speed tests % ./iperf3 -c 192.168.xxxx -p 5201 Connecting to host 192.168.xxxx, port 5201 [ 5] local 192.168.xxxx port 50917 connected to 192.168.xxxx port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 268 MBytes 2.25 Gbits/sec [ 5] 1.00-2.00 sec 281 MBytes 2.36 Gbits/sec [ 5] 2.00-3.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 3.00-4.00 sec 278 MBytes 2.33 Gbits/sec [ 5] 4.00-5.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 5.00-6.00 sec 279 MBytes 2.34 Gbits/sec [ 5] 6.00-7.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 7.00-8.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 8.00-9.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 9.00-10.00 sec 280 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 2.72 GBytes 2.34 Gbits/sec sender [ 5] 0.00-10.00 sec 2.72 GBytes 2.34 Gbits/sec receiver iperf Done. % ./iperf3 -c 192.168.xxxx -p 5201 -R Connecting to host 192.168.xxxx, port 5201 Reverse mode, remote host 192.168.xxxx is sending [ 5] local 192.168.xxxx port 49235 connected to 192.168.xxxx port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 251 MBytes 2.11 Gbits/sec [ 5] 1.00-2.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 2.00-3.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 3.00-4.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 4.00-5.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 5.00-6.00 sec 280 MBytes 2.34 Gbits/sec [ 5] 6.00-7.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 7.00-8.00 sec 279 MBytes 2.34 Gbits/sec [ 5] 8.00-9.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 9.00-10.00 sec 280 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 2.71 GBytes 2.33 Gbits/sec sender [ 5] 0.00-10.00 sec 2.70 GBytes 2.32 Gbits/sec receiver iperf Done. % ./iperf3 -c 192.168.xx.xx -p 5201 --bidir Connecting to host 192.168.xx.xx, port 5201 [ 5] local 192.168.xx.xx port 49292 connected to 192.168.xx.xx port 5201 [ 7] local 192.168.xx.xx port 49293 connected to 192.168.xx.xx port 5201 [ ID][Role] Interval Transfer Bitrate [ 5][TX-C] 0.00-1.00 sec 54.1 MBytes 454 Mbits/sec [ 7][RX-C] 0.00-1.00 sec 203 MBytes 1.71 Gbits/sec [ 5][TX-C] 1.00-2.00 sec 25.3 MBytes 212 Mbits/sec [ 7][RX-C] 1.00-2.00 sec 250 MBytes 2.10 Gbits/sec [ 5][TX-C] 2.00-3.00 sec 24.7 MBytes 208 Mbits/sec [ 7][RX-C] 2.00-3.00 sec 249 MBytes 2.09 Gbits/sec [ 5][TX-C] 3.00-4.00 sec 25.0 MBytes 210 Mbits/sec [ 7][RX-C] 3.00-4.00 sec 249 MBytes 2.09 Gbits/sec [ 5][TX-C] 4.00-5.00 sec 25.0 MBytes 210 Mbits/sec [ 7][RX-C] 4.00-5.00 sec 249 MBytes 2.09 Gbits/sec [ 5][TX-C] 5.00-6.00 sec 24.8 MBytes 208 Mbits/sec [ 7][RX-C] 5.00-6.00 sec 249 MBytes 2.09 Gbits/sec [ 5][TX-C] 6.00-7.00 sec 25.0 MBytes 210 Mbits/sec [ 7][RX-C] 6.00-7.00 sec 249 MBytes 2.09 Gbits/sec [ 5][TX-C] 7.00-8.00 sec 25.0 MBytes 209 Mbits/sec [ 7][RX-C] 7.00-8.00 sec 250 MBytes 2.10 Gbits/sec [ 5][TX-C] 8.00-9.00 sec 25.0 MBytes 210 Mbits/sec [ 7][RX-C] 8.00-9.00 sec 249 MBytes 2.09 Gbits/sec [ 5][TX-C] 9.00-10.00 sec 25.0 MBytes 210 Mbits/sec [ 7][RX-C] 9.00-10.00 sec 250 MBytes 2.09 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID][Role] Interval Transfer Bitrate Retr [ 5][TX-C] 0.00-10.00 sec 279 MBytes 234 Mbits/sec sender [ 5][TX-C] 0.00-10.00 sec 273 MBytes 229 Mbits/sec receiver [ 7][RX-C] 0.00-10.00 sec 2.39 GBytes 2.05 Gbits/sec sender [ 7][RX-C] 0.00-10.00 sec 2.39 GBytes 2.05 Gbits/sec receiver iperf Done. Edited November 6, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
RlndVt Posted November 6, 2023 Share Posted November 6, 2023 21 hours ago, ebin-dev said: Using linux kernel 6.1.60 and linux-u-boot-current-helios64_21.08.9_arm64 (and rtl_nic firmware from git.kernel.org) such kernel panics cannot be reproduced here (booting from emmc). Did you manually build 6.1.60? I don't see it available through the package manager. I'll try the custom u-boot build. I'm booting from an SD-card. 21 hours ago, ebin-dev said: without rtl_nic firmware from git.kernel.org FWIW, as I mention I installed armbian-firmware-full which includes 'rtl8156a-2.fw'. The md5sum matches from git.kernel.org. 22 hours ago, 0x349850341010010101010100 said: @RlndVt that is actually the same kernel panic was getting at times. But I was also not able to apply the fix. So if it is really related to the realtek driver that makes sense. Glad to hear I'm not alone :). 21 hours ago, ebin-dev said: Does the problem also occur if you use Armbian 23.05.4 - 6.1.36 ? I'll try that soon. I'm guessing that will work because I had been running Armbian 23 for a month till a 'recent' update/broke my system. 22 hours ago, ebin-dev said: 23 hours ago, RlndVt said: Unknown command 'kaslrseed' - try 'help' That is most likely a bug in that version of u-boot. The solution is to flash another bootloader as shown earlier in this thread. Is apparently a intentional change. (I'm assuming that) The error message is the 'gracefully skips' mentioned in the PR. https://github.com/armbian/build/pull/4352 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 6, 2023 Author Share Posted November 6, 2023 (edited) 4 hours ago, RlndVt said: Did you manually build 6.1.60? I don't see it available through the package manager. I'll try the custom u-boot build. I'm booting from an SD-card. Yes - I built 6.1.60 and made it available in this thread for the ones who also need kernel plus matching linux-headers. But I would prefer to stay on Armbian 23.05.4 - 6.1.36. Edited November 6, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
RlndVt Posted November 7, 2023 Share Posted November 7, 2023 (edited) I reverted linux-image-current-rockchip64 to 23.02.2 (5.15.93-rockchip64) and my system booted. For me some extra confirmation that the problem lies in the kernel version. I did see the same kaslrseed message which I'm ignoring for now. $ apt-cache policy linux-image-current-rockchip64 linux-image-current-rockchip64: Installed: 23.02.2 Candidate: 23.8.1 Version table: 23.8.1 500 500 http://apt.armbian.com bookworm/main arm64 Packages *** 23.02.2 500 500 http://apt.armbian.com bookworm/main arm64 Packages 100 /var/lib/dpkg/status @ebin-dev, could you explain how you built the newer kernel versions? Or point me to a resource that can help me along? I'm hesitant about flashing 6.1.36 as I would like to avoid reconfiguring the install. EDIT: Building the required packages is apparently trivial: `git clone https://github.com/armbian/build` and a `./compile.sh`. The result does however still seem to be missing the required patches. I'm now looking into how to get the right patches into the right place, would love some help. Edited November 7, 2023 by RlndVt Expand on building the kernel. 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 7, 2023 Author Share Posted November 7, 2023 4 hours ago, RlndVt said: @ebin-dev, could you explain how you built the newer kernel versions? Or point me to a resource that can help me along? I'm hesitant about flashing 6.1.36 as I would like to avoid reconfiguring the install. There are three kernel versions 6.1.58, 6.1.60 and 6.6.0. I am currently using 6.1.58 and bootloader linux-u-boot-current-helios64_21.08.9_arm64 flashed to emmc/sd. In 6.1.58 the dwc3-usb regression is patched. All versions boot nicely but their performance in combination with the r8152 driver vary. (Install with 'dpkg -i linux*') 0 Quote Link to comment Share on other sites More sharing options...
RlndVt Posted November 7, 2023 Share Posted November 7, 2023 FWIW 23.02.2/5.15.93 crashes on shutdown. [ OK ] Reached target reboot.target - System Reboot. [10787.888857] watchdog: watchdog0: watchdog did not stop! [10788.208644] xhci-hcd xhci-hcd.3.auto: Host halt failed, -110 [10788.209246] ------------[ cut here ]------------ [10788.209658] WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/drm_modeset_lock.c:266 drm_modeset_lock+0xe4/0x108 [10788.210510] Modules linked in: rfkill ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables binfmt_misc ip6t_rt ipt_REJECT leds_pwm gpio_charger nf_reject_ipv4 xt_LOG pwm_fan panfrost snd_soc_hdmi_codec snd_soc_rockchip_i2s gpu_sched nf_log_syslog snd_soc_rockchip_pcm xt_multiport snd_soc_core hantro_vpu(C) rockchip_vdec(C) rockchip_rga xt_comment rockchip_iep v4l2_h264 snd_pcm_dmaengine videobuf2_dma_contig videobuf2_dma_sg videobuf2_vmalloc v4l2_mem2mem nft_limit snd_pcm videobuf2_memops videobuf2_v4l2 snd_timer xt_limit videobuf2_common xt_addrtype snd lz4hc videodev lz4 mc soundcore xt_tcpudp xt_conntrack nf_conntrack gpio_beeper cpufreq_dt nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nft_counter sg nf_tables nfnetlink zram nfsd auth_rpcgss nfs_acl lockd grace ledtrig_netdev lm75 sunrpc dm_mod ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod r8152 realtek cdc_ncm cdc_ether usbnet fusb302 tcpm dwmac_rk typec [10788.210772] stmmac_platform stmmac pcs_xpcs adc_keys [10788.218830] CPU: 1 PID: 1 Comm: systemd-shutdow Tainted: G C 5.15.93-rockchip64 #23.02.2 [10788.219659] Hardware name: Helios64 (DT) [10788.220009] pstate: a0000005 (NzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [10788.220626] pc : drm_modeset_lock+0xe4/0x108 [10788.221010] lr : drm_modeset_lock+0x40/0x108 [10788.221393] sp : ffff800009e1bb50 [10788.221689] x29: ffff800009e1bb50 x28: ffff000000680000 x27: 0000000000000000 [10788.222326] x26: ffff000000fce490 x25: ffff8000094bfc80 x24: 0000000000000008 [10788.222962] x23: ffff800009d38050 x22: ffff000008bcf000 x21: ffff8000095504a8 [10788.223599] x20: ffff000008bcf188 x19: ffff800009e1bbe0 x18: 0000000000000010 [10788.224236] x17: 0000000000000000 x16: 0000000000000000 x15: 000000000000035d [10788.224872] x14: ffff800009e1b800 x13: 00000000ffffffea x12: ffff800009b2fe58 [10788.225509] x11: 0000000000000003 x10: ffff800009b17e18 x9 : ffff800009e1bb88 [10788.226145] x8 : ffff800009e1bbb0 x7 : ffff800009e1bbb0 x6 : 0000000000000001 [10788.226781] x5 : 0000000000000000 x4 : ffff800009e1bbe0 x3 : ffff000008bcf188 [10788.227418] x2 : 0000000000000000 x1 : ffff000008bcf1b0 x0 : 0000000000000000 [10788.228055] Call trace: [10788.228276] drm_modeset_lock+0xe4/0x108 [10788.228629] drm_modeset_lock_all_ctx+0x28/0xf8 [10788.229037] drm_atomic_helper_shutdown+0x74/0x130 [10788.229468] rockchip_drm_platform_shutdown+0x18/0x28 [10788.229921] platform_shutdown+0x24/0x38 [10788.230275] device_shutdown+0x148/0x240 [10788.230629] kernel_restart_prepare+0x38/0x48 [10788.231023] kernel_restart+0x18/0x68 [10788.231353] __do_sys_reboot+0x220/0x248 [10788.231706] __arm64_sys_reboot+0x24/0x30 [10788.232067] invoke_syscall+0x44/0x108 [10788.232407] el0_svc_common.constprop.3+0x94/0xf8 [10788.232828] do_el0_svc+0x24/0x98 [10788.233127] el0_svc+0x20/0x50 [10788.233406] el0t_64_sync_handler+0x90/0xb8 [10788.233780] el0t_64_sync+0x180/0x184 [10788.234110] ---[ end trace 744dd2aea6b1d549 ]--- [10788.234544] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018 [10788.235352] Mem abort info: [10788.235618] ESR = 0x0000000096000004 [10788.235950] EC = 0x25: DABT (current EL), IL = 32 bits [10788.236417] SET = 0, FnV = 0 [10788.236687] EA = 0, S1PTW = 0 [10788.236964] FSC = 0x04: level 0 translation fault [10788.237391] Data abort info: [10788.237645] ISV = 0, ISS = 0x00000004 [10788.237981] CM = 0, WnR = 0 [10788.238244] user pgtable: 4k pages, 48-bit VAs, pgdp=00000000096eb000 [10788.238809] [0000000000000018] pgd=0000000000000000, p4d=0000000000000000 [10788.239408] Internal error: Oops: 96000004 [#1] PREEMPT SMP [10788.239898] Modules linked in: rfkill ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables binfmt_misc ip6t_rt ipt_REJECT leds_pwm gpio_charger nf_reject_ipv4 xt_LOG pwm_fan panfrost snd_soc_hdmi_codec snd_soc_rockchip_i2s gpu_sched nf_log_syslog snd_soc_rockchip_pcm xt_multiport snd_soc_core hantro_vpu(C) rockchip_vdec(C) rockchip_rga xt_comment rockchip_iep v4l2_h264 snd_pcm_dmaengine videobuf2_dma_contig videobuf2_dma_sg videobuf2_vmalloc v4l2_mem2mem nft_limit snd_pcm videobuf2_memops videobuf2_v4l2 snd_timer xt_limit videobuf2_common xt_addrtype snd lz4hc videodev lz4 mc soundcore xt_tcpudp xt_conntrack nf_conntrack gpio_beeper cpufreq_dt nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nft_counter sg nf_tables nfnetlink zram nfsd auth_rpcgss nfs_acl lockd grace ledtrig_netdev lm75 sunrpc dm_mod ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod r8152 realtek cdc_ncm cdc_ether usbnet fusb302 tcpm dwmac_rk typec [10788.240040] stmmac_platform stmmac pcs_xpcs adc_keys [10788.248043] CPU: 4 PID: 1 Comm: systemd-shutdow Tainted: G WC 5.15.93-rockchip64 #23.02.2 [10788.248864] Hardware name: Helios64 (DT) [10788.249209] pstate: a0000005 (NzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [10788.249819] pc : ww_mutex_lock+0x54/0x88 [10788.250170] lr : drm_modeset_lock+0x40/0x108 [10788.250549] sp : ffff800009e1bb40 [10788.250841] x29: ffff800009e1bb40 x28: ffff000000680000 x27: 0000000000000000 [10788.251470] x26: ffff000000fce490 x25: ffff8000094bfc80 x24: 0000000000000008 [10788.252098] x23: 0000000000000000 x22: ffff000008bcf000 x21: ffff000008bcf2d8 [10788.252724] x20: 0000000000000018 x19: ffff800009e1bbe0 x18: 0000000000000010 [10788.253351] x17: 0000000000000000 x16: 0000000000000000 x15: 000000000000035d [10788.253979] x14: ffff800009e1b800 x13: 00000000ffffffea x12: ffff800009b2fe58 [10788.254607] x11: 0000000000000003 x10: ffff800009b17e18 x9 : ffff800009e1bb88 [10788.255234] x8 : ffff800009e1bbb0 x7 : ffff800009e1bbb0 x6 : 0000000000000001 [10788.255862] x5 : 0000000000000000 x4 : ffff800009e1bbe0 x3 : 0000000000000018 [10788.256489] x2 : ffff000000680000 x1 : 0000000000000000 x0 : 0000000000000018 [10788.257117] Call trace: [10788.257334] ww_mutex_lock+0x54/0x88 [10788.257651] drm_modeset_lock+0x40/0x108 [10788.257999] drm_modeset_lock_all_ctx+0x64/0xf8 [10788.258399] drm_atomic_helper_shutdown+0x74/0x130 [10788.258823] rockchip_drm_platform_shutdown+0x18/0x28 [10788.259269] platform_shutdown+0x24/0x38 [10788.259616] device_shutdown+0x148/0x240 [10788.259963] kernel_restart_prepare+0x38/0x48 [10788.260349] kernel_restart+0x18/0x68 [10788.260673] __do_sys_reboot+0x220/0x248 [10788.261021] __arm64_sys_reboot+0x24/0x30 [10788.261375] invoke_syscall+0x44/0x108 [10788.261708] el0_svc_common.constprop.3+0x94/0xf8 [10788.262123] do_el0_svc+0x24/0x98 [10788.262418] el0_svc+0x20/0x50 [10788.262689] el0t_64_sync_handler+0x90/0xb8 [10788.263058] el0t_64_sync+0x180/0x184 [10788.263384] Code: d50323bf d65f03c0 d2800001 f9800071 (c85ffc60) [10788.263920] ---[ end trace 744dd2aea6b1d54a ]--- [10788.264346] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [10788.265021] Kernel Offset: disabled [10788.265329] CPU features: 0x800820b1,20000846 [10788.265713] Memory Limit: none [10788.265988] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- U-Boot TPL 2022.07-armbian (Aug 22 2023 - 15:26:42) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB Channel 1: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB 256B stride lpddr4_set_rate: change freq to 400000000 mhz 0, 1 lpddr4_set_rate: change freq to 800000000 mhz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2022.07-armbian (Aug 22 2023 - 15:26:42 +0000) Trying to boot from MMC1 mmc_load_image_raw_sector: mmc block read error Trying to boot from SPI Trying to boot from MMC1 mmc_load_image_raw_sector: mmc block read error Trying to boot from MMC2 mmc_load_image_raw_sector: mmc block read error SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### 0 Quote Link to comment Share on other sites More sharing options...
RlndVt Posted November 7, 2023 Share Posted November 7, 2023 (edited) 38 minutes ago, ebin-dev said: There are three kernel versions 6.1.58, 6.1.60 and 6.6.0. Thanks, I've installed 6.1.58; but got the same kernel problem as previously on my second boot. (First and third were okay.) I'm going to try the 6.6.0 version now. (E: 6.6.0 had two kernel crashes but booted on the third.) Could you share how you patched 6.1.xx versions? Edited November 7, 2023 by RlndVt 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 7, 2023 Author Share Posted November 7, 2023 (edited) New Armbian build system: ./compile.sh kernel-patch <board etc> # this allows you to modify the source during a pause and then compiles the corresponding patch ./comile.sh kernel <board etc> # this compiles kernel only, copy patch to be applied here: ./build/patch/kernel/archive/rockchip64-6.1 What may happen is that the watchdog timer has to reset the r8152 driver (mainline v1.12.13) under heavy loads (the higher the kernel version, the more likely) I do not observe any kernel crashes on boot with any of the kernels 6.1.36, 6.1.58, 6.1.60 and 6.6.0 starting from Armbian 23.05.4 and using one of the two bootloaders as discussed earlier. On the other side, I really had problems after installing Armbian full firmware and the current bootloader - and the only way out was to start from scratch. Good luck ! P.S.: The dwc3-usb regression is fixed upstream in linux 6.1.59 and later. Edited November 13, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 10, 2023 Author Share Posted November 10, 2023 (edited) @RlndVt Did you have any results compiling a kernel for your Helios or testing the Armbian 23.5.4 - 6.1.36 Image ? P.S.: How to build Armbian is described here. But the system has changed and the new build system is not documented (yet). The important bits are those: ./compile.sh kernel-patch <board etc> # this allows you to modify the source during a pause and then compiles the corresponding patch ./comile.sh kernel <board etc> # this compiles kernel only, copy patch to be applied here: ./build/patch/kernel/archive/rockchip64-6.1 The dwc3-usb regression is anyway fixed in all linux kernels starting from 6.1.59. Edited November 12, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 11, 2023 Author Share Posted November 11, 2023 (edited) Armbian bookworm 23.05.4 with linux downgraded to 5.10.43 seems to be the perfect setup (if you need linux-headers). It runs absolutely stable during stress tests using linux-u-boot-current-helios64_21.08.9_arm64 or linux-u-boot-edge-helios64_22.02.1_arm64. This kernel is the last one with hs400 support: emmc is accessed with 230MB/s. The fans don't spin up during boot but start slowly. However, it seems that RAM access is a little bit slower (timed cache reads) but what matters is stability. P.S.: If you downgrade from linux 6.x to linux 5.x all symlinks vmlinux* and uInitrd* should be deleted in the root directory / before reboot. _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 23.08.0-trunk Bookworm with Linux 5.10.43-rockchip64 No end-user support: community creations System load: 2% Up time: 12 min Memory usage: 29% of 3.77G IP: 192.168.xx.yy CPU temp: 46°C Usage of /: 46% of 15G storage/: 62% of 3.6T storage temp: 25°C # modinfo r8152 filename: /lib/modules/5.10.43-rockchip64/kernel/drivers/net/usb/r8152.ko version: v2.14.0 (2020/09/24) license: GPL description: Realtek RTL8152/RTL8153 Based USB Ethernet Adapters author: Realtek nic sw <nic_swsd@realtek.com> # hdparm -tT /dev/mmcblk2p1 /dev/mmcblk2p1: Timing cached reads: 2180 MB in 2.00 seconds = 1089.64 MB/sec Timing buffered disk reads: 714 MB in 3.01 seconds = 237.50 MB/sec % ./iperf3 -c 192.168.xx.30 -p 5201 Connecting to host 192.168.xx.30, port 5201 [ 5] local 192.168.xx.45 port 49517 connected to 192.168.xx.30 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 228 MBytes 1.91 Gbits/sec [ 5] 1.00-2.00 sec 281 MBytes 2.36 Gbits/sec [ 5] 2.00-3.00 sec 266 MBytes 2.23 Gbits/sec [ 5] 3.00-4.00 sec 248 MBytes 2.08 Gbits/sec [ 5] 4.00-5.00 sec 248 MBytes 2.08 Gbits/sec [ 5] 5.00-6.00 sec 245 MBytes 2.05 Gbits/sec [ 5] 6.00-7.00 sec 252 MBytes 2.11 Gbits/sec [ 5] 7.00-8.00 sec 270 MBytes 2.26 Gbits/sec [ 5] 8.00-9.00 sec 264 MBytes 2.22 Gbits/sec [ 5] 9.00-10.00 sec 249 MBytes 2.09 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 2.49 GBytes 2.14 Gbits/sec sender [ 5] 0.00-10.00 sec 2.48 GBytes 2.13 Gbits/sec receiver iperf Done. % ./iperf3 -c 192.168.xx.30 -p 5201 -R Connecting to host 192.168.xx.30, port 5201 Reverse mode, remote host 192.168.xx.30 is sending [ 5] local 192.168.xx.45 port 49520 connected to 192.168.xx.30 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 259 MBytes 2.17 Gbits/sec [ 5] 1.00-2.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 2.00-3.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 3.00-4.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 4.00-5.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 5.00-6.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 6.00-7.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 7.00-8.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 8.00-9.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 9.00-10.00 sec 280 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 2.72 GBytes 2.34 Gbits/sec 15 sender [ 5] 0.00-10.00 sec 2.72 GBytes 2.33 Gbits/sec receiver iperf Done. % ./iperf3 -c 192.168.xx.30 -p 5201 --bidir Connecting to host 192.168.xx.30, port 5201 [ 5] local 192.168.xx.45 port 49541 connected to 192.168.xx.30 port 5201 [ 7] local 192.168.xx.45 port 49542 connected to 192.168.xx.30 port 5201 [ ID][Role] Interval Transfer Bitrate [ 5][TX-C] 0.00-1.00 sec 257 MBytes 2.16 Gbits/sec [ 7][RX-C] 0.00-1.00 sec 116 MBytes 977 Mbits/sec [ 5][TX-C] 1.00-2.00 sec 58.5 MBytes 491 Mbits/sec [ 7][RX-C] 1.00-2.00 sec 280 MBytes 2.35 Gbits/sec [ 5][TX-C] 2.00-3.00 sec 60.9 MBytes 511 Mbits/sec [ 7][RX-C] 2.00-3.00 sec 280 MBytes 2.35 Gbits/sec [ 5][TX-C] 3.00-4.00 sec 51.8 MBytes 435 Mbits/sec [ 7][RX-C] 3.00-4.00 sec 280 MBytes 2.35 Gbits/sec [ 5][TX-C] 4.00-5.00 sec 138 MBytes 1.16 Gbits/sec [ 7][RX-C] 4.00-5.00 sec 205 MBytes 1.72 Gbits/sec [ 5][TX-C] 5.00-6.00 sec 58.0 MBytes 486 Mbits/sec [ 7][RX-C] 5.00-6.00 sec 280 MBytes 2.35 Gbits/sec [ 5][TX-C] 6.00-7.00 sec 50.2 MBytes 421 Mbits/sec [ 7][RX-C] 6.00-7.00 sec 279 MBytes 2.34 Gbits/sec [ 5][TX-C] 7.00-8.00 sec 74.2 MBytes 622 Mbits/sec [ 7][RX-C] 7.00-8.00 sec 259 MBytes 2.17 Gbits/sec [ 5][TX-C] 8.00-9.00 sec 116 MBytes 974 Mbits/sec [ 7][RX-C] 8.00-9.00 sec 225 MBytes 1.89 Gbits/sec [ 5][TX-C] 9.00-10.00 sec 190 MBytes 1.59 Gbits/sec [ 7][RX-C] 9.00-10.00 sec 172 MBytes 1.45 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID][Role] Interval Transfer Bitrate Retr [ 5][TX-C] 0.00-10.00 sec 1.03 GBytes 885 Mbits/sec sender [ 5][TX-C] 0.00-10.00 sec 1.02 GBytes 879 Mbits/sec receiver [ 7][RX-C] 0.00-10.00 sec 2.32 GBytes 2.00 Gbits/sec 7 sender [ 7][RX-C] 0.00-10.00 sec 2.32 GBytes 1.99 Gbits/sec receiver iperf Done. dmesg.txt Edited November 13, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 14, 2023 Author Share Posted November 14, 2023 (edited) So far all my attempts to use the mainline driver r8152 in recent kernels 6.1.x and 6.6.y were accompanied by the system having to reset the driver on heavy loads. (My apologies to @RlndVt and @0x349850341010010101010100 - the mainline r8152 driver indeed causes problems) My attempts to replace the r8152 mainline driver by a recent version from Realtek (v.2.17.1) in linux kernels 6.1.xx and in 6.6.xx were accompanied by crashes. The logical solution now was to step back to linux 5.10.43 (Realtek driver v2.14.0 (2020/09/24)) also used with Debian bullseye before. After some performance tuning, network performance is now outstanding with that system (Armbian bookworm 23.05.4, linux downgraded to 5.10.43, linux-u-boot-edge-helios64_22.02.1_arm64, content of /lib/firmware/rtl_nic replaced by this firmware) (Bitrates bidirectional: 2.28+1.54=3.82Gb/s; Transfer bidirectional 2.65+1.80=4.45 GBytes transferred in 10s) P.S.: Performance optimised using sbc-bench - the famous tool from @tkaiser - and by changing the task affinity of iperf3. ./iperf3 -c 192.168.xx.30 -p 5201 Connecting to host 192.168.xx.30, port 5201 [ 5] local 192.168.xx.45 port 52050 connected to 192.168.xx.30 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 241 MBytes 2.02 Gbits/sec [ 5] 1.00-2.00 sec 242 MBytes 2.03 Gbits/sec [ 5] 2.00-3.00 sec 234 MBytes 1.97 Gbits/sec [ 5] 3.00-4.00 sec 271 MBytes 2.28 Gbits/sec [ 5] 4.00-5.00 sec 269 MBytes 2.26 Gbits/sec [ 5] 5.00-6.00 sec 268 MBytes 2.25 Gbits/sec [ 5] 6.00-7.00 sec 268 MBytes 2.24 Gbits/sec [ 5] 7.00-8.00 sec 267 MBytes 2.24 Gbits/sec [ 5] 8.00-9.00 sec 269 MBytes 2.25 Gbits/sec [ 5] 9.00-10.00 sec 269 MBytes 2.25 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 2.54 GBytes 2.18 Gbits/sec sender [ 5] 0.00-10.00 sec 2.53 GBytes 2.17 Gbits/sec receiver iperf Done. ./iperf3 -c 192.168.xx.30 -p 5201 -R Connecting to host 192.168.xx.30, port 5201 Reverse mode, remote host 192.168.xx.30 is sending [ 5] local 192.168.xx.45 port 51998 connected to 192.168.xx.30 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 267 MBytes 2.24 Gbits/sec [ 5] 1.00-2.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 2.00-3.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 3.00-4.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 4.00-5.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 5.00-6.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 6.00-7.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 7.00-8.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 8.00-9.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 9.00-10.00 sec 280 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 2.73 GBytes 2.34 Gbits/sec 16 sender [ 5] 0.00-10.00 sec 2.73 GBytes 2.34 Gbits/sec receiver iperf Done. ./iperf3 -c 192.168.xx.30 -p 5201 --bidir Connecting to host 192.168.xx.30, port 5201 [ 5] local 192.168.xx.45 port 52006 connected to 192.168.xx.30 port 5201 [ 7] local 192.168.xx.45 port 52007 connected to 192.168.xx.30 port 5201 [ ID][Role] Interval Transfer Bitrate [ 5][TX-C] 0.00-1.00 sec 185 MBytes 1.55 Gbits/sec [ 7][RX-C] 0.00-1.00 sec 271 MBytes 2.28 Gbits/sec [ 5][TX-C] 1.00-2.00 sec 183 MBytes 1.53 Gbits/sec [ 7][RX-C] 1.00-2.00 sec 273 MBytes 2.29 Gbits/sec [ 5][TX-C] 2.00-3.00 sec 185 MBytes 1.55 Gbits/sec [ 7][RX-C] 2.00-3.00 sec 271 MBytes 2.27 Gbits/sec [ 5][TX-C] 3.00-4.00 sec 184 MBytes 1.54 Gbits/sec [ 7][RX-C] 3.00-4.00 sec 272 MBytes 2.29 Gbits/sec [ 5][TX-C] 4.00-5.00 sec 184 MBytes 1.54 Gbits/sec [ 7][RX-C] 4.00-5.00 sec 272 MBytes 2.28 Gbits/sec [ 5][TX-C] 5.00-6.00 sec 185 MBytes 1.55 Gbits/sec [ 7][RX-C] 5.00-6.00 sec 270 MBytes 2.27 Gbits/sec [ 5][TX-C] 6.00-7.00 sec 183 MBytes 1.53 Gbits/sec [ 7][RX-C] 6.00-7.00 sec 272 MBytes 2.28 Gbits/sec [ 5][TX-C] 7.00-8.00 sec 184 MBytes 1.55 Gbits/sec [ 7][RX-C] 7.00-8.00 sec 270 MBytes 2.27 Gbits/sec [ 5][TX-C] 8.00-9.00 sec 184 MBytes 1.54 Gbits/sec [ 7][RX-C] 8.00-9.00 sec 270 MBytes 2.27 Gbits/sec [ 5][TX-C] 9.00-10.00 sec 184 MBytes 1.54 Gbits/sec [ 7][RX-C] 9.00-10.00 sec 269 MBytes 2.26 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID][Role] Interval Transfer Bitrate Retr [ 5][TX-C] 0.00-10.00 sec 1.80 GBytes 1.54 Gbits/sec sender [ 5][TX-C] 0.00-10.00 sec 1.79 GBytes 1.54 Gbits/sec receiver [ 7][RX-C] 0.00-10.00 sec 2.65 GBytes 2.28 Gbits/sec 6 sender [ 7][RX-C] 0.00-10.00 sec 2.65 GBytes 2.27 Gbits/sec receiver iperf Done. Edit: Links added Edited November 17, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
RlndVt Posted November 18, 2023 Share Posted November 18, 2023 (edited) I'm not using the 2.5Gbps port fwiw, but I did have a crash a few days ago: [830618.309898] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: return_address+0x78/0x78 [830618.310813] CPU: 5 PID: 67 Comm: kswapd0 Tainted: G C 6.6.0-edge-rockchip64 #1 [830618.311578] Hardware name: Helios64 (DT) [830618.311933] Call trace: [830618.312159] dump_backtrace+0x98/0x118 [830618.312502] show_stack+0x18/0x24 [830618.312805] dump_stack_lvl+0x48/0x60 [830618.313141] dump_stack+0x18/0x24 [830618.313443] panic+0x31c/0x388 [830618.313723] __ktime_get_real_seconds+0x0/0xc [830618.314121] c_start+0x0/0x10 [830618.314394] preempt_count_add+0xfc/0x130 [830618.314759] _raw_spin_lock+0x1c/0x7c [830618.315095] test_range_bit+0x40/0x1e4 [830618.315438] try_release_extent_mapping+0x198/0x240 [830618.315877] btrfs_release_folio+0x48/0xcc [830618.316249] filemap_release_folio+0x78/0xbc [830618.316637] shrink_folio_list+0xab4/0xd64 [830618.317009] evict_folios+0x230/0x5c8 [830618.317342] try_to_shrink_lruvec+0x1b0/0x2a8 [830618.317736] shrink_one+0x15c/0x234 [830618.318054] shrink_node+0x988/0xd8c [830618.318381] balance_pgdat+0x388/0x868 [830618.318723] kswapd+0x24c/0x538 [830618.319014] kthread+0xfc/0x108 [830618.319302] ret_from_fork+0x10/0x20 [830618.319630] SMP: stopping secondary CPUs [830618.319990] Kernel Offset: disabled [830618.320307] CPU features: 0x1,00000208,24020000,1000421b [830618.320783] Memory Limit: none [830618.321068] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: return_address+0x78/0x78 ]--- Going to revert to buster. (5.15.) Buster has been 99% stable for me. Might consider attempting bullseye. Edited November 18, 2023 by RlndVt 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 18, 2023 Author Share Posted November 18, 2023 (edited) @RlndVt The kernel panic was produced by '6.6.0-edge-rockchip64' (after 830618s = 9.6 days). Hopefully those issues will vanish once the 6.6 kernel becomes more mature. Edited November 18, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted November 25, 2023 Author Share Posted November 25, 2023 (edited) My latest tests with linux 6.6.2 were very promising: the watchdog timer does not reset the mainline r8152 driver anymore under heavy load (using the 2.5G interface). However, the mainline r8152 driver does not support bidirectional data exchange (total bidirectional transfer is capped to 2.35Gb/s). If you like to test it, please find the kernel deb files here (debs-6.6.2) (to be installed with dpkg -i linux*) and the Armbian image here (Armbian-23.11.0-6.6.2) . sbc-bench results are here. (you may also like to consider these remarks) P.S.: After a few days of testing linux-6.6.2, I must conclude that it is not yet fit for the purpose (produces swapper0 kernel panics). The best stable performance is still delivered by linux-5.10.43 (r8152 v2.14) and linux-5.15.52 (r8152 v1.12.12). _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 23.11.0-trunk Bookworm with Linux 6.6.2-edge-rockchip64 System load: 2% Up time: 21 min Memory usage: 31% of 3.71G IP: 192.168.xx.xx CPU temp: 49°C Usage of /: 48% of 15G storage/: 62% of 3.6T storage temp: 24°C % ./iperf3 -c 192.168.xx.30 -p 5201 Connecting to host 192.168.xx.30, port 5201 [ 5] local 192.168.xx.45 port 49535 connected to 192.168.xx.30 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 252 MBytes 2.12 Gbits/sec [ 5] 1.00-2.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 2.00-3.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 3.00-4.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 4.00-5.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 5.00-6.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 6.00-7.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 7.00-8.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 8.00-9.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 9.00-10.00 sec 281 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 2.71 GBytes 2.33 Gbits/sec sender [ 5] 0.00-10.00 sec 2.71 GBytes 2.33 Gbits/sec receiver iperf Done. % ./iperf3 -c 192.168.xx.30 -p 5201 -R Connecting to host 192.168.xx.30, port 5201 Reverse mode, remote host 192.168.xx.30 is sending [ 5] local 192.168.xx.45 port 49537 connected to 192.168.xx.30 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 255 MBytes 2.14 Gbits/sec [ 5] 1.00-2.00 sec 276 MBytes 2.32 Gbits/sec [ 5] 2.00-3.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 3.00-4.00 sec 278 MBytes 2.34 Gbits/sec [ 5] 4.00-5.00 sec 278 MBytes 2.33 Gbits/sec [ 5] 5.00-6.00 sec 276 MBytes 2.31 Gbits/sec [ 5] 6.00-7.00 sec 279 MBytes 2.34 Gbits/sec [ 5] 7.00-8.00 sec 277 MBytes 2.32 Gbits/sec [ 5] 8.00-9.00 sec 279 MBytes 2.34 Gbits/sec [ 5] 9.00-10.00 sec 278 MBytes 2.33 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 2.69 GBytes 2.31 Gbits/sec 70 sender [ 5] 0.00-10.00 sec 2.69 GBytes 2.31 Gbits/sec receiver iperf Done. % ./iperf3 -c 192.168.xx.30 -p 5201 --bidir Connecting to host 192.168.xx.30, port 5201 [ 5] local 192.168.xx.45 port 49539 connected to 192.168.xx.30 port 5201 [ 7] local 192.168.xx.45 port 49540 connected to 192.168.xx.30 port 5201 [ ID][Role] Interval Transfer Bitrate [ 5][TX-C] 0.00-1.00 sec 23.8 MBytes 199 Mbits/sec [ 7][RX-C] 0.00-1.00 sec 212 MBytes 1.78 Gbits/sec [ 5][TX-C] 1.00-2.00 sec 28.4 MBytes 238 Mbits/sec [ 7][RX-C] 1.00-2.00 sec 244 MBytes 2.05 Gbits/sec [ 5][TX-C] 2.00-3.00 sec 24.9 MBytes 209 Mbits/sec [ 7][RX-C] 2.00-3.00 sec 250 MBytes 2.09 Gbits/sec [ 5][TX-C] 3.00-4.00 sec 75.0 MBytes 628 Mbits/sec [ 7][RX-C] 3.00-4.00 sec 207 MBytes 1.73 Gbits/sec [ 5][TX-C] 4.00-5.00 sec 96.2 MBytes 808 Mbits/sec [ 7][RX-C] 4.00-5.00 sec 190 MBytes 1.60 Gbits/sec [ 5][TX-C] 5.00-6.00 sec 24.4 MBytes 204 Mbits/sec [ 7][RX-C] 5.00-6.00 sec 244 MBytes 2.04 Gbits/sec [ 5][TX-C] 6.00-7.00 sec 25.0 MBytes 210 Mbits/sec [ 7][RX-C] 6.00-7.00 sec 248 MBytes 2.08 Gbits/sec [ 5][TX-C] 7.00-8.00 sec 24.6 MBytes 207 Mbits/sec [ 7][RX-C] 7.00-8.00 sec 246 MBytes 2.06 Gbits/sec [ 5][TX-C] 8.00-9.00 sec 24.4 MBytes 204 Mbits/sec [ 7][RX-C] 8.00-9.00 sec 245 MBytes 2.06 Gbits/sec [ 5][TX-C] 9.00-10.00 sec 25.1 MBytes 211 Mbits/sec [ 7][RX-C] 9.00-10.00 sec 244 MBytes 2.04 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID][Role] Interval Transfer Bitrate Retr [ 5][TX-C] 0.00-10.00 sec 372 MBytes 312 Mbits/sec sender [ 5][TX-C] 0.00-10.00 sec 364 MBytes 305 Mbits/sec receiver [ 7][RX-C] 0.00-10.00 sec 2.28 GBytes 1.95 Gbits/sec 61 sender [ 7][RX-C] 0.00-10.00 sec 2.27 GBytes 1.95 Gbits/sec receiver iperf Done. Edited December 3, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
TheGuv Posted December 9, 2023 Share Posted December 9, 2023 I appreciate the work being done to get us some stability. I'm currently running 5.10.43 with r8152 v2.14.0 but finding it unstable with several reboots each day. I think 6.1.36 for me was marginally better but not much in it. @ebin-dev seems to be having a good time with 5.10.43 so I'm assuming I've missed something along the way. I have: uBoot from 22.02.1 kernel 5.10.43-rockchip64 #21.05.4 SMP PREEMPT Wed Jun 16 08:02:12 UTC 2021 r8152a v2.14.0 (2020/09/24) CPU min/max 1608000/performance. 4x HDD using mergerfs and snapraid, 1xSSD for root drive and booting from eMMC Did I miss something? 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted December 9, 2023 Author Share Posted December 9, 2023 (edited) @TheGuv Your CPU governor is set to performance, while I am using the standard settings (see below). You may safely upgrade linux to 5.15.52. Although it uses the r8152 mainline driver v.1.12.12 it is stable. To figure out what is wrong with your system you should start from a fresh image (bookworm 23.05.4-6.1.36) and downgrade to one of the linux versions 5.15.93, 5.15.52 or 5.10.43 if you have problems with 6.1.36. Im am currently using linux 5.15.52. # cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=408000 MAX_SPEED=1800000 GOVERNOR=ondemand Edited December 9, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
TheGuv Posted December 9, 2023 Share Posted December 9, 2023 Thank you @ebin-dev for the help and clues. I tried 5.15.52 installing three .deb files linux-dtb-current-rockchip64_22.05.4_arm64.deb linux-headers-current-rockchip64_22.05.4_arm64.deb linux-image-current-rockchip64_22.05.4_arm64.deb downloaded from the 5.15.52 pool directory but afterwards I had no networking, and both the serial and console were acting strange with hangs and pauses which prevented me from login in to see what was going on. I reverted to 5.10.43. Did I need to do something else, like different firmware in /lib/firmware/rtl_nic which is currently from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_nic ? Should I have updated the initrd after installing the .debs? I know I'm being daft somewhere but after so many different tests over the last weeks I'm kind of spinning ! 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted December 9, 2023 Author Share Posted December 9, 2023 (edited) @TheGuv You need the firmware for the r8152 mainline driver present in linux 5.15.x and above. Edit: if you copy the firmware files to /lib/firmware/rtl_nic before you install the new linux kernel then those files are automatically copied into initrd during installation of the kernel. Otherwise you need to update initrd yourself. I would certainly overwrite u-boot on emmc by https://imola.armbian.com/apt/pool/main/l/linux-u-boot-helios64-edge/linux-u-boot-edge-helios64_22.02.1_arm64.deb as described earlier in this thread. And finally I would run sbc-bench at least once. It would appear to permanently change some performance related settings such that your system is more responsive. I disabled Armbian updates back in August 2021... Good luck. Edited December 10, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
halfa Posted December 11, 2023 Share Posted December 11, 2023 On my side I've been running 5.16.11 from linux-image-edge-rockchip64_22.02.1 and it has been rather stable, with occasional (once every 2 months?) lockups. I'm running on a jammy base. Just saw that the 6.6.2 kernel is available in the test repos, anyone gave it a try? armbian-bsp-cli-helios64/jammy 23.11.1 arm64 [upgradable from: 22.02.1] armbian-firmware/jammy,jammy,jammy 23.11.1 all [upgradable from: 22.05.1] linux-dtb-edge-rockchip64/jammy 23.11.1 arm64 [upgradable from: 22.02.1] linux-headers-edge-rockchip64/jammy 23.11.1 arm64 [upgradable from: 22.02.1] linux-image-edge-rockchip64/jammy 23.11.1 arm64 [upgradable from: 22.02.1] 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted December 22, 2023 Author Share Posted December 22, 2023 (edited) Thanks to @prahal there is a fix for the reduced emmc speed. I can confirm that emmc can be accessed with hs400 again (read and write without CQE errors) - I have tested it with linux 5.15.93 and 6.1.11 (it works probably also for all higher linux versions). # hdparm -tT /dev/mmcblk1p1 /dev/mmcblk1p1: Timing cached reads: 2632 MB in 2.00 seconds = 1316.22 MB/sec Timing buffered disk reads: 658 MB in 3.01 seconds = 218.91 MB/sec # helios64: enabling hs400 speed for accessing emmc # changes to /boot/dtb/rockchip/rk3399-kobol-helios64.dtb (use device tree compiler 'dtc' for that) added to phy@f780: rockchip,enable-strobe-pulldown; added to mmc@fe330000: mmc-hs400-1_8v; mmc-hs400-enhanced-strobe; Edited December 22, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted December 23, 2023 Author Share Posted December 23, 2023 (edited) On 12/12/2023 at 12:08 AM, halfa said: Just saw that the 6.6.2 kernel is available in the test repos, anyone gave it a try? Linux 6.6.7 and 6.6.8 are stable so far on my system (manually installed linux-image, linux-dtb, linux-headers only). You need to copy the rtl_nic firmware files to /lib/firmware/rtl_nic ... Edit: Again, the watchdog timer may have to reset the mainline r8152 driver upon heavy network traffic. Edited December 24, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted December 29, 2023 Author Share Posted December 29, 2023 (edited) _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 23.11.0-trunk Bookworm with Linux 6.6.8-edge-rockchip64 System load: 2% Up time: 1:01 Memory usage: 31% of 3.71G IP: 192.168.xx.yy CPU temp: 46°C Usage of /: 49% of 15G storage/: 62% of 3.6T storage temp: 23°C So finally I arrived at a stable Armbian Bookworm configuration for Helios64: Starting from Armbian Bookworm image (Armbian_23.5.4_Helios64_bookworm_current_6.1.36) Disable Armbian updates in /etc/apt/sources.list.d/armbian.list Copy rtl_nic firmware to /lib/firmware/rtl_nic Upgrade kernel to linux-6.6.8 # download link to those debs downloaded 23.12.2023. (Edit: there would appear to be issues with NFS if you use linux 6.6.8 - use linux 6.1.71 in that case; if you still have issues, use linux 5.15.93) Flash u-boot to emmc (linux-u-boot-edge-helios64_22.02.1_arm64) # see here Set nic offload options (ethtool -K end1 tso on gso on gro on) # change 'end1' to your network interface name Apply any changes to /boot/dtb/rockchip/rk3399-kobol-helios64.dtb (hs400 support, L2 cache information) # download link for your convenience Execute 'sbc-bench -r' at least once; you may change the cpu governor in /etc/default/cpufrequtils to 'ondemand' ! If you intend to use the 2.5G interface you need to fix the hardware issue first ! # Even if the 2.5G port is connected to a 2.5G switch, interface speed is 1G during autonegotiation for some time ... With this configuration iperf3 measures 2.33 Gb/s transferred from/to the server (one-way), while in bidirectional mode 2x1.71Gb/s are transferred (simultaneously in both directions): # ./iperf3 -c 192.168.xx.yy -p 5201 Connecting to host 192.168.xx.yy, port 5201 [ 6] local 192.168.xx.zz port 55582 connected to 192.168.xx.yy port 5201 [ ID] Interval Transfer Bitrate [ 6] 0.00-1.01 sec 258 MBytes 2.15 Gbits/sec [ 6] 1.01-2.01 sec 282 MBytes 2.36 Gbits/sec [ 6] 2.01-3.01 sec 279 MBytes 2.34 Gbits/sec [ 6] 3.01-4.01 sec 281 MBytes 2.35 Gbits/sec [ 6] 4.01-5.01 sec 280 MBytes 2.35 Gbits/sec [ 6] 5.01-6.01 sec 281 MBytes 2.36 Gbits/sec [ 6] 6.01-7.01 sec 281 MBytes 2.36 Gbits/sec [ 6] 7.01-8.00 sec 279 MBytes 2.35 Gbits/sec [ 6] 8.00-9.01 sec 281 MBytes 2.35 Gbits/sec [ 6] 9.01-10.01 sec 280 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 6] 0.00-10.01 sec 2.72 GBytes 2.33 Gbits/sec sender [ 6] 0.00-10.01 sec 2.72 GBytes 2.33 Gbits/sec receiver iperf Done. # ./iperf3 -c 192.168.xx.yy -p 5201 -R Connecting to host 192.168.xx.yy, port 5201 Reverse mode, remote host 192.168.xx.yy is sending [ 6] local 192.168.xx.zz port 55588 connected to 192.168.xx.yy port 5201 [ ID] Interval Transfer Bitrate [ 6] 0.00-1.01 sec 262 MBytes 2.18 Gbits/sec [ 6] 1.01-2.00 sec 278 MBytes 2.34 Gbits/sec [ 6] 2.00-3.01 sec 280 MBytes 2.35 Gbits/sec [ 6] 3.01-4.01 sec 279 MBytes 2.34 Gbits/sec [ 6] 4.01-5.00 sec 278 MBytes 2.34 Gbits/sec [ 6] 5.00-6.01 sec 279 MBytes 2.34 Gbits/sec [ 6] 6.01-7.01 sec 279 MBytes 2.34 Gbits/sec [ 6] 7.01-8.01 sec 279 MBytes 2.34 Gbits/sec [ 6] 8.01-9.01 sec 279 MBytes 2.34 Gbits/sec [ 6] 9.01-10.01 sec 278 MBytes 2.34 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 6] 0.00-10.01 sec 2.71 GBytes 2.33 Gbits/sec 53 sender [ 6] 0.00-10.01 sec 2.71 GBytes 2.33 Gbits/sec receiver iperf Done. # ./iperf3 -c 192.168.xx.yy -p 5201 --bidir Connecting to host 192.168.xx.yy, port 5201 [ 6] local 192.168.xx.zz port 55599 connected to 192.168.xx.yy port 5201 [ 8] local 192.168.xx.zz port 55600 connected to 192.168.xx.yy port 5201 [ ID][Role] Interval Transfer Bitrate [ 6][TX-C] 0.00-1.01 sec 221 MBytes 1.84 Gbits/sec [ 8][RX-C] 0.00-1.01 sec 193 MBytes 1.61 Gbits/sec [ 6][TX-C] 1.01-2.01 sec 166 MBytes 1.39 Gbits/sec [ 8][RX-C] 1.01-2.01 sec 215 MBytes 1.80 Gbits/sec [ 6][TX-C] 2.01-3.01 sec 214 MBytes 1.80 Gbits/sec [ 8][RX-C] 2.01-3.01 sec 198 MBytes 1.67 Gbits/sec [ 6][TX-C] 3.01-4.01 sec 235 MBytes 1.97 Gbits/sec [ 8][RX-C] 3.01-4.01 sec 197 MBytes 1.66 Gbits/sec [ 6][TX-C] 4.01-5.01 sec 222 MBytes 1.87 Gbits/sec [ 8][RX-C] 4.01-5.01 sec 197 MBytes 1.65 Gbits/sec [ 6][TX-C] 5.01-6.01 sec 194 MBytes 1.63 Gbits/sec [ 8][RX-C] 5.01-6.01 sec 210 MBytes 1.76 Gbits/sec [ 6][TX-C] 6.01-7.00 sec 184 MBytes 1.54 Gbits/sec [ 8][RX-C] 6.01-7.00 sec 212 MBytes 1.78 Gbits/sec [ 6][TX-C] 7.00-8.01 sec 192 MBytes 1.61 Gbits/sec [ 8][RX-C] 7.00-8.01 sec 208 MBytes 1.75 Gbits/sec [ 6][TX-C] 8.01-9.01 sec 216 MBytes 1.81 Gbits/sec [ 8][RX-C] 8.01-9.01 sec 203 MBytes 1.70 Gbits/sec [ 6][TX-C] 9.01-10.01 sec 206 MBytes 1.73 Gbits/sec [ 8][RX-C] 9.01-10.01 sec 204 MBytes 1.71 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID][Role] Interval Transfer Bitrate Retr [ 6][TX-C] 0.00-10.01 sec 2.00 GBytes 1.72 Gbits/sec sender [ 6][TX-C] 0.00-10.01 sec 2.00 GBytes 1.72 Gbits/sec receiver [ 8][RX-C] 0.00-10.01 sec 1.99 GBytes 1.71 Gbits/sec 17 sender [ 8][RX-C] 0.00-10.01 sec 1.99 GBytes 1.71 Gbits/sec receiver iperf Done. # hdparm -tT /dev/mmcblk1 /dev/mmcblk1: Timing cached reads: 2986 MB in 2.00 seconds = 1493.93 MB/sec Timing buffered disk reads: 706 MB in 3.00 seconds = 235.11 MB/sec # lscpu -C NAME ONE-SIZE ALL-SIZE WAYS TYPE LEVEL SETS PHY-LINE COHERENCY-SIZE L1d Data 1 L1i Instruction 1 L2 Unified 2 Edited April 1 by ebin-dev links added, nic offload settings updated, download links added for linux 6.1.71 and 5.15.93, governors updated 1 Quote Link to comment Share on other sites More sharing options...
OdyX Posted December 30, 2023 Share Posted December 30, 2023 (edited) Thanks @ebin-dev for these instructions; after I bricked a nicely-working (but constantly shutting down) bullseye Helios64 by "apt upgrade"ing it to bookwork, I went with a (backup and a) clean reinstall following your instructions, and it seems much stabler indeed! (Of course, it's not doing anything yet as I still need to resetup everything I had...). The only issue I have is that it doesn't boot if I have my DELOCK 4-SATA-to-USB-C plugged in (to a USB-3.0 port). Unplugging it, booting and plugging it later works though. Any idea? Edited December 30, 2023 by OdyX 0 Quote Link to comment Share on other sites More sharing options...
ebin-dev Posted December 30, 2023 Author Share Posted December 30, 2023 (edited) 16 hours ago, OdyX said: The only issue I have is that it doesn't boot if I have my DELOCK 4-SATA-to-USB-C plugged in (to a USB-3.0 port). Unplugging it, booting and plugging it later works though. Any idea? Did you add 'vendor:device:u' to usbstoragequirks in /boot/armbianEnv.txt ? (here is why this might help) Edit: example with 4 external sata hdds bridged with JMicron 578 (usbstoragequirks=152d:0578:u) # dmesg | grep 2-1.3 [ 2.544431] usb 2-1.3: new SuperSpeed USB device number 3 using xhci-hcd [ 2.565982] usb 2-1.3: New USB device found, idVendor=152d, idProduct=0578, bcdDevice= 3.01 [ 2.566017] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.566035] usb 2-1.3: Product: External HDD [ 2.566049] usb 2-1.3: Manufacturer: External USB3.0 [ 2.566062] usb 2-1.3: SerialNumber: 0000007788FC [ 2.567670] usb-storage 2-1.3:1.0: USB Mass Storage device detected [ 2.568719] usb-storage 2-1.3:1.0: Quirks match for vid 152d pid 0578: 1000000 [ 2.569099] scsi host0: usb-storage 2-1.3:1.0 [ 122.172373] usb 2-1.3: USB disconnect, device number 3 Edited December 31, 2023 by ebin-dev 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.