Completely eliminating the timer tick in modern Linux =5.0
The 1HZ tick can't be removed completely from all cpus otherwise we won't be able to keep any statistics. Instead what happens is that it is now run through a workqueue and you can now configure a housekeeping CPU that will handle all global workqueue tasks. See this commit for details.
It is also recommended to use nohz_full command-line parameter along with cpusets to manage the set of isolated cpus. You still need to let one of them (boot CPU by default) to be the housekeeping cpu.
Ubuntu AWS instance reachability check failed
If anybody has a similar problem: the ubuntu 14.04 is screwed and becomes brain dead if you restart it as it has DHCP problems. AWS support will ask you create a new instance and attach the volume (your initial volume which does not boot) and try to increase the timeout (it would be 300 by default). THIS DOES NOT HELP.
The ONLY way to make this work is to create a new instance with ubuntu 16.04 (or wtv is the latest/greatest) and attach your problematic volume as the secondary mount. Its a pain but AWS has to be blamed for giving users ubuntu 14.04 as an OS option when clearly it has problems.
Related Topics
How to Get Around the Linux "Too Many Arguments" Limit
How to Ask Bash for the Current Options
How to Initialize Raw Socket for Vlan Sniffing
Grep for String and Open at the Corresponding Line
Executable Object Files and Virtual Memory
Listing Files Using a Variable Filter
Copying Files from Multiple Directories into a Single Destination Directory
Retrieve Ipv4 and Ipv6 Nameservers Programmatically
Output Stdout and Stderr to File and Screen and Stderr to File in a Limited Environment
Why Would the Elf Header of a Shared Library Specify Linux as the Osabi
Linking a Dynamically Linked Executable with Ld
How to Properly Quote This Bash Pipeline for Watch
How to Increase Openfabrics Memory Limit for Torque Jobs
Hard Time Installing Ia32-Lib on MAC Osx