second core CPU power state depends on battery state at boot time

Bug #129812 reported by xbx
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

(using gutsy, but I think it was the same in feisty)

using a "Genuine Intel(R) CPU T2400 @ 1.83GHz"

if the computer was unplugged at boot time
 * both processors go to C3 when the laptop is unplugged. (1)
 * CPU0 goes to C2, CPU1 to C3 when the laptop is plugged in. (2)

whereas, if the computer was plugged at boot time
 * CPU0 goes to C3, CPU1 to C2 when the laptop is unplugged. (3)
 * both processors go to C2 when the laptop is plugged in. (4)

=> So it looks like CPU1 available powerstate are defined at boot time and never modified, whereas CPU0 changes when the laptop is plugged or unplugged.

---------
(1)
cat /proc/acpi/processor/CPU*/power
active state: C3
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
    C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
    C2: type[C2] promotion[C3] demotion[C1] latency[001] usage[00024024] duration[00000000000114130312]
   *C3: type[C3] promotion[--] demotion[C2] latency[057] usage[00112408] duration[00000000000645676141]
active state: C3
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
    C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
    C2: type[C2] promotion[C3] demotion[C1] latency[001] usage[00551884] duration[00000000002261918965]
   *C3: type[C3] promotion[--] demotion[C2] latency[057] usage[04377438] duration[00000000031179229264]

---------
(2)
 cat /proc/acpi/processor/CPU*/power
active state: C2
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
    C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
   *C2: type[C2] promotion[--] demotion[C1] latency[001] usage[00071033] duration[00000000000410369580]
active state: C3
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
    C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
    C2: type[C2] promotion[C3] demotion[C1] latency[001] usage[00565392] duration[00000000002326080358]
   *C3: type[C3] promotion[--] demotion[C2] latency[057] usage[04501678] duration[00000000031832189184]

---------
(3)
cat /proc/acpi/processor/CPU*/power
active state: C3
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
    C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
    C2: type[C2] promotion[C3] demotion[C1] latency[001] usage[00003896] duration[00000000000022791437]
   *C3: type[C3] promotion[--] demotion[C2] latency[057] usage[00024417] duration[00000000000235697781]
active state: C2
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
    C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
   *C2: type[C2] promotion[--] demotion[C1] latency[001] usage[00112419] duration[00000000001047405218]

---------
(4)
cat /proc/acpi/processor/CPU*/power
active state: C2
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
    C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
   *C2: type[C2] promotion[--] demotion[C1] latency[001] usage[00072639] duration[00000000000618470508]
active state: C2
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
    C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
   *C2: type[C2] promotion[--] demotion[C1] latency[001] usage[00070689] duration[00000000000656339622]

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. On what type of hardware, for example laptop model, did you notice this? Additionally, which specific version of the kernel are you running? Thanks in advance.

Changed in linux-source-2.6.22:
assignee: nobody → brian-murray
status: New → Incomplete
Revision history for this message
xbx (xavierb) wrote :

hi,

the laptop is an
        hp compaq nx9420
the kernel is
        Linux version 2.6.22-9-generic (buildd@palmer) (gcc version 4.1.3 20070718 (prerelease) (Ubuntu 4.1.2-14ubuntu1)) #1 SMP Fri Aug 3 00:50:37 GMT 2007 (Ubuntu 2.6.22-9.25-generic)

here is the full dmesg.

what other piece of info would you need?

Changed in linux-source-2.6.22:
assignee: brian-murray → ubuntu-kernel-team
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
xbx (xavierb) wrote :

fixed in 2.6.27

tested with the livecd for "Alpha5 for Intrepid Ibex 8.10".

I don't know for 2.6.26
but I do know that's it's not fixed in hardy.

Revision history for this message
xbx (xavierb) wrote :

fixed in 2.6.27!

tested with the livecd for "Alpha5 for Intrepid Ibex 8.10".

I don't know for 2.6.26
but I do know that's it's not fixed in hardy.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for testing and the update. I'm going to tentatively mark this "Fix Released" for Intrepid. If you notice any regressions prior to Intrepid's final release please feel free to reopen this by setting the status back to New. Unfortunately for Hardy i's unlikely this will be fixed with an SRU - http://wiki.ubuntu.com/StableReleaseUpdates . Thanks.

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.