Hello, I am putting together a couple update servers. Went with c2d
E7500 on gigabyte G41M-ES2L boards. fbsd 8.0 release generic (so far)
amd64, 1g mem, 1tb wd cavier blk, fresh system.
My Kill-a-watt shows 41 watts idle and when I enable powerd then it
climbs to 43 watts idle.
It shows that the freq is controlled well, goes down to 365 mhz but
the tdp is not decreased, rather it increases.
If I disable eist, c1 and c3 helpers in bios, as per suggestion in
mail archive, then it adds 1 watt to both figures. I was hoping to get
this total tdp down to a very low amount, and it is but it should
theoretically go lower with powerd, right?
The bios reports 1.268V and 26C temp. I was hoping that the voltage
would go down to .85 or so when powerd lowered the freq to 365 etc.
Healthd does not seem to know what monitoring chip it is and I have no
idea unless I install xp (ugh) and run something from cpuid.com on it.
What is a good/better/best monitoring program, mbmon and bsdhwmon are
untried for they are not current I see. Or what do I do from here to
fix this problem?
thx,
John
dmesg shows
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 6160b2506000b25
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 6160b2506000b25
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
powerd -v
powerd: unable to determine AC line status
load 0%, current freq 2926 MHz ( 0), wanted freq 2834 MHz
load 0%, current freq 2926 MHz ( 0), wanted freq 2745 MHz
.......
load 3%, current freq 365 MHz ( 7), wanted freq 365 MHz
load 0%, current freq 365 MHz ( 7), wanted freq 365 MHz
healthd -d
************************
Unknown Vendor: ID = FFFF
************************
Temp.= 191.0, 159.0, 159.0; Rot.= 874, 3358, 2657
Vcore = 1.25, 1.92; Volt. = 3.31, 4.92, 1.16, -14.16, -6.12
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
1994
The Regents of the University of California. All rights
reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009
root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (2926.08-MHz
K8-class CPU)
Origin = "GenuineIntel" Id = 0x1067a Stepping = 10
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,P
GE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,
HTT,TM,PBE>
Features2=0x408e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR
,PDCM,SSE4.1,XSAVE>
AMD Features=0x20100800<SYSCALL,NX,LM>
AMD Features2=0x1<LAHF>
TSC: P-state invariant
real memory = 1073741824 (1024 MB)
avail memory = 983613440 (938 MB)
ACPI APIC Table: <GBT GBTUACPI>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0: Changing APIC ID to 2
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <GBT GBTUACPI> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 3dbe0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff
on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
vgapci0: <VGA-compatible display> port 0xe400-0xe407 mem
0xe3000000-0xe33fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on
pci0
pci0: <multimedia, HDA> at device 27.0 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 17 at device 28.1 on pci0
pci2: <ACPI PCI bus> on pcib2
re0: <RealTek
8168/8168B/8168C/8168CP/8168D/8168DP/8111B/8111C/8111CP/8111DP PCIe
Gigabit Ethernet> port 0xc000-0xc0ff mem 0xe341000
0-0xe3410fff,0xe3400000-0xe340ffff irq 17 at device 0.0 on pci2
re0: Using 1 MSI messages
re0: Chip rev. 0x3c000000
re0: MAC rev. 0x00400000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
re0: Ethernet address: 6c:f0:49:63:5a:47
re0: [FILTER]
uhci0: <Intel 82801G (ICH7) USB controller USB-A> port 0xe000-0xe01f
irq 23 at device 29.0 on pci0
uhci0: [ITHREAD]
uhci0: LegSup = 0x003b
usbus0: <Intel 82801G (ICH7) USB controller USB-A> on uhci0
uhci1: <Intel 82801G (ICH7) USB controller USB-B> port 0xe100-0xe11f
irq 19 at device 29.1 on pci0
uhci1: [ITHREAD]
uhci1: LegSup = 0x0010
usbus1: <Intel 82801G (ICH7) USB controller USB-B> on uhci1
uhci2: <Intel 82801G (ICH7) USB controller USB-C> port 0xe200-0xe21f
irq 18 at device 29.2 on pci0
uhci2: [ITHREAD]
uhci2: LegSup = 0x0010
usbus2: <Intel 82801G (ICH7) USB controller USB-C> on uhci2
uhci3: <Intel 82801G (ICH7) USB controller USB-D> port 0xe300-0xe31f
irq 16 at device 29.3 on pci0
uhci3: [ITHREAD]
uhci3: LegSup = 0x0010
usbus3: <Intel 82801G (ICH7) USB controller USB-D> on uhci3
ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem
0xe3504000-0xe35043ff irq 23 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus4: waiting for BIOS to give up control
usbus4: EHCI version 1.0
usbus4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0
pcib3: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci3: <ACPI PCI bus> on pcib3
dc0: <82c169 PNIC 10/100BaseTX> port 0xd000-0xd0ff mem
0xe2000000-0xe20000ff irq 20 at device 0.0 on pci3
miibus1: <MII bus> on dc0
bmtphy0: <BCM5201 10/100baseTX PHY> PHY 1 on miibus1
bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: Ethernet address: 00:02:e3:07:a9:70
dc0: [ITHREAD]
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH7 SATA300 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.2 on
pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
atrtc0: <AT realtime clock> port 0x70-0x73 on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
uart0: [FILTER]
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 6160b2506000b25
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 6160b2506000b25
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
ppc0: cannot reserve I/O port range
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 480Mbps High Speed USB v2.0
ad0: 953868MB <WDC WD1001FALS-00J7B0 05.00K05> at ata0-master SATA150
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on
usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on
usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on
usbus2
ugen3.1: <Intel> at usbus3
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on
usbus3
ugen4.1: <Intel> at usbus4
uhub4: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on
usbus4
acd0: CDROM <CREATIVE CD5230E/C1.01> at ata1-master PIO4
SMP: AP CPU #1 Launched!
Root mount waiting for: usbus4 usbus3 usbus2 usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
Root mount waiting for: usbus4
Root mount waiting for: usbus4
Root mount waiting for: usbus4
uhub4: 8 ports with 8 removable, self powered
Trying to mount root from ufs:/dev/ad0s1a
re0: link state changed to UP
On Mon, March 22, 2010 19:57, John Long wrote:> dmesg shows > cpu0: <ACPI CPU> on acpi0 > est0: <Enhanced SpeedStep Frequency Control> on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 6160b2506000b25 > device_attach: est0 attach returned 6 > p4tcc0: <CPU Frequency Thermal Control> on cpu0 > cpu1: <ACPI CPU> on acpi0 > est1: <Enhanced SpeedStep Frequency Control> on cpu1 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 6160b2506000b25 > device_attach: est1 attach returned 6 > p4tcc1: <CPU Frequency Thermal Control> on cpu1I get similar output on 8-STABLE and C2Q 9400/9450. wasn't it supposed to attach ok ? matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style
John Long wrote:> Hello, I am putting together a couple update servers. Went with c2d > E7500 on gigabyte G41M-ES2L boards. fbsd 8.0 release generic (so far) > amd64, 1g mem, 1tb wd cavier blk, fresh system. > My Kill-a-watt shows 41 watts idle and when I enable powerd then it > climbs to 43 watts idle. > It shows that the freq is controlled well, goes down to 365 mhz but > the tdp is not decreased, rather it increases. > If I disable eist, c1 and c3 helpers in bios, as per suggestion in > mail archive, then it adds 1 watt to both figures. I was hoping to get > this total tdp down to a very low amount, and it is but it should > theoretically go lower with powerd, right? > The bios reports 1.268V and 26C temp. I was hoping that the voltage > would go down to .85 or so when powerd lowered the freq to 365 etc. > Healthd does not seem to know what monitoring chip it is and I have no > idea unless I install xp (ugh) and run something from cpuid.com on it. > What is a good/better/best monitoring program, mbmon and bsdhwmon are > untried for they are not current I see. Or what do I do from here to > fix this problem? > thx, > John > dmesg shows > cpu0: <ACPI CPU> on acpi0 > est0: <Enhanced SpeedStep Frequency Control> on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 6160b2506000b25 > device_attach: est0 attach returned 6 > p4tcc0: <CPU Frequency Thermal Control> on cpu0 > cpu1: <ACPI CPU> on acpi0 > est1: <Enhanced SpeedStep Frequency Control> on cpu1 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 6160b2506000b25 > device_attach: est1 attach returned 6 > p4tcc1: <CPU Frequency Thermal Control> on cpu1 > powerd -v > powerd: unable to determine AC line status > load 0%, current freq 2926 MHz ( 0), wanted freq 2834 MHz > load 0%, current freq 2926 MHz ( 0), wanted freq 2745 MHz > ....... > load 3%, current freq 365 MHz ( 7), wanted freq 365 MHz > load 0%, current freq 365 MHz ( 7), wanted freq 365 MHzYour ACPI BIOS seems not reporting tables required to control EIST. So powerd probably uses only thermal throttling, which is not really effective for power saving on modern CPUs. You should check your BIOS options or may be update BIOS. If you have no luck with EIST - try to use C-states if BIOS reports at least them. It also can be quite effective. -- Alexander Motin
At 07:55 PM 3/22/2010, Nenhum_de_Nos wrote: > >On Mon, March 22, 2010 19:57, John Long wrote: >> dmesg shows >> cpu0: <ACPI CPU> on acpi0 >> est0: <Enhanced SpeedStep Frequency Control> on cpu0 >> est: CPU supports Enhanced Speedstep, but is not recognized. >> est: cpu_vendor GenuineIntel, msr 6160b2506000b25 >> device_attach: est0 attach returned 6 >> p4tcc0: <CPU Frequency Thermal Control> on cpu0 >> cpu1: <ACPI CPU> on acpi0 >> est1: <Enhanced SpeedStep Frequency Control> on cpu1 >> est: CPU supports Enhanced Speedstep, but is not recognized. >> est: cpu_vendor GenuineIntel, msr 6160b2506000b25 >> device_attach: est1 attach returned 6 >> p4tcc1: <CPU Frequency Thermal Control> on cpu1 > >I get similar output on 8-STABLE and C2Q 9400/9450. >wasn't it supposed to attach ok ? >matheus I am not sure just what is the best way for all this to work. I do not know what a return of 6 means (not recognized?) or how to fix it. I can find no similar mention anywhere of the fact that power is increased and not lowered by the use of powerd or similar and thought that would provoke some hints and more discussion because it is intriguing and it self negates its own purpose and functionality. I am trying to ascertain the viability of this motherboard w/ regards to getting the power function working proper and am constrained by the lack of monitoring tools vs what cupid.com has for win with hwmonitor and cpuz (they have a dev kit also). Would another brand/model of mb work better? I know that most all are lacking in acpi function in diff ways. Maybe I am squeezing water out of a rock, that the cpu is at its min or 6 watts now, but I just do not know. Btw: Intel is blowing out all 775 type chips. Today is about the last day. They want everyone on I3/I5 etc but they are not as functional re low tdp as 775 chips. Just because you lower the freq by stretching the clock or actually lowering the freq does not result in a lower TDP. I do not think that the multiplier being lowered in this case. What appears to be happening is that the cpu gets busier and that increases the tdp over not using it at all making it less than useless in my case. I can find very little comprehensive info on how the eist/est//p4tcc/powerd thing is supposed to work. Reading source of powerd is not helping. Logically, if the voltage is lowered then the power is going to be lower. Is the voltage a function of the load automatically controlled by hardware and/or the bios or is it supposed to be an artifact of the freq being lowered by something like powerd? I believe the former for the latter is not working. I now have everything relevant in the bios enabled. est appears to be not working but what would happen if it were working? Is that the key to lowering the TDP when the freq is lowered? Then what is required for it to work? Where would I find the source in the tree? p4tcc appears that it is a failsafe for thermal runaway and since my temp is 26 - 30 or so all the time then it would be of no use because there is too little differential. I csupd to stable and rebuilt and there is no difference w/ this prob. I did see that I went from SATA150 (it should be SATA300) to udma100 sata but that is for another thread. I changed hw.acpi.cpu.cx_lowest=C1 to C3 and that saved me about 1.5 watts w/ powerd but it is still a watt higher than without powerd running at all. Does anyone know of anything else I can try or is this the best it can get? John seemingly relevant sysctls: debug.acpi.suspend_bounce: 0 debug.acpi.reset_clock: 1 debug.acpi.do_powerstate: 1 debug.acpi.acpi_ca_version: 20100121 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 debug.cpufreq.verbose: 0 debug.cpufreq.lowest: 0 hw.pcic.pd6722_vsense: 1 hw.pcic.intr_mask: 57016 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 dev.acpi.0.%desc: GBT GBTUACPI 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.PX40.SYSR dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C02 _UID=1 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.PX40.PMIO dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=2 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.EXPL dev.acpi_sysresource.2.%pnpinfo: _HID=PNP0C02 _UID=4 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_.MEM_ dev.acpi_sysresource.3.%pnpinfo: _HID=PNP0C01 _UID=0 dev.acpi_sysresource.3.%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.%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: 1466 dev.cpu.0.freq_levels: 2933/-1 2566/-1 2199/-1 1833/-1 1466/-1 1099/-1 733/-1 366/-1 dev.cpu.0.cx_supported: C1/1 C2/1 C3/150 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 500us 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/1 C2/1 C3/150 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 500us dev.atapci.0.%desc: Intel ICH7 SATA300 controller dev.atapci.0.%driver: atapci dev.atapci.0.%location: slot=31 function=2 handle=\_SB_.PCI0.IDE1 dev.atapci.0.%pnpinfo: vendor=0x8086 device=0x27c0 subvendor=0x1458 subdevice=0xb002 class=0x010180 dev.atapci.0.%parent: pci0 dev.ata.0.%desc: ATA channel 0 dev.ata.0.%driver: ata dev.ata.0.%parent: atapci0 dev.ata.1.%desc: ATA channel 1 dev.ata.1.%driver: ata dev.ata.1.%parent: atapci0 dev.atdma.0.%desc: AT DMA controller dev.atdma.0.%driver: atdma dev.atdma.0.%location: handle=\_SB_.PCI0.PX40.DMA1 dev.atdma.0.%pnpinfo: _HID=PNP0200 _UID=0 dev.atdma.0.%parent: acpi0 dev.p4tcc.0.%desc: CPU Frequency Thermal Control dev.p4tcc.0.%driver: p4tcc dev.p4tcc.0.%parent: cpu0 dev.p4tcc.0.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1 2500/-1 1250/-1 dev.p4tcc.1.%desc: CPU Frequency Thermal Control dev.p4tcc.1.%driver: p4tcc dev.p4tcc.1.%parent: cpu1 dev.p4tcc.1.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1 2500/-1 1250/-1 dev.cpufreq.0.%driver: cpufreq dev.cpufreq.0.%parent: cpu0 dev.cpufreq.1.%driver: cpufreq dev.cpufreq.1.%parent: cpu1
At 11:27 PM 3/22/2010, Alexander Motin wrote: >John Long wrote: >> Hello, I am putting together a couple update servers. Went with c2d >> E7500 on gigabyte G41M-ES2L boards. fbsd 8.0 release generic (so far) >> amd64, 1g mem, 1tb wd cavier blk, fresh system. >> My Kill-a-watt shows 41 watts idle and when I enable powerd then it >> climbs to 43 watts idle. >> It shows that the freq is controlled well, goes down to 365 mhz but >> the tdp is not decreased, rather it increases. >> If I disable eist, c1 and c3 helpers in bios, as per suggestion in >> mail archive, then it adds 1 watt to both figures. I was hoping to get >> this total tdp down to a very low amount, and it is but it should >> theoretically go lower with powerd, right? >> The bios reports 1.268V and 26C temp. I was hoping that the voltage >> would go down to .85 or so when powerd lowered the freq to 365 etc. >> Healthd does not seem to know what monitoring chip it is and I have no >> idea unless I install xp (ugh) and run something from cpuid.com on it. >> What is a good/better/best monitoring program, mbmon and bsdhwmon are >> untried for they are not current I see. Or what do I do from here to >> fix this problem? >> thx, >> John >> dmesg shows >> cpu0: <ACPI CPU> on acpi0 >> est0: <Enhanced SpeedStep Frequency Control> on cpu0 >> est: CPU supports Enhanced Speedstep, but is not recognized. >> est: cpu_vendor GenuineIntel, msr 6160b2506000b25 >> device_attach: est0 attach returned 6 >> p4tcc0: <CPU Frequency Thermal Control> on cpu0 >> cpu1: <ACPI CPU> on acpi0 >> est1: <Enhanced SpeedStep Frequency Control> on cpu1 >> est: CPU supports Enhanced Speedstep, but is not recognized. >> est: cpu_vendor GenuineIntel, msr 6160b2506000b25 >> device_attach: est1 attach returned 6 >> p4tcc1: <CPU Frequency Thermal Control> on cpu1 >> powerd -v >> powerd: unable to determine AC line status >> load 0%, current freq 2926 MHz ( 0), wanted freq 2834 MHz >> load 0%, current freq 2926 MHz ( 0), wanted freq 2745 MHz >> ....... >> load 3%, current freq 365 MHz ( 7), wanted freq 365 MHz >> load 0%, current freq 365 MHz ( 7), wanted freq 365 MHz > >Your ACPI BIOS seems not reporting tables required to control EIST. So >powerd probably uses only thermal throttling, which is not really >effective for power saving on modern CPUs. You should check your BIOS >options or may be update BIOS. > >If you have no luck with EIST - try to use C-states if BIOS reports at >least them. It also can be quite effective. > >-- >Alexander Motin Thanks for the info, I did try to kick it to C3 and that helped poquito amount. Everything is enabled in bios that matters to this, that does help a little too but powerd actually raises tdp a little. See other recent reply for more info. Thanks, John