Forum
Replies (3)
  • You Reply:

    Hi Beta.Saa

     

    I agree, disabling C-States entirely would not be a good solution - like you I use my Sigma as a 24x7 server, and I purchased it mainly because of the high energy efficiency

     

    Please see my other reply below - I didn't disable C-States entirely, I just changed the limit from 10 to 7

    I assume the difference in energy consumption between C-States 10 and 7 is probably very small

     

  • You Reply:

    Sorry for the slow reply, I've been very busy on a project at work

     

    Just to clarify - I did not disable C-States in the BIOS, I changed the C-State limit

     

    The setting is located here in the BIOS:

    Chipset - System Agent (SA) Configuration - TCSS setup menu - Tc C-State Limit

        Changed from default (10) to 7

     

    There's another setting for Link Power Management, I can't remember if it was enabled by default or if I set it myself when I first got the machine, but I also disabled that in the BIOS:

    Chipset - PCH-IO Configuration - SATA Configuration - Aggressive LPM Support

        Set to Disable

  • You Reply:

    Thanks for the reply - there is no obvious impact, usage of the OS is normal.

     

    My understanding is these errors are a way for the firmware/ACPI to report hardware errors that aren't reported to the OS kernel (un-notified hardware errors that occurred in a previous boot).

     

    In the early days of using the device I had some very occasional intermittent freezes maybe once every 2-3 weeks. But since changing the C-states settings in the BIOS to prevent the CPU going into very deep sleep states, and ensuring Linux loads the latest intel microcode firmware, it's been very stable.

     

    I'm still interested to know what this SOC Firmware Error is, possibly it's related to one of the previous freezes?