Date: Thu, 18 Nov 2010 07:59:38 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: stable@freebsd.org, "Alexandre \"Sunny\" Kovalenko" <gaijin.k@ovi.com>, Ian Smith <smithi@nimnet.asn.au> Subject: Re: Console options for legacy-free mini-itx server? Message-ID: <201011180759.39129.jhb@freebsd.org> In-Reply-To: <1290041198.1899.19.camel@RabbitsDen.RabbitsLawn.verizon.net> References: <20101115045549.GB96011@johnny.reilly.home> <20101118001349.GA40554@johnny.reilly.home> <1290041198.1899.19.camel@RabbitsDen.RabbitsLawn.verizon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, November 17, 2010 7:46:38 pm Alexandre "Sunny" Kovalenko wrote: > On Thu, 2010-11-18 at 11:13 +1100, Andrew Reilly wrote: > > Hi Alexandre, > > > > On Wed, Nov 17, 2010 at 06:56:53PM -0500, Alexandre Sunny Kovalenko wrote: > > > On Thu, 2010-11-18 at 10:40 +1100, Andrew Reilly wrote: > > > > dev.cpu.0.%desc: ACPI CPU > > > > dev.cpu.0.%driver: cpu > > > > dev.cpu.0.%location: handle=\_PR_.CPU0 > > > > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > > > > dev.cpu.0.%parent: acpi0 > > > > dev.cpu.0.freq: 2933 > > > > 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_lowest: C1 > > > > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 311us > > > > dev.cpu.1.%desc: ACPI CPU > > > > dev.cpu.1.%driver: cpu > > > > dev.cpu.1.%location: handle=\_PR_.CPU1 > > > > dev.cpu.1.%pnpinfo: _HID=none _UID=0 > > > > dev.cpu.1.%parent: acpi0 > > > > dev.cpu.1.cx_supported: C1/3 C2/205 C3/245 > > > > dev.cpu.1.cx_lowest: C1 > > > > 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? > > > > > > > > Cheers, > > > > > > > > > > Does portion of 'devinfo -rv' similar to the snippet below show 'est' > > > attached to both CPUs? > > > <...> > > > cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU0 > > > ACPI I/O ports: > > > 0x1014 > > > 0x1015 > > > acpi_perf0 > > > acpi_throttle0 > > > coretemp0 > > > ==> est0 > > > p4tcc0 > > > cpufreq0 > > > cpu1 pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU1 > > > ACPI I/O ports: > > > 0x1014 > > > 0x1015 > > > acpi_perf1 > > > acpi_throttle1 > > > coretemp1 > > > ==> est1 > > > p4tcc1 > > > cpufreq1 > > > <...> > > > > Yes, but as you can see they are not nested under coretemp. devices: > > > > cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU0 > > ACPI I/O ports: > > 0x414 > > 0x415 > > acpi_perf0 > > est0 > > p4tcc0 > > cpufreq0 > > cpu1 pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU1 > > ACPI I/O ports: > > 0x414 > > 0x415 > > acpi_perf1 > > est1 > > p4tcc1 > > cpufreq1 > > > > This seems to be at odds with the dmesg and sysctl view of things? > > > > Cheers, > > > > I am sorry -- in the attempt to point them out, I have messed up the > alignment -- they *should not* be nested under coretemp. It is strange > that 'est' reported error on attach, yet seems to be attached to the > device. This said, I am way out of my depth here -- hopefully someone > smarter than I will chime in. You used devinfo -v, so it shows the devices that exist even if they failed to attach. Try just using 'devinfo' and seeing if est1 still shows up. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011180759.39129.jhb>