Comment by dmitrygr

14 hours ago

modifying source to avoid an assembly isntr isn't a fix... this need a compiler fix most likely, or a microcode fix, if possible.

9 comments

dmitrygr

Reply
whadawha  13 hours ago

Anyone have knowledge of whether microcode can be patched on consumer grade Intel CPUs?

  • bri3d  13 hours ago

    Yes? It is regularly; both the firmware or the OS can deliver updates depending on configuration. The Raptor Lake CPUs in question have gone through an enormous number of microcode revisions already due to quite famous voltage scaling issues; it's unclear if this errata is fallout from or related to a similar root cause or just another issue with the processor.

  • __patchbit__  12 hours ago

    At boot time, the following package provides the latest Intel CPU microcode data files on NetBSD.

      sysutils/intel-microcode-netbsd

    dmesg shows

      cpu 0: ucode 0xf0->0xf6
  cpu 1: ucode 0xf0->0xf6

  • throwaway2037  9 hours ago

    Why is this downvoted? (At the time of writing, the text is grey, so it has at least a few downvotes.)

    This is a good question. As others have noted below, yes, and sometimes you can see kernel logging on start-up when the microcode is loaded.

    • wtallis  4 hours ago

      It's a dumb question, because it's in reply to a comment that already implies the answer, and it's trivial to find an answer online in less time than it takes to post that question and wait for someone to supply an answer.

      The subject of CPU microcode update mechanisms is an interesting and relevant topic, but such a shallow, low-effort question is not a good way to promote interesting discussion on that topic.