Jump to content

NanoPi M4V2 randomly turning off


Oleg Dvortsov

Recommended Posts

Armbianmonitor:

Hi, I'm new to Linux and Armbian, I need your help. My Nanopi M4 V2 freezes periodically and I can’t understand the reason.

I am using Armbian Buster with Kernel 5.4.2. On board also used 4x SATA HAT for NanoPi M4.

 

I still can’t show the system log before it froze again. But now in the system log more than 2 hours the same thing is repeated:

 

Mar 13 14:34:50 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: 01 03 0c 00
Mar 13 14:34:54 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: writing
Mar 13 14:34:54 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: 01 03 0c 00
Mar 13 14:34:58 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: writing
Mar 13 14:34:58 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: 01 03 0c 00
Mar 13 14:35:01 AsProDent-NAS CRON[5306]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 13 14:35:02 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: writing
Mar 13 14:35:02 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: 01 03 0c 00
Mar 13 14:35:06 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: writing
Mar 13 14:35:06 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: 01 03 0c 00
Mar 13 14:35:10 AsProDent-NAS brcm_patchram_plus_rk3399[1238]: writing

 

Edited by Oleg Dvortsov
Link to comment
Share on other sites

Last I checked, there were some outstanding stability issues with the M4V2 that have yet to be resolved. Current thoughts are that U-Boot is not training the RAM correctly which results in crashes/freezes once Linux is booted, but this is uncertain.

Link to comment
Share on other sites

Hey there,

I have a NanoPiM4v2 with the SATA-Hat and I'm powering it using a standard ATX PSU.

The NanoPi "turns off" after about 8-48 hours of uptime. When this happens, the "Heartbeat"-LED turns off, while all others stay normal.

The NanoPi doesn't actually power off however, as I need to long-press the power button to turn it off completely, before turning it on again.

I've tried checking the logs, but they all seem normal until they just cut off.

Link to comment
Share on other sites

I get the same problem with Kernel 5.4.x on a NanoPi M4v2. I switched for tests to 4.4.x and there is working stable.

 

Did your logs getting spammed with this too? I got this every 4s.

Apr  6 14:47:33 nanopi brcm_patchram_plus_rk3399[1498]: writing
Apr  6 14:47:33 nanopi brcm_patchram_plus_rk3399[1498]: 01 03 0c 00

 

Edited by Dyfcom
Link to comment
Share on other sites

I got the same problem with the same setup. In v. 5.4.28 is still this problem.

 

On 3/14/2020 at 6:11 AM, Neko May said:

Last I checked, there were some outstanding stability issues with the M4V2 that have yet to be resolved. Current thoughts are that U-Boot is not training the RAM correctly which results in crashes/freezes once Linux is booted, but this is uncertain.

 

So, we as new armbian user can only wait for a stable version or downgrade to 4.4?

Link to comment
Share on other sites

22 hours ago, Dyfcom said:

I get the same problem with Kernel 5.4.x on a NanoPi M4v2. I switched for tests to 4.4.x and there is working stable.

 

Did your logs getting spammed with this too? I got this every 4s.


Apr  6 14:47:33 nanopi brcm_patchram_plus_rk3399[1498]: writing
Apr  6 14:47:33 nanopi brcm_patchram_plus_rk3399[1498]: 01 03 0c 00

 

The crash didnt occur since I opened the thread, and I'm also suspecting its caused by my really sketch PSU set up.

I also do not have the same errors as you in my log.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines