Closed koolkhel closed 2 years ago
From my experience you can detect missing power by running coremark 2 or 3 times in a row. if the power adapter is too weak then the R4s would reboot
coremark did not produce an oops. Still happens sporadically, after a few hours of work. I've enabled panic on oops, it helps but still sometimes the device becomes unresponsive. Network LEDs remain lit and only a full power cycle helps.
I took a current OpenWRT snapshot that now apparently supports NanoPi R4S. Uptime is 60 hours already, no issues.
Good to hear that snapshots work well in your case. I would be curious to know the reason of the oops but on my side my R4s has uptime of more than 15 days with my builds as a router.
Hello!
I'm having quite regular OOPS on NanoPi R4S which later make all disk IO stop:
After that stuff like "touch 1" hang indefinitely, only a hard reboot helps.
I'm using:
Could that be a power issue? Every time that seems to be the clk_change_rate function which is suspicious.