EP2C602 Smbios Firmware processor component error

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   AsRock Rack EP2C602
Dual Xeon E5-2690, Noctua NH-U12DXi4 fans
(8x8GB) 64GB DDR3
Corsair RM1000X Power Supply
NOTHING else, just doing a general POST test.  (Some other parts haven't arrived.)

System turns on and navigates BIOS just fine.

Under Event Logs -> View smbios Event Log, it shows 3 entries timestamped as of its first POST.  The first is a log area reset, the second is a chassis secure switch activated.  It's the THIRD that I'm writing about:

EFI 00021002 Minor

DESCRIPTION
Firmware processor component
encountered a communication
error.

I can't find anything about what this means, if it's a problem, or what it indicates might be bad.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
darlingm Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 14 Sep 2016 Status: Offline Points: 4	Post Options Post Reply Quote darlingm Report Post Thanks(0) Quote Reply Topic: EP2C602 Smbios Firmware processor component error Posted: 14 Sep 2016 at 11:38am
	AsRock Rack EP2C602 Dual Xeon E5-2690, Noctua NH-U12DXi4 fans (8x8GB) 64GB DDR3 Corsair RM1000X Power Supply NOTHING else, just doing a general POST test. (Some other parts haven't arrived.) System turns on and navigates BIOS just fine. Under Event Logs -> View smbios Event Log, it shows 3 entries timestamped as of its first POST. The first is a log area reset, the second is a chassis secure switch activated. It's the THIRD that I'm writing about: EFI 00021002 Minor DESCRIPTION Firmware processor component encountered a communication error. I can't find anything about what this means, if it's a problem, or what it indicates might be bad.

wardog Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447	Post Options Post Reply Quote wardog Report Post Thanks(0) Quote Reply Posted: 14 Sep 2016 at 3:27pm
	I believe if you place a graphics card in her you'll find this will subside.

darlingm Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 14 Sep 2016 Status: Offline Points: 4	Post Options Post Reply Quote darlingm Report Post Thanks(0) Quote Reply Posted: 15 Sep 2016 at 5:51am
	Wasn't planning on adding a graphics card, it's a non-graphical linux server. Is this an error that can be safely ignored? Or is something off with the integrated graphics?

wardog Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447	Post Options Post Reply Quote wardog Report Post Thanks(0) Quote Reply Posted: 15 Sep 2016 at 10:36am
	Scour the logs for EDAC and or mpc85xx . Also, dare I ask what kernel? https://sourceforge.net/p/bluesmoke/mailman/message/27294291/ Bluesmoke > EDAC > finally mainstream kernel http://bluesmoke.sourceforge.net/

snakedogman Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Oct 2016 Status: Offline Points: 1	Post Options Post Reply Quote snakedogman Report Post Thanks(0) Quote Reply Posted: 27 Oct 2016 at 1:15am
	Hi, I recently built a system very much like yours (many people seemed to be inspired by the "32 thread monster PC" article ;)) and I see the same log message in my UEFI. I have installed a Geforce GTX970 Graphics card. Running Windows 10 here. No idea what it means. Do you also have the issue that the system sometimes needs to go through the initial boot phase several times before starting the OS? Mine does this, ie start up the PC, after a couple of seconds I get the Asrock logo, then it goes black again (doesn't turn off) and then again the Asrock logo. Usually after the third time it boots to Windows just fine. Sometimes it boots to Windows immediately. I wondered if it was related to these log messages.