mcelog fails to start in VMware environments utilizing Ivy and Sandy Bridge CPUs
This document (7004434) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 11 Service Pack 3
Situation
mcelog fails to start on virtual machines in VMware environments equipped with Ivy or Sandy Bridge CPUs. The error messages seen are:
/var/log/boot.msg:
/var/log/boot.msg:
mcelog start/var/log/mcelog:
Starting mcelog... failed
startproc: exit status of parent of /usr/sbin/mcelog: 1
mcelog: Failed to set imc_log on cpu 0
: No such file or directory
Resolution
Please apply the latest mcelog package. (mcelog-1.0.2013.01.18.0.15.1 or later)
zypper update mcelog
zypper update mcelog
Cause
When the icm log is tried to get activated the virtualized CPU returns an error.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7004434
- Creation Date: 23-Oct-2013
- Modified Date:28-Sep-2022
-
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
