Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-17356

Add microcode_ctl to list of packages requiring a reboot

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • rhel-8.10
    • rhel-8.8.0, rhel-9.2.0
    • dnf-plugins-core
    • None
    • dnf-plugins-core-4.0.21-25.el8
    • None
    • Low
    • rhel-sst-cs-software-management
    • ssg_core_services
    • 20
    • 24
    • None
    • QE ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Bug Fix
    • Hide
      .The `yum needs-restarting --reboothint` command now recommends a reboot to update the CPU microcode

      To fully update the CPU microcode, you must reboot a system. Previously, when you installed the `microcode_ctl` package, which contains the updated CPU microcode, the `yum needs-restarting --reboothint` command did not recommend the reboot. With this update, the issue has been fixed, and `yum needs-restarting --reboothint` now recommends a reboot to update the CPU microcode.
      Show
      .The `yum needs-restarting --reboothint` command now recommends a reboot to update the CPU microcode To fully update the CPU microcode, you must reboot a system. Previously, when you installed the `microcode_ctl` package, which contains the updated CPU microcode, the `yum needs-restarting --reboothint` command did not recommend the reboot. With this update, the issue has been fixed, and `yum needs-restarting --reboothint` now recommends a reboot to update the CPU microcode.
    • Done
    • None

      When updating microcode_ctl package, the new microcode is automatically loaded as post-installation scriptlet.

      This leads to the kernel printing the following warning:
      [ +0.001340] x86/CPU: CPU features have changed after loading microcode, but might not take effect.
      [ +0.000097] x86/CPU: Please consider either early loading through initrd/built-in or a potential BIOS update.
      From microcode_ctl maintainer (@esyr), microcode reloading should be quite safe, but potentially it didn't get applied. Hence adding the package to "needs reboot" list may be wise.

              rhn-support-ppisar Petr Pisar
              rhn-support-rmetrich Renaud Métrich
              packaging-team-maint packaging-team-maint
              Jan Blazek Jan Blazek
              Mariya Pershina Mariya Pershina
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: