[indiana-discuss] b111a: Power Management and nwam-issue ?

Brian Ruthven - Solaris Network Sustaining - Sun UK Brian.Ruthven at Sun.COM
Tue Apr 28 02:55:02 PDT 2009


I was following this thread and finally got round to checking my laptop 
(Tosh Tecra M10). Sure enough, it runs constantly at 2261MHz according 
to powertop. Pressing "p" as indicated seems to have made no difference. 
So I dug out the mail below and compared my power.conf to what is below. 
Strangely, I find two lines I wasn't expecting:

cpupm disable
cpupm enable

Which takes preference? Is it top-down parsing, or does one take higher 
precedence than the other?

My history is this:
    Installed 2008.11rc2 (all I had handy at the time)
    upgrade to snv-109
    upgrade to snv-111a

I still have all the previous boot environments (including a snapshot I 
took manually just after booting the original install the first time). 
beadm list gives:

    # beadm list
    BE          Active Mountpoint Space   Policy Created         
    --          ------ ---------- -----   ------ -------         
    opensolaris -      -          7.30M   static 2009-03-24 10:42
    snv-101a    -      -          286.90M static 2009-03-24 16:33
    snv-109     -      -          20.23M  static 2009-03-25 10:10
    snv-111a    NR     /          9.56G   static 2009-04-24 12:56


Checking the previous BEs, I find this:

    Each BE has both a power.conf and power.conf-Orig
    Each power.conf-Orig has the line "cpupm enable".
    opensolaris, 101a and 109 have power.conf saying "cpupm disable".
    snv-111a has both enable and disable lines.

Can anybody shed any light on this please? In my opinion, this sounds 
like an installer bug deciding between the enable of power.conf-Orig and 
the pre-existing value of disable.

We could discuss why my original install had it disabled, but at the end 
of the day, any admin could disable it and a subsequent upgrade could 
leave the power.conf file in an inconsistent state (at least it's not 
clear to me which is taking preference) assuming this is some kind of 
upgrade bug.

I feel this is a new bug (can't spot anything quickly on bugs.osol.org) 
but if somebody could verify it or point me to an existing one, I'd be 
grateful.

I can supply any files / output from any of the BEs above if necessary.

Thanks,
Brian


Brock Pytlik wrote:
> Mark Haywood wrote:
>> [snip]
>> Could you provide the contents of /etc/power.conf as well? Thanks!
>>
> Sure:
> #
> # Copyright 1996-2002 Sun Microsystems, Inc.  All rights reserved.
> # Use is subject to license terms.
> #
> #pragma ident   "@(#)power.conf 2.1     02/03/04 SMI"
> #
> # Power Management Configuration File
> #
>
> device-dependency-property removable-media /dev/fb
> autopm                  default
> autoS3                  default
> cpu-threshold           1s
> # Auto-Shutdown         Idle(min)       Start/Finish(hh:mm)     Behavior
> autoshutdown            30              9:00 9:00               
> noshutdown
> cpupm  enable
>
> Brock
>>>
>>>
>>>
>>>
>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> indiana-discuss mailing list
>>>> indiana-discuss at opensolaris.org
>>>> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>>>
>>
>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

-- 
Brian Ruthven                                        Sun Microsystems UK
Solaris Revenue Product Engineering             Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG




More information about the indiana-discuss mailing list