nbj

Found the same problem regarding the odroid c2 in arch and hardkernel:http://forum.odroid.com/viewtopic.php?f=136&t=21520 https://archlinuxarm.org/forum/viewtopic.php?f=67&t=10420

Did a little more testing and found that it isn't resolved and that the cause for this problem is related to the "setenv nographics "1". If set to 0 there's no problem. Can anyone test? Thanks

Was able to compile from source and the problem is gone. Keep up the good work!!

Just to say that I can now compile u-boot and kernel successfully.

OK. I will wait then. Regards

I'm trying to build but it fails. Logs are attached. Can anyone help? Thanks. Regards Nuno output.tar.gz

Installed from Armbian_5.14_Odroidc2_Ubuntu_xenial_3.14.72. Tested in two different Odroid C2's. One with EMMC, the other with SD CARD and fully updated. Procedure: fallocate -l 2G /root/2GB.file cp /root/2GB.file /. After that all sort of erratic behavior from the board and eventually it crashes. In /var/log/kern.log: Aug 19 14:28:01 localhost kernel: [ 669.078129] INFO: rcu_preempt detected stalls on CPUs/tasks: { 3} (detected by 2, t=33627 jiffies, g=296, c=295, q=84431) Aug 19 14:28:01 localhost kernel: [ 669.083412] Task dump for CPU 3: Aug 19 14:28:01 localhost kernel: [ 669.083418] kthread_hdcp R running task 0 65 2 0x00000002 Aug 19 14:28:01 localhost kernel: [ 669.083425] Call trace: Aug 19 14:28:01 localhost kernel: [ 669.083438] [<ffffffc00108570c>] __switch_to+0x74/0x90 Aug 19 14:28:01 localhost kernel: [ 669.083446] [<ffffffc001820418>] __schedule+0x3e8/0x790 Aug 19 14:28:01 localhost kernel: [ 669.083451] [<ffffffc0018207f0>] schedule+0x30/0x88 Installed Hardkernel's Xenial minimal image (fully updated) for testing, and this problem doesn't exist. Regards Nuno

Your efforts are much appreciated! Keep up the good work

I don't mind compiling myself. My only problem is that I already have a fully configured/working system, and don´t want to start from scratch, so the best option would be the ability to use apt-get. I tried compiling on a PC, but the resulting image was not bootable. Should I try and do it on the Odroid itself?

For me it only survived the first reboot. After the reboot it kind of "froze" (responded to pings but no ssh or any other service I have running) while it was running and when I cold restarted it, the problem persisted. Solid blue LED

That was also my solution...

Hi, I have the same issue. If I do an apt-get update using the EMMC, it won't boot any more with a solid blue led. With SD card it boots normally after the update. Tried what glaucioklipel suggested with no luck. Even tried copying the entire boot partition from the SD card but got a boot loop. I´m using the Ubuntu xenial 5.14 image. Any help appreciated. Thanks Regards