praseodymium reported high load, top shows
top - 14:20:37 up 73 days, 20:36, 1 user, load average: 71.78, 72.49, 58.23 Tasks: 193 total, 31 running, 159 sleeping, 0 stopped, 3 zombie %Cpu(s): 9.1 us, 90.2 sy, 0.0 ni, 0.5 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st KiB Mem: 16355812 total, 15461452 used, 894360 free, 221308 buffers KiB Swap: 976316 total, 0 used, 976316 free. 8399008 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 30718 root -2 0 0 0 0 R 100.0 0.0 28:45.88 acpi_pad/2 30724 root -2 0 0 0 0 R 100.0 0.0 28:42.36 acpi_pad/8 30725 root -2 0 0 0 0 R 100.0 0.0 28:44.01 acpi_pad/9 30715 root -2 0 0 0 0 R 100.0 0.0 28:48.33 acpi_pad/0 30720 root -2 0 0 0 0 R 100.0 0.0 28:45.46 acpi_pad/4 30723 root -2 0 0 0 0 R 100.0 0.0 28:44.25 acpi_pad/7 30719 root -2 0 0 0 0 R 100.0 0.0 28:47.30 acpi_pad/3 30722 root -2 0 0 0 0 R 100.0 0.0 28:42.94 acpi_pad/6 30716 root -2 0 0 0 0 R 100.0 0.0 28:45.94 acpi_pad/1 30721 root -2 0 0 0 0 R 100.0 0.0 28:45.04 acpi_pad/5 30747 root -2 0 0 0 0 R 100.0 0.0 28:40.92 acpi_pad/10
we've seen something similar before in T110202: re-seat power cord for Nembus and http://serverfault.com/questions/561190/unusual-load-average-for-an-idle-workstation seems to suggest acpi_pad module should be disabled altogether