On Nov 10 00:21:59, h...@stare.cz wrote:
> On Nov 02 12:30:56, dera...@openbsd.org wrote:
> > Paul de Weerd wrote:
> >
> > > A recent commit by Theo changed the hw.perfpolicy behavior to always
> > > run at full speed when AC power is on. This means that my workstation
> > > (and servers, once
Nicola Dell'Uomo wrote:
> Hi,
>
> I tested my laptop using different -CURRENT releases (#67, #71, #76) and the
> problem persists.
> First of all I disabled apmd as Theo suggested and my laptop did not auto
> suspended anymore.
> This is the output of systat sens -1 when my system fails to
On Tue, Nov 9, 2021 at 3:29 PM Jan Stary wrote:
> On Nov 10 00:21:59, h...@stare.cz wrote:
> > Regarding C states, this machine has
> >
> > acpicpu0 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> >
> > I suppose the cpu supports C1, C2, C3, but can
On Nov 10 00:21:59, h...@stare.cz wrote:
> Regarding C states, this machine has
>
> acpicpu0 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
>
> I suppose the cpu supports C1, C2, C3, but can someone please kindly
> explain (or point to an explanation of)
On Nov 02 12:30:56, dera...@openbsd.org wrote:
> Paul de Weerd wrote:
>
> > A recent commit by Theo changed the hw.perfpolicy behavior to always
> > run at full speed when AC power is on. This means that my workstation
> > (and servers, once I upgrade them) now consumes significantly more
> >
Hmm.
Stop using apmd, and run
systat sens 1
And watch to see what happens to the various sensors.
This will show you everything.
Nicola Dell'Uomo wrote:
> Battery self test is okay and my laptop has just 1 year of life (X1 carbon
> 8th gen).
> The problem replicated just now after a
It looks like your battery is failing.
Nicola Dell'Uomo wrote:
> I've been experiencing odd power management behavior since some days: my
> laptop goes to suspend and I didn't know why.
> Today I looked at /var/messages and I found this out:
> [snip]
> Nov 3 15:04:20 puffy apmd: system
On Wed, Nov 03, 2021 at 11:55:41AM +, Stuart Henderson wrote:
> On 2021/11/03 05:47, Crystal Kolipe wrote:
> > > Your OptiPlex 9020 is probably a modern i5/i7, which probably contains
> > > C states similar to this:
> > >
> > > acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1),
On Tue, Nov 02, 2021 at 12:26:15PM -0600, Theo de Raadt wrote:
> acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
>
> Which means when the idle loop calls the "mwait" instruction, the cpu
> will 'instantly' slow down, until an interrupt happens. And thus, save
> power. That
On 2021/11/03 05:47, Crystal Kolipe wrote:
> > Your OptiPlex 9020 is probably a modern i5/i7, which probably contains
> > C states similar to this:
> >
> > acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
> >
> > Which means when the idle loop calls the "mwait" instruction,
On Tue, Nov 02, 2021 at 12:30:56PM -0600, Theo de Raadt wrote:
> Paul de Weerd wrote:
>
> > A recent commit by Theo changed the hw.perfpolicy behavior to always
> > run at full speed when AC power is on. This means that my workstation
> > (and servers, once I upgrade them) now consumes
On Wed, 3 Nov 2021, Stuart Henderson wrote:
> > See also https://en.wikichip.org/wiki/race-to-sleep - it's generally
> > more energy efficient to run the CPU at full speed so it can finish its
> > work faster and get back to a low-power state sooner
>
> So there's not really any point in doing
On 2021/11/03 16:46, Damien Miller wrote:
> On Tue, 2 Nov 2021, Theo de Raadt wrote:
>
> > Paul de Weerd wrote:
> >
> > > A recent commit by Theo changed the hw.perfpolicy behavior to always
> > > run at full speed when AC power is on. This means that my workstation
> > > (and servers, once I
On Tue, Nov 02, 2021 at 12:30:56PM -0600, Theo de Raadt wrote:
| Paul de Weerd wrote:
|
| > A recent commit by Theo changed the hw.perfpolicy behavior to always
| > run at full speed when AC power is on. This means that my workstation
| > (and servers, once I upgrade them) now consumes
On Tue, 2 Nov 2021, Theo de Raadt wrote:
> Paul de Weerd wrote:
>
> > A recent commit by Theo changed the hw.perfpolicy behavior to always
> > run at full speed when AC power is on. This means that my workstation
> > (and servers, once I upgrade them) now consumes significantly more
> > power,
Solene Rapenne wrote:
> On mardi 2 novembre 2021 19:19:03 CET, Paul de Weerd wrote:
> > A recent commit by Theo changed the hw.perfpolicy behavior to always
> > run at full speed when AC power is on. This means that my workstation
> > (and servers, once I upgrade them) now consumes
> Date: Tue, 2 Nov 2021 19:19:03 +0100
> From: Paul de Weerd
>
> A recent commit by Theo changed the hw.perfpolicy behavior to always
> run at full speed when AC power is on. This means that my workstation
> (and servers, once I upgrade them) now consumes significantly more
> power, even though
Paul de Weerd wrote:
> A recent commit by Theo changed the hw.perfpolicy behavior to always
> run at full speed when AC power is on. This means that my workstation
> (and servers, once I upgrade them) now consumes significantly more
> power, even though they usually idle.
Did you measure how
Paul de Weerd wrote:
> A recent commit by Theo changed the hw.perfpolicy behavior to always
> run at full speed when AC power is on. This means that my workstation
> (and servers, once I upgrade them) now consumes significantly more
> power, even though they usually idle.
Did you measure how
A recent commit by Theo changed the hw.perfpolicy behavior to always
run at full speed when AC power is on. This means that my workstation
(and servers, once I upgrade them) now consumes significantly more
power, even though they usually idle.
[weerd@pom] $ sysctl
20 matches
Mail list logo
