Temporarily remove label vs frutype mismatch trace
The OCC will report the IO Ring temperature with a label type of 0xC0,
which indicates processor core, and a unique fru_type (0x09).
In order to avoid spamming the journal with an error message before the
IO ring temperature support is added, remove the trace that complains
when the fru_type for a 0xC0 sensor isn't 0x00 (processor core).
It wasn't just changed to debug since it would fill the journal if
anyone ever turned on debug traces.
A future commit will add IO ring temperature support, and then maybe
this check can be put back in.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I68300087a5cd27b3b549ac097b6b73176a87a216
diff --git a/occ_manager.cpp b/occ_manager.cpp
index ea66cd4..4b5df04 100644
--- a/occ_manager.cpp
+++ b/occ_manager.cpp
@@ -283,10 +283,7 @@
{
if (fruTypeValue != processorCore)
{
- log<level::ERR>(fmt::format("readTempSensors: Fru type "
- "error! fruTypeValue = {}) ",
- fruTypeValue)
- .c_str());
+ // TODO: support IO ring temp
continue;
}