Fan KunPeng Posted March 4, 2019 Share Posted March 4, 2019 I get kernel panic from TTL: espressobin login: [26830.163585] Internal error: synchronous parity or ECC error: 86000018 [#1] PREEMPT SMP [26830.168894] Modules linked in: zstd zram zsmalloc bridge stp llc sch_fq_codel ip_tables x_tables mv88e6xxx dsa_core [26830.179650] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.20-mvebu64 #5.75 [26830.186812] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT) [26830.193445] pstate: 60000085 (nZCv daIf -PAN -UAO) [26830.198382] pc : need_update+0x0/0xb0 [26830.202138] lr : quiet_vmstat+0x4c/0x60 [26830.206076] sp : ffffff8008f73e80 [26830.209480] x29: ffffff8008f73e80 x28: 0000000007ed0018 [26830.214946] x27: 0000000000000000 x26: ffffff8008f826c0 [26830.220411] x25: 0000000000000000 x24: 000018670e807e00 [26830.225877] x23: 0000000000000000 x22: 0000186738b3b700 [26830.231343] x21: 0000186738b3b700 x20: 0000000000000000 [26830.236809] x19: ffffffc03ffbed08 x18: 0000000000000000 [26830.242273] x17: 0000000000000000 x16: 0000000000000000 [26830.247740] x15: 0000000000000400 x14: 0000000000000400 [26830.253205] x13: 0000000000000000 x12: 0000000000000001 [26830.258671] x11: 0000000000037708 x10: 0000000000000910 [26830.264136] x9 : ffffff8008f73e40 x8 : ffffff8008f83030 [26830.269601] x7 : 0000000000000000 x6 : 0000000000000000 [26830.275067] x5 : 0000004037055000 x4 : ffffff80090336c8 [26830.280532] x3 : 0000000000000000 x2 : 0000000000000001 [26830.285999] x1 : 0000004037055000 x0 : 0000000000000000 [26830.291467] Process swapper/0 (pid: 0, stack limit = 0x000000006512fe99) [26830.298363] Call trace: [26830.300876] need_update+0x0/0xb0 [26830.304283] tick_nohz_idle_stop_tick+0xb8/0x240 [26830.309029] do_idle+0x1c4/0x298 [26830.312343] cpu_startup_entry+0x24/0x28 [26830.316379] rest_init+0xd0/0xe0 [26830.319694] start_kernel+0x3ec/0x418 [26830.323456] Code: 910003fd 97ffff11 a8c17bfd d65f03c0 (a9bd7bfd) [26830.329733] ---[ end trace ea6ec43db8163ab5 ]--- [26830.334475] Kernel panic - not syncing: Attempted to kill the idle task! [26830.341372] SMP: stopping secondary CPUs [26830.345409] Kernel Offset: disabled [26830.348990] CPU features: 0x0,2080200c [26830.352840] Memory Limit: none [26830.355981] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- I used Ubuntu 18.04.1 LTS armbian with 4.19.20-mvebu64 kernel. U-Boot info: U-Boot 2018.03-devel-18.12.3-gc9aa92c-dirty (Feb 18 2019 - 23:13:53 -0500) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU 1000 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 800 [MHz] DRAM: 1 GiB Link to comment Share on other sites More sharing options...
Fan KunPeng Posted March 20, 2019 Author Share Posted March 20, 2019 stable after I changed cpu scale cpufreq-set -g performance 1 Link to comment Share on other sites More sharing options...
Jens Bauer Posted June 22, 2019 Share Posted June 22, 2019 On 3/4/2019 at 9:11 AM, Fan KunPeng said: Model: Marvell Armada 3720 Community Board ESPRESSOBin Which board are you using ? Link to comment Share on other sites More sharing options...
Fan KunPeng Posted July 7, 2019 Author Share Posted July 7, 2019 On 6/23/2019 at 6:46 AM, Jens Bauer said: Which board are you using ? ESPRESSOBin V5 1 Link to comment Share on other sites More sharing options...
Jens Bauer Posted July 7, 2019 Share Posted July 7, 2019 I was asking for the board (version) because there's difference between the first boards and the latest. As far as I understand, they fixed some of the erratic RAM behaviours, but the RAM may still be prone to EMI, so you may want to drop the board inside some metal-box to help stabilize it a little. That said, if your problem happened at the same point always, it's likely not some random EMI that causes it. I did have some problems with Xenial and in the beginning also Bionic, but now I seem to have a stable Bionic (the 5.75 image; eg. 4.19.20). Also make sure if you use SATA, that you do not use a cheap SATA-cable (eg. those that come with port multipliers). That's one point you certainly don't want to save a few bucks. 'reboot' seem to be more stable in Bionic, but it seems that after the board restarts, I sometimes still have to interrupt the boot at the timout-prompt and type 'reset' in order to get a proper hardware initialization. -Not much helpful information on your issue, but it's important to know the board version as it may make a big difference. =) Link to comment Share on other sites More sharing options...
ebin-dev Posted July 7, 2019 Share Posted July 7, 2019 @Fan KunPeng Are you using the latest boot loader ? 1 Link to comment Share on other sites More sharing options...
Recommended Posts