Re: hardware for home use large storage
2010/3/21 Andriy Gapon : > on 09/02/2010 14:53 Andriy Gapon said the following: >> on 09/02/2010 12:32 Matthew D. Fuller said the following: >>> On Tue, Feb 09, 2010 at 04:37:50PM +1030 I heard the voice of >>> Daniel O'Connor, and lo! it spake thus: Probably the result of idiotic penny pinching though :-/ >>> Irritating. One of my favorite parts of AMD's amd64 chips is that I >>> no longer have to spend through the nose or be a detective (or, often, >>> both) to get ECC. So far, it seems like there are relatively few >>> hidden holes on that path, and I haven't stepped in one, but every new >>> one I hear about increases my terror of the day when there are more >>> holes than solid ground :( >> >> Yep. >> For sure, Gigabyte BIOS on this board is completely missing ECC >> initialization >> code. I mean not only the menus in setup, but the code that does memory >> controller programming. >> Not sure about the physical lanes though. > > BTW, not 100% sure if I my test method was correct, but it seems that ECC pins > of DIMM sockets (CB0, CB1, etc) of my motherboard (GA-MA780G-UD3H) are not > connected to anywhere. > So looks like Gigabyte is saving some cents on this. > Hi, I got this reply from Gigabyte about my concern about actual ECC support on board: Model Name : GA-X48-DS4(rev. 1.3) --- Dear Sir, Thank you for your kindly mail and inquiry. About the issue you mentioned, we do not guarantee all Third party H/W monitor utilities will work properly with our motherboard because most of the S/W does not know our H/W design and impossible optimize their S/W for our motherboard. We are sorry if there is any inconvenience. In addition, basically, if you could boot up your system with ECC memory module, it means your motherboard could fully support the ECC memory module. If the motherboard does not support the ECC memory, you could not use this kind of memory module for the system to use. By the way, ECC function will automatically enable in the BIOS program. You do not need to turn on it manually. --- I call this bullshit because all testing utilities I used, not a single one confirmed any presence of ECC. Also, most of the Asus boards are extremely unstable with ECC enabled. Finally I replaced my Kingston ECC DDR2 with no-ECC memory on Asus board and bought Intel s3210shlx server board for my workstation. Andrei Kolu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Can't boot after make installworld
The ZFS bootloader has been changed in 8-STABLE compared to 8.0-RELEASE. Reinstall your boot blocks. P.S: "LOADER_ZFS_SUPPORT=YES" is also deprecated in 8-STABLE, not to mention that you have it in the wrong place, for 8.0, it goes into make.conf, not src.conf. Is there any particular reason you are upgrading from a production release to a development branch of the OS? - Sincerely, Dan Naumov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Can't boot after make installworld
On Mon, 22 Mar 2010 07:13, Dan Naumov wrote:
In Message-Id:
The ZFS bootloader has been changed in 8-STABLE compared to
8.0-RELEASE. Reinstall your boot blocks.
P.S: "LOADER_ZFS_SUPPORT=YES" is also deprecated in 8-STABLE, not to
mention that you have it in the wrong place, for 8.0, it goes into
make.conf, not src.conf.
P.S.S: src.conf is the correct place this should be placed but will also
work if placed in make.conf.
As stated in src.conf(5)
---
The src.conf file contains settings that will apply to every build
involving the FreeBSD source tree; see build(7).
The src.conf file uses the standard makefile syntax. However, src.conf
should not specify any dependencies to make(1). Instead, src.conf is to
set make(1) variables that control the aspects of how the system builds.
---
It would be almost to the same effect of doing this at the end of your
make.conf except it has already been done for you elsewhere.
.if ${.CURDIR:M/usr/src*}
.include "/etc/src.conf"
.endif
Is there any particular reason you are upgrading from a production
release to a development branch of the OS?
- Sincerely,
Dan Naumov
Regards,
--
jhell
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Can't boot after make installworld
On Mar 22, 2010, at 7:01 AM, jhell wrote:
On Mon, 22 Mar 2010 07:13, Dan Naumov wrote:
In Message-Id: >
The ZFS bootloader has been changed in 8-STABLE compared to
8.0-RELEASE. Reinstall your boot blocks.
P.S: "LOADER_ZFS_SUPPORT=YES" is also deprecated in 8-STABLE, not to
mention that you have it in the wrong place, for 8.0, it goes into
make.conf, not src.conf.
P.S.S: src.conf is the correct place this should be placed but will
also work if placed in make.conf.
As stated in src.conf(5)
---
The src.conf file contains settings that will apply to every build
involving the FreeBSD source tree; see build(7).
The src.conf file uses the standard makefile syntax. However,
src.conf should not specify any dependencies to make(1). Instead,
src.conf is to set make(1) variables that control the aspects of how
the system builds.
---
It would be almost to the same effect of doing this at the end of
your make.conf except it has already been done for you elsewhere.
.if ${.CURDIR:M/usr/src*}
.include "/etc/src.conf"
.endif
And can be easily tuned via the SRCCONF variable (unless of course
WITHOUT_SRCCONF is defined...), as this logic is a part of bsd.own.mk .
Cheers,
-Garrett
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Can't boot after make installworld
On 3/22/10, Dan Naumov wrote: > The ZFS bootloader has been changed in 8-STABLE compared to > 8.0-RELEASE. Reinstall your boot blocks. Thanks for pointers, I will run gpart to reinstall bootcode on my SD card. > Is there any particular reason you are upgrading from a production > release to a development branch of the OS? I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx chipset and as I own motherboard with HD3300 built-in I thought that I would give it a try. I upgraded to see if there is any progress with ¿zfs? I don't really know if it's zfs related, but at certain load, my system crashes, and reboots. It happens only when using bonnie++ to benchmark I/O. And I'm a little bit to lazy to prepare my system for coredumps - I don't have swap slice for crashdumps, because I wanted to simplify adding drives to my raidz1 configuration. Could anyone tell me what's needed, besides having swap to produce good crashdump? At first I didn't knew that I am upgrading to bleeding edge/developer branch of FreeBSD. I'll come straight out with it, 8.0-STABLE sounds more stable than 8.0-RELEASE-p2, which I was running before upgrade ;) I'm a little confused with FreeBSD release cycle at first I compared it with Debian release cycle, because I'm most familiar to it, and I used it a lot before using FreeBSD. Debian development is more one-dimensional - unstable/testing/stable/oldstable whereas FreeBSD has two stable branches - 8.0 and 7.2 which are actively developed. But still I am confused with FreeBSD naming and it's relation with tags which are used in standard-supfile. We have something like this: 9.0-CURRENT -> tag=. 8.0-STABLE -> tag=RELENG_8 8.0-RELEASE-p2 -> tag=RELENG_8_0 ? (btw what does p2 mean?) If someone patient could explain it to me I'd be grateful. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Can't boot after make installworld
> I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx > chipset and as I own motherboard with HD3300 built-in I thought that I > would give it a try. I upgraded to see if there is any progress with > ¿zfs? I don't really know if it's zfs related, but at certain load, my > system crashes, and reboots. It happens only when using bonnie++ to > benchmark I/O. And I'm a little bit to lazy to prepare my system for > coredumps - I don't have swap slice for crashdumps, because I wanted > to simplify adding drives to my raidz1 configuration. Could anyone > tell me what's needed, besides having swap to produce good crashdump? As of right now, even if you don't care about capability to take crash dumps, it is highly recommended to still use traditional swap partitions even if your system is otherwise fully ZFS. There are know stability problems involving using a ZVOL as a swap device. These issues are being worked on, but this is still the situation as of now. > At first I didn't knew that I am upgrading to bleeding edge/developer > branch of FreeBSD. I'll come straight out with it, 8.0-STABLE sounds > more stable than 8.0-RELEASE-p2, which I was running before upgrade ;) > I'm a little confused with FreeBSD release cycle at first I compared > it with Debian release cycle, because I'm most familiar to it, and I > used it a lot before using FreeBSD. Debian development is more > one-dimensional - unstable/testing/stable/oldstable whereas FreeBSD > has two stable branches - 8.0 and 7.2 which are actively developed. > But still I am confused with FreeBSD naming and it's relation with > tags which are used in standard-supfile. We have something like this: > 9.0-CURRENT -> tag=. > 8.0-STABLE -> tag=RELENG_8 > 8.0-RELEASE-p2 -> tag=RELENG_8_0 ? (btw what does p2 mean?) > If someone patient could explain it to me I'd be grateful. 9-CURRENT: the real crazyland 8-STABLE: a dev branch, from which 8.0 was tagged and eventually 8.1 will be RELENG_8_0: 8.0-RELEASE + latest critical security and reliability updates (8.0 is up to patchset #2, hence -p2) Same line of thinking applies to 7-STABLE, 7.3-RELEASE and so on. - Sincerely, Dan Naumov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Can't boot after make installworld
On Mon, Mar 22, 2010 at 10:41 PM, Krzysztof Dajka wrote: > I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx > chipset and as I own motherboard with HD3300 built-in I thought that I > would give it a try. I upgraded to see if there is any progress with > ¿zfs? I don't really know if it's zfs related, but at certain load, my > system crashes, and reboots. It happens only when using bonnie++ to > benchmark I/O. If you can consistently panic your 8.0 system with just bonnie++ alone, something is really really wrong. Are you using an amd64 system with 2gb ram or more or is this i386 + 1-2gb ram? Amd64 systems with 2gb ram or more don't really usually require any tuning whatsoever (except for tweaking performance for a specific workload), but if this is i386, tuning will be generally required to archieve stability. - Sincerely, Dan Naumov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Powerd and est / eist functionality
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: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 6160b2506000b25 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 6160b2506000b25 device_attach: est1 attach returned 6 p4tcc1: 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 = 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 r...@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 Features2=0x408e3bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 1073741824 (1024 MB) avail memory = 983613440 (938 MB) ACPI APIC Table: 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 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3dbe (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: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0xe400-0xe407 mem 0xe300-0xe33f,0xd000-0xdfff irq 16 at device 2.0 on pci0 pci0: at device 27.0 (no driver attached) pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 pcib2: irq 17 at device 28.1 on pci0 pci2: on pcib2 re0: port 0xc000-0xc0ff mem 0xe341000 0-0xe3410fff,0xe340-0xe340 irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x3c00 re0: MAC rev. 0x0040 miibus0: on re0 rgephy0: 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: port 0xe000-0xe01f irq 23 at device 29.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x003b usbus0: on uhci0 uhci1: port 0xe100-0xe11f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x0010 usbus1: on uhci1 uhci2: port 0xe200-0xe21f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x0010 usbus2: on uhci2 uhci3: port 0xe300-0xe31f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] uhci3: LegSup = 0x0010 usbus3: on uhci3 ehci0: mem 0xe3504000-0xe35043ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: waiting
Re: Powerd and est / eist functionality
On Mon, March 22, 2010 19:57, John Long wrote: >dmesg shows >cpu0: on acpi0 >est0: on cpu0 >est: CPU supports Enhanced Speedstep, but is not recognized. >est: cpu_vendor GenuineIntel, msr 6160b2506000b25 >device_attach: est0 attach returned 6 >p4tcc0: on cpu0 >cpu1: on acpi0 >est1: on cpu1 >est: CPU supports Enhanced Speedstep, but is not recognized. >est: cpu_vendor GenuineIntel, msr 6160b2506000b25 >device_attach: est1 attach returned 6 >p4tcc1: on cpu1 I 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Does zfs have it's own nfs server?
On Sat, 20 Mar 2010, Willem Jan Withagen wrote: On 20-3-2010 0:50, Charles Sprickman wrote: Just wondering, is this using the base nfsd/mountd, or is there some in-kernel nfs code strictly for zfs? I haven't found much info on the share* options in the manpage or wiki. There's also the complete ZFS manual you should read: http://dlc.sun.com/pdf/819-5461/819-5461.pdf Anyone know how to tie the version of that document to the current version that's in FreeBSD? Overall, it's a great reference. Already answered a number of questions. Here's another Sun doc that I used to get started: http://hub.opensolaris.org/bin/download/Community+Group+zfs/demos/zfsdemo.pdf It looks like it's for sales engineers who are going to do a demo of ZFS, however it works quite well as a quick-start. It describes the basic concepts well and walks you through creating some pools. It's hands-down my favorite "Intro to ZFS" doc that I've found so far. Thanks, Charles It's for Solaris, so perhaps not everything works on FreeBSD. But most of it will. Could you give an example of passing options that would say, limit to a subnet and map root to root using the zfs sharenfs command? Something like this: (Email might wrap the line) zfs set sharenfs='-alldirs -maproot=0 -network 192.168.10.0 -mask 255.255.255.0' zfsdata/home/wjw to export /home/wjw which is available as /zfsdata/home/wjw in ZFS. All the zfs does is add this to the /etc/zfs/exports file. And then the regular mountd/nfsd combo does the NDS-service. --WjW ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Powerd and est / eist functionality
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: on acpi0 >est0: on cpu0 >est: CPU supports Enhanced Speedstep, but is not recognized. >est: cpu_vendor GenuineIntel, msr 6160b2506000b25 >device_attach: est0 attach returned 6 >p4tcc0: on cpu0 >cpu1: on acpi0 >est1: on cpu1 >est: CPU supports Enhanced Speedstep, but is not recognized. >est: cpu_vendor GenuineIntel, msr 6160b2506000b25 >device_attach: est1 attach returned 6 >p4tcc1: 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
