Bug 4478 - kernel patch for ASPM increases power use
Summary: kernel patch for ASPM increases power use
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2012-02-11 10:26 CET by José Jorge
Modified: 2012-12-02 14:32 CET (History)
0 users

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments

Description José Jorge 2012-02-11 10:26:18 CET
Since the last kernel update, the power use of my laptop idle went from 11W to 14W. It seems the kernel patch; which also comes with kernel 3.2.5, prevents the trick of boot option "pcie-aspm=force" to work, while not activating it on my hardware.

kernel 2.6.38.8-6 dmesg:

PCIe ASPM is forcedly enabled
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it

kernel 2.6.38.8-10 and 3.2.5 with Cauldron dmesg :

PCIe ASPM is forcedly enabled
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI _OSC control for PCIe not granted, disabling ASPM
Comment 1 Manuel Hiebel 2012-02-11 13:54:05 CET
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => tmb
Source RPM: (none) => kernel

Comment 2 José Jorge 2012-02-18 11:11:45 CET
Some more info, maybe I just report myself upstream? (but is this patch in the main tree?)

kernel 2.6.38.8-6 dmesg | grep OSC :

 pci0000:00: Requesting ACPI _OSC control (0x1d)
 pci0000:00: ACPI _OSC control (0x1d) granted
 pci0000:ff: Requesting ACPI _OSC control (0x1d)

kernel 2.6.38.8-10 dmesg | grep OSC :

 pci0000:00: Requesting ACPI _OSC control (0x1d)
 pci0000:00: ACPI _OSC control (0x1d) granted
 pci0000:ff: Requesting ACPI _OSC control (0x1d)
 pci0000:ff: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
Comment 3 Manuel Hiebel 2012-11-05 16:52:50 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 4 Manuel Hiebel 2012-12-02 14:32:18 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.