Meier

Members
  • Content Count

    10
  • Joined

  • Last visited

About Meier

  • Rank
    Member

Recent Profile Visitors

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

  1. Thanks Myy for the pointers. I'll try if the dptx.bin driver helps preventing the boot oops message. Is there a way to tell how that binary file has been compiled, or to make sure it is legit? Regarding the stress testing in overlayroot, this command immediately aborts as it fills up the available tmpfs within seconds. Good thought about find /, I'll try that.
  2. Unfortunately, I still keep getting the freezes from time to time. Two thinks I noticed: When running `stress -i 4 -d 4` I can crash the board in ~3 minutes very reliably. But not any board, just this one, but even without any additional peripherals like the SSD plugged in. As it's running on eMMC, it might be this particular eMMC that causes the crash. This let me to build a latest Armbian Ubuntu 18.04 image with `overlayroot` to eliminate all I/O to the eMMC. This board that has been crashing has now been running for ~2 days. I'll try to gather more data in case the boards crash with the build from the current master branch. Just FYI in case you're curious: this is the project I'm working on https://github.com/digitalbitbox/bitbox-base.
  3. Thanks Igor! Will try that today and let you know how it works out. Update: works fine so far, after 3+ hours uptime, also with the self-compiled image, but intervals between freezes can be quite long.
  4. Additional info: after some quick uptime of ~1h the board started to fault repeatedly, but without crashing completely. SSH connections were closed, but later a login was possible again. Three specific errors in short interval, all logged in full here: https://pastebin.com/SAcUAGb2 Jul 8 16:59:31 carol kernel: [ 3752.234046] Unhandled fault: synchronous external abort (0x96000210) at 0xffffff8009d5401c Jul 8 16:59:31 carol kernel: [ 3752.240736] Internal error: : 96000210 [#1] SMP ... Jul 8 17:00:12 carol kernel: [ 3759.996389] BUG: spinlock lockup suspected on CPU#3, nvme/296 Jul 8 17:00:12 carol kernel: [ 3760.001966] lock: 0xffffff8009141870, .magic: dead4ead, .owner: nvme/296, .owner_cpu: 3 ... Jul 8 17:00:12 carol kernel: [ 3792.419942] Watchdog detected hard LOCKUP on cpu 3 Jul 8 17:00:12 carol kernel: [ 3792.420464] ------------[ cut here ]------------ Jul 8 17:00:12 carol kernel: [ 3792.430494] WARNING: at kernel/watchdog.c:352
  5. On several RockPro64 boards I experience infrequent freezes, mostly directly on boot, but also after some longer (hours, days) uptime. I use the official power adapter and no additional hardware except a PCIe adapter for an SSD, which works flawlessly when operational. When looking at the kern.log, there are quite a few errors and warnings, but comparing to a successful boot these are all also present. So I don't think they cause the freeze directly. Currently, I recorded the freeze on the latest Armbian Bionic as release just recently. FWIW, I think the same issue also occurs on the previous Debian Stretch image (had various freezes, but have not recorded any details yet). On a unsuccessful boot, the error occurs after about 8 seconds. A reboot (or two) usually fixes the issue, until the next time... Jul 8 15:18:23 carol kernel: [ 8.528275] Unable to handle kernel NULL pointer dereference at virtual address 00000000 Jul 8 15:18:23 carol kernel: [ 8.530625] pgd = ffffffc0ead3f000 Jul 8 15:18:23 carol kernel: [ 8.532515] [00000000] *pgd=0000000000000000, *pud=0000000000000000 Jul 8 15:18:23 carol kernel: [ 8.534710] Internal error: Oops: 96000005 [#1] SMP Jul 8 15:18:24 carol kernel: [ 8.536753] Modules linked in: af_packet iptable_nat nf_nat_ipv4 nf_nat nf_log_ipv4 nf_log_common xt_LOG xt_limit nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_conntrack nf_conntrack iptable_filter snd_soc_rockchip_hdmi_dp rk_vcodec ip_tables x_tables autofs4 phy_rockchip_pcie Jul 8 15:18:24 carol kernel: [ 8.542598] CPU: 5 PID: 1044 Comm: find Not tainted 4.4.182-rockchip64 #1 Jul 8 15:18:24 carol kernel: [ 8.544959] Hardware name: Pine64 RockPro64 (DT) Jul 8 15:18:24 carol kernel: [ 8.547155] task: ffffffc0eb247000 task.stack: ffffffc0e1c78000 Jul 8 15:18:24 carol kernel: [ 8.549491] PC is at do_dentry_open+0x234/0x2e4 Jul 8 15:18:24 carol kernel: [ 8.551687] LR is at do_dentry_open+0x288/0x2e4 Jul 8 15:18:24 carol kernel: [ 8.553852] pc : [<ffffff80081f2738>] lr : [<ffffff80081f278c>] pstate: a0000145 Jul 8 15:18:24 carol kernel: [ 8.556284] sp : ffffffc0e1c7bbc0 Jul 8 15:18:24 carol kernel: [ 8.558403] x29: ffffffc0e1c7bbc0 x28: ffffffc0eb247000 Jul 8 15:18:24 carol kernel: [ 8.560742] x27: 0000000000000000 x26: ffffffc0f26eb000 Jul 8 15:18:24 carol kernel: [ 8.563064] x25: 000000000000011d x24: ffffffc0e1cff690 Jul 8 15:18:24 carol kernel: [ 8.565376] x23: ffffff8008219cb8 x22: 0000000000000000 Jul 8 15:18:24 carol kernel: [ 8.567670] x21: 0000000000000000 x20: ffffffc0f27882b0 Jul 8 15:18:24 carol kernel: [ 8.569954] x19: ffffffc0e1cff680 x18: 0000007fb4979a70 Jul 8 15:18:24 carol kernel: [ 8.572191] x17: 0000007fb48e8848 x16: ffffff80081f3ea4 Jul 8 15:18:24 carol kernel: [ 8.574416] x15: 0000000000000000 x14: ffffffffffffffff Jul 8 15:18:24 carol kernel: [ 8.576663] x13: 0000000000000000 x12: 0101010101010101 Jul 8 15:18:24 carol kernel: [ 8.578896] x11: 7f7f7f7f7f7f7f7f x10: 0000007fb4a8a140 Jul 8 15:18:24 carol kernel: [ 8.581115] x9 : 0000000000000000 x8 : ffffffc0e1cff7b8 Jul 8 15:18:24 carol kernel: [ 8.583390] x7 : 0000000000000000 x6 : ffffffc0f061d1e9 Jul 8 15:18:24 carol kernel: [ 8.585641] x5 : 0000000000000000 x4 : 00000000000055b1 Jul 8 15:18:24 carol kernel: [ 8.587874] x3 : 00000040eee4a000 x2 : ffffff8008219a20 Jul 8 15:18:24 carol kernel: [ 8.590114] x1 : ffffff8008c02140 x0 : 0000000000000000 Jul 8 15:18:24 carol kernel: [ 8.592341] Jul 8 15:18:24 carol kernel: [ 8.592341] PC: 0xffffff80081f26b8: Jul 8 15:18:24 carol kernel: [ 8.596219] 26b8 54fffd60 f940c680 f9001660 b4fffd20 aa1603e1 aa1303e0 940c0a2c 2a0003f6 Jul 8 15:18:24 carol kernel: [ 8.598764] 26d8 35000700 b9405261 d5033bbf f940ca80 b5000320 b50004b7 f9401660 f9402c17 Jul 8 15:18:24 carol kernel: [ 8.601305] 26f8 b5000457 b9405660 370004c0 b9405660 36080100 f9401661 f9400c22 b5000062 Jul 8 15:18:24 carol kernel: [ 8.603883] 2718 f9401421 b4000061 320e0000 b9005660 b9405260 12166c00 b9005260 f9409a60 ... Full kern.log boot log: https://pastebin.com/zcpxB1HQ Please find attached the full armbianmonitor output here: https://pastebin.com/NkVAejC6 Any help is greatly appreciated!
  6. Just wanted to let you know that we collaborated with Mender and Armbian for RockPro64 is now fully supported by the Mender.io open source client-server manager for over-the-air software updates. It should be relatively straight-forward to exend this approach to other boards as well. https://mender.io/ https://github.com/mendersoftware/mender-convert/pull/103
  7. I am looking to build a stable applicance that is updateable on demand / over-the-air in an atomic way. Ideally, it uses a dual-partition setup, where the is an active rootfs and an inactive one. On update, a new rootfs is streamed directly to the inactive partition, the device reboots to the new rootfs and - if everything runs according to plan - the new rootfs is committed as the new active one. If the reboot fails, the device reverts to the previous (still active) rootfs. This functionality is very common with embedded devices, many using the Yocto project. I'd like to try to use Armbian, however, building the image from source with my own userpatches and include a software package like [swupdate](https://github.com/sbabic/swupdate) or [rauc](https://github.com/rauc/rauc/) for the update functionality. The challenge for me is mainly to get the correct disk image (dual partition and bootloader configuration). I was not able to find any documentation, guide or project that tries something similar, integrating an updater into the Armbian build process. Is anyone aware of other projects where I could get inspiration, or is this really a first?
  8. Thanks for the quick reply! I just ran the command with additional WIREGUARD=no for BRANCH=default, unfortunately it did not even start to work. The "board selection" pops up, and then the script exits: sudo ./compile.sh BOARD=rockpro64 PROGRESS_LOG_TO_FILE=yes KERNEL_ONLY=no KERNEL_CONFIGURE=no RELEASE=stretch BUILD_DESKTOP=no BRANCH=default WIREGUARD=no [ o.k. ] Using config file [ config-default.conf ] [ o.k. ] Command line: setting BOARD to [ rockpro64 ] ./compile.sh: line 57: BOARD=rockpro64: command not found [ o.k. ] Command line: setting PROGRESS_LOG_TO_FILE to [ yes ] [ o.k. ] Command line: setting KERNEL_ONLY to [ no ] [ o.k. ] Command line: setting KERNEL_CONFIGURE to [ no ] [ o.k. ] Command line: setting RELEASE to [ stretch ] [ o.k. ] Command line: setting BUILD_DESKTOP to [ no ] [ o.k. ] Command line: setting BRANCH to [ default ] [ o.k. ] Command line: setting WIREGUARD to [ no ] [ o.k. ] This script will try to update Already up to date. Already on 'master' Your branch is up to date with 'origin/master'. [ o.k. ] Preparing [ host ] [ o.k. ] Build host OS release [ bionic ] [ o.k. ] Syncing clock [ host ] >> GUI: Select the target board. >> select "rockpro64", <OK> [ error ] ERROR in function source [ main.sh:198 ] [ error ] Kernel branch not defined for this board [ default ] [ o.k. ] Process terminated note: line 57 in compile.sh is: `eval $parameter=\"$value\"` When running `sudo ./compile.sh BOARD=rockpro64 PROGRESS_LOG_TO_FILE=yes KERNEL_ONLY=no KERNEL_CONFIGURE=no RELEASE=stretch BUILD_DESKTOP=no WIREGUARD=no` without specifying the branch, the compilation is successful. What branch is used in this case? Although successful, there are still a lot of warnings in the `compilation.log`, mostly `warning: type qualifiers ignored on function return type [-Wignored-qualifiers]` and `note: offset of packed bit-field ‘MaxAMSDU’ has changed in GCC 4.4` At least for the latter, I guess according to the GCC release notes that is safe to ignore? See full compilation log here: compilation_WIREGUARD-no.log One additional question, if I may? When tinkering with the User provided image configuration script, is there a way to skip recompiling the kernel every time?
  9. Noob here, please excuse if I ask something obvious and feel free to just point me into the right direction. About a week ago, I was able to successfully build Armbian for RockPro64 in the standard Vagrant build environment, creating a bootable image using the compilation GUI without any special kernel configuration. I tried again yesterday, both with the GUI and the CLI command below, but the build process always fails: $ sudo ./compile.sh BOARD=rockpro64 PROGRESS_LOG_TO_FILE=yes KERNEL_ONLY=no KERNEL_CONFIGURE=no RELEASE=stretch BUILD_DESKTOP=no BRANCH=default ... CC [M] drivers/net/wireless/rockchip_wlan/rtl8723bu/core/rtw_mp_ioctl.o CC [M] drivers/net/wireless/rockchip_wlan/rtl8723bu/core/rtw_bt_mp.o LD [M] drivers/net/wireless/rockchip_wlan/rtl8723bu/8723bu.o LD drivers/net/wireless/built-in.o LD drivers/net/built-in.o LD drivers/built-in.o [ error ] ERROR in function compile_kernel [ compilation.sh:389 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated In the `compilation.log` there are two main errors. First example (occurs maybe 10+ times): In file included from drivers/net/wireless/rockchip_wlan/mvl88w8977/mlan/mlan.h:32:0, from drivers/net/wireless/rockchip_wlan/mvl88w8977/mlan/mlan_shim.c:26: drivers/net/wireless/rockchip_wlan/mvl88w8977/mlan/mlan_ioctl.h:1797:1: note: offset of packed bit-field ‘MaxAMSDU’ has changed in GCC 4.4 } MLAN_PACK_END ExtCap_t, *pExtCap_t; ^ Second example (occurs 50+ times): In file included from ./arch/arm64/include/asm/compat.h:25:0, from ./arch/arm64/include/asm/stat.h:23, from include/linux/stat.h:5, from include/linux/module.h:10, from drivers/net/wireless/rtl8812au/include/basic_types.h:76, from drivers/net/wireless/rtl8812au/include/drv_types.h:26, from drivers/net/wireless/rtl8812au/core/rtw_cmd.c:17: include/linux/sched.h:1211:1: warning: type qualifiers ignored on function return type [-Wignored-qualifiers] const struct sched_group_energy * const(*sched_domain_energy_f)(int cpu); ^~~~~ cc1: warning: unrecognized command line option ‘-Wno-cast-function-type’ Initially I was suspecting the virtualbox image, going back to the exact release I've been using last week (two updates from Vagrant since), but to no avail. After looking at Github issues, reading posts and sifting through the scripts, I got the build process working by explicitly using BRANCH="dev". I am especially wondering why it worked wihtout issues a week ago, but not anymore. Any recent changes? Might this have something to do with these ongoing changes? In that regard, I'd rather expect the "dev" branch to fail than the default one. Please find attached the various compilation.log files: compilation.log for BRANCH="default": https://pastebin.com/wMLiAHdA (compilation fails with error shown at the beginning) compilation.log for BRANCH="dev": https://pastebin.com/i5UXZZys (compilation successful) I'm thankful for any insights or pointers to getting a stable RockPro64 image, as I'd like to later customize it with additional software (definitely not there yet).