I referred to this page while upgrading my fedora 23 to 25 (in a dual boot side by side with Windows 7) :DNF_system_upgradeHowever, it seems that my upgrade is not fully successful.When I enter uname -r into terminal, I am receiving this:4.9.8-201.fc25.i686When I enter cat /etc/fedora-release, I am receiving this:Fedora release 25 (Twenty Five)And even more confusing is that when I enter rpm -q kernel, I am receiving this:kernel-4.9.7-101.fc24.i686 kernel-4.9.7-201.fc25.i686kernel-4.9.8-201.fc25.i686The reason I think the upgrade was not successful is that after reboot there are some symptomatic issues mentioned below:(i) Some complaint about systemd-modules-load.service during reboot which I think is related to the upgrade even though it is not resulting into complete failure of not being able to enter the workspace. To be specific, the result of entering systemctl status systemd-modules-load.service into terminal is: systemd-modules-load.service - Load Kernel Modules    Loaded: loaded  (/usr/lib/systemd/system/systemd-modules-load    Active: failed  (Result: exit-code) since Thu 2017-02-09 19:0       Docs: man:systemd-modules-load.service(8)             man:modules-load.d(5)   Process: 696 ExecStart=/usr/lib/systemd/systemd-modules-load   Main PID: 696  (code=exited, status=1/FAILURE)Feb 09 19:00:58 localhost.localdomain systemd1: Starting Load Feb 09  19:00:58 localhost.localdomain systemd1: systemd-modul Feb 09  19:00:58 localhost.localdomain systemd1: Failed to sta Feb 09  19:00:58 localhost.localdomain systemd1: systemd-modul Feb 09  19:00:58 localhost.localdomain systemd1: systemd-modul(ii):When entering systemctl status mcelog into command line, I am getting: mcelog.service - Machine Check Exception Logging Daemon    Loaded:  loaded (/usr/lib/systemd/system/mcelog.service; enabled; vendor  preset: enabled)    Active: active (running) since Thu 2017-02-09  21:33:44 MST; 5min ago  Main PID: 790 (mcelog)      Tasks: 1 (limit: 4915)    CGroup: /system.slice/mcelog.service             790 /usr/sbin/mcelog --ignorenodev --daemon --foregroundFeb 09 21:37:09 localhost.localdomain mcelog[790]: Hardware event.  This is not a software error. Feb 09 21:37:09 localhost.localdomain  mcelog[790]: MCE 1 Feb 09 21:37:09 localhost.localdomain mcelog[790]:  CPU 3 THERMAL EVENT TSC 845761d8f5 Feb 09 21:37:09  localhost.localdomain mcelog[790]: TIME 1486701429 Thu Feb  9 21:37:09  2017 Feb 09 21:37:09 localhost.localdomain mcelog[790]: Processor 3  below trip temperature. Throttling disabled Feb 09 21:37:09  localhost.localdomain mcelog[790]: STATUS 88030002 MCGSTATUS 0 Feb 09  21:37:09 localhost.localdomain mcelog[790]: MCGCAP c07 APICID 3  SOCKETID 0 Feb 09 21:37:09 localhost.localdomain mcelog[790]: CPUID  Vendor Intel Family 6 Model 42 Feb 09 21:37:09 localhost.localdomain  mcelog[790]: mcelog: warning: 16 bytes ignored in each record Feb 09  21:37:09 localhost.localdomain mcelog[790]: mcelog: consider an update(iii)In fact, I am able to do my regular stuff (e.g. programming in python etc.) successfully in it with a sounding desktop environment and internet access. However, All cpus (namely 0, 1, 2 and 3) of the computer are getting heated more than usual and it will result in an automatic shutdown due to excessive temperatures. Hints:It is related to Kernel-core-4.9.8.201.fc25.i686 package as I am receiving constant notification that the issue cannot be reported and most likely it does not have to do with software.
How to fix a Fedora upgrade when encountered with systemd-modules-load.service issue?
fedora;systemd;upgrade;dnf