[lkml]   [2005]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: C4 non-strangeness [was: C4 strangeness [was Re: [PATCH] i386 No Idle HZ aka dynticks 051221]
    On Út 27-12-05 16:33:30, Dominik Brodowski wrote:
    > Hi,
    > On Tue, Dec 27, 2005 at 03:22:38PM +0100, Pavel Machek wrote:
    > > So... I guess I found out what is going on.
    > >
    > > When power is unplugged, X32 adds C4 state. When power is plugged, X32
    > > removes C4 state (behaviour Ted seen). When I load ipw2200, this
    > > behaviour stops, and I see everything up-to C4. Strange. I remember
    > > ipw had some problems with C3 and C4, perhaps this is related?
    > Nothing strange at all. The C-States are exported by the BIOS to the OS
    > using the _CST method/object/whatever. This can change on runtime. When the
    > BIOS recognizes it is on battery power, the _CST contains the C4 state, if
    > it is on AC power, the _CST doesn't contain it. The ACPI code follows what
    > it is told by the BIOS, for it has no chance to know about this additional
    > C-State if on AC power, and it wouldn't be wise to second-guess the BIOS.
    > Ipw does limit the max_cstate setting dynamically if it recognizes problems;
    > however I haven't seen _any_ such things lately on my own system. Might be
    > related to dyntick being _enabled_, though ;-)

    This was without dynticks... But why C4 availability no longer changes
    (between AC and battery power) with ipw2200 loaded? I'd understand
    higher C states being unavailable...
    Thanks, Sharp!
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-12-27 17:17    [W:0.020 / U:0.824 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site