From owner-freebsd-current@freebsd.org Sun Jul 29 07:05:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1631104DDCE for ; Sun, 29 Jul 2018 07:05:18 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 65C1874867 for ; Sun, 29 Jul 2018 07:05:18 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-wr1-x42e.google.com with SMTP id h9-v6so9242498wro.3 for ; Sun, 29 Jul 2018 00:05:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=6vz702sPt7ow/i6HDXHnsm9RsatoJwoi7ru2hz8rIZ8=; b=WB3evJAqlC2S2auLPAKYHdeedsNDRa7969XEfF+hxS/cucTmILm3NzO6B6TT0P2U8r lb5aTqlaV3eknAd4pB6cYcI5PcbnjjbxdUhVMSTqsvuVtNNjpvz/wzBh4icgvNNPFlke RyvX+pwAR2fVAw6UdEjktsH0GzP2ALMdWxghFLTp0LuMCx4k8BWhgoQomfUJqi1RDEYT B3cyY/kzbnXaMIFguyIOy8y+h+Y0Cwg2R0gdevIjf/TEaCmwZwDhzmYm8hCUJRg3HsJS jYswPeU8xeQd7zXAKBXAQT5yY/IacaHKxOUlU8uC0ckJECPRLpzr0Dt1UYKLysicMHis xzPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=6vz702sPt7ow/i6HDXHnsm9RsatoJwoi7ru2hz8rIZ8=; b=sXc/pA9tvSJQQ/sS+/mw80cJjyX1HRs9moS9zPaffX2ltXPnRrItzJs9qU8Lhy4ZYh Y+6zk4rYFEgCsFiuWeX0x06HdCkVK4d8fNDOE6+QqjdDi2Qe9jR8ZCnQJPFVwFKSSeHi 6FFk65Q9cv3xmdr7Z7+rNpiyv+QUwQNN4xn5B+c634eKTI6WNJ7ZcN0Uwm+xUqKVt1mr eVhFU4seWHVOSxl1G/Jb89rDJVJeJxPfmXlBBm7Q5d/5G7lH0E+xqyI3/AFg+mKHYGuT lifY9k4m+/L/FIHUcXxizvHrEhoL1Ad8G/PvJWxbFK2XWMGq0Wo9bSnODJCj6zxx0BoD 7UmQ== X-Gm-Message-State: AOUpUlEZ0ckdzFnkkb2GwJJF98D2YKbBfl7AuBrtdxzya+nm/GgzbsRD ezlRn1FfOlpOjjuxsnbZT1KAF2AfgY0= X-Google-Smtp-Source: AAOMgpe5Z6a9TrcE7f851bAZigqEEQNfBLsHAypOYiGXXUBNe0EbXnzkGWoo24hnQOxnctP5xTb6zg== X-Received: by 2002:adf:ea0a:: with SMTP id q10-v6mr12024772wrm.224.1532847916716; Sun, 29 Jul 2018 00:05:16 -0700 (PDT) Received: from kloomba ([95.104.142.14]) by smtp.gmail.com with ESMTPSA id u4-v6sm13912645wrt.31.2018.07.29.00.05.15 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Jul 2018 00:05:15 -0700 (PDT) Sender: Roman Bogorodskiy Date: Sun, 29 Jul 2018 11:05:09 +0400 From: Roman Bogorodskiy To: freebsd-current@freebsd.org Subject: Re: EFI issues Message-ID: <20180729070507.GA2216@kloomba> References: <20180728072938.GA28778@kloomba> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <20180728072938.GA28778@kloomba> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 07:05:19 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Roman Bogorodskiy wrote: > Hi, >=20 > I have a test box that's updated to -CURRENT usually once in a week or > two. This box boots using UEFI. After a regular update about two weeks > ago it started to panic on boot frequently (not UEFI related), but I > could not get a crash dump because my swap partition was too small. So I > moved data to the backup drive, repartitioned the main drive and boot > again. This went fine, so I decided to upgrade to fresh -CURRENT from > ~Jul 27th. Booting with the new kernel went fine, but after installworld > machine stopped booting, and on the screen I see: >=20 > FreeBSD/amd64 EFI loader, ... >=20 > .. >=20 > BootOrder: .... >=20 > And then it gets stuck and nothing happens. >=20 > As I already have a fresh backup, I decided that it'd be easier to > just re-install and copy data back over (maybe I messed up with > repartitioning). So I've downloaded a fresh snapshot: >=20 > FreeBSD-12.0-CURRENT-amd64-20180726-r336739-memstick.img >=20 > And re-installed. In the installer I choose all the same settings that > were before: UEFI + GPT, default partition scheme it suggested (efi > followed by freebsd-ufs followed by freebsd-swap), just increased the > swap size. >=20 > And the newly installed system won't boot just like a previous one: >=20 > https://people.freebsd.org/~novel/misc/freebsd_efi_lookup.jpg >=20 > Is there a way to recover this? Tried updating to get r336837 mentioned in another thread, and it still doesn't help. Current version is r336859. Partitioning schema looks this way: =3D> 40 1953525088 ada0 GPT (932G) 40 409600 1 efi (200M) 409640 1803550720 2 freebsd-ufs (860G) 1803960360 148897792 3 freebsd-swap (71G) 1952858152 666976 - free - (326M) I can boot it when booting from memstick r336739 and setting vfs.root.mountfrom=3D"ufs:ada0p2". Roman Bogorodskiy --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbXWcjAAoJEMltX/4IwiJquJ4IAIrv25WyEzE2pZ1qfNSCZRat uxcXYx7PGY4zsqzjb4rvBwqmm6/T8PH9/8nDnj6l/31RM6L2kV71D7a9uga7fHyy keF7kvoAhZvUOloukwLjMSaHnpz+GZvWS/toCNDAf2nLDzs0q9EMLLFLzZY1rQEh YGLrHnQWjDpyIV71k/42MzwtHMGSlU83mo5AqGghmkGTQQHR+G5UzSvrnIfgjint fYFdMtofSREeypu9n2cKaHG8CF2kpcoI59p66mIq29Ncqcr/k4dpUQm66L8Nq19r /+GpmyGSF0TA2TzYG22KU+6pHczZzsK8stxa9Ox6eSqPGTmvEf5L5RtbOXswRuA= =kbZK -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- From owner-freebsd-current@freebsd.org Sun Jul 29 07:50:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C9DF104EC93 for ; Sun, 29 Jul 2018 07:50:20 +0000 (UTC) (envelope-from ohartmann@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 CF7A7758C8; Sun, 29 Jul 2018 07:50:19 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([2.245.38.16]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LyS5K-1g59f90ZUc-015uJJ; Sun, 29 Jul 2018 09:45:09 +0200 Date: Sun, 29 Jul 2018 09:44:35 +0200 From: "O. Hartmann" To: Roman Bogorodskiy Cc: freebsd-current@freebsd.org Subject: Re: EFI issues Message-ID: <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180728072938.GA28778@kloomba> References: <20180728072938.GA28778@kloomba> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:wnkVEHKyoCrn7eYll98zWJCZj/RP9KThyQbL6wmmNFk0/P867g6 9aWj4GA8IVuJ1aW9omdqEmh4Da2SIQPpvaMq6v4cyK9nt3ex+Vj0h4EeTYxsK8F+q2ZNBg8 Bjnb+9DuqcUYhRVRzyuVqnYAozK9wc7ziu2OT/uQbE4eH37HpwWA5J5Lny2v6bJhTeXuP2Q Tr+LMUochw/2e1+a36qVg== X-UI-Out-Filterresults: notjunk:1;V01:K0:Bc0mxaiRa88=:yCV5miMUovPfxo7hhvyVXL dpFbMMZvgHpUZdtdCuTvPnlytg1Idc81xBb+Q0rJMwVzh1vVJz4RRZMdeBzX1TTIIl0x3WaQX Wt7tEBGmjR1gjGvWxu0AOGqK/LR5UMZgKO0uVhd+6IPeDgCep5578v+T8z/1EsS11GNprHl/I iEiQH5Pc8yskQg0H0GEUidyIpGLX6dWNsk4TkT4khGiyNG8OgsKfdCJkLfpTmR+SVMEmTgfNs grm4v8WSi2IB+AfZ2b2nfsUTLTTPDcnwxxH9cvHeP8XUHTiW62kl3ki/7DiAYeHjbnk68q2S+ ZEa4iuzLW191awBf/0kFfrK4uCC6wWlqIHwy4CHXqwqbzjUQ1DUemKOZK+7285qRNsGYeOHXb pmM5ThBErdiNdg09Zc5C0OBWzxGT/V0/YSmGO4d1H/3MRAnh01+4VjrPDvptJRnjPPbkvE+/d T9wadsPSh246q16nXS6v5qL/Qm8VA2HUCEDu6e70XsmDESapSp+qjwivbVd9ebU1Jmsb/UN1M hg7sGFBsxaGjQ18DpoQaXbSqrDTwnHZEzueMPD7uWUBeJZlBrD54/NPClAtSe7Aw1csVEoWPr mMMPtKOwKG1CDBiWa+kVFjsDmjvEJoz8OLcp7Yz4hHQBoaiXy2R48n6LaESgeJHW/+BmZ/eSH q34zvGbP9BDErflH1muX2Go7lRtaMsQfO30Y2+vsZjInSSEuYk1I1g8BL+jinT7O23mJbWgGS exXYfgj5Lh4Amefd46vvQB0X+DW9kGSEkY0eEm45v6ZLQl3zABdA8fFU1odazqOOoa8zfjNv6 Vgr5W3w X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 07:50:20 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkFtIFNh dCwgMjggSnVsIDIwMTggMTE6Mjk6NDAgKzA0MDANClJvbWFuIEJvZ29yb2Rza2l5IDxub3ZlbEBm cmVlYnNkLm9yZz4gc2NocmllYjoNCg0KPiBIaSwNCj4gDQo+IEkgaGF2ZSBhIHRlc3QgYm94IHRo YXQncyB1cGRhdGVkIHRvIC1DVVJSRU5UIHVzdWFsbHkgb25jZSBpbiBhIHdlZWsgb3INCj4gdHdv LiBUaGlzIGJveCBib290cyB1c2luZyBVRUZJLiBBZnRlciBhIHJlZ3VsYXIgdXBkYXRlIGFib3V0 IHR3byB3ZWVrcw0KPiBhZ28gaXQgc3RhcnRlZCB0byBwYW5pYyBvbiBib290IGZyZXF1ZW50bHkg KG5vdCBVRUZJIHJlbGF0ZWQpLCBidXQgSQ0KPiBjb3VsZCBub3QgZ2V0IGEgY3Jhc2ggZHVtcCBi ZWNhdXNlIG15IHN3YXAgcGFydGl0aW9uIHdhcyB0b28gc21hbGwuIFNvIEkNCj4gbW92ZWQgZGF0 YSB0byB0aGUgYmFja3VwIGRyaXZlLCByZXBhcnRpdGlvbmVkIHRoZSBtYWluIGRyaXZlIGFuZCBi b290DQo+IGFnYWluLiBUaGlzIHdlbnQgZmluZSwgc28gSSBkZWNpZGVkIHRvIHVwZ3JhZGUgdG8g ZnJlc2ggLUNVUlJFTlQgZnJvbQ0KPiB+SnVsIDI3dGguIEJvb3Rpbmcgd2l0aCB0aGUgbmV3IGtl cm5lbCB3ZW50IGZpbmUsIGJ1dCBhZnRlciBpbnN0YWxsd29ybGQNCj4gbWFjaGluZSBzdG9wcGVk IGJvb3RpbmcsIGFuZCBvbiB0aGUgc2NyZWVuIEkgc2VlOg0KPiANCj4gRnJlZUJTRC9hbWQ2NCBF RkkgbG9hZGVyLCAuLi4NCj4gDQo+IC4uDQo+IA0KPiBCb290T3JkZXI6IC4uLi4NCj4gDQo+IEFu ZCB0aGVuIGl0IGdldHMgc3R1Y2sgYW5kIG5vdGhpbmcgaGFwcGVucy4NCj4gDQo+IEFzIEkgYWxy ZWFkeSBoYXZlIGEgZnJlc2ggYmFja3VwLCBJIGRlY2lkZWQgdGhhdCBpdCdkIGJlIGVhc2llciB0 bw0KPiBqdXN0IHJlLWluc3RhbGwgYW5kIGNvcHkgZGF0YSBiYWNrIG92ZXIgKG1heWJlIEkgbWVz c2VkIHVwIHdpdGgNCj4gcmVwYXJ0aXRpb25pbmcpLiBTbyBJJ3ZlIGRvd25sb2FkZWQgYSBmcmVz aCBzbmFwc2hvdDoNCj4gDQo+IEZyZWVCU0QtMTIuMC1DVVJSRU5ULWFtZDY0LTIwMTgwNzI2LXIz MzY3MzktbWVtc3RpY2suaW1nDQo+IA0KPiBBbmQgcmUtaW5zdGFsbGVkLiBJbiB0aGUgaW5zdGFs bGVyIEkgY2hvb3NlIGFsbCB0aGUgc2FtZSBzZXR0aW5ncyB0aGF0DQo+IHdlcmUgYmVmb3JlOiBV RUZJICsgR1BULCBkZWZhdWx0IHBhcnRpdGlvbiBzY2hlbWUgaXQgc3VnZ2VzdGVkIChlZmkNCj4g Zm9sbG93ZWQgYnkgZnJlZWJzZC11ZnMgZm9sbG93ZWQgYnkgZnJlZWJzZC1zd2FwKSwganVzdCBp bmNyZWFzZWQgdGhlDQo+IHN3YXAgc2l6ZS4NCj4gDQo+IEFuZCB0aGUgbmV3bHkgaW5zdGFsbGVk IHN5c3RlbSB3b24ndCBib290IGp1c3QgbGlrZSBhIHByZXZpb3VzIG9uZToNCj4gDQo+IGh0dHBz Oi8vcGVvcGxlLmZyZWVic2Qub3JnL35ub3ZlbC9taXNjL2ZyZWVic2RfZWZpX2xvb2t1cC5qcGcN Cj4gDQo+IElzIHRoZXJlIGEgd2F5IHRvIHJlY292ZXIgdGhpcz8NCj4gDQo+IFJvbWFuIEJvZ29y b2Rza2l5DQoNCkp1c3QgY3VyaW91czoNCg0KV2hlbiBJIGluc3RhbGxlZCBGcmVlQlNEIGxhc3Qg dGltZSBmcm9tIHRoZSByZWNlbnQgKDIwMTgtMDctMjYpIFVTQiBmbGFzaCBkcml2ZSBvbiBhIFNT RCwNCnRoZSBmcmVlYnNkLXN3YXAgcGFydGl0aW9uIGZvbGxvd2VkIGltbWVkaWF0ZWx5IGFmdGVy IHRoZSBFU1AgYW5kL29yIGZyZWVic2QtYm9vdCBHUFQNCmxvYWRlciBwYXJ0aXRpb24uIEJ1dCBp biBtb3N0IGNhc2VzIEkgdXNlZCB0byB1c2UgWkZTIGZvciB0ZXN0aW5nLg0KDQpTaW5jZSBJIGhh ZCBteSBVRUZJIGFkdmVudHVyZSBvZiBteSBvd24gdGhlc2UgZGF5cyBhbmQgcmVjZWl2ZWQgdmFs dWFibGUgaGludHMgZnJvbSB0aGUNCmRldmVsb3BtZW50L21haW50ZW5hbmNlIHRlYW0gb24gc29t ZSBVRUZJIGFzcGVjdHMsIGl0IHdvdWxkIGJlIG9mIGludGVyZXN0IHRvIGtub3cgeW91cg0KcmVj ZW50IGhhcmR3YXJlIGFuZCwgbW9yZSBpbXBvcnRhbnRseSBzaW5jZSBJIHNlZSB0aGUgYm9vdCBv cmRlciBwcmVzZW50ZWQgaW4geW91DQpzY3JlZW5zaG90LCBhIGR1bXAgb2YgdGhlIGVmaSB2YXJp YWJsZSBzZXR0aW5ncy4gSnVzdCBmb3IgY3VyaW9zaXR5LiBGb3IgdGhhdCwgeW91IGhhdmUNCnRv IGJvb3QgdGhlIHJlY2VudCBVU0IgZmxhc2ggZHJpdmUgaW1hZ2Ugd2l0aCBVRUZJLW9ubHksIHRo ZW4gbG9nb24gYXMgcm9vdCBhbmQgcGVyZm9ybQ0KDQprbGRsb2FkIGVmaXJ0DQoNCmFuZCB0aGVu IGlzc3VlIA0KDQojIGVmaWJvb3RtZ3IgLXYNCg0KSW4gbXkgY2FzZSwgaXQgbG9va3MgbGlrZQ0K DQpbLi4uXQ0KW29oYXJ0bWFubl06IHN1ZG8gZWZpYm9vdG1nciAtdg0KQm9vdEN1cnJlbnQ6IDAw MDENClRpbWVvdXQgICAgOiAzIHNlY29uZHMNCkJvb3RPcmRlciAgOiAwMDAxLCAwMDAyLCAwMDAz LCAwMDA0LCAwMDA1LCAwMDAwDQorQm9vdDAwMDEqIEZyZWVCU0QtMTIgXA0KICAgSEQoMSxHUFQs ZTE0NjA5NDEtZTJlOS0xMWU1LWI5MTMtZDA1MDk5MDdlZjA5LDB4MjgsMHg2NDApL0ZpbGUoXGVm aVxib290XEJPT1R4NjQuZWZpKSBcDQogICBhZGEwcDE6L2VmaS9ib290L0JPT1R4NjQuZWZpIChu dWxsKSANCiBCb290MDAwMiogSGFyZCBEcml2ZSAgQkJTKEhELCwweDApDQogQm9vdDAwMDMqIENE L0RWRCBEcml2ZSAgQkJTKENEUk9NLCwweDApDQogQm9vdDAwMDQqIFVTQiAgQkJTKFVTQiwsMHgw KQ0KIEJvb3QwMDA1KiBOZXR3b3JrIENhcmQgIEJCUyhOZXR3b3JrLCwweDApDQogQm9vdDAwMDAg IEZyZWVCU0QtMTINCkhEKDEsR1BULGUxNDYwOTQxLWUyZTktMTFlNS1iOTEzLWQwNTA5OTA3ZWYw OSwweDI4LDB4NjQwKS9GaWxlKFxlZmlcYm9vdFxCT09UeDY0LmVmaSkNCmFkYTBwMTovZWZpL2Jv b3QvQk9PVHg2NC5lZmkgKG51bGwpDQoNCg0KVW5yZWZlcmVuY2VkIFZhcmlhYmxlczoNClsuLi5d DQoNCkJvb3QwMDAwIGlzIHRoZSBzYW1lIGFzIEJvb3QwMDAxIGFuZCBpcyBkZWZpbmVkIGR1ZSB0 byBzb21lICJidWciIFdhcm5lciBMb3NoIGhhcyBmaXhlZA0KcmVjZW50bHksIGl0IGlzIHRoZSBz YW1lIGFzIEJvb3QwMDAxDQoNCktpbmQgcmVnYXJkcywNCg0Kb2gNCg0KLSAtLSANCk8uIEhhcnRt YW5uDQoNCkljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2RlciDDnGJlcm1pdHRsdW5nIG1l aW5lciBEYXRlbiBmw7xyDQpXZXJiZXp3ZWNrZSBvZGVyIGbDvHIgZGllIE1hcmt0LSBvZGVyIE1l aW51bmdzZm9yc2NodW5nICjCpyAyOCBBYnMuIDQgQkRTRykuDQotLS0tLUJFR0lOIFBHUCBTSUdO QVRVUkUtLS0tLQ0KDQppTFVFQVJNS0FCMFdJUVFaVlpNekF0d0MyVC84NlRyUzUyOGZ5RmhZbEFV Q1cxMXdmZ0FLQ1JEUzUyOGZ5RmhZDQpsTW9qQWY5MjlVU3gxeDdJL3NTR0x0RVdLTzhybTlJWGYx SkVwUTdHU2RJNllIaWQzNjR4N2ZiclVCaERaWXVUDQpKVmFuWTU3TGkyb0xPWG9nSHRNdzZlRFV5 RCthQWY5R1RFMzBMVU5SaG1jSjdlbDYyVndwbTBvVUJHMmFzNTJpDQordjU4RVo5YzIweUtRS3VY dDQ0NmRoYklMeU9ERFBLbWM5eWtBdm5FMFR0TWlUSGs2dlJuDQo9TTd2aQ0KLS0tLS1FTkQgUEdQ IFNJR05BVFVSRS0tLS0tDQo= From owner-freebsd-current@freebsd.org Sun Jul 29 08:10:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4B50104F840 for ; Sun, 29 Jul 2018 08:10:10 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::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 17B53763B7 for ; Sun, 29 Jul 2018 08:10:10 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id o11-v6so9672453wmh.2 for ; Sun, 29 Jul 2018 01:10:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=46pveQZO7zSeUOkRlNLcxhA5YVL+gpjAtmLKQ62CHwA=; b=Mxmy80IEMNTISLKOOf3ALTFbK7G3CybsnHNXdIU2PmZxzlwiUvml/2JYU1VUXMhI7E tCBuq0Al7ZrfPnbLLnV6PHaro+uqVbhWTyAsrGVOPOrvXOq/fGwL5EE0dtycpi7IZh8x RPI6jR9v438q//0UW14qroRAYqKGBWsEyCjSDU7ETjy3ZNwfKcD9LWjbcdFAyCbh14aH /H19CeMac+iIopEk6WFaveZpmxY6d6pC0sDCwUnR5Jj9IDS6UpZ7BjCU2GrSBCqbgI9Y bw5pGvqceXWl5V35O+2fJWgGGhALNBvBq8a8N6qT4M8eUdhJIM22o+5GREnhb3Me9kln zKHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=46pveQZO7zSeUOkRlNLcxhA5YVL+gpjAtmLKQ62CHwA=; b=U++aIP8+ClE5AodGErms9hjJCGZIIMA9IVdH5XTrVLBcZprYJTJRGINvTGZ7WU5Y8B mhlDJisdCTI1HTXOhDITTZvtvJFzWZ/coKhhUDiF6k5YRJY4FYxC485Gr/CCvzaO8/cH aJKcRRKnpsECfM9TwcUio0AcCLinG1jn60f9AhDnpJ6TvKGjaxFaVzZ8YDvkOVgrgmrj Iw0lEPYD3jjhQJ5Ppgkcj2BmDWYbf21AZPnMgXtLksxt7iZn+RIgzD0dG/VX8/q89qnd ec7VPc2bFHflQqaESN89dKOKINCyd0tLp6AT/MaBy4zjV2BkuzPI98WoUear5ZoCdOwZ cLTg== X-Gm-Message-State: AOUpUlEqT9inL3H/+bGOJ5pktlyhy/Jwry8fM9j0bXkozDY7mkyTrgIy 85wskJdVzkc8o/g+qLh8a0Nm1fshk+o= X-Google-Smtp-Source: AAOMgpd9ab2Lfg2urwqKUAXGrdAnIYTQBXYkplNDYuRyJfjrmyv5g/zB24gHboGTNkRhbLbIepYpWQ== X-Received: by 2002:a1c:ac44:: with SMTP id v65-v6mr10273397wme.25.1532851808962; Sun, 29 Jul 2018 01:10:08 -0700 (PDT) Received: from kloomba ([95.104.142.14]) by smtp.gmail.com with ESMTPSA id u7-v6sm5051633wmd.46.2018.07.29.01.10.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Jul 2018 01:10:08 -0700 (PDT) Sender: Roman Bogorodskiy Date: Sun, 29 Jul 2018 12:09:58 +0400 From: Roman Bogorodskiy To: "O. Hartmann" Cc: freebsd-current@freebsd.org Subject: Re: EFI issues Message-ID: <20180729080957.GB2216@kloomba> References: <20180728072938.GA28778@kloomba> <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS" Content-Disposition: inline In-Reply-To: <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 08:10:11 -0000 --RASg3xLB4tUQ4RcS Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable O. Hartmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > Am Sat, 28 Jul 2018 11:29:40 +0400 > Roman Bogorodskiy schrieb: >=20 > > Hi, > >=20 > > I have a test box that's updated to -CURRENT usually once in a week or > > two. This box boots using UEFI. After a regular update about two weeks > > ago it started to panic on boot frequently (not UEFI related), but I > > could not get a crash dump because my swap partition was too small. So I > > moved data to the backup drive, repartitioned the main drive and boot > > again. This went fine, so I decided to upgrade to fresh -CURRENT from > > ~Jul 27th. Booting with the new kernel went fine, but after installworld > > machine stopped booting, and on the screen I see: > >=20 > > FreeBSD/amd64 EFI loader, ... > >=20 > > .. > >=20 > > BootOrder: .... > >=20 > > And then it gets stuck and nothing happens. > >=20 > > As I already have a fresh backup, I decided that it'd be easier to > > just re-install and copy data back over (maybe I messed up with > > repartitioning). So I've downloaded a fresh snapshot: > >=20 > > FreeBSD-12.0-CURRENT-amd64-20180726-r336739-memstick.img > >=20 > > And re-installed. In the installer I choose all the same settings that > > were before: UEFI + GPT, default partition scheme it suggested (efi > > followed by freebsd-ufs followed by freebsd-swap), just increased the > > swap size. > >=20 > > And the newly installed system won't boot just like a previous one: > >=20 > > https://people.freebsd.org/~novel/misc/freebsd_efi_lookup.jpg > >=20 > > Is there a way to recover this? > >=20 > > Roman Bogorodskiy >=20 > Just curious: >=20 > When I installed FreeBSD last time from the recent (2018-07-26) USB flash= drive on a SSD, > the freebsd-swap partition followed immediately after the ESP and/or free= bsd-boot GPT > loader partition. But in most cases I used to use ZFS for testing. When I reinstalled it yesterday from -CURRENT snapshot mentioned above, in guided mode it suggested a similar partitioning schema that I use: =3D> 40 1953525088 ada0 GPT (932G) 40 409600 1 efi (200M) 409640 1803550720 2 freebsd-ufs (860G) 1803960360 148897792 3 freebsd-swap (71G) 1952858152 666976 - free - (326M) The only difference it that the freebsd-swap size was 3.5G (and therefore, freebsd-ufs is large), the order was the same. > Since I had my UEFI adventure of my own these days and received valuable = hints from the > development/maintenance team on some UEFI aspects, it would be of interes= t to know your > recent hardware and, more importantly since I see the boot order presente= d in you > screenshot, a dump of the efi variable settings. Just for curiosity. For = that, you have > to boot the recent USB flash drive image with UEFI-only, then logon as ro= ot and perform >=20 > kldload efirt >=20 > and then issue=20 >=20 > # efibootmgr -v >=20 > In my case, it looks like >=20 > [...] > [ohartmann]: sudo efibootmgr -v > BootCurrent: 0001 > Timeout : 3 seconds > BootOrder : 0001, 0002, 0003, 0004, 0005, 0000 > +Boot0001* FreeBSD-12 \ > HD(1,GPT,e1460941-e2e9-11e5-b913-d0509907ef09,0x28,0x640)/File(\efi\bo= ot\BOOTx64.efi) \ > ada0p1:/efi/boot/BOOTx64.efi (null)=20 > Boot0002* Hard Drive BBS(HD,,0x0) > Boot0003* CD/DVD Drive BBS(CDROM,,0x0) > Boot0004* USB BBS(USB,,0x0) > Boot0005* Network Card BBS(Network,,0x0) > Boot0000 FreeBSD-12 > HD(1,GPT,e1460941-e2e9-11e5-b913-d0509907ef09,0x28,0x640)/File(\efi\boot\= BOOTx64.efi) > ada0p1:/efi/boot/BOOTx64.efi (null) >=20 >=20 > Unreferenced Variables: > [...] >=20 > Boot0000 is the same as Boot0001 and is defined due to some "bug" Warner = Losh has fixed > recently, it is the same as Boot0001 Motherboard is (from dmidecode): Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 0806 Release Date: 02/20/2014 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 4.6 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: B85M-E Version: Rev X.0x Serial Number: 140526238405585 Asset Tag: To be filled by O.E.M. = = =20 Features: = = =20 Board is a hosting board = = =20 Board is replaceable = = =20 Location In Chassis: To be filled by O.E.M. = = =20 Chassis Handle: 0x0003 = = =20 Type: Motherboard = = =20 Contained Object Handles: 0 'efibootmgr -v' output: BootCurrent: 0004 Timeout : 1 seconds BootOrder : 0001, 0002, 0003, 0004 Boot0001* Hard Drive BBS(HD,,0x0) Boot0002* Network Card BBS(Network,,0x0) Boot0003* UEFI OS HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28,0x640= 00)/File(\EFI\BOOT\BOOTX64.EFI) ada0p1:/EFI/BOOT/BOOTX64.EFI (null) Path(0,0,ae84b11df581724e85442bab0c2cac5c020000020000) +Boot0004* UEFI: SanDisk PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x4,0x= 0)/HD(1,MBR,0x90909090,0x1,0x640) VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6,53006100= 6e004400690073006b000000) Unreferenced Variables: > Kind regards, >=20 > oh >=20 > - --=20 > O. Hartmann >=20 > Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr > Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs. 4 B= DSG). > -----BEGIN PGP SIGNATURE----- >=20 > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW11wfgAKCRDS528fyFhY > lMojAf929USx1x7I/sSGLtEWKO8rm9IXf1JEpQ7GSdI6YHid364x7fbrUBhDZYuT > JVanY57Li2oLOXogHtMw6eDUyD+aAf9GTE30LUNRhmcJ7el62Vwpm0oUBG2as52i > +v58EZ9c20yKQKuXt446dhbILyODDPKmc9ykAvnE0TtMiTHk6vRn > =3DM7vi > -----END PGP SIGNATURE----- Roman Bogorodskiy --RASg3xLB4tUQ4RcS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbXXZVAAoJEMltX/4IwiJqJu8IAMS11Fhah0Sv2lbRdIszqLKM TGQnSLOF+gw6M5WxoF059m/fM4SEKwNUsTH+7R/tLg/m7I9NWA+vxz8DJC9PeEMF GDRITpkbiSlGCZx1LvmnpAUTCO4av9+sX+bqeKYSO15a4Xn+vY1H5tMfmZW8hD+X 1bd20rveUpqyj3tlbaegvoRK5bT48joQRnYF20V+S3tqRwRzfON5iAfshfQlwsSM sjeu/gz2pEowpa9C6qNGrNLNO/B6OkDE5l6CTgtl+l7gCl3YaBTTuc9JsHNGrg88 RYg9Nnz2Y1VGGy2K3Rzn6UFOLLCwGHJxeldyaS1kitU1YDOKp5kIZ6eMhoN1IyI= =tcvb -----END PGP SIGNATURE----- --RASg3xLB4tUQ4RcS-- From owner-freebsd-current@freebsd.org Sun Jul 29 09:01:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01F261050ED9 for ; Sun, 29 Jul 2018 09:01:17 +0000 (UTC) (envelope-from ohartmann@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 72C0278087; Sun, 29 Jul 2018 09:01:16 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([2.245.38.16]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LtmK9-1g8h4N1OMv-011AeT; Sun, 29 Jul 2018 10:55:58 +0200 Date: Sun, 29 Jul 2018 10:55:23 +0200 From: "O. Hartmann" To: Roman Bogorodskiy Cc: "O. Hartmann" , freebsd-current@freebsd.org Subject: Re: EFI issues Message-ID: <20180729105550.4ac8711a@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180729080957.GB2216@kloomba> References: <20180728072938.GA28778@kloomba> <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> <20180729080957.GB2216@kloomba> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:Eq6G0sX2cPSeEk9ZdBJDK6aNirdH3HqYDAD3QUKMXkf1Qif38OM ZRVAltfdOb2yA8Z07g+PJWY6Omo6jhSViBWl5Q3bqp1NHrx3CC6kaVALXIL4jafIfuisCQu HFSYnMT3hAw37qHadS+M3/3g/C/PTF78KdRCAFnxcuW3ky/PEeI/azIqGtIop4CPnNIZNEg 9KG07Qi5ZxxQbsCmQ6G8Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:/McUwsVvUg0=:FNc52TjRwCFbvDgW1qy9jA 3jnCtMdvGa9v7nsTMO0vY33NtHqepmRiBMEKerD0tmTRMvNcqo4IUKK7rFuOHCarzXkpGO3hN KZV4bT18rVo7hEG9mUZ5JCyIuamgCdFuztEvqrmsxVA6PpuKnfyGrawbJey4wISMFli563L4U nYJVVp7ciXy7mtd395f+yMZ1rX6PHoZ6CBXZgO3MOns0fXNY9PX2v2NwJQlr5WtBlMUF3czX1 sZDUvV/KbZS4bVB36AgVLSGc68Lyg4PCE+pYePtKaaeyfvH4lz4ho+/Z7firuzmbIoL1+LTM/ y7M31zsM4U5cXdAh5kr92BPU4AJkMS0yq7oaVBeLjcxLSNxulYRtnf9NZF8eARE9opEYhHdmp Xz4+TnCEBkBxiZMJeSIifEojuOH6G9AGEU8BdliXZD4aaSVd6/tHFmLbyLeAfckpy8UkCRHOO U8XC7qPcCMINYKJTc1E/7A5VhWFNQspl3ceFWEaVMeHXtPlbGdW/w6BTHQGNZlL8eV+hxZqIr d2bCAXFpWMQOcSGF0mRrSGbcP56IPsa/Hepmz60sckDdTi6DPh4yGBR8LTbAFif3oVTknXgUf bDG1wp8Cj1hNuPjsvkFycVV/Tzyp4bMKcykWS3UwHkKGDlyqBQCnlXhrWTPJ7MdkeT2/H8/i5 sriz+LFd1seJvDeLiVGIlKjDvsgCM+TiuVF1Sxg70jOvLo4G1ziaDNyxOThzkrSQU/KH8ZfEM +fVC+VnFU179eS4qikktjFfhJ9uG2ps+AAGrXfdG61VLBwgKae6h7XRKWUtFVptdRUx8OsCq9 Ji0F9rW X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 09:01:17 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkFtIFN1 biwgMjkgSnVsIDIwMTggMTI6MDk6NTggKzA0MDANClJvbWFuIEJvZ29yb2Rza2l5IDxub3ZlbEBm cmVlYnNkLm9yZz4gc2NocmllYjoNCg0KPiAgIE8uIEhhcnRtYW5uIHdyb3RlOg0KPiANCj4gPiAt LS0tLUJFR0lOIFBHUCBTSUdORUQgTUVTU0FHRS0tLS0tDQo+ID4gSGFzaDogU0hBNTEyDQo+ID4g DQo+ID4gQW0gU2F0LCAyOCBKdWwgMjAxOCAxMToyOTo0MCArMDQwMA0KPiA+IFJvbWFuIEJvZ29y b2Rza2l5IDxub3ZlbEBmcmVlYnNkLm9yZz4gc2NocmllYjoNCj4gPiAgIA0KPiA+ID4gSGksDQo+ ID4gPiANCj4gPiA+IEkgaGF2ZSBhIHRlc3QgYm94IHRoYXQncyB1cGRhdGVkIHRvIC1DVVJSRU5U IHVzdWFsbHkgb25jZSBpbiBhIHdlZWsgb3INCj4gPiA+IHR3by4gVGhpcyBib3ggYm9vdHMgdXNp bmcgVUVGSS4gQWZ0ZXIgYSByZWd1bGFyIHVwZGF0ZSBhYm91dCB0d28gd2Vla3MNCj4gPiA+IGFn byBpdCBzdGFydGVkIHRvIHBhbmljIG9uIGJvb3QgZnJlcXVlbnRseSAobm90IFVFRkkgcmVsYXRl ZCksIGJ1dCBJDQo+ID4gPiBjb3VsZCBub3QgZ2V0IGEgY3Jhc2ggZHVtcCBiZWNhdXNlIG15IHN3 YXAgcGFydGl0aW9uIHdhcyB0b28gc21hbGwuIFNvIEkNCj4gPiA+IG1vdmVkIGRhdGEgdG8gdGhl IGJhY2t1cCBkcml2ZSwgcmVwYXJ0aXRpb25lZCB0aGUgbWFpbiBkcml2ZSBhbmQgYm9vdA0KPiA+ ID4gYWdhaW4uIFRoaXMgd2VudCBmaW5lLCBzbyBJIGRlY2lkZWQgdG8gdXBncmFkZSB0byBmcmVz aCAtQ1VSUkVOVCBmcm9tDQo+ID4gPiB+SnVsIDI3dGguIEJvb3Rpbmcgd2l0aCB0aGUgbmV3IGtl cm5lbCB3ZW50IGZpbmUsIGJ1dCBhZnRlciBpbnN0YWxsd29ybGQNCj4gPiA+IG1hY2hpbmUgc3Rv cHBlZCBib290aW5nLCBhbmQgb24gdGhlIHNjcmVlbiBJIHNlZToNCj4gPiA+IA0KPiA+ID4gRnJl ZUJTRC9hbWQ2NCBFRkkgbG9hZGVyLCAuLi4NCj4gPiA+IA0KPiA+ID4gLi4NCj4gPiA+IA0KPiA+ ID4gQm9vdE9yZGVyOiAuLi4uDQo+ID4gPiANCj4gPiA+IEFuZCB0aGVuIGl0IGdldHMgc3R1Y2sg YW5kIG5vdGhpbmcgaGFwcGVucy4NCj4gPiA+IA0KPiA+ID4gQXMgSSBhbHJlYWR5IGhhdmUgYSBm cmVzaCBiYWNrdXAsIEkgZGVjaWRlZCB0aGF0IGl0J2QgYmUgZWFzaWVyIHRvDQo+ID4gPiBqdXN0 IHJlLWluc3RhbGwgYW5kIGNvcHkgZGF0YSBiYWNrIG92ZXIgKG1heWJlIEkgbWVzc2VkIHVwIHdp dGgNCj4gPiA+IHJlcGFydGl0aW9uaW5nKS4gU28gSSd2ZSBkb3dubG9hZGVkIGEgZnJlc2ggc25h cHNob3Q6DQo+ID4gPiANCj4gPiA+IEZyZWVCU0QtMTIuMC1DVVJSRU5ULWFtZDY0LTIwMTgwNzI2 LXIzMzY3MzktbWVtc3RpY2suaW1nDQo+ID4gPiANCj4gPiA+IEFuZCByZS1pbnN0YWxsZWQuIElu IHRoZSBpbnN0YWxsZXIgSSBjaG9vc2UgYWxsIHRoZSBzYW1lIHNldHRpbmdzIHRoYXQNCj4gPiA+ IHdlcmUgYmVmb3JlOiBVRUZJICsgR1BULCBkZWZhdWx0IHBhcnRpdGlvbiBzY2hlbWUgaXQgc3Vn Z2VzdGVkIChlZmkNCj4gPiA+IGZvbGxvd2VkIGJ5IGZyZWVic2QtdWZzIGZvbGxvd2VkIGJ5IGZy ZWVic2Qtc3dhcCksIGp1c3QgaW5jcmVhc2VkIHRoZQ0KPiA+ID4gc3dhcCBzaXplLg0KPiA+ID4g DQo+ID4gPiBBbmQgdGhlIG5ld2x5IGluc3RhbGxlZCBzeXN0ZW0gd29uJ3QgYm9vdCBqdXN0IGxp a2UgYSBwcmV2aW91cyBvbmU6DQo+ID4gPiANCj4gPiA+IGh0dHBzOi8vcGVvcGxlLmZyZWVic2Qu b3JnL35ub3ZlbC9taXNjL2ZyZWVic2RfZWZpX2xvb2t1cC5qcGcNCj4gPiA+IA0KPiA+ID4gSXMg dGhlcmUgYSB3YXkgdG8gcmVjb3ZlciB0aGlzPw0KPiA+ID4gDQo+ID4gPiBSb21hbiBCb2dvcm9k c2tpeSAgDQo+ID4gDQo+ID4gSnVzdCBjdXJpb3VzOg0KPiA+IA0KPiA+IFdoZW4gSSBpbnN0YWxs ZWQgRnJlZUJTRCBsYXN0IHRpbWUgZnJvbSB0aGUgcmVjZW50ICgyMDE4LTA3LTI2KSBVU0IgZmxh c2ggZHJpdmUgb24gYQ0KPiA+IFNTRCwgdGhlIGZyZWVic2Qtc3dhcCBwYXJ0aXRpb24gZm9sbG93 ZWQgaW1tZWRpYXRlbHkgYWZ0ZXIgdGhlIEVTUCBhbmQvb3INCj4gPiBmcmVlYnNkLWJvb3QgR1BU IGxvYWRlciBwYXJ0aXRpb24uIEJ1dCBpbiBtb3N0IGNhc2VzIEkgdXNlZCB0byB1c2UgWkZTIGZv ciB0ZXN0aW5nLiAgDQo+IA0KPiBXaGVuIEkgcmVpbnN0YWxsZWQgaXQgeWVzdGVyZGF5IGZyb20g LUNVUlJFTlQgc25hcHNob3QgbWVudGlvbmVkIGFib3ZlLA0KPiBpbiBndWlkZWQgbW9kZSBpdCBz dWdnZXN0ZWQgYSBzaW1pbGFyIHBhcnRpdGlvbmluZyBzY2hlbWEgdGhhdCBJIHVzZToNCj4gDQo+ ID0+ICAgICAgICA0MCAgMTk1MzUyNTA4OCAgYWRhMCAgR1BUICAoOTMyRykgIA0KPiAgICAgICAg ICAgNDAgICAgICA0MDk2MDAgICAgIDEgIGVmaSAgKDIwME0pDQo+ICAgICAgIDQwOTY0MCAgMTgw MzU1MDcyMCAgICAgMiAgZnJlZWJzZC11ZnMgICg4NjBHKQ0KPiAgIDE4MDM5NjAzNjAgICAxNDg4 OTc3OTIgICAgIDMgIGZyZWVic2Qtc3dhcCAgKDcxRykNCj4gICAxOTUyODU4MTUyICAgICAgNjY2 OTc2ICAgICAgICAtIGZyZWUgLSAgKDMyNk0pDQo+IA0KPiBUaGUgb25seSBkaWZmZXJlbmNlIGl0 IHRoYXQgdGhlIGZyZWVic2Qtc3dhcCBzaXplIHdhcyAzLjVHIChhbmQNCj4gdGhlcmVmb3JlLCBm cmVlYnNkLXVmcyBpcyBsYXJnZSksIHRoZSBvcmRlciB3YXMgdGhlIHNhbWUuDQo+IA0KPiA+IFNp bmNlIEkgaGFkIG15IFVFRkkgYWR2ZW50dXJlIG9mIG15IG93biB0aGVzZSBkYXlzIGFuZCByZWNl aXZlZCB2YWx1YWJsZSBoaW50cyBmcm9tDQo+ID4gdGhlIGRldmVsb3BtZW50L21haW50ZW5hbmNl IHRlYW0gb24gc29tZSBVRUZJIGFzcGVjdHMsIGl0IHdvdWxkIGJlIG9mIGludGVyZXN0IHRvDQo+ ID4ga25vdyB5b3VyIHJlY2VudCBoYXJkd2FyZSBhbmQsIG1vcmUgaW1wb3J0YW50bHkgc2luY2Ug SSBzZWUgdGhlIGJvb3Qgb3JkZXIgcHJlc2VudGVkDQo+ID4gaW4geW91IHNjcmVlbnNob3QsIGEg ZHVtcCBvZiB0aGUgZWZpIHZhcmlhYmxlIHNldHRpbmdzLiBKdXN0IGZvciBjdXJpb3NpdHkuIEZv ciB0aGF0LA0KPiA+IHlvdSBoYXZlIHRvIGJvb3QgdGhlIHJlY2VudCBVU0IgZmxhc2ggZHJpdmUg aW1hZ2Ugd2l0aCBVRUZJLW9ubHksIHRoZW4gbG9nb24gYXMgcm9vdA0KPiA+IGFuZCBwZXJmb3Jt DQo+ID4gDQo+ID4ga2xkbG9hZCBlZmlydA0KPiA+IA0KPiA+IGFuZCB0aGVuIGlzc3VlIA0KPiA+ IA0KPiA+ICMgZWZpYm9vdG1nciAtdg0KPiA+IA0KPiA+IEluIG15IGNhc2UsIGl0IGxvb2tzIGxp a2UNCj4gPiANCj4gPiBbLi4uXQ0KPiA+IFtvaGFydG1hbm5dOiBzdWRvIGVmaWJvb3RtZ3IgLXYN Cj4gPiBCb290Q3VycmVudDogMDAwMQ0KPiA+IFRpbWVvdXQgICAgOiAzIHNlY29uZHMNCj4gPiBC b290T3JkZXIgIDogMDAwMSwgMDAwMiwgMDAwMywgMDAwNCwgMDAwNSwgMDAwMA0KPiA+ICtCb290 MDAwMSogRnJlZUJTRC0xMiBcDQo+ID4gICAgSEQoMSxHUFQsZTE0NjA5NDEtZTJlOS0xMWU1LWI5 MTMtZDA1MDk5MDdlZjA5LDB4MjgsMHg2NDApL0ZpbGUoXGVmaVxib290XEJPT1R4NjQuZWZpKQ0K PiA+IFwgYWRhMHAxOi9lZmkvYm9vdC9CT09UeDY0LmVmaSAobnVsbCkgDQo+ID4gIEJvb3QwMDAy KiBIYXJkIERyaXZlICBCQlMoSEQsLDB4MCkNCj4gPiAgQm9vdDAwMDMqIENEL0RWRCBEcml2ZSAg QkJTKENEUk9NLCwweDApDQo+ID4gIEJvb3QwMDA0KiBVU0IgIEJCUyhVU0IsLDB4MCkNCj4gPiAg Qm9vdDAwMDUqIE5ldHdvcmsgQ2FyZCAgQkJTKE5ldHdvcmssLDB4MCkNCj4gPiAgQm9vdDAwMDAg IEZyZWVCU0QtMTINCj4gPiBIRCgxLEdQVCxlMTQ2MDk0MS1lMmU5LTExZTUtYjkxMy1kMDUwOTkw N2VmMDksMHgyOCwweDY0MCkvRmlsZShcZWZpXGJvb3RcQk9PVHg2NC5lZmkpDQo+ID4gYWRhMHAx Oi9lZmkvYm9vdC9CT09UeDY0LmVmaSAobnVsbCkNCj4gPiANCj4gPiANCj4gPiBVbnJlZmVyZW5j ZWQgVmFyaWFibGVzOg0KPiA+IFsuLi5dDQo+ID4gDQo+ID4gQm9vdDAwMDAgaXMgdGhlIHNhbWUg YXMgQm9vdDAwMDEgYW5kIGlzIGRlZmluZWQgZHVlIHRvIHNvbWUgImJ1ZyIgV2FybmVyIExvc2gg aGFzDQo+ID4gZml4ZWQgcmVjZW50bHksIGl0IGlzIHRoZSBzYW1lIGFzIEJvb3QwMDAxICANCj4g DQo+IE1vdGhlcmJvYXJkIGlzIChmcm9tIGRtaWRlY29kZSk6DQo+IA0KPiBIYW5kbGUgMHgwMDAw LCBETUkgdHlwZSAwLCAyNCBieXRlcw0KPiBCSU9TIEluZm9ybWF0aW9uDQo+ICAgICAgICAgVmVu ZG9yOiBBbWVyaWNhbiBNZWdhdHJlbmRzIEluYy4NCj4gICAgICAgICBWZXJzaW9uOiAwODA2DQo+ ICAgICAgICAgUmVsZWFzZSBEYXRlOiAwMi8yMC8yMDE0DQo+ICAgICAgICAgQWRkcmVzczogMHhG MDAwMA0KPiAgICAgICAgIFJ1bnRpbWUgU2l6ZTogNjQga0INCj4gICAgICAgICBST00gU2l6ZTog MTYgTUINCj4gICAgICAgICBDaGFyYWN0ZXJpc3RpY3M6DQo+ICAgICAgICAgICAgICAgICBQQ0kg aXMgc3VwcG9ydGVkDQo+ICAgICAgICAgICAgICAgICBBUE0gaXMgc3VwcG9ydGVkDQo+ICAgICAg ICAgICAgICAgICBCSU9TIGlzIHVwZ3JhZGVhYmxlDQo+ICAgICAgICAgICAgICAgICBCSU9TIHNo YWRvd2luZyBpcyBhbGxvd2VkDQo+ICAgICAgICAgICAgICAgICBCb290IGZyb20gQ0QgaXMgc3Vw cG9ydGVkDQo+ICAgICAgICAgICAgICAgICBTZWxlY3RhYmxlIGJvb3QgaXMgc3VwcG9ydGVkDQo+ ICAgICAgICAgICAgICAgICBCSU9TIFJPTSBpcyBzb2NrZXRlZA0KPiAgICAgICAgICAgICAgICAg RUREIGlzIHN1cHBvcnRlZA0KPiAgICAgICAgICAgICAgICAgNS4yNSIvMS4yIE1CIGZsb3BweSBz ZXJ2aWNlcyBhcmUgc3VwcG9ydGVkIChpbnQgMTNoKQ0KPiAgICAgICAgICAgICAgICAgMy41Ii83 MjAga0IgZmxvcHB5IHNlcnZpY2VzIGFyZSBzdXBwb3J0ZWQgKGludCAxM2gpDQo+ICAgICAgICAg ICAgICAgICAzLjUiLzIuODggTUIgZmxvcHB5IHNlcnZpY2VzIGFyZSBzdXBwb3J0ZWQgKGludCAx M2gpDQo+ICAgICAgICAgICAgICAgICBQcmludCBzY3JlZW4gc2VydmljZSBpcyBzdXBwb3J0ZWQg KGludCA1aCkNCj4gICAgICAgICAgICAgICAgIDgwNDIga2V5Ym9hcmQgc2VydmljZXMgYXJlIHN1 cHBvcnRlZCAoaW50IDloKQ0KPiAgICAgICAgICAgICAgICAgU2VyaWFsIHNlcnZpY2VzIGFyZSBz dXBwb3J0ZWQgKGludCAxNGgpDQo+ICAgICAgICAgICAgICAgICBQcmludGVyIHNlcnZpY2VzIGFy ZSBzdXBwb3J0ZWQgKGludCAxN2gpDQo+ICAgICAgICAgICAgICAgICBBQ1BJIGlzIHN1cHBvcnRl ZA0KPiAgICAgICAgICAgICAgICAgVVNCIGxlZ2FjeSBpcyBzdXBwb3J0ZWQNCj4gICAgICAgICAg ICAgICAgIEJJT1MgYm9vdCBzcGVjaWZpY2F0aW9uIGlzIHN1cHBvcnRlZA0KPiAgICAgICAgICAg ICAgICAgVGFyZ2V0ZWQgY29udGVudCBkaXN0cmlidXRpb24gaXMgc3VwcG9ydGVkDQo+ICAgICAg ICAgICAgICAgICBVRUZJIGlzIHN1cHBvcnRlZA0KPiAgICAgICAgIEJJT1MgUmV2aXNpb246IDQu Ng0KPiANCj4gSGFuZGxlIDB4MDAwMiwgRE1JIHR5cGUgMiwgMTUgYnl0ZXMNCj4gQmFzZSBCb2Fy ZCBJbmZvcm1hdGlvbg0KPiAgICAgICAgIE1hbnVmYWN0dXJlcjogQVNVU1RlSyBDT01QVVRFUiBJ TkMuDQo+ICAgICAgICAgUHJvZHVjdCBOYW1lOiBCODVNLUUNCj4gICAgICAgICBWZXJzaW9uOiBS ZXYgWC4weA0KPiAgICAgICAgIFNlcmlhbCBOdW1iZXI6IDE0MDUyNjIzODQwNTU4NQ0KPiAgICAg ICAgIEFzc2V0IFRhZzogVG8gYmUgZmlsbGVkIGJ5DQo+IE8uRS5NLg0KPiBGZWF0dXJlczogQm9h cmQgaXMgYSBob3N0aW5nDQo+IGJvYXJkIEJvYXJkIGlzDQo+IHJlcGxhY2VhYmxlIExvY2F0aW9u IEluIENoYXNzaXM6IFRvIGJlIGZpbGxlZCBieQ0KPiBPLkUuTS4gQ2hhc3NpcyBIYW5kbGU6DQo+ IDB4MDAwMyBUeXBlOg0KPiBNb3RoZXJib2FyZCBDb250YWluZWQgT2JqZWN0IEhhbmRsZXM6IDAN Cj4gDQo+ICdlZmlib290bWdyIC12JyBvdXRwdXQ6DQo+IA0KPiBCb290Q3VycmVudDogMDAwNA0K PiBUaW1lb3V0ICAgIDogMSBzZWNvbmRzDQo+IEJvb3RPcmRlciAgOiAwMDAxLCAwMDAyLCAwMDAz LCAwMDA0DQo+ICBCb290MDAwMSogSGFyZCBEcml2ZSAgQkJTKEhELCwweDApDQo+ICBCb290MDAw MiogTmV0d29yayBDYXJkICBCQlMoTmV0d29yaywsMHgwKQ0KPiAgQm9vdDAwMDMqIFVFRkkgT1MN Cj4gSEQoMSxHUFQsNzg0NTllYzAtOTMwMy0xMWU4LTk3ZTYtOThkZWQwMDA5YjFjLDB4MjgsMHg2 NDAwMCkvRmlsZShcRUZJXEJPT1RcQk9PVFg2NC5FRkkpDQo+IGFkYTBwMTovRUZJL0JPT1QvQk9P VFg2NC5FRkkgKG51bGwpDQo+IFBhdGgoMCwwLGFlODRiMTFkZjU4MTcyNGU4NTQ0MmJhYjBjMmNh YzVjMDIwMDAwMDIwMDAwKSArQm9vdDAwMDQqIFVFRkk6IFNhbkRpc2sNCj4gUGNpUm9vdCgweDAp L1BjaSgweDFkLDB4MCkvVVNCKDB4MSwweDApL1VTQigweDQsMHgwKS9IRCgxLE1CUiwweDkwOTA5 MDkwLDB4MSwweDY0MCkNCj4gVmVuSHcoMmQ2NDQ3ZWYtM2JjOS00MWEwLWFjMTktNGQ1MWQwMWI0 Y2U2LDUzMDA2MTAwNmUwMDQ0MDA2OTAwNzMwMDZiMDAwMDAwKQ0KPiANCj4gDQo+IFVucmVmZXJl bmNlZCBWYXJpYWJsZXM6DQo+IA0KPiANCj4gPiBLaW5kIHJlZ2FyZHMsDQo+ID4gDQo+ID4gb2gN Cj4gPiANCj4gPiAtIC0tIA0KPiA+IE8uIEhhcnRtYW5uDQo+ID4gDQo+ID4gSWNoIHdpZGVyc3By ZWNoZSBkZXIgTnV0enVuZyBvZGVyINxiZXJtaXR0bHVuZyBtZWluZXIgRGF0ZW4gZvxyDQo+ID4g V2VyYmV6d2Vja2Ugb2RlciBm/HIgZGllIE1hcmt0LSBvZGVyIE1laW51bmdzZm9yc2NodW5nICin IDI4IEFicy4gNCBCRFNHKS4NCj4gPiAtLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KPiA+ IA0KPiA+IGlMVUVBUk1LQUIwV0lRUVpWWk16QXR3QzJULzg2VHJTNTI4ZnlGaFlsQVVDVzExd2Zn QUtDUkRTNTI4ZnlGaFkNCj4gPiBsTW9qQWY5MjlVU3gxeDdJL3NTR0x0RVdLTzhybTlJWGYxSkVw UTdHU2RJNllIaWQzNjR4N2ZiclVCaERaWXVUDQo+ID4gSlZhblk1N0xpMm9MT1hvZ0h0TXc2ZURV eUQrYUFmOUdURTMwTFVOUmhtY0o3ZWw2MlZ3cG0wb1VCRzJhczUyaQ0KPiA+ICt2NThFWjljMjB5 S1FLdVh0NDQ2ZGhiSUx5T0REUEttYzl5a0F2bkUwVHRNaVRIazZ2Um4NCj4gPiA9TTd2aQ0KPiA+ IC0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLSAgDQo+IA0KPiBSb21hbiBCb2dvcm9kc2tpeQ0K DQpUaGUgb3JkZXIgb2YgdGhlIHBhcnRpdGlvbnMgd2FzIHNpbXBseSBhbiBvYnNlcnZhdGlvbiBh bmQgZnJvbSB0aGUgIm9sZCBkYXlzIiB3aXRoIEhERCBhcw0KbWFzcyBzdG9yYWdlL2Jvb3Qgc3Rv cmFnZSB3aXRoIHJvdGF0aW5nIHBsYXR0ZXJzIGl0IHdhcyBzb21lIHNvcnQgb2YgaW1wb3J0YW50 IGZvciB0aGUNCmFjY2VzcyBsYXRlbmN5IHdoZXJlIHRvIHBvc2l0aW9uIHRoZSBzd2FwIHBhcnRp dGlvbi4gV2l0aCBOQU5EIGZsYXNoIGJhc2VkIFNTRCB0aGlzDQpiZWNhbWUgb2Jzb2xldGUgLSBz bywgcGxlYXNlIGRvbid0IGJlIGJvdGhlcmVkIGFib3V0IHRoYXQuDQoNCi0gRnJvbSBteSAobm9u LWV4cGVydCkgcG9pbnQgb2YgdmlldywgeW91IFVFRkkgdmFyaWFibGVzIGxvb2sgIm5vcm1hbCIg KGFjY29yZGluZyB0byB3aGF0DQpJIHNlZSBvbiBteSBib3hlcyBhdCBob21lKSwgYnV0IEkgd2Fz IHdvbmRlcmluZyBhYm91dCB0aGUgImFnZWQiIGZpcm13YXJlIG9mIHlvdQ0KbWFpbmJvYXJkLiBD aGVja2luZyBvdXQgYXQgQVNVUycgd2Vic2l0ZS9zdXBwb3J0LCB0aGV5IGNsYWltIHRoZXkgaGF2 ZSBhIG1vcmUgcmVjZW50DQpmaXJtYXJlIGZyb20gMjAxOCEgVGhpcyB3b3VsZCBiZSBvbiBwYXIg d2l0aCB0aGUgU3BlY3RyZS9NZWx0ZG93biBtaXRpZ2F0aW9uIHByb21pc2VzDQptYWRlIGJ5IG1v c3QgdmFsdWFibGUvcmVsaWFibGUgbWFpbmJvYXJkIHZlbmRvcnMgYW5kIEludGVsOg0KDQpodHRw czovL3d3dy5hc3VzLmNvbS9Nb3RoZXJib2FyZHMvQjg1TUUvSGVscERlc2tfQklPUy8NCg0KIFZl cnNpb24gMzYwMiAyMDE4LzA1LzI1IDcuMjkgTUJ5dGUgQjg1TS1FIEJJT1MgMzYwMg0KDQpTaW5j ZSBkbWlkZWNvZGUgcmVwb3J0cyBvbiBteSBBU1JvY2sgY3JhcCBtYWluYm9hcmQgYWxzbw0KDQpC SU9TIFJldmlzaW9uOiA0LjYNCg0KSSBndWVzcyB0aGlzIG9uZSBpcyBmYWtlIG9yIHNvbWUgImRl ZmF1bHQiIGZyb20gdGhlIGRtaWRlY29kZSBwcm9ncmFtIG5vdCBpZGVudGlmeWluZw0KdGhlIGNv cnJlY3QgcmV2aXNpb24gLSBvciBpdCdzIGFub3RoZXIgc2VtYW50aWMgbm90IGtub3duIHRvIG1l Lg0KDQpCdXQgbXkgZG1pZGVjb2RlIGxvb2tzIGxpa2UgdGhpcywgd2l0aCB0aGUgbGF0ZXN0IEJF VEEgQVNyb2NrIHByb3ZpZGVzIGZvciB0aGlzIGxvbmcNCnRpbWUgYWdvIGRpc2NvbnRpbnVlZCBa NzcgUHJvNC1ib2FyZDogDQoNClsuLi5dDQoNCiMgZG1pZGVjb2RlIDMuMQ0KIyBTTUJJT1MgZW50 cnkgcG9pbnQgYXQgMHgwMDBmMDRjMA0KRm91bmQgU01CSU9TIGVudHJ5IHBvaW50IGluIEVGSSwg cmVhZGluZyB0YWJsZSBmcm9tIC9kZXYvbWVtLg0KU01CSU9TIDIuNyBwcmVzZW50Lg0KMjYgc3Ry dWN0dXJlcyBvY2N1cHlpbmcgMTUyMyBieXRlcy4NClRhYmxlIGF0IDB4MDAwRUU3RjAuDQoNCkhh bmRsZSAweDAwMDAsIERNSSB0eXBlIDAsIDI0IGJ5dGVzDQpCSU9TIEluZm9ybWF0aW9uDQogICAg ICAgIFZlbmRvcjogQW1lcmljYW4gTWVnYXRyZW5kcyBJbmMuDQogICAgICAgIFZlcnNpb246IFAy LjAwDQogICAgICAgIFJlbGVhc2UgRGF0ZTogMDMvMTMvMjAxOA0KICAgICAgICBBZGRyZXNzOiAw eEYwMDAwDQogICAgICAgIFJ1bnRpbWUgU2l6ZTogNjQga0INCiAgICAgICAgUk9NIFNpemU6IDgx OTIga0INCiAgICAgICAgQ2hhcmFjdGVyaXN0aWNzOg0KICAgICAgICAgICAgICAgIFBDSSBpcyBz dXBwb3J0ZWQNCiAgICAgICAgICAgICAgICBCSU9TIGlzIHVwZ3JhZGVhYmxlDQogICAgICAgICAg ICAgICAgQklPUyBzaGFkb3dpbmcgaXMgYWxsb3dlZA0KICAgICAgICAgICAgICAgIEJvb3QgZnJv bSBDRCBpcyBzdXBwb3J0ZWQNCiAgICAgICAgICAgICAgICBTZWxlY3RhYmxlIGJvb3QgaXMgc3Vw cG9ydGVkDQogICAgICAgICAgICAgICAgQklPUyBST00gaXMgc29ja2V0ZWQNCiAgICAgICAgICAg ICAgICBFREQgaXMgc3VwcG9ydGVkDQogICAgICAgICAgICAgICAgNS4yNSIvMS4yIE1CIGZsb3Bw eSBzZXJ2aWNlcyBhcmUgc3VwcG9ydGVkIChpbnQgMTNoKQ0KICAgICAgICAgICAgICAgIDMuNSIv NzIwIGtCIGZsb3BweSBzZXJ2aWNlcyBhcmUgc3VwcG9ydGVkIChpbnQgMTNoKQ0KICAgICAgICAg ICAgICAgIDMuNSIvMi44OCBNQiBmbG9wcHkgc2VydmljZXMgYXJlIHN1cHBvcnRlZCAoaW50IDEz aCkNCiAgICAgICAgICAgICAgICBQcmludCBzY3JlZW4gc2VydmljZSBpcyBzdXBwb3J0ZWQgKGlu dCA1aCkNCiAgICAgICAgICAgICAgICA4MDQyIGtleWJvYXJkIHNlcnZpY2VzIGFyZSBzdXBwb3J0 ZWQgKGludCA5aCkNCiAgICAgICAgICAgICAgICBTZXJpYWwgc2VydmljZXMgYXJlIHN1cHBvcnRl ZCAoaW50IDE0aCkNCiAgICAgICAgICAgICAgICBQcmludGVyIHNlcnZpY2VzIGFyZSBzdXBwb3J0 ZWQgKGludCAxN2gpDQogICAgICAgICAgICAgICAgQUNQSSBpcyBzdXBwb3J0ZWQNCiAgICAgICAg ICAgICAgICBVU0IgbGVnYWN5IGlzIHN1cHBvcnRlZA0KICAgICAgICAgICAgICAgIEJJT1MgYm9v dCBzcGVjaWZpY2F0aW9uIGlzIHN1cHBvcnRlZA0KICAgICAgICAgICAgICAgIFRhcmdldGVkIGNv bnRlbnQgZGlzdHJpYnV0aW9uIGlzIHN1cHBvcnRlZA0KICAgICAgICAgICAgICAgIFVFRkkgaXMg c3VwcG9ydGVkDQogICAgICAgIEJJT1MgUmV2aXNpb246IDQuNg0KWy4uLl0NCg0KV2F0Y2ggb3V0 IHRoZSBWZXJzaW9uOiBQMi4wMCBlbnRyeSwgd2hpY2ggaXMgaW5kZWVkIHRoZSB2ZXJzaW9uIG51 bWJlciBvZiB0aGUgZmlybXdhcmUuDQpTbywgaW4geW91ciBjYXNlLCB0aGUgZmlybXdhcmUgaXMg YWxzbyBhIGJpdCBvdXRkYXRlZCwgZnJvbSAyMDE0LiBJJ2QgdXBkYXRlIHRoZSBmaXJtd2FyZQ0K cHJpb3IgdG8gYW55IGZ1cnRoZXIgYWN0aW9uIGlmIHRoZXJlIGFyZSBubyBvYmxpZ2F0aW9ucyBm cm9tIGhhcmR3YXJlIGluY29tcGF0aWJpbGl0aWVzDQpzbyBmYXIgdG8gbWVldCB0aGUgbmVjY2Vz c2l0eSBvZiBsYXRlcyBJbnRlbC9BTUQgbWljcm9jb2RlIHVwZGF0ZXMgYW5kL29yIG90aGVyIFVF RkkNCnZ1bG5lcmFiaWxpdGllcyBvZiB3aGljaCBJIGhhdmUgbm8gYWN0aXZlIG1lbW9yaWVzIGFi b3V0LCBidXQgdGhleSBoaXQgbWUgMjAxNS8yMDE2IG9uDQpvdXIgc2VydmVycy4gVGhlcmUgaXMg bm8gZ3VhcmFudGVlIHRoYXQgdGhlIGZpcm13YXJlIHVwZGF0ZSB3aWxsIHNhbHZhZ2UgeW91ciBw cm9ibGVtLA0KYnV0IHRoYXQgbWlnaHQgYmUgd29ydGggYSBzaG90LiBBbHNvLCBBU1VTIG1lbnRp b24gdG8gaGF2ZSBzb2x2ZWQgcGVyZm9ybWFuY2UgaXNzdWVzDQp3aXRoIHRoZSBsYXRlc3QgZmly bXdhcmUsIHBsZWFzZSBjb25zaWRlciBjb25zdWx0aW5nIHRoZSBkZXNjcmlwdGlvbiBvZiB0aGUg bGF0ZXN0DQpmaXJtd2FyZSByZWxlYXNlLiANCg0KQXMgdGhlIG5leHQgc3RlcCwgYXMgZnJvbSBt eSAibmFpdmUiIHBvaW50IG9mIHZpZXcsIEkgd291bGQgcGVyZm9ybSB0aGUgc3RlcHMgcmVjb21t ZW5kZWQNCnRvIG1lIGJ5IEZyZWVCU0QncyBkZXZlbG9wZXJzIHRvIHNldCB0aGUgVUVGSSB2YXJp YWJsZXMgYWdhaW46DQoNCkJvb3QgaW4gVUVGSSBtb2RlIGZyb20gdGhlIFVTQiBmbGFzaCBkZXZp Y2UNCkxvZ29uIGFzIHJvb3QNCm1vdW50IC11dyAvDQprbGRsb2FkIGVmaXJ0DQptb3VudCAtdCBt c2Rvc2ZzIC9kZXYvYWRhMHAxIC9tbnQNCg0KZWZpYm9vdG1nciAtYyAtbCAvbW50L2VmaS9ib290 L0JPT1R4NjQuZWZpIC1MIEZyZWVCU0QNCmVmaWJvb3RtZ3IgLXYNCg0KTG9vayBmb3IgdGhlICJC b290MDAwWCIgZW50cnkgbGFiZWxlZCB3aXRoICJGcmVlQlNEIiwgdGFrZSB0aGUgbnVtYmVyIHBv cnRpb24gb2YgdGhlIHRoYXQNCkJvb3QwMDBYIHZhcmlhYmxlICgwMDBYKSBhbmQgcGVyZm9ybQ0K DQplZmlib290bWdyIC1hIDAwMFgNCmVmaWJvb3RtZ3IgLW4gMDAwWCAodGhpcyBvbmUgaXMgImV4 dHJhIiBhbmQgY2FuIGJlIG9tbWl0ZWQsIGl0IG1lYW5zICJuZXh0IGJvb3QiLCBzZWUNCm1hbnBh Z2UgZWZpYm9vdG1ncig4KSkNCg0KYW5kIGNoZWNrIGFnYWluIHdpdGggDQoNCmVmaWJvb3RtZ3Ig LXYNCg0KVGhlICJtYW5ldXZlciIgYWJvdmUgaXMgb25seSBpbiBjYXNlIHRoZSBzZXR0aW5ncyBv ZiBVRUZJIHZhcmlhYmxlcyBoYXMgZ29uZSByb2d1ZS4NCg0KUmVnYXJkcywNCg0Kb2gNCg0KDQoN Ci0gLS0gDQpPLiBIYXJ0bWFubg0KDQpJY2ggd2lkZXJzcHJlY2hlIGRlciBOdXR6dW5nIG9kZXIg 3GJlcm1pdHRsdW5nIG1laW5lciBEYXRlbiBm/HINCldlcmJlendlY2tlIG9kZXIgZvxyIGRpZSBN YXJrdC0gb2RlciBNZWludW5nc2ZvcnNjaHVuZyAopyAyOCBBYnMuIDQgQkRTRykuDQotLS0tLUJF R0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KDQppTFVFQVJNS0FCMFdJUVFaVlpNekF0d0MyVC84NlRy UzUyOGZ5RmhZbEFVQ1cxMkJGZ0FLQ1JEUzUyOGZ5RmhZDQpsTFpPQWYwVjlyLzBMek1vS09KZnhO aEJOc0xHRmtWUnhCNnp2OU9RVjN5dEFjekdiNGFsR0pSTXY4UHFEbFBpDQpWeGdwM0QrQXE1SjlC L1RoaDJQQ0VYOXY4QUZ1QWdDb1V6dHdkN0FQQmVDYVcxVFZpdldsN1g5UHB1U1pJY2xVDQpQaGlh eHhVNTFEWWVraktaRUVVaXdKaXE3NUtaSCs2U0dkenZmRU4rMGE1SDFCSzJhd2dQDQo9ZnpSVQ0K LS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQo= From owner-freebsd-current@freebsd.org Sun Jul 29 11:18:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 780F31053AAA for ; Sun, 29 Jul 2018 11:18:01 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E39A87C6F6 for ; Sun, 29 Jul 2018 11:18:00 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id l2-v6so5908615wme.1 for ; Sun, 29 Jul 2018 04:18:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=4iI28UFemhMPU5J+sXDHA47jdwsOGjytoff15JqtYCE=; b=uPvyaS9wwZ2J2mu1WMjhc5eP8rqvcgJnAE/rr0eegJwBrXbbD/e9+0dUEwMsukAL5O 0k1ZGbH36fk5cSEdz3FsbIjdQDpNN2IxPDSlM4OUIn6QrII1O55JdoQ9fj8fvu0doAgh QJj7vYp9QDVoR5ea+AlfMrAn+jwgnplIndWyqflpu9lFIpZ1X9DO8YYswibj9xoANz0b xl/a5ZriS+Z0t/i8FQ25AyyEZA8ncR9IiIgMLjRfLrrMG6Pm+bw2XGOJG8IStEPqty2J a4Fwf1lfYvHCFZl5ngU3Pwo9taW6YFxvdF8EGUj9bbIFCqSC0QNZtm2gVmEGIX5J6CyU PxWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=4iI28UFemhMPU5J+sXDHA47jdwsOGjytoff15JqtYCE=; b=kGWxhnmyieqhHS0pmevVJb2gty2rv3MnpbGFBDRXHn/AWevKsmbYpCEA7LgnS62Zzx W6jel3z+e+oGL27KBa8cbH0zHnpHIpJL5Vq/IgAjBGfHYemdlmNR3bhiucXQSQfFjWN9 mooOJnEr9eMKx9EjOwPRpHMyuNE1HJuF06YoxRK92V9cF7q+pcM4QsLfz6svtOb+BrzT 12l7TYOnFqVZrZYaXzvnIfVJtuFA+/q8bxWhHkfchWvwpkqtOt+MNTEE9zwA9/kfNVCU jTh+ixi9F+0Us9OfT+WhsYLlxvwd6fo48VNfKeZT3G4X6EcZjSoUCBsyEGLka7dGAV8M tOIg== X-Gm-Message-State: AOUpUlGhUtGRDUHxa3/OCXcRzb+6sWpOzyfjLMONjEWKY4zXAeVj5CZt oEs4rcL1yOBVBpzst7/W3Y8FEbJnvJ8= X-Google-Smtp-Source: AAOMgpdGMm1hF5iWaJRB1n6/d5dvWX3oSXLbcMNLH52YHHScA6HyImX35q0UxkjjTKWSLKNtAxb1xg== X-Received: by 2002:a1c:6d94:: with SMTP id b20-v6mr11418982wmi.28.1532863079165; Sun, 29 Jul 2018 04:17:59 -0700 (PDT) Received: from kloomba ([95.104.142.14]) by smtp.gmail.com with ESMTPSA id w9-v6sm7282623wrr.77.2018.07.29.04.17.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Jul 2018 04:17:58 -0700 (PDT) Sender: Roman Bogorodskiy Date: Sun, 29 Jul 2018 15:17:53 +0400 From: Roman Bogorodskiy To: "O. Hartmann" Cc: freebsd-current@freebsd.org Subject: Re: EFI issues Message-ID: <20180729111751.GC2216@kloomba> References: <20180728072938.GA28778@kloomba> <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> <20180729080957.GB2216@kloomba> <20180729105550.4ac8711a@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pAwQNkOnpTn9IO2O" Content-Disposition: inline In-Reply-To: <20180729105550.4ac8711a@thor.intern.walstatt.dynvpn.de> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 11:18:01 -0000 --pAwQNkOnpTn9IO2O Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable O. Hartmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > Am Sun, 29 Jul 2018 12:09:58 +0400 > Roman Bogorodskiy schrieb: >=20 > > O. Hartmann wrote: > >=20 > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA512 > > >=20 > > > Am Sat, 28 Jul 2018 11:29:40 +0400 > > > Roman Bogorodskiy schrieb: > > > =20 > > > > Hi, > > > >=20 > > > > I have a test box that's updated to -CURRENT usually once in a week= or > > > > two. This box boots using UEFI. After a regular update about two we= eks > > > > ago it started to panic on boot frequently (not UEFI related), but I > > > > could not get a crash dump because my swap partition was too small.= So I > > > > moved data to the backup drive, repartitioned the main drive and bo= ot > > > > again. This went fine, so I decided to upgrade to fresh -CURRENT fr= om > > > > ~Jul 27th. Booting with the new kernel went fine, but after install= world > > > > machine stopped booting, and on the screen I see: > > > >=20 > > > > FreeBSD/amd64 EFI loader, ... > > > >=20 > > > > .. > > > >=20 > > > > BootOrder: .... > > > >=20 > > > > And then it gets stuck and nothing happens. > > > >=20 > > > > As I already have a fresh backup, I decided that it'd be easier to > > > > just re-install and copy data back over (maybe I messed up with > > > > repartitioning). So I've downloaded a fresh snapshot: > > > >=20 > > > > FreeBSD-12.0-CURRENT-amd64-20180726-r336739-memstick.img > > > >=20 > > > > And re-installed. In the installer I choose all the same settings t= hat > > > > were before: UEFI + GPT, default partition scheme it suggested (efi > > > > followed by freebsd-ufs followed by freebsd-swap), just increased t= he > > > > swap size. > > > >=20 > > > > And the newly installed system won't boot just like a previous one: > > > >=20 > > > > https://people.freebsd.org/~novel/misc/freebsd_efi_lookup.jpg > > > >=20 > > > > Is there a way to recover this? > > > >=20 > > > > Roman Bogorodskiy =20 > > >=20 > > > Just curious: > > >=20 > > > When I installed FreeBSD last time from the recent (2018-07-26) USB f= lash drive on a > > > SSD, the freebsd-swap partition followed immediately after the ESP an= d/or > > > freebsd-boot GPT loader partition. But in most cases I used to use ZF= S for testing. =20 > >=20 > > When I reinstalled it yesterday from -CURRENT snapshot mentioned above, > > in guided mode it suggested a similar partitioning schema that I use: > >=20 > > =3D> 40 1953525088 ada0 GPT (932G) =20 > > 40 409600 1 efi (200M) > > 409640 1803550720 2 freebsd-ufs (860G) > > 1803960360 148897792 3 freebsd-swap (71G) > > 1952858152 666976 - free - (326M) > >=20 > > The only difference it that the freebsd-swap size was 3.5G (and > > therefore, freebsd-ufs is large), the order was the same. > >=20 > > > Since I had my UEFI adventure of my own these days and received valua= ble hints from > > > the development/maintenance team on some UEFI aspects, it would be of= interest to > > > know your recent hardware and, more importantly since I see the boot = order presented > > > in you screenshot, a dump of the efi variable settings. Just for curi= osity. For that, > > > you have to boot the recent USB flash drive image with UEFI-only, the= n logon as root > > > and perform > > >=20 > > > kldload efirt > > >=20 > > > and then issue=20 > > >=20 > > > # efibootmgr -v > > >=20 > > > In my case, it looks like > > >=20 > > > [...] > > > [ohartmann]: sudo efibootmgr -v > > > BootCurrent: 0001 > > > Timeout : 3 seconds > > > BootOrder : 0001, 0002, 0003, 0004, 0005, 0000 > > > +Boot0001* FreeBSD-12 \ > > > HD(1,GPT,e1460941-e2e9-11e5-b913-d0509907ef09,0x28,0x640)/File(\ef= i\boot\BOOTx64.efi) > > > \ ada0p1:/efi/boot/BOOTx64.efi (null)=20 > > > Boot0002* Hard Drive BBS(HD,,0x0) > > > Boot0003* CD/DVD Drive BBS(CDROM,,0x0) > > > Boot0004* USB BBS(USB,,0x0) > > > Boot0005* Network Card BBS(Network,,0x0) > > > Boot0000 FreeBSD-12 > > > HD(1,GPT,e1460941-e2e9-11e5-b913-d0509907ef09,0x28,0x640)/File(\efi\b= oot\BOOTx64.efi) > > > ada0p1:/efi/boot/BOOTx64.efi (null) > > >=20 > > >=20 > > > Unreferenced Variables: > > > [...] > > >=20 > > > Boot0000 is the same as Boot0001 and is defined due to some "bug" War= ner Losh has > > > fixed recently, it is the same as Boot0001 =20 > >=20 > > Motherboard is (from dmidecode): > >=20 > > Handle 0x0000, DMI type 0, 24 bytes > > BIOS Information > > Vendor: American Megatrends Inc. > > Version: 0806 > > Release Date: 02/20/2014 > > Address: 0xF0000 > > Runtime Size: 64 kB > > ROM Size: 16 MB > > Characteristics: > > PCI is supported > > APM is supported > > BIOS is upgradeable > > BIOS shadowing is allowed > > Boot from CD is supported > > Selectable boot is supported > > BIOS ROM is socketed > > EDD is supported > > 5.25"/1.2 MB floppy services are supported (int 13h) > > 3.5"/720 kB floppy services are supported (int 13h) > > 3.5"/2.88 MB floppy services are supported (int 13h) > > Print screen service is supported (int 5h) > > 8042 keyboard services are supported (int 9h) > > Serial services are supported (int 14h) > > Printer services are supported (int 17h) > > ACPI is supported > > USB legacy is supported > > BIOS boot specification is supported > > Targeted content distribution is supported > > UEFI is supported > > BIOS Revision: 4.6 > >=20 > > Handle 0x0002, DMI type 2, 15 bytes > > Base Board Information > > Manufacturer: ASUSTeK COMPUTER INC. > > Product Name: B85M-E > > Version: Rev X.0x > > Serial Number: 140526238405585 > > Asset Tag: To be filled by > > O.E.M. > > Features: Board is a hosting > > board Board is > > replaceable Location In Chassis: To be filled by > > O.E.M. Chassis Handle: > > 0x0003 Type: > > Motherboard Contained Object Handles: 0 > >=20 > > 'efibootmgr -v' output: > >=20 > > BootCurrent: 0004 > > Timeout : 1 seconds > > BootOrder : 0001, 0002, 0003, 0004 > > Boot0001* Hard Drive BBS(HD,,0x0) > > Boot0002* Network Card BBS(Network,,0x0) > > Boot0003* UEFI OS > > HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28,0x64000)/File(\EFI\B= OOT\BOOTX64.EFI) > > ada0p1:/EFI/BOOT/BOOTX64.EFI (null) > > Path(0,0,ae84b11df581724e85442bab0c2cac5c020000020000) +Boot0004* UEFI:= SanDisk > > PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x4,0x0)/HD(1,MBR,0x9090909= 0,0x1,0x640) > > VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6,530061006e004400690073006b00= 0000) > >=20 > >=20 > > Unreferenced Variables: > >=20 > >=20 > > > Kind regards, > > >=20 > > > oh > > >=20 > > > - --=20 > > > O. Hartmann > > >=20 > > > Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr > > > Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs.= 4 BDSG). > > > -----BEGIN PGP SIGNATURE----- > > >=20 > > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW11wfgAKCRDS528fyFhY > > > lMojAf929USx1x7I/sSGLtEWKO8rm9IXf1JEpQ7GSdI6YHid364x7fbrUBhDZYuT > > > JVanY57Li2oLOXogHtMw6eDUyD+aAf9GTE30LUNRhmcJ7el62Vwpm0oUBG2as52i > > > +v58EZ9c20yKQKuXt446dhbILyODDPKmc9ykAvnE0TtMiTHk6vRn > > > =3DM7vi > > > -----END PGP SIGNATURE----- =20 > >=20 > > Roman Bogorodskiy >=20 > The order of the partitions was simply an observation and from the "old d= ays" with HDD as > mass storage/boot storage with rotating platters it was some sort of impo= rtant for the > access latency where to position the swap partition. With NAND flash base= d SSD this > became obsolete - so, please don't be bothered about that. >=20 > - From my (non-expert) point of view, you UEFI variables look "normal" (a= ccording to what > I see on my boxes at home), but I was wondering about the "aged" firmware= of you > mainboard. Checking out at ASUS' website/support, they claim they have a = more recent > firmare from 2018! This would be on par with the Spectre/Meltdown mitigat= ion promises > made by most valuable/reliable mainboard vendors and Intel: >=20 > https://www.asus.com/Motherboards/B85ME/HelpDesk_BIOS/ >=20 > Version 3602 2018/05/25 7.29 MByte B85M-E BIOS 3602 >=20 > Since dmidecode reports on my ASRock crap mainboard also >=20 > BIOS Revision: 4.6 >=20 > I guess this one is fake or some "default" from the dmidecode program not= identifying > the correct revision - or it's another semantic not known to me. >=20 > But my dmidecode looks like this, with the latest BETA ASrock provides fo= r this long > time ago discontinued Z77 Pro4-board:=20 >=20 > [...] >=20 > # dmidecode 3.1 > # SMBIOS entry point at 0x000f04c0 > Found SMBIOS entry point in EFI, reading table from /dev/mem. > SMBIOS 2.7 present. > 26 structures occupying 1523 bytes. > Table at 0x000EE7F0. >=20 > Handle 0x0000, DMI type 0, 24 bytes > BIOS Information > Vendor: American Megatrends Inc. > Version: P2.00 > Release Date: 03/13/2018 > Address: 0xF0000 > Runtime Size: 64 kB > ROM Size: 8192 kB > Characteristics: > PCI is supported > BIOS is upgradeable > BIOS shadowing is allowed > Boot from CD is supported > Selectable boot is supported > BIOS ROM is socketed > EDD is supported > 5.25"/1.2 MB floppy services are supported (int 13h) > 3.5"/720 kB floppy services are supported (int 13h) > 3.5"/2.88 MB floppy services are supported (int 13h) > Print screen service is supported (int 5h) > 8042 keyboard services are supported (int 9h) > Serial services are supported (int 14h) > Printer services are supported (int 17h) > ACPI is supported > USB legacy is supported > BIOS boot specification is supported > Targeted content distribution is supported > UEFI is supported > BIOS Revision: 4.6 > [...] >=20 > Watch out the Version: P2.00 entry, which is indeed the version number of= the firmware. > So, in your case, the firmware is also a bit outdated, from 2014. I'd upd= ate the firmware > prior to any further action if there are no obligations from hardware inc= ompatibilities > so far to meet the neccessity of lates Intel/AMD microcode updates and/or= other UEFI > vulnerabilities of which I have no active memories about, but they hit me= 2015/2016 on > our servers. There is no guarantee that the firmware update will salvage = your problem, > but that might be worth a shot. Also, ASUS mention to have solved perform= ance issues > with the latest firmware, please consider consulting the description of t= he latest > firmware release.=20 >=20 > As the next step, as from my "naive" point of view, I would perform the s= teps recommended > to me by FreeBSD's developers to set the UEFI variables again: >=20 > Boot in UEFI mode from the USB flash device > Logon as root > mount -uw / > kldload efirt > mount -t msdosfs /dev/ada0p1 /mnt >=20 > efibootmgr -c -l /mnt/efi/boot/BOOTx64.efi -L FreeBSD > efibootmgr -v >=20 > Look for the "Boot000X" entry labeled with "FreeBSD", take the number por= tion of the that > Boot000X variable (000X) and perform >=20 > efibootmgr -a 000X > efibootmgr -n 000X (this one is "extra" and can be ommited, it means "nex= t boot", see > manpage efibootmgr(8)) >=20 > and check again with=20 >=20 > efibootmgr -v >=20 > The "maneuver" above is only in case the settings of UEFI variables has g= one rogue. >=20 > Regards, >=20 > oh I've updated BIOS (which alone didn't change anything) and executed commands you suggested, and it helped! Thanks! Now 'efibootmgr -v' output looks like this: BootCurrent: 0000 Timeout : 1 seconds BootOrder : 0000, 0004, 0006, 0003, 0007 +Boot0000* FreeBSD HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28,0x640= 00)/File(\efi\boot\BOOTx64.efi) ada0p1:/efi/boot/BOOTx64.efi (null) Boot0004* Hard Drive BBS(HD,,0x0) Boot0006* Network Card BBS(Network,,0x0) Boot0003* UEFI OS HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28,0x640= 00)/File(\EFI\BOOT\BOOTX64.EFI) ada0p1:/EFI/BOOT/BOOTX64.EFI (null) Path(0,0,ef47642dc93ba041ac194d51d01b4ce65200650061006c00= 740065006b00200042006f006f00740020004100670065006e0074000000) Boot0007* UEFI: SanDisk PciRoot(0x0)/Pci(0x14,0x0)/USB(0x9,0x0)/HD(1,MBR,0= x90909090,0x1,0x640) VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6,34004300= 350033003100300030003100350034003100300031003500310030003900300039003500000= 0) Unreferenced Variables: This is strange, because the only difference I see is that Boot0000 has lowercase filenames ('/efi/boot/BOOTx64.efi' vs '/EFI/BOOT/BOOTX64.EFI'). I'm wondering if that's the only reason it wasn't working before? > - --=20 > O. Hartmann >=20 > Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr > Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs. 4 B= DSG). > -----BEGIN PGP SIGNATURE----- >=20 > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW12BFgAKCRDS528fyFhY > lLZOAf0V9r/0LzMoKOJfxNhBNsLGFkVRxB6zv9OQV3ytAczGb4alGJRMv8PqDlPi > Vxgp3D+Aq5J9B/Thh2PCEX9v8AFuAgCoUztwd7APBeCaW1TVivWl7X9PpuSZIclU > PhiaxxU51DYekjKZEEUiwJiq75KZH+6SGdzvfEN+0a5H1BK2awgP > =3DfzRU > -----END PGP SIGNATURE----- Roman Bogorodskiy --pAwQNkOnpTn9IO2O Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbXaJfAAoJEMltX/4IwiJqv1oH/Rb994mHo4UiyMiiP+WksFgF e3PJoxrHCKH1ItlqGilZYLHg1TeLEkL6xExzFGI+v2xGqu+RYCfEErMAF9TyX5j+ ZpiHkO5gCQs2PYE0mqkeS8CXKJ6lfWHW6pzJFYyFTqhi/FwZOOt8lRb6j1RX7rJM iC8dB533jGq6KsLUTQIcfruPsMjctGUF1WdWCYs2TWNMdjGyF16fStJokKxtR9z7 3tMu7zIBUcBjBFepeC7uFmLdxscAGPloEA6cc/64UZrzI1HpJ6Al/vgKQ7sjrAsC NLtDYQMG4Hhl0sJilRchrPfKNM8azIkjPeYhiTyIR25ojvmfZ7ZTDOdl/7m55Bk= =NBrr -----END PGP SIGNATURE----- --pAwQNkOnpTn9IO2O-- From owner-freebsd-current@freebsd.org Sun Jul 29 12:35:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB9BA105647E for ; Sun, 29 Jul 2018 12:35:57 +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 3B4497FB44; Sun, 29 Jul 2018 12:35:56 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([2.245.38.16]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M1iGk-1fze8x3qGo-00tliS; Sun, 29 Jul 2018 14:35:38 +0200 Date: Sun, 29 Jul 2018 14:35:02 +0200 From: "O. Hartmann" To: Roman Bogorodskiy Cc: "O. Hartmann" , freebsd-current@freebsd.org, Toomas Soome , "Rodney W. Grimes" , Warner Losh , Allan Jude Subject: Re: EFI issues Message-ID: <20180729143529.16bad01a@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180729111751.GC2216@kloomba> References: <20180728072938.GA28778@kloomba> <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> <20180729080957.GB2216@kloomba> <20180729105550.4ac8711a@thor.intern.walstatt.dynvpn.de> <20180729111751.GC2216@kloomba> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:SvqHgRR0Oei8sz1Ym/ksgFtIXLmshsPv49CFF/voqkVTZsArR8d 38Z2q3SYYJM9Cldnionx1KlVqkBPPCOyUIFEqqLPYgZXFQvEQx/CkV866SDGbD0CbQtMb0x K7JIHtBUTqO+IXtfO0yPCDPrBbEp+NiY7G1sHBtUG44SvfB+AjmZOWfmIgLEu06rClPDci7 6PHyGJQpz9gwl87MjWEvA== X-UI-Out-Filterresults: notjunk:1;V01:K0:9CJqKCzajgw=:6OIa3lKjTTK2m/D5mfWkJn XOn39CdS6hMM+B5WKHv2tza94irF7o9eHCbSvD4g6XRFngbvBO2vAwr2aAY6hI8i0ES9lCOHA cMVmhPu+cX1JdqVq68NmU4BpGGGei1G9YkBQTnSc7sfQsHxV5YLAEUxg7FC1lNZn5AZQ1viwv MnRjSZc2jXx4wWvdSMsyZO5VrlN1XBaDecHx2CTpPvUhj360RZtl7wiBaP1E0DVgVf9rT5LN3 BoV5tlmLrnaYvbmcziLwC7aHuy3TtH5A+borVNwUNPeeegkp8Qu5dX5/NIQJqhALHuJLKSao+ gzpZGULpnK6QyZ1937aRDAc2mSkuH7pRA8kzPlKbF+Ww9Ufr5nPPvUX6Ggf7NTycgujmVRs8N TzRZdncL6o54j+PGgRRu/FLUoRk/mosBHj4p7Au4znTVuLQ8G4sFg+bTUf6wmx3FrXIK3JRP3 KvEcOjOCy6Sy2bPoWe8X/lAdAqatxs9dJ/utri6uJWEJTJP712gs7cBRFUky8JLxW6h1ubUxr szGgt/hDSg8kjkYljedX09Hk9di5K7rl6KbRNukeVlODJKPm0fzLBhvd0P5EqmOu+8ZBnRYCZ BOPdl5PO9luut5RlK5JqJ563U5gS9ywZnqbkVxMbkKROFYjE5mUYILFiPqDEgTenInF1hWxof wFImSMHZ6MByyHNLQuYD6eQGIeTlGzfpzqBaQl66+W20OVMZsqE/zg3JvvXDqDLzyyzwwEIhr BwgaP9ua5gblAq7+LcZJKMwTonw3eL/z9LbKSjNVtVQXs+Na3WpLaSO38eOrg2B8t61G9g/lN nh9U3Jq X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 12:35:58 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkFtIFN1 biwgMjkgSnVsIDIwMTggMTU6MTc6NTMgKzA0MDANClJvbWFuIEJvZ29yb2Rza2l5IDxub3ZlbEBm cmVlYnNkLm9yZz4gc2NocmllYjoNCg0KPiAgIE8uIEhhcnRtYW5uIHdyb3RlOg0KPiANCj4gPiAt LS0tLUJFR0lOIFBHUCBTSUdORUQgTUVTU0FHRS0tLS0tDQo+ID4gSGFzaDogU0hBNTEyDQo+ID4g DQo+ID4gQW0gU3VuLCAyOSBKdWwgMjAxOCAxMjowOTo1OCArMDQwMA0KPiA+IFJvbWFuIEJvZ29y b2Rza2l5IDxub3ZlbEBmcmVlYnNkLm9yZz4gc2NocmllYjoNCj4gPiAgIA0KPiA+ID4gICBPLiBI YXJ0bWFubiB3cm90ZToNCj4gPiA+ICAgDQo+ID4gPiA+IC0tLS0tQkVHSU4gUEdQIFNJR05FRCBN RVNTQUdFLS0tLS0NCj4gPiA+ID4gSGFzaDogU0hBNTEyDQo+ID4gPiA+IA0KPiA+ID4gPiBBbSBT YXQsIDI4IEp1bCAyMDE4IDExOjI5OjQwICswNDAwDQo+ID4gPiA+IFJvbWFuIEJvZ29yb2Rza2l5 IDxub3ZlbEBmcmVlYnNkLm9yZz4gc2NocmllYjoNCj4gPiA+ID4gICAgIA0KPiA+ID4gPiA+IEhp LA0KPiA+ID4gPiA+IA0KPiA+ID4gPiA+IEkgaGF2ZSBhIHRlc3QgYm94IHRoYXQncyB1cGRhdGVk IHRvIC1DVVJSRU5UIHVzdWFsbHkgb25jZSBpbiBhIHdlZWsgb3INCj4gPiA+ID4gPiB0d28uIFRo aXMgYm94IGJvb3RzIHVzaW5nIFVFRkkuIEFmdGVyIGEgcmVndWxhciB1cGRhdGUgYWJvdXQgdHdv IHdlZWtzDQo+ID4gPiA+ID4gYWdvIGl0IHN0YXJ0ZWQgdG8gcGFuaWMgb24gYm9vdCBmcmVxdWVu dGx5IChub3QgVUVGSSByZWxhdGVkKSwgYnV0IEkNCj4gPiA+ID4gPiBjb3VsZCBub3QgZ2V0IGEg Y3Jhc2ggZHVtcCBiZWNhdXNlIG15IHN3YXAgcGFydGl0aW9uIHdhcyB0b28gc21hbGwuIFNvIEkN Cj4gPiA+ID4gPiBtb3ZlZCBkYXRhIHRvIHRoZSBiYWNrdXAgZHJpdmUsIHJlcGFydGl0aW9uZWQg dGhlIG1haW4gZHJpdmUgYW5kIGJvb3QNCj4gPiA+ID4gPiBhZ2Fpbi4gVGhpcyB3ZW50IGZpbmUs IHNvIEkgZGVjaWRlZCB0byB1cGdyYWRlIHRvIGZyZXNoIC1DVVJSRU5UIGZyb20NCj4gPiA+ID4g PiB+SnVsIDI3dGguIEJvb3Rpbmcgd2l0aCB0aGUgbmV3IGtlcm5lbCB3ZW50IGZpbmUsIGJ1dCBh ZnRlciBpbnN0YWxsd29ybGQNCj4gPiA+ID4gPiBtYWNoaW5lIHN0b3BwZWQgYm9vdGluZywgYW5k IG9uIHRoZSBzY3JlZW4gSSBzZWU6DQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gRnJlZUJTRC9hbWQ2 NCBFRkkgbG9hZGVyLCAuLi4NCj4gPiA+ID4gPiANCj4gPiA+ID4gPiAuLg0KPiA+ID4gPiA+IA0K PiA+ID4gPiA+IEJvb3RPcmRlcjogLi4uLg0KPiA+ID4gPiA+IA0KPiA+ID4gPiA+IEFuZCB0aGVu IGl0IGdldHMgc3R1Y2sgYW5kIG5vdGhpbmcgaGFwcGVucy4NCj4gPiA+ID4gPiANCj4gPiA+ID4g PiBBcyBJIGFscmVhZHkgaGF2ZSBhIGZyZXNoIGJhY2t1cCwgSSBkZWNpZGVkIHRoYXQgaXQnZCBi ZSBlYXNpZXIgdG8NCj4gPiA+ID4gPiBqdXN0IHJlLWluc3RhbGwgYW5kIGNvcHkgZGF0YSBiYWNr IG92ZXIgKG1heWJlIEkgbWVzc2VkIHVwIHdpdGgNCj4gPiA+ID4gPiByZXBhcnRpdGlvbmluZyku IFNvIEkndmUgZG93bmxvYWRlZCBhIGZyZXNoIHNuYXBzaG90Og0KPiA+ID4gPiA+IA0KPiA+ID4g PiA+IEZyZWVCU0QtMTIuMC1DVVJSRU5ULWFtZDY0LTIwMTgwNzI2LXIzMzY3MzktbWVtc3RpY2su aW1nDQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gQW5kIHJlLWluc3RhbGxlZC4gSW4gdGhlIGluc3Rh bGxlciBJIGNob29zZSBhbGwgdGhlIHNhbWUgc2V0dGluZ3MgdGhhdA0KPiA+ID4gPiA+IHdlcmUg YmVmb3JlOiBVRUZJICsgR1BULCBkZWZhdWx0IHBhcnRpdGlvbiBzY2hlbWUgaXQgc3VnZ2VzdGVk IChlZmkNCj4gPiA+ID4gPiBmb2xsb3dlZCBieSBmcmVlYnNkLXVmcyBmb2xsb3dlZCBieSBmcmVl YnNkLXN3YXApLCBqdXN0IGluY3JlYXNlZCB0aGUNCj4gPiA+ID4gPiBzd2FwIHNpemUuDQo+ID4g PiA+ID4gDQo+ID4gPiA+ID4gQW5kIHRoZSBuZXdseSBpbnN0YWxsZWQgc3lzdGVtIHdvbid0IGJv b3QganVzdCBsaWtlIGEgcHJldmlvdXMgb25lOg0KPiA+ID4gPiA+IA0KPiA+ID4gPiA+IGh0dHBz Oi8vcGVvcGxlLmZyZWVic2Qub3JnL35ub3ZlbC9taXNjL2ZyZWVic2RfZWZpX2xvb2t1cC5qcGcN Cj4gPiA+ID4gPiANCj4gPiA+ID4gPiBJcyB0aGVyZSBhIHdheSB0byByZWNvdmVyIHRoaXM/DQo+ ID4gPiA+ID4gDQo+ID4gPiA+ID4gUm9tYW4gQm9nb3JvZHNraXkgICAgDQo+ID4gPiA+IA0KPiA+ ID4gPiBKdXN0IGN1cmlvdXM6DQo+ID4gPiA+IA0KPiA+ID4gPiBXaGVuIEkgaW5zdGFsbGVkIEZy ZWVCU0QgbGFzdCB0aW1lIGZyb20gdGhlIHJlY2VudCAoMjAxOC0wNy0yNikgVVNCIGZsYXNoIGRy aXZlDQo+ID4gPiA+IG9uIGEgU1NELCB0aGUgZnJlZWJzZC1zd2FwIHBhcnRpdGlvbiBmb2xsb3dl ZCBpbW1lZGlhdGVseSBhZnRlciB0aGUgRVNQIGFuZC9vcg0KPiA+ID4gPiBmcmVlYnNkLWJvb3Qg R1BUIGxvYWRlciBwYXJ0aXRpb24uIEJ1dCBpbiBtb3N0IGNhc2VzIEkgdXNlZCB0byB1c2UgWkZT IGZvcg0KPiA+ID4gPiB0ZXN0aW5nLiAgICANCj4gPiA+IA0KPiA+ID4gV2hlbiBJIHJlaW5zdGFs bGVkIGl0IHllc3RlcmRheSBmcm9tIC1DVVJSRU5UIHNuYXBzaG90IG1lbnRpb25lZCBhYm92ZSwN Cj4gPiA+IGluIGd1aWRlZCBtb2RlIGl0IHN1Z2dlc3RlZCBhIHNpbWlsYXIgcGFydGl0aW9uaW5n IHNjaGVtYSB0aGF0IEkgdXNlOg0KPiA+ID4gICANCj4gPiA+ID0+ICAgICAgICA0MCAgMTk1MzUy NTA4OCAgYWRhMCAgR1BUICAoOTMyRykgICAgDQo+ID4gPiAgICAgICAgICAgNDAgICAgICA0MDk2 MDAgICAgIDEgIGVmaSAgKDIwME0pDQo+ID4gPiAgICAgICA0MDk2NDAgIDE4MDM1NTA3MjAgICAg IDIgIGZyZWVic2QtdWZzICAoODYwRykNCj4gPiA+ICAgMTgwMzk2MDM2MCAgIDE0ODg5Nzc5MiAg ICAgMyAgZnJlZWJzZC1zd2FwICAoNzFHKQ0KPiA+ID4gICAxOTUyODU4MTUyICAgICAgNjY2OTc2 ICAgICAgICAtIGZyZWUgLSAgKDMyNk0pDQo+ID4gPiANCj4gPiA+IFRoZSBvbmx5IGRpZmZlcmVu Y2UgaXQgdGhhdCB0aGUgZnJlZWJzZC1zd2FwIHNpemUgd2FzIDMuNUcgKGFuZA0KPiA+ID4gdGhl cmVmb3JlLCBmcmVlYnNkLXVmcyBpcyBsYXJnZSksIHRoZSBvcmRlciB3YXMgdGhlIHNhbWUuDQo+ ID4gPiAgIA0KPiA+ID4gPiBTaW5jZSBJIGhhZCBteSBVRUZJIGFkdmVudHVyZSBvZiBteSBvd24g dGhlc2UgZGF5cyBhbmQgcmVjZWl2ZWQgdmFsdWFibGUgaGludHMNCj4gPiA+ID4gZnJvbSB0aGUg ZGV2ZWxvcG1lbnQvbWFpbnRlbmFuY2UgdGVhbSBvbiBzb21lIFVFRkkgYXNwZWN0cywgaXQgd291 bGQgYmUgb2YNCj4gPiA+ID4gaW50ZXJlc3QgdG8ga25vdyB5b3VyIHJlY2VudCBoYXJkd2FyZSBh bmQsIG1vcmUgaW1wb3J0YW50bHkgc2luY2UgSSBzZWUgdGhlIGJvb3QNCj4gPiA+ID4gb3JkZXIg cHJlc2VudGVkIGluIHlvdSBzY3JlZW5zaG90LCBhIGR1bXAgb2YgdGhlIGVmaSB2YXJpYWJsZSBz ZXR0aW5ncy4gSnVzdCBmb3INCj4gPiA+ID4gY3VyaW9zaXR5LiBGb3IgdGhhdCwgeW91IGhhdmUg dG8gYm9vdCB0aGUgcmVjZW50IFVTQiBmbGFzaCBkcml2ZSBpbWFnZSB3aXRoDQo+ID4gPiA+IFVF Rkktb25seSwgdGhlbiBsb2dvbiBhcyByb290IGFuZCBwZXJmb3JtDQo+ID4gPiA+IA0KPiA+ID4g PiBrbGRsb2FkIGVmaXJ0DQo+ID4gPiA+IA0KPiA+ID4gPiBhbmQgdGhlbiBpc3N1ZSANCj4gPiA+ ID4gDQo+ID4gPiA+ICMgZWZpYm9vdG1nciAtdg0KPiA+ID4gPiANCj4gPiA+ID4gSW4gbXkgY2Fz ZSwgaXQgbG9va3MgbGlrZQ0KPiA+ID4gPiANCj4gPiA+ID4gWy4uLl0NCj4gPiA+ID4gW29oYXJ0 bWFubl06IHN1ZG8gZWZpYm9vdG1nciAtdg0KPiA+ID4gPiBCb290Q3VycmVudDogMDAwMQ0KPiA+ ID4gPiBUaW1lb3V0ICAgIDogMyBzZWNvbmRzDQo+ID4gPiA+IEJvb3RPcmRlciAgOiAwMDAxLCAw MDAyLCAwMDAzLCAwMDA0LCAwMDA1LCAwMDAwDQo+ID4gPiA+ICtCb290MDAwMSogRnJlZUJTRC0x MiBcDQo+ID4gPiA+ICAgIEhEKDEsR1BULGUxNDYwOTQxLWUyZTktMTFlNS1iOTEzLWQwNTA5OTA3 ZWYwOSwweDI4LDB4NjQwKS9GaWxlKFxlZmlcYm9vdFxCT09UeDY0LmVmaSkNCj4gPiA+ID4gXCBh ZGEwcDE6L2VmaS9ib290L0JPT1R4NjQuZWZpIChudWxsKSANCj4gPiA+ID4gIEJvb3QwMDAyKiBI YXJkIERyaXZlICBCQlMoSEQsLDB4MCkNCj4gPiA+ID4gIEJvb3QwMDAzKiBDRC9EVkQgRHJpdmUg IEJCUyhDRFJPTSwsMHgwKQ0KPiA+ID4gPiAgQm9vdDAwMDQqIFVTQiAgQkJTKFVTQiwsMHgwKQ0K PiA+ID4gPiAgQm9vdDAwMDUqIE5ldHdvcmsgQ2FyZCAgQkJTKE5ldHdvcmssLDB4MCkNCj4gPiA+ ID4gIEJvb3QwMDAwICBGcmVlQlNELTEyDQo+ID4gPiA+IEhEKDEsR1BULGUxNDYwOTQxLWUyZTkt MTFlNS1iOTEzLWQwNTA5OTA3ZWYwOSwweDI4LDB4NjQwKS9GaWxlKFxlZmlcYm9vdFxCT09UeDY0 LmVmaSkNCj4gPiA+ID4gYWRhMHAxOi9lZmkvYm9vdC9CT09UeDY0LmVmaSAobnVsbCkNCj4gPiA+ ID4gDQo+ID4gPiA+IA0KPiA+ID4gPiBVbnJlZmVyZW5jZWQgVmFyaWFibGVzOg0KPiA+ID4gPiBb Li4uXQ0KPiA+ID4gPiANCj4gPiA+ID4gQm9vdDAwMDAgaXMgdGhlIHNhbWUgYXMgQm9vdDAwMDEg YW5kIGlzIGRlZmluZWQgZHVlIHRvIHNvbWUgImJ1ZyIgV2FybmVyIExvc2ggaGFzDQo+ID4gPiA+ IGZpeGVkIHJlY2VudGx5LCBpdCBpcyB0aGUgc2FtZSBhcyBCb290MDAwMSAgICANCj4gPiA+IA0K PiA+ID4gTW90aGVyYm9hcmQgaXMgKGZyb20gZG1pZGVjb2RlKToNCj4gPiA+IA0KPiA+ID4gSGFu ZGxlIDB4MDAwMCwgRE1JIHR5cGUgMCwgMjQgYnl0ZXMNCj4gPiA+IEJJT1MgSW5mb3JtYXRpb24N Cj4gPiA+ICAgICAgICAgVmVuZG9yOiBBbWVyaWNhbiBNZWdhdHJlbmRzIEluYy4NCj4gPiA+ICAg ICAgICAgVmVyc2lvbjogMDgwNg0KPiA+ID4gICAgICAgICBSZWxlYXNlIERhdGU6IDAyLzIwLzIw MTQNCj4gPiA+ICAgICAgICAgQWRkcmVzczogMHhGMDAwMA0KPiA+ID4gICAgICAgICBSdW50aW1l IFNpemU6IDY0IGtCDQo+ID4gPiAgICAgICAgIFJPTSBTaXplOiAxNiBNQg0KPiA+ID4gICAgICAg ICBDaGFyYWN0ZXJpc3RpY3M6DQo+ID4gPiAgICAgICAgICAgICAgICAgUENJIGlzIHN1cHBvcnRl ZA0KPiA+ID4gICAgICAgICAgICAgICAgIEFQTSBpcyBzdXBwb3J0ZWQNCj4gPiA+ICAgICAgICAg ICAgICAgICBCSU9TIGlzIHVwZ3JhZGVhYmxlDQo+ID4gPiAgICAgICAgICAgICAgICAgQklPUyBz aGFkb3dpbmcgaXMgYWxsb3dlZA0KPiA+ID4gICAgICAgICAgICAgICAgIEJvb3QgZnJvbSBDRCBp cyBzdXBwb3J0ZWQNCj4gPiA+ICAgICAgICAgICAgICAgICBTZWxlY3RhYmxlIGJvb3QgaXMgc3Vw cG9ydGVkDQo+ID4gPiAgICAgICAgICAgICAgICAgQklPUyBST00gaXMgc29ja2V0ZWQNCj4gPiA+ ICAgICAgICAgICAgICAgICBFREQgaXMgc3VwcG9ydGVkDQo+ID4gPiAgICAgICAgICAgICAgICAg NS4yNSIvMS4yIE1CIGZsb3BweSBzZXJ2aWNlcyBhcmUgc3VwcG9ydGVkIChpbnQgMTNoKQ0KPiA+ ID4gICAgICAgICAgICAgICAgIDMuNSIvNzIwIGtCIGZsb3BweSBzZXJ2aWNlcyBhcmUgc3VwcG9y dGVkIChpbnQgMTNoKQ0KPiA+ID4gICAgICAgICAgICAgICAgIDMuNSIvMi44OCBNQiBmbG9wcHkg c2VydmljZXMgYXJlIHN1cHBvcnRlZCAoaW50IDEzaCkNCj4gPiA+ICAgICAgICAgICAgICAgICBQ cmludCBzY3JlZW4gc2VydmljZSBpcyBzdXBwb3J0ZWQgKGludCA1aCkNCj4gPiA+ICAgICAgICAg ICAgICAgICA4MDQyIGtleWJvYXJkIHNlcnZpY2VzIGFyZSBzdXBwb3J0ZWQgKGludCA5aCkNCj4g PiA+ICAgICAgICAgICAgICAgICBTZXJpYWwgc2VydmljZXMgYXJlIHN1cHBvcnRlZCAoaW50IDE0 aCkNCj4gPiA+ICAgICAgICAgICAgICAgICBQcmludGVyIHNlcnZpY2VzIGFyZSBzdXBwb3J0ZWQg KGludCAxN2gpDQo+ID4gPiAgICAgICAgICAgICAgICAgQUNQSSBpcyBzdXBwb3J0ZWQNCj4gPiA+ ICAgICAgICAgICAgICAgICBVU0IgbGVnYWN5IGlzIHN1cHBvcnRlZA0KPiA+ID4gICAgICAgICAg ICAgICAgIEJJT1MgYm9vdCBzcGVjaWZpY2F0aW9uIGlzIHN1cHBvcnRlZA0KPiA+ID4gICAgICAg ICAgICAgICAgIFRhcmdldGVkIGNvbnRlbnQgZGlzdHJpYnV0aW9uIGlzIHN1cHBvcnRlZA0KPiA+ ID4gICAgICAgICAgICAgICAgIFVFRkkgaXMgc3VwcG9ydGVkDQo+ID4gPiAgICAgICAgIEJJT1Mg UmV2aXNpb246IDQuNg0KPiA+ID4gDQo+ID4gPiBIYW5kbGUgMHgwMDAyLCBETUkgdHlwZSAyLCAx NSBieXRlcw0KPiA+ID4gQmFzZSBCb2FyZCBJbmZvcm1hdGlvbg0KPiA+ID4gICAgICAgICBNYW51 ZmFjdHVyZXI6IEFTVVNUZUsgQ09NUFVURVIgSU5DLg0KPiA+ID4gICAgICAgICBQcm9kdWN0IE5h bWU6IEI4NU0tRQ0KPiA+ID4gICAgICAgICBWZXJzaW9uOiBSZXYgWC4weA0KPiA+ID4gICAgICAg ICBTZXJpYWwgTnVtYmVyOiAxNDA1MjYyMzg0MDU1ODUNCj4gPiA+ICAgICAgICAgQXNzZXQgVGFn OiBUbyBiZSBmaWxsZWQgYnkNCj4gPiA+IE8uRS5NLg0KPiA+ID4gRmVhdHVyZXM6IEJvYXJkIGlz IGEgaG9zdGluZw0KPiA+ID4gYm9hcmQgQm9hcmQgaXMNCj4gPiA+IHJlcGxhY2VhYmxlIExvY2F0 aW9uIEluIENoYXNzaXM6IFRvIGJlIGZpbGxlZCBieQ0KPiA+ID4gTy5FLk0uIENoYXNzaXMgSGFu ZGxlOg0KPiA+ID4gMHgwMDAzIFR5cGU6DQo+ID4gPiBNb3RoZXJib2FyZCBDb250YWluZWQgT2Jq ZWN0IEhhbmRsZXM6IDANCj4gPiA+IA0KPiA+ID4gJ2VmaWJvb3RtZ3IgLXYnIG91dHB1dDoNCj4g PiA+IA0KPiA+ID4gQm9vdEN1cnJlbnQ6IDAwMDQNCj4gPiA+IFRpbWVvdXQgICAgOiAxIHNlY29u ZHMNCj4gPiA+IEJvb3RPcmRlciAgOiAwMDAxLCAwMDAyLCAwMDAzLCAwMDA0DQo+ID4gPiAgQm9v dDAwMDEqIEhhcmQgRHJpdmUgIEJCUyhIRCwsMHgwKQ0KPiA+ID4gIEJvb3QwMDAyKiBOZXR3b3Jr IENhcmQgIEJCUyhOZXR3b3JrLCwweDApDQo+ID4gPiAgQm9vdDAwMDMqIFVFRkkgT1MNCj4gPiA+ IEhEKDEsR1BULDc4NDU5ZWMwLTkzMDMtMTFlOC05N2U2LTk4ZGVkMDAwOWIxYywweDI4LDB4NjQw MDApL0ZpbGUoXEVGSVxCT09UXEJPT1RYNjQuRUZJKQ0KPiA+ID4gYWRhMHAxOi9FRkkvQk9PVC9C T09UWDY0LkVGSSAobnVsbCkNCj4gPiA+IFBhdGgoMCwwLGFlODRiMTFkZjU4MTcyNGU4NTQ0MmJh YjBjMmNhYzVjMDIwMDAwMDIwMDAwKSArQm9vdDAwMDQqIFVFRkk6IFNhbkRpc2sNCj4gPiA+IFBj aVJvb3QoMHgwKS9QY2koMHgxZCwweDApL1VTQigweDEsMHgwKS9VU0IoMHg0LDB4MCkvSEQoMSxN QlIsMHg5MDkwOTA5MCwweDEsMHg2NDApDQo+ID4gPiBWZW5IdygyZDY0NDdlZi0zYmM5LTQxYTAt YWMxOS00ZDUxZDAxYjRjZTYsNTMwMDYxMDA2ZTAwNDQwMDY5MDA3MzAwNmIwMDAwMDApDQo+ID4g PiANCj4gPiA+IA0KPiA+ID4gVW5yZWZlcmVuY2VkIFZhcmlhYmxlczoNCj4gPiA+IA0KPiA+ID4g ICANCj4gPiA+ID4gS2luZCByZWdhcmRzLA0KPiA+ID4gPiANCj4gPiA+ID4gb2gNCj4gPiA+ID4g DQo+ID4gPiA+IC0gLS0gDQo+ID4gPiA+IE8uIEhhcnRtYW5uDQo+ID4gPiA+IA0KPiA+ID4gPiBJ Y2ggd2lkZXJzcHJlY2hlIGRlciBOdXR6dW5nIG9kZXIg3GJlcm1pdHRsdW5nIG1laW5lciBEYXRl biBm/HINCj4gPiA+ID4gV2VyYmV6d2Vja2Ugb2RlciBm/HIgZGllIE1hcmt0LSBvZGVyIE1laW51 bmdzZm9yc2NodW5nICinIDI4IEFicy4gNCBCRFNHKS4NCj4gPiA+ID4gLS0tLS1CRUdJTiBQR1Ag U0lHTkFUVVJFLS0tLS0NCj4gPiA+ID4gDQo+ID4gPiA+IGlMVUVBUk1LQUIwV0lRUVpWWk16QXR3 QzJULzg2VHJTNTI4ZnlGaFlsQVVDVzExd2ZnQUtDUkRTNTI4ZnlGaFkNCj4gPiA+ID4gbE1vakFm OTI5VVN4MXg3SS9zU0dMdEVXS084cm05SVhmMUpFcFE3R1NkSTZZSGlkMzY0eDdmYnJVQmhEWll1 VA0KPiA+ID4gPiBKVmFuWTU3TGkyb0xPWG9nSHRNdzZlRFV5RCthQWY5R1RFMzBMVU5SaG1jSjdl bDYyVndwbTBvVUJHMmFzNTJpDQo+ID4gPiA+ICt2NThFWjljMjB5S1FLdVh0NDQ2ZGhiSUx5T0RE UEttYzl5a0F2bkUwVHRNaVRIazZ2Um4NCj4gPiA+ID4gPU03dmkNCj4gPiA+ID4gLS0tLS1FTkQg UEdQIFNJR05BVFVSRS0tLS0tICAgIA0KPiA+ID4gDQo+ID4gPiBSb21hbiBCb2dvcm9kc2tpeSAg DQo+ID4gDQo+ID4gVGhlIG9yZGVyIG9mIHRoZSBwYXJ0aXRpb25zIHdhcyBzaW1wbHkgYW4gb2Jz ZXJ2YXRpb24gYW5kIGZyb20gdGhlICJvbGQgZGF5cyIgd2l0aA0KPiA+IEhERCBhcyBtYXNzIHN0 b3JhZ2UvYm9vdCBzdG9yYWdlIHdpdGggcm90YXRpbmcgcGxhdHRlcnMgaXQgd2FzIHNvbWUgc29y dCBvZiBpbXBvcnRhbnQNCj4gPiBmb3IgdGhlIGFjY2VzcyBsYXRlbmN5IHdoZXJlIHRvIHBvc2l0 aW9uIHRoZSBzd2FwIHBhcnRpdGlvbi4gV2l0aCBOQU5EIGZsYXNoIGJhc2VkDQo+ID4gU1NEIHRo aXMgYmVjYW1lIG9ic29sZXRlIC0gc28sIHBsZWFzZSBkb24ndCBiZSBib3RoZXJlZCBhYm91dCB0 aGF0Lg0KPiA+IA0KPiA+IC0gRnJvbSBteSAobm9uLWV4cGVydCkgcG9pbnQgb2YgdmlldywgeW91 IFVFRkkgdmFyaWFibGVzIGxvb2sgIm5vcm1hbCIgKGFjY29yZGluZyB0bw0KPiA+IHdoYXQgSSBz ZWUgb24gbXkgYm94ZXMgYXQgaG9tZSksIGJ1dCBJIHdhcyB3b25kZXJpbmcgYWJvdXQgdGhlICJh Z2VkIiBmaXJtd2FyZSBvZiB5b3UNCj4gPiBtYWluYm9hcmQuIENoZWNraW5nIG91dCBhdCBBU1VT JyB3ZWJzaXRlL3N1cHBvcnQsIHRoZXkgY2xhaW0gdGhleSBoYXZlIGEgbW9yZSByZWNlbnQNCj4g PiBmaXJtYXJlIGZyb20gMjAxOCEgVGhpcyB3b3VsZCBiZSBvbiBwYXIgd2l0aCB0aGUgU3BlY3Ry ZS9NZWx0ZG93biBtaXRpZ2F0aW9uIHByb21pc2VzDQo+ID4gbWFkZSBieSBtb3N0IHZhbHVhYmxl L3JlbGlhYmxlIG1haW5ib2FyZCB2ZW5kb3JzIGFuZCBJbnRlbDoNCj4gPiANCj4gPiBodHRwczov L3d3dy5hc3VzLmNvbS9Nb3RoZXJib2FyZHMvQjg1TUUvSGVscERlc2tfQklPUy8NCj4gPiANCj4g PiAgVmVyc2lvbiAzNjAyIDIwMTgvMDUvMjUgNy4yOSBNQnl0ZSBCODVNLUUgQklPUyAzNjAyDQo+ ID4gDQo+ID4gU2luY2UgZG1pZGVjb2RlIHJlcG9ydHMgb24gbXkgQVNSb2NrIGNyYXAgbWFpbmJv YXJkIGFsc28NCj4gPiANCj4gPiBCSU9TIFJldmlzaW9uOiA0LjYNCj4gPiANCj4gPiBJIGd1ZXNz IHRoaXMgb25lIGlzIGZha2Ugb3Igc29tZSAiZGVmYXVsdCIgZnJvbSB0aGUgZG1pZGVjb2RlIHBy b2dyYW0gbm90IGlkZW50aWZ5aW5nDQo+ID4gdGhlIGNvcnJlY3QgcmV2aXNpb24gLSBvciBpdCdz IGFub3RoZXIgc2VtYW50aWMgbm90IGtub3duIHRvIG1lLg0KPiA+IA0KPiA+IEJ1dCBteSBkbWlk ZWNvZGUgbG9va3MgbGlrZSB0aGlzLCB3aXRoIHRoZSBsYXRlc3QgQkVUQSBBU3JvY2sgcHJvdmlk ZXMgZm9yIHRoaXMgbG9uZw0KPiA+IHRpbWUgYWdvIGRpc2NvbnRpbnVlZCBaNzcgUHJvNC1ib2Fy ZDogDQo+ID4gDQo+ID4gWy4uLl0NCj4gPiANCj4gPiAjIGRtaWRlY29kZSAzLjENCj4gPiAjIFNN QklPUyBlbnRyeSBwb2ludCBhdCAweDAwMGYwNGMwDQo+ID4gRm91bmQgU01CSU9TIGVudHJ5IHBv aW50IGluIEVGSSwgcmVhZGluZyB0YWJsZSBmcm9tIC9kZXYvbWVtLg0KPiA+IFNNQklPUyAyLjcg cHJlc2VudC4NCj4gPiAyNiBzdHJ1Y3R1cmVzIG9jY3VweWluZyAxNTIzIGJ5dGVzLg0KPiA+IFRh YmxlIGF0IDB4MDAwRUU3RjAuDQo+ID4gDQo+ID4gSGFuZGxlIDB4MDAwMCwgRE1JIHR5cGUgMCwg MjQgYnl0ZXMNCj4gPiBCSU9TIEluZm9ybWF0aW9uDQo+ID4gICAgICAgICBWZW5kb3I6IEFtZXJp Y2FuIE1lZ2F0cmVuZHMgSW5jLg0KPiA+ICAgICAgICAgVmVyc2lvbjogUDIuMDANCj4gPiAgICAg ICAgIFJlbGVhc2UgRGF0ZTogMDMvMTMvMjAxOA0KPiA+ICAgICAgICAgQWRkcmVzczogMHhGMDAw MA0KPiA+ICAgICAgICAgUnVudGltZSBTaXplOiA2NCBrQg0KPiA+ICAgICAgICAgUk9NIFNpemU6 IDgxOTIga0INCj4gPiAgICAgICAgIENoYXJhY3RlcmlzdGljczoNCj4gPiAgICAgICAgICAgICAg ICAgUENJIGlzIHN1cHBvcnRlZA0KPiA+ICAgICAgICAgICAgICAgICBCSU9TIGlzIHVwZ3JhZGVh YmxlDQo+ID4gICAgICAgICAgICAgICAgIEJJT1Mgc2hhZG93aW5nIGlzIGFsbG93ZWQNCj4gPiAg ICAgICAgICAgICAgICAgQm9vdCBmcm9tIENEIGlzIHN1cHBvcnRlZA0KPiA+ICAgICAgICAgICAg ICAgICBTZWxlY3RhYmxlIGJvb3QgaXMgc3VwcG9ydGVkDQo+ID4gICAgICAgICAgICAgICAgIEJJ T1MgUk9NIGlzIHNvY2tldGVkDQo+ID4gICAgICAgICAgICAgICAgIEVERCBpcyBzdXBwb3J0ZWQN Cj4gPiAgICAgICAgICAgICAgICAgNS4yNSIvMS4yIE1CIGZsb3BweSBzZXJ2aWNlcyBhcmUgc3Vw cG9ydGVkIChpbnQgMTNoKQ0KPiA+ICAgICAgICAgICAgICAgICAzLjUiLzcyMCBrQiBmbG9wcHkg c2VydmljZXMgYXJlIHN1cHBvcnRlZCAoaW50IDEzaCkNCj4gPiAgICAgICAgICAgICAgICAgMy41 Ii8yLjg4IE1CIGZsb3BweSBzZXJ2aWNlcyBhcmUgc3VwcG9ydGVkIChpbnQgMTNoKQ0KPiA+ICAg ICAgICAgICAgICAgICBQcmludCBzY3JlZW4gc2VydmljZSBpcyBzdXBwb3J0ZWQgKGludCA1aCkN Cj4gPiAgICAgICAgICAgICAgICAgODA0MiBrZXlib2FyZCBzZXJ2aWNlcyBhcmUgc3VwcG9ydGVk IChpbnQgOWgpDQo+ID4gICAgICAgICAgICAgICAgIFNlcmlhbCBzZXJ2aWNlcyBhcmUgc3VwcG9y dGVkIChpbnQgMTRoKQ0KPiA+ICAgICAgICAgICAgICAgICBQcmludGVyIHNlcnZpY2VzIGFyZSBz dXBwb3J0ZWQgKGludCAxN2gpDQo+ID4gICAgICAgICAgICAgICAgIEFDUEkgaXMgc3VwcG9ydGVk DQo+ID4gICAgICAgICAgICAgICAgIFVTQiBsZWdhY3kgaXMgc3VwcG9ydGVkDQo+ID4gICAgICAg ICAgICAgICAgIEJJT1MgYm9vdCBzcGVjaWZpY2F0aW9uIGlzIHN1cHBvcnRlZA0KPiA+ICAgICAg ICAgICAgICAgICBUYXJnZXRlZCBjb250ZW50IGRpc3RyaWJ1dGlvbiBpcyBzdXBwb3J0ZWQNCj4g PiAgICAgICAgICAgICAgICAgVUVGSSBpcyBzdXBwb3J0ZWQNCj4gPiAgICAgICAgIEJJT1MgUmV2 aXNpb246IDQuNg0KPiA+IFsuLi5dDQo+ID4gDQo+ID4gV2F0Y2ggb3V0IHRoZSBWZXJzaW9uOiBQ Mi4wMCBlbnRyeSwgd2hpY2ggaXMgaW5kZWVkIHRoZSB2ZXJzaW9uIG51bWJlciBvZiB0aGUNCj4g PiBmaXJtd2FyZS4gU28sIGluIHlvdXIgY2FzZSwgdGhlIGZpcm13YXJlIGlzIGFsc28gYSBiaXQg b3V0ZGF0ZWQsIGZyb20gMjAxNC4gSSdkDQo+ID4gdXBkYXRlIHRoZSBmaXJtd2FyZSBwcmlvciB0 byBhbnkgZnVydGhlciBhY3Rpb24gaWYgdGhlcmUgYXJlIG5vIG9ibGlnYXRpb25zIGZyb20NCj4g PiBoYXJkd2FyZSBpbmNvbXBhdGliaWxpdGllcyBzbyBmYXIgdG8gbWVldCB0aGUgbmVjY2Vzc2l0 eSBvZiBsYXRlcyBJbnRlbC9BTUQgbWljcm9jb2RlDQo+ID4gdXBkYXRlcyBhbmQvb3Igb3RoZXIg VUVGSSB2dWxuZXJhYmlsaXRpZXMgb2Ygd2hpY2ggSSBoYXZlIG5vIGFjdGl2ZSBtZW1vcmllcyBh Ym91dCwNCj4gPiBidXQgdGhleSBoaXQgbWUgMjAxNS8yMDE2IG9uIG91ciBzZXJ2ZXJzLiBUaGVy ZSBpcyBubyBndWFyYW50ZWUgdGhhdCB0aGUgZmlybXdhcmUNCj4gPiB1cGRhdGUgd2lsbCBzYWx2 YWdlIHlvdXIgcHJvYmxlbSwgYnV0IHRoYXQgbWlnaHQgYmUgd29ydGggYSBzaG90LiBBbHNvLCBB U1VTIG1lbnRpb24NCj4gPiB0byBoYXZlIHNvbHZlZCBwZXJmb3JtYW5jZSBpc3N1ZXMgd2l0aCB0 aGUgbGF0ZXN0IGZpcm13YXJlLCBwbGVhc2UgY29uc2lkZXINCj4gPiBjb25zdWx0aW5nIHRoZSBk ZXNjcmlwdGlvbiBvZiB0aGUgbGF0ZXN0IGZpcm13YXJlIHJlbGVhc2UuIA0KPiA+IA0KPiA+IEFz IHRoZSBuZXh0IHN0ZXAsIGFzIGZyb20gbXkgIm5haXZlIiBwb2ludCBvZiB2aWV3LCBJIHdvdWxk IHBlcmZvcm0gdGhlIHN0ZXBzDQo+ID4gcmVjb21tZW5kZWQgdG8gbWUgYnkgRnJlZUJTRCdzIGRl dmVsb3BlcnMgdG8gc2V0IHRoZSBVRUZJIHZhcmlhYmxlcyBhZ2FpbjoNCj4gPiANCj4gPiBCb290 IGluIFVFRkkgbW9kZSBmcm9tIHRoZSBVU0IgZmxhc2ggZGV2aWNlDQo+ID4gTG9nb24gYXMgcm9v dA0KPiA+IG1vdW50IC11dyAvDQo+ID4ga2xkbG9hZCBlZmlydA0KPiA+IG1vdW50IC10IG1zZG9z ZnMgL2Rldi9hZGEwcDEgL21udA0KPiA+IA0KPiA+IGVmaWJvb3RtZ3IgLWMgLWwgL21udC9lZmkv Ym9vdC9CT09UeDY0LmVmaSAtTCBGcmVlQlNEDQo+ID4gZWZpYm9vdG1nciAtdg0KPiA+IA0KPiA+ IExvb2sgZm9yIHRoZSAiQm9vdDAwMFgiIGVudHJ5IGxhYmVsZWQgd2l0aCAiRnJlZUJTRCIsIHRh a2UgdGhlIG51bWJlciBwb3J0aW9uIG9mIHRoZQ0KPiA+IHRoYXQgQm9vdDAwMFggdmFyaWFibGUg KDAwMFgpIGFuZCBwZXJmb3JtDQo+ID4gDQo+ID4gZWZpYm9vdG1nciAtYSAwMDBYDQo+ID4gZWZp Ym9vdG1nciAtbiAwMDBYICh0aGlzIG9uZSBpcyAiZXh0cmEiIGFuZCBjYW4gYmUgb21taXRlZCwg aXQgbWVhbnMgIm5leHQgYm9vdCIsIHNlZQ0KPiA+IG1hbnBhZ2UgZWZpYm9vdG1ncig4KSkNCj4g PiANCj4gPiBhbmQgY2hlY2sgYWdhaW4gd2l0aCANCj4gPiANCj4gPiBlZmlib290bWdyIC12DQo+ ID4gDQo+ID4gVGhlICJtYW5ldXZlciIgYWJvdmUgaXMgb25seSBpbiBjYXNlIHRoZSBzZXR0aW5n cyBvZiBVRUZJIHZhcmlhYmxlcyBoYXMgZ29uZSByb2d1ZS4NCj4gPiANCj4gPiBSZWdhcmRzLA0K PiA+IA0KPiA+IG9oICANCj4gDQo+IEkndmUgdXBkYXRlZCBCSU9TICh3aGljaCBhbG9uZSBkaWRu J3QgY2hhbmdlIGFueXRoaW5nKSBhbmQgZXhlY3V0ZWQNCj4gY29tbWFuZHMgeW91IHN1Z2dlc3Rl ZCwgYW5kIGl0IGhlbHBlZCEgVGhhbmtzIQ0KPiANCj4gTm93ICdlZmlib290bWdyIC12JyBvdXRw dXQgbG9va3MgbGlrZSB0aGlzOg0KPiANCj4gQm9vdEN1cnJlbnQ6IDAwMDANCj4gVGltZW91dCAg ICA6IDEgc2Vjb25kcw0KPiBCb290T3JkZXIgIDogMDAwMCwgMDAwNCwgMDAwNiwgMDAwMywgMDAw Nw0KPiArQm9vdDAwMDAqIEZyZWVCU0QNCj4gSEQoMSxHUFQsNzg0NTllYzAtOTMwMy0xMWU4LTk3 ZTYtOThkZWQwMDA5YjFjLDB4MjgsMHg2NDAwMCkvRmlsZShcZWZpXGJvb3RcQk9PVHg2NC5lZmkp DQo+IGFkYTBwMTovZWZpL2Jvb3QvQk9PVHg2NC5lZmkgKG51bGwpIEJvb3QwMDA0KiBIYXJkIERy aXZlICBCQlMoSEQsLDB4MCkNCj4gIEJvb3QwMDA2KiBOZXR3b3JrIENhcmQgIEJCUyhOZXR3b3Jr LCwweDApDQo+ICBCb290MDAwMyogVUVGSSBPUw0KPiBIRCgxLEdQVCw3ODQ1OWVjMC05MzAzLTEx ZTgtOTdlNi05OGRlZDAwMDliMWMsMHgyOCwweDY0MDAwKS9GaWxlKFxFRklcQk9PVFxCT09UWDY0 LkVGSSkNCj4gYWRhMHAxOi9FRkkvQk9PVC9CT09UWDY0LkVGSSAobnVsbCkNCj4gUGF0aCgwLDAs ZWY0NzY0MmRjOTNiYTA0MWFjMTk0ZDUxZDAxYjRjZTY1MjAwNjUwMDYxMDA2YzAwNzQwMDY1MDA2 YjAwMjAwMDQyMDA2ZjAwNmYwMDc0MDAyMDAwNDEwMDY3MDA2NTAwNmUwMDc0MDAwMDAwKQ0KPiBC b290MDAwNyogVUVGSTogU2FuRGlzaw0KPiBQY2lSb290KDB4MCkvUGNpKDB4MTQsMHgwKS9VU0Io MHg5LDB4MCkvSEQoMSxNQlIsMHg5MDkwOTA5MCwweDEsMHg2NDApDQo+IFZlbkh3KDJkNjQ0N2Vm LTNiYzktNDFhMC1hYzE5LTRkNTFkMDFiNGNlNiwzNDAwNDMwMDM1MDAzMzAwMzEwMDMwMDAzMDAw MzEwMDM1MDAzNDAwMzEwMDMwMDAzMTAwMzUwMDMxMDAzMDAwMzkwMDMwMDAzOTAwMzUwMDAwMDAp DQo+IA0KPiANCj4gVW5yZWZlcmVuY2VkIFZhcmlhYmxlczoNCj4gDQo+IFRoaXMgaXMgc3RyYW5n ZSwgYmVjYXVzZSB0aGUgb25seSBkaWZmZXJlbmNlIEkgc2VlIGlzIHRoYXQgQm9vdDAwMDAgaGFz DQo+IGxvd2VyY2FzZSBmaWxlbmFtZXMgKCcvZWZpL2Jvb3QvQk9PVHg2NC5lZmknIHZzDQo+ICcv RUZJL0JPT1QvQk9PVFg2NC5FRkknKS4gSSdtIHdvbmRlcmluZyBpZiB0aGF0J3MgdGhlIG9ubHkg cmVhc29uIGl0DQo+IHdhc24ndCB3b3JraW5nIGJlZm9yZT8NCj4gDQo+ID4gLSAtLSANCj4gPiBP LiBIYXJ0bWFubg0KWy4uLl0NCg0KPiANCj4gUm9tYW4gQm9nb3JvZHNraXkNCg0KSSdtIGdsYWQg dG8gYmUgb2YgaGVscC4gQnV0IGl0IHdhcyBhICJ3aWxkIGd1ZXNzIiwgbm90IGV4cGVyaWVuY2Ug b3IgZGVjZW5kIGtub3dsZWRnZS4NCk1heWJlIHRoZXJlIGlzIGFuIGlzc3VlIHdpdGggcmVjZW50 IFVFRkkvYm9vdC9zdGFuZCBpbXBsZW1lbnRhdGlvbiBzaW5jZSB0aGlzIHBvcnRpb24gb2YNCkZy ZWVCU0QgaXMgdW5kZXIgaGVhdnkgZGV2ZWxvcG1lbnQgb3IgaGFzIGJlZW4gdW5kZXIgc3VjaCAu Li4NCg0KWXB1IHNocHVsZCBjb25zaWRlciBjb250YWN0aW5nIFdhcm5lciBMb3NoIG9yIFRvb21h cyBTb29tZSAob24gdGhlIGN1cnJlbnRAIGxpc3QsIHRoZXJlDQppcyBhIHRocmVhZCBlbnRpdGVs dCAiW1VFRkldIEJvb3QgaXNzdWVzIG9uIHNvbWUgVUVGSSBpbXBsZW1lbnRhdGlvbnMiIHN0YXJ0 ZWQgYnkgbXlzZWxmDQp0YXJnZXR0aW5nIHNvbWUgd2VpcmQgRnJlZUJTRC9VRUZJIGlzc3Vlcy4g VG9vbWFzIFNvb21lIGdhdmUgbWUgdGhlIGhpbnQgd2l0aA0KZWZpYm9vdG1ncig4KSBhbmQgSSBm aWd1cmVkIG91dCBieSBsZWFybmluZyBmcm9tIHRoZSBkZWZpbml0aW9ucywgdGhhdCBvbiBzcGVj aWZpYyBVRUZJDQppbXBsZW1lbnRhdGlvbnMsIHRoZSBib290IHBhdGggIi9lZmkvYm9vdC9ib290 eDY0LmVmaSIgaXMgY29uc2lkZXJlZCB0aGUgZGVmYXVsdCBmb3INCmNoYW5nZWFibGUgbWVkaWEg KGxpa2UgVVNCIGZsYXNoIGRyaXZlcykgYW5kIG5vdCBuZWNlc3NhcnlseSB0aGUgZGVmYXVsdCBm b3IgU0FUQS9TQVMNCmRldmljZXMuICANCg0KSSBmZWx0IGZyYW5rIGFuZCBmcmVlIHRvIENDIHNv bWUgcGVvcGxlIGZvcm0gdGhlIGxpc3QsIGhvcGluZyB0aGF0IGNvdWxkIHNoZWQgbGlnaHQgb24N CnRoZSBpc3N1ZS4NCg0KS2luZCByZWdhcmRzLA0Kb2gNCg0KLSAtLSANCk8uIEhhcnRtYW5uDQoN CkljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2RlciDcYmVybWl0dGx1bmcgbWVpbmVyIERh dGVuIGb8cg0KV2VyYmV6d2Vja2Ugb2RlciBm/HIgZGllIE1hcmt0LSBvZGVyIE1laW51bmdzZm9y c2NodW5nICinIDI4IEFicy4gNCBCRFNHKS4NCi0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0t DQoNCmlMVUVBUk1LQUIwV0lRUVpWWk16QXR3QzJULzg2VHJTNTI4ZnlGaFlsQVVDVzEyMGtRQUtD UkRTNTI4ZnlGaFkNCmxJK2RBZjBVcWdsMUdrVXN0U3JISlpQRkpna1Y5MVl6alVSRmFRSHdwcTI2 a0E4VWV4N21XbnRCS05VVGp6eC8NCk1VRy9VNElVdnlJbUdFU21CWllPY1N5QXBUWE9BZjlQRFdY QldNL3p3ZnU5TDlUYm9nVnVKMVdZVE9GNGhkQjYNCmlFdmJOV1J0TlF5NmVRd0Q2K2VVQklTeEpm RytkUzhEVkF6d2tQNDYrdlUyM1I2VkkyYzgNCj1POWx4DQotLS0tLUVORCBQR1AgU0lHTkFUVVJF LS0tLS0NCg== From owner-freebsd-current@freebsd.org Sun Jul 29 12:58:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFC201056B18 for ; Sun, 29 Jul 2018 12:58:50 +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 411D18073B for ; Sun, 29 Jul 2018 12:58:50 +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:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1532869127; bh=r7BzI5XtJgcVbTnTFq+Dd1/wcrjXzmF5kg7fQxw qJhE=; b=l7lF6GQrKljN/HRduOAOPxEQ7m0fdta1U7Qzx5rO1jzQA/nUb/c/+88 LtFFTUqr/NP0rLL1wwY/LtyTId4ziUqX3uhRDE70J5WwS6ax/51jC8RyFP5G3KbK Tgwlq60H7vodHds8dhV8q6+8DegEnqjIJt33ELbN6vQ2/4pSkIZA= 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 C978D1020F for ; Sun, 29 Jul 2018 08:58:47 -0400 (EDT) To: freebsd-current From: Michael Butler Subject: console spam during mergemaster Openpgp: preference=signencrypt Message-ID: <602f48b6-9dc4-37fd-a3bf-1c6852c51c5f@protected-networks.net> Date: Sun, 29 Jul 2018 08:58:47 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 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.27 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, 29 Jul 2018 12:58:50 -0000 This started a few days ago .. no apparent ill effect but still annoying .. *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate script for target "/var/tmp/temproot/etc/periodic/daily" ignored make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/periodic/daily" defined here make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate script for target "/var/tmp/temproot/etc/periodic/daily" ignored make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/periodic/daily" defined here make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate script for target "/var/tmp/temproot/etc/periodic/monthly" ignored make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/periodic/monthly" defined here make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate script for target "/var/tmp/temproot/etc/periodic/monthly" ignored make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/periodic/monthly" defined here make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate script for target "/var/tmp/temproot/etc/pam.d" ignored make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/pam.d" defined here make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate script for target "/var/tmp/temproot/etc/pam.d" ignored imb From owner-freebsd-current@freebsd.org Sun Jul 29 13:06:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F6BF1056E14 for ; Sun, 29 Jul 2018 13:06:34 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 BF11280BB1 for ; Sun, 29 Jul 2018 13:06:33 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([2.245.38.16]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MZkv0-1fPTco0p26-00LUBf; Sun, 29 Jul 2018 15:06:20 +0200 Date: Sun, 29 Jul 2018 15:05:43 +0200 From: "O. Hartmann" To: Michael Butler Cc: freebsd-current Subject: Re: console spam during mergemaster Message-ID: <20180729150610.62936c38@thor.intern.walstatt.dynvpn.de> In-Reply-To: <602f48b6-9dc4-37fd-a3bf-1c6852c51c5f@protected-networks.net> References: <602f48b6-9dc4-37fd-a3bf-1c6852c51c5f@protected-networks.net> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:vXtbsk9WC8m8gNwaRh49Z6PBslZB0NHrHDl95lnY05jAFhfbdik 6xJzjOPzu77wlB8RJQZpsb3cD0Fyy749E7tmcRqX2Z/EFHT1gE+fKg4VJS+vtNpPwhYKu9J QpsNA19id0+rfoFzWR4xf/iVVwsfkfz4jqMU446pHJ5ARY3AiwBEZzfPeWBSJ6BKxYTPs3w NVhwMLNInxMOeiyd0GSUA== X-UI-Out-Filterresults: notjunk:1;V01:K0:mZ1vPZ3AXMM=:jNikhbx9akB7l42uwFVl6o MVaqFECuG+0KF2LFQ7cf3bQN44+7KgDE8ZBYi54O5FsfmB8CvvC/sIKPAdqDqwsu7ckrlAzGY X+RFD4m2tFGRw+gVhj0JMQxUYCqd6Z+fVPno9gBajlppFdkpRuI3H9pvuXXSWyUK1QDyqsYfU FZ4Teb/9RU/sr29F9uRAFHhPkJ8o9DjlB8WvDwBcX5h2c1P9vtszDDvP7xkvZtGWpUXg6HqAr B8F5wYm0sdKtXIeE6F3O3Tk2yLmEtF28U+hI1WERuecNupqtoV/oDnvXwo7O2ovI/LoBxKJ3I zssVDOrNTSyNXvTNvndidjM6i7BBbToq9d4BZj4L5BtM+hJYTc+FFc02SzXlKN5TxAAm/EphC 5+SygxpkGa0Tg0Tdm3VoC5Wpk5KpkKdB7yFlomeMGotszhVR22qs13aRZcbpJb1p+WEOiMoH2 8Twjzp+pxdr5JKi8s052PHhhZS0kC4lZavkUWw08UDZNCnQu6pRJFNXwjvTzd6weJiVFsGj39 TbN/WxfOvf7lVb/E+JCBCjrM54To5KiguhM+kKdbsf2vedmKN7MtfDaUJt+NG8kQlTQTZh+fk JIao/O9C8wsQH5MbFIoNrRDwzeTQptUP7yy3wy6qCpIPfFiQrmVDN0zbF2tR7LA0D6Koxt9mj Fph1yQn1jQPZRYpBk9EwgvEKKmp7s8803Zi09wbXnPmV052Ukm3zc8NQAHuzIfWzBvX9vRr+J GrkHfvr78UVlSx7wmtf6NKeDtah4Pa1aXkQd8Z/P+lB46tJEiM7nMdXVx6NrCZX+phgUkRFPR i3Q46SB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 13:06:34 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkFtIFN1 biwgMjkgSnVsIDIwMTggMDg6NTg6NDcgLTA0MDANCk1pY2hhZWwgQnV0bGVyIDxpbWJAcHJvdGVj dGVkLW5ldHdvcmtzLm5ldD4gc2NocmllYjoNCg0KPiBUaGlzIHN0YXJ0ZWQgYSBmZXcgZGF5cyBh Z28gLi4gbm8gYXBwYXJlbnQgaWxsIGVmZmVjdCBidXQgc3RpbGwgYW5ub3lpbmcgLi4NCj4gDQo+ ICoqKiBDcmVhdGluZyB0aGUgdGVtcG9yYXJ5IHJvb3QgZW52aXJvbm1lbnQgaW4gL3Zhci90bXAv dGVtcHJvb3QNCj4gICoqKiAvdmFyL3RtcC90ZW1wcm9vdCByZWFkeSBmb3IgdXNlDQo+ICAqKiog Q3JlYXRpbmcgYW5kIHBvcHVsYXRpbmcgZGlyZWN0b3J5IHN0cnVjdHVyZSBpbiAvdmFyL3RtcC90 ZW1wcm9vdA0KPiANCj4gbWFrZVs0XTogIi91c3Ivc3JjL3NoYXJlL21rL2JzZC5kaXJzLm1rIiBs aW5lIDI5OiB3YXJuaW5nOiBkdXBsaWNhdGUNCj4gc2NyaXB0IGZvciB0YXJnZXQgIi92YXIvdG1w L3RlbXByb290L2V0Yy9wZXJpb2RpYy9kYWlseSIgaWdub3JlZA0KPiBtYWtlWzRdOiAiL3Vzci9z cmMvc2hhcmUvbWsvYnNkLmRpcnMubWsiIGxpbmUgMzE6IHdhcm5pbmc6IHVzaW5nDQo+IHByZXZp b3VzIHNjcmlwdCBmb3IgIi92YXIvdG1wL3RlbXByb290L2V0Yy9wZXJpb2RpYy9kYWlseSIgZGVm aW5lZCBoZXJlDQo+IG1ha2VbNF06ICIvdXNyL3NyYy9zaGFyZS9tay9ic2QuZGlycy5tayIgbGlu ZSAzMTogd2FybmluZzogZHVwbGljYXRlDQo+IHNjcmlwdCBmb3IgdGFyZ2V0ICIvdmFyL3RtcC90 ZW1wcm9vdC9ldGMvcGVyaW9kaWMvZGFpbHkiIGlnbm9yZWQNCj4gbWFrZVs0XTogIi91c3Ivc3Jj L3NoYXJlL21rL2JzZC5kaXJzLm1rIiBsaW5lIDMxOiB3YXJuaW5nOiB1c2luZw0KPiBwcmV2aW91 cyBzY3JpcHQgZm9yICIvdmFyL3RtcC90ZW1wcm9vdC9ldGMvcGVyaW9kaWMvZGFpbHkiIGRlZmlu ZWQgaGVyZQ0KPiBtYWtlWzRdOiAiL3Vzci9zcmMvc2hhcmUvbWsvYnNkLmRpcnMubWsiIGxpbmUg Mjk6IHdhcm5pbmc6IGR1cGxpY2F0ZQ0KPiBzY3JpcHQgZm9yIHRhcmdldCAiL3Zhci90bXAvdGVt cHJvb3QvZXRjL3BlcmlvZGljL21vbnRobHkiIGlnbm9yZWQNCj4gbWFrZVs0XTogIi91c3Ivc3Jj L3NoYXJlL21rL2JzZC5kaXJzLm1rIiBsaW5lIDMxOiB3YXJuaW5nOiB1c2luZw0KPiBwcmV2aW91 cyBzY3JpcHQgZm9yICIvdmFyL3RtcC90ZW1wcm9vdC9ldGMvcGVyaW9kaWMvbW9udGhseSIgZGVm aW5lZCBoZXJlDQo+IG1ha2VbNF06ICIvdXNyL3NyYy9zaGFyZS9tay9ic2QuZGlycy5tayIgbGlu ZSAzMTogd2FybmluZzogZHVwbGljYXRlDQo+IHNjcmlwdCBmb3IgdGFyZ2V0ICIvdmFyL3RtcC90 ZW1wcm9vdC9ldGMvcGVyaW9kaWMvbW9udGhseSIgaWdub3JlZA0KPiBtYWtlWzRdOiAiL3Vzci9z cmMvc2hhcmUvbWsvYnNkLmRpcnMubWsiIGxpbmUgMzE6IHdhcm5pbmc6IHVzaW5nDQo+IHByZXZp b3VzIHNjcmlwdCBmb3IgIi92YXIvdG1wL3RlbXByb290L2V0Yy9wZXJpb2RpYy9tb250aGx5IiBk ZWZpbmVkIGhlcmUNCj4gbWFrZVszXTogIi91c3Ivc3JjL3NoYXJlL21rL2JzZC5kaXJzLm1rIiBs aW5lIDI5OiB3YXJuaW5nOiBkdXBsaWNhdGUNCj4gc2NyaXB0IGZvciB0YXJnZXQgIi92YXIvdG1w L3RlbXByb290L2V0Yy9wYW0uZCIgaWdub3JlZA0KPiBtYWtlWzNdOiAiL3Vzci9zcmMvc2hhcmUv bWsvYnNkLmRpcnMubWsiIGxpbmUgMzE6IHdhcm5pbmc6IHVzaW5nDQo+IHByZXZpb3VzIHNjcmlw dCBmb3IgIi92YXIvdG1wL3RlbXByb290L2V0Yy9wYW0uZCIgZGVmaW5lZCBoZXJlDQo+IG1ha2Vb M106ICIvdXNyL3NyYy9zaGFyZS9tay9ic2QuZGlycy5tayIgbGluZSAzMTogd2FybmluZzogZHVw bGljYXRlDQo+IHNjcmlwdCBmb3IgdGFyZ2V0ICIvdmFyL3RtcC90ZW1wcm9vdC9ldGMvcGFtLmQi IGlnbm9yZWQNCj4gDQo+IAlpbWINCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX18NCj4gZnJlZWJzZC1jdXJyZW50QGZyZWVic2Qub3JnIG1haWxpbmcgbGlz dA0KPiBodHRwczovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1j dXJyZW50DQo+IFRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLWN1cnJl bnQtdW5zdWJzY3JpYmVAZnJlZWJzZC5vcmciDQoNCm1lLCB0b28NCg0KUmVnYXJkcywNCg0Kb2gN Cg0KLSAtLSANCk8uIEhhcnRtYW5uDQoNCkljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2Rl ciDDnGJlcm1pdHRsdW5nIG1laW5lciBEYXRlbiBmw7xyDQpXZXJiZXp3ZWNrZSBvZGVyIGbDvHIg ZGllIE1hcmt0LSBvZGVyIE1laW51bmdzZm9yc2NodW5nICjCpyAyOCBBYnMuIDQgQkRTRykuDQot LS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KDQppTFVFQVJNS0FCMFdJUVFaVlpNekF0d0My VC84NlRyUzUyOGZ5RmhZbEFVQ1cxMjd3Z0FLQ1JEUzUyOGZ5RmhZDQpsREJkQWY0bUZoUm1BV1Bv dDBGWlo2Ky9aOFR1VGVqL3pyY3hUczVTMHNBUU96VEhtb0Z1NDNodWl3VUpiczZaDQo4RE1FaWsy VCt5bkpmNG9jZjErVXhBa3lOS2dtQWYwZTdhZXJLWUNxR0tnNVFDUDN6U1MzVHBkRVJueFdQVk1u DQpiL0xWYTBreUp6elUxdm54QmhqOUxOb0NyQWxJVjI3SjhKdHhOUDdkYjlDc3Z5Z2FrczcvDQo9 ZTdTVg0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQo= From owner-freebsd-current@freebsd.org Sun Jul 29 17:43:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BA96105C1DE; Sun, 29 Jul 2018 17:43:32 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBF3688B14; Sun, 29 Jul 2018 17:43:31 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id d9-v6so14005935itf.2; Sun, 29 Jul 2018 10:43:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=95+2uWkKXGvMAu6AYwp2gnoeXEoghGAMfPQM71Yv4Ro=; b=K2XDcEjYJgVgzsXm9+5vrk5k4RHpj3H+iZtJlYnxd1lg9Fqc7fA66c9xwKn4B91tOr suyjvawkHtIWuE8/YhMeVfHZRPpw4CDMkN6xeCs8Dw3JF9h0zvKZXwucl570FR6G6sp5 z11oIpCVq/T90rNbnowX/4pm5cj0aASjkNc5Fh2tI36PWOp3y17PADWW5IvxtFYkdOyM VG2lKCqTqDFGgSuvofEqnYIqjWlyba5Y2KePcVC6ihF19JGP4AEQPzxkHVpYYSUAJsOU Gxw0To+cbBpeAZICzRO0CHZEpRrBlJKQcwEW3AIQX4o7rT0dpRdDrmx48fNgWUZq1Sfu kIog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=95+2uWkKXGvMAu6AYwp2gnoeXEoghGAMfPQM71Yv4Ro=; b=RzBFw8yliVqWRwo44jzluvXHOVFlCEna525DwBwzZGM4/rC0a5bnJzj9yoz/S5dxvP J/OV91XDXJTrauzmLSaIF0eKlLxwSkmSeYt9/UlA5aMzA1nDYs0YgVqRFPcfx6IwFm3E K8qOS+WayVwmk9INzzE5MkkZIDSOBHfrIbiWpZ3Id2HVMqHJQaNIDm21d/sxenBlNEm8 fGAx03nETYmRu7pKvN6i0jcJtod0PJ1zvIh80DNqktLNycptv6zzsafA4ODSj0PMoaFF OHGjD8GKpH+i9qCo95v9exvY8A46zdxJtwgcGQpZfVFDc3dTU91OfvTmOAb1sgfgXL7O d/Lg== X-Gm-Message-State: AOUpUlEow5xjgRfaDivNo9NZu+a3FvbkSNoDPsDHOv5KT+1VXp/P7AnG i6mbwPuelceczmevulZ37H3ToSKDXomWDO6vtERvEVk8 X-Google-Smtp-Source: AAOMgpfbldCGdA885rp4r9ljOUOIprpYhbjCISrHn/aKf6gGdv+KXSOLaGHKyKZH8Vv5abcTA8/rwu7SR/I4xc4vfnc= X-Received: by 2002:a24:60d:: with SMTP id 13-v6mr12432726itv.1.1532886211164; Sun, 29 Jul 2018 10:43:31 -0700 (PDT) MIME-Version: 1.0 From: blubee blubeeme Date: Mon, 30 Jul 2018 01:43:19 +0800 Message-ID: Subject: SVN down or slow To: FreeBSD Ports , FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 17:43:32 -0000 Has anyone else noticed that svn is getting this type of error trying to run svn: svn: E000065: Error running context: No route to host From owner-freebsd-current@freebsd.org Sun Jul 29 20:36:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3997E1062982 for ; Sun, 29 Jul 2018 20:36:59 +0000 (UTC) (envelope-from Alexander@leidinger.net) 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 C0F74786B0 for ; Sun, 29 Jul 2018 20:36:58 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: by mailman.ysv.freebsd.org (Postfix) id 8522A1062981; Sun, 29 Jul 2018 20:36:58 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73A7F1062980 for ; Sun, 29 Jul 2018 20:36:58 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 09993786AF for ; Sun, 29 Jul 2018 20:36:57 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Sun, 29 Jul 2018 22:36:39 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1532896610; bh=bsAwjuU1lumbusJkmqeh468pHANg1bpkAuwV7Walvec=; h=Date:From:To:Subject; b=18xe32QX2PBGu7AjWxgufGMoNhceSaCHoJ1qhRDOlTgM5fHFykqfZVT4nkVm4UJsa AfUYRedRZ4CocMCo+w6xgR0XqyM3HE1aN0CKyPBuh8Sm/zMByMZ10yeSXwBiY8AzDd /grO789uiA0/PFOo72Jhpdldgrm+Eav9nqpmzws7Ec7PPHlKSmyjegduHgJRU9WjS8 qaqKz1z+nS+tU+/rewN6Z3A6M1weOofkVgJrVHyRfmEuHfScKB+GOk6kp1r+BQgFbg jAosoWRHKPintJ0bnwBF2+mYq3mAEu9RKU8ONPoxDeqeUywIVl24SFlzLWv/AHof8O dOwGsvumxpqxw== Message-ID: <20180729223639.Horde.j63W3h82ohqpZmVnSIRGTkv@webmail.leidinger.net> From: Alexander Leidinger To: current@freebsd.org Subject: recent changes in OS boot watchdog area? User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_tzKa79DHoMEhDR1MIF8PoXm"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 20:36:59 -0000 This message is in MIME format and has been PGP signed. --=_tzKa79DHoMEhDR1MIF8PoXm Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, settings in BIOS: - power-off system if watchdog is not taken care of 10 minutes after powe= r-on What I have with r336564 is: watchdogd is started during boot and=20=20 system=20runs fine. What I have with r336767 is: watchdogd is started but system powers=20=20 off=20after 10 minutes. What I have with r336767 + disable of OS boot watchdog in BIOS:=20=20 watchdogs=20is started during boot and system runs fine. I checked files with *watch* or *dog* in name. No recent changes. Has=20=20 anything=20changed somewhere else which may affect this? Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_tzKa79DHoMEhDR1MIF8PoXm Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbXiVXAAoJEKrxQhqFIICEQmoP/iKVVutum6R+6tvp1bwOziKK wpHU+KKfLvhoEG4Ype6kXjcqIeeHRrWpDOWiH/LVQZVJNG+0pduMAtOXgbuM5SBe OwpL30al+DsXM3/t6NEpJ64HNXWIA0e8F88kY//Ub7uhP49QCvEnfrJj/FmJ1eGh 8qhK8ie1v3OuedRjaCzSmbMHGcyox2qRpMmzIJJVHCOg4zjuzYJaycTBtYxOblis ehOn66Kjd0ABUsBOa/oGyWcyPe8vCmHljDBDWylWvuydo9vq0i483APNZrQXN0SI uSGG7CLt8UXJgj2hzYHk5Ik6EerryCjGa49QuPe0K0YHK9zvkQnNPxu67AXQoWY4 lKetbzg2EZzNVn+M90fqMjD9k3q/Sjx3+c5fHVmQSHhupC8Gr6iuYtb64wKRnvdB OU986HqVMOvsT0e2b34Q+q0qIMVouTU+yRBzEiJC4Q+DlGWVm/8/VlfTzC3X4VjD Jt22Mc13IFltqu0cV4Jx4pwEhc6jp2ErMd7mw10N3K0bncxGNTed0+SosYRLQH9o 03yjHaGettlT9n/T/MQEqKhrRX/VTrie5HMTr4snNtbe7aVMj3oYSaKiOEk1h5Ba Clv132X/YUOq37vGYDi8xvRZWs422K4i+DV0k5FQIHwxrdVYfsFc8U6Yu/3FN+IJ 8uv94OKZRL99s1YlXFV3 =MzhL -----END PGP SIGNATURE----- --=_tzKa79DHoMEhDR1MIF8PoXm-- From owner-freebsd-current@freebsd.org Sun Jul 29 22:20:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCB2410654E9; Sun, 29 Jul 2018 22:20:22 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 523D17C958; Sun, 29 Jul 2018 22:20:22 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id w6TMKKVb088480 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 29 Jul 2018 15:20:21 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132] claimed to be yv.noip.me Subject: Re: SVN down or slow To: blubee blubeeme , FreeBSD Ports , FreeBSD current References: From: Yuri Message-ID: <76d53b4e-a4dd-8001-f158-c5ff0057524a@rawbw.com> Date: Sun, 29 Jul 2018 15:20:19 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 22:20:23 -0000 On 7/29/18 10:43 AM, blubee blubeeme wrote: > Has anyone else noticed that svn is getting this type of error trying to > run svn: svn: E000065: Error running context: No route to host This is likely due to network problems, not the subversion server itself. Yuri From owner-freebsd-current@freebsd.org Sun Jul 29 23:17:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A53F1066686; Sun, 29 Jul 2018 23:17:38 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from madarka.gustik.eu (madarka.gustik.eu [176.9.62.177]) (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 B9F197E490; Sun, 29 Jul 2018 23:17:37 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from romy.j20.helspy.pw (unknown [IPv6:2a01:c844:106d:4420:df9b:a36f:cb77:f65e]) by madarka.gustik.eu (Postfix) with ESMTPSA id 6A55016A68; Mon, 30 Jul 2018 01:17:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gustik.eu; s=mail; t=1532906253; bh=/zpV/S/YRI2HA2QnC0Dpxqo7wqOgUnQT6JCQbe7jDoY=; h=Date:From:To:Subject; b=U1bKHvaGRdUxSEYhJuLZtL214wu2jktIqRGvYCiUCzdnY9oAm10/0c8sEGSOFyycP RkIh4AS50YZ/GcV4qnOPn6aru1jS7BOB6HTaJbb1XxM/33J0w4XxCv2Z3Qb8w5gSCD nVq3rn/RSHdp/gBPYXHs74Fi5NBpxLb8jXgcluFE= Date: Mon, 30 Jul 2018 01:17:32 +0200 From: Lars Schotte To: FreeBSD Ports , FreeBSD current , mandree@FreeBSD.org Subject: OpenVPN produces garbage on TAP on -current Message-ID: <20180730011732.3604d5c5@romy.j20.helspy.pw> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Jul 2018 23:17:38 -0000 Hey, is it possible that OpenVPN can not handle TAP on -current (12) any more? I tried it with Linux -> FreeBSD and FreeBSD -> FreeBSD with the same result. On the server, the pings for example arrived at unknown ethernet packets or sth. He was still trying to learn new MAC addrs. I am suspecting there a problem with how OpenVPN filled TAP device. -- Lars Schotte Mudroňova 13 92101 PieÅ¡Å¥any From owner-freebsd-current@freebsd.org Mon Jul 30 21:09:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 997DA1060FFD for ; Mon, 30 Jul 2018 21:09:02 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 F0D0E847CB for ; Mon, 30 Jul 2018 21:09:01 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf1-x12e.google.com with SMTP id v22-v6so9151663lfe.8 for ; Mon, 30 Jul 2018 14:09:01 -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=k8lM957NBvd8njvOuSHx2m32f0YHL8zZgOM1SxeBYSY=; b=YWVvu3whqoW94YdVWr9Hy5ewr/AE1eAiXF5q5k6BUB3dSMPO0wgh9OrVjdPGGar/2E 5UC5+WNAdMg73TvcLPQ6H2bTA+R6YSIHdPsIEAuy99Lfs6ljNrTUsp85w7l10sHy5vGv DouK5X0r3pUcn1jkDU4R9UQlt3kE8xetmYwtZDBZqVgJ2PQ1O9Nz+V/l5pbEltv7JrHP yzvoMg703FlyxwroyH+bDMZMMmDvDC/eJ0gy56AUCL6gZJMxb39QkJi5fJnOBzKRZagZ LUqNOaUjueW+/Smu2ETe3f1xCEpf3Vkta0N4sQRc8q9STmjpaGAp3Kdu5+XEpA2o1cVp 5fow== 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=k8lM957NBvd8njvOuSHx2m32f0YHL8zZgOM1SxeBYSY=; b=Zlu37mV5I9RtNOKCI3KZBcMGmWha/9PX3DCr3Ik01/Bx+ISzNKl9oTgQn4aSZZaEHB lH2Mhw9HsUnG8WLz8sVM++2h1+MjyjV+cXXDbmos4u6X5kqYgAjApFnZ0qxEeM61useo VN2ZMCE42pqk0j3pEo2BlpPZxuEL5g4vS+9qU3Atuu2sNjNq9B2YQWiLhp2uBxQIXJ8l But08+A6A4cgKOVpi6oCb8MkY9EC33yOjsYon9RtsY9yWskC+Lcthz8/mP29GbcFV2ww aeywESBJJ5AosAdvTdZ/KUrBHx8UhFzx4J7kk+CcPJCtaXzVtRYVUJ0lCI9wb96yXOSv Gatg== X-Gm-Message-State: AOUpUlFhYWSgXjvAObK3NT5y0Z3F+Cd89ErqHimaaw6GY90W0ZwhKI3+ cEyhxnEXkI9sDylzna6J2oZwMAsQykeBPApoOxeAkQf3 X-Google-Smtp-Source: AAOMgpe/8o9uiVdI3RjxBLT6nWBj77SBeAWapo8trj3MBpgrW+5b7Fc7SCkVBnzRRfF20NeLOV5ulX3hTDAvA80Ty3c= X-Received: by 2002:a19:8d07:: with SMTP id p7-v6mr11832329lfd.117.1532984940004; Mon, 30 Jul 2018 14:09:00 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 2002:ab3:7851:0:0:0:0:0 with HTTP; Mon, 30 Jul 2018 14:08:59 -0700 (PDT) In-Reply-To: <20180729150610.62936c38@thor.intern.walstatt.dynvpn.de> References: <602f48b6-9dc4-37fd-a3bf-1c6852c51c5f@protected-networks.net> <20180729150610.62936c38@thor.intern.walstatt.dynvpn.de> From: Alan Somers Date: Mon, 30 Jul 2018 15:08:59 -0600 X-Google-Sender-Auth: GxoEVO-VM4aerIm8niYnwT0RN2k Message-ID: Subject: Re: console spam during mergemaster To: "O. Hartmann" Cc: Michael Butler , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 30 Jul 2018 21:09:02 -0000 On Sun, Jul 29, 2018 at 7:05 AM, O. Hartmann wrote= : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Am Sun, 29 Jul 2018 08:58:47 -0400 > Michael Butler schrieb: > > > This started a few days ago .. no apparent ill effect but still annoyin= g > .. > > > > *** Creating the temporary root environment in /var/tmp/temproot > > *** /var/tmp/temproot ready for use > > *** Creating and populating directory structure in /var/tmp/temproot > > > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > > script for target "/var/tmp/temproot/etc/periodic/daily" ignored > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/periodic/daily" defined here > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > > script for target "/var/tmp/temproot/etc/periodic/daily" ignored > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/periodic/daily" defined here > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > > script for target "/var/tmp/temproot/etc/periodic/monthly" ignored > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/periodic/monthly" defined > here > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > > script for target "/var/tmp/temproot/etc/periodic/monthly" ignored > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/periodic/monthly" defined > here > > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > > script for target "/var/tmp/temproot/etc/pam.d" ignored > > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/pam.d" defined here > > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > > script for target "/var/tmp/temproot/etc/pam.d" ignored > > > > imb > > _______________________________________________ > > 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" > > me, too > > Regards, > > oh > > - -- > 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 Ab= s. 4 BDSG). > -----BEGIN PGP SIGNATURE----- > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW127wgAKCRDS528fyFhY > lDBdAf4mFhRmAWPot0FZZ6+/Z8TuTej/zrcxTs5S0sAQOzTHmoFu43huiwUJbs6Z > 8DMEik2T+ynJf4ocf1+UxAkyNKgmAf0e7aerKYCqGKg5QCP3zSS3TpdERnxWPVMn > b/LVa0kyJzzU1vnxBhj9LNoCrAlIV27J8JtxNP7db9Csvygaks7/ > =3De7SV > -----END PGP SIGNATURE----- It's caused by r336640. I've let the committer know. From owner-freebsd-current@freebsd.org Tue Jul 31 04:52:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C40A104D227; Tue, 31 Jul 2018 04:52:12 +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 0874478FB9; Tue, 31 Jul 2018 04:52:11 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lx4dh-1g3ejc3m9Z-016dqu; Tue, 31 Jul 2018 06:51:58 +0200 Date: Tue, 31 Jul 2018 06:51:50 +0200 From: "O. Hartmann" To: Mark Millard via svn-src-head Cc: Mark Millard , tuexen@FreeBSD.org, FreeBSD Current Subject: Re: svn commit: r336940 - in head/sys: netinet netinet6 [This broke ci.freebsd.org 's FreeBSD-head-mips*-build 's] Message-ID: <20180731065145.6fbc7d56@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:U1gu1N/lk9xo1/hiZipRr7lWAMYRUqxfUXlpZKwrWXaxPMcPmpw fdJFEm9PG08bh09Q9+mqO4QjqFjgNhm11qFy8wM8vDFyIYMGweYBVxaL+3q4JBzDoM97pvz fE612nwYtg78ve1Z9vbokmL+GKDvorJmCkUjkhunfnpEkaGUlmhb1gOxYuHwSkFNdrzfxq4 22X6OdhPs/gyzxrah3I9A== X-UI-Out-Filterresults: notjunk:1;V01:K0:kbHM9UQwNLI=:+9/d3DV6/4kxfR46sCYu3d Ocyqjwd9pAXbgFks9NToHBNiwL2zxsSjcn20JBmcCcZq03MMqDkGoeSlBq+pTWmiF8Ivw9IOW OoQCbenVyQ/nBm6az8MLSweBAdL3JbPw+ARiFlmXgEv5XFeZZQBKsmFiwN0Yl1oKFlq6ePIlw I7qPiqJCFEbHEWLUJj+Filj6eNGbNBYuA3Hca7hM2+pF4GzfdQVPJbvypi+DLU/23bhtvdxWl cwVnmzbDjaQn4a6uW3vSSydIFaBhf+CHtcNZKaug01cxKLCGfVb41/sljsqOYwjd2d9pkFzQi 30AuThDrsccmBSiOdYfPUdjbieUHCEDb8Ig8vYdLzZYDXcSrtSi24+zWdPKIoFCz+Iq9enl6N EOWUgJvyC8DVJz9EqI0HPqE8oamz/0owBZ+1aKGVJAWUwToFU0TsULQ1ftei0FJr5AjlKO//3 EY3ZQCQYv4VKZ3ibPVMiyAAKoOL5YbqK8om+GaE9MOLpnEYBsUF3dVkRU74I3iME4cq7inelY 0b62V2DypuXQk5wlFr0X8aKAzfhqnoWlGYKP6bc3MS6FVCWYPhxmWb/DKdmEkgoM/2z2Ig8dO nt6cbGluhwIBLiVVJfoidauPtfhbHeunA2mwlJkN9fLlQBGto9/dmT74pJL9KP5aaBlhe7cwX yDySN+LrulhpJFOjx1/oFra0OUp7gP+U3Ej8HAcL2eZNfCilFKHIHtxNPs0VdDWbOzE25SfSZ io4VBbdVEkJSNCkOrzLGDaqooh4dy11Yds/LpKRmovI7cP0686KtBuQNjWku78sYziY+I8UO5 Wl3oc/o X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 31 Jul 2018 04:52:12 -0000 On Mon, 30 Jul 2018 18:44:24 -0700 Mark Millard via svn-src-head wrote: > https://ci.freebsd.org/job/FreeBSD-head-mips-build/3577/consoleText shows: > > --- tcp_usrreq.o --- > cc1: warnings being treated as errors > /usr/src/sys/netinet/tcp_usrreq.c: In function 'tcp_usr_send': > /usr/src/sys/netinet/tcp_usrreq.c:905: warning: unused variable > 'sin' [-Wunused-variable] . . . > --- tcp_usrreq.o --- > *** [tcp_usrreq.o] Error code 1 > > make[2]: stopped in /usr/obj/usr/src/mips.mips/sys/MALTA > 1 error > > (Note: -r366935 built correctly as #3576 .) > > > > https://ci.freebsd.org/job/FreeBSD-head-mips64-build/3624/consoleText shows: > > --- tcp_usrreq.o --- > cc1: warnings being treated as errors > /usr/src/sys/netinet/tcp_usrreq.c: In function 'tcp_usr_send': > /usr/src/sys/netinet/tcp_usrreq.c:905: warning: unused variable > 'sin' [-Wunused-variable] *** [tcp_usrreq.o] Error code 1 > > make[2]: stopped in /usr/obj/usr/src/mips.mips64/sys/MALTA64 > > (Note: -r366935 built correctly as #3623 .) > > > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) This broke also AMD64 builds. Regards oh From owner-freebsd-current@freebsd.org Tue Jul 31 05:18:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41FAA104DCBE for ; Tue, 31 Jul 2018 05:18:51 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-29.consmr.mail.bf2.yahoo.com (sonic317-29.consmr.mail.bf2.yahoo.com [74.6.129.84]) (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 C5F4B7992A for ; Tue, 31 Jul 2018 05:18:50 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: sU4ZO2MVM1mcEgZix_x7pDzvsXoGYa7UsD1zAuJI31K30vsTS58.xIxaYK3_KFE m8p3k80Y4i3PR3EJzFQtmRbs2rmQnE2q0IwrStCDXll0wv94IHhrhRk05FugzD.HrdgKksyIAnmf 3_W78SMvjn0.cDSert304CLo1EVOsHpKgmeDMEPFAYBb74JfheGa2Ukj9jvLX0.DrIFM7A82Uk.P sR6qXbtPU8QPhFrMQaQakI8C6gHEqVSPcMZEUvjpKAJWYt5J0cTrhx3eFh5QC_eGjepGDyCIskmQ 0zOtf6CXC1ZGJ_jbXYjoljAUE7_s7b3GpatpfGeylmS6IPDEnoPNped9Ga1_lq_T2pvFeTtz4IU6 Bip1jkH9f2SpmBGJ4TB2nf_vA_seLx6CahCgXeqalx4AD4rnITf83RIr2Pigu5IiBcscMHVqOrxh Wo7PWG2MIaUE_7gTe_26ji7oelAeh4STZhzqCJN.yp4KrPezrW.BG_yomZ6No9VsbcApfKkTMTfx kbG6pkkwaFwgNUkmnuTWwKdFQ7q2ug4ZqsUrQ4ifAxpIgjrdJNT2qYSu.pGFRGGdtXr0mzBxcbEO GWlsd5INZJMbDWpN7hAIBxoXf0SOvpnwMeFLtd4cjhPrzUZxLdKZbaLgcF5bQCggLpip0Z8dV9WI dxboXv68qqdz8dcbM19_oExxsog25w7IEPgalgUmwfnksBvjpx4r72AKvlozBNJFjjdQU.QjmbqG lerD597Uijx0U4g.9.GWsCDfvI_kONkrqhYHwa7BUYU8WqOYQQK7ruMMSEt3jbTXF986TlBptGam OidMKQWKQUsXb.DU1ek39Gc8XHqsF8c8ELCIoazcHaC_FmTuJiCtEFE5xeQ_28CS66FwrcfKhYCv 8hbOGNlEw2wp3EY3Ty316MtluAffDlCLv63m.r_HqiVrhviUOGtmTW318VckaCEsNV6xJGYp3yJ0 cSKim7bECSLXwc4q1fE5eNssSmPynDa2RfIizeIfaBmhNo7oVoVHODn3U3sKIPRE3.zQEWUl7wSo IdDhbhm7e.g-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.bf2.yahoo.com with HTTP; Tue, 31 Jul 2018 05:18:50 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp425.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 9ef6618dee7b706436cbd8dfd35801ed; Tue, 31 Jul 2018 05:18:47 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: svn commit: r336940 - in head/sys: netinet netinet6 [This broke ci.freebsd.org 's FreeBSD-head-mips*-build 's] From: Mark Millard In-Reply-To: Date: Mon, 30 Jul 2018 22:18:45 -0700 Cc: tuexen@FreeBSD.org, FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180731065145.6fbc7d56@freyja.zeit4.iv.bundesimmobilien.de> To: "O. Hartmann" X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 31 Jul 2018 05:18:51 -0000 [Just a resend from the correct E-mail account.] On 2018-Jul-30, at 9:51 PM, O. Hartmann = wrote: > On Mon, 30 Jul 2018 18:44:24 -0700 > Mark Millard via svn-src-head wrote: >=20 >> https://ci.freebsd.org/job/FreeBSD-head-mips-build/3577/consoleText = shows: >>=20 >> --- tcp_usrreq.o --- >> cc1: warnings being treated as errors >> /usr/src/sys/netinet/tcp_usrreq.c: In function 'tcp_usr_send': >> /usr/src/sys/netinet/tcp_usrreq.c:905: warning: unused variable >> 'sin' [-Wunused-variable] . . . >> --- tcp_usrreq.o --- >> *** [tcp_usrreq.o] Error code 1 >>=20 >> make[2]: stopped in /usr/obj/usr/src/mips.mips/sys/MALTA >> 1 error >>=20 >> (Note: -r366935 built correctly as #3576 .) >>=20 >>=20 >>=20 >> https://ci.freebsd.org/job/FreeBSD-head-mips64-build/3624/consoleText = shows: >>=20 >> --- tcp_usrreq.o --- >> cc1: warnings being treated as errors >> /usr/src/sys/netinet/tcp_usrreq.c: In function 'tcp_usr_send': >> /usr/src/sys/netinet/tcp_usrreq.c:905: warning: unused variable >> 'sin' [-Wunused-variable] *** [tcp_usrreq.o] Error code 1 >>=20 >> make[2]: stopped in /usr/obj/usr/src/mips.mips64/sys/MALTA64 >>=20 >> (Note: -r366935 built correctly as #3623 .) >>=20 > . . . > This broke also AMD64 builds. >=20 FreeBSD-head-amd64-build 's were not broken: #9676 of -r336933 (before) and #9677 of -r336943 (after) both built just fine according to: https://ci.freebsd.org/job/FreeBSD-head-amd64-build/ =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Tue Jul 31 06:28:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B24D104F9E5; Tue, 31 Jul 2018 06:28:08 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D28247BD3F; Tue, 31 Jul 2018 06:28:07 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.131] (p57BB496B.dip0.t-ipconnect.de [87.187.73.107]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 59A0072106C28; Tue, 31 Jul 2018 08:28:04 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: svn commit: r336940 - in head/sys: netinet netinet6 [This broke ci.freebsd.org 's FreeBSD-head-mips*-build 's] From: Michael Tuexen In-Reply-To: Date: Tue, 31 Jul 2018 08:28:02 +0200 Cc: FreeBSD Current , svn-src-head@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3865FB6F-B74D-472E-A755-FE55C18AE217@freebsd.org> References: To: Mark Millard X-Mailer: Apple Mail (2.3445.9.1) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 31 Jul 2018 06:28:08 -0000 > On 31. Jul 2018, at 03:44, Mark Millard = wrote: >=20 > https://ci.freebsd.org/job/FreeBSD-head-mips-build/3577/consoleText = shows: >=20 > --- tcp_usrreq.o --- > cc1: warnings being treated as errors > /usr/src/sys/netinet/tcp_usrreq.c: In function 'tcp_usr_send': > /usr/src/sys/netinet/tcp_usrreq.c:905: warning: unused variable 'sin' = [-Wunused-variable] > . . . > --- tcp_usrreq.o --- > *** [tcp_usrreq.o] Error code 1 >=20 > make[2]: stopped in /usr/obj/usr/src/mips.mips/sys/MALTA > 1 error >=20 > (Note: -r366935 built correctly as #3576 .) >=20 >=20 >=20 > https://ci.freebsd.org/job/FreeBSD-head-mips64-build/3624/consoleText = shows: >=20 > --- tcp_usrreq.o --- > cc1: warnings being treated as errors > /usr/src/sys/netinet/tcp_usrreq.c: In function 'tcp_usr_send': > /usr/src/sys/netinet/tcp_usrreq.c:905: warning: unused variable 'sin' = [-Wunused-variable] > *** [tcp_usrreq.o] Error code 1 >=20 > make[2]: stopped in /usr/obj/usr/src/mips.mips64/sys/MALTA64 >=20 > (Note: -r366935 built correctly as #3623 .) Fixed in https://svnweb.freebsd.org/changeset/base/336962 Thanks for the report and sorry for the breakage. Best regards Michael >=20 >=20 >=20 >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) >=20 From owner-freebsd-current@freebsd.org Tue Jul 31 10:41:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABCAA105547E; Tue, 31 Jul 2018 10:41:20 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 586CA840DE; Tue, 31 Jul 2018 10:41:20 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6F42821C47; Tue, 31 Jul 2018 06:41:19 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 31 Jul 2018 06:41:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=jgWSuDk6w7G1EtDVhtvuDyHaxMTUIDA67msZLglXhXc=; b=PqNQaq/h hwNYFG9JrHU1U00XK1BkRYLB28kfZPFTnmmQZQx4j/D/End38XRlY2dP8U4L2IYT fHuI1kvrynpget9egYFYHTKqaQbiUjrfL/9Hg2NhB22k/nWPHN+S9kkAbbp7jHhv l/o2iN5Q3MUAlf2qKL+jPsWb0E6qpr2NnzkdnvNvRLI9sXoqZPUbV7Mii54JRHZ0 LWP3aCuNB6YW2rhv5ScvrEa97ruJT8c1Yobj7R8pPiMlTKBwsH+JXmnjZBZUvN4O z3kn6KlAtQRixMtG3aeLplRLl6BP9hHXp2V9FhpRnnpjbXBdPW5yc2pqjvMeGFsR 8icm02yjv/GebQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=jgWSuDk6w7G1EtDVhtvuDyHaxMTUI DA67msZLglXhXc=; b=ELYnYOliIV6+mo7MvacmUtMzulcT7ljosyElVQDuZgV2t 6dPGu4Nb4AO275iLU6X1SnJIS5pOPDRTI0k83GZ0ZftY2SWuxzBnjw4whXDoCHWA Bu3JeN1dBw2tj1/0hmfulP4PLbQKYwOOwVetgummDFG5hBt1D0hshz0RnFp5/r4w WECNYaRtXaW2PEbF8+z31qOB6rAuiUvDV+fTXEgH6d4t2S/QfgA1Qnb+2pGE8sN8 L6+PLGUTy17nxZ4NKuS5k4LjtH47d9aetCuQ0tFA5DSwuWm3uzPFi97qxFbkmrMk D4Pc/kv1SmGiKJMqQXTZ/ND2W4+O4tpJczSD98V2g== X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id A51211026B; Tue, 31 Jul 2018 06:41:18 -0400 (EDT) To: freebsd-ports@freebsd.org Cc: freebsd-questions@freebsd.org, FreeBSD Current From: tech-lists Subject: how to make ports not install xorg or dependencies Organization: none Message-ID: <703ec31c-a798-68c6-c9fa-4d73bce50be2@zyxst.net> Date: Tue, 31 Jul 2018 11:41:17 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 31 Jul 2018 10:41:20 -0000 Hello, context: freebsd-12 r336215 arm64 I don't want xorg or X11 or any of its components installed on this system. I install ports in the traditional way, in other words cd port && make config && make install. Any ports that in a generic config want to install xorg libs, I want the no-x11 variant. There used to be a way to enforce this no-xorg in make.conf but looking at /usr/share/examples/etc/make.conf I can find no reference to X Xorg x11 or xorg. I presume there's a new method. If there is, can anyone please tell me how? thanks, -- J. From owner-freebsd-current@freebsd.org Tue Jul 31 10:49:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 728051055A33; Tue, 31 Jul 2018 10:49:39 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 E2ECE8477C; Tue, 31 Jul 2018 10:49:38 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 41ftVT4kwvz6dVQ; Tue, 31 Jul 2018 12:49:37 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id GP8N408Eqh-n; Tue, 31 Jul 2018 12:49:35 +0200 (CEST) Received: from marvin.madpilot.net (host109-130-dynamic.20-87-r.retail.telecomitalia.it [87.20.130.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.madpilot.net (Postfix) with ESMTPSA; Tue, 31 Jul 2018 12:49:35 +0200 (CEST) Subject: Re: how to make ports not install xorg or dependencies To: tech-lists , freebsd-ports@freebsd.org Cc: FreeBSD Current , freebsd-questions@freebsd.org References: <703ec31c-a798-68c6-c9fa-4d73bce50be2@zyxst.net> From: Guido Falsi Openpgp: preference=signencrypt Autocrypt: addr=mad@madpilot.net; prefer-encrypt=mutual; keydata= xsBNBE+G+l0BCADi/WBQ0aRJfnE7LBPsM0G3m/m3Yx7OPu4iYFvS84xawmRHtCNjWIntsxuX fptkmEo3Rsw816WUrek8dxoUAYdHd+EcpBcnnDzfDH5LW/TZ4gbrFezrHPdRp7wdxi23GN80 qPwHEwXuF0X4Wy5V0OO8B6VT/nA0ADYnBDhXS52HGIJ/GCUjgqJn+phDTdCFLvrSFdmgx4Wl c0W5Z1p5cmDF9l8L/hc959AeyNf7I9dXnjekGM9gVv7UDUYzCifR3U8T0fnfdMmS8NeI9NC+ wuREpRO4lKOkTnj9TtQJRiptlhcHQiAlG1cFqs7EQo57Tqq6cxD1FycZJLuC32bGbgalABEB AAHNHkd1aWRvIEZhbHNpIDxtYWRAbWFkcGlsb3QubmV0PsLAeQQTAQgAIwIbAwIeAQIXgAUL CQgHAwUVCgkICwQWAgMBBQJS79AgAhkBAAoJEBrmhg5Wy9KTc0kH/RO64ORBlTbTHaUaOj8F Je5O5NU2Pt9Cyt5ZWBRvxntr1zPTJGKRPS9ihlIfqT4ZvEngQGp57EUyFbCpI0UWasTerImM tt5WACnGmCzUTB39UXx8Oy4b1EgWeTJQ747e/F1mQLXTNa6ijRBE9fYlTb4gAkPN88/wVV9v 3PZozKLTg16ghBzHM/P7Lk8L7clPEZChX1FTa/6eSt3nvzfCuTMZbBPJF/ph+q1KyPqRgVfh tyhu5dvgMoPz/ni41IfeSrkJTD5RXzdyGR9q4Z1NYeBsLkRjC4LxKAP5KqUsvlOUjKvO1byj ApYdMarol+IGkaSk9e3zVYAJkWKjn/ni8XbOwU0EUxB7QQEQAKFhrDceoPdK/IHDSmoj6SQY isvM7VdhcleS7E9DoEAVt7yMbf6HbbMVTTY6ckvwTWQssywLBXNVqxgc4WLJjzfUhgef+WE7 5M3+WFYlOVQLGZY/zEVgma1raYnOHNAOzeHLDmEXjbZP6vGAeDyBbGfQPpE7qGYZ7ubeT3Xw QO+PklcCrvOPj2ZPcAxGNS2xVU/LzONqCrJqLMJSIcCdsbiSP4G5PnDFHtMokaTY6OEr8OEQ fOAerhcHUa/z7Uu8YtmaqKH+QGkE/WEgaRqSiTnv0JOTD+DxehaqvoKPPZ++2NpCZMHB2i6A /xifmQwEiIjEXtcueBRzkNUQkxhqZyS13SrhocL9ydtaVPBzZatAEjUDDEJmAMLVFs45qfyh MiNapHJo2n3MW/E5omqCvEkDdWX/en3P7CK2TemeaDghMsgkNKax/z0wNo5UZCkOPOz0xpNi UilOVbkuezZZNg65741qee2lfXhQIaZ66yT7hphc/N/z3PIAtLeze4u1VR2EXAuZ2sWAdlKC NTlJMsaU/x70BV11Wd/ypnVzM68dfdQIIAj1iMFAD/lXGlEUmKXg5Ov2VQDlTntQoanCYrAg +8CttPzjrydgLZFq3hrtQmfc0se5yv1WHS69+BsUOG09RvvawUDZxUjW19kyeN9THaNRgow3 kSuArUp6zSmJABEBAAHCwF8EGAEIAAkFAlMQe0ECGwwACgkQGuaGDlbL0pMN5wgA4bCkX/qw EVC06ToeR6C2putmSWQMgpDaqrv65Hubo+QGmg2P4ewTYQQ4g6oYWS03qHxqVVWhKz7FjfrV +dH8qbCLfSgIcvdBha7ayGZVrsiuMLKGbw36fcmkZPpSDOfHcP0XH8Z+u9CWj0xUkTxAlZ/7 i6gYSUpG2JWNtdmE/X8VVEyXusCLwy0K0BI60A/4dRTIX3C4QKrJ3ZbUXegz70ynjHf+lQMZ 9IZKASoRMuS5FozPQh6abvmwZEPdf5I9riUElzvHrqJ8Bx0t3Pujdoth+yNHpnBxrtO8LkQd rQ58P0SwcaIX33T2U9pG8bhu5YVR88FQ8OQ0cEsPBpDncg== Message-ID: <1d971811-95eb-efa9-af2a-c9fb5a3b5313@madpilot.net> Date: Tue, 31 Jul 2018 12:49:35 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <703ec31c-a798-68c6-c9fa-4d73bce50be2@zyxst.net> 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.27 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, 31 Jul 2018 10:49:39 -0000 On 7/31/18 12:41 PM, tech-lists wrote: > Hello, > > context: freebsd-12 r336215 arm64 > > I don't want xorg or X11 or any of its components installed on this > system. I install ports in the traditional way, in other words cd port > && make config && make install. Any ports that in a generic config want > to install xorg libs, I want the no-x11 variant. > > There used to be a way to enforce this no-xorg in make.conf but looking > at /usr/share/examples/etc/make.conf I can find no reference to X Xorg > x11 or xorg. I presume there's a new method. If there is, can anyone > please tell me how? You can add OPTIONS_UNSET+=X11 in make.conf. ports having an X11 option will have that disabled by default. There is no warranty no port will have X11 dependencies anyway, it's not mandatory to respect that knob. -- Guido Falsi From owner-freebsd-current@freebsd.org Tue Jul 31 10:51:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99A4D1055AFB; Tue, 31 Jul 2018 10:51:18 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 17023849F4; Tue, 31 Jul 2018 10:51:18 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 41ftXP0bWGz6dVQ; Tue, 31 Jul 2018 12:51:17 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id eWJQW70RVhCM; Tue, 31 Jul 2018 12:51:15 +0200 (CEST) Received: from marvin.madpilot.net (host109-130-dynamic.20-87-r.retail.telecomitalia.it [87.20.130.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.madpilot.net (Postfix) with ESMTPSA; Tue, 31 Jul 2018 12:51:15 +0200 (CEST) Subject: Re: how to make ports not install xorg or dependencies From: Guido Falsi To: tech-lists , freebsd-ports@freebsd.org Cc: FreeBSD Current , freebsd-questions@freebsd.org References: <703ec31c-a798-68c6-c9fa-4d73bce50be2@zyxst.net> <1d971811-95eb-efa9-af2a-c9fb5a3b5313@madpilot.net> Openpgp: preference=signencrypt Autocrypt: addr=mad@madpilot.net; prefer-encrypt=mutual; keydata= xsBNBE+G+l0BCADi/WBQ0aRJfnE7LBPsM0G3m/m3Yx7OPu4iYFvS84xawmRHtCNjWIntsxuX fptkmEo3Rsw816WUrek8dxoUAYdHd+EcpBcnnDzfDH5LW/TZ4gbrFezrHPdRp7wdxi23GN80 qPwHEwXuF0X4Wy5V0OO8B6VT/nA0ADYnBDhXS52HGIJ/GCUjgqJn+phDTdCFLvrSFdmgx4Wl c0W5Z1p5cmDF9l8L/hc959AeyNf7I9dXnjekGM9gVv7UDUYzCifR3U8T0fnfdMmS8NeI9NC+ wuREpRO4lKOkTnj9TtQJRiptlhcHQiAlG1cFqs7EQo57Tqq6cxD1FycZJLuC32bGbgalABEB AAHNHkd1aWRvIEZhbHNpIDxtYWRAbWFkcGlsb3QubmV0PsLAeQQTAQgAIwIbAwIeAQIXgAUL CQgHAwUVCgkICwQWAgMBBQJS79AgAhkBAAoJEBrmhg5Wy9KTc0kH/RO64ORBlTbTHaUaOj8F Je5O5NU2Pt9Cyt5ZWBRvxntr1zPTJGKRPS9ihlIfqT4ZvEngQGp57EUyFbCpI0UWasTerImM tt5WACnGmCzUTB39UXx8Oy4b1EgWeTJQ747e/F1mQLXTNa6ijRBE9fYlTb4gAkPN88/wVV9v 3PZozKLTg16ghBzHM/P7Lk8L7clPEZChX1FTa/6eSt3nvzfCuTMZbBPJF/ph+q1KyPqRgVfh tyhu5dvgMoPz/ni41IfeSrkJTD5RXzdyGR9q4Z1NYeBsLkRjC4LxKAP5KqUsvlOUjKvO1byj ApYdMarol+IGkaSk9e3zVYAJkWKjn/ni8XbOwU0EUxB7QQEQAKFhrDceoPdK/IHDSmoj6SQY isvM7VdhcleS7E9DoEAVt7yMbf6HbbMVTTY6ckvwTWQssywLBXNVqxgc4WLJjzfUhgef+WE7 5M3+WFYlOVQLGZY/zEVgma1raYnOHNAOzeHLDmEXjbZP6vGAeDyBbGfQPpE7qGYZ7ubeT3Xw QO+PklcCrvOPj2ZPcAxGNS2xVU/LzONqCrJqLMJSIcCdsbiSP4G5PnDFHtMokaTY6OEr8OEQ fOAerhcHUa/z7Uu8YtmaqKH+QGkE/WEgaRqSiTnv0JOTD+DxehaqvoKPPZ++2NpCZMHB2i6A /xifmQwEiIjEXtcueBRzkNUQkxhqZyS13SrhocL9ydtaVPBzZatAEjUDDEJmAMLVFs45qfyh MiNapHJo2n3MW/E5omqCvEkDdWX/en3P7CK2TemeaDghMsgkNKax/z0wNo5UZCkOPOz0xpNi UilOVbkuezZZNg65741qee2lfXhQIaZ66yT7hphc/N/z3PIAtLeze4u1VR2EXAuZ2sWAdlKC NTlJMsaU/x70BV11Wd/ypnVzM68dfdQIIAj1iMFAD/lXGlEUmKXg5Ov2VQDlTntQoanCYrAg +8CttPzjrydgLZFq3hrtQmfc0se5yv1WHS69+BsUOG09RvvawUDZxUjW19kyeN9THaNRgow3 kSuArUp6zSmJABEBAAHCwF8EGAEIAAkFAlMQe0ECGwwACgkQGuaGDlbL0pMN5wgA4bCkX/qw EVC06ToeR6C2putmSWQMgpDaqrv65Hubo+QGmg2P4ewTYQQ4g6oYWS03qHxqVVWhKz7FjfrV +dH8qbCLfSgIcvdBha7ayGZVrsiuMLKGbw36fcmkZPpSDOfHcP0XH8Z+u9CWj0xUkTxAlZ/7 i6gYSUpG2JWNtdmE/X8VVEyXusCLwy0K0BI60A/4dRTIX3C4QKrJ3ZbUXegz70ynjHf+lQMZ 9IZKASoRMuS5FozPQh6abvmwZEPdf5I9riUElzvHrqJ8Bx0t3Pujdoth+yNHpnBxrtO8LkQd rQ58P0SwcaIX33T2U9pG8bhu5YVR88FQ8OQ0cEsPBpDncg== Message-ID: <68cef083-a3d1-88f0-941c-441f5b2ba164@madpilot.net> Date: Tue, 31 Jul 2018 12:51:14 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <1d971811-95eb-efa9-af2a-c9fb5a3b5313@madpilot.net> 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.27 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, 31 Jul 2018 10:51:18 -0000 On 7/31/18 12:49 PM, Guido Falsi wrote: > On 7/31/18 12:41 PM, tech-lists wrote: >> Hello, >> >> context: freebsd-12 r336215 arm64 >> >> I don't want xorg or X11 or any of its components installed on this >> system. I install ports in the traditional way, in other words cd port >> && make config && make install. Any ports that in a generic config want >> to install xorg libs, I want the no-x11 variant. >> >> There used to be a way to enforce this no-xorg in make.conf but looking >> at /usr/share/examples/etc/make.conf I can find no reference to X Xorg >> x11 or xorg. I presume there's a new method. If there is, can anyone >> please tell me how? > > You can add OPTIONS_UNSET+=X11 in make.conf. > > ports having an X11 option will have that disabled by default. > > There is no warranty no port will have X11 dependencies anyway, it's not > mandatory to respect that knob. > I was too hasty in hitting send. There are other options which influence X11 dependencies. I usually also disable XPM and CUPS at least. It also depends on which ports you are installing. -- Guido Falsi From owner-freebsd-current@freebsd.org Tue Jul 31 11:13:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A200E10566BE; Tue, 31 Jul 2018 11:13:35 +0000 (UTC) (envelope-from SRS0=JK01=KP=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3EF1A85A55; Tue, 31 Jul 2018 11:13:35 +0000 (UTC) (envelope-from SRS0=JK01=KP=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 02E9828416; Tue, 31 Jul 2018 13:13:33 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 0DBCA28412; Tue, 31 Jul 2018 13:13:31 +0200 (CEST) Subject: Re: how to make ports not install xorg or dependencies To: tech-lists , freebsd-ports@freebsd.org Cc: freebsd-questions@freebsd.org, FreeBSD Current References: <703ec31c-a798-68c6-c9fa-4d73bce50be2@zyxst.net> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <8265d700-9f0f-d2a5-a2c8-96ad4dd2e8b2@quip.cz> Date: Tue, 31 Jul 2018 13:13:31 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <703ec31c-a798-68c6-c9fa-4d73bce50be2@zyxst.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 31 Jul 2018 11:13:35 -0000 tech-lists wrote on 2018/07/31 12:41: > There used to be a way to enforce this no-xorg in make.conf but looking > at /usr/share/examples/etc/make.conf I can find no reference to X Xorg > x11 or xorg. I presume there's a new method. If there is, can anyone > please tell me how? We are using OPTIONS_UNSET= X11 GUI CUPS DOCS EXAMPLES NLS for all of our packages (built with poudriere) As Guido Falsi already said it is not guaranteed that you will not have ports with some X libs, because some ports does not have option to disable X11 dependencies. Miroslav Lachman From owner-freebsd-current@freebsd.org Tue Jul 31 16:38:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13300105E5FA; Tue, 31 Jul 2018 16:38:16 +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 8541471691; Tue, 31 Jul 2018 16:38:15 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w6VGPb1x032224; Tue, 31 Jul 2018 09:25:43 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "FreeBSD Current"freebsd-current@freebsd.org From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "FreeBSD Stable"freebsd-stable@freebsd.org Subject: Can't upgrade past 10.4-STABLE (interrupt storm?) Date: Tue, 31 Jul 2018 09:25:43 -0700 Message-Id: <7406fb42a5e2ec2cb09fca98ca1e39bb@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 31 Jul 2018 17:54:57 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 31 Jul 2018 16:38:16 -0000 Hello, I've got an older laptop that I attempted to install 12 on w/o success=2E Well, it installed=2E But was unusable=2E Typing anything at the console frequently doesn't output on the screen w/o tapping one of the arrow keys=2E But doing that causes other problems=2E As I can't really use the output=2E :( I suspected an interrupt storm of some type=2E But really can't say for sure=2E a vmstat -i seems to show unusually high numbers for irq1: atkbd0 often ~1/3rd the number for CPU0=2E I can easily realize all this during the install process from the install media=2E So it's easy to test=2E This is a i386 based Pentium M=2E FreeBSD 10=2E4-STABLE runs like a dream=2E But I'm going to need to move forward at some point, and I'd like that some point to be now=2E :) Any thoughts on how I might discover /what/ change was made from 10=2E4-->11* to cause this? It has a trackpad=2E Should that make any difference=2E Thanks! --Chris From owner-freebsd-current@freebsd.org Wed Aug 1 04:27:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F3CB1048E2C for ; Wed, 1 Aug 2018 04:27:22 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: from sanddollar.geekisp.com (sanddollar.geekisp.com [216.168.135.167]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.geekisp.com", Issuer "mail.geekisp.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D4D2073077 for ; Wed, 1 Aug 2018 04:27:21 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: (qmail 27592 invoked by uid 1003); 1 Aug 2018 04:20:42 -0000 Received: from unknown (HELO grape.lasagna.io) (tyler@monkeypox.org@173.228.82.91) by mail.geekisp.com with (AES256-SHA encrypted) SMTP; 1 Aug 2018 04:20:42 -0000 Date: Tue, 31 Jul 2018 21:20:34 -0700 From: "R. Tyler Croy" To: Michael Butler Cc: tech-lists , freebsd-current@freebsd.org Subject: Re: em0 link fail Message-ID: <20180801042034.GD3303@grape.lasagna.io> References: <739ef71a-f29f-68ea-955a-fb53c57960a6@protected-networks.net> <8e2bf594-6d7e-477e-836b-4cc4483cb525@protected-networks.net> <64e462dd-16fc-b57f-7bf2-02068d0e24c8@zyxst.net> <7a4607ce-e212-5cba-bc04-1d0abf1a7824@protected-networks.net> <20180726044705.GB5081@grape.lasagna.io> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XuV1QlJbYrcVoo+x" Content-Disposition: inline In-Reply-To: <20180726044705.GB5081@grape.lasagna.io> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 04:27:22 -0000 --XuV1QlJbYrcVoo+x Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable (replies inline) On Wed, 25 Jul 2018, R. Tyler Croy wrote: > (replies inline) >=20 > On Sun, 15 Jul 2018, Michael Butler wrote: >=20 > > On 07/05/18 09:54, I wrote: > > > On 07/05/18 09:27, tech-lists wrote: > > >> On 03/07/2018 19:47, Michael Butler wrote: > > >>> That would've been .. > > >>> > > >>> Jun=A0 1 09:56:15 toshi kernel: FreeBSD 12.0-CURRENT #35 r334484: F= ri Jun > > >>> 1 08:25:58 EDT 2018 > > >>> > > >>> I'm going to build one with SVN r334862 reverted to see if that wor= ks, > > >> > > >> Hi, > > >> > > >> Is it working now? Am asking because a system I'd like to take from > > >> 11-stable to 12 uses the em driver. > > >=20 > > > No :-( I haven't had the chance yet to revisit it, > >=20 > > As it turns out, SVN r336313 (committed today) solves the issue I was > > having with the hardware stalling, >=20 >=20 >=20 > I'll give r336313 a try as soon as possible and corroborate the fixes! After a couple days with this new build, it looks like i can corroborate the fix referenced by Michael. :D --XuV1QlJbYrcVoo+x Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSQYoZaRujHSSvxiNcUJsfcP1HhbwUCW2E1EgAKCRAUJsfcP1Hh b3ddAKCoOMzjoek6qjZGlGPqXJhmPKBN/QCcCo3uPBrnLbZifJhKjE8ZA3lXaRs= =Mv+F -----END PGP SIGNATURE----- --XuV1QlJbYrcVoo+x-- From owner-freebsd-current@freebsd.org Wed Aug 1 07:58:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B447105D132 for ; Wed, 1 Aug 2018 07:58:50 +0000 (UTC) (envelope-from yuri@rawbw.com) 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 96462871F4 for ; Wed, 1 Aug 2018 07:58:49 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5B006105D131; Wed, 1 Aug 2018 07:58:49 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49B96105D130 for ; Wed, 1 Aug 2018 07:58:49 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id A8672871F3 for ; Wed, 1 Aug 2018 07:58:48 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id w717wkWa029105 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 1 Aug 2018 00:58:47 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132] claimed to be yv.noip.me To: current From: Yuri Subject: Error occurs in the VirtualBox VM installed from the vmdk image when "close" is pressed on the VM window Message-ID: <9e22fe0a-b8bc-d6e3-f3c0-4b8c79caac53@rawbw.com> Date: Wed, 1 Aug 2018 00:58:45 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 07:58:50 -0000 I installed this VMDK image https://download.freebsd.org/ftp/snapshots/VM-IMAGES/12.0-CURRENT/amd64/Latest/FreeBSD-12.0-CURRENT-amd64.vmdk.xz rom Jul 26. Once it boots, pressing "close" causes the error. Yuri From owner-freebsd-current@freebsd.org Wed Aug 1 10:45:57 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 114F51051FE8; Wed, 1 Aug 2018 10:45:57 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 7665E8D4E1; Wed, 1 Aug 2018 10:45:56 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [172.16.0.23] (unknown [172.16.0.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 19C6F5CC4; Wed, 1 Aug 2018 10:45:50 +0000 (UTC) To: "freebsd-hackers@freebsd.org" , "freebsd-security@freebsd.org security" , "freebsd-arch@freebsd.org" , freebsd-current From: Eric McCorkle Subject: Status of OpenSSL 1.1.1 Openpgp: preference=signencrypt Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEWue2FBYJKwYBBAHaRw8BAQdAP/qVPlXodV6pYO5b1Jw0eFyMhyDD7B5y5eFsciutEfS0 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiWBBMWCAA+FiEEDxi/0rkj zd6Uc6cFCN/CKRbBwmwFAlrnthQCGwMFCQHhM4AFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQCN/CKRbBwmyGKAD/XTSBOItCKcYCPTlsaS1aQYVEwWXXFgdjWE+WsNdZUS8A/AhYAbQZ kNZNimE2rQLoklkfTA74qF/V257NuQi4QDcLuDgEWue2FBIKKwYBBAGXVQEFAQEHQKpZVyCG ync/xqejm2C1HKGXLJTUu38RvnrR3UYECz9nAwEIB4h+BBgWCAAmFiEEDxi/0rkjzd6Uc6cF CN/CKRbBwmwFAlrnthQCGwwFCQHhM4AACgkQCN/CKRbBwmyi2wEAmvaGt8QMjGELzm27gP4c jJGUi7oigsLmTiFPkpJqPz0A+QFBSCvxJaxCMyoVru/xB6bunpJ+Wtsj8HD1EuJOn4EJ Message-ID: Date: Wed, 1 Aug 2018 06:45:46 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="uvRxCuPiU4O8rLJUO8gnVepNcNGAYCG8B" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 10:45:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --uvRxCuPiU4O8rLJUO8gnVepNcNGAYCG8B Content-Type: multipart/mixed; boundary="5PqJ62IpHtYhdL4HEu7BZ3qbdy4AlIwSY"; protected-headers="v1" From: Eric McCorkle To: "freebsd-hackers@freebsd.org" , "freebsd-security@freebsd.org security" , "freebsd-arch@freebsd.org" , freebsd-current Message-ID: Subject: Status of OpenSSL 1.1.1 --5PqJ62IpHtYhdL4HEu7BZ3qbdy4AlIwSY Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi folks, I'm wondering what's the status of OpenSSL 1.1.1 integration into base? More specifically, is there a repo or a branch that's started the integration? I'm aware of the wiki page and the list of port build issues, but that seems to be based on replacing the base OpenSSL with a port build (similar to the way one replaces it with LibreSSL). I have some work I'd like to do that's gating on sorting out the kernel/loader crypto situation, and I'd very much like to see OpenSSL 1.1.1 get merged, so I can start to look into doing that. Incidentally, if there's something I can do to help out with integrating 1.1.1 into base, I'd potentially be interested. --5PqJ62IpHtYhdL4HEu7BZ3qbdy4AlIwSY-- --uvRxCuPiU4O8rLJUO8gnVepNcNGAYCG8B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQPGL/SuSPN3pRzpwUI38IpFsHCbAUCW2GPWgAKCRAI38IpFsHC bJePAQCmuLjTR2PAwzbA+l16EUlF5M109QDnv/UGFSBQp0RSngD/fN4NHt3Vfmq3 /dlzLN2yDCJasSCThgN25NbUisHRjQI= =RdGb -----END PGP SIGNATURE----- --uvRxCuPiU4O8rLJUO8gnVepNcNGAYCG8B-- From owner-freebsd-current@freebsd.org Wed Aug 1 13:02:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BF1B105B959 for ; Wed, 1 Aug 2018 13:02:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE9F372EBD for ; Wed, 1 Aug 2018 13:02:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x233.google.com with SMTP id k16-v6so15965590iom.12 for ; Wed, 01 Aug 2018 06:02:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9iFYQcW5bmYSYAKQpPKP2DdPY4RdHvnvxYD2jmtwvjQ=; b=iyxCR24fC4dqI/L954Zn7ydCbmXmQPWvyEqGSkU2iA1UvVmSLAgAnhguZdSynfF0Hq WnivKz3YwNTX4+eiGKzB85hR/dKcOh4WTlqoFhZzxJjA6RZfH2bcqlmxPV+vav6tfT9a NDWWepXvfKN80sApvLfnZ+tuy0+Q8zS4k1mSlzv0mNVoxrrwnLXhgWPzEr1xbdEGfTbv 1GtDqVC8yoB80lwOxr9H8Ceg5NMsz7IRF/y426zU7i/I8TBNcdoxj0j00btdPrN+paNM b3RARY5wgPgyJGZ2pIsUjoffNQ7RI5DtZUTBLSjohLtrFvyaewH55uwLl9GARo94Rn78 DpRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9iFYQcW5bmYSYAKQpPKP2DdPY4RdHvnvxYD2jmtwvjQ=; b=CPKUvsazI3oSGPkLC8qOdPUU/z42m5lsjmWGAvdFv/fH0sUHpQ2SYLr709UgtId7bP ck/YpzpmkvluFbvN/zGGvkMjbShV5iGiq8HYOXF6So2jOJsFWZn+Z0Iunqu4DEBUlP9e 3BuNGUweeilBVvZMy7jAYbFnKbQu39/4CrIB4EwwYyv/KLIVS4BV80TJR8NEM+aOSCOc D8+I7vOFcQV3nFS9QWOUoweXtUpHCqDFzgjxShjGuHhCM1DR9e+YxiJUM0po2uA0+Xzc TXHBXp+aT0xVP1elVSs/c8yftRrqe6D7ciKdnIg/Aiz4NdGEgntcEkFW3sHP0Nn17Ln6 hPoA== X-Gm-Message-State: AOUpUlHpBAquF2VnJ11lEgVer/uWRhKuTPdvYHwb/H1m50O6VvniwOpP wh520FOkxCPyYxf3zAVgLuWsIo5VjSo6bwHa7dQMHw== X-Google-Smtp-Source: AAOMgpeua2uji37665Jo3KSqhx78c+24h3sP4o9fScVTtTBwXOSp64OteB/mdos3JzjKyjEX3Pu6HBriOS55QEWwyyQ= X-Received: by 2002:a6b:3902:: with SMTP id g2-v6mr3217918ioa.168.1533128577684; Wed, 01 Aug 2018 06:02:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Wed, 1 Aug 2018 14:02:46 +0100 Message-ID: Subject: Re: Status of OpenSSL 1.1.1 To: Eric McCorkle Cc: FreeBSD Hackers , freebsd-security , "freebsd-arch@freebsd.org" , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 13:02:59 -0000 On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle wrote: > Hi folks, > > I'm wondering what's the status of OpenSSL 1.1.1 integration into base? > More specifically, is there a repo or a branch that's started the > integration? I'm aware of the wiki page and the list of port build > issues, but that seems to be based on replacing the base OpenSSL with a > port build (similar to the way one replaces it with LibreSSL). > > I have some work I'd like to do that's gating on sorting out the > kernel/loader crypto situation, and I'd very much like to see OpenSSL > 1.1.1 get merged, so I can start to look into doing that. > There are patches to use bear SSL for the loader. OpenSSL is simply too large to use due to limits the loader operates under. Warner Incidentally, if there's something I can do to help out with integrating > 1.1.1 into base, I'd potentially be interested. > > From owner-freebsd-current@freebsd.org Wed Aug 1 14:05:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60F1C105D3E4; Wed, 1 Aug 2018 14:05:34 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (static-98-116-200-172.nycmny.fios.verizon.net [98.116.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id 0773B754A8; Wed, 1 Aug 2018 14:05:33 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [192.168.43.57] (mobile-107-107-59-242.mycingular.net [107.107.59.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 7B9BF5D4F; Wed, 1 Aug 2018 14:05:32 +0000 (UTC) Subject: Re: Status of OpenSSL 1.1.1 To: Warner Losh Cc: FreeBSD Hackers , freebsd-security , "freebsd-arch@freebsd.org" , freebsd-current References: From: Eric McCorkle Openpgp: preference=signencrypt Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEWue2FBYJKwYBBAHaRw8BAQdAP/qVPlXodV6pYO5b1Jw0eFyMhyDD7B5y5eFsciutEfS0 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiWBBMWCAA+FiEEDxi/0rkj zd6Uc6cFCN/CKRbBwmwFAlrnthQCGwMFCQHhM4AFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQCN/CKRbBwmyGKAD/XTSBOItCKcYCPTlsaS1aQYVEwWXXFgdjWE+WsNdZUS8A/AhYAbQZ kNZNimE2rQLoklkfTA74qF/V257NuQi4QDcLuDgEWue2FBIKKwYBBAGXVQEFAQEHQKpZVyCG ync/xqejm2C1HKGXLJTUu38RvnrR3UYECz9nAwEIB4h+BBgWCAAmFiEEDxi/0rkjzd6Uc6cF CN/CKRbBwmwFAlrnthQCGwwFCQHhM4AACgkQCN/CKRbBwmyi2wEAmvaGt8QMjGELzm27gP4c jJGUi7oigsLmTiFPkpJqPz0A+QFBSCvxJaxCMyoVru/xB6bunpJ+Wtsj8HD1EuJOn4EJ Message-ID: Date: Wed, 1 Aug 2018 10:05:28 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 14:05:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS Content-Type: multipart/mixed; boundary="MkkRTdgKDiexhqqCfM3q3sy204CtZoNlA"; protected-headers="v1" From: Eric McCorkle To: Warner Losh Cc: FreeBSD Hackers , freebsd-security , "freebsd-arch@freebsd.org" , freebsd-current Message-ID: Subject: Re: Status of OpenSSL 1.1.1 References: In-Reply-To: --MkkRTdgKDiexhqqCfM3q3sy204CtZoNlA Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 08/01/2018 09:02, Warner Losh wrote: >=20 >=20 > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > wrote: >=20 > Hi folks, >=20 > I'm wondering what's the status of OpenSSL 1.1.1 integration into b= ase? > More specifically, is there a repo or a branch that's started the > integration?=C2=A0 I'm aware of the wiki page and the list of port = build > issues, but that seems to be based on replacing the base OpenSSL wi= th a > port build (similar to the way one replaces it with LibreSSL). >=20 > I have some work I'd like to do that's gating on sorting out the > kernel/loader crypto situation, and I'd very much like to see OpenS= SL > 1.1.1 get merged, so I can start to look into doing that. >=20 >=20 > There are patches to use bear SSL for the loader. OpenSSL is simply too= > large to use due to limits the loader operates under. I was going to look into the feasibility of doing something like what LibreSSL does with portable, where they extract a subset of the full library designed to be embedded in the kernel, loader, etc. I think it ought to be possible to do something like that, but it really ought to be done in a tree with 1.1.1 integrated. --MkkRTdgKDiexhqqCfM3q3sy204CtZoNlA-- --JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQPGL/SuSPN3pRzpwUI38IpFsHCbAUCW2G+KAAKCRAI38IpFsHC bGLuAPwJYpPYYEmpGeu6HQnVaM9iakWHN8vM2OAGNoySUSn01QD/UfTooHun+QlI wvSpvUvJ1rCt+H5m6Ho6w49tHObnUgs= =jIbP -----END PGP SIGNATURE----- --JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS-- From owner-freebsd-current@freebsd.org Wed Aug 1 14:30:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADDE5105E8CD for ; Wed, 1 Aug 2018 14:30:00 +0000 (UTC) (envelope-from a.n.us@ieee.org) 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 527D476BAD for ; Wed, 1 Aug 2018 14:30:00 +0000 (UTC) (envelope-from a.n.us@ieee.org) Received: by mail-io0-x22c.google.com with SMTP id q19-v6so16195549ioh.11 for ; Wed, 01 Aug 2018 07:30:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=fKvWseJO15to3UkoKgDjFdBHmQGdUpJND+wmiqOvG8A=; b=C4+LJQdjcV+3+DJps2414NR3GnHcjwqhCQ+tIrgCey9rIG/EL+VFdcjrJJva5MyxbP PSWJDFnsctL88YPmfW4E1Gqnl4z7ICZCnmUXvmCqFKVc9cqnf9KuLl47CYN/dAiwiGh4 l2quSLK7UpTfZTfvsRKEKhol0SPXOy39LHe4wjhesOGvkn+ZC3N+WMOuFdAnR8Gfaf4k lpZhXqQYiAHf509y3iT4NoRrff8Cw8KpXquOdo4sQCTNjQ62hEppjMdo//E0Pb6VIwIh uYB+6AY3MytphBGElPYILxPS3xVnujOT6RKFcO6uuHX6RrnT/rcfdaX5QRYsPFiT3/Xu EoWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=fKvWseJO15to3UkoKgDjFdBHmQGdUpJND+wmiqOvG8A=; b=UKQsQVEpzzdoQ8SV4HM09nW7C/NEfuxdPaw6YSWz0vluiYmtr6fwvbDHu5gqfacPhl dhHQ4mOKowVP9Zek5UsvttDiSaJlWhZZIMmIevQyMUzkL6ZJPorhwo/QaenvBlhR+pxJ 4HejniQNYhUR4oh+tOVeWHyj5L+Lamw98l3iciDLzhwgjAc92T2oWQGoRu5i4lXWSsQm Xp7qjtmdZOaxa8exyQZy1ifvYu+9+YELzLHl2kwjoPSF9I5yg1O6DFvfbGIgsOla04+7 xH4FofBfJ4bqr3nGrzxdQETCt/Yzrm+4BLGbY4ZC+BjAgS61SNnc49ai4kUEVZiNP7g1 YwGg== X-Gm-Message-State: AOUpUlHs6UbIgCyu2gFYgHKzPkRmbk4h0My2e2dAsXoX5UNVSJSO+eFp 9P8W6QopVMEpthrTJul6gseOHd68Nm54a30ok/Uyi5sNJo0= X-Google-Smtp-Source: AAOMgpemMsyHLwOH0SvMsYYV5xZLpcZKM5JvDKhbwXoMVQBdoXp78aBUVuDFV1qx3PMhHwo+nNOzHzcypes0WlPR4zw= X-Received: by 2002:a6b:6306:: with SMTP id p6-v6mr3508066iog.175.1533133799288; Wed, 01 Aug 2018 07:29:59 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:5919:0:0:0:0:0 with HTTP; Wed, 1 Aug 2018 07:29:18 -0700 (PDT) From: AN Date: Wed, 1 Aug 2018 10:29:18 -0400 Message-ID: Subject: can't make installworld To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 14:30:00 -0000 FreeBSD BSD12 12.0-CURRENT FreeBSD 12.0-CURRENT #16 r335386: Tue Jun 19 19:57:51 EDT 2018 root@BSD12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 # cat /etc/master.passwd | grep ntp ntpd:*:123:123::0:0:NTP Daemon:/var/db/ntp:/usr/sbin/nologin # cat /etc/group | grep ntp ntpd:*:123: # svnlite info 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: 337003 Node Kind: directory Schedule: normal Last Changed Author: manu Last Changed Rev: 337000 Last Changed Date: 2018-07-31 15:14:52 -0400 (Tue, 31 Jul 2018) For several days I have been trying to update the world without success. In single user mode, trying to make installworld I get the following: >>>Installworld check ... Required tool true not found in path. Any idea how to fix this? From owner-freebsd-current@freebsd.org Wed Aug 1 14:41:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27605105F1FD for ; Wed, 1 Aug 2018 14:41:56 +0000 (UTC) (envelope-from gjb@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 C710C774CA; Wed, 1 Aug 2018 14:41:55 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 8D7C611548; Wed, 1 Aug 2018 14:41:55 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Wed, 1 Aug 2018 14:41:53 +0000 From: Glen Barber To: AN Cc: freebsd-current@freebsd.org Subject: Re: can't make installworld Message-ID: <20180801144153.GB96585@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NMuMz9nt05w80d4+" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 14:41:56 -0000 --NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 01, 2018 at 10:29:18AM -0400, AN wrote: > FreeBSD BSD12 12.0-CURRENT FreeBSD 12.0-CURRENT #16 r335386: Tue Jun > 19 19:57:51 EDT 2018 > root@BSD12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 >=20 > # cat /etc/master.passwd | grep ntp > ntpd:*:123:123::0:0:NTP Daemon:/var/db/ntp:/usr/sbin/nologin >=20 >=20 > # cat /etc/group | grep ntp > ntpd:*:123: >=20 This is a particularly annoying problem since 20180719. >=20 > # svnlite info > 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: 337003 > Node Kind: directory > Schedule: normal > Last Changed Author: manu > Last Changed Rev: 337000 > Last Changed Date: 2018-07-31 15:14:52 -0400 (Tue, 31 Jul 2018) >=20 >=20 > For several days I have been trying to update the world without > success. In single user mode, trying to make installworld I get the > following: >=20 > >>>Installworld check > ... > Required tool true not found in path. >=20 >=20 > Any idea how to fix this? What does your $PATH contain? Glen --NMuMz9nt05w80d4+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlthxqwACgkQAxRYpUeP 4pMOOA/+OFXI5D6cdYNNmvgiBd1EkUl9l/UR9SHhKlqWLLXQALTO7jA6fOzqXHlA JCpd4eXXEOwQOm8hDIyHrtTyY42NFvygCm4b3IHslPT/f0hd9c48ZxsvdFpFCrv7 wwP9xQcI3hwNo4A/Opk7459YkR5kSQDLBkzixs26fwo/af/PQ0BwmutQSOyYc+sx N7STinRR1VZe/gRHn8rwLZvarN4xg509PvUOCv+P5SUnR+MjEehKBbZ3IalrhBwE +UO1TG01vmewmFCgwQSVvDWTGCzcAvckJHqN9GRtgf2E0LqzDcSx4kkLmkq6vyug mLuJbyLbC81FQW9gFk6XK9S/5VaUkI0JxCFU0SfDFZWV3lGlo3vmbCKdE/3Ju6fk Nr4RF3LoANthcFu3hTTUVl+HvH8Uxlr/FWZSp1W4XaI3+tWSz/2MxkmAMAy2T3tc JDB4oxtA16T5oxa5K3YT/YGTF41jxIOotp4OGWmp+XMdYPKVxml7ozusGSFWd4PP CRf2xGpPNPt91FObb3cg7DXHL6pzY8/BSROnmYPWX3QBtryymyoNRDA4aOFs5z7R OEwGqnLUzYdcWWGX6nHWTBZ2WafXHiRA4Q4CVVZ63YaRTXpfQnqfIBKp++27GfX1 4N5D6sMNd43z/yocnHnZnD274zJGd4iZ3q2MHidtIYVlpfRvhZU= =1xut -----END PGP SIGNATURE----- --NMuMz9nt05w80d4+-- From owner-freebsd-current@freebsd.org Wed Aug 1 15:06:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9832105FF21 for ; Wed, 1 Aug 2018 15:06:34 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F41B7844A for ; Wed, 1 Aug 2018 15:06:34 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id n11-v6so7432007wmc.2 for ; Wed, 01 Aug 2018 08:06:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=hLv/5m1wyZclFwq7LAQBmFiTkWWNFjl7zqb/bQeMFgQ=; b=Yt36P1ZddVk5zpLu+kFIUH2q6YN7KHCgN06UxfUg8oOZ4a9mYinnWLZZQG3l/bD3Mr 9f52TYVaEMyUwV+zdE+gYEyo3oXssS4gB+9pUX+HHk8Dh58lXClmGkNyVhk2Yj+GBYXD 1KNb0uBN8bAYHQ3aRUffOX58x6Cloj71JqjJ+PrTPqcqHvwdL2ohK0k00UK7kndVGhzD 6E9nIn/aBk/tf9kbF/Bfg9kyfp9wf6oQ43E49rqISuMDzoOwA56abgv9OZyYQN74BEo6 U4WAuufenZh5q8oALYfkT0aIbfmwN4QSGpzvWjUnF3OF7BAwIzeJhtlO0XVmeZw3460T cLWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hLv/5m1wyZclFwq7LAQBmFiTkWWNFjl7zqb/bQeMFgQ=; b=ty7CP68dTYuPNd13aGjo/Gm0oC9/zx06pYll3iEglxvBGp2HDL+8YnSdZRLveRj7RJ 83jVixqxEe97HoTbELuWvHhjwCRDUb/SwhSPklGKWjmYDi4iCL5JfrrrgM8Op7dDY8e9 fDl+Yuhf6Js7ZU9R/h05dRvTxoDJt+auoW2EVgm3lewyeZ8T5pq68j2uabeSFW2Ga2Ed dLWQUWifSrgMN53lckB6QBet5idG3aLtAvTBwWe4Pk0/oGh1SnSsuZ6+SH98svfX5xME W3hzthkgRKkd4Geywf6efeRkJJDRUqNOjIlHecCy9Og9FJiwgt0Q5IkuLSJtnWnpSxC2 5cnA== X-Gm-Message-State: AOUpUlFNGaZJMsuOYD8JvvdkpES5yOtPCOnsy8HQ1Vp9OXsOMW/H/t/U SPh4v3AOHe1Ku7pSkf8bZhPCatqq9zbrHOQgYMEAww== X-Google-Smtp-Source: AAOMgpcUg7skgJ43cnr1F+a/dgeMN9E0PCIk9PI7L4HLYI1wsEuf40aY2Wf35vrj2hwHsDEEU1PmhuDQ3Kjy4nfcRno= X-Received: by 2002:a1c:af53:: with SMTP id y80-v6mr2855688wme.55.1533135992962; Wed, 01 Aug 2018 08:06:32 -0700 (PDT) MIME-Version: 1.0 From: Johannes Lundberg Date: Wed, 1 Aug 2018 16:05:56 +0100 Message-ID: Subject: acpiconf -s 3 does not call acpi sleep event handlers To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 15:06:34 -0000 Hi As the title says, callbacks registered with EVENTHANDLER_REGISTER(acpi_sleep_event, .... does not get called when calling acpiconf -s 3. They do however, when suspending with lid or sleep button. Is this deliberate or an oversight? Cheers From owner-freebsd-current@freebsd.org Wed Aug 1 15:18:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E31C10602D4 for ; Wed, 1 Aug 2018 15:18:13 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 0E2A978DE2 for ; Wed, 1 Aug 2018 15:18:12 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 16b54f68-959e-11e8-93fa-f3ebd9db2b94 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 16b54f68-959e-11e8-93fa-f3ebd9db2b94; Wed, 01 Aug 2018 15:18:05 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w71FI5Yv038157; Wed, 1 Aug 2018 09:18:05 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533136685.1369.4.camel@freebsd.org> Subject: Re: can't make installworld From: Ian Lepore To: Glen Barber , AN Cc: freebsd-current@freebsd.org Date: Wed, 01 Aug 2018 09:18:05 -0600 In-Reply-To: <20180801144153.GB96585@FreeBSD.org> References: <20180801144153.GB96585@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 15:18:13 -0000 On Wed, 2018-08-01 at 14:41 +0000, Glen Barber wrote: > On Wed, Aug 01, 2018 at 10:29:18AM -0400, AN wrote: > > > > FreeBSD BSD12 12.0-CURRENT FreeBSD 12.0-CURRENT #16 r335386: Tue > > Jun > > 19 19:57:51 EDT 2018 > > root@BSD12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL  amd64 > > > > # cat /etc/master.passwd | grep ntp > > ntpd:*:123:123::0:0:NTP Daemon:/var/db/ntp:/usr/sbin/nologin > > > > > > # cat /etc/group | grep ntp > > ntpd:*:123: > > > This is a particularly annoying problem since 20180719. > It's not a problem at all, we are just in one of the rare times when you actually have to follow the recommended update procedure exactly, without shortcuts. In particular, you cannot skip the pre-world "mergemaster -p" step as described in the handbook or at the bottom of UPDATING. -- Ian > > > > > > # svnlite info > > 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: 337003 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: manu > > Last Changed Rev: 337000 > > Last Changed Date: 2018-07-31 15:14:52 -0400 (Tue, 31 Jul 2018) > > > > > > For several days I have been trying to update the world without > > success.  In single user mode, trying to make installworld I get > > the > > following: > > > > > > > > > > > > > > > > > > > Installworld check > > ... > > Required tool true not found in path. > > > > > > Any idea how to fix this? > What does your $PATH contain? > > Glen > From owner-freebsd-current@freebsd.org Wed Aug 1 15:33:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69FDF1060DE8 for ; Wed, 1 Aug 2018 15:33:13 +0000 (UTC) (envelope-from a.n.us@ieee.org) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 0964879B8B for ; Wed, 1 Aug 2018 15:33:12 +0000 (UTC) (envelope-from a.n.us@ieee.org) Received: by mail-io0-x22a.google.com with SMTP id z19-v6so16414544ioh.4 for ; Wed, 01 Aug 2018 08:33:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=6mUeQfNOACJGOGJrTKtelhZ2gUoe7MkyPzxjHuyz9Ls=; b=HagcNdoO7SyyEnn8fsD5g2y/WM9v9OY2VEsV51BxSm1tPi57HFHZAHncL6c8rv86u6 xhcgM8piy5PSZks0/juNLy3IuszUo6pUvU+bAaxHfX7gd9FkgNvg5k6i6VRGORc9Z9SN hCvEYQNybwhebpw5RyO6M/xZ1ceOy+SDNetmBDlDES+//fLsS0uY/xa7kXppJEhqPN/C jWQd/gHOE4Xpd/dokSFNu1x/HhIoWwiCWWV4byBpitnsmFPxqrxxT349Sz5OI1Knv9J1 GPa6b/r4HjozmcEYYy5myN5PJXzM7LFfHYLHNDTfFB7OKbTKDCpUB/6y/PzFEogalFB5 ghWg== 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; bh=6mUeQfNOACJGOGJrTKtelhZ2gUoe7MkyPzxjHuyz9Ls=; b=E2KUmaxd9+02loeeNHB9jOXV5RgAf+5pqXkrXP84JRm+cv8quRXsOnpxyiKzzpM+4B FjI+/o1JFLNRjzcPx/B7qZK0PdTsOOa2brejpXeP+vsF3RZ+6dvbzffrOaFUWUY5bebH bHtOWRaebnu9zvg9fprUJ0xDzLd5w2Ew+MzcnCTUYMQQ3jVilmgNmClaYZ1vkfW5NMKe VmUYF+eZzMPd4aR8Bp9/HqGjNqEUeI2JOIaHboCR6qJQ/kZ6PxHgVkJ5bCb8xmGQVM8A x/PCHAbivHFkXVbppc7xg6biGUOiV2A/0Wgw79z9U47+L1Ty1U6OC9phdjFUuqzq4q4W 2Rgw== X-Gm-Message-State: AOUpUlFe3gwYKItMZUfYOSH8O04SS4aR1zIyKOkX1njPj0i50RT9rR1Q ShqQQn3J28BxETBxdRkAaoLfNPqSoli5H6LiNZbL/a5h X-Google-Smtp-Source: AAOMgpcKzJW6tRpCJ2gaFjnCM33qHAkUbbL21XFnVImfdO34fqVFmGD0NbqrLyts6JwVRthdTzWPLSPFHjBcC8BC0FE= X-Received: by 2002:a6b:cd8f:: with SMTP id d137-v6mr3765094iog.154.1533137592238; Wed, 01 Aug 2018 08:33:12 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:5919:0:0:0:0:0 with HTTP; Wed, 1 Aug 2018 08:32:31 -0700 (PDT) In-Reply-To: <20180801144912.GC96585@FreeBSD.org> References: <20180801144153.GB96585@FreeBSD.org> <20180801144912.GC96585@FreeBSD.org> From: AN Date: Wed, 1 Aug 2018 11:32:31 -0400 Message-ID: Subject: Re: can't make installworld To: Glen Barber , freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 15:33:13 -0000 Glen: On Wed, Aug 1, 2018 at 10:49 AM, Glen Barber wrote: > Hmm, gross. :( > > Was there a previous error during a prior installworld attempt? > > As a quick workaround regarding this particular binary missing, you > could: > > # make -C /usr/src/usr.bin/true install This worked and allowed installworld to finish successfully. > If that fails, please reply with the list in CC, as there may be > something more serious going on here. > > Glen > > On Wed, Aug 01, 2018 at 10:45:17AM -0400, AN wrote: >> Hey Glen: >> >> Thanks for the reply. >> >> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin >> >> On Wed, Aug 1, 2018 at 10:41 AM, Glen Barber wrote: >> > On Wed, Aug 01, 2018 at 10:29:18AM -0400, AN wrote: >> >> FreeBSD BSD12 12.0-CURRENT FreeBSD 12.0-CURRENT #16 r335386: Tue Jun >> >> 19 19:57:51 EDT 2018 >> >> root@BSD12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 >> >> >> >> # cat /etc/master.passwd | grep ntp >> >> ntpd:*:123:123::0:0:NTP Daemon:/var/db/ntp:/usr/sbin/nologin >> >> >> >> >> >> # cat /etc/group | grep ntp >> >> ntpd:*:123: >> >> >> > >> > This is a particularly annoying problem since 20180719. >> > >> >> >> >> # svnlite info >> >> 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: 337003 >> >> Node Kind: directory >> >> Schedule: normal >> >> Last Changed Author: manu >> >> Last Changed Rev: 337000 >> >> Last Changed Date: 2018-07-31 15:14:52 -0400 (Tue, 31 Jul 2018) >> >> >> >> >> >> For several days I have been trying to update the world without >> >> success. In single user mode, trying to make installworld I get the >> >> following: >> >> >> >> >>>Installworld check >> >> ... >> >> Required tool true not found in path. >> >> >> >> >> >> Any idea how to fix this? >> > >> > What does your $PATH contain? >> > >> > Glen >> > Thanks for your help and quick response. From owner-freebsd-current@freebsd.org Wed Aug 1 20:22:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECFD51068355 for ; Wed, 1 Aug 2018 20:22:02 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f171.google.com (mail-io0-f171.google.com [209.85.223.171]) (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 8D192860B6 for ; Wed, 1 Aug 2018 20:22:02 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f171.google.com with SMTP id w11-v6so17218256iob.2 for ; Wed, 01 Aug 2018 13:22:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=JLILBMA4SeTZiB4S/A1DARbftE0SdOcFSyajl1mVzDM=; b=LFsWgzsfKsy7lLFoMCLVR8COzdryJezdFtvP82imTKlVJqZHDvd3XDCZgbBxVyFur8 BZvgBhkfCZD4CkchGoO2tdaoe9x6hQ/vD5zOqtoqNBqex1e+iPf62ndv78Qi7faMwquW wDotDf/GYSMcQmfqdO9esevA3gNTX/FiB/CsqXgBilRY9y4RxDMlby50wDkpdsKDwqYU 2CclXD8Kw3gLmMddZ5ice55ztT+PGVVDP6/yW7rQkVBXQXZ2Vavk/MsetWLAy47nE4+O EC0mm9ueuD9cWNhSl45yzdhQmHUuSUKvTLxCkF6pHHW9XhNmbkRMsoE+jDWqo0LFCglk feDA== X-Gm-Message-State: AOUpUlGA+fhPgXDhCJFXNUVrYH0zHWoti5M++r/Amkvdc34bD6sM7Jz4 VV9KBkz1zBRn6cwIp8ZW0VtQ9/cj X-Google-Smtp-Source: AAOMgpdIc9MfRnuqqDxx716d1okHSNB2vrQRynBWNyS/Odrv8uB4qdi1RiHyRagiqO/L8xJcnPzreg== X-Received: by 2002:a5e:dc49:: with SMTP id s9-v6mr4590616iop.237.1533154505345; Wed, 01 Aug 2018 13:15:05 -0700 (PDT) Received: from mail-io0-f179.google.com (mail-io0-f179.google.com. [209.85.223.179]) by smtp.gmail.com with ESMTPSA id b15-v6sm128283itb.25.2018.08.01.13.15.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Aug 2018 13:15:05 -0700 (PDT) Received: by mail-io0-f179.google.com with SMTP id v26-v6so17196451iog.5 for ; Wed, 01 Aug 2018 13:15:05 -0700 (PDT) X-Received: by 2002:a6b:be46:: with SMTP id o67-v6mr4585215iof.143.1533154505019; Wed, 01 Aug 2018 13:15:05 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:7e0a:0:0:0:0:0 with HTTP; Wed, 1 Aug 2018 13:15:04 -0700 (PDT) In-Reply-To: References: From: Conrad Meyer Date: Wed, 1 Aug 2018 13:15:04 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers To: Johannes Lundberg Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 20:22:03 -0000 It seems deliberate, although the commit message does not call it out and the event is perhaps poorly named. The event currently indicates that the lid was closed. And the final registered eventhandler for the event calls ReqSleepState. The ReqSleepState routine, as well as the userspace ioctl that 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather than invoking the acpi sleep event), were introduced together in r170976. Best, Conrad On Wed, Aug 1, 2018 at 8:05 AM, Johannes Lundberg wrote: > Hi > > As the title says, callbacks registered with > EVENTHANDLER_REGISTER(acpi_sleep_event, .... > does not get called when calling acpiconf -s 3. > They do however, when suspending with lid or sleep button. > > Is this deliberate or an oversight? > > Cheers > _______________________________________________ > 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 Aug 1 21:49:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CBE0106A14A for ; Wed, 1 Aug 2018 21:49:02 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09E0D89B96; Wed, 1 Aug 2018 21:49:02 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id o18-v6so239420wmc.0; Wed, 01 Aug 2018 14:49:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VJsoTYW5cciU+nWA2ojgW0VMCh2FcgIW+S+MUtZCeQo=; b=NEII1f0hKrnGCltoprBlvbcBApAZIAtdx03xYeN0EVoDnS7nRqf0+dyGfOjb+LD2DE MoHsUdnkHA9TZhrvlnhQ7KwiaV8cjmquu3uVcufzemGR5OHej0gLTHQjEQtRljP2bMVY er61N6Y7TNUIZWn7V+JFMKI3p68V5tf9hRWbRxugjQgDhRCu2HX7GncajVpgRQFn752N Hvbd2HN9GyS2S9PpNALrbTvalSrLN5kii1f9H78rvCnTnRytQr4FrPwo8HGj1+ekUnTT S4TT0gz++4JbY3henlw55Klx7KHZFQDAiNi/ulshjQk0nOZ4NwVHrNuurjlgVSNf99ny MeFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VJsoTYW5cciU+nWA2ojgW0VMCh2FcgIW+S+MUtZCeQo=; b=sddPneHPqM1ZfIa0jXUrhKYGByy+FhczQ1D57RHU1uLY+MFA+abOkUJ6rS2EJrT1iw tDs8NHONazWVyetabhmHAhBE4U6OXkO+JVaXY9R0gPALrdu1ADn1N9zC3l1BwSSd3Tro wEQv5vSqzRc4C6LkSARU4b7hsFMoUU9TRie7a6b+AZKSk7DZwyuYMpBLebxrG3mcuZVR eyXM1TfEcdNjObLTXnan/P6ENpsrT+63OGYTPCg3dPtv4oEb7WsnUknuie8Hq9FPy3zj witfpc11I9EvnWw+cSf58PNV+4T/ot2fpUSxrpA2ZAH8qLTiFBIeYMsJIScg/aPwoH3z EnDw== X-Gm-Message-State: AOUpUlFqzuuPklhJheOEQnXYTdFGZobiFQ4BiSexVDVLLtKqGhunx9Pn SOLT4LpOOXjtiioAddx4A24jUtVq5QlH09T+GVYUhHEy X-Google-Smtp-Source: AAOMgpcmEwDjP80Fm0we7hZxpLgfRjg1+YP3/tRxouNhewhchJpqy8RoqzYBBKE7G53hrRdO7wKR5BUPhQ+scA1A9wA= X-Received: by 2002:a1c:c912:: with SMTP id f18-v6mr155961wmb.73.1533160140889; Wed, 01 Aug 2018 14:49:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Wed, 1 Aug 2018 22:48:23 +0100 Message-ID: Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers To: cem@freebsd.org Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 21:49:02 -0000 On Wed, Aug 1, 2018 at 9:15 PM Conrad Meyer wrote: > It seems deliberate, although the commit message does not call it out > and the event is perhaps poorly named. The event currently indicates > that the lid was closed. And the final registered eventhandler for > the event calls ReqSleepState. > > The ReqSleepState routine, as well as the userspace ioctl that > 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather > than invoking the acpi sleep event), were introduced together in > r170976. > > Unless there's a way of calling suspend properly from the cli (zzz uses acpiconf...) maybe something like this makes more sense to get the same behavior on for example lid close as zzz or acpiconf -s 3? (untested) diff --git a/sys/dev/acpica/acpi.c b/sys/dev/acpica/acpi.c index c1bfd880c89..87b506d6bf5 100644 --- a/sys/dev/acpica/acpi.c +++ b/sys/dev/acpica/acpi.c @@ -3700,7 +3700,8 @@ acpiioctl(struct cdev *dev, u_long cmd, caddr_t addr, int flag, struct thread *t case ACPIIO_REQSLPSTATE: state = *(int *)addr; if (state != ACPI_STATE_S5) - return (acpi_ReqSleepState(sc, state)); + return ACPI_SUCCESS(AcpiOsExecute(OSL_NOTIFY_HANDLER, + acpi_invoke_sleep_eventhandler, &state)) ? 0 : ENXIO; device_printf(sc->acpi_dev, "power off via acpi ioctl not supported\n"); error = EOPNOTSUPP; break; > Best, > Conrad > > On Wed, Aug 1, 2018 at 8:05 AM, Johannes Lundberg > wrote: > > Hi > > > > As the title says, callbacks registered with > > EVENTHANDLER_REGISTER(acpi_sleep_event, .... > > does not get called when calling acpiconf -s 3. > > They do however, when suspending with lid or sleep button. > > > > Is this deliberate or an oversight? > > > > Cheers > > _______________________________________________ > > 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 Aug 1 22:00:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB252106A6FE for ; Wed, 1 Aug 2018 22:00:35 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6ECC78A3E7; Wed, 1 Aug 2018 22:00:35 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id s12-v6so267513wmc.0; Wed, 01 Aug 2018 15:00:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jG81iVeJvAIaZ9DeYF6SyH1Boi3s/cp5TYO4tFXc/vI=; b=KezBZRQ8W0FlLYo84fKf6CW7K1P7tSMss9EBiBc+2QZ4XbZNg5Qd4rcgecLZ6plVJv nGzilAIU7h4Av8OnbkTFFe0JO458NsLzB87oF5RZJW2mG2C3UiYa0nImm6DkvOJBfGei iEZOV82kiHJ2qDWMIiA9pIuqkWKfNiHhICCSCPqXcpaOj3KOHxF+IEFyflspNCCksB+G vu5UVnylsu32pj6h8K8JMvGHsGnWbX9fgPTa5ZRuIp2TIqn+KerfVaTnFrXeq3u617K1 72L0aWj1/Gj7Cp0aH6CeqP3tJP/iymblexN6nXWTLsBqItyaJrl56v0lA8WqKPdsDRmR MVbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jG81iVeJvAIaZ9DeYF6SyH1Boi3s/cp5TYO4tFXc/vI=; b=sZPAuVJoXbpf/+3RV+vhbDQURSIc1BLlYP6Fj7ol7dCji8qzePHCPsQWf8Ztpa0zZ0 ESCTAw8q8W6hyNl7vHP5IwCjnRsln+3y8oHGg67AEzvfn9dbyfn68vtocycNPP8HlPUd Jtu54uYGIiLbnG5q9H8Srd1OlXAy2js/sHHEN7H+0ad52rOq0atFxefYi6DW3OReBIOd 8vznHm2RpzmisyPvPc49eMEYwHzT27+9hFMzwksOn18yg9BQwZjxRlLq85U/OfUq2cjo qzocamtKeRFXVek64HOO1jjE6Y3viJ1JAhSNB7M0LnBgN/xprJ5sLdBgsl9COVNeVgXK Dl5A== X-Gm-Message-State: AOUpUlEWoNEoneBM8baJi2F6CrRucq5oy5gqjBnBTLltIlGacfvH2bzo 9ZTmawrXeWMIR6JRBXmoxhoZ3IUxJk9gxd9Q2pjgqQ== X-Google-Smtp-Source: AAOMgpf4kdjWPF9OHf5L3Hn7R8/n5PquBQhUMoZJqcdeTuWU65ZC5WxD0s94SXb16NFS0uTxpjBkIbP0R/c3KzGAq4U= X-Received: by 2002:a1c:af53:: with SMTP id y80-v6mr159129wme.55.1533160834282; Wed, 01 Aug 2018 15:00:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Wed, 1 Aug 2018 23:00:23 +0100 Message-ID: Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers To: cem@freebsd.org Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 22:00:36 -0000 On Wed, Aug 1, 2018 at 22:55 Conrad Meyer wrote: > ReqSleepState is the routine that takes care of suspend, not the > eventhandler. I'm not sure what difference the proposed change is > supposed to make. Listeners to acpi_sleep_event don=E2=80=99t get the event when suspending w= ith acpiconf (but they do when suspending via lid or sleep button). I think one would expect the same behavior when suspending via command line or physical switch. > > Best, > Conrad > > On Wed, Aug 1, 2018 at 2:48 PM, Johannes Lundberg > wrote: > > > > > > On Wed, Aug 1, 2018 at 9:15 PM Conrad Meyer wrote: > >> > >> It seems deliberate, although the commit message does not call it out > >> and the event is perhaps poorly named. The event currently indicates > >> that the lid was closed. And the final registered eventhandler for > >> the event calls ReqSleepState. > >> > >> The ReqSleepState routine, as well as the userspace ioctl that > >> 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather > >> than invoking the acpi sleep event), were introduced together in > >> r170976. > >> > > > > Unless there's a way of calling suspend properly from the cli (zzz uses > > acpiconf...) maybe something like this makes more sense to get the same > > behavior on for example lid close as zzz or acpiconf -s 3? (untested) > > > > diff --git a/sys/dev/acpica/acpi.c b/sys/dev/acpica/acpi.c > > index c1bfd880c89..87b506d6bf5 100644 > > --- a/sys/dev/acpica/acpi.c > > +++ b/sys/dev/acpica/acpi.c > > @@ -3700,7 +3700,8 @@ acpiioctl(struct cdev *dev, u_long cmd, caddr_t > addr, > > int flag, struct thread *t > > case ACPIIO_REQSLPSTATE: > > state =3D *(int *)addr; > > if (state !=3D ACPI_STATE_S5) > > - return (acpi_ReqSleepState(sc, state)); > > + return ACPI_SUCCESS(AcpiOsExecute(OSL_NOTIFY_HANDLER, > > + acpi_invoke_sleep_eventhandler, &state)) ? 0 : > > ENXIO; > > device_printf(sc->acpi_dev, "power off via acpi ioctl not > > supported\n"); > > error =3D EOPNOTSUPP; > > break; > > > > > >> > >> Best, > >> Conrad > >> > >> On Wed, Aug 1, 2018 at 8:05 AM, Johannes Lundberg > >> wrote: > >> > Hi > >> > > >> > As the title says, callbacks registered with > >> > EVENTHANDLER_REGISTER(acpi_sleep_event, .... > >> > does not get called when calling acpiconf -s 3. > >> > They do however, when suspending with lid or sleep button. > >> > > >> > Is this deliberate or an oversight? > >> > > >> > Cheers > >> > _______________________________________________ > >> > 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 Aug 1 22:02:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BF4F106A8E3 for ; Wed, 1 Aug 2018 22:02:43 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f65.google.com (mail-it0-f65.google.com [209.85.214.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BCFAA8A77F for ; Wed, 1 Aug 2018 22:02:42 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f65.google.com with SMTP id g141-v6so380281ita.4 for ; Wed, 01 Aug 2018 15:02: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:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=sNWbDk4z+eP7pBcACPa5sojtvjkXqf1uXK0eshEUHQY=; b=pvmLT5z1CDt0Gx2HZ+hX1KNTf5tnkyHjoN8MoOjLGy+wB72GB1aTCoBtoUWWNzWxYP yLWxgpevIDLGJ2u6OqIHFYvFHtNpmecgsSh4GXyt/Ll7IY1KsanVdljtbaYaA6uUZUHA buv/guW264fqbkA0LqC+G6PIWXwx9h88ZqF1dDmRdIQaaFPUbkXOxrvLR18ofW8P0I2I cxoUfo3R13Sij9T+xCbuOodSg643NpNvA7Chcv5hm5pbZBHLQWAUIuNVVuqY6FfvxvYo 1p0esvOvbUo9NpAX24EHH4y3LF9ZZc0df+scfDu8oBxB/0LUA1J3EHXc/FjyOvJiVgEk 5Xcw== X-Gm-Message-State: AOUpUlE9V3pw1K7kpNgwQjkv6BnxbnTUFssg5OwTv6zpQ+i6UBT9Y5jD Mm431nroS3zYe5WuCW6vYs9BHBWZ X-Google-Smtp-Source: AAOMgpedI3AZYgr9mAv9ysEWOTwy/t3vpwu9dPdUlEmkBbtOHypCEF6Ll3JXSeR/h1e11zCbBLQfFw== X-Received: by 2002:a02:1103:: with SMTP id 3-v6mr110191jaf.144.1533160533598; Wed, 01 Aug 2018 14:55:33 -0700 (PDT) Received: from mail-io0-f176.google.com (mail-io0-f176.google.com. [209.85.223.176]) by smtp.gmail.com with ESMTPSA id a79-v6sm87617itc.33.2018.08.01.14.55.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Aug 2018 14:55:33 -0700 (PDT) Received: by mail-io0-f176.google.com with SMTP id q19-v6so83177ioh.11 for ; Wed, 01 Aug 2018 14:55:33 -0700 (PDT) X-Received: by 2002:a6b:4e04:: with SMTP id c4-v6mr107209iob.19.1533160533251; Wed, 01 Aug 2018 14:55:33 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:7e0a:0:0:0:0:0 with HTTP; Wed, 1 Aug 2018 14:55:32 -0700 (PDT) In-Reply-To: References: From: Conrad Meyer Date: Wed, 1 Aug 2018 14:55:32 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers To: Johannes Lundberg Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 22:02:43 -0000 ReqSleepState is the routine that takes care of suspend, not the eventhandler. I'm not sure what difference the proposed change is supposed to make. Best, Conrad On Wed, Aug 1, 2018 at 2:48 PM, Johannes Lundberg wrote: > > > On Wed, Aug 1, 2018 at 9:15 PM Conrad Meyer wrote: >> >> It seems deliberate, although the commit message does not call it out >> and the event is perhaps poorly named. The event currently indicates >> that the lid was closed. And the final registered eventhandler for >> the event calls ReqSleepState. >> >> The ReqSleepState routine, as well as the userspace ioctl that >> 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather >> than invoking the acpi sleep event), were introduced together in >> r170976. >> > > Unless there's a way of calling suspend properly from the cli (zzz uses > acpiconf...) maybe something like this makes more sense to get the same > behavior on for example lid close as zzz or acpiconf -s 3? (untested) > > diff --git a/sys/dev/acpica/acpi.c b/sys/dev/acpica/acpi.c > index c1bfd880c89..87b506d6bf5 100644 > --- a/sys/dev/acpica/acpi.c > +++ b/sys/dev/acpica/acpi.c > @@ -3700,7 +3700,8 @@ acpiioctl(struct cdev *dev, u_long cmd, caddr_t addr, > int flag, struct thread *t > case ACPIIO_REQSLPSTATE: > state = *(int *)addr; > if (state != ACPI_STATE_S5) > - return (acpi_ReqSleepState(sc, state)); > + return ACPI_SUCCESS(AcpiOsExecute(OSL_NOTIFY_HANDLER, > + acpi_invoke_sleep_eventhandler, &state)) ? 0 : > ENXIO; > device_printf(sc->acpi_dev, "power off via acpi ioctl not > supported\n"); > error = EOPNOTSUPP; > break; > > >> >> Best, >> Conrad >> >> On Wed, Aug 1, 2018 at 8:05 AM, Johannes Lundberg >> wrote: >> > Hi >> > >> > As the title says, callbacks registered with >> > EVENTHANDLER_REGISTER(acpi_sleep_event, .... >> > does not get called when calling acpiconf -s 3. >> > They do however, when suspending with lid or sleep button. >> > >> > Is this deliberate or an oversight? >> > >> > Cheers >> > _______________________________________________ >> > 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 Aug 1 22:24:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F318B106B015 for ; Wed, 1 Aug 2018 22:24:48 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f65.google.com (mail-it0-f65.google.com [209.85.214.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B9728B389 for ; Wed, 1 Aug 2018 22:24:48 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f65.google.com with SMTP id s7-v6so478106itb.4 for ; Wed, 01 Aug 2018 15:24:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=laZsIh0SSchmqwEQRUlZCfCFxbJF1SIZzPikQRwwANs=; b=kbLG2IovrdWSFl152Qj3USQrd5y67++14FlzdcZbxcGsdzYotkSMVLGSV5BM2js9M9 AbJv/KhoeZCWJR8MLrDyRoAQY91aYbiJrUrAvOb6tIRpDkV1r6viMmZHb4mIS6k38tBf jPvx36f46M3szc7E5JCeVRP0ObNk9TSbJS0VOVD5f79NPZAaUaBDavIG1UlSI0bz/2Gp 8KyvviIUZReHxlwHoziWo2FcgR9Lh3BvhedO5XBea1YIBSayTs3SKtH5jb2M225lMwTa HWI0WQktfLmZL1g6QL3sVVMpq1BgQDsZ/SK32vBdgG/rblzph4auLQaBTAgozDD7c1th a5uw== X-Gm-Message-State: AOUpUlGNGeqANdIIDGNHSEL/0toA2SYck1+HAQyqV8OK0a2Sny9QSXmw eB9ln8cySzUXzG+o6tKd1HtZtsri X-Google-Smtp-Source: AAOMgpcj3Snzj+zuLK0/ElMBcJCIZ/hbjTemK+IgYm9h/2vUaMqL3T0L3SL8s/+prFhqcArMNMQeaQ== X-Received: by 2002:a24:4f52:: with SMTP id c79-v6mr349004itb.36.1533161855950; Wed, 01 Aug 2018 15:17:35 -0700 (PDT) Received: from mail-it0-f44.google.com (mail-it0-f44.google.com. [209.85.214.44]) by smtp.gmail.com with ESMTPSA id b81-v6sm5785itg.6.2018.08.01.15.17.35 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Aug 2018 15:17:35 -0700 (PDT) Received: by mail-it0-f44.google.com with SMTP id d10-v6so452544itj.5 for ; Wed, 01 Aug 2018 15:17:35 -0700 (PDT) X-Received: by 2002:a24:be8f:: with SMTP id i137-v6mr326360itf.61.1533161855537; Wed, 01 Aug 2018 15:17:35 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:7e0a:0:0:0:0:0 with HTTP; Wed, 1 Aug 2018 15:17:34 -0700 (PDT) In-Reply-To: References: From: Conrad Meyer Date: Wed, 1 Aug 2018 15:17:34 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers To: Johannes Lundberg Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Aug 2018 22:24:49 -0000 I don't understand the concern. There is only one listener to the event and it just invokes ReqSleepState, which is responsible for performing all suspend behavior. The behavior is identical between lid close and acpiconf. On Wed, Aug 1, 2018 at 3:00 PM, Johannes Lundberg wrot= e: > > > On Wed, Aug 1, 2018 at 22:55 Conrad Meyer wrote: >> >> ReqSleepState is the routine that takes care of suspend, not the >> eventhandler. I'm not sure what difference the proposed change is >> supposed to make. > > > Listeners to acpi_sleep_event don=E2=80=99t get the event when suspending= with > acpiconf (but they do when suspending via lid or sleep button). > > I think one would expect the same behavior when suspending via command li= ne > or physical switch. > > >> >> >> Best, >> Conrad >> >> On Wed, Aug 1, 2018 at 2:48 PM, Johannes Lundberg >> wrote: >> > >> > >> > On Wed, Aug 1, 2018 at 9:15 PM Conrad Meyer wrote: >> >> >> >> It seems deliberate, although the commit message does not call it out >> >> and the event is perhaps poorly named. The event currently indicates >> >> that the lid was closed. And the final registered eventhandler for >> >> the event calls ReqSleepState. >> >> >> >> The ReqSleepState routine, as well as the userspace ioctl that >> >> 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather >> >> than invoking the acpi sleep event), were introduced together in >> >> r170976. >> >> >> > >> > Unless there's a way of calling suspend properly from the cli (zzz use= s >> > acpiconf...) maybe something like this makes more sense to get the sam= e >> > behavior on for example lid close as zzz or acpiconf -s 3? (untested) >> > >> > diff --git a/sys/dev/acpica/acpi.c b/sys/dev/acpica/acpi.c >> > index c1bfd880c89..87b506d6bf5 100644 >> > --- a/sys/dev/acpica/acpi.c >> > +++ b/sys/dev/acpica/acpi.c >> > @@ -3700,7 +3700,8 @@ acpiioctl(struct cdev *dev, u_long cmd, caddr_t >> > addr, >> > int flag, struct thread *t >> > case ACPIIO_REQSLPSTATE: >> > state =3D *(int *)addr; >> > if (state !=3D ACPI_STATE_S5) >> > - return (acpi_ReqSleepState(sc, state)); >> > + return ACPI_SUCCESS(AcpiOsExecute(OSL_NOTIFY_HANDLER, >> > + acpi_invoke_sleep_eventhandler, &state)) ? 0 : >> > ENXIO; >> > device_printf(sc->acpi_dev, "power off via acpi ioctl not >> > supported\n"); >> > error =3D EOPNOTSUPP; >> > break; >> > >> > >> >> >> >> Best, >> >> Conrad >> >> >> >> On Wed, Aug 1, 2018 at 8:05 AM, Johannes Lundberg >> >> wrote: >> >> > Hi >> >> > >> >> > As the title says, callbacks registered with >> >> > EVENTHANDLER_REGISTER(acpi_sleep_event, .... >> >> > does not get called when calling acpiconf -s 3. >> >> > They do however, when suspending with lid or sleep button. >> >> > >> >> > Is this deliberate or an oversight? >> >> > >> >> > Cheers >> >> > _______________________________________________ >> >> > 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 Aug 2 04:55:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 124F51056E1D; Thu, 2 Aug 2018 04:55:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACE3672703; Thu, 2 Aug 2018 04:55:27 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id E5CC21CB3; Thu, 2 Aug 2018 04:55:20 +0000 (UTC) Date: Thu, 2 Aug 2018 04:55:19 +0000 From: Mark Linimon To: Miroslav Lachman <000.fbsd@quip.cz> Cc: tech-lists , freebsd-ports@freebsd.org, freebsd-questions@freebsd.org, FreeBSD Current Subject: Re: how to make ports not install xorg or dependencies Message-ID: <20180802045518.GA13138@lonesome.com> References: <703ec31c-a798-68c6-c9fa-4d73bce50be2@zyxst.net> <8265d700-9f0f-d2a5-a2c8-96ad4dd2e8b2@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8265d700-9f0f-d2a5-a2c8-96ad4dd2e8b2@quip.cz> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 04:55:28 -0000 On Tue, Jul 31, 2018 at 01:13:31PM +0200, Miroslav Lachman wrote: > As Guido Falsi already said it is not guaranteed that you will not > have ports with some X libs, because some ports does not have option > to disable X11 dependencies. IMHO those ports have bugs. mcl From owner-freebsd-current@freebsd.org Thu Aug 2 05:20:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 438B81058268 for ; Thu, 2 Aug 2018 05:20:19 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-pg1-f173.google.com (mail-pg1-f173.google.com [209.85.215.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3316738DF; Thu, 2 Aug 2018 05:20:18 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-pg1-f173.google.com with SMTP id y5-v6so563449pgv.1; Wed, 01 Aug 2018 22:20:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6hdGdfhKqeBOxJnJ7bBPrqXtHk7IcbuUtSBAQ2qFdCA=; b=Il+IbrRR3KZJDSVguGlt03bmeFx//13ukZe82OpexFihhmL7gVHs9rfDh6Tt81oZme cimncF+AC9f6hf9cMYBz1zsDxyV9UIeNKMA+mxVFkdDFs2NeDzwVo6Jht4kJ68+yVoe6 eObOWX+i8OtEp+6NK5zAHiTf2Ay1EU1xK6HGPdU8vWFdo7H2H9V6kFLxrHgFL+/wADge Av1/ffvoIbnUo0yLaHWLsODo4bVw/3k1JYrvT5AslnG3Sc2ECzp9m8EEkD1BLwGYH9+4 RCDqrb+OHhMNfohlG8xHXexPNM+eWwA9FkiDeD0rn2tXGIESWY5mq7sYqjycdj+ZgwjV KevQ== X-Gm-Message-State: AOUpUlG1os42XK63wE3kMo20P5f5Y3pWLfMT6k+1nzXN18mjk4Xgq+lj fe+c1clerR83vqENuKxYy1RQ7l8M X-Google-Smtp-Source: AAOMgpeX0fvAA8P25kaNkoO/OW4n9/jjotqE9s80CG7ymKra9sDJjimRSR660aaOx7C6ZLuu3V8B6Q== X-Received: by 2002:a62:b917:: with SMTP id z23-v6mr1355202pfe.131.1533187212297; Wed, 01 Aug 2018 22:20:12 -0700 (PDT) Received: from [192.168.1.36] (broadband-82-140-196-15.atc.tvcom.ru. [82.140.196.15]) by smtp.googlemail.com with ESMTPSA id c85-v6sm1839858pfd.110.2018.08.01.22.20.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Aug 2018 22:20:11 -0700 (PDT) Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers To: cem@freebsd.org, Johannes Lundberg Cc: freebsd-current References: From: Andriy Gapon Message-ID: Date: Thu, 2 Aug 2018 08:20:08 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: 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.27 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, 02 Aug 2018 05:20:19 -0000 On 02/08/2018 01:17, Conrad Meyer wrote: > I don't understand the concern. There is only one listener to the > event and it just invokes ReqSleepState, which is responsible for > performing all suspend behavior. The behavior is identical between > lid close and acpiconf. Unless someone is adding a new listener for that event. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu Aug 2 05:27:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10F5F1058743 for ; Thu, 2 Aug 2018 05:27:23 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8197373E02; Thu, 2 Aug 2018 05:27:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x42e.google.com with SMTP id g6-v6so803698wrp.0; Wed, 01 Aug 2018 22:27:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j587P3SkEL7sa9CM1D5uaV0F93UgmF0MQWPas1vsCRE=; b=VbxpWNFk2cNxYA0PEHicCcubFQt35XzR7BI7Z7K0Ygb3BtEfsCfyaLZxlyeSv2HVDn L2q0HKn32Zii7CO0faUhg0pePw3QFpfROSbprjzsiXtJnKsQpnHE8ATLNSoVMbmVKfbm O9g8+EwcpJjaELrY92iPN3bwAtM3t2PAPG3zztt+QBIwR+h5UGVKk0kSkGhvGqJXWsCa PkT+re1qj2cemmVY7QJAsaAqm/Yzze6CbxoUT6rc0GHO/GSkRJEcZvNnmNGWZD12Oca6 SxfhhUqpRqlrFToOeujuhiM6D+GJjOibqjJCejgGgP1uhZ6sVfM3tayMhAOV2AbCok3P RlRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j587P3SkEL7sa9CM1D5uaV0F93UgmF0MQWPas1vsCRE=; b=Gz4+8Sfu/z951Hl2inZCkWhB02TtsFsb2PL3/7m7VERCeXbhdn4rYyPahocz9LC2K+ B7Gevko9oAJo8GQiAsHmQ/8dw/zJ1JCA71NT9JYiIkt48Ve/+9H7ck1jkh5pSEHWfaqW M8MlPvrxAjAPEtSv0zoQKmyn7t+CfNoJNnB5ho8iGXrkljc2/W8QxNrduuKIu8V8jXls QjhVsueIrKKo4CYaqz6ava35EvPHXpI+rGGbUFcwx9Tn4RDRmkYTVXnAQ5EyIyQg/D+/ SaLoaljIvmkaBBDouEoF5vuMmSU89ItNJQ34XA7sKcsMMkTwiayvx3qkhVxkESY0Hu+1 uUjg== X-Gm-Message-State: AOUpUlG6Vj7eLJr7/Qkf7qu74enbh2mikYB/oiSz0/FCStC4Cil1OJKV Z9bS/lHb0NUAFZLUnGp4knoMoKe7PmrLlDNyhJR6BA== X-Google-Smtp-Source: AAOMgpeH89lR8lhQpTfMrW+LKb3XmAB1p4Npq193ZbucXQziF0H8XasrlmPQKzHKNE9ByOZYh51J92Bdiwqk+rJXAUI= X-Received: by 2002:a5d:40c4:: with SMTP id b4-v6mr708913wrq.133.1533187641201; Wed, 01 Aug 2018 22:27:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Thu, 2 Aug 2018 06:27:10 +0100 Message-ID: Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers To: Andriy Gapon Cc: cem@freebsd.org, freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 05:27:23 -0000 On Thu, Aug 2, 2018 at 06:20 Andriy Gapon wrote: > On 02/08/2018 01:17, Conrad Meyer wrote: > > I don't understand the concern. There is only one listener to the > > event and it just invokes ReqSleepState, which is responsible for > > performing all suspend behavior. The behavior is identical between > > lid close and acpiconf. > > Unless someone is adding a new listener for that event. > Exactly my point. > -- > Andriy Gapon > From owner-freebsd-current@freebsd.org Thu Aug 2 12:09:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E0EC10651CD; Thu, 2 Aug 2018 12:09:04 +0000 (UTC) (envelope-from timo.voelker@fh-muenster.de) Received: from mail.fh-muenster.de (mail.fh-muenster.de [212.201.120.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.fh-muenster.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B0BD685220; Thu, 2 Aug 2018 12:09:03 +0000 (UTC) (envelope-from timo.voelker@fh-muenster.de) Received: from fhad-ex13.fhad.fh-muenster.de (unknown [10.41.11.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.fh-muenster.de (Postfix) with ESMTPS id BB116284728; Thu, 2 Aug 2018 14:08:56 +0200 (CEST) Received: from fhad-ex13.fhad.fh-muenster.de (10.41.11.26) by fhad-ex13.fhad.fh-muenster.de (10.41.11.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1415.2; Thu, 2 Aug 2018 14:08:56 +0200 Received: from fhad-ex13.fhad.fh-muenster.de ([fe80::d9a6:349d:aadc:72e6]) by fhad-ex13.fhad.fh-muenster.de ([fe80::d9a6:349d:aadc:72e6%5]) with mapi id 15.01.1415.002; Thu, 2 Aug 2018 14:08:56 +0200 From: =?utf-8?B?VGltbyBWw7Zsa2Vy?= To: "freebsd-hackers@freebsd.org" CC: "freebsd-current@freebsd.org" Subject: Re: Unable to UEFI boot 11.2 via pxeboot Thread-Topic: Unable to UEFI boot 11.2 via pxeboot Thread-Index: AQHUKMhMn24QMJWRqkeXKQYwbojdqqSsQBQA Date: Thu, 2 Aug 2018 12:08:56 +0000 Message-ID: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> References: In-Reply-To: Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.40.10.31] Content-Type: multipart/signed; boundary="Apple-Mail=_6E682B83-9F17-4551-B00B-26D7F1CF3F3F"; protocol="application/pkcs7-signature"; micalg=sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 12:09:04 -0000 --Apple-Mail=_6E682B83-9F17-4551-B00B-26D7F1CF3F3F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 It seems this issue is related to current as well. I did a quick test = and got this output, while I tried to (pxe)boot FreeBSD current (without = a USB stick plugged in) https://ibb.co/no8Fve Best regards Timo > On 31. Jul 2018, at 14:16, Timo V=C3=B6lker = wrote: >=20 > Hi, >=20 > I'm unable to boot up the amd64 11.2 via pxeboot using UEFI on a Dell = PowerEdge R430. I get this output >=20 > https://ibb.co/h5ntuT >=20 > If I press a key to interrupt reboot, I get to the OK prompt. If I = enter lsdev -v, it prints nothing more than "net devices:". The variable = currdev is not set (show currdev prints variable 'currdev' not found). I = configured pxeboot to be the one and only boot medium in BIOS setup.=20 >=20 > However, I found a workaround that works for me. If I put an (empty) = USB stick in a USB port of the PowerEdge, it successfully boots via = pxeboot (which is still the one and only configured boot medium). I then = get this output >=20 > https://ibb.co/mU8SM8 >=20 > With FreeBSD 11.1 pxeboot worked on the Dell PowerEdge R430, even = without a USB stick plugged in. I couldn't test this with FreeBSD = 12-current. Hope this helps anyway to find an open issue. >=20 > I found this thread which seems to be related. >=20 > = https://lists.freebsd.org/pipermail/freebsd-current/2018-July/070082.html >=20 > Thanks, >=20 > Timo --Apple-Mail=_6E682B83-9F17-4551-B00B-26D7F1CF3F3F Content-Disposition: attachment; filename="smime.p7s" Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQsDCCBRIw ggP6oAMCAQICCQDjC9X4ryXZgTANBgkqhkiG9w0BAQsFADCBgjELMAkGA1UEBhMCREUxKzApBgNV BAoMIlQtU3lzdGVtcyBFbnRlcnByaXNlIFNlcnZpY2VzIEdtYkgxHzAdBgNVBAsMFlQtU3lzdGVt cyBUcnVzdCBDZW50ZXIxJTAjBgNVBAMMHFQtVGVsZVNlYyBHbG9iYWxSb290IENsYXNzIDIwHhcN MTYwMjIyMTMzODIyWhcNMzEwMjIyMjM1OTU5WjCBlTELMAkGA1UEBhMCREUxRTBDBgNVBAoTPFZl cmVpbiB6dXIgRm9lcmRlcnVuZyBlaW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBW LjEQMA4GA1UECxMHREZOLVBLSTEtMCsGA1UEAxMkREZOLVZlcmVpbiBDZXJ0aWZpY2F0aW9uIEF1 dGhvcml0eSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAy2DX/2ahQc3S+oeXinOr mU3qZzlaoWCARxVOjJWy5c/O01dLjc74VmwVVXYH6kb9yANFYz5w1KtUgLEjnL43KKkJ/wVdGA/E mJk3syD2ZngXh8KdDsxKMucWna4OjSl5BwAgVNwVX0qW13i2NNPBdLWd6b/Ad03qvVkH4FovbDyl ANw1vWUNj38ybfJaaktiAe6sODRZRTZJBdp4ymptW8CBaxHM0jyoi/hxGso74oDdFrRneos26k6R KT2zUVytqAy+nTTj0Q0Xg3XEOR6wlAsS8dVpjiX0uD0rv8COwx47pb9VEKsqrheXXjPOyPP0CQfj AoYxRmsBxRAMEcdZ6QIDAQABo4IBdDCCAXAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBST49gy JtrV8UqlkUrg6kviogzP4TAfBgNVHSMEGDAWgBS/WSA2AHmgoCJrjNXyYdK4LMuCSjASBgNVHRMB Af8ECDAGAQH/AgECMDMGA1UdIAQsMCowDwYNKwYBBAGBrSGCLAEBBDANBgsrBgEEAYGtIYIsHjAI BgZngQwBAgIwTAYDVR0fBEUwQzBBoD+gPYY7aHR0cDovL3BraTAzMzYudGVsZXNlYy5kZS9ybC9U ZWxlU2VjX0dsb2JhbFJvb3RfQ2xhc3NfMi5jcmwwgYYGCCsGAQUFBwEBBHoweDAsBggrBgEFBQcw AYYgaHR0cDovL29jc3AwMzM2LnRlbGVzZWMuZGUvb2NzcHIwSAYIKwYBBQUHMAKGPGh0dHA6Ly9w a2kwMzM2LnRlbGVzZWMuZGUvY3J0L1RlbGVTZWNfR2xvYmFsUm9vdF9DbGFzc18yLmNlcjANBgkq hkiG9w0BAQsFAAOCAQEAhwv/PgKbZchWLdY7mpiLcU/auimqIflGLvWypA+uETh5OLMOdLp2XZ7o GIKWYttMM+jd+WrfMr0sTEdgVX/ndGu0LIPYeWu2t01QC2YHte2zl63q7n8w5pn9IuJyTT6EW+75 z5nqf9dSOS6smABEfmk7v3Xu0As7Gs3l9w8ibEeE9qVHoP3QGjR9rdI9d7Pu9NdN/8Po5ZJPWT6Q RxBKsIVYwG9/+K7tCEKeHtTfFC5Nj7yelMPn7fYY+DxJ5yaopzbYLN4izYuC2Nl44lUSozuHRLYR C9UMUq9pjA8G39CiU4tXmHvP/Qck9Py9w/1KkgKXG/K3ts9lihqitXIZOTCCBawwggSUoAMCAQIC BxtjutAeLD0wDQYJKoZIhvcNAQELBQAwgZUxCzAJBgNVBAYTAkRFMUUwQwYDVQQKEzxWZXJlaW4g enVyIEZvZXJkZXJ1bmcgZWluZXMgRGV1dHNjaGVuIEZvcnNjaHVuZ3NuZXR6ZXMgZS4gVi4xEDAO BgNVBAsTB0RGTi1QS0kxLTArBgNVBAMTJERGTi1WZXJlaW4gQ2VydGlmaWNhdGlvbiBBdXRob3Jp dHkgMjAeFw0xNjA1MjQxMTM4NDBaFw0zMTAyMjIyMzU5NTlaMIGNMQswCQYDVQQGEwJERTFFMEMG A1UECgw8VmVyZWluIHp1ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0 emVzIGUuIFYuMRAwDgYDVQQLDAdERk4tUEtJMSUwIwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJ c3N1aW5nIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnTt5HEfeH4bLxmnXEJ45 19miMNtyHAV/KV9LaPGtGdZM4WsbsQt/oavge4uL2C3Obog6EO5X5R5/BFE267pwbWOgvpYuQOHR g0xmPRxkaeWbpK1yrmg5UYd5zBfTri9dY3FLOXrrQqeXkGkFv5D/pEBwvQPnv54YiB+fmYhNDkeN SF9lmRDS2SpJ7cG5LR2fEssV0z9/HlQvOq6TV6d+eMrVSuIa5e1BfVNfyLMq9YowrO0XBSQ/tqAL B/1NGpoDUqA2nN4kh2Xk5/rHlnMkFM3Q6BtonhhZrnZ+99EKeDyHS7A3z1PKOjgQ88tHbYxkPTxa RUq6yoB8uPPnp0xMzQIDAQABo4ICBTCCAgEwEgYDVR0TAQH/BAgwBgEB/wIBATAOBgNVHQ8BAf8E BAMCAQYwKQYDVR0gBCIwIDANBgsrBgEEAYGtIYIsHjAPBg0rBgEEAYGtIYIsAQEEMB0GA1UdDgQW BBRrOpiL+fJTidrgrbIyHgkf6Ko7dDAfBgNVHSMEGDAWgBST49gyJtrV8UqlkUrg6kviogzP4TCB jwYDVR0fBIGHMIGEMECgPqA8hjpodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWcy LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMECgPqA8hjpodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2Jh bC1yb290LWcyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHdBggrBgEFBQcBAQSB0DCBzTAzBggrBgEF BQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEoGCCsGAQUFBzAC hj5odHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWcyLWNhL3B1Yi9jYWNlcnQvY2Fj ZXJ0LmNydDBKBggrBgEFBQcwAoY+aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1n Mi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAIF4RaROpH8OVfAJ sWo+eMxoNakc85WeP/P432s4d4ksjbWtPsfylM2gBq66zKixrTMItiSGYjZMeG5Q8NVuYI1PUjFD l0Z18GLkbmZRwUIxZ1DlSec5HsufyoZI3ggU/xVLK2aboDifAM79p+vRf1ctyExf3BARlz6WBAJc hKgpOWyU/BCSBnue7thGtBu1Aww42dywqT9xBguyAwczwo1IYyUlPHp7V273igU477igri/02wfV W4QYwam4S85skBqC5Lk9+nfx0h8zAr9T53b53CYlQW8vphv6pBOQ+nx+2QtgXey/ykGgYfsRSSnY qC11FdhKGOoW71U0IhoTjQYwggXmMIIEzqADAgECAgwdgtH8FJ0VCMZ26e4wDQYJKoZIhvcNAQEL BQAwgY0xCzAJBgNVBAYTAkRFMUUwQwYDVQQKDDxWZXJlaW4genVyIEZvZXJkZXJ1bmcgZWluZXMg RGV1dHNjaGVuIEZvcnNjaHVuZ3NuZXR6ZXMgZS4gVi4xEDAOBgNVBAsMB0RGTi1QS0kxJTAjBgNV BAMMHERGTi1WZXJlaW4gR2xvYmFsIElzc3VpbmcgQ0EwHhcNMTcwNzEwMTAxODIwWhcNMjAwNzA5 MTAxODIwWjB6MQswCQYDVQQGEwJERTEgMB4GA1UECgwXRmFjaGhvY2hzY2h1bGUgTXVlbnN0ZXIx MjAwBgNVBAsMKUZhY2hiZXJlaWNoIEVsZWt0cm90ZWNobmlrIHVuZCBJbmZvcm1hdGlrMRUwEwYD VQQDDAxUaW1vIFZvZWxrZXIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC/gQYu/Hjb 3078pLzYaFpcgo/JHZHLjOLe85YFMr056WFSN/Jwdh1Asny4ZKcLzHd7vMjr3fjg8Sgo04y+lBI4 8O5FJTgixYB1oV9DU5GlWcC/6eLhpIPNraOcK4KJVlwqw7uc1L8fbyjCMrTNtYHFEy23B9NFgxbS pxhQ6FCgS6kjziTgFL6s072+j6MMJi1RdZZUNZGq52gCyIKNAxMt2b42/Kk7PTWYCSA8HzxrLsQe YxmxoxLoGTlnZxuC8WKU+1V1pUiS+Ns3krHHBHIeeogR/JeILBX0OheqStUnnEABcsWj+4uGYxvP RdZXBXm8wKjcRcnJDrKizS4G6j27AgMBAAGjggJWMIICUjBABgNVHSAEOTA3MBEGDysGAQQBga0h giwBAQQDBTARBg8rBgEEAYGtIYIsAgEEAwEwDwYNKwYBBAGBrSGCLAEBBDAJBgNVHRMEAjAAMA4G A1UdDwEB/wQEAwIF4DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFOOJ r1RvTOvocygvlHm6xGfZS5dNMB8GA1UdIwQYMBaAFGs6mIv58lOJ2uCtsjIeCR/oqjt0MCYGA1Ud EQQfMB2BG3RpbW8udm9lbGtlckBmaC1tdWVuc3Rlci5kZTCBjQYDVR0fBIGFMIGCMD+gPaA7hjlo dHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Rmbi1jYS1nbG9iYWwtZzIvcHViL2NybC9jYWNybC5jcmww P6A9oDuGOWh0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZGZuLWNhLWdsb2JhbC1nMi9wdWIvY3JsL2Nh Y3JsLmNybDCB2wYIKwYBBQUHAQEEgc4wgcswMwYIKwYBBQUHMAGGJ2h0dHA6Ly9vY3NwLnBjYS5k Zm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBJBggrBgEFBQcwAoY9aHR0cDovL2NkcDEucGNhLmRmbi5k ZS9kZm4tY2EtZ2xvYmFsLWcyL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDBJBggrBgEFBQcwAoY9aHR0 cDovL2NkcDIucGNhLmRmbi5kZS9kZm4tY2EtZ2xvYmFsLWcyL3B1Yi9jYWNlcnQvY2FjZXJ0LmNy dDANBgkqhkiG9w0BAQsFAAOCAQEAGEYW34tG4ACeQk3vN6TBr9HRRE4Rc3tJoh5odaAx4UDnO6B7 EsTOSyZmJ5jdY6ui8ns9jiwwv6yZsuhopqSatS06aSlXoJ7GWBeTS9FbDu4Fa3+Hmfo+UiqG0cul MLOfKasuZx8bsoOq1kR7WdABUL3m7FuLhIVEeuJ39yQSiWxwJ4jZ5Cx0evaXIcGDIXOE9e+GcXz2 mm1yfFxITLHt5q37phfTDLH4IOgWt9GORlDBoatSu56QwfRGwhVYmkTRrUFss3QuQ/z3SwOt30Lj MNdVk6OkQBNj9QBH5PSH/Ok/JIQODVotZWG7HQ8/8nyzYTH0ccW/1HIrCwvKicZJcTGCA40wggOJ AgEBMIGeMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8VmVyZWluIHp1ciBGb2VyZGVydW5nIGVp bmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYuMRAwDgYDVQQLDAdERk4tUEtJMSUw IwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5nIENBAgwdgtH8FJ0VCMZ26e4wCQYFKw4D AhoFAKCCAcMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTgwODAy MTIwODU2WjAjBgkqhkiG9w0BCQQxFgQU9e+r2f2XGo5yyPugFhOw/xVLpjswga8GCSsGAQQBgjcQ BDGBoTCBnjCBjTELMAkGA1UEBhMCREUxRTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9lcmRlcnVuZyBl aW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBWLjEQMA4GA1UECwwHREZOLVBLSTEl MCMGA1UEAwwcREZOLVZlcmVpbiBHbG9iYWwgSXNzdWluZyBDQQIMHYLR/BSdFQjGdunuMIGxBgsq hkiG9w0BCRACCzGBoaCBnjCBjTELMAkGA1UEBhMCREUxRTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9l cmRlcnVuZyBlaW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBWLjEQMA4GA1UECwwH REZOLVBLSTElMCMGA1UEAwwcREZOLVZlcmVpbiBHbG9iYWwgSXNzdWluZyBDQQIMHYLR/BSdFQjG dunuMA0GCSqGSIb3DQEBAQUABIIBABtxJHo2eGNIFwL4hLSURisTLgQzx3F41Ppo3guu27ChflH1 INVTMg4/yGUJ754BKzWgHc42cW5TDhki0EcMaKaqfTjGXVYctjS2OpCNwhMq6YRSKmFsT81U+AZ0 WbPvZTh8JNLOWiU1LAxc8dMXrR8uIC32fM3rBGDghvs03T/XCgctj3LPn3MqKL4xNcg347O/8SzR zTRPppsJG8XuxQ260ZPg1HQKX85etVhhm+yP0c2sDwFIOezE6iZyBzKbqqTytu1UuJRdV8WIqv27 CBXHo5ROGV3Drj1e3GkIZO/biJqSYQ50doLjx/5JpcJ8qqbueOYtOascO12mEzn2u48AAAAAAAA= --Apple-Mail=_6E682B83-9F17-4551-B00B-26D7F1CF3F3F-- From owner-freebsd-current@freebsd.org Thu Aug 2 12:45:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88D9D10669B9; Thu, 2 Aug 2018 12:45:35 +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 33F5587437; Thu, 2 Aug 2018 12:45:35 +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 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PCU0060032O6J00@st13p35im-asmtp001.me.com>; Thu, 02 Aug 2018 12:45:11 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PCU00H713F8F550@st13p35im-asmtp001.me.com>; Thu, 02 Aug 2018 12:45:11 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-02_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=27 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808020133 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Unable to UEFI boot 11.2 via pxeboot Date: Thu, 02 Aug 2018 15:45:07 +0300 In-reply-to: <9A67D337-ADC9-4B19-A44D-6C08135861D3@me.com> Cc: "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" To: =?utf-8?Q?Timo_V=C3=B6lker?= References: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> <9A67D337-ADC9-4B19-A44D-6C08135861D3@me.com> X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 12:45:35 -0000 Could you check the current with = https://svnweb.freebsd.org/changeset/base/337131 = thanks, toomas > On 2 Aug 2018, at 15:32, Toomas Soome wrote: >=20 >=20 >=20 >> On 2 Aug 2018, at 15:08, Timo V=C3=B6lker = > = wrote: >>=20 >> It seems this issue is related to current as well. I did a quick test = and got this output, while I tried to (pxe)boot FreeBSD current (without = a USB stick plugged in) >>=20 >> https://ibb.co/no8Fve >>=20 >> Best regards >>=20 >> Timo >=20 > the hint is about efipart_inithandles() returning 2, thats errno code = for ENOENT. congratz, you have hit the corner case:D >=20 > Since efinet_dev is part of devsw, we can not skip the devswitch init = with such error, we still need to walk the list. Let me see if I can = provide quick fix. >=20 > rgds, > toomas >=20 >=20 >>=20 >>> On 31. Jul 2018, at 14:16, Timo V=C3=B6lker = > = wrote: >>>=20 >>> Hi, >>>=20 >>> I'm unable to boot up the amd64 11.2 via pxeboot using UEFI on a = Dell PowerEdge R430. I get this output >>>=20 >>> https://ibb.co/h5ntuT >>>=20 >>> If I press a key to interrupt reboot, I get to the OK prompt. If I = enter lsdev -v, it prints nothing more than "net devices:". The variable = currdev is not set (show currdev prints variable 'currdev' not found). I = configured pxeboot to be the one and only boot medium in BIOS setup.=20 >>>=20 >>> However, I found a workaround that works for me. If I put an (empty) = USB stick in a USB port of the PowerEdge, it successfully boots via = pxeboot (which is still the one and only configured boot medium). I then = get this output >>>=20 >>> https://ibb.co/mU8SM8 >>>=20 >>> With FreeBSD 11.1 pxeboot worked on the Dell PowerEdge R430, even = without a USB stick plugged in. I couldn't test this with FreeBSD = 12-current. Hope this helps anyway to find an open issue. >>>=20 >>> I found this thread which seems to be related. >>>=20 >>> = https://lists.freebsd.org/pipermail/freebsd-current/2018-July/070082.html >>>=20 >>> Thanks, >>>=20 >>> Timo >>=20 >=20 From owner-freebsd-current@freebsd.org Thu Aug 2 13:32:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E71B510679F1; Thu, 2 Aug 2018 13:32: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 89CC98934D; Thu, 2 Aug 2018 13:32:32 +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 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PCU00A00287NZ00@st13p35im-asmtp002.me.com>; Thu, 02 Aug 2018 12:32:06 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PCU001A12TFKS10@st13p35im-asmtp002.me.com>; Thu, 02 Aug 2018 12:32:06 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-02_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=27 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808020131 From: Toomas Soome Message-id: <9A67D337-ADC9-4B19-A44D-6C08135861D3@me.com> MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Unable to UEFI boot 11.2 via pxeboot Date: Thu, 02 Aug 2018 15:32:02 +0300 In-reply-to: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> Cc: "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" To: =?utf-8?Q?Timo_V=C3=B6lker?= References: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 13:32:33 -0000 > On 2 Aug 2018, at 15:08, Timo V=C3=B6lker = wrote: >=20 > It seems this issue is related to current as well. I did a quick test = and got this output, while I tried to (pxe)boot FreeBSD current (without = a USB stick plugged in) >=20 > https://ibb.co/no8Fve >=20 > Best regards >=20 > Timo the hint is about efipart_inithandles() returning 2, thats errno code = for ENOENT. congratz, you have hit the corner case:D Since efinet_dev is part of devsw, we can not skip the devswitch init = with such error, we still need to walk the list. Let me see if I can = provide quick fix. rgds, toomas >=20 >> On 31. Jul 2018, at 14:16, Timo V=C3=B6lker = wrote: >>=20 >> Hi, >>=20 >> I'm unable to boot up the amd64 11.2 via pxeboot using UEFI on a Dell = PowerEdge R430. I get this output >>=20 >> https://ibb.co/h5ntuT >>=20 >> If I press a key to interrupt reboot, I get to the OK prompt. If I = enter lsdev -v, it prints nothing more than "net devices:". The variable = currdev is not set (show currdev prints variable 'currdev' not found). I = configured pxeboot to be the one and only boot medium in BIOS setup.=20 >>=20 >> However, I found a workaround that works for me. If I put an (empty) = USB stick in a USB port of the PowerEdge, it successfully boots via = pxeboot (which is still the one and only configured boot medium). I then = get this output >>=20 >> https://ibb.co/mU8SM8 >>=20 >> With FreeBSD 11.1 pxeboot worked on the Dell PowerEdge R430, even = without a USB stick plugged in. I couldn't test this with FreeBSD = 12-current. Hope this helps anyway to find an open issue. >>=20 >> I found this thread which seems to be related. >>=20 >> = https://lists.freebsd.org/pipermail/freebsd-current/2018-July/070082.html >>=20 >> Thanks, >>=20 >> Timo >=20 From owner-freebsd-current@freebsd.org Thu Aug 2 13:43:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 785661067D76; Thu, 2 Aug 2018 13:43:01 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2777A89837; Thu, 2 Aug 2018 13:43:01 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id B38AB261AE; Thu, 2 Aug 2018 13:43:00 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f178.google.com with SMTP id s12-v6so2001221ljj.0; Thu, 02 Aug 2018 06:43:00 -0700 (PDT) X-Gm-Message-State: AOUpUlG76ltkE7qCM2DoeWfaKGukaXASbk4au4mZ3JrpEer6FJKPiqlr zymqwevmzUPwYDlAvEjRj3OT7+IuXfPUUp5rEgI= X-Google-Smtp-Source: AAOMgpf6CzCqCRla5wsUSvBrDs8Bxyl/uOmvgQgnxqtbdCoDA//vWKJBuOxb7A7mIZmd6AhNz7s//1hwPok1RDZAeMo= X-Received: by 2002:a2e:8617:: with SMTP id a23-v6mr2418818lji.43.1533217379231; Thu, 02 Aug 2018 06:42:59 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Thu, 2 Aug 2018 06:42:38 -0700 (PDT) In-Reply-To: References: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> <9A67D337-ADC9-4B19-A44D-6C08135861D3@me.com> From: Kyle Evans Date: Thu, 2 Aug 2018 08:42:38 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Unable to UEFI boot 11.2 via pxeboot To: Toomas Soome Cc: =?UTF-8?B?VGltbyBWw7Zsa2Vy?= , "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 13:43:01 -0000 On Thu, Aug 2, 2018 at 7:45 AM, Toomas Soome wrote: >> On 2 Aug 2018, at 15:32, Toomas Soome wrote: >> >> >> >>> On 2 Aug 2018, at 15:08, Timo V=C3=B6lker > wrote: >>> >>> It seems this issue is related to current as well. I did a quick test a= nd got this output, while I tried to (pxe)boot FreeBSD current (without a U= SB stick plugged in) >>> >>> https://ibb.co/no8Fve >>> >>> Best regards >>> >>> Timo >> >> the hint is about efipart_inithandles() returning 2, thats errno code fo= r ENOENT. congratz, you have hit the corner case:D >> >> Since efinet_dev is part of devsw, we can not skip the devswitch init wi= th such error, we still need to walk the list. Let me see if I can provide = quick fix. >> >> rgds, >> toomas >> > > Could you check the current with https://svnweb.freebsd.org/changeset/bas= e/337131 > > thanks, > toomas > Hmm... that's less than great. Is this worth an MFC + 11.2 EN? I'd suspect it's not an entirely common case at all, but loader.efi is highly visible and actually updated in stable/11 (vs. soon-to-be thrown on ESP in head. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Thu Aug 2 13:47:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6490C106801E; Thu, 2 Aug 2018 13:47:21 +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 10EA489B4E; Thu, 2 Aug 2018 13:47:21 +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 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PCU00I0057NEL00@st13p35im-asmtp002.me.com>; Thu, 02 Aug 2018 13:47:20 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PCU00L316ARFI10@st13p35im-asmtp002.me.com>; Thu, 02 Aug 2018 13:47:18 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-02_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=27 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808020143 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Unable to UEFI boot 11.2 via pxeboot From: Toomas Soome In-reply-to: Date: Thu, 02 Aug 2018 16:47:14 +0300 Cc: =?utf-8?Q?Timo_V=C3=B6lker?= , "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" Content-transfer-encoding: quoted-printable Message-id: <92E673FE-FF42-41F3-8610-CCB960805A34@me.com> References: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> <9A67D337-ADC9-4B19-A44D-6C08135861D3@me.com> To: Kyle Evans X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 13:47:21 -0000 > On 2 Aug 2018, at 16:42, Kyle Evans wrote: >=20 > On Thu, Aug 2, 2018 at 7:45 AM, Toomas Soome wrote: >>> On 2 Aug 2018, at 15:32, Toomas Soome wrote: >>>=20 >>>=20 >>>=20 >>>> On 2 Aug 2018, at 15:08, Timo V=C3=B6lker = > = wrote: >>>>=20 >>>> It seems this issue is related to current as well. I did a quick = test and got this output, while I tried to (pxe)boot FreeBSD current = (without a USB stick plugged in) >>>>=20 >>>> https://ibb.co/no8Fve >>>>=20 >>>> Best regards >>>>=20 >>>> Timo >>>=20 >>> the hint is about efipart_inithandles() returning 2, thats errno = code for ENOENT. congratz, you have hit the corner case:D >>>=20 >>> Since efinet_dev is part of devsw, we can not skip the devswitch = init with such error, we still need to walk the list. Let me see if I = can provide quick fix. >>>=20 >>> rgds, >>> toomas >>>=20 >>=20 >> Could you check the current with = https://svnweb.freebsd.org/changeset/base/337131 = >>=20 >> thanks, >> toomas >>=20 >=20 > Hmm... that's less than great. Is this worth an MFC + 11.2 EN? I'd > suspect it's not an entirely common case at all, but loader.efi is > highly visible and actually updated in stable/11 (vs. soon-to-be > thrown on ESP in head. >=20 >=20 Once the fix is confirmed, I think it is worth MFC (I haven't checked 11 = source, however). I just want to be sure the provided patch will provide = complete fix. rgds, toomas From owner-freebsd-current@freebsd.org Thu Aug 2 14:33:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FC461069024 for ; Thu, 2 Aug 2018 14:33:24 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 AE0C38B39F for ; Thu, 2 Aug 2018 14:33:23 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 01033ad4-9661-11e8-93fa-f3ebd9db2b94 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 01033ad4-9661-11e8-93fa-f3ebd9db2b94; Thu, 02 Aug 2018 14:33:21 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w72EXKEv040611; Thu, 2 Aug 2018 08:33:20 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533220400.1369.31.camel@freebsd.org> Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers From: Ian Lepore To: Andriy Gapon , cem@freebsd.org, Johannes Lundberg Cc: freebsd-current Date: Thu, 02 Aug 2018 08:33:20 -0600 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 14:33:24 -0000 On Thu, 2018-08-02 at 08:20 +0300, Andriy Gapon wrote: > On 02/08/2018 01:17, Conrad Meyer wrote: > > > > I don't understand the concern.  There is only one listener to the > > event and it just invokes ReqSleepState, which is responsible for > > performing all suspend behavior.  The behavior is identical between > > lid close and acpiconf. > Unless someone is adding a new listener for that event. > Or if there is some listener in some proprietary or local module that's not part of base freebsd. The ability to support modules that didn't exist at the time the event was added is exactly the main benefit of a loose-runtime-binding scheme such as event notifications. -- Ian From owner-freebsd-current@freebsd.org Thu Aug 2 21:05:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1C2A1050807 for ; Thu, 2 Aug 2018 21:05:56 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 696227C67F for ; Thu, 2 Aug 2018 21:05:56 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f50.google.com with SMTP id g141-v6so5480007ita.4 for ; Thu, 02 Aug 2018 14:05:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=Fmp9Fr+JPwFr0xT5z3ZNYQaTyj5cviS9XK4weAPgmvM=; b=FZD9QyKaBk15QNnO5GA2JDpnkpoffedvQs8/EN+UBtd7tCzgmkkSpg5ljnymsaODMZ DzHPqCMe4mbz4szk3tWDta6ATTpK+s93GyDM/8qPtjo4CmG5My/CEmXC2xrJY0xemJ80 a1npw+o3BXJy3LW/Gq5EKG9DQcs0poLT+4yzpqmX1EtwGEbOgr6yMkpNnUovHNI1Qnqm yIZk7U1BT/FC/0WCNrsa9pvOfMTkKE7B+5Guf/Vi4BPIQwZ/khxHnzSjZKetyfRKJ57C NfiQ9U4UhuqflcbzOV3k6ZLhHd9t/TL9YP1DqMyZvl5lPJwi94iltbh+lFMUKt2de2b6 pMZw== X-Gm-Message-State: AOUpUlH0ivK2KRGIIS9lHbRkeeIV8xpOITgXQQkZ+zm0Tt23jGfxVdvj DKKrADKuoo2ziJULO56JWyvsNasF X-Google-Smtp-Source: AAOMgpenqg9DWBezl940ekPXVAY/BNx7JAuNNHPrCPw1g6VMkRVDoffKS3QCcnyc1OJo4F5WzlQ2nw== X-Received: by 2002:a24:7686:: with SMTP id z128-v6mr4369928itb.9.1533243949847; Thu, 02 Aug 2018 14:05:49 -0700 (PDT) Received: from mail-it0-f51.google.com (mail-it0-f51.google.com. [209.85.214.51]) by smtp.gmail.com with ESMTPSA id g185-v6sm1323641ita.17.2018.08.02.14.05.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Aug 2018 14:05:49 -0700 (PDT) Received: by mail-it0-f51.google.com with SMTP id j81-v6so3797658ite.0 for ; Thu, 02 Aug 2018 14:05:49 -0700 (PDT) X-Received: by 2002:a24:a308:: with SMTP id p8-v6mr4187974ite.53.1533243949632; Thu, 02 Aug 2018 14:05:49 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:7e0a:0:0:0:0:0 with HTTP; Thu, 2 Aug 2018 14:05:49 -0700 (PDT) In-Reply-To: References: From: Conrad Meyer Date: Thu, 2 Aug 2018 14:05:49 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 21:05:57 -0000 For those not on the bug, this is being followed up in PR 230290. On Wed, Aug 1, 2018 at 10:27 PM, Johannes Lundberg wrote: > > > On Thu, Aug 2, 2018 at 06:20 Andriy Gapon wrote: >> >> On 02/08/2018 01:17, Conrad Meyer wrote: >> > I don't understand the concern. There is only one listener to the >> > event and it just invokes ReqSleepState, which is responsible for >> > performing all suspend behavior. The behavior is identical between >> > lid close and acpiconf. >> >> Unless someone is adding a new listener for that event. > > > Exactly my point. > >> >> -- >> Andriy Gapon From owner-freebsd-current@freebsd.org Thu Aug 2 23:45:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2551F1054D29; Thu, 2 Aug 2018 23:45:41 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.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 53D9F8421B; Thu, 2 Aug 2018 23:45:40 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074422-887ff7000000681f-63-5b63979bc4e7 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 4A.FF.26655.C97936B5; Thu, 2 Aug 2018 19:45:32 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id w72NjQE6006707; Thu, 2 Aug 2018 19:45:27 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w72NjJkH013976 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 Aug 2018 19:45:22 -0400 Date: Thu, 2 Aug 2018 18:45:19 -0500 From: Benjamin Kaduk To: Eric McCorkle Cc: Warner Losh , FreeBSD Hackers , "freebsd-arch@freebsd.org" , freebsd-current , freebsd-security Subject: Re: Status of OpenSSL 1.1.1 Message-ID: <20180802234519.GD68224@kduck.kaduk.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOKsWRmVeSWpSXmKPExsUixG6nojtnenK0wd3zxhbfpv9lsZg9fRqT xZw3H5gstm/+x2jRs+kJm8XTrcsZHdg8Puz+yuox49N8Fo97OyYwBTBHcdmkpOZklqUW6dsl cGW8vLyOueASd8WBD6/YGhifcnQxcnJICJhI7F+4gamLkYtDSGAxk8SypiPMEM4GRomdjXOh MleYJD5sPsAO0sIioCLx49NBVhCbDchu6L4M1MHBISKgITF/tyBIPbNAF5PEr0lnWUBqhIFq ui/dB6vhBVp3cHY5xMxDjBL7N/eA1fAKCEqcnPkEzGYW0JHYufUOG0g9s4C0xPJ/HBBheYnm rbPBxnAKOEtM+uMDEhYVUJbY23eIfQKj4Cwkg2YhGTQLYdAsJIMWMLKsYpRNya3SzU3MzClO TdYtTk7My0st0jXVy80s0UtNKd3ECI4DF6UdjBP/eR1iFOBgVOLh1dBIjhZiTSwrrsw9xCjJ waQkystfDhTiS8pPqcxILM6ILyrNSS0Geo+DWUmE920nUI43JbGyKrUoHyYlzcGiJM57vyY8 WkggPbEkNTs1tSC1CCYrw8GhJMG7cRpQo2BRanpqRVpmTglCmomDE2Q4D9BwFZAa3uKCxNzi zHSI/ClGXY4/76dOYhZiycvPS5US5xUCKRIAKcoozYObA0pfEtn7a14xigO9Jcw7DaSKB5j6 4Ca9AlrCBLQk2zERZElJIkJKqoExo2f2n3aLPr2M1OT57Lez/KVzyjUd35uV/b75wlLp3TGt uKQA82sNTP/uv1r+7Mss5ap1dTcjthhHBzo/rth1emmdBnNrzr0+x+nx7+WL1XYUbipimPQr rTU838O3dlE//6QJr4WWvThrk1nl0lN0xHGt3YMpn5hdclg7Lu1aLRd+/NYqzT4lluKMREMt 5qLiRABbGPrYOgMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 02 Aug 2018 23:45:41 -0000 On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote: > On 08/01/2018 09:02, Warner Losh wrote: > > > > > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > > wrote: > > > > Hi folks, > > > > I'm wondering what's the status of OpenSSL 1.1.1 integration into base? > > More specifically, is there a repo or a branch that's started the > > integration?  I'm aware of the wiki page and the list of port build > > issues, but that seems to be based on replacing the base OpenSSL with a > > port build (similar to the way one replaces it with LibreSSL). > > > > I have some work I'd like to do that's gating on sorting out the > > kernel/loader crypto situation, and I'd very much like to see OpenSSL > > 1.1.1 get merged, so I can start to look into doing that. > > > > > > There are patches to use bear SSL for the loader. OpenSSL is simply too > > large to use due to limits the loader operates under. > > I was going to look into the feasibility of doing something like what > LibreSSL does with portable, where they extract a subset of the full > library designed to be embedded in the kernel, loader, etc. > > I think it ought to be possible to do something like that, but it really > ought to be done in a tree with 1.1.1 integrated. > It wouldn't be terribly easy or effective, IMO. OpenSSL wasn't designed with such modularity in mind. -Ben From owner-freebsd-current@freebsd.org Fri Aug 3 01:39:57 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2172A10582DC for ; Fri, 3 Aug 2018 01:39:57 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8AC08A10F; Fri, 3 Aug 2018 01:39:56 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: by mail-it0-x243.google.com with SMTP id 72-v6so6336564itw.3; Thu, 02 Aug 2018 18:39:56 -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=6NxwxKQlyT+d21giH+lxaXBIohF/9yDbvpuz9IQHJz0=; b=HRQ3RsuRv3EUUYkwkoRf8l9w5zC8B8XLgf4bprFCDOLPq2yyUviNCXhMF8R013FoJF VN+0zNbybSfxW5+M9W3UTM7n8A1xDseukxmG/IOtsNObepKC83ewVCJsh/HGiqcsUKIp p7Pd6A4hUlh78YSwcrzVSlAdboXdCak1yS1jaw9jFXmbDWTjQt5r0Te8CA190qkiLT5h 5i/28l1mDPCEMcKJHFn6dryToHXFIjHMOAssXxIZfa9o9c52HUWlseZOC2qNvxYqj7tq ZWBzqffbNh+kwGTPibsL122zsAXcxsFUT+wtpFUwCt+7BTL/HS0HYOZ4yMlHIGqY9ZJ2 /jMw== 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=6NxwxKQlyT+d21giH+lxaXBIohF/9yDbvpuz9IQHJz0=; b=WcOL8P+Y3c/bX3TWodhkWOb8Bx4c8qDFAOFWRshIn7K8LWWZ3FFeND0ENxGgMbsGd3 INIh7MDK1iNe8FYKgoZvYt6WJtr5/GV/WemaDptshZPEdJVu+Oz2Bq5qDSa8H06H7Ifi DIWE445czdRXS78EmzhDfG/3pFN00qi0dbkATuzt6C0zXE7mQC8uweYFQhN7f5wigaif fq/luxreqcDjkk4HjQ3jGfBKY8uXlMzhDi31HOscjdfBk/qu/1ijnRhXSZcK8LGq6jgk iAxZbml9pWFLG2VLIrQ8gtmm344Y42BSEhj6uAVY6iHQkh99kFkr/vzmTMTb/IitjfCm U9vw== X-Gm-Message-State: AOUpUlH0/w6X3gLpoEUJGMi8KPIPUNOo0GVbiwNvS3gB0yg0hG554QgL 6b414gyqiWzYf+GHxjf7hk+yQZNxhakr8A/aNJ6+hMj1 X-Google-Smtp-Source: AAOMgpfC9xjhHwUHajJ/EWoAZGuVJ7fIctxT5DFeRAtBFXPmUxFHwlpis8D8yKg7oYYgKI+PGZN8FhCh3K3XceqcDcw= X-Received: by 2002:a24:98d6:: with SMTP id n205-v6mr4851666itd.44.1533260396052; Thu, 02 Aug 2018 18:39:56 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:3d1:0:0:0:0:0 with HTTP; Thu, 2 Aug 2018 18:39:55 -0700 (PDT) In-Reply-To: <20180729143529.16bad01a@thor.intern.walstatt.dynvpn.de> References: <20180728072938.GA28778@kloomba> <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> <20180729080957.GB2216@kloomba> <20180729105550.4ac8711a@thor.intern.walstatt.dynvpn.de> <20180729111751.GC2216@kloomba> <20180729143529.16bad01a@thor.intern.walstatt.dynvpn.de> From: Oleg Lelchuk Date: Thu, 2 Aug 2018 21:39:55 -0400 Message-ID: Subject: Re: EFI issues To: "O. Hartmann" Cc: Roman Bogorodskiy , freebsd-current@freebsd.org, Toomas Soome , "Rodney W. Grimes" , Warner Losh , Allan Jude Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 01:39:57 -0000 Yes, I also had the same issue until I followed the suggestions given in this email exchange. Thanks! On Sun, Jul 29, 2018 at 8:35 AM, O. Hartmann wrote= : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Am Sun, 29 Jul 2018 15:17:53 +0400 > Roman Bogorodskiy schrieb: > > > O. Hartmann wrote: > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA512 > > > > > > Am Sun, 29 Jul 2018 12:09:58 +0400 > > > Roman Bogorodskiy schrieb: > > > > > > > O. Hartmann wrote: > > > > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > > Hash: SHA512 > > > > > > > > > > Am Sat, 28 Jul 2018 11:29:40 +0400 > > > > > Roman Bogorodskiy schrieb: > > > > > > > > > > > Hi, > > > > > > > > > > > > I have a test box that's updated to -CURRENT usually once in a > week or > > > > > > two. This box boots using UEFI. After a regular update about tw= o > weeks > > > > > > ago it started to panic on boot frequently (not UEFI related), > but I > > > > > > could not get a crash dump because my swap partition was too > small. So I > > > > > > moved data to the backup drive, repartitioned the main drive an= d > boot > > > > > > again. This went fine, so I decided to upgrade to fresh -CURREN= T > from > > > > > > ~Jul 27th. Booting with the new kernel went fine, but after > installworld > > > > > > machine stopped booting, and on the screen I see: > > > > > > > > > > > > FreeBSD/amd64 EFI loader, ... > > > > > > > > > > > > .. > > > > > > > > > > > > BootOrder: .... > > > > > > > > > > > > And then it gets stuck and nothing happens. > > > > > > > > > > > > As I already have a fresh backup, I decided that it'd be easier > to > > > > > > just re-install and copy data back over (maybe I messed up with > > > > > > repartitioning). So I've downloaded a fresh snapshot: > > > > > > > > > > > > FreeBSD-12.0-CURRENT-amd64-20180726-r336739-memstick.img > > > > > > > > > > > > And re-installed. In the installer I choose all the same > settings that > > > > > > were before: UEFI + GPT, default partition scheme it suggested > (efi > > > > > > followed by freebsd-ufs followed by freebsd-swap), just > increased the > > > > > > swap size. > > > > > > > > > > > > And the newly installed system won't boot just like a previous > one: > > > > > > > > > > > > https://people.freebsd.org/~novel/misc/freebsd_efi_lookup.jpg > > > > > > > > > > > > Is there a way to recover this? > > > > > > > > > > > > Roman Bogorodskiy > > > > > > > > > > Just curious: > > > > > > > > > > When I installed FreeBSD last time from the recent (2018-07-26) > USB flash drive > > > > > on a SSD, the freebsd-swap partition followed immediately after > the ESP and/or > > > > > freebsd-boot GPT loader partition. But in most cases I used to us= e > ZFS for > > > > > testing. > > > > > > > > When I reinstalled it yesterday from -CURRENT snapshot mentioned > above, > > > > in guided mode it suggested a similar partitioning schema that I us= e: > > > > > > > > =3D> 40 1953525088 ada0 GPT (932G) > > > > 40 409600 1 efi (200M) > > > > 409640 1803550720 2 freebsd-ufs (860G) > > > > 1803960360 148897792 3 freebsd-swap (71G) > > > > 1952858152 666976 - free - (326M) > > > > > > > > The only difference it that the freebsd-swap size was 3.5G (and > > > > therefore, freebsd-ufs is large), the order was the same. > > > > > > > > > Since I had my UEFI adventure of my own these days and received > valuable hints > > > > > from the development/maintenance team on some UEFI aspects, it > would be of > > > > > interest to know your recent hardware and, more importantly since > I see the boot > > > > > order presented in you screenshot, a dump of the efi variable > settings. Just for > > > > > curiosity. For that, you have to boot the recent USB flash drive > image with > > > > > UEFI-only, then logon as root and perform > > > > > > > > > > kldload efirt > > > > > > > > > > and then issue > > > > > > > > > > # efibootmgr -v > > > > > > > > > > In my case, it looks like > > > > > > > > > > [...] > > > > > [ohartmann]: sudo efibootmgr -v > > > > > BootCurrent: 0001 > > > > > Timeout : 3 seconds > > > > > BootOrder : 0001, 0002, 0003, 0004, 0005, 0000 > > > > > +Boot0001* FreeBSD-12 \ > > > > > HD(1,GPT,e1460941-e2e9-11e5-b913-d0509907ef09,0x28,0x640)/ > File(\efi\boot\BOOTx64.efi) > > > > > \ ada0p1:/efi/boot/BOOTx64.efi (null) > > > > > Boot0002* Hard Drive BBS(HD,,0x0) > > > > > Boot0003* CD/DVD Drive BBS(CDROM,,0x0) > > > > > Boot0004* USB BBS(USB,,0x0) > > > > > Boot0005* Network Card BBS(Network,,0x0) > > > > > Boot0000 FreeBSD-12 > > > > > HD(1,GPT,e1460941-e2e9-11e5-b913-d0509907ef09,0x28,0x640)/ > File(\efi\boot\BOOTx64.efi) > > > > > ada0p1:/efi/boot/BOOTx64.efi (null) > > > > > > > > > > > > > > > Unreferenced Variables: > > > > > [...] > > > > > > > > > > Boot0000 is the same as Boot0001 and is defined due to some "bug" > Warner Losh has > > > > > fixed recently, it is the same as Boot0001 > > > > > > > > Motherboard is (from dmidecode): > > > > > > > > Handle 0x0000, DMI type 0, 24 bytes > > > > BIOS Information > > > > Vendor: American Megatrends Inc. > > > > Version: 0806 > > > > Release Date: 02/20/2014 > > > > Address: 0xF0000 > > > > Runtime Size: 64 kB > > > > ROM Size: 16 MB > > > > Characteristics: > > > > PCI is supported > > > > APM is supported > > > > BIOS is upgradeable > > > > BIOS shadowing is allowed > > > > Boot from CD is supported > > > > Selectable boot is supported > > > > BIOS ROM is socketed > > > > EDD is supported > > > > 5.25"/1.2 MB floppy services are supported (int 13h= ) > > > > 3.5"/720 kB floppy services are supported (int 13h) > > > > 3.5"/2.88 MB floppy services are supported (int 13h= ) > > > > Print screen service is supported (int 5h) > > > > 8042 keyboard services are supported (int 9h) > > > > Serial services are supported (int 14h) > > > > Printer services are supported (int 17h) > > > > ACPI is supported > > > > USB legacy is supported > > > > BIOS boot specification is supported > > > > Targeted content distribution is supported > > > > UEFI is supported > > > > BIOS Revision: 4.6 > > > > > > > > Handle 0x0002, DMI type 2, 15 bytes > > > > Base Board Information > > > > Manufacturer: ASUSTeK COMPUTER INC. > > > > Product Name: B85M-E > > > > Version: Rev X.0x > > > > Serial Number: 140526238405585 > > > > Asset Tag: To be filled by > > > > O.E.M. > > > > Features: Board is a hosting > > > > board Board is > > > > replaceable Location In Chassis: To be filled by > > > > O.E.M. Chassis Handle: > > > > 0x0003 Type: > > > > Motherboard Contained Object Handles: 0 > > > > > > > > 'efibootmgr -v' output: > > > > > > > > BootCurrent: 0004 > > > > Timeout : 1 seconds > > > > BootOrder : 0001, 0002, 0003, 0004 > > > > Boot0001* Hard Drive BBS(HD,,0x0) > > > > Boot0002* Network Card BBS(Network,,0x0) > > > > Boot0003* UEFI OS > > > > HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28, > 0x64000)/File(\EFI\BOOT\BOOTX64.EFI) > > > > ada0p1:/EFI/BOOT/BOOTX64.EFI (null) > > > > Path(0,0,ae84b11df581724e85442bab0c2cac5c020000020000) +Boot0004* > UEFI: SanDisk > > > > PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x4,0x0)/HD( > 1,MBR,0x90909090,0x1,0x640) > > > > VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6, > 530061006e004400690073006b000000) > > > > > > > > > > > > Unreferenced Variables: > > > > > > > > > > > > > Kind regards, > > > > > > > > > > oh > > > > > > > > > > - -- > > > > > 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). > > > > > -----BEGIN PGP SIGNATURE----- > > > > > > > > > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW11wfgAKCRDS528fyFhY > > > > > lMojAf929USx1x7I/sSGLtEWKO8rm9IXf1JEpQ7GSdI6YHid364x7fbrUBhDZYuT > > > > > JVanY57Li2oLOXogHtMw6eDUyD+aAf9GTE30LUNRhmcJ7el62Vwpm0oUBG2as52i > > > > > +v58EZ9c20yKQKuXt446dhbILyODDPKmc9ykAvnE0TtMiTHk6vRn > > > > > =3DM7vi > > > > > -----END PGP SIGNATURE----- > > > > > > > > Roman Bogorodskiy > > > > > > The order of the partitions was simply an observation and from the > "old days" with > > > HDD as mass storage/boot storage with rotating platters it was some > sort of important > > > for the access latency where to position the swap partition. With NAN= D > flash based > > > SSD this became obsolete - so, please don't be bothered about that. > > > > > > - From my (non-expert) point of view, you UEFI variables look "normal= " > (according to > > > what I see on my boxes at home), but I was wondering about the "aged" > firmware of you > > > mainboard. Checking out at ASUS' website/support, they claim they hav= e > a more recent > > > firmare from 2018! This would be on par with the Spectre/Meltdown > mitigation promises > > > made by most valuable/reliable mainboard vendors and Intel: > > > > > > https://www.asus.com/Motherboards/B85ME/HelpDesk_BIOS/ > > > > > > Version 3602 2018/05/25 7.29 MByte B85M-E BIOS 3602 > > > > > > Since dmidecode reports on my ASRock crap mainboard also > > > > > > BIOS Revision: 4.6 > > > > > > I guess this one is fake or some "default" from the dmidecode program > not identifying > > > the correct revision - or it's another semantic not known to me. > > > > > > But my dmidecode looks like this, with the latest BETA ASrock provide= s > for this long > > > time ago discontinued Z77 Pro4-board: > > > > > > [...] > > > > > > # dmidecode 3.1 > > > # SMBIOS entry point at 0x000f04c0 > > > Found SMBIOS entry point in EFI, reading table from /dev/mem. > > > SMBIOS 2.7 present. > > > 26 structures occupying 1523 bytes. > > > Table at 0x000EE7F0. > > > > > > Handle 0x0000, DMI type 0, 24 bytes > > > BIOS Information > > > Vendor: American Megatrends Inc. > > > Version: P2.00 > > > Release Date: 03/13/2018 > > > Address: 0xF0000 > > > Runtime Size: 64 kB > > > ROM Size: 8192 kB > > > Characteristics: > > > PCI is supported > > > BIOS is upgradeable > > > BIOS shadowing is allowed > > > Boot from CD is supported > > > Selectable boot is supported > > > BIOS ROM is socketed > > > EDD is supported > > > 5.25"/1.2 MB floppy services are supported (int 13h) > > > 3.5"/720 kB floppy services are supported (int 13h) > > > 3.5"/2.88 MB floppy services are supported (int 13h) > > > Print screen service is supported (int 5h) > > > 8042 keyboard services are supported (int 9h) > > > Serial services are supported (int 14h) > > > Printer services are supported (int 17h) > > > ACPI is supported > > > USB legacy is supported > > > BIOS boot specification is supported > > > Targeted content distribution is supported > > > UEFI is supported > > > BIOS Revision: 4.6 > > > [...] > > > > > > Watch out the Version: P2.00 entry, which is indeed the version numbe= r > of the > > > firmware. So, in your case, the firmware is also a bit outdated, from > 2014. I'd > > > update the firmware prior to any further action if there are no > obligations from > > > hardware incompatibilities so far to meet the neccessity of lates > Intel/AMD microcode > > > updates and/or other UEFI vulnerabilities of which I have no active > memories about, > > > but they hit me 2015/2016 on our servers. There is no guarantee that > the firmware > > > update will salvage your problem, but that might be worth a shot. > Also, ASUS mention > > > to have solved performance issues with the latest firmware, please > consider > > > consulting the description of the latest firmware release. > > > > > > As the next step, as from my "naive" point of view, I would perform > the steps > > > recommended to me by FreeBSD's developers to set the UEFI variables > again: > > > > > > Boot in UEFI mode from the USB flash device > > > Logon as root > > > mount -uw / > > > kldload efirt > > > mount -t msdosfs /dev/ada0p1 /mnt > > > > > > efibootmgr -c -l /mnt/efi/boot/BOOTx64.efi -L FreeBSD > > > efibootmgr -v > > > > > > Look for the "Boot000X" entry labeled with "FreeBSD", take the number > portion of the > > > that Boot000X variable (000X) and perform > > > > > > efibootmgr -a 000X > > > efibootmgr -n 000X (this one is "extra" and can be ommited, it means > "next boot", see > > > manpage efibootmgr(8)) > > > > > > and check again with > > > > > > efibootmgr -v > > > > > > The "maneuver" above is only in case the settings of UEFI variables > has gone rogue. > > > > > > Regards, > > > > > > oh > > > > I've updated BIOS (which alone didn't change anything) and executed > > commands you suggested, and it helped! Thanks! > > > > Now 'efibootmgr -v' output looks like this: > > > > BootCurrent: 0000 > > Timeout : 1 seconds > > BootOrder : 0000, 0004, 0006, 0003, 0007 > > +Boot0000* FreeBSD > > HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28, > 0x64000)/File(\efi\boot\BOOTx64.efi) > > ada0p1:/efi/boot/BOOTx64.efi (null) Boot0004* Hard Drive BBS(HD,,0x0) > > Boot0006* Network Card BBS(Network,,0x0) > > Boot0003* UEFI OS > > HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28, > 0x64000)/File(\EFI\BOOT\BOOTX64.EFI) > > ada0p1:/EFI/BOOT/BOOTX64.EFI (null) > > Path(0,0,ef47642dc93ba041ac194d51d01b4ce65200650061006c00740065006b00 > 200042006f006f00740020004100670065006e0074000000) > > Boot0007* UEFI: SanDisk > > PciRoot(0x0)/Pci(0x14,0x0)/USB(0x9,0x0)/HD(1,MBR,0x90909090,0x1,0x640) > > VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6, > 340043003500330031003000300031003500340031003000310035003100 > 300039003000390035000000) > > > > > > Unreferenced Variables: > > > > This is strange, because the only difference I see is that Boot0000 has > > lowercase filenames ('/efi/boot/BOOTx64.efi' vs > > '/EFI/BOOT/BOOTX64.EFI'). I'm wondering if that's the only reason it > > wasn't working before? > > > > > - -- > > > O. Hartmann > [...] > > > > > Roman Bogorodskiy > > I'm glad to be of help. But it was a "wild guess", not experience or > decend knowledge. > Maybe there is an issue with recent UEFI/boot/stand implementation since > this portion of > FreeBSD is under heavy development or has been under such ... > > Ypu shpuld consider contacting Warner Losh or Toomas Soome (on the curren= t@ > list, there > is a thread entitelt "[UEFI] Boot issues on some UEFI implementations" > started by myself > targetting some weird FreeBSD/UEFI issues. Toomas Soome gave me the hint > with > efibootmgr(8) and I figured out by learning from the definitions, that on > specific UEFI > implementations, the boot path "/efi/boot/bootx64.efi" is considered the > default for > changeable media (like USB flash drives) and not necessaryly the default > for SATA/SAS > devices. > > I felt frank and free to CC some people form the list, hoping that could > shed light on > the issue. > > Kind regards, > oh > > - -- > 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 Ab= s. 4 BDSG). > -----BEGIN PGP SIGNATURE----- > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW120kQAKCRDS528fyFhY > lI+dAf0Uqgl1GkUstSrHJZPFJgkV91YzjURFaQHwpq26kA8Uex7mWntBKNUTjzx/ > MUG/U4IUvyImGESmBZYOcSyApTXOAf9PDWXBWM/zwfu9L9TbogVuJ1WYTOF4hdB6 > iEvbNWRtNQy6eQwD6+eUBISxJfG+dS8DVAzwkP46+vU23R6VI2c8 > =3DO9lx > -----END PGP SIGNATURE----- > _______________________________________________ > 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 Fri Aug 3 02:39:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72A421059CE4 for ; Fri, 3 Aug 2018 02:39:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0C7788C16B for ; Fri, 3 Aug 2018 02:39:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C27FB1059CE2; Fri, 3 Aug 2018 02:39:35 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B14141059CE1 for ; Fri, 3 Aug 2018 02:39:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 533608C168 for ; Fri, 3 Aug 2018 02:39:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 9B2D72F361 for ; Fri, 3 Aug 2018 02:39:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w732dY82026785 for ; Fri, 3 Aug 2018 02:39:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w732dYid026784 for current@FreeBSD.org; Fri, 3 Aug 2018 02:39:34 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 208938] usr.sbin/config does not preserve whitespace in static env Date: Fri, 03 Aug 2018 02:39:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kevans@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10- mfc-stable11? X-Bugzilla-Changed-Fields: flagtypes.name bug_status cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 Aug 2018 03:15:38 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 02:39:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208938 Kyle Evans changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |mfc-stable10-, | |mfc-stable11? Status|New |In Progress CC| |kevans@freebsd.org --- Comment #2 from Kyle Evans --- Hi, Sorry for the radio silence on this. I committed a new version of the env l= ine sanitizer (written by ian@) in r335642 which also fixed this, and later revisions to config(8) fixed this same kind of bug in hints. I'll be MFC'ing the rewrite and all of my other env work (deduplication, fi= xing the order of precedence) likely this weekend. Thanks, Kyle Evans --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Fri Aug 3 02:39:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF2801059D1F for ; Fri, 3 Aug 2018 02:39:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3888C18B for ; Fri, 3 Aug 2018 02:39:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 114541059D1D; Fri, 3 Aug 2018 02:39:46 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 002E21059D1B for ; Fri, 3 Aug 2018 02:39:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96E9D8C189 for ; Fri, 3 Aug 2018 02:39:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E536A2F365 for ; Fri, 3 Aug 2018 02:39:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w732dir5026940 for ; Fri, 3 Aug 2018 02:39:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w732ditM026939 for current@FreeBSD.org; Fri, 3 Aug 2018 02:39:44 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 208938] usr.sbin/config does not preserve whitespace in static env Date: Fri, 03 Aug 2018 02:39:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kevans@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: kevans@freebsd.org X-Bugzilla-Flags: mfc-stable10- mfc-stable11? X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 Aug 2018 03:42:31 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 02:39:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208938 Kyle Evans changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |kevans@freebsd.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Fri Aug 3 05:43:14 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B076105E1C0 for ; Fri, 3 Aug 2018 05:43:14 +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 E701B7181C for ; Fri, 3 Aug 2018 05:43:13 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w735h6gJ093162; Thu, 2 Aug 2018 22:43:13 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "RW" , In-Reply-To: From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Niclas Zeising" Subject: Re: ntpd as ntpd user question Date: Thu, 02 Aug 2018 22:43:12 -0700 Message-Id: <1bd91aa67e408dd8f275225325edccd9@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 05:43:14 -0000 On Mon, 23 Jul 2018 12:57:28 +0200 "Niclas Zeising" said > On 07/21/18 19:56, RW wrote: > > On Sat, 21 Jul 2018 11:14:45 -0600 > > Ian Lepore wrote: > >=20 > >=20 > >> There's a "pre-world" stage of mergemaster (-Fp option I think) which > >> isn't needed often, but one of the times it is needed is apparently > >> when new user ids are added=2E > >=20 > > I wish mergemaster had an option to just add new users and groups, > > rather than merging the files=2E >=20 > etcupdate is usually pretty good at automatically merge updates to files= =20 > without user interaction, even when the files are locally edited as=20 > well=2E For instance, I had no problem merging /etc/master=2Epasswd and=20 > /etc/group for the ntp change=2E > Regards > --=20 > Niclas FWIW I found mergemaster intimidating when I was first starting out=2E Not because I didn't understand patch(1)/diff(1)=2E I was well familiar there=2E But I found it unintuitive=2E Despite the messages regarding it's usage=2E Anyway=2E I finally developed a strategy that worked for me=2E I start out with the standard mergemaster -p then the installworld But I implement the following mergemster, thusly mergemaster -vF It dispenses with asking about all the files that only have revision changes, and date differences, and just updates them, the -v portion, just keeps "enlightened" as to wtf is actually happening during the process=2E Then all that's left are just some 5-9 files I need to deal with, with mergemaster informing me that by default, it'll leave them for me, to look at later=2E To which I reply Y=2E Done=2E Knowing diff/patch, makes the resulting unmerged files a trivial task, requiring perhaps 5-10 minutes while still at the console=2E Then I reboot into the new system=2E HTH --Chris > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= " From owner-freebsd-current@freebsd.org Fri Aug 3 07:28:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B13BB106009F; Fri, 3 Aug 2018 07:28:49 +0000 (UTC) (envelope-from timo.voelker@fh-muenster.de) Received: from mail.fh-muenster.de (mail.fh-muenster.de [212.201.120.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.fh-muenster.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 475A774660; Fri, 3 Aug 2018 07:28:49 +0000 (UTC) (envelope-from timo.voelker@fh-muenster.de) Received: from fhad-ex13.fhad.fh-muenster.de (unknown [10.41.11.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.fh-muenster.de (Postfix) with ESMTPS id 74E5028465E; Fri, 3 Aug 2018 09:28:47 +0200 (CEST) Received: from fhad-ex13.fhad.fh-muenster.de (10.41.11.26) by fhad-ex13.fhad.fh-muenster.de (10.41.11.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1415.2; Fri, 3 Aug 2018 09:28:47 +0200 Received: from fhad-ex13.fhad.fh-muenster.de ([fe80::d9a6:349d:aadc:72e6]) by fhad-ex13.fhad.fh-muenster.de ([fe80::d9a6:349d:aadc:72e6%5]) with mapi id 15.01.1415.002; Fri, 3 Aug 2018 09:28:47 +0200 From: =?utf-8?B?VGltbyBWw7Zsa2Vy?= To: Toomas Soome CC: "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: Unable to UEFI boot 11.2 via pxeboot Thread-Topic: Unable to UEFI boot 11.2 via pxeboot Thread-Index: AQHUKMhMn24QMJWRqkeXKQYwbojdqqSsQBQAgAAGdACAAAOogIABOfIA Date: Fri, 3 Aug 2018 07:28:47 +0000 Message-ID: References: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> <9A67D337-ADC9-4B19-A44D-6C08135861D3@me.com> In-Reply-To: Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.40.10.31] Content-Type: multipart/signed; boundary="Apple-Mail=_FF14ABAA-F971-491B-873C-2CDE51DF1955"; protocol="application/pkcs7-signature"; micalg=sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 07:28:49 -0000 --Apple-Mail=_FF14ABAA-F971-491B-873C-2CDE51DF1955 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Toomas, it seems your fix works here. Some of the error messages remain, but I = was able to (pxe)boot without a USB stick plugged in. https://ibb.co/g8Bkfe Right after the moment from the screenshot, the FreeBSD boot manager = showed up. Thanks, Timo > On 2. Aug 2018, at 14:45, Toomas Soome wrote: >=20 > Could you check the current with = https://svnweb.freebsd.org/changeset/base/337131 >=20 > thanks, > toomas >=20 >> On 2 Aug 2018, at 15:32, Toomas Soome wrote: >>=20 >>=20 >>=20 >>> On 2 Aug 2018, at 15:08, Timo V=C3=B6lker = wrote: >>>=20 >>> It seems this issue is related to current as well. I did a quick = test and got this output, while I tried to (pxe)boot FreeBSD current = (without a USB stick plugged in) >>>=20 >>> https://ibb.co/no8Fve >>>=20 >>> Best regards >>>=20 >>> Timo >>=20 >> the hint is about efipart_inithandles() returning 2, thats errno code = for ENOENT. congratz, you have hit the corner case:D >>=20 >> Since efinet_dev is part of devsw, we can not skip the devswitch init = with such error, we still need to walk the list. Let me see if I can = provide quick fix. >>=20 >> rgds, >> toomas >>=20 >>=20 >>>=20 >>>> On 31. Jul 2018, at 14:16, Timo V=C3=B6lker = wrote: >>>>=20 >>>> Hi, >>>>=20 >>>> I'm unable to boot up the amd64 11.2 via pxeboot using UEFI on a = Dell PowerEdge R430. I get this output >>>>=20 >>>> https://ibb.co/h5ntuT >>>>=20 >>>> If I press a key to interrupt reboot, I get to the OK prompt. If I = enter lsdev -v, it prints nothing more than "net devices:". The variable = currdev is not set (show currdev prints variable 'currdev' not found). I = configured pxeboot to be the one and only boot medium in BIOS setup.=20 >>>>=20 >>>> However, I found a workaround that works for me. If I put an = (empty) USB stick in a USB port of the PowerEdge, it successfully boots = via pxeboot (which is still the one and only configured boot medium). I = then get this output >>>>=20 >>>> https://ibb.co/mU8SM8 >>>>=20 >>>> With FreeBSD 11.1 pxeboot worked on the Dell PowerEdge R430, even = without a USB stick plugged in. I couldn't test this with FreeBSD = 12-current. Hope this helps anyway to find an open issue. >>>>=20 >>>> I found this thread which seems to be related. >>>>=20 >>>> = https://lists.freebsd.org/pipermail/freebsd-current/2018-July/070082.html >>>>=20 >>>> Thanks, >>>>=20 >>>> Timo >>>=20 >>=20 >=20 --Apple-Mail=_FF14ABAA-F971-491B-873C-2CDE51DF1955 Content-Disposition: attachment; filename="smime.p7s" Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQsDCCBRIw ggP6oAMCAQICCQDjC9X4ryXZgTANBgkqhkiG9w0BAQsFADCBgjELMAkGA1UEBhMCREUxKzApBgNV BAoMIlQtU3lzdGVtcyBFbnRlcnByaXNlIFNlcnZpY2VzIEdtYkgxHzAdBgNVBAsMFlQtU3lzdGVt cyBUcnVzdCBDZW50ZXIxJTAjBgNVBAMMHFQtVGVsZVNlYyBHbG9iYWxSb290IENsYXNzIDIwHhcN MTYwMjIyMTMzODIyWhcNMzEwMjIyMjM1OTU5WjCBlTELMAkGA1UEBhMCREUxRTBDBgNVBAoTPFZl cmVpbiB6dXIgRm9lcmRlcnVuZyBlaW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBW LjEQMA4GA1UECxMHREZOLVBLSTEtMCsGA1UEAxMkREZOLVZlcmVpbiBDZXJ0aWZpY2F0aW9uIEF1 dGhvcml0eSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAy2DX/2ahQc3S+oeXinOr mU3qZzlaoWCARxVOjJWy5c/O01dLjc74VmwVVXYH6kb9yANFYz5w1KtUgLEjnL43KKkJ/wVdGA/E mJk3syD2ZngXh8KdDsxKMucWna4OjSl5BwAgVNwVX0qW13i2NNPBdLWd6b/Ad03qvVkH4FovbDyl ANw1vWUNj38ybfJaaktiAe6sODRZRTZJBdp4ymptW8CBaxHM0jyoi/hxGso74oDdFrRneos26k6R KT2zUVytqAy+nTTj0Q0Xg3XEOR6wlAsS8dVpjiX0uD0rv8COwx47pb9VEKsqrheXXjPOyPP0CQfj AoYxRmsBxRAMEcdZ6QIDAQABo4IBdDCCAXAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBST49gy JtrV8UqlkUrg6kviogzP4TAfBgNVHSMEGDAWgBS/WSA2AHmgoCJrjNXyYdK4LMuCSjASBgNVHRMB Af8ECDAGAQH/AgECMDMGA1UdIAQsMCowDwYNKwYBBAGBrSGCLAEBBDANBgsrBgEEAYGtIYIsHjAI BgZngQwBAgIwTAYDVR0fBEUwQzBBoD+gPYY7aHR0cDovL3BraTAzMzYudGVsZXNlYy5kZS9ybC9U ZWxlU2VjX0dsb2JhbFJvb3RfQ2xhc3NfMi5jcmwwgYYGCCsGAQUFBwEBBHoweDAsBggrBgEFBQcw AYYgaHR0cDovL29jc3AwMzM2LnRlbGVzZWMuZGUvb2NzcHIwSAYIKwYBBQUHMAKGPGh0dHA6Ly9w a2kwMzM2LnRlbGVzZWMuZGUvY3J0L1RlbGVTZWNfR2xvYmFsUm9vdF9DbGFzc18yLmNlcjANBgkq hkiG9w0BAQsFAAOCAQEAhwv/PgKbZchWLdY7mpiLcU/auimqIflGLvWypA+uETh5OLMOdLp2XZ7o GIKWYttMM+jd+WrfMr0sTEdgVX/ndGu0LIPYeWu2t01QC2YHte2zl63q7n8w5pn9IuJyTT6EW+75 z5nqf9dSOS6smABEfmk7v3Xu0As7Gs3l9w8ibEeE9qVHoP3QGjR9rdI9d7Pu9NdN/8Po5ZJPWT6Q RxBKsIVYwG9/+K7tCEKeHtTfFC5Nj7yelMPn7fYY+DxJ5yaopzbYLN4izYuC2Nl44lUSozuHRLYR C9UMUq9pjA8G39CiU4tXmHvP/Qck9Py9w/1KkgKXG/K3ts9lihqitXIZOTCCBawwggSUoAMCAQIC BxtjutAeLD0wDQYJKoZIhvcNAQELBQAwgZUxCzAJBgNVBAYTAkRFMUUwQwYDVQQKEzxWZXJlaW4g enVyIEZvZXJkZXJ1bmcgZWluZXMgRGV1dHNjaGVuIEZvcnNjaHVuZ3NuZXR6ZXMgZS4gVi4xEDAO BgNVBAsTB0RGTi1QS0kxLTArBgNVBAMTJERGTi1WZXJlaW4gQ2VydGlmaWNhdGlvbiBBdXRob3Jp dHkgMjAeFw0xNjA1MjQxMTM4NDBaFw0zMTAyMjIyMzU5NTlaMIGNMQswCQYDVQQGEwJERTFFMEMG A1UECgw8VmVyZWluIHp1ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0 emVzIGUuIFYuMRAwDgYDVQQLDAdERk4tUEtJMSUwIwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJ c3N1aW5nIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnTt5HEfeH4bLxmnXEJ45 19miMNtyHAV/KV9LaPGtGdZM4WsbsQt/oavge4uL2C3Obog6EO5X5R5/BFE267pwbWOgvpYuQOHR g0xmPRxkaeWbpK1yrmg5UYd5zBfTri9dY3FLOXrrQqeXkGkFv5D/pEBwvQPnv54YiB+fmYhNDkeN SF9lmRDS2SpJ7cG5LR2fEssV0z9/HlQvOq6TV6d+eMrVSuIa5e1BfVNfyLMq9YowrO0XBSQ/tqAL B/1NGpoDUqA2nN4kh2Xk5/rHlnMkFM3Q6BtonhhZrnZ+99EKeDyHS7A3z1PKOjgQ88tHbYxkPTxa RUq6yoB8uPPnp0xMzQIDAQABo4ICBTCCAgEwEgYDVR0TAQH/BAgwBgEB/wIBATAOBgNVHQ8BAf8E BAMCAQYwKQYDVR0gBCIwIDANBgsrBgEEAYGtIYIsHjAPBg0rBgEEAYGtIYIsAQEEMB0GA1UdDgQW BBRrOpiL+fJTidrgrbIyHgkf6Ko7dDAfBgNVHSMEGDAWgBST49gyJtrV8UqlkUrg6kviogzP4TCB jwYDVR0fBIGHMIGEMECgPqA8hjpodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWcy LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMECgPqA8hjpodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2Jh bC1yb290LWcyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHdBggrBgEFBQcBAQSB0DCBzTAzBggrBgEF BQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEoGCCsGAQUFBzAC hj5odHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWcyLWNhL3B1Yi9jYWNlcnQvY2Fj ZXJ0LmNydDBKBggrBgEFBQcwAoY+aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1n Mi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAIF4RaROpH8OVfAJ sWo+eMxoNakc85WeP/P432s4d4ksjbWtPsfylM2gBq66zKixrTMItiSGYjZMeG5Q8NVuYI1PUjFD l0Z18GLkbmZRwUIxZ1DlSec5HsufyoZI3ggU/xVLK2aboDifAM79p+vRf1ctyExf3BARlz6WBAJc hKgpOWyU/BCSBnue7thGtBu1Aww42dywqT9xBguyAwczwo1IYyUlPHp7V273igU477igri/02wfV W4QYwam4S85skBqC5Lk9+nfx0h8zAr9T53b53CYlQW8vphv6pBOQ+nx+2QtgXey/ykGgYfsRSSnY qC11FdhKGOoW71U0IhoTjQYwggXmMIIEzqADAgECAgwdgtH8FJ0VCMZ26e4wDQYJKoZIhvcNAQEL BQAwgY0xCzAJBgNVBAYTAkRFMUUwQwYDVQQKDDxWZXJlaW4genVyIEZvZXJkZXJ1bmcgZWluZXMg RGV1dHNjaGVuIEZvcnNjaHVuZ3NuZXR6ZXMgZS4gVi4xEDAOBgNVBAsMB0RGTi1QS0kxJTAjBgNV BAMMHERGTi1WZXJlaW4gR2xvYmFsIElzc3VpbmcgQ0EwHhcNMTcwNzEwMTAxODIwWhcNMjAwNzA5 MTAxODIwWjB6MQswCQYDVQQGEwJERTEgMB4GA1UECgwXRmFjaGhvY2hzY2h1bGUgTXVlbnN0ZXIx MjAwBgNVBAsMKUZhY2hiZXJlaWNoIEVsZWt0cm90ZWNobmlrIHVuZCBJbmZvcm1hdGlrMRUwEwYD VQQDDAxUaW1vIFZvZWxrZXIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC/gQYu/Hjb 3078pLzYaFpcgo/JHZHLjOLe85YFMr056WFSN/Jwdh1Asny4ZKcLzHd7vMjr3fjg8Sgo04y+lBI4 8O5FJTgixYB1oV9DU5GlWcC/6eLhpIPNraOcK4KJVlwqw7uc1L8fbyjCMrTNtYHFEy23B9NFgxbS pxhQ6FCgS6kjziTgFL6s072+j6MMJi1RdZZUNZGq52gCyIKNAxMt2b42/Kk7PTWYCSA8HzxrLsQe YxmxoxLoGTlnZxuC8WKU+1V1pUiS+Ns3krHHBHIeeogR/JeILBX0OheqStUnnEABcsWj+4uGYxvP RdZXBXm8wKjcRcnJDrKizS4G6j27AgMBAAGjggJWMIICUjBABgNVHSAEOTA3MBEGDysGAQQBga0h giwBAQQDBTARBg8rBgEEAYGtIYIsAgEEAwEwDwYNKwYBBAGBrSGCLAEBBDAJBgNVHRMEAjAAMA4G A1UdDwEB/wQEAwIF4DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFOOJ r1RvTOvocygvlHm6xGfZS5dNMB8GA1UdIwQYMBaAFGs6mIv58lOJ2uCtsjIeCR/oqjt0MCYGA1Ud EQQfMB2BG3RpbW8udm9lbGtlckBmaC1tdWVuc3Rlci5kZTCBjQYDVR0fBIGFMIGCMD+gPaA7hjlo dHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Rmbi1jYS1nbG9iYWwtZzIvcHViL2NybC9jYWNybC5jcmww P6A9oDuGOWh0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZGZuLWNhLWdsb2JhbC1nMi9wdWIvY3JsL2Nh Y3JsLmNybDCB2wYIKwYBBQUHAQEEgc4wgcswMwYIKwYBBQUHMAGGJ2h0dHA6Ly9vY3NwLnBjYS5k Zm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBJBggrBgEFBQcwAoY9aHR0cDovL2NkcDEucGNhLmRmbi5k ZS9kZm4tY2EtZ2xvYmFsLWcyL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDBJBggrBgEFBQcwAoY9aHR0 cDovL2NkcDIucGNhLmRmbi5kZS9kZm4tY2EtZ2xvYmFsLWcyL3B1Yi9jYWNlcnQvY2FjZXJ0LmNy dDANBgkqhkiG9w0BAQsFAAOCAQEAGEYW34tG4ACeQk3vN6TBr9HRRE4Rc3tJoh5odaAx4UDnO6B7 EsTOSyZmJ5jdY6ui8ns9jiwwv6yZsuhopqSatS06aSlXoJ7GWBeTS9FbDu4Fa3+Hmfo+UiqG0cul MLOfKasuZx8bsoOq1kR7WdABUL3m7FuLhIVEeuJ39yQSiWxwJ4jZ5Cx0evaXIcGDIXOE9e+GcXz2 mm1yfFxITLHt5q37phfTDLH4IOgWt9GORlDBoatSu56QwfRGwhVYmkTRrUFss3QuQ/z3SwOt30Lj MNdVk6OkQBNj9QBH5PSH/Ok/JIQODVotZWG7HQ8/8nyzYTH0ccW/1HIrCwvKicZJcTGCA40wggOJ AgEBMIGeMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8VmVyZWluIHp1ciBGb2VyZGVydW5nIGVp bmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYuMRAwDgYDVQQLDAdERk4tUEtJMSUw IwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5nIENBAgwdgtH8FJ0VCMZ26e4wCQYFKw4D AhoFAKCCAcMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTgwODAz MDcyODQ3WjAjBgkqhkiG9w0BCQQxFgQUwBuhS6b0G8iWHa+otjCUuQtvrFwwga8GCSsGAQQBgjcQ BDGBoTCBnjCBjTELMAkGA1UEBhMCREUxRTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9lcmRlcnVuZyBl aW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBWLjEQMA4GA1UECwwHREZOLVBLSTEl MCMGA1UEAwwcREZOLVZlcmVpbiBHbG9iYWwgSXNzdWluZyBDQQIMHYLR/BSdFQjGdunuMIGxBgsq hkiG9w0BCRACCzGBoaCBnjCBjTELMAkGA1UEBhMCREUxRTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9l cmRlcnVuZyBlaW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBWLjEQMA4GA1UECwwH REZOLVBLSTElMCMGA1UEAwwcREZOLVZlcmVpbiBHbG9iYWwgSXNzdWluZyBDQQIMHYLR/BSdFQjG dunuMA0GCSqGSIb3DQEBAQUABIIBAHkrOi1h3D3eX1jI8/QrruSP/EZJaLRf0ynPuhIyU/UwlgMR xaHrXu4/lysIccoLXDRyEDQL9gHEE1fGL7bs54dyOSvKIC7ehFhO8y2JRkNGvF3P5p+vibUX6z44 Y/A7klUB/iV2QrNxKbI8ZkN5l7ZCd7CD4r0LfDYTXWib7rEMISi2CYW5hkGSbtKl9GupXDgmKlZa vOXOAQijr+7PjR8yZrRPJqlMmJPk4TAaInlvNUFUILSTm4tGh9g7UNwHUscdUNO1EUZBhn1zmzvM TJwC1QZosfojlejhygmNXwrgDM0p7D1VG3yCzFNwPQ8KjMh/dUhZsppVyUg+ktwuP2kAAAAAAAA= --Apple-Mail=_FF14ABAA-F971-491B-873C-2CDE51DF1955-- From owner-freebsd-current@freebsd.org Fri Aug 3 07:31:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C922106027D for ; Fri, 3 Aug 2018 07:31:42 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) 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 12F6E74966 for ; Fri, 3 Aug 2018 07:31:42 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id C89AE106027C; Fri, 3 Aug 2018 07:31:41 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B781B106027B for ; Fri, 3 Aug 2018 07:31:41 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 5030C7495F for ; Fri, 3 Aug 2018 07:31:41 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1flUYh-0006J1-5X for current@freebsd.org; Fri, 03 Aug 2018 10:31:35 +0300 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: ntpd user/group issue Message-Id: <1C5B5B84-7FF1-489B-9607-11F1432B7C1E@cs.huji.ac.il> Date: Fri, 3 Aug 2018 10:31:34 +0300 To: FreeBSD Current X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 07:31:42 -0000 Hi, I am cross compiling, which means i=E2=80=99m using for example an 11.1 = to compile current, for another host - an image which is different from the one i'm using to = compile. make install checks for ntpd in /etc, instead, should it look elsewhere? = DESTDIR perhaps? cheers, danny From owner-freebsd-current@freebsd.org Fri Aug 3 08:17:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 429161061688; Fri, 3 Aug 2018 08:17:31 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (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 C60637615B; Fri, 3 Aug 2018 08:17:30 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.mr11p00im-asmtp003.me.com by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PCV00100LGYU200@mr11p00im-asmtp003.me.com>; Fri, 03 Aug 2018 08:17:12 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PCV00GWULOHJJ40@mr11p00im-asmtp003.me.com>; Fri, 03 Aug 2018 08:17:08 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-03_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=27 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808030093 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Unable to UEFI boot 11.2 via pxeboot From: Toomas Soome In-reply-to: Date: Fri, 03 Aug 2018 11:17:04 +0300 Cc: "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" Content-transfer-encoding: quoted-printable Message-id: References: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> <9A67D337-ADC9-4B19-A44D-6C08135861D3@me.com> To: =?utf-8?Q?Timo_V=C3=B6lker?= X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 08:17:31 -0000 > On 3 Aug 2018, at 10:28, Timo V=C3=B6lker = wrote: >=20 > Hi Toomas, >=20 > it seems your fix works here. Some of the error messages remain, but I = was able to (pxe)boot without a USB stick plugged in. >=20 > https://ibb.co/g8Bkfe >=20 > Right after the moment from the screenshot, the FreeBSD boot manager = showed up. >=20 > Thanks, >=20 > Timo Ok, so far so good. As seen from the screen dump, some cleanup is = required, I do not think we should print about efipart_inithandles() in = case of errno 2 - thats perfectly normal case if there are no block = devices. Update commited:) rgds, toomas >=20 >> On 2. Aug 2018, at 14:45, Toomas Soome wrote: >>=20 >> Could you check the current with = https://svnweb.freebsd.org/changeset/base/337131 >>=20 >> thanks, >> toomas >>=20 >>> On 2 Aug 2018, at 15:32, Toomas Soome wrote: >>>=20 >>>=20 >>>=20 >>>> On 2 Aug 2018, at 15:08, Timo V=C3=B6lker = wrote: >>>>=20 >>>> It seems this issue is related to current as well. I did a quick = test and got this output, while I tried to (pxe)boot FreeBSD current = (without a USB stick plugged in) >>>>=20 >>>> https://ibb.co/no8Fve >>>>=20 >>>> Best regards >>>>=20 >>>> Timo >>>=20 >>> the hint is about efipart_inithandles() returning 2, thats errno = code for ENOENT. congratz, you have hit the corner case:D >>>=20 >>> Since efinet_dev is part of devsw, we can not skip the devswitch = init with such error, we still need to walk the list. Let me see if I = can provide quick fix. >>>=20 >>> rgds, >>> toomas >>>=20 >>>=20 >>>>=20 >>>>> On 31. Jul 2018, at 14:16, Timo V=C3=B6lker = wrote: >>>>>=20 >>>>> Hi, >>>>>=20 >>>>> I'm unable to boot up the amd64 11.2 via pxeboot using UEFI on a = Dell PowerEdge R430. I get this output >>>>>=20 >>>>> https://ibb.co/h5ntuT >>>>>=20 >>>>> If I press a key to interrupt reboot, I get to the OK prompt. If I = enter lsdev -v, it prints nothing more than "net devices:". The variable = currdev is not set (show currdev prints variable 'currdev' not found). I = configured pxeboot to be the one and only boot medium in BIOS setup.=20 >>>>>=20 >>>>> However, I found a workaround that works for me. If I put an = (empty) USB stick in a USB port of the PowerEdge, it successfully boots = via pxeboot (which is still the one and only configured boot medium). I = then get this output >>>>>=20 >>>>> https://ibb.co/mU8SM8 >>>>>=20 >>>>> With FreeBSD 11.1 pxeboot worked on the Dell PowerEdge R430, even = without a USB stick plugged in. I couldn't test this with FreeBSD = 12-current. Hope this helps anyway to find an open issue. >>>>>=20 >>>>> I found this thread which seems to be related. >>>>>=20 >>>>> = https://lists.freebsd.org/pipermail/freebsd-current/2018-July/070082.html >>>>>=20 >>>>> Thanks, >>>>>=20 >>>>> Timo >>>>=20 >>>=20 >>=20 >=20 From owner-freebsd-current@freebsd.org Fri Aug 3 08:40:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0D091062072 for ; Fri, 3 Aug 2018 08:40:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7391076D90 for ; Fri, 3 Aug 2018 08:40:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id i18-v6so4325910ioj.13 for ; Fri, 03 Aug 2018 01:40:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=j5gof52vQnrzZXrvewO0qR/autX+lEzx/eBTz20ZTmI=; b=uZ7WpE2hJot34RmJgNnGy/EEgS274Y+ZeDfOnDzQr3pImvqvkyPXPC112I+zYGFuKd iwdnlaFEJfsKCrxpng78DPxTnRMseicYMpCqOiSEQfGkdTfLklN1Y/27OF+KcosUay34 3LQGR/KNrh3ptOiVAAs+84cx2xeLpeNz5gEQcHG3VwlQYtM/xIh6nXy17QMC0MburvRB i6sOcBm7CThfy+yUJEebhLXRVlTl8E3eDZaFH6AERgpCa4soEacMrb1XnkAd7A0lGOKL d9T+5HMXVB9jNV+S5QjH4qQteOfE47Xwj2yYtvZl6huenZZGtl8R95NlRvnzxiZXWy8l QSOQ== 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=j5gof52vQnrzZXrvewO0qR/autX+lEzx/eBTz20ZTmI=; b=VS798p2C4VLhXcze8VmnRkUxMON886jyWjOjHxeIp1+OhVKDBW4g2WMhe0BFbzKR4P 6zguI+i9uhgdVr4+yAv6l7q9Ffm5QnjECDdLKzexztS7LHCcqILHm18H21cDgeLmJBe1 2vH8lY6FvM+wBKmyqMcIXHpBbK8t9syQYBnWCixTc1eusZDpADG7Zvgk7JsnR3t6mmFP rlH7npppNI1PK85SMPBT5/zdqZIwuyCBxGuPnb1pNpybFWl9ofeTgRJQQiWY84CTors1 wUEuKIQwods1VAw7bVgMoQyDG8Sg5LXJG16HSgEH3sL3W7wTtqSOGJSTw0kgBpIyaKN7 w+MQ== X-Gm-Message-State: AOUpUlHh57fPOE6BPaXaRllwyIFLRgnCae42z2vS9PuG8Avof3rw+/jw KLk2HHkGtcVZ8wKvz3cosJotN3UetTDK2ExWibqzsw== X-Google-Smtp-Source: AA+uWPwyBLpKNx5CaibjkRjr6+Gc3h9ch0f1gzH8AdGfz0H3KpSF9InbYctS/O4EB3uM4K35dqEfofUBBV6wCB3Yk40= X-Received: by 2002:a6b:d004:: with SMTP id x4-v6mr5058616ioa.299.1533285632650; Fri, 03 Aug 2018 01:40:32 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:4485:0:0:0:0:0 with HTTP; Fri, 3 Aug 2018 01:40:32 -0700 (PDT) X-Originating-IP: [86.153.210.77] In-Reply-To: <20180729143529.16bad01a@thor.intern.walstatt.dynvpn.de> References: <20180728072938.GA28778@kloomba> <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> <20180729080957.GB2216@kloomba> <20180729105550.4ac8711a@thor.intern.walstatt.dynvpn.de> <20180729111751.GC2216@kloomba> <20180729143529.16bad01a@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Fri, 3 Aug 2018 02:40:32 -0600 X-Google-Sender-Auth: NPJiDvMB3PQ3qT_dXUb9WrQAgn4 Message-ID: Subject: Re: EFI issues To: "O. Hartmann" Cc: Roman Bogorodskiy , FreeBSD Current , Toomas Soome , "Rodney W. Grimes" , Allan Jude Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 08:40:34 -0000 On Sun, Jul 29, 2018 at 6:35 AM, O. Hartmann wrote: > > > > 'efibootmgr -v' output: > > > > > > > > BootCurrent: 0004 > > > > Timeout : 1 seconds > > > > BootOrder : 0001, 0002, 0003, 0004 > > > > Boot0001* Hard Drive BBS(HD,,0x0) > > > > Boot0002* Network Card BBS(Network,,0x0) > > > > Boot0003* UEFI OS > > > > HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28, > 0x64000)/File(\EFI\BOOT\BOOTX64.EFI) > > > > ada0p1:/EFI/BOOT/BOOTX64.EFI (null) > > > > Path(0,0,ae84b11df581724e85442bab0c2cac5c020000020000) +Boot0004* > UEFI: SanDisk > > > > PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x4,0x0)/HD( > 1,MBR,0x90909090,0x1,0x640) > > > > VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6, > 530061006e004400690073006b000000) > ... > > I've updated BIOS (which alone didn't change anything) and executed > > commands you suggested, and it helped! Thanks! > > > > Now 'efibootmgr -v' output looks like this: > > > > BootCurrent: 0000 > > Timeout : 1 seconds > > BootOrder : 0000, 0004, 0006, 0003, 0007 > > +Boot0000* FreeBSD > > HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28, > 0x64000)/File(\efi\boot\BOOTx64.efi) > > ada0p1:/efi/boot/BOOTx64.efi (null) Boot0004* Hard Drive BBS(HD,,0x0) > > Boot0006* Network Card BBS(Network,,0x0) > > Boot0003* UEFI OS > > HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28, > 0x64000)/File(\EFI\BOOT\BOOTX64.EFI) > > ada0p1:/EFI/BOOT/BOOTX64.EFI (null) > > Path(0,0,ef47642dc93ba041ac194d51d01b4ce65200650061006c00740065006b00 > 200042006f006f00740020004100670065006e0074000000) > > Boot0007* UEFI: SanDisk > > PciRoot(0x0)/Pci(0x14,0x0)/USB(0x9,0x0)/HD(1,MBR,0x90909090,0x1,0x640) > > VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6, > 340043003500330031003000300031003500340031003000310035003100 > 300039003000390035000000) > > > > > > Unreferenced Variables: > > > > This is strange, because the only difference I see is that Boot0000 has > > lowercase filenames ('/efi/boot/BOOTx64.efi' vs > > '/EFI/BOOT/BOOTX64.EFI'). I'm wondering if that's the only reason it > > wasn't working before? > > > > > - -- > > > O. Hartmann > [...] > > > > > Roman Bogorodskiy > > I'm glad to be of help. But it was a "wild guess", not experience or > decend knowledge. > Maybe there is an issue with recent UEFI/boot/stand implementation since > this portion of > FreeBSD is under heavy development or has been under such ... > > Ypu shpuld consider contacting Warner Losh or Toomas Soome (on the current@ > list, there > is a thread entitelt "[UEFI] Boot issues on some UEFI implementations" > started by myself > targetting some weird FreeBSD/UEFI issues. Toomas Soome gave me the hint > with > efibootmgr(8) and I figured out by learning from the definitions, that on > specific UEFI > implementations, the boot path "/efi/boot/bootx64.efi" is considered the > default for > changeable media (like USB flash drives) and not necessaryly the default > for SATA/SAS > devices. Case shouldn't matter. If it does, I've done something wrong. Internally, we convert to lower case and the filesystem is case insensitive in this case. The whole default file thing is something I thought I understood really, really well, but it's becoming clear that there's issues that are clear as mud. We should be coping with this junk in the installer... Warner From owner-freebsd-current@freebsd.org Fri Aug 3 08:44:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04C1310623F5 for ; Fri, 3 Aug 2018 08:44:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8897977199 for ; Fri, 3 Aug 2018 08:44:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22a.google.com with SMTP id r15-v6so4381789ioa.3 for ; Fri, 03 Aug 2018 01:44:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BAiAO4BN65wamN90CtGrC3g8xn03btAGQa9snL4okZQ=; b=AgMTGXLK+Jm7fyXoAok+LfpFrN9+zmvWAB8v6GV1RWkMUIfzUd4+da10WpE+aPBBgu zbsUXqKSs/e3aDV1giQLrA7ElR+OFj8z2087t1FF9Eaol0cYIeDW509p2cAuVP3EZ2mN 8arVoYI9ax8IB78J4rSQebSB2plZOVvrOZZAoPxSjMtuZb/OBzEUnjfPkL1ucAge4R1O wNEy9mapC8fyfnonYrcDEb0GdFnfY1KU/YkoQc4a5IDHYhDcx64AFF/aDg0B6SsNy4dw 1BSDXVc8p8JhB0LA9tjvWFI+kQ4Oad6MaXpQV75Qy6gqq6xpSRS8c/xM/5zuwYJBu9sg XJwg== 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=BAiAO4BN65wamN90CtGrC3g8xn03btAGQa9snL4okZQ=; b=masJ1i8Fo8nQvri26+tfBrUpUJU9+W+5MVInNPUnRTbgTvVVZKKriSnrL6+BaPQ6aK 6Fg2hSsAmWagUEgBFXQXXD+jCYKEzZRsX7QQmFQSs9czyn8/B7Reyv66eBxJgd1NV/Qp pyonza3Ic0LmzkRjS05CSyCE0d5AUtEV0twS6ojvi6R/HmEkOKdh4ZZfYY7J5hi7c1gJ QmptOqVnwYVAIh6tAE3pUyJOzgzXQTA9T9+zPpigE8pRxXeGDuPNTkO587wbnASBsmym Ec2boa+q2HRMdgqRCUkx5M7mwKci9ttQY5JDOW34eTKUU9EsIt/rWove0bPKIqdl6qNe i11w== X-Gm-Message-State: AOUpUlGLPxKnvQslReVG3dYQuX2xxArzfu+u7VbbhNrk7k8zQnEnwKtg wi5rRKQ+z93M3ReDMA9x2khlPu9RxA+5P+itfgZELw== X-Google-Smtp-Source: AA+uWPxRtETiA0vQuvKOkan73dUmhjbC72QhIOzEYkHQ5bQhRNSsT2bApwIbofxOY4mxJwvfamQK9l4tbkP2Pn85yKQ= X-Received: by 2002:a6b:d004:: with SMTP id x4-v6mr5064998ioa.299.1533285849927; Fri, 03 Aug 2018 01:44:09 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:4485:0:0:0:0:0 with HTTP; Fri, 3 Aug 2018 01:44:09 -0700 (PDT) X-Originating-IP: [86.153.210.77] In-Reply-To: <20180802234519.GD68224@kduck.kaduk.org> References: <20180802234519.GD68224@kduck.kaduk.org> From: Warner Losh Date: Fri, 3 Aug 2018 02:44:09 -0600 X-Google-Sender-Auth: ij_u90ZUmAUGxcJSfLBylG5FCvM Message-ID: Subject: Re: Status of OpenSSL 1.1.1 To: Benjamin Kaduk Cc: Eric McCorkle , FreeBSD Hackers , "freebsd-arch@freebsd.org" , freebsd-current , freebsd-security Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 08:44:11 -0000 On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk wrote: > On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote: > > On 08/01/2018 09:02, Warner Losh wrote: > > > > > > > > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > > > wrote: > > > > > > Hi folks, > > > > > > I'm wondering what's the status of OpenSSL 1.1.1 integration into > base? > > > More specifically, is there a repo or a branch that's started the > > > integration? I'm aware of the wiki page and the list of port build > > > issues, but that seems to be based on replacing the base OpenSSL > with a > > > port build (similar to the way one replaces it with LibreSSL). > > > > > > I have some work I'd like to do that's gating on sorting out the > > > kernel/loader crypto situation, and I'd very much like to see > OpenSSL > > > 1.1.1 get merged, so I can start to look into doing that. > > > > > > > > > There are patches to use bear SSL for the loader. OpenSSL is simply too > > > large to use due to limits the loader operates under. > > > > I was going to look into the feasibility of doing something like what > > LibreSSL does with portable, where they extract a subset of the full > > library designed to be embedded in the kernel, loader, etc. > > > > I think it ought to be possible to do something like that, but it really > > ought to be done in a tree with 1.1.1 integrated. > > > > It wouldn't be terribly easy or effective, IMO. OpenSSL wasn't designed > with such modularity in mind. > Others that have tried have found OpenSSL to be way too large for the boot loader and a completely impossible to subset enough to get things small enough due to the intertwingled nature of things. Warner From owner-freebsd-current@freebsd.org Fri Aug 3 11:02:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03AB31065CDE; Fri, 3 Aug 2018 11:02:24 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (static-98-116-200-172.nycmny.fios.verizon.net [98.116.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id A0FD67C467; Fri, 3 Aug 2018 11:02:23 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [172.16.0.23] (unknown [172.16.0.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 89930619A; Fri, 3 Aug 2018 11:02:22 +0000 (UTC) Subject: Re: Status of OpenSSL 1.1.1 To: Warner Losh , Benjamin Kaduk Cc: FreeBSD Hackers , "freebsd-arch@freebsd.org" , freebsd-current , freebsd-security References: <20180802234519.GD68224@kduck.kaduk.org> From: Eric McCorkle Openpgp: preference=signencrypt Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEWue2FBYJKwYBBAHaRw8BAQdAP/qVPlXodV6pYO5b1Jw0eFyMhyDD7B5y5eFsciutEfS0 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiWBBMWCAA+FiEEDxi/0rkj zd6Uc6cFCN/CKRbBwmwFAlrnthQCGwMFCQHhM4AFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQCN/CKRbBwmyGKAD/XTSBOItCKcYCPTlsaS1aQYVEwWXXFgdjWE+WsNdZUS8A/AhYAbQZ kNZNimE2rQLoklkfTA74qF/V257NuQi4QDcLuDgEWue2FBIKKwYBBAGXVQEFAQEHQKpZVyCG ync/xqejm2C1HKGXLJTUu38RvnrR3UYECz9nAwEIB4h+BBgWCAAmFiEEDxi/0rkjzd6Uc6cF CN/CKRbBwmwFAlrnthQCGwwFCQHhM4AACgkQCN/CKRbBwmyi2wEAmvaGt8QMjGELzm27gP4c jJGUi7oigsLmTiFPkpJqPz0A+QFBSCvxJaxCMyoVru/xB6bunpJ+Wtsj8HD1EuJOn4EJ Message-ID: Date: Fri, 3 Aug 2018 07:02:18 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3Jlf5EtgHrBUwuVED8RcynGXM8EBmN3FH" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 11:02:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3Jlf5EtgHrBUwuVED8RcynGXM8EBmN3FH Content-Type: multipart/mixed; boundary="SgFMOIbWT0nMndG6NllvpPpohfXOlolaP"; protected-headers="v1" From: Eric McCorkle To: Warner Losh , Benjamin Kaduk Cc: FreeBSD Hackers , "freebsd-arch@freebsd.org" , freebsd-current , freebsd-security Message-ID: Subject: Re: Status of OpenSSL 1.1.1 References: <20180802234519.GD68224@kduck.kaduk.org> In-Reply-To: --SgFMOIbWT0nMndG6NllvpPpohfXOlolaP Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 08/03/2018 04:44, Warner Losh wrote: >=20 >=20 > On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk > wrote: >=20 > On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote: > > On 08/01/2018 09:02, Warner Losh wrote: > > > > > > > > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > > > > >> wr= ote: > > > > > >=C2=A0 =C2=A0 =C2=A0Hi folks, > > > > > >=C2=A0 =C2=A0 =C2=A0I'm wondering what's the status of OpenSSL 1= =2E1.1 integration > into base? > > >=C2=A0 =C2=A0 =C2=A0More specifically, is there a repo or a bran= ch that's > started the > > >=C2=A0 =C2=A0 =C2=A0integration?=C2=A0 I'm aware of the wiki pag= e and the list of > port build > > >=C2=A0 =C2=A0 =C2=A0issues, but that seems to be based on replac= ing the base > OpenSSL with a > > >=C2=A0 =C2=A0 =C2=A0port build (similar to the way one replaces = it with LibreSSL). > > > > > >=C2=A0 =C2=A0 =C2=A0I have some work I'd like to do that's gatin= g on sorting out the > > >=C2=A0 =C2=A0 =C2=A0kernel/loader crypto situation, and I'd very= much like to > see OpenSSL > > >=C2=A0 =C2=A0 =C2=A01.1.1 get merged, so I can start to look int= o doing that. > > > > > > > > > There are patches to use bear SSL for the loader. OpenSSL is > simply too > > > large to use due to limits the loader operates under. > > > > I was going to look into the feasibility of doing something like = what > > LibreSSL does with portable, where they extract a subset of the f= ull > > library designed to be embedded in the kernel, loader, etc. > > > > I think it ought to be possible to do something like that, but it= > really > > ought to be done in a tree with 1.1.1 integrated. > > >=20 > It wouldn't be terribly easy or effective, IMO.=C2=A0 OpenSSL wasn'= t designed > with such modularity in mind. >=20 >=20 > Others that have tried have found OpenSSL to be way too large for the > boot loader and a completely impossible to subset enough to get things > small enough due to the intertwingled nature of things. To what extent, if any, does this change in 1.1.1, though? --SgFMOIbWT0nMndG6NllvpPpohfXOlolaP-- --3Jlf5EtgHrBUwuVED8RcynGXM8EBmN3FH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQPGL/SuSPN3pRzpwUI38IpFsHCbAUCW2Q2OgAKCRAI38IpFsHC bHx7AQCF1Yu898/tbKfMJvXrPaJmDmV2wf66gtK5k+KJ1ulKmgEAuuXdSuUriYuK n3pc4P82OqfT9LnymaHfY6T9KM/6QAg= =tWx/ -----END PGP SIGNATURE----- --3Jlf5EtgHrBUwuVED8RcynGXM8EBmN3FH-- From owner-freebsd-current@freebsd.org Fri Aug 3 11:50:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F9F610672E3; Fri, 3 Aug 2018 11:50:17 +0000 (UTC) (envelope-from timo.voelker@fh-muenster.de) Received: from mail.fh-muenster.de (mail.fh-muenster.de [212.201.120.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.fh-muenster.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B61EC7DBC3; Fri, 3 Aug 2018 11:50:16 +0000 (UTC) (envelope-from timo.voelker@fh-muenster.de) Received: from fhad-ex03.fhad.fh-muenster.de (unknown [10.40.11.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.fh-muenster.de (Postfix) with ESMTPS id ACA9F284B7E; Fri, 3 Aug 2018 13:50:14 +0200 (CEST) Received: from fhad-ex13.fhad.fh-muenster.de (10.41.11.26) by fhad-ex03.fhad.fh-muenster.de (10.40.11.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1415.2; Fri, 3 Aug 2018 13:50:14 +0200 Received: from fhad-ex13.fhad.fh-muenster.de ([fe80::d9a6:349d:aadc:72e6]) by fhad-ex13.fhad.fh-muenster.de ([fe80::d9a6:349d:aadc:72e6%5]) with mapi id 15.01.1415.002; Fri, 3 Aug 2018 13:50:14 +0200 From: =?utf-8?B?VGltbyBWw7Zsa2Vy?= To: Toomas Soome CC: "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: Unable to UEFI boot 11.2 via pxeboot Thread-Topic: Unable to UEFI boot 11.2 via pxeboot Thread-Index: AQHUKMhMn24QMJWRqkeXKQYwbojdqqSsQBQAgAAGdACAAAOogIABOfIAgAANfwCAADuNgA== Date: Fri, 3 Aug 2018 11:50:14 +0000 Message-ID: <679C6D10-4951-4669-8B8A-53EAB358FAA3@fh-muenster.de> References: <3DF39C46-977E-4D07-AF23-F0C7D5DAF2E6@fh-muenster.de> <9A67D337-ADC9-4B19-A44D-6C08135861D3@me.com> In-Reply-To: Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.40.10.31] Content-Type: multipart/signed; boundary="Apple-Mail=_CC385DA5-9338-491F-B7D1-F70CCCF6D922"; protocol="application/pkcs7-signature"; micalg=sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 11:50:17 -0000 --Apple-Mail=_CC385DA5-9338-491F-B7D1-F70CCCF6D922 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 3. Aug 2018, at 10:17, Toomas Soome wrote: >=20 >=20 >=20 >> On 3 Aug 2018, at 10:28, Timo V=C3=B6lker = wrote: >>=20 >> Hi Toomas, >>=20 >> it seems your fix works here. Some of the error messages remain, but = I was able to (pxe)boot without a USB stick plugged in. >>=20 >> https://ibb.co/g8Bkfe >>=20 >> Right after the moment from the screenshot, the FreeBSD boot manager = showed up. >>=20 >> Thanks, >>=20 >> Timo >=20 > Ok, so far so good. As seen from the screen dump, some cleanup is = required, I do not think we should print about efipart_inithandles() in = case of errno 2 - thats perfectly normal case if there are no block = devices. Update commited:) >=20 > rgds, > toomas It still works and it looks better with less error messages :-) https://ibb.co/bVv9Oz Thanks, Timo >=20 >>=20 >>> On 2. Aug 2018, at 14:45, Toomas Soome wrote: >>>=20 >>> Could you check the current with = https://svnweb.freebsd.org/changeset/base/337131 >>>=20 >>> thanks, >>> toomas >>>=20 >>>> On 2 Aug 2018, at 15:32, Toomas Soome wrote: >>>>=20 >>>>=20 >>>>=20 >>>>> On 2 Aug 2018, at 15:08, Timo V=C3=B6lker = wrote: >>>>>=20 >>>>> It seems this issue is related to current as well. I did a quick = test and got this output, while I tried to (pxe)boot FreeBSD current = (without a USB stick plugged in) >>>>>=20 >>>>> https://ibb.co/no8Fve >>>>>=20 >>>>> Best regards >>>>>=20 >>>>> Timo >>>>=20 >>>> the hint is about efipart_inithandles() returning 2, thats errno = code for ENOENT. congratz, you have hit the corner case:D >>>>=20 >>>> Since efinet_dev is part of devsw, we can not skip the devswitch = init with such error, we still need to walk the list. Let me see if I = can provide quick fix. >>>>=20 >>>> rgds, >>>> toomas >>>>=20 >>>>=20 >>>>>=20 >>>>>> On 31. Jul 2018, at 14:16, Timo V=C3=B6lker = wrote: >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> I'm unable to boot up the amd64 11.2 via pxeboot using UEFI on a = Dell PowerEdge R430. I get this output >>>>>>=20 >>>>>> https://ibb.co/h5ntuT >>>>>>=20 >>>>>> If I press a key to interrupt reboot, I get to the OK prompt. If = I enter lsdev -v, it prints nothing more than "net devices:". The = variable currdev is not set (show currdev prints variable 'currdev' not = found). I configured pxeboot to be the one and only boot medium in BIOS = setup.=20 >>>>>>=20 >>>>>> However, I found a workaround that works for me. If I put an = (empty) USB stick in a USB port of the PowerEdge, it successfully boots = via pxeboot (which is still the one and only configured boot medium). I = then get this output >>>>>>=20 >>>>>> https://ibb.co/mU8SM8 >>>>>>=20 >>>>>> With FreeBSD 11.1 pxeboot worked on the Dell PowerEdge R430, even = without a USB stick plugged in. I couldn't test this with FreeBSD = 12-current. Hope this helps anyway to find an open issue. >>>>>>=20 >>>>>> I found this thread which seems to be related. >>>>>>=20 >>>>>> = https://lists.freebsd.org/pipermail/freebsd-current/2018-July/070082.html >>>>>>=20 >>>>>> Thanks, >>>>>>=20 >>>>>> Timo >>>>>=20 >>>>=20 >>>=20 >>=20 >=20 --Apple-Mail=_CC385DA5-9338-491F-B7D1-F70CCCF6D922 Content-Disposition: attachment; filename="smime.p7s" Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQsDCCBRIw ggP6oAMCAQICCQDjC9X4ryXZgTANBgkqhkiG9w0BAQsFADCBgjELMAkGA1UEBhMCREUxKzApBgNV BAoMIlQtU3lzdGVtcyBFbnRlcnByaXNlIFNlcnZpY2VzIEdtYkgxHzAdBgNVBAsMFlQtU3lzdGVt cyBUcnVzdCBDZW50ZXIxJTAjBgNVBAMMHFQtVGVsZVNlYyBHbG9iYWxSb290IENsYXNzIDIwHhcN MTYwMjIyMTMzODIyWhcNMzEwMjIyMjM1OTU5WjCBlTELMAkGA1UEBhMCREUxRTBDBgNVBAoTPFZl cmVpbiB6dXIgRm9lcmRlcnVuZyBlaW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBW LjEQMA4GA1UECxMHREZOLVBLSTEtMCsGA1UEAxMkREZOLVZlcmVpbiBDZXJ0aWZpY2F0aW9uIEF1 dGhvcml0eSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAy2DX/2ahQc3S+oeXinOr mU3qZzlaoWCARxVOjJWy5c/O01dLjc74VmwVVXYH6kb9yANFYz5w1KtUgLEjnL43KKkJ/wVdGA/E mJk3syD2ZngXh8KdDsxKMucWna4OjSl5BwAgVNwVX0qW13i2NNPBdLWd6b/Ad03qvVkH4FovbDyl ANw1vWUNj38ybfJaaktiAe6sODRZRTZJBdp4ymptW8CBaxHM0jyoi/hxGso74oDdFrRneos26k6R KT2zUVytqAy+nTTj0Q0Xg3XEOR6wlAsS8dVpjiX0uD0rv8COwx47pb9VEKsqrheXXjPOyPP0CQfj AoYxRmsBxRAMEcdZ6QIDAQABo4IBdDCCAXAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBST49gy JtrV8UqlkUrg6kviogzP4TAfBgNVHSMEGDAWgBS/WSA2AHmgoCJrjNXyYdK4LMuCSjASBgNVHRMB Af8ECDAGAQH/AgECMDMGA1UdIAQsMCowDwYNKwYBBAGBrSGCLAEBBDANBgsrBgEEAYGtIYIsHjAI BgZngQwBAgIwTAYDVR0fBEUwQzBBoD+gPYY7aHR0cDovL3BraTAzMzYudGVsZXNlYy5kZS9ybC9U ZWxlU2VjX0dsb2JhbFJvb3RfQ2xhc3NfMi5jcmwwgYYGCCsGAQUFBwEBBHoweDAsBggrBgEFBQcw AYYgaHR0cDovL29jc3AwMzM2LnRlbGVzZWMuZGUvb2NzcHIwSAYIKwYBBQUHMAKGPGh0dHA6Ly9w a2kwMzM2LnRlbGVzZWMuZGUvY3J0L1RlbGVTZWNfR2xvYmFsUm9vdF9DbGFzc18yLmNlcjANBgkq hkiG9w0BAQsFAAOCAQEAhwv/PgKbZchWLdY7mpiLcU/auimqIflGLvWypA+uETh5OLMOdLp2XZ7o GIKWYttMM+jd+WrfMr0sTEdgVX/ndGu0LIPYeWu2t01QC2YHte2zl63q7n8w5pn9IuJyTT6EW+75 z5nqf9dSOS6smABEfmk7v3Xu0As7Gs3l9w8ibEeE9qVHoP3QGjR9rdI9d7Pu9NdN/8Po5ZJPWT6Q RxBKsIVYwG9/+K7tCEKeHtTfFC5Nj7yelMPn7fYY+DxJ5yaopzbYLN4izYuC2Nl44lUSozuHRLYR C9UMUq9pjA8G39CiU4tXmHvP/Qck9Py9w/1KkgKXG/K3ts9lihqitXIZOTCCBawwggSUoAMCAQIC BxtjutAeLD0wDQYJKoZIhvcNAQELBQAwgZUxCzAJBgNVBAYTAkRFMUUwQwYDVQQKEzxWZXJlaW4g enVyIEZvZXJkZXJ1bmcgZWluZXMgRGV1dHNjaGVuIEZvcnNjaHVuZ3NuZXR6ZXMgZS4gVi4xEDAO BgNVBAsTB0RGTi1QS0kxLTArBgNVBAMTJERGTi1WZXJlaW4gQ2VydGlmaWNhdGlvbiBBdXRob3Jp dHkgMjAeFw0xNjA1MjQxMTM4NDBaFw0zMTAyMjIyMzU5NTlaMIGNMQswCQYDVQQGEwJERTFFMEMG A1UECgw8VmVyZWluIHp1ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0 emVzIGUuIFYuMRAwDgYDVQQLDAdERk4tUEtJMSUwIwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJ c3N1aW5nIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnTt5HEfeH4bLxmnXEJ45 19miMNtyHAV/KV9LaPGtGdZM4WsbsQt/oavge4uL2C3Obog6EO5X5R5/BFE267pwbWOgvpYuQOHR g0xmPRxkaeWbpK1yrmg5UYd5zBfTri9dY3FLOXrrQqeXkGkFv5D/pEBwvQPnv54YiB+fmYhNDkeN SF9lmRDS2SpJ7cG5LR2fEssV0z9/HlQvOq6TV6d+eMrVSuIa5e1BfVNfyLMq9YowrO0XBSQ/tqAL B/1NGpoDUqA2nN4kh2Xk5/rHlnMkFM3Q6BtonhhZrnZ+99EKeDyHS7A3z1PKOjgQ88tHbYxkPTxa RUq6yoB8uPPnp0xMzQIDAQABo4ICBTCCAgEwEgYDVR0TAQH/BAgwBgEB/wIBATAOBgNVHQ8BAf8E BAMCAQYwKQYDVR0gBCIwIDANBgsrBgEEAYGtIYIsHjAPBg0rBgEEAYGtIYIsAQEEMB0GA1UdDgQW BBRrOpiL+fJTidrgrbIyHgkf6Ko7dDAfBgNVHSMEGDAWgBST49gyJtrV8UqlkUrg6kviogzP4TCB jwYDVR0fBIGHMIGEMECgPqA8hjpodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWcy LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMECgPqA8hjpodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2Jh bC1yb290LWcyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHdBggrBgEFBQcBAQSB0DCBzTAzBggrBgEF BQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEoGCCsGAQUFBzAC hj5odHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWcyLWNhL3B1Yi9jYWNlcnQvY2Fj ZXJ0LmNydDBKBggrBgEFBQcwAoY+aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1n Mi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAIF4RaROpH8OVfAJ sWo+eMxoNakc85WeP/P432s4d4ksjbWtPsfylM2gBq66zKixrTMItiSGYjZMeG5Q8NVuYI1PUjFD l0Z18GLkbmZRwUIxZ1DlSec5HsufyoZI3ggU/xVLK2aboDifAM79p+vRf1ctyExf3BARlz6WBAJc hKgpOWyU/BCSBnue7thGtBu1Aww42dywqT9xBguyAwczwo1IYyUlPHp7V273igU477igri/02wfV W4QYwam4S85skBqC5Lk9+nfx0h8zAr9T53b53CYlQW8vphv6pBOQ+nx+2QtgXey/ykGgYfsRSSnY qC11FdhKGOoW71U0IhoTjQYwggXmMIIEzqADAgECAgwdgtH8FJ0VCMZ26e4wDQYJKoZIhvcNAQEL BQAwgY0xCzAJBgNVBAYTAkRFMUUwQwYDVQQKDDxWZXJlaW4genVyIEZvZXJkZXJ1bmcgZWluZXMg RGV1dHNjaGVuIEZvcnNjaHVuZ3NuZXR6ZXMgZS4gVi4xEDAOBgNVBAsMB0RGTi1QS0kxJTAjBgNV BAMMHERGTi1WZXJlaW4gR2xvYmFsIElzc3VpbmcgQ0EwHhcNMTcwNzEwMTAxODIwWhcNMjAwNzA5 MTAxODIwWjB6MQswCQYDVQQGEwJERTEgMB4GA1UECgwXRmFjaGhvY2hzY2h1bGUgTXVlbnN0ZXIx MjAwBgNVBAsMKUZhY2hiZXJlaWNoIEVsZWt0cm90ZWNobmlrIHVuZCBJbmZvcm1hdGlrMRUwEwYD VQQDDAxUaW1vIFZvZWxrZXIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC/gQYu/Hjb 3078pLzYaFpcgo/JHZHLjOLe85YFMr056WFSN/Jwdh1Asny4ZKcLzHd7vMjr3fjg8Sgo04y+lBI4 8O5FJTgixYB1oV9DU5GlWcC/6eLhpIPNraOcK4KJVlwqw7uc1L8fbyjCMrTNtYHFEy23B9NFgxbS pxhQ6FCgS6kjziTgFL6s072+j6MMJi1RdZZUNZGq52gCyIKNAxMt2b42/Kk7PTWYCSA8HzxrLsQe YxmxoxLoGTlnZxuC8WKU+1V1pUiS+Ns3krHHBHIeeogR/JeILBX0OheqStUnnEABcsWj+4uGYxvP RdZXBXm8wKjcRcnJDrKizS4G6j27AgMBAAGjggJWMIICUjBABgNVHSAEOTA3MBEGDysGAQQBga0h giwBAQQDBTARBg8rBgEEAYGtIYIsAgEEAwEwDwYNKwYBBAGBrSGCLAEBBDAJBgNVHRMEAjAAMA4G A1UdDwEB/wQEAwIF4DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFOOJ r1RvTOvocygvlHm6xGfZS5dNMB8GA1UdIwQYMBaAFGs6mIv58lOJ2uCtsjIeCR/oqjt0MCYGA1Ud EQQfMB2BG3RpbW8udm9lbGtlckBmaC1tdWVuc3Rlci5kZTCBjQYDVR0fBIGFMIGCMD+gPaA7hjlo dHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Rmbi1jYS1nbG9iYWwtZzIvcHViL2NybC9jYWNybC5jcmww P6A9oDuGOWh0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZGZuLWNhLWdsb2JhbC1nMi9wdWIvY3JsL2Nh Y3JsLmNybDCB2wYIKwYBBQUHAQEEgc4wgcswMwYIKwYBBQUHMAGGJ2h0dHA6Ly9vY3NwLnBjYS5k Zm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBJBggrBgEFBQcwAoY9aHR0cDovL2NkcDEucGNhLmRmbi5k ZS9kZm4tY2EtZ2xvYmFsLWcyL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDBJBggrBgEFBQcwAoY9aHR0 cDovL2NkcDIucGNhLmRmbi5kZS9kZm4tY2EtZ2xvYmFsLWcyL3B1Yi9jYWNlcnQvY2FjZXJ0LmNy dDANBgkqhkiG9w0BAQsFAAOCAQEAGEYW34tG4ACeQk3vN6TBr9HRRE4Rc3tJoh5odaAx4UDnO6B7 EsTOSyZmJ5jdY6ui8ns9jiwwv6yZsuhopqSatS06aSlXoJ7GWBeTS9FbDu4Fa3+Hmfo+UiqG0cul MLOfKasuZx8bsoOq1kR7WdABUL3m7FuLhIVEeuJ39yQSiWxwJ4jZ5Cx0evaXIcGDIXOE9e+GcXz2 mm1yfFxITLHt5q37phfTDLH4IOgWt9GORlDBoatSu56QwfRGwhVYmkTRrUFss3QuQ/z3SwOt30Lj MNdVk6OkQBNj9QBH5PSH/Ok/JIQODVotZWG7HQ8/8nyzYTH0ccW/1HIrCwvKicZJcTGCA40wggOJ AgEBMIGeMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8VmVyZWluIHp1ciBGb2VyZGVydW5nIGVp bmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYuMRAwDgYDVQQLDAdERk4tUEtJMSUw IwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5nIENBAgwdgtH8FJ0VCMZ26e4wCQYFKw4D AhoFAKCCAcMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTgwODAz MTE1MDE0WjAjBgkqhkiG9w0BCQQxFgQUBTLB6yhWFmmb6QWylSwlcseWPRIwga8GCSsGAQQBgjcQ BDGBoTCBnjCBjTELMAkGA1UEBhMCREUxRTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9lcmRlcnVuZyBl aW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBWLjEQMA4GA1UECwwHREZOLVBLSTEl MCMGA1UEAwwcREZOLVZlcmVpbiBHbG9iYWwgSXNzdWluZyBDQQIMHYLR/BSdFQjGdunuMIGxBgsq hkiG9w0BCRACCzGBoaCBnjCBjTELMAkGA1UEBhMCREUxRTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9l cmRlcnVuZyBlaW5lcyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBWLjEQMA4GA1UECwwH REZOLVBLSTElMCMGA1UEAwwcREZOLVZlcmVpbiBHbG9iYWwgSXNzdWluZyBDQQIMHYLR/BSdFQjG dunuMA0GCSqGSIb3DQEBAQUABIIBAJKTGVAIMRexQugbu3ZjScT4XFOK4MovisI4kIh4a8QXhcnt lGwQVXalIdbtBrIqDlWlYJM5AHpU8H0UqKoaLWj4jcjXP6lV8P2KIvsOUEdFjvbhpMQN2YjFV1An ZHq0IMXi33iv5klaxC7wmMyn/rVu7E6hGzbeCe4Mj6o/9dHqjv5yHvfLnOVSeMT1t4taHrBFYAom fNGtRFlCofidNxxdGJw9OBq3gMSEndWFeFXaJZ9T9Hd64qEAw0qY4Q2H5LibYABtwjq3LGRrwJBn 0TFaFtZIuuNWdRQqlWAEkn4i2ZLjTqh8GDx4K/+gaFTvKCqDXj7XhE/S0bQJDLTy+30AAAAAAAA= --Apple-Mail=_CC385DA5-9338-491F-B7D1-F70CCCF6D922-- From owner-freebsd-current@freebsd.org Fri Aug 3 14:38:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3189A106BEEE for ; Fri, 3 Aug 2018 14:38:18 +0000 (UTC) (envelope-from ian@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 C79F38647A for ; Fri, 3 Aug 2018 14:38:17 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8947B106BEED; Fri, 3 Aug 2018 14:38:17 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77E64106BEEC for ; Fri, 3 Aug 2018 14:38:17 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 EDC0686478 for ; Fri, 3 Aug 2018 14:38:16 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 988593a3-9728-11e8-93fa-f3ebd9db2b94 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 988593a3-9728-11e8-93fa-f3ebd9db2b94; Fri, 03 Aug 2018 14:22:06 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w73EM466043371; Fri, 3 Aug 2018 08:22:04 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533306124.1454.2.camel@freebsd.org> Subject: Re: ntpd user/group issue From: Ian Lepore To: Daniel Braniss , FreeBSD Current Date: Fri, 03 Aug 2018 08:22:04 -0600 In-Reply-To: <1C5B5B84-7FF1-489B-9607-11F1432B7C1E@cs.huji.ac.il> References: <1C5B5B84-7FF1-489B-9607-11F1432B7C1E@cs.huji.ac.il> Content-Type: text/plain; charset="iso-8859-7" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 14:38:18 -0000 On Fri, 2018-08-03 at 10:31 +0300, Daniel Braniss wrote: > Hi, > I am cross compiling, which means i¢m using for example an 11.1 to > compile current, for > another host - an image which is different from the one i'm using to > compile. > > make install checks for ntpd in /etc, instead, should it look > elsewhere? DESTDIR perhaps? > > cheers, > danny > Add -DDB_FROM_SRC to the make command when you're installing, to work around this. Fixing the build system to automatically do so isn't as easy as you might think, but I've been working on it in slow motion. -- Ian From owner-freebsd-current@freebsd.org Fri Aug 3 16:55:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF2C7106ED35 for ; Fri, 3 Aug 2018 16:55:09 +0000 (UTC) (envelope-from tommi.pernila@gmail.com) Received: from mail-qt0-f172.google.com (mail-qt0-f172.google.com [209.85.216.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C4628C2FF; Fri, 3 Aug 2018 16:55:09 +0000 (UTC) (envelope-from tommi.pernila@gmail.com) Received: by mail-qt0-f172.google.com with SMTP id z8-v6so6823023qto.9; Fri, 03 Aug 2018 09:55:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=u6zuYV8T6atIOxIQCwYkG3l8KuTDfxcTOgdOm9QUP6k=; b=TaSNhiwvqpo+9xLhtcCF8225mroXaFGi6uwxf/FT3baQWMyPHcQqYqQ+LsjOZhFztw Qe38yYXu1pwEGiRMQQI3zrPNGXXUTmv2QQyLGopv5VXAjyPg3EqqhMyNU/hBNLpS24/i NAlAHweFJJbyXcObfBtaEPH0x8l5DsE7tJjOWz4dXIim1kYaMP0XrA/UASNvVl7Lgwf0 9jcGMcoONItZFkDwfK4ICOUZy18qh4jcUZ+M6Qp35oQ481/sYGcrEG7j9NkVs8Rr1aJv RTZUG9m+E3/MMJR71Whu0KHVT/dZfpUlOEnfYmfvdBBVhQfDxavDhjJv438h/yR3KZWp 3lAQ== X-Gm-Message-State: AOUpUlEaGt7P6gtDhDDqjHpiVpJ0b0q/XF8MEFaHeSg8iBbhqygOiCTF 7uUq3gK7cPyfUFHs7SRmer4CitBVK5yGVkCUrlc= X-Google-Smtp-Source: AAOMgpdgh4WaNOWJRfhCTi6qUmB5zGc4+QrSdHjSGrmSnFlnkZ9Dc0SOXzWJDX09VCN61dl8yVsfR9z6Sk91fMFUEGk= X-Received: by 2002:ac8:3159:: with SMTP id h25-v6mr4723114qtb.305.1533315302883; Fri, 03 Aug 2018 09:55:02 -0700 (PDT) MIME-Version: 1.0 References: <0e75a2ba-9a59-8301-a678-68a822025bd6@metricspace.net> <9df63df2-9d61-4106-f360-347411869b41@metricspace.net> <5ba11024-e99b-86e1-48b7-125fb80b4001@metricspace.net> <1531078307.1336.22.camel@freebsd.org> <06cb8190-7a04-5c92-8fb9-637d1a80758f@freebsd.org> In-Reply-To: From: Tommi Pernila Date: Fri, 3 Aug 2018 19:54:51 +0300 Message-ID: Subject: Re: GELI with UEFI supporting Boot Environments goes to HEAD when? To: Warner Losh Cc: Allan Jude , Eric McCorkle , Ian Lepore , Oliver Pinter , Warner Losh , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 16:55:10 -0000 On Tue, 10 Jul 2018 at 1.05, Warner Losh wrote: > I have this in my tree already... > > Warner > > On Mon, Jul 9, 2018, 10:28 AM Allan Jude wrote: > >> I will look at updating the rootgen.sh script this evening, to support >> creating more flexible ESP partitions, so we can drop the loader.efi >> into an msdosfs directly. >> >> On 07/08/2018 15:31, Ian Lepore wrote: >> > On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote: >> >> Hi! >> >> >> >> Have you or Warner any update on this code? >> >> >> >> On Thursday, April 12, 2018, Eric McCorkle >> >> wrote: >> >> >> > >> > Are you aware of https://reviews.freebsd.org/D15743 ? >> > >> > That's my changes to add geli support to loader(8) in an architecture- >> > agnostic way, so that "it just works" for all platforms and flavors of >> > loader. It has been succesfully tested on armv6/7 (ubldr) and on x86 >> > using qemu. The x86 tests cover ufs and zfs, legacy bios and uefi. The >> > only variations that aren't tested yet are the uefi flavors, because >> > the current rootgen.sh script for assembling test images is still using >> > boot1.efi and I don't know enough about efi myself to update the script >> > to make it assemble images the new way Warner envisions. >> > >> > -- Ian >> > >> >>> >> >>> I'm in the middle of moving to a new apartment right now. It's >> >>> going to >> >>> be a bit before I can get to this. >> >>> >> >>> On 04/11/2018 20:31, Warner Losh wrote: >> >>>> >> >>>> OK. I've pushed in the main part of it. The additional work I >> >>>> have >> >>>> shouldn't affect any of this stuff. I was going to look at what >> >>>> part(s) >> >>>> of your open reviewed needed to be redone tomorrow and send you >> >>>> feedback, but if you wanted to get a start before then, I'm happy >> >>>> to >> >>>> answer questions. All the rest of my work is going to be >> >>>> selecting the >> >>>> root partition when we're told to us a specific partition, so >> >>>> will be >> >>>> very constrained. >> >>>> >> >>>> Warner >> >>>> >> >>>> On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle > >>>> net >> >>>> > wrote: >> >>>> >> >>>> I think the thing to do at this point is to wait for the >> >>>> current >> >>> work on >> >>>> >> >>>> loader.efi to land, then adapt my patches to apply against >> >>>> that work. >> >>>> >> >>>> On 04/11/2018 15:06, Warner Losh wrote: >> >>>> > Still reviewing the code. I'm worried it's too i386 >> >>>> specific and it >> >>>> > conflicts with some work I'm doing. I'll have a list of >> >>>> actionable >> >>>> > critiques this week. >> >>>> > >> >>>> > Warner >> >>>> > >> >>>> > On Wed, Apr 11, 2018 at 1:03 PM, Oliver Pinter >> >>>> > > >>>> >> >>>> > >>>> >> >> >>>> > wrote: >> >>>> > >> >>>> > Hi! >> >>>> > >> >>>> > Is there any update regarding the rebase or the >> >>>> inclusion to >> >>> base >> >>>> >> >>>> > system? >> >>>> > On 3/28/18, Eric McCorkle > >>>> > >>> eric@metricspace.net> >> >>>> >> >>>> > > >>>> et>>> >> >>> wrote: >> >>>> >> >>>> > > I'll do another rebase from head just to be sure >> >>>> > > >> >>>> > > On March 28, 2018 3:23:23 PM EDT, Warner Losh < >> >>> imp@bsdimp.com >> >>>> >> >>>> > >> wrote: >> >>>> > >>It's on my list for nexr, finally. I have an >> >>>> alternate patch >> >>> for >> >>>> >> >>>> > >>loader.efi >> >>>> > >>from ESP, but i don't think it will affect the GELI >> >>>> stuff. I >> >>> have some >> >>>> >> >>>> > >>time >> >>>> > >>slotted for integration issues though. >> >>>> > >> >> >>>> > >>I am quite mindful of the freeze dates.... I have >> >>>> some uefi >> >>> boot >> >>>> >> >>>> > >>loader >> >>>> > >>protocol changes that I need to get in. >> >>>> > >> >> >>>> > >>Warner >> >>>> > >> >> >>>> > >>On Feb 21, 2018 11:18 PM, "Tommi Pernila" < >> >>> tommi.pernila@iki.fi >> >>>> >> >>>> > > >>>> fi>>> >> >>> wrote: >> >>>> >> >>>> > >> >> >>>> > >>> Awesome, thanks for the update and the work that >> >>>> you have >> >>> done! >> >>>> >> >>>> > >>> >> >>>> > >>> Now we just need some more reviewers eyes on the >> >>>> code :) >> >>>> > >>> >> >>>> > >>> Br, >> >>>> > >>> >> >>>> > >>> Tommi >> >>>> > >>> >> >>>> > >>> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle < >> >>> eric@metricspace.net >> >>>> >> >>>> > > >>>> et>>> >> >>>> > >>wrote: >> >>>> > >>> >> >>>> > >>>> FYI, I just IFC'ed everything, and the current >> >>>> patches >> >>>> are still >> >>>> > >>fine. >> >>>> > >>>> >> >>>> > >>>> Also, the full GELI + standalone loader has been >> >>>> deployed >> >>>> on one of >> >>>> > >>my >> >>>> > >>>> laptops for some time now. >> >>>> > >>>> >> >>>> > >>>> On 02/21/2018 18:15, Eric McCorkle wrote: >> >>>> > >>>> > The GELI work could be merged at this point, >> >>>> though it >> >>>> won't be >> >>>> > >>usable >> >>>> > >>>> > without an additional patch to enable loader- >> >>>> only >> >>>> operation. The >> >>>> > >>>> > patches are currently up for review: >> >>>> > >>>> > >> >>>> > >>>> > This is the order in which they'd need to be >> >>>> merged: >> >>>> > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > https://reviews.freebsd.org/D12732 >> >>>> >> >>>> > > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > This one changes the efipart device. Toomas >> >>>> Soome >> >>>> identified >> >>>> > some >> >>>> > >>>> > problems, which I have addressed. He has not >> >>>> re-reviewed it, >> >>>> > >>however. >> >>>> > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > https://reviews.freebsd.org/D12692 >> >>>> >> >>>> > > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > This adds some crypto code needed for GELI. It >> >>>> simply >> >>>> adds new >> >>>> > >>code, >> >>>> > >>>> > and doesn't conflict with anything. >> >>>> > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > https://reviews.freebsd.org/D12698 >> >>>> >> >>>> > > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > This adds the EFI KMS interface code, and has >> >>>> the EFI >> >>>> loader pass >> >>>> > >>keys >> >>>> > >>>> > into the keybuf interface. >> >>>> > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > I can't post the main GELI driver until those >> >>>> get >> >>>> merged, as it >> >>>> > >>depends >> >>>> > >>>> > on them. It can be found on the geli branch on >> >>>> my >> >>>> github freebsd >> >>>> > >>>> > repository, however. >> >>>> > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > Additionally, you need this patch, which allows >> >>>> loader.efi to >> >>>> > >>function >> >>>> > >>>> > when installed directly to the ESP: >> >>>> > >>>> > >> >>>> > >>>> > https://reviews.freebsd.org/D13497 >> >>>> >> >>>> > > >>>> > >> >>>> > >>>> > >> >>>> > >>>> > On 02/20/2018 22:56, Tommi Pernila wrote: >> >>>> > >>>> >> Hi Eric, >> >>>> > >>>> >> >> >>>> > >>>> >> could you provide a brief update how the work >> >>>> is going? >> >>>> > >>>> >> >> >>>> > >>>> >> >> >>>> > >>>> >> Br, >> >>>> > >>>> >> >> >>>> > >>>> >> Tommi >> >>>> > >>>> >> >> >>>> > >>>> >> >> >>>> > >>>> >> On Nov 16, 2017 04:29, "Eric McCorkle" >> >>>> >> >>>> > > >>>> et>> >> >>>> > >>>> >> > >>>> > >>>> >>> >> >>>> > wrote: >> >>>> > >>>> >> >> >>>> > >>>> >> Right, so basically, the remaining GELI >> >>>> patches >> >>>> are against >> >>>> > >>>> loader, and >> >>>> > >>>> >> most of them can go in independently of the >> >>>> work >> >>>> on removing >> >>>> > >>boot1. >> >>>> > >>>> >> There's a unanimous consensus on getting >> >>>> rid of >> >>>> boot1 which >> >>>> > >>>> includes its >> >>>> > >>>> >> original author, so that's going to happen. >> >>>> > >>>> >> >> >>>> > >>>> >> >> >>>> > >>>> >> For GELI, we have the following (not >> >>>> necessarily >> >>>> in order): >> >>>> > >>>> >> >> >>>> > >>>> >> a) Adding the KMS interfaces, pseudo- >> >>>> device, and >> >>>> kernel >> >>>> > >>keybuf >> >>>> > >>>> >> interactions >> >>>> > >>>> >> b) Modifications to the efipart driver >> >>>> > >>>> >> c) boot crypto >> >>>> > >>>> >> d) GELI partition types (not strictly >> >>>> necessary) >> >>>> > >>>> >> >> >>>> > >>>> >> Then there's the GELI driver itself. (a) >> >>>> and (c) >> >>> are >> >>>> >> >>>> > good to >> >>>> > >>>> land, (b) >> >>>> > >>>> >> needs some more work after Toomas Soome >> >>>> pointed >> >>> out a >> >>>> >> >>>> > >>legitimate >> >>>> > >>>> >> problem, and (d) actually needs a good bit >> >>>> more >> >>>> code (but >> >>>> > >>again, >> >>>> > >>>> it's >> >>>> > >>>> >> more cosmetic). Additionally, the GELI >> >>>> driver >> >>>> will need >> >>>> > >>further >> >>>> > >>>> mods to >> >>>> > >>>> >> efipart to be written (nothing too >> >>>> big). But we >> >>>> could go >> >>>> > >>ahead >> >>>> > >>>> with (a) >> >>>> > >>>> >> and (c), as they've already been proven to >> >>>> work. >> >>>> > >>>> >> >> >>>> > >>>> >> I'd wanted to have this stuff shaped up >> >>>> sooner, >> >>>> but I'm >> >>>> > >>>> preoccupied with >> >>>> > >>>> >> the 7th RISC-V workshop at the end of the >> >>>> month. >> >>>> > >>>> >> >> >>>> > >>>> >> Once this stuff is all in, loader should >> >>>> handle >> >>>> any GELI >> >>>> > >>volumes it >> >>>> > >>>> >> finds, and it should Just Work once boot1 >> >>>> is gone. >> >>>> > >>>> >> >> >>>> > >>>> >> >> >>>> > >>>> > _______________________________________________ >> >>>> > >>>> > freebsd-current@freebsd.org >> >>>> >> >>>> > > >>>> > mailing list >> >>>> > >>>> > https://lists.freebsd.org/mailman/listinfo/freeb >> >>>> sd- >> >>> current >> >>>> >> >>>> >> >>>> > > >>>> rent >> >>>> > >> >>>> > >>>> > To unsubscribe, send any mail to >> >>> "freebsd-current-unsubscribe@ >> >>>> >> >>>> > >>>> freebsd.org >> >>>> " >> >>>> > >>>> > >> >>>> > >>>> >> >>>> > >>> >> >>>> > > >> >>>> > > -- >> >>>> > > Sent from my Android device with K-9 Mail. Please >> >>>> excuse my >> >>> brevity. >> >>>> >> >>>> > > _______________________________________________ >> >>>> > > freebsd-current@freebsd.org >> >>>> >> >>>> > >>>> > >> >>>> > mailing list >> >>>> > > https://lists.freebsd.org/mailman/listinfo/freebsd-cu >> >>>> rrent >> >>>> >> >>>> > > >>>> rent >> >>>> > >> >>>> > > 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" >> >> -- >> Allan Jude >> > Hi all, could anyone comment on the overall status of this feature? Is it going to make in 12.0 as it's code freeze is nearing up? Br, Tommi From owner-freebsd-current@freebsd.org Fri Aug 3 17:12:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 305AB106F182 for ; Fri, 3 Aug 2018 17:12:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF4E28CC36 for ; Fri, 3 Aug 2018 17:12:48 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x234.google.com with SMTP id z20-v6so5609754iol.0 for ; Fri, 03 Aug 2018 10:12:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hrBjNWeeIRR/l6GVriuEpeuk95LBuTMcDJ+XjLKYyQ0=; b=iT0B60Y0sOVTQLzWFEbvO1sby8hkqzc0nuDR69FZf6DGWfA/ajhzA8cex2lePHJwNK fLP/LtD3KP1cTuouzioSyLIRQJYN5w8xobPEOq+0lRmxDayS7hziRAE/yAiWeNmP0Rq4 YPvw9hB0ftgzY4/h20Fi/eOBRRwqCGIa5qL1nLPv0kgru2lty/VF4CRU5N9FNBpwqcMR 9HyM+Xz4Q3+TIggFCxh8d/QvAoAjurDfaz2pCT27k5vuHZKvEtr0IMOCPiU9T3vlQACw sl0MnADiUB1+JmDfuPYdflOU9hJoXl8mj7n2pKqpQ5lRCSBPJT8EGWxULKH73PkemH/+ HEOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hrBjNWeeIRR/l6GVriuEpeuk95LBuTMcDJ+XjLKYyQ0=; b=TpspxoSCzR7P2K9/w/C5k455bZD7dr4ue5UzQo4UXMHb+JaGFbj5+LGdFn8lXWGlhm rmIhLbC6hVmKMLG8S4eQYM0+LRxoYUof53p5I3UGAioye6UB7jwZk7vWKBYxXYZFECZk WnVxmwqP9oyrkwsJgm+Q4+KtXdEvL+KmB/RPdU89wiub1KS5BHQGuXSpaP0HbzIMmoWP NvdBFV+qZllWV4z5kxvIEuv7HYVsVbXp9VAKvPLPCWcPzscxAw7FeKaciWICxiPdTbCy yp7BIZw2EVSFBGysW/UmSIZ+uBncMOEwEB/QAEINN2Nd9gdNfHWX8WQBmHYXeX3riDci JiBQ== X-Gm-Message-State: AOUpUlFPguIDhf3a02zard7YsZOh1P8S5VzTRhXSp+/D3p6mXTbvtzs7 QxSZ1QWPfrI2Z5kzcTxqp1JRExs3rTPCqH3l34YtUw== X-Google-Smtp-Source: AA+uWPzETGqdMCeA11h77tIkzUrW9y1G7GPntXcmhNOodpVNhF7CCiJT9bhVXPU1Pc8rU2Pft18mzaQmIM03nkQxR9E= X-Received: by 2002:a6b:f719:: with SMTP id k25-v6mr628503iog.37.1533316367762; Fri, 03 Aug 2018 10:12:47 -0700 (PDT) MIME-Version: 1.0 References: <0e75a2ba-9a59-8301-a678-68a822025bd6@metricspace.net> <9df63df2-9d61-4106-f360-347411869b41@metricspace.net> <5ba11024-e99b-86e1-48b7-125fb80b4001@metricspace.net> <1531078307.1336.22.camel@freebsd.org> <06cb8190-7a04-5c92-8fb9-637d1a80758f@freebsd.org> <1533315524.1454.13.camel@freebsd.org> In-Reply-To: <1533315524.1454.13.camel@freebsd.org> From: Warner Losh Date: Fri, 3 Aug 2018 18:12:31 +0100 Message-ID: Subject: Re: GELI with UEFI supporting Boot Environments goes to HEAD when? To: Ian Lepore Cc: Tommi Pernila , Allan Jude , Eric McCorkle , Oliver Pinter , Warner Losh , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 17:12:49 -0000 On Fri, Aug 3, 2018, 5:58 PM Ian Lepore wrote: > On Fri, 2018-08-03 at 19:54 +0300, Tommi Pernila wrote: > > On Tue, 10 Jul 2018 at 1.05, Warner Losh wrote: > > > > > > > > I have this in my tree already... > > > > > > Warner > > > > > > On Mon, Jul 9, 2018, 10:28 AM Allan Jude > > > wrote: > > > > > > > > > > > I will look at updating the rootgen.sh script this evening, to > > > > support > > > > creating more flexible ESP partitions, so we can drop the > > > > loader.efi > > > > into an msdosfs directly. > > > > > > > > On 07/08/2018 15:31, Ian Lepore wrote: > > > > > > > > > > On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote: > > > > > > > > > > > > Hi! > > > > > > > > > > > > Have you or Warner any update on this code? > > > > > > > > > > > > On Thursday, April 12, 2018, Eric McCorkle > > > > > net> > > > > > > wrote: > > > > > > > > > > > Are you aware of https://reviews.freebsd.org/D15743 ? > > > > > > > > > > That's my changes to add geli support to loader(8) in an > > > > > architecture- > > > > > agnostic way, so that "it just works" for all platforms and > > > > > flavors of > > > > > loader. It has been succesfully tested on armv6/7 (ubldr) and > > > > > on x86 > > > > > using qemu. The x86 tests cover ufs and zfs, legacy bios and > > > > > uefi. The > > > > > only variations that aren't tested yet are the uefi flavors, > > > > > because > > > > > the current rootgen.sh script for assembling test images is > > > > > still using > > > > > boot1.efi and I don't know enough about efi myself to update > > > > > the script > > > > > to make it assemble images the new way Warner envisions. > > > > > > > > > > -- Ian > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm in the middle of moving to a new apartment right > > > > > > > now. It's > > > > > > > going to > > > > > > > be a bit before I can get to this. > > > > > > > > > > > > > > On 04/11/2018 20:31, Warner Losh wrote: > > > > > > > > > > > > > > > > > > > > > > > > OK. I've pushed in the main part of it. The additional > > > > > > > > work I > > > > > > > > have > > > > > > > > shouldn't affect any of this stuff. I was going to look > > > > > > > > at what > > > > > > > > part(s) > > > > > > > > of your open reviewed needed to be redone tomorrow and > > > > > > > > send you > > > > > > > > feedback, but if you wanted to get a start before then, > > > > > > > > I'm happy > > > > > > > > to > > > > > > > > answer questions. All the rest of my work is going to be > > > > > > > > selecting the > > > > > > > > root partition when we're told to us a specific > > > > > > > > partition, so > > > > > > > > will be > > > > > > > > very constrained. > > > > > > > > > > > > > > > > Warner > > > > > > > > > > > > > > > > On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle > > > > > > > icspace. > > > > > > > > net > > > > > > > > > wrote: > > > > > > > > > > > > > > > > I think the thing to do at this point is to wait for > > > > > > > > the > > > > > > > > current > > > > > > > work on > > > > > > > > > > > > > > > > > > > > > > > > loader.efi to land, then adapt my patches to apply > > > > > > > > against > > > > > > > > that work. > > > > > > > > > > > > > > > > On 04/11/2018 15:06, Warner Losh wrote: > > > > > > > > > Still reviewing the code. I'm worried it's too > > > > > > > > i386 > > > > > > > > specific and it > > > > > > > > > conflicts with some work I'm doing. I'll have a > > > > > > > > list of > > > > > > > > actionable > > > > > > > > > critiques this week. > > > > > > > > > > > > > > > > > > Warner > > > > > > > > > > > > > > > > > > On Wed, Apr 11, 2018 at 1:03 PM, Oliver Pinter > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi! > > > > > > > > > > > > > > > > > > Is there any update regarding the rebase or > > > > > > > > the > > > > > > > > inclusion to > > > > > > > base > > > > > > > > > > > > > > > > > > > > > > > > > system? > > > > > > > > > On 3/28/18, Eric McCorkle > > > > > > > t > > > > > > > > > > > > > > eric@metricspace.net> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > icspace.n > > > > > > > > et>>> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > I'll do another rebase from head just to be > > > > > > > > sure > > > > > > > > > > > > > > > > > > > > On March 28, 2018 3:23:23 PM EDT, Warner > > > > > > > > Losh < > > > > > > > imp@bsdimp.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > > >>It's on my list for nexr, finally. I have an > > > > > > > > alternate patch > > > > > > > for > > > > > > > > > > > > > > > > > > > > > > > > > >>loader.efi > > > > > > > > > >>from ESP, but i don't think it will affect > > > > > > > > the GELI > > > > > > > > stuff. I > > > > > > > have some > > > > > > > > > > > > > > > > > > > > > > > > > >>time > > > > > > > > > >>slotted for integration issues though. > > > > > > > > > >> > > > > > > > > > >>I am quite mindful of the freeze dates.... > > > > > > > > I have > > > > > > > > some uefi > > > > > > > boot > > > > > > > > > > > > > > > > > > > > > > > > > >>loader > > > > > > > > > >>protocol changes that I need to get in. > > > > > > > > > >> > > > > > > > > > >>Warner > > > > > > > > > >> > > > > > > > > > >>On Feb 21, 2018 11:18 PM, "Tommi Pernila" < > > > > > > > tommi.pernila@iki.fi > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > nila@iki. > > > > > > > > fi>>> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > >>> Awesome, thanks for the update and the > > > > > > > > work that > > > > > > > > you have > > > > > > > done! > > > > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > > > >>> Now we just need some more reviewers eyes > > > > > > > > on the > > > > > > > > code :) > > > > > > > > > >>> > > > > > > > > > >>> Br, > > > > > > > > > >>> > > > > > > > > > >>> Tommi > > > > > > > > > >>> > > > > > > > > > >>> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle > > > > > > > > < > > > > > > > eric@metricspace.net > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > icspace.n > > > > > > > > et>>> > > > > > > > > > >>wrote: > > > > > > > > > >>> > > > > > > > > > >>>> FYI, I just IFC'ed everything, and the > > > > > > > > current > > > > > > > > patches > > > > > > > > are still > > > > > > > > > >>fine. > > > > > > > > > >>>> > > > > > > > > > >>>> Also, the full GELI + standalone loader > > > > > > > > has been > > > > > > > > deployed > > > > > > > > on one of > > > > > > > > > >>my > > > > > > > > > >>>> laptops for some time now. > > > > > > > > > >>>> > > > > > > > > > >>>> On 02/21/2018 18:15, Eric McCorkle wrote: > > > > > > > > > >>>> > The GELI work could be merged at this > > > > > > > > point, > > > > > > > > though it > > > > > > > > won't be > > > > > > > > > >>usable > > > > > > > > > >>>> > without an additional patch to enable > > > > > > > > loader- > > > > > > > > only > > > > > > > > operation. The > > > > > > > > > >>>> > patches are currently up for review: > > > > > > > > > >>>> > > > > > > > > > > >>>> > This is the order in which they'd need > > > > > > > > to be > > > > > > > > merged: > > > > > > > > > >>>> > > > > > > > > > > >>>> > > > > > > > > > > >>>> > https://reviews.freebsd.org/D12732 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > >>>> > This one changes the efipart > > > > > > > > device. Toomas > > > > > > > > Soome > > > > > > > > identified > > > > > > > > > some > > > > > > > > > >>>> > problems, which I have addressed. He > > > > > > > > has not > > > > > > > > re-reviewed it, > > > > > > > > > >>however. > > > > > > > > > >>>> > > > > > > > > > > >>>> > > > > > > > > > > >>>> > https://reviews.freebsd.org/D12692 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > >>>> > This adds some crypto code needed for > > > > > > > > GELI. It > > > > > > > > simply > > > > > > > > adds new > > > > > > > > > >>code, > > > > > > > > > >>>> > and doesn't conflict with anything. > > > > > > > > > >>>> > > > > > > > > > > >>>> > > > > > > > > > > >>>> > https://reviews.freebsd.org/D12698 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > >>>> > This adds the EFI KMS interface code, > > > > > > > > and has > > > > > > > > the EFI > > > > > > > > loader pass > > > > > > > > > >>keys > > > > > > > > > >>>> > into the keybuf interface. > > > > > > > > > >>>> > > > > > > > > > > >>>> > > > > > > > > > > >>>> > I can't post the main GELI driver until > > > > > > > > those > > > > > > > > get > > > > > > > > merged, as it > > > > > > > > > >>depends > > > > > > > > > >>>> > on them. It can be found on the geli > > > > > > > > branch on > > > > > > > > my > > > > > > > > github freebsd > > > > > > > > > >>>> > repository, however. > > > > > > > > > >>>> > > > > > > > > > > >>>> > > > > > > > > > > >>>> > Additionally, you need this patch, > > > > > > > > which allows > > > > > > > > loader.efi to > > > > > > > > > >>function > > > > > > > > > >>>> > when installed directly to the ESP: > > > > > > > > > >>>> > > > > > > > > > > >>>> > https://reviews.freebsd.org/D13497 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > >>>> > On 02/20/2018 22:56, Tommi Pernila > > > > > > > > wrote: > > > > > > > > > >>>> >> Hi Eric, > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> could you provide a brief update how > > > > > > > > the work > > > > > > > > is going? > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> Br, > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> Tommi > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> On Nov 16, 2017 04:29, "Eric McCorkle" > > > > > > > > > > > > > > > > > > > > > > > > icspace.n > > > > > > > > et>> > > > > > > > > > >>>> >> > > > > > > > > > > > > > > ce.net > > > > > > > > >>> > > > > > > > > > wrote: > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> Right, so basically, the remaining > > > > > > > > GELI > > > > > > > > patches > > > > > > > > are against > > > > > > > > > >>>> loader, and > > > > > > > > > >>>> >> most of them can go in > > > > > > > > independently of the > > > > > > > > work > > > > > > > > on removing > > > > > > > > > >>boot1. > > > > > > > > > >>>> >> There's a unanimous consensus on > > > > > > > > getting > > > > > > > > rid of > > > > > > > > boot1 which > > > > > > > > > >>>> includes its > > > > > > > > > >>>> >> original author, so that's going > > > > > > > > to happen. > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> For GELI, we have the following > > > > > > > > (not > > > > > > > > necessarily > > > > > > > > in order): > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> a) Adding the KMS interfaces, > > > > > > > > pseudo- > > > > > > > > device, and > > > > > > > > kernel > > > > > > > > > >>keybuf > > > > > > > > > >>>> >> interactions > > > > > > > > > >>>> >> b) Modifications to the efipart > > > > > > > > driver > > > > > > > > > >>>> >> c) boot crypto > > > > > > > > > >>>> >> d) GELI partition types (not > > > > > > > > strictly > > > > > > > > necessary) > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> Then there's the GELI driver > > > > > > > > itself. (a) > > > > > > > > and (c) > > > > > > > are > > > > > > > > > > > > > > > > > > > > > > > > > good to > > > > > > > > > >>>> land, (b) > > > > > > > > > >>>> >> needs some more work after Toomas > > > > > > > > Soome > > > > > > > > pointed > > > > > > > out a > > > > > > > > > > > > > > > > > > > > > > > > > >>legitimate > > > > > > > > > >>>> >> problem, and (d) actually needs a > > > > > > > > good bit > > > > > > > > more > > > > > > > > code (but > > > > > > > > > >>again, > > > > > > > > > >>>> it's > > > > > > > > > >>>> >> more cosmetic). Additionally, the > > > > > > > > GELI > > > > > > > > driver > > > > > > > > will need > > > > > > > > > >>further > > > > > > > > > >>>> mods to > > > > > > > > > >>>> >> efipart to be written (nothing too > > > > > > > > big). But we > > > > > > > > could go > > > > > > > > > >>ahead > > > > > > > > > >>>> with (a) > > > > > > > > > >>>> >> and (c), as they've already been > > > > > > > > proven to > > > > > > > > work. > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> I'd wanted to have this stuff > > > > > > > > shaped up > > > > > > > > sooner, > > > > > > > > but I'm > > > > > > > > > >>>> preoccupied with > > > > > > > > > >>>> >> the 7th RISC-V workshop at the end > > > > > > > > of the > > > > > > > > month. > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> Once this stuff is all in, loader > > > > > > > > should > > > > > > > > handle > > > > > > > > any GELI > > > > > > > > > >>volumes it > > > > > > > > > >>>> >> finds, and it should Just Work > > > > > > > > once boot1 > > > > > > > > is gone. > > > > > > > > > >>>> >> > > > > > > > > > >>>> >> > > > > > > > > > >>>> > > > > > > > > > _______________________________________________ > > > > > > > > > >>>> > freebsd-current@freebsd.org > > > > > > > > > > > > > > > > > > > > > > > > > mailing list > > > > > > > > > >>>> > https://lists.freebsd.org/mailman/listi > > > > > > > > nfo/freeb > > > > > > > > sd- > > > > > > > current > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > current> > > > > > > > > > > > > > > > > eebsd-cur > > > > > > > > rent > > > > > > > > > > > > > > > current>> > > > > > > > > > >>>> > To unsubscribe, send any mail to > > > > > > > "freebsd-current-unsubscribe@ > > > > > > > > > > > > > > > > > > > > > > > > > >>>> freebsd.org > > > > > > > > " > > > > > > > > > >>>> > > > > > > > > > > >>>> > > > > > > > > > >>> > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Sent from my Android device with K-9 Mail. > > > > > > > > Please > > > > > > > > excuse my > > > > > > > brevity. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > freebsd-current@freebsd.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > mailing list > > > > > > > > > > https://lists.freebsd.org/mailman/listinfo/f > > > > > > > > reebsd-cu > > > > > > > > rrent > > > > > > > > > > > > > > > current> > > > > > > > > > > > > > > > > eebsd-cur > > > > > > > > rent > > > > > > > > > > > > > > > current>> > > > > > > > > > > To unsubscribe, send any mail to > > > > > > > > > "freebsd-current-unsubscribe@freebsd.org > > > > > > > > > > > > > > > > > > > > > > > > g > > > > > > > > >" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > 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" > > > > -- > > > > Allan Jude > > > > > > Hi all, > > > > could anyone comment on the overall status of this feature? > > Is it going to make in 12.0 as it's code freeze is nearing up? > > > > Br, > > > > Tommi > > I'm not sure what part of the above mix of top- and bottom-posted > replies you're asking about. The support for GELI when booting from > UEFI is already in 12-current. I don't know anything about the "boot > environments" stuff (like, even what it means). > After Ian's changes, it should all be good. Once the disk is unlocked, you can do anything. Including ZFS boot environments that we already support for unencrypted disks. Warner > From owner-freebsd-current@freebsd.org Fri Aug 3 17:15:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F09FD106F268 for ; Fri, 3 Aug 2018 17:14:59 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 73B718CEE9 for ; Fri, 3 Aug 2018 17:14:58 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 7b6be9bb-973e-11e8-904b-1d2e466b3c59 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 7b6be9bb-973e-11e8-904b-1d2e466b3c59; Fri, 03 Aug 2018 16:58:46 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w73Gwieb043684; Fri, 3 Aug 2018 10:58:44 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533315524.1454.13.camel@freebsd.org> Subject: Re: GELI with UEFI supporting Boot Environments goes to HEAD when? From: Ian Lepore To: Tommi Pernila , Warner Losh Cc: Allan Jude , Eric McCorkle , Oliver Pinter , Warner Losh , freebsd-current Date: Fri, 03 Aug 2018 10:58:44 -0600 In-Reply-To: References: <0e75a2ba-9a59-8301-a678-68a822025bd6@metricspace.net> <9df63df2-9d61-4106-f360-347411869b41@metricspace.net> <5ba11024-e99b-86e1-48b7-125fb80b4001@metricspace.net> <1531078307.1336.22.camel@freebsd.org> <06cb8190-7a04-5c92-8fb9-637d1a80758f@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 17:15:00 -0000 On Fri, 2018-08-03 at 19:54 +0300, Tommi Pernila wrote: > On Tue, 10 Jul 2018 at 1.05, Warner Losh wrote: > > > > > I have this in my tree already... > > > > Warner > > > > On Mon, Jul 9, 2018, 10:28 AM Allan Jude > > wrote: > > > > > > > > I will look at updating the rootgen.sh script this evening, to > > > support > > > creating more flexible ESP partitions, so we can drop the > > > loader.efi > > > into an msdosfs directly. > > > > > > On 07/08/2018 15:31, Ian Lepore wrote: > > > > > > > > On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote: > > > > > > > > > > Hi! > > > > > > > > > > Have you or Warner any update on this code? > > > > > > > > > > On Thursday, April 12, 2018, Eric McCorkle > > > > net> > > > > > wrote: > > > > > > > > > Are you aware of https://reviews.freebsd.org/D15743 ? > > > > > > > > That's my changes to add geli support to loader(8) in an > > > > architecture- > > > > agnostic way, so that "it just works" for all platforms and > > > > flavors of > > > > loader. It has been succesfully tested on armv6/7 (ubldr) and > > > > on x86 > > > > using qemu.  The x86 tests cover ufs and zfs, legacy bios and > > > > uefi. The > > > > only variations that aren't tested yet are the uefi flavors, > > > > because > > > > the current rootgen.sh script for assembling test images is > > > > still using > > > > boot1.efi and I don't know enough about efi myself to update > > > > the script > > > > to make it assemble images the new way Warner envisions. > > > > > > > > -- Ian > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm in the middle of moving to a new apartment right > > > > > > now.  It's > > > > > > going to > > > > > > be a bit before I can get to this. > > > > > > > > > > > > On 04/11/2018 20:31, Warner Losh wrote: > > > > > > > > > > > > > > > > > > > > > OK. I've pushed in the main part of it. The additional > > > > > > > work I > > > > > > > have > > > > > > > shouldn't affect any of this stuff.  I was going to look > > > > > > > at what > > > > > > > part(s) > > > > > > > of your open reviewed needed to be redone tomorrow and > > > > > > > send you > > > > > > > feedback, but if you wanted to get a start before then, > > > > > > > I'm happy > > > > > > > to > > > > > > > answer questions. All the rest of my work is going to be > > > > > > > selecting the > > > > > > > root partition when we're told to us a specific > > > > > > > partition, so > > > > > > > will be > > > > > > > very constrained. > > > > > > > > > > > > > > Warner > > > > > > > > > > > > > > On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle > > > > > > icspace. > > > > > > > net > > > > > > > > wrote: > > > > > > > > > > > > > >      I think the thing to do at this point is to wait for > > > > > > > the > > > > > > > current > > > > > > work on > > > > > > > > > > > > > > > > > > > > >      loader.efi to land, then adapt my patches to apply > > > > > > > against > > > > > > > that work. > > > > > > > > > > > > > >      On 04/11/2018 15:06, Warner Losh wrote: > > > > > > >      > Still reviewing the code. I'm worried it's too > > > > > > > i386 > > > > > > > specific and it > > > > > > >      > conflicts with some work I'm doing. I'll have a > > > > > > > list of > > > > > > > actionable > > > > > > >      > critiques this week. > > > > > > >      > > > > > > > >      > Warner > > > > > > >      > > > > > > > >      > On Wed, Apr 11, 2018 at 1:03 PM, Oliver Pinter > > > > > > >      > > > > > > >       > > > > > > >       > > > > > >      >> > > > > > > >      > wrote: > > > > > > >      > > > > > > > >      >     Hi! > > > > > > >      > > > > > > > >      >     Is there any update regarding the rebase or > > > > > > > the > > > > > > > inclusion to > > > > > > base > > > > > > > > > > > > > > > > > > > > >      >     system? > > > > > > >      >     On 3/28/18, Eric McCorkle > > > > > > t > > > > > > > > > > > > eric@metricspace.net> > > > > > > > > > > > > > > > > > > > > >      >      > > > > > > icspace.n > > > > > > > et>>> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > >      >     > I'll do another rebase from head just to be > > > > > > > sure > > > > > > >      >     > > > > > > > >      >     > On March 28, 2018 3:23:23 PM EDT, Warner > > > > > > > Losh < > > > > > > imp@bsdimp.com > > > > > > > > > > > > > > > > > > > > >      >      > > > > > > > >> wrote: > > > > > > >      >     >>It's on my list for nexr, finally. I have an > > > > > > > alternate patch > > > > > > for > > > > > > > > > > > > > > > > > > > > >      >     >>loader.efi > > > > > > >      >     >>from ESP, but i don't think it will affect > > > > > > > the GELI > > > > > > > stuff. I > > > > > > have some > > > > > > > > > > > > > > > > > > > > >      >     >>time > > > > > > >      >     >>slotted for integration issues though. > > > > > > >      >     >> > > > > > > >      >     >>I am quite mindful of the freeze dates.... > > > > > > > I  have > > > > > > > some uefi > > > > > > boot > > > > > > > > > > > > > > > > > > > > >      >     >>loader > > > > > > >      >     >>protocol changes that I need to get in. > > > > > > >      >     >> > > > > > > >      >     >>Warner > > > > > > >      >     >> > > > > > > >      >     >>On Feb 21, 2018 11:18 PM, "Tommi Pernila" < > > > > > > tommi.pernila@iki.fi > > > > > > > > > > > > > > > > > > > > >      >      > > > > > > nila@iki. > > > > > > > fi>>> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > >      >     >> > > > > > > >      >     >>> Awesome, thanks for the update and the > > > > > > > work that > > > > > > > you have > > > > > > done! > > > > > > > > > > > > > > > > > > > > >      >     >>> > > > > > > >      >     >>> Now we just need some more reviewers eyes > > > > > > > on the > > > > > > > code :) > > > > > > >      >     >>> > > > > > > >      >     >>> Br, > > > > > > >      >     >>> > > > > > > >      >     >>> Tommi > > > > > > >      >     >>> > > > > > > >      >     >>> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle > > > > > > > < > > > > > > eric@metricspace.net > > > > > > > > > > > > > > > > > > > > >      >      > > > > > > icspace.n > > > > > > > et>>> > > > > > > >      >     >>wrote: > > > > > > >      >     >>> > > > > > > >      >     >>>> FYI, I just IFC'ed everything, and the > > > > > > > current > > > > > > > patches > > > > > > >      are still > > > > > > >      >     >>fine. > > > > > > >      >     >>>> > > > > > > >      >     >>>> Also, the full GELI + standalone loader > > > > > > > has been > > > > > > > deployed > > > > > > >      on one of > > > > > > >      >     >>my > > > > > > >      >     >>>> laptops for some time now. > > > > > > >      >     >>>> > > > > > > >      >     >>>> On 02/21/2018 18:15, Eric McCorkle wrote: > > > > > > >      >     >>>> > The GELI work could be merged at this > > > > > > > point, > > > > > > > though it > > > > > > >      won't be > > > > > > >      >     >>usable > > > > > > >      >     >>>> > without an additional patch to enable > > > > > > > loader- > > > > > > > only > > > > > > >      operation.  The > > > > > > >      >     >>>> > patches are currently up for review: > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > This is the order in which they'd need > > > > > > > to be > > > > > > > merged: > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > https://reviews.freebsd.org/D12732 > > > > > > >       > > > > > > >      >      > > > > > >      > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > This one changes the efipart > > > > > > > device.  Toomas > > > > > > > Soome > > > > > > >      identified > > > > > > >      >     some > > > > > > >      >     >>>> > problems, which I have addressed.  He > > > > > > > has not > > > > > > >      re-reviewed it, > > > > > > >      >     >>however. > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > https://reviews.freebsd.org/D12692 > > > > > > >       > > > > > > >      >      > > > > > >      > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > This adds some crypto code needed for > > > > > > > GELI.  It > > > > > > > simply > > > > > > >      adds new > > > > > > >      >     >>code, > > > > > > >      >     >>>> > and doesn't conflict with anything. > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > https://reviews.freebsd.org/D12698 > > > > > > >       > > > > > > >      >      > > > > > >      > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > This adds the EFI KMS interface code, > > > > > > > and has > > > > > > > the EFI > > > > > > >      loader pass > > > > > > >      >     >>keys > > > > > > >      >     >>>> > into the keybuf interface. > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > I can't post the main GELI driver until > > > > > > > those > > > > > > > get > > > > > > >      merged, as it > > > > > > >      >     >>depends > > > > > > >      >     >>>> > on them.  It can be found on the geli > > > > > > > branch on > > > > > > > my > > > > > > >      github freebsd > > > > > > >      >     >>>> > repository, however. > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > Additionally, you need this patch, > > > > > > > which allows > > > > > > >      loader.efi to > > > > > > >      >     >>function > > > > > > >      >     >>>> > when installed directly to the ESP: > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > https://reviews.freebsd.org/D13497 > > > > > > >       > > > > > > >      >      > > > > > >      > > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > On 02/20/2018 22:56, Tommi Pernila > > > > > > > wrote: > > > > > > >      >     >>>> >> Hi Eric, > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >> could you provide a brief update how > > > > > > > the work > > > > > > > is going? > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >> Br, > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >> Tommi > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >> On Nov 16, 2017 04:29, "Eric McCorkle" > > > > > > >       > > > > > > >      >      > > > > > > icspace.n > > > > > > > et>> > > > > > > >      >     >>>> >> > > > > > >       > > > > > > ce.net > > > > > > >      >>> > > > > > > >      >     wrote: > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >>     Right, so basically, the remaining > > > > > > > GELI > > > > > > > patches > > > > > > >      are against > > > > > > >      >     >>>> loader, and > > > > > > >      >     >>>> >>     most of them can go in > > > > > > > independently of the > > > > > > > work > > > > > > >      on removing > > > > > > >      >     >>boot1. > > > > > > >      >     >>>> >>     There's a unanimous consensus on > > > > > > > getting > > > > > > > rid of > > > > > > >      boot1 which > > > > > > >      >     >>>> includes its > > > > > > >      >     >>>> >>     original author, so that's going > > > > > > > to happen. > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >>     For GELI, we have the following > > > > > > > (not > > > > > > > necessarily > > > > > > >      in order): > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >>     a) Adding the KMS interfaces, > > > > > > > pseudo- > > > > > > > device, and > > > > > > >      kernel > > > > > > >      >     >>keybuf > > > > > > >      >     >>>> >>     interactions > > > > > > >      >     >>>> >>     b) Modifications to the efipart > > > > > > > driver > > > > > > >      >     >>>> >>     c) boot crypto > > > > > > >      >     >>>> >>     d) GELI partition types (not > > > > > > > strictly > > > > > > > necessary) > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >>     Then there's the GELI driver > > > > > > > itself.  (a) > > > > > > > and (c) > > > > > > are > > > > > > > > > > > > > > > > > > > > >      >     good to > > > > > > >      >     >>>> land, (b) > > > > > > >      >     >>>> >>     needs some more work after Toomas > > > > > > > Soome > > > > > > > pointed > > > > > > out a > > > > > > > > > > > > > > > > > > > > >      >     >>legitimate > > > > > > >      >     >>>> >>     problem, and (d) actually needs a > > > > > > > good bit > > > > > > > more > > > > > > >      code (but > > > > > > >      >     >>again, > > > > > > >      >     >>>> it's > > > > > > >      >     >>>> >>     more cosmetic).  Additionally, the > > > > > > > GELI > > > > > > > driver > > > > > > >      will need > > > > > > >      >     >>further > > > > > > >      >     >>>> mods to > > > > > > >      >     >>>> >>     efipart to be written (nothing too > > > > > > > big).  But we > > > > > > >      could go > > > > > > >      >     >>ahead > > > > > > >      >     >>>> with (a) > > > > > > >      >     >>>> >>     and (c), as they've already been > > > > > > > proven to > > > > > > > work. > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >>     I'd wanted to have this stuff > > > > > > > shaped up > > > > > > > sooner, > > > > > > >      but I'm > > > > > > >      >     >>>> preoccupied with > > > > > > >      >     >>>> >>     the 7th RISC-V workshop at the end > > > > > > > of the > > > > > > > month. > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >>     Once this stuff is all in, loader > > > > > > > should > > > > > > > handle > > > > > > >      any GELI > > > > > > >      >     >>volumes it > > > > > > >      >     >>>> >>     finds, and it should Just Work > > > > > > > once boot1 > > > > > > > is gone. > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> >> > > > > > > >      >     >>>> > > > > > > > > _______________________________________________ > > > > > > >      >     >>>> > freebsd-current@freebsd.org > > > > > > >       > > > > > > >      >      > > > > > >      > mailing list > > > > > > >      >     >>>> > https://lists.freebsd.org/mailman/listi > > > > > > > nfo/freeb > > > > > > > sd- > > > > > > current > > > > > > > > > > > > > > > > > > > > >       > > > > > > current> > > > > > > >      >      > > > > > > eebsd-cur > > > > > > > rent > > > > > > >       > > > > > > current>> > > > > > > >      >     >>>> > To unsubscribe, send any mail to > > > > > > "freebsd-current-unsubscribe@ > > > > > > > > > > > > > > > > > > > > >      >     >>>> freebsd.org > > > > > > > " > > > > > > >      >     >>>> > > > > > > > >      >     >>>> > > > > > > >      >     >>> > > > > > > >      >     > > > > > > > >      >     > -- > > > > > > >      >     > Sent from my Android device with K-9 Mail. > > > > > > > Please > > > > > > > excuse my > > > > > > brevity. > > > > > > > > > > > > > > > > > > > > >      >     > > > > > > > > _______________________________________________ > > > > > > >      >     > freebsd-current@freebsd.org > > > > > > >       > > > > > > >       > > > > > >      > > > > > > > >      >     mailing list > > > > > > >      >     > https://lists.freebsd.org/mailman/listinfo/f > > > > > > > reebsd-cu > > > > > > > rrent > > > > > > >       > > > > > > current> > > > > > > >      >      > > > > > > eebsd-cur > > > > > > > rent > > > > > > >       > > > > > > current>> > > > > > > >      >     > To unsubscribe, send any mail to > > > > > > >      >     "freebsd-current-unsubscribe@freebsd.org > > > > > > >       > > > > > > >      >      > > > > > > g > > > > > > >      >" > > > > > > >      >     > > > > > > > >      > > > > > > > >      > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > 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" > > > -- > > > Allan Jude > > > > Hi all, > > could anyone comment on the overall status of this feature? > Is it going to make in 12.0 as it's code freeze is nearing up? > > Br, > > Tommi I'm not sure what part of the above mix of top- and bottom-posted replies you're asking about. The support for GELI when booting from UEFI is already in 12-current. I don't know anything about the "boot environments" stuff (like, even what it means). -- Ian From owner-freebsd-current@freebsd.org Fri Aug 3 17:42:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA3DD106FB45 for ; Fri, 3 Aug 2018 17:42:29 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 709F08E07B for ; Fri, 3 Aug 2018 17:42:29 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.106] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 11a86a21 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 3 Aug 2018 10:42:26 -0700 (PDT) Subject: Re: ntpd as ntpd user question To: bsd-lists@BSDforge.com, Niclas Zeising Cc: RW , freebsd-current@freebsd.org References: <1bd91aa67e408dd8f275225325edccd9@udns.ultimatedns.net> From: Pete Wright Message-ID: Date: Fri, 3 Aug 2018 10:42:22 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <1bd91aa67e408dd8f275225325edccd9@udns.ultimatedns.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 17:42:30 -0000 On 8/2/18 10:43 PM, Chris H wrote: > On Mon, 23 Jul 2018 12:57:28 +0200 "Niclas Zeising" > said > >> On 07/21/18 19:56, RW wrote: >> > On Sat, 21 Jul 2018 11:14:45 -0600 >> > Ian Lepore wrote: >> > > >> There's a "pre-world" stage of mergemaster (-Fp option I >> think) which >> >> isn't needed often, but one of the times it is needed is apparently >> >> when new user ids are added. >> > > I wish mergemaster had an option to just add new users and groups, >> > rather than merging the files. >> >> etcupdate is usually pretty good at automatically merge updates to >> files without user interaction, even when the files are locally >> edited as well.  For instance, I had no problem merging >> /etc/master.passwd and /etc/group for the ntp change. >> Regards >> -- >> Niclas > FWIW I found mergemaster intimidating when I was first starting out. Not > because I didn't understand patch(1)/diff(1). I was well familiar there. > But I found it unintuitive. Despite the messages regarding it's usage. > Anyway. I finally developed a strategy that worked for me. > I start out with the standard > > mergemaster -p > > then the installworld > But I implement the following mergemster, thusly > > mergemaster -vF > > It dispenses with asking about all the files that only have revision > changes, and date differences, and just updates them, the -v portion, > just keeps "enlightened" as to wtf is actually happening during the > process. > Then all that's left are just some 5-9 files I need to deal with, > with mergemaster informing me that by default, it'll leave them > for me, to look at later. To which I reply Y. Done. > Knowing diff/patch, makes the resulting unmerged files a trivial > task, requiring perhaps 5-10 minutes while still at the console. > Then I reboot into the new system. > this certainly sums up my experience and workflow now.  if i were someone with more free time on my hands i'd look at adding an option to mergemaster to read in an env-var or the ~/.mergemasterrc file to use a diff program of choice. i remember when i used to admin IRIX systems we would use xdiff frequently when updates of software required updates to configs, being a junior admin at the time and having a decent gui to manage diffs certainly made me feel more confident about the changes i was making. but honestly this is such an edge case i haven't put any effort into hacking on this :) -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Fri Aug 3 20:26:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E77D8104F87A for ; Fri, 3 Aug 2018 20:26:47 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69B5673A34 for ; Fri, 3 Aug 2018 20:26:47 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x429.google.com with SMTP id c13-v6so6496298wrt.1 for ; Fri, 03 Aug 2018 13:26:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=6KhlYMo1QiZZtphcfeN6Mgnx1gd/H+tMSIigWGkMfSs=; b=sWi4lluX2NB0k4EROZFcr2daC63KSvckwHdCVHgBKoix2uO4IYDpgq5zxuTN3sR/EZ cr++xiL0okuO7t9xGoHTSg8EGOM72g2153xYiUR1/KQF/AVUiLDiElOLY86yElfQ0rKh 3IvLbt6GOMqVVFng+8a+Bxx8da0VYmctASDeyfzy+AgZD048QDM4zQfywa/cht/omRnL 7mCmjpPXTj6TJQI9PyKp3Tih0lFJT4nfkypgEJ2KKTCQskIL0gBwqo9JWiBPJttlvv5K G/FhXeanpbCgVqTJbfqIksUPor8HUZhpUb/83oD263K13iNd85sLe7GDYgNFxfBRssnT 6ckQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6KhlYMo1QiZZtphcfeN6Mgnx1gd/H+tMSIigWGkMfSs=; b=hk123S9NeQISIRwVke77T57912eD9OkLuYteO0JPVfQdPXBGRuDuZipqsGKBxmIvmP ZLZ9RbMWoW5kE1zHVgapU+peQ230H4IgHimuFp+UXLHMOu1ruBySl3VDNorccFlVww9e u58CLJ8lvS0x3TExi6Yl2RvPHXHMzkROhl5J6adi+xXl7KwMki/JQPKxKdSU+qzkuI17 /JqOiydp28w4poLvc5zn0BziBopR5NsNCuAvp+6qEz3k8LwL4/QcwEk369BJ2nHOTZlG 1aWyyKgFWbGEsJspp2hOoQOmj/ILw08yCuyP8M8ug/m7ojeF+5+chh6GgFrxG3v+/g5F lu0A== X-Gm-Message-State: AOUpUlHOdki2T+y48WZiy3Xn1wlueLM7aa65B7bIiw6LwX0BfZAVMR65 i97IidzeZuKNXByxZPPDyOSonGSlMbuw6U1kAPm0vDbb X-Google-Smtp-Source: AAOMgpe18+W1C/eNZrVS99fYSg/FHiNq2MGHG5OUXzNjqDCCIZ9cc0/hY3Q5zLkHNEYOgkMYhtvpyugrwKPcOaHQRXg= X-Received: by 2002:adf:e584:: with SMTP id l4-v6mr3307445wrm.190.1533328005126; Fri, 03 Aug 2018 13:26:45 -0700 (PDT) MIME-Version: 1.0 From: Johannes Lundberg Date: Fri, 3 Aug 2018 21:26:08 +0100 Message-ID: Subject: Linux process causes kernel panic To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 20:26:48 -0000 Hi After install new kernel+world built from today's checkout I keep getting the same crash over and over. Never had this problem before. The previous kernel was from 3 weeks ago. Looks familiar to anyone? Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xfffe665c fault code = supervisor write data, protection violation instruction pointer = 0x20:0xffffffff82282db3 stack pointer = 0x0:0xfffffe004c74c8c8 frame pointer = 0x0:0xfffffe004c74c980 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 = 1579 (wcgrid_zika_vina_7.) trap number = 12 panic: page fault cpuid = 0 time = 1533327428 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe004c74c580 vpanic() at vpanic+0x1a3/frame 0xfffffe004c74c5e0 panic() at panic+0x43/frame 0xfffffe004c74c640 trap_fatal() at trap_fatal+0x35f/frame 0xfffffe004c74c690 trap_pfault() at trap_pfault+0x62/frame 0xfffffe004c74c6e0 trap() at trap+0x2ba/frame 0xfffffe004c74c7f0 calltrap() at calltrap+0x8/frame 0xfffffe004c74c7f0 --- trap 0xc, rip = 0xffffffff82282db3, rsp = 0xfffffe004c74c8c8, rbp = 0xfffffe004c74c980 --- futex_xchgl() at futex_xchgl+0x23/frame 0xfffffe004c74c980 ia32_syscall() at ia32_syscall+0x29f/frame 0xfffffe004c74cab0 int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x4000001 Uptime: 7m29s Dumping 411 out of 8056 MB:..4%..12%..24%..32%..43%..51%..63%..74%..82%..94% Dump complete From owner-freebsd-current@freebsd.org Fri Aug 3 20:34:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB730104FC54 for ; Fri, 3 Aug 2018 20:34:55 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yb0-x241.google.com (mail-yb0-x241.google.com [IPv6:2607:f8b0:4002:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8391774008 for ; Fri, 3 Aug 2018 20:34:55 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yb0-x241.google.com with SMTP id e84-v6so3142270ybb.0 for ; Fri, 03 Aug 2018 13:34:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HtE98E5E1wdptLpL9TK0hL9kqBV2WtLxG7Vzy2YAxtI=; b=K0eJY50U1YmMmi9SwMiKO4soU2HZAyQJQMi0UCh/fVKJsg54cDZ4lNZVmAscZ3KoIW 00t/nMrhTM68ROEXcyfTsW05htnEzTV/VzdMK3pJysK+2ICGQrleFiJpfu7uS1YgDVD2 83vPCAuIn8zZxzoI8WvWI1BALA2tPA3DMf4/RxyKn1HzQoVsd0gw0eWMHnoGIPUFeQno BM9Sinp+rArfhpIVUlzYRIhipZYgfbM5NZgWUU72szup96p4H3ffKrCVA1xN+Xdowfc2 iJI+BMKr8S35vUJp1AzYRqnRhaSVF6GlSKO5P9C4xtVBTD1334aYYYQirqsTBIKUt1+B O4kw== 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=HtE98E5E1wdptLpL9TK0hL9kqBV2WtLxG7Vzy2YAxtI=; b=GZV/TfJB6n0ueuI4aWjwzW001gxxPK+yjgyEGdw9fqDJsI7Bk0Gh0gSzVjoWsI5EK7 E3+6NOOlDZMgb7C3bQ7hQlGpNKwUhUqMJKyybXkwFxJQ08Wo1ODPBsywfsEw664DNmU/ JLM+PC1Lci/hImBeBQ+eHdovuAvRk+87F6iS5Mdy04iTpugUFskNRGs1w/c/XuKtnENe OqVtzXAmnre+VJyqmB3U26Eq2QsSdlPDGrh18Z61j+5JpSfB6VOEWbSxLQJw/9l8iFXa e35UuD9Y3evi/gW428iX3xVYz3IKDkwfTnG1H/7YQgaT7BGsIjSNiBgesRcKOutOcxW2 nf7g== X-Gm-Message-State: AOUpUlEqysx0zR0hDkp9TZf9QPfc1WQHfKaPCj0obw8s9oi3Ydojo+6b 1ew747cewX+T5e6l2Jr34pPFBot8lvgyRUrU/8ofCbpsUWA= X-Google-Smtp-Source: AAOMgpfsw7jsNsWkfp/Nte/Va6qT0e0JRoq4NsJfc0FY9EbeRVqfMgPyJ5yvMeoPdQekxnDrJuoC/25NRc6/DncG9N0= X-Received: by 2002:a25:3812:: with SMTP id f18-v6mr2879354yba.199.1533328494721; Fri, 03 Aug 2018 13:34:54 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a5b:bc5:0:0:0:0:0 with HTTP; Fri, 3 Aug 2018 13:34:54 -0700 (PDT) In-Reply-To: References: From: Oliver Pinter Date: Fri, 3 Aug 2018 22:34:54 +0200 Message-ID: Subject: Re: Linux process causes kernel panic To: Johannes Lundberg Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 20:34:56 -0000 Hi! On 8/3/18, Johannes Lundberg wrote: > Hi > > After install new kernel+world built from today's checkout I keep getting > the same crash over and over. Never had this problem before. The previous > kernel was from 3 weeks ago. > > Looks familiar to anyone? Have you an Intel Broadwell or newer Intel CPU or an AMD CPU with SMAP support? > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xfffe665c > fault code = supervisor write data, protection violation > instruction pointer = 0x20:0xffffffff82282db3 > stack pointer = 0x0:0xfffffe004c74c8c8 > frame pointer = 0x0:0xfffffe004c74c980 > 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 = 1579 (wcgrid_zika_vina_7.) > trap number = 12 > panic: page fault > cpuid = 0 > time = 1533327428 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe004c74c580 > vpanic() at vpanic+0x1a3/frame 0xfffffe004c74c5e0 > panic() at panic+0x43/frame 0xfffffe004c74c640 > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe004c74c690 > trap_pfault() at trap_pfault+0x62/frame 0xfffffe004c74c6e0 > trap() at trap+0x2ba/frame 0xfffffe004c74c7f0 > calltrap() at calltrap+0x8/frame 0xfffffe004c74c7f0 > --- trap 0xc, rip = 0xffffffff82282db3, rsp = 0xfffffe004c74c8c8, rbp = > 0xfffffe004c74c980 --- > futex_xchgl() at futex_xchgl+0x23/frame 0xfffffe004c74c980 > ia32_syscall() at ia32_syscall+0x29f/frame 0xfffffe004c74cab0 > int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x4000001 > Uptime: 7m29s > Dumping 411 out of 8056 > MB:..4%..12%..24%..32%..43%..51%..63%..74%..82%..94% > Dump complete > _______________________________________________ > 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 Fri Aug 3 20:37:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A338C104FD49 for ; Fri, 3 Aug 2018 20:37:49 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 218C57414C for ; Fri, 3 Aug 2018 20:37:49 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x42c.google.com with SMTP id c13-v6so6519785wrt.1 for ; Fri, 03 Aug 2018 13:37:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fXQdHL1WQ0R50OKgDcomjBin4NQdMUbj6Zj8c4KB8g4=; b=iNUvDsbfpmdwnKRxHnNMYKEj48YQBPP2SXVxIKw9+fu+cHMmDxZI4BgT4ehRhszVDo zNHufhJu59OkWyOkEiUv5N7FMDRo2E2X/WNMtoJ4S83PIbF5MCIN48K2wpP1yOn01hMx 8FDdWMGvDLcAZXpkfCt5gaq24wayxxczovoI9BHBKGCQLvfurs0oC/Tt0B9T0FxPF1Ht Pq2hMWniI94Gw78v1vaMkyvFkFKdHr/4qQkJntR530NZZMH5CFMvOK0hIfcGsYOVc+b0 JBwea5iesnQXOLrzv05JZSW5tRbVE73FUf3VRdQyMiMT1FEEqoNknfFWJuFQIuce3e80 NLWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fXQdHL1WQ0R50OKgDcomjBin4NQdMUbj6Zj8c4KB8g4=; b=EGq/V9T93jDT0VCyrCM74esfJqxGpkOSZhePpsKkvc3kM75B9NaTa4hbYhAb/VMGyi HOmGVu0dQ39NIZrMxK8uCa5QzJsoT4i1iIIdNONbN2CHWyTmmR6xpu95i6fwyOWNx4bm WVzqi5BDAaeefWSTZW9q9gB9/KFRgImmZZzp4U14hlo8EN9434vo2s+GV4Ie4fBVNf6i uzr3TpmEv/tKAKG36B29pIDcPYBGyzIDVUfPWiXXCTBo0LI/wDhYdqYowqgsyyGa7MrI n1S7HF24qpv/gKoRfmkA8RZvzu73Fc3iiRHb1eNOdQwfgIZ2/8MWovEIlUn2fiQ2RDnC NfDw== X-Gm-Message-State: AOUpUlEg+JAwvxkG//1IZpaDFeSaZznWRLioNPBQnMArVibY41i/g9XL kB9BCjYkFovFVyB+qJFRxCmghym/yo/iLRs3txE= X-Google-Smtp-Source: AAOMgpcq83rpI4DNokNHH/q7CxI1HGHNxso+wsSVEhVIU4YkTYVFqrGfcsXbWotlptx4I3QToBqt6jwlhfJIOtjZrMo= X-Received: by 2002:a5d:46d1:: with SMTP id g17-v6mr3448163wrs.76.1533328668155; Fri, 03 Aug 2018 13:37:48 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Fri, 3 Aug 2018 21:37:11 +0100 Message-ID: Subject: Re: Linux process causes kernel panic To: Oliver Pinter Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 20:37:50 -0000 On Fri, Aug 3, 2018 at 9:34 PM Oliver Pinter wrote: > Hi! > > On 8/3/18, Johannes Lundberg wrote: > > Hi > > > > After install new kernel+world built from today's checkout I keep getting > > the same crash over and over. Never had this problem before. The previous > > kernel was from 3 weeks ago. > > > > Looks familiar to anyone? > > Have you an Intel Broadwell or newer Intel CPU or an AMD CPU with SMAP > support? > This is Intel Broadwell, Core i5. > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0xfffe665c > > fault code = supervisor write data, protection violation > > instruction pointer = 0x20:0xffffffff82282db3 > > stack pointer = 0x0:0xfffffe004c74c8c8 > > frame pointer = 0x0:0xfffffe004c74c980 > > 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 = 1579 (wcgrid_zika_vina_7.) > > trap number = 12 > > panic: page fault > > cpuid = 0 > > time = 1533327428 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > > 0xfffffe004c74c580 > > vpanic() at vpanic+0x1a3/frame 0xfffffe004c74c5e0 > > panic() at panic+0x43/frame 0xfffffe004c74c640 > > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe004c74c690 > > trap_pfault() at trap_pfault+0x62/frame 0xfffffe004c74c6e0 > > trap() at trap+0x2ba/frame 0xfffffe004c74c7f0 > > calltrap() at calltrap+0x8/frame 0xfffffe004c74c7f0 > > --- trap 0xc, rip = 0xffffffff82282db3, rsp = 0xfffffe004c74c8c8, rbp = > > 0xfffffe004c74c980 --- > > futex_xchgl() at futex_xchgl+0x23/frame 0xfffffe004c74c980 > > ia32_syscall() at ia32_syscall+0x29f/frame 0xfffffe004c74cab0 > > int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x4000001 > > Uptime: 7m29s > > Dumping 411 out of 8056 > > MB:..4%..12%..24%..32%..43%..51%..63%..74%..82%..94% > > Dump complete > > _______________________________________________ > > 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 Fri Aug 3 20:39:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47182104FE75 for ; Fri, 3 Aug 2018 20:39:19 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yb0-x244.google.com (mail-yb0-x244.google.com [IPv6:2607:f8b0:4002:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D590E7429B for ; Fri, 3 Aug 2018 20:39:18 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yb0-x244.google.com with SMTP id s1-v6so3142232ybk.3 for ; Fri, 03 Aug 2018 13:39:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Z+IL9JdnrrlBHDhTsS+fGwRcjEY3HK2guGaHBs/DZXA=; b=T8cidlxObsjRNJSoi3tPUiIfFO1rg8KYUCaOyedPjlzQ3dAGUPqeL/yUvGNwB5IxCM V7/UUYl6ShZ4xdKaPZSkLt1+nD4XfEW5NnhZBQfdGCQIWlbC4ReNEoHmbqlrDOSGfKdQ 2Q9/fBg7g4QQ8GVMMlLxjDxZlBGsyqeL/glAp8s59ZnwTq5UQeshB4qXsxLPEOm+1RXh ni2tBhbIQe1AU6/uLen+S6X3E4KDHF9/iN3QtLbkZJe26QKtXASoyX+Rt4EeHn761pfh h28C+CbQNahlNMBsm2uFrBMFm+SooMr2nvDui/R9FEaQQKa/Q/ywvYCnhdkYhMpFlMHS vPvg== 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=Z+IL9JdnrrlBHDhTsS+fGwRcjEY3HK2guGaHBs/DZXA=; b=J9tcE/K8IuCYc6bVvx2U12XsRXubC9NjxoZdeCxTXQDiz/Spm/2PpIFmG7Z4ME4S39 aNFRDi4hqSU1awqUA/aJebhwxWeZmcdE7rNmO0FJ5tbKkkaZzHZ0LVVQ2HJHgmBy5CCx jgBr4IRxEeFFEvj0NU1yoZNkhSBZYJVY4r5ADFRNn9abAVk/6Nb5kl9AYxupmm5Nu1XC FFElp/qknoXQzf5Um9HJJ29I4MNFvo17wgGzU6D4JSrgMLymZrGmY4IdSG6TGAnPig0A AOvzTZ5jLkd7EJlznkUSZnTeqsaBOTP/nza+xXpccbyqwzUQtyWGRfcIxLnc6SvEeldv sucw== X-Gm-Message-State: AOUpUlGqjIKIiCLi43/7WlKRrZwMRu2qc9pmQlYHH2AZlH6/6LFwGC8Z TzxvzVwfavQa+lKEeYaPj3FZxMfwY7kX15+G8NpAKA== X-Google-Smtp-Source: AAOMgpd4A1WRekHeZZ40AHD60d+0j1cl1uEL2lFF/Su8C7zq3Kd3U6QZOEcekfk4z0vJyp80RilFGoAXIRVD7zH/GvQ= X-Received: by 2002:a25:3812:: with SMTP id f18-v6mr2886034yba.199.1533328758389; Fri, 03 Aug 2018 13:39:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a5b:bc5:0:0:0:0:0 with HTTP; Fri, 3 Aug 2018 13:39:17 -0700 (PDT) In-Reply-To: References: From: Oliver Pinter Date: Fri, 3 Aug 2018 22:39:17 +0200 Message-ID: Subject: Re: Linux process causes kernel panic To: Johannes Lundberg Cc: freebsd-current , kib@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 20:39:19 -0000 On 8/3/18, Johannes Lundberg wrote: > On Fri, Aug 3, 2018 at 9:34 PM Oliver Pinter > > wrote: > >> Hi! >> >> On 8/3/18, Johannes Lundberg wrote: >> > Hi >> > >> > After install new kernel+world built from today's checkout I keep >> > getting >> > the same crash over and over. Never had this problem before. The >> > previous >> > kernel was from 3 weeks ago. >> > >> > Looks familiar to anyone? >> >> Have you an Intel Broadwell or newer Intel CPU or an AMD CPU with SMAP >> support? >> > > This is Intel Broadwell, Core i5. The smapification of amd64/linux/linux_support.s is missing from the SMAP patch. CC kib@. > > >> > >> > Fatal trap 12: page fault while in kernel mode >> > cpuid = 0; apic id = 00 >> > fault virtual address = 0xfffe665c >> > fault code = supervisor write data, protection violation >> > instruction pointer = 0x20:0xffffffff82282db3 >> > stack pointer = 0x0:0xfffffe004c74c8c8 >> > frame pointer = 0x0:0xfffffe004c74c980 >> > 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 = 1579 (wcgrid_zika_vina_7.) >> > trap number = 12 >> > panic: page fault >> > cpuid = 0 >> > time = 1533327428 >> > KDB: stack backtrace: >> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >> > 0xfffffe004c74c580 >> > vpanic() at vpanic+0x1a3/frame 0xfffffe004c74c5e0 >> > panic() at panic+0x43/frame 0xfffffe004c74c640 >> > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe004c74c690 >> > trap_pfault() at trap_pfault+0x62/frame 0xfffffe004c74c6e0 >> > trap() at trap+0x2ba/frame 0xfffffe004c74c7f0 >> > calltrap() at calltrap+0x8/frame 0xfffffe004c74c7f0 >> > --- trap 0xc, rip = 0xffffffff82282db3, rsp = 0xfffffe004c74c8c8, rbp = >> > 0xfffffe004c74c980 --- >> > futex_xchgl() at futex_xchgl+0x23/frame 0xfffffe004c74c980 >> > ia32_syscall() at ia32_syscall+0x29f/frame 0xfffffe004c74cab0 >> > int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x4000001 >> > Uptime: 7m29s >> > Dumping 411 out of 8056 >> > MB:..4%..12%..24%..32%..43%..51%..63%..74%..82%..94% >> > Dump complete >> > _______________________________________________ >> > 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 Fri Aug 3 20:43:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E66CD1050397 for ; Fri, 3 Aug 2018 20:43:01 +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 4D5057485D for ; Fri, 3 Aug 2018 20:43:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w73Kgo1Y006651 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 3 Aug 2018 23:42:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w73Kgo1Y006651 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w73Kgo2P006650; Fri, 3 Aug 2018 23:42:50 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 3 Aug 2018 23:42:50 +0300 From: Konstantin Belousov To: Johannes Lundberg Cc: freebsd-current Subject: Re: Linux process causes kernel panic Message-ID: <20180803204250.GE6049@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) 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.27 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, 03 Aug 2018 20:43:02 -0000 On Fri, Aug 03, 2018 at 09:26:08PM +0100, Johannes Lundberg wrote: > Hi > > After install new kernel+world built from today's checkout I keep getting > the same crash over and over. Never had this problem before. The previous > kernel was from 3 weeks ago. > > Looks familiar to anyone? > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xfffe665c > fault code = supervisor write data, protection violation > instruction pointer = 0x20:0xffffffff82282db3 > stack pointer = 0x0:0xfffffe004c74c8c8 > frame pointer = 0x0:0xfffffe004c74c980 > 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 = 1579 (wcgrid_zika_vina_7.) > trap number = 12 > panic: page fault > cpuid = 0 > time = 1533327428 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe004c74c580 > vpanic() at vpanic+0x1a3/frame 0xfffffe004c74c5e0 > panic() at panic+0x43/frame 0xfffffe004c74c640 > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe004c74c690 > trap_pfault() at trap_pfault+0x62/frame 0xfffffe004c74c6e0 > trap() at trap+0x2ba/frame 0xfffffe004c74c7f0 > calltrap() at calltrap+0x8/frame 0xfffffe004c74c7f0 > --- trap 0xc, rip = 0xffffffff82282db3, rsp = 0xfffffe004c74c8c8, rbp = > 0xfffffe004c74c980 --- > futex_xchgl() at futex_xchgl+0x23/frame 0xfffffe004c74c980 > ia32_syscall() at ia32_syscall+0x29f/frame 0xfffffe004c74cab0 > int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x4000001 > Uptime: 7m29s > Dumping 411 out of 8056 MB:..4%..12%..24%..32%..43%..51%..63%..74%..82%..94% > Dump complete Post first 40 lines from the verbose dmesg boot of your machine. I have a guess what is going on, I need the dmesg to confirm. If my guess is correct, you can use a workaround by setting the "hw.cpu_stdext_disable=0x00100000" tunable at the loader prompt for now. From owner-freebsd-current@freebsd.org Fri Aug 3 20:53:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68DF510508AC for ; Fri, 3 Aug 2018 20:53:24 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0D29474F17; Fri, 3 Aug 2018 20:53:24 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 432C510A87D; Fri, 3 Aug 2018 16:53:23 -0400 (EDT) Subject: Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of '__atomic_fetch_add') To: Mark Millard References: <95fdbf29-6c11-77a6-27a3-2d0dc30f1668@FreeBSD.org> <788B1EE7-EFC9-4AD4-9FD1-9876D0121189@yahoo.com> <9D40F38E-F1DC-4A3F-8792-09AD30D8802B@yahoo.com> <1ea2a8d0-b27a-503a-0a8b-48d7fbcd8fcb@FreeBSD.org> <0103123A-2D77-4D64-8FF6-97CD521CA7A8@yahoo.com> <11b515f2-5777-f983-bec5-e60bceda06ab@FreeBSD.org> <6DB0B921-30C8-4BF5-B610-770C0CBF1174@yahoo.com> <462BE582-0C2E-4D40-92F3-A27155777E58@yahoo.com> <1E03ECE7-297C-4D40-BC58-FB1903538181@yahoo.com> <8E61EA21-2DBE-4DED-A7E6-CCE4C79D0359@yahoo.com> Cc: Konstantin Belousov , FreeBSD Current From: John Baldwin Message-ID: Date: Fri, 3 Aug 2018 13:53:22 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <8E61EA21-2DBE-4DED-A7E6-CCE4C79D0359@yahoo.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Fri, 03 Aug 2018 16:53:23 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 20:53:24 -0000 I decided that it was better to fix our stdatomic.h, so I have a review to do that at https://reviews.freebsd.org/D16585 -- John Baldwin From owner-freebsd-current@freebsd.org Fri Aug 3 20:56:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E211310509CD for ; Fri, 3 Aug 2018 20:56:37 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 56D687508A for ; Fri, 3 Aug 2018 20:56:37 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id o11-v6so7514640wmh.2 for ; Fri, 03 Aug 2018 13:56:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=G7o+7uRFv+7ETrZbktIbX6K3kTJ68i+vKjd3NoR7FN8=; b=Gxq6tu255NUxLe58xQOyeTQ2trVtefca5ZFwEM3QvBdSTEC4u89/YJ0l42s2Ks++9+ G4var3q7Yab4dOlmNB6LVtRAJqqpJRW5K9uBLYI7bihX+efh/2c+a5h0AkWVaXxjWEAy qW8AcV+MEc2uuvdHhdDRTbc8TG/SijuQRs2044GmAxxPpWFgU3iBxM3RrEmocpl8hkWg Lf/NUbUNWpaEKpfm6dODX264lGn+LEohsPaIf+ss5aYEeeyWUWiN+Y1pda4HdDsCGmib n/lmQbGZ7amov5FfKSDTzaFuyG0G1QvkAR9voNP1YYoKYEEGevcOq4C/YiMri8Ii7+7Z wY5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=G7o+7uRFv+7ETrZbktIbX6K3kTJ68i+vKjd3NoR7FN8=; b=GDSIsMnSkoFanI03rdxNvn3wJ3xbW4G5yim2EG6bnX44uKknwTgnTuPveXFU6qRCR+ QyMqMf12X8eBjgvKWMBzC136tq2FjEWpO7RjSWLA8V4gdsdw+kqf5ef0uan21vLvk7LI oReYqp7+2UGQJuPblVfD7Hha4HG38JfNtWNLbQpOoHyCf/pedHZX2LjVJFv9x7C5bBJI mFKsmnTBCmzaWKGwWMoX4UnVybxNsgEwGSXfwJS638BAD1LWOUsU3l97ifz03uNIK5UM 77ySVRnpbq58skrTfbBdMJwWWw8V+ZfssoDmF3nkqRmmn69P9Rjz6iPzOW8zb7cp8jU8 sLJg== X-Gm-Message-State: AOUpUlEJAN1XCtADjleAAcjuzGVwNEcUrat/hvqYU2USfA5dcsoh+q17 JgV5KsmXyjKPd4sw7ZjBQ4lWy7aBcevL0JrZgfLNODqO X-Google-Smtp-Source: AAOMgpcu2PYWPDuqvDrcuRClzHbcPTNdLS8f/ijUK3UXK5QNhZwXnviJVTXLUp15c5I16Fuq1Z/0VwsCNaSv1iv5ONU= X-Received: by 2002:a1c:f03:: with SMTP id 3-v6mr5937618wmp.129.1533329796098; Fri, 03 Aug 2018 13:56:36 -0700 (PDT) MIME-Version: 1.0 References: <20180803204250.GE6049@kib.kiev.ua> In-Reply-To: <20180803204250.GE6049@kib.kiev.ua> From: Johannes Lundberg Date: Fri, 3 Aug 2018 21:55:58 +0100 Message-ID: Subject: Re: Linux process causes kernel panic To: Konstantin Belousov Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 20:56:38 -0000 On Fri, Aug 3, 2018 at 9:43 PM Konstantin Belousov wrote: > On Fri, Aug 03, 2018 at 09:26:08PM +0100, Johannes Lundberg wrote: > > Hi > > > > After install new kernel+world built from today's checkout I keep getting > > the same crash over and over. Never had this problem before. The previous > > kernel was from 3 weeks ago. > > > > Looks familiar to anyone? > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0xfffe665c > > fault code = supervisor write data, protection violation > > instruction pointer = 0x20:0xffffffff82282db3 > > stack pointer = 0x0:0xfffffe004c74c8c8 > > frame pointer = 0x0:0xfffffe004c74c980 > > 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 = 1579 (wcgrid_zika_vina_7.) > > trap number = 12 > > panic: page fault > > cpuid = 0 > > time = 1533327428 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > > 0xfffffe004c74c580 > > vpanic() at vpanic+0x1a3/frame 0xfffffe004c74c5e0 > > panic() at panic+0x43/frame 0xfffffe004c74c640 > > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe004c74c690 > > trap_pfault() at trap_pfault+0x62/frame 0xfffffe004c74c6e0 > > trap() at trap+0x2ba/frame 0xfffffe004c74c7f0 > > calltrap() at calltrap+0x8/frame 0xfffffe004c74c7f0 > > --- trap 0xc, rip = 0xffffffff82282db3, rsp = 0xfffffe004c74c8c8, rbp = > > 0xfffffe004c74c980 --- > > futex_xchgl() at futex_xchgl+0x23/frame 0xfffffe004c74c980 > > ia32_syscall() at ia32_syscall+0x29f/frame 0xfffffe004c74cab0 > > int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x4000001 > > Uptime: 7m29s > > Dumping 411 out of 8056 > MB:..4%..12%..24%..32%..43%..51%..63%..74%..82%..94% > > Dump complete > > Post first 40 lines from the verbose dmesg boot of your machine. > Table 'FACP' at 0xd970da80 Table 'APIC' at 0xd970db90 APIC: Found table at 0xd970db90 APIC: Using the MADT enumerator. Copyright (c) 1992-2018 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 12.0-CURRENT #86 d2391fd58c4(master)-dirty: Fri Aug 3 10:57:46 BST 2018 root@jd:/usr/obj/usr/src/amd64.amd64/sys/JD amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) WARNING: WITNESS option enabled, expect reduced performance. Table 'FACP' at 0xd970da80 Table 'APIC' at 0xd970db90 Table 'FPDT' at 0xd970dc18 Table 'FIDT' at 0xd970dc60 Table 'MCFG' at 0xd970dd00 Table 'HPET' at 0xd970dd40 Table 'SSDT' at 0xd970dd78 Table 'UEFI' at 0xd970e230 Table 'SSDT' at 0xd970e278 Table 'ASF!' at 0xd970eef8 Table 'SSDT' at 0xd970ef98 Table 'SSDT' at 0xd970f4b8 Table 'SSDT' at 0xd9710030 Table 'SSDT' at 0xd97101f8 Table 'PCCT' at 0xd97105a0 Table 'SSDT' at 0xd9710610 Table 'SSDT' at 0xd97110d8 Table 'SSDT' at 0xd9715288 Table 'SLIC' at 0xd9719790 Table 'MSDM' at 0xd9719908 Table 'DMAR' at 0xd9719960 Table 'BGRT' at 0xd9719a10 ACPI: No SRAT table found PPIM 0: PA=0xe0000000, VA=0xffffffff81a10000, size=0x7e9000, mode=0x1 VT(efifb): resolution 1920x1080 Preloaded elf kernel "/boot/kernel.JD/kernel" at 0xffffffff8186c000. Preloaded boot_entropy_cache "/boot/entropy" at 0xffffffff81875e58. Preloaded elf obj module "/boot/kernel.JD/snd_hda.ko" at 0xffffffff81875eb0. Preloaded elf obj module "/boot/kernel.JD/ums.ko" at 0xffffffff81876560. Table 'FACP' at 0xd970da80 FACP: Found table at 0xd970da80 Calibrating TSC clock ... TSC clock: 2194965386 Hz CPU: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (2194.97-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306d4 Family=0x6 Model=0x3d Stepping=4 Features=0xbfebfbff Features2=0x7ffafbbf AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x21c27ab XSAVE Features=0x1 VT-x: Basic Features=0xda0400 Pin-Based Controls=0x7f Primary Processor Controls=0xfff9fffe Secondary Processor Controls=0x53cff Exit Controls=0xda0400 Entry Controls=0xda0400 EPT Features=0x6334141 VPID Features=0xf01 TSC: P-state invariant, performance statistics Data TLB: 2 MByte or 4 MByte pages, 4-way set associative, 32 entries and a separate array with 1 GByte pages, 4-way set associative, 4 entries Data TLB: 4 KB pages, 4-way set associative, 64 entries Instruction TLB: 2M/4M pages, fully associative, 8 entries Instruction TLB: 4KByte pages, 8-way set associative, 64 entries 64-Byte prefetching Shared 2nd-Level TLB: 4 KByte /2 MByte pages, 6-way associative, 1536 entries. Also 1GBbyte pages, 4-way, 16 entries L2 cache: 256 kbytes, 8-way associative, 64 bytes/line real memory = 8589934592 (8192 MB) Physical memory chunk(s): 0x0000000000010000 - 0x0000000000057fff, 294912 bytes (72 pages) 0x0000000000059000 - 0x000000000005efff, 24576 bytes (6 pages) 0x0000000000060000 - 0x000000000009dfff, 253952 bytes (62 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x0000000001a00000 - 0x00000000bcb65fff, 3138805760 bytes (766310 pages) 0x00000000bcfef000 - 0x00000000d95aefff, 475791360 bytes (116160 pages) 0x00000000d971f000 - 0x00000000d9eb1fff, 7942144 bytes (1939 pages) 0x00000000dbaff000 - 0x00000000dbafffff, 4096 bytes (1 pages) 0x0000000100000000 - 0x0000000211d39fff, 4594049024 bytes (1121594 pages) avail memory = 8163524608 (7785 MB) Table 'FACP' at 0xd970da80 Table 'APIC' at 0xd970db90 Table 'FPDT' at 0xd970dc18 Table 'FIDT' at 0xd970dc60 Table 'MCFG' at 0xd970dd00 Table 'HPET' at 0xd970dd40 Table 'SSDT' at 0xd970dd78 Table 'UEFI' at 0xd970e230 Table 'SSDT' at 0xd970e278 Table 'ASF!' at 0xd970eef8 Table 'SSDT' at 0xd970ef98 Table 'SSDT' at 0xd970f4b8 Table 'SSDT' at 0xd9710030 Table 'SSDT' at 0xd97101f8 Table 'PCCT' at 0xd97105a0 Table 'SSDT' at 0xd9710610 Table 'SSDT' at 0xd97110d8 Table 'SSDT' at 0xd9715288 Table 'SLIC' at 0xd9719790 Table 'MSDM' at 0xd9719908 Table 'DMAR' at 0xd9719960 DMAR: Found table at 0xd9719960 x2APIC available but disabled by DMAR table MADT: Found CPU APIC ID 0 ACPI ID 1: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 2 ACPI ID 2: enabled SMP: Added CPU 2 (AP) MADT: Found CPU APIC ID 1 ACPI ID 3: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 3 ACPI ID 4: enabled SMP: Added CPU 3 (AP) Event timer "LAPIC" quality 600 LAPIC: ipi_wait() us multiplier 46 (r 4708131 tsc 2194965386) ACPI APIC Table: Package ID shift: 4 L3 cache ID shift: 4 L2 cache ID shift: 1 L1 cache ID shift: 1 Core ID shift: 1 INTR: Adding local APIC 2 as a target FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads Package HW ID = 0 Core HW ID = 0 CPU0 (BSP): APIC ID: 0 CPU1 (AP/HT): APIC ID: 1 Core HW ID = 1 CPU2 (AP): APIC ID: 2 CPU3 (AP/HT): APIC ID: 3 APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 3 APIC: CPU 2 has ACPI ID 2 APIC: CPU 3 has ACPI ID 4 x86bios: IVT 0x000000-0x0004ff at 0xfffff80000000000 x86bios: SSEG 0x059000-0x059fff at 0xfffffe00035c6000 x86bios: EBDA 0x091000-0x09ffff at 0xfffff80000091000 x86bios: ROM 0x0a0000-0x0fefff at 0xfffff800000a0000 lapic0: CMCI unmasked Pentium Pro MTRR support enabled random: read 3840 bytes from preloaded cache random: unblocking device. arc4random: read 32 bytes from preloaded cache VIMAGE (virtualized network stack) enabled ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ACPI: RSDP 0x00000000D96F9000 000024 (v02 DELL ) ACPI: XSDT 0x00000000D96F90A8 0000D4 (v01 DELL CBX3 01072009 AMI 00010013) ACPI: FACP 0x00000000D970DA80 00010C (v05 DELL CBX3 01072009 AMI 00010013) ACPI: DSDT 0x00000000D96F9210 01486B (v02 DELL CBX3 01072009 INTL 20120913) ACPI: FACS 0x00000000DA60FF80 000040 ACPI: APIC 0x00000000D970DB90 000084 (v03 DELL CBX3 01072009 AMI 00010013) ACPI: FPDT 0x00000000D970DC18 000044 (v01 DELL CBX3 01072009 AMI 00010013) ACPI: FIDT 0x00000000D970DC60 00009C (v01 DELL CBX3 01072009 AMI 00010013) ACPI: MCFG 0x00000000D970DD00 00003C (v01 DELL CBX3 01072009 MSFT 00000097) ACPI: HPET 0x00000000D970DD40 000038 (v01 DELL CBX3 01072009 AMI. 00000005) ACPI: SSDT 0x00000000D970DD78 0004B5 (v01 SataRe SataTabl 00001000 INTL 20120913) ACPI: UEFI 0x00000000D970E230 000042 (v01 00000000 00000000) ACPI: SSDT 0x00000000D970E278 000C7D (v02 Ther_R Ther_Rvp 00001000 INTL 20120913) ACPI: ASF! 0x00000000D970EEF8 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240) ACPI: SSDT 0x00000000D970EF98 00051F (v02 PmRef Cpu0Ist 00003000 INTL 20120913) ACPI: SSDT 0x00000000D970F4B8 000B74 (v02 CpuRef CpuSsdt 00003000 INTL 20120913) ACPI: SSDT 0x00000000D9710030 0001C7 (v02 PmRef LakeTiny 00003000 INTL 20120913) ACPI: SSDT 0x00000000D97101F8 0003A5 (v02 CppcTa CppcTabl 00001000 INTL 20120913) ACPI: PCCT 0x00000000D97105A0 00006E (v05 PcctTa PcctTabl 00001000 INTL 20120913) ACPI: SSDT 0x00000000D9710610 000AC4 (v02 Cpc_Ta Cpc_Tabl 00001000 INTL 20120913) ACPI: SSDT 0x00000000D97110D8 0041AC (v02 SaSsdt SaSsdt 00003000 INTL 20120913) ACPI: SSDT 0x00000000D9715288 004508 (v01 DptfTa DptfTabl 00001000 INTL 20120913) ACPI: SLIC 0x00000000D9719790 000176 (v03 DELL CBX3 01072009 MSFT 00010013) ACPI: MSDM 0x00000000D9719908 000055 (v03 DELL CBX3 06222004 AMI 00010013) ACPI: DMAR 0x00000000D9719960 0000B0 (v01 INTEL BDW 00000001 INTL 00000001) ACPI: BGRT 0x00000000D9719A10 000038 (v00 ?? 01072009 AMI 00010013) MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 ioapic0: ver 0x20 maxredir 0x27 ioapic0: Routing external 8259A's -> intpin 0 lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: level lapic0: LINT1 polarity: low lapic2: Routing NMI -> LINT1 lapic2: LINT1 trigger: edge lapic2: LINT1 polarity: low lapic1: Routing NMI -> LINT0 WARNING: Bogus Interrupt Trigger Mode. Assume CONFORMS. lapic1: LINT0 trigger: edge lapic1: LINT0 polarity: high lapic3: Routing NMI -> LINT1 lapic3: LINT1 trigger: edge lapic3: LINT1 polarity: low MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0 irqs 0-39 on motherboard lapic0: Forcing LINT1 to edge trigger lapic: Divisor 2, Frequency 49885584 Hz lapic: deadline tsc mode, Frequency 2194965386 Hz cpu0 BSP: ID: 0x00000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff x2APIC: 0 lint0: 0x00010700 lint1: 0x00002400 TPR: 0x00000000 SVR: 0x000011ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000000f2 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff x2APIC: 0 lint0: 0x00000400 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000011ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000100f2 lapic3: CMCI unmasked SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x03000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff x2APIC: 0 lint0: 0x00010700 lint1: 0x00002400 TPR: 0x00000000 SVR: 0x000011ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000000f2 SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x02000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff x2APIC: 0 lint0: 0x00010700 lint1: 0x00002400 TPR: 0x00000000 SVR: 0x000011ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000100f2 SMP: passed TSC synchronization test TSC timecounter discards lower 1 bit(s) Timecounter "TSC-low" frequency 1097482693 Hz quality 1000 wlan: <802.11 Link Layer> > > I have a guess what is going on, I need the dmesg to confirm. > If my guess is correct, you can use a workaround by setting the > "hw.cpu_stdext_disable=0x00100000" tunable at the loader prompt for now. > thanks I'll try that From owner-freebsd-current@freebsd.org Fri Aug 3 21:17:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3656310513C8 for ; Fri, 3 Aug 2018 21:17:15 +0000 (UTC) (envelope-from tommi.pernila@gmail.com) Received: from mail-qk0-f169.google.com (mail-qk0-f169.google.com [209.85.220.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE40875AEC; Fri, 3 Aug 2018 21:17:14 +0000 (UTC) (envelope-from tommi.pernila@gmail.com) Received: by mail-qk0-f169.google.com with SMTP id n85-v6so4874179qke.8; Fri, 03 Aug 2018 14:17:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uNG9aF2IEjsNFUrzSt8kIVRodUvRyZFPx/KUeFdoEu0=; b=dH9hfXSfDujsnoagtbHm8oQK9zdNMLm7/StijkDoNCbNGreGA2kRiBVRZyQwLgLzH9 HMcgO1U2VEuj5zc1k70YyRNB+Xp3HQNBzGC2LeQffwwkwIvvkXtbH5sg/p4+608iYfws +lkyFJpDW8xotNSTlXSVWIjtLITCnWnGz7Mpu7x9e82gxOvsCnpjCRIR40gLF14QmIAK pHjJpgGp+g05sJZNlplQv6NjNoSxFA1ajqwW9O3urLbuChUV8NFcX4wXnNNWY1eDqbfW L+F4OyP17E3qaTBwKgSfpBRyUJFLMdp85x/sq+smP5dgnfjyMcvBT4Tcw0XHgE+E9dA2 3dBQ== X-Gm-Message-State: AOUpUlERFoK+n/JuSGOZ4u4FJLlkmmkeBriMW3VyQGszoqGF+hduCLBN MjRUjNlhTxVR021utopJqPmbxi7JmN8TodXCi2s= X-Google-Smtp-Source: AAOMgpeIbUkcuiovR/z16817oH0r1TfwuV/BAfi0YY+rlAea5JVhKiR2Y9Z0h34xqDqrDmlFLmul5sAoA5HZOHVUEkE= X-Received: by 2002:a37:114b:: with SMTP id b72-v6mr4298946qkh.242.1533331033716; Fri, 03 Aug 2018 14:17:13 -0700 (PDT) MIME-Version: 1.0 References: <0e75a2ba-9a59-8301-a678-68a822025bd6@metricspace.net> <9df63df2-9d61-4106-f360-347411869b41@metricspace.net> <5ba11024-e99b-86e1-48b7-125fb80b4001@metricspace.net> <1531078307.1336.22.camel@freebsd.org> <06cb8190-7a04-5c92-8fb9-637d1a80758f@freebsd.org> <1533315524.1454.13.camel@freebsd.org> In-Reply-To: From: Tommi Pernila Date: Sat, 4 Aug 2018 00:17:02 +0300 Message-ID: Subject: Re: GELI with UEFI supporting Boot Environments goes to HEAD when? To: Warner Losh Cc: Allan Jude , Eric McCorkle , Ian Lepore , Oliver Pinter , Warner Losh , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 21:17:15 -0000 On Fri, 3 Aug 2018 at 20.17, Warner Losh wrote: > On Fri, Aug 3, 2018, 5:58 PM Ian Lepore wrote: > > > On Fri, 2018-08-03 at 19:54 +0300, Tommi Pernila wrote: > > > On Tue, 10 Jul 2018 at 1.05, Warner Losh wrote: > > > > > > > > > > > I have this in my tree already... > > > > > > > > Warner > > > > > > > > On Mon, Jul 9, 2018, 10:28 AM Allan Jude > > > > wrote: > > > > > > > > > > > > > > I will look at updating the rootgen.sh script this evening, to > > > > > support > > > > > creating more flexible ESP partitions, so we can drop the > > > > > loader.efi > > > > > into an msdosfs directly. > > > > > > > > > > On 07/08/2018 15:31, Ian Lepore wrote: > > > > > > > > > > > > On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote: > > > > > > > > > > > > > > Hi! > > > > > > > > > > > > > > Have you or Warner any update on this code? > > > > > > > > > > > > > > On Thursday, April 12, 2018, Eric McCorkle > > > > > > net> > > > > > > > wrote: > > > > > > > > > > > > > Are you aware of https://reviews.freebsd.org/D15743 ? > > > > > > > > > > > > That's my changes to add geli support to loader(8) in an > > > > > > architecture- > > > > > > agnostic way, so that "it just works" for all platforms and > > > > > > flavors of > > > > > > loader. It has been succesfully tested on armv6/7 (ubldr) and > > > > > > on x86 > > > > > > using qemu. The x86 tests cover ufs and zfs, legacy bios and > > > > > > uefi. The > > > > > > only variations that aren't tested yet are the uefi flavors, > > > > > > because > > > > > > the current rootgen.sh script for assembling test images is > > > > > > still using > > > > > > boot1.efi and I don't know enough about efi myself to update > > > > > > the script > > > > > > to make it assemble images the new way Warner envisions. > > > > > > > > > > > > -- Ian > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm in the middle of moving to a new apartment right > > > > > > > > now. It's > > > > > > > > going to > > > > > > > > be a bit before I can get to this. > > > > > > > > > > > > > > > > On 04/11/2018 20:31, Warner Losh wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > OK. I've pushed in the main part of it. The additional > > > > > > > > > work I > > > > > > > > > have > > > > > > > > > shouldn't affect any of this stuff. I was going to look > > > > > > > > > at what > > > > > > > > > part(s) > > > > > > > > > of your open reviewed needed to be redone tomorrow and > > > > > > > > > send you > > > > > > > > > feedback, but if you wanted to get a start before then, > > > > > > > > > I'm happy > > > > > > > > > to > > > > > > > > > answer questions. All the rest of my work is going to be > > > > > > > > > selecting the > > > > > > > > > root partition when we're told to us a specific > > > > > > > > > partition, so > > > > > > > > > will be > > > > > > > > > very constrained. > > > > > > > > > > > > > > > > > > Warner > > > > > > > > > > > > > > > > > > On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle > > > > > > > > icspace. > > > > > > > > > net > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > I think the thing to do at this point is to wait for > > > > > > > > > the > > > > > > > > > current > > > > > > > > work on > > > > > > > > > > > > > > > > > > > > > > > > > > > loader.efi to land, then adapt my patches to apply > > > > > > > > > against > > > > > > > > > that work. > > > > > > > > > > > > > > > > > > On 04/11/2018 15:06, Warner Losh wrote: > > > > > > > > > > Still reviewing the code. I'm worried it's too > > > > > > > > > i386 > > > > > > > > > specific and it > > > > > > > > > > conflicts with some work I'm doing. I'll have a > > > > > > > > > list of > > > > > > > > > actionable > > > > > > > > > > critiques this week. > > > > > > > > > > > > > > > > > > > > Warner > > > > > > > > > > > > > > > > > > > > On Wed, Apr 11, 2018 at 1:03 PM, Oliver Pinter > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Hi! > > > > > > > > > > > > > > > > > > > > Is there any update regarding the rebase or > > > > > > > > > the > > > > > > > > > inclusion to > > > > > > > > base > > > > > > > > > > > > > > > > > > > > > > > > > > > > system? > > > > > > > > > > On 3/28/18, Eric McCorkle > > > > > > > > t > > > > > > > > > > > > > > > > eric@metricspace.net> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > icspace.n > > > > > > > > > et>>> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'll do another rebase from head just to be > > > > > > > > > sure > > > > > > > > > > > > > > > > > > > > > > On March 28, 2018 3:23:23 PM EDT, Warner > > > > > > > > > Losh < > > > > > > > > imp@bsdimp.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > > > >>It's on my list for nexr, finally. I have an > > > > > > > > > alternate patch > > > > > > > > for > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>loader.efi > > > > > > > > > > >>from ESP, but i don't think it will affect > > > > > > > > > the GELI > > > > > > > > > stuff. I > > > > > > > > have some > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>time > > > > > > > > > > >>slotted for integration issues though. > > > > > > > > > > >> > > > > > > > > > > >>I am quite mindful of the freeze dates.... > > > > > > > > > I have > > > > > > > > > some uefi > > > > > > > > boot > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>loader > > > > > > > > > > >>protocol changes that I need to get in. > > > > > > > > > > >> > > > > > > > > > > >>Warner > > > > > > > > > > >> > > > > > > > > > > >>On Feb 21, 2018 11:18 PM, "Tommi Pernila" < > > > > > > > > tommi.pernila@iki.fi > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > nila@iki. > > > > > > > > > fi>>> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > >>> Awesome, thanks for the update and the > > > > > > > > > work that > > > > > > > > > you have > > > > > > > > done! > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > > > > >>> Now we just need some more reviewers eyes > > > > > > > > > on the > > > > > > > > > code :) > > > > > > > > > > >>> > > > > > > > > > > >>> Br, > > > > > > > > > > >>> > > > > > > > > > > >>> Tommi > > > > > > > > > > >>> > > > > > > > > > > >>> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle > > > > > > > > > < > > > > > > > > eric@metricspace.net > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > icspace.n > > > > > > > > > et>>> > > > > > > > > > > >>wrote: > > > > > > > > > > >>> > > > > > > > > > > >>>> FYI, I just IFC'ed everything, and the > > > > > > > > > current > > > > > > > > > patches > > > > > > > > > are still > > > > > > > > > > >>fine. > > > > > > > > > > >>>> > > > > > > > > > > >>>> Also, the full GELI + standalone loader > > > > > > > > > has been > > > > > > > > > deployed > > > > > > > > > on one of > > > > > > > > > > >>my > > > > > > > > > > >>>> laptops for some time now. > > > > > > > > > > >>>> > > > > > > > > > > >>>> On 02/21/2018 18:15, Eric McCorkle wrote: > > > > > > > > > > >>>> > The GELI work could be merged at this > > > > > > > > > point, > > > > > > > > > though it > > > > > > > > > won't be > > > > > > > > > > >>usable > > > > > > > > > > >>>> > without an additional patch to enable > > > > > > > > > loader- > > > > > > > > > only > > > > > > > > > operation. The > > > > > > > > > > >>>> > patches are currently up for review: > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > This is the order in which they'd need > > > > > > > > > to be > > > > > > > > > merged: > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > https://reviews.freebsd.org/D12732 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > This one changes the efipart > > > > > > > > > device. Toomas > > > > > > > > > Soome > > > > > > > > > identified > > > > > > > > > > some > > > > > > > > > > >>>> > problems, which I have addressed. He > > > > > > > > > has not > > > > > > > > > re-reviewed it, > > > > > > > > > > >>however. > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > https://reviews.freebsd.org/D12692 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > This adds some crypto code needed for > > > > > > > > > GELI. It > > > > > > > > > simply > > > > > > > > > adds new > > > > > > > > > > >>code, > > > > > > > > > > >>>> > and doesn't conflict with anything. > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > https://reviews.freebsd.org/D12698 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > This adds the EFI KMS interface code, > > > > > > > > > and has > > > > > > > > > the EFI > > > > > > > > > loader pass > > > > > > > > > > >>keys > > > > > > > > > > >>>> > into the keybuf interface. > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > I can't post the main GELI driver until > > > > > > > > > those > > > > > > > > > get > > > > > > > > > merged, as it > > > > > > > > > > >>depends > > > > > > > > > > >>>> > on them. It can be found on the geli > > > > > > > > > branch on > > > > > > > > > my > > > > > > > > > github freebsd > > > > > > > > > > >>>> > repository, however. > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > Additionally, you need this patch, > > > > > > > > > which allows > > > > > > > > > loader.efi to > > > > > > > > > > >>function > > > > > > > > > > >>>> > when installed directly to the ESP: > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > https://reviews.freebsd.org/D13497 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > On 02/20/2018 22:56, Tommi Pernila > > > > > > > > > wrote: > > > > > > > > > > >>>> >> Hi Eric, > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> could you provide a brief update how > > > > > > > > > the work > > > > > > > > > is going? > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> Br, > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> Tommi > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> On Nov 16, 2017 04:29, "Eric McCorkle" > > > > > > > > > > > > > > > > > > > > > > > > > > > icspace.n > > > > > > > > > et>> > > > > > > > > > > >>>> >> > > > > > > > > > > > > > > > > ce.net > > > > > > > > > >>> > > > > > > > > > > wrote: > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> Right, so basically, the remaining > > > > > > > > > GELI > > > > > > > > > patches > > > > > > > > > are against > > > > > > > > > > >>>> loader, and > > > > > > > > > > >>>> >> most of them can go in > > > > > > > > > independently of the > > > > > > > > > work > > > > > > > > > on removing > > > > > > > > > > >>boot1. > > > > > > > > > > >>>> >> There's a unanimous consensus on > > > > > > > > > getting > > > > > > > > > rid of > > > > > > > > > boot1 which > > > > > > > > > > >>>> includes its > > > > > > > > > > >>>> >> original author, so that's going > > > > > > > > > to happen. > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> For GELI, we have the following > > > > > > > > > (not > > > > > > > > > necessarily > > > > > > > > > in order): > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> a) Adding the KMS interfaces, > > > > > > > > > pseudo- > > > > > > > > > device, and > > > > > > > > > kernel > > > > > > > > > > >>keybuf > > > > > > > > > > >>>> >> interactions > > > > > > > > > > >>>> >> b) Modifications to the efipart > > > > > > > > > driver > > > > > > > > > > >>>> >> c) boot crypto > > > > > > > > > > >>>> >> d) GELI partition types (not > > > > > > > > > strictly > > > > > > > > > necessary) > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> Then there's the GELI driver > > > > > > > > > itself. (a) > > > > > > > > > and (c) > > > > > > > > are > > > > > > > > > > > > > > > > > > > > > > > > > > > > good to > > > > > > > > > > >>>> land, (b) > > > > > > > > > > >>>> >> needs some more work after Toomas > > > > > > > > > Soome > > > > > > > > > pointed > > > > > > > > out a > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>legitimate > > > > > > > > > > >>>> >> problem, and (d) actually needs a > > > > > > > > > good bit > > > > > > > > > more > > > > > > > > > code (but > > > > > > > > > > >>again, > > > > > > > > > > >>>> it's > > > > > > > > > > >>>> >> more cosmetic). Additionally, the > > > > > > > > > GELI > > > > > > > > > driver > > > > > > > > > will need > > > > > > > > > > >>further > > > > > > > > > > >>>> mods to > > > > > > > > > > >>>> >> efipart to be written (nothing too > > > > > > > > > big). But we > > > > > > > > > could go > > > > > > > > > > >>ahead > > > > > > > > > > >>>> with (a) > > > > > > > > > > >>>> >> and (c), as they've already been > > > > > > > > > proven to > > > > > > > > > work. > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> I'd wanted to have this stuff > > > > > > > > > shaped up > > > > > > > > > sooner, > > > > > > > > > but I'm > > > > > > > > > > >>>> preoccupied with > > > > > > > > > > >>>> >> the 7th RISC-V workshop at the end > > > > > > > > > of the > > > > > > > > > month. > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> Once this stuff is all in, loader > > > > > > > > > should > > > > > > > > > handle > > > > > > > > > any GELI > > > > > > > > > > >>volumes it > > > > > > > > > > >>>> >> finds, and it should Just Work > > > > > > > > > once boot1 > > > > > > > > > is gone. > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> >> > > > > > > > > > > >>>> > > > > > > > > > > _______________________________________________ > > > > > > > > > > >>>> > freebsd-current@freebsd.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > mailing list > > > > > > > > > > >>>> > https://lists.freebsd.org/mailman/listi > > > > > > > > > nfo/freeb > > > > > > > > > sd- > > > > > > > > current > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > current> > > > > > > > > > > > > > > > > > > eebsd-cur > > > > > > > > > rent > > > > > > > > > > > > > > > > > current>> > > > > > > > > > > >>>> > To unsubscribe, send any mail to > > > > > > > > "freebsd-current-unsubscribe@ > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>>> freebsd.org > > > > > > > > > " > > > > > > > > > > >>>> > > > > > > > > > > > >>>> > > > > > > > > > > >>> > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > Sent from my Android device with K-9 Mail. > > > > > > > > > Please > > > > > > > > > excuse my > > > > > > > > brevity. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > freebsd-current@freebsd.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > mailing list > > > > > > > > > > > https://lists.freebsd.org/mailman/listinfo/f > > > > > > > > > reebsd-cu > > > > > > > > > rrent > > > > > > > > > > > > > > > > > current> > > > > > > > > > > > > > > > > > > eebsd-cur > > > > > > > > > rent > > > > > > > > > > > > > > > > > current>> > > > > > > > > > > > To unsubscribe, send any mail to > > > > > > > > > > "freebsd-current-unsubscribe@freebsd.org > > > > > > > > > > > > > > > > > > > > > > > > > > > g > > > > > > > > > >" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > 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" > > > > > -- > > > > > Allan Jude > > > > > > > > Hi all, > > > > > > could anyone comment on the overall status of this feature? > > > Is it going to make in 12.0 as it's code freeze is nearing up? > > > > > > Br, > > > > > > Tommi > > > > I'm not sure what part of the above mix of top- and bottom-posted > > replies you're asking about. The support for GELI when booting from > > UEFI is already in 12-current. I don't know anything about the "boot > > environments" stuff (like, even what it means). > > > > After Ian's changes, it should all be good. Once the disk is unlocked, you > can do anything. Including ZFS boot environments that we already support > for unencrypted disks. > > Warner > Excellent news! Thank you all for your work on this! *starts updating CURRENT install* -Tommi > From owner-freebsd-current@freebsd.org Fri Aug 3 21:20:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBE3310515C8 for ; Fri, 3 Aug 2018 21:20:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3932B75D1F for ; Fri, 3 Aug 2018 21:20:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id i18-v6so6112909ioj.13 for ; Fri, 03 Aug 2018 14:20:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZOCgteSEbaOliTjwoQJbw4rJogkJs2XOAZasRf/Zjik=; b=B2OtV5X1PFynJAbz8W8bdo6lZSAWrwmolxVmMbXQ2kHs/5t04fT651xqQmEFs1WXBi YWV10yHv3OhY/kVGB4SOetwNVjm5lFRzau9dmp/uUFNh2YdgUVBSg0bBZf0mr7VyI8tw B1OgKUrzrhwCPQm2MsnHlJBF0rOuW2GX7x2PV4DFbPRButwlO7957LF6L3e2mwNRsmIJ V8/jHC/P4FcoB6Zna7YFEi4RH8AoR1vcQwTes9007URvLzLQ0LTaaHLmWOVcHyX9oGLY AFeEjkVYqA9VYOZyzrAGtLIJhaOMWK2CL14YiUe4DkjCBZiy3X0tRmyJyiGtutzyWEa1 LZsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZOCgteSEbaOliTjwoQJbw4rJogkJs2XOAZasRf/Zjik=; b=VrUAa517kxYw9K6qTBE1FnyhrcbBFtq8K5+bQFjbEfGufVM5t3oWnPtHBm4R9T1a7l Y0QBuS9CkyZmIMlELY6fa1lxHnf1JaZFqCdNVPXVi51LY4I7LhRG/gwCwX33RbCv3npK jx0l4V6PVdt4iJyl0WHyOPSMi8NBSvQ/09b7wj7NHCi+jEqXbDCN7k/V8ixFNtB/aNgy Wy5E9VBn0btHKfNeC8W0Mvg6XQ+dYY6Sc9hqgi05Ufhe+uWe2n0BlXX/MMSKmIE2acmz 6X+LawvJFceGaOFSOrPEARoeKDDgKpZUo+7kA61k6iKzqHhNpvp4RSmNWtndveOPWUd3 HM4g== X-Gm-Message-State: AOUpUlFhsNIvGg1zId27HzxwLsBix2yKLqWfb+lOvIJcEAA/0FZz5JeO 1wSJiCC7BjwkvhHqYCLV5vDb/vSXT86XcsGXSde78Q== X-Google-Smtp-Source: AA+uWPxBiTduBXX88jO5WVdpvw7EUYJ417WR/0+GtE/Wc1LCyQ76zoPb/3fcfRzT4apE56pPamRetRQqRJBc+S5mEdM= X-Received: by 2002:a6b:d004:: with SMTP id x4-v6mr7309764ioa.299.1533331211344; Fri, 03 Aug 2018 14:20:11 -0700 (PDT) MIME-Version: 1.0 References: <0e75a2ba-9a59-8301-a678-68a822025bd6@metricspace.net> <9df63df2-9d61-4106-f360-347411869b41@metricspace.net> <5ba11024-e99b-86e1-48b7-125fb80b4001@metricspace.net> <1531078307.1336.22.camel@freebsd.org> <06cb8190-7a04-5c92-8fb9-637d1a80758f@freebsd.org> <1533315524.1454.13.camel@freebsd.org> In-Reply-To: From: Warner Losh Date: Fri, 3 Aug 2018 22:20:00 +0100 Message-ID: Subject: Re: GELI with UEFI supporting Boot Environments goes to HEAD when? To: Tommi Pernila Cc: Allan Jude , Eric McCorkle , Ian Lepore , Oliver Pinter , Warner Losh , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 21:20:13 -0000 On Fri, Aug 3, 2018, 10:17 PM Tommi Pernila wrote: > > > On Fri, 3 Aug 2018 at 20.17, Warner Losh wrote: > >> On Fri, Aug 3, 2018, 5:58 PM Ian Lepore wrote: >> >> > On Fri, 2018-08-03 at 19:54 +0300, Tommi Pernila wrote: >> > > On Tue, 10 Jul 2018 at 1.05, Warner Losh wrote: >> > > >> > > > >> > > > I have this in my tree already... >> > > > >> > > > Warner >> > > > >> > > > On Mon, Jul 9, 2018, 10:28 AM Allan Jude >> > > > wrote: >> > > > >> > > > > >> > > > > I will look at updating the rootgen.sh script this evening, to >> > > > > support >> > > > > creating more flexible ESP partitions, so we can drop the >> > > > > loader.efi >> > > > > into an msdosfs directly. >> > > > > >> > > > > On 07/08/2018 15:31, Ian Lepore wrote: >> > > > > > >> > > > > > On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote: >> > > > > > > >> > > > > > > Hi! >> > > > > > > >> > > > > > > Have you or Warner any update on this code? >> > > > > > > >> > > > > > > On Thursday, April 12, 2018, Eric McCorkle > > > > > > > net> >> > > > > > > wrote: >> > > > > > > >> > > > > > Are you aware of https://reviews.freebsd.org/D15743 ? >> > > > > > >> > > > > > That's my changes to add geli support to loader(8) in an >> > > > > > architecture- >> > > > > > agnostic way, so that "it just works" for all platforms and >> > > > > > flavors of >> > > > > > loader. It has been succesfully tested on armv6/7 (ubldr) and >> > > > > > on x86 >> > > > > > using qemu. The x86 tests cover ufs and zfs, legacy bios and >> > > > > > uefi. The >> > > > > > only variations that aren't tested yet are the uefi flavors, >> > > > > > because >> > > > > > the current rootgen.sh script for assembling test images is >> > > > > > still using >> > > > > > boot1.efi and I don't know enough about efi myself to update >> > > > > > the script >> > > > > > to make it assemble images the new way Warner envisions. >> > > > > > >> > > > > > -- Ian >> > > > > > >> > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > I'm in the middle of moving to a new apartment right >> > > > > > > > now. It's >> > > > > > > > going to >> > > > > > > > be a bit before I can get to this. >> > > > > > > > >> > > > > > > > On 04/11/2018 20:31, Warner Losh wrote: >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > OK. I've pushed in the main part of it. The additional >> > > > > > > > > work I >> > > > > > > > > have >> > > > > > > > > shouldn't affect any of this stuff. I was going to look >> > > > > > > > > at what >> > > > > > > > > part(s) >> > > > > > > > > of your open reviewed needed to be redone tomorrow and >> > > > > > > > > send you >> > > > > > > > > feedback, but if you wanted to get a start before then, >> > > > > > > > > I'm happy >> > > > > > > > > to >> > > > > > > > > answer questions. All the rest of my work is going to be >> > > > > > > > > selecting the >> > > > > > > > > root partition when we're told to us a specific >> > > > > > > > > partition, so >> > > > > > > > > will be >> > > > > > > > > very constrained. >> > > > > > > > > >> > > > > > > > > Warner >> > > > > > > > > >> > > > > > > > > On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle > > > > > > > > > icspace. >> > > > > > > > > net >> > > > > > > > > > wrote: >> > > > > > > > > >> > > > > > > > > I think the thing to do at this point is to wait for >> > > > > > > > > the >> > > > > > > > > current >> > > > > > > > work on >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > loader.efi to land, then adapt my patches to apply >> > > > > > > > > against >> > > > > > > > > that work. >> > > > > > > > > >> > > > > > > > > On 04/11/2018 15:06, Warner Losh wrote: >> > > > > > > > > > Still reviewing the code. I'm worried it's too >> > > > > > > > > i386 >> > > > > > > > > specific and it >> > > > > > > > > > conflicts with some work I'm doing. I'll have a >> > > > > > > > > list of >> > > > > > > > > actionable >> > > > > > > > > > critiques this week. >> > > > > > > > > > >> > > > > > > > > > Warner >> > > > > > > > > > >> > > > > > > > > > On Wed, Apr 11, 2018 at 1:03 PM, Oliver Pinter >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > >> >> > > > > > > > > > wrote: >> > > > > > > > > > >> > > > > > > > > > Hi! >> > > > > > > > > > >> > > > > > > > > > Is there any update regarding the rebase or >> > > > > > > > > the >> > > > > > > > > inclusion to >> > > > > > > > base >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > system? >> > > > > > > > > > On 3/28/18, Eric McCorkle > > > > > > > > > t >> > > > > > > > > > > > > > > > > eric@metricspace.net> >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > icspace.n >> > > > > > > > > et>>> >> > > > > > > > wrote: >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > I'll do another rebase from head just to be >> > > > > > > > > sure >> > > > > > > > > > > >> > > > > > > > > > > On March 28, 2018 3:23:23 PM EDT, Warner >> > > > > > > > > Losh < >> > > > > > > > imp@bsdimp.com >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> wrote: >> > > > > > > > > > >>It's on my list for nexr, finally. I have an >> > > > > > > > > alternate patch >> > > > > > > > for >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >>loader.efi >> > > > > > > > > > >>from ESP, but i don't think it will affect >> > > > > > > > > the GELI >> > > > > > > > > stuff. I >> > > > > > > > have some >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >>time >> > > > > > > > > > >>slotted for integration issues though. >> > > > > > > > > > >> >> > > > > > > > > > >>I am quite mindful of the freeze dates.... >> > > > > > > > > I have >> > > > > > > > > some uefi >> > > > > > > > boot >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >>loader >> > > > > > > > > > >>protocol changes that I need to get in. >> > > > > > > > > > >> >> > > > > > > > > > >>Warner >> > > > > > > > > > >> >> > > > > > > > > > >>On Feb 21, 2018 11:18 PM, "Tommi Pernila" < >> > > > > > > > tommi.pernila@iki.fi >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > nila@iki. >> > > > > > > > > fi>>> >> > > > > > > > wrote: >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >> >> > > > > > > > > > >>> Awesome, thanks for the update and the >> > > > > > > > > work that >> > > > > > > > > you have >> > > > > > > > done! >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >>> >> > > > > > > > > > >>> Now we just need some more reviewers eyes >> > > > > > > > > on the >> > > > > > > > > code :) >> > > > > > > > > > >>> >> > > > > > > > > > >>> Br, >> > > > > > > > > > >>> >> > > > > > > > > > >>> Tommi >> > > > > > > > > > >>> >> > > > > > > > > > >>> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle >> > > > > > > > > < >> > > > > > > > eric@metricspace.net >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > icspace.n >> > > > > > > > > et>>> >> > > > > > > > > > >>wrote: >> > > > > > > > > > >>> >> > > > > > > > > > >>>> FYI, I just IFC'ed everything, and the >> > > > > > > > > current >> > > > > > > > > patches >> > > > > > > > > are still >> > > > > > > > > > >>fine. >> > > > > > > > > > >>>> >> > > > > > > > > > >>>> Also, the full GELI + standalone loader >> > > > > > > > > has been >> > > > > > > > > deployed >> > > > > > > > > on one of >> > > > > > > > > > >>my >> > > > > > > > > > >>>> laptops for some time now. >> > > > > > > > > > >>>> >> > > > > > > > > > >>>> On 02/21/2018 18:15, Eric McCorkle wrote: >> > > > > > > > > > >>>> > The GELI work could be merged at this >> > > > > > > > > point, >> > > > > > > > > though it >> > > > > > > > > won't be >> > > > > > > > > > >>usable >> > > > > > > > > > >>>> > without an additional patch to enable >> > > > > > > > > loader- >> > > > > > > > > only >> > > > > > > > > operation. The >> > > > > > > > > > >>>> > patches are currently up for review: >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > This is the order in which they'd need >> > > > > > > > > to be >> > > > > > > > > merged: >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > https://reviews.freebsd.org/D12732 >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > This one changes the efipart >> > > > > > > > > device. Toomas >> > > > > > > > > Soome >> > > > > > > > > identified >> > > > > > > > > > some >> > > > > > > > > > >>>> > problems, which I have addressed. He >> > > > > > > > > has not >> > > > > > > > > re-reviewed it, >> > > > > > > > > > >>however. >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > https://reviews.freebsd.org/D12692 >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > This adds some crypto code needed for >> > > > > > > > > GELI. It >> > > > > > > > > simply >> > > > > > > > > adds new >> > > > > > > > > > >>code, >> > > > > > > > > > >>>> > and doesn't conflict with anything. >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > https://reviews.freebsd.org/D12698 >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > This adds the EFI KMS interface code, >> > > > > > > > > and has >> > > > > > > > > the EFI >> > > > > > > > > loader pass >> > > > > > > > > > >>keys >> > > > > > > > > > >>>> > into the keybuf interface. >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > I can't post the main GELI driver until >> > > > > > > > > those >> > > > > > > > > get >> > > > > > > > > merged, as it >> > > > > > > > > > >>depends >> > > > > > > > > > >>>> > on them. It can be found on the geli >> > > > > > > > > branch on >> > > > > > > > > my >> > > > > > > > > github freebsd >> > > > > > > > > > >>>> > repository, however. >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > Additionally, you need this patch, >> > > > > > > > > which allows >> > > > > > > > > loader.efi to >> > > > > > > > > > >>function >> > > > > > > > > > >>>> > when installed directly to the ESP: >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > https://reviews.freebsd.org/D13497 >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> > On 02/20/2018 22:56, Tommi Pernila >> > > > > > > > > wrote: >> > > > > > > > > > >>>> >> Hi Eric, >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> could you provide a brief update how >> > > > > > > > > the work >> > > > > > > > > is going? >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> Br, >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> Tommi >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> On Nov 16, 2017 04:29, "Eric McCorkle" >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > icspace.n >> > > > > > > > > et>> >> > > > > > > > > > >>>> >> > > > > > > > > > > > > > > > > > > ce.net >> > > > > > > > > >>> >> > > > > > > > > > wrote: >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> Right, so basically, the remaining >> > > > > > > > > GELI >> > > > > > > > > patches >> > > > > > > > > are against >> > > > > > > > > > >>>> loader, and >> > > > > > > > > > >>>> >> most of them can go in >> > > > > > > > > independently of the >> > > > > > > > > work >> > > > > > > > > on removing >> > > > > > > > > > >>boot1. >> > > > > > > > > > >>>> >> There's a unanimous consensus on >> > > > > > > > > getting >> > > > > > > > > rid of >> > > > > > > > > boot1 which >> > > > > > > > > > >>>> includes its >> > > > > > > > > > >>>> >> original author, so that's going >> > > > > > > > > to happen. >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> For GELI, we have the following >> > > > > > > > > (not >> > > > > > > > > necessarily >> > > > > > > > > in order): >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> a) Adding the KMS interfaces, >> > > > > > > > > pseudo- >> > > > > > > > > device, and >> > > > > > > > > kernel >> > > > > > > > > > >>keybuf >> > > > > > > > > > >>>> >> interactions >> > > > > > > > > > >>>> >> b) Modifications to the efipart >> > > > > > > > > driver >> > > > > > > > > > >>>> >> c) boot crypto >> > > > > > > > > > >>>> >> d) GELI partition types (not >> > > > > > > > > strictly >> > > > > > > > > necessary) >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> Then there's the GELI driver >> > > > > > > > > itself. (a) >> > > > > > > > > and (c) >> > > > > > > > are >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > good to >> > > > > > > > > > >>>> land, (b) >> > > > > > > > > > >>>> >> needs some more work after Toomas >> > > > > > > > > Soome >> > > > > > > > > pointed >> > > > > > > > out a >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >>legitimate >> > > > > > > > > > >>>> >> problem, and (d) actually needs a >> > > > > > > > > good bit >> > > > > > > > > more >> > > > > > > > > code (but >> > > > > > > > > > >>again, >> > > > > > > > > > >>>> it's >> > > > > > > > > > >>>> >> more cosmetic). Additionally, the >> > > > > > > > > GELI >> > > > > > > > > driver >> > > > > > > > > will need >> > > > > > > > > > >>further >> > > > > > > > > > >>>> mods to >> > > > > > > > > > >>>> >> efipart to be written (nothing too >> > > > > > > > > big). But we >> > > > > > > > > could go >> > > > > > > > > > >>ahead >> > > > > > > > > > >>>> with (a) >> > > > > > > > > > >>>> >> and (c), as they've already been >> > > > > > > > > proven to >> > > > > > > > > work. >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> I'd wanted to have this stuff >> > > > > > > > > shaped up >> > > > > > > > > sooner, >> > > > > > > > > but I'm >> > > > > > > > > > >>>> preoccupied with >> > > > > > > > > > >>>> >> the 7th RISC-V workshop at the end >> > > > > > > > > of the >> > > > > > > > > month. >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> Once this stuff is all in, loader >> > > > > > > > > should >> > > > > > > > > handle >> > > > > > > > > any GELI >> > > > > > > > > > >>volumes it >> > > > > > > > > > >>>> >> finds, and it should Just Work >> > > > > > > > > once boot1 >> > > > > > > > > is gone. >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> >> >> > > > > > > > > > >>>> > >> > > > > > > > > _______________________________________________ >> > > > > > > > > > >>>> > freebsd-current@freebsd.org >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > mailing list >> > > > > > > > > > >>>> > https://lists.freebsd.org/mailman/listi >> > > > > > > > > nfo/freeb >> > > > > > > > > sd- >> > > > > > > > current >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > > > current> >> > > > > > > > > > > > > > > > > > > eebsd-cur >> > > > > > > > > rent >> > > > > > > > > > > > > > > > > > current>> >> > > > > > > > > > >>>> > To unsubscribe, send any mail to >> > > > > > > > "freebsd-current-unsubscribe@ >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >>>> freebsd.org >> > > > > > > > > " >> > > > > > > > > > >>>> > >> > > > > > > > > > >>>> >> > > > > > > > > > >>> >> > > > > > > > > > > >> > > > > > > > > > > -- >> > > > > > > > > > > Sent from my Android device with K-9 Mail. >> > > > > > > > > Please >> > > > > > > > > excuse my >> > > > > > > > brevity. >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > _______________________________________________ >> > > > > > > > > > > freebsd-current@freebsd.org >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > mailing list >> > > > > > > > > > > https://lists.freebsd.org/mailman/listinfo/f >> > > > > > > > > reebsd-cu >> > > > > > > > > rrent >> > > > > > > > > > > > > > > > > > current> >> > > > > > > > > > > > > > > > > > > eebsd-cur >> > > > > > > > > rent >> > > > > > > > > > > > > > > > > > current>> >> > > > > > > > > > > To unsubscribe, send any mail to >> > > > > > > > > > "freebsd-current-unsubscribe@freebsd.org >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > g >> > > > > > > > > >" >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > _______________________________________________ >> > > > > > > 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" >> > > > > -- >> > > > > Allan Jude >> > > > > >> > > Hi all, >> > > >> > > could anyone comment on the overall status of this feature? >> > > Is it going to make in 12.0 as it's code freeze is nearing up? >> > > >> > > Br, >> > > >> > > Tommi >> > >> > I'm not sure what part of the above mix of top- and bottom-posted >> > replies you're asking about. The support for GELI when booting from >> > UEFI is already in 12-current. I don't know anything about the "boot >> > environments" stuff (like, even what it means). >> > >> >> After Ian's changes, it should all be good. Once the disk is unlocked, you >> can do anything. Including ZFS boot environments that we already support >> for unencrypted disks. >> >> Warner >> > > Excellent news! > > Thank you all for your work on this! > > *starts updating CURRENT install* > Let us know of there is a problem... Warner > From owner-freebsd-current@freebsd.org Fri Aug 3 21:25:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03A9B1051EE2 for ; Fri, 3 Aug 2018 21:25:52 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 7C96776383 for ; Fri, 3 Aug 2018 21:25:51 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: c3a22236-9763-11e8-aff6-0b9b8210da61 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id c3a22236-9763-11e8-aff6-0b9b8210da61; Fri, 03 Aug 2018 21:25:39 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w73LPbD3044149; Fri, 3 Aug 2018 15:25:37 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533331537.1454.26.camel@freebsd.org> Subject: Re: GELI with UEFI supporting Boot Environments goes to HEAD when? From: Ian Lepore To: Warner Losh , Tommi Pernila Cc: Allan Jude , Eric McCorkle , Oliver Pinter , Warner Losh , freebsd-current Date: Fri, 03 Aug 2018 15:25:37 -0600 In-Reply-To: References: <0e75a2ba-9a59-8301-a678-68a822025bd6@metricspace.net> <9df63df2-9d61-4106-f360-347411869b41@metricspace.net> <5ba11024-e99b-86e1-48b7-125fb80b4001@metricspace.net> <1531078307.1336.22.camel@freebsd.org> <06cb8190-7a04-5c92-8fb9-637d1a80758f@freebsd.org> <1533315524.1454.13.camel@freebsd.org> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Aug 2018 21:25:52 -0000 On Fri, 2018-08-03 at 22:20 +0100, Warner Losh wrote: > On Fri, Aug 3, 2018, 10:17 PM Tommi Pernila > wrote: > > > > > > > > > On Fri, 3 Aug 2018 at 20.17, Warner Losh wrote: > > > > > [...] > > Thank you all for your work on this! > > > > *starts updating CURRENT install* > > > Let us know of there is a problem... And don't forget to do the often-skipped "mergemaster -p" step of the updating before doing the installworld, to add the new ntpd user. :) -- Ian From owner-freebsd-current@freebsd.org Sat Aug 4 03:11:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B6D4105B985 for ; Sat, 4 Aug 2018 03:11:21 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw1-xc44.google.com (mail-yw1-xc44.google.com [IPv6:2607:f8b0:4864:20::c44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A21228214C for ; Sat, 4 Aug 2018 03:11:20 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw1-xc44.google.com with SMTP id z143-v6so1717706ywa.7 for ; Fri, 03 Aug 2018 20:11:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to; bh=YXcqXtaXAW/iG41/BIDFhcVfPDDqOL3Ta/Z3RM7rcUs=; b=FlC3ri80pSdbvO5mBIpdoFTSlVE1uWaM8LmyakUZktq39k2nnPSbz8qbwnnpyLdmSI e5ppwdFqb3tx6enUK1E8awpdnKbfSunqiCNYyXPSHCqIyZqrm3C95YxgRoN1Enit3k3x 0e9vOnfzwTfN8E5qc+ubwd+ud+unPQOVd6T7Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=YXcqXtaXAW/iG41/BIDFhcVfPDDqOL3Ta/Z3RM7rcUs=; b=DF9hhaYc+KATZc1PnFIhvzVIptdJoUCoxhIw0zbCv23kYugPVeSFGSOCiIvgg16KtH v4qRg/lEoD48xLY1KeTubuyq1boj8ShbNapHqR/aJ5iABgCHqzNCwh97czvIT6oFhgyM PYTaMA/y1q3XhEsn1MTgU9jlS1wDGr5c9/mkEs0B/komfLEnRfYok0+ahb/4yburfKFe wbhOto6tAGYAySfDUkiMLOsGgUIAl8Pmmw68w0O93NM8RNfg0KTpdQOqQCFuw8mu+72W UO8XzZwGeBl7lYXad/a1VU9P3Lip95DPlbCLGO9dGod24e654oW6PtIrLTK2H3EOsyWr eElQ== X-Gm-Message-State: AOUpUlFsLGaAXleSFmjCPl1m/2/vuv77dUa5AIUaGTc3tzj6tU42lXla cdxkpYX7nZeanP+DTcZ+C1YCxhlbBVK3i/T0iJ9fKQ== X-Google-Smtp-Source: AAOMgpclb4eP9AeUd+TmKtRDrh8YQ0d7O6m0f8X06zU+RxuJanAWqTWdZlw0dTgrUT+pcnX6bV1udg/aIIMZUcfThYU= X-Received: by 2002:a0d:e846:: with SMTP id r67-v6mr3598598ywe.19.1533352279375; Fri, 03 Aug 2018 20:11:19 -0700 (PDT) MIME-Version: 1.0 From: Eitan Adler Date: Fri, 3 Aug 2018 20:10:52 -0700 Message-ID: Subject: panic: mutex pmap not owned at ... efirt_machdep.c:255 To: Konstantin Belousov , freebsd-current Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 03:11:21 -0000 Hi all, After installing the latest current kernel I get the following panic: panic: mutex pmap not owned at ... efirt_machdep.c:255 cpuid =3 time = 1 ... mtx_assert() efi_arch_enter() efirt_modevents() module_register_init() mi_startup() btext() Unfortunately this appears to be early enough that the keyboard is not usable. I'll try to bisect this over the next few days unless someone has an idea is to the exact cause. -- Eitan Adler From owner-freebsd-current@freebsd.org Sat Aug 4 04:27:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E76CA105D79D for ; Sat, 4 Aug 2018 04:27:24 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BAC684466; Sat, 4 Aug 2018 04:27:24 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 3A6E814D34; Sat, 4 Aug 2018 04:27:24 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f173.google.com with SMTP id p10-v6so6520409ljg.2; Fri, 03 Aug 2018 21:27:24 -0700 (PDT) X-Gm-Message-State: AOUpUlGP0n6GtCsbsePVe+p1ZLvwCE+HkjzWTMkLWVTpEZlm2SOlpkTY kR/47Q3cTcQ29+2uCI2zm/1BclhHfyphR5SH7uA= X-Google-Smtp-Source: AAOMgpfLNxhzbNbATsCEWX1h+meKrvZKG+mM6AQfNbC47+xP7C8M8Iou/gJtF9htoHFOKHB3kQ9L0GmHjZRcWKPAEhg= X-Received: by 2002:a2e:1004:: with SMTP id j4-v6mr7453302lje.2.1533356842820; Fri, 03 Aug 2018 21:27:22 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Fri, 3 Aug 2018 21:27:02 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Fri, 3 Aug 2018 23:27:02 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 To: Eitan Adler Cc: Konstantin Belousov , freebsd-current Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 04:27:25 -0000 On Fri, Aug 3, 2018 at 10:10 PM, Eitan Adler wrote: > Hi all, > > After installing the latest current kernel I get the following panic: > > panic: mutex pmap not owned at ... efirt_machdep.c:255 > cpuid =3 > time = 1 > ... > mtx_assert() > efi_arch_enter() > efirt_modevents() > module_register_init() > mi_startup() > btext() > This seems odd- pmap lock is acquired at [1], then asserted shortly later at [2]... I avoid some of this stuff as well as I can, but is it actually possible for PCPU_GET(...) acquired curpmap to not match curthread->td_proc->p_vmspace->vm_pmap in this context? [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt.c?view=markup#l260 [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efirt_machdep.c?view=markup#l254 From owner-freebsd-current@freebsd.org Sat Aug 4 08:37:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E206D1062D59 for ; Sat, 4 Aug 2018 08:37:35 +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 5156E8BAA7; Sat, 4 Aug 2018 08:37:35 +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 w748bKbE070333 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Aug 2018 11:37:23 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w748bKbE070333 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w748bK40070332; Sat, 4 Aug 2018 11:37:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Aug 2018 11:37:20 +0300 From: Konstantin Belousov To: Kyle Evans Cc: freebsd-current Current Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 Message-ID: <20180804083720.GJ6049@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) 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.27 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, 04 Aug 2018 08:37:36 -0000 On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote: > On Fri, Aug 3, 2018 at 10:10 PM, Eitan Adler wrote: > > Hi all, > > > > After installing the latest current kernel I get the following panic: > > > > panic: mutex pmap not owned at ... efirt_machdep.c:255 > > cpuid =3 > > time = 1 > > ... > > mtx_assert() > > efi_arch_enter() > > efirt_modevents() > > module_register_init() > > mi_startup() > > btext() > > > > This seems odd- pmap lock is acquired at [1], then asserted shortly > later at [2]... I avoid some of this stuff as well as I can, but is it > actually possible for PCPU_GET(...) acquired curpmap to not match > curthread->td_proc->p_vmspace->vm_pmap in this context? > > [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt.c?view=markup#l260 > [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efirt_machdep.c?view=markup#l254 There could be that curpcpu not yet synced with proc0 pmap. It could be fixed. But it is not clear to me why efi_arch_enter() is called there. I see the check for GetTime belonging to the range described by a map descriptor. I do not see why do you need an enter into the EFI context for comparing integers. From owner-freebsd-current@freebsd.org Sat Aug 4 11:19:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD0AB1066B9A for ; Sat, 4 Aug 2018 11:19:06 +0000 (UTC) (envelope-from david@catwhisker.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 5DF8C705B9 for ; Sat, 4 Aug 2018 11:19:06 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 228CE1066B99; Sat, 4 Aug 2018 11:19:06 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1125D1066B98 for ; Sat, 4 Aug 2018 11:19:06 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.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 522F8705B8 for ; Sat, 4 Aug 2018 11:19:05 +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 w74BJ2g0007250 for ; Sat, 4 Aug 2018 11:19:02 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w74BJ2j7007249 for current@freebsd.org; Sat, 4 Aug 2018 04:19:02 -0700 (PDT) (envelope-from david) Date: Sat, 4 Aug 2018 04:19:02 -0700 From: David Wolfskill To: current@freebsd.org Subject: "Can't load kernel" after r337232 -> r337285 update (amd64) Message-ID: <20180804111902.GD1174@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BH+GvGmapu2BjrwQ" Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 11:19:07 -0000 --BH+GvGmapu2BjrwQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Yesterday, the daily build/smoike-test of head yielded: FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #68 r33723= 2M/337232:1200076: Fri Aug 3 03:52:52 PDT 2018 root@g1-215.catwhisker.= org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 (This is on my laptop; my build machine is busy doing the Saturday "catch-up" packages build in partial preparation for tomorrow.) This morning, after what seemed to be an "uneventful" build/install... well, I didn't even get a loader menu. (This was on the slice that uses the Forth loader. I haven't updated the slice that uses the Lua loader today.) Extracting the uname string from the installed kernel taht won't load, I see: FreeBSD 12.0-CURRENT #69 r337285M/337285:1200076: Sat Aug 4 03:55:21 PDT = 2018 root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM = 6.0.1) Links to various bits of possible interest are at -- in particular, the | amd64 |=20 | laptop head uname list dmesg build typescript -- updated daily=20 part -- though the links are for the last successfully-booted kernel, which would be yesterday's (r337232). I can boot from other slices OK -- as I type, I'm on the stable/11 slice: FreeBSD g1-215.catwhisker.org 11.2-STABLE FreeBSD 11.2-STABLE #699 r337280= M/337285:1102501: Sat Aug 4 03:38:52 PDT 2018 root@g1-215.catwhisker.o= rg:/common/S1/obj/usr/src/sys/CANARY amd64 so given a clue or two, I may be able to do some poking & report results. Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --BH+GvGmapu2BjrwQ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAltli6ZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hcZzggAuqetH7dVHyIyi+XLErkxv/5GMT0n5cEYNj78eaFyZTCZ2aCCqG9nJBF3 3e5ekv2EIJLw54y2FoT7y8WCxBidsEHHY+ot3wPD9BaHqIEmyezrxNhL5u6lQky1 CBHTgsjnH72TmU+hhCdunkQ6O3bXiHWWE6hPPmifho9mtCq6XAxdW32O2nWiUkEP J8GCMajnlumt1TKjQjzqcJBWnC6qZpzepxZKgH0SZmYKE1mfGkYdhGtTO4Gjc2CE iZKH05GU64UdWZ9pstzixGZ7nC0P4z5o26jpDmWZTsUeOjP0ErwBWPvP3BsN8yZn OSRmcvr7Jv3sdcEx25FgFqKRND+eig== =p1mu -----END PGP SIGNATURE----- --BH+GvGmapu2BjrwQ-- From owner-freebsd-current@freebsd.org Sat Aug 4 12:12:55 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BF751068AF1 for ; Sat, 4 Aug 2018 12:12:55 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC6627272A for ; Sat, 4 Aug 2018 12:12:54 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x433.google.com with SMTP id g6-v6so7886607wrp.0 for ; Sat, 04 Aug 2018 05:12:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HGpw8Uzep10h2Unw6uCxHBzD+Yfp14+jbcgoudC5ixA=; b=haqTBP0AGh662juDYMei60Ojv6x7Ya67nD7Y84NSNJqfst1AeSd/DEKdpHPZEZoqxX OA/gobDuJx/LMPM7sXrB2KqNG+WcGWe0lWDaXkXfLiHyMT/jIeyYBSySYSasqqp6+VpR T4p+nlwnbHrmRjUEkVc6Ak9HmrecChA/BkrbR0XT+KVka7oTFNptTA0x0kWeUvK+P0V8 UTDsnnV2SQIEHZG2tmLKhpB2LKSyKoCpH9QDhO2BYJgr1/26HypIcqYgAxMHInwhVlGs Fzej78XPUZImPI1RIxxoDkgNvv8XagMdEuxX6swgR0LujCC8SbN5oxYC7L/To7wuIsbO af3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HGpw8Uzep10h2Unw6uCxHBzD+Yfp14+jbcgoudC5ixA=; b=otv7D5nbN/x4BpWsZgddUcVb60+Zgsfj3NtFphiGOf0ZuCBAknaTFytRoqbvLj9pDF xf9c68bW5yknZvznWxnRbyt/tOFHZzJBO/fyzfV3yTS+cfRwvpKHcI+i4MFylUmrp6aA L5W7+htBKDU4iOjcJ/XMPKqX4GBvqp1pW5F+uOnnQXu7WjJTKyFStKvPJM2NJhyTsRm+ 2N+u/8d2jnFo6rnByecshSeJsVJxQoiGSqkWGdZeYd3mkyt3BHDivlL3+51IcdcFPby6 SockB22IsphaULd5tBWCcIdIZay2a6Qrup0LTkDk3UVQ720jvo5gt365zd5lbCHK+V5N yZnw== X-Gm-Message-State: AOUpUlFi7cczFndZV4buerorqIvgLmecIwE3s4xMAcXsZkgxIUO/r0oT KBE03umEnFD45i+pZnGtmh1jhc7G7RmDExnEqGA= X-Google-Smtp-Source: AAOMgpfWZ2Yt9xolPwEp7scWKuYFg6aV9wSQlI3Io93A2q9/eDN6I2IfdIEvZM5kXyIFtIcCBDXcp4Asv5mlZBAjGUE= X-Received: by 2002:a5d:40c4:: with SMTP id b4-v6mr4499010wrq.133.1533384773636; Sat, 04 Aug 2018 05:12:53 -0700 (PDT) MIME-Version: 1.0 References: <20180803204250.GE6049@kib.kiev.ua> In-Reply-To: <20180803204250.GE6049@kib.kiev.ua> From: Johannes Lundberg Date: Sat, 4 Aug 2018 13:12:17 +0100 Message-ID: Subject: Re: Linux process causes kernel panic To: Konstantin Belousov Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 12:12:55 -0000 On Fri, Aug 3, 2018 at 9:43 PM Konstantin Belousov wrote: > On Fri, Aug 03, 2018 at 09:26:08PM +0100, Johannes Lundberg wrote: > > Hi > > > > After install new kernel+world built from today's checkout I keep getting > > the same crash over and over. Never had this problem before. The previous > > kernel was from 3 weeks ago. > > > > Looks familiar to anyone? > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0xfffe665c > > fault code = supervisor write data, protection violation > > instruction pointer = 0x20:0xffffffff82282db3 > > stack pointer = 0x0:0xfffffe004c74c8c8 > > frame pointer = 0x0:0xfffffe004c74c980 > > 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 = 1579 (wcgrid_zika_vina_7.) > > trap number = 12 > > panic: page fault > > cpuid = 0 > > time = 1533327428 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > > 0xfffffe004c74c580 > > vpanic() at vpanic+0x1a3/frame 0xfffffe004c74c5e0 > > panic() at panic+0x43/frame 0xfffffe004c74c640 > > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe004c74c690 > > trap_pfault() at trap_pfault+0x62/frame 0xfffffe004c74c6e0 > > trap() at trap+0x2ba/frame 0xfffffe004c74c7f0 > > calltrap() at calltrap+0x8/frame 0xfffffe004c74c7f0 > > --- trap 0xc, rip = 0xffffffff82282db3, rsp = 0xfffffe004c74c8c8, rbp = > > 0xfffffe004c74c980 --- > > futex_xchgl() at futex_xchgl+0x23/frame 0xfffffe004c74c980 > > ia32_syscall() at ia32_syscall+0x29f/frame 0xfffffe004c74cab0 > > int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x4000001 > > Uptime: 7m29s > > Dumping 411 out of 8056 > MB:..4%..12%..24%..32%..43%..51%..63%..74%..82%..94% > > Dump complete > > Post first 40 lines from the verbose dmesg boot of your machine. > > I have a guess what is going on, I need the dmesg to confirm. > If my guess is correct, you can use a workaround by setting the > "hw.cpu_stdext_disable=0x00100000" tunable at the loader prompt for now. > No panic over night with that tunable so it seems you're on the right track. From owner-freebsd-current@freebsd.org Sat Aug 4 12:32:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7215710699ED for ; Sat, 4 Aug 2018 12:32:40 +0000 (UTC) (envelope-from tsoome@me.com) 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 0DCD97374F for ; Sat, 4 Aug 2018 12:32:40 +0000 (UTC) (envelope-from tsoome@me.com) Received: by mailman.ysv.freebsd.org (Postfix) id C6E1410699EC; Sat, 4 Aug 2018 12:32:39 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4DA310699EB for ; Sat, 4 Aug 2018 12:32:39 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr11p00im-asmtp002.me.com (mr11p00im-asmtp002.me.com [17.110.69.253]) (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 46CC57374E for ; Sat, 4 Aug 2018 12:32:39 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.mr11p00im-asmtp002.me.com by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PCX00G00PBIOV00@mr11p00im-asmtp002.me.com> for current@freebsd.org; Sat, 04 Aug 2018 11:32:10 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PCX0009RPDDRI10@mr11p00im-asmtp002.me.com> for current@freebsd.org; Sat, 04 Aug 2018 11:32:10 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-04_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808040129 From: Toomas Soome MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: "Can't load kernel" after r337232 -> r337285 update (amd64) Date: Sat, 04 Aug 2018 14:31:56 +0300 References: <20180804111902.GD1174@albert.catwhisker.org> To: current@freebsd.org In-reply-to: <20180804111902.GD1174@albert.catwhisker.org> Message-id: X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 12:32:40 -0000 > On 4 Aug 2018, at 14:19, David Wolfskill wrote: >=20 > Yesterday, the daily build/smoike-test of head yielded: >=20 > FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #68 = r337232M/337232:1200076: Fri Aug 3 03:52:52 PDT 2018 = root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY = amd64 >=20 > (This is on my laptop; my build machine is busy doing the Saturday > "catch-up" packages build in partial preparation for tomorrow.) >=20 > This morning, after what seemed to be an "uneventful" build/install... > well, I didn't even get a loader menu. (This was on the slice that > uses the Forth loader. I haven't updated the slice that uses the > Lua loader today.) >=20 > Extracting the uname string from the installed kernel taht won't > load, I see: >=20 > FreeBSD 12.0-CURRENT #69 r337285M/337285:1200076: Sat Aug 4 03:55:21 = PDT 2018 > = root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on = LLVM 6.0.1) >=20 > Links to various bits of possible interest are at > -- in particular, = the >=20 > | amd64 > |=20 > | laptop head uname list dmesg build typescript -- updated daily=20= >=20 > part -- though the links are for the last successfully-booted kernel, > which would be yesterday's (r337232). >=20 > I can boot from other slices OK -- as I type, I'm on the stable/11 = slice: > FreeBSD g1-215.catwhisker.org 11.2-STABLE FreeBSD 11.2-STABLE #699 = r337280M/337285:1102501: Sat Aug 4 03:38:52 PDT 2018 = root@g1-215.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 >=20 > so given a clue or two, I may be able to do some poking & report = results. >=20 > Peace, > david > --=20 > David H. Wolfskill david@catwhisker.org > Trump is gaslighting us: = https://www.bbc.com/news/world-us-canada-44959300 >=20 > See http://www.catwhisker.org/~david/publickey.gpg for my public key. It probably r337271, could you check https://reviews.freebsd.org/D16588? = =20 rgds, toomas From owner-freebsd-current@freebsd.org Sat Aug 4 12:37:57 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0F441069D12 for ; Sat, 4 Aug 2018 12:37:56 +0000 (UTC) (envelope-from david@catwhisker.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 923DE73BDF for ; Sat, 4 Aug 2018 12:37:56 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 573601069D0F; Sat, 4 Aug 2018 12:37:56 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 460801069D0E for ; Sat, 4 Aug 2018 12:37:56 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.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 A89F073BDC for ; Sat, 4 Aug 2018 12:37:55 +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 w74Cbr3B011388; Sat, 4 Aug 2018 12:37:53 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w74CbrFG011387; Sat, 4 Aug 2018 05:37:53 -0700 (PDT) (envelope-from david) Date: Sat, 4 Aug 2018 05:37:53 -0700 From: David Wolfskill To: Toomas Soome Cc: current@freebsd.org Subject: Re: "Can't load kernel" after r337232 -> r337285 update (amd64) Message-ID: <20180804123753.GO1174@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Toomas Soome , current@freebsd.org References: <20180804111902.GD1174@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="piJIew5TPuzXDO6S" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 12:37:57 -0000 --piJIew5TPuzXDO6S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 04, 2018 at 02:31:56PM +0300, Toomas Soome wrote: > ...=20 >=20 > It probably r337271, could you check https://reviews.freebsd.org/D16588? = =20 >=20 > rgds, > toomas > .... Thanks; I'll give that a try & report back. Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --piJIew5TPuzXDO6S Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAltlniFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hc1bAf/fjHfyvig7halWHD1QpCYzRdgW3fYT7qMAztpWskdC0+TOprtnlkgLewt nwob0atLO0gUjRSs7T5uajO2Jd9fWVSlJNKNCD42wj6Nm1KPXB14CIpaP4HQW9Yg OPJP0MqBUIo9ZYsCHTjVZNVgBlTZnd6msUzksxMBEXJGcDp4Q5UG2d3TB6SgKuXC AoluNQC20QvAI2uYTr5edFQ129HcFEV8bu54b4w3aKKkcZPtoDdrfaQ1Ufn54k/m UKv/9q1OjOeLJ5rLIzKNS1Yhlf4DYIguGTjIasNHnxrwA2gBnp645wMgeDaLHw1b /wwZ963DFM1ateoJCWDtmi5bUOmLAQ== =aqNX -----END PGP SIGNATURE----- --piJIew5TPuzXDO6S-- From owner-freebsd-current@freebsd.org Sat Aug 4 13:05:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73CC9106AA00 for ; Sat, 4 Aug 2018 13:05:47 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 233BF75535 for ; Sat, 4 Aug 2018 13:05:47 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id B6419181CE for ; Sat, 4 Aug 2018 13:05:46 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f52.google.com with SMTP id u202-v6so5979121lff.9 for ; Sat, 04 Aug 2018 06:05:46 -0700 (PDT) X-Gm-Message-State: AOUpUlGBygNvuhWqoqFnWnMyOYM2ddpdcbdtCYV5nRqva6F8og3RCXI1 iwoga+OIhkIZZuZkkkb2WHC9iSEq6dd9tmpRKt0= X-Google-Smtp-Source: AAOMgpeT+tWvtCMroH+ClCP76bnzH0WrkQnKJq+ZH7PFf3OiBn3JV+aNjNztUHdbeFIWRb6FsK2kwfFPUNDmuRhGdUc= X-Received: by 2002:a19:138b:: with SMTP id 11-v6mr7393174lft.74.1533387945191; Sat, 04 Aug 2018 06:05:45 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Sat, 4 Aug 2018 06:05:24 -0700 (PDT) In-Reply-To: <20180804083720.GJ6049@kib.kiev.ua> References: <20180804083720.GJ6049@kib.kiev.ua> From: Kyle Evans Date: Sat, 4 Aug 2018 08:05:24 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 To: Konstantin Belousov Cc: freebsd-current Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 13:05:47 -0000 On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov wrote: > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote: >> >> This seems odd- pmap lock is acquired at [1], then asserted shortly >> later at [2]... I avoid some of this stuff as well as I can, but is it >> actually possible for PCPU_GET(...) acquired curpmap to not match >> curthread->td_proc->p_vmspace->vm_pmap in this context? >> >> [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt.c?view=markup#l260 >> [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efirt_machdep.c?view=markup#l254 > There could be that curpcpu not yet synced with proc0 pmap. It could be > fixed. > > But it is not clear to me why efi_arch_enter() is called there. I see > the check for GetTime belonging to the range described by a map descriptor. > I do not see why do you need an enter into the EFI context for comparing > integers. This probably could have been documented better, but efi_runtime pointer may (always?) point into runtime service memory that isn't valid/available at that point, so we get a fault and panic when dereferencing it to grab rt_gettime address. We ran into this wall when adding the check originally. From owner-freebsd-current@freebsd.org Sat Aug 4 13:14:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79E7A106AE10 for ; Sat, 4 Aug 2018 13:14: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 EA39D75B60; Sat, 4 Aug 2018 13:14: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 w74DDqlQ033367 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Aug 2018 16:13:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w74DDqlQ033367 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w74DDq4m033366; Sat, 4 Aug 2018 16:13:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Aug 2018 16:13:52 +0300 From: Konstantin Belousov To: Kyle Evans Cc: freebsd-current Current Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 Message-ID: <20180804131352.GL6049@kib.kiev.ua> References: <20180804083720.GJ6049@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) 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.27 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, 04 Aug 2018 13:14:03 -0000 On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote: > On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov wrote: > > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote: > >> > >> This seems odd- pmap lock is acquired at [1], then asserted shortly > >> later at [2]... I avoid some of this stuff as well as I can, but is it > >> actually possible for PCPU_GET(...) acquired curpmap to not match > >> curthread->td_proc->p_vmspace->vm_pmap in this context? > >> > >> [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt.c?view=markup#l260 > >> [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efirt_machdep.c?view=markup#l254 > > There could be that curpcpu not yet synced with proc0 pmap. It could be > > fixed. > > > > But it is not clear to me why efi_arch_enter() is called there. I see > > the check for GetTime belonging to the range described by a map descriptor. > > I do not see why do you need an enter into the EFI context for comparing > > integers. > > This probably could have been documented better, but efi_runtime > pointer may (always?) point into runtime service memory that isn't > valid/available at that point, so we get a fault and panic when > dereferencing it to grab rt_gettime address. We ran into this wall > when adding the check originally. Wouldn't it be enough to access it by translating physical address into DMAP ? From owner-freebsd-current@freebsd.org Sat Aug 4 13:29:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A98B5106B5CF for ; Sat, 4 Aug 2018 13:29:36 +0000 (UTC) (envelope-from david@catwhisker.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 460A576E37 for ; Sat, 4 Aug 2018 13:29:36 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 07C4B106B5CE; Sat, 4 Aug 2018 13:29:36 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA987106B5CD for ; Sat, 4 Aug 2018 13:29:35 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.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 4D50076E36 for ; Sat, 4 Aug 2018 13:29: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 w74DTXU0012391; Sat, 4 Aug 2018 13:29:33 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w74DTXOR012390; Sat, 4 Aug 2018 06:29:33 -0700 (PDT) (envelope-from david) Date: Sat, 4 Aug 2018 06:29:33 -0700 From: David Wolfskill To: Toomas Soome Cc: current@freebsd.org Subject: Re: "Can't load kernel" after r337232 -> r337285 update (amd64) Message-ID: <20180804132933.GQ1174@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Toomas Soome , current@freebsd.org References: <20180804111902.GD1174@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="F7k3T93ZFCHaQmPK" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 13:29:36 -0000 --F7k3T93ZFCHaQmPK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 04, 2018 at 02:31:56PM +0300, Toomas Soome wrote: > ...=20 > It probably r337271, could you check https://reviews.freebsd.org/D16588? = =20 >=20 > rgds, > toomas > .... Success: FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #69 r33728= 5M/337285:1200076: Sat Aug 4 03:55:21 PDT 2018 root@g1-215.catwhisker.= org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 Thank you! I have updated the review to mention this, as well. Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --F7k3T93ZFCHaQmPK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAltlqj1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hc7zQf+KOavq1t90Lyh13z2WTKERx3iFHS4bPHR/MrHu8FZpIpeQ+WTx87CijDt EHYzj5NaGGedKr5eEB5/NpBu1JfZkKuSh3jxWIG5Mk+xskVOR8RI9ym1+mePdZOy n0T6UxBolehCoAepHfSdLb4CGDkTuE3DtX5Dp8r/JAjIdSYdQfowBvGl34IxQK0e Q7n1BAY4WGZcckpA6XRUwRB8bPHpY0IFf6dKq0aSRCc5yjEWCG8OnJOg7/5N4m8c niudM14OzsxTaSm8UfvDOll/XIktvJ0QjJ5iP6IEoj0bpJHY/V8s4x6OXyWn33l5 rj6DkQ/Zl6wylRYqCRJP6zQNhVtSRA== =xuib -----END PGP SIGNATURE----- --F7k3T93ZFCHaQmPK-- From owner-freebsd-current@freebsd.org Sat Aug 4 13:57:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E34D106C26A for ; Sat, 4 Aug 2018 13:57:21 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 10F8778161; Sat, 4 Aug 2018 13:57:21 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id A2DE6186EA; Sat, 4 Aug 2018 13:57:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f49.google.com with SMTP id u202-v6so6035137lff.9; Sat, 04 Aug 2018 06:57:20 -0700 (PDT) X-Gm-Message-State: AOUpUlENxlRgYV/a0wMU4mOMC/hgYG/C6EaU3hL7voSQhE6indwng0dn nO3IRZwY7jHMavxqvYqGeScRq3yaEBWbTNmQ/O8= X-Google-Smtp-Source: AAOMgpd8zji5Okmh9PcfRU8Dvx5yZZwriJJ47LoNZrXswruXqqMaT24Uu1LR8FNPcdfkQfGA5VBTHRRvlq0jYyhmx20= X-Received: by 2002:a19:9481:: with SMTP id o1-v6mr7559745lfk.38.1533391039254; Sat, 04 Aug 2018 06:57:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Sat, 4 Aug 2018 06:56:58 -0700 (PDT) In-Reply-To: <20180804131352.GL6049@kib.kiev.ua> References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> From: Kyle Evans Date: Sat, 4 Aug 2018 08:56:58 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 To: Konstantin Belousov Cc: freebsd-current Current , Eitan Adler Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 13:57:21 -0000 On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov wrote: > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote: >> On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov wrote: >> > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote: >> >> >> >> This seems odd- pmap lock is acquired at [1], then asserted shortly >> >> later at [2]... I avoid some of this stuff as well as I can, but is it >> >> actually possible for PCPU_GET(...) acquired curpmap to not match >> >> curthread->td_proc->p_vmspace->vm_pmap in this context? >> >> >> >> [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt.c?view=markup#l260 >> >> [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efirt_machdep.c?view=markup#l254 >> > There could be that curpcpu not yet synced with proc0 pmap. It could be >> > fixed. >> > >> > But it is not clear to me why efi_arch_enter() is called there. I see >> > the check for GetTime belonging to the range described by a map descriptor. >> > I do not see why do you need an enter into the EFI context for comparing >> > integers. >> >> This probably could have been documented better, but efi_runtime >> pointer may (always?) point into runtime service memory that isn't >> valid/available at that point, so we get a fault and panic when >> dereferencing it to grab rt_gettime address. We ran into this wall >> when adding the check originally. > Wouldn't it be enough to access it by translating physical address into > DMAP ? Ah, sure, sure. [1] is proper form, yeah? [1] https://people.freebsd.org/~kevans/efi-dmap.diff From owner-freebsd-current@freebsd.org Sat Aug 4 14:22:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DC3B106CE0D for ; Sat, 4 Aug 2018 14:22:47 +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 B61DC79935 for ; Sat, 4 Aug 2018 14:22:46 +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 w74EMZxb049291 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Aug 2018 17:22:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w74EMZxb049291 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w74EMZPk049290; Sat, 4 Aug 2018 17:22:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Aug 2018 17:22:35 +0300 From: Konstantin Belousov To: Johannes Lundberg Cc: freebsd-current Subject: Re: Linux process causes kernel panic Message-ID: <20180804142235.GM6049@kib.kiev.ua> References: <20180803204250.GE6049@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) 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.27 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, 04 Aug 2018 14:22:47 -0000 On Sat, Aug 04, 2018 at 01:12:17PM +0100, Johannes Lundberg wrote: > No panic over night with that tunable so it seems you're on the right > track. Please try this, on top of r337316. diff --git a/sys/amd64/linux/linux_machdep.c b/sys/amd64/linux/linux_machdep.c index 6c5b014853f..434ea0eac07 100644 --- a/sys/amd64/linux/linux_machdep.c +++ b/sys/amd64/linux/linux_machdep.c @@ -78,6 +78,9 @@ __FBSDID("$FreeBSD$"); #include #include +#include +#include + #include #include #include @@ -88,8 +91,6 @@ __FBSDID("$FreeBSD$"); #include #include -#include - int linux_execve(struct thread *td, struct linux_execve_args *args) { @@ -276,3 +277,48 @@ linux_set_cloned_tls(struct thread *td, void *desc) return (0); } + +int futex_xchgl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_xchgl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_xchgl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_xchgl_smap : futex_xchgl_nosmap); +} + +int futex_addl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_addl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_addl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_addl_smap : futex_addl_nosmap); +} + +int futex_orl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_orl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_orl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_orl_smap : futex_orl_nosmap); +} + +int futex_andl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_andl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_andl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_andl_smap : futex_andl_nosmap); +} + +int futex_xorl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_xorl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_xorl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_xorl_smap : futex_xorl_nosmap); +} diff --git a/sys/amd64/linux/linux_support.s b/sys/amd64/linux/linux_support.s index a9f02160be2..391f76414f2 100644 --- a/sys/amd64/linux/linux_support.s +++ b/sys/amd64/linux/linux_support.s @@ -38,7 +38,7 @@ futex_fault: movl $-EFAULT,%eax ret -ENTRY(futex_xchgl) +ENTRY(futex_xchgl_nosmap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax @@ -49,25 +49,58 @@ ENTRY(futex_xchgl) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_xchgl) +END(futex_xchgl_nosmap) -ENTRY(futex_addl) +ENTRY(futex_xchgl_smap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax cmpq %rax,%rsi ja futex_fault + stac + xchgl %edi,(%rsi) + clac + movl %edi,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_xchgl_smap) + +ENTRY(futex_addl_nosmap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault +#ifdef SMP + lock +#endif + xaddl %edi,(%rsi) + movl %edi,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_addl_nosmap) + +ENTRY(futex_addl_smap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault + stac #ifdef SMP lock #endif xaddl %edi,(%rsi) + clac movl %edi,(%rdx) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_addl) +END(futex_addl_smap) -ENTRY(futex_orl) +ENTRY(futex_orl_nosmap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax @@ -85,9 +118,31 @@ ENTRY(futex_orl) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_orl) +END(futex_orl_nosmap) -ENTRY(futex_andl) +ENTRY(futex_orl_smap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault + movl (%rsi),%eax +1: movl %eax,%ecx + orl %edi,%ecx + stac +#ifdef SMP + lock +#endif + cmpxchgl %ecx,(%rsi) + clac + jnz 1b + movl %eax,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_orl_smap) + +ENTRY(futex_andl_nosmap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax @@ -105,9 +160,51 @@ ENTRY(futex_andl) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_andl) +END(futex_andl_nosmap) + +ENTRY(futex_andl_smap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault + movl (%rsi),%eax +1: movl %eax,%ecx + andl %edi,%ecx + stac +#ifdef SMP + lock +#endif + cmpxchgl %ecx,(%rsi) + clac + jnz 1b + movl %eax,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_andl_smap) + +ENTRY(futex_xorl_nosmap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault + movl (%rsi),%eax +1: movl %eax,%ecx + xorl %edi,%ecx +#ifdef SMP + lock +#endif + cmpxchgl %ecx,(%rsi) + jnz 1b + movl %eax,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_xorl_nosmap) -ENTRY(futex_xorl) +ENTRY(futex_xorl_smap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax @@ -116,13 +213,15 @@ ENTRY(futex_xorl) movl (%rsi),%eax 1: movl %eax,%ecx xorl %edi,%ecx + stac #ifdef SMP lock #endif cmpxchgl %ecx,(%rsi) + clac jnz 1b movl %eax,(%rdx) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_xorl) +END(futex_xorl_smap) diff --git a/sys/amd64/linux32/linux32_machdep.c b/sys/amd64/linux32/linux32_machdep.c index ce06be57e9f..61ecc87dc77 100644 --- a/sys/amd64/linux32/linux32_machdep.c +++ b/sys/amd64/linux32/linux32_machdep.c @@ -58,10 +58,12 @@ __FBSDID("$FreeBSD$"); #include #include +#include #include #include #include #include +#include #include #include @@ -822,3 +824,48 @@ linux_set_thread_area(struct thread *td, return (0); } + +int futex_xchgl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_xchgl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_xchgl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_xchgl_smap : futex_xchgl_nosmap); +} + +int futex_addl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_addl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_addl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_addl_smap : futex_addl_nosmap); +} + +int futex_orl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_orl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_orl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_orl_smap : futex_orl_nosmap); +} + +int futex_andl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_andl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_andl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_andl_smap : futex_andl_nosmap); +} + +int futex_xorl_nosmap(int oparg, uint32_t *uaddr, int *oldval); +int futex_xorl_smap(int oparg, uint32_t *uaddr, int *oldval); +DEFINE_IFUNC(, int, futex_xorl, (int, uint32_t *, int *), static) +{ + + return ((cpu_stdext_feature & CPUID_STDEXT_SMAP) != 0 ? + futex_xorl_smap : futex_xorl_nosmap); +} diff --git a/sys/amd64/linux32/linux32_support.s b/sys/amd64/linux32/linux32_support.s index bba0d8d5e71..981bba9f582 100644 --- a/sys/amd64/linux32/linux32_support.s +++ b/sys/amd64/linux32/linux32_support.s @@ -38,7 +38,7 @@ futex_fault: movl $-EFAULT,%eax ret -ENTRY(futex_xchgl) +ENTRY(futex_xchgl_nosmap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax @@ -49,25 +49,58 @@ ENTRY(futex_xchgl) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_xchgl) +END(futex_xchgl_nosmap) -ENTRY(futex_addl) +ENTRY(futex_xchgl_smap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax cmpq %rax,%rsi ja futex_fault + stac + xchgl %edi,(%rsi) + clac + movl %edi,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_xchgl_smap) + +ENTRY(futex_addl_nosmap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault +#ifdef SMP + lock +#endif + xaddl %edi,(%rsi) + movl %edi,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_addl_nosmap) + +ENTRY(futex_addl_smap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault + stac #ifdef SMP lock #endif xaddl %edi,(%rsi) + clac movl %edi,(%rdx) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_addl) +END(futex_addl_smap) -ENTRY(futex_orl) +ENTRY(futex_orl_nosmap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax @@ -85,9 +118,31 @@ ENTRY(futex_orl) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_orl) +END(futex_orl_nosmap) -ENTRY(futex_andl) +ENTRY(futex_orl_smap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault + movl (%rsi),%eax +1: movl %eax,%ecx + orl %edi,%ecx + stac +#ifdef SMP + lock +#endif + cmpxchgl %ecx,(%rsi) + clac + jnz 1b + movl %eax,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_orl_smap) + +ENTRY(futex_andl_nosmap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax @@ -105,9 +160,51 @@ ENTRY(futex_andl) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_andl) +END(futex_andl_nosmap) + +ENTRY(futex_andl_smap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault + movl (%rsi),%eax +1: movl %eax,%ecx + andl %edi,%ecx + stac +#ifdef SMP + lock +#endif + cmpxchgl %ecx,(%rsi) + clac + jnz 1b + movl %eax,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_andl_smap) + +ENTRY(futex_xorl_nosmap) + movq PCPU(CURPCB),%r8 + movq $futex_fault,PCB_ONFAULT(%r8) + movq $VM_MAXUSER_ADDRESS-4,%rax + cmpq %rax,%rsi + ja futex_fault + movl (%rsi),%eax +1: movl %eax,%ecx + xorl %edi,%ecx +#ifdef SMP + lock +#endif + cmpxchgl %ecx,(%rsi) + jnz 1b + movl %eax,(%rdx) + xorl %eax,%eax + movq %rax,PCB_ONFAULT(%r8) + ret +END(futex_xorl_nosmap) -ENTRY(futex_xorl) +ENTRY(futex_xorl_smap) movq PCPU(CURPCB),%r8 movq $futex_fault,PCB_ONFAULT(%r8) movq $VM_MAXUSER_ADDRESS-4,%rax @@ -116,13 +213,15 @@ ENTRY(futex_xorl) movl (%rsi),%eax 1: movl %eax,%ecx xorl %edi,%ecx + stac #ifdef SMP lock #endif cmpxchgl %ecx,(%rsi) + clac jnz 1b movl %eax,(%rdx) xorl %eax,%eax movq %rax,PCB_ONFAULT(%r8) ret -END(futex_xorl) +END(futex_xorl_smap) From owner-freebsd-current@freebsd.org Sat Aug 4 14:27:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C81F1106CFDA for ; Sat, 4 Aug 2018 14:27:52 +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 5322B79CF4; Sat, 4 Aug 2018 14:27:52 +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 w74ERfq8050411 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Aug 2018 17:27:44 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w74ERfq8050411 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w74ERf6J050410; Sat, 4 Aug 2018 17:27:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Aug 2018 17:27:41 +0300 From: Konstantin Belousov To: Kyle Evans Cc: freebsd-current Current , Eitan Adler Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 Message-ID: <20180804142741.GN6049@kib.kiev.ua> References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) 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.27 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, 04 Aug 2018 14:27:53 -0000 On Sat, Aug 04, 2018 at 08:56:58AM -0500, Kyle Evans wrote: > On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov wrote: > > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote: > >> On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov wrote: > >> > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote: > >> >> > >> >> This seems odd- pmap lock is acquired at [1], then asserted shortly > >> >> later at [2]... I avoid some of this stuff as well as I can, but is it > >> >> actually possible for PCPU_GET(...) acquired curpmap to not match > >> >> curthread->td_proc->p_vmspace->vm_pmap in this context? > >> >> > >> >> [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt.c?view=markup#l260 > >> >> [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efirt_machdep.c?view=markup#l254 > >> > There could be that curpcpu not yet synced with proc0 pmap. It could be > >> > fixed. > >> > > >> > But it is not clear to me why efi_arch_enter() is called there. I see > >> > the check for GetTime belonging to the range described by a map descriptor. > >> > I do not see why do you need an enter into the EFI context for comparing > >> > integers. > >> > >> This probably could have been documented better, but efi_runtime > >> pointer may (always?) point into runtime service memory that isn't > >> valid/available at that point, so we get a fault and panic when > >> dereferencing it to grab rt_gettime address. We ran into this wall > >> when adding the check originally. > > Wouldn't it be enough to access it by translating physical address into > > DMAP ? > > Ah, sure, sure. [1] is proper form, yeah? > > [1] https://people.freebsd.org/~kevans/efi-dmap.diff I would brace it with #ifdef PHYS_TO_DMAP, #error otherwise. Also, it might make sense to check against dmaplimit as well (on arm64 it is called PHYS_IN_DMAP(), sight). So it might make sense to define MD function in arch/efirt_machdep.c to translate table' address into the KVA. From owner-freebsd-current@freebsd.org Sat Aug 4 14:51:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 730DC106DA54 for ; Sat, 4 Aug 2018 14:51:26 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EEA1A7AB3A for ; Sat, 4 Aug 2018 14:51:25 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: da427f57-97f5-11e8-904b-1d2e466b3c59 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id da427f57-97f5-11e8-904b-1d2e466b3c59; Sat, 04 Aug 2018 14:51:22 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w74EpLuc046084; Sat, 4 Aug 2018 08:51:21 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533394281.9860.5.camel@freebsd.org> Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 From: Ian Lepore To: Kyle Evans , Konstantin Belousov Cc: freebsd-current Current , Eitan Adler Date: Sat, 04 Aug 2018 08:51:21 -0600 In-Reply-To: References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 14:51:26 -0000 On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote: > On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov com> wrote: > > > > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote: > > > > > > On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov > > ail.com> wrote: > > > > > > > > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote: > > > > > > > > > > > > > > > This seems odd- pmap lock is acquired at [1], then asserted > > > > > shortly > > > > > later at [2]... I avoid some of this stuff as well as I can, > > > > > but is it > > > > > actually possible for PCPU_GET(...) acquired curpmap to not > > > > > match > > > > > curthread->td_proc->p_vmspace->vm_pmap in this context? > > > > > > > > > > [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt > > > > > .c?view=markup#l260 > > > > > [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efir > > > > > t_machdep.c?view=markup#l254 > > > > There could be that curpcpu not yet synced with proc0 pmap.  It > > > > could be > > > > fixed. > > > > > > > > But it is not clear to me why efi_arch_enter() is called > > > > there.  I see > > > > the check for GetTime belonging to the range described by a map > > > > descriptor. > > > > I do not see why do you need an enter into the EFI context for > > > > comparing > > > > integers. > > > This probably could have been documented better, but efi_runtime > > > pointer may (always?) point into runtime service memory that > > > isn't > > > valid/available at that point, so we get a fault and panic when > > > dereferencing it to grab rt_gettime address. We ran into this > > > wall > > > when adding the check originally. > > Wouldn't it be enough to access it by translating physical address > > into > > DMAP ? > Ah, sure, sure. [1] is proper form, yeah? > > [1] https://people.freebsd.org/~kevans/efi-dmap.diff What do we do on 32-bit arm that has no dmap but may have efi runtime support? -- Ian From owner-freebsd-current@freebsd.org Sat Aug 4 14:59:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9B28106DE6F for ; Sat, 4 Aug 2018 14:59:05 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 64A517B0C2; Sat, 4 Aug 2018 14:59:05 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id F3D2418CEC; Sat, 4 Aug 2018 14:59:04 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f49.google.com with SMTP id l16-v6so6085828lfc.13; Sat, 04 Aug 2018 07:59:04 -0700 (PDT) X-Gm-Message-State: AOUpUlHZR/vn8LUxKqe9k5Xr+cZ4q4d9TZ4Hupawf2ygP7j7n3zK6u7w mUM2DV5NKVsTLxCxVwrw2d5yJ+86bLY4dA3Ro74= X-Google-Smtp-Source: AAOMgpeTUtwrsHk0gvdDDs+LJvbCqdP94sqi7ZZzKQ7zlN3U6PhffES9+2+TG8AtZtcbidwmWHTlcV5+7imIO1suwkA= X-Received: by 2002:a19:1586:: with SMTP id 6-v6mr6958738lfv.51.1533394743569; Sat, 04 Aug 2018 07:59:03 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Sat, 4 Aug 2018 07:58:43 -0700 (PDT) In-Reply-To: <1533394281.9860.5.camel@freebsd.org> References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> <1533394281.9860.5.camel@freebsd.org> From: Kyle Evans Date: Sat, 4 Aug 2018 09:58:43 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 To: Ian Lepore Cc: Konstantin Belousov , freebsd-current Current , Eitan Adler Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 14:59:06 -0000 On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote: > On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote: >> On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov > com> wrote: >> > >> > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote: >> > > >> > > On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov > > > ail.com> wrote: >> > > > >> > > > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote: >> > > > > >> > > > > >> > > > > This seems odd- pmap lock is acquired at [1], then asserted >> > > > > shortly >> > > > > later at [2]... I avoid some of this stuff as well as I can, >> > > > > but is it >> > > > > actually possible for PCPU_GET(...) acquired curpmap to not >> > > > > match >> > > > > curthread->td_proc->p_vmspace->vm_pmap in this context? >> > > > > >> > > > > [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt >> > > > > .c?view=markup#l260 >> > > > > [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efir >> > > > > t_machdep.c?view=markup#l254 >> > > > There could be that curpcpu not yet synced with proc0 pmap. It >> > > > could be >> > > > fixed. >> > > > >> > > > But it is not clear to me why efi_arch_enter() is called >> > > > there. I see >> > > > the check for GetTime belonging to the range described by a map >> > > > descriptor. >> > > > I do not see why do you need an enter into the EFI context for >> > > > comparing >> > > > integers. >> > > This probably could have been documented better, but efi_runtime >> > > pointer may (always?) point into runtime service memory that >> > > isn't >> > > valid/available at that point, so we get a fault and panic when >> > > dereferencing it to grab rt_gettime address. We ran into this >> > > wall >> > > when adding the check originally. >> > Wouldn't it be enough to access it by translating physical address >> > into >> > DMAP ? >> Ah, sure, sure. [1] is proper form, yeah? >> >> [1] https://people.freebsd.org/~kevans/efi-dmap.diff > > What do we do on 32-bit arm that has no dmap but may have efi runtime > support? > This should probably just be compiled out for !arm64 && !x86 - its sole purpose was to compensate for outdated loader.efi that hasn't done the SetVirtualAddressMap. EFI on 32-bit ARM is "new" enough that it shouldn't have this problem. From owner-freebsd-current@freebsd.org Sat Aug 4 15:22:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B33D3106E934 for ; Sat, 4 Aug 2018 15:22:36 +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 3D5557C37E; Sat, 4 Aug 2018 15:22:36 +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 w74FMPmA062847 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Aug 2018 18:22:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w74FMPmA062847 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w74FMPau062846; Sat, 4 Aug 2018 18:22:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Aug 2018 18:22:25 +0300 From: Konstantin Belousov To: Kyle Evans Cc: Ian Lepore , freebsd-current Current , Eitan Adler Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 Message-ID: <20180804152225.GP6049@kib.kiev.ua> References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> <1533394281.9860.5.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) 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.27 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, 04 Aug 2018 15:22:36 -0000 On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote: > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote: > > On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote: > >> On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov >> com> wrote: > >> > > >> > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote: > >> > > > >> > > On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov >> > > ail.com> wrote: > >> > > > > >> > > > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote: > >> > > > > > >> > > > > > >> > > > > This seems odd- pmap lock is acquired at [1], then asserted > >> > > > > shortly > >> > > > > later at [2]... I avoid some of this stuff as well as I can, > >> > > > > but is it > >> > > > > actually possible for PCPU_GET(...) acquired curpmap to not > >> > > > > match > >> > > > > curthread->td_proc->p_vmspace->vm_pmap in this context? > >> > > > > > >> > > > > [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt > >> > > > > .c?view=markup#l260 > >> > > > > [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efir > >> > > > > t_machdep.c?view=markup#l254 > >> > > > There could be that curpcpu not yet synced with proc0 pmap. It > >> > > > could be > >> > > > fixed. > >> > > > > >> > > > But it is not clear to me why efi_arch_enter() is called > >> > > > there. I see > >> > > > the check for GetTime belonging to the range described by a map > >> > > > descriptor. > >> > > > I do not see why do you need an enter into the EFI context for > >> > > > comparing > >> > > > integers. > >> > > This probably could have been documented better, but efi_runtime > >> > > pointer may (always?) point into runtime service memory that > >> > > isn't > >> > > valid/available at that point, so we get a fault and panic when > >> > > dereferencing it to grab rt_gettime address. We ran into this > >> > > wall > >> > > when adding the check originally. > >> > Wouldn't it be enough to access it by translating physical address > >> > into > >> > DMAP ? > >> Ah, sure, sure. [1] is proper form, yeah? > >> > >> [1] https://people.freebsd.org/~kevans/efi-dmap.diff > > > > What do we do on 32-bit arm that has no dmap but may have efi runtime > > support? > > > > This should probably just be compiled out for !arm64 && !x86 - its > sole purpose was to compensate for outdated loader.efi that hasn't > done the SetVirtualAddressMap. EFI on 32-bit ARM is "new" enough that > it shouldn't have this problem. Does EFI on 32bit arm have RT support ? From owner-freebsd-current@freebsd.org Sat Aug 4 15:25:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8A46106EA16 for ; Sat, 4 Aug 2018 15:25:50 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CEF77C4D0 for ; Sat, 4 Aug 2018 15:25:50 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: a952add9-97fa-11e8-904b-1d2e466b3c59 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id a952add9-97fa-11e8-904b-1d2e466b3c59; Sat, 04 Aug 2018 15:25:48 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w74FPlZN046159; Sat, 4 Aug 2018 09:25:47 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533396347.9860.11.camel@freebsd.org> Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 From: Ian Lepore To: Konstantin Belousov , Kyle Evans Cc: freebsd-current Current , Eitan Adler Date: Sat, 04 Aug 2018 09:25:47 -0600 In-Reply-To: <20180804152225.GP6049@kib.kiev.ua> References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> <1533394281.9860.5.camel@freebsd.org> <20180804152225.GP6049@kib.kiev.ua> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 15:25:51 -0000 On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote: > On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote: > > > > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote: > > > > > > On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote: > > > > > > > > On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov > > > gmail. > > > > com> wrote: > > > > > > > > > > > > > > > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote: > > > > > > > > > > > > > > > > > > On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov > > > > > bel@gm > > > > > > ail.com> wrote: > > > > > > > > > > > > > > > > > > > > > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This seems odd- pmap lock is acquired at [1], then > > > > > > > > asserted > > > > > > > > shortly > > > > > > > > later at [2]... I avoid some of this stuff as well as I > > > > > > > > can, > > > > > > > > but is it > > > > > > > > actually possible for PCPU_GET(...) acquired curpmap to > > > > > > > > not > > > > > > > > match > > > > > > > > curthread->td_proc->p_vmspace->vm_pmap in this context? > > > > > > > > > > > > > > > > [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev > > > > > > > > /efirt > > > > > > > > .c?view=markup#l260 > > > > > > > > [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd6 > > > > > > > > 4/efir > > > > > > > > t_machdep.c?view=markup#l254 > > > > > > > There could be that curpcpu not yet synced with proc0 > > > > > > > pmap.  It > > > > > > > could be > > > > > > > fixed. > > > > > > > > > > > > > > But it is not clear to me why efi_arch_enter() is called > > > > > > > there.  I see > > > > > > > the check for GetTime belonging to the range described by > > > > > > > a map > > > > > > > descriptor. > > > > > > > I do not see why do you need an enter into the EFI > > > > > > > context for > > > > > > > comparing > > > > > > > integers. > > > > > > This probably could have been documented better, but > > > > > > efi_runtime > > > > > > pointer may (always?) point into runtime service memory > > > > > > that > > > > > > isn't > > > > > > valid/available at that point, so we get a fault and panic > > > > > > when > > > > > > dereferencing it to grab rt_gettime address. We ran into > > > > > > this > > > > > > wall > > > > > > when adding the check originally. > > > > > Wouldn't it be enough to access it by translating physical > > > > > address > > > > > into > > > > > DMAP ? > > > > Ah, sure, sure. [1] is proper form, yeah? > > > > > > > > [1] https://people.freebsd.org/~kevans/efi-dmap.diff > > > What do we do on 32-bit arm that has no dmap but may have efi > > > runtime > > > support? > > > > > This should probably just be compiled out for !arm64 && !x86 - its > > sole purpose was to compensate for outdated loader.efi that hasn't > > done the SetVirtualAddressMap. EFI on 32-bit ARM is "new" enough > > that > > it shouldn't have this problem. > Does EFI on 32bit arm have RT support ? I suspect the uboot implementation doesn't, but I can't think of any reason why other implementations are not possible/available. In particular, even 32bit arm supports virtualization and such an environment could provide rt support. -- Ian From owner-freebsd-current@freebsd.org Sat Aug 4 15:43:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84C6A106F0AB for ; Sat, 4 Aug 2018 15:43:39 +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 0E88B7CFFF; Sat, 4 Aug 2018 15:43:38 +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 w74FhSVJ067398 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Aug 2018 18:43:31 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w74FhSVJ067398 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w74FhSHE067397; Sat, 4 Aug 2018 18:43:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Aug 2018 18:43:27 +0300 From: Konstantin Belousov To: Ian Lepore Cc: Kyle Evans , freebsd-current Current , Eitan Adler Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 Message-ID: <20180804154327.GQ6049@kib.kiev.ua> References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> <1533394281.9860.5.camel@freebsd.org> <20180804152225.GP6049@kib.kiev.ua> <1533396347.9860.11.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1533396347.9860.11.camel@freebsd.org> User-Agent: Mutt/1.10.1 (2018-07-13) 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.27 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, 04 Aug 2018 15:43:39 -0000 On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote: > On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote: > > On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote: > > > > > > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote: > > > > > > > > On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote: > > > > > > > > > > On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov > > > > gmail. > > > > > com> wrote: > > > > > > > > > > > > > > > > > > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote: > > > > > > > > > > > > > > > > > > > > > On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov > > > > > > bel@gm > > > > > > > ail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This seems odd- pmap lock is acquired at [1], then > > > > > > > > > asserted > > > > > > > > > shortly > > > > > > > > > later at [2]... I avoid some of this stuff as well as I > > > > > > > > > can, > > > > > > > > > but is it > > > > > > > > > actually possible for PCPU_GET(...) acquired curpmap to > > > > > > > > > not > > > > > > > > > match > > > > > > > > > curthread->td_proc->p_vmspace->vm_pmap in this context? > > > > > > > > > > > > > > > > > > [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev > > > > > > > > > /efirt > > > > > > > > > .c?view=markup#l260 > > > > > > > > > [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd6 > > > > > > > > > 4/efir > > > > > > > > > t_machdep.c?view=markup#l254 > > > > > > > > There could be that curpcpu not yet synced with proc0 > > > > > > > > pmap.ššIt > > > > > > > > could be > > > > > > > > fixed. > > > > > > > > > > > > > > > > But it is not clear to me why efi_arch_enter() is called > > > > > > > > there.ššI see > > > > > > > > the check for GetTime belonging to the range described by > > > > > > > > a map > > > > > > > > descriptor. > > > > > > > > I do not see why do you need an enter into the EFI > > > > > > > > context for > > > > > > > > comparing > > > > > > > > integers. > > > > > > > This probably could have been documented better, but > > > > > > > efi_runtime > > > > > > > pointer may (always?) point into runtime service memory > > > > > > > that > > > > > > > isn't > > > > > > > valid/available at that point, so we get a fault and panic > > > > > > > when > > > > > > > dereferencing it to grab rt_gettime address. We ran into > > > > > > > this > > > > > > > wall > > > > > > > when adding the check originally. > > > > > > Wouldn't it be enough to access it by translating physical > > > > > > address > > > > > > into > > > > > > DMAP ? > > > > > Ah, sure, sure. [1] is proper form, yeah? > > > > > > > > > > [1] https://people.freebsd.org/~kevans/efi-dmap.diff > > > > What do we do on 32-bit arm that has no dmap but may have efi > > > > runtime > > > > support? > > > > > > > This should probably just be compiled out for !arm64 && !x86 - its > > > sole purpose was to compensate for outdated loader.efi that hasn't > > > done the SetVirtualAddressMap. EFI on 32-bit ARM is "new" enough > > > that > > > it shouldn't have this problem. > > Does EFI on 32bit arm have RT support ? > > I suspect the uboot implementation doesn't, but I can't think of any > reason why other implementations are not possible/available. In > particular, even 32bit arm supports virtualization and such an > environment could provide rt support. No, I mean, does our kernel has RT support on armv7 ? I only implemented necessary VM tricks for amd64, then it was ported to arm64, and in both cases it relies on 64bit address space and specific location of the KVA. From owner-freebsd-current@freebsd.org Sat Aug 4 15:47:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22F33106F27C for ; Sat, 4 Aug 2018 15:47:19 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 A49E17D271 for ; Sat, 4 Aug 2018 15:47:18 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: a6ce24b0-97fd-11e8-aff6-0b9b8210da61 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id a6ce24b0-97fd-11e8-aff6-0b9b8210da61; Sat, 04 Aug 2018 15:47:12 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w74FlBvX046208; Sat, 4 Aug 2018 09:47:11 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533397631.9860.14.camel@freebsd.org> Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 From: Ian Lepore To: Konstantin Belousov Cc: Kyle Evans , freebsd-current Current , Eitan Adler Date: Sat, 04 Aug 2018 09:47:11 -0600 In-Reply-To: <20180804154327.GQ6049@kib.kiev.ua> References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> <1533394281.9860.5.camel@freebsd.org> <20180804152225.GP6049@kib.kiev.ua> <1533396347.9860.11.camel@freebsd.org> <20180804154327.GQ6049@kib.kiev.ua> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 15:47:19 -0000 On Sat, 2018-08-04 at 18:43 +0300, Konstantin Belousov wrote: > On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote: > > > > On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote: > > > > > > On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote: > > > > > > > > > > > > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote: > > > > > > > > > > > > > > > [...] > > > > > What do we do on 32-bit arm that has no dmap but may have efi > > > > > runtime > > > > > support? > > > > > > > > > This should probably just be compiled out for !arm64 && !x86 - its > > > > sole purpose was to compensate for outdated loader.efi that hasn't > > > > done the SetVirtualAddressMap. EFI on 32-bit ARM is "new" enough > > > > that > > > > it shouldn't have this problem. > > > Does EFI on 32bit arm have RT support ? > > I suspect the uboot implementation doesn't, but I can't think of any > > reason why other implementations are not possible/available. In > > particular, even 32bit arm supports virtualization and such an > > environment could provide rt support. > No, I mean, does our kernel has RT support on armv7 ?  I only implemented > necessary VM tricks for amd64, then it was ported to arm64, and in both > cases it relies on 64bit address space and specific location of the KVA. I didn't realize the kernel implementation was arch-specific. So I guess this comes under the category of "we'll solve that problem when something comes along that provides efi rt for arm32." -- Ian From owner-freebsd-current@freebsd.org Sat Aug 4 19:19:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5FF1210501A5 for ; Sat, 4 Aug 2018 19:19:07 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 69D6984542; Sat, 4 Aug 2018 19:19:06 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 443f3786; Sat, 4 Aug 2018 21:18:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=lBS9bTL5moq7XQNpqeu03v/5ZEk=; b=QuG3EC2lCbaeYkGnRaVldiohrkMw uLWLuIJaaeZTl6kskmVoxzt41nh3tIbrs+QzX4v1NtfCF64ibtpznpPBSsAxwceh XXwRUx8MMRT7zN8nIpfsceAWnV9nlx6bwGd05CNZTtbiGGSM86wFNWGSTeYvpHFJ sfRZCFUaIwFMNMM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=UnvC66ZN7ZCBOqK4BjjHgVt9rDVwsy1N/r78X5AyZCbTCfB+J60dfxM3 EPcdgsBC/HBmuEO9r490Q93QJIHl4S7kz/Q8SL1M4yKcClON9Jp/HkOCqL2hc+k3 eqbNRQtNCurx6nunEzQcLiCJK22SyDj0NS65Xv2dovX6lgBiwVg= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 37661b3d TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 4 Aug 2018 21:18:58 +0200 (CEST) Date: Sat, 4 Aug 2018 21:18:58 +0200 From: Emmanuel Vadot To: Ian Lepore Cc: Konstantin Belousov , Kyle Evans , freebsd-current Current , Eitan Adler Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 Message-Id: <20180804211858.e7ea14c07b239cacf06ef248@bidouilliste.com> In-Reply-To: <1533397631.9860.14.camel@freebsd.org> References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> <1533394281.9860.5.camel@freebsd.org> <20180804152225.GP6049@kib.kiev.ua> <1533396347.9860.11.camel@freebsd.org> <20180804154327.GQ6049@kib.kiev.ua> <1533397631.9860.14.camel@freebsd.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 19:19:07 -0000 On Sat, 04 Aug 2018 09:47:11 -0600 Ian Lepore wrote: > On Sat, 2018-08-04 at 18:43 +0300, Konstantin Belousov wrote: > > On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote: > > >=20 > > > On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote: > > > >=20 > > > > On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote: > > > > >=20 > > > > >=20 > > > > > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrot= e: > > > > > >=20 > > > > > >=20 > > > > > >=20 > [...] > > > > > > What do we do on 32-bit arm that has no dmap but may have efi > > > > > > runtime > > > > > > support? > > > > > >=20 > > > > > This should probably just be compiled out for !arm64 && !x86 - its > > > > > sole purpose was to compensate for outdated loader.efi that hasn't > > > > > done the SetVirtualAddressMap. EFI on 32-bit ARM is "new" enough > > > > > that > > > > > it shouldn't have this problem. > > > > Does EFI on 32bit arm have RT support ? > > > I suspect the uboot implementation doesn't, but I can't think of any > > > reason why other implementations are not possible/available. In > > > particular, even 32bit arm supports virtualization and such an > > > environment could provide rt support. > > No, I mean, does our kernel has RT support on armv7 ?=A0=A0I only imple= mented > > necessary VM tricks for amd64, then it was ported to arm64, and in both > > cases it relies on 64bit address space and specific location of the KVA. >=20 > I didn't realize the kernel implementation was arch-specific. So I > guess this comes under the category of "we'll solve that problem when > something comes along that provides efi rt for arm32." U-Boot doesn't provide a runtime service, I never tested the available port of EDK2 for BBB or RPI, I guess they boot the kernel in HYP/non-secure mode and install an runtime in secure world along with some psci firmware. --=20 Emmanuel Vadot From owner-freebsd-current@freebsd.org Sat Aug 4 19:28:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A216C1050878 for ; Sat, 4 Aug 2018 19:28:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B83A84C76 for ; Sat, 4 Aug 2018 19:28:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id d10-v6so12609512itj.5 for ; Sat, 04 Aug 2018 12:28:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JYzdJaQUXrFib9w8WsSNu4tPZiaEE95G5dyWvMfw11M=; b=CI9nRNzTf13M5YiQqRZD+I0za1OCiU+TriN2zlgfYeLdc792vWLneP8C3xY9NgQWD4 QULjlmkUOi4RbvB+Hv2261kfk2iH3UqlMfBytxYSzUXG0XY8s5vjvOttGMIjuKtmPeip 8CvyzsVclr2M7wpB1tvx8p3qiLJt+NZoLoCbOvE+112nrWgb8uVoujoiIUqZI5q0rFko 5UH1uoCgoHna7UeA9e7Mz9KwjCHHiRAJTZAknzhGOp+XhdLFFIjOFwNDofb+5gLEBQ18 1gvbno0YHxNUIZelIFbA9QDTpu73d5JPysH8VRY56cg0dtO87J/jTWFi2OFo2TVfFh5V Z9yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JYzdJaQUXrFib9w8WsSNu4tPZiaEE95G5dyWvMfw11M=; b=Gdn/CQ5vVhnjSlMDG51jF9dH2W84Y/YPrM3Frkm18EvVnygtGfQlr26Nwr66xL3WNR ZBCAafUUgQyGXz7QgbOKMQ4FGdL96BFJ1DgBf2h45L9SAEf92MVJsub3+YNKR8++6hfm W9VEJCvIUo7xxN3IPWBUSpn4c9aG6Lc3OR9Iv4oi/+ULifd2sQ7nr2RMvl6tCEpMeiDm zlqriRwizSbC36WDcngL+7hrdtjIkAFTbDUQnrRmXTb2VPsNlNSIiBuY2Ua9x3uUNgGE jBgYA8TuQnsNebHibgqx/D4pHnSXFbYiTIIzxLFcQUiJetI7VXsYO1fmUBYER7VVzvnt Bw9Q== X-Gm-Message-State: AOUpUlEseJG23cRIbt/MzRikaPC5dYYMgoGo5yK/mcExaa/OXx7PFaIX idcYflo1Nz2drJTsc8R8no3vMboljZ7zVkwNWojztw== X-Google-Smtp-Source: AAOMgpfPVxJHi2H0NVzoW0TzuJE2RCi8rmweuj1HOA5N00uJliK/ZpOxmDsmpBT/X68E+dTmslsMjFp9hkB/lP8jvYo= X-Received: by 2002:a24:3ec3:: with SMTP id s186-v6mr10496819its.73.1533410918340; Sat, 04 Aug 2018 12:28:38 -0700 (PDT) MIME-Version: 1.0 References: <20180804083720.GJ6049@kib.kiev.ua> <20180804131352.GL6049@kib.kiev.ua> <1533394281.9860.5.camel@freebsd.org> <20180804152225.GP6049@kib.kiev.ua> <1533396347.9860.11.camel@freebsd.org> <20180804154327.GQ6049@kib.kiev.ua> <1533397631.9860.14.camel@freebsd.org> <20180804211858.e7ea14c07b239cacf06ef248@bidouilliste.com> In-Reply-To: <20180804211858.e7ea14c07b239cacf06ef248@bidouilliste.com> From: Warner Losh Date: Sat, 4 Aug 2018 20:28:25 +0100 Message-ID: Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 To: Emmanuel Vadot Cc: Ian Lepore , Konstantin Belousov , Kyle Evans , freebsd-current Current , Eitan Adler Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 19:28:39 -0000 On Sat, Aug 4, 2018, 8:21 PM Emmanuel Vadot wrote: > On Sat, 04 Aug 2018 09:47:11 -0600 > Ian Lepore wrote: > > > On Sat, 2018-08-04 at 18:43 +0300, Konstantin Belousov wrote: > > > On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote: > > > > > > > > On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote: > > > > > > > > > > On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote: > > > > > > > > > > > > > > > > > > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore > wrote: > > > > > > > > > > > > > > > > > > > > > > > [...] > > > > > > > What do we do on 32-bit arm that has no dmap but may have efi > > > > > > > runtime > > > > > > > support? > > > > > > > > > > > > > This should probably just be compiled out for !arm64 && !x86 - > its > > > > > > sole purpose was to compensate for outdated loader.efi that > hasn't > > > > > > done the SetVirtualAddressMap. EFI on 32-bit ARM is "new" enough > > > > > > that > > > > > > it shouldn't have this problem. > > > > > Does EFI on 32bit arm have RT support ? > > > > I suspect the uboot implementation doesn't, but I can't think of any > > > > reason why other implementations are not possible/available. In > > > > particular, even 32bit arm supports virtualization and such an > > > > environment could provide rt support. > > > No, I mean, does our kernel has RT support on armv7 ? I only > implemented > > > necessary VM tricks for amd64, then it was ported to arm64, and in both > > > cases it relies on 64bit address space and specific location of the > KVA. > > > > I didn't realize the kernel implementation was arch-specific. So I > > guess this comes under the category of "we'll solve that problem when > > something comes along that provides efi rt for arm32." > > U-Boot doesn't provide a runtime service, I never tested the available > port of EDK2 for BBB or RPI, I guess they boot the kernel in > HYP/non-secure mode and install an runtime in secure world along with > some > When I looked at it, I'd assumed there would be VA range we'd assign to the PAs in the EFI table that at the loader and kernel would agree on. The DMAP does this on x64 and aarch64, but that's not an option for armv7 nor i386. Warner > From owner-freebsd-current@freebsd.org Sat Aug 4 19:37:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 038751050B9B for ; Sat, 4 Aug 2018 19:37:37 +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 5AC9E85092; Sat, 4 Aug 2018 19:37:36 +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 w74JbNn2021249 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Aug 2018 22:37:26 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w74JbNn2021249 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w74JbNKY021248; Sat, 4 Aug 2018 22:37:23 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Aug 2018 22:37:23 +0300 From: Konstantin Belousov To: Warner Losh Cc: Emmanuel Vadot , Ian Lepore , Kyle Evans , freebsd-current Current , Eitan Adler Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 Message-ID: <20180804193723.GU6049@kib.kiev.ua> References: <20180804131352.GL6049@kib.kiev.ua> <1533394281.9860.5.camel@freebsd.org> <20180804152225.GP6049@kib.kiev.ua> <1533396347.9860.11.camel@freebsd.org> <20180804154327.GQ6049@kib.kiev.ua> <1533397631.9860.14.camel@freebsd.org> <20180804211858.e7ea14c07b239cacf06ef248@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) 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.27 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, 04 Aug 2018 19:37:37 -0000 On Sat, Aug 04, 2018 at 08:28:25PM +0100, Warner Losh wrote: > When I looked at it, I'd assumed there would be VA range we'd assign to the > PAs in the EFI table that at the loader and kernel would agree on. The DMAP > does this on x64 and aarch64, but that's not an option for armv7 nor i386. It is not DMAP. Amd64 works by assumption that ROM BIOS and its memory are located at the physical addresses below 4G. Since kernel is always mapped at upper half of the virtual address space, we hope that identity mapping for RT memory can be established over the user half of the VA. Apparently arm64 makes the same assumption. From owner-freebsd-current@freebsd.org Sat Aug 4 22:09:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8811D1054952; Sat, 4 Aug 2018 22:09:03 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (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 1367D8A914; Sat, 4 Aug 2018 22:09:03 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190e-57fff70000007f9c-29-5b6622cb2425 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 85.A9.32668.CC2266B5; Sat, 4 Aug 2018 18:03:56 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id w74M3rZD021204; Sat, 4 Aug 2018 18:03:54 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w74M3nrs010151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Aug 2018 18:03:51 -0400 Date: Sat, 4 Aug 2018 17:03:49 -0500 From: Benjamin Kaduk To: Eric McCorkle Cc: Warner Losh , FreeBSD Hackers , "freebsd-arch@freebsd.org" , freebsd-current , freebsd-security Subject: Re: Status of OpenSSL 1.1.1 Message-ID: <20180804220349.GJ68224@kduck.kaduk.org> References: <20180802234519.GD68224@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOKsWRmVeSWpSXmKPExsUixCmqrXtGKS3aYE+PoMW36X9ZLGZPn8Zk MefNByaL7Zv/MVr0bHrCZvF063JGBzaPD7u/snrM+DSfxePejglMAcxRXDYpqTmZZalF+nYJ XBmbWqQKdghXbLh5lrmB8SVvFyMnh4SAicSzTx8Zuxi5OIQEFjNJLNw4EcrZwChx9OgLZgjn CpPEv642li5GDg4WARWJ2WcVQLrZgMyG7svMIGERAQ2J+bsFQcqZBbqYJH5NOssCUiMMVNN9 6T4ziM0LtO3BqitQM98ySTzZ8oQNIiEocXLmE7AGZgEdiZ1b77CBDGUWkJZY/o8DIiwv0bx1 NtgcTgFnibe7v7KD2KICyhJ7+w6xT2AUnIVk0iwkk2YhTJqFZNICRpZVjLIpuVW6uYmZOcWp ybrFyYl5ealFusZ6uZkleqkppZsYwXEgybeDcVKD9yFGAQ5GJR7eEzxp0UKsiWXFlbmHGCU5 mJREeU0vp0QL8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuH935AaLcSbklhZlVqUD5OS5mBREue9 VxMeLSSQnliSmp2aWpBaBJOV4eBQkuA9oQi0R7AoNT21Ii0zpwQhzcTBCTKcB2i4H0gNb3FB Ym5xZjpE/hSjLsef91MnMQux5OXnpUqJ81aBFAmAFGWU5sHNAaUviez9Na8YxYHeEuaVASYz IR5g6oOb9ApoCRPQkmoTkA+KSxIRUlINjOq3b4TMurCu6EJmaMvyo/0P3f9kfuZ9+fvwzDUf /Sbu1PjxjC3xj/O8kIeWGk9fROzpnvBS5JjzliaRPT5ZTUqz08+GsaTdkNgr1vU45NJhX/Oo KGcJUZfm2tmbLARzrm7devDNwTYdoeOZBiJKBzlWFn3plK0MY376uubx9EnN5ue7/x6J01Fi Kc5INNRiLipOBACMabjjOgMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 04 Aug 2018 22:09:03 -0000 On Fri, Aug 03, 2018 at 07:02:18AM -0400, Eric McCorkle wrote: > On 08/03/2018 04:44, Warner Losh wrote: > > > > > > On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk > > wrote: > > > > On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote: > > > On 08/01/2018 09:02, Warner Losh wrote: > > > > > > > > > > > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > > > > > > >> wrote: > > > > > > > >     Hi folks, > > > > > > > >     I'm wondering what's the status of OpenSSL 1.1.1 integration > > into base? > > > >     More specifically, is there a repo or a branch that's > > started the > > > >     integration?  I'm aware of the wiki page and the list of > > port build > > > >     issues, but that seems to be based on replacing the base > > OpenSSL with a > > > >     port build (similar to the way one replaces it with LibreSSL). > > > > > > > >     I have some work I'd like to do that's gating on sorting out the > > > >     kernel/loader crypto situation, and I'd very much like to > > see OpenSSL > > > >     1.1.1 get merged, so I can start to look into doing that. > > > > > > > > > > > > There are patches to use bear SSL for the loader. OpenSSL is > > simply too > > > > large to use due to limits the loader operates under. > > > > > > I was going to look into the feasibility of doing something like what > > > LibreSSL does with portable, where they extract a subset of the full > > > library designed to be embedded in the kernel, loader, etc. > > > > > > I think it ought to be possible to do something like that, but it > > really > > > ought to be done in a tree with 1.1.1 integrated. > > > > > > > It wouldn't be terribly easy or effective, IMO.  OpenSSL wasn't designed > > with such modularity in mind. > > > > > > Others that have tried have found OpenSSL to be way too large for the > > boot loader and a completely impossible to subset enough to get things > > small enough due to the intertwingled nature of things. > > To what extent, if any, does this change in 1.1.1, though? > Probably not enough -- while libssl got a bit reorganized, libcrypto hasn't changed much. -Ben From owner-freebsd-current@freebsd.org Sat Aug 4 23:33:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E0DE105764D for ; Sat, 4 Aug 2018 23:33:01 +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 9470D8E4CA for ; Sat, 4 Aug 2018 23:33:00 +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:mime-version :user-agent:date:date:message-id:subject:subject:from:from :resent-message-id:resent-date:resent-from; s=201508; t= 1533425579; bh=JcV3O8glRm7oxMbzofTIN4DgpCftOH9eUihXv9QdRAI=; b=W BaRF+C0YmZuso6DC3wo8CLZokppUP3frNDguB6cpRyCkHAXaIjb8UokFMRdaz8uF pxzjTA63uKH43MfIgY8z90op24l/kTr7H6lUDAQNCrxMyKPTNvQNsU80sW0nq6Oy +m89PRMlR3a2MNJOOSaRMER3DkqhYG9GyJmTSGPQYs= 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 9C3322FCE9 for ; Sat, 4 Aug 2018 19:32:59 -0400 (EDT) Resent-From: Michael Butler Resent-To: freebsd-current Resent-Date: Sat, 4 Aug 2018 19:32:59 -0400 Resent-Message-ID: Resent-User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 To: brd@freebsd.org Cc: freebsd-current , Will Andrews From: Michael Butler Subject: SVN r337340 breaks installworld and mergemaster Openpgp: preference=signencrypt Message-ID: <3a1d3074-82be-60a6-d162-895cb37ea850@protected-networks.net> Date: Sat, 4 Aug 2018 19:31:14 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 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.27 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, 04 Aug 2018 23:33:01 -0000 make installworld results in .. (cd /usr/src/etc; make MK_MAKE_CHECK_USE_SANDBOX=yes etc-examples) cd /usr/src/etc; install -o root -g wheel -m 444 crontab devd.conf devfs.conf ddb.conf dhclient.conf disktab fbtab gettytab group hosts hosts.allow hosts.equiv libalias.conf libmap.conf login.access login.conf mac.conf motd netconfig networks newsyslog.conf nsswitch.conf phones profile protocols rc.bsdextended rc.firewall remote rpc services sysctl.conf syslog.conf termcap.small etc.amd64/ttys amd.map auto_master ftpusers inetd.conf /usr/src/usr.bin/locate/locate/locate.rc /usr/src/usr.bin/mail/misc/mail.rc ntp.conf pf.os rc.sendmail csh.cshrc csh.login csh.logout regdomain.xml nsmb.conf opieaccess /usr/share/examples/etc install: auto_master: No such file or directory *** Error code 71 Stop. make[6]: stopped in /usr/src/etc *** Error code 1 Stop. mergemaster complains of .. imb@vm01:/home/imb> sudo mergemaster -FUi *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot install: auto_master: No such file or directory *** FATAL ERROR: Cannot 'cd' to /usr/src and install files to the temproot environment imb