Re: Motherboard advice
Hi, On Mon, Jul 30, 2012 at 05:37:41AM +, Jelle Hermsen wrote: I'm going to build a new workstation and since I'll only be running Dragonfly I want to take this opportunity to get it right. I've been using laptops for years and I must admit I can't quite see the forest for the trees here. I know that I want to have ECC memory and I would love to have some kind of graphics chipset that just works without too much hassle (since I'll mostly be running a terminal in X). Have a look at the supported hardware page: http://www.dragonflybsd.org/docs/supportedhardware/ For ECC support, you'll probably need to use a server board and add discrete sound and graphics cards. These two Supermicro boards are the only ones with ECC support + sound onboard I know of: http://www.supermicro.nl/products/motherboard/Xeon/C600/X9SRA.cfm http://www.supermicro.nl/products/motherboard/Xeon/C600/X9DAi.cfm There is also one Asus workstation board which *may* support ECC. -- Francois Tigeot
Re: Motherboard advice
On 07/30/2012 08:06 AM, Francois Tigeot wrote: Hi, On Mon, Jul 30, 2012 at 05:37:41AM +, Jelle Hermsen wrote: I'm going to build a new workstation and since I'll only be running Dragonfly I want to take this opportunity to get it right. I've been using laptops for years and I must admit I can't quite see the forest for the trees here. I know that I want to have ECC memory and I would love to have some kind of graphics chipset that just works without too much hassle (since I'll mostly be running a terminal in X). Have a look at the supported hardware page: http://www.dragonflybsd.org/docs/supportedhardware/ For ECC support, you'll probably need to use a server board and add discrete sound and graphics cards. These two Supermicro boards are the only ones with ECC support + sound onboard I know of: http://www.supermicro.nl/products/motherboard/Xeon/C600/X9SRA.cfm http://www.supermicro.nl/products/motherboard/Xeon/C600/X9DAi.cfm There is also one Asus workstation board which *may* support ECC. Thanks for the tip. I'll take a look at those Supermicro boards. Cheers, Jelle
watchdog question
Dear readers, because of a problem of a system freezing up ever so often (and so hard that even the kernel debugger wont launch), I am looking into activating the hardware watchdog. I've configured it in the kernel and it is recognized all well. Now, my question: I read the kernel.watchdog.auto and kernel.watchdog.period knobs to mean the kernel can auto-update the kernel; on the other hand, the documentation refers me to the watchdogd daemon. The latter one claims /dev/wdog isn't writable. But why have two solutions to one problem? Doesn't the kernel auto updating suffice, anyway? Thank you, Konrad
Re: watchdog question
On Mon, 30 Jul 2012 15:58:25 +0200, Konrad Neuwirth kon...@fimsch.net wrote: Dear readers, because of a problem of a system freezing up ever so often (and so hard that even the kernel debugger wont launch), I am looking into activating the hardware watchdog. I've configured it in the kernel and it is recognized all well. What did you exactly configure in the kernel? Is this 3.0 or master? Sascha
Re: watchdog question
On 30/07/12 14:58, Konrad Neuwirth wrote: Now, my question: I read the kernel.watchdog.auto and kernel.watchdog.period knobs to mean the kernel can auto-update the kernel; on the other hand, the documentation refers me to the watchdogd daemon. The latter one claims /dev/wdog isn't writable. But why have two solutions to one problem? Doesn't the kernel auto updating suffice, anyway? There are two options: the kernel auto-refreshing or a userland process (watchdogd) refreshing. Whether you want one or the other depends; obviously the kernel auto-refresh is more convenient, but it may not be sufficient for your scenario. Just picture userland processes hanging but bits of the kernel going on. This is a scenario that only the latter option will get you out of. HTH, Alex
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=0xbfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE 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 Tue, Jul 24, 2012 at 09:59:35AM +0800, Sepherosa Ziehau wrote: On Tue, Jul 24, 2012 at 9:57 AM, Sepherosa Ziehau sepher...@gmail.com wrote: On Tue, Jul 24, 2012 at 3:24 AM, Sven Gaerner sgaer...@gmx.net 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 s...@online.de wrote: On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner sgaer...@gmx.net 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 sgaer...@gmx.net 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 Tue, Jul 31, 2012 at 5:01 AM, Sven Gaerner sgaer...@gmx.net 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 sepher...@gmail.com wrote: On Tue, Jul 24, 2012 at 3:24 AM, Sven Gaerner sgaer...@gmx.net 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 s...@online.de wrote: On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner sgaer...@gmx.net 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 sgaer...@gmx.net 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
