VlaoMao 0 Posted March 8, 2018 Share Posted March 8, 2018 Hello! I followed build instruction from github, builded full OS image to flash to microSD and get kernel oops on boot (selected orangepiwin->dev(4.14.x)->xenial->server) log: https://pastebin.com/G4UtkGPR Possible to fix? Link to post Share on other sites More sharing options...
Igor 2301 Posted March 8, 2018 Share Posted March 8, 2018 33 minutes ago, VlaoMao said: Possible to fix? By who? This year? Today? What for? Have you noticed this? Link to post Share on other sites More sharing options...
VlaoMao 0 Posted March 8, 2018 Author Share Posted March 8, 2018 Just now, Igor said: Have you noticed this? Yes, I can read. can there be conjectures or thoughts that caused this? Link to post Share on other sites More sharing options...
Xalius 41 Posted March 8, 2018 Share Posted March 8, 2018 Can you post a boot log with earlyprintk enabled? There are about 7 seconds missing from it.... Link to post Share on other sites More sharing options...
VlaoMao 0 Posted March 8, 2018 Author Share Posted March 8, 2018 5 minutes ago, Xalius said: Can you post a boot log with earlyprintk enabled? There are about 7 seconds missing from it.... yes, i will try rebuild and post output here Link to post Share on other sites More sharing options...
VlaoMao 0 Posted March 8, 2018 Author Share Posted March 8, 2018 58 minutes ago, Xalius said: Can you post a boot log with earlyprintk enabled? There are about 7 seconds missing from it.... I rebuilded with debian, but log is still the same https://pastebin.com/rWLnrT28 Link to post Share on other sites More sharing options...
zador.blood.stained 764 Posted March 8, 2018 Share Posted March 8, 2018 [ 1.583064] WARNING: CPU: 0 PID: 29 at drivers/clocksource/arm_arch_timer.c:222 fsl_a008585_read_cntvct_el0+0x28/0x30 ... [ 1.595818] PC is at fsl_a008585_read_cntvct_el0+0x28/0x30 This is the "famous" A64 timer errata/bug: https://lists.denx.de/pipermail/u-boot/2016-November/271836.html Currently there are no 100% reliable ways to fix this, and it's not up to us to fix. [ 7.588166] Internal error: undefined instruction: 0 [#1] SMP Possibly DRAM instability or CPU underpowering. So DVFS tables and DRAM frequency need to be checked first by anyone who wants to investigate and fix this, assuming there are no HW issues. Link to post Share on other sites More sharing options...
Recommended Posts