Nobby42

Members
  • Content Count

    16
  • Joined

  • Last visited

About Nobby42

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Now I have get the next crash processes (see the log). Kernel 5.4.13 CPU 1,42/1,8Ghz governor is set to "conservative" What I doing. I open the webgui from a nextcloud (docker) installation. log_crash-20200191.txt
  2. Since I set the CPU frequency to 1.4/1.8Ghz I have no problems. Look at this topic
  3. It was the same with me, too. CPU message on the console and nothing works. I use the 5.4.8 kernel. Currently I use a power supply with 5.3V/4A on pin4/6 https://www.amazon.de/gp/product/B01HRR9GY4/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8&psc=1 But I'm not entirely satisfied with that either. I am currently preparing a rack mounting of the NanoPi and will then use this power supply. https://www.meanwell.com/webapp/product/search.aspx?prod=RS-25 That's stable at 5A.
  4. Hi, I have had formative experience with the NanoPI M4v2.. First, you need a real power supply. The Rasbberry 4 power supply for example breaks down when using a NMVe and a SSD, at high load, to below 5V (approx. 4.8V - 4.7V). 2. the CPU frequency. I think the 1.5/2Ghz is too much. I have had several crashes. For example the NanoPi crashes when transferring large amounts of data, sometimes processes (kworker, sshd, ...) just crashed and sometimes the NanoPi just stopped. Since I use the frequency to 1.4/1.8Ghz and a similar power supply, it looks like the NanoPI runs stable with NMVe and USB SSD. Currently I am using the NanoPi as a file server, MQTT Broker and nextcloud server and haven't had any crashes for 4 days.
  5. Hi, when I used rsync to copy several GB of data from the NMV3 to a USB SSD, the SSHD crashed. [96500.101926] ------------[ cut here ]------------ [96500.102376] kernel BUG at arch/arm64/kernel/traps.c:405! [96500.102858] Internal error: Oops - BUG: 0 [#2] PREEMPT SMP [96500.103343] Modules linked in: sg uas hci_uart bluetooth cpufreq_userspace zstd zram dw_hdmi_i2s_audio rockchip_rga v4l2_mem2mem videobuf2_dma_sg panfrost fusb302 tcpm videobuf2_memops gpu_sched typec videobuf2_v4l2 videobuf2_common videodev mc brcmfmac brcmutil cfg80211 rfkill rockchipdrm analogix_dp dw_mipi_dsi dw_hdmi ip_tables ipv6 crc_ccitt phy_rockchip_typec phy_rockchip_pcie dwmac_rk stmmac_platform stmmac phylink [96500.106655] CPU: 3 PID: 14434 Comm: sshd Tainted: G D W 5.4.8-rockchip64 #19.11.7 [96500.107413] Hardware name: FriendlyElec NanoPi M4 Ver2.0 (DT) [96500.107921] pstate: 00000005 (nzcv daif -PAN -UAO) [96500.108354] pc : do_undefinstr+0x2e4/0x310 [96500.108718] lr : do_undefinstr+0x1dc/0x310 [96500.109081] sp : ffff8000130237d0 [96500.109375] x29: ffff8000130237d0 x28: ffff00003a6ae200 [96500.109846] x27: 00000000327efa40 x26: 000057c3dbe99326 [96500.110315] x25: 0000000000000010 x24: 0000000000000000 [96500.110785] x23: 0000000040000005 x22: ffff800010c89364 [96500.111255] x21: ffff800013023970 x20: ffff800013023830 [96500.111724] x19: ffff80001136b508 x18: 0000000000000000 [96500.112194] x17: 0000000000000000 x16: 0000000000000000 [96500.112664] x15: 0000000000000000 x14: 7f6754efac8b8b63 [96500.113133] x13: 64022bac43b4cbe6 x12: 000000000003d440 [96500.113603] x11: 0000000000000074 x10: 0000000000000001 [96500.114073] x9 : 0000000093637393 x8 : 0000000000000000 [96500.114542] x7 : 0000000000000001 x6 : 0000000000000000 [96500.115012] x5 : 00000000d5300000 x4 : ffff800011381370 [96500.115481] x3 : 0000000000000001 x2 : 0000000000000000 [96500.115951] x1 : ffff00003a6ae200 x0 : 0000000040000005 [96500.116422] Call trace: [96500.116644] do_undefinstr+0x2e4/0x310 [96500.116978] el1_undef+0x10/0x84 [96500.117272] __ip_queue_xmit+0x3c/0x390 [96500.117615] ip_queue_xmit+0x10/0x18 [96500.117937] __tcp_transmit_skb+0x4b0/0xae0 [96500.118310] tcp_write_xmit+0x39c/0x1080 [96500.118659] __tcp_push_pending_frames+0x38/0xc0 [96500.119067] tcp_push+0x114/0x160 [96500.119364] tcp_sendmsg_locked+0xab4/0xbe8 [96500.119735] tcp_sendmsg+0x34/0x58 [96500.120041] inet_sendmsg+0x40/0x68 [96500.120353] sock_write_iter+0x8c/0xe8 [96500.120689] new_sync_write+0x100/0x180 [96500.121028] __vfs_write+0x2c/0x40 [96500.121332] vfs_write+0xb0/0x1d0 [96500.121627] ksys_write+0x64/0xe8 [96500.121923] __arm64_sys_write+0x18/0x20 [96500.122273] el0_svc_common.constprop.1+0x88/0x178 [96500.122699] el0_svc_handler+0x20/0x80 [96500.123032] el0_svc+0x8/0xc [96500.123293] Code: f9401bf7 17ffff7d a9025bf5 f9001bf7 (d4210000) [96500.123833] ---[ end trace 4a19b31e1f6dad94 ]--- It is a kernel problem?
  6. Nobby42

    NanoPI 4MV2

    Hi, I have no experience with GitHub, but I'll look into it. It may take a while.
  7. Nobby42

    NanoPI 4MV2

    Yes ;-) Thanks for your support.
  8. Nobby42

    NanoPI 4MV2

    Hi piter75, I think I found the problem. The UAS. https://unix.stackexchange.com/questions/441668/debian-usb3-hdd-uas-i-o-errors After I add the USB-ID for my adapter in the armbianEnv.txt the SSD was black list für the UAS and the board booting with the rootfs on the SSD. [ 56.463044] hub 8-1:1.0: USB hub found [ 56.463741] hub 8-1:1.0: 4 ports detected [ 57.026120] usb 8-1.2: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd [ 57.047008] usb 8-1.2: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 [ 57.047771] usb 8-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 57.048436] usb 8-1.2: Product: ASM1153USB3.0TOSATA [ 57.048886] usb 8-1.2: Manufacturer: ASM1153USB3.0TOSATA [ 57.049374] usb 8-1.2: SerialNumber: 123456789019 [ 57.051688] usb 8-1.2: UAS is blacklisted for this device, using usb-storage instead [ 57.052403] usb-storage 8-1.2:1.0: USB Mass Storage device detected [ 57.053572] usb-storage 8-1.2:1.0: Quirks match for vid 174c pid 55aa: c00000 [ 57.054428] scsi host0: usb-storage 8-1.2:1.0 [ 57.060247] usbcore: registered new interface driver uas [ 58.058774] scsi 0:0:0:0: Direct-Access ASM1153U ASM1153USB3.0TOS 0 PQ: 0 ANSI: 6 [ 58.062417] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB) [ 58.064363] sd 0:0:0:0: [sda] Write Protect is off [ 58.065331] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 58.097560] sda: sda1 [ 58.104521] sd 0:0:0:0: [sda] Attached SCSI disk
  9. Nobby42

    NanoPI 4MV2

    Hi piter75, thanks for your support. I ran some tests yesterday. During the last test I made a mistake and forgot to remove the SD card and the Pi boots with all memory media. After booting I saw that the ROOTFS is on the device /dev/sda1. Why? It looks like it booted from a mix of SD and EMMC and rootfs on sda1 lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda └─sda1 ext4 b1a869c6-23b1-4254-b604-6c8e9abe4440 215.3G 1% / mmcblk2 └─mmcblk2p1 ext4 71e19ca5-088d-4ecb-aa80-97d8e8445f20 13.3G 1% /media/mmcboot mmcblk2boot0 mmcblk2boot1 mmcblk1 └─mmcblk1p1 ext4 c2a23e0b-b4a8-475a-a890-a9f2f107f46a 13G 9% /media/sd-card zram0 39.5M 11% /var/log zram1 [SWAP] cat /media/mmcboot/boot/armbianEnv.txt verbosity=7 overlay_prefix=rockchip fdtfile=rockchip/rk3399-nanopi-m4v2.dtb rootdev=UUID=b1a869c6-23b1-4254-b604-6c8e9abe4440 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat /media/sd-card/boot/armbianEnv.txt verbosity=1 overlay_prefix=rockchip fdtfile=rockchip/rk3399-nanopi-m4v2.dtb rootdev=UUID=c2a23e0b-b4a8-475a-a890-a9f2f107f46a rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat /media/sd-card/etc/fstab UUID=c2a23e0b-b4a8-475a-a890-a9f2f107f46a / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 nobby@Viking:~$ ^C nobby@Viking:~$ cat /boot/armbianEnv.txt verbosity=7 overlay_prefix=rockchip fdtfile=rockchip/rk3399-nanopi-m4v2.dtb rootdev=UUID=b1a869c6-23b1-4254-b604-6c8e9abe4440 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 UUID=71e19ca5-088d-4ecb-aa80-97d8e8445f20 /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 /media/mmcboot/boot /boot none bind 0 0 UUID=b1a869c6-23b1-4254-b604-6c8e9abe4440 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 Very mysterious. Here are the armbianmonitor output. http://ix.io/26eq When I boot from emmc I see this error. MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** Something wrong with the emmc? I have found this topic and will test it today. https://tinkerboarding.co.uk/forum/post-8800.html
  10. Nobby42

    NanoPI 4MV2

    Happy new year. UUID looks good. Here they are from the last test. lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda └─sda1 ext4 5a664488-9c46-46a8-92a8-73127b19c54b 215.3G 1% /media/ssd mmcblk2 └─mmcblk2p1 ext4 ddceb71a-f588-4aea-bdb0-2fc352dfef3d 13.3G 1% /media/mmc mmcblk2boot0 mmcblk2boot1 mmcblk1 └─mmcblk1p1 ext4 6afbab68-85eb-40bf-bb45-e469f4b615f5 13G 9% / zram0 41.7M 7% /var/log zram1 [SWAP] cat /media/mmc/boot/armbianEnv.txt verbosity=1 overlay_prefix=rockchip fdtfile=rockchip/rk3399-nanopi-m4v2.dtb rootdev=UUID=5a664488-9c46-46a8-92a8-73127b19c54b rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat /media/ssd/etc/fstab # <file system> <mount point> <type> <options> <dump><pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=ddceb71a-f588-4aea-bdb0-2fc352dfef3d /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 1 /media/mmcboot/boot /boot none bind 0 0 UUID=5a664488-9c46-46a8-92a8-73127b19c54b / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 1
  11. Nobby42

    NanoPI 4MV2

    The NanoPi don't boot from emmc with roots on SSD with the 5.4.6 kernel. I have attached the boot log. After the Pi found the ssd they do nothing. I have tested variuos SSD. Booting from only SD or only EMMC works fine. nanopi_log201911231_1.txt
  12. Nobby42

    NanoPI 4MV2

    I also use the NanoPi as a server. Could it possibly be due to the CPU frequency? The 5.4.6 kernel use 1,5/2Ghz and the 4.4.192 kernel 1,4/1,8Ghz. I'll test it tomorrow.
  13. Nobby42

    NanoPI 4MV2

    @piter75 Thanks. Now the ethernet workes and I can test the legacy kernel. With the 5.4.6 kernel I have a lot of problems. Sometimes the Pi crashes. I cannot verify the reason. I boot the Pi from emmc and rootfs on a SSD. Looks like a problem with the USB SSD adapter but I am not shure. I use USB adapters with JM567 and ASM1153 chipset.
  14. Nobby42

    NanoPI 4MV2

    Hi, I work without WiFi. Regards Norbert
  15. Nobby42

    NanoPI 4MV2

    Hi, I have testet the image with the 5.4.2 kernel. No problems. Can anyone reproduce the problem with the 4.4.192 kernel? Kind regards Norbert