Console options for legacy-free mini-itx server?
areilly at bigpond.net.au
Wed Nov 17 23:41:59 UTC 2010
On Wed, Nov 17, 2010 at 06:26:56PM -0500, Alexandre Sunny Kovalenko wrote:
> On Thu, 2010-11-18 at 10:06 +1100, Andrew Reilly wrote:
> > On Wed, Nov 17, 2010 at 01:42:15PM +1100, Ian Smith wrote:
> > > I'm used to seeing est either attach to both CPUs, or fail to attach to
> > > either CPU. Here it's attached to cpu0, but not to cpu1. Is that odd?
> > It seems odd, but since I don't know what est does (there isn't
> > a man page), I'm not sure how it (possibly) being broken
> > affects me.
> > Cheers,
> Faint reference to 'est' could be found in 'man cpufreq'.
Thanks for the reference! From reading that, it seems as though
the sysctl-exposed functionality matches the dmesg.boot
description (speed controls only available on cpu 0):
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.freq_levels: 2933/90000 2799/83000 2666/77000 2533/71000 2399/65000 2266/59000 2133/53000 1999/46000 1866/40000 1733/34000 1599/28000 1466/22000 1333/16000 1199/10000 1049/8750 899/7500 749/6250 599/5000 449/3750 299/2500 149/1250
dev.cpu.0.cx_supported: C1/3 C2/205 C3/245
dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 311us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.cx_supported: C1/3 C2/205 C3/245
dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 191us
Since the cpufreq man page lists the inability to set the
frequency of different CPUs differently, perhaps this isn't a
bug at all?
More information about the freebsd-stable