<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Kernel microcode errors in messages file in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/kernel-microcode-errors-in-messages-file/m-p/3391054#M14235</link>
    <description>this is done at boot time, i think the script is located in /etc/init.d/microcode.&lt;BR /&gt;&lt;BR /&gt;as you might know, it is possible to update the microcode of your cpu to get rid of small bugs. this is a handy feature, as it saves cost for intel because they don't have to adjust their production process every time they find a bug.&lt;BR /&gt;&lt;BR /&gt;so, linux allows you to load this microcode cpu update when you boot, using the above startup script. i recommend taking a look at the script for more info.</description>
    <pubDate>Fri, 01 Oct 2004 02:24:06 GMT</pubDate>
    <dc:creator>dirk dierickx</dc:creator>
    <dc:date>2004-10-01T02:24:06Z</dc:date>
    <item>
      <title>Kernel microcode errors in messages file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-microcode-errors-in-messages-file/m-p/3391053#M14234</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I have fedora Linuix installed on Intel P4 single processor machine. Today I got the following message in /var/log/messages file:&lt;BR /&gt;&lt;BR /&gt;Sep 28 17:24:57 slate kernel: IA-32 Microcode Update Driver: v1.13 &lt;TIGRAN&gt;&lt;BR /&gt;Sep 28 17:24:57 kernel: microcode: No suitable data for cpu 0&lt;BR /&gt;&lt;BR /&gt;Can any body help to explain and resolve this problem.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/TIGRAN&gt;</description>
      <pubDate>Thu, 30 Sep 2004 15:37:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-microcode-errors-in-messages-file/m-p/3391053#M14234</guid>
      <dc:creator>john D_3</dc:creator>
      <dc:date>2004-09-30T15:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel microcode errors in messages file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-microcode-errors-in-messages-file/m-p/3391054#M14235</link>
      <description>this is done at boot time, i think the script is located in /etc/init.d/microcode.&lt;BR /&gt;&lt;BR /&gt;as you might know, it is possible to update the microcode of your cpu to get rid of small bugs. this is a handy feature, as it saves cost for intel because they don't have to adjust their production process every time they find a bug.&lt;BR /&gt;&lt;BR /&gt;so, linux allows you to load this microcode cpu update when you boot, using the above startup script. i recommend taking a look at the script for more info.</description>
      <pubDate>Fri, 01 Oct 2004 02:24:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-microcode-errors-in-messages-file/m-p/3391054#M14235</guid>
      <dc:creator>dirk dierickx</dc:creator>
      <dc:date>2004-10-01T02:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel microcode errors in messages file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-microcode-errors-in-messages-file/m-p/3391055#M14236</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Here is a link below which may throw some light&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=106894" target="_blank"&gt;http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=106894&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds&lt;BR /&gt;&lt;BR /&gt;Gopi</description>
      <pubDate>Mon, 04 Oct 2004 13:01:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-microcode-errors-in-messages-file/m-p/3391055#M14236</guid>
      <dc:creator>HGN</dc:creator>
      <dc:date>2004-10-04T13:01:25Z</dc:date>
    </item>
  </channel>
</rss>

