cool! next;
# pkg install intel-pcm # kldload cpuctl # pcm.x 1 See what it reports. -a On 9 May 2014 13:12, Kevin Oberman <[email protected]> wrote: > On Fri, May 9, 2014 at 3:25 AM, Adrian Chadd <[email protected]> wrote: >> >> Hi! >> >> On 9 May 2014 02:55, Poul-Henning Kamp <[email protected]> wrote: >> > In message <[email protected]>, Ian Smith writes: >> >>On Mon, 5 May 2014 06:25:21 +0000, Poul-Henning Kamp wrote: >> >> > In message <[email protected]>, Ian Smith >> >> > writes: >> >> > >> >> > Do we have a canonical page with all the various workarounds one >> >> > should >> >> > attempt in order to get suspend/resume to work ? >> >> >> >>Bits scattered all over the place. For the above there's: >> > >> > So based on various scattered hints, I tried booting the VT kernel, >> > r265336, on my Thinkpad T430s and that seems to fix both Suspend/Resume >> > and also console switching. >> > >> > Much appreciated! >> > >> > I'll keep an eye on any peripheral bogons as I used it now. >> >> Woo! >> >> Would you mind populating http://wiki.freebsd.org/Laptops with your >> details? >> >> Thanks! >> >> >> -a > > > Excellent! This alone will save batteries and also lower the carbon > footprint of FreeBSD servers! > > Just to clarify the various settings of *_cx_lowest in rc.conf, HIGH is > obvious. At one time, LOW was also obvious, but then some vendors started > shipping BIOS that "skipped" some C-states in different power conditions. > E.g. C1, C2 and C3 when on Battery, but only C1 and C3 when on AC. This > scenario was common on Sandybridge systems (like my T320). Skipping a state > broke "LOW" as it only saw C1 when on AC. Thus, Cmax appeared. Cmax is > simply C8. It is just easier ot remember then C8. The code was re-written to > ignore "missing" C-states and try all possible C-states until C8 was > reached. > > Why "LOW" was not just changed to deal with this I don't understand, but > Cmax (or C8) is recommended to gain the maximum power savings from > C-states. > > On AC power: > dev.cpu.0.cx_supported: C1/1/1 C2/3/104 > dev.cpu.0.cx_lowest: C8 > dev.cpu.0.cx_usage: 8.86% 91.13% last 2685us > > On battery: > dev.cpu.0.cx_supported: C1/1/1 C2/2/80 C3/3/109 > dev.cpu.0.cx_lowest: C8 > dev.cpu.0.cx_usage: 3.09% 0.74% 96.15% last 728us > > Note the supported list on AC? > C2/3/104 The first part, "C2", is what the OS labels that second state. The > next part, "3", is the ACPI number of this state. On AC, this system has no > C-state 2, so FreeBSD call the ACPI state 3 "C2". Oh, the last number is the > number of clock cycles required to get into/out of that state. so in my > case, when on battery, my CPU goes ot C2 after being halted for 80 clock > cycles and C3 after 109. I hope this makes sense to everyone. I'm not really > sure that it does to me! > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: [email protected] _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "[email protected]"
