From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 03:03:22 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5D4351065677
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 03:03:22 +0000 (UTC)
(envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
by mx1.freebsd.org (Postfix) with ESMTP id 8DB808FC17
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 03:03:21 +0000 (UTC)
Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua
[212.40.38.100])
by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id FAA24310;
Sun, 21 Mar 2010 05:03:16 +0200 (EET) (envelope-from avg@icyb.net.ua)
Received: from localhost.topspin.kiev.ua ([127.0.0.1])
by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
id 1NtBRc-0009ut-Gf; Sun, 21 Mar 2010 05:03:16 +0200
Message-ID: <4BA58C73.90806@icyb.net.ua>
Date: Sun, 21 Mar 2010 05:03:15 +0200
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.23 (X11/20100211)
MIME-Version: 1.0
To: "Matthew D. Fuller" <fullermd@over-yonder.net>
References: <4B6F9A8D.4050907@langille.org> <201002081556.54782.doconnor@gsoft.com.au> <20100209053002.GA9449@over-yonder.net> <201002091637.52002.doconnor@gsoft.com.au>
<20100209103228.GB9449@over-yonder.net>
<4B715AC7.2090201@icyb.net.ua>
In-Reply-To: <4B715AC7.2090201@icyb.net.ua>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: hardware for home use large storage
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 03:03:22 -0000
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.
--
Andriy Gapon
From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 04:15:28 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D2A4B106564A
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 04:15:28 +0000 (UTC)
(envelope-from jhellenthal@gmail.com)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com
[209.85.160.182])
by mx1.freebsd.org (Postfix) with ESMTP id 837968FC12
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 04:15:28 +0000 (UTC)
Received: by gyg13 with SMTP id 13so514334gyg.13
for <freebsd-stable@freebsd.org>; Sat, 20 Mar 2010 21:15:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:date:from:to:cc
:subject:in-reply-to:message-id:references:user-agent
:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version
:content-type; bh=9i4sA6GiLK5vq8bMEeREJiK7PhWq5jv0aJK8vru0FEI=;
b=B1brqYf7WICCuUaJQlOsmHVXj7E53sN01NS9aLbFgSDAgHd74ONXCUHWpN5tHANU4R
ZKTRHVuyD9MGVKYsEKmme2X6R/jaRYSX4UCIx9Q9DVWZuOA2YmIA+K4XU/Nbd/LxKlHr
6pmX7048la8kysVFGTPesNsLV8W+NGdeWydsk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:date:from:to:cc:subject:in-reply-to:message-id:references
:user-agent:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version
:content-type;
b=bKg2BzcV+JF+SttMyon2on7KoN2v1NKJUrQLjmNYJFYh2z2NMZmCqNNejHuz69CWJq
pfVmmQlPax++/5ceGHmMuqgOxaLj9+lcAPfJipTstNC3Js1o56QeKANXMzegvJPhseat
Fs/AK6UuwRqVPHmiet7s1Jd+J4KKGRIR/otp4=
Received: by 10.90.45.3 with SMTP id s3mr2646036ags.106.1269144927774;
Sat, 20 Mar 2010 21:15:27 -0700 (PDT)
Received: from centel.dataix.local (ppp-23.100.dialinfree.com [209.172.23.100])
by mx.google.com with ESMTPS id 20sm1172815iwn.1.2010.03.20.21.15.22
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sat, 20 Mar 2010 21:15:26 -0700 (PDT)
Sender: "J. Hellenthal" <jhellenthal@gmail.com>
Date: Sun, 21 Mar 2010 00:15:48 -0400
From: jhell <jhell@DataIX.net>
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
In-Reply-To: <20100320001820.GA92920@icarus.home.lan>
Message-ID: <alpine.BSF.2.00.1003210009480.3725@pragry.qngnvk.ybpny>
References: <4BA08FA8.5000902@omnilan.de>
<585602e11003170127t669ebe04k752bc4383f3fde22@mail.gmail.com>
<4BA3FF91.7090903@digiware.nl>
<alpine.OSX.2.00.1003191948260.3110@charles-sprickmans-imac.local>
<20100320001820.GA92920@icarus.home.lan>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
X-OpenPGP-Key-Id: 0x89D8547E
X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-stable@freebsd.org
Subject: Re: Does zfs have it's own nfs server?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 04:15:28 -0000
On Fri, 19 Mar 2010 20:18, Jeremy Chadwick wrote:
In Message-Id: <20100320001820.GA92920@icarus.home.lan>
> On Fri, Mar 19, 2010 at 07:50:24PM -0400, Charles Sprickman wrote:
>> On Fri, 19 Mar 2010, Willem Jan Withagen wrote:
>>
>>> On 17-3-2010 9:27, Matthias Gamsjager wrote:
>>>> sharenfs does work in freebsd but iscsi does not. I'm not sure about smb.
>>>>
>>>> about nfs: you should take a look at /etc/zfs/exports
>>>>
>>>>
>>>>
>>>> On Wed, Mar 17, 2010 at 9:15 AM, Harald Schmalzbauer
>>>> <h.schmalzbauer@omnilan.de> wrote:
>>>>> Hello,
>>>>>
>>>>> I observed some very strange filesystem security problems.
>>>>> Now I found that if I set sharenfs=yes data/pub I can mount_nfs but it
>>>>> does't respect any settings in /etc/exports. Also I get very strange uid
>>>>> numbers when writing.
>>>>> If I turn sharenfs off, limitations in /etc/exports work as expected.
>>>>> I thought sharenfs and sharesmb are only working on
>>>>> OpenSolaris. What about
>>>>> shareiscsi?
>>>
>>> I do not use /etc/exports for zfs shares....
>>> But instead of yes as value, you can use the NFS-options as string
>>> and that gets it into /etc/zfs/exports.
>>
>> 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.
>
> ZFS on FreeBSD's "sharenfs" option does nothing more than manage data in
> a flat file (/etc/zfs/exports) and automatically send a SIGHUP to
> mountd's pid (based on reading the contents of the file
> _PATH_MOUNTDPID). If you grep through /usr/src/cddl you can see what
> I'm referring to.
>
> "So how does mountd know about /etc/zfs/exports?"
>
> $ ps -auxw | grep mount
> root 861 0.0 0.0 6836 1716 ?? Is 10Mar10 0:00.00 /usr/sbin/mountd -r -l /etc/exports /etc/zfs/exports
>
> This is defined/referenced in /etc/rc.d/mountd.
>
> All that said:
>
> I avoid use of the "sharenfs" option in ZFS on RELENG_7 and RELENG_8, as
> I found certain quirks/behavioural oddities (such as mountd not picking
> up changes, or claims of not exporting something which visually
> confirmed should have been exported -- and in one case, mounting of a
> ZFS-exported NFS filesystem worked but then any I/O would block on the
> client indefinitely. Don't ask me how/why that happened). Possibly
> these were bugs that existed during ZFS's transitional phase between 7.x
> and 8.x, but the unreliable nature of the situation left a bad taste in
> my mouth. The workaround:
>
> Using /etc/exports to reference the local ZFS filesystems I want
> exported, HUP mountd, done. Above oddities/quirks no longer happened.
> And there's an added bonus: all your exports are therefore kept in one
> single place: a text file that's existed since what, 1989 or so?
>
> Of course, the advantage is that with ZFS properties you can inherit
> options -- that might be useful to some, but not to me.
>
> There's also known quirks/issues with the parsing logic with "sharenfs".
> This was discussed in December 2009.
>
>> 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?
>
> zfs create pool/fs
> zfs set sharenfs="-maproot=blah -network x.x.x.x -mask y.y.y.y" pool/fs
>
> Right now I'm more or less "avoiding" NFS as much as possible, as the
> number of severe/major bug reports on RELENG_8 keep coming in, and that
> scares me greatly.
>
>
There is also this:
http://www.freebsd.org/cgi/query-pr.cgi?pr=144447
Which I filed a while back that shows a bug in at least stable/7 that does
not unshare/remove shared filesystems from /etc/zfs/exports.
PJD has taken this PR and asked for a followup if this can be confirmed on
a 8.X system as he believes it is fixed there.
If someone of this thread is running a 8.X system would you please
followup to this PR with YES/NO it exists or not, and it would be greatly
appreciated.
I believe this also has a part of sending HUP to mountd but I could not
test that either on stable/7 or stable/8.
--
jhell
From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 04:39:00 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D9363106564A
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 04:39:00 +0000 (UTC)
(envelope-from jhellenthal@gmail.com)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com
[209.85.160.182])
by mx1.freebsd.org (Postfix) with ESMTP id 895528FC0C
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 04:39:00 +0000 (UTC)
Received: by gyg13 with SMTP id 13so519253gyg.13
for <freebsd-stable@freebsd.org>; Sat, 20 Mar 2010 21:39:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:date:from:to:cc
:subject:in-reply-to:message-id:references:user-agent
:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version
:content-type; bh=eMzQrVMYRQk9SXd82NnbdO+U1Aq1jn59ePL4C01tFmY=;
b=rN2maHasqfZG4nJT0X9daahcPwMdxjsNPLbtPsX2TjWNmR45e0NsQHImEmIvEeuZa/
/BuuaMOwFKSmqovn2W1pF3RYUDBik6jmUuzNfdXX+/Rzu5BkZR7at2XDPWkPkL8DP3J8
0hYyron+QQTAybj0l4jJYQDRZ71Ggl/7Agv74=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:date:from:to:cc:subject:in-reply-to:message-id:references
:user-agent:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version
:content-type;
b=CJPVPkYO3naMK+9BRAHP2WUT5VVSSF5MJ4eANePsiLAgFLZmD5i5qS0OYtw7ZotQFe
abFVxb2I5quOaBzhmWFZnx3RwEl1RhwJqAstS8PI8/xRUAdabf0hCCGjO8W+E2gzYOge
uNZJwHytQfjKCxrSM4cNMXBtpwOVe/zN440zw=
Received: by 10.150.173.8 with SMTP id v8mr5900522ybe.338.1269146339719;
Sat, 20 Mar 2010 21:38:59 -0700 (PDT)
Received: from centel.dataix.local (ppp-23.100.dialinfree.com [209.172.23.100])
by mx.google.com with ESMTPS id 20sm1194793iwn.13.2010.03.20.21.38.50
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sat, 20 Mar 2010 21:38:58 -0700 (PDT)
Sender: "J. Hellenthal" <jhellenthal@gmail.com>
Date: Sun, 21 Mar 2010 00:39:01 -0400
From: jhell <jhell@DataIX.net>
To: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de>
In-Reply-To: <4BA294F7.4030209@mail.zedat.fu-berlin.de>
Message-ID: <alpine.BSF.2.00.1003210033050.3725@pragry.qngnvk.ybpny>
References: <4B9E2DFD.2000701@zedat.fu-berlin.de>
<06D5F9F6F655AD4C92E28B662F7F853E037DDA15@seaxch09.desktop.isilon.com>
<4B9EBCE5.7080303@mail.zedat.fu-berlin.de>
<4BA294F7.4030209@mail.zedat.fu-berlin.de>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
X-OpenPGP-Key-Id: 0x89D8547E
X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-stable@freebsd.org, Matthew Fleming <matthew.fleming@isilon.com>
Subject: Re: Fatal trap 12: page fault while in kernel mode/current process:
12 (swi2: cambio)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 04:39:01 -0000
On Thu, 18 Mar 2010 17:02, O. Hartmann wrote:
In Message-Id: <4BA294F7.4030209@mail.zedat.fu-berlin.de>
> On 03/16/10 00:04, O. Hartmann wrote:
>> On 03/15/10 18:30, Matthew Fleming wrote:
>>>> Since the last update and make world on Friday, 12th March I get a
>>> crash
>>>> on one of my FreeBSD SMP boxes (it is always the same core message),
>>>> saying something about
>>>>
>>>> Fatal trap 12: page fault while in kernel mode [...] current process:
>>> 12
>>>> (swi2: cambio)
>>>
>>> Can you show the stack traceback from the kernel core?
>>>
>>> We had a problem a while ago at Isilon that I can't tell if it's
>>> related. In our case, the camisr() routine was called after panic(9)
>>> started and before the halt of other processors. This did Bad
>>> Things(TM) since the mtx_lock is a no-op after panicstr is set.
>>>
>>> We solved it locally by wrapping camisr() in a local cambio_swi()
>>> routine that only called camisr(NULL) when panicstr == NULL.
>>>
>>> Thanks,
>>> matthew
>>
>> Hello.
>>
>> I will do as soon as possible. The box is in production at the moment
>> and I've less time to put everything into debugging to provide more
>> details.
>>
>> Just in case: does the kernel automatically save the screen with the
>> dump information? If not, I have no other terminal facility to get a
>> dump via the classical way.
>>
>> Regards,
>> Oliver
>
> Since yesterday, this problem went away! This is mystical. After deactivating
> radeon.ko and the virtual box stuff I tried again with a new build of world
> and - voila! - everything worked again. This is strange ...
>
> Oliver
>
If possible set a dump device and use the following in your rc.conf:
crashinfo_enable="YES"
dumpdev="ADD-DEVICE-HERE"
After the crash happens look for core.txt.N files in /var/crash.
You will probably want to look over the crash info and scrub it of
vital information to comply with your companies policies. It is very
verbose.
DDB as I have heard can be configured AFAIR to textdump but I have no
knowledge of that.
Good Luck,
--
jhell
From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 15:31:29 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1AAB31065676
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 15:31:29 +0000 (UTC)
(envelope-from to.my.trociny@gmail.com)
Received: from mail-ew0-f227.google.com (mail-ew0-f227.google.com
[209.85.219.227])
by mx1.freebsd.org (Postfix) with ESMTP id 988578FC13
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 15:31:28 +0000 (UTC)
Received: by ewy27 with SMTP id 27so283604ewy.13
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 08:31:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:to:cc:subject:references
:organization:from:date:in-reply-to:message-id:user-agent
:mime-version:content-type;
bh=wsUQklLfafOxuK8Re6AMmr3FF6DeWoUOKaDO03tLII0=;
b=a9Gs1gasJLzgWgW8aKK7Spj2npoU3KC+rpOqqPUJmhrufY5XFLSYbG9C1lYR/6to0j
VVEwB6/XxtjGd+MjTalkSdviifzHGKd92MVDNKqp+X4cYEeugKj1O4ZfXs22TrQ2svvI
mpkOKDvLm8v2fXS1KnGV7Mwus5cTC1AmrG/3E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=to:cc:subject:references:organization:from:date:in-reply-to
:message-id:user-agent:mime-version:content-type;
b=nbgXu/Ko5ZscsLKOMAOgF1TJacY/mPJoIjIvM3Wt9aDziRrklJJF+OASbcV+Qg3jSN
POE7dGrNhmAy5jlAPsRT892Q+tur9v9RIlKTtQZy8dU5yUYykqHwfNmoxCDoyCFn8Ujl
yS5ZH20RmUeyjhmBnn7HPrFQemU42eUTELURM=
Received: by 10.213.2.79 with SMTP id 15mr2674883ebi.96.1269185487207;
Sun, 21 Mar 2010 08:31:27 -0700 (PDT)
Received: from localhost ([95.69.160.238])
by mx.google.com with ESMTPS id 16sm1203275ewy.3.2010.03.21.08.31.24
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sun, 21 Mar 2010 08:31:25 -0700 (PDT)
To: jhell <jhell@DataIX.net>
References: <4B9E2DFD.2000701@zedat.fu-berlin.de>
<06D5F9F6F655AD4C92E28B662F7F853E037DDA15@seaxch09.desktop.isilon.com>
<4B9EBCE5.7080303@mail.zedat.fu-berlin.de>
<4BA294F7.4030209@mail.zedat.fu-berlin.de>
<alpine.BSF.2.00.1003210033050.3725@pragry.qngnvk.ybpny>
Organization: TOA Ukraine
From: Mikolaj Golub <to.my.trociny@gmail.com>
Date: Sun, 21 Mar 2010 17:31:23 +0200
In-Reply-To: <alpine.BSF.2.00.1003210033050.3725@pragry.qngnvk.ybpny>
(jhell@dataix.net's message of "Sun\,
21 Mar 2010 00\:39\:01 -0400")
Message-ID: <86hbo9elo4.fsf@kopusha.onet>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de>,
freebsd-stable@freebsd.org, Matthew Fleming <matthew.fleming@isilon.com>
Subject: Re: Fatal trap 12: page fault while in kernel mode/current process:
12 (swi2: cambio)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 15:31:29 -0000
On Sun, 21 Mar 2010 00:39:01 -0400 jhell wrote:
> DDB as I have heard can be configured AFAIR to textdump but I have no
> knowledge of that.
ddb_enable="YES" in /etc/rc.conf would be enough. But I also remove "textdump
set" in kdb.enter.panic script (/etc/ddb.conf) as I prefer normal dumps (with
output of ddb scripts in capture buffer) to textdumps. You can't debug
textdump and crashinfo will fail too. And all info provided in textdump is
retrieved from vmcore capture buffer by crashifo utility automatically.
--
Mikolaj Golub
From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 19:15:31 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8932A106566B
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 19:15:31 +0000 (UTC)
(envelope-from alteriks@gmail.com)
Received: from mail-fx0-f209.google.com (mail-fx0-f209.google.com
[209.85.220.209])
by mx1.freebsd.org (Postfix) with ESMTP id 20BBF8FC0C
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 19:15:30 +0000 (UTC)
Received: by fxm1 with SMTP id 1so4713884fxm.33
for <freebsd-stable@freebsd.org>; Sun, 21 Mar 2010 12:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:date:message-id:subject
:from:to:content-type;
bh=2No85wpr3EjT2K377zyMgGDyzjBwU+aCn2+x7aGqJ2U=;
b=QBKsnfN+AZTPakN9UhiXZTKVbNGt7V0u6qIqhmUobKI09KFTaz6XI2heQOTHiQYT8x
Tp+WY9x6zUSkEQznURSq3beFt6oK4LiflJAckZb7hQQGDEcryrZRBoE6Sp5hptGDaykL
IoavVyidhteMlTpPxg/4Rnh/GSOUqXqDztMuk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:date:message-id:subject:from:to:content-type;
b=Ckfz/zdjJdRRyRpP8RKpYoyuarJOTuvwLTgGtGB+wkfMjYD7f5WwSO1beefykMpdId
oUCI2OYXnJVomY91VcqjFJvJaufDscCZmMFa0h8DHOGTbPhO4cGaRIxYErHuRYXC/fkp
0duOy6lQznPWxkXmswtr1QZFQ0USnHLqGp6MQ=
MIME-Version: 1.0
Received: by 10.102.237.35 with SMTP id k35mr11087853muh.72.1269198929915;
Sun, 21 Mar 2010 12:15:29 -0700 (PDT)
Date: Sun, 21 Mar 2010 19:15:29 +0000
Message-ID: <684e57ec1003211215n1e729b0cka61aabe64e1ddca8@mail.gmail.com>
From: Krzysztof Dajka <alteriks@gmail.com>
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 19:15:31 -0000
Hi, I'm having problem with upgrading my FreeBSD to RELENG_8. Building
world and kernel went smoothly I can boot with new kernel, but after 'make
installworld' I could boot my system. My system prints only:
BTX loader 1.00 BTX version is 1.01
Console: internal video/keyboard
BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS drive E: is disk2
BIOS drive F: is disk3
|
And freezes...
Here is my configuration:
[~] # cat /etc/src.conf
LOADER_ZFS_SUPPORT=YES
[~] # cat /etc/make.conf
WITH_KDE_PHONON=YES
# added by use.perl 2010-03-10 21:03:54
PERL_VERSION=5.10.1
WITHOUT_NOUVEAU=YES
What have I done:
rm -rf /usr/obj
make buildworld
make buildkernel
make installkernel
nextboot -o '-s' -k kernel
shutdown -r now
Reboot went fine:
[~] # uname -a
FreeBSD altstation 8.0-STABLE FreeBSD 8.0-STABLE #0: Sun Mar 21 09:57:11 UTC
2010 toor@altstation:/usr/obj/usr/src/sys/GENERIC amd64
zfs mount -a
zfs set readonly=off zroot
adjkerntz -i
mergemaster -p
cd /usr/src
make installworld
mergemaster
shutdown -r now
Unfortunately my system hangs while booting and I had to rollback to
snapshot before 'make installworld' Actually I'm using new kernel build
today and 'world' from install dvd. It's my first FreeBSD upgrade, am I
missing something?
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 02:06:39 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 36D59106566C;
Mon, 22 Mar 2010 02:06:39 +0000 (UTC)
(envelope-from danger@FreeBSD.org)
Received: from services.rulez.sk (services.rulez.sk [92.240.234.125])
by mx1.freebsd.org (Postfix) with ESMTP id DD32B8FC12;
Mon, 22 Mar 2010 02:06:38 +0000 (UTC)
Received: from services.rulez.sk (services.rulez.sk [92.240.234.125])
by services.rulez.sk (Postfix) with ESMTP id 4F131133474B;
Mon, 22 Mar 2010 03:06:37 +0100 (CET)
X-Virus-Scanned: amavisd-new at rulez.sk
Received: from services.rulez.sk ([92.240.234.125])
by services.rulez.sk (services.rulez.sk [92.240.234.125]) (amavisd-new,
port 10024)
with ESMTP id TdvBe5qPEFWy; Mon, 22 Mar 2010 03:06:31 +0100 (CET)
Received: from danger-mbp.local (danger.mcrn.sk [84.16.37.254])
(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: danger@rulez.sk)
by services.rulez.sk (Postfix) with ESMTPSA id C75A51334715;
Mon, 22 Mar 2010 03:06:31 +0100 (CET)
Message-ID: <4BA6D0A7.7010107@FreeBSD.org>
Date: Mon, 22 Mar 2010 03:06:31 +0100
From: Daniel Gerzo <danger@FreeBSD.org>
Organization: The FreeBSD Project
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv:1.9.2.2pre) Gecko/20100311 Lanikai/3.1b2pre
MIME-Version: 1.0
To: current@freebsd.org, stable@freebsd.org, hackers@freebsd.org,
questions@freebsd.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc:
Subject: HEADSUP: Call for FreeBSD Status Reports - 1Q/2010
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 02:06:39 -0000
Dear all,
I would like to remind you that the next round of status reports
covering the first quarter of 2010 is due on April 15th, 2010. This
initiative is very welcome in our community. Therefore, I would like to
ask you to submit your status reports as soon as possible, so that we
can compile the report on time.
There is a lot of projects which are currently being worked on, so do
not hesitate and write us a few lines - a short description about what
you are working on, what are your plans and goals, so we can inform our
community about your great work! Check out the reports from past to get
some inspiration of what your submission should look like.
If you know about a project that should be included in the status
report, please let us know as well, so we can poke the responsible
people to provide us with something useful. Updates to submissions from
the last report are welcome too.
Note that the submissions are accepted from anyone involved with the
FreeBSD community, you do not have to be a FreeBSD committer.
Submissions about anything related to FreeBSD are very welcome!
Please email us the filled-in XML template to be found at
http://www.freebsd.org/news/status/report-sample.xml to
monthly@FreeBSD.org, or alternatively use our web based form located at
http://www.freebsd.org/cgi/monthly.cgi.
For more information, please visit http://www.freebsd.org/news/status/.
We are looking forward to see your submissions!
--
S pozdravom / Best regards
Daniel Gerzo, FreeBSD committer
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 10:48:30 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E8D631065676
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 10:48:29 +0000 (UTC)
(envelope-from antinix@gmail.com)
Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com
[74.125.82.182])
by mx1.freebsd.org (Postfix) with ESMTP id 7D2C78FC17
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 10:48:29 +0000 (UTC)
Received: by wyb33 with SMTP id 33so2492017wyb.13
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 03:48:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:sender:received:in-reply-to
:references:from:date:x-google-sender-auth:message-id:subject:cc
:content-type:content-transfer-encoding;
bh=hxRDrAmwnQtCbEx43qontcuu2pzSZTaF3CKSk02YsYE=;
b=yIOKHqQ4RceRL3J0t4R/9FJdmObstsbgvnAtp0vYKnZSDiBu1/OEY/Xbtol7hmzW2X
XR4wyITiKjI9jJaO3iavU2JFwLHo11rSYNFGONzHqp9av/HNpECAdZL6gonTcZYV5A7U
A36m9PkDUgkAnWYKrEkCnLwM8gEq5oXB0IPQQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:from:date
:x-google-sender-auth:message-id:subject:cc:content-type
:content-transfer-encoding;
b=SsgzCYXWJLvYCgbYbSifefxb6mhd17n8mXKf7dfkP4YSSQ6G76WDRHEDNRqUpNhy4W
/23P/539iNcGeO9QJFPqGTvvtZm528WmqDEU0pAc/h5hmRR5PEsN/vPd82/seswLFduh
eIh/d7xDyYkMSk0Qw3XURDiZYWil3JmxduCrI=
MIME-Version: 1.0
Sender: antinix@gmail.com
Received: by 10.216.178.148 with SMTP id f20mr643464wem.43.1269253193041; Mon,
22 Mar 2010 03:19:53 -0700 (PDT)
In-Reply-To: <4BA58C73.90806@icyb.net.ua>
References: <4B6F9A8D.4050907@langille.org>
<201002081556.54782.doconnor@gsoft.com.au>
<20100209053002.GA9449@over-yonder.net>
<201002091637.52002.doconnor@gsoft.com.au>
<20100209103228.GB9449@over-yonder.net> <4B715AC7.2090201@icyb.net.ua>
<4BA58C73.90806@icyb.net.ua>
From: Andrei Kolu <antik@bsd.ee>
Date: Mon, 22 Mar 2010 12:19:32 +0200
X-Google-Sender-Auth: 677fd9aeaef26d93
Message-ID: <10263ac1003220319s52c6450ay96fb0c8ea05a0ae1@mail.gmail.com>
Cc: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: hardware for home use large storage
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 10:48:30 -0000
2010/3/21 Andriy Gapon <avg@icyb.net.ua>:
> 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. =A0One 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. =A0So 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 =A0 :(
>>
>> Yep.
>> For sure, Gigabyte BIOS on this board is completely missing ECC initiali=
zation
>> code. =A0I mean not only the menus in setup, but the code that does memo=
ry
>> 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 no=
t
> 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
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 11:13:08 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8362C1065675
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 11:13:08 +0000 (UTC)
(envelope-from dan.naumov@gmail.com)
Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com
[209.85.218.216])
by mx1.freebsd.org (Postfix) with ESMTP id 17D2A8FC16
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 11:13:07 +0000 (UTC)
Received: by bwz8 with SMTP id 8so16991bwz.3
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 04:13:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:date:message-id:subject
:from:to:content-type;
bh=6OqUxqWwxWMbKlY2b09etAPxKBwn29NGrb7fTt74YAI=;
b=vIDs5qVRe6/VD9zpYxYz1Ja5vLIZsgH8QoqnStxx4FTQxfy8C657PPUzk2XhEZrVBb
8EreQSo2WKFrwF7XlgAJ96XI1yHxizi2kHnhq/Tvb25QzOQUovJalm6gM+vmGuqpJ+OU
MztY+soKAne4Ic9VcMbkkn+wBRSutUU0svKmQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:date:message-id:subject:from:to:content-type;
b=fBqLgLqNKy9/DcM+lGCWDXimVlHVrvOwsMZ2+sSjHGxw3TAOhkbxIY6kR16CMsufok
kWUhGBCPv61sf06l+MzndBk5+9Tfqo+rvKn36j41iuxNSlaPhRtG1rRt4vdNGt1SiAgW
Tgqf5yFy7Io2WRZ8T3774A5OwrYPFUUWwBA5Y=
MIME-Version: 1.0
Received: by 10.204.24.134 with SMTP id v6mr7793949bkb.204.1269256383784; Mon,
22 Mar 2010 04:13:03 -0700 (PDT)
Date: Mon, 22 Mar 2010 13:13:03 +0200
Message-ID: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
From: Dan Naumov <dan.naumov@gmail.com>
To: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>,
alteriks@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Cc:
Subject: RE: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 11:13:08 -0000
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
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 14:01:46 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 983681065670
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 14:01:46 +0000 (UTC)
(envelope-from jhellenthal@gmail.com)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com
[209.85.212.54])
by mx1.freebsd.org (Postfix) with ESMTP id 412E08FC13
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 14:01:45 +0000 (UTC)
Received: by vws1 with SMTP id 1so382216vws.13
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 07:01:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:date:from:to:cc
:subject:in-reply-to:message-id:references:user-agent
:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version
:content-type; bh=HE3iwj8p3w/cRulJdb5dVUP6Mrv85z8/1gPDUqH1Mtk=;
b=EfvyH3TLpfI6l4iO2u5WEslKSeISEJptgcXjricSsp6cUrpX7/RpAg4vWyAUt2uhtc
/N0pUUOgaIcs+dZqprgEwPZ9fScC8rcGYbs6siS+Tdn47TlGu8k/GgVpjnUedB9qljXs
0Jkb854+vNUq+TJ81RBd/UGNDxeiNpRm7BmUo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:date:from:to:cc:subject:in-reply-to:message-id:references
:user-agent:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version
:content-type;
b=tMFKK5aG3Y4AME82WpiLkvNzUH8NT45nELbcEWlRDdGxIs4fo22wJHwwM74joABgSb
zl676mRWUZdY3XwxnjVQRM6HGH+87jnsdnVyTFyxOSFoKpbKx5GP0eOPfQrZfUN9o9hG
pFC6MDclVFRjaA1UK2WRNusqmvUcWvZHmzQJ0=
Received: by 10.220.126.166 with SMTP id c38mr1310558vcs.49.1269266486517;
Mon, 22 Mar 2010 07:01:26 -0700 (PDT)
Received: from centel.dataix.local (ppp-21.63.dialinfree.com [209.172.21.63])
by mx.google.com with ESMTPS id 25sm35579381vws.4.2010.03.22.07.01.23
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Mon, 22 Mar 2010 07:01:25 -0700 (PDT)
Sender: "J. Hellenthal" <jhellenthal@gmail.com>
Date: Mon, 22 Mar 2010 10:01:39 -0400
From: jhell <jhell@DataIX.net>
To: Dan Naumov <dan.naumov@gmail.com>
In-Reply-To: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.1003220950100.63287@pragry.qngnvk.ybpny>
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
X-OpenPGP-Key-Id: 0x89D8547E
X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>,
alteriks@gmail.com
Subject: RE: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 14:01:46 -0000
On Mon, 22 Mar 2010 07:13, Dan Naumov wrote:
In Message-Id: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@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
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 15:47:44 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 50A9D106566B
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 15:47:44 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com
[209.85.220.224])
by mx1.freebsd.org (Postfix) with ESMTP id CF4AF8FC16
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 15:47:43 +0000 (UTC)
Received: by fxm24 with SMTP id 24so1785245fxm.3
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 08:47:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:references:message-id:from:to
:in-reply-to:content-type:content-transfer-encoding:x-mailer
:mime-version:subject:date:cc;
bh=+Zz1Kig6LNZ/t2XeQgx3UR13a3cc8aTBz/CgoUI1/aI=;
b=rW4FtiEUeGfTc9he2xbTqHXtwjEpruS78kOJLCUAIO5sYs3nEVmJ6udzvXWORCehzR
2Mkksy98VeAYQCYJ6D2z1dWN9BKtrg4pVDEr4pAaxprSukCgLup2EYKK6rFJfXV8slS0
tQX9sij3LU3xeqADRrP4VwKhP6/rE5aF9Wf4w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=references:message-id:from:to:in-reply-to:content-type
:content-transfer-encoding:x-mailer:mime-version:subject:date:cc;
b=wg6N9GPKqjWB7csHKWldDyZgdbIvFWbobjfjlB0b0iD6bBhDPNoBRquxTt67XFwqo5
qxYb9+JeDKzU6WpfsKYPljIRwqQCV6PmTSlh+ECaAxmKCXf46MXUkaPnrxoj96vJgcEp
AjzEyvDc7Cv+XqmoZ587XhdLsqZv3xxOGh37w=
Received: by 10.223.77.85 with SMTP id f21mr2523985fak.40.1269272861197;
Mon, 22 Mar 2010 08:47:41 -0700 (PDT)
Received: from [192.168.0.27] (deviant.freebsdgirl.com [173.8.183.73])
by mx.google.com with ESMTPS id z10sm8868663fka.1.2010.03.22.08.47.37
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Mon, 22 Mar 2010 08:47:38 -0700 (PDT)
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
<alpine.BSF.2.00.1003220950100.63287@pragry.qngnvk.ybpny>
Message-Id: <00E5A20A-4AB5-4769-A85C-B061D35B1BAA@gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: jhell <jhell@DataIX.net>
In-Reply-To: <alpine.BSF.2.00.1003220950100.63287@pragry.qngnvk.ybpny>
Content-Type: text/plain;
charset=us-ascii;
format=flowed;
delsp=yes
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (7E18)
Mime-Version: 1.0 (iPhone Mail 7E18)
Date: Mon, 22 Mar 2010 08:47:31 -0700
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>,
Dan Naumov <dan.naumov@gmail.com>,
"alteriks@gmail.com" <alteriks@gmail.com>
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 15:47:44 -0000
On Mar 22, 2010, at 7:01 AM, jhell <jhell@DataIX.net> wrote:
>
> On Mon, 22 Mar 2010 07:13, Dan Naumov wrote:
> In Message-Id: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@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
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 20:41:37 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 840BB106566C
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 20:41:37 +0000 (UTC)
(envelope-from alteriks@gmail.com)
Received: from mail-ew0-f223.google.com (mail-ew0-f223.google.com
[209.85.219.223])
by mx1.freebsd.org (Postfix) with ESMTP id 181458FC19
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 20:41:36 +0000 (UTC)
Received: by ewy23 with SMTP id 23so891830ewy.34
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 13:41:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=jHg9urWjCnlEqOFzbpCWYVMwtDXFSGkXReSj2cEW/t4=;
b=gpDYwh/zE2rnmK43PK8qjHep9qBsDb4ytgWQCLj3LhZbIzuYgfW2Y/wbW7vc1ml1wf
cthutwa275CqtJdpXPKzt/b0tIa5NtCfGwVKm6xnMUZkih31E/p5RR7FYsmhPOBeSLQH
S/L7erFyblAetf/XCJr50uEDfhgwiyoMi0Tgw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=fTcM64dfg+3K+r3a8FmqHW+JYDYSvKCQObslCfd9DyJgD5sovhmL+MT3s9+MvTO73y
p49N+gTTJTajwblLXhqESAcsWuNMRnDo/3pGxOg+9gYJ4np8BZf1HyDiSGptlhFgdBq+
uT9bxCuaTICIqzxkuzhT58ugH7Ou7Z4hOmgK8=
MIME-Version: 1.0
Received: by 10.102.216.24 with SMTP id o24mr12876874mug.67.1269290495675;
Mon, 22 Mar 2010 13:41:35 -0700 (PDT)
In-Reply-To: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
Date: Mon, 22 Mar 2010 20:41:35 +0000
Message-ID: <684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
From: Krzysztof Dajka <alteriks@gmail.com>
To: Dan Naumov <dan.naumov@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 20:41:37 -0000
On 3/22/10, Dan Naumov <dan.naumov@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
=C2=BFzfs? 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=3D.
8.0-STABLE -> tag=3DRELENG_8
8.0-RELEASE-p2 -> tag=3DRELENG_8_0 ? (btw what does p2 mean?)
If someone patient could explain it to me I'd be grateful.
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 21:55:18 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D13B81065673
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 21:55:18 +0000 (UTC)
(envelope-from dan.naumov@gmail.com)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157])
by mx1.freebsd.org (Postfix) with ESMTP id 631728FC26
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 21:55:18 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id d23so640773fga.13
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 14:55:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=P70DNmkyoJ2MWZ56QeL8jXo46BXWTgZA0u5iTkqSR+Y=;
b=HikipFNh8Vu+VLaxZdqIgpXUM7Byi6VXhPBPWgP4xvlYby8O6GzLnDCihI63JuU6ZQ
q4nirfXnPVrrQoRaAmDGLKkfuD9jFCNNg37LmAsWuDZVw6qidd+TSYaVEfK5w1Rx1qSx
Qr4G8OUsDdZZJMyAqTgP/5Wli+q97PrtZ9Mcg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=xhNuxlejrcjWpDAKWcZephetE6Ax36IWhmN/Jho7BAx1yVtG+9ErH09qB4545twxlM
II90srwgv53TkX8sFHR8AddBx4fCmMhc9kfNXde2WMHypssGVy20q+bZ5Asn+DRLwTyC
dPD/yIT42eLMdKzUoW839rPvP0BpN+vhfTWno=
MIME-Version: 1.0
Received: by 10.204.7.194 with SMTP id e2mr4290124bke.103.1269294917066; Mon,
22 Mar 2010 14:55:17 -0700 (PDT)
In-Reply-To: <684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
<684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
Date: Mon, 22 Mar 2010 23:55:17 +0200
Message-ID: <cf9b1ee01003221455i7fc5d66fi42315cefd3ed6033@mail.gmail.com>
From: Dan Naumov <dan.naumov@gmail.com>
To: Krzysztof Dajka <alteriks@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 21:55:19 -0000
> 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
> =BFzfs? 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=3D.
> 8.0-STABLE -> tag=3DRELENG_8
> 8.0-RELEASE-p2 -> tag=3DRELENG_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 b=
e
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
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 22:00:19 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5E2FD1065677
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 22:00:19 +0000 (UTC)
(envelope-from dan.naumov@gmail.com)
Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com
[209.85.220.224])
by mx1.freebsd.org (Postfix) with ESMTP id AE3198FC16
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 22:00:18 +0000 (UTC)
Received: by fxm24 with SMTP id 24so276458fxm.3
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 15:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=pvhEnU0w2wbnlVkIZLRqgOfW/sJZtk01q8Eeah4O7WI=;
b=aeoaqpdfMYvnMB1b6capfQK+dqLNl0bpqzADEvJV6JRrMhT437nIeWocgF4uMcOb23
mTVlQt5Ua412u8oOIqKeFNmFAlzBsapoQolLZtv5GfRrRtZjEOKYDqzh3plfq0dt6mnS
fFFmmBnAnjHyooui48OsInbP6aNTxPkJFkQes=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=Q2CO3DrWep+x6vfUnNE1YswUirnepnMMqcRx6rb5WTHyfdFYAp5PFys96xkIblRxQs
YYQJxt3idDBDTy9P5pEcBYlAJi/HeEYY5tnPDV6DCMeVjCghUjHuh2cRhPkUxjjNjKe7
I9zRA7lq9DS+Nc0qNLfk0bBD13W0xQ7YxHp6M=
MIME-Version: 1.0
Received: by 10.204.156.199 with SMTP id y7mr1958968bkw.108.1269295217212;
Mon, 22 Mar 2010 15:00:17 -0700 (PDT)
In-Reply-To: <684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
<684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
Date: Tue, 23 Mar 2010 00:00:17 +0200
Message-ID: <cf9b1ee01003221500j6c605590ka1d25722f35d58cc@mail.gmail.com>
From: Dan Naumov <dan.naumov@gmail.com>
To: Krzysztof Dajka <alteriks@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 22:00:19 -0000
On Mon, Mar 22, 2010 at 10:41 PM, Krzysztof Dajka <alteriks@gmail.com> wrot=
e:
> 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
> =BFzfs? 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
From owner-freebsd-stable@FreeBSD.ORG Mon Mar 22 23:17:34 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id BD65F106566C
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 23:17:34 +0000 (UTC)
(envelope-from fbsd2@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id 5318B8FC15
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 23:17:34 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2MMwUVU088357
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 15:58:33 -0700 (PDT)
(envelope-from fbsd2@sstec.com)
Message-Id: <5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
X-Sender:
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 22 Mar 2010 15:57:35 -0700
To: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
From: John Long <fbsd2@sstec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 23:17:34 -0000
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
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 02:56:17 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 452E21065708
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 02:56:17 +0000 (UTC)
(envelope-from matheusber@gmail.com)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25])
by mx1.freebsd.org (Postfix) with ESMTP id E7FFD8FC0C
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 02:56:16 +0000 (UTC)
Received: by qw-out-2122.google.com with SMTP id 5so1233369qwi.7
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 19:56:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:received:received
:message-id:in-reply-to:references:date:subject:from:to:user-agent
:mime-version:content-type:content-transfer-encoding:x-priority
:importance; bh=jR5ARqPqVX1FA0+wF1zAmH/8l5nfIZDM74KPID+tNQ4=;
b=MVSTMV6gIGbMkJf71PfqnBQMb14iQBHTSxWrft5q4ARWsCdDZlOy0XcZPHo64zYEzN
V4eX9qKIpfHUYck9tn0wYX0IVoGRE9N4nsAoK6jaZa8SjqxXCCjoFY9REGnv2lwMreAh
ZHX3c3HRlceYRYf9vzHn8bfrDndZnVZNLnhW4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:message-id:in-reply-to:references:date:subject:from:to
:user-agent:mime-version:content-type:content-transfer-encoding
:x-priority:importance;
b=bMZD5/uxTsNMb+izbwN/RCbdTy0ZSR/WsGW60HWHNLRrg2q9d83lWAZ3Qxj6Kj85Nc
It/+pdGNNq+BiqeZuhrT/LT4a51glaUP5N006qDfQ/79oY2ZwR57BHGbP/TD65OYfSyL
6DgbkKjbcku6W3OzSQu/vnn+dF+duyUAL7bFY=
Received: by 10.224.27.34 with SMTP id g34mr1538952qac.19.1269312976084;
Mon, 22 Mar 2010 19:56:16 -0700 (PDT)
Received: from cygnus.homeunix.com ([189.71.112.4])
by mx.google.com with ESMTPS id 7sm10098492qwf.14.2010.03.22.19.56.12
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Mon, 22 Mar 2010 19:56:13 -0700 (PDT)
Sender: Nenhum_de_Nos <matheusber@gmail.com>
Received: by cygnus.homeunix.com (Postfix, from userid 80)
id 6724AB8A1E; Mon, 22 Mar 2010 23:55:57 -0300 (BRT)
Received: from 10.1.1.100 (SquirrelMail authenticated user matheus)
by lamneth with HTTP; Mon, 22 Mar 2010 23:55:57 -0300 (BRT)
Message-ID: <a333ac6f65b2061fbc46994599f969ba.squirrel@lamneth>
In-Reply-To: <5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
References: <5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
Date: Mon, 22 Mar 2010 23:55:57 -0300 (BRT)
From: "Nenhum_de_Nos" <matheus@eternamente.info>
To: freebsd-stable@freebsd.org
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 02:56:17 -0000
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
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 04:42:06 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9D5CD106566C
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 04:42:06 +0000 (UTC)
(envelope-from spork@bway.net)
Received: from xena.bway.net (xena.bway.net [216.220.96.26])
by mx1.freebsd.org (Postfix) with ESMTP id 646688FC15
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 04:42:06 +0000 (UTC)
Received: (qmail 2829 invoked by uid 0); 23 Mar 2010 04:42:05 -0000
Received: from unknown (HELO ?10.3.2.40?) (spork@bway.net@96.57.144.66)
by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP;
23 Mar 2010 04:42:05 -0000
Date: Tue, 23 Mar 2010 00:42:03 -0400 (EDT)
From: Charles Sprickman <spork@bway.net>
X-X-Sender: spork@charles-sprickmans-imac.local
To: Willem Jan Withagen <wjw@digiware.nl>
In-Reply-To: <4BA4BC82.3020606@digiware.nl>
Message-ID: <alpine.OSX.2.00.1003230039170.3110@charles-sprickmans-imac.local>
References: <4BA08FA8.5000902@omnilan.de>
<585602e11003170127t669ebe04k752bc4383f3fde22@mail.gmail.com>
<4BA3FF91.7090903@digiware.nl>
<alpine.OSX.2.00.1003191948260.3110@charles-sprickmans-imac.local>
<4BA4BC82.3020606@digiware.nl>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Matthias Gamsjager <mgamsjager@gmail.com>,
FreeBSD Stable Users <freebsd-stable@freebsd.org>
Subject: Re: Does zfs have it's own nfs server?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 04:42:06 -0000
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
>
>
>
>
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 06:27:23 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0C7EF106566B
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 06:27:23 +0000 (UTC)
(envelope-from mavbsd@gmail.com)
Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com
[209.85.220.224])
by mx1.freebsd.org (Postfix) with ESMTP id 8BCC18FC1D
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 06:27:22 +0000 (UTC)
Received: by fxm24 with SMTP id 24so642147fxm.3
for <freebsd-stable@freebsd.org>; Mon, 22 Mar 2010 23:27:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:message-id:date:from
:user-agent:mime-version:to:cc:subject:references:in-reply-to
:content-type:content-transfer-encoding;
bh=59KnBjEAWNiOvD4x4tcRaAG1mSz0v4602GXYnL4qPvo=;
b=oPQniZiRlaLTeJaizjOV584yuXdDjChyr9sZ4iMUg18huWKWqB7JrJ39SdFCnMqI3O
QtW9yurRKlcsK5rQQdYRz3PenHgWPnS5G1CgZQyn7mMkcYOER+v3/XdQkZC3Nk84YJyX
Rxt2BC3n/eYxRstkJrxHYtzBe1hNZL61S/4VQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject
:references:in-reply-to:content-type:content-transfer-encoding;
b=kJb9hU4ApkL0ehhHRyIcfclkeocki0Gqij20gYT/CEh3UAzrxJgd217Xwt8PketqLo
UBxOFVWkxZ+0qXYvNq9n5ZO7SyKquEKEGKaOKYpEcw/rR7Y0oP5EIW+e6PDkWPR5+YWv
vUyjQMOILgCO9J6LPD0KlfkloRG/BKSfDFG2s=
Received: by 10.103.76.21 with SMTP id d21mr2152001mul.17.1269325641073;
Mon, 22 Mar 2010 23:27:21 -0700 (PDT)
Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226])
by mx.google.com with ESMTPS id n7sm3552437mue.15.2010.03.22.23.27.20
(version=SSLv3 cipher=RC4-MD5); Mon, 22 Mar 2010 23:27:20 -0700 (PDT)
Sender: Alexander Motin <mavbsd@gmail.com>
Message-ID: <4BA85F46.9010306@FreeBSD.org>
Date: Tue, 23 Mar 2010 08:27:18 +0200
From: Alexander Motin <mav@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.23 (X11/20091212)
MIME-Version: 1.0
To: John Long <fbsd2@sstec.com>
References: <1269310984.00232724.1269300005@10.7.7.3>
In-Reply-To: <1269310984.00232724.1269300005@10.7.7.3>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 06:27:23 -0000
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
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 07:41:09 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6F52C1065670
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 07:41:09 +0000 (UTC)
(envelope-from alexz@visp.ru)
Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2])
by mx1.freebsd.org (Postfix) with ESMTP id 2725F8FC12
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 07:41:07 +0000 (UTC)
Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin)
by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD))
(envelope-from <alexz@visp.ru>) id 1NtyjZ-000EBE-KK
for freebsd-stable@freebsd.org; Tue, 23 Mar 2010 10:41:05 +0300
From: "Alexander Zagrebin" <alexz@visp.ru>
To: <freebsd-stable@freebsd.org>
Date: Tue, 23 Mar 2010 10:41:06 +0300
Message-ID: <74426BABA82C4FD28FDF848FB65197FF@vosz.local>
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
Thread-Index: AcrKXDIlzjxECYGjS0mTJBZeKyknSg==
Subject: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS (doesn't link
with libzfsboot)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 07:41:09 -0000
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
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 09:28:13 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E821B106564A
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 09:28:13 +0000 (UTC)
(envelope-from alteriks@gmail.com)
Received: from mail.agora.pl (mail.agora.pl [193.42.230.55])
by mx1.freebsd.org (Postfix) with ESMTP id 70E708FC0C
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 09:28:13 +0000 (UTC)
Received: from zcs01.agora.pl (vzcs03.agora.pl [10.205.98.92])
by mail.agora.pl (8.13.8/8.11.1) with ESMTP id o2N9SCOb009666;
Tue, 23 Mar 2010 10:28:12 +0100
Received: from localhost (localhost.localdomain [127.0.0.1])
by zcs01.agora.pl (Postfix) with ESMTP id 02E4F1176C;
Tue, 23 Mar 2010 10:28:12 +0100 (CET)
X-Virus-Scanned: amavisd-new at zcs01.agora.pl
Received: from zcs01.agora.pl ([127.0.0.1])
by localhost (zcs01.agora.pl [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id W7J+RrKnx2Qk; Tue, 23 Mar 2010 10:28:11 +0100 (CET)
Received: from t42.localnet (unknown [10.201.55.171])
by zcs01.agora.pl (Postfix) with ESMTPSA id D89401183C;
Tue, 23 Mar 2010 10:28:11 +0100 (CET)
From: "alteriks@gmail.com" <alteriks@gmail.com>
To: Dan Naumov <dan.naumov@gmail.com>
Date: Tue, 23 Mar 2010 10:28:10 +0100
User-Agent: KMail/1.12.4 (Linux/2.6.30-1-686; KDE/4.3.4; i686; ; )
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
<684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
<cf9b1ee01003221500j6c605590ka1d25722f35d58cc@mail.gmail.com>
In-Reply-To: <cf9b1ee01003221500j6c605590ka1d25722f35d58cc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201003231028.11043.alteriks@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 09:28:14 -0000
On Monday, 22 of March 2010 23:00:17 Dan Naumov wrote:
> On Mon, Mar 22, 2010 at 10:41 PM, Krzysztof Dajka <alteriks@gmail.com>=20
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
> > =BFzfs? 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.
>=20
> 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 3x500=
GB=20
in raidz1. As it's full zfs system, I'm booting from SD card. What should I=
=20
enable in kernel to produce good crashdump?
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 09:48:14 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 19E001065670
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 09:48:14 +0000 (UTC)
(envelope-from alteriks@gmail.com)
Received: from mail.agora.pl (mail.agora.pl [193.42.230.53])
by mx1.freebsd.org (Postfix) with ESMTP id 96A9C8FC1A
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 09:48:13 +0000 (UTC)
Received: from zcs01.agora.pl (vzcs03.agora.pl [10.205.98.92])
by mail.agora.pl (8.13.8/8.11.1) with ESMTP id o2N9CmYu017923;
Tue, 23 Mar 2010 10:12:49 +0100
Received: from localhost (localhost.localdomain [127.0.0.1])
by zcs01.agora.pl (Postfix) with ESMTP id E19BD119B4;
Tue, 23 Mar 2010 10:12:48 +0100 (CET)
X-Virus-Scanned: amavisd-new at zcs01.agora.pl
Received: from zcs01.agora.pl ([127.0.0.1])
by localhost (zcs01.agora.pl [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id VVErzYberUnH; Tue, 23 Mar 2010 10:12:48 +0100 (CET)
Received: from t42.localnet (unknown [10.201.55.171])
by zcs01.agora.pl (Postfix) with ESMTPSA id 012F9119B5;
Tue, 23 Mar 2010 10:12:45 +0100 (CET)
From: "alteriks@gmail.com" <alteriks@gmail.com>
To: Dan Naumov <dan.naumov@gmail.com>
Date: Tue, 23 Mar 2010 10:12:43 +0100
User-Agent: KMail/1.12.4 (Linux/2.6.30-1-686; KDE/4.3.4; i686; ; )
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
<684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
<cf9b1ee01003221455i7fc5d66fi42315cefd3ed6033@mail.gmail.com>
In-Reply-To: <cf9b1ee01003221455i7fc5d66fi42315cefd3ed6033@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201003231012.43616.alteriks@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 09:48:14 -0000
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
> > =BFzfs? 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?
>=20
> 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.
>=20
> > 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=3D.
> > 8.0-STABLE -> tag=3DRELENG_8
> > 8.0-RELEASE-p2 -> tag=3DRELENG_8_0 ? (btw what does p2 mean?)
> > If someone patient could explain it to me I'd be grateful.
>=20
> 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)
>=20
> Same line of thinking applies to 7-STABLE, 7.3-RELEASE and so on.
>=20
>=20
> - Sincerely,
> Dan Naumov
>=20
Thanks for clarifying. I will try turning swap ASAP.
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 14:28:01 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C9D601065761
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 14:28:01 +0000 (UTC)
(envelope-from jhb@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
by mx1.freebsd.org (Postfix) with ESMTP id 16F428FC1F
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 14:28:00 +0000 (UTC)
Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net
[66.111.2.69])
by cyrus.watson.org (Postfix) with ESMTPSA id C2DF846B8E;
Tue, 23 Mar 2010 10:27:59 -0400 (EDT)
Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9])
by bigwig.baldwin.cx (Postfix) with ESMTPA id AEDC88A01F;
Tue, 23 Mar 2010 10:27:58 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-stable@freebsd.org
Date: Tue, 23 Mar 2010 10:09:54 -0400
User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; )
References: <74426BABA82C4FD28FDF848FB65197FF@vosz.local>
In-Reply-To: <74426BABA82C4FD28FDF848FB65197FF@vosz.local>
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
Message-Id: <201003231009.54872.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1
(bigwig.baldwin.cx); Tue, 23 Mar 2010 10:27:58 -0400 (EDT)
X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.7 required=4.2 tests=AWL,BAYES_00 autolearn=ham
version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx
Cc: Alexander Zagrebin <alexz@visp.ru>
Subject: Re: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS (doesn't
link with libzfsboot)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 14:28:01 -0000
On Tuesday 23 March 2010 3:41:06 am Alexander Zagrebin wrote:
> 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?
Can you provide the output of the errors you are seeing?
--
John Baldwin
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 16:19:13 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 608381065677
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 16:19:13 +0000 (UTC)
(envelope-from David.Boyd@insightbb.com)
Received: from mxsf12.insightbb.com (mxsf12.insightbb.com [74.128.0.94])
by mx1.freebsd.org (Postfix) with ESMTP id 2D5608FC14
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 16:19:12 +0000 (UTC)
X-IronPort-AV: E=Sophos;i="4.51,296,1267419600"; d="scan'208";a="54799010"
Received: from unknown (HELO asav02.insightbb.com) ([172.31.249.123])
by mxsf12.insightbb.com with ESMTP; 23 Mar 2010 12:19:11 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAA+HqEtKgYlR/2dsb2JhbACIZpJCdL0tDYRwBA
X-IronPort-AV: E=Sophos;i="4.51,296,1267419600"; d="scan'208";a="353321242"
Received: from 74-129-137-81.dhcp.insightbb.com (HELO sneezy) ([74.129.137.81])
by asav02.insightbb.com with SMTP; 23 Mar 2010 12:19:11 -0400
From: "David Boyd" <David.Boyd@insightbb.com>
To: <freebsd-stable@freebsd.org>
Date: Tue, 23 Mar 2010 12:19:11 -0400
Message-ID: <OJEBKOFDEOADELCOBJCGIEJPCOAA.David.Boyd@insightbb.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: 7.3-RELEASE sysinstall netDev feature
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 16:19:13 -0000
The 7.3-RELEASE release notes indicate that sysinstall now supports a list
of network interfaces in the netDev (install.cfg) parameter.
After upgrading to 7.3-RELEASE (via csup) sysinstall does not seem to
support that feature.
Also, the man page doesn't contain any mention of the new feature.
Is this the code committed by Rink Springer last October?
This feature would sure be great for our many scripted installs (avoiding
the hassles associated with plugging the cable into the wrong interface or
having the interface type change unexpectedly due to hardware swaps).
Thanks.
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 17:04:06 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 95592106566C
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 17:04:06 +0000 (UTC)
(envelope-from rink@gloom.codethulu.net)
Received: from mx1.codethulu.net (mail.codethulu.net [77.243.236.173])
by mx1.freebsd.org (Postfix) with ESMTP id 517918FC12
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 17:04:06 +0000 (UTC)
Received: from anathema.codethulu.net (mail.codethulu.net [77.243.236.173])
by mx1.codethulu.net (Postfix) with ESMTP id B90A6375A81B;
Tue, 23 Mar 2010 17:47:29 +0100 (CET)
X-Virus-Scanned: amavisd-new at codethulu.net
Received: from mx1.codethulu.net ([77.243.236.173])
by anathema.codethulu.net (anathema.codethulu.net [77.243.236.173])
(amavisd-new, port 10024)
with ESMTP id keR730hqy5gW; Tue, 23 Mar 2010 17:47:25 +0100 (CET)
Received: from gloom.codethulu.net (mail.codethulu.net [77.243.236.173])
by mx1.codethulu.net (Postfix) with ESMTP id 9B0CF375A81A;
Tue, 23 Mar 2010 17:47:25 +0100 (CET)
Received: by gloom.codethulu.net (Postfix, from userid 1000)
id 96F5E6D455; Tue, 23 Mar 2010 17:47:25 +0100 (CET)
Date: Tue, 23 Mar 2010 17:47:25 +0100
From: Rink Springer <rink@FreeBSD.org>
To: David Boyd <David.Boyd@insightbb.com>
Message-ID: <20100323164725.GD43249@rink.nu>
References: <OJEBKOFDEOADELCOBJCGIEJPCOAA.David.Boyd@insightbb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OJEBKOFDEOADELCOBJCGIEJPCOAA.David.Boyd@insightbb.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: freebsd-stable@freebsd.org
Subject: Re: 7.3-RELEASE sysinstall netDev feature
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 17:04:06 -0000
Hi David,
On Tue, Mar 23, 2010 at 12:19:11PM -0400, David Boyd wrote:
> Is this the code committed by Rink Springer last October?
The code I committed (revision 198317) added support for 'netDev=ANY';
this would select the first device that has an active link.
Note that the value is case sensitive, so only using 'ANY' will work.
> This feature would sure be great for our many scripted installs (avoiding
> the hassles associated with plugging the cable into the wrong interface or
> having the interface type change unexpectedly due to hardware swaps).
What exactly happens in such a case? Is the line planly ignored? Are you
using a non-interactive install?
Regards,
--
Rink P.W. Springer - http://rink.nu
"Beauty often seduces us on the road to truth."
- Dr. Wilson
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 19:27:28 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5393F106564A
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 19:27:28 +0000 (UTC)
(envelope-from alexz@visp.ru)
Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2])
by mx1.freebsd.org (Postfix) with ESMTP id 055AE8FC08
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 19:27:27 +0000 (UTC)
Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin)
by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD))
(envelope-from <alexz@visp.ru>)
id 1Nu9l6-000OzR-W0; Tue, 23 Mar 2010 22:27:25 +0300
From: "Alexander Zagrebin" <alexz@visp.ru>
To: "'John Baldwin'" <jhb@freebsd.org>
References: <74426BABA82C4FD28FDF848FB65197FF@vosz.local>
<201003231009.54872.jhb@freebsd.org>
Date: Tue, 23 Mar 2010 22:27:24 +0300
Keywords: freebsd-stable
Message-ID: <B7C3DB99508C418ABC14AE4B8FB7F845@vosz.local>
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
In-Reply-To: <201003231009.54872.jhb@freebsd.org>
Thread-Index: AcrKlXvVoTfOd6wUS02H4yL2CZX4QwAJLNFA
Cc: freebsd-stable@freebsd.org
Subject: RE: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS (doesn't
link with libzfsboot)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 19:27:28 -0000
> On Tuesday 23 March 2010 3:41:06 am Alexander Zagrebin wrote:
> > 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?
>
> Can you provide the output of the errors you are seeing?
There are no build errors.
IMHO, to support a ZFS, the loader have to be linked with the libzfsboot.
But (IMHO again) in the RELENG_7_3_0_RELEASE zfsloader builds without
this library.
To build zfsloader, the /usr/src/sys/boot/i386/zfsloader/Makefile contains
the following most important lines:
LOADER_ZFS_SUPPORT=yes
...
.include "${.CURDIR}/../loader/Makefile"
So the /usr/src/sys/boot/i386/loader/Makefile have to set required CFLAGS
and so on,
but it don't. It contains the folowing ZFS related lines:
# Set by zfsloader Makefile
#.if ${MK_ZFS} != "no"
#CFLAGS+= -DLOADER_ZFS_SUPPORT
#LIBZFS= ${.OBJDIR}/../../zfs/libzfsboot.a
#.else
LIBZFS=
#.endif
As you can see, all ZFS related stuff is commented out.
So "LOADER_ZFS_SUPPORT=yes" (/usr/src/sys/boot/i386/zfsloader/Makefile)
doesn't
affects a build process.
--
Alexander Zagrebin
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 20:08:09 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C781A106564A;
Tue, 23 Mar 2010 20:08:09 +0000 (UTC)
(envelope-from sektie@gmail.com)
Received: from mail-pz0-f199.google.com (mail-pz0-f199.google.com
[209.85.222.199])
by mx1.freebsd.org (Postfix) with ESMTP id 9028B8FC08;
Tue, 23 Mar 2010 20:08:09 +0000 (UTC)
Received: by pzk37 with SMTP id 37so626747pzk.7
for <multiple recipients>; Tue, 23 Mar 2010 13:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:sender:received:in-reply-to
:references:date:x-google-sender-auth:received:message-id:subject
:from:to:cc:content-type:content-transfer-encoding;
bh=ztYMkLWDSwRqd7EwG+Wha+Ld21OjHlwxdtF0VipSVU4=;
b=ROHSiAPGvg85jPXP8MfietJKIamqMEOcG8n7ZOcs7QFsfjjNdv2+n8Sjx03vkWDhZw
C4nRTu4q7743tzSQWjxb1tK/bl1GuUbzWgbB1rvws0vJa0yif/iOzDCQpJjeWp0v8vjK
ciGLBMrkavILqT1hDghXq2wxbMmMN86POlN88=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
b=IhzMwQ7geCmqnkJcovCVqkqoEWABhOFSEO8aUoQxK8vazrS0dHQOSqOvB3nCPp97bI
j58l29gDoQfsY+Zw4dHw6UQnMet28no3diG3/JIl1gmal+JhLMKzphJB163ehEQ7BGMe
Hmvc8c3JuZHXkWqVsK5sgm3grtTNBpvMQcMT4=
MIME-Version: 1.0
Sender: sektie@gmail.com
Received: by 10.141.4.5 with HTTP; Tue, 23 Mar 2010 12:58:13 -0700 (PDT)
In-Reply-To: <20100323164725.GD43249@rink.nu>
References: <OJEBKOFDEOADELCOBJCGIEJPCOAA.David.Boyd@insightbb.com>
<20100323164725.GD43249@rink.nu>
Date: Tue, 23 Mar 2010 12:58:13 -0700
X-Google-Sender-Auth: 6c7ba30029a45c87
Received: by 10.141.23.20 with SMTP id a20mr79792rvj.1.1269374293668; Tue, 23
Mar 2010 12:58:13 -0700 (PDT)
Message-ID: <e277d6c81003231258k58d31c2cw919dd18f33d2c509@mail.gmail.com>
From: Randi Harper <randi@freebsd.org>
To: Rink Springer <rink@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: David Boyd <David.Boyd@insightbb.com>, freebsd-stable@freebsd.org
Subject: Re: 7.3-RELEASE sysinstall netDev feature
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 20:08:09 -0000
On Tue, Mar 23, 2010 at 9:47 AM, Rink Springer <rink@freebsd.org> wrote:
> Hi David,
>
> On Tue, Mar 23, 2010 at 12:19:11PM -0400, David Boyd wrote:
>> Is this the code committed by Rink Springer last October?
>
> The code I committed (revision 198317) added support for 'netDev=3DANY';
> this would select the first device that has an active link.
>
> Note that the value is case sensitive, so only using 'ANY' will work.
>
>> This feature would sure be great for our many scripted installs (avoidin=
g
>> the hassles associated with plugging the cable into the wrong interface =
or
>> having the interface type change unexpectedly due to hardware swaps).
>
> What exactly happens in such a case? Is the line planly ignored? Are you
> using a non-interactive install?
>
> Regards,
>
> --
> Rink P.W. Springer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0- http://rink.nu
> "Beauty often seduces us on the road to truth."
> - Dr. Wilson
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
If you can enable debugging and take a look at the debug console, that
output would be helpful. What exactly are you specifying for netDev?
ANY or a comma delimited list of interfaces? Is it saying that it
can't find a network interface or is it prompting you to select one?
-- randi
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 21:42:30 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3BE0C1065673
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 21:42:30 +0000 (UTC)
(envelope-from jhb@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
by mx1.freebsd.org (Postfix) with ESMTP id 0C61E8FC13
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 21:42:30 +0000 (UTC)
Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net
[66.111.2.69])
by cyrus.watson.org (Postfix) with ESMTPSA id B00A846B17;
Tue, 23 Mar 2010 17:42:29 -0400 (EDT)
Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9])
by bigwig.baldwin.cx (Postfix) with ESMTPA id 1D6258A01F;
Tue, 23 Mar 2010 17:42:29 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-stable@freebsd.org
Date: Tue, 23 Mar 2010 17:39:36 -0400
User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; )
References: <74426BABA82C4FD28FDF848FB65197FF@vosz.local>
<201003231009.54872.jhb@freebsd.org>
<B7C3DB99508C418ABC14AE4B8FB7F845@vosz.local>
In-Reply-To: <B7C3DB99508C418ABC14AE4B8FB7F845@vosz.local>
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
Message-Id: <201003231739.36145.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1
(bigwig.baldwin.cx); Tue, 23 Mar 2010 17:42:29 -0400 (EDT)
X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.7 required=4.2 tests=AWL,BAYES_00 autolearn=ham
version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx
Cc: Alexander Zagrebin <alexz@visp.ru>
Subject: Re: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS (doesn't
link with libzfsboot)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 21:42:30 -0000
On Tuesday 23 March 2010 3:27:24 pm Alexander Zagrebin wrote:
> > On Tuesday 23 March 2010 3:41:06 am Alexander Zagrebin wrote:
> > > 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?
> >
> > Can you provide the output of the errors you are seeing?
>
> There are no build errors.
>
> IMHO, to support a ZFS, the loader have to be linked with the libzfsboot.
> But (IMHO again) in the RELENG_7_3_0_RELEASE zfsloader builds without
> this library.
Oh, gah. Fixed in 7. Probably too late for 7.3.
--
John Baldwin
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 22:09:31 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CF7DB1065673;
Tue, 23 Mar 2010 22:09:31 +0000 (UTC)
(envelope-from sektie@gmail.com)
Received: from mail-pz0-f201.google.com (mail-pz0-f201.google.com
[209.85.222.201])
by mx1.freebsd.org (Postfix) with ESMTP id 9DDA28FC1C;
Tue, 23 Mar 2010 22:09:31 +0000 (UTC)
Received: by pzk39 with SMTP id 39so3177516pzk.15
for <multiple recipients>; Tue, 23 Mar 2010 15:09:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:sender:received:in-reply-to
:references:date:x-google-sender-auth:message-id:subject:from:to:cc
:content-type; bh=r34wnregUAVciBUvGSHeoqtvqK0XxpmonIRZQC1NrJI=;
b=Gmuo0PUIC0VgxFdHpTfGFh2bGflWjBfkAwwlPYP8lorG70GnmafhlUt4Dh7ocxag9q
7U9BqDIPcWG5Js/o2ovDgP+a4NQ2vtZGqfjt7FpH5/N2yd/XM0JvQatYQiGjZ9kvlVnS
+KLde65P+h8bjOYbo8chGfr7qw1ZSXjJ1uf1c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
b=HxPm7H/zLmLmSnDzn14oLXrXCoqaG77D8uQP5snWQrb5to4dYQbfbQu/ymLhtHGpv2
GdMBlc606qacuK/3Pj7kePSUPWej9EQod3Y2crqNpiCA8RW67lp6XzJaehFLWnA//jKt
hIEGu65/lDOyaLtJw1lilOGVCaz1Bp/QHgl/0=
MIME-Version: 1.0
Sender: sektie@gmail.com
Received: by 10.141.187.4 with SMTP id o4mr4572032rvp.217.1269382171049; Tue,
23 Mar 2010 15:09:31 -0700 (PDT)
In-Reply-To: <OJEBKOFDEOADELCOBJCGOEKBCOAA.David.Boyd@insightbb.com>
References: <e277d6c81003231258k58d31c2cw919dd18f33d2c509@mail.gmail.com>
<OJEBKOFDEOADELCOBJCGOEKBCOAA.David.Boyd@insightbb.com>
Date: Tue, 23 Mar 2010 15:09:31 -0700
X-Google-Sender-Auth: 4e2d60f50e6e5370
Message-ID: <e277d6c81003231509l3590ffa7gb1724e7d606f2da0@mail.gmail.com>
From: Randi Harper <randi@freebsd.org>
To: David Boyd <David.Boyd@insightbb.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Rink Springer <rink@freebsd.org>, freebsd-stable@freebsd.org
Subject: Re: 7.3-RELEASE sysinstall netDev feature
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 22:09:31 -0000
On Tue, Mar 23, 2010 at 1:51 PM, David Boyd <David.Boyd@insightbb.com> wrote:
> Randi,
>
> Sorry for taking so long to reply.
>
> I won't be able to retry this today.
>
> But I looked at the code in tcpip.c and the support for the comma separated
> list of interface names (or netDev=ALL) is just not there in 7.3-RELEASE.
>
> I looked at the csup'd source and at the source from the dvd1 image.
Yeah, I suspect this wasn't MFC'ed and the release notes will need to
be corrected. I'm going to double check this later tonight. FWIW, if
this is something you are really that interested in having work, it
will work just fine in 7.3-RELEASE, you'd just have to build it
yourself.
-- randi
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 22:29:41 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 242601065676
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 22:29:41 +0000 (UTC)
(envelope-from kensmith@buffalo.edu)
Received: from localmailB.acsu.buffalo.edu (localmail.buffalo.edu
[128.205.5.200])
by mx1.freebsd.org (Postfix) with ESMTP id EAFFA8FC0A
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 22:29:40 +0000 (UTC)
Received: from localmailB.acsu.buffalo.edu (localhost [127.0.0.1])
by localhost (Postfix) with SMTP id 2D0D278A
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 18:29:40 -0400 (EDT)
Received: from localmailB.acsu.buffalo.edu (localhost [127.0.0.1])
by localmailB.acsu.buffalo.edu (Postfix) with ESMTP id B58A67E8
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 18:29:39 -0400 (EDT)
Received: from mweb2.acsu.buffalo.edu (mweb2.acsu.buffalo.edu [128.205.5.239])
by localmailB.acsu.buffalo.edu (Prefixe) with ESMTP id B0FE8613
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 18:29:39 -0400 (EDT)
Received: from ken-smiths-macbook-pro.local
(cpe-76-180-182-44.buffalo.res.rr.com [76.180.182.44])
by mweb2.acsu.buffalo.edu (Postfix) with ESMTP id 7B3AC203C0
for <freebsd-stable@freebsd.org>; Tue, 23 Mar 2010 18:29:39 -0400 (EDT)
Message-ID: <4BA940CE.2050305@buffalo.edu>
Date: Tue, 23 Mar 2010 18:29:34 -0400
From: Ken Smith <kensmith@buffalo.edu>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-PM-EL-Spam-Prob: XX: 27%
Subject: FYI - FreeBSD 7.3 has been released...
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 22:29:41 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Just a quick note for any of you who are not subscribed to the
freebsd-announce@ mailing list.
7.3-RELEASE was announced today. The announcement message is
available here:
http://www.freebsd.org/releases/7.3R/announce.html
Thanks.
- --
Ken Smith
- - From there to here, from here to | kensmith@buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkupQM4ACgkQ/G14VSmup/ZXLgCdF63w0KJV6fU/NbeNWHAQ4lar
3TsAoIwRSTyijFSb8SiZh2+91WDr0Gh1
=CUdv
-----END PGP SIGNATURE-----
From owner-freebsd-stable@FreeBSD.ORG Tue Mar 23 22:51:12 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C207F1065679;
Tue, 23 Mar 2010 22:51:12 +0000 (UTC)
(envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46])
by mx1.freebsd.org (Postfix) with ESMTP id A59A38FC1C;
Tue, 23 Mar 2010 22:51:12 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
id 67A298C088; Tue, 23 Mar 2010 17:31:26 -0500 (CDT)
Date: Tue, 23 Mar 2010 17:31:26 -0500
From: Mark Linimon <linimon@lonesome.com>
To: FreeBSD portmgr secretary <portmgr-secretary@FreeBSD.org>
Message-ID: <20100323223126.GA3967@lonesome.com>
References: <20100323201137.GA45259@goodking.goodking.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100323201137.GA45259@goodking.goodking.ca>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: ports@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org
Subject: Re: Complete ports thaw
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 22:51:12 -0000
It probably bears repeating that the tree will be unstable for the next
few days while a number of large commits hit the tree. These were held
off during the release process to make life easier in case portmgr had
to do tag-slips.
Image processing libraries, xorg, kde, and gnome are scheduled to be
updated, among others.
mcl
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 07:54:52 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 23863106566C
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 07:54:52 +0000 (UTC)
(envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46])
by mx1.freebsd.org (Postfix) with ESMTP id 04E658FC15
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 07:54:51 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
id 9011F8C085; Wed, 24 Mar 2010 02:54:51 -0500 (CDT)
Date: Wed, 24 Mar 2010 02:54:51 -0500
From: Mark Linimon <linimon@lonesome.com>
To: Krzysztof Dajka <alteriks@gmail.com>
Message-ID: <20100324075451.GB13561@lonesome.com>
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
<684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>,
Dan Naumov <dan.naumov@gmail.com>
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 07:54:52 -0000
On Mon, Mar 22, 2010 at 08:41:35PM +0000, Krzysztof Dajka wrote:
> But still I am confused with FreeBSD naming and it's relation with
> tags which are used in standard-supfile.
Please see the following for an overview:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/introduction.html#CURRENT
The definition of the -STABLE branches is that we try to keep the interfaces
to the kernel stable. While this helps also keep the src tree itself stable,
from time to time regressions will be introduced as changes are merged back
from the -CURRENT branch.
So, for the src tree, there are:
- releases, which are not updated;
- releases plus security fixes;
- -STABLE branches;
- the -CURRENT branch.
The ports tree is not branched, so you can consider that everything is
"current". If you need to stay with a ports tree that is more tested,
you'll need to stay with the ports tree that came with a -release.
mcl
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 08:49:26 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4B71D106566B
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 08:49:26 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from qmta05.westchester.pa.mail.comcast.net
(qmta05.westchester.pa.mail.comcast.net [76.96.62.48])
by mx1.freebsd.org (Postfix) with ESMTP id ECB778FC08
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 08:49:25 +0000 (UTC)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44])
by qmta05.westchester.pa.mail.comcast.net with comcast
id wwoD1d0060xGWP855wpSQg; Wed, 24 Mar 2010 08:49:26 +0000
Received: from koitsu.dyndns.org ([98.248.46.159])
by omta12.westchester.pa.mail.comcast.net with comcast
id wwpR1d0013S48mS3YwpRq7; Wed, 24 Mar 2010 08:49:26 +0000
Received: by icarus.home.lan (Postfix, from userid 1000)
id E93BC9B436; Wed, 24 Mar 2010 01:49:23 -0700 (PDT)
Date: Wed, 24 Mar 2010 01:49:23 -0700
From: Jeremy Chadwick <freebsd@jdc.parodius.com>
To: Krzysztof Dajka <alteriks@gmail.com>
Message-ID: <20100324084923.GA27740@icarus.home.lan>
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
<684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: freebsd-stable@freebsd.org
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 08:49:26 -0000
On Mon, Mar 22, 2010 at 08:41:35PM +0000, Krzysztof Dajka wrote:
> At first I didn't knew that I am upgrading to bleeding edge/developer
> branch of FreeBSD.
You're not. There seems to be some misconceptions with regards to what
the tags represent, because people's opinions get in the way (mine
included).
I'll give you the run down as someone who's been using FreeBSD since the
2.2 days. I'm speaking strictly about src (base system, OS, etc.) and
not ports. Ports are their own thing, and aren't tagged (the ports
infrastructure should work on any of the below tags, which is why ports
are always tag=.).
I also include correlations to Debian release nomenclature. Hope this
helps.
-RELEASE (tag=RELENG_x_y)
An official release of the OS when a new version comes out. Changes to
this tag are rarely made; the exceptions to the rule are security fixes
and *serious* (major/extreme) stability fixes. "Serious" means
something that would impact the OS from functioning for all systems and
is considered volatile -- it does not mean "feature X doesn't work
right" or "driver X doesn't function correctly". Users who encounter a
problem of this nature are told to run -STABLE where the fix is.
The FreeBSD user community often totes this as "the most rock solid
release tag there is", which in my opinion hasn't been the case since
the 4.x days. We've used the STABLE branches since the 4.x days and
have only run into problems on rare occasion (rolling back to a previous
commit is as easy as using csup's "date" tag in the supfile).
In the Debian world, this tag would correlate with stable/lenny.
-STABLE (tag=RELENG_x)
Identical to RELEASE except changes to this tag are made fairly
regularly. OS/kernel, drivers, base system/userland, and security
issues are all addressed here. Meaning: if you encounter something
broken in non-CURRENT FreeBSD, the fix/change will most likely go into
this branch. The more you read popular FreeBSD mailing lists
(freebsd-stable, freebsd-users, freebsd-questions, etc.), the more
you'll realise that's the case.
MFCs ("merge from CURRENT") are also occasionally brought down from HEAD
(see below) into this branch for usability testing. This is where
anti-STABLE advocates get their "STABLE isn't stable at all, use RELEASE
if you want stability" viewpoint.
The FreeBSD user community has split opinions of this branch; some
believe it to be "a development/unstable" branch, while others (like
myself) believe it to be more solid than RELEASE, since developers are
much more focused on STABLE than RELEASE. Developers who break the
STABLE branch are usually lectured/reprimanded in some way; such
breakage usually appears as buildworld/buildkernel failing. Turnaround
time for fixing such breakage is usually 24-48 hours tops.
In the Debian world, this tag would correlate with testing/squeeze.
-CURRENT (tag=., otherwise known as HEAD)
This is where all the crazy, in-development code and features go. That
includes library API changes, kernel ABI changes, kernel threading
adjustments, experimental drivers ("it works on this one system I have
at home but that's it"), or anything else a developer/committer is
working on which is brand-spanking-new. It also encapsulates major
underlying configuration changes in the OS, including pathname changes
or syntactical changes. The OS is also significantly slower
(kernel-wise out-of-the-box due to the default kernel configs enabling
debugging/analysis features which are necessary for development.
This branch is known to break quite often, and that's 100% OK. Data
loss can happen as well, depending on what breaks or what bugs are
introduced, so if you run this you should absolutely do back-ups.
In the Debian world, this tag would correlate with unstable/sid.
--
| Jeremy Chadwick jdc@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 13:30:50 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6BE6C1065675;
Wed, 24 Mar 2010 13:30:50 +0000 (UTC)
(envelope-from ohartman@zedat.fu-berlin.de)
Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de
[130.133.4.66])
by mx1.freebsd.org (Postfix) with ESMTP id E96858FC1B;
Wed, 24 Mar 2010 13:30:49 +0000 (UTC)
Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69])
by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp
(envelope-from <ohartman@zedat.fu-berlin.de>)
id <1NuQfY-0005RR-QD>; Wed, 24 Mar 2010 14:30:48 +0100
Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198])
by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa
(envelope-from <ohartman@zedat.fu-berlin.de>)
id <1NuQfY-0003UM-OQ>; Wed, 24 Mar 2010 14:30:48 +0100
Message-ID: <4BAA1478.9020201@zedat.fu-berlin.de>
Date: Wed, 24 Mar 2010 13:32:40 +0000
From: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
rv:1.9.1.8) Gecko/20100317 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org,
freebsd-questions@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: 130.133.86.198
Cc:
Subject: Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon graphics
on FBSD 8.0-STABLE SMP/sm64 box
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 13:30:50 -0000
Since the introduction of Thunderbird 3.0 and Firefox 3.6 I see
spontanous crashes/coredumps of both thunderbird and firefox. Interingly
Firefox 3.5.X works well on he same platform.
The platform is a FreeBSD 8.0-STABLE/amd64 (r205536: Tue Mar 23 22:19:04
CET 2010), SMP box with 8GB of RAM, QuadCore Intel Q6600 on a P35-based
motherboard.
Thunderbird 3 crashes rarely compared to Firefox 3. The longer the
application thunderbird runs, the higher the likelyhood the app crashes
and vanishes. Sometimes this happens immediately after starting
thunderbird, sometimes it takes its few minutes or half an hour.
Firefox 3 is sensitive to its pull-down menus or requester showing up in
some situations. I can provoke a crash by clicking onto a pull-down-menu
in firefox 3, it immediately dumps a core.
Well, I wouldn't write s cross-posting if I would be sure this behaviour
is due to some oddities in my installation, but since this odd behaviour
occured both on Firefox 3.6 and Thunderbird 3 in several situations and
with several tries to get a workaround, I feel desperately lost.
What I did so far:
- Recompiling EVERY port on my box (four times in a row to make sure
everything is right, its a pain with nearly 950 ports).
- Deinstalling both Firefox 3 and Thunderbird 3 and installing the
binary packages from FreeBSD.ORG
I have a private UP box, running the same OS FreeBSD 8.0-STABLE/amd64 on
a single core Athlon 3500+ with only 2GB of RAM. There I use both
Thunderbird 3.0.3 and Firefox 3.6.2 without any problem.
I suspect the X11 server or some part of the accelerator stuff
triggering the crashes. On the both machines,
WITHOUT_NOUVEAU = YES
is defined. On the UP box at home, I utilise a HD4830 graphics
accelerator with DR enabled. The lab's box have had
both HD4670 and now HD4770 accelerators, both do not work properly with
the state-of-the-art drivers supported by the official pots collection.
HD4670 never got to work since the new RadeonHD driver 1.3 was
introduced (prior to that it worked), the new HD4770 works with
explicitely disabling DRI and crashes whenever I leave a session (quit
windowmaker). Well, this is another story, but I suspect the Radeon
driver infrastructure causing the problems - but I'm not sure.
I use perl-threaded 5.10, but I guess this is not a problem since the
problems occur whether I have threaded perl or not.
As I said, I feel like a dead man in the water ...
Regards,
Oliver
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 14:06:56 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 17A9E106564A;
Wed, 24 Mar 2010 14:06:56 +0000 (UTC)
(envelope-from gary.jennejohn@freenet.de)
Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3])
by mx1.freebsd.org (Postfix) with ESMTP id A31418FC08;
Wed, 24 Mar 2010 14:06:55 +0000 (UTC)
Received: from [195.4.92.18] (helo=8.mx.freenet.de)
by mout1.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
25) (Exim 4.72 #2)
id 1NuREU-0002G1-Cf; Wed, 24 Mar 2010 15:06:54 +0100
Received: from p57ae0c82.dip0.t-ipconnect.de ([87.174.12.130]:18145
helo=ernst.jennejohn.org)
by 8.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25)
(Exim 4.72 #2) id 1NuRET-0006U0-Sh; Wed, 24 Mar 2010 15:06:54 +0100
Date: Wed, 24 Mar 2010 15:06:53 +0100
From: Gary Jennejohn <gary.jennejohn@freenet.de>
To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
Message-ID: <20100324150653.3a447c98@ernst.jennejohn.org>
In-Reply-To: <4BAA1478.9020201@zedat.fu-berlin.de>
References: <4BAA1478.9020201@zedat.fu-berlin.de>
X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; amd64-portbld-freebsd9.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org,
freebsd-ports@freebsd.org
Subject: Re: Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon
graphics on FBSD 8.0-STABLE SMP/sm64 box
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gary.jennejohn@freenet.de
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 14:06:56 -0000
On Wed, 24 Mar 2010 13:32:40 +0000
"O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote:
> Since the introduction of Thunderbird 3.0 and Firefox 3.6 I see
> spontanous crashes/coredumps of both thunderbird and firefox. Interingly
> Firefox 3.5.X works well on he same platform.
>
> The platform is a FreeBSD 8.0-STABLE/amd64 (r205536: Tue Mar 23 22:19:04
> CET 2010), SMP box with 8GB of RAM, QuadCore Intel Q6600 on a P35-based
> motherboard.
>
> Thunderbird 3 crashes rarely compared to Firefox 3. The longer the
> application thunderbird runs, the higher the likelyhood the app crashes
> and vanishes. Sometimes this happens immediately after starting
> thunderbird, sometimes it takes its few minutes or half an hour.
>
> Firefox 3 is sensitive to its pull-down menus or requester showing up in
> some situations. I can provoke a crash by clicking onto a pull-down-menu
> in firefox 3, it immediately dumps a core.
>
If you suspect the graphics card's driver is at fault then I would try
linux-opera or even linux-firefox and see whether it also dies when you
use a drop-down menu.
Another possibility would be to set hw.physmem to say 3G or 4G in
loader.conf and see whether that affects thunderbird/firefox. Who
knows, there may some weird problem caused by all that memory? That
would a fairly quick and cheap way to test this.
--
Gary Jennejohn
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 15:47:29 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F2326106566B
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 15:47:28 +0000 (UTC)
(envelope-from michal@ionic.co.uk)
Received: from mail1.sharescope.co.uk (pm1.ionic.co.uk [85.159.80.19])
by mx1.freebsd.org (Postfix) with ESMTP id 860CC8FC0C
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 15:47:27 +0000 (UTC)
Received: from localhost (unknown [127.0.0.1])
by mail1.sharescope.co.uk (Postfix) with ESMTP id CBB20FC0AB
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 15:47:27 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sharescope.co.uk
Received: from mail1.sharescope.co.uk ([127.0.0.1])
by localhost (mail1.sharescope.co.uk [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id HrnZV2EYPthN for <freebsd-stable@freebsd.org>;
Wed, 24 Mar 2010 15:47:23 +0000 (GMT)
Received: from [192.168.2.37] (office.ionic.co.uk [85.159.85.2])
(Authenticated sender: chris@sharescope.co.uk)
by mail1.sharescope.co.uk (Postfix) with ESMTPSA id 5E03CFC0A2
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 15:47:23 +0000 (GMT)
Message-ID: <4BAA3409.6080406@ionic.co.uk>
Date: Wed, 24 Mar 2010 15:47:21 +0000
From: Michal <michal@ionic.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 15:47:29 -0000
I wrote a really long e-mail but realised I could ask this question far
far easier, if it doesn't make sense, the original e-mail is bellow
Can I use ZFS to create a multinode storage area. Multiple HDD's in
Multiple servers to create one target of, for example, //officestorage
Allowing me to expand the storage space when needed and clients being
able to retrieve data (like RAID0 but over devices not HDD)
Here is an example I found which is where I'm getting some ideas from
http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
Any pointers would be helpful,
Thanks
---------------------------------------------------------------------
I've been searching around and I am finding myself confused and reading
conflicting information. I would like to build a Storage system where by
I have multiple nodes. At the minute I have a number or NAS's which work
well and RAID6 works well in the situation we have, but unfortunately
it's a short-term solution I inherited and once you crunch the numbers
of 6 devices with 6 HDD's in RAID6 you realise how much space you have
wasted then say, 1 device of RAID6 with 36 HDD's (the saving is a fair
few TB)
There are other issues as well, increasing the size, 3rd party NAS
device features missing which other storage devices have...etc so I
looked around and my grand idea was basically this;
"Build a system where I can have multiple nodes which create one target
(we will use //officestorage for our example) as opposed to //nas1/
which is of course 1 device. Using multiple nodes will allow us to add a
new device, thus increasing the space available but the target will
always be the same and to the client nothing has change (other then
available space) (Think of this as RAID0). Multiple nodes will also
allow for redundancy across devices (think RAID1) and give better IO as
it's multiple devices and not just 1 device. I could have devices in
different locations so a whole building could burn down and still not
lose the data"
After looking around I found this
https://help.ubuntu.com/community/HighlyAvailableAoETarget
Which looks quite good, it's basically RAID1 but instead of HDD's it's
across servers, I've used DRBD and it worked well, but this doesn't give
me better IO as only 1 device is live.
I then found this
http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
Which looks fantastic, though I will need a master server to create the
RAID0 and RAID1 across the multiple nodes and then share this out, which
is ok but I would need a hot swap master server, so I'm looking at two
of those. I then started thinking about ZFS, I've heard lots of good
things about it in the past and thinking can ZFS do what I want. I have
read some things which say it can do what that 2nd link does and others
which say it can't. Everything I come across is about using just 1
device and I could build 1 device with DRBD, but that doesn't help, nor
will it allow me to expand it (if your server runs out of physical space
you can't add more HDD's.
Anyone point me in the right direction??
Thanks
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 16:11:42 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id BD381106564A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 16:11:42 +0000 (UTC)
(envelope-from vince@unsane.co.uk)
Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net
[IPv6:2001:470:1f08:110::2])
by mx1.freebsd.org (Postfix) with ESMTP id 0EBDC8FC0A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 16:11:41 +0000 (UTC)
Received: from vhoffman.lon.namesco.net (184.67-246-213.ippool.namesco.net
[213.246.67.184]) (authenticated bits=0)
by unsane.co.uk (8.14.3/8.14.3) with ESMTP id o2OGBcNI005678
(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO)
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 16:11:39 GMT
(envelope-from vince@unsane.co.uk)
Message-ID: <4BAA39BA.4070702@unsane.co.uk>
Date: Wed, 24 Mar 2010 16:11:38 +0000
From: Vincent Hoffman <vince@unsane.co.uk>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <4BAA3409.6080406@ionic.co.uk>
In-Reply-To: <4BAA3409.6080406@ionic.co.uk>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 16:11:42 -0000
On 24/03/2010 15:47, Michal wrote:
> I wrote a really long e-mail but realised I could ask this question far
> far easier, if it doesn't make sense, the original e-mail is bellow
>
> Can I use ZFS to create a multinode storage area. Multiple HDD's in
> Multiple servers to create one target of, for example, //officestorage
> Allowing me to expand the storage space when needed and clients being
> able to retrieve data (like RAID0 but over devices not HDD)
>
At least in theory you could use geom_gate and zfs I suppose, never
tried it though.
ggatec(8), ggated(8) are your friends for that.
Vince
> Here is an example I found which is where I'm getting some ideas from
> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>
> Any pointers would be helpful,
> Thanks
>
>
> ---------------------------------------------------------------------
>
>
> I've been searching around and I am finding myself confused and reading
> conflicting information. I would like to build a Storage system where by
> I have multiple nodes. At the minute I have a number or NAS's which work
> well and RAID6 works well in the situation we have, but unfortunately
> it's a short-term solution I inherited and once you crunch the numbers
> of 6 devices with 6 HDD's in RAID6 you realise how much space you have
> wasted then say, 1 device of RAID6 with 36 HDD's (the saving is a fair
> few TB)
>
> There are other issues as well, increasing the size, 3rd party NAS
> device features missing which other storage devices have...etc so I
> looked around and my grand idea was basically this;
>
> "Build a system where I can have multiple nodes which create one target
> (we will use //officestorage for our example) as opposed to //nas1/
> which is of course 1 device. Using multiple nodes will allow us to add a
> new device, thus increasing the space available but the target will
> always be the same and to the client nothing has change (other then
> available space) (Think of this as RAID0). Multiple nodes will also
> allow for redundancy across devices (think RAID1) and give better IO as
> it's multiple devices and not just 1 device. I could have devices in
> different locations so a whole building could burn down and still not
> lose the data"
>
>
> After looking around I found this
>
> https://help.ubuntu.com/community/HighlyAvailableAoETarget
>
> Which looks quite good, it's basically RAID1 but instead of HDD's it's
> across servers, I've used DRBD and it worked well, but this doesn't give
> me better IO as only 1 device is live.
>
> I then found this
>
> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>
> Which looks fantastic, though I will need a master server to create the
> RAID0 and RAID1 across the multiple nodes and then share this out, which
> is ok but I would need a hot swap master server, so I'm looking at two
> of those. I then started thinking about ZFS, I've heard lots of good
> things about it in the past and thinking can ZFS do what I want. I have
> read some things which say it can do what that 2nd link does and others
> which say it can't. Everything I come across is about using just 1
> device and I could build 1 device with DRBD, but that doesn't help, nor
> will it allow me to expand it (if your server runs out of physical space
> you can't add more HDD's.
>
> Anyone point me in the right direction??
>
> Thanks
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 16:15:24 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E5719106564A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 16:15:24 +0000 (UTC)
(envelope-from spawk@acm.poly.edu)
Received: from acm.poly.edu (acm.poly.edu [128.238.9.200])
by mx1.freebsd.org (Postfix) with ESMTP id 846158FC1A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 16:15:24 +0000 (UTC)
Received: (qmail 12979 invoked from network); 24 Mar 2010 16:15:23 -0000
Received: from unknown (HELO ?10.0.0.170?) (spawk@128.238.64.31)
by acm.poly.edu with AES256-SHA encrypted SMTP;
24 Mar 2010 16:15:23 -0000
Message-ID: <4BAA3A7C.1030907@acm.poly.edu>
Date: Wed, 24 Mar 2010 12:14:52 -0400
From: Boris Kochergin <spawk@acm.poly.edu>
User-Agent: Thunderbird 2.0.0.23 (X11/20100311)
MIME-Version: 1.0
To: Vincent Hoffman <vince@unsane.co.uk>,
FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
References: <4BAA3409.6080406@ionic.co.uk> <4BAA39BA.4070702@unsane.co.uk>
In-Reply-To: <4BAA39BA.4070702@unsane.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 16:15:25 -0000
Vincent Hoffman wrote:
> On 24/03/2010 15:47, Michal wrote:
>
>> I wrote a really long e-mail but realised I could ask this question far
>> far easier, if it doesn't make sense, the original e-mail is bellow
>>
>> Can I use ZFS to create a multinode storage area. Multiple HDD's in
>> Multiple servers to create one target of, for example, //officestorage
>> Allowing me to expand the storage space when needed and clients being
>> able to retrieve data (like RAID0 but over devices not HDD)
>>
>>
> At least in theory you could use geom_gate and zfs I suppose, never
> tried it though.
> ggatec(8), ggated(8) are your friends for that.
>
>
> Vince
Indeed, you can. I've done it. As for failover, you could run the
recently-committed HAST code on primary and backup central machines.
Upon failure of the primary central machine, the backup one would take
its IP address, mount the ZFS filesystem over the network, do whatever
other userspace things may be necessary, and resume servicing I/O.
-Boris
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 16:20:29 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 87A1F106567E
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 16:20:29 +0000 (UTC)
(envelope-from fjwcash@gmail.com)
Received: from mail-px0-f200.google.com (mail-px0-f200.google.com
[209.85.216.200])
by mx1.freebsd.org (Postfix) with ESMTP id 5AB988FC1D
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 16:20:29 +0000 (UTC)
Received: by pxi38 with SMTP id 38so4501091pxi.27
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 09:20:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:content-type;
bh=sLJysUoZZF5sCFHiquj3ibUSmSQ8VZ6JBVuqiLB3Mv4=;
b=HnpmLx3eFpxaJNRvWIeEcF2fBGl0XocO32clTg3qHSN+SsFLbhbIZnznBWgaG1JLEm
aExDW2bXBn/9ZyME0OmSTZk/QgYUy+Md6XUzo76Q6Uyg4lyH9c7eZvUhEA0MuD6KPd2v
z8a9u88cLYAcFq+5YFUCuT9HZ7QoYt4xv0xzs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
b=Z5Af8Av/+GNPe9lWZM48znURlr7irF17BMYeagPV7zvpL7kHwqUDSvtFVaX+joWiTo
a/cIhh5smDsULsPT1ACGb9P5I0LaD2Q8EBrxbzG2+xjHDqFaEOFrUFz3FIG3U6Dj4O+G
uNIshTXEg1YnqMMfhps6uwutZ/SvIx2wHG04Q=
MIME-Version: 1.0
Received: by 10.141.13.7 with SMTP id q7mr3150189rvi.257.1269447628534; Wed,
24 Mar 2010 09:20:28 -0700 (PDT)
In-Reply-To: <4BAA3409.6080406@ionic.co.uk>
References: <4BAA3409.6080406@ionic.co.uk>
Date: Wed, 24 Mar 2010 09:20:28 -0700
Message-ID: <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
From: Freddie Cash <fjwcash@gmail.com>
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 16:20:29 -0000
On Wed, Mar 24, 2010 at 8:47 AM, Michal <michal@ionic.co.uk> wrote:
> I wrote a really long e-mail but realised I could ask this question far
> far easier, if it doesn't make sense, the original e-mail is bellow
>
> Can I use ZFS to create a multinode storage area. Multiple HDD's in
> Multiple servers to create one target of, for example, //officestorage
> Allowing me to expand the storage space when needed and clients being
> able to retrieve data (like RAID0 but over devices not HDD)
>
> Here is an example I found which is where I'm getting some ideas from
> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>
> Horribly, horribly, horribly complex. But, then, that's the Linux world.
:)
Server 1: bunch of disks exported via iSCSI
Server 2: bunch of disks exported via iSCSI
Server 3: bunch of disks exported via iSCSI
"SAN" box: uses all those iSCSI exports to create a ZFS pool
Use 1 iSCSI export from each server to create a raidz vdev. Or multiple
mirror vdevs. When you need more storage, just add another server full of
disks, export them via iSCSI to the "SAN" box, and expand the ZFS pool.
And, if you need fail-over, on your "SAN" box, you can use HAST at the lower
layers (currently only available in 9-CURRENT) to mirror the storage across
two systems, and use CARP to provide a single IP for the two boxes.
---------------------------------------------------------------------
> I've been searching around and I am finding myself confused and reading
> conflicting information. I would like to build a Storage system where by
> I have multiple nodes. At the minute I have a number or NAS's which work
> well and RAID6 works well in the situation we have, but unfortunately
> it's a short-term solution I inherited and once you crunch the numbers
> of 6 devices with 6 HDD's in RAID6 you realise how much space you have
> wasted then say, 1 device of RAID6 with 36 HDD's (the saving is a fair
> few TB)
>
> Yes, you save space, but your throughput will be horribly horribly horribly
low. RAID arrays should be narrow (1-9 disks), not wide (30+ disks), and
then combined into a larger array (multiple small RAID6 arrays joined into a
RAID0 stripe).
--
Freddie Cash
fjwcash@gmail.com
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 17:04:35 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DB0C9106566B
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:04:35 +0000 (UTC)
(envelope-from mloftis@wgops.com)
Received: from juggler.wgops.com (juggler.wgops.com [204.11.247.41])
by mx1.freebsd.org (Postfix) with ESMTP id B63D08FC13
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:04:35 +0000 (UTC)
Received: by juggler.wgops.com (Postfix, from userid 65534)
id 22845A80C9; Wed, 24 Mar 2010 11:04:35 -0600 (MDT)
X-Spam-ASN:
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on juggler.wgops.com
X-Spam-Level:
X-Spam-Status: No, score=-1.3 required=5.0 tests=ALL_TRUSTED,
SARE_SUB_OBFU_OTHER autolearn=no version=3.2.5
Received: from [192.168.1.44] (host-72-174-39-176.msl-mt.client.bresnan.net
[72.174.39.176])
by juggler.wgops.com (Postfix) with ESMTPSA id D8DE0A80C6
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 11:04:32 -0600 (MDT)
Date: Wed, 24 Mar 2010 11:04:36 -0600
From: Michael Loftis <mloftis@wgops.com>
To: freebsd-stable@freebsd.org
Message-ID: <C901C61A8023D94FD0DFBF27@[192.168.1.44]>
In-Reply-To: <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
References: <4BAA3409.6080406@ionic.co.uk>
<b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: clamav-milter 0.95.3 at juggler
X-Virus-Status: Clean
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 17:04:35 -0000
--On Wednesday, March 24, 2010 9:20 AM -0700 Freddie Cash
<fjwcash@gmail.com> wrote:
> On Wed, Mar 24, 2010 at 8:47 AM, Michal <michal@ionic.co.uk> wrote:
>
>> I wrote a really long e-mail but realised I could ask this question far
>> far easier, if it doesn't make sense, the original e-mail is bellow
>>
>> Can I use ZFS to create a multinode storage area. Multiple HDD's in
>> Multiple servers to create one target of, for example, //officestorage
>> Allowing me to expand the storage space when needed and clients being
>> able to retrieve data (like RAID0 but over devices not HDD)
>>
>> Here is an example I found which is where I'm getting some ideas from
>> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>>
>> Horribly, horribly, horribly complex. But, then, that's the Linux world.
> :)
>
> Server 1: bunch of disks exported via iSCSI
> Server 2: bunch of disks exported via iSCSI
> Server 3: bunch of disks exported via iSCSI
>
> "SAN" box: uses all those iSCSI exports to create a ZFS pool
>
> Use 1 iSCSI export from each server to create a raidz vdev. Or multiple
> mirror vdevs. When you need more storage, just add another server full of
> disks, export them via iSCSI to the "SAN" box, and expand the ZFS pool.
>
> And, if you need fail-over, on your "SAN" box, you can use HAST at the
> lower layers (currently only available in 9-CURRENT) to mirror the
> storage across two systems, and use CARP to provide a single IP for the
> two boxes.
If you were to do something like this, I'd make sure to have a fast local
ZIL (log) device on the head node. That would reduce latency for writes,
you might also do the same for reads. Then your bulk storage comes from
the iSCSI boxes.
Just a thought.
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 17:12:56 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DA3231065672
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:12:56 +0000 (UTC)
(envelope-from michal@ionic.co.uk)
Received: from mail1.sharescope.co.uk (pm1.ionic.co.uk [85.159.80.19])
by mx1.freebsd.org (Postfix) with ESMTP id 96E918FC18
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:12:56 +0000 (UTC)
Received: from localhost (unknown [127.0.0.1])
by mail1.sharescope.co.uk (Postfix) with ESMTP id AE3E7FC0AB
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:12:56 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sharescope.co.uk
Received: from mail1.sharescope.co.uk ([127.0.0.1])
by localhost (mail1.sharescope.co.uk [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id GQr4QdIyczBg for <freebsd-stable@freebsd.org>;
Wed, 24 Mar 2010 17:12:52 +0000 (GMT)
Received: from [192.168.2.37] (office.ionic.co.uk [85.159.85.2])
(Authenticated sender: chris@sharescope.co.uk)
by mail1.sharescope.co.uk (Postfix) with ESMTPSA id 772CCFC0A2
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:12:52 +0000 (GMT)
Message-ID: <4BAA4812.8070307@ionic.co.uk>
Date: Wed, 24 Mar 2010 17:12:50 +0000
From: Michal <michal@ionic.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <4BAA3409.6080406@ionic.co.uk>
<b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
In-Reply-To: <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 17:12:57 -0000
On 24/03/2010 16:20, Freddie Cash wrote:
Horribly, horribly, horribly complex. But, then, that's the Linux world.
> :)
Yes I know, it's not very clean, but was trying to gather ideas and I
found that
>
> Server 1: bunch of disks exported via iSCSI
> Server 2: bunch of disks exported via iSCSI
> Server 3: bunch of disks exported via iSCSI
>
> "SAN" box: uses all those iSCSI exports to create a ZFS pool
>
> Use 1 iSCSI export from each server to create a raidz vdev. Or multiple
> mirror vdevs. When you need more storage, just add another server full of
> disks, export them via iSCSI to the "SAN" box, and expand the ZFS pool.
>
> And, if you need fail-over, on your "SAN" box, you can use HAST at the lower
> layers (currently only available in 9-CURRENT) to mirror the storage across
> two systems, and use CARP to provide a single IP for the two boxes.
>
> ---------------------------------------------------------------------
This is pretty much what I have been looking for, I don't mind using a
SAN Controller server in which to deal with all of this in fact I
expected that, but I wanted to present the disks from a server full of
HDD's (which in effect is just a storage device) and then join them up.
I've briefly looked over RAIDz, will give it a good reading over later.
I'm thinking 6 disks in each server, and two raidz vdev created from 3
disks in each server. I can them serve them to the network. I've never
used ISCSI on FreeBSD however, I played with AOE on different *nix's so
I will give ISCSI a good looking over.
> Yes, you save space, but your throughput will be horribly horribly horribly
> low. RAID arrays should be narrow (1-9 disks), not wide (30+ disks), and
> then combined into a larger array (multiple small RAID6 arrays joined into a
> RAID0 stripe).
Oh Yes I agree, was doing some very crude calculations and the
difference in space was quite a lot, but no I would never do that in
reality
> If you were to do something like this, I'd make sure to have a fast
>local ZIL (log) device on the head node. That would reduce latency
>for writes, you might also do the same for reads. Then your bulk
>storage comes from the iSCSI boxes.
>
>Just a thought.
I've not come across ZIL so I think I will have to do my research
>At least in theory you could use geom_gate and zfs I suppose, never
>tried it though.
>ggatec(8), ggated(8) are your friends for that.
>
>Vince
Just had a look at ggatec, I've not seen or heard of that so I will
continue looking through that.
Many thanks to all, if I get something solid working I will be sure to
update the list with what will hopefully be a very cheap (other then
HDD's) SAN
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 17:14:16 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AC121106567A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:14:16 +0000 (UTC)
(envelope-from fjwcash@gmail.com)
Received: from mail-pz0-f196.google.com (mail-pz0-f196.google.com
[209.85.222.196])
by mx1.freebsd.org (Postfix) with ESMTP id 803708FC27
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:14:16 +0000 (UTC)
Received: by pzk34 with SMTP id 34so1051736pzk.3
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 10:14:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:content-type;
bh=Nnf/Ao03WytsMAEZqBZLcIEr1DzyDtr5y7j4qIFQ4s0=;
b=YPyXM+7qLkxnnwE97jOSJdEuKT9NiBCgj0J8wn3242WrvioNa4R7Fe+Tiv/JztP2cU
m13lKM1WibZB9mFPk+uLicx5mYupLKkPut8F+gn1mW0izW5KFlZ9h2vsbXuUnLlHhVPS
o4dh96UWIYUPvVMUbMsDaVbb+e9nGBHuaVnc0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
b=urFnEAsGoCuQOBzM3wlNTk3y8Tf5quxgGSwvdvrviDYcmhRYD1ZioFG2tvczIrXs+L
LKVFLd7IKM30QGjJw5Kb2PUtb7t65jqEFKOc8yX3eUikR5v6+rLK6PZiFVq7JWVYz1XQ
DpdCeDogWWY1wP7wZEzMk6YWoQJ8dcxh6Z604=
MIME-Version: 1.0
Received: by 10.141.15.17 with SMTP id s17mr5576596rvi.14.1269450854253; Wed,
24 Mar 2010 10:14:14 -0700 (PDT)
In-Reply-To: <C901C61A8023D94FD0DFBF27@192.168.1.44>
References: <4BAA3409.6080406@ionic.co.uk>
<b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
<C901C61A8023D94FD0DFBF27@192.168.1.44>
Date: Wed, 24 Mar 2010 10:14:14 -0700
Message-ID: <b269bc571003241014u3a97bf81v8e21742440bef8af@mail.gmail.com>
From: Freddie Cash <fjwcash@gmail.com>
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 17:14:16 -0000
On Wed, Mar 24, 2010 at 10:04 AM, Michael Loftis <mloftis@wgops.com> wrote:
> --On Wednesday, March 24, 2010 9:20 AM -0700 Freddie Cash <
> fjwcash@gmail.com> wrote:
> On Wed, Mar 24, 2010 at 8:47 AM, Michal <michal@ionic.co.uk> wrote:
>
>>
>> I wrote a really long e-mail but realised I could ask this question far
>>> far easier, if it doesn't make sense, the original e-mail is bellow
>>>
>>> Can I use ZFS to create a multinode storage area. Multiple HDD's in
>>> Multiple servers to create one target of, for example, //officestorage
>>> Allowing me to expand the storage space when needed and clients being
>>> able to retrieve data (like RAID0 but over devices not HDD)
>>>
>>> Here is an example I found which is where I'm getting some ideas from
>>> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>>>
>>> Horribly, horribly, horribly complex. But, then, that's the Linux world.
>>>
>> :)
>>
>> Server 1: bunch of disks exported via iSCSI
>> Server 2: bunch of disks exported via iSCSI
>> Server 3: bunch of disks exported via iSCSI
>>
>> "SAN" box: uses all those iSCSI exports to create a ZFS pool
>>
>> Use 1 iSCSI export from each server to create a raidz vdev. Or multiple
>> mirror vdevs. When you need more storage, just add another server full of
>> disks, export them via iSCSI to the "SAN" box, and expand the ZFS pool.
>>
>> And, if you need fail-over, on your "SAN" box, you can use HAST at the
>> lower layers (currently only available in 9-CURRENT) to mirror the
>> storage across two systems, and use CARP to provide a single IP for the
>> two boxes.
>>
>
> If you were to do something like this, I'd make sure to have a fast local
> ZIL (log) device on the head node. That would reduce latency for writes,
> you might also do the same for reads. Then your bulk storage comes from the
> iSCSI boxes.
>
Yes, that would be helpful (mirrored slogs, until we get slog removal
support).
As would an L2ARC (cache) device in the head node.
As well as lots and lots and lots of RAM.
And as fast of ethernet NICs as you can get between the head node and the
storage nodes.
And, and, and, and ... :)
--
Freddie Cash
fjwcash@gmail.com
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 17:18:51 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 79AA0106576E
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:18:51 +0000 (UTC)
(envelope-from mloftis@wgops.com)
Received: from juggler.wgops.com (juggler.wgops.com [204.11.247.41])
by mx1.freebsd.org (Postfix) with ESMTP id 5430E8FC17
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:18:51 +0000 (UTC)
Received: by juggler.wgops.com (Postfix, from userid 65534)
id E0DFDA80C9; Wed, 24 Mar 2010 11:18:50 -0600 (MDT)
X-Spam-ASN:
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on juggler.wgops.com
X-Spam-Level:
X-Spam-Status: No, score=-1.3 required=5.0 tests=ALL_TRUSTED,
SARE_SUB_OBFU_OTHER autolearn=no version=3.2.5
Received: from [192.168.1.44] (host-72-174-39-176.msl-mt.client.bresnan.net
[72.174.39.176])
by juggler.wgops.com (Postfix) with ESMTPSA id E5DC0A80C6
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 11:18:47 -0600 (MDT)
Date: Wed, 24 Mar 2010 11:18:51 -0600
From: Michael Loftis <mloftis@wgops.com>
To: freebsd-stable@freebsd.org
Message-ID: <6B439D7236FCE1188F74836F@[192.168.1.44]>
In-Reply-To: <4BAA4812.8070307@ionic.co.uk>
References: <4BAA3409.6080406@ionic.co.uk>
<b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
<4BAA4812.8070307@ionic.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: clamav-milter 0.95.3 at juggler
X-Virus-Status: Clean
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 17:18:51 -0000
--On Wednesday, March 24, 2010 5:12 PM +0000 Michal <michal@ionic.co.uk>
wrote:
>
>> If you were to do something like this, I'd make sure to have a fast
>> local ZIL (log) device on the head node. That would reduce latency
>> for writes, you might also do the same for reads. Then your bulk
>> storage comes from the iSCSI boxes.
>>
>> Just a thought.
>
> I've not come across ZIL so I think I will have to do my research
ZFS Intent Log, basically ZFS's WAL (Write Ahead Log) -- write committed to
the ZIL are considered durable, and the system then batches up ZIL writes
to normal storage. For reads there's the cache devices. I honestly do not
know the state of this in FreeBSD, I gave up using ZFS on FreeBSD for now
due to poor performance. Also the *linux* iSCSI kernel initiator is
*really* buggy, can't say anything about FreeBSD iSCSI initiator nor
target, nor anything about the Linux iSCSI target.
By using (fast) ZFS log and ZFS cache devices that are local to the 'san
head end' you can *greatly* increase the array's perceived/usable speed.
>
>
>> At least in theory you could use geom_gate and zfs I suppose, never
>> tried it though.
>> ggatec(8), ggated(8) are your friends for that.
>>
>> Vince
>
> Just had a look at ggatec, I've not seen or heard of that so I will
> continue looking through that.
>
>
> Many thanks to all, if I get something solid working I will be sure to
> update the list with what will hopefully be a very cheap (other then
> HDD's) SAN
>
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 17:20:07 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2017F106567B
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:20:07 +0000 (UTC)
(envelope-from fjwcash@gmail.com)
Received: from mail-iw0-f185.google.com (mail-iw0-f185.google.com
[209.85.223.185])
by mx1.freebsd.org (Postfix) with ESMTP id DAAD98FC16
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:20:06 +0000 (UTC)
Received: by iwn15 with SMTP id 15so2831848iwn.7
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 10:20:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:content-type;
bh=rGcjHmASP9vuHe11YVxHrBFz3JgiUEffezYJpWaLsSo=;
b=mC5d5eaitZlT1P8OnwB+bKraYrDT+IURVC77J8TqB7j3/wvZnCjuQspKhamqCu2pxK
/PbIhh527Lw7FMntE07qAPRaMJY+xPor6ggDEEKgxxjIAQEBzEusweGO++zvOI/SCc4A
7lQJZEpY3BPQ/qMmB8qKQDDwCZ2l8YqVKIUK8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
b=DbRIipUZ6eOdredndZqKEBLkBogDbD6nJciPLZh30X+mURlzgp2MuAcKPDR4oaod0s
S3NyGUc/WT1CiUpQ4NHCyopbxSdinJmdGo0revtOEZ9o8Zxm2jYnFEVC3YPDfFCsKEQp
g8QxJYoN5sosoSP3SsDqB2YkHsBDlSHwfGFSM=
MIME-Version: 1.0
Received: by 10.231.168.85 with SMTP id t21mr3705641iby.0.1269451206252; Wed,
24 Mar 2010 10:20:06 -0700 (PDT)
In-Reply-To: <4BAA4812.8070307@ionic.co.uk>
References: <4BAA3409.6080406@ionic.co.uk>
<b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
<4BAA4812.8070307@ionic.co.uk>
Date: Wed, 24 Mar 2010 10:20:05 -0700
Message-ID: <b269bc571003241020t41c97e57r9877aa8fdab7bcda@mail.gmail.com>
From: Freddie Cash <fjwcash@gmail.com>
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 17:20:07 -0000
On Wed, Mar 24, 2010 at 10:12 AM, Michal <michal@ionic.co.uk> wrote:
> This is pretty much what I have been looking for, I don't mind using a
> SAN Controller server in which to deal with all of this in fact I
> expected that, but I wanted to present the disks from a server full of
> HDD's (which in effect is just a storage device) and then join them up.
> I've briefly looked over RAIDz, will give it a good reading over later.
> I'm thinking 6 disks in each server, and two raidz vdev created from 3
> disks in each server. I can them serve them to the network. I've never
> used ISCSI on FreeBSD however, I played with AOE on different *nix's so
> I will give ISCSI a good looking over.
AFAIK, there's no ATA-over-Ethernet support in FreeBSD, leaving iSCSI as the
only "network block device" option.
Although, I guess one could use ggate to export the remote disks. Not sure
how that compares to iSCSI/AoE. Or where exactly in the storage stack that
works (below iSCSI/AoE??).
--
Freddie Cash
fjwcash@gmail.com
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 17:37:00 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B61ED106566C
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:37:00 +0000 (UTC)
(envelope-from michal@ionic.co.uk)
Received: from mail1.sharescope.co.uk (pm1.ionic.co.uk [85.159.80.19])
by mx1.freebsd.org (Postfix) with ESMTP id 71A4F8FC0A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:36:59 +0000 (UTC)
Received: from localhost (unknown [127.0.0.1])
by mail1.sharescope.co.uk (Postfix) with ESMTP id AAEC5FC0AB
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:37:00 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sharescope.co.uk
Received: from mail1.sharescope.co.uk ([127.0.0.1])
by localhost (mail1.sharescope.co.uk [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id Znd1F+PxxLAc for <freebsd-stable@freebsd.org>;
Wed, 24 Mar 2010 17:36:56 +0000 (GMT)
Received: from [192.168.2.37] (office.ionic.co.uk [85.159.85.2])
(Authenticated sender: chris@sharescope.co.uk)
by mail1.sharescope.co.uk (Postfix) with ESMTPSA id 4AF57FC0A2
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 17:36:56 +0000 (GMT)
Message-ID: <4BAA4DB6.80604@ionic.co.uk>
Date: Wed, 24 Mar 2010 17:36:54 +0000
From: Michal <michal@ionic.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <4BAA3409.6080406@ionic.co.uk> <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com> <C901C61A8023D94FD0DFBF27@192.168.1.44>
<b269bc571003241014u3a97bf81v8e21742440bef8af@mail.gmail.com>
In-Reply-To: <b269bc571003241014u3a97bf81v8e21742440bef8af@mail.gmail.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 17:37:00 -0000
On 24/03/2010 17:14, Freddie Cash wrote:
>
> Yes, that would be helpful (mirrored slogs, until we get slog removal
> support).
>
> As would an L2ARC (cache) device in the head node.
>
> As well as lots and lots and lots of RAM.
>
> And as fast of ethernet NICs as you can get between the head node and the
> storage nodes.
>
> And, and, and, and ... :)
>
As far as I know more RAM is more important the fast CPU, so RAM is the
order of the day, and I guess it depends what you think fast CPU is, but
I wasn't planning on a duel CPU or anything top of the range. I have
some duel core's knocking around...I think testing will show how
good/bad my calculations/assumptions are. Most are done in batched,
nightly and weekly so extremely fast isn't THAT important as we are
looking at device/server backup's and stored data which is moved off
servers once a week. At the minute we are not looking at 100 user file
system or anything along those lines.
For NICS I can sort out a Gb switch or some point-to-point Gb
connections betweeen the nodes, there is also the option is trying
getting some cheap fibre cards (I have a few laying around) and a cheap
fibre switch (something off ebay for testing might do) to have fibre
between the nodes. This however all goes out the water for trying to do
replication to other sites which are 100mb lines, but for the minute I
will focus on 1 location to stop it getting too complex. There are quite
a lot of hardware things which need to be done correctly, and yes I do
need to look at lots of other things. But stage one is just getting a
few Storage devices talking to a Storage controller and seeing if my
ideas work (improve IO, improved redundancy, easy to add storage)
Michael, I sort of understand what you are talking about with ZIL, but
not completely, so thanks for the pointers, there are clearly things I
have not thought about.
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 20:37:35 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 43BD1106564A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 20:37:35 +0000 (UTC)
(envelope-from fbsd2@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id 0563D8FC16
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 20:37:34 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2OKbJYF072375;
Wed, 24 Mar 2010 13:37:23 -0700 (PDT) (envelope-from fbsd2@sstec.com)
Message-Id: <5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
X-Sender:
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 24 Mar 2010 13:37:06 -0700
To: "Nenhum_de_Nos" <matheus@eternamente.info>, freebsd-stable@freebsd.org
From: John Long <fbsd2@sstec.com>
In-Reply-To: <a333ac6f65b2061fbc46994599f969ba.squirrel@lamneth>
References: <5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc:
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 20:37:35 -0000
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
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 20:45:23 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 72402106566B;
Wed, 24 Mar 2010 20:45:23 +0000 (UTC) (envelope-from fbsd2@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id 24E818FC1E;
Wed, 24 Mar 2010 20:45:22 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2OKjJpr072554;
Wed, 24 Mar 2010 13:45:22 -0700 (PDT) (envelope-from fbsd2@sstec.com)
Message-Id: <5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
X-Sender:
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 24 Mar 2010 13:45:06 -0700
To: Alexander Motin <mav@FreeBSD.org>
From: John Long <fbsd2@sstec.com>
In-Reply-To: <4BA85F46.9010306@FreeBSD.org>
References: <1269310984.00232724.1269300005@10.7.7.3>
<1269310984.00232724.1269300005@10.7.7.3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@FreeBSD.org>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 20:45:23 -0000
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
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 21:36:56 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 7B5DC106566B
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 21:36:56 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from qmta08.emeryville.ca.mail.comcast.net
(qmta08.emeryville.ca.mail.comcast.net [76.96.30.80])
by mx1.freebsd.org (Postfix) with ESMTP id 608358FC12
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 21:36:55 +0000 (UTC)
Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87])
by qmta08.emeryville.ca.mail.comcast.net with comcast
id x7FF1d00A1smiN4A89cwyd; Wed, 24 Mar 2010 21:36:56 +0000
Received: from koitsu.dyndns.org ([98.248.46.159])
by omta20.emeryville.ca.mail.comcast.net with comcast
id x9cv1d00c3S48mS8g9cwFn; Wed, 24 Mar 2010 21:36:56 +0000
Received: by icarus.home.lan (Postfix, from userid 1000)
id 8C0EA9B436; Wed, 24 Mar 2010 14:36:54 -0700 (PDT)
Date: Wed, 24 Mar 2010 14:36:54 -0700
From: Jeremy Chadwick <freebsd@jdc.parodius.com>
To: John Long <fbsd2@sstec.com>
Message-ID: <20100324213654.GA44288@icarus.home.lan>
References: <5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: freebsd-stable@freebsd.org, Nenhum_de_Nos <matheus@eternamente.info>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 21:36:56 -0000
On Wed, Mar 24, 2010 at 01:37:06PM -0700, John Long wrote:
> 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.
You're placing too many eggs in one basket. Hardware monitoring is a
separate beast, and one you won't find good support for on FreeBSD.
By "hardware monitoring" I'm talking about thermals off the mainboard,
fan RPMs, CPU temperature (not on-die temps), and voltages. Let's talk
about those first, as they're something I'm familiar with.
- These data sources are only available if the motherboard manufacturer
added a H/W monitoring I/C to their mainboard. Consumer mainboards
are spotty as far as offering this capability.
- Each mainboard is different. Each mainboard model, or even
subrevision, can use a completely different H/W monitoring chip. To
make matters more complex, there are multiple models of H/W monitoring
ICs, and even multiple revision/versions of the same model that behave
completely different than their predecessor(s).
- How this chip is implemented on the mainboard is up to the
manufacturer. Some chips only exist on the LPC bus (think ISA I/O
ports). Some chips support SMBus. The mainboard has to be engineered
so that the pins on the H/W IC tie in to the LPC or SMBus bus(ses). You
don't know which is available/used unless the manufacturer states such
in their User Manual.
- In the case of LPC, the exact I/O ports must be provided by the board
manufacturer. In the case of SMBus, the slave address must be
provided by the board manufacturer. **YOU CANNOT GUESS THESE** despite
Linux's lm-sensors project having folks think otherwise. Guessing
("probing") is very high risk, and involves submitting reads to a select
set of LPC I/O ports (which could be used for other things/devices), or
to a select SMBus slave address. Some registers do things to the system
(or associated chips) on read operations; bits can get reset. I've seen
this happen in the case of one Winbond chip where an incorrect CRxx read
resulted in the chips' watchdog firing an NMI.
- Knowing the exact model and subrevision of H/W IC is important, since
programmer of the monitoring software has to know what all the
register offsets are, how to decode the data, etc.. There is no
standard, and there are multiple manufacturers of such devices
(Nuvoton/Winbond, National Semiconductor, ON Semiconductor/Analog
Devices, SMSC, TI, and some others. For a while companies like AMD,
nVidia, Intel, Broadcom, ALi, and VIA were making their own chips as
well).
- In the case of SMBus, the operating system must have an SMBus driver
for the system chipset (not H/W chip). For example, Intel systems often
use ichsmb(4), AMD systems use amdsmb(4), and so on. Without a driver
it's not feasible/possible for userland applications to talk to a device
connected to SMBus. For sake of example, there's no SMBus driver on
FreeBSD for ServerWorks chipsets.
Getting all of this data out of the mainboard manufacturer is like
pulling teeth, especially in the case of consumer boards. Server board
manufacturers (Supermicro, Tyan, Intel, etc.) often disclose this
information to those who request it via Technical Support. But if you
were to mail, say, Asus for this information, it'd likely go in one ear
and out the other.
All that (negativity) said: the closest thing you'll find on FreeBSD to
interface with these chips is ports/sysutils/mbmon,
ports/sysutils/healthd, or ports/sysutils/bsdhwmon.
mbmon supports very old mainboards which utilise LPC (it's SMBus support
is broken/shoddy). It also tries auto-probing, often gets it wrong, and
spits out readings which are incorrect/off the charts. Sometimes it
gets things wrong and spits out values that look real but aren't.
healthd is basically mbmon with some minor changes to the core but major
changes to the surrounding user interface.
bsdhwmon is intended for servers only and only speaks to devices using
SMBus, of which I'm the author.
Are we having fun yet?
Now back to the bigger picture...
CPU temperature (assuming you have a newer AMD or Intel CPU) is
available via the coretemp(4) driver, and active CPU clock frequency is
available via the cpufreq(4) drivers and their subsets. There is also
some very archaic (IMHO) support for temperature monitoring via ACPI,
but I believe that's mainly intended for laptops. With regards to ACPI,
you're purely limited by what the mainboard/BIOS implementer does; many
consumer motherboard vendors have absolutely no idea what to do with a
technical support request asking they fix/improve their ACPI tables.
For coretemp(4), you'll find the thermals under dev.cpu.X.temperature
in sysctl.
For cpufreq(4), you'll find the available processor frequency levels
under dev.cpu.X.freq_levels and what the current frequency is in
dev.cpu.X.freq.
For est(4), there's dev.est.X.freq_settings but I'm not sure how to get
these to be used or how to tune them; keep reading.
> 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.
That's a very interesting opinion you have there. I continue to see
LGA775 chips sold regularly all over, and new stock coming in fairly
often to major resellers online.
The i3/i5/i7 chips don't appear to offer ECC framework on their memory
controllers (which are now on-die as I'm sure you know), which is why I
plan to stay away from them for servers. Intel's pushing Xeon for that,
which I'm not willing to switch to until the prices drop more. There
are existing C2D and C2Q CPUs which have the exact same capabilities and
features as their Xeon counterparts yet the Xeons cost $50-100 more.
It's like SCSI all over again.
If low-as-possible TDP is all you're concerned with, buy an Atom.
> 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.
What you probably want to look at is the source to all the subset
cpufreq(4) drivers that powerd(8) speaks to. See the cpufreq(4) man
page for details.
It seems most of us here -- myself included -- have very little
familiarity with how to get FreeBSD to use one subset driver or another
(e.g. est(4) vs. acpi_throttle(4), etc.). Someone recently clued me in
to how to switch from acpi_throttle to est on my Intel board which
*does* attach est(4) successfully, but I haven't bothered trying it
yet:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055665.html
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055666.html
The disabled=1 variables shown there are for loader.conf, by the way,
and require a reboot after adjusting.
I'd give you links to the main thread, but Dan Naumov's mail client
doesn't appear to have Reference-Id header support so every reply of
his appears as a "new" entry in the thread list. Search for "powerd on
8.0, is it considered safe?" here:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/thread.html
> est appears to be not working but what would happen if it were
> working?
It should lower the clock frequency of the CPU during idle times, and
increase it during load. **HOW** it goes about adjusting the frequency
is where the different subset drivers come into play.
The attachment "error 6" message you see usually indicates the est(4)
driver doesn't have support for you specific model of CPU based on its
capabilities, or at least that's how I understand it. John Baldwin (I
think?) or Nate Lawson might have to chime in here.
You're not the first one to report this issue. It comes up fairly
often. Possibly since you're digging into the code you'd like to take
up maintaining these pieces?
> 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.
This is a bug/quirk of some changes in ata(4). Your drive should be
operating at full SATA speed (probably SATA300). You can bring this up
in another thread if you want, but it's purely cosmetic as far as I
know. atacontrol(8) and diskinfo(8) -t and -c will come in handy.
--
| Jeremy Chadwick jdc@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 22:03:36 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5038D106564A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 22:03:36 +0000 (UTC)
(envelope-from alteriks@gmail.com)
Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com
[209.85.220.224])
by mx1.freebsd.org (Postfix) with ESMTP id D74DB8FC22
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 22:03:35 +0000 (UTC)
Received: by fxm24 with SMTP id 24so2608928fxm.3
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 15:03:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type;
bh=q+7IyDjfJOPP9luZ9rzeby1cfx1IguEFF940Wxim948=;
b=mLcpvDwat/GsgzznnxgMf3ZGh3/uOQsL4f21msBrIYTpx4vnUSu2J9NtjhAIgd1dQL
GhECZjYmEX0EHJnXvGeO/9coWQiYrOTfUVTMScwsNxkCKd/7fbMN0nbfQcEaiZpG/gW/
lLwbklrI4WYD+dmbp0ySmk6nHr9CrMhcLmKbI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
b=QHxpNCFsXZKojtm6rvKZodchYNLaZ7hgkHEpF/n8/hST7AQRJfVpVc1163m2ADuirX
zsIav63Fby4zIpiSdnQwz9NOTWg87P+AYGb6enEWrifjc25aZKMkScQiffUMWqRzno25
BOCvcNJm061q0pzOAaUKsbulgjj2xGwMDcezM=
MIME-Version: 1.0
Received: by 10.103.4.4 with SMTP id g4mr3001779mui.80.1269468214651; Wed, 24
Mar 2010 15:03:34 -0700 (PDT)
In-Reply-To: <20100324213906.GA45252@icarus.home.lan>
References: <cf9b1ee01003220413t14a75e95pc4acf072f876ac64@mail.gmail.com>
<684e57ec1003221341s241c6d4fl9f2afa411c55d697@mail.gmail.com>
<20100324084923.GA27740@icarus.home.lan>
<684e57ec1003241430p7eeba4cbrc81300cd44ab9eb9@mail.gmail.com>
<20100324213906.GA45252@icarus.home.lan>
Date: Wed, 24 Mar 2010 22:03:34 +0000
Message-ID: <684e57ec1003241503m5e905646g7e99403fc5d27901@mail.gmail.com>
From: Krzysztof Dajka <alteriks@gmail.com>
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-stable@freebsd.org
Subject: Re: Can't boot after make installworld
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 22:03:36 -0000
Thanks a lot for clarifying. I think that I'm going to stick with
STABLE release, as it reflects my expectations and time I can dedicate
to tinker with my system.
For some while I thought that I would return to Debian, because I
became used to it's pros and cons. Thanks to experience I gained in
few months in FreeBSD land I didn't think about Debian in GNU/Linux
incarnation, but at least Debian/kFreeBSD. Unfortunately as of today
Debian/kFreeBSD doesn't support booting from zfs. I think that it was
good idea to migrate to FreeBSD, as for now I'm missing fast upgrades
and deployment which are Debian assets, but I'm getting used to ports
and possibility of tuning system.
I've read thread
http://lists.freebsd.org/pipermail/freebsd-fs/2010-March/007956.html,
PJD is suggesting to enable few options in kernel:
> options WITNESS
> options WITNESS_SKIPSPIN
> options INVARIANTS
> options INVARIANT_SUPPORT
> options DEBUG_VFS_LOCKS
> options DEBUG_LOCKS
> options KDB
> options DDB
Is there something else I should turn on in kernel before running
bonnie++ which will surely crash my system? And one more question is
there a way to build new kernel which would be called ie kernel_debug
which I would load only when needed?
On
3/24/10, Jeremy Chadwick <freebsd@jdc.parodius.com> wrote:
>Since you replied to Mark and I personally -- can you send a copy of
>this mail back to the mailing list? Others should be able to help
>answer the above questions; in this case, more eyes = good. :-)
Sorry about that sending mails not to everyone happens to me all the time ;)
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 22:19:54 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CCC5E1065672
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 22:19:54 +0000 (UTC)
(envelope-from freebsd-stable@m.gmane.org)
Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])
by mx1.freebsd.org (Postfix) with ESMTP id 5A19D8FC0A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 22:19:54 +0000 (UTC)
Received: from list by lo.gmane.org with local (Exim 4.69)
(envelope-from <freebsd-stable@m.gmane.org>) id 1NuYvK-0000uF-5H
for freebsd-stable@freebsd.org; Wed, 24 Mar 2010 23:19:38 +0100
Received: from 78-1-170-106.adsl.net.t-com.hr ([78.1.170.106])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 23:19:38 +0100
Received: from ivoras by 78-1-170-106.adsl.net.t-com.hr with local (Gmexim 0.1
(Debian)) id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 23:19:38 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-stable@freebsd.org
From: Ivan Voras <ivoras@freebsd.org>
Date: Wed, 24 Mar 2010 23:19:16 +0100
Lines: 45
Message-ID: <hoe355$tuk$1@dough.gmane.org>
References: <4BAA3409.6080406@ionic.co.uk>
<b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: 78-1-170-106.adsl.net.t-com.hr
User-Agent: Thunderbird 2.0.0.21 (X11/20090612)
In-Reply-To: <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 22:19:54 -0000
Freddie Cash wrote:
> On Wed, Mar 24, 2010 at 8:47 AM, Michal <michal@ionic.co.uk> wrote:
>
>> I wrote a really long e-mail but realised I could ask this question far
>> far easier, if it doesn't make sense, the original e-mail is bellow
>>
>> Can I use ZFS to create a multinode storage area. Multiple HDD's in
>> Multiple servers to create one target of, for example, //officestorage
>> Allowing me to expand the storage space when needed and clients being
>> able to retrieve data (like RAID0 but over devices not HDD)
>>
>> Here is an example I found which is where I'm getting some ideas from
>> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>>
>> Horribly, horribly, horribly complex. But, then, that's the Linux world.
> :)
>
> Server 1: bunch of disks exported via iSCSI
> Server 2: bunch of disks exported via iSCSI
> Server 3: bunch of disks exported via iSCSI
>
> "SAN" box: uses all those iSCSI exports to create a ZFS pool
For what it's worth - I think this is a good idea! iSCSI and ZFS make it
extraordinarily flexible to do this. You can have a RAIS - redundant
array of inexpensive servers :)
For example: each server box hosts 8-12 drives - use a hardware
controller with RAID6 and a BBU to create a single volume (if FreeBSD
booting issues allow, but that can be worked around). Export this volume
via iSCSI. Repeat for the rest of the servers. Then, on the client,
create a RAIDZ. or if you trust your setup that much. a straight striped
ZFS volume. If you do it the RAIDZ way, one of your storage servers can
fail completely.
As you need more space, add more servers in batches of three (if you did
RAIDZ, else the number doesn't matter), add them to the client as usual.
The "client" in this case can be a file server, and you can achieve
failover between several of those by using e.g. carp, heartbeat, etc. -
if the master node fails, some other one can reconstitute the ZFS pool
ad make it available.
But, you need very fast links between the nodes, and I wouldn't use
something like this without extensively testing the failure modes.
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 22:30:26 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 684A1106564A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 22:30:25 +0000 (UTC)
(envelope-from 000.fbsd@quip.cz)
Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4])
by mx1.freebsd.org (Postfix) with ESMTP id 272368FC0C
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 22:30:24 +0000 (UTC)
Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1])
by elsa.codelab.cz (Postfix) with ESMTP id C4E2619E02A;
Wed, 24 Mar 2010 23:30:23 +0100 (CET)
Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by elsa.codelab.cz (Postfix) with ESMTPSA id B323C19E023;
Wed, 24 Mar 2010 23:30:20 +0100 (CET)
Message-ID: <4BAA927C.802@quip.cz>
Date: Wed, 24 Mar 2010 23:30:20 +0100
From: Miroslav Lachman <000.fbsd@quip.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3
MIME-Version: 1.0
To: Michal <michal@ionic.co.uk>
References: <4BAA3409.6080406@ionic.co.uk> <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com> <C901C61A8023D94FD0DFBF27@192.168.1.44> <b269bc571003241014u3a97bf81v8e21742440bef8af@mail.gmail.com>
<4BAA4DB6.80604@ionic.co.uk>
In-Reply-To: <4BAA4DB6.80604@ionic.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 22:30:26 -0000
Michal wrote:
> On 24/03/2010 17:14, Freddie Cash wrote:
>
>>
>> Yes, that would be helpful (mirrored slogs, until we get slog removal
>> support).
>>
>> As would an L2ARC (cache) device in the head node.
>>
>> As well as lots and lots and lots of RAM.
>>
>> And as fast of ethernet NICs as you can get between the head node and the
>> storage nodes.
>>
>> And, and, and, and ... :)
>>
>
> As far as I know more RAM is more important the fast CPU, so RAM is the
> order of the day, and I guess it depends what you think fast CPU is, but
> I wasn't planning on a duel CPU or anything top of the range. I have
> some duel core's knocking around...
Any modern multicore CPU will be fine. And more RAM you have, the larger
ARC / prefetch will be used (more read speed you will gain)
> Michael, I sort of understand what you are talking about with ZIL, but
> not completely, so thanks for the pointers, there are clearly things I
> have not thought about.
This links can be useful to you
ZFS L2ARC
http://blogs.sun.com/brendan/entry/test
ZFS Evil Tuning Guide
http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Disabling_the_ZIL_.28Don.27t.29
ZFS ZIL + L2ARC SSD Setup
http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg34674.html
Miroslav Lachman
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 23:45:32 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 29CCF106564A
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 23:45:32 +0000 (UTC)
(envelope-from michal@ionic.co.uk)
Received: from mail1.sharescope.co.uk (pm1.ionic.co.uk [85.159.80.19])
by mx1.freebsd.org (Postfix) with ESMTP id DBECC8FC17
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 23:45:31 +0000 (UTC)
Received: from localhost (unknown [127.0.0.1])
by mail1.sharescope.co.uk (Postfix) with ESMTP id 5AC85FC0AB
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 23:45:32 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sharescope.co.uk
Received: from mail1.sharescope.co.uk ([127.0.0.1])
by localhost (mail1.sharescope.co.uk [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id KnDqwol4+5dd for <freebsd-stable@freebsd.org>;
Wed, 24 Mar 2010 23:45:28 +0000 (GMT)
Received: from [192.168.2.37] (office.ionic.co.uk [85.159.85.2])
(Authenticated sender: chris@sharescope.co.uk)
by mail1.sharescope.co.uk (Postfix) with ESMTPSA id 1A84AFC0A2
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 23:45:28 +0000 (GMT)
Message-ID: <4BAAA415.1000804@ionic.co.uk>
Date: Wed, 24 Mar 2010 23:45:25 +0000
From: Michal <michal@ionic.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <4BAA3409.6080406@ionic.co.uk> <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
<hoe355$tuk$1@dough.gmane.org>
In-Reply-To: <hoe355$tuk$1@dough.gmane.org>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 23:45:32 -0000
On 24/03/2010 22:19, Ivan Voras wrote:
>
> For what it's worth - I think this is a good idea! iSCSI and ZFS make it
> extraordinarily flexible to do this. You can have a RAIS - redundant
> array of inexpensive servers :)
>
> For example: each server box hosts 8-12 drives - use a hardware
> controller with RAID6 and a BBU to create a single volume (if FreeBSD
> booting issues allow, but that can be worked around). Export this volume
> via iSCSI. Repeat for the rest of the servers. Then, on the client,
> create a RAIDZ. or if you trust your setup that much. a straight striped
> ZFS volume. If you do it the RAIDZ way, one of your storage servers can
> fail completely.
>
> As you need more space, add more servers in batches of three (if you did
> RAIDZ, else the number doesn't matter), add them to the client as usual.
>
> The "client" in this case can be a file server, and you can achieve
> failover between several of those by using e.g. carp, heartbeat, etc. -
> if the master node fails, some other one can reconstitute the ZFS pool
> ad make it available.
>
> But, you need very fast links between the nodes, and I wouldn't use
> something like this without extensively testing the failure modes.
>
I do aswell :D The thing is, I see it two ways; I worked for a a huge
online betting company, and we had the money for HP MSA's and big
expensive SAN's, then we have a lot of SMB's with no where near the
budget for that but the same problem with lots of data and the need for
backend storage for databases. It's all well and good having 1 ZFS
server, but it's fragile in the the sense of no redundancy, then we have
1 ZFS server and a 2nd with DRBD, but that's a waste of money...think 12
TB, and you need to pay for another 12TB box for redundancy, and you are
still looking at 1 server. I am thinking a cheap solution but one that
has IO throughput, redundancy and is easy to manange and expand across
multiple nodes
A "NAS" based solution...one based on a single NAS device which has
single targets //nas1 //nas2 etc is ok, but has many problems. A "SAN"
based solution can overcome these, it does add cost, but the amount can
be minimised. I'll work on it over the next few days and get some notes
typed up as well as some run some performance numbers. I'll try and do
it modular by adding more RAM and sorting our ZLS and cache, comparing
how they effect performance
From owner-freebsd-stable@FreeBSD.ORG Wed Mar 24 23:47:14 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4F256106567B;
Wed, 24 Mar 2010 23:47:14 +0000 (UTC)
(envelope-from ohartman@mail.zedat.fu-berlin.de)
Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de
[130.133.4.66])
by mx1.freebsd.org (Postfix) with ESMTP id CB5308FC1A;
Wed, 24 Mar 2010 23:47:13 +0000 (UTC)
Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69])
by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp
(envelope-from <ohartman@mail.zedat.fu-berlin.de>)
id <1NuaI4-0000aU-Se>; Thu, 25 Mar 2010 00:47:12 +0100
Received: from e178057006.adsl.alicedsl.de ([85.178.57.6]
helo=thor.walstatt.dyndns.org)
by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa
(envelope-from <ohartman@mail.zedat.fu-berlin.de>)
id <1NuaI4-0001nS-Pt>; Thu, 25 Mar 2010 00:47:12 +0100
Message-ID: <4BAAA480.5060307@mail.zedat.fu-berlin.de>
Date: Thu, 25 Mar 2010 00:47:12 +0100
From: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
rv:1.9.1.8) Gecko/20100308 Thunderbird/3.0.3
MIME-Version: 1.0
To: gary.jennejohn@freenet.de
References: <4BAA1478.9020201@zedat.fu-berlin.de>
<20100324150653.3a447c98@ernst.jennejohn.org>
In-Reply-To: <20100324150653.3a447c98@ernst.jennejohn.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: 85.178.57.6
Cc: freebsd-stable@freebsd.org, "O. Hartmann" <ohartman@zedat.fu-berlin.de>,
freebsd-questions@freebsd.org, freebsd-ports@freebsd.org
Subject: Re: Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon
graphics on FBSD 8.0-STABLE SMP/sm64 box
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 23:47:14 -0000
On 03/24/10 15:06, Gary Jennejohn wrote:
> On Wed, 24 Mar 2010 13:32:40 +0000
> "O. Hartmann"<ohartman@zedat.fu-berlin.de> wrote:
>
>> Since the introduction of Thunderbird 3.0 and Firefox 3.6 I see
>> spontanous crashes/coredumps of both thunderbird and firefox. Interingly
>> Firefox 3.5.X works well on he same platform.
>>
>> The platform is a FreeBSD 8.0-STABLE/amd64 (r205536: Tue Mar 23 22:19:04
>> CET 2010), SMP box with 8GB of RAM, QuadCore Intel Q6600 on a P35-based
>> motherboard.
>>
>> Thunderbird 3 crashes rarely compared to Firefox 3. The longer the
>> application thunderbird runs, the higher the likelyhood the app crashes
>> and vanishes. Sometimes this happens immediately after starting
>> thunderbird, sometimes it takes its few minutes or half an hour.
>>
>> Firefox 3 is sensitive to its pull-down menus or requester showing up in
>> some situations. I can provoke a crash by clicking onto a pull-down-menu
>> in firefox 3, it immediately dumps a core.
>>
>
> If you suspect the graphics card's driver is at fault then I would try
> linux-opera or even linux-firefox and see whether it also dies when you
> use a drop-down menu.
>
> Another possibility would be to set hw.physmem to say 3G or 4G in
> loader.conf and see whether that affects thunderbird/firefox. Who
> knows, there may some weird problem caused by all that memory? That
> would a fairly quick and cheap way to test this.
>
> --
> Gary Jennejohn
You're right, I'll test this as soon as I'm back in my lab.
Oliver Hartmann
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 00:33:42 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 76D3D106564A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 00:33:42 +0000 (UTC)
(envelope-from ben@morrow.me.uk)
Received: from relay.ptn-ipout02.plus.net (relay.ptn-ipout02.plus.net
[212.159.7.36]) by mx1.freebsd.org (Postfix) with ESMTP id 16DE98FC0C
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 00:33:41 +0000 (UTC)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFZMqkvUOFPl/2dsb2JhbACbG3PABIR+BA
Received: from plesk-mail01.plus.net ([212.56.83.229])
by relay.ptn-ipout02.plus.net with ESMTP; 25 Mar 2010 00:33:40 +0000
Received: (qmail 18494 invoked from network); 25 Mar 2010 00:33:38 +0000
Received: from host86-142-60-221.range86-142.btcentralplus.com (HELO
osiris.mauzo.dyndns.org) (86.142.60.221)
by plesk-mail01.plus.net with SMTP; 25 Mar 2010 00:33:36 +0000
Received: (qmail 4736 invoked by uid 1001); 25 Mar 2010 00:33:35 -0000
Date: Thu, 25 Mar 2010 00:33:35 +0000
From: Ben Morrow <ben@morrow.me.uk>
To: michal@ionic.co.uk, freebsd-stable@freebsd.org
Message-ID: <20100325003335.GA4691@osiris.mauzo.dyndns.org>
References: <4BAA3409.6080406@ionic.co.uk>
<b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
<hoe355$tuk$1@dough.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BAAA415.1000804@ionic.co.uk>
X-Newsgroups: gmane.os.freebsd.stable
Organization: Who, me?
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc:
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 00:33:42 -0000
Quoth Michal <michal@ionic.co.uk>:
>
> I do aswell :D The thing is, I see it two ways; I worked for a a huge
> online betting company, and we had the money for HP MSA's and big
> expensive SAN's, then we have a lot of SMB's with no where near the
> budget for that but the same problem with lots of data and the need for
> backend storage for databases. It's all well and good having 1 ZFS
> server, but it's fragile in the the sense of no redundancy, then we have
> 1 ZFS server and a 2nd with DRBD, but that's a waste of money...think 12
> TB, and you need to pay for another 12TB box for redundancy, and you are
> still looking at 1 server. I am thinking a cheap solution but one that
> has IO throughput, redundancy and is easy to manange and expand across
> multiple nodes
If you do it right, you could have the 'SAN' box be one of the boxes
full of discs, with some or all of the others able to take over the
'SAN' role if it fails. That way you get redundancy without having to
have a machine sit idle. (You're still using more discs than you
strictly need to hold that much data, of course, but you can't avoid
that.)
Ben
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 01:06:46 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CFC7C106566B
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 01:06:46 +0000 (UTC)
(envelope-from fbsd2@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id 61DEA8FC08
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 01:06:46 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2P16WjX078194;
Wed, 24 Mar 2010 18:06:35 -0700 (PDT) (envelope-from fbsd2@sstec.com)
Message-Id: <5.2.1.1.2.20100324165115.03159ab8@mail.sstec.com>
X-Sender:
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 24 Mar 2010 18:04:51 -0700
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
From: John Long <fbsd2@sstec.com>
In-Reply-To: <20100324213654.GA44288@icarus.home.lan>
References: <5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: freebsd-stable@freebsd.org, Nenhum_de_Nos <matheus@eternamente.info>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 01:06:46 -0000
At 02:36 PM 3/24/2010, Jeremy Chadwick wrote:
>On Wed, Mar 24, 2010 at 01:37:06PM -0700, John Long wrote:
>> 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.
>
>You're placing too many eggs in one basket. Hardware monitoring is a
>separate beast, and one you won't find good support for on FreeBSD.
>By "hardware monitoring" I'm talking about thermals off the mainboard,
>fan RPMs, CPU temperature (not on-die temps), and voltages. Let's talk
>about those first, as they're something I'm familiar with.
>
>- These data sources are only available if the motherboard manufacturer
>added a H/W monitoring I/C to their mainboard. Consumer mainboards
>are spotty as far as offering this capability.
>
>- Each mainboard is different. Each mainboard model, or even
>subrevision, can use a completely different H/W monitoring chip. To
>make matters more complex, there are multiple models of H/W monitoring
>ICs, and even multiple revision/versions of the same model that behave
>completely different than their predecessor(s).
>
>- How this chip is implemented on the mainboard is up to the
>manufacturer. Some chips only exist on the LPC bus (think ISA I/O
>ports). Some chips support SMBus. The mainboard has to be engineered
>so that the pins on the H/W IC tie in to the LPC or SMBus bus(ses). You
>don't know which is available/used unless the manufacturer states such
>in their User Manual.
>
>- In the case of LPC, the exact I/O ports must be provided by the board
>manufacturer. In the case of SMBus, the slave address must be
>provided by the board manufacturer. **YOU CANNOT GUESS THESE** despite
>Linux's lm-sensors project having folks think otherwise. Guessing
>("probing") is very high risk, and involves submitting reads to a select
>set of LPC I/O ports (which could be used for other things/devices), or
>to a select SMBus slave address. Some registers do things to the system
>(or associated chips) on read operations; bits can get reset. I've seen
>this happen in the case of one Winbond chip where an incorrect CRxx read
>resulted in the chips' watchdog firing an NMI.
>
>- Knowing the exact model and subrevision of H/W IC is important, since
>programmer of the monitoring software has to know what all the
>register offsets are, how to decode the data, etc.. There is no
>standard, and there are multiple manufacturers of such devices
>(Nuvoton/Winbond, National Semiconductor, ON Semiconductor/Analog
>Devices, SMSC, TI, and some others. For a while companies like AMD,
>nVidia, Intel, Broadcom, ALi, and VIA were making their own chips as
>well).
>
>- In the case of SMBus, the operating system must have an SMBus driver
>for the system chipset (not H/W chip). For example, Intel systems often
>use ichsmb(4), AMD systems use amdsmb(4), and so on. Without a driver
>it's not feasible/possible for userland applications to talk to a device
>connected to SMBus. For sake of example, there's no SMBus driver on
>FreeBSD for ServerWorks chipsets.
>
>Getting all of this data out of the mainboard manufacturer is like
>pulling teeth, especially in the case of consumer boards. Server board
>manufacturers (Supermicro, Tyan, Intel, etc.) often disclose this
>information to those who request it via Technical Support. But if you
>were to mail, say, Asus for this information, it'd likely go in one ear
>and out the other.
>
>All that (negativity) said: the closest thing you'll find on FreeBSD to
>interface with these chips is ports/sysutils/mbmon,
>ports/sysutils/healthd, or ports/sysutils/bsdhwmon.
>
>mbmon supports very old mainboards which utilise LPC (it's SMBus support
>is broken/shoddy). It also tries auto-probing, often gets it wrong, and
>spits out readings which are incorrect/off the charts. Sometimes it
>gets things wrong and spits out values that look real but aren't.
>
>healthd is basically mbmon with some minor changes to the core but major
>changes to the surrounding user interface.
>
>bsdhwmon is intended for servers only and only speaks to devices using
>SMBus, of which I'm the author.
>
>Are we having fun yet?
>
>Now back to the bigger picture...
>
>CPU temperature (assuming you have a newer AMD or Intel CPU) is
>available via the coretemp(4) driver, and active CPU clock frequency is
>available via the cpufreq(4) drivers and their subsets. There is also
>some very archaic (IMHO) support for temperature monitoring via ACPI,
>but I believe that's mainly intended for laptops. With regards to ACPI,
>you're purely limited by what the mainboard/BIOS implementer does; many
>consumer motherboard vendors have absolutely no idea what to do with a
>technical support request asking they fix/improve their ACPI tables.
>
>For coretemp(4), you'll find the thermals under dev.cpu.X.temperature
>in sysctl.
>
>For cpufreq(4), you'll find the available processor frequency levels
>under dev.cpu.X.freq_levels and what the current frequency is in
>dev.cpu.X.freq.
>
>For est(4), there's dev.est.X.freq_settings but I'm not sure how to get
>these to be used or how to tune them; keep reading.
I want to thank you very much for all the info you have provided. It has
clued me into a much better understanding and I see that it is a big
un-standard thing to monitor these functions. It seems that things are
actually working well with this system and I am chasing diminishing returns.
Let me just add this link for others that are on a path of understanding re
eist/est/powerd etc..
http://www.techarp.com/showarticle.aspx?artno=420&pgno=1 All power states
defined and link to acpi docs.
>
>> 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.
>
>That's a very interesting opinion you have there. I continue to see
>LGA775 chips sold regularly all over, and new stock coming in fairly
>often to major resellers online.
Knowing of the problems with h55 and bsd etc while needing to update both
my servers (k6-3 antiques from 1998 plus I have to get ready for the DNSSEC
changeover coming soon - run my own dns), I have been trying to catch the
Frys specials for a couple months on the Eseries c2d mdb and chip combos. 2
weeks ago I caught the hint that they were blowing all 775 stuff out, Frys
employee verified that, Intel's orders. Frys is big, Intel is not making
anymore 775 chips and when they are gone then only few online will have it.
They are going fast, On Saturday Frys (Woodland hills) had 25 E7500s, they
had a E7500 and mbd sale on monday and another today. I doubt they have
anymore other than open box now. They blew out all other 775 chips they had
prior to monday (e3400 last wk, 6300 prior). They may have some Q or E8200
etc but they may have another sale if so. It will not be long before newegg
and others are out of stock and cost will go way up. They want to push
everyone into the I-series. Wait and see..
>
>The i3/i5/i7 chips don't appear to offer ECC framework on their memory
>controllers (which are now on-die as I'm sure you know), which is why I
>plan to stay away from them for servers. Intel's pushing Xeon for that,
>which I'm not willing to switch to until the prices drop more. There
>are existing C2D and C2Q CPUs which have the exact same capabilities and
>features as their Xeon counterparts yet the Xeons cost $50-100 more.
>It's like SCSI all over again.
>
I agree with your thoughts however I believe one can still use the I-series
in a p55 board and get the ECC working but then you need to use a separate
video bd and the TDP is going to be about 30+ watts higher than using a g41
or such mbd and 775 chip.
>If low-as-possible TDP is all you're concerned with, buy an Atom.
Atom is about half the perf of a c2d especially if c2d is oc'd. An Atom in
a gclf945 mbd is about 35 watts because of the old 945 chip is 130nm tech.
Atom in Nvidia mdb would be way to go but c2d is still much faster. I get
41 watts with E7500, G41 mbd w/ video, 1 GB mem and 1 TB WD cavier HD
including losses thru power supply (antec 380 green -80 plus bronze,
smallest 80 plus handy). 24/7/365 is $1.00 per watt at my current rate of
8.5c / KWhr per year. Save 20 watts is saving $20.00 or more per year plus
I am set up for running on batteries and going solar. Do not discount the
problems in the economy. I run a truth website (netctr.com), things are not
as we are told by tptb.
>
>> 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.
>
>What you probably want to look at is the source to all the subset
>cpufreq(4) drivers that powerd(8) speaks to. See the cpufreq(4) man
>page for details.
I followed that and quite a bit more, it looks to be too much for just I to
handle with my constraints of duty and time.
>
>It seems most of us here -- myself included -- have very little
>familiarity with how to get FreeBSD to use one subset driver or another
>(e.g. est(4) vs. acpi_throttle(4), etc.). Someone recently clued me in
>to how to switch from acpi_throttle to est on my Intel board which
>*does* attach est(4) successfully, but I haven't bothered trying it
>yet:
>
>http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055665.html
>http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055666.html
>
>The disabled=1 variables shown there are for loader.conf, by the way,
>and require a reboot after adjusting.
>
>I'd give you links to the main thread, but Dan Naumov's mail client
>doesn't appear to have Reference-Id header support so every reply of
>his appears as a "new" entry in the thread list. Search for "powerd on
>8.0, is it considered safe?" here:
>
>http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/thread.html
I read all that and much more for several years back in my archives (I keep
about 11 years of mailists in my system here). I figured it was a nebulous
quest without more info. Now I see it is more then I need to byte off :-)
>
>> est appears to be not working but what would happen if it were
>> working?
>
>It should lower the clock frequency of the CPU during idle times, and
>increase it during load. **HOW** it goes about adjusting the frequency
>is where the different subset drivers come into play.
>
>The attachment "error 6" message you see usually indicates the est(4)
>driver doesn't have support for you specific model of CPU based on its
>capabilities, or at least that's how I understand it. John Baldwin (I
>think?) or Nate Lawson might have to chime in here.
>
>You're not the first one to report this issue. It comes up fairly
>often. Possibly since you're digging into the code you'd like to take
>up maintaining these pieces?
I appreciate the offer but I think it is more than I can chew right now :-)
I was just trying to find out how all this was supposed to work in the proper.
>> 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.
>
>This is a bug/quirk of some changes in ata(4). Your drive should be
>operating at full SATA speed (probably SATA300). You can bring this up
>in another thread if you want, but it's purely cosmetic as far as I
>know. atacontrol(8) and diskinfo(8) -t and -c will come in handy.
Moving this to another thread for there are some unknowns here.
>
>--
>| Jeremy Chadwick jdc@parodius.com |
>| Parodius Networking http://www.parodius.com/ |
>| UNIX Systems Administrator Mountain View, CA, USA |
>| Making life hard for others since 1977. PGP: 4BD6C0CB |
Thanks much again,
John
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 01:48:51 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 776A3106564A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 01:48:51 +0000 (UTC)
(envelope-from fullermd@over-yonder.net)
Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44])
by mx1.freebsd.org (Postfix) with ESMTP id 4AED28FC15
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 01:48:50 +0000 (UTC)
Received: from draco.over-yonder.net (c-75-64-226-141.hsd1.ms.comcast.net
[75.64.226.141])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by thyme.infocus-llc.com (Postfix) with ESMTPSA id 99EAE37B43C;
Wed, 24 Mar 2010 20:48:49 -0500 (CDT)
Received: by draco.over-yonder.net (Postfix, from userid 100)
id A9F8B61C41; Wed, 24 Mar 2010 20:48:48 -0500 (CDT)
Date: Wed, 24 Mar 2010 20:48:48 -0500
From: "Matthew D. Fuller" <fullermd@over-yonder.net>
To: John Long <fbsd2@sstec.com>
Message-ID: <20100325014848.GW62031@over-yonder.net>
References: <5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
<5.2.1.1.2.20100324165115.03159ab8@mail.sstec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.2.1.1.2.20100324165115.03159ab8@mail.sstec.com>
X-Editor: vi
X-OS: FreeBSD <http://www.freebsd.org/>
User-Agent: Mutt/1.5.20-fullermd.4 (2009-06-14)
X-Virus-Scanned: clamav-milter 0.95.3 at thyme.infocus-llc.com
X-Virus-Status: Clean
Cc: freebsd-stable@freebsd.org, Jeremy Chadwick <freebsd@jdc.parodius.com>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 01:48:51 -0000
On Wed, Mar 24, 2010 at 06:04:51PM -0700 I heard the voice of
John Long, and lo! it spake thus:
>
>> The i3/i5/i7 chips don't appear to offer ECC framework on their
>> memory controllers (which are now on-die as I'm sure you know),
>> which is why I plan to stay away from them for servers.
>
> I agree with your thoughts however I believe one can still use the
> I-series in a p55 board and get the ECC working
Not the case. To use ECC, the memory controller has to support it.
Nehalem moved the memory controller on-die, and on the non-Xeons, it
doesn't have ECC capability. You'd have to go Xeon, use prior chips
(with the memory controller on the motherboard) with careful
motherboard selection, or use AMD (where all the chips have ECC in the
IMC, though you still need a little care to be sure your motherboard
doesn't sabotage it).
--
Matthew Fuller (MF4839) | fullermd@over-yonder.net
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 02:07:13 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 49AC2106564A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 02:07:13 +0000 (UTC)
(envelope-from fbsd2@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id 04B928FC0C
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 02:07:12 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2P2733S079388
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 19:07:12 -0700 (PDT)
(envelope-from fbsd2@sstec.com)
Message-Id: <5.2.1.1.2.20100324180724.0321b1c8@mail.sstec.com>
X-Sender:
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 24 Mar 2010 19:06:51 -0700
To: freeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
From: John Long <fbsd2@sstec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: 8.x Amd64, ATA SATA mode reporting
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 02:07:13 -0000
Moved from another thread
>> I csupd to stable amd64 8.0 and rebuilt then noticed from dmesg that I
went from SATA150 (it should be SATA300) to >> udma100 SATA.
>
>This is a bug/quirk of some changes in ata(4). Your drive should be
>operating at full SATA speed (probably SATA300). You can bring this up
>in another thread if you want, but it's purely cosmetic as far as I
>know. atacontrol(8) and diskinfo(8) -t and -c will come in handy.
I am looking for stability and find this possibly disconcerting.
It looks like you are right about cosmetic for the speed test is about the
same in either. In Generic atacontrol cannot determine the mode at all and
in stable it shows up but as the wrong thing, udma100 SATA instead of SATA300.
dmesg reports on both the same:
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]
I noticed the following line in stable compile from sysctl, I find out it
reports that in generic also.
hptmv.status: RocketRAID 18xx SATA Controller driver Version v1.16
So I added nodevice hptmv
rebuild and It took it out but there was no improvement in results.
Kernel additions at the end.
So, if it is of no matter then cool, if you want me to do something just
let me know.
thx,
John
8 stable:
dmesg ad0: 953868MB <WDC WD1001FALS-00J7B0 05.00K05> at ata0-master UDMA100
SATA
%atacontrol list
ATA channel 0:
Master: ad0 <WDC WD1001FALS-00J7B0/05.00K05> SATA revision 2.x
Slave: no device present
ATA channel 1:
Master: acd0 <CREATIVE CD5230E/C1.01> ATA/ATAPI revision 0
Slave: no device present
%atacontrol mode ad0
current mode = UDMA100 SATA
%diskinfo -t ad0
ad0
512 # sectorsize
1000203804160 # mediasize in bytes (932G)
1953523055 # mediasize in sectors
0 # stripesize
0 # stripeoffset
1938018 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.
WD-WMATV5906953 # Disk ident.
Seek times:
Full stroke: 250 iter in 4.930305 sec = 19.721 msec
Half stroke: 250 iter in 3.434680 sec = 13.739 msec
Quarter stroke: 500 iter in 5.588974 sec = 11.178 msec
Short forward: 400 iter in 1.601327 sec = 4.003 msec
Short backward: 400 iter in 2.187711 sec = 5.469 msec
Seq outer: 2048 iter in 0.391555 sec = 0.191 msec
Seq inner: 2048 iter in 0.243926 sec = 0.119 msec
Transfer rates:
outside: 102400 kbytes in 0.945528 sec = 108299 kbytes/sec
middle: 102400 kbytes in 1.066398 sec = 96024 kbytes/sec
inside: 102400 kbytes in 1.775079 sec = 57688 kbytes/sec
%diskinfo -c ad0
ad0
512 # sectorsize
1000203804160 # mediasize in bytes (932G)
1953523055 # mediasize in sectors
0 # stripesize
0 # stripeoffset
1938018 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.
WD-WMATV5906953 # Disk ident.
I/O command overhead:
time to read 10MB block 0.105669 sec = 0.005 msec/sector
time to read 20480 sectors 2.138126 sec = 0.104 msec/sector
calculated command overhead
=========================================================
8 Generic:
dmesg ad0: 953868MB <WDC WD1001FALS-00J7B0 05.00K05> at ata0-master SATA150
%atacontrol list
ATA channel 0:
Master: ad0 <WDC WD1001FALS-00J7B0/05.00K05> SATA revision 2.x
Slave: no device present
ATA channel 1:
Master: acd0 <CREATIVE CD5230E/C1.01> ATA/ATAPI revision 0
Slave: no device present
%atacontrol mode ad0
current mode = ???
%diskinfo -t ad0
ad0
512 # sectorsize
1000203804160# mediasize in bytes (932G)
1953523055 # mediasize in sectors
0 # stripesize
0 # stripeoffset
1938018 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.
WD-WMATV5906953# Disk ident.
Seek times:
Full stroke: 250 iter in 4.990163 sec = 19.961 msec
Half stroke: 250 iter in 3.460091 sec = 13.840 msec
Quarter stroke: 500 iter in 5.572893 sec = 11.146 msec
Short forward: 400 iter in 1.601550 sec = 4.004 msec
Short backward: 400 iter in 2.187599 sec = 5.469 msec
Seq outer: 2048 iter in 0.378502 sec = 0.185 msec
Seq inner: 2048 iter in 0.248222 sec = 0.121 msec
Transfer rates:
outside: 102400 kbytes in 0.955476 sec = 107172 kbytes/sec
middle: 102400 kbytes in 1.067399 sec = 95934 kbytes/sec
inside: 102400 kbytes in 1.776965 sec = 57626 kbytes/sec
%diskinfo -c ad0
ad0
512 # sectorsize
1000203804160 # mediasize in bytes (932G)
1953523055 # mediasize in sectors
0 # stripesize
0 # stripeoffset
1938018 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.
WD-WMATV5906953 # Disk ident.
I/O command overhead:
time to read 10MB block 0.090332 sec = 0.004 msec/sector
time to read 20480 sectors 2.140744 sec = 0.105 msec/sector
calculated command overhead = 0.100 msec/sector
=======================================================
#
# SSTEC custom -- FreeBSD/amd64
#
# $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.531.2.8 2010/01/18 00:53:21 imp
Exp $
include GENERIC
ident SSTEC
#
# CPU control pseudo-device. Provides access to MSRs, CPUID info and
# microcode update feature.
###
#device cpuctl
## ======================================================================
## Additions for Firewall / Divert
options IPFIREWALL #firewall
options IPFIREWALL_VERBOSE #enable logging to syslogd(8)
options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity
options IPFIREWALL_FORWARD #packet destination changes
options IPDIVERT #divert sockets
###
#options IPFIREWALL_NAT #ipfw kernel nat support
# libalias library, performing NAT required for IPFIREWALL_NAT
###
#options LIBALIAS
# Statically Link in accept filters
options ACCEPT_FILTER_DATA
options ACCEPT_FILTER_HTTP
###
options ACCEPT_FILTER_DNS
# DUMMYNET it is advisable to also have at least "options HZ=1000" to achieve
# a smooth scheduling of the traffic.
options DUMMYNET
###
options HZ=1000
## ======================================================================
#excludes
nodevice hptmv # Highpoint RocketRAID 182x
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 02:27:55 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 66235106564A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 02:27:55 +0000 (UTC)
(envelope-from dmagda@ee.ryerson.ca)
Received: from tomts5-srv.bellnexxia.net (tomts5-srv.bellnexxia.net
[209.226.175.25])
by mx1.freebsd.org (Postfix) with ESMTP id F19F28FC12
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 02:27:54 +0000 (UTC)
Received: from toip3.srvr.bell.ca ([209.226.175.86])
by tomts5-srv.bellnexxia.net
(InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id
<20100325022754.EXDJ6410.tomts5-srv.bellnexxia.net@toip3.srvr.bell.ca>
for <freebsd-stable@freebsd.org>; Wed, 24 Mar 2010 22:27:54 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApEBAHlhqktMQR7Y/2dsb2JhbAAH23+EfgQ
Received: from bas1-toronto09-1279336152.dsl.bell.ca (HELO [192.168.1.103])
([76.65.30.216])
by toip3.srvr.bell.ca with ESMTP; 24 Mar 2010 22:15:41 -0400
Message-Id: <C202E72E-9721-4B50-A501-C8E5686B83EC@ee.ryerson.ca>
From: David Magda <dmagda@ee.ryerson.ca>
To: Michal <michal@ionic.co.uk>
In-Reply-To: <4BAAA415.1000804@ionic.co.uk>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 24 Mar 2010 22:27:53 -0400
References: <4BAA3409.6080406@ionic.co.uk> <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
<hoe355$tuk$1@dough.gmane.org> <4BAAA415.1000804@ionic.co.uk>
X-Mailer: Apple Mail (2.936)
Cc: freebsd-stable@freebsd.org
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 02:27:55 -0000
On Mar 24, 2010, at 19:45, Michal wrote:
> It's all well and good having 1 ZFS server, but it's fragile in the
> the sense of no redundancy, then we have 1 ZFS server and a 2nd with
> DRBD, but that's a waste of money...think 12 TB, and you need to pay
> for another 12TB box for redundancy, and you are still looking at 1
> server. I am thinking a cheap solution but one that has IO
> throughput, redundancy and is easy to manange and expand across
> multiple nodes
If you want an appliance, a Sun/Oracle 7000 series may be close:
http://www.oracle.com/us/products/servers-storage/storage/open-storage/
The 7310 allows for two active-active heads, with fail over if one
dies. Does NFS, SMB/CIFS, and iSCSI; the newest software release
(2010.Q1) gives SAN functionality so you can export LUNs via FC if you
purchase the optional HBAs.
Unfortunately Oracle's web site seriously sucks compared to Sun's for
product information. A lot of good weblog posts though:
http://blogs.sun.com/brendan/
http://blogs.sun.com/brendan/entry/slog_screenshots (write perf.)
http://blogs.sun.com/brendan/entry/l2arc_screenshots (read perf.)
http://blogs.sun.com/ahl/entry/sun_storage_7310
http://blogs.sun.com/wesolows/category/Clustering
Probably cheaper in price than most vendors, but more expensive than
DIY (though you have to add the cost of time).
Disclaimer: just a generally happy Sun customer. (We'll see about
Oracle though. :)
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 08:54:48 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 721A31065672
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 08:54:48 +0000 (UTC)
(envelope-from hausen@punkt.de)
Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131])
by mx1.freebsd.org (Postfix) with ESMTP id EE2608FC20
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 08:54:47 +0000 (UTC)
Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110])
by gate1.intern.punkt.de with ESMTP id o2P8sk7i050196;
Thu, 25 Mar 2010 09:54:46 +0100 (CET)
Received: from hugo10.ka.punkt.de (localhost [127.0.0.1])
by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id o2P8sjCs089883;
Thu, 25 Mar 2010 09:54:45 +0100 (CET)
(envelope-from ry93@hugo10.ka.punkt.de)
Received: (from ry93@localhost)
by hugo10.ka.punkt.de (8.14.2/8.14.2/Submit) id o2P8sj5s089882;
Thu, 25 Mar 2010 09:54:45 +0100 (CET) (envelope-from ry93)
Date: Thu, 25 Mar 2010 09:54:45 +0100
From: "Patrick M. Hausen" <hausen@punkt.de>
To: Michal <michal@ionic.co.uk>
Message-ID: <20100325085445.GA89466@hugo10.ka.punkt.de>
References: <4BAA3409.6080406@ionic.co.uk>
<b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com>
<hoe355$tuk$1@dough.gmane.org> <4BAAA415.1000804@ionic.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4BAAA415.1000804@ionic.co.uk>
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: freebsd-stable@freebsd.org
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 08:54:48 -0000
Hi, all,
On Wed, Mar 24, 2010 at 11:45:25PM +0000, Michal wrote:
> I am thinking a cheap solution but one that
> has IO throughput, redundancy and is easy to manange and expand across
> multiple nodes
Fast, reliable, cheap. Pick any two.
IMHO this is just as true today as it was twenty years ago.
Best regards,
Patrick
--
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de http://www.punkt.de
Gf: Jürgen Egeling AG Mannheim 108285
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 09:09:11 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A22F4106564A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 09:09:11 +0000 (UTC)
(envelope-from michal@ionic.co.uk)
Received: from mail1.sharescope.co.uk (pm1.ionic.co.uk [85.159.80.19])
by mx1.freebsd.org (Postfix) with ESMTP id 5D8AC8FC19
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 09:09:11 +0000 (UTC)
Received: from localhost (unknown [127.0.0.1])
by mail1.sharescope.co.uk (Postfix) with ESMTP id EBF8DFC0AB
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 09:09:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sharescope.co.uk
Received: from mail1.sharescope.co.uk ([127.0.0.1])
by localhost (mail1.sharescope.co.uk [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id 45zGy8CfAdPg for <freebsd-stable@freebsd.org>;
Thu, 25 Mar 2010 09:09:06 +0000 (GMT)
Received: from [192.168.2.37] (office.ionic.co.uk [85.159.85.2])
(Authenticated sender: chris@sharescope.co.uk)
by mail1.sharescope.co.uk (Postfix) with ESMTPSA id BF930FC085
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 09:09:05 +0000 (GMT)
Message-ID: <4BAB2830.6010801@ionic.co.uk>
Date: Thu, 25 Mar 2010 09:09:04 +0000
From: Michal <michal@ionic.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <4BAA3409.6080406@ionic.co.uk> <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com> <hoe355$tuk$1@dough.gmane.org>
<4BAAA415.1000804@ionic.co.uk>
<20100325085445.GA89466@hugo10.ka.punkt.de>
In-Reply-To: <20100325085445.GA89466@hugo10.ka.punkt.de>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 09:09:11 -0000
On 25/03/2010 08:54, Patrick M. Hausen wrote:
> Hi, all,
>
> On Wed, Mar 24, 2010 at 11:45:25PM +0000, Michal wrote:
>> I am thinking a cheap solution but one that
>> has IO throughput, redundancy and is easy to manange and expand across
>> multiple nodes
>
> Fast, reliable, cheap. Pick any two.
>
> IMHO this is just as true today as it was twenty years ago.
>
> Best regards,
> Patrick
I will never get what you would get by spending a lot of money, by doing
it on the cheap. But yes I agree to a certain extent, it's still
expensive and out of the SMB reach
>If you want an appliance, a Sun/Oracle 7000 series may be close:
>
>http://www.oracle.com/us/products/servers-storage/storage/open-storage/
>
>The 7310 allows for two active-active heads, with fail over if one
>dies. Does NFS, SMB/CIFS, and iSCSI; the newest software release
>(2010.Q1) gives SAN functionality so you can export LUNs via FC if you
>purchase the optional HBAs.
There are cheaper options yes I agree, but I think even that might be
out of my budget. I've been fighting for months. Time is ok as a factor,
learning it only helps me in the long run so it's win win for me. I,
too, am still unsure how Oracle buy out will effect Sun...I'm not
optimistic though...I'm expecting to move off MySQL at some point, when
I don't know but I think I will be forced to for some reason or another
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 10:16:15 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C24B71065674
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 10:16:15 +0000 (UTC)
(envelope-from torfinn.ingolfsen@broadpark.no)
Received: from eterpe-smout.broadpark.no (eterpe-smout.broadpark.no
[80.202.8.16]) by mx1.freebsd.org (Postfix) with ESMTP id 7A97A8FC17
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 10:16:15 +0000 (UTC)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from ignis-smin.broadpark.no ([unknown] [80.202.8.11])
by eterpe-smout.broadpark.no
(Sun Java(tm) System Messaging Server 7u3-12.01 64bit (built Oct 15
2009)) with ESMTP id <0KZU00FNO1V0IX20@eterpe-smout.broadpark.no> for
freebsd-stable@freebsd.org; Thu, 25 Mar 2010 11:16:12 +0100 (CET)
Received: from kg-v2.kg4.no ([unknown] [80.203.92.186])
by ignis-smin.broadpark.no
(Sun Java(tm) System Messaging Server 7u3-12.01 64bit (built Oct 15
2009)) with SMTP id <0KZU009MI1UZSGS0@ignis-smin.broadpark.no> for
freebsd-stable@freebsd.org; Thu, 25 Mar 2010 11:16:12 +0100 (CET)
Date: Thu, 25 Mar 2010 11:16:11 +0100
From: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no>
To: freebsd-stable@freebsd.org
Message-id: <20100325111611.b1e8994f.torfinn.ingolfsen@broadpark.no>
In-reply-to: <5.2.1.1.2.20100324165115.03159ab8@mail.sstec.com>
References: <5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
<5.2.1.1.2.20100324165115.03159ab8@mail.sstec.com>
X-Mailer: Sylpheed 3.0.1 (GTK+ 2.18.7; amd64-portbld-freebsd8.0)
X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq;
m"_0v;
~rUM2Yy!zmkh)3&U|u!=<N>T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 10:16:15 -0000
On Wed, 24 Mar 2010 18:04:51 -0700
John Long <fbsd2@sstec.com> wrote:
> I want to thank you very much for all the info you have provided. It has
> clued me into a much better understanding and I see that it is a big
> un-standard thing to monitor these functions. It seems that things are
FYI: for (some) Asus boards thererb is als acpi_aiboost(4).
--
Regards,
Torfinn Ingolfsen
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 13:01:35 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DB1A8106564A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 13:01:35 +0000 (UTC)
(envelope-from freebsd-stable@m.gmane.org)
Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])
by mx1.freebsd.org (Postfix) with ESMTP id 90CA98FC19
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 13:01:35 +0000 (UTC)
Received: from list by lo.gmane.org with local (Exim 4.69)
(envelope-from <freebsd-stable@m.gmane.org>) id 1Numgl-0005x6-Ug
for freebsd-stable@freebsd.org; Thu, 25 Mar 2010 14:01:31 +0100
Received: from lara.cc.fer.hr ([161.53.72.113])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 14:01:31 +0100
Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 14:01:31 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-stable@freebsd.org
From: Ivan Voras <ivoras@freebsd.org>
Date: Thu, 25 Mar 2010 14:01:21 +0100
Lines: 18
Message-ID: <hofmr0$i08$1@dough.gmane.org>
References: <4BAA3409.6080406@ionic.co.uk> <b269bc571003240920r3c06a67ci1057921899c36637@mail.gmail.com> <hoe355$tuk$1@dough.gmane.org>
<4BAAA415.1000804@ionic.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
rv:1.9.1.5) Gecko/20100118 Thunderbird/3.0
In-Reply-To: <4BAAA415.1000804@ionic.co.uk>
Subject: Re: Multi node storage, ZFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 13:01:35 -0000
On 03/25/10 00:45, Michal wrote:
> backend storage for databases. It's all well and good having 1 ZFS
> server, but it's fragile in the the sense of no redundancy, then we have
> 1 ZFS server and a 2nd with DRBD, but that's a waste of money...think 12
> TB, and you need to pay for another 12TB box for redundancy, and you are
> still looking at 1 server. I am thinking a cheap solution but one that
> has IO throughput, redundancy and is easy to manange and expand across
> multiple nodes.
Well, what I described is kind of like that, centered around trying to
best balance redundancy and cost. For example, you don't need two 12 TB
boxes in a mirror. Depending on what you need you can get only one 12 TB
box at the start, then with ZFS trivially extend that storage with
another 12 TB box when you need it, repeat to infinity (each box will
internally have RAID6 or something like that). Of course then you have a
problem if a single box fails, which you can get around by using
triplets of 12 TB boxes in RAIDZ, etc. etc.
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 14:41:28 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CAE661065673
for <freebsd-stable@FreeBSD.org>; Thu, 25 Mar 2010 14:41:28 +0000 (UTC)
(envelope-from bra@fsn.hu)
Received: from people.fsn.hu (people.fsn.hu [195.228.252.137])
by mx1.freebsd.org (Postfix) with ESMTP id 3ECB58FC18
for <freebsd-stable@FreeBSD.org>; Thu, 25 Mar 2010 14:41:27 +0000 (UTC)
Received: by people.fsn.hu (Postfix, from userid 1001)
id 44CE223AD13; Thu, 25 Mar 2010 15:22:10 +0100 (CET)
X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR:
15.9664]
X-CRM114-CacheID: sfid-20100325_15220_267D7945
X-CRM114-Status: Good ( pR: 15.9664 )
Received: from japan.t-online.private (japan.t-online.co.hu [195.228.243.99])
by people.fsn.hu (Postfix) with ESMTPSA id 5945723AD0C
for <freebsd-stable@FreeBSD.org>; Thu, 25 Mar 2010 15:22:09 +0100 (CET)
Message-ID: <4BAB718C.3090001@fsn.hu>
Date: Thu, 25 Mar 2010 15:22:04 +0100
From: Attila Nagy <bra@fsn.hu>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
rv:1.9.1.8) Gecko/20100319 Thunderbird/3.0.3
MIME-Version: 1.0
To: Mailing List FreeBSD Stable <freebsd-stable@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3
(people.fsn.hu); Thu, 25 Mar 2010 15:22:09 +0100 (CET)
Cc:
Subject: 8-STABLE freezes on UDP traffic (DNS), 7.x doesn't
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 14:41:28 -0000
Hi,
I have some recursive nameservers, running unbound and 7.2-STABLE #0:
Wed Sep 2 13:37:17 CEST 2009 on a bunch of HP BL460c machines (bce
interfaces).
These work OK.
During the process of migrating to 8.x, I've upgraded one of these
machines to 8.0-STABLE #25: Tue Mar 9 18:15:34 CET 2010 (the dates
indicate an approximate time, when the source was checked out from
cvsup.hu.freebsd.org, I don't know the exact revision).
The first problem was that the machine occasionally lost network access
for some minutes. I could log in on the console, and I could see the
processes, involved in network IO in "keglim" state, but couldn't do any
network IO. This lasted for some minutes, then everything came back to
normal.
I could fix this issue by raising kern.ipc.nmbclusters to 51200
(doubling from its default size), when I can't see these blackouts.
But now the machine freezes. It can run for about a day, and then it
just freezes. I can't even break in to the debugger with sending NMI to it.
top says:
last pid: 92428; load averages: 0.49, 0.40, 0.38 up 0+21:13:18
07:41:43
43 processes: 2 running, 38 sleeping, 1 zombie, 2 lock
CPU: 1.3% user, 0.0% nice, 1.3% system, 26.0% interrupt, 71.3% idle
Mem: 1682M Active, 99M Inact, 227M Wired, 5444K Cache, 44M Buf, 5899M Free
Swap:
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
45011 bind 4 49 0 1734M 1722M RUN 2 37:42 22.17% unbound
712 bind 3 44 0 70892K 19904K uwait 0 71:07 3.86%
python2.6
The common in these freezes seems to be the high interrupt count.
Normally, during load the CPU times look like this:
CPU: 3.5% user, 0.0% nice, 1.8% system, 0.4% interrupt, 94.4% idle
I could observe a "freeze", where top remained running and everything
was 0%, except interrupt, which was 25% exactly (the machine has four
cores), and another, where I could save the following console output:
CPU: 0.0% user, 0.0% nice, 0.2% system, 50.0% interrupt, 49.8% idle
.......(partial, broken line)....32M 2423M *udp 1 50:16 10.89% unbound
714 bind 3 44 0 70892K 26852K uwait 3 8:41 4.69%
python2.6
61004 root 1 62 0 37428K 10876K *udp 1 0:00 1.56% python
706 root 1 44 0 2696K 624K piperd 1 0:07 0.00%
readproctit
Both unbound and python accepts DNS requests, and it seems when 25%
interrupt happens, only unbound is in *udp state, where it is 50%, both
programs are in that state.
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 15:39:40 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5BFB9106566C
for <freebsd-stable@FreeBSD.org>; Thu, 25 Mar 2010 15:39:40 +0000 (UTC)
(envelope-from mloftis@wgops.com)
Received: from juggler.wgops.com (juggler.wgops.com [204.11.247.41])
by mx1.freebsd.org (Postfix) with ESMTP id 390DA8FC0C
for <freebsd-stable@FreeBSD.org>; Thu, 25 Mar 2010 15:39:39 +0000 (UTC)
Received: by juggler.wgops.com (Postfix, from userid 65534)
id 9C1CDA810C; Thu, 25 Mar 2010 09:39:39 -0600 (MDT)
X-Spam-ASN:
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on juggler.wgops.com
X-Spam-Level:
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed
version=3.2.5
Received: from [192.168.1.44] (host-72-174-39-176.msl-mt.client.bresnan.net
[72.174.39.176])
by juggler.wgops.com (Postfix) with ESMTPSA id 6D22DA80BE
for <freebsd-stable@FreeBSD.org>; Thu, 25 Mar 2010 09:39:37 -0600 (MDT)
Date: Thu, 25 Mar 2010 09:39:40 -0600
From: Michael Loftis <mloftis@wgops.com>
To: Mailing List FreeBSD Stable <freebsd-stable@FreeBSD.org>
Message-ID: <886B21E1787F0003B89E34B6@[192.168.1.44]>
In-Reply-To: <4BAB718C.3090001@fsn.hu>
References: <4BAB718C.3090001@fsn.hu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: clamav-milter 0.95.3 at juggler
X-Virus-Status: Clean
Cc:
Subject: Re: 8-STABLE freezes on UDP traffic (DNS), 7.x doesn't
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 15:39:40 -0000
--On Thursday, March 25, 2010 3:22 PM +0100 Attila Nagy <bra@fsn.hu> wrote:
<...>
> Both unbound and python accepts DNS requests, and it seems when 25%
> interrupt happens, only unbound is in *udp state, where it is 50%, both
> programs are in that state.
Try turning of hardware TSO/checksum offload if it's availble on your
chipset? ifconfig <interface> -rxcsum -txcsum -tso -- I'm only using nfe
chips right now, but w/ the TSO/CSUM on they lock up constantly under high
load. We're pretty sure it's mostly the nfe driver, or the chips
themselves, but have never ruled out some generic 8.x hardware offload
issues.
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 15:48:18 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D9C01106564A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 15:48:18 +0000 (UTC)
(envelope-from mike@sentex.net)
Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18])
by mx1.freebsd.org (Postfix) with ESMTP id A704E8FC26
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 15:48:18 +0000 (UTC)
Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27])
by lava.sentex.ca (8.14.3/8.14.3) with ESMTP id o2PFmHMH028420;
Thu, 25 Mar 2010 11:48:17 -0400 (EDT) (envelope-from mike@sentex.net)
Message-Id: <201003251548.o2PFmHMH028420@lava.sentex.ca>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 25 Mar 2010 11:48:02 -0400
To: freebsd-stable@freebsd.org
From: Mike Tancsa <mike@sentex.net>
In-Reply-To: <886B21E1787F0003B89E34B6@[192.168.1.44]>
References: <4BAB718C.3090001@fsn.hu> <886B21E1787F0003B89E34B6@[192.168.1.44]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: 8-STABLE freezes on UDP traffic (DNS), 7.x doesn't
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 15:48:18 -0000
At 11:39 AM 3/25/2010, Michael Loftis wrote:
>--On Thursday, March 25, 2010 3:22 PM +0100 Attila Nagy <bra@fsn.hu> wrote:
>
><...>
>>Both unbound and python accepts DNS requests, and it seems when 25%
>>interrupt happens, only unbound is in *udp state, where it is 50%, both
>>programs are in that state.
>
>Try turning of hardware TSO/checksum offload if it's availble on
>your chipset? ifconfig <interface> -rxcsum -txcsum -tso -- I'm only
>using nfe chips right now, but w/ the TSO/CSUM on they lock up
>constantly under high load. We're pretty sure it's mostly the nfe
>driver, or the chips themselves, but have never ruled out some
>generic 8.x hardware offload issues.
There were also a bunch of commits last night for the bce driver. If
its the NIC in RELENG_8, perhaps those bug fixes might help
<http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-March/001804.html>http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-March/001804.html
http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-March/001803.html
---Mike
>_______________________________________________
>freebsd-stable@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
--------------------------------------------------------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike@sentex.net
Providing Internet since 1994 www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 13:11:09 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D8BB81065674;
Thu, 25 Mar 2010 13:11:09 +0000 (UTC)
(envelope-from jack@jarasoft.net)
Received: from raats.xs4all.nl (raats.xs4all.nl [82.95.230.43])
by mx1.freebsd.org (Postfix) with ESMTP id 8961B8FC19;
Thu, 25 Mar 2010 13:11:09 +0000 (UTC)
Received: from raats.xs4all.nl (orac.jarasoft.net [10.10.10.10])
by raats.xs4all.nl (Postfix) with ESMTP id 9204D23440;
Thu, 25 Mar 2010 14:11:12 +0100 (CET)
Received: from jarasc430 (unknown [10.10.10.100])
by raats.xs4all.nl (Postfix) with ESMTPA id 55A9022905;
Thu, 25 Mar 2010 14:11:12 +0100 (CET)
Message-ID: <4FBFE9F90804409B855AD118FE27B11E@jarasc430>
From: "Jack Raats" <jack@jarasoft.net>
To: <freebsd-stable@freebsd.org>, <freebsd-questions@freebsd.org>,
<postfix-users@postfix.org>
Date: Thu, 25 Mar 2010 14:11:00 +0100
Organization: JaRaSoft, Steenbergen, Nederland
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Relayed-By: GPGrelay Version 0.959 (Win32)
X-Virus-Scanned: ClamAV using ClamSMTP on orac.jarasoft.net
X-Mailman-Approved-At: Thu, 25 Mar 2010 16:42:36 +0000
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc:
Subject: Exchange ActiveSync account
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Jack Raats <jack@jarasoft.net>
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 13:11:09 -0000
Hi,
I have an Exchange ActiveSync account and I would like to get this mail =
on my freebsd 7.3-stable server.
I donn't haven an imap or pop account, only the information of the =
activesync account.
Can anyone give me a clue how to achieve this?
Thanks for your time!
Jack Raats
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 17:17:31 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CF8A81065672
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 17:17:31 +0000 (UTC)
(envelope-from mavbsd@gmail.com)
Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com
[209.85.220.222])
by mx1.freebsd.org (Postfix) with ESMTP id 5A60E8FC1A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 17:17:30 +0000 (UTC)
Received: by fxm22 with SMTP id 22so3814520fxm.14
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 10:17:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:message-id:date:from
:user-agent:mime-version:to:cc:subject:references:in-reply-to
:content-type:content-transfer-encoding;
bh=iZYs9aY+H1n4uarHxgfb2x8reqytibkNa8/ob+aqNVE=;
b=huJUk4WjbRCO+250EqqaGLsH/xfwnR4o2CGPzzy5Itjr055X7+1suck+NNixmE1+/H
Vc51AWGk6LiZrzFzFFDOWdMyNkokYaiVm4JcUhEwHdP0P7D6qXmgLDox8CLbmo+pAI7m
UVKQ1XoUxJoRRAsKtfM32TG+H3G3G3z+ijROQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject
:references:in-reply-to:content-type:content-transfer-encoding;
b=S3W+OULsmL5BaCR1GLIMOOJxcs31PSL9e5vs6d7htlLH8fVeCogYfIE1uurz75yfGh
PKBr0HszBRzHji8lp1gj51fQRv/jzHvDq7Ottb53Wlu6Nl5gEILiexZ+oA34nEtSXntU
PtYHzdM9gheQF3sY4lM4NOe8oSzkdqOXd86YI=
Received: by 10.223.7.4 with SMTP id b4mr2553377fab.102.1269537449959;
Thu, 25 Mar 2010 10:17:29 -0700 (PDT)
Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226])
by mx.google.com with ESMTPS id 13sm1234196fxm.14.2010.03.25.10.17.28
(version=SSLv3 cipher=RC4-MD5); Thu, 25 Mar 2010 10:17:29 -0700 (PDT)
Sender: Alexander Motin <mavbsd@gmail.com>
Message-ID: <4BAB9AA6.8020600@FreeBSD.org>
Date: Thu, 25 Mar 2010 19:17:26 +0200
From: Alexander Motin <mav@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.23 (X11/20091212)
MIME-Version: 1.0
To: John Long <fbsd2@sstec.com>
References: <1269530613.00233492.1269520205@10.7.7.3>
In-Reply-To: <1269530613.00233492.1269520205@10.7.7.3>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: 8.x Amd64, ATA SATA mode reporting
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 17:17:31 -0000
John Long wrote:
> Moved from another thread
>>> I csupd to stable amd64 8.0 and rebuilt then noticed from dmesg that
> I went from SATA150 (it should be SATA300) to >> udma100 SATA.
>>
>>This is a bug/quirk of some changes in ata(4). Your drive should be
>>operating at full SATA speed (probably SATA300). You can bring this up
>>in another thread if you want, but it's purely cosmetic as far as I
>>know. atacontrol(8) and diskinfo(8) -t and -c will come in handy.
>
> I am looking for stability and find this possibly disconcerting.
> It looks like you are right about cosmetic for the speed test is about
> the same in either. In Generic atacontrol cannot determine the mode at
> all and in stable it shows up but as the wrong thing, udma100 SATA
> instead of SATA300.
The problem is that ICH7 chipset unable to report negotiated SATA speed.
That's why only SATA reported there.
UDMA100 report is also correct there (even if it looks strange). As SATA
just wraps all existing parallel ATA protocols, from ATA protocol point
of view that mode is active.
--
Alexander Motin
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 18:18:06 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 74A72106564A
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 18:18:06 +0000 (UTC)
(envelope-from torfinn.ingolfsen@broadpark.no)
Received: from eterpe-smout.broadpark.no (eterpe-smout.broadpark.no
[80.202.8.16]) by mx1.freebsd.org (Postfix) with ESMTP id 3127D8FC18
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 18:18:05 +0000 (UTC)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from ignis-smin.broadpark.no ([unknown] [80.202.8.11])
by eterpe-smout.broadpark.no
(Sun Java(tm) System Messaging Server 7u3-12.01 64bit (built Oct 15
2009)) with ESMTP id <0KZU00MU4O658P30@eterpe-smout.broadpark.no> for
freebsd-stable@freebsd.org; Thu, 25 Mar 2010 19:18:05 +0100 (CET)
Received: from kg-v2.kg4.no ([unknown] [80.203.92.186])
by ignis-smin.broadpark.no
(Sun Java(tm) System Messaging Server 7u3-12.01 64bit (built Oct 15
2009)) with SMTP id <0KZU00N1SO640780@ignis-smin.broadpark.no> for
freebsd-stable@freebsd.org; Thu, 25 Mar 2010 19:18:05 +0100 (CET)
Date: Thu, 25 Mar 2010 19:18:04 +0100
From: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no>
To: freebsd-stable@freebsd.org
Message-id: <20100325191804.73c0cbf0.torfinn.ingolfsen@broadpark.no>
In-reply-to: <4FBFE9F90804409B855AD118FE27B11E@jarasc430>
References: <4FBFE9F90804409B855AD118FE27B11E@jarasc430>
X-Mailer: Sylpheed 3.0.1 (GTK+ 2.18.7; amd64-portbld-freebsd8.0)
X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq;
m"_0v;
~rUM2Yy!zmkh)3&U|u!=<N>T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH
Cc:
Subject: Re: Exchange ActiveSync account
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 18:18:06 -0000
On Thu, 25 Mar 2010 14:11:00 +0100
Jack Raats <jack@jarasoft.net> wrote:
> I have an Exchange ActiveSync account and I would like to get this mail on my freebsd 7.3-stable server.
> I donn't haven an imap or pop account, only the information of the activesync account.
>
> Can anyone give me a clue how to achieve this?
>From http://en.wikipedia.org/wiki/Activesync
"Activesync uses ActiveSync Exchange, a proprietary protocol, requiring
other vendors to license the protocol to achieve compatibility."
In other words; it might not be possible.
HTH
--
Regards,
Torfinn Ingolfsen
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 18:36:57 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C53CE1065673
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 18:36:57 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com
[209.85.218.216])
by mx1.freebsd.org (Postfix) with ESMTP id 4CEF68FC14
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 18:36:56 +0000 (UTC)
Received: by bwz8 with SMTP id 8so2346774bwz.3
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 11:36:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=Khg5lgnHtlPxTgxRBZ7KfuVbUyAes052bP9BHvykolI=;
b=fIKi0+PWeVGG6xPEp3TWQFTk6nLB3venCFvzu7T6gbpDy1JMfoffNlhpBKSlVS5TGr
Wq1Ex/vCklslwqOym2A34IvA4ge3rN2smp+lRuKUbZM1tJIwJfIHwI9cm24/gsU5qePx
byO0hLlfZdtAe8hjXaT7lGo3WYQQElxzkh+pw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=BEHcqrIdewcPixMnOPdrAW3v1fmp0UpnYxo8NxirM0iCtiJ+0KYxwCSyf3tph4RZe+
77jGlGREsC2Qdu2AnMqIBAkiuZ0VvwNLEsAObbsS3E15dMCWiBRIR9ME1qbNAM4eIRe3
dyZ+CoInM/ZBlVHK4F63yy1CJsQqGYqnP219U=
Received: by 10.204.23.6 with SMTP id p6mr56373bkb.67.1269542214900;
Thu, 25 Mar 2010 11:36:54 -0700 (PDT)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id 15sm40228bwz.4.2010.03.25.11.36.51
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Thu, 25 Mar 2010 11:36:53 -0700 (PDT)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Thu, 25 Mar 2010 11:36:28 -0700
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Thu, 25 Mar 2010 11:36:28 -0700
To: Attila Nagy <bra@fsn.hu>
Message-ID: <20100325183628.GD1278@michelle.cdnetworks.com>
References: <4BAB718C.3090001@fsn.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BAB718C.3090001@fsn.hu>
User-Agent: Mutt/1.4.2.3i
Cc: Mailing List FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: 8-STABLE freezes on UDP traffic (DNS), 7.x doesn't
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 18:36:57 -0000
On Thu, Mar 25, 2010 at 03:22:04PM +0100, Attila Nagy wrote:
> Hi,
>
> I have some recursive nameservers, running unbound and 7.2-STABLE #0:
> Wed Sep 2 13:37:17 CEST 2009 on a bunch of HP BL460c machines (bce
> interfaces).
> These work OK.
>
> During the process of migrating to 8.x, I've upgraded one of these
> machines to 8.0-STABLE #25: Tue Mar 9 18:15:34 CET 2010 (the dates
> indicate an approximate time, when the source was checked out from
> cvsup.hu.freebsd.org, I don't know the exact revision).
>
> The first problem was that the machine occasionally lost network access
> for some minutes. I could log in on the console, and I could see the
> processes, involved in network IO in "keglim" state, but couldn't do any
> network IO. This lasted for some minutes, then everything came back to
> normal.
> I could fix this issue by raising kern.ipc.nmbclusters to 51200
> (doubling from its default size), when I can't see these blackouts.
>
> But now the machine freezes. It can run for about a day, and then it
> just freezes. I can't even break in to the debugger with sending NMI to it.
> top says:
> last pid: 92428; load averages: 0.49, 0.40, 0.38 up 0+21:13:18
> 07:41:43
> 43 processes: 2 running, 38 sleeping, 1 zombie, 2 lock
> CPU: 1.3% user, 0.0% nice, 1.3% system, 26.0% interrupt, 71.3% idle
> Mem: 1682M Active, 99M Inact, 227M Wired, 5444K Cache, 44M Buf, 5899M Free
> Swap:
>
> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
> 45011 bind 4 49 0 1734M 1722M RUN 2 37:42 22.17% unbound
> 712 bind 3 44 0 70892K 19904K uwait 0 71:07 3.86%
> python2.6
>
> The common in these freezes seems to be the high interrupt count.
> Normally, during load the CPU times look like this:
> CPU: 3.5% user, 0.0% nice, 1.8% system, 0.4% interrupt, 94.4% idle
>
> I could observe a "freeze", where top remained running and everything
> was 0%, except interrupt, which was 25% exactly (the machine has four
> cores), and another, where I could save the following console output:
> CPU: 0.0% user, 0.0% nice, 0.2% system, 50.0% interrupt, 49.8% idle
When you see high number of interrupts, could you check this comes
from bce(4)? I guess you can use systat(1) to check how many number
interrupts are generated from bce(4).
> .......(partial, broken line)....32M 2423M *udp 1 50:16 10.89% unbound
> 714 bind 3 44 0 70892K 26852K uwait 3 8:41 4.69%
> python2.6
> 61004 root 1 62 0 37428K 10876K *udp 1 0:00 1.56% python
> 706 root 1 44 0 2696K 624K piperd 1 0:07 0.00%
> readproctit
>
> Both unbound and python accepts DNS requests, and it seems when 25%
> interrupt happens, only unbound is in *udp state, where it is 50%, both
> programs are in that state.
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 18:53:26 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E07CD106566C
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 18:53:26 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com
[209.85.218.216])
by mx1.freebsd.org (Postfix) with ESMTP id 696838FC16
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 18:53:26 +0000 (UTC)
Received: by bwz8 with SMTP id 8so2360995bwz.3
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 11:53:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=3avqiYpUseEg4n7Hqsov6nHK6pRCyAL0t+abjBTgPWM=;
b=njpZdI0xNrUAs9NC4IHGHNtgZmhWz3lVfzuVdAM6Qo15UaaHiAMj7Xz6+Hge3YaIuS
EmXPvGh4Zn6tvnlo+FcoiSiOJ6oqp9JgCDUNZSaEFomxioc9o74VLXg9AMsqunY5UbyM
xlT9rZn1hln3xr946Zs2rmZsiMCEtDpyTLhgM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=L2jwxgVlBGnbz1BEU/0kyJ7E758CMVnVZmUDIfLlfLnYPM5Y+BNmbyZa6gNl9t8fzj
2QdOFwmkXsWnsx3CeLMbwBajf3KXnkYZrdCoZeG88mVZ0ownVf22tdakBkdAIys702iS
a1JIFDMInaAaI7XnCyKsLnmWAlSIzBMSKgoic=
Received: by 10.204.132.131 with SMTP id b3mr47730bkt.135.1269543205233;
Thu, 25 Mar 2010 11:53:25 -0700 (PDT)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id 14sm51311bwz.10.2010.03.25.11.53.22
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Thu, 25 Mar 2010 11:53:23 -0700 (PDT)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Thu, 25 Mar 2010 11:52:58 -0700
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Thu, 25 Mar 2010 11:52:58 -0700
To: Michael Loftis <mloftis@wgops.com>
Message-ID: <20100325185258.GF1278@michelle.cdnetworks.com>
References: <4BAB718C.3090001@fsn.hu> <886B21E1787F0003B89E34B6@[192.168.1.44]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <886B21E1787F0003B89E34B6@[192.168.1.44]>
User-Agent: Mutt/1.4.2.3i
Cc: Mailing List FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: 8-STABLE freezes on UDP traffic (DNS), 7.x doesn't
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 18:53:27 -0000
On Thu, Mar 25, 2010 at 09:39:40AM -0600, Michael Loftis wrote:
>
>
> --On Thursday, March 25, 2010 3:22 PM +0100 Attila Nagy <bra@fsn.hu> wrote:
>
> <...>
> >Both unbound and python accepts DNS requests, and it seems when 25%
> >interrupt happens, only unbound is in *udp state, where it is 50%, both
> >programs are in that state.
>
> Try turning of hardware TSO/checksum offload if it's availble on your
> chipset? ifconfig <interface> -rxcsum -txcsum -tso -- I'm only using nfe
> chips right now, but w/ the TSO/CSUM on they lock up constantly under high
> load. We're pretty sure it's mostly the nfe driver, or the chips
If you have nfe(4) issues please file PR for that. I'm not aware of
TSO, Tx checksum offloading related issue of nfe(4). Due to lack of
documentation for the controller it might be hard to analyze the
issue but it may help other users who are suffering from the same
issue.
> themselves, but have never ruled out some generic 8.x hardware offload
> issues.
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 19:31:00 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8DC281065670
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 19:31:00 +0000 (UTC)
(envelope-from bra@fsn.hu)
Received: from people.fsn.hu (people.fsn.hu [195.228.252.137])
by mx1.freebsd.org (Postfix) with ESMTP id 3DEF88FC1D
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 19:30:59 +0000 (UTC)
Received: by people.fsn.hu (Postfix, from userid 1001)
id E59DB23B1E5; Thu, 25 Mar 2010 20:30:57 +0100 (CET)
X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR:
23.8687]
X-CRM114-CacheID: sfid-20100325_20305_63671EE7
X-CRM114-Status: Good ( pR: 23.8687 )
Message-ID: <4BABB9F0.6010506@fsn.hu>
Date: Thu, 25 Mar 2010 20:30:56 +0100
From: Attila Nagy <bra@fsn.hu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.8.1.23) Gecko/20090817 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0
MIME-Version: 1.0
To: pyunyh@gmail.com
References: <4BAB718C.3090001@fsn.hu>
<20100325183628.GD1278@michelle.cdnetworks.com>
In-Reply-To: <20100325183628.GD1278@michelle.cdnetworks.com>
X-Stationery: 0.4.10
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3
(people.fsn.hu); Thu, 25 Mar 2010 20:30:56 +0100 (CET)
Cc: Mailing List FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: 8-STABLE freezes on UDP traffic (DNS), 7.x doesn't
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 19:31:00 -0000
Pyun YongHyeon wrote:
> On Thu, Mar 25, 2010 at 03:22:04PM +0100, Attila Nagy wrote:
>
>> Hi,
>>
>> I have some recursive nameservers, running unbound and 7.2-STABLE #0:
>> Wed Sep 2 13:37:17 CEST 2009 on a bunch of HP BL460c machines (bce
>> interfaces).
>> These work OK.
>>
>> During the process of migrating to 8.x, I've upgraded one of these
>> machines to 8.0-STABLE #25: Tue Mar 9 18:15:34 CET 2010 (the dates
>> indicate an approximate time, when the source was checked out from
>> cvsup.hu.freebsd.org, I don't know the exact revision).
>>
>> The first problem was that the machine occasionally lost network access
>> for some minutes. I could log in on the console, and I could see the
>> processes, involved in network IO in "keglim" state, but couldn't do any
>> network IO. This lasted for some minutes, then everything came back to
>> normal.
>> I could fix this issue by raising kern.ipc.nmbclusters to 51200
>> (doubling from its default size), when I can't see these blackouts.
>>
>> But now the machine freezes. It can run for about a day, and then it
>> just freezes. I can't even break in to the debugger with sending NMI to it.
>> top says:
>> last pid: 92428; load averages: 0.49, 0.40, 0.38 up 0+21:13:18
>> 07:41:43
>> 43 processes: 2 running, 38 sleeping, 1 zombie, 2 lock
>> CPU: 1.3% user, 0.0% nice, 1.3% system, 26.0% interrupt, 71.3% idle
>> Mem: 1682M Active, 99M Inact, 227M Wired, 5444K Cache, 44M Buf, 5899M Free
>> Swap:
>>
>> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
>> 45011 bind 4 49 0 1734M 1722M RUN 2 37:42 22.17% unbound
>> 712 bind 3 44 0 70892K 19904K uwait 0 71:07 3.86%
>> python2.6
>>
>> The common in these freezes seems to be the high interrupt count.
>> Normally, during load the CPU times look like this:
>> CPU: 3.5% user, 0.0% nice, 1.8% system, 0.4% interrupt, 94.4% idle
>>
>> I could observe a "freeze", where top remained running and everything
>> was 0%, except interrupt, which was 25% exactly (the machine has four
>> cores), and another, where I could save the following console output:
>> CPU: 0.0% user, 0.0% nice, 0.2% system, 50.0% interrupt, 49.8% idle
>>
>
> When you see high number of interrupts, could you check this comes
> from bce(4)? I guess you can use systat(1) to check how many number
> interrupts are generated from bce(4).
>
I've tried it multiple times, but couldn't yet catch the moment when the
machine was still alive (so the script could run) and there were
increased amount of interrupts.
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 19:50:40 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 742071065672
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 19:50:40 +0000 (UTC)
(envelope-from me@nezmer.info)
Received: from mail.nezmer.info (nezmer.info [97.107.142.36])
by mx1.freebsd.org (Postfix) with ESMTP id 53A778FC1B
for <freebsd-stable@freebsd.org>; Thu, 25 Mar 2010 19:50:40 +0000 (UTC)
Date: Thu, 25 Mar 2010 21:32:10 +0200
From: Nezmer <bsd@nezmer.info>
To: freebsd-stable@freebsd.org
Message-ID: <20100325193127.GA80926@mail>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: mutt-ng/devel-r804 (FreeBSD)
Subject: 8-STABLE/amd64: kernel panic after a minute of mounting xfs
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 19:50:40 -0000
(8-STABLE/amd64 Feb 25th)
Hi,
This is the 1st time FreeBSD panics on me. It happened after a
minute of mounting an XFS partition. I'm not sure It's XFS but It's the
only part of the OS I try for the 1st time.
kernel: vn_iowait doing nothing on FreeBSD?
last message repeated 15 times
kernel:
kernel:
kernel: Fatal trap 12: page fault while in kernel mode
kernel: cpuid = 1; apic id = 01
kernel: fault virtual address = 0x290
kernel: fault code = supervisor read data, page not present
kernel: instruction pointer = 0x20:0xffffffff8057e38e
kernel: stack pointer = 0x28:0xffffff80790af7d0
kernel: frame pointer = 0x28:0xffffff80790af7f0
kernel: code segment = base 0x0, limit 0xfffff, type 0x1b
kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
kernel: processor eflags = interrupt enabled, resume, IOPL = 0
kernel: current process = 4668 (umount)
kernel: trap number = 12
kernel: panic: page fault
kernel: cpuid = 1
kernel: Uptime: 31m48s
kernel: Cannot dump. Device not defined or unavailable.
kernel: Automatic reboot in 15 seconds - press a key on the console to abort
kernel: --> Press a key on the console to reboot,
kernel: --> or switch off the system now.
kernel: Rebooting...
From owner-freebsd-stable@FreeBSD.ORG Thu Mar 25 23:04:55 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B6CC1106566C;
Thu, 25 Mar 2010 23:04:55 +0000 (UTC)
(envelope-from h.schmalzbauer@omnilan.de)
Received: from host.omnilan.net (host.omnilan.net [62.245.232.135])
by mx1.freebsd.org (Postfix) with ESMTP id 082FE8FC08;
Thu, 25 Mar 2010 23:04:54 +0000 (UTC)
Received: from titan.flintsbach.schmalzbauer.de
(titan.flintsbach.schmalzbauer.de [172.21.1.150])
(authenticated bits=0)
by host.omnilan.net (8.13.8/8.13.8) with ESMTP id o2PN4quW071075
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 26 Mar 2010 00:04:53 +0100 (CET)
(envelope-from h.schmalzbauer@omnilan.de)
Message-ID: <4BABEC09.8070709@omnilan.de>
Date: Fri, 26 Mar 2010 00:04:41 +0100
From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de>
Organization: OmniLAN
User-Agent: Thunderbird 2.0.0.23 (X11/20090906)
MIME-Version: 1.0
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
References: <1266934981.00222684.1266922202@10.7.7.3> <4B83EFD4.8050403@FreeBSD.org> <4B8E1489.2070306@omnilan.de> <4B8E1B3D.306@FreeBSD.org> <4B8E1DA9.2090406@omnilan.de> <20100303110647.GA51588@icarus.home.lan> <4B9C034B.90900@omnilan.de>
<4B9CC493.30009@omnilan.de>
In-Reply-To: <4B9CC493.30009@omnilan.de>
X-Enigmail-Version: 0.95.6
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig43C912A24C95AA60A133E470"
Cc: Alexander Motin <mav@freebsd.org>, freebsd-stable@freebsd.org
Subject: Dtrong elcheapo-ZFS-disk recommendation [Was: Re: ahcich timeouts,
only with ahci, not with ataahci]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 23:04:55 -0000
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig43C912A24C95AA60A133E470
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Harald Schmalzbauer schrieb am 14.03.2010 12:12 (localtime):
> Harald Schmalzbauer schrieb am 13.03.2010 22:27 (localtime):
>> Am 03.03.2010 12:06, schrieb Jeremy Chadwick:
>>> On Wed, Mar 03, 2010 at 09:28:25AM +0100, Harald Schmalzbauer wrote:
>>>> Alexander Motin schrieb am 03.03.2010 09:18 (localtime):
>>>>> Harald Schmalzbauer wrote:
>>>>>> Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
>>>>>>> Harald Schmalzbauer wrote:
>>>>>>>> I'm frequently getting my machine locked with ahcichX timeouts:
>>>>>>>> ahcich2: Timeout on slot 0
>>>>>>>> ahcich2: is 00000000 cs 00000001 ss 00000000 rs 00000001 tfd c0 =
>>>>>>>> serr
>>>>>>>> 00000000
>>>>>>>> ahcich2: Timeout on slot 8
>>>>>>>> ahcich2: is 00000000 cs 00000100 ss 00000000 rs 00000100 tfd c0 =
>>>>>>>> serr
>>>>>>>> 00000000
>>>>>>>> ahcich2: Timeout on slot 8
>>>>>>>> ahcich2: is 00000000 cs fffff07f ss ffffff7f rs ffffff7f tfd c0 =
>>>>>>>> serr
>>>>>>>> 00000000
>>>>>>>> ...
>>>>>>> Looking that is (Interrupt status) is zero and `rs =3D=3D cs | ss=
`=20
>>>>>>> (running
>>>>>>> command bitmasks in driver and hardware), controller doesn't repo=
rt
>>>>>>> command completion. Looking on TFD status 0xc0 with BUSY bit set,=
I
>>>>>>> would suppose that either disk stuck in command processing for so=
me
>>>>>>> reason, or controller missed command completion status.
>>>>>>>
>>>>>>> Have you noticed 30 second (default ATA timeout) pause before=20
>>>>>>> timeout
>>>>>>> message printed? Just want to be sure that driver waited enough=20
>>>>>>> before
>>>>>>> give up.
>>>>>>>
>>>>>>>> This happens when backup over GbE overloads ZFS/HDD capabilities=
=2E
>>>>>>>> I reduced vfs.zfs.txg.timeout to 1 to prevent the machine from=20
>>>>>>>> locking
>>>>>>>> up almost immediately, but from it still happens.
>>>>>>>> When I don't use ahci but ataahci (the old driver if I=20
>>>>>>>> understand things
>>>>>>>> correct) I also see the ZFS burst write congestion, but this=20
>>>>>>>> doesn't
>>>>>>>> lead to controller timeouts, thus blocking the machine.
>>>>>>>>
>>>>>>>> Sometimes the machine recovers from the disk lock, but most=20
>>>>>>>> often I have
>>>>>>>> to reboot.
>>>>>>> How it looks when it doesn't? Can you send me full log messages?
>>>>>> Hello, this morning I had a stall, but the machine recovered after=
=20
>>>>>> about
>>>>>> one Minute. Here's what I got from the kernel:
>>>>>> ahcich2: Timeout on slot 29
>>>>>> ahcich2: is 00000000 cs 00000003 ss e0000003 rs e0000003 tfd c0 se=
rr
>>>>>> 00000000
>>>>>> em1: watchdog timeout -- resetting
>>>>>> em1: watchdog timeout -- resetting
>>>>>> ahcich2: Timeout on slot 10
>>>>>> ahcich2: is 00000000 cs 00006000 ss 00007c00 rs 00007c00 tfd c0 se=
rr
>>>>>> 00000000
>>>>>> ahcich2: Timeout on slot 18
>>>>>> ahcich2: is 00000000 cs 00040000 ss 00000000 rs 00040000 tfd c0 se=
rr
>>>>>> 00000000
>>>>>> ahcich2: Timeout on slot 2
>>>>>> ahcich2: is 00000000 cs 00000004 ss 00000000 rs 00000004 tfd c0 se=
rr
>>>>>> 00000000
>>>>>> ahcich2: Timeout on slot 2
>>>>>> ahcich2: is 00000000 cs 00000000 ss 0000000c rs 0000000c tfd 40 se=
rr
>>>>>> 00000000
>>>>>>
>>>>>> Does this tell you something useful?
>>>>> It doesn't. Looking on logged register content - commands are indee=
d
>>>>> still running and no interrupts requested. Interesting to see em1
>>>>> watchdog timeout there. Aren't they related somehow?
>>>> dmesg | grep "irq 18":
>>>> uhci0: <Intel 82801I (ICH9) USB controller> port 0x20c0-0x20df irq
>>>> 18 at device 26.0 on pci0
>>>> uhci4: <Intel 82801I (ICH9) USB controller> port 0x2040-0x205f irq
>>>> 18 at device 29.2 on pci0
>>>> em1: <Intel(R) PRO/1000 Network Connection 6.9.14> port
>>>> 0x1000-0x103f mem 0xe1920000-0xe193ffff,0xe1900000-0xe191ffff irq 18=
>>>> at device 2.0 on pci3
>>>> ichsmb0: <Intel 82801I (ICH9) SMBus controller> port 0x2000-0x201f
>>>> mem 0xe1a22000-0xe1a220ff irq 18 at device 31.3 on pci0
>>>>
>>>> The don't share the same IRQ at least.
=2E..
For the records: I replaced the Samsung F2 1.5TB 5200rpm EcoGreen Drives.=
In my dreams that should improove my 3-disk RAIDZ from 33MB/s avarage=20
(>5G transferes) to about 60MB/s.
In reality, it improoved it to 90MB/s, _and_ completely eliminatong the=20
ahcich timeouts, as well as the burst writes where the complete machine=20
stuck while ZFS flushed/wrote trransaction groups.
So the difference in ZFS usage between the disks is far beond my=20
imagination.
I can higly recommend the:
=3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D
Model Family: Hitachi Deskstar 7K2000
Device Model: Hitachi HDS722020ALA330
Serial Number: JK1174YAH9ZH7W
Firmware Version: JKAOA28A
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Thu Mar 25 23:48:13 2010 CET
Some TB restored so far, no errors, no oddities, no problems at all.=20
Same server, same FreeBSD, but ahci.ko enabled again (so with NCQ,=20
thanks mav and friends).
I can confirm that the F2 Samsung drives worked fine with the old ata=20
driver (speaking without enabling NQC) and ZFS. They did their job for 2 =
weeks without any error in that time, but reproducable showed ahcich=20
timeouts (with the newer ahci.ko) if load was higher than about 50MB/s=20
@raizd with 3 disks (same ICH9)
So if I got my problem solved by replacing my HDDs (even the old one had =
the latest firmware) ans also got triple performance :))
Just to share the info.
Thanks,
-Harry
--------------enig43C912A24C95AA60A133E470
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
iEYEARECAAYFAkur7BQACgkQLDqVQ9VXb8gEhwCgnuIk7hCb5UG/w/vH8aQZ4iPk
jbgAnii5epltON0RxQwo52oE96ihSzIK
=VLpd
-----END PGP SIGNATURE-----
--------------enig43C912A24C95AA60A133E470--
From owner-freebsd-stable@FreeBSD.ORG Fri Mar 26 04:24:25 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8EDFB106566B;
Fri, 26 Mar 2010 04:24:25 +0000 (UTC)
(envelope-from smithi@nimnet.asn.au)
Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159])
by mx1.freebsd.org (Postfix) with ESMTP id D6AF28FC17;
Fri, 26 Mar 2010 04:24:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o2Q4OL16016904;
Fri, 26 Mar 2010 15:24:22 +1100 (EST)
(envelope-from smithi@nimnet.asn.au)
Date: Fri, 26 Mar 2010 15:24:20 +1100 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: John Long <fbsd2@sstec.com>
In-Reply-To: <5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
Message-ID: <20100326004840.M30338@sola.nimnet.asn.au>
References: <1269310984.00232724.1269300005@10.7.7.3>
<1269310984.00232724.1269300005@10.7.7.3>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Alexander Motin <mav@freebsd.org>,
FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 04:24:25 -0000
On Wed, 24 Mar 2010, John Long wrote:
> 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.
I'm interested in this apparently strange finding. Can you show sysctl
dev.cpu after boot but before running powerd, and after starting powerd?
I wonder particularly what dev.cpu.o.freq is before running powerd, ie
whether it boots up at full speed? We've seen some that haven't,
perhaps influenced by BIOS settings?
Turning on debug.cpufreq.verbose and hw.acpi.verbose may add clues?
> >> It shows that the freq is controlled well, goes down to 365 mhz but
> >> the tdp is not decreased, rather it increases.
Yes you're only getting p4tcc throttling as Alexander points out. You'll
need to get est working to get power reduction from lower frequencies,
which likely won't correspond to these f/8 step throttling frequencies.
As Jeremy suggested, here's how to turn throttling off, and something
like what you could expect with est working:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055666.html
> >> 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?
If powerd were actually reducing frequency (and voltage) via est it
certainly would. Finding out why est is failing to attach on your
hardware is the only likely path to success, try focusing on that and
ignoring side issues. Have you browsed freebsd-acpi archives re this?
> >> 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.
Have you tried C2? Are you running the latest BIOS? And perhaps your
ACPI ASL may be amenable to repair, if Gigabyte ACPI is broken here?
cheers, Ian
From owner-freebsd-stable@FreeBSD.ORG Fri Mar 26 07:11:12 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F3EF0106566B
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 07:11:11 +0000 (UTC)
(envelope-from peterjeremy@acm.org)
Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au
[211.29.132.195])
by mx1.freebsd.org (Postfix) with ESMTP id 849518FC19
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 07:11:10 +0000 (UTC)
Received: from server.vk2pj.dyndns.org
(c122-106-253-149.belrs3.nsw.optusnet.com.au [122.106.253.149])
by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id
o2Q7B7jn009355
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 26 Mar 2010 18:11:09 +1100
X-Bogosity: Ham, spamicity=0.000000
Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])
by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id o2Q7B6vr033111;
Fri, 26 Mar 2010 18:11:06 +1100 (EST)
(envelope-from peter@server.vk2pj.dyndns.org)
Received: (from peter@localhost)
by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id o2Q7B6Xv033110;
Fri, 26 Mar 2010 18:11:06 +1100 (EST) (envelope-from peter)
Date: Fri, 26 Mar 2010 18:11:06 +1100
From: Peter Jeremy <peterjeremy@acm.org>
To: Nezmer <bsd@nezmer.info>
Message-ID: <20100326071106.GB32799@server.vk2pj.dyndns.org>
References: <20100325193127.GA80926@mail>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="i0/AhcQY5QxfSsSZ"
Content-Disposition: inline
In-Reply-To: <20100325193127.GA80926@mail>
X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc
User-Agent: Mutt/1.5.20 (2009-06-14)
X-CMAE-Score: 0
Cc: freebsd-stable@freebsd.org
Subject: Re: 8-STABLE/amd64: kernel panic after a minute of mounting xfs
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 07:11:12 -0000
--i0/AhcQY5QxfSsSZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2010-Mar-25 21:32:10 +0200, Nezmer <bsd@nezmer.info> wrote:
>This is the 1st time FreeBSD panics on me. It happened after a
>minute of mounting an XFS partition. I'm not sure It's XFS but It's the
>only part of the OS I try for the 1st time.
>
>kernel: vn_iowait doing nothing on FreeBSD?
This is part of XFS. I'm not sure how important it is.
>kernel: Fatal trap 12: page fault while in kernel mode
=2E..
>kernel: Cannot dump. Device not defined or unavailable.
Unfortunately, there's not much that can be done given this
information. As a minimum, you need a backtrace. Ideally, you need a
core-dump to investigate the cause.
See http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ke=
rneldebug.html
--=20
Peter Jeremy
--i0/AhcQY5QxfSsSZ
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iEYEARECAAYFAkusXgoACgkQ/opHv/APuIfyrACgr6xlk5s4usDxaz4bGIPELGEs
QzgAn3FZMZ6GzwCOmcb6dDZey1w2MYDO
=4lWp
-----END PGP SIGNATURE-----
--i0/AhcQY5QxfSsSZ--
From owner-freebsd-stable@FreeBSD.ORG Fri Mar 26 08:20:44 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id ECE681065670;
Fri, 26 Mar 2010 08:20:43 +0000 (UTC) (envelope-from fbsd2@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id 690098FC16;
Fri, 26 Mar 2010 08:20:43 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2Q8KcOe024439;
Fri, 26 Mar 2010 01:20:41 -0700 (PDT) (envelope-from fbsd2@sstec.com)
Message-Id: <5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
X-Sender:
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Fri, 26 Mar 2010 01:20:19 -0700
To: Ian Smith <smithi@nimnet.asn.au>
From: John Long <fbsd2@sstec.com>
In-Reply-To: <20100326004840.M30338@sola.nimnet.asn.au>
References: <5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<1269310984.00232724.1269300005@10.7.7.3>
<1269310984.00232724.1269300005@10.7.7.3>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Alexander Motin <mav@freebsd.org>,
FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 08:20:44 -0000
At 09:24 PM 3/25/2010, Ian Smith wrote:
>On Wed, 24 Mar 2010, John Long wrote:
> > 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.
>
>I'm interested in this apparently strange finding. Can you show sysctl
>dev.cpu after boot but before running powerd, and after starting powerd?
>
>I wonder particularly what dev.cpu.o.freq is before running powerd, ie
>whether it boots up at full speed? We've seen some that haven't,
>perhaps influenced by BIOS settings?
Bios is most recent re their site. F6 I believe. boots to same 41 watts.
%sysctl dev.cpu
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: 2933
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
%powerd -n adp
about 3 secs later
%sysctl dev.cpu
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: 1833
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
wait about 10 more sec and it is down to min freq and pwr is up to 44 watts.
%sysctl dev.cpu
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: 366
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
>Turning on debug.cpufreq.verbose and hw.acpi.verbose may add clues?
Either of the above makes no change in dev.cpu out but sysctl -a gets
really noisy in places
cpufreq: dup done, inserting new level 1833 after 2199
cpufreq: expand set added rel setting 62% to 1833 level
cpufreq: dup set considering derived setting 1466
cpufreq: removed last relative driver: p4tcc1
cpufreq: dup done, inserting new level 1466 after 1833
cpufreq: expand set added rel setting 50% to 1466 level
cpufreq: dup set considering derived setting 1099
cpufreq: removed last relative driver: p4tcc1
cpufreq: dup done, inserting new level 1099 after 1466
cpufreq: expand set added rel setting 37% to 1099 level
cpufreq: dup set considering derived setting 733
cpufreq: removed last relative driver: p4tcc1
cpufreq: dup done, inserting new level 733 after 1099
cpufreq: expand set added rel setting 25% to 733 level
cpufreq: dup set considering derived setting 366
cpufreq: removed last relative driver: p4tcc1
cpufreq: dup done, inserting new level 366 after 733
cpufreq: expand set added rel setting 12% to 366 level
cpufreq: setting rel freq 10000 on p4tcc1 (cpu 1)
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: get returning known freq 2933
cpufreq: adding 8 relative settings
cpufreq: adding abs setting 2933 at head
cpufreq: expand set added rel setting 100% to 2933 level
cpufreq: dup set considering derived setting 2566
cpufreq: removed last relative driver: p4tcc0
cpufreq: dup done, inserting new level 2566 after 2933
cpufreq: expand set added rel setting 87% to 2566 level
cpufreq: dup set considering derived setting 2199
cpufreq: removed last relative driver: p4tcc0
cpufreq: dup done, inserting new level 2199 after 2566
cpufreq: expand set added rel setting 75% to 2199 level
cpufreq: dup set considering derived setting 1833
cpufreq: removed last relative driver: p4tcc0
cpufreq: dup done, inserting new level 1833 after 2199
cpufreq: expand set added rel setting 62% to 1833 level
cpufreq: dup set considering derived setting 1466
cpufreq: removed last relative driver: p4tcc0
cpufreq: dup done, inserting new level 1466 after 1833
cpufreq: expand set added rel setting 50% to 1466 level
cpufreq: dup set considering derived setting 1099
........
Hundreds of those lines, Keeps repeating, fast to slow to fast etc...
>
> > >> It shows that the freq is controlled well, goes down to 365 mhz but
> > >> the tdp is not decreased, rather it increases.
>
>Yes you're only getting p4tcc throttling as Alexander points out. You'll
>need to get est working to get power reduction from lower frequencies,
>which likely won't correspond to these f/8 step throttling frequencies.
>
>As Jeremy suggested, here's how to turn throttling off, and something
>like what you could expect with est working:
>http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055666.html
from link:
I would recommend you to disable it by setting:
hint.p4tcc.0.disabled=1
hint.acpi_throttle.0.disabled=1
I get unknown oid on both. Not sure how to disable p4tcc here. What I have
to work with.
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
Tried variations of dev instead of hint, no go.
going to c3 lowers it about a watt with powerd running to 43. c2 would be
somewhere inbetween?
%sysctl -a | grep lowest
debug.cpufreq.lowest: 0
hw.acpi.cpu.cx_lowest: C1
dev.cpu.0.cx_lowest: C1
dev.cpu.1.cx_lowest: C1
%
%sysctl -a | grep C1
hw.acpi.cpu.cx_lowest: C1
dev.cpu.0.cx_supported: C1/1 C2/1 C3/150
dev.cpu.0.cx_lowest: C1
dev.cpu.1.cx_supported: C1/1 C2/1 C3/150
dev.cpu.1.cx_lowest: C1
%
%sysctl hw.acpi.cpu.cx_lowest=C2
hw.acpi.cpu.cx_lowest: C1 -> C2
42/43 watts now
%sysctl dev.cpu.0.cx_lowest=C2
dev.cpu.0.cx_lowest: C2 -> C2
%sysctl dev.cpu.1.cx_lowest=C2
dev.cpu.1.cx_lowest: C2 -> C2
no other change with above 2 lines.
%killall powerd
It drops to 41 watts while still in C2
>
> > >> 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?
>
>If powerd were actually reducing frequency (and voltage) via est it
>certainly would. Finding out why est is failing to attach on your
>hardware is the only likely path to success, try focusing on that and
>ignoring side issues. Have you browsed freebsd-acpi archives re this?
Sounds right, I did not find the est code yet to peruse it some. Otherwise
I am out of clues on what to do.
> > >> 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.
>
>Have you tried C2? Are you running the latest BIOS? And perhaps your
>ACPI ASL may be amenable to repair, if Gigabyte ACPI is broken here?
Changes to the asl are a bit more than I would want to get into. If I can
find the est code then I might dig further..
Bios is most recent, has EIST, c1e and c2e I believe enabled. That seems to
do the best all by itself. Maybe It does no good to beat a dead horse??
:-) I see an ITE IT8718F-S chip on board. mbmon does work somewhat but its
code is way old and does not see the newer chip versions. some good docs
with mbmon in usr/local/share/docs tho..
%mbmon -d -A
Summary of Detection:
* ISA monitor(s):
** Nat.Semi.Con. Chip LM78 found.
** Int.Tec.Exp. Chip IT8705F/IT8712F or SIS950 found
vcore is 1.14 now but most of the rest are not correct readings. It is 1.28
without bios settings enabled.
It never gets lower. Probably if I declock it below 2.93. 1.05 is what I
was hoping to go down to or lower at 365mhz.
%mbmon
Temp.= 191.0, 0.0, 0.0; Rot.= 874, 3358, 2657
Vcore = 1.14, 1.92; Volt. = 3.31, 4.92, 1.09, -14.19, -6.12
Temp.= 191.0, 0.0, 0.0; Rot.= 874, 3358, 2657
Vcore = 1.15, 1.92; Volt. = 3.31, 4.92, 1.09, -14.19, -6.12
%
%powerd -n adp
%mbmon
Temp.= 191.0, 0.0, 0.0; Rot.= 874, 3358, 2657
Vcore = 1.18, 1.92; Volt. = 3.31, 4.92, 1.22, -14.19, -6.12
Temp.= 191.0, 0.0, 0.0; Rot.= 874, 3358, 2657
Vcore = 1.14, 1.92; Volt. = 3.31, 4.92, 1.16, -14.19, -6.12
It jumped up in vcore a little there with powerd. C1E and C2E which include
P-states are what I am really after and I think that the bios by itself
provides those changes better than any other changes in these settings.
>
>cheers, Ian
Thanks to everyone that responded.
John
From owner-freebsd-stable@FreeBSD.ORG Fri Mar 26 08:31:45 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 128DB106566B
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 08:31:45 +0000 (UTC)
(envelope-from mavbsd@gmail.com)
Received: from mail-fx0-f225.google.com (mail-fx0-f225.google.com
[209.85.220.225])
by mx1.freebsd.org (Postfix) with ESMTP id 900AE8FC14
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 08:31:44 +0000 (UTC)
Received: by fxm25 with SMTP id 25so102501fxm.3
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 01:31:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:message-id:date:from
:user-agent:mime-version:to:cc:subject:references:in-reply-to
:x-enigmail-version:content-type:content-transfer-encoding;
bh=M9TK1a5uaywNFQZ2gdpRuPNG6Gp1hg9LiBs5EHMMxYk=;
b=tHBPZp9f2kQefs/JfimeFdLROmtyn8YIXZR9sYqKglLLa4N6/5LDtAvFVHtghh0CyW
Kh41CNqd6I22dkEUpvGO4Z247sDjLgWlI1LpCIsTTMB49hFFMRTCDTWR0QNbYOUQl9ew
08Tl1Zb/iau+yfAoQLHCa6x6jBBQPScwvki0Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject
:references:in-reply-to:x-enigmail-version:content-type
:content-transfer-encoding;
b=wqHviV/IuZAqIjkqLRhFQdHLLYqdAodoIM5vGyo7QhsY3jva0wvAuipTTLW4pemt+S
hlzj1QpiTRAdAto5xT90pRhlLVsKGIdif7xUQgkKH5rvD+ik20pcMMcheHW1ktCumekg
l0w5khBrB+8NeuwinWCf54ZlHmxi8V4+nKrZ8=
Received: by 10.223.64.84 with SMTP id d20mr515403fai.76.1269592303318;
Fri, 26 Mar 2010 01:31:43 -0700 (PDT)
Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226])
by mx.google.com with ESMTPS id 16sm461047fxm.8.2010.03.26.01.31.41
(version=SSLv3 cipher=RC4-MD5); Fri, 26 Mar 2010 01:31:42 -0700 (PDT)
Sender: Alexander Motin <mavbsd@gmail.com>
Message-ID: <4BAC70EB.5020606@FreeBSD.org>
Date: Fri, 26 Mar 2010 10:31:39 +0200
From: Alexander Motin <mav@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.23 (X11/20091212)
MIME-Version: 1.0
To: John Long <fbsd2@sstec.com>
References: <5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<1269310984.00232724.1269300005@10.7.7.3>
<1269310984.00232724.1269300005@10.7.7.3>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
In-Reply-To: <5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 08:31:45 -0000
John Long wrote:
>>Have you tried C2? Are you running the latest BIOS? And perhaps your
>>ACPI ASL may be amenable to repair, if Gigabyte ACPI is broken here?
As I can see, your ACPI reports C3 state support. You may try it also.
Here is my notes about power and C3 also:
http://wiki.freebsd.org/TuningPowerConsumption
--
Alexander Motin
From owner-freebsd-stable@FreeBSD.ORG Fri Mar 26 09:14:49 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DA6F91065672
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 09:14:49 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from qmta05.emeryville.ca.mail.comcast.net
(qmta05.emeryville.ca.mail.comcast.net [76.96.30.48])
by mx1.freebsd.org (Postfix) with ESMTP id BD2D28FC17
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 09:14:49 +0000 (UTC)
Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90])
by qmta05.emeryville.ca.mail.comcast.net with comcast
id xlDT1d0021wfjNsA5lEq8q; Fri, 26 Mar 2010 09:14:50 +0000
Received: from koitsu.dyndns.org ([98.248.46.159])
by omta23.emeryville.ca.mail.comcast.net with comcast
id xlEp1d0013S48mS8jlEplp; Fri, 26 Mar 2010 09:14:50 +0000
Received: by icarus.home.lan (Postfix, from userid 1000)
id B04489B436; Fri, 26 Mar 2010 02:14:47 -0700 (PDT)
Date: Fri, 26 Mar 2010 02:14:47 -0700
From: Jeremy Chadwick <freebsd@jdc.parodius.com>
To: John Long <fbsd2@sstec.com>
Message-ID: <20100326091447.GA91547@icarus.home.lan>
References: <5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<1269310984.00232724.1269300005@10.7.7.3>
<1269310984.00232724.1269300005@10.7.7.3>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Alexander Motin <mav@freebsd.org>,
FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>,
Ian Smith <smithi@nimnet.asn.au>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 09:14:49 -0000
On Fri, Mar 26, 2010 at 01:20:19AM -0700, John Long wrote:
> >Yes you're only getting p4tcc throttling as Alexander points out. You'll
> >need to get est working to get power reduction from lower frequencies,
> >which likely won't correspond to these f/8 step throttling frequencies.
> >
> >As Jeremy suggested, here's how to turn throttling off, and something
> >like what you could expect with est working:
> >http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055666.html
>
> from link:
> I would recommend you to disable it by setting:
> hint.p4tcc.0.disabled=1
> hint.acpi_throttle.0.disabled=1
>
> I get unknown oid on both. Not sure how to disable p4tcc here. What
> I have to work with.
These are /boot/loader.conf tunables, not sysctl. I'm pretty sure I
stated that in my previous mail...?
> Bios is most recent, has EIST, c1e and c2e I believe enabled. That
> seems to do the best all by itself. Maybe It does no good to beat a
> dead horse?? :-) I see an ITE IT8718F-S chip on board. mbmon does
> work somewhat but its code is way old and does not see the newer
> chip versions. some good docs with mbmon in usr/local/share/docs
> tho..
> %mbmon -d -A
> Summary of Detection:
> * ISA monitor(s):
> ** Nat.Semi.Con. Chip LM78 found.
> ** Int.Tec.Exp. Chip IT8705F/IT8712F or SIS950 found
>
> vcore is 1.14 now but most of the rest are not correct readings. It
> is 1.28 without bios settings enabled.
> It never gets lower. Probably if I declock it below 2.93. 1.05 is
> what I was hoping to go down to or lower at 365mhz.
>
> %mbmon
> Temp.= 191.0, 0.0, 0.0; Rot.= 874, 3358, 2657
> Vcore = 1.14, 1.92; Volt. = 3.31, 4.92, 1.09, -14.19, -6.12
>
> Temp.= 191.0, 0.0, 0.0; Rot.= 874, 3358, 2657
> Vcore = 1.15, 1.92; Volt. = 3.31, 4.92, 1.09, -14.19, -6.12
> %
> %powerd -n adp
> %mbmon
> Temp.= 191.0, 0.0, 0.0; Rot.= 874, 3358, 2657
> Vcore = 1.18, 1.92; Volt. = 3.31, 4.92, 1.22, -14.19, -6.12
>
> Temp.= 191.0, 0.0, 0.0; Rot.= 874, 3358, 2657
> Vcore = 1.14, 1.92; Volt. = 3.31, 4.92, 1.16, -14.19, -6.12
Ignore all of the above values -- mbmon doesn't work properly with your
board, or that sub-revision of IT chip. It's that simple. Re-read the
rant I sent you for explanation; I already covered all the bases. :-) I
disagree about the mbmon docs -- they're more like chaotic brain dumps
or scribbled notes than actual coherent, well-written instructions or
details. That said, I have utmost respect for SHIMIZU Yoshifumi and his
efforts/work.
I'm willing to make an exception here. If you can get the following
information from the motherboard manufacturer, I'd be willing to add
support for your board to bsdhwmon. What I need:
1) The exact H/W monitoring IC they use (not what mbmon says, and
not what's silkscreened on the chip),
2) If the H/W monitoring IC is tied in to SMBus,
3) What the SMBus slave address is they chose for the H/W IC
4) Output of "kenv | grep smbios" from your system.
Assuming all of the above meets necessary criteria, I can probably add
support for this board to bsdhwmon. I have only slight qualms/concerns
adding consumer boards to bsdhwmon, but the big kicker is that the board
**must** have an actual H/W monitoring IC tied/wired to SMBus. I *will
not* use the old LPC/ISA (/dev/io) infrastructure.
> It jumped up in vcore a little there with powerd. C1E and C2E which
> include P-states are what I am really after and I think that the
> bios by itself provides those changes better than any other changes
> in these settings.
...and this would fall under the est(4) subset driver for cpufreq(4).
--
| Jeremy Chadwick jdc@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Fri Mar 26 10:08:36 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 7BE9F106566B;
Fri, 26 Mar 2010 10:08:36 +0000 (UTC)
(envelope-from auryn@zirakzigil.org)
Received: from mail.zirakzigil.org (mail.zirakzigil.org [82.63.178.63])
by mx1.freebsd.org (Postfix) with ESMTP id 278C08FC19;
Fri, 26 Mar 2010 10:08:35 +0000 (UTC)
Received: from localhost (unknown [192.168.1.2])
by mail.zirakzigil.org (Postfix) with ESMTP id 0E17E94FF9;
Fri, 26 Mar 2010 11:08:34 +0100 (CET)
X-Virus-Scanned: amavisd-new at zirakzigil.org
Received: from mail.zirakzigil.org ([192.168.1.2])
by localhost (ext.zirakzigil.org [192.168.1.2]) (amavisd-new,
port 10024)
with ESMTP id DCJftBbxsp0S; Fri, 26 Mar 2010 11:08:31 +0100 (CET)
Received: from aurynmob2.giulioferro.it (unknown [192.168.1.2])
(Authenticated sender: auryn@zirakzigil.org)
by mail.zirakzigil.org (Postfix) with ESMTPA id AA41594FEE;
Fri, 26 Mar 2010 11:08:31 +0100 (CET)
Message-ID: <4BAC879A.2040301@zirakzigil.org>
Date: Fri, 26 Mar 2010 11:08:26 +0100
From: Giulio Ferro <auryn@zirakzigil.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
rv:1.9.1.7) Gecko/20100223 Thunderbird/3.0.1
MIME-Version: 1.0
To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>,
freebsd-stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc:
Subject: NFS lockd problem
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 10:08:36 -0000
Outset:
1 NFS server (with lockd)
2 NFS client (with lockd)
The clients serve several jails with apache, whose data (www) resides on
the server
From time to time everything seem to freeze. Then, after one minute or
so, the system
works again as nothing had happened.
In these occasions I get this in the logs on the client madchines:
Mar 26 10:29:38 virt1 kernel: nfs server
192.168.40.121:/data/mount_servers/wwwsec/www: lockd not responding
followed shortly after by:
Mar 26 10:29:38 virt1 kernel: nfs server
192.168.40.121:/data/mount_servers/wwwsec/www: lockd is alive again
On the server I only get this:
Mar 26 10:29:31 data1 kernel: NLM: failed to contact remote rpcbind,
stat = 5, port = 28416
I don't think it's a network problem, since all connections are local
and high speed (1Gb/s)
I must admit that, with the other nfs problem I reported weeks ago, this
kind of freebsd system seems
less than stable to me, and this is very disappointing...
Anyway I'd appreciate any pointer on this issue...
From owner-freebsd-stable@FreeBSD.ORG Fri Mar 26 20:09:34 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C72721065673
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 20:09:34 +0000 (UTC)
(envelope-from David.Boyd@insightbb.com)
Received: from mxsf02.insightbb.com (mxsf02.insightbb.com [74.128.0.63])
by mx1.freebsd.org (Postfix) with ESMTP id 933CD8FC1F
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 20:09:34 +0000 (UTC)
X-IronPort-AV: E=Sophos;i="4.51,316,1267419600"; d="scan'208";a="741841668"
Received: from unknown (HELO asav01.insightbb.com) ([172.31.249.123])
by mxsf02.insightbb.com with ESMTP; 26 Mar 2010 16:09:33 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FALKxrEtKgYlR/2dsb2JhbACIdpIzdL8mDYRxBA
X-IronPort-AV: E=Sophos;i="4.51,315,1267419600"; d="scan'208";a="251623796"
Received: from 74-129-137-81.dhcp.insightbb.com (HELO sneezy) ([74.129.137.81])
by asav01.insightbb.com with SMTP; 26 Mar 2010 16:09:33 -0400
From: "David Boyd" <David.Boyd@insightbb.com>
To: <freebsd-stable@freebsd.org>
Date: Fri, 26 Mar 2010 16:09:33 -0400
Message-ID: <OJEBKOFDEOADELCOBJCGEELPCOAA.David.Boyd@insightbb.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: 7.3-RELEASE make release requires wrong version of perl
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 20:09:34 -0000
Attempting make release results in error complaining that perl-5.8.9
installs into the same locations as perl-5.10.1.
This seems similar to the problem I encountered with make release when NODOC
was not set.
The complaint then was that ghostscript8-nox11 installs into the same
locations as ghostscrip8.
Any help would be appreciated.
Thanks.
From owner-freebsd-stable@FreeBSD.ORG Fri Mar 26 23:47:48 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 87618106564A;
Fri, 26 Mar 2010 23:47:48 +0000 (UTC) (envelope-from fbsd2@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id 42A7A8FC0C;
Fri, 26 Mar 2010 23:47:47 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2QNlilb051541;
Fri, 26 Mar 2010 16:47:47 -0700 (PDT) (envelope-from fbsd2@sstec.com)
Message-Id: <5.2.1.1.2.20100326161613.0316fc28@mail.sstec.com>
X-Sender:
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Fri, 26 Mar 2010 16:46:40 -0700
To: Alexander Motin <mav@FreeBSD.org>
From: John Long <fbsd2@sstec.com>
In-Reply-To: <4BAC70EB.5020606@FreeBSD.org>
References: <5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<1269310984.00232724.1269300005@10.7.7.3>
<1269310984.00232724.1269300005@10.7.7.3>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@FreeBSD.org>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 23:47:48 -0000
At 01:31 AM 3/26/2010, Alexander Motin wrote:
>John Long wrote:
>>>Have you tried C2? Are you running the latest BIOS? And perhaps your
>>>ACPI ASL may be amenable to repair, if Gigabyte ACPI is broken here?
>
>As I can see, your ACPI reports C3 state support. You may try it also.
>Here is my notes about power and C3 also:
>http://wiki.freebsd.org/TuningPowerConsumption
>Alexander Motin
Hi, you have achieved good results with your laptop tuning, 50% power
reduction.
I tried the disable thing and got what I thought would happen.
hint.p4tcc.0.disabled=1
hint.acpi_throttle.0.disabled=1
Since est is not working on this system then it falls back to p4tcc and
throttle but if they are disabled then powerd chokes with "lookup freq: no
such file or directory" and does not run.
I did locate est.c under cpufreq dir. It looks to be from 2004/5 era and
alas the cpu lookups in there are most all from that time frame also. I
find this bit of code:
/*
* Probe for supported CPU settings. First, check our static table of
* settings. If no match, try using the ones offered by acpi_perf
* (i.e., _PSS). We use ACPI second because some systems (IBM R/T40
* series) export both legacy SMM IO-based access and direct MSR access
* but the direct access specifies invalid values for _PSS.
*/
static int
est_get_info(device_t dev)
{
struct est_softc *sc;
uint64_t msr;
int error;
sc = device_get_softc(dev);
msr = rdmsr(MSR_PERF_STATUS);
error = est_table_info(dev, msr, &sc->freq_list);
if (error)
error = est_acpi_info(dev, &sc->freq_list);
if (error)
error = est_msr_info(dev, msr, &sc->freq_list);
if (error) {
printf(
"est: CPU supports Enhanced Speedstep, but is not recognized.\n"
"est: cpu_vendor %s, msr %0jx\n", cpu_vendor, msr);
return (ENXIO);
}
return (0);
}
Therein looks to be the problem, the msr table/freq_list lookup is just way
out of date and fails to load est and therefore the fallback to p4tcc for
powerd which is useless for reduction. I need to get est running so that it
handles the P-states which include the voltage reduction. There are a
couple other places where it tests and sets flags that may be relevant but
it is a little bit more work and a little over my head than I was looking
for. Maybe ACPI is just not giving enough info and the asl can be modified
but I do not know enough about it or much of any of this.. There is a whole
box of worms in acpica dir. I looked thru acpi_perf.c but the rabbit trail
looks a bit daunting. There are briar patches throughout.
Maybe Colin Percival or Nate Lawson can shed some light on this and if it
is reasonable to do an update for that bit of code/table. If there were a
prog that could invoke est.c and have it spit out the factors it sees for a
clue as to just what might be needed to get it loaded, that would be helpful.
>> est: CPU supports Enhanced Speedstep, but is not recognized.
>> est: cpu_vendor GenuineIntel, msr 6160b2506000b25
is meaningless to me :-(
I do realize that there have been hundreds of cpus and factors since that
time, maybe a wildcard lookup of some sort would suffice. To just get this
thing loaded because the rest of the code looks clever and good. Also, if
some discovery here helps the project and saves a few watts times thousands
of us then it might be worth pursuing but if the general consensus is not
worth the trouble then I understand.
John
btw: I had tried C3 earlier and C2 also, they both save about 1 watt max
and C3 is quite a dramatic thing to do considering the crucial parts of the
system it shuts down. For a laptop that would be okay but this is going to
be a relatively busy server running dns, apache, nat etc. I do not think it
will have much time to sleep but with the speed of a c2d it will not been
too busy either, always just a few percent. Therein lies my desire, to get
the voltage down when the freq is low and still allow demand speed to be
there if needed.
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 00:18:32 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 23758106566B
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 00:18:32 +0000 (UTC)
(envelope-from bc979@lafn.org)
Received: from zoom.lafn.org (zoom.lafn.ORG [206.117.18.8])
by mx1.freebsd.org (Postfix) with ESMTP id C6CF88FC28
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 00:18:31 +0000 (UTC)
Received: from [10.0.1.4] (pool-71-109-144-133.lsanca.dsl-w.verizon.net
[71.109.144.133]) (authenticated bits=0)
by zoom.lafn.org (8.14.3/8.14.2) with ESMTP id o2R0IUYf041990
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
for <freebsd-stable@freebsd.org>; Fri, 26 Mar 2010 17:18:31 -0700 (PDT)
(envelope-from bc979@lafn.org)
From: Doug Hardie <bc979@lafn.org>
Content-Type: text/plain; charset=us-ascii
Message-Id: <548D66CF-4FAA-4D4D-949E-6D2CC509D069@lafn.org>
Date: Fri, 26 Mar 2010 17:18:30 -0700
To: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v1077)
X-Mailer: Apple Mail (2.1077)
X-Virus-Scanned: clamav-milter 0.95.3 at zoom.lafn.org
X-Virus-Status: Clean
Subject: FreeBSD 8.0 SCSI Boot
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 00:18:32 -0000
I tried to upgrade a 7.2 system to 8.0. It uses a SCSI drive. It works =
fine on 7.2. However, it would appear that during the upgrade process =
when running make delete-old (?) there is a note about make =
delete-old-libs (?). Don't do that at that point. End of system. Make =
installworld fails miserably. Unfortunately rebooting caused numerous =
problems. First the /etc/fstab was listed as corrupt. Then it quit =
booting altogether. A complete reload from the disc 1 goes nowhere =
either. It installs just fine but when it goes to reboot, All I get is =
F1 followed by a bunch of increasing #s. Any key just adds more to the =
list. I have tried with both the standard and FreeBSD boot managers =
with the same result. Is there anyway to get it to boot off the SCSI =
drive? I couldn't find anything related to this in the forums etc.=
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 05:35:40 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6EDD3106564A;
Sat, 27 Mar 2010 05:35:40 +0000 (UTC)
(envelope-from smithi@nimnet.asn.au)
Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159])
by mx1.freebsd.org (Postfix) with ESMTP id DC36F8FC12;
Sat, 27 Mar 2010 05:35:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o2R5ZaIV089393;
Sat, 27 Mar 2010 16:35:36 +1100 (EST)
(envelope-from smithi@nimnet.asn.au)
Date: Sat, 27 Mar 2010 16:35:36 +1100 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
In-Reply-To: <20100326091447.GA91547@icarus.home.lan>
Message-ID: <20100327153102.X30338@sola.nimnet.asn.au>
References: <5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<1269310984.00232724.1269300005@10.7.7.3>
<1269310984.00232724.1269300005@10.7.7.3>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
<20100326091447.GA91547@icarus.home.lan>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Alexander Motin <mav@freebsd.org>,
FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 05:35:40 -0000
On Fri, 26 Mar 2010, Jeremy Chadwick wrote:
[ leaving the MB monitoring stuff alone for your expert attention :-]
> > It jumped up in vcore a little there with powerd. C1E and C2E which
> > include P-states are what I am really after and I think that the
> > bios by itself provides those changes better than any other changes
> > in these settings.
>
> ...and this would fall under the est(4) subset driver for cpufreq(4).
Just checking, I know nothing about these so far, but are you suggesting
that John having C1E and C2E enabled in BIOS may be affecting ACPI/EST
detection, and that things may be different were these disabled?
If that's not what you meant, could you expand a little?
John: you may want to explore where this comes together in kern_cpu.c
where you'll see those cpufreq debugging messages you quoted. Some of
the more gritty documentation may be found browsing with something like:
% less /sys/{sys,kern,amd64/include}/*cpu*.[ch]
cheers, Ian
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 07:08:30 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A25ED106566C;
Sat, 27 Mar 2010 07:08:30 +0000 (UTC) (envelope-from stb@lassitu.de)
Received: from gilb.zs64.net (gilb.zs64.net [212.12.50.234])
by mx1.freebsd.org (Postfix) with ESMTP id 679C28FC0C;
Sat, 27 Mar 2010 07:08:30 +0000 (UTC)
Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 7FA0E5A864;
Sat, 27 Mar 2010 08:08:28 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Stefan Bethke <stb@lassitu.de>
In-Reply-To: <20100310110202.GA1715@garage.freebsd.pl>
Date: Sat, 27 Mar 2010 08:08:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <807E774E-2473-422A-8C0A-3127E9AD6229@lassitu.de>
References: <864468D4-DCE9-493B-9280-00E5FAB2A05C@lassitu.de>
<20100309122954.GE3155@garage.freebsd.pl>
<EC9BC6B4-8D0E-4FE3-852F-0E3A24569D33@sarenet.es>
<20100309125815.GF3155@garage.freebsd.pl>
<CB854F58-03AF-46DD-8153-85FA96037C21@sarenet.es>
<BFF1E2D6-B48A-4A5E-ACEE-8577FDB07820@sarenet.es>
<20100310110202.GA1715@garage.freebsd.pl>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
X-Mailer: Apple Mail (2.1077)
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: Many processes stuck in zfs
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 07:08:30 -0000
Am 10.03.2010 um 12:02 schrieb Pawel Jakub Dawidek:
> Once the deadlock occur, enter DDB and send me the output of:
>=20
> ps
> show alllocks
> show lockedvnods
> show allchains
> alltrace
panic: deadlkres: possible deadlock detected for 0xffffff000c66e000, =
blocked for 1801490 ticks
I've saved a core, and can try to look at more things. The text dump is =
at http://www.lassitu.de/freebsd/core.txt.13
show alllocks and show lockedvnods only gave me a "no such command" =
error. Otherwise, the full output is at =
http://www.lassitu.de/freebsd/zfs_panic.txt.
Thanks,
Stefan
--=20
Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 16:02:07 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 32D93106566B
for <freebsd-stable@FreeBSD.org>; Sat, 27 Mar 2010 16:02:07 +0000 (UTC)
(envelope-from freebsd-stable@chef-ingenieur.de)
Received: from mail.webmatic.de (mail.webmatic.de [212.78.101.66])
by mx1.freebsd.org (Postfix) with ESMTP id E863B8FC18
for <freebsd-stable@FreeBSD.org>; Sat, 27 Mar 2010 16:02:06 +0000 (UTC)
Received: from [192.168.178.25] (p5B0F5FD4.dip.t-dialin.net [91.15.95.212])
by mail.webmatic.de (Postfix) with ESMTPSA id 8E6C96D43E
for <freebsd-stable@FreeBSD.org>; Sat, 27 Mar 2010 16:45:12 +0100 (CET)
Message-ID: <4BAE2808.4010809@chef-ingenieur.de>
Date: Sat, 27 Mar 2010 16:45:12 +0100
From: Thomas Krause <freebsd-stable@chef-ingenieur.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de;
rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-stable <freebsd-stable@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Cc:
Subject: freebsd-update 7.2->7.3 manul merging of all files
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 16:02:07 -0000
Hi,
I want to upgrade a 7.2-RELEASE-p4 to 7.3-RELEASE with the command
# freebsd-update upgrade -r 7.3-RELEASE
After fetching and patching I get
Attempting to automatically merge changes in files... done.
The following file could not be merged automatically: /boot/device.hints
Press Enter to edit this file in vi and resolve the conflicts
manually...
this goes on with *every* file in the /etc directory. What's wrong here?
Best regards,
Thomas.
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 18:50:22 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1983F1065672;
Sat, 27 Mar 2010 18:50:22 +0000 (UTC) (envelope-from cswiger@mac.com)
Received: from asmtpout024.mac.com (asmtpout024.mac.com [17.148.16.99])
by mx1.freebsd.org (Postfix) with ESMTP id 0396C8FC1D;
Sat, 27 Mar 2010 18:50:21 +0000 (UTC)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.151.93.190] by asmtp024.mac.com
(Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008;
32bit)) with ESMTPSA id <0KZY00LJ6EZU5S00@asmtp024.mac.com>; Sat,
27 Mar 2010 11:50:21 -0700 (PDT)
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam
adjust=0
reason=mlx engine=5.0.0-0908210000 definitions=main-1003270119
From: Chuck Swiger <cswiger@mac.com>
In-reply-to: <4BAC879A.2040301@zirakzigil.org>
Date: Sat, 27 Mar 2010 11:50:17 -0700
Message-id: <4931283F-5B5B-4368-BB40-20B5FEBF4E17@mac.com>
References: <4BAC879A.2040301@zirakzigil.org>
To: Giulio Ferro <auryn@zirakzigil.org>
X-Mailer: Apple Mail (2.1078)
Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>,
freebsd-stable@freebsd.org
Subject: Re: NFS lockd problem
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 18:50:22 -0000
On Mar 26, 2010, at 3:08 AM, Giulio Ferro wrote:
> Outset:
> 1 NFS server (with lockd)
> 2 NFS client (with lockd)
>
> The clients serve several jails with apache, whose data (www) resides on the server
If you need file locking to work reliably, you pretty much have to give up on using NFS + rpc.lockd and run against a local UFS filesystem.
Regards,
--
-Chuck
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 19:04:42 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3B8871065670
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 19:04:42 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from qmta03.westchester.pa.mail.comcast.net
(qmta03.westchester.pa.mail.comcast.net [76.96.62.32])
by mx1.freebsd.org (Postfix) with ESMTP id DEEB18FC08
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 19:04:41 +0000 (UTC)
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35])
by qmta03.westchester.pa.mail.comcast.net with comcast
id yHka1d0030ldTLk53K2iX2; Sat, 27 Mar 2010 19:02:42 +0000
Received: from koitsu.dyndns.org ([98.248.46.159])
by omta04.westchester.pa.mail.comcast.net with comcast
id yK4h1d0023S48mS3QK4hnC; Sat, 27 Mar 2010 19:04:41 +0000
Received: by icarus.home.lan (Postfix, from userid 1000)
id A0A859B436; Sat, 27 Mar 2010 12:04:39 -0700 (PDT)
Date: Sat, 27 Mar 2010 12:04:39 -0700
From: Jeremy Chadwick <freebsd@jdc.parodius.com>
To: freebsd-stable@freebsd.org
Message-ID: <20100327190439.GA45830@icarus.home.lan>
References: <4BAC879A.2040301@zirakzigil.org>
<4931283F-5B5B-4368-BB40-20B5FEBF4E17@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4931283F-5B5B-4368-BB40-20B5FEBF4E17@mac.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: NFS lockd problem
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 19:04:42 -0000
On Sat, Mar 27, 2010 at 11:50:17AM -0700, Chuck Swiger wrote:
> On Mar 26, 2010, at 3:08 AM, Giulio Ferro wrote:
> > Outset:
> > 1 NFS server (with lockd)
> > 2 NFS client (with lockd)
> >
> > The clients serve several jails with apache, whose data (www) resides on the server
>
> If you need file locking to work reliably, you pretty much have to give up on using NFS + rpc.lockd and run against a local UFS filesystem.
I thought fcntl(2) worked reliably/properly with NFS on FreeBSD? I
remember reading somewhere how mixing locking types (fcntl vs. flock vs.
lockf) causes major problems, but as long as the same locking method is
used universally things should work...?
--
| Jeremy Chadwick jdc@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 20:38:02 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 04CF6106564A
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 20:38:02 +0000 (UTC)
(envelope-from peterjeremy@acm.org)
Received: from mail35.syd.optusnet.com.au (mail35.syd.optusnet.com.au
[211.29.133.51])
by mx1.freebsd.org (Postfix) with ESMTP id 893A38FC08
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 20:38:01 +0000 (UTC)
Received: from server.vk2pj.dyndns.org
(c122-106-253-149.belrs3.nsw.optusnet.com.au [122.106.253.149])
by mail35.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id
o2RKboi8010760
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Sun, 28 Mar 2010 07:37:58 +1100
X-Bogosity: Ham, spamicity=0.000000
Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])
by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id o2RKbojA014158;
Sun, 28 Mar 2010 07:37:50 +1100 (EST)
(envelope-from peter@server.vk2pj.dyndns.org)
Received: (from peter@localhost)
by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id o2RKbnDw014157;
Sun, 28 Mar 2010 07:37:49 +1100 (EST) (envelope-from peter)
Date: Sun, 28 Mar 2010 07:37:49 +1100
From: Peter Jeremy <peterjeremy@acm.org>
To: Doug Hardie <bc979@lafn.org>
Message-ID: <20100327203749.GH32799@server.vk2pj.dyndns.org>
References: <548D66CF-4FAA-4D4D-949E-6D2CC509D069@lafn.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="uAgJxtfIS94j9H4T"
Content-Disposition: inline
In-Reply-To: <548D66CF-4FAA-4D4D-949E-6D2CC509D069@lafn.org>
X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc
User-Agent: Mutt/1.5.20 (2009-06-14)
X-CMAE-Score: 0
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: FreeBSD 8.0 SCSI Boot
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 20:38:02 -0000
--uAgJxtfIS94j9H4T
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2010-Mar-26 17:18:30 -0700, Doug Hardie <bc979@lafn.org> wrote:
>I tried to upgrade a 7.2 system to 8.0. It uses a SCSI drive. It
>works fine on 7.2.
We will need some more details before we can help you.
> However, it would appear that during the upgrade
>process when running make delete-old (?) there is a note about make
>delete-old-libs (?). Don't do that at that point. End of system.
>Make installworld fails miserably.
You shouldn't run either "make delete-old" or "make delete-old-libs"
until you have successfully run "make installworld" - the upgrade
procedure shows delete-old after installworld. Whilst delete-old will
just make it harder to revert from a failed upgrade, running
delete-old-libs will prevent you running installworld. When you run
delete-old-libs, it warns you "Please be sure no application still
uses those libraries, else you can not start such an application."
One application that needs the old libraries is installworld.
> Unfortunately rebooting caused numerous problems.
Given that your installworld had failed - presumably leaving various
FreeBSD-7.2 files lying around, whilst you deleted the libraries
required by some of them, this is not surprising.
> First the /etc/fstab was listed as corrupt.
This is surprising. Assuming you cleanly rebooted your system, it
is very unlikely that your /etc/fstab was corrupted and is more likely
a problem with one of the mount programs.
Can you provide the exact error message and what you then did.
> Then it quit booting altogether.
If it rebooted once, there's no reason why it shouldn't reboot a
second time. What actions did you take between the two reboots and
what exactly do you mean by "quit booting"?
> A complete reload from the disc 1 goes
>nowhere either. It installs just fine but when it goes to reboot,
>All I get is F1 followed by a bunch of increasing #s. Any key just
>adds more to the list. I have tried with both the standard and
>FreeBSD boot managers with the same result.
At that point, FreeBSD is using the BIOS drivers to access the SCSI
disk. If you get the 'F1' prompt then the BIOS is correctly loading
the boot sector (so it can access the disk) so there is no obvious
reason why it isn't booting.
Do you have a copy of the dmesg from 7.2? If not, can you give us
some details about your motherboard (vendor/model), what SCSI
controller you are using, what targets are attached and what other
disks (if any) you have. Are you using a PS/2 or USB keyboard?
Can you expand on what you mean by "a complete reload" - did you do a
full install of FreeBSD 8.0, including partitioning and creating disk
slices or did you re-use the existing slices? Are you using a
"dangerously dedicated" disk? Were any disk geometry errors reported?
--=20
Peter Jeremy
--uAgJxtfIS94j9H4T
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iEYEARECAAYFAkuubJ0ACgkQ/opHv/APuIeWfQCaAuZPhiNGF4WqEmTAVQy0lgFY
naoAnAjwS5MXH4zSgXyp0W/3yPAgXkkl
=NFG3
-----END PGP SIGNATURE-----
--uAgJxtfIS94j9H4T--
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 21:10:29 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 78521106566B
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 21:10:29 +0000 (UTC)
(envelope-from bc979@lafn.org)
Received: from zoom.lafn.org (zoom.lafn.ORG [206.117.18.8])
by mx1.freebsd.org (Postfix) with ESMTP id 585918FC0C
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 21:10:29 +0000 (UTC)
Received: from [10.0.1.4] (pool-71-109-144-133.lsanca.dsl-w.verizon.net
[71.109.144.133]) (authenticated bits=0)
by zoom.lafn.org (8.14.3/8.14.2) with ESMTP id o2RLAPBZ073329
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
Sat, 27 Mar 2010 14:10:26 -0700 (PDT) (envelope-from bc979@lafn.org)
References: <548D66CF-4FAA-4D4D-949E-6D2CC509D069@lafn.org>
<20100327203749.GH32799@server.vk2pj.dyndns.org>
In-Reply-To: <20100327203749.GH32799@server.vk2pj.dyndns.org>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
Message-Id: <7E608CAE-2C4D-4C68-B06E-C1C61E8460E3@lafn.org>
Content-Transfer-Encoding: quoted-printable
From: Doug Hardie <bc979@lafn.org>
Date: Sat, 27 Mar 2010 14:10:25 -0700
To: Peter Jeremy <peterjeremy@acm.org>
X-Mailer: Apple Mail (2.1077)
X-Virus-Scanned: clamav-milter 0.95.3 at zoom.lafn.org
X-Virus-Status: Clean
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: FreeBSD 8.0 SCSI Boot
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 21:10:29 -0000
On 27 March 2010, at 13:37, Peter Jeremy wrote:
> On 2010-Mar-26 17:18:30 -0700, Doug Hardie <bc979@lafn.org> wrote:
>> I tried to upgrade a 7.2 system to 8.0. It uses a SCSI drive. It
>> works fine on 7.2.
>=20
> We will need some more details before we can help you.
>=20
>> However, it would appear that during the upgrade
>> process when running make delete-old (?) there is a note about make
>> delete-old-libs (?). Don't do that at that point. End of system.
>> Make installworld fails miserably.
>=20
> You shouldn't run either "make delete-old" or "make delete-old-libs"
> until you have successfully run "make installworld" - the upgrade
> procedure shows delete-old after installworld. Whilst delete-old will
> just make it harder to revert from a failed upgrade, running
> delete-old-libs will prevent you running installworld. When you run
> delete-old-libs, it warns you "Please be sure no application still
> uses those libraries, else you can not start such an application."
> One application that needs the old libraries is installworld.
I know that now. Probably should have before, but didn't figure it out. =
Not having access to UPDATING made writing the original message a bit =
difficult. make delete-old was run after make installworld. When it =
completes it says you can run make delete-old-libs. That is where I =
made the first mistake. I believe that message is quite misleading and =
should be removed. The first failure occurred on mergemaster not make =
installworld. It died on the second install file. The error was =
something to the effect that rw on /etc/fstab was invalid and gave the =
sysctl settings to use in boot to get around it. There was nothing =
other than a reboot possible at that point. There was no other option.
>=20
>> Unfortunately rebooting caused numerous problems.
>=20
> Given that your installworld had failed - presumably leaving various
> FreeBSD-7.2 files lying around, whilst you deleted the libraries
> required by some of them, this is not surprising.
>=20
>> First the /etc/fstab was listed as corrupt.
>=20
> This is surprising. Assuming you cleanly rebooted your system, it
> is very unlikely that your /etc/fstab was corrupted and is more likely
> a problem with one of the mount programs.
>=20
> Can you provide the exact error message and what you then did.
that information is long gone.
>=20
>> Then it quit booting altogether.
>=20
> If it rebooted once, there's no reason why it shouldn't reboot a
> second time. What actions did you take between the two reboots and
> what exactly do you mean by "quit booting"?
It dies in the boot laoder with F1 followed by numeous #s.
>=20
>> A complete reload from the disc 1 goes
>> nowhere either. It installs just fine but when it goes to reboot,
>> All I get is F1 followed by a bunch of increasing #s. Any key just
>> adds more to the list. I have tried with both the standard and
>> FreeBSD boot managers with the same result.
>=20
> At that point, FreeBSD is using the BIOS drivers to access the SCSI
> disk. If you get the 'F1' prompt then the BIOS is correctly loading
> the boot sector (so it can access the disk) so there is no obvious
> reason why it isn't booting.
>=20
> Do you have a copy of the dmesg from 7.2? If not, can you give us
> some details about your motherboard (vendor/model), what SCSI
> controller you are using, what targets are attached and what other
> disks (if any) you have. Are you using a PS/2 or USB keyboard?
The 7.2 stuff is long gone. The disk has been wiped several times. =
Until I can get past the F1 issue I don't have access to the hardware =
information. It uses a PS/2 keyboard and is i386 32 bit. Its an AMD =
processor thats quite old.
>=20
> Can you expand on what you mean by "a complete reload" - did you do a
> full install of FreeBSD 8.0, including partitioning and creating disk
> slices or did you re-use the existing slices? Are you using a
> "dangerously dedicated" disk? Were any disk geometry errors reported?
Complete reload means with the live filesystem:
dd if=3D/dev/zero of=3D/dev/da0 bs=3D10240 count=3D100
Boot from Disc 1
Follow the Standard Install option is sysinstall
I have done that 4 times now. There was a semi-dead ad0 disk in the =
unit. That has been removed and going through the above one more time =
at this moment.
There were no errors reportd for disk geometry and its not dangerously =
dedicated. I gave up with that on version 2.7.
This time it worked. I used the first boot manager entry, not the =
FreeBSD Boot manager and there is no F1 line. It just boots into =
FreeBSD. Thats fine since there is only FreeBSD on the machine. I =
guess something from the ad0 drive was interfering with the boot. The =
disk was reporting numerous write errors although it could be read fine =
and was only holding archive'd data. Its loss is insignificant.
I believe the big issue where was the message about make delete-old-libs =
that make delete-old outputs. I had never tried that before and never =
had problems. This time I decided to try it. I think that message =
should be removed.
>=20
> --=20
> Peter Jeremy
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 22:47:37 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8371C106566C
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 22:47:37 +0000 (UTC)
(envelope-from johnr1@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id 20C5B8FC0A
for <freebsd-stable@freebsd.org>; Sat, 27 Mar 2010 22:47:36 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2RMNXMK079911;
Sat, 27 Mar 2010 15:23:41 -0700 (PDT)
(envelope-from johnr1@sstec.com)
Message-Id: <5.2.1.1.2.20100327152147.03232eb0@mail.sstec.com>
X-Sender: john@mail.sstec.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sat, 27 Mar 2010 15:23:28 -0700
To: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no>,
freebsd-stable@freebsd.org
From: "John R. Long" <johnr1@sstec.com>
In-Reply-To: <20100325111611.b1e8994f.torfinn.ingolfsen@broadpark.no>
References: <5.2.1.1.2.20100324165115.03159ab8@mail.sstec.com>
<5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100322150534.032bee30@mail.sstec.com>
<5.2.1.1.2.20100324100236.0320fec8@mail.sstec.com>
<5.2.1.1.2.20100324165115.03159ab8@mail.sstec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc:
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 22:47:37 -0000
At 03:16 AM 3/25/2010, Torfinn Ingolfsen wrote:
>On Wed, 24 Mar 2010 18:04:51 -0700
>John Long <fbsd2@sstec.com> wrote:
>
>> I want to thank you very much for all the info you have provided. It has
>> clued me into a much better understanding and I see that it is a big
>> un-standard thing to monitor these functions. It seems that things are
>
>FYI: for (some) Asus boards thererb is als acpi_aiboost(4).
I wish I had known that b4. Thanks
>--
>Regards,
>Torfinn Ingolfsen
>
>_______________________________________________
>freebsd-stable@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
From owner-freebsd-stable@FreeBSD.ORG Sat Mar 27 23:52:02 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id EA9BF106564A;
Sat, 27 Mar 2010 23:52:02 +0000 (UTC) (envelope-from fbsd2@sstec.com)
Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net
[216.102.148.67])
by mx1.freebsd.org (Postfix) with ESMTP id A288B8FC0A;
Sat, 27 Mar 2010 23:52:02 +0000 (UTC)
Received: from main.sstec.com (main.sstec.com [192.168.74.8])
by star.sstec.com (8.13.8/8.13.8) with ESMTP id o2RNpr4i080969;
Sat, 27 Mar 2010 16:51:56 -0700 (PDT) (envelope-from fbsd2@sstec.com)
Message-Id: <5.2.1.1.2.20100327152415.0320bf28@mail.sstec.com>
X-Sender:
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sat, 27 Mar 2010 16:51:49 -0700
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
From: John Long <fbsd2@sstec.com>
In-Reply-To: <20100326091447.GA91547@icarus.home.lan>
References: <5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<1269310984.00232724.1269300005@10.7.7.3>
<1269310984.00232724.1269300005@10.7.7.3>
<5.2.1.1.2.20100324134153.032459d8@mail.sstec.com>
<5.2.1.1.2.20100325235505.031e8338@mail.sstec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Alexander Motin <mav@freebsd.org>,
FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>,
Ian Smith <smithi@nimnet.asn.au>
Subject: Re: Powerd and est / eist functionality
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 23:52:03 -0000
At 02:14 AM 3/26/2010, Jeremy Chadwick wrote:
>On Fri, Mar 26, 2010 at 01:20:19AM -0700, John Long wrote:
>> >Yes you're only getting p4tcc throttling as Alexander points out. You'll
>> >need to get est working to get power reduction from lower frequencies,
>> >which likely won't correspond to these f/8 step throttling frequencies.
>> >
>> >As Jeremy suggested, here's how to turn throttling off, and something
>> >like what you could expect with est working:
>> >http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055666.html
>>
>> from link:
>> I would recommend you to disable it by setting:
>> hint.p4tcc.0.disabled=1
>> hint.acpi_throttle.0.disabled=1
>>
>> I get unknown oid on both. Not sure how to disable p4tcc here. What
>> I have to work with.
>
>These are /boot/loader.conf tunables, not sysctl. I'm pretty sure I
>stated that in my previous mail...?
Drats, you are right. too late at night.. did not give me anything positive
anyway.
>
>> Bios is most recent, has EIST, c1e and c2e I believe enabled. That
>> seems to do the best all by itself. Maybe It does no good to beat a
>> dead horse?? :-) I see an ITE IT8718F-S chip on board. mbmon does
>> work somewhat but its code is way old and does not see the newer
>> chip versions. some good docs with mbmon in usr/local/share/docs
>> tho..
>> %mbmon -d -A
>> Summary of Detection:
>> * ISA monitor(s):
>> ** Nat.Semi.Con. Chip LM78 found.
>> ** Int.Tec.Exp. Chip IT8705F/IT8712F or SIS950 found
>>
>
>Ignore all of the above values -- mbmon doesn't work properly with your
>board, or that sub-revision of IT chip. It's that simple. Re-read the
>rant I sent you for explanation; I already covered all the bases. :-) I
>disagree about the mbmon docs -- they're more like chaotic brain dumps
>or scribbled notes than actual coherent, well-written instructions or
>details.
Agreed, but they were something vs not much and I was grasping :-)
That said, I have utmost respect for SHIMIZU Yoshifumi and his
>efforts/work.
>
>I'm willing to make an exception here. If you can get the following
>information from the motherboard manufacturer, I'd be willing to add
>support for your board to bsdhwmon. What I need:
>
>1) The exact H/W monitoring IC they use (not what mbmon says, and
> not what's silkscreened on the chip),
That would be a bit impossible for me, what is on the chip is all I can
provide.
>
>2) If the H/W monitoring IC is tied in to SMBus,
hellava question too, Tell me and we would both know :-)
>
>3) What the SMBus slave address is they chose for the H/W IC
% dmesg | grep -i smbus
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
I am pretty sure I would get a deer in the headlights response from
gigabyte over this question..
>
>4) Output of "kenv | grep smbios" from your system.
> kenv | grep smbios
smbios.bios.reldate="11/04/2009"
smbios.bios.vendor="Award Software International, Inc."
smbios.bios.version="F6"
smbios.chassis.maker="Gigabyte Technology Co., Ltd."
smbios.chassis.serial=" "
smbios.chassis.tag=" "
smbios.chassis.version=" "
smbios.memory.enabled="1048576"
smbios.planar.maker="Gigabyte Technology Co., Ltd."
smbios.planar.product="G41M-ES2L"
smbios.planar.serial=" "
smbios.planar.version="x.x"
smbios.socket.enabled="1"
smbios.socket.populated="1"
smbios.system.maker="Gigabyte Technology Co., Ltd."
smbios.system.product="G41M-ES2L"
smbios.system.serial=" "
smbios.system.uuid="00000000-0000-0000-0000-6cf049635a47"
smbios.system.version=" "
smbios.version="2.4"
1 out of 4 is not too bad :-)
>
>Assuming all of the above meets necessary criteria, I can probably add
>support for this board to bsdhwmon. I have only slight qualms/concerns
>adding consumer boards to bsdhwmon, but the big kicker is that the board
>**must** have an actual H/W monitoring IC tied/wired to SMBus. I *will
>not* use the old LPC/ISA (/dev/io) infrastructure.
I understand, there are just too many possible different implementations
and chips being used. Getting Vcore from both healthd and mbmon, being
about the same and that being the main concern for my discovery into
functionality has me satiated. Getting the rest of the sensors would be
great but certainly would not be worth any effort from you or anyone for
just this one of hundreds of mbds. I do appreciate the offer tho. I should
of bought Asus in the first place. I always have for past 12 years but my
selection dwindled about 3 weeks ago when Frys dropped the asus p5qpl-am.
That was the only non realtek ether g41 mbd I could find. I took a chance
that the re8111 (gigabyte and most others) drivers would work as well and
it looks like they do. The only remaining viable asus mbd, to me, is the
p5g41-m lx2/gm but a search on asus's site and it is not to be found
therefore that would be a nono for me.
There are just too many different mbds out there, the manufs have just gone
hog wild.
>
>> It jumped up in vcore a little there with powerd. C1E and C2E which
>> include P-states are what I am really after and I think that the
>> bios by itself provides those changes better than any other changes
>> in these settings.
>
>...and this would fall under the est(4) subset driver for cpufreq(4).
This repeated clue got me to the next step and I thank you for that. The
key, as I see it, is to get est working either by getting the msr tables
updated somehow or getting the acpi working better so est could fall back
on it therefore powerd would have a better set of signals to use rather
than thermal. Like I have mentioned elsewhere, it looks like est has not
really been updated nor worked on much for about 5 years and is missing the
proper tables for the mbds since. That is a big and near impossible job
unless it can be modded to a sort of wildcard detection if there is some
commonality to newer mbds.
John
>
>--
>| Jeremy Chadwick jdc@parodius.com |
>| Parodius Networking http://www.parodius.com/ |
>| UNIX Systems Administrator Mountain View, CA, USA |
>| Making life hard for others since 1977. PGP: 4BD6C0CB |