Re: frequency scaling on D525MW not working properly
On Fri, Aug 03, 2012 at 09:22:12AM +0800, Sepherosa Ziehau wrote: > On Fri, Aug 3, 2012 at 2:00 AM, Sven Gaerner wrote: > > On Tue, Jul 31, 2012 at 09:27:15AM +0800, Sepherosa Ziehau wrote: > >> On Tue, Jul 31, 2012 at 5:01 AM, Sven Gaerner wrote: > >> [...] > >> > >> Hmm, maybe i8254 is not working at all. Could you post following > >> information: > >> - bootverbose dmesg w/ hw.i8254.intr_disable="0" in /boot/loader.conf > >> - sysctl kern.cputimer > >> - sysctl hw.acpi > > > > Attached the requested details. > > Grrr, only C1 is detected. If the CPU does support C3, there could be > some settings in BIOS? > > Best Regards, > sephe > > -- > Tomorrow Will Never Die The BIOS settings are very limited. I did not find anything that looks like configuring the C-states. You can just enable/disable the HPET timer, the ACPI wake states (S1 or S3) and other settings that are not related to ACPI/frequency scaling like configuring the USB ports. It looks like FreeBSD also doesn't detect the settings well: http://lists.freebsd.org/pipermail/freebsd-acpi/2011-August/007264.html I guess there is no chance to get C3 states working. I looked into the manual [1] and on page 28ff the table lists the expected power consumption when the system is in various states. I did not see any C3 state there, only C1. So I guess I have to use this board with the limitation or think about changing to a board that supports frequency scaling. Thanks for your support. Regards, Sven [1] http://downloadmirror.intel.com/19123/eng/D525MW_D525MWV_TechProdSpec.pdf
Re: frequency scaling on D525MW not working properly
On Fri, Aug 3, 2012 at 2:00 AM, Sven Gaerner wrote: > On Tue, Jul 31, 2012 at 09:27:15AM +0800, Sepherosa Ziehau wrote: >> On Tue, Jul 31, 2012 at 5:01 AM, Sven Gaerner wrote: >> [...] >> >> Hmm, maybe i8254 is not working at all. Could you post following >> information: >> - bootverbose dmesg w/ hw.i8254.intr_disable="0" in /boot/loader.conf >> - sysctl kern.cputimer >> - sysctl hw.acpi > > Attached the requested details. Grrr, only C1 is detected. If the CPU does support C3, there could be some settings in BIOS? Best Regards, sephe -- Tomorrow Will Never Die
Re: frequency scaling on D525MW not working properly
Also on the D5* atoms on FreeBSD it would be nice to check that it actually works as advertised, by running a few cpu-bound processes (i.e. for (;;); ) and measuring the watts being burned at different frequencies. That's the real proof that the frequency scaling is doing something real. -Matt
Re: frequency scaling on D525MW not working properly
On Tue, Jul 31, 2012 at 5:01 AM, Sven Gaerner wrote: > On Tue, Jul 24, 2012 at 09:59:35AM +0800, Sepherosa Ziehau wrote: >> On Tue, Jul 24, 2012 at 9:57 AM, Sepherosa Ziehau >> wrote: >> > On Tue, Jul 24, 2012 at 3:24 AM, Sven Gaerner wrote: >> >> On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: >> >>> On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner wrote: >> >>> > On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner >> >>> > wrote: >> >>> > >> >>> >> On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: >> >>> >>> >> >>> >>> On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner >> >>> >>> wrote: >> >>> >>> >> >>> >>> >[...] >> >>> >> > >> > I mean following steps: >> > 1) Add the following line into into /boot/loader.conf, then reboot: >> > hw.i8254.intr_disable="0" >> > 2) sysctl hw.acpi.cpu.cx_lowest=C3 >> >> I mean do step1) first, then do step 2) after step1)'s reboot. > > I did that, but I cannot set hw.acpi.cpu.cx_lowest=C3. I always get > "Invalid argument" when running "sudo sysctl hw.acpi.cpu.cx_lowest=C3". Hmm, maybe i8254 is not working at all. Could you post following information: - bootverbose dmesg w/ hw.i8254.intr_disable="0" in /boot/loader.conf - sysctl kern.cputimer - sysctl hw.acpi Best Regards, sephe > > Regards, > Sven > -- Tomorrow Will Never Die
Re: frequency scaling on D525MW not working properly
On Tue, Jul 24, 2012 at 09:59:35AM +0800, Sepherosa Ziehau wrote: > On Tue, Jul 24, 2012 at 9:57 AM, Sepherosa Ziehau wrote: > > On Tue, Jul 24, 2012 at 3:24 AM, Sven Gaerner wrote: > >> On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: > >>> On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner wrote: > >>> > On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner > >>> > wrote: > >>> > > >>> >> On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: > >>> >>> > >>> >>> On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner > >>> >>> wrote: > >>> >>> > >>> >>> >[...] > >>> > > > > I mean following steps: > > 1) Add the following line into into /boot/loader.conf, then reboot: > > hw.i8254.intr_disable="0" > > 2) sysctl hw.acpi.cpu.cx_lowest=C3 > > I mean do step1) first, then do step 2) after step1)'s reboot. I did that, but I cannot set hw.acpi.cpu.cx_lowest=C3. I always get "Invalid argument" when running "sudo sysctl hw.acpi.cpu.cx_lowest=C3". Regards, Sven
Re: frequency scaling on D525MW not working properly
On Wed, Jul 25, 2012 at 10:02:58AM +0200, Sascha Wildner wrote: > As Brian Mastenbrook pointed out in a comment on the digest, the > Atom should support P4TCC: > > http://www.shiningsilence.com/dbsdlog/2012/07/24/10128.html > > Check your CPU features in dmesg. It should show the TM feature, as > it does on my Atom 330 (second to last): > > Features=0xbfe9fbff > > Compiling the kernel with CPU_ENABLE_TCC gives new dmesg and sysctls: > > almsta# grep TCC /var/run/dmesg.boot > Pentium 4 TCC support enabled, current performance 13% > almsta# sysctl hw.p4tcc > hw.p4tcc.cpuperf: 13 > hw.p4tcc.cpuperf_performance: 100 > hw.p4tcc.cpuperf_economy: 13 > > However, a quick test with factor(6) showed no difference between 13 > and 100: > > almsta# sysctl hw.p4tcc.cpuperf=100 > hw.p4tcc.cpuperf: 13 -> 100 > almsta# time factor 23424111 > 23424111: 7 7 4780430839 > 4.726u 0.000s 0:04.77 98.9% 16+66k 0+0io 0pf+0w > > almsta# sysctl hw.p4tcc.cpuperf=13 > hw.p4tcc.cpuperf: 100 -> 13 > almsta# time factor 23424111 > 23424111: 7 7 4780430839 > 4.726u 0.007s 0:04.77 98.9% 16+66k 0+0io 0pf+0w > > Anyway, if your system is i386, try out adding "options > CPU_ENABLE_TCC" to the config and see what it gives. > > I'll see later today about providing it for x86_64 too. > > Sascha Thanks a lot for all the hints. I will try this options these days and get back with the results. Sven
Re: frequency scaling on D525MW not working properly
On Wed, 25 Jul 2012 10:05:54 +0200, william opensource4you wrote: All, just my 2 cents :-) since one week, I'm just installing dbsd on an hp-mini: Atom N455. I've no CPU related issues. Yeah, N* Atoms support Enhanced SpeedStep, while D* Atoms don't. Sascha
Re: frequency scaling on D525MW not working properly
All, just my 2 cents :-) since one week, I'm just installing dbsd on an hp-mini: Atom N455. I've no CPU related issues. here sysctl out put: hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.px_dom0.available: 1666 1333 1000 hw.acpi.cpu.px_dom0.members: cpu0(1000) hw.acpi.cpu.px_dom0.select: 1000 hw.acpi.cpu.px_global: 1666 hw.acpi.cpu0.cx_supported: C1/1 C2/1 C3/57 hw.acpi.cpu0.cx_lowest: C1 hw.acpi.cpu0.cx_usage: 100.00% 0.00% 0.00% last 5000us hw.acpi.cpu1.cx_supported: C1/1 C2/1 C3/57 hw.acpi.cpu1.cx_lowest: C1 hw.acpi.cpu1.cx_usage: 100.00% 0.00% 0.00% last 5000u powerd sounds to work: dfly# powerd -d qavg= 0.02 savg= 0.00 1/ 1 ncpus=0 dom0 set frequency 1000 qavg= 1.02 savg= 0.34 0/ 0 ncpus=1 dom0 set frequency 1666 qavg= 0.00 savg= 0.22 1/ 1 ncpus=0 dom0 set frequency 1000 qavg= 0.49 savg= 0.28 0/ 0 ncpus=1 Please note that I'm using dbsd current (21/07/2012). if I can help to perform additional tests ... do not hesitate, this is test machine. Regards William ps: Later I will post more details about what is working and what not. On Mon, Jul 23, 2012 at 9:54 PM, Sven Gaerner wrote: > On Mon, Jul 23, 2012 at 10:28:14AM +, Adrian Bocaniciu wrote: >> >> Intel Atom processors, unlike more expensive Intel processors, do not >> support frequency scaling. >> >> See for example the specifications for Atom D525 at: >> http://ark.intel.com/products/49490/ >> >> where it is stated that Enhanced Intel SpeedStep Technology is not >> supported. The same is written in all Atom datasheets. >> >> The only way to reduce the power consumption of Atom is to ensure that >> the processor is halted when it has nothing to do, i.e. in the idle >> loop, which I suppose that DragonFlyBSD does, or to use the ACPI C3 >> sleep state whenever you can tolerate the latency required for waking up >> the processor. >> >> I also have a couple of D525MW boards, but I have not tested >> DragonFlyBSD on them, and they are much less warm, but my Mini-ITX cases >> (Lian Li & Antec) have case coolers that ensure an adequate air flow >> inside the cases even if both the motherboards and the power supplies >> are fanless. > > Thanks for the details. I did not look at that point as I expected at > least frequency scaling which is supported by the Atom on the Fit-PC2 I > also use. > > I think I will try to get the temperature down by using a fan. But then > it is no longer a fanless system that I wanted to have running all the > time. And a system in a mini-ITX case with a temperature of 55 degrees > is not what I want to have running all the time. > > Thanks all for the help. I guess I will have to think about a > replacement to get a cooler fanless system. > > Regards, > Sven >
Re: frequency scaling on D525MW not working properly
On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner wrote: Hello, I bought an Atom based Intel D525MW board. DragonFly release is running on that system. But I have a few minor issues. The CPU is getting somewhat warm (about 55 degrees celsius). [...] As Brian Mastenbrook pointed out in a comment on the digest, the Atom should support P4TCC: http://www.shiningsilence.com/dbsdlog/2012/07/24/10128.html Check your CPU features in dmesg. It should show the TM feature, as it does on my Atom 330 (second to last): Features=0xbfe9fbff Compiling the kernel with CPU_ENABLE_TCC gives new dmesg and sysctls: almsta# grep TCC /var/run/dmesg.boot Pentium 4 TCC support enabled, current performance 13% almsta# sysctl hw.p4tcc hw.p4tcc.cpuperf: 13 hw.p4tcc.cpuperf_performance: 100 hw.p4tcc.cpuperf_economy: 13 However, a quick test with factor(6) showed no difference between 13 and 100: almsta# sysctl hw.p4tcc.cpuperf=100 hw.p4tcc.cpuperf: 13 -> 100 almsta# time factor 23424111 23424111: 7 7 4780430839 4.726u 0.000s 0:04.77 98.9% 16+66k 0+0io 0pf+0w almsta# sysctl hw.p4tcc.cpuperf=13 hw.p4tcc.cpuperf: 100 -> 13 almsta# time factor 23424111 23424111: 7 7 4780430839 4.726u 0.007s 0:04.77 98.9% 16+66k 0+0io 0pf+0w Anyway, if your system is i386, try out adding "options CPU_ENABLE_TCC" to the config and see what it gives. I'll see later today about providing it for x86_64 too. Sascha
Re: frequency scaling on D525MW not working properly
On Tue, Jul 24, 2012 at 9:57 AM, Sepherosa Ziehau wrote: > On Tue, Jul 24, 2012 at 3:24 AM, Sven Gaerner wrote: >> On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: >>> On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner wrote: >>> > On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner wrote: >>> > >>> >> On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: >>> >>> >>> >>> On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner >>> >>> wrote: >>> >>> >>> >>> >[...] >>> >>> Hmm, disabling UEFI is OK, but make sure that you have enabled EST in >>> BIOS (something probably read like "enhanced speed step" or something >>> like "P-state"). >> There is no such option. And the only UEFI option is to enable booting >> of an UEFI compliant OS. Speed stepping cannot be configured. The BIOS >> options are very limited. >> >>> Besides CPU P-State, you could also set allowable CPU C-State to C3 by >>> setting sysctl hw.acpi.cpu.cx_lowest and put tunable >>> hw.i8254.intr_disable="0" in /boot/loader.conf (you need to reboot >>> after changing /boot/loader.conf). However, it should be noted that >>> enabling C3 will disable LAPIC timer and i8254 timer will be used >>> instead, which may cause extra overhead. >> This seems not to change anything. The temperature remains the same. And >> setting hw.acpi.cpu.cx_lowest returns with "Invalid Argument". > > I mean following steps: > 1) Add the following line into into /boot/loader.conf, then reboot: > hw.i8254.intr_disable="0" > 2) sysctl hw.acpi.cpu.cx_lowest=C3 I mean do step1) first, then do step 2) after step1)'s reboot. i8254 is intentionally disabled by default, so some mobo w/o it could boot properly. Best Regards, sephe > > Best Regards, > sephe > > -- > Tomorrow Will Never Die -- Tomorrow Will Never Die
Re: frequency scaling on D525MW not working properly
On Tue, Jul 24, 2012 at 3:24 AM, Sven Gaerner wrote: > On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: >> On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner wrote: >> > On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner wrote: >> > >> >> On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: >> >>> >> >>> On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner >> >>> wrote: >> >>> >> >>> >[...] >> >> Hmm, disabling UEFI is OK, but make sure that you have enabled EST in >> BIOS (something probably read like "enhanced speed step" or something >> like "P-state"). > There is no such option. And the only UEFI option is to enable booting > of an UEFI compliant OS. Speed stepping cannot be configured. The BIOS > options are very limited. > >> Besides CPU P-State, you could also set allowable CPU C-State to C3 by >> setting sysctl hw.acpi.cpu.cx_lowest and put tunable >> hw.i8254.intr_disable="0" in /boot/loader.conf (you need to reboot >> after changing /boot/loader.conf). However, it should be noted that >> enabling C3 will disable LAPIC timer and i8254 timer will be used >> instead, which may cause extra overhead. > This seems not to change anything. The temperature remains the same. And > setting hw.acpi.cpu.cx_lowest returns with "Invalid Argument". I mean following steps: 1) Add the following line into into /boot/loader.conf, then reboot: hw.i8254.intr_disable="0" 2) sysctl hw.acpi.cpu.cx_lowest=C3 Best Regards, sephe -- Tomorrow Will Never Die
Re: frequency scaling on D525MW not working properly
On Mon, 23 Jul 2012 21:24:38 +0200, Sven Gaerner wrote: On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner wrote: > On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner wrote: > >> On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: >>> >>> On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner >>> wrote: >>> >>> >[...] Hmm, disabling UEFI is OK, but make sure that you have enabled EST in BIOS (something probably read like "enhanced speed step" or something like "P-state"). There is no such option. And the only UEFI option is to enable booting of an UEFI compliant OS. Speed stepping cannot be configured. The BIOS options are very limited. It looks like the Atom D525 (along with the rest of D*) does not support it: http://ark.intel.com/products/49490 Only N*, Z* and E* Atoms seem to have it: http://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors Sascha
Re: frequency scaling on D525MW not working properly
On Mon, Jul 23, 2012 at 10:28:14AM +, Adrian Bocaniciu wrote: > > Intel Atom processors, unlike more expensive Intel processors, do not > support frequency scaling. > > See for example the specifications for Atom D525 at: > http://ark.intel.com/products/49490/ > > where it is stated that Enhanced Intel SpeedStep Technology is not > supported. The same is written in all Atom datasheets. > > The only way to reduce the power consumption of Atom is to ensure that > the processor is halted when it has nothing to do, i.e. in the idle > loop, which I suppose that DragonFlyBSD does, or to use the ACPI C3 > sleep state whenever you can tolerate the latency required for waking up > the processor. > > I also have a couple of D525MW boards, but I have not tested > DragonFlyBSD on them, and they are much less warm, but my Mini-ITX cases > (Lian Li & Antec) have case coolers that ensure an adequate air flow > inside the cases even if both the motherboards and the power supplies > are fanless. Thanks for the details. I did not look at that point as I expected at least frequency scaling which is supported by the Atom on the Fit-PC2 I also use. I think I will try to get the temperature down by using a fan. But then it is no longer a fanless system that I wanted to have running all the time. And a system in a mini-ITX case with a temperature of 55 degrees is not what I want to have running all the time. Thanks all for the help. I guess I will have to think about a replacement to get a cooler fanless system. Regards, Sven
Re: frequency scaling on D525MW not working properly
On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: > On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner wrote: > > On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner wrote: > > > >> On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: > >>> > >>> On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner > >>> wrote: > >>> > >>> >[...] > > Hmm, disabling UEFI is OK, but make sure that you have enabled EST in > BIOS (something probably read like "enhanced speed step" or something > like "P-state"). There is no such option. And the only UEFI option is to enable booting of an UEFI compliant OS. Speed stepping cannot be configured. The BIOS options are very limited. > Besides CPU P-State, you could also set allowable CPU C-State to C3 by > setting sysctl hw.acpi.cpu.cx_lowest and put tunable > hw.i8254.intr_disable="0" in /boot/loader.conf (you need to reboot > after changing /boot/loader.conf). However, it should be noted that > enabling C3 will disable LAPIC timer and i8254 timer will be used > instead, which may cause extra overhead. This seems not to change anything. The temperature remains the same. And setting hw.acpi.cpu.cx_lowest returns with "Invalid Argument". Updating the BIOS to a more recent version did also not help. Thanks for your hints. Sven
Re: frequency scaling on D525MW not working properly
On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner wrote: > On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner wrote: > >> On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: >>> >>> On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner >>> wrote: >>> >>> >[...] >>> >Also there is no sysctl hw.acpi.cpu.px_dom0.select available, >>> >so I guess powerd is also running not properly and the CPU >>> >frequency is not >>> >scaled in any way. After looking into the dmesg output, I guess >>> >some driver does >>> >not recognize parts of the hardware/ACPI stuff correctly (see >>> >below; the text is >>> >repeated for the other 3 logical CPUs). cpu0: on acpi0 cpu_cst0: >>> >on cpu0 cpu_pst0: >>> >Can't get _PSS package - AE_NOT_FOUND The dmesg is attached. It >>> >would be great >>> >if there is someone who can help me to get this fixed. If more >>> >details are >>> >necessary, just let me know. Sven >>> >>> Is this a mobo with UEFI? >>> >>> Sascha >> >> >> Yes, but booting via UEFI is disabled. Hmm, disabling UEFI is OK, but make sure that you have enabled EST in BIOS (something probably read like "enhanced speed step" or something like "P-state"). Besides CPU P-State, you could also set allowable CPU C-State to C3 by setting sysctl hw.acpi.cpu.cx_lowest and put tunable hw.i8254.intr_disable="0" in /boot/loader.conf (you need to reboot after changing /boot/loader.conf). However, it should be noted that enabling C3 will disable LAPIC timer and i8254 timer will be used instead, which may cause extra overhead. Best Regards, sephe -- Tomorrow Will Never Die
Re: frequency scaling on D525MW not working properly
On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner wrote: On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner wrote: >[...] >Also there is no sysctl hw.acpi.cpu.px_dom0.select available, >so I guess powerd is also running not properly and the CPU >frequency is not >scaled in any way. After looking into the dmesg output, I guess >some driver does >not recognize parts of the hardware/ACPI stuff correctly (see >below; the text is >repeated for the other 3 logical CPUs). cpu0: on acpi0 cpu_cst0: >on cpu0 cpu_pst0: >Can't get _PSS package - AE_NOT_FOUND The dmesg is attached. It >would be great >if there is someone who can help me to get this fixed. If more >details are >necessary, just let me know. Sven Is this a mobo with UEFI? Sascha Yes, but booting via UEFI is disabled. IIRC the performance state stuff will not work w/ UEFI. Cc to sephe, as I think he knew more. Sascha
Re: frequency scaling on D525MW not working properly
On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: > On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner wrote: > > >[...] > >Also there is no sysctl hw.acpi.cpu.px_dom0.select available, > >so I guess powerd is also running not properly and the CPU > >frequency is not > >scaled in any way. After looking into the dmesg output, I guess > >some driver does > >not recognize parts of the hardware/ACPI stuff correctly (see > >below; the text is > >repeated for the other 3 logical CPUs). cpu0: on acpi0 cpu_cst0: > >on cpu0 cpu_pst0: > >Can't get _PSS package - AE_NOT_FOUND The dmesg is attached. It > >would be great > >if there is someone who can help me to get this fixed. If more > >details are > >necessary, just let me know. Sven > > Is this a mobo with UEFI? > > Sascha Yes, but booting via UEFI is disabled. Sven
Re: frequency scaling on D525MW not working properly
On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner wrote: [...] Also there is no sysctl hw.acpi.cpu.px_dom0.select available, so I guess powerd is also running not properly and the CPU frequency is not scaled in any way. After looking into the dmesg output, I guess some driver does not recognize parts of the hardware/ACPI stuff correctly (see below; the text is repeated for the other 3 logical CPUs). cpu0: on acpi0 cpu_cst0: on cpu0 cpu_pst0: Can't get _PSS package - AE_NOT_FOUND The dmesg is attached. It would be great if there is someone who can help me to get this fixed. If more details are necessary, just let me know. Sven Is this a mobo with UEFI? Sascha
frequency scaling on D525MW not working properly
Hello, I bought an Atom based Intel D525MW board. DragonFly release is running on that system. But I have a few minor issues. The CPU is getting somewhat warm (about 55 degrees celsius). This is not a real problem, because it is not too hot. But I think this occurs because the frequency scaling does not work. Running "sysctl hw.acpi" prints the following lines (I cut the output to one logical CPU, but for the other three the output is identical): hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu0.cx_supported: C1/3 hw.acpi.cpu0.cx_lowest: C1 hw.acpi.cpu0.cx_usage: 100.00% last 5000us Also there is no sysctl hw.acpi.cpu.px_dom0.select available, so I guess powerd is also running not properly and the CPU frequency is not scaled in any way. After looking into the dmesg output, I guess some driver does not recognize parts of the hardware/ACPI stuff correctly (see below; the text is repeated for the other 3 logical CPUs). cpu0: on acpi0 cpu_cst0: on cpu0 cpu_pst0: Can't get _PSS package - AE_NOT_FOUND The dmesg is attached. It would be great if there is someone who can help me to get this fixed. If more details are necessary, just let me know. Sven Copyright (c) 2003-2012 The DragonFly Project. Copyright (c) 1992-2003 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. DragonFly v3.0.2.70.gd51ef-RELEASE #2: Thu Jul 19 22:17:26 CEST 2012 r...@marvin.fritz.box:/usr/obj/usr/src/sys/GENERIC TSC clock: 1800110025 Hz, i8254 clock: 1193212 Hz CPU: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (1800.08-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106ca Stepping = 10 Features=0xbfebfbff Features2=0x40e31d AMD Features=0x2010 AMD Features2=0x1 real memory = 4277054464 (4078 MB) avail memory = 3344994304 (3190 MB) lapic: divisor index 0, frequency 13876 Hz Initialize MI interrupts module_register: module dsched_fq already exists! Module dsched_fq failed to register: 17 module_register_init: MOD_LOAD (powernow, c0ddadba, 0) error 2 FQ scheduler policy version 1.1 loaded FQ scheduler policy unloaded module_register_init: MOD_LOAD (dsched_fq, c0dde030, 0) error 17 kbd0 at kbdmux0 disk scheduler: set policy of md0 to noop md0: Malloc disk ACPI: RSDP 0xf2060 00024 (v2 INTEL ) ACPI: XSDT 0xceffe120 0004C (v1 INTEL D525MW 0053 0113) ACPI: FACP 0xceffd000 000F4 (v3 INTEL D525MW 0053 MSFT 010D) ACPI: DSDT 0xceff9000 03796 (v1 INTEL D525MW 0053 MSFT 010D) ACPI: FACS 0xcef87000 00040 ACPI: APIC 0xceff8000 00084 (v2 INTEL D525MW 0053 MSFT 010D) ACPI: MCFG 0xceff7000 0003C (v1 INTEL D525MW 0053 MSFT 010D) ACPI: HPET 0xceff6000 00038 (v1 INTEL D525MW 0053 MSFT 010D) ACPI: SSDT 0xceff2000 0377C (v1 INTEL D525MW 0053 MSFT 010D) npx0: on motherboard npx0: INT 16 interface Using XMM optimized bcopy/copyin/copyout cryptosoft0: on motherboard acpi0: on motherboard ACPI FADT: SCI testing interrupt mode ... sched_ithd: stray interrupt 9 on cpu0 ACPI FADT: SCI select level/high objcache_reclaimlist objcache_reclaimlist objcache_reclaimlist objcache_reclaimlist acpi0: Power Button (fixed) Warning: ACPI is disabling APM's device. You can't run both acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 acpi_hpet0: frequency 14318180 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x20c0-0x20c7 mem 0xf010-0xf01f,0xe000-0xefff,0xf020-0xf027 irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 8188k stolen memory agp0: aperture size is 256M pci0: (vendor 0x8086, dev 0x27d8) at device 27.0 irq 22 pcib1: at device 28.0 on pci0 pci1: on pcib1 re0: port 0x1000-0x10ff mem 0xf000-0xf0003fff,0xf0004000-0xf0004fff irq 16 at device 0.0 on pci1 re0: Hardware rev. 0x2c00; MAC ver. 0x2f; PCI-E 125MHz miibus0: on re0 rgephy0: <8211B/RTL8169S/8110S media interface> on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: MAC address: e8:40:f2:3d:9b:10 pcib2: at device 28.1 on pci0 pci2: on pcib2 pcib3: at device 28.2 on pci0 pci3: on pcib3 pcib4: at device 28.3 on pci0 pci4: on pcib4 uhci0: port 0x2080-0x209f irq 23 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2060-0x207f irq 19 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x2040-0x205f irq 18 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x2020-0x203f irq 16 at device 29.3 on pci0 usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xf
