problem in the kernel package has been detected

Latest response

Hi,
I installed a RHEL 7.4 , and after installing I am getting a popup continuously in every 2-3 min, saying "A Problem in the Kernel package has been detected" .
I was looking into the o/p of /var/log/messages and trying to understand the root cause, but not able to understand. Below is the o/p of /var/log/messages:
[root@inbhdhcp215123 yum.repos.d]# tail -f /var/log/messages
Jun 10 12:24:06 localhost dbus-daemon: dbus[797]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
Jun 10 12:24:06 localhost dbus[797]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
Jun 10 12:24:06 localhost systemd: Starting Fingerprint Authentication Daemon...
Jun 10 12:24:06 localhost dbus[797]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun 10 12:24:06 localhost dbus-daemon: dbus[797]: [system] Successfully activated service 'net.reactivated.Fprint'
Jun 10 12:24:06 localhost systemd: Started Fingerprint Authentication Daemon.
Jun 10 12:24:06 localhost fprintd: Launching FprintObject
Jun 10 12:24:06 localhost journal: D-Bus service launched with name: net.reactivated.Fprint
Jun 10 12:24:06 localhost journal: entering main loop
Jun 10 12:24:16 localhost su: (to root) npandey on pts/1
Jun 10 12:24:36 localhost journal: No devices in use, exit
Jun 10 12:30:01 localhost systemd: Created slice User Slice of root.
Jun 10 12:30:01 localhost systemd: Starting User Slice of root.
Jun 10 12:30:01 localhost systemd: Started Session 5 of user root.
Jun 10 12:30:01 localhost systemd: Starting Session 5 of user root.
Jun 10 12:30:01 localhost systemd: Removed slice User Slice of root.
Jun 10 12:30:01 localhost systemd: Stopping User Slice of root.
Jun 10 12:30:18 localhost kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 3682)
Jun 10 12:30:18 localhost kernel: CPU0: Core temperature above threshold, cpu clock throttled (total events = 3681)
Jun 10 12:30:18 localhost kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 6065)
Jun 10 12:30:18 localhost kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 6066)
Jun 10 12:30:18 localhost kernel: mce: [Hardware Error]: Machine check events logged
Jun 10 12:30:18 localhost kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 6066)
Jun 10 12:30:18 localhost kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 6065)
Jun 10 12:30:18 localhost kernel: CPU2: Core temperature/speed normal
Jun 10 12:30:18 localhost kernel: CPU0: Core temperature/speed normal
Jun 10 12:30:18 localhost kernel: CPU0: Package temperature/speed normal
Jun 10 12:30:18 localhost kernel: CPU2: Package temperature/speed normal
Jun 10 12:30:18 localhost kernel: mce: [Hardware Error]: Machine check events logged
Jun 10 12:30:18 localhost kernel: CPU3: Package temperature/speed normal
Jun 10 12:30:18 localhost kernel: CPU1: Package temperature/speed normal
Jun 10 12:30:19 localhost sh: abrt-dump-oops: Found oopses: 1
Jun 10 12:30:19 localhost sh: abrt-dump-oops: Creating problem directories
Jun 10 12:30:19 localhost sh: abrt-dump-oops: Not going to make dump directories world readable because PrivateReports is on
Jun 10 12:30:20 localhost abrt-dump-oops: Reported 1 kernel oopses to Abrt
Jun 10 12:30:53 localhost abrt-server: Looking for kernel package
Jun 10 12:30:53 localhost abrt-server: Kernel package kernel-3.10.0-693.el7.x86_64 found
Jun 10 12:30:54 localhost dbus-daemon: dbus[797]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
Jun 10 12:30:54 localhost dbus[797]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
Jun 10 12:30:54 localhost dbus-daemon: dbus[797]: [system] Successfully activated service 'org.freedesktop.problems'
Jun 10 12:30:54 localhost dbus[797]: [system] Successfully activated service 'org.freedesktop.problems'
Jun 10 12:30:54 localhost abrt-server: Email address of sender was not specified. Would you like to do so now? If not, 'user@localhost' is to be used [y/N]
Jun 10 12:30:54 localhost abrt-server: Email address of receiver was not specified. Would you like to do so now? If not, 'root@localhost' is to be used [y/N]
Jun 10 12:30:54 localhost abrt-server: Sending an email...
Jun 10 12:30:54 localhost abrt-server: Sending a notification email to: root@localhost
Jun 10 12:30:54 localhost abrt-server: Email was sent to: root@localhost

Please provide some suggestion.
Thanks in Advance.

Responses

Looks like the system is overheating and you've got Machine Check Exceptions (hardware errors).

Check the CPU fan is running.

Failing that, log a ticket with the hardware vendor to check the MCEs.

I am having this same error, and now understand way. Thank you Neeraj and Jamie.