Activity log for bug #516325

Date Who What changed Old value New value Message
2010-02-02 23:29:29 Alex Chiang bug added bug
2010-02-02 23:30:36 Alex Chiang bug watch added http://bugzilla.kernel.org/show_bug.cgi?id=15064
2010-02-02 23:30:36 Alex Chiang bug task added linux
2010-02-03 00:08:23 Bug Watch Updater linux: status Unknown Fix Released
2010-02-09 19:42:55 Stefan Bader linux (Ubuntu): importance Undecided Medium
2010-02-09 19:42:55 Stefan Bader linux (Ubuntu): status New Triaged
2010-02-09 19:43:21 Stefan Bader nominated for series Ubuntu Karmic
2010-02-09 19:43:21 Stefan Bader bug task added linux (Ubuntu Karmic)
2010-02-09 19:51:22 Stefan Bader linux (Ubuntu Karmic): importance Undecided Medium
2010-02-09 19:51:22 Stefan Bader linux (Ubuntu Karmic): status New Fix Committed
2010-02-09 19:51:22 Stefan Bader linux (Ubuntu Karmic): assignee Stefan Bader (stefan-bader-canonical)
2010-02-09 19:53:11 Stefan Bader linux (Ubuntu): status Triaged Fix Committed
2010-02-09 19:53:44 Stefan Bader linux (Ubuntu): assignee Andy Whitcroft (apw)
2010-02-09 19:56:42 Stefan Bader description Please backport the following patch into Karmic: http://lkml.org/lkml/2010/1/26/368 From: Len Brown <len.brown@intel.com> upstream in 2.6.33-rc: 5d76b6f6c17572e662f5c99c2023adae92100855 Refreshed here for 2.6.32.y, applies w/ offset back to 2.6.29.y. Linux has always ignored ACPI BIOS C2 with exit latency > 100 usec, and the ACPI spec is clear that is correct FADT-supplied C2. However, the ACPI spec explicitly states that _CST-supplied C-states have no latency limits. So move the 100usec C2 test out of the code shared by FADT and _CST code-paths, and into the FADT-specific path. This bug has not been visible until Nehalem, which advertises a CPU-C2 worst case exit latency on servers of 205usec. That (incorrect) figure is being used by BIOS writers on mobile Nehalem systems for the AC configuration. Thus, Linux ignores C2 leaving just C1, which is saves less power, and also impacts performance by preventing the use of turbo mode. http://bugzilla.kernel.org/show_bug.cgi?id=15064 SRU Justification: Impact: Not entering deeper C-states causes more heat and can cause systems to throttle or even to shut down. Fix: This has been backported from upstream and made it into 2.6.32.7 for Lucid. It looks simple enough to not cause regressions. --- Please backport the following patch into Karmic: http://lkml.org/lkml/2010/1/26/368 From: Len Brown <len.brown@intel.com> upstream in 2.6.33-rc: 5d76b6f6c17572e662f5c99c2023adae92100855 Refreshed here for 2.6.32.y, applies w/ offset back to 2.6.29.y. Linux has always ignored ACPI BIOS C2 with exit latency > 100 usec, and the ACPI spec is clear that is correct FADT-supplied C2. However, the ACPI spec explicitly states that _CST-supplied C-states have no latency limits. So move the 100usec C2 test out of the code shared by FADT and _CST code-paths, and into the FADT-specific path. This bug has not been visible until Nehalem, which advertises a CPU-C2 worst case exit latency on servers of 205usec. That (incorrect) figure is being used by BIOS writers on mobile Nehalem systems for the AC configuration. Thus, Linux ignores C2 leaving just C1, which is saves less power, and also impacts performance by preventing the use of turbo mode. http://bugzilla.kernel.org/show_bug.cgi?id=15064
2010-02-10 21:20:17 Launchpad Janitor linux (Ubuntu): status Fix Committed Fix Released
2010-02-11 15:29:17 Launchpad Janitor branch linked lp:ubuntu/linux-mvl-dove
2010-03-10 11:24:43 Launchpad Janitor branch linked lp:ubuntu/linux-ec2
2010-03-24 07:30:53 Martin Pitt tags verification-needed
2010-03-24 08:21:11 Launchpad Janitor branch linked lp:ubuntu/karmic-proposed/linux-mvl-dove
2010-03-24 08:24:14 Launchpad Janitor branch linked lp:ubuntu/karmic-proposed/linux-ec2
2010-03-31 23:13:18 Launchpad Janitor branch linked lp:ubuntu/linux-qcm-msm
2010-04-28 17:36:06 Launchpad Janitor linux (Ubuntu Karmic): status Fix Committed Fix Released
2011-02-03 13:52:23 Bug Watch Updater linux: importance Unknown Medium