Correct pinhole reset logic for chassis state
The BMC state manager had the logic corrected to check for 0 to indicate
pinhole reset, 1 is NOT pinhole reset. The Chassis state manager also
needed a change. Correcting this now.
Trace if pinholse reset was the cause in the else leg.
See: 2e352a21b64c6dcfe3bea980ff459d99f355828f
Tested:
Rainier 2S4U
Power on.
Remove input power to all four power supplies.
Apply power to all four power supplies.
Wait for BMC Ready.
Verify Blackout (110000AC) error logged.
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Change-Id: I3d8f7669627a78232dd0d5202447f488ef71a510
diff --git a/chassis_state_manager.cpp b/chassis_state_manager.cpp
index 128672f..1da1130 100644
--- a/chassis_state_manager.cpp
+++ b/chassis_state_manager.cpp
@@ -140,8 +140,9 @@
setStateChangeTime();
+ // 0 indicates pinhole reset. 1 is NOT pinhole reset
if (phosphor::state::manager::utils::getGpioValue(
- "reset-cause-pinhole") != 1)
+ "reset-cause-pinhole") != 0)
{
if (standbyVoltageRegulatorFault())
{
@@ -152,6 +153,10 @@
report<Blackout>();
}
}
+ else
+ {
+ info("Pinhole reset");
+ }
}
}
}