proposal: set default lid state to S3, performance/economy Cx states to Cmax

[Fabian Keil]

Warren Block <wblock at wonkity.com> wrote:

> On Sun, 4 May 2014, Adrian Chadd wrote:

> > The easy-to-run test is "sysctl dev.cpu.0.cx_lowest=Cmax" and then use stuff.
> 
> It's that "use stuff" step that would preferably be automated.  Is the 
> failure mode a lockup, or could a program detect problems?  The idea 
> is to get lots of feedback, fast.

One possible failure mode is that timers tick unreliably which can be
detected automatically (in some cases), for example by using the DTrace
script timestamp-test.d:
http://www.fabiankeil.de/gehacktes/dtrace-timestamp-tests/

It should also be possible to let the kernel do this itself
and log an error message and maybe optionally disable Cx
states that cause problems:
sysctl dev.cpu.0.cx_lowest=Cmax-as-long-as-it-appears-to-be-working

Fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20140505/5e8634ba/attachment.sig>