From owner-freebsd-stable@FreeBSD.ORG Sun May 17 07:30:38 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1EAD3C45 for ; Sun, 17 May 2015 07:30:38 +0000 (UTC) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F0361DEC for ; Sun, 17 May 2015 07:30:36 +0000 (UTC) Received: from [10.0.5.3] (ewsw01.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.14.6/8.13.6) with ESMTP id t4H7SwDe078079 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sun, 17 May 2015 17:29:03 +1000 (EST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Message-ID: <55584366.7080708@heuristicsystems.com.au> Date: Sun, 17 May 2015 17:29:42 +1000 From: Dewayne Geraghty User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: FreeBSD Stable Mailing List Subject: System load greater than logical cores and idprio 30 getting time. Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 May 2015 07:30:38 -0000 I don't understand why processes running at idpro 30 are gettting as much CPU time as stated below when the load average is greater than the number of logical cores. I don't think its just a measuring error as I have other short lived processes that also complete at idprio 31. The scheduler for this server is kern.sched.name: ULE kern.sched.interact: 0 This top extract was taken from a Xeon E3-1230L with 8 logical cores, running 10.1Stable built/installed May 6,2015. -- top extract -- last pid: 83135; load averages: 11.32, 8.98, 6.24 up 1+01:33:51 14:42:19 81 processes: 13 running, 68 sleeping CPU: 95.9% user, 0.0% nice, 4.1% system, 0.0% interrupt, 0.0% idle Mem: 299M Active, 5507M Inact, 1351M Wired, 5580K Cache, 899M Buf, 568M Free Swap: 3881M Total, 16M Used, 3865M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 40867 root 1 154 i30 50316K 4720K RUN 2 17:59 42.97% ssh-keygen 40869 root 1 154 i30 50316K 4728K RUN 6 17:49 42.48% ssh-keygen 83099 root 1 76 0 86468K 70696K RUN 4 0:02 16.46% c++ And couple of hours later (note not WCPU) last pid: 21436; load averages: 20.13, 14.73, 12.00 up 1+04:15:45 17:24:13 101 processes: 23 running, 78 sleeping CPU: 95.6% user, 0.0% nice, 4.4% system, 0.0% interrupt, 0.0% idle Mem: 724M Active, 5292M Inact, 1241M Wired, 32M Cache, 847M Buf, 443M Free Swap: 3881M Total, 21M Used, 3861M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME CPU COMMAND 20141 root 1 155 i31 83084K 37688K RUN 7 0:09 25.98% ssh-keygen 21380 root 1 79 0 110M 101M CPU3 3 0:03 24.46% c++ 21340 root 1 78 0 74492K 66468K CPU4 4 0:03 20.46% c++ I recall the BSD scheduler behaving as expected, ie when the load > cores, then idprio 31 processes barely received any time. Regards, Dewayne. From owner-freebsd-stable@FreeBSD.ORG Mon May 18 09:55:16 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ACB8DD1D for ; Mon, 18 May 2015 09:55:16 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 9B5851CB7 for ; Mon, 18 May 2015 09:55:16 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 7D474446 for ; Mon, 18 May 2015 09:55:15 +0000 (UTC) Date: Mon, 18 May 2015 09:55:14 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-stable@freebsd.org Message-ID: <1039671927.5.1431942914160.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : Build-UFS-image #1682 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkKKb2VAfYQKfu1t7qk4nR5qzUBEI+UqT4BPec4qHVhqUy0FFdq50sMH+3y9bCDNOufctov6VqTNffZ3YXArnZK95YF0OX97fh+E9txYOUX1adc+TikcKjuYpHmL5dE62eaZTI+4A5jnRonskQ1PaoIFz0Kbu4mWzkFsmdiXTraGzomXq4cHUCATA2+K4eDYgjXEQI30z3GOMmmZ4t/+6QGk1cMb/BqMWHbn80AsRCb4tU7Hpd72XLDpsuO7YRP1Q0CjmNAuBOTj+sFiiOe6U9HpqOlQN+iFUvBdZo/ybuy5Kh71cAaYQNL68cYdZJ6binH/DkG3KY/fS7DFYAeuwjwIDAQAB X-Jenkins-Job: Build-UFS-image X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2015 09:55:16 -0000 See From owner-freebsd-stable@FreeBSD.ORG Tue May 19 00:22:22 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47D74E7 for ; Tue, 19 May 2015 00:22:22 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [191.243.120.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F23B31ACD for ; Tue, 19 May 2015 00:22:21 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) by mail.bsdinfo.com.br (Postfix) with ESMTP id 8A32530FC56 for ; Mon, 18 May 2015 21:21:46 -0300 (BRT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bsdinfo.com.br; h=content-transfer-encoding:content-type:content-type:subject :subject:to:mime-version:user-agent:from:from:date:date :message-id; s=dkim; t=1431994906; x=1432858907; bh=fFwgwewUgn8j rUgU3FnKriiPxZel8KvYiNJcT9gFYAw=; b=Bssyg1ASikii57LfAUDrAHXVzKFx nh0bCOBGJdpfjn8o0CzYJMMKqvKb8TI2xEIOp281Dnx29rpjX3M7oaCj+lOP7N59 Wk6cN5Be8LN53SbkEd8xrQHrUunbh9kXrH/yKP6AwkLf1J8bBVWLYyv3dR4zkeWM RfVldwCEAKgClBk= X-Virus-Scanned: amavisd-new at mail.bsdinfo.com.br Received: from mail.bsdinfo.com.br ([127.0.0.1]) by mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBqKfQdS_HEQ for ; Mon, 18 May 2015 21:21:46 -0300 (BRT) Received: from [192.168.10.208] (unknown [186.193.54.69]) by mail.bsdinfo.com.br (Postfix) with ESMTPSA id E73F830FC55 for ; Mon, 18 May 2015 21:21:45 -0300 (BRT) Message-ID: <555A8208.9010208@bsdinfo.com.br> Date: Mon, 18 May 2015 21:21:28 -0300 From: Marcelo Gondim User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: FreeBSD Stable Mailing List Subject: table with bug in ipfw Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 00:22:22 -0000 Hi all, I see that there is still the following bug in ipfw: # ipfw table 33 add 0.0.0.0/8 # ipfw table 33 list ::/8 0 and # ipfw table 33 add 255.255.255.255 # ipfw table 33 list ::/8 0 The IP 255.255.255.255 not appear but it's there. Look below: # ipfw table 33 add 255.255.255.255 ipfw: setsockopt(IP_FW_TABLE_XADD): File exists This is very ugly to see. As it was not fixed in 10.1, would be expected to 10.2? Best regards, Gondim From owner-freebsd-stable@FreeBSD.ORG Tue May 19 08:24:10 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C71578D6 for ; Tue, 19 May 2015 08:24:10 +0000 (UTC) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 54F01100D for ; Tue, 19 May 2015 08:24:09 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.9/8.14.9) with ESMTP id t4J8O3Dp010001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 19 May 2015 10:24:03 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.9/8.14.9/Submit) with ESMTP id t4J8O3b5009998 for ; Tue, 19 May 2015 10:24:03 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Tue, 19 May 2015 10:24:03 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD stable Subject: ctfconvert fails for cddl/lib/drti, ctfconvert is missing Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 08:24:11 -0000 During make -j 1 installworld on stable/10, this happened to me on two separate occations: ===> cddl/lib/drti (install) make[6]: /usr/obj/usr/src/cddl/lib/drti/.depend, 87: ignoring stale .depend for /usr/src/cddl/lib/drti/../../../sys/cddl/compat/opensolaris/sys/cyclic.h clang -O2 -pipe -fno-omit-frame-pointer -I/usr/src/cddl/lib/drti/../../../sys/cddl/compat/opensolaris -I/usr/src/cddl/lib/drti/../../../cddl/compat/opensolaris/include -I/usr/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/head -I/usr/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/lib/libctf/common -I/usr/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/lib/libdtrace/common -I/usr/src/cddl/lib/drti/../../../sys/cddl/contrib/opensolaris/uts/common -DPIC -fpic -DNEED_SOLARIS_BOOLEAN -std=gnu89 -Qunused-arguments -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-unknown-pragmas ! -c /usr/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/lib/libdtrace/common/drti.c -o drti.o ctfconvert -L VERSION drti.o make[6]: exec(ctfconvert) failed (No such file or directory) *** Error code 1 I run make -j 4 buildworld with -D NO_CLEAN. I had DESTDIR set to a new and empty ZFS BE, so maybe ctfconvert isn't installed in time. /etc/make.conf contains: KERNCONF=ENTERPRISE GENERIC ZFS STRIP= CFLAGS+=-fno-omit-frame-pointer /etc/src.conf contains: CC=clang CXX=clang++ CPP=clang-cpp NO_WERROR= WERROR= WITH_CLANG_EXTRAS=yes WITH_CLANG_FULL=yes WITH_CTF=1 WITH_GCC=yes WITH_GNUCXX=yes WITH_LIBCPLUSPLUS=yes WITH_NAND=yes Running make -k installworld succeeds. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-stable@FreeBSD.ORG Tue May 19 09:06:18 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2193CB08 for ; Tue, 19 May 2015 09:06:18 +0000 (UTC) Received: from freesbee.wheel.dk (freesbee.wheel.dk [IPv6:2001:6c8:130::97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freesbee.wheel.dk", Issuer "RapidSSL SHA256 CA - G3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D8B9115E3 for ; Tue, 19 May 2015 09:06:17 +0000 (UTC) Received: by freesbee.wheel.dk (Postfix, from userid 1023) id A6E32324613; Tue, 19 May 2015 11:06:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wheel.dk; s=20131204; t=1432026374; bh=9CoHMw8IliC0WBvduZxZ1KJDeiZE9LIliNwFd3xzBLI=; h=Date:From:To:Subject; b=bh86SIqR2oH1ZoHwtphSO/TJtCJUODPlOS7JXgrx+l/0Yf+wvQIgfepEwCAg6DTvl TPHV5+4mCqvg3FwTczk+2t5Z8te0vmIOXGwAq4hZ6UVZEBQL0Cmcx9u2hRDYn1s1x9 ykFTTq8niJ1GKkaq74KXTuQlNKCrvd2PAZG6dfy3eQQ0BXcwEPZz0VVUHPQ4ldXIzf GWo6VGziP9+u7YXN0MObfAJoH64gD8DD+3Ff2CHWscuf3okT8YsaLy+m0kfwOlFUgo gloxBEmLsKCj91PCeI9dli/E+RDHF5BbpPA8t33VGWEOTw0HoJ+Bsjm7jls85Mx6Jb /L41r02bSd+fQ== Received: from localhost (localhost [127.0.0.1]) by freesbee.wheel.dk (Postfix) with ESMTP id A62323243FE for ; Tue, 19 May 2015 11:06:14 +0200 (CEST) Date: Tue, 19 May 2015 11:06:14 +0200 (CEST) From: Claus Andersen To: freebsd-stable@freebsd.org Subject: Unattended install using bsdinstall and ZFS Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 09:06:18 -0000 Hi, Got no answer on -questions so I hope I do not break netiquette by trying my luck here: I cannot wrap my head around this: Am able to do an unattended install using bsdinstall and UFS on 10.1. But I cannot get ZFS to work unattended. If I set the variables concerning ZFS in the install script they do not seem to get picked up. If I set them on the command line using export before I execute the script it only picks up on ZFSBOOT_* but seems to ignore ZFSINTERACTIVE and ZFS_CONFIRM_LAYOUT This almost works: # ZFSBOOT_DISKS="da0 da1" # ZFSBOOT_VDEV_TYPE="mirror" # ZFSBOOT_CONFIRM_LAYOUT=0 # export ZFSBOOT_DISKS ZFSBOOT_VDEV_TYPE ZFSBOOT_CONFIRM_LAYOUT # bsdinstall script install.txt But this still gives me the menu "ZFS Configuration". In the menu I can see that it has picked up ZFSBOOT_DISKS and ZFSBOOT_VDEV_TYPE. The minimal "install.txt" contains: DISTRIBUTIONS="kernel.txz base.txz" RELEASE="10.1" ZFSINTERACTIVE="NO" #!/bin/sh echo "Installation complete, running in host system" It seems to ignore ZFSINTERACTIVE. I have tried with 0, "0", "false", "False", "FALSE". And I have tried going the export route. I would rather use whatever bsdinstall makes available so I can retire my current range of DIY scripts. What is the correct(TM) way of doing unattended install using bsdinstall and ZFS? Google and the man page was not enough for me - I need a real human being! Kind Regards, Claus Andersen From owner-freebsd-stable@FreeBSD.ORG Tue May 19 10:52:54 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 974787B3 for ; Tue, 19 May 2015 10:52:54 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A2851782 for ; Tue, 19 May 2015 10:52:53 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 89AB728428; Tue, 19 May 2015 12:44:43 +0200 (CEST) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8408728427; Tue, 19 May 2015 12:44:42 +0200 (CEST) Message-ID: <555B141A.3000901@quip.cz> Date: Tue, 19 May 2015 12:44:42 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Claus Andersen , freebsd-stable@freebsd.org Subject: Re: Unattended install using bsdinstall and ZFS References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 10:52:54 -0000 Claus Andersen wrote on 05/19/2015 11:06: > Hi, > > Got no answer on -questions so I hope I do not break netiquette by > trying my luck here: > > I cannot wrap my head around this: Am able to do an unattended install > using bsdinstall and UFS on 10.1. But I cannot get ZFS to work unattended. > If I set the variables concerning ZFS in the install script they do not > seem to get picked up. If I set them on the command line using export > before I execute the script it only picks up on ZFSBOOT_* but seems to > ignore ZFSINTERACTIVE and ZFS_CONFIRM_LAYOUT > > This almost works: > # ZFSBOOT_DISKS="da0 da1" > # ZFSBOOT_VDEV_TYPE="mirror" > # ZFSBOOT_CONFIRM_LAYOUT=0 > # export ZFSBOOT_DISKS ZFSBOOT_VDEV_TYPE ZFSBOOT_CONFIRM_LAYOUT > # bsdinstall script install.txt > > But this still gives me the menu "ZFS Configuration". In the menu I can > see that it has picked up ZFSBOOT_DISKS and ZFSBOOT_VDEV_TYPE. > > The minimal "install.txt" contains: > > DISTRIBUTIONS="kernel.txz base.txz" > RELEASE="10.1" > ZFSINTERACTIVE="NO" > > #!/bin/sh > echo "Installation complete, running in host system" > > It seems to ignore ZFSINTERACTIVE. I have tried with 0, "0", "false", > "False", "FALSE". And I have tried going the export route. > > I would rather use whatever bsdinstall makes available so I can retire my > current range of DIY scripts. > > What is the correct(TM) way of doing unattended install using bsdinstall > and ZFS? Google and the man page was not enough for me - I need a real > human being! I didn't use bsdinstall script, but I look in to code and I think you should not set ZFSINTERACTIVE at all (or leave it empty?). If it is set, you get Interactive install. You just need to set NONINTERACTIVE This is the code used by bsdinstall and there are useful comments: /usr/share/bsdconfig/variable.subr # f_zfsinteractive # # Has the user specifically requested the ZFS-portion of configuration and # setup to be performed interactively? Returns success if the user has asked # for the ZFS configuration to be done interactively even if perhaps overall # non-interactive mode has been requested (by setting nonInteractive). # # Returns success if $zfsInteractive is set and non-NULL. # f_zfsinteractive() { local value f_getvar $VAR_ZFSINTERACTIVE value && [ "$value" ] } # f_interactive # # Are we running interactively? Return error if $nonInteractive is set and non- # NULL, otherwise return success. # f_interactive() { local value ! f_getvar $VAR_NONINTERACTIVE value || [ ! "$value" ] } Take a closer look in to /usr/share/bsdconfig/variable.subr Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Tue May 19 12:34:27 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6974CFFF for ; Tue, 19 May 2015 12:34:27 +0000 (UTC) Received: from freesbee.wheel.dk (freesbee.wheel.dk [IPv6:2001:6c8:130::97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freesbee.wheel.dk", Issuer "RapidSSL SHA256 CA - G3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 26F441393 for ; Tue, 19 May 2015 12:34:26 +0000 (UTC) Received: by freesbee.wheel.dk (Postfix, from userid 1023) id C3F58324613; Tue, 19 May 2015 14:34:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wheel.dk; s=20131204; t=1432038855; bh=GochkIl6JD5PBU6EiOYmycdIxfun9irlILvDu4Iy7Gc=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=DMcc51NN9+S7yNJrhQIWZKMF99mBHpcr+x9GxNK64IUDFYpouaiVNZYQOb5IxRijY TKFPbqU5ikCWCKlQSDweyqG32kQfs7jOREMblyOCWHW5ZWZ+nIo/XcN6sX/91dyqjM hUBklUHAp2+br9hDIEASbYhSpEWGuTZXSmrHzVEQa8LUo7xCelO1leOTmFGeYzhJTe zF8tRVDV1oC3hnBefxCwF/5/ATfiKZ4ieD8wKTrQnYOTccbvu7ghZE0EzdihFeoxGu A+T46/38jAZfL/23Sl0kQ3J4G1lCwgyTSLd2gXQe2l6IcMPd2Meznxe24pZI0rXnn2 FGe4oUAFwdWNQ== Received: from localhost (localhost [127.0.0.1]) by freesbee.wheel.dk (Postfix) with ESMTP id C2F3A3243FE; Tue, 19 May 2015 14:34:15 +0200 (CEST) Date: Tue, 19 May 2015 14:34:15 +0200 (CEST) From: Claus Andersen To: Miroslav Lachman <000.fbsd@quip.cz> cc: freebsd-stable@freebsd.org Subject: Re: Unattended install using bsdinstall and ZFS In-Reply-To: <555B141A.3000901@quip.cz> Message-ID: References: <555B141A.3000901@quip.cz> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 12:34:27 -0000 On Tue, 19 May 2015, Miroslav Lachman wrote: > I didn't use bsdinstall script, but I look in to code and I think you should > not set ZFSINTERACTIVE at all (or leave it empty?). > If it is set, you get Interactive install. > > You just need to set NONINTERACTIVE Thanks! This makes sense - but does not work for me. I have tried to set NONINTERACTIVE but I get the same result: The "ZFS Configuration" dialog. On a side note I would expect NONINTERACTIVE to be set in "script" - but I digress. When I follow the source as you suggest I see: /usr/libexec/bsdinstall/script calls "bsdinstall zfsboot" because ZFSBOOT_DISKS is set. Looking in /usr/libexec/bsdinstall/zfsboot the interesting bit here seems to be: # # If interactive and the user has not explicitly chosen a vdev type or disks, # make the user confirm scripted/default choices when proceeding to install. # : ${ZFSBOOT_CONFIRM_LAYOUT:=1} But I have set both vdev type and disks. I have even tried setting ZFSBOOT_CONFIRM_LAYOUT=0 - but most of my tests are without setting this. And this seems to control a later confimation step - and not the initial "ZFS Configuration" dialog. This bit kills me if I have ZFSINTERACTIVE set. But I have not (anymore): # User may have specifically requested ZFS-related operations be interactive ! f_interactive && f_zfsinteractive && unset $VAR_NONINTERACTIVE So when I examine the code with my limited capabilities everything looks correct. But it still fails for me. I do the following in a new clean and pristine VM booting the 10.1 CD. # export ZFSBOOT_DISKS="da0 da1" # export ZFSBOOT_VDEV_TYPE="mirror" # bsdinstall script install.txt But this still gives me the menu "ZFS Configuration". In the menu I can see that it has picked up ZFSBOOT_DISKS and ZFSBOOT_VDEV_TYPE. I have tried the following invariant: # export ZFSBOOT_DISKS="da0 da1" # export ZFSBOOT_VDEV_TYPE="mirror" # export NONINTERACTIVE="YES" # bsdinstall script install.txt With the same result. The minimal "install.txt" contains: DISTRIBUTIONS="kernel.txz base.txz" RELEASE="10.1" NONINTERACTIVE="YES" #!/bin/sh echo "Installation complete, running in host system" Anything obvious I am doing wrong? Or even the not-so-obvious would be welcome :-) Rgds, Claus From owner-freebsd-stable@FreeBSD.ORG Tue May 19 15:16:06 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F24B5100 for ; Tue, 19 May 2015 15:16:06 +0000 (UTC) Received: from mailout02.t-online.de (mailout02.t-online.de [194.25.134.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B607B1A4A for ; Tue, 19 May 2015 15:16:06 +0000 (UTC) Received: from fwd13.aul.t-online.de (fwd13.aul.t-online.de [172.20.27.62]) by mailout02.t-online.de (Postfix) with SMTP id E83AD2B39D for ; Tue, 19 May 2015 17:15:57 +0200 (CEST) Received: from [192.168.1.21] (bRURn4Zawhlx7f-lxL99TZUDQCYdWwGulZryMH-8-Wq+2I6RblMj1jqQMXTojr+Zs0@[91.34.151.127]) by fwd13.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1YujFM-2uUxNo0; Tue, 19 May 2015 17:15:56 +0200 Message-ID: <555B53AB.7070307@t-online.de> Date: Tue, 19 May 2015 17:15:55 +0200 From: Ulrich Drolshagen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Please help with cleaning up an accident on 9.0 release Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-ID: bRURn4Zawhlx7f-lxL99TZUDQCYdWwGulZryMH-8-Wq+2I6RblMj1jqQMXTojr+Zs0 X-TOI-MSGID: 90f0ab17-09c9-4ea8-94a5-6fb50cc6472b X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 15:16:07 -0000 Hi all, I brought myself in real trouble with a really important 9.0 release system (9.0-RELEASE-p4). It's amd64. By accident I deleted the following binaries from /bin: cat, chflags, chio, chmod and cp Does anybody still have an old iso from which he can extract these binaries for me please? I would be really thankful if anybody could help Ulrich -- http://www.ulrich-drolshagen.de -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.22 (GNU/Linux) mQENBFMIv8UBCADEIH0+GYnbVfirtv411UvPMu+gbQfx+iGEaV8RUwF5Q0JswakD azXEeIc+iTYfNQXilfGtCaLJLKqi77aUlh1tfJOzbKczK5ZZjTQmKT5JN6BnIW33 sOE51dFgJu7ks3dObWrPyWvNAZQj6VSymNs0WoS6NA0uYRjtQDNO5JfgRE9zm+c9 KZFVgjuPd07KJ01sJ08eRGAn9WIf64qEf3gReVFbOyPEeLAvIZTVPQsoPqG8aych LO+Tn3m88rQkog47nswqAn3CfzFWCIM59qvroohEjHlbPsjk9ILKlyUFfGHlErOh lHmhOcMrI9UeFr/beAIaiP9ZGhI8ss9QK+h1ABEBAAG0PFVscmljaCBEcm9sc2hh Z2VuIChrZWluIFBhc3N3b3J0KSA8dS5kcm9sc2hhZ2VuQHQtb25saW5lLmRlPokB OQQTAQIAIwUCUwi/xQIbIwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEG0f 9rZg0jvzm0QIAJG27e32Y4Jv3WmoCEZibnQIvkM5EzRXF24+V/5p6kjBn9PJ6XP/ 7CGfmJPc/b8UHisj4OSWRXD/Gy3JY9tcZb3PNu2AIzFBRYpVcBmcz9M6sPNqBH6G krSaL6ZTZg2g3bGzXYPRUI/cLSj73McE/J85xj1jRvqjC6BZBQMAXCnkSmEThB/D DAvmq9md7ex3dyWdTDHOUU8K0rxVoxtK4cKus8UP0f8yXNwNBP3ImdlXlSYNhtWs Dn0uvZlnRk4JG6oTjiiEfzxgI4sYidtxT470rzkYm5bKcl5du1Z4uBV1D2YPWxIM 832kiVJHCFfOGQQUcu2d75b86A2x3s9Y84u5AQ0EUwi/xQEIANyNNQQpaazD+/Oi y6FqIMFRJwOfPcerktm6OakgHDtdHzsfHMkyDdughZPCmC5JZSXZ7Ji2OGEUlm6c T4BFuf26QmUYOZKQvz8X3Sp241xYU2akcW8bUYnLIbN65vCXgRRaN3R6ssGp9X8e /J0EfqU4CknZgtoF0+X6WXESSowxSkc0U5qLYL62XP7BxKX6ZMrr6ZiwYAt9k01A GpoFK7bWG91OJ+NhVP8lvFrw193tQCrefWnXFWMmLspv+w/5w9/MRJ/vTKxKmiiv upQ+SrhJqwO4TxgSM8veY3a/s3mOJ+1V765Zavw9B2lZC5+338egmdJ80VnQZt6p 2WT4QOMAEQEAAYkBHwQYAQIACQUCUwi/xQIbDAAKCRBtH/a2YNI78+8SCACs681f cofM+mCrXi0f8XZsxieLUM9Wix9gPcTO4WK8HXVmVdocyFzXoAU8pA+/9XbAYGhK 3BqaP1xPPfxW+FJrEuiXwaOw8ydePAxYgrU9pPF+w0Mg2zq0cbIAtq289CNGdhZX 7efYikuZW/qTyqn827kIGIMLvxHW9Od+vk73PtFUJxpFh7CBeO0nA/JhMkX+vpCS DEDkeOIBASn8RUSviJuk/G+bKJP1LCDZK307+XXvwVQIJ/MIwjpTGgFYyZeNsGoe w25Xkzol9bvJ6dIvoq8NDGnM+1i1HHVVn92RjHPPZUi0Dbsyzgxg4iQp3dPpy+oE mdGOquwS9NztyY1e =Xc2/ -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-stable@FreeBSD.ORG Tue May 19 15:24:18 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B1A70337 for ; Tue, 19 May 2015 15:24:18 +0000 (UTC) Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 769401B9D for ; Tue, 19 May 2015 15:24:18 +0000 (UTC) Received: by obblk2 with SMTP id lk2so14924442obb.0 for ; Tue, 19 May 2015 08:24:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=94QBHE6vRwssYOq7N1Jg3+DjBvLwteJRR6VgRNT78jA=; b=OFrOXkf8QB7kqi30lcXwu9Tj5grStjrfqh0vzE+F26PJ5UHfKnKx8nkY0lDibTwFSP uMgeac64xJtv+ItlPiselk7MZZ+AprTtM1rXFxHMSciDpUhEyyDxFi6a3iojfl94EZxF AlthbkxQo2x5ljYNGOOpB7sdqDvHZiiiEGSZySGi2bkI7uhhwkXrhnBoFH3+hpxOavzK i//KFRe6Vjazjsc1VLdh5p88L0T3t+tCC9RF140WlHaD78X7Z/0zwvOfmrsBKf8fLuvJ T9BBHBhGHtOX6LMv2idRk06GdJMkQqANHO7Q/JZJMXETuVO+2juH9IlX8wH4UttZQ9Og DcbQ== X-Received: by 10.182.112.138 with SMTP id iq10mr24892423obb.38.1432049057861; Tue, 19 May 2015 08:24:17 -0700 (PDT) MIME-Version: 1.0 Sender: royce.williams@gmail.com Received: by 10.202.211.77 with HTTP; Tue, 19 May 2015 08:23:56 -0700 (PDT) In-Reply-To: <555B53AB.7070307@t-online.de> References: <555B53AB.7070307@t-online.de> From: Royce Williams Date: Tue, 19 May 2015 07:23:56 -0800 X-Google-Sender-Auth: vLssYKA34axJSkpDCUTtAnmVE0c Message-ID: Subject: Re: Please help with cleaning up an accident on 9.0 release To: Ulrich Drolshagen Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 15:24:18 -0000 On Tue, May 19, 2015 at 7:15 AM, Ulrich Drolshagen wrote: > Hi all, > > I brought myself in real trouble with a really important 9.0 release > system (9.0-RELEASE-p4). It's amd64. By accident I deleted the following > binaries from /bin: cat, chflags, chio, chmod and cp > Does anybody still have an old iso from which he can extract these > binaries for me please? > > I would be really thankful if anybody could help > Here you go: http://www.techsolvency.com/tmp/ Royce From owner-freebsd-stable@FreeBSD.ORG Tue May 19 15:32:22 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44B0E84E for ; Tue, 19 May 2015 15:32:22 +0000 (UTC) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "ca.infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C39FC1CD4 for ; Tue, 19 May 2015 15:32:21 +0000 (UTC) Received: from ox-dell39.ox.adestra.com (no-reverse-dns.metronet-uk.com [85.199.232.226] (may be forged)) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.15.1/8.15.1) with ESMTPSA id t4JFW32V074017 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 19 May 2015 16:32:12 +0100 (BST) (envelope-from matthew@freebsd.org) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=freebsd.org DKIM-Filter: OpenDKIM Filter v2.9.2 smtp.infracaninophile.co.uk t4JFW32V074017 Authentication-Results: smtp.infracaninophile.co.uk/t4JFW32V074017; dkim=none reason="no signature"; dkim-adsp=none; dkim-atps=neutral X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host no-reverse-dns.metronet-uk.com [85.199.232.226] (may be forged) claimed to be ox-dell39.ox.adestra.com Message-ID: <555B576D.3090203@freebsd.org> Date: Tue, 19 May 2015 16:31:57 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Please help with cleaning up an accident on 9.0 release References: <555B53AB.7070307@t-online.de> In-Reply-To: <555B53AB.7070307@t-online.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="9rB3oUv9Bb9EhvoGMVrM4UfHegswo4dWG" X-Virus-Scanned: clamav-milter 0.98.7 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 15:32:22 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9rB3oUv9Bb9EhvoGMVrM4UfHegswo4dWG Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 05/19/15 16:15, Ulrich Drolshagen wrote: > I brought myself in real trouble with a really important 9.0 release > system (9.0-RELEASE-p4). It's amd64. By accident I deleted the followin= g > binaries from /bin: cat, chflags, chio, chmod and cp > Does anybody still have an old iso from which he can extract these > binaries for me please? >=20 > I would be really thankful if anybody could help http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/amd64/9.0= -RELEASE/ Cheers, Matthew --9rB3oUv9Bb9EhvoGMVrM4UfHegswo4dWG 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 iQJ8BAEBCgBmBQJVW1dzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnqGIP/3MrwRDGbzA55B13fBeD06jy cooog238MnA7KpnV2YC/nL2Zgp4aflCnBggBgvpelJmyAqVRu+I2xolDin/5zbcw Kihy8+8EpZZrpHP6cKSt99vuPqEpLqMewas4P3BbT1PywM4p29dABWa9lHxoKPpn O9ttrgiJ4RCe0wxa/2MV9YRiVbbtaLX4PXdK4bsvu2F37skBpwT+9/nopkI9Mglg g4tLlaInQHc8PmgxTxm0pRLbcbMI7QQYvtEvVbc31QQkGLoKE/vzFrtBcsPFXQol NQOwO/cgK0lU+dN0hBnQXpOShKqPO0rwpQ38INf8wB/3BWx9R1gyeKO6332gPbZr OAdHC83GNgI6jwJrhYrssalIJVpVwEWBQ4dj4RcAj9zTUdt2lPVT0+ItknNk23zC N1x9J9uxg9/PNJDMN0/zjsjQnD7wKfhAv+orK4IYfs1bgHfbNtcHYlgPLOb/Z/T2 2q0jrC/TUdLEvxifU82lBLYbnOYuKYs/eZLNsjl4KzVDM46dXzip6Xrelm+e6/HF IDBbmv5FvI3TWDWckji1iBQmuzm2W6sQ2SJ3f9ofrqceJD1WEabgf4um3TaketUa 3Cjgg0h+8YhG66nvS3E199Q7a4nZy4F9Hxs2Sq1Mdabq/PSbAyKl/3HArHBVLEPH QC5vMqqCT91vaOQxCiBZ =G23U -----END PGP SIGNATURE----- --9rB3oUv9Bb9EhvoGMVrM4UfHegswo4dWG-- From owner-freebsd-stable@FreeBSD.ORG Tue May 19 15:59:54 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DC974776 for ; Tue, 19 May 2015 15:59:54 +0000 (UTC) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9EF6D1FDE for ; Tue, 19 May 2015 15:59:54 +0000 (UTC) Received: from fwd09.aul.t-online.de (fwd09.aul.t-online.de [172.20.27.151]) by mailout01.t-online.de (Postfix) with SMTP id CEC6160895 for ; Tue, 19 May 2015 17:59:45 +0200 (CEST) Received: from [192.168.1.21] (ECT4EaZYQhDXrmTW+kfiNXLeSjt4+YhuJ-3wL27dQWbe0TQqNHTlVhTDQZWFQAHQtG@[91.34.151.127]) by fwd09.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1YujvX-3KZIrQ0; Tue, 19 May 2015 17:59:31 +0200 Message-ID: <555B5DE3.1030700@t-online.de> Date: Tue, 19 May 2015 17:59:31 +0200 From: Ulrich Drolshagen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Please help with cleaning up an accident on 9.0 release References: <555B53AB.7070307@t-online.de> In-Reply-To: <555B53AB.7070307@t-online.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-ID: ECT4EaZYQhDXrmTW+kfiNXLeSjt4+YhuJ-3wL27dQWbe0TQqNHTlVhTDQZWFQAHQtG X-TOI-MSGID: 670f8cc2-6f7d-4a71-8286-e7dc1c411292 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 15:59:54 -0000 Royce helped me to resolve my problem Thank you very much Royce and all others looking into it. Ulrich Am 19.05.2015 um 17:15 schrieb Ulrich Drolshagen: > Hi all, > > I brought myself in real trouble with a really important 9.0 release > system (9.0-RELEASE-p4). It's amd64. By accident I deleted the following > binaries from /bin: cat, chflags, chio, chmod and cp > Does anybody still have an old iso from which he can extract these > binaries for me please? > > I would be really thankful if anybody could help > > Ulrich > > > > > > From owner-freebsd-stable@FreeBSD.ORG Wed May 20 12:54:24 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1341C47F for ; Wed, 20 May 2015 12:54:24 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B279B13AC for ; Wed, 20 May 2015 12:54:23 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 4FCFD6AC0DB; Wed, 20 May 2015 14:54:20 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id t4KCsK48080280; Wed, 20 May 2015 14:54:20 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id t4KCsI65079383; Wed, 20 May 2015 14:54:18 +0200 (CEST) (envelope-from lars) Date: Wed, 20 May 2015 14:54:18 +0200 From: Lars Engels To: Royce Williams Cc: Ulrich Drolshagen , freebsd-stable Subject: Re: Please help with cleaning up an accident on 9.0 release Message-ID: <20150520125418.GQ53149@e-new.0x20.net> References: <555B53AB.7070307@t-online.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="90KBcPA0h13nTGdQ" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p23 User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 12:54:24 -0000 --90KBcPA0h13nTGdQ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 19, 2015 at 07:23:56AM -0800, Royce Williams wrote: > On Tue, May 19, 2015 at 7:15 AM, Ulrich Drolshagen > wrote: >=20 > > Hi all, > > > > I brought myself in real trouble with a really important 9.0 release > > system (9.0-RELEASE-p4). It's amd64. By accident I deleted the following > > binaries from /bin: cat, chflags, chio, chmod and cp > > Does anybody still have an old iso from which he can extract these > > binaries for me please? > > > > I would be really thankful if anybody could help > > >=20 > Here you go: >=20 > http://www.techsolvency.com/tmp/ >=20 And all of them have statically compiled versions in /rescue --90KBcPA0h13nTGdQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJVXIP6XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1t89oIAJCvh2c+pYwXKZ6oDuQj/3M+ L7gDO/MXBGqDgvu0qLE5IdpgamCPVGsS3QQP1VnBsAJlGihGD6XMdW53LNDdzdlz UwgdaqIiYQCyecL3bss7Gkg3mdrDLdm1mezGRcjNjxvaUZXu0dC66ISsaopHrGse UZCzCZEofICYDvwRx3JrG3k6OLoFuYKnAuwgU89yEOcLyjIv38K1xrHPQdsHfrVc fmKWGP4UjGDqpE/qsHtt58FL5t8MseiUs1cHllIy4nZ+nwE1lFnHfqWYeSe7Qip0 h3JcCsvJrRD/xNM8JLnIl2Cf/uMuObAisGUOmVKbt4hx4TrZFyQ5evjSY1jrlZQ= =iL7N -----END PGP SIGNATURE----- --90KBcPA0h13nTGdQ-- From owner-freebsd-stable@FreeBSD.ORG Wed May 20 12:57:17 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 228F49FC for ; Wed, 20 May 2015 12:57:17 +0000 (UTC) Received: from forward13h.cmail.yandex.net (forward13h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::9e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CFF4D143C for ; Wed, 20 May 2015 12:57:16 +0000 (UTC) Received: from web6h.yandex.ru (web6h.yandex.ru [IPv6:2a02:6b8:0:f05::16]) by forward13h.cmail.yandex.net (Yandex) with ESMTP id 91DFC21A00; Wed, 20 May 2015 15:57:01 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web6h.yandex.ru (Yandex) with ESMTP id 152112782633; Wed, 20 May 2015 15:57:00 +0300 (MSK) Received: by web6h.yandex.ru with HTTP; Wed, 20 May 2015 15:57:00 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: Marcelo Gondim , FreeBSD Stable Mailing List In-Reply-To: <555A8208.9010208@bsdinfo.com.br> References: <555A8208.9010208@bsdinfo.com.br> Subject: Re: table with bug in ipfw MIME-Version: 1.0 Message-Id: <1442671432126620@web6h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Wed, 20 May 2015 15:57:00 +0300 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 12:57:17 -0000 19.05.2015, 03:22, "Marcelo Gondim" : > Hi all, Hi, > > I see that there is still the following bug in ipfw: > > # ipfw table 33 add 0.0.0.0/8 > # ipfw table 33 list > ::/8 0 > > and > > # ipfw table 33 add 255.255.255.255 > # ipfw table 33 list > ::/8 0 > > The IP 255.255.255.255 not appear but it's there. Look below: > > # ipfw table 33 add 255.255.255.255 > ipfw: setsockopt(IP_FW_TABLE_XADD): File exists > > This is very ugly to see. As it was not fixed in 10.1, would be expected > to 10.2? It was fixed in -head but didn't get to -stable. I'll try to take a look soon. > > Best regards, > Gondim > > _______________________________________________ > 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 May 20 16:17:47 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F2398B66; Wed, 20 May 2015 16:17:46 +0000 (UTC) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A31F31EA5; Wed, 20 May 2015 16:17:46 +0000 (UTC) Received: by wghq2 with SMTP id q2so58331626wgh.1; Wed, 20 May 2015 09:17:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=5IOMShMm8+dArp26rdC6HlVSD9yyeToRQxv5F6nypjA=; b=rlGXV6zxwzpsuqugADBCLJ+gDNOVIfrZrzfy4p4skG0y2/TkHnnJprgdl4N+nSvcW9 xa4WohbKHgqm1ayu6LPGl0EjbZOnxEuwPNOU4QsXL7wLolmE2aRCZo7HiaVpEHulS982 5x/q5ZJGJpltDbzDCUsrohwrif/Rx2V3QFXqAB9QTTDWh2RQ3t81fPwCoi7/8hAtzsLt nDToD5vsxYjdNGQkqJK5bAqdreLZuQuXzq58aqET2TdS4GpzWWfCm2z6niPGvMrBUek7 g8X/AM2Y6BdHgIC6adVj0EDS636a/BJiylBtwI6oxnmp4NwdrJxwvVxURt6cV/OqvN5a NUAw== MIME-Version: 1.0 X-Received: by 10.194.60.43 with SMTP id e11mr30617936wjr.36.1432138664942; Wed, 20 May 2015 09:17:44 -0700 (PDT) Received: by 10.28.30.22 with HTTP; Wed, 20 May 2015 09:17:44 -0700 (PDT) Date: Wed, 20 May 2015 19:17:44 +0300 Message-ID: Subject: L2ARC degraded. Checksum errors, I/O errors From: George Kontostanos To: freebsd-stable , "freebsd-fs@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 16:17:47 -0000 Hello, Appologies if that has been asked before. I was wondering if the following bug has been addressed so far: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198242 Thanks -- George Kontostanos --- From owner-freebsd-stable@FreeBSD.ORG Wed May 20 17:50:43 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D687394; Wed, 20 May 2015 17:50:43 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 583821B01; Wed, 20 May 2015 17:50:43 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Yv88X-0004vI-4Q; Wed, 20 May 2015 20:50:33 +0300 Date: Wed, 20 May 2015 20:50:33 +0300 From: Slawa Olhovchenkov To: George Kontostanos Cc: freebsd-stable , "freebsd-fs@freebsd.org" Subject: Re: L2ARC degraded. Checksum errors, I/O errors Message-ID: <20150520175033.GK1394@zxy.spb.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 17:50:43 -0000 On Wed, May 20, 2015 at 07:17:44PM +0300, George Kontostanos wrote: > Hello, > > Appologies if that has been asked before. I was wondering if the following > bug has been addressed so far: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198242 As I know kstat.zfs.misc.arcstats.l2_cksum_bad: 14495 kstat.zfs.misc.arcstats.l2_io_error: 12877 caused by hardware failure on L2ARC device. try replace it. From owner-freebsd-stable@FreeBSD.ORG Wed May 20 19:08:26 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A0F02933; Wed, 20 May 2015 19:08:26 +0000 (UTC) Received: from EXCH2-1.slu.se (webmail.slu.se [77.235.224.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32BF317ED; Wed, 20 May 2015 19:08:25 +0000 (UTC) Received: from exch2-4.slu.se (77.235.224.124) by EXCH2-1.slu.se (77.235.224.121) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Wed, 20 May 2015 20:53:05 +0200 Received: from exch2-4.slu.se ([fe80::3117:818f:aa48:9d9b]) by exch2-4.slu.se ([fe80::3117:818f:aa48:9d9b%22]) with mapi id 15.00.1076.000; Wed, 20 May 2015 20:53:05 +0200 From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= To: Slawa Olhovchenkov CC: George Kontostanos , "freebsd-fs@freebsd.org" , freebsd-stable Subject: Re: L2ARC degraded. Checksum errors, I/O errors Thread-Topic: L2ARC degraded. Checksum errors, I/O errors Thread-Index: AQHQky400/SoOpaDyEOxzwCf8lvG/Q== Date: Wed, 20 May 2015 18:53:05 +0000 Message-ID: <68854ba9-1852-4a2c-b329-f3fecee176b6@email.android.com> Accept-Language: sv-SE, en-US Content-Language: sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 19:08:26 -0000 DQpEZW4gMjAgbWFqIDIwMTUgNzo1MCBlbSBza3JldiBTbGF3YSBPbGhvdmNoZW5rb3YgPHNsd0B6 eHkuc3BiLnJ1PjoNCj4NCj4gT24gV2VkLCBNYXkgMjAsIDIwMTUgYXQgMDc6MTc6NDRQTSArMDMw MCwgR2VvcmdlIEtvbnRvc3Rhbm9zIHdyb3RlOg0KPg0KPiA+IEhlbGxvLA0KPiA+DQo+ID4gQXBw b2xvZ2llcyBpZiB0aGF0IGhhcyBiZWVuIGFza2VkIGJlZm9yZS4gSSB3YXMgd29uZGVyaW5nIGlm IHRoZSBmb2xsb3dpbmcNCj4gPiBidWcgaGFzIGJlZW4gYWRkcmVzc2VkIHNvIGZhcjoNCj4gPiBo dHRwczovL2J1Z3MuZnJlZWJzZC5vcmcvYnVnemlsbGEvc2hvd19idWcuY2dpP2lkPTE5ODI0Mg0K Pg0KPiBBcyBJIGtub3cNCj4NCj4ga3N0YXQuemZzLm1pc2MuYXJjc3RhdHMubDJfY2tzdW1fYmFk OiAxNDQ5NQ0KPiBrc3RhdC56ZnMubWlzYy5hcmNzdGF0cy5sMl9pb19lcnJvcjogMTI4NzcNCj4N Cj4gY2F1c2VkIGJ5IGhhcmR3YXJlIGZhaWx1cmUgb24gTDJBUkMgZGV2aWNlLg0KPiB0cnkgcmVw bGFjZSBpdC4NCg0KSGFyZGx5LiBXZSBhcmUgc2VlaW5nIHRoaXMgcGhlbm9tZW5vbiBvbiBhbGwg b2YgeW91ciBaRlMgc3RvcmFnZSdzLCB3aGVyZSBzb21lIG9mIHRoZSBMMkFSQydzIGFyZSBuZXcs IHNvIEknZCBiZSB2ZXJ5IHN1cnByaXNlZCBpZiB0aGVzZSBhcmUgcmVhbCBoYXJkd2FyZSBmYWls dXJlcy4gVGhhdCwgYXMgd2VsbCBhcyBiZWluZyByZXBvcnRlZCBieSBzbyBtYW55LCBteSB2b3Rl IGlzIG9uIGJ1Zy4NCg0KQGdrb250b3MNClRoYW5rcyBmb3IgYnJpbmdpbmcgdGhpcyB0byBhdHRl bnRpb24sIEknbSBhbHNvIGludGVyZXN0ZWQgaW4gaGVhcmluZyBpZiBhbnlvbmUncyB3b3JraW5n IG9uIHRoaXMuDQoNCi9LDQoNCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX18NCj4gZnJlZWJzZC1mc0BmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QNCj4gaHR0 cDovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1mcw0KPiBUbyB1 bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC1mcy11bnN1YnNjcmliZUBmcmVl YnNkLm9yZyINCg== From owner-freebsd-stable@FreeBSD.ORG Wed May 20 19:40:22 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04C73A1A; Wed, 20 May 2015 19:40:22 +0000 (UTC) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9FFE61C4E; Wed, 20 May 2015 19:40:21 +0000 (UTC) Received: by wicmx19 with SMTP id mx19so166598187wic.0; Wed, 20 May 2015 12:40:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=v89E/u2S2gkhXndX+AkJZ5nRkFyy0ZsWHruq8NUN708=; b=GE3tn0qWp4P2RePbdPfg+J4uoQfpF3BKP/vGw/8hdrpywi85LXGqtAuc/ILvM+SkJU UQLpyPElfbuW+S5SVf422AFGrNONx1bU6JxecVYf9hnbm8xY/xjNpGlx1TwrHgA6FYlP nZT84lrv9ZEMteFAf7CIBZL1jbdZNaOzci6WqVc8bGfiuALBo56a6vlDjSjqGmEV7+Pc FmMT0EHw2wmB8j5FyuRbpx9fFO7aAJmYC/mLqPWMk1dyyMMS73Qbp471h0B93cOU8/NZ eF1Lfjet7Sfvyy1kLjaVuHsbN0GCd2jQUV3U6t7lT9wAGzsOm26qyOBozhSxe2uvpDgm a+Vw== MIME-Version: 1.0 X-Received: by 10.194.82.38 with SMTP id f6mr64894131wjy.16.1432150820175; Wed, 20 May 2015 12:40:20 -0700 (PDT) Received: by 10.28.30.22 with HTTP; Wed, 20 May 2015 12:40:20 -0700 (PDT) In-Reply-To: <68854ba9-1852-4a2c-b329-f3fecee176b6@email.android.com> References: <68854ba9-1852-4a2c-b329-f3fecee176b6@email.android.com> Date: Wed, 20 May 2015 22:40:20 +0300 Message-ID: Subject: Re: L2ARC degraded. Checksum errors, I/O errors From: George Kontostanos To: =?UTF-8?Q?Karli_Sj=C3=B6berg?= Cc: "freebsd-fs@freebsd.org" , freebsd-stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 19:40:22 -0000 On Wed, May 20, 2015 at 9:53 PM, Karli Sj=C3=B6berg = wrote: > > Den 20 maj 2015 7:50 em skrev Slawa Olhovchenkov : > > > > On Wed, May 20, 2015 at 07:17:44PM +0300, George Kontostanos wrote: > > > > > Hello, > > > > > > Appologies if that has been asked before. I was wondering if the > following > > > bug has been addressed so far: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D198242 > > > > As I know > > > > kstat.zfs.misc.arcstats.l2_cksum_bad: 14495 > > kstat.zfs.misc.arcstats.l2_io_error: 12877 > > > > caused by hardware failure on L2ARC device. > > try replace it. > > Hardly. We are seeing this phenomenon on all of your ZFS storage's, where > some of the L2ARC's are new, so I'd be very surprised if these are real > hardware failures. That, as well as being reported by so many, my vote is > on bug. > > @gkontos > Thanks for bringing this to attention, I'm also interested in hearing if > anyone's working on this. > > /K > Thanks, I am ignoring the previous comment as it makes no real sense. > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 George Kontostanos --- From owner-freebsd-stable@FreeBSD.ORG Wed May 20 20:16:22 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04285639; Wed, 20 May 2015 20:16:22 +0000 (UTC) Received: from EXCH2-1.slu.se (pop.slu.se [77.235.224.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 618791116; Wed, 20 May 2015 20:16:20 +0000 (UTC) Received: from exch2-4.slu.se (77.235.224.124) by EXCH2-1.slu.se (77.235.224.121) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Wed, 20 May 2015 22:16:10 +0200 Received: from exch2-4.slu.se ([fe80::3117:818f:aa48:9d9b]) by exch2-4.slu.se ([fe80::3117:818f:aa48:9d9b%22]) with mapi id 15.00.1076.000; Wed, 20 May 2015 22:16:10 +0200 From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= To: George Kontostanos CC: "freebsd-fs@freebsd.org" , freebsd-stable Subject: Re: L2ARC degraded. Checksum errors, I/O errors Thread-Topic: L2ARC degraded. Checksum errors, I/O errors Thread-Index: AQHQkznP0/SoOpaDyEOxzwCf8lvG/Q== Date: Wed, 20 May 2015 20:16:09 +0000 Message-ID: Accept-Language: sv-SE, en-US Content-Language: sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 20:16:22 -0000 DQpEZW4gMjAgbWFqIDIwMTUgOTo0MCBlbSBza3JldiBHZW9yZ2UgS29udG9zdGFub3MgPGdrb250 b3MubWFpbEBnbWFpbC5jb20+Og0KPg0KPg0KPg0KPiBPbiBXZWQsIE1heSAyMCwgMjAxNSBhdCA5 OjUzIFBNLCBLYXJsaSBTasO2YmVyZyA8a2FybGkuc2pvYmVyZ0BzbHUuc2U+IHdyb3RlOg0KPj4N Cj4+DQo+PiBEZW4gMjAgbWFqIDIwMTUgNzo1MCBlbSBza3JldiBTbGF3YSBPbGhvdmNoZW5rb3Yg PHNsd0B6eHkuc3BiLnJ1PjoNCj4+ID4NCj4+ID4gT24gV2VkLCBNYXkgMjAsIDIwMTUgYXQgMDc6 MTc6NDRQTSArMDMwMCwgR2VvcmdlIEtvbnRvc3Rhbm9zIHdyb3RlOg0KPj4gPg0KPj4gPiA+IEhl bGxvLA0KPj4gPiA+DQo+PiA+ID4gQXBwb2xvZ2llcyBpZiB0aGF0IGhhcyBiZWVuIGFza2VkIGJl Zm9yZS4gSSB3YXMgd29uZGVyaW5nIGlmIHRoZSBmb2xsb3dpbmcNCj4+ID4gPiBidWcgaGFzIGJl ZW4gYWRkcmVzc2VkIHNvIGZhcjoNCj4+ID4gPiBodHRwczovL2J1Z3MuZnJlZWJzZC5vcmcvYnVn emlsbGEvc2hvd19idWcuY2dpP2lkPTE5ODI0Mg0KPj4gPg0KPj4gPiBBcyBJIGtub3cNCj4+ID4N Cj4+ID4ga3N0YXQuemZzLm1pc2MuYXJjc3RhdHMubDJfY2tzdW1fYmFkOiAxNDQ5NQ0KPj4gPiBr c3RhdC56ZnMubWlzYy5hcmNzdGF0cy5sMl9pb19lcnJvcjogMTI4NzcNCj4+ID4NCj4+ID4gY2F1 c2VkIGJ5IGhhcmR3YXJlIGZhaWx1cmUgb24gTDJBUkMgZGV2aWNlLg0KPj4gPiB0cnkgcmVwbGFj ZSBpdC4NCj4+DQo+PiBIYXJkbHkuIFdlIGFyZSBzZWVpbmcgdGhpcyBwaGVub21lbm9uIG9uIGFs bCBvZiB5b3VyIFpGUyBzdG9yYSBoZWxhLCB3aGVyZSBzb21lIG9mIHRoZSBMMkFSQydzIGFyZSBu ZXcsIHNvIEknZCBiZSB2ZXJ5IHN1cnByaXNlZCBpZiB0aGVzZSBhcmUgcmVhbCBoYXJkd2FyZSBm YWlsdXJlcy4gVGhhdCwgYXMgd2VsbCBhcyBiZWluZyByZXBvcnRlZCBieSBzbyBtYW55LCBteSB2 b3RlIGlzIG9uIGJ1Zy4NCj4+DQo+PiBAZ2tvbnRvcw0KPj4gVGhhbmtzIGZvciBicmluZ2luZyB0 aGlzIHRvIGF0dGVudGlvbiwgSSdtIGFsc28gaW50ZXJlc3RlZCBpbiBoZWFyaW5nIGlmIGFueW9u ZSdzIHdvcmtpbmcgb24gdGhpcy4NCj4+DQo+PiAvSw0KPg0KPg0KPiBUaGFua3MsIEkgYW0gaWdu b3JpbmcgdGhlIHByZXZpb3VzIGNvbW1lbnQgYXMgaXQgbWFrZXMgbm8gcmVhbCBzZW5zZS4NCg0K V2hvb3BzIQ0KDQoncy95b3VyIFpGUyBzdG9yYWdlJ3Mvb3VyIFpGUyBzdG9yYWdlJ3MvJyA6KQ0K DQovSw0KDQo+DQo+Pg0KPj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fXw0KPj4gPiBmcmVlYnNkLWZzQGZyZWVic2Qub3JnIG1haWxpbmcgbGlzdA0KPj4g PiBodHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLWZzDQo+ PiA+IFRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLWZzLXVuc3Vic2Ny aWJlQGZyZWVic2Qub3JnIg0KPg0KPg0KPg0KPg0KPiAtLQ0KPiBHZW9yZ2UgS29udG9zdGFub3MN Cj4gLS0tDQo= From owner-freebsd-stable@FreeBSD.ORG Wed May 20 23:18:26 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16DBD93E for ; Wed, 20 May 2015 23:18:26 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D86CF15A4 for ; Wed, 20 May 2015 23:18:25 +0000 (UTC) Received: by igbyr2 with SMTP id yr2so115622754igb.0 for ; Wed, 20 May 2015 16:18:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neosmart.net; s=google; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=qp0GHckjmrTbGgg3bx7rJTOsGGm6/ZfZrcQHcitwKXA=; b=M2V8iGYGR+7WGjqBN4Tb+YohKkdPjfHvRRcXWEPclfZD7m/db+TVft1tynv7r5W2xH g72Fn5mpP90zKUM4GwNIdM3wSScJoKRfkSss3gK8JmvS944CiS/CwIkYEP9DQTwhSsaV f6mAdVKQWY2xjGO7MMP5f2yFsb9wFYlh8kvY0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=qp0GHckjmrTbGgg3bx7rJTOsGGm6/ZfZrcQHcitwKXA=; b=Ci4o77DWHFjjwTjFdFRspDF27IhhnnigFXRmy2ajVolhTkIsrzbYUlTgOLNvdcwylC yMWTXowYrwlCtLfvxd79ERhpaEC5rvIhNinA0+8TIZ6bUxBkhPmxNFBKfCK77mnVRaFO 2q3/6zpZ6smqN65rqqWkAlMHrwNOCGYQdNtIdX8Os0PqqIunPjX2T10G3MbovVp5KvkH +SafJ9o8nOLKklphgd/1hqPtcLvx1N1MMZ/oFvgnK5lfyDYNplDv07WaiFziwmwzpVZC P9LjVQy1rIxosytq2hplUu4gXLSnx3F6CIDiyctsaKWRp5BEJ6tSDr3YdVajusVNBN80 kvzQ== X-Gm-Message-State: ALoCoQkT19JcQvfRyNQviHYPfcUReFsDD5fqJwaMeJ4qoLb49plpZn77lQ421VLEwzAil6sQM945 X-Received: by 10.50.66.234 with SMTP id i10mr385251igt.22.1432163905219; Wed, 20 May 2015 16:18:25 -0700 (PDT) Received: from ?IPv6:2601:249:e00:ac50::12a5? ([2601:249:e00:ac50::12a5]) by mx.google.com with ESMTPSA id e69sm13466886ioe.11.2015.05.20.16.18.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 May 2015 16:18:23 -0700 (PDT) From: Mahmoud Al-Qudsi Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? Message-Id: <44D62B59-1ABE-4FC3-9E29-39478A94703E@neosmart.net> Date: Wed, 20 May 2015 18:18:20 -0500 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 23:18:26 -0000 Hello, I have not delved too deeply into either the NFS spec or the FreeBSD = nfsd code, but from my admittedly-limited understanding, it seems that = reclaim is both a mandatory feature and one that is present in the current FreeBSD = NFS v4.1 implementation. Is my understanding of this correct? My reason for asking is when attempting to migrate an ESXi server to a = FreeBSD NFSv4.1 datastore, ESXi throws the following error: > WARNING: NFS41: NFS41FSCompleteMount:3601: RECLAIM_COMPLETE FS failed: = Not > supported; forcing read-only operation VMware ESXi 6.0 is able to mount NFSv4.1 shares exported from other=20 operating systems, so I figured I would ask here on the list before = digging out a copy of tcpdump and going down that rabbit hole. I can mount and use NFSv3 shares just fine with ESXi from this same = server, and=20 can mount the same shares as NFSv4 from other clients (e.g. OS X) as = well. Thanks, Mahmoud Al-Qudsi NeoSmart Technologies From owner-freebsd-stable@FreeBSD.ORG Thu May 21 01:54:51 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2699A19C for ; Thu, 21 May 2015 01:54:51 +0000 (UTC) Received: from ms3.isat.co.za (ms3.isat.co.za [196.1.71.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8ACD5176F for ; Thu, 21 May 2015 01:54:48 +0000 (UTC) Received: from ms3 (ms3 [192.168.71.18]) by ms3.isat.co.za with ESMTP ; Thu, 21 May 2015 03:39:53 +0200 Message-ID: <04E8BE51-AE00-459A-A36A-9B9DF35993A9@ms3.isat.co.za> From: "iSAT" To: freebsd-stable@freebsd.org Date: 21 May 2015 03:39:53 +0200 Subject: Will iSAT's ALMMS improve my ADSL speed? MailRef#B4-2066030# MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 01:54:51 -0000 Wed 20 May 2015 ADSL Internet access speed is a very common search used in Google and other search engines. It is also regularly hotly debated on Internet forums. Clearly it is a common concern. Assisting to resolve ADSL speed issues is one of the many benefits of iSAT's ADSL line monitoring and management system. ALMMS helps in three key ways: 1. ALMMS helps to keep your line operating at the speed that you are paying for. So if you are paying for a 4 Mbps line, ALMMS will try and get, and keep your line at that speed. To achieve this, iSAT works directly with Telkom, you do not have to contact them yourself. ALMMS will also let you know what your best speed is, and if this is not going to work for you, you can look for an alternative to ADSL. 2. ALMMS monitors and reports on changes on your ADSL line, so if a Telkom infrastructure upgrade is done, and you can then operate at a higher line speed, ALMMS will let you know. 3. And thirdly and very importantly, ALMMS eliminates the ADSL line as part of the ADSL access speed problem. If ALMMS reports that your line is operating optimally, then you know that the problem has nothing to do with your ADSL line. Which means that the problem is with the ADSL access package that you are using. It might not mean that you have a poor access solution, although this is possible, it could be that have chosen the wrong solution. If you are using ADSL for business, you may need to use a more business oriented type of access option. If you are using your ADSL for downloading movies, or playing games, remember that the cheapest access solution is not always the best. Whatever your usage situation, once you know that your ADSL line is working optimally, you can try various access solutions. Most ISP's will not tie you down to a contract. So if you are using ADSL Internet access, you are relying on a Telkom ADSL line. Then there is absolutely no doubt that you need this ADSL line monitoring and management service from iSAT now. This type of product is unique in South Africa and only available from iSAT. And at only R20 a month, it really is a no-brainer. If your ADSL line is not already with iSAT, get it moved today, it'ss an entirely painless process, and your service will not be interrupted at all. If you have other services with a different ISP, leave them as they are, they will continue working, just get the ADSL line moved now, and enable ALMMS immediately. [1]Click here to see some actual examples of what ALMMS does. For an overview about ALMMS [2]click here. For a detailed description of ALMMS [3]click here. ALMMS is making our competitors nervous, please read some common objections and our responses [4]here. For frequently asked questions about ALMMS [5]click here. For general news about ALMMS [6]click here. Sign up now it will only take 5 minutes Sign up on-line (this is the quickest and easiest method, and completely secure), [7]click here. Or Request a form to fill in and fax through to us, [8]click here. It's time for change, help be part of the solution and not part of the problem Kind regards, If you aren't using ADSL access, please forward this email on to someone who is, they will be grateful for your help. And we apologise for taking up your time. This email was sent to freebsd-stable@freebsd.org. Click [9]Unsubscribe to send us a mail to remove this address from our mailing list. If you have any questions, we would love to hear them. Please mail us at [10]almms@isat.co.za References 1. https://www.isat.co.za/products/adsl-line-monitoring-management-system.aspx?examples=true&mailref=B4-2066030 2. https://www.isat.co.za/products/adsl-line-monitoring-management-system.aspx?overview=true&mailref=B4-2066030 3. https://www.isat.co.za/products/adsl-line-monitoring-management-system.aspx?details=true&mailref=B4-2066030 4. https://www.isat.co.za/products/adsl-line-monitoring-management-system.aspx?objections=true&mailref=B4-2066030 5. https://www.isat.co.za/products/adsl-line-monitoring-management-system.aspx?faqs=true&mailref=B4-2066030 6. https://www.isat.co.za/products/adsl-line-monitoring-management-system.aspx?news=true&mailref=B4-2066030 7. https://www.isat.co.za/ordering/adsl-line-monitoring-management-system.aspx?almms=true&mailref=B4-2066030 8. https://www.isat.co.za/documents/isat-almms-registration-form.pdf 9. mailto:almms@isat.co.za?subject=?Subject=Unsubscribe%20-freebsd-stable@freebsd.org 10. mailto:almms@isat.co.za From owner-freebsd-stable@FreeBSD.ORG Thu May 21 01:57:52 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFBB12BC for ; Thu, 21 May 2015 01:57:52 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 9E0401796 for ; Thu, 21 May 2015 01:57:51 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CxAwCeOl1V/95baINcg2ReBoMYwD4JgVAKhS1KAoF1FAEBAQEBAQGBCoQiAQEBAwEBAQEgKyALBRYYAgINGQIpAQkmBggCBQQBHASIAwgNqzCkBQEBAQEGAQEBAQEBARuBIYoZhCwHAQEFFzQHgmiBRQWXIYQag1w+hiuEe4oJI4Fmgi4iMQd8CRcjgQEBAQE X-IronPort-AV: E=Sophos;i="5.13,466,1427774400"; d="scan'208";a="213626450" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 20 May 2015 21:57:45 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 6E80BB3F85; Wed, 20 May 2015 21:57:43 -0400 (EDT) Date: Wed, 20 May 2015 21:57:43 -0400 (EDT) From: Rick Macklem To: Mahmoud Al-Qudsi Cc: freebsd-stable@freebsd.org Message-ID: <1013279983.41809469.1432173463439.JavaMail.root@uoguelph.ca> In-Reply-To: <44D62B59-1ABE-4FC3-9E29-39478A94703E@neosmart.net> Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 01:57:52 -0000 Mahoud Al-Qudsi wrote: > Hello, > > I have not delved too deeply into either the NFS spec or the FreeBSD > nfsd > code, but from my admittedly-limited understanding, it seems that > reclaim is > both a mandatory feature and one that is present in the current > FreeBSD NFS > v4.1 implementation. Is my understanding of this correct? > Only the global RECLAIM_COMPLETE is implemented. I'll be honest that I don't even really understand what the "single fs reclaim_complete" semantics are and, as such, it isn't implemented. I think it is meant to be used when a file system is migrated from one server to another (transferring the locks to the new server) or something like that. Migration/replication isn't supported. Maybe someday if I figure out what the RFC expects the server to do for this case. > My reason for asking is when attempting to migrate an ESXi server to > a FreeBSD > NFSv4.1 datastore, ESXi throws the following error: > > > WARNING: NFS41: NFS41FSCompleteMount:3601: RECLAIM_COMPLETE FS > > failed: Not > > supported; forcing read-only operation > This is the first time I've heard of a client using this. The only clients I've ever had the opportunity to test against are Linux, Solaris and the FreeBSD one. > VMware ESXi 6.0 is able to mount NFSv4.1 shares exported from other > operating systems, so I figured I would ask here on the list before > digging > out a copy of tcpdump and going down that rabbit hole. > > I can mount and use NFSv3 shares just fine with ESXi from this same > server, and > can mount the same shares as NFSv4 from other clients (e.g. OS X) as > well. > This is NFSv4.1 specific, so NFSv4.0 should work, I think. Or just use NFSv3. rick > Thanks, > > Mahmoud Al-Qudsi > NeoSmart Technologies > > _______________________________________________ > 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 Thu May 21 02:57:13 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1279CD8A for ; Thu, 21 May 2015 02:57:13 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C92CE1E26 for ; Thu, 21 May 2015 02:57:12 +0000 (UTC) Received: by igbhj9 with SMTP id hj9so5370745igb.1 for ; Wed, 20 May 2015 19:57:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neosmart.net; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yq0C9TxWBvA9ll0Dqj+Q9dI+n/0K8q5a8WLoyA4P+qg=; b=Ff0yzBDSoWgncwQ/u2BTfZmeB+JTdagErozwGJQ3U5gSdyGV6DDy/y5+q/8HQSDQGC LV17D+x+GGoEzW1Sn/94pXVhmHyWdeMNM9oRQDlqwpsjnwjwsDRAgFeNDVjE2et6WXSP Br7XjJROPmJ6hGDnOXr8S2Bqd2sMqOl+KLna4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=yq0C9TxWBvA9ll0Dqj+Q9dI+n/0K8q5a8WLoyA4P+qg=; b=RKhAIfBcGY3NcCyWWluei+Tym1SpdRUvsz6Yt0V/GeljIkTshADhAqusjuUs3zHgx5 izGozJKe64mczNuL74OIOjONidDzKwxrd8pHdFdmZW2o2QxV0ea0V3SiLMiHJDM59YxD 6gu8AnfBSqsMxn81WKBJFTyVZpu+FHJXgVk4eiefYUFrN5SADjW6EnZbWHMEyastNJ1Q QIhygkkC1rn208fb5+N4FfZM56V/Fg5sw55xxezac3qN/9DUP7AuUv7ptU3DGiaNiTH1 wedUjkxOAxfd4LwtvVKgAcVHFIMXWjgoR901rFTRWC3K8Un5PB38pM47mCOY08+GDeiw lXFw== X-Gm-Message-State: ALoCoQlteBY3v6SmluiXJ70A1ec6j2KiJOgvmQgq50fKrYNr8dAhN7h5bPgpgNe5iee0nPtJvVIb X-Received: by 10.50.30.69 with SMTP id q5mr1153147igh.11.1432177032218; Wed, 20 May 2015 19:57:12 -0700 (PDT) Received: from ?IPv6:2601:249:e00:ac50::12a5? ([2601:249:e00:ac50::12a5]) by mx.google.com with ESMTPSA id 7sm13853709iol.43.2015.05.20.19.57.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 May 2015 19:57:11 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2100\)) Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? From: Mahmoud Al-Qudsi In-Reply-To: <1013279983.41809469.1432173463439.JavaMail.root@uoguelph.ca> Date: Wed, 20 May 2015 21:57:09 -0500 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <1013279983.41809469.1432173463439.JavaMail.root@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.2100) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 02:57:13 -0000 On May 20, 2015, at 8:57 PM, Rick Macklem wrote: > Only the global RECLAIM_COMPLETE is implemented. I'll be honest that > I don't even really understand what the "single fs reclaim_complete" > semantics are and, as such, it isn't implemented. Thanks for verifying that. > I think it is meant to be used when a file system is migrated from > one server to another (transferring the locks to the new server) or > something like that. > Migration/replication isn't supported. Maybe someday if I figure out > what the RFC expects the server to do for this case. I wasn=E2=80=99t clear on if this was lock reclaiming or block = reclaiming. Thanks. >> I can mount and use NFSv3 shares just fine with ESXi from this same >> server, and >> can mount the same shares as NFSv4 from other clients (e.g. OS X) as >> well. >>=20 > This is NFSv4.1 specific, so NFSv4.0 should work, I think. Or just use = NFSv3. >=20 > rick For some reason, ESXi doesn=E2=80=99t do ESXi 4.0, only v3 or v4.1. I am using NFS v3 for now, but unless I=E2=80=99m mistaken, since = FreeBSD supports neither =E2=80=9Cnohide=E2=80=9D nor =E2=80=9Ccrossmnt=E2=80=9D there is = no way for a single export(/import) to cross ZFS filesystem boundaries.=20 I am using ZFS snapshots to manage virtual machine images, each machine has its own ZFS filesystem so I can snapshot and rollback individually. = But=20 this means that under NFSv3 (so far as I can tell), each =E2=80=9Cfolder=E2= =80=9D (ZFS fs)=20 must be mounted separately on the ESXi host. I can get around exporting=20= them each individually with the -alldirs parameter, but client-side, = there does not seem to be a way of traversing ZFS filesystem mounts without = explicitly mounting each and every one - a maintenance nightmare if there ever was = one. The only thing I can think of would be unions for the top-level = directory, but I=E2=80=99m very, very leery of the the nullfs/unionfs modules as they=E2=80=99ve = been a source of=20 system instability for us in the past (deadlocks, undetected lock = inversions, etc). That and I really rather a maintenance nightmare than a hack. Would you have any other suggestions? Thanks, Mahmoud From owner-freebsd-stable@FreeBSD.ORG Thu May 21 11:07:32 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C20C8DA4; Thu, 21 May 2015 11:07:32 +0000 (UTC) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F86C1AF8; Thu, 21 May 2015 11:07:32 +0000 (UTC) Received: by wizk4 with SMTP id k4so10621178wiz.1; Thu, 21 May 2015 04:07:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OUe2uac6aVgrKI/xGrXJzTJ6KnbFlXBD8kByNq3gXbQ=; b=lX22Yiu7aV7YueNU6OlgPnr9rK6fXDv6UUJ01tcHiVRS/AV8CDaR8Y5LmBd6rSzxQ+ u/KyuASq4l61iyV+j6eVWt5+XUuIh690ARoAY9TuSD63JtuaiiwC7BumNVMgFXqeV4GT /szAsacfRBHo8bZ3Oc5OLRSmzdX/cLFo44SgfvgXUYf1KNUM9Slu8ajLyrtn8FeZE8Nq JCj8rDVlDCBVpG6N8eoplrN2oaP1yOF0gBgXc2ZIXMOWvGjsPfZFQEuWVCv5eDpmRYH3 SM/ZAkoRSFMYshX+O79Q760JvOzMhXaaOFvD5WrxlGEA0fTKHtPZohOYBL6bwg0d6YOs YRaA== MIME-Version: 1.0 X-Received: by 10.180.101.138 with SMTP id fg10mr5238792wib.46.1432206450700; Thu, 21 May 2015 04:07:30 -0700 (PDT) Received: by 10.28.30.22 with HTTP; Thu, 21 May 2015 04:07:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 May 2015 14:07:30 +0300 Message-ID: Subject: Re: L2ARC degraded. Checksum errors, I/O errors From: George Kontostanos To: =?UTF-8?Q?Karli_Sj=C3=B6berg?= Cc: "freebsd-fs@freebsd.org" , freebsd-stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 11:07:32 -0000 On Wed, May 20, 2015 at 11:16 PM, Karli Sj=C3=B6berg wrote: > > Den 20 maj 2015 9:40 em skrev George Kontostanos = : > > > > > > > > On Wed, May 20, 2015 at 9:53 PM, Karli Sj=C3=B6berg > wrote: > >> > >> > >> Den 20 maj 2015 7:50 em skrev Slawa Olhovchenkov : > >> > > >> > On Wed, May 20, 2015 at 07:17:44PM +0300, George Kontostanos wrote: > >> > > >> > > Hello, > >> > > > >> > > Appologies if that has been asked before. I was wondering if the > following > >> > > bug has been addressed so far: > >> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D198242 > >> > > >> > As I know > >> > > >> > kstat.zfs.misc.arcstats.l2_cksum_bad: 14495 > >> > kstat.zfs.misc.arcstats.l2_io_error: 12877 > >> > > >> > caused by hardware failure on L2ARC device. > >> > try replace it. > >> > >> Hardly. We are seeing this phenomenon on all of your ZFS stora hela, > where some of the L2ARC's are new, so I'd be very surprised if these are > real hardware failures. That, as well as being reported by so many, my vo= te > is on bug. > >> > >> @gkontos > >> Thanks for bringing this to attention, I'm also interested in hearing > if anyone's working on this. > >> > >> /K > > > > > > Thanks, I am ignoring the previous comment as it makes no real sense. > > Whoops! > > 's/your ZFS storage's/our ZFS storage's/' :) > > /K > > That too :) But I was referring to the comment made by @slw --=20 George Kontostanos --- From owner-freebsd-stable@FreeBSD.ORG Thu May 21 12:20:47 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E0D756D1 for ; Thu, 21 May 2015 12:20:46 +0000 (UTC) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id A5F3213BF for ; Thu, 21 May 2015 12:20:46 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CsBAAQzV1V/95baINcg2ReBoMZv3SBTwqFLUoCgXwSAQEBAQEBAYEKhCIBAQEDAQEBASArIAsFFhgCAg0ZAikBCSYGCAIFBAEcBIgDCA2sbqQdAQEBBwEBAQEBAQEbgSGKGYQiEAIBBRcBMweCaIFFBZcthBuDYT6GK4R+ig4jgWaCLiIxB4E/gQEBAQE X-IronPort-AV: E=Sophos;i="5.13,468,1427774400"; d="scan'208";a="211860782" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 21 May 2015 08:19:37 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id AB0A9B3F2D; Thu, 21 May 2015 08:19:37 -0400 (EDT) Date: Thu, 21 May 2015 08:19:37 -0400 (EDT) From: Rick Macklem To: Mahmoud Al-Qudsi Cc: freebsd-stable@freebsd.org Message-ID: <1950364073.41930419.1432210777686.JavaMail.root@uoguelph.ca> In-Reply-To: Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 12:20:47 -0000 Mahmoud Al-Qudsi wrote: > On May 20, 2015, at 8:57 PM, Rick Macklem > wrote: > > Only the global RECLAIM_COMPLETE is implemented. I'll be honest > > that > > I don't even really understand what the "single fs > > reclaim_complete" > > semantics are and, as such, it isn't implemented. >=20 > Thanks for verifying that. >=20 > > I think it is meant to be used when a file system is migrated from > > one server to another (transferring the locks to the new server) or > > something like that. > > Migration/replication isn't supported. Maybe someday if I figure > > out > > what the RFC expects the server to do for this case. >=20 > I wasn=E2=80=99t clear on if this was lock reclaiming or block reclaiming= . > Thanks. >=20 > >> I can mount and use NFSv3 shares just fine with ESXi from this > >> same > >> server, and > >> can mount the same shares as NFSv4 from other clients (e.g. OS X) > >> as > >> well. > >>=20 > > This is NFSv4.1 specific, so NFSv4.0 should work, I think. Or just > > use NFSv3. > >=20 > > rick >=20 > For some reason, ESXi doesn=E2=80=99t do ESXi 4.0, only v3 or v4.1. >=20 > I am using NFS v3 for now, but unless I=E2=80=99m mistaken, since FreeBSD > supports > neither =E2=80=9Cnohide=E2=80=9D nor =E2=80=9Ccrossmnt=E2=80=9D there is = no way for a single > export(/import) > to cross ZFS filesystem boundaries. >=20 > I am using ZFS snapshots to manage virtual machine images, each > machine > has its own ZFS filesystem so I can snapshot and rollback > individually. But > this means that under NFSv3 (so far as I can tell), each =E2=80=9Cfolder= =E2=80=9D > (ZFS fs) > must be mounted separately on the ESXi host. I can get around > exporting > them each individually with the -alldirs parameter, but client-side, > there does > not seem to be a way of traversing ZFS filesystem mounts without > explicitly > mounting each and every one - a maintenance nightmare if there ever > was one. >=20 > The only thing I can think of would be unions for the top-level > directory, but I=E2=80=99m > very, very leery of the the nullfs/unionfs modules as they=E2=80=99ve bee= n a > source of > system instability for us in the past (deadlocks, undetected lock > inversions, etc). > That and I really rather a maintenance nightmare than a hack. >=20 > Would you have any other suggestions? >=20 Well, if you are just doing an NFSv4.1 mount, you could capture packets during the failed mount attaempt with tcpdump and then email me the raw packet capture, I can take a look at it. (tcpdump doesn't handle nfs packets well, but wireshark will accept a raw packet capture) Something like: # tcpdump -s 0 -w .pcap host should work. When I read RFC-5661 around page #567, it seems clear that the client should use RECLAIM_COMPLETE with the fs arg false after acquiring a noew clientid, which is what a fresh mount would normally be. (If the packet capture shows an EXCHANGEID followed by a RECLAIM_COMPLETE with the fs arg true, I think ESXi is broken, but I can send you a patch that will just ignore the "true", so it works.) I think the "true" case is only used when a file system has been "moved" by a server cluster, indicated to the client via a NFS4ERR_MOVED error when it is accessed at the old server, but the working in RFC-5661 isn't very clear. rick > Thanks, >=20 > Mahmoud >=20 > _______________________________________________ > 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 Thu May 21 12:29:33 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4C0696D for ; Thu, 21 May 2015 12:29:33 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 535B61553 for ; Thu, 21 May 2015 12:29:32 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CsBACmzl1V/95baINcg2ReBoMZv3WBTwqFLUoCgXwSAQEBAQEBAYEKhCIBAQEDAQEBASArIAsFFhgCAg0ZAikBCSYGCAIFBAEcBIgDCA2sZ6QcAQEBBwEBAQEBAQEbgSGKGYQzAQEFFwEzB4JogUUFly2EG4QfiymKDiOBZoIuIjEHgQU6gQEBAQE X-IronPort-AV: E=Sophos;i="5.13,468,1427774400"; d="scan'208";a="213700155" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 21 May 2015 08:29:31 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 18FE8B3EB1; Thu, 21 May 2015 08:29:31 -0400 (EDT) Date: Thu, 21 May 2015 08:29:31 -0400 (EDT) From: Rick Macklem To: Mahmoud Al-Qudsi Cc: freebsd-stable@freebsd.org Message-ID: <1600389691.41938009.1432211371089.JavaMail.root@uoguelph.ca> In-Reply-To: Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 12:29:33 -0000 Mahmoud Al-Qudsi wrote: > On May 20, 2015, at 8:57 PM, Rick Macklem > wrote: > > Only the global RECLAIM_COMPLETE is implemented. I'll be honest > > that > > I don't even really understand what the "single fs > > reclaim_complete" > > semantics are and, as such, it isn't implemented. >=20 > Thanks for verifying that. >=20 > > I think it is meant to be used when a file system is migrated from > > one server to another (transferring the locks to the new server) or > > something like that. > > Migration/replication isn't supported. Maybe someday if I figure > > out > > what the RFC expects the server to do for this case. >=20 > I wasn=E2=80=99t clear on if this was lock reclaiming or block reclaiming= . > Thanks. >=20 > >> I can mount and use NFSv3 shares just fine with ESXi from this > >> same > >> server, and > >> can mount the same shares as NFSv4 from other clients (e.g. OS X) > >> as > >> well. > >>=20 > > This is NFSv4.1 specific, so NFSv4.0 should work, I think. Or just > > use NFSv3. > >=20 > > rick >=20 Btw, here's a snippet from RFC-5661 (around page#567) that I think clarifies what the client should be doing on a mount. Whenever a client establishes a new client ID and before it does the first non-reclaim operation that obtains a lock, it MUST send a RECLAIM_COMPLETE with rca_one_fs set to FALSE, even if there are no locks to reclaim. If non-reclaim locking operations are done before the RECLAIM_COMPLETE, an NFS4ERR_GRACE error will be returned. It clearly states that rca_one_fs should be FALSE, which is what all the clients I have tested against does. rick > For some reason, ESXi doesn=E2=80=99t do ESXi 4.0, only v3 or v4.1. >=20 > I am using NFS v3 for now, but unless I=E2=80=99m mistaken, since FreeBSD > supports > neither =E2=80=9Cnohide=E2=80=9D nor =E2=80=9Ccrossmnt=E2=80=9D there is = no way for a single > export(/import) > to cross ZFS filesystem boundaries. >=20 > I am using ZFS snapshots to manage virtual machine images, each > machine > has its own ZFS filesystem so I can snapshot and rollback > individually. But > this means that under NFSv3 (so far as I can tell), each =E2=80=9Cfolder= =E2=80=9D > (ZFS fs) > must be mounted separately on the ESXi host. I can get around > exporting > them each individually with the -alldirs parameter, but client-side, > there does > not seem to be a way of traversing ZFS filesystem mounts without > explicitly > mounting each and every one - a maintenance nightmare if there ever > was one. >=20 > The only thing I can think of would be unions for the top-level > directory, but I=E2=80=99m > very, very leery of the the nullfs/unionfs modules as they=E2=80=99ve bee= n a > source of > system instability for us in the past (deadlocks, undetected lock > inversions, etc). > That and I really rather a maintenance nightmare than a hack. >=20 > Would you have any other suggestions? >=20 > Thanks, >=20 > Mahmoud >=20 > _______________________________________________ > 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 Thu May 21 15:33:59 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB5FDE99 for ; Thu, 21 May 2015 15:33:59 +0000 (UTC) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B1EF1D2C for ; Thu, 21 May 2015 15:33:59 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 3A3E220E74 for ; Thu, 21 May 2015 11:33:58 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 21 May 2015 11:33:58 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=smkelly.org; h= content-type:date:from:message-id:mime-version:subject:to :x-sasl-enc:x-sasl-enc; s=mesmtp; bh=8GS+UbLrcYPmwW6zfxZlE7E0V3s =; b=b40yqQHxFaDlZV0Whav5MO05TKq4Vp7IYsijislh5i/4hV+RLwbCu1JI9xI nmITNDLaWo+3y6BiGnvj4kHTIg2t11+0AnrGHnhTtrc8g686S5BJ4yaTTRZ18S9X QylenGVQxwpzyRzwVRpTPO9ttwRYXq5txLYSRCGhClGP4ink= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=8G S+UbLrcYPmwW6zfxZlE7E0V3s=; b=fxs3TB/O30Wmk0JzamZ3kuf4qVEzQAVRkT RL9SqgOhDMZRF9VGRoTuBb+2TE2mbAziyYrhckUsz3yDl8KqVlCkLL96E2KBOAvp x4rVNVhGedtQluud1i2o23vACWNNAgC1tveCoxE4aS6PTlnzr/dcrMZ57vwr4mgU WgGLxr4Cg= X-Sasl-enc: Xy7YI3Jou0PdcyZpgWdkG7FwmW65C6WFzWo4HsaK1PLE 1432222438 Received: from tardis.gwp.corp.flightaware.com (unknown [38.100.147.146]) by mail.messagingengine.com (Postfix) with ESMTPA id F24D56800C7 for ; Thu, 21 May 2015 11:33:57 -0400 (EDT) From: Sean Kelly Subject: 10.1 NVMe kernel panic Message-Id: <90B2D392-01FD-415A-B3D9-3CEDFC8373C4@smkelly.org> Date: Thu, 21 May 2015 10:33:56 -0500 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2100\)) X-Mailer: Apple Mail (2.2100) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 15:33:59 -0000 Greetings. I have a Dell R630 server with four of Dell=E2=80=99s 800GB NVMe SSDs = running FreeBSD 10.1-p10. According to the PCI vendor, they are some = sort of rebranded Samsung drive. If I boot the system and then load = nvme.ko and nvd.ko from a command line, the drives show up okay. If I = put nvme_load=3D=E2=80=9CYES=E2=80=9D nvd_load=3D=E2=80=9CYES=E2=80=9D in /boot/loader.conf, the box panics on boot: panic: nexus_setup_intr: NULL irq resource! If I boot the system with =E2=80=9CSafe Mode: ON=E2=80=9D from the = loader menu, it also boots successfully and the drives show up. You can see a full =E2=80=98boot -v=E2=80=99 here: http://smkelly.org/stuff/nvme-panic.txt = Anyone have any insight into what the issue may be here? Ideally I need = to get this working in the next few days or return this thing to Dell. Thanks! --=20 Sean Kelly smkelly@smkelly.org http://smkelly.org From owner-freebsd-stable@FreeBSD.ORG Fri May 22 07:34:21 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F3F73BD for ; Fri, 22 May 2015 07:34:21 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC4F11A5E for ; Fri, 22 May 2015 07:34:20 +0000 (UTC) Received: from moby.local ([94.216.163.228]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lu8Ri-1ZKHI30foc-011W11 for ; Fri, 22 May 2015 09:34:13 +0200 Message-ID: <555EDBBB.4090107@gmx.com> Date: Fri, 22 May 2015 09:33:15 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: CPU frequency doesn't drop below 1200MHz (like it used to) References: <555C71C8.4080007@gmx.com> In-Reply-To: <555C71C8.4080007@gmx.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:axMH9z3LGLBXx67A5fq+OG4jIF5kekg3V4a6SjHt9Wiz0aifEpU hzUCVVsfNRgR2bZ2ls1ASIL6I8kEi8a6GtZH8+dtiDSGGe74aHD+89/fuEZ2dEuNjnHgUl7 tQO8E4pRI4ddWCIbhw0sdNbqJoTn4v1NzvCAtOy+d7tE5qk8AL8gdu4toSECjp7hF81A+DT 05GSYjIzOT8OyTz3ZWweg== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 07:34:21 -0000 Hi, I just noticed that my CPU's frequency doesn't support dropping below 1200MHz. It used to be able to go down to 150MHz, if I am not mistaken. I'd like it to go down to 600MHz via powerd, like it used to go. This is a month's old 10-STABLE. > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 1400/18055 1300/16611 1200/15194 This is the CPU: > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz Thanks in advance for any ideas, Nikos From owner-freebsd-stable@FreeBSD.ORG Fri May 22 07:42:17 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A56E2709 for ; Fri, 22 May 2015 07:42:17 +0000 (UTC) Received: from frv158.fwdcdn.com (frv158.fwdcdn.com [212.42.77.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 67F841BB0 for ; Fri, 22 May 2015 07:42:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=IjOrCM35UYdYbSgFv6XFMVf1Cql1rxuhMPhpwJBhjEs=; b=G2q8yMSKqim4C1kZ79WpjBtj2ErUpzwdeGkU9bdjld3uVliBIrAtk9MbRP6vTmrSWi4JldzbL9K3vWipPPjRgkncCLZeS+0bkWccO47Odkd/XQIIfJcSyCAc3hmPe00hzDgHN84cf7C0CSD+UWvtUeXzVrqHTIqOIUW/8hCn9fU=; Received: from [134.249.91.180] (helo=nonamehost.local) by frv158.fwdcdn.com with esmtpsa ID 1Yvhav-000PGK-PF ; Fri, 22 May 2015 10:42:13 +0300 Date: Fri, 22 May 2015 10:42:13 +0300 From: Ivan Klymenko To: Nikos Vassiliadis Cc: freebsd-stable@freebsd.org Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) Message-ID: <20150522104213.4e083225@nonamehost.local> In-Reply-To: <555EDBBB.4090107@gmx.com> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Authentication-Result: IP=134.249.91.180; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 07:42:17 -0000 Fri, 22 May 2015 09:33:15 +0200 Nikos Vassiliadis =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0= =B2: > Hi, >=20 > I just noticed that my CPU's frequency doesn't support dropping > below 1200MHz. It used to be able to go down to 150MHz, if I am > not mistaken. I'd like it to go down to 600MHz via powerd, like > it used to go. This is a month's old 10-STABLE. >=20 > > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels > > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 > > 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 > > 1400/18055 1300/16611 1200/15194 >=20 > This is the CPU: > > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz >=20 > Thanks in advance for any ideas, > Nikos Try changing the options in /boot/device.hints hint.acpi_throttle.0.disabled=3D"0" hint.p4tcc.0.disabled=3D"0" From owner-freebsd-stable@FreeBSD.ORG Fri May 22 10:48:57 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B996125; Fri, 22 May 2015 10:48:57 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 5B9CC1204; Fri, 22 May 2015 10:48:57 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id A3AF7D7B; Fri, 22 May 2015 10:48:53 +0000 (UTC) Date: Fri, 22 May 2015 10:48:46 +0000 (GMT) From: jenkins-admin@freebsd.org To: whu@FreeBSD.org, kib@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <637159375.39.1432291731748.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_10-i386 - Build #90 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_10-i386 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 10:48:57 -0000 FreeBSD_STABLE_10-i386 - Build #90 - Failure: Check console output at https://jenkins.freebsd.org/job/FreeBSD_STABLE_10-i386/90/ to view the results. From owner-freebsd-stable@FreeBSD.ORG Fri May 22 11:58:38 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8B68B7B1 for ; Fri, 22 May 2015 11:58:38 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09F8F1ADA for ; Fri, 22 May 2015 11:58:38 +0000 (UTC) Received: from moby.local ([94.216.163.228]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0LZhoi-1ZadBJ1Swu-00lQyR; Fri, 22 May 2015 13:58:29 +0200 Message-ID: <555F19B6.4070707@gmx.com> Date: Fri, 22 May 2015 13:57:42 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Ivan Klymenko CC: freebsd-stable@freebsd.org Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> In-Reply-To: <20150522104213.4e083225@nonamehost.local> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:S7A1M/yJlDPBs7jD+N6IBhdCyokIPKDSw0kunqo8Ii0VYjApwoR nGAyFWMDPOoI0ImBq2kix1RKQVsZxMvAWOtHsSoOIm9MV0iZdxWvqJJtLB2gLQ8p7nbPJM3 iyGLN1a/ALuUfczsgefuw8CnTD8ETg5ddBp5Huq26a57XgnO6X5lyMkkUf4wwV4kgrZgk0a NP/0cxROoAI+J5SAAvIhg== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 11:58:38 -0000 On 05/22/15 09:42, Ivan Klymenko wrote: > Try changing the options in /boot/device.hints > hint.acpi_throttle.0.disabled="0" > hint.p4tcc.0.disabled="0" Thanks Ivan, now it works as it did before! From owner-freebsd-stable@FreeBSD.ORG Fri May 22 13:28:51 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D56DFBA2 for ; Fri, 22 May 2015 13:28:51 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C147152D for ; Fri, 22 May 2015 13:28:51 +0000 (UTC) Received: by lbbqq2 with SMTP id qq2so12845184lbb.3 for ; Fri, 22 May 2015 06:28:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=w6vHIRp+KlXadytAmunf/J98rtWFIeeNTlf7r4BhsQY=; b=zBsGp0Clt7cFHs2yxUQnsdPaT8PnOX4T8GkqkAvK09ST3As1Tp7+29t1pEBEkL0Ylv actA4ydp3CXlb8JFG7Flk0Kx6I8feP16WNPCm/nJj7DE7qUGsMW+a9S1FqeeWxqbvq4C nLbNj7ZvH3FU9Xo3b3+6jeS9G09wqcXiKJDF9hLlerPyzpNteuAkaED2Zx4NjffmhqaW 51wdxxSva+aK6MEJU7FwQ+Tak8NTP1s//sZJOV1oDJWASYm9E+kQo3JQqiEUozVJcfkX xl3zQjhWAodG4rtBTOzSOLwDmbwmUzjdg9v9OEox3k3VRS9u3KookTT2EQclQqAByoTO Mnhw== MIME-Version: 1.0 X-Received: by 10.152.164.233 with SMTP id yt9mr6611604lab.58.1432301329144; Fri, 22 May 2015 06:28:49 -0700 (PDT) Received: by 10.152.137.193 with HTTP; Fri, 22 May 2015 06:28:49 -0700 (PDT) In-Reply-To: <20150522104213.4e083225@nonamehost.local> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> Date: Fri, 22 May 2015 16:28:49 +0300 Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Kimmo Paasiala To: Ivan Klymenko Cc: Nikos Vassiliadis , "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 13:28:51 -0000 On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: > Fri, 22 May 2015 09:33:15 +0200 > Nikos Vassiliadis =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0= =B2: > >> Hi, >> >> I just noticed that my CPU's frequency doesn't support dropping >> below 1200MHz. It used to be able to go down to 150MHz, if I am >> not mistaken. I'd like it to go down to 600MHz via powerd, like >> it used to go. This is a month's old 10-STABLE. >> >> > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels >> > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 >> > 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 >> > 1400/18055 1300/16611 1200/15194 >> >> This is the CPU: >> > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz >> >> Thanks in advance for any ideas, >> Nikos > > Try changing the options in /boot/device.hints > hint.acpi_throttle.0.disabled=3D"0" > hint.p4tcc.0.disabled=3D"0" Thanks, those also fixed powerd(8) for me that stopped working after upgrading to stable/10 from releng/10.1. Why are those setting suddenly needed now? -Kimmo From owner-freebsd-stable@FreeBSD.ORG Fri May 22 14:56:14 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AAD3EFA1; Fri, 22 May 2015 14:56:14 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 9A1221FBD; Fri, 22 May 2015 14:56:14 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 14D7FDF9; Fri, 22 May 2015 14:56:13 +0000 (UTC) Date: Fri, 22 May 2015 14:56:09 +0000 (GMT) From: jenkins-admin@freebsd.org To: whu@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <1936971844.44.1432306570095.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <637159375.39.1432291731748.JavaMail.jenkins@jenkins-9.freebsd.org> References: <637159375.39.1432291731748.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_10-i386 - Build #91 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_10-i386 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 14:56:14 -0000 FreeBSD_STABLE_10-i386 - Build #91 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_STABLE_10-i386/91/ to view the results. From owner-freebsd-stable@FreeBSD.ORG Fri May 22 17:19:37 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 91A3CC58 for ; Fri, 22 May 2015 17:19:37 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFC8C1152 for ; Fri, 22 May 2015 17:19:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id t4MHJPQl074933; Sat, 23 May 2015 03:19:26 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 23 May 2015 03:19:25 +1000 (EST) From: Ian Smith To: Kimmo Paasiala cc: Ivan Klymenko , Nikos Vassiliadis , freebsd-stable@freebsd.org Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) In-Reply-To: Message-ID: <20150523014640.K7173@sola.nimnet.asn.au> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 17:19:37 -0000 On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: > Fri, 22 May 2015 09:33:15 +0200 > Nikos Vassiliadis ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ: > >> Hi, >> >> I just noticed that my CPU's frequency doesn't support dropping >> below 1200MHz. It used to be able to go down to 150MHz, if I am >> not mistaken. I'd like it to go down to 600MHz via powerd, like >> it used to go. This is a month's old 10-STABLE. >> >> > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels >> > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 >> > 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 >> > 1400/18055 1300/16611 1200/15194 >> >> This is the CPU: >> > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz >> >> Thanks in advance for any ideas, >> Nikos > > Try changing the options in /boot/device.hints > hint.acpi_throttle.0.disabled="0" > hint.p4tcc.0.disabled="0" > Thanks, those also fixed powerd(8) for me that stopped working after > upgrading to stable/10 from releng/10.1. Why are those setting > suddenly needed now? > > -Kimmo Looks like the changes to these two hints, now defaulting to 1, committed to -head some months ago has been merged to stable/10. Can you say exactly in what way powerd stopped working then? Except that the minimum frequency that may be set with powerd's -m switch will be higher without p4tcc (or acpi_throttle) running, this change shouldn't hurt powerd; if anything it should be more efficient, as the lower p4tcc-generated frequencies don't save much if any power. If you compare dev.cpu.0.freq_levels, as above, both before and after booting with the changed hints, you can see the ones due to p4tcc's use of subfrequencies with factors of 1/8 to 7/8 of some base freq, but the power use in milliWatts provided for these seems largely ficticious. On my Lenovo X200, Core2Duo 2.4GHz, idling on battery at 800MHz (minimum EST freq) or at 100MHz using p4tcc draws almost exactly the same power, about 7.6W measured from the battery - but responsiveness as performance is required is a great deal better using just the base EST freqs; YMMV. This generally gets discussed on the freebsd-mobile and freebsd-acpi lists; not sure if a deeper discussion of issues is warranted here. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Fri May 22 17:26:43 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41C6EE3A for ; Fri, 22 May 2015 17:26:43 +0000 (UTC) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB1FA1270 for ; Fri, 22 May 2015 17:26:42 +0000 (UTC) Received: by labbd9 with SMTP id bd9so17178589lab.2 for ; Fri, 22 May 2015 10:26:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=NmKiXg6t8IiS4fjqIYDne3fKE6U3RhOONPX2Jcofrss=; b=ejrkp5csdq5HqB9OStIdRzpaqrSVoMorSpKXTM2eWpxJBvhMIksRD9wgGHMFdgKJ9f OWbj3w7hj+Ci2FQyEjtr6i+mMoBy+R44gaQuBrMyZ5ECDYIe0STrVg1rEle2kxExPF3N suiNv9dQfDo7Jb48/1zDH82SWkRSamugr+Q5Q1ZD8xNyL0X+Wxb+F713lbLFJNledlEZ sXooJtUDCIpG/Li15TvD14yNg8cC+BnXzIVtCbMjdiZuo5cWCLIf2Bzma47mD9jVAO6E kIu9ESiyWS5/d9lDVmegee4PiTSRhnRAWFpvoo6F3YNz9M+HLGfIR1YsgZjDimFeWx/u GPQA== MIME-Version: 1.0 X-Received: by 10.112.72.40 with SMTP id a8mr4371195lbv.58.1432315600717; Fri, 22 May 2015 10:26:40 -0700 (PDT) Received: by 10.152.137.193 with HTTP; Fri, 22 May 2015 10:26:40 -0700 (PDT) In-Reply-To: <20150523014640.K7173@sola.nimnet.asn.au> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> Date: Fri, 22 May 2015 20:26:40 +0300 Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Kimmo Paasiala To: Ian Smith Cc: Ivan Klymenko , Nikos Vassiliadis , "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 17:26:43 -0000 On Fri, May 22, 2015 at 8:19 PM, Ian Smith wrote: > On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: >> Fri, 22 May 2015 09:33:15 +0200 >> Nikos Vassiliadis =D1=8F=D1=8F=D1=8F=D1=8F=D1=8F=D1=8F= =D1=8F=D1=8F=D1=8F=D1=8F=D1=8F=D1=8F=D1=8F=D1=8F: >> >>> Hi, >>> >>> I just noticed that my CPU's frequency doesn't support dropping >>> below 1200MHz. It used to be able to go down to 150MHz, if I am >>> not mistaken. I'd like it to go down to 600MHz via powerd, like >>> it used to go. This is a month's old 10-STABLE. >>> >>> > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels >>> > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 >>> > 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 >>> > 1400/18055 1300/16611 1200/15194 >>> >>> This is the CPU: >>> > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz >>> >>> Thanks in advance for any ideas, >>> Nikos >> >> Try changing the options in /boot/device.hints >> hint.acpi_throttle.0.disabled=3D"0" >> hint.p4tcc.0.disabled=3D"0" > > > Thanks, those also fixed powerd(8) for me that stopped working after > > upgrading to stable/10 from releng/10.1. Why are those setting > > suddenly needed now? > > > > -Kimmo > > Looks like the changes to these two hints, now defaulting to 1, > committed to -head some months ago has been merged to stable/10. > > Can you say exactly in what way powerd stopped working then? Powerd(8) complained (excerpt from dmesg -a): Starting powerd. powerd: no cpufreq(4) support -- aborting: No such file or directory /etc/rc: WARNING: failed to start powerd Putting those two settings in loader.conf and rebooting fixed the problem and powerd started working again apparently because cpufreq(4) device was available again. -Kimmo > > Except that the minimum frequency that may be set with powerd's -m > switch will be higher without p4tcc (or acpi_throttle) running, this > change shouldn't hurt powerd; if anything it should be more efficient, > as the lower p4tcc-generated frequencies don't save much if any power. > > If you compare dev.cpu.0.freq_levels, as above, both before and after > booting with the changed hints, you can see the ones due to p4tcc's use > of subfrequencies with factors of 1/8 to 7/8 of some base freq, but the > power use in milliWatts provided for these seems largely ficticious. > > On my Lenovo X200, Core2Duo 2.4GHz, idling on battery at 800MHz (minimum > EST freq) or at 100MHz using p4tcc draws almost exactly the same power, > about 7.6W measured from the battery - but responsiveness as performance > is required is a great deal better using just the base EST freqs; YMMV. > > This generally gets discussed on the freebsd-mobile and freebsd-acpi > lists; not sure if a deeper discussion of issues is warranted here. > > cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Fri May 22 18:30:08 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1A9EAE6; Fri, 22 May 2015 18:30:08 +0000 (UTC) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A1FD31A63; Fri, 22 May 2015 18:30:08 +0000 (UTC) Received: from fwd30.aul.t-online.de (fwd30.aul.t-online.de [172.20.26.135]) by mailout01.t-online.de (Postfix) with SMTP id C84015043F4; Fri, 22 May 2015 20:29:59 +0200 (CEST) Received: from [192.168.119.11] (Tl7K7mZCrhOEPoFnprfVb50i-LKsIQOHu0G9bcphhz0YlbdNmEBp9ruXa1SrReYwV+@[84.154.106.214]) by fwd30.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1Yvrhj-0dllYG0; Fri, 22 May 2015 20:29:55 +0200 Message-ID: <555F7599.5000605@freebsd.org> Date: Fri, 22 May 2015 20:29:45 +0200 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Nikos Vassiliadis CC: freebsd-stable Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> In-Reply-To: <555EDBBB.4090107@gmx.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-ID: Tl7K7mZCrhOEPoFnprfVb50i-LKsIQOHu0G9bcphhz0YlbdNmEBp9ruXa1SrReYwV+ X-TOI-MSGID: b177711b-380d-4b30-a1c4-b92fa6317367 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 18:30:09 -0000 Am 22.05.2015 um 09:33 schrieb Nikos Vassiliadis: > Hi, > > I just noticed that my CPU's frequency doesn't support dropping > below 1200MHz. It used to be able to go down to 150MHz, if I am > not mistaken. I'd like it to go down to 600MHz via powerd, like > it used to go. This is a month's old 10-STABLE. > >> [nik@moby ~]$ sysctl dev.cpu.0.freq_levels >> dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 >> 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 >> 1400/18055 1300/16611 1200/15194 > > This is the CPU: >> hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz Well, your CPU does not support clock frequencies below 1200 MHz. Throttling works by injection of "wait cycles" that reduce the amount of work the CPU can perform per unit of time, but does not really lower the CPU frequency. That means, that with throttling the CPU will need more energy to perform some calculation than it would without. If you select 150 MHz, then your CPU will be clocked at 1200 MHz, but will only perform any operations on each 8th clock cycle. This limits peak energy consumption (and that was the reason this feature was introduced in the power-hungry Pentium-4 processors), but increases the amount of energy needed to perform the computation. The power consumption of your CPU may be (an estimated) 50% to 70% at "150 Mhz" compared to 1200 Mhz. But you'll need 8 times as long until the CPU can fall into a deep sleep state. Since RAM and other components see the same clock whether throttling is enabled or not, you'll need 8 times as long full power for your RAM (which will also go into a low power refresh mode, when the CPU is idle). Throttling has been disabled, because there are no longer any CPUs which need it to prevent overheating. (Or rather: there are now better mechanisms than throttling, which are implemented in any modern x68 CPU.) Throttling could also impact system stability. It really serves no purpose anymore and it was never suitable to improve the power efficiency of e.g. a laptop computer. You'll see better battery live if you keep throttling disabled. Regards, STefan From owner-freebsd-stable@FreeBSD.ORG Fri May 22 18:47:59 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1EE76240; Fri, 22 May 2015 18:47:59 +0000 (UTC) Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD33C1CC2; Fri, 22 May 2015 18:47:58 +0000 (UTC) Received: by iebgx4 with SMTP id gx4so37644045ieb.0; Fri, 22 May 2015 11:47:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=cWLj6dAptnh500IXPj5u2fxdo2MB/1l2qJSut+8+iSc=; b=Mx9haUyj3WDFZl3jnKozeyhAv9TIDEAfIHrRgVKv/L2527dIbv+TytgNIVrqz7Q+f0 4spdO8StNmCcfaxxchwgDa8XLMh0auhrmt/osI1UbXMyuIGQ88kPSrPfXUIg99hzoXFL hEVN3RuOwYD5w7c1/AmLEU0e0mg20CA/wOwx+vfpgJNKeAwltXVATSgH/CS6RhnjM6K6 9k0f3WgfLh9n5oXPxIVUvgm9jd+yxmCHYigVDbnfGoxwVjwoJzmUlA8cJW4/H8jD/n1J 7jj3dzknuYs1HuIpP/hXjDKJqF5xMdoI5CPr1RfCfD1O7yXaQO3VQJCltTKEoVaEndlZ FwMw== MIME-Version: 1.0 X-Received: by 10.50.114.9 with SMTP id jc9mr7460344igb.49.1432320478293; Fri, 22 May 2015 11:47:58 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Fri, 22 May 2015 11:47:58 -0700 (PDT) In-Reply-To: <555F7599.5000605@freebsd.org> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <555F7599.5000605@freebsd.org> Date: Fri, 22 May 2015 11:47:58 -0700 X-Google-Sender-Auth: l7BGVcMt0wlomc0WHCFqXCmnsXw Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Adrian Chadd To: Stefan Esser Cc: Nikos Vassiliadis , freebsd-stable Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 18:47:59 -0000 Hi, The whole point of throttling on modern hardware isn't to get really low clock rates, it's to deal with being out of thermal envelope. But, the modern intel cores will do that for you without OS involvement. So, you don't have to actually use p4tcc and it may actually configure your hardware wrong. Just throttle down to 1200MHz and go into deeper sleep states (>C1). I checked this on a variety of older and modern hardware; they all worked better just doing lowest ACPI P state and lowest ACPI C state. -adrian From owner-freebsd-stable@FreeBSD.ORG Fri May 22 20:59:12 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D7FB8BC; Fri, 22 May 2015 20:59:12 +0000 (UTC) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 151731C23; Fri, 22 May 2015 20:59:12 +0000 (UTC) Received: by igcau1 with SMTP id au1so41611525igc.1; Fri, 22 May 2015 13:59:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=g1yQcWgwR1oGMD5a0TUG0U6dDj14PeWK64hS1kcVsz0=; b=XKn+qv4ONApMrVXbPvrlE0U7y8Amzj9A9p+64Kc23BMWKGFySiZdtBiGEEJ68oUlOo rwlm0MhhY1grfBitOBGiSyq5aB4GubUMvKXn8DwW5rVeR+tC3EOYxTqz1UpmjiGb6CK+ 5gFPm52KiCPop80gCtFUeTLQZrCgCt5UcxFzBBKwSLZOhpLtcMfep9sVtgtZUg/dmc4n kbsqFO0Vv9dZZJtR3rJnRXzFMsI+ugeQJQeZZk2/8xbOSpPCmUC7S2cubiB6aKnAIVJp V4jhS6aXMPp+WLUB5yPsF+Tb4/bdYkUUmjvf3g0zy+0DBccrqZjA+7C2TjHZOhgrvQ7O yRwQ== MIME-Version: 1.0 X-Received: by 10.43.34.205 with SMTP id st13mr11672680icb.4.1432328351518; Fri, 22 May 2015 13:59:11 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.174.22 with HTTP; Fri, 22 May 2015 13:59:11 -0700 (PDT) In-Reply-To: References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <555F7599.5000605@freebsd.org> Date: Fri, 22 May 2015 13:59:11 -0700 X-Google-Sender-Auth: MAbWRawMOEKXiDA2-dksRYQ05os Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Kevin Oberman To: Adrian Chadd Cc: Stefan Esser , Nikos Vassiliadis , freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2015 20:59:12 -0000 On Fri, May 22, 2015 at 11:47 AM, Adrian Chadd wrote: > Hi, > > The whole point of throttling on modern hardware isn't to get really > low clock rates, it's to deal with being out of thermal envelope. > > But, the modern intel cores will do that for you without OS involvement. > > So, you don't have to actually use p4tcc and it may actually configure > your hardware wrong. Just throttle down to 1200MHz and go into deeper > sleep states (>C1). I checked this on a variety of older and modern > hardware; they all worked better just doing lowest ACPI P state and > lowest ACPI C state. > > > > -adrian > > It's actually worse than this. TCC (which was first available on the Pentium 4) was always documented by Intel as a Thermal Control Circuit. Nothing about power management. FreeBSD suborned it for power management a long time go, but it never actually saved power. EST , which adjusts frequency and voltage does save a bit. Cx states save a lot. Using TCC for this was a very bad idea. (I did research on this back when I worked for Berkeley Lab.) There are a couple of very limited corner cases where throttling MAY save an utterly insignificant amount of power, but when C-states came about, Intel never considered the impact of C-states when the OS was playing around with throttling. (Windows never did that.) If you want to save power, set both economy_cx_lowest (battery) and performance_cx_lowest (AC) to Cmax in rc.conf. (This is the default in head.) Do not set a minimum frequency for powerd or it may fail to start if you specify a "frequncy" that is no longer available. That capability was to prevent system lockups when TCC and Cx collided. With TCC off, there is no need to worry about it. Please don't just turn TCC back on. It really just makes things worse. Read mav's excellent article on the issues on the FreeBSD wiki at https://wiki.freebsd.org/TuningPowerConsumption. His research and mine came to virtually identical conclusions. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Sat May 23 07:00:43 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48DA93BA for ; Sat, 23 May 2015 07:00:43 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B00C61957 for ; Sat, 23 May 2015 07:00:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id t4N70Z0M009427; Sat, 23 May 2015 17:00:36 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 23 May 2015 17:00:35 +1000 (EST) From: Ian Smith To: Kimmo Paasiala cc: Ivan Klymenko , Nikos Vassiliadis , "freebsd-stable@freebsd.org" Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) In-Reply-To: Message-ID: <20150523163014.U7173@sola.nimnet.asn.au> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 07:00:43 -0000 On Fri, 22 May 2015 20:26:40 +0300, Kimmo Paasiala wrote: > On Fri, May 22, 2015 at 8:19 PM, Ian Smith wrote: > > On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > > > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: [..] > >> Try changing the options in /boot/device.hints > >> hint.acpi_throttle.0.disabled="0" > >> hint.p4tcc.0.disabled="0" > > > > > Thanks, those also fixed powerd(8) for me that stopped working after > > > upgrading to stable/10 from releng/10.1. Why are those setting > > > suddenly needed now? > > > > > > -Kimmo [..] > > Can you say exactly in what way powerd stopped working then? > > Powerd(8) complained (excerpt from dmesg -a): > > Starting powerd. > powerd: no cpufreq(4) support -- aborting: No such file or directory > /etc/rc: WARNING: failed to start powerd > > Putting those two settings in loader.conf and rebooting fixed the > problem and powerd started working again apparently because cpufreq(4) > device was available again. Ok, if anabling acpi_throttle and/or p4tcc made cpufreq - and thus powerd - work for you, then it seems likely that you do not have EST enabled in your BIOS. Or at least, we've seen another instance where that was the case, which was fixed by enabling EST (or however your particular BIOS refers to it .. AMD for example use different terms). What CPU is this? In what machine? If EST (ono) IS enabled in your BIOS, this needs further investigation. As is, powerd may be running, but it's doing so highly inefficiently; refer to Stefan, Adrian and Kevin's responses for details. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Sat May 23 11:01:18 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4861756 for ; Sat, 23 May 2015 11:01:18 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33253117D for ; Sat, 23 May 2015 11:01:18 +0000 (UTC) Received: by lbbzk7 with SMTP id zk7so27393986lbb.0 for ; Sat, 23 May 2015 04:01:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IXpoVgE2NelTrCvh0OMNN/NeozHNM3+qi+3zSeUIpmA=; b=ecwV5hmWfeOWWJFkwTIjDT70Jjct3/m+Wu1ZLx3CsDIA4VeG4s17ckGwj4Zglh3M95 b+/Gn9FFZOs4kru/0s6V1WvZc4D8LENdmkgogpEDyuxDthykI9zXQe8YkNpJ49XeByER v08cavcudaAwDlEmSF9rQdGIAfo9ReHLKANovx1GMQy3e0gybPf+0q8yPDHFbL3OHKqO vXZdf1BNq5muR6jhEIfzmI4FSSMdlt1EppSMsVwRi582dcXV6hfouePCWtw76YIRVmJl ycq+xNOuoCm5AN7ltnRKkwz2722phKalyPJTCupipFJgs2xMIorrAXNieg9dmwqoyzRH 77pg== MIME-Version: 1.0 X-Received: by 10.152.27.105 with SMTP id s9mr10185642lag.86.1432378876241; Sat, 23 May 2015 04:01:16 -0700 (PDT) Received: by 10.152.137.193 with HTTP; Sat, 23 May 2015 04:01:16 -0700 (PDT) In-Reply-To: <20150523163014.U7173@sola.nimnet.asn.au> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> <20150523163014.U7173@sola.nimnet.asn.au> Date: Sat, 23 May 2015 14:01:16 +0300 Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Kimmo Paasiala To: Ian Smith Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 11:01:18 -0000 On Sat, May 23, 2015 at 10:00 AM, Ian Smith wrote: > On Fri, 22 May 2015 20:26:40 +0300, Kimmo Paasiala wrote: > > On Fri, May 22, 2015 at 8:19 PM, Ian Smith wrote: > > > On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > > > > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: > [..] > > >> Try changing the options in /boot/device.hints > > >> hint.acpi_throttle.0.disabled="0" > > >> hint.p4tcc.0.disabled="0" > > > > > > > Thanks, those also fixed powerd(8) for me that stopped working after > > > > upgrading to stable/10 from releng/10.1. Why are those setting > > > > suddenly needed now? > > > > > > > > -Kimmo > [..] > > > Can you say exactly in what way powerd stopped working then? > > > > Powerd(8) complained (excerpt from dmesg -a): > > > > Starting powerd. > > powerd: no cpufreq(4) support -- aborting: No such file or directory > > /etc/rc: WARNING: failed to start powerd > > > > Putting those two settings in loader.conf and rebooting fixed the > > problem and powerd started working again apparently because cpufreq(4) > > device was available again. > > Ok, if anabling acpi_throttle and/or p4tcc made cpufreq - and thus > powerd - work for you, then it seems likely that you do not have EST > enabled in your BIOS. Or at least, we've seen another instance where > that was the case, which was fixed by enabling EST (or however your > particular BIOS refers to it .. AMD for example use different terms). > > What CPU is this? In what machine? > > If EST (ono) IS enabled in your BIOS, this needs further investigation. > > As is, powerd may be running, but it's doing so highly inefficiently; > refer to Stefan, Adrian and Kevin's responses for details. > > cheers, Ian It's an Intel Atom running amd64 version of FreeBSD stable/10: FreeBSD firewall.rdnzl.info 10.1-STABLE FreeBSD 10.1-STABLE #1 r283292: Sat May 23 01:08:03 EEST 2015 root@firewall.rdnzl.info:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.68-MHz K8-class CPU) Origin="GenuineIntel" Id=0x106ca Family=0x6 Model=0x1c Stepping=10 Features=0xbfebfbff Features2=0x40e31d AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics Powerd was working on 10.1-RELEASE but stopped working after upgrade to 10-STABLE and nothing was changed in BIOS settings. However, reading the other replies to this thread I get the impression that powerd(8) doesn't actually save energy on this platform and I'm better off without it? -Kimmo From owner-freebsd-stable@FreeBSD.ORG Sat May 23 14:15:23 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74F9345C for ; Sat, 23 May 2015 14:15:23 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB89A13D9 for ; Sat, 23 May 2015 14:15:22 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id t4NEFIjQ023727; Sun, 24 May 2015 00:15:18 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 24 May 2015 00:15:18 +1000 (EST) From: Ian Smith To: Kimmo Paasiala cc: "freebsd-stable@freebsd.org" Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) In-Reply-To: Message-ID: <20150523234646.R7173@sola.nimnet.asn.au> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> <20150523163014.U7173@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 14:15:23 -0000 On Sat, 23 May 2015 14:01:16 +0300, Kimmo Paasiala wrote: > On Sat, May 23, 2015 at 10:00 AM, Ian Smith wrote: > > On Fri, 22 May 2015 20:26:40 +0300, Kimmo Paasiala wrote: > > > On Fri, May 22, 2015 at 8:19 PM, Ian Smith wrote: > > > > On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > > > > > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: > > [..] > > > >> Try changing the options in /boot/device.hints > > > >> hint.acpi_throttle.0.disabled="0" > > > >> hint.p4tcc.0.disabled="0" > > > > > > > > > Thanks, those also fixed powerd(8) for me that stopped working after > > > > > upgrading to stable/10 from releng/10.1. Why are those setting > > > > > suddenly needed now? > > [..] > > > > Can you say exactly in what way powerd stopped working then? > > > > > > Powerd(8) complained (excerpt from dmesg -a): > > > > > > Starting powerd. > > > powerd: no cpufreq(4) support -- aborting: No such file or directory > > > /etc/rc: WARNING: failed to start powerd > > > > > > Putting those two settings in loader.conf and rebooting fixed the > > > problem and powerd started working again apparently because cpufreq(4) > > > device was available again. > > > > Ok, if anabling acpi_throttle and/or p4tcc made cpufreq - and thus > > powerd - work for you, then it seems likely that you do not have EST > > enabled in your BIOS. Or at least, we've seen another instance where > > that was the case, which was fixed by enabling EST (or however your > > particular BIOS refers to it .. AMD for example use different terms). > > > > What CPU is this? In what machine? > > > > If EST (ono) IS enabled in your BIOS, this needs further investigation. > > > > As is, powerd may be running, but it's doing so highly inefficiently; > > refer to Stefan, Adrian and Kevin's responses for details. > It's an Intel Atom running amd64 version of FreeBSD stable/10: > > FreeBSD firewall.rdnzl.info 10.1-STABLE FreeBSD 10.1-STABLE #1 > r283292: Sat May 23 01:08:03 EEST 2015 > root@firewall.rdnzl.info:/usr/obj/usr/src/sys/GENERIC amd64 > > CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.68-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x106ca Family=0x6 Model=0x1c Stepping=10 > Features=0xbfebfbff > Features2=0x40e31d > AMD Features=0x20100800 > AMD Features2=0x1 > TSC: P-state invariant, performance statistics > > Powerd was working on 10.1-RELEASE but stopped working after upgrade > to 10-STABLE and nothing was changed in BIOS settings. Which would be consistent with EST not being enabled in your BIOS; with no EST, cpufreq(4) still checks for 'relative' drivers such as p4tcc or acpi_throttle and uses that, as a last resort really; with those also disabled, no cpufreq, so no powerd. Have you checked BIOS settings to confirm that you do have SpeedStep (however termed) properly enabled? Please show `sysctl dev.cpu dev.est` and `sysctl -a | grep freq_levels` > However, reading the other replies to this thread I get the impression > that powerd(8) doesn't actually save energy on this platform and I'm > better off without it? No, I don't think that's correct; using deeper C-states is most likely a bigger win, but higher than needed CPU freq will still use extra power, so run hotter. `sysctl dev.cpu` will also reveal your C-state usage. Reason I'm pursuing this is that this change shouldn't hurt, but it will flush out those cases where people were only getting cpufreq due to use of a 'relative' cpufreq driver like p4tcc, unless EST's enabled in BIOS; I suspect yours may be one such case :) If not, there's a bug to fix. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Sat May 23 14:40:30 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5052860 for ; Sat, 23 May 2015 14:40:29 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5614E164A for ; Sat, 23 May 2015 14:40:29 +0000 (UTC) Received: by lbbzk7 with SMTP id zk7so29265143lbb.0 for ; Sat, 23 May 2015 07:40:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6IzIFCodNBntDjzduFv7uwT+InPzKqI5RDgnLTKXM4w=; b=jkDG9SsY9EF23T0freFRvCXwRIppLbHlAqAht+Ljxz9d+/GdJqUQxrWfPWHp/B+sag GxlFOGbahQouTVIBg8/NXNvNI0bjPObLgp/09b/B7WhLjxsDR0/LFIH5Zax10Slg/uXO e0ZZ9TS2fDbKpkIFLn5kGFyfzRI9/QgWittEavu1ItuNARC8nI1Gy2W/MN8kQWAp+eb9 y8BMvasygVSw7RjAKTUHXSO3bs8u+F2hUxpPOOxmW2Se74lzrnpte2Ulksd51oY7fHIn EVfy04fkgTSoZQ+4zha5aj6f+1XddFVeieCyy9xTApC0YS54kxrQN7nuQnlRPt6c1Vfi CBCw== MIME-Version: 1.0 X-Received: by 10.152.22.34 with SMTP id a2mr10911115laf.59.1432392026818; Sat, 23 May 2015 07:40:26 -0700 (PDT) Received: by 10.152.137.193 with HTTP; Sat, 23 May 2015 07:40:26 -0700 (PDT) In-Reply-To: <20150523234646.R7173@sola.nimnet.asn.au> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> <20150523163014.U7173@sola.nimnet.asn.au> <20150523234646.R7173@sola.nimnet.asn.au> Date: Sat, 23 May 2015 17:40:26 +0300 Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Kimmo Paasiala To: Ian Smith Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 14:40:30 -0000 On Sat, May 23, 2015 at 5:15 PM, Ian Smith wrote: > On Sat, 23 May 2015 14:01:16 +0300, Kimmo Paasiala wrote: > > On Sat, May 23, 2015 at 10:00 AM, Ian Smith wrote: > > > On Fri, 22 May 2015 20:26:40 +0300, Kimmo Paasiala wrote: > > > > On Fri, May 22, 2015 at 8:19 PM, Ian Smith wrote: > > > > > On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > > > > > > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: > > > [..] > > > > >> Try changing the options in /boot/device.hints > > > > >> hint.acpi_throttle.0.disabled="0" > > > > >> hint.p4tcc.0.disabled="0" > > > > > > > > > > > Thanks, those also fixed powerd(8) for me that stopped working after > > > > > > upgrading to stable/10 from releng/10.1. Why are those setting > > > > > > suddenly needed now? > > > [..] > > > > > Can you say exactly in what way powerd stopped working then? > > > > > > > > Powerd(8) complained (excerpt from dmesg -a): > > > > > > > > Starting powerd. > > > > powerd: no cpufreq(4) support -- aborting: No such file or directory > > > > /etc/rc: WARNING: failed to start powerd > > > > > > > > Putting those two settings in loader.conf and rebooting fixed the > > > > problem and powerd started working again apparently because cpufreq(4) > > > > device was available again. > > > > > > Ok, if anabling acpi_throttle and/or p4tcc made cpufreq - and thus > > > powerd - work for you, then it seems likely that you do not have EST > > > enabled in your BIOS. Or at least, we've seen another instance where > > > that was the case, which was fixed by enabling EST (or however your > > > particular BIOS refers to it .. AMD for example use different terms). > > > > > > What CPU is this? In what machine? > > > > > > If EST (ono) IS enabled in your BIOS, this needs further investigation. > > > > > > As is, powerd may be running, but it's doing so highly inefficiently; > > > refer to Stefan, Adrian and Kevin's responses for details. > > > It's an Intel Atom running amd64 version of FreeBSD stable/10: > > > > FreeBSD firewall.rdnzl.info 10.1-STABLE FreeBSD 10.1-STABLE #1 > > r283292: Sat May 23 01:08:03 EEST 2015 > > root@firewall.rdnzl.info:/usr/obj/usr/src/sys/GENERIC amd64 > > > > CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.68-MHz K8-class CPU) > > Origin="GenuineIntel" Id=0x106ca Family=0x6 Model=0x1c Stepping=10 > > Features=0xbfebfbff > > Features2=0x40e31d > > AMD Features=0x20100800 > > AMD Features2=0x1 > > TSC: P-state invariant, performance statistics > > > > Powerd was working on 10.1-RELEASE but stopped working after upgrade > > to 10-STABLE and nothing was changed in BIOS settings. > > Which would be consistent with EST not being enabled in your BIOS; with > no EST, cpufreq(4) still checks for 'relative' drivers such as p4tcc or > acpi_throttle and uses that, as a last resort really; with those also > disabled, no cpufreq, so no powerd. Have you checked BIOS settings to > confirm that you do have SpeedStep (however termed) properly enabled? > > Please show `sysctl dev.cpu dev.est` and `sysctl -a | grep freq_levels` > > > However, reading the other replies to this thread I get the impression > > that powerd(8) doesn't actually save energy on this platform and I'm > > better off without it? > > No, I don't think that's correct; using deeper C-states is most likely a > bigger win, but higher than needed CPU freq will still use extra power, > so run hotter. `sysctl dev.cpu` will also reveal your C-state usage. > > Reason I'm pursuing this is that this change shouldn't hurt, but it will > flush out those cases where people were only getting cpufreq due to use > of a 'relative' cpufreq driver like p4tcc, unless EST's enabled in BIOS; > I suspect yours may be one such case :) If not, there's a bug to fix. > > cheers, Ian Looking deeper into this it appears I don't have speedstep (EST) support in the CPU it being a crappy Atom D510: http://ark.intel.com/products/43098 This the full 'sysctl dev.cpu' output: % sysctl dev.cpu dev.cpu.3.cx_usage: 100.00% last 65712us dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_supported: C1/1/0 dev.cpu.3.%parent: acpi0 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%location: handle=\_PR_.P004 dev.cpu.3.%driver: cpu dev.cpu.3.%desc: ACPI CPU dev.cpu.2.cx_usage: 100.00% last 41518us dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_supported: C1/1/0 dev.cpu.2.%parent: acpi0 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%location: handle=\_PR_.P003 dev.cpu.2.%driver: cpu dev.cpu.2.%desc: ACPI CPU dev.cpu.1.cx_usage: 100.00% last 12706us dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_supported: C1/1/0 dev.cpu.1.%parent: acpi0 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%location: handle=\_PR_.P002 dev.cpu.1.%driver: cpu dev.cpu.1.%desc: ACPI CPU dev.cpu.0.cx_usage: 100.00% last 3132us dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_supported: C1/1/0 dev.cpu.0.%parent: acpi0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%location: handle=\_PR_.P001 dev.cpu.0.%driver: cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.%parent: So I should keep those two hints in loader.conf to use p4tcc I guess? -Kimmo From owner-freebsd-stable@FreeBSD.ORG Sat May 23 15:15:56 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 32FAC30A for ; Sat, 23 May 2015 15:15:56 +0000 (UTC) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05B221A24 for ; Sat, 23 May 2015 15:15:55 +0000 (UTC) Received: by igbhj9 with SMTP id hj9so11669001igb.1 for ; Sat, 23 May 2015 08:15:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=wXMrN7UtZwhmWepQ85XRjXwRbQJAg9sfdKrRthAvlo4=; b=fZzvXbwmpNRXRMmuLZLphGtxRD6YQ7qe+8M9x0hP5PbJhusbRzXnXIjo/Uit3j2TF6 154Ntcb8o9rgnREZvHhb7tIjDamp4vDNCJzmIJ5p1ljD63cfoOFzbYvWl+aIhLO5mBo7 XZvUVPbrWcPSgsCBaa28Y+ZQJsviUjQ1X8D+G6lTkGIwsHW9oe8ChpMQ7u3x+y4Eymfv f4czbm7swfwzUU+evaRa6/PgXvOfhHbbDVNF4M/vhRyj7bifS4+oYRWHNNiCY1Sol9EN cBdSAgg53MZhESbFb48io418Le7Xu+xtwoTz0Qr92A7bcl/eWoOwT6h4KEuxruXz+Ydj lxqg== MIME-Version: 1.0 X-Received: by 10.43.163.129 with SMTP id mo1mr5658753icc.61.1432394155097; Sat, 23 May 2015 08:15:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Sat, 23 May 2015 08:15:55 -0700 (PDT) In-Reply-To: References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> <20150523163014.U7173@sola.nimnet.asn.au> <20150523234646.R7173@sola.nimnet.asn.au> Date: Sat, 23 May 2015 08:15:55 -0700 X-Google-Sender-Auth: Eta0fv8Sng32FwXJzQK06-a_LDo Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Adrian Chadd To: Kimmo Paasiala Cc: Ian Smith , "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 15:15:56 -0000 Hm, no thermal monitoring and no speedstep. Could be dangerous/fun. What's the output of sysctl dev.cpu.0 ? -adrian On 23 May 2015 at 07:40, Kimmo Paasiala wrote: > On Sat, May 23, 2015 at 5:15 PM, Ian Smith wrote: >> On Sat, 23 May 2015 14:01:16 +0300, Kimmo Paasiala wrote: >> > On Sat, May 23, 2015 at 10:00 AM, Ian Smith wrote: >> > > On Fri, 22 May 2015 20:26:40 +0300, Kimmo Paasiala wrote: >> > > > On Fri, May 22, 2015 at 8:19 PM, Ian Smith wrote: >> > > > > On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: >> > > > > > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: >> > > [..] >> > > > >> Try changing the options in /boot/device.hints >> > > > >> hint.acpi_throttle.0.disabled="0" >> > > > >> hint.p4tcc.0.disabled="0" >> > > > > >> > > > > > Thanks, those also fixed powerd(8) for me that stopped working after >> > > > > > upgrading to stable/10 from releng/10.1. Why are those setting >> > > > > > suddenly needed now? >> > > [..] >> > > > > Can you say exactly in what way powerd stopped working then? >> > > > >> > > > Powerd(8) complained (excerpt from dmesg -a): >> > > > >> > > > Starting powerd. >> > > > powerd: no cpufreq(4) support -- aborting: No such file or directory >> > > > /etc/rc: WARNING: failed to start powerd >> > > > >> > > > Putting those two settings in loader.conf and rebooting fixed the >> > > > problem and powerd started working again apparently because cpufreq(4) >> > > > device was available again. >> > > >> > > Ok, if anabling acpi_throttle and/or p4tcc made cpufreq - and thus >> > > powerd - work for you, then it seems likely that you do not have EST >> > > enabled in your BIOS. Or at least, we've seen another instance where >> > > that was the case, which was fixed by enabling EST (or however your >> > > particular BIOS refers to it .. AMD for example use different terms). >> > > >> > > What CPU is this? In what machine? >> > > >> > > If EST (ono) IS enabled in your BIOS, this needs further investigation. >> > > >> > > As is, powerd may be running, but it's doing so highly inefficiently; >> > > refer to Stefan, Adrian and Kevin's responses for details. >> >> > It's an Intel Atom running amd64 version of FreeBSD stable/10: >> > >> > FreeBSD firewall.rdnzl.info 10.1-STABLE FreeBSD 10.1-STABLE #1 >> > r283292: Sat May 23 01:08:03 EEST 2015 >> > root@firewall.rdnzl.info:/usr/obj/usr/src/sys/GENERIC amd64 >> > >> > CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.68-MHz K8-class CPU) >> > Origin="GenuineIntel" Id=0x106ca Family=0x6 Model=0x1c Stepping=10 >> > Features=0xbfebfbff >> > Features2=0x40e31d >> > AMD Features=0x20100800 >> > AMD Features2=0x1 >> > TSC: P-state invariant, performance statistics >> > >> > Powerd was working on 10.1-RELEASE but stopped working after upgrade >> > to 10-STABLE and nothing was changed in BIOS settings. >> >> Which would be consistent with EST not being enabled in your BIOS; with >> no EST, cpufreq(4) still checks for 'relative' drivers such as p4tcc or >> acpi_throttle and uses that, as a last resort really; with those also >> disabled, no cpufreq, so no powerd. Have you checked BIOS settings to >> confirm that you do have SpeedStep (however termed) properly enabled? >> >> Please show `sysctl dev.cpu dev.est` and `sysctl -a | grep freq_levels` >> >> > However, reading the other replies to this thread I get the impression >> > that powerd(8) doesn't actually save energy on this platform and I'm >> > better off without it? >> >> No, I don't think that's correct; using deeper C-states is most likely a >> bigger win, but higher than needed CPU freq will still use extra power, >> so run hotter. `sysctl dev.cpu` will also reveal your C-state usage. >> >> Reason I'm pursuing this is that this change shouldn't hurt, but it will >> flush out those cases where people were only getting cpufreq due to use >> of a 'relative' cpufreq driver like p4tcc, unless EST's enabled in BIOS; >> I suspect yours may be one such case :) If not, there's a bug to fix. >> >> cheers, Ian > > Looking deeper into this it appears I don't have speedstep (EST) > support in the CPU it being a crappy Atom D510: > > http://ark.intel.com/products/43098 > > This the full 'sysctl dev.cpu' output: > > % sysctl dev.cpu > dev.cpu.3.cx_usage: 100.00% last 65712us > dev.cpu.3.cx_lowest: C1 > dev.cpu.3.cx_supported: C1/1/0 > dev.cpu.3.%parent: acpi0 > dev.cpu.3.%pnpinfo: _HID=none _UID=0 > dev.cpu.3.%location: handle=\_PR_.P004 > dev.cpu.3.%driver: cpu > dev.cpu.3.%desc: ACPI CPU > dev.cpu.2.cx_usage: 100.00% last 41518us > dev.cpu.2.cx_lowest: C1 > dev.cpu.2.cx_supported: C1/1/0 > dev.cpu.2.%parent: acpi0 > dev.cpu.2.%pnpinfo: _HID=none _UID=0 > dev.cpu.2.%location: handle=\_PR_.P003 > dev.cpu.2.%driver: cpu > dev.cpu.2.%desc: ACPI CPU > dev.cpu.1.cx_usage: 100.00% last 12706us > dev.cpu.1.cx_lowest: C1 > dev.cpu.1.cx_supported: C1/1/0 > dev.cpu.1.%parent: acpi0 > dev.cpu.1.%pnpinfo: _HID=none _UID=0 > dev.cpu.1.%location: handle=\_PR_.P002 > dev.cpu.1.%driver: cpu > dev.cpu.1.%desc: ACPI CPU > dev.cpu.0.cx_usage: 100.00% last 3132us > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_supported: C1/1/0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%location: handle=\_PR_.P001 > dev.cpu.0.%driver: cpu > dev.cpu.0.%desc: ACPI CPU > dev.cpu.%parent: > > So I should keep those two hints in loader.conf to use p4tcc I guess? > > -Kimmo > _______________________________________________ > 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 May 23 15:57:06 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 709D2DA for ; Sat, 23 May 2015 15:57:06 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D62C01EB6 for ; Sat, 23 May 2015 15:57:05 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id t4NFv1ci027070; Sun, 24 May 2015 01:57:02 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 24 May 2015 01:57:01 +1000 (EST) From: Ian Smith To: Kimmo Paasiala cc: "freebsd-stable@freebsd.org" Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) In-Reply-To: Message-ID: <20150524010831.W7173@sola.nimnet.asn.au> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> <20150523163014.U7173@sola.nimnet.asn.au> <20150523234646.R7173@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 15:57:06 -0000 On Sat, 23 May 2015 17:40:26 +0300, Kimmo Paasiala wrote: > On Sat, May 23, 2015 at 5:15 PM, Ian Smith wrote: [..] > > > It's an Intel Atom running amd64 version of FreeBSD stable/10: > > > > > > FreeBSD firewall.rdnzl.info 10.1-STABLE FreeBSD 10.1-STABLE #1 > > > r283292: Sat May 23 01:08:03 EEST 2015 > > > root@firewall.rdnzl.info:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.68-MHz K8-class CPU) > > > Origin="GenuineIntel" Id=0x106ca Family=0x6 Model=0x1c Stepping=10 > > > Features=0xbfebfbff > > > Features2=0x40e31d > > > AMD Features=0x20100800 > > > AMD Features2=0x1 > > > TSC: P-state invariant, performance statistics > > > > > > Powerd was working on 10.1-RELEASE but stopped working after upgrade > > > to 10-STABLE and nothing was changed in BIOS settings. [..] > > > However, reading the other replies to this thread I get the impression > > > that powerd(8) doesn't actually save energy on this platform and I'm > > > better off without it? > > > > No, I don't think that's correct; using deeper C-states is most likely a > > bigger win, but higher than needed CPU freq will still use extra power, > > so run hotter. `sysctl dev.cpu` will also reveal your C-state usage. > > > > Reason I'm pursuing this is that this change shouldn't hurt, but it will > > flush out those cases where people were only getting cpufreq due to use > > of a 'relative' cpufreq driver like p4tcc, unless EST's enabled in BIOS; > > I suspect yours may be one such case :) If not, there's a bug to fix. Seems _I've_ got a bug to fix; I need to stop assuming all modern Intel CPUs are going to make SpeedStep and/or deeper C-states available :( > Looking deeper into this it appears I don't have speedstep (EST) > support in the CPU it being a crappy Atom D510: > > http://ark.intel.com/products/43098 Indeed. It is rated at only 13W TDP, so relatively low power anyway. > This the full 'sysctl dev.cpu' output: > > % sysctl dev.cpu > dev.cpu.3.cx_usage: 100.00% last 65712us > dev.cpu.3.cx_lowest: C1 > dev.cpu.3.cx_supported: C1/1/0 [..] > dev.cpu.0.cx_usage: 100.00% last 3132us > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_supported: C1/1/0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%location: handle=\_PR_.P001 > dev.cpu.0.%driver: cpu > dev.cpu.0.%desc: ACPI CPU > dev.cpu.%parent: It doesn't even provide dev.cpu.0.freq, and has no deeper C-states ('Idle States' on that page) available, so it looks like you may as well not bother running powerd. Others maybe can offer better suggestions. > So I should keep those two hints in loader.conf to use p4tcc I guess? If this is a desktop I'd just let it run flat out, ie disable p4tcc and acpi_throttle, have no cpufreq and forget powerd. If it's a laptop and power consumption on battery matters to you, you could see if p4tcc's lower frequencies actually save any power much, by running 'powerd -v' in a terminal while testing with different loads, or if your 'acpiconf -i0' shows discharging rates in mA or mW, or both. Sorry again for my poor assumption, and thanks for the data point! cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Sat May 23 17:08:18 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C97EFAC9 for ; Sat, 23 May 2015 17:08:18 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C76D1654 for ; Sat, 23 May 2015 17:08:18 +0000 (UTC) Received: by labbd9 with SMTP id bd9so29753714lab.2 for ; Sat, 23 May 2015 10:08:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sM6ktgAbvWFU0lK3oRo3or56md2+fqkgrd6lje661y4=; b=Nxo2nSWJPz9Vw10zTwy9vi7xLisqSsPgWmUGnJlYz4bHlWKA8AtuVCc/UeZh4VTxBI 6bUxbeTQajP+5y1azuNpAE/4E4OQ5tziMzGbq2NXNy+aYShsjSJeJyTB1amz+/zJkGF4 IvjWn7bN+KQQFGRmHTziXXkjmqcZEqWRCcbXOMZIqZ5cBH69HVVdP9+6i5jCkMM2qC3+ z/VrA68xShSXMyHL9OtGSxP68MhVUvwUtgw/L2l2b4xHtjhAXGuy2eNjelPInjnW5qLD H+jqMN3hggIIiHu/yZ1Nf84Mpe3+El+1iUM/+mh7jpItHBuCxiCspzJmA1Ow8IONnMb6 0BRw== MIME-Version: 1.0 X-Received: by 10.152.203.162 with SMTP id kr2mr11198285lac.68.1432400895967; Sat, 23 May 2015 10:08:15 -0700 (PDT) Received: by 10.152.137.193 with HTTP; Sat, 23 May 2015 10:08:15 -0700 (PDT) In-Reply-To: <20150524010831.W7173@sola.nimnet.asn.au> References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> <20150523163014.U7173@sola.nimnet.asn.au> <20150523234646.R7173@sola.nimnet.asn.au> <20150524010831.W7173@sola.nimnet.asn.au> Date: Sat, 23 May 2015 20:08:15 +0300 Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Kimmo Paasiala To: Ian Smith Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 17:08:18 -0000 On Sat, May 23, 2015 at 6:57 PM, Ian Smith wrote: > On Sat, 23 May 2015 17:40:26 +0300, Kimmo Paasiala wrote: > > On Sat, May 23, 2015 at 5:15 PM, Ian Smith wrote: > [..] > > > > It's an Intel Atom running amd64 version of FreeBSD stable/10: > > > > > > > > FreeBSD firewall.rdnzl.info 10.1-STABLE FreeBSD 10.1-STABLE #1 > > > > r283292: Sat May 23 01:08:03 EEST 2015 > > > > root@firewall.rdnzl.info:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > > > CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.68-MHz K8-class CPU) > > > > Origin="GenuineIntel" Id=0x106ca Family=0x6 Model=0x1c Stepping=10 > > > > Features=0xbfebfbff > > > > Features2=0x40e31d > > > > AMD Features=0x20100800 > > > > AMD Features2=0x1 > > > > TSC: P-state invariant, performance statistics > > > > > > > > Powerd was working on 10.1-RELEASE but stopped working after upgrade > > > > to 10-STABLE and nothing was changed in BIOS settings. > [..] > > > > However, reading the other replies to this thread I get the impression > > > > that powerd(8) doesn't actually save energy on this platform and I'm > > > > better off without it? > > > > > > No, I don't think that's correct; using deeper C-states is most likely a > > > bigger win, but higher than needed CPU freq will still use extra power, > > > so run hotter. `sysctl dev.cpu` will also reveal your C-state usage. > > > > > > Reason I'm pursuing this is that this change shouldn't hurt, but it will > > > flush out those cases where people were only getting cpufreq due to use > > > of a 'relative' cpufreq driver like p4tcc, unless EST's enabled in BIOS; > > > I suspect yours may be one such case :) If not, there's a bug to fix. > > Seems _I've_ got a bug to fix; I need to stop assuming all modern Intel > CPUs are going to make SpeedStep and/or deeper C-states available :( > > > Looking deeper into this it appears I don't have speedstep (EST) > > support in the CPU it being a crappy Atom D510: > > > > http://ark.intel.com/products/43098 > > Indeed. It is rated at only 13W TDP, so relatively low power anyway. > > > This the full 'sysctl dev.cpu' output: > > > > % sysctl dev.cpu > > > dev.cpu.3.cx_usage: 100.00% last 65712us > > dev.cpu.3.cx_lowest: C1 > > dev.cpu.3.cx_supported: C1/1/0 > [..] > > dev.cpu.0.cx_usage: 100.00% last 3132us > > dev.cpu.0.cx_lowest: C1 > > dev.cpu.0.cx_supported: C1/1/0 > > dev.cpu.0.%parent: acpi0 > > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > > dev.cpu.0.%location: handle=\_PR_.P001 > > dev.cpu.0.%driver: cpu > > dev.cpu.0.%desc: ACPI CPU > > dev.cpu.%parent: > > It doesn't even provide dev.cpu.0.freq, and has no deeper C-states > ('Idle States' on that page) available, so it looks like you may as well > not bother running powerd. Others maybe can offer better suggestions. > > > So I should keep those two hints in loader.conf to use p4tcc I guess? > > If this is a desktop I'd just let it run flat out, ie disable p4tcc and > acpi_throttle, have no cpufreq and forget powerd. > > If it's a laptop and power consumption on battery matters to you, you > could see if p4tcc's lower frequencies actually save any power much, by > running 'powerd -v' in a terminal while testing with different loads, or > if your 'acpiconf -i0' shows discharging rates in mA or mW, or both. > > Sorry again for my poor assumption, and thanks for the data point! > > cheers, Ian It's a firewall/router with some minimal services like nginx running. I'll just leave it like it's now without any frequency control. Thanks, -Kimmo From owner-freebsd-stable@FreeBSD.ORG Sat May 23 19:24:00 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65055EE6; Sat, 23 May 2015 19:24:00 +0000 (UTC) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1B0B139E; Sat, 23 May 2015 19:23:59 +0000 (UTC) Received: by wicmx19 with SMTP id mx19so16516866wic.0; Sat, 23 May 2015 12:23:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=cAWN18orTAh33CPffJehDjpRVDARtpGTw11vQyxWrm4=; b=JXBjW5oDBB063k+nzC2GKyCou+Vt6aEcC1DRI1FDH18ScJw7ea0FRylvgENlDOM1km b9pTff/qKS7VEiEXThaYWXJfte19zTrYv6bUSO2DzFKnZQ7knpTSl4ij82s9vHcIIl2x R5V7rDvJIe6JGd4za+pNWoMbluqvNKisM2KC7Ry48eiy3vcrto/mzSzPD/MSGl+XQJ8A FAWVVbsUzcBdcG8ixsy2ngD0SeyM68HiszEAc5i59x7LP8loVLlWofHbEaBrW3+DNgb+ 4iWAUO6l/rtQJ1KbLrRjrttrdtHwlt9wyZkPBxVvzrtv+kTR4H9wMn71JlLfhL2hhUWk lWOw== MIME-Version: 1.0 X-Received: by 10.194.60.43 with SMTP id e11mr26503166wjr.36.1432409037121; Sat, 23 May 2015 12:23:57 -0700 (PDT) Received: by 10.28.30.22 with HTTP; Sat, 23 May 2015 12:23:57 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 May 2015 22:23:57 +0300 Message-ID: Subject: Re: L2ARC degraded. Checksum errors, I/O errors From: George Kontostanos To: "freebsd-fs@freebsd.org" , freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 19:24:00 -0000 Once again, do we know if this https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198242 has been committed yet? -- George Kontostanos --- From owner-freebsd-stable@FreeBSD.ORG Sat May 23 19:41:14 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A547136F for ; Sat, 23 May 2015 19:41:14 +0000 (UTC) Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69C2E1539 for ; Sat, 23 May 2015 19:41:14 +0000 (UTC) Received: by igbsb11 with SMTP id sb11so12102929igb.0 for ; Sat, 23 May 2015 12:41:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/77o3QNRHp++WkpIYbOjIpEn3z+VQawEp/58zQJwelU=; b=ziWA7iB11NxypbyiMhxZyqSkeL2nLYGUQ9X0VUQZmEvgusMvgW7B/FpWDXnrWZ7ksz oCn9+MR6JurHvCWASFv86PWTYb/cRbTV2lRQMjm32yC4BygDIoP/TngZWPYVu2Lq6+5C CQprymkAJ67H3A2TQoAgys8h6eIbZRFcJ9ThCYWGO+w9LDY1/7vM/vpsr1OCULQqc0FX t5Uzi2AAPJs+q6Vl8xRB3p+1L4Vbr9s5hXPWRhYLDHdfe8h208LxTWlnOw5sT1xxkRlF FXcdNJKmNu+79CbQ5iHP5qQ7r/443u8uWy/7h3Y1wo+QtNmz0nQjbLQbSGYSqhTEElmF tpFQ== MIME-Version: 1.0 X-Received: by 10.50.79.232 with SMTP id m8mr13613830igx.6.1432410072331; Sat, 23 May 2015 12:41:12 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Sat, 23 May 2015 12:41:12 -0700 (PDT) In-Reply-To: References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> <20150523163014.U7173@sola.nimnet.asn.au> <20150523234646.R7173@sola.nimnet.asn.au> <20150524010831.W7173@sola.nimnet.asn.au> Date: Sat, 23 May 2015 12:41:12 -0700 X-Google-Sender-Auth: vDJtgVwrDNbkAVVfa4KFNXgHrgs Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Adrian Chadd To: Kimmo Paasiala Cc: Ian Smith , "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 19:41:14 -0000 Frequency control may not be relevant on that platform. Try installing the intel-pcm package; then # kldload cpuctl # pcm.x 1 Then paste some of that in here. Let's see if the CPU is idling some other way. -adrian From owner-freebsd-stable@FreeBSD.ORG Sat May 23 20:24:41 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6BC1BB26 for ; Sat, 23 May 2015 20:24:41 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 356C919F7 for ; Sat, 23 May 2015 20:24:41 +0000 (UTC) Received: by igbpi8 with SMTP id pi8so14541467igb.0 for ; Sat, 23 May 2015 13:24:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neosmart.net; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=l4rZcTcHpkU9PIPCs+LbvNrndio73HAqdvyWc2LpXcE=; b=KF5vlQ/MlmwLRbaoPP8WDTwgycoXl8mcGjRcfUm+feSC4T1xP5VHExZ8yF34Awwdm9 A1tLPhJEG20SBPWUgB3Y5g3iYqEBLGlmfCz7aA8THqQLxsU2wNRCSKaH0eT+mz62JGjT 62oBvzgvpnj6TkcEiAIO2KucB2zYdUvnIssS4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=l4rZcTcHpkU9PIPCs+LbvNrndio73HAqdvyWc2LpXcE=; b=PTvdKJn9WCjrON4y9YRXIgoCciuGaaBl2W2HCCNdlDYsabs3D9k0yCaJjFQlPzP53L eGJzECi2TI6v0kIIW18Mm+Yx7JuqGvp2hcsKa6YwDkr173wJCWK4Xa4e2Xv9V6CmuT3y kpat6tY+Ad2FkiTSimD60E1YtG8UkP1CRTS609Pl+8iphPAEeESbG4bF3pq8ZVGtDG9Z jqg0Q7fVYeXDraJt6APAHDD/Pdayg2I1dNNIB6gtvL5ATsouVxHQcMbUB+1Qe2ehrwi0 lQj7d4Pc+eeN2VJ/VysiPJNeAS/yIW28GqR2PowUNC3dTx2CUQG8YVgdhnDY56DTWbtX c8UA== X-Gm-Message-State: ALoCoQmm09VERkAE8j+V0ehQQVbg+xRCRk103ftecqYQTzGzCwwJPe0VrTM2eBQGK87K0YDSNpij X-Received: by 10.50.90.179 with SMTP id bx19mr13758742igb.43.1432412680503; Sat, 23 May 2015 13:24:40 -0700 (PDT) Received: from [192.168.2.30] (ERMLON6511W-LP140-03-3096583261.dsl.bell.ca. [184.146.28.93]) by mx.google.com with ESMTPSA id o9sm4899651ioe.35.2015.05.23.13.24.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 23 May 2015 13:24:40 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2100\)) Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? From: Mahmoud Al-Qudsi In-Reply-To: <1950364073.41930419.1432210777686.JavaMail.root@uoguelph.ca> Date: Sat, 23 May 2015 16:24:38 -0400 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <1950364073.41930419.1432210777686.JavaMail.root@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.2100) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 20:24:41 -0000 > On May 21, 2015, at 8:19 AM, Rick Macklem wrote: > > Well, if you are just doing an NFSv4.1 mount, you could capture > packets during the failed mount attaempt with tcpdump and then > email me the raw packet capture, I can take a look at it. > (tcpdump doesn't handle nfs packets well, but wireshark will accept > a raw packet capture) Something like: > # tcpdump -s 0 -w .pcap host > should work. > > When I read RFC-5661 around page #567, it seems clear that the > client should use RECLAIM_COMPLETE with the fs arg false after > acquiring a noew clientid, which is what a fresh mount would normally be. > (If the packet capture shows an EXCHANGEID followed by a RECLAIM_COMPLETE > with the fs arg true, I think ESXi is broken, but I can send you a patch > that will just ignore the "true", so it works.) > I think the "true" case is only used when a file system has been "moved" > by a server cluster, indicated to the client via a NFS4ERR_MOVED error > when it is accessed at the old server, but the working in RFC-5661 isn't > very clear. > > rick Thank you kindly. I am travelling at the moment; but as soon as I can, I will get that to you. Much appreciated, Mahmoud From owner-freebsd-stable@FreeBSD.ORG Sat May 23 21:10:34 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D5DA3E5; Sat, 23 May 2015 21:10:34 +0000 (UTC) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EAAF1E5B; Sat, 23 May 2015 21:10:34 +0000 (UTC) Received: by lami4 with SMTP id i4so31383570lam.0; Sat, 23 May 2015 14:10:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=La4H8iuTENAoCf1T07Sub2aJmGgRyFXmHqCsQf4wVro=; b=XRL+eRltv82NjC1FBF7LN+ZzukQUJE6/jUxRB1lzg5hkcBDme7bfOt0HYyRZD9qA2h fXNRMJziBHKe47u4nsaFTR5W7Ff73VQADvsUfxZX0t9a/ziyfXRSUMguYjr1g+s0PxOL tfFnVSD7DbAnMX9KK7e6mfP+Ivw/H4DjKzTvcZnyt/khy6J42bmvxNbKs/07rB2U4Gep G5xVWAg917uw9lxRtYIm0UbevABDdQo1QJkszk050J5J0DTjCWxx6bqZoQdfCyz7ZaB9 woMLOnkH8IbSdTnMT445T8KRA1QyqsMidscvxOJp5sd7QFTNfPXuywtYcfY72izDtEIo fLDg== MIME-Version: 1.0 X-Received: by 10.152.27.105 with SMTP id s9mr11860439lag.86.1432415432087; Sat, 23 May 2015 14:10:32 -0700 (PDT) Received: by 10.152.137.193 with HTTP; Sat, 23 May 2015 14:10:32 -0700 (PDT) In-Reply-To: References: <555C71C8.4080007@gmx.com> <555EDBBB.4090107@gmx.com> <20150522104213.4e083225@nonamehost.local> <20150523014640.K7173@sola.nimnet.asn.au> <20150523163014.U7173@sola.nimnet.asn.au> <20150523234646.R7173@sola.nimnet.asn.au> <20150524010831.W7173@sola.nimnet.asn.au> Date: Sun, 24 May 2015 00:10:32 +0300 Message-ID: Subject: Re: CPU frequency doesn't drop below 1200MHz (like it used to) From: Kimmo Paasiala To: Adrian Chadd Cc: Ian Smith , "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 21:10:34 -0000 On Sat, May 23, 2015 at 10:41 PM, Adrian Chadd wrote: > Frequency control may not be relevant on that platform. > > Try installing the intel-pcm package; then > > # kldload cpuctl > # pcm.x 1 > > Then paste some of that in here. Let's see if the CPU is idling some other way. > > > > -adrian Five iterations one every second: Script started on Sun May 24 00:07:18 2015 command: sudo pcm.x 1 -i=5 Intel(r) Performance Counter Monitor V2.8 (2014-12-18 12:52:39 +0100 ID=ba39a89) Copyright (c) 2009-2014 Intel Corporation Number of physical cores: 1 Number of logical cores: 4 Number of online logical cores: 4 Threads (logical cores) per physical core: 4 Num sockets: 1 Physical cores per socket: 1 Core PMU (perfmon) version: 3 Number of core PMU generic (programmable) counters: 2 Width of generic (programmable) counters: 40 bits Number of core PMU fixed counters: 3 Width of fixed counters: 40 bits Nominal core frequency: 1660000000 Hz Delay: 1 Detected Intel(R) Atom(TM) CPU D510 @ 1.66GHz "Intel(r) microarchitecture codename Atom(tm)" EXEC : instructions per nominal CPU cycle IPC : instructions per CPU cycle FREQ : relation to nominal CPU frequency='unhalted clock ticks'/'invariant timer ticks' (includes Intel Turbo Boost) L2MISS: L2 cache misses L2HIT : L2 cache hit ratio (0.00-1.00) TEMP : Temperature reading in 1 degree Celsius relative to the TjMax temperature (thermal headroom): 0 corresponds to the max temperature Core (SKT) | EXEC | IPC | FREQ | L2MISS | L2HIT | TEMP 0 0 0.00 0.19 0.00 5513 0.85 89 1 0 0.00 0.37 0.00 2676 0.84 89 2 0 0.00 0.39 0.01 21 K 0.83 N/A 3 0 0.00 0.28 0.00 4731 0.64 N/A ----------------------------------------------------------------------------------------------------------------------------- TOTAL * 0.00 0.33 0.00 34 K 0.82 N/A Instructions retired: 6666 K ; Active cycles: 20 M ; Time (TSC): 1765 Mticks ; C0 (active,non-halted) core residency: 0.28 % C1 core residency: 99.72 %; C2 package residency: 0.00 %; C4 package residency: 0.00 %; C6 package residency: 0.00 %; PHYSICAL CORE IPC : 1.33 => corresponds to 66.42 % utilization for cores in active state Instructions per nominal CPU cycle: 0.00 => corresponds to 0.19 % core utilization over time interval ---------------------------------------------------------------------------------------------- EXEC : instructions per nominal CPU cycle IPC : instructions per CPU cycle FREQ : relation to nominal CPU frequency='unhalted clock ticks'/'invariant timer ticks' (includes Intel Turbo Boost) L2MISS: L2 cache misses L2HIT : L2 cache hit ratio (0.00-1.00) TEMP : Temperature reading in 1 degree Celsius relative to the TjMax temperature (thermal headroom): 0 corresponds to the max temperature Core (SKT) | EXEC | IPC | FREQ | L2MISS | L2HIT | TEMP 0 0 0.00 0.19 0.00 6296 0.82 89 1 0 0.00 0.35 0.00 12 K 0.81 89 2 0 0.00 0.44 0.00 6378 0.84 N/A 3 0 0.00 0.24 0.00 3846 0.86 N/A ----------------------------------------------------------------------------------------------------------------------------- TOTAL * 0.00 0.34 0.00 29 K 0.83 N/A Instructions retired: 6646 K ; Active cycles: 19 M ; Time (TSC): 1766 Mticks ; C0 (active,non-halted) core residency: 0.28 % C1 core residency: 99.72 %; C2 package residency: 0.00 %; C4 package residency: 0.00 %; C6 package residency: 0.00 %; PHYSICAL CORE IPC : 1.34 => corresponds to 67.19 % utilization for cores in active state Instructions per nominal CPU cycle: 0.00 => corresponds to 0.19 % core utilization over time interval ---------------------------------------------------------------------------------------------- EXEC : instructions per nominal CPU cycle IPC : instructions per CPU cycle FREQ : relation to nominal CPU frequency='unhalted clock ticks'/'invariant timer ticks' (includes Intel Turbo Boost) L2MISS: L2 cache misses L2HIT : L2 cache hit ratio (0.00-1.00) TEMP : Temperature reading in 1 degree Celsius relative to the TjMax temperature (thermal headroom): 0 corresponds to the max temperature Core (SKT) | EXEC | IPC | FREQ | L2MISS | L2HIT | TEMP 0 0 0.00 0.25 0.00 12 K 0.74 89 1 0 0.00 0.42 0.00 3166 0.94 89 2 0 0.00 0.19 0.00 4869 0.68 94 3 0 0.00 0.36 0.00 13 K 0.81 94 ----------------------------------------------------------------------------------------------------------------------------- TOTAL * 0.00 0.34 0.00 33 K 0.82 N/A Instructions retired: 8041 K ; Active cycles: 23 M ; Time (TSC): 1755 Mticks ; C0 (active,non-halted) core residency: 0.34 % C1 core residency: 99.66 %; C2 package residency: 0.00 %; C4 package residency: 0.00 %; C6 package residency: 0.00 %; PHYSICAL CORE IPC : 1.36 => corresponds to 67.89 % utilization for cores in active state Instructions per nominal CPU cycle: 0.00 => corresponds to 0.23 % core utilization over time interval ---------------------------------------------------------------------------------------------- EXEC : instructions per nominal CPU cycle IPC : instructions per CPU cycle FREQ : relation to nominal CPU frequency='unhalted clock ticks'/'invariant timer ticks' (includes Intel Turbo Boost) L2MISS: L2 cache misses L2HIT : L2 cache hit ratio (0.00-1.00) TEMP : Temperature reading in 1 degree Celsius relative to the TjMax temperature (thermal headroom): 0 corresponds to the max temperature Core (SKT) | EXEC | IPC | FREQ | L2MISS | L2HIT | TEMP 0 0 0.00 0.20 0.00 4436 0.85 89 1 0 0.00 0.30 0.00 3244 0.77 89 2 0 0.00 0.41 0.01 4260 0.93 N/A 3 0 0.00 0.35 0.00 11 K 0.83 N/A ----------------------------------------------------------------------------------------------------------------------------- TOTAL * 0.00 0.34 0.00 23 K 0.86 N/A Instructions retired: 7227 K ; Active cycles: 21 M ; Time (TSC): 1765 Mticks ; C0 (active,non-halted) core residency: 0.30 % C1 core residency: 99.70 %; C2 package residency: 0.00 %; C4 package residency: 0.00 %; C6 package residency: 0.00 %; PHYSICAL CORE IPC : 1.37 => corresponds to 68.70 % utilization for cores in active state Instructions per nominal CPU cycle: 0.00 => corresponds to 0.20 % core utilization over time interval ---------------------------------------------------------------------------------------------- EXEC : instructions per nominal CPU cycle IPC : instructions per CPU cycle FREQ : relation to nominal CPU frequency='unhalted clock ticks'/'invariant timer ticks' (includes Intel Turbo Boost) L2MISS: L2 cache misses L2HIT : L2 cache hit ratio (0.00-1.00) TEMP : Temperature reading in 1 degree Celsius relative to the TjMax temperature (thermal headroom): 0 corresponds to the max temperature Core (SKT) | EXEC | IPC | FREQ | L2MISS | L2HIT | TEMP 0 0 0.00 0.20 0.00 5675 0.85 89 1 0 0.00 0.33 0.00 8696 0.80 89 2 0 0.00 0.41 0.01 4598 0.93 N/A 3 0 0.00 0.32 0.00 7239 0.85 N/A ----------------------------------------------------------------------------------------------------------------------------- TOTAL * 0.00 0.33 0.00 26 K 0.86 N/A Instructions retired: 7363 K ; Active cycles: 22 M ; Time (TSC): 1766 Mticks ; C0 (active,non-halted) core residency: 0.31 % C1 core residency: 99.69 %; C2 package residency: 0.00 %; C4 package residency: 0.00 %; C6 package residency: 0.00 %; PHYSICAL CORE IPC : 1.34 => corresponds to 66.84 % utilization for cores in active state Instructions per nominal CPU cycle: 0.00 => corresponds to 0.21 % core utilization over time interval ---------------------------------------------------------------------------------------------- Cleaning up Zeroed PMU registers Freeing up all RMIDs Script done on Sun May 24 00:07:23 2015 Need more or is this enough? -Kimmo