August 8, 201510 yr Unlike unRAID 5.0.6, I'm seeing all of my CPUs running at full speed [from the dashboard]. I'm used to seeing most of my CPUs down around 800MHz, but, they're all up at 2500-3100MHz. Does unRAID 6.0.1 not tell the CPUs to go to idle? BTW, CPU utilization shows 0%, but, I think that might be accurate. 'top' is giving me the same.
August 8, 201510 yr Community Expert Unlike unRAID 5.0.6, I'm seeing all of my CPUs running at full speed [from the dashboard]. I'm used to seeing most of my CPUs down around 800MHz, but, they're all up at 2500-3100MHz. Does unRAID 6.0.1 not tell the CPUs to go to idle? BTW, CPU utilization shows 0%, but, I think that might be accurate. 'top' is giving me the same. There have been reports that you always see 100% from the dashboard, but that it can be correct if you check via the command line.
August 11, 201510 yr Author There have been reports that you always see 100% from the dashboard, but that it can be correct if you check via the command line. Silly question; how do I check from the command-line? 'cat'ing /proc/cpuinfo showed all of the CPUs running at 2200MHz. This is slightly less than what's being reported on the dashboard, but, nowhere near as slow as unRAID 5.
August 11, 201510 yr Yeah, it's a bug that's been hanging about since the betas. LT have pretty much been unable/unwilling to fix it. It affects Intel Haswell chips mostly, and it seems to be something to do with the GUI holding the CPU frequency too high. It doesn't happen on AMD, it doesn't happen on Sandy Bridge, Ivy Bridge, Bay Trail, Atom.
August 11, 201510 yr The additional parameter in the boot menu fixes the issue for many users. It forces the kernel to not use the intel p state drivers, which seem overly eager to jump to higher speed tiers.
August 11, 201510 yr Author The additional parameter in the boot menu fixes the issue for many users. It forces the kernel to not use the intel p state drivers, which seem overly eager to jump to higher speed tiers. Tell me the parameter BRiT!
August 11, 201510 yr The additional parameter in the boot menu fixes the issue for many users. It forces the kernel to not use the intel p state drivers, which seem overly eager to jump to higher speed tiers. Tell me the parameter BRiT! Add this to syslinux.cfg intel_pstate=disable
Archived
This topic is now archived and is closed to further replies.