From owner-freebsd-stable@freebsd.org Sun Oct 28 06:53:10 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7294A10E9BC1 for ; Sun, 28 Oct 2018 06:53:10 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc11.plala.or.jp (msc11.plala.or.jp [60.36.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id 531C172C3B; Sun, 28 Oct 2018 06:53:08 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc11.plala.or.jp with ESMTP id <20181028064928.IPZW29305.msc11.plala.or.jp@localhost>; Sun, 28 Oct 2018 15:49:28 +0900 Date: Sun, 28 Oct 2018 15:49:23 +0900 (JST) Message-Id: <20181028.154923.772689078675954444.ish@amail.plala.or.jp> To: re@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available From: Masachika ISHIZUKA In-Reply-To: <20181027170348.GN61572@FreeBSD.org> References: <20181027170348.GN61572@FreeBSD.org> X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac11; Sun, 28 Oct 2018 15:49:28 +0900 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 28 Oct 2018 06:53:10 -0000 > === Upgrading === > [snip] > > The freebsd-update(8) utility supports binary upgrades of amd64 and i386 > systems running earlier FreeBSD releases. Systems running earlier > FreeBSD releases can upgrade as follows: > > # freebsd-update upgrade -r 12.0-BETA2 Hi. I want to binary upgrade to 12.0-BETA2 from 11.2-RELEASE-p4 as follow. # uname -a FreeBSD carrot.ish.org 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #0: Thu Sep 27 08:16:24 UTC 2018 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # freebsd-update upgrade -r 12.0-BETA2 Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 11.2-RELEASE from update4.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic kernel/generic-dbg src/src world/base world/lib32 The following components of FreeBSD do not seem to be installed: world/base-dbg world/doc world/lib32-dbg Does this look reasonable (y/n)? y Fetching metadata signature for 12.0-BETA2 from update4.freebsd.org... failed. Fetching metadata signature for 12.0-BETA2 from update1.freebsd.org... failed. No mirrors remaining, giving up. Where is the mirror server that has the 12.0-BETA2 amd64 binary patches ? -- Masachika ISHIZUKA From owner-freebsd-stable@freebsd.org Sun Oct 28 13:27:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A432010D0489 for ; Sun, 28 Oct 2018 13:27:55 +0000 (UTC) (envelope-from hokuriku@geo.or.jp) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 37AB08413D for ; Sun, 28 Oct 2018 13:27:55 +0000 (UTC) (envelope-from hokuriku@geo.or.jp) Received: by mailman.ysv.freebsd.org (Postfix) id F108210D0485; Sun, 28 Oct 2018 13:27:54 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6F7010D0484 for ; Sun, 28 Oct 2018 13:27:54 +0000 (UTC) (envelope-from hokuriku@geo.or.jp) Received: from sgmrmt102-fen.alpha-prm.jp (sgmrmt102-fen.alpha-prm.jp [157.205.202.200]) by mx1.freebsd.org (Postfix) with ESMTP id EB57D84137 for ; Sun, 28 Oct 2018 13:27:53 +0000 (UTC) (envelope-from hokuriku@geo.or.jp) Received: from sgmtsf02 ([157.205.230.82]) by sgmmta112.alpha-prm.jp with ESMTP id <20181028131727.DOUR3239.sgmmta112.alpha-prm.jp@sgmtsf02> for ; Sun, 28 Oct 2018 22:17:27 +0900 Received: from sgmiso03.alpha-prm.jp (sgmiso03-fen.alpha-prm.jp [157.205.230.99]) by sgmtsf02 (Postfix) with ESMTP id BAE2A3805B9 for ; Sun, 28 Oct 2018 22:17:27 +0900 (JST) Received: from sgmiso03.alpha-prm.jp (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id ACBCEB0041 for ; Sun, 28 Oct 2018 22:17:27 +0900 (JST) Received: from sgmiso03.alpha-prm.jp (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9C2BBB003C for ; Sun, 28 Oct 2018 22:17:27 +0900 (JST) Received: from sgmmxo13.alpha-prm.jp (unknown [157.205.201.41]) by sgmiso03.alpha-prm.jp (Postfix) with ESMTP for ; Sun, 28 Oct 2018 22:17:27 +0900 (JST) Received: from INT-VM ([66.23.226.146]) by sgmmxo13.alpha-prm.jp with ESMTP id <20181028131727.DYYP1729.sgmmxo13.alpha-prm.jp@INT-VM> for ; Sun, 28 Oct 2018 22:17:27 +0900 From: "James Kitula" Subject: NDI[VN]: JKT: Blsvn: JV Invite To: stable@FreeBSD.org MIME-Version: 1.0 Reply-To: jamkitula@outlook.com Date: Sun, 28 Oct 2018 09:17:33 -0400 Message-Id: <20181028131727.DYYP1729.sgmmxo13.alpha-prm.jp@INT-VM> X-TM-AS-GCONF: 00 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 28 Oct 2018 13:27:55 -0000 - This mail is in HTML. Some elements may be ommited in plain text. - Hello, This is a follow up of the message we previously sent to you.. We are international project financiers and we specialize in both star= t up projects and existing businesses needing funding or Loan for expa= nsion. We are committed to helping businesses develop and succeed. We will like to partner with you/your company should you be interested= or may require funding for the expansion of your business. We will be= glad to receiving your terms and condition before proceeding further. This is my personal email: jamkitula@outlook.com Looking forward to hear from you. Sincere regards, James Kitula. From owner-freebsd-stable@freebsd.org Sun Oct 28 13:51:21 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6449210D15E1; Sun, 28 Oct 2018 13:51:21 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 F334485174; Sun, 28 Oct 2018 13:51:20 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 7C3B5D3C; Sun, 28 Oct 2018 09:51:19 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 28 Oct 2018 09:51:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=to :from:subject:message-id:date:mime-version:content-type :content-transfer-encoding; s=fm3; bh=MTD4EfQ5gzUCaq1k6yUdOpP1v4 jovnvOMru3RedRMSM=; b=ixsVdjrn9AnN39yuoNrg9R60phHL6bhhzaubQoSKYY aiAldS8JA+NPmsFygN0pDaGAWqGJPTsJ6L1WWJFMPAQiOZcm/iL38tIOeLopnUQ1 uMdOiRPq47OcZGBSTEjfcbFgc/u/4++rU6/sv1PGYRz382+h9llmXVMUAEhLaHr0 A8yB4Kj4Uoj4moXGXHinPZH1Lhsz2MufDklcNpyDj7BY4ghUPw3g9yxrc5KWKkbY CnKyHWV+uNmAXgYEbBLTispSiQAX6nFREoqxNQts0H2ZMslhIZtomTSw6oGhV3pb 72lCHJDZ3PjzI4r/ki6bCkvKO9S8cFP/2bNg1/j9T8NA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=MTD4Ef Q5gzUCaq1k6yUdOpP1v4jovnvOMru3RedRMSM=; b=Zww7EyUP6Zd5f0fxVPSml9 fCV353viUkk55xwUkr5U8eUPZRLiPpw8JqXEFE88Zdg94NQiEKKDeHJxhEyr3YQH wM8frMxDgzL0HEu8YTUk/leTrccUx/KWzq06SX1m3P1H+MV5D1zuicB68iBnWzcJ /4rTG/WNL6OUH7v/PdAW1k254zoCoS0+yyvAwgQFHJ89JF01OxlucrtPx+hqmJRc 8G1FmqRelxsY2QWI7IcAuM24ocbBKMmOl7zMotIXJqFHiVn1LIwm8C1H+600s9nH /2aqruSazHfqvadJ3LXwrMpnibk/lCRaZV3MH/R48/v8my5fJi00H5/EjtcuKUNQ == X-ME-Sender: X-ME-Proxy: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 6B0B4102DD; Sun, 28 Oct 2018 09:51:18 -0400 (EDT) To: freebsd-doc@FreeBSD.org, "freebsd-stable@freebsd.org" From: tech-lists Subject: ioat(4) manual errors Organization: none Message-ID: Date: Sun, 28 Oct 2018 13:51:17 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 28 Oct 2018 13:51:21 -0000 Hi, man 4 ioat references ioatcontrol(8) in SEE ALSO but neither the manpage or executable for ioatcontrol exists. The man page also references /dev/ioat_test in the FILES section but that doesn't exist either. Context is FreeBSD 12.0-BETA2 #3 r339812 amd64 with GENERIC kernel ioat is loaded: [snip] > file /dev/ioat_test /dev/ioat_test: cannot open `/dev/ioat_test' (No such file or directory) > dmesg | grep ioat ioat0: mem 0xc7d1c000-0xc7d1ffff irq 31 at device 4.0 numa-domain 0 on pci0 ioat0: Capabilities: 2f7 ioat1: mem 0xc7d18000-0xc7d1bfff irq 39 at device 4.1 numa-domain 0 on pci0 ioat1: Capabilities: 2f7 ioat2: mem 0xc7d14000-0xc7d17fff irq 31 at device 4.2 numa-domain 0 on pci0 ioat2: Capabilities: f7 ioat3: mem 0xc7d10000-0xc7d13fff irq 39 at device 4.3 numa-domain 0 on pci0 ioat3: Capabilities: f7 ioat4: mem 0xc7d0c000-0xc7d0ffff irq 31 at device 4.4 numa-domain 0 on pci0 ioat4: Capabilities: f7 ioat5: mem 0xc7d08000-0xc7d0bfff irq 39 at device 4.5 numa-domain 0 on pci0 ioat5: Capabilities: f7 ioat6: mem 0xc7d04000-0xc7d07fff irq 31 at device 4.6 numa-domain 0 on pci0 ioat6: Capabilities: f7 ioat7: mem 0xc7d00000-0xc7d03fff irq 39 at device 4.7 numa-domain 0 on pci0 ioat7: Capabilities: f7 ioat8: mem 0xfbf1c000-0xfbf1ffff irq 55 at device 4.0 numa-domain 1 on pci9 ioat8: Capabilities: 2f7 ioat9: mem 0xfbf18000-0xfbf1bfff irq 63 at device 4.1 numa-domain 1 on pci9 ioat9: Capabilities: 2f7 ioat10: mem 0xfbf14000-0xfbf17fff irq 55 at device 4.2 numa-domain 1 on pci9 ioat10: Capabilities: f7 ioat11: mem 0xfbf10000-0xfbf13fff irq 63 at device 4.3 numa-domain 1 on pci9 ioat11: Capabilities: f7 ioat12: mem 0xfbf0c000-0xfbf0ffff irq 55 at device 4.4 numa-domain 1 on pci9 ioat12: Capabilities: f7 ioat13: mem 0xfbf08000-0xfbf0bfff irq 63 at device 4.5 numa-domain 1 on pci9 ioat13: Capabilities: f7 ioat14: mem 0xfbf04000-0xfbf07fff irq 55 at device 4.6 numa-domain 1 on pci9 ioat14: Capabilities: f7 ioat15: mem 0xfbf00000-0xfbf03fff irq 63 at device 4.7 numa-domain 1 on pci9 ioat15: Capabilities: f7 [/snip] thanks, -- J. From owner-freebsd-stable@freebsd.org Sun Oct 28 21:01:07 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB49A10E0A68 for ; Sun, 28 Oct 2018 21:01:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7CD866FDBD for ; Sun, 28 Oct 2018 21:01:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3E79310E0A64; Sun, 28 Oct 2018 21:01:07 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D6B410E0A61 for ; Sun, 28 Oct 2018 21:01:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7C706FDB4 for ; Sun, 28 Oct 2018 21:01:06 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E9E421FA9C for ; Sun, 28 Oct 2018 21:01:05 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9SL15xa093967 for ; Sun, 28 Oct 2018 21:01:05 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9SL15Hg093958 for stable@FreeBSD.org; Sun, 28 Oct 2018 21:01:05 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201810282101.w9SL15Hg093958@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: stable@FreeBSD.org Subject: Problem reports for stable@FreeBSD.org that need special attention Date: Sun, 28 Oct 2018 21:01:05 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 28 Oct 2018 21:01:08 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 230620 | "install -d" issue Open | 227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock 2 problems total for which you should take action. From owner-freebsd-stable@freebsd.org Mon Oct 29 07:59:36 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A552D1088CCB for ; Mon, 29 Oct 2018 07:59:36 +0000 (UTC) (envelope-from mnd999@gmail.com) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CFCF83A6A for ; Mon, 29 Oct 2018 07:59:36 +0000 (UTC) (envelope-from mnd999@gmail.com) Received: by mail-wr1-x42e.google.com with SMTP id g9-v6so7539243wrq.4 for ; Mon, 29 Oct 2018 00:59:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=Ba6QQsBReEMfpDtPveMWEKIcixX/IrxbskGMpmcqF7M=; b=qFCeKfaP7bpkTtAOZlXZs5lWBgy6WS+gGSUbJw55Qr9yMfgsDpSR2fNuUG2OJbjI+m 7arsaQbP8T+6K4IQRFxbE1FjCt/gb6Otbd8O0MZdvCBvlrtZO7N9GZ2M6jI/qCQbUvYi 423f2uYvPtVJYk0cFlSqNkMWYUIFBAjegpzAqznOZCQAFAcesx7veis0n2TSIw5B1OzT XtLsUl211gczvVuO08WQhktocSJk7+qIWRxt/qrYm0CJ9mZwyAsUC8fMwCqgeutGrueE ey0tDnuMbOGSZoDiedy1rNgyYnElAiAJ5bxuClRKxxZCnLBy9wTuxMj3cJS79bSaAB7j r+9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=Ba6QQsBReEMfpDtPveMWEKIcixX/IrxbskGMpmcqF7M=; b=jsAUtdhqRFZMbUk3L9Ur+OnGdo+aBxCmNVD09KCdLgHgzBUffCUdzGB0ETwg41PxTM hGvnmRhf4RVObb98TFkPdHJaVWhXAcSupo3ku1FpcqyPFV67Ha07+lA8fFe6XGOjSHBd LLaW8mktZvlJqc1nNuv7K7Saz2zMa3qLI6u06mhDczl9ErKX1djn6QIuKyweirw9K44d Y4z/qdU5KBCsAxKlbqRPtYd0WLJOw0DAXwdX1nUVQeap8HBxU+9TPDmNDwrXU+kyTIP/ t/tny4bZgYq9/w3JJUgGvIoCHI1bCZafRPIUISlb4PkinHgT15d2A5p3MEIAWC8p7xh6 4ISQ== X-Gm-Message-State: AGRZ1gJBr6T/uvjOWzKR+2MCrPB28muDkwqIzLfgfoLWMgLqS7xLexFM UMNudaKx3UjqRpkDZCcdiTbkJs0f X-Google-Smtp-Source: AJdET5fH1seeg4xfyTpnEV68PJ5lC68WxOVB/t1I7kSHTByXhEGxsla3WbW1nvrhpaVV+KJGWyG2QA== X-Received: by 2002:adf:afdc:: with SMTP id y28-v6mr14294559wrd.176.1540799974522; Mon, 29 Oct 2018 00:59:34 -0700 (PDT) Received: from markspc.local (d.0.5.a.4.f.f.8.e.6.2.e.3.8.8.c.2.a.6.7.3.a.d.0.0.b.8.0.1.0.0.2.ip6.arpa. [2001:8b0:da3:76a2:c883:e26e:8ff4:a50d]) by smtp.googlemail.com with ESMTPSA id y141-v6sm18591704wme.10.2018.10.29.00.59.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Oct 2018 00:59:33 -0700 (PDT) From: Mark Dixon X-Google-Original-From: Mark Dixon To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available Date: Mon, 29 Oct 2018 07:59:32 +0000 Message-ID: <16223295.sFgvYJuXru@markspc.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 07:59:37 -0000 Same, FreeBSD update doesn't seem to be working: $ sudo freebsd-update upgrade -r 12.0-BETA2 Mark From owner-freebsd-stable@freebsd.org Mon Oct 29 11:34:15 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C157510D4764 for ; Mon, 29 Oct 2018 11:34:15 +0000 (UTC) (envelope-from ardovm@yahoo.it) Received: from sonic311-21.consmr.mail.gq1.yahoo.com (sonic311-21.consmr.mail.gq1.yahoo.com [98.137.65.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3692F6CDAE for ; Mon, 29 Oct 2018 11:34:14 +0000 (UTC) (envelope-from ardovm@yahoo.it) X-YMail-OSG: trtLVHEVM1n.7C304Hp5cIzSkYR92JvjbCCkRPMdTeuX2xbmpmRGgnLzVUfzg23 nOW_h2NFHTUUKXBk9tRymIe2plBkXGwi.NruC6uwMSsZ9Zb7OVSCm4TZiJiL9ERuujzEZ1CsL8rc SlrocxcFCqWen6R7gc95dFFk5ahQGrfvxNFO6Q5nig34QST2UAYiWOXtYOUHHTrgjr4KDCZXkA7J pmE3nLq28bJXmsyjFbtq12H4zEMjxIov3HSfcX_g29s03tBYBPRvChlKxcRtdA7_ZRrCFGbmOI6O ZfXCRBAXeClOnruNxfPUyqyvx4gX6bEdGeAfF5dP5vbm5AL8lOk8OtvriqPDgU7YVXVglO1pk8aw SaqWDYO6bQz.vvnB.b5ptbchqrxNz84.p7lniTeWvBU7mrnCFhf6tBndJuGTrthN75jgT0WIwNex 6sIgn2Pe1J0muc7qENAqQ7tX6Etyuty_eNWfJPhgtYNHnHKL0fZBnXLPO0IA0Ieubxrbq0yxcNIp FjyD0s9eiaWw40XIleUYfwDARVEsM3alqJ8Kz2lTGkKtFySTiOH83d.A3ER6JXslmYu5lEq1jDtw GjmGhLnsdJXYDARjVc8FtRDDt6Wo5h7xGgim.X7ZE7GfaCZ67Rn7dEor2NL_p943vp6OWOnq20IO ZI9Hya2KYjbQMpEHhbLxqKj6LqFwk9olUbz10_.lrLmC_0MbZbHzNd4d.ksAoTel72OmDpnPU.d_ 13Ho0_E.4SWtdo_.UoZoVt0bcOfcWXhPL6v2SpUNB3qQcBSWvlinE9CHtUPYi4aDuP1rnIybn2o4 wslM3KiDCDgKIVZ4Ul4XNIpbSzL9BpnbpMiywyeNe.WChqBpT1r7TMW3WfwnfDFXiofrB5WcAe_G Q9.YeGL.5YACbyISWKisXJAIZYVQFsIo9j1gMeIpg8h7HuABZHJi9jKwoVmgM0JM.JhrrQNGPmk1 3cq47A0waQAohqMPwi59WY16h134W3xNuCv3tlpAwtkAF_EToQUwemetvtJVKDDg9oNSkFGCnw9I ACl1y Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Mon, 29 Oct 2018 11:34:07 +0000 Received: from 104.219.53.199 (EHLO nuvolo.localdomain) ([104.219.53.199]) by smtp409.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 543d7a8ce78ff167faa981a2d8778f8b for ; Mon, 29 Oct 2018 11:23:56 +0000 (UTC) Received: by nuvolo.localdomain (Postfix, from userid 1001) id 20D5A112E34; Mon, 29 Oct 2018 12:23:55 +0100 (CET) Date: Mon, 29 Oct 2018 12:23:55 +0100 From: Arrigo Marchiori To: freebsd-stable@freebsd.org Subject: Kernel modules and updates (problems with graphics/drm-stable-kmod) Message-ID: <20181029112355.GA3887@nuvolo> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 11:34:15 -0000 Dear All, I am encountering a strange problem with port graphics/drm-stable-kmod. My system is a 11.2-STABLE amd64 with GENERIC kernel. I upgrade the base system every week or two from source. My /etc/make.conf lists graphics/drm-stable-kmod in PORTS_MODULES, in order to have it recompiled with every kernel. When I install the new kernel, run mergemaster and reboot, however, Xorg is unable to drive the video card: something goes wrong with DRM and he tty belonging to Xorg remains black. The other tty's work well. I tracked down the problem to the file /boot/kernel/radeonkms.ko ^^^^^^ If I delete that file and reboot, Xorg works fine. My question is: why is that file there? The port graphics/drm-stable-kmod installs its module in /boot/modules/radeonkms.ko but the other version from /boot/kernel/ ^^^^^^^ ^^^^^^ seems to be loaded instead, and therefore Xorg does not work. Is this a bug of either installkernel, or the port? Or am I doing anything wrong? Thank you in advance, -- rigo http://rigo.altervista.org From owner-freebsd-stable@freebsd.org Mon Oct 29 12:19:28 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5523010D66E4 for ; Mon, 29 Oct 2018 12:19:28 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 DD4206EB00 for ; Mon, 29 Oct 2018 12:19:27 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 42kDDS0mN4zDhxn; Mon, 29 Oct 2018 12:19:20 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id A7GIzp8tzuao; Mon, 29 Oct 2018 12:19:19 +0000 (UTC) Received: from garnet.daemonic.se (host-95-192-226-92.mobileonline.telia.com [95.192.226.92]) by mail.daemonic.se (Postfix) with ESMTPSA id 42kDDR0PzFzDhFd; Mon, 29 Oct 2018 12:19:18 +0000 (UTC) Subject: Re: Kernel modules and updates (problems with graphics/drm-stable-kmod) To: Arrigo Marchiori , freebsd-stable@freebsd.org References: <20181029112355.GA3887@nuvolo> From: Niclas Zeising Message-ID: <47be1338-40fa-ec15-0c97-4655ee39ab12@freebsd.org> Date: Mon, 29 Oct 2018 13:19:18 +0100 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <20181029112355.GA3887@nuvolo> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 12:19:28 -0000 On 10/29/18 12:23 PM, Arrigo Marchiori via freebsd-stable wrote: > Dear All, > > I am encountering a strange problem with port graphics/drm-stable-kmod. > My system is a 11.2-STABLE amd64 with GENERIC kernel. > > I upgrade the base system every week or two from source. My > /etc/make.conf lists graphics/drm-stable-kmod in PORTS_MODULES, in > order to have it recompiled with every kernel. > > When I install the new kernel, run mergemaster and reboot, however, > Xorg is unable to drive the video card: something goes wrong with DRM > and he tty belonging to Xorg remains black. The other tty's work > well. > > I tracked down the problem to the file /boot/kernel/radeonkms.ko > ^^^^^^ > If I delete that file and reboot, Xorg works fine. > > My question is: why is that file there? The port > graphics/drm-stable-kmod installs its module in > /boot/modules/radeonkms.ko but the other version from /boot/kernel/ > ^^^^^^^ ^^^^^^ > seems to be loaded instead, and therefore Xorg does not work. > > Is this a bug of either installkernel, or the port? Or am I doing > anything wrong? > > Thank you in advance, > Hi! /boot/kernel/radeonkms.ko is part of the old drm driver that is in base on 11.2 and 12. In order to load the module from drm-stable-kmod you need to specify the whole path, /boot/modules/radeonkms.ko when loading the module. Regards -- Niclas Zeising From owner-freebsd-stable@freebsd.org Mon Oct 29 12:34:51 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6D3A10D6C88 for ; Mon, 29 Oct 2018 12:34:51 +0000 (UTC) (envelope-from SRS0=eyDw=NJ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 4A1426F2B4 for ; Mon, 29 Oct 2018 12:34:51 +0000 (UTC) (envelope-from SRS0=eyDw=NJ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 23EF128423 for ; Mon, 29 Oct 2018 13:34:42 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id C8D0628417 for ; Mon, 29 Oct 2018 13:34:40 +0100 (CET) To: freebsd-stable@freebsd.org From: Miroslav Lachman <000.fbsd@quip.cz> Subject: sync command runs for hours after upgrade to 11.2 Message-ID: <21a79514-0ada-83bd-bd4a-77fb838042fe@quip.cz> Date: Mon, 29 Oct 2018 13:34:40 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 12:34:51 -0000 I upgraded about 10 machines from 10.4 to 11.2 this month. The last machines were upgrade few days ago and one of them exhibits strange behaviour with sync(8) command. We have sync in one script for MRTG which is called each 5 minutes. Every day between 8 - 15h the sync calls are not finished in few seconds (or fraction of second) as usual but they run for hours and cannot be killed. # ps auxww | grep sync mrtg 22897 23.9 0.0 4232 2048 - R 09:20 69:30.86 sync mrtg 22186 23.8 0.0 4232 2048 - R 09:15 72:14.36 sync mrtg 29535 23.2 0.0 4232 2048 - R 10:05 48:05.80 sync mrtg 46040 22.5 0.0 4232 2048 - R 11:25 22:24.87 sync mrtg 59472 22.4 0.0 4232 2048 - R 12:40 4:30.85 sync mrtg 25683 22.2 0.0 4232 2048 - R 09:40 59:20.61 sync mrtg 51972 22.1 0.0 4232 2048 - R 12:05 12:19.05 sync mrtg 27983 22.0 0.0 4232 2048 - R 09:55 52:25.62 sync mrtg 6534 21.8 0.0 4232 2048 - R 08:00 126:28.14 sync mrtg 49674 21.7 0.0 4232 2048 - R 11:50 15:57.96 sync mrtg 58720 21.6 0.0 4232 2048 - R 12:35 5:33.81 sync mrtg 7419 21.5 0.0 4232 2048 - R 08:05 122:03.06 sync mrtg 16371 21.5 0.0 4232 2048 - R 08:50 88:07.14 sync mrtg 26454 21.5 0.0 4232 2048 - R 09:45 56:50.32 sync mrtg 36149 21.5 0.0 4232 2048 - R 10:35 37:25.89 sync mrtg 37607 21.5 0.0 4232 2048 - R 10:45 34:19.37 sync mrtg 6588 21.3 0.0 4232 2048 - R 08:00 126:31.50 sync mrtg 30283 21.1 0.0 4232 2048 - R 10:10 46:04.96 sync mrtg 11030 21.0 0.0 4232 2048 - R 08:15 114:01.56 sync mrtg 52724 21.0 0.0 4232 2048 - R 12:10 11:07.51 sync mrtg 61965 21.0 0.0 4232 2048 - R 12:55 1:23.08 sync mrtg 35360 20.9 0.0 4232 2048 - R 10:30 38:59.89 sync mrtg 40764 20.9 0.0 4232 2048 - R 11:05 27:59.73 sync mrtg 28855 20.8 0.0 4232 2048 - R 10:00 50:07.67 sync mrtg 33199 20.8 0.0 4232 2048 - R 10:15 44:08.61 sync mrtg 57984 20.8 0.0 4232 2048 - R 12:30 6:39.88 sync mrtg 17866 20.7 0.0 4232 2048 - R 09:00 81:18.44 sync mrtg 57226 20.7 0.0 4232 2048 - R 12:25 7:49.24 sync mrtg 34610 20.6 0.0 4232 2048 - R 10:25 40:34.89 sync mrtg 27242 20.5 0.0 4232 2048 - R 09:50 54:37.43 sync mrtg 8180 20.4 0.0 4232 2048 - R 08:10 117:47.97 sync mrtg 12422 20.4 0.0 4232 2048 - R 08:25 106:02.85 sync mrtg 17071 20.4 0.0 4232 2048 - R 08:55 84:41.97 sync mrtg 48920 20.4 0.0 4232 2048 - R 11:45 17:14.73 sync mrtg 23521 20.3 0.0 4232 2048 - R 09:25 66:46.53 sync mrtg 39911 20.3 0.0 4232 2048 - R 11:00 29:28.89 sync mrtg 56437 20.2 0.0 4232 2048 - R 12:20 8:56.43 sync mrtg 61234 20.2 0.0 4232 2048 - R 12:50 2:23.54 sync mrtg 14981 20.1 0.0 4232 2048 - R 08:40 95:00.02 sync mrtg 46832 20.1 0.0 4232 2048 - R 11:30 21:03.80 sync mrtg 50447 20.1 0.0 4232 2048 - R 11:55 14:42.42 sync mrtg 51273 20.1 0.0 4232 2048 - R 12:00 13:33.55 sync mrtg 14088 20.0 0.0 4232 2048 - R 08:35 98:16.55 sync mrtg 39126 20.0 0.0 4232 2048 - R 10:55 31:12.26 sync mrtg 62764 20.0 0.0 4232 2048 - R 13:00 0:21.80 sync mrtg 15716 19.9 0.0 4232 2048 - R 08:45 91:27.30 sync mrtg 55646 19.9 0.0 4232 2048 - R 12:15 10:03.76 sync mrtg 33863 19.7 0.0 4232 2048 - R 10:20 42:24.80 sync mrtg 48174 19.6 0.0 4232 2048 - R 11:40 18:29.01 sync mrtg 24297 19.5 0.0 4232 2048 - R 09:30 64:03.59 sync mrtg 44522 19.5 0.0 4232 2048 - R 11:15 25:02.50 sync root 61355 19.5 0.0 4232 2048 2 R+ 12:51 2:06.40 sync mrtg 38358 19.4 0.0 4232 2048 - R 10:50 32:39.67 sync mrtg 36847 19.1 0.0 4232 2048 - R 10:40 35:44.49 sync mrtg 45339 19.1 0.0 4232 2048 - R 11:20 23:45.21 sync mrtg 60318 19.1 0.0 4232 2048 - R 12:45 3:27.70 sync mrtg 13200 18.8 0.0 4232 2048 - R 08:30 102:11.46 sync mrtg 18627 18.8 0.0 4232 2048 - R 09:05 78:06.64 sync mrtg 41498 18.8 0.0 4232 2048 - R 11:10 26:30.43 sync mrtg 47563 18.8 0.0 4232 2048 - R 11:35 19:42.28 sync mrtg 11700 18.5 0.0 4232 2048 - R 08:20 110:05.39 sync mrtg 19368 18.3 0.0 4232 2048 - R 09:10 75:03.78 sync mrtg 25043 18.0 0.0 4232 2048 - R 09:35 61:45.86 sync The same script is used on each of our servers without any problem. This machine is running Apache and PHP without any problems. Web is still responding even if the system load is about 60: last pid: 59734; load averages: 61.76, 59.62, 57.24 up 2+12:33:30 12:42:31 387 processes: 64 running, 318 sleeping, 5 zombie CPU: 14.1% user, 0.0% nice, 85.7% system, 0.1% interrupt, 0.1% idle Mem: 1006M Active, 9907M Inact, 9056M Laundry, 2703M Wired, 1405M Buf, 1224M Free Swap: 16G Total, 63M Used, 16G Free The one thing that can be of some coincidence is rsync backup which is running in the time between 6 - 17h. Can anybody help where should I look to solve this problem? # uname -srmi FreeBSD 11.2-RELEASE-p4 amd64 GENERIC /dev/mirror/gm0root on / (ufs, local, noatime) /dev/mirror/gm0usr on /usr (ufs, local, noatime, soft-updates) /dev/mirror/gm0var on /var (ufs, local, noatime, nosuid, soft-updates) /dev/mirror/gm0tmp on /tmp (ufs, local, noatime, noexec, nosuid, soft-updates) /dev/mirror/gm0vol0 on /vol0 (ufs, local, noatime, noexec, nosuid, soft-updates) /dev/mirror/gm0vol1 on /vol1 (ufs, local, noatime, noexec, nosuid, soft-updates) No ZFS involved. Kind regards Miroslav Lachman From owner-freebsd-stable@freebsd.org Mon Oct 29 12:45:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CFDD10D72FD for ; Mon, 29 Oct 2018 12:45:52 +0000 (UTC) (envelope-from ardovm@yahoo.it) Received: from sonic314-19.consmr.mail.gq1.yahoo.com (sonic314-19.consmr.mail.gq1.yahoo.com [98.137.69.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB1656FB3E for ; Mon, 29 Oct 2018 12:45:51 +0000 (UTC) (envelope-from ardovm@yahoo.it) X-YMail-OSG: ppj7CsoVM1ntbvPns8xfL0MePT1eeLCX0Te938vBut9wUIhDB6PFMkxjp1.h5em ke84vhmQqKIGA_S8oF8Ejt8q_98ThSAL50YO_Y2PSfPVyJB9t2JtmtqfoTTtSK_bCezG7FBEYl0i vA9_le2SbGhXeoiEUjbbS3oVHGHDRuELqZRNv1c1NbQ9P_WU9J4_PCVxpFfmAXJGAbZyDnb3K6Pc sqK.yJOB0hkBafxwhVEWCSaNABEZz_4rWkuIfnDLU9.5gVTYnveDYjMFarKZFRPT.agWYqHSMgoD 1cQ4kfbWlCI6IxVWMlqdsb18Z235ZEk0q9RuRahB1TAWUuTa05bFqPHZoTAGv4zCBkXqqTtyrHeb yB6JxMnq9tiHzecUzEX4Mdabw1l6DIvDEs4IYtr0tA_FF44nYnkzXy.lzHV5KOJ3fa6eVJoOB3Kh ABAvh38x5uOcam8XuS0Oox3r8NBdJYNYjYnYqThRLkiCQvFHGytdlSOZkbaoHAOuUGiRYIexUsVq Im72LttKNeGn9yVpn0MyX0GxcMqzayvy3Umk4YudRMG6VISYku073s1V6pEnrMguMu8pKp5SzCdJ T2CfVCYQ_NOyT_OnzNXsKYsd4ctpQGVQFDe3C0ZL_KZHK1.g_Gl3jR01QPeWyzFqhRH2rSV7pvh. zUIfKb_3L7w06LRfjwidsSqU3FRk64.kNoCWT0v2uOQw2HWVl28twN4NET8dHa66TGgwavA_rHmV 4fkocX_lPc_zhNNxT3vwbBQOp0eS1uXrXjwgPJGmBhcOTWruNlR0bQ01TLtAJBsXjJi83kTiMu2W Wc2J57gyy.1aDZ9ly8FV45vFpVIpaIerWF3K7hruxrCjI6SoQc5JF8_jXyKQAdsvgJK3RRQjp57r FMOCPfwddrwpzZ9qLp_tUIliFGjng4W5oGfECot4.p9jjGd0jNMYHJec3cJ50S2TSkbWrTJ3LoTm PUCK1CCREzO4FYH1EaclCNVpad6oTGifAkAPrPZxBoxxVrl1OXl32AQSLSY9whiunpAfjZUT0qii XhyummcTbq3PHsJSg6QXJ Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.gq1.yahoo.com with HTTP; Mon, 29 Oct 2018 12:45:50 +0000 Received: from 104.219.53.199 (EHLO nuvolo.localdomain) ([104.219.53.199]) by smtp410.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 397a6ccfe2253a3d51ca49696a0ee92d; Mon, 29 Oct 2018 12:35:40 +0000 (UTC) Received: by nuvolo.localdomain (Postfix, from userid 1001) id 15D01112E34; Mon, 29 Oct 2018 13:35:39 +0100 (CET) Date: Mon, 29 Oct 2018 13:35:39 +0100 From: Arrigo Marchiori To: Niclas Zeising Cc: freebsd-stable@freebsd.org Subject: Re: Kernel modules and updates (problems with graphics/drm-stable-kmod) Message-ID: <20181029123539.GB3887@nuvolo> References: <20181029112355.GA3887@nuvolo> <47be1338-40fa-ec15-0c97-4655ee39ab12@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <47be1338-40fa-ec15-0c97-4655ee39ab12@freebsd.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 12:45:52 -0000 Hello Niclas, On Mon, Oct 29, 2018 at 01:19:18PM +0100, Niclas Zeising wrote: > On 10/29/18 12:23 PM, Arrigo Marchiori via freebsd-stable wrote: > > Dear All, > > > > I am encountering a strange problem with port graphics/drm-stable-kmod. > > My system is a 11.2-STABLE amd64 with GENERIC kernel. > > > > I upgrade the base system every week or two from source. My > > /etc/make.conf lists graphics/drm-stable-kmod in PORTS_MODULES, in > > order to have it recompiled with every kernel. > > > > When I install the new kernel, run mergemaster and reboot, however, > > Xorg is unable to drive the video card: something goes wrong with DRM > > and he tty belonging to Xorg remains black. The other tty's work > > well. > > > > I tracked down the problem to the file /boot/kernel/radeonkms.ko > > ^^^^^^ > > If I delete that file and reboot, Xorg works fine. > > > > My question is: why is that file there? The port > > graphics/drm-stable-kmod installs its module in > > /boot/modules/radeonkms.ko but the other version from /boot/kernel/ > > ^^^^^^^ ^^^^^^ > > seems to be loaded instead, and therefore Xorg does not work. > > > > Is this a bug of either installkernel, or the port? Or am I doing > > anything wrong? > > > > Thank you in advance, > > > > Hi! > /boot/kernel/radeonkms.ko is part of the old drm driver that is in base > on 11.2 and 12. In order to load the module from drm-stable-kmod you > need to specify the whole path, /boot/modules/radeonkms.ko when loading > the module. > Regards Thank you for your reply. I should have read more carefully the pkg-message from graphics/drm-stable-kmod ! Best regards, -- rigo http://rigo.altervista.org From owner-freebsd-stable@freebsd.org Mon Oct 29 13:25:03 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACD1B10D7F8B for ; Mon, 29 Oct 2018 13:25:03 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [46.251.251.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "0x20.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4671970F05 for ; Mon, 29 Oct 2018 13:25:03 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from e.0x20.net (mail.0x20.net [46.251.251.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id B1AF39D94F; Mon, 29 Oct 2018 14:24:55 +0100 (CET) Received: (from lars@localhost) by e.0x20.net (8.15.2/8.15.2/Submit) id w9TDOt13095457; Mon, 29 Oct 2018 14:24:55 +0100 (CET) (envelope-from lars) Date: Mon, 29 Oct 2018 14:24:55 +0100 From: Lars Engels To: Mark Dixon Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available Message-ID: <20181029132455.GI98934@e.0x20.net> References: <16223295.sFgvYJuXru@markspc.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <16223295.sFgvYJuXru@markspc.local> X-Editor: VIM - Vi IMproved 8.0 User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 13:25:03 -0000 On Mon, Oct 29, 2018 at 07:59:32AM +0000, Mark Dixon wrote: > Same, FreeBSD update doesn't seem to be working: > > $ sudo freebsd-update upgrade -r 12.0-BETA2 IIRC freebsd-update only works for RCs, not ALPHA and BETA versions. From owner-freebsd-stable@freebsd.org Mon Oct 29 13:41:07 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C130210DA195 for ; Mon, 29 Oct 2018 13:41:07 +0000 (UTC) (envelope-from mnd999@gmail.com) Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FE77719D4 for ; Mon, 29 Oct 2018 13:41:07 +0000 (UTC) (envelope-from mnd999@gmail.com) Received: by mail-it1-x12f.google.com with SMTP id f16-v6so1962389ita.3 for ; Mon, 29 Oct 2018 06:41:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IqYI2VwnBF84ims2qdLPH8toLNjRBOLyuezgSRnZwQ0=; b=k2CNRRq4SQHLTDu+4oVAkyH3d/wkkYZkqCtPVdpvJ4jPK6WfgU6UjTEoA3wkHIymqF /aQHsjisCv0wY8eFP7rGb8QfGhHRidLjsYH+vMBIg2FHWWlzjOuLD4NEiOH0h0d5AIHV l8NCCL81Vg/peRr8e3CKHKXlK388gO4ffdJwTjN63+SfK4cAX5yIMgYwtM5hpSpTbywj /aN61/YPPkuFwul2uW8QrpjKChccgTPWmmf8BEdIe3HAPaxgiZqGOLuyVXzMMKich72I clde13m1KbA1Q0Px/1KErT27i1tFIrjA38xZkH+RcdHxh96ZKKu8EaVt6QABdTcfSWcd Amtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IqYI2VwnBF84ims2qdLPH8toLNjRBOLyuezgSRnZwQ0=; b=p3kSx7o0ZGps3xO2Vw2nkMX9Q6d2ax09GsfvWQs2OO4lNOxPLrMuFhnrP2KSxBKbJY RiW7y8Tv7NNn9iepAbb/hAxW8WtELFxNOwaeAoFz42/DiMaZLxcDmoeGzjByXLNalAju EbW7zhBjA19STanC5fgSxGhsLL4aAZ1pbgqizw3riAb+YNZmtnrxQ7XGjWfl+NOVj21i uxrI4Q5EXIIcmelSKy8QFWuyNRDyeITJ/IojA1IVdf/0rwawIEsZPVmS5uGtaR3+3k4p I77Sz+Nyu4jp/SRJwwgG5idqbm6FaUHuGEoGB1ht/8bjUt8KXEGoK8p/cK3VpPohRXj0 DkMQ== X-Gm-Message-State: AGRZ1gLm9CsmGhVRcwNzUJtlW3wKiqG472PR4R9TKgzUuympPKt4EQiC tvJL5CEtSOWHHL3Q5jEmCf5IyHGSumTtKbHWzibmRQ== X-Google-Smtp-Source: AJdET5ckvf+63ZeUj5ZViffii56ScolzQ1sDNtKnyRGqXcTIBU5ifJO44GAcoKgJVyyRGzwCOJiPr3TJAye7QAgk6Cg= X-Received: by 2002:a02:9bfb:: with SMTP id f56-v6mr9986341jal.67.1540820465656; Mon, 29 Oct 2018 06:41:05 -0700 (PDT) MIME-Version: 1.0 References: <16223295.sFgvYJuXru@markspc.local> <20181029132455.GI98934@e.0x20.net> In-Reply-To: <20181029132455.GI98934@e.0x20.net> From: Mark Dixon Date: Mon, 29 Oct 2018 13:40:54 +0000 Message-ID: Subject: Re: FreeBSD 12.0-BETA2 Now Available To: lars.engels@0x20.net Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 13:41:08 -0000 On Mon, 29 Oct 2018 at 13:24, Lars Engels wrote: > On Mon, Oct 29, 2018 at 07:59:32AM +0000, Mark Dixon wrote: > > Same, FreeBSD update doesn't seem to be working: > > > > $ sudo freebsd-update upgrade -r 12.0-BETA2 > > IIRC freebsd-update only works for RCs, not ALPHA and BETA versions. > The release notes for the beta (this thread) provide instructions for it, and it certain has done for previous releases. If this has changed, the instructions should be removed from the release notes. Mark From owner-freebsd-stable@freebsd.org Mon Oct 29 15:09:25 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F33BC10DCCCD for ; Mon, 29 Oct 2018 15:09:24 +0000 (UTC) (envelope-from rleigh@codelibre.net) Received: from a-painless.mh.aa.net.uk (a-painless.mh.aa.net.uk [81.187.30.51]) (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 94F6774C54 for ; Mon, 29 Oct 2018 15:09:24 +0000 (UTC) (envelope-from rleigh@codelibre.net) Received: from 9.c.0.5.8.a.e.f.f.f.e.5.5.d.2.e.d.b.d.d.0.6.8.0.0.b.8.0.1.0.0.2.ip6.arpa ([2001:8b0:860:ddbd:e2d5:5eff:fea8:50c9]) by a-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1gH9AR-0004w5-P2 for freebsd-stable@freebsd.org; Mon, 29 Oct 2018 15:09:23 +0000 Subject: Re: FreeBSD 12.0-BETA2 Now Available To: freebsd-stable@freebsd.org References: <16223295.sFgvYJuXru@markspc.local> <20181029132455.GI98934@e.0x20.net> From: Roger Leigh Message-ID: <68e4423a-218a-2912-2fe2-f834c7124f6f@codelibre.net> Date: Mon, 29 Oct 2018 15:09:14 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 15:09:25 -0000 On 29/10/2018 13:40, Mark Dixon wrote: > On Mon, 29 Oct 2018 at 13:24, Lars Engels wrote: > >> On Mon, Oct 29, 2018 at 07:59:32AM +0000, Mark Dixon wrote: >>> Same, FreeBSD update doesn't seem to be working: >>> >>> $ sudo freebsd-update upgrade -r 12.0-BETA2 >> >> IIRC freebsd-update only works for RCs, not ALPHA and BETA versions. >> > > The release notes for the beta (this thread) provide instructions for it, > and it certain has done for previous releases. If this has changed, the > instructions should be removed from the release notes. I've likewise tried and failed to follow these instructions. Assuming that it is supported, will it be possible to upgrade from BETA2 to RCs and then the final RELEASE? Thanks, Roger From owner-freebsd-stable@freebsd.org Mon Oct 29 16:04:43 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DACE410DE592 for ; Mon, 29 Oct 2018 16:04:43 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc11.plala.or.jp (msc11.plala.or.jp [60.36.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id D20E676A35; Mon, 29 Oct 2018 16:04:42 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::5]) by msc11.plala.or.jp with ESMTP id <20181029160431.JZXT29305.msc11.plala.or.jp@localhost>; Tue, 30 Oct 2018 01:04:31 +0900 Date: Tue, 30 Oct 2018 01:04:24 +0900 (JST) Message-Id: <20181030.010424.17654226369780713.ish@amail.plala.or.jp> To: freebsd-stable@freebsd.org Cc: re@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available From: Masachika ISHIZUKA In-Reply-To: <68e4423a-218a-2912-2fe2-f834c7124f6f@codelibre.net> References: <20181029132455.GI98934@e.0x20.net> <68e4423a-218a-2912-2fe2-f834c7124f6f@codelibre.net> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac11; Tue, 30 Oct 2018 01:04:31 +0900 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 16:04:44 -0000 > Assuming that it is supported, will it be possible to upgrade from > BETA2 to RCs and then the final RELEASE? I think so. Indeed, older releases were not upgradable from betas, but recent releases were upgradable from beta releases. Although it said that we could not upgrade to 12.0-BETA1 in the previous release note, we can upgrade to 12.0-BETA1 by freebsd-update. And at this moment, we cannot upgrade to 12.0-BETA2 by freebsd-update. -- Masachika ISHIZUKA From owner-freebsd-stable@freebsd.org Mon Oct 29 16:07:58 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CC8510DE759 for ; Mon, 29 Oct 2018 16:07:58 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C10A176C89; Mon, 29 Oct 2018 16:07:57 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 6B07618B17; Mon, 29 Oct 2018 16:07:57 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Mon, 29 Oct 2018 16:07:55 +0000 From: Glen Barber To: Masachika ISHIZUKA Cc: freebsd-stable@freebsd.org, re@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available Message-ID: <20181029160755.GQ75350@FreeBSD.org> References: <20181029132455.GI98934@e.0x20.net> <68e4423a-218a-2912-2fe2-f834c7124f6f@codelibre.net> <20181030.010424.17654226369780713.ish@amail.plala.or.jp> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Liytj72NTuI9Pzy1" Content-Disposition: inline In-Reply-To: <20181030.010424.17654226369780713.ish@amail.plala.or.jp> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 16:07:58 -0000 --Liytj72NTuI9Pzy1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 30, 2018 at 01:04:24AM +0900, Masachika ISHIZUKA wrote: > > Assuming that it is supported, will it be possible to upgrade from > > BETA2 to RCs and then the final RELEASE? >=20 > I think so. >=20 Yes. > Indeed, older releases were not upgradable from betas, but > recent releases were upgradable from beta releases. >=20 > Although it said that we could not upgrade to 12.0-BETA1 in > the previous release note, we can upgrade to 12.0-BETA1 by > freebsd-update. > And at this moment, we cannot upgrade to 12.0-BETA2 by > freebsd-update. Sorry, I forgot to reply to your original report. This is being looked into. It is, unfortunately, more fallout from updating OpenSSL to version 1.1.1. Glen --Liytj72NTuI9Pzy1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlvXMFsACgkQAxRYpUeP 4pOb4w//T+owJ7La2RhmTCxAm4MZ7fwT0dKOcMw5iTQG3KPkMuegISvHX4wNVxEO vWJWgucJp9qLc30WGXtWcNnD0nQvKB7SGk4H6cuAN1XY2ZXiTyBLjB3DXgENtHOk gHdGMKyu0V1YepwsRgINdavqRpAKP4vNlBHazyFrMTDo/ET+a2Pz+28t4DQrlbVu dKFqZhTix4BeZhwRFe4PMicsDY9pKOoBxMu4hthx4rGElu5hmMcjGaNclo2Ja0nP mEpe0upoEVcGfy0fx47DCSam/0N+GpQTRGtjdhXEEEpR1uglHEEi0YkK3Wfpturb fuO54zaig5eyX/T3eVq73mcDlIkkVpzrEloLZz7IIx3JqiIWaDCVlEWMp7ONWhWN hHuMnmMFI73cU4iqMOjd1epcfVWjtGjyFoN1A19grJ9uUpuST+yH/6+pshB+SVxY UCBWDF7YOIrboWcwyfdv96a9u9SOvoXusUVD1jBoa4GWyUVUErt33uOeH3cbSyIP aiSAqo/HI4RwGmcLmsQFmgQy9VW+wldmsTTxZsupn4Dt/O7A+UOS+cy7XRj5lEYX YdAxpeOch6cDLvipCb2cd0u2t1DYIrAPo2d0Rp4HQVcvnUuLkZd8+7m1HQm7LC/B CeSZXGo8W/hLkx1wey22FXvU+qYxacgSodR7P7+Z8AGqauo2UhE= =Suyq -----END PGP SIGNATURE----- --Liytj72NTuI9Pzy1-- From owner-freebsd-stable@freebsd.org Mon Oct 29 21:13:54 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22FBD10EA63B for ; Mon, 29 Oct 2018 21:13:54 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-it1-x12c.google.com (mail-it1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A744E83B64; Mon, 29 Oct 2018 21:13:53 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by mail-it1-x12c.google.com with SMTP id f16-v6so3803199ita.3; Mon, 29 Oct 2018 14:13:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/sJfP0tVLuEQVXc+MJMwSS4NUdQKygF/sC501Bn+00k=; b=g3uDryA0gNeQ/yFjzz8ZB6W5119Fsb84N5c02lBeKNydPznw1z1k24lVvA3XhBrNzj bo7wjSdY1KFQi0b25gKwWagEUi5AizXKafcggXoa6d6dLBF9hsCZ+2RE9MODnIovKRoo 28dFOvvks6rp6O+rU2wbyH2ZwztJwWfsohLTHBODNdcHb693n+UYkw9w9ekUmyrAI6fx aSLFzEiPb4Y8MyM02D+p5Y512whu5QLWdP876IPYOY4XeeeQo0NFoBVEmSb2PMneAmRw TnPvycPihbgxQlraD1OblQ95K1e3vTyMn590vSY6CnxftVsmirLYMJa3rsxSxIpRXUxw 6sNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/sJfP0tVLuEQVXc+MJMwSS4NUdQKygF/sC501Bn+00k=; b=Ky+2/jzaMW7hFg1qbAtfUbRCTpTTmc6JgvQVJOnRpsWhu0mMGpjQ/w9RGpmvMAz71M 83OYDvVygKII5Xdo/wpjD+LjkYPcqDCFeakol3sGDl9m0rziRxkkiHeJQW/UWAu4ZEFs 0ma8+fRRTjQxC13erMrM6LEa9IKPxxYkoxeysbaeqdtJeqGKkJ4a8bVxcFZ7vnsJNaZ4 s6zguFNiz3FO34DTcAtZrDUIXldh858rjoLh9PRVERuQ0RDfgkIeUujAB4S6aRsX/uKf C4UMwynNs8H7dk6Huz1i407w5CZl8IWy2rmvSRotuoTkoBCbChBdUCRsAZJbL61t34bR 6XCw== X-Gm-Message-State: AGRZ1gImsO/lC4/LY89E5C2tFB4hoQxH8ZcatZ0eo+fie6GjfN/VnnqY lgaKWOHQshUxSYVJvkBgLNTYAz6/W54UHtmr+PNp8g== X-Google-Smtp-Source: AJdET5dvSr1yajRhYnojnsl/koK/nFj6Sn7p3BTcQx1OG4zH57qtQbOa/vHNhXokZs6kNtxVvwDNwdOM9i/ofRKdnls= X-Received: by 2002:a24:35d7:: with SMTP id k206-v6mr5589046ita.102.1540847632463; Mon, 29 Oct 2018 14:13:52 -0700 (PDT) MIME-Version: 1.0 References: <20181029112355.GA3887@nuvolo> <47be1338-40fa-ec15-0c97-4655ee39ab12@freebsd.org> In-Reply-To: <47be1338-40fa-ec15-0c97-4655ee39ab12@freebsd.org> From: Matthew Macy Date: Mon, 29 Oct 2018 14:13:41 -0700 Message-ID: Subject: Re: Kernel modules and updates (problems with graphics/drm-stable-kmod) To: Niclas Zeising Cc: Arrigo Marchiori , Warner Losh , freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 29 Oct 2018 21:13:54 -0000 On Mon, Oct 29, 2018 at 05:20 Niclas Zeising wrote: > On 10/29/18 12:23 PM, Arrigo Marchiori via freebsd-stable wrote: > > Dear All, > > > > I am encountering a strange problem with port graphics/drm-stable-kmod. > > My system is a 11.2-STABLE amd64 with GENERIC kernel. > > > > I upgrade the base system every week or two from source. My > > /etc/make.conf lists graphics/drm-stable-kmod in PORTS_MODULES, in > > order to have it recompiled with every kernel. > > > > When I install the new kernel, run mergemaster and reboot, however, > > Xorg is unable to drive the video card: something goes wrong with DRM > > and he tty belonging to Xorg remains black. The other tty's work > > well. > > > > I tracked down the problem to the file /boot/kernel/radeonkms.ko > > ^^^^^^ > > If I delete that file and reboot, Xorg works fine. > > > > My question is: why is that file there? The port > > graphics/drm-stable-kmod installs its module in > > /boot/modules/radeonkms.ko but the other version from /boot/kernel/ > > ^^^^^^^ ^^^^^^ > > seems to be loaded instead, and therefore Xorg does not work. > > > > Is this a bug of either installkernel, or the port? Or am I doing > > anything wrong? > > > > Thank you in advance, > > > > Hi! > /boot/kernel/radeonkms.ko is part of the old drm driver that is in base > on 11.2 and 12. In order to load the module from drm-stable-kmod you > need to specify the whole path, /boot/modules/radeonkms.ko when loading > the module. > Regards > -- > Niclas Zeising > __ This is why there was an effort to move the drivers from base in 12 and they have now been marked deprecated. Niclas - I=E2=80=99ve lost track of the work that=E2=80=99s been done there= - is this error not possible on 12? Thanks. _____________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Tue Oct 30 09:47:12 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BF7110DD29B for ; Tue, 30 Oct 2018 09:47:12 +0000 (UTC) (envelope-from ciunas.bennett@intel.com) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga104.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F2D97A7B7 for ; Tue, 30 Oct 2018 09:47:11 +0000 (UTC) (envelope-from ciunas.bennett@intel.com) X-Amp-Result: CLEAN X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Oct 2018 02:47:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,444,1534834800"; d="xml'?bin'?scan'72,48,208?xlsx'72,48,208,72,48?rels'72,48,208,72,48"; a="99939186" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by fmsmga002.fm.intel.com with ESMTP; 30 Oct 2018 02:47:00 -0700 Received: from irsmsx112.ger.corp.intel.com (10.108.20.5) by IRSMSX108.ger.corp.intel.com (163.33.3.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 30 Oct 2018 09:47:00 +0000 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.144]) by irsmsx112.ger.corp.intel.com ([169.254.1.93]) with mapi id 14.03.0415.000; Tue, 30 Oct 2018 09:46:59 +0000 From: "Bennett, Ciunas" To: Konstantin Belousov CC: "freebsd-stable@freebsd.org" Subject: RE: Possible memory leak in the kernel (contigmalloc) Thread-Topic: Possible memory leak in the kernel (contigmalloc) Thread-Index: AdRrtbzKvvQI2iPZToSPdiaEvmHIXQBqhpgAALREjJA= Date: Tue, 30 Oct 2018 09:46:59 +0000 Message-ID: <770FD3608C9E864796AB46CB37B561B1BE0B4096@irsmsx105.ger.corp.intel.com> References: <770FD3608C9E864796AB46CB37B561B1BDFCF0CD@IRSMSX101.ger.corp.intel.com> <20181026201230.GV5335@kib.kiev.ua> In-Reply-To: <20181026201230.GV5335@kib.kiev.ua> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMmE5ZWI5ZWEtMzEyZi00ZTQzLWFkOGMtZGU2ZDA5NGY3NTg3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiQkU5RG5kRThxeUcxRjJTTG05cG9oMlpMTktrRUFtK1wvS0RPY0xpMjZUZkh2eEwzQTkzazk3TmcxQnlWMjdpNUIifQ== x-originating-ip: [163.33.239.182] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 09:47:12 -0000 Hi, I was debugging the issue by viewing the free ques "sysctl vm.phys_free" an= d also using "show page" in ddb. The inactive memory is never being released back into the free que. = I thought that when inactive memory reaches a certain threshold that the ke= rnel will start reclaiming and move it to the free list? In my program this is not happening, the program uses free memory (contigma= lloc), and then it is put into the inactive que (contiigfree) when the prog= ram frees it. This inactive memory is never released by the kernel, and the inactive que = grows until all the memory is in this que. I have attached a xml sheet that shows the memory usage in the system. Ciunas. -----Original Message----- From: Konstantin Belousov [mailto:kostikbel@gmail.com] = Sent: Friday, October 26, 2018 9:13 PM To: Bennett, Ciunas Cc: freebsd-stable@freebsd.org Subject: Re: Possible memory leak in the kernel (contigmalloc) On Wed, Oct 24, 2018 at 04:27:52PM +0000, Bennett, Ciunas wrote: > Hello, > = > I have encountered an issue with a kernel application that I have = > written, the issue might be caused by a memory leak in the kernel. > The application allocates and deallocates contiguous memory using > contigmalloc() and contigfree(). The application will fail after a = > period of time because there is not enough free contiguous memory = > left. There could be an issue with the freeing of memory when using = > the contigfree() function. > It is unlikely that there is an issue with a leak, but I would be not surpr= ised if your allocation/free pattern would cause fragmentation on free list= s that results in contigmalloc(9) failures after. Look at the vmstat -z/vmstat -m output to see uma and malloc stats. More interesting for your case can be the output from sysctl vm.phys_free which provides information about the free queues and order of free pages on= them. -------------------------------------------------------------- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the s= ole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact = the sender and delete all copies. From owner-freebsd-stable@freebsd.org Tue Oct 30 10:12:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CF2210DE3E1 for ; Tue, 30 Oct 2018 10:12:02 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 06EFB7BA90 for ; Tue, 30 Oct 2018 10:12:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w9UABoeU037275 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Oct 2018 12:11:53 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w9UABoeU037275 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w9UABopc037274; Tue, 30 Oct 2018 12:11:50 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 30 Oct 2018 12:11:50 +0200 From: Konstantin Belousov To: "Bennett, Ciunas" Cc: "freebsd-stable@freebsd.org" Subject: Re: Possible memory leak in the kernel (contigmalloc) Message-ID: <20181030101150.GN5335@kib.kiev.ua> References: <770FD3608C9E864796AB46CB37B561B1BDFCF0CD@IRSMSX101.ger.corp.intel.com> <20181026201230.GV5335@kib.kiev.ua> <770FD3608C9E864796AB46CB37B561B1BE0B4096@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <770FD3608C9E864796AB46CB37B561B1BE0B4096@irsmsx105.ger.corp.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 10:12:02 -0000 On Tue, Oct 30, 2018 at 09:46:59AM +0000, Bennett, Ciunas wrote: > Hi, > > I was debugging the issue by viewing the free ques "sysctl > vm.phys_free" and also using "show page" in ddb. The inactive memory > is never being released back into the free que. I thought that when > inactive memory reaches a certain threshold that the kernel will start > reclaiming and move it to the free list? In my program this is not > happening, the program uses free memory (contigmalloc), and then it > is put into the inactive que (contiigfree) when the program frees it. Contigfree() does not release memory into inactive queue. By definition, inactive pages have valid content, which is not possible for the pages freed by contigfree(). contigfree()->kmem_free()->kmem_unback()->vm_page_free(). > This inactive memory is never released by the kernel, and the inactive > que grows until all the memory is in this que. I have attached a xml > sheet that shows the memory usage in the system. Inactive memory is not freed, it makes no sense as far as there is valid content, which is either not recoverable (anon memory or dirty file pages) or high-cost to restore (clean file pages, need to re-read from disk). Inactive is processed by pagedaemon when system has memory deficit, and either inactive pages are written to swap, or written to their file backing storage. I suspect that you have other activities on your system going on, which cause creation of the inactive memory and unrecoverable fragmentation. Note that contigmalloc() tries to do defragmentation to satisfy requests, but this is not always possible. > Ciunas. > > -----Original Message----- > From: Konstantin Belousov [mailto:kostikbel@gmail.com] > Sent: Friday, October 26, 2018 9:13 PM > To: Bennett, Ciunas > Cc: freebsd-stable@freebsd.org > Subject: Re: Possible memory leak in the kernel (contigmalloc) > > On Wed, Oct 24, 2018 at 04:27:52PM +0000, Bennett, Ciunas wrote: > > Hello, > > > > I have encountered an issue with a kernel application that I have > > written, the issue might be caused by a memory leak in the kernel. > > The application allocates and deallocates contiguous memory using > > contigmalloc() and contigfree(). The application will fail after a > > period of time because there is not enough free contiguous memory > > left. There could be an issue with the freeing of memory when using > > the contigfree() function. > > > > It is unlikely that there is an issue with a leak, but I would be not surprised if your allocation/free pattern would cause fragmentation on free lists that results in contigmalloc(9) failures after. > > Look at the vmstat -z/vmstat -m output to see uma and malloc stats. > More interesting for your case can be the output from > sysctl vm.phys_free > which provides information about the free queues and order of free pages on them. > -------------------------------------------------------------- > Intel Research and Development Ireland Limited > Registered in Ireland > Registered Office: Collinstown Industrial Park, Leixlip, County Kildare > Registered Number: 308263 > > > This e-mail and any attachments may contain confidential material for the sole > use of the intended recipient(s). Any review or distribution by others is > strictly prohibited. If you are not the intended recipient, please contact the > sender and delete all copies. From owner-freebsd-stable@freebsd.org Tue Oct 30 11:17:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FDB010DFE4A for ; Tue, 30 Oct 2018 11:17:02 +0000 (UTC) (envelope-from ciunas.bennett@intel.com) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orsmga106.jf.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7921F7DEA7 for ; Tue, 30 Oct 2018 11:17:01 +0000 (UTC) (envelope-from ciunas.bennett@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Oct 2018 04:15:49 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,444,1534834800"; d="scan'208";a="92355724" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by FMSMGA003.fm.intel.com with ESMTP; 30 Oct 2018 04:15:49 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.144]) by IRSMSX101.ger.corp.intel.com ([169.254.1.134]) with mapi id 14.03.0415.000; Tue, 30 Oct 2018 11:15:48 +0000 From: "Bennett, Ciunas" To: Konstantin Belousov CC: "freebsd-stable@freebsd.org" Subject: RE: Possible memory leak in the kernel (contigmalloc) Thread-Topic: Possible memory leak in the kernel (contigmalloc) Thread-Index: AdRrtbzKvvQI2iPZToSPdiaEvmHIXQBqhpgAALREjJAAAgPuAAABiKNg Date: Tue, 30 Oct 2018 11:15:47 +0000 Message-ID: <770FD3608C9E864796AB46CB37B561B1BE0B5562@irsmsx105.ger.corp.intel.com> References: <770FD3608C9E864796AB46CB37B561B1BDFCF0CD@IRSMSX101.ger.corp.intel.com> <20181026201230.GV5335@kib.kiev.ua> <770FD3608C9E864796AB46CB37B561B1BE0B4096@irsmsx105.ger.corp.intel.com> <20181030101150.GN5335@kib.kiev.ua> In-Reply-To: <20181030101150.GN5335@kib.kiev.ua> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzE3YThmNzQtNzc5OC00ZjljLTkzN2EtNDM3ODYyMmRmMWI0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoidDVJdW1YbllmMmxyaHFZZWJvN2tcLzUwRTgrTm5ZTmVDV0VEXC9OVGdDWlRIMzRod3JncFF6QkMrSDByVGdJNHhsIn0= x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 11:17:02 -0000 Hi, The only other activity that is running is the csh script that is insertin= g and removing the kernel module. I am not using the VM for any other purpose but to run this test. In my tests the correlation between memory allocation and moving to inactiv= e list can be seen. I don't think any other process is creating the inactive memory. Thanks. -----Original Message----- From: Konstantin Belousov [mailto:kostikbel@gmail.com] = Sent: Tuesday, October 30, 2018 10:12 AM To: Bennett, Ciunas Cc: freebsd-stable@freebsd.org Subject: Re: Possible memory leak in the kernel (contigmalloc) On Tue, Oct 30, 2018 at 09:46:59AM +0000, Bennett, Ciunas wrote: > Hi, > = > I was debugging the issue by viewing the free ques "sysctl = > vm.phys_free" and also using "show page" in ddb. The inactive memory = > is never being released back into the free que. I thought that when = > inactive memory reaches a certain threshold that the kernel will start = > reclaiming and move it to the free list? In my program this is not = > happening, the program uses free memory (contigmalloc), and then it is = > put into the inactive que (contiigfree) when the program frees it. Contigfree() does not release memory into inactive queue. By definition, i= nactive pages have valid content, which is not possible for the pages freed= by contigfree(). contigfree()->kmem_free()->kmem_unback()->vm_page_free(). > This inactive memory is never released by the kernel, and the inactive = > que grows until all the memory is in this que. I have attached a xml = > sheet that shows the memory usage in the system. Inactive memory is not freed, it makes no sense as far as there is valid co= ntent, which is either not recoverable (anon memory or dirty file pages) or high-cost to restore (clean file pages, need to re-read from disk= ). Inactive is processed by pagedaemon when system has memory deficit, and= either inactive pages are written to swap, or written to their file backin= g storage. I suspect that you have other activities on your system going on, which cau= se creation of the inactive memory and unrecoverable fragmentation. Note that contigmalloc() tries to do defragmentation to satisfy requests, b= ut this is not always possible. > Ciunas. > = > -----Original Message----- > From: Konstantin Belousov [mailto:kostikbel@gmail.com] > Sent: Friday, October 26, 2018 9:13 PM > To: Bennett, Ciunas > Cc: freebsd-stable@freebsd.org > Subject: Re: Possible memory leak in the kernel (contigmalloc) > = > On Wed, Oct 24, 2018 at 04:27:52PM +0000, Bennett, Ciunas wrote: > > Hello, > > = > > I have encountered an issue with a kernel application that I have = > > written, the issue might be caused by a memory leak in the kernel. > > The application allocates and deallocates contiguous memory using > > contigmalloc() and contigfree(). The application will fail after a = > > period of time because there is not enough free contiguous memory = > > left. There could be an issue with the freeing of memory when using = > > the contigfree() function. > > > = > It is unlikely that there is an issue with a leak, but I would be not sur= prised if your allocation/free pattern would cause fragmentation on free li= sts that results in contigmalloc(9) failures after. > = > Look at the vmstat -z/vmstat -m output to see uma and malloc stats. > More interesting for your case can be the output from > sysctl vm.phys_free > which provides information about the free queues and order of free pages = on them. > -------------------------------------------------------------- > Intel Research and Development Ireland Limited Registered in Ireland = > Registered Office: Collinstown Industrial Park, Leixlip, County = > Kildare Registered Number: 308263 > = > = > This e-mail and any attachments may contain confidential material for = > the sole use of the intended recipient(s). Any review or distribution = > by others is strictly prohibited. If you are not the intended = > recipient, please contact the sender and delete all copies. -------------------------------------------------------------- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the s= ole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact = the sender and delete all copies. From owner-freebsd-stable@freebsd.org Tue Oct 30 14:59:26 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FAB710EAD15 for ; Tue, 30 Oct 2018 14:59:26 +0000 (UTC) (envelope-from daisy.williams@distinctive-web-search.com) Received: from server2.pam.lflink.com (server2.pam.lflink.com [80.211.3.230]) (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 EA29D6A014 for ; Tue, 30 Oct 2018 14:59:25 +0000 (UTC) (envelope-from daisy.williams@distinctive-web-search.com) Received: from WS72 (unknown [223.190.93.20]) by server2.pam.lflink.com (Postfix) with ESMTPA id BDEA672FD for ; Tue, 30 Oct 2018 09:32:37 -0400 (EDT) From: "Daisy Williams" To: Subject: Improve the web presence of your business Date: Tue, 30 Oct 2018 18:52:01 +0530 Message-ID: <1b9901d47055$080121d0$18036570$@distinctive-web-search.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdRwJYuAoK0tk9P1Sfepg4Hyn0CInw== Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 14:59:26 -0000 Greetings, Let's work together! We are a trusted digital marketing agency for more than 10 years, our team of 200+ marketing gurus has served over 4000 clients. Our unique "Pay-for-performance" model attracts customers from all geographies of the world, and we are proud to cater to the needs of every type of business belonging to varied industries, scales, and regions. We do "Performance Based Marketing" service, Pay only when we rank your keywords on Top searches. - FREE website analysis report - No monthly fee / No contractual payout - Dedicated 24*7 support - Only one time set up fee Our results 'Talk' Get your website evaluated NOW, Just reply to this email with your contact details along with your requirement and we will call you back. Thanks & Regards, Daisy Williams Marketing Manager Head Office: San Jose, CA 95120 Disclaimer: We are using this domain for marketing. If you are interested and want to know about us, just reply to this email, if we have offended you by sending this to you by mistake, we apologize. Please reply "NO" or "UNSUBSCRIBE" to this email if not interested, so that we shall add you to our "Do Not Contact Again" list. From owner-freebsd-stable@freebsd.org Tue Oct 30 18:36:08 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B85C910F0E4C for ; Tue, 30 Oct 2018 18:36:08 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 412CF73A53 for ; Tue, 30 Oct 2018 18:36:08 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w9UIZvWC053948 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Oct 2018 20:36:00 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w9UIZvWC053948 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w9UIZvbF053947; Tue, 30 Oct 2018 20:35:57 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 30 Oct 2018 20:35:57 +0200 From: Konstantin Belousov To: "Bennett, Ciunas" Cc: "freebsd-stable@freebsd.org" Subject: Re: Possible memory leak in the kernel (contigmalloc) Message-ID: <20181030183557.GP5335@kib.kiev.ua> References: <770FD3608C9E864796AB46CB37B561B1BDFCF0CD@IRSMSX101.ger.corp.intel.com> <20181026201230.GV5335@kib.kiev.ua> <770FD3608C9E864796AB46CB37B561B1BE0B4096@irsmsx105.ger.corp.intel.com> <20181030101150.GN5335@kib.kiev.ua> <770FD3608C9E864796AB46CB37B561B1BE0B5562@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <770FD3608C9E864796AB46CB37B561B1BE0B5562@irsmsx105.ger.corp.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 18:36:09 -0000 On Tue, Oct 30, 2018 at 11:15:47AM +0000, Bennett, Ciunas wrote: > Hi, > The only other activity that is running is the csh script that is inserting and removing the kernel module. > I am not using the VM for any other purpose but to run this test. > In my tests the correlation between memory allocation and moving to inactive list can be seen. > I don't think any other process is creating the inactive memory. But it is created. More, since anon private memory is freed (not deactivated) on the process exit, something is accumulating the memory. The other possibility is that the memory is the caching pages from vnodes, but for this buffers must be created and then reclaimed, which would suggest even more activity on the system. > Thanks. > > -----Original Message----- > From: Konstantin Belousov [mailto:kostikbel@gmail.com] > Sent: Tuesday, October 30, 2018 10:12 AM > To: Bennett, Ciunas > Cc: freebsd-stable@freebsd.org > Subject: Re: Possible memory leak in the kernel (contigmalloc) > > On Tue, Oct 30, 2018 at 09:46:59AM +0000, Bennett, Ciunas wrote: > > Hi, > > > > I was debugging the issue by viewing the free ques "sysctl > > vm.phys_free" and also using "show page" in ddb. The inactive memory > > is never being released back into the free que. I thought that when > > inactive memory reaches a certain threshold that the kernel will start > > reclaiming and move it to the free list? In my program this is not > > happening, the program uses free memory (contigmalloc), and then it is > > put into the inactive que (contiigfree) when the program frees it. > Contigfree() does not release memory into inactive queue. By definition, inactive pages have valid content, which is not possible for the pages freed by contigfree(). > contigfree()->kmem_free()->kmem_unback()->vm_page_free(). > > > > This inactive memory is never released by the kernel, and the inactive > > que grows until all the memory is in this que. I have attached a xml > > sheet that shows the memory usage in the system. > Inactive memory is not freed, it makes no sense as far as there is valid content, which is either not recoverable (anon memory or dirty file > pages) or high-cost to restore (clean file pages, need to re-read from disk). Inactive is processed by pagedaemon when system has memory deficit, and either inactive pages are written to swap, or written to their file backing storage. > > I suspect that you have other activities on your system going on, which cause creation of the inactive memory and unrecoverable fragmentation. > Note that contigmalloc() tries to do defragmentation to satisfy requests, but this is not always possible. > > > > Ciunas. > > > > -----Original Message----- > > From: Konstantin Belousov [mailto:kostikbel@gmail.com] > > Sent: Friday, October 26, 2018 9:13 PM > > To: Bennett, Ciunas > > Cc: freebsd-stable@freebsd.org > > Subject: Re: Possible memory leak in the kernel (contigmalloc) > > > > On Wed, Oct 24, 2018 at 04:27:52PM +0000, Bennett, Ciunas wrote: > > > Hello, > > > > > > I have encountered an issue with a kernel application that I have > > > written, the issue might be caused by a memory leak in the kernel. > > > The application allocates and deallocates contiguous memory using > > > contigmalloc() and contigfree(). The application will fail after a > > > period of time because there is not enough free contiguous memory > > > left. There could be an issue with the freeing of memory when using > > > the contigfree() function. > > > > > > > It is unlikely that there is an issue with a leak, but I would be not surprised if your allocation/free pattern would cause fragmentation on free lists that results in contigmalloc(9) failures after. > > > > Look at the vmstat -z/vmstat -m output to see uma and malloc stats. > > More interesting for your case can be the output from > > sysctl vm.phys_free > > which provides information about the free queues and order of free pages on them. > > -------------------------------------------------------------- > > Intel Research and Development Ireland Limited Registered in Ireland > > Registered Office: Collinstown Industrial Park, Leixlip, County > > Kildare Registered Number: 308263 > > > > > > This e-mail and any attachments may contain confidential material for > > the sole use of the intended recipient(s). Any review or distribution > > by others is strictly prohibited. If you are not the intended > > recipient, please contact the sender and delete all copies. > > > -------------------------------------------------------------- > Intel Research and Development Ireland Limited > Registered in Ireland > Registered Office: Collinstown Industrial Park, Leixlip, County Kildare > Registered Number: 308263 > > > This e-mail and any attachments may contain confidential material for the sole > use of the intended recipient(s). Any review or distribution by others is > strictly prohibited. If you are not the intended recipient, please contact the > sender and delete all copies. > From owner-freebsd-stable@freebsd.org Tue Oct 30 18:37:14 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B11710F0E8A for ; Tue, 30 Oct 2018 18:37:14 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id C009D73AEC for ; Tue, 30 Oct 2018 18:37:13 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 3948ACA4 for ; Tue, 30 Oct 2018 21:37:07 +0300 (MSK) To: freebsd-stable@freebsd.org Reply-To: lev@FreeBSD.org From: Lev Serebryakov Subject: How to boot from GPT partition without "bootme" attribute? Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: <0c51f6ec-4190-18eb-6e67-e364509bf6c8@FreeBSD.org> Date: Tue, 30 Oct 2018 21:37:00 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XhoGJ28K9tYvrSGLwBscC0iGNr40nWmFL" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 18:37:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XhoGJ28K9tYvrSGLwBscC0iGNr40nWmFL Content-Type: multipart/mixed; boundary="QqVMaYedQ37ZEwTzoSUaoLQrb3UsCN3pS"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: freebsd-stable@freebsd.org Message-ID: <0c51f6ec-4190-18eb-6e67-e364509bf6c8@FreeBSD.org> Subject: How to boot from GPT partition without "bootme" attribute? --QqVMaYedQ37ZEwTzoSUaoLQrb3UsCN3pS Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable I have disk with GPT scheme and three partitions: p1 - freebsd-boot p2 - freebsd-ufs p3 - freebsd-ufs pmbr is installed on this disk, and gptboot is installed on p1. Both p2 and p3 contains valid FreeBSD installation, with /boot/loader, kernel, and everything. I have attribute "bootme" set on p3, but not on p2. What should I do to boot from p2? I've tried to interrupt gptboot and override its choice: 0:ad(0p3)/boot/loader with 0:ad(0p2)/boot/loader After that loader, loaded from p2, loads kernel from p3 and boots system from p3! If I have MBR, I could override "active" slice in boot0 MBR loader interactively. Is it analogous feature for GPT? --=20 // Lev Serebryakov --QqVMaYedQ37ZEwTzoSUaoLQrb3UsCN3pS-- --XhoGJ28K9tYvrSGLwBscC0iGNr40nWmFL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlvYpM1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R490iBAApdAYxJultYh4m41HLD0ZwO2wAWIIOzetDogOixVBB/zs1LARX6dXqo7D iyFWtWK4xPBhf7nzZe4wegyMgKzA5AjkcYZ1GuDOaEzI8u9YUMXpJfsliuoSWSlq 7FL6wzKUKZK6it4X11wgJFRfNF0yPm7Pwy3lB2BWcgQ1u8C/K3diF4mseO0rE6Nl aFebyUU9dOrF5xyFGUjd49DGylC7fgevjZdwPQsxBdLIJRktrTfKpNlLvk+UY+Ad cQE+xShjkgc9GS/SgrHfI+SGQZGJLXwxoJ+rg/fHwtYaOiwoUh9rO58015I6nAGS 6FV8KqmBQC79xrEuaJCav70KwTSQbygKWI6xpMp5v2EVU5CYpKRiZ8mGX0rykcGK MdIgAH+Y9bHZUW9/KNmthHsr83O8hjJHqxcU2Aw1qXt5tX0OfTUHxKqvCHT6UAeS 9KIxHU7peTvRxYo16Ctxr0sb5g7UR5LBV0mbsrRz5B3VZSfta9GSW/9eH7DJ2v/u nQvHMWbmRZ7QaUxkroRPpPkJ4UCm5NhzKRowkTTWJLR/wZxDpTP4kvZhuKHQmop0 YQU5hnU/Yn1rLlJnm5zTCKvwuzsdBbadn34au7+2Ki55BFXJ6lPyhLhH40a+jhu/ OwncBkLbT/gaIPHMDiR3lm1A6zK88gS+sdAaMlCwU/xHimDjpes= =pbMR -----END PGP SIGNATURE----- --XhoGJ28K9tYvrSGLwBscC0iGNr40nWmFL-- From owner-freebsd-stable@freebsd.org Tue Oct 30 21:38:12 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23C1210F593E for ; Tue, 30 Oct 2018 21:38:12 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-35.consmr.mail.ne1.yahoo.com (sonic317-35.consmr.mail.ne1.yahoo.com [66.163.184.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B59F17BE3E for ; Tue, 30 Oct 2018 21:38:11 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 1nN8K0YVM1mHl6EkHobwYqiMbvGWY9jd8iOS.ODGN._TJy.iWXByzDuY890dd9f 566kQJF0I9qhKFvXEC.YW5HKIvnln4EngFkfiFxS0nJfM4IfvAKrqgWiuJlxWmDXx.Cmm7TicTUt 90.yvpOjPcBKlclmKgdeDU1VmhOAJ6ZRgJt.NdG3aD9JShAngbgnVouEnc9hY__A6ire949X0HI0 Q71BRJWKkwMx1hfMy7lwrwXgKD5ssVYxb8aEqF2VCkG2zV21uY8uAf6z_WYKUdPtbAjBQOG235BR 4ibksINdlLetnvEsO4FqISthevdaXB_UtmWoLrugVTwmsC5V2oE0gA7.Y6cqxG02gl5NVPSsZVgr HhLXTj_Cdd4LZ5NaDgAUtomzxAM8ptzBcdcO_dqc9Bly3sYI8ddqy64HONgqtVbe7BuMzQJeujvq xInqJweazO5vty6SLSGDq_M8naeHeBRE60ETsWj.q1PUT.xBKXmLwv3mS2IHhOT_NGcrCkeSr0j_ Pn72BpJ7Yt0tWzHTAYQMoSJF7tPkpK_ZOoTFrtWybsDtbXeIKZbnjxMOJRWCuWoSGQsPF4yfKd8G qNNgj795DgPHRnixstxT.1jT_CzxZ5wURiJHBBxXMpiUMftvUWdgVFszLUJfl68GMWDjAOdq3TUg 5cKS45TQPeF4SmVZ33DEinLUHA2l8e9BeEFZwJrvDsK9IOKdm6ZjI8cIeI8Gb1wCHz5wLex7asZZ IXBxx3jMm7OWpY54fGsOMhepDGHSZq.961.MCu.B34B_MWOVPt5xwkLyw.bnria1OdgL7zfXjUjz z6iHrsqT1xzeB4sIs3l3.UK09I248uVW9rwG2pgxh6y87iOffaZI9QXt6W7L49SOrFDVBTXHAAhe Igzi5a8t4WNhx5EUDWhcFnZDkq9l47GCi9YYVVjEbcyu9USgwA6uTOMQbm5MtnyuygR46rPoh1S0 V2OsMYSgiMr07zX0ux7ZFLfB_985F_vBVd4lvOeJeWlZ8_qr0w2BUkt_nqccV2AhFW.GmRr94tM9 wT9_iw_OVx_fwCuDseMPiYotlIYpN2AN4pxB1U4nRJ15z6A-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.ne1.yahoo.com with HTTP; Tue, 30 Oct 2018 21:38:10 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp421.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 10bafcd5dbef4b676b2eac7cb176b7a2; Tue, 30 Oct 2018 21:38:08 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: How to boot from GPT partition without "bootme" attribute? Message-Id: Date: Tue, 30 Oct 2018 14:38:07 -0700 To: Lev Serebryakov , FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 21:38:12 -0000 Lev Serebryakov lev at FreeBSD.org wrote on Tue Oct 30 18:37:14 UTC 2018 : > I have disk with GPT scheme and three partitions: > > p1 - freebsd-boot > p2 - freebsd-ufs > p3 - freebsd-ufs > > pmbr is installed on this disk, and gptboot is installed on p1. Both p2 > and p3 contains valid FreeBSD installation, with /boot/loader, kernel, > and everything. > > I have attribute "bootme" set on p3, but not on p2. > > What should I do to boot from p2? > > I've tried to interrupt gptboot and override its choice: > > 0:ad(0p3)/boot/loader > > with > > 0:ad(0p2)/boot/loader > > After that loader, loaded from p2, loads kernel from p3 and boots > system from p3! Are the kernel's on p2 and p3 distinct in an identifiable way? Can you be sure it was not a mix of the p2 kernel and p3 world that booted? I ask because . . . One way to control what world is booted is to adjust the /etc/fstab where the /boot/kernel/kernel is loaded from, having that /etc/fstab to point to a different / area. I do this on small, single board computers to get the kernel from a microsd card but world from a USB storage media device. (I tend to use some form of labeling style reference to avoid device numbering dependencies.) The /etc/fstab where world is from has / agreeing and directs swap partition bindings and such that are appropriate to the specific world. (I've frequently had a world on the microsd card that the initial /etc/fstab can be edited to point to. This gives me a way to boot if there is a problem for the USB media.) I've done such things in gpt and non-gpt contexts. Any chance that that /etc/fstab initially used points to p3's world for / ? There are also things like /boot/loader.conf having something like: vfs.root.mountfrom='ufs:/dev/gpt/MyRoot' to control where things are booted from. > If I have MBR, I could override "active" slice in boot0 MBR loader > interactively. > > Is it analogous feature for GPT? === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-stable@freebsd.org Tue Oct 30 22:58:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E58A1036A99 for ; Tue, 30 Oct 2018 22:58:52 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2r.ore.mailhop.org (outbound2r.ore.mailhop.org [54.200.129.228]) (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 E719A7E5A3 for ; Tue, 30 Oct 2018 22:58:51 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1540940331; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=frgZi9nJtBWGQphyJvADeR+rM9loagyrWycJVDL1rvO6CJUfCTVpVlvr6m1vKjCafsb/dBZQn7D8l mtaulJVd9EtyzScIAqJi2ptpV90/Mh/pbthlXSj2bvRqFDGRCmd/4aQonpOxqZorADUC9f8yPJj6gb EafPJFDLG9zcmlwZagNhxVM5cgBBDjahBHdkhvvlYWCGaCaKxr8Jvu+Npi/yzFKQ0RP8j/Ib+NKgIc BZP9Z29gOUeVn+FcNd5+TCV9e9JWMrjH/XgdVR5xUi+R3CmKWCqDvB0ZPK5I6dYswy1a2X15TbvPjM XYOXbXE5l8QNnRD/IfmXxoy0eFoerkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=crimCGb5fi0fbN4e7a7lG4ZOErPtxeEd5th0yVX9Kec=; b=Mtf7/fcrki8wO7V05AwQH3lVoJ9OUIq7i8WguTENvEjU+QDf2kE3JLH4P06OdC2hnukM/4wpD8GTF WallSzrxkRwgSP/kxoyLYKX5cW73YpPicwKH5MIwO/a9WTtJlTQp8ID9jzC1+UbIX5EKjf0Few5/E8 GUAmOqPIbTw0EPTZZ+m7QwueaC30XPEMdttXGmqyLDQXrrsyOyiCmdaR6tDODGzFVQiCrk/s8eDUBi BM2oRSSNEioPSAb6zQvSjM986aiD2+41J3LCLa9zZ/7rYxcGgwYcpxKy9pNQdXB4VTskInjw1tCE6z 6GbwvtnHM6JG9RUa2s8CCe7sn/e3q2w== ARC-Authentication-Results: i=1; outbound2.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=crimCGb5fi0fbN4e7a7lG4ZOErPtxeEd5th0yVX9Kec=; b=KAJeuRjHE47cNuGzxcazHZpeCreLwCUgtgpic8+gRCL901ib2Q0WE5wno7SgY1TeW+GgnpBfewQ/6 msM65xxEl3Y+anHCjSJXEiloXtqQxkJ4eAY1V+FocD2VltR2oANdrZ+DfdgJXt2yk8cXBk7434P3Jt s0zb9hR4lgtS8ZUaeZUigJVypyvJB8PGCyHvTnfG+0FJMnZrTclAigTpH74uS1heL+gUiTvhJbRYek naI+EDyTLZxhckBh+4AS0hu8EP8oHwTn9hjRS9hNs6paYIj9izgaaViNja7l+wICw9j6t92Bm3ssjp YrINUdRBtriswsG8I0o6gcZRha6zKag== X-MHO-RoutePath: aGlwcGll X-MHO-User: 5d0ffb1e-dc97-11e8-a630-335f030b21f2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 5d0ffb1e-dc97-11e8-a630-335f030b21f2; Tue, 30 Oct 2018 22:58:50 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w9UMwnHj065552; Tue, 30 Oct 2018 16:58:49 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1540940329.22340.160.camel@freebsd.org> Subject: Re: How to boot from GPT partition without "bootme" attribute? From: Ian Lepore To: lev@FreeBSD.org, freebsd-stable@freebsd.org Date: Tue, 30 Oct 2018 16:58:49 -0600 In-Reply-To: <0c51f6ec-4190-18eb-6e67-e364509bf6c8@FreeBSD.org> References: <0c51f6ec-4190-18eb-6e67-e364509bf6c8@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 22:58:52 -0000 On Tue, 2018-10-30 at 21:37 +0300, Lev Serebryakov wrote: >  I have disk with GPT scheme and three partitions: > > p1 - freebsd-boot > p2 - freebsd-ufs > p3 - freebsd-ufs > >  pmbr is installed on this disk, and gptboot is installed on p1. Both > p2 > and p3 contains valid FreeBSD installation, with /boot/loader, > kernel, > and everything. > >  I have attribute "bootme" set on p3, but not on p2. > >  What should I do to boot from p2? > >  I've tried to interrupt gptboot and override its choice: > >  0:ad(0p3)/boot/loader > >  with > >  0:ad(0p2)/boot/loader > >  After that loader, loaded from p2, loads kernel from p3 and boots > system from p3! > >  If I have MBR, I could override "active" slice in boot0 MBR loader > interactively. > >  Is it analogous feature for GPT? > While loader(8) is loading the kernel, interrupt it to get the console prompt (or ask the menu to give the prompt if you use menus) and do:  unload  set currdev=disk0p2  boot -- Ian From owner-freebsd-stable@freebsd.org Tue Oct 30 22:59:11 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A3721036ABB for ; Tue, 30 Oct 2018 22:59:11 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id AB65C7E5C2 for ; Tue, 30 Oct 2018 22:59:10 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:7863:d468:19f9:6573]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 0B79CD45; Wed, 31 Oct 2018 01:59:08 +0300 (MSK) Date: Wed, 31 Oct 2018 01:59:08 +0300 From: Lev Serebryakov Reply-To: Lev Serebryakov Organization: FreeBSD Message-ID: <1265066238.20181031015908@serebryakov.spb.ru> To: Mark Millard , FreeBSD-STABLE Mailing List Subject: Re: How to boot from GPT partition without "bootme" attribute? In-Reply-To: References: 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.29 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, 30 Oct 2018 22:59:11 -0000 Hello Mark, Wednesday, October 31, 2018, 12:38:07 AM, you wrote: >> After that loader, loaded from p2, loads kernel from p3 and boots >> system from p3! > Are the kernel's on p2 and p3 distinct in an identifiable way? > Can you be sure it was not a mix of the p2 kernel and p3 world > that booted? I ask because . . . Maybe, it is kernel from p2 and userland from p3, but anyway, it is not what I want to achieve. I'll add other kernel IDENT for other partition for check, but I'm sure, that p3 is moutned as /. I have different /etc/fstab on different partitions, of course. If kernel on "bootme" GPT partition will be faulty, it will be disaster, as gptboot could not (or I can not find how to) switch "bootme" attribute of GPT partition. I want to migrate my NanoBSD images from MBR to GPT, but I can not find way to easily boot from "previous" partition when "new" one is messed up. > Any chance that that /etc/fstab initially used points > to p3's world for / ? /etc/fstab on p2 points to p2, and /etc/fstab on p3 points to p3, I'm sure. -- Best regards, Lev mailto:lev@FreeBSD.org From owner-freebsd-stable@freebsd.org Tue Oct 30 23:02:13 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 358C61036D83 for ; Tue, 30 Oct 2018 23:02:13 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id CF0C17E9BC; Tue, 30 Oct 2018 23:02:12 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:7863:d468:19f9:6573]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id B2E67D48; Wed, 31 Oct 2018 02:02:11 +0300 (MSK) Date: Wed, 31 Oct 2018 02:02:11 +0300 From: Lev Serebryakov Reply-To: Lev Serebryakov Organization: FreeBSD Message-ID: <1925766357.20181031020211@serebryakov.spb.ru> To: Ian Lepore , freebsd-stable@freebsd.org Subject: Re: How to boot from GPT partition without "bootme" attribute? In-Reply-To: <1540940329.22340.160.camel@freebsd.org> References: <0c51f6ec-4190-18eb-6e67-e364509bf6c8@FreeBSD.org> <1540940329.22340.160.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: base64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 30 Oct 2018 23:02:13 -0000 SGVsbG8gSWFuLA0KDQpXZWRuZXNkYXksIE9jdG9iZXIgMzEsIDIwMTgsIDE6NTg6NDkgQU0s IHlvdSB3cm90ZToNCg0KDQo+IFdoaWxlIGxvYWRlcig4KSBpcyBsb2FkaW5nIHRoZSBrZXJu ZWwsIGludGVycnVwdCBpdCB0byBnZXQgdGhlIGNvbnNvbGUNCj4gcHJvbXB0IChvciBhc2sg dGhlIG1lbnUgdG8gZ2l2ZSB0aGUgcHJvbXB0IGlmIHlvdSB1c2UgbWVudXMpIGFuZCBkbzoN Cg0KPiCgdW5sb2FkDQo+IKBzZXQgY3VycmRldj1kaXNrMHAyDQo+IKBib290DQogVGhueCEN Cg0KIElzIGl0IHBvc3NpYmxlIHRvIHBhc3MgdGhpcyBpbmZvcm1hdGlvbiBmcm9tIGdwdGJv b3QoOCkgdG8gbG9hZGVyKDgpDQpzb21laG93PyBTZWxlY3RpbmcgImFjdGl2ZSIgcGFydGl0 aW9uIHRoaXMgd2F5IGxvb2tzIHRlZGlvdXMuDQoNCiBJTUhPLCBiZXR0ZXIgc29sdXRpb24g d2lsbCBiZSBhZGQgc29tZSBpbnRlcmFjdGl2aXR5IHRvIGdwdGJvb3QoOCkgYWtpbiB0bw0K c3VwZXItY29tcGFjdCwgYnV0IG1pZ2h0eSBib290MCg4KQ0KDQotLSANCkJlc3QgcmVnYXJk cywNCiBMZXYgICAgICAgICAgICAgICAgICAgICAgICAgICAgbWFpbHRvOmxldkBGcmVlQlNE Lm9yZw== From owner-freebsd-stable@freebsd.org Wed Oct 31 10:56:11 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B7F610D3109 for ; Wed, 31 Oct 2018 10:56:11 +0000 (UTC) (envelope-from raul@b2n.org) Received: from mail3.custos.es (bohn.b2n.org [212.34.158.159]) by mx1.freebsd.org (Postfix) with ESMTP id 6D1AD6F6D8 for ; Wed, 31 Oct 2018 10:56:09 +0000 (UTC) (envelope-from raul@b2n.org) Received: from plank.b2n.org (plank.b2n.org [213.37.4.13]) by mail3.custos.es (Postfix) with ESMTP id D4194125F2C for ; Wed, 31 Oct 2018 11:56:01 +0100 (CET) Received: from turing.b2n.org (unknown [10.64.3.2]) by plank.b2n.org (Postfix) with ESMTP id 730952D06E for ; Wed, 31 Oct 2018 11:56:00 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=b2n.org; s=dkim; t=1540983360; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=XrUeg7IX5CsTMkx73bZ61LVdRdMjisYozcY/eZRQ8Mo=; b=AqcTqpJFmi/FT/FIMi5TW/qH65hHts3ZZ726oVDU+NNPQ+kWpENQUZQus4G5wRoYiRW+vO ZhOJXJxayHsPINJP6O5PF4MbWq3bh4rKH60Zc+rRjWfRm817tzS+RMZwEG9vCjx2x6ZDdV PAh/aB9wGqRttTlr4sfbvZBW45jICj7s3W/VWHiodtUFq1uqjNhf+7GwWGtwZ2LyibU2CN hP+Es7SHuGsncgnyG/I6hDRNevgn0dgzpLMhf1MvTMQAnzgku2+mcHSCaddrTORCsfv4e9 zLemzZbl0+/i7bK/g5GeF0GECj7Uo+bgrBhx3IgFdMWkca3mMnKjn20cWMDgtw== Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.b2n.org (Postfix) with ESMTPSA id 3878E385502 for ; Wed, 31 Oct 2018 11:56:00 +0100 (CET) To: freebsd-stable@freebsd.org From: =?UTF-8?B?UmHDumw=?= Openpgp: preference=signencrypt Autocrypt: addr=raul@b2n.org; prefer-encrypt=mutual; keydata= xsFNBFns2ZIBEAC7xWTucmdvscBLlryw1xv2opUqexkdusr4cR8lzRn+KOUmpDoibIK4C0In PPY157sWviEwCx24Hs+e664vwx6xD7zQ7ttVE30t+bm4iVqdxyIDMdgEbWOcTpYRjhRIGGpX BeBt+eYw+uE519bXHJZJJGcIzUU6Wk9fghx8RHMb5IEg4+9rsyCnEznE8u8AfJTgeOdA4h0h EweHjOFJdn6i+3r1KZlwFMIUFBo+q8ldHVzjPZGGSjguW62GgYMFn5uiYxpqTkKqD9FwrRlz n41QIOzE8o6jJfF/r4py1EiHwOTfvrrCNOA5cJXFrTsmCTj8dAySEThlxfSKQED0uPZVaegL 8KDvJ56oR9U6YE86fTdn713TvukVWeK58ZjgF/kQMymTjFFbe2IeG/QkxjWbcHb8EpLNXtIL HFX0+sezFnhKJrfGyq4jqWqWp8suzzhgQBNSQxkHNuQADabHJ13VH6qqIeC0UGUtUjEwxznh 51uyh0APK+7xhSc4+JKcVZcK7xkhY04wPT4x/dn2IbwCXewTMHROqo4oWP2ajN4bTOte1tot ZUbeLgPdr9iZrTSdt63lnTTbAxnXAxxBc/q8hVsiWM9SfOIkZ0kGeNA8NlrubcuXQzTJHy2h JhmLSuLfUaGZcr+F/3KtohTvshy2291/ruM8ExMUSDd3wb96fwARAQABzSxSYcO6bCBNdcOx b3ogLSBDVVNUT1MgPHJhdWwubXVub3pAY3VzdG9zLmVzPsLBfwQTAQIAKQUCWezZkgIbIwUJ CWYBgAcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJELKl4+9JDtBb750P/1d/rU1Ngc94 rVL2vqDEijJdFYEZbzE96MugnwCEdJ8Al/6mWbD4vaPIuuuW+TE8dMPItcUv1vq8D/wX8NSs OS5FNu7XfGpjjxOKdUpLLoiGbJC4AbhMZhvdpvWQQAk5szCzGT+nYPve7Ut6SyWtZPYwWM+K o5CNyRu838jfGhm6G8CvaLJHcrMBlA87OBkQi4tzT+NIBBp0U8vGXV8z6LlpI/EGXLgSJPnO pFn8PL6tXZ1uiI+AXVJT+emdB68InejcHgFrwoowZBLzXllGPH4pYVZ1h9pPARoPCmSlCe4x g+ELKvkogatQM4BXuzRGiYCVJDBqgFoRDDd/dnmsCb5DV0xWSlmpWPy06e9C8PwCI3NmukCh mq2ic74mAo9lKTv8VVc9czushKagVQhYPT3o6DHOCFJeoXvaQWIOprpAkcf5nz15SjeZWFqW EzF8+0LUocGLDLMaDkWBBruJuQfz8V3ktDdXkEv55sgrbf/98sGdIz3aOSrLy3Rop3m3shnM Uua1XpE6Fv+6g8owSI15k8bd0lmsq83/YYW2hN0vQWn/HR7xTwpA9fZh4stxJRJAHAJ7nQ/u SJkp2+NVOn9ZImKqegqqmn+amnkRsSunM1fe/i2GVsgKzkOlyDiLotUk8JU6t741kIJscGfW 8y1uC2Cf7T1tHdQsG4Hq1+C/zsFNBFns2ZIBEACv+REqRGM1e6CuNil4Kim3Bi5RTXXx2/JJ dCC5W0ZsEoynoQ31RJ+3nu9OGDGzmEL+2fMVxvKiomXnwq6xZmhb6HFw03e/lOfYEEMm1hjj 23Dw9gNO3Dy5j1o3vzOWPOQwZpsE2vG0XE3ZfZ+Rg1b3SIe1R7w0nnzDAjznpYuG6WEYGFr9 r7IDouLqgBeR1i4B4M+7E8FLql06pyxF4plcJ1KSf++SNZf0arFuLzGZh9aA6L4OQ3eIqBg0 VqId8GiO6cz1t68dpOuwlt/HEcA3tCL15IIhKxQyWAU3S4yM/KBSXXGW2OI+EebFrBxYXySA IByYogpq795uiZ6gBDtQDvx1A8WHMy/7nDnXwJ9XTKzpjIFjKH0Gi/IpvxD1Aci/JbCzB76w iTA4Hbdw0iiZFUN3Wby5eVvkOBA5G+uaLJH10nyIZAe1IszaCxK+3sad6bVd2FsD7qmVHovq iLrjEa+p36kZB/Aeqm+Xwnwss32cOT3GZ6Cgs3ZYBwLJcPo+hhV9JXn7j8nt4tfJr5wm/HDN 4LgUKhUxTWrTS+iTbMtQ9NQdY4QrnB8Qa5E9mEeuZgorZCIrQm1D6MaoEX6fJ8yTru82EavX 9geX58VlFNcK32Ys1Ox0gsg6bX3CRRdAX42X4byuGGkkFwANULSCtepqbm9HO7FbGjkzNtO/ TQARAQABwsFlBBgBAgAPBQJZ7NmSAhsMBQkJZgGAAAoJELKl4+9JDtBbHaYP+wXvUGqFdxea O3Ec2WAFDzSS7EnLWAxrEHkKCIpVKYQ0TlYTd9HS2aGZ0oVJA3vNezJ3j8yusylNO9wWWIdX JQ5hrgzvEYzvb1hpo65CUsK954scz8lmh+Wh2bx728PssQsbL2gCiUJsLD6IDm9Q7374Ztsb sd1Qg+G7TmU2VQrVMo7eA3hGeNCcmiZH3zxHF8L2q1IEbo11/GaDzg9E53/lkd2+gizSD2PG OabRmIRAY7pUDjn54trQy/5fxNq0idyUUZYe6UbhE7UhpWAEdnU2Hp8bVyeJDMM6HiV7Apqg SuGcmGMYfBlNd+itjJk4MFYoIij+UiryCHfWwO8+bELyffDgHEcoVsgbL7Nn6TXoH6QjuMD2 cjGXoKplCV5jxTQJAd5/vnczlTbDA30UOwcje02r4mMh3vLaYeLNJ0Z8RCh09o7IeGskmwy4 849V5LoX3/TRKDnCf+rK7v08SEhb5QeUZ2GUwyEEby67TEmKE5LmQRj1gPnrH3Wlx2BkS/pS Y3k2cGEtoSYF3gUIec2VvzG52VSMJIOZZDcgscwvubJdRdvNPhGApWPgT8ZDfeafgJz/tRg/ hj6Zeln2xKBxgVKY/dJJouCJZdTOE6lB9vRJyCveVSi+uDu3G8idTON5cRLEy/acpBE8n0Ve noPvPYKoN8z5Hsw8DRyWVkxU Subject: 'loadable library and perl binaries are mismatched' rebuilding ports after upgrade to 12.0-BETA2 r339930 Message-ID: <7de5da1e-125c-1411-9398-433f09bfecd0@b2n.org> Date: Wed, 31 Oct 2018 11:55:59 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 31 Oct 2018 10:56:11 -0000 Hi! Coming from 11.2p4, using sources, everything went fine and is already running without noticeable problem. Mariadb101 had some known problem so after trying well documented workaround on it's rc.d script it finally get promoted to Mariadb102 ... *Great work*, version 12 already feels smooth, performant, snappy ... well rounded. Before deleting old-libs I tried a 'portmaster -Raf' and there is where I'm getting into trouble. This installation has survived three server boxes and in the meantime (since FreeBSD version ~6) lots of big changes on the ports tree have happened. It has more than 800 ports installed so it's a bit complex setup. I try everything on this box. Maybe I broke some port dependencies, or I miss something, I'm not sure. Build fails for me with: [....] Dumper.c loadable library and perl binaries are mismatched (got handshake key 0xd480080, needed 0xe180080) [....] It can be on Dumper.c, vxs.c ... and others. No matter how I try always get stuck on this perl mismatch. I have no ports / portmaster tricks left to try, can anyone give me a hint?. Thanks in advance. Raúl. From owner-freebsd-stable@freebsd.org Wed Oct 31 13:43:03 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F92F10D991A for ; Wed, 31 Oct 2018 13:43:03 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E96B756AC for ; Wed, 31 Oct 2018 13:43:02 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 4CFCB110498 for ; Wed, 31 Oct 2018 13:42:54 +0000 (UTC) From: Stefan Bethke Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: ZFS high write IO in single user mode Message-Id: <9D56C3BA-753B-472F-8FD7-AF90E1F14301@lassitu.de> Date: Wed, 31 Oct 2018 14:42:52 +0100 To: FreeBSD Stable X-Mailer: Apple Mail (2.3445.100.39) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 31 Oct 2018 13:43:03 -0000 I have two hosts that are configured identically (in a kind of manual = hot-standby configuration), running a set of jails each. ZFS datasets = for the jails and bhyve VMs are synced across regularly. When one of the = machines exhibits a problem, I can shut down the problematic jails or = the whole machine, and start the jails/VMs on the other host. This has = been working really well for the past ~10 years. A couple of years ago, one of the ZFS pools on one of the machines = developed some logical inconsistencies that were not detected by zpool = scrub. The only indication that something was amiss was high disk IO, in = particular, writes, even when no processes were running. I eventually = resolved that situation by recreating the zpool and restoring the = datasets from the working machine. About a year ago, I upgraded the hardware and in the process created = fresh pools. This has been running well. Since about two days ago, I now = have the situation again where I have a steady write rate even in single = user mode, with the root dataset mounted read only, and the second pool = that contains the jail datasets not mounted at all. I only have a video console (via IPMI KVM) so I won=E2=80=99t transcribe = the complete output, but here=E2=80=99s what I think are significant = observations: gstat reports ~30 writes/sec on each of the two disks that make up the = zmirror pool. mount shows the root dataset to be mounted read-only. zpool status takes a really long time, and then reports that everything = is fine for both pools (boot/os and jails). smartctl doesn=E2=80=99t show any problems for either of the disks. I=E2=80=99m happy to just wipe the pools and start fresh, but I=E2=80=99d = like to use this opportunity to hopefully figure out why ZFS appears to = act weirdly, and hopefully find a permanent fix. This is 11-stable from = September 13th. Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-stable@freebsd.org Wed Oct 31 17:04:47 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C11D10DF485 for ; Wed, 31 Oct 2018 17:04:47 +0000 (UTC) (envelope-from bounce@lachlan.in.net) Received: from server.pmta001.nsriversystems.in.net (server.pmta001.nsriversystems.in.net [46.105.85.240]) by mx1.freebsd.org (Postfix) with ESMTP id 0546C7E6EC for ; Wed, 31 Oct 2018 17:04:46 +0000 (UTC) (envelope-from bounce@lachlan.in.net) To: freebsd-stable@freebsd.org Subject: Perfect present for your loved once with 50% off Message-ID: <8cfd095a446abaff44e9680ae13b70a0@lachlan.in.net> Date: Thu, 01 Nov 2018 00:23:15 +0800 From: "Love Lamp" Reply-To: Love@lachlan.in.net Complaint-To: abuse@lachlan.in.net Priority: 3 Precedence: bulk MIME-Version: 1.0 X-Mailer-LID: 6 X-Mailer-RecptId: 300237 X-Mailer-SID: 6 X-Abuse-Reports-To: abuse@lachlan.in.net 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.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2018 17:04:47 -0000 Your email client cannot read this email. To view it online, please go here: http://lachlan.in.net/lachlan/display.php?M=300237&C=51fa20b7fe2a3ee4355f4125384cc9b9&S=6&L=6&N=3 To stop receiving these emails:http://lachlan.in.net/lachlan/unsubscribe.php?M=300237&C=51fa20b7fe2a3ee4355f4125384cc9b9&L=6&N=6 From owner-freebsd-stable@freebsd.org Wed Oct 31 17:13:33 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57A7910DF990 for ; Wed, 31 Oct 2018 17:13:33 +0000 (UTC) (envelope-from juraj.vanco@intel.com) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga103.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF48E7F1F6 for ; Wed, 31 Oct 2018 17:13:32 +0000 (UTC) (envelope-from juraj.vanco@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Oct 2018 10:13:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,447,1534834800"; d="scan'208";a="83045260" Received: from irsmsx106.ger.corp.intel.com ([163.33.3.31]) by fmsmga008.fm.intel.com with ESMTP; 31 Oct 2018 10:13:24 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.253]) by IRSMSX106.ger.corp.intel.com ([169.254.8.163]) with mapi id 14.03.0415.000; Wed, 31 Oct 2018 17:13:24 +0000 From: "Vanco, Juraj" To: Konstantin Belousov , "Bennett, Ciunas" CC: "freebsd-stable@freebsd.org" Subject: RE: Possible memory leak in the kernel (contigmalloc) Thread-Topic: Possible memory leak in the kernel (contigmalloc) Thread-Index: AdRrtbzKvvQI2iPZToSPdiaEvmHIXQBqhpgAALREjJAAAgPuAAABiKNgABAShYAALsIvoA== Date: Wed, 31 Oct 2018 17:13:23 +0000 Message-ID: <996B37956731CF40B1A674B085ACCE9440F747CA@IRSMSX103.ger.corp.intel.com> References: <770FD3608C9E864796AB46CB37B561B1BDFCF0CD@IRSMSX101.ger.corp.intel.com> <20181026201230.GV5335@kib.kiev.ua> <770FD3608C9E864796AB46CB37B561B1BE0B4096@irsmsx105.ger.corp.intel.com> <20181030101150.GN5335@kib.kiev.ua> <770FD3608C9E864796AB46CB37B561B1BE0B5562@irsmsx105.ger.corp.intel.com> <20181030183557.GP5335@kib.kiev.ua> In-Reply-To: <20181030183557.GP5335@kib.kiev.ua> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDUwNmYxMGItYzUzYi00ZDg3LWE1YTAtZjExODg4NDQ5ZDhiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiMTNMdTNhUkdYOTFTbGZxNUVscDZcL1o4TzREU0tIXC8zSEVDYmIzZ09hNVwvVW0rRnNZSUhTd2wwcVdsUW1QWjVLbiJ9 dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 31 Oct 2018 17:13:33 -0000 Hi Konstatin, what we can directly see, is that the number of inactive pages increases an= d this happens after running single loop of contigmalloc -> contigfree even= with the repeating size of allocated blocks. The only source of inactive page could come from kernel memory management c= ontrol structures. Even if such structure becomes once inactive (cached pages), I do not see a= ny reason that kernel cannot reclaim these inactive cached pages when again= the contigmalloc asks for the same space of memory. I think this cycle should not take all the amount of physical memory withou= t being able to reclaim back when it's out of memory: int array0[10] =3D {2097152, 1024, 2101248, 1024, 2097152, 2101248, 210= 1248, 2097152, 2101248, 1024}; int array1[10] =3D {1024, 2101248, 2097152, 2101248, 2101248, 2097152, = 1024, 2101248, 1024, 2097152}; void *mem_blocks[10]; for (i =3D 0; i < 10; i++) mem_blocks[i] =3D contigmalloc(array0[i], TEST_MEM, 0, 0, ~0, PAGE_= SIZE, 0); for (i =3D 0; i < 10; i++) contigfree(mem_blocks[i], array0[i], TEST_MEM); for (i =3D 0; i < 10; i++) mem_blocks[i] =3D contigmalloc(array1[i], TEST_MEM, 0, 0, ~0, PAGE_= SIZE, 0); for (i =3D 0; i < 10; i++) contigfree(mem_blocks[i], array1[i], TEST_MEM); jv -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd= .org] On Behalf Of Konstantin Belousov Sent: Tuesday, October 30, 2018 6:36 PM To: Bennett, Ciunas Cc: freebsd-stable@freebsd.org Subject: Re: Possible memory leak in the kernel (contigmalloc) On Tue, Oct 30, 2018 at 11:15:47AM +0000, Bennett, Ciunas wrote: > Hi, > The only other activity that is running is the csh script that is insert= ing and removing the kernel module. > I am not using the VM for any other purpose but to run this test. > In my tests the correlation between memory allocation and moving to inact= ive list can be seen. > I don't think any other process is creating the inactive memory. But it is created. More, since anon private memory is freed (not deactivat= ed) on the process exit, something is accumulating the memory. The other possibility is that the memory is the caching pages from vnodes, = but for this buffers must be created and then reclaimed, which would sugges= t even more activity on the system. > Thanks. > = > -----Original Message----- > From: Konstantin Belousov [mailto:kostikbel@gmail.com] > Sent: Tuesday, October 30, 2018 10:12 AM > To: Bennett, Ciunas > Cc: freebsd-stable@freebsd.org > Subject: Re: Possible memory leak in the kernel (contigmalloc) > = > On Tue, Oct 30, 2018 at 09:46:59AM +0000, Bennett, Ciunas wrote: > > Hi, > > = > > I was debugging the issue by viewing the free ques "sysctl = > > vm.phys_free" and also using "show page" in ddb. The inactive memory = > > is never being released back into the free que. I thought that when = > > inactive memory reaches a certain threshold that the kernel will = > > start reclaiming and move it to the free list? In my program this is = > > not happening, the program uses free memory (contigmalloc), and then = > > it is put into the inactive que (contiigfree) when the program frees it. > Contigfree() does not release memory into inactive queue. By definition,= inactive pages have valid content, which is not possible for the pages fre= ed by contigfree(). > contigfree()->kmem_free()->kmem_unback()->vm_page_free(). > = > = > > This inactive memory is never released by the kernel, and the = > > inactive que grows until all the memory is in this que. I have = > > attached a xml sheet that shows the memory usage in the system. > Inactive memory is not freed, it makes no sense as far as there is = > valid content, which is either not recoverable (anon memory or dirty = > file > pages) or high-cost to restore (clean file pages, need to re-read from di= sk). Inactive is processed by pagedaemon when system has memory deficit, a= nd either inactive pages are written to swap, or written to their file back= ing storage. > = > I suspect that you have other activities on your system going on, which c= ause creation of the inactive memory and unrecoverable fragmentation. > Note that contigmalloc() tries to do defragmentation to satisfy requests,= but this is not always possible. > = > = > > Ciunas. > > = > > -----Original Message----- > > From: Konstantin Belousov [mailto:kostikbel@gmail.com] > > Sent: Friday, October 26, 2018 9:13 PM > > To: Bennett, Ciunas > > Cc: freebsd-stable@freebsd.org > > Subject: Re: Possible memory leak in the kernel (contigmalloc) > > = > > On Wed, Oct 24, 2018 at 04:27:52PM +0000, Bennett, Ciunas wrote: > > > Hello, > > > = > > > I have encountered an issue with a kernel application that I have = > > > written, the issue might be caused by a memory leak in the kernel. > > > The application allocates and deallocates contiguous memory using > > > contigmalloc() and contigfree(). The application will fail after a = > > > period of time because there is not enough free contiguous memory = > > > left. There could be an issue with the freeing of memory when = > > > using the contigfree() function. > > > > > = > > It is unlikely that there is an issue with a leak, but I would be not s= urprised if your allocation/free pattern would cause fragmentation on free = lists that results in contigmalloc(9) failures after. > > = > > Look at the vmstat -z/vmstat -m output to see uma and malloc stats. > > More interesting for your case can be the output from > > sysctl vm.phys_free > > which provides information about the free queues and order of free page= s on them. > > -------------------------------------------------------------- > > Intel Research and Development Ireland Limited Registered in Ireland = > > Registered Office: Collinstown Industrial Park, Leixlip, County = > > Kildare Registered Number: 308263 > > = > > = > > This e-mail and any attachments may contain confidential material = > > for the sole use of the intended recipient(s). Any review or = > > distribution by others is strictly prohibited. If you are not the = > > intended recipient, please contact the sender and delete all copies. > = > = > -------------------------------------------------------------- > Intel Research and Development Ireland Limited Registered in Ireland = > Registered Office: Collinstown Industrial Park, Leixlip, County = > Kildare Registered Number: 308263 > = > = > This e-mail and any attachments may contain confidential material for = > the sole use of the intended recipient(s). Any review or distribution = > by others is strictly prohibited. If you are not the intended = > recipient, please contact the sender and delete all copies. > = _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -------------------------------------------------------------- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the s= ole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact = the sender and delete all copies. From owner-freebsd-stable@freebsd.org Wed Oct 31 19:00:24 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E430010E241A for ; Wed, 31 Oct 2018 19:00:23 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8184A83CA1 for ; Wed, 31 Oct 2018 19:00:23 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1gHvix-0000Qu-Hv for freebsd-stable@freebsd.org; Wed, 31 Oct 2018 20:00:16 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Subject: Re: 'loadable library and perl binaries are mismatched' rebuilding ports after upgrade to 12.0-BETA2 r339930 References: <7de5da1e-125c-1411-9398-433f09bfecd0@b2n.org> Date: Wed, 31 Oct 2018 19:40:30 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: <7de5da1e-125c-1411-9398-433f09bfecd0@b2n.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 897836312160ed0141c32cdc6ac56212 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 31 Oct 2018 19:00:24 -0000 On Wed, 31 Oct 2018 11:55:59 +0100, Ra=C3=BAl wrote: > Hi! > > Coming from 11.2p4, using sources, everything went fine and is already= > running without noticeable problem. Mariadb101 had some known problem = so > after trying well documented workaround on it's rc.d script it finally= > get promoted to Mariadb102 ... > > *Great work*, version 12 already feels smooth, performant, snappy ... > well rounded. > > Before deleting old-libs I tried a 'portmaster -Raf' and there is wher= e > I'm getting into trouble. This installation has survived three server > boxes and in the meantime (since FreeBSD version ~6) lots of big chang= es > on the ports tree have happened. It has more than 800 ports installed = so > it's a bit complex setup. I try everything on this box. Maybe I broke > some port dependencies, or I miss something, I'm not sure. Build fails= > for me with: > > [....] > Dumper.c loadable library and perl binaries are mismatched (got > handshake key 0xd480080, needed 0xe180080) > [....] > > It can be on Dumper.c, vxs.c ... and others. > No matter how I try always get stuck on this perl mismatch. > > I have no ports / portmaster tricks left to try, can anyone give me a = = > hint?. What version of perl is being upgraded to what version? In /usr/ports/UPDATING there are instructions on how to update perl usin= g = portmaster. Regards, Ronald. > > Thanks in advance. > > Ra=C3=BAl. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.o= rg" From owner-freebsd-stable@freebsd.org Wed Oct 31 19:52:49 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4308B10E3D69 for ; Wed, 31 Oct 2018 19:52:49 +0000 (UTC) (envelope-from bounce-1064-23316020-656-248@asotca.cf) Received: from pron.asotca.cf (pron.asotca.cf [45.33.54.239]) by mx1.freebsd.org (Postfix) with ESMTP id D3463863BD for ; Wed, 31 Oct 2018 19:52:48 +0000 (UTC) (envelope-from bounce-1064-23316020-656-248@asotca.cf) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=asotcacf; d=asotca.cf; h=Date:To:From:Reply-to:Subject:Message-ID:List-Unsubscribe:MIME-Version:Content-Type; i=newsletter@asotca.cf; bh=M+Tufe7OwOsY+1IsG1pK3SqyKYM=; b=mCzyufdOZY4UILjQ2H5E4+TP/MCf172iLfjw/3d2XBXDpba7LUgDq5uSc4swJP2S7YSw0SrOojdh tblTyyJNSyEveTSY4FFbbwmPy1vXjwmkXepkBGzTzS8/h33vBw1BwDiLv+iTkmpOLfr7ix8m13SR wOTr3IVrAXGqgTKB8e8= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=asotcacf; d=asotca.cf; b=Appw315GQzNdsnwZtKi0OG/E8h6hl15D6MuNtQ00cgr9Jv7920q7D+ut0YOaQkWZ4/z6KRv0LJpl N7GzOoQnkBg5vv3JNza9c2bhJ6fTrY88QlpEum2cu2dBD7BWfHWTeDZeNCMplgifC/PJ1xho/JlV /Vos+h6+ybN/v+tdimg=; Received: by pron.asotca.cf id hr84120e97c9 for ; Wed, 31 Oct 2018 19:51:20 +0000 (envelope-from ) Date: Wed, 31 Oct 2018 15:55:01 +0100 To: "freebsd-stable@freebsd.org" From: Winter Clothes Reply-to: Winter Clothes Subject: Today's Special Deals! | Winter Goose Coats 70% OFF! Message-ID: <772637c6dd0069042d49691cfbc58dff@localhost> X-Priority: 3 X-Mailer: Email Sending System X-Complaints-To: anzhelanebjtc@go2.pl X-MessageID: NXx8fHwxMTQyOTR8fHx8ZnJlZWJzZC1zdGFibGVAZnJlZWJzZC5vcmd8fHx8M3x8fHwxfHx8fDA%3D X-Report-Abuse: MIME-Version: 1.0 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 31 Oct 2018 19:52:49 -0000 Today's Special Deals! | Winter Goose Coats 70% OFF! Your email client cannot read this email. To view it online, please go here: http://pron.asotca.cf/edmi/wb.php?p=3Drx= /rx/rs/2gym/rv/rs To stop receiving these emails:http://pron.asotca.cf/edmi/u.php?p=3Drx/rs/2= gym/rv/rx/rs From owner-freebsd-stable@freebsd.org Thu Nov 1 02:26:29 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D327E10E0A7C for ; Thu, 1 Nov 2018 02:26:29 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [60.36.166.23]) by mx1.freebsd.org (Postfix) with ESMTP id C088D798E1; Thu, 1 Nov 2018 02:26:28 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20181101022619.LASQ16956.msc13.plala.or.jp@localhost>; Thu, 1 Nov 2018 11:26:19 +0900 Date: Thu, 01 Nov 2018 11:26:14 +0900 (JST) Message-Id: <20181101.112614.410204338792675244.ish@amail.plala.or.jp> To: freebsd-stable@freebsd.org Cc: re@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available From: Masachika ISHIZUKA In-Reply-To: <20181029160755.GQ75350@FreeBSD.org> References: <68e4423a-218a-2912-2fe2-f834c7124f6f@codelibre.net> <20181030.010424.17654226369780713.ish@amail.plala.or.jp> <20181029160755.GQ75350@FreeBSD.org> X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Thu, 1 Nov 2018 11:26:19 +0900 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 01 Nov 2018 02:26:30 -0000 >> Although it said that we could not upgrade to 12.0-BETA1 in >> the previous release note, we can upgrade to 12.0-BETA1 by >> freebsd-update. >> And at this moment, we cannot upgrade to 12.0-BETA2 by >> freebsd-update. > > Sorry, I forgot to reply to your original report. This is being looked > into. It is, unfortunately, more fallout from updating OpenSSL to > version 1.1.1. Thank you for reply and your efforts. Now, freebsd-update can upgrade 12.0-BETA2 amd64. I confirmed from both 11.2-RELEASE-p4 and 12.0-BETA1. Note that freebsd-update install dose not execute pwd_mkdb, we must execute 'pwd_mkdb -p /etc/master.passwd 'manually if we use ntpd. -- Masachika ISHIZUKA From owner-freebsd-stable@freebsd.org Thu Nov 1 06:53:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B1E710DD5BB for ; Thu, 1 Nov 2018 06:53:55 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from roadkill.tharned.org (tunnel294749-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:107f::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Tharned" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F1376BFA7 for ; Thu, 1 Nov 2018 06:53:54 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from flake.tharned.org ([IPv6:2001:470:1f11:107f:f471:2353:b30c:aa7a]) (authenticated bits=0) by roadkill.tharned.org (8.15.2/8.15.2) with ESMTPSA id wA16rFIP033191 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 1 Nov 2018 01:53:52 -0500 (CDT) (envelope-from gcr+freebsd-stable@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tharned.org; s=2017; t=1541055232; bh=I42lA0B8j4kPx8uC13GR19mLRjvK7G82htx3uVPs6Ms=; h=From:To:Subject:Date; b=wJO4GVX9b1hXc7hpi0czygV3hnh+xQcqOZmO2q5VUtVxzvcxbdE/9abq5OKH7IsjK pMZBtrDmnkwSIcoqGErumH7ZNDP/GMTcCS6ZmtfzWESBdwmZjZHsqV8g76mWGAyPWG /qxatjsHCnctjYAhBVdyqEK/6jcfGgM6fSOctUPgW0Q1RNY6sPIixuiUs+G/i/p2LZ 4Gj3+EAlf0hgfLryDdl1ppyrXbGRVqVXCRjnvlXX2g7GJJHATMn9TS3PYnoeZQYJMj UMOPCrdUgvcxtxwyPJ/3DjD1WmwNv71ogLpG4nQqrYGzhdHMEp3fTdzKwcyUI8b2fq BhzLPxPubPOTQ== X-Authentication-Warning: roadkill.tharned.org: Host [IPv6:2001:470:1f11:107f:f471:2353:b30c:aa7a] claimed to be flake.tharned.org From: Greg Rivers To: freebsd-stable@freebsd.org Subject: High UDP loss on 11.2-RELEASE-p4 Date: Thu, 01 Nov 2018 01:53:15 -0500 Message-ID: <5249318.XtdPABXNba@no.place.like.home> User-Agent: KMail/4.14.10 (FreeBSD/11.2-RELEASE-p4; KDE/4.14.38; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (roadkill.tharned.org [IPv6:2001:470:1f10:107f:0:0:0:2]); Thu, 01 Nov 2018 01:53:52 -0500 (CDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 01 Nov 2018 06:53:55 -0000 I'm seeing considerable packet loss running recursive DNS (BIND 9.12.2) on 11.2. This is on server grade hardware (HP DL380G8) with an Intel 10Gb NIC (ix). I spun up iperf3; the results were disappointing: $ iperf3 --get-server-output -c r5 -u -b 1g -R Connecting to host r5, port 5201 Reverse mode, remote host r5 is sending [ 5] local xxx.xxx.242.11 port 56921 connected to xxx.xxx.235.238 port 5201 [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-1.00 sec 77.0 MBytes 645 Mbits/sec 0.003 ms 32835/88105 (37%) [ 5] 1.00-2.00 sec 72.2 MBytes 605 Mbits/sec 0.002 ms 33813/85638 (39%) [ 5] 2.00-3.00 sec 71.3 MBytes 599 Mbits/sec 0.003 ms 34291/85534 (40%) [ 5] 3.00-4.00 sec 70.0 MBytes 587 Mbits/sec 0.012 ms 35459/85757 (41%) [ 5] 4.00-5.00 sec 71.9 MBytes 603 Mbits/sec 0.002 ms 34053/85688 (40%) [ 5] 5.00-6.00 sec 72.7 MBytes 609 Mbits/sec 0.004 ms 33354/85555 (39%) [ 5] 6.00-7.00 sec 71.7 MBytes 602 Mbits/sec 0.002 ms 33984/85472 (40%) [ 5] 7.00-8.00 sec 71.0 MBytes 596 Mbits/sec 0.002 ms 34618/85623 (40%) [ 5] 8.00-9.00 sec 70.8 MBytes 594 Mbits/sec 0.002 ms 34773/85630 (41%) [ 5] 9.00-10.00 sec 71.3 MBytes 598 Mbits/sec 0.002 ms 34593/85784 (40%) - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-10.00 sec 1.17 GBytes 1.00 Gbits/sec 0.000 ms 0/858786 (0%) sender [ 5] 0.00-10.00 sec 720 MBytes 604 Mbits/sec 0.002 ms 341773/858786 (40%) receiver Server output: ----------------------------------------------------------- Accepted connection from xxx.xxx.242.11, port 54163 [ 5] local xxx.xxx.235.238 port 5201 connected to xxx.xxx.242.11 port 56921 [ ID] Interval Transfer Bandwidth Total Datagrams [ 5] 0.00-1.00 sec 111 MBytes 930 Mbits/sec 79657 [ 5] 1.00-2.00 sec 119 MBytes 999 Mbits/sec 85536 [ 5] 2.00-3.00 sec 119 MBytes 1.00 Gbits/sec 85625 [ 5] 3.00-4.00 sec 119 MBytes 999 Mbits/sec 85541 [ 5] 4.00-5.00 sec 119 MBytes 1.00 Gbits/sec 85667 [ 5] 5.00-6.00 sec 119 MBytes 1000 Mbits/sec 85592 [ 5] 6.00-7.00 sec 119 MBytes 1.00 Gbits/sec 85720 [ 5] 7.00-8.00 sec 119 MBytes 998 Mbits/sec 85457 [ 5] 8.00-9.00 sec 119 MBytes 1.00 Gbits/sec 85622 [ 5] 9.00-10.00 sec 119 MBytes 1000 Mbits/sec 85603 [ 5] 10.00-10.10 sec 12.2 MBytes 1.02 Gbits/sec 8767 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 5] 0.00-10.10 sec 1.17 GBytes 993 Mbits/sec 0.000 ms 0/858787 (0%) 40% loss at 1Gb. I'm running with the following tunes, which did improve DNS service when I applied them: dev.ix.0.tx_processing_limit: -1 hw.ix.flow_control: 0 hw.ix.num_queues: 8 hw.ix.rx_process_limit: -1 hw.ix.rxd: 2048 hw.ix.tx_process_limit: -1 hw.ix.txd: 2048 kern.ipc.maxsockbuf: 16777216 kern.random.harvest.mask: 351 machdep.hyperthreading_allowed: 0 net.inet.ip.intr_queue_maxlen: 2048 net.inet.raw.maxdgram: 16384 net.inet.raw.recvspace: 16384 net.isr.bindthreads: 1 net.isr.defaultqlimit: 2048 net.isr.maxthreads: 16 net.link.ifqmaxlen: 4096 net.local.stream.recvspace: 16384 net.local.stream.sendspace: 16384 net.route.netisr_maxqlen: 2048 Are there any known problems with 11.2 and UDP? Can anyone else reproduce this? Any insight or suggestions? -- Greg From owner-freebsd-stable@freebsd.org Thu Nov 1 22:46:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE49810DB819 for ; Thu, 1 Nov 2018 22:46:38 +0000 (UTC) (envelope-from raul@b2n.org) Received: from mail3.custos.es (bohn.b2n.org [212.34.158.159]) by mx1.freebsd.org (Postfix) with ESMTP id 3DD178FF86 for ; Thu, 1 Nov 2018 22:46:37 +0000 (UTC) (envelope-from raul@b2n.org) Received: from plank.b2n.org (plank.b2n.org [213.37.4.13]) by mail3.custos.es (Postfix) with ESMTP id 4AB5C125EC2 for ; Thu, 1 Nov 2018 23:46:30 +0100 (CET) Received: from turing.b2n.org (unknown [10.64.3.2]) by plank.b2n.org (Postfix) with ESMTP id 5DC392D563 for ; Thu, 1 Nov 2018 23:46:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=b2n.org; s=dkim; t=1541112388; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rRK+0vaUk4Ob2hupdP5vNPT3fJTt4zeId2gucgEWIa0=; b=SyKL4bm0xzkLuR6t2bi/f6wdqrkM0AxtyBf4+a9wmglom/a1BIMoQSLKq32gUtckscvMuy 0RlqhI/VDEQRaFJdemr8YIo+NHGWRZIfkKeLGvWmDX+tf6O3C3xsGnS84ik7dQ7ze+p3vj fQcb/m6xJY4Eeyh+QmwBMxoAkSl7xMCep52vlVFhuCyxlo85BNeT2jDnhP+DO+VeqDtez1 UTXt+3x7Zifz/OaVmbdgoBt4VmDgDp4fxs2xCnTZjH2lme81xO/yjrWqiha6GeAMyo8Ayq LyAy1ELGfqsssN1ijK4kkoF3bM0k1v4thSuffttq2+MCXkkFlgmnXkeWp8GmCg== Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.b2n.org (Postfix) with ESMTPSA id 28BD5371B88 for ; Thu, 1 Nov 2018 23:46:26 +0100 (CET) Subject: SOLVED: 'loadable library and perl binaries are mismatched' rebuilding ports after upgrade to 12.0-BETA2 r339930 To: freebsd-stable@freebsd.org References: <7de5da1e-125c-1411-9398-433f09bfecd0@b2n.org> From: =?UTF-8?B?UmHDumw=?= Message-ID: <71e19279-9383-5749-5211-fb8166c39046@b2n.org> Date: Thu, 1 Nov 2018 23:46:10 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 01 Nov 2018 22:46:38 -0000 Hello Ronald, On 10/31/18 7:40 PM, Ronald Klop wrote: > What version of perl is being upgraded to what version? Same perl version, it was the OS from 11.2p4 to 12b2. As a list colleague suggested, the answer was in the portmaster man page. About the end of it says: 'Using portmaster to do a complete reinstallation of all ports' and worked perfect. Thanks for your interest. Raúl. From owner-freebsd-stable@freebsd.org Fri Nov 2 13:26:13 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15DEF10F64BE for ; Fri, 2 Nov 2018 13:26:13 +0000 (UTC) (envelope-from bounce-1472-23316020-656-248@txlntc.ga) Received: from bws.txlntc.ga (bws.txlntc.ga [45.79.19.180]) by mx1.freebsd.org (Postfix) with ESMTP id A58706A12F for ; Fri, 2 Nov 2018 13:26:12 +0000 (UTC) (envelope-from bounce-1472-23316020-656-248@txlntc.ga) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=txlntcga; d=txlntc.ga; h=Date:To:From:Reply-to:Subject:Message-ID:List-Unsubscribe:MIME-Version:Content-Type; i=newsletter@txlntc.ga; bh=Nqa5YtWFfKzoqfmwdmvnVk9xlws=; b=OepL6qWTRnC7zwIMGyNxsmulgAuvTdIiqDrn8qzBndFXrddxKuzo/vqYu50TYB4LdqGsQSAGWX3R TRYAC4mmpdPkCoFb+FAq21u6fS8ptzaYd/c89MJ2DQTmMPcRKuhsGkZAplUmxJ34AvyL2Zxb0Tn/ KqV6q7fJ30QD5TNPwTI= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=txlntcga; d=txlntc.ga; b=NwFnQ0u0oYR9zy+uDDrJppM6hAoHJZtYzzGfpf7YJZtnCuic36ip9LEnmoV22HJSjDBrrvpkN2oo inZD2F7R6LsB/Wmqm6DHSVLi5NJPhUgsE9uNOZ+N1h0eXNaX849Qh6H/eHrukzN+csGLtz+gYKph EhqfjGZ38Cjlxa1iDpc=; Received: by bws.txlntc.ga id hrh8780e97cg for ; Fri, 2 Nov 2018 13:26:12 +0000 (envelope-from ) Date: Fri, 2 Nov 2018 04:00:59 +0100 To: "freebsd-stable@freebsd.org" From: Discount Bags Reply-to: Discount Bags Subject: Today Best Handbag Deals! Michael Kors 70% OFF! Message-ID: <7bdf57e7d971be3b0a8c47a9e25d65ed@localhost> X-Priority: 3 X-Mailer: Email Sending System X-Complaints-To: anzhelanebjtc@go2.pl X-MessageID: N3x8fHwxMTQyOTR8fHx8ZnJlZWJzZC1zdGFibGVAZnJlZWJzZC5vcmd8fHx8M3x8fHwxfHx8fDA%3D X-Report-Abuse: MIME-Version: 1.0 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 02 Nov 2018 13:26:13 -0000 Today Best Handbag Deals! Michael Kors 70% OFF! Your email client cannot read this email. To view it online, please go here: http://bws.txlntc.ga/edmc/wb.php?p=3Drz/= rz/rs/2gym/rv/rs To stop receiving these emails:http://bws.txlntc.ga/edmc/u.php?p=3Drz/rs/2g= ym/rv/rz/rs From owner-freebsd-stable@freebsd.org Fri Nov 2 14:15:14 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1104D10F8598; Fri, 2 Nov 2018 14:15:14 +0000 (UTC) (envelope-from freebsd@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 6A6B06CD90; Fri, 2 Nov 2018 14:15:13 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id wA2EFCcF031131; Fri, 2 Nov 2018 15:15:12 +0100 (CET) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 00B5C1FC; Fri, 2 Nov 2018 15:15:11 +0100 (CET) To: FreeBSD Stable , FreeBSD SCSI From: Harry Schmalzbauer Subject: 12.0-BETA3 isp(4): exclusive sleep mutex CAM device lock (CAM device lock) Organization: OmniLAN Message-ID: <47f120a6-f032-de93-f5ff-9b32342df453@omnilan.de> Date: Fri, 2 Nov 2018 15:15:11 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Greylist: ACL 130 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Fri, 02 Nov 2018 15:15:12 +0100 (CET) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 02 Nov 2018 14:15:14 -0000 Hello, unnfortunately I can't determine if this is begnin, so I'd like to ask the experts: uma_zalloc_arg: zone "64" with the following non-sleepable locks held: exclusive sleep mutex CAM device lock (CAM device lock) r = 0 (0xfffff8000f1424d0) locked @ /usr/local/share/deploy-tools/RELENG_12/src/sys/cam/cam_xpt.c:4309 stack backtrace: #0 0xffffffff8060ead3 at witness_debugger+0x73 #1 0xffffffff8060fa48 at witness_warn+0x448 #2 0xffffffff808b6f18 at uma_zalloc_arg+0x38 #3 0xffffffff8058773a at malloc+0x9a #4 0xffffffff8036f423 at nvlist_create+0x23 #5 0xffffffff8030d597 at ctl_port_register+0x187 #6 0xffffffff8031aa25 at ctlfeasync+0x405 #7 0xffffffff802ca772 at xpt_async_process_dev+0x162 #8 0xffffffff802c603d at xpt_async_process+0x15d #9 0xffffffff802c697e at xpt_done_process+0x35e #10 0xffffffff802c8a76 at xpt_done_td+0xf6 #11 0xffffffff8056e094 at fork_exit+0x84 #12 0xffffffff808f46de at fork_trampoline+0xe uma_zalloc_arg: zone "64" with the following non-sleepable locks held: exclusive sleep mutex CAM device lock (CAM device lock) r = 0 (0xfffff8000f1414d0) locked @ /usr/local/share/deploy-tools/RELENG_12/src/sys/cam/cam_xpt.c:4309 stack backtrace: #0 0xffffffff8060ead3 at witness_debugger+0x73 #1 0xffffffff8060fa48 at witness_warn+0x448 #2 0xffffffff808b6f18 at uma_zalloc_arg+0x38 #3 0xffffffff8058773a at malloc+0x9a #4 0xffffffff8036f423 at nvlist_create+0x23 #5 0xffffffff8030d597 at ctl_port_register+0x187 #6 0xffffffff8031aa25 at ctlfeasync+0x405 #7 0xffffffff802ca772 at xpt_async_process_dev+0x162 #8 0xffffffff802c603d at xpt_async_process+0x15d #9 0xffffffff802c697e at xpt_done_process+0x35e #10 0xffffffff802c8a76 at xpt_done_td+0xf6 #11 0xffffffff8056e094 at fork_exit+0x84 #12 0xffffffff808f46de at fork_trampoline+0xe Thanks for hints, -harry From owner-freebsd-stable@freebsd.org Fri Nov 2 15:02:23 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24F2F10FA4ED; Fri, 2 Nov 2018 15:02:23 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 C31696FA24; Fri, 2 Nov 2018 15:02:22 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D9B0C223AD; Fri, 2 Nov 2018 11:02:21 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Fri, 02 Nov 2018 11:02:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=v tDMjmfMOIE7wMNrzwj6mw6BgpccGA6QGunh3rZjMJ8=; b=Y3SZb0NT0tRRX22dL 2jGyvb7Sxwj5NYJUngt394csqNHrFE6LzthPzmB1/F+ekrOXM7ynkScgWt1uanpE dT0S4cyYYRzs73Oz1jhU+iIDeDqw28BisTdAjkwwFFQEKnWVGgubqRZ8LwtJTkoq 5gPh8kOz+l8ceSQRO1PbxPxtRWEMB/H4PlQa9fBiA9A/6MJ+XqAbxiMv9KMOtuSG /PECP4v4ElFyEBZbHTt7HaSD2QgKlfqHtWb0qImCrKNtBGZrPfrCHSnxrOEAUyRd dmvDQdIP5nV3OhTR1msG9UUH9l5abd8e1NXwpc8iYzuBg05krWhEQPzHegUNKTJk EbsZA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=vtDMjmfMOIE7wMNrzwj6mw6BgpccGA6QGunh3rZjM J8=; b=S4xWQJjjQ6igQ3C8qOA1jZDNhK3gENX06XVDBUFAU0UMI1dSk45BTuYkV bSj190VrJyWrEB382N8aqdfWVa2TChwHoQPZ0so8mCmyPtCllH7biGnzFAm61/XZ aS4zXdPL0afSW86sdC6crxvf5pD85Dnsg953Mkyk6MIpjV0xk8ubiGogNUCjL0Hr +HMENmWPc5lg2OUbOh/hazWCsoxU16jFrwUDfRwqttcAU3K+bYC3gvwZB0L0ngNC 9EGyl33uzsRTiOAVUr9X/IEvq4cPPR0eOyjAVG0Plwi1zBmFrtL+s9s2xUpCGmyw 2OQVauoeapOZo2pOa3xpSWow1kyyw== X-ME-Sender: X-ME-Proxy: Received: from [192.168.0.116] (unknown [161.97.249.191]) by mail.messagingengine.com (Postfix) with ESMTPA id 31E22103E5; Fri, 2 Nov 2018 11:02:20 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: 12.0-BETA3 isp(4): exclusive sleep mutex CAM device lock (CAM device lock) From: Scott Long In-Reply-To: <47f120a6-f032-de93-f5ff-9b32342df453@omnilan.de> Date: Fri, 2 Nov 2018 09:02:16 -0600 Cc: FreeBSD Stable , FreeBSD SCSI Content-Transfer-Encoding: quoted-printable Message-Id: <674B7523-839F-4B0C-A333-D27057687A65@samsco.org> References: <47f120a6-f032-de93-f5ff-9b32342df453@omnilan.de> To: Harry Schmalzbauer X-Mailer: Apple Mail (2.3445.100.39) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 02 Nov 2018 15:02:23 -0000 It=E2=80=99s harmless unless you run your machine under severe and = sustained memory exhaustion. Scott > On Nov 2, 2018, at 8:15 AM, Harry Schmalzbauer = wrote: >=20 > Hello, >=20 > unnfortunately I can't determine if this is begnin, so I'd like to ask = the experts: >=20 > uma_zalloc_arg: zone "64" with the following non-sleepable locks held: > exclusive sleep mutex CAM device lock (CAM device lock) r =3D 0 = (0xfffff8000f1424d0) locked @ = /usr/local/share/deploy-tools/RELENG_12/src/sys/cam/cam_xpt.c:4309 > stack backtrace: > #0 0xffffffff8060ead3 at witness_debugger+0x73 > #1 0xffffffff8060fa48 at witness_warn+0x448 > #2 0xffffffff808b6f18 at uma_zalloc_arg+0x38 > #3 0xffffffff8058773a at malloc+0x9a > #4 0xffffffff8036f423 at nvlist_create+0x23 > #5 0xffffffff8030d597 at ctl_port_register+0x187 > #6 0xffffffff8031aa25 at ctlfeasync+0x405 > #7 0xffffffff802ca772 at xpt_async_process_dev+0x162 > #8 0xffffffff802c603d at xpt_async_process+0x15d > #9 0xffffffff802c697e at xpt_done_process+0x35e > #10 0xffffffff802c8a76 at xpt_done_td+0xf6 > #11 0xffffffff8056e094 at fork_exit+0x84 > #12 0xffffffff808f46de at fork_trampoline+0xe > uma_zalloc_arg: zone "64" with the following non-sleepable locks held: > exclusive sleep mutex CAM device lock (CAM device lock) r =3D 0 = (0xfffff8000f1414d0) locked @ = /usr/local/share/deploy-tools/RELENG_12/src/sys/cam/cam_xpt.c:4309 > stack backtrace: > #0 0xffffffff8060ead3 at witness_debugger+0x73 > #1 0xffffffff8060fa48 at witness_warn+0x448 > #2 0xffffffff808b6f18 at uma_zalloc_arg+0x38 > #3 0xffffffff8058773a at malloc+0x9a > #4 0xffffffff8036f423 at nvlist_create+0x23 > #5 0xffffffff8030d597 at ctl_port_register+0x187 > #6 0xffffffff8031aa25 at ctlfeasync+0x405 > #7 0xffffffff802ca772 at xpt_async_process_dev+0x162 > #8 0xffffffff802c603d at xpt_async_process+0x15d > #9 0xffffffff802c697e at xpt_done_process+0x35e > #10 0xffffffff802c8a76 at xpt_done_td+0xf6 > #11 0xffffffff8056e094 at fork_exit+0x84 > #12 0xffffffff808f46de at fork_trampoline+0xe >=20 > Thanks for hints, >=20 > -harry >=20 > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to = "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Fri Nov 2 16:34:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7473910FCA6D for ; Fri, 2 Nov 2018 16:34:38 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E56A739BD; Fri, 2 Nov 2018 16:34:38 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id AB4FB1552; Fri, 2 Nov 2018 16:34:37 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Fri, 2 Nov 2018 16:34:35 +0000 From: Glen Barber To: Masachika ISHIZUKA Cc: freebsd-stable@freebsd.org, re@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available Message-ID: <20181102163435.GU81143@FreeBSD.org> References: <68e4423a-218a-2912-2fe2-f834c7124f6f@codelibre.net> <20181030.010424.17654226369780713.ish@amail.plala.or.jp> <20181029160755.GQ75350@FreeBSD.org> <20181101.112614.410204338792675244.ish@amail.plala.or.jp> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="a6Ri6/t33sscKOaw" Content-Disposition: inline In-Reply-To: <20181101.112614.410204338792675244.ish@amail.plala.or.jp> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 02 Nov 2018 16:34:38 -0000 --a6Ri6/t33sscKOaw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 01, 2018 at 11:26:14AM +0900, Masachika ISHIZUKA wrote: > >> Although it said that we could not upgrade to 12.0-BETA1 in > >> the previous release note, we can upgrade to 12.0-BETA1 by > >> freebsd-update. > >> And at this moment, we cannot upgrade to 12.0-BETA2 by > >> freebsd-update. > >=20 > > Sorry, I forgot to reply to your original report. This is being looked > > into. It is, unfortunately, more fallout from updating OpenSSL to > > version 1.1.1. >=20 > Thank you for reply and your efforts. >=20 > Now, freebsd-update can upgrade 12.0-BETA2 amd64. > I confirmed from both 11.2-RELEASE-p4 and 12.0-BETA1. >=20 > Note that freebsd-update install dose not execute pwd_mkdb, we > must execute 'pwd_mkdb -p /etc/master.passwd 'manually if we use > ntpd. Could you please open a PR about this, and add cperciva@ to the CC list? Glen --a6Ri6/t33sscKOaw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlvcfJsACgkQAxRYpUeP 4pMMIhAAk/cOYPY/vKthLTf4r1gdJhndsEj671QYqCRtUi+cr4ZU50dPm2QQCAyI xJNlqu24hS1sUWXqwJdmqQaf0xefiPe5Jc9MBlCjInXvbXXT2TsT5fjeh8epbkO+ 8TnZoogfqn8U2RZDD7usTprjI8qNdbP5EveIxr0iMlaSgaZD10sM/GIpKH81ceDb 1gyAwgzFbLtviS2STTEpuZTA0FSDD01NFtXzqQA37p1togf9GIG40T+9OkbmGjlW qgoBTxMCzk384VxES5RFORYrgS9ws19iv0xPCJq3Yw03W8sdu6cCc4qQKEIz/rN3 FKD/6eYmBjnmAA9e+BNCoedFPkqcpAE9vNC1OjRBe1NsvVNFKee54VxCZNFnzEby Oy4dHEVIxkxvNVaybPdL77cnDUS9FdsEnSf3Z/bmnBb7gsFOzlI93XNqWNUGyhCn LJXsqC2FqvdXON6G0ANUfrY1nqV54VZOs4oLiW6p0wry5TS/AkHdBIQIGqmn66Dv cEjMcFJQyJlK0E7TTY3JILC5ZjMIYf3VrJdDf3Ng7pyO//CtgWhxuefh1Z+0sb2/ kEx4ux+oRDVNJSCz/7AqASpLEy2BwJ6tNpM3RfdkN1Xc9PCySx0xdYmYMGFqLhSt u3+UDliYZg1PH9OWb46X7rdrGQvHVWTNYabcj/7dv8CaM1j2wFI= =XyPE -----END PGP SIGNATURE----- --a6Ri6/t33sscKOaw-- From owner-freebsd-stable@freebsd.org Sat Nov 3 00:30:58 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12EE410E051F for ; Sat, 3 Nov 2018 00:30:58 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc11.plala.or.jp (msc11.plala.or.jp [60.36.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id 022C386639; Sat, 3 Nov 2018 00:30:56 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc11.plala.or.jp with ESMTP id <20181103003045.VQC13862.msc11.plala.or.jp@localhost>; Sat, 3 Nov 2018 09:30:45 +0900 Date: Sat, 03 Nov 2018 09:30:35 +0900 (JST) Message-Id: <20181103.093035.2017538878039144864.ish@amail.plala.or.jp> To: freebsd-stable@freebsd.org Cc: re@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available From: Masachika ISHIZUKA In-Reply-To: <20181102163435.GU81143@FreeBSD.org> References: <20181029160755.GQ75350@FreeBSD.org> <20181101.112614.410204338792675244.ish@amail.plala.or.jp> <20181102163435.GU81143@FreeBSD.org> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac11; Sat, 3 Nov 2018 09:30:45 +0900 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 03 Nov 2018 00:30:58 -0000 >> Note that freebsd-update install dose not execute pwd_mkdb, we >> must execute 'pwd_mkdb -p /etc/master.passwd 'manually if we use >> ntpd. > > Could you please open a PR about this, and add cperciva@ to the CC list? I opened PR 232921 and added cperciva@ to the cc list. -- Masachika ISHIZUKA From owner-freebsd-stable@freebsd.org Sat Nov 3 00:36:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6D6210E0C81 for ; Sat, 3 Nov 2018 00:36:52 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F4D386B67; Sat, 3 Nov 2018 00:36:52 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 31AAC9F35; Sat, 3 Nov 2018 00:36:52 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Sat, 3 Nov 2018 00:36:49 +0000 From: Glen Barber To: Masachika ISHIZUKA Cc: freebsd-stable@freebsd.org, re@freebsd.org Subject: Re: FreeBSD 12.0-BETA2 Now Available Message-ID: <20181103003649.GW81143@FreeBSD.org> References: <20181029160755.GQ75350@FreeBSD.org> <20181101.112614.410204338792675244.ish@amail.plala.or.jp> <20181102163435.GU81143@FreeBSD.org> <20181103.093035.2017538878039144864.ish@amail.plala.or.jp> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2tWkrNKppd65XSnD" Content-Disposition: inline In-Reply-To: <20181103.093035.2017538878039144864.ish@amail.plala.or.jp> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 03 Nov 2018 00:36:53 -0000 --2tWkrNKppd65XSnD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 03, 2018 at 09:30:35AM +0900, Masachika ISHIZUKA wrote: > >> Note that freebsd-update install dose not execute pwd_mkdb, we > >> must execute 'pwd_mkdb -p /etc/master.passwd 'manually if we use > >> ntpd. > >=20 > > Could you please open a PR about this, and add cperciva@ to the CC list? >=20 > I opened PR 232921 and added cperciva@ to the cc list. Thank you. Glen --2tWkrNKppd65XSnD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlvc7Z0ACgkQAxRYpUeP 4pP7NA/+PPf+gXdNh1Rs0u0uMnPJ+cUs9du+dP5qZOnHGyfkMRicVe5dKVs2Et7m fY0TFI790yN0M6UFJXxoRm9bGsc5MfOpSzC+K4KEltRnMYuRAAn51mgjBJjaHEUv 7PCAJMfqQTVSrucBzpqeUr0kVHlMR5mxadwnAxWz04SbKKyHd4cFAQG9bXSheWHd QPJoJWTj50os0GtGJpmhLxPz2/ELWYi0t7SQLffir+8mEPOmYrww78++nY87CJgX 5Ztfy4qSfGpuhzO1lKRtwE//gG341TzwLNsiP4rT5fIdOuV1rmm5M/+2Fq7i6A3o rgTLsgI/efA3CsUiUbtKvCBsLOkRU0j186yipmGm856KNqs4TMmTVIvD8gkffjA/ FIANL7ka5O17CYKtmTulxPVrAyp7JjGlOAypAGtJ/VdfZw0wRjDUG/kGMZYfEbCG Ej907eMv1GR3TCwUlMqfLgjgwUeYVIjtm86AoVjt/7WS3I42tMYFQ1M08PwRC4k5 nwVsV/k/IZH8hPTab8NZ5VIldufbn0IQ1pbmgsGoPWJ9Ol2i7mviEucDiVTUbYdz BarDdx1CcdhywP4xDttvceoK7foHl3boDoCAOqfGDkYiCNFwA9+57t0XJENwox74 AEGUyEwbsd+MPkUwRAGH7W/hjOkMQ0oKk0ZadlByZkNt0vq82Q8= =Le7j -----END PGP SIGNATURE----- --2tWkrNKppd65XSnD-- From owner-freebsd-stable@freebsd.org Sat Nov 3 17:50:01 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E430410DF882; Sat, 3 Nov 2018 17:50:00 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CAD18BA96; Sat, 3 Nov 2018 17:50:00 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 4B9E01651C; Sat, 3 Nov 2018 17:50:00 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Sat, 3 Nov 2018 17:49:58 +0000 From: Glen Barber To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 12.0-BETA3 Now Available Message-ID: <20181103174958.GW45661@FreeBSD.org> Reply-To: FreeBSD Release Engineering Team MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 03 Nov 2018 17:50:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The third BETA build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-BETA3 amd64 GENERIC o 12.0-BETA3 i386 GENERIC o 12.0-BETA3 powerpc GENERIC o 12.0-BETA3 powerpc64 GENERIC64 o 12.0-BETA3 sparc64 GENERIC o 12.0-BETA3 armv6 RPI-B o 12.0-BETA3 armv7 BANANAPI o 12.0-BETA3 armv7 BEAGLEBONE o 12.0-BETA3 armv7 CUBIEBOARD o 12.0-BETA3 armv7 CUBIEBOARD2 o 12.0-BETA3 armv7 CUBOX-HUMMINGBOARD o 12.0-BETA3 armv7 RPI2 o 12.0-BETA3 armv7 PANDABOARD o 12.0-BETA3 armv7 WANDBOARD o 12.0-BETA3 armv7 GENERICSD o 12.0-BETA3 aarch64 GENERIC o 12.0-BETA3 aarch64 RPI3 o 12.0-BETA3 aarch64 PINE64-LTS Note regarding arm SD card images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.0/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the "stable/12" branch. A summary of changes since 12.0-BETA2 includes: o SPE exception handling was implemented for the powerpcspe architecture. (Note, the powerpcspe build failed for BETA3 for reasons unrelated to source code changes, and is being investigated). o The localedef(1) utility was updated to add '-b' and '-l' options to specify output endianness, and now used when building share/ctypedef and share/colldef. (PR 231965) o The uplcom(4) driver has been updated to add support for formula-based arbitrary baud rates. (PR 225932) o The cxgbe(4) driver has been updated to use automatic cidx updates with ofld and ctrl queues. o Backwards compatibility for the geli(8) 'attach' subcommand has been added, allowing older geli(8) binaries to attach newer geli(4)-backed devices. (PR 232595) o The timezone database files have been updated to version 2018g. o Bhyve has been updated to allow the VNC server to listen for incoming IPv6 connections. (PR 232018) o Various fixes and updates to lualoader. o NUMA support can now be disabled via sysctl(8) by adding vm.numa.disabled=1 in loader.conf(5). o And various other miscellaneous fixes. A list of changes since 11.2-RELEASE is available in the stable/12 release notes: https://www.freebsd.org/releases/12.0R/relnotes.html Please note, the release notes page is far from complete, and will be updated on an ongoing basis as the 12.0-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): https://download.freebsd.org/ftp/releases/VM-IMAGES/12.0-BETA3/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 135 MB and 165 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI loader file is needed for qemu-system-aarch64 to be able to boot the virtual machine images. See this page for more information: https://wiki.freebsd.org/arm64/QEMU To boot the VM image, run: % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ -bios QEMU_EFI.fd -serial telnet::4444,server -nographic \ -drive if=none,file=VMDISK,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -device virtio-net-device,netdev=net0 \ -netdev user,id=net0 Be sure to replace "VMDISK" with the path to the virtual machine image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: ap-south-1 region: ami-0b11f11c62b62b89a eu-west-3 region: ami-0b0fcc030402e10d6 eu-west-2 region: ami-0192397e78f5895ca eu-west-1 region: ami-0db8552914f93ae8c ap-northeast-2 region: ami-0baa216e14b3d5ec8 ap-northeast-1 region: ami-0c7a27bd048ba2d42 sa-east-1 region: ami-0d063602355a4f1bd ca-central-1 region: ami-032a9eb595f2244d3 ap-southeast-1 region: ami-039dcb5c7817c27a0 ap-southeast-2 region: ami-0ca61f5d0b3c6ce5b eu-central-1 region: ami-02ef27d661779d0a8 us-east-1 region: ami-07380393ea7dc9ad3 us-east-2 region: ami-031c7e040e277b3d4 us-west-1 region: ami-016204e250b5a864f us-west-2 region: ami-01f0894333d0750ed === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-12.0-BETA3 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 12.0-BETA3 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 11.x. Alternatively, the user can install misc/compat11x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 12.0-BETA3 amd64 GENERIC: SHA512 (FreeBSD-12.0-BETA3-amd64-bootonly.iso) = dba456a06061b6a89ef23fc9607e9cc6ee63b79c7c2eda1b43b8a9ec3c35e8714fc66c0b0083b99b3cf78e2554fe89c43135bcfbe030dd43168541da368cf35f SHA512 (FreeBSD-12.0-BETA3-amd64-bootonly.iso.xz) = 70d295a4e4a201f032055e305a42da51b49f6366c74a4da8c952584c55a7f3e47c83de372aaf80553978e028dfab5a44745d82a06646de8bc4d0989c0d9197e9 SHA512 (FreeBSD-12.0-BETA3-amd64-disc1.iso) = 8e31c46116745f1ebd148bb339b380953e7ea7e1ae9e60b37f1cbc8107ab196fe5378a4045f827f8acb3bc81026904c58e3a16f4ac8c1fae2018d7e2231e1b3d SHA512 (FreeBSD-12.0-BETA3-amd64-disc1.iso.xz) = fd34e90dc5a18a198296126d1f382ac4078591a8b5dd36a9e7bb131dedfe7a461e5098d83df79ddd36e7f635369888959f7db35831404be78ea50adf8f4f38d8 SHA512 (FreeBSD-12.0-BETA3-amd64-dvd1.iso) = 93142ea933bd85926d60e1f3ef7a5643cff205a915f39326ce9f03dce2e8abe80952afcc79c840dd678d7b1306260109afd65db66e05886e11cc8f70278b25bd SHA512 (FreeBSD-12.0-BETA3-amd64-dvd1.iso.xz) = 0a247c6d73e51b52dad134e84cbda3ab8b1a2b90e7e8a06dae1485d8b199a30e3800ffd89c37041d62d5a2e0ad0873951b36cf3ce85a3106b0b11ea6050606e0 SHA512 (FreeBSD-12.0-BETA3-amd64-memstick.img) = 504856f2af4d42c7248dae8da306ba4de0ea47dd0376e6c22a4ce807201917ab529810358f1ee48ae3e333854bfeb1e2d60e5deff354f19337670b7518e2085c SHA512 (FreeBSD-12.0-BETA3-amd64-memstick.img.xz) = f6a357ba049c3b83b3f4b0122ce25bf1fee305c6d963061624db57ea7e50897e2fad6af50b1b39798f0ef03ea250584bfab33e9d833a025224a018745fd8ada5 SHA512 (FreeBSD-12.0-BETA3-amd64-mini-memstick.img) = 47a6f3b26500eda2de3574e1c88172caf8e1f951f1623a235cab1fe81e9f8e342541ac4000b05d444500883af6a69e6387cf87204ae06475c31f9ef168d923ef SHA512 (FreeBSD-12.0-BETA3-amd64-mini-memstick.img.xz) = a937355ed35e96fe7bf4f8972c676b6dba13a1b4ef9697ea63b33f3248fd4d64e905efd36e5f8c6e2ec624301589ba5dc54d6accb745c06776f69d6cb62359ac SHA256 (FreeBSD-12.0-BETA3-amd64-bootonly.iso) = a43fc3ed684066588c9bef2d08911f52554d6234300449be6737cb86e9f152ad SHA256 (FreeBSD-12.0-BETA3-amd64-bootonly.iso.xz) = 4ef3e4ce656b3499856f1df70bdbc9ed26580f6f9c4ec26532881e909b83f8f3 SHA256 (FreeBSD-12.0-BETA3-amd64-disc1.iso) = 5fe350bd57afe840b0c9ad3cc67e346ff139735349d1ae58844dff7dc0b39a63 SHA256 (FreeBSD-12.0-BETA3-amd64-disc1.iso.xz) = 5e46e24a784b5cf664de1dc3e04c64aaceec095548d92fa8932fbc69aba6385a SHA256 (FreeBSD-12.0-BETA3-amd64-dvd1.iso) = 74404e40ea8099a5bfef78a37b0bcce9fa1c750cefd01e4791e9c21464b1dc95 SHA256 (FreeBSD-12.0-BETA3-amd64-dvd1.iso.xz) = e919b2bc7a129fca5c533cf331c6a34909a9444289f0164b3f43d61e45992950 SHA256 (FreeBSD-12.0-BETA3-amd64-memstick.img) = c84eef15b1455720ca86d8bcd8e63733a1f0d09b0095ae5d86c1d0b0965c262a SHA256 (FreeBSD-12.0-BETA3-amd64-memstick.img.xz) = 17c4ff9c58a034182910dd0141da45bfe688669095d72d96a327f3ae239bd83b SHA256 (FreeBSD-12.0-BETA3-amd64-mini-memstick.img) = 0d921094f64c5f5ad44a4f8eab66d5525f2362fac1ee67d54c3d4088bf30054b SHA256 (FreeBSD-12.0-BETA3-amd64-mini-memstick.img.xz) = 547cc5f5975dbf98ae2d2de9dd9d48d7c193346dabeb3b8f726cb69d4fd9c5c3 o 12.0-BETA3 i386 GENERIC: SHA512 (FreeBSD-12.0-BETA3-i386-bootonly.iso) = a82c2cc8a426cbc7f3fb8470c1e407911c25f902a4394d2bf346deeb647ed466aabbb57b0f457bb0e2a5f15a4aeaa45c3fb6010df3befb7ea4275c3d9d9f8ca2 SHA512 (FreeBSD-12.0-BETA3-i386-bootonly.iso.xz) = de7c6b365de1f41621d7ec24b430e6ccc4f37d1c551a9370838cd3bc579113ba89731f87734a90fa5bfb802bc54f277063994f92e1e0569ed9966d672dc1d7c9 SHA512 (FreeBSD-12.0-BETA3-i386-disc1.iso) = 3529dcd8b33b10ac0a52315b5b7a2ed4c32054d61246748668e159b468045382146b080318c5234b4aa698d6fae2cedf6322d2e5e76c604ea3f31408f63a7fb2 SHA512 (FreeBSD-12.0-BETA3-i386-disc1.iso.xz) = 607596710acf0a907f3ae808e59c3e658afb28e2bc8e07ff0d3e65c7f9e9597667b23445eecff5bb5f4cd7d5b5ad8cf15eead1cbbd0aa789ef57a512ddbbd581 SHA512 (FreeBSD-12.0-BETA3-i386-dvd1.iso) = 4eec3e39111d11df7ac00afe59c46f6c96ae28e3fdce7932afb04aacea221a7bae2a5856cb8ea6e2137e7e22c9c788af48b7ec5bf185dc3342d5f55e09686b13 SHA512 (FreeBSD-12.0-BETA3-i386-dvd1.iso.xz) = af71583f999086548bf53b10edd1f191f60a6971a5f8ae2796d99b1658693180e20671a606dc08382e07b10f027109db8bccaf0d64a475381e4ad579bddb7347 SHA512 (FreeBSD-12.0-BETA3-i386-memstick.img) = 7fa31db1712e32c0af73ab3369b3a55c8d31986d88a131738c8637cdf41a8aae6b2c3b442739094bd616479351dfd599b54cb57f36a116733dc730f687fe5b65 SHA512 (FreeBSD-12.0-BETA3-i386-memstick.img.xz) = b08c499d444157cf4ea045e3913deee1b10cce61579fe33f32e3f697e3299849ab54fe8f3a6acd4223ad896d6507377ae01c55479548be5a717a169e1060f75d SHA512 (FreeBSD-12.0-BETA3-i386-mini-memstick.img) = 3c6065fdeef74633062732029e679afbb92cb02554bc75503f8751949826205c2c51b96fda1af77985087da1135a9bee190c12942a717ad7980e5ae99cf7f840 SHA512 (FreeBSD-12.0-BETA3-i386-mini-memstick.img.xz) = a23ef548abc9e6334f8a1ad0e747172c93edbdc381d4c0cec519b0b66f0ab3e7f61c439f15c47ba99de48de51c0222a4d560152d57d063ab7a5846906586caef SHA256 (FreeBSD-12.0-BETA3-i386-bootonly.iso) = ce124d92e10a2d8b5fa339fab9492b8e76bd3a0314cacbadaa7bb09e8ddacd8b SHA256 (FreeBSD-12.0-BETA3-i386-bootonly.iso.xz) = e04e23a1ac5772a2ff79ac9d94ef512d38eb0f15e650b8281e15fb27dc9e9b75 SHA256 (FreeBSD-12.0-BETA3-i386-disc1.iso) = 8e783402e25c39861df40ec73cef51b1cb0fc1c51225e4f7c667d444765f98c8 SHA256 (FreeBSD-12.0-BETA3-i386-disc1.iso.xz) = cd86f49388919f1acefa610dfd51459f6b91abff1ea0e00167aaf9d17056b453 SHA256 (FreeBSD-12.0-BETA3-i386-dvd1.iso) = 3f5a6f47f84666511ca7484ce4162b570b6ccc141ecebcc21dd1001b272b4dee SHA256 (FreeBSD-12.0-BETA3-i386-dvd1.iso.xz) = 6acf3ba79b2d73298b81dad62de0f8e5fe7a9d118eaa27c6f7b4848dfb66e910 SHA256 (FreeBSD-12.0-BETA3-i386-memstick.img) = 1de52cf5c25b32edd16aa3a2065d73dce5ca5b1b941e0508dfa62762dafcf912 SHA256 (FreeBSD-12.0-BETA3-i386-memstick.img.xz) = 730fe89f3d6acddc52f0b2981fb9feb11add8fad62c380bd2aa206a02e81d0ad SHA256 (FreeBSD-12.0-BETA3-i386-mini-memstick.img) = f8142f710a466567058712f175b4388812547aa2e273028e4cb1cdae4fc2f6b3 SHA256 (FreeBSD-12.0-BETA3-i386-mini-memstick.img.xz) = 562575c10899f560a2dac9483b0e15aff34becb91a730071115e5ca628b2ffdb o 12.0-BETA3 powerpc GENERIC: SHA512 (FreeBSD-12.0-BETA3-powerpc-bootonly.iso) = fbd06682ab3f5fbc64b2000de34bc217f2b5c79d86fa19c152dfd9788378016a6bd93eddb9b809cb2c79c2ff1bcb0c3cb8b0272fe61919692a1e863686d22f32 SHA512 (FreeBSD-12.0-BETA3-powerpc-bootonly.iso.xz) = 3291bfb73972e1189b307167922beafbfa16828fc289b6ee4e570fc98bd46cfa6dc99f0227c8cc305fca26cd7237f1285ba6bb47c48d0750f336bba74eb9828b SHA512 (FreeBSD-12.0-BETA3-powerpc-disc1.iso) = c263c381db5b5c5b7d2ec57bbe90d548b4b66d1590c1709ccd57eacd69ce8077406e69b306588e703b6384883cef1d952cb724ec960a0a87f3833fdb6abf6145 SHA512 (FreeBSD-12.0-BETA3-powerpc-disc1.iso.xz) = fd923e912e0aad61dedbd0357fd89a966de1eb9ae8a0b43f462ff50a437a8caab2ababe4929ab42c93e9ebc7e58f4d8bb537b435386b2bc971fa33d7b10de3d6 SHA512 (FreeBSD-12.0-BETA3-powerpc-dvd1.iso) = e4f10d31305cd7585cc428ff1c3005a950322379dffd5f720bb800a456f67f1e56a99fab01d87c21e521a368b001e7e3a45d01baa667bc64c3fa9a466d0113df SHA512 (FreeBSD-12.0-BETA3-powerpc-dvd1.iso.xz) = 1b0b60e924e92a881d3721af27046335909108590dd19ca393586b3d3f7dcd46bac81641a594d2f7284f55523e4f20bfaf850d2cab9492fb03436487552d8507 SHA512 (FreeBSD-12.0-BETA3-powerpc-memstick.img) = 240ffe0955a3780c273ff2ec0e46fd71cb69c173c2bc96d9f7febc17056cd19a3a18bbeb50f2edbaf14252ca6cbd1f6b59070ceab53192f94e1792b6d31a4b5c SHA512 (FreeBSD-12.0-BETA3-powerpc-memstick.img.xz) = 4eb15a24ca7d6126f0705b2e2d3b338714ef80dd1ace3d9c7f90b2731f6eb596e5241ef54ba717b6db196c1daff429416936ad2341f13dc302976df49e408c2f SHA512 (FreeBSD-12.0-BETA3-powerpc-mini-memstick.img) = 9b75b1c007971a56d943bc50535c39ecb4f79cf6bcca71a0cf5210b47eb1b50f6aafc1e71a14fe842475ed9afb02daa38b974348d172f3462177862d1d28eca3 SHA512 (FreeBSD-12.0-BETA3-powerpc-mini-memstick.img.xz) = 9138020f77539e286d712baa5bdd9649c4097b6523fefbe92ddb73c1d58914c90c22a2f7e4234756616d528826395292c3ed101f4dd3fa399f9b213b5336dedb SHA256 (FreeBSD-12.0-BETA3-powerpc-bootonly.iso) = 41bb438f7306e466c3bef4a7114c93fa195da6ba47a4a5fe208fecf5f213c88d SHA256 (FreeBSD-12.0-BETA3-powerpc-bootonly.iso.xz) = 0dffc3d1c38a6060582dec7d7d3105c2125454e2c7c81266d15d25582b7d9f07 SHA256 (FreeBSD-12.0-BETA3-powerpc-disc1.iso) = e00757accbde7fc126372575736563d6266bcde8bd2169c7bb6458841b686e22 SHA256 (FreeBSD-12.0-BETA3-powerpc-disc1.iso.xz) = 5053ec57cddd5fd9bcec8ed62bb0404f95839bf571b945e70e04c0c48a456e38 SHA256 (FreeBSD-12.0-BETA3-powerpc-dvd1.iso) = d4e72276ad0283bf5fca8e0401258c04d92dc38ad55c8ff15adc4ebee418fc50 SHA256 (FreeBSD-12.0-BETA3-powerpc-dvd1.iso.xz) = 93eefd111c14199d9bd7861e397e4fb5cadc7fbd8e7425fd3998e7f8ffd83570 SHA256 (FreeBSD-12.0-BETA3-powerpc-memstick.img) = ab7f855a2ba7d1571c9e2ea8a1d51e3890880aa4ef4929dc5ec4a77f76f4e7ba SHA256 (FreeBSD-12.0-BETA3-powerpc-memstick.img.xz) = f1ebf56c66de5e323f7f8cc3c6c682d0226af2dab9da2d4b1c18f4249476be0d SHA256 (FreeBSD-12.0-BETA3-powerpc-mini-memstick.img) = f6629a700ef2e6e5c5d863797ee8c1e7fc3445cfb5a5985310e57e338c2e572c SHA256 (FreeBSD-12.0-BETA3-powerpc-mini-memstick.img.xz) = e2e247c99851256ed4888fab3557aea84c5fa897997ab68c0fe56d8709b23199 o 12.0-BETA3 powerpc64 GENERIC64: SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-bootonly.iso) = e837d56674ac61b2a56fdb42fe51546dccd3cce9f550d99f7095fda0f02bd90e0f9c39f528ba6d2f62ef7b8218e2a3f37e95864c307a89e1517e70725c0e9f7c SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-bootonly.iso.xz) = 3cb9279cdac6b67da34421132757751bb24e21211f7b9f53962bfffc9c3d7758757c9cdeb3a5e88bf46a0e613eb3e2f344bfa577196fa945a24a35e1be03b650 SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-disc1.iso) = 8420a8e98591bbfaf0a91e1bc7c759524701ca0af02a96508b1ef86618c9098b6078dc832eedbc02c8c0b4859d433cecd079e917b15afc20647f09e62f1c8bcf SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-disc1.iso.xz) = 261d3fd6fed70dd8515bcdc967ca06ee9c1d860961f53b9340a9f417190b702721bf71722afb91366543d282827cab9a579c72d265ef3d8567d6ed58835967c8 SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-dvd1.iso) = d66c10064c5d9caa521ee95e179ef7e733b584a082e8d43b7be655bba88ee97735f0a1b4b6c156120fe044fce9bc6f3ac77f758d4855e6f20bff731ad8eee32c SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-dvd1.iso.xz) = bd0df0451071a63239f545f34431f3172d8ed6664dbf834fed437664efffd7c4cbfbb77ba1dae8eec18e9198ec93826e97a0bdc08fb025de8192b995c7e291eb SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-memstick.img) = 2e37fab75b69cc798c5aa929ed435da4cd8fb122e0b7091a642449ff5e5975f7f04818c02830f83a25dd7aeb1cb7ba47d13b197e029e485ab0d6cf39f19d3121 SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-memstick.img.xz) = ee009b862569b987dd9332fb1227c0e26c0644bffbf99e9c8145553ff0bb4981331d4bdcdc4f96cf46ade6df95f6d58be345a1bbb9d3b1c38ea6b7b24f4a517d SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-mini-memstick.img) = fd48abd674b041acbf817930c580a533b7d4c512b9c5814af5baef157d4e00fb0cc285daeb6d1f44de132d7f0535d97ff7f19af2a3f1a8878f72870a07ec0053 SHA512 (FreeBSD-12.0-BETA3-powerpc-powerpc64-mini-memstick.img.xz) = 7d9e87b0251b6fd393cd38a753032903b9477b19de72c65d6a74eb6722f8a8b4b529d16dc44ffc1e38b58fdaeae13347cf215bb4868b5aace5726974a8f8594c SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-bootonly.iso) = 3d1348fc7b1a1d2597c5105097edb117dc3a102ecdcde73f2679784dc3351e76 SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-bootonly.iso.xz) = 139a3c9d93f1954c671a7612da5b7f09511d36d868d9b046159f815b31bca18d SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-disc1.iso) = 3792281207298a3e5e470e9fe362abb21376c89e311d85a9ee75145a22594bab SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-disc1.iso.xz) = e0f0557be6f6416cdddadebfb0d385e85e8df60042f73cf78b6b311ca994ceed SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-dvd1.iso) = a609bf9878a664eab9f54150a41b2331f70192fcb42baa049bd03a93523a6234 SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-dvd1.iso.xz) = 0abf984d768f358b0c1d153c5ac1cf1f009f0836bf6037e86963e3d3c56b6187 SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-memstick.img) = 28b73c1f4832fbc8df297a130e54088fea3545d8147b4537ec36dcdd33ea1ccf SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-memstick.img.xz) = 84e9f47dc14f4c2fe488ba7aab92648b7eefadce50b53228456bf03fe2b46f5b SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-mini-memstick.img) = 9807c221e9c9c8649c64c7be44d17405015e9f807a5f21077ca878ab40883f2a SHA256 (FreeBSD-12.0-BETA3-powerpc-powerpc64-mini-memstick.img.xz) = 9667f8d934ecc99fcb863f64f1cfb75b237f89567be7b5ea56584d2fa107626a o 12.0-BETA3 sparc64 GENERIC: SHA512 (FreeBSD-12.0-BETA3-sparc64-bootonly.iso) = 0d7557cbee59ee7ca847595bb5bfb2f4e9c886eb2380cc7317412f5a2e2cfd32bf75924382b95993742361cdede286d8ce51d59519c030119d7e8d13891d827f SHA512 (FreeBSD-12.0-BETA3-sparc64-bootonly.iso.xz) = 142d6e288273ef2858a5e430c30898205f44e02212d867e04e58565eb2ad42a11d58324d20deefa0a43f6dabced22285f38c344a184cab37cf7963f73e2084ab SHA512 (FreeBSD-12.0-BETA3-sparc64-disc1.iso) = 1d85f079474b8e9288b87ed532a7026086690700ec07534cc1d6f7d1b8e2ba4c6ca5ec1afe0361f21ee455fc0c9e6c2965c545bb6609da49b1f42e785341ee6e SHA512 (FreeBSD-12.0-BETA3-sparc64-disc1.iso.xz) = 4acc590a400cf20c0b9987613c4fecb53a1a4d23d577513ad1404c41a205b3dc9f918e1680e9957b1fcf7b09cf73723b78717d3c1fb8b5a9c4e2be503396c505 SHA512 (FreeBSD-12.0-BETA3-sparc64-dvd1.iso) = f24bdf6913cf91c6ef2921ded7736319edf34f644bd05eef491229e68fef032b403dbe0871891441000154c263432b843587eda0fc9a778d76eb05fe0e0dcd53 SHA512 (FreeBSD-12.0-BETA3-sparc64-dvd1.iso.xz) = faec09bfee2cddcb86c03a5d6f6735119fb755178abbf5e9278c8415dbed82f637f68daab59ed58d5beea54516d8bf58a8f3fbc9f92ee5a777f462b8472a1ff6 SHA256 (FreeBSD-12.0-BETA3-sparc64-bootonly.iso) = 704152f8a73542459cb512ba89244865b1bf899eb7a34e1e4565b5f08c86be23 SHA256 (FreeBSD-12.0-BETA3-sparc64-bootonly.iso.xz) = c606754ea819336569198c2b66677edd7237398438eb8bd49028bfa6ce7e7af6 SHA256 (FreeBSD-12.0-BETA3-sparc64-disc1.iso) = 528ef9e71b06e63ea1d32c10413c8a4160cce863b6bc3f192edc0bfa044d5011 SHA256 (FreeBSD-12.0-BETA3-sparc64-disc1.iso.xz) = 85cb67acc3f132e66ee5c8ecbcc0eef4f0017961f75654cc80cd0305bd457803 SHA256 (FreeBSD-12.0-BETA3-sparc64-dvd1.iso) = 567aec5625f1bcdbcf84974e404e3345f586fc89b7e51ecf64d0b505d8f1f724 SHA256 (FreeBSD-12.0-BETA3-sparc64-dvd1.iso.xz) = 5af429e3f848f6caf5dcf398049e0fc45b3896957cf7935ecceea9dc50a7adde o 12.0-BETA3 armv6 RPI-B: SHA512 (FreeBSD-12.0-BETA3-arm-armv6-RPI-B.img.xz) = 99f5a5d4c622fdc47cd4e35938cb1e85fd73b5a0cf2a1fcda3fe8c2cd497ab6a40b5deb72373ba05b272ef70818b6166b9dff7665bc3a31181b9bc83af3b9b11 SHA256 (FreeBSD-12.0-BETA3-arm-armv6-RPI-B.img.xz) = 06d3341e5560b35986335309432413e5a0cf16d6108bc0c18e19bb9cb1cba3cc o 12.0-BETA3 armv7 BANANAPI: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-BANANAPI.img.xz) = 0b7b5c2403a9a39c01ce52724d6d186bcbaacaf3d3b38ff75ae97ea41066456d7e591b17b259aa113bd3f56684051db429af4a1f046a995fc6f753a74f9be70a SHA256 (FreeBSD-12.0-BETA3-arm-armv7-BANANAPI.img.xz) = 94ce5994727e305eefe71defb156337ee5d444c4dfa6f9b5ddf2f00a53af5f03 o 12.0-BETA3 armv7 BEAGLEBONE: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-BEAGLEBONE.img.xz) = 22f54169853058ef1aa2d5c418ce3e9a0f49261db639519aaf0a8928045372f61acd1dac871493e6a1ed5c003dbf1210ca42d7cad5622abe01c56b2e12fa4477 SHA256 (FreeBSD-12.0-BETA3-arm-armv7-BEAGLEBONE.img.xz) = d8d070007b450d3b16e4f777365be63b0441b0e25e5dc1dcdcee0dc925a5c670 o 12.0-BETA3 armv7 CUBIEBOARD: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-CUBIEBOARD.img.xz) = 149b71fa899b706f66c20b91277342e1405b03d72b0501e86e781df4b746637420377653c1fb5a73ab83e088d0206bc52beac0bed29b915e09a5e746fdd06ff8 SHA256 (FreeBSD-12.0-BETA3-arm-armv7-CUBIEBOARD.img.xz) = 185834737b91a31e6e370b2b7ebae966edfabf78958e161906866e1f9b5084e3 o 12.0-BETA3 armv7 CUBIEBOARD2: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-CUBIEBOARD2.img.xz) = 222e37f86abfabc49e5092e3779d6d05c669f37241064ad624baf726fb60e96a87d2181fbff1ed9745dd28895555fb6ea565a5ea77e74df952598f0344cb7a22 SHA256 (FreeBSD-12.0-BETA3-arm-armv7-CUBIEBOARD2.img.xz) = 189a8998c40b8df7e01b45d851bec9e021833ea037575d6343cc570a8659fe72 o 12.0-BETA3 armv7 CUBOX-HUMMINGBOARD: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-CUBOX-HUMMINGBOARD.img.xz) = 791a863de669938070e2072c662dc8f7be7e0913f0a7880fdd70059d79363e54ccbe8642bdb612d57c2599afc8fb3c2ffdfc3ff49cdb0a48fd190ef9d23999a1 SHA256 (FreeBSD-12.0-BETA3-arm-armv7-CUBOX-HUMMINGBOARD.img.xz) = be98543b8e2ea3ff057e677e3b7335f95083b9e570b35c32685f9bcb3fde986d o 12.0-BETA3 armv7 RPI2: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-RPI2.img.xz) = d08c1bacc356ad2cd1413bc1651dfed0b82ec417d45c27da41bec41c825e7e7cbe77cc5d811b8b399cf6f39eb7100d034abe869ef30ea5dadd0e1d5ff9c4fef6 SHA256 (FreeBSD-12.0-BETA3-arm-armv7-RPI2.img.xz) = 389fe30a486eee05864b7b02e4cb2f30071e141d20176ceb15ceeb6bb5aa6212 o 12.0-BETA3 armv7 PANDABOARD: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-PANDABOARD.img.xz) = ebc5ac72c6c5777c908b938c696096ab783aafeb31675f30169135e30d137a4cea432638e82471284c001d52a8e69fb5669144d379df6933d5a9312bfa9285e4 SHA256 (FreeBSD-12.0-BETA3-arm-armv7-PANDABOARD.img.xz) = 9b01aed50f330d998f113eb82b6b94e9b1064f4dcc65f45529b7da9e955d3df3 o 12.0-BETA3 armv7 WANDBOARD: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-WANDBOARD.img.xz) = fb66078ebf4dea5407e6728727c0ccab86f9e29c2bbedc3a093f005cfcf0823acfd0ab1cd27ab43e8519cff6e8f2e07e590cefcb1c4aa64f29c01b5f46f409a1 SHA256 (FreeBSD-12.0-BETA3-arm-armv7-WANDBOARD.img.xz) = cdd1207263f89b1ef1b71cc89c911d214a4adec055d51bb3f069f14af978e144 o 12.0-BETA3 armv7 GENERICSD: SHA512 (FreeBSD-12.0-BETA3-arm-armv7-GENERICSD.img.xz) = 6d347212d1ac81c5f1161d0f6777684eca5b191ad9374993b004cf78600c8bf11ad62cad9f570723c744b27d700c0eaaf8b1b17c6c841be6dafd5607df0b89d2 SHA256 (FreeBSD-12.0-BETA3-arm-armv7-GENERICSD.img.xz) = 04c90102eb415995d0592066daa4c0ad6af9740e76a537783afb373b8b71d4be o 12.0-BETA3 aarch64 GENERIC: SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64-memstick.img) = fb6134311c13226d65ed96a6078a85769a7ba2012fad5d656acbd0e1b473d087a46926495373ecb1038cdd103d466796f84b73e76302bb48c7e532ca2a77158b SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64-memstick.img.xz) = f54656ee9104d9b3f0cd0e3d4544701d66633a1e78359b34e774efd4b315a8012e7988486eaeeb556adba24328f3ba1a5035abdb70d1d4ff8b54852494ac3986 SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64-mini-memstick.img) = 589124818d0a8e05097ed280841458f193a919169dee56c0cf2c3593b460b68a9fb80b5ae41d8bd712e52d898aab30e2b851942ec95d98247d39fb03a36fe780 SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64-mini-memstick.img.xz) = 4babfd5f769a7f711c1c93663aa69d9a7830b0b26d794978acc3dae247c14ecf6b6ad6eb239eaf3dacb46076f3e734bf9acb5d5895083fdedf843422cf459e24 SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64-memstick.img) = 196c3b84f711598ab38b8b665087b0c0ff76945eb19d35499d8c4cb852b1316c SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64-memstick.img.xz) = 86031bb085dbde87bce40ffac080e8b84a3262c90bfa01b96f14557b99c05959 SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64-mini-memstick.img) = 7b60126078b2593321baf2ec53a6e1ef356de30db0a2ac64b4f4fa8ba9c8f631 SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64-mini-memstick.img.xz) = b7223c72ac7fad175a668796dcbe43fef75a7152162830964253f558fdab1db9 o 12.0-BETA3 aarch64 RPI3: SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64-RPI3.img.xz) = ad3da1c2c4320897e5e97c2cf0997cb287576d72946758c9ab106fabd10f52bdbdfcbacf393afb70d967bc48a77c2296cf4fdf0553d6ccc67c12db7d4801c2bf SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64-RPI3.img.xz) = 050793d6d5bb32dd32669182a8507983f005b8830dc9501a18952a95a27e31c2 o 12.0-BETA3 aarch64 PINE64-LTS: SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64-PINE64-LTS.img.xz) = fe15197f0524f1065f43b8f325e7183b22848b2fa5a4395fe11694f47a161a4c866c58038e8ee5260dea419a7e874c2ccfb041ab9e283272cc06e8cd9ed9a653 SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64-PINE64-LTS.img.xz) = cf53caa14c4632856d65837cedd872e80e28ad905a4f7bdc690313a132287627 == VM IMAGE CHECKSUMS == o 12.0-BETA3 amd64: SHA512 (FreeBSD-12.0-BETA3-amd64.qcow2.xz) = 0f2b1553a2a2b221fe257b47a87761ca983c87d3d58a36facff66024f6fd1fec4b93df4b3e452edf14cad4a2aaa8f98d68c81abef31710e8ea68d7a517c27bd2 SHA512 (FreeBSD-12.0-BETA3-amd64.raw.xz) = e06bfe0b1149e32140c94ae5afb4741e0110fb8b0607ce3345dcd684b90e6142c78d43be8cd2c056f5646942685243bdd833b6fcc09d3958e324be9e6de31a78 SHA512 (FreeBSD-12.0-BETA3-amd64.vhd.xz) = ad3fa529a5ad3a6b9a181b4205bd8dcd8aca4fcde11cedec21b97727c4543f9a74bad24bed8c8d5ca5bcda673f96a0d6d798a83dacba8f572489030a5af81dd1 SHA512 (FreeBSD-12.0-BETA3-amd64.vmdk.xz) = 714f6420a73055aed7eddc34bc8744949d79a0dbaa67510b419cd1157a27a759f5c5056f1d78103da367f0f54edb5a6b7eb1847f9c286c03e8829c2bce244fbb SHA256 (FreeBSD-12.0-BETA3-amd64.qcow2.xz) = d6976a1af3e5131ab8b4146651d9cba563a4d445e915848293f1353fd6c783e6 SHA256 (FreeBSD-12.0-BETA3-amd64.raw.xz) = c42d04f10f31033d3b0df5e81d0e185353bc250006acc2df02af66c130442968 SHA256 (FreeBSD-12.0-BETA3-amd64.vhd.xz) = 4a616d09790316a2941b1d6d6adf6d6ecd2f8c696ed7fe6a44a5064607fb3347 SHA256 (FreeBSD-12.0-BETA3-amd64.vmdk.xz) = b51fb0cd11b6b19a7ab46c7cbafc1508aa68e312fa1be07e8eedf1927eba6f2b o 12.0-BETA3 i386: SHA512 (FreeBSD-12.0-BETA3-i386.qcow2.xz) = 567c289b10010d90bbbed73734052ba1312fcbd896c5e718dd0000af57a2fb31a155cf9d38785e214f9e326ad451575ab801f47ce456b556e024c0db354bb4ab SHA512 (FreeBSD-12.0-BETA3-i386.raw.xz) = 242f9fdec05eb1c5812765edd4c90e84d59d370f84dc2a0c9bda41a1d3fff3f98e239e4d65d5023423623995919b53720719d40849af6863b0c217e1f751e08c SHA512 (FreeBSD-12.0-BETA3-i386.vhd.xz) = 9901329ecea5dcf7c76e3ad524a6b2002cd22017bdc6c88ad12d3b3a629e7421c507b989a8e82dcbfc44ac14578a2b3ef3027baa1ac74970e31a5f0240265990 SHA512 (FreeBSD-12.0-BETA3-i386.vmdk.xz) = edd431ae2ecc2aead7c6d19504dc832b97dc3462a600e398afd3b81a429858376e065dcea04ddea423fb1bf59ef6050221918c5b651f099d865bac589232e345 SHA256 (FreeBSD-12.0-BETA3-i386.qcow2.xz) = fa485e57ce373980b66652751e427dbdeae14bec87f7aea7b14e33dc8f941c85 SHA256 (FreeBSD-12.0-BETA3-i386.raw.xz) = b875fe95bb1cfd090ade5168b209a40bdf6c1da7e9ee597b1a338a10f4e3631f SHA256 (FreeBSD-12.0-BETA3-i386.vhd.xz) = 86853f478ac8cc25d6852ec6b6cb24967441612d868c91c7b8605dd23394644d SHA256 (FreeBSD-12.0-BETA3-i386.vmdk.xz) = 2abf790637e640cb6e35479d4e3fb3b171405572fb8f3ff3b3fcabae626b1772 o 12.0-BETA3 aarch64: SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64.qcow2.xz) = 72b14f614492452b5b3f82ec08c803632a1710e3c32b48e3d66df005ad62d1572cdbc3a9311d8995818bec7add513136beef203da83e9334a7bb6a7de4a03217 SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64.raw.xz) = 1bd2e9c0a65551ab27556a0fad8cf302344974cccab47137bd24581f600e9fdebb78ec85dcb8278516354057d1eaf14f8555707bd809e680d73fd9a83a7e70e1 SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64.vhd.xz) = 41f4d5c41dfdf9d63e7c756d336d94727f5d35fcb88d68b2ceb9b06201069b807ffcdd62fdf18f0197263cdeb9682537c605ddcfe5de3914f833ed814b94ad00 SHA512 (FreeBSD-12.0-BETA3-arm64-aarch64.vmdk.xz) = 7abb4e78731ba06143bf94fbe245a1e6215b42563166ee6640dcdfdea3d3b629130b8b1348ab389eddff356e451e93f5a6b12ea01c697dc51c8718845221faf6 SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64.qcow2.xz) = 98820178902ba3793d58a931f82a6ece2e3a7b7e2f8cadd113f83da4014e61cd SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64.raw.xz) = 5309af122e2c04fc3a3854d005999ee23618081ac736377969bcba6f8649492b SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64.vhd.xz) = 30190333407a7efc57cc6b42ed949e49bcaff4f2621b1b85f0b1460134b99a4e SHA256 (FreeBSD-12.0-BETA3-arm64-aarch64.vmdk.xz) = 0ef09ff69c20457f6710061093aaf238ec4b4a06743f78416a662578de3b7719 Regards, Glen Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlvd38YACgkQAxRYpUeP 4pN2zw/9FwkqnJ1vSX0ni6Cigo0lHjYuHzTy2BadgREZebzRao/0k+JpJWSZxJ4s LS2+geU4DLlh0bi/2tYU8ahqGcvVvk6ya+2gfogtIIeXbVBeVQLK6T2SlKYKXnwj XPLCF/7RLH5ZdwBLByskm4TenSoeJQeH2ztSTyGhKpFHWdqXmskHRB+ZNLRhbEO4 0ko8YRcJocEZPtBBHEi2VJ1ZGupnhBD0q/cHp10L89Y/wdoPUK6JQOQaNTScLHey w1qv63O0uba0JGbynVqvAYn4bwKsArv7IEhAaCio3/BQqkxIc2gsVI0Fm1yAG98Q rySTJ87sSpS+RNUV8tpoI/UqZmTzEgcPidMtgzlAJ+YwX9ADiJPKunBUcRBrKzMa eCom4SMn8nrD2QdEmns/0Ch8/bFcTxfe6q6LCExqfN5V9EWhcMOagLc0gXcVjY8+ V+JD8qpc9a/WryGwFhWRCfOr0K9RsCvWjmmglWfJT4VDCmPfrGVjdLmNa0GF2c08 Zal75ZYRJAxjLkJU04NwuDtitKX2lMz921d5wucNRXsrMVNApr+yvSZ/c0A+V22f cTBh4d52IUDtaOKWF1+1gWaGs68/czlcnt3IGQjJfAPhgJqzI4gZP9JyYbhAlfbg G2H4uXL3ZbAijK7fKmQX3MoYE4XkrIK16QtS27cKl7gVLsERqZE= =B1av -----END PGP SIGNATURE-----