PEL: New event log when receiving bad host PEL

Create a new event log/PEL when a PEL comes in from the host but it
isn't valid.

The PEL subsystem used is 'platform firmware' because the code won't
know which specific host subsystem it came from.  The severity is
unrecoverable as opposed to informational to make it easier to notice.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I933e5c82f1ef755c6266604fbdec6d0c1fe5b784
diff --git a/extensions/openpower-pels/manager.cpp b/extensions/openpower-pels/manager.cpp
index 40501a5..05ccb42 100644
--- a/extensions/openpower-pels/manager.cpp
+++ b/extensions/openpower-pels/manager.cpp
@@ -100,10 +100,27 @@
         }
         else
         {
-            log<level::ERR>("Invalid PEL found",
+            log<level::ERR>("Invalid PEL received from the host",
                             entry("PELFILE=%s", rawPelPath.c_str()),
                             entry("OBMCLOGID=%d", obmcLogID));
-            // TODO, make a whole new OpenBMC event log + PEL
+
+            AdditionalData ad;
+            ad.add("PLID", getNumberString("0x%08X", pel->plid()));
+            ad.add("OBMC_LOG_ID", std::to_string(obmcLogID));
+            ad.add("RAW_PEL_FILENAME", rawPelPath);
+            ad.add("PEL_SIZE", std::to_string(data.size()));
+
+            std::string asciiString;
+            auto src = pel->primarySRC();
+            if (src)
+            {
+                asciiString = (*src)->asciiString();
+            }
+
+            ad.add("SRC", asciiString);
+
+            _eventLogger.log("org.open_power.Logging.Error.BadHostPEL",
+                             Entry::Level::Error, ad);
         }
     }
     else