<?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 Need some information of Core i7, Shutting down cores in Linux and C states in Mobile and Desktop Processors</title>
    <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Need-some-information-of-Core-i7-Shutting-down-cores-in-Linux/m-p/248345#M3336</link>
    <description>&lt;P&gt;I am doing some experiments with the i7 and Linux 2.6.30. This question has to with Core i7 and linux.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I enable the C6 state in the bios and have a wattmeter that says that the wattage at idle is around 186 watts when all cores are Active. I can independently see them being much of the time in C6 state via a software.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I shut down the cores using echo "0" &amp;gt; /sys/devices/system/cpu/cpuX/online where X is the core i want to shut down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But then the wattage shoots upto 196 Watts, which i am inferring implies that the shut down core now goes into a C1 sleep state rather than C6 state. Is this a problem with linux or with the processor?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A related problem: Why does some USB devices prevent i7 processor to get into C6 states? I have a wattsup-pro device and whenever i start reading data from it, the processor mysteriously only runs in C0-C1 state, but usually when the reading is off it runs nicely in C6 state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to zero onto the reason why this happen. I couldn't find any i7 dedicated developer forums so i am posting it here. Any information or direction to someone who knows this will be most appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for reading.&lt;/P&gt;</description>
    <pubDate>Sat, 05 Dec 2009 10:35:24 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2009-12-05T10:35:24Z</dc:date>
    <item>
      <title>Need some information of Core i7, Shutting down cores in Linux and C states</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Need-some-information-of-Core-i7-Shutting-down-cores-in-Linux/m-p/248345#M3336</link>
      <description>&lt;P&gt;I am doing some experiments with the i7 and Linux 2.6.30. This question has to with Core i7 and linux.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I enable the C6 state in the bios and have a wattmeter that says that the wattage at idle is around 186 watts when all cores are Active. I can independently see them being much of the time in C6 state via a software.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I shut down the cores using echo "0" &amp;gt; /sys/devices/system/cpu/cpuX/online where X is the core i want to shut down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But then the wattage shoots upto 196 Watts, which i am inferring implies that the shut down core now goes into a C1 sleep state rather than C6 state. Is this a problem with linux or with the processor?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A related problem: Why does some USB devices prevent i7 processor to get into C6 states? I have a wattsup-pro device and whenever i start reading data from it, the processor mysteriously only runs in C0-C1 state, but usually when the reading is off it runs nicely in C6 state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to zero onto the reason why this happen. I couldn't find any i7 dedicated developer forums so i am posting it here. Any information or direction to someone who knows this will be most appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for reading.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Dec 2009 10:35:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Need-some-information-of-Core-i7-Shutting-down-cores-in-Linux/m-p/248345#M3336</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2009-12-05T10:35:24Z</dc:date>
    </item>
  </channel>
</rss>

