From owner-freebsd-stable@FreeBSD.ORG Sun Dec 12 00:38:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA6C41065672 for ; Sun, 12 Dec 2010 00:38:07 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 6274D8FC0C for ; Sun, 12 Dec 2010 00:38:07 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:2540:154a:ba54:4afb] ([IPv6:2607:f3e0:0:4:2540:154a:ba54:4afb]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oBC0c5Qr012496 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 11 Dec 2010 19:38:05 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D04195F.1080802@sentex.net> Date: Sat, 11 Dec 2010 19:37:51 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Kostik Belousov References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> In-Reply-To: <20101211232253.GR33073@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2010 00:38:07 -0000 On 12/11/2010 6:22 PM, Kostik Belousov wrote: > On Sat, Dec 11, 2010 at 06:08:08PM -0500, Mike Tancsa wrote: >> On 12/11/2010 11:01 AM, Kostik Belousov wrote: >>> >>> I have no access to AESNI hardware. For start, you may use >>> src/tools/tools/crypto/cryptotest >>> to somewhat verify the sanity of the driver. >> >> I doesnt happen every time, but one out of 5 or so >> > First, which arch is it, amd64 or i386 ? > > Also, please revert r216162 and do the same tests. Hi, Its AMD64, but i386 seems to be impacted too. I am not sure how to revert to a specific commit, but for now I csup'd with a date tag of *date=2010.12.02.23.00.00 which is a day before http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-December/004338.html And that seems to fix it! I have been running cryptotest -c -z -t 10 in a loop for the past 10min and not one error. ---Mike From owner-freebsd-stable@FreeBSD.ORG Sun Dec 12 08:43:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 865FB1065674 for ; Sun, 12 Dec 2010 08:43:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 21A088FC16 for ; Sun, 12 Dec 2010 08:43:31 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id oBC8hRh9019082 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 12 Dec 2010 10:43:27 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id oBC8hRs6061620; Sun, 12 Dec 2010 10:43:27 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id oBC8hRoK061619; Sun, 12 Dec 2010 10:43:27 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 12 Dec 2010 10:43:27 +0200 From: Kostik Belousov To: Mike Tancsa Message-ID: <20101212084327.GS33073@deviant.kiev.zoral.com.ua> References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ulKx6OyYBbhdAroi" Content-Disposition: inline In-Reply-To: <4D04195F.1080802@sentex.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2010 08:43:32 -0000 --ulKx6OyYBbhdAroi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 11, 2010 at 07:37:51PM -0500, Mike Tancsa wrote: > On 12/11/2010 6:22 PM, Kostik Belousov wrote: > > On Sat, Dec 11, 2010 at 06:08:08PM -0500, Mike Tancsa wrote: > >> On 12/11/2010 11:01 AM, Kostik Belousov wrote: > >>> > >>> I have no access to AESNI hardware. For start, you may use > >>> src/tools/tools/crypto/cryptotest > >>> to somewhat verify the sanity of the driver. > >> > >> I doesnt happen every time, but one out of 5 or so=20 > >> > > First, which arch is it, amd64 or i386 ? > >=20 > > Also, please revert r216162 and do the same tests. >=20 > Hi, > Its AMD64, but i386 seems to be impacted too. I am not sure how to > revert to a specific commit, but for now I csup'd with a date tag of >=20 > *date=3D2010.12.02.23.00.00 >=20 > which is a day before > http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-December/004338.= html >=20 >=20 > And that seems to fix it! >=20 > I have been running > cryptotest -c -z -t 10 > in a loop for the past 10min and not one error. Please try this patch on the latest HEAD or RELENG_8. diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c index 482b5da..1b493b4 100644 --- a/sys/amd64/amd64/fpu.c +++ b/sys/amd64/amd64/fpu.c @@ -426,7 +426,9 @@ fpudna(void) fxrstor(&fpu_initialstate); if (pcb->pcb_initial_fpucw !=3D __INITIAL_FPUCW__) fldcw(pcb->pcb_initial_fpucw); - fpuuserinited(curthread); + pcb->pcb_flags |=3D PCB_FPUINITDONE; + if (PCB_USER_FPU(pcb)) + pcb->pcb_flags |=3D PCB_USERFPUINITDONE; } else fxrstor(pcb->pcb_save); critical_exit(); diff --git a/sys/i386/isa/npx.c b/sys/i386/isa/npx.c index 9ec5d25..f314e44 100644 --- a/sys/i386/isa/npx.c +++ b/sys/i386/isa/npx.c @@ -684,7 +684,9 @@ npxdna(void) fpurstor(&npx_initialstate); if (pcb->pcb_initial_npxcw !=3D __INITIAL_NPXCW__) fldcw(pcb->pcb_initial_npxcw); - npxuserinited(curthread); + pcb->pcb_flags |=3D PCB_NPXINITDONE; + if (PCB_USER_FPU(pcb)) + pcb->pcb_flags |=3D PCB_NPXUSERINITDONE; } else { /* * The following fpurstor() may cause an IRQ13 when the --ulKx6OyYBbhdAroi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk0Eiy4ACgkQC3+MBN1Mb4gKGgCeLZ2OoaLYKytj4UNXTI78KrWq Xd4AoJafIILy8juGyZ0ZBddwogi9TNLk =qohO -----END PGP SIGNATURE----- --ulKx6OyYBbhdAroi-- From owner-freebsd-stable@FreeBSD.ORG Sun Dec 12 14:27:00 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26818106564A for ; Sun, 12 Dec 2010 14:27:00 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id D231F8FC12 for ; Sun, 12 Dec 2010 14:26:59 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:2540:154a:ba54:4afb] ([IPv6:2607:f3e0:0:4:2540:154a:ba54:4afb]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oBCEQuAc016331 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 12 Dec 2010 09:26:57 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D04DBA1.4070108@sentex.net> Date: Sun, 12 Dec 2010 09:26:41 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Kostik Belousov References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> <20101212084327.GS33073@deviant.kiev.zoral.com.ua> In-Reply-To: <20101212084327.GS33073@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2010 14:27:00 -0000 On 12/12/2010 3:43 AM, Kostik Belousov wrote: > On Sat, Dec 11, 2010 at 07:37:51PM -0500, Mike Tancsa wrote: >> On 12/11/2010 6:22 PM, Kostik Belousov wrote: >> *date=2010.12.02.23.00.00 >> >> which is a day before >> http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-December/004338.html >> >> >> And that seems to fix it! >> >> I have been running >> cryptotest -c -z -t 10 >> in a loop for the past 10min and not one error. > > Please try this patch on the latest HEAD or RELENG_8. > I tried both on i386 and amd64 and all looks good! I did 1000 iterations of cryptotest -c -z -t 10 without issue! Thanks for the quick fix! ---Mike 0(backup3)# patch -p1 < p Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c |index 482b5da..1b493b4 100644 |--- a/sys/amd64/amd64/fpu.c |+++ b/sys/amd64/amd64/fpu.c -------------------------- Patching file sys/amd64/amd64/fpu.c using Plan A... Hunk #1 succeeded at 426. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sys/i386/isa/npx.c b/sys/i386/isa/npx.c |index 9ec5d25..f314e44 100644 |--- a/sys/i386/isa/npx.c |+++ b/sys/i386/isa/npx.c -------------------------- Patching file sys/i386/isa/npx.c using Plan A... Hunk #1 succeeded at 684. done 0(backup3)# From owner-freebsd-stable@FreeBSD.ORG Sun Dec 12 15:08:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC416106566C for ; Sun, 12 Dec 2010 15:08:29 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 72FEB8FC0A for ; Sun, 12 Dec 2010 15:08:28 +0000 (UTC) Received: by wwf26 with SMTP id 26so5057182wwf.31 for ; Sun, 12 Dec 2010 07:08:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=KaAoVazSWGN/o110TP9mwjEzidnJKDgUzet7O3R94/s=; b=fQgwuOH7xvagV3cWkbhl+1A1E820wZ8tmhuuh3jsdEdDcgbikMQGcRnPLNzZ/r3gbW LELnrcB3LnSsb8OzGHp7kajcQh0eWgUWx7f42v7EQ1wRzrVY9RMpF61HBSVlGaav39uD ASRf5INI7WBkXtxotK6BQGoPipwrvvNb24/o0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dwh43p+esW8aUpy5ZrFE71Lb0Mmci4XEUdPg2v3/B5sC90kgvijRRGMWg+5mavH2Mq +7PRhUFOlX4kXOCK5eEzD49E5rc4EruSABFIaySjzpVGYD9HlA4JxCK740/fcXA4+qAJ uDyN9ruAP6imDQUOGApmHPHD2Qu13pyj1Y6FY= MIME-Version: 1.0 Received: by 10.227.155.138 with SMTP id s10mr1021625wbw.61.1292164739599; Sun, 12 Dec 2010 06:38:59 -0800 (PST) Received: by 10.227.23.203 with HTTP; Sun, 12 Dec 2010 06:38:59 -0800 (PST) Date: Sun, 12 Dec 2010 09:38:59 -0500 Message-ID: From: Kim Culhan To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 8.2-BETA1 sysinstall: No USB devices found X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2010 15:08:29 -0000 Intalling from: ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/8.2/FreeBSD-8.2-BETA1-amd64-memstick.img >From sysinstall choose installation media: 9 USB Install from a USB drive Returns: No USB devices found! Several usb slots on the motherboard were tried with the same result. The motherboard is: Intel D945GCLF2 with the latest bios dated 04142010 Please let me know if there is any way I can help. -kim From owner-freebsd-stable@FreeBSD.ORG Sun Dec 12 15:17:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C255106564A for ; Sun, 12 Dec 2010 15:17:32 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id CFA778FC08 for ; Sun, 12 Dec 2010 15:17:31 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id DBDEBE63D4; Sun, 12 Dec 2010 15:17:30 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=date:from :to:cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=mail; bh=cM6KZQaCKWWL uIeycizrbcTkxSI=; b=DY1ZXmfZCeT4pdJiHSBtgfRjja/GEvxQKTMcusVwVIDY RwZPbSyMQAnbD1yV9i2JAil2FSSgkFPjfOm/WuY1zJLPz7PnLZcsZFpKDR/pMMip oRxgt6QD0mQCa9dI/db5lc+jVUNoa3ejDioZvMhXXP+25VBl6f4b2fQ03ncTNss= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=date:from:to :cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=mail; b=o6Wwf6 kxddZqVX1iTWqI/hyav9zH0G98WscFTuf/Nq9NYDs8BjPxWoB+6VAMFFYSc9xnwG fpHgnHpBLrTSCl3nfsEqI1g+ZWMAq4u99d2BeIGRigLZH2DOzDhSm6S07kkroxRv pRf13drjFzW+DcVi9xFqoe5GiEtDruVrXbCTg= Received: from core.draftnet (client-86-27-21-134.glfd.adsl.virginmedia.com [86.27.21.134]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id D7613E63D3; Sun, 12 Dec 2010 15:17:29 +0000 (GMT) Date: Sun, 12 Dec 2010 15:17:04 +0000 From: Bruce Cran To: Kim Culhan Message-ID: <20101212151704.197dddee@core.draftnet> In-Reply-To: References: X-Mailer: Claws Mail 3.7.7 (GTK+ 2.22.1; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 8.2-BETA1 sysinstall: No USB devices found X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2010 15:17:32 -0000 On Sun, 12 Dec 2010 09:38:59 -0500 Kim Culhan wrote: > No USB devices found! Can you try re-scanning for devices (via the Options screen) - sysinstall can fail to detect USB disks the first time around. -- Bruce Cran From owner-freebsd-stable@FreeBSD.ORG Sun Dec 12 15:45:10 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EB57106566B for ; Sun, 12 Dec 2010 15:45:10 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 128DE8FC0C for ; Sun, 12 Dec 2010 15:45:09 +0000 (UTC) Received: by wwf26 with SMTP id 26so5076250wwf.31 for ; Sun, 12 Dec 2010 07:45:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=4Qv+LvaepfI4/IDFIjjXDpsGpnfbhcVARrqpytAMuS0=; b=Y/MhEnvDlLQDwj3QGkGEgieP7UMJa0c+BA9I7FiEVi6JIV7TQf7LRULQ2s+zDUnNlX AYyZKuIhQIp+CjXBoOMz9Y3ajgEZUlnDjYYTY6hncHD4SpktKh0Xv/UfzCXmnbCjgRKY k3FtNCeKfn/uyuD+hk1JITkOOfRv0sxxZ9ueo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ppE+V7VJ5qw/lZrA8UABXXDaoPqdeeWiDUJBBsB0OzQWG6OOT6IFwIlhc/jeoV+5zh pF8843f/mLLo4RiHs871cIwoT24jXkhvmbZ3uiC3q4jiZ2x/KxlRBI2JXFCbtnmp5RjB Yf4vWKnBtAuxIyw71PTDYu3lvAoPvFfhocxl8= MIME-Version: 1.0 Received: by 10.227.195.203 with SMTP id ed11mr1051710wbb.206.1292168708867; Sun, 12 Dec 2010 07:45:08 -0800 (PST) Received: by 10.227.23.203 with HTTP; Sun, 12 Dec 2010 07:45:08 -0800 (PST) In-Reply-To: <20101212151704.197dddee@core.draftnet> References: <20101212151704.197dddee@core.draftnet> Date: Sun, 12 Dec 2010 10:45:08 -0500 Message-ID: From: Kim Culhan To: Bruce Cran Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: 8.2-BETA1 sysinstall: No USB devices found X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2010 15:45:10 -0000 On Sun, Dec 12, 2010 at 10:17 AM, Bruce Cran wrote: > On Sun, 12 Dec 2010 09:38:59 -0500 > Kim Culhan wrote: > > > No USB devices found! > > Can you try re-scanning for devices (via the Options screen) - > sysinstall can fail to detect USB disks the first time around. > Thanks Bruce worked fine. Hitting on Re-scan devices didn't appear to have any effect but hitting a space on Media Type allowed choosing USB. thanks -kim From owner-freebsd-stable@FreeBSD.ORG Sun Dec 12 16:28:36 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26DE1106564A for ; Sun, 12 Dec 2010 16:28:36 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id B10478FC13 for ; Sun, 12 Dec 2010 16:28:35 +0000 (UTC) Received: by wwf26 with SMTP id 26so5100140wwf.31 for ; Sun, 12 Dec 2010 08:28:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=tuXLUKaJdCo4fpX9kTAZQ4LaIHX+xDXls1mF5xWrRNY=; b=ao3e6ETYFiTXPU3MlJwu+XOEpDHNW9TOdbPG10M3Iu+KaY82dHjJzH5PcwfYkpwuHT RgGSnmGeDR3oS2mb2dN5o+lhvAZpv1X4MMsAuc68RQKHYc+WO6bRIlzJvxWUcgJBW/1H J8fyCGmJnS6lROOuvCPx8yMBBYXq+/pYs1KUI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=t1q+47YDzlv3PweSpF3Fi7hMh7OCcnezcEt32O27LbzzAToTvtaS7Ix8wnI9XXJlMf H61/m9IBjb2vsJIapydO3BCeVv/jcQBQHXDgfpEyLOljFFmqoMmP426y4fp3rNdDFLoX 2MN386dUIaYNpuj2nO6Hs46dPB4Bz5uBztQPM= MIME-Version: 1.0 Received: by 10.216.4.82 with SMTP id 60mr1887833wei.89.1292171314527; Sun, 12 Dec 2010 08:28:34 -0800 (PST) Received: by 10.216.12.80 with HTTP; Sun, 12 Dec 2010 08:28:34 -0800 (PST) In-Reply-To: <20101212151704.197dddee@core.draftnet> References: <20101212151704.197dddee@core.draftnet> Date: Sun, 12 Dec 2010 10:28:34 -0600 Message-ID: From: Brandon Gooch To: Bruce Cran Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Kim Culhan Subject: Re: 8.2-BETA1 sysinstall: No USB devices found X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2010 16:28:36 -0000 On Sun, Dec 12, 2010 at 9:17 AM, Bruce Cran wrote: > On Sun, 12 Dec 2010 09:38:59 -0500 > Kim Culhan wrote: > >> No USB devices found! > > Can you try re-scanning for devices (via the Options screen) - > sysinstall can fail to detect USB disks the first time around. > > -- > Bruce Cran How difficult would it be for the installer to automatically re-scan for devices when USB is selected as install or Fix-it media? -Brandon From owner-freebsd-stable@FreeBSD.ORG Sun Dec 12 17:34:58 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81D541065672 for ; Sun, 12 Dec 2010 17:34:58 +0000 (UTC) (envelope-from mvoorhis@cs.wpi.edu) Received: from MAIL1.WPI.EDU (MAIL1.WPI.EDU [130.215.36.91]) by mx1.freebsd.org (Postfix) with ESMTP id 3504C8FC08 for ; Sun, 12 Dec 2010 17:34:57 +0000 (UTC) Received: from SMTP.WPI.EDU (SMTP.WPI.EDU [130.215.36.186]) by MAIL1.WPI.EDU (8.14.5.Beta0/8.14.5.Beta0) with ESMTP id oBCH8k9g019578 for ; Sun, 12 Dec 2010 12:08:46 -0500 Received: from APPLIANCE4.WPI.EDU (appliance4.wpi.edu [130.215.36.61]) by SMTP.WPI.EDU (8.14.4/8.14.4) with ESMTP id oBCH8jD6002115 for ; Sun, 12 Dec 2010 12:08:46 -0500 (envelope-from mvoorhis@cs.wpi.edu) Received: from [192.168.2.2] (24-241-20-47.dhcp.oxfr.ma.charter.com [24.241.20.47]) (authenticated authen=mvoorhis) by APPLIANCE4.WPI.EDU (8.14.5.Beta0/8.14.5.Beta0) with ESMTP id oBCH8i1Q027324 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sun, 12 Dec 2010 12:08:45 -0500 Message-ID: <4D050197.8010600@cs.wpi.edu> Date: Sun, 12 Dec 2010 12:08:39 -0500 From: Michael Voorhis User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20101212151704.197dddee@core.draftnet> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 8.2-BETA1 sysinstall: No USB devices found X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2010 17:34:58 -0000 On 12/12/2010 11:28 AM, Brandon Gooch wrote: > How difficult would it be for the installer to automatically re-scan > for devices when USB is selected as install or Fix-it media? Ditto this. I do all my OS installs via a USB CD reader and it took me a little while to come up with the rescan-fix. I don't order rack servers with optical disk readers that I'll only be using once to install the OS, so all the stuff I build is installed from USB disc readers. My initial response was "how can we not know there's a CD reader when I just booted and read the installer from it." One of the 1st things sysinstall does is run a device scan deviceGetAll(), but that misses the USB device, apparently. The deviceRescan() calls the same function, but preceeds it with deviceReset(). All this stuff is in src/usr.sbin/sysinstall/devices.c. I'm not smart enough to make my own install disks right now; what would happen if the reset were inserted in front of the rescan (in main.c) at the beginning of sysinstall execution? That seems to be the only difference between the initial scan and the "option" scan. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 02:53:55 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFAC6106566B for ; Mon, 13 Dec 2010 02:53:55 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 492CB8FC08 for ; Mon, 13 Dec 2010 02:53:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id oBD2rfa8053569; Mon, 13 Dec 2010 13:53:41 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 13 Dec 2010 13:53:41 +1100 (EST) From: Ian Smith To: Michael Voorhis In-Reply-To: <4D050197.8010600@cs.wpi.edu> Message-ID: <20101213131456.Y83735@sola.nimnet.asn.au> References: <20101212151704.197dddee@core.draftnet> <4D050197.8010600@cs.wpi.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: 8.2-BETA1 sysinstall: No USB devices found X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 02:53:56 -0000 On Sun, 12 Dec 2010, Michael Voorhis wrote: > On 12/12/2010 11:28 AM, Brandon Gooch wrote: > > How difficult would it be for the installer to automatically re-scan > > for devices when USB is selected as install or Fix-it media? > > Ditto this. I do all my OS installs via a USB CD reader and it took me a > little while to come up with the rescan-fix. This one goes back a while; I got involved in a discusion in questions@ where Randi provided a fair bit of info on some of the issues here: Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found! http://lists.freebsd.org/pipermail/freebsd-questions/2009-December/208977.html > I don't order rack servers with optical disk readers that I'll only be using > once to install the OS, so all the stuff I build is installed from USB disc > readers. My initial response was "how can we not know there's a CD reader > when I just booted and read the installer from it." Ah, perhaps it's not just older kit and/or some types of USB stick that have this issue then .. > One of the 1st things sysinstall does is run a device scan deviceGetAll(), > but that misses the USB device, apparently. The deviceRescan() calls the > same function, but preceeds it with deviceReset(). > > All this stuff is in src/usr.sbin/sysinstall/devices.c. I'm not smart enough > to make my own install disks right now; what would happen if the reset were > inserted in front of the rescan (in main.c) at the beginning of sysinstall > execution? That seems to be the only difference between the initial scan and > the "option" scan. There may be an issue with doing that too: it seems that reset also resets other things, in my case losing the disk slicing, labelling and choice of distributions that had already been done: Re: Installing 8.1-RELEASE from the memstick http://lists.freebsd.org/pipermail/freebsd-questions/2010-August/219690.html I still don't undersand why memstick images need to be in DD mode (daXa) rather than allowing being properly sliced (daXsY), unless it's just the clash with sliced da devices indicating 'real' SCSI disks in devices.c? I'd love to be able to put amd64 and i386 installers, plus say the packages from the DVD, plus somewhere to save dmesgs, on one stick. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 03:36:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01129106566C for ; Mon, 13 Dec 2010 03:36:08 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 749018FC18 for ; Mon, 13 Dec 2010 03:36:06 +0000 (UTC) Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta05.westchester.pa.mail.comcast.net with comcast id iTVY1f0010xGWP855Tc7lz; Mon, 13 Dec 2010 03:36:07 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta12.westchester.pa.mail.comcast.net with comcast id iTc41f00W3LrwQ23YTc5no; Mon, 13 Dec 2010 03:36:06 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 3F1759B427; Sun, 12 Dec 2010 19:36:03 -0800 (PST) Date: Sun, 12 Dec 2010 19:36:03 -0800 From: Jeremy Chadwick To: Ian Smith Message-ID: <20101213033603.GA91170@icarus.home.lan> References: <20101212151704.197dddee@core.draftnet> <4D050197.8010600@cs.wpi.edu> <20101213131456.Y83735@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101213131456.Y83735@sola.nimnet.asn.au> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Michael Voorhis , freebsd-stable@freebsd.org Subject: Re: 8.2-BETA1 sysinstall: No USB devices found X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 03:36:08 -0000 On Mon, Dec 13, 2010 at 01:53:41PM +1100, Ian Smith wrote: > On Sun, 12 Dec 2010, Michael Voorhis wrote: > > On 12/12/2010 11:28 AM, Brandon Gooch wrote: > > > How difficult would it be for the installer to automatically re-scan > > > for devices when USB is selected as install or Fix-it media? > > > > Ditto this. I do all my OS installs via a USB CD reader and it took me a > > little while to come up with the rescan-fix. > > This one goes back a while; I got involved in a discusion in questions@ > where Randi provided a fair bit of info on some of the issues here: > Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found! > http://lists.freebsd.org/pipermail/freebsd-questions/2009-December/208977.html > > > I don't order rack servers with optical disk readers that I'll only be using > > once to install the OS, so all the stuff I build is installed from USB disc > > readers. My initial response was "how can we not know there's a CD reader > > when I just booted and read the installer from it." > > Ah, perhaps it's not just older kit and/or some types of USB stick that > have this issue then .. > > > One of the 1st things sysinstall does is run a device scan deviceGetAll(), > > but that misses the USB device, apparently. The deviceRescan() calls the > > same function, but preceeds it with deviceReset(). > > > > All this stuff is in src/usr.sbin/sysinstall/devices.c. I'm not smart enough > > to make my own install disks right now; what would happen if the reset were > > inserted in front of the rescan (in main.c) at the beginning of sysinstall > > execution? That seems to be the only difference between the initial scan and > > the "option" scan. > > There may be an issue with doing that too: it seems that reset also > resets other things, in my case losing the disk slicing, labelling and > choice of distributions that had already been done: > Re: Installing 8.1-RELEASE from the memstick > http://lists.freebsd.org/pipermail/freebsd-questions/2010-August/219690.html > > I still don't undersand why memstick images need to be in DD mode (daXa) > rather than allowing being properly sliced (daXsY), unless it's just the > clash with sliced da devices indicating 'real' SCSI disks in devices.c? > > I'd love to be able to put amd64 and i386 installers, plus say the > packages from the DVD, plus somewhere to save dmesgs, on one stick. I've been trying to do this for quite some time -- I dedicated nearly 4 weeks to trying to accomplish something similar ~6 months ago. My idea was to have multiple .iso files on a single USB memstick, which GRUB/MEMLINUX would therefore boot. Things like Kubuntu, FreeBSD 7.x i386 and amd64, 8.x i386 and amd64, DBAN, memtest86+, Western Digital, Seagate, Maxtor, Hitachi, etc. disk analysis/repair tools, and a couple of other ISOs. To clarify: literally I wanted a single FAT32 filesystem with .iso files placed on it, with some GRUB/MEMLINUX boot semantics/config files put in place, to provide a menuing system with information of what ISO file represented what. You'd select the OS/thing you wanted to boot (see below website for a screenshot) and off it went. Why .iso files on FAT32 rather than a dedicated slice for each thing? Because it makes testing a new release or upgrading an ISO very simple; insert USB stick in , delete old file, copy over new one, edit the GRUB configuration bits, sync and/or umount, and pull the USB stick. The tool I was using was this (though it has been updated regularly. Note that the latest version is 2 days old; I was working with a version many months ago): http://www.pendrivelinux.com/boot-multiple-iso-from-usb-multiboot-usb/ The result: I was able to get things like memtest86+ and DBAN to boot, and very specific Linux distributions (with a lot of pain), in addition to FreeBSD. However, FreeBSD would always fail to find the necessary installation packages/sources/etc. due to "how" the whole booting process above works. I had to spend a lot of time messing around with MEMLINUX and the "map --hook rootnoverify (0xff)" parameters and similar whatnots: http://syslinux.zytor.com/wiki/index.php/MEMDISK Another problem I ran into is described on that site under the "Boot Errors" section, blabbing about how the drive has to be defragmented and the files have to be in contiguous order (I assume this means every block of data in the ISO has to be in linear order and cannot be spread across non-linear sectors/blocks of the USB drive). What I'm trying to say is that basically accomplishing things how I described above is impossible given the limitations of the PC BIOS (I have to assume INT 0x13), and that's really too bad given the need for such a thing in this day and age. What did I end up doing? Buying multiple HP-brand 4GB USB memory sticks and dedicating each of them to whatever tool was needed. When visiting the datacenter I haul with me a large tote of tools, cables, and of course said sticks. HTH. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 05:17:44 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A02D106564A for ; Mon, 13 Dec 2010 05:17:44 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 51FCB8FC08 for ; Mon, 13 Dec 2010 05:17:42 +0000 (UTC) Received: from ur.gsoft.com.au (Ur.gsoft.com.au [203.31.81.44]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id oBD5HIJl058423 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Dec 2010 15:47:24 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: multipart/signed; boundary=Apple-Mail-146-377626062; protocol="application/pkcs7-signature"; micalg=sha1 From: "Daniel O'Connor" In-Reply-To: <20101213033603.GA91170@icarus.home.lan> Date: Mon, 13 Dec 2010 15:47:18 +1030 Message-Id: References: <20101212151704.197dddee@core.draftnet> <4D050197.8010600@cs.wpi.edu> <20101213131456.Y83735@sola.nimnet.asn.au> <20101213033603.GA91170@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1082) X-Spam-Score: -2.51 () ALL_TRUSTED,BAYES_00,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Michael Voorhis , freebsd-stable@freebsd.org, Ian Smith Subject: Re: 8.2-BETA1 sysinstall: No USB devices found X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 05:17:44 -0000 --Apple-Mail-146-377626062 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 13/12/2010, at 14:06, Jeremy Chadwick wrote: > The result: I was able to get things like memtest86+ and DBAN to boot, > and very specific Linux distributions (with a lot of pain), in = addition > to FreeBSD. However, FreeBSD would always fail to find the necessary > installation packages/sources/etc. due to "how" the whole booting > process above works. I had to spend a lot of time messing around with > MEMLINUX and the "map --hook rootnoverify (0xff)" parameters and = similar > whatnots: For just FreeBSD I have used syslinux to boot an MFS and then have = sysinstall read off the USB stick as a hard disk. I submitted a few patches and they're committed now so you can probably = do it out of the box. The only pain is generating the MFS but that isn't _too_ tricky. It would be nice if it was generated during the normal 'make release' = though (hint hint) Also, I tried a minimal MFS and then loading the kernel directly from = FAT32 using the loader but I could never get it to "see" the FAT32 even = though by my reading of the code it should work.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --Apple-Mail-146-377626062-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 08:49:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0C701065670 for ; Mon, 13 Dec 2010 08:49:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5F0588FC20 for ; Mon, 13 Dec 2010 08:49:56 +0000 (UTC) Received: by wyf19 with SMTP id 19so5705363wyf.13 for ; Mon, 13 Dec 2010 00:49:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=uJufJs63KdrEunsXk3dETOQrFvdn5NZfwiCAd8dobK8=; b=uPtzMUDytqQuTr5Q61wl+0NIS2u9f05JJuDo9rWywqaeF7Z5ohZv+WS5UcO+kzqh/J imXFD2DbdM6Y9bbDvDi/ivagcs58MFNfolApbjNvtBA7mvaQ4pBFdBE/inzqBQvD1t22 IV3AS6DTDl27/wAisCwua+Er1tDInNqViy/x0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=wPeQWwq65fez1KSfezBHzkHiJDUD66ZeTqpjK68zx5iBMtqypKkXjDZNpxgHNPCI8T 8I2AxPhADmpRnKuAqJ6YcLSlW1ZTdb2hUtdMH0hkXROP0hZxw+IMJeOBWRuY5biWznmZ /9gwA24V9e04xji75lbKzwNralPSjsirWO7Bg= MIME-Version: 1.0 Received: by 10.216.178.207 with SMTP id f57mr4279175wem.35.1292230195360; Mon, 13 Dec 2010 00:49:55 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.65.210 with HTTP; Mon, 13 Dec 2010 00:49:54 -0800 (PST) In-Reply-To: References: <4B521FC2.4050402@errno.com> <4B535AAE.3060308@errno.com> <4B5BA0C1.8010901@errno.com> Date: Mon, 13 Dec 2010 16:49:54 +0800 X-Google-Sender-Auth: -1F2dTZY-Hvxn8Xn6zJM3ZrGhtU Message-ID: From: Adrian Chadd To: Russell Yount Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: atheros broadcast/multicast corruption with multiple hostap's X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 08:49:57 -0000 (I'm removing Sam from the CC: ; it seems he's not interested in this stuff any longer.) On 8 December 2010 09:54, Russell Yount wrote: > Adrian, > > Yes, I can help track down this. > > I have only 11agb radios though: > =A0 =A0NL-5354MP + Aries2 > =A0 5004 MP Atheros 4G / CM9 Which chipsets are they? > The changes I made definiately work for these chips, I have 4 APs operati= ng > with 4 SSID each all=A0configured with=A0WPA2 using x509 certs. Currently= , the > kernel I am using is 8.1. Are they using different keys? Did you try WPA + AES/CCMP in STA mode with these? If not, would you please do that? > I seem to recall that the hardware abstration layer for different chipset= s > treated handling of multicast reception differently. > > Could you send me pointers to what problems are described? > > Sorry, I took so long to reply, been rather busy, =A0I do not check this = email > account as often as my others. What would be a better account to email? What I'd really like to do is write up a set of testing procedures for doing things to the ath driver - in station, hostap and adhoc modes - so I can test my local 11n+refactored HAL against it. If you've got a working setup then I'd like to try and get that documented and reproducable, complete with a set of tests for each to try and ensure that as much stuff works as possible. I'd also like to make sure that the AR5416 HAL as shipped in FreeBSD behaves the same way as the AR5210,AR5211,AR5212 HALs as well. I only have an AR5213 card here; the rest of mine are 11n (AR5416, AR9160, AR9280.) I don't know if I'm going to be able to get all of this into 9.0-RELEASE but I'd like to try. The atheros 11n chipsets are everywhere now; I'd like to both support the legacy stuff and the new stuff with all the features fully working. :-) Right now I haven't any idea about what works and what doesn't. Thanks, Adrian From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 11:54:42 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4F741065670 for ; Mon, 13 Dec 2010 11:54:42 +0000 (UTC) (envelope-from me@janh.de) Received: from mailhost.uni-hamburg.de (mailhost.uni-hamburg.de [134.100.32.155]) by mx1.freebsd.org (Postfix) with ESMTP id 591CF8FC14 for ; Mon, 13 Dec 2010 11:54:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mailhost.uni-hamburg.de (Postfix) with ESMTP id BC14A9052A; Mon, 13 Dec 2010 12:54:40 +0100 (CET) X-Virus-Scanned: by University of Hamburg (RRZ/mailhost) Received: from mailhost.uni-hamburg.de ([127.0.0.1]) by localhost (mailhost.uni-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rnDA7GM9zXqw; Mon, 13 Dec 2010 12:54:40 +0100 (CET) Received: from nb895.math (f054009026.adsl.alicedsl.de [78.54.9.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: fmjv004) by mailhost.uni-hamburg.de (Postfix) with ESMTPSA id 4629890095; Mon, 13 Dec 2010 12:54:40 +0100 (CET) Message-ID: <4D0609A9.3020008@janh.de> Date: Mon, 13 Dec 2010 12:55:21 +0100 From: Jan Henrik Sylvester User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101210 Thunderbird/3.1.7 MIME-Version: 1.0 To: Kostik Belousov References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> <20101212084327.GS33073@deviant.kiev.zoral.com.ua> <4D04DBA1.4070108@sentex.net> In-Reply-To: <4D04DBA1.4070108@sentex.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 11:54:42 -0000 On 12/12/2010 15:26, Mike Tancsa wrote: > On 12/12/2010 3:43 AM, Kostik Belousov wrote: >> Please try this patch on the latest HEAD or RELENG_8. >> > > I tried both on i386 and amd64 and all looks good! I did 1000 > iterations of > cryptotest -c -z -t 10 > > without issue! Thanks for the quick fix! I redid my testing on a (read-only attached) geli provider (now with XTS instead of CBC) taking checksums of all files: 8.2-BETA1 without patch without aesni loaded: all checksums ok. 8.2-BETA1 with patch without aesni loaded: all checksums ok. 8.2-BETA1 without patch with aesni loaded: 124 of 18209 failures. 8.2-BETA1 with patch with aesni loaded: all checksums ok. The patch seems to fix my geli problem on 8.2-BETA1 amd64, too. Thanks! Jan Henrik From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 12:38:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5784E1065673; Mon, 13 Dec 2010 12:38:19 +0000 (UTC) (envelope-from milu@dat.pl) Received: from jab.dat.pl (dat.pl [80.51.155.34]) by mx1.freebsd.org (Postfix) with ESMTP id 30ED58FC17; Mon, 13 Dec 2010 12:38:17 +0000 (UTC) Received: from jab.dat.pl (jsrv.dat.pl [127.0.0.1]) by jab.dat.pl (Postfix) with ESMTP id 21878AC; Mon, 13 Dec 2010 13:23:13 +0100 (CET) X-Virus-Scanned: amavisd-new at dat.pl Received: from jab.dat.pl ([127.0.0.1]) by jab.dat.pl (jab.dat.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZMOYtoRUXrLL; Mon, 13 Dec 2010 13:23:10 +0100 (CET) Received: from snifi.localnet (unknown [212.69.68.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jab.dat.pl (Postfix) with ESMTPSA id 8C5F026; Mon, 13 Dec 2010 13:23:10 +0100 (CET) From: Maciej Milewski To: freebsd-stable@freebsd.org Date: Mon, 13 Dec 2010 13:23:44 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.36-ARCH; KDE/4.5.4; x86_64; ; ) References: In-Reply-To: X-KMail-Markup: true MIME-Version: 1.0 Message-Id: <201012131323.45172.milu@dat.pl> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Adrian Chadd , Russell Yount Subject: Re: atheros broadcast/multicast corruption with multiple hostap's X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 12:38:19 -0000 Hi Adrian, I've found the chipsets you were asking - those cards are pretty popular as far as I can see on many wireless forums. > > I have only 11agb radios though: > Which chipsets are they? > > NL-5354MP + Aries2 It looks that it's miniPCI Atheros 5213, Senao NL-5354MP Plus Aries2 [1] > > 5004 MP Atheros 4G / CM9 Atheros AR5004 4th generation chipset. AR5213 (MAC+BB) + AR5112 (2.4/5GHz radio) more info [2] > What I'd really like to do is write up a set of testing procedures for > doing things to the ath driver - in station, hostap and adhoc modes - > so I can test my local 11n+refactored HAL against it. If you've got a > working setup then I'd like to try and get that documented and > reproducable, complete with a set of tests for each to try and ensure > that as much stuff works as possible. That would be very nice to have it in one place to follow in case of any suspected problems. > I'd also like to make sure that the AR5416 HAL as shipped in FreeBSD > behaves the same way as the AR5210,AR5211,AR5212 HALs as well. I only > have an AR5213 card here; the rest of mine are 11n (AR5416, AR9160, > AR9280.) > I don't know if I'm going to be able to get all of this into > 9.0-RELEASE but I'd like to try. The atheros 11n chipsets are > everywhere now; I'd like to both support the legacy stuff and the new > stuff with all the features fully working. :-) Right now I haven't any > idea about what works and what doesn't. > > Thanks, > Adrian [1] http://www.seattlewireless.net/ClientAdapters/802.11g [2] http://store.netgate.com/5004-MP-ATHEROS-4G-CM9-80211abg-miniPCI-Card- P125.aspx Greetings, Maciej From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 13:26:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED03F1065774 for ; Mon, 13 Dec 2010 13:26:22 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 552AB8FC15 for ; Mon, 13 Dec 2010 13:26:22 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id E373946B17; Mon, 13 Dec 2010 08:26:21 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CE5388A01D; Mon, 13 Dec 2010 08:26:19 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Date: Mon, 13 Dec 2010 08:24:33 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20101102; KDE/4.4.5; amd64; ; ) References: <4BCE4D0F.2020807@quip.cz> <4BCE6615.9010707@quip.cz> <4D03AC1D.5070906@quip.cz> In-Reply-To: <4D03AC1D.5070906@quip.cz> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201012130824.33968.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 13 Dec 2010 08:26:19 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.9 required=4.2 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Garrett Cooper , Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: /libexec/ld-elf.so.1: Cannot execute objects on / X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 13:26:23 -0000 On Saturday, December 11, 2010 11:51:41 am Miroslav Lachman wrote: > Miroslav Lachman wrote: > > Garrett Cooper wrote: > >> 2010/4/20 Miroslav Lachman<000.fbsd@quip.cz>: > >>> I have large storage partition (/vol0) mounted as noexec and nosuid. > >>> Then > >>> one directory from this partition is mounted by nullfs as "exec and > >>> suid" so > >>> anything on it can be executed. > >>> > >>> The directory contains full installation of jail. Jail is running > >>> fine, but > >>> some ports (PHP for example) cannot be compiled inside the jail with > >>> message: > >>> > >>> /libexec/ld-elf.so.1: Cannot execute objects on / > >>> > >>> The same apply to executing of apxs > >>> > >>> root@rainnew ~/# /usr/local/sbin/apxs -q MPM_NAME > >>> /libexec/ld-elf.so.1: Cannot execute objects on / > >>> > >>> apxs:Error: Sorry, no shared object support for Apache. > >>> apxs:Error: available under your platform. Make sure. > >>> apxs:Error: the Apache module mod_so is compiled into. > >>> apxs:Error: your server binary '/usr/local/sbin/httpd'.. > >>> > >>> (it should return "prefork") > >>> > >>> So I think there is some bug in checking the mountpoint options, > >>> where the > >>> check is made on "parent" of the nullfs instead of the nullfs target > >>> mountpoint. > >>> > >>> It is on 6.4-RELEASE i386 GENERIC. I did not test it on another release. > >>> > >>> This is list of related mount points: > >>> > >>> /dev/mirror/gm0s2d on /vol0 (ufs, local, noexec, nosuid, soft-updates) > >>> /vol0/jail/.nullfs/rain on /vol0/jail/rain_new (nullfs, local) > >>> /usr/ports on /vol0/jail/rain_new/usr/ports (nullfs, local) > >>> devfs on /vol0/jail/rain_new/dev (devfs, local) > >>> > >>> If I changed /vol0 options to (ufs, local, soft-updates) the above > >>> error is > >>> gone and apxs / compilation works fine. > >>> > >>> Can somebody look at this problem? > >> > >> Can you please provide output from ktrace / truss for the issue? > > > > I did > > # ktrace /usr/local/sbin/apxs -q MPM_NAME > > > > The output is here http://freebsd.quip.cz/ld-elf/ktrace.out > > > > Let me know if you need something else. > > > > Thank you for your interest! > > The problem is still there in FreeBSD 8.1-RELEASE amd64 GENERIC (and in > 7.x). > > Can somebody say if this is a bug or an expected "feature"? I think this is the expected behavior as nullfs is simply re-exposing /vol0 and it shouldn't be able to create a more privileged mount than the underlying mount I think (e.g. a read/write nullfs mount of a read-only filesystem would not make the underlying files read/write). It can be used to provide less privilege (e.g. a readonly nullfs mount of a read/write filesystem does not allow writes via the nullfs layer). That said, I'm not sure exactly where the permission check is failing. execve() only checks MNT_NOEXEC on the "upper" vnode's mountpoint (i.e. the nullfs mountpoint) and the VOP_ACCESS(.., V_EXEC) check does not look at MNT_NOEXEC either. I do think there might be bugs in that a nullfs mount that specifies noexec or nosuid might not enforce the noexec or nosuid bits if the underlying mount point does not have them set (from what I can see). -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 15:27:21 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C60C61065696 for ; Mon, 13 Dec 2010 15:27:21 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB558FC0C for ; Mon, 13 Dec 2010 15:27:21 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:2540:154a:ba54:4afb] ([IPv6:2607:f3e0:0:4:2540:154a:ba54:4afb]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oBDFRImS085547 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 13 Dec 2010 10:27:18 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D063B44.4050303@sentex.net> Date: Mon, 13 Dec 2010 10:27:00 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: stable-list freebsd X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Subject: cryptodev cipher registration (aesni and padlock) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 15:27:21 -0000 While doing some testing with the aesni driver, it seems some ciphers are registered with openssl and some are not. e.g. if I start an ssh session using aes128, I see the following [pyroxene]% ssh -c aes128-cbc smarthost1 "cryptostats" | grep sym 654198 symmetric crypto ops (0 errors, 0 times driver blocked) [pyroxene]% ssh -c aes128-cbc smarthost1 "cryptostats" | grep sym 654225 symmetric crypto ops (0 errors, 0 times driver blocked) [pyroxene]% ie it shows the hardware transformation count increasing. But if I do aes 192 or 256, it does not [pyroxene]% ssh -c aes256-cbc smarthost1 "cryptostats" | grep sym 654231 symmetric crypto ops (0 errors, 0 times driver blocked) [pyroxene]% ssh -c aes192-cbc smarthost1 "cryptostats" | grep sym 654231 symmetric crypto ops (0 errors, 0 times driver blocked) [pyroxene]% ssh -c aes192-cbc smarthost1 "cryptostats" | grep sym 654231 symmetric crypto ops (0 errors, 0 times driver blocked) [pyroxene]% ssh -c aes192-cbc smarthost1 "cryptostats" | grep sym 654231 symmetric crypto ops (0 errors, 0 times driver blocked) [pyroxene]% Yet the are supposed to be supported, no ? Where in openssl is this configured ? The padlock driver does the same thing % ssh -c aes256-cbc smarthost1 "cryptotest -z" 0.000 sec, 2 aes crypts, 16 bytes, 4000000 byte/sec, 30.5 Mb/sec 0.000 sec, 2 aes crypts, 32 bytes, 16000000 byte/sec, 122.1 Mb/sec 0.000 sec, 2 aes crypts, 64 bytes, 32000000 byte/sec, 244.1 Mb/sec 0.000 sec, 2 aes crypts, 128 bytes, 64000000 byte/sec, 488.3 Mb/sec 0.000 sec, 2 aes crypts, 256 bytes, 128000000 byte/sec, 976.6 Mb/sec 0.000 sec, 2 aes crypts, 512 bytes, 170666667 byte/sec, 1302.1 Mb/sec 0.000 sec, 2 aes crypts, 1024 bytes, 292571429 byte/sec, 2232.1 Mb/sec 0.000 sec, 2 aes crypts, 2048 bytes, 455111111 byte/sec, 3472.2 Mb/sec 0.000 sec, 2 aes crypts, 4096 bytes, 512000000 byte/sec, 3906.2 Mb/sec 0.000 sec, 2 aes crypts, 8192 bytes, 420102564 byte/sec, 3205.1 Mb/sec 0.000 sec, 2 aes192 crypts, 16 bytes, 8000000 byte/sec, 61.0 Mb/sec 0.000 sec, 2 aes192 crypts, 32 bytes, 16000000 byte/sec, 122.1 Mb/sec 0.000 sec, 2 aes192 crypts, 64 bytes, 32000000 byte/sec, 244.1 Mb/sec 0.000 sec, 2 aes192 crypts, 128 bytes, 64000000 byte/sec, 488.3 Mb/sec 0.000 sec, 2 aes192 crypts, 256 bytes, 128000000 byte/sec, 976.6 Mb/sec 0.000 sec, 2 aes192 crypts, 512 bytes, 204800000 byte/sec, 1562.5 Mb/sec 0.000 sec, 2 aes192 crypts, 1024 bytes, 341333333 byte/sec, 2604.2 Mb/sec 0.000 sec, 2 aes192 crypts, 2048 bytes, 409600000 byte/sec, 3125.0 Mb/sec 0.000 sec, 2 aes192 crypts, 4096 bytes, 546133333 byte/sec, 4166.7 Mb/sec 0.000 sec, 2 aes192 crypts, 8192 bytes, 496484848 byte/sec, 3787.9 Mb/sec 0.000 sec, 2 aes256 crypts, 16 bytes, 10666667 byte/sec, 81.4 Mb/sec 0.000 sec, 2 aes256 crypts, 32 bytes, 21333333 byte/sec, 162.8 Mb/sec 0.000 sec, 2 aes256 crypts, 64 bytes, 32000000 byte/sec, 244.1 Mb/sec 0.000 sec, 2 aes256 crypts, 128 bytes, 51200000 byte/sec, 390.6 Mb/sec 0.000 sec, 2 aes256 crypts, 256 bytes, 102400000 byte/sec, 781.2 Mb/sec 0.000 sec, 2 aes256 crypts, 512 bytes, 204800000 byte/sec, 1562.5 Mb/sec 0.000 sec, 2 aes256 crypts, 1024 bytes, 292571429 byte/sec, 2232.1 Mb/sec 0.000 sec, 2 aes256 crypts, 2048 bytes, 409600000 byte/sec, 3125.0 Mb/sec 0.000 sec, 2 aes256 crypts, 4096 bytes, 512000000 byte/sec, 3906.2 Mb/sec 0.000 sec, 2 aes256 crypts, 8192 bytes, 442810811 byte/sec, 3378.4 Mb/secW From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 20:06:17 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24FE9106566C for ; Mon, 13 Dec 2010 20:06:17 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id AC4E58FC18 for ; Mon, 13 Dec 2010 20:06:16 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id oBDK6CCT023914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Dec 2010 07:06:14 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id oBDK6C2T061372; Tue, 14 Dec 2010 07:06:12 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id oBDK6CKq061371; Tue, 14 Dec 2010 07:06:12 +1100 (EST) (envelope-from peter) Date: Tue, 14 Dec 2010 07:06:12 +1100 From: Peter Jeremy To: "Eugene M. Zheganin" Message-ID: <20101213200611.GA61140@server.vk2pj.dyndns.org> References: <4D037934.6080401@norma.perm.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <4D037934.6080401@norma.perm.ru> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: FreeBSD Stable Subject: Re: 8.1 livelock/hangup: possible actions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 20:06:17 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Dec-11 18:14:28 +0500, "Eugene M. Zheganin" wro= te: >I'm having problems with 8.1-REL/zfs/amd64. It's a IMB x3250 m2 system,=20 >1Gb RAM, dualcore intel e3110, two bge(4) and LSI1064e disk controller. 1GB RAM is really light on for ZFS and there are some known ARC issues in 8.1 that can lead to free memory starvation. The most obvious indicator of this issue is that "free" memory reported by "top" OR "systat -v" drops _very_ low although there is plenty of "cache" and "inactive" memory. If you can't update to 8-stable, try changing arc_memory_throttle() in /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c to have uint64_t available_memory =3D ptoa((uintmax_t)cnt.v_free_count + cnt.v_cache_count); instead of uint64_t available_memory =3D ptoa((uintmax_t)cnt.v_free_count); at the top of the function. This fixes the worst bug but there are lots of other fixes if you upgrade. --=20 Peter Jeremy --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAk0GfLMACgkQ/opHv/APuIcmqQCfcDHujyc+QQ7WhJXyXMexh/xO Yl8AoJg7csaq3LMeUZROJ/Jpzxq+03X1 =NStw -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 21:07:06 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88540106566B for ; Mon, 13 Dec 2010 21:07:06 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 168728FC0A for ; Mon, 13 Dec 2010 21:07:05 +0000 (UTC) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id oBDL73aR020306 ; Mon, 13 Dec 2010 22:07:04 +0100 (CET) X-Ids: 168 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.14.3/8.14.3) with ESMTP id oBDL5WcM075896; Mon, 13 Dec 2010 22:05:32 +0100 (CET) (envelope-from arno@heho.snv.jussieu.fr) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.14.3/8.14.3/Submit) id oBDL5WwX075892; Mon, 13 Dec 2010 22:05:32 +0100 (CET) (envelope-from arno) To: Jeremy Chadwick From: "Arno J. Klaassen" References: <20101210100230.GA25419@icarus.home.lan> Date: Mon, 13 Dec 2010 22:05:32 +0100 In-Reply-To: <20101210100230.GA25419@icarus.home.lan> (Jeremy Chadwick's message of "Fri\, 10 Dec 2010 02\:02\:30 -0800") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Miltered: at jchkmail.jussieu.fr with ID 4D068AF7.007 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4D068AF7.007/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ Cc: freebsd-stable@freebsd.org Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 21:07:06 -0000 Hello, Jeremy Chadwick writes: > On Fri, Dec 10, 2010 at 10:37:32AM +0100, Arno J. Klaassen wrote: >> just FYI that on an 8-way Tyan S3992-E based box, a reboot under >> 8.2-PRERELEASE (in fact, 8-stable since quite a while) makes the box >> freeze, whilst the same thing under -current works OK. > > Try toggling these two sysctls on the 8.2-PRERELEASE box. Be sure to > check what the defaults are before toggling them, and only mess with one > at a time. > > hw.acpi.handle_reboot > hw.acpi.disable_on_reboot nope, no difference. Defaults are 0 for both sysctls, both on -current and -8-stable. I noticed that -current prints 'cpu_reset: Stopping other CPUs' at the very end were -8-stable doesn't. Thanx for your answer, best, Arno From owner-freebsd-stable@FreeBSD.ORG Mon Dec 13 23:46:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F561106564A for ; Mon, 13 Dec 2010 23:46:46 +0000 (UTC) (envelope-from prvs=19633a9885=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 9671E8FC0A for ; Mon, 13 Dec 2010 23:46:45 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Mon, 13 Dec 2010 23:46:32 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Mon, 13 Dec 2010 23:46:32 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50011773701.msg for ; Mon, 13 Dec 2010 23:46:31 +0000 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=19633a9885=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Message-ID: <59F3B2944C764A36B912E6B50B4D4DD9@multiplay.co.uk> From: "Steven Hartland" To: "Jeremy Chadwick" , "Arno J. Klaassen" References: <20101210100230.GA25419@icarus.home.lan> Date: Mon, 13 Dec 2010 23:46:31 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Cc: freebsd-stable@freebsd.org Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2010 23:46:46 -0000 ----- Original Message ----- From: "Arno J. Klaassen" > Jeremy Chadwick writes: > >> On Fri, Dec 10, 2010 at 10:37:32AM +0100, Arno J. Klaassen wrote: >>> just FYI that on an 8-way Tyan S3992-E based box, a reboot under >>> 8.2-PRERELEASE (in fact, 8-stable since quite a while) makes the box >>> freeze, whilst the same thing under -current works OK. >> >> Try toggling these two sysctls on the 8.2-PRERELEASE box. Be sure to >> check what the defaults are before toggling them, and only mess with one >> at a time. >> >> hw.acpi.handle_reboot >> hw.acpi.disable_on_reboot > > nope, no difference. Defaults are 0 for both sysctls, both on -current > and -8-stable. > > I noticed that -current prints 'cpu_reset: Stopping other CPUs' at the > very end were -8-stable doesn't. > > Thanx for your answer, best, Arno Ooo we had that on a box here on Friday that was running a recent stable, thought it was an isolated incident, possibly not! Will try those options if it happens again but I know this hardware doesn't usually have issues rebooting, so if that fixes its a recent issue in stable. Regards Steve P.S. Resend to test mailman fix, so appologies to anyone who gets this more than once, but my mails have been bouncing from the lists. ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 00:21:42 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 525CC1065672 for ; Tue, 14 Dec 2010 00:21:42 +0000 (UTC) (envelope-from roberto@keltia.net) Received: from keltia.net (centre.keltia.net [IPv6:2a01:240:fe5c::41]) by mx1.freebsd.org (Postfix) with ESMTP id EB4CC8FC12 for ; Tue, 14 Dec 2010 00:21:41 +0000 (UTC) Received: from lonrach.keltia.net (unknown [IPv6:2a01:240:fe5c:0:d69a:20ff:fed0:3a83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.net (Postfix/TLS) with ESMTPSA id E97D6B912 for ; Tue, 14 Dec 2010 01:21:38 +0100 (CET) Date: Tue, 14 Dec 2010 01:21:37 +0100 From: Ollivier Robert To: stable@freebsd.org Message-ID: <20101214002137.GD35142@lonrach.keltia.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: MacOS X / MBP 4,1 - FreeBSD 8.0 / T3500-E5520 Nehalem User-Agent: Mutt/1.5.20 (2009-06-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (keltia.net); Tue, 14 Dec 2010 01:21:39 +0100 (CET) Cc: Subject: Build issue in libstdc++ at revision r216418 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 00:21:42 -0000 Just trying to update my 8.1-PRERELEASE to 8.2-PRERELEASE and it tumbles upon this error in libstdc++. Any idea? 2 -O -pipe -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H -I/usr/src/gnu/lib/libstdc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -I. -frandom-seed=RepeatabilityConsideredGood -fstack-protector -fno-implicit-templates -ffunction-sections -fdata-sections -Wno-deprecated -c atomicity.cc atomicity.cc: In function '_Atomic_word __gnu_cxx::__exchange_and_add(volatile _Atomic_word*, int)': atomicity.cc:36: error: redefinition of '_Atomic_word __gnu_cxx::__exchange_and_add(volatile _Atomic_word*, int)' /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/ext/atomicity.h:50: error: '_Atomic_word __gnu_cxx::__exchange_and_add(volatile _Atomic_word*, int)' previously defined here atomicity.cc: In function 'void __gnu_cxx::__atomic_add(volatile _Atomic_word*, int)': atomicity.cc:47: error: redefinition of 'void __gnu_cxx::__atomic_add(volatile _Atomic_word*, int)'/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/ext/atomicity.h:54: error: 'void __gnu_cxx::__atomic_add(volatile _Atomic_word*, int)' previously defined here *** Error code 1 Stop in /usr/src/gnu/lib/libstdc++. *** Error code 1 Stop in /usr/src/gnu/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. 162.46 real 111.68 user 45.58 sys Tue Dec 14 00:42:55 CET 2010 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr In memoriam to Ondine : http://ondine.keltia.net/ From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 00:38:38 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0868C106564A for ; Tue, 14 Dec 2010 00:38:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id A65E68FC08 for ; Tue, 14 Dec 2010 00:38:37 +0000 (UTC) Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta08.westchester.pa.mail.comcast.net with comcast id inDo1f00A0Fqzac58oedjX; Tue, 14 Dec 2010 00:38:37 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta08.westchester.pa.mail.comcast.net with comcast id ioeU1f00a3LrwQ23UoeZ27; Tue, 14 Dec 2010 00:38:37 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 04A7E9B427; Mon, 13 Dec 2010 16:38:26 -0800 (PST) Date: Mon, 13 Dec 2010 16:38:26 -0800 From: Jeremy Chadwick To: Steven Hartland Message-ID: <20101214003825.GA13836@icarus.home.lan> References: <20101210100230.GA25419@icarus.home.lan> <59F3B2944C764A36B912E6B50B4D4DD9@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59F3B2944C764A36B912E6B50B4D4DD9@multiplay.co.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 00:38:38 -0000 On Mon, Dec 13, 2010 at 11:46:31PM -0000, Steven Hartland wrote: > ----- Original Message ----- From: "Arno J. Klaassen" > > > >Jeremy Chadwick writes: > > > >>On Fri, Dec 10, 2010 at 10:37:32AM +0100, Arno J. Klaassen wrote: > >>>just FYI that on an 8-way Tyan S3992-E based box, a reboot under > >>>8.2-PRERELEASE (in fact, 8-stable since quite a while) makes the box > >>>freeze, whilst the same thing under -current works OK. > >> > >>Try toggling these two sysctls on the 8.2-PRERELEASE box. Be sure to > >>check what the defaults are before toggling them, and only mess with one > >>at a time. > >> > >>hw.acpi.handle_reboot > >>hw.acpi.disable_on_reboot > > > >nope, no difference. Defaults are 0 for both sysctls, both on -current > >and -8-stable. > > > >I noticed that -current prints 'cpu_reset: Stopping other CPUs' at the > >very end were -8-stable doesn't. This message isn't always shown, and as I understand it, this is normal. There may have been a fix for the issue in HEAD/CURRENT, but historically this message has not always been shown. It probably has something to do with which CPU is handling the printing of the messages (and which gets reset first on a multi-CPU system). > >Thanx for your answer, best, Arno > > Ooo we had that on a box here on Friday that was running a recent stable, > thought it was an isolated incident, possibly not! Will try those options > if it happens again but I know this hardware doesn't usually have issues > rebooting, so if that fixes its a recent issue in stable. This is purely speculative on my part, and is the only thing I (off the top of my head) can think of that might cause it: there were some ACPICA changes that were brought in within the past 4-8 weeks (possibly two different sets), that may have caused this. I'm not sure however, and sadly I can't remember who did the work or the commit. Two things to point out: 1) I've seen systems where "cpu_reset: Stopping other CPUs" gets printed (or sometimes doesn't, see above), then for about 5 *full minutes* the system sits there doing nothing, but then eventually reboots. Try being a bit more patient to see if this is the case. Also try dropping to the debugger via serial console (serial break) or VGA (Ctrl-Alt-Esc). 2) I'd recommend to those who are experiencing this problem to try booting with ACPI disabled (it's one of the boot menu options), and then try rebooting the system. If this works, chances are the issue is related to the ACPI code, and someone may want to cross-post to freebsd-acpi to get proper attention to it. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 01:24:17 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81E01106564A for ; Tue, 14 Dec 2010 01:24:17 +0000 (UTC) (envelope-from prvs=19646eb657=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 14A358FC08 for ; Tue, 14 Dec 2010 01:24:16 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Tue, 14 Dec 2010 01:13:16 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Tue, 14 Dec 2010 01:13:16 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50011774164.msg for ; Tue, 14 Dec 2010 01:13:16 +0000 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=19646eb657=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Message-ID: <8EE279F73559489794D17C900733517A@multiplay.co.uk> From: "Steven Hartland" To: "Jeremy Chadwick" References: <20101210100230.GA25419@icarus.home.lan><59F3B2944C764A36B912E6B50B4D4DD9@multiplay.co.uk> <20101214003825.GA13836@icarus.home.lan> Date: Tue, 14 Dec 2010 01:13:15 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Cc: freebsd-stable@freebsd.org Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 01:24:17 -0000 ----- Original Message ----- From: "Jeremy Chadwick" > Two things to point out: > > 1) I've seen systems where "cpu_reset: Stopping other CPUs" gets printed > (or sometimes doesn't, see above), then for about 5 *full minutes* the > system sits there doing nothing, but then eventually reboots. Try being > a bit more patient to see if this is the case. Also try dropping to the > debugger via serial console (serial break) or VGA (Ctrl-Alt-Esc). Waited over 24 hours with the machine sat at the sync print apparently when our engineer kicked it with the reset button. > 2) I'd recommend to those who are experiencing this problem to try > booting with ACPI disabled (it's one of the boot menu options), and then > try rebooting the system. If this works, chances are the issue is > related to the ACPI code, and someone may want to cross-post to > freebsd-acpi to get proper attention to it. 9 times out of 10 this doesn't work any more as machines require it for correct driver detection, still worth a go but thought I'd mention it. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 01:56:52 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFACD106566C for ; Tue, 14 Dec 2010 01:56:51 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 89B3A8FC0C for ; Tue, 14 Dec 2010 01:56:51 +0000 (UTC) Received: by vws9 with SMTP id 9so70015vws.13 for ; Mon, 13 Dec 2010 17:56:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=kaR5p7/4iXfNrQW1ws1vvXrsfUW8dDObqEugvQ1FFvY=; b=AxLHy4Vr8vKJF1wF2QmClKF0tRURtVzerCR6JM9F9mXwv1BPCLocae452YWTEmwm+b XDgYHWJq6PusRDxEVEqHBjAP8O9UWRkzHF11KSWNwWlpvtDMfUNQeNGL2Wo+6bb4fqJ1 T+oLZSkcP1x5c91hvc+wtfX+RXnTokv3mA2M4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=kPKFZfQbrUA9gG2rfpDXFLYjgwD/ZGTBKC7UOMxQZhp475S7L6uamBEzN46JYDCL2k rOOjdsZZW7yfuGj10tB2Jd0ML96SRU3FAvxff/5rANzZwQp4f1GX243joKfIDnKJpox4 qEHUaAnEMZ1Ht1d6LsxQu5w83A/KsQ3qnCVgA= Received: by 10.220.164.70 with SMTP id d6mr1408235vcy.130.1292290304905; Mon, 13 Dec 2010 17:31:44 -0800 (PST) Received: from kan.dnsalias.net (c-24-63-226-98.hsd1.ma.comcast.net [24.63.226.98]) by mx.google.com with ESMTPS id d14sm1573641vcx.23.2010.12.13.17.31.42 (version=SSLv3 cipher=RC4-MD5); Mon, 13 Dec 2010 17:31:43 -0800 (PST) Date: Mon, 13 Dec 2010 20:31:37 -0500 From: Alexander Kabaev To: Ollivier Robert Message-ID: <20101213203137.061562bb@kan.dnsalias.net> In-Reply-To: <20101214002137.GD35142@lonrach.keltia.net> References: <20101214002137.GD35142@lonrach.keltia.net> X-Mailer: Claws Mail 3.7.7 (GTK+ 2.22.1; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/nXKYDaygNS9s1MqnAHVoj1x"; protocol="application/pgp-signature" Cc: stable@freebsd.org Subject: Re: Build issue in libstdc++ at revision r216418 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 01:56:52 -0000 --Sig_/nXKYDaygNS9s1MqnAHVoj1x Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 14 Dec 2010 01:21:37 +0100 Ollivier Robert wrote: > Just trying to update my 8.1-PRERELEASE to 8.2-PRERELEASE and it > tumbles upon this error in libstdc++. Any idea? >=20 > 2 -O -pipe -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H > -I/usr/src/gnu/lib/libstdc++ > -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++ > -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc > -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include > -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcclibs/include > -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -I. > -frandom-seed=3DRepeatabilityConsideredGood -fstack-protector > -fno-implicit-templates -ffunction-sections -fdata-sections > -Wno-deprecated -c atomicity.cc atomicity.cc: In function > '_Atomic_word __gnu_cxx::__exchange_and_add(volatile _Atomic_word*, > int)': atomicity.cc:36: error: redefinition of '_Atomic_word > __gnu_cxx::__exchange_and_add(volatile _Atomic_word*, > int)' /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/ext/a= tomicity.h:50: > error: '_Atomic_word __gnu_cxx::__exchange_and_add(volatile > _Atomic_word*, int)' previously defined here atomicity.cc: In > function 'void __gnu_cxx::__atomic_add(volatile _Atomic_word*, int)': > atomicity.cc:47: error: redefinition of 'void > __gnu_cxx::__atomic_add(volatile _Atomic_word*, > int)'/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/ext/at= omicity.h:54: > error: 'void __gnu_cxx::__atomic_add(volatile _Atomic_word*, int)' > previously defined here *** Error code 1 >=20 Clean your obj, pretty please. Then do make cleandir couple of times in src. Then repeat your build. --=20 Alexander Kabaev --Sig_/nXKYDaygNS9s1MqnAHVoj1x Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iD8DBQFNBsj9Q6z1jMm+XZYRAkVhAKDJnXXXqp/CMebxMwe6YBdIUbjV3wCbBm97 4/6NYejXd/rBi3nvNTDKoBg= =Go2H -----END PGP SIGNATURE----- --Sig_/nXKYDaygNS9s1MqnAHVoj1x-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 02:47:47 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 184C5106564A; Tue, 14 Dec 2010 02:47:47 +0000 (UTC) (envelope-from russell.yount@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 9E5568FC08; Tue, 14 Dec 2010 02:47:46 +0000 (UTC) Received: by qyk8 with SMTP id 8so3815395qyk.13 for ; Mon, 13 Dec 2010 18:47:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=rWfY3JGaRPriKwvqGeMl65TZUK8SFcElc4ohN2lq54k=; b=JiHW5hwSi8Rzx8vrQd30kvdIuo/I4/iYZfi6j6vLFdobJaM/JKqE97uYyx6BgrlDDX P7CLJ7QS0pPvP/WodpXFFhUZN1sqnpYg3e8dlBN0mfh+22A69JwywpW3rtC17mtwZ/gw WqPfcAKxhPx5ulZgZDDhOWzD0Fjm34tPuAVDw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ThZQ1T65x1EBrwrTG1+8RkWjXJk1oRjY5xzcR8dzvzZNiGhhqjaNyD87Hx/kuIB2no omMgZMfUcaLPvyfX6XTG9CVO1IjpfG+2r0jZVqEFGJVl6CcTNoYozqy4Gxb8bF4vXOnv XDuLrzXoAz1T8Gxi9NfD93gBjxTx0RHlrv9qs= MIME-Version: 1.0 Received: by 10.229.84.81 with SMTP id i17mr4423846qcl.215.1292294865633; Mon, 13 Dec 2010 18:47:45 -0800 (PST) Received: by 10.220.13.148 with HTTP; Mon, 13 Dec 2010 18:47:45 -0800 (PST) In-Reply-To: References: <4B521FC2.4050402@errno.com> <4B535AAE.3060308@errno.com> <4B5BA0C1.8010901@errno.com> Date: Mon, 13 Dec 2010 21:47:45 -0500 Message-ID: From: Russell Yount To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: atheros broadcast/multicast corruption with multiple hostap's X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 02:47:47 -0000 Adrian, Let me try to answer your questions first. >Which chipsets are they? Both the NL-5354MP + Aries2 5004 MP Atheros 4G / CM9 identify themselves as ath0: mem 0xa0000000-0xa000ffff irq 10 at device 16.0 on pci0 ath0: [ITHREAD] ath0: AR5212 mac 5.9 RF5112 phy 4.3 I also have two D-Link DWL-AG530 on an old Dell desktop machine I used to debug the driver problems which identify themselves as the same chips. >Are they using different keys? Here is a summary of my setup. Each of the four APs has 4 SSID: wireless{0,1,2,3} Each of the wlan{0,1,2,3} is bridged to a corresponding VLAN on eth0. A 5th VLAN has an IP interface for the AP itself. There are 4 instances of hostapd operating on each AP. This is the only non-standard part of the configuration which I added rc scripts to start the hostapd's with different hostapd.conf and /var/run/hostapd.pid files Each hostapd is configured to talk to a pair of radius servers, one primary and one backup. The radius servers are built from freeradius2 ports configuration and configured as 4 virtual radius servers operating on different service ports. Each instance is provisioned with a certificate which matches the SSID it is serving signed by a common root self signed certificate. The self signed root also is used to sign the client certificates. The AP also run pf so they can block the CARP multicast from the two system which are gateways for the different VLANs mirroring the SSIDs. >Did you try WPA + AES/CCMP in STA mode with these? If not, would you please do that? Yes, station mode works. >What would be a better account to email? Really this address I normally read. I also use rjy@cmu.edu but am trying to seperate my personal projects from work so I prefer to use this gmail one. The main reason it took to long for me to get back to you was I have been getting a pre-surgery workup for knee surgery I had last friday. I normally check this account reasonably often. >What I'd really like to do is write up a set of testing procedures for >doing things to the ath driver - in station, hostap and adhoc modes - >so I can test my local 11n+refactored HAL against it. If you've got a >working setup then I'd like to try and get that documented and >reproducable, complete with a set of tests for each to try and ensure >that as much stuff works as possible. I think I can help you on that. I would not suggest that you duplicate my setup, but rather here are some suggestions as to where to start. 1.) The /etc/rc.conf lacks the ability to start multiple hostapds. This make stock system testing of mulitiple SSIDs difficult. I cloned the hostapd script as /etc/rc.d/hostapd{0,1,2,3} and referenced /etc/hostapd/hostapd{0,1,2,3}.conf to make this easier to configure. 2.) Similarly you have multiple wireless cards on a client system the wpa_suppliment rc script lacks the ability to specify a diffferent configuration file per interface. 3.) The problem the patch I made fixed was related to the AP recognizing multicast/broadcast traffic orginated by clients when multiple SSID where configured on an AP. Without the patch only the last configured SSID actually recognizes broadcasts coming from client reliably. Since often traffic is initiated by the client the ARP entry on the gateway will be populated by incoming traffic and the gateway will not need to broadcast a whereis this IP which the client would respond to. To test this was tricky since when client connects it orginates traffic using DHCP to get an address. To test I either used a client which did not DHCP or forced thegateway ARP cache to be cleared after client got an address via DHCP. 4.) I can try to help you create a set of scripts which test driver hostapd and wpa_supplicate. Can we work on this off the list for a while until we have something people can comment on? -Russ On Mon, Dec 13, 2010 at 3:49 AM, Adrian Chadd wrote: > (I'm removing Sam from the CC: ; it seems he's not interested in this > stuff any longer.) > > On 8 December 2010 09:54, Russell Yount wrote: > > Adrian, > > > > Yes, I can help track down this. > > > > I have only 11agb radios though: > > NL-5354MP + Aries2 > > 5004 MP Atheros 4G / CM9 > > Which chipsets are they? > > > The changes I made definiately work for these chips, I have 4 APs > operating > > with 4 SSID each all configured with WPA2 using x509 certs. Currently, > the > > kernel I am using is 8.1. > > Are they using different keys? > > Did you try WPA + AES/CCMP in STA mode with these? If not, would you > please do that? > > > I seem to recall that the hardware abstration layer for different > chipsets > > treated handling of multicast reception differently. > > > > Could you send me pointers to what problems are described? > > > > Sorry, I took so long to reply, been rather busy, I do not check this > email > > account as often as my others. > > What would be a better account to email? > > What I'd really like to do is write up a set of testing procedures for > doing things to the ath driver - in station, hostap and adhoc modes - > so I can test my local 11n+refactored HAL against it. If you've got a > working setup then I'd like to try and get that documented and > reproducable, complete with a set of tests for each to try and ensure > that as much stuff works as possible. > > I'd also like to make sure that the AR5416 HAL as shipped in FreeBSD > behaves the same way as the AR5210,AR5211,AR5212 HALs as well. I only > have an AR5213 card here; the rest of mine are 11n (AR5416, AR9160, > AR9280.) > > I don't know if I'm going to be able to get all of this into > 9.0-RELEASE but I'd like to try. The atheros 11n chipsets are > everywhere now; I'd like to both support the legacy stuff and the new > stuff with all the features fully working. :-) Right now I haven't any > idea about what works and what doesn't. > > Thanks, > > > Adrian > From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 07:08:12 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8F1C106566B for ; Tue, 14 Dec 2010 07:08:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 6E1EB8FC17 for ; Tue, 14 Dec 2010 07:08:12 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id oBE788g9029050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Dec 2010 09:08:08 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id oBE788wv044021; Tue, 14 Dec 2010 09:08:08 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id oBE7871Z044020; Tue, 14 Dec 2010 09:08:07 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 14 Dec 2010 09:08:07 +0200 From: Kostik Belousov To: Mike Tancsa Message-ID: <20101214070807.GJ33073@deviant.kiev.zoral.com.ua> References: <4D063B44.4050303@sentex.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="332CIdRmeZdukXAd" Content-Disposition: inline In-Reply-To: <4D063B44.4050303@sentex.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: stable-list freebsd Subject: Re: cryptodev cipher registration (aesni and padlock) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 07:08:12 -0000 --332CIdRmeZdukXAd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 13, 2010 at 10:27:00AM -0500, Mike Tancsa wrote: > While doing some testing with the aesni driver, it seems some ciphers are= registered with openssl and some are not. >=20 > e.g. if I start an ssh session using aes128, I see the following >=20 > [pyroxene]% ssh -c aes128-cbc smarthost1 "cryptostats" | grep sym > 654198 symmetric crypto ops (0 errors, 0 times driver blocked) > [pyroxene]% ssh -c aes128-cbc smarthost1 "cryptostats" | grep sym > 654225 symmetric crypto ops (0 errors, 0 times driver blocked) > [pyroxene]%=20 >=20 > ie it shows the hardware transformation count increasing. But if I do ae= s 192 or 256, it does not >=20 > [pyroxene]% ssh -c aes256-cbc smarthost1 "cryptostats" | grep sym > 654231 symmetric crypto ops (0 errors, 0 times driver blocked) > [pyroxene]% ssh -c aes192-cbc smarthost1 "cryptostats" | grep sym > 654231 symmetric crypto ops (0 errors, 0 times driver blocked) > [pyroxene]% ssh -c aes192-cbc smarthost1 "cryptostats" | grep sym > 654231 symmetric crypto ops (0 errors, 0 times driver blocked) > [pyroxene]% ssh -c aes192-cbc smarthost1 "cryptostats" | grep sym > 654231 symmetric crypto ops (0 errors, 0 times driver blocked) > [pyroxene]%=20 > Yet the are supposed to be supported, no ? Where in openssl is this conf= igured ? The padlock driver does the same thing >=20 > % ssh -c aes256-cbc smarthost1 "cryptotest -z" > 0.000 sec, 2 aes crypts, 16 bytes, 4000000 byte/sec, = 30.5 Mb/sec > 0.000 sec, 2 aes crypts, 32 bytes, 16000000 byte/sec, = 122.1 Mb/sec > 0.000 sec, 2 aes crypts, 64 bytes, 32000000 byte/sec, = 244.1 Mb/sec > 0.000 sec, 2 aes crypts, 128 bytes, 64000000 byte/sec, = 488.3 Mb/sec > 0.000 sec, 2 aes crypts, 256 bytes, 128000000 byte/sec, = 976.6 Mb/sec > 0.000 sec, 2 aes crypts, 512 bytes, 170666667 byte/sec, = 1302.1 Mb/sec > 0.000 sec, 2 aes crypts, 1024 bytes, 292571429 byte/sec, = 2232.1 Mb/sec > 0.000 sec, 2 aes crypts, 2048 bytes, 455111111 byte/sec, = 3472.2 Mb/sec > 0.000 sec, 2 aes crypts, 4096 bytes, 512000000 byte/sec, = 3906.2 Mb/sec > 0.000 sec, 2 aes crypts, 8192 bytes, 420102564 byte/sec, = 3205.1 Mb/sec > 0.000 sec, 2 aes192 crypts, 16 bytes, 8000000 byte/sec, = 61.0 Mb/sec > 0.000 sec, 2 aes192 crypts, 32 bytes, 16000000 byte/sec, = 122.1 Mb/sec > 0.000 sec, 2 aes192 crypts, 64 bytes, 32000000 byte/sec, = 244.1 Mb/sec > 0.000 sec, 2 aes192 crypts, 128 bytes, 64000000 byte/sec, = 488.3 Mb/sec > 0.000 sec, 2 aes192 crypts, 256 bytes, 128000000 byte/sec, = 976.6 Mb/sec > 0.000 sec, 2 aes192 crypts, 512 bytes, 204800000 byte/sec, = 1562.5 Mb/sec > 0.000 sec, 2 aes192 crypts, 1024 bytes, 341333333 byte/sec, = 2604.2 Mb/sec > 0.000 sec, 2 aes192 crypts, 2048 bytes, 409600000 byte/sec, = 3125.0 Mb/sec > 0.000 sec, 2 aes192 crypts, 4096 bytes, 546133333 byte/sec, = 4166.7 Mb/sec > 0.000 sec, 2 aes192 crypts, 8192 bytes, 496484848 byte/sec, = 3787.9 Mb/sec > 0.000 sec, 2 aes256 crypts, 16 bytes, 10666667 byte/sec, = 81.4 Mb/sec > 0.000 sec, 2 aes256 crypts, 32 bytes, 21333333 byte/sec, = 162.8 Mb/sec > 0.000 sec, 2 aes256 crypts, 64 bytes, 32000000 byte/sec, = 244.1 Mb/sec > 0.000 sec, 2 aes256 crypts, 128 bytes, 51200000 byte/sec, = 390.6 Mb/sec > 0.000 sec, 2 aes256 crypts, 256 bytes, 102400000 byte/sec, = 781.2 Mb/sec > 0.000 sec, 2 aes256 crypts, 512 bytes, 204800000 byte/sec, = 1562.5 Mb/sec > 0.000 sec, 2 aes256 crypts, 1024 bytes, 292571429 byte/sec, = 2232.1 Mb/sec > 0.000 sec, 2 aes256 crypts, 2048 bytes, 409600000 byte/sec, = 3125.0 Mb/sec > 0.000 sec, 2 aes256 crypts, 4096 bytes, 512000000 byte/sec, = 3906.2 Mb/sec > 0.000 sec, 2 aes256 crypts, 8192 bytes, 442810811 byte/sec, = 3378.4 Mb/secW =46rom my reading of src/crypto/openssl/crypto/engine/eng_cryptodev.c, and browsing http://cvs.openssl.org/rlog?f=3Dopenssl/crypto/engine/eng_cryptodev.c it seems that only OpenSSL HEAD and 1.0 branch have support for AES-192 and AES-256 when working with /dev/crypto. --332CIdRmeZdukXAd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk0HF9cACgkQC3+MBN1Mb4j8dwCcCRyZzbaZRPcf9TNggJ3gRUW0 k3oAoIZRLVFtFRBmye8kX1gBLWI4tD/s =oncn -----END PGP SIGNATURE----- --332CIdRmeZdukXAd-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 07:29:51 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19214106566C for ; Tue, 14 Dec 2010 07:29:51 +0000 (UTC) (envelope-from roberto@keltia.net) Received: from keltia.net (centre.keltia.net [IPv6:2a01:240:fe5c::41]) by mx1.freebsd.org (Postfix) with ESMTP id C32E48FC13 for ; Tue, 14 Dec 2010 07:29:50 +0000 (UTC) Received: from [IPv6:2a01:240:fe5c::226:4aff:fef1:1dd7] (unknown [IPv6:2a01:240:fe5c:0:226:4aff:fef1:1dd7]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.net (Postfix/TLS) with ESMTPSA id CA20A13B7; Tue, 14 Dec 2010 08:29:49 +0100 (CET) References: <20101214002137.GD35142@lonrach.keltia.net> <20101213203137.061562bb@kan.dnsalias.net> In-Reply-To: <20101213203137.061562bb@kan.dnsalias.net> Mime-Version: 1.0 (iPhone Mail 8C148a) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Message-Id: <7FD9B10A-8215-4959-89AE-03235C98CE45@keltia.net> X-Mailer: iPhone Mail (8C148a) From: Ollivier Robert Date: Tue, 14 Dec 2010 08:29:48 +0100 To: Alexander Kabaev X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (keltia.net); Tue, 14 Dec 2010 08:29:49 +0100 (CET) Cc: "stable@freebsd.org" Subject: Re: Build issue in libstdc++ at revision r216418 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 07:29:51 -0000 Le 14 d=C3=A9c. 2010 =C3=A0 02:31, Alexander Kabaev a =C3= =A9crit : > Clean your obj, pretty please. Then do make cleandir couple of times in > src. Then repeat your build. Obj was empty but cleandir did the trick, thanks!= From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 13:57:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06A311065672 for ; Tue, 14 Dec 2010 13:57:19 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 454278FC16 for ; Tue, 14 Dec 2010 13:57:17 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA16321; Tue, 14 Dec 2010 15:57:08 +0200 (EET) (envelope-from avg@freebsd.org) Message-ID: <4D0777B3.5020208@freebsd.org> Date: Tue, 14 Dec 2010 15:57:07 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Jeremy Chadwick References: <20101210100230.GA25419@icarus.home.lan> <59F3B2944C764A36B912E6B50B4D4DD9@multiplay.co.uk> <20101214003825.GA13836@icarus.home.lan> In-Reply-To: <20101214003825.GA13836@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Steven Hartland Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 13:57:19 -0000 on 14/12/2010 02:38 Jeremy Chadwick said the following: > 1) [snip] > Also try dropping to the > debugger via serial console (serial break) or VGA (Ctrl-Alt-Esc). This is a good advice. > 2) I'd recommend to those who are experiencing this problem to try > booting with ACPI disabled (it's one of the boot menu options), and then > try rebooting the system. If this works, chances are the issue is > related to the ACPI code, and someone may want to cross-post to > freebsd-acpi to get proper attention to it. This seems to be an outdated advice. A lot of modern hardware doesn't even boot with ACPI disabled. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 14:39:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5729010656D4; Tue, 14 Dec 2010 14:39:57 +0000 (UTC) (envelope-from eugene@imedia.ru) Received: from lynx.imedia.ru (lynx.imedia.ru [83.242.167.254]) by mx1.freebsd.org (Postfix) with ESMTP id B951C8FC18; Tue, 14 Dec 2010 14:39:56 +0000 (UTC) X-All-Recipients: DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=imedia.ru; s=common; t=1292336866; bh=MqdJ+FtZyHxeV3IfULRh/o76tGaCRdcS/ACOm1dBFLs=; h=From:Reply-To:To:Subject:Date:MIME-Version:Content-Type: Content-Transfer-Encoding:Message-Id; b=ZCrALQSgp5689yIkKe2Av1DRTDrbl4t900OnkSm+ERBjwiGyh7pyhpOvtLyRkVFEp jUIrGk+nnsy2E2bLcgHxRu9qcS8RStY7NJbMSAMkBDyWrbQK5KgGVB4FfVSFyq6eu5 7X4qnWkNucPVBxbbuKoflpXtIEXiOhmRLi1CJPbk= Received: from badger.imedia.ru (root@badger.imedia.ru [10.167.1.243]) by lynx.imedia.ru (8.14.3/8.14.3/TWINS7_LDAP) with ESMTP id oBEERkOB044879; Tue, 14 Dec 2010 17:27:46 +0300 (MSK) (envelope-from eugene@imedia.ru) Received: from badger.imedia.ru (eugene@localhost [127.0.0.1]) by badger.imedia.ru (8.14.4/8.13.1) with ESMTP id oBEERkKf047875; Tue, 14 Dec 2010 17:27:46 +0300 (MSK) (envelope-from eugene@imedia.ru) Received: from localhost (localhost [[UNIX: localhost]]) by badger.imedia.ru (8.14.4/8.13.8/Submit) id oBEERfBS047874; Tue, 14 Dec 2010 17:27:41 +0300 (MSK) (envelope-from eugene@imedia.ru) From: Eugene Mitrofanov Organization: Independent Media Sanoma Magazines To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Date: Tue, 14 Dec 2010 17:27:41 +0300 User-Agent: KMail/1.9.10 X-Origin: badger.imedia.ru MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201012141727.41909.eugene@imedia.ru> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (lynx.imedia.ru [10.167.0.252]); Tue, 14 Dec 2010 17:27:46 +0300 (MSK) X-Virus-Scanned: clamav-milter 0.96.4-exp at lynx.imedia.ru X-Virus-Status: Clean Cc: Subject: 8.1-STABLE Unexpected XML: what does it mean? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugene Mitrofanov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2010 14:39:57 -0000 Hi I observe the very strange message while run a lot of commands: root@beaver:eugene# glabel status Unexpected XML: name=stripesize data="18432" Unexpected XML: name=stripeoffset data="0" Unexpected XML: name=stripesize data="18432" Unexpected XML: name=stripeoffset data="0" Name Status Components iso9660/CDROM N/A acd0 root@beaver:eugene# mdconfig -l Unexpected XML: name=stripesize data="18432" Unexpected XML: name=stripeoffset data="0" root@beaver:eugene# gmirror status Unexpected XML: name=stripesize data="18432" Unexpected XML: name=stripeoffset data="0" gmirror: Command 'status' not available. What subsystem prints them? How can I fix it? Good luck -- EMIT-RIPN, EVM7-RIPE From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 15:12:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 337F91065675 for ; Tue, 14 Dec 2010 15:12:32 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id D8E2A8FC1D for ; Tue, 14 Dec 2010 15:12:31 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PSWYI-0003de-5k for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 16:12:30 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Dec 2010 16:12:30 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Dec 2010 16:12:30 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Tue, 14 Dec 2010 16:12:18 +0100 Lines: 11 Message-ID: References: <201012141727.41909.eugene@imedia.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: <201012141727.41909.eugene@imedia.ru> X-Enigmail-Version: 1.1.2 Cc: freebsd-questions@freebsd.org Subject: Re: 8.1-STABLE Unexpected XML: what does it mean? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 15:12:32 -0000 On 14/12/2010 15:27, Eugene Mitrofanov wrote: > Hi > > I observe the very strange message while run a lot of commands: > > root@beaver:eugene# glabel status > Unexpected XML: name=stripesize data="18432" > Unexpected XML: name=stripeoffset data="0" Maybe you have a label or some other "custom" device name with non-ascii characters or with characters which break xml parsing? From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 15:19:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27266106566B; Tue, 14 Dec 2010 15:19:50 +0000 (UTC) (envelope-from eugene@imedia.ru) Received: from lynx.imedia.ru (lynx.imedia.ru [83.242.167.254]) by mx1.freebsd.org (Postfix) with ESMTP id 889C78FC0A; Tue, 14 Dec 2010 15:19:49 +0000 (UTC) X-All-Recipients: DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=imedia.ru; s=common; t=1292339988; bh=lLGllliIAh3hbPIw7GeHNKIBwvI7dIPDmtmIo5SlLYo=; h=From:Reply-To:To:Subject:Date:Cc:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding:Message-Id; b=DdTdMf0TGTmy9TLWAEUY9TscyT9U/vpuiUIn27KXwuLPb4ZDW9hilKNR4ouMUcuPd lorO/B6F0ausavH91eGvOcsB/R9yPFj2cLqARgzgEf0ILNGl3UEPy38RY15YG6/lzC d4HphyC8gKOy6ejdZ0aflRvmz6io56HbNgd+dKZ0= Received: from badger.imedia.ru (root@badger.imedia.ru [10.167.1.243]) by lynx.imedia.ru (8.14.3/8.14.3/TWINS7_LDAP) with ESMTP id oBEFJmmB055320; Tue, 14 Dec 2010 18:19:48 +0300 (MSK) (envelope-from eugene@imedia.ru) Received: from badger.imedia.ru (eugene@localhost [127.0.0.1]) by badger.imedia.ru (8.14.4/8.13.1) with ESMTP id oBEFJlZb048904; Tue, 14 Dec 2010 18:19:47 +0300 (MSK) (envelope-from eugene@imedia.ru) Received: from localhost (localhost [[UNIX: localhost]]) by badger.imedia.ru (8.14.4/8.13.8/Submit) id oBEFJl68048903; Tue, 14 Dec 2010 18:19:47 +0300 (MSK) (envelope-from eugene@imedia.ru) From: Eugene Mitrofanov Organization: Independent Media Sanoma Magazines To: freebsd-stable@freebsd.org Date: Tue, 14 Dec 2010 18:19:47 +0300 User-Agent: KMail/1.9.10 References: <201012141727.41909.eugene@imedia.ru> In-Reply-To: X-Origin: badger.imedia.ru MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201012141819.47712.eugene@imedia.ru> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (lynx.imedia.ru [10.167.0.252]); Tue, 14 Dec 2010 18:19:48 +0300 (MSK) X-Virus-Scanned: clamav-milter 0.96.4-exp at lynx.imedia.ru X-Virus-Status: Clean Cc: Ivan Voras , freebsd-questions@freebsd.org Subject: Re: 8.1-STABLE Unexpected XML: what does it mean? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugene Mitrofanov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2010 15:19:50 -0000 How can I locate this device? Also I dont understand why mdconfig complains? On Tuesday 14 December 2010, Ivan Voras wrote: > On 14/12/2010 15:27, Eugene Mitrofanov wrote: > > Hi > > > > I observe the very strange message while run a lot of commands: > > > > root@beaver:eugene# glabel status > > Unexpected XML: name=stripesize data="18432" > > Unexpected XML: name=stripeoffset data="0" > > Maybe you have a label or some other "custom" device name with non-ascii > characters or with characters which break xml parsing? > > _______________________________________________ > 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" > > -- EMIT-RIPN, EVM7-RIPE From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 15:25:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AEDC106566C for ; Tue, 14 Dec 2010 15:25:08 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 2503F8FC0A for ; Tue, 14 Dec 2010 15:25:06 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PSWkU-00025W-4C for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 16:25:06 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Dec 2010 16:25:06 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Dec 2010 16:25:06 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Tue, 14 Dec 2010 16:24:53 +0100 Lines: 8 Message-ID: References: <201012141727.41909.eugene@imedia.ru> <201012141819.47712.eugene@imedia.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: <201012141819.47712.eugene@imedia.ru> X-Enigmail-Version: 1.1.2 Cc: freebsd-questions@freebsd.org Subject: Re: 8.1-STABLE Unexpected XML: what does it mean? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 15:25:08 -0000 On 14/12/2010 16:19, Eugene Mitrofanov wrote: > > How can I locate this device? Also I dont understand why mdconfig complains? Try examining the output of # sysctl -b kern.geom.confxml From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 15:29:21 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 181EE1065670; Tue, 14 Dec 2010 15:29:21 +0000 (UTC) (envelope-from eugene@imedia.ru) Received: from lynx.imedia.ru (lynx.imedia.ru [83.242.167.254]) by mx1.freebsd.org (Postfix) with ESMTP id A8B428FC18; Tue, 14 Dec 2010 15:29:19 +0000 (UTC) X-All-Recipients: DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=imedia.ru; s=common; t=1292340558; bh=3qRVS3+asLmS9H0L778czEYUTAkxmnjS9RebfUOo06M=; h=From:Reply-To:To:Subject:Date:Cc:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding:Message-Id; b=OPh6NOg9e2LZIs3YKAp2FeO4TOAOAVYw7A39RIsKP33KDA36N0HFjcGMesLjkGmOW 25fmRMMZHrmuHOcNa4ohpuhjpfDN1zZ81fhQv3bZqXdZU7BnNarh16WlBXIBln071m ytSkY/7yxW0GHCRzLVBWtW1bq4cVV67SdVX3JYzI= Received: from badger.imedia.ru (root@badger.imedia.ru [10.167.1.243]) by lynx.imedia.ru (8.14.3/8.14.3/TWINS7_LDAP) with ESMTP id oBEFTHHk057067; Tue, 14 Dec 2010 18:29:17 +0300 (MSK) (envelope-from eugene@imedia.ru) Received: from badger.imedia.ru (eugene@localhost [127.0.0.1]) by badger.imedia.ru (8.14.4/8.13.1) with ESMTP id oBEFTHtT049036; Tue, 14 Dec 2010 18:29:17 +0300 (MSK) (envelope-from eugene@imedia.ru) Received: from localhost (localhost [[UNIX: localhost]]) by badger.imedia.ru (8.14.4/8.13.8/Submit) id oBEFTHvY049035; Tue, 14 Dec 2010 18:29:17 +0300 (MSK) (envelope-from eugene@imedia.ru) From: Eugene Mitrofanov Organization: Independent Media Sanoma Magazines To: freebsd-stable@freebsd.org Date: Tue, 14 Dec 2010 18:29:17 +0300 User-Agent: KMail/1.9.10 References: <201012141727.41909.eugene@imedia.ru> <201012141819.47712.eugene@imedia.ru> In-Reply-To: X-Origin: badger.imedia.ru MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201012141829.17662.eugene@imedia.ru> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (lynx.imedia.ru [10.167.0.252]); Tue, 14 Dec 2010 18:29:18 +0300 (MSK) X-Virus-Scanned: clamav-milter 0.96.4-exp at lynx.imedia.ru X-Virus-Status: Clean Cc: Ivan Voras , freebsd-questions@freebsd.org Subject: Re: 8.1-STABLE Unexpected XML: what does it mean? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugene Mitrofanov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2010 15:29:21 -0000 On Tuesday 14 December 2010, Ivan Voras wrote: > On 14/12/2010 16:19, Eugene Mitrofanov wrote: > > > > How can I locate this device? Also I dont understand why mdconfig complains? > > Try examining the output of > > # sysctl -b kern.geom.confxml Here they are: FD fd0 1 r0w0e0 fd0 1474560 512 18432 0 ACD acd0 1 r0w0e0 acd0t01 550307840 2048 r0w0e0 acd0 550307840 2048 LABEL acd0 2 r0w0e0 r0w0e0 iso9660/CDROM 550307840 2048 0 550307840 1074820 0 0 VFS ffs.ipsd0s1g 4 r1w1e1 ffs.ipsd0s1f 4 r1w1e1 ffs.da0s1d 4 r1w1e1 ffs.da1s1d 4 r1w1e1 ffs.da1s1e 4 r1w1e1 ffs.ipsd0s1e 4 r1w1e1 ffs.ipsd0s1d 4 r1w1e1 ffs.ipsd0s1a 4 r1w1e1 PART da1s1 3 BSD 8 0 1560072086 63 255 OK r2w2e4 r1w1e1 da1s1e 584008535552 512 419430416 1560072086 5 freebsd-ufs 214748372992 584008535552 7 r1w1e1 da1s1d 214748364800 512 16 419430415 4 freebsd-ufs 8192 214748364800 7 da0s1 3 BSD 8 0 4294945556 63 255 OK r1w1e2 r1w1e1 da0s1d 2199012125184 512 0 4294945556 4 freebsd-ufs 0 2199012125184 7 ipsd0s1 3 BSD 8 0 286744543 32 128 OK r6w6e11 r1w1e1 ipsd0s1g 56618885120 512 176160784 286744543 7 freebsd-ufs 90194321408 56618885120 7 r1w1e1 ipsd0s1f 17179869184 512 142606352 176160783 6 freebsd-ufs 73014452224 17179869184 7 r1w1e1 ipsd0s1e 51539607552 512 41943056 142606351 5 freebsd-ufs 21474844672 51539607552 7 r1w1e1 ipsd0s1d 8589934592 512 25165840 41943055 4 freebsd-ufs 12884910080 8589934592 7 r1w1e0 ipsd0s1b 8589934592 512 8388624 25165839 2 !0 4294975488 8589934592 0 r1w1e1 ipsd0s1a 4294967296 512 16 8388623 1 freebsd-ufs 8192 4294967296 7 da1 2 MBR 4 63 1560084434 63 255 OK r2w2e6 r2w2e4 da1s1 798756908544 512 63 1560072149 1 freebsd 32256 798756908544 165 active da0 2 MBR 4 63 4294950911 63 255 OK r1w1e3 r1w1e2 da0s1 2199012125184 512 63 4294945619 1 freebsd 32256 2199012125184 165 active ipsd0 2 MBR 4 32 286744575 32 128 OK r6w6e17 r6w6e11 ipsd0s1 146813206528 512 32 286744575 1 freebsd 16384 146813206528 165 active MD SWAP swap 4 r1w1e0 DISK da1 1 r2w2e6 da1 798763253760 512 255 63 da0 1 r1w1e3 da0 2199014866944 512 255 63 ipsd0 1 r6w6e17 ipsd0 146813222912 512 128 32 DEV da1s1e 4 r0w0e0 da1s1d 4 r0w0e0 da0s1d 4 r0w0e0 ipsd0s1g 4 r0w0e0 ipsd0s1f 4 r0w0e0 ipsd0s1e 4 r0w0e0 ipsd0s1d 4 r0w0e0 ipsd0s1b 4 r0w0e0 ipsd0s1a 4 r0w0e0 da1s1 3 r0w0e0 da0s1 3 r0w0e0 ipsd0s1 3 r0w0e0 iso9660/CDROM 3 r0w0e0 acd0t01 2 r0w0e0 da1 2 r0w0e0 da0 2 r0w0e0 ipsd0 2 r0w0e0 acd0 2 r0w0e0 fd0 2 r0w0e0 -- EMIT-RIPN, EVM7-RIPE From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 15:54:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE0C9106566B for ; Tue, 14 Dec 2010 15:54:28 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 769738FC15 for ; Tue, 14 Dec 2010 15:54:28 +0000 (UTC) Received: by gyf3 with SMTP id 3so428166gyf.13 for ; Tue, 14 Dec 2010 07:54:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=fMMNxqdfTtM06/N9sBrinM38V6A2q50tscW6FGkfYW8=; b=r8/rTOoZMvAEWvkFIbTF154IXhaoMQXIm0xeAFzkTWWA+fFSF+5moDYPq7DByKhxfF L6t441HCngnlD763ZhKwoEOXEwGFVDsGuCx233iazM2RhuxtTVOQn7dSl2QqFgBBZG8K l/50FA9y67SOd6hEP2YEB5xb4sUU+RiwdGcss= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=ac0A0h7TlSRYEDpGk9ZJCNL3mh/WhS/74xSFCh1pNIuwnA2CFeqNmxv9M4UWreaeL7 9FW/b1ArDJk5Ei7LrihyOB+tbm963LgClwrsW+lONiKwRprVfauBSyaZAXyFvBOKtttD 53Z9LZxRMtMkIhmoLvu/ibVwUKgkTGnhBHUqs= MIME-Version: 1.0 Received: by 10.236.111.38 with SMTP id v26mr3215092yhg.39.1292340725502; Tue, 14 Dec 2010 07:32:05 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.236.109.45 with HTTP; Tue, 14 Dec 2010 07:32:05 -0800 (PST) In-Reply-To: References: Date: Tue, 14 Dec 2010 16:32:05 +0100 X-Google-Sender-Auth: LNwDjeRbXe6SI8OWwFnloUvRLms Message-ID: From: Attilio Rao To: "Arno J. Klaassen" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 15:54:28 -0000 2010/12/10 Arno J. Klaassen : > > Hello, > > just FYI that on an 8-way Tyan S3992-E based box, a reboot under > 8.2-PRERELEASE (in fact, 8-stable since quite a while) makes the box > freeze, whilst the same thing under -current works OK. > > For info the end of console output in both cases as well as dmesg.boot > for -current. > > Feel free to contact me for more info or test patches. Hello Arno, I'd need you do the following things: - Compile a new kernel including this patch: http://www.freebsd.org/~attilio/diagno-stable8.diff and including the kernel config options KDB, DDB, DIAGNOSTIC and WITNESS. Please accurately skip, if present in your config file, options WITNESS_SKIPSPIN and KDB_UNATTENDED. These options could make the deadlock not visible anymore, at some extent. You may repeat a lot of times the reboot in order to try to get something but if you can't reproduce it just let me know. - When the kernel deadlocks, this time, after a while it should be able to resolve the deadlock alone. If that happens you will see the DDB prompt. At the ddb prompt type the following commands: db> ps db> show allpcpu db> allt db> show alllocks Note that this is quite a big output and you'd need a serial console to log it. If you can't arrange serial connections, I'll tell you what informations I need to specifically check and you may annotate someway and reply to me (the full logs would be valuable, but it is better than nothing). Are the instructions clear? Let me know if you have any question. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 16:36:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 366561065679 for ; Tue, 14 Dec 2010 16:36:56 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id DC4E48FC20 for ; Tue, 14 Dec 2010 16:36:55 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PSXrw-0000Py-7u for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 17:36:52 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Dec 2010 17:36:52 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Dec 2010 17:36:52 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Tue, 14 Dec 2010 17:36:36 +0100 Lines: 35 Message-ID: References: <201012141727.41909.eugene@imedia.ru> <201012141819.47712.eugene@imedia.ru> <201012141829.17662.eugene@imedia.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: <201012141829.17662.eugene@imedia.ru> X-Enigmail-Version: 1.1.2 Cc: freebsd-questions@freebsd.org Subject: Re: 8.1-STABLE Unexpected XML: what does it mean? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 16:36:56 -0000 On 14/12/2010 16:29, Eugene Mitrofanov wrote: > On Tuesday 14 December 2010, Ivan Voras wrote: >> On 14/12/2010 16:19, Eugene Mitrofanov wrote: >>> >>> How can I locate this device? Also I dont understand why mdconfig > complains? >> >> Try examining the output of >> >> # sysctl -b kern.geom.confxml > > Here they are: > > > > FD > > > fd0 > 1 > > > r0w0e0 > fd0 > 1474560 > 512 > 18432 > 0 > > > Looks ok so far (except weird stripesize). Sorry, I have no idea what is broken here. Try updating and rebuilding world in case you have some rare corruption. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 16:43:37 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73AFD106566B; Tue, 14 Dec 2010 16:43:37 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 570358FC15; Tue, 14 Dec 2010 16:43:35 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA18923; Tue, 14 Dec 2010 18:43:25 +0200 (EET) (envelope-from avg@freebsd.org) Message-ID: <4D079EAC.8090700@freebsd.org> Date: Tue, 14 Dec 2010 18:43:24 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Eugene Mitrofanov References: <201012141727.41909.eugene@imedia.ru> In-Reply-To: <201012141727.41909.eugene@imedia.ru> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org, Ivan Voras Subject: Re: 8.1-STABLE Unexpected XML: what does it mean? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 16:43:37 -0000 on 14/12/2010 16:27 Eugene Mitrofanov said the following: > Hi > > I observe the very strange message while run a lot of commands: > > root@beaver:eugene# glabel status > Unexpected XML: name=stripesize data="18432" > Unexpected XML: name=stripeoffset data="0" > Unexpected XML: name=stripesize data="18432" > Unexpected XML: name=stripeoffset data="0" > Name Status Components > iso9660/CDROM N/A acd0 > > root@beaver:eugene# mdconfig -l > Unexpected XML: name=stripesize data="18432" > Unexpected XML: name=stripeoffset data="0" > > root@beaver:eugene# gmirror status > Unexpected XML: name=stripesize data="18432" > Unexpected XML: name=stripeoffset data="0" > gmirror: Command 'status' not available. > > What subsystem prints them? How can I fix it? I'd hazard a guess that either your userland and kernel are out of sync or something like that is taking place. The messages come from libgeom and they mean it doesn't understand those "stripe*" properties. P.S. geom@ is often the best mailing list for geom issues. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 19:41:17 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBE9C1065672 for ; Tue, 14 Dec 2010 19:41:17 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 850688FC0A for ; Tue, 14 Dec 2010 19:41:17 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 6684573098; Tue, 14 Dec 2010 20:35:50 +0100 (CET) Date: Tue, 14 Dec 2010 20:35:50 +0100 From: Luigi Rizzo To: stable@freebsd.org Message-ID: <20101214193550.GA88466@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: how to access the SOL (Serial over Lan) port in FreeBSD ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 19:41:17 -0000 Hi, i recently bought two motherboards with Intel AMT support, a remote management tool which among other things implements Serial Over Lan (SOL) -- which seems to be accessible via TCP port 16994 I have enabled the feature in the bios and built a client (amtterm, see http://dl.bytesex.org/releases/amtterm/ ) which does connect to the port, but there is no data. Especially, on the FreeBSD side i see no "uart" device associated with the SOL port, only uart0 which is the physical serial port on board. Any idea on how to make the SOL port visible ? I am using a stock 8.2-beta kernel for amd64, tried to load ipmi but it makes no difference. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 20:43:02 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBBA7106566B for ; Tue, 14 Dec 2010 20:43:02 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221]) by mx1.freebsd.org (Postfix) with ESMTP id ADF048FC08 for ; Tue, 14 Dec 2010 20:43:01 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id oBEKOlX7058867; Wed, 15 Dec 2010 02:24:47 +0600 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <4D07D28A.8010301@rdtc.ru> Date: Wed, 15 Dec 2010 02:24:42 +0600 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.1.10) Gecko/20100712 Thunderbird/3.0.5 MIME-Version: 1.0 To: Luigi Rizzo References: <20101214193550.GA88466@onelab2.iet.unipi.it> In-Reply-To: <20101214193550.GA88466@onelab2.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: how to access the SOL (Serial over Lan) port in FreeBSD ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 20:43:02 -0000 On 15.12.2010 01:35, Luigi Rizzo wrote: > i recently bought two motherboards with Intel AMT support, > a remote management tool which among other things implements > Serial Over Lan (SOL) -- which seems to be accessible > via TCP port 16994 > > I have enabled the feature in the bios and built a client > (amtterm, see http://dl.bytesex.org/releases/amtterm/ ) > which does connect to the port, but there is no data. > > Especially, on the FreeBSD side i see no "uart" device > associated with the SOL port, only uart0 which is the > physical serial port on board. > > Any idea on how to make the SOL port visible ? > I am using a stock 8.2-beta kernel for amd64, > tried to load ipmi but it makes no difference. Today I successfully tested IPMI 2.0 card integrated within SuperMicro server. For server side, I've got /dev/ttyu0 as first physical port, /dev/ttyu1 as second and /dev/ttyu2 for SOL port automatically at boot time. Open request for /dev/ttyu2 locks waiting for DCD until I use ipmitool shell at remote workstation and command 'sol activate' in the shell. It gave me clean serial channel and I've successfully got getty login prompt, logged in, run Midnight Commander (TERM=xterm) without a problem. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 21:14:27 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D49CA106566B for ; Tue, 14 Dec 2010 21:14:27 +0000 (UTC) (envelope-from ptyll@nitronet.pl) Received: from mail.nitronet.pl (smtp.nitronet.pl [195.90.106.27]) by mx1.freebsd.org (Postfix) with ESMTP id 941C88FC13 for ; Tue, 14 Dec 2010 21:14:27 +0000 (UTC) Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PSbde-000I8Y-9t for stable@freebsd.org; Tue, 14 Dec 2010 21:38:22 +0100 Date: Tue, 14 Dec 2010 21:38:16 +0100 From: Pawel Tyll X-Priority: 3 (Normal) Message-ID: <1893986912.20101214213816@nitronet.pl> To: Luigi Rizzo In-Reply-To: <20101214193550.GA88466@onelab2.iet.unipi.it> References: <20101214193550.GA88466@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Nitronet.pl X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: ptyll@nitronet.pl X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false Cc: stable@freebsd.org Subject: Re: how to access the SOL (Serial over Lan) port in FreeBSD ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 21:14:27 -0000 Hi Luigi, > i recently bought two motherboards with Intel AMT support, > a remote management tool which among other things implements > Serial Over Lan (SOL) -- which seems to be accessible > via TCP port 16994 > I have enabled the feature in the bios and built a client > (amtterm, see http://dl.bytesex.org/releases/amtterm/ ) > which does connect to the port, but there is no data. > Especially, on the FreeBSD side i see no "uart" device > associated with the SOL port, only uart0 which is the > physical serial port on board. > Any idea on how to make the SOL port visible ? > I am using a stock 8.2-beta kernel for amd64, > tried to load ipmi but it makes no difference. I'm using Intel servers with Intel motherboards, they are IPMI-capable and both LAN and SOL are implemented by bridging with onboard ethernet and serial port. After loading IPMI driver and configuring IPMI using ipmitool (/usr/ports/sysutils/ipmitool), SOL is accessible via built-in ssh shell that listens on IPMI IP, or ipmitool running from remote. No additional serial ports nor ethernet adapters are exposed to the system, and you cannot connect to IPMI IP from local machine. Cheers. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 21:19:00 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9A441065672 for ; Tue, 14 Dec 2010 21:19:00 +0000 (UTC) (envelope-from rwa@athabascau.ca) Received: from smtp.athabascau.ca (smtp.athabascau.ca [131.232.10.21]) by mx1.freebsd.org (Postfix) with ESMTP id 8EB738FC15 for ; Tue, 14 Dec 2010 21:19:00 +0000 (UTC) Received: from CONVERSION-DAEMON.local.athabascau.ca by local.athabascau.ca (PMDF V6.2-1x12 #31425) id <0LDF0F101PSP6Q@local.athabascau.ca> for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 13:19:38 -0700 (MST) Received: from auwow.bogons ([192.168.1.2]) by local.athabascau.ca (PMDF V6.2-1x12 #31425) with ESMTPSA id <0LDF0EVFPPSHA1@local.athabascau.ca> for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 13:19:37 -0700 (MST) Date: Tue, 14 Dec 2010 13:19:29 -0700 (MST) From: Ross Alexander In-reply-to: <20101211120033.DC0541065746@hub.freebsd.org> X-X-Sender: rwa@auwow.bogons To: freebsd-stable@freebsd.org Message-id: Organization: Athabasca University X-Envelope-from: rwa@athabascau.ca MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII; format=flowed User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) References: <20101211120033.DC0541065746@hub.freebsd.org> Subject: Re: umass: AutoSense failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 21:19:00 -0000 On Sat, 11 Dec 2010, Harad Weiss wrote > Message: 7 > Date: Fri, 10 Dec 2010 22:59:17 +0100 > From: Harald Weis > Subject: Re: umass: AutoSense failed > To: freebsd-stable@freebsd.org > Cc: Jeremy Chadwick > Message-ID: <20101210215917.GA2447@pollux.local.net> > Content-Type: text/plain; charset=us-ascii > > [big snip] > > The AutoSense failure occurs on two desktop computers, whether > motherboard or not, and on three laptops. As I said, all PC's > run 8.1-RELEASE. > What I do not know is whether the Sony DSC (Digital Still Camera) has > worked on 8.0-RELEASE. I didn't use it for some time, so I'm afraid > I never tried it on 8.x. > But I am sure it worked on all earlier releases. > In my original post I have forgotten to mention that I never had any > problems with all sorts of thumbdrives and USB disks. > Fortunately, I can read the 256MB CF memory of the DSC on an Ubuntu > laptop. > Could it possibly be a DSC hardware problem which is ignored by Ubuntu, > but not by FreeBSD? My Sony DSC camera did work under 8.0-RELEASE. It's a model DSC-W35. It's seeing the umass problem now, and has since 8.1-PRERELEASE afair. This fault is the same on i386 or amd64, intel or amd chipsets, USB 1.0 or 2.0, through hubs or straight off the m/b, etc.. I'm keeping a backup box (intel atom / i386) running 7.3-STABLE around specifically to work around the problem. I'd have said something eralier, but I've gotten used to small nits poppping up and then disappearing; this one is dragging along :( sincerest regards, Ross -- Ross Alexander, (780) 675-6823 / (780) 689-0749, rwa@athabascau.ca "Always do right. This will gratify some people, and astound the rest." -- Samuel Clemens __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 21:39:34 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B995C106564A for ; Tue, 14 Dec 2010 21:39:34 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from thalia-smout.broadpark.no (thalia-smout.broadpark.no [80.202.8.21]) by mx1.freebsd.org (Postfix) with ESMTP id 706C68FC18 for ; Tue, 14 Dec 2010 21:39:34 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from ignis-smin.broadpark.no ([80.202.8.11]) by thalia-smout.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with ESMTP id <0LDF00HP4QPW5230@thalia-smout.broadpark.no> for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 21:39:32 +0100 (CET) Received: from kg-v2.kg4.no ([84.48.120.77]) by ignis-smin.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with SMTP id <0LDF00GQSQPV8AJ0@ignis-smin.broadpark.no> for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 21:39:32 +0100 (CET) Date: Tue, 14 Dec 2010 21:39:31 +0100 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20101214213931.52e1ec86.torfinn.ingolfsen@broadpark.no> In-reply-to: <20101214193550.GA88466@onelab2.iet.unipi.it> References: <20101214193550.GA88466@onelab2.iet.unipi.it> X-Mailer: Sylpheed 3.0.3 (GTK+ 2.22.1; amd64-portbld-freebsd8.1) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: how to access the SOL (Serial over Lan) port in FreeBSD ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 21:39:34 -0000 On Tue, 14 Dec 2010 20:35:50 +0100 Luigi Rizzo wrote: > i recently bought two motherboards with Intel AMT support, > a remote management tool which among other things implements > Serial Over Lan (SOL) -- which seems to be accessible > via TCP port 16994 > > I have enabled the feature in the bios and built a client And configured it? See http://linux.die.net/man/7/amt-howto I know nothing about AMT (yet), but it looks interesting. HTH -- Torfinn From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 22:06:17 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5E82106564A for ; Tue, 14 Dec 2010 22:06:17 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 79A538FC16 for ; Tue, 14 Dec 2010 22:06:17 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 092C473098; Tue, 14 Dec 2010 23:00:38 +0100 (CET) Date: Tue, 14 Dec 2010 23:00:38 +0100 From: Luigi Rizzo To: Torfinn Ingolfsen Message-ID: <20101214220038.GA89625@onelab2.iet.unipi.it> References: <20101214193550.GA88466@onelab2.iet.unipi.it> <20101214213931.52e1ec86.torfinn.ingolfsen@broadpark.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101214213931.52e1ec86.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: how to access the SOL (Serial over Lan) port in FreeBSD ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 22:06:17 -0000 On Tue, Dec 14, 2010 at 09:39:31PM +0100, Torfinn Ingolfsen wrote: > On Tue, 14 Dec 2010 20:35:50 +0100 > Luigi Rizzo wrote: > > > i recently bought two motherboards with Intel AMT support, > > a remote management tool which among other things implements > > Serial Over Lan (SOL) -- which seems to be accessible > > via TCP port 16994 > > > > I have enabled the feature in the bios and built a client > > And configured it? > See http://linux.die.net/man/7/amt-howto yes, some of the other features do work (power and status, accessible through the web on port 16992 or using amttool). The terminal support is apparently enabled (amtterm does the negotiation, and if i disable it then port 16994 is not accessible). cheers luigi From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 22:25:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51F19106564A for ; Tue, 14 Dec 2010 22:25:50 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 9A2C18FC17 for ; Tue, 14 Dec 2010 22:25:49 +0000 (UTC) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id oBEMPl88042282 ; Tue, 14 Dec 2010 23:25:47 +0100 (CET) X-Ids: 168 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.14.3/8.14.3) with ESMTP id oBEMOsUv090493; Tue, 14 Dec 2010 23:24:54 +0100 (CET) (envelope-from arno@heho.snv.jussieu.fr) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.14.3/8.14.3/Submit) id oBEMOrLo090490; Tue, 14 Dec 2010 23:24:53 +0100 (CET) (envelope-from arno) To: Andriy Gapon From: "Arno J. Klaassen" References: <20101210100230.GA25419@icarus.home.lan> <59F3B2944C764A36B912E6B50B4D4DD9@multiplay.co.uk> <20101214003825.GA13836@icarus.home.lan> <4D0777B3.5020208@freebsd.org> Date: Tue, 14 Dec 2010 23:24:52 +0100 In-Reply-To: <4D0777B3.5020208@freebsd.org> (Andriy Gapon's message of "Tue\, 14 Dec 2010 15\:57\:07 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Miltered: at jchkmail.jussieu.fr with ID 4D07EEEB.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4D07EEEB.000/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ Cc: freebsd-stable@freebsd.org, Steven Hartland , Jeremy Chadwick Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 22:25:50 -0000 Andriy Gapon writes: > on 14/12/2010 02:38 Jeremy Chadwick said the following: >> 1) > [snip] >> Also try dropping to the >> debugger via serial console (serial break) or VGA (Ctrl-Alt-Esc). > > This is a good advice. may be ;-) but the box realy freezes, no way to drop into the debugger nor via serial (ALT_BREAK_TO_DEBUGGER compiled as well) nor via VGA/PS2 ... realy frozen Arno From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 22:48:16 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E4F4106566C for ; Tue, 14 Dec 2010 22:48:16 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by mx1.freebsd.org (Postfix) with ESMTP id 06C0E8FC19 for ; Tue, 14 Dec 2010 22:48:15 +0000 (UTC) Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA11.westchester.pa.mail.comcast.net with comcast id j9k61f0030EZKEL5BAoGU0; Tue, 14 Dec 2010 22:48:16 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta01.westchester.pa.mail.comcast.net with comcast id jAoC1f00H3LrwQ23MAoDq2; Tue, 14 Dec 2010 22:48:14 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id D60E89B427; Tue, 14 Dec 2010 14:48:09 -0800 (PST) Date: Tue, 14 Dec 2010 14:48:09 -0800 From: Jeremy Chadwick To: "Arno J. Klaassen" Message-ID: <20101214224809.GA53593@icarus.home.lan> References: <20101210100230.GA25419@icarus.home.lan> <59F3B2944C764A36B912E6B50B4D4DD9@multiplay.co.uk> <20101214003825.GA13836@icarus.home.lan> <4D0777B3.5020208@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, Steven Hartland , Andriy Gapon Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 22:48:16 -0000 On Tue, Dec 14, 2010 at 11:24:52PM +0100, Arno J. Klaassen wrote: > Andriy Gapon writes: > > > on 14/12/2010 02:38 Jeremy Chadwick said the following: > >> 1) > > [snip] > >> Also try dropping to the > >> debugger via serial console (serial break) or VGA (Ctrl-Alt-Esc). > > > > This is a good advice. > > may be ;-) but the box realy freezes, no way to drop into the debugger > nor via serial (ALT_BREAK_TO_DEBUGGER compiled as well) nor > via VGA/PS2 ... realy frozen Bummer. It sounds like it's a regression of some kind, since your original mail stated this problem has been happening for you on RELENG_8 (8.x) for quite some time. (I have to assume it didn't happen for you at all on 7.3 or prior). Would it be possible for you to dedicate some time narrowing down when the problem was introduced? A good starting point might be to try 8.0-RELEASE and then 8.1-RELEASE (just download + burn + boot livefs images and try that). If it happens on 8.1-RELEASE but not 8.0, then we've at least narrowed down the timeframe. It might also be worth trying the same with 7.3-RELEASE vs. 7.4-BETA1 (which just came out) see if the same bug was introduced there as result of an MFC. Otherwise, numerous csups with different date= strings in your supfiles and multiple buildworld/kernel/installs would be required. I would probably pick intervals of 4 months at first. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 23:08:36 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87E0F106566B; Tue, 14 Dec 2010 23:08:36 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 1CD8A8FC0A; Tue, 14 Dec 2010 23:08:35 +0000 (UTC) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id oBEN8Xaj050499 ; Wed, 15 Dec 2010 00:08:34 +0100 (CET) X-Ids: 165 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.14.3/8.14.3) with ESMTP id oBEN7wGw090862; Wed, 15 Dec 2010 00:07:58 +0100 (CET) (envelope-from arno@heho.snv.jussieu.fr) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.14.3/8.14.3/Submit) id oBEN7vKI090859; Wed, 15 Dec 2010 00:07:57 +0100 (CET) (envelope-from arno) To: Jeremy Chadwick From: "Arno J. Klaassen" References: <20101210100230.GA25419@icarus.home.lan> <59F3B2944C764A36B912E6B50B4D4DD9@multiplay.co.uk> <20101214003825.GA13836@icarus.home.lan> <4D0777B3.5020208@freebsd.org> <20101214224809.GA53593@icarus.home.lan> Date: Wed, 15 Dec 2010 00:07:57 +0100 In-Reply-To: <20101214224809.GA53593@icarus.home.lan> (Jeremy Chadwick's message of "Tue\, 14 Dec 2010 14\:48\:09 -0800") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Miltered: at jchkmail.jussieu.fr with ID 4D07F8F1.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4D07F8F1.002/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ Cc: Attilio Rao , freebsd-stable@freebsd.org, Steven Hartland , Andriy Gapon Subject: Re: 8.2-PRERELEASE freezing on reboot (-current OK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Dec 2010 23:08:36 -0000 Jeremy Chadwick writes: > On Tue, Dec 14, 2010 at 11:24:52PM +0100, Arno J. Klaassen wrote: >> Andriy Gapon writes: >> >> > on 14/12/2010 02:38 Jeremy Chadwick said the following: >> >> 1) >> > [snip] >> >> Also try dropping to the >> >> debugger via serial console (serial break) or VGA (Ctrl-Alt-Esc). >> > >> > This is a good advice. >> >> may be ;-) but the box realy freezes, no way to drop into the debugger >> nor via serial (ALT_BREAK_TO_DEBUGGER compiled as well) nor >> via VGA/PS2 ... realy frozen > > Bummer. It sounds like it's a regression of some kind, since your > original mail stated this problem has been happening for you on RELENG_8 > (8.x) for quite some time. (I have to assume it didn't happen for you > at all on 7.3 or prior). yop, build this box with some 7.X; it's a spare/development/test one, doesn't get that much attention when problems, nor frequent reboots. I noticed this problem at least some months ago (I track -stable on it when I have time/envy) and adopted the anti-Murphy attitude (wait for -RELEASE and recheck) > Would it be possible for you to dedicate some time narrowing down when > the problem was introduced? > > A good starting point might be to try 8.0-RELEASE and then 8.1-RELEASE > (just download + burn + boot livefs images and try that). If it happens > on 8.1-RELEASE but not 8.0, then we've at least narrowed down the > timeframe. I answered Attilio Rao in private on a patch he sent me in order to get at least more info. I will test and let you, and list, know the results. > It might also be worth trying the same with 7.3-RELEASE vs. 7.4-BETA1 > (which just came out) see if the same bug was introduced there as result > of an MFC. > > Otherwise, numerous csups with different date= strings in your supfiles > and multiple buildworld/kernel/installs would be required. I would > probably pick intervals of 4 months at first. Quite sure many 8-XXX worlds worked great on this box including reboots, I will find the date window when things went wrong. Merci, Arno From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 00:38:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D87C106564A for ; Wed, 15 Dec 2010 00:38:51 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id 43DAA8FC08 for ; Wed, 15 Dec 2010 00:38:50 +0000 (UTC) Received: (qmail 6395 invoked by uid 89); 15 Dec 2010 00:38:50 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 15 Dec 2010 00:38:50 -0000 From: Dan Allen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 14 Dec 2010 17:38:49 -0700 Message-Id: To: FreeBSD-STABLE Mailing List Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Subject: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 00:38:51 -0000 Recently my network connection now is setup AFTER ntpd is launched = rather than before. So when ntpd starts there is no net connection and it gives up. I read /usr/src/UPDATING but nothing is mentioned about a change in boot = order. Any ideas? Thanks, Dan Allen From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 00:46:12 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4DDD1065670 for ; Wed, 15 Dec 2010 00:46:12 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout026.mac.com (asmtpout026.mac.com [17.148.16.101]) by mx1.freebsd.org (Postfix) with ESMTP id 9B4E68FC14 for ; Wed, 15 Dec 2010 00:46:12 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp026.mac.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 64bit)) with ESMTPSA id <0LDG00IXG24Y3F30@asmtp026.mac.com> for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 16:46:10 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1010190000 definitions=main-1012140187 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2010-12-14_14:2010-12-14, 2010-12-14, 1970-01-01 signatures=0 From: Chuck Swiger In-reply-to: Date: Tue, 14 Dec 2010 16:46:10 -0800 Message-id: <7B9EB743-7C87-42AF-85DE-C05352E4A429@mac.com> References: To: Dan Allen X-Mailer: Apple Mail (2.1082) Cc: FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 00:46:12 -0000 On Dec 14, 2010, at 4:38 PM, Dan Allen wrote: > Recently my network connection now is setup AFTER ntpd is launched rather than before. > > So when ntpd starts there is no net connection and it gives up. Change the REQUIRE line in /etc/rc.d/ntpd to indicate whatever dependency you need to have so that your network connection is up before ntpd tries to run. "man rcorder" is informative.... Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 00:46:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D5F51065673 for ; Wed, 15 Dec 2010 00:46:56 +0000 (UTC) (envelope-from kpotter@cap-press.com) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.freebsd.org (Postfix) with SMTP id A91248FC25 for ; Wed, 15 Dec 2010 00:46:55 +0000 (UTC) Received: (qmail 94368 invoked by uid 0); 15 Dec 2010 00:20:13 -0000 Received: from 209.68.2.28 (HELO www.cap-press.com) (209.68.2.28) by relay01.pair.com with SMTP; 15 Dec 2010 00:20:13 -0000 X-pair-Authenticated: 209.68.2.28 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_97b141643bab6cbf973d27e216a96e96" Date: Tue, 14 Dec 2010 19:20:13 -0500 From: Keith Potter To: , Message-ID: <4596b291f711df77f624773afad3811d@cap-press.com> X-Sender: kpotter@cap-press.com User-Agent: Roundcube Webmail/0.4 Cc: Subject: 8.2-PRERELEASE, ZFS Slows Machine to a Crawl X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 00:46:56 -0000 --=_97b141643bab6cbf973d27e216a96e96 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8; format=flowed Greetings! We are setting up a new server using 8.2-PRERELEASE (as of 12/12/10) and we are encountering performance issues with ZFS. The system boots from a ZFS volume consisting of two Western Digital 2TB RE4 drives in a ZFS mirror. The rest of the system consists of an Intel-based Tyan motherboard, 2 x Xeon 5520, and 12GB ECC ram. I have attached the dmesg output to this email as a text file for more hardware details. The performance degradation occurs when copying large amounts of data to or from the ZFS volume. It happens both when copying from the network onto the volume, and when copying from the volume back onto itself. When copying a large (22GB) file, the disk throughput according to `zpool iostat -v` is only about 30-35 MB/s, but yet the system is extremely slow interactively. SSH-ing into the machine takes a good 5-10 seconds just to get a password prompt, and running simple commands like `ls` and `top` takes several seconds to respond. Compression is enabled for some volumes in the pool, but not for any of the volumes that have been copied to or from. CPU load stays very low (<5%) during all of this. We have tried tuning some of the ZFS paramters. The default for vfs.zfs.arc_max was about 11GB, but we have tried setting it as low as 400MB with no change. vfs.numvnodes has typically been below 10000 during all of this, but even such, we have toyed with the kern.maxvnodes parameter (ranging from 10000 to 500000) with no effect. The only thing that had any real effect was setting vfs.zfs.txg.write_limit_override to 500000000 or so, which helped slightly, but the system was still very slow to respond. When not under IO load the system is very fast, running a buildworld in 13 minutes. Unfortunately, I am not sure whether the issue existed under 8.1-RELEASE because we did not copy any large files before it was updated. I've attached the outputs of `zpool status` and `zpool iostat -v` below: pool: zroot state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 errors: No known data errors pool used avail read write read write ------------- ----- ----- ----- ----- ----- ----- zroot 240G 1.58T 0 1 6.40K 3.18K mirror 240G 1.58T 0 1 6.40K 3.18K gpt/disk0 - - 0 0 5.64K 3.21K gpt/disk1 - - 0 0 4.75K 3.21K ------------- ----- ----- ----- ----- ----- ----- I greatly appreciate any input! --=_97b141643bab6cbf973d27e216a96e96 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=UTF-8; name=dmesg.txt Content-Disposition: attachment; filename=dmesg.txt Y2FtOiB1c2luZyBtaW5pbXVtIHNjc2lfZGVsYXkgKDEwMG1zKQ0KQ29weXJpZ2h0IChjKSAxOTky LTIwMTAgVGhlIEZyZWVCU0QgUHJvamVjdC4NCkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4 MywgMTk4NiwgMTk4OCwgMTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KICAgICAgICBUaGUg UmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmlnaHRzIHJlc2Vy dmVkLg0KRnJlZUJTRCBpcyBhIHJlZ2lzdGVyZWQgdHJhZGVtYXJrIG9mIFRoZSBGcmVlQlNEIEZv dW5kYXRpb24uDQpGcmVlQlNEIDguMi1QUkVSRUxFQVNFICMwOiBTdW4gRGVjIDEyIDE2OjA2OjQ4 IEVTVCAyMDEwDQogICAgcm9vdEBibGFoOi91c3Ivb2JqL3Vzci9zcmMvc3lzL1hFT04gYW1kNjQN ClRpbWVjb3VudGVyICJpODI1NCIgZnJlcXVlbmN5IDExOTMxODIgSHogcXVhbGl0eSAwDQpDUFU6 IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAgICBFNTUyMCAgQCAyLjI3R0h6ICgyMjY2Ljc2 LU1IeiBLOC1jbGFzcyBDUFUpDQogIE9yaWdpbiA9ICJHZW51aW5lSW50ZWwiICBJZCA9IDB4MTA2 YTUgIEZhbWlseSA9IDYgIE1vZGVsID0gMWEgIFN0ZXBwaW5nID0gNQ0KICBGZWF0dXJlcz0weGJm ZWJmYmZmPEZQVSxWTUUsREUsUFNFLFRTQyxNU1IsUEFFLE1DRSxDWDgsQVBJQyxTRVAsTVRSUixQ R0UsTUNBLENNT1YsUEFULFBTRTM2LENMRkxVU0gsRFRTLEFDUEksTU1YLEZYU1IsU1NFLFNTRTIs U1MsSFRULFRNLFBCRT4NCiAgRmVhdHVyZXMyPTB4OWNlM2JkPFNTRTMsRFRFUzY0LE1PTixEU19D UEwsVk1YLEVTVCxUTTIsU1NTRTMsQ1gxNix4VFBSLFBEQ00sRENBLFNTRTQuMSxTU0U0LjIsUE9Q Q05UPg0KICBBTUQgRmVhdHVyZXM9MHgyODEwMDgwMDxTWVNDQUxMLE5YLFJEVFNDUCxMTT4NCiAg QU1EIEZlYXR1cmVzMj0weDE8TEFIRj4NCiAgVFNDOiBQLXN0YXRlIGludmFyaWFudA0KcmVhbCBt ZW1vcnkgID0gMTI4ODQ5MDE4ODggKDEyMjg4IE1CKQ0KYXZhaWwgbWVtb3J5ID0gMTIzNzAxNjk4 NTYgKDExNzk3IE1CKQ0KQUNQSSBBUElDIFRhYmxlOiA8MDMxNzEwIEFQSUMxNjE3Pg0KRnJlZUJT RC9TTVA6IE11bHRpcHJvY2Vzc29yIFN5c3RlbSBEZXRlY3RlZDogMTYgQ1BVcw0KRnJlZUJTRC9T TVA6IDIgcGFja2FnZShzKSB4IDQgY29yZShzKSB4IDIgU01UIHRocmVhZHMNCiBjcHUwIChCU1Ap OiBBUElDIElEOiAgMA0KIGNwdTEgKEFQKTogQVBJQyBJRDogIDENCiBjcHUyIChBUCk6IEFQSUMg SUQ6ICAyDQogY3B1MyAoQVApOiBBUElDIElEOiAgMw0KIGNwdTQgKEFQKTogQVBJQyBJRDogIDQN CiBjcHU1IChBUCk6IEFQSUMgSUQ6ICA1DQogY3B1NiAoQVApOiBBUElDIElEOiAgNg0KIGNwdTcg KEFQKTogQVBJQyBJRDogIDcNCiBjcHU4IChBUCk6IEFQSUMgSUQ6IDE2DQogY3B1OSAoQVApOiBB UElDIElEOiAxNw0KIGNwdTEwIChBUCk6IEFQSUMgSUQ6IDE4DQogY3B1MTEgKEFQKTogQVBJQyBJ RDogMTkNCiBjcHUxMiAoQVApOiBBUElDIElEOiAyMA0KIGNwdTEzIChBUCk6IEFQSUMgSUQ6IDIx DQogY3B1MTQgKEFQKTogQVBJQyBJRDogMjINCiBjcHUxNSAoQVApOiBBUElDIElEOiAyMw0KaW9h cGljMCA8VmVyc2lvbiAyLjA+IGlycXMgMC0yMyBvbiBtb3RoZXJib2FyZA0KaW9hcGljMSA8VmVy c2lvbiAyLjA+IGlycXMgMjQtNDcgb24gbW90aGVyYm9hcmQNCmtiZDEgYXQga2JkbXV4MA0KYWNw aTA6IDwwMzE3MTAgWFNEVDE2MTc+IG9uIG1vdGhlcmJvYXJkDQphY3BpMDogW0lUSFJFQURdDQph Y3BpMDogUG93ZXIgQnV0dG9uIChmaXhlZCkNCmFjcGkwOiByZXNlcnZhdGlvbiBvZiAwLCBhMDAw MCAoMykgZmFpbGVkDQphY3BpMDogcmVzZXJ2YXRpb24gb2YgMTAwMDAwLCBiZmYwMDAwMCAoMykg ZmFpbGVkDQpUaW1lY291bnRlciAiQUNQSS1mYXN0IiBmcmVxdWVuY3kgMzU3OTU0NSBIeiBxdWFs aXR5IDEwMDANCmFjcGlfdGltZXIwOiA8MjQtYml0IHRpbWVyIGF0IDMuNTc5NTQ1TUh6PiBwb3J0 IDB4ODA4LTB4ODBiIG9uIGFjcGkwDQpjcHUwOiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpBQ1BJIFdh cm5pbmc6IEluY29ycmVjdCBjaGVja3N1bSBpbiB0YWJsZSBbT0VNQl0gLSAweEFELCBzaG91bGQg YmUgMHhBQSAoMjAxMDEwMTMvdGJ1dGlscy0zNTQpDQpjcHUxOiA8QUNQSSBDUFU+IG9uIGFjcGkw DQpjcHUyOiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpjcHUzOiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpj cHU0OiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpjcHU1OiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpjcHU2 OiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpjcHU3OiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpjcHU4OiA8 QUNQSSBDUFU+IG9uIGFjcGkwDQpjcHU5OiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpjcHUxMDogPEFD UEkgQ1BVPiBvbiBhY3BpMA0KY3B1MTE6IDxBQ1BJIENQVT4gb24gYWNwaTANCmNwdTEyOiA8QUNQ SSBDUFU+IG9uIGFjcGkwDQpjcHUxMzogPEFDUEkgQ1BVPiBvbiBhY3BpMA0KY3B1MTQ6IDxBQ1BJ IENQVT4gb24gYWNwaTANCmNwdTE1OiA8QUNQSSBDUFU+IG9uIGFjcGkwDQpwY2liMDogPEFDUEkg SG9zdC1QQ0kgYnJpZGdlPiBwb3J0IDB4Y2Y4LTB4Y2ZmIG9uIGFjcGkwDQpwY2kwOiA8QUNQSSBQ Q0kgYnVzPiBvbiBwY2liMA0KcGNpYjE6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBhdCBkZXZpY2Ug MS4wIG9uIHBjaTANCnBjaTEwOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liMQ0KcGNpYjI6IDxBQ1BJ IFBDSS1QQ0kgYnJpZGdlPiBhdCBkZXZpY2UgMy4wIG9uIHBjaTANCnBjaTk6IDxBQ1BJIFBDSSBi dXM+IG9uIHBjaWIyDQpwY2liMzogPEFDUEkgUENJLVBDSSBicmlkZ2U+IGF0IGRldmljZSA3LjAg b24gcGNpMA0KcGNpODogPEFDUEkgUENJIGJ1cz4gb24gcGNpYjMNCnBjaWI0OiA8UENJLVBDSSBi cmlkZ2U+IGF0IGRldmljZSA4LjAgb24gcGNpMA0KcGNpNzogPFBDSSBidXM+IG9uIHBjaWI0DQpw Y2liNTogPFBDSS1QQ0kgYnJpZGdlPiBhdCBkZXZpY2UgOS4wIG9uIHBjaTANCnBjaTY6IDxQQ0kg YnVzPiBvbiBwY2liNQ0KcGNpYjY6IDxQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDEwLjAgb24g cGNpMA0KcGNpNTogPFBDSSBidXM+IG9uIHBjaWI2DQpwY2kwOiA8YmFzZSBwZXJpcGhlcmFsLCBp bnRlcnJ1cHQgY29udHJvbGxlcj4gYXQgZGV2aWNlIDIwLjAgKG5vIGRyaXZlciBhdHRhY2hlZCkN CnBjaTA6IDxiYXNlIHBlcmlwaGVyYWwsIGludGVycnVwdCBjb250cm9sbGVyPiBhdCBkZXZpY2Ug MjAuMSAobm8gZHJpdmVyIGF0dGFjaGVkKQ0KcGNpMDogPGJhc2UgcGVyaXBoZXJhbCwgaW50ZXJy dXB0IGNvbnRyb2xsZXI+IGF0IGRldmljZSAyMC4yIChubyBkcml2ZXIgYXR0YWNoZWQpDQpwY2kw OiA8YmFzZSBwZXJpcGhlcmFsLCBpbnRlcnJ1cHQgY29udHJvbGxlcj4gYXQgZGV2aWNlIDIwLjMg KG5vIGRyaXZlciBhdHRhY2hlZCkNCnBjaTA6IDxiYXNlIHBlcmlwaGVyYWw+IGF0IGRldmljZSAy Mi4wIChubyBkcml2ZXIgYXR0YWNoZWQpDQpwY2kwOiA8YmFzZSBwZXJpcGhlcmFsPiBhdCBkZXZp Y2UgMjIuMSAobm8gZHJpdmVyIGF0dGFjaGVkKQ0KcGNpMDogPGJhc2UgcGVyaXBoZXJhbD4gYXQg ZGV2aWNlIDIyLjIgKG5vIGRyaXZlciBhdHRhY2hlZCkNCnBjaTA6IDxiYXNlIHBlcmlwaGVyYWw+ IGF0IGRldmljZSAyMi4zIChubyBkcml2ZXIgYXR0YWNoZWQpDQpwY2kwOiA8YmFzZSBwZXJpcGhl cmFsPiBhdCBkZXZpY2UgMjIuNCAobm8gZHJpdmVyIGF0dGFjaGVkKQ0KcGNpMDogPGJhc2UgcGVy aXBoZXJhbD4gYXQgZGV2aWNlIDIyLjUgKG5vIGRyaXZlciBhdHRhY2hlZCkNCnBjaTA6IDxiYXNl IHBlcmlwaGVyYWw+IGF0IGRldmljZSAyMi42IChubyBkcml2ZXIgYXR0YWNoZWQpDQpwY2kwOiA8 YmFzZSBwZXJpcGhlcmFsPiBhdCBkZXZpY2UgMjIuNyAobm8gZHJpdmVyIGF0dGFjaGVkKQ0KdWhj aTA6IDxJbnRlbCA4MjgwMUpJIChJQ0gxMCkgVVNCIGNvbnRyb2xsZXIgVVNCLUQ+IHBvcnQgMHg5 NDAwLTB4OTQxZiBpcnEgMTYgYXQgZGV2aWNlIDI2LjAgb24gcGNpMA0KdWhjaTA6IFtJVEhSRUFE XQ0KdWhjaTA6IExlZ1N1cCA9IDB4MmYwMA0KdXNidXMwOiA8SW50ZWwgODI4MDFKSSAoSUNIMTAp IFVTQiBjb250cm9sbGVyIFVTQi1EPiBvbiB1aGNpMA0KdWhjaTE6IDxJbnRlbCA4MjgwMUpJIChJ Q0gxMCkgVVNCIGNvbnRyb2xsZXIgVVNCLUU+IHBvcnQgMHg5NDgwLTB4OTQ5ZiBpcnEgMjEgYXQg ZGV2aWNlIDI2LjEgb24gcGNpMA0KdWhjaTE6IFtJVEhSRUFEXQ0KdWhjaTE6IExlZ1N1cCA9IDB4 MmYwMA0KdXNidXMxOiA8SW50ZWwgODI4MDFKSSAoSUNIMTApIFVTQiBjb250cm9sbGVyIFVTQi1F PiBvbiB1aGNpMQ0KdWhjaTI6IDxJbnRlbCA4MjgwMUpJIChJQ0gxMCkgVVNCIGNvbnRyb2xsZXIg VVNCLUY+IHBvcnQgMHg5ODAwLTB4OTgxZiBpcnEgMTkgYXQgZGV2aWNlIDI2LjIgb24gcGNpMA0K dWhjaTI6IFtJVEhSRUFEXQ0KdWhjaTI6IExlZ1N1cCA9IDB4MmYwMA0KdXNidXMyOiA8SW50ZWwg ODI4MDFKSSAoSUNIMTApIFVTQiBjb250cm9sbGVyIFVTQi1GPiBvbiB1aGNpMg0KZWhjaTA6IDxJ bnRlbCA4MjgwMUpJIChJQ0gxMCkgVVNCIDIuMCBjb250cm9sbGVyIFVTQi1CPiBtZW0gMHhmYmNm NjAwMC0weGZiY2Y2M2ZmIGlycSAxOCBhdCBkZXZpY2UgMjYuNyBvbiBwY2kwDQplaGNpMDogW0lU SFJFQURdDQp1c2J1czM6IEVIQ0kgdmVyc2lvbiAxLjANCnVzYnVzMzogPEludGVsIDgyODAxSkkg KElDSDEwKSBVU0IgMi4wIGNvbnRyb2xsZXIgVVNCLUI+IG9uIGVoY2kwDQpwY2liNzogPEFDUEkg UENJLVBDSSBicmlkZ2U+IGlycSAxNyBhdCBkZXZpY2UgMjguMCBvbiBwY2kwDQpwY2k0OiA8QUNQ SSBQQ0kgYnVzPiBvbiBwY2liNw0KcGNpYjg6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBpcnEgMTcg YXQgZGV2aWNlIDI4LjQgb24gcGNpMA0KcGNpMzogPEFDUEkgUENJIGJ1cz4gb24gcGNpYjgNCmVt MDogPEludGVsKFIpIFBSTy8xMDAwIE5ldHdvcmsgQ29ubmVjdGlvbiA3LjEuOD4gcG9ydCAweGVj MDAtMHhlYzFmIG1lbSAweGZiZWUwMDAwLTB4ZmJlZmZmZmYsMHhmYmVkYzAwMC0weGZiZWRmZmZm IGlycSAxNiBhdCBkZXZpY2UgMC4wIG9uIHBjaTMNCmVtMDogVXNpbmcgTVNJWCBpbnRlcnJ1cHRz IHdpdGggMyB2ZWN0b3JzDQplbTA6IFtJVEhSRUFEXQ0KZW0wOiBbSVRIUkVBRF0NCmVtMDogW0lU SFJFQURdDQplbTA6IEV0aGVybmV0IGFkZHJlc3M6IDAwOmUwOjgxOmJhOmJmOmU3DQpwY2liOTog PEFDUEkgUENJLVBDSSBicmlkZ2U+IGlycSAxNiBhdCBkZXZpY2UgMjguNSBvbiBwY2kwDQpwY2ky OiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liOQ0KZW0xOiA8SW50ZWwoUikgUFJPLzEwMDAgTmV0d29y ayBDb25uZWN0aW9uIDcuMS44PiBwb3J0IDB4ZGMwMC0weGRjMWYgbWVtIDB4ZmJkZTAwMDAtMHhm YmRmZmZmZiwweGZiZGRjMDAwLTB4ZmJkZGZmZmYgaXJxIDE3IGF0IGRldmljZSAwLjAgb24gcGNp Mg0KZW0xOiBVc2luZyBNU0lYIGludGVycnVwdHMgd2l0aCAzIHZlY3RvcnMNCmVtMTogW0lUSFJF QURdDQplbTE6IFtJVEhSRUFEXQ0KZW0xOiBbSVRIUkVBRF0NCmVtMTogRXRoZXJuZXQgYWRkcmVz czogMDA6ZTA6ODE6YmE6YmY6ZTgNCnVoY2kzOiA8SW50ZWwgODI4MDFKSSAoSUNIMTApIFVTQiBj b250cm9sbGVyIFVTQi1BPiBwb3J0IDB4OTg4MC0weDk4OWYgaXJxIDIzIGF0IGRldmljZSAyOS4w IG9uIHBjaTANCnVoY2kzOiBbSVRIUkVBRF0NCnVoY2kzOiBMZWdTdXAgPSAweDJmMDANCnVzYnVz NDogPEludGVsIDgyODAxSkkgKElDSDEwKSBVU0IgY29udHJvbGxlciBVU0ItQT4gb24gdWhjaTMN CnVoY2k0OiA8SW50ZWwgODI4MDFKSSAoSUNIMTApIFVTQiBjb250cm9sbGVyIFVTQi1CPiBwb3J0 IDB4OWMwMC0weDljMWYgaXJxIDE5IGF0IGRldmljZSAyOS4xIG9uIHBjaTANCnVoY2k0OiBbSVRI UkVBRF0NCnVoY2k0OiBMZWdTdXAgPSAweDJmMDANCnVzYnVzNTogPEludGVsIDgyODAxSkkgKElD SDEwKSBVU0IgY29udHJvbGxlciBVU0ItQj4gb24gdWhjaTQNCnVoY2k1OiA8SW50ZWwgODI4MDFK SSAoSUNIMTApIFVTQiBjb250cm9sbGVyIFVTQi1DPiBwb3J0IDB4YTAwMC0weGEwMWYgaXJxIDE4 IGF0IGRldmljZSAyOS4yIG9uIHBjaTANCnVoY2k1OiBbSVRIUkVBRF0NCnVoY2k1OiBMZWdTdXAg PSAweDJmMDANCnVzYnVzNjogPEludGVsIDgyODAxSkkgKElDSDEwKSBVU0IgY29udHJvbGxlciBV U0ItQz4gb24gdWhjaTUNCmVoY2kxOiA8SW50ZWwgODI4MDFKSSAoSUNIMTApIFVTQiAyLjAgY29u dHJvbGxlciBVU0ItQT4gbWVtIDB4ZmJjZjgwMDAtMHhmYmNmODNmZiBpcnEgMjMgYXQgZGV2aWNl IDI5Ljcgb24gcGNpMA0KZWhjaTE6IFtJVEhSRUFEXQ0KdXNidXM3OiBFSENJIHZlcnNpb24gMS4w DQp1c2J1czc6IDxJbnRlbCA4MjgwMUpJIChJQ0gxMCkgVVNCIDIuMCBjb250cm9sbGVyIFVTQi1B PiBvbiBlaGNpMQ0KcGNpYjEwOiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDMwLjAg b24gcGNpMA0KcGNpMTogPEFDUEkgUENJIGJ1cz4gb24gcGNpYjEwDQp2Z2FwY2kwOiA8VkdBLWNv bXBhdGlibGUgZGlzcGxheT4gcG9ydCAweGNjMDAtMHhjYzdmIG1lbSAweGZiMDAwMDAwLTB4ZmI3 ZmZmZmYsMHhmYWZlMDAwMC0weGZhZmZmZmZmIGlycSAxNiBhdCBkZXZpY2UgMC4wIG9uIHBjaTEN CmlzYWIwOiA8UENJLUlTQSBicmlkZ2U+IGF0IGRldmljZSAzMS4wIG9uIHBjaTANCmlzYTA6IDxJ U0EgYnVzPiBvbiBpc2FiMA0KYXRhcGNpMDogPEludGVsIElDSDEwIFNBVEEzMDAgY29udHJvbGxl cj4gcG9ydCAweGFjMDAtMHhhYzA3LDB4YTg4MC0weGE4ODMsMHhhODAwLTB4YTgwNywweGE0ODAt MHhhNDgzLDB4YTQwMC0weGE0MGYsMHhhMDgwLTB4YTA4ZiBpcnEgMTkgYXQgZGV2aWNlIDMxLjIg b24gcGNpMA0KYXRhcGNpMDogW0lUSFJFQURdDQphdGEyOiA8QVRBIGNoYW5uZWwgMD4gb24gYXRh cGNpMA0KYXRhMjogW0lUSFJFQURdDQphdGEzOiA8QVRBIGNoYW5uZWwgMT4gb24gYXRhcGNpMA0K YXRhMzogW0lUSFJFQURdDQpwY2kwOiA8c2VyaWFsIGJ1cywgU01CdXM+IGF0IGRldmljZSAzMS4z IChubyBkcml2ZXIgYXR0YWNoZWQpDQphdGFwY2kxOiA8SW50ZWwgSUNIMTAgU0FUQTMwMCBjb250 cm9sbGVyPiBwb3J0IDB4YmMwMC0weGJjMDcsMHhiODgwLTB4Yjg4MywweGI4MDAtMHhiODA3LDB4 YjQ4MC0weGI0ODMsMHhiNDAwLTB4YjQwZiwweGIwODAtMHhiMDhmIGlycSAxOSBhdCBkZXZpY2Ug MzEuNSBvbiBwY2kwDQphdGFwY2kxOiBbSVRIUkVBRF0NCmF0YTQ6IDxBVEEgY2hhbm5lbCAwPiBv biBhdGFwY2kxDQphdGE0OiBbSVRIUkVBRF0NCmF0YTU6IDxBVEEgY2hhbm5lbCAxPiBvbiBhdGFw Y2kxDQphdGE1OiBbSVRIUkVBRF0NCmFjcGlfYnV0dG9uMDogPFBvd2VyIEJ1dHRvbj4gb24gYWNw aTANCmF0cnRjMDogPEFUIHJlYWx0aW1lIGNsb2NrPiBwb3J0IDB4NzAtMHg3MSBpcnEgOCBvbiBh Y3BpMA0KdWFydDA6IDwxNjU1MCBvciBjb21wYXRpYmxlPiBwb3J0IDB4M2Y4LTB4M2ZmIGlycSA0 IGZsYWdzIDB4MTAgb24gYWNwaTANCnVhcnQwOiBbRklMVEVSXQ0KdWFydDE6IDwxNjU1MCBvciBj b21wYXRpYmxlPiBwb3J0IDB4MmY4LTB4MmZmIGlycSAzIG9uIGFjcGkwDQp1YXJ0MTogW0ZJTFRF Ul0NCmFjcGlfaHBldDA6IDxIaWdoIFByZWNpc2lvbiBFdmVudCBUaW1lcj4gaW9tZW0gMHhmZWQw MDAwMC0weGZlZDAwM2ZmIG9uIGFjcGkwDQpUaW1lY291bnRlciAiSFBFVCIgZnJlcXVlbmN5IDE0 MzE4MTgwIEh6IHF1YWxpdHkgOTAwDQpxcGkwOiA8UVBJIHN5c3RlbSBidXM+IG9uIG1vdGhlcmJv YXJkDQpwY2liMTE6IDxRUEkgSG9zdC1QQ0kgYnJpZGdlPiBwY2lidXMgMjU1IG9uIHFwaTANCnBj aTI1NTogPFBDSSBidXM+IG9uIHBjaWIxMQ0KcGNpYjEyOiA8UVBJIEhvc3QtUENJIGJyaWRnZT4g cGNpYnVzIDI1NCBvbiBxcGkwDQpwY2kyNTQ6IDxQQ0kgYnVzPiBvbiBwY2liMTINCm9ybTA6IDxJ U0EgT3B0aW9uIFJPTT4gYXQgaW9tZW0gMHhjMDAwMC0weGM3ZmZmIG9uIGlzYTANCnNjMDogPFN5 c3RlbSBjb25zb2xlPiBhdCBmbGFncyAweDEwMCBvbiBpc2EwDQpzYzA6IENHQSA8MTYgdmlydHVh bCBjb25zb2xlcywgZmxhZ3M9MHgzMDA+DQp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0 IDB4M2QwLTB4M2RiIGlvbWVtIDB4YjgwMDAtMHhiZmZmZiBvbiBpc2EwDQphdGtiZGMwOiA8S2V5 Ym9hcmQgY29udHJvbGxlciAoaTgwNDIpPiBhdCBwb3J0IDB4NjAsMHg2NCBvbiBpc2EwDQphdGti ZDA6IDxBVCBLZXlib2FyZD4gaXJxIDEgb24gYXRrYmRjMA0Ka2JkMCBhdCBhdGtiZDANCmF0a2Jk MDogW0dJQU5ULUxPQ0tFRF0NCmF0a2JkMDogW0lUSFJFQURdDQpwcGMwOiBjYW5ub3QgcmVzZXJ2 ZSBJL08gcG9ydCByYW5nZQ0KZXN0MDogPEVuaGFuY2VkIFNwZWVkU3RlcCBGcmVxdWVuY3kgQ29u dHJvbD4gb24gY3B1MA0KcDR0Y2MwOiA8Q1BVIEZyZXF1ZW5jeSBUaGVybWFsIENvbnRyb2w+IG9u IGNwdTANCmVzdDE6IDxFbmhhbmNlZCBTcGVlZFN0ZXAgRnJlcXVlbmN5IENvbnRyb2w+IG9uIGNw dTENCnA0dGNjMTogPENQVSBGcmVxdWVuY3kgVGhlcm1hbCBDb250cm9sPiBvbiBjcHUxDQplc3Qy OiA8RW5oYW5jZWQgU3BlZWRTdGVwIEZyZXF1ZW5jeSBDb250cm9sPiBvbiBjcHUyDQpwNHRjYzI6 IDxDUFUgRnJlcXVlbmN5IFRoZXJtYWwgQ29udHJvbD4gb24gY3B1Mg0KZXN0MzogPEVuaGFuY2Vk IFNwZWVkU3RlcCBGcmVxdWVuY3kgQ29udHJvbD4gb24gY3B1Mw0KcDR0Y2MzOiA8Q1BVIEZyZXF1 ZW5jeSBUaGVybWFsIENvbnRyb2w+IG9uIGNwdTMNCmVzdDQ6IDxFbmhhbmNlZCBTcGVlZFN0ZXAg RnJlcXVlbmN5IENvbnRyb2w+IG9uIGNwdTQNCnA0dGNjNDogPENQVSBGcmVxdWVuY3kgVGhlcm1h bCBDb250cm9sPiBvbiBjcHU0DQplc3Q1OiA8RW5oYW5jZWQgU3BlZWRTdGVwIEZyZXF1ZW5jeSBD b250cm9sPiBvbiBjcHU1DQpwNHRjYzU6IDxDUFUgRnJlcXVlbmN5IFRoZXJtYWwgQ29udHJvbD4g b24gY3B1NQ0KZXN0NjogPEVuaGFuY2VkIFNwZWVkU3RlcCBGcmVxdWVuY3kgQ29udHJvbD4gb24g Y3B1Ng0KcDR0Y2M2OiA8Q1BVIEZyZXF1ZW5jeSBUaGVybWFsIENvbnRyb2w+IG9uIGNwdTYNCmVz dDc6IDxFbmhhbmNlZCBTcGVlZFN0ZXAgRnJlcXVlbmN5IENvbnRyb2w+IG9uIGNwdTcNCnA0dGNj NzogPENQVSBGcmVxdWVuY3kgVGhlcm1hbCBDb250cm9sPiBvbiBjcHU3DQplc3Q4OiA8RW5oYW5j ZWQgU3BlZWRTdGVwIEZyZXF1ZW5jeSBDb250cm9sPiBvbiBjcHU4DQpwNHRjYzg6IDxDUFUgRnJl cXVlbmN5IFRoZXJtYWwgQ29udHJvbD4gb24gY3B1OA0KZXN0OTogPEVuaGFuY2VkIFNwZWVkU3Rl cCBGcmVxdWVuY3kgQ29udHJvbD4gb24gY3B1OQ0KcDR0Y2M5OiA8Q1BVIEZyZXF1ZW5jeSBUaGVy bWFsIENvbnRyb2w+IG9uIGNwdTkNCmVzdDEwOiA8RW5oYW5jZWQgU3BlZWRTdGVwIEZyZXF1ZW5j eSBDb250cm9sPiBvbiBjcHUxMA0KcDR0Y2MxMDogPENQVSBGcmVxdWVuY3kgVGhlcm1hbCBDb250 cm9sPiBvbiBjcHUxMA0KZXN0MTE6IDxFbmhhbmNlZCBTcGVlZFN0ZXAgRnJlcXVlbmN5IENvbnRy b2w+IG9uIGNwdTExDQpwNHRjYzExOiA8Q1BVIEZyZXF1ZW5jeSBUaGVybWFsIENvbnRyb2w+IG9u IGNwdTExDQplc3QxMjogPEVuaGFuY2VkIFNwZWVkU3RlcCBGcmVxdWVuY3kgQ29udHJvbD4gb24g Y3B1MTINCnA0dGNjMTI6IDxDUFUgRnJlcXVlbmN5IFRoZXJtYWwgQ29udHJvbD4gb24gY3B1MTIN CmVzdDEzOiA8RW5oYW5jZWQgU3BlZWRTdGVwIEZyZXF1ZW5jeSBDb250cm9sPiBvbiBjcHUxMw0K cDR0Y2MxMzogPENQVSBGcmVxdWVuY3kgVGhlcm1hbCBDb250cm9sPiBvbiBjcHUxMw0KZXN0MTQ6 IDxFbmhhbmNlZCBTcGVlZFN0ZXAgRnJlcXVlbmN5IENvbnRyb2w+IG9uIGNwdTE0DQpwNHRjYzE0 OiA8Q1BVIEZyZXF1ZW5jeSBUaGVybWFsIENvbnRyb2w+IG9uIGNwdTE0DQplc3QxNTogPEVuaGFu Y2VkIFNwZWVkU3RlcCBGcmVxdWVuY3kgQ29udHJvbD4gb24gY3B1MTUNCnA0dGNjMTU6IDxDUFUg RnJlcXVlbmN5IFRoZXJtYWwgQ29udHJvbD4gb24gY3B1MTUNClpGUyBmaWxlc3lzdGVtIHZlcnNp b24gNA0KWkZTIHN0b3JhZ2UgcG9vbCB2ZXJzaW9uIDE1DQpUaW1lY291bnRlcnMgdGljayBldmVy eSAxLjAwMCBtc2VjDQp2Ym94ZHJ2OiBmQXN5bmM9MCBvZmZNaW49MHg1ZDQgb2ZmTWF4PTB4ODc4 DQp1c2J1czA6IDEyTWJwcyBGdWxsIFNwZWVkIFVTQiB2MS4wDQp1c2J1czE6IDEyTWJwcyBGdWxs IFNwZWVkIFVTQiB2MS4wDQp1c2J1czI6IDEyTWJwcyBGdWxsIFNwZWVkIFVTQiB2MS4wDQp1c2J1 czM6IDQ4ME1icHMgSGlnaCBTcGVlZCBVU0IgdjIuMA0KdXNidXM0OiAxMk1icHMgRnVsbCBTcGVl ZCBVU0IgdjEuMA0KdXNidXM1OiAxMk1icHMgRnVsbCBTcGVlZCBVU0IgdjEuMA0KdXNidXM2OiAx Mk1icHMgRnVsbCBTcGVlZCBVU0IgdjEuMA0KdXNidXM3OiA0ODBNYnBzIEhpZ2ggU3BlZWQgVVNC IHYyLjANCmFkNDogMTkwNzcyOU1CIDxXREMgV0QyMDAzRllZUy0wMlcwQjAgMDEuMDFEMDE+IGF0 IGF0YTItbWFzdGVyIFVETUExMDAgU0FUQSAzR2Ivcw0KdWdlbjAuMTogPEludGVsPiBhdCB1c2J1 czANCnVodWIwOiA8SW50ZWwgVUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAw LCBhZGRyIDE+IG9uIHVzYnVzMA0KdWdlbjEuMTogPEludGVsPiBhdCB1c2J1czENCnVodWIxOiA8 SW50ZWwgVUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBhZGRyIDE+IG9u IHVzYnVzMQ0KdWdlbjIuMTogPEludGVsPiBhdCB1c2J1czINCnVodWIyOiA8SW50ZWwgVUhDSSBy b290IEhVQiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBhZGRyIDE+IG9uIHVzYnVzMg0KdWdl bjMuMTogPEludGVsPiBhdCB1c2J1czMNCnVodWIzOiA8SW50ZWwgRUhDSSByb290IEhVQiwgY2xh c3MgOS8wLCByZXYgMi4wMC8xLjAwLCBhZGRyIDE+IG9uIHVzYnVzMw0KdWdlbjQuMTogPEludGVs PiBhdCB1c2J1czQNCnVodWI0OiA8SW50ZWwgVUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYg MS4wMC8xLjAwLCBhZGRyIDE+IG9uIHVzYnVzNA0KdWdlbjUuMTogPEludGVsPiBhdCB1c2J1czUN CnVodWI1OiA8SW50ZWwgVUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBh ZGRyIDE+IG9uIHVzYnVzNQ0KdWdlbjYuMTogPEludGVsPiBhdCB1c2J1czYNCnVodWI2OiA8SW50 ZWwgVUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBhZGRyIDE+IG9uIHVz YnVzNg0KdWdlbjcuMTogPEludGVsPiBhdCB1c2J1czcNCnVodWI3OiA8SW50ZWwgRUhDSSByb290 IEhVQiwgY2xhc3MgOS8wLCByZXYgMi4wMC8xLjAwLCBhZGRyIDE+IG9uIHVzYnVzNw0KYWQ2OiAx OTA3NzI5TUIgPFdEQyBXRDIwMDNGWVlTLTAyVzBCMCAwMS4wMUQwMT4gYXQgYXRhMy1tYXN0ZXIg VURNQTEwMCBTQVRBIDNHYi9zDQpTTVA6IEFQIENQVSAjMSBMYXVuY2hlZCENClNNUDogQVAgQ1BV ICMxMSBMYXVuY2hlZCENClNNUDogQVAgQ1BVICM0IExhdW5jaGVkIQ0KU01QOiBBUCBDUFUgIzEz IExhdW5jaGVkIQ0KU01QOiBBUCBDUFUgIzMgTGF1bmNoZWQhDQpTTVA6IEFQIENQVSAjMTIgTGF1 bmNoZWQhDQpTTVA6IEFQIENQVSAjMiBMYXVuY2hlZCENClNNUDogQVAgQ1BVICMxMCBMYXVuY2hl ZCENClNNUDogQVAgQ1BVICM2IExhdW5jaGVkIQ0KU01QOiBBUCBDUFUgIzkgTGF1bmNoZWQhDQpT TVA6IEFQIENQVSAjNSBMYXVuY2hlZCENClNNUDogQVAgQ1BVICMxNCBMYXVuY2hlZCENClNNUDog QVAgQ1BVICM3IExhdW5jaGVkIQ0KU01QOiBBUCBDUFUgIzggTGF1bmNoZWQhDQpTTVA6IEFQIENQ VSAjMTUgTGF1bmNoZWQhDQpSb290IG1vdW50IHdhaXRpbmcgZm9yOiB1c2J1czcgdXNidXM2IHVz YnVzNSB1c2J1czQgdXNidXMzIHVzYnVzMiB1c2J1czEgdXNidXMwDQp1aHViMDogMiBwb3J0cyB3 aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQNCnVodWIxOiAyIHBvcnRzIHdpdGggMiByZW1v dmFibGUsIHNlbGYgcG93ZXJlZA0KdWh1YjI6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2Vs ZiBwb3dlcmVkDQp1aHViNDogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQN CnVodWI1OiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZA0KdWh1YjY6IDIg cG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2VsZiBwb3dlcmVkDQpSb290IG1vdW50IHdhaXRpbmcg Zm9yOiB1c2J1czcgdXNidXMzDQpSb290IG1vdW50IHdhaXRpbmcgZm9yOiB1c2J1czcgdXNidXMz DQp1aHViMzogNiBwb3J0cyB3aXRoIDYgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQNCnVodWI3OiA2 IHBvcnRzIHdpdGggNiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZA0KdWdlbjcuMjogPEFtZXJpY2Fu IE1lZ2F0cmVuZHMgSW5jLj4gYXQgdXNidXM3DQpUcnlpbmcgdG8gbW91bnQgcm9vdCBmcm9tIHpm czp6cm9vdA0KdmJveG5ldDA6IEV0aGVybmV0IGFkZHJlc3M6IDBhOjAwOjI3OjAwOjAwOjAwDQpl bTE6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBVUA0KDQo= --=_97b141643bab6cbf973d27e216a96e96-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 00:47:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23D5B10656A5 for ; Wed, 15 Dec 2010 00:47:15 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id C42B28FC22 for ; Wed, 15 Dec 2010 00:47:14 +0000 (UTC) Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta10.westchester.pa.mail.comcast.net with comcast id iz671f0051YDfWL5ACnE1Y; Wed, 15 Dec 2010 00:47:14 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta20.westchester.pa.mail.comcast.net with comcast id jCnD1f00D3LrwQ23gCnEMm; Wed, 15 Dec 2010 00:47:14 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 252849B427; Tue, 14 Dec 2010 16:47:12 -0800 (PST) Date: Tue, 14 Dec 2010 16:47:12 -0800 From: Jeremy Chadwick To: Dan Allen Message-ID: <20101215004712.GA56065@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 00:47:15 -0000 On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > Recently my network connection now is setup AFTER ntpd is launched rather than before. > > So when ntpd starts there is no net connection and it gives up. > > I read /usr/src/UPDATING but nothing is mentioned about a change in boot order. > > Any ideas? This issue has been discussed pretty thoroughly in the past. There's no official solution, but there is an rc.d script I wrote which addresses this shortcoming. Nothing related to the "boot order" has changed, but network drivers and overall methodology has changed. Anyway, many people are using the below with success. http://jdc.parodius.com/freebsd/netwait Official patches, including the rc.conf(5) change I propose: http://jdc.parodius.com/freebsd/netwait_patches/ Example usage (in rc.conf): netwait_enable="yes" netwait_ip="4.2.2.1 4.2.2.2" netwait_if="em0" For what these variables mean, please see the script itself. They are thoroughly documented. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 00:47:42 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F751106566B for ; Wed, 15 Dec 2010 00:47:42 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 0ADAA8FC26 for ; Wed, 15 Dec 2010 00:47:41 +0000 (UTC) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta05.westchester.pa.mail.comcast.net with comcast id jCLf1f00717dt5G55Cnh4B; Wed, 15 Dec 2010 00:47:41 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta13.westchester.pa.mail.comcast.net with comcast id jCng1f00G3LrwQ23ZCnhDJ; Wed, 15 Dec 2010 00:47:41 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7C1809B42B; Tue, 14 Dec 2010 16:47:39 -0800 (PST) Date: Tue, 14 Dec 2010 16:47:39 -0800 From: Jeremy Chadwick To: Chuck Swiger Message-ID: <20101215004739.GB56065@icarus.home.lan> References: <7B9EB743-7C87-42AF-85DE-C05352E4A429@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7B9EB743-7C87-42AF-85DE-C05352E4A429@mac.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Dan Allen , FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 00:47:42 -0000 On Tue, Dec 14, 2010 at 04:46:10PM -0800, Chuck Swiger wrote: > On Dec 14, 2010, at 4:38 PM, Dan Allen wrote: > > Recently my network connection now is setup AFTER ntpd is launched rather than before. > > > > So when ntpd starts there is no net connection and it gives up. > > Change the REQUIRE line in /etc/rc.d/ntpd to indicate whatever dependency you need to have so that your network connection is up before ntpd tries to run. "man rcorder" is informative.... It's not that simple. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 00:53:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA70310656A3 for ; Wed, 15 Dec 2010 00:53:50 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout029.mac.com (asmtpout029.mac.com [17.148.16.104]) by mx1.freebsd.org (Postfix) with ESMTP id 8EE548FC25 for ; Wed, 15 Dec 2010 00:53:50 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp029.mac.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 64bit)) with ESMTPSA id <0LDG0036U2HPFS60@asmtp029.mac.com> for freebsd-stable@freebsd.org; Tue, 14 Dec 2010 16:53:50 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1010190000 definitions=main-1012140190 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2010-12-14_14:2010-12-14, 2010-12-14, 1970-01-01 signatures=0 From: Chuck Swiger In-reply-to: <20101215004739.GB56065@icarus.home.lan> Date: Tue, 14 Dec 2010 16:53:49 -0800 Message-id: References: <7B9EB743-7C87-42AF-85DE-C05352E4A429@mac.com> <20101215004739.GB56065@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1082) Cc: Dan Allen , FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 00:53:50 -0000 On Dec 14, 2010, at 4:47 PM, Jeremy Chadwick wrote: [ ... ] >> Change the REQUIRE line in /etc/rc.d/ntpd to indicate whatever dependency you need to have so that your network connection is up before ntpd tries to run. "man rcorder" is informative.... > > It's not that simple. Shrug-- if there is *unmentioned* additional complexity, well, no doubt you're correct. Another alternative might be to switch to launchd, which is more of a capability-based system which stops and starts services more dynamically, including upon notification that an intermittent network connection is presently active and usable. ("rc NG" is quite capable on it's own right, but a lot of the flexible behavior of a Mac laptop dealing with suspend/resume, network drops and resumes, etc comes from launchd architecture.) Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 00:55:25 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6570F10656A5 for ; Wed, 15 Dec 2010 00:55:25 +0000 (UTC) (envelope-from lichray@gmail.com) Received: from mail-ey0-f178.google.com (mail-ey0-f178.google.com [209.85.215.178]) by mx1.freebsd.org (Postfix) with ESMTP id E347A8FC17 for ; Wed, 15 Dec 2010 00:55:24 +0000 (UTC) Received: by eyh5 with SMTP id 5so725495eyh.37 for ; Tue, 14 Dec 2010 16:55:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=3byv2tyy5wbztoEdQ8H+yVA0hLJoPLJ5W0n4H5v99oo=; b=Nm9dEPqgWKsUDp2xbDps7OnzZLsAnmchpwN2k/WFHEe95L053xP0c7mdKC1794TKdO GLVeLVoXQaBlUeLl9JeQGGLSR+DugMhoQPBb6E4oGeMPdYRIGclX57GYasaEtf7yE8Us ahY3OgriimlDRpFN28Lcworv46HEK+Uh/VPKc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=JDw3cTddmACFolM8xSLquhabLQp+3N8S3ffCGobWLIl+eeR/WIZGMiaK9hBQ7GrJe3 kAlObuoBjiHz3yx1r8B9kSIrfbCja5QEBvY1xy7Oy0sGxUqgS3pk0dNsFJi4DNeFKHRS ZDZzcBlu+wlKwCqN2IVLtHWlrBNboB6ZqTdaU= MIME-Version: 1.0 Received: by 10.213.108.201 with SMTP id g9mr4235589ebp.46.1292374522301; Tue, 14 Dec 2010 16:55:22 -0800 (PST) Received: by 10.213.4.4 with HTTP; Tue, 14 Dec 2010 16:55:22 -0800 (PST) In-Reply-To: <20101215004712.GA56065@icarus.home.lan> References: <20101215004712.GA56065@icarus.home.lan> Date: Tue, 14 Dec 2010 18:55:22 -0600 Message-ID: From: Zhihao Yuan To: Jeremy Chadwick Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Dan Allen , dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 00:55:25 -0000 ping is slow. I hope that we can change the behavior of detecting network to something event driven. Like to insert a script into syslogd to detect the host's dhclient status (in a static IP environment, we don't need 'netwait'), or check ifconfig, something like that. On Tue, Dec 14, 2010 at 6:47 PM, Jeremy Chadwick wrote: > On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > > Recently my network connection now is setup AFTER ntpd is launched rather > than before. > > > > So when ntpd starts there is no net connection and it gives up. > > > > I read /usr/src/UPDATING but nothing is mentioned about a change in boot > order. > > > > Any ideas? > > This issue has been discussed pretty thoroughly in the past. There's no > official solution, but there is an rc.d script I wrote which addresses > this shortcoming. Nothing related to the "boot order" has changed, but > network drivers and overall methodology has changed. > > Anyway, many people are using the below with success. > > http://jdc.parodius.com/freebsd/netwait > > Official patches, including the rc.conf(5) change I propose: > > http://jdc.parodius.com/freebsd/netwait_patches/ > > Example usage (in rc.conf): > > netwait_enable="yes" > netwait_ip="4.2.2.1 4.2.2.2" > netwait_if="em0" > > For what these variables mean, please see the script itself. They are > thoroughly documented. > > -- > | Jeremy Chadwick jdc@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > _______________________________________________ > 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" > -- Zhihao Yuan The best way to predict the future is to invent it. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 01:12:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CE781065672 for ; Wed, 15 Dec 2010 01:12:51 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by mx1.freebsd.org (Postfix) with ESMTP id CD82F8FC12 for ; Wed, 15 Dec 2010 01:12:50 +0000 (UTC) Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta12.westchester.pa.mail.comcast.net with comcast id j7TT1f0061ei1Bg5CDCqep; Wed, 15 Dec 2010 01:12:50 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta24.westchester.pa.mail.comcast.net with comcast id jDCo1f00M3LrwQ23kDCplj; Wed, 15 Dec 2010 01:12:50 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 885439B427; Tue, 14 Dec 2010 17:12:47 -0800 (PST) Date: Tue, 14 Dec 2010 17:12:47 -0800 From: Jeremy Chadwick To: Zhihao Yuan Message-ID: <20101215011247.GA56591@icarus.home.lan> References: <20101215004712.GA56065@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Dan Allen , dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 01:12:51 -0000 On Tue, Dec 14, 2010 at 06:55:22PM -0600, Zhihao Yuan wrote: > ping is slow. I hope that we can change the behavior of detecting network to > something event driven. Like to insert a script into syslogd to detect the > host's dhclient status (in a static IP environment, we don't need > 'netwait'), or check ifconfig, something like that. > > On Tue, Dec 14, 2010 at 6:47 PM, Jeremy Chadwick > wrote: > > > On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > > > Recently my network connection now is setup AFTER ntpd is launched rather > > than before. > > > > > > So when ntpd starts there is no net connection and it gives up. > > > > > > I read /usr/src/UPDATING but nothing is mentioned about a change in boot > > order. > > > > > > Any ideas? > > > > This issue has been discussed pretty thoroughly in the past. There's no > > official solution, but there is an rc.d script I wrote which addresses > > this shortcoming. Nothing related to the "boot order" has changed, but > > network drivers and overall methodology has changed. > > > > Anyway, many people are using the below with success. > > > > http://jdc.parodius.com/freebsd/netwait > > > > Official patches, including the rc.conf(5) change I propose: > > > > http://jdc.parodius.com/freebsd/netwait_patches/ > > > > Example usage (in rc.conf): > > > > netwait_enable="yes" > > netwait_ip="4.2.2.1 4.2.2.2" > > netwait_if="em0" > > > > For what these variables mean, please see the script itself. They are > > thoroughly documented. I don't know what "ping is slow" means -- utter nonsense. Read the script. Look at how it works please. Seriously. I spent a lot of time on it, with the help of a lot of community members (including some with very complex network setups (multiple NICs of different brands, VLANs, custom routes)). netwait is in no way a permanent solution -- it simply addresses most non-complex environments *reliably*. ifconfig, devd, etc. are not sufficient ways of determining if the network is *actually usable*. I cannot stress this enough. I am not talking out of my ass. What everyone's proposing (launchd, "way to monitor syslog", event-driven, blah blah) is wonderful, but until someone has actually done it, it's just ideal talk. These words are coming from someone who's very much an idealist, so keep that in mind too; I'm one of the "worst offenders" when it comes to recommending solutions but not having the time to implement them. I'm going to bow out of the conversation at this point and simply ask folks here on the thread to take the time to dig up/read old mailing list archives on the matter. We (FreeBSD Community and the freebsd-rc folks) have been over all of this before. Sorry for sounding crass and rude, but every time this question comes up, I feel like I have to "defend" why the netwait script exists, why it was designed the way it was, and so on. Yes, a better infrastructure is needed to solve the problem *at the core*, but until someone writes that, we need something that works. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 01:43:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DF7F1065672; Wed, 15 Dec 2010 01:43:07 +0000 (UTC) (envelope-from lichray@gmail.com) Received: from mail-ey0-f178.google.com (mail-ey0-f178.google.com [209.85.215.178]) by mx1.freebsd.org (Postfix) with ESMTP id E0D088FC13; Wed, 15 Dec 2010 01:43:06 +0000 (UTC) Received: by eyh5 with SMTP id 5so739684eyh.37 for ; Tue, 14 Dec 2010 17:43:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=O3pMq3dwfG3tey7/6Xo5JOzDNOSTeQfAGdujnXG2c0w=; b=Wx64KqHEhIa7bcg2CdK5SiQiy5cH//yPE7ZZj1unPDBoCpwGYYh9tG2gZXucOY1egN h0S2bJJcv69XY4NxJClyMq8P4qFsSPAiia1KLCn4JW0o6omz87vZFtw+KkVRgmIACgtH ySu5oXmNrPPsWbgLu01BR7OwmPTvekBWcc70c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cR5ZskcEu8nA6L7tjnKr0F2Z9Gfuc0s1wC14ogVdY/VW1hwn8vMt/nW5fG1PZXRgr7 zrGs8I8Piny0SRJZMNWnI0ZkB8StIwMjF8GJO9FG6zy5AkfN7dJUgoF8WK5mRKxpXDke HkJ2RaNugxaJ4yFnQGrOuuU68SOrctB7B9WsI= MIME-Version: 1.0 Received: by 10.213.30.7 with SMTP id s7mr1205442ebc.20.1292377384786; Tue, 14 Dec 2010 17:43:04 -0800 (PST) Received: by 10.213.4.4 with HTTP; Tue, 14 Dec 2010 17:43:04 -0800 (PST) In-Reply-To: <20101215011247.GA56591@icarus.home.lan> References: <20101215004712.GA56065@icarus.home.lan> <20101215011247.GA56591@icarus.home.lan> Date: Tue, 14 Dec 2010 19:43:04 -0600 Message-ID: From: Zhihao Yuan To: Jeremy Chadwick Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Dan Allen , dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 01:43:07 -0000 I read your script. OK. My question is, how can I use more than 1 netwait_if? I know I can just use netwait_ip instead, but, for example, in a mDNS configured environment, ping may take a long time to response. In some conditions, it can be 1min. So I don't want to use the fallback 'ping' method. Most laptops today have both LAN and WLAN internet faces, some of them have even more. So please give my 'utter nonsense' an answer. On Tue, Dec 14, 2010 at 7:12 PM, Jeremy Chadwick wrote: > On Tue, Dec 14, 2010 at 06:55:22PM -0600, Zhihao Yuan wrote: > > ping is slow. I hope that we can change the behavior of detecting network > to > > something event driven. Like to insert a script into syslogd to detect > the > > host's dhclient status (in a static IP environment, we don't need > > 'netwait'), or check ifconfig, something like that. > > > > On Tue, Dec 14, 2010 at 6:47 PM, Jeremy Chadwick > > wrote: > > > > > On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > > > > Recently my network connection now is setup AFTER ntpd is launched > rather > > > than before. > > > > > > > > So when ntpd starts there is no net connection and it gives up. > > > > > > > > I read /usr/src/UPDATING but nothing is mentioned about a change in > boot > > > order. > > > > > > > > Any ideas? > > > > > > This issue has been discussed pretty thoroughly in the past. There's > no > > > official solution, but there is an rc.d script I wrote which addresses > > > this shortcoming. Nothing related to the "boot order" has changed, but > > > network drivers and overall methodology has changed. > > > > > > Anyway, many people are using the below with success. > > > > > > http://jdc.parodius.com/freebsd/netwait > > > > > > Official patches, including the rc.conf(5) change I propose: > > > > > > http://jdc.parodius.com/freebsd/netwait_patches/ > > > > > > Example usage (in rc.conf): > > > > > > netwait_enable="yes" > > > netwait_ip="4.2.2.1 4.2.2.2" > > > netwait_if="em0" > > > > > > For what these variables mean, please see the script itself. They are > > > thoroughly documented. > > I don't know what "ping is slow" means -- utter nonsense. Read the > script. Look at how it works please. Seriously. I spent a lot of time > on it, with the help of a lot of community members (including some with > very complex network setups (multiple NICs of different brands, VLANs, > custom routes)). > > netwait is in no way a permanent solution -- it simply addresses most > non-complex environments *reliably*. ifconfig, devd, etc. are not > sufficient ways of determining if the network is *actually usable*. I > cannot stress this enough. I am not talking out of my ass. > > What everyone's proposing (launchd, "way to monitor syslog", > event-driven, blah blah) is wonderful, but until someone has actually > done it, it's just ideal talk. These words are coming from someone > who's very much an idealist, so keep that in mind too; I'm one of the > "worst offenders" when it comes to recommending solutions but not having > the time to implement them. > > I'm going to bow out of the conversation at this point and simply ask > folks here on the thread to take the time to dig up/read old mailing > list archives on the matter. We (FreeBSD Community and the freebsd-rc > folks) have been over all of this before. > > Sorry for sounding crass and rude, but every time this question comes > up, I feel like I have to "defend" why the netwait script exists, why it > was designed the way it was, and so on. Yes, a better infrastructure is > needed to solve the problem *at the core*, but until someone writes > that, we need something that works. > > -- > | Jeremy Chadwick jdc@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > -- Zhihao Yuan The best way to predict the future is to invent it. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 01:57:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0477106564A for ; Wed, 15 Dec 2010 01:57:11 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id 846178FC0A for ; Wed, 15 Dec 2010 01:57:11 +0000 (UTC) Received: (qmail 3756 invoked by uid 89); 15 Dec 2010 01:57:10 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 15 Dec 2010 01:57:10 -0000 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Dan Allen In-Reply-To: <20101215004712.GA56065@icarus.home.lan> Date: Tue, 14 Dec 2010 18:57:09 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <990D2B43-658D-4323-ADBB-F1461BD747A5@airwired.net> References: <20101215004712.GA56065@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1082) Cc: dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 01:57:11 -0000 On 14 Dec 2010, at 5:47 PM, Jeremy Chadwick wrote: > This issue has been discussed pretty thoroughly in the past. There's = no > official solution, but there is an rc.d script I wrote which addresses > this shortcoming. Nothing related to the "boot order" has changed, = but > network drivers and overall methodology has changed. Thanks: I will give your script a try. FYI: it has worked fine for about 15 years of my using FreeBSD until = recently! The other solution would be for ntpd to not just give up the first time = it looks for the net. It could try again a minute later and it would = work just fine. Apparently it never tries a second time! This is something that should just work out of the box, IMHO. Thanks everyone for your help! Dan From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 02:03:02 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8908106566C for ; Wed, 15 Dec 2010 02:03:02 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id 82C778FC19 for ; Wed, 15 Dec 2010 02:03:02 +0000 (UTC) Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta08.emeryville.ca.mail.comcast.net with comcast id jDue1f00K0EPchoA8E31Rx; Wed, 15 Dec 2010 02:03:01 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta01.emeryville.ca.mail.comcast.net with comcast id jE2w1f00L3LrwQ28ME2y6d; Wed, 15 Dec 2010 02:02:59 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C2EC89B427; Tue, 14 Dec 2010 18:02:53 -0800 (PST) Date: Tue, 14 Dec 2010 18:02:53 -0800 From: Jeremy Chadwick To: Zhihao Yuan Message-ID: <20101215020253.GA57526@icarus.home.lan> References: <20101215004712.GA56065@icarus.home.lan> <20101215011247.GA56591@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Dan Allen , dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 02:03:02 -0000 On Tue, Dec 14, 2010 at 07:43:04PM -0600, Zhihao Yuan wrote: > I read your script. OK. My question is, how can I use more than 1 > netwait_if? I know I can just use netwait_ip instead, but, for example, in a > mDNS configured environment, ping may take a long time to response. In some > conditions, it can be 1min. So I don't want to use the fallback 'ping' > method. Most laptops today have both LAN and WLAN internet faces, some of > them have even more. So please give my 'utter nonsense' an answer. > On Tue, Dec 14, 2010 at 7:12 PM, Jeremy Chadwick > wrote: > > > On Tue, Dec 14, 2010 at 06:55:22PM -0600, Zhihao Yuan wrote: > > > ping is slow. I hope that we can change the behavior of detecting network > > to > > > something event driven. Like to insert a script into syslogd to detect > > the > > > host's dhclient status (in a static IP environment, we don't need > > > 'netwait'), or check ifconfig, something like that. > > > > > > On Tue, Dec 14, 2010 at 6:47 PM, Jeremy Chadwick > > > wrote: > > > > > > > On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > > > > > Recently my network connection now is setup AFTER ntpd is launched > > rather > > > > than before. > > > > > > > > > > So when ntpd starts there is no net connection and it gives up. > > > > > > > > > > I read /usr/src/UPDATING but nothing is mentioned about a change in > > boot > > > > order. > > > > > > > > > > Any ideas? > > > > > > > > This issue has been discussed pretty thoroughly in the past. There's > > no > > > > official solution, but there is an rc.d script I wrote which addresses > > > > this shortcoming. Nothing related to the "boot order" has changed, but > > > > network drivers and overall methodology has changed. > > > > > > > > Anyway, many people are using the below with success. > > > > > > > > http://jdc.parodius.com/freebsd/netwait > > > > > > > > Official patches, including the rc.conf(5) change I propose: > > > > > > > > http://jdc.parodius.com/freebsd/netwait_patches/ > > > > > > > > Example usage (in rc.conf): > > > > > > > > netwait_enable="yes" > > > > netwait_ip="4.2.2.1 4.2.2.2" > > > > netwait_if="em0" > > > > > > > > For what these variables mean, please see the script itself. They are > > > > thoroughly documented. > > > > I don't know what "ping is slow" means -- utter nonsense. Read the > > script. Look at how it works please. Seriously. I spent a lot of time > > on it, with the help of a lot of community members (including some with > > very complex network setups (multiple NICs of different brands, VLANs, > > custom routes)). > > > > netwait is in no way a permanent solution -- it simply addresses most > > non-complex environments *reliably*. ifconfig, devd, etc. are not > > sufficient ways of determining if the network is *actually usable*. I > > cannot stress this enough. I am not talking out of my ass. > > > > What everyone's proposing (launchd, "way to monitor syslog", > > event-driven, blah blah) is wonderful, but until someone has actually > > done it, it's just ideal talk. These words are coming from someone > > who's very much an idealist, so keep that in mind too; I'm one of the > > "worst offenders" when it comes to recommending solutions but not having > > the time to implement them. > > > > I'm going to bow out of the conversation at this point and simply ask > > folks here on the thread to take the time to dig up/read old mailing > > list archives on the matter. We (FreeBSD Community and the freebsd-rc > > folks) have been over all of this before. > > > > Sorry for sounding crass and rude, but every time this question comes > > up, I feel like I have to "defend" why the netwait script exists, why it > > was designed the way it was, and so on. Yes, a better infrastructure is > > needed to solve the problem *at the core*, but until someone writes > > that, we need something that works. "ping is slow", literally, is nonsensical. There's nothing "slow" about ping. You can adjust netwait_timeout as you see fit if you don't like waiting for ICMP ECHO REPLY -- but I won't be held responsible if layer 1 or layer 2 takes longer than $netwait_timeout to be configured. But now you're changing subject matter -- you have a dual-homed machine that you want to verify the usability of both interfaces for. Verifying packet flow *actually works* on both of these interfaces is possible, but the present incarnation of the script does not support this. If your network interface takes 60 seconds to come up and get configured fully, and Internet connectivity needs to be reliable before starting daemons that rely on such connectivity, then you *absolutely should* be waiting 60 seconds or longer. It's up to you to decide whether or not reliable network connectivity is work waiting for. Why? Because named, ntpd, and many other daemons do not "retry" if their initial attempts to do DNS lookups or communication fail. I'm not responsible for this problem -- but netwait helps ensure that these failures no longer happen -- which is what the OP was complaining about. Circling back to "what interface do I choose": the design concept is that you should pick whatever interface is, ideally, associated with your default gateway (in theory, whatever points towards the Internet). For example: if you have two NICs (LAN and WLAN), both of which are connected + configured during network configuration time, and both go to the Internet, then it really doesn't matter which interface you choose in netwait_if. If you rely more on the WLAN interface (e.g. physical LAN might not always be connected depending on your environment), then pick the WLAN interface and be done with it. And all of this is assuming that you want to verify your *Internet* connectivity works -- again, remember the OP's complaint. Furthermore, nothing stops you from also using a netwait_ip of something on your LAN (like 192.168.1.1 for your home router, etc.). I can't really phrase any of this any better. If you'd like to work on the daemons that don't retry some of their network activity on startup, please do so -- it would be a more proper fix. But there are many such daemons that behave this way. The design model of these daemons is to assume network connectivity is working when they start, and netwait reliably ensures that. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 05:03:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03AC4106566B for ; Wed, 15 Dec 2010 05:03:56 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id D5D068FC19 for ; Wed, 15 Dec 2010 05:03:55 +0000 (UTC) Received: by pzk32 with SMTP id 32so270678pzk.13 for ; Tue, 14 Dec 2010 21:03:55 -0800 (PST) Received: by 10.143.19.4 with SMTP id w4mr5174831wfi.192.1292389435295; Tue, 14 Dec 2010 21:03:55 -0800 (PST) Received: from localhost (118-93-184-18.dsl.dyn.ihug.co.nz [118.93.184.18]) by mx.google.com with ESMTPS id x35sm1058699wfd.1.2010.12.14.21.03.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 14 Dec 2010 21:03:54 -0800 (PST) Date: Wed, 15 Dec 2010 18:03:48 +1300 From: Jonathan Chen To: Dan Allen Message-ID: <20101215050348.GA2197@osiris.chen.org.nz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 05:03:56 -0000 On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > Recently my network connection now is setup AFTER ntpd is launched rather than before. > > So when ntpd starts there is no net connection and it gives up. Let me guess: You're on a DHCP network and the network script are running before the network address is assigned. The solution is to wait for DHCP negotiation to complete before letting the rest of the network scripts to complete. I added the following to /etc/rc.conf: ifconfig_re0="SYNCDHCP" Change re0 to your network device. Cheers. -- Jonathan Chen ---------------------------------------------------------------------- "The things we know best are the things we haven't been taught." - Marquis de Vauvenargues From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 06:14:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89C6B106564A; Wed, 15 Dec 2010 06:14:48 +0000 (UTC) (envelope-from eugene@imedia.ru) Received: from lynx.imedia.ru (lynx.imedia.ru [83.242.167.254]) by mx1.freebsd.org (Postfix) with ESMTP id ECE158FC12; Wed, 15 Dec 2010 06:14:47 +0000 (UTC) X-All-Recipients: DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=imedia.ru; s=common; t=1292393685; bh=dK3Rk8dE3xZwFA63aP5GgEGa1EtCPx3u3whSf9wfkqA=; h=From:Reply-To:To:Subject:Date:Cc:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding:Message-Id; b=kKN19whDIs6w+mH7HLj/IWC0ZVI9Gki2ndZBJOfJHP2Np7FW/D/6rai6f/6A+Qg1i HBX7MeqWMm7NTdADofXyaAbYxB+k04fWZTiOAxYOcVIPk/JrVsFa/39oEe0o55jpS6 tvxN19K9bcV5SKrRjnJccbGgNfEHHmHZPv+FSzHY= Received: from badger.imedia.ru (root@badger.imedia.ru [10.167.1.243]) by lynx.imedia.ru (8.14.3/8.14.3/TWINS7_LDAP) with ESMTP id oBF6EjFg080507; Wed, 15 Dec 2010 09:14:45 +0300 (MSK) (envelope-from eugene@imedia.ru) Received: from badger.imedia.ru (eugene@localhost [127.0.0.1]) by badger.imedia.ru (8.14.4/8.13.1) with ESMTP id oBF6EjV5055454; Wed, 15 Dec 2010 09:14:45 +0300 (MSK) (envelope-from eugene@imedia.ru) Received: from localhost (localhost [[UNIX: localhost]]) by badger.imedia.ru (8.14.4/8.13.8/Submit) id oBF6Ee7B055453; Wed, 15 Dec 2010 09:14:40 +0300 (MSK) (envelope-from eugene@imedia.ru) From: Eugene Mitrofanov Organization: Independent Media Sanoma Magazines To: freebsd-stable@freebsd.org Date: Wed, 15 Dec 2010 09:14:40 +0300 User-Agent: KMail/1.9.10 References: <201012141727.41909.eugene@imedia.ru> <201012141829.17662.eugene@imedia.ru> In-Reply-To: X-Origin: badger.imedia.ru MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201012150914.40884.eugene@imedia.ru> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (lynx.imedia.ru [10.167.0.252]); Wed, 15 Dec 2010 09:14:45 +0300 (MSK) X-Virus-Scanned: clamav-milter 0.96.4-exp at lynx.imedia.ru X-Virus-Status: Clean Cc: Ivan Voras Subject: Re: 8.1-STABLE Unexpected XML: what does it mean? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugene Mitrofanov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2010 06:14:48 -0000 On Tuesday 14 December 2010, Ivan Voras wrote: > On 14/12/2010 16:29, Eugene Mitrofanov wrote: > > On Tuesday 14 December 2010, Ivan Voras wrote: > >> On 14/12/2010 16:19, Eugene Mitrofanov wrote: > >>> > >>> How can I locate this device? Also I dont understand why mdconfig > > complains? > >> > >> Try examining the output of > >> > >> # sysctl -b kern.geom.confxml > > > > Here they are: > > > > > > > > FD > > > > > > fd0 > > 1 > > > > > > r0w0e0 > > fd0 > > 1474560 > > 512 > > 18432 > > 0 > > > > > > > > Looks ok so far (except weird stripesize). Sorry, I have no idea what is > broken here. Try updating and rebuilding world in case you have some > rare corruption. > Thanks, I will try. -- EMIT-RIPN, EVM7-RIPE From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 09:19:05 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7C081065673 for ; Wed, 15 Dec 2010 09:19:05 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 2F08E8FC08 for ; Wed, 15 Dec 2010 09:19:05 +0000 (UTC) Received: from megatron.madpilot.net (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP id DDB6B1DC3 for ; Wed, 15 Dec 2010 10:02:11 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received; s=mail; t=1292403721; x= 1294218121; bh=XtUjMaZIvxgZa1l/nx7H4GhosL5pO45nvZeuw1tnw94=; b=r UqYjfn7FYngC9OKwr3QFfBlnkSzNHLBoUxTzfvD5T2XzHhQ8zUdym0nMmZ+gU/m6 QezzVyvZ+TZrtj942vLlAm0gHvGMU/Kx5K/wbKQXXpRs6O6tJqB+yQgTNfQ2xWEY yJw4guxxHp43V0en525LbukiBQhtMkPMRoZxFd7Y1I= X-Virus-Scanned: amavisd-new at madpilot.net Received: from megatron.madpilot.net ([127.0.0.1]) by megatron.madpilot.net (megatron.madpilot.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id isJPbjVAHxHZ for ; Wed, 15 Dec 2010 10:02:01 +0100 (CET) Received: by megatron.madpilot.net (Postfix, from userid 1000) id 44BE91DBB; Wed, 15 Dec 2010 10:02:01 +0100 (CET) Date: Wed, 15 Dec 2010 10:02:01 +0100 From: Guido Falsi To: freebsd-stable@freebsd.org Message-ID: <20101215090200.GA547@megatron.madpilot.net> References: <20101215004712.GA56065@icarus.home.lan> <20101215011247.GA56591@icarus.home.lan> <20101215020253.GA57526@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101215020253.GA57526@icarus.home.lan> X-Operating-System: FreeBSD 8.1-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 09:19:05 -0000 On Tue, Dec 14, 2010 at 06:02:53PM -0800, Jeremy Chadwick wrote: > > For example: if you have two NICs (LAN and WLAN), both of which are > connected + configured during network configuration time, and both go to > the Internet, then it really doesn't matter which interface you choose > in netwait_if. If you rely more on the WLAN interface (e.g. physical > LAN might not always be connected depending on your environment), then > pick the WLAN interface and be done with it. I have found that for such a configuration (laptop with LAN and WLAN) a very good solution is configuring a lagg interface to failover with the wired interface as primary and the WLAN as backup connection, then the system sees just one network interface and you avoid all the problems multihomed hosts tend to have. In this way one can also flawlessly move around from wired to wireless interface just connecting and disconnecting the wired interface. This may or may not be also a good solution for other setups. I find this script very useful on some servers though. Some machines I have put the network interfaces offline after the kernel probe and they don't come back up for a minute or so. Since I absolutely need the interface up and working for ntpd and other demons such a script is a life saver! Just my 2 cent! ;) -- Guido Falsi From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 10:40:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98903106566B; Wed, 15 Dec 2010 10:40:40 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 750988FC14; Wed, 15 Dec 2010 10:40:40 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id oBFAedZp087831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 Dec 2010 02:40:39 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id oBFAed67087828; Wed, 15 Dec 2010 02:40:39 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA00636; Wed, 15 Dec 10 02:38:02 PST Date: Wed, 15 Dec 2010 02:37:40 -0800 From: perryh@pluto.rain.com To: avg@freebsd.org Message-Id: <4d089a74.vwMJkPEIddt7PIxy%perryh@pluto.rain.com> References: <4cfc72a5.3nAjkv8mdrO/NrKQ%perryh@pluto.rain.com> <4CFD0633.9060509@freebsd.org> In-Reply-To: <4CFD0633.9060509@freebsd.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_4d089a74.3VsRVeW/kwmmuUSPzspeBOJv/FT71OEQDPEttesGTjzsZlxH" Cc: freebsd-stable@freebsd.org Subject: How to debug a double fault? (Re: Could MSGBUF_SIZE be made a loader tunable?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 10:40:40 -0000 This is a multi-part message in MIME format. --=_4d089a74.3VsRVeW/kwmmuUSPzspeBOJv/FT71OEQDPEttesGTjzsZlxH Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Andriy Gapon wrote: > on 06/12/2010 07:20 perryh@pluto.rain.com said the following: > > Would there be some fundamental problem in changing MSGBUF_SIZE > > from a compiled-in constant to a tunable that could be set at the > > loader prompt? > > I didn't see any obvious downside from examining the 8.1-RELEASE > > code ... > I also don't immediately see why that wouldn't work. > Can you try to come up with a patch? I came up with what I think is a start, but it has led to: How do I go about debugging a "Fatal double fault"? A kernel in which I changed only the name built and booted fine, so it seems I can in fact build a working kernel. The next iteration (patch1), where I think I added a tunable (msgbufsize) to the infrastructure but didn't attempt to use it anywhere, also seemed to work. However, when I replaced the various uses of MSGBUF_SIZE with msgbufsize (patch2), it built OK but died very early: OK unload OK boot T_MSGB_SZ /boot/T_MSGB_SZ/kernel text=0x7bdea5 data=0xe7334+0xa3fb0 syms=[0x4+0xa64b0+0x4+0xdc392] / Fatal double fault: eip = 0xc07feb98 esp = 0xc101e000 ebp = 0xc101e004 cpuid = 0; apic id = 00 panic: double fault cpuid = 0 How do I go about tracking this down? --=_4d089a74.3VsRVeW/kwmmuUSPzspeBOJv/FT71OEQDPEttesGTjzsZlxH Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="patch1" --- boot/common/loader.8-81R Sun Jun 13 19:09:06 2010 +++ boot/common/loader.8 Mon Dec 13 21:34:49 2010 @@ -615,6 +615,14 @@ the NBUF parameter will override this limit. Modifies .Dv VM_BCACHE_SIZE_MAX . +.It Va kern.msgbufsize +Sets the size of the kernel message buffer. +The default of 64KB is usually sufficient unless +large amounts of trace data need to be collected +between opportunities to examine the buffer or +dump it to a file. +Modifies kernel option +.Dv MSGBUF_SIZE .It Va machdep.disable_mtrrs Disable the use of i686 MTRRs (x86 only). .It Va net.inet.tcp.tcbhashsize --- boot/forth/loader.conf-81R Sun Jun 13 19:09:06 2010 +++ boot/forth/loader.conf Mon Dec 13 21:50:16 2010 @@ -99,6 +99,7 @@ #kern.maxswzone="" # Set the max swmeta KVA storage #kern.maxtsiz="" # Set the max text size #kern.maxusers="32" # Set size of various static tables +#kern.msgbufsize="" # Set size of kernel message buffer #kern.nbuf="" # Set the number of buffer headers #kern.ncallout="" # Set the maximum # of timer events #kern.ngroups="1023" # Set the maximum # of supplemental groups --- kern/subr_param.c-81R Sun Jun 13 19:09:06 2010 +++ kern/subr_param.c Mon Dec 13 21:46:40 2010 @@ -89,6 +89,7 @@ int nswbuf; long maxswzone; /* max swmeta KVA storage */ long maxbcache; /* max buffer cache KVA storage */ +long msgbufsize; /* size of kernel message buffer */ long maxpipekva; /* Limit on pipe KVA */ int vm_guest; /* Running as virtual machine guest? */ u_long maxtsiz; /* max text size */ @@ -110,6 +111,8 @@ "Maximum memory for swap metadata"); SYSCTL_LONG(_kern, OID_AUTO, maxbcache, CTLFLAG_RDTUN, &maxbcache, 0, "Maximum value of vfs.maxbufspace"); +SYSCTL_LONG(_kern, OID_AUTO, msgbufsize, CTLFLAG_RDTUN, &msgbufsize, 0, + "Size of the kernel message buffer"); SYSCTL_ULONG(_kern, OID_AUTO, maxtsiz, CTLFLAG_RDTUN, &maxtsiz, 0, "Maximum text size"); SYSCTL_ULONG(_kern, OID_AUTO, dfldsiz, CTLFLAG_RDTUN, &dfldsiz, 0, @@ -217,6 +220,10 @@ maxbcache = VM_BCACHE_SIZE_MAX; #endif TUNABLE_LONG_FETCH("kern.maxbcache", &maxbcache); +#ifdef MSGBUF_SIZE + msgbufsize = MSGBUF_SIZE; +#endif + TUNABLE_LONG_FETCH("kern.msgbufsize", &msgbufsize); maxtsiz = MAXTSIZ; TUNABLE_ULONG_FETCH("kern.maxtsiz", &maxtsiz); --- sys/buf.h-81R Sun Jun 13 19:09:06 2010 +++ sys/buf.h Mon Dec 13 21:38:26 2010 @@ -449,6 +449,7 @@ extern int nbuf; /* The number of buffer headers */ extern long maxswzone; /* Max KVA for swap structures */ extern long maxbcache; /* Max KVA for buffer cache */ +extern long msgbufsize; /* size of kernel message buffer */ extern long runningbufspace; extern long hibufspace; extern int dirtybufthresh; --=_4d089a74.3VsRVeW/kwmmuUSPzspeBOJv/FT71OEQDPEttesGTjzsZlxH Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="patch2" --- i386/i386/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ i386/i386/machdep.c Tue Dec 14 20:38:13 2010 @@ -2059,7 +2059,7 @@ physmem = Maxmem; basemem = 0; physmap[0] = init_first << PAGE_SHIFT; - physmap[1] = ptoa(Maxmem) - round_page(MSGBUF_SIZE); + physmap[1] = ptoa(Maxmem) - round_page(msgbufsize); physmap_idx = 0; goto physmap_done; #endif @@ -2445,7 +2445,7 @@ * calculation, etc.). */ while (phys_avail[pa_indx - 1] + PAGE_SIZE + - round_page(MSGBUF_SIZE) >= phys_avail[pa_indx]) { + round_page(msgbufsize) >= phys_avail[pa_indx]) { physmem -= atop(phys_avail[pa_indx] - phys_avail[pa_indx - 1]); phys_avail[pa_indx--] = 0; phys_avail[pa_indx--] = 0; @@ -2454,10 +2454,10 @@ Maxmem = atop(phys_avail[pa_indx]); /* Trim off space for the message buffer. */ - phys_avail[pa_indx] -= round_page(MSGBUF_SIZE); + phys_avail[pa_indx] -= round_page(msgbufsize); /* Map the message buffer. */ - for (off = 0; off < round_page(MSGBUF_SIZE); off += PAGE_SIZE) + for (off = 0; off < round_page(msgbufsize); off += PAGE_SIZE) pmap_kenter((vm_offset_t)msgbufp + off, phys_avail[pa_indx] + off); @@ -2666,7 +2666,7 @@ /* now running on new page tables, configured,and u/iom is accessible */ - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); /* transfer to user mode */ _ucodesel = GSEL(GUCODE_SEL, SEL_UPL); @@ -2921,7 +2921,7 @@ /* now running on new page tables, configured,and u/iom is accessible */ - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); /* make a call gate to reenter kernel with */ gdp = &ldt[LSYS5CALLS_SEL].gd; --- i386/i386/pmap.c-81R Sun Jun 13 19:09:06 2010 +++ i386/i386/pmap.c Tue Dec 14 20:38:17 2010 @@ -448,7 +448,7 @@ /* * msgbufp is used to map the system message buffer. */ - SYSMAP(struct msgbuf *, unused, msgbufp, atop(round_page(MSGBUF_SIZE))) + SYSMAP(struct msgbuf *, unused, msgbufp, atop(round_page(msgbufsize))) /* * KPTmap is used by pmap_kextract(). --- i386/xen/pmap.c-81R Sun Jun 13 19:09:06 2010 +++ i386/xen/pmap.c Tue Dec 14 20:38:09 2010 @@ -465,7 +465,7 @@ /* * msgbufp is used to map the system message buffer. */ - SYSMAP(struct msgbuf *, unused, msgbufp, atop(round_page(MSGBUF_SIZE))) + SYSMAP(struct msgbuf *, unused, msgbufp, atop(round_page(msgbufsize))) /* * ptemap is used for pmap_pte_quick --- sys/msgbuf.h-81R Sun Jun 13 19:09:06 2010 +++ sys/msgbuf.h Tue Dec 14 20:38:03 2010 @@ -54,6 +54,7 @@ #ifdef _KERNEL extern int msgbuftrigger; extern struct msgbuf *msgbufp; +extern long msgbufsize; void msgbufinit(void *ptr, int size); void msgbuf_addchar(struct msgbuf *mbp, int c); --=_4d089a74.3VsRVeW/kwmmuUSPzspeBOJv/FT71OEQDPEttesGTjzsZlxH-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 11:16:47 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B9B5106564A for ; Wed, 15 Dec 2010 11:16:47 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id 8EA7C8FC14 for ; Wed, 15 Dec 2010 11:16:46 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.3) with ESMTP id oBFB46If067854 for ; Wed, 15 Dec 2010 13:04:07 +0200 (EET) (envelope-from mamalos@eng.auth.gr) Message-ID: <4D08A0A1.40205@eng.auth.gr> Date: Wed, 15 Dec 2010 13:04:01 +0200 From: George Mamalakis User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101103 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 11:16:47 -0000 Dear all, I was testing a program that would exhaust all my memory (in C++), and when this would happen, it would call set_new_handler() along with one of my functions that would inform the user about the lack of memory and then it would exit the program. Instead, the program was force-killed by the kernel (signal 9) and I was informed that: "swap zone exhausted, increase kern.maxswzone" on my main console. So far so good. In two other consoles I was running top -P, and vmvstat 5, and their output was: # top -P last pid: 1776; load averages: 1.71, 0.72, 0.40 up 0+00:24:29 12:24:39 34 processes: 2 running, 32 sleeping CPU 0: 2.6% user, 0.0% nice, 88.3% system, 0.0% interrupt, 9.0% idle CPU 1: 0.0% user, 0.0% nice, 39.1% system, 0.0% interrupt, 60.9% idle CPU 2: 0.0% user, 0.0% nice, 2.6% system, 1.5% interrupt, 95.9% idle CPU 3: 0.4% user, 0.0% nice, 89.8% system, 0.0% interrupt, 9.8% idle Mem: 2629M Active, 221M Inact, 966M Wired, 82M Cache, 7280K Buf, 16M Free Swap: 4096M Total, 1821M Used, 2275M Free, 44% Inuse, 196K In, 30M Out FreeBSD/amd64 (example.com) (ttyv2)ATE C TIME WCPU COMMAND 1771 mamalos 1 117 0 573G 3566M CPU1 1 1:48 94.38% memory login: oot 1 44 0 11544K 1176K select 0 0:17 0.29% hald-addon 1535 root 1 44 0 16552K 1436K swread 2 0:03 0.20% hald-addon 1772 mamalos 1 44 0 9364K 2032K CPU3 0 0:02 0.00% top 790 root 1 46 0 8068K 812K select 3 0:01 0.00% moused 1514 root 1 44 0 21696K 1596K wait 0 0:00 0.00% login 1711 mamalos 1 45 0 10148K 0K wait 1 0:00 0.00% 1021 root 1 44 0 7044K 864K zio->i 2 0:00 0.00% syslogd 829 root 1 64 0 3204K 16K select 2 0:00 0.00% devd 1568 root 1 47 0 10148K 964K ttyin 1 0:00 0.00% bash 1530 root 1 44 0 17872K 1108K swread 2 0:00 0.00% hald-runne 1513 root 1 44 0 21696K 0K wait 0 0:00 0.00% 1680 mamalos 1 44 0 10148K 0K wait 3 0:00 0.00% 1512 root 1 44 0 21696K 0K wait 0 0:00 0.00% 1511 root 1 44 0 21696K 0K wait 0 0:00 0.00% and: # vmstat 5 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad4 cd0 in sy cs us sy id 1 0 9 565G 133M 1761 3 4 156 901 13078 0 0 173 1693 1581 0 7i 92 when the program was shut. As you can see (in vmstat's output) avm equals to 565G of memory(?!?!?!), and top shows that the first process (it's called memory) has a size of 573G! moreover, on another terminal I run: # sysctl -a | grep -i swap vm.swap_enabled: 1 vm.nswapdev: 1 vm.swap_async_max: 4 vm.swap_reserved: 544762376192 vm.swap_total: 4294967296 vm.swap_idle_threshold2: 10 vm.swap_idle_threshold1: 2 vm.stats.vm.v_swappgsout: 795224 vm.stats.vm.v_swappgsin: 1188 vm.stats.vm.v_swapout: 200045 vm.stats.vm.v_swapin: 606 vm.disable_swapspace_pageouts: 0 vm.defer_swapspace_pageouts: 0 vm.swap_idle_enabled: 0 where one can see that vm.swap_reserved is equal to 507G whereas the total size (vm.swap_total) is 4G.(?!?!?) As far as my system is concerned: $ uname -a FreeBSD example.com 8.1-STABLE FreeBSD 8.1-STABLE #1: Fri Nov 5 17:27:37 EET 2010 root@:/mnt/obj/mnt/src/sys/GENERIC amd64 and I use zfs on one of my filesystems. So: $ cat /boot/loader.conf zfs_load="YES" vfs.zfs.prefetch_disable=0 nvidia_load="YES" kern.maxfiles="35000" kern.ipc.shmall="65536" atapicam_load=YES snd_hda_load=YES I had noticed in the past that at some moments vmstat would show more memory than what my total memory was, but never sooo much. Is this a bug or am I missing something very fundamental? Thank you all for your time in advance. -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 11:26:29 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84706106567A for ; Wed, 15 Dec 2010 11:26:29 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) by mx1.freebsd.org (Postfix) with ESMTP id F23038FC18 for ; Wed, 15 Dec 2010 11:26:28 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.4/8.14.4) with ESMTP id oBFBQOhi013502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Dec 2010 12:26:24 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.4/8.14.4/Submit) with ESMTP id oBFBQOhv013499 for ; Wed, 15 Dec 2010 12:26:24 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Wed, 15 Dec 2010 12:26:24 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: stable@freebsd.org In-Reply-To: <4D08A0A1.40205@eng.auth.gr> Message-ID: References: <4D08A0A1.40205@eng.auth.gr> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Organization: =?ISO-8859-1?Q?Fagskolen_i_Gj=F8vik?= OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2055831798-228856486-1292412384=:10096" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on mail.fig.ol.no Cc: Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 11:26:29 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-228856486-1292412384=:10096 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Wed, 15 Dec 2010 13:04+0200, George Mamalakis wrote: > I was testing a program that would exhaust all my memory (in C++), > and when this would happen, it would call set_new_handler() along > with one of my functions that would inform the user about the lack > of memory and then it would exit the program. Instead, the program > was force-killed by the kernel (signal 9) and I was informed that: If all your process' memory is exhausted, then there is no memory left for the runtime system for doing I/O and the other stuff you want. Next, unless I'm on drugs, maybe you should call set_new_handler() before you actually run out of memory. Just my $0.02. Trond. -- ---------------------------------------------------------------------- Trond Endrestøl | Trond.Endrestol@fagskolen.gjovik.no ACM, NAS, NUUG, SAGE, USENIX | FreeBSD 8.1-STABLE & Alpine 2.00 --2055831798-228856486-1292412384=:10096-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 11:47:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 783D9106567A for ; Wed, 15 Dec 2010 11:47:32 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BDCD78FC16 for ; Wed, 15 Dec 2010 11:47:31 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA09271; Wed, 15 Dec 2010 13:47:24 +0200 (EET) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1PSppM-000NEH-Fm; Wed, 15 Dec 2010 13:47:24 +0200 Message-ID: <4D08AACB.6060306@freebsd.org> Date: Wed, 15 Dec 2010 13:47:23 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101211 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <4cfc72a5.3nAjkv8mdrO/NrKQ%perryh@pluto.rain.com> <4CFD0633.9060509@freebsd.org> <4d089a74.vwMJkPEIddt7PIxy%perryh@pluto.rain.com> In-Reply-To: <4d089a74.vwMJkPEIddt7PIxy%perryh@pluto.rain.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to debug a double fault? (Re: Could MSGBUF_SIZE be made a loader tunable?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 11:47:32 -0000 on 15/12/2010 12:37 perryh@pluto.rain.com said the following: > Fatal double fault: > eip = 0xc07feb98 > esp = 0xc101e000 > ebp = 0xc101e004 > cpuid = 0; apic id = 00 > panic: double fault > cpuid = 0 > > How do I go about tracking this down? Do you have the standard debugging options in your kernel? http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html BTW, are you sure that you correctly placed initialization of msgbufsize ? I am not saying that you haven't, just make sure that it is set before its first use. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 13:44:33 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C80CD106566B for ; Wed, 15 Dec 2010 13:44:33 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id 46CBC8FC08 for ; Wed, 15 Dec 2010 13:44:33 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.3) with ESMTP id oBFDi1IO082444; Wed, 15 Dec 2010 15:44:02 +0200 (EET) (envelope-from mamalos@eng.auth.gr) Message-ID: <4D08C61C.4090006@eng.auth.gr> Date: Wed, 15 Dec 2010 15:43:56 +0200 From: George Mamalakis User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101103 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: =?UTF-8?B?VHJvbmQgRW5kcmVzdMO4bA==?= References: <4D08A0A1.40205@eng.auth.gr> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 13:44:33 -0000 On 15/12/2010 13:26, Trond Endrestøl wrote: > On Wed, 15 Dec 2010 13:04+0200, George Mamalakis wrote: > >> I was testing a program that would exhaust all my memory (in C++), >> and when this would happen, it would call set_new_handler() along >> with one of my functions that would inform the user about the lack >> of memory and then it would exit the program. Instead, the program >> was force-killed by the kernel (signal 9) and I was informed that: > If all your process' memory is exhausted, then there is no memory left > for the runtime system for doing I/O and the other stuff you want. > Next, unless I'm on drugs, maybe you should call set_new_handler() > before you actually run out of memory. Just my $0.02. > > > Trond. > > > > _______________________________________________ > 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" Trond, My problem was not that the program was force-killed, my problem was that the system reserved 500G+ of swap, even though the total size is 4G. -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 13:52:31 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B686A1065675 for ; Wed, 15 Dec 2010 13:52:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 270E88FC1F for ; Wed, 15 Dec 2010 13:52:30 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id oBFDphnf012827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Dec 2010 15:51:43 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id oBFDphhh058926; Wed, 15 Dec 2010 15:51:43 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id oBFDphLd058925; Wed, 15 Dec 2010 15:51:43 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 15 Dec 2010 15:51:43 +0200 From: Kostik Belousov To: George Mamalakis Message-ID: <20101215135143.GY33073@deviant.kiev.zoral.com.ua> References: <4D08A0A1.40205@eng.auth.gr> <4D08C61C.4090006@eng.auth.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lXBubL3wS507qnlw" Content-Disposition: inline In-Reply-To: <4D08C61C.4090006@eng.auth.gr> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: stable@freebsd.org Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 13:52:31 -0000 --lXBubL3wS507qnlw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 15, 2010 at 03:43:56PM +0200, George Mamalakis wrote: > On 15/12/2010 13:26, Trond Endrest??l wrote: > >On Wed, 15 Dec 2010 13:04+0200, George Mamalakis wrote: > > > >>I was testing a program that would exhaust all my memory (in C++), > >>and when this would happen, it would call set_new_handler() along > >>with one of my functions that would inform the user about the lack > >>of memory and then it would exit the program. Instead, the program > >>was force-killed by the kernel (signal 9) and I was informed that: > >If all your process' memory is exhausted, then there is no memory left > >for the runtime system for doing I/O and the other stuff you want. > >Next, unless I'm on drugs, maybe you should call set_new_handler() > >before you actually run out of memory. Just my $0.02. > > > > > >Trond. > > > > > > > >_______________________________________________ > >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" > Trond, >=20 > My problem was not that the program was force-killed, my problem was=20 > that the system reserved 500G+ of swap, even though the total size is 4G. Read tuning(7), in particular, the description of vm.overcommit sysctl. --lXBubL3wS507qnlw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk0Ix+8ACgkQC3+MBN1Mb4gPjQCeJ2dn1EvNvyyxvaUc6dn1acIo wUEAnjujMA2If/mtVwQIwqJ6npMFmUzK =lNou -----END PGP SIGNATURE----- --lXBubL3wS507qnlw-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 15:29:20 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 789FA1065675 for ; Wed, 15 Dec 2010 15:29:20 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id E21468FC13 for ; Wed, 15 Dec 2010 15:29:19 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.3) with ESMTP id oBFFSX7J002157; Wed, 15 Dec 2010 17:28:33 +0200 (EET) (envelope-from mamalos@eng.auth.gr) Message-ID: <4D08DE9C.1060108@eng.auth.gr> Date: Wed, 15 Dec 2010 17:28:28 +0200 From: George Mamalakis User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101103 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Kostik Belousov References: <4D08A0A1.40205@eng.auth.gr> <4D08C61C.4090006@eng.auth.gr> <20101215135143.GY33073@deviant.kiev.zoral.com.ua> In-Reply-To: <20101215135143.GY33073@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 15:29:20 -0000 On 15/12/2010 15:51, Kostik Belousov wrote: > On Wed, Dec 15, 2010 at 03:43:56PM +0200, George Mamalakis wrote: >> On 15/12/2010 13:26, Trond Endrest??l wrote: >>> On Wed, 15 Dec 2010 13:04+0200, George Mamalakis wrote: >>> >>>> I was testing a program that would exhaust all my memory (in C++), >>>> and when this would happen, it would call set_new_handler() along >>>> with one of my functions that would inform the user about the lack >>>> of memory and then it would exit the program. Instead, the program >>>> was force-killed by the kernel (signal 9) and I was informed that: >>> If all your process' memory is exhausted, then there is no memory left >>> for the runtime system for doing I/O and the other stuff you want. >>> Next, unless I'm on drugs, maybe you should call set_new_handler() >>> before you actually run out of memory. Just my $0.02. >>> >>> >>> Trond. >>> >>> >>> >>> _______________________________________________ >>> 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" >> Trond, >> >> My problem was not that the program was force-killed, my problem was >> that the system reserved 500G+ of swap, even though the total size is 4G. > Read tuning(7), in particular, the description of vm.overcommit sysctl. Thank you Kostik, it proves that I was missing something fundamental after all :) On the other hand, what I noticed was that during the process of allocating the huge amount of memory, root processes got killed, which at first seems rational, on the other hand it is a bit strange. My dmesg shows: pid 1732 (npviewer.bin), uid 1001: exited on signal 11 (core dumped) pid 2227 (npviewer.bin), uid 1001: exited on signal 11 (core dumped) swap zone exhausted, increase kern.maxswzone pid 1544 (console-kit-daemon), uid 0, was killed: out of swap space swap zone exhausted, increase kern.maxswzone pid 2864 (memory), uid 1001, was killed: out of swap space swap zone exhausted, increase kern.maxswzone pid 1676 (gconf-helper), uid 1001, was killed: out of swap space where one can see that pid 1544 was killed before 2864, which is the process that caused all this mess. Yes, I know that I should use limits so as not to allow such things to happen, but on the other hand, if a malicious user causes such a situation he/she may gain access to information through core-dumps on root processes, AND cause DoS attacks. If it were for me, I would sort all processes based on their memory consumption, and start by killing those that have the highest value (top-bottom) that are NOT owned by root (just a thought, without thinking about it too much), so as to prevent such situations from happening. No need to answer my questions, they are rhetorical. I assume that there must be some good reason behind this behavior. Thanx again for all the help. -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 17:00:59 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A83A3106566C; Wed, 15 Dec 2010 17:00:59 +0000 (UTC) (envelope-from jeremie@le-hen.org) Received: from smtpfb1-g21.free.fr (smtpfb1-g21.free.fr [212.27.42.9]) by mx1.freebsd.org (Postfix) with ESMTP id A1C5D8FC13; Wed, 15 Dec 2010 17:00:56 +0000 (UTC) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by smtpfb1-g21.free.fr (Postfix) with ESMTP id 309A7786874; Wed, 15 Dec 2010 17:44:15 +0100 (CET) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id A45B9D4822E; Wed, 15 Dec 2010 17:44:06 +0100 (CET) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id 898C733D1C; Wed, 15 Dec 2010 08:28:37 +0000 (UTC) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id 68EFCA10E3; Wed, 15 Dec 2010 08:28:37 +0000 (UTC) Date: Wed, 15 Dec 2010 09:28:37 +0100 From: Jeremie Le Hen To: freebsd-stable@FreeBSD.org Message-ID: <20101215082837.GA8734@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: pjd@FreeBSD.org, mm@FreeBSD.org Subject: Panic in ZFS layer on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 17:00:59 -0000 Hi, [ Please Cc: me when replying, as I'm not subscribed to -stable@. ] My filer at home runs FreeBSD. A single data RAID-1 zpool with 10~15 datasets, two of them using compression. Over the night, I got the following panic: Tracing pid 0 tid 100111 td 0x86393a00 kdb_enter(809faa5b,809faa5b,80a12e84,cb114aec,0,...) at kdb_enter+0x3a panic(80a12e84,1c000,2e3e8000,80a12e7e,7d0,...) at panic+0x131 kmem_malloc(8169008c,1c000,2,cb114b6c,80909a99,...) at kmem_malloc+0x285 page_alloc(0,1c000,cb114b5f,2,2f0c800,...) at page_alloc+0x27 uma_large_malloc(1c000,2,0,8609b3f0,30,...) at uma_large_malloc+0x4a malloc(1c000,860b2120,2,cb114bb0,8601d36d,...) at malloc+0x7c zfs_kmem_alloc(1c000,2,cb114bf0,8601f77b,1c000,...) at zfs_kmem_alloc+0x20 zio_buf_alloc(1c000,cb114c30,86008817,92c33bd0,cb114bf0,...) at zio_buf_alloc+0x44 zio_compress_data(3,b4264000,20000,0,cb114c58,...) at zio_compress_data+0x8b zio_write_bp_init(92c339c0,92bba254,cb114c80,8071a322,cb114ca0,...) at zio_write_bp_init+0xff zio_execute(92c339c0,8638e0c0,cb114cd0,8071c5f4,92c33c14,...) at zio_execute+0xab taskq_run_safe(92c33c14,1,0,80a8429c,0,...) at taskq_run_safe+0x13 taskqueue_run(8638e0c0,8638e0d8,0,809ef596,0,...) at taskqueue_run+0x15d taskqueue_thread_loop(8638c3d0,cb114d38,8071c72a,0,cb114d20,...) at taskqueue_thread_loop+0xbd fork_exit(8071c72a,8638c3d0,cb114d38) at fork_exit+0x91 fork_trampoline() at fork_trampoline+0x8 I couldn't get a crash dump, sorry. However, I'm still using the same kernel so I can probably use addr2line(1) if you need it. Regards, -- Jeremie Le Hen Humans are born free and equal. But some are more equal than others. Coluche From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 17:29:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1F6810656E2 for ; Wed, 15 Dec 2010 17:29:01 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 17E808FC17 for ; Wed, 15 Dec 2010 17:29:00 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA16546; Wed, 15 Dec 2010 19:28:58 +0200 (EET) (envelope-from avg@freebsd.org) Message-ID: <4D08FAD9.4010300@freebsd.org> Date: Wed, 15 Dec 2010 19:28:57 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Jeremie Le Hen References: <20101215082837.GA8734@felucia.tataz.chchile.org> In-Reply-To: <20101215082837.GA8734@felucia.tataz.chchile.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Panic in ZFS layer on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 17:29:01 -0000 on 15/12/2010 10:28 Jeremie Le Hen said the following: > Hi, > > [ Please Cc: me when replying, as I'm not subscribed to -stable@. ] > > My filer at home runs FreeBSD. A single data RAID-1 zpool with 10~15 > datasets, two of them using compression. Over the night, I got the > following panic: Thanks for the stack trace! But where is the promised panic message? :) I suspect that you ran out of kernel address space. You'd probably have to tune your system and/or add more memory. Please research this topic via mailing lists archives. > Tracing pid 0 tid 100111 td 0x86393a00 > kdb_enter(809faa5b,809faa5b,80a12e84,cb114aec,0,...) at kdb_enter+0x3a > panic(80a12e84,1c000,2e3e8000,80a12e7e,7d0,...) at panic+0x131 > kmem_malloc(8169008c,1c000,2,cb114b6c,80909a99,...) at kmem_malloc+0x285 > page_alloc(0,1c000,cb114b5f,2,2f0c800,...) at page_alloc+0x27 > uma_large_malloc(1c000,2,0,8609b3f0,30,...) at uma_large_malloc+0x4a > malloc(1c000,860b2120,2,cb114bb0,8601d36d,...) at malloc+0x7c > zfs_kmem_alloc(1c000,2,cb114bf0,8601f77b,1c000,...) at > zfs_kmem_alloc+0x20 > zio_buf_alloc(1c000,cb114c30,86008817,92c33bd0,cb114bf0,...) at > zio_buf_alloc+0x44 > zio_compress_data(3,b4264000,20000,0,cb114c58,...) at > zio_compress_data+0x8b > zio_write_bp_init(92c339c0,92bba254,cb114c80,8071a322,cb114ca0,...) at > zio_write_bp_init+0xff > zio_execute(92c339c0,8638e0c0,cb114cd0,8071c5f4,92c33c14,...) at > zio_execute+0xab > taskq_run_safe(92c33c14,1,0,80a8429c,0,...) at taskq_run_safe+0x13 > taskqueue_run(8638e0c0,8638e0d8,0,809ef596,0,...) at taskqueue_run+0x15d > taskqueue_thread_loop(8638c3d0,cb114d38,8071c72a,0,cb114d20,...) at > taskqueue_thread_loop+0xbd > fork_exit(8071c72a,8638c3d0,cb114d38) at fork_exit+0x91 > fork_trampoline() at fork_trampoline+0x8 > > I couldn't get a crash dump, sorry. However, I'm still using the same > kernel so I can probably use addr2line(1) if you need it. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 20:13:57 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95CD11065673 for ; Wed, 15 Dec 2010 20:13:57 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout029.mac.com (asmtpout029.mac.com [17.148.16.104]) by mx1.freebsd.org (Postfix) with ESMTP id 7EFC28FC16 for ; Wed, 15 Dec 2010 20:13:57 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp029.mac.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 64bit)) with ESMTPSA id <0LDH00M9CK78FG30@asmtp029.mac.com> for freebsd-stable@FreeBSD.ORG; Wed, 15 Dec 2010 12:13:57 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1010190000 definitions=main-1012150126 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2010-12-15_10:2010-12-15, 2010-12-15, 1970-01-01 signatures=0 From: Chuck Swiger Date: Wed, 15 Dec 2010 12:13:56 -0800 Message-id: To: FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.1082) Cc: Subject: named: high memory usage...? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 20:13:57 -0000 Hi-- I'd recently updated a machine to 7-STABLE, and I've noticed that named from the base system (which claims to be BIND 9.4-ESV-R4) is using more than twice as much memory as it used to: PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 706 bind 4 4 0 69424K 57292K kqread 0:09 0.00% named It's serving about 20 zones with total record size of less than 100K, and has the following option block set: options { directory "/var/named"; recursive-clients 400; clients-per-query 210; max-clients-per-query 220; max-cache-size 10m; }; This box was previously running FreeBSD-6.4 and dns/bind94 port, and named never crept above 30M VSIZE/RES even under heavy load (ie, "adnslogres -c 100" against a millon line httpd-access.log file); the size above is from named running for about a day, *without* putting any significant load upon the nameserver.... Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 22:55:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 238C6106566B for ; Wed, 15 Dec 2010 22:55:51 +0000 (UTC) (envelope-from jeremie@le-hen.org) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by mx1.freebsd.org (Postfix) with ESMTP id 994478FC19 for ; Wed, 15 Dec 2010 22:55:48 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id 732A1D48094; Wed, 15 Dec 2010 23:55:42 +0100 (CET) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id D101A33D1C; Wed, 15 Dec 2010 22:55:40 +0000 (UTC) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id B186BA10E3; Wed, 15 Dec 2010 22:55:40 +0000 (UTC) Date: Wed, 15 Dec 2010 23:55:40 +0100 From: Jeremie Le Hen To: Andriy Gapon Message-ID: <20101215225540.GD8734@felucia.tataz.chchile.org> References: <20101215082837.GA8734@felucia.tataz.chchile.org> <4D08FAD9.4010300@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D08FAD9.4010300@freebsd.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org, Jeremie Le Hen Subject: Re: Panic in ZFS layer on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 22:55:51 -0000 On Wed, Dec 15, 2010 at 07:28:57PM +0200, Andriy Gapon wrote: > on 15/12/2010 10:28 Jeremie Le Hen said the following: > > Hi, > > > > [ Please Cc: me when replying, as I'm not subscribed to -stable@. ] > > > > My filer at home runs FreeBSD. A single data RAID-1 zpool with 10~15 > > datasets, two of them using compression. Over the night, I got the > > following panic: > > Thanks for the stack trace! > But where is the promised panic message? :) Eheh, sorry for this :-). > I suspect that you ran out of kernel address space. > You'd probably have to tune your system and/or add more memory. > Please research this topic via mailing lists archives. You guessed right! panic: kmem_malloc(114688): kmem_map too small: 775847936 total allocated I think running a 64 bits kernel would help a lot in that case. Unfortunately I don't think my CPU supports the instruction set: CPU: Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz (1869.88-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Family = 6 Model = f Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20000000 AMD Features2=0x1 TSC: P-state invariant I will look into the wiki about ZFS tuning. Thanks, -- Jeremie Le Hen Humans are born free and equal. But some are more equal than others. Coluche From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 23:00:43 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2244410656AC; Wed, 15 Dec 2010 23:00:43 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) by mx1.freebsd.org (Postfix) with ESMTP id E59548FC18; Wed, 15 Dec 2010 23:00:42 +0000 (UTC) Received: from draco.over-yonder.net (c-75-64-226-141.hsd1.ms.comcast.net [75.64.226.141]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id BED2737B48A; Wed, 15 Dec 2010 17:00:41 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 396C261C5C; Wed, 15 Dec 2010 17:00:41 -0600 (CST) Date: Wed, 15 Dec 2010 17:00:41 -0600 From: "Matthew D. Fuller" To: Jeremie Le Hen Message-ID: <20101215230041.GC66337@over-yonder.net> References: <20101215082837.GA8734@felucia.tataz.chchile.org> <4D08FAD9.4010300@freebsd.org> <20101215225540.GD8734@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101215225540.GD8734@felucia.tataz.chchile.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.21-fullermd.4 (2010-09-15) X-Virus-Scanned: clamav-milter 0.96.5 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, Andriy Gapon Subject: Re: Panic in ZFS layer on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 23:00:43 -0000 On Wed, Dec 15, 2010 at 11:55:40PM +0100 I heard the voice of Jeremie Le Hen, and lo! it spake thus: > > I think running a 64 bits kernel would help a lot in that case. > Unfortunately I don't think my CPU supports the instruction set: It does. > AMD Features=0x20000000 LM = Long Mode All the Core 2's are 64-bit capable. I think even the Core's were. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 23:01:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D30B1065697 for ; Wed, 15 Dec 2010 23:01:22 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout023.mac.com (asmtpout023.mac.com [17.148.16.98]) by mx1.freebsd.org (Postfix) with ESMTP id 7120D8FC15 for ; Wed, 15 Dec 2010 23:01:22 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp023.mac.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LDH009RYRY9CY30@asmtp023.mac.com>; Wed, 15 Dec 2010 15:01:22 -0800 (PST) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2010-12-15_12:2010-12-15, 2010-12-15, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1010190000 definitions=main-1012150153 From: Chuck Swiger In-reply-to: <20101215225540.GD8734@felucia.tataz.chchile.org> Date: Wed, 15 Dec 2010 15:01:21 -0800 Message-id: <4FF974FA-2522-4A21-B4BB-DC111FA0FE71@mac.com> References: <20101215082837.GA8734@felucia.tataz.chchile.org> <4D08FAD9.4010300@freebsd.org> <20101215225540.GD8734@felucia.tataz.chchile.org> To: Jeremie Le Hen X-Mailer: Apple Mail (2.1082) Cc: freebsd-stable@freebsd.org, Andriy Gapon Subject: Re: Panic in ZFS layer on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 23:01:22 -0000 Hi-- On Dec 15, 2010, at 2:55 PM, Jeremie Le Hen wrote: > I think running a 64 bits kernel would help a lot in that case. > Unfortunately I don't think my CPU supports the instruction set: > > CPU: Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz (1869.88-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x6f6 Family = 6 Model = f Stepping = 6 > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20000000 Actually, your CPU does support LM (aka AMD64 extension or Intel EM64T). However, IMO you really want to have at least 2GB of RAM at the minimum to do ZFS.... Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 23:08:16 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A91AC106564A; Wed, 15 Dec 2010 23:08:16 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (email2.emsphone.com [199.67.51.116]) by mx1.freebsd.org (Postfix) with ESMTP id 7ACE88FC14; Wed, 15 Dec 2010 23:08:16 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email2.allantgroup.com (8.14.4/8.14.4) with ESMTP id oBFN8DiH068108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Dec 2010 17:08:14 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.4/8.14.4) with ESMTP id oBFN8Do6094556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Dec 2010 17:08:13 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.4/8.14.4/Submit) id oBFN8DNS094555; Wed, 15 Dec 2010 17:08:13 -0600 (CST) (envelope-from dan) Date: Wed, 15 Dec 2010 17:08:13 -0600 From: Dan Nelson To: Andriy Gapon Message-ID: <20101215230812.GB4939@dan.emsphone.com> References: <20101215082837.GA8734@felucia.tataz.chchile.org> <4D08FAD9.4010300@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D08FAD9.4010300@freebsd.org> X-OS: FreeBSD 8.2-PRERELEASE User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.96.4 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (email2.allantgroup.com [199.67.51.78]); Wed, 15 Dec 2010 17:08:14 -0600 (CST) X-Scanned-By: MIMEDefang 2.68 on 199.67.51.78 Cc: freebsd-stable@freebsd.org, Jeremie Le Hen Subject: Re: Panic in ZFS layer on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 23:08:16 -0000 In the last episode (Dec 15), Andriy Gapon said: > on 15/12/2010 10:28 Jeremie Le Hen said the following: > > Hi, > > > > [ Please Cc: me when replying, as I'm not subscribed to -stable@. ] > > > > My filer at home runs FreeBSD. A single data RAID-1 zpool with 10~15 > > datasets, two of them using compression. Over the night, I got the > > following panic: > > Thanks for the stack trace! > But where is the promised panic message? :) > > I suspect that you ran out of kernel address space. > You'd probably have to tune your system and/or add more memory. > Please research this topic via mailing lists archives. > > > Tracing pid 0 tid 100111 td 0x86393a00 > > kdb_enter(809faa5b,809faa5b,80a12e84,cb114aec,0,...) at kdb_enter+0x3a > > panic(80a12e84,1c000,2e3e8000,80a12e7e,7d0,...) at panic+0x131 > > kmem_malloc(8169008c,1c000,2,cb114b6c,80909a99,...) at kmem_malloc+0x285 > > page_alloc(0,1c000,cb114b5f,2,2f0c800,...) at page_alloc+0x27 > > uma_large_malloc(1c000,2,0,8609b3f0,30,...) at uma_large_malloc+0x4a > > malloc(1c000,860b2120,2,cb114bb0,8601d36d,...) at malloc+0x7c > > zfs_kmem_alloc(1c000,2,cb114bf0,8601f77b,1c000,...) at > > zfs_kmem_alloc+0x20 > > zio_buf_alloc(1c000,cb114c30,86008817,92c33bd0,cb114bf0,...) at > > zio_buf_alloc+0x44 > > zio_compress_data(3,b4264000,20000,0,cb114c58,...) at > > zio_compress_data+0x8b The following patch may help you. It helps me :) It converts the zio_buf_alloc() call into a zio_buf_alloc_nowait(), so that if the alloc fails, zio_compress_data() returns failure and zfs writes the block uncompressed instead of panicing. Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c =================================================================== --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c (revision 216418) +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c (working copy) @@ -202,6 +202,20 @@ zio_buf_alloc(size_t size) return (kmem_alloc(size, KM_SLEEP)); } +void * +zio_buf_alloc_nowait(size_t size) +{ +#ifdef ZIO_USE_UMA + size_t c = (size - 1) >> SPA_MINBLOCKSHIFT; + + ASSERT(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT); + + return (kmem_cache_alloc(zio_buf_cache[c], KM_NOSLEEP)); +#else + return (kmem_alloc(size, KM_NOSLEEP)); +#endif +} + /* * Use zio_data_buf_alloc to allocate data. The data will not appear in a * crashdump if the kernel panics. This exists so that we will limit the amount Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio_compress.c =================================================================== --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio_compress.c (revision 216418) +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio_compress.c (working copy) @@ -32,6 +32,12 @@ #include #include +int panics_avoided_by_not_compressing = 0; +SYSCTL_DECL(_vfs_zfs); +SYSCTL_INT(_vfs_zfs, OID_AUTO, compression_panics_avoided, CTLFLAG_RD, + &panics_avoided_by_not_compressing, 0, + "kmem_map panics avoided by skipping compression when memory is low"); + /* * Compression vectors. */ @@ -109,7 +115,17 @@ zio_compress_data(int cpfunc, void *src, uint64_t destbufsize = P2ALIGN(srcsize - (srcsize >> 3), SPA_MINBLOCKSIZE); if (destbufsize == 0) return (0); + +#if 1 + dest = zio_buf_alloc_nowait(destbufsize); + if (dest == 0) + { + panics_avoided_by_not_compressing++; + return (0); + } +#else dest = zio_buf_alloc(destbufsize); +#endif ciosize = ci->ci_compress(src, dest, (size_t)srcsize, (size_t)destbufsize, ci->ci_level); Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h =================================================================== --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h (revision 216418) +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h (working copy) @@ -398,6 +398,7 @@ extern zio_t *zio_unique_parent(zio_t *cio); extern void zio_add_child(zio_t *pio, zio_t *cio); extern void *zio_buf_alloc(size_t size); +extern void *zio_buf_alloc_nowait(size_t size); extern void zio_buf_free(void *buf, size_t size); extern void *zio_data_buf_alloc(size_t size); extern void zio_data_buf_free(void *buf, size_t size); -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 23:12:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BEF61065679 for ; Wed, 15 Dec 2010 23:12:54 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 35C958FC1A for ; Wed, 15 Dec 2010 23:12:53 +0000 (UTC) Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta02.westchester.pa.mail.comcast.net with comcast id jQEp1f0021uE5Es52bCuxx; Wed, 15 Dec 2010 23:12:54 +0000 Received: from koitsu.dyndns.org ([98.248.34.134]) by omta16.westchester.pa.mail.comcast.net with comcast id jbCs1f00J2tehsa3cbCtmQ; Wed, 15 Dec 2010 23:12:54 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 1DF749B422; Wed, 15 Dec 2010 15:12:51 -0800 (PST) Date: Wed, 15 Dec 2010 15:12:51 -0800 From: Jeremy Chadwick To: Jeremie Le Hen Message-ID: <20101215231251.GA2443@icarus.home.lan> References: <20101215082837.GA8734@felucia.tataz.chchile.org> <4D08FAD9.4010300@freebsd.org> <20101215225540.GD8734@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101215225540.GD8734@felucia.tataz.chchile.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, Andriy Gapon Subject: Re: Panic in ZFS layer on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2010 23:12:54 -0000 On Wed, Dec 15, 2010 at 11:55:40PM +0100, Jeremie Le Hen wrote: > On Wed, Dec 15, 2010 at 07:28:57PM +0200, Andriy Gapon wrote: > > on 15/12/2010 10:28 Jeremie Le Hen said the following: > > > Hi, > > > > > > [ Please Cc: me when replying, as I'm not subscribed to -stable@. ] > > > > > > My filer at home runs FreeBSD. A single data RAID-1 zpool with 10~15 > > > datasets, two of them using compression. Over the night, I got the > > > following panic: > > > > Thanks for the stack trace! > > But where is the promised panic message? :) > > Eheh, sorry for this :-). > > > I suspect that you ran out of kernel address space. > > You'd probably have to tune your system and/or add more memory. > > Please research this topic via mailing lists archives. > > You guessed right! > > panic: kmem_malloc(114688): kmem_map too small: 775847936 total allocated Adjust the following two tunables (loader.conf, not sysctl) in combination: vm.kmem_size vfs.zfs.arc_max I strongly recommend setting vfs.zfs.arc_max to about half of your system memory in your case (so, vfs.zfs.arc_max="512M"). For example, on a 4GB system, I use: vm.kmem_size="4096M" vfs.zfs.arc_max="3072M" Make sure vm.kmem_size is larger than arc_max. Other people will advocate increasing your physical RAM, which I agree with, but the problem isn't technically the amount of RAM you have, it's that (paraphrasing to keep it simple) the kernel ran out of usable memory to use, even though the permissible size (vm.kmem_size_max -- note the difference in the tunable) is much larger. So, what I'm saying: you can use the above two tunables I mentioned to effectively ensure you don't encounter this problem. If after tuning you DO encounter this *exact same problem* (kmem_map too small), please report back, as there may be another bug with ARC limiting that needs to be looked at. (Every situation is unique/different) -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 00:20:44 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB5DD106566B for ; Thu, 16 Dec 2010 00:20:44 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id AB9EA8FC0C for ; Thu, 16 Dec 2010 00:20:44 +0000 (UTC) Received: (qmail 18034 invoked by uid 89); 16 Dec 2010 00:20:41 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 16 Dec 2010 00:20:41 -0000 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Dan Allen In-Reply-To: <20101215020253.GA57526@icarus.home.lan> Date: Wed, 15 Dec 2010 17:20:39 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20101215004712.GA56065@icarus.home.lan> <20101215011247.GA56591@icarus.home.lan> <20101215020253.GA57526@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1082) Cc: dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Dec 2010 00:20:45 -0000 On 14 Dec 2010, at 7:02 PM, Jeremy Chadwick wrote: > The design model of these daemons is to assume network connectivity is = working when they start, and netwait > reliably ensures that. Thanks Jeremy for the script. It works like a charm on my system, = fixing the problem. Dan From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 03:03:18 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1577106564A for ; Thu, 16 Dec 2010 03:03:18 +0000 (UTC) (envelope-from nakaji@jp.freebsd.org) Received: from d4407.kankyo-u.ac.jp (d4407.kankyo-u.ac.jp [202.216.78.81]) by mx1.freebsd.org (Postfix) with ESMTP id A637A8FC0A for ; Thu, 16 Dec 2010 03:03:18 +0000 (UTC) X-Virus-Scanned: amavisd-new at d4407.kankyo-u.ac.jp Received: from jimmy.4407.kankyo-u.ac.jp.kankyo-u.ac.jp (localhost [IPv6:::1]) by d4407.kankyo-u.ac.jp (8.14.4/8.14.4) with ESMTP id oBG2AfMb005984 for ; Thu, 16 Dec 2010 11:10:47 +0900 (JST) (envelope-from nakaji@jp.freebsd.org) From: NAKAJI Hiroyuki To: stable@freebsd.org Date: Thu, 16 Dec 2010 11:10:41 +0900 Message-ID: <8662uutqla.fsf@jimmy.4407.kankyo-u.ac.jp> User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: Subject: HELP! /usr/bin/as core dump after 'make world' from RELENG_6 to RELENG_7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Dec 2010 03:03:19 -0000 Hi, I made world from RELENG_6 to RELENG_7 on my FreeBSD/i386 box. make buildworld ... ok make buildkernel ... ok make installkernel ... maybe ok reboot -- -s ... ok mergemaster -p ... ok make installworld ... ok mergemaster ... ok reboot ... ok And then I did make delete-old BATCH_DELETE_OLD_FILES=1 make delete-old-libs BATCH_DELETE_OLD_FILES=1 to update all other packages using "portmaster -a". After all, "portmaster -a" gets a 'cannot compile' error. I found as.core in the WRKDIR and 'signal 11' in dmesg. I tried "gdb /usr/bin/as as.core" and got gdb.core file ... Is there any way to recover from this terrible stuation? BTW, I wonder why. Because a few days ago, I successfully updated my another FreeBSD/pc98 box from older 6.2-STABLE to 7.4-PRERELEASE and then 8.1-PRERELEASE with the same way. Thanks in advance. -- NAKAJI Hiroyuki From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 07:55:29 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F315106566B for ; Thu, 16 Dec 2010 07:55:29 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout025.mac.com (asmtpout025.mac.com [17.148.16.100]) by mx1.freebsd.org (Postfix) with ESMTP id 2ED728FC08 for ; Thu, 16 Dec 2010 07:55:28 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from [17.151.91.229] by asmtp025.mac.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 64bit)) with ESMTPSA id <0LDI000BQGNP6820@asmtp025.mac.com> for stable@freebsd.org; Wed, 15 Dec 2010 23:55:04 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1010190000 definitions=main-1012150262 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2010-12-16_03:2010-12-16, 2010-12-16, 1970-01-01 signatures=0 From: Chuck Swiger In-reply-to: <8662uutqla.fsf@jimmy.4407.kankyo-u.ac.jp> Date: Wed, 15 Dec 2010 23:55:01 -0800 Message-id: <0CF9CB22-76DC-4A56-AD84-D00A8A300CF5@mac.com> References: <8662uutqla.fsf@jimmy.4407.kankyo-u.ac.jp> To: NAKAJI Hiroyuki X-Mailer: Apple Mail (2.1082) Cc: stable@freebsd.org Subject: Re: HELP! /usr/bin/as core dump after 'make world' from RELENG_6 to RELENG_7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Dec 2010 07:55:29 -0000 Hi, Hiroyuki-- On Dec 15, 2010, at 6:10 PM, NAKAJI Hiroyuki wrote: > After all, "portmaster -a" gets a 'cannot compile' error. I found as.core > in the WRKDIR and 'signal 11' in dmesg. > > I tried "gdb /usr/bin/as as.core" and got gdb.core file ... > > Is there any way to recover from this terrible stuation? > > BTW, I wonder why. Because a few days ago, I successfully updated my > another FreeBSD/pc98 box from older 6.2-STABLE to 7.4-PRERELEASE and then > 8.1-PRERELEASE with the same way. The primary way to recover from a problem with an upgrade is to restore your system from the backups that everyone should be taking. If you deleted old libraries, then you've removed the shared libraries older 6.x binaries from ports want. You can probably fix this by installing /usr/ports/misc/compat6x; however, it is better to reinstall all of your installed ports in order to relink against the new 7.x system libraries. Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 09:40:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F410C106564A; Thu, 16 Dec 2010 09:40:40 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id B7A9D8FC12; Thu, 16 Dec 2010 09:40:40 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id oBG9eerj081364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 16 Dec 2010 01:40:40 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id oBG9eeVi081363; Thu, 16 Dec 2010 01:40:40 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA04229; Thu, 16 Dec 10 01:35:02 PST Date: Thu, 16 Dec 2010 01:34:38 -0800 From: perryh@pluto.rain.com To: avg@freebsd.org Message-Id: <4d09dd2e.iVncbZ/gHBXX0WdL%perryh@pluto.rain.com> References: <4cfc72a5.3nAjkv8mdrO/NrKQ%perryh@pluto.rain.com> <4CFD0633.9060509@freebsd.org> <4d089a74.vwMJkPEIddt7PIxy%perryh@pluto.rain.com> <4D08AACB.6060306@freebsd.org> In-Reply-To: <4D08AACB.6060306@freebsd.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to debug a double fault? (Re: Could MSGBUF_SIZE be made a loader tunable?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Dec 2010 09:40:41 -0000 Andriy Gapon wrote: > on 15/12/2010 12:37 perryh@pluto.rain.com said the following: > > Fatal double fault: > > eip = 0xc07feb98 > > esp = 0xc101e000 > > ebp = 0xc101e004 > > cpuid = 0; apic id = 00 > > panic: double fault > > cpuid = 0 > > > > How do I go about tracking this down? > > Do you have the standard debugging options in your kernel? No, it is 8.1-RELEASE GENERIC with only the name changed and the (first attempt) msgbufsize patches applied. I was trying to minimize changes to GENERIC, so as to minimize the opportunity to screw something up, and I had this silly idea that something this simple might "just work." It does occur to me to wonder whether any debugger would be functional this early, before even the first line of the signon message has been displayed. Is it possible, given the loader messages, to come up with a base address which could be used to compare the eip value with the kernel symbol table? Granted this won't provide a traceback, but even knowing in which function it crashed would be a start. > BTW, are you sure that you correctly placed initialization of > msgbufsize ? I am not at all sure of that, and am not sufficiently familiar with the sequence of events early in intiialization to know how to find out -- although I suppose the observed crash might not be altogether surprising if the kernel message buffer got allocated with a zero size :( Apart from the name, msgbufsize is set up in exactly the same way and place -- in init_param1() -- as maxswzone and maxbcache. Perhaps that is not early enough; any idea what would be a better example? From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 09:50:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09A0E106564A for ; Thu, 16 Dec 2010 09:50:54 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4E5AE8FC13 for ; Thu, 16 Dec 2010 09:50:52 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA01485; Thu, 16 Dec 2010 11:50:45 +0200 (EET) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1PTAU0-00015X-QO; Thu, 16 Dec 2010 11:50:44 +0200 Message-ID: <4D09E0F3.5040302@freebsd.org> Date: Thu, 16 Dec 2010 11:50:43 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101211 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <4cfc72a5.3nAjkv8mdrO/NrKQ%perryh@pluto.rain.com> <4CFD0633.9060509@freebsd.org> <4d089a74.vwMJkPEIddt7PIxy%perryh@pluto.rain.com> <4D08AACB.6060306@freebsd.org> <4d09dd2e.iVncbZ/gHBXX0WdL%perryh@pluto.rain.com> In-Reply-To: <4d09dd2e.iVncbZ/gHBXX0WdL%perryh@pluto.rain.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to debug a double fault? (Re: Could MSGBUF_SIZE be made a loader tunable?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Dec 2010 09:50:54 -0000 on 16/12/2010 11:34 perryh@pluto.rain.com said the following: > Andriy Gapon wrote: >> on 15/12/2010 12:37 perryh@pluto.rain.com said the following: >>> Fatal double fault: >>> eip = 0xc07feb98 >>> esp = 0xc101e000 >>> ebp = 0xc101e004 >>> cpuid = 0; apic id = 00 >>> panic: double fault >>> cpuid = 0 >>> >>> How do I go about tracking this down? >> >> Do you have the standard debugging options in your kernel? > > No, it is 8.1-RELEASE GENERIC with only the name changed and the > (first attempt) msgbufsize patches applied. I was trying to > minimize changes to GENERIC, so as to minimize the opportunity > to screw something up, and I had this silly idea that something > this simple might "just work." > > It does occur to me to wonder whether any debugger would be > functional this early, before even the first line of the signon > message has been displayed. Is it possible, given the loader > messages, to come up with a base address which could be used to > compare the eip value with the kernel symbol table? Granted this > won't provide a traceback, but even knowing in which function it > crashed would be a start. You can research this approach, but I would just add KDB+DDB and get a stack trace without sweat. >> BTW, are you sure that you correctly placed initialization of >> msgbufsize ? > > I am not at all sure of that, and am not sufficiently familiar with > the sequence of events early in intiialization to know how to find > out -- although I suppose the observed crash might not be altogether > surprising if the kernel message buffer got allocated with a zero > size :( > > Apart from the name, msgbufsize is set up in exactly the same > way and place -- in init_param1() -- as maxswzone and maxbcache. > Perhaps that is not early enough; any idea what would be a better > example? I don't see any connection between msgbufsize and maxswzone, so I also don't know if that place is early enough. Just try to initialize the variable where it's defined and use TUNABLE_LONG. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 12:44:36 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A0EA106564A; Thu, 16 Dec 2010 12:44:36 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id 2FE278FC0C; Thu, 16 Dec 2010 12:44:36 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 17E3A131FD3; Thu, 16 Dec 2010 13:44:35 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id hl9nCo3F9zAO; Thu, 16 Dec 2010 13:44:32 +0100 (CET) Received: from [10.9.8.1] (188-167-78-139.dynamic.chello.sk [188.167.78.139]) by mail.vx.sk (Postfix) with ESMTPSA id B63C8131FCA; Thu, 16 Dec 2010 13:44:32 +0100 (CET) Message-ID: <4D0A09AF.3040005@FreeBSD.org> Date: Thu, 16 Dec 2010 13:44:31 +0100 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sk; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: New ZFSv28 patchset for 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Dec 2010 12:44:36 -0000 Hi everyone, following the announcement of Pawel Jakub Dawidek (pjd@FreeBSD.org) I am providing a ZFSv28 testing patch for 8-STABLE. Link to the patch: http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.patch.xz Link to mfsBSD ISO files for testing (i386 and amd64): http://mfsbsd.vx.sk/iso/zfs-v28/8.2-beta-zfsv28-amd64.iso http://mfsbsd.vx.sk/iso/zfs-v28/8.2-beta-zfsv28-i386.iso The root password for the ISO files: "mfsroot" The ISO files work on real systems and in virtualbox. They conatin a full install of FreeBSD 8.2-PRERELEASE with ZFS v28, simply use the provided "zfsinstall" script. The patch is against FreeBSD 8-STABLE as of 2010-12-15. When applying the patch be sure to use correct options for patch(1) and make sure the file sys/cddl/compat/opensolaris/sys/sysmacros.h gets deleted: # cd /usr/src # fetch http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.patch.xz # xz -d stable-8-zfsv28-20101215.patch.xz # patch -E -p0 < stable-8-zfsv28-20101215.patch # rm sys/cddl/compat/opensolaris/sys/sysmacros.h >From Pawel's announcement: Some of the changes since the last patchset (zfs_20100831.patch): - Boot support for ZFS v28 (only RAIDZ3 is not yet supported). - Various fixes for the existing ZFS boot code. - Support for sendfile(2) (by avg@). - Userland<->kernel compatibility with v13-v15 (by mm@). - ACL fixes (by trasz@). - Various bug fixes. Please test, test, test. Chances are this is the last patchset before v28 going to HEAD (finally) and after a reasonable testing period into 8-STABLE. Especially test new changes, like boot support and sendfile(2) support. Also be sure to verify if you can import for existing ZFS pools (v13-v15) when running v28 or boot from your existing pools. Please test the (v13-v15) compatibility layer as well: Old usereland + new kernel / old kernel + new userland More information about ZFS on my blog: http://blog.vx.sk From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 13:20:11 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4CA01065694; Thu, 16 Dec 2010 13:20:11 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtpb-ews07.kpnxchange.com (cpsmtpb-ews07.kpnxchange.com [213.75.39.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4D7C58FC17; Thu, 16 Dec 2010 13:20:10 +0000 (UTC) Received: from cpbrm-ews26.kpnxchange.com ([10.94.84.157]) by cpsmtpb-ews07.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Dec 2010 14:08:07 +0100 Received: from CPSMTPM-CMT104.kpnxchange.com ([195.121.3.20]) by cpbrm-ews26.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Dec 2010 14:08:06 +0100 Received: from koko.offrom.nl ([77.170.60.162]) by CPSMTPM-CMT104.kpnxchange.com with Microsoft SMTPSVC(7.0.6001.18000); Thu, 16 Dec 2010 14:08:06 +0100 Received: from squid.home.itmc.RWTH-Aachen.DE (squid.vpn.offrom.nl [10.168.0.72]) by koko.offrom.nl (8.14.3/8.14.3) with ESMTP id oBGD84Pe076099; Thu, 16 Dec 2010 14:08:04 +0100 (CET) (envelope-from willy@vpn.offrom.nl) Received: from willy by squid.home.itmc.RWTH-Aachen.DE with local (Exim 4.72) (envelope-from ) id 1PTDYx-0001ZX-Rh; Thu, 16 Dec 2010 14:08:03 +0100 Date: Thu, 16 Dec 2010 14:08:03 +0100 From: Willy Offermans To: Samba List Message-ID: <20101216130803.GH4765@vpn.offrom.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on koko.offrom.nl X-OriginalArrivalTime: 16 Dec 2010 13:08:06.0594 (UTC) FILETIME=[479A6220:01CB9D22] X-RcptDomain: FreeBSD.ORG Cc: freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Samba upgrade HowTo requested X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 13:20:12 -0000 Dear Samba friends, Last weekend I decided to upgrade the samba server. We were running Samba 3.3 something and FreeBSD portupgrade was complaining that this version should be removed and assumingly replaced by the newest version. I removed the package via portupgrade and installed the 3.5.6 version. The upgrade went quite smoothly in general, but I encountered some difficulties with the printer drivers. Before the upgrade we were able to print on 4 printers. After the upgrade only 1.5 printer was working. 1 Printer worked as expected, 1 printer printed only garbage and 2 printers were not working at all. I only managed to solve the problems by de-installing and re-installing the printer drivers on the samba server. So somehow the databases in /var/db/samba/*.tdb have been messed up. I do not know what went wrong in detail and neither do I know how to prevent these kind of issues in the next upgrade. What is the procedure to upgrade samba to the newest version? How should one proceed and what are the pitfalls? How should we deal with the printer definitions and printer drivers? What should we in general do with the database files, next to backup? And specifically for FreeBSD users: How should we deal with an upgrade of samba via portupgrade? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: Willy@Offermans.Rompen.nl From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 14:49:02 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2C0F106566B; Thu, 16 Dec 2010 14:49:02 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtpb-ews10.kpnxchange.com (cpsmtpb-ews10.kpnxchange.com [213.75.39.15]) by mx1.freebsd.org (Postfix) with ESMTP id 399368FC13; Thu, 16 Dec 2010 14:49:01 +0000 (UTC) Received: from cpbrm-ews13.kpnxchange.com ([10.94.84.144]) by cpsmtpb-ews10.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Dec 2010 15:49:00 +0100 Received: from CPSMTPM-CMT104.kpnxchange.com ([195.121.3.20]) by cpbrm-ews13.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Dec 2010 15:49:00 +0100 Received: from koko.offrom.nl ([77.170.60.162]) by CPSMTPM-CMT104.kpnxchange.com with Microsoft SMTPSVC(7.0.6001.18000); Thu, 16 Dec 2010 15:49:00 +0100 Received: from squid.home.itmc.RWTH-Aachen.DE (squid.vpn.offrom.nl [10.168.0.72]) by koko.offrom.nl (8.14.3/8.14.3) with ESMTP id oBGEmuAe076653; Thu, 16 Dec 2010 15:48:56 +0100 (CET) (envelope-from willy@vpn.offrom.nl) Received: from willy by squid.home.itmc.RWTH-Aachen.DE with local (Exim 4.72) (envelope-from ) id 1PTF8Z-0001fg-EK; Thu, 16 Dec 2010 15:48:55 +0100 Date: Thu, 16 Dec 2010 15:48:55 +0100 From: Willy Offermans To: Peter Trifonov Message-ID: <20101216144855.GJ4765@vpn.offrom.nl> References: <20101216130803.GH4765@vpn.offrom.nl> <005601cb9d2f$6b92aef0$42b80cd0$@dcn.ftk.spbstu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005601cb9d2f$6b92aef0$42b80cd0$@dcn.ftk.spbstu.ru> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on koko.offrom.nl X-OriginalArrivalTime: 16 Dec 2010 14:49:00.0041 (UTC) FILETIME=[5FBD1790:01CB9D30] X-RcptDomain: FreeBSD.ORG Cc: Samba List , freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: [Samba] Samba upgrade HowTo requested X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 14:49:02 -0000 Hello Peter, On Thu, Dec 16, 2010 at 05:42:10PM +0300, Peter Trifonov wrote: > Hi Willy, > > > Last weekend I decided to upgrade the samba server. We were running > > Samba > > 3.3 something and FreeBSD portupgrade was complaining that this version > > should be removed and assumingly replaced by the newest version. I > > removed the package via portupgrade and installed the 3.5.6 version. The > Are you running winbindd on this server? If yes, does it work properly? > In my case it failed to communicate group IDs to the system, so I had to > rollback to v. 3.4.9. > > > And specifically for FreeBSD users: How should we deal with an upgrade of > samba via portupgrade? > I have upgraded it many times before, and in most cases it was just make > deinstall & make reinstall. > > > With best regards, > P. Trifonov Concerning your first question: No, we are not running winbindd, so I cannot tell you if it might work. To your second remark: Well, it might be that it has worked in your case, but certainly not in mine. I do not know what happened to the drivers or database of the drivers, but something was really messed up. I like to clarify this and to put it on a higher level. I like to figure out what the procedure is to follow and how we can inform the users about this procedure. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: Willy@Offermans.Rompen.nl From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 16:07:13 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6A3D106564A for ; Thu, 16 Dec 2010 16:07:13 +0000 (UTC) (envelope-from mvoorhis@cs.wpi.edu) Received: from MAIL1.WPI.EDU (MAIL1.WPI.EDU [130.215.36.91]) by mx1.freebsd.org (Postfix) with ESMTP id A5F088FC13 for ; Thu, 16 Dec 2010 16:07:13 +0000 (UTC) Received: from SMTP.WPI.EDU (SMTP.WPI.EDU [130.215.36.186]) by MAIL1.WPI.EDU (8.14.5.Beta0/8.14.5.Beta0) with ESMTP id oBGG7CkA018033; Thu, 16 Dec 2010 11:07:12 -0500 Received: from APPLIANCE4.WPI.EDU (appliance4.wpi.edu [130.215.36.61]) by SMTP.WPI.EDU (8.14.4/8.14.4) with ESMTP id oBGG7Bki021827; Thu, 16 Dec 2010 11:07:12 -0500 (envelope-from mvoorhis@cs.wpi.edu) Received: from [130.215.28.97] (eressea.wpi.edu [130.215.28.97]) (authenticated authen=mvoorhis) by APPLIANCE4.WPI.EDU (8.14.5.Beta0/8.14.5.Beta0) with ESMTP id oBGG7BpV013112 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 16 Dec 2010 11:07:11 -0500 Message-ID: <4D0A392F.2070204@cs.wpi.edu> Date: Thu, 16 Dec 2010 11:07:11 -0500 From: Michael Voorhis User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Jeremy Chadwick , freebsd-stable@freebsd.org References: <20101215004712.GA56065@icarus.home.lan> In-Reply-To: <20101215004712.GA56065@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Dec 2010 16:07:14 -0000 My high-tech solution to NTPDATE (et.al.) running before the link was up was to edit /etc/rc.d/NETWORKING and append these two lines at the bottom of the file: ====== /bin/echo "Waiting 10s for network link to wake up." /bin/sleep 10 ====== This has solved this startup problem in all the cases where it had previously been a problem. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 16:56:20 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AABC01065670 for ; Thu, 16 Dec 2010 16:56:20 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 278AF8FC1F for ; Thu, 16 Dec 2010 16:56:19 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id oBGGu1Z9096115; Thu, 16 Dec 2010 17:56:16 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id oBGGu0ns096112; Thu, 16 Dec 2010 17:56:00 +0100 (CET) (envelope-from olli) Date: Thu, 16 Dec 2010 17:56:00 +0100 (CET) Message-Id: <201012161656.oBGGu0ns096112@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, mamalos@eng.auth.gr In-Reply-To: <4D08DE9C.1060108@eng.auth.gr> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Thu, 16 Dec 2010 17:56:16 +0100 (CET) Cc: Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, mamalos@eng.auth.gr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 16:56:20 -0000 George Mamalakis wrote: > My dmesg shows: > > pid 1732 (npviewer.bin), uid 1001: exited on signal 11 (core dumped) > pid 2227 (npviewer.bin), uid 1001: exited on signal 11 (core dumped) > swap zone exhausted, increase kern.maxswzone > pid 1544 (console-kit-daemon), uid 0, was killed: out of swap space > swap zone exhausted, increase kern.maxswzone > pid 2864 (memory), uid 1001, was killed: out of swap space > swap zone exhausted, increase kern.maxswzone > pid 1676 (gconf-helper), uid 1001, was killed: out of swap space > > where one can see that pid 1544 was killed before 2864, which is the > process that caused all this mess. Yes, I know that I should use limits > so as not to allow such things to happen, but on the other hand, if a > malicious user causes such a situation he/she may gain access to > information through core-dumps on root processes, AND cause DoS attacks. No. First, when the kernel kills processes because it runs out of swap space, it uses SIGKILL which does _not_ cause a core dump to be written. Second, core dumps are always created with permissions 0600, i.e. they are only readable by the owner of the process. Of course, any user who can run a machine out of memory can cause a DoS attack by doing this. That's the reason why resource limits exist. > If it were for me, I would sort all processes based on their memory > consumption, and start by killing those that have the highest value > (top-bottom) that are NOT owned by root (just a thought, without > thinking about it too much), so as to prevent such situations from > happening. It is very non-trivial to find a generic algorithm that kills the "right" process in such a situation. For example, an attacker could start a lot of small processes that allocate memory. That's the reason why an admin should always configure resource limits approprately. The kernel's killing feature should only be regarded as the very last emergency break, which basically exists only to prevent a reboot. If you're interested, you can find the selection algorithm for processes to kill in the vm_pageout_oom() function in src/sys/vm/vm_pageout.c. Basically, it selects the process that consumes the most physical memory (RAM + swap), not counting the virtual size of the process. Also, some processes are excluded, such as system processes and protected processes (cron and sshd, for example). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-stable@FreeBSD.ORG Thu Dec 16 19:43:09 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A8F2106564A for ; Thu, 16 Dec 2010 19:43:09 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id 9392B8FC0A for ; Thu, 16 Dec 2010 19:43:08 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.3) with ESMTP id oBGJh2KH061639; Thu, 16 Dec 2010 21:43:02 +0200 (EET) (envelope-from mamalos@eng.auth.gr) Message-ID: <4D0A6BC1.9040201@eng.auth.gr> Date: Thu, 16 Dec 2010 21:42:57 +0200 From: George Mamalakis User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101103 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, mamalos@eng.auth.gr References: <201012161656.oBGGu0ns096112@lurza.secnetix.de> In-Reply-To: <201012161656.oBGGu0ns096112@lurza.secnetix.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Oliver Fromme Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Dec 2010 19:43:09 -0000 On 16/12/2010 18:56, Oliver Fromme wrote: > George Mamalakis wrote: > > My dmesg shows: > > > > pid 1732 (npviewer.bin), uid 1001: exited on signal 11 (core dumped) > > pid 2227 (npviewer.bin), uid 1001: exited on signal 11 (core dumped) > > swap zone exhausted, increase kern.maxswzone > > pid 1544 (console-kit-daemon), uid 0, was killed: out of swap space > > swap zone exhausted, increase kern.maxswzone > > pid 2864 (memory), uid 1001, was killed: out of swap space > > swap zone exhausted, increase kern.maxswzone > > pid 1676 (gconf-helper), uid 1001, was killed: out of swap space > > > > where one can see that pid 1544 was killed before 2864, which is the > > process that caused all this mess. Yes, I know that I should use limits > > so as not to allow such things to happen, but on the other hand, if a > > malicious user causes such a situation he/she may gain access to > > information through core-dumps on root processes, AND cause DoS attacks. > > No. First, when the kernel kills processes because it runs > out of swap space, it uses SIGKILL which does _not_ cause > a core dump to be written. Second, core dumps are always > created with permissions 0600, i.e. they are only readable > by the owner of the process. > > Of course, any user who can run a machine out of memory can > cause a DoS attack by doing this. That's the reason why > resource limits exist. > > > If it were for me, I would sort all processes based on their memory > > consumption, and start by killing those that have the highest value > > (top-bottom) that are NOT owned by root (just a thought, without > > thinking about it too much), so as to prevent such situations from > > happening. > > It is very non-trivial to find a generic algorithm that > kills the "right" process in such a situation. For example, > an attacker could start a lot of small processes that > allocate memory. That's the reason why an admin should > always configure resource limits approprately. The kernel's > killing feature should only be regarded as the very last > emergency break, which basically exists only to prevent a > reboot. > > If you're interested, you can find the selection algorithm > for processes to kill in the vm_pageout_oom() function in > src/sys/vm/vm_pageout.c. Basically, it selects the process > that consumes the most physical memory (RAM + swap), not > counting the virtual size of the process. Also, some > processes are excluded, such as system processes and > protected processes (cron and sshd, for example). > > Best regards > Oliver > Oliver, thanx for your comments. I know it is difficult to choose which process to kill and how to be "fair" during such a killing procedure. Nevertheless, I would assume that all non-root processes would have higher priority to get killed, and that root's processes would get killed last. I understand your comments completely, but I was just so surprised when I realized how easy it was for me to kill root processes on my system. Thanx again and best regards! mamalos -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Fri Dec 17 01:10:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E43AA106566C for ; Fri, 17 Dec 2010 01:10:32 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 919BE8FC16 for ; Fri, 17 Dec 2010 01:10:32 +0000 (UTC) Received: by ywp6 with SMTP id 6so74485ywp.13 for ; Thu, 16 Dec 2010 17:10:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=X28Nglm4NRlpTKI1+K1NaXo7x0iVPGBeP+Ifna5LvTY=; b=sAM9s1L3AHd9E9V4+e86uJCFOp7xQ3TU6uzaoBhpHamyWXc0ouMHohmwaAeNT4T4l+ bRumGimecPmMBEiAzHd0zSOH9lR5ypvVsYPbCfv+QDNmN4pkDRnFZ9J/WkVO0HLCTS0l +LzqM/VrCSocl8w7QhFpSowFvqxOD/HXUlCaw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=MDKE5Y31UJsYUU+24om8O8NswjoAKs88KdUV0VEp0yH/GC5zIkjAuVYaj8dmDto40O T+udkCe/UIiGltiZTSUFqQbDWtNGp6JG+CNrraBAQ68TV/1ZDZo7wcUviUHUagq1n0r4 u1SALBqQ/U8QSgY4qZWKEOItCgDnBT5z1YjDg= Received: by 10.150.54.13 with SMTP id c13mr1930966yba.331.1292548231556; Thu, 16 Dec 2010 17:10:31 -0800 (PST) Received: from centel.dataix.local (adsl-99-109-125-135.dsl.klmzmi.sbcglobal.net [99.109.125.135]) by mx.google.com with ESMTPS id r24sm5145092yba.6.2010.12.16.17.10.28 (version=SSLv3 cipher=RC4-MD5); Thu, 16 Dec 2010 17:10:29 -0800 (PST) Sender: "J. Hellenthal" Message-ID: <4D0AB882.5090800@DataIX.net> Date: Thu, 16 Dec 2010 20:10:26 -0500 From: jhell Organization: http://www.DataIX.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101210 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Kostik Belousov References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> <20101212084327.GS33073@deviant.kiev.zoral.com.ua> In-Reply-To: <20101212084327.GS33073@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Dec 2010 01:10:33 -0000 On 12/12/2010 03:43, Kostik Belousov wrote: > On Sat, Dec 11, 2010 at 07:37:51PM -0500, Mike Tancsa wrote: >> On 12/11/2010 6:22 PM, Kostik Belousov wrote: >>> On Sat, Dec 11, 2010 at 06:08:08PM -0500, Mike Tancsa wrote: >>>> On 12/11/2010 11:01 AM, Kostik Belousov wrote: >>>>> >>>>> I have no access to AESNI hardware. For start, you may use >>>>> src/tools/tools/crypto/cryptotest >>>>> to somewhat verify the sanity of the driver. >>>> >>>> I doesnt happen every time, but one out of 5 or so >>>> >>> First, which arch is it, amd64 or i386 ? >>> >>> Also, please revert r216162 and do the same tests. >> >> Hi, >> Its AMD64, but i386 seems to be impacted too. I am not sure how to >> revert to a specific commit, but for now I csup'd with a date tag of >> >> *date=2010.12.02.23.00.00 >> >> which is a day before >> http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-December/004338.html >> >> >> And that seems to fix it! >> >> I have been running >> cryptotest -c -z -t 10 >> in a loop for the past 10min and not one error. > > Please try this patch on the latest HEAD or RELENG_8. > > diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c > index 482b5da..1b493b4 100644 > --- a/sys/amd64/amd64/fpu.c > +++ b/sys/amd64/amd64/fpu.c > @@ -426,7 +426,9 @@ fpudna(void) > fxrstor(&fpu_initialstate); > if (pcb->pcb_initial_fpucw != __INITIAL_FPUCW__) > fldcw(pcb->pcb_initial_fpucw); > - fpuuserinited(curthread); > + pcb->pcb_flags |= PCB_FPUINITDONE; > + if (PCB_USER_FPU(pcb)) > + pcb->pcb_flags |= PCB_USERFPUINITDONE; > } else > fxrstor(pcb->pcb_save); > critical_exit(); > diff --git a/sys/i386/isa/npx.c b/sys/i386/isa/npx.c > index 9ec5d25..f314e44 100644 > --- a/sys/i386/isa/npx.c > +++ b/sys/i386/isa/npx.c > @@ -684,7 +684,9 @@ npxdna(void) > fpurstor(&npx_initialstate); > if (pcb->pcb_initial_npxcw != __INITIAL_NPXCW__) > fldcw(pcb->pcb_initial_npxcw); > - npxuserinited(curthread); > + pcb->pcb_flags |= PCB_NPXINITDONE; > + if (PCB_USER_FPU(pcb)) > + pcb->pcb_flags |= PCB_NPXUSERINITDONE; > } else { > /* > * The following fpurstor() may cause an IRQ13 when the Regarding this patch(r216455) and r216162 I have had to back both of them out of my local tree to avoid panics on a ZFS & UFS2 i386 system. With the following panic strings: Dumptime: Thu Dec 9 08:37:40 2010 Panic String: double fault Dumptime: Thu Dec 9 08:41:57 2010 Panic String: page fault Dumptime: Fri Dec 10 00:23:35 2010 Panic String: free: address 0x85ceb000(0x85ceb000) has not been allocated. Dumptime: Fri Dec 10 14:37:33 2010 Panic String: page fault Dumptime: Sat Dec 11 04:10:01 2010 Panic String: vm_fault: fault on nofault entry, addr: 8289c000 Dumptime: Sun Dec 12 23:45:01 2010 Panic String: page fault Dumptime: Tue Dec 14 01:32:09 2010 Panic String: page fault Dumptime: Tue Dec 14 16:46:33 2010 Panic String: general protection fault Dumptime: Thu Dec 16 10:03:15 2010 Panic String: vm_fault: fault on nofault entry, addr: b3811000 Seems to be caused by r216162 or directly related to it. If further information is needed let me know. Ill be around here for the next few hours. -- jhell,v From owner-freebsd-stable@FreeBSD.ORG Fri Dec 17 01:14:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AD63106566B for ; Fri, 17 Dec 2010 01:14:51 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 186238FC17 for ; Fri, 17 Dec 2010 01:14:50 +0000 (UTC) Received: by ywp6 with SMTP id 6so75721ywp.13 for ; Thu, 16 Dec 2010 17:14:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=UstT52AZh9LLReh8UHnvnGHhOfJlNV6j/h6z9cxUv9I=; b=DBeSEJ7Nw2lfG7mPDWaYEklCFNsOgGKdmEeZKtGjXpEJ/X2hzaEjGyT/UKpqbtXz7/ 9sKpqpvnCWxYxoBWbbXjhXdhFuvhxDWnmtlRiEO3xDF7/Ew+mnLnlJ8XYUvUmx0Afq85 XRWYn2NUmkrx2HvI9vcboOZ8NoIqF/Ch+IO+0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=rKjmce6mTrWn41s4+xAod+K4LuaTHLdesbNZun5YGjw2aFXl9a3JWr6suOlMlB12ku oO3Rp/nNP1DT/HyRwGMCMKXCdcxbnl9/Wc9cYpY8cNhUXbVm1d2muLturJeXw3gI1PcH gokFsbp9CZyUCP/vaIEoTH6uuZzhLmx3P6RkQ= Received: by 10.90.87.8 with SMTP id k8mr1596467agb.6.1292548490311; Thu, 16 Dec 2010 17:14:50 -0800 (PST) Received: from centel.dataix.local (adsl-99-109-125-135.dsl.klmzmi.sbcglobal.net [99.109.125.135]) by mx.google.com with ESMTPS id e24sm3531346ana.22.2010.12.16.17.14.48 (version=SSLv3 cipher=RC4-MD5); Thu, 16 Dec 2010 17:14:49 -0800 (PST) Sender: "J. Hellenthal" Message-ID: <4D0AB987.5090000@DataIX.net> Date: Thu, 16 Dec 2010 20:14:47 -0500 From: jhell Organization: http://www.DataIX.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101210 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Kostik Belousov References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> <20101212084327.GS33073@deviant.kiev.zoral.com.ua> <4D0AB882.5090800@DataIX.net> In-Reply-To: <4D0AB882.5090800@DataIX.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Dec 2010 01:14:51 -0000 On 12/16/2010 20:10, jhell wrote: > Regarding this patch(r216455) and r216162 I have had to back both of > them out of my local tree to avoid panics on a ZFS & UFS2 i386 system. > > With the following panic strings: > Dumptime: Thu Dec 9 08:37:40 2010 > Panic String: double fault > Dumptime: Thu Dec 9 08:41:57 2010 > Panic String: page fault > Dumptime: Fri Dec 10 00:23:35 2010 > Panic String: free: address 0x85ceb000(0x85ceb000) has not been allocated. > Dumptime: Fri Dec 10 14:37:33 2010 > Panic String: page fault > Dumptime: Sat Dec 11 04:10:01 2010 > Panic String: vm_fault: fault on nofault entry, addr: 8289c000 > Dumptime: Sun Dec 12 23:45:01 2010 > Panic String: page fault > Dumptime: Tue Dec 14 01:32:09 2010 > Panic String: page fault > Dumptime: Tue Dec 14 16:46:33 2010 > Panic String: general protection fault > Dumptime: Thu Dec 16 10:03:15 2010 > Panic String: vm_fault: fault on nofault entry, addr: b3811000 > > > Seems to be caused by r216162 or directly related to it. If further > information is needed let me know. Ill be around here for the next few > hours. > PS: Also when the system crashes with the above panic strings /boot/zfs/zpool.cache ends up corrupt leaving me with the need to boot from a good kernel and force import the pool. Also scrubs with the two revs end up with checksum errors all over the place. Without it everything returns to normal. -- jhell,v From owner-freebsd-stable@FreeBSD.ORG Fri Dec 17 10:26:19 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3190E106564A; Fri, 17 Dec 2010 10:26:19 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtpb-ews09.kpnxchange.com (cpsmtpb-ews09.kpnxchange.com [213.75.39.14]) by mx1.freebsd.org (Postfix) with ESMTP id AC4668FC15; Fri, 17 Dec 2010 10:26:18 +0000 (UTC) Received: from cpbrm-ews07.kpnxchange.com ([10.94.84.138]) by cpsmtpb-ews09.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 17 Dec 2010 11:26:17 +0100 Received: from CPSMTPM-CMT108.kpnxchange.com ([195.121.3.24]) by cpbrm-ews07.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 17 Dec 2010 11:26:16 +0100 Received: from koko.offrom.nl ([77.170.60.162]) by CPSMTPM-CMT108.kpnxchange.com with Microsoft SMTPSVC(7.0.6001.18000); Fri, 17 Dec 2010 11:26:16 +0100 Received: from squid.home.itmc.RWTH-Aachen.DE (squid.vpn.offrom.nl [10.168.0.72]) by koko.offrom.nl (8.14.3/8.14.3) with ESMTP id oBHAQDhU083170; Fri, 17 Dec 2010 11:26:13 +0100 (CET) (envelope-from willy@vpn.offrom.nl) Received: from willy by squid.home.itmc.RWTH-Aachen.DE with local (Exim 4.72) (envelope-from ) id 1PTXVs-000269-NW; Fri, 17 Dec 2010 11:26:12 +0100 Date: Fri, 17 Dec 2010 11:26:12 +0100 From: Willy Offermans To: tms3@tms3.com Message-ID: <20101217102612.GC7694@vpn.offrom.nl> References: <4d0a2fd5.50f.2ce7dc40.5721f9f0@tms3.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4d0a2fd5.50f.2ce7dc40.5721f9f0@tms3.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_FILL_THIS_FORM_SHORT,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on koko.offrom.nl X-OriginalArrivalTime: 17 Dec 2010 10:26:16.0289 (UTC) FILETIME=[D6392D10:01CB9DD4] X-RcptDomain: FreeBSD.ORG Cc: Samba List , freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: [Samba] Samba upgrade HowTo requested X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 10:26:19 -0000 Hello tms3, On Thu, Dec 16, 2010 at 07:27:17AM -0800, tms3@tms3.com wrote: > > > > > > >Well, it might be that it has worked in your case, but certainly > >not in > >mine. I do not know what happened to the drivers or database of > >the drivers, but > >something was really messed up. I like to clarify this and to put > >it on a > >higher level. I like to figure out what the procedure is to follow > >and how > >we can inform the users about this procedure. > > Well, it might do you well to go over the list of dependencies that > the port installed initially, and upgrade those components as well. > I'm not sure what is NOT working for you, but as a general rule, I > try to keep those dependecies up to date. > > > > > > > > > >-- I do not think that this issue is related to dependencies. Of course I need to be sure that the dependencies are correctly installed as well, but this job is accomplished by ``portupgrade -R -N'' quite well. No, the real problem lays in the settings and databases created in a previous version of samba, which will be lost, altered or corrupted upon an upgrade. To phrase the questions again? Is there a procedure on how to upgrade samba to a newer version? How can the ignorant user be informed when using portupgrade? I'm sorry, I just recall the UPDATING file in /usr/ports/. The following is a cut from this file: 20101026: AFFECTS: users of net/samba35 AUTHOR: Timur Bakeyev This is the latest stable release of the Samba3 distribution. It has been extended with the experimental support of the NFS4-like ACLs on ZFS partitions, thanks to the sysutils/libsunacl library by Edward Tomasz Napierala(trasz). This support haven't been tested thoroughly, so try it on your own risk. This port reverted back to the pre- net/samba34 layout of the directories and now they are again $PREFIX/etc/samba, /var/run/samba, /var/log/samba, /var/db/samba and /var/spool/samba respectively. In case, you are upgrading from net/samba34, please rename corresponding samba34/ subdirectories into samba/ ones. Upgrades from older versions of Samba and fresh installations should be seamless. Especially the last sentence is of interest. I upgraded from samba 3.3.x to 3.5.6 and went smoothly in general, but only the printer drivers were messed up. Maybe this behavior is not covered by the information in UPDATING. Anyway, to my opinion there is a need for information on how to upgrade samba. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy ************************************* Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut für Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-150 D-52074 Aachen, Germany Phone: +49 241 80 28592 Fax: +49 241 80 22593 Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: Willy@Offermans.Rompen.nl e-mail: Willy.Offermans@CatalyticCenter.RWTH-Aachen.de From owner-freebsd-stable@FreeBSD.ORG Fri Dec 17 10:38:36 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9374106566B; Fri, 17 Dec 2010 10:38:36 +0000 (UTC) (envelope-from romain.garbage@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6DB948FC0A; Fri, 17 Dec 2010 10:38:36 +0000 (UTC) Received: by yxh35 with SMTP id 35so237493yxh.13 for ; Fri, 17 Dec 2010 02:38:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Rf4Jb5JZNN/5h05NPYKI9iWMwPlKKwsLZG2nN90P0ac=; b=gWQlN/ZvUYOgMSD1rTcHix4uixuD33fdxOxuTC7VfeQJmg8qfVQGRPVoXXVkq+HmhL FtgMMDQhvqfg0EYLwfVdzV7/BumN/c7jxVPjhpBBirOTms/xogzeQELr3rbFvRAjo5A8 05RVtCk+isiVcNhk6g1fU/O23FY19nquUUN2M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=UPGEdhA17Zz4loDt+s4thkRM3sn17eYD7zowWFVl7P055mb6+yg9dm9z44xnREbJrL uuITxWwGXBuqFbvkdJSxx+V/ZC9f2KJXI4/nz31PCNjaWqcnNG3YXIMmsoiaKpeY8Oaa FsvmxXK3j3WeLj3Dh8d2JORkuDzvK+9RojuJY= MIME-Version: 1.0 Received: by 10.90.68.8 with SMTP id q8mr1963438aga.159.1292580732068; Fri, 17 Dec 2010 02:12:12 -0800 (PST) Received: by 10.91.213.13 with HTTP; Fri, 17 Dec 2010 02:12:12 -0800 (PST) In-Reply-To: <4D0A09AF.3040005@FreeBSD.org> References: <4D0A09AF.3040005@FreeBSD.org> Date: Fri, 17 Dec 2010 11:12:12 +0100 Message-ID: From: Romain Garbage To: Martin Matuska Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Dec 2010 10:38:36 -0000 2010/12/16 Martin Matuska : > Hi everyone, > > following the announcement of Pawel Jakub Dawidek (pjd@FreeBSD.org) I am > providing a ZFSv28 testing patch for 8-STABLE. > > Link to the patch: > > http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.pa= tch.xz > > Link to mfsBSD ISO files for testing (i386 and amd64): > =C2=A0 =C2=A0http://mfsbsd.vx.sk/iso/zfs-v28/8.2-beta-zfsv28-amd64.iso > =C2=A0 =C2=A0http://mfsbsd.vx.sk/iso/zfs-v28/8.2-beta-zfsv28-i386.iso > > The root password for the ISO files: "mfsroot" > The ISO files work on real systems and in virtualbox. > They conatin a full install of FreeBSD 8.2-PRERELEASE with ZFS v28, > simply use the provided "zfsinstall" script. > > The patch is against FreeBSD 8-STABLE as of 2010-12-15. > > When applying the patch be sure to use correct options for patch(1) > and make sure the file sys/cddl/compat/opensolaris/sys/sysmacros.h gets > deleted: > > =C2=A0 =C2=A0# cd /usr/src > =C2=A0 =C2=A0# fetch > http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.pa= tch.xz > =C2=A0 =C2=A0# xz -d stable-8-zfsv28-20101215.patch.xz > =C2=A0 =C2=A0# patch -E -p0 < stable-8-zfsv28-20101215.patch > =C2=A0 =C2=A0# rm sys/cddl/compat/opensolaris/sys/sysmacros.h Patch seemed to apply fine against yesterday evening (2010-12-16) 8-STABLE, world and kernel compiled fine, and booting from mirrored pool v15 was also fine. Cheers, Romain From owner-freebsd-stable@FreeBSD.ORG Fri Dec 17 11:37:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CDB31065693; Fri, 17 Dec 2010 11:37:40 +0000 (UTC) (envelope-from bamston@reactor-xg.kiev.ua) Received: from mail.reactor-xg.kiev.ua (reactor-xg.kiev.ua [62.80.166.14]) by mx1.freebsd.org (Postfix) with ESMTP id 665A68FC08; Fri, 17 Dec 2010 11:37:38 +0000 (UTC) Received: from mail.reactor-xg.kiev.ua (mail.reactor-xg.kiev.ua [62.80.166.14]) by mail.reactor-xg.kiev.ua (Reactor-XG Mailer System) with ESMTP id oBHB4VJO088719; Fri, 17 Dec 2010 13:04:31 +0200 (EET) (envelope-from bamston@reactor-xg.kiev.ua) Authentication-Results: mail.reactor-xg.kiev.ua; sender-id=pass header.from=bamston@reactor-xg.kiev.ua; auth=pass (PLAIN); spf=pass smtp.mfrom=bamston@reactor-xg.kiev.ua Message-ID: <4D0B43BF.8050100@reactor-xg.kiev.ua> Date: Fri, 17 Dec 2010 13:04:31 +0200 From: "Andrei V. Lavreniyuk" Organization: Technica-03, Inc. User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.9.2.13) Gecko/20101213 Thunderbird/3.1.7 MIME-Version: 1.0 To: Romain Garbage References: <4D0A09AF.3040005@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Fri, 17 Dec 2010 12:01:52 +0000 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Martin Matuska Subject: Re: New ZFSv28 patchset for 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrei Lavreniyuk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 11:37:40 -0000 17.12.2010 12:12, Romain Garbage ÐÉÛÅÔ: >> following the announcement of Pawel Jakub Dawidek (pjd@FreeBSD.org) I am >> providing a ZFSv28 testing patch for 8-STABLE. >> >> Link to the patch: >> >> http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.patch.xz >> >> Link to mfsBSD ISO files for testing (i386 and amd64): >> http://mfsbsd.vx.sk/iso/zfs-v28/8.2-beta-zfsv28-amd64.iso >> http://mfsbsd.vx.sk/iso/zfs-v28/8.2-beta-zfsv28-i386.iso >> >> The root password for the ISO files: "mfsroot" >> The ISO files work on real systems and in virtualbox. >> They conatin a full install of FreeBSD 8.2-PRERELEASE with ZFS v28, >> simply use the provided "zfsinstall" script. >> >> The patch is against FreeBSD 8-STABLE as of 2010-12-15. >> >> When applying the patch be sure to use correct options for patch(1) >> and make sure the file sys/cddl/compat/opensolaris/sys/sysmacros.h gets >> deleted: >> >> # cd /usr/src >> # fetch >> http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.patch.xz >> # xz -d stable-8-zfsv28-20101215.patch.xz >> # patch -E -p0< stable-8-zfsv28-20101215.patch >> # rm sys/cddl/compat/opensolaris/sys/sysmacros.h > > Patch seemed to apply fine against yesterday evening (2010-12-16) > 8-STABLE, world and kernel compiled fine, and booting from mirrored > pool v15 was also fine. ...booting from RAIDZ2 pool v15 was bad... :( --- Best regards, Andrei Lavreniyuk. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 17 14:01:14 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FB4D1065674 for ; Fri, 17 Dec 2010 14:01:14 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id EA0838FC16 for ; Fri, 17 Dec 2010 14:01:13 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:5022:4efd:b73a:4846] ([IPv6:2607:f3e0:0:4:5022:4efd:b73a:4846]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oBHE1A76099177 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 17 Dec 2010 09:01:11 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D0B6D26.7030808@sentex.net> Date: Fri, 17 Dec 2010 09:01:10 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: jhell References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> <20101212084327.GS33073@deviant.kiev.zoral.com.ua> <4D0AB882.5090800@DataIX.net> <4D0AB987.5090000@DataIX.net> In-Reply-To: <4D0AB987.5090000@DataIX.net> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: Kostik Belousov , Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Dec 2010 14:01:14 -0000 On 12/16/2010 8:14 PM, jhell wrote: > On 12/16/2010 20:10, jhell wrote: >> Regarding this patch(r216455) and r216162 I have had to back both of >> them out of my local tree to avoid panics on a ZFS & UFS2 i386 system. I have zfs & UFS on AMD64 and have not seen any issues. How do you trigger the issue in i386 ? Or does it just randomly happen ? ---Mike From owner-freebsd-stable@FreeBSD.ORG Fri Dec 17 22:37:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 314C91065670 for ; Fri, 17 Dec 2010 22:37:41 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id C91A38FC14 for ; Fri, 17 Dec 2010 22:37:40 +0000 (UTC) Received: by qwj9 with SMTP id 9so1155619qwj.13 for ; Fri, 17 Dec 2010 14:37:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=FtxJ9muxikO0Njt1GrzOeCXvHPwkPilrlq3/THmavKQ=; b=KaAqxtW7Z5izCI3Ds1fx7PvAWkoz1rVI9o7JERmwntkwTo4JjMtUQlp3NuXo7yg/52 UXTAJQZY3Xqd8l8YiNfKAWAe87J0rVCgbJIwE3BH2fSGFdoiQmjHfIfdMq3beS50czdX 9thXq/CzlSDQZzSqtFAjxYHVf1dNPjA3JlgLQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=TIY+HsnAhvGzb8L9z1d8Ds0CdQOChArCXCiG/W38jyYKK0avKfil5DD6HnrA5a6C3I /6csmIOJN76JCptPXLCfcPJJ25GOI6xOh2KEJNthcaBc7VDsPCClfUeAe38HcWC7X04F MnhC1kJa2ZgqcNFYKiI90gZ1PR/QcPEi2G0sY= Received: by 10.229.189.20 with SMTP id dc20mr1266127qcb.231.1292625460045; Fri, 17 Dec 2010 14:37:40 -0800 (PST) Received: from centel.dataix.local (adsl-99-109-126-202.dsl.klmzmi.sbcglobal.net [99.109.126.202]) by mx.google.com with ESMTPS id e29sm470927qck.39.2010.12.17.14.37.37 (version=SSLv3 cipher=RC4-MD5); Fri, 17 Dec 2010 14:37:38 -0800 (PST) Sender: "J. Hellenthal" Message-ID: <4D0BE630.6010900@DataIX.net> Date: Fri, 17 Dec 2010 17:37:36 -0500 From: jhell Organization: http://www.DataIX.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101210 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Mike Tancsa References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> <20101212084327.GS33073@deviant.kiev.zoral.com.ua> <4D0AB882.5090800@DataIX.net> <4D0AB987.5090000@DataIX.net> <4D0B6D26.7030808@sentex.net> In-Reply-To: <4D0B6D26.7030808@sentex.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Dec 2010 22:37:41 -0000 On 12/17/2010 09:01, Mike Tancsa wrote: > On 12/16/2010 8:14 PM, jhell wrote: >> On 12/16/2010 20:10, jhell wrote: >>> Regarding this patch(r216455) and r216162 I have had to back both of >>> them out of my local tree to avoid panics on a ZFS & UFS2 i386 system. > > > I have zfs & UFS on AMD64 and have not seen any issues. How do you > trigger the issue in i386 ? Or does it just randomly happen ? > > ---Mike I can simply run a scrub on the pool and within a little while within 12% - 18% it goes ker-plunk!. Not that it really has to do with the percentage rage as it does the timing. I do have prefetch enabled when this happens and currently running with it turned off and will booting so said kernel.bad in a little while to see if that makes a difference. -- jhell,v From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 04:48:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44B2B1065679 for ; Sat, 18 Dec 2010 04:48:18 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id F227B8FC0C for ; Sat, 18 Dec 2010 04:48:16 +0000 (UTC) Received: by iwn39 with SMTP id 39so1402970iwn.13 for ; Fri, 17 Dec 2010 20:48:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:date:from:to:cc :subject:in-reply-to:message-id:references:user-agent :x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version :content-type; bh=zUlbyMzr/yP7FDCKhl56ZAkG+vrCSC7LDC+oEqOQZNg=; b=iYu+deRxlrEr8seL1P0s7q22EE1qQfE4dw9GBbg56bZ4iZj+AXTpeNr2WckxN/TwQ0 CMwoGiryAjJ1uTtKF33VNpfjdrR+HwjyHkuWX0uSisS/FEDsmW8xLQe+OJwPfA43F+6E vCXemEOo75d0QzrhuqjBkgDclEGMjGfs48vuA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version :content-type; b=ng5U1IeBEjnImS4iHFLKlnZ+Bz4h6ZADMdS0r7STiEttX8hW7ak0VdXYmZe0ag1b48 IeVpVOmn4mNNzGHmz/lj3zlV1D6+lNiTQX39igqVde5Q5Gpj6jZbhk/fkdMEQMjQ3oe+ ZPQNIR5OweX1Dl0AygwlHTyzTzNiR0s7QqNPI= Received: by 10.42.172.67 with SMTP id m3mr1689024icz.177.1292647696512; Fri, 17 Dec 2010 20:48:16 -0800 (PST) Received: from centel.dataix.local (adsl-99-109-126-202.dsl.klmzmi.sbcglobal.net [99.109.126.202]) by mx.google.com with ESMTPS id 14sm1554311ico.8.2010.12.17.20.48.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 17 Dec 2010 20:48:14 -0800 (PST) Sender: "J. Hellenthal" Date: Fri, 17 Dec 2010 23:47:50 -0500 From: jhell To: Mike Tancsa In-Reply-To: <4D0B6D26.7030808@sentex.net> Message-ID: References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> <20101212084327.GS33073@deviant.kiev.zoral.com.ua> <4D0AB882.5090800@DataIX.net> <4D0AB987.5090000@DataIX.net> <4D0B6D26.7030808@sentex.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kostik Belousov , Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 04:48:18 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 17 Dec 2010 09:01, Mike Tancsa wrote: In Message-Id: <4D0B6D26.7030808@sentex.net> > On 12/16/2010 8:14 PM, jhell wrote: >> On 12/16/2010 20:10, jhell wrote: >>> Regarding this patch(r216455) and r216162 I have had to back both of >>> them out of my local tree to avoid panics on a ZFS & UFS2 i386 system. > > > I have zfs & UFS on AMD64 and have not seen any issues. How do you > trigger the issue in i386 ? Or does it just randomly happen ? > Looks as if I have it narrowed down to that its only effecting prefetch on i386. Seeing as prefetch is not really suggested below 4G of RAM and as well on i386 it is not really much concern to me ATM. Whatever did change "Not in the ZFS code" & "Not in r216162 or r216455" has effected prefetch on i386 directly though or at least as far as I can see for the moment. As of right now Ill look into a few other commits starting with r216305 which was a MFC of r216194. I would like to see this resolved as I currently only have i386's to run from unless that is someone would like to donate some hardware ;) Regards, - -- jhell,v -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJNDD0AAAoJEJBXh4mJ2FR+SqIH/jkWf8Z69lKC3wlSYjwwNqTL gX/rEuAU/2xOQj2bKR4/BEfeNXtSy9n47IbbCZApGuBABf2lkytSUk2n1XgQ1sB1 GRJl8gCm5BtmhZh0oTc9CIwUcJy+h/w3dU34WXp5riegk0MwpPJlbx9JX4huC+6s j+wG0oJpxJZq1v/0uWM7ks1D6yYzgBXFyp9j+8ZGoeeXIeraqglj57eB0+Ck1Jq2 JjQ9uLTqnkLS2Zzf/Vgbju4O4bV6geAd+j6Td6Fwt+c3yHCWOHSFQcakyrdJzntl feWJPAl9ZZSGBhvdAH4pumLt01BVyESIe/rsbtD68pAIGWqxrL3NsI6bIDg3cvI= =apgr -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 05:41:57 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46152106564A for ; Sat, 18 Dec 2010 05:41:57 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id E75E18FC0C for ; Sat, 18 Dec 2010 05:41:56 +0000 (UTC) Received: (qmail 31960 invoked by uid 399); 18 Dec 2010 05:41:55 -0000 Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 18 Dec 2010 05:41:55 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4D0C49A2.4000203@FreeBSD.org> Date: Fri, 17 Dec 2010 21:41:54 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101210 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 05:41:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Howdy, Traditionally for contributed software generally, and BIND in particular we have tried to keep the major version of the contributed software consistent throughout a given RELENG_$N branch of FreeBSD. Hopefully the reasoning for this is obvious, we want to avoid POLA violations. However this policy led to an unfortunate situation with FreeBSD 6 and BIND 9.3. We ended up "supporting" it long after the vendor's EOL date, both in ports and in the base. I have written previously about this issue being an inevitable result of the fact that our release engineering schedule and ISC's have both changed, and diverged. In RELENG_6 the problem was exacerbated by the fact that BIND 9.3 was such an old version that there was no clean upgrade path, users needed to make changes to configuration files, regression test, etc. Therefore the decision was made to live with the issue in RELENG_6. We currently face a similar situation in RELENG_7, which has BIND 9.4-ESV; scheduled to EOL in May 2011. https://www.isc.org/software/bind/versions In contrast, BIND 9.6-ESV will be supported until March 2013. Additionally BIND 9.6 is a superset of 9.4, and users should not need to make any changes to their configuration files. In fact, at the moment src/etc/namedb is identical in head/ stable/8, and stable/7. There may be some differences in operation; for example in some situations BIND 9.6 can use more memory than an identically configured 9.4 server. But in the overwhelming number of situations users would simply be able to upgrade in place without concern. In order to avoid repeating the scenario where we have a version of BIND in the base that is not supported by the vendor I am proposing that we upgrade to BIND 9.6-ESV in FreeBSD RELENG_7. There is an additional element to this decision that is relevant for users who wish to set up their resolving name servers for DNSSEC validation. BIND 9.6 is the oldest version that has (or will have) support for the algorithms and other features necessary for modern DNSSEC. While I do not think that the decision of changing BIND versions should turn exclusively on this element, I do think it is a factor that should be considered. My purpose in writing this message is to solicit feedback from users who would be adversely affected if this change was made. Please do not devolve down the rathole of whether BIND should be removed from the base altogether. This is incredibly unlikely to happen for RELENG_7 or RELENG_8. The question of whether or not it should happen in HEAD prior to the eventual 9.0-RELEASE is a topic for another thread. I am particularly interested in feedback from users with significant DNS usage that are still using 9.4, especially if you're using the version in the base. I would appreciate it if you could install 9.6 from the ports and at minimum run /usr/local/sbin/named-checkconf to see if any errors are generated. Of course it would be that much more helpful if you could also evaluate BIND 9.6 in operation in your environment. Your feedback on the issue of upgrading BIND in RELENG_7 is welcome. Sooner is better. :) Regards, Doug - -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBCAAGBQJNDEmiAAoJEFzGhvEaGryEZMEH/RrDmyaJj/1kXzNIua7wSmIN pP/Bp6A9yh2IPao7fAb5Zo8EfEsN5dfhJNyCl/xXRTODZqv5iBo1AaJpQ4ezKkpm y2tbWczOZyWU+yFyG2trdQorDUMc57M2Q6NULENglvDlTsf5sk3pLid+rOXHIs9c cIB3WdUe1A38qHzPjLOsCAQIY0u2/doNoCE1ltK2yYWew/l8inVnNxUqaMBgFNf1 8cElZ9D+biqzNLt1Gd8k6xMePspwebT+T21aB03m2BylslSEa6m/pdw1N4H4D25W 0EsJnf9ryYfodl2Q5/gq9cGDIXAvo4llzPeMMoJuqvlwmh9TChjy9dhR8ZJnLfA= =Ug9P -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 09:15:45 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04EFB1065694; Sat, 18 Dec 2010 09:15:45 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7ABAF8FC19; Sat, 18 Dec 2010 09:15:44 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id oBI9FSZA090564; Sat, 18 Dec 2010 10:15:43 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id oBI9FSWA090563; Sat, 18 Dec 2010 10:15:28 +0100 (CET) (envelope-from olli) Date: Sat, 18 Dec 2010 10:15:28 +0100 (CET) Message-Id: <201012180915.oBI9FSWA090563@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, dougb@FreeBSD.ORG In-Reply-To: <4D0C49A2.4000203@FreeBSD.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Sat, 18 Dec 2010 10:15:43 +0100 (CET) Cc: Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, dougb@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Dec 2010 09:15:45 -0000 Doug Barton wrote: > In order to avoid repeating the scenario where we have a version of BIND > in the base that is not supported by the vendor I am proposing that we > upgrade to BIND 9.6-ESV in FreeBSD RELENG_7. I agree. > I am particularly interested in feedback from users with significant DNS > usage that are still using 9.4, especially if you're using the version > in the base. I would appreciate it if you could install 9.6 from the > ports and at minimum run /usr/local/sbin/named-checkconf to see if any > errors are generated. Of course it would be that much more helpful if > you could also evaluate BIND 9.6 in operation in your environment. I already installed the ports' version of BIND 9.6 a few months ago on two stable/7 machines that are primary and secondary nameservers for a bunch of domains. It was a simple drop-in replacement, no problems whatsoever. > Your feedback on the issue of upgrading BIND in RELENG_7 is welcome. > Sooner is better. :) I vote for the upgrade. It's easy and seamless for users, as far as I can tell, and it avoids problems in the long run. I agree with you that the situation that we had with FreeBSD 6 should be avoided. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd C++: "an octopus made by nailing extra legs onto a dog" -- Steve Taylor, 1998 From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 09:16:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3067E1065672 for ; Sat, 18 Dec 2010 09:16:32 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221]) by mx1.freebsd.org (Postfix) with ESMTP id 86B108FC1D for ; Sat, 18 Dec 2010 09:16:31 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id oBI9GSJo089223; Sat, 18 Dec 2010 15:16:28 +0600 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <4D0C7BE7.5020605@rdtc.ru> Date: Sat, 18 Dec 2010 15:16:23 +0600 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.1.10) Gecko/20100712 Thunderbird/3.0.5 MIME-Version: 1.0 To: Doug Barton References: <4D0C49A2.4000203@FreeBSD.org> In-Reply-To: <4D0C49A2.4000203@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 09:16:32 -0000 On 18.12.2010 11:41, Doug Barton wrote: > I am particularly interested in feedback from users with significant DNS > usage that are still using 9.4, especially if you're using the version > in the base. I would appreciate it if you could install 9.6 from the > ports and at minimum run /usr/local/sbin/named-checkconf to see if any > errors are generated. Of course it would be that much more helpful if > you could also evaluate BIND 9.6 in operation in your environment. > > Your feedback on the issue of upgrading BIND in RELENG_7 is welcome. > Sooner is better. :) I run serveral DNS servers based on FreeBSD+bind. One of them is FreeBSD 7.3-STABLE and bind-9.4. It's public primary server for two zones (one forward and one reverse) and public secondary for several others; plus it's recursive caching DNS server for users, low-loaded. I've just updated ports tree and installed dns/bind96. /usr/local/sbin/named-checkconf shows no messages at all. I've restarted bind using ports version. All seems OK. I'll write back if problems arise. About upgrading bind version in RELENG_7, I'm for it. Btw, I run one bind96 server/4.11-STABLE for long time (and even one bind95/4.11-STABLE) and six 6.11-STABLE servers with stock bind93 ;-) Never had a problem with them. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 09:27:39 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9ABF106564A; Sat, 18 Dec 2010 09:27:39 +0000 (UTC) (envelope-from alteriks@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 55B4D8FC08; Sat, 18 Dec 2010 09:27:39 +0000 (UTC) Received: by vws9 with SMTP id 9so576400vws.13 for ; Sat, 18 Dec 2010 01:27:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=/CWgwz8yiPm3f81xsiHwpsz2vito+EpSpbVCuwYLZ+E=; b=kklXErZh8Ecet6eWfoflCvzcQ9BvzWmIRHrkhPWdR+1Musa/xnUnOCtenSl80NX9MR KKLKl8hM1jc3sf6kHYF2oBK0ozISfYDxe1K9QF031l1zseHEmrlfAHY8RINjxFAIaNSB O4w3coH/pOdOjoPxe9dVx48XPF2IkR3Qx8RRE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=R0LopqnMkq+Wx+1oPaj0HJL1Cte5V0n1Jz1dOgC/OSE8tL1qba5gqN6YvoBiwHnO8I shirzLclUNFxAnrkE5uJPTiWt9boZp0Za6K8dnQWAZsJhyf8tT208Cdvp+t+BAnnJMwl +POvNYf2/AcA4BHobeQCTlpQtGG5WgsaoimBE= Received: by 10.220.188.74 with SMTP id cz10mr523502vcb.118.1292662832781; Sat, 18 Dec 2010 01:00:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.87.4 with HTTP; Sat, 18 Dec 2010 01:00:11 -0800 (PST) In-Reply-To: <4D0A09AF.3040005@FreeBSD.org> References: <4D0A09AF.3040005@FreeBSD.org> From: Krzysztof Dajka Date: Sat, 18 Dec 2010 10:00:11 +0100 Message-ID: To: Martin Matuska Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 09:27:40 -0000 Hi, I applied patch against evening 2010-12-16 STABLE. I did what Martin asked: On Thu, Dec 16, 2010 at 1:44 PM, Martin Matuska wrote: > =C2=A0 =C2=A0# cd /usr/src > =C2=A0 =C2=A0# fetch > http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.pa= tch.xz > =C2=A0 =C2=A0# xz -d stable-8-zfsv28-20101215.patch.xz > =C2=A0 =C2=A0# patch -E -p0 < stable-8-zfsv28-20101215.patch > =C2=A0 =C2=A0# rm sys/cddl/compat/opensolaris/sys/sysmacros.h > Patch applied cleanly. #make buildworld #make buildkernel #make installkernel Reboot into single user mode. #mergemaster -p #make installworld #mergemaster Reboot. Rebooting with old world and new kernel went fine. But after reboot with new world I got: ZFS: zfs_alloc()/zfs_free() mismatch Just before loading kernel modules, after that my system hangs. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 09:42:02 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B01B1065675; Sat, 18 Dec 2010 09:42:02 +0000 (UTC) (envelope-from Volker.Lendecke@SerNet.DE) Received: from mail.SerNet.de (mail1.SerNet.de [193.175.80.2]) by mx1.freebsd.org (Postfix) with ESMTP id DD51E8FC12; Sat, 18 Dec 2010 09:42:01 +0000 (UTC) Received: from intern.SerNet.DE by mail.SerNet.DE with esmtp (Exim 4.69 #1) id 1PTspQ-00023V-Sf; Sat, 18 Dec 2010 10:11:48 +0100 Received: by intern.SerNet.DE id 1PTspQ-000SD4-LX; Sat, 18 Dec 2010 10:11:48 +0100 Received: by intern.SerNet.DE id 1PTspQ-000SCm-3c; Sat, 18 Dec 2010 10:11:48 +0100 Date: Sat, 18 Dec 2010 10:10:26 +0100 Date: Sat, 18 Dec 2010 10:10:26 +0100 From: Volker Lendecke To: Willy Offermans References: <4d0a2fd5.50f.2ce7dc40.5721f9f0@tms3.com> <20101217102612.GC7694@vpn.offrom.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101217102612.GC7694@vpn.offrom.nl> User-Agent: Mutt/1.5.20 (2009-06-14) Message-Id: Organization: SerNet GmbH, Goettingen, Germany Cc: Samba List , tms3@tms3.com, freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: [Samba] Samba upgrade HowTo requested X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Volker.Lendecke@SerNet.DE List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Dec 2010 09:42:02 -0000 On Fri, Dec 17, 2010 at 11:26:12AM +0100, Willy Offermans wrote: > I do not think that this issue is related to dependencies. Of course I need > to be sure that the dependencies are correctly installed as well, but this > job is accomplished by ``portupgrade -R -N'' quite well. > > No, the real problem lays in the settings and databases created in a > previous version of samba, which will be lost, altered or corrupted upon an > upgrade. To phrase the questions again? > > Is there a procedure on how to upgrade samba to a newer version? > > How can the ignorant user be informed when using portupgrade? > > I'm sorry, I just recall the UPDATING file in /usr/ports/. The > following is a cut from this file: > > > > 20101026: > AFFECTS: users of net/samba35 > AUTHOR: Timur Bakeyev > > This is the latest stable release of the Samba3 distribution. It has > been extended with the experimental support of the NFS4-like ACLs on > ZFS partitions, thanks to the sysutils/libsunacl library by Edward > Tomasz Napierala(trasz). This support haven't been tested thoroughly, > so try it on your own risk. This looks interesting. I just did a portsnap fetch update in my FreeBSD 8.1 box, but I don't find that snippet. Where can I find those patches? Volker From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 09:47:41 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65546106564A for ; Sat, 18 Dec 2010 09:47:41 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id C1E968FC12 for ; Sat, 18 Dec 2010 09:47:40 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id oBI9lMtt092384; Sat, 18 Dec 2010 10:47:37 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id oBI9lMoU092383; Sat, 18 Dec 2010 10:47:22 +0100 (CET) (envelope-from olli) Date: Sat, 18 Dec 2010 10:47:22 +0100 (CET) Message-Id: <201012180947.oBI9lMoU092383@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, mamalos@eng.auth.gr In-Reply-To: <4D0A6BC1.9040201@eng.auth.gr> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Sat, 18 Dec 2010 10:47:37 +0100 (CET) Cc: Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, mamalos@eng.auth.gr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Dec 2010 09:47:41 -0000 George Mamalakis wrote: > Oliver, thanx for your comments. I know it is difficult to choose which > process to kill and how to be "fair" during such a killing procedure. > Nevertheless, I would assume that all non-root processes would have > higher priority to get killed, and that root's processes would get > killed last. The owner of the process is not taken into consideration, because the "run-away" process causing the memory shortage may as well be a root-owned process. In such a situation, if root processes were exempt from killing, the system would deadlock and require a hard reboot. Killing the root-owned process is the lesser of two evils. As I already explained, there is a process flag that root- owned processes can set for themselves, preventing the kernel from killing them in low-memory situations. See the description of the MADV_PROTECT flag in the madvise(2) manual page. For example, cron(8) and sshd(8) make use of this, so they will not be killed. This is a better way than simply excluding all root processes. > I understand your comments completely, but I was just so > surprised when I realized how easy it was for me to kill root processes > on my system. Only because you didn't configure resource limits. ;-) When you're the only user on a machine, such as a desktop box, this is usually not a big deal. But in all other cases it's strongly recommended to set resource limits, in particular for shell users and for server processes. Without any resource limits, a normal user can starve the system and take it down. This is an old and well-known problem for all UNIX systems (and most non-UNIX systems, too, I guess). You certainly didn't discover any new problem. If you're concerned, configure resource limits. Period. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "File names are infinite in length, where infinity is set to 255 characters." -- Peter Collinson, "The Unix File System" From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 09:50:56 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9AAD10656C5 for ; Sat, 18 Dec 2010 09:50:56 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id 08EA68FC18 for ; Sat, 18 Dec 2010 09:50:55 +0000 (UTC) Received: (qmail 45653 invoked from network); 18 Dec 2010 09:24:14 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 18 Dec 2010 09:24:14 -0000 Date: Sat, 18 Dec 2010 10:24:14 +0100 (CET) Message-Id: <20101218.102414.74714683.sthaug@nethelp.no> To: freebsd-stable@FreeBSD.ORG, dougb@FreeBSD.ORG, olli@lurza.secnetix.de From: sthaug@nethelp.no In-Reply-To: <201012180915.oBI9FSWA090563@lurza.secnetix.de> References: <4D0C49A2.4000203@FreeBSD.org> <201012180915.oBI9FSWA090563@lurza.secnetix.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 09:50:56 -0000 > > In order to avoid repeating the scenario where we have a version of BIND > > in the base that is not supported by the vendor I am proposing that we > > upgrade to BIND 9.6-ESV in FreeBSD RELENG_7. ... > > I vote for the upgrade. It's easy and seamless for users, > as far as I can tell, and it avoids problems in the long > run. I agree with you that the situation that we had with > FreeBSD 6 should be avoided. +1 here. I run several 7-STABLE boxes with BIND 9.6, no problems. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 11:15:42 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 185CB106566C; Sat, 18 Dec 2010 11:15:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 869FE8FC17; Sat, 18 Dec 2010 11:15:41 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id oBIBFc8u077150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Dec 2010 13:15:38 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id oBIBFcTE020255; Sat, 18 Dec 2010 13:15:38 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id oBIBFcV0020254; Sat, 18 Dec 2010 13:15:38 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 18 Dec 2010 13:15:38 +0200 From: Kostik Belousov To: Doug Barton Message-ID: <20101218111538.GZ33073@deviant.kiev.zoral.com.ua> References: <4D0C49A2.4000203@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s1V7GiNVmT/EiLBY" Content-Disposition: inline In-Reply-To: <4D0C49A2.4000203@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-stable@freebsd.org Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 11:15:42 -0000 --s1V7GiNVmT/EiLBY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 17, 2010 at 09:41:54PM -0800, Doug Barton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 >=20 > Howdy, >=20 > Traditionally for contributed software generally, and BIND in particular > we have tried to keep the major version of the contributed software > consistent throughout a given RELENG_$N branch of FreeBSD. Hopefully the > reasoning for this is obvious, we want to avoid POLA violations. Actually not. My own POV is that we should follow the vendor release cycle, and not the FreeBSD release cycle, for the contributed software. I do not advocate immediate upgrade of the third-party software that reached its EOL, but I think that we should do this without pushback if maintainer consider the neccessity of upgrade. --s1V7GiNVmT/EiLBY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk0Ml9kACgkQC3+MBN1Mb4iGeQCg1w2HBxiS2SgK0Sfsd/8w1fYs 96AAniSAijb2k9TbtbjqXKiPF7QUhwhs =7gcR -----END PGP SIGNATURE----- --s1V7GiNVmT/EiLBY-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 12:19:06 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBEC0106564A for ; Sat, 18 Dec 2010 12:19:06 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from outgoing.holservices.gr (outgoing.holservices.gr [62.38.2.44]) by mx1.freebsd.org (Postfix) with SMTP id E27418FC08 for ; Sat, 18 Dec 2010 12:19:05 +0000 (UTC) Received: (qmail 28939 invoked from network); 18 Dec 2010 11:33:50 -0000 Received: from unknown (HELO deliver.mail.dc.hol.net) (192.168.20.70) by arete.mail.dc.hol.net with SMTP; 18 Dec 2010 11:33:50 -0000 Received: from auth-smtp.hol.gr (takeit01.mail.dc.hol.net [192.168.20.71]) by deliver.hol.gr (8.12.11/8.11.6) with ESMTP id oBIBprPU014138 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256 bits) verified OK); Sat, 18 Dec 2010 13:51:54 +0200 Received: from [192.168.2.2] (ppp046176001046.dsl.hol.gr [46.176.1.46]) by auth-smtp.hol.gr (8.13.1/8.13.1) with ESMTP id oBIBprbm021919; Sat, 18 Dec 2010 13:51:53 +0200 Message-ID: <4D0CA06A.2080603@eng.auth.gr> Date: Sat, 18 Dec 2010 13:52:10 +0200 From: George Mamalakis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, mamalos@eng.auth.gr References: <201012180947.oBI9lMoU092383@lurza.secnetix.de> In-Reply-To: <201012180947.oBI9lMoU092383@lurza.secnetix.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on takeit01.mail.dc.hol.net X-Virus-Status: Clean Cc: Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 12:19:06 -0000 Oliver, I am sending you this email outside the list, because I think that enough emails have been sent regarding my message. Now to your statements: On 18/12/2010 11:47 πμ, Oliver Fromme wrote: > George Mamalakis wrote: > > Oliver, thanx for your comments. I know it is difficult to choose which > > process to kill and how to be "fair" during such a killing procedure. > > Nevertheless, I would assume that all non-root processes would have > > higher priority to get killed, and that root's processes would get > > killed last. > > The owner of the process is not taken into consideration, > because the "run-away" process causing the memory shortage > may as well be a root-owned process. In such a situation, > if root processes were exempt from killing, the system > would deadlock and require a hard reboot. Killing the > root-owned process is the lesser of two evils. > As I explained in one of my previous emails, I expected that root processes would have *lower priority* than non-root processes; I never implied that root processes shouldn't get killed, it would be irrational to say so. > As I already explained, there is a process flag that root- > owned processes can set for themselves, preventing the > kernel from killing them in low-memory situations. See > the description of the MADV_PROTECT flag in the madvise(2) > manual page. For example, cron(8) and sshd(8) make use of > this, so they will not be killed. This is a better way > than simply excluding all root processes. > > > I understand your comments completely, but I was just so > > surprised when I realized how easy it was for me to kill root processes > > on my system. > > Only because you didn't configure resource limits. ;-) > > When you're the only user on a machine, such as a desktop > box, this is usually not a big deal. But in all other > cases it's strongly recommended to set resource limits, > in particular for shell users and for server processes. > > Without any resource limits, a normal user can starve the > system and take it down. This is an old and well-known > problem for all UNIX systems (and most non-UNIX systems, > too, I guess). You certainly didn't discover any new > problem. > > If you're concerned, configure resource limits. Period. > As I stated in my first message (if I recall correctly), all this happened because I didn't configure my rlimits (it's my laptop). Of course I am aware of resource limits, and I configure them on most of the servers I administer for the last 12 years (I've seen my vmstat showing 500+ processes in blocked-by-io state, and the system wouldn't hang..:)). I never implied to have discovered anything new, and especially something regarding resource limits. All my enthusiasm was caused firstly due to fbsd's memory allocation algorithm (I never knew the system would assume that it could allocate 500+GB of memory, and the replies on this issue where very enlightening for me), and secondly due to fbsd's algorithm on process killing when memory has been starved. Certainly, I was not surprised by the fact that my system was out of memory...exceeding my system's memory limits was my experiment in the first place! Anyway, thanx again for your answer and all your pointers (MADV_PROTECT, etc), and I think there is no need to get angry about my emails. As I initially stated, my questions where rhetorical, and no answers where needed. I trusted that there should be a good reason behind this behavior...Some of you answered on the list and I just replied with my opinion. Nothing more, nothing less. Have a nice day and kind regards, mamalos -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 13:56:52 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81FD3106564A for ; Sat, 18 Dec 2010 13:56:52 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2017D8FC0A for ; Sat, 18 Dec 2010 13:56:51 +0000 (UTC) Received: by wyf19 with SMTP id 19so1495057wyf.13 for ; Sat, 18 Dec 2010 05:56:51 -0800 (PST) Received: by 10.227.69.202 with SMTP id a10mr1311503wbj.141.1292679180777; Sat, 18 Dec 2010 05:33:00 -0800 (PST) Received: from dfleuriot.local (angel.c-mal.com [82.241.189.111]) by mx.google.com with ESMTPS id 11sm1101717wbi.6.2010.12.18.05.32.57 (version=SSLv3 cipher=RC4-MD5); Sat, 18 Dec 2010 05:33:00 -0800 (PST) Message-ID: <4D0CB7FC.7020103@my.gd> Date: Sat, 18 Dec 2010 14:32:44 +0100 From: Damien User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4D0C49A2.4000203@FreeBSD.org> In-Reply-To: <4D0C49A2.4000203@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 13:56:52 -0000 Hello Doug, List, I confirm the upgrade from 94 to 96 is very minor. I'm running several fbsd8.0 and 8.1 servers but I still have a 7.2-STABLE box here. I just upgraded from the ports collections 9.4.4.ESV.2 to 9.6.3.ESV3 named-checkconf doesn't report any error, neither does checkzone. I started the new named daemon successfully and can still resolve just fine, both with recursion from localhost and without from external hosts. Please note that I was using 94 from ports and not the base system, but either way I haven't made a single change to my configuration files. I am also in favor of upgrading the base system's version of BIND to 9.6. -- Damien On 12/18/10 6:41 AM, Doug Barton wrote: > Howdy, > > Traditionally for contributed software generally, and BIND in particular > we have tried to keep the major version of the contributed software > consistent throughout a given RELENG_$N branch of FreeBSD. Hopefully the > reasoning for this is obvious, we want to avoid POLA violations. > > However this policy led to an unfortunate situation with FreeBSD 6 and > BIND 9.3. We ended up "supporting" it long after the vendor's EOL date, > both in ports and in the base. I have written previously about this > issue being an inevitable result of the fact that our release > engineering schedule and ISC's have both changed, and diverged. In > RELENG_6 the problem was exacerbated by the fact that BIND 9.3 was such > an old version that there was no clean upgrade path, users needed to > make changes to configuration files, regression test, etc. Therefore the > decision was made to live with the issue in RELENG_6. > > We currently face a similar situation in RELENG_7, which has BIND > 9.4-ESV; scheduled to EOL in May 2011. > https://www.isc.org/software/bind/versions In contrast, BIND 9.6-ESV > will be supported until March 2013. Additionally BIND 9.6 is a superset > of 9.4, and users should not need to make any changes to their > configuration files. In fact, at the moment src/etc/namedb is identical > in head/ stable/8, and stable/7. There may be some differences in > operation; for example in some situations BIND 9.6 can use more memory > than an identically configured 9.4 server. But in the overwhelming > number of situations users would simply be able to upgrade in place > without concern. > > In order to avoid repeating the scenario where we have a version of BIND > in the base that is not supported by the vendor I am proposing that we > upgrade to BIND 9.6-ESV in FreeBSD RELENG_7. > > There is an additional element to this decision that is relevant for > users who wish to set up their resolving name servers for DNSSEC > validation. BIND 9.6 is the oldest version that has (or will have) > support for the algorithms and other features necessary for modern > DNSSEC. While I do not think that the decision of changing BIND versions > should turn exclusively on this element, I do think it is a factor that > should be considered. > > My purpose in writing this message is to solicit feedback from users who > would be adversely affected if this change was made. Please do not > devolve down the rathole of whether BIND should be removed from the base > altogether. This is incredibly unlikely to happen for RELENG_7 or > RELENG_8. The question of whether or not it should happen in HEAD prior > to the eventual 9.0-RELEASE is a topic for another thread. > > I am particularly interested in feedback from users with significant DNS > usage that are still using 9.4, especially if you're using the version > in the base. I would appreciate it if you could install 9.6 from the > ports and at minimum run /usr/local/sbin/named-checkconf to see if any > errors are generated. Of course it would be that much more helpful if > you could also evaluate BIND 9.6 in operation in your environment. > > Your feedback on the issue of upgrading BIND in RELENG_7 is welcome. > Sooner is better. :) > > > Regards, > > Doug > _______________________________________________ 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 Dec 18 14:44:35 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60FDD106566B; Sat, 18 Dec 2010 14:44:35 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 1E73F8FC15; Sat, 18 Dec 2010 14:44:35 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:5022:4efd:b73a:4846] ([IPv6:2607:f3e0:0:4:5022:4efd:b73a:4846]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oBIEiWo9001744 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 18 Dec 2010 09:44:33 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D0CC8CD.7070605@sentex.net> Date: Sat, 18 Dec 2010 09:44:29 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Doug Barton References: <4D0C49A2.4000203@FreeBSD.org> In-Reply-To: <4D0C49A2.4000203@FreeBSD.org> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: freebsd-stable@freebsd.org Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 14:44:35 -0000 On 12/18/2010 12:41 AM, Doug Barton wrote: > > I am particularly interested in feedback from users with significant DNS > usage that are still using 9.4, especially if you're using the version > in the base. I would appreciate it if you could install 9.6 from the > ports and at minimum run /usr/local/sbin/named-checkconf to see if any > errors are generated. Of course it would be that much more helpful if > you could also evaluate BIND 9.6 in operation in your environment. Its significant to us, but not compared to large orgs usage wise:) IFF we had to make any config changes on this end we would view it as work that would eventually need to be done regardless. That being said, the new named-checkconf seems happy on our main servers (~2,000 zones each) so we would welcome this update to RELENG_7. ---Mike From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 17:16:29 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41A7F106564A; Sat, 18 Dec 2010 17:16:29 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) by mx1.freebsd.org (Postfix) with ESMTP id ED3818FC08; Sat, 18 Dec 2010 17:16:28 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.4/8.14.4) with ESMTP id oBIHGSW8099732; Sat, 18 Dec 2010 12:16:28 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.4/8.14.4/Submit) id oBIHGS3m099731; Sat, 18 Dec 2010 12:16:28 -0500 (EST) (envelope-from wollman) Date: Sat, 18 Dec 2010 12:16:28 -0500 (EST) From: Garrett Wollman Message-Id: <201012181716.oBIHGS3m099731@hergotha.csail.mit.edu> To: dougb@freebsd.org In-Reply-To: <4D0C49A2.4000203@FreeBSD.org> Organization: none X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (hergotha.csail.mit.edu [127.0.0.1]); Sat, 18 Dec 2010 12:16:28 -0500 (EST) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on hergotha.csail.mit.edu Cc: stable@freebsd.org Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 17:16:29 -0000 In article <4D0C49A2.4000203@FreeBSD.org>, dougb@freebsd.org writes: >In order to avoid repeating the scenario where we have a version of BIND >in the base that is not supported by the vendor I am proposing that we >upgrade to BIND 9.6-ESV in FreeBSD RELENG_7. +1 All users are going to want working DNSsec soon, if they don't already, and that requires 9.6. (In fact, we should start shipping with DNSsec enabled by default and the root key pre-configured, if we aren't already doing so.) -GAWollman -- Garrett A. Wollman | What intellectual phenomenon can be older, or more oft wollman@bimajority.org| repeated, than the story of a large research program Opinions not shared by| that impaled itself upon a false central assumption my employers. | accepted by all practitioners? - S.J. Gould, 1993 From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 18:19:52 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 493DA106564A for ; Sat, 18 Dec 2010 18:19:52 +0000 (UTC) (envelope-from mloftis@wgops.com) Received: from mail-bw0-f48.google.com (mail-bw0-f48.google.com [209.85.214.48]) by mx1.freebsd.org (Postfix) with ESMTP id D5FA28FC18 for ; Sat, 18 Dec 2010 18:19:51 +0000 (UTC) Received: by bwz8 with SMTP id 8so1628247bwz.7 for ; Sat, 18 Dec 2010 10:19:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.126.87 with SMTP id b23mr1868495bks.203.1292695009279; Sat, 18 Dec 2010 09:56:49 -0800 (PST) Received: by 10.204.121.82 with HTTP; Sat, 18 Dec 2010 09:56:49 -0800 (PST) In-Reply-To: <4D08DE9C.1060108@eng.auth.gr> References: <4D08A0A1.40205@eng.auth.gr> <4D08C61C.4090006@eng.auth.gr> <20101215135143.GY33073@deviant.kiev.zoral.com.ua> <4D08DE9C.1060108@eng.auth.gr> Date: Sat, 18 Dec 2010 10:56:49 -0700 Message-ID: From: Michael Loftis To: George Mamalakis Content-Type: text/plain; charset=ISO-8859-1 Cc: Kostik Belousov , stable Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 18:19:52 -0000 On Wed, Dec 15, 2010 at 8:28 AM, George Mamalakis wrote: > where one can see that pid 1544 was killed before 2864, which is the process > that caused all this mess. Yes, I know that I should use limits so as not to > allow such things to happen, but on the other hand, if a malicious user > causes such a situation he/she may gain access to information through > core-dumps on root processes, AND cause DoS attacks. If it were for me, I > would sort all processes based on their memory consumption, and start by > killing those that have the highest value (top-bottom) that are NOT owned by > root (just a thought, without thinking about it too much), so as to prevent > such situations from happening. > Which on most large, multi-user systems, will actually end up being your database processes most of the time. Once in a while it might get lucky and clobber the right process but usually in my experience that algorithm does not work. Neither does "most CPU using" and in fact, most CPU using usually ends up worse because your long lived daemons (Apache, MySQL, mail server, etc) become the primary targets. As was said by someone else, the system killing mechanism should be a last resort, per user resource limits should be your first lines of defense, and process limits, things of that nature. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 18:37:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4077D1065672 for ; Sat, 18 Dec 2010 18:37:24 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id 049DA8FC1B for ; Sat, 18 Dec 2010 18:37:23 +0000 (UTC) Received: (qmail 18398 invoked by uid 89); 18 Dec 2010 18:37:22 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 18 Dec 2010 18:37:22 -0000 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Dan Allen In-Reply-To: <20101215004712.GA56065@icarus.home.lan> Date: Sat, 18 Dec 2010 11:37:21 -0700 Content-Transfer-Encoding: 7bit Message-Id: References: <20101215004712.GA56065@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1082) Cc: dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 18:37:24 -0000 On 14 Dec 2010, at 5:47 PM, Jeremy Chadwick wrote: > Anyway, many people are using the below with success. Sorry to say that netwait did NOT in the end fix the problem. I however discovered that if I put synchronous_dhclient="YES" into my /etc/rc.conf file, that over many days & reboots now has been delivering reliable networking such that ntpd always works. Thanks again to everyone for their help. Dan From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 19:59:02 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31E381065670; Sat, 18 Dec 2010 19:59:02 +0000 (UTC) (envelope-from alteriks@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id BAB3B8FC19; Sat, 18 Dec 2010 19:59:01 +0000 (UTC) Received: by qyk36 with SMTP id 36so1655578qyk.13 for ; Sat, 18 Dec 2010 11:59:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=bygcB+Uaihq6uZ+MFHMQjUKdtkLHnFyMXX+CVkvoxr0=; b=qjgec5kORj6G8LxxxeYEATrMjViu5vKDXC8HZ1cx/ycl+x5mC0Gia6wFUwOZ8echOH y2AZh2aYJ5wcunlsWOWTp5hLB1F6ALnbcb2nvdlsuePLSsTC8Yac6nUkwYYIRGjR4NrP VdsiUTEkNxPv+61Nt3zEuvi1oHOrwpfgaqOe0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=VjnEtDG93gHYlOyR8dmUS4x4QZ9xmKOpC+/kCgQBBDijKK/IJX5tDlKd1fkbz4D6vg 9VBt92sTqQoSPJtiMHByKJY8x8Ex8RCiqtPRrFkpJwZePCavKAUbaogRSS+h3uYtcqWS Dg9htxzCcfZMk0h/ZDAnFmJw2ijVEDohEixro= Received: by 10.224.73.137 with SMTP id q9mr2363130qaj.53.1292702340999; Sat, 18 Dec 2010 11:59:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.87.4 with HTTP; Sat, 18 Dec 2010 11:58:40 -0800 (PST) In-Reply-To: <4D0D0BC6.8090607@FreeBSD.org> References: <4D0A09AF.3040005@FreeBSD.org> <4D0D0BC6.8090607@FreeBSD.org> From: Krzysztof Dajka Date: Sat, 18 Dec 2010 19:58:40 +0000 Message-ID: To: Martin Matuska Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 19:59:02 -0000 On Sat, Dec 18, 2010 at 7:30 PM, Martin Matuska wrote: > The information about pools is stored in /boot/zfs/zpool.cache > If this file doesn't contain correct information, your system pools will > not be discovered. > > In v28, importing a pool with the "altroot" option does not touch the > cache file (it has to be specified manually with a option to zpool import= ). > > Regarding rollback - rolling back a live root file system is not > recommended. > > D=C5=88a 18.12.2010 19:43, Krzysztof Dajka =C2=A0wrote / nap=C3=ADsal(a): >> t my system working >> again. I did: >> zpool import -o altroot=3D/tank tank >> chroot /tank >> reboot >> >> Can anyone explain why chroot to /tank is needed? > I used 8.2BETA1 memstick image to import and rollback. Thanks for explanation, few moments ago I would argue that zpool(1) didn't mention cachefile :) From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 22:02:47 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E63CF1065670 for ; Sat, 18 Dec 2010 22:02:47 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by mx1.freebsd.org (Postfix) with ESMTP id 8F6AE8FC14 for ; Sat, 18 Dec 2010 22:02:46 +0000 (UTC) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta14.westchester.pa.mail.comcast.net with comcast id kltp1f00317dt5G5Em2n85; Sat, 18 Dec 2010 22:02:47 +0000 Received: from koitsu.dyndns.org ([98.248.34.134]) by omta13.westchester.pa.mail.comcast.net with comcast id km2l1f00F2tehsa3Zm2mN2; Sat, 18 Dec 2010 22:02:47 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 5F4909B427; Sat, 18 Dec 2010 14:02:44 -0800 (PST) Date: Sat, 18 Dec 2010 14:02:44 -0800 From: Jeremy Chadwick To: Dan Allen Message-ID: <20101218220244.GA19039@icarus.home.lan> References: <20101215004712.GA56065@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 22:02:48 -0000 On Sat, Dec 18, 2010 at 11:37:21AM -0700, Dan Allen wrote: > > On 14 Dec 2010, at 5:47 PM, Jeremy Chadwick wrote: > > > Anyway, many people are using the below with success. > > Sorry to say that netwait did NOT in the end fix the problem. > > I however discovered that if I put > > synchronous_dhclient="YES" > > into my /etc/rc.conf file, that over many days & reboots now has > been delivering reliable networking such that ntpd always works. > > Thanks again to everyone for their help. For DHCP-based clients, yeah, netwait itself isn't sufficient; you'd need to use synchronous_dhclient as you discovered. synchronous_dhclient will accomplish the same thing as netwait for DHCP-based clients. Explanation: dhclient will sit and wait until DHCP is fully negotiated before continuing on with remaining rc scripts. The negotiation involves packets going back/forth between the client and server on UDP ports 67 and 68, which obvious acts as a validator that traffic is flowing across the interface. I'll add a comment to the top of the netwait script noting that it should be used for environments where the system is not using DHCP (configured static IPs in rc.conf), and mention for DHCP-based clients to use synchronous_dhclient instead. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP:4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 22:34:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93830106564A for ; Sat, 18 Dec 2010 22:34:51 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from fep28.mx.upcmail.net (fep28.mx.upcmail.net [62.179.121.48]) by mx1.freebsd.org (Postfix) with ESMTP id 0B4A78FC0C for ; Sat, 18 Dec 2010 22:34:50 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep15-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20101218221752.TTI1633.viefep15-int.chello.at@edge01.upcmail.net>; Sat, 18 Dec 2010 23:17:52 +0100 Received: from pinky ([213.46.23.80]) by edge01.upcmail.net with edge id kmHq1f00z1jgp3H01mHrze; Sat, 18 Dec 2010 23:17:52 +0100 X-SourceIP: 213.46.23.80 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-stable@freebsd.org, mamalos@eng.auth.gr References: <201012180947.oBI9lMoU092383@lurza.secnetix.de> <4D0CA06A.2080603@eng.auth.gr> Date: Sat, 18 Dec 2010 23:17:52 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <4D0CA06A.2080603@eng.auth.gr> User-Agent: Opera Mail/11.00 (Win32) X-Cloudmark-Analysis: v=1.1 cv=JvXQbuMnWGQeb488dJ7w43Du7THgE+O7ieb9U20/rjk= c=1 sm=0 a=ibccumBnqR4A:10 a=bgpUlknNv7MA:10 a=IkcTkHD0fZMA:10 a=OTpCH1uB5A2NhoDKScIA:9 a=UPwGookIBHp8xoehJbIA:7 a=Fmv0QQmSyubh4KiFr7uznZlh834A:4 a=QEXdDO2ut3YA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Cc: Subject: Re: vm.swap_reserved toooooo large? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 22:34:51 -0000 On Sat, 18 Dec 2010 12:52:10 +0100, George Mamalakis wrote: > Oliver, > > I am sending you this email outside the list, because I think that ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ That didn't work out as you intended. :-) > enough emails have been sent regarding my message. > Now to your statements: > > On 18/12/2010 11:47 πμ, Oliver Fromme wrote: >> George Mamalakis wrote: >> > Oliver, thanx for your comments. I know it is difficult to choose >> which >> > process to kill and how to be "fair" during such a killing >> procedure. >> > Nevertheless, I would assume that all non-root processes would have >> > higher priority to get killed, and that root's processes would get >> > killed last. >> >> The owner of the process is not taken into consideration, >> because the "run-away" process causing the memory shortage >> may as well be a root-owned process. In such a situation, >> if root processes were exempt from killing, the system >> would deadlock and require a hard reboot. Killing the >> root-owned process is the lesser of two evils. >> > As I explained in one of my previous emails, I expected that root > processes would have *lower priority* than non-root processes; I never > implied that root processes shouldn't get killed, it would be irrational > to say so. >> As I already explained, there is a process flag that root- >> owned processes can set for themselves, preventing the >> kernel from killing them in low-memory situations. See >> the description of the MADV_PROTECT flag in the madvise(2) >> manual page. For example, cron(8) and sshd(8) make use of >> this, so they will not be killed. This is a better way >> than simply excluding all root processes. >> >> > I understand your comments completely, but I was just so >> > surprised when I realized how easy it was for me to kill root >> processes >> > on my system. >> >> Only because you didn't configure resource limits. ;-) >> >> When you're the only user on a machine, such as a desktop >> box, this is usually not a big deal. But in all other >> cases it's strongly recommended to set resource limits, >> in particular for shell users and for server processes. >> >> Without any resource limits, a normal user can starve the >> system and take it down. This is an old and well-known >> problem for all UNIX systems (and most non-UNIX systems, >> too, I guess). You certainly didn't discover any new >> problem. >> >> If you're concerned, configure resource limits. Period. >> > As I stated in my first message (if I recall correctly), all this > happened because I didn't configure my rlimits (it's my laptop). Of > course I am aware of resource limits, and I configure them on most of > the servers I administer for the last 12 years (I've seen my vmstat > showing 500+ processes in blocked-by-io state, and the system wouldn't > hang..:)). I never implied to have discovered anything new, and > especially something regarding resource limits. All my enthusiasm was > caused firstly due to fbsd's memory allocation algorithm (I never knew > the system would assume that it could allocate 500+GB of memory, and the > replies on this issue where very enlightening for me), and secondly due > to fbsd's algorithm on process killing when memory has been starved. > Certainly, I was not surprised by the fact that my system was out of > memory...exceeding my system's memory limits was my experiment in the > first place! > > Anyway, thanx again for your answer and all your pointers (MADV_PROTECT, > etc), and I think there is no need to get angry about my emails. As I > initially stated, my questions where rhetorical, and no answers where > needed. I trusted that there should be a good reason behind this > behavior...Some of you answered on the list and I just replied with my > opinion. Nothing more, nothing less. > > Have a nice day and kind regards, > > mamalos From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 22:51:54 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4E4C1065670 for ; Sat, 18 Dec 2010 22:51:54 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout029.mac.com (asmtpout029.mac.com [17.148.16.104]) by mx1.freebsd.org (Postfix) with ESMTP id 86C618FC14 for ; Sat, 18 Dec 2010 22:51:54 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from [17.153.98.123] by asmtp029.mac.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 64bit)) with ESMTPSA id <0LDN00JVMBIHIJ20@asmtp029.mac.com>; Sat, 18 Dec 2010 14:51:54 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1010190000 definitions=main-1012180126 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2010-12-18_02:2010-12-18, 2010-12-18, 1970-01-01 signatures=0 From: Chuck Swiger In-reply-to: <4D0C49A2.4000203@FreeBSD.org> Date: Sat, 18 Dec 2010 14:51:53 -0800 Message-id: <699B0DD9-A3E0-4508-8AAD-E493EF6DB3D9@mac.com> References: <4D0C49A2.4000203@FreeBSD.org> To: Doug Barton X-Mailer: Apple Mail (2.1082) Cc: freebsd-stable@FreeBSD.org Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 22:51:54 -0000 Hi-- On Dec 17, 2010, at 9:41 PM, Doug Barton wrote: > In order to avoid repeating the scenario where we have a version of BIND > in the base that is not supported by the vendor I am proposing that we > upgrade to BIND 9.6-ESV in FreeBSD RELENG_7. +1 > I am particularly interested in feedback from users with significant DNS > usage that are still using 9.4, especially if you're using the version > in the base. I would appreciate it if you could install 9.6 from the > ports and at minimum run /usr/local/sbin/named-checkconf to see if any > errors are generated. Of course it would be that much more helpful if > you could also evaluate BIND 9.6 in operation in your environment. dns/bind-9.6 seems to work better for me than the 7-STABLE base version of BIND. [1] No errors from named-checkconf. "make test" (under /usr/ports/dns/bind96/work/bind-9.6-ESV-R3/bin/tests after running .../system/ifconfig.sh up) passed all of the tests; and normal operation serving zones and so forth also work fine. One gripe is that stopping via rc script fails: # grep named /etc/rc.conf named_enable="YES" named_program="/usr/local/sbin/named" # /etc/rc.d/named stop named not running? (check /var/run/named/pid). ...because of the "-t /var/named", probably. Is there a symlink or something I can do to fix this? Regards, -- -Chuck [1]: I did some comparisons, and it appears max-cache-size option wasn't being honored by base named (claims to be BIND 9.4.-ESV-R4) from: FreeBSD example.com 7.4-PRERELEASE FreeBSD 7.4-PRERELEASE #1: Tue Dec 14 19:55:55 EST 2010 ...whereas top showed that named from dns/bind-9.6 filled its cache under load until it reached the max-cache-size plus a chunk for the recursive clients, and then remained at a stable size afterwards. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 23:07:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5559E106564A for ; Sat, 18 Dec 2010 23:07:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id F29D48FC15 for ; Sat, 18 Dec 2010 23:07:14 +0000 (UTC) Received: (qmail 12830 invoked by uid 399); 18 Dec 2010 23:07:13 -0000 Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 18 Dec 2010 23:07:13 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4D0D3E9F.4010100@FreeBSD.org> Date: Sat, 18 Dec 2010 15:07:11 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101210 Thunderbird/3.1.7 MIME-Version: 1.0 To: Kostik Belousov References: <4D0C49A2.4000203@FreeBSD.org> <20101218111538.GZ33073@deviant.kiev.zoral.com.ua> In-Reply-To: <20101218111538.GZ33073@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Following vendor release cycle (Was: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 23:07:15 -0000 On 12/18/2010 03:15, Kostik Belousov wrote: > On Fri, Dec 17, 2010 at 09:41:54PM -0800, Doug Barton wrote: >> Howdy, >> >> Traditionally for contributed software generally, and BIND in particular >> we have tried to keep the major version of the contributed software >> consistent throughout a given RELENG_$N branch of FreeBSD. Hopefully the >> reasoning for this is obvious, we want to avoid POLA violations. > Actually not. My own POV is that we should follow the vendor release > cycle, and not the FreeBSD release cycle, for the contributed software. > > I do not advocate immediate upgrade of the third-party software that > reached its EOL, but I think that we should do this without pushback > if maintainer consider the neccessity of upgrade. Just to be clear, there were considerable discussions, over a long period of time; between myself, the release engineers, and the security-officer team regarding the subject of BIND 9.3 in RELENG_6. I was given the green light to upgrade if I felt it was necessary (as you're suggesting here) but the final decision to live with the status quo was mine, and I accept responsibility for it. My reasoning was as follows: 1. All the latest versions of BIND are available in ports, and I made sure that they worked in RELENG_6 so that users who wanted to stay at that OS level but had more serious DNS needs had an easy path. 2. Because BIND 9.3 lacked the ability to do modern DNSSEC anyone who wanted that feature would have to upgrade anyway. 3. BIND 9.3 was still suitable for the (primary) stated purpose of BIND in the base, a basic local resolving name server. 4. BIND 9.3 was different enough that users migrating from it to more modern versions were experiencing problems. 5. Users were naturally migrating to RELENG_[78] at a pace which minimized the impact of the issue. If any of those things had stopped being true my decision would have been different, but as it was I chose to "grin and bear it" in order to avoid the POLA violation for any users who were actually using BIND 9.3 in RELENG_6. However, the circumstances for BIND 9.4 and RELENG_7 are different, and much more amenable to the upgrade, which is why I'm proposing it. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 23:15:25 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BBD71065670 for ; Sat, 18 Dec 2010 23:15:25 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 072F98FC13 for ; Sat, 18 Dec 2010 23:15:24 +0000 (UTC) Received: (qmail 21431 invoked by uid 399); 18 Dec 2010 23:15:24 -0000 Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 18 Dec 2010 23:15:24 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4D0D408A.2020802@FreeBSD.org> Date: Sat, 18 Dec 2010 15:15:22 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101210 Thunderbird/3.1.7 MIME-Version: 1.0 To: Garrett Wollman References: <201012181716.oBIHGS3m099731@hergotha.csail.mit.edu> In-Reply-To: <201012181716.oBIHGS3m099731@hergotha.csail.mit.edu> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Enabling DNSSEC (Was: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 23:15:25 -0000 On 12/18/2010 09:16, Garrett Wollman wrote: > In article<4D0C49A2.4000203@FreeBSD.org>, dougb@freebsd.org writes: > >> In order to avoid repeating the scenario where we have a version of BIND >> in the base that is not supported by the vendor I am proposing that we >> upgrade to BIND 9.6-ESV in FreeBSD RELENG_7. > > +1 > > All users are going to want working DNSsec soon, if they don't > already, and that requires 9.6. (In fact, we should start shipping > with DNSsec enabled by default and the root key pre-configured, if we > aren't already doing so.) I'm not planning to do that in the base for a couple of reasons. The primary one being that the way BIND 9.6 handles the root key it would have to be manually re-configured when the root key changes. When that happens (not IF, it will happen someday) users who have the old configuration will no longer be able to validate. The other reason I don't want to do it in the base is that one open source OS vendor has already been burned by doing something similar, and I don't want to repeat that mistake. What I do plan to do (and hopefully before the upcoming release) is to make ports for BIND 9.6 and 9.7+ methods of handling DNSSEC so that users can enable and disable it easily, have a very easy way of being notified of changes, doing the updates, etc. It's also worth pointing out that BIND 9.7 and up support RFC 5011 rollover of the root key, which ICANN is going to perform, which means that people with "old" root keys in their configurations will be much more resilient. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 23:20:43 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDB8B106564A for ; Sat, 18 Dec 2010 23:20:43 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 4E4DA8FC0A for ; Sat, 18 Dec 2010 23:20:42 +0000 (UTC) Received: (qmail 25343 invoked by uid 399); 18 Dec 2010 23:20:42 -0000 Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 18 Dec 2010 23:20:42 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4D0D41C9.8060807@FreeBSD.org> Date: Sat, 18 Dec 2010 15:20:41 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101210 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4D0C49A2.4000203@FreeBSD.org> <699B0DD9-A3E0-4508-8AAD-E493EF6DB3D9@mac.com> In-Reply-To: <699B0DD9-A3E0-4508-8AAD-E493EF6DB3D9@mac.com> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: /etc/rc.d/named stop (Was: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 23:20:43 -0000 On 12/18/2010 14:51, Chuck Swiger wrote: >One gripe is that stopping via rc script fails: > > # grep named /etc/rc.conf named_enable="YES" > named_program="/usr/local/sbin/named" > > # /etc/rc.d/named stop named not running? (check > /var/run/named/pid). > > ...because of the "-t /var/named", probably. Is there a symlink or > something I can do to fix this? If you start named with the rc.d script it should do that for you. ll /var/run/named/pid lrwxr-xr-x 1 root bind 28 Dec 18 13:52 /var/run/named/pid@ -> /var/named/var/run/named/pid Make sure you don't have named_symlink_enable=NO somewhere, for example in /etc/rc.conf.local. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 23:41:33 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40D631065672; Sat, 18 Dec 2010 23:41:33 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout030.mac.com (asmtpout030.mac.com [17.148.16.105]) by mx1.freebsd.org (Postfix) with ESMTP id 26F238FC17; Sat, 18 Dec 2010 23:41:32 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from [17.153.98.123] by asmtp030.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0LDN00DSIDSJ2M70@asmtp030.mac.com>; Sat, 18 Dec 2010 15:41:09 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1010190000 definitions=main-1012180134 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2010-12-18_02:2010-12-18, 2010-12-18, 1970-01-01 signatures=0 From: Chuck Swiger In-reply-to: <4D0D41C9.8060807@FreeBSD.org> Date: Sat, 18 Dec 2010 15:41:07 -0800 Message-id: <04FBEACB-765E-4EC0-8FAE-3ED26E190773@mac.com> References: <4D0C49A2.4000203@FreeBSD.org> <699B0DD9-A3E0-4508-8AAD-E493EF6DB3D9@mac.com> <4D0D41C9.8060807@FreeBSD.org> To: Doug Barton X-Mailer: Apple Mail (2.1082) Cc: freebsd-stable@freebsd.org Subject: Re: /etc/rc.d/named stop (Was: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 23:41:33 -0000 On Dec 18, 2010, at 3:20 PM, Doug Barton wrote: > If you start named with the rc.d script it should do that for you. > > ll /var/run/named/pid > lrwxr-xr-x 1 root bind 28 Dec 18 13:52 /var/run/named/pid@ -> /var/named/var/run/named/pid > > Make sure you don't have named_symlink_enable=NO somewhere, for example in /etc/rc.conf.local. OK, I have the symlink: # ll /var/run/named/pid lrwxr-xr-x 1 root bind 28 Dec 18 17:27 /var/run/named/pid@ -> /var/named/var/run/named/pid ...and I also have a stale /var/named/var/run/named/pid file; /usr/local/sbin/named from ports seems to be using a /var/named/var/run/named/named.pid file instead. I'm using default launch args (which end up being "/usr/local/sbin/named -t /var/named -u bind") and not changing the default pidfile location in the named.conf AFAICT. Tweaking the links seems to make rc.d script work as expected, so that was helpful, thanks. Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 23:50:13 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBE70106564A for ; Sat, 18 Dec 2010 23:50:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 56DE38FC0A for ; Sat, 18 Dec 2010 23:50:13 +0000 (UTC) Received: (qmail 22329 invoked by uid 399); 18 Dec 2010 23:50:12 -0000 Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 18 Dec 2010 23:50:12 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4D0D48B3.7000104@FreeBSD.org> Date: Sat, 18 Dec 2010 15:50:11 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101210 Thunderbird/3.1.7 MIME-Version: 1.0 To: Chuck Swiger References: <4D0C49A2.4000203@FreeBSD.org> <699B0DD9-A3E0-4508-8AAD-E493EF6DB3D9@mac.com> <4D0D41C9.8060807@FreeBSD.org> <04FBEACB-765E-4EC0-8FAE-3ED26E190773@mac.com> In-Reply-To: <04FBEACB-765E-4EC0-8FAE-3ED26E190773@mac.com> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: /etc/rc.d/named stop (Was: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2010 23:50:13 -0000 On 12/18/2010 15:41, Chuck Swiger wrote: > /usr/local/sbin/named from ports seems to be using a /var/named/var/run/named/named.pid file instead. You're not using the default named.conf file then. What you've got there is the named default, whether from ports or the base, doesn't matter. I always suggest that people start from the default named.conf, and add and subtract accordingly, preferably with include directives to make life easier. Look at pid-file in the options section in particular. :) It's different from the default due to hysterical raisins, which I'm sort of loathe to change now. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/