Thanks. I never would have thought of that. These resets happen once or twice a week, so we’ll wait and see if that fixes it.
And Lieutenant, leave that poor holodeck alone.
Thanks. I never would have thought of that. These resets happen once or twice a week, so we’ll wait and see if that fixes it.
And Lieutenant, leave that poor holodeck alone.
Several days in. Still going strong.
If the C-state was causing the firmware to crash, why didn’t it generate any post codes or warnings?
Usually AER is pretty good about catching AGESA misbehavior
Seems that C-state was the issue all along. How strange that the motherboard’s firmware would crash because of it. Even stranger that itself, nor the kernel could detect the crash, even with AER.
I will mark this problem as solved. And I will re-open it if the anomalous resets come back.
Glad that fixed the issue. How old is your power supply? Some old power supplies had trouble with the lower power C-states not drawing enough causing the power supply to switch off.
Having some C-states enabled is better for power efficiency. See if your BIOS allows enabling some and experiment with that.