Add kernel debug trace to Invalid IPC Message Errors

  - There is an extremly intermittent situation
    where on a system with no IPC message passing
    the INTRP will receive an IPC message from the
    kernel. To debug why this is happening, the
    printk buffer is being added to the errorlog to
    help debug this problem the next time it occurs

Change-Id: Iaec648fa6a640cdef6e125a6cafb92c5a37c6257
CQ: SW452174
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/61214
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/70873

src/usr/intr/intrrp.C

@@ -5,7 +5,7 @@
 /*                                                                        */
 /* OpenPOWER HostBoot Project                                             */
 /*                                                                        */
-/* Contributors Listed Below - COPYRIGHT 2011,2018                        */
+/* Contributors Listed Below - COPYRIGHT 2011,2019                        */
 /* [+] International Business Machines Corp.                              */
 /*                                                                        */
 /*                                                                        */
@@ -56,6 +56,7 @@
 #include <p9_misc_scom_addresses.H>
 #include <p9n2_misc_scom_addresses_fld.H>
 #include <util/utilmbox_scratch.H>
+#include <errl/errludprintk.H>
 
 using namespace INTR;
 using namespace TARGETING;
@@ -990,6 +991,9 @@ void IntrRp::msgHandler()
                              KernelIpc::ipc_data_area.msg_queue_id,
                              l_xirr_pir
                             );
+                        //Add the printk to give more data as to how we got
+                        // in this situation
+                        ERRORLOG::ErrlUserDetailsPrintk().addToLog(l_err);
                     }
                     else
                     {