From owner-freebsd-stable@freebsd.org Mon Aug 28 01:59:12 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4709FE03041 for ; Mon, 28 Aug 2017 01:59:12 +0000 (UTC) (envelope-from services@service.iworku.com) Received: from out21-27.dm.aliyun.com (out21-27.dm.aliyun.com [115.124.21.27]) by mx1.freebsd.org (Postfix) with ESMTP id C60E96465F for ; Mon, 28 Aug 2017 01:59:10 +0000 (UTC) (envelope-from services@service.iworku.com) X-EnvId: 19901778511 Received: from ip-10-0-1-175.cn-north-1.compute.internal(54.222.142.129) by smtpdm.aliyun.com(127.0.0.1); Mon, 28 Aug 2017 09:58:26 +0800 Date: Mon, 28 Aug 2017 01:58:26 +0000 (UTC) From: IWORKU To: freebsd-stable@freebsd.org Message-ID: <1779542798.12207.1503885506029.JavaMail.root@ip-10-0-1-175> Subject: We figured out why our client don't choose us! MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 28 Aug 2017 01:59:12 -0000 From owner-freebsd-stable@freebsd.org Mon Aug 28 06:55:11 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDCCAE074E8 for ; Mon, 28 Aug 2017 06:55:11 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC7B86B916 for ; Mon, 28 Aug 2017 06:55:11 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-yw0-x234.google.com with SMTP id h127so24456043ywf.3 for ; Sun, 27 Aug 2017 23:55:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DvodAsPZpi2wonsgqc1V0TKjRmiLF0x3zShDcRQIQuw=; b=O9zCMtlK22rDzs/GFznZmXLiUSnwGnZN9OWsuGmuqHCVuxlUsSCwWrcFtFPZ8FT8NB 9PyCvdH6nYRwlnmN767kQMdbPyARuVFduIhl7FZ+/qyrZsU5LjO2QajJ3/yNW6u9BPS0 AeDWxRWXPkeajxgFmWtyv+tS4RAhQNTGMCZMFcQPzmUhr7e0YeF0RuRqYVUuwieUkkXb Ivd1TAM6Dy00HAcf6kXLHci8fDL3+KT8TR+SB3t5ATQHb0Se5yLU1vPETrly7lU/0zHE AQ4+QdJ7RTiISH/0082nfmusdq49x0MRLGJm+IpwA/qeSZG3AQ1n9zEjj6iSE0TXlv1H Wfhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DvodAsPZpi2wonsgqc1V0TKjRmiLF0x3zShDcRQIQuw=; b=jL/oy/KXffWBJXD8kaS9zbkKPJTXL+dwXCJmXHcUoB87jg4JQbSlkQ009ijiab+urE cAIxDObFtADPe597PVZ78RT6GSsZlGKcOzodcMJvafAE5IZvPcsj6N7LkMMCYkKin/1a LynqGUf0TSbWOI1dtOpvzaPrxeBxqgOa6FnoVCMieylsCaSLRD9DQCKGFbsyVJmeUing FdSFMZvQ1lV82Qnt74dPLh8pFH0pWhc2gZRSfTM1ssxC1GiSp5x61HVpoWTMBO+2owDQ Le8DzcIRUWEYeQfphJlRlUsOe29uBQ1N61/oD7tDf2sDVw9D6Qq0v13haVeb4LrbCLmE PuAg== X-Gm-Message-State: AHYfb5h+3LTRHtpzA+VByZ31FHlIFPV1AyKtUsFnUOzjLVtRsac4r5lt EZgWCJd8WEcxL+dvdGMkyN2G5HlNHYQE X-Received: by 10.129.50.206 with SMTP id y197mr2857517ywy.314.1503903310687; Sun, 27 Aug 2017 23:55:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.227.193 with HTTP; Sun, 27 Aug 2017 23:54:40 -0700 (PDT) In-Reply-To: References: <1C5A448F-C91A-4599-8500-E4E46E6F5205@dsl-only.net> From: Ed Schouten Date: Mon, 28 Aug 2017 08:54:40 +0200 Message-ID: Subject: Re: svn commit: r322875 - head/sys/dev/nvme To: Mark Millard Cc: David Chisnall , Warner Losh , svn-src-head@freebsd.org, FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 28 Aug 2017 06:55:12 -0000 Mark, 2017-08-25 14:53 GMT+02:00 Ed Schouten : > 2017-08-25 9:46 GMT+02:00 Mark Millard : >> It appears that at least 11.1-STABLE -r322807 does not handle >> -std=c++98 styles of use of _Static_assert for g++7 in that >> g++7 reports an error: > > Maybe we need to do something like this? > > Index: sys/sys/cdefs.h > =================================================================== > --- sys/sys/cdefs.h (revision 322887) > +++ sys/sys/cdefs.h (working copy) > @@ -294,7 +294,7 @@ > #if (defined(__cplusplus) && __cplusplus >= 201103L) || \ > __has_extension(cxx_static_assert) > #define _Static_assert(x, y) static_assert(x, y) > -#elif __GNUC_PREREQ__(4,6) > +#elif __GNUC_PREREQ__(4,6) && !defined(__cplusplus) > /* Nothing, gcc 4.6 and higher has _Static_assert built-in */ > #elif defined(__COUNTER__) > #define _Static_assert(x, y) __Static_assert(x, __COUNTER__) Could you let me know whether this patch fixes the build for you? If so, I'll commit it! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 From owner-freebsd-stable@freebsd.org Mon Aug 28 08:25:34 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E07DE089AC; Mon, 28 Aug 2017 08:25:34 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC8EC6DECA; Mon, 28 Aug 2017 08:25:33 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id t201so2995334wmt.5; Mon, 28 Aug 2017 01:25:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=g4tmIP1MMpzZW6W0cqtfNKZutAW5I+Z8R4+QjMiZltg=; b=UG/3MYNZso7x1XPgJT+dy9Q6kEdsvCaBIOUdlIHY/bI/oAZCZYbG8chaA7TMNOhNV4 6DG/enUiTaggVan8qF31a489bsMItK06w/wNTJ1VmmbYN/PpczYMEQuBu80XvLcXM2QM jSNCPYy6RYDFe+o3k6hNo/b2UDlhDG8319lqkjJObdUu6q14/SCWzoNxA+f7Rc12pjAc zjnRHf9C14nTmuJFpiWIpV0kzf8oBo5S9H+yEGjW41exsaIbfJtqkk788J9u+SXhVxqO Ibzfooc7ZQIsLsAwF2F7UgP1En/BEatsT3vIbrDfU8bzhY2SS6iSgt2MqGcDAWsKZxNX +fZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=g4tmIP1MMpzZW6W0cqtfNKZutAW5I+Z8R4+QjMiZltg=; b=ZXPgeseO89seaWtdKLl0I2pjs97RutLCwpR3gQ6rfsXv2Zn+17KkqOibQmOaegG4zU jUK7MS3Y5j3m0O6+eHrwFiauEEOnjASmRXi3tJkoplfKbstpExSmDwbw8R8KpNRh5VMj R5pcklUXdi/qCzWsOIru1UC/Ahw/NbTJPys0lhnKNCqvDx84WkGlxkaTu/OD8X16f4qk ud1f7lVACTFQ+oY/GjmGb10V2o6gqHJUj3NXNcqRXFDXpsouV19BseOOHFhIWQ/pvjIg 5tUZT1+26CwR6Fr5JBqiggwuhKQ9pUVSKBuh0WMNc97nAsLRQClCDkPMAMvth3HuBXll Z2xw== X-Gm-Message-State: AHYfb5gU7JmkwT4MXUzJAywEYdPjc6n7spFTo6B/ATrKlUzrhBgGFW94 1/Kt16CaQTij4VK+2yabBQ== X-Received: by 10.28.175.213 with SMTP id y204mr2814414wme.67.1503908731196; Mon, 28 Aug 2017 01:25:31 -0700 (PDT) Received: from ben.home (LFbn-MAR-1-330-35.w2-15.abo.wanadoo.fr. [2.15.164.35]) by smtp.gmail.com with ESMTPSA id 52sm11626802wrt.38.2017.08.28.01.25.29 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 28 Aug 2017 01:25:30 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???) From: Ben RUBSON In-Reply-To: <13DE4E6D-CE83-4B5D-BF88-0EFE65111311@gmail.com> Date: Mon, 28 Aug 2017 10:25:27 +0200 Cc: Hans Petter Selasky , FreeBSD Net , hiren , Slawa Olhovchenkov , FreeBSD Stable Content-Transfer-Encoding: quoted-printable Message-Id: <7B084207-062A-4529-B0DC-5BFEB6517780@gmail.com> References: <9c306f10-7c05-d28d-e551-a930603aaafa@selasky.org> <896dd782-cb2c-0259-65d1-b00daae452de@FreeBSD.org> <0DB9F6FF-8BC9-48F5-B359-AC1905B9EB06@gmail.com> <7f14c95d-1ef8-bf82-c469-e6566c3aba66@selasky.org> <76A5EE7E-1D2E-46B4-86F1-F219C3DCE6EA@gmail.com> <4C91C6E5-0725-42E7-9813-1F3ACF3DDD6E@gmail.com> <5840c25e-7472-3276-6df9-1ed4183078ad@selasky.org> <2ADA8C57-2C2D-4F97-9F0B-82D53EDDC649@gmail.com> <061cdf72-6285-8239-5380-58d9d19a1ef7@selasky.org> <92BEE83D-498F-47D5-A53C-39DCDC00A0FD@gmail.com> <5d8960d8-e1ff-8719-320f-d3ae84054714@selasky.org> <6B4A35F7-5694-4945-9575-19ADB678F9FA@gmail.com> <297a784a-3d80-b1a6-652e-a78621fe5a8b@selasky.org> <3ECCFBF1-18D9-4E33-8F39-0C366C3BB8B4@gmail.com> <0a5787c5-8a53-ab09-971a-dc1cd5f3aca0@freebsd.org> <645f2ee3-3eaa-660e-2a64-37d53e88322f@freebsd.org> <13DE4E6D-CE83-4B5D-BF88-0EFE65111311@gmail.com> To: Julien Charbon X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 28 Aug 2017 08:25:34 -0000 > On 16 Aug 2017, at 11:02, Ben RUBSON wrote: >=20 >> On 15 Aug 2017, at 23:33, Julien Charbon wrote: >>=20 >> On 8/11/17 11:32 AM, Ben RUBSON wrote: >>>> On 08 Aug 2017, at 13:33, Julien Charbon wrote: >>>>=20 >>>> On 8/8/17 10:31 AM, Hans Petter Selasky wrote: >>>>>=20 >>>>> Suggested fix attached. >>>>=20 >>>> I agree we your conclusion. Just for the record, more precisely = this >>>> regression seems to have been introduced with: >>>> (...) >>>> Thus good catch, and your patch looks good. I am going to just = verify >>>> the other in_pcbrele_wlocked() calls in TCP stack. >>>=20 >>> Julien, do you plan to make this fix reach 11.0-p12 ? >>=20 >> I am checking if your issue is another flavor of the issue fixed by: >>=20 >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D307551 >> https://reviews.freebsd.org/D8211 >>=20 >> This fix in not in 11.0 but in 11.1. Currently I did not found how = an >> inp in INP_TIMEWAIT state can have been INP_FREED without having its = tw >> set to NULL already except the issue fixed by r307551. >>=20 >> Thus could you try to apply this patch: >>=20 >> = https://github.com/freebsd/freebsd/commit/acb5bfda99b753d9ead3529d04f20087= c5f7d0a0.patch >>=20 >> and see if you can still reproduce this issue? >=20 > Thank you for your answer Julien. > Unfortunately, I'm not sure at all how to reproduce the issue. > I have other servers which are 100% identical to this one, same = workload, > same some-months uptime, but they did not trigger the bug yet. >=20 > If other network stack experts (I'm not) agree with your analysis, > we could then certainly go further with D8211 / r307551. >=20 > One thing that perhaps might help : > # netstat -an | grep TIME_WAIT$ | wc -l > 468 >=20 > Note that due to this running bug, sendmail has lots of difficulties = to send outgoing mails. > As soon as I run the above netstat command, I receive a lot of stacked = mails (more than 20 this time). > As if netstat was able to somehow help... >=20 > Number of TIME_WAIT connections however does not decrease, but = increases. >=20 >> And in the spirit of r307551 fix and based on Hans patch I will also >> propose to add a kernel log describing the issue instead of starting = an >> infinite loop when INVARIANT is not set. >=20 > Which should then never be triggered :) > Good idea I think ! What about : D8211/r307551 + Hans' patch + Julien's idea of a kernel log (sort of "We should not be here but we = are") And backporting all this to 11.0 (and so to 11.1 too) ? As this bug can impact every FreeBSD machine / server, leading to an unavailable / unreachable system (this is how mine ended), sounds like it could inevitably be a good thing, for production = stability purpose. Thank you very much ! Ben From owner-freebsd-stable@freebsd.org Mon Aug 28 09:02:14 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDE74E09402 for ; Mon, 28 Aug 2017 09:02:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-57.reflexion.net [208.70.210.57]) (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 9D83A6EFC7 for ; Mon, 28 Aug 2017 09:02:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 15297 invoked from network); 28 Aug 2017 09:02:07 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 28 Aug 2017 09:02:07 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.2) with SMTP; Mon, 28 Aug 2017 05:02:07 -0400 (EDT) Received: (qmail 3497 invoked from network); 28 Aug 2017 09:02:07 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 28 Aug 2017 09:02:07 -0000 Received: from [192.168.1.109] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 54F3EEC8816; Mon, 28 Aug 2017 02:02:06 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r322875 - head/sys/dev/nvme From: Mark Millard In-Reply-To: Date: Mon, 28 Aug 2017 02:02:05 -0700 Cc: David Chisnall , Warner Losh , svn-src-head@freebsd.org, FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers Content-Transfer-Encoding: 7bit Message-Id: <0639EC0E-1F0F-4CB0-A3FE-4E8CD814B6D3@dsl-only.net> References: <1C5A448F-C91A-4599-8500-E4E46E6F5205@dsl-only.net> To: Ed Schouten X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 28 Aug 2017 09:02:15 -0000 On 2017-Aug-27, at 11:54 PM, Ed Schouten wrote: > 2017-08-25 14:53 GMT+02:00 Ed Schouten : >> 2017-08-25 9:46 GMT+02:00 Mark Millard : >>> It appears that at least 11.1-STABLE -r322807 does not handle >>> -std=c++98 styles of use of _Static_assert for g++7 in that >>> g++7 reports an error: >> >> Maybe we need to do something like this? >> >> Index: sys/sys/cdefs.h >> =================================================================== >> --- sys/sys/cdefs.h (revision 322887) >> +++ sys/sys/cdefs.h (working copy) >> @@ -294,7 +294,7 @@ >> #if (defined(__cplusplus) && __cplusplus >= 201103L) || \ >> __has_extension(cxx_static_assert) >> #define _Static_assert(x, y) static_assert(x, y) >> -#elif __GNUC_PREREQ__(4,6) >> +#elif __GNUC_PREREQ__(4,6) && !defined(__cplusplus) >> /* Nothing, gcc 4.6 and higher has _Static_assert built-in */ >> #elif defined(__COUNTER__) >> #define _Static_assert(x, y) __Static_assert(x, __COUNTER__) > > Could you let me know whether this patch fixes the build for you? If > so, I'll commit it! As a variant of stable/11 -r322807 . . . buildworld and buildkernel seem to work fine. (I did not try any port [re-]builds.) Based on the same main.cc as before . . . g++7 -std=c++98 main.cc g++7 -Wpedantic -std=c++98 main.cc g++7 -std=c++03 main.cc g++7 -Wpedantic -std=c++03 main.cc no longer complain (so no error, no warning). clang++ -Wpedantic -std=c++11 main.cc clang++ -Wpedantic -std=c++98 main.cc clang++ -Wpedantic -std=c++03 main.cc each still give the warning but no error. g++7 -Wpedantic -std=c++11 main.cc g++7 -std=c++11 main.cc clang++ -std=c++11 main.cc clang++ -std=c++98 main.cc clang++ -std=c++03 main.cc are still silent, no errors, no warnings. Note that clang here is version 4 --the same as in my original report that had the g++7 rejection example. This is because of the stable/11 context that I used. (An intended MFC had been listed.) If needed I could probably try under some version of head (and so test clang version 5). === Mark Millard markmi at dsl-only.net From owner-freebsd-stable@freebsd.org Mon Aug 28 09:36:49 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E195AE09D3D for ; Mon, 28 Aug 2017 09:36:49 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B34D70178 for ; Mon, 28 Aug 2017 09:36:49 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-yw0-x22f.google.com with SMTP id h127so26197847ywf.3 for ; Mon, 28 Aug 2017 02:36:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u/B4CIKTIpXtJTDiWp0pYzBNCK+pwX/dz8cXZe59aU8=; b=OwN4Jvtgsv4wQf6E8c3As7Ou7Z1YkhCYLnKYu8zHXGLKeyX+xTCHlpOBDvhVe10Zvq ElF9ntamn5VUAT/O7Ez2jGTc0rpMacYEWoo6q6BMzQjcfUp+d96BwKq664r9s5MHIkvJ xxfTWcZ4M36HU7iv5qlXL82htQWtiGdhaAtf2Irc8hLIJUVgf9LP48HZ1TNMrM7yjWVA 3nK2iFESEU1UiAlnzZu669y9XN63++gj2rilZo/Qf0hhsMSY2/fq/j/avj/qX1V8ZUJX lXIHdMsBMYYslASPcMxtYzzYv1IHHwyK9mEfjqZD5oRw4+gBERdnYINkmcCvEOPAtk1M 0LZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u/B4CIKTIpXtJTDiWp0pYzBNCK+pwX/dz8cXZe59aU8=; b=uVG2IY44Or6H3+WiJBPg+Fl7bEXwe+26IN/kjHZa7qL9eJDa5nyKZSUTaeM4tKPG8v uH4HGCyuwBzIRtirZq/6MVsCw8QgIYKpmw6YsCO61QGtSaRH/7NcekxalfMjl8/7+HAs AcUfOhosg8aLGyr0DjmK9LkZKY6Ijm+wUcOMzUbe5wLcSsapKWkGeCpd7xOkwB4aNrNF Z57rfjGXh1aK8zo1wb+IwNmKH8hCKy+mgFAXwzp7lZr458HmKFnuWDEMkhtxIsTGapgR d9l2UwUr7o86Usm3vPwGWcA8Vk5gfOla4ncY/E9cUJ7Hr/G9Csn8Qt2HIM7GYj62cKXB Xiow== X-Gm-Message-State: AHYfb5itTGYJQ2ZfXIVYQGBc43pUZRgAGsGNUyueLz1jp8VvB6JvgQJT 89Xd9A0YO+66ksW5mokP7+SKilizXs+p X-Received: by 10.37.171.208 with SMTP id v74mr5173459ybi.99.1503913008729; Mon, 28 Aug 2017 02:36:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.227.193 with HTTP; Mon, 28 Aug 2017 02:36:18 -0700 (PDT) In-Reply-To: <0639EC0E-1F0F-4CB0-A3FE-4E8CD814B6D3@dsl-only.net> References: <1C5A448F-C91A-4599-8500-E4E46E6F5205@dsl-only.net> <0639EC0E-1F0F-4CB0-A3FE-4E8CD814B6D3@dsl-only.net> From: Ed Schouten Date: Mon, 28 Aug 2017 11:36:18 +0200 Message-ID: Subject: Re: svn commit: r322875 - head/sys/dev/nvme To: Mark Millard Cc: David Chisnall , Warner Losh , svn-src-head@freebsd.org, FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 28 Aug 2017 09:36:50 -0000 2017-08-28 11:02 GMT+02:00 Mark Millard : > Based on the same main.cc as before . . . > > g++7 -std=c++98 main.cc > g++7 -Wpedantic -std=c++98 main.cc > g++7 -std=c++03 main.cc > g++7 -Wpedantic -std=c++03 main.cc > > no longer complain (so no error, no > warning). Perfect! I've committed this change as r322965. Thanks for testing! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 From owner-freebsd-stable@freebsd.org Mon Aug 28 09:57:53 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36C6BE0A312; Mon, 28 Aug 2017 09:57:53 +0000 (UTC) (envelope-from julien.charbon@gmail.com) Received: from mail-wr0-f195.google.com (mail-wr0-f195.google.com [209.85.128.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B814570B02; Mon, 28 Aug 2017 09:57:52 +0000 (UTC) (envelope-from julien.charbon@gmail.com) Received: by mail-wr0-f195.google.com with SMTP id p8so27389wrf.3; Mon, 28 Aug 2017 02:57:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=E/PSboiAWtBz8mEaNK12R1IfS6w2/l2Ar7yulM7Eeks=; b=Ykcu2hCyOPn438sJORa0ttfuoMyInJayNpgr98r+HF8VBmNvzS9Ys9Zyj7W8EwjSpL 5uETSFPfpAgjOkR8//LBDgboHu92F96fIxBXrFcN7VNrAWZrW/nEOZcQElYMKUWUWLqZ tz4wfjcNgj2126iemLTjUAt+a1f1ssVE6ONr64adE90F9ks4nQWULICmAkpUgDgisjEn yJTpT/otXUjk0Ipur/Ifgb+tZWKd5A5GXd/R2wUNohoyXIsIaVMwkTo9Yb7vhRYtGWD0 wQPT0k9YbQs2GRSb4fdAfXxG8GPl3HmWVpbnVuwzWb1O+/dU2BgedJVbdMnsmrz0XYwK LCOw== X-Gm-Message-State: AHYfb5gaDzxg09nZFPwT95APGwvRccPx42/3rP52+6AfvMBRboPPilpk h1nKgTp14YNSQoZy+Xg= X-Received: by 10.223.129.135 with SMTP id 7mr3623239wra.11.1503912428789; Mon, 28 Aug 2017 02:27:08 -0700 (PDT) Received: from [10.100.64.20] ([217.30.88.7]) by smtp.gmail.com with ESMTPSA id 5sm10748675wre.5.2017.08.28.02.27.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Aug 2017 02:27:08 -0700 (PDT) Subject: Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???) To: Ben RUBSON Cc: Hans Petter Selasky , FreeBSD Net , hiren , Slawa Olhovchenkov , FreeBSD Stable References: <7f14c95d-1ef8-bf82-c469-e6566c3aba66@selasky.org> <76A5EE7E-1D2E-46B4-86F1-F219C3DCE6EA@gmail.com> <4C91C6E5-0725-42E7-9813-1F3ACF3DDD6E@gmail.com> <5840c25e-7472-3276-6df9-1ed4183078ad@selasky.org> <2ADA8C57-2C2D-4F97-9F0B-82D53EDDC649@gmail.com> <061cdf72-6285-8239-5380-58d9d19a1ef7@selasky.org> <92BEE83D-498F-47D5-A53C-39DCDC00A0FD@gmail.com> <5d8960d8-e1ff-8719-320f-d3ae84054714@selasky.org> <6B4A35F7-5694-4945-9575-19ADB678F9FA@gmail.com> <297a784a-3d80-b1a6-652e-a78621fe5a8b@selasky.org> <3ECCFBF1-18D9-4E33-8F39-0C366C3BB8B4@gmail.com> <0a5787c5-8a53-ab09-971a-dc1cd5f3aca0@freebsd.org> <645f2ee3-3eaa-660e-2a64-37d53e88322f@freebsd.org> <13DE4E6D-CE83-4B5D-BF88-0EFE65111311@gmail.com> <7B084207-062A-4529-B0DC-5BFEB6517780@gmail.com> From: Julien Charbon Message-ID: <82e661b4-1bac-ff5b-f776-8dba44cac15e@freebsd.org> Date: Mon, 28 Aug 2017 11:27:15 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <7B084207-062A-4529-B0DC-5BFEB6517780@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 28 Aug 2017 09:57:53 -0000 Hi Ben, On 8/28/17 10:25 AM, Ben RUBSON wrote: >> On 16 Aug 2017, at 11:02, Ben RUBSON wrote: >> >>> On 15 Aug 2017, at 23:33, Julien Charbon wrote: >>> >>> On 8/11/17 11:32 AM, Ben RUBSON wrote: >>>>> On 08 Aug 2017, at 13:33, Julien Charbon wrote: >>>>> >>>>> On 8/8/17 10:31 AM, Hans Petter Selasky wrote: >>>>>> >>>>>> Suggested fix attached. >>>>> >>>>> I agree we your conclusion. Just for the record, more precisely this >>>>> regression seems to have been introduced with: >>>>> (...) >>>>> Thus good catch, and your patch looks good. I am going to just verify >>>>> the other in_pcbrele_wlocked() calls in TCP stack. >>>> >>>> Julien, do you plan to make this fix reach 11.0-p12 ? >>> >>> I am checking if your issue is another flavor of the issue fixed by: >>> >>> https://svnweb.freebsd.org/base?view=revision&revision=307551 >>> https://reviews.freebsd.org/D8211 >>> >>> This fix in not in 11.0 but in 11.1. Currently I did not found how an >>> inp in INP_TIMEWAIT state can have been INP_FREED without having its tw >>> set to NULL already except the issue fixed by r307551. >>> >>> Thus could you try to apply this patch: >>> >>> https://github.com/freebsd/freebsd/commit/acb5bfda99b753d9ead3529d04f20087c5f7d0a0.patch >>> >>> and see if you can still reproduce this issue? >> >> Thank you for your answer Julien. >> Unfortunately, I'm not sure at all how to reproduce the issue. >> I have other servers which are 100% identical to this one, same workload, >> same some-months uptime, but they did not trigger the bug yet. >> >> If other network stack experts (I'm not) agree with your analysis, >> we could then certainly go further with D8211 / r307551. >> >> One thing that perhaps might help : >> # netstat -an | grep TIME_WAIT$ | wc -l >> 468 >> >> Note that due to this running bug, sendmail has lots of difficulties to send outgoing mails. >> As soon as I run the above netstat command, I receive a lot of stacked mails (more than 20 this time). >> As if netstat was able to somehow help... >> >> Number of TIME_WAIT connections however does not decrease, but increases. >> >>> And in the spirit of r307551 fix and based on Hans patch I will also >>> propose to add a kernel log describing the issue instead of starting an >>> infinite loop when INVARIANT is not set. >> >> Which should then never be triggered :) >> Good idea I think ! > > What about : > D8211/r307551 > + Hans' patch > + Julien's idea of a kernel log (sort of "We should not be here but we are") I did this change and I am testing it, on your side did you try this patch applied on 11.0? https://github.com/freebsd/freebsd/commit/acb5bfda99b753d9ead3529d04f20087c5f7d0a0.patch > And backporting all this to 11.0 (and so to 11.1 too) ? > > As this bug can impact every FreeBSD machine / server, > leading to an unavailable / unreachable system (this is how mine ended), > sounds like it could inevitably be a good thing, for production stability purpose. The main fix for your issue is (I believe): Fix a double-free when an inp transitions to INP_TIMEWAIT state after having been dropped. https://svnweb.freebsd.org/base?view=revision&revision=307551 This fix has been MFC-ed on both stable/11, stable/10 and is already included in 11.1 and will be in 10.4. To push in 11.0 release directly, I guess you have to promote this change to an Errata (never did that myself): https://www.freebsd.org/security/notices.html https://www.freebsd.org/security/security.html#reporting While waiting for this errata to be accepted better using the patch. My 2 cents. -- Julien From owner-freebsd-stable@freebsd.org Mon Aug 28 13:43:11 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CB17E0DC67 for ; Mon, 28 Aug 2017 13:43:11 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (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 B364F77AB5 for ; Mon, 28 Aug 2017 13:43:10 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3xgtJD1746z1D0 for ; Mon, 28 Aug 2017 15:43:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1503927784; x=1506519785; bh=O0QMNnURZFOc6NU//C9LiMmcp2r84yZqfvf FDpit0AA=; b=DQWpUxCrhnEGv0Cr7RjGiwjCqu5C7vYS0FHq58v4VGTcv4AdOfn PakXb2DIIeATARdS5vbSAeMxK3XFlINFHJZgy+4Ix9Vr3gaS7XfZjd4cPWFLTJPE QE9naVLYQGnTv1vyjcImJBE3CrzOKr6Czmoac5k2Gj/tkoZnzA6KdZDo= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id B01I0A2e-lWu for ; Mon, 28 Aug 2017 15:43:04 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3xgtJ852qnz1Cx for ; Mon, 28 Aug 2017 15:43:04 +0200 (CEST) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3xgtJ84pCSzCQ for ; Mon, 28 Aug 2017 15:43:04 +0200 (CEST) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Mon, 28 Aug 2017 15:43:04 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 28 Aug 2017 15:43:04 +0200 From: Mark Martinec To: freebsd-stable@freebsd.org Subject: syslogd include directive reads but disregards all but the last included .conf file Organization: Jozef Stefan Institute Message-ID: <6122450ad5f06579a0b740a94d694940@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.2.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 28 Aug 2017 13:43:11 -0000 Could somebody please check why the new 'include' 11.1 feature of syslogd does not work when given more than one file to include... Any chance of fixing this as a patch release to 11.1 ? > The 11.1 release brought a very desirable feature to syslogd: > > $ man syslog.conf : > A special include keyword can be used to include all files with names > ending in '.conf' and not beginning with a '.' contained in the > directory > following the keyword. > > but ... > > It turns out that of all the *.conf files found in the included > directory /etc/syslog.d, only entries found in the (alphabetically) > *last* file there are taken into account, all other entries in > remaining included files are just ignored. [...] Details at: Bug 221742 syslogd include directive reads but disregards all but the last included .conf file https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221742 Mark From owner-freebsd-stable@freebsd.org Wed Aug 30 03:35:59 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1485FDED9F1 for ; Wed, 30 Aug 2017 03:35:59 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from mail.akips.com (mail.akips.com [45.32.79.107]) (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 0A64981296 for ; Wed, 30 Aug 2017 03:35:58 +0000 (UTC) (envelope-from paul.koch@akips.com) Date: Wed, 30 Aug 2017 13:29:59 +1000 From: Paul Koch To: freebsd-stable@freebsd.org Subject: date -r {big number} results in segmentation fault Message-ID: <20170830132959.13596a93@akips.com> Organization: AKIPS 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.23 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, 30 Aug 2017 03:35:59 -0000 I had one of those in-a-hurry copy-n-paste errors... date -r 15038137211503813721 Segmentation fault Haven't had a chance to look into it yet though. This was on 11.1-RELEASE-p1 #0 r322350 Paul. -- Paul Koch | Founder | CEO AKIPS Network Monitor | akips.com Brisbane, Australia From owner-freebsd-stable@freebsd.org Wed Aug 30 03:42:59 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39B21DEDE05 for ; Wed, 30 Aug 2017 03:42:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-93.reflexion.net [208.70.210.93]) (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 DF1928186F for ; Wed, 30 Aug 2017 03:42:58 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 2437 invoked from network); 30 Aug 2017 03:48:09 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 30 Aug 2017 03:48:09 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.2) with SMTP; Tue, 29 Aug 2017 23:42:56 -0400 (EDT) Received: (qmail 13065 invoked from network); 30 Aug 2017 03:42:56 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 30 Aug 2017 03:42:56 -0000 Received: from [192.168.1.109] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id AE8E0EC913D; Tue, 29 Aug 2017 20:42:55 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r322715 - in stable/11: etc/mtree lib/libcasper lib/libcasper/services lib/libcasper/services/cap_dns lib/libcasper/services/cap_dns/tests lib/libcasper/services/cap_grp lib/libcasper/s... Message-Id: Date: Tue, 29 Aug 2017 20:42:55 -0700 To: ngie@FreeBSD.org, svn-src-stable-11@freebsd.org, FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 03:42:59 -0000 installworld for -r323012 is getting things like (at least with the = likes of -j14): --- pwd_test.install --- --- _proginstall --- install -N /usr/src/etc -s -o root -g wheel -m 555 pwd_test = /usr/obj/DESTDIRs/clang-armv7-installworld-dist-from-src/usr/tests/lib/lib= casper/services/cap_pwd/pwd_test install: pwd_test: No such file or directory *** [_proginstall] Error code 71 This was on a amd64 -> armv6 cross build and local installworld on the amd64 file system, not a live install. # svnlite status /usr/src/ | sort ? /usr/src/sys/amd64/conf/GENERIC-NODBG ? /usr/src/sys/arm/conf/GENERIC-NODBG ? /usr/src/sys/arm64/conf/GENERIC-NODBG ? /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG ? /usr/src/sys/powerpc/conf/GENERICvtsc-NODBG M /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp M /usr/src/sys/boot/powerpc/kboot/Makefile # uname -apKU FreeBSD FBSDx6411SL 11.1-STABLE FreeBSD 11.1-STABLE r323012M amd64 = amd64 1101502 1101502 # svnlite info /usr/src/ | grep "Re[plv]" Relative URL: ^/stable/11 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 323012 Last Changed Rev: 323012 =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-stable@freebsd.org Wed Aug 30 03:48:56 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDE45DEDF80 for ; Wed, 30 Aug 2017 03:48:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-93.reflexion.net [208.70.210.93]) (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 6D23581AAE for ; Wed, 30 Aug 2017 03:48:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 11497 invoked from network); 30 Aug 2017 03:48:55 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 30 Aug 2017 03:48:55 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.2) with SMTP; Tue, 29 Aug 2017 23:48:55 -0400 (EDT) Received: (qmail 16244 invoked from network); 30 Aug 2017 03:48:54 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 30 Aug 2017 03:48:54 -0000 Received: from [192.168.1.109] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 33458EC86F0; Tue, 29 Aug 2017 20:48:54 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r322715 - in stable/11: etc/mtree lib/libcasper lib/libcasper/services lib/libcasper/services/cap_dns lib/libcasper/services/cap_dns/tests lib/libcasper/services/cap_grp lib/libcasper/s... Date: Tue, 29 Aug 2017 20:48:53 -0700 References: To: ngie@FreeBSD.org, svn-src-stable-11@freebsd.org, FreeBSD-STABLE Mailing List In-Reply-To: Message-Id: <9F5FD75E-6A8F-4161-8522-78851C4D209D@dsl-only.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 03:48:56 -0000 Nevermind, stupid mistake on my part: armv6 was not actually updated yet. > On 2017-Aug-29, at 8:42 PM, Mark Millard = wrote: >=20 > installworld for -r323012 is getting things like (at least with the = likes of -j14): >=20 > --- pwd_test.install --- > --- _proginstall --- > install -N /usr/src/etc -s -o root -g wheel -m 555 pwd_test = /usr/obj/DESTDIRs/clang-armv7-installworld-dist-from-src/usr/tests/lib/lib= casper/services/cap_pwd/pwd_test > install: pwd_test: No such file or directory > *** [_proginstall] Error code 71 >=20 >=20 > This was on a amd64 -> armv6 cross build and local installworld > on the amd64 file system, not a live install. >=20 >=20 > # svnlite status /usr/src/ | sort > ? /usr/src/sys/amd64/conf/GENERIC-NODBG > ? /usr/src/sys/arm/conf/GENERIC-NODBG > ? /usr/src/sys/arm64/conf/GENERIC-NODBG > ? /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG > ? /usr/src/sys/powerpc/conf/GENERICvtsc-NODBG > M /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp > M /usr/src/sys/boot/powerpc/kboot/Makefile >=20 >=20 > # uname -apKU > FreeBSD FBSDx6411SL 11.1-STABLE FreeBSD 11.1-STABLE r323012M amd64 = amd64 1101502 1101502 >=20 >=20 > # svnlite info /usr/src/ | grep "Re[plv]" > Relative URL: ^/stable/11 > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 323012 > Last Changed Rev: 323012 =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-stable@freebsd.org Wed Aug 30 05:12:40 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4723DEF528 for ; Wed, 30 Aug 2017 05:12:40 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E7A883746; Wed, 30 Aug 2017 05:12:40 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id w191so1965039itc.1; Tue, 29 Aug 2017 22:12:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8SvR8FUf5US3ooFX9sj2FcpdWHbVLECyVdj/YFA/ix4=; b=UHfm+O/mrc/PFY40b1FDkbx8qsxy/Zvizm0lvdjAHbWZ3xaEzAq5WKDUw81cq1kinE Ik9dHA/Xe7mcPaB7YRqC1vYsgFI/a1EQa9kjSbWeBQqA678rlqocD+faKy6KtXIUC5Yn bllojpk0WC2nvX9QCXCUyZdetRfZuN0zpcOBgMttK9RcdgeoBOK62Vtl/FUn8pcRpaHS IA+WOxzvv00xRLI3lLoQuIF6RzK+pMY3rfP5nREerFwDzPqB3i3i3vaukseGw+Jww4t8 HAQtSHYJfXjooeUUk5laobhOZ9TyzPJqYtF3ddk9mZexTU9e/XITVRmeXAkxccE2C3SB rr2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8SvR8FUf5US3ooFX9sj2FcpdWHbVLECyVdj/YFA/ix4=; b=Mp62Xq6OyWToNHmM9v8mBVe+sasj6v8WEz7IEv8mg1BNEbjgv8mPDgDsu8rykUmJgL ZtJYI4G1wFVJ3I4M+oRN3UNiYSeolw+9J7YOmMTZRgn5gzhoM652wf78uy4rMiuGS8Pk QZXBB0wigguldqG4iP4iE0+ZPGE3ZO92TuD+FPOWSRhPduhcibdAIFU7qTF+YvJh+oNV 76rdUflLZmfiwlRpBAzHQeAZWaLtkoyaHNRsWMDICtx1Qz4gFhceU5tORU83Tk7ulOeA VtzkP53iVlU74vU2dAWKzChrNCwC6ummm373hz+K0YtSxU0rAMTn85nj5mzIL9Y2Gk46 9QMA== X-Gm-Message-State: AHYfb5iC6mn1/NohihnkDwwY7cqct16FDC3tevMDDezHX9X4ymnUSzp6 8RJvmSrF8U/QxF5dWIPdUdq205UildztXcs= X-Received: by 10.36.172.31 with SMTP id s31mr433569ite.74.1504069959839; Tue, 29 Aug 2017 22:12:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.33.14 with HTTP; Tue, 29 Aug 2017 22:12:39 -0700 (PDT) In-Reply-To: <20170830132959.13596a93@akips.com> References: <20170830132959.13596a93@akips.com> From: Xin LI Date: Tue, 29 Aug 2017 22:12:39 -0700 Message-ID: Subject: Re: date -r {big number} results in segmentation fault To: Paul Koch , Ed Maste Cc: FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 05:12:40 -0000 I think emaste@ have fixed it in r321293. MFC? Cheers, On Tue, Aug 29, 2017 at 8:29 PM, Paul Koch wrote: > > I had one of those in-a-hurry copy-n-paste errors... > > date -r 15038137211503813721 > Segmentation fault > > Haven't had a chance to look into it yet though. > This was on 11.1-RELEASE-p1 #0 r322350 > > Paul. > -- > Paul Koch | Founder | CEO > AKIPS Network Monitor | akips.com > Brisbane, Australia > > _______________________________________________ > 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 Wed Aug 30 07:32:42 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FC6FDF1C9F for ; Wed, 30 Aug 2017 07:32:42 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (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 660E42651 for ; Wed, 30 Aug 2017 07:32:40 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id v7U7TYJa042448 for ; Wed, 30 Aug 2017 09:29:34 +0200 (CEST) Received: from [217.29.44.214] ([217.29.44.214]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id v7U7TXuh049574 for ; Wed, 30 Aug 2017 09:29:33 +0200 (CEST) (envelope-from hausen@punkt.de) From: "Patrick M. Hausen" Content-Type: multipart/signed; boundary="Apple-Mail=_35D9B998-D020-4761-B435-5E5868EA5F60"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Bridged networking regression in 11.0? Message-Id: Date: Wed, 30 Aug 2017 09:29:35 +0200 To: freebsd-stable X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 07:32:42 -0000 --Apple-Mail=_35D9B998-D020-4761-B435-5E5868EA5F60 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, everyone, one of the systems on which we run our jail based "proServer" product = failed in a very odd way for the second time with a couple of days between the = two incidents. We run VIMAGE based jails (a lot) and bridge them with the physical = interface of the machine. --------- cloned_interfaces=3D"bridge0 bridge1" ifconfig_bridge0_name=3D"inet0" ifconfig_inet0=3D"addm ix0 up" ifconfig_inet0_alias0=3D"inet 217.29.41.2/24" ifconfig_inet0_ipv6=3D"inet6 2a00:b580:8000:11:44e8:ab80:816:7869/64 = auto_linklocal" ifconfig_bridge1_name=3D"mgmt0" ifconfig_mgmt0=3D"addm ix1 up" ifconfig_mgmt0_alias0=3D"inet 10.5.105.7/16" ifconfig_mgmt0_ipv6=3D"inet6 auto_linklocal" --------- The rest is managed by iocage wich creates the needed epair(4) = interfaces, for some reason renames them to "vnetX" and adds them as members to the bridge. E.g. --------- [ry93@ph002 ~]$ ifconfig inet0 inet0: flags=3D8843 metric 0 mtu = 1500 ether 02:50:51:fe:cc:00 inet6 fe80::50:51ff:fefe:cc00%inet0 prefixlen 64 scopeid 0x4 inet6 2a00:b580:8000:11:44e8:ab80:816:7869 prefixlen 64 inet 217.29.41.2 netmask 0xffffff00 broadcast 217.29.41.255 nd6 options=3D21 groups: bridge id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: vnet0:69 flags=3D143 ifmaxaddr 0 port 76 priority 128 path cost 2000 [... 50 vnet interfaces following ...] member: ix0 flags=3D143 ifmaxaddr 0 port 1 priority 128 path cost 2000 --------- When the system fails - no jail is reachable from the outside via IP - no jail is reachable from the host via IP - the host itself is reachable just fine - when we `iocage console` into a jail it can reach it's own IP = addresses but nothing "outside" I tried - ifconfig ix0 down; ifconfig ix0 up - ifconfig inet0 down; ifconfig inet0 up # aka bridge0 - iocage stop ; iocage start The latter deletes the epair instance connected to the jail and creates = a fresh one, then adds it to the bridge. No change in connectivity ... the start of = the jail takes "forever" because various processes hang waiting DNS timeouts (no = networking ;-) There's nothing in /var/log/messages or the dmesg buffer that relates to = networking! Rebooting the host system "fixes" the situation. Now I'm well aware that this is too little information to draw some = definite conclusions. Hence my first question is: what should I do (commands) when the = situation arises again to gather more evidence? Or maybe we are just lucky and there is a known problem? Yes, I know = VIMAGE is still considered experimental. We have been running this in production for = months and it looks like it could be related to upgrading host and jails from 10.3 to = 11.0 *or* switching the old shell based iocage for Brandon's new python based version. I cannot rule out iocage, yet it's not very probable - this is not a = Docker like running service or network component, after all. Once the jails are up, iocage is done = ... An then there's the chance that it is something with the ix driver and = the way we use the interface ... so for completeness: --------- ix0: = port 0x6020-0x603f mem 0xc7c00000-0xc7dfffff,0xc7e04000-0xc7e07fff irq = 26 at device 0.0 numa-domain 0 on pci3 ix0: Using MSIX interrupts with 9 vectors ix0: Ethernet address: 0c:c4:7a:34:ec:ba ix0: PCI Express Bus: Speed 5.0GT/s Width x8 ix0: netmap queues/slots: TX 8/2048, RX 8/2048 ix0: promiscuous mode enabled ix0: link state changed to UP --------- As usual thanks for any hints, Patrick --Apple-Mail=_35D9B998-D020-4761-B435-5E5868EA5F60 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJZpmlfAAoJEJBvLuLt2olcCcMH/1LZg6EqbDFuYbjbxGeKdi7Y lBn2573lo0+aet5ae5d+GwlPbbfLiXH78gyGMbSPR/gYYdOv6UgMQDCtBsR8FHc4 JVT+Q8tmYGEvJNn2BwXKB0Vnpx4dXEjr/cMdIjlqgKaMtpZYUdlXkQgEh9Ere79u 6OWgUvEujXRFVOpF6r9SIfR4xx++lokj/9FkjKiiSAwpbT4xVxQT7nL5xwXm6cOR HOoBPdaMPgJogeJUl0/kHVTvWOA4R/YicgIxfM2NWORoBrQovsX+MGkye6C4/fwk Pz4iZC3bDeDfD4u/S9drY0vW1xzLlLRCv0+drXNlkkoNutYkAH2/OVCF2fP0xhg= =PY8Z -----END PGP SIGNATURE----- --Apple-Mail=_35D9B998-D020-4761-B435-5E5868EA5F60-- From owner-freebsd-stable@freebsd.org Wed Aug 30 10:04:25 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6E7FDF46B1 for ; Wed, 30 Aug 2017 10:04:25 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (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 52A6765D0B for ; Wed, 30 Aug 2017 10:04:23 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id v7UA4Lat050491; Wed, 30 Aug 2017 12:04:21 +0200 (CEST) Received: from [217.29.44.214] ([217.29.44.214]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id v7UA4LN0064589; Wed, 30 Aug 2017 12:04:21 +0200 (CEST) (envelope-from hausen@punkt.de) From: "Patrick M. Hausen" Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_001E5C35-A564-4041-AE42-39368B95FE97"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Wed, 30 Aug 2017 12:04:20 +0200 Subject: Re: Bridged networking regression in 11.0? In-Reply-To: To: freebsd-stable References: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 10:04:25 -0000 --Apple-Mail=_001E5C35-A564-4041-AE42-39368B95FE97 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, all, > Am 30.08.2017 um 09:29 schrieb Patrick M. Hausen : > one of the systems on which we run our jail based "proServer" product = failed > in a very odd way for the second time with a couple of days between = the two > incidents. > [...] We found this open bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 What puzzles me is the fact that the original reporter claims that ifconfig down/up fixes the problem temporarily for him. Which in my case it didn't. But possibly I should have down/up'ed *all* bridge members not only the physical IF ... Patrick --Apple-Mail=_001E5C35-A564-4041-AE42-39368B95FE97 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJZpo2lAAoJEJBvLuLt2olc6EgH/jgdwFq40K2WRnwswSrBNSiZ zWeo8a1CXVodkfFst6SW7R9th6e71XrNLpVX9wZzFiq9iIu7gWRlmnOkpEnY4O1+ umaeVTxOvD+pUpzC3ydEzhLrESYX/GJUEGHTxnRH2CZAJUOlwkN3EJqKTzwgk39S 9wms06Qaj8X3++h6K7xQRNCTTUHGuwDPG3TcPhg6Ao2KxUGJyC0uPG7Y9/LSbtNq if/oRZVxKC0Y/4jmWy7mzUJuIUfAicgm4GY8FXlqhJqAxHP8n/bXpdrqtYu5HFkf v59O/ZJhHHT8rznggakp/ll/I5oXA07yBpGmfaYPsbBu8/+6Ne6aR5lUZpOc4Gc= =C54p -----END PGP SIGNATURE----- --Apple-Mail=_001E5C35-A564-4041-AE42-39368B95FE97-- From owner-freebsd-stable@freebsd.org Wed Aug 30 10:49:42 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 227D4DF55A0 for ; Wed, 30 Aug 2017 10:49:42 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (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 90578671AC for ; Wed, 30 Aug 2017 10:49:41 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id v7UAnb1q052627 for ; Wed, 30 Aug 2017 12:49:37 +0200 (CEST) Received: from [217.29.44.214] ([217.29.44.214]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id v7UAnbOU068605 for ; Wed, 30 Aug 2017 12:49:37 +0200 (CEST) (envelope-from hausen@punkt.de) From: "Patrick M. Hausen" Content-Type: multipart/signed; boundary="Apple-Mail=_FAFAF464-9B5D-4012-8A6C-53F0DBC4911A"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Bridged networking regression in 11.0? Date: Wed, 30 Aug 2017 12:49:37 +0200 References: To: freebsd-stable In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 10:49:42 -0000 --Apple-Mail=_FAFAF464-9B5D-4012-8A6C-53F0DBC4911A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii OK, guys, more replying to myswlf ;-) > Am 30.08.2017 um 12:04 schrieb Patrick M. Hausen : >=20 > Hi, all, >=20 >> Am 30.08.2017 um 09:29 schrieb Patrick M. Hausen : >> one of the systems on which we run our jail based "proServer" product = failed >> in a very odd way for the second time with a couple of days between = the two >> incidents. >> [...] >=20 > We found this open bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 > [...] To me it looks like not much changed in if_bridge.c from RELENG_10_3 to RELENG_11_0 ... = https://svnweb.freebsd.org/base/releng/11.0/sys/net/if_bridge.c?view=3Ddif= f&r1=3D303975&r2=3D296373&diff_format=3Dh The revisions are the topmost entries in https://svnweb.freebsd.org/base/releng/11.0/sys/net/if_bridge.c https://svnweb.freebsd.org/base/releng/10.3/sys/net/if_bridge.c respectively. Is this the correct/best way to answer the question what changed? The only real change relates to IF teardown and we did not change = anything (stop/restart jails) when the outages occured. So ... the network interface driver? Probably? ix0: = port 0x6020-0x603f mem 0xc7c00000-0xc7dfffff,0xc7e04000-0xc7e07fff irq = 26 at device 0.0 numa-domain 0 on pci3 ix0: Using MSIX interrupts with 9 vectors ix0: Ethernet address: 0c:c4:7a:34:ec:ba ix0: PCI Express Bus: Speed 5.0GT/s Width x8 ix0: netmap queues/slots: TX 8/2048, RX 8/2048 Patrick --Apple-Mail=_FAFAF464-9B5D-4012-8A6C-53F0DBC4911A Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJZpphBAAoJEJBvLuLt2olc5ucH/3mRHfA780PpOeUO1PkCWfx3 iu1QS26ZvyTNoQSvfyZLOj6Q6Ve30ahfIHuAw4iuHownGlfy7BKQyMW57JPMWzQg odcCKyJIXzhINJr77pne1HtGTvrG8gnOTaGvugls/+SCQRH5WnI4bwYJzQjjTTbw UGORhuzS+/HlV4KS9CQpOx0irKpS70aGe2E6tuh51rmQIRP+TKMYal1DfdZE3SVA OiKEPU3L9L3ctikzYJvpEvfpqQvOZAo+B0g9HfEzp1lMcnA2j9/6qbpezSvrh/zM 65S7Eo082PnhI6gz59usyCxNIdu20Jj/BtAR/kwbNyO2+gzEIE/gWowT/vBoS7c= =rsPv -----END PGP SIGNATURE----- --Apple-Mail=_FAFAF464-9B5D-4012-8A6C-53F0DBC4911A-- From owner-freebsd-stable@freebsd.org Wed Aug 30 12:01:02 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F19BDF6F7F; Wed, 30 Aug 2017 12:01:02 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC4F869A14; Wed, 30 Aug 2017 12:01:01 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qt0-x233.google.com with SMTP id u11so26099780qtu.1; Wed, 30 Aug 2017 05:01:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NpPfIuwGyGGWk7ZVbc5A7z+WG8m3+vqmefm1PV98Fss=; b=iQkcV23n1kTEOIgkHYKJ+MoOcutglEO4aj4okmgYtA/YuvoVMATobkd7phEp8qStl5 ZKfJzJGV8qBJvJ6bEkh+bvaB96u8L0Gjo0Z3yfdJyCxPIirPHrqpQmIIcr6YalRNVpEa +TyWq+Ej68rAXztiG0TzC0TfGdgKqk1VVbTIWlBfW+aYtdPj4Fh/WovRTDjcKUCsWpnD dr89hfM6y6/UocAQDrCW50r6AXK8fH80XFIoot4V1Dx5Si7tgKhZpDvxgfE1VYQRbloS dAdaonh/UdLCIfK1cG3R/rJXOOXxRZ3aD4vCBAe62j26D1u4X1pxIaCtS2mLCDTpBxql rTcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NpPfIuwGyGGWk7ZVbc5A7z+WG8m3+vqmefm1PV98Fss=; b=nUzMrmRACPKyLy3/pg779oFPpJP7f82ICfnabAAy+9olrLdrrJwj6Ml1VzFC5dWUZZ XKa6X08iUykVwisb2Vomq2J2QQIiQbMv7tVXFY/ewpsbDwRxmxUNU6b6cuZ4kWsHCmuB FgZZIkNEj6ExnZtetKOMz9MDvwyi331jD5BaK8eH8M4HnfxFHxqvC51FLacrj5puLfUt ebHVa6HPZeIT+M7blLMcpaxXZwVRtuCPbljsUyTZzBHELzLpF207JDNHOpk5pG9u5pLW VEoJHqb0lycS8x2ppm7DE0DCkj7JmQ0j8FzwV2WwRTPoRtCqlYazl0jbZB5AQnB7uf8o paGA== X-Gm-Message-State: AHYfb5iKp8WUvW+/QSigAb+0l0H14g9gG+ZG2fJfHBSVG8PoKfwBg4PQ S/6PO7Wl50yW/Tg4tgMwPKLi2sHLDW9L X-Received: by 10.200.1.207 with SMTP id b15mr1635684qtg.30.1504094455917; Wed, 30 Aug 2017 05:00:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.38.129 with HTTP; Wed, 30 Aug 2017 05:00:55 -0700 (PDT) In-Reply-To: References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> From: Cassiano Peixoto Date: Wed, 30 Aug 2017 09:00:55 -0300 Message-ID: Subject: Re: pkg issue after FreeBSD 11 upgrade To: Matthew Seaman Cc: "freebsd-ports@freebsd.org" , freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 12:01:02 -0000 Hi Matthew, Sorry back to this subject. But I really need to restart services with a port. I'm quite sure there is a bug with pkg and FreeBSD 11. I made a simple port to restart cron service: # $FreeBSD$ PORTNAME= ze PORTVERSION= 1.0 CATEGORIES= custom MASTER_SITES= # DISTFILES= # EXTRACT_ONLY= # NONE MAINTAINER= peixotocassiano@gmail.com COMMENT= ze port #NO_MTREE= yes SUB_FILES= pkg-install NO_BUILD= yes NO_WRKSUBDIR= yes do-install: mkdir -p ${STAGEDIR}${DATADIR} @${CP} -r ${FILESDIR}/versions ${STAGEDIR}${DATADIR}/ post-install: ${SH} ${PKGINSTALL} ${PKGNAME} POST-INSTALL .include Here is my pkg-install to restart cron service: #!/bin/sh if [ $2 = "POST-INSTALL" ]; then service cron restart fi Here is the output when I install the port: root@kkk:~ # service cron start cron already running? (pid=2287). root@kkk:~ # pkg install ze Updating Custom repository catalogue... Fetching meta.txz: 100% 560 B 0.6kB/s 00:01 Fetching packagesite.txz: 100% 122 KiB 62.6kB/s 00:02 Processing entries: 100% Custom repository update completed. 427 packages processed. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: ze: 1.0 Number of packages to be installed: 1 672 B to be downloaded. [1/1] Fetching ze-1.0.txz: 100% 672 B 0.7kB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Installing ze-1.0... + set -- ze-1.0 PRE-INSTALL + [ PRE-INSTALL '=' POST-INSTALL ] Extracting ze-1.0: 100% + set -- ze-1.0 POST-INSTALL + [ POST-INSTALL '=' POST-INSTALL ] + service cron restart Stopping cron. Waiting for PIDS: 2287. Starting cron. root@kkk:~ # ps ax | grep cron 2320 1 S+ 0:00.00 grep cron As you can see the cron has stopped but hasn't started. But If I install the same port with traditional ports approach it works, see: root@kkk: /usr/ports/custom/ze/# ps ax | grep cron 1280 - Is 0:00.97 /usr/sbin/cron -s root@kkk: /usr/ports/custom/ze# make install ===> ze-1.1 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by ze-1.1 for building ===> Extracting for ze-1.1 ===> Patching for ze-1.1 ===> Configuring for ze-1.1 ===> Staging for ze-1.1 ===> Generating temporary packing list mkdir -p /usr/ports/custom/ze/work/stage/usr/local/share/ze /bin/sh /usr/ports/custom/ze/work/pkg-install ze-1.1 POST-INSTALL ====> Compressing man pages (compress-man) ===> Installing for ze-1.1 ===> Checking if ze already installed Stopping cron. Waiting for PIDS: 1280. Starting cron. ===> Registering installation for ze-1.1 Installing ze-1.1... root@kkk: /usr/ports/custom/ze# ps ax | grep cron 37527 - Ss 0:00.00 /usr/sbin/cron -s Thanks for your help. On Fri, Aug 11, 2017 at 1:45 PM, Cassiano Peixoto wrote: > Hi Matthew, > > Thanks for your answer. Slapd is just an example, it happens with any > application like apache, mysql, dovecot and others. > > I can see the process is running and up, and it dies after pkg process has > finished. Looks like pkg is killing any application related to its thread. > > I know it's not the best approach, but used to work on FreeBSD 10. > > Anyway, I'll change my script to restart services out of pkg process. > > Thanks. > > On Fri, Aug 11, 2017 at 5:09 AM, Matthew Seaman > wrote: > >> On 10/08/2017 22:05, Cassiano Peixoto wrote: >> > I ran into an issue after FreeBSD 11 upgrade. I have some meta ports >> that >> > starts services like slapd. >> > >> > Its has been working fine on 10-STABLE. But after FreeBSD >> > 11-STABLE r321625M upgrade it stopped working. >> > >> > Here is a simple example of my pkg-install.in script: >> > >> > #!/bin/sh >> > /usr/local/etc/rc.d/slapd stop >> > /usr/local/etc/rc.d/slapd start >> > >> > I can see its executing while upgrading a package: >> > >> > Stopping slapd. >> > Waiting for PIDS: 13875. >> > Starting slapd. >> > >> > But looking if the process is running, it's not: >> > >> > # ps ax | grep slapd >> > 14164 0 S+ 0:00.00 grep slapd >> > >> > Then I manually run the rc.d script and the service starts: >> > >> > # /usr/local/etc/rc.d/slapd restart >> > slapd not running? (check /var/run/openldap/slapd.pid). >> > Starting slapd. >> > >> > So my question is: something has changed on FreeBSD 11 not allowing this >> > kind of execution? >> > >> > BTW, I'm using pkg 1.10.1 and my ports collection is as same as I was >> using >> > on FreeBSD 10. >> >> Restarting daemons after upgrading is something the project has been >> quite resistant to implementing. Mostly because as soon as you start >> looking into it in any depth the true complexity of doing that sort of >> thing reliably for any conceivable system becomes apparent and you end >> up muttering darkly about systemd and losing the will to live. >> >> However, yes, restarting slapd -- it's clear that your script does get >> called, but slapd fails to start at that point during the upgrade >> process. slapd is well known (at least to me) for failing to start >> /silently/ -- you need to check the process is actually there after >> trying to start it, and look at the logfiles and so forth. It also >> seems to quit at the slightest provocation, presumably to avoid any >> potential for data corruption. >> >> So check you logs to see why slapd didn't start. It's quite possible >> that it was simply that something else that slapd needed wasn't >> available at that exact point during the upgrade process, and just >> waiting until the upgrade had finished would sort things out. >> >> Cheers, >> >> Matthew >> >> > From owner-freebsd-stable@freebsd.org Wed Aug 30 12:48:56 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2918E00F20; Wed, 30 Aug 2017 12:48:56 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-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 BDD236B399; Wed, 30 Aug 2017 12:48:56 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 1189A1F84C; Wed, 30 Aug 2017 12:48:56 +0000 (UTC) Date: Wed, 30 Aug 2017 14:48:55 +0200 From: Baptiste Daroussin To: Cassiano Peixoto Cc: Matthew Seaman , freebsd-stable@freebsd.org, "freebsd-ports@freebsd.org" Subject: Re: pkg issue after FreeBSD 11 upgrade Message-ID: <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="iwilfg3mpwxm4orf" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170714 (1.8.3) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 12:48:57 -0000 --iwilfg3mpwxm4orf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 30, 2017 at 09:00:55AM -0300, Cassiano Peixoto wrote: > Hi Matthew, >=20 > Sorry back to this subject. But I really need to restart services with a > port. I'm quite sure there is a bug with pkg and FreeBSD 11. >=20 > I made a simple port to restart cron service: It is not a bug, it is by design, pkg becomes the reaper of the scripts it = runs and kills everything once the script is executed. btw if you install crontab in cron.d you do not need to restart the service, cron will figure out itself and reload what it needed. Bapt --iwilfg3mpwxm4orf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlmmtDUACgkQY4mL3PG3 Plpciw/7BpzAPh+s3Y/DtoCKai+2fdmmNeBvI/AUZpyKedxAUY3dDm36hnEAsw2U YRiWHT2C4SLCE+fvxDj8NFPXR5NXdrZ4leBPAQzcSkPFJozLHvQrOswl7v9/MKiZ QIpJV49xhjSnubWpyN+Cpa5Am46hmjLOXWNF+nrTgln8gh5tMTZIwTkw/HK0tWeF UBGR55T43iezGREbC86qdswrV2Ysnlcd7BHazsU/U9r1oUjT6LNrfgM8HyXRLmyM 7kdpeEfYmWl4mQ+wBGtTFTDDqC80HVthffqSes7pQfmSTio2xLOuza+9mjD1dZen RNaRJchVRVEfN4BP6sel7OlJFCNbgBCrGM6cMcp3H7rzbQWpHnq7bdurXOT9XDXe Jpz9t+fDh2CyKEY59ZlGDC4oI+/ZxT1hxCwzLHu+h5D7JczEo+kXQc+Hr83hFWcD dCkPaZuo8izt++V2mpaa2LSetcl2jI3hrVTh99JmmmXdTrPVuxT6Tm7ssJVcWR+L 6nj72w+zVs3M2USZS4hQa7LCoDp23zdZbwtBOELyAYHCsjGaXXuug25nWi99O/+P 1SfZWDsKprZKipZt+fWXHQW+Qu4HeumNUK4pCW0XIr/8j7A7Ge7LHOh+iRHklvJ4 o/aStqMKIRoH0y2FfvthNllpkmycd/utX6eksq6dLiCgpoPhDHs= =ZKUk -----END PGP SIGNATURE----- --iwilfg3mpwxm4orf-- From owner-freebsd-stable@freebsd.org Wed Aug 30 12:54:29 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51545E01217 for ; Wed, 30 Aug 2017 12:54:29 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [128.127.144.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C47A26B8C1 for ; Wed, 30 Aug 2017 12:54:27 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. (net206-94.perm.ertelecom.ru [46.146.206.94] (may be forged)) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id v7U9jFAN006816 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 30 Aug 2017 14:45:18 +0500 (YEKT) (envelope-from emz@norma.perm.ru) To: freebsd-stable@freebsd.org From: "Eugene M. Zheganin" Subject: zfs, iSCSI and volmode=dev Message-ID: Date: Wed, 30 Aug 2017 14:45:15 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spamd-Result: default: False [2.92 / 25.00] BAYES_HAM(-1.58)[92.33%] HFILTER_HOSTNAME_UNKNOWN(2.50)[] RBL_SPAMHAUS_PBL(2.00)[94.206.146.46.zen.spamhaus.org : 127.0.0.10] RCVD_COUNT_1(0.00)[] MID_RHS_MATCH_FROM(0.00)[] FROM_EQ_ENVFROM(0.00)[] RCPT_COUNT_1(0.00)[] ONCE_RECEIVED(0.10)[] MIME_GOOD(-0.10)[text/plain] TO_DN_NONE(0.00)[] DMARC_NA(0.00)[norma.perm.ru] RECEIVED_SPAMHAUS(0.00)[94.206.146.46.zen.spamhaus.org] R_DKIM_NA(0.00)[] FROM_HAS_DN(0.00)[] TO_MATCH_ENVRCPT_ALL(0.00)[] R_SPF_SOFTFAIL(0.00)[~all] X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 0.98 X-Rspamd-Queue-ID: v7U9jFAN006816 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 12:54:29 -0000 Hi, I have an iSCSI production system that exports a large number of zvols as the iSCSI targets. System is running FreeBSD 11.0-RELEASE-p7 and initially all of the zvols were confugured with default volmode. I've read that it's recommended to use them in dev mode, so the system isn't bothered with all of these geom structures, so I've switched all of the zvols to dev mode, then I exported/imported the pools back. Surprisingly, the performance has fallen down like 10 times (200-300 Mbits/sec against 3-4 Gbits/sec previously). After observing for 5 minutes the ESXes trying to boot up, and doing this extremely slowly, I switched the volmode back to default, then again exported/imported the pools. The performance went back to normal. So... why did this happen ? The result seems to be counter-intuitive. At least not obvious to me. Thanks. Eugene. From owner-freebsd-stable@freebsd.org Wed Aug 30 12:55:24 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DF9BE012F7; Wed, 30 Aug 2017 12:55:24 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F0476BACD; Wed, 30 Aug 2017 12:55:24 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x22f.google.com with SMTP id l65so27366081qkc.0; Wed, 30 Aug 2017 05:55:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3Ma4nnzqgRm0wWTndLhmOkASU+DqbW9BS+sm+tdMC6c=; b=s3WwfvccmgfZrVvZw5mH2VuGzfolWTkCGFBzvY4sOL8yahJtThy6n1K82g42X0uqz1 v4Goyov/8i351wsVovW/VA5i7UoFFxAmk2Zr+zDlXJB8Pxl664sGxTFsMEm/SnmgkC+w 0g3LB+DdR2+G4lD85iovsUR3++h69nMqw8Tgxx33ebxxiAd2ra/9mBPX+XCFU3skxG6U HI18EljUEai2+4xrEIHWrmkSsYUqN3pJTzuw8GcGeLEBVbjaG3nqqYy/pqF09O3MgsH+ ILSDK3DO28o9WEZgAPJOJYuzyU9RzuO0J+0ckz3oGJsYpn/bmF9Te0Xfu4++0OE+FrQ2 C3OQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3Ma4nnzqgRm0wWTndLhmOkASU+DqbW9BS+sm+tdMC6c=; b=ePmhPbs+VOpj9h2mH9aWqM7krmZgiwXVE3+bOvXgkH4obgZIsrYGMm4fJy0YUkZes4 LvASpqDGcd+0iFhCd3LpH8b5xfRa/5g3QIXvhbnTUSIgC1ZhjhGb5T1JE4LXoIMKwbS0 vSoaxRB+skKKJJOs0cO6YYzh504MeD1BHZRXIzTadfrPRfLA2jA8Ey9R/tOZWiJcAEFl qqY+myIfSlZ2s+Q7F7Wtnbd6ccKtzrWHEnbKGHUlBEgic+rFiKJj/SNAh4uDbRGwmfx+ 4MlbRG7ywo0WKxGhk3M0oksW09KAwfTb4PhRZJuh12DcPMkVgTULYn70gPq8jrQrOVJg AY+g== X-Gm-Message-State: AHYfb5jnIroXS4GCNwBQK+FY0hXxWhvZpgoYJ0u0GIKBIBMf043alZ+0 4vSY915Ty1mpsQQphGRkefIyjrE4Kg== X-Received: by 10.55.27.96 with SMTP id b93mr9975411qkb.282.1504097723006; Wed, 30 Aug 2017 05:55:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.38.129 with HTTP; Wed, 30 Aug 2017 05:55:22 -0700 (PDT) In-Reply-To: <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> From: Cassiano Peixoto Date: Wed, 30 Aug 2017 09:55:22 -0300 Message-ID: Subject: Re: pkg issue after FreeBSD 11 upgrade To: Baptiste Daroussin Cc: Matthew Seaman , freebsd-stable@freebsd.org, "freebsd-ports@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 12:55:24 -0000 Hi Baptiste, Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. Cron is just an example, I manage more than 50 FreeBSD servers, and I've been using ports for years to update some configs and restart the service on all of them. Many times I need to change nginx config, ldap, etc. I just need to restart the service. Is there some flag to disable it? Or some hack that I could do? Thanks. On Wed, Aug 30, 2017 at 9:48 AM, Baptiste Daroussin wrote: > On Wed, Aug 30, 2017 at 09:00:55AM -0300, Cassiano Peixoto wrote: > > Hi Matthew, > > > > Sorry back to this subject. But I really need to restart services with a > > port. I'm quite sure there is a bug with pkg and FreeBSD 11. > > > > I made a simple port to restart cron service: > > It is not a bug, it is by design, pkg becomes the reaper of the scripts it > runs > and kills everything once the script is executed. > > btw if you install crontab in cron.d you do not need to restart the > service, > cron will figure out itself and reload what it needed. > > Bapt > From owner-freebsd-stable@freebsd.org Wed Aug 30 12:59:52 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21BBEE014A2; Wed, 30 Aug 2017 12:59:52 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.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 CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1B426BD97; Wed, 30 Aug 2017 12:59:51 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 223B61FCCD; Wed, 30 Aug 2017 12:59:51 +0000 (UTC) Date: Wed, 30 Aug 2017 14:59:50 +0200 From: Baptiste Daroussin To: Cassiano Peixoto Cc: Matthew Seaman , freebsd-stable@freebsd.org, "freebsd-ports@freebsd.org" Subject: Re: pkg issue after FreeBSD 11 upgrade Message-ID: <20170830125950.mcp34sddcp6c757t@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mlwiwldfnfnqq37l" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170714 (1.8.3) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 12:59:52 -0000 --mlwiwldfnfnqq37l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote: > Hi Baptiste, >=20 > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in fr= eebsd kernel appeared in 10.2 >=20 > Cron is just an example, I manage more than 50 FreeBSD servers, and I've > been using ports for years to update some configs and restart the service > on all of them. Many times I need to change nginx config, ldap, etc. I ju= st > need to restart the service. HANDLE_RC_SCRIPTS=3Dtrue in your pkg.conf and pkg will automatically restart anything rc script provide once the package containing it is upgrading. This is off by default because in many cases it is dangerous (database upgr= ades, dovecot like things upgrade etc). But if you know what you are doing it doe= s the job. Best regards, Bapt --mlwiwldfnfnqq37l Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlmmtrgACgkQY4mL3PG3 PlqHEw/+MRYsI8ooPOcoCefWAd0FuPycC1zNtZfSTEnKXibcq6l7TNS8eHVC5f6S UPPwPetke/+UIM6AKXtVHyi+ZKh8BFQk/OcbHEUceOdNKnA5goFB10oexKPdqdid 5XXZ+yqj2msrW2liEzcpfwk0M4W3bTS9OmAv0IRqCasln18r29CC/cq91j32ZBWw vvSLPUBeC/+dxYsL0y30rmh4CZvev+71B65OeBmrOTgpiYF/bJOUaT+BeB54RetC 2538jyRpodOOvgcwywT9o4YSDqX4M8mFFRl89/eZsYI28/BJSVOb0nlQ2OqO9nb2 AfCaeNixSoVy26oNV3L3bjUANc1sb8ziiu/YozmHjuZ5L6B8lSQnYdAgoXJUgSKs vJnHGHZn2owboL04wkoteHGzhlj8WfvhnrYFjP1jEkSuXiQAjFnDkMkDwlH4NVVy UjUW2LKNCyLiTDU+heu7tRCZgYBDDqMERV2DrIGCi9fEn/ZgbyTxI2kSjpRMvhRK TNUAu8OOLZUpMkJYf8/bnMq1Bk1t0k1JFu2xDoVAu3I32/j/iaUgPdZG6q34y0Uh KBN4LwqJw4vhuK7RK8KsuLyriLiY9Xpy4968dWOuxBivjHud015SR/kzbbiwhkS2 jqiCwpdTcuAdjNA6I3dehwA9Ro3iP2fHNxHF4XJC5TXislgN230= =2bkK -----END PGP SIGNATURE----- --mlwiwldfnfnqq37l-- From owner-freebsd-stable@freebsd.org Wed Aug 30 13:01:45 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40765E0172B; Wed, 30 Aug 2017 13:01:45 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (unknown [IPv6:2a01:4f8:a0:51d6::108: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 059CD6C18B; Wed, 30 Aug 2017 13:01:45 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.seppmail (business-24-134-14-193.pool2.vodafone-ip.de [24.134.14.193]) by host64.shmhost.net (Postfix) with ESMTPSA id BC5D28117B; Wed, 30 Aug 2017 15:01:31 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: pkg issue after FreeBSD 11 upgrade From: Franco Fichtner In-Reply-To: Date: Wed, 30 Aug 2017 15:01:30 +0200 Cc: Baptiste Daroussin , freebsd-stable@freebsd.org, Matthew Seaman , "freebsd-ports@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> To: Cassiano Peixoto X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-Spam-Flag: NO X-Spam-Score: -1.0 X-Spam-Status: No score=-1.0 tagged_above=10.0 required=10.0 tests=[ALL_TRUSTED] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 13:01:45 -0000 Hi Cassiano, > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto = wrote: >=20 > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 = only. It was a later 10.x change as far as I know. > Is there some flag to disable it? Or some hack that I could do? No. At OPNsense we use a patch to revert the behaviour. = https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-l= ibpkg_scripts.c Cheers, Franco= From owner-freebsd-stable@freebsd.org Wed Aug 30 13:05:05 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99AC8E018F9; Wed, 30 Aug 2017 13:05:05 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.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 CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75D5B6C477; Wed, 30 Aug 2017 13:05:05 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id D122D1FF24; Wed, 30 Aug 2017 13:05:04 +0000 (UTC) Date: Wed, 30 Aug 2017 15:05:04 +0200 From: Baptiste Daroussin To: Franco Fichtner Cc: Cassiano Peixoto , freebsd-stable@freebsd.org, Matthew Seaman , "freebsd-ports@freebsd.org" Subject: Re: pkg issue after FreeBSD 11 upgrade Message-ID: <20170830130504.kgbwkztaomnqq3hy@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="u7bfalyehqj2uupg" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170714 (1.8.3) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 13:05:05 -0000 --u7bfalyehqj2uupg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 30, 2017 at 03:01:30PM +0200, Franco Fichtner wrote: > Hi Cassiano, >=20 > > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto wrote: > >=20 > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. >=20 > It was a later 10.x change as far as I know. >=20 > > Is there some flag to disable it? Or some hack that I could do? >=20 > No. At OPNsense we use a patch to revert the behaviour. >=20 > https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-= libpkg_scripts.c Why and what is your use case, there is a reason why this code has been add= ed, and I would like to hear more about use cases so we can try to address them. Best regards, Bapt --u7bfalyehqj2uupg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlmmuAAACgkQY4mL3PG3 PlqxuQ//flVXRlQHww9kjQ9i7iVEVLKcodNCqX6mHQTLmp/fuYBmDILgw4My5IPK xJzcR8FPfeiNSuPRL3jAXKwrWoSc2w+HgnGO8AsCPULHNuylsVIoAqe1L/dibjfn LmxekNfiZgb/mrcKswjZRfLxyhLNkkhqoKt4bIeMBgtHvRa8DKFIImuJnwZLVYiz MpeUyJSLGYrdcO+0xyZwXVVCElz2FZV9OlbC+WYlJBbIvStIybEmix5ZavuWMGgj lcEOt2iNuPiGB7R1O3Og+X3hGsSRf4BxnRYQW4aiHc0HUjYO5MlHtdWYgL7Xt3JZ Ztanh6YOFGavYPHbG4//fIuvPz3Lx7olrrCreWP6IjbwNlcKDxnctWo1SnjUzS/A jbj70jpN8MgUa/tZFq2rrdLf3kAF/4mR52xdTR06NcvZmWmfAld+p7NmBnprmkax FgYZ2g6HdyCY132dOBejJ5Iq6yjmg5TpVaVjjdThezLMxMs1FtjuL83V/c3RP8lt 5CrTvzWEyMPSxz7xNzGShRNSurv97gPc0M4kbUqgMhQNL8UQgGv+b0tgOK07j1WV kJADTLFjrNJcwzc8EjxhHHh5GI1VCiL9QMpE/ZnEdj7Qf1HoI4oNKOy4WNtQYrQW rk4O9X/UBRbia9L4aZMn1gBH+rDXZ1V/j9ldo7LrpCfg5FH2tFs= =aLYO -----END PGP SIGNATURE----- --u7bfalyehqj2uupg-- From owner-freebsd-stable@freebsd.org Wed Aug 30 13:07:53 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F253EE01A76; Wed, 30 Aug 2017 13:07:53 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A91446C6BD; Wed, 30 Aug 2017 13:07:53 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x22b.google.com with SMTP id a77so27500339qkb.1; Wed, 30 Aug 2017 06:07:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3pzK1xcTM9zB0Bapo1Ar8wmDHGqDnzxrw+BsxRMVbAQ=; b=FjBqvLbdlYO7p/vSHjuY4kU9P76IM2sXiSPQNiZxJpWlJ/uYwxDD0/xqvXwQs/+gyw eXHx9YNEr/YjmRldFeSjgm0O9sh5tzsNbxDDbnKmj6qtb4WJ3nvr9+fIR/GmqDdOp4dQ ZdEfednHGsmazgpIEyuTvtJDhndUweK/gIeqf2TiI57OOGKEO0OwY5fFY5zsBBetmbGE HDqeb/alBUjLMFMzRhh0pKngyGQ6AyW4wcMMg05aewVYjr4tY/rTNdsJlfixk0tyjr3Y s5mECt3aEDdMVDlDApZOlHVTvSPK4qxDLpgUnCW9G1njNxBzckq268F/lXnCmts8qn1t U+/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3pzK1xcTM9zB0Bapo1Ar8wmDHGqDnzxrw+BsxRMVbAQ=; b=odi8LNO04StnZI7M1zeeJlxroeyD7/yMEN2tiTV4Y2bPty8c6rhisFUuw6iAHng9lC TuKt1bLZ+QzvU5cwLUJmAX+1UJtwYRSTnblYXkb8NllFW7tBl7XBzyY/1SnsC8wcVUhR hhwVB+7J5nL+QftTxmPQ1H9pRdWRIVsmeY9uu3iuioMMgFnbB7iYquWfTqImVWHRSoLb 9PPD3ypaRUbV4MiaFm4AVw3QeqJimjQs2j3HvlkpcpIYHhbHJeuQa2kZbZ4VsQDBmMN4 xP4I5Hzyk06kwgIBbllg5ft9c6Da1kMof3q9K2itzzYItudK/BVYHTROMLN9mUrQWGWo iZqg== X-Gm-Message-State: AHYfb5ipfKcqcodx5r6ZMymscXRUxMGRSsuZB1/FGYrpULGGxTzC8mFe 62nfyzo7ZNGNjhvajHpCDfXIwSuTvImfDac= X-Received: by 10.55.97.76 with SMTP id v73mr1546612qkb.90.1504098472310; Wed, 30 Aug 2017 06:07:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.38.129 with HTTP; Wed, 30 Aug 2017 06:07:51 -0700 (PDT) In-Reply-To: <20170830125950.mcp34sddcp6c757t@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> <20170830125950.mcp34sddcp6c757t@ivaldir.net> From: Cassiano Peixoto Date: Wed, 30 Aug 2017 10:07:51 -0300 Message-ID: Subject: Re: pkg issue after FreeBSD 11 upgrade To: Baptiste Daroussin Cc: Matthew Seaman , freebsd-stable@freebsd.org, "freebsd-ports@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 13:07:54 -0000 Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal with when I need to restart a service without upgrading? Reaper functionnality is a trouble for many administrators who made meta ports to manage their servers. I really think it could be a option to be enabled/disabled. Can you see this possibility? Thanks. On Wed, Aug 30, 2017 at 9:59 AM, Baptiste Daroussin wrote: > On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote: > > Hi Baptiste, > > > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. > > It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in > freebsd > kernel appeared in 10.2 > > > > Cron is just an example, I manage more than 50 FreeBSD servers, and I've > > been using ports for years to update some configs and restart the service > > on all of them. Many times I need to change nginx config, ldap, etc. I > just > > need to restart the service. > > HANDLE_RC_SCRIPTS=true in your pkg.conf and pkg will automatically restart > anything rc script provide once the package containing it is upgrading. > > This is off by default because in many cases it is dangerous (database > upgrades, > dovecot like things upgrade etc). But if you know what you are doing it > does the > job. > > Best regards, > Bapt > From owner-freebsd-stable@freebsd.org Wed Aug 30 13:15:15 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29B3BE01D82; Wed, 30 Aug 2017 13:15:15 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D412B6CBD1; Wed, 30 Aug 2017 13:15:14 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x22d.google.com with SMTP id a77so27594439qkb.1; Wed, 30 Aug 2017 06:15:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AF0FnDIIAfE6sXeuI5tje0jc1+guNiMqwxAPq93cFXA=; b=p1ZGPhqt4jZJzbkKySBYkPMjCktAkp8872UwRo8NrsGuSeQlLrcGM6kD2wzhn6NAuP +rqs1ypuLdui+ZAqy7C9YaFMloSxa9694Qdl9AEvfo+guWsobo9dmkNii76+eJgJWSa6 jBQJtfhbq4WnMP3a32tmMwvwbKiFdvEd/xk6R5J1uN24SGVuL4ZW7FjFcWL96RP9ozHa yL0MZHeB8VnS/4ltLZ9G7hY6nF5Q3jOCXt28jx4VGCNHr9LRpN9vqFbdx+6sCYkJGcFj 4EBSTEhjVfdlMWr6c/wf2mnC1lJiMTSyd6IrPIdRAsWoVhPaqG2n/p6CKUDYY7AfqDqy wltw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AF0FnDIIAfE6sXeuI5tje0jc1+guNiMqwxAPq93cFXA=; b=czQjtu1xwvgWUTfjvEIFW1WYI1b49BR6h9acVP9W19GhThPNGKzu1LI+WWTq6P31GD jZSlcnYFoiDNJc/XXLI60vKEl76UmsDyRBBjsjIXTKmEsIcTBraxJoJF8G70hV0itM1W iU918tJ04Obb62k+smq+J0B7o3BABqwEyY1uluVwt+XekjjNbSrMUfeQa6++kQMS5OL5 O+4u6Le2uUzclQwoZLMFcKcOKGrN2veQzqyAVZKf1GIMc2PbGK/rsVCvXo7ldLvpUjXo O0Du0LiVkskLQjesKY/LKiYOttcjTWIFjRv2Uey4OzcJ2p3IBX+heoTNYQqZH7OXMPg/ CcAA== X-Gm-Message-State: AHYfb5hSmtYa2QdbB691thN0RvUTXWXyMEUPo1tWMu92cnb9VDVNqVTt m5WT6fyaSgtBKGXrkILhcz5Pzkukf/Ke X-Received: by 10.55.97.76 with SMTP id v73mr1584232qkb.90.1504098913900; Wed, 30 Aug 2017 06:15:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.38.129 with HTTP; Wed, 30 Aug 2017 06:15:13 -0700 (PDT) In-Reply-To: References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> From: Cassiano Peixoto Date: Wed, 30 Aug 2017 10:15:13 -0300 Message-ID: Subject: Re: pkg issue after FreeBSD 11 upgrade To: Franco Fichtner Cc: Baptiste Daroussin , freebsd-stable@freebsd.org, Matthew Seaman , "freebsd-ports@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 13:15:15 -0000 Hi Franco, Thank you. You know what I'm suffering. As I said in my last email I think it would be an option to enable/disable. I just upgraded my customers servers to FreeBSD 11 and I just realized it. I think when more admins who maintain this kind of port (needing to restart services), as soon as they migrate they will face the same problem. On Wed, Aug 30, 2017 at 10:01 AM, Franco Fichtner wrote: > Hi Cassiano, > > > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto > wrote: > > > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. > > It was a later 10.x change as far as I know. > > > Is there some flag to disable it? Or some hack that I could do? > > No. At OPNsense we use a patch to revert the behaviour. > > https://github.com/opnsense/ports/blob/master/ports-mgmt/ > pkg/files/patch-libpkg_scripts.c > > > Cheers, > Franco From owner-freebsd-stable@freebsd.org Wed Aug 30 13:23:43 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53649E020FA; Wed, 30 Aug 2017 13:23:43 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (unknown [IPv6:2a01:4f8:a0:51d6::108: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 0BFFD6D1D6; Wed, 30 Aug 2017 13:23:43 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.seppmail (business-24-134-14-193.pool2.vodafone-ip.de [24.134.14.193]) by host64.shmhost.net (Postfix) with ESMTPSA id 8E41A866B7; Wed, 30 Aug 2017 15:23:40 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: pkg issue after FreeBSD 11 upgrade From: Franco Fichtner In-Reply-To: <20170830130504.kgbwkztaomnqq3hy@ivaldir.net> Date: Wed, 30 Aug 2017 15:23:39 +0200 Cc: Cassiano Peixoto , freebsd-stable@freebsd.org, Matthew Seaman , "freebsd-ports@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <26A778CD-11ED-4DAF-A2A8-7D0E263430A1@lastsummer.de> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> <20170830130504.kgbwkztaomnqq3hy@ivaldir.net> To: Baptiste Daroussin X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-Spam-Flag: NO X-Spam-Score: -1.0 X-Spam-Status: No score=-1.0 tagged_above=10.0 required=10.0 tests=[ALL_TRUSTED] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 13:23:43 -0000 Hi Baptiste, > On 30. Aug 2017, at 3:05 PM, Baptiste Daroussin = wrote: >=20 >> No. At OPNsense we use a patch to revert the behaviour. >>=20 >> = https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-l= ibpkg_scripts.c >=20 > Why and what is your use case, there is a reason why this code has = been added, > and I would like to hear more about use cases so we can try to address = them. There's to things in this patch. (1) The hard fail for scripts leaves a GUI-driven environment without its package, so post-install fails become fatal and appliances are completely stranded, possibly left without means of recovery. This is where FreeBSD base and the "appliance" GUI packages are = completely separated. This is somewhat mitigated by marking said GUI package vital, but vital won't help if the package was deinstalled during an upgrade and then the upgrade script itself fails. Every now and then, I see "user disappeared" during package installs on stock FreeBSD systems so the install fails. I am guessing that's the same issue. (2) The reaper kills a package-based watchdog / backend service. Maybe HANDLE_RC_SCRIPTS can cope with this, but it would be beneficial to be able to enable this per package / rc service / metadata as generally the reaper is a fine and sane addition. Cheers, Franco= From owner-freebsd-stable@freebsd.org Wed Aug 30 14:11:03 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 318ACE02F52; Wed, 30 Aug 2017 14:11:03 +0000 (UTC) (envelope-from crees@physics.org) Received: from mail37c50.megamailservers.eu (mail161c50.megamailservers.eu [91.136.10.171]) (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 56D2D6E94F; Wed, 30 Aug 2017 14:11:01 +0000 (UTC) (envelope-from crees@physics.org) X-Authenticated-User: bayofrum.uwclub.net Received: from pegasus.bayofrum.net (host-80-41-56-156.as13285.net [80.41.56.156]) (authenticated bits=0) by mail37c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id v7UDr6Ai001600; Wed, 30 Aug 2017 13:53:08 +0000 Received: from [192.168.1.150] (zeus.bayofrum.net [192.168.1.150]) by pegasus.bayofrum.net (Postfix) with ESMTPSA id 7D080801DD; Wed, 30 Aug 2017 14:51:49 +0100 (BST) Subject: Re: pkg issue after FreeBSD 11 upgrade To: Cassiano Peixoto , Baptiste Daroussin Cc: freebsd-stable@freebsd.org, Matthew Seaman , "freebsd-ports@freebsd.org" References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> <20170830125950.mcp34sddcp6c757t@ivaldir.net> From: Chris Rees Message-ID: Date: Wed, 30 Aug 2017 14:51:49 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-bayofrum-MailScanner-Information: Please contact the ISP for more information X-bayofrum-MailScanner-ID: 7D080801DD.A05FC X-bayofrum-MailScanner: Found to be clean X-bayofrum-MailScanner-From: crees@physics.org X-Spam-Status: No X-CTCH-RefID: str=0001.0A0B0201.59A6C344.011E, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.2 cv=LIoWeNe9 c=1 sm=1 tr=0 a=eImF4KVNE/MQsd0gg/pNFQ==:117 a=eImF4KVNE/MQsd0gg/pNFQ==:17 a=IkcTkHD0fZMA:10 a=KeKAF7QvOSUA:10 a=6I5d2MoRAAAA:8 a=FWAKdnKL9gblLq5QA-kA:9 a=QEXdDO2ut3YA:10 a=IjZwj45LgO3ly-622nXo:22 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 14:11:03 -0000 Cassiano Peixoto wrote: > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal > with when I need to restart a service without upgrading? Reaper > functionnality is a trouble for many administrators who made meta ports to > manage their servers. I really think it could be a option to be > enabled/disabled. Can you see this possibility? > > Thanks. > > On Wed, Aug 30, 2017 at 9:59 AM, Baptiste Daroussin > wrote: > >> On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote: >>> Hi Baptiste, >>> >>> Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. >> It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in >> freebsd >> kernel appeared in 10.2 >>> Cron is just an example, I manage more than 50 FreeBSD servers, and I've >>> been using ports for years to update some configs and restart the service >>> on all of them. Many times I need to change nginx config, ldap, etc. I >> just >>> need to restart the service. >> HANDLE_RC_SCRIPTS=true in your pkg.conf and pkg will automatically restart >> anything rc script provide once the package containing it is upgrading. >> >> This is off by default because in many cases it is dangerous (database >> upgrades, >> dovecot like things upgrade etc). But if you know what you are doing it >> does the >> job. >> >> Best regards, >> Bapt >> > Hey, I think you also want process supervision given your other comments. You can do this easily using daemon -P to run your scripts (but you'd need to rewrite the rc script...) Or use runit or similar? You could implement "runlevels" with that if that's REALLY what you want :) Cheers, Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@freebsd.org Wed Aug 30 14:34:28 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08B5DE035F5; Wed, 30 Aug 2017 14:34:28 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-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 D80066F618; Wed, 30 Aug 2017 14:34:27 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 380931389; Wed, 30 Aug 2017 14:34:27 +0000 (UTC) Date: Wed, 30 Aug 2017 16:34:27 +0200 From: Baptiste Daroussin To: Cassiano Peixoto Cc: Matthew Seaman , freebsd-stable@freebsd.org, "freebsd-ports@freebsd.org" Subject: Re: pkg issue after FreeBSD 11 upgrade Message-ID: <20170830143426.r53pztrybmmvfy6c@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> <20170830125950.mcp34sddcp6c757t@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vcnzoghu4f62oozl" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170714 (1.8.3) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 14:34:28 -0000 --vcnzoghu4f62oozl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixoto wrote: > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal > with when I need to restart a service without upgrading? Reaper > functionnality is a trouble for many administrators who made meta ports to > manage their servers. I really think it could be a option to be > enabled/disabled. Can you see this possibility? >=20 Yes I could add an option to disable the reaper functionnality (and will probably to unblock such use case as soon as I have time to do it.) However I still think this is not the right idea :) and a better one could = be found Bapt --vcnzoghu4f62oozl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlmmzOwACgkQY4mL3PG3 PloL3w/8C6qQd7JhPXERMD8QLSgFiRo4ZRp/yObh5igDZcIIs8hPQgGKviHFPSfr sgfi+2LyaTv6sNtblHlvaSNSjUlV8iUGdNEUpJ/uG4ELqYpgSP8+G/yuXbcZ8yh9 xfMUgwRsxH1KTdzRlIapAVgvWnfXB691D9AuJMs+6jhpYf3fgH7Qhrz+BWZjVS2o qZy/ga/aML+Xjs11ByButtjby3z9H/ASxEWxuTJQvkzcoyhX2H7MoqyoHN4oB2yC G0jZkSf4itwRtCHz1/pLZ3LjdoJSTB+EOK9gNKnbsEtD2RgXSARTo64PIdrzjJtj nBe877Fmwuqg+lRi3wpKfxYTiNOIL9Nyv4F7tfJy9k8FF5H/Oq+vt1jDRqrHQX8F C5YZuO/FwmQ7k6mIyfvwGSDRcBJ1bkDTN1V+zJJTB5Qlu9GgwC6Jq4zid2r0cnFq C9JXVPx7ug8BCLhDQWY1/9w2HG2VmBrF52YkyYkOwvIKmjMgEigu1rLJiANdVbaQ 4pJqEFD5vxNx3ArprCroEhK8PN5q4f9yuvK8VHY/unKJeLrWmPMO52eZyX7/qUki L6rVq1CZuQuX/Tsz9OQUqH/HouKtfgCsEyX4tzbGpywvTlBxbc9mjD0L0UI40MdS 1TRTKkpGOGYKyiWcVnkiwVrepNY5/GraQzuOoZkBnPBBv6m9JVM= =42m/ -----END PGP SIGNATURE----- --vcnzoghu4f62oozl-- From owner-freebsd-stable@freebsd.org Wed Aug 30 15:46:46 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3F66E0488F; Wed, 30 Aug 2017 15:46:46 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 697F071809; Wed, 30 Aug 2017 15:46:46 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qt0-x229.google.com with SMTP id h15so13686253qta.4; Wed, 30 Aug 2017 08:46:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jkH04P7LzxVvAaquNPmVAvImFQZdCUnTvof0m9C8DxA=; b=F1lPCRLVA+kc+zagFs2qGnZMkFhHhR1cb5MNe+faBJwgEpKUCwvsTTaU3OpgcwVGUC mNIlBjBb9H/+7g22b5QdNenrGSPxwFZlmEZk99uu7cdetfpxlbs1pqXAvj5+vawtCicc dL9xCidhb9Bfx85WegNJBUmNmen//XZrflMU14BMSSc0wQmJecNPRJHSZdRyJX7NEggS 8+KLMV0hUmhN8Q3Tx5y3aUhoJG6OK/RNBx1l4WY28/kswLi/Ni0GNk1LgMcj5YS3HYkt n2u2w6TEL5/rEd0R/Y5REVfmBUHVk4wkM/GbBKZtY+Pt1cr3u0qdKPqFdBoi3SOPlAhQ rXiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jkH04P7LzxVvAaquNPmVAvImFQZdCUnTvof0m9C8DxA=; b=OUZ1OLzdsGXhlBV/fAoqu8SM0HKLAo4xpEgP9zHlQgjYA/MuEKiJ/Y4KiekDWjG4Rd dV5jZkJ+TnxqvvNx5h7GytF4C3BSZ3LDrUGJMRSpL90uKZE32hwU1FYI/z+g0lNxoKlw mHVh1+aNMrGYE8Yj/x29VjsQM7gzx5djhRHmacoYuB+B4BADQYpMI5jhbKOea8CoF4f4 KbbZzwi8+bq8M4pcr4k1b97GNGbnTWblPf+LZGOw0pSqq9jr40mFogr0gsr5Uiwa9idg MwE+9AX3eqtjdkMZkxiXakUNsubh9PCag0bV9rzdUT8ppfE2JFD/ZoH8yFI85NgJNz/E 23iQ== X-Gm-Message-State: AHYfb5gybZe54KvPW+jPH5h2ZG3EbVoA5Yl6udFFBC8BVANJ14pA145L hzPYz1LBLQtSymKtqDVASI2lv2+H11zO X-Received: by 10.200.56.1 with SMTP id q1mr2555200qtb.16.1504108005177; Wed, 30 Aug 2017 08:46:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.38.129 with HTTP; Wed, 30 Aug 2017 08:46:44 -0700 (PDT) In-Reply-To: <20170830143426.r53pztrybmmvfy6c@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> <20170830125950.mcp34sddcp6c757t@ivaldir.net> <20170830143426.r53pztrybmmvfy6c@ivaldir.net> From: Cassiano Peixoto Date: Wed, 30 Aug 2017 12:46:44 -0300 Message-ID: Subject: Re: pkg issue after FreeBSD 11 upgrade To: Baptiste Daroussin Cc: Matthew Seaman , "freebsd-stable@freebsd.org" , "freebsd-ports@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 15:46:46 -0000 Thank you for your support Baptiste, I really appreciate that. As same as HANDLE_RC_SCRIPTS option the new one should be handled carefully. Please keep us posted when it's ready. On Wednesday, August 30, 2017, Baptiste Daroussin wrote: > On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixoto wrote: > > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal > > with when I need to restart a service without upgrading? Reaper > > functionnality is a trouble for many administrators who made meta ports > to > > manage their servers. I really think it could be a option to be > > enabled/disabled. Can you see this possibility? > > > > Yes I could add an option to disable the reaper functionnality (and will > probably to unblock such use case as soon as I have time to do it.) > > However I still think this is not the right idea :) and a better one could > be > found > > Bapt > From owner-freebsd-stable@freebsd.org Wed Aug 30 23:10:25 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C11F5E0C508 for ; Wed, 30 Aug 2017 23:10:25 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 704F583F4D for ; Wed, 30 Aug 2017 23:10:25 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-yw0-x22a.google.com with SMTP id t188so38281836ywb.1 for ; Wed, 30 Aug 2017 16:10:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=4VQpr/hK4sXXSm9St0fTf3cLrCG+yzp3lkTcgLK6B3o=; b=GDcDvEfVfqX7OaEVVF2ixiwSg32y6dDAgJnQZE4wU25Qry7/jndkiVGvVsZG+qDXqM EIAtzrGnxjvHyZQrwqk2fLa9Rjk+nk1arXJX7/AIRoOSkKVQ1B6OVcuaU7bKihrkY2YL KZcYHtYnYyQiwkFg8jpve4AoXD5n47liy82Ki1YirZy94elq8fbi+UNdGE/EuP2g39+M BC4y48M2YRN56Lp7mSU3nJqthHw9e5EVO2IDpRGm65nzFLMP1v278X0HkqaemUGJCA21 z2DQ9qIYjuc5SZo9auF4M4bZwSe9TWTwJD7VbijswFL/ZWOkc7EzrRtQ37XPLziJ3iim mzmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=4VQpr/hK4sXXSm9St0fTf3cLrCG+yzp3lkTcgLK6B3o=; b=WcaIMduQCCldQTj5VLaDmo1UDyi7y+DjlyVCiaHNSpUbJZr42XIJhOuZXmi+7Wh7G1 gnHR2d3TV7thYWhXmxl66hbMtgtLhb15+g88NDL78kH5EklprFX/TGL3B+/mXwRHl+AL o2O6WS5Qvk9YQ2hBWdXVDTGFu4tMLUNDOGFQOy54vj4x/MRV9FXUpgBpA/q/8JMNu6Ks lIpSY2ZUtJ210ttHggDLQmNPq/wKBEw8QUXM7q6dJfq8frJM5QucT/PG4+K4UvDfTqo0 8lUxmE0vX9i0Kl3S/PyC83UeDo94EBtx+JC9gxFKpRInUd0Q6AyRNVj+X3tO+E8EYztz RpUg== X-Gm-Message-State: AHYfb5hiscFZK8BRBTy5nizQbMM4/ddOzQOXF62GmQwH6IqcdyghBcxV IX3ccDYLjGS5hUWxmcxK22cYD9+fFQ== X-Received: by 10.37.224.8 with SMTP id x8mr553420ybg.74.1504134624592; Wed, 30 Aug 2017 16:10:24 -0700 (PDT) MIME-Version: 1.0 Sender: jtubnor@gmail.com Received: by 10.37.198.10 with HTTP; Wed, 30 Aug 2017 16:10:04 -0700 (PDT) In-Reply-To: References: From: Jason Tubnor Date: Thu, 31 Aug 2017 09:10:04 +1000 X-Google-Sender-Auth: WiPSf2THNR2SrVUB15-2GdpK5Ww Message-ID: Subject: Re: Bridged networking regression in 11.0? To: "Patrick M. Hausen" Cc: freebsd-stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 30 Aug 2017 23:10:25 -0000 On 30 August 2017 at 20:49, Patrick M. Hausen wrote: > > The only real change relates to IF teardown and we did not change anything > (stop/restart jails) when the outages occured. > > So ... the network interface driver? Probably? > > > We are using igb(4) with vlan(4), tap(4) bundled into bridge(4). The taps are entries to bhyve guests. These were built initially on FreeBSD 11.0 and have been recently uplifted to FreeBSD 11.1. We have never had any issues with these bridges, even under heavy load. We do want to netmap/vale but not until it is maintainable via freebsd-update (built into generic). So based on what you have said, a bit more of a breakdown to determine the culprit that is within the bridge might be needed, especially with VIMAGE (though our FreeNAS jails use VIMAGE and bridges without breakage also). Cheers, Jason. From owner-freebsd-stable@freebsd.org Thu Aug 31 02:38:35 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2176EE12C96 for ; Thu, 31 Aug 2017 02:38:35 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E98956545E for ; Thu, 31 Aug 2017 02:38:34 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id f99so6735210ioi.3 for ; Wed, 30 Aug 2017 19:38:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=H6HE7lJLgMPNMP8FelzD5guEuPmhinlM0hI6p4kkhj8=; b=cNjZlHNMTKGSBrmoaUa8GsCL9YKt5rZWBBoKBU5nJGqgo/fIMt4gjgglqkim/oTF2m aQj2zMOIGzydNMFgAUzflnJCaourhcmd3Ike4ZVigy2S8p81mJecoXlzjLS/FeaB7hXt qJ2RE3PmxoX/6Nw2wgmC4YMp7GdOsPRjAPNW3aZOBkNKa+CHXEo0eFq67vtu+OmVPzQN gpuZnD9IzWBOujzZixIGd9Pfm4A/RNRQtrX9SscPnEUbAibU/VU645KkdiasxRZFmORA Q26820TvX4MpN85zSY5HrxzYrg40tYAkxXfRVuT8HZiihddvKMLGjxfjFlQ/16H+h6Sz w0/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=H6HE7lJLgMPNMP8FelzD5guEuPmhinlM0hI6p4kkhj8=; b=OF1WlN/hQUSzxvAb7mIsqBveWoTGxZVR8lsicOQ2B4SGOs/D64qbCNK/65hxw+1bD7 3izWz2anjflYd5dTVrXVlF7bILy7RiUdzgtoIfTzDkLx1iAdzbmXRvPZBg1nWYdd5tGq PWXx6N3Z22p5X7AZDaA0CVxSYQqx6QAiTHBEzUL6IuGDzjoIsrm6NUu6S0qvRBz1lnIR 64sszIGbpx6B0bgnBbHhlaF6qMOwBDXG81vcijzG+TFT+f+q7l+RGg23UKwozPCI7s5a 2gRmhwu9ou+CizmoeBDB7DB+fI2PY+I7nbVN++ViXFxpGLG1ASkOoLuQO5+OQk1ewqD1 15nQ== X-Gm-Message-State: AHYfb5inyutHJZ83bOzfgBjoRGzJoj2F8P9dZ9Ti2ZydOAMAqAeyCSfT obYJT8fFCTWAoydEzIbgGrZzk7NsHA== X-Received: by 10.36.81.203 with SMTP id s194mr3666918ita.140.1504147114271; Wed, 30 Aug 2017 19:38:34 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.24.66 with HTTP; Wed, 30 Aug 2017 19:38:13 -0700 (PDT) In-Reply-To: References: <20170830132959.13596a93@akips.com> From: Ed Maste Date: Wed, 30 Aug 2017 22:38:13 -0400 X-Google-Sender-Auth: zu2y9Iqhq_v3r2Gycul85QYlTEw Message-ID: Subject: Re: date -r {big number} results in segmentation fault To: Xin LI Cc: Paul Koch , FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 31 Aug 2017 02:38:35 -0000 On 30 August 2017 at 01:12, Xin LI wrote: > I think emaste@ have fixed it in r321293. MFC? Thanks for the note, now merged in r323044. From owner-freebsd-stable@freebsd.org Thu Aug 31 16:04:33 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 402D7E00FFE; Thu, 31 Aug 2017 16:04:33 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC0B98248B; Thu, 31 Aug 2017 16:04:32 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x242.google.com with SMTP id z91so35837wrc.1; Thu, 31 Aug 2017 09:04:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kp3kddJg30cxSsH2HJvyTRO8GEJGj9OT10YL0bwTMSI=; b=HfXYEuD71s5lkUOM8UgG/0sR1165oI92h7Ef9RtNOWY/aFnyy75kx2XQ6tC6hb2sKn /7h8AnOi99xIlykAbCFbr27f26u5/Jnpr4SUf1PZZNC6e+1f6Wg6l4CJ1pc61si+lIqM ZCvSU6JtRtDja/eFBULtV6ZvvtA1nWz/fvJdcsGAN+bLBaHAXcD6qwijeRK79NMt6j3b eNlNhgfe/SQOjKmtHD4amJjCNAV5AB8fS29pGNIYd6D+25OSKBp+NhhSYQirJ1D0n36L cWDmitL/P5DF8sogo5ljVbYL4OAHbuzJltN/bPWcpyskOQNKVuQ8kEaAaoEO4/SpP6ET 2/Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kp3kddJg30cxSsH2HJvyTRO8GEJGj9OT10YL0bwTMSI=; b=txD53RKMPbLwEAWLQP5ySmSluML1+08Pume4Eay4WKlMLcVcSX6E1Z+fE72mSpzCtE zLs45UVLsucugLjFIpKbR8PAYoenirWIyguFgaJ4+oG2LEUF58Ete3SaTcQ44/k3FmJX 5WljsrwEkfUOyY8F5OFgcnnnIAP8ylef7X5ytY+Fj4ZcTQlifEhPDs+KURgvnt+eXm5Q UqoCuIS/G/TxYlsgIN151fWTR/dTiyieJRK0UHp5c+Wdb2wlt0yNDe9dLYLwIR/FGcPs W7ll6vRvUFuiKQ9CwjEndNyV7vnf91rMDLBkPIteq+Nf8UhnsnmdThEJY289G7q2/Xcn jqmw== X-Gm-Message-State: AHYfb5j7VRII4i19QkFzB4NeEcE6B4E2I7JRbP5whuiWq8/cYUbq5Ncx IeOBmE1uRA5y8CZpmWc= X-Google-Smtp-Source: ADKCNb476N5sZSYn1JIX0qvyq4emwAVV6iG82x//ixJpxcRvP+L0vkmjOIigSjOnJ1P1RCWHJHDHRQ== X-Received: by 10.223.150.35 with SMTP id b32mr3354121wra.87.1504195471031; Thu, 31 Aug 2017 09:04:31 -0700 (PDT) Received: from ben.home (LFbn-MAR-1-330-35.w2-15.abo.wanadoo.fr. [2.15.164.35]) by smtp.gmail.com with ESMTPSA id 33sm85967wra.6.2017.08.31.09.04.29 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 31 Aug 2017 09:04:30 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???) From: Ben RUBSON In-Reply-To: <82e661b4-1bac-ff5b-f776-8dba44cac15e@freebsd.org> Date: Thu, 31 Aug 2017 18:04:27 +0200 Cc: Hans Petter Selasky , FreeBSD Net , hiren , Slawa Olhovchenkov , FreeBSD Stable Content-Transfer-Encoding: quoted-printable Message-Id: <82EFBD5E-8FC2-4156-A030-AF70D97A37BA@gmail.com> References: <7f14c95d-1ef8-bf82-c469-e6566c3aba66@selasky.org> <76A5EE7E-1D2E-46B4-86F1-F219C3DCE6EA@gmail.com> <4C91C6E5-0725-42E7-9813-1F3ACF3DDD6E@gmail.com> <5840c25e-7472-3276-6df9-1ed4183078ad@selasky.org> <2ADA8C57-2C2D-4F97-9F0B-82D53EDDC649@gmail.com> <061cdf72-6285-8239-5380-58d9d19a1ef7@selasky.org> <92BEE83D-498F-47D5-A53C-39DCDC00A0FD@gmail.com> <5d8960d8-e1ff-8719-320f-d3ae84054714@selasky.org> <6B4A35F7-5694-4945-9575-19ADB678F9FA@gmail.com> <297a784a-3d80-b1a6-652e-a78621fe5a8b@selasky.org> <3ECCFBF1-18D9-4E33-8F39-0C366C3BB8B4@gmail.com> <0a5787c5-8a53-ab09-971a-dc1cd5f3aca0@freebsd.org> <645f2ee3-3eaa-660e-2a64-37d53e88322f@freebsd.org> <13DE4E6D-CE83-4B5D-BF88-0EFE65111311@gmail.com> <7B084207-062A-4529-B0DC-5BFEB6517780@gmail.com> <82e661b4-1bac-ff5b-f776-8dba44cac15e@freebsd.org> To: Julien Charbon X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 31 Aug 2017 16:04:33 -0000 > On 28 Aug 2017, at 11:27, Julien Charbon wrote: >=20 > On 8/28/17 10:25 AM, Ben RUBSON wrote: >>> On 16 Aug 2017, at 11:02, Ben RUBSON wrote: >>>=20 >>>> On 15 Aug 2017, at 23:33, Julien Charbon wrote: >>>>=20 >>>> On 8/11/17 11:32 AM, Ben RUBSON wrote: >>>>>> On 08 Aug 2017, at 13:33, Julien Charbon wrote: >>>>>>=20 >>>>>> On 8/8/17 10:31 AM, Hans Petter Selasky wrote: >>>>>>>=20 >>>>>>> Suggested fix attached. >>>>>>=20 >>>>>> I agree we your conclusion. Just for the record, more precisely = this >>>>>> regression seems to have been introduced with: >>>>>> (...) >>>>>> Thus good catch, and your patch looks good. I am going to just = verify >>>>>> the other in_pcbrele_wlocked() calls in TCP stack. >>>>>=20 >>>>> Julien, do you plan to make this fix reach 11.0-p12 ? >>>>=20 >>>> I am checking if your issue is another flavor of the issue fixed = by: >>>>=20 >>>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D307551 >>>> https://reviews.freebsd.org/D8211 >>>>=20 >>>> This fix in not in 11.0 but in 11.1. Currently I did not found how = an >>>> inp in INP_TIMEWAIT state can have been INP_FREED without having = its tw >>>> set to NULL already except the issue fixed by r307551. >>>>=20 >>>> Thus could you try to apply this patch: >>>>=20 >>>> = https://github.com/freebsd/freebsd/commit/acb5bfda99b753d9ead3529d04f20087= c5f7d0a0.patch >>>>=20 >>>> and see if you can still reproduce this issue? >>>=20 >>> Thank you for your answer Julien. >>> Unfortunately, I'm not sure at all how to reproduce the issue. >>> I have other servers which are 100% identical to this one, same = workload, >>> same some-months uptime, but they did not trigger the bug yet. >>>=20 >>> If other network stack experts (I'm not) agree with your analysis, >>> we could then certainly go further with D8211 / r307551. >>>=20 >>> One thing that perhaps might help : >>> # netstat -an | grep TIME_WAIT$ | wc -l >>> 468 >>>=20 >>> Note that due to this running bug, sendmail has lots of difficulties = to send outgoing mails. >>> As soon as I run the above netstat command, I receive a lot of = stacked mails (more than 20 this time). >>> As if netstat was able to somehow help... >>>=20 >>> Number of TIME_WAIT connections however does not decrease, but = increases. >>>=20 >>>> And in the spirit of r307551 fix and based on Hans patch I will = also >>>> propose to add a kernel log describing the issue instead of = starting an >>>> infinite loop when INVARIANT is not set. >>>=20 >>> Which should then never be triggered :) >>> Good idea I think ! >>=20 >> What about : >> D8211/r307551 >> + Hans' patch >> + Julien's idea of a kernel log (sort of "We should not be here but = we are") >=20 > I did this change and I am testing it Good news ! > on your side did you try this patch applied on 11.0? >=20 > = https://github.com/freebsd/freebsd/commit/acb5bfda99b753d9ead3529d04f20087= c5f7d0a0.patch Yes, patch applied and running correctly, however hard to say whether or not it solves this issue, as there is no easy way to reproduce it. >> And backporting all this to 11.0 (and so to 11.1 too) ? >>=20 >> As this bug can impact every FreeBSD machine / server, >> leading to an unavailable / unreachable system (this is how mine = ended), >> sounds like it could inevitably be a good thing, for production = stability purpose. >=20 > The main fix for your issue is (I believe): >=20 > Fix a double-free when an inp transitions to INP_TIMEWAIT state > after having been dropped. > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D307551 >=20 > This fix has been MFC-ed on both stable/11, stable/10 and is already > included in 11.1 and will be in 10.4. To push in 11.0 release = directly, > I guess you have to promote this change to an Errata (never did that > myself): >=20 > https://www.freebsd.org/security/notices.html > https://www.freebsd.org/security/security.html#reporting Mail sent to FreeBSD Security Team ! Many thanks, let's stay tuned ! Ben From owner-freebsd-stable@freebsd.org Fri Sep 1 15:40:08 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04F34E158A5 for ; Fri, 1 Sep 2017 15:40:08 +0000 (UTC) (envelope-from devgs@ukr.net) Received: from frv191.fwdcdn.com (frv191.fwdcdn.com [212.42.77.191]) (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 BF42576A6A for ; Fri, 1 Sep 2017 15:40:07 +0000 (UTC) (envelope-from devgs@ukr.net) Received: from [10.10.1.26] (helo=frv197.fwdcdn.com) by frv191.fwdcdn.com with esmtp ID 1dnnkr-000DDB-Hp for freebsd-stable@freebsd.org; Fri, 01 Sep 2017 18:21:09 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-Id:To: Subject:From:Date:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=PuQCoafWGHc1y1XBWkuf33OMlHg4Wr1RXSnIhqlGT3k=; b=MzNvjhl9OU1/AISnEJjbvFHNKx +ZJwRxEXXydrUwIf2Ng+FAW+GvTZ59qP7iW1hEEef1WCDCSmUbbXI6BlQffqit/FqvHzh9RoOhb27 m1oe6AkInk5WoLAQKnrSJg4bWB3dscXYgzbw2ioi7j7Mm6p6Ldb4VvhA6Io0jbwq0ZtQ=; Received: from [10.10.10.33] (helo=frv33.fwdcdn.com) by frv197.fwdcdn.com with smtp ID 1dnnki-000BnD-TX for freebsd-stable@freebsd.org; Fri, 01 Sep 2017 18:21:00 +0300 Date: Fri, 01 Sep 2017 18:21:00 +0300 From: Paul Subject: High CPU usage in kernel on highly contended lock file To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: mail.ukr.net 5.0 Message-Id: <1504278581.38180443.tad3fj7o@frv33.fwdcdn.com> Received: from devgs@ukr.net by frv33.fwdcdn.com; Fri, 01 Sep 2017 18:21:00 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Sep 2017 15:40:08 -0000 It seems that a lot of CPU resources are spend when trying to get exclusive lock on file from multiple processes concurrently. By multiple i mean hundreds. It seems that there's an initial cost of fcntl() call. Each process that tries to lock the file consumes some amount of CPU and cools down. However, each repeated fcntl() call will consume same amount of resources again. It seems as if entering the "wait queue" is expensive. Environment: #uname -a FreeBSD test.com 11.1-STABLE FreeBSD 11.1-STABLE #0 r322650: Thu Aug 31 19:49:49 EEST 2017 root@test.com:/usr/obj/usr/src/sys/SERVER amd64 Test case: test.c: #include #include #include #include #include #include static int child_count = 0; static void schild_handler(int sig) { --child_count; } static void alarm_handler(int sig) { } void lock_write(int fd) { struct flock fl; fl.l_type = F_WRLCK; fl.l_whence = SEEK_SET; fl.l_start = 0; fl.l_len = 1; do { // Simulate interruption with alarm to re-enter the wait queue. alarm(1); } while (fcntl(fd, F_SETLKW, &fl) < 0); } int main(int argc, char ** argv) { if (argc < 2) { return 1; } signal(SIGCHLD, schild_handler); struct sigaction sig_action; memset(&sig_action, 0, sizeof sig_action); sig_action.sa_handler = alarm_handler; sigemptyset(&sig_action.sa_mask); sigaction(SIGALRM, &sig_action, NULL); int fd = open(argv[1], O_CREAT|O_RDWR, 0777); for (int i = 0; i < 300; ++i) { pid_t child_pid = fork(); if (!child_pid) { // Lock the descriptor. lock_write(fd); // Simulate some work. sleep(1); return 0; } ++child_count; } do { printf("\rchild count: %5u\n", child_count); sleep(1); } while(child_count); return 0; } Commands: # cd /tmp # ~~~~~ Create test.c # clang -o test test.c # ./test 11111 Note that on linux, even if 1000 children are spawned instead of 300, none of them ever appear in the top. This is a huge problem, because our current software uses lock files for sync purposes. And at times, when a lot of processes of said software are spawned (prime time), system becomes totally unresponsive with over 1000 LA. From owner-freebsd-stable@freebsd.org Fri Sep 1 19:24:43 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 726F1E01B2D; Fri, 1 Sep 2017 19:24:43 +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 E6475F05; Fri, 1 Sep 2017 19:24:42 +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 v81JOYrB099198 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 1 Sep 2017 22:24:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v81JOYrB099198 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v81JOXvF099197; Fri, 1 Sep 2017 22:24:33 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 1 Sep 2017 22:24:33 +0300 From: Konstantin Belousov To: Paul Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: High CPU usage in kernel on highly contended lock file Message-ID: <20170901192433.GA1700@kib.kiev.ua> References: <1504278581.38180443.tad3fj7o@frv33.fwdcdn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1504278581.38180443.tad3fj7o@frv33.fwdcdn.com> User-Agent: Mutt/1.8.3 (2017-05-23) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Sep 2017 19:24:43 -0000 On Fri, Sep 01, 2017 at 06:21:00PM +0300, Paul wrote: > > It seems that a lot of CPU resources are spend when trying to get exclusive lock on file from multiple processes concurrently. By multiple i mean hundreds. > It seems that there's an initial cost of fcntl() call. Each process that tries to lock the file consumes some amount of CPU and cools down. > However, each repeated fcntl() call will consume same amount of resources again. It seems as if entering the "wait queue" is expensive. Yes, our lockf is somewhat expensive, I believe it is because the implementation tries to maintain the fairness. In other words, the lock requesters are put on queue in order. Another heavy feature is the deadlock detection. POSIX seems to state that the detection is optional, but perhaps it is required for reliable operations of the network locking protocols for NFS. Sure, there can be opportunities to optimize the current algorithms. Somebody interested in such optimization should start with profiling the kernel. From owner-freebsd-stable@freebsd.org Sat Sep 2 14:05:52 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4FEDE14BBA for ; Sat, 2 Sep 2017 14:05:52 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from ua.ulka.com.au (ua.ulka.com.au [203.217.10.26]) (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 576C43FA2 for ; Sat, 2 Sep 2017 14:05:48 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from PLUTO (pluto.ulka.com.au [10.0.0.27]) by ua.ulka.com.au (8.14.7/8.14.7) with SMTP id v82DnrYS051009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 2 Sep 2017 23:19:54 +0930 (CST) (envelope-from vpc@ulka.com.au) From: "Priyadarshana Chandrasena" To: Subject: HP Smart array P440 support Date: Sat, 2 Sep 2017 23:18:59 +0930 Message-ID: <001501d323f2$3e517560$baf46020$@ulka.com.au> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdMj8Z77OerjIwSwRFS+N/O/IX1NQw== Content-Language: en-au Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Sep 2017 14:05:53 -0000 I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. I have a HP smart array P440 in my server. I can not find out anywhere if ciss driver support include HP Gen 9 storage controllers. Could you please update the ciss driver in 10.3? Regrads, P Chandrasena From owner-freebsd-stable@freebsd.org Sat Sep 2 14:30:41 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6215FE16187 for ; Sat, 2 Sep 2017 14:30:41 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id C1FB264A39 for ; Sat, 2 Sep 2017 14:30:37 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Sat, 02 Sep 2017 16:29:25 +0200 Authentication-Results: connect.ultra-secure.de; iprev=temperror; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 607CE7B7-EDE2-41B6-91A9-1D54CAA15225.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Sat, 02 Sep 2017 16:29:17 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: HP Smart array P440 support From: Rainer Duffner In-Reply-To: <001501d323f2$3e517560$baf46020$@ulka.com.au> Date: Sat, 2 Sep 2017 16:29:14 +0200 Cc: FreeBSD-stable@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> To: Priyadarshana Chandrasena X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=15 total_conn=1 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 3848, bad: 1, connections: 4273, history: 3847, asn_score: 381, asn_connections: 392, asn_good: 381, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Sep 2017 14:30:41 -0000 > Am 02.09.2017 um 15:48 schrieb Priyadarshana Chandrasena = : >=20 > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. = I > have a HP smart array P440 in my server. I can not find out anywhere = if ciss > driver support include HP Gen 9 storage controllers. Could you please > update the ciss driver in 10.3? >=20 Try 10.3 I know the release-notes say nothing about it, but I believe it is = supported. If not that, 11.0 surely does (even though the release-notes don=E2=80=99t= mention it, either) From owner-freebsd-stable@freebsd.org Sat Sep 2 15:41:22 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4D4CE18F68 for ; Sat, 2 Sep 2017 15:41:22 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by mx1.freebsd.org (Postfix) with ESMTP id 99F8C66A95 for ; Sat, 2 Sep 2017 15:41:22 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 025B3E6065; Sat, 2 Sep 2017 17:41:20 +0200 (CEST) Date: Sat, 02 Sep 2017 17:41:19 +0200 (CEST) Message-Id: <20170902.174119.74668153.sthaug@nethelp.no> To: vpc@ulka.com.au, rainer@ultra-secure.de Cc: FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support From: sthaug@nethelp.no In-Reply-To: <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-2022-jp-2 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Sep 2017 15:41:22 -0000 > > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. I > > have a HP smart array P440 in my server. I can not find out anywhere if ciss > > driver support include HP Gen 9 storage controllers. Could you please > > update the ciss driver in 10.3? > > Try 10.3 > > I know the release-notes say nothing about it, but I believe it is supported. > > If not that, 11.0 surely does (even though the release-notes don$,1ry(Bt mention it, either) I can confirm that 10.3 supports the P440 controller. From a DL360 Gen9 server running 10.3 here: ciss0: port 0x2000-0x20ff mem 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff irq 16 at device 0.0 on pci3 ciss0: PERFORMANT Transport ... da0 at ciss0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SPC-3 SCSI device da0: Serial Number PDNLH0BRH8S3RF da0: 135.168MB/s transfers da0: Command Queueing enabled da0: 139979MB (286677120 512 byte sectors) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-stable@freebsd.org Sat Sep 2 18:25:48 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B3C8E1FE25 for ; Sat, 2 Sep 2017 18:25:48 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C97056C446 for ; Sat, 2 Sep 2017 18:25:47 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-qk0-x22d.google.com with SMTP id k126so11134898qkb.4 for ; Sat, 02 Sep 2017 11:25:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7veCu8/3pL8dogNEcW/yXa1J6CwJYZnnVv/F+Sjo02U=; b=MJxtH4DY7KcxGIPOzvl52ujOPmW2MZSHBrdJqPZho+kchwTsZBQqDOd7fsR8o52Vuq bIhvHEgPfO0ZV91FB88FKofn/N7EvZ3CVQd6k+zr1a5NT7/IgPKzXgcogxbSA/9xYy5P zs/1BnDK1MRWadFJAY4B1y2q/0Dq/0h3TAHdEoW1UKEIXJ/MwgC2jlZiHktITukQHrqj fUC2B9BtN+mExYTKpLCgQQhwDvUXLPcW2J/otqa7QNecf5JKZUvRt9ChsJvhJDfuYhUw Q4FdEdAFnVlU0GrzBwy3FsiBLrdrXc1BLdFFxvz1DRz6Rme3vCNhpfjTaCBUYVVIhNpw wVkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7veCu8/3pL8dogNEcW/yXa1J6CwJYZnnVv/F+Sjo02U=; b=RXH9yX03JUkLnAt4/o2UO/6WVxODe2o71vUQxXn0gkVMYT0P240V6tJcNOF4SbJ7kV YmB8LN4GfH6k6fSNKw7gosuO5R6fkWs8kY9YYkji66adDmnUa4pAM91RjWMzl5eCNDlK RXooyaxBfqGtshs5V2xW0gQTIkTEwOJ7ve5TvdVQKzDqF1pGTEgFEwcq3w/qsN2vuZsJ yn3YsypK5Cqa2Z2JdCwbZLkDpQGhxfmkK6aS7yVnOJFxwg9Dn/3AmlrUihbMd6F8oNLK +yz2dzzVlXIx4USl+iAMXIawPnF1/uFJ3ZZh2GS+NzmajS8yz1odYSnlrvoCJarVMDhX 45AQ== X-Gm-Message-State: AHPjjUjtRJmtBVwxMOcFDOPf2LAx7GgdOKM9Q4Q8j/7VivwPV7nakMxc lnhf7vsbOTj2a9cPuAt1zA== X-Google-Smtp-Source: ADKCNb6zYX0yt1BpHHmaYJo7eE+ziE8PW4khZIPI0DgMT8ZH/yApvDRMJF3O92f04B3UbOS7UqLPKw== X-Received: by 10.55.125.194 with SMTP id y185mr7644641qkc.15.1504376746640; Sat, 02 Sep 2017 11:25:46 -0700 (PDT) Received: from [192.168.1.41] (ool-43522949.dyn.optonline.net. [67.82.41.73]) by smtp.gmail.com with ESMTPSA id f74sm1202953qka.40.2017.09.02.11.25.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Sep 2017 11:25:45 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: HP Smart array P440 support From: Mark Saad X-Mailer: iPhone Mail (14G60) In-Reply-To: <20170902.174119.74668153.sthaug@nethelp.no> Date: Sat, 2 Sep 2017 14:25:44 -0400 Cc: vpc@ulka.com.au, rainer@ultra-secure.de, FreeBSD-stable@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> <20170902.174119.74668153.sthaug@nethelp.no> To: sthaug@nethelp.no X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Sep 2017 18:25:48 -0000 All Also don't forget to is install cciss_vol_status to monitor the array . --- Mark Saad | nonesuch@longcount.org On Sep 2, 2017, at 11:41 AM, sthaug@nethelp.no wrote: >>> I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. I= >>> have a HP smart array P440 in my server. I can not find out anywhere if c= iss >>> driver support include HP Gen 9 storage controllers. Could you please >>> update the ciss driver in 10.3? >>=20 >> Try 10.3 >>=20 >> I know the release-notes say nothing about it, but I believe it is suppor= ted. >>=20 >> If not that, 11.0 surely does (even though the release-notes don=1B$,1ry=1B= (Bt mention it, either) >=20 > I can confirm that 10.3 supports the P440 controller. =46rom a DL360 Gen9 > server running 10.3 here: >=20 > ciss0: port 0x2000-0x20ff mem 0x92c00000-0x92cffff= f,0x92d00000-0x92d003ff irq 16 at device 0.0 on pci3 > ciss0: PERFORMANT Transport > ... > da0 at ciss0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SPC-3 SCSI device > da0: Serial Number PDNLH0BRH8S3RF > da0: 135.168MB/s transfers > da0: Command Queueing enabled > da0: 139979MB (286677120 512 byte sectors) >=20 > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > _______________________________________________ > 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 Sat Sep 2 20:38:46 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6C81E03275 for ; Sat, 2 Sep 2017 20:38:46 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "alchemy.franken.de", Issuer "alchemy.franken.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47C096FC3B; Sat, 2 Sep 2017 20:38:45 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.15.2/8.15.2/ALCHEMY.FRANKEN.DE) with ESMTPS id v82KchZP013677 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 2 Sep 2017 22:38:43 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.15.2/8.15.2/Submit) id v82KchfZ013676; Sat, 2 Sep 2017 22:38:43 +0200 (CEST) (envelope-from marius) Date: Sat, 2 Sep 2017 22:38:43 +0200 From: Marius Strobl To: freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 10.4-BETA3 Now Available Message-ID: <20170902203843.GV20729@alchemy.franken.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Sep 2017 20:38:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 The third BETA build of the 10.4-RELEASE release cycle is now available. Installation images are available for: o amd64 GENERIC o i386 GENERIC o ia64 GENERIC o powerpc GENERIC o powerpc64 GENERIC64 o sparc64 GENERIC o armv6 BEAGLEBONE o armv6 CUBOX-HUMMINGBOARD o armv6 GUMSTIX o armv6 PANDABOARD o armv6 RPI-B Note regarding arm/armv6 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/10.4/ 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/10" branch. A list of changes since 10.3-RELEASE are available in the stable/10 release notes: https://www.freebsd.org/relnotes/10-STABLE/relnotes/article.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 10.4-RELEASE cycle progresses. === Noteworthy Changes Since 10.4-BETA1 === o Support for the Kaby Lake generation of Intel i219 (4) and i219 (5) devices has been added to em(4). o The em(4) driver is now capable of enabling Wake On LAN (WOL) also for Intel i217, i218 and i219 chips. Note that stale configurations from previous unsuccessful attempts to enable WOL for these devices now will actually take effect. For example, an `ifconfig em0 wol` activates all WOL variants including wol_mcast, which might be undesirable. o Support for WOL has been added to the igb(4) driver, which was not able to activate this feature on any device before. The same remark regarding stale WOL configurations as for em(4) applies. O The firmware shipping with qlxgbe(4) has been updated to version 5.4.66. Additionally, this driver received some TSO and locking fixes, performance optimizations as well as SYSCTLs providing MAC, RX and TX statistics. === Known Issues === The armv6 WANDBOARD image failed to build. An image for these boards will be made available again at a later point in the 10.4-RELEASE cycle once the underlying problem has been addressed. === 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/10.4-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 160 MB and 128 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: Created AMI in ap-south-1 region: ami-5b95d134 Created AMI in eu-west-2 region: ami-44e9f920 Created AMI in eu-west-1 region: ami-c340baba Created AMI in ap-northeast-2 region: ami-4561b92b Created AMI in ap-northeast-1 region: ami-9251aaf4 Created AMI in sa-east-1 region: ami-a9bfccc5 Created AMI in ca-central-1 region: ami-ea29978e Created AMI in ap-southeast-1 region: ami-085d306b Created AMI in ap-southeast-2 region: ami-43ca2f21 Created AMI in eu-central-1 region: ami-268c3949 Created AMI in us-east-1 region: ami-873a30fc Created AMI in us-east-2 region: ami-d283a0b7 Created AMI in us-west-1 region: ami-41e7d321 Created AMI in us-west-2 region: ami-d1a055a9 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-10.4-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 10.4-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 9.x. Alternatively, the user can install misc/compat9x 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 10.4-BETA3 amd64 GENERIC: SHA512 (FreeBSD-10.4-BETA3-amd64-bootonly.iso) = 3228e62dec3913a49440781ee0fce1ac3018f5d5ebefda25e4b5172c8c5bbc922f5b0bf63b9824ea0a8e6523067e2302e16f546e662711b855f539c6056eb71f SHA512 (FreeBSD-10.4-BETA3-amd64-bootonly.iso.xz) = 50e0598cf2c147ddbd6ab22fecb25cdf4d6981bd81d42d362f597617f31b2daac585a980903f1296f8e28d1f4ea36736b4e92aebdbaea94c1d26036a86824d19 SHA512 (FreeBSD-10.4-BETA3-amd64-disc1.iso) = b4a3150a0041237e650c9df178c94aa6621bb4efa0ce372d67e80c44c7fa382535199b65c2340603f592b5492b3da967260b2df92c6dbbc2d06b2ab52c5429d2 SHA512 (FreeBSD-10.4-BETA3-amd64-disc1.iso.xz) = 12ccbf0e847b27518e026061b6f3ad3b1c31c337d0881161e9dd860812abd14a8f61e196c977d54b5857fc5ac939dfc215462cbcb5dd2db745852de4940419ad SHA512 (FreeBSD-10.4-BETA3-amd64-dvd1.iso) = 624bfb3556dca6358f36f25d0f6eb88b3a6568693f834094f1a62212a100c8ebb4300d0bd964c5159d2b06a591350003e7970d67dd89c5650d95c51d27e844f3 SHA512 (FreeBSD-10.4-BETA3-amd64-dvd1.iso.xz) = bb4285059d5e2b97129a3f0b0ad55ac6f4a5605fee9c849539cd653407505202599e8b93e6d050cec6898edafe06e37fae8d6a8831731e5eb62f0608e44e17ba SHA512 (FreeBSD-10.4-BETA3-amd64-memstick.img) = 00fed66244ce0b9b57e30d6f89efb35bfd56cae58dd9c84b0bd9a2e19d4e276a59f14022936e6c34caa7d44d82eabe2e00ba9649a2bd47aa8d1edba10d83d762 SHA512 (FreeBSD-10.4-BETA3-amd64-memstick.img.xz) = 8e80bfc4d2072b6b933fb6edaacff99320bc082b97ed4f91ac5d8141ef80a850faaa6b311a9b1e8d1687c482a78f571d40e379b1095857ef2940a55d4b7f9f87 SHA512 (FreeBSD-10.4-BETA3-amd64-mini-memstick.img) = 0bf2a0be1b56a64baf2cfcd293d5ba5332d1130f10216c3f0aaa47c949dc04eed7173611d17c0865d8d0d3ff34556454276f8a11316698604618e3edf5773823 SHA512 (FreeBSD-10.4-BETA3-amd64-mini-memstick.img.xz) = 0d3ac5b08488e666a2385d3b26d7333715cbea3828760cd6130e714b3b11c362a18d8466d946c0f783f8eb7844a3d5e5d1eb92dfdaf01207b029885c67c75f54 SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-bootonly.iso) = 2f8cff9589e1bd61778228103e61448359dabc65a83ff019ef0bfbc86a3d0e5459ce7f002ff19b5245af5257586527aef046703cbfccd81872947c7cb9849819 SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-bootonly.iso.xz) = a582e902e449439aacba28091bb7dc2c6be77602ec9236d1b804417709a50c3be53408b51b79eeeef26c53b10e6802bb25124f814b9175f7a8e2491472f9302f SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-disc1.iso) = cdf1b74d4bb36b45409f79c2d0ab2dc92ea0d6519248fdaf8af8ae8c5ec6ca266b141c960c6b60cc123569d295998d427f04dc1647dbef1b79fb56432a37fc0a SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-disc1.iso.xz) = f4699f2bb592e617a17560e3aa8435be2ec7db220b759e6b2433fcd1fed7dcdb3a1d7491e79541cdc4ab27eb2b8c8de56250d8ac751cef01d92e50356efdeeea SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-dvd1.iso) = ec4de4cd0467faa89d2eca1e722741d174b583b2431665055b115b67a9771dacde9646cbce375fdf54af47cb4247f64d4aabbe512e7c63a87ad22c3ea295c229 SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-dvd1.iso.xz) = 70da74db7d8ad836919a28cb14388deeec6a4e4bb7367a4bb987ff975b98db285b9988e12af185f46147650c3e1f8deb9c765851c1bc67b80a12ebec98299b68 SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-memstick.img) = 0a7d7b21e91493f3c7796c6f8971578ad291ebf844a6a40b43e19894eb6423ae8deb52a4f1d81ffb7d5e612230d42be9895c927c27f79f7d2fd30dddae9df2a1 SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-memstick.img.xz) = 6c01a9c804db36f2a30e68070df8dd85f3530d13b8bb14b30b25da122a27c343e06619b93420b572c47448dc2736072dcf593e54ad63486429affeb824b68151 SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-mini-memstick.img) = 6ee0ac15fad474f064f225583a146b098fafc8a6d2129dbb4c7757c95c3cec63913234416ee3b3f33cbc2b34d592abd4577c3168676c70690ae183d2e96a5456 SHA512 (FreeBSD-10.4-BETA3-amd64-uefi-mini-memstick.img.xz) = a102b36f784a1d7784f3c4440efb753aa1131f54ceee5b08783edb84c6037d3d6c1eabcb15b4ad7c53eef100dd759f97bce0d27411d64413d17649176c5d212f SHA256 (FreeBSD-10.4-BETA3-amd64-bootonly.iso) = 6cf14c534f2ef0be59bf9c143e669de1d347b32392d627f851bf7dc44834a4a9 SHA256 (FreeBSD-10.4-BETA3-amd64-bootonly.iso.xz) = 851ef0e8072ce43006d6167b21324addd239fb70de16289a769155ac617f00ac SHA256 (FreeBSD-10.4-BETA3-amd64-disc1.iso) = 48f5b2bcfa5811ca098bad96d1218c513d3a382c51b923049381ecde0fc53537 SHA256 (FreeBSD-10.4-BETA3-amd64-disc1.iso.xz) = 5058979fd905b4c8863599263a315ff854e9ec16d373e10337a375296cd81552 SHA256 (FreeBSD-10.4-BETA3-amd64-dvd1.iso) = ea7ed986eb0d67652046cd269fdde87f7d6d03b1901ebd08a2f5445c19c86e9a SHA256 (FreeBSD-10.4-BETA3-amd64-dvd1.iso.xz) = 43ab22b0ea5efb33ddf80091b43475d2c5373c864d8c08c2fdd427f3a1475003 SHA256 (FreeBSD-10.4-BETA3-amd64-memstick.img) = 53cd47a618e951c2942d23113c1fdb955929f5f26f09164f9cd46ad06f0d8299 SHA256 (FreeBSD-10.4-BETA3-amd64-memstick.img.xz) = f01762865c20d0a878ab61d0bd2e5b7036be0be5edf9165fab1e7f11a6d21d2c SHA256 (FreeBSD-10.4-BETA3-amd64-mini-memstick.img) = ec3c23f9a9e817e8f5e691f93952573767f0eb75a4db154ab270a9ab5431d449 SHA256 (FreeBSD-10.4-BETA3-amd64-mini-memstick.img.xz) = dedd225acc88df7137ab6efa85243384ef3a4cd28e2f8bbe91429c42422b8188 SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-bootonly.iso) = 7c4c0b9c3d1086df1d14fddc32cf543ac12cdc193f65dbc2d0fd68b05b48f4ce SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-bootonly.iso.xz) = 2413234ba3f25dfc81f13d22acdd95c2e4a29629b23aa4d0c940c2b8a2c7fc1b SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-disc1.iso) = e132e8f10a942582e2ebb216e1d3dae2ad7f87531fd393abc21f28cf8fd76947 SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-disc1.iso.xz) = fa96b088f0ddbbe7e448ffa95c30715241df18856c9722d05d98d9bdbd3beedb SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-dvd1.iso) = c4db42c3aaf9ae7181c8f6731f6b48dfe4561b88f38709f70b898c53ccd7bf2f SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-dvd1.iso.xz) = d1944c9ca6c42d09e2d3ee9632b633735bf2eef5345641e77f5cccfbc9c18fbd SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-memstick.img) = 2b786c593ca22732b670c57a2f45db2f4b28bda2112b54e608997e8d0748656d SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-memstick.img.xz) = ce90141c5cac6fb61d996aa0484bfd5eed41853e918f41928c6b30eeedaacc11 SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-mini-memstick.img) = bf666b863e0feadda235b8d92963921a1309e639408b50281673ad1077086714 SHA256 (FreeBSD-10.4-BETA3-amd64-uefi-mini-memstick.img.xz) = ab3ed3edb9c7525b58f1dbaa02b4f2ea199f2de37b8cc92d9460b879330ec271 o 10.4-BETA3 i386 GENERIC: SHA512 (FreeBSD-10.4-BETA3-i386-bootonly.iso) = 9ef95882d7421d3463fecaf98fe38b6385c410add6b375e711fd0c90aa5c055686971a55c9d5b763dde2145189761d25e9427dc098fb98b0c703a85fb6de2a2c SHA512 (FreeBSD-10.4-BETA3-i386-bootonly.iso.xz) = 77a98ea8ce6c768bb6dbbc0e89f3e9b32af363036c0c3b61c1ab11a363434f08d553855aeb62653a82309811cd77487203a839e57b6edaea60bee13f748a041b SHA512 (FreeBSD-10.4-BETA3-i386-disc1.iso) = b98787919c3965bd291cb1f8f5e3a21bc982dd80435b8a98c2ab7be2bed2d1e87d95c0b9630ee6892504bb309e97f34caa5098c591bf0d179bb7ec7f61bec1ca SHA512 (FreeBSD-10.4-BETA3-i386-disc1.iso.xz) = cc0e24e8c8b331391b461a365559836951621ea73fb3dff95cfeb0bd5f2ddecc69e5486fec3593302d87a54db29f430237ffc5165f322b889e164db6cdc3f823 SHA512 (FreeBSD-10.4-BETA3-i386-dvd1.iso) = 6abffbe186912a9eb23234cae2a9635133de65e2ae0661cc1ac912ba568b20bae43a9d4c4e10c890a4c8c4b97b209b36be3603017a2225fd4c41f97e75323fe5 SHA512 (FreeBSD-10.4-BETA3-i386-dvd1.iso.xz) = cac8aaa6d7a9dbd11312409511a435ca2c968a3bd6c9d1c5f2c763eb89be7a6dcfc43df8d066c10ecde8a2d8ab8fb3768f5a74fb2fcc9825502162dc1d0df76e SHA512 (FreeBSD-10.4-BETA3-i386-memstick.img) = b084f6f6d618c8138dd3104ccd2fb662b3733642ef8f013f947f0f481fabdb37c649595f5e1c8409052471f952f22ac6b5a88f6ecff0500a6c79fdf6c2dfc29b SHA512 (FreeBSD-10.4-BETA3-i386-memstick.img.xz) = 2b887149540d782e472674f36702c3b7fc91d4eca9d1cb79814c40bd954680d9c6d962778a768330604442bb9864e6a778fbff5ea82e0fe55cc873722689d16a SHA512 (FreeBSD-10.4-BETA3-i386-mini-memstick.img) = 6672a8779b8fdccd9716ae8511c23b2b30a48cba137272c29c180a9b4aec6704dbc21ab76571b6828039d8fda7559c7a4e9d325eda4ae527a162ac76e128a094 SHA512 (FreeBSD-10.4-BETA3-i386-mini-memstick.img.xz) = b69d45f5483d273140d88a98649a947040269ffb3a32ff34133dca277e4d0073575bb8b0ce24825b8a8cc95454a23e228ee457920a29385a495e68a3a1789866 SHA256 (FreeBSD-10.4-BETA3-i386-bootonly.iso) = 20f2e937ba1a167cfd43f132cd4d98eccaeb15acb947690c89d8dac2f0756381 SHA256 (FreeBSD-10.4-BETA3-i386-bootonly.iso.xz) = 8294fede4bc94d833b1d4ba6f30ee718942317388972851c66fe6cf9c9667b0f SHA256 (FreeBSD-10.4-BETA3-i386-disc1.iso) = 301f679942bd999aeff6550c203337658c97deec5b631fc2cb7aebd7ad15f474 SHA256 (FreeBSD-10.4-BETA3-i386-disc1.iso.xz) = 98910f334c8bde6a9a32d9127dc5c2fe927e790370efb6641b0594eab6ce38cf SHA256 (FreeBSD-10.4-BETA3-i386-dvd1.iso) = d7e0129f5c11a6b419eefb381a5c68d886a9b2a1f0e86a46f572ea869e450073 SHA256 (FreeBSD-10.4-BETA3-i386-dvd1.iso.xz) = ce99b17988225df644ae158c9e9bc4c78743016c540f6e81215040eb060c1b7d SHA256 (FreeBSD-10.4-BETA3-i386-memstick.img) = 1436646dfbfd8bad7c102237536541be950aa04a882de130d112c49bb735ee67 SHA256 (FreeBSD-10.4-BETA3-i386-memstick.img.xz) = 5a3a481299467168b87fcc9e004647303d633028a910ca4ac0e1ab44926ab395 SHA256 (FreeBSD-10.4-BETA3-i386-mini-memstick.img) = 3324d6d257d28fc19fa5b6c51a0dfc4af7f53e707d3849a6694e5418386c1e4c SHA256 (FreeBSD-10.4-BETA3-i386-mini-memstick.img.xz) = 4bc8177dc53db3cd3d172cdd752e87aefc756a9b712c65aab631e7d8fcbc1c69 o 10.4-BETA3 ia64 GENERIC: SHA512 (FreeBSD-10.4-BETA3-ia64-bootonly.iso) = 93021b20db53eee85cc1c343c8c3439aca30f158e446c7f57e0381d62e8427cbb390b140cb7538cd1ef26af53efdd09ca0cb9fd84867d022f234a69150457960 SHA512 (FreeBSD-10.4-BETA3-ia64-bootonly.iso.xz) = 63db939967a51e950b6ddd1ffabba74acf29e97673c6d15a7be90a427ee3c5c90c994d65fa1135f59553f703eb1e801fd3789192d1121cdc97033de6e154a18f SHA512 (FreeBSD-10.4-BETA3-ia64-disc1.iso) = 163688665e6b1a51ed5f616a01f57472781709f35a2db9220fa8a7dd814f0eaf004312bb323b3c9d8bff4aebe33cafcfc0ca73d1c4ffc867d257f54cbb331b61 SHA512 (FreeBSD-10.4-BETA3-ia64-disc1.iso.xz) = 569601f749fcdd041352072bc25bf81ecbc1746c2e35909b7b87195b88778826443c6204a684555c3de6cdaee1539e730f024a1cde871a9c3b4b0d0f6c74c809 SHA512 (FreeBSD-10.4-BETA3-ia64-dvd1.iso) = 82d2aa72f19edfce96bb217620f50b8620e1e81b8418cbafcad7955fa7ed5898e105d14e59f21619af9b44bc9706267508acda4b4db46134256e631f5a0ddcf4 SHA512 (FreeBSD-10.4-BETA3-ia64-dvd1.iso.xz) = 75be04149d9a4d931b41f1fd10d43ae4cb8918d29a7dc19e7041073f5375ac7cef28ce15364d438205efca91e7d8de96ff3c897565b072cbd84e24a631c689aa SHA512 (FreeBSD-10.4-BETA3-ia64-memstick.img) = 0b1a90cfa4804d5aff050b889bee1b3e44da2ed39028cec6bba47a04bdb123c525cb649a1541f83a4782ac9ae2431882768f7ae2d7bb2a28dcbcf9381ad5b009 SHA512 (FreeBSD-10.4-BETA3-ia64-memstick.img.xz) = 8d5d5309246e19317491713f3e918a1d18092569375425c3ffb3f9cb2135c1d03575d73c17cd3bff87e729a66976a866db2f3ab9ce89af4eac3985cbd18015c2 SHA512 (FreeBSD-10.4-BETA3-ia64-mini-memstick.img) = e245a6b5036d5a607acf18fd9d471c7cb5686128a3886a7ea0cac3b055c55ad025d636b9b5eb258d2c6ec1ee2685dc20ac4aeb89646050c2036025beda17d9e1 SHA512 (FreeBSD-10.4-BETA3-ia64-mini-memstick.img.xz) = ef0ef241e9120affc90d200c73b391d217cbe7d43cdb15670507f7ade89422839191399ec7442f28c42886573dc29e5fca5518039cef756c0ed1281ddc7e26ea SHA256 (FreeBSD-10.4-BETA3-ia64-bootonly.iso) = f62d3599505d6cef31950eaaf634470161cd3bcef2e1c40cf1323be2a663316c SHA256 (FreeBSD-10.4-BETA3-ia64-bootonly.iso.xz) = ad8d11fcdab462de33100458597cb5ad6ba1932ae7c1340d147e767ea7ff7b09 SHA256 (FreeBSD-10.4-BETA3-ia64-disc1.iso) = a8ae04a5cb2bddc731ec752e8b4423d9b762f095b979bf93f19f92fcb6ff5a05 SHA256 (FreeBSD-10.4-BETA3-ia64-disc1.iso.xz) = 452b912d1472f52b44939987553c6179862fa01554917171424cf5c064d2e724 SHA256 (FreeBSD-10.4-BETA3-ia64-dvd1.iso) = e801cd438ae4d3d066160d74fec7e7e683065863db6fb16e6ba3bc153ec3fff9 SHA256 (FreeBSD-10.4-BETA3-ia64-dvd1.iso.xz) = 7171dcdfdb22b2f180399ed61c1c1b05a9154479b9a2f7fc31921c1ac8ca6e54 SHA256 (FreeBSD-10.4-BETA3-ia64-memstick.img) = 0e96d327ebb1fc0dffe0fec729ed1cd11a8c163e969a8630ca1d06671fa4c5aa SHA256 (FreeBSD-10.4-BETA3-ia64-memstick.img.xz) = 8e434574fb00f971c8a601e6e8671e0ac4f6173cbca977890df1823b2a4b43e4 SHA256 (FreeBSD-10.4-BETA3-ia64-mini-memstick.img) = 5fcac652a3419004b37e807592b769a45b445ef5dc6c61d52d9e6e8594da7aa5 SHA256 (FreeBSD-10.4-BETA3-ia64-mini-memstick.img.xz) = a1bfdcbcaaad5c15e7378cf547aca8a68967f453a7169284d35a93a4a69dea6c o 10.4-BETA3 powerpc GENERIC: SHA512 (FreeBSD-10.4-BETA3-powerpc-bootonly.iso) = d6e61638582385a87a4170c975ca73be7dfd3d335751692e97a94e2f55aaf983c2c717a401f66e3e01bd6c8f0bf3744e7fdc7c1c17d37f31b12d75d920f84928 SHA512 (FreeBSD-10.4-BETA3-powerpc-bootonly.iso.xz) = b1ac85a4ebd528cb8b001a9d15d8ab6b1f187a01caa19b4ce30f96a2b3b4730f4c622d064c5e21867bb11ec4d657a075febf4ce1fd38312954aff4cc0939c7c2 SHA512 (FreeBSD-10.4-BETA3-powerpc-disc1.iso) = fa63e2a850bf490e1f22edfbe9c5d3b886185f93199fa9f5a0b0331c49570f394a993406c9d270438fb6b22390edbb47cdc5ddc6e40ec2822bc7341193e054b3 SHA512 (FreeBSD-10.4-BETA3-powerpc-disc1.iso.xz) = 0cfc1868cdea3f2edca88b5d212738f2b86c13cfd4371b528d107162c38c0f0768e7b781baade95bee7dc6096c2d0b027859280dcc757957fb8a90c56083591a SHA512 (FreeBSD-10.4-BETA3-powerpc-dvd1.iso) = 053a66fa3fa0490d1bd146dff1430f16299dfa7130969c3170f3f0995ddafe61624dd24d7ddfde3018cc35224d064e69fdaaba97121978a0d2fd7d8e34f9eb01 SHA512 (FreeBSD-10.4-BETA3-powerpc-dvd1.iso.xz) = 9ccb4a38823f6816d19cc1c6aa120fe66ebceb86f2dbc3ef76ceaafa0bc330583b347d89f2bbb0bfb059f78d060f5bda5ced9aa691618f1384e56161ef026d3c SHA512 (FreeBSD-10.4-BETA3-powerpc-memstick.img) = fa76de43f9807bc25485f6bcee78f3de54ddd1c7ff7e2fed4d4da5f23a4cd903304facd9cc48156be1fc7679d059fda8aa11cbdb9c7e24082c800a8ca050fad4 SHA512 (FreeBSD-10.4-BETA3-powerpc-memstick.img.xz) = 48a35b6cb4df6a466d8ab35f04ab66387e225f2dcc3ac39a1687da45efe3c0fe95338a3e2e830ee81ebc220294babf1a41d522fd7b4e5cb7dbb5ca181a16b2f8 SHA512 (FreeBSD-10.4-BETA3-powerpc-mini-memstick.img) = 6fd59f1f8d7b1953e0052fee9c9862eb8283b8e11662c77ef901ffc80acbe780f8ed795ddf9632eece5e4527385e47a5b47e620013de0b945fc8ab79502200b6 SHA512 (FreeBSD-10.4-BETA3-powerpc-mini-memstick.img.xz) = 92b1a08bad8ba20e26d67c6b54d2d8742138abb0b9cdfb29d0efc78e4fc1279fe9619a04c7f247f1fb2709c3fdef43248254da2a080cfc836498c8b7e89dbecd SHA256 (FreeBSD-10.4-BETA3-powerpc-bootonly.iso) = 3c1c809e60095e99c7d193513375fd7bc62bd8d82e93aa84f44e8f0d8dfa72c6 SHA256 (FreeBSD-10.4-BETA3-powerpc-bootonly.iso.xz) = a709c0e16487dce59e9a885733957fbb22df1c14ae4384785528b3069ee37c3a SHA256 (FreeBSD-10.4-BETA3-powerpc-disc1.iso) = 6d5a39d211292299d17b63866b74befddfa219a25a89cdb7e0c20aae04316574 SHA256 (FreeBSD-10.4-BETA3-powerpc-disc1.iso.xz) = 6d55da5d8caefaaa6f511a8fc340bd6853f57ebeaa58266df639da4eb4ad3f6e SHA256 (FreeBSD-10.4-BETA3-powerpc-dvd1.iso) = 3c93e26cf2514cd4e12bda3f4ddf29f7331960760867e7637aa71ad5e6f378ee SHA256 (FreeBSD-10.4-BETA3-powerpc-dvd1.iso.xz) = 34513d690223a2857c7ec7ce83fcde628fc3f35c2c33bbb1031c77526c1fa6c5 SHA256 (FreeBSD-10.4-BETA3-powerpc-memstick.img) = 5783aa8a8e39c0dfbb6cd1610ae258f2830717b764865c6e4de28e4bde99c161 SHA256 (FreeBSD-10.4-BETA3-powerpc-memstick.img.xz) = 927a0bd0915bd664670d6ee0d0e62b98e152c4de7fb4cdc509f5bd2f45c4343e SHA256 (FreeBSD-10.4-BETA3-powerpc-mini-memstick.img) = 1b269fa4d992aa8ff8d195c6ec850bd475e802282caf379007ffe465daab2f11 SHA256 (FreeBSD-10.4-BETA3-powerpc-mini-memstick.img.xz) = 03cec4160dcaac58f4e53de9218cb8bbec7587a50728ecf3186d3f72a5d46ca9 o 10.4-BETA3 powerpc64 GENERIC64: SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-bootonly.iso) = e51c4d50036da62525358a937f265376e30ab17979b2ecb223cb395e3b5d91dda0928f3cc56825334af493f96b19db6dbda7699f068cb35e84623bad673db026 SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-bootonly.iso.xz) = 6653f4a6a67137f6536dd9b13a2902b06031d8403996cd9fff20a6a1c6f571a6a7d9dba032380293c0e6e8be9a618387f55e55c497f8696dee7de2b1e9a005cc SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-disc1.iso) = f43f0e8d7ddb8085df9e23f044f8b169eb0451ae4e1958948aadc4d9acb95439986d9abfb6fdc74486eefba51f22d0458a52dac8978b92f145cd423382be1752 SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-disc1.iso.xz) = 4e8a9811276aff4f765970412f5838e58a1ff678cd47f867fd5c3d532f23ec88c7be610f087253b0000f8df12771fd11830df93bc627c7bb09ac15571a83851c SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-dvd1.iso) = 49f720cc2176fc54d4d82f1d7e16ee1a4c86e86c48b1a03826a02be92f5261d0d4eed5fe5cf0fd2bf3a07e6bed45a2949095f7db962a8f6b914c8c91ba6a5010 SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-dvd1.iso.xz) = f1557fcb7e27a4f15b9014618e409ffaab2bc13724bf32d3fe96e2ccdd559bc31d6e589d2a4c08a166cd045459d96a2cb861571de48f88288e7bd9999d08f7fa SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-memstick.img) = 320b975ad1bd68e078aa2fd9210b8a30a0a570299d6d68756ed0a7839ff7bacf958dc867255226bf6541a92403ab0351b575695e2a6c05e0719eab942b321444 SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-memstick.img.xz) = 4e656c4835e754663e7398dfef245872995a8833cb20991103c7e9545480b4edd786cb35d0970ee1ff2cd315ac9002bfc74e8700b6402e8a948ba1bf1b0b5cb0 SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-mini-memstick.img) = 010b9a28d9d6a01d041fe8cb81ce2efe2947a8686c95d3c9ff2583b65919ec6824ba6ab764e07040d7069b822ee6909e0bac69f18ac8763e962e9d690457bc96 SHA512 (FreeBSD-10.4-BETA3-powerpc-powerpc64-mini-memstick.img.xz) = 26a42980a5b2c8c85f7da3cea37d6565938f4c9500f2e2e2c8aff0d00fd7b5c7d25cbb9b58f42dd0801ceadbe35f78d530b9384faa90fc2c8710dfdd833a6a5c SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-bootonly.iso) = a87c3770a4baf9aef37dbcbb4a05059e6aee3b861bd87cee4ab27adaa2ad1c65 SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-bootonly.iso.xz) = 23c1592ac3d86b06679503ba1e4881a20066184dcdee0b6cbed530d484609331 SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-disc1.iso) = 68d918ac82eed4b7919a070466bfccc4de988a74b8215660ddc9122bc0cc2335 SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-disc1.iso.xz) = e84cda3060afc5d599c48fb65c09ced22cba70f82b69da6adc38f46902431d74 SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-dvd1.iso) = a4f83cdfcb860de7ea4afb632b4c4ee793353da0565eaed45f95ca791b956803 SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-dvd1.iso.xz) = 8a528d2a2d22ad3d473006c6e75205ff1e4945bbe895d334678da65b9ba7945e SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-memstick.img) = 3d503e74b96c6f951e40c1e63a1492d370661ba5cb76c77b92ee78a3e8991941 SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-memstick.img.xz) = 4469b7f68a617339e874bfc5eade47a87fe18bba70470729c085acdaf472bb59 SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-mini-memstick.img) = 2cd6f08dc50f3ae89ecbd19b77cede1af9cf2e2ad75033db25fb9639d27ba7f4 SHA256 (FreeBSD-10.4-BETA3-powerpc-powerpc64-mini-memstick.img.xz) = fbfbf2e27238568e50a8ccca8ec83d2fbd08edbb2b69832aba090d79d30a0e61 o 10.4-BETA3 sparc64 GENERIC: SHA512 (FreeBSD-10.4-BETA3-sparc64-bootonly.iso) = ea6c0a96c935e8e292431641a3882ececbcdee1c05d29dbf25187b1e5c274af22dbd5c0d0b88846d59aee32ac4815f6ab8b14e96c4ff2af398c74228a049836d SHA512 (FreeBSD-10.4-BETA3-sparc64-bootonly.iso.xz) = e42302dd11c5b761313551fb46b4ab8d66cd982287ffb3a792e3bae121d91e8522982a4ab39688c6e26e8ff6f34c5c9bbd0262bd708bd1daef0608b0f7340689 SHA512 (FreeBSD-10.4-BETA3-sparc64-disc1.iso) = cbe07bb7764faa363a28cab7b3e4d431169e43e342bb1e10e4fbf089efd2b166cbbaf25ace01609cb0d76bba463503ae980aad99b4a80bf083ec7d0ff35f9d0a SHA512 (FreeBSD-10.4-BETA3-sparc64-disc1.iso.xz) = b89a8d460f23a732e485686a6481c89684d93db35517b1d71a10a8a4ab6a49fdcd3fc7aa342734be7fce60026d8bea91bd68385fa47598a26f4cd4fc2bbe519e SHA512 (FreeBSD-10.4-BETA3-sparc64-dvd1.iso) = 1ccb3f0be730f7b4a76d91fe8d22244ae7b27fe8b00947aa88f5b67b5582b510b4b381261992047a06788d0fc48b21c587807e6644a7a535dcc742e693f2123c SHA512 (FreeBSD-10.4-BETA3-sparc64-dvd1.iso.xz) = 58a9c3ae488d50cd65b1bf6a62427f2833f80da8eec4580a9b221976cd192f122e4a614442c64dc660aa470c94a08dc5853b99036574cf9abf88db40b790444b SHA256 (FreeBSD-10.4-BETA3-sparc64-bootonly.iso) = 068e223e902dde6fa765219b10b47cc47d5091875ae5ea7d8a29e02827049fa4 SHA256 (FreeBSD-10.4-BETA3-sparc64-bootonly.iso.xz) = d4be653ea2ffdf0a3053f6a34780c7fccbf6631ae7a3d2e38a921c41a7d6d598 SHA256 (FreeBSD-10.4-BETA3-sparc64-disc1.iso) = bf8a9cadfb3a19d1f53627fd61a86549825567706450331be2b71ba766c5a06d SHA256 (FreeBSD-10.4-BETA3-sparc64-disc1.iso.xz) = 5674fe2c75be4e7013ce1d76275b37f643ff83b88c90e4148735bdf284220e92 SHA256 (FreeBSD-10.4-BETA3-sparc64-dvd1.iso) = ed0d0e7444b372e0703edd4490f16ea403b548c768c7b20fcb8492c0fcdd045b SHA256 (FreeBSD-10.4-BETA3-sparc64-dvd1.iso.xz) = b637b0f34c55a39f2d1662d195191824ddcc172f201e546031ee68f97e8a361f o 10.4-BETA3 armv6 BEAGLEBONE: SHA512 (FreeBSD-10.4-BETA3-arm-armv6-BEAGLEBONE.img.xz) = 816e31bc25ff6bc5778b078e6fe525172bdab2ee5bddc0e8b5be972ffc66499425163c5549fd9ecb40425abf32b0786905cd323a9f6708ebea1a6a2021942124 SHA256 (FreeBSD-10.4-BETA3-arm-armv6-BEAGLEBONE.img.xz) = dd0a8e8508afe7e544c8ab14fba1b2270ef16bf47288adeb51403206eab740f1 o 10.4-BETA3 armv6 CUBOX-HUMMINGBOARD: SHA512 (FreeBSD-10.4-BETA3-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = 256bf7d7f13a7e536beae5751a8f7689f18d213dbb3fb9af1abbce3c6b87a91de42498f8f5e9faa39a78f07abaa2d2c1ed33870d7f68285927c0c25afe31cab1 SHA256 (FreeBSD-10.4-BETA3-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = ac02ed03b694601351ef9e9bdaba7eed355ea55ee5726238e48ed473a3705aa9 o 10.4-BETA3 armv6 GUMSTIX: SHA512 (FreeBSD-10.4-BETA3-arm-armv6-GUMSTIX.img.xz) = fc8d21c75a3a468d3bd1d0e0f7541e2c0a78873dc55896c1f433b02e1bfbd246599594d895d426c06b4de2f0fd84d90714a97a1141da1a8df8317b6e0d6a20a3 SHA256 (FreeBSD-10.4-BETA3-arm-armv6-GUMSTIX.img.xz) = 52e531501e1d2dfa882ef89feb2cc94728c227ea4004404017c5ed383a1e7ffe o 10.4-BETA3 armv6 RPI-B: SHA512 (FreeBSD-10.4-BETA3-arm-armv6-RPI-B.img.xz) = 72a40e553a1cc97eeefaf64319087cc931e70551ff6842a35a397d56db6a1457ef8670dad46ec84a0df98089297f2a1ed77d4f5a9cd28b488b957511947c8db3 SHA256 (FreeBSD-10.4-BETA3-arm-armv6-RPI-B.img.xz) = 9f621f6b456ddb00dab272e74bedd753864f1ba20db4cc22901b0df5f63dafc2 o 10.4-BETA3 armv6 PANDABOARD: SHA512 (FreeBSD-10.4-BETA3-arm-armv6-PANDABOARD.img.xz) = d3c3e705a6a4462549f519f36403d4b441c0c93f7cc6e8302a6ae65104c9fa437e8f926130bf5fd9a5f62eb45bcbe2b0312dd1c927f4315c7dcc6f2b8a00f047 SHA256 (FreeBSD-10.4-BETA3-arm-armv6-PANDABOARD.img.xz) = 0ffacea2b475714c635a6ec9946213e6ea36c39bbb99581acfcb55cc58175552 == VM IMAGE CHECKSUMS == o 10.4-BETA3 amd64: SHA512 (FreeBSD-10.4-BETA3-amd64.qcow2.xz) = 10dd4d1be34cda4fcedee9f020d116e96cfeb13b6fa211db6fbdc36c41c553bceabee9ac989dc9beb683995a53769da75f2ad828728a8df3a42377fb46248342 SHA512 (FreeBSD-10.4-BETA3-amd64.raw.xz) = 8a91b47fc5d7f11d2c9e88c0b7ce5ce526724d0c2cc5f943d039b5996e0f15083a1b372326e50d3e1d7fa184b25de6a318b66964a6c351fd65f0cdcfa2dd2a4b SHA512 (FreeBSD-10.4-BETA3-amd64.vhd.xz) = 812f32857e8ee1c9b978abd90ba6c233e097e9d80e916b405854857f9e74e573bc7d3ad73ff42361117ef7457097fae8a2363a679e9bcc499c22dc584bffdcb3 SHA512 (FreeBSD-10.4-BETA3-amd64.vmdk.xz) = ed2467c9c5c956eb4337583d873783d240c671240404faeacf8dc1ccfef6676f088ff5f455578efcc5641a4352c9f3b5f124aaa01f0522ac02a74f4229b67da3 SHA256 (FreeBSD-10.4-BETA3-amd64.qcow2.xz) = 7e9c7837b68c3e16d12e94732a1a69a0c5f627d942506c0fb385115db77f2384 SHA256 (FreeBSD-10.4-BETA3-amd64.raw.xz) = 5a18de30287c608cacd40683becb581b6a3ba9dfa0919f1f7382b477a0b57702 SHA256 (FreeBSD-10.4-BETA3-amd64.vhd.xz) = 5305714a3ecbd05c9f9d17c111fbaedb56a63059bfb3802323d6fbac0d91c962 SHA256 (FreeBSD-10.4-BETA3-amd64.vmdk.xz) = 40389a4999c75e39316fce5725e2d6823738c325832df28404e6ee6d7800dadf o 10.4-BETA3 i386: SHA512 (FreeBSD-10.4-BETA3-i386.qcow2.xz) = 0dd8a2d1abebc28be4a18897fec181c50c995965863425037f0caa289051fe81b68aa6ab2d7ef8693a51a58fc8ec56df93c3a1e0c007a65fe370697aebe2c75e SHA512 (FreeBSD-10.4-BETA3-i386.raw.xz) = 32ed462c47278baf2c60bbef7a8d33fcc30e3254997928f2013d739190ab707eb589e754863b15d77ddc2d85fadf8035e3bf943b63424b0e45ba21b4b58c8dff SHA512 (FreeBSD-10.4-BETA3-i386.vhd.xz) = fda06b22df954f41725e8e28743db6b854b699f2293d5a9294b1fef23c2f6338a95f364acb71db76523d6e9324c775574bb3c1776a02104ef561ead0f07cb7d0 SHA512 (FreeBSD-10.4-BETA3-i386.vmdk.xz) = 8af7d76c73faef4fced294a6f3026a70b0520da63c31343615c27bd7c27d53857660705c803458dfe3fd6cc0e1ef3e10597d695437ad60cc16537aa6722d5693 SHA256 (FreeBSD-10.4-BETA3-i386.qcow2.xz) = a84ca385f56381ec4984311c3bb23d8f68f9e336e59314968d81d68362fd9204 SHA256 (FreeBSD-10.4-BETA3-i386.raw.xz) = fc7e760711a174e1a578e0cffe678fd03f0c38e4a35d1ce2911791b04cc5b8ff SHA256 (FreeBSD-10.4-BETA3-i386.vhd.xz) = f55c83d65de7c0d183c3fc92486903d9a12432cec86ca3ff1d766206fdf7ddc5 SHA256 (FreeBSD-10.4-BETA3-i386.vmdk.xz) = 5d12a20dbbfaa5e162895ab2af68c1bb637a9645daf6700913e5dea7e4c34156 Regards Marius -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJZqxbOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1M0Q5QjQzNTVGOTU5ODBGQzVENzZCMDIy MEI3MERFMTNGMUQxRTRGAAoJECC3DeE/HR5PV30P/jikpnz2jkdLvN+YYrf0GrvA GL2sMYhMNAiNztVPW2YEpI8l9nhgdnJyW8jk5nvQ0sPvvRnWEaLpn+QuGqJKO+rn SFoCyq47hj3OTXx6dXgAOJn2TOn9WMGfmTmds/YrWsAp7FUcL7aPPsicZnmmrVzm WO9rFhGoHOaF00kh8DZ/Q+mDblZhzsahO2kbg4/Epa/ODxBV//KKGwDWY0xyp7c5 pZffHaL/FydqvlIN6Kmgi29lFOpfUya84H+8TmTPxGHsZvavAEu2oz5I8J8zVvKN jTNZgAk1f5MG1+uJowwY5eR+HvgkgB2DoTFPL4BIv9FMqEnz1yoRCkFRx64/Q+j6 55ykg1Hi4e7xvZtJH/06LVbynUYAsEZNPHsOumOqateGDxyUpBk4BWFO9u3oY+oo KTKC74+kJ+iZFH+JseBfHFlBAYh3+RDq7UYIuqurAkTMz0cl08q1JcYQYJoAKiJR WOJ+giepqodg9yQZ7fgK+t7Y1kbHNTs9Vlg1L0Y3b2vG9IaPU6b0DkgUBAsscYUp jpJWMbMSksd//N8PQhPgy6JuMfO0Z/5YjWejYFQEZEt3pT7EhzRqczuFXxhAJ3P7 I4WwgAMKRF2HCXL7U9ElmMTMygCQuoQVQ7ruVTm4bwD23yAnTK+djYvKksYsE8RI SbiAkG6SdHp0GQDQbAKr =ix1C -----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Sat Sep 2 23:06:37 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F035DE093C9 for ; Sat, 2 Sep 2017 23:06:37 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from ua.ulka.com.au (ua.ulka.com.au [203.217.10.26]) (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 645F973C16 for ; Sat, 2 Sep 2017 23:06:36 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from PLUTO (pluto.ulka.com.au [10.0.0.27]) by ua.ulka.com.au (8.14.7/8.14.7) with SMTP id v82N6QuL052413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 3 Sep 2017 08:36:26 +0930 (CST) (envelope-from vpc@ulka.com.au) From: "Priyadarshana Chandrasena" To: "'Mark Saad'" , Cc: , References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> <20170902.174119.74668153.sthaug@nethelp.no> <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> In-Reply-To: <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> Subject: RE: HP Smart array P440 support Date: Sun, 3 Sep 2017 08:35:31 +0930 Message-ID: <000001d3243f$ff2d3a10$fd87ae30$@ulka.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKf262D1pzaEW0PjHJqNu5p+S/e0gHTaXA5AxT7FosCgV+fHaDNeiOQ Content-Language: en-au X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Sep 2017 23:06:38 -0000 I will try to install 10.3 and thanks for your comments and help. Regards, Chandrasena -----Original Message----- From: Mark Saad [mailto:nonesuch@longcount.org]=20 Sent: Sunday, 3 September 2017 3:56 AM To: sthaug@nethelp.no Cc: vpc@ulka.com.au; rainer@ultra-secure.de; FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support All Also don't forget to is install cciss_vol_status to monitor the array . --- Mark Saad | nonesuch@longcount.org On Sep 2, 2017, at 11:41 AM, sthaug@nethelp.no wrote: >>> I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in=20 >>> it. I have a HP smart array P440 in my server. I can not find out=20 >>> anywhere if ciss driver support include HP Gen 9 storage=20 >>> controllers. Could you please update the ciss driver in 10.3? >>=20 >> Try 10.3 >>=20 >> I know the release-notes say nothing about it, but I believe it is supported. >>=20 >> If not that, 11.0 surely does (even though the release-notes=20 >> don=1B$,1ry=1B(Bt mention it, either) >=20 > I can confirm that 10.3 supports the P440 controller. From a DL360=20 > Gen9 server running 10.3 here: >=20 > ciss0: port 0x2000-0x20ff mem=20 > 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff irq 16 at device 0.0 on=20 > pci3 > ciss0: PERFORMANT Transport > ... > da0 at ciss0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SPC-3 SCSI device > da0: Serial Number PDNLH0BRH8S3RF > da0: 135.168MB/s transfers > da0: Command Queueing enabled > da0: 139979MB (286677120 512 byte sectors) >=20 > Steinar Haug, Nethelp consulting, sthaug@nethelp.no=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list=20 > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"