Date: Mon, 1 Nov 2010 14:25:36 +0200 From: Joerg Traeger <jt@xoasis.de> To: Andriy Gapon <avg@icyb.net.ua> Cc: freebsd-acpi@freebsd.org Subject: Re: est CPU support Message-ID: <201011011325.36879.jt@xoasis.de> In-Reply-To: <4CCE9C0F.6060907@icyb.net.ua> References: <201011011052.11084.jt@xoasis.de> <4CCE9C0F.6060907@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 01 November 2010, Andriy Gapon wrote: > on 01/11/2010 11:52 Joerg Traeger said the following: > > Hi, > > > > I have got several mainboards with CPUs which appear not to be > > supportet by est. An error exists: > > > > (examle of somewhat older Intel DG45FC with DualCore E5200 and latest > > BIOS) > > > > est0: <Enhanced SpeedStep Frequency Control> on cpu0 > > est: CPU supports Enhanced Speedstep, but is not recognized. > > est: cpu_vendor GenuineIntel, msr 61a4c1f06004c1f > > device_attach: est0 attach returned 6 <---------- > > Do you have ACPI enabled? Yes, sure it is enabled. debug.acpi.suspend_bounce: 0 debug.acpi.reset_clock: 1 debug.acpi.do_powerstate: 1 debug.acpi.interpreter_slack: 1 debug.acpi.enable_debug_objects: 0 debug.acpi.acpi_ca_version: 20100331 debug.acpi.ec.timeout: 750 debug.acpi.ec.polled: 0 debug.acpi.ec.burst: 0 debug.acpi.batt.batt_sleep_ms: 0 debug.acpi.resume_beep: 0 hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S3 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: NONE hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.cpu.cx_lowest: C1 machdep.acpi_timer_freq: 3579545 machdep.acpi_root: 984000 machdep.idle: acpi machdep.idle_available: spin, mwait, mwait_hlt, hlt, acpi, dev.acpi.0.%desc: INTEL DG45FC dev.acpi.0.%driver: acpi dev.acpi.0.%parent: nexus0 dev.acpi_sysresource.0.%desc: System Resource dev.acpi_sysresource.0.%driver: acpi_sysresource dev.acpi_sysresource.0.%location: handle=\_SB_.PCI0.MCH_ dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C01 _UID=10 dev.acpi_sysresource.0.%parent: acpi0 dev.acpi_sysresource.1.%desc: System Resource dev.acpi_sysresource.1.%driver: acpi_sysresource dev.acpi_sysresource.1.%location: handle=\_SB_.PCI0.SBRG.SIO1 dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=46 dev.acpi_sysresource.1.%parent: acpi0 dev.acpi_sysresource.2.%desc: System Resource dev.acpi_sysresource.2.%driver: acpi_sysresource dev.acpi_sysresource.2.%location: handle=\_SB_.PCI0.SBRG.RMSC dev.acpi_sysresource.2.%pnpinfo: _HID=PNP0C02 _UID=16 dev.acpi_sysresource.2.%parent: acpi0 dev.acpi_sysresource.3.%desc: System Resource dev.acpi_sysresource.3.%driver: acpi_sysresource dev.acpi_sysresource.3.%location: handle=\_SB_.PCI0.ICH9 dev.acpi_sysresource.3.%pnpinfo: _HID=PNP0C01 _UID=455 dev.acpi_sysresource.3.%parent: acpi0 dev.acpi_sysresource.4.%desc: System Resource dev.acpi_sysresource.4.%driver: acpi_sysresource dev.acpi_sysresource.4.%location: handle=\_SB_.RMEM dev.acpi_sysresource.4.%pnpinfo: _HID=PNP0C01 _UID=1 dev.acpi_sysresource.4.%parent: acpi0 dev.acpi_sysresource.5.%desc: System Resource dev.acpi_sysresource.5.%driver: acpi_sysresource dev.acpi_sysresource.5.%location: handle=\OMSC dev.acpi_sysresource.5.%pnpinfo: _HID=PNP0C02 _UID=3601 dev.acpi_sysresource.5.%parent: acpi0 dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz dev.acpi_timer.0.%driver: acpi_timer dev.acpi_timer.0.%location: unknown dev.acpi_timer.0.%pnpinfo: unknown dev.acpi_timer.0.%parent: acpi0 dev.cpu.0.%parent: acpi0 dev.cpu.1.%parent: acpi0 dev.pci_link.0.%parent: acpi0 dev.pci_link.1.%parent: acpi0 dev.pci_link.2.%parent: acpi0 dev.pci_link.3.%parent: acpi0 dev.pci_link.4.%parent: acpi0 dev.pci_link.5.%parent: acpi0 dev.pci_link.6.%parent: acpi0 dev.pci_link.7.%parent: acpi0 dev.pcib.0.%parent: acpi0 dev.acpi_button.0.%desc: Power Button dev.acpi_button.0.%driver: acpi_button dev.acpi_button.0.%location: handle=\_SB_.PWRB dev.acpi_button.0.%pnpinfo: _HID=PNP0C0C _UID=170 dev.acpi_button.0.%parent: acpi0 dev.acpi_button.0.wake: 1 dev.uart.0.%parent: acpi0 dev.atdma.0.%parent: acpi0 dev.attimer.0.%parent: acpi0 dev.atrtc.0.%parent: acpi0 dev.fpupnp.0.%parent: acpi0 > > > p4tcc0: <CPU Frequency Thermal Control> on cpu0 > > [...] > > est1: <Enhanced SpeedStep Frequency Control> on cpu1 > > est: CPU supports Enhanced Speedstep, but is not recognized. > > est: cpu_vendor GenuineIntel, msr 61a4c1f06004c1f > > device_attach: est1 attach returned 6 > > p4tcc1: <CPU Frequency Thermal Control> on cpu1 > > > > Searching the net I found several hints this CPU (Intel DualCore E5200) > > _is_ supported by EST and the voltage is being reduced in idle states > > like intended. > > So it looks like there are more things which might break success using > > est for me. Can you explain what may be a reason for this problem? In the > > past it was about hardcoding cpu data about voltages into the source but > > as I know this is not the case anymore but ACPI is involved. > > Is the BIOS likely to be the reason or is it an ignored CPU stepping > > or...? > > > > Same happens with the new CPU Intel Atom N550 on a Jetway board called > > NC9c-550-LF. est does not attach and some watts are wasted. > > > > Thank you! -- If you say that you can't, then I shall reply, Parsley, sage, rosemary and thyme
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011011325.36879.jt>