From owner-freebsd-stable@FreeBSD.ORG Sun Jun 21 05:55:32 2015 Return-Path: Delivered-To: freebsd-stable@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 962D94AD; Sun, 21 Jun 2015 05:55:32 +0000 (UTC) (envelope-from gshapiro@gshapiro.net) Received: from zim.gshapiro.net (zim.gshapiro.net [IPv6:2001:4f8:3:36::224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.gshapiro.net", Issuer "Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7824191B; Sun, 21 Jun 2015 05:55:32 +0000 (UTC) (envelope-from gshapiro@gshapiro.net) Received: from minime.local ([IPv6:2601:647:4e01:8f7b:3119:4472:b3b8:15f2]) (authenticated bits=0) by zim.gshapiro.net (8.15.1.30/8.15.1.30) with ESMTPSA id t5L5tTDK076596 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 20 Jun 2015 22:55:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gshapiro.net; s=gatsby.dkim; t=1434866132; bh=sMZam+daLMIiJz1MNQDIrKLhRwYjzUJrFM65+lVSkFY=; h=Date:From:To:Subject:References:In-Reply-To; b=Fu/2vDCW5BbGSLUrwVbWdK+t1t6+cbLtWuVyjCbkXk6K2vjAlflHRtjLtrWQZ5ghO 4KbFpejpXL4CTDJYcnb1N2Q4s8wtEhnQg35dd5gvNQYLqmdBJUiZoU5GTMtRn/rHg9 TrtRtAqNJkgJt7kXF+vXB0wU2SDutrQ47yXPGBqw= Date: Sat, 20 Jun 2015 22:55:29 -0700 From: Gregory Shapiro To: FreeBSD Errata Notices , freebsd-stable Subject: Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-15:08.sendmail Message-ID: <20150621055529.GC51738@minime.local> References: <201506180553.t5I5rKlO059969@freefall.freebsd.org> <20150618112132.GD7234@pol-server.leissner.se> <20150618132211.GO7234@pol-server.leissner.se> <20150618151032.GB42082@minime.local> <20150618151608.GB3755@pol-server.leissner.se> <20150618154115.GA68153@C02N93Y5G3QT.corp.proofpoint.com> <20150620032245.GF45374@minime.local> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="ibTvN161/egqYuK8" Content-Disposition: inline In-Reply-To: <20150620032245.GF45374@minime.local> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2015 05:55:32 -0000 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > I'll post a patch here by tomorrow for those willing to assist in testing. As promised, there are two patches attached to this email, only one of which is needed (see below). This fixes the case where the DHParameters option is set to a file which doesn't exist, which is the case on newer versions of FreeBSD which enable STARTTLS by default by auto-creating TLS certificates. The first attachment, new.patch, is just the change since the one committed to svn for the errata (i.e., if you have an up to date svn checkout, use this one). The second attachment, full.patch, is the full set of changes needed (i.e., the ones from the first errata to tls.c and the new one to sendmail.h for the outstanding fix). You only need one, don't try to apply both. Since the change is to a .h file, be sure to build carefully (either do a make depend or a make clean if not using a full buildworld). If testing, please try before Monday and drop me a note (no need to reply-all) letting me know if you were successful or not. --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="new.patch" Index: contrib/sendmail/src/sendmail.h =================================================================== --- contrib/sendmail/src/sendmail.h (revision 284661) +++ contrib/sendmail/src/sendmail.h (working copy) @@ -1935,7 +1935,7 @@ /* server requirements */ #define TLS_I_SRV (TLS_I_SRV_CERT | TLS_I_RSA_TMP | TLS_I_VRFY_PATH | \ - TLS_I_VRFY_LOC | TLS_I_TRY_DH | TLS_I_DH512 | \ + TLS_I_VRFY_LOC | TLS_I_TRY_DH | TLS_I_DH1024 | \ TLS_I_CACHE) /* client requirements */ --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="full.patch" Index: contrib/sendmail/src/tls.c =================================================================== --- contrib/sendmail/src/tls.c (revision 283856) +++ contrib/sendmail/src/tls.c (working copy) @@ -650,7 +650,7 @@ ** 1024 generate 1024 bit parameters ** 2048 generate 2048 bit parameters ** /file/name read parameters from /file/name - ** default is: 1024 for server, 512 for client (OK? XXX) + ** default is: 1024 */ if (bitset(TLS_I_TRY_DH, req)) @@ -676,8 +676,8 @@ } if (dhparam == NULL) { - dhparam = srv ? "1" : "5"; - req |= (srv ? TLS_I_DH1024 : TLS_I_DH512); + dhparam = "1"; + req |= TLS_I_DH1024; } else if (*dhparam == '/') { Index: contrib/sendmail/src/sendmail.h =================================================================== --- contrib/sendmail/src/sendmail.h (revision 283856) +++ contrib/sendmail/src/sendmail.h (working copy) @@ -1935,7 +1935,7 @@ /* server requirements */ #define TLS_I_SRV (TLS_I_SRV_CERT | TLS_I_RSA_TMP | TLS_I_VRFY_PATH | \ - TLS_I_VRFY_LOC | TLS_I_TRY_DH | TLS_I_DH512 | \ + TLS_I_VRFY_LOC | TLS_I_TRY_DH | TLS_I_DH1024 | \ TLS_I_CACHE) /* client requirements */ --ibTvN161/egqYuK8-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 21 06:12:24 2015 Return-Path: Delivered-To: freebsd-stable@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 91ED2917 for ; Sun, 21 Jun 2015 06:12:24 +0000 (UTC) (envelope-from gshapiro@gshapiro.net) Received: from zim.gshapiro.net (zim.gshapiro.net [IPv6:2001:4f8:3:36::224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.gshapiro.net", Issuer "Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 779BED47 for ; Sun, 21 Jun 2015 06:12:24 +0000 (UTC) (envelope-from gshapiro@gshapiro.net) Received: from minime.local ([IPv6:2601:647:4e01:8f7b:3119:4472:b3b8:15f2]) (authenticated bits=0) by zim.gshapiro.net (8.15.1.30/8.15.1.30) with ESMTPSA id t5L6CJYD076896 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 20 Jun 2015 23:12:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gshapiro.net; s=gatsby.dkim; t=1434867142; bh=ma/G16Xp7Ida5iPBC/IlKuf1lAvlYxIVHXiHcxesuok=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=mUCMJD1YpdRwQWUySV2eAiMp/SnDGcUIYavbL6d7CGaxug7doNUNZo9/HYlSJe1gW EnxjWy3pOV3OdJKrT/zca/UgQqU88pWZkmhN3Nrsj4Ul5/U8vGPJo1TpPNBO6R2k7A Cstgz5dDM280rL4/j60OHSliTNASfhMbRCnKnDLE= Date: Sat, 20 Jun 2015 23:12:19 -0700 From: Gregory Shapiro To: Jamie Landeg-Jones Cc: freebsd-stable@freebsd.org Subject: Re: Last openssl update brakes localhost email sending Message-ID: <20150621061219.GD51738@minime.local> References: <5582C749.9060801@sentex.net> <20150618150404.GA42082@minime.local> <201506182302.t5IN2l82090847@dyslexicfish.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201506182302.t5IN2l82090847@dyslexicfish.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2015 06:12:24 -0000 > I'm curious... Why is localhost delivery encrypted by default in the first place? sendmail, when acting as a client, employs opportunistic encryption by default. Local mail submission done via command line uses the MSP configuration /etc/mail/submit.cf to send the mail. That submit.cf is built to relay the mail to an MTA host, localhost by default, but can be configured to use a central mail server as well if desired (e.g., for a centralized mail hub, centralized queue management, etc.). The standard submit.cf makes no assumptions about the location of the MTA host and therefore doesn't disable encryption. > The only reason I can think of is if there is some unencrypted TCP > relayed 'tunnel', that has been set up not using ssh or some other > encrypted transport. One other use case (likely not a concern) is to prevent other privileged users from easily snooping localhost traffic (`tcpdump -i lo0 -X -s 0 port 25`). From owner-freebsd-stable@FreeBSD.ORG Sun Jun 21 10:43:44 2015 Return-Path: Delivered-To: freebsd-stable@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B2DEE79; Sun, 21 Jun 2015 10:43:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 06E3E279; Sun, 21 Jun 2015 10:43:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Z6ciy-000JNC-86; Sun, 21 Jun 2015 13:43:40 +0300 Date: Sun, 21 Jun 2015 13:43:40 +0300 From: Slawa Olhovchenkov To: Glen Barber Cc: freebsd-stable@freebsd.org Subject: Re: bsdinstall support for multiple kernels Message-ID: <20150621104340.GB1647@zxy.spb.ru> References: <20150422111334.GS1394@zxy.spb.ru> <20150422111844.GA31769@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150422111844.GA31769@hub.FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2015 10:43:44 -0000 On Wed, Apr 22, 2015 at 11:18:44AM +0000, Glen Barber wrote: > On Wed, Apr 22, 2015 at 02:13:34PM +0300, Slawa Olhovchenkov wrote: > > How to enable bsdinstall support for multiple kernels? > > I am do release with KERNEL="GENERIC VSTREAM" > > On install media I see: > > total 361273 > > -rw-r--r-- 1 root wheel 812 Apr 22 13:03 MANIFEST > > -rw-r--r-- 1 root wheel 65350060 Apr 22 13:03 base.txz > > -rw-r--r-- 1 root wheel 1429196 Apr 22 13:03 doc.txz > > -rw-r--r-- 1 root wheel 884900 Apr 22 13:03 games.txz > > -rw-r--r-- 1 root wheel 78546640 Apr 22 13:03 kernel.VSTREAM.txz > > -rw-r--r-- 1 root wheel 89654176 Apr 22 13:03 kernel.txz > > -rw-r--r-- 1 root wheel 16838288 Apr 22 13:03 lib32.txz > > -rw-r--r-- 1 root wheel 117241492 Apr 22 13:03 src.txz > > > > In MANIFEST: > > > > # cat /media/usr/freebsd-dist/MANIFEST > > base.txz 37829caef728f80374a15a92e129f0b3957e08884f5322686000a6b97da9699d 19559 base "Base system (MANDATORY)" on > > doc.txz dbb99b5b673bb7290f283ecc8bc5868cecb693a2e231fdbad039b6d7ad872f57 121 doc "Additional documentation" off > > games.txz 7eb01b2f857d5c4d075362cc564a522ce1ab60bde21b984015387d767d2b0398 53 games "Games (fortune, etc.)" on > > kernel.VSTREAM.txz 18023a9b347cefa6e89104ce4e92c014d4cd9b676fc0346b5914ca850fbeaf8a 1542 kernel.VSTREAM "Kernel (MANDATORY).VSTREAM" > > kernel.txz f791b8b18eedeecf8bd70ef840fefb439cd50652fbfcdfc0f242ae9c16c172ea 1542 kernel "Kernel (MANDATORY)" on > > lib32.txz 0228f00df8a78feb5e24d7c10c26c72ba29d9f9f8b036e04030782103bf1b3a7 685 lib32 "32-bit compatibility libraries" on > > src.txz 15c4bcfed094a30e41016fcdf27f103216857d96ca7af9e6288f1ded78b1b363 68212 src "System source code" off > > > > bsdinstall don't ask about kernel.VSTREAM and don't install kernel.VSTREAM. > > > > What I miss? > > Currently, the installer only installs GENERIC. > > I have fixes for this in a projects branch, but it's not ready to merge > back to head just yet. (^/projects/release-install-debug if you're > interested.) Do you plan to commit this before 10.2-RELEASE? From owner-freebsd-stable@FreeBSD.ORG Sun Jun 21 11:31:25 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF8BA6C7; Sun, 21 Jun 2015 11:31:24 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Sun, 21 Jun 2015 11:31:21 +0000 From: Glen Barber To: Slawa Olhovchenkov Cc: freebsd-stable@freebsd.org Subject: Re: bsdinstall support for multiple kernels Message-ID: <20150621113121.GU62182@hub.FreeBSD.org> References: <20150422111334.GS1394@zxy.spb.ru> <20150422111844.GA31769@hub.FreeBSD.org> <20150621104340.GB1647@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="L2YZAWjVjAQ1Un1Q" Content-Disposition: inline In-Reply-To: <20150621104340.GB1647@zxy.spb.ru> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2015 11:31:25 -0000 --L2YZAWjVjAQ1Un1Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 21, 2015 at 01:43:40PM +0300, Slawa Olhovchenkov wrote: > On Wed, Apr 22, 2015 at 11:18:44AM +0000, Glen Barber wrote: >=20 > > On Wed, Apr 22, 2015 at 02:13:34PM +0300, Slawa Olhovchenkov wrote: > > > How to enable bsdinstall support for multiple kernels? > > > I am do release with KERNEL=3D"GENERIC VSTREAM" > > > On install media I see: > > > total 361273 > > > -rw-r--r-- 1 root wheel 812 Apr 22 13:03 MANIFEST > > > -rw-r--r-- 1 root wheel 65350060 Apr 22 13:03 base.txz > > > -rw-r--r-- 1 root wheel 1429196 Apr 22 13:03 doc.txz > > > -rw-r--r-- 1 root wheel 884900 Apr 22 13:03 games.txz > > > -rw-r--r-- 1 root wheel 78546640 Apr 22 13:03 kernel.VSTREAM.txz > > > -rw-r--r-- 1 root wheel 89654176 Apr 22 13:03 kernel.txz > > > -rw-r--r-- 1 root wheel 16838288 Apr 22 13:03 lib32.txz > > > -rw-r--r-- 1 root wheel 117241492 Apr 22 13:03 src.txz > > >=20 > > > In MANIFEST: > > >=20 > > > # cat /media/usr/freebsd-dist/MANIFEST > > > base.txz 37829caef728f80374a15a92e129f0b3957e08884f5322686000a= 6b97da9699d 19559 base "Base system (MANDATORY)" on > > > doc.txz dbb99b5b673bb7290f283ecc8bc5868cecb693a2e231fdbad039b6d7ad872= f57 121 doc "Additional documentation" off > > > games.txz 7eb01b2f857d5c4d075362cc564a522ce1ab60bde21b984015387= d767d2b0398 53 games "Games (fortune, etc.)" on > > > kernel.VSTREAM.txz 18023a9b347cefa6e89104ce4e92c014d4cd9b676fc03= 46b5914ca850fbeaf8a 1542 kernel.VSTREAM "Kernel (MANDATORY).VSTR= EAM" > > > kernel.txz f791b8b18eedeecf8bd70ef840fefb439cd50652fbfcdfc0f242a= e9c16c172ea 1542 kernel "Kernel (MANDATORY)" on > > > lib32.txz 0228f00df8a78feb5e24d7c10c26c72ba29d9f9f8b036e0403078= 2103bf1b3a7 685 lib32 "32-bit compatibility libraries" = on > > > src.txz 15c4bcfed094a30e41016fcdf27f103216857d96ca7af9e6288f1ded78b1b= 363 68212 src "System source code" off > > >=20 > > > bsdinstall don't ask about kernel.VSTREAM and don't install kernel.VS= TREAM. > > >=20 > > > What I miss? > >=20 > > Currently, the installer only installs GENERIC. > >=20 > > I have fixes for this in a projects branch, but it's not ready to merge > > back to head just yet. (^/projects/release-install-debug if you're > > interested.) >=20 >=20 > Do you plan to commit this before 10.2-RELEASE? >=20 Absolutely not. It is not ready for head yet, and there are non-trivial changes. Glen --L2YZAWjVjAQ1Un1Q Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVhqCJAAoJEAMUWKVHj+KTEaMP/17rUx0d0uRXTp2frY+DHhvg gwcmAzTN5BlKKwwQxjVZikUswPA7lL1ZEdFDUg1rXazRB3mZAnVK14wMkXx31Zkn 2TBIU5+dBZhf+DeaB1HxLQDnrp5M77Vo5SRfT8kYXaowkfR1th0d65L/CeZXgWeO WjddHdUEsn6s5bjkTh9Z3zzw0h/ZBuLTBHYIigVTCl1Om9JLkOV+08LVtCwPhj2+ JINtENdY15nDSXvPmQWFtP3rdK9Rb+LRcrOcG0tJRHEtbLkx3BVboiXFDguqsBFh XlftkzGv7Mryijo5gqZSDVQFDTzjPENAjA01k5KY3otyorY75fmb4/q3x7DCyGlO o/GAlLscPnjC5Ap5suKSJ95zViArmIP3HZ1hdEv4vRyCEB99RlIcgF87/v1TJ65e mHqgVaNaIAIPXLoMNtF97W6M15N+KNNTP+P7t8v7nW91p/7qdcydYoHf1e5VK4ql bEot247SI1sS5eK8bi9r/k8cowcQBROgY/rP5Rl2DbaBDsm70Ge2rRohvr4yMI+7 1S8iav4jcRUy1PQtFjYwCWCSJvrzj2Eh4CA8jZrErGrQM/EJYXTN8eE1Oxyw8s8q 7byWZUeOPScFfJBzaVaQqQKl6c9UXpLlczp4cIvohAnz9eoSFNZRvbILZJaxOp+1 wQ+PzVuHlWnF3AFeeJv7 =uVzu -----END PGP SIGNATURE----- --L2YZAWjVjAQ1Un1Q-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 22 02:51:37 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44A89635 for ; Mon, 22 Jun 2015 02:51:37 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id 22A479DE for ; Mon, 22 Jun 2015 02:51:36 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from akips.com (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id 9C9DB13D73 for ; Mon, 22 Jun 2015 12:42:14 +1000 (EST) Date: Mon, 22 Jun 2015 12:41:48 +1000 From: Paul Koch To: freebsd-stable@freebsd.org Subject: gptboot: unable to read backup GPT header - virtualbox guest with SAS controller Message-ID: <20150622124148.6aafd502@akips.com> Organization: AKIPS X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY, URIBL_BLOCKED autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on host1.akips.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 02:51:37 -0000 Hi, We get the following error after installing 10.1-p12 in a VirtualBox guest when setup with an emulated LSI / SAS controller and a 50G fixed sized virtual disk: gptboot: error 1 lba 104857599 gptboot: unable to read backup GPT header Can't seem to find anyone who has this same issue. The problem does not exist if we configure the guest with a SATA controller and same size virtual disk. Setup: - 10.1-RELEASE-p12 host - VirtualBox 4.3.28 - 10.1-RELEASE-p12 guest Guest info after boot... # uname -a FreeBSD shed65.akips.com 10.1-RELEASE-p12 FreeBSD 10.1-RELEASE-p12 #0 r284334: Sat Jun 13 05:45:13 UTC 2015 root@shed21.akips.com:/usr/obj/usr/src/sys/GENERIC amd64 # diskinfo -v da0 da0 512 # sectorsize 53687091200 # mediasize in bytes (50G) 104857600 # mediasize in sectors 0 # stripesize 0 # stripeoffset 6527 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. # Disk ident. # gpart show => 34 104857533 da0 GPT (50G) 34 2014 - free - (1.0M) 2048 1024 1 freebsd-boot (512K) 3072 8388608 2 freebsd-swap (4.0G) 8391680 1024 - free - (512K) 8392704 10485760 3 freebsd-ufs [bootme] (5.0G) 18878464 10485760 4 freebsd-ufs (5.0G) 29364224 75491328 5 freebsd-zfs (36G) 104855552 2015 - free - (1.0M) # gpart status Name Status Components da0p1 OK da0 da0p2 OK da0 da0p3 OK da0 da0p4 OK da0 da0p5 OK da0 The primary and backup GPT headers differ, which is expected we think. Primary GPT header # dd if=/dev/da0 bs=512 skip=1 count=1 2>/dev/null | hexdump 0000000 4645 2049 4150 5452 0000 0001 005c 0000 0000010 b85b a5f5 0000 0000 0001 0000 0000 0000 0000020 ffff 063f 0000 0000 0022 0000 0000 0000 0000030 ffde 063f 0000 0000 16e7 cafe 18d1 11e5 0000040 f697 0008 9b27 bd6a 0002 0000 0000 0000 0000050 0080 0000 0080 0000 8856 ebca 0000 0000 0000060 0000 0000 0000 0000 0000 0000 0000 0000 * Backup GPT header # dd if=/dev/da0 bs=512 skip=104857599 count=1 2>/dev/null | hexdump 0000000 4645 2049 4150 5452 0000 0001 005c 0000 0000010 98b1 45c8 0000 0000 ffff 063f 0000 0000 0000020 0001 0000 0000 0000 0022 0000 0000 0000 0000030 ffde 063f 0000 0000 16e7 cafe 18d1 11e5 0000040 f697 0008 9b27 bd6a ffdf 063f 0000 0000 0000050 0080 0000 0080 0000 8856 ebca 0000 0000 0000060 0000 0000 0000 0000 0000 0000 0000 0000 * MD5 of the primary and backup partition tables identical. # dd if=/dev/da0 bs=512 skip=2 count=32 2>/dev/null | md5 8c4510e1854f3371c3241e8a4374dc2c # dd if=/dev/da0 bs=512 skip=104857567 count=32 2>/dev/null | md5 8c4510e1854f3371c3241e8a4374dc2c The guest boots fine, but we always get the gptboot error. Is this just a problem with the virtualbox SAS controller emulation where gptboot can't retrieve the backup table ? Appears to fail in sys/boot/i386/common/drv.c in drvread(). We have another problem to do with the same setup to do with setting bootonce flag not being updated in the backup partition table, but I'll describe that in a separate email. Paul. -- Paul Koch | Founder, CEO AKIPS Network Monitor | akips.com Brisbane, Australia From owner-freebsd-stable@FreeBSD.ORG Mon Jun 22 05:42:14 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C27AAF19 for ; Mon, 22 Jun 2015 05:42:14 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id B0327125 for ; Mon, 22 Jun 2015 05:42:14 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from akips.com (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id 407CF13D73 for ; Mon, 22 Jun 2015 15:42:10 +1000 (EST) Date: Mon, 22 Jun 2015 15:41:43 +1000 From: Paul Koch To: freebsd-stable@freebsd.org Subject: bootonce not set in backup partition table - virtualbox guest with SAS controller Message-ID: <20150622154143.21c68162@akips.com> Organization: AKIPS X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY, URIBL_BLOCKED autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on host1.akips.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 05:42:14 -0000 We seem to have a problem where after setting bootonce on an alternate root partition, the backup partition table does not match the primary after rebooting onto an alternate root. Setup: - 10.1-RELEASE-p12 host - VirtualBox 4.3.28 - 10.1-RELEASE-p12 guest, SAS controller with 50G fixed sized disk. This problem does not happen when we setup the guest with a 50G fixed disk off a SATA controller. We have an custom install setup where we create two 5G root partitions, / and /alt. This allows us to install a new OS+packages onto the alt, set bootonce and reboot using /alt. After our initial install we have: # diskinfo -v da0 da0 512 # sectorsize 53687091200 # mediasize in bytes (50G) 104857600 # mediasize in sectors 0 # stripesize 0 # stripeoffset 6527 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. # Disk ident. # gpart show => 34 104857533 da0 GPT (50G) 34 6 - free - (3.0K) 40 1024 1 freebsd-boot (512K) 1064 8388608 2 freebsd-swap (4.0G) 8389672 984 - free - (492K) 8390656 10485760 3 freebsd-ufs [bootme] (5.0G) 18876416 10485760 4 freebsd-ufs (5.0G) 29362176 75493376 5 freebsd-zfs (36G) 104855552 2015 - free - (1.0M) # gpart status Name Status Components da0p1 OK da0 da0p2 OK da0 da0p3 OK da0 da0p4 OK da0 da0p5 OK da0 MD5 of the primary and backup partition tables are identical. # dd if=/dev/da0 bs=512 skip=2 count=32 2>/dev/null | md5 03fb4d3642e76f454c5649e96512bd6f # dd if=/dev/da0 bs=512 skip=104857567 count=32 2>/dev/null | md5 03fb4d3642e76f454c5649e96512bd6f We then do an upgrade where we install onto /alt and set the appropriate bootonce flag using gpart set -a bootonce -i 4 da0 After it boots on the alternate root: # diskinfo -v da0 da0 512 # sectorsize 53687091200 # mediasize in bytes (50G) 104857600 # mediasize in sectors 0 # stripesize 0 # stripeoffset 6527 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. # Disk ident. # gpart show => 34 104857533 da0 GPT (50G) [CORRUPT] 34 6 - free - (3.0K) 40 1024 1 freebsd-boot (512K) 1064 8388608 2 freebsd-swap (4.0G) 8389672 984 - free - (492K) 8390656 10485760 3 freebsd-ufs [bootme] (5.0G) 18876416 10485760 4 freebsd-ufs [bootonce] (5.0G) 29362176 75493376 5 freebsd-zfs (36G) 104855552 2015 - free - (1.0M) # gpart status Name Status Components da0p1 CORRUPT da0 da0p2 CORRUPT da0 da0p3 CORRUPT da0 da0p4 CORRUPT da0 da0p5 CORRUPT da0 Dump of the primary GPT header # dd if=/dev/da0 bs=512 skip=1 count=1 2>/dev/null | hexdump 0000000 4645 2049 4150 5452 0000 0001 005c 0000 0000010 11e9 ae86 0000 0000 0001 0000 0000 0000 0000020 ffff 063f 0000 0000 0022 0000 0000 0000 0000030 ffde 063f 0000 0000 378d 9abb 18ed 11e5 0000040 9e8d 0008 3f27 7893 0002 0000 0000 0000 0000050 0080 0000 0080 0000 b6fe fca6 0000 0000 0000060 0000 0000 0000 0000 0000 0000 0000 0000 * Dump of the backup GPT header # dd if=/dev/da0 bs=512 skip=104857599 count=1 2>/dev/null | hexdump 0000000 4645 2049 4150 5452 0000 0001 005c 0000 0000010 2997 eaf5 0000 0000 ffff 063f 0000 0000 0000020 0001 0000 0000 0000 0022 0000 0000 0000 0000030 ffde 063f 0000 0000 378d 9abb 18ed 11e5 0000040 9e8d 0008 3f27 7893 ffdf 063f 0000 0000 0000050 0080 0000 0080 0000 d0ab 529c 0000 0000 0000060 0000 0000 0000 0000 0000 0000 0000 0000 * MD5 of the primary and backup partition tables are different. # dd if=/dev/da0 bs=512 skip=2 count=32 2>/dev/null | md5 1e8cc33d84d2ae1ec7621a662ac8cca0 # dd if=/dev/da0 bs=512 skip=104857567 count=32 2>/dev/null | md5 f07e707260e734d4a9d5baeaa077bc58 Dump of the primary partition table # dd if=/dev/da0 bs=512 skip=2 count=32 2>/dev/null | hexdump 0000000 6b9d 83bd 7f41 11dc 0bbe 1500 b860 0f4f 0000010 b409 9abc 18ed 11e5 9e8d 0008 3f27 7893 0000020 0028 0000 0000 0000 0427 0000 0000 0000 0000030 0000 0000 0000 0000 0067 0070 0074 0062 0000040 006f 006f 0074 0000 0000 0000 0000 0000 0000050 0000 0000 0000 0000 0000 0000 0000 0000 * 0000080 7cb5 516e 6ecf 11d6 f88f 0200 092d 2b71 0000090 3b28 9abe 18ed 11e5 9e8d 0008 3f27 7893 00000a0 0428 0000 0000 0000 0427 0080 0000 0000 00000b0 0000 0000 0000 0000 0061 006b 0069 0070 00000c0 0073 002d 0073 0077 0061 0070 0000 0000 00000d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0000100 7cb6 516e 6ecf 11d6 f88f 0200 092d 2b71 0000110 c0b3 9abf 18ed 11e5 9e8d 0008 3f27 7893 0000120 0800 0080 0000 0000 07ff 0120 0000 0000 0000130 0000 0000 0000 0800 0061 006b 0069 0070 0000140 0073 002d 0072 006f 006f 0074 0030 0000 0000150 0000 0000 0000 0000 0000 0000 0000 0000 * 0000180 7cb6 516e 6ecf 11d6 f88f 0200 092d 2b71 0000190 66da 9ac1 18ed 11e5 9e8d 0008 3f27 7893 00001a0 0800 0120 0000 0000 07ff 01c0 0000 0000 00001b0 0000 0000 0000 0400 0061 006b 0069 0070 00001c0 0073 002d 0072 006f 006f 0074 0031 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0000200 7cba 516e 6ecf 11d6 f88f 0200 092d 2b71 0000210 1d30 9ac3 18ed 11e5 9e8d 0008 3f27 7893 0000220 0800 01c0 0000 0000 f7ff 063f 0000 0000 0000230 0000 0000 0000 0000 0061 006b 0069 0070 0000240 0073 002d 0068 006f 006d 0065 0000 0000 0000250 0000 0000 0000 0000 0000 0000 0000 0000 * Dump of the backup partition table # dd if=/dev/da0 bs=512 skip=104857567 count=32 2>/dev/null | hexdump 0000000 6b9d 83bd 7f41 11dc 0bbe 1500 b860 0f4f 0000010 b409 9abc 18ed 11e5 9e8d 0008 3f27 7893 0000020 0028 0000 0000 0000 0427 0000 0000 0000 0000030 0000 0000 0000 0000 0067 0070 0074 0062 0000040 006f 006f 0074 0000 0000 0000 0000 0000 0000050 0000 0000 0000 0000 0000 0000 0000 0000 * 0000080 7cb5 516e 6ecf 11d6 f88f 0200 092d 2b71 0000090 3b28 9abe 18ed 11e5 9e8d 0008 3f27 7893 00000a0 0428 0000 0000 0000 0427 0080 0000 0000 00000b0 0000 0000 0000 0000 0061 006b 0069 0070 00000c0 0073 002d 0073 0077 0061 0070 0000 0000 00000d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0000100 7cb6 516e 6ecf 11d6 f88f 0200 092d 2b71 0000110 c0b3 9abf 18ed 11e5 9e8d 0008 3f27 7893 0000120 0800 0080 0000 0000 07ff 0120 0000 0000 0000130 0000 0000 0000 0800 0061 006b 0069 0070 0000140 0073 002d 0072 006f 006f 0074 0030 0000 0000150 0000 0000 0000 0000 0000 0000 0000 0000 * 0000180 7cb6 516e 6ecf 11d6 f88f 0200 092d 2b71 0000190 66da 9ac1 18ed 11e5 9e8d 0008 3f27 7893 00001a0 0800 0120 0000 0000 07ff 01c0 0000 0000 00001b0 0000 0000 0000 0c00 0061 006b 0069 0070 <<< different 00001c0 0073 002d 0072 006f 006f 0074 0031 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0000200 7cba 516e 6ecf 11d6 f88f 0200 092d 2b71 0000210 1d30 9ac3 18ed 11e5 9e8d 0008 3f27 7893 0000220 0800 01c0 0000 0000 f7ff 063f 0000 0000 0000230 0000 0000 0000 0000 0061 006b 0069 0070 0000240 0073 002d 0068 006f 006d 0065 0000 0000 0000250 0000 0000 0000 0000 0000 0000 0000 0000 * The line at offset 00001b0 is out by one bit. Looks like the bootonce flag is only updated in the primary partition table and not the backup. At this point our boot script tries to do gpart set -a bootme -i 4 da0 gpart unset -a bootme -i 3 da0 gpart unset -a bootonce -i 4 da0 but we of course get gpart: table 'da0' is corrupt: Operation not permitted We currently have a workaround that does gpart recover da0 before doing the set/unset gpart commands. Not sure what we are doing wrong because it all works fine if we configure the vm guest using a SATA controller. Paul. -- Paul Koch | Founder, CEO AKIPS Network Monitor | akips.com Brisbane, Australia From owner-freebsd-stable@FreeBSD.ORG Mon Jun 22 12:46:06 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3630647 for ; Mon, 22 Jun 2015 12:46:06 +0000 (UTC) (envelope-from avanzada@transporteprofesionalmx.com) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hub.freebsd.org", Issuer "hub.freebsd.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B115730F for ; Mon, 22 Jun 2015 12:46:06 +0000 (UTC) (envelope-from avanzada@transporteprofesionalmx.com) Received: by hub.freebsd.org (Postfix) id A2ECA646; Mon, 22 Jun 2015 12:46:06 +0000 (UTC) Delivered-To: stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 86B34645 for ; Mon, 22 Jun 2015 12:46:06 +0000 (UTC) (envelope-from avanzada@transporteprofesionalmx.com) Received: from mail3.transporteprofesionalmx.com (mail3.transporteprofesionalmx.com [66.199.229.124]) by mx1.freebsd.org (Postfix) with ESMTP id 8897730E for ; Mon, 22 Jun 2015 12:46:05 +0000 (UTC) (envelope-from avanzada@transporteprofesionalmx.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=key1; d=transporteprofesionalmx.com; h=Message-ID:From:To:Subject:Date:MIME-Version:Content-Type; i=avanzada@transporteprofesionalmx.com; bh=Uc+i8UDyYrJ6ktfZKqKCar8KinE=; b=oipjtucRor2zZ1wNmTYKesRi1Ntyfx4i5w8SsPJRjS0i8/k8pYHejuvercEdoipYdsSo5r8XSoBs f1xZodfGhQgZAsYuiDZSJtxF9zwkSy1SgjUyD7yCdJEJfTSGSR5O8If/1J2eoTqd5GKlHgVa1PI+ xAiqe6JUQfjv+8H8MCQ= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=key1; d=transporteprofesionalmx.com; b=ias8+MSLRqnAfZXm+9N1zXWrA+1w478tIJCVJEesFimrlg4I8IzhO2dCPxYRU6L/h5BRJ0ixUlj4 ub1ygfH6qk5n5XtUq8E45Ig4Tq5wDWANeDDlVWDjrQSUTKFxpTMqHtZUVTEgwqLz+JuQdziWrkvh z8uinuxmiSyVdMytbVk=; Received: from WIN-M5RODRE2RR8 (66.199.229.124) by mail3.transporteprofesionalmx.com id hh01nu0our0l for ; Mon, 22 Jun 2015 07:45:50 -0500 (envelope-from ) desc: 902830 Message-ID: <88fdf23fa52074d3eb6a8218001afab8@transporteprofesionalmx.com> From: "Operadores de Autotransporte" To: Subject: Programa de formacion avanzada para operadores Date: Mon, 22 Jun 2015 07:45:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 12:46:06 -0000 ¡Facilite y mejore el mantenimiento preventivo! Formacion Avanzada Formación Avanzada para Operadores de Autotransporte 20 y 21 de Julio - Monterrey, N.L. / 27 y 28 de Julio - México, D.F. Le traemos hoy un programa avanzado de profesionalización, para formar personal mejor calificado y adaptado a las exigencias que la modernización del transporte por carretera demanda buscando hacer compatibles la seguridad y la eficiencia para obtener una productividad real y consistente que los mantenga activos en esta estratégica actividad. Comuníquese a nuestro Teléfono: 01-800-212-0746 Lic. Suria Herrera, Líder Comercial, con gusto le atenderá. ¿Desea recibir el Folleto completo? Responda esta invitación con la clave: "Avanzada" y los siguientes datos: Nombre: Empresa: Teléfono: y se lo enviaremos a la brevedad. Este mensaje le ha sido enviado como usuario o bien un usuario le refirió para recibirlo. Si no pertenece al sector y no desea recibir actualizaciones al respecto, stable@freebsd.org responda con el asunto TdQ4w9 From owner-freebsd-stable@FreeBSD.ORG Mon Jun 22 14:18:01 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9628DA8F for ; Mon, 22 Jun 2015 14:18:01 +0000 (UTC) (envelope-from daniel@byte.nl) Received: from mail-out.s1.byte.nl (mail-out.s1.byte.nl [82.94.214.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 58ABF2BF for ; Mon, 22 Jun 2015 14:18:00 +0000 (UTC) (envelope-from daniel@byte.nl) Received: from localhost (localhost [127.0.0.1]) by mail-out.s1.byte.nl (Postfix) with ESMTP id 1E9C610103B for ; Mon, 22 Jun 2015 16:10:07 +0200 (CEST) Received: from mail-out.s1.byte.nl ([127.0.0.1]) by localhost (mail-out3.c1.internal [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46WNvbyTdZ4X for ; Mon, 22 Jun 2015 16:10:04 +0200 (CEST) Received: from [192.168.101.77] (unknown [37.74.194.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: byte0030) by mail-out.s1.byte.nl (Postfix) with ESMTPSA id 211C7100F2B for ; Mon, 22 Jun 2015 16:10:04 +0200 (CEST) Message-ID: <5588173C.30608@byte.nl> Date: Mon, 22 Jun 2015 16:10:04 +0200 From: Daniel Genis User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 14:18:01 -0000 Hello Everyone, we're currently running 10.1-RELEASE, but are encountering the l2arc memory leak which got resolved in 10.1-STABLE r274172, maybe we need r275609 also (as discussed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197164). We are kind of new to FreeBSD, so we're wondering what are the plans to merge these fixes into the 10.1-RELEASE branch ? We'd love to get these fixes without having to rebuild the kernel. Is there any chance for the merge to happen in the near future, or should we compile the kernel to get the fixes? Thanks for you help! With kind regards, Daniel From owner-freebsd-stable@FreeBSD.ORG Mon Jun 22 14:28:15 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FB2AB62 for ; Mon, 22 Jun 2015 14:28:15 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CA6F29C0 for ; Mon, 22 Jun 2015 14:28:14 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id t5MESBn7080586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 22 Jun 2015 08:28:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id t5MESAnw080583; Mon, 22 Jun 2015 08:28:10 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 22 Jun 2015 08:28:10 -0600 (MDT) From: Warren Block To: Paul Koch cc: freebsd-stable@freebsd.org Subject: Re: gptboot: unable to read backup GPT header - virtualbox guest with SAS controller In-Reply-To: <20150622124148.6aafd502@akips.com> Message-ID: References: <20150622124148.6aafd502@akips.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 22 Jun 2015 08:28:11 -0600 (MDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 14:28:15 -0000 On Mon, 22 Jun 2015, Paul Koch wrote: > We get the following error after installing 10.1-p12 in a VirtualBox guest > when setup with an emulated LSI / SAS controller and a 50G fixed sized > virtual disk: > > gptboot: error 1 lba 104857599 > gptboot: unable to read backup GPT header > > Can't seem to find anyone who has this same issue. > > The problem does not exist if we configure the guest with a SATA controller > and same size virtual disk. ... > The guest boots fine, but we always get the gptboot error. > > Is this just a problem with the virtualbox SAS controller emulation where > gptboot can't retrieve the backup table ? That would be my first guess: an off-by-one error preventing the last block from being read. It's not clear which emulated controller was being used for the diskinfo output posted earlier. If it really was an off-by-one bug, the block count would differ depending on the controller. However, some controllers keep metadata on the drive, and report a reduced capacity, and that would have almost the same effect. Seems like there would be a complaint by the controller firmware about the contents of the metadata block, but maybe not by an emulated controller. If controller metadata is the problem, installing FreeBSD using the emulated controller in place should make sure the backup GPT is in the correct position, rather than switching to the SCSI controller after installing with, say, SATA. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 22 18:23:55 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B478ECD5 for ; Mon, 22 Jun 2015 18:23:55 +0000 (UTC) (envelope-from admondmx@transporteprofesionalmx.com) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hub.freebsd.org", Issuer "hub.freebsd.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 95834FB4 for ; Mon, 22 Jun 2015 18:23:55 +0000 (UTC) (envelope-from admondmx@transporteprofesionalmx.com) Received: by hub.freebsd.org (Postfix) id 89F1ECD4; Mon, 22 Jun 2015 18:23:55 +0000 (UTC) Delivered-To: stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6F2EECD3 for ; Mon, 22 Jun 2015 18:23:55 +0000 (UTC) (envelope-from admondmx@transporteprofesionalmx.com) Received: from mail5.transporteprofesionalmx.com (mail5.transporteprofesionalmx.com [66.199.229.126]) by mx1.freebsd.org (Postfix) with ESMTP id 350ABFB3 for ; Mon, 22 Jun 2015 18:23:54 +0000 (UTC) (envelope-from admondmx@transporteprofesionalmx.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=key1; d=transporteprofesionalmx.com; h=Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding; i=admondmx@transporteprofesionalmx.com; bh=yZ1fHYZ9yKg90ymFr+HZC6qotfE=; b=eg0JsUctQAsPdWdZCoGZKViQZcQduJBE5gvxRqeRvreZRmC5cSsdMr/afJ0ISzUnlAk+uG38rZ6J t8EEWsdWLKRZ9yealJxAB9M27h3EMAv+SaHExg4blpvt4tjNc53zhM+8uGaNitUENvEGMo8QOvbS cdWyP2tvVAhWoLixIKs= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=key1; d=transporteprofesionalmx.com; b=iggxnYOb1l+AfEQBwymx95WiITsrJs/aiRi27sM5oYnzfa6HoxJaf8nzY925t05XpHV29mXKW8cu NoWLbIy2wmQ1TZxvE84Q4M/DaNQy62C/VEbMGMaODNHV4/8vF1Zla4QA/9zW49bwgnqXGBcvj0M8 /1kydQjMRUjxwfH4YHw=; Received: from WIN-M5RODRE2RR8 (66.199.229.124) by mail5.transporteprofesionalmx.com id hh19ao0our07 for ; Mon, 22 Jun 2015 13:23:39 -0500 (envelope-from ) desc: 902830 Message-ID: <67272f218e7700070791080e001da29e@transporteprofesionalmx.com> From: "Fatiga en el Transporte" To: Subject: Administracion de la fatiga en el transporte Date: Mon, 22 Jun 2015 13:23:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 18:23:55 -0000 Aparte su lugar hoy ¡ Un sólo día basta para obtener grandes beneficios ! 24 de Julio en México, D.F. 29 de Julio en Monterry, N.L. Administración de la Fatiga en el Transporte ¡No espere a que sea demasiado tarde! Hoy le traemos la manera más efectiva de blindar a su negocio contra los riesgos de la fatiga, cansancio, somnolencia puntual o crónica de sus operadores: un programa práctico e intensivo que le permitirá aumentar la seguridad de su operación, reduciendo la siniestralidad y contribuyendo al crecimiento de su empresa. Comuníquese al Teléfono: 01-800-212-0746 ¿Desea recibir el Folleto completo? Enseguida se lo enviaremos, solamente responda esta invitación con la clave: "Admon" y los siguientes datos: Nombre: Empresa: Teléfono: Lic. Mayra Miranda, Líder de Proyectos, con gusto le atenderé Este mensaje le ha sido enviado como usuario o bien un usuario le refirió para recibirlo. Si no pertenece al sector y no desea recibir actualizaciones al respecto, stable@freebsd.org responda con el asunto MeK4sT From owner-freebsd-stable@FreeBSD.ORG Mon Jun 22 20:48:16 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C3D7075C for ; Mon, 22 Jun 2015 20:48:16 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7FAD3254 for ; Mon, 22 Jun 2015 20:48:16 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 75D9016A402; Mon, 22 Jun 2015 22:48:12 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gsfoUHTTolpL; Mon, 22 Jun 2015 22:48:02 +0200 (CEST) Received: from [IPv6:2001:4cb8:3:1:3531:d392:e648:92ed] (unknown [IPv6:2001:4cb8:3:1:3531:d392:e648:92ed]) by smtp.digiware.nl (Postfix) with ESMTPA id 8F71516A407; Mon, 22 Jun 2015 22:48:02 +0200 (CEST) Message-ID: <55887483.1050505@digiware.nl> Date: Mon, 22 Jun 2015 22:48:03 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Daniel Genis , freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? References: <5588173C.30608@byte.nl> In-Reply-To: <5588173C.30608@byte.nl> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 20:48:16 -0000 On 22/06/2015 16:10, Daniel Genis wrote: > Hello Everyone, > > we're currently running 10.1-RELEASE, but are encountering the l2arc > memory leak which got resolved in 10.1-STABLE r274172, maybe we need > r275609 also (as discussed here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197164). > > We are kind of new to FreeBSD, so we're wondering what are the plans to > merge these fixes into the 10.1-RELEASE branch ? > > We'd love to get these fixes without having to rebuild the kernel. > Is there any chance for the merge to happen in the near future, or > should we compile the kernel to get the fixes? > > Thanks for you help! Daniel, The RELEASE branch is exactly what it says, RELEASE. And is only done once per version when the actual official RELEASE is. So the next one will be the upcoming 10.2-RELEASE. Which is schedules for August 2015 according to: https://www.freebsd.org/releng/ But note that releases are often delayed for a few weeks in de BETA/Release Candidate process. The other way to get to the front of the like is starting and tracking 10-STABLE which is the running front of the kernel/software development. https://www.freebsd.org/doc/handbook/current-stable.html As I read the bug report, the fix is also included in 10-STABLE. Groetjes, --WjW From owner-freebsd-stable@FreeBSD.ORG Tue Jun 23 03:43:02 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2AF26E40 for ; Tue, 23 Jun 2015 03:43:02 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 1BD41988; Tue, 23 Jun 2015 03:43:02 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id BE198E48; Tue, 23 Jun 2015 03:43:00 +0000 (UTC) Date: Tue, 23 Jun 2015 03:42:57 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org Message-ID: <615945691.15.1435030977676.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_stable_10 - Build #1517 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jun 2015 03:43:02 -0000 FreeBSD_stable_10 - Build #1517 - Failure: Check console output at https://jenkins.freebsd.org/job/FreeBSD_stable_10/1517/ to view the results. From owner-freebsd-stable@FreeBSD.ORG Tue Jun 23 06:51:24 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D8D0C52 for ; Tue, 23 Jun 2015 06:51:24 +0000 (UTC) (envelope-from bouncesf1@i-promote.org) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hub.freebsd.org", Issuer "hub.freebsd.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 232488F for ; Tue, 23 Jun 2015 06:51:24 +0000 (UTC) (envelope-from bouncesf1@i-promote.org) Received: by hub.freebsd.org (Postfix) id 189E7C51; Tue, 23 Jun 2015 06:51:24 +0000 (UTC) Delivered-To: stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17B71C50 for ; Tue, 23 Jun 2015 06:51:24 +0000 (UTC) (envelope-from bouncesf1@i-promote.org) Received: from mtag1n16.safe-amazon.com (mtag1n16.safe-amazon.com [5.189.154.10]) by mx1.freebsd.org (Postfix) with ESMTP id B0F928D for ; Tue, 23 Jun 2015 06:51:23 +0000 (UTC) (envelope-from bouncesf1@i-promote.org) To: stable@freebsd.org Subject: =?UTF-8?B?UHJvcG9zaXRpb24gZGUgcmFjaGF0IGRlIHZvcyBjcsOpZGl0cw==?= Message-ID: Date: Tue, 23 Jun 2015 06:50:02 +0000 From: "Rachat Credit France" Reply-To: contact@rachatcreditfrance.com MIME-Version: 1.0 X-Mailer-LID: 2 X-Mailer-RecptId: 3613139 X-Mailer-SID: 4 X-Mailer-Sent-By: 1 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jun 2015 06:51:24 -0000 Comment réduire vos mensualités ? Des experts en regroupement de crédits vous accompagnent pour alléger vos fins de mois et simplifier la gestion de votre budget. Avantages Une réduction de vos mensualités jusqu'à 60%. Une gestion simplifiée de votre budget. Une seule mensualité, un seul interlocuteur. Simulez votre Rachat [http://sf1.safe-amazon.com/link.php?M=3613139&N=4&L=1&F=T] *UN CREDIT VOUS ENGAGE ET DOIT ETRE REMBOURSE. VERIFIEZ VOS CAPACITES DE REMBOURSEMENT AVANT DE VOUS ENGAGER. Aucun versement de quelque nature que ce soit ne peut être exigé d'un particulier avant obtention d'un ou plusieurs prêts d'argent. L'emprunteur dispose d'un délai de réflexion de 14 jours. Lorsqu'une opération de crédit entraine une diminution du montant des mensualités, celle-ci peut entraîner un allongement de la durée de remboursement du crédit et majorer son coût total. EXEMPLE À TITRE INFORMATIF, LE MONTANT DES MENSUALITÉS VARIERA EN FONCTION DU PROFIL ET DES CONDITIONS DE NOS PARTENAIRES. 1er Comparateur de Proximité. Pour voir correctement ce message, rendez vous ici [http://sf1.safe-amazon.com/display.php?M=3613139&C=6763fc9a0e315dca4b37fb4913907461&S=4&L=2&N=1] Conformément à la loi informatique et libertés, vous bénéficiez d'un droit suppression de vos données. Pour ne plus recevoir d'information suivez ce lien [http://sf1.safe-amazon.com/unsubscribe.php?M=3613139&C=6763fc9a0e315dca4b37fb4913907461&L=2&N=4] DevisProx : 105 rue de l Abbe Groult, Paris, Ile de France 75015 From owner-freebsd-stable@FreeBSD.ORG Tue Jun 23 07:48:14 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E685DF50 for ; Tue, 23 Jun 2015 07:48:14 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id CC0D0AD6 for ; Tue, 23 Jun 2015 07:48:14 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id 14E24F9142C for ; Tue, 23 Jun 2015 00:40:30 -0700 (PDT) Date: Tue, 23 Jun 2015 00:39:55 -0700 (MST) From: timp To: freebsd-stable@freebsd.org Message-ID: <1435045195074-6020423.post@n5.nabble.com> In-Reply-To: <20150621055529.GC51738@minime.local> References: <20150618112132.GD7234@pol-server.leissner.se> <20150618132211.GO7234@pol-server.leissner.se> <20150618151032.GB42082@minime.local> <20150618151608.GB3755@pol-server.leissner.se> <20150618154115.GA68153@C02N93Y5G3QT.corp.proofpoint.com> <20150620032245.GF45374@minime.local> <20150621055529.GC51738@minime.local> Subject: Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-15:08.sendmail MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jun 2015 07:48:15 -0000 For the purity of the experiment I installed fresh FreeBSD 10.1-RELEASE amd64. Then I updated it to p13. Tried to send email via localhost - no luck as before. Then I applied Gregory's new.patch patch, rebuilt, installed and rebooted. It works now! I successfully sent and received my email. Here is how it looks now: % echo ttt | mail -s 'ss' ptimofeev@xxx.ru Jun 23 10:31:35 test10-64 sendmail[825]: t5N7VZcc000825: from=timp, size=38, class=0, nrcpts=1, msgid=<201506230731.t5N7VZcc000825@xxx.ru>, relay=timp@localhost Jun 23 10:31:35 test10-64 sendmail[825]: STARTTLS=client, relay=[127.0.0.1], version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-GCM-SHA384, bits=256/256 Jun 23 10:31:35 test10-64 sm-mta[826]: STARTTLS=server, relay=localhost [127.0.0.1], version=TLSv1/SSLv3, verify=NO, cipher=DHE-RSA-AES256-GCM-SHA384, bits=256/256 Jun 23 10:31:35 test10-64 sm-mta[826]: t5N7VZLw000826: from=, size=333, class=0, nrcpts=1, msgid=<201506230731.t5N7VZcc000825@xxx.ru>, proto=ESMTP, daemon=Daemon0, relay=localhost [127.0.0.1] Jun 23 10:31:35 test10-64 sendmail[825]: t5N7VZcc000825: to=ptimofeev@xxx.ru, ctladdr=timp (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30038, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (t5N7VZLw000826 Message accepted for delivery) Jun 23 10:31:36 test10-64 sm-mta[828]: t5N7VZLw000826: to=, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30333, relay=kalmar.xxx.ru. [192.168.31.190], dsn=2.0.0, stat=Sent (t5N7VZaL008894 Message accepted for delivery) I hope this patch will be in p14, as addition to p13! -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-FreeBSD-Announce-FreeBSD-Errata-Notice-FreeBSD-EN-15-08-sendmail-tp6019450p6020423.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Tue Jun 23 10:48:25 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8CF55CD6 for ; Tue, 23 Jun 2015 10:48:25 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 7BDA1936; Tue, 23 Jun 2015 10:48:25 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id DFB6AF7A; Tue, 23 Jun 2015 10:48:24 +0000 (UTC) Date: Tue, 23 Jun 2015 10:48:22 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org Message-ID: <865892623.19.1435056503013.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <615945691.15.1435030977676.JavaMail.jenkins@jenkins-9.freebsd.org> References: <615945691.15.1435030977676.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_stable_10 - Build #1518 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jun 2015 10:48:25 -0000 FreeBSD_stable_10 - Build #1518 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_stable_10/1518/ to view the results. From owner-freebsd-stable@FreeBSD.ORG Tue Jun 23 11:37:12 2015 Return-Path: Delivered-To: freebsd-stable@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C1AAEEDB for ; Tue, 23 Jun 2015 11:37:12 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from cerebro.liukuma.net (cerebro.liukuma.net [IPv6:2a00:d1e0:1000:1b00::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7EB53FF1 for ; Tue, 23 Jun 2015 11:37:12 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from cerebro.liukuma.net (localhost [127.0.0.1]) by cerebro.liukuma.net (Postfix) with ESMTP id 734488A0497; Tue, 23 Jun 2015 14:37:08 +0300 (EEST) DKIM-Filter: OpenDKIM Filter v2.8.3 cerebro.liukuma.net 734488A0497 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=liukuma.net; s=liukudkim; t=1435059428; bh=ozibXZ7mcRLpAd2G9my3oCPgiuDkGiwa4pU/PB1T+3Q=; h=From:To:References:In-Reply-To:Subject:Date; b=Xdiu74ijg+jShvExmEdymQQGtkbeo7jQ7VocYrbhYOULIiwCQ4lMBs+1/JCWOTS5g 29X0ljW56NxmTdoEwDUVlq5v5Lqp2rD0xn3pesCEHynkDIvYryMYy6zeCDkV5z98dQ 8ozjr4qc44HZcIQk+2XkZMbnYoQntcBB6OBRE8Dg= X-Virus-Scanned: amavisd-new at liukuma.net Received: from cerebro.liukuma.net ([127.0.0.1]) by cerebro.liukuma.net (cerebro.liukuma.net [127.0.0.1]) (amavisd-new, port 10027) with LMTP id OWl2D64oWoR6; Tue, 23 Jun 2015 14:37:07 +0300 (EEST) Received: from Rivendell (dsl-kmibrasgw1-50dfdd-193.dhcp.inet.fi [80.223.221.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: ignatz@cerebro.liukuma.net) by cerebro.liukuma.net (Postfix) with ESMTPSA id 6DB758A0494; Tue, 23 Jun 2015 14:37:07 +0300 (EEST) DKIM-Filter: OpenDKIM Filter v2.8.3 cerebro.liukuma.net 6DB758A0494 Message-ID: From: "Reko Turja" To: "Willem Jan Withagen" , "Daniel Genis" , References: <5588173C.30608@byte.nl> <55887483.1050505@digiware.nl> In-Reply-To: <55887483.1050505@digiware.nl> Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? Date: Tue, 23 Jun 2015 14:36:19 +0300 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 Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jun 2015 11:37:12 -0000 -----Original Message----- From: Willem Jan Withagen Sent: Monday, June 22, 2015 11:48 PM To: Daniel Genis ; freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? >> We are kind of new to FreeBSD, so we're wondering what are the plans to >> merge these fixes into the 10.1-RELEASE branch ? >> >> We'd love to get these fixes without having to rebuild the kernel. >> Is there any chance for the merge to happen in the near future, or >> should we compile the kernel to get the fixes? >The RELEASE branch is exactly what it says, RELEASE. And is only done >once per version when the actual official RELEASE is. So the next one >will be the upcoming 10.2-RELEASE. Which is schedules for August 2015 >according to: There are actually 2 branches tracking release: RELEASE which is the original release itself and RELENG which is the release+security and some errata fixes. In practice one should always track and compile RELENG sources with production servers, unless there's a bugfix or added driver that's only available in STABLE. > The other way to get to the front of the like is starting and tracking > 10-STABLE which is the running front of the kernel/software development. STABLE means stable ABI, not necessarily that the branch is running stable. It should be considered more as a beta, than something to track if one does want. (Yes, there can be even major breakages in STABLE. It's not usual but it can happen.) The running front of development is HEAD, which is 11.0 at this time - once latest major release gets first "dot" release, the major version number of HEAD gets advanced. HEAD is more or less recommended for those who can deal with debugging breakages and whatnot and can be severely broken from time to time. It looks like at the moment the fix for you would be temporarily track/compile 10.1 STABLE and then once 10.2 is released start tracking 10.2 RELENG -Reko From owner-freebsd-stable@freebsd.org Wed Jun 24 16:38:06 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6328916D7B for ; Wed, 24 Jun 2015 16:38:06 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7D3C719F4 for ; Wed, 24 Jun 2015 16:38:06 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6805E20988 for ; Wed, 24 Jun 2015 12:38:05 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Wed, 24 Jun 2015 12:38:05 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=X6IWPXlxfzokb7Y aPt9aexjEPtg=; b=SZS1tcocSna4/GNMCXMHvh1ON6B6pnVxfSjqdumutuPnPQ8 7nF85ybDkIIy3lASfi1iCHDOHV09L2Zj7hkYhFgcDNSyl2nUbZ6gT26WN+vYyYyz f9dKnBYtD00ZkxQBXxvKskJQXMDD40yXc4loyfLs49we0RL8x3nmOXJWweZk= Received: by web3.nyi.internal (Postfix, from userid 99) id 447601043F2; Wed, 24 Jun 2015 12:38:05 -0400 (EDT) Message-Id: <1435163885.1004254.306704961.62F7F38C@webmail.messagingengine.com> X-Sasl-Enc: 005EXfSL0sh8nwncg8NA7CyM+Jz+sBvPmtG1RQ5YYkH0 1435163885 From: Mark Felder To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-eecef38c Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? Date: Wed, 24 Jun 2015 11:38:05 -0500 In-Reply-To: <5588173C.30608@byte.nl> References: <5588173C.30608@byte.nl> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2015 16:38:06 -0000 On Mon, Jun 22, 2015, at 09:10, Daniel Genis wrote: > Hello Everyone, > > we're currently running 10.1-RELEASE, but are encountering the l2arc > memory leak which got resolved in 10.1-STABLE r274172, maybe we need > r275609 also (as discussed here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197164). > > We are kind of new to FreeBSD, so we're wondering what are the plans to > merge these fixes into the 10.1-RELEASE branch ? > > We'd love to get these fixes without having to rebuild the kernel. > Is there any chance for the merge to happen in the near future, or > should we compile the kernel to get the fixes? > > Thanks for you help! > > With kind regards, > > Daniel > Wasn't this fixed in the following EN? https://www.freebsd.org/security/advisories/FreeBSD-EN-15:07.zfs.asc If so, it should be solved if you're running 10.1-RELEASE-p11 From owner-freebsd-stable@freebsd.org Wed Jun 24 19:58:31 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34C1E916B3E for ; Wed, 24 Jun 2015 19:58:31 +0000 (UTC) (envelope-from daniel@byte.nl) Received: from mail-out.s1.byte.nl (mail-out.s1.byte.nl [82.94.214.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ECB851F57 for ; Wed, 24 Jun 2015 19:58:30 +0000 (UTC) (envelope-from daniel@byte.nl) Received: from localhost (localhost [127.0.0.1]) by mail-out.s1.byte.nl (Postfix) with ESMTP id 3FB371223CD for ; Wed, 24 Jun 2015 21:58:22 +0200 (CEST) Received: from mail-out.s1.byte.nl ([127.0.0.1]) by localhost (mail-out4.c1.internal [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zij4-rMG9Pkr for ; Wed, 24 Jun 2015 21:58:20 +0200 (CEST) Received: from [192.168.0.101] (ip-217-103-19-76.ip.prioritytelecom.net [217.103.19.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: byte0030) by mail-out.s1.byte.nl (Postfix) with ESMTPSA id 521F412229A for ; Wed, 24 Jun 2015 21:58:20 +0200 (CEST) Message-ID: <558B0BDB.1090201@byte.nl> Date: Wed, 24 Jun 2015 21:58:19 +0200 From: Daniel Genis User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? References: <5588173C.30608@byte.nl> <1435163885.1004254.306704961.62F7F38C@webmail.messagingengine.com> In-Reply-To: <1435163885.1004254.306704961.62F7F38C@webmail.messagingengine.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2015 19:58:31 -0000 Hello erveryone, thanks for all the responses. I missed the 10.1-RELEASE-p11 release, that's exactly what we were looking for. I have looked at the freebsd repo on github. I should have checked the "releng/10.1" branch instead of the "release/10.1.0" branch. We're just a few patchlevels behind and will update. Appreciate the good product, and the prompt help! With kind regards, Daniel On 06/24/2015 06:38 PM, Mark Felder wrote: > > On Mon, Jun 22, 2015, at 09:10, Daniel Genis wrote: >> Hello Everyone, >> >> we're currently running 10.1-RELEASE, but are encountering the l2arc >> memory leak which got resolved in 10.1-STABLE r274172, maybe we need >> r275609 also (as discussed here: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197164). >> >> We are kind of new to FreeBSD, so we're wondering what are the plans to >> merge these fixes into the 10.1-RELEASE branch ? >> >> We'd love to get these fixes without having to rebuild the kernel. >> Is there any chance for the merge to happen in the near future, or >> should we compile the kernel to get the fixes? >> >> Thanks for you help! >> >> With kind regards, >> >> Daniel >> > > Wasn't this fixed in the following EN? > > https://www.freebsd.org/security/advisories/FreeBSD-EN-15:07.zfs.asc > > > If so, it should be solved if you're running 10.1-RELEASE-p11 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Wed Jun 24 20:06:00 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B92AA916DA1 for ; Wed, 24 Jun 2015 20:06:00 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anubis.delphij.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DC6F259C for ; Wed, 24 Jun 2015 20:06:00 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from zeta.ixsystems.com (unknown [12.229.62.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id 7D574185DE; Wed, 24 Jun 2015 13:05:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1435176359; x=1435190759; bh=OK9YbmbgclZZw7Bierurv0ruQT8AXmyqTUUkSiN3T4c=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=SYFfpOTb7INJAk9PB8OFMnt/f+jpd7TaQ/fK86YcKzo5W2tQfpEfftmaQpYfAFLNR Bq9HxeMI69Yl+cI1PQCjlD9wrUgSdw3U3YDwhHNePmwTs/YF/0MRg9zhUTLaXerdgA FiRN65e3KlMknz1eOzQXTFAtli0zeDH6cZQ/SumI= Message-ID: <558B0DA6.8080203@delphij.net> Date: Wed, 24 Jun 2015 13:05:58 -0700 From: Xin Li Reply-To: d@delphij.net Organization: The FreeBSD Project MIME-Version: 1.0 To: Reko Turja , Willem Jan Withagen , Daniel Genis , freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? References: <5588173C.30608@byte.nl> <55887483.1050505@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2015 20:06:00 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 06/23/15 04:36, Reko Turja wrote: > -----Original Message----- From: Willem Jan Withagen Sent: Monday, > June 22, 2015 11:48 PM To: Daniel Genis ; > freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak > fix be pulled into 10.1-RELEASE ? > >>> We are kind of new to FreeBSD, so we're wondering what are the >>> plans to merge these fixes into the 10.1-RELEASE branch ? >>> >>> We'd love to get these fixes without having to rebuild the >>> kernel. Is there any chance for the merge to happen in the near >>> future, or should we compile the kernel to get the fixes? > >> The RELEASE branch is exactly what it says, RELEASE. And is only >> done once per version when the actual official RELEASE is. So the >> next one will be the upcoming 10.2-RELEASE. Which is schedules >> for August 2015 according to: > > There are actually 2 branches tracking release: RELEASE which is > the original release itself and RELENG which is the > release+security and some errata fixes. In practice one should > always track and compile RELENG sources with production servers, > unless there's a bugfix or added driver that's only available in > STABLE. The release/X.Y.Z are actually "tags" and not branches (i.e. read only copy of whatever state is in the release engineering/errata branch, releng/X.Y, is at the time it's released), but technically in svn a tag is also a branch. We do all efforts to avoid making any changes once a tag is laid, because it's a historical and reference point. Users who use -RELEASE should track releng/X.Y branch, or use freebsd-update(1) to keep their system up-to-date. Our goal is to allow a majority of users to use binary releases without having to compile and build themselves. If you know some specific reasons that forces you to compile yourself, please consider sending re@ an email so we will see what we can improve this. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1.5 (FreeBSD) iQIcBAEBCgAGBQJViw2mAAoJEJW2GBstM+nsuKcP/A1cJupbolHtlbbIifahHxAA VpV5/wzb4FZKLiUQX/E8A+iqSw5PPFrWozGkVEDx7xcziZcLTMTgfaZdWgFAoI67 VB1+1cm0cxpm9vVoQahSeCVcTtp/whK26jCnfeDVWnTUcBZTRO85Ni90T5Zyuc7P Hr6E22z7WAFKXB2wP7tOjDS1ZwcUR9wqERWaxDy4V7fLhJh7QK0u6KxAoX/TSRaU E3l5BOdSdfUBH49OkB2WMdB7n8jLWAmMNP0jkT5PxPtAX+3HaZk6xBbLSTSR2/Up Ulw8WKHXhiwYg8lz/c/AZ0W2wJanzfM+tXTSmwgs/50mO+NUbZyPcpAibTp7ozNu ukKzpMwrKEUQ2VdFBq8VuHpNEBnsz6kp3ZTR6qiFL9uJgghjcGuq88/hrS3oz2f8 Skr24McdbhDNJII9OLOZWelERkRyP1jCqqNuwEo4y4QzTCfHB3E+3XxEomkXLiK5 yVvQMwFD2SQSVT4kg/epDWvLu5vaVZgxyjxA8doYeXt1iaURPCt0IsOTeT3oAe7E e2mOi6ub0aDYPox1RSqZ7ZbWpakpTuxtCSgC9u2Qz1ncwhesL+F6BDNcxOPdfeLC x+5yV6K6DE3Xx38B4rxoSEgZlNgoZcKpkX/Tlo5gL9IxBPjRpBqqTPSzRgiyBRe4 9/5oGcFQEDlS4ekPGSR3 =DtFf -----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Thu Jun 25 08:48:04 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6771D98DBFD for ; Thu, 25 Jun 2015 08:48:04 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from smtp.mimar.rs (smtp.mimar.rs [193.53.106.135]) by mx1.freebsd.org (Postfix) with ESMTP id 198F011A0 for ; Thu, 25 Jun 2015 08:48:03 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from vscan.mimar.rs (vscan.mimar.rs [193.53.106.134]) by smtp.mimar.rs (Postfix) with ESMTP id DE3D0898EB for ; Thu, 25 Jun 2015 10:40:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:organization:references:in-reply-to:message-id:subject :subject:from:from:date:date:received:received; s=mimar-0901; t= 1435221652; x=1437036053; bh=INw0kHQgxR0L2wulqUQYLzMWHvO8NC+k7Ls 9iklXcGw=; b=bHCGbYunHRNXCwdk8XxupxyWEOw7eIztVsfbnw9zA6xfaJSSvGg 4ztOqLteglid5j2lZYkfrEY4V0g4kM6XIGou6NDhDDSLgpR5DBtWRBMl8AtGSorG KDdu1AFQqbm9cqKzavxaH+4Z0yAwcPpyKwbXi4ficBFPLVOBcejU+tvY= X-Virus-Scanned: amavisd-new at mimar.rs Received: from smtp.mimar.rs ([193.53.106.135]) by vscan.mimar.rs (vscan.mimar.rs [193.53.106.134]) (amavisd-new, port 10026) with ESMTP id Hksl8jo6cwGb for ; Thu, 25 Jun 2015 10:40:52 +0200 (CEST) Received: from efreet (unknown [193.53.106.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by smtp.mimar.rs (Postfix) with ESMTPSA id F11168947B for ; Thu, 25 Jun 2015 10:40:51 +0200 (CEST) Date: Thu, 25 Jun 2015 10:40:51 +0200 From: Marko =?UTF-8?B?Q3VwYcSH?= To: freebsd-stable@freebsd.org Subject: Re: Last openssl update brakes localhost email sending Message-ID: <20150625104051.06decfa6@efreet> In-Reply-To: <20150618150404.GA42082@minime.local> References: <5582C749.9060801@sentex.net> <20150618150404.GA42082@minime.local> Organization: Mimar X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 08:48:04 -0000 On Thu, 18 Jun 2015 08:04:04 -0700 Gregory Shapiro wrote: > > We ran into this as well. There are notes in UPDATING now that > > have the instructions on what changes need to be done to the > > locale .mc file. >=20 > Even better than UPDATING: >=20 > https://security.FreeBSD.org/advisories/FreeBSD-EN-15:08.sendmail.asc All of my 10.1-RELEASE-p13 systems are affected, some 20 boxes. Sendmail is used only for sending daily and security run outputs, but I am starting to feel unconfortable as it will soon be two weeks since I received them. All those systems are without source code on them, and it is quite inconvenient for me to rebuild from source. Is binary update for this coming soon? Is it coming at all? --=20 Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-stable@freebsd.org Thu Jun 25 09:14:00 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 115BC98D6DE for ; Thu, 25 Jun 2015 09:14:00 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE47A1FDA for ; Thu, 25 Jun 2015 09:13:59 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Z83E2-000B1u-SN; Thu, 25 Jun 2015 12:13:38 +0300 Date: Thu, 25 Jun 2015 12:13:38 +0300 From: Slawa Olhovchenkov To: d@delphij.net Cc: Reko Turja , Willem Jan Withagen , Daniel Genis , freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? Message-ID: <20150625091338.GJ58397@zxy.spb.ru> References: <5588173C.30608@byte.nl> <55887483.1050505@digiware.nl> <558B0DA6.8080203@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <558B0DA6.8080203@delphij.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 09:14:00 -0000 On Wed, Jun 24, 2015 at 01:05:58PM -0700, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 06/23/15 04:36, Reko Turja wrote: > > -----Original Message----- From: Willem Jan Withagen Sent: Monday, > > June 22, 2015 11:48 PM To: Daniel Genis ; > > freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak > > fix be pulled into 10.1-RELEASE ? > > > >>> We are kind of new to FreeBSD, so we're wondering what are the > >>> plans to merge these fixes into the 10.1-RELEASE branch ? > >>> > >>> We'd love to get these fixes without having to rebuild the > >>> kernel. Is there any chance for the merge to happen in the near > >>> future, or should we compile the kernel to get the fixes? > > > >> The RELEASE branch is exactly what it says, RELEASE. And is only > >> done once per version when the actual official RELEASE is. So the > >> next one will be the upcoming 10.2-RELEASE. Which is schedules > >> for August 2015 according to: > > > > There are actually 2 branches tracking release: RELEASE which is > > the original release itself and RELENG which is the > > release+security and some errata fixes. In practice one should > > always track and compile RELENG sources with production servers, > > unless there's a bugfix or added driver that's only available in > > STABLE. > > The release/X.Y.Z are actually "tags" and not branches (i.e. read only > copy of whatever state is in the release engineering/errata branch, > releng/X.Y, is at the time it's released), but technically in svn a > tag is also a branch. We do all efforts to avoid making any changes > once a tag is laid, because it's a historical and reference point. > > Users who use -RELEASE should track releng/X.Y branch, or use > freebsd-update(1) to keep their system up-to-date. > > Our goal is to allow a majority of users to use binary releases > without having to compile and build themselves. If you know some > specific reasons that forces you to compile yourself, please consider > sending re@ an email so we will see what we can improve this. You are some wrong. Tracking releng/X.Y for -RELEASE don't allow reproductable build of -RELEASE image: after existing errata `svn export releng/X.Y` give different result compared to original release build. This is wrong. Building release image must be also from `svn export release/X.Y.Z`. Last release (10.1) will be build from releng/10.1 and I can't find easy way to get source of releases form svn. From owner-freebsd-stable@freebsd.org Thu Jun 25 10:13:44 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D7C698DD59; Thu, 25 Jun 2015 10:13:44 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 58E251E42; Thu, 25 Jun 2015 10:13:44 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 8467151F; Thu, 25 Jun 2015 10:13:44 +0000 (UTC) Date: Thu, 25 Jun 2015 10:13:40 +0000 (GMT) From: jenkins-admin@freebsd.org To: avg@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <711970529.32.1435227224094.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_9-i386 - Build #75 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_9-i386 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 10:13:44 -0000 FreeBSD_STABLE_9-i386 - Build #75 - Failure: Check console output at https://jenkins.freebsd.org/job/FreeBSD_STABLE_9-i386/75/ to view the results. From owner-freebsd-stable@freebsd.org Thu Jun 25 10:34:14 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D1FD98C7F4 for ; Thu, 25 Jun 2015 10:34:14 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 6517E194A; Thu, 25 Jun 2015 10:34:14 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 61BA2520; Thu, 25 Jun 2015 10:34:14 +0000 (UTC) Date: Thu, 25 Jun 2015 10:34:13 +0000 (GMT) From: jenkins-admin@freebsd.org To: avg@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org Message-ID: <1551290483.34.1435228454246.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_stable_9 - Build #812 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_stable_9 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 10:34:14 -0000 FreeBSD_stable_9 - Build #812 - Failure: Check console output at https://jenkins.freebsd.org/job/FreeBSD_stable_9/812/ to view the results. From owner-freebsd-stable@freebsd.org Thu Jun 25 12:24:20 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E3C098C175; Thu, 25 Jun 2015 12:24:20 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id ED5E711F1; Thu, 25 Jun 2015 12:24:19 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 9A72B54E; Thu, 25 Jun 2015 12:24:19 +0000 (UTC) Date: Thu, 25 Jun 2015 12:24:18 +0000 (GMT) From: jenkins-admin@freebsd.org To: avg@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <1986970194.36.1435235058661.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <711970529.32.1435227224094.JavaMail.jenkins@jenkins-9.freebsd.org> References: <711970529.32.1435227224094.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_9-i386 - Build #76 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_9-i386 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 12:24:20 -0000 FreeBSD_STABLE_9-i386 - Build #76 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_STABLE_9-i386/76/ to view the results. From owner-freebsd-stable@freebsd.org Thu Jun 25 13:11:32 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76FBD98CAA1 for ; Thu, 25 Jun 2015 13:11:32 +0000 (UTC) (envelope-from rjk@wintek.com) Received: from local.wintek.com (local.wintek.com [72.12.201.234]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3771A58 for ; Thu, 25 Jun 2015 13:11:31 +0000 (UTC) (envelope-from rjk@wintek.com) Received: from rjk.wintek.local (172.28.1.248) by local.wintek.com (172.28.1.234) with Microsoft SMTP Server id 8.3.389.2; Thu, 25 Jun 2015 09:11:27 -0400 Message-ID: <558BFDFC.3050302@wintek.com> Date: Thu, 25 Jun 2015 09:11:24 -0400 From: Richard Kuhns User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1 MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" Subject: Virtualbox on my new Dell 7810 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 13:11:32 -0000 Hi all, I'm having another issue with my new desktop machine, this time with Virtualbox. I originally sent this to freebsd-emulation a few days ago, but I haven't had any response. I'm hoping someone here can help me. My machine is running FreeBSD 10.2-PRERELEASE #2 r284595 with a GENERIC kernel. I built & installed virtualbox-ose-4.3.28 (and kmod, of course) from ports. /etc/make.conf contains NO_LPR=yes NO_PROFILE= true CUPS_OVERWRITE_BASE=yes OPTIONS_SET= OPTIMIZED_CFLAGS OPTIONS_UNSET= NLS ############ DEFAULT_VERSIONS=python=2.7 python2=2.7 gcc=4.9 bdb=5 perl=5.22 At boot, I now see the following: vboxdrv: fAsync=1 offMin=0x3ae80 offMax=0x3ae80 supdrvGipCreate: omni timer not supported, falling back to synchronous mode I've never seen the supdrvGipCreate message before. I first moved a 32 bit Windows 7 VM from my old desktop which was running a FreeBSD-stable a week or 2 old (literally; I took the drive out of the old machine). The first time I tried to boot the VM it took about 7 minutes. The CPU I allocated to the VM stayed at 100%. After some googling, I turned off hyperthreading in the 7810's BIOS. The VM now boots in a reasonable time and is almost usable. It'll be ok for 2 or 3 seconds, then almost freeze up for a little while (so far always less than a minute), and then be ok again for a few seconds. When it 'freezes up' its CPU is at 100%. As a test I started installing a 64 bit Windows 8.1 VM. It behaves exactly the same way. Does anyone have any ideas or suggestions? I'm hoping there's a BIOS setting I can tweak to make this work. Thanks in advance! -- Richard Kuhns Main Number: 765-742-8428 Wintek Corporation Direct: 765-269-8541 427 N 6th Street Internet Support: 765-269-8503 Lafayette, IN 47901-2211 Consulting: 765-269-8504 From owner-freebsd-stable@freebsd.org Thu Jun 25 13:41:02 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA22798C871 for ; Thu, 25 Jun 2015 13:41:02 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id BBE3E1B84; Thu, 25 Jun 2015 13:41:02 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 7FFD056E; Thu, 25 Jun 2015 13:41:02 +0000 (UTC) Date: Thu, 25 Jun 2015 13:41:01 +0000 (GMT) From: jenkins-admin@freebsd.org To: avg@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org Message-ID: <923261714.38.1435239662435.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1551290483.34.1435228454246.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1551290483.34.1435228454246.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_stable_9 - Build #813 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_stable_9 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 13:41:02 -0000 FreeBSD_stable_9 - Build #813 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_stable_9/813/ to view the results. From owner-freebsd-stable@freebsd.org Thu Jun 25 17:26:03 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B33E698E533 for ; Thu, 25 Jun 2015 17:26:03 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anubis.delphij.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 926EF1DAC for ; Thu, 25 Jun 2015 17:26:03 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from zeta.ixsystems.com (unknown [12.229.62.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id E58AD18BD8; Thu, 25 Jun 2015 10:26:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1435253163; x=1435267563; bh=jdu49Krw7mkhLUW/HbHtFeXT9kGaiy+8oGZXPROwUxk=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=iWp0P5limsq47NWECMpZh3fSU28XqZ3C/qlViuS0TrI0iUrDTA0LBaqs8kR/Huugl kCH6LR0bVwIe3GKFNZdCFicCQtxssjlMTwl58+mpZb2vOLZelu7G+Re9OKkzOptCR4 nOahkcarEOwMIhK0RTufkg911Fwy6cPhqZ0orGaI= Message-ID: <558C39AA.6030501@delphij.net> Date: Thu, 25 Jun 2015 10:26:02 -0700 From: Xin Li Reply-To: d@delphij.net Organization: The FreeBSD Project MIME-Version: 1.0 To: Slawa Olhovchenkov , d@delphij.net CC: Reko Turja , Willem Jan Withagen , Daniel Genis , freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? References: <5588173C.30608@byte.nl> <55887483.1050505@digiware.nl> <558B0DA6.8080203@delphij.net> <20150625091338.GJ58397@zxy.spb.ru> In-Reply-To: <20150625091338.GJ58397@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 17:26:03 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 06/25/15 02:13, Slawa Olhovchenkov wrote: > On Wed, Jun 24, 2015 at 01:05:58PM -0700, Xin Li wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 >> >> On 06/23/15 04:36, Reko Turja wrote: >>> -----Original Message----- From: Willem Jan Withagen Sent: >>> Monday, June 22, 2015 11:48 PM To: Daniel Genis ; >>> freebsd-stable@freebsd.org Subject: Re: can the l2arc memory >>> leak fix be pulled into 10.1-RELEASE ? >>> >>>>> We are kind of new to FreeBSD, so we're wondering what are >>>>> the plans to merge these fixes into the 10.1-RELEASE branch >>>>> ? >>>>> >>>>> We'd love to get these fixes without having to rebuild the >>>>> kernel. Is there any chance for the merge to happen in the >>>>> near future, or should we compile the kernel to get the >>>>> fixes? >>> >>>> The RELEASE branch is exactly what it says, RELEASE. And is >>>> only done once per version when the actual official RELEASE >>>> is. So the next one will be the upcoming 10.2-RELEASE. Which >>>> is schedules for August 2015 according to: >>> >>> There are actually 2 branches tracking release: RELEASE which >>> is the original release itself and RELENG which is the >>> release+security and some errata fixes. In practice one should >>> always track and compile RELENG sources with production >>> servers, unless there's a bugfix or added driver that's only >>> available in STABLE. >> >> The release/X.Y.Z are actually "tags" and not branches (i.e. read >> only copy of whatever state is in the release engineering/errata >> branch, releng/X.Y, is at the time it's released), but >> technically in svn a tag is also a branch. We do all efforts to >> avoid making any changes once a tag is laid, because it's a >> historical and reference point. >> >> Users who use -RELEASE should track releng/X.Y branch, or use >> freebsd-update(1) to keep their system up-to-date. >> >> Our goal is to allow a majority of users to use binary releases >> without having to compile and build themselves. If you know >> some specific reasons that forces you to compile yourself, please >> consider sending re@ an email so we will see what we can improve >> this. > > You are some wrong. Tracking releng/X.Y for -RELEASE don't allow > reproductable build of -RELEASE image: after existing errata `svn > export releng/X.Y` give different result compared to original > release build. This is wrong. Building release image must be also > from `svn export release/X.Y.Z`. Last release (10.1) will be build > from releng/10.1 and I can't find easy way to get source of > releases form svn. releng/* is a _branch_ and it's not intended for reproducible builds. In order to do so one will have to use a tag. However, svn tag is different from CVS or other SCM's tag as they are also a branch. To make things worse, we are using $FreeBSD$ expansion and that would result in different contents in the files, and these strings would end up going into some binaries, and speaking for binary update, you would never want an update to refresh all binaries just because there is difference because one copy is built from tag and another is from branch. To solve this issue we (re@, although it's mostly Glen doing the hard work for the last few releases) always build on releng/* branch, and then lay down tag once the build is considered "gold". To reproduce that build, what I can possibly think of would be something like this: Assuming we have: SVN_RELEASE_VERSION=10.1 FSVN=svn://svn.freebsd.org/base Then one can reliably checkout the branch by doing: svn export -r $(svn info ${FSVN}/release/${SVN_RELEASE_VERSION}.0 | grep 'Last Changed Rev:' | cut -f2 -d:) ${FSVN}/releng/${SVN_RELEASE_VERSION} src Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1.5 (FreeBSD) iQIcBAEBCgAGBQJVjDmlAAoJEJW2GBstM+ns/Q8P/jvLJvSWvO9HENkUSF0hqKCd cz8k53g9tCusNHGmN9j5FEERp1RiEEBLnIBd2yO2TnU6cgZUhq2IpA2+RMz2/RhE XgVp8yrJRebTjstZzFMrYVEnQPKmYFQs8lrsC7sh6tQML2jRGXIDc1jL/rjD73+s a+WoDQdcyqVZaeiLrpCB3Q5HZGDTk0mmHHlvo6kiKFcnGYe4FZ4Gqbt6jF0uj0qm KXita7Ix23IiB0LBr9csV79AfuEe7ZqObj9vQxocHlrPQiwFCfwnDX2edpE2Slmz 4KIHRR4Ogv3KVdrdmopZDNiRcA3/DfC8wyNkOc5rCBtFrDUT4hKTZ2K48YSqKEbZ TbRJutOf9lYpILEOOFS6ZE3QN1Dd2fZeSofoI1Xqt4vHEjxmYtK/pAWf2J44k8SR bMkswHBEpBoqrp5+df6eQsV/mIKHPHYgamzHJHowRMCALOyLjLAtEIYnsRMrL9Je jaHWrrlbrJ0F4yqW7Pm4BhYWZsu8lM5yHhmSQabHv0vUH22k9gAu2ohHGiTYmSu6 oANaYtv1ErIPWICckPQoI1LYTa9mKzLWmsLycTRk2UPDToQUjkzB4RG8l75d8/1n pUxgmN+tn+A2/o/2/L/JHAiXf6dMxrdimOv71D8XgYzNR3WD1RJlciURMt8i1VMM chfd7G6j1ey68TtD2PSD =Ymad -----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Thu Jun 25 18:19:29 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A980A98C46C for ; Thu, 25 Jun 2015 18:19:29 +0000 (UTC) (envelope-from gshapiro@gshapiro.net) Received: from zim.gshapiro.net (zim.gshapiro.net [IPv6:2001:4f8:3:36::224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.gshapiro.net", Issuer "Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9298B1C37 for ; Thu, 25 Jun 2015 18:19:29 +0000 (UTC) (envelope-from gshapiro@gshapiro.net) Received: from C02N93Y5G3QT.corp.proofpoint.com (mx2.proofpoint.com [208.86.202.10]) (authenticated bits=0) by zim.gshapiro.net (8.15.1.36/8.15.1.36) with ESMTPSA id t5PIJMaH044335 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 25 Jun 2015 11:19:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gshapiro.net; s=gatsby.dkim; t=1435256369; bh=rqXV0LSJRPfuIkzuwhpygdQeAo1vxhEDI3ixo0/AQ7k=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=GH3M6L9ANNPd9yaRThDD9KC0guqFFsH4RARlU0R8lOVyjFQ01K2VXzzR5JZx9QBzJ SBiWdvGH0BA1JOMT5bIWiwmA0XmqO0gWQLcswKap56mfVOoyzIkUCYg6GEzxaKT8Yb BHGuYYopzs71BE70/9C2Wz68JeeYvR+IN1hbULII= Date: Thu, 25 Jun 2015 11:19:22 -0700 From: Gregory Shapiro To: Marko =?utf-8?B?Q3VwYcSH?= Cc: freebsd-stable@freebsd.org Subject: Re: Last openssl update brakes localhost email sending Message-ID: <20150625181921.GI85100@C02N93Y5G3QT.corp.proofpoint.com> References: <5582C749.9060801@sentex.net> <20150618150404.GA42082@minime.local> <20150625104051.06decfa6@efreet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150625104051.06decfa6@efreet> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2015 18:19:29 -0000 > All of my 10.1-RELEASE-p13 systems are affected, some 20 boxes. Sendmail > is used only for sending daily and security run outputs, but I am > starting to feel unconfortable as it will soon be two weeks since I > received them. > > All those systems are without source code on them, and it is quite > inconvenient for me to rebuild from source. Is binary update for this > coming soon? Is it coming at all? It is coming, the commit for the stable branches was last night. The Security and RE teams are working on the releng branches next to produce the binary patches. A workaround is available: openssl dhparam -out /etc/mail/certs/dh.param 2048 cd /etc/mail/; make restart From owner-freebsd-stable@freebsd.org Fri Jun 26 02:19:44 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB95998DDDE for ; Fri, 26 Jun 2015 02:19:44 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id D2A711578 for ; Fri, 26 Jun 2015 02:19:44 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from akips.com (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id 7388D13D73; Fri, 26 Jun 2015 12:19:36 +1000 (EST) Date: Fri, 26 Jun 2015 12:19:06 +1000 From: Paul Koch To: Warren Block Cc: freebsd-stable@freebsd.org Subject: Re: gptboot: unable to read backup GPT header - virtualbox guest with SAS controller Message-ID: <20150626121906.598684d1@akips.com> In-Reply-To: References: <20150622124148.6aafd502@akips.com> Organization: AKIPS X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY, URIBL_BLOCKED autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on host1.akips.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2015 02:19:45 -0000 On Mon, 22 Jun 2015 08:28:10 -0600 (MDT) Warren Block wrote: > On Mon, 22 Jun 2015, Paul Koch wrote: > > > We get the following error after installing 10.1-p12 in a VirtualBox guest > > when setup with an emulated LSI / SAS controller and a 50G fixed sized > > virtual disk: > > > > gptboot: error 1 lba 104857599 > > gptboot: unable to read backup GPT header > > > > Can't seem to find anyone who has this same issue. > > > > The problem does not exist if we configure the guest with a SATA controller > > and same size virtual disk. > > ... > > > The guest boots fine, but we always get the gptboot error. > > > > Is this just a problem with the virtualbox SAS controller emulation where > > gptboot can't retrieve the backup table ? > > That would be my first guess: an off-by-one error preventing the last > block from being read. It's not clear which emulated controller was > being used for the diskinfo output posted earlier. If it really was an > off-by-one bug, the block count would differ depending on the > controller. > > However, some controllers keep metadata on the drive, and report a > reduced capacity, and that would have almost the same effect. Seems > like there would be a complaint by the controller firmware about the > contents of the metadata block, but maybe not by an emulated controller. > If controller metadata is the problem, installing FreeBSD using the > emulated controller in place should make sure the backup GPT is in the > correct position, rather than switching to the SCSI controller after > installing with, say, SATA. It does look like gptboot couldn't access the last sector on the virtual SAS disk. We were playing with expanding the size of the virtual disk... Shutting down the VM, expanding the disk size, rebooting, and no gptboot error. Running the appropriate gpart/zpool commands to take up the expanded space, then reboot, and the gptboot error is back again. We've been having similar/same issues with a customer who is running on bare hardware using a Cisco C240 M4 using the mrsas driver, but it also appears to exhibit the problem we were having where the backup partition table does not get updated when the gpart bootonce flag is set so we can boot from an alternate partition. Adding 'gpart recover ${disk}' to our startup script gets around the problem. Paul. -- Paul Koch | Founder, CEO AKIPS Network Monitor | akips.com Brisbane, Australia From owner-freebsd-stable@freebsd.org Fri Jun 26 08:28:14 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 485AC98D76B; Fri, 26 Jun 2015 08:28:14 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD550189F; Fri, 26 Jun 2015 08:28:13 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id t5Q8S9dt086345; Fri, 26 Jun 2015 10:28:09 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 3FC33563; Fri, 26 Jun 2015 10:28:09 +0200 (CEST) Message-ID: <558D0D18.7060209@omnilan.de> Date: Fri, 26 Jun 2015 10:28:08 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org CC: FreeBSD Stable Subject: Bug reminder, KBDMUX_DFLT_KEYMAP + option *KB*_DFLT_KEYMAP and *map.h in sys/conf/files X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig420642347F2AA42DD09B650C" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Fri, 26 Jun 2015 10:28:09 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2015 08:28:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig420642347F2AA42DD09B650C Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello, since 10.2 code freeze will start in a week, I'd like to ask if somebody can have a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193865 + https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193817 Short summary: Defining ..._DFLT_KEYMAP should work sc(4)/vt(4) source/target independent (currently if you have a vt(4) driven building machine you can't build a sc(4) kernel with a non-default "sc" keymap) Also, KBDMUX_DFLT_KEYMAP shloud be made available, like we've had=20 ATKBD_DFLT_KEYMAP and UKBD_DFLT_KEYMAP for a very long time, but truned useless since kbdmux(4) was enabled by default long time ago! Lost discussion was started here: https://lists.freebsd.org/pipermail/freebsd-stable/2014-September/080104.= html Thanks, -Harry --------------enig420642347F2AA42DD09B650C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlWNDRgACgkQLDqVQ9VXb8iycQCgjS4GGgQiKQIrAaeifugOuulI PhIAoKUAV3Bgg04Ny7YDOzCv2l+cIdUD =n+PC -----END PGP SIGNATURE----- --------------enig420642347F2AA42DD09B650C-- From owner-freebsd-stable@freebsd.org Fri Jun 26 17:49:30 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CCAC98C56F; Fri, 26 Jun 2015 17:49:30 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id F13761C2E; Fri, 26 Jun 2015 17:49:29 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 70F261B04; Fri, 26 Jun 2015 17:49:29 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 26 Jun 2015 17:49:27 +0000 From: Glen Barber To: freebsd-snapshots@FreeBSD.org Cc: freebsd-stable@FreeBSD.org Subject: New FreeBSD snapshots available: stable/10 (20150625 r284813) Message-ID: <20150626174927.GA69720@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2015 17:49:30 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 [-stable@ in CC since these are the first 10.2-PRERELEASE builds available since the code slush went into effect, which marks the start of the release cycle.] New FreeBSD development branch installation ISOs and virtual machine disk images have been uploaded to the FTP mirrors. As with any development branch, the installation snapshots are not intended for use on production systems. We do, however, encourage testing on non-production systems as much as possible. Please also consider installing the sysutils/panicmail port, which can help in providing FreeBSD developers the necessary information regarding system crashes. Checksums for the installation ISOs and the VM disk images follow at the end of this email. === Installation ISOs === Installation images are available for: o 10.2-PRERELEASE amd64 GENERIC o 10.2-PRERELEASE i386 GENERIC o 10.2-PRERELEASE ia64 GENERIC o 10.2-PRERELEASE powerpc GENERIC o 10.2-PRERELEASE powerpc64 GENERIC64 o 10.2-PRERELEASE sparc64 GENERIC o 10.2-PRERELEASE armv6 BEAGLEBONE o 10.2-PRERELEASE armv6 CUBOX-HUMMINGBOARD o 10.2-PRERELEASE armv6 GUMSTIX o 10.2-PRERELEASE armv6 RPI-B o 10.2-PRERELEASE armv6 PANDABOARD o 10.2-PRERELEASE armv6 WANDBOARD Snapshots may be downloaded from the corresponding architecture directory from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/ Please be patient if your local FTP mirror has not yet caught up with the changes. Problems, bug reports, or regression reports should be reported through the Bugzilla PR system or the appropriate mailing list, such as -current@ or -stable@ . === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures: o 10.2-PRERELEASE amd64 o 10.2-PRERELEASE i386 Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/ Images are available in the following disk image formats: ~ RAW disk image ~ QCOW2 (qemu) ~ VMDK (qemu, VirtualBox, VMWare) ~ VHD (qemu, xen) The partition layout is: ~ 512k - freebsd-boot GPT partition type (bootfs GPT label) ~ 1GB - freebsd-swap GPT partition type (swapfs GPT label) ~ ~17GB - freebsd-ufs GPT partition type (rootfs GPT label) === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: us-east-1 region: ami-7d3bc116 us-west-1 region: ami-cd8b7d89 us-west-2 region: ami-9b4f48ab sa-east-1 region: ami-271d9f3a eu-west-1 region: ami-0c6b2c7b eu-central-1 region: ami-424b705f ap-northeast-1 region: ami-626ecf62 ap-southeast-1 region: ami-80494fd2 ap-southeast-2 region: ami-9d4c09a7 == ISO CHECKSUMS == o 10.2-PRERELEASE amd64 GENERIC: SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-bootonly.iso) = b3cf2016a048b73ff720866cb8e8f83b842b5a4f64208c615b6ce2cdad503136 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-bootonly.iso.xz) = ffd1cf3e1d653ad6a66fdb8f60b537a97639a74cf50d7b41eb56cdbf60b0d019 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-disc1.iso) = c115e84308b2bf8ff807d6f9766e07cc5509785eb41d48bc9d6dd2cf8ae49e8a SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-disc1.iso.xz) = d2f7e39f1032c83fedd23995b4235eb37db9897f73a788ab2176e8c85bbceadb SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-memstick.img) = eb4924188ad1a841cd68e2007983cd4cd3912ef1b0e1caf86746cadf318a74ea SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-memstick.img.xz) = e10deeef2ef859293567b93617984e1055a44e34c1178d73f64185f04b988572 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-mini-memstick.img) = 9e5d7777a5814d80c7be4c26eebf90b02dcb908dd7106235d0993418a97c469b SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-mini-memstick.img.xz) = 2e5767f82e0cd375be29b91ddbcd9b2a8fd0d17c5aed22528a0e81e5e7dc7dd4 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-bootonly.iso) = 0eee0b96deb9d961360f271d922a03f482b4275565b69a495323fb26cc510d2a SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-bootonly.iso.xz) = d42ac19bb256c26921d4dff325775efec589a2117399837923d99a4db584ef38 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-disc1.iso) = 4cc4ab007fca2551bfa5906ff0cbbb1695e5e0ec7f8c3ddbced52b31f883d3fb SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-disc1.iso.xz) = c77e937571a61e5a55e330c18c30e2eeff1a49a7fc063b8ed80b658468036182 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-memstick.img) = 79de1b81b7d4561af52d9ba29950d2852f719423c70d247a5a50d69cc9181db2 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-memstick.img.xz) = 33844bb9ee77d4f73e1cd0817687423276ed43c6f761aed3361e42f80c975c8c SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-mini-memstick.img) = e9973e02e274c7b261e646de9a5c37654106e42dfacd62e65c02940cecdc5b1c SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-mini-memstick.img.xz) = 2869a9dac1c875f3681c32ab246d6ffe78845fbbe3fb6a994babc4a4af8d99d0 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-bootonly.iso) = c6a73c0563df4a2a3a3359577952e58e MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-bootonly.iso.xz) = bbd92c55ee64cc6d3544330a2938b36e MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-disc1.iso) = 54294c1171cfd98b56714e0bc1daf554 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-disc1.iso.xz) = 146364e7b1194eb8831053097bdc88b2 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-memstick.img) = 88cf766618515425be50d1a67694a7ef MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-memstick.img.xz) = 792cd6acfad0288924ba8620ebf4d7d9 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-mini-memstick.img) = 88e37802c9f8733121252c13e2ca2aa4 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-mini-memstick.img.xz) = 44c7b8bae8823ec198803bf1c46eb435 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-bootonly.iso) = 5a5cdc7f7bd397488b90b22441cf3ecf MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-bootonly.iso.xz) = 54af667a45ecc9adef262798e9a806c3 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-disc1.iso) = 6a136e06f26647529308b3e1385c5469 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-disc1.iso.xz) = 15a76b9e7d6f0b00a6cb13d9583090a6 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-memstick.img) = 9b4abd05d1a117f413ac96b0ba63140a MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-memstick.img.xz) = a8638fe1cffd6b0768a90112768a4f97 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-mini-memstick.img) = d2b2306801ea2cafad3df8a5e3269ed5 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813-uefi-mini-memstick.img.xz) = a9dac3f56c860005b063b26ab5234aea o 10.2-PRERELEASE i386 GENERIC: SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-bootonly.iso) = d9fe1e8a8194bb3476135374316b97604205b17b82f67461316d3047776e705c SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-bootonly.iso.xz) = 54fcd085409c0eeed8f56286a5f2da1dfee0a40a8727fe716622c88352f895e6 SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-disc1.iso) = 87206e8ca3ed9f60e9df2d36164428393a5aac5bed82b2677188342579b9a426 SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-disc1.iso.xz) = ab40479a9318aa4fcb1798527e2223c9780ecdca79aa89375637727f270e59da SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-memstick.img) = d55a7f22ce1c54af6ba2ec95e63830599fedf08a553701a42df63462c53f0fb4 SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-memstick.img.xz) = 85df149b65d490b999adeedd6a35cba5a9d9af57b58f8ca6e515b915f468d630 SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-mini-memstick.img) = 8c407f2ba480045f3efca38b451b7fb2383fae70cbaaa0b06c7454f97cee0348 SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-mini-memstick.img.xz) = 2bb6dff87fd989e7d857bdb350b7fe4f0045fa48868e7a77bc2c05e381bc15d8 MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-bootonly.iso) = 978bd0d4a305674487c159bf43bdce79 MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-bootonly.iso.xz) = 80b56fe52e9fde2cff2decb2f2c934a6 MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-disc1.iso) = c2f3bcf1fc9acde4430056ffeda22bbb MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-disc1.iso.xz) = 7fd26d2cf2469101323a89e82fca576d MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-memstick.img) = 67f617de47c5b58e431ca62bd0a16441 MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-memstick.img.xz) = e623454a1a1f551bdb1bd11e8b3feb10 MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-mini-memstick.img) = bd17aa3611a6e7252f00f2dbf07cdd2f MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813-mini-memstick.img.xz) = 05a07a65edae551b7fac554d4a3ac181 o 10.2-PRERELEASE ia64 GENERIC: SHA256 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-bootonly.iso) = 1f288e002cc08f5a383e47904b0643ee215ac6fd77841759f5316756a5ac82a6 SHA256 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-bootonly.iso.xz) = 5dedbb5a9f6f484b668d3885504923d5a3606a2e5c51266eb711f71db76e72e0 SHA256 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-disc1.iso) = 24cf99e5aff7219f10266bd899766e187d2bccba6576e542297c1f4144875ad9 SHA256 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-disc1.iso.xz) = a4a3355b9e829ace8f06746e69ce60489358d7730aaa8624389ee07228a9c458 SHA256 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-memstick.img) = fa29e5aae2c16b3a76ef2f90c5cc82bc28a1d6b0a1c019427c0b9c504b59bd2c SHA256 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-memstick.img.xz) = e8ff0d6e218441e51b044e59674e9cfa22e1e238ce19659ec3aa08ae9083f100 SHA256 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-mini-memstick.img) = c24b39db83e3b6f00a7b5fd85cd129af094d57ec5d901ab86dc3186d52aef743 SHA256 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-mini-memstick.img.xz) = 1479eb78747f441d76230d9bb8601dd404c0d4401cca55dc6156a8cb063010dc MD5 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-bootonly.iso) = 773b549ca7c0b5643678cf4869002c28 MD5 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-bootonly.iso.xz) = 3a88dc04d2ac2e3c25657ea5f676051a MD5 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-disc1.iso) = 4b5a49ee9f4e57737cf44d5152247217 MD5 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-disc1.iso.xz) = 641c861108cb1c06ccf72ffd8a02a990 MD5 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-memstick.img) = 75c26348e1733e8d668ee2e7169f5dd6 MD5 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-memstick.img.xz) = 13a4549de7055089e0aa110c97c96da3 MD5 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-mini-memstick.img) = a1b396572a02eb506d20da8bd107fe6c MD5 (FreeBSD-10.2-PRERELEASE-ia64-20150625-r284813-mini-memstick.img.xz) = da51456b6861ed0e7d6af104166a9e76 o 10.2-PRERELEASE powerpc GENERIC: SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-bootonly.iso) = c6e1d68baf84fc058b34f9b888a36f0bf71484877d0c6bfd8e6a160c8266aa6e SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-bootonly.iso.xz) = dd8f4538ba9f894309b9f1eefe035d02b7362bb7e2a811908c735836a5a6563e SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-disc1.iso) = 029a9bcfc0e17e984cfc4ac81abbc4e48155970e131214fc7885ed7f55cbf0f1 SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-disc1.iso.xz) = 2cd8d26d13f18a6af37fadbce39cc8f34f39eeb6fb3370fc448dd2b4d54d757e SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-memstick.img) = 39b35f0924548f4b10f08fdf933d3f4c29d13201c5e07ff681b1765a11774641 SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-memstick.img.xz) = d8041b8f7e7caa27640709ccd035e7259da7f6b0d855d9bb6cd3c9977501c256 SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-mini-memstick.img) = 6f912928ac53d5ce05b1257ff2c197c597d52e4af1422f2fa5d3de4a5efe29fc SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-mini-memstick.img.xz) = b5f2d72d4f7df983e43b338cf7bcd844b0885ac599963a17415b74af49b241e0 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-bootonly.iso) = 89b300eddaef11bec0d9950df8fae15b MD5 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-bootonly.iso.xz) = cc43baf5429b9821a7cc16ff59b8cde4 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-disc1.iso) = 2e4821c7841b24b3f997444c488f47ba MD5 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-disc1.iso.xz) = a263ee1238da58a2ad24451cdb425527 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-memstick.img) = e082fc08ceb60db07fd2d248025818ec MD5 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-memstick.img.xz) = 0a643fd653799cb11fcfa7675f19b15b MD5 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-mini-memstick.img) = fc106d78d62e5baede6d455a4aadb499 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-20150625-r284813-mini-memstick.img.xz) = c2306de6b79e86134274858fdb6bda22 o 10.2-PRERELEASE powerpc64 GENERIC64: SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-bootonly.iso) = e872780c85a5e34bb445b6a3b31c9b8c1db478de951991d027a313fcfdee879e SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-bootonly.iso.xz) = 0b4a89651f81c032056ec43ced4cdfacbc76c9d0ef3aa3e2fb52305c15a36a65 SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-disc1.iso) = e54bad78ba326862dea12d077d1c8dd72a1c3d889863bc15bc2aca1e2d62caf1 SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-disc1.iso.xz) = 23c3cf38de96c3d891728be81819759c10f38e4e69b77848bcf2d3a482392a1c SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-memstick.img) = f6630c63307811756aed7d1f9de5ad1936004ea98466a18ad1a6a335118290fb SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-memstick.img.xz) = 35c201fa13569d273b6261ca2774e9dbc003426d286767c51b4fff7001db4c4e SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-mini-memstick.img) = e0511ed6a8b7d10ba567d743e3af3151cf8d719f04a2e6e9dea6181368faf9b8 SHA256 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-mini-memstick.img.xz) = dfb965c397ee29172629bc9b231e3f9948aead88af0594ef4d517b261e545818 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-bootonly.iso) = e26970582fdcf2d015b496de0cd2d231 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-bootonly.iso.xz) = 075bfc8ff6f818d04f439ca9f03d58d3 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-disc1.iso) = ef1423b772eaa8856e702f33fc31dd53 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-disc1.iso.xz) = 35de957675c7a3dbce3ea8b29cd0b383 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-memstick.img) = 02962ca2859b178a6a93f1714d44fdbf MD5 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-memstick.img.xz) = ad6ec4e7653074d48c9f157d84a31c89 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-mini-memstick.img) = 3c9dd4e2cb224bd4791c66ca09f0d439 MD5 (FreeBSD-10.2-PRERELEASE-powerpc-powerpc64-20150625-r284813-mini-memstick.img.xz) = cfa3d6263fa30c84b78bdc4c2beff93a o 10.2-PRERELEASE sparc64 GENERIC: SHA256 (FreeBSD-10.2-PRERELEASE-sparc64-20150625-r284813-bootonly.iso) = ae8848f3df68281d2ede86ce254d50eaedb02c3de8a5696e4547c2fb5aecf299 SHA256 (FreeBSD-10.2-PRERELEASE-sparc64-20150625-r284813-bootonly.iso.xz) = 5e5b1685ea829f3787ee247ce0268dab88df5dc2f4146ee7c7ed347b6227b9fb SHA256 (FreeBSD-10.2-PRERELEASE-sparc64-20150625-r284813-disc1.iso) = e30b45d5dfcb90a3fd90ed6c51ad09d8a3df33ab50952d47f00f506fc8924114 SHA256 (FreeBSD-10.2-PRERELEASE-sparc64-20150625-r284813-disc1.iso.xz) = 80524b5e6dde0e175f0692ec6f31a8c4917e83f699a1039bbc5af99a5a17c05e MD5 (FreeBSD-10.2-PRERELEASE-sparc64-20150625-r284813-bootonly.iso) = db71a3468d61a43bc071fbea75b1e484 MD5 (FreeBSD-10.2-PRERELEASE-sparc64-20150625-r284813-bootonly.iso.xz) = f12a5cce1a5dbff987d9ecc641bcfdd2 MD5 (FreeBSD-10.2-PRERELEASE-sparc64-20150625-r284813-disc1.iso) = 31fdfcabf1b260329565a766c7e6a763 MD5 (FreeBSD-10.2-PRERELEASE-sparc64-20150625-r284813-disc1.iso.xz) = e827e53366f8d7d74666e4be476319db o 10.2-PRERELEASE armv6 BEAGLEBONE: SHA256 (FreeBSD-10.2-PRERELEASE-arm-armv6-BEAGLEBONE-20150625-r284813.img.xz) = aa56dd23079d76fc7ca770df9fca166dce3df26bf6aa922b64c7b486e1582d14 MD5 (FreeBSD-10.2-PRERELEASE-arm-armv6-BEAGLEBONE-20150625-r284813.img.xz) = 795a5f1a9df30e2a5f1e7415292ba241 o 10.2-PRERELEASE armv6 CUBOX-HUMMINGBOARD: SHA256 (FreeBSD-10.2-PRERELEASE-arm-armv6-CUBOX-HUMMINGBOARD-20150625-r284813.img.xz) = 7645b3a937496368334dd4bb511427fee097ca1809fdf85a70692fbda0b25c3e MD5 (FreeBSD-10.2-PRERELEASE-arm-armv6-CUBOX-HUMMINGBOARD-20150625-r284813.img.xz) = 97b2b2e60dd07c0b84b70a83eb5225bd o 10.2-PRERELEASE armv6 GUMSTIX: SHA256 (FreeBSD-10.2-PRERELEASE-arm-armv6-GUMSTIX-20150625-r284813.img.xz) = ee856d36c41cb91a1192fe1821478f4062ca578dce7a16429eef622870c4ee66 MD5 (FreeBSD-10.2-PRERELEASE-arm-armv6-GUMSTIX-20150625-r284813.img.xz) = 5c0b15d453a4f919db4cfe02f94e2c0c o 10.2-PRERELEASE armv6 RPI-B: SHA256 (FreeBSD-10.2-PRERELEASE-arm-armv6-RPI-B-20150625-r284813.img.xz) = af832b68f0cd8fd2d983816de7bd5e4f4e308a18f604e726bc48148806ffc0c1 MD5 (FreeBSD-10.2-PRERELEASE-arm-armv6-RPI-B-20150625-r284813.img.xz) = 1bc29c111f8ae39169f0a2d4eea5876b o 10.2-PRERELEASE armv6 PANDABOARD: SHA256 (FreeBSD-10.2-PRERELEASE-arm-armv6-PANDABOARD-20150625-r284813.img.xz) = b87bbf6edc5f09b64770304f8a9aa253cd8adf3cce6963aa6e3395683930c15f MD5 (FreeBSD-10.2-PRERELEASE-arm-armv6-PANDABOARD-20150625-r284813.img.xz) = 74d568e52bfe9c70993c590729b630eb o 10.2-PRERELEASE armv6 WANDBOARD: SHA256 (FreeBSD-10.2-PRERELEASE-arm-armv6-WANDBOARD-20150625-r284813.img.xz) = 9d13f87bcf8fefb82f6690a158cea74060bda846679ab230f3a618b4d4a7251d MD5 (FreeBSD-10.2-PRERELEASE-arm-armv6-WANDBOARD-20150625-r284813.img.xz) = d76fea1c7af758bbb3de9a44e82e4f55 == VM IMAGE CHECKSUMS == o 10.2-PRERELEASE amd64: SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813.qcow2.xz) = f7aaf37b89e9e3d45791316a6644ea3eacb11d4f15d2254f5a2333aad1482bf8 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813.raw.xz) = aad972da4c3cce11f41f7c9fd39f89ea001aaf3aa96a7ec8c759f4d87e8d51f4 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813.vhd.xz) = d5c555916ecf2a449f2da14e417fdf06c0fd44833a623c246986b779681c5784 SHA256 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813.vmdk.xz) = a20bde749418c904826aa90d726a0c7feb5454a322707626d0998011fc41e768 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813.qcow2.xz) = 270ccea0d4d8c2a807488e5d96b46ccb MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813.raw.xz) = 6b20984aebea5e2e781bea87486e4f79 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813.vhd.xz) = e95cc7cdf2ce1fa293098adb41ff9f49 MD5 (FreeBSD-10.2-PRERELEASE-amd64-20150625-r284813.vmdk.xz) = 38a0bab8a1021d7b26bc924ad9b6fd28 o 10.2-PRERELEASE i386: SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813.qcow2.xz) = 8bf74690dc6dcc70c578e06348ef7bf169981898df93cfdab3e23261b92c88c8 SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813.raw.xz) = 29f8bd6276b61e93b05ca006bd12694cca236f7ab0598c98f85c2610bb96a02c SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813.vhd.xz) = 4d81c45d6e6cf49d1731d6a6e8afa50c374ef305b8db2833b43eccc33dbfb4ea SHA256 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813.vmdk.xz) = 6dbd0f47ac0eee23662e6fd066cbec1ac0d15489e66072342badc3ec7189c08e MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813.qcow2.xz) = 43f5c3cabb296bfa94758b64641e8946 MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813.raw.xz) = dd5583ec657d0402b91e6987e5b02b03 MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813.vhd.xz) = 057af8d4cb888a9917443c61a0c75423 MD5 (FreeBSD-10.2-PRERELEASE-i386-20150625-r284813.vmdk.xz) = 4ca64394ba4f69956ecb98f6fc827c9b Regards, Glen Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVjZCnAAoJEAMUWKVHj+KT7b8QAKRvoKJJ5c27pcvjEvrwW4Fc kG30DpmPCqC7Kh74eqPMbNZyKU9+T59DPa7hc78xuqSS6GIkcgwpnDhvriOgcHMO Pd0vJpjVimdsYx7vF2ft4Gyucvh5SylOs4BYaDL6qY0zbHkN6Owws2B5qfD4ShBO mPwL6Yb6/WLD3CZY17aKwrqlkq/eSbSHRr1EXbo1zQ7SbXZMVDR6FCRBjFdf+3LH 8yuO8BBG7UkF15Rq1uGLb4NaeyloWCyC3SR3PGCywYc3Mdq+yT13fQnv0+YxvqYo hNhPHMV9tIXPnCxYkRNPi6FqOVtxNaEI1vnjYGAXE5ZlbfDB0/DUlEeXetfwJTzC PBIXKy+VfwLCKWbQicBOtudn+TjtfSu3tGez4Im1AvOTLkyxtgQlmt0visXCU0WS AYR2NQRMyDa84/ky4tdP6xtwJvu3MI3d4+Kco8JQZbf2SrJ6lDiSq+HRI3QZ1bn+ vP+QncJHVDT5UHXWz7Gd6e62NOyNvej/dkHsDvhLEEscPZMwclwSb1nW0oiV1lrc moL9j8q1sCq8f8BdmwQwzbnmRFY4UM4ED7T4pQa4BvwH1Fdj3Ts7gsu++nCz/tRh QFLCScD/2BoDvLqOVEyL4sfwzA9REuLA/JxgmdPqv+fmEaqIXUDa3g/AhB2vNg2k WVWJtAGAouy8yBV+mWvT =T+md -----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Fri Jun 26 21:07:20 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD8A498D770 for ; Fri, 26 Jun 2015 21:07:20 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8965011F1 for ; Fri, 26 Jun 2015 21:07:19 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Z8aq1-000186-F5 for freebsd-stable@freebsd.org; Fri, 26 Jun 2015 23:07:05 +0200 Received: from gly.ftfl.ca ([129.173.34.203]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 26 Jun 2015 23:07:05 +0200 Received: from jrm by gly.ftfl.ca with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 26 Jun 2015 23:07:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Joseph Mingrone Subject: suspend/resume regression Date: Fri, 26 Jun 2015 18:06:52 -0300 Lines: 49 Message-ID: <86oak289hv.fsf@gly.ftfl.ca> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: gly.ftfl.ca User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) Cancel-Lock: sha1:7YRMgSvTlyvyHHomqfWCeervrGM= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2015 21:07:20 -0000 --=-=-= Content-Type: text/plain This is on a Lenovo X220. Suspend/resume was working until some time between late April and last week's STABLE snapshot. Suspend always seems to work, but there are two issues with resume. 1) When i915kms isn't loaded, then resuming works, but the screen doesn't come back on. I'm able to ssh in to verify all is well. kern.vty=vt is set in /boot/loader.conf. I'm not positive that this wasn't a problem in the past since I always started the system up with xdm. 2) When i915kms is loaded, then resuming doesn't work and the system needs a hard restart. This definitely used to worked. For case 1), after the system has resumed and i915kms is then loaded the message below appears in /var/log/messages: Jun 26 17:42:22 phe kernel: error: [drm:pid0:intel_lvds_enable] *ERROR* timed out waiting for panel to power off If there is anything I can test or any useful information I left out, just let me know. Joseph --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVjb7sAAoJEDakDIOw1u+e9B4QAJoipTYfvsKSR5ewFM0sNN87 GgUBPFCCjx3fLAJRLGzyhcP2y2GNHi+iT5AIURDYfHDAx0xh6cQK59wh2tq3YwMG Rt+/ygdzdQA16KweZItjO7Lqm72bbgBMobjpVI242FHZm4cKxPBnU/Qfnsfo1ArO nQWFSff3u/T1Yu3ZuWJG3+2XVDa92iJA8OGT2RMef000M3s5TKJVdn599ncTr1QK sIS8rzPKityYj0mzgi5UYSq0Zp7QunDr25jWvavGi6WN/4Dj+QrcKvSM/Byvgppg AYM4vPPz35grCnuU7WIxeYFNeLDy0+p/eXa38FR0fyzb9bl2viZJE3Oxig/PZm+4 30GE6xQtr/BnLQKYOTVx/YNb1u89LTHwZq+c9nbfCDo8w9sVN8DYVfyfNDjTX5Y2 pdivqXImsc9/P2qYRydjC5XX1oxMqjB3X9/Q0mh5DUv2HwcmajUyXksb5rUKWV7g NUR6LykaKqSaAn/8Htw2fh/rw6es3tcZnjcnVSRg4mWa5rKsyCjakfGHLRCKjN0t cdcl9ijZe/7NCkU9iWiuj3++AC+SY5KATZSumJ7qfgjvGaOMkTDoNkucPs4fQz1Q 8c6mXVgbou4Rd2wkB9uo1CBrt4WDsMRpiKud5KZkSBYWYubvNqATN767InANcEFU 3bHX1wdPIh6dwi6azApA =BnVc -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-stable@freebsd.org Sat Jun 27 10:15:20 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4214E98E10C for ; Sat, 27 Jun 2015 10:15:20 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3FB41217 for ; Sat, 27 Jun 2015 10:15:19 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: by lagx9 with SMTP id x9so80029899lag.1 for ; Sat, 27 Jun 2015 03:15:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=k7pAXvFvBsBU54kl0etqXFp9N+ZkfxeRGwgxj9ysDDc=; b=T2tamLmNJ9AJB974Ad/E8CNvRUXVAcZls0NSP8B56uNh7uUmXuNo9pHdexny+btNe6 cc8P96t9U275pitQtGkS8+cEIHe6dHs7+vW4fqFpXJDCZoA1Ass4vp636OB1AKwuv4AL XFJDetHc5x7YOkTjYGi2rnFO6Q/j5DBFaUtItF0xtRsUcicDVypvzo4BbWmfCdSGP2Lq sdIL6eXoR9liDgeHjX3Hz27n8/uIuJ1aXl7dayuKIm2RHk8sonSz7tF/4DyIomSq4iUm afKsiuUr7kRjsm7Pl7mpWEtGfKK01KaT60gXe7r8ZbAuSMakewgtfxEuomizyL2OI/5e HIaQ== MIME-Version: 1.0 X-Received: by 10.112.126.42 with SMTP id mv10mr5604015lbb.58.1435400117817; Sat, 27 Jun 2015 03:15:17 -0700 (PDT) Received: by 10.152.219.35 with HTTP; Sat, 27 Jun 2015 03:15:17 -0700 (PDT) Date: Sat, 27 Jun 2015 13:15:17 +0300 Message-ID: Subject: Bug 201072 From: Kimmo Paasiala To: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2015 10:15:20 -0000 Hello, Could someone take a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201072 ? The patch I've created fixes an issue on stable/10 with various atf directories that are still created by /etc/mtree/* database but are then deleted by 'make delete-old' later. The directories are clearly redundant because the WITH/WITHOUT_ATF flags were removed in https://svnweb.freebsd.org/base?view=revision&sortby=rev&sortdir=down&revision=r261236. -Kimmo From owner-freebsd-stable@freebsd.org Sat Jun 27 12:08:45 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5290998D4DA for ; Sat, 27 Jun 2015 12:08:45 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C5EA1ECA for ; Sat, 27 Jun 2015 12:08:45 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Z8ouR-000FPe-Je; Sat, 27 Jun 2015 15:08:35 +0300 Date: Sat, 27 Jun 2015 15:08:35 +0300 From: Slawa Olhovchenkov To: freebsd-stable@freebsd.org, Ryan Stone Subject: pmcstat on selected cpu -- posible bug? Message-ID: <20150627120835.GK58397@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2015 12:08:45 -0000 I have dual-socket E5v3 system and try to profiling source of CPU load on first socket. cpuset -l 1 pmcstat -S CPU_CLK_UNHALTED_CORE -l 10 -c 1 -n 500 -O sample.out pmcstat -R sample.out -G out.txt -k /boot/kernel.VSTREAM cat out.txt | ./stackcollapse-pmc.pl | ./flamegraph.pl --width=1200 > cpi.svg cpi.svg can be see at http://zxy.spb.ru/cpi.svg I see many times send in t4_intr, but all chelsio interrupt handlers (t4_intr) binded to second CPU socket: # vmstat -i interrupt total rate irq9: acpi0 4 0 irq18: ehci0 ehci1 2893412 2 irq19: xhci0 3185327 2 cpu0:timer 1532629922 1093 irq264: mps0 1399546223 998 irq265: mps1 3638584876 2595 irq266: ahci0 3049531638 2175 irq267: ahci1 707587584 504 irq268: mps2 6161214642 4395 irq270: t5nex0:evt 4 0 irq281: t5nex0:1.0 62811267214 44810 irq282: t5nex0:1.1 63080900542 45002 irq283: t5nex0:1.2 62979721970 44930 irq284: t5nex0:1.3 62968826175 44922 irq285: t5nex0:1.4 62963754266 44918 irq286: t5nex0:1.5 63303732253 45161 irq287: t5nex0:1.6 63012633949 44953 irq288: t5nex0:1.7 63538714658 45328 irq289: t5nex0:1,0 73899 0 irq290: t5nex0:1,1 111666 0 cpu3:timer 1534027652 1094 cpu6:timer 1546786165 1103 cpu13:timer 1588099533 1132 cpu2:timer 1534703017 1094 cpu7:timer 1553306409 1108 cpu9:timer 1586733982 1131 cpu1:timer 1538685850 1097 cpu8:timer 1587569958 1132 cpu5:timer 1537756504 1097 cpu12:timer 1585898180 1131 cpu4:timer 1530812247 1092 cpu10:timer 1586851448 1132 cpu15:timer 1586024994 1131 cpu11:timer 1587022608 1132 cpu14:timer 1586503852 1131 Total 544625692623 388539 # cpuset -g -x 281 irq 281 mask: 8 irq 282 mask: 9 irq 283 mask: 10 irq 284 mask: 11 irq 285 mask: 12 irq 286 mask: 13 irq 287 mask: 14 irq 288 mask: 15 irq 289 mask: 8 irq 290 mask: 12 Cross-checked by dtrace: # dtrace -n '::t4_intr:entry { @[stringof(curthread->td_name), curthread->td_oncpu] = count(); }' dtrace: description '::t4_intr:entry ' matched 1 probe ^C irq282: t5nex0:1.1 9 361413 irq281: t5nex0:1.0 8 361573 irq285: t5nex0:1.4 12 364535 irq283: t5nex0:1.2 10 365919 irq284: t5nex0:1.3 11 366386 irq287: t5nex0:1.6 14 367603 irq286: t5nex0:1.5 13 368409 irq288: t5nex0:1.7 15 371441 What is wrong? Bug in pmcstat? From owner-freebsd-stable@freebsd.org Sat Jun 27 12:08:58 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3992498D4F2 for ; Sat, 27 Jun 2015 12:08:58 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.31.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F1ED71F6F for ; Sat, 27 Jun 2015 12:08:57 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.151.233] (helo=fabiankeil.de) by smtprelay06.ispgateway.de with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1Z8omF-0007r1-SW for freebsd-stable@FreeBSD.org; Sat, 27 Jun 2015 14:00:07 +0200 Date: Sat, 27 Jun 2015 14:00:08 +0200 From: Fabian Keil Cc: freebsd-stable@FreeBSD.org Subject: Re: New FreeBSD snapshots available: stable/10 (20150625 r284813) Message-ID: <6c6ee862.655af331@fabiankeil.de> In-Reply-To: <20150626174927.GA69720@FreeBSD.org> References: <20150626174927.GA69720@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/0fV2PR1jBp53_K_1fw6L7FM"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2015 12:08:58 -0000 --Sig_/0fV2PR1jBp53_K_1fw6L7FM Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Glen Barber wrote: > [-stable@ in CC since these are the first 10.2-PRERELEASE builds > available since the code slush went into effect, which marks the start > of the release cycle.] >=20 > New FreeBSD development branch installation ISOs and virtual machine > disk images have been uploaded to the FTP mirrors. >=20 > As with any development branch, the installation snapshots are not > intended for use on production systems. We do, however, encourage > testing on non-production systems as much as possible. ggatec and ggatel are still broken on i386: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197309 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199559 If the ZFS root pools isn't found right away, the system deadlocks: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D198563 Patches are available so it would be great if these issues could be fixed before the release. Fabian --Sig_/0fV2PR1jBp53_K_1fw6L7FM Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlWOkEMACgkQBYqIVf93VJ0hZQCgwzvEkJDuB5F5hr7c61z8ZzHy u10AniRJiYIpKDa4R4Ukwt3PM55fizxS =BYF2 -----END PGP SIGNATURE----- --Sig_/0fV2PR1jBp53_K_1fw6L7FM-- From owner-freebsd-stable@freebsd.org Sat Jun 27 17:03:45 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27A5698C0C1 for ; Sat, 27 Jun 2015 17:03:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E4876119C for ; Sat, 27 Jun 2015 17:03:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igcsj18 with SMTP id sj18so52469411igc.1 for ; Sat, 27 Jun 2015 10:03:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HVEiuppmHuX7KHVJ0ebQ4BNTOG4VnhmlE83+uqCaqmI=; b=my/OJi/7qW9T/1cYD3IPi1qzpu8xQHkFsij2vdPhe3gFi8vjjJEkDS27GvAvTjOQ+k JUuQRvwRPQKyu7fpOg9kx5ln6J73yj1hWtu+8kQ/8ePM5j8xE3TZ3jJmeAT1iKvIsUL8 BjIQ6ileqB+PirXyapQ+SFdxK+whF81HwEJHhSrljZscdaDZ9z95wMFgNQK6Mzzh1d1X NX5f59SLPigEjfLEein8/AnKDT5Dd6FqKzYotrwitSsEtfF8XnNOvehx3ZjCsOYmJkiP nqBdmYAFIGNaGPunZHerdsCVxJdWNv0T01dlcN6jvnRIefNMa/717Gkp2I845KllEBOT 0o9Q== MIME-Version: 1.0 X-Received: by 10.107.155.74 with SMTP id d71mr9681562ioe.29.1435424624246; Sat, 27 Jun 2015 10:03:44 -0700 (PDT) Received: by 10.36.38.133 with HTTP; Sat, 27 Jun 2015 10:03:44 -0700 (PDT) In-Reply-To: <86oak289hv.fsf@gly.ftfl.ca> References: <86oak289hv.fsf@gly.ftfl.ca> Date: Sat, 27 Jun 2015 10:03:44 -0700 Message-ID: Subject: Re: suspend/resume regression From: Adrian Chadd To: Joseph Mingrone Cc: FreeBSD Stable Mailing List Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2015 17:03:45 -0000 does it always fail now? -a On 26 June 2015 at 14:06, Joseph Mingrone wrote: > This is on a Lenovo X220. Suspend/resume was working until some time > between late April and last week's STABLE snapshot. > > Suspend always seems to work, but there are two issues with resume. > > 1) When i915kms isn't loaded, then resuming works, but the screen > doesn't come back on. I'm able to ssh in to verify all is well. > kern.vty=vt is set in /boot/loader.conf. I'm not positive that this > wasn't a problem in the past since I always started the system up with > xdm. > > 2) When i915kms is loaded, then resuming doesn't work and the system > needs a hard restart. This definitely used to worked. > > For case 1), after the system has resumed and i915kms is then loaded > the message below appears in /var/log/messages: > > Jun 26 17:42:22 phe kernel: error: [drm:pid0:intel_lvds_enable] *ERROR* > timed out waiting for panel to power off > > If there is anything I can test or any useful information I left out, > just let me know. > > Joseph From owner-freebsd-stable@freebsd.org Sat Jun 27 22:13:54 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B817E98E01C for ; Sat, 27 Jun 2015 22:13:54 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 79A7E1AA8 for ; Sat, 27 Jun 2015 22:13:51 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Z8yM1-0003Bn-Dw for freebsd-stable@freebsd.org; Sun, 28 Jun 2015 00:13:41 +0200 Received: from gly.ftfl.ca ([129.173.34.203]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 28 Jun 2015 00:13:41 +0200 Received: from jrm by gly.ftfl.ca with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 28 Jun 2015 00:13:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Joseph Mingrone Subject: Re: suspend/resume regression Date: Sat, 27 Jun 2015 19:13:35 -0300 Lines: 29 Message-ID: <86616894vk.fsf@gly.ftfl.ca> References: <86oak289hv.fsf@gly.ftfl.ca> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Complaints-To: usenet@ger.gmane.org Cc: Adrian Chadd X-Gmane-NNTP-Posting-Host: gly.ftfl.ca User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) Cancel-Lock: sha1:dXSIi43DOey3+ozm/vMPg5ynXwk= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2015 22:13:54 -0000 --=-=-= Content-Type: text/plain Adrian Chadd writes: > does it always fail now? Yes. The behaviour I described is, so far with 15-20 tries, consistent. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVjyAPAAoJEDakDIOw1u+eHsgP/2wzHuBY+HuLMgpcUdBcvrXS D+MagLEZH32yRpNkWNSiERR6DK8284BAH0wjqestLuVEUiwSUGh+DP7Rfk16vu4f EqwJejinRKyrahn7N32+EqfLJ/adGLS7l8cUyn6dnRbGhDjAmJRy0dNWggVamxl5 O5eBOGWqFg6k7yXfx6qZK/iDHm8H1A2Ce7h/TB8YSdSr9cgG9UgXz63qVK09ozL3 POGWilujEyMRICMIYPVZ2VHbDQXLlUyb+CRLxsE0SEsivR/Ofa/f4zKOKzLEzN32 VK5HXEUEStrGFVIoMkyqqPUlv754vOGT9leNY3rGDZnXkoqJ1KgQJRBBPriUwyyx Ofc4MjzUlLv0uH+3057Fg5w0pLpuQS7zDBGtk+piJW5+yIqGYV8xjsroHEH6npui lErRH6XOIx3eYhOuHwSkWALtHVlD4mzvHsrgIZ0k/Xum4lY730f5un2rSJIJgzoy ckyglZORHVX2eBChhGe5gTRkMvqIn27h+ay8+w04FmYBSJX6CNz+RiYTHWQikaJz oF5iP8qmHubkXfhhUwJkeETuRnp7k3sWZpsB8t2fS4X99alyF6LW/HImKiyD5TkL ViacGO8f5gFTG+GpMoOdL2rxGgzEdTKCQBkqmspn+ioN28rjoPBBoaHvFWdttcrz ytdejQ859UW8nFAGUa81 =9sLx -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-stable@freebsd.org Sat Jun 27 22:48:49 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 684A598E52C for ; Sat, 27 Jun 2015 22:48:49 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 384061903 for ; Sat, 27 Jun 2015 22:48:49 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oiyy130 with SMTP id y130so96767576oiy.0 for ; Sat, 27 Jun 2015 15:48:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=cylfXkiH8BNpvO5gH2tJUJ+Tl5J3lgmoV8NjYWYF5uw=; b=OCMrnp7F+EHyqqQQ0CQ57tgtQi7rllDeksuq1fTzr+u4rQlAYeUDeaJuXCCwDxuhti F1ya2qFKqCbOLR2TUTj3NhfwfEiWgdmwMHvaCdKMxB3PQqBnhaUsTSzLLjvOBpfpJYFQ B2qOjUXIFFRy9ufXEsCVIuOLLH/mhWcd39XszSdJNV+IFkQJ/GPH1Hbp+OIFXe+qvoiY AMnCYX/IljqCuxGgwsQVvezxjhM9cXtWewXu6pgarPp9MAPBmEwbHsZ3vWpbf57Qfu78 /ZQhV/wDy4hokl6ONxtCxd7BpicXPn2MxsRA2AX1p+PoKJsB0JigkFvUzZdx7+IT6f3d vuog== MIME-Version: 1.0 X-Received: by 10.182.240.228 with SMTP id wd4mr4887961obc.79.1435445328429; Sat, 27 Jun 2015 15:48:48 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Sat, 27 Jun 2015 15:48:48 -0700 (PDT) In-Reply-To: <86616894vk.fsf@gly.ftfl.ca> References: <86oak289hv.fsf@gly.ftfl.ca> <86616894vk.fsf@gly.ftfl.ca> Date: Sat, 27 Jun 2015 15:48:48 -0700 X-Google-Sender-Auth: fSmbCAK-9OMnOd9Nbkc4FsRP1YI Message-ID: Subject: Re: suspend/resume regression From: Kevin Oberman To: Joseph Mingrone Cc: FreeBSD-STABLE Mailing List , Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2015 22:48:49 -0000 On Sat, Jun 27, 2015 at 3:13 PM, Joseph Mingrone wrote: > Adrian Chadd writes: > > does it always fail now? > > Yes. The behaviour I described is, so far with 15-20 tries, consistent. > I confirm that I see the similar behavior on my T520 ThinkPad, Sandy Bridge system. FreeBSD rogue 10.2-PRERELEASE FreeBSD 10.2-PRERELEASE #1 r284698: Mon Jun 22 09:25:11 PDT 2015 root@rogue:/usr/obj/usr/src/sys/GENERIC amd64 It has been working flawlessly since Adrian's ACPI update. As of now, it suspends fine, but it won't resume. I get a fan spin-up, but the power LED continues to pulse, indicating it is suspended and the logs show nothing after the suspend. Shall I start a binary hunt for the culprit? It will likely take a few kernel builds as my last known working kernel was in late May. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-stable@freebsd.org Sat Jun 27 22:56:05 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D03DD98E6D3 for ; Sat, 27 Jun 2015 22:56:05 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9A4841E20 for ; Sat, 27 Jun 2015 22:56:05 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by iebmu5 with SMTP id mu5so95108200ieb.1 for ; Sat, 27 Jun 2015 15:56:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ftfl.ca; s=google; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=PmhzcIfRwpmj8Ls6o7FYM7BNxTaojjq2hkVuf3KItjY=; b=Rz2ylOPiZ0O8ti7m9M9sYam3/DfZ7TIutZfefNIxwOb1e2n+v5ObLl+juAgtABWr36 LIfJ3CM7YIsfUX90HfV25dHBxt7yLrSayuGOp8XumJSIK17CSRYZTDNWtd6j0Il1/S+8 RbFg2/zw8FTBQfaMUDjAh6wmfkh0DElUu5sFk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=PmhzcIfRwpmj8Ls6o7FYM7BNxTaojjq2hkVuf3KItjY=; b=ApHuo5cjLLexo/vkFl8Aaaa+Akh/GQJeZKk6WxD7qkwCs7GyJJ89ojuHw/v7Nv6X1s BfWGcoQ+g2uxukVI4OHzBQIPuhdQzjqq1wWE6jPzeIyol3u25Hd/lN4duOZXl/tsxNnW ysUmBEegAj2bRzqTv6Z8fpo4kEotItGbTKn6mbJdFN788iOP61ml6oqZigj8FkLktTiF fJccd5SydhatKnmH2iYKf1ftm3flqZbFsLHEjBX24nqeH1jlLYvMlHRnc3H2hLSch7J8 VnfSpkh8Vw5/ab7BIsIsopMvFNnhELFGbYqgmHd3RkgEEF32OgLRUxVuVNy4h2o20HeD Kciw== X-Gm-Message-State: ALoCoQnJ43c/vFJAt9ctrDORQzgIgLnA+cpYNI+ykGP0arQYQLpkcwuv172DoGkO8d3FwY1d8hw/ X-Received: by 10.50.102.68 with SMTP id fm4mr6203572igb.25.1435445764830; Sat, 27 Jun 2015 15:56:04 -0700 (PDT) Received: from gly.ftfl.ca.ftfl.ca (gly.ftfl.Ca. [129.173.34.203]) by mx.google.com with ESMTPSA id z6sm2034251ign.13.2015.06.27.15.56.02 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 27 Jun 2015 15:56:03 -0700 (PDT) From: Joseph Mingrone To: Kevin Oberman Cc: FreeBSD-STABLE Mailing List , Adrian Chadd Subject: Re: suspend/resume regression References: <86oak289hv.fsf@gly.ftfl.ca> <86616894vk.fsf@gly.ftfl.ca> Date: Sat, 27 Jun 2015 19:56:00 -0300 In-Reply-To: (Kevin Oberman's message of "Sat, 27 Jun 2015 15:48:48 -0700") Message-ID: <86oak07ocf.fsf@gly.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2015 22:56:06 -0000 --=-=-= Content-Type: text/plain Kevin Oberman writes: > On Sat, Jun 27, 2015 at 3:13 PM, Joseph Mingrone wrote: >> Adrian Chadd writes: >> > does it always fail now? >> Yes. The behaviour I described is, so far with 15-20 tries, consistent. > I confirm that I see the similar behavior on my T520 ThinkPad, Sandy Bridge > system. > FreeBSD rogue 10.2-PRERELEASE FreeBSD 10.2-PRERELEASE #1 r284698: Mon Jun > 22 09:25:11 PDT 2015 root@rogue:/usr/obj/usr/src/sys/GENERIC amd64 > It has been working flawlessly since Adrian's ACPI update. As of now, it > suspends fine, but it won't resume. I get a fan spin-up, but the power LED > continues to pulse, indicating it is suspended and the logs show nothing > after the suspend. > Shall I start a binary hunt for the culprit? It will likely take a few > kernel builds as my last known working kernel was in late May. > -- > Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 That sounds about right (when i915kms is loaded). Thanks for the update. I was trying r282199 from the end of April when a lot of stuff under /stable/10/sys/dev/drm2 got touched, but since you say it's working I'll move ahead to about two weeks ago. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVjyoAAAoJEDakDIOw1u+eZnkP/idnQGGbL2NmsoAwkYeHShcS Fz4aWwhtQVqv7uDvgPM+Si6zbPw8kx6GZImp2XeC/aoSkdBZlz6lYGO5fvsjTZFS y7gkSx8Paa13XbdlT/P6UDDCHTzstAnys/ak147cv7VAWnT/ZGbVQkayYvzJYfKp eXxhfHMxPxV/Dy3H6vCNxivlhLX1cRIoFhaefineSrxN362dcJ3DyMg8T6rt6IW5 BlwROOtukEpsdLaoh7kp/UKJX4LEfDCYmgMjppfDa6tuICabI+2c1SRDVGb/Sy/9 oL6Ms/ObYKFBCCwEdReB20EZ++upJmsUfyGLDT2+qOZB2yB5JmNR/MeG1NwWNqos 6x2J7TRE+cmNvf1NwhnMfYyqpf3XkEnMqLszdwk9vaG7dfqNvcjXpmtFLs7kMHw9 RPVGEZBOPlZTkklOsq3VgKzych1ElNBzyfPrxS6KQyDgBYwoFjlphnR1a6O4a0AJ xKFDpK5Qy+3fHZWCs5mcSJ1SY1g5U9ORp33O+6blgF2bUJUE1Cv1bbf2ayKNigcQ 3JRf37mHoTpslgDoM0BECEXI640MfQQDPDG6hTzAkXICqkG8uf5LbZ8b3JlNEohm GftFnH0G8wshhsAtD/h74812TcmxDYkel9BZMpvuIZrIQFgLbmK3jpfLgfSAiu+E Fd0NqoVnGpLGdOCdWPJ/ =QmZy -----END PGP SIGNATURE----- --=-=-=--