PaceyIV

I think the watchdog have restarted my board this morning at 5.31 AM during battery recharge. Igor, your board is not available now. Do you have changed your ip address?

I modified my fstab according to the link that you provided me but I don't restart the board to apply the changes. I thought to apply at the first freeze, but with Armbian 5.32 the board is still up (uptime 7 days). The difference between Armbian 5.31 and 5.32 are only about cryptography?

My rootfs is on a sata hard disk. Here my fstab /dev/sda1 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 0 /dev/mmcblk0p1 /media/mmc ext4 defaults 0 0 /media/mmc/boot /boot none bind 0 0 /dev/sda4 /media/data ext4 defaults,noatime,nodiratime,commit=600 0 0 /var/swap none swap sw 0 0 What value I have to put as commit interval? 1? I have to disable log2ram? How can I do it?

I bought the first one. Before upgrading to the last kernel the board was quite stable uptime from a week to month. With the link I send you I can see my rpimonitor using Tor.

By board is powered by and external 5V power supply that I bought from Olimex and there is also a battery connected to it.

Uhm...Now that I enable watchdog I retry to upgrade my server to the new kernel and uboot. In my case the board crashes when I don't use it, I don't think there is something that I can do to break it down. Do you enable log2ram? (How can I stop receiving mail from it by cronjob?) And do you use rpimonitor?

Your board is still alive?

I use my board as a web server, the load is very low. There is always on apache, exim4, rpimonitor, minidlna, samba and flexget. At night there is transmission and some script that mirror some directory on google drive and idrive.

Uptime of two days with linux-dtb-next-sunxi linux-image-next-sunxi linux-u-boot-lime2-next version 5.25. The board restarts now after I cat /dev/watchdog

Yes, I've upgraded from the last available. The kernel was 4.9.7.

The board crashed again after 16 hours The log is available here http://sprunge.us/UbYN

Ok, I've installed it now. I restart the board and I cross my fingers

I've upgrade armbian to 5.31, now I have 2 freeze in 2 days Here my log http://sprunge.us/gUeO

No, I don't install it because I don't find any information about it. I do apt-get update but I still see the linux-dtb-next-sunxi and linux-image-next-sunxi, both for version 5.27

Where I can read the changelog about the last armbian release 5.27? Github shows only 5.24 https://github.com/armbian/build/releases and on the docs 5.25 https://docs.armbian.com/Release_Changelog/

After 10 days (I think!) the board freeze again. If I try to get some html page I've get the timeout error. If I try to connect to it by ssh using putty I get no error, only the black screen. Same behavior with the debug console. The strange thing is that the board responds to ping request (<= 2ms). Armbianmonitor available at link http://sprunge.us/MQJK

According to the template of rpimonitor that I found at this forum in some topic we have to check this if (/sys/power/axp_pmu/battery/amperage > 0) "Battery Discharging" else if (/sys/power/axp_pmu/battery/charging == 1) "Battery Charging" else "Battery Charged" This works at every combination of power source - Board powered through battery only - Board powered through DC-IN - Board powered through USB OTG # Battery info for Allwinner # kernel 4.4+ axp_dir="/sys/power/axp_pmu" if [[ -e "$axp_dir" ]]; then status_battery_connected=$(cat $axp_dir/battery/connected) if [[ "$status_battery_connected" == "1" ]]; then battery_current=$(cat $axp_dir/battery/amperage) status_battery_charging=$(cat $axp_dir/charger/charging) status_battery_charge=$(cat $axp_dir/battery/charge) battery_percent=$(cat $axp_dir/battery/capacity) # dispay charging / percentage if [[ "$battery_current" -gt "0" ]]; then status_battery_text=" discharging" elif [[ "$status_battery_charging" -eq "1" ]]; then status_battery_text=" charging" else status_battery_text=" charged" fi fi fi I've tested it with 4.8.4-sunxi

Thanks. This thing was in my todo list.

Yes!

Hi, there is something wrong with the configuration of your server. If I try to connect to http://armbian.com/I get the nginx wellcome page. You have to forward the traffic to www.armbian.com

After the Igor's post I switched to mainline kernel. I also installed the u-boot with the path of the DRAM_CLK I've seen the other difference in the patch but I don't understand it. The lan works properly for a while and then I have to restart the board to see the full speed (with the previous kernel and u-boot). The changes in the patch can produce this behavior? With the new kernel and uboot (http://beta.armbian.com/pool/main/l/linux-u-boot-lime2-next/linux-u-boot-next-lime2_5.24.161101_armhf.deb) I haven't seen net problems yet. Igor said that this has DRAM_CLK patch. I don't know if it has also the ethernet path.

It's Rev C, RTL8211CL. My actual uptime is 2 days and the speed is still fast.

The board freeze again: 4 hours from last reboot. Yesterday I run a memtester with 20 loops without any errors. In the evening I worked to restore rpi-monitor with the new kernel and I reboot the board. Here the updated armbianmonitor log http://sprunge.us/FVaS PS. The board is still up after 3 days.

I have manually create all the datasources and the templates (I've tried to use armbianmonitor-daemon without success with also the commands . /etc/init.d/armhwinfo query and env) but I don't find any information about how to create and maintain battery_peak. I've just made a link to /etc/armbianmonitor/datasources/battery_charge so I don't see the undefined value to battery. There is a tutorial with all the stuff in one place?

Ok. I've just install this http://beta.armbian.com/pool/main/l/linux-u-boot-lime2-next/linux-u-boot-next-lime2_5.24.161101_armhf.deb Now I wait a few days or weeks if the board freeze again or not. Thanks.