From owner-freebsd-current@freebsd.org Sun Apr 9 03:26:24 2017 Return-Path: Delivered-To: freebsd-current@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 4A695D358C5 for ; Sun, 9 Apr 2017 03:26:24 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mail-lf0-f67.google.com (mail-lf0-f67.google.com [209.85.215.67]) (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 EE29CD6A for ; Sun, 9 Apr 2017 03:26:23 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mail-lf0-f67.google.com with SMTP id 75so506369lfs.3 for ; Sat, 08 Apr 2017 20:26:23 -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:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=/UFj26tTrMgA8fHmlXlRCS0zHo5krwac478iVd1tB6Q=; b=Ywqv+chnCGubpzySDzQAeVYAeKib3hOL+aLYnguYAlrCOuaWkJ8uPpAnj8DptsxjEo WqvyzCkFhZoFYsgTzVjIoK4iHGsFC5fBFKN4bWbVsSsEbH/c4GGH4E2l61//UKXM1Lsr J0ruCc7jPnOPtuPEJuiZ5qIZsszHrGxRTZJjB9t6h18lanOXpORPx1AL1cV2e36qDNMD rJ7kMAUIoglQ5khl8pov7hfck0ceyLIlWgImwVcswfwTA/5a/bXoC6jp1jLHxD143jiR Xuab+V732q/Od5SAZBvmJuO0FyTgCL1DBf2xHs4sq7uzCfMz7DPiUApZizdWGwpPaJWG C8sA== X-Gm-Message-State: AFeK/H3FjLmUfHMGGg3PNTtBgvXG0p8JC6lbbykAP8Awv0WN4ps6gsac/bsfJj+x0o7GwA== X-Received: by 10.25.32.9 with SMTP id g9mr15393085lfg.7.1491708375648; Sat, 08 Apr 2017 20:26:15 -0700 (PDT) Received: from [192.168.1.2] ([89.169.173.68]) by smtp.gmail.com with ESMTPSA id h10sm1974365ljh.59.2017.04.08.20.26.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Apr 2017 20:26:15 -0700 (PDT) Subject: Re: problem with ls, not show a correct list To: =?UTF-8?Q?Nilton_Jos=c3=a9_Rizzo?= , Toomas Soome References: <25969d2c-6857-77a4-86a4-08b22f15cbfe@freebsd.org> <7a08478e-ee7c-70f6-1b52-bb966f47c594@freebsd.org> <1ba4fb7aa090271be631f01e9f72d844@i805.com.br> Cc: Allan Jude , FreeBSD Current , owner-freebsd-current@freebsd.org From: Andrey Chernov Message-ID: Date: Sun, 9 Apr 2017 06:26:09 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1ba4fb7aa090271be631f01e9f72d844@i805.com.br> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2017 03:26:24 -0000 On 07.04.2017 23:20, Nilton José Rizzo wrote: > Em 2017-04-07 05:51, Toomas Soome escreveu: >>> On 7. apr 2017, at 11:29, Andrey Chernov wrote: >>> >>>> Hi Allan, the ls show all files without case match >>>> >>>> ls [a-z]* >>>> >>>> show all files beginning with a and A like this [aA-zZ]* >>> >>> No, last "Z" is not included. > > > Look this, it's a great error!!!! I see no error. You do not include Z into [a-z] expression above, so why you expect it is unknown. > I lower- equal a upper-case why Z not show in this list? No, it is not case-equal sorting. As I already mention, it is dictionaries sorting, letters considered first, their case - next (and maybe many other factors for non-ASCII - next). > image when a admin use like thinks some rm -rf /*/[A-Z]* Admin should either run C or US-ASCII locale or do not use a-z ranges without knowing sorting on his locale. I see no errors in your sh examples. In general it was decided (not by me) to use CLDR collation since it is able to stable sort all Unicode chars. From owner-freebsd-current@freebsd.org Sun Apr 9 16:32:09 2017 Return-Path: Delivered-To: freebsd-current@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 ECE85D36FC2; Sun, 9 Apr 2017 16:32:09 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from server.i805.com.br (mailhost.i805.com.br [50.7.9.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fbsd10.amd64", Issuer "fbsd10.amd64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BE543DB3; Sun, 9 Apr 2017 16:32:09 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from server.i805.com.br (localhost [127.0.0.1]) by server.i805.com.br (8.15.2/8.15.2) with ESMTPS id v39GVos6030182 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 9 Apr 2017 13:31:51 -0300 (BRT) (envelope-from rizzo@i805.com.br) Received: (from www@localhost) by server.i805.com.br (8.15.2/8.15.2/Submit) id v39GVnpZ030181; Sun, 9 Apr 2017 13:31:49 -0300 (BRT) (envelope-from rizzo@i805.com.br) X-Authentication-Warning: server.i805.com.br: www set sender to rizzo@i805.com.br using -f To: Andrey Chernov Subject: Re: problem with ls, not show a correct list X-PHP-Script: www.i805.com.br/roundcube/index.php for 186.221.219.53 X-PHP-Originating-Script: 80:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sun, 09 Apr 2017 13:31:48 -0300 From: =?UTF-8?Q?Nilton_Jos=C3=A9_Rizzo?= Cc: Toomas Soome , Allan Jude , FreeBSD Current , owner-freebsd-current@freebsd.org In-Reply-To: References: <25969d2c-6857-77a4-86a4-08b22f15cbfe@freebsd.org> <7a08478e-ee7c-70f6-1b52-bb966f47c594@freebsd.org> <1ba4fb7aa090271be631f01e9f72d844@i805.com.br> Message-ID: X-Sender: rizzo@i805.com.br User-Agent: Roundcube Webmail/1.2.3 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on server.i805.com.br X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2017 16:32:10 -0000 Em 2017-04-09 00:26, Andrey Chernov escreveu: > On 07.04.2017 23:20, Nilton José Rizzo wrote: >> Em 2017-04-07 05:51, Toomas Soome escreveu: >>>> On 7. apr 2017, at 11:29, Andrey Chernov wrote: >>>> >>>>> Hi Allan, the ls show all files without case match >>>>> >>>>> ls [a-z]* >>>>> >>>>> show all files beginning with a and A like this [aA-zZ]* >>>> >>>> No, last "Z" is not included. >> >> >> Look this, it's a great error!!!! > > I see no error. You do not include Z into [a-z] expression above, so > why > you expect it is unknown. > >> I lower- equal a upper-case why Z not show in this list? > > No, it is not case-equal sorting. As I already mention, it is > dictionaries sorting, letters considered first, their case - next (and > maybe many other factors for non-ASCII - next). > >> image when a admin use like thinks some rm -rf /*/[A-Z]* > > Admin should either run C or US-ASCII locale or do not use a-z ranges > without knowing sorting on his locale. > > I see no errors in your sh examples. try this ls [a-b,k-m] in sh using the locale setting to pt_BR.UTF-8 it's not work # locale LANG=pt_BR.UTF-8 LC_CTYPE="pt_BR.UTF-8" LC_COLLATE="pt_BR.UTF-8" LC_TIME="pt_BR.UTF-8" LC_NUMERIC="pt_BR.UTF-8" LC_MONETARY="pt_BR.UTF-8" LC_MESSAGES="pt_BR.UTF-8" LC_ALL= # ls [[:lower:]][a-c,k-m]* aa # ls a b d f j m p t x A B D g k M q u y aa c e h K n r v z Aa C E i l o s w Z # It's not show the correct list, this commant MUST BE SHOW like a C locale # locale LANG=C LC_CTYPE="C" LC_COLLATE="C" LC_TIME="C" LC_NUMERIC="C" LC_MONETARY="C" LC_MESSAGES="C" LC_ALL= # ls [a-c,k-m]* a aa b c k l m # ls [[:lower:]][a-c,k-m]* aa # When I try to use the poor workaround [[:lower:]] or [[:upper:]] this have too different behavior. The list replacement not work properly Note, I know that Unicode have some differents, but when tha basic list replacement and other basic default behavior must be preserved. > > In general it was decided (not by me) to use CLDR collation since it is > able to stable sort all Unicode chars. > It's a great problema yes!, the default shell in FreeBSD to user root in fresh new installation is csh, look the passwd file root:*:0:0::0:0:Charlie &:/root:/bin/csh and it's will be great problem because all man pages with trate a list substitution not say anything about this. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" -- ******************************************************** * Nilton José Rizzo Sistema de Informação UFRRJ * * http://cursos.ufrrj.br/grad/sistemas/ * * lattes:http://lattes.cnpq.br/0079460703536198 * ******************************************************** From owner-freebsd-current@freebsd.org Sun Apr 9 17:01:43 2017 Return-Path: Delivered-To: freebsd-current@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 1626AD36B86 for ; Sun, 9 Apr 2017 17:01:43 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mail-lf0-f67.google.com (mail-lf0-f67.google.com [209.85.215.67]) (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 B9B3CED0 for ; Sun, 9 Apr 2017 17:01:42 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mail-lf0-f67.google.com with SMTP id x72so2173585lfb.1 for ; Sun, 09 Apr 2017 10:01:42 -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:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=cUHpENRWy78tgMrND82+SGmxgyopecDtyb067deDFv8=; b=IHbeYkMykT7q/ptQ+hCWLaMWN6s+5U634e2bul68oMZuW1oKo6b+SMekEkkdvstevu w7kSeCqv44iv2VK43gYF/YO74iyRTcAhLWpwtb5FBOWJfbQI0f+VBFG65Mt9bzloTZhm gNPbgn/rOrgBWd1jW/3lm1lpW8nmWX5wNzZcukisJISO/P0Wnyw4IhrIHO6s3sZwd+ma 2xAY5UdMeNqh7S92hf2w2UmPwKxUZ6PI1C6f9iKidgJvX7Mxc+S0/z6FCATNJMmhZQ1s dsc2jKueuHNRaXmL++Y1aqKaCrcISg353Tkk0/bdi23cncT5jDQgW3o6XzS6GHBzdGMM VCRQ== X-Gm-Message-State: AFeK/H2o5/jEug097NU7M/VrfM8tLIAhGojCYVLgqnf88XX6cY5OgC9/IYm9p5hAsDdy4w== X-Received: by 10.25.212.144 with SMTP id l138mr14511926lfg.26.1491757300242; Sun, 09 Apr 2017 10:01:40 -0700 (PDT) Received: from [192.168.1.2] ([89.169.173.68]) by smtp.gmail.com with ESMTPSA id y25sm2303537lja.7.2017.04.09.10.01.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Apr 2017 10:01:39 -0700 (PDT) Subject: Re: problem with ls, not show a correct list To: =?UTF-8?Q?Nilton_Jos=c3=a9_Rizzo?= References: <25969d2c-6857-77a4-86a4-08b22f15cbfe@freebsd.org> <7a08478e-ee7c-70f6-1b52-bb966f47c594@freebsd.org> <1ba4fb7aa090271be631f01e9f72d844@i805.com.br> Cc: Toomas Soome , Allan Jude , FreeBSD Current , owner-freebsd-current@freebsd.org From: Andrey Chernov Message-ID: <908cb150-022d-7725-9b6f-866209a31cbb@freebsd.org> Date: Sun, 9 Apr 2017 20:01:33 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2017 17:01:43 -0000 On 09.04.2017 19:31, Nilton José Rizzo wrote: > try this > > ls [a-b,k-m] > > in sh using the locale setting to pt_BR.UTF-8 > > it's not work For the set below I got on -current a A b k K l m with any non-C locale which is right. > # ls > a b d f j m p t x > A B D g k M q u y > aa c e h K n r v z > Aa C E i l o s w Z > It's not show the correct list, this commant MUST BE SHOW like a C > locale Must not, according to CLDR linguists. > Note, I know that Unicode have some differents, but when tha basic > list replacement > and other basic default behavior must be preserved. No, Unicode is the same here, all sorting done as described by CLDR rules. From owner-freebsd-current@freebsd.org Mon Apr 10 01:08:14 2017 Return-Path: Delivered-To: freebsd-current@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 45DE1D35F29 for ; Mon, 10 Apr 2017 01:08:14 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 32D8A7E3 for ; Mon, 10 Apr 2017 01:08:14 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 32315D35F28; Mon, 10 Apr 2017 01:08:14 +0000 (UTC) Delivered-To: current@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 31D32D35F25 for ; Mon, 10 Apr 2017 01:08:14 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC22C7E2 for ; Mon, 10 Apr 2017 01:08:13 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1cxNoK-0002xj-TY for current@freebsd.org; Mon, 10 Apr 2017 03:08:04 +0200 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1cxNoK-0000K1-S7 for current@freebsd.org; Mon, 10 Apr 2017 03:08:04 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); for ; Mon, 10 Apr 2017 01:08:04 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "current" Subject: new problem? Date: Sun, 09 Apr 2017 18:08:04 -0700 (PDT) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 01:08:14 -0000 i386_set_ldt: start=3D-1 num=3D1 descs=3D0x38449fac Tons of those, eight at a time, newly spamming /var/log/messages, maybe aft= er a fsck_ffs -y the partitions after a crash, that fixed it, as in df=20 df output, then eight of the above line with the hex values varying only ls ls output, then eight of the above line with the hex values varying only ...................................... 2nd problem persistent LOR in [several] nvidia_os:c:662, 824 =20 [dmesg only, above, ] vfs_mount.c:1277 ffs_softdep.c:1908 vfs_subr.c:2600, 2150,=20 ffs_vnops.c:280 vfs_bio.c:3500 ufs_dirhash.c:281 vfs_syscalls.c:3364 [some above also in dmesg, most in /var/log/messages... and another one or two I've wrote down but lost, gfvs_* I think. but that line above may be the cause of the i386 line at the top. ????? N= ew one to me.=20 Sorry. !=20= From owner-freebsd-current@freebsd.org Mon Apr 10 06:50:42 2017 Return-Path: Delivered-To: freebsd-current@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 2C6F6D36D6F for ; Mon, 10 Apr 2017 06:50:42 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F09E7D0C for ; Mon, 10 Apr 2017 06:50:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-pg0-x22c.google.com with SMTP id x125so101031024pgb.0 for ; Sun, 09 Apr 2017 23:50:41 -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=mTX96eL8RelnglQrdpHPnJEOsd7l8gPLEU5wMTjBcgA=; b=CS1Mjjn72HqhLf3hupOzv30pbF2bzt/Fhu1np0f4mp9PTNR87ES/rMiAI7tkh0lqPf kSYE80CohsNCscxMB9CBAfFkagii1s4haH0Q4m17vmF1Vw2esADMMAikBEhj2Dd5++oj /+s4h18f9Wfti9dIKr2+9L8lAGqvK+SgINZMgh++P00vwKkeDdV65REPN4XIo3nF+iPz 5cOBITINeEL7k+1g8ESIe+VyTISSd45pgjOcFfJs2W4Yjt2R9Bs86ES6/NDJ8+GgHuVv 5JnbAZmkjRtr2+jIeCTDw5XZFPBjjMuvN8ecb6zYTEfqNDM89YEc8YweDX+xw/ZE8IzZ z5uw== 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=mTX96eL8RelnglQrdpHPnJEOsd7l8gPLEU5wMTjBcgA=; b=ZOtfqu/eTxfKUX0Idp8xbgMpXr0QtDk0Z76Z0cvHg7vTokwuTqW6XDD9OTQbGBnvt9 0jUJ6HA2z/FedTBjKzACzfU1o0z4YhpGCQcwbqRZM/euGf79PDOcydnbuyWxuvkyckXy GqGK0YEvd84CZfMApLD1BsaskMKAfltJT6iBDwa0boFe3E0P5mpbYj4wnMgk4+bIr3Q0 QxQ+jobjxv5qjCWy93yhNyv8e/rUKf+cwjpGboDhzqWhKEc09kG9PEf4Ue3Xd731bjXk G1u4FSX9tQiEYvPObkhIG7+wyoeFHjjBFqRY77ysoMyDJyDvdViUwTQABIQWrzlYC3bL PBdA== X-Gm-Message-State: AN3rC/7V//eWqERo6l6MfjgvwM+u5lq+eFVVwqxSONZfmozqF1JmDiIp0U7BoF0rREhBbRxsCnTYufDpTUcJJg== X-Received: by 10.98.58.3 with SMTP id h3mr6890723pfa.27.1491807041549; Sun, 09 Apr 2017 23:50:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.159.8 with HTTP; Sun, 9 Apr 2017 23:50:40 -0700 (PDT) Received: by 10.100.159.8 with HTTP; Sun, 9 Apr 2017 23:50:40 -0700 (PDT) In-Reply-To: References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> From: Pavel Timofeev Date: Mon, 10 Apr 2017 09:50:40 +0300 Message-ID: Subject: Re: VNET branch destiny To: "Bjoern A. Zeeb" Cc: freebsd-current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 06:50:42 -0000 31 =D0=BC=D0=B0=D1=80=D1=82=D0=B0 2017 =D0=B3. 17:40 =D0=BF=D0=BE=D0=BB=D1= =8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Bjoern A. Zeeb" < bzeeb-lists@lists.zabbadoz.net> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: On 31 Mar 2017, at 13:57, Pavel Timofeev wrote: Hello, dear freebsd-current@! > > There was FreeBSD Foundation report back in 2016Q2 where it told us > about VNET (VIMAGE) update project sponsored by foundation. > What is the current situation? Is it committed into base? If not > what's the plan? > Changes are in 12 and 11. 12 has seen more slight fixes due to other changes that other committers are tracking and I hope they merge to 11. /bz Sorry, do you know if there is any plan to include VNET into GENERIC? From owner-freebsd-current@freebsd.org Mon Apr 10 10:33:19 2017 Return-Path: Delivered-To: freebsd-current@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 319B8D35087 for ; Mon, 10 Apr 2017 10:33:19 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq6.tb.mail.iss.as9143.net (smtpq6.tb.mail.iss.as9143.net [212.54.42.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E3B1087C for ; Mon, 10 Apr 2017 10:33:18 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.42.135] (helo=smtp11.tb.mail.iss.as9143.net) by smtpq6.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cxWGz-0008IZ-1g; Mon, 10 Apr 2017 12:10:13 +0200 Received: from 5ed15678.cm-7-2b.dynamic.ziggo.nl ([94.209.86.120] helo=wan0.bsd4all.org) by smtp11.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cxWGy-0000gK-Vl; Mon, 10 Apr 2017 12:10:13 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id 028C67BD9; Mon, 10 Apr 2017 12:10:11 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99v1BdEDnduV; Mon, 10 Apr 2017 12:10:08 +0200 (CEST) Received: from [192.168.1.64] (mm [192.168.1.64]) by wan0.bsd4all.org (Postfix) with ESMTPSA id 37EF47BD2; Mon, 10 Apr 2017 12:10:06 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: VNET branch destiny From: peter.blok@bsd4all.org In-Reply-To: Date: Mon, 10 Apr 2017 12:10:06 +0200 Cc: "Bjoern A. Zeeb" , freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> To: Pavel Timofeev X-Mailer: Apple Mail (2.3273) X-SourceIP: 94.209.86.120 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=QacWhoTv c=1 sm=1 tr=0 a=IkzOOneQUJP1+bAPekPvBg==:17 a=IkcTkHD0fZMA:10 a=AzvcPWV-tVgA:10 a=pGLkceISAAAA:8 a=9bHR7MVLAAAA:8 a=6I5d2MoRAAAA:8 a=fPk2_tupby7NrgzYZxYA:9 a=QEXdDO2ut3YA:10 a=6kGIvZw6iX1k4Y-7sg4_:22 a=I7KxNEAtLM9g1UmuDjRu:22 a=IjZwj45LgO3ly-622nXo:22 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 10:33:19 -0000 There have been issues with pf if I recall correctly. I currently have = issues with stable, pf and vnet. There is an issue with pf table entries = when an interface is moved to a different vnet. Does anyone no if there is a specific fix for this that hasn=E2=80=99t = been ported to stable? I haven=E2=80=99t had the time to test this on = current. Peter > On 10 Apr 2017, at 08:50, Pavel Timofeev wrote: >=20 > 31 =D0=BC=D0=B0=D1=80=D1=82=D0=B0 2017 =D0=B3. 17:40 = =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C = "Bjoern A. Zeeb" < > bzeeb-lists@lists.zabbadoz.net> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB= : >=20 > On 31 Mar 2017, at 13:57, Pavel Timofeev wrote: >=20 > Hello, dear freebsd-current@! >>=20 >> There was FreeBSD Foundation report back in 2016Q2 where it told us >> about VNET (VIMAGE) update project sponsored by foundation. >> What is the current situation? Is it committed into base? If not >> what's the plan? >>=20 >=20 > Changes are in 12 and 11. 12 has seen more slight fixes due to other > changes that other committers are tracking and I hope they merge to = 11. >=20 > /bz >=20 >=20 > Sorry, do you know if there is any plan to include VNET into GENERIC? > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Mon Apr 10 12:10:21 2017 Return-Path: Delivered-To: freebsd-current@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 01B40D361B9 for ; Mon, 10 Apr 2017 12:10:20 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57B8412CE for ; Mon, 10 Apr 2017 12:10:19 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MACmL-1cmFbO2ZVh-00BL0v for ; Mon, 10 Apr 2017 14:10:11 +0200 Date: Mon, 10 Apr 2017 14:10:03 +0200 From: "O. Hartmann" To: freebsd-current Subject: CURRENT: Compile time of ports has increased significantly since LLVM 4.0 Message-ID: <20170410141003.7d422d86@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:Wa1w0ZudyCGEmpPHSAeNN85Rvgqi9lV7bg7tbp8zJMyYvk/5f9A sCEv5mnEF3LWPZRaiIaYBb/cLqJoyWq07GLdiABNir8ieHJI3SDwjdl6iXE62ewUbCnE0Qa VPA973UCGB5gLiOOOGkVSYeAyhnfigojoUBedGJiaTPgl8RQAeIWqQPBoDqz4J8bHGXFcMC SdkkZ/k6/ZtRtrS6GKRIg== X-UI-Out-Filterresults: notjunk:1;V01:K0:TLz8U1PqfO0=:syzMDegN0fdnzO1vnuxr/2 pGIixB7FzMc53S8u8Sg780nRIdOHwnqQBlhlw6XN3nbzXQW6E5nWc3rTjrMwRy9u2sht/d4kX QY0x0lOfzQfxF2LCe4O+SFKxe9r9LHPAY8Wye4qmj/vLNnGqdMEXET2S4Od0wkBHrAykNb75U cIPoEnVO8boNQPTK2PB5KrUvIK6pGGVpXbzrfFEG3Np24ti2Dp2Q1UdDKbGCt2M4IRglOIbDx GkObqTXFddl84WuhJvqeRbr0zHECCga7BqWJc1VFMphFoIK8Cl+A9KWTexu4PqZItA6wlBKz3 zu1HYTS0Hnse0avk79aPBYHDveUC8OEkB3Zt5x7H/MZ9+KYk4v6zyjOGiRj9vqdtifTqSxxRn z1wIBoLxUfeTyIGwPL0dw4MifB9WVNHhH/fIVo4KZ6gZzJVquEVcGmX+f1qcRUZmonnWbdOxA zxHqkOFzbPs/VEGLyKrLYA7AXsFSkeNcoaVCIdq0YaaqyeX4QL5xM3A3cxP/nKeudSdgNGv/s jaIAkmcn9kC5MYGwzcmuk1+8hkGnZH1V8+IhCH0itatmq+PU5v1NNBUuorkemfnqKo3RXdrfD feEiiosm/L33w7I8ktgz2fHRDKGTQgOYZs/NCzZQp3B1PaU27JogxFeApgYd0QzjP34iSOxv1 JEPXiJURikqdAUqQxsv6cS+IFi8HDnLPyLUjrluhVeMtEetDT0PIPXcSjXJlLi+szugIlvvmV bGFzpjaS06N2Vz0dHY4/qGEIB6J5+rBgZ0zwmberaCi2ZX9MEluO8ZoPVWz4RJ5IX9eIwSiaz 0y1RASO X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 12:10:21 -0000 We build pretty often world and ports. With poudriere as port building backend, The daily/weekly builds have now grown in compile time significantly since approx. the introduction of LLVM 4.0 into FreeBSD. The build box is a LGA1150 IvyBridge XEON system with 3,4 GHz and 16 GB RAM. The configuration of poudriere (most recent ports tree version, as well as most recent CURRENT host and most recent CURRENT jail: FreeBSD 12.0-CURRENT #4 r316067: Tue Mar 28 06:26:18 CEST 2017 amd64). Within the past 4 - 6 months, wekbkit-gtk2 and webkit-gtk3 took ~ 1h 90 min, or, when started together, ~ 2h 40 min. Now they take each(!, even separately started and indivuidually conmpiled without concurrent jobs) more than 3 hours. The same with /editors/libreoffice. On this bos it took 2h 40 min to compile libreoffice 5.2.X up to 5.2.6, now it graces or is beyond 4 hours! This observation is taken from a time span of 5 - 6 months and even with worst case scenarios like parallel start of webkit[2]-gtk[23] in parallel. So, does someone also diagnose this compile time stretching? I also see this while regularily building ports via "make" in /usr/ports. Thanks in advance, Oliver From owner-freebsd-current@freebsd.org Mon Apr 10 12:59:05 2017 Return-Path: Delivered-To: freebsd-current@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 E7F36D36F03 for ; Mon, 10 Apr 2017 12:59:05 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DA302AE for ; Mon, 10 Apr 2017 12:59:04 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M6ioC-1cCDXp0CRQ-00wWLg for ; Mon, 10 Apr 2017 14:58:57 +0200 Date: Mon, 10 Apr 2017 14:58:55 +0200 From: "Hartmann, O." To: FreeBSD CURRENT Subject: r316677:EFI boot failure: Can't load kernel Message-ID: <20170410145846.73d4350a@hermann> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:M+ZEqXE2BOfrFisfpqIAEPPPmLIG6aTmIlYP7koT5Y0AP/iyNcd P3gbj3/iOVi1zKcrrfRNVNCyg9ZR0g2gucIAVQZPmQl0kyHQBBvE6BvAGcgBO3EhnI+cRUV 7I4hmvdgye9aCbuOm7Ycmt9yZlgU5d6dAzMdPzFcJgCwEdWCPbk/mC2tPOiaDYz/X7BJAcr 84zlmHxR/wB4IBp4bUEsg== X-UI-Out-Filterresults: notjunk:1;V01:K0:GgTIJE8MAco=:KeRtZsY12xSybKMSAflh+X be4R2Rc/gMpVLGC41c/Nc+sGEwt7cU0sm9V6rL5Phoycc9yI1e6G5EXJstsahE537vZZXXXH5 2RAn9/D6zssHvJr6bfMHSC96EF4ozvesxkYB36CGUnRPaPikAQrZ1GwADKfaF0BEllzHrHrg3 BoynlN/Wl5rJrhQxq2j1g6Gas7wyvlAYcsOPanw0lfRD8FEahXr2J6GcQX0QRLlPUOvvOjL4r p7gE+JeulNRYOh4n8KWz6F6hwNPXyiAWBD9Eu9cGaTxlZhkvEnS96CG6M1YgstSZRyrzDD1Xj yZkxEIoSr5hO2v/hfmg9fTRfMdSRIa4U8UmK0XBjbD2QTiz7nOH3TdmkYzwrgtFSMfVrEbgEI /eC+xRGkEVCi1nQX7exj7nlw5Pj8i2GtguptGzNaeAyQGLTMKA1NGGJyt/QnppamBu+MR8+4k uvKdm7N8Sd2q7H6I5XgwPgM4HpntgqIt+1auNbeldNwjSPsIE9FtkqvyDs/dJEN2lxX/55EBK 9zg0nr1Fmx3THjxnjB9tv1EmI0oEYr0HHo93NDHwaPbzbdgKP6c+89YaDpX3XvAJ37IYlF15z GCNXaKdnDJDHkzW+zh026MROqJLpkO3OBTWwnbmin6znl4Aw39YAKkKt6ECI++NHFtQF5+TL4 yORMD1ldKz1CCCsveir4FMeCm5taDJ4CXkYtYYsdR3ONuT3POQXsl7xio3qg9ToTsq26z5bT6 SPuYe6VfPJ10L8YY4VHQXsSeXEsGrTAHevDyFMrwQ7ZJjY2u8R0reHYdLjZmkM8oaEn38EzX2 exC7qQZ X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 12:59:06 -0000 After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740 XEON) reject to boot properly. They die immediately after loading /boot/loader.efi and jump into loader prompt: [...] \ can't load 'kernel' I had to investigate with an USB flashdrive the filesystem, but everything seems to be properly in place and installed. I need advice how to revive the system after this. Thanks in advance, Oliver From owner-freebsd-current@freebsd.org Mon Apr 10 13:14:43 2017 Return-Path: Delivered-To: freebsd-current@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 B994BD37714 for ; Mon, 10 Apr 2017 13:14:43 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 926CBF25 for ; Mon, 10 Apr 2017 13:14:43 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OO700I003DGBU00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 10 Apr 2017 13:14:27 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1491830067; bh=XPvnZg0x5PTl21HkW4ovb9HUWXdnA8TkG9v5rJvwmsQ=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=qYVZe8frHv8YQ+kGTDdn+AtbsA/Ndel2rGmYqNKLZqQX33gi8K7NxWOoPmOX/hSfl LZoVtZvoqHH3BTz6PFMaFkcWwHC9xSnWdFEuPnOboganJyaYDyYo9wJORKdCCtrcql dgTbIrDd4x3xlMXL0jbak9ZCPEyXxmTeDIqpOFLb3GF26CeWflXP4knXRpcY0Tatqw E1V6L8ChFUMMW9JAi3L930y3Zx2LIq0ESam5gifKMl1rFzgJr1BT79j6vqnox2mhhq JgsJ1uYMzX2rJsNeXqcMdeW2YgO5HY1RJUv7uf53E47BBmFUjFsQ2SR362L23VnijL 4AI7VjRhOwD2w== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OO70016C3FYVV10@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 10 Apr 2017 13:14:24 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-10_11:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1704100110 From: Toomas Soome 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: r316677:EFI boot failure: Can't load kernel Date: Mon, 10 Apr 2017 16:14:21 +0300 References: <20170410145846.73d4350a@hermann> To: FreeBSD CURRENT In-reply-to: <20170410145846.73d4350a@hermann> Message-id: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 13:14:43 -0000 > On 10. apr 2017, at 15:58, Hartmann, O. = wrote: >=20 > After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740 > XEON) reject to boot properly. They die immediately after > loading /boot/loader.efi and jump into loader prompt: >=20 > [...] > \ > can't load 'kernel' >=20 >=20 > I had to investigate with an USB flashdrive the filesystem, but > everything seems to be properly in place and installed. >=20 > I need advice how to revive the system after this. >=20 hm, this implies that r316676 was ok? If so, the only logical conclusion = is that it hast to do about the kernel size and if there is enough space = in UEFI memory to place the kernel. You can fetch the current memory map from loader OK prompt with memmap = command, I hope this will help to identify the issue. rgds, toomas From owner-freebsd-current@freebsd.org Mon Apr 10 13:50:15 2017 Return-Path: Delivered-To: freebsd-current@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 CE5DCD36346 for ; Mon, 10 Apr 2017 13:50:15 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 91B38A02 for ; Mon, 10 Apr 2017 13:50:15 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x243.google.com with SMTP id w130so5466659iow.0 for ; Mon, 10 Apr 2017 06:50:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=6D6ibcJjI+uGw+NXu3TVsZkA8LeuszLbrMFu+AeRQmY=; b=P7Wkto7zNCPzS++NNENCbgAybNkBrbMKeScB32fs/cQ1kcTu5NkVQps/0MbVs/9Nsn YMn1bM9s6n/IpOKCmEBKU/aeR6qBqC0Q8bybHpGONYgqnklRb+5VTviPCA8MsS0r3gii f8GMZ/C0ZcFcS3ZRj9I/Bt9K1BN+/zpxLpU7Efh2B6Yi0xUpuX4nZkAN0TK51Xkyc2Et cZtnu/TlUk1kwGo9cYTSEg6z4sdnXRp2S0yRv914ZRjGd1e8HOqjGWW0ewXs9/HM0fZ1 3pIJderIwnWVBPJP/C9I7dIEENPKDKm9Qvl6W/sOUUfs5PYQ70SXdtJiIpvAgk5OH1Tc DLkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=6D6ibcJjI+uGw+NXu3TVsZkA8LeuszLbrMFu+AeRQmY=; b=LAeOEJRaiKT+GebD2T4YyG795Fx0fyibwDKHqLfa2bARBbJxYZv4QYwEbeh51sosly 19KkyOxlV0NDwpMllyhwvIfzAuTL4g0zDR+QpUnz4vSUWIATqQvPzuyPf43gSxbhQCMj 3Oh9g9wf7tQ73SZlynsafzvg4rmDsUSoaQZAqc434eXs55m87M8YiQkKOHsYL/5Cp2/S Ldrz5/l5ZsnFoiF9bZa4wMz9JC1611wESyorBPRGrnsdIm5/+zExNcw+pyO2+5fQhd5M P/XrpOvyLbOBU96QowjPQg3ftXquh9RFzjfpULJSzrliEc2XA+tcunFfp/W8MKHZS6B4 o4jg== X-Gm-Message-State: AN3rC/5KKjqP547pwtEmRBRGI8jf//YcJ54fNjaiZZpeCfYFwetIlUII 1rPe4YBduYxD6w== X-Received: by 10.36.85.148 with SMTP id e142mr12391548itb.106.1491832215003; Mon, 10 Apr 2017 06:50:15 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-88-57.neo.res.rr.com. [74.141.88.57]) by smtp.googlemail.com with ESMTPSA id p70sm4934150itg.0.2017.04.10.06.50.13 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 10 Apr 2017 06:50:14 -0700 (PDT) Message-ID: <58EB8D98.5050904@gmail.com> Date: Mon, 10 Apr 2017 09:50:16 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: peter.blok@bsd4all.org CC: Pavel Timofeev , "Bjoern A. Zeeb" , freebsd-current Subject: Re: VNET branch destiny References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> In-Reply-To: <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 13:50:15 -0000 peter.blok@bsd4all.org wrote: > There have been issues with pf if I recall correctly. I currently have issues with stable, pf and vnet. There is an issue with pf table entries when an interface is moved to a different vnet. > > Does anyone no if there is a specific fix for this that hasn’t been ported to stable? I haven’t had the time to test this on current. > > Peter PF was fixed in 11.0 to not panic when run on a host that has vimage compiled into the kernel. On 11.0 you can configure pf to run in a vnet jail but it really does not enforce any firewall rules because pf needs access to the kernel which jail(8) is blocking by design. As far as I know this is a show shopper that can not be fixed without a pf rewrite changing the way it works internally. This PR gives all the details https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212013 From owner-freebsd-current@freebsd.org Mon Apr 10 14:36:37 2017 Return-Path: Delivered-To: freebsd-current@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 C7D5FD37204 for ; Mon, 10 Apr 2017 14:36:37 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq1.tb.mail.iss.as9143.net (smtpq1.tb.mail.iss.as9143.net [212.54.42.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76BFA7C1 for ; Mon, 10 Apr 2017 14:36:36 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.42.133] (helo=smtp9.tb.mail.iss.as9143.net) by smtpq1.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cxaAS-00086g-TZ; Mon, 10 Apr 2017 16:19:44 +0200 Received: from 5ed15678.cm-7-2b.dynamic.ziggo.nl ([94.209.86.120] helo=wan0.bsd4all.org) by smtp9.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cxaAS-0003NN-Pm; Mon, 10 Apr 2017 16:19:44 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id 27E117294; Mon, 10 Apr 2017 16:19:43 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CkUrj3ENUN_j; Mon, 10 Apr 2017 16:19:38 +0200 (CEST) Received: from [192.168.1.64] (mm [192.168.1.64]) by wan0.bsd4all.org (Postfix) with ESMTPSA id 087A2728A; Mon, 10 Apr 2017 16:19:37 +0200 (CEST) From: peter.blok@bsd4all.org Message-Id: <75BD8407-83AC-4383-912A-70083CED3FFD@bsd4all.org> Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: VNET branch destiny Date: Mon, 10 Apr 2017 16:19:37 +0200 In-Reply-To: <58EB8D98.5050904@gmail.com> Cc: Pavel Timofeev , "Bjoern A. Zeeb" , freebsd-current To: Ernie Luzar References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> <58EB8D98.5050904@gmail.com> X-Mailer: Apple Mail (2.3273) X-SourceIP: 94.209.86.120 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=DaNnkrlW c=1 sm=1 tr=0 a=IkzOOneQUJP1+bAPekPvBg==:17 a=AzvcPWV-tVgA:10 a=pGLkceISAAAA:8 a=6Q3WNqvRAAAA:8 a=6I5d2MoRAAAA:8 a=EEZ-tilfT3c-UgNY3FoA:9 a=IG4rVTXlw-NOpdIq:21 a=dffPz0lcM9dU9V5V:21 a=QEXdDO2ut3YA:10 a=CTX6184NhUg2i1LZ3OMA:9 a=jot15N5koVxdeT_G:21 a=Og90m685kHM33Zxz:21 a=8LL_voLXoUa5cjVQ:21 a=_W_S_7VecoQA:10 a=6kGIvZw6iX1k4Y-7sg4_:22 a=I8PBwKCn76L9oNdl0isp:22 a=IjZwj45LgO3ly-622nXo:22 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 14:36:37 -0000 Well, in my case it panic=E2=80=99ed on 11-stable. I=E2=80=99m only = using pf on the host, not in the jail. I=E2=80=99m using Devin Teske=E2=80= =99s jng to create a netgraph bridge. It is my intention to use the = netgrpah bridge with bhyve as well. The panic (one-time) happened in pfioctl when I refreshed the rules. I = suspect the problem is related to the following message when I stop the = jail. kernel: Freed UMA keg (pf table entries) was not empty (32 items). Lost = -57 pages of memory. Current does not display the UMA message. I=E2=80=99m still narrowing = down what happens with the pf table entries. My suspicion is that the = netgraph bridge which creates a ng_ether device which is handed over to = the jail vnet, is causing this. The panic happened on LIST_REMOVE in keg_fetch_slab static uma_slab_t keg_fetch_slab(uma_keg_t keg, uma_zone_t zone, int flags) { uma_slab_t slab; int reserve; mtx_assert(&keg->uk_lock, MA_OWNED); slab =3D NULL; reserve =3D 0; if ((flags & M_USE_RESERVE) =3D=3D 0) reserve =3D keg->uk_reserve; for (;;) { /* * Find a slab with some space. Prefer slabs that are = partially * used over those that are totally full. This helps to = reduce * fragmentation. */ if (keg->uk_free > reserve) { if (!LIST_EMPTY(&keg->uk_part_slab)) { slab =3D LIST_FIRST(&keg->uk_part_slab); } else { slab =3D LIST_FIRST(&keg->uk_free_slab); LIST_REMOVE(slab, us_link); LIST_INSERT_HEAD(&keg->uk_part_slab, = slab, us_link); } MPASS(slab->us_keg =3D=3D keg); return (slab); } KDB: stack backtrace: #0 0xffffffff805df0e7 at kdb_backtrace+0x67 #1 0xffffffff8059d176 at vpanic+0x186 #2 0xffffffff8059cfe3 at panic+0x43 #3 0xffffffff808ebaa2 at trap_fatal+0x322 #4 0xffffffff808ebaf9 at trap_pfault+0x49 #5 0xffffffff808eb336 at trap+0x286 #6 0xffffffff808d1441 at calltrap+0x8 #7 0xffffffff808a871e at zone_fetch_slab+0x6e #8 0xffffffff808a87cd at zone_import+0x4d #9 0xffffffff808a4fc9 at uma_zalloc_arg+0x529 #10 0xffffffff80803214 at pfr_ina_define+0x584 #11 0xffffffff807f0734 at pfioctl+0x3364 #12 0xffffffff80469288 at devfs_ioctl_f+0x128 #13 0xffffffff805fa925 at kern_ioctl+0x255 #14 0xffffffff805fa65f at sys_ioctl+0x16f #15 0xffffffff808ec604 at amd64_syscall+0x6c4 #16 0xffffffff808d172b at Xfast_syscall+0xfb The panic is so far not reproducible. > On 10 Apr 2017, at 15:50, Ernie Luzar wrote: >=20 > peter.blok@bsd4all.org wrote: >> There have been issues with pf if I recall correctly. I currently = have issues with stable, pf and vnet. There is an issue with pf table = entries when an interface is moved to a different vnet. >> Does anyone no if there is a specific fix for this that hasn=E2=80=99t = been ported to stable? I haven=E2=80=99t had the time to test this on = current. >> Peter >=20 > PF was fixed in 11.0 to not panic when run on a host that has vimage = compiled into the kernel. On 11.0 you can configure pf to run in a vnet = jail but it really does not enforce any firewall rules because pf needs = access to the kernel which jail(8) is blocking by design. As far as I = know this is a show shopper that can not be fixed without a pf rewrite = changing the way it works internally. >=20 > This PR gives all the details > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212013 >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Mon Apr 10 14:39:06 2017 Return-Path: Delivered-To: freebsd-current@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 507E5D372FC for ; Mon, 10 Apr 2017 14:39:06 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::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 15E3B960 for ; Mon, 10 Apr 2017 14:39:06 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x22c.google.com with SMTP id l7so97377790ioe.3 for ; Mon, 10 Apr 2017 07:39:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=8qPHJPeXDOFoFD9lFdPkd+IvsbXIb2fifUCQe8ydIVQ=; b=EFf+7GjyMAbOLwaQjjNav1rQKrE7YOSMjfiPRYx1LamM0Q3Jy+yp+TUnjVGm4WQvTx asfSPwI28zLbPWP8q1hDVjl0a89sYD6DK6Xskjx9qu2MZ467LeyG88KnYQSlJ3u92wmA 1uBVp0lbt18n+bxX7S7uA0pTwlLcw0fe12sMjAbra/6Ld/pMh6oZtkmKDaKqZTUprPXD dj3QshLwm1zvRnPjhLtMwl2nq2T6VgScFJdt8yUacEuFK9Oem2NzIQ+qONjwd0P/SqtU ZmwLjQ1g1/3JjvAbnJ9YQMchbuZrAbmtPrVs6K7XdWwBg0b0uF9KBkkqFKKKoH6atoMF HAXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=8qPHJPeXDOFoFD9lFdPkd+IvsbXIb2fifUCQe8ydIVQ=; b=P3b5/Bfk2c5jZb5tvw0GYBxKZL5jdNI7MZCMiVjF1wMF++zz8dQDrVQqu/thxVJh9/ xkhEY+KyiBkCZ5diMxL8gDNhHQ3r9OJ0xlInxPN7SbICHGpo2KcBNz5lrQBsICHIpoSM oMxelMOo7VJo0LRWvnLZPZj2bm9fsFz51tW55wFI/LlzLhlbTQ4VWOioWUuA1upJXu28 WYoc9QeeRRVondmDegE6U3YtkHJyrNkgEoapXd6U2qYnyVqHPDPkKjOJ6VddfUAe3Vty 6gSwL6xbg7o+XrCDZkIAt6yJqJ4tpR4LxPRYUxiYNbN1QrCkqJU7mTR38Iqjm3VidSt6 hHfQ== X-Gm-Message-State: AN3rC/4Jpm5G7MYhukP4SdAtsSzosVgw9MV09GkyVPVclwskpJdj6reA 4n7kMzvAGMdN5ja5 X-Received: by 10.36.105.132 with SMTP id e126mr12491992itc.61.1491835142798; Mon, 10 Apr 2017 07:39:02 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-88-57.neo.res.rr.com. [74.141.88.57]) by smtp.googlemail.com with ESMTPSA id p6sm6460781iof.12.2017.04.10.07.39.01 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 10 Apr 2017 07:39:02 -0700 (PDT) Message-ID: <58EB990A.50502@gmail.com> Date: Mon, 10 Apr 2017 10:39:06 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: freebsd-current CC: "Bjoern A. Zeeb" Subject: Re: VNET branch destiny References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> In-Reply-To: <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 14:39:06 -0000 To the VNET (VIMAGE) update project team members Release 11.0 has some out standing VNET (VIMAGE) PR's that need addressing. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212013 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212031 I believe 212000 and 212013 would require an rewrite replacing the kernel method they use to the user land method as used by ipfw. At the very lease it should be documented somewhere that pf & ipfilter do not work in an vnet/vimage jail. PR 212031 looks like a vimage/vnet problem to me. To the members of current, This bug report is not a jail(8) problem but a kernel problem that needs to be addressed. Could someone please look into fixing it. I effects all jail(8) users. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210049 There is also the matter of removing the depreciated rc.conf jail definition method from the rc.d scripts making the jail.conf method the default. This is long over due and maybe something over looked in the 11.0 release. Thank you for your attention. From owner-freebsd-current@freebsd.org Mon Apr 10 15:21:14 2017 Return-Path: Delivered-To: freebsd-current@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 B934DD376E6 for ; Mon, 10 Apr 2017 15:21:14 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::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 7B601243 for ; Mon, 10 Apr 2017 15:21:14 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x22f.google.com with SMTP id a103so34849309ioj.1 for ; Mon, 10 Apr 2017 08:21:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=PqJnwScdyh1KM7PCFiG/HazCoCtGSwK+XO/o4A/pUQc=; b=CCSdb0/vnCpl27QYhXYtuwr4HN5NO87smBm2Hx3GwelgibMsmF6X1jjx4MEfgz89Lv mszhXsAhwMv1jEYu3Cpo/apuqDEi2oARhJ7ajrwQbnm936OAWuMGCnFvtlOBKSRwyPfA J6nAAWDAyDQaG3npq3h0VqD8yvddjkkG6PMyPPE2OAwFvnnfRO8sJ4cTArTY8+7SY+b/ JHHA99WLgu33LJnSbhTV1UaSc/CSIaDYve4fYk4TUgXqMUZBvkCj2MLey40gffmfVIF3 cPMYQ0RONCizAw/FkNHDSfXeH13q5TKk4q1P3K+zmtvJXprsTBGB7/LSTzBFTqxKAeJo Frjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=PqJnwScdyh1KM7PCFiG/HazCoCtGSwK+XO/o4A/pUQc=; b=WD6d+pvOTdpILEZYK5/zOHJLCtsAMzi6O/UUuWECX7bYoKeJc8YMSx1k3meec94QJr 84v9wNZ1M1KpNcQpoy5PPsLxHFSD5X5LMkVUs0k7gKzPEliCdgQiMJHLeTT69hNUiUqu wzD4dCq4ywuiMHwhadtvCZNZmeb2RkXbjVwFadyieDUtV3syslgPWz8/M/bhPIo805yY 3rM/3Ruorqwb4ualgWNQ9oX+ooY/Z5Mr7jFze3PQOffWWnLaVUhb/zxpFeGFd2A2NbPB TusTJQapWeOB6jwTR03mU/e90KIGg+Wo8DXfFKLI5SloM3uLaP5zqLtejgDHfnPyA+BL Bang== X-Gm-Message-State: AN3rC/6CcdAwSr3zU/BHR5YEHn5kJG5O0owgKdg/eVR3L37H8GIoCAesxCTNls4SdzycbA== X-Received: by 10.36.218.5 with SMTP id z5mr12061919itg.79.1491837672375; Mon, 10 Apr 2017 08:21:12 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-88-57.neo.res.rr.com. [74.141.88.57]) by smtp.googlemail.com with ESMTPSA id g204sm3679694ita.31.2017.04.10.08.21.11 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 10 Apr 2017 08:21:11 -0700 (PDT) Message-ID: <58EBA2ED.9000100@gmail.com> Date: Mon, 10 Apr 2017 11:21:17 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: peter.blok@bsd4all.org CC: Pavel Timofeev , "Bjoern A. Zeeb" , freebsd-current Subject: Re: VNET branch destiny References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> <58EB8D98.5050904@gmail.com> <75BD8407-83AC-4383-912A-70083CED3FFD@bsd4all.org> In-Reply-To: <75BD8407-83AC-4383-912A-70083CED3FFD@bsd4all.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 15:21:14 -0000 peter.blok@bsd4all.org wrote: > Well, in my case it panic’ed on 11-stable. I’m only using pf on the > host, not in the jail. I’m using Devin Teske’s jng to create a netgraph > bridge. It is my intention to use the netgrpah bridge with bhyve as well. > > The panic (one-time) happened in pfioctl when I refreshed the rules. I > suspect the problem is related to the following message when I stop the > jail. > > kernel: Freed UMA keg (pf table entries) was not empty (32 items). Lost > -57 pages of memory. > > Current does not display the UMA message. I’m still narrowing down what > happens with the pf table entries. My suspicion is that the netgraph > bridge which creates a ng_ether device which is handed over to the > jail vnet, is causing this. > > > The panic happened on LIST_REMOVE in keg_fetch_slab > > static uma_slab_t > keg_fetch_slab(uma_keg_t keg, uma_zone_t zone, int flags) > { > uma_slab_t slab; > int reserve; > > mtx_assert(&keg->uk_lock, MA_OWNED); > slab = NULL; > reserve = 0; > if ((flags & M_USE_RESERVE) == 0) > reserve = keg->uk_reserve; > > for (;;) { > /* > * Find a slab with some space. Prefer slabs that are > partially > * used over those that are totally full. This helps to > reduce > * fragmentation. > */ > if (keg->uk_free > reserve) { > if (!LIST_EMPTY(&keg->uk_part_slab)) { > slab = LIST_FIRST(&keg->uk_part_slab); > } else { > slab = LIST_FIRST(&keg->uk_free_slab); > *LIST_REMOVE(slab, us_link);* > LIST_INSERT_HEAD(&keg->uk_part_slab, slab, > us_link); > } > MPASS(slab->us_keg == keg); > return (slab); > } > > KDB: stack backtrace: > #0 0xffffffff805df0e7 at kdb_backtrace+0x67 > #1 0xffffffff8059d176 at vpanic+0x186 > #2 0xffffffff8059cfe3 at panic+0x43 > #3 0xffffffff808ebaa2 at trap_fatal+0x322 > #4 0xffffffff808ebaf9 at trap_pfault+0x49 > #5 0xffffffff808eb336 at trap+0x286 > #6 0xffffffff808d1441 at calltrap+0x8 > #7 0xffffffff808a871e at zone_fetch_slab+0x6e > #8 0xffffffff808a87cd at zone_import+0x4d > #9 0xffffffff808a4fc9 at uma_zalloc_arg+0x529 > #10 0xffffffff80803214 at pfr_ina_define+0x584 > #11 0xffffffff807f0734 at pfioctl+0x3364 > #12 0xffffffff80469288 at devfs_ioctl_f+0x128 > #13 0xffffffff805fa925 at kern_ioctl+0x255 > #14 0xffffffff805fa65f at sys_ioctl+0x16f > #15 0xffffffff808ec604 at amd64_syscall+0x6c4 > #16 0xffffffff808d172b at Xfast_syscall+0xfb > > The panic is so far not reproducible. > > >> On 10 Apr 2017, at 15:50, Ernie Luzar > > wrote: >> >> peter.blok@bsd4all.org wrote: >>> There have been issues with pf if I recall correctly. I currently >>> have issues with stable, pf and vnet. There is an issue with pf table >>> entries when an interface is moved to a different vnet. >>> Does anyone no if there is a specific fix for this that hasn’t been >>> ported to stable? I haven’t had the time to test this on current. >>> Peter >> >> PF was fixed in 11.0 to not panic when run on a host that has vimage >> compiled into the kernel. On 11.0 you can configure pf to run in a >> vnet jail but it really does not enforce any firewall rules because pf >> needs access to the kernel which jail(8) is blocking by design. As far >> as I know this is a show shopper that can not be fixed without a pf >> rewrite changing the way it works internally. >> >> This PR gives all the details >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212013 >> >> I also tested using Devin Teske’s jng to create a netgraph bridge on RELEASE 10.0 and it worked. But when I tried the same configuration on RELEASE 11.0 it no longer worked. I strongly suggest you verify pf is functional in your vnet jail before you go chasing a dump which I suspect is totally misleading. Setup a simple vnet pf rule set being run in the vnet jail that allows everything out except port 43 which the "whois" command uses and then issue the whois command from the vent jail console. If the vnet pf port 43 rule is really blocking port 43 it will cause the whois command to not return any results. If the whois command returns results this indicates that even thought you have all the correct settings to run pf in your vnet jail and have received no error messages about it, pf is not really enforcing any rules. (IE; not working) I am assuming that the host has no firewall at all or is at least allowing outbound port 43 packets out. From owner-freebsd-current@freebsd.org Mon Apr 10 18:14:40 2017 Return-Path: Delivered-To: freebsd-current@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 4E870D37190 for ; Mon, 10 Apr 2017 18:14:40 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2E3AEC16 for ; Mon, 10 Apr 2017 18:14:40 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2DA0AD3718F; Mon, 10 Apr 2017 18:14:40 +0000 (UTC) Delivered-To: current@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 2D488D3718E for ; Mon, 10 Apr 2017 18:14:40 +0000 (UTC) (envelope-from bdrewery@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 012D3C15; Mon, 10 Apr 2017 18:14:40 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id EDFDA36C9; Mon, 10 Apr 2017 18:14:38 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 99A6559A9; Mon, 10 Apr 2017 18:14:37 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id KQ6TSMXT-bCO; Mon, 10 Apr 2017 18:14:34 +0000 (UTC) Subject: Re: buildkernel broken for META_MODE DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 2DA5059A3 To: "Ngie Cooper (yaneurabeya)" References: Cc: FreeBSD Current From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: Date: Mon, 10 Apr 2017 11:14:15 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gFat4U58T4mhiKkQPI6oHVIDvF45a1tR7" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 18:14:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gFat4U58T4mhiKkQPI6oHVIDvF45a1tR7 Content-Type: multipart/mixed; boundary="7x6LAB7EeaDmiWFvTiCe7fK97b9R6PdlV"; protected-headers="v1" From: Bryan Drewery To: "Ngie Cooper (yaneurabeya)" Cc: FreeBSD Current Message-ID: Subject: Re: buildkernel broken for META_MODE References: In-Reply-To: --7x6LAB7EeaDmiWFvTiCe7fK97b9R6PdlV Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 4/7/2017 12:13 PM, Ngie Cooper (yaneurabeya) wrote: > Hi, > I ran into this error when trying to run a meta mode build (for the fi= rst time). It might be related to the recent assym* ordering changes. > Thanks! > -Ngie >=20 > $ cat /etc/src-env.conf > WITH_AUTO_OBJ=3D yes > WITH_META_MODE=3D yes > UPDATE_DEPENDFILE=3D yes > $ pwd > /usr/src > $ svnversion > 316603M > $ svn st | grep -v \? > M usr.bin/grep/tests/Makefile > $ env SRCCONF=3D/dev/null NO_FILEMON=3D1 script ~/bk.ts make buildkerne= l -j3 > Script started on Fri Apr 7 11:52:38 2017 > Command: time make buildkernel -j3 > --- buildkernel --- > make[1]: "/usr/src/Makefile.inc1" line 146: SYSTEM_COMPILER: Determined= that CC=3Dcc matches the source tree. Not bootstrapping a cross-compile= r. > --- buildkernel --- > -------------------------------------------------------------- >>>> Kernel build for GENERIC started on Fri Apr 7 11:52:39 PDT 2017 > -------------------------------------------------------------- > =3D=3D=3D> GENERIC > mkdir -p /usr/obj/usr/src/sys > -------------------------------------------------------------- >>>> stage 1: configuring the kernel > -------------------------------------------------------------- > ... > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/acpi_quirks.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/feeder_eq_gen.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/feeder_rate_gen.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/snd_fxdiv_gen.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/miidevs.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/pccarddevs.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/teken_state.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/usbdevs.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/vnode_if.h > Building /usr/obj/usr/obj/usr/src/sys/GENERIC/ia32_genassym.o > --- ia32_genassym.o --- > :1:10: fatal error: 'opt_global.h' file not found > #include "opt_global.h" > ^~~~~~~~~~~~~~ > 1 error generated. > *** [ia32_genassym.o] Error code 1 >=20 > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > .ERROR_TARGET=3D'ia32_genassym.o' > .ERROR_META_FILE=3D'/usr/obj/usr/obj/usr/src/sys/GENERIC/ia32_genassym.= o.meta' >=20 It was previously reported here too https://lists.freebsd.org/pipermail/freebsd-current/2016-June/061946.html= =2E It's a race. I had forgotten about it but will look at it again. --=20 Regards, Bryan Drewery --7x6LAB7EeaDmiWFvTiCe7fK97b9R6PdlV-- --gFat4U58T4mhiKkQPI6oHVIDvF45a1tR7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJY68t6AAoJEDXXcbtuRpfPmYcIAJyj7G4Abbu0EY52CRDRlyZc 2eIalQbpF4hjSFUj+r0Qcq307Gfmc2ytu66TOL0cL5T2SEErKNyRVGpi+qHpkn7D TyrFk4YPny3663BwmDcUH8+r6W6AzKSNCez7YV6ZXEQyLQrPsDMmRJjp+AVqbXMW lAV+iN0Jh56VUn5g5r8xkkpTb9y3cB9xBdfBaBpgO79h5HQiaLH8Rui87LYMUGLP G0LUvFq9V8jqywVxcsXAZOsqONF3jLnrqZdchJYrX2Py4oB+HEI14UKxSy23T4nE sm5x/eaZ32ript1ZZy8XazkoGUOoQFH8zgLr3RlnKghcqOFMJ/aWffDu2VGmQq4= =NxUe -----END PGP SIGNATURE----- --gFat4U58T4mhiKkQPI6oHVIDvF45a1tR7-- From owner-freebsd-current@freebsd.org Mon Apr 10 18:05:01 2017 Return-Path: Delivered-To: freebsd-current@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 1312ED37E30 for ; Mon, 10 Apr 2017 18:05:01 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67548152 for ; Mon, 10 Apr 2017 18:04:59 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.173.121]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M9wrU-1cmfJP1nxY-00B39S; Mon, 10 Apr 2017 20:04:47 +0200 Date: Mon, 10 Apr 2017 20:04:40 +0200 From: "O. Hartmann" To: Toomas Soome Cc: FreeBSD CURRENT Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170410145846.73d4350a@hermann> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/eanPv8Mm9=mL/bx3EaSLN6F"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:0xaIIg1nJITTeL+bZ54DysuReYG8x8zLU9WJRNmSfhW8K2FVTaw i4y2vt3lgc6fypILHga3N61/neGio20zN1qWaN45si6mwzzh6OzCp4fEgI2VTOMkghyXBh7 MOTwk3Vt35bN8/nNlGnnDLzx00fC3Ms6z6r3E8d538gTQxOGhvs1YhqU+dguIoQObZsetTr 5fbn9DK48UIsows3UIshw== X-UI-Out-Filterresults: notjunk:1;V01:K0:i7J7L9wLGyM=:v4XyRsyYCgYitTZMwrK1C2 +NOAkBxt9jejRrccapBGA2Key2/OvryLSt9db1MEdKjP/EJCoWRMi70Sl/GDr4WRSZ2Qk8T1b YYXtVBWrYbtdCdDI6Et1MwGGrWaUs5Vk9YpiZeG+d7VqI61QM8yN0y2QqYCaxGo8d0VKnrt1K w6yHWyLTTYxH1V9RKiiqcDVjToEyr7B+hz174tJFr8LEfsZhYSvT1QvkjslOIrgt+aT4uU0zU h3hWihkl1oWSMKd/WvQ2RUZ5RpB3gF07jaYS4dwbudTre7ALy0kNBwcSK7ZPmy7VpDfwVd+IJ JUjj4kPijPIU5UBq+oo+uTmVkQ1tt0UVfdSb8gX1UwxkT3rZyZDUW+1p9M/uOjsaGvG+jN5MD 78ESPvcDj12kvv0Fwj8Ns2FSIHcBeVDbnMkkxF9gYKPJ1QkJ5umuwE2hrlOgPGPq6WLlL8QmW ozuQUnJSmcjobVgp+7LzP5Vzd+N1lluZUSQNSdBRVqPjaKJa/Ae6/6dGjtP7joo67QwpcoECW dEsVKdsFPg9GcmG374IT3F62gNjNAO/tv+yqPSLe3TAk7pKGWZlvgxpcb9BSFSdc7tZbYj5KD YK4Lod9OFyzfBtL+V8e5XMuy6XFbMfx2oZG8b07PE8tVl2FeK68aIodWi4hm55rZZU6mWFQE7 GReGnP9hXsO1FpwAJRAMyMPW/xmHfSslkaC3MgDOBp1ACPVlEYrQNWMLFZwDn0JyAgEqBGNZY Pf/yPIewudbz9DctX2rQI9mfOfpqcLfVyBnq9nMWSg7RarL94bQXLS+NmDM= X-Mailman-Approved-At: Mon, 10 Apr 2017 18:34:06 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 18:05:01 -0000 --Sig_/eanPv8Mm9=mL/bx3EaSLN6F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 10 Apr 2017 16:14:21 +0300 Toomas Soome schrieb: > > On 10. apr 2017, at 15:58, Hartmann, O. wrote: > >=20 > > After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740 > > XEON) reject to boot properly. They die immediately after > > loading /boot/loader.efi and jump into loader prompt: > >=20 > > [...] > > \ > > can't load 'kernel' > >=20 > >=20 > > I had to investigate with an USB flashdrive the filesystem, but > > everything seems to be properly in place and installed. > >=20 > > I need advice how to revive the system after this. > > =20 >=20 >=20 > hm, this implies that r316676 was ok? If so, the only logical conclusion = is that it > hast to do about the kernel size and if there is enough space in UEFI mem= ory to place > the kernel. >=20 > You can fetch the current memory map from loader OK prompt with memmap co= mmand, I hope > this will help to identify the issue. >=20 > rgds, > toomas And? Regrads, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/eanPv8Mm9=mL/bx3EaSLN6F Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLQEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWOvJOAAKCRDS528fyFhY lEGwAfiu5W/+RCIi794WSjdaX3eX1ExjlaNrVrDtD5t3Z/Izq1s1W/t7gQpO/Fvd //V7SHYocDYlYjm1TINyi2kIiDgB/3zXt69Qgjxmv8AGUaPDTy4g8PLZTZy2JBVH gIKKBEMmR+SKhB5FTqSf4zYF5t1MazqtRdtg+0IOQOyPBMXuPvU= =GJ08 -----END PGP SIGNATURE----- --Sig_/eanPv8Mm9=mL/bx3EaSLN6F-- From owner-freebsd-current@freebsd.org Mon Apr 10 18:55:33 2017 Return-Path: Delivered-To: freebsd-current@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 A9BACD37DF6 for ; Mon, 10 Apr 2017 18:55:33 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 74E4AA34 for ; Mon, 10 Apr 2017 18:55:32 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cxeTD-0004NY-KO for freebsd-current@freebsd.org; Mon, 10 Apr 2017 20:55:24 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-current@freebsd.org Subject: Re: CURRENT: Compile time of ports has increased significantly since LLVM 4.0 References: <20170410141003.7d422d86@freyja.zeit4.iv.bundesimmobilien.de> Date: Mon, 10 Apr 2017 20:55:22 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20170410141003.7d422d86@freyja.zeit4.iv.bundesimmobilien.de> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 4c3c8b3d32e7d0cfaf2d58264fc1daa3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 18:55:33 -0000 There is a similar thread with subject: 'how to mark llvm* forbidden?' going on right now on this list. Regards, Ronald. On Mon, 10 Apr 2017 14:10:03 +0200, O. Hartmann wrote: > We build pretty often world and ports. > > With poudriere as port building backend, The daily/weekly builds have > now grown > in compile time significantly since approx. the introduction of LLVM 4.0 > into > FreeBSD. > > The build box is a LGA1150 IvyBridge XEON system with 3,4 GHz and 16 GB > RAM. > The configuration of poudriere (most recent ports tree version, as well > as most > recent CURRENT host and most recent CURRENT jail: FreeBSD 12.0-CURRENT > #4 > r316067: Tue Mar 28 06:26:18 CEST 2017 amd64). > > Within the past 4 - 6 months, wekbkit-gtk2 and webkit-gtk3 took ~ 1h 90 > min, > or, when started together, ~ 2h 40 min. Now they take each(!, even > separately > started and indivuidually conmpiled without concurrent jobs) more than 3 > hours. > > The same with /editors/libreoffice. On this bos it took 2h 40 min to > compile > libreoffice 5.2.X up to 5.2.6, now it graces or is beyond 4 hours! > > This observation is taken from a time span of 5 - 6 months and even with > worst > case scenarios like parallel start of webkit[2]-gtk[23] in parallel. > > So, does someone also diagnose this compile time stretching? I also see > this > while regularily building ports via "make" in /usr/ports. > > > Thanks in advance, > > Oliver > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Mon Apr 10 18:59:08 2017 Return-Path: Delivered-To: freebsd-current@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 083EFD37F61 for ; Mon, 10 Apr 2017 18:59:08 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D2183C70 for ; Mon, 10 Apr 2017 18:59:07 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OO700100HMWON00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 10 Apr 2017 18:59:06 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1491850746; bh=BUitX0oQmNc5T4tvGrwwgo9h1lOXwhvIKGwWrkYIKHE=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=FudFH6dkwwq77RLa2nRzjjnosPZhfitPEpUgv0BK4nntB+DN6pUZVSpuY4Na0WQNd YFB27db7dv3GHumqxkgtIyKrRc/Zn9Q4Efm4lRxy/FZzKgENqiVRH5mhEdNyoni6xj go554K+0ehjd5njW8E/2W2XejO3UGSJArITgydcSxNr2xC62gXV5CO0YM9kJLPIXLt tt4DhsDomum7uoQqS4b1C7bDeF2es3did4BaQDdAN/EKfW6iCvt/iS5+YJPXNBP4DS 6Qot/0LTxWtpiV3CcgwhQD+U80CtYB/AIVI8N6eqCMA+B00hSdlxtx223roMMDvSy6 HlGkKBiitFZRg== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OO7003DIJEDDR10@st13p35im-asmtp001.me.com>; Mon, 10 Apr 2017 18:59:03 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-10_15:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1704100150 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: r316677:EFI boot failure: Can't load kernel Date: Mon, 10 Apr 2017 21:59:00 +0300 In-reply-to: <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> Cc: FreeBSD CURRENT To: "O. Hartmann" References: <20170410145846.73d4350a@hermann> <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 18:59:08 -0000 > On 10. apr 2017, at 21:04, O. Hartmann = wrote: >=20 > Am Mon, 10 Apr 2017 16:14:21 +0300 > Toomas Soome schrieb: >=20 >>> On 10. apr 2017, at 15:58, Hartmann, O. = wrote: >>>=20 >>> After today's update to r316677, some UEFI boxes (Fujitsu Celsius = M740 >>> XEON) reject to boot properly. They die immediately after >>> loading /boot/loader.efi and jump into loader prompt: >>>=20 >>> [...] >>> \ >>> can't load 'kernel' >>>=20 >>>=20 >>> I had to investigate with an USB flashdrive the filesystem, but >>> everything seems to be properly in place and installed. >>>=20 >>> I need advice how to revive the system after this. >>>=20 >>=20 >>=20 >> hm, this implies that r316676 was ok? If so, the only logical = conclusion is that it >> hast to do about the kernel size and if there is enough space in UEFI = memory to place >> the kernel. >>=20 >> You can fetch the current memory map from loader OK prompt with = memmap command, I hope >> this will help to identify the issue. >>=20 >> rgds, >> toomas >=20 >=20 > And? >=20 > Regrads, >=20 > oh >=20 Well, the memory needed is starting from the: #define KERNEL_PHYSICAL_BASE (2*1024*1024) and it should be large enough for kernel. But it feels a bit like = barking under the random tree; the problem is that the error is not = telling us anything why it did happen:( This message you get is coming from sys/boot/common/boot.c, as part of = the autoload sequence; did you try to load kernel manually with load = command? also if you have old kernel around, does old kernel get loaded? rgds, toomas From owner-freebsd-current@freebsd.org Mon Apr 10 19:04:28 2017 Return-Path: Delivered-To: freebsd-current@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 CCD2FD3767C for ; Mon, 10 Apr 2017 19:04:28 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DDE425E for ; Mon, 10 Apr 2017 19:04:27 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.173.121]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MJSQ7-1cudOq0QRP-0034s7; Mon, 10 Apr 2017 21:04:11 +0200 Date: Mon, 10 Apr 2017 21:04:04 +0200 From: "O. Hartmann" To: Toomas Soome Cc: FreeBSD CURRENT Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170410145846.73d4350a@hermann> <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/wi.qSKhre3gvHa24St8px2="; protocol="application/pgp-signature" X-Provags-ID: V03:K0:gaAURaB9h0SwvlvJN0QwTZfSMAzY3AXY2MOU0TEYWELXP+CFA+X 9Wq+5ihT29eL8H+O0LsgfUgAS/inE82WDBCQMwbmXKOrnMh92PqoHQETgLmqquB7/m9WBG4 aBtDrgILx2W0XHJwf1l5k4aqHVSzYhQcCn0YOIPiVh8w7vxCyivV0UGsU7RdTe/vWb6fCWG uZE2RV2tmf79eJSXEypzQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:PNwyL7JKRAE=:Opaqti6o3fIuL5D1CV+k0D /p7yGdFdj8nohW9RKqjNHuZXGUYKVFXGI8eTXQWTZUOX2tsQnQjojfyVDIEXD3wnlYdo8nL7q YnPuqB/zs6uzEm2Z74FFAK8nmbKk5l8uxrEx342xJJoqDJL1Dcv/xuu0SK9jtxkP/nufgwLoV z1au0k4En/a93ZtE+OaE5rsSMF8rxkb76cTvRVOfLEln9HKJbmOKyczddLZooNc/Z496pS8J9 cw4vhoQzCQ/aViFiNYBp+U++I0X6+TK99eIujl1r4jr9KRA5PgUXjHujK3uoXjIiJez1qV5jx Cv0doEwWP0YaC3Nuth2owiDaujhguJHL9u2EZ0C6qgv5uVyJty5wbwbQwH7MwTURo1h8DddbS FCiQMmw9MJSLCvCzYjWffaQZCPWY3VoIyUWRPxzBvqtJMq/Fro3/DCbS3rxSivhKjwfCNjiLT /u/WcT4MlUBJOWszPbF8wdBffcPJ9vCfWMRgmTMLiFjCtK+YplQZjnh4Yw9uTwz36fAR5Ed0S Xd2SEEKSjviXdRhu85/6u8VpRk5fzZt95UmtmK6VQV59FZnZaDEGqQMDXHym/f+H0vPPcJ+qC 0MzWauYlHCau5qkdm1D/bBUkidTxD6tMrPml2/6Nr2VzGLXwt6CfATP6EIhyi6ztULGamne7v knOkHlDBP+bpITZzK/UXp/TY5uxRt7Sp64WbkUrwypAEtUFv3+LW3cWlZjVUBWi0UEa2frcNj IOsNEd1Qy6p6vgI85zIuPGh4dGEUPbdjxq1Ej+A/QT8cU5hOW9RXph9job0= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 19:04:28 -0000 --Sig_/wi.qSKhre3gvHa24St8px2= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 10 Apr 2017 21:59:00 +0300 Toomas Soome schrieb: > > On 10. apr 2017, at 21:04, O. Hartmann wrote: > >=20 > > Am Mon, 10 Apr 2017 16:14:21 +0300 > > Toomas Soome schrieb: > > =20 > >>> On 10. apr 2017, at 15:58, Hartmann, O. wrot= e: > >>>=20 > >>> After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740 > >>> XEON) reject to boot properly. They die immediately after > >>> loading /boot/loader.efi and jump into loader prompt: > >>>=20 > >>> [...] > >>> \ > >>> can't load 'kernel' > >>>=20 > >>>=20 > >>> I had to investigate with an USB flashdrive the filesystem, but > >>> everything seems to be properly in place and installed. > >>>=20 > >>> I need advice how to revive the system after this. > >>> =20 > >>=20 > >>=20 > >> hm, this implies that r316676 was ok? If so, the only logical conclusi= on is that it > >> hast to do about the kernel size and if there is enough space in UEFI = memory to place > >> the kernel. > >>=20 > >> You can fetch the current memory map from loader OK prompt with memmap= command, I > >> hope this will help to identify the issue. > >>=20 > >> rgds, > >> toomas =20 > >=20 > >=20 > > And? > >=20 > > Regrads, > >=20 > > oh > > =20 >=20 > Well, the memory needed is starting from the: >=20 > #define KERNEL_PHYSICAL_BASE (2*1024*1024) >=20 > and it should be large enough for kernel. But it feels a bit like barking= under the > random tree; the problem is that the error is not telling us anything why= it did > happen:( >=20 > This message you get is coming from sys/boot/common/boot.c, as part of th= e autoload > sequence; did you try to load kernel manually with load command? also if = you have old > kernel around, does old kernel get loaded? >=20 > rgds, > toomas >=20 >=20 >=20 >=20 I haven't done anything yet, since the accident happened when I left my bur= eau and I desperately tried to examine on the fly what happened. I'll be at the box tomorrow morning and I will check whether I can load the= old kernel manually. I'll report in what happened. Kind regards, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/wi.qSKhre3gvHa24St8px2= Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWOvXJAAKCRDS528fyFhY lPz8Af9KsWdoP1WM0TwHJ0f7f6q6ZuLwDwNMH8mOMguoHymBSbWMfSz4CTKr92gU xLnrrX1PmLdznr1gk88gK22wznS9Af0UI9s9h6KG3MCK53CFT1X8YBvLfMln9+XI EBgLi4RsB4oJTXK38so0BKs0I7mLS0UGLES3TbGQEIkw0tfAhlWg =+WeK -----END PGP SIGNATURE----- --Sig_/wi.qSKhre3gvHa24St8px2=-- From owner-freebsd-current@freebsd.org Mon Apr 10 20:11:02 2017 Return-Path: Delivered-To: freebsd-current@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 AA1AFD38374 for ; Mon, 10 Apr 2017 20:11:02 +0000 (UTC) (envelope-from luzar722@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 6F241E61 for ; Mon, 10 Apr 2017 20:11:02 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id a103so46158852ioj.1 for ; Mon, 10 Apr 2017 13:11:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=Tf/hOXl3ORoXfYG8jIO4ME5jswrs7VUnZz+R5quoloM=; b=l+rWSdKOkB3HLPnpQhmPzmwEkiSOxh7EYAtbA9UcrHpEWPN1LXfCTr0d1YqQ8E2kJ3 8ceVg1t65i/kQR0iC6zYqqMKNSZjT2lnBNQEMRYPyE52PeMnK5K+sP4Hr1qV5WedbvOl MtGAgJHQPylalnhbIVIEreuM6gVT/Le16A9RGmU5NONcTqQ9HNgRq+c6KvRT811CmMeD WKeASqDd0HDKmDxFkXILITNcFM5s93xPrTyZYDIRP4iBovumlhr0s80MTM1jGJKiw5L+ Qt0hb2M7+F+pPmAsnz33IQyLxr6FviOGqvhCOO18mfon0HmK7y6fWX7YZnTMa7fEuIS8 SjiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=Tf/hOXl3ORoXfYG8jIO4ME5jswrs7VUnZz+R5quoloM=; b=Oh1FF28VgiXTj8EGJXk7gSO3aLWTVfGSRpi+16tm4I0I3CQykiFz0HSKlWtfOLN4eN OqfVQVY65Hss79M9SybmdwsBy6lVAYZwSySwY+QR3t6Hkd+s6oMdM8DX9uqAA5a4XRHN JZzK7wBdvv4OljJoXduc6NyNQ6k+xs2BNEKL4eF3lbVUHWAIWMZot6MRpT6jH2k9TNXL jkzJDXVNtfCICx3angGJxOA7f9/Cv/Mh+Mqhctp6sMmn+HuifsyAUM0yy48Mh1H2trn2 2nyfz8IowZMK4rrQlwc9l5/BnJA9kdhhCGRAykTFcUnaBNi72spLFJ8sUvrc0RFLxdNJ 1s4A== X-Gm-Message-State: AFeK/H2dYjrK/G7GZauKdRZA/zjidgFcZkW1+nsTowTAANZfMV9G6ptYWHoQL/n/lNi0Hg== X-Received: by 10.107.48.142 with SMTP id w136mr50083746iow.16.1491855061881; Mon, 10 Apr 2017 13:11:01 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-88-57.neo.res.rr.com. [74.141.88.57]) by smtp.googlemail.com with ESMTPSA id s40sm4007930ite.18.2017.04.10.13.11.00 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 10 Apr 2017 13:11:01 -0700 (PDT) Message-ID: <58EBE6E6.8060008@gmail.com> Date: Mon, 10 Apr 2017 16:11:18 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: peter.blok@bsd4all.org CC: Pavel Timofeev , "Bjoern A. Zeeb" , freebsd-current Subject: Re: VNET branch destiny References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> <58EB8D98.5050904@gmail.com> <75BD8407-83AC-4383-912A-70083CED3FFD@bsd4all.org> In-Reply-To: <75BD8407-83AC-4383-912A-70083CED3FFD@bsd4all.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 20:11:02 -0000 peter.blok@bsd4all.org wrote: > Well, in my case it panic’ed on 11-stable. I’m only using pf on the > host, not in the jail. I’m using Devin Teske’s jng to create a netgraph > bridge. It is my intention to use the netgrpah bridge with bhyve as well. > I also tested using Devin Teske’s jng to create a netgraph bridge on RELEASE 10.0 and it worked. But when I tried the same configuration on RELEASE 11.0 it no longer worked. Sorry for the noise. I missed this sentence. "I’m only using pf on the host, not in the jail.". Thats what happens when I answer email after a long day at work. From owner-freebsd-current@freebsd.org Mon Apr 10 20:59:38 2017 Return-Path: Delivered-To: freebsd-current@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 A89FAD37626 for ; Mon, 10 Apr 2017 20:59:38 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq1.tb.mail.iss.as9143.net (smtpq1.tb.mail.iss.as9143.net [212.54.42.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C2EEB6C4 for ; Mon, 10 Apr 2017 20:59:37 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.34.120] (helo=smtp12.mnd.mail.iss.as9143.net) by smtpq1.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cxgPO-0006Gb-7V; Mon, 10 Apr 2017 22:59:34 +0200 Received: from 5ed15678.cm-7-2b.dynamic.ziggo.nl ([94.209.86.120] helo=wan0.bsd4all.org) by smtp12.mnd.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cxgPO-0004Tv-5f; Mon, 10 Apr 2017 22:59:34 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id D72BE719F; Mon, 10 Apr 2017 22:59:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bn_4cYY7IzIV; Mon, 10 Apr 2017 22:59:32 +0200 (CEST) Received: from [192.168.1.64] (mm [192.168.1.64]) by wan0.bsd4all.org (Postfix) with ESMTPSA id E18EA7196; Mon, 10 Apr 2017 22:59:31 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: VNET branch destiny From: peter.blok@bsd4all.org In-Reply-To: <58EBE6E6.8060008@gmail.com> Date: Mon, 10 Apr 2017 22:59:30 +0200 Cc: Pavel Timofeev , "Bjoern A. Zeeb" , freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> <58EB8D98.5050904@gmail.com> <75BD8407-83AC-4383-912A-70083CED3FFD@bsd4all.org> <58EBE6E6.8060008@gmail.com> To: Ernie Luzar X-Mailer: Apple Mail (2.3273) X-SourceIP: 94.209.86.120 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=Baeo6vl2 c=1 sm=1 tr=0 a=IkzOOneQUJP1+bAPekPvBg==:17 a=IkcTkHD0fZMA:10 a=AzvcPWV-tVgA:10 a=pGLkceISAAAA:8 a=6Q3WNqvRAAAA:8 a=Npu8PpBfyOLFG9ZBfWYA:9 a=QEXdDO2ut3YA:10 a=6kGIvZw6iX1k4Y-7sg4_:22 a=I8PBwKCn76L9oNdl0isp:22 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 20:59:38 -0000 No problem. Although pf is not used the vnet_destroy seems to be the = issue. Some parts are not virtualized and the = vnet_destroy->vnet_pf_uninit teardown happens on the host vnet so to = speak. > On 10 Apr 2017, at 22:11, Ernie Luzar wrote: >=20 > peter.blok@bsd4all.org wrote: >> Well, in my case it panic=E2=80=99ed on 11-stable. I=E2=80=99m only = using pf on the host, not in the jail. I=E2=80=99m using Devin Teske=E2=80= =99s jng to create a netgraph bridge. It is my intention to use the = netgrpah bridge with bhyve as well. >=20 >=20 > I also tested using Devin Teske=E2=80=99s jng to create a netgraph = bridge on > RELEASE 10.0 and it worked. But when I tried the same configuration on > RELEASE 11.0 it no longer worked. >=20 > Sorry for the noise. I missed this sentence. "I=E2=80=99m only using = pf on the > host, not in the jail.". Thats what happens when I answer email after = a long day at work. >=20 >=20 From owner-freebsd-current@freebsd.org Mon Apr 10 21:09:52 2017 Return-Path: Delivered-To: freebsd-current@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 0E234D37B53 for ; Mon, 10 Apr 2017 21:09:52 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C3570F2 for ; Mon, 10 Apr 2017 21:09:51 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 249DD25D3892; Mon, 10 Apr 2017 21:09:49 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 4EFFDD1F894; Mon, 10 Apr 2017 21:09:48 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id jrfYPuwCLZm4; Mon, 10 Apr 2017 21:09:47 +0000 (UTC) Received: from [192.168.124.1] (unknown [IPv6:fde9:577b:c1a9:4410:382a:5743:ea4:280]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 89541D1F88F; Mon, 10 Apr 2017 21:09:46 +0000 (UTC) From: "Bjoern A. Zeeb" To: peter.blok@bsd4all.org Cc: "Ernie Luzar" , "Pavel Timofeev" , freebsd-current Subject: Re: VNET branch destiny Date: Mon, 10 Apr 2017 21:09:43 +0000 Message-ID: <0049B4F0-8B07-49BA-8879-CD4D56190DE7@lists.zabbadoz.net> In-Reply-To: References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> <58EB8D98.5050904@gmail.com> <75BD8407-83AC-4383-912A-70083CED3FFD@bsd4all.org> <58EBE6E6.8060008@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (2.0BETAr6082) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 21:09:52 -0000 On 10 Apr 2017, at 20:59, peter.blok@bsd4all.org wrote: > No problem. Although pf is not used the vnet_destroy seems to be the > issue. Some parts are not virtualized and the > vnet_destroy->vnet_pf_uninit teardown happens on the host vnet so to > speak. The base system VNET is not shutdown; it never was. Module unload however could be a possible scenario. From owner-freebsd-current@freebsd.org Tue Apr 11 05:17:51 2017 Return-Path: Delivered-To: freebsd-current@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 B222DD2F789 for ; Tue, 11 Apr 2017 05:17:51 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2BBCF73 for ; Tue, 11 Apr 2017 05:17:50 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MfzEP-1cjjGs1vhF-00NTKF; Tue, 11 Apr 2017 07:17:43 +0200 Date: Tue, 11 Apr 2017 07:17:42 +0200 From: "Hartmann, O." To: "O. Hartmann" Cc: Toomas Soome , FreeBSD CURRENT Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <20170411071734.52017b27@hermann> In-Reply-To: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> References: <20170410145846.73d4350a@hermann> <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:w7HEGyM1sbf2BNQGNrQJqw8SoQfX5dWUSKtyyZVeU1pmKdZy5oB VyOWo0G3RjuBoG22Lum9lbzEz5yPIts4P6P0hRYry6Wa5XRs5/DPqJPjFRHlKz/YjZN8k6j Fda1l+o8q8GDBNXz4O/bEIQh5T5Qaiq6Y+m8CRbFxJcD2Ei8612WUcp6zlL49ZCUX4H2E1Z zXOpwZwCzQnI+baZT3PVQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:0YNBJ48kgwU=:so9sC2cJEoWlijP9lH/+ie dsFx5YPO1XZV8M/zx4xY51lFo8ZKCnMeFPGcN1UaRdmod3mqC4R6J5fhR137ELXnVduZF6XI+ d1aVE1Aw660nl0Ha4wDfI8t948Vqk80KEUNxpfHrlyv07fxBq0+YhZsDxsUFm/3ByEnJsOH8j xQNlB9T8VhpuE1lr/EXJiS3PuQEXX7uW5Lvs5/3byhK/WJyR5JBzoInf4nJrUt8cUdYJu+2zP ubAUi3vSopiPSmMKuqArWldtw52j0nRHPdxzQKOBrx226Rf+g1swhYvndglJ6Jty/QFoabvUe TSFs7mPJSIJHUQy6HntCiadstAdEMCNcTywp3Ue8KivRiSYLZu62hl0XpVdqvaRMXaLEAz5GL iScISCozS2iUg5yyjPF7gTrcSNze+5NwNLV0M7mAoWTOBw91/KEdKYvZj3sPO/Tx0BjyGICOm sq+k/ghpecavIa5utLeFfU5Wley5/VpBzmgsWzVbNNU4TirP9XrIvpZJLORva20zYMXc2oZXQ NdHMmbnuGOsLPYMM7YW42g8A/FSvIDiZ25v9u7wjKuLWszpBVA2B85iAP1cJuCqJ9DfUV9tq/ lMaqFHwcU93ZSQSazhAG/gIUSaJaCGV/FYKP3Yj+y03gxOJbuC4/u1vYCL225F7sHAuoud0ZN lirkHCi8mgQw3rbYCa4Fw4Ka0+wI+irRuphLqlVsyw4iRYyWvxWTdCc2QwsnMq0GBkDHCVnqr 8IhRQumbrrzFbbg/c/m71ZrnQ3AYrH/BGYg6fDGipO4XdC9vjCOTgAzWQfq7CZ1zekYbx0FWi 8c0aHkr X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 05:17:51 -0000 On Mon, 10 Apr 2017 21:04:04 +0200 "O. Hartmann" wrote: > Am Mon, 10 Apr 2017 21:59:00 +0300 > Toomas Soome schrieb: > > > > On 10. apr 2017, at 21:04, O. Hartmann > > > wrote: > > > > > > Am Mon, 10 Apr 2017 16:14:21 +0300 > > > Toomas Soome schrieb: > > > > > >>> On 10. apr 2017, at 15:58, Hartmann, O. > > >>> wrote: > > >>> > > >>> After today's update to r316677, some UEFI boxes (Fujitsu > > >>> Celsius M740 XEON) reject to boot properly. They die > > >>> immediately after loading /boot/loader.efi and jump into loader > > >>> prompt: > > >>> > > >>> [...] > > >>> \ > > >>> can't load 'kernel' > > >>> > > >>> > > >>> I had to investigate with an USB flashdrive the filesystem, but > > >>> everything seems to be properly in place and installed. > > >>> > > >>> I need advice how to revive the system after this. > > >>> > > >> > > >> > > >> hm, this implies that r316676 was ok? If so, the only logical > > >> conclusion is that it hast to do about the kernel size and if > > >> there is enough space in UEFI memory to place the kernel. > > >> > > >> You can fetch the current memory map from loader OK prompt with > > >> memmap command, I hope this will help to identify the issue. > > >> > > >> rgds, > > >> toomas > > > > > > > > > And? > > > > > > Regrads, > > > > > > oh > > > > > > > Well, the memory needed is starting from the: > > > > #define KERNEL_PHYSICAL_BASE (2*1024*1024) > > > > and it should be large enough for kernel. But it feels a bit like > > barking under the random tree; the problem is that the error is not > > telling us anything why it did happen:( > > > > This message you get is coming from sys/boot/common/boot.c, as part > > of the autoload sequence; did you try to load kernel manually with > > load command? also if you have old kernel around, does old kernel > > get loaded? > > > > rgds, > > toomas > > > > > > > > > > I haven't done anything yet, since the accident happened when I left > my bureau and I desperately tried to examine on the fly what happened. > > I'll be at the box tomorrow morning and I will check whether I can > load the old kernel manually. > > I'll report in what happened. > > Kind regards, > > oh > I did the following: replaced /boot/loader with /boot/loader.old (which was from end of March) copied /boot/loader.efi from the r315864 snapshot USB image into /boot/loader.efi of the broken systems. Aprt from the fact that I don't know which one is broken, the boxes are booting again. Conclusion: UEFI loader is broken! From owner-freebsd-current@freebsd.org Tue Apr 11 05:18:21 2017 Return-Path: Delivered-To: freebsd-current@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 EF943D2F82B for ; Tue, 11 Apr 2017 05:18:21 +0000 (UTC) (envelope-from ari@stonepile.fi) Received: from dmx.stonepile.fi (susi.stonepile.fi [84.22.101.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 B35A01AC for ; Tue, 11 Apr 2017 05:18:21 +0000 (UTC) (envelope-from ari@stonepile.fi) Received: from dmx.stonepile.fi (dmx.stonepile.fi [192.168.64.10]) by dmx.stonepile.fi (Postfix) with ESMTP id BC5BE273249 for ; Tue, 11 Apr 2017 08:10:25 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=stonepile.fi; h= content-transfer-encoding:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject:received:received; s=k2; t= 1491887423; bh=i8Gh4qtnmRP0La7aosNcvoVCT/nZLpq88qz3bg2sc9U=; b=U MimNbAVE8nahbUPEKQ6zLBHxWGHMdC5xS9WrOjkMWXobXLe4L9ksZNMYK7fISvmP hINupLEeStRF6RKKRg/ujLau2UNsAHr489ATK/gDD788SborxWGlw3Co+hcRXoZV ES5eGY5VSouXBzF+/axA6JQBNNpJrkMF5NJPAAfxaI= Received: from dmx.stonepile.fi ([192.168.64.10]) by dmx.stonepile.fi (dmx.stonepile.fi [192.168.64.10]) (amavisd-new, port 10026) with ESMTP id pMxHXs5JXnAp for ; Tue, 11 Apr 2017 08:10:23 +0300 (EEST) Received: from [192.168.2.200] (unknown [194.136.144.131]) by dmx.stonepile.fi (Postfix) with ESMTPSA id 2819C273018 for ; Tue, 11 Apr 2017 08:10:23 +0300 (EEST) Subject: Re: VNET branch destiny To: freebsd-current@freebsd.org References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> <58EB990A.50502@gmail.com> From: Ari Suutari Message-ID: <29a0a3da-1640-b8ad-a053-19420181c315@stonepile.fi> Date: Tue, 11 Apr 2017 08:10:47 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <58EB990A.50502@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 05:18:22 -0000 Hi, There is also this one: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213673 It's about memory leak with pf tables + vnet, but the problem results in panic, which is quite easily reproduced. Ari S. On 10.4.2017 17:39, Ernie Luzar wrote: > To the VNET (VIMAGE) update project team members > > Release 11.0 has some out standing VNET (VIMAGE) PR's that need > addressing. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212000 > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212013 > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212031 > > I believe 212000 and 212013 would require an rewrite replacing the > kernel method they use to the user land method as used by ipfw. At the > very lease it should be documented somewhere that pf & ipfilter do not > work in an vnet/vimage jail. > > PR 212031 looks like a vimage/vnet problem to me. > > > To the members of current, This bug report is not a jail(8) problem > but a kernel problem that needs to be addressed. Could someone please > look into fixing it. I effects all jail(8) users. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210049 > > There is also the matter of removing the depreciated rc.conf jail > definition method from the rc.d scripts making the jail.conf method > the default. This is long over due and maybe something over looked in > the 11.0 release. > > > Thank you for your attention. > > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Tue Apr 11 06:47:40 2017 Return-Path: Delivered-To: freebsd-current@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 A3658D39FD6 for ; Tue, 11 Apr 2017 06:47:40 +0000 (UTC) (envelope-from srs0=dq0p=3t=sigsegv.be=kristof@codepro.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 618BCEDA for ; Tue, 11 Apr 2017 06:47:40 +0000 (UTC) (envelope-from srs0=dq0p=3t=sigsegv.be=kristof@codepro.be) Received: from [10.0.2.164] (94-224-12-229.access.telenet.be [94.224.12.229]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id 87B5CD246; Tue, 11 Apr 2017 08:47:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigsegv.be; s=mail; t=1491893257; bh=5IWNZWUJi7orAA1JdtGvcD2Uo51VFboOZ+hBfr0E5JQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=yxeMuH58MPJgDfBPAimlGA0CMfO4X9dEYftwoLDGJopys7UqhqpyPcgZFk70ZEyL0 fO1f5fumSaBCEcJMH8mD1WMInHnDNFalXO1XDYHfBY0g2ZBdZ6f7KZa9zN33JkQw4h RlnOJwUccahEX8QrG+5Ckbkoz7gpBS9k3m657L1g= From: "Kristof Provost" To: peter.blok@bsd4all.org Cc: "Pavel Timofeev" , "Bjoern A. Zeeb" , freebsd-current Subject: Re: VNET branch destiny Date: Tue, 11 Apr 2017 08:47:36 +0200 Message-ID: <7B9879DE-7500-47CB-8471-38E2B899C324@sigsegv.be> In-Reply-To: <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate (2.0BETAr6082) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 06:47:40 -0000 On 10 Apr 2017, at 12:10, peter.blok@bsd4all.org wrote: > There have been issues with pf if I recall correctly. I currently have > issues with stable, pf and vnet. There is an issue with pf table > entries when an interface is moved to a different vnet. > > Does anyone no if there is a specific fix for this that hasn’t been > ported to stable? I haven’t had the time to test this on current. > I’m currently aware of at least some issues with pf and vnet, even in CURRENT. Not that one though, so can you make sure there’s a bug report with as much detail as possible? Please also cc me (kp@freebsd.org) on the report. Thanks, Kristof From owner-freebsd-current@freebsd.org Tue Apr 11 04:56:41 2017 Return-Path: Delivered-To: freebsd-current@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 625FBD2F2B9 for ; Tue, 11 Apr 2017 04:56:41 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC9A39D6 for ; Tue, 11 Apr 2017 04:56:40 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from hermann ([87.138.105.249]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M4GRv-1c7twL1LpT-00rlXb; Tue, 11 Apr 2017 06:51:18 +0200 Date: Tue, 11 Apr 2017 06:51:17 +0200 From: "Hartmann, O." To: Toomas Soome Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <20170411065109.3c74c132@hermann> In-Reply-To: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> References: <20170410145846.73d4350a@hermann> <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:pzhrY8obD4DZkr49q4JNKhxecvuKcu8BIAiv9oQj9pqZcqrn2It +G0Ky1D6BdwVTVThEOOvJd5TgnjmxORkueiTYTxsiBcnJIjuuNVP7i6JXBwEMrBsPqXozUe Sy7et0n9PuheSkrYZo+50v+f5kqW7ggRNUccQ8/5W2L8IvWg4gmsys9gYtObAiSAxtt7bpu zQF2ZzStIKUsWwljWfzSw== X-UI-Out-Filterresults: notjunk:1;V01:K0:cIWpxOVOAPs=:CcSw/7x5Gqt84tnj9mJcbW z8NuMAVjliW8tDmQwGYoMB18UOcbcAcgJYWFSBmDlg7+b3KXaDViNmQP5bBmsRpwGei/PvPJK Pkf7oKDdIb6aV9gWL7slgUF3vEU6kClp8uTPiXlNyIraFuWhYm3g3OQrrOlYYtYXDO6URnGw7 n15JE4HT1bUwNd/KE6HxwmyJ8jUPgrX06lTJ2SZ3qK9dOMTWKzL2QWQRQJT+q52QygTocRUpI PJffGqm3bAdb6IzAXxp9n4mtEFC76T9ZCpIeYUbrt8sr8tkZfiamXMLTm0yFjA0Zq5ftc9zbP w5Isqv+9QUZIoFcJenyPeznX1B+5xWNre4e/P6X7WMWNDLt+Q1Shxpx9Qsxsw3xlNsl0t1Wxb GBPdxbhAUKMhhUcWCmT1wEGHjDXorvNuc+UPWGe7A9CiWvQXJLTS0Z2OOEqOoQuaxzZSojU0k +z3qYBKGgiuUF58heaJpcGWbt0vJt491F6vV/AqkCATgHPXZxqvn4Il2Vcpjc3FOi0c00gJ5l Cipl99FKERoxsBNcKydVTlxCDa6eA5jCqD+gIbxpRLwYHMXkWgdK25m2bd7fcrtO8k7SRFhBj D0kEgak29NGzpFFR9+Sh5zSX9yJbEzHDSotmPZgCJ1lUOBjO4M0H6ojSWCBtnwG4VUe+UMgsS u5jFd4j/aq6wwuyiJFsPvFDm4wE2Av9OzkX3bF5QD5d7WSkId3aN5WcwLVkeEH+OO38qGSF1p czwq3l6x/i7E1/aqvh7iwD31GqmVTgjYwCbsl1JLIXK94a3igR5AA53DYG+0fLRyEFo4b+ARG DSGb2W9 X-Mailman-Approved-At: Tue, 11 Apr 2017 10:57:34 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 04:56:41 -0000 On Mon, 10 Apr 2017 21:04:04 +0200 "O. Hartmann" wrote: > Am Mon, 10 Apr 2017 21:59:00 +0300 > Toomas Soome schrieb: > > > > On 10. apr 2017, at 21:04, O. Hartmann > > > wrote: > > > > > > Am Mon, 10 Apr 2017 16:14:21 +0300 > > > Toomas Soome schrieb: > > > > > >>> On 10. apr 2017, at 15:58, Hartmann, O. > > >>> wrote: > > >>> > > >>> After today's update to r316677, some UEFI boxes (Fujitsu > > >>> Celsius M740 XEON) reject to boot properly. They die > > >>> immediately after loading /boot/loader.efi and jump into loader > > >>> prompt: > > >>> > > >>> [...] > > >>> \ > > >>> can't load 'kernel' > > >>> > > >>> > > >>> I had to investigate with an USB flashdrive the filesystem, but > > >>> everything seems to be properly in place and installed. > > >>> > > >>> I need advice how to revive the system after this. > > >>> > > >> > > >> > > >> hm, this implies that r316676 was ok? If so, the only logical > > >> conclusion is that it hast to do about the kernel size and if > > >> there is enough space in UEFI memory to place the kernel. > > >> > > >> You can fetch the current memory map from loader OK prompt with > > >> memmap command, I hope this will help to identify the issue. > > >> > > >> rgds, > > >> toomas > > > > > > > > > And? > > > > > > Regrads, > > > > > > oh > > > > > > > Well, the memory needed is starting from the: > > > > #define KERNEL_PHYSICAL_BASE (2*1024*1024) > > > > and it should be large enough for kernel. But it feels a bit like > > barking under the random tree; the problem is that the error is not > > telling us anything why it did happen:( > > > > This message you get is coming from sys/boot/common/boot.c, as part > > of the autoload sequence; did you try to load kernel manually with > > load command? also if you have old kernel around, does old kernel > > get loaded? > > > > rgds, > > toomas > > > > > > > > > > I haven't done anything yet, since the accident happened when I left > my bureau and I desperately tried to examine on the fly what happened. > > I'll be at the box tomorrow morning and I will check whether I can > load the old kernel manually. > > I'll report in what happened. > > Kind regards, > > oh > Sitting in front of the dead systems here, I checked for the suggestions of yours. memmap doesn#t give me an insight - I'm not familiar with the memory layout. Issuing a "ls" shows only / Also, we put an alternative UEFI boot loader onto the partition, taken from the snapshot r315864 (/boot/boot1.efifat, dd'ed onto the EFI partition) - with no success. By the way, my EFI partition is 300MB in size - just for the record if this is an issue. The booting filesystems are UFS and residing on a SSD. The point that the boot loader doens't see any folder structure but / confuses me. How to row back from this desaster? Oliver From owner-freebsd-current@freebsd.org Tue Apr 11 12:19:40 2017 Return-Path: Delivered-To: freebsd-current@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 AEA9DD3952E for ; Tue, 11 Apr 2017 12:19:40 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq5.tb.mail.iss.as9143.net (smtpq5.tb.mail.iss.as9143.net [212.54.42.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68F64D96 for ; Tue, 11 Apr 2017 12:19:39 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.42.133] (helo=smtp9.tb.mail.iss.as9143.net) by smtpq5.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cxuCw-0000kc-M1; Tue, 11 Apr 2017 13:43:38 +0200 Received: from 5ed15678.cm-7-2b.dynamic.ziggo.nl ([94.209.86.120] helo=wan0.bsd4all.org) by smtp9.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cxuCw-00022M-JT; Tue, 11 Apr 2017 13:43:38 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id 566B37373; Tue, 11 Apr 2017 13:43:36 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TaRDiZWU5D4p; Tue, 11 Apr 2017 13:43:34 +0200 (CEST) Received: from [192.168.1.64] (mm [192.168.1.64]) by wan0.bsd4all.org (Postfix) with ESMTPSA id 532B97368; Tue, 11 Apr 2017 13:43:34 +0200 (CEST) From: peter.blok@bsd4all.org Message-Id: <85718A56-E6B1-461F-A2BA-915B1AE43D06@bsd4all.org> Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: VNET branch destiny Date: Tue, 11 Apr 2017 13:43:33 +0200 In-Reply-To: <7B9879DE-7500-47CB-8471-38E2B899C324@sigsegv.be> Cc: Pavel Timofeev , "Bjoern A. Zeeb" , freebsd-current , ari@stonepile.fi To: Kristof Provost References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> <7B9879DE-7500-47CB-8471-38E2B899C324@sigsegv.be> X-Mailer: Apple Mail (2.3273) X-SourceIP: 94.209.86.120 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=DaNnkrlW c=1 sm=1 tr=0 a=IkzOOneQUJP1+bAPekPvBg==:17 a=AzvcPWV-tVgA:10 a=6I5d2MoRAAAA:8 a=6Q3WNqvRAAAA:8 a=d0me-gdv5dYI96SJEs4A:9 a=QEXdDO2ut3YA:10 a=0olLsx9A0LFJz_lWwhEA:9 a=jh6bSLaAOEbd74PK:21 a=_W_S_7VecoQA:10 a=IjZwj45LgO3ly-622nXo:22 a=I8PBwKCn76L9oNdl0isp:22 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 12:19:40 -0000 Hi Kristof, I=E2=80=99m prety sure it is the same as = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213673 = . It is = unrelated to epair or ng_eiface (my case). I=E2=80=99ll dig some more. Peter > On 11 Apr 2017, at 08:47, Kristof Provost wrote: >=20 > On 10 Apr 2017, at 12:10, peter.blok@bsd4all.org wrote: >> There have been issues with pf if I recall correctly. I currently = have issues with stable, pf and vnet. There is an issue with pf table = entries when an interface is moved to a different vnet. >>=20 >> Does anyone no if there is a specific fix for this that hasn=E2=80=99t = been ported to stable? I haven=E2=80=99t had the time to test this on = current. >>=20 > I=E2=80=99m currently aware of at least some issues with pf and vnet, = even in CURRENT. > Not that one though, so can you make sure there=E2=80=99s a bug report = with as much detail as possible? > Please also cc me (kp@freebsd.org) on the report. >=20 > Thanks, > Kristof From owner-freebsd-current@freebsd.org Tue Apr 11 14:44:04 2017 Return-Path: Delivered-To: freebsd-current@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 C69D5D39F42 for ; Tue, 11 Apr 2017 14:44:04 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msa03b.plala.or.jp (msa03.plala.or.jp [IPv6:2400:7800:0:5010::3]) by mx1.freebsd.org (Postfix) with ESMTP id 4A37C1C4 for ; Tue, 11 Apr 2017 14:44:04 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc02.plala.or.jp ([172.23.12.32]) by msa01b.plala.or.jp with ESMTP id <20170411144258.SOEF18684.msa01b.plala.or.jp@msc02.plala.or.jp>; Tue, 11 Apr 2017 23:42:58 +0900 Received: from localhost ([58.89.104.250]) by msc02.plala.or.jp with ESMTP id <20170411144258.MWGB18141.msc02.plala.or.jp@localhost>; Tue, 11 Apr 2017 23:42:58 +0900 Date: Tue, 11 Apr 2017 23:42:52 +0900 (JST) Message-Id: <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> To: ohartmann@walstatt.org Cc: tsoome@me.com, freebsd-current@freebsd.org Subject: Re: r316677:EFI boot failure: Can't load kernel From: Masachika ISHIZUKA In-Reply-To: <20170411071734.52017b27@hermann> References: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> <20170411071734.52017b27@hermann> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; msa01m; Tue, 11 Apr 2017 23:42:58 +0900 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 14:44:04 -0000 > replaced /boot/loader with /boot/loader.old (which was from end of > March) > > copied /boot/loader.efi from the r315864 snapshot USB image > into /boot/loader.efi of the broken systems. > > Aprt from the fact that I don't know which one is broken, the boxes are > booting again. > > Conclusion: UEFI loader is broken! Hi. I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. As reporting Bug 218473, I cannot boot /boot/loader.efi after r316585. Replacing only loader.efi before r316584, I can boot again. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Tue Apr 11 16:33:32 2017 Return-Path: Delivered-To: freebsd-current@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 0F389D39F62 for ; Tue, 11 Apr 2017 16:33:32 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DA0EFE71 for ; Tue, 11 Apr 2017 16:33:31 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OO900D004ISPT00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Tue, 11 Apr 2017 15:33:21 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1491924801; bh=1dRn9KGsMVNOCoodYIk3dMzAyN0vjzzpIV5vIzRXV7k=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=lsLsAuvxtEBLv3zty4f01j0UTxvVdBKds3pykcLQS9IO5m4IlP9qLgnWJOSzcKUu0 UGyUYFwQpg/GReD+NgEbfNBKwrNfuVMifXtV6lkkHlYQYJ07nL6majeUIz2kwi01IA hs3ieb6e3ohutsKY2U6Un6UrI35nFPnOlvjtghUsDlX7kU7OsZVdAL5nreYkFovbVi 1yHo0dE1eXoWiP9xblXBSgOKlVzBd2XCFXW22gvivvijgJo0ISGWLr5mokcCCmnJtH VAR0+Fg3vY8IqFTLumaiGzlco/fA4PjPQ0dAwiyPMligbFoVo1vzBN/WJz9MnjvW6y 3IflHOWpxokxQ== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OO9001FB4JIE420@st13p35im-asmtp002.me.com>; Tue, 11 Apr 2017 15:33:21 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-11_13:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1704110119 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: r316677:EFI boot failure: Can't load kernel From: Toomas Soome In-reply-to: <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> Date: Tue, 11 Apr 2017 18:33:18 +0300 Cc: "Hartmann, O." , freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <4E8539E2-B5D9-437E-ADBF-4730ECED0E05@me.com> References: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> <20170411071734.52017b27@hermann> <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> To: Masachika ISHIZUKA X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 16:33:32 -0000 > On 11. apr 2017, at 17:42, Masachika ISHIZUKA = wrote: >=20 >> replaced /boot/loader with /boot/loader.old (which was from end of >> March) >>=20 >> copied /boot/loader.efi from the r315864 snapshot USB image >> into /boot/loader.efi of the broken systems. >>=20 >> Aprt from the fact that I don't know which one is broken, the boxes = are >> booting again. >>=20 >> Conclusion: UEFI loader is broken! >=20 > Hi. >=20 > I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. > As reporting Bug 218473, I cannot boot /boot/loader.efi after > r316585. Replacing only loader.efi before r316584, I can boot > again. > --=20 > Masachika ISHIZUKA Yea, it seems to be the same issue for both of you, now have some work = to do to identify why this does happen. from loader prompt the lsdev -v output would be helpful - you can send = it directly, we do not need to spam the list:) rgds, toomas= From owner-freebsd-current@freebsd.org Tue Apr 11 22:18:25 2017 Return-Path: Delivered-To: freebsd-current@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 6774BD3A0FB for ; Tue, 11 Apr 2017 22:18:25 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 4C29CE4C for ; Tue, 11 Apr 2017 22:18:24 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-4-62.albq.qwest.net [97.123.4.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id CE82F1928AC for ; Tue, 11 Apr 2017 22:18:23 +0000 (UTC) To: freebsd-current From: Sean Bruno Subject: List test, please ignore. Message-ID: <8760bb37-1de1-6531-7443-ad7de82d9069@freebsd.org> Date: Tue, 11 Apr 2017 16:18:23 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="EQfkQofaiCdJrSoMQR6mJHtgIWaXjFOP8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 22:18:25 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --EQfkQofaiCdJrSoMQR6mJHtgIWaXjFOP8 Content-Type: multipart/mixed; boundary="TqBLFjDdvj1vqmFJgJ1kDnDAolGj3igiR"; protected-headers="v1" From: Sean Bruno To: freebsd-current Message-ID: <8760bb37-1de1-6531-7443-ad7de82d9069@freebsd.org> Subject: List test, please ignore. --TqBLFjDdvj1vqmFJgJ1kDnDAolGj3igiR Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable ignore --TqBLFjDdvj1vqmFJgJ1kDnDAolGj3igiR-- --EQfkQofaiCdJrSoMQR6mJHtgIWaXjFOP8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAljtVi9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmTnRQgAgDIqhSn6lCsCBR9jHB8KRMs5xOLkDyPxAJNpVQ/F6v245DfAUk3RgoAm UBE54eytThj+jgTb26LcnGh1KB8sTbL0jpx0ySx7glpYmfPGVQ+p7ekLgVlG5Dkq YL8Vy/grGFgTWhEo3umnIBLP+1L2dOMVGlh75hVQ+zOQfP+9Yv8ItTqpvhms4l4u T4cQgjHcZ7eGqfKI5X9wb8ajH3I4T1q9LKOZL+uCGanUMYPYDSIL83mAawqt0LJ+ MSlgucxz9WkITC2v3LCLvFH9cuwi3CzA///vMsh8vE6bzpBrK3qf2N0d9RTmya1r KBm33fR3UqQGVDFBU8+VfpZyCaFPPg== =mq7S -----END PGP SIGNATURE----- --EQfkQofaiCdJrSoMQR6mJHtgIWaXjFOP8-- From owner-freebsd-current@freebsd.org Tue Apr 11 22:45:00 2017 Return-Path: Delivered-To: freebsd-current@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 BBA62D3A95F for ; Tue, 11 Apr 2017 22:45:00 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E74AE0F; Tue, 11 Apr 2017 22:45:00 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by mail-oi0-x236.google.com with SMTP id g204so13580183oib.1; Tue, 11 Apr 2017 15:45:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=VSlp+pCDKHK/CdB4+7Phs/85yKpUH8fP3Q0zQwFNkIY=; b=lQuH92BP4SYXhVEfiRQ5Ne0LRgb8nRBNOtQTcWA097q3HdJBvylv0343DOJG1ojIyA RT/TBSYQUh/+hm/XykFXgY9mF4+FDZM/qdFPzqft10m/va8aWemV9rTe3MQvt+33P59u 2TMXqaQKz0KOvZvUwIyAzvWlhCsSEEFD/GPePl02uGgCDKfCRq9uxCWJV1aCBwSYYtjr IHqRKrbsUMFn2Z6XdalpiwzWkC0Pkm9lsiW4msy8L9z6LP7R5GHrAzhVRSuLHXKF34A7 djL8isc4BgtKnPCjaZYMuDnNY7Uolmgvc8WYvvZHPEg1PC855NcK5nyIwdnTmjqeCebZ eeaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=VSlp+pCDKHK/CdB4+7Phs/85yKpUH8fP3Q0zQwFNkIY=; b=PE9ZDMw81FpGnNNAHUtAVm2N4pP2DhR6H2mEERY7TC8Cp5Qcto4GdJl/qHbcrlAieu HAaBtulteo0lCgoVa5aQBszNl3uDx+57Zuo+l3CFxtYCMKsrnSvnnhPe50qFzIBJdUQE IA4K2YhMas24QAdu4OzV/I1DRZHu+1FWr2UCtzYIPL56eNaAs+twlwHy+OGVzwcrD+2S WjTNnoyzlwoAGgpHm8J7in9gZ+8HMQOGO5KRQUSxEfXZMK88Ny6ZhpOYwcbznGxXOJ90 QzUjMk9QftT0V8nf7E/JeK59GuQk1bnQf+O95UjtqVAI8tXEcuR3wIDiyDcAWDd7qKju imGQ== X-Gm-Message-State: AN3rC/5y/J/XJ9J9jYvIAN57A2WeKT69ajXPNKttUeiKGKPalJySDTR3hTn2xXT2p5uUVdIw1TaHCdtUUyZAjQ== X-Received: by 10.157.48.146 with SMTP id s18mr14122318otc.108.1491950699570; Tue, 11 Apr 2017 15:44:59 -0700 (PDT) MIME-Version: 1.0 References: <8760bb37-1de1-6531-7443-ad7de82d9069@freebsd.org> In-Reply-To: <8760bb37-1de1-6531-7443-ad7de82d9069@freebsd.org> From: Eric Joyner Date: Tue, 11 Apr 2017 22:44:48 +0000 Message-ID: Subject: Re: List test, please ignore. To: Sean Bruno , freebsd-current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 22:45:00 -0000 Never! On Tue, Apr 11, 2017 at 3:18 PM Sean Bruno wrote: > ignore > > From owner-freebsd-current@freebsd.org Tue Apr 11 23:49:52 2017 Return-Path: Delivered-To: freebsd-current@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 83501D3AC0A for ; Tue, 11 Apr 2017 23:49:52 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msa01a.plala.or.jp (msa01.plala.or.jp [58.93.240.1]) by mx1.freebsd.org (Postfix) with ESMTP id F0AABDAE for ; Tue, 11 Apr 2017 23:49:50 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc01.plala.or.jp ([172.23.12.31]) by msa03b.plala.or.jp with ESMTP id <20170411234726.YYYG10034.msa03b.plala.or.jp@msc01.plala.or.jp>; Wed, 12 Apr 2017 08:47:26 +0900 Received: from localhost ([58.89.104.250]) by msc01.plala.or.jp with ESMTP id <20170411234726.MPVL19006.msc01.plala.or.jp@localhost>; Wed, 12 Apr 2017 08:47:26 +0900 Date: Wed, 12 Apr 2017 08:47:22 +0900 (JST) Message-Id: <20170412.084722.2206764483279765796.ish@amail.plala.or.jp> To: tsoome@me.com Cc: ohartmann@walstatt.org, freebsd-current@freebsd.org Subject: Re: r316677:EFI boot failure: Can't load kernel From: Masachika ISHIZUKA In-Reply-To: <4E8539E2-B5D9-437E-ADBF-4730ECED0E05@me.com> References: <20170411071734.52017b27@hermann> <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> <4E8539E2-B5D9-437E-ADBF-4730ECED0E05@me.com> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; msa03m; Wed, 12 Apr 2017 08:47:26 +0900 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 23:49:52 -0000 >> I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. >> As reporting Bug 218473, I cannot boot /boot/loader.efi after >> r316585. Replacing only loader.efi before r316584, I can boot >> again. > > Yea, it seems to be the same issue for both of you, now have some work to do to identify why this does happen. > > from loader prompt the lsdev -v output would be helpful - you can send it directly, we do not need to spam the list:) Hi. I cannot lsdev because loader.efi was hung up before loader menu. ========= EFI console: \ <--- hang up ========= I can only reboot (ctrl-alt-del) for this hang up. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Wed Apr 12 14:03:18 2017 Return-Path: Delivered-To: freebsd-current@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 2E821D3BCE1 for ; Wed, 12 Apr 2017 14:03:18 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq1.tb.mail.iss.as9143.net (smtpq1.tb.mail.iss.as9143.net [212.54.42.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DDC9BA84 for ; Wed, 12 Apr 2017 14:03:17 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.34.117] (helo=smtp9.mnd.mail.iss.as9143.net) by smtpq1.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cyIrT-0001Na-U4; Wed, 12 Apr 2017 16:03:07 +0200 Received: from 5ed15678.cm-7-2b.dynamic.ziggo.nl ([94.209.86.120] helo=wan0.bsd4all.org) by smtp9.mnd.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cyIrT-0001o4-RR; Wed, 12 Apr 2017 16:03:07 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id 4B2277352; Wed, 12 Apr 2017 16:03:07 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkHOLd3saLVj; Wed, 12 Apr 2017 16:03:06 +0200 (CEST) Received: from [192.168.1.64] (mm [192.168.1.64]) by wan0.bsd4all.org (Postfix) with ESMTPSA id D768E734A; Wed, 12 Apr 2017 16:03:05 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: panic with jail bug_id 213673 was: VNET branch destiny From: peter.blok@bsd4all.org In-Reply-To: <85718A56-E6B1-461F-A2BA-915B1AE43D06@bsd4all.org> Date: Wed, 12 Apr 2017 16:03:05 +0200 Cc: Pavel Timofeev , "Bjoern A. Zeeb" , freebsd-current , ari@stonepile.fi Content-Transfer-Encoding: quoted-printable Message-Id: <1B59D667-DF9E-4F68-A024-FC96FAFEE747@bsd4all.org> References: <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> <7B9879DE-7500-47CB-8471-38E2B899C324@sigsegv.be> <85718A56-E6B1-461F-A2BA-915B1AE43D06@bsd4all.org> To: Kristof Provost X-Mailer: Apple Mail (2.3273) X-SourceIP: 94.209.86.120 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=ZpSdE5zG c=1 sm=1 tr=0 a=IkzOOneQUJP1+bAPekPvBg==:17 a=IkcTkHD0fZMA:10 a=AzvcPWV-tVgA:10 a=6Q3WNqvRAAAA:8 a=6I5d2MoRAAAA:8 a=l_XCJ1vjxRHGdAvyGXcA:9 a=4gPl2zFEiwZUWhjw:21 a=zPDBYn9PRV8jXRl9:21 a=QEXdDO2ut3YA:10 a=I8PBwKCn76L9oNdl0isp:22 a=IjZwj45LgO3ly-622nXo:22 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2017 14:03:18 -0000 The problem happens when stopping a jail. It doesn=E2=80=99t seem to be = related to vnet at all. When stopping a jail, pfr_cleanup calls uma_zdestroy(V_pfr_kentry_z). = The dtor calls zone_release, which calls slab_free_item. The issue seems = to be that the keg found in zone_release does not belong to the zone = that is to be destroyed, but belongs to the zone that is created for the = same purpose at the host. The zone belongs to the jail (verified). The = added if (marked with XXX) fixes the problem. I don=E2=80=99t understand how a keg ends up in a different zone. zone_release(uma_zone_t zone, void **bucket, int cnt) { void *item; uma_slab_t slab; uma_keg_t keg; uint8_t *mem; int clearfull; int i; =20 clearfull =3D 0; keg =3D zone_first_keg(zone); KEG_LOCK(keg); for (i =3D 0; i < cnt; i++) { item =3D bucket[i]; if (!(zone->uz_flags & UMA_ZONE_VTOSLAB)) { mem =3D (uint8_t *)((uintptr_t)item & = (~UMA_SLAB_MASK)); if (zone->uz_flags & UMA_ZONE_HASH) { slab =3D hash_sfind(&keg->uk_hash, mem); } else { mem +=3D keg->uk_pgoff; slab =3D (uma_slab_t)mem; } } else { slab =3D vtoslab((vm_offset_t)item); if (slab->us_keg !=3D keg) { KEG_UNLOCK(keg); keg =3D slab->us_keg; KEG_LOCK(keg); } } if (keg =3D=3D slab->us_keg) = // XXX seems to fix the problem slab_free_item(keg, slab, item); > On 11 Apr 2017, at 13:43, peter.blok@bsd4all.org wrote: >=20 > Hi Kristof, >=20 > I=E2=80=99m prety sure it is the same as = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213673 = . It is = unrelated to epair or ng_eiface (my case). >=20 > I=E2=80=99ll dig some more. >=20 > Peter >=20 >=20 >> On 11 Apr 2017, at 08:47, Kristof Provost wrote: >>=20 >> On 10 Apr 2017, at 12:10, peter.blok@bsd4all.org wrote: >>> There have been issues with pf if I recall correctly. I currently = have issues with stable, pf and vnet. There is an issue with pf table = entries when an interface is moved to a different vnet. >>>=20 >>> Does anyone no if there is a specific fix for this that hasn=E2=80=99t= been ported to stable? I haven=E2=80=99t had the time to test this on = current. >>>=20 >> I=E2=80=99m currently aware of at least some issues with pf and vnet, = even in CURRENT. >> Not that one though, so can you make sure there=E2=80=99s a bug = report with as much detail as possible? >> Please also cc me (kp@freebsd.org) on the report. >>=20 >> Thanks, >> Kristof >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Apr 12 19:47:17 2017 Return-Path: Delivered-To: freebsd-current@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 97B1BD3A0D0 for ; Wed, 12 Apr 2017 19:47:17 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 76E2E816 for ; Wed, 12 Apr 2017 19:47:16 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v3CJmneK061786 for ; Wed, 12 Apr 2017 12:48:55 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> References: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> <20170411071734.52017b27@hermann>, <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> From: "Chris H" Subject: Re: r316677:EFI boot failure: Can't load kernel Date: Wed, 12 Apr 2017 12:48:55 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2017 19:47:17 -0000 On Tue, 11 Apr 2017 23:42:52 +0900 (JST) Masachika ISHIZUKA wrote > > replaced /boot/loader with /boot/loader.old (which was from end of > > March) > > > > copied /boot/loader.efi from the r315864 snapshot USB image > > into /boot/loader.efi of the broken systems. > > > > Aprt from the fact that I don't know which one is broken, the boxes are > > booting again. > > > > Conclusion: UEFI loader is broken! > > Hi. > > I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. > As reporting Bug 218473, I cannot boot /boot/loader.efi after > r316585. Replacing only loader.efi before r316584, I can boot > again. I was going to also report similar findings. After reporting the problem && submitting additional info to help diagnose the situation. I found that the most efficient way to overcome the issue, was to move loader.efi aside, and copy loader.efi from the install DVD. I've since lowered the priority of (u)efi in the BIOS, taking legacy as the higher priority. Because I had additional problems with vt. In the end, I find I have no issues simply booting to syscons(4) -- Xorg even works more harmoniously with it. :-) --Chris From owner-freebsd-current@freebsd.org Wed Apr 12 20:03:59 2017 Return-Path: Delivered-To: freebsd-current@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 233D0D3A610 for ; Wed, 12 Apr 2017 20:03:59 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC2C884 for ; Wed, 12 Apr 2017 20:03:58 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OOB00K00BIRT700@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Wed, 12 Apr 2017 20:03:58 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1492027437; bh=YhvBDNfwDcoYK/lOG7W8mL0JAhj0CLAEjk3CCUjYrWE=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=KuzMKKplj+i5kJd4SrrQ+9jAyP6RZD5XjSR1fVBuFgyVquoERUNwfrkizPPEKbS9t 1Z1B7T7qsmtgLz9yFYrqWk83mW9iF/J/UmoWqhrP++jOmIvWaejxAg1V1nMyUyYUBS SysEDLButXYbAUwbakPhAZFmlRJ+wq7F063uJzMTRarnSIc3qUeD/chnGDURkWJPPX K7sGr9gbT4iqMG5n5E9/56Tdue3sk7TvFAXBFXH2SgK/ptpisVQEWfTJO72/eazWIM pf0CAvatbp3qny/NPwRCBg2cbwo34E4fkvv602kvrS+rtWHHmqZ9JA6YD/XJXOg3yg iim9rcOGjvOow== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OOB00M8KBQB0900@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Wed, 12 Apr 2017 20:03:52 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-12_15:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1704120164 From: Toomas Soome MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: r316677:EFI boot failure: Can't load kernel Date: Wed, 12 Apr 2017 23:03:47 +0300 References: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> <20170411071734.52017b27@hermann> <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> To: FreeBSD CURRENT In-reply-to: Message-id: X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2017 20:03:59 -0000 > On 12. apr 2017, at 22:48, Chris H wrote: >=20 > On Tue, 11 Apr 2017 23:42:52 +0900 (JST) Masachika ISHIZUKA > > wrote >=20 >>> replaced /boot/loader with /boot/loader.old (which was from end of >>> March) >>>=20 >>> copied /boot/loader.efi from the r315864 snapshot USB image >>> into /boot/loader.efi of the broken systems. >>>=20 >>> Aprt from the fact that I don't know which one is broken, the boxes = are >>> booting again. >>>=20 >>> Conclusion: UEFI loader is broken! >>=20 >> Hi. >>=20 >> I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. >> As reporting Bug 218473, I cannot boot /boot/loader.efi after >> r316585. Replacing only loader.efi before r316584, I can boot >> again. >=20 > I was going to also report similar findings. > After reporting the problem && submitting additional info to help > diagnose the situation. > I found that the most efficient way to overcome the issue, was to > move loader.efi aside, and copy loader.efi from the install DVD. > I've since lowered the priority of (u)efi in the BIOS, taking > legacy as the higher priority. Because I had additional problems > with vt. In the end, I find I have no issues simply booting to > syscons(4) -- Xorg even works more harmoniously with it. :-) >=20 We have progress with investigation, but testing has to confirm if the = suspect is really it or not. rgds, toomas From owner-freebsd-current@freebsd.org Wed Apr 12 21:45:22 2017 Return-Path: Delivered-To: freebsd-current@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 AF033D3B071 for ; Wed, 12 Apr 2017 21:45:22 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670060.outbound.protection.outlook.com [40.107.67.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 60B0FEE8; Wed, 12 Apr 2017 21:45:22 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0192.CANPRD01.PROD.OUTLOOK.COM (10.165.218.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Wed, 12 Apr 2017 21:45:20 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.1019.026; Wed, 12 Apr 2017 21:45:20 +0000 From: Rick Macklem To: Konstantin Belousov CC: Gergely Czuczy , Dimitry Andric , Ian Lepore , FreeBSD Current Subject: Re: process killed: text file modification Thread-Topic: process killed: text file modification Thread-Index: AQHSnqPLfXcZwdtVHkecT5jK6Yv9dKGYQJIXgAAZ/baAAFsxgIAAVqF+gAAJQ4CAAFvPgIAAF1PPgABnggCAArMZZIAAClcAgAHrwICAA2WzgIAA/q43gACd2YCAAN05xoAd9Xb6 Date: Wed, 12 Apr 2017 21:45:20 +0000 Message-ID: References: <20170317141917.GS16105@kib.kiev.ua> <20170318032150.GW16105@kib.kiev.ua> <4642046a-08e6-35af-c76e-c5e306f01e62@harmless.hu> <050751d5-8c4d-b257-7c83-3a9bfb38a86d@harmless.hu> , <20170324070141.GB43712@kib.kiev.ua>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=uoguelph.ca; x-microsoft-exchange-diagnostics: 1; YTXPR01MB0192; 7:4kM0i5oVMQAg0t4Tm7tIz8CeQcWCgyba/OFBhktz22OKthwyHzya99hsP0KRFYf6LS33gGtNoxxnvD/7at1xghB1erv3WYrv9SrM1rGx2LCkiKO0MK/93vPEBYyELkNAA33TAaHB6BlMCHGmGIuzJWA1ZOYZk+sbaZAWwt504nZl7xaYvDeenYWTQdUFXOxFasXrAD0f6dOB5f0cciqBfChrQbz1U2b6yry6AdXyWZcVS1DbfKi3daZkMLOLJEu7t9xfihiBgLDDpvcPSErIDEIXvbv0bkIwjzwWNDGFkR3EU8jdwLe1apIa0ffov70zFAPjAi9gr5G+a7om4mzjzg== x-ms-office365-filtering-correlation-id: 350c5d27-4ec2-42cb-2609-08d481ed3760 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:YTXPR01MB0192; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(75325880899374); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123560025)(20161123555025)(20161123564025)(20161123562025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(6072148); SRVR:YTXPR01MB0192; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0192; x-forefront-prvs: 027578BB13 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39850400002)(39410400002)(39840400002)(39450400003)(39400400002)(377454003)(40764003)(24454002)(55674003)(4326008)(2906002)(53936002)(9686003)(6436002)(55016002)(3660700001)(76176999)(53546009)(189998001)(54356999)(38730400002)(81166006)(305945005)(110136004)(6246003)(25786009)(8676002)(50986999)(74482002)(39060400002)(122556002)(86362001)(1411001)(8936002)(77096006)(6506006)(2900100001)(6306002)(74316002)(54906002)(5660300001)(3280700002)(93886004)(33656002)(229853002)(2950100002)(6916009)(102836003)(7696004); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0192; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2017 21:45:20.0381 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0192 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2017 21:45:22 -0000 I have just committed a patch to head (r316745) which should fix this. (It includes code to handle the recent change to head to make the pageouts write through the buffer cache.) It will be MFC'd and should be in 11.1. Thanks everyone, for your help with this, rick ________________________________________ From: owner-freebsd-current@freebsd.org = on behalf of Rick Macklem Sent: Friday, March 24, 2017 4:14:45 PM To: Konstantin Belousov Cc: Gergely Czuczy; Dimitry Andric; Ian Lepore; FreeBSD Current Subject: Re: process killed: text file modification I can't do commits until I get home in mid-April. That's why it will be waiting until then. It should make it into stable/11 in plenty of time for 11.1. Thanks for your help with this, rick ________________________________________ From: owner-freebsd-current@freebsd.org = on behalf of Konstantin Belousov Sent: Friday, March 24, 2017 3:01:41 AM To: Rick Macklem Cc: Gergely Czuczy; Dimitry Andric; Ian Lepore; FreeBSD Current Subject: Re: process killed: text file modification On Thu, Mar 23, 2017 at 09:39:00PM +0000, Rick Macklem wrote: > Try whatever you like. However, if the case that failed before doesn't fa= il now, > I'd call the test a success. > > Thanks, rick > ps: It looks like Kostik is going to work on converting the NFS vop_putpa= ges() to > using the buffer cache. However, if this isn't ready for head/curre= nt by mid-April, > I will commit this patch to help fix things in the meantime. I do not see a reason to wait for my work before committing your patch. IMO, instead, it should be committed ASAP and merged into stable/11 for upcoming 11.1. I will do required adjustments if/when _putpages() patch progresses enough. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Apr 13 06:13:58 2017 Return-Path: Delivered-To: freebsd-current@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 CE9F1D3BF07 for ; Thu, 13 Apr 2017 06:13:58 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A45F6D19 for ; Thu, 13 Apr 2017 06:13:58 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OOC004003PSTP00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Thu, 13 Apr 2017 06:13:52 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1492064031; bh=x4cle7nlNEUaz2+SuT6uv6nOEHFp0D7DtOQ0F24Jo34=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=WzaHFPhc02inn+O16aRujMs6NgnSOztZFSZFQmFywbt6ONNUTdxd0BNepotFL4K7u JjgpGLeGasCz8siWfmc1RgoEbML5ydiq3DoF8fh+vDjiEhVBt40wDMCyy56rIdQNZU jz18KKhcbfuTTwupX+fHXXjUud7AMMlurmShxV2kGieyalgC/EVIwkGXXIvr4IppqC +2tpr61OISYPFo5QQQLszjE0cWesbVP0FiNM6kLvRlUL+IFBOGYiAHmNWWrJN6dw4U E5W7s96zKHDOrvd/8VjkJzpshji0bl4bsQ3AS8NXBmj+z1KohqrnCdQZa5dVIwBFj0 Mw1jTKo3NKiIw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OOC008SW3Z1AO10@st13p35im-asmtp002.me.com>; Thu, 13 Apr 2017 06:13:51 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-13_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1704130050 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: r316677:EFI boot failure: Can't load kernel Date: Thu, 13 Apr 2017 09:13:49 +0300 In-reply-to: Cc: freebsd-current@freebsd.org To: Chris H References: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> <20170411071734.52017b27@hermann> <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2017 06:13:58 -0000 > On 12. apr 2017, at 22:48, Chris H wrote: >=20 > On Tue, 11 Apr 2017 23:42:52 +0900 (JST) Masachika ISHIZUKA > > wrote >=20 >>> replaced /boot/loader with /boot/loader.old (which was from end of >>> March) >>>=20 >>> copied /boot/loader.efi from the r315864 snapshot USB image >>> into /boot/loader.efi of the broken systems. >>>=20 >>> Aprt from the fact that I don't know which one is broken, the boxes = are >>> booting again. >>>=20 >>> Conclusion: UEFI loader is broken! >>=20 >> Hi. >>=20 >> I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. >> As reporting Bug 218473, I cannot boot /boot/loader.efi after >> r316585. Replacing only loader.efi before r316584, I can boot >> again. >=20 > I was going to also report similar findings. > After reporting the problem && submitting additional info to help > diagnose the situation. > I found that the most efficient way to overcome the issue, was to > move loader.efi aside, and copy loader.efi from the install DVD. > I've since lowered the priority of (u)efi in the BIOS, taking > legacy as the higher priority. Because I had additional problems > with vt. In the end, I find I have no issues simply booting to > syscons(4) -- Xorg even works more harmoniously with it. :-) >=20 I believe we did identify the problem, the fix is posted as = https://reviews.freebsd.org/D10381 = please review, if you can confirm the fix by testing, it would also be = really helpful - the issue is, the problem appears to be system specific = and not always manifesting itself. thanks, toomas From owner-freebsd-current@freebsd.org Thu Apr 13 21:05:18 2017 Return-Path: Delivered-To: freebsd-current@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 3FD2AD104F4 for ; Thu, 13 Apr 2017 21:05:18 +0000 (UTC) (envelope-from mmumby@xtra.co.nz) Received: from out2303.xtra.co.nz (out2303.xtra.co.nz [210.55.143.50]) (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 E38DE971 for ; Thu, 13 Apr 2017 21:05:16 +0000 (UTC) (envelope-from mmumby@xtra.co.nz) DKIM-Signature: v=1; a=rsa-sha256; d=xtra.co.nz; s=alpha; c=relaxed/relaxed; q=dns/txt; i=@xtra.co.nz; t=1492116606; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc; bh=EAVSmnUryko3wqXsr1biuZVWi44goF/YnSdptkArGoo=; b=zfpmTZTFUmRKlM91yNyq/EeEW3De1I4AthcwU+JuuovBe2d57V4R9mBaHwiLALQc mOr7tD4dc1mPsID2HbV/xjMVTKPztCOa+bN8NItYhh/a9zH4kfG7HKwBZ8Z9O507 2D0oj80khVrzkIZwnV+5DhLWns3wxh5ykaAD7UC7Zow=; Received: from [122.62.136.121] by send.xtra.co.nz with ESMTP (using SSLv3 with cipher DES-CBC3-SHA (112/168 bits)) id 58EFE47D-AEBD3710@mta2305.omr; Thu, 13 Apr 2017 20:50:06 +0000 MIME-Version: 1.0 Message-ID: <2F.ED.19079.D74EFE85@xtra.co.nz> To: "freebsd-current@freebsd.org" From: Subject: Ports not building due to release not supported Date: Fri, 14 Apr 2017 08:50:05 +1200 Importance: normal X-Priority: 3 X-Mailman-Approved-At: Thu, 13 Apr 2017 21:21:07 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2017 21:05:18 -0000 Hi, I am unable to build ports as I am getting the error message =E2=80=93 Ports Collection support for your FreeBSD version has ended, and no ports a= re guaranteed to build on this system. Please upgrade to a supported release. But my version is=20 FreeBSD rpi2 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r293851: Fri Jan 22 22:09= :32 NZDT 2016 mark@raspberryPI:/usr/home/mark/crochet-master/work/obj/a= rm.armv6/usr/src/sys/RPI2 arm When I try to update I get the following =E2=80=93 root@rpi2:/usr/ports/net/freeradius3 # freebsd-update fetch src component not installed, skipped Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching public key from update4.freebsd.org... failed. Fetching public key from update5.freebsd.org... failed. Fetching public key from update6.freebsd.org... failed. Fetching public key from update3.freebsd.org... failed. No mirrors remaining, giving up. This version was originally built on FreeBSD 10.2, but I updated it to 11 a= few weeks after I got it working. Any assistance will be appreciated. Thanks Mark From owner-freebsd-current@freebsd.org Thu Apr 13 21:44:17 2017 Return-Path: Delivered-To: freebsd-current@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 83193D3C70E for ; Thu, 13 Apr 2017 21:44:17 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 125902A9 for ; Thu, 13 Apr 2017 21:44:16 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:1c1d:86a1:a200:b700]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 2B0141AC8 for ; Thu, 13 Apr 2017 21:44:06 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/2B0141AC8; dkim=none; dkim-atps=neutral Subject: Re: Ports not building due to release not supported To: freebsd-current@freebsd.org References: <2F.ED.19079.D74EFE85@xtra.co.nz> From: Matthew Seaman Message-ID: <9186a4e6-05e2-e3ff-abe8-bfb463354225@FreeBSD.org> Date: Thu, 13 Apr 2017 22:44:05 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <2F.ED.19079.D74EFE85@xtra.co.nz> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="OQ0IL37ixAtef11aE7H0dqXiSBCl4WCt5" X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2017 21:44:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OQ0IL37ixAtef11aE7H0dqXiSBCl4WCt5 Content-Type: multipart/mixed; boundary="vBuD2hsTabVOwkOoNnL1bMvsX394CqpOB"; protected-headers="v1" From: Matthew Seaman To: freebsd-current@freebsd.org Message-ID: <9186a4e6-05e2-e3ff-abe8-bfb463354225@FreeBSD.org> Subject: Re: Ports not building due to release not supported References: <2F.ED.19079.D74EFE85@xtra.co.nz> In-Reply-To: <2F.ED.19079.D74EFE85@xtra.co.nz> --vBuD2hsTabVOwkOoNnL1bMvsX394CqpOB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 13/04/2017 21:50, mmumby@xtra.co.nz wrote: > I am unable to build ports as I am getting the error message =E2=80=93 > Ports Collection support for your FreeBSD version has ended, and no por= ts are > guaranteed to build on this system. Please upgrade to a supported relea= se. >=20 > But my version is=20 > FreeBSD rpi2 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r293851: Fri Jan 22 2= 2:09:32 NZDT 2016 mark@raspberryPI:/usr/home/mark/crochet-master/work= /obj/arm.armv6/usr/src/sys/RPI2 arm Yes, 11.0-CURRENT is no longer supported. 11.0-RELEASE is what is now supported. Your freebsd-update command is failing because the freebsd update servers don't understand '11.0-CURRENT' as a known release -- this was a development version before 11.0-RELEASE came out. Your best choices are either to grab some install media from the FTP sites and install a new 11.0-RELEASE system, or to use svn or similar to grab up-to-date sources and build yourself a newer system. Almost certainly the former given you have a rpi2. Cheers, Matthew --vBuD2hsTabVOwkOoNnL1bMvsX394CqpOB-- --OQ0IL37ixAtef11aE7H0dqXiSBCl4WCt5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJY7/ElXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATr40QAInsSeiYHtD7w+od3pkBQxMW t7LcV7MURDL0CzRtn+dmWXfW714D0AtGCQhMtTPcSJGSTU4Y+cS2bFuLZJU7phMg wBlH35bC9QS59mmwPprB+YW+hnFbYGsyqIGBVfM9WAeatpOcn+Xgm68jR+SrjT5U 7Y+B++45sfBozfZFzQMFEFw353thtEuel5vEOZK/dFGuwY/w8LAK4wC1NGu3/UL5 wj5VZ58GGQ/qUb6KqyJNrN5XIVpc5W81/l/hJYI8Xr0C14twI92+SRQhRr2A7yYK 3o3JUkVuAIrP7zVEQyCbhyQ79sO39PE33yjdkDOkJM+BZlGbcVO2O5Jh7QBd3lWJ BNNMKD3p8At2FSUIKFQ4ATc4J6oUHfZPZfAo52PwqfeM9N4Z17q+1IGomsJp2s/1 a66wy2AGhCr4V9RJBxc0TLMof/gz+j29BCOs+aXBF/fzduxzgjKD0boFkmQJOrLA /6JUspUOOyqxil7Q0213S/jwYhXpzU5ndKv3mD9C1wa9iPLjTtTcK82WKW+gdjj/ 5oZd1pLoUN9oI8zg1ZX4WdPvEHJIWCVbmu8GqGSUVK4uH1qOnNjxmml9FUfcxQys RNF01drtqQ/6f6gjKLO6iWelWkzXfV7tWMK+WQg8fECERLDjzyYPQPDl1hGYfmuU J7IcEw3X9+hH84au+Fev =/A9e -----END PGP SIGNATURE----- --OQ0IL37ixAtef11aE7H0dqXiSBCl4WCt5-- From owner-freebsd-current@freebsd.org Fri Apr 14 13:47:40 2017 Return-Path: Delivered-To: freebsd-current@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 67499D3DD2E for ; Fri, 14 Apr 2017 13:47:40 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::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 38D94AEE for ; Fri, 14 Apr 2017 13:47:40 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x22f.google.com with SMTP id k87so90749237ioi.0 for ; Fri, 14 Apr 2017 06:47:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=Hi8qkINTqO5xzMeVdN6zeQWcrLtq2sYTfGqm/SCBB14=; b=gJk6XpaeO9/97aSCXg5WMuxH7usOcuXPo3ETLISee0YiC5m8N8vXUlaXAkMNYIuYxm +2hA/tV8EIQcjY7JijYGTzQuKzMSK5+VNQImMLkHEw3qu/BRu2LgakrIOcBJXO22e+sF kIRSgt//o/uuQATlBKSYSLGF0V02QaOfWMg+dPlqWFta9JSurR7a1QcxCkKPGt2I+41I QEwlp/bkgwRsFvGnHSIyKtPenFHIcC8zT+AfUSLE0RwJOFrOY7PPHALo0BEd9mVjQOb1 g28TLFhiclT0Yf60pocARmi+GmfNCD5FePunr7hgxP0QxC1GVf/ETurlzt0+jYlg19Eq 3x+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=Hi8qkINTqO5xzMeVdN6zeQWcrLtq2sYTfGqm/SCBB14=; b=IRV0yZyAIrnSSnPmJlcuZMPECa/QzupLAFIT98yVqlXWLaMsuKKpOaEzgpbE0jfDf/ qib55c9KzhbGl6MyKdERTYUPWsQPwPuH/DBu40GimIfdELU6o47wm0n5qPkQiQeqXS/T /u+6DPUR3QqIS7Xq72677my2htbvuNN2pAcTSHwD0E2L+JclOsIbHyuNAgyWqx1U78hY 46W2XvXRNTetQ1V9fNrvb/HCEA/amysivK5PpQC/qJwJ1p+Ed3HhZ9TF2rPl3in7oTLz pp/sOeJc4uswjfgpmWzpuglGWByZy3iuAXTFLURGjpEyWwUOLmFAO2LzgX6o6SptU3NV 1MuQ== X-Gm-Message-State: AN3rC/5JbTZTMvrSeYCDphlM3f16mxM5DgKnABvw5jIpYO38Au1ymkxa 1O/M8okAfDVpy2Bx X-Received: by 10.107.12.167 with SMTP id 39mr10901075iom.28.1492177659491; Fri, 14 Apr 2017 06:47:39 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-88-57.neo.res.rr.com. [74.141.88.57]) by smtp.googlemail.com with ESMTPSA id p70sm816345itg.0.2017.04.14.06.47.38 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 14 Apr 2017 06:47:39 -0700 (PDT) Message-ID: <58F0D301.7000509@gmail.com> Date: Fri, 14 Apr 2017 09:47:45 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: FreeBSD current Subject: csh script help Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 13:47:40 -0000 To aid in debugging the script I'm writing, I place "echo" commands throughout so I can kind of have a trace of the logic as different conditions are processed. Normally I just delete these "echo" commands after I get the script working. But this time I want to try something different. I want to enable/disable the echo commands in mass. So in the beginning of the script I added these 2 lints. #trace="" # use to enable trace echo trace="#" # use to disable trace echo In front of each of the echo commands I added this, $trace echo "what ever." When I exec the script I get error message #: not found What is happing here? Is the substitution to late? Is there a way to fix this? Thanks for your help From owner-freebsd-current@freebsd.org Fri Apr 14 14:08:43 2017 Return-Path: Delivered-To: freebsd-current@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 41085D3D5A1 for ; Fri, 14 Apr 2017 14:08:43 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout04.t-online.de (mailout04.t-online.de [194.25.134.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0689BB96 for ; Fri, 14 Apr 2017 14:08:42 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd38.aul.t-online.de (fwd38.aul.t-online.de [172.20.26.138]) by mailout04.t-online.de (Postfix) with SMTP id E1C4641BFB04; Fri, 14 Apr 2017 16:08:33 +0200 (CEST) Received: from Stefans-MBP.fritz.box (bppzj+ZXghb-Xn89e3Ffj7LuQHBev4StXdpYB8C4WOpi4vmMThP97h6F0D2F0FPZA-@[84.154.103.108]) by fwd38.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1cz1tp-1YY5fE0; Fri, 14 Apr 2017 16:08:33 +0200 Subject: Re: csh script help To: freebsd-current@freebsd.org References: <58F0D301.7000509@gmail.com> From: Stefan Esser Cc: luzar722@gmail.com Message-ID: <2b66121b-2bec-81fd-4281-7cf02dae7434@freebsd.org> Date: Fri, 14 Apr 2017 16:08:32 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <58F0D301.7000509@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ID: bppzj+ZXghb-Xn89e3Ffj7LuQHBev4StXdpYB8C4WOpi4vmMThP97h6F0D2F0FPZA- X-TOI-MSGID: ac4447a3-1cc2-4582-a815-ef024c0c0977 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 14:08:43 -0000 Am 14.04.17 um 15:47 schrieb Ernie Luzar: > To aid in debugging the script I'm writing, I place "echo" commands > throughout so I can kind of have a trace of the logic as different > conditions are processed. Normally I just delete these "echo" commands > after I get the script working. > > But this time I want to try something different. I want to > enable/disable the echo commands in mass. So in the beginning of the > script I added these 2 lints. > > #trace="" # use to enable trace echo > trace="#" # use to disable trace echo > > In front of each of the echo commands I added this, > $trace echo "what ever." > > When I exec the script I get error message #: not found This is to be expected ;-) > What is happing here? Is the substitution to late? No. > Is there a way to fix this? Use ":" instead of "#" to insert a "null command" before the echo: % set trace="" % $trace echo Hello Hello % set trace=":" % $trace echo Hello % Regards, STefan From owner-freebsd-current@freebsd.org Fri Apr 14 15:53:45 2017 Return-Path: Delivered-To: freebsd-current@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 8D80FD3D4AE for ; Fri, 14 Apr 2017 15:53:45 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 068301F4 for ; Fri, 14 Apr 2017 15:53:44 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.129.149]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lx4dh-1bxHrK1rHF-016jG3 for ; Fri, 14 Apr 2017 17:53:35 +0200 Date: Fri, 14 Apr 2017 17:53:28 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd) Message-ID: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/S9A5.IvWIx5joBFZB5EHxbg"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:slsS10sMk6MFJXOwtnaiJ9quDcGZxjPlT5KEbN7TLYiw9m6bApY KZklOVumwVCp634+PFFpbrY7wmqThZpyk9zVe9NPbsaGTw+F0hRjo+x6e2vaXQzU/kHaADz 6mMKsW+4Zg0N71sNidwmtSglOF1esBKNX6zrRaShhlny+SOYsFe2YaztJJCG8E698OT4R0O GN35Xc1E7iage64efztHQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:KiGmtXi9v0A=:hNJ2L9EDL8AqvJ+TU2z26X 0gOdyR3DjoSgOTXQ0P8Li/hI/Hq4bTGnNfLzoV0LXzgYIifBhdqIdSjFm3hy1MlLIcXiqJs4c jo/78pOSgUkuEhsPk5sQbun6BTY4k0Hpj1Mx+tSi/L5vi9cg8XsDUHi3a/3r0/qbF076AybXa ibNHXOOpKnugBDFPtqsY1TD/ZjpryKiT7dYyZa6vafQ/bBymDbvAygh3HZ0sBuRR/eopPmPJv YhumtMycFg9lby8ITuBFRweIberLBBz9feT5tlnmuCgPcNUsId30C05+lhlZQ78F1xVsYkd0F /VHq7kSEhsNBVVOyupIt7cJKWEqPTTHrcQEO1aVapasTc51K+qJCUEvrcQlXer3xHQYGc9kuC eBMwvMGzcVl83gOr4nU8CAHjAZbG3BPDRcIPPzaSOGzXE4SfUYcbhl76uQph/5FwztIwrTXmN K4wQpgsRHy/LqbvO/8MFaXfCMEmDHu700QpPKCTIupQoila6Eiasb3QYwHHsMYKm/x9ORwDlh qk8gqaFORztCAohkW64tdNpE3+7lhSeGOaBOBi+1urmFUDTNOiJdg3bm4PsPKormfLUq5LL57 pFJ9VUdw8Zf+QuUUJ6toXKVArd/LKnfr7e0rulDnI+FQEyTB8qeqvJAK65uP2tmLcSJeiyBfl s2LQs5QK0UDAh61xVBt8bduHMarYao7PpafFxPDIg6nzGOMi9sgg+2m25JYAffehsCPJ4SPGa 54dCvK19df9hkKbAlJgV5NbhtUjx8bdtwr6gEgK1jqwdPlvT2VZWa3w+7qU= X-Mailman-Approved-At: Fri, 14 Apr 2017 16:00:12 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 15:53:45 -0000 --Sig_/S9A5.IvWIx5joBFZB5EHxbg Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I just updated today CURRENT's tree sources for nanoBSD to r316844 and reco= mpiled an image I use for an PCengines APU 2C4. The APU now crashes with the error sh= own below. r316717 is all right and boots and works as expected. Just now, I depend on the box, so debugging kernel with more info is underw= ay, but in due time. Kind regards, Oliver [...] uhub2: on = usbus1 uhub2: 4 ports with 4 removable, self powered Link state changed to up igb0: link state changed to UP Link state changed to up igb1: link state changed to UP igb1.100: link state changed to UP igb1.2: link state changed to UP igb1.66: link state changed to UP igb1.111: link state changed to UP igb1.10: link state changed to UP tun0: link state changed to UP link state changed to down igb0: link state changed to DOWN Bump sched buckets to 64 (was 0) Link state changed to up Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0xfffff80012231600 fault code =3D supervisor read instruction, protection violati= on instruction pointer =3D 0x20:0xfffff80012231600 stack pointer =3D 0x28:0xfffffe012cdc1f58 frame pointer =3D 0x28:0xfffffe012cdc1fc0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 941 (syslogd) trap number =3D 12 panic: page fault cpuid =3D 1 time =3D 1492182471 Uptime: 16s PCEngines apu2 coreboot build 20160311 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/S9A5.IvWIx5joBFZB5EHxbg Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPDweAAKCRDS528fyFhY lNCeAf9Cp/fgLeS2A5dyCrrKtdbaaQgp04ywoataqrY6xS4eEGsDoD8Ia5KrWJ8v oFEdAb5krSF4bSmIH1PH1yfU9YF7Af9tBk2/nXbD4cRa2ddbFw9Zyyz8NN7F4obX 9t+SK0fa07FPAq3o1Y4Kv2JqDFTDM0HZ7ngaJcxUd1jrRGAVifcc =iFRZ -----END PGP SIGNATURE----- --Sig_/S9A5.IvWIx5joBFZB5EHxbg-- From owner-freebsd-current@freebsd.org Fri Apr 14 16:02:05 2017 Return-Path: Delivered-To: freebsd-current@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 D2493D3D96C for ; Fri, 14 Apr 2017 16:02:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002: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 91DD9C55 for ; Fri, 14 Apr 2017 16:02:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-yb0-x22d.google.com with SMTP id f204so19925782ybc.2 for ; Fri, 14 Apr 2017 09:02:05 -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=B/oYgBWanUHrloTKMRv8kGktoTx+CbfeXtWQNqCqW3k=; b=H8F8qbNGekEgskyQ4Nkng2Fr99nTwiqL05ez2XPuiToDudG/D3cr6ZXExl7V3Y9F9P B4HKFHn5DeMd4q9BIHmbJDKM+nMjpFHUd67HQPgtDfakL6B/QVoB8DGi6Npquy55+6lY ZrJ0An0wQ5vk+f0K4bYVpeEFKa1ssxLespespcBkqyA4etaGXIZZPuEjqmFz0FfEum6Y FytFMqVmFWfdufj/cZjOyZV+Bb4nB4AvZ8XfIbIxBfvNuN9QRhqx535yLTbjCEVvi4dF QdaXi5JX6tgp6wbg1lBoI+p4wzzfnvV7fN18691x/YRewVmFU7bi+Vnl0CpejsRqEUyk YszA== 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=B/oYgBWanUHrloTKMRv8kGktoTx+CbfeXtWQNqCqW3k=; b=HpAcmXKp4lFytjvYxen8Zhc10EcpJbUTW2erBj+JjNGkhAsJ45uaMNq3SYNQwULeOh LcZJDNpkYl+M+vHKlJ35Yj71uSwaXqnyzAjHVoLoKeijBeobZdR2SklEsGoYCDSqSps8 hVx6MWVrF+7+Cax1eiq1rQ8SmI6QcxemPRsTH9pXJ9lh0Kg23rD6n24BvEosIOV5Eeqa 35zC9B50cGt6lsWgPaBMY/22zMH9qelMbN1rq1bLY7gc4trVkL7kStwbzLFvfCSOenNA BUwToqLwmEIcFZDi2uEMihTniYaXM5Vz4td0HqPHvnoR+D2g4Kz7uBF5+ZckchFgTXkk 9Unw== X-Gm-Message-State: AN3rC/5nO062UmufBy5ND6Wmoapn/1nF3nBQqNvWuvZGBEExqUUOQQGC NtnRBKqI25zWj4mdXHYCPLSBFBruoQ== X-Received: by 10.37.171.193 with SMTP id v59mr5003013ybi.193.1492185724308; Fri, 14 Apr 2017 09:02:04 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.129.20.214 with HTTP; Fri, 14 Apr 2017 09:02:03 -0700 (PDT) In-Reply-To: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> References: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> From: Alan Somers Date: Fri, 14 Apr 2017 10:02:03 -0600 X-Google-Sender-Auth: qUn1riSEABrZvrCrKADEdEivhZQ Message-ID: Subject: Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd) To: "O. Hartmann" Cc: FreeBSD CURRENT Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 16:02:05 -0000 On Fri, Apr 14, 2017 at 9:53 AM, O. Hartmann wrote: > I just updated today CURRENT's tree sources for nanoBSD to r316844 and recompiled an > image I use for an PCengines APU 2C4. The APU now crashes with the error shown below. > > r316717 is all right and boots and works as expected. > > Just now, I depend on the box, so debugging kernel with more info is underway, but in due > time. > > Kind regards, > > Oliver > > [...] > uhub2: on usbus1 > uhub2: 4 ports with 4 removable, self powered > Link state changed to up > igb0: link state changed to UP > Link state changed to up > igb1: link state changed to UP > igb1.100: link state changed to UP > igb1.2: link state changed to UP > igb1.66: link state changed to UP > igb1.111: link state changed to UP > igb1.10: link state changed to UP > tun0: link state changed to UP > link state changed to down > igb0: link state changed to DOWN > Bump sched buckets to 64 (was 0) > Link state changed to up > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xfffff80012231600 > fault code = supervisor read instruction, protection violation > instruction pointer = 0x20:0xfffff80012231600 > stack pointer = 0x28:0xfffffe012cdc1f58 > frame pointer = 0x28:0xfffffe012cdc1fc0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 941 (syslogd) > trap number = 12 > panic: page fault > cpuid = 1 > time = 1492182471 > Uptime: 16s > PCEngines apu2 > coreboot build 20160311 At a minimum, you need to include a backtrace with a bug report like this. -Alan From owner-freebsd-current@freebsd.org Fri Apr 14 16:58:42 2017 Return-Path: Delivered-To: freebsd-current@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 1AEADD3EC4B for ; Fri, 14 Apr 2017 16:58:42 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88E8EE3F; Fri, 14 Apr 2017 16:58:40 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.225.0.75]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M4Gup-1c8tJ40vBr-00rrvU; Fri, 14 Apr 2017 18:58:33 +0200 Date: Fri, 14 Apr 2017 18:58:27 +0200 From: "O. Hartmann" To: Alan Somers Cc: FreeBSD CURRENT Subject: Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd) Message-ID: <20170414185827.1ab68398@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/CXaekI.U9YSFnFWM1jqm6cC"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:UcnnqhTBztHsPNJO8Og00uvusvpmeQtHZVMSzVbMvGNQup8QahV lwElfs4ExaqxT+nkOF2A2xQJprBS6H/LtAGxxfjVFsbqHOqhZcBz7jh2qVDZ+mWqNemyESy JpypEZdcBSDwjzY21l0qYDeUyHf/0ZTspnAVhZvZa7nOgWSRoq/Xiq82+Npe+7uQuB/zwpe Rmg/kWxXQ+0fnN4cthc4A== X-UI-Out-Filterresults: notjunk:1;V01:K0:PHA/PhIYrTc=:yKfkt5Bq4cMdnIfMSn3cDp g/820GoUAYc+N+53O2hh4eBBVYR8Wued3zCy/Lclst/WwYyYgxi7EV5+3cXi17ckUdBZD33r9 8Zu+urgW9wfWbZ+EKoLi25qnqTcRmVVZQZTOrNEqzH2/fYAFimcigmyXUg9qK02NNSW7qf2lj JbqJqY741RdTNKsLrWL1zI5GLjS8N3tPTFgiCcnQO0XEQKFUoqGjwy4S9lUJ45KZWAKdxH0MW FSSQlpnoIPCBl+BA7MktqXIro6dyV5ydW51OmDBe26lYVtLyLNV+uOmbB8UHBwT+ZXALYGeWw Bcu8XkoEDdCWMBJG/0BpsKSxVRuwOVJvOapnkKnUtryv2hHMDKa3JIEg2QrXHx4daFSMFfEZx XDxOo5936xpmyw+NsdcZwgFgGOV74TCuXCe95n13xPxZm1/zpxaEYLYjj3mLEpYtH1LnwXB9k UvdIdzzw4HLRl6N0964LMkYdCaBzXqOM0BBCHh68c9WCBNunLR+49Hc4RyjawG6CAjr+Zycou REvD4rwAGt3Sg62EwofZfZ8B4eKIs9/LVD2tZru4LIM/DDJBuGVYVYBaDgr81mdF9sAfrOAzW 7K7xi57Tq9eWqFVo2a/lnw7IHOQhJS3OdlOFd4IB6syaJ+vOrU7/bQHU2KGBRBgAQXmFn7BRY Mvl26iiw9HjRLISlE+rnvggAnwR5Yj+vCtMlPBKeeH579lewPMkVcObi2x1JLoU1nCmfkPHA1 U/RLqyCGFc3QVm13fmQ/xDH2lyDTvGm55TYj3K2etcD/XpjXET/ztnBZtB4= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 16:58:42 -0000 --Sig_/CXaekI.U9YSFnFWM1jqm6cC Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Fri, 14 Apr 2017 10:02:03 -0600 Alan Somers schrieb: > On Fri, Apr 14, 2017 at 9:53 AM, O. Hartmann wr= ote: > > I just updated today CURRENT's tree sources for nanoBSD to r316844 and = recompiled an > > image I use for an PCengines APU 2C4. The APU now crashes with the erro= r shown below. > > > > r316717 is all right and boots and works as expected. > > > > Just now, I depend on the box, so debugging kernel with more info is un= derway, but in > > due time. > > > > Kind regards, > > > > Oliver > > > > [...] > > uhub2: = on usbus1 > > uhub2: 4 ports with 4 removable, self powered > > Link state changed to up > > igb0: link state changed to UP > > Link state changed to up > > igb1: link state changed to UP > > igb1.100: link state changed to UP > > igb1.2: link state changed to UP > > igb1.66: link state changed to UP > > igb1.111: link state changed to UP > > igb1.10: link state changed to UP > > tun0: link state changed to UP > > link state changed to down > > igb0: link state changed to DOWN > > Bump sched buckets to 64 (was 0) > > Link state changed to up > > > > > > Fatal trap 12: page fault while in kernel mode > > cpuid =3D 0; apic id =3D 00 > > fault virtual address =3D 0xfffff80012231600 > > fault code =3D supervisor read instruction, protection vio= lation > > instruction pointer =3D 0x20:0xfffff80012231600 > > stack pointer =3D 0x28:0xfffffe012cdc1f58 > > frame pointer =3D 0x28:0xfffffe012cdc1fc0 > > code segment =3D base 0x0, limit 0xfffff, type 0x1b > > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > > current process =3D 941 (syslogd) > > trap number =3D 12 > > panic: page fault > > cpuid =3D 1 > > time =3D 1492182471 > > Uptime: 16s > > PCEngines apu2 > > coreboot build 20160311 =20 >=20 > At a minimum, you need to include a backtrace with a bug report like this. >=20 > -Alan Just sent a PR: Bug 218663 and added the backtrace as required: [...] Link state changed to up Kernel page fault with the following non-sleepable locks held: shared rw bpf interface lock (bpf interface lock) r =3D 0 (0xfffff80002ff40= 28) locked @ /pool/sources/CURRENT/src/sys/net/bpf.c:2206 shared rw udpinp (udpinp) r = =3D 0 (0xfffff800127f5c98) locked @ /pool/sources/CURRENT/src/sys/netinet/udp_usr= req.c:1140 stack backtrace: #0 0xffffffff80641960 at witness_debugger+0x70 #1 0xffffffff80642d8e at witness_warn+0x45e #2 0xffffffff8096f563 at trap_pfault+0x53 #3 0xffffffff8096ed5e at trap+0x24e #4 0xffffffff80952ce3 at calltrap+0x8 #5 0xffffffff806fc253 at iflib_txq_drain+0x1383 #6 0xffffffff806feda0 at drain_ring_lockless+0xc0 #7 0xffffffff806feb6e at ifmp_ring_enqueue+0x32e #8 0xffffffff806fda90 at iflib_if_transmit+0xb0 #9 0xffffffff806dfb00 at ether_output+0x730 #10 0xffffffff80761ae6 at arprequest+0x426 #11 0xffffffff80761f41 at arpresolve_full+0x3d1 #12 0xffffffff807621ac at arpresolve+0x10c #13 0xffffffff806df8b1 at ether_output+0x4e1 #14 0xffffffff80785c36 at ip_output+0x14e6 #15 0xffffffff8080ddd1 at udp_send+0xab1 #16 0xffffffff80676c44 at sosend_dgram+0x3e4 #17 0xffffffff8067d3a9 at kern_sendit+0x229 Fatal trap 12: page fault while in kernel mode cpuid =3D 2; apic id =3D 02 fault virtual address =3D 0xfffff8001282fb00 fault code =3D supervisor read instruction, protection violati= on instruction pointer =3D 0x20:0xfffff8001282fb00 stack pointer =3D 0x28:0xfffffe012d2aef48 frame pointer =3D 0x28:0xfffffe012d2aefb0 code segment =3D base rx0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 941 (syslogd) [ thread pid 941 tid 100084 ] Stopped at 0xfffff8001282fb00 db> bt Tracing pid 941 tid 100084 td 0xfffff80004520000 ??() at 0xfffff8001282fb00 bpf_mtap() at bpf_mtap+0x1ab/frame 0xfffffe012d2aefb0 iflib_txq_drain() at iflib_txq_drain+0x1383/frame 0xfffffe012d2af130 drain_ring_lockless() at drain_ring_lockless+0xc0/frame 0xfffffe012d2af190 ifmp_ring_enqueue() at ifmp_ring_enqueue+0x32e/frame 0xfffffe012d2af200 iflib_if_transmit() at iflib_if_transmit+0xb0/frame 0xfffffe012d2af240 ether_output() at ether_output+0x730/frame 0xfffffe012d2af2e0 arprequest() at arprequest+0x426/frame 0xfffffe012d2af3e0 arpresolve_full() at arpresolve_full+0x3d1/frame 0xfffffe012d2af460 arpresolve() at arpresolve+0x10c/frame 0xfffffe012d2af4d0 ether_output() at ether_output+0x4e1/frame 0xfffffe012d2af570 ip_output() at ip_output+0x14e6/frame 0xfffffe012d2af6b0 udp_send() at udp_send+0xab1/frame 0xfffffe012d2af780 sosend_dgram() at sosend_dgram+0x3e4/frame 0xfffffe012d2af7f0 kern_sendit() at kern_sendit+0x229/frame 0xfffffe012d2af890 sendit() at sendit+0x1a7/frame 0xfffffe012d2af8e0 sys_sendto() at sys_sendto+0x4d/frame 0xfffffe012d2af930 amd64_syscall() at amd64_syscall+0x4c2/frame 0xfffffe012d2afab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012d2afab0 syscall (133, FreeBSD ELF64, sys_sendto), rip =3D 0x800b8a5fa, rsp =3D 0x7f= ffffffd6b8, rbp =3D 0x7fffffffdcc0 --- --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/CXaekI.U9YSFnFWM1jqm6cC Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPD/swAKCRDS528fyFhY lBGUAf0bsNI9FE6wgFfSSVLuHG7hbwzy9SJ9ZHwwYE9yHBFNUDxXJN1UPjBJ9nD8 C6l9Jbb8wqJetJvwXLJFd/SrEvvkAf4rPuZc1sZ2mt2KgeJ8T0mPQtbj+FSCID3W JNoi7ripcHm04AIyTQFVHAbWQxrcYD2hWrn/Hl4Pai3rLlwaPBn/ =KLgQ -----END PGP SIGNATURE----- --Sig_/CXaekI.U9YSFnFWM1jqm6cC-- From owner-freebsd-current@freebsd.org Fri Apr 14 17:03:15 2017 Return-Path: Delivered-To: freebsd-current@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 115D1D3D05C for ; Fri, 14 Apr 2017 17:03:15 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-in6.apple.com (mail-out6.apple.com [17.151.62.28]) (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 E92EDB01 for ; Fri, 14 Apr 2017 17:03:14 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay3.apple.com (relay3.apple.com [17.128.113.83]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in6.apple.com (Apple Secure Mail Relay) with SMTP id 90.F4.04732.CC001F85; Fri, 14 Apr 2017 10:03:08 -0700 (PDT) X-AuditID: 11973e15-7c68a9a00000127c-fd-58f100cce50b Received: from [17.150.219.72] (Unknown_Domain [17.150.219.72]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id 5F.82.22697.CC001F85; Fri, 14 Apr 2017 10:03:08 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: csh script help From: Chuck Swiger In-Reply-To: <58F0D301.7000509@gmail.com> Date: Fri, 14 Apr 2017 10:03:07 -0700 Cc: FreeBSD current Content-Transfer-Encoding: quoted-printable Message-Id: <9A420780-8DEB-4FBA-9CDE-A9E152110E38@mac.com> References: <58F0D301.7000509@gmail.com> To: Ernie Luzar X-Mailer: Apple Mail (2.3273) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrILMWRmVeSWpSXmKPExsUi2FAYrHuG4WOEwaxpvBZz3nxgsrh+ehK7 A5PHjE/zWTx2zrrLHsAUxWWTkpqTWZZapG+XwJVxsrmRsWAPS8X63e2MDYxHmLsYOTkkBEwk GqY0s3YxcnEICaxmkrj9oAMusWryFXaIxDwmiftNt9hBEswCWhI3/r1k6mLk4OAV0Jfofc4I EhYWkJGY3rcerIRNQEVi8az/YHM4BTQljh+9AVbDIqAqMfXLd6gxhhK3D/SyQdjaEssWvgar 5xWwkvg7dx9YXEhAQ6KtGSIuAjRz85anbBC3yUrcmn0J6s6nrBKtr/MnMArOQnLdLITrZiHZ sICReRWjUG5iZo5uZp6ZXmJBQU6qXnJ+7iZGUJhOtxPdwXhmldUhRgEORiUe3oqjHyKEWBPL iitzDzFKc7AoifO2T3kXISSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoFRW/zy3M9iwR3L3186 cEr8nuGn0qmsj5WU/7qc5tnG2RsUld9y58+H94y/bB4+X9WS+3r9Qo/VG2omHZr+atmsYhaW C57SHZNWeGj2bYzWnXaKZ+e0nxwdXeesbSbcvPXzpkLESX0er5ftjpEvN9+8f5+zn1Xdp9LU w/u4WvyvbUe7svSbzbYvV2Ipzkg01GIuKk4EANMoTA40AgAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKLMWRmVeSWpSXmKPExsUiOO22h+4Zho8RBnufcFnMefOByeL66Uns DkweMz7NZ/HYOesuewBTFJdNSmpOZllqkb5dAlfGyeZGxoI9LBXrd7czNjAeYe5i5OSQEDCR WDX5CnsXIxeHkMA8Jon7TbfYQRLMAloSN/69ZOpi5ODgFdCX6H3OCBIWFpCRmN63HqyETUBF YvGs/2BzOAU0JY4fvQFWwyKgKjH1y3eoMYYStw/0skHY2hLLFr4Gq+cVsJL4O3cfWFxIQEOi rRkiLgI0c/OWp2wQt8lK3Jp9iXkCI98sJBfNQrhoFpKpCxiZVzEKFKXmJFYa6yUWFOSk6iXn 525iBAVWQ2HwDsY/y6wOMQpwMCrx8F44/iFCiDWxrLgy9xCjBAezkgjvpH9AId6UxMqq1KL8 +KLSnNTiQ4zSHCxK4rz9u4FSAumJJanZqakFqUUwWSYOTqkGRsn0Z4su3lbIlq65O5fV32JR 1ZLZB8/4eZd5dqxvemKpcudUJPuW6/u7Xx7LzKli+8exWnzTkYO9Pk97FIperFK+lhm0mnN+ b1H7gr9vT75YevPs0ftJNy9N7C5d/XR6MKNHyZW5p2w/qkQkrcq94TTn/azAUuFv2c7fPG8Z N6/O5IrsfpTXu1yJpTgj0VCLuag4EQD9uOd0KAIAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 17:03:15 -0000 On Apr 14, 2017, at 6:47 AM, Ernie Luzar wrote: > To aid in debugging the script I'm writing, I place "echo" commands = throughout so I can kind of have a trace of the logic as different = conditions are processed. Normally I just delete these "echo" commands = after I get the script working. Since you've gotten an answer to the question you asked, let me only = note that both sh and csh support the -x flag, which causes the shell to = echo the commands as it runs. This is extremely helpful for debugging. Regards, --=20 -Chuck From owner-freebsd-current@freebsd.org Fri Apr 14 17:19:03 2017 Return-Path: Delivered-To: freebsd-current@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 46597D3E0FA for ; Fri, 14 Apr 2017 17:19:03 +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 B048C8C6; Fri, 14 Apr 2017 17:19:02 +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 v3EHIvGM004553 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 14 Apr 2017 20:18:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v3EHIvGM004553 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v3EHIvdh004552; Fri, 14 Apr 2017 20:18:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 14 Apr 2017 20:18:57 +0300 From: Konstantin Belousov To: "O. Hartmann" Cc: Alan Somers , FreeBSD CURRENT Subject: Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd) Message-ID: <20170414171857.GK1788@kib.kiev.ua> References: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> <20170414185827.1ab68398@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170414185827.1ab68398@thor.intern.walstatt.dynvpn.de> User-Agent: Mutt/1.8.0 (2017-02-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-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 17:19:03 -0000 On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 02 > fault virtual address = 0xfffff8001282fb00 > fault code = supervisor read instruction, protection violation > ??() at 0xfffff8001282fb00 > bpf_mtap() at bpf_mtap+0x1ab/frame 0xfffffe012d2aefb0 > iflib_txq_drain() at iflib_txq_drain+0x1383/frame 0xfffffe012d2af130 > drain_ring_lockless() at drain_ring_lockless+0xc0/frame 0xfffffe012d2af190 > ifmp_ring_enqueue() at ifmp_ring_enqueue+0x32e/frame 0xfffffe012d2af200 > iflib_if_transmit() at iflib_if_transmit+0xb0/frame 0xfffffe012d2af240 > ether_output() at ether_output+0x730/frame 0xfffffe012d2af2e0 > arprequest() at arprequest+0x426/frame 0xfffffe012d2af3e0 > arpresolve_full() at arpresolve_full+0x3d1/frame 0xfffffe012d2af460 > arpresolve() at arpresolve+0x10c/frame 0xfffffe012d2af4d0 > ether_output() at ether_output+0x4e1/frame 0xfffffe012d2af570 > ip_output() at ip_output+0x14e6/frame 0xfffffe012d2af6b0 > udp_send() at udp_send+0xab1/frame 0xfffffe012d2af780 > sosend_dgram() at sosend_dgram+0x3e4/frame 0xfffffe012d2af7f0 > kern_sendit() at kern_sendit+0x229/frame 0xfffffe012d2af890 > sendit() at sendit+0x1a7/frame 0xfffffe012d2af8e0 > sys_sendto() at sys_sendto+0x4d/frame 0xfffffe012d2af930 > amd64_syscall() at amd64_syscall+0x4c2/frame 0xfffffe012d2afab0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012d2afab0 > syscall (133, FreeBSD ELF64, sys_sendto), rip = 0x800b8a5fa, rsp = 0x7fffffffd6b8, > rbp = 0x7fffffffdcc0 --- You probably have BPF_JITTER option in your kernel config. Either set net.bpf_jitter.enable to 0 for now, or remove the option. It is due to r316767. The issue is known and a solution is being discussed. From owner-freebsd-current@freebsd.org Fri Apr 14 17:31:30 2017 Return-Path: Delivered-To: freebsd-current@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 A36B5D3E711 for ; Fri, 14 Apr 2017 17:31:30 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1826CAE7; Fri, 14 Apr 2017 17:31:29 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.225.0.75]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M3AWN-1c9rFx3ig3-00szfM; Fri, 14 Apr 2017 19:31:27 +0200 Date: Fri, 14 Apr 2017 19:31:20 +0200 From: "O. Hartmann" To: Konstantin Belousov Cc: "O. Hartmann" , Alan Somers , FreeBSD CURRENT Subject: Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd) Message-ID: <20170414193120.2f99e58d@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170414171857.GK1788@kib.kiev.ua> References: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> <20170414185827.1ab68398@thor.intern.walstatt.dynvpn.de> <20170414171857.GK1788@kib.kiev.ua> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/N2i=UqM0mEacQLLRd1y0CuS"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:ncHunRu7vfOfZt2Mq+RnPE8xXu0/rUj3ykcJttbMjQYQ538ikAj 7uzMbZC61PhME5ad9El8y6k/wO82jssQsM15QghOOpaKzzUdTzJCbAnSzl4h2wbE71HzgUU hpBRp8cwdYPBolslIA5VLbgQIhIqJyOR0ELOiFlAqqu2kZ5Hc0uUXshaezR2eaaB+39VERP 0s4igARWujmru3V1JU0Sg== X-UI-Out-Filterresults: notjunk:1;V01:K0:auEzEn/KPwI=:DL/v9teLvHv/UmYNCYMVj0 4iRhOSjXAoOPGA8/XxZCaOTjhTrqpShYwCsMltCyQ9wWxxoMaoLmk3jaOnFGql9vpVKcNjP6X l1pMkpb8TY8r+Nxy4is7axH/lWL2rCaWPG1KMp1GvJyHgyLzcygCEgkjJNUXf1ozj1D3HV53n 9CE1z/HrjMsNALoGrWuLjsaVUyXCBZsE990RDC4Wf2nvgifL51kYZZWe4R+RqIaYE06PVJHw5 AR1kqS6Ha3reD6rnkkFYrNAxcXfE0Iw+dU+oEzCKTzCGMGZgB7yWMWMV88J9HPSyBczaF4Msl iTdRLeBPoG7x85mOnPN0RkWAq0fcfMGUvobZ57+5esM/Risg+N/QG845GW7gbKkcxxfpI48lc NryTsQ/HEzBsd2KqMhU5l/FaDOJmY3LRg8R548IqsIiKTEOHzNYTw42Wwsq1R4dn5PGdxaxUO jAjkjRzxVOZjPKycAGt0crPZnsCQRJjnpBhHwg3zlgL1ZJsrMunE9IfkwBlbfQDv32S8VKFuN aU39IhiLDWk2qQc2QSoZRPeb+q9Cy7m8t3M9ueN3l40vb7DNpnZ3uKnl7LOO+CfkfGkUYJezl 7GaOJAOEJXR03caEuukX/9/6DpFawpFDvk6MbmciTd8TJboDPciGU/2iZ9+X/qC/C/k1QoccJ bI0aviGcqeyLc45k23djSFKU6JK+DcZ/zI9FUcrl8wMi+zRkNIp68j6WIGA0f+RfEmLUC52mc Ctqh1QTaOxx5BsIygrKxJs5BAnfLg44nD0hHjE2gwUhOpwjU7TBol8nOcNw= X-Mailman-Approved-At: Fri, 14 Apr 2017 18:01:57 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 17:31:30 -0000 --Sig_/N2i=UqM0mEacQLLRd1y0CuS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Fri, 14 Apr 2017 20:18:57 +0300 Konstantin Belousov schrieb: > On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: > > Fatal trap 12: page fault while in kernel mode > > cpuid =3D 2; apic id =3D 02 > > fault virtual address =3D 0xfffff8001282fb00 > > fault code =3D supervisor read instruction, protection vio= lation =20 >=20 > > ??() at 0xfffff8001282fb00 > > bpf_mtap() at bpf_mtap+0x1ab/frame 0xfffffe012d2aefb0 > > iflib_txq_drain() at iflib_txq_drain+0x1383/frame 0xfffffe012d2af130 > > drain_ring_lockless() at drain_ring_lockless+0xc0/frame 0xfffffe012d2af= 190 > > ifmp_ring_enqueue() at ifmp_ring_enqueue+0x32e/frame 0xfffffe012d2af200 > > iflib_if_transmit() at iflib_if_transmit+0xb0/frame 0xfffffe012d2af240 > > ether_output() at ether_output+0x730/frame 0xfffffe012d2af2e0 > > arprequest() at arprequest+0x426/frame 0xfffffe012d2af3e0 > > arpresolve_full() at arpresolve_full+0x3d1/frame 0xfffffe012d2af460 > > arpresolve() at arpresolve+0x10c/frame 0xfffffe012d2af4d0 > > ether_output() at ether_output+0x4e1/frame 0xfffffe012d2af570 > > ip_output() at ip_output+0x14e6/frame 0xfffffe012d2af6b0 > > udp_send() at udp_send+0xab1/frame 0xfffffe012d2af780 > > sosend_dgram() at sosend_dgram+0x3e4/frame 0xfffffe012d2af7f0 > > kern_sendit() at kern_sendit+0x229/frame 0xfffffe012d2af890 > > sendit() at sendit+0x1a7/frame 0xfffffe012d2af8e0 > > sys_sendto() at sys_sendto+0x4d/frame 0xfffffe012d2af930 > > amd64_syscall() at amd64_syscall+0x4c2/frame 0xfffffe012d2afab0 > > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012d2afab0 > > syscall (133, FreeBSD ELF64, sys_sendto), rip =3D 0x800b8a5fa, rsp =3D = 0x7fffffffd6b8, > > rbp =3D 0x7fffffffdcc0 --- =20 >=20 > You probably have BPF_JITTER option in your kernel config. Either set > net.bpf_jitter.enable to 0 for now, or remove the option. >=20 > It is due to r316767. The issue is known and a solution is being discusse= d. Thank you very much. Indeed, I have. Regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/N2i=UqM0mEacQLLRd1y0CuS Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPEHaAAKCRDS528fyFhY lJfGAf4msNBcjA+bJLRgeile4TOB2kD9YNzaCSx9Tx2jtx/h/e3oEVycLhbsCF7k +00TRemY1XW/tJA3HvaC4N31nd3kAf9zkDity53bDyvfW5pMP0To0R7AwrS9s3fn RMFYbfyuRDAWr62/sIFBst4Q8CC2rlRPjafWA2hdCLsO6xeHPtw7 =iTnK -----END PGP SIGNATURE----- --Sig_/N2i=UqM0mEacQLLRd1y0CuS-- From owner-freebsd-current@freebsd.org Fri Apr 14 18:31:52 2017 Return-Path: Delivered-To: freebsd-current@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 52956D3E619 for ; Fri, 14 Apr 2017 18:31:52 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::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 1A592D19 for ; Fri, 14 Apr 2017 18:31:52 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id 70so6562756ita.0 for ; Fri, 14 Apr 2017 11:31:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=bTZ1YPK2x7THAXKVcHVBO+vz1OcQp2Os1++EiYZ/fE4=; b=CxIzYQsgVh8w4OFJe4z9mVQHYZBQrHrZt4oCA7P/n9DaWizPo9k3ff9OnpkyvjfQ8Z fzLUbudmqOikTJq3PelQlMHmtkkFBexYMkLSW2V8SbKJLnpeuPgmS8hqU+irfkoGR78a aFsfWX4UOsW1SgR54N5Th/hzcudyoCFHyNOeAJrd0bEZFqOfmmFrtf9haIllfyY0VIRG V7b0E3x3caHYDTA3lYY1VWGa1W8kBwD6gkjWcswpBtJTT3YlZWxy6nRV6veAdXl1u9lc u7iDzCCwW8B0m4963t/Ad1J43BfB48OAK9hoRKwEMVPrT80VWsoZY6i7u9xOEGb3sfLb SYTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=bTZ1YPK2x7THAXKVcHVBO+vz1OcQp2Os1++EiYZ/fE4=; b=DHxCNHPgvkJqsTVtGuQqlkSNuWLx61PGjrWlCKM3Fp+Vcq02jrosJwoqK+FwXyzWzx H4AN6G08y3k7VAkPZJMDRQk9mThqJpcBp1T4R5ZzEAQ4lH/y2q27bTGgGxvW/2eJHaUm r0eJcxGu2l2Bu/fEPYGnewYcjpPc93sJ2lwZmOgDAV4ZeBks+WLVgrBJl1WC8lQRJMU/ BQ5AgUvOgNk3qUakCfvxwfngcu61yxZMrP1InuWilwrWYq3EJ+8FMBPnIYWdgO2HAFkj SkVzZLzYExU48JUYeMpuyF/X3Gc0JQ5WNxfJu3/l2+fbDyOcKrzOEY7fc6ApEzssGkFs 4nJw== X-Gm-Message-State: AN3rC/4i3RXimRpiIa6BwuXIw3R95fegtY0MSoQ4Un31dXKPAZZlvEuB 3scmB/gl54Cl6Q== X-Received: by 10.36.103.215 with SMTP id u206mr9302itc.6.1492194711435; Fri, 14 Apr 2017 11:31:51 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-88-57.neo.res.rr.com. [74.141.88.57]) by smtp.googlemail.com with ESMTPSA id z20sm1380827ioz.23.2017.04.14.11.31.50 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 14 Apr 2017 11:31:51 -0700 (PDT) Message-ID: <58F115A8.8010407@gmail.com> Date: Fri, 14 Apr 2017 14:32:08 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Chuck Swiger CC: FreeBSD current Subject: Re: csh script help References: <58F0D301.7000509@gmail.com> <9A420780-8DEB-4FBA-9CDE-A9E152110E38@mac.com> In-Reply-To: <9A420780-8DEB-4FBA-9CDE-A9E152110E38@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 18:31:52 -0000 Chuck Swiger wrote: > On Apr 14, 2017, at 6:47 AM, Ernie Luzar wrote: >> To aid in debugging the script I'm writing, I place "echo" commands throughout so I can kind of have a trace of the logic as different conditions are processed. Normally I just delete these "echo" commands after I get the script working. > > Since you've gotten an answer to the question you asked, let me only note that both sh and csh support the -x flag, which causes the shell to echo the commands as it runs. This is extremely helpful for debugging. > > Regards, Where is the this -x flag coded at? Do the executed lines roll fast off the screen or can I slowly step through the script a line at a time? Thanks for this bit of information. From owner-freebsd-current@freebsd.org Fri Apr 14 18:58:58 2017 Return-Path: Delivered-To: freebsd-current@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 A824FD3E3F1 for ; Fri, 14 Apr 2017 18:58:58 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-in24.apple.com (mail-out24.apple.com [17.171.2.34]) (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 6DDCFC93 for ; Fri, 14 Apr 2017 18:58:57 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay4.apple.com (relay4.apple.com [17.128.113.87]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in24.apple.com (Apple Secure Mail Relay) with SMTP id 42.06.22073.56811F85; Fri, 14 Apr 2017 11:43:49 -0700 (PDT) X-AuditID: 11ab0218-e3b909a000005639-38-58f11865a482 Received: from [17.150.219.72] (Unknown_Domain [17.150.219.72]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by relay4.apple.com (Apple SCV relay) with SMTP id 32.8F.13512.46811F85; Fri, 14 Apr 2017 11:43:48 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: csh script help From: Chuck Swiger In-Reply-To: <58F115A8.8010407@gmail.com> Date: Fri, 14 Apr 2017 11:43:47 -0700 Cc: FreeBSD current Content-Transfer-Encoding: quoted-printable Message-Id: <427BD3AE-6619-4E3A-BFE7-32882B46921D@mac.com> References: <58F0D301.7000509@gmail.com> <9A420780-8DEB-4FBA-9CDE-A9E152110E38@mac.com> <58F115A8.8010407@gmail.com> To: Ernie Luzar X-Mailer: Apple Mail (2.3273) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUi2FAYrpsq8THC4ESzrMWcNx+YLK6fnsTu wOQx49N8Fo+ds+6yBzBFcdmkpOZklqUW6dslcGWcvPSEtaCJu+Ljk7VsDYy3OLoYOTkkBEwk rm7qY+5i5OIQEljDJDHn61xmmMS5/etZIBLzgBLdrYwgCWYBLYkb/14ydTFycPAK6Ev0PgcL CwvISEzvW88OYrMJqEgsnvUfbA6ngKbEpkX3WEBsFgFViSV//7JBjDGUuH2gF8rWlli28DUz xEgriVmL3UHCQgJlEgd3rwEbIwI0cvOWp2wQp8lK3Jp9CexmCYGnrBI/O/+yTWAUnIXkulkI 181CsmEBI/MqRuHcxMwc3cw8IxO9xIKCnFS95PzcTYygQF3NJLGD8ctrw0OMAhyMSjy8FUc/ RAixJpYVV+YeYpTmYFES550x9V2EkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsbd88zaWLPD +7mKT98r0KmVPrb3qL1e+q1TT2RF/7fIGMw6tlhTiXFnBPvXgLz0tbOezPqm1RR3y3JxWxX3 1ccXZVUn3n69QMp0im9PkFSDVcnPHImE28fPTy8IttmenqZQcuJQ13KOPo0K3tgDp2NDcq1X P/plbjDb7tGp8EdLG2QXl3LeWaLEUpyRaKjFXFScCAAlTCrANQIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUiOO22h26KxMcIg7vbRC3mvPnAZHH99CR2 ByaPGZ/ms3jsnHWXPYApissmJTUnsyy1SN8ugSvj5KUnrAVN3BUfn6xla2C8xdHFyMkhIWAi cW7/epYuRi4OIYF5TBJzulsZQRLMAloSN/69ZOpi5ODgFdCX6H0OFhYWkJGY3reeHcRmE1CR WDzrPzOIzSmgKbFp0T0WEJtFQFViyd+/bBBjDCVuH+iFsrUlli18zQwx0kpi1mJ3kLCQQJnE wd1rwMaIAI3cvOUpG8RpshK3Zl9insDINwvJQbMQDpqFZOgCRuZVjAJFqTmJlSZ6iQUFOal6 yfm5mxhBYdVQGL6D8d8yq0OMAhyMSjy8FUc/RAixJpYVV+YeYpTgYFYS4U0S/BghxJuSWFmV WpQfX1Sak1p8iFGag0VJnLd/N1C1QHpiSWp2ampBahFMlomDU6qBcftsxfPzn2tkP7dmUvlu YxAiL8s+q3vJYQcNubYKwymGfFf4M2uWqXqxZqS/nul8b/q2bgM91TKvR9NTVz/coCXStuvJ wlU619f2+z54cv6cw/SzdnKptWtYZ///815WrPvanAc2O33sy5U2nxEri/k0YxFPi1m6T3Hq Hc6zd+7KesQ06t98o8RSnJFoqMVcVJwIAGqMgHMnAgAA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 18:58:58 -0000 Hi-- On Apr 14, 2017, at 11:32 AM, Ernie Luzar wrote: > Chuck Swiger wrote: >> On Apr 14, 2017, at 6:47 AM, Ernie Luzar wrote: >>> To aid in debugging the script I'm writing, I place "echo" commands = throughout so I can kind of have a trace of the logic as different = conditions are processed. Normally I just delete these "echo" commands = after I get the script working. >>=20 >> Since you've gotten an answer to the question you asked, let me only = note that both sh and csh support the -x flag, which causes the shell to = echo the commands as it runs. This is extremely helpful for debugging. >> Regards, >=20 > Where is the this -x flag coded at? Do the executed lines roll fast = off the screen or can I slowly step through the script a line at a time? >=20 > Thanks for this bit of information. You can either run the script via "/bin/sh -x myscript.sh" and similar = for csh, or you can add -x to the first line of the script, commonly "#! = /bin/sh" and invoke it directly via ./myscript.sh. The lines are displayed as rapidly as the shell runs. If running natively on FreeBSD, most people would use a terminal = emulator like xterm which provides scrollback. You could also run under = nohup, which will save output to a file named nohup.out, unless you = redirect output somewhere else. Regards, --=20 -Chuck From owner-freebsd-current@freebsd.org Fri Apr 14 19:06:22 2017 Return-Path: Delivered-To: freebsd-current@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 1CB30D3E957 for ; Fri, 14 Apr 2017 19:06:22 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3F426D6 for ; Fri, 14 Apr 2017 19:06:20 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cz6Xq-0004Dq-BG; Fri, 14 Apr 2017 21:06:12 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Adrian Chadd" Cc: freebsd-current Subject: Re: if_iwn dhcp troubles (solved) References: Date: Fri, 14 Apr 2017 21:06:08 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.5 X-Spam-Status: No, score=0.5 required=5.0 tests=ALL_TRUSTED, BAYES_60 autolearn=disabled version=3.4.0 X-Scan-Signature: dba824da175698ffceeb6951503097fc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 19:06:22 -0000 Since the latest iwn changes my laptop does pick up the network/dhcp settings immediately. No more DHCP trouble and 'fatal firmware error' problems anymore. Thanks and regards, Ronald. On Thu, 09 Jun 2016 14:43:32 +0200, Ronald Klop wrote: > Hello Adrian, > > See attachments. One is with and one is without -ht option. > > # 14:40:52 root@sjakie [~] > uname -a > FreeBSD sjakie.klop.ws 11.0-ALPHA1 FreeBSD 11.0-ALPHA1 #7 r300901M: Sat > May 28 16:54:00 CEST 2016 > root@sjakie.klop.ws:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 > > Regards, > Ronald. > > > > On Tue, 31 May 2016 02:38:38 +0200, Adrian Chadd > wrote: > >> hi, >> >> what's the output of 'ifconfig -v wlan0 list scan' ? >> >> >> -a >> >> >> On 30 May 2016 at 14:15, Ronald Klop wrote: >>> On Mon, 30 May 2016 03:01:10 +0200, Adrian Chadd >>> >>> wrote: >>> >>>> ok, so there seem to be more lingering 802.11n issues. can you tell me >>>> mrore about the environment there, so I can try to duplicate it? >>>> >>>> I'd like to fix whatever 11n issues there are in iwn! >>>> >>>> Thanks! >>>> >>>> >>>> -a >>> >>> >>> Hi Adrian, >>> >>> I don't know what you want to know, but it is just my laptop at home. I >>> installed an Intel WiFi card, because the Broadcom it had didn't have >>> support in FreeBSD. I normally have if_lagg configured, but disabled it >>> to >>> debug this. >>> I connect with WiFi to a Ubiquiti Unifi AP AC Lite >>> (https://www.ubnt.com/unifi/unifi-ap-ac-lite/). >>> Other (non-freebsd) devices, like a phone, connect happily with the >>> WiFi. >>> >>> >>> pciconf -vl: >>> ... >>> iwn0@pci0:4:0:0: class=0x028000 card=0x40608086 chip=0x088e8086 >>> rev=0x24 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Centrino Advanced-N 6235' >>> class = network >>> ... >>> ================= >>> cat /etc/wpa_supplicant.conf (really plain) >>> network={ >>> ssid="xxxxxxxxx" >>> psk="yyyyyyyy" >>> } >>> ================= >>> cat /etc/rc.conf: >>> # Kernel >>> zfs_enable="YES" >>> saver="green" >>> accounting_enable="YES" >>> powerd_enable="YES" >>> devfs_system_ruleset="system" >>> background_fsck="NO" >>> dumpdev="AUTO" >>> kld_list="coretemp ichsmb radeonkms fuse if_lagg vboxdrv cuse" >>> keymap="/etc/keymap.test" >>> # if_bwn bwn_v4_lp_ucode" >>> >>> # Networking >>> hostname="sjakie.klop.ws" >>> #wpa_supplicant_flags="$wpa_supplicant_flags -d" >>> wlans_iwn0="wlan0" >>> create_args_wlan0="wlanaddr 00:26:b9:12:40:a4 country NL" >>> ifconfig_wlan0="-ht WPA" >>> #ifconfig_bge0="up" >>> #cloned_interfaces="lagg0" >>> #ifconfig_lagg0="laggproto failover laggport bge0 laggport wlan0 >>> SYNCDHCP" >>> >>> ifconfig_wlan0="$ifconfig_wlan0 DHCP" >>> >>> #ifconfig_DEFAULT="SYNCDHCP" >>> #ifconfig_em0_alias0="inet 192.168.1.36 netmask 0xffffffff" >>> firewall_enable="YES" >>> firewall_type="/etc/ipfw.sjakie" >>> #local_unbound_enable="YES" >>> >>> # Daemons >>> ntpdate_enable="YES" >>> ntpd_enable="YES" >>> sshd_enable="YES" >>> inetd_enable="YES" >>> syslogd_flags="" >>> sendmail_enable="NO" >>> sendmail_submit_enable="NO" >>> sendmail_outbound_enable="NO" >>> sendmail_msp_queue_enable="NO" >>> >>> # Bluetooth >>> #hcsecd_enable="YES" >>> #sdpd_enable="YES" >>> #bthidd_enable="YES" >>> >>> # Ports >>> bsdstats_enable="YES" >>> #postfix_enable="YES" >>> #smtpd_enable="YES" >>> #smtpd_flags="-v" >>> cupsd_enable="YES" >>> dbus_enable="YES" >>> polkitd_enable="YES" >>> #hald_enable="YES" >>> smartd_enable="YES" >>> #mdnsd_enable="YES" >>> avahi_daemon_enable="YES" >>> bruteblockd_enable="YES" >>> bruteblockd_table="1" >>> bruteblockd_flags="-s 5" >>> #collectd_enable="YES" >>> >>> rpcbind_enable="YES" >>> #nfs_client_enable="YES" >>> mountd_enable="YES" >>> nfs_server_enable="YES" >>> >>> panicmail_enable="YES" >>> slim_enable="YES" >>> >>> webcamd_enable="YES" >>> webcamd_flags="-m v4l2-dev.v4l_hflip=1" >>> >>> >>> ============= >>> dmesg: >>> Copyright (c) 1992-2016 The FreeBSD Project. >>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, >>> 1994 >>> The Regents of the University of California. All rights >>> reserved. >>> FreeBSD is a registered trademark of The FreeBSD Foundation. >>> FreeBSD 11.0-ALPHA1 #7 r300901M: Sat May 28 16:54:00 CEST 2016 >>> root@sjakie.klop.ws:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 >>> FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on >>> LLVM >>> 3.8.0) >>> can't re-use a leaf (ixl_rx_miss_bufs)! >>> VT(vga): resolution 640x480 >>> CPU: Pentium(R) Dual-Core CPU T4300 @ 2.10GHz (2094.80-MHz >>> K8-class >>> CPU) >>> Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 >>> Stepping=10 >>> >>> Features=0xbfebfbff >>> >>> Features2=0xc00e39d >>> AMD Features=0x20100800 >>> AMD Features2=0x1 >>> TSC: P-state invariant, performance statistics >>> real memory = 4294967296 (4096 MB) >>> avail memory = 4047171584 (3859 MB) >>> Event timer "LAPIC" quality 400 >>> ACPI APIC Table: >>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>> random: unblocking device. >>> ioapic0 irqs 0-23 on motherboard >>> random: entropy device external interface >>> kbd1 at kbdmux0 >>> netmap: loaded module >>> module_register_init: MOD_LOAD (vesa, 0xffffffff80fe16e0, 0) error 19 >>> vtvga0: on motherboard >>> cryptosoft0: on motherboard >>> acpi0: on motherboard >>> acpi0: Power Button (fixed) >>> Timecounter "HPET" frequency 14318180 Hz quality 950 >>> Event timer "HPET" frequency 14318180 Hz quality 450 >>> Event timer "HPET1" frequency 14318180 Hz quality 440 >>> Event timer "HPET2" frequency 14318180 Hz quality 440 >>> Event timer "HPET3" frequency 14318180 Hz quality 440 >>> cpu0: on acpi0 >>> cpu1: on acpi0 >>> atrtc0: port 0x70-0x77 irq 8 on acpi0 >>> atrtc0: Warning: Couldn't map I/O. >>> Event timer "RTC" frequency 32768 Hz quality 0 >>> attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 >>> Timecounter "i8254" frequency 1193182 Hz quality 0 >>> Event timer "i8254" frequency 1193182 Hz quality 100 >>> Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 >>> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 >>> acpi_ec0: port 0x62,0x66 on acpi0 >>> pcib0: port 0xcf8-0xcff on acpi0 >>> pci0: on pcib0 >>> pcib1: irq 16 at device 1.0 on pci0 >>> pcib1: [GIANT-LOCKED] >>> pci1: on pcib1 >>> vgapci0: port 0x2000-0x20ff mem >>> 0xd0000000-0xdfffffff,0xfc000000-0xfc00ffff irq 16 at device 0.0 on >>> pci1 >>> vgapci0: Boot video device >>> hdac0: mem 0xfc010000-0xfc013fff irq 17 at >>> device >>> 0.1 on pci1 >>> uhci0: port 0x1800-0x181f irq 16 >>> at >>> device 26.0 on pci0 >>> usbus0 on uhci0 >>> uhci1: port 0x1820-0x183f irq 21 >>> at >>> device 26.1 on pci0 >>> usbus1 on uhci1 >>> uhci2: port 0x1840-0x185f irq 19 >>> at >>> device 26.2 on pci0 >>> usbus2 on uhci2 >>> ehci0: mem >>> 0xfc504800-0xfc504bff >>> irq 19 at device 26.7 on pci0 >>> usbus3: EHCI version 1.0 >>> usbus3 on ehci0 >>> hdac1: mem 0xfc500000-0xfc503fff irq 22 >>> at >>> device 27.0 on pci0 >>> pcib2: irq 17 at device 28.0 on pci0 >>> pcib2: [GIANT-LOCKED] >>> pcib3: irq 16 at device 28.1 on pci0 >>> pcib3: [GIANT-LOCKED] >>> pci2: on pcib3 >>> iwn0: mem 0xf8000000-0xf8001fff irq 17 >>> at >>> device 0.0 on pci2 >>> pcib4: irq 19 at device 28.3 on pci0 >>> pcib4: [GIANT-LOCKED] >>> pcib5: irq 16 at device 28.5 on pci0 >>> pcib5: [GIANT-LOCKED] >>> pci3: on pcib5 >>> bge0: >> 0x5784100> mem 0xfc100000-0xfc10ffff irq 17 at device 0.0 on pci3 >>> bge0: CHIP ID 0x05784100; ASIC REV 0x5784; CHIP REV 0x57841; PCI-E >>> miibus0: on bge0 >>> brgphy0: PHY 1 on miibus0 >>> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >>> 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow >>> bge0: Using defaults for TSO: 65518/35/2048 >>> bge0: Ethernet address: 00:26:b9:12:40:a4 >>> uhci3: port 0x1860-0x187f irq 23 >>> at >>> device 29.0 on pci0 >>> usbus4 on uhci3 >>> uhci4: port 0x1880-0x189f irq 19 >>> at >>> device 29.1 on pci0 >>> usbus5 on uhci4 >>> uhci5: port 0x18a0-0x18bf irq 18 >>> at >>> device 29.2 on pci0 >>> usbus6 on uhci5 >>> ehci1: mem >>> 0xfc504c00-0xfc504fff >>> irq 23 at device 29.7 on pci0 >>> usbus7: EHCI version 1.0 >>> usbus7 on ehci1 >>> pcib6: at device 30.0 on pci0 >>> pci4: on pcib6 >>> pci4: at device 1.0 (no driver attached) >>> sdhci_pci0: mem 0xfc200800-0xfc2008ff irq 18 at >>> device 1.1 >>> on pci4 >>> sdhci_pci0: 1 slot(s) allocated >>> isab0: at device 31.0 on pci0 >>> isa0: on isab0 >>> ahci0: port >>> 0x18f0-0x18f7,0x18e4-0x18e7,0x18e8-0x18ef,0x18e0-0x18e3,0x18c0-0x18df >>> mem >>> 0xfc504000-0xfc5047ff irq 19 at device 31.2 on pci0 >>> ahci0: AHCI v1.20 with 4 3Gbps ports, Port Multiplier supported >>> ahcich0: at channel 0 on ahci0 >>> ahcich1: at channel 1 on ahci0 >>> ahcich5: at channel 5 on ahci0 >>> acpi_button0: on acpi0 >>> acpi_button1: on acpi0 >>> acpi_lid0: on acpi0 >>> acpi_acad0: on acpi0 >>> battery0: on acpi0 >>> acpi_tz0: on acpi0 >>> acpi_tz1: on acpi0 >>> acpi_tz2: on acpi0 >>> atkbdc0: port 0x60,0x64 irq 1 on acpi0 >>> atkbd0: irq 1 on atkbdc0 >>> kbd0 at atkbd0 >>> atkbd0: [GIANT-LOCKED] >>> psm0: irq 12 on atkbdc0 >>> psm0: [GIANT-LOCKED] >>> psm0: model Generic PS/2 mouse, device ID 0 >>> ppc0: cannot reserve I/O port range >>> est0: on cpu0 >>> est1: on cpu1 >>> ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is >>> present; >>> to enable, add "vfs.zfs.prefetch_disable=0" to >>> /boot/loader.conf. >>> ZFS filesystem version: 5 >>> ZFS storage pool version: features support (5000) >>> Timecounters tick every 1.000 msec >>> hdacc0: at cad 0 on hdac0 >>> hdaa0: at nid 1 on hdacc0 >>> pcm0: at nid 3 on hdaa0 >>> hdacc1: at cad 0 on hdac1 >>> hdaa1: at nid 1 on hdacc1 >>> pcm1: at nid 13,10 and 14 on hdaa1 >>> pcm2: at nid 15 and 19 on hdaa1 >>> usbus0: 12Mbps Full Speed USB v1.0 >>> usbus1: 12Mbps Full Speed USB v1.0 >>> usbus2: 12Mbps Full Speed USB v1.0 >>> usbus3: 480Mbps High Speed USB v2.0 >>> ugen0.1: at usbus0 >>> uhub0: on >>> usbus0 >>> ugen1.1: at usbus1 >>> uhub1: on >>> usbus1 >>> ugen2.1: at usbus2 >>> uhub2: on >>> usbus2 >>> ugen3.1: at usbus3 >>> uhub3: on >>> usbus3 >>> usbus4: 12Mbps Full Speed USB v1.0 >>> usbus5: 12Mbps Full Speed USB v1.0 >>> usbus6: 12Mbps Full Speed USB v1.0 >>> usbus7: 480Mbps High Speed USB v2.0 >>> ugen4.1: at usbus4 >>> uhub4: on >>> usbus4 >>> ugen5.1: at usbus5 >>> uhub5: on >>> usbus5 >>> ugen6.1: at usbus6 >>> uhub6: on >>> usbus6 >>> ugen7.1: at usbus7 >>> uhub7: on >>> usbus7 >>> ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 >>> ada0: ACS-2 ATA SATA 3.x device >>> ada0: Serial Number S1DHNSAD914271K >>> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) >>> ada0: Command Queueing enabled >>> ada0: 476940MB (976773168 512 byte sectors) >>> ada0: quirks=0x3<4K,NCQ_TRIM_BROKEN> >>> cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 >>> cd0: Removable CD-ROM SCSI device >>> cd0: Serial Number KZZ9B7E2004 >>> cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO >>> 8192bytes) >>> cd0: Attempt to query device size failed: NOT READY, Medium not present >>> - >>> tray open >>> SMP: AP CPU #1 Launched! >>> Timecounter "TSC" frequency 2094797271 Hz quality 1000 >>> Trying to mount root from zfs:zroot/root []... >>> Root mount waiting for: usbus7 usbus6 usbus5 usbus4 usbus3 usbus2 >>> usbus1 >>> usbus0 >>> uhub0: 2 ports with 2 removable, self powered >>> uhub1: 2 ports with 2 removable, self powered >>> uhub2: 2 ports with 2 removable, self powered >>> uhub5: 2 ports with 2 removable, self powered >>> uhub4: 2 ports with 2 removable, self powered >>> uhub6: 2 ports with 2 removable, self powered >>> Root mount waiting for: usbus7 usbus3 >>> Root mount waiting for: usbus7 usbus3 >>> uhub3: 6 ports with 6 removable, self powered >>> uhub7: 6 ports with 6 removable, self powered >>> Root mount waiting for: usbus3 >>> ugen6.2: at usbus6 >>> ugen0.2: at usbus0 >>> uhub8: on usbus0 >>> Root mount waiting for: usbus3 >>> uhub8: 3 ports with 0 removable, self powered >>> ugen3.2: at usbus3 >>> ugen0.3: at usbus0 >>> ukbd0: >>> on >>> usbus0 >>> kbd2 at ukbd0 >>> GEOM_ELI: Device gpt/swap0.eli created. >>> GEOM_ELI: Encryption: AES-XTS 128 >>> GEOM_ELI: Crypto: software >>> ugen0.4: at usbus0 >>> coretemp0: on cpu0 >>> coretemp1: on cpu1 >>> ichsmb0: port 0x1c00-0x1c1f irq >>> 19 at >>> device 31.3 on pci0 >>> smbus0: on ichsmb0 >>> info: [drm] Initialized drm 1.1.0 20060810 >>> drmn0: on vgapci0 >>> info: [drm] RADEON_IS_PCIE >>> info: [drm] initializing kernel modesetting (RV710 0x1002:0x9553 >>> 0x1028:0x02BE). >>> info: [drm] register mmio base: 0xFC000000 >>> info: [drm] register mmio size: 65536 >>> info: [drm] radeon_atrm_get_bios: ===> Try ATRM... >>> info: [drm] radeon_atrm_get_bios: pci_find_class() found: 0:1:0:0, >>> vendor=1002, device=9553 >>> info: [drm] radeon_atrm_get_bios: Get ACPI device handle >>> info: [drm] radeon_atrm_get_bios: Get ACPI handle for "ATRM" >>> info: [drm] radeon_atrm_get_bios: Failed to get "ATRM" handle: >>> AE_NOT_FOUND >>> info: [drm] radeon_acpi_vfct_bios: ===> Try VFCT... >>> info: [drm] radeon_acpi_vfct_bios: Get "VFCT" ACPI table >>> info: [drm] radeon_acpi_vfct_bios: Failed to get "VFCT" table: >>> AE_NOT_FOUND >>> info: [drm] igp_read_bios_from_vram: ===> Try IGP's VRAM... >>> info: [drm] igp_read_bios_from_vram: VRAM base address: 0xd0000000 >>> info: [drm] igp_read_bios_from_vram: Map address: 0xfffff800d0000000 >>> (262144 >>> bytes) >>> info: [drm] igp_read_bios_from_vram: Incorrect BIOS signature: 0x0000 >>> info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM... >>> info: [drm] radeon_read_bios: Map address: 0xfffff800000c0000 (131072 >>> bytes) >>> info: [drm] ATOM BIOS: BR32787 >>> drmn0: info: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M >>> used) >>> drmn0: info: GTT: 512M 0x0000000020000000 - 0x000000003FFFFFFF >>> info: [drm] Detected VRAM RAM=512M, BAR=256M >>> info: [drm] RAM width 64bits DDR >>> [TTM] Zone kernel: Available graphics memory: 2059256 kiB >>> [TTM] Initializing pool allocator >>> info: [drm] radeon: 512M of VRAM memory ready >>> info: [drm] radeon: 512M of GTT memory ready. >>> info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). >>> info: [drm] Driver supports precise vblank timestamp query. >>> info: [drm] MSI enabled 1 message(s) >>> drmn0: info: radeon: using MSI. >>> info: [drm] radeon: irq initialized. >>> info: [drm] GART: num cpu pages 131072, num gpu pages 131072 >>> info: [drm] probing gen 2 caps for device 8086:2a41 = 1/0 >>> info: [drm] Loading RV710 Microcode >>> info: [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). >>> drmn0: info: WB enabled >>> drmn0: info: fence driver on ring 0 use gpu addr 0x0000000020000c00 and >>> cpu >>> addr 0x0xfffff80014286c00 >>> drmn0: info: fence driver on ring 3 use gpu addr 0x0000000020000c0c and >>> cpu >>> addr 0x0xfffff80014286c0c >>> info: [drm] ring test on 0 succeeded in 1 usecs >>> info: [drm] ring test on 3 succeeded in 1 usecs >>> info: [drm] ib test on ring 0 succeeded in 0 usecs >>> info: [drm] ib test on ring 3 succeeded in 0 usecs >>> info: [drm] radeon_device_init: Taking over the fictitious range >>> 0xd0000000-0xe0000000 >>> iicbus0: on iicbb0 addr 0xff >>> iic0: on iicbus0 >>> iicbus1: on iicbb1 addr 0x0 >>> iic1: on iicbus1 >>> iicbus2: on iicbb2 addr 0x0 >>> iic2: on iicbus2 >>> iicbus3: on iicbb3 addr 0x0 >>> iic3: on iicbus3 >>> iicbus4: on iicbb4 addr 0x0 >>> iic4: on iicbus4 >>> iicbus5: on iicbb5 addr 0x0 >>> iic5: on iicbus5 >>> iicbus6: on iicbb6 addr 0x0 >>> iic6: on iicbus6 >>> info: [drm] Radeon Display Connectors >>> info: [drm] Connector 0: >>> info: [drm] VGA-1 >>> info: [drm] DDC: 0x7fa0 0x7fa0 0x7fa4 0x7fa4 0x7fa8 0x7fa8 0x7fac >>> 0x7fac >>> info: [drm] Encoders: >>> info: [drm] CRT1: INTERNAL_KLDSCP_DAC1 >>> info: [drm] Connector 1: >>> info: [drm] HDMI-A-1 >>> info: [drm] HPD1 >>> info: [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c >>> 0x7e5c >>> info: [drm] Encoders: >>> info: [drm] DFP1: INTERNAL_UNIPHY >>> info: [drm] Connector 2: >>> info: [drm] LVDS-1 >>> info: [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c >>> 0x7e4c >>> info: [drm] Encoders: >>> info: [drm] LCD1: INTERNAL_UNIPHY2 >>> info: [drm] Internal thermal controller with fan control >>> info: [drm] radeon: power management initialized >>> info: [drm] Connector VGA-1: get mode from tunables: >>> info: [drm] - kern.vt.fb.modes.VGA-1 >>> info: [drm] - kern.vt.fb.default_mode >>> info: [drm] Connector HDMI-A-1: get mode from tunables: >>> info: [drm] - kern.vt.fb.modes.HDMI-A-1 >>> info: [drm] - kern.vt.fb.default_mode >>> info: [drm] Connector LVDS-1: get mode from tunables: >>> info: [drm] - kern.vt.fb.modes.LVDS-1 >>> info: [drm] - kern.vt.fb.default_mode >>> info: [drm] fb mappable at 0xD0142000 >>> info: [drm] vram apper at 0xD0000000 >>> info: [drm] size 8294400 >>> info: [drm] fb depth is 24 >>> info: [drm] pitch is 7680 >>> fbd0 on drmn0 >>> VT: Replacing driver "vga" with new "fb". >>> info: [drm] Initialized radeon 2.29.0 20080528 for drmn0 on minor 0 >>> fuse-freebsd: version 0.4.4, FUSE ABI 7.8 >>> vboxdrv: fAsync=0 offMin=0x2a0 offMax=0xc05 >>> Cuse v0.1.34 @ /dev/cuse >>> wlan0: Ethernet address: 00:26:b9:12:40:a4 >>> iwn0: iwn_read_firmware: ucode rev=0x12a80601 >>> ubt0: >> 2> on >>> usbus6 >>> ums0: >>> on >>> usbus0 >>> ums0: 3 buttons and [XY] coordinates ID=2 >>> wlan0: link state changed to UP >>> WARNING: attempt to domain_add(bluetooth) after domainfinalize() >>> WARNING: attempt to domain_add(netgraph) after domainfinalize() >>> ipfw2 (+ipv6) initialized, divert loadable, nat loadable, default to >>> deny, >>> logging disabled >>> Accounting enabled >>> >>> >>> I hope this will give a hint. If anything else is needed, please tell. >>> I can >>> also start wpa_supplicant in debug mode or other things which might >>> give >>> info. >>> >>> Regards, >>> Ronald. >>> >>> >>> >>> >>>> >>>> >>>> On 29 May 2016 at 14:27, Ronald Klop wrote: >>>>> >>>>> On Sun, 29 May 2016 19:59:05 +0200, Adrian Chadd >>>>> >>>>> wrote: >>>>> >>>>>> hi, >>>>>> >>>>>> Do ifconfig wlan0 -ht (ie, disable 11n) >>>>>> >>>>>> see if that helps >>>>> >>>>> >>>>> >>>>> Hi, >>>>> >>>>> This does make the errors go away and startup more smoothly. >>>>> >>>>> Regards, >>>>> Ronald. >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 29 May 2016 at 05:46, Ronald Klop wrote: >>>>>>> >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> My laptop has troubles obtaining an ip address on the wlan0 >>>>>>> (if_iwn). >>>>>>> The >>>>>>> interface has trouble staying up during dhcp resolving. Below some >>>>>>> information from logs. *If* it obtains an IP address it seems quite >>>>>>> stable >>>>>>> afterwards. >>>>>>> Before >>>>>>> https://svnweb.freebsd.org/base?view=revision&revision=300732 I >>>>>>> had >>>>>>> to reboot a couple of times before it would happen to get an IP >>>>>>> address. >>>>>>> >>>>>>> If I need to supply more information please tell. I'm willing to >>>>>>> test >>>>>>> patches also. >>>>>>> >>>>>>> Regards, >>>>>>> Ronald. >>>>>>> >>>>>>> >>>>>>> From uname -a: >>>>>>> FreeBSD sjakie.klop.ws 11.0-ALPHA1 FreeBSD 11.0-ALPHA1 #7 r300901M: >>>>>>> Sat >>>>>>> May >>>>>>> 28 16:54:00 CEST 2016 >>>>>>> root@sjakie.klop.ws:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 >>>>>>> >>>>>>> From dmesg: >>>>>>> iwn0: mem 0xf8000000-0xf8001fff irq >>>>>>> 17 >>>>>>> at >>>>>>> device 0.0 on pci2 >>>>>>> >>>>>>> From /etc/rc.conf. >>>>>>> wlans_iwn0="wlan0" >>>>>>> create_args_wlan0="wlanaddr 00:26:b9:12:40:a4 country NL" >>>>>>> ifconfig_wlan0="WPA" >>>>>>> ifconfig_wlan0="$ifconfig_wlan0 SYNCDHCP" >>>>>>> >>>>>>> From console.log: >>>>>>> May 29 13:34:45 sjakie kernel: Created wlan(4) interfaces: wlan0. >>>>>>> May 29 13:34:45 sjakie kernel: Starting wpa_supplicant. >>>>>>> May 29 13:34:45 sjakie kernel: Starting dhclient. >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: no link ... >>>>>>> May 29 13:34:45 sjakie kernel: .. >>>>>>> May 29 13:34:45 sjakie kernel: ... >>>>>>> May 29 13:34:45 sjakie kernel: got link >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state up -> down >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state down -> up >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state up -> down >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 6 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state down -> up >>>>>>> May 29 13:34:45 sjakie kernel: >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state up -> down >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 15 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state down -> up >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state up -> down >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 4 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 9 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state down -> up >>>>>>> May 29 13:34:45 sjakie kernel: >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state up -> down >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 16 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state down -> up >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state up -> down >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 5 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 5 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 11 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0 link state down -> up >>>>>>> May 29 13:34:45 sjakie kernel: DHCPREQUEST on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPDISCOVER on wlan0 to >>>>>>> 255.255.255.255 >>>>>>> port >>>>>>> 67 interval 12 >>>>>>> May 29 13:34:45 sjakie kernel: DHCPACK from 192.168.1.1 >>>>>>> May 29 13:34:45 sjakie kernel: bound to 192.168.1.109 -- renewal in >>>>>>> 2147483647 seconds. >>>>>>> >>>>>>> From messages: >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: Ethernet address: >>>>>>> 00:26:b9:12:40:a4 >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_read_firmware: ucode >>>>>>> rev=0x12a80601 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to UP >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_intr: fatal firmware error >>>>>>> May 29 13:34:45 sjakie kernel: firmware error log: >>>>>>> May 29 13:34:45 sjakie kernel: error type = "UNKNOWN" >>>>>>> (0x00000038) >>>>>>> May 29 13:34:45 sjakie kernel: program counter = 0x00009F64 >>>>>>> May 29 13:34:45 sjakie kernel: source line = 0x000003C4 >>>>>>> May 29 13:34:45 sjakie kernel: error data = 0x0000000000000000 >>>>>>> May 29 13:34:45 sjakie kernel: branch link = 0x00009F6000009F60 >>>>>>> May 29 13:34:45 sjakie kernel: interrupt link = 0x0000DBEA00000000 >>>>>>> May 29 13:34:45 sjakie kernel: time = 54908 >>>>>>> May 29 13:34:45 sjakie kernel: driver status: >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 0: qid=0 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 1: qid=1 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 2: qid=2 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 3: qid=3 cur=2 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 4: qid=4 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 5: qid=5 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 6: qid=6 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 7: qid=7 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 8: qid=8 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 9: qid=9 cur=81 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 10: qid=10 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 11: qid=11 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 12: qid=12 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 13: qid=13 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 14: qid=14 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 15: qid=15 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 16: qid=16 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 17: qid=17 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 18: qid=18 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 19: qid=19 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: rx ring: cur=39 >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_panicked: controller >>>>>>> panicked, >>>>>>> iv_state = 5; restarting >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to DOWN >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_read_firmware: ucode >>>>>>> rev=0x12a80601 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to UP >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to DOWN >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: scan timeout >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_read_firmware: ucode >>>>>>> rev=0x12a80601 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to UP >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to DOWN >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: scan timeout >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_read_firmware: ucode >>>>>>> rev=0x12a80601 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to UP >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_intr: fatal firmware error >>>>>>> May 29 13:34:45 sjakie kernel: firmware error log: >>>>>>> May 29 13:34:45 sjakie kernel: error type = "UNKNOWN" >>>>>>> (0x00000038) >>>>>>> May 29 13:34:45 sjakie kernel: program counter = 0x00009F64 >>>>>>> May 29 13:34:45 sjakie kernel: source line = 0x000003C4 >>>>>>> May 29 13:34:45 sjakie kernel: error data = 0x0000000000000000 >>>>>>> May 29 13:34:45 sjakie kernel: branch link = 0x00009F6000009F60 >>>>>>> May 29 13:34:45 sjakie kernel: interrupt link = 0x0000DBEA00000000 >>>>>>> May 29 13:34:45 sjakie kernel: time = 7464 >>>>>>> May 29 13:34:45 sjakie kernel: driver status: >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 0: qid=0 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 1: qid=1 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 2: qid=2 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 3: qid=3 cur=2 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 4: qid=4 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 5: qid=5 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 6: qid=6 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 7: qid=7 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 8: qid=8 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 9: qid=9 cur=81 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 10: qid=10 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 11: qid=11 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 12: qid=12 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 13: qid=13 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 14: qid=14 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 15: qid=15 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 16: qid=16 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 17: qid=17 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 18: qid=18 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 19: qid=19 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: rx ring: cur=63 >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_panicked: controller >>>>>>> panicked, >>>>>>> iv_state = 5; restarting >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to DOWN >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_read_firmware: ucode >>>>>>> rev=0x12a80601 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to UP >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to DOWN >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: scan timeout >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_read_firmware: ucode >>>>>>> rev=0x12a80601 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to UP >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_intr: fatal firmware error >>>>>>> May 29 13:34:45 sjakie kernel: firmware error log: >>>>>>> May 29 13:34:45 sjakie kernel: error type = "UNKNOWN" >>>>>>> (0x00000038) >>>>>>> May 29 13:34:45 sjakie kernel: program counter = 0x00009F64 >>>>>>> May 29 13:34:45 sjakie kernel: source line = 0x000003C4 >>>>>>> May 29 13:34:45 sjakie kernel: error data = 0x0000000000000000 >>>>>>> May 29 13:34:45 sjakie kernel: branch link = 0x00009F6000009F60 >>>>>>> May 29 13:34:45 sjakie kernel: interrupt link = 0x0000DBEA00000000 >>>>>>> May 29 13:34:45 sjakie kernel: time = 69923 >>>>>>> May 29 13:34:45 sjakie kernel: driver status: >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 0: qid=0 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 1: qid=1 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 2: qid=2 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 3: qid=3 cur=2 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 4: qid=4 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 5: qid=5 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 6: qid=6 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 7: qid=7 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 8: qid=8 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 9: qid=9 cur=81 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 10: qid=10 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 11: qid=11 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 12: qid=12 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 13: qid=13 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 14: qid=14 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 15: qid=15 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 16: qid=16 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 17: qid=17 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 18: qid=18 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: tx ring 19: qid=19 cur=0 queued=0 >>>>>>> May 29 13:34:45 sjakie kernel: rx ring: cur=61 >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_panicked: controller >>>>>>> panicked, >>>>>>> iv_state = 5; restarting >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to DOWN >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_read_firmware: ucode >>>>>>> rev=0x12a80601 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to UP >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to DOWN >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: scan timeout >>>>>>> May 29 13:34:45 sjakie kernel: iwn0: iwn_read_firmware: ucode >>>>>>> rev=0x12a80601 >>>>>>> May 29 13:34:45 sjakie kernel: wlan0: link state changed to UP >>>>>>> _______________________________________________ >>>>>>> freebsd-current@freebsd.org mailing list >>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>>> To unsubscribe, send any mail to >>>>>>> "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sat Apr 15 02:53:49 2017 Return-Path: Delivered-To: freebsd-current@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 0A94CD3E1D7 for ; Sat, 15 Apr 2017 02:53:49 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-41.reflexion.net [208.70.210.41]) (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 C213C10DD for ; Sat, 15 Apr 2017 02:53:48 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 16846 invoked from network); 15 Apr 2017 02:56:45 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 15 Apr 2017 02:56:45 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Fri, 14 Apr 2017 22:53:46 -0400 (EDT) Received: (qmail 24506 invoked from network); 15 Apr 2017 02:53:46 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 15 Apr 2017 02:53:46 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 5D889EC78CC; Fri, 14 Apr 2017 19:53:45 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) From: Mark Millard In-Reply-To: Date: Fri, 14 Apr 2017 19:53:44 -0700 Cc: Pedro Giffuni , FreeBSD Ports , FreeBSD Toolchain , freebsd-arm , ericturgeon.bsd@gmail.com, FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <9758023E-1526-41F9-9416-6AC8AD3201B5@dsl-only.net> To: Gerald Pfeifer X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 02:53:49 -0000 On 2017-Apr-14, at 4:30 PM, Gerald Pfeifer wrote: > On Thu, 13 Apr 2017, Pedro Giffuni wrote: >> I didn=E2=80=99t want to get into this but the problem is that as = part of it's >> build/bootstrapping process, GCC historically takes system headers >> and attempts to =E2=80=9Cfix=E2=80=9D them. I am unsure the fixes do = anything at all >> nowadays but the effect is that the compiler tends to take snapshots >> of the system headers when it is built. cdefs.h is used by all the >> system headers so changes in cdefs.h have good chances affecting >> such builds but any change are likely to cause similar trouble. >>=20 >> In the case of gcc-aux, it appears the compilation is based on a >> bootstrap compiler which already carries outdated headers. >> A workaround, suggested by gerald@ the last time a similar issue >> happened was to run for install-tools/fixinc.sh. I think that may >> regenerate the headers and let the build use updated headers. >> Ultimately gcc-aux needs maintainer intervention and using >> outdated headers will break sooner or later: especially on -current. >=20 > Indeed, thanks for the analysis/background, Pedro! >=20 > I had a look at gcc6-aux is based on the 20170202 snapshot of GCC 6,=20= > and perhaps John (as the maintainer of that port) has plans to update=20= > it? Let me copy him. [As I have a prior E-mail exchange with John M. indicating that he was not intending to be the lang/gcc6-aux maintainer, I avoid spamming him with this material: I've removed him from the CC list in this reply. I can send the material to him if I see evidence of his wanting it.] Just FYI: [Previously: temporarily adding __nonnull and __nonnull_all back into into my local head FreeBSD variant got problems with: __vm_ooffset_t and __vm_pindex_t no longer existing and also the same pid_t issue indicated below.] I tried using [on a Pine64+ 2GB aarch64 system]: # = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap/libexec/gcc/aarc= h64-aux-freebsd12.0/6.3.1/install-tools/mkheaders = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap to deal with __nonnull, __nonnull_all, __vm_ooffset_t, and = __vm_pindex_t. I then built via portmaster -CDK usage. Various header issues did go away but the build of lang/gcc6-aux still stopped with: In file included from = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:20:0: ./config.h:556:15: error: two or more data types in declaration = specifiers #define pid_t int ^ I'm guessing that the define for pid_t in config.h resulted in something like: typedef ??? pid_t; that turned into something like a: typedef ??? int; for the error listed above. There were also implicit-declaration warnings: = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c: In function 'simple_object_internal_read': = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:75:21: warning: implicit declaration of function 'read' = [-Wimplicit-function-declaration] ssize_t got =3D read (descriptor, buffer, size); ^~~~ = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c: In function 'simple_object_internal_write': = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:119:23: warning: implicit declaration of function 'write' = [-Wimplicit-function-declaration] ssize_t wrote =3D write (descriptor, buffer, size); ^~~~~ The implicit-declaration warnings for read and write may well also not be expected/desirable. It may be that more than a script run is needed to make things be appropriate. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-current@freebsd.org Sat Apr 15 03:07:40 2017 Return-Path: Delivered-To: freebsd-current@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 B44A7D3E955; Sat, 15 Apr 2017 03:07:40 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 7D5FC20B; Sat, 15 Apr 2017 03:07:40 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pg0-x243.google.com with SMTP id o123so18618139pga.1; Fri, 14 Apr 2017 20:07:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=F45sLgS5DdNiaxYMSXZhbG240fLI5g2HYPhd0FSj0DA=; b=nvK5lMBRg8px5VCy2+gGAAbqDXNbJZfsQtYQHaBvXyiL7NLa/2/70HtuposuUILZD5 JG6a7JT8TplH1kC9tw1N67kV1Zpv6aiqWGCEs7l59lYhoWlyp+XrKRNkf7p3YkQgBDKl Yn7PfchnZC03mMg3s7g5nT2lVWtvT5fl58BjVoBNlEwwqOv3J4LKwPL9Kxt5l+0dswSO RnJjd/Fwi5wOUkucq8/C8dE0fgwd9EHzkqDpuC/jiZp/JjolNsn66BZkBmz//masP69c MkWEGQcD/kUE2vIPite9aghZ6shWYaPr6kovxIC1/CMx0fhAT0mXxdQU9u6PRJAzV4f2 QWLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=F45sLgS5DdNiaxYMSXZhbG240fLI5g2HYPhd0FSj0DA=; b=d1TMCd87fLbloRdPHLhxZblgAgs0N02sngn8HFlKrRMvgBn1aJ6xZWlAs/cDFWYNZr tV1zsBSYgOaxzi6PmBgvzh2AF5BsMvpczJ++p4PNTeWlc3qXinWfW0M8QCDlu3+LXDM0 0oiOgKzi1iQQUsQ8CmlEBQiUDpkZoAUO9iQX4APFk1cpYXjdejYwukmbkZUL4LBV86RD Kr6KLrPIVptb7czZfbDCDCqddpQeit3hRfCwbtpICS6DV9eVAK+G9jtjMIyLhBmNdxHj Br+chtKNUAmD8BtZDuVQGMC8+Ly1eX8eaYjcbtbFPY5pfDOeoDI6K44R0BNn/wkYvhss SS8A== X-Gm-Message-State: AN3rC/47Q8RWGBBmIvwr946W/+YPwsJkGNkDTfpa5LEgltuI2/wkJ8iy nkKi+CUOzia+VA== X-Received: by 10.84.169.67 with SMTP id g61mr939580plb.51.1492225660005; Fri, 14 Apr 2017 20:07:40 -0700 (PDT) Received: from pinklady.local (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id l127sm5468287pga.7.2017.04.14.20.07.38 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 14 Apr 2017 20:07:39 -0700 (PDT) Subject: Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/signed; boundary="Apple-Mail=_534C68CC-3A27-411C-AB28-2AACB66F40B1"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail From: "Ngie Cooper (yaneurabeya)" In-Reply-To: Date: Fri, 14 Apr 2017 20:07:37 -0700 Cc: Gerald Pfeifer , Pedro Giffuni , FreeBSD Ports , FreeBSD Toolchain , freebsd-arm , ericturgeon.bsd@gmail.com, FreeBSD Current Message-Id: <7606F976-20B7-4FB8-BE80-C27773F5529A@gmail.com> References: <9758023E-1526-41F9-9416-6AC8AD3201B5@dsl-only.net> To: Mark Millard X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 03:07:40 -0000 --Apple-Mail=_534C68CC-3A27-411C-AB28-2AACB66F40B1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 14, 2017, at 19:53, Mark Millard wrote: >=20 > On 2017-Apr-14, at 4:30 PM, Gerald Pfeifer wrote: >=20 >> On Thu, 13 Apr 2017, Pedro Giffuni wrote: >>> I didn=E2=80=99t want to get into this but the problem is that as = part of it's >>> build/bootstrapping process, GCC historically takes system headers >>> and attempts to =E2=80=9Cfix=E2=80=9D them. I am unsure the fixes do = anything at all >>> nowadays but the effect is that the compiler tends to take snapshots >>> of the system headers when it is built. cdefs.h is used by all the >>> system headers so changes in cdefs.h have good chances affecting >>> such builds but any change are likely to cause similar trouble. >>>=20 >>> In the case of gcc-aux, it appears the compilation is based on a >>> bootstrap compiler which already carries outdated headers. >>> A workaround, suggested by gerald@ the last time a similar issue >>> happened was to run for install-tools/fixinc.sh. I think that may >>> regenerate the headers and let the build use updated headers. >>> Ultimately gcc-aux needs maintainer intervention and using >>> outdated headers will break sooner or later: especially on -current. >>=20 >> Indeed, thanks for the analysis/background, Pedro! >>=20 >> I had a look at gcc6-aux is based on the 20170202 snapshot of GCC 6, >> and perhaps John (as the maintainer of that port) has plans to update >> it? Let me copy him. >=20 > [As I have a prior E-mail exchange with John M. indicating that > he was not intending to be the lang/gcc6-aux maintainer, I > avoid spamming him with this material: I've removed him from > the CC list in this reply. I can send the material to him if I > see evidence of his wanting it.] >=20 > Just FYI: >=20 > [Previously: temporarily adding __nonnull and __nonnull_all > back into into my local head FreeBSD variant got problems > with: __vm_ooffset_t and __vm_pindex_t no longer existing and > also the same pid_t issue indicated below.] >=20 >=20 > I tried using [on a Pine64+ 2GB aarch64 system]: >=20 > # = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap/libexec/gcc/aarc= h64-aux-freebsd12.0/6.3.1/install-tools/mkheaders = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap >=20 > to deal with __nonnull, __nonnull_all, __vm_ooffset_t, and = __vm_pindex_t. >=20 > I then built via portmaster -CDK usage. Various header issues > did go away but the build of lang/gcc6-aux still stopped with: >=20 > In file included from = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:20:0: > ./config.h:556:15: error: two or more data types in declaration = specifiers > #define pid_t int > ^ >=20 > I'm guessing that the define for pid_t in config.h resulted > in something like: >=20 > typedef ??? pid_t; >=20 > that turned into something like a: >=20 > typedef ??? int; >=20 > for the error listed above. >=20 > There were also implicit-declaration warnings: >=20 > = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c: In function 'simple_object_internal_read': > = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:75:21: warning: implicit declaration of function 'read' = [-Wimplicit-function-declaration] > ssize_t got =3D read (descriptor, buffer, size); > ^~~~ > = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c: In function 'simple_object_internal_write': > = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:119:23: warning: implicit declaration of function 'write' = [-Wimplicit-function-declaration] > ssize_t wrote =3D write (descriptor, buffer, size); > ^~~~~ >=20 > The implicit-declaration warnings for read and write may well > also not be expected/desirable. >=20 > It may be that more than a script run is needed to make > things be appropriate. Is there a reason why you need ada support (that seems to be the = only real reason for installing gcc6 vs gcc6-aux)? gcc6-aux uses a = snapshot of gcc6 with custom options. Thanks! -Ngie --Apple-Mail=_534C68CC-3A27-411C-AB28-2AACB66F40B1 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJY8Y56AAoJEPWDqSZpMIYVCqUQAJ3/RIVZHjUlbjtlq+eCNLiZ fk4l21s7AFvgMtRsqSulnEjPQywT+kcq/BIZUr7r+J9KRqIWu8uBIeZQ3znciXbS zH8LEfJFl/2Xy1ixCE3nJ1e4v/kP4CgeKLtiNVz4PgxA0rcqgucQLqWApC4QaRPl xe7/lLOTn1j9As4YaNErasU55JSzmlvGEQQb4HAKIR+/CX9qofekwj8cqtsdy7Bt dQ93H3HPVsJRHSbPDYt4zWfbGC//PZM28nEWVNguVKI21XIz68oToB9mWPdF7QVM qWCB7OfDoVHclKk4dmdNJe3Qz/qhDdYJQQd2T8i6q9qHE4xxuuTLlKx5J8KAxohd oM7ZEbqBMtddJA35g1nGwhBnIqcOITho+aDMaANYo7ykEUNpY2LFOtuxuBeSJpZ5 LgVXuRz4kopf4UHZ+XoNCI4EFWIFl/VpJd/rjpMkBgbn/Olu+6tNIyy6tZUB5BPn Cchu+5lmRaqTVtjjFbc0QS/SdXlRnoz2MA+xd+CvI2TDFXdoDS+amUU2keOPvkS+ nOb0h5exvPecvlnhhVQPgmLRnl6SJ4+N6MBt5l7Zfp5nc9lUMMK+1xo48guPd4E8 mLgozotLhXZIcRECl++g5dCm7x+7pYN/4+VHM9jd4YiRvZnnABj4+XaNlovukQAR yVjX49cZnKiT2FVMK3d5 =jZS8 -----END PGP SIGNATURE----- --Apple-Mail=_534C68CC-3A27-411C-AB28-2AACB66F40B1-- From owner-freebsd-current@freebsd.org Sat Apr 15 03:27:32 2017 Return-Path: Delivered-To: freebsd-current@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 7A76DD3E3FD for ; Sat, 15 Apr 2017 03:27:32 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-42.reflexion.net [208.70.210.42]) (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 2624EA47 for ; Sat, 15 Apr 2017 03:27:31 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 20862 invoked from network); 15 Apr 2017 03:27:30 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 15 Apr 2017 03:27:30 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Fri, 14 Apr 2017 23:27:30 -0400 (EDT) Received: (qmail 20674 invoked from network); 15 Apr 2017 03:27:30 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 15 Apr 2017 03:27:30 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 7AFFEEC8B57; Fri, 14 Apr 2017 20:27:29 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) From: Mark Millard In-Reply-To: <7606F976-20B7-4FB8-BE80-C27773F5529A@gmail.com> Date: Fri, 14 Apr 2017 20:27:29 -0700 Cc: Gerald Pfeifer , Pedro Giffuni , FreeBSD Ports , FreeBSD Toolchain , freebsd-arm , ericturgeon.bsd@gmail.com, FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <9758023E-1526-41F9-9416-6AC8AD3201B5@dsl-only.net> <7606F976-20B7-4FB8-BE80-C27773F5529A@gmail.com> To: "Ngie Cooper (yaneurabeya)" X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 03:27:32 -0000 On 2017-Apr-14, at 8:07 PM, Ngie Cooper (yaneurabeya) wrote: > Is there a reason why you need ada support (that seems to be the = only real reason for installing gcc6 vs gcc6-aux)? gcc6-aux uses a = snapshot of gcc6 with custom options. > Thanks! > -Ngie I got to lang/gcc6-aux indirectly: I saw the ports checkin notice and github information for ports-mgmt/synth indicating that native aarch64 support was now in place/possible. When I looked at what pkg would provide it was older. So on a Pine64+ 2GB [an aarch64 context] I did an svnlite update for /usr/ports and then tried to build ports-mgmt/synth . Synth is written in ada and so indirectly then attempts a lang/gcc6-aux build if it is not already in place. [gcc5-aux likely would not support aarch64.] I've no direct interest in lang/gcc6-aux or ada as stands. But indirectly such is involved in what I wanted to explore. I've seen material quoted from a exp-run that reported that about 54(?) ports were then blocked by lang/gcc6-aux not building. (So some problems might not be aarch64 specific despite my example context: the "54" material was likely not for an aarch64 context.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-current@freebsd.org Sat Apr 15 09:30:20 2017 Return-Path: Delivered-To: freebsd-current@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 351F7D3F996; Sat, 15 Apr 2017 09:30:20 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 08FB71A5; Sat, 15 Apr 2017 09:30:19 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 030211F81; Sat, 15 Apr 2017 04:30:12 -0500 (CDT) Date: Sat, 15 Apr 2017 04:30:10 -0500 From: Mark Linimon To: Mark Millard Cc: "Ngie Cooper (yaneurabeya)" , Gerald Pfeifer , FreeBSD Ports , FreeBSD Current , FreeBSD Toolchain , freebsd-arm , Pedro Giffuni , ericturgeon.bsd@gmail.com Subject: Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) Message-ID: <20170415093010.GA4104@lonesome.com> References: <9758023E-1526-41F9-9416-6AC8AD3201B5@dsl-only.net> <7606F976-20B7-4FB8-BE80-C27773F5529A@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 09:30:20 -0000 On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote: > I've seen material quoted from a exp-run that reported > that about 54(?) ports were then blocked by lang/gcc6-aux > not building. Although the first is an older run (the last complete run IIUC), there were 50 and 51 respectively as of: http://thunderx1.nyi.freebsd.org/build.html?mastername=110arm64-default&build=423029 http://beefy8.nyi.freebsd.org/build.html?mastername=head-armv6-default&build=p437390_s316341 I think you're fairly deep into unexplored territory here. mcl From owner-freebsd-current@freebsd.org Sat Apr 15 09:33:41 2017 Return-Path: Delivered-To: freebsd-current@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 73FEFD3FC4F for ; Sat, 15 Apr 2017 09:33:41 +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 1A629968; Sat, 15 Apr 2017 09:33:40 +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 v3F9XYZU021302 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 15 Apr 2017 12:33:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v3F9XYZU021302 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v3F9XYwA021301; Sat, 15 Apr 2017 12:33:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 15 Apr 2017 12:33:34 +0300 From: Konstantin Belousov To: "O. Hartmann" Cc: "O. Hartmann" , Alan Somers , FreeBSD CURRENT Subject: Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd) Message-ID: <20170415093334.GO1788@kib.kiev.ua> References: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> <20170414185827.1ab68398@thor.intern.walstatt.dynvpn.de> <20170414171857.GK1788@kib.kiev.ua> <20170415111841.0c34be88@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170415111841.0c34be88@thor.intern.walstatt.dynvpn.de> User-Agent: Mutt/1.8.0 (2017-02-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-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 09:33:41 -0000 On Sat, Apr 15, 2017 at 11:18:41AM +0200, O. Hartmann wrote: > Am Fri, 14 Apr 2017 20:18:57 +0300 > Konstantin Belousov schrieb: > > > On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: > > > Fatal trap 12: page fault while in kernel mode > > > cpuid = 2; apic id = 02 > > > fault virtual address = 0xfffff8001282fb00 > > > fault code = supervisor read instruction, protection violation > > > > > ??() at 0xfffff8001282fb00 > > > bpf_mtap() at bpf_mtap+0x1ab/frame 0xfffffe012d2aefb0 > > > iflib_txq_drain() at iflib_txq_drain+0x1383/frame 0xfffffe012d2af130 > > > drain_ring_lockless() at drain_ring_lockless+0xc0/frame 0xfffffe012d2af190 > > > ifmp_ring_enqueue() at ifmp_ring_enqueue+0x32e/frame 0xfffffe012d2af200 > > > iflib_if_transmit() at iflib_if_transmit+0xb0/frame 0xfffffe012d2af240 > > > ether_output() at ether_output+0x730/frame 0xfffffe012d2af2e0 > > > arprequest() at arprequest+0x426/frame 0xfffffe012d2af3e0 > > > arpresolve_full() at arpresolve_full+0x3d1/frame 0xfffffe012d2af460 > > > arpresolve() at arpresolve+0x10c/frame 0xfffffe012d2af4d0 > > > ether_output() at ether_output+0x4e1/frame 0xfffffe012d2af570 > > > ip_output() at ip_output+0x14e6/frame 0xfffffe012d2af6b0 > > > udp_send() at udp_send+0xab1/frame 0xfffffe012d2af780 > > > sosend_dgram() at sosend_dgram+0x3e4/frame 0xfffffe012d2af7f0 > > > kern_sendit() at kern_sendit+0x229/frame 0xfffffe012d2af890 > > > sendit() at sendit+0x1a7/frame 0xfffffe012d2af8e0 > > > sys_sendto() at sys_sendto+0x4d/frame 0xfffffe012d2af930 > > > amd64_syscall() at amd64_syscall+0x4c2/frame 0xfffffe012d2afab0 > > > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012d2afab0 > > > syscall (133, FreeBSD ELF64, sys_sendto), rip = 0x800b8a5fa, rsp = 0x7fffffffd6b8, > > > rbp = 0x7fffffffdcc0 --- > > > > You probably have BPF_JITTER option in your kernel config. Either set > > net.bpf_jitter.enable to 0 for now, or remove the option. > > > > It is due to r316767. The issue is known and a solution is being discussed. > > simply setting "net.bpf_jitter.enable=0" in /boot/loader.conf.local doesn't help, the > Trap 12 still occurs. It is sysctl, not tunable. From owner-freebsd-current@freebsd.org Sat Apr 15 10:01:43 2017 Return-Path: Delivered-To: freebsd-current@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 C62A2D3C965 for ; Sat, 15 Apr 2017 10:01:43 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 42049C76; Sat, 15 Apr 2017 10:01:42 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.171.81]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MJmcS-1d0QRu0psa-0017Qz; Sat, 15 Apr 2017 12:01:34 +0200 Date: Sat, 15 Apr 2017 11:59:10 +0200 From: "O. Hartmann" To: Konstantin Belousov Cc: "O. Hartmann" , Alan Somers , FreeBSD CURRENT Subject: Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd) Message-ID: <20170415115910.65e1a0ea@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170415093334.GO1788@kib.kiev.ua> References: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> <20170414185827.1ab68398@thor.intern.walstatt.dynvpn.de> <20170414171857.GK1788@kib.kiev.ua> <20170415111841.0c34be88@thor.intern.walstatt.dynvpn.de> <20170415093334.GO1788@kib.kiev.ua> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/O/0bDijjmV9a8EmdUwSZDUu"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:atJjOWlCb/sl/NrxqlPst+fnS4o7ISOq6qduhEwlee81VKcYogY Rly+b0p5hPRQ92Xn0ulGocCWiwjkKi8cUPkJKEkQ7U13MbbiEARyaffrEeGCwGsP+l+IEoB HXyCzL5U+ucasxtDN0PytKmw9Y7NYwdxOhByXuE9eP31vGvu+CzlfevSigwkwcCV/6VwrbH h+8eIyxVLtqrSJRVG7I+w== X-UI-Out-Filterresults: notjunk:1;V01:K0:7dQ6yiHq8rI=:uPGJQ8ckmO5/VYyWYPXUxY ul7o+Fk4zpKEfeamzDyEy915cT1Jn6bvTGjcrLdSVuUSmCrY6X6DsZRZDwjx67JG2S60wHpEt KS1hV1nj1+UjcSy/+7fQeCPcHG2zufB/FqHkDsYMugbpWVTQoOtlGOqrEknLDSTR1GnvHNoxd sCHi5WIH+yoHMd+yU4UCBcOghkRGQfn+J7n0/RYWlvowUf88Seft5AA+ngg4fDKlAL9vHLlZI wtpUYvh6HCIKRpq4Sh0fGL5mWl15f8gj8lQRAFmLIbOAZ+Rm0VEJPGQbXib/khsd2KYz+uUHP 4H7vificDcG6aZNZZbTVOkdxe8ps1+krtMj1Bhp8fh7Df2uRxoTmJBsjZwsOTSDIEJH1ZuF6d r5KGCKqwE+PhUcI14r8tVOpVH6Ph+ySv5DKpwQb8iTl35o07/7S6MsTY29nKJI2XHH6s4M8/d FSmRaxBNTvl+ia4Z+ipc/EZizR2mfWAPprptC1VlfuNizxXWB3lFh/gWeH15SyR1diGhCbsEV ifRa430i4JH+DO3U1YCLckQJPhqL5AVrNyKxXhdeWW7M1JrtTaYZSeFmwzFrkSrKE4Tc75Jvc 2xcXDNZNnkSFUSbgD289GWnR6uONsjbzGjYTlChbbuqIj3Xcs8lh7XFQeofK3A+N9BbTCn7Dv H/KuyB8Umh/UMU+CFYJNta2CYyzT7TYXRfMT9ZmX1/Ct5yGPhdl2klZgAAgILE0PMYiqzQuxG riBKdfdZR6A2Oc4dS4jpjQ0qau7rPsl274+GGdl9+qnLWJrEdUJT4pRHY4U= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 10:01:43 -0000 --Sig_/O/0bDijjmV9a8EmdUwSZDUu Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sat, 15 Apr 2017 12:33:34 +0300 Konstantin Belousov schrieb: > On Sat, Apr 15, 2017 at 11:18:41AM +0200, O. Hartmann wrote: > > Am Fri, 14 Apr 2017 20:18:57 +0300 > > Konstantin Belousov schrieb: > > =20 > > > On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: =20 > > > > Fatal trap 12: page fault while in kernel mode > > > > cpuid =3D 2; apic id =3D 02 > > > > fault virtual address =3D 0xfffff8001282fb00 > > > > fault code =3D supervisor read instruction, protection= violation =20 > > > =20 > > > > ??() at 0xfffff8001282fb00 > > > > bpf_mtap() at bpf_mtap+0x1ab/frame 0xfffffe012d2aefb0 > > > > iflib_txq_drain() at iflib_txq_drain+0x1383/frame 0xfffffe012d2af130 > > > > drain_ring_lockless() at drain_ring_lockless+0xc0/frame 0xfffffe012= d2af190 > > > > ifmp_ring_enqueue() at ifmp_ring_enqueue+0x32e/frame 0xfffffe012d2a= f200 > > > > iflib_if_transmit() at iflib_if_transmit+0xb0/frame 0xfffffe012d2af= 240 > > > > ether_output() at ether_output+0x730/frame 0xfffffe012d2af2e0 > > > > arprequest() at arprequest+0x426/frame 0xfffffe012d2af3e0 > > > > arpresolve_full() at arpresolve_full+0x3d1/frame 0xfffffe012d2af460 > > > > arpresolve() at arpresolve+0x10c/frame 0xfffffe012d2af4d0 > > > > ether_output() at ether_output+0x4e1/frame 0xfffffe012d2af570 > > > > ip_output() at ip_output+0x14e6/frame 0xfffffe012d2af6b0 > > > > udp_send() at udp_send+0xab1/frame 0xfffffe012d2af780 > > > > sosend_dgram() at sosend_dgram+0x3e4/frame 0xfffffe012d2af7f0 > > > > kern_sendit() at kern_sendit+0x229/frame 0xfffffe012d2af890 > > > > sendit() at sendit+0x1a7/frame 0xfffffe012d2af8e0 > > > > sys_sendto() at sys_sendto+0x4d/frame 0xfffffe012d2af930 > > > > amd64_syscall() at amd64_syscall+0x4c2/frame 0xfffffe012d2afab0 > > > > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012d2afab0 > > > > syscall (133, FreeBSD ELF64, sys_sendto), rip =3D 0x800b8a5fa, rsp = =3D 0x7fffffffd6b8, > > > > rbp =3D 0x7fffffffdcc0 --- =20 > > >=20 > > > You probably have BPF_JITTER option in your kernel config. Either set > > > net.bpf_jitter.enable to 0 for now, or remove the option. > > >=20 > > > It is due to r316767. The issue is known and a solution is being disc= ussed. =20 > >=20 > > simply setting "net.bpf_jitter.enable=3D0" in /boot/loader.conf.local d= oesn't help, the > > Trap 12 still occurs. =20 >=20 > It is sysctl, not tunable. Correct, I didn't/couldn't think that far. Having a setting in /etc/sysctl.= conf accordingly, booting the kernel doesn't reveal the Trap 12 anymore. Thanks. Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/O/0bDijjmV9a8EmdUwSZDUu Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPHu7gAKCRDS528fyFhY lLzLAf92lC4fqo0TzDv1qEbyJCRX7Jos+cqxPrqoq4/clfEBEy0kMRuDmfyaUuz7 E1hOEtvAOAKCZYu0hlti8BSjWCGtAf95VVeRHvO+pPC1Db4xQBf2JrzfahKm6DGW dTCJXH/pMM8WIeEphCRopTysAOYKAzKZ13O9KOBiGKJXIcjAt8cf =Uk50 -----END PGP SIGNATURE----- --Sig_/O/0bDijjmV9a8EmdUwSZDUu-- From owner-freebsd-current@freebsd.org Sat Apr 15 09:18:53 2017 Return-Path: Delivered-To: freebsd-current@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 325B9D3F6B5 for ; Sat, 15 Apr 2017 09:18:53 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B682BAE; Sat, 15 Apr 2017 09:18:51 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.138.9]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MBFgr-1crIxp05rx-00AAvR; Sat, 15 Apr 2017 11:18:48 +0200 Date: Sat, 15 Apr 2017 11:18:41 +0200 From: "O. Hartmann" To: Konstantin Belousov Cc: "O. Hartmann" , Alan Somers , FreeBSD CURRENT Subject: Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd) Message-ID: <20170415111841.0c34be88@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170414171857.GK1788@kib.kiev.ua> References: <20170414175246.2353dcf0@thor.intern.walstatt.dynvpn.de> <20170414185827.1ab68398@thor.intern.walstatt.dynvpn.de> <20170414171857.GK1788@kib.kiev.ua> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/U_7E9_slqHqr/SBsLaZ4do6"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:RHbOe7pGoWcBYzXDYiAItRIbe6BQ+zqFwbfUnzM22PuTx2wgtbF WWWBVk6gdQaHaQVchIKxwDvYMVCGracCCG2iAzcNc9b1A/OxFX19SLU7bk+J4T3iuGuC3ru 0Cf4MAadUw6oWL9OkcQe3YtMyxngcGk2n1LtpzBFGUVATMsvWTq3Lll/Q29GdhahUQCO5fu wIeSHS8DhryweLillEe0A== X-UI-Out-Filterresults: notjunk:1;V01:K0:NpXDBTCbCHw=:JHULKD13NDhYTfDXcxYvH9 7jI0ADUA9JzrcS3k8VsmJUV6IYoYV648cTXkLATBeKaPVG3FX2x42rajNJG3DvdAS3WynsKm2 za8Fmi/pDNIucR6FCmwF05tgTF1S/rWuNZ+5OoDoDfos/D71uofMUGk8EbVOaSbjphIxyU2u7 V2jB97W+CefGRpXaXAl2zclv35z78RUiw/iSHkZY+qcRm/oWbi1q/0ti5ACVoIGRBBVq8V8A3 I7biNF5xCHDMWE533N3UDAjaqduN3E6QHePvgmLg0GEqGVPlwJogNek72bH5Qjuy6wJx7kbNO xCHVGCedUG8F6CpQm7caurnCYGbLN0RAU7ENk5BlxVdoqmKLKID/dhOQAvfBMRwapkX8ZWXLj NJ2ELMm6DFv3y8O52SMOlge2CG6W8Iv5Qu7ssru3U74P9i/V42AExmD3ngs1cgs5HQz2f8ub+ ZjwTf28E31+cCH+nuUJwNUgb/zO00FtstXahNA3d1fuHJsFJC7J/JzVj2DWSNeDmh0CpaWyPG h+qLmgoHo13W106Q4k3010hZ91uS6/QD/K9JVrREM0W+nDvF3xCgOog95+oBTVg8qqXB1k9aJ siXX+lBAnO6fG9DMYgG+cH1TGtly5dLREen/30SUDm4JVO9bNpFOXJoe2845JOmAkh2Zp5Ups HU1UEXQgfneAiAlRSmCR9xLJQ6x8JJg1sZUxaCRwjCwQpmcucOAxIzsOIOKaZTDMehAhG1ilv hdnljoYgyCawhX20z1XYmJ+Akg0HhbNt9VKTjIazjY5Ed5YMb+vtxXEGNb8= X-Mailman-Approved-At: Sat, 15 Apr 2017 11:30:31 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 09:18:53 -0000 --Sig_/U_7E9_slqHqr/SBsLaZ4do6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Fri, 14 Apr 2017 20:18:57 +0300 Konstantin Belousov schrieb: > On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: > > Fatal trap 12: page fault while in kernel mode > > cpuid =3D 2; apic id =3D 02 > > fault virtual address =3D 0xfffff8001282fb00 > > fault code =3D supervisor read instruction, protection vio= lation =20 >=20 > > ??() at 0xfffff8001282fb00 > > bpf_mtap() at bpf_mtap+0x1ab/frame 0xfffffe012d2aefb0 > > iflib_txq_drain() at iflib_txq_drain+0x1383/frame 0xfffffe012d2af130 > > drain_ring_lockless() at drain_ring_lockless+0xc0/frame 0xfffffe012d2af= 190 > > ifmp_ring_enqueue() at ifmp_ring_enqueue+0x32e/frame 0xfffffe012d2af200 > > iflib_if_transmit() at iflib_if_transmit+0xb0/frame 0xfffffe012d2af240 > > ether_output() at ether_output+0x730/frame 0xfffffe012d2af2e0 > > arprequest() at arprequest+0x426/frame 0xfffffe012d2af3e0 > > arpresolve_full() at arpresolve_full+0x3d1/frame 0xfffffe012d2af460 > > arpresolve() at arpresolve+0x10c/frame 0xfffffe012d2af4d0 > > ether_output() at ether_output+0x4e1/frame 0xfffffe012d2af570 > > ip_output() at ip_output+0x14e6/frame 0xfffffe012d2af6b0 > > udp_send() at udp_send+0xab1/frame 0xfffffe012d2af780 > > sosend_dgram() at sosend_dgram+0x3e4/frame 0xfffffe012d2af7f0 > > kern_sendit() at kern_sendit+0x229/frame 0xfffffe012d2af890 > > sendit() at sendit+0x1a7/frame 0xfffffe012d2af8e0 > > sys_sendto() at sys_sendto+0x4d/frame 0xfffffe012d2af930 > > amd64_syscall() at amd64_syscall+0x4c2/frame 0xfffffe012d2afab0 > > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012d2afab0 > > syscall (133, FreeBSD ELF64, sys_sendto), rip =3D 0x800b8a5fa, rsp =3D = 0x7fffffffd6b8, > > rbp =3D 0x7fffffffdcc0 --- =20 >=20 > You probably have BPF_JITTER option in your kernel config. Either set > net.bpf_jitter.enable to 0 for now, or remove the option. >=20 > It is due to r316767. The issue is known and a solution is being discusse= d. simply setting "net.bpf_jitter.enable=3D0" in /boot/loader.conf.local doesn= 't help, the Trap 12 still occurs. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/U_7E9_slqHqr/SBsLaZ4do6 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPHlcgAKCRDS528fyFhY lJ3EAgCWqAEmNBOiMbmT+BL8AzJ9PM1zZauakSzQJ+qyRyGMjXR+SQwHsrVAhsjv lTYeqLdwZCfnWYWsmft+Tv2rCnkvAf4tv0cTJ8g6DR2+QRMf3ewFGnZU8kFyvIdp JUWDodZ9cvou6AwHk3BX6vpsLZUOB3oW/svnTCRPIRxF+/tA6+Gh =hNIZ -----END PGP SIGNATURE----- --Sig_/U_7E9_slqHqr/SBsLaZ4do6-- From owner-freebsd-current@freebsd.org Sat Apr 15 11:53:42 2017 Return-Path: Delivered-To: freebsd-current@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 D3151D3EFFA for ; Sat, 15 Apr 2017 11:53:42 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 379FAAEB for ; Sat, 15 Apr 2017 11:53:41 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.171.81]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Md3ZK-1chHQ92EGw-00IGIj for ; Sat, 15 Apr 2017 13:53:39 +0200 Date: Sat, 15 Apr 2017 13:53:33 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: r316958: booting a server takes >10 minutes! Message-ID: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/Or=oNYDoPNOaMaP_s468==K"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:PKahzSTvym5a1FSdFmQtT1SHKC5K9v6oh9pAAaZvxYWeCXsKCZv qvei0OlrdZSPBjpq5e2rUS0sPt48mi1Jg65rGaqT8cxAmoXcRj9JwzCOvumVRvtDHDL6N7d ozPk0Ipc3NMQCB4vF5bp4uNVBxhGMwinCvA0r1Af8he3SDK3LVDX2uVtB6eiftd+WJqLVah 0PrzERp/5QLQOH0NyJy5Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:L8Pd9b36DII=:fam32k+GvqrKNz6lJ7HA2y 4oVngrbXbt0ZxBceWaWCyLwd6YgNwne+Rrh4pQFdR5TmFIhaB8pbvCqWkv/+6VZI+4AEfAX4U Ar6H5fJ8HBCzJATVXor5lzwKgfiZFOZ9FdJTbBI7wyLAFenqwLlSsjFAbJoqI5plecCdqWr9I K5ic9YGqjqDymqkaHBR4ZIfNBZPSKrhBiov4n8fjq3V8+z2FV39yAfcTnSds0WdU9LPq1tOtR UDeIujLts3+kC1g3KaepyR/snt7+TsiWEj12wwBTJt3cKwtvYLBVNgv7K/O5ItmfjZ7SFXL8r 4YMu4g6//9n6loCD6UnbqtdrZS0odgYHsIlT8eGbPX6Nlb8t0tOAKYX5ZTx5qW1CaRydXpYTr RI0LjeVqzjvMZYiPpYO6KljPeLwyVb0KKwqUJpwUL50FwNwoS5HxWw48oc7Ut64rSFMWaJlKw 3h/GeGeYXk7c2k/pFoMKS/olwoHeChSKtLTM+7uGaLJbqvvPkSMGdSroRhRkOphMry6QJFDqA fXPt0cGQ8Ut3zdlnqpPGYY/Vl+LAif/FlSgpoZcvchYhShBsT2dA+cTnqOVmSMZJktNeVLDgt 3XDowJCE62RRB63Nh3GU3ARpXoXVzEawLDgcTuma5JsbIit2g0EQOusJeYSXTRQoFE05DeMM2 6qr1ztAMP1V+441BVZKnxHjKYbsgxj5uHDpRZugo2Al6CV01SMnwebKoJiuEovv0kWoXmF1Sv PBXU4XUXksNByanPDU9IG5kAgC9Ckt9ArOZsBUAMoqmDcUB61aC8I2VVMIY= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 11:53:42 -0000 --Sig_/Or=oNYDoPNOaMaP_s468==K Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Recent CURRENT running on a server makes the system booting in multiuser mo= de booting incredibly slow! On a machine, before I interrupted the booting process han= ging in starting postgresql 9.6.2 server, it took > 10 minutes. Due to a serious bug in CURRENT, I had to disable BPF_JITTER via sysctl net.bpf_jitter.enable=3D0 The box also is a syslog "receiving" server for other hosts, syslogd's opti= on "-s" isn't used (just for the record). I'm back to r316717 now which boots the box fine. Booting in single-user mode is also quick as expected. oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/Or=oNYDoPNOaMaP_s468==K Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPIJvQAKCRDS528fyFhY lEbmAf4/Y1gbmBJkU6fhnN9KHVN5uWkPKnnsLgsouUj0YlVaahFto6Y/Vq2xScX5 kFWlCi9eBmRYdmYBU59y3evzMGk1Af0bdI4DHfL0RCxppnh1WeKmwcM3YQpkXwnk NAXMoFsqw6laGtrDplHfoaGcJG8xXP67nvUGAk+k7lAWqIJ0cXij =UOOl -----END PGP SIGNATURE----- --Sig_/Or=oNYDoPNOaMaP_s468==K-- From owner-freebsd-current@freebsd.org Sat Apr 15 12:02:19 2017 Return-Path: Delivered-To: freebsd-current@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 73981D3CBF1 for ; Sat, 15 Apr 2017 12:02:19 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 540AF2E3 for ; Sat, 15 Apr 2017 12:02:19 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To: References:Message-ID:To:From:Subject:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=9nfrlSYDOq4xqAyKy45VwYMoz28qWahOHgwyqS9AApU=; b=g9hVrherJ3H0d/mCWAMMymQwIQ 0YusPE7ZFDsXihwc1VQmhAcP137O6hCxRRmJNvO7NQmf+FaZ01JjBCN/fW4YUT0UiJ0rbLQlf1QQ+ Fp0FpKxc0OFR90zPwpGXHx1SIbkGpy8GhVeBPdz2LdVcOY9itnT6p9Qb7vA6jfxxjej8=; Received: from [47.220.164.50] (port=50155 helo=[192.168.200.198]) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1czMPB-000Ln2-QU; Sat, 15 Apr 2017 07:02:17 -0500 User-Agent: Microsoft-MacOutlook/f.21.0.170409 Date: Sat, 15 Apr 2017 07:02:16 -0500 Subject: Re: r316958: booting a server takes >10 minutes! From: Larry Rosenman To: "O. Hartmann" , FreeBSD CURRENT Message-ID: <2C4F83FA-DEDC-40BD-A4F6-FFC13876338E@lerctr.org> Thread-Topic: r316958: booting a server takes >10 minutes! References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 12:02:19 -0000 On 4/15/17, 6:53 AM, "O. Hartmann" wrote: Recent CURRENT running on a server makes the system booting in multiuse= r mode booting incredibly slow! On a machine, before I interrupted the booting process= hanging in starting postgresql 9.6.2 server, it took > 10 minutes. =20 Due to a serious bug in CURRENT, I had to disable BPF_JITTER via sysctl net.bpf_jitter.enable=3D0 =20 The box also is a syslog "receiving" server for other hosts, syslogd's = option "-s" isn't used (just for the record). =20 I'm back to r316717 now which boots the box fine. =20 Booting in single-user mode is also quick as expected. =20 oh =20 --=20 O. Hartmann =20 Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs. 4 B= DSG). I=E2=80=99m seeing similar, and HAVE the syslogd patch applied. =20 My system seems to hang with PostgreSQL taking a LONG time to come up, I al= so saw sshd/exim and other processes spinning on a =E2=80=9CNo Bufferspace availab= ile=E2=80=9D (from a truss, no I don=E2=80=99t have the output).=20 Something=E2=84=A2 is seriously not right here. =20 From owner-freebsd-current@freebsd.org Sat Apr 15 12:40:24 2017 Return-Path: Delivered-To: freebsd-current@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 A50D4D3EBA1 for ; Sat, 15 Apr 2017 12:40:24 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 204C91AE6 for ; Sat, 15 Apr 2017 12:40:23 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.171.81]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MeQ43-1cgSIl0Lvz-00QDsA; Sat, 15 Apr 2017 14:40:20 +0200 Date: Sat, 15 Apr 2017 14:40:11 +0200 From: "O. Hartmann" To: Larry Rosenman Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: r316958: booting a server takes >10 minutes! Message-ID: <20170415144011.594ef11e@thor.intern.walstatt.dynvpn.de> In-Reply-To: <2C4F83FA-DEDC-40BD-A4F6-FFC13876338E@lerctr.org> References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2C4F83FA-DEDC-40BD-A4F6-FFC13876338E@lerctr.org> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/S2=sxiZJy7KJzGKV8C1wQVV"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:tuE18OkrrlW9g18V5ppaZ4aFHH6lrHBq0kH1+YWVrq2Ow2CHMAX vri0152XBLUtpxzpXInxXIPjeU3SCsnMNSJlJdKW8fXdteGot35HzMnl0v7/FavOguM/ra+ TEy89RO7/iGn1UKJxLiD/LOjiw0jjRVRnDunxUFhRR9wol4IC9jpdkuhaWaNAhi84pHTD36 6IbnK+jNLX0bk6AFQG+uw== X-UI-Out-Filterresults: notjunk:1;V01:K0:o6wtNL+qIEY=:cWaIdgz0MCousGjLCN6P7D Dmrl0rYHPh1D8LGVz+Zclq3xm3MXAcU+mVhp8Doj8zomSBmEPDMo1lyDV5AO1b4GDAIOndb1/ ti2jKxZUUUymTtfdF9mnOElJJo4OtS4eI40Sce0YcL0+o+U5Ln+LE7dMEGOoyzegV8h5nlb+d NqL1+6V59wZmldf55nMkIIEOrfZfgxbBuxHXWuww7H8/dQSCm2zPRKXXVX7a2h8SimDnIQ1GH 49GVeqti141t/tXDAPWrKyjNdmsOE90AB35uC8AjXgOCDyXzR71li6spHD40eJW7/fG6ISbbB aJmwrdB3NF8CZ1ycvKaedPeBguuFw1RDkpBTje5TaT5QA7L1NRqb0wgAZUnifGWc9QXcHU1jg 5LXVw8iYm9uxW0DbiX1HvpfFkVZYiXMov1JZDmcVOsIhDGG47iALgjeYqHZZdIyH0q6jArWuw oYlN7SNmAXf+kpXChRaOjh11/ebY8T+GyUyo3pQs0MNRCOch7tSaL4Sp5cngmesJo2GYG8dT4 Zgrb9LJ/AkZzlflc+qPfgVp9UL+/0uOx0d70AoS9VReOUil5BKqqGPQzZzfIJK/uBpPBHYUg3 47wdUNBtKu83TO/9RbqfgBehaCDTXKUS8X4VQX65rB1wHSuqDxbYfZreJU27MtXRm7QjF6hC2 5saRMcmfLI6bC8g1Iz6PXvC4paM2bEKrVEsRTDxNzMELy3R0NCV4eRbhR+YrSWebCDsGSEWvl K3FG5lScfCO7Y3FOSs1GYYWeIP/8j7jfMfii4OVBp7bwVp+6Rxe9Di1MNHU= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 12:40:24 -0000 --Sig_/S2=sxiZJy7KJzGKV8C1wQVV Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Sat, 15 Apr 2017 07:02:16 -0500 Larry Rosenman schrieb: > On 4/15/17, 6:53 AM, "O. Hartmann" ohartmann@walstatt.org> wrote: >=20 > Recent CURRENT running on a server makes the system booting in multiu= ser mode > booting incredibly slow! On a machine, before I interrupted the booting p= rocess hanging > in starting postgresql 9.6.2 server, it took > 10 minutes. > =20 > Due to a serious bug in CURRENT, I had to disable BPF_JITTER via sysc= tl > net.bpf_jitter.enable=3D0 > =20 > The box also is a syslog "receiving" server for other hosts, syslogd'= s option "-s" > isn't used (just for the record). > =20 > I'm back to r316717 now which boots the box fine. > =20 > Booting in single-user mode is also quick as expected. > =20 > oh > =20 > --=20 > O. Hartmann > =20 > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3= =BCr > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 2= 8 Abs. 4 BDSG). >=20 >=20 > I=E2=80=99m seeing similar, and HAVE the syslogd patch applied. =20 >=20 > My system seems to hang with PostgreSQL taking a LONG time to come up, I = also saw > sshd/exim and other processes spinning on a =E2=80=9CNo Bufferspace avail= abile=E2=80=9D (from a truss, > no I don=E2=80=99t have the output).=20 >=20 > Something=E2=84=A2 is seriously not right here. >=20 I follow the svc-src-head@ list on the topic: svn commit: r316874 - head/sys/kern which might be the reason for this issue ... oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/S2=sxiZJy7KJzGKV8C1wQVV Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPIUqwAKCRDS528fyFhY lEjdAf0foNe+MB+ZKntZ8uJDgEuK2MantfT/D2NGNGy+zM9bORAqLdqRLIQYnP92 Sgy01KbM9izGhlXaBxpUZqvOUZCDAf0Womu/vrlRgNEdL0Qj6r53oedKh84kcatm 7rrFWsq8g1+/lw7jpSxV+gF1LjB/M4CfftcRuMPlwXdh4pK4+LxT =2Kyw -----END PGP SIGNATURE----- --Sig_/S2=sxiZJy7KJzGKV8C1wQVV-- From owner-freebsd-current@freebsd.org Sat Apr 15 14:36:10 2017 Return-Path: Delivered-To: freebsd-current@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 2800FD3F3A9 for ; Sat, 15 Apr 2017 14:36:10 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward4p.cmail.yandex.net (forward4p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D8FC97DF for ; Sat, 15 Apr 2017 14:36:09 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [77.88.29.86]) by forward4p.cmail.yandex.net (Yandex) with ESMTP id 058EE20D08 for ; Sat, 15 Apr 2017 17:36:06 +0300 (MSK) Received: from smtp3p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp3p.mail.yandex.net (Yandex) with ESMTP id CEE7B1320053 for ; Sat, 15 Apr 2017 17:36:05 +0300 (MSK) Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id CHeHyYUv13-a4waHsGf; Sat, 15 Apr 2017 17:36:04 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1492266964; bh=ZqjY0zrZc1ibiIQWEAgZK53aAMgP9g6LQh1ixYp73p0=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=ckxKaGn5Ez80rfeUtXZ36jx0k8Khfm+2dEnXuwQZ66OZp4KdCYjUyW+0XJ9IioZdA h434131o3Z1s5/EHyUKdDhLySIkOSn8d19o+VMbOEUtX/AVrySWeSzXnfYrgDrNlYZ vJxvHz6vRnVsaO3LlEH0pByEtrDLwrMIPU8KrMM0= Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0 Subject: Re: r316958: booting a server takes >10 minutes! To: freebsd-current@freebsd.org References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> From: Boris Samorodov Message-ID: <3a13cfd2-c7c9-e44a-c608-6f90fca752fb@passap.ru> Date: Sat, 15 Apr 2017 17:36:04 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 14:36:10 -0000 15.04.2017 14:53, O. Hartmann пишет: > Recent CURRENT running on a server makes the system booting in multiuser mode booting > incredibly slow! On a machine, before I interrupted the booting process hanging in > starting postgresql 9.6.2 server, it took > 10 minutes. Same here. BTW, the command "service -e" runs forever and eats CPU. I had to kill sendmail and dbus (which were chewing CPU) and then "service -e" run fine. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve "It is not necessary to change. Survival is not mandatory." From owner-freebsd-current@freebsd.org Sat Apr 15 14:54:02 2017 Return-Path: Delivered-To: freebsd-current@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 1EB24D3FDC6; Sat, 15 Apr 2017 14:54:02 +0000 (UTC) (envelope-from danfe@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 F2171758; Sat, 15 Apr 2017 14:54:01 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 2E9DB539B; Sat, 15 Apr 2017 14:54:01 +0000 (UTC) Date: Sat, 15 Apr 2017 14:54:01 +0000 From: Alexey Dokuchaev To: Matthew Rezny Cc: Dimitry Andric , Mark Millard , Johannes M Dieterich , FreeBSD Current , FreeBSD Toolchain , FreeBSD Ports , FreeBSD PowerPC ML Subject: Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example) Message-ID: <20170415145401.GH97090@FreeBSD.org> References: <3EDEF0B7-59C5-4648-9737-6682E18645BC@dsl-only.net> <2502554.oHoOYGyFJH@workstation.reztek> <20170405161541.GA32323@FreeBSD.org> <2629274.jcOtFEnjsX@workstation.reztek> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2629274.jcOtFEnjsX@workstation.reztek> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 14:54:02 -0000 Sorry Matthew, forgot to reply to this one. On Wed, Apr 05, 2017 at 07:01:35PM +0200, Matthew Rezny wrote: > On Wednesday 05 April 2017 16:15:41 Alexey Dokuchaev wrote: > > ... > > Hmm, I don't quite get it: shouldn't static linking actually increase > > the binaries (and thus the package) size? > > I might have reversed static and shared somewhere in the linking > explanation, or not properly described the situation. [...] Understood, makes sense now. > There was a brief period in which llvm39 was fully switched to dynamic > linking, which made it considerably smaller but caused runtime problems > (and was also likely to be slower). That still sounds like the most sane way to go; provided those problems are/would be fixed, I hope for that switch to happen again one day. (I somewhat doubt that "slower" was noticeable enough to worry about.) > The best solution to cut rebuild time for LLVM is ccache. Indeed, ccache helps greatly. Now that I've managed to cut down package times as well, situation with LLVM ports no longer looks as bad as I originally saw it; thank you. ./danfe From owner-freebsd-current@freebsd.org Sat Apr 15 16:00:34 2017 Return-Path: Delivered-To: freebsd-current@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 9EB1DD3FA78 for ; Sat, 15 Apr 2017 16:00:34 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 6925C22A for ; Sat, 15 Apr 2017 16:00:34 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 69606273DF; Sat, 15 Apr 2017 16:00:26 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id v3FG0Psp002322; Sat, 15 Apr 2017 16:00:25 GMT (envelope-from phk@phk.freebsd.dk) To: "O. Hartmann" cc: FreeBSD CURRENT Subject: Re: r316958: booting a server takes >10 minutes! In-reply-to: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> From: "Poul-Henning Kamp" References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2320.1492272025.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sat, 15 Apr 2017 16:00:25 +0000 Message-ID: <2321.1492272025@critter.freebsd.dk> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 16:00:34 -0000 -------- >Recent CURRENT running on a server makes the system booting in multiuser = mode booting >incredibly slow! On a machine, before I interrupted the booting process h= anging in >starting postgresql 9.6.2 server, it took > 10 minutes. Maybe this ticket ? https://lists.freebsd.org/pipermail/freebsd-ports/2017-April/108144.html -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-current@freebsd.org Sat Apr 15 16:09:19 2017 Return-Path: Delivered-To: freebsd-current@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 7B846D3FD17 for ; Sat, 15 Apr 2017 16:09:19 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 27DAE9F4 for ; Sat, 15 Apr 2017 16:09:17 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v3FG9Gi7089097; Sat, 15 Apr 2017 16:09:16 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v3FG9GEJ089096; Sat, 15 Apr 2017 09:09:16 -0700 (PDT) (envelope-from david) Date: Sat, 15 Apr 2017 09:09:16 -0700 From: David Wolfskill To: Poul-Henning Kamp Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: r316958: booting a server takes >10 minutes! Message-ID: <20170415160916.GY1326@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Poul-Henning Kamp , "O. Hartmann" , FreeBSD CURRENT References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2321.1492272025@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RrnDFcckYBZtnE5W" Content-Disposition: inline In-Reply-To: <2321.1492272025@critter.freebsd.dk> User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 16:09:19 -0000 --RrnDFcckYBZtnE5W Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 15, 2017 at 04:00:25PM +0000, Poul-Henning Kamp wrote: > -------- >=20 > >Recent CURRENT running on a server makes the system booting in multiuser= mode booting > >incredibly slow! On a machine, before I interrupted the booting process = hanging in > >starting postgresql 9.6.2 server, it took > 10 minutes. >=20 > Maybe this ticket ? >=20 > https://lists.freebsd.org/pipermail/freebsd-ports/2017-April/108144.html > ... I doubt it: While I encountered the observed symptom, that was not until today's build of head (r316956, in my case); yesterday's (r316823) was fine. And I understand that the Cloudflare/f-root server issue isn't quite that recent: "The new f-root servers appeared around two weeks ago...." Peace, david --=20 David H. Wolfskill david@catwhisker.org Who would have thought that a "hotelier" would be so ... unwelcoming? Sad. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --RrnDFcckYBZtnE5W Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJY8kWsXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XnFcH/2Or+a7TDNgaTIlW5leYZyzc OYEX8JJb1vra/nnigEP/q6E8i21MvRpdj4IlQcCdMuJNQr03ZiiZIaH+AWvKDSOM wQPF+NHPCfNxicrDX84MkeUsGEHkcwBABB3zc6BN1iwz9ePHb7MWA/ExfeaIG5jL Jr0EzTmDGS37+F+mQ47fbHQCQ7E6uFnLRVNK/bCtVVUek9XQa3jX9iKN9Hp2MJyp O7GmWc7K9p9HsFF7yYLuv9kLtAtiDM8/mIQYwiHmyn85ii3rV4Yk8QcjkxkLCVqx Q2/S3hinsumX7DJCWm6hqJPCTW0Fy2pVVD2gtBRJrQcRI91OSlwCihHv4afd/zs= =RHs1 -----END PGP SIGNATURE----- --RrnDFcckYBZtnE5W-- From owner-freebsd-current@freebsd.org Sat Apr 15 16:19:27 2017 Return-Path: Delivered-To: freebsd-current@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 AA8D4D3F072 for ; Sat, 15 Apr 2017 16:19:27 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 85643F8F for ; Sat, 15 Apr 2017 16:19:27 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 95565D05B for ; Sat, 15 Apr 2017 16:19:19 +0000 (UTC) Subject: Re: r316958: booting a server takes >10 minutes! To: freebsd-current@freebsd.org References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> From: Allan Jude Message-ID: Date: Sat, 15 Apr 2017 12:19:02 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OVdLB94MCQNKU4KGTMH2d7sFoKLr3XaQJ" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 16:19:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OVdLB94MCQNKU4KGTMH2d7sFoKLr3XaQJ Content-Type: multipart/mixed; boundary="hMI632gfi89wQA5ExPwbDrlcdoOGsdXs3"; protected-headers="v1" From: Allan Jude To: freebsd-current@freebsd.org Message-ID: Subject: Re: r316958: booting a server takes >10 minutes! References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> --hMI632gfi89wQA5ExPwbDrlcdoOGsdXs3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2017-04-15 07:53, O. Hartmann wrote: > Recent CURRENT running on a server makes the system booting in multiuse= r mode booting > incredibly slow! On a machine, before I interrupted the booting process= hanging in > starting postgresql 9.6.2 server, it took > 10 minutes. >=20 > Due to a serious bug in CURRENT, I had to disable BPF_JITTER via sysctl= > net.bpf_jitter.enable=3D0 >=20 > The box also is a syslog "receiving" server for other hosts, syslogd's = option "-s" isn't > used (just for the record). >=20 > I'm back to r316717 now which boots the box fine. >=20 > Booting in single-user mode is also quick as expected. >=20 > oh >=20 Is it stalled in a specific place? --=20 Allan Jude --hMI632gfi89wQA5ExPwbDrlcdoOGsdXs3-- --OVdLB94MCQNKU4KGTMH2d7sFoKLr3XaQJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJY8kgGAAoJEBmVNT4SmAt+gIIQANGIjTP8eTqjg7GG2LV1qv3w uP8dnW6fU6rTZwVlS9qeGXT00W9qaMztzcMVrniGuyfRl4piFWvO/9dRQzYgTvO7 XEbqnszlwEDZV1GeuKaTH0P+yw09IC4TBemH8vF8ZVXrFMXhNnszjxr2vtF+dBLB zAxIS6FPjftfrGuv2AhreRy6Z7Wzo/CpK+5pXv0RPZiV2XoLld61lGYTFi44v610 Fch8ss8hVkV77BIaoXxj4gnbS/r5i5l6TEoqZ/ssMiCXNzcBRv+gxeQ92MPSYCfJ hKYNOfQQZy6RAHgiAH2PsLSNULVLHH05HY3dEJKkUYeUCSBVabcFSUMeSKIyDjOn fTP7vUhKC57HrR2dsC9apqqRqKAndXu1NwrNxALpDfMDCdn/AyH3xfJ9m90Yf0Cc MLnynfCT+fGP5sh9nFjcME2rxV1dZSEAMsIgu54wMvZ6sajhD5uZaifnvkc9+6nz QSqDLzDfNZT5r0bDac9FrFj+D4+8eFVrcPYt8DLs4aY/RBZrD5XwSoIflgCtX7yi l/ghmfIwAQkGzYNukTcacFDQ+Qho7Td+VwiKEeEsCkZqYvpvmmuskuBWP+VHvoWq dwxHlZaAAk09Oxo0z4JGlib1tduMy2rt8UEtHxA2ALwmYcuLz6AjpmfhFfzuJQm+ spoAF3UXStXacd7hxax5 =D/n7 -----END PGP SIGNATURE----- --OVdLB94MCQNKU4KGTMH2d7sFoKLr3XaQJ-- From owner-freebsd-current@freebsd.org Sat Apr 15 16:41:30 2017 Return-Path: Delivered-To: freebsd-current@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 723CCD3F7F6 for ; Sat, 15 Apr 2017 16:41:30 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 3B4402F9 for ; Sat, 15 Apr 2017 16:41:30 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id A02F6273AA; Sat, 15 Apr 2017 16:41:28 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id v3FGfSwU004293; Sat, 15 Apr 2017 16:41:28 GMT (envelope-from phk@phk.freebsd.dk) To: David Wolfskill cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: r316958: booting a server takes >10 minutes! In-reply-to: <20170415160916.GY1326@albert.catwhisker.org> From: "Poul-Henning Kamp" References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2321.1492272025@critter.freebsd.dk> <20170415160916.GY1326@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4291.1492274488.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sat, 15 Apr 2017 16:41:28 +0000 Message-ID: <4292.1492274488@critter.freebsd.dk> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 16:41:30 -0000 -------- In message <20170415160916.GY1326@albert.catwhisker.org>, David Wolfskill = write s: >And I understand that the Cloudflare/f-root server issue isn't quite >that recent: "The new f-root servers appeared around two weeks ago...." And isn't the zone cache expiry time around two weeks as well ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-current@freebsd.org Sat Apr 15 18:01:12 2017 Return-Path: Delivered-To: freebsd-current@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 98B50D3F755 for ; Sat, 15 Apr 2017 18:01:12 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 69353F72 for ; Sat, 15 Apr 2017 18:01:12 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1492279270; bh=/rev/eSv DMC7XGx+Bems+NRkAX+RMTXwx/g9rOVUSO0=; b=WsbxzC5bllgNYfTKdN4lVm/m KUuq9S4693QbQuUsbxG64dvDxhv9jKUY6z1mPYyon/DEKO0GwOZDl77Mcg0EVe3Y Nwpt8wBir4LGFQyjexwpO5SkdRXuzvL5A4YtZ7HyLxpXUYv/6YNh7ND6nbR6ciPW IsmNwutJg+Qeke49QG4= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 8CC263C44 for ; Sat, 15 Apr 2017 14:01:10 -0400 (EDT) Subject: Re: r316958: booting a server takes >10 minutes! To: freebsd-current@freebsd.org References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2321.1492272025@critter.freebsd.dk> <20170415160916.GY1326@albert.catwhisker.org> <4292.1492274488@critter.freebsd.dk> From: Michael Butler Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492 Message-ID: <175cf4c2-e61c-ec63-adc2-e963b6420695@protected-networks.net> Date: Sat, 15 Apr 2017 14:01:10 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <4292.1492274488@critter.freebsd.dk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 18:01:12 -0000 On 04/15/17 12:41, Poul-Henning Kamp wrote: > -------- > In message <20170415160916.GY1326@albert.catwhisker.org>, David Wolfskill write > s: > >> And I understand that the Cloudflare/f-root server issue isn't quite >> that recent: "The new f-root servers appeared around two weeks ago...." > > And isn't the zone cache expiry time around two weeks as well ? Sure, but none of my name-servers were doing root zone-transfers and, when I restarted this morning, only a few of my jails would come up. Reverting to a kernel previous to SVN r316874 restored normal start-up, imb From owner-freebsd-current@freebsd.org Sat Apr 15 18:43:34 2017 Return-Path: Delivered-To: freebsd-current@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 2095BD3F7B8 for ; Sat, 15 Apr 2017 18:43:34 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 BF333F5A for ; Sat, 15 Apr 2017 18:43:33 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v3FIhV8o090924; Sat, 15 Apr 2017 18:43:31 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v3FIhVGq090923; Sat, 15 Apr 2017 11:43:31 -0700 (PDT) (envelope-from david) Date: Sat, 15 Apr 2017 11:43:31 -0700 From: David Wolfskill To: Poul-Henning Kamp Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: r316958: booting a server takes >10 minutes! Message-ID: <20170415184331.GB1326@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Poul-Henning Kamp , "O. Hartmann" , FreeBSD CURRENT References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2321.1492272025@critter.freebsd.dk> <20170415160916.GY1326@albert.catwhisker.org> <4292.1492274488@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tAUcVu0bGQSXS+ov" Content-Disposition: inline In-Reply-To: <4292.1492274488@critter.freebsd.dk> User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 18:43:34 -0000 --tAUcVu0bGQSXS+ov Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 15, 2017 at 04:41:28PM +0000, Poul-Henning Kamp wrote: > -------- > ... > >And I understand that the Cloudflare/f-root server issue isn't quite > >that recent: "The new f-root servers appeared around two weeks ago...." >=20 > And isn't the zone cache expiry time around two weeks as well ? > .... Regardless, I observe that my laptop was (somewhat) affected by this, but my build machine did not appear to be affected. The build machine has very few ports install, runs a GENERIC kernel, and normally runs headless, while the laptop normally runs xdm and has my (somewhat old-fashioned) set of ports for a user-facing machine. But among the ports on which X11 depends is dbus, and dbus-daemon was one of the processes that was apparently spinning in CPU without evidence of accomplishing much of anything, so the X11 environment wasn't usable. (I was able to login to and use a vty on the laptop, though.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Who would have thought that a "hotelier" would be so ... unwelcoming? Sad. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --tAUcVu0bGQSXS+ov Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJY8mnTXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XSNcIAMiWHBAkLHST9eh95DxC9zm0 2kG3ZBl8eSg3NX6AlMMy4nwXzbXUgsw4Fa9sLc3qJKD0egAIt2x6DJOLuAzsg365 6LmSkpO36p/2Jgw0J1MNmt4MIRlJ5+ZGb/DjZH50+W0/Gz6F1a6uBXPtkEt5s3pR eBu07i6yebmFH5P9aYFdRVeqs2717vJBvJ+DKHZsllKCophlFr1HVOxgQgFZxKq/ wp1Blt8RvqSOKJneBQ8AN5xQu+CHDJmTtgP1N2mPb50Pqf0QCNDAA2XlLoZ2PXnb xyKpKFtlrUoARkuW/4/JB5i7q1t2L5HS3BnLVviq+krWvkGO1Vt0HSQ0P21nnsM= =F258 -----END PGP SIGNATURE----- --tAUcVu0bGQSXS+ov-- From owner-freebsd-current@freebsd.org Sat Apr 15 19:00:22 2017 Return-Path: Delivered-To: freebsd-current@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 870DDD3FAF8 for ; Sat, 15 Apr 2017 19:00:22 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 658039D9 for ; Sat, 15 Apr 2017 19:00:22 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To: References:Message-ID:CC:To:From:Subject:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Nk3mySNmSQKm8S/RDvQMRXpaBwn3iuk5oHeKQT7bxOQ=; b=fZpadwEHwLeHM+GfTohYgqm4CG /vq1q5gyRxyEuo5nrcvYkMV0JBCE0tFKQ8Rh4HOKajvT9ScnK3zsenkjQd2Yv0CHafNllK59qc2ma zwDXIOuw1TOjMOwnaiSiUrIifCjE4S1Q2e3AuL0O0pFgRXQ+1RO6xiAR+Qs7OEa9G3YI=; Received: from [47.220.164.50] (port=6615 helo=[192.168.200.198]) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1czSvf-0008ve-32; Sat, 15 Apr 2017 14:00:15 -0500 User-Agent: Microsoft-MacOutlook/f.21.0.170409 Date: Sat, 15 Apr 2017 14:00:13 -0500 Subject: Re: r316958: booting a server takes >10 minutes! From: Larry Rosenman To: David Wolfskill , Poul-Henning Kamp CC: "O. Hartmann" , FreeBSD CURRENT Message-ID: <3E0D0513-0337-40E1-8173-11D845C0EFF4@lerctr.org> Thread-Topic: r316958: booting a server takes >10 minutes! References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2321.1492272025@critter.freebsd.dk> <20170415160916.GY1326@albert.catwhisker.org> <4292.1492274488@critter.freebsd.dk> <20170415184331.GB1326@albert.catwhisker.org> In-Reply-To: <20170415184331.GB1326@albert.catwhisker.org> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 19:00:22 -0000 On 4/15/17, 1:43 PM, "David Wolfskill" wrote: On Sat, Apr 15, 2017 at 04:41:28PM +0000, Poul-Henning Kamp wrote: > -------- > ... > >And I understand that the Cloudflare/f-root server issue isn't quite > >that recent: "The new f-root servers appeared around two weeks ago..= .." >=20 > And isn't the zone cache expiry time around two weeks as well ? > .... =20 Regardless, I observe that my laptop was (somewhat) affected by this, but my build machine did not appear to be affected. =20 The build machine has very few ports install, runs a GENERIC kernel, and normally runs headless, while the laptop normally runs xdm and has my (somewhat old-fashioned) set of ports for a user-facing machine. But among the ports on which X11 depends is dbus, and dbus-daemon was one of the processes that was apparently spinning in CPU without evidence of accomplishing much of anything, so the X11 environment wasn't usable. (I was able to login to and use a vty on the laptop, though.) =20 Peace, david As was my HOME server which does NOT do ANY DNS services (It=E2=80=99s a DNS Clie= nt, DHCP Client).=20 It was with PostgreSQL starting and I also noted Exim, SSHD, and others spi= nning. Lots of NO BUFFERSPACE in a truss.=20 I suspect it=E2=80=99s related to UDP changes in the system.=20 =20 From owner-freebsd-current@freebsd.org Sat Apr 15 18:56:38 2017 Return-Path: Delivered-To: freebsd-current@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 46E50D3FA79 for ; Sat, 15 Apr 2017 18:56:38 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9125C977; Sat, 15 Apr 2017 18:56:36 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.171.81]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MP0LT-1cvuEE1kl5-006Lx0; Sat, 15 Apr 2017 20:56:29 +0200 Date: Sat, 15 Apr 2017 20:56:18 +0200 From: "O. Hartmann" To: Allan Jude Cc: freebsd-current@freebsd.org Subject: Re: r316958: booting a server takes >10 minutes! Message-ID: <20170415205618.75514254@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/J31ASitu_82ZEq.agIWTyOP"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:bs3TLGsE7VLsatzVLi+Q9OvP/mOy5Y9n91rW/YVoLzi0eM2E9dz GidQ4ItPeeyVARFg2MUqZPpUmQnnugy0y7B8t9DWR1gM2M4uK/8DndCUvjRyxPaZebU0K9z r0BqDaCb3UcVPy1WUT5m4bqYg5MGWki+7COi5vXvtCKSkP1AvPx/DiON5qQpqIsqmD4pOJu cbOomkB1E8ALujEEinX7Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:dXCmksn3f68=:t54nnqyn/biR7bjYbrOWv3 SiHgSGaPxdnvLIYyy5WcJXuSVkUs+GZB4b+/2GfESuKYzmAde3/IFFNtIG6WN5YzC/Z7QdaNK N7gSbhVjpYUTcjXfZKYtq+w7MJC3V9ZZPSNNqZBRP4eWmuWvrgo3l0uAhI/Ki0zliqy+Ww7Kf +eltoZoQM2FjCcxHxUyxLSPvZxDWzLO9xg+T1+LZfa1+ADIWiCXnX4y1mDMz7bzvh2Y8Yt6Ot md7Q2g0eJu9RVuud2oCTwjinh/dxFg/Bbn+VcYHUyl4fpZzmqFq0A3oSjmLfCjGKAfkdWQYxw TcjfZp7CuT8z5Z+JoSAkK+jS4VsIf+n8w0hXS1tI5fzbKMBHYkOJzUuM/s19Ppa1Mb9vmjAQy mOkTerdlgWiHTqHYY2HTMJM4t2p88BQF3nW32mJlQiKbxFy9w0Q8eP7LDasurGRrlgDTVoN72 FKTAT/BFb0QMGXlQu5feU/XBAqMA464aJA5gh1SJE8CwQsEYjqHwX0KR5f9Eo4cTktGtWWRUE OaRAjaDUVIeQ0V5YZH39LMOMdVWO1ctql7ZmxyCKiaUdLpwTK0ZBwGa4l7uVE8zyScb0TGRt1 m2ikK37FgY5HbRXp0kVqHFo+/IV7bA/lMB+r89bXvV9LOiEr3Z4b2Sp7EDPffbZfxOppqFdEr E/jc7pfrTjCEiHXGUmfyecldCQsHQ+YqT3foH25aFNc5KUXNMpPKnPCPy71r9DUymrGl2DrVV pXuvUhcRi1GWFsvlRzkvkNK1lRPeaPEzUpTDMtdW0Wki/2nj+X+xrQTk5bM= X-Mailman-Approved-At: Sat, 15 Apr 2017 19:11:43 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 18:56:38 -0000 --Sig_/J31ASitu_82ZEq.agIWTyOP Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Sat, 15 Apr 2017 12:19:02 -0400 Allan Jude schrieb: > On 2017-04-15 07:53, O. Hartmann wrote: > > Recent CURRENT running on a server makes the system booting in multiuse= r mode booting > > incredibly slow! On a machine, before I interrupted the booting process= hanging in > > starting postgresql 9.6.2 server, it took > 10 minutes. > >=20 > > Due to a serious bug in CURRENT, I had to disable BPF_JITTER via sysctl > > net.bpf_jitter.enable=3D0 > >=20 > > The box also is a syslog "receiving" server for other hosts, syslogd's = option "-s" > > isn't used (just for the record). > >=20 > > I'm back to r316717 now which boots the box fine. > >=20 > > Booting in single-user mode is also quick as expected. > >=20 > > oh > > =20 >=20 > Is it stalled in a specific place? >=20 No. It seems erratic and involves diffrent services which are about to be s= tarted. slapd, mountd for instance take longer as expected, postgresql takes a very long t= ime, usually I have to terminate starting via Ctrl-C. But longest seems to be postgresql. = Ctrl-C kills starting, but then, something spins forever and Ctrl-T says, that "sh" does= something - not sure what or I didn't remember. I switched back to a working revision. oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/J31ASitu_82ZEq.agIWTyOP Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPJs0gAKCRDS528fyFhY lIdcAfoDQbQIW4MVRaRrKn7pNOGJ3o2jjzUieRX6lT5TsieYhThHkJj7EyMM8Th4 ywUjdBzuhzf7oZVhFgWBueuKBgRXAf9gRD7FvQGFFnae7UYj/9lIOubV0GEO2pzu plQDaUiBHdfP6HPhclIeI0tx84dpD2MSYRQ1MUqy522z3Oit1tIu =VMrS -----END PGP SIGNATURE----- --Sig_/J31ASitu_82ZEq.agIWTyOP-- From owner-freebsd-current@freebsd.org Sat Apr 15 19:13:28 2017 Return-Path: Delivered-To: freebsd-current@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 3ED20D3F23B for ; Sat, 15 Apr 2017 19:13:28 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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 028809DD for ; Sat, 15 Apr 2017 19:13:28 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1czT8T-0005ZK-Mx; Sat, 15 Apr 2017 21:13:29 +0200 Date: Sat, 15 Apr 2017 21:13:29 +0200 From: Kurt Jaeger To: Larry Rosenman , FreeBSD CURRENT Subject: Re: r316958: booting a server takes >10 minutes! Message-ID: <20170415191329.GA74780@home.opsec.eu> References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2321.1492272025@critter.freebsd.dk> <20170415160916.GY1326@albert.catwhisker.org> <4292.1492274488@critter.freebsd.dk> <20170415184331.GB1326@albert.catwhisker.org> <3E0D0513-0337-40E1-8173-11D845C0EFF4@lerctr.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E0D0513-0337-40E1-8173-11D845C0EFF4@lerctr.org> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 19:13:28 -0000 Hi! Larry wrote: > It was with PostgreSQL starting and I also noted Exim, SSHD, and > others spinning. Lots of NO BUFFERSPACE in a truss. Interesting. I had my build host being dead in the network (no ping, also with bufferspace problems), but I was able to login via console. And: It failed to shutdown/reboot properly, with some 200+ unclean blocks, trying to get them on disk in an seemingly endless loop. I had to hard-reset the box. But: It's older, r315141. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-current@freebsd.org Sat Apr 15 19:24:08 2017 Return-Path: Delivered-To: freebsd-current@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 A13A3D3F9C7 for ; Sat, 15 Apr 2017 19:24:08 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 66A043AB for ; Sat, 15 Apr 2017 19:24:06 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To: References:Message-ID:To:From:Subject:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=qwEflVihK1zSInCKEiY77NHanMW2IO2cnWAd00wqdLE=; b=uyVItPw+JeMGxSzrQO6CMjvmXO Kw4IQmVsWapVP2q2DNQ6hXVVoZ8GVBvbnc+jp9ThcP+N9veUTowWN2Fx2xiHC0Pk0Tf3d/vdXImOJ p2ebzzFzVSHJl8oEjAJIwMdAutfjX/5G/L8RkF3JInXkBwXc2+YjpXXixN/tYrZ0UlOQ=; Received: from [47.220.164.50] (port=64281 helo=[192.168.200.198]) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1czTIj-0009Y5-B1; Sat, 15 Apr 2017 14:24:05 -0500 User-Agent: Microsoft-MacOutlook/f.21.0.170409 Date: Sat, 15 Apr 2017 14:24:05 -0500 Subject: Re: r316958: booting a server takes >10 minutes! From: Larry Rosenman To: Kurt Jaeger , FreeBSD CURRENT Message-ID: Thread-Topic: r316958: booting a server takes >10 minutes! References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2321.1492272025@critter.freebsd.dk> <20170415160916.GY1326@albert.catwhisker.org> <4292.1492274488@critter.freebsd.dk> <20170415184331.GB1326@albert.catwhisker.org> <3E0D0513-0337-40E1-8173-11D845C0EFF4@lerctr.org> <20170415191329.GA74780@home.opsec.eu> In-Reply-To: <20170415191329.GA74780@home.opsec.eu> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 19:24:08 -0000 Current SVN seems to have fixed it (via sobomax@ syslogd commit). borg.lerctr.org /usr/src $ svn info;uname -aKU Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 316973 Node Kind: directory Schedule: normal Last Changed Author: sobomax Last Changed Rev: 316973 Last Changed Date: 2017-04-15 13:20:11 -0500 (Sat, 15 Apr 2017) FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #22 r316973: Sat Apr 15 14:06:54 CDT 2017 root@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER amd64 1200028 1200028 borg.lerctr.org /usr/src $ [borg][ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 On 4/15/17, 2:13 PM, "Kurt Jaeger" wrote: Hi! Larry wrote: > It was with PostgreSQL starting and I also noted Exim, SSHD, and > others spinning. Lots of NO BUFFERSPACE in a truss. Interesting. I had my build host being dead in the network (no ping, also with bufferspace problems), but I was able to login via console. And: It failed to shutdown/reboot properly, with some 200+ unclean blocks, trying to get them on disk in an seemingly endless loop. I had to hard-reset the box. But: It's older, r315141. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-current@freebsd.org Sat Apr 15 20:21:52 2017 Return-Path: Delivered-To: freebsd-current@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 9DD8ED3FDC9; Sat, 15 Apr 2017 20:21:52 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 134CBD6; Sat, 15 Apr 2017 20:21:51 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.171.81]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lt1eU-1c1W291fDe-012ZOI; Sat, 15 Apr 2017 22:21:43 +0200 Date: Sat, 15 Apr 2017 22:21:36 +0200 From: "O. Hartmann" To: Bruce Evans Cc: FreeBSD CURRENT , svn-src-head@freebsd.org Subject: Re: svn commit: r316977 - head/sys/dev/syscons Message-ID: <20170415222136.6c58a00d@thor.intern.walstatt.dynvpn.de> In-Reply-To: <201704152003.v3FK3o3w002356@repo.freebsd.org> References: <201704152003.v3FK3o3w002356@repo.freebsd.org> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/JAMg6MZfkRLtgW_8a6nHCI4"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:hwROznmUk/jAPRB/idEVZfJMZf52hVfSZVj8WbX5x3lT4q72i1W BNNFjcbVkVcS26GOZy9Q8KGsYuwkldt+wIwBZIlZW2aXK8s04KcHhJbSkX3JOSJe+KuzKO5 wVeAdI82uWzlH8FlhUftfnXYCf1Rzdb6/67UcE5jr7vZij5zvSBpK5pgYkCdDLMVu7sSi1O PY8P2QfW4PD5nAHMOBtaw== X-UI-Out-Filterresults: notjunk:1;V01:K0:DIfKdXluKU8=:sK4D6n/shaU7wpD474fuoT XPADMEaymNY5lava7h8ay8lIEc9v9MrUTCOpq5GQHvPWsWSHxMvCf/mNYI2OMYOfynRzam+g7 XQzA5GW2p6Ux+RpDCpD7rITysC4xEFcCxDNJblBqNBc4kU0VR600/PUV0AYVwLYTmSdldwdqk +jN38JeoNlSEG4wv4m+1Pa3iXU1Q0yOBjO/jQZPMGAif2ZnZyE6Fku1rY8Ad4d66CQ676KpsR TweDaEsbUZOuYBOMRkH48tXi79CiEa0Oa8zOftJwCDQ/Z/CcB+gjqTugAxI9T6B4NJJ9704ZF CC3Kk8UMkXXrLhQXY5Mb1LR2rxxkbVlwuDvvEKbhbCVVpWeQVnOH6YqnJJ05224GbzJl1WoOU hBA1eVUFR3MRQ2YrzSvdEMgUyT1VmBbutcPGafki4Am3QUAcx1lLISZaWiDYF32HFVCn0Kyik 4XAABteJAfGXgBj+GpjFrUAbUPrfx8IGBxsCBYwfpS3EV94uOeQbJecUu0f9smaQt5fSYnuhr nwc5SGDPJERjX1nVG1feTG4gZBMtLzt3MK5vM9Y5wj1Hux2DXHr6pkxoNOKzuGEmDpKvzVisx /XlQU5/AbKKAjhDI7XQVUnP02KBv0zlNCRTYAG0PJ/Nk/dc1/3X7APjDj1Ch6zru6d+G1QhqW u6Ob8cM65AJRSzC0/0+YqcGJ8YfK0cvED9fkVf31VyftzivVV7WknOREbZagh2KHbzHmtj6nJ yd+4znEJmJ+lSq+WHwjjwX63O9ly9ee5hAgkcn9QJ8YKlOYGlrWPc1UTNEU= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 20:21:52 -0000 --Sig_/JAMg6MZfkRLtgW_8a6nHCI4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sat, 15 Apr 2017 20:03:50 +0000 (UTC) Bruce Evans schrieb: > Author: bde > Date: Sat Apr 15 20:03:50 2017 > New Revision: 316977 > URL: https://svnweb.freebsd.org/changeset/base/316977 >=20 > Log: > Add a 10x16 mouse cursor and use it in all graphics (strictly, pixel) > modes if the font size is >=3D 14. > =20 > This is the X cursor XC_left_ptr (#68) (glyph #45 in an X cursor font). > Also found in vt. The old 9x13 cursor is the 10x16 one trimmed not very > well. > =20 > 8x8 fonts need a smaller cursor instead of a larger one, except when > the pixel size is small. Text mode is still limited to width and height > 1 more than the font (so the 9x13 is already 4 pixels too high for it). >=20 > Modified: > head/sys/dev/syscons/scvgarndr.c >=20 > Modified: head/sys/dev/syscons/scvgarndr.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > --- head/sys/dev/syscons/scvgarndr.c Sat Apr 15 19:47:50 2017 (r316976) > +++ head/sys/dev/syscons/scvgarndr.c Sat Apr 15 20:03:50 2017 (r316977) > @@ -173,6 +173,14 @@ static const struct mousedata mouse9x13=20 > 0x0c00, 0x0c00, 0x0600, 0x0600, 0x0000, 0x0000, 0x0000, 0x0000, }, > 9, 13, > }; > + > +static const struct mousedata mouse10x16 =3D { { > + 0xc000, 0xa000, 0x9000, 0x8800, 0x8400, 0x8200, 0x8100, 0x8080, > + 0x8040, 0x83c0, 0x9200, 0xa900, 0xc900, 0x0480, 0x0480, 0x0300, }, { > + 0x0000, 0x4000, 0x6000, 0x7000, 0x7800, 0x7c00, 0x7e00, 0x7f00, > + 0x7f80, 0x7c00, 0x6c00, 0x4600, 0x0600, 0x0300, 0x0300, 0x0000, }, > + 10, 16, > +}; > #endif > #endif > =20 > @@ -1042,7 +1050,7 @@ draw_pxlmouse_planar(scr_stat *scp, int=20 > int i, j, k; > uint8_t m1; > =20 > - mdp =3D &mouse9x13; > + mdp =3D (scp->font_size < 14) ? &mouse9x13 : &mouse10x16; > line_width =3D scp->sc->adp->va_line_width; > xoff =3D (x - scp->xoff*8)%8; > yoff =3D y - rounddown(y, line_width); > @@ -1087,7 +1095,7 @@ remove_pxlmouse_planar(scr_stat *scp, in > vm_offset_t p; > int bx, by, i, line_width, xend, xoff, yend, yoff; > =20 > - mdp =3D &mouse9x13; > + mdp =3D (scp->font_size < 14) ? &mouse9x13 : &mouse10x16; > =20 > /* > * It is only necessary to remove the mouse image where it overlaps > @@ -1132,7 +1140,7 @@ vga_pxlmouse_direct(scr_stat *scp, int x > uint8_t *u8; > int bpp; > =20 > - mdp =3D &mouse9x13; > + mdp =3D (scp->font_size < 14) ? &mouse9x13 : &mouse10x16; > =20 > /* > * Determine overlap with the border and then if removing, do nothing There is a lot of development going on theses days for syscons. What's abou= t vt()? vt() is considered broken for x11/nvidia-driver and vt() is considered a requiremen= t when UEFI is boot scheme, isn't it? I'm just curious. regards, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/JAMg6MZfkRLtgW_8a6nHCI4 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPKA0AAKCRDS528fyFhY lJqfAgCPq5IumlxQf2Uz7bYZPQrXGlScayd+aZ1in3C9ijuf4umTj5hB/a4SyIEX Yf/c6CmBJ+Xd59kodhnr3egZ/8YTAf9JKnsHTdhGBgAvGhRJVnUU8GRMIFH2NqGs TGNf6lxT/ojJNv2yzjFD9ys/hsUYYHMwKgwXHHTi/Aqd72hmMdGo =K6Pe -----END PGP SIGNATURE----- --Sig_/JAMg6MZfkRLtgW_8a6nHCI4-- From owner-freebsd-current@freebsd.org Sat Apr 15 21:58:36 2017 Return-Path: Delivered-To: freebsd-current@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 9FDD7D3F3DE for ; Sat, 15 Apr 2017 21:58:36 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 4AC18C31 for ; Sat, 15 Apr 2017 21:58:35 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v3FLwXms092996; Sat, 15 Apr 2017 21:58:33 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v3FLwXWr092995; Sat, 15 Apr 2017 14:58:33 -0700 (PDT) (envelope-from david) Date: Sat, 15 Apr 2017 14:58:33 -0700 From: David Wolfskill To: Larry Rosenman Cc: Kurt Jaeger , FreeBSD CURRENT Subject: Re: r316958: booting a server takes >10 minutes! Message-ID: <20170415215833.GD1326@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Larry Rosenman , Kurt Jaeger , FreeBSD CURRENT References: <20170415135314.6e628657@thor.intern.walstatt.dynvpn.de> <2321.1492272025@critter.freebsd.dk> <20170415160916.GY1326@albert.catwhisker.org> <4292.1492274488@critter.freebsd.dk> <20170415184331.GB1326@albert.catwhisker.org> <3E0D0513-0337-40E1-8173-11D845C0EFF4@lerctr.org> <20170415191329.GA74780@home.opsec.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PN720ooTGWi/DZaq" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 21:58:36 -0000 --PN720ooTGWi/DZaq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 15, 2017 at 02:24:05PM -0500, Larry Rosenman wrote: > Current SVN seems to have fixed it (via sobomax@ syslogd commit).=20 > .... Confirmed: I had experienced the issue running: FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #315 r3169= 56M/316956:1200028: Sat Apr 15 08:13:46 PDT 2017 root@g1-252.catwhisker= =2Eorg:/common/S4/obj/usr/src/sys/CANARY amd64 on my laptop, then cherry-picked r316973 and re-buit; no issue with processes spinning in CPU. Peace, david --=20 David H. Wolfskill david@catwhisker.org Who would have thought that a "hotelier" would be so ... unwelcoming? Sad. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --PN720ooTGWi/DZaq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJY8peJXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X3T8IANIul5G+Ng4RX+Jevm0CDTRS nwZuTuCukoCIelknN3AFDpuIWL0AQrvbk0lVdm3gMm5BSENocLNaeUgg/IsHgfvc H1u/fk1eWfPCYihUyS//6Yx6PV5AYinm4YJqzyTeqODKgpSaqxSwalajqc+rEVv/ 43yyhPPIQcIYmS+3sBpYqSppl218/KJ/vypJMdwuuCCiL3d2VsxFQZNhzQHFW2Nu pwKYD9t6D5SjUJNSOgTIFmGORiP3uiEXfzE8PivGFeq68w3R4M9+YHXuvF8QjURZ ztiWZ7mKkJATJbmafcZ2KG8kZVwgXE2KX/v1oO/WW5/ymz6v+LsQtWF2o/nsY8A= =7jnb -----END PGP SIGNATURE----- --PN720ooTGWi/DZaq--