In recent years, Linux kernel, especially after 4.1, in the Bay Trail platform will be randomly suspended and crashed, pro-test j1900, freezing very frequent, and no symptoms before the crash, directly hung up, the console is not corresponding.
The problem has been bugzilla.kernel.org, from the beginning of 2015, until now, still not completely resolved, the temporary plan has several, but does not guarantee that it will work.
Summarize your own j1900-tested, potentially useful solution.
Scenario 1:
In kernel flag, add:
intel_idle.max_cstate=1
Tested, in Ubuntu 14.04, 15.10 Effective, power consumption will be slightly increased, but in Ubuntu 16.04 is invalid, still freezes, but the crash interval becomes longer.
Edit/etc/default/grub, add a line:
grub_cmdline_linux="intel_idle.max_cstate=1"
Scenario 2:
Kernel flag Plus:
processor.max_cstate=1 intel_idle.max_cstate=0
Or
processor.max_cstate=1
Without long-term testing, the effect is unknown. Reference documents
Scenario 3:
Kernel flag:
intel_idle.max_cstate=5
In Rc.local Plus:
Echo 1 >/sys/devices/system/cpu/intel_pstate/no_turboecho1 >/sys/devices/ system/cpu/cpu0/cpuidle/state3/Disableecho1 >/sys/devices/system/cpu/cpu1/cpuidle /state3/Disableecho1 >/sys/devices/system/cpu/cpu2/cpuidle/state3/Disable echo1 >/sys/devices/system/cpu/cpu3/cpuidle/state3/disable
Disable State3, in test, the effect is unknown.
Cpuidle state does not seem to be able to change after landing, always prompt permission denied, with Sudo also not.
Linux Crash/hang on Bay trail/j1900/n2940