Date: Fri, 21 Nov 2003 10:57:03 -0800 (PST) From: Nate Lawson <nate@root.org> To: Eric Anderson <anderson@centtech.com> Cc: current@freebsd.org Subject: Re: acpi_cpu Message-ID: <20031121105300.D75531@root.org> In-Reply-To: <3FBBF3DE.40605@centtech.com> References: <20031116120622.O57495@root.org> <200311180346.22259@harrymail> <20031118095752.R64353@root.org> <200311182346.13704@harrymail> <3FBAC2DB.1080004@centtech.com> <20031118172757.S65940@root.org> <3FBAF515.6070507@centtech.com> <20031118223605.O66622@root.org> <3FBBF3DE.40605@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Nov 2003, Eric Anderson wrote: > Nate Lawson wrote: > >You should run a benchmark with different values for > >hw.acpi.cpu.current_speed to be sure the throttling control still works > >ok. I left it mostly intact so you shouldn't see any problems but it's > >still good to test. As you change it, you should see dmesg output of > >"acpi_cpu0: set speed to xx%" > > I can change the hw.acpi.cpu.economy_speed value, but the current_speed > is read only. When I set economy speed, it automatically bumps the > current speed down to my economy value (as expected). However, no dmesg > output. The only note I see is when going from AC to battery, I get: > kernel: system power profile changed to 'economy' > and of course going back to aAC shows 'performance' instead of economy. > I never see any "set speed to xx%". That is correct behavior. The printf is either under bootverbose or an ACPI debugging print so you won't see it normally. > >You should set hw.acpi.cpu.cx_lowest to 1 regularly and 2 or 3 if you're > >using battery. This will save on heat. I'd also be interested in if > >you'd set it to 3 while on battery and run a typical workload for an hour > >and then send me the result of sysctl hw.acpi.cpu. The cx_history value > >helps me know if my scheduler is accurate. > > I'll try this tomorrow - anyway to get it to automatically set it to a > value when going in to economy mode? Not yet, but working on a generalized way to program a variety of settings for economy/performance mode based on devd. > On a side note - can I do anything with the "lid control switch" acpi > piece? I'd like to make it turn off the screen and go into a sleep > mode (it goes into sleep, but the screen stays lit up). ACPI events now are accessible through devd. So if you look at /etc/*mumble*/devd.conf, you can see an example for getting the lid switch state. However, the more direct way to do this is via sysctl hw.acpi.lid_switch_state=S3 (or whatever state you want the laptop to go into when you close the lid). Please test the desired state manually with acpiconf before enabling it by default. Much of our suspend/resume support is still incomplete. -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031121105300.D75531>