This Article provides detail about syslog message seen below,

%PFE-3: fpc0 PFEBM: BEM0

The below log messages are seen on the device when it is coming up 

May 28 11:29:03 labroot:  %PFE-3: fpc0 PFEBM: BEM0
 

1. The log messages are expected when the device is booting up or when the FPC comes up.
2. This should not cause any impact .

Lab device logs seen after reboot :

May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 Ukern event counter Sock_tx init delayed
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 Ukern event counter Sock_rx init delayed
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 TVP_SYSCTL_NOT_SUPPORTED: sysctl hw.re.type not supported
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 PFEBM: BEM0
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 BME0 created
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 BRCM-VIRTUAL,pfe_virtual_module_init(),1447:brcm_virtual_mbb is set to 1
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 local_ioctl:510 PTP_FPGA_CFG_CTL_EXTRA_CYCLES: END 4
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 local_ioctl:518 PTP_FPGA_CHK_CFG_CTL_INIT: c4
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 local_ioctl:520 PTP_FPGA_CHK_CFG_CTL_INIT: 1
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 local_ioctl:681 PTP_FPGA_RESET_DISABLE
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 local_ioctl:670 PTP_FPGA_RESET_ENABLE reg_addr=94 IN
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 local_ioctl:681 PTP_FPGA_RESET_DISABLE
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 PIC: 0 S/W Init...
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 SCHED: Thread 4 (Module Init) aborted, hogged 5547 ms
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 CMLC: Command opcode 351 already present
May 30 14:47:02 jtac-qfx5200-32c-32q-r2051 fpc0 SCHED: Thread 4 (Module Init) ran for 1828 ms without yielding

 

Also please note if these log messages are not seen when the device is coming up or FPC is coming up, check for the log messages before the syslog is seen for the cause of FPC reboot.