freebsd-stable Digest, Vol 349, Issue 2
freebsd-sta...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. RE: Can't boot after make installworld (jhell)
2. Re: Can't boot after make installworld (Garrett Cooper)
3. Re: Can't boot after make installworld (Krzysztof Dajka)
4. Re: Can't boot after make installworld (Dan Naumov)
5. Re: Can't boot after make installworld (Dan Naumov)
6. Powerd and est / eist functionality (John Long)
7. Re: Powerd and est / eist functionality (Nenhum_de_Nos)
8. Re: Does zfs have it's own nfs server? (Charles Sprickman)
9. Re: Powerd and est / eist functionality (Alexander Motin)
10. upcoming 7.3-RELEASE: zfsloader doesn't support ZFS (doesn't
link with libzfsboot) (Alexander Zagrebin)
11. Re: Can't boot after make installworld (alte...@gmail.com)
12. Re: Can't boot after make installworld (alte...@gmail.com)
----------------------------------------------------------------------
Message: 1
Date: Mon, 22 Mar 2010 10:01:39 -0400
From: jhell <jh...@DataIX.net>
Subject: RE: Can't boot after make installworld
To: Dan Naumov <dan.n...@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>,
alte...@gmail.com
Message-ID: <alpine.BSF.2.00.1...@pragry.qngnvk.ybpny>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Mon, 22 Mar 2010 07:13, Dan Naumov wrote:
In Message-Id: <cf9b1ee01003220413t14a...@mail.gmail.com>
> 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
------------------------------
Message: 2
Date: Mon, 22 Mar 2010 08:47:31 -0700
From: Garrett Cooper <yane...@gmail.com>
Subject: Re: Can't boot after make installworld
To: jhell <jh...@DataIX.net>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>, Dan
Naumov <dan.n...@gmail.com>, "alte...@gmail.com"
<alte...@gmail.com>
Message-ID: <00E5A20A-4AB5-4769...@gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
On Mar 22, 2010, at 7:01 AM, jhell <jh...@DataIX.net> wrote:
>
> On Mon, 22 Mar 2010 07:13, Dan Naumov wrote:
> In Message-Id: <cf9b1ee01003220413t14a...@mail.gmail.com
> >
>
>> 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
------------------------------
Message: 3
Date: Mon, 22 Mar 2010 20:41:35 +0000
From: Krzysztof Dajka <alte...@gmail.com>
Subject: Re: Can't boot after make installworld
To: Dan Naumov <dan.n...@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>
Message-ID:
<684e57ec1003221341s241...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On 3/22/10, Dan Naumov <dan.n...@gmail.com> 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.
------------------------------
Message: 4
Date: Mon, 22 Mar 2010 23:55:17 +0200
From: Dan Naumov <dan.n...@gmail.com>
Subject: Re: Can't boot after make installworld
To: Krzysztof Dajka <alte...@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>
Message-ID:
<cf9b1ee01003221455i7fc...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
> 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
------------------------------
Message: 5
Date: Tue, 23 Mar 2010 00:00:17 +0200
From: Dan Naumov <dan.n...@gmail.com>
Subject: Re: Can't boot after make installworld
To: Krzysztof Dajka <alte...@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>
Message-ID:
<cf9b1ee01003221500j6c6...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Mar 22, 2010 at 10:41 PM, Krzysztof Dajka <alte...@gmail.com> 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
------------------------------
Message: 6
Date: Mon, 22 Mar 2010 15:57:35 -0700
From: John Long <fb...@sstec.com>
Subject: Powerd and est / eist functionality
To: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>
Message-ID: <5.2.1.1.2.201003...@mail.sstec.com>
Content-Type: text/plain; charset="us-ascii"
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
ro...@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
------------------------------
Message: 7
Date: Mon, 22 Mar 2010 23:55:57 -0300 (BRT)
From: "Nenhum_de_Nos" <mat...@eternamente.info>
Subject: Re: Powerd and est / eist functionality
To: freebsd...@freebsd.org
Message-ID: <a333ac6f65b2061fbc46994599f969ba.squirrel@lamneth>
Content-Type: text/plain;charset=iso-8859-1
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
--
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
------------------------------
Message: 8
Date: Tue, 23 Mar 2010 00:42:03 -0400 (EDT)
From: Charles Sprickman <sp...@bway.net>
Subject: Re: Does zfs have it's own nfs server?
To: Willem Jan Withagen <w...@digiware.nl>
Cc: Matthias Gamsjager <mgams...@gmail.com>, FreeBSD Stable Users
<freebsd...@freebsd.org>
Message-ID:
<alpine.OSX.2.00.1...@charles-sprickmans-imac.local>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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
>
>
>
>
------------------------------
Message: 9
Date: Tue, 23 Mar 2010 08:27:18 +0200
From: Alexander Motin <m...@FreeBSD.org>
Subject: Re: Powerd and est / eist functionality
To: John Long <fb...@sstec.com>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>
Message-ID: <4BA85F46...@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1
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
------------------------------
Message: 10
Date: Tue, 23 Mar 2010 10:41:06 +0300
From: "Alexander Zagrebin" <al...@visp.ru>
Subject: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS (doesn't
link with libzfsboot)
To: <freebsd...@freebsd.org>
Message-ID: <74426BABA82C4FD2...@vosz.local>
Content-Type: text/plain; charset="koi8-r"
I have tried to build RELENG_7_3_0_RELEASE and have noticed that zfsloader
really doesn't supports ZFS due to incomplete Makefiles (LOADER_ZFS_SUPPORT
issue).
Will be this issue fixed in 7.3-RELEASE?
--
Alexander Zagrebin
------------------------------
Message: 11
Date: Tue, 23 Mar 2010 10:28:10 +0100
From: "alte...@gmail.com" <alte...@gmail.com>
Subject: Re: Can't boot after make installworld
To: Dan Naumov <dan.n...@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>
Message-ID: <201003231028....@gmail.com>
Content-Type: Text/Plain; charset="iso-8859-1"
On Monday, 22 of March 2010 23:00:17 Dan Naumov wrote:
> On Mon, Mar 22, 2010 at 10:41 PM, Krzysztof Dajka <alte...@gmail.com>
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.
I have AMD64 with ~3,6G ram (rest is assigned to built-in hd3300) and 3x500GB
in raidz1. As it's full zfs system, I'm booting from SD card. What should I
enable in kernel to produce good crashdump?
------------------------------
Message: 12
Date: Tue, 23 Mar 2010 10:12:43 +0100
From: "alte...@gmail.com" <alte...@gmail.com>
Subject: Re: Can't boot after make installworld
To: Dan Naumov <dan.n...@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>
Message-ID: <201003231012....@gmail.com>
Content-Type: Text/Plain; charset="iso-8859-1"
On Monday, 22 of March 2010 22:55:17 Dan Naumov 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. 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
>
Thanks for clarifying. I will try turning swap ASAP.
------------------------------
End of freebsd-stable Digest, Vol 349, Issue 2
**********************************************