From owner-freebsd-current@freebsd.org Sun Sep 16 00:04: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 0E28E108D849 for ; Sun, 16 Sep 2018 00:04:57 +0000 (UTC) (envelope-from ler@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 B786774C65 for ; Sun, 16 Sep 2018 00:04:56 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from ler-imac.local (unknown [IPv6:2600:1700:210:b18f:6979:a972:e749:c62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 87ACD13951 for ; Sun, 16 Sep 2018 00:04:56 +0000 (UTC) (envelope-from ler@FreeBSD.org) Date: Sat, 15 Sep 2018 19:04:55 -0500 From: Larry Rosenman To: freebsd-current@FreeBSD.org Subject: udp6: Page fault panics Message-ID: <20180916000455.isqioezu6oovhjzg@ler-imac.local> Mail-Followup-To: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="sjyes5rs5asz7mtj" Content-Disposition: inline User-Agent: NeoMutt/20180716 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, 16 Sep 2018 00:04:57 -0000 --sjyes5rs5asz7mtj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've got 2 of these: Fatal trap 12: page fault while in kernel mode cpuid =3D 4; apic id =3D 04 fault virtual address =3D 0x7c fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80631428 stack pointer =3D 0x28:0xfffffe00ca17c440 frame pointer =3D 0x28:0xfffffe00ca17c480 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 1225 (isc-worker0003) trap number =3D 12 panic: page fault cpuid =3D 4 time =3D 1537050918 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00ca17c= 0f0 vpanic() at vpanic+0x1a3/frame 0xfffffe00ca17c150 panic() at panic+0x43/frame 0xfffffe00ca17c1b0 trap_fatal() at trap_fatal+0x35f/frame 0xfffffe00ca17c200 trap_pfault() at trap_pfault+0x49/frame 0xfffffe00ca17c260 trap() at trap+0x2ba/frame 0xfffffe00ca17c370 calltrap() at calltrap+0x8/frame 0xfffffe00ca17c370 --- trap 0xc, rip =3D 0xffffffff80631428, rsp =3D 0xfffffe00ca17c440, rbp = =3D 0xfffffe00ca17c480 --- selectroute() at selectroute+0x198/frame 0xfffffe00ca17c480 in6_selectroute_fib() at in6_selectroute_fib+0xf/frame 0xfffffe00ca17c4a0 ip6_output() at ip6_output+0xfd7/frame 0xfffffe00ca17c710 udp6_send() at udp6_send+0x720/frame 0xfffffe00ca17c8d0 sosend_dgram() at sosend_dgram+0x346/frame 0xfffffe00ca17c930 kern_sendit() at kern_sendit+0x201/frame 0xfffffe00ca17c9d0 sendit() at sendit+0x19e/frame 0xfffffe00ca17ca20 sys_sendmsg() at sys_sendmsg+0x61/frame 0xfffffe00ca17ca80 amd64_syscall() at amd64_syscall+0x272/frame 0xfffffe00ca17cbb0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00ca17cbb0 --- syscall (28, FreeBSD ELF64, sys_sendmsg), rip =3D 0x800be5a9a, rsp =3D = 0x7fffdf9fa468, rbp =3D 0x7fffdf9fa4a0 -- - Uptime: 35s Fatal trap 12: page fault while in kernel mode cpuid =3D 6; apic id =3D 06 fault virtual address =3D 0x98 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80636b2b stack pointer =3D 0x28:0xfffffe00c9d864b0 frame pointer =3D 0x28:0xfffffe00c9d86710 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 2274 (isc-worker0005) trap number =3D 12 panic: page fault cpuid =3D 6 time =3D 1537053032 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00c9d86= 160 vpanic() at vpanic+0x1a3/frame 0xfffffe00c9d861c0 panic() at panic+0x43/frame 0xfffffe00c9d86220 trap_fatal() at trap_fatal+0x35f/frame 0xfffffe00c9d86270 trap_pfault() at trap_pfault+0x49/frame 0xfffffe00c9d862d0 trap() at trap+0x2ba/frame 0xfffffe00c9d863e0 calltrap() at calltrap+0x8/frame 0xfffffe00c9d863e0 --- trap 0xc, rip =3D 0xffffffff80636b2b, rsp =3D 0xfffffe00c9d864b0, rbp = =3D 0xfffffe00c9d86710 --- ip6_output() at ip6_output+0xeeb/frame 0xfffffe00c9d86710 udp6_send() at udp6_send+0x720/frame 0xfffffe00c9d868d0 sosend_dgram() at sosend_dgram+0x346/frame 0xfffffe00c9d86930 kern_sendit() at kern_sendit+0x201/frame 0xfffffe00c9d869d0 sendit() at sendit+0x19e/frame 0xfffffe00c9d86a20 sys_sendmsg() at sys_sendmsg+0x61/frame 0xfffffe00c9d86a80 amd64_syscall() at amd64_syscall+0x272/frame 0xfffffe00c9d86bb0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00c9d86bb0 --- syscall (28, FreeBSD ELF64, sys_sendmsg), rip =3D 0x800be5a9a, rsp =3D = 0x7fffdf5f8468, rbp =3D 0x7fffdf5f84a0 -- - Uptime: 33m21s both on r338696. Ideas? I *DO* have cores, and can give access. This is one of my nameservers. --=20 Larry Rosenman https://people.FreeBSD.org/~ler/ Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 --sjyes5rs5asz7mtj Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHBBAABCgCrFiEEHjgknedhWzvJgwVzaXyZsatIp30FAludnictFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3JnbGVyQEZyZWVCU0Qub3JnXxSAAAAAAC4AKGlz c3Vlci1mcHJAbm90YXRpb25zLm9wZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxRTM4 MjQ5REU3NjE1QjNCQzk4MzA1NzM2OTdDOTlCMUFCNDhBNzdEAAoJEGl8mbGrSKd9 ofMH/RI321C9nxzKaaMJtdABqU9TsWdkVG1mZd3Q6osvghJaABluA3Isjhf+XTaj p/Zoc4iBCku3pnnx9NVNBM7+T70haAgcYDw6+4KcYPuNTfLk/W7hspm6eXxdLwPs YNwWWwpP27beahcO8WqCJY5BFqRhtemzSp4Pv1yS0Z2jGuxB4KNQ9EFLMB2HKcid CaRMOuvct1A0Yt++/IBniYlDXkAttWMwZObwK0EMOaSiHrYZhcK13Ox/VpBP18tK 6KhYs9068YF+fC/TfCl8eyLiV1j1sTFS+qY3QnnS32I3uPYDm705fFwBcKZd12b0 fZnKwrsBG1HPD7Duh+M5STtRE14= =ZEYi -----END PGP SIGNATURE----- --sjyes5rs5asz7mtj-- From owner-freebsd-current@freebsd.org Sun Sep 16 00:16:44 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 BEF9A108E270 for ; Sun, 16 Sep 2018 00:16:44 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (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 532EB7657C; Sun, 16 Sep 2018 00:16:44 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1537056995; bh=FtVyRDjO m9AhBHXMIpq5RjrRvZO11QgKf9izOQRfrZk=; b=atOLldwd+fEmRVJd52TzRMgF y61qlVDydHcdd3KAJ5LGf7BW/fdOJbzDS1WtLXsA8WESF50d8WO7PpHQPcENVPZ0 pFJU732CSbo3kT7hggzwlzpDqciLKXWErIpwi53Fp+nRrm+496P4QfDk4g+UFg6g 6KOPY2QUK1UDdg9jfUQ= 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 4A6B8C63C; Sat, 15 Sep 2018 20:16:35 -0400 (EDT) Subject: Re: udp6: Page fault panics To: freebsd-current@FreeBSD.org, Larry Rosenman References: <20180916000455.isqioezu6oovhjzg@ler-imac.local> From: Michael Butler Openpgp: preference=signencrypt Message-ID: Date: Sat, 15 Sep 2018 20:16:34 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <20180916000455.isqioezu6oovhjzg@ler-imac.local> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US 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, 16 Sep 2018 00:16:45 -0000 On 9/15/18 8:04 PM, Larry Rosenman wrote: > I've got 2 of these: > > Fatal trap 12: page fault while in kernel mode > cpuid = 4; apic id = 04 > fault virtual address = 0x7c > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80631428 > stack pointer = 0x28:0xfffffe00ca17c440 > frame pointer = 0x28:0xfffffe00ca17c480 > 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 = 1225 (isc-worker0003) > trap number = 12 > panic: page fault > cpuid = 4 > time = 1537050918 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00ca17c0f0 > vpanic() at vpanic+0x1a3/frame 0xfffffe00ca17c150 > panic() at panic+0x43/frame 0xfffffe00ca17c1b0 > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe00ca17c200 > trap_pfault() at trap_pfault+0x49/frame 0xfffffe00ca17c260 > trap() at trap+0x2ba/frame 0xfffffe00ca17c370 > calltrap() at calltrap+0x8/frame 0xfffffe00ca17c370 > --- trap 0xc, rip = 0xffffffff80631428, rsp = 0xfffffe00ca17c440, rbp = 0xfffffe00ca17c480 --- > selectroute() at selectroute+0x198/frame 0xfffffe00ca17c480 > in6_selectroute_fib() at in6_selectroute_fib+0xf/frame 0xfffffe00ca17c4a0 > ip6_output() at ip6_output+0xfd7/frame 0xfffffe00ca17c710 > udp6_send() at udp6_send+0x720/frame 0xfffffe00ca17c8d0 > sosend_dgram() at sosend_dgram+0x346/frame 0xfffffe00ca17c930 > kern_sendit() at kern_sendit+0x201/frame 0xfffffe00ca17c9d0 > sendit() at sendit+0x19e/frame 0xfffffe00ca17ca20 > sys_sendmsg() at sys_sendmsg+0x61/frame 0xfffffe00ca17ca80 > amd64_syscall() at amd64_syscall+0x272/frame 0xfffffe00ca17cbb0 > fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00ca17cbb0 > --- syscall (28, FreeBSD ELF64, sys_sendmsg), rip = 0x800be5a9a, rsp = 0x7fffdf9fa468, rbp = 0x7fffdf9fa4a0 -- > - > Uptime: 35s [ .. snip .. ] This is likely another instance of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230950 I had similar, seemingly random panics on a nameserver I run and the only workaround I have so far is to revert SVNs r338257 and r338306 :-( imb From owner-freebsd-current@freebsd.org Sun Sep 16 09:25:45 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 07D18109C3B7; Sun, 16 Sep 2018 09:25:45 +0000 (UTC) (envelope-from pstef@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 A883F84A70; Sun, 16 Sep 2018 09:25:44 +0000 (UTC) (envelope-from pstef@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1403) id 8595B15A8D; Sun, 16 Sep 2018 09:25:44 +0000 (UTC) Date: Sun, 16 Sep 2018 11:25:44 +0200 From: "Piotr P. Stefaniak" To: Mark Millard Cc: freebsd-arm , FreeBSD Current Subject: Re: FYI: devel/kyua 14 failures for head -r338518M based build in a Pine64+ 2GB (aarch64 / cortexA53 / A64) context Message-ID: <20180916092544.GK53055@freefall.freebsd.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-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: Sun, 16 Sep 2018 09:25:45 -0000 On 2018-09-11 02:44:49, Mark Millard wrote: >usr.bin/indent/functional_test:nsac -> failed: atf-check failed; see the output of the test for details [0.151s] >usr.bin/indent/functional_test:sac -> failed: atf-check failed; see the output of the test for details [0.150s] Those were predictable since r334944 and before r336601, so I don't know how it happens that you're getting them with r338518. From owner-freebsd-current@freebsd.org Sun Sep 16 12:06: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 310BF10A03EC for ; Sun, 16 Sep 2018 12:06:36 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-20.consmr.mail.bf2.yahoo.com (sonic312-20.consmr.mail.bf2.yahoo.com [74.6.128.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3B6F89A09 for ; Sun, 16 Sep 2018 12:06:35 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: te6dNIsVM1kF2C8gmql.v4016t0xF3SJPfkKAASisuru8ROlyypc43MJzLd7C0U uXNJgnVgXSkxjiJGRKiaADFjMc2ZaY8zdAUoFDzmkWaH13FSFgGCPsiMyX.8HeLBv9U7fnIkorQO Yqbi7PusRaPTxQ.8_uf6Sxi1e9iW3PwxHOZrDl1kr6g8fBBNB331Y2Nv.exaKfunWUjx6lcT9Ppa q7ZeLhlep7beY4MTMcNUXaW6C25FTbH01jmsyzI0JKA2RkGPdsrBV9vwSyVdgsAN_1W0Mfd4jHjv TFAjoGDDh8xctsF8QrYtFW.MNGac1CqVRGyTBQcHZLwT5uCOVz5frGlDgxzUIRrMjtVwLbN9IfYb siONGD1PhrOgcINiBi6HMKW2WftTP1ZmbDNFJWD98u9uY.jUBkPzKWnioeRDlc_YmZuMWu1mONoL iDPuPBl_hw07DRhGCZgSlqD1SUnf880.s.v5k4LvDcECQQYcwBTul_wkVlagtd9vR_bAb1ZJOEeh RWqsFsbhE8FOpPoA47f02e_py0.3inNW5yDLN0RVbpcbNQ9YEB0qDlbB6Y0ORAYw5hezW9BQWGO9 _7fq.KtxHod8oUnajqzsgvcH.FyAyGzUSgk8SbHcd4iTiwweqoeXEiF_rcuKoa40SjEWXsD6mabB XbpF3bUanlvijLnCVdZxXOHEeHNGaN0x5uaDMQsK04hYn1yAcQ0OIsVoS8DvaGs3ReAmxxyjkSri tiewzyoC7vM1ztqzwq6atAyvpKmN19WEw1JKKT2FWGabWVu267XeyNOiZzAnXJqeFUW0knporYF8 coatl0PFIZzvGZIUVN5TOlYy0soDMWZLMnreBjsxMHrLGTATUJkQZYCXqSYquzSaRGdIrKXwUWl3 .gnFFKJ_rtVhE7jONNXk.LGPVqCoKQ9jys763JoiFOw9.OS5VAdCa.p5gTfXZgSD2Z9uQGr8QMqM bCAbCwT0wk.yRcFeRUqNr88FWRUWPrY2GiAqESSl_O2vqol9TXUogbAw.yf6W_g1RwU02sLKB.wm ARTbbONdvow-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.bf2.yahoo.com with HTTP; Sun, 16 Sep 2018 12:06:29 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp423.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID eaec93886b593d4509947a2f775b6ce9; Sun, 16 Sep 2018 12:06:26 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: FYI: devel/kyua 14 failures for head -r338518M based build in a Pine64+ 2GB (aarch64 / cortexA53 / A64) context From: Mark Millard In-Reply-To: <20180916092544.GK53055@freefall.freebsd.org> Date: Sun, 16 Sep 2018 05:06:23 -0700 Cc: freebsd-arm , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180916092544.GK53055@freefall.freebsd.org> To: "Piotr P. Stefaniak" 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: Sun, 16 Sep 2018 12:06:36 -0000 On 2018-Sep-16, at 2:25 AM, Piotr P. Stefaniak = wrote: > On 2018-09-11 02:44:49, Mark Millard wrote: >> usr.bin/indent/functional_test:nsac -> failed: atf-check failed; = see the output of the test for details [0.151s] >> usr.bin/indent/functional_test:sac -> failed: atf-check failed; see = the output of the test for details [0.150s] >=20 > Those were predictable since r334944 and before r336601, so I don't = know > how it happens that you're getting them with r338518. >=20 Hmm: # ls -lTdt /usr/tests/usr.bin/indent/* -r--r--r-- 1 root wheel 121 Sep 13 22:53:30 2018 = /usr/tests/usr.bin/indent/Kyuafile . . . -r--r--r-- 1 root wheel 295 Sep 13 22:53:29 2018 = /usr/tests/usr.bin/indent/binary.0 -r--r--r-- 1 root wheel 92 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0.pro -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0.stdout -r--r--r-- 1 root wheel 122 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0 -r--r--r-- 1 root wheel 94 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0.pro -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0.stdout -r--r--r-- 1 root wheel 123 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0 vs. ( note: usr.bin vs usr/bin ): Modified: head/ObsoleteFiles.inc = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- head/ObsoleteFiles.inc Sun Jul 22 12:04:21 2018 = (r336600) +++ head/ObsoleteFiles.inc Sun Jul 22 12:45:02 2018 = (r336601) @@ -38,6 +38,13 @@ # xargs -n1 | sort | uniq -d; # done =20 +# 20180722: indent(1) option renamed, test files follow +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0 +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.pro +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.stdout +OLD_FILES+=3Dusr/bin/indent/tests/sac.0 +OLD_FILES+=3Dusr/bin/indent/tests/sac.0.pro +OLD_FILES+=3Dusr/bin/indent/tests/sac.0.stdout # 20180721: move of libmlx5.so.1 and libibverbs.so.1 OLD_LIBS+=3Dusr/lib/libmlx5.so.1 OLD_LIBS+=3Dusr/lib/libibverbs.so.1 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun Sep 16 17:50: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 2EDC610A6AEF; Sun, 16 Sep 2018 17:50:40 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mailout.stack.nl (mailout05.stack.nl [IPv6:2001:610:1108:5010::202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.stack.nl", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C6BA171C92; Sun, 16 Sep 2018 17:50:39 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from toad2.stack.nl (toad2.stack.nl [IPv6:2001:610:1108:5010::161]) by mailout.stack.nl (Postfix) with ESMTP id C27B44B; Sun, 16 Sep 2018 19:50:29 +0200 (CEST) Received: by toad2.stack.nl (Postfix, from userid 1677) id BB603892CD; Sun, 16 Sep 2018 19:50:29 +0200 (CEST) Date: Sun, 16 Sep 2018 19:50:29 +0200 From: Jilles Tjoelker To: Mark Millard Cc: freebsd-arm , FreeBSD Current Subject: Re: FYI: devel/kyua 14 failures for head -r338518M based build in a Pine64+ 2GB (aarch64 / cortexA53 / A64) context Message-ID: <20180916175029.GA55717@stack.nl> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) 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, 16 Sep 2018 17:50:40 -0000 On Tue, Sep 11, 2018 at 08:48:03AM -0700, Mark Millard wrote: > [Adding listing broken tests, but ignoring sys/cddl/zfs/ ones. > lib/libc/string/memcmp_test:diff is one of them.] > ===> Broken tests > lib/libc/string/memcmp_test:diff -> broken: Premature exit; test case received signal 6 (core dumped) [3.962s] The problem here is that our definition of memcmp() is tighter than the one in the standards and glibc. We define the return value to be the difference between the first differing bytes, while the standards and glibc only define the sign (negative, zero or positive). Looking at contrib/cortex-strings/src/aarch64/memcmp.S, a bic pos, pos, #7 after the clz may help. On another note, the comment just below that, /* But we need to zero-extend (char is unsigned) the value and then perform a signed 32-bit subtraction. */ shows a wrong reason for doing the right thing since memcmp (as well as strcmp and strncmp) are defined to compare based on unsigned chars, regardless of the signedness of char. -- Jilles Tjoelker From owner-freebsd-current@freebsd.org Sun Sep 16 20:21:45 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 05C8B10A9736 for ; Sun, 16 Sep 2018 20:21:45 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic303-4.consmr.mail.bf2.yahoo.com (sonic303-4.consmr.mail.bf2.yahoo.com [74.6.131.43]) (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 A14BD7EAA4 for ; Sun, 16 Sep 2018 20:21:44 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: JSOFQo4VM1mYQcBz.40qWfs251XMRE0ME4h1gaAt.KnD1kpEn36wMCwmlZj7blv qIliHFSA6Baernz4IMSOLFiS3RxS.HMRGE6GXnF8zy7s0X9amV7Krggminoxtq74IljZXnDBvCZW 46BM2SH26OUxfHWOC_KgX8BtZzcKfD8q_IulXafdZO_sHFVzFRYU5plrY9KvRzDjGD22uPaVWE8P OISLMrng2lxiv5WSYdh.1iIWtbXQw.tIl_gFXaDHbpCfxUlaFZWmGa9KXpymjqD8PJC8_O2b5n6d sFUdqgpAEa6jrrX0pEFdYyDCpSxw0eEBJHhpZ786.p0COVMej9s7umBWCuOzzjGSR3YKkJkzPnWH iT8LHBODza7PqG2tm9GG83XGILjJc4H9JbYt17JzeQMLuTK2efZKpy2arYqQ7sDrmKJVAdBP4k7d 92_DJ5WdrE0Jzjz8gMGVwas_w5Oc7qtgqclHXiR1IEcAJDLkDQa48nyROz8EtbzOHWn2F0CR7H2y 3eyVUqiLZAVp_7h4nlj1pNEvyO40pXfnax4U2lO4y9OVmcj2Y8rRLNBcLoaR0H92n.w2yutskU2u YZc_l7qX9R9HdgJnMsNUm_xz9AURFSstwESy3g1epxxxHvs_9n08N0.v9U7cdTLCWlOxSd4a7i7P j_DMc.eZN35iizgIIYEO6_oA5_Jx5b2nR3Q5npSRrdBpnspGlGh1.4KN0ddV7NLT.M5.PdOLMXNn OFkfmY84vG6BKV_WfiBnEGeNrAahVA9mrKXb3dlVmmQnto2BXpj1r6L6L6pszym5hWq9Rive6KGX bWI8hN9FF9fckho_dRpo9EanvWdTXFefrpo4JcwsXYdum7.qyJnqc8bW.EI.gherKENtov6Lt8N2 zLTvdpwkvNLLa5ixpSUTZKg8aQPi.HtcISjn4sGHl4FKpif4fQIbZb80z6ZKZRVRM0P4bpCmYDQw D9Uqxdb8VxpnYn8QXAjbopn7ZimhWEtPRcw_xGnOBY7LhJMp7LKebzPF9l68OPtS6dUM7Ko79u2G sJzrN0RITexM- Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.bf2.yahoo.com with HTTP; Sun, 16 Sep 2018 20:21:38 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp428.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 52cbd135864599ae043a5a6370b2329a; Sun, 16 Sep 2018 20:21:35 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: FYI: devel/kyua 14 failures for head -r338518M based build in a Pine64+ 2GB (aarch64 / cortexA53 / A64) context From: Mark Millard In-Reply-To: <20180916175029.GA55717@stack.nl> Date: Sun, 16 Sep 2018 13:21:33 -0700 Cc: freebsd-arm , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180916175029.GA55717@stack.nl> To: Jilles Tjoelker 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: Sun, 16 Sep 2018 20:21:45 -0000 On 2018-Sep-16, at 10:50 AM, Jilles Tjoelker wrote: > On Tue, Sep 11, 2018 at 08:48:03AM -0700, Mark Millard wrote: >> [Adding listing broken tests, but ignoring sys/cddl/zfs/ ones. >> lib/libc/string/memcmp_test:diff is one of them.] >=20 >> =3D=3D=3D> Broken tests >> lib/libc/string/memcmp_test:diff -> broken: Premature exit; test = case received signal 6 (core dumped) [3.962s] >=20 > The problem here is that our definition of memcmp() is tighter than = the > one in the standards and glibc. We define the return value to be the > difference between the first differing bytes, while the standards and > glibc only define the sign (negative, zero or positive). >=20 > Looking at contrib/cortex-strings/src/aarch64/memcmp.S, a > bic pos, pos, #7 after the clz may help. >=20 > On another note, the comment just below that, >=20 > /* But we need to zero-extend (char is unsigned) the value and = then > perform a signed 32-bit subtraction. */ >=20 > shows a wrong reason for doing the right thing since memcmp (as well = as > strcmp and strncmp) are defined to compare based on unsigned chars, > regardless of the signedness of char. Ahh, standard are so much fun: there are so many to choose from. I looked up ISO/IEC 9899:2011 (E) and its 7.24.4.1 "The memcmp = function". It makes no such explicit claim about using using unsigned chars for the comparison standard: QUOTE of the Description part: The memcmp function compares the first n characters of the object = pointed by s1 to the first n characters of the object pointed by s2. END QUOTE QUOTE of the Returns part: The memcmp function returns an integer greater than, equal to, or less = than zero, accordingly as the object pointed to by s1 is greater than, equal to, or = less than the object pointed to by s2. END QUOTE If I had to guess the intent of "characters" would be based on the char = type for C11. I did not find anything about the issue in the C99 rationale = that I also happen to have available to look at. For all I know, POSIX or other standards may be more explicit and not agree. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun Sep 16 20:43: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 4CCC210A9EE6 for ; Sun, 16 Sep 2018 20:43:55 +0000 (UTC) (envelope-from manfredantar@gmail.com) Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (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 C136D7FA94; Sun, 16 Sep 2018 20:43:54 +0000 (UTC) (envelope-from manfredantar@gmail.com) Received: by mail-pl1-x634.google.com with SMTP id p5-v6so6432241plk.3; Sun, 16 Sep 2018 13:43:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :cc:to; bh=xbfuC/Q0zy41owB6cTKMYHUZox8R+rg51AQyNxjBG9E=; b=GvDrGRuvU7rjJp0bGNp+4AnxYkAD3maYUshtjSPTUjbLyhn4uobP3JSuyEIfJ15Y2w iQxsGIT1AF0M6ScYfXoxc6B6KvAsTcivQgjFQxMAC8xYUQb2UNO7j4WS7ecOW0hksX9G kU0bWTx42JpJrB/BtbDX9YgACaXAKXfGNxV0J0sHW5wapf8MLBRRGcR2Z05ff8lnDACT wtqW51ryQ5zDg/zUes9oyMawSmVe2i71KAB50EUbqB0BA4u6aEj9JKMshLSwYu+ZGQ8L o/2sFWTVkERXvFqelwKRzRp5hp62XuMMoQ72X8kAAH27z45ZxgdmC99AXYpyONhQ5GMD R04Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:cc:to; bh=xbfuC/Q0zy41owB6cTKMYHUZox8R+rg51AQyNxjBG9E=; b=BpBZzRkQFJ9drmR2tolgLhB3VkDcIiiHpJZ1vYvB/N5YI9u6959N6DBMmAESXtXB+f RmkvucNdfeevZZ25NQwyCmInos1BTxbSEAGFxaAryCoHmi9XPOadeX69aZzTgdL/OY7z K4Lif0SrcwRdGPbIWR9mPZUMGYFXEmJmWzWNTLxiH8uubYSthWq3M48GqO48/tNecL2r jPcPqDMG+UKS50b96TRw2NKncIReMb+DTgolEYICvj6U2IUAVu9VBrivBz0GTgsrL6C/ 1f4oQmegUZlBev3Zcp7M5xB0IwM56L5NFo+pXVnp5PU/AXz69avtVA+ajFGq5UTvfESf /Vdg== X-Gm-Message-State: APzg51DEoAfNssoB97jZSM3oeydNr43YdmF7oH/8BwiZwNgwdKxgOZtI UzBk/O8Q+EGlffe1qVKQ/fhtC5clB8YFEg== X-Google-Smtp-Source: ANB0VdaFsfT0d6D5F5FABmrdOA69qA8NEYKXEfn6qruLOyjBRInOyvJkqalbc+pgMwe1DDinfUi5nQ== X-Received: by 2002:a17:902:d213:: with SMTP id t19-v6mr22083942ply.63.1537130633075; Sun, 16 Sep 2018 13:43:53 -0700 (PDT) Received: from octo.pozo.com (50-197-129-138-static.hfc.comcastbusiness.net. [50.197.129.138]) by smtp.gmail.com with ESMTPSA id q25-v6sm17928328pfk.96.2018.09.16.13.43.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Sep 2018 13:43:52 -0700 (PDT) From: Manfred Antar Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Current-Alpha6 panic with new support.S AMD64 Message-Id: <10C66C40-045A-4555-8B47-189E5C1FEA13@gmail.com> Date: Sun, 16 Sep 2018 13:43:51 -0700 Cc: kib@freebsd.org To: freebsd-current , mjg@reebsd.org 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: Sun, 16 Sep 2018 20:43:55 -0000 With r338700 support.S i get panic after rebooting: avail memory = 16529514496 (15763 MB) 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 100 kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff80747d86 stack pointer = 0x28:0xffffffff82451820 frame pointer = 0x28:0xffffffff82451820 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () [ thread pid 0 tid 0 ] Stopped at strcmp+0x6: movb (%rsi),%dl db> bt Tracing pid 0 tid 0 td 0xffffffff81015180 strcmp() at strcmp+0x6/frame 0xffffffff82451820 sysctl_register_oid() at sysctl_register_oid+0x4c/frame 0xffffffff82451b40 sysctl_add_oid() at sysctl_add_oid+0x20d/frame 0xffffffff82451b90 et_register() at et_register+0x14d/frame 0xffffffff82451bf0 native_lapic_init() at native_lapic_init+0x4e3/frame 0xffffffff82451c10 madt_setup_local() at madt_setup_local+0x26e/frame 0xffffffff82451c40 apic_setup_local() at apic_setup_local+0x44/frame 0xffffffff82451c50 mi_startup() at mi_startup+0x118/frame 0xffffffff82451c70 btext() at btext+0x2c db> With support.S r338683 no problem Manfred From owner-freebsd-current@freebsd.org Sun Sep 16 20:50: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 0104410AA0CC; Sun, 16 Sep 2018 20:50:32 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mailout.stack.nl (mailout05.stack.nl [131.155.140.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.stack.nl", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9536E7FC6B; Sun, 16 Sep 2018 20:50:31 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from toad2.stack.nl (toad2.stack.nl [IPv6:2001:610:1108:5010::161]) by mailout.stack.nl (Postfix) with ESMTP id B65E54B; Sun, 16 Sep 2018 22:50:29 +0200 (CEST) Received: by toad2.stack.nl (Postfix, from userid 1677) id AEC86892D3; Sun, 16 Sep 2018 22:50:29 +0200 (CEST) Date: Sun, 16 Sep 2018 22:50:29 +0200 From: Jilles Tjoelker To: Mark Millard Cc: freebsd-arm , FreeBSD Current Subject: Re: FYI: devel/kyua 14 failures for head -r338518M based build in a Pine64+ 2GB (aarch64 / cortexA53 / A64) context Message-ID: <20180916205029.GB55717@stack.nl> References: <20180916175029.GA55717@stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) 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, 16 Sep 2018 20:50:32 -0000 On Sun, Sep 16, 2018 at 01:21:33PM -0700, Mark Millard wrote: > On 2018-Sep-16, at 10:50 AM, Jilles Tjoelker wrote: > > On another note, the comment just below that, > > /* But we need to zero-extend (char is unsigned) the value and then > > perform a signed 32-bit subtraction. */ > > shows a wrong reason for doing the right thing since memcmp (as well as > > strcmp and strncmp) are defined to compare based on unsigned chars, > > regardless of the signedness of char. > Ahh, standard are so much fun: there are so many to choose from. > I looked up ISO/IEC 9899:2011 (E) and its 7.24.4.1 "The memcmp function". > It makes no such explicit claim about using using unsigned chars for > the comparison standard: > QUOTE of the Description part: > The memcmp function compares the first n characters of the object pointed > by s1 to the first n characters of the object pointed by s2. > END QUOTE > QUOTE of the Returns part: > The memcmp function returns an integer greater than, equal to, or less > than zero, accordingly as the object pointed to by s1 is greater than, > equal to, or less than the object pointed to by s2. > END QUOTE > If I had to guess the intent of "characters" would be based on the > char type for C11. I did not find anything about the issue in the C99 > rationale that I also happen to have available to look at. In C99, C11 and C17, the text about using unsigned chars is under "Comparison functions" and it applies to memcmp, strcmp and strncmp (which are documented together in the section). > For all I know, POSIX or other standards may be more explicit and not > agree. POSIX does not document memcmp, strcmp and strncmp close together and copies the text about using unsigned chars to each of them. This means that it agrees with the C standards. -- Jilles Tjoelker From owner-freebsd-current@freebsd.org Sun Sep 16 21:05:44 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 13F8C10AAE83; Sun, 16 Sep 2018 21:05:44 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (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 B4DF880D61; Sun, 16 Sep 2018 21:05:43 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from hammy.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 87A6D5646F; Sun, 16 Sep 2018 16:05:42 -0500 (CDT) Subject: Re: Bad DHCP Checksums over VLANs To: Kurt Jaeger Cc: freebsd-current@freebsd.org, freebsd-net@freebsd.org References: <9dd3c7f9-d970-5d30-ebf2-c0f40c76011b@vangyzen.net> <20180915060615.GF2118@home.opsec.eu> From: Eric van Gyzen Message-ID: <794ae64b-54d8-cfde-2e9c-87b3b74e0516@vangyzen.net> Date: Sun, 16 Sep 2018 16:05:41 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180915060615.GF2118@home.opsec.eu> 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: Sun, 16 Sep 2018 21:05:44 -0000 On 9/15/18 1:06 AM, Kurt Jaeger wrote: > Can you disable all the options of the NIC ? > > ifconfig igb0 -rxcsum -txcsum -wol -tso4 -vlanmtu -vlanhwtag -vlanhwcsum -vlanhwtso > > Try to disable everything that can be disabled, e.g. LRO etc. Disabling vlanhwtag works around the problem. Also note that only DHCP traffic has this problem. If I assign an address manually, all traffic flows normally. Maybe the problem is in the BPF send path. Eric From owner-freebsd-current@freebsd.org Sun Sep 16 21:08: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 8B12710802B1 for ; Sun, 16 Sep 2018 21:08:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic316-9.consmr.mail.gq1.yahoo.com (sonic316-9.consmr.mail.gq1.yahoo.com [98.137.69.33]) (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 15A8481022 for ; Sun, 16 Sep 2018 21:08:20 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: aBOTvt4VM1lOU_VaJz55xDv4BQPkvbWowWnPwNVfyFWcl.b2e7TsLQmfDxoK6MB XXiclXZIosmO9XDy5O0kG5m5lv3d9Dl9ihbLgmWddNz85HMT2PCC.OL_B8nHoOYlfRmFt4uJUSWI _rTMGsZAPlJT0qqe21uIOhH5Qp4Rsxv3yvDzFEgS51BQOIE3zO17N_IWp0ceUn6jo7ho55Kmb3pa Q.QMevQEE8Zumsqs7Id5KK4Hd_BBdLz963FUozagwESR.D33aiSOrw16AAIHlgmu6eLJVwgZJoOh JoaJDEG7.rACViSrh8UIyWAt2h8aFLGqzphiq5YXfTEbDKvlZAqEyjModv4gMUGtyZi_MVblI5zP M.d9k.8qUvz9Mk0nKsIbumgPzTKzAF4tztvdmrU.ngH3BcxQx2yWaFrakjVJdzvD8lGX6EClH_ed V5Cd6zKHzetdbt6MswYOcRyI0Vz6t.wMakXwDLPr1VWSb7wkOfgHgaL8dtCan23Dx24vTiED03zo TkQWWUDEdpCBJriO7EELPrPPuMTiPnXJMgdKly_dXaq59n4_RuSM2edZFZluUv49FIiKvqF61nZk IlWB21Bmvbco.d0q.8SMNGMihU5h.eUklAr79kP0nNXOOfJ33A6srmrtrV1ptMyDH2pmAffBx0ls wQgSRx4Ya8xqujKdgTdBBt4T7VzOQOEX158kxKFydYRdTtXAzZXh5KS2Vmnp4NbghGppQwmloSfL 2nJImixxO2T9Zu8pu9GAesewhnWiEXiFQQBx573fRtj2.q.f7Vp_WZYm93mIjryDlAglBruSfIZr uvLry6KV7xSxTWYrTXjZvwhXHNVxqN9iPsfkl4kZy4orgCvqjTABUNIw.q.xtIva0lUz.9QtufC_ A4XZO5b0MJ2mbqmuf17p2xuZpPI17mq8vrHgsNHNB747OF8oK4Yl25MfmBfyR8yBtGPeczPhjqBf TibBDZBlbVnIiNlOWA2SbgtXq4H95NS3om56UXE.DWRjwViA2CEUxxcQPwlbj0KIzkf5rw5BMbJ8 5PIWdXFR2 Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Sun, 16 Sep 2018 21:08:14 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp420.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID eb64288a0ca7d1d2582ace146573d790; Sun, 16 Sep 2018 20:58:05 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: FYI: devel/kyua 14 failures for head -r338518M based build in a Pine64+ 2GB (aarch64 / cortexA53 / A64) context From: Mark Millard In-Reply-To: <20180916205029.GB55717@stack.nl> Date: Sun, 16 Sep 2018 13:58:04 -0700 Cc: freebsd-arm , FreeBSD Current Content-Transfer-Encoding: 7bit Message-Id: <8FD86880-11E4-49E3-848E-B05FF23A37B5@yahoo.com> References: <20180916175029.GA55717@stack.nl> <20180916205029.GB55717@stack.nl> To: Jilles Tjoelker 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: Sun, 16 Sep 2018 21:08:21 -0000 On 2018-Sep-16, at 1:50 PM, Jilles Tjoelker wrote: > On Sun, Sep 16, 2018 at 01:21:33PM -0700, Mark Millard wrote: >> On 2018-Sep-16, at 10:50 AM, Jilles Tjoelker wrote: > >>> On another note, the comment just below that, > >>> /* But we need to zero-extend (char is unsigned) the value and then >>> perform a signed 32-bit subtraction. */ > >>> shows a wrong reason for doing the right thing since memcmp (as well as >>> strcmp and strncmp) are defined to compare based on unsigned chars, >>> regardless of the signedness of char. > >> Ahh, standard are so much fun: there are so many to choose from. > >> I looked up ISO/IEC 9899:2011 (E) and its 7.24.4.1 "The memcmp function". >> It makes no such explicit claim about using using unsigned chars for >> the comparison standard: > >> QUOTE of the Description part: >> The memcmp function compares the first n characters of the object pointed >> by s1 to the first n characters of the object pointed by s2. >> END QUOTE > >> QUOTE of the Returns part: >> The memcmp function returns an integer greater than, equal to, or less >> than zero, accordingly as the object pointed to by s1 is greater than, >> equal to, or less than the object pointed to by s2. >> END QUOTE > >> If I had to guess the intent of "characters" would be based on the >> char type for C11. I did not find anything about the issue in the C99 >> rationale that I also happen to have available to look at. > > In C99, C11 and C17, the text about using unsigned chars is under > "Comparison functions" and it applies to memcmp, strcmp and strncmp > (which are documented together in the section). > >> For all I know, POSIX or other standards may be more explicit and not >> agree. > > POSIX does not document memcmp, strcmp and strncmp close together and > copies the text about using unsigned chars to each of them. This means > that it agrees with the C standards. > Thanks for noting the factored-out material in the C11 standard. Sorry for the noise of missing that factorization when I looked up memcmp. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun Sep 16 21:14: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 8626010808B5; Sun, 16 Sep 2018 21:14:59 +0000 (UTC) (envelope-from kp@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 3BF8881682; Sun, 16 Sep 2018 21:14:59 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) (Authenticated sender: kp) by smtp.freebsd.org (Postfix) with ESMTPSA id 1C6FE1B9CB; Sun, 16 Sep 2018 21:14:59 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from [172.28.128.1] (ptr-8rh08jyfxuybr5zu0sb.18120a2.ip6.access.telenet.be [IPv6:2a02:1811:240e:402:18d0:b636:eff9:67b]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id 96C8342367; Sun, 16 Sep 2018 23:14:56 +0200 (CEST) From: "Kristof Provost" To: "Eric van Gyzen" Cc: "Kurt Jaeger" , freebsd-current@freebsd.org, freebsd-net@freebsd.org Subject: Re: Bad DHCP Checksums over VLANs Date: Sun, 16 Sep 2018 23:14:55 +0200 X-Mailer: MailMate (2.0BETAr6121) Message-ID: <2D1D4467-2256-40C5-B69F-B9BDC7C7F7D6@FreeBSD.org> In-Reply-To: <794ae64b-54d8-cfde-2e9c-87b3b74e0516@vangyzen.net> References: <9dd3c7f9-d970-5d30-ebf2-c0f40c76011b@vangyzen.net> <20180915060615.GF2118@home.opsec.eu> <794ae64b-54d8-cfde-2e9c-87b3b74e0516@vangyzen.net> MIME-Version: 1.0 Content-Type: text/plain; format=flowed 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, 16 Sep 2018 21:14:59 -0000 On 16 Sep 2018, at 23:05, Eric van Gyzen wrote: > On 9/15/18 1:06 AM, Kurt Jaeger wrote: >> Can you disable all the options of the NIC ? >> >> ifconfig igb0 -rxcsum -txcsum -wol -tso4 -vlanmtu -vlanhwtag >> -vlanhwcsum -vlanhwtso >> >> Try to disable everything that can be disabled, e.g. LRO etc. > > Disabling vlanhwtag works around the problem. > > Also note that only DHCP traffic has this problem. If I assign an > address manually, all traffic flows normally. Maybe the problem is in > the BPF send path. > I had a similar issue, where -vlanhwtag also fixed it. That was on a I210 (gib) card (in a FreeNAS mini XL). Regards, Kristof From owner-freebsd-current@freebsd.org Sun Sep 16 21:15: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 23A49108096C for ; Sun, 16 Sep 2018 21:15: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 7FE088175D for ; Sun, 16 Sep 2018 21:15: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 w8GLFQtC049287 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 17 Sep 2018 00:15:29 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w8GLFQtC049287 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w8GLFPaJ049285; Mon, 17 Sep 2018 00:15:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 17 Sep 2018 00:15:25 +0300 From: Konstantin Belousov To: Manfred Antar Cc: freebsd-current , mjg@reebsd.org Subject: Re: Current-Alpha6 panic with new support.S AMD64 Message-ID: <20180916211525.GR3161@kib.kiev.ua> References: <10C66C40-045A-4555-8B47-189E5C1FEA13@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10C66C40-045A-4555-8B47-189E5C1FEA13@gmail.com> 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: Sun, 16 Sep 2018 21:15:37 -0000 On Sun, Sep 16, 2018 at 01:43:51PM -0700, Manfred Antar wrote: > With r338700 support.S i get panic after rebooting: > > avail memory = 16529514496 (15763 MB) > 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 100 > kernel trap 9 with interrupts disabled > > > Fatal trap 9: general protection fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xffffffff80747d86 > stack pointer = 0x28:0xffffffff82451820 > frame pointer = 0x28:0xffffffff82451820 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = resume, IOPL = 0 > current process = 0 () > [ thread pid 0 tid 0 ] > Stopped at strcmp+0x6: movb (%rsi),%dl > db> bt > Tracing pid 0 tid 0 td 0xffffffff81015180 > strcmp() at strcmp+0x6/frame 0xffffffff82451820 > sysctl_register_oid() at sysctl_register_oid+0x4c/frame 0xffffffff82451b40 > sysctl_add_oid() at sysctl_add_oid+0x20d/frame 0xffffffff82451b90 > et_register() at et_register+0x14d/frame 0xffffffff82451bf0 > native_lapic_init() at native_lapic_init+0x4e3/frame 0xffffffff82451c10 > madt_setup_local() at madt_setup_local+0x26e/frame 0xffffffff82451c40 > apic_setup_local() at apic_setup_local+0x44/frame 0xffffffff82451c50 > mi_startup() at mi_startup+0x118/frame 0xffffffff82451c70 > btext() at btext+0x2c > db> > > With support.S r338683 no problem What is your cpu ? Show first 50 lines from the verbose dmesg. Also please try this patch. diff --git a/sys/amd64/amd64/support.S b/sys/amd64/amd64/support.S index f86d3d11506..5a4e62faba1 100644 --- a/sys/amd64/amd64/support.S +++ b/sys/amd64/amd64/support.S @@ -122,7 +122,6 @@ ENTRY(memmove_std) movq %rdx,%rcx andq $7,%rcx /* any bytes left? */ jne 2f - movq %r9,%rax POP_FRAME_POINTER ret 2: From owner-freebsd-current@freebsd.org Sun Sep 16 22:30: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 58E631083549 for ; Sun, 16 Sep 2018 22:30:13 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 E18068357F for ; Sun, 16 Sep 2018 22:30:12 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id AC6DB34311 for ; Sun, 16 Sep 2018 16:30:46 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3zbv2jxIZkE3 for ; Sun, 16 Sep 2018 16:30:46 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA for ; Sun, 16 Sep 2018 16:30:46 -0600 (MDT) To: freebsd-current@freebsd.org From: Rebecca Cran Subject: FreeBSD EFI projects Message-ID: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> Date: Sun, 16 Sep 2018 16:30:10 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 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, 16 Sep 2018 22:30:13 -0000 I'm just getting back into FreeBSD development, and I'm trying to focus on (U)EFI work. It seems there are various things that people would like to have done, some of which are listed on https://wiki.freebsd.org/DevSummit/201806/HaveNeedWant12 - and some of which I know are already being worked on. Would a wiki page be useful for coordinating efforts and seeing who's working on what, or should tasks be tracked through bugzilla? -- Rebecca From owner-freebsd-current@freebsd.org Mon Sep 17 02:53:27 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 744F4108F15B for ; Mon, 17 Sep 2018 02:53:27 +0000 (UTC) (envelope-from doctorwhoguy@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::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 E90078ADA7 for ; Mon, 17 Sep 2018 02:53:26 +0000 (UTC) (envelope-from doctorwhoguy@gmail.com) Received: by mail-it0-x235.google.com with SMTP id h23-v6so9100754ita.5 for ; Sun, 16 Sep 2018 19:53:26 -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=GsM1xHeazDEPAua7CAdVMmJOpLeXgWm93uQTta23hhY=; b=va6QJOlFwyw9u7OamF+1IxHjSzQ71cpIy8VPlUG9895+SOKiDdijAEBga3Xn10NU0v dCxLvrfIWbXfHjswbsxbWzXXl4hwlqjgqB4l+utndpKL8hMi8u9gRmENwOBwWhauomq/ HVijcfUn1MCv7UNO3mbYeCWXkEMPoHRpscV1jhhVQYYnJfVGVmkOf9zpXXDPMTlxeNBO uz9nEVluS+uKsuzdGTeofibwGQbbk/nREccN13Cie6U8B60BKgr6wSNN6+g2esm4Moxt K3pn+cUieO4B+IundPQB19k6j+nsxUIxl4jU6zD5GamcQ+SFL7WIOCIkWStyHeAN4LZN NRqA== 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=GsM1xHeazDEPAua7CAdVMmJOpLeXgWm93uQTta23hhY=; b=p4x9vHy0NwKIDIhxEtr1q9nqPiEtmzo/ruB+JtAfEbW3PS0wJKWiHiQbko4IRFO+mj XAPJTsWr7Aayu8dA1EG8aeJoqgFbd5j4ZydZAQpEWKOBEJ1lTUQ9VgisImbSjP00yfzN qERZXAMj4Fp2eM/5pO3vsUFyvyzp5nGxaQ/6aX2Zx38t1T0ElPhVTEOU1mqOZuZYUoZn AG9SjfuEyHElTvwGvlQh7qK/7sIScCMH37u2McFuBKV63Sao/RKr7y3shOhgl3BtS/Z+ vxi4sci6rk6n2RJdq4lUjju1Rk0RSd84dzf5Pfk7lptpFBYj5y8hrhNxNmA3By3Zm2W7 9INg== X-Gm-Message-State: APzg51CE0pqVctMfVZvEUSrU9yLEBp80EMDDVxYwh+VM/NJ7t7ejfTeR Yafa8ABGiUrFS+LkJ/JnXxb1yYdwbW4vb/C8XdQtqw== X-Google-Smtp-Source: ANB0VdYqvUYk7ckwrMSjFSU9uFXoHR75bubF21vN39b+m6/u1vV4KdacdfKxYOd7A1b6HpggLwygZ1T6UbHv4LO62iw= X-Received: by 2002:a24:7dd5:: with SMTP id b204-v6mr11083754itc.96.1537152806005; Sun, 16 Sep 2018 19:53:26 -0700 (PDT) MIME-Version: 1.0 From: Patrick McMunn Date: Sun, 16 Sep 2018 21:53:12 -0500 Message-ID: Subject: FreeBSD-12-ALPHA6: Network not starting at boot & can't start Plasma 5 To: freebsd-current@freebsd.org 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: Mon, 17 Sep 2018 02:53:27 -0000 I was running a fresh installation of 11.2-stable for the past couple of weeks, and I decided to update from source to 12-current over the weekend. After upgrading and rebooting, my network was no longer starting at boot. It wouldn't work until I ran "service netif restart". Also, after updating I made sure to run "pkg update && pkg upgrade" to reinstall all my packages with ones compiled for FreeBSD 12. I restarted again and tried to log into Plasma 5 from sddm. The screen went black for a moment and immediately returned to the sddm login screen. I removed and reinstalled all packages on my system to see if maybe there was a stale config file left over or something. The login problem persisted. It worked fine under 11.2-stable Thinking perhaps I might have made a mistake in upgrading from source, I downloaded the 12-ALPHA6 snapshot, loaded it onto a USB stick, and did a fresh installaton. The problem with network not starting at boot persists. I haven't done a full install of Plasma 5 yet to test it again. From owner-freebsd-current@freebsd.org Mon Sep 17 03:33: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 D8DE8108FFDB for ; Mon, 17 Sep 2018 03:33:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::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 61EE28C308 for ; Mon, 17 Sep 2018 03:33:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x234.google.com with SMTP id p129-v6so9183189ite.3 for ; Sun, 16 Sep 2018 20:33:09 -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=5/i0plStpPLwPDb3Gdqs2cpFazvQ6LeUl4hkRQ/R2c4=; b=gHve3T+1hwk1iYrJorhMAOQasXP3tOFfP+QvmQMuZqp2Zf5EszNKWRy5n4A9ayadZE Y9PgzZLOaTkG0xyKqcVa2OJOsPDmSt674If3OIaJpXdMmk2S4nfBTh8jmNUAjnUkLlO0 jMc5lRsLjDjVjPvvkM2gK9RI5Gn+9izM77u6BFJScNF8hzqK1ApiMu7YTIGEth1cMYud kFt4mb1wMhQLRRFemoPnlfmN2EnWbW4KosBF4XeNaW01hd8FuJty/4Zhf+vTqMgEk1Hn sXyP+coaNIf+dKQTojwFOqd9YOjreDUp4IRdq34WEHZghMvGnvCr1nJVvjlcVPntX96M 7tGA== 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=5/i0plStpPLwPDb3Gdqs2cpFazvQ6LeUl4hkRQ/R2c4=; b=pRX901Fpr8hAVo4HirbPK4uZbMaj/9DMTOy1bLwwnbwJ+oCRI2W557wmx5afzJQkI4 5yT2HYPpQpgGDJn/iz7JVbq4DOwOYjuCqIfggFZ1eT+nHm+G+x7OZZa4Bm8N8py89RT5 SUc+bIGvRfxVNO7kHnGBigLzoDJDMwAugnBiaUiJnQxOXSO/6TMhVE840w5y6JyqF4dM 52wFFe3WIT8obt55qWYLFAkbUtZ3kuqtVr07ylewoEau/xX+bpZe9F8oUIMqJ8N7nC8f PTiVanyYgMrmbfLZtiAm+f1PO/1AFBE7+CJulN952tCbFRX3nZ/4srxDdJNVKAr+1iOB rP4Q== X-Gm-Message-State: APzg51ATtShKKCDBY8ixiOd4XP1KqxAaAOZ3MyzTgnhaP/K8jOZI3/M4 ZAplL5ft21ltfV7bSIX7fGrQDhHLmFVwWU5bXnLEiDz/ X-Google-Smtp-Source: ANB0VdYeJfnxQ73Y09xyJ8RFomJLBkkvYzliqdxz+aThUswnkh0fnL038pLdOyZ0I4CvbcdoFskR2yno8kiCFuQbtvk= X-Received: by 2002:a02:59cc:: with SMTP id v73-v6mr21252892jad.5.1537155188636; Sun, 16 Sep 2018 20:33:08 -0700 (PDT) MIME-Version: 1.0 References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> In-Reply-To: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> From: Warner Losh Date: Sun, 16 Sep 2018 21:32:57 -0600 Message-ID: Subject: Re: FreeBSD EFI projects To: rebecca@bluestop.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: Mon, 17 Sep 2018 03:33:10 -0000 On Sun, Sep 16, 2018 at 4:31 PM Rebecca Cran wrote: > I'm just getting back into FreeBSD development, and I'm trying to focus > on (U)EFI work. > > It seems there are various things that people would like to have done, > some of which are listed on > https://wiki.freebsd.org/DevSummit/201806/HaveNeedWant12 - and some of > which I know are already being worked on. > > Would a wiki page be useful for coordinating efforts and seeing who's > working on what, or should tasks be tracked through bugzilla? > Bugzilla is OK at individual tasks, but falls down when it comes to creating master bugs. You can do it, but only if you want a master list. It gets harder when you want to add metadata, imho. I much prefer a wiki page to track bigger picture things (though there's nothing wrong with creating a master bugzila bug if you want). That can also give the bigger context and have a richer set of design discussions + howtos than bugzilla would afford, ihmo. What did you have in mind working on? I have a few things that are in various stages of completeness around this issue that I've not had time to polish off for the tree. Some I'd like to, but some may benefit from a fresh perspective. Also, there's a fair number of hidden bugs in the stuff committed around finding the whole path sometimes and the like. Warner From owner-freebsd-current@freebsd.org Mon Sep 17 04:19: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 330A41090D59; Mon, 17 Sep 2018 04:19:01 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BCF068D3F8; Mon, 17 Sep 2018 04:19:00 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g1kzy-000IA4-Es; Mon, 17 Sep 2018 06:18:58 +0200 Date: Mon, 17 Sep 2018 06:18:58 +0200 From: Kurt Jaeger To: Kristof Provost Cc: Eric van Gyzen , Kurt Jaeger , freebsd-current@freebsd.org, freebsd-net@freebsd.org Subject: Re: Bad DHCP Checksums over VLANs Message-ID: <20180917041858.GH2118@home.opsec.eu> References: <9dd3c7f9-d970-5d30-ebf2-c0f40c76011b@vangyzen.net> <20180915060615.GF2118@home.opsec.eu> <794ae64b-54d8-cfde-2e9c-87b3b74e0516@vangyzen.net> <2D1D4467-2256-40C5-B69F-B9BDC7C7F7D6@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2D1D4467-2256-40C5-B69F-B9BDC7C7F7D6@FreeBSD.org> 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, 17 Sep 2018 04:19:01 -0000 Hi! > >> ifconfig igb0 -rxcsum -txcsum -wol -tso4 -vlanmtu -vlanhwtag > >> -vlanhwcsum -vlanhwtso > >> > >> Try to disable everything that can be disabled, e.g. LRO etc. > > > > Disabling vlanhwtag works around the problem. > > > > Also note that only DHCP traffic has this problem. If I assign an > > address manually, all traffic flows normally. Maybe the problem is in > > the BPF send path. > > > I had a similar issue, where -vlanhwtag also fixed it. > That was on a I210 (gib) card (in a FreeNAS mini XL). I've created a PR for this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231416 -- pi@FreeBSD.org +49 171 3101372 2 years to go ! From owner-freebsd-current@freebsd.org Mon Sep 17 05:29: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 B8CA710920BB for ; Mon, 17 Sep 2018 05:29:15 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 33D068ED0A for ; Mon, 17 Sep 2018 05:29:15 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id F2CD33447A; Sun, 16 Sep 2018 23:29:48 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 2cOb7w18eENc; Sun, 16 Sep 2018 23:29:48 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Sun, 16 Sep 2018 23:29:48 -0600 (MDT) From: Rebecca Cran Subject: FreeBSD EFI projects To: Warner Losh Cc: FreeBSD Current References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> Message-ID: <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> Date: Sun, 16 Sep 2018 23:29:12 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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: Mon, 17 Sep 2018 05:29:15 -0000 On 9/16/18 9:32 PM, Warner Losh wrote: > > What did you have in mind working on? I have a few things that are in > various stages of completeness around this issue that I've not had > time to polish off for the tree. Some I'd like to, but some may > benefit from a fresh perspective. Also, there's a fair number of > hidden bugs in the stuff committed around finding the whole path > sometimes and the like. One thing I've started working on is switching the ESP to use FAT32 everywhere except the ISO images (due to the limitation in the El Torito format not supporting sufficiently large regions). The specifications from EFI 1.10 onward have been clear that only FAT32 is supported for the ESP (but that FAT12 and FAT16 must be supported for removable devices), and I've read that some systems do enforce that. Unfortunately that does mean the ESP must be a minimum of 33MB, but I think it's worthwhile for increased compatibility. Related to that, I've also been working on removing the FAT filesystem templates that are currently checked into svn, instead generating them during the release stage. I've had some interest on #bsdmips about booting a 64-bit FreeBSD on old Apple systems that use 32-bit EFI: it sounds like it should be possible, and is something I'd like to try and get working. I'd also really like to help move the changes to mount an existing ESP during installation instead of clobbering it towards being committed, if possible. Another thing I'd like to work on is trying to catch corner cases like in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210244 where calling GetMemoryMap causes the memory map to become fragmented. I'd also like to try and improve diagnostics, for example at the moment if the system doesn't have enough memory to run the loader it silently exits instead of displaying an error message. And I would also be interested in taking a look at any projects you've not completed yet, to see if I can help in any way. -- Rebecca From owner-freebsd-current@freebsd.org Mon Sep 17 07:35: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 B93911094CCB for ; Mon, 17 Sep 2018 07:35:06 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from smh-06.1blu.de (smh-06.1blu.de [178.254.0.206]) (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 7ED8A71C91 for ; Mon, 17 Sep 2018 07:35:05 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [172.16.29.5] (helo=sh4-5.1blu.de) by smh-06.1blu.de with esmtp (Exim 4.86_2) (envelope-from ) id 1g1o3U-0000AS-44 for freebsd-current@freebsd.org; Mon, 17 Sep 2018 09:34:48 +0200 Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.86_2) (envelope-from ) id 1g1o3U-0002qO-18 for freebsd-current@freebsd.org; Mon, 17 Sep 2018 09:34:48 +0200 Date: Mon, 17 Sep 2018 09:34:47 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org Subject: updating my pordriere oven to latest CURRENT Message-ID: <20180917073447.GA8078@sh4-5.1blu.de> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.5.24 (2015-08-30) 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, 17 Sep 2018 07:35:06 -0000 Hello, I'm short before updating my poudriere oven, a Dell PowerEdge r210, from r318593 to r338641. I have there a ZFS in use for poudriere, created with: # zpool create poudriere /dev/da1 and set in /usr/local/etc/poudriere.conf: ZPOOL=poudriere ZROOTFS=/poudriere # zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT poudriere 278G 3.90G 274G - 13% 1% 1.00x ONLINE - # mount /dev/da0p2 on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) poudriere on /poudriere (zfs, local, nfsv4acls) poudriere/poudriere on /poudriere/poudriere (zfs, local, nfsv4acls) poudriere/poudriere/jails on /poudriere/poudriere/jails (zfs, local, nfsv4acls) ... Before running 'make installkernel' ... and later updating the poudriere tool itself from ports too, I wanted to ask if I have to take care about anything before. I've read src/UPDATING between the above mentioned versions and can't see anything, i.e. the zpool should be fine after the update too. Any comments on this? Thanks matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From owner-freebsd-current@freebsd.org Mon Sep 17 08:18: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 AF2D01095958 for ; Mon, 17 Sep 2018 08:18:19 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward106o.mail.yandex.net (forward106o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::609]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2166872C3B; Mon, 17 Sep 2018 08:18:18 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback9o.mail.yandex.net (mxback9o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::23]) by forward106o.mail.yandex.net (Yandex) with ESMTP id B919C7847DC; Mon, 17 Sep 2018 11:18:07 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback9o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 6GXPRHmZAg-I74Spk8g; Mon, 17 Sep 2018 11:18:07 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1537172287; bh=nHHSdKU8U29Msx/Hny9cB/8q/LB0VKCKO+YPQCbNnjw=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=Q0alod8CvCxIvhoDT02iM5mKwTfo3jwNrYCsGpTHBtwps8PMJCV8eDCmSDhLljGo8 5EuuAXs0A4XUNs2lwVVjS053/WUsEmC6+JomqxujGNdYd0MxcB54yJHXGH4eKW4JFQ CvSh99q7uJsYNoiiuMbdO73BGABMV4v5Vc6LUxr0= Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 2dzlgg7u9H-I5wOA0TV; Mon, 17 Sep 2018 11:18:05 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1537172285; bh=nHHSdKU8U29Msx/Hny9cB/8q/LB0VKCKO+YPQCbNnjw=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=LBlXhKrBzj4lcSgP04IimxCe6bXWIrEkMveLOWlmXB8MzSHMj/lv3pTaS5cvuePP3 LJTxbc9+Kgdf9ufqC3rJDmyUrSE0bSi7tg0rm9GyDjSfnas03yK9B78A2bIDVCv1Le uusksEnrEul4jxQK76OkzbR0KJ/NW5H2AghkipDM= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: udp6: Page fault panics To: freebsd-current@FreeBSD.org, "Bjoern A. Zeeb" , karels@FreeBSD.org, Matt Macy , rstone@freebsd.org References: <20180916000455.isqioezu6oovhjzg@ler-imac.local> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Autocrypt: addr=bu7cher@yandex.ru; prefer-encrypt=mutual; keydata= xsBNBEwBF1kBCADB9sXFhBEUy8qQ4X63Y8eBatYMHGEFWN9ypS5lI3RE6qQW2EYbxNk7qUC5 21YIIS1mMFVBEfvR7J9uc7yaYgFCEb6Sce1RSO4ULN2mRKGHP3/Sl0ijZEjWHV91hY1YTHEF ZW/0GYinDf56sYpDDehaBF5wkWIo1+QK5nmj3vl0DIDCMNd7QEiWpyLVwECgLX2eOAXByT8B bCqVhJGcG6iFP7/B9Ll6uX5gb8thM9LM+ibwErDBVDGiOgvfxqidab7fdkh893IBCXa82H9N CNwnEtcgzh+BSKK5BgvPohFMgRwjti37TSxwLu63QejRGbZWSz3OK3jMOoF63tCgn7FvABEB AAHNIkFuZHJleSBWLiBFbHN1a292IDxhZUBmcmVlYnNkLm9yZz7CwHsEEwECACUCGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheABQJMB/ruAhkBAAoJEAHF6gQQyKF6MLwH/3Ri/TZl9uo0 SepYWXOnxL6EaDVXDA+dLb1eLKC4PRBBjX29ttQ0KaWapiE6y5/AfzOPmRtHLrHYHjd/aiHX GMLHcYRXD+5GvdkK8iMALrZ28X0JXyuuZa8rAxWIWmCbYHNSBy2unqWgTI04Erodk90IALgM 9JeHN9sFqTM6zalrMnTzlcmel4kcjT3lyYw3vOKgoYLtsLhKZSbJoVVVlvRlGBpHFJI5AoYJ SyfXoN0rcX6k9X7Isp2K50YjqxV4v78xluh1puhwZyC0p8IShPrmrp9Oy9JkMX90o6UAXdGU KfdExJuGJfUZOFBTtNIMNIAKfMTjhpRhxONIr0emxxDOwE0ETAEXWQEIAJ2p6l9LBoqdH/0J PEFDY2t2gTvAuzz+8zs3R03dFuHcNbOwjvWCG0aOmVpAzkRa8egn5JB4sZaFUtKPYJEQ1Iu+ LUBwgvtXf4vWpzC67zs2dDuiW4LamH5p6xkTD61aHR7mCB3bg2TUjrDWn2Jt44cvoYxj3dz4 S49U1rc9ZPgD5axCNv45j72tggWlZvpefThP7xT1OlNTUqye2gAwQravXpZkl5JG4eOqJVIU X316iE3qso0iXRUtO7OseBf0PiVmk+wCahdreHOeOxK5jMhYkPKVn7z1sZiB7W2H2TojbmcK HZC22sz7Z/H36Lhg1+/RCnGzdEcjGc8oFHXHCxUAEQEAAcLAXwQYAQIACQUCTAEXWQIbDAAK CRABxeoEEMihegkYCAC3ivGYNe2taNm/4Nx5GPdzuaAJGKWksV+w9mo7dQvU+NmI2az5w8vw 98OmX7G0OV9snxMW+6cyNqBrVFTu33VVNzz9pnqNCHxGvj5dL5ltP160JV2zw2bUwJBYsgYQ WfyJJIM7l3gv5ZS3DGqaGIm9gOK1ANxfrR5PgPzvI9VxDhlr2juEVMZYAqPLEJe+SSxbwLoz BcFCNdDAyXcaAzXsx/E02YWm1hIWNRxanAe7Vlg7OL+gvLpdtrYCMg28PNqKNyrQ87LQ49O9 50IIZDOtNFeR0FGucjcLPdS9PiEqCoH7/waJxWp6ydJ+g4OYRBYNM0EmMgy1N85JJrV1mi5i Message-ID: Date: Mon, 17 Sep 2018 11:17:04 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180916000455.isqioezu6oovhjzg@ler-imac.local> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="p3mMtZH4M5KQgdvfcSJzhob0ntgxYDaJ3" 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, 17 Sep 2018 08:18:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --p3mMtZH4M5KQgdvfcSJzhob0ntgxYDaJ3 Content-Type: multipart/mixed; boundary="IPqMzjFczEhRHEmhJeYZ1EoyHUOziB9PK"; protected-headers="v1" From: "Andrey V. Elsukov" To: freebsd-current@FreeBSD.org, "Bjoern A. Zeeb" , karels@FreeBSD.org, Matt Macy , rstone@freebsd.org Message-ID: Subject: Re: udp6: Page fault panics References: <20180916000455.isqioezu6oovhjzg@ler-imac.local> In-Reply-To: <20180916000455.isqioezu6oovhjzg@ler-imac.local> --IPqMzjFczEhRHEmhJeYZ1EoyHUOziB9PK Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 16.09.2018 03:04, Larry Rosenman wrote: > vpanic() at vpanic+0x1a3/frame 0xfffffe00ca17c150 > panic() at panic+0x43/frame 0xfffffe00ca17c1b0 > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe00ca17c200 > trap_pfault() at trap_pfault+0x49/frame 0xfffffe00ca17c260 > trap() at trap+0x2ba/frame 0xfffffe00ca17c370 > calltrap() at calltrap+0x8/frame 0xfffffe00ca17c370 > --- trap 0xc, rip =3D 0xffffffff80631428, rsp =3D 0xfffffe00ca17c440, r= bp =3D 0xfffffe00ca17c480 --- > selectroute() at selectroute+0x198/frame 0xfffffe00ca17c480 > in6_selectroute_fib() at in6_selectroute_fib+0xf/frame 0xfffffe00ca17c4= a0 > ip6_output() at ip6_output+0xfd7/frame 0xfffffe00ca17c710 (kgdb) l *selectroute+0x198 0xffffffff80de14c8 is in selectroute (/home/devel/freebsd/base/head/sys/netinet6/in6_src.c:736). 731 * Use a cached route if it exists and is valid, else try to allocat= e 732 * a new one. Note that we should check the address family of the 733 * cached destination, in case of sharing the cache with IPv4. 734 */ 735 if (ro) { 736 if (ro->ro_rt && 737 (!(ro->ro_rt->rt_flags & RTF_UP) || 738 ((struct sockaddr *)(&ro->ro_dst))->sa_family !=3D AF_INET6 ||= 739 !IN6_ARE_ADDR_EQUAL(&satosin6(&ro->ro_dst)->sin6_addr, 740 dst))) { > calltrap() at calltrap+0x8/frame 0xfffffe00c9d863e0 > --- trap 0xc, rip =3D 0xffffffff80636b2b, rsp =3D 0xfffffe00c9d864b0, r= bp =3D 0xfffffe00c9d86710 --- > ip6_output() at ip6_output+0xeeb/frame 0xfffffe00c9d86710 > udp6_send() at udp6_send+0x720/frame 0xfffffe00c9d868d0 (kgdb) l *ip6_output+0xeeb 0xffffffff80de75bb is in ip6_output (/home/devel/freebsd/base/head/sys/netinet6/ip6_output.c:531). 526 */ 527 if (inp) { 528 ro->ro_dst.sin6_family =3D AF_INET6; 529 RT_VALIDATE((struct route *)ro, &inp->inp_rt_cookie, fibnum); 530 } 531 if (ro->ro_rt && fwd_tag =3D=3D NULL && (ro->ro_rt->rt_flags & RTF_U= P) && 532 ro->ro_dst.sin6_family =3D=3D AF_INET6 && 533 IN6_ARE_ADDR_EQUAL(&ro->ro_dst.sin6_addr, &ip6->ip6_dst)) { 534 rt =3D ro->ro_rt; 535 ifp =3D ro->ro_rt->rt_ifp; It looks like Ryan's assumption is correct and panics happen due to several threads use the same PCB and then route cache invalidation happen= s. https://lists.freebsd.org/pipermail/freebsd-net/2018-September/051563.htm= l But IPv6 path also needs similar patch. --=20 WBR, Andrey V. Elsukov --IPqMzjFczEhRHEmhJeYZ1EoyHUOziB9PK-- --p3mMtZH4M5KQgdvfcSJzhob0ntgxYDaJ3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlufYwAACgkQAcXqBBDI oXqjqQf6A1DsifgYufCZ3bT3UAqCzqShY5ZxFYVtAiBZ694c7p5MfWvz4W1+QYfW CRFRTuBzsqNazwhJNIfMRuuz51Wg8qpYtGd0F9LepLQiKwpAbL+Z4jQ4xVwiS2n/ qPuTmXwdW6kaC5sN8yibCheKI8Lc/Sz3tmK6rk4TkKtrCVhkiC0QfiR/GCDaOuM0 Qh4FSGyBxsOU+G2MDHsbSxGveljqWjCK6gpcPB7wTh+iRpbP9JuZA4WHxHiKbk2y sjQuoHwzZie6c2zebPCcb48fQ8gxk83kdhCoJXP1a0Z85OjhIhJbQVdOdiW2RWNk rWAXrh96UBlYZbHS0bVtcM4JsMon1g== =hL6Z -----END PGP SIGNATURE----- --p3mMtZH4M5KQgdvfcSJzhob0ntgxYDaJ3-- From owner-freebsd-current@freebsd.org Mon Sep 17 08:31: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 A01291095F88 for ; Mon, 17 Sep 2018 08:31:51 +0000 (UTC) (envelope-from dnebdal@gmail.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 397BE73445 for ; Mon, 17 Sep 2018 08:31:51 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id F2D4D1095F87; Mon, 17 Sep 2018 08:31:50 +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 D0D051095F83 for ; Mon, 17 Sep 2018 08:31:50 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: from mail-yb1-xb44.google.com (mail-yb1-xb44.google.com [IPv6:2607:f8b0:4864:20::b44]) (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 37E2B73437; Mon, 17 Sep 2018 08:31:50 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: by mail-yb1-xb44.google.com with SMTP id o63-v6so1727973yba.2; Mon, 17 Sep 2018 01:31:50 -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=01fp3VNrg8y6AwTkr84OIUCzELGxWV7hqSAr6E2wcz4=; b=VKMGdErM4TbZqKwP8qnBFLwoqB0ForzhU7V7xlyFaxVCI7v3+GLwkxhL77Xy3MUSWt V/Mlp1c27jw0xmqVzOpG4rk8b//wXoScCQtpUQWQTn8WmW+7vRsBDhbRXId4sk7OCYhB fn11i2dsqOOXqcMibbR1civOFM217mPwlAXy9DoJ0HtSSBQwxr9f0Yft2Y7YGjUA1NUs PMdOSsbelq54Zp8CBZ+ofSZhSW8Ez5gbJf96chsPdGqT3zhY2LjC/9kjwBiiqjDk1TnW eilLVe2r1W2JgnOBpWxYfOYdc4Fu+RJmeCfil4izvFOmWdgpiAiCLvbhxYPTalpk+4z5 Rk0A== 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=01fp3VNrg8y6AwTkr84OIUCzELGxWV7hqSAr6E2wcz4=; b=V2Egj5iSHYiujdIITqC0b4KTA7hqnr+fmxsJYvxn1Nkg7wowcdFdUy0H++ZUW/VJA5 7kKl5kOrW09x2qAPumsS6wJJHnzyds5si3ar5ncDp9YD4VOQS8H2jRw3s88DjdBQOSy2 L+UhUxeMmTvkbtfVIiC2oBGCVKRKkJ1kIGQmYNBfZiWl9L4xqmy/lPtKGwnkuS20KXWI daBzwVbvuflkhn3TO050IBL59M6r60hPsdpgOsyX/bG+TpBIVWH4XLoiUTyzIwIdneS1 +cbZ8z/tOXpQ3aNadiVedh0xKFhFFxaHVgzaWsLZA+OBCvBa7Ob2qd2RXgNJkBjoUHo2 MF5A== X-Gm-Message-State: APzg51DqN1cd8Ao39pR+yeyyC7qxNTZx/PnX+bPcDI9ECsk3/k1x/vKj N/bEbtAUbjHlf+pzLAQgXRHRGUm7OuhTIW2tfL4snQ== X-Google-Smtp-Source: ANB0VdZGCRRnEqY13jT9I7GBSfdkxKywaNzowHt2/lG23WLaPJpnbNjTYxC1PcFswZbJtslkAIXTz0JseuRfjgHd2zg= X-Received: by 2002:a5b:44b:: with SMTP id s11-v6mr9570589ybp.505.1537173109435; Mon, 17 Sep 2018 01:31:49 -0700 (PDT) MIME-Version: 1.0 References: <43892083.20180913024646@serebryakov.spb.ru> <7316152.20180913112742@serebryakov.spb.ru> <73a0934b-136f-785e-57bc-1f5624eea4fa@FreeBSD.org> <594107633.20180914031133@serebryakov.spb.ru> In-Reply-To: <594107633.20180914031133@serebryakov.spb.ru> From: Daniel Nebdal Date: Mon, 17 Sep 2018 09:40:13 +0200 Message-ID: Subject: Re: Speed problems with both system openssl and security/openssl-devel To: lev@freebsd.org Cc: John Baldwin , Kevin Oberman , current@freebsd.org, brnrd@freebsd.org, jkim@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: Mon, 17 Sep 2018 08:31:52 -0000 On Fri, 14 Sep 2018 at 02:12, Lev Serebryakov wrote: > > Hello John, > > Friday, September 14, 2018, 1:44:13 AM, you wrote: > > >> % grep aesni ~/nanobsd/gatevay.v3/J3160 > >> device aesni > > > From my understanding of the OpenSSL code, it doesn't use the kernel driver > > at all (the kernel driver is only needed for in-kernel crypto such as IPSec > > or GELI). > It is my understanding too. > > > AESNI are just instructions that can be used in userland, and > > OpenSSL's AESNI acceleration is purely different routines in userland. > > I would verify if AESNI shows up in the CPU features in dmesg first (if it > > doesn't I'd check for a BIOS option disabling it). > It is enabled. It is used for sure by openssl 1.1.0 on Linux and bu openssl 1.1.1 > on FreeBSD, but not by openssl 1.0.2 and 1.1.0 on FreeBSD. Problem is, > openssl 1.1.1 is not used by anything on FreeBSD (yet) and almost > everything uses system (1.0.2) and only some other ports could use 1.1.0 > from ports. > > -- > Best regards, > Lev mailto:lev@FreeBSD.org > Could it be relevant that the Debian binary was probably compiled with gcc, and the FreeBSD binary with clang? This seems like the sort of code that plausibly could bring out some compiler corner cases. (It's weird that 1.1.1 is fine, though.) -- Daniel Nebdal From owner-freebsd-current@freebsd.org Mon Sep 17 09:20: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 D02C8109735C for ; Mon, 17 Sep 2018 09:20:56 +0000 (UTC) (envelope-from aoh+freebsd-current@lysator.liu.se) 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 70DF374CD1 for ; Mon, 17 Sep 2018 09:20:56 +0000 (UTC) (envelope-from aoh+freebsd-current@lysator.liu.se) Received: by mailman.ysv.freebsd.org (Postfix) id 361F7109735B; Mon, 17 Sep 2018 09:20: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 140A3109735A for ; Mon, 17 Sep 2018 09:20:56 +0000 (UTC) (envelope-from aoh+freebsd-current@lysator.liu.se) Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) (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 8D68A74CCE for ; Mon, 17 Sep 2018 09:20:55 +0000 (UTC) (envelope-from aoh+freebsd-current@lysator.liu.se) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 125654002A for ; Mon, 17 Sep 2018 11:20:47 +0200 (CEST) Received: from slartibartfast.lysator.liu.se (slartibartfast.lysator.liu.se [IPv6:2001:6b0:17:f0a0::df]) by mail.lysator.liu.se (Postfix) with SMTP id ECED440024 for ; Mon, 17 Sep 2018 11:20:45 +0200 (CEST) Received: by slartibartfast.lysator.liu.se (sSMTP sendmail emulation); Mon, 17 Sep 2018 11:20:45 +0200 Date: Mon, 17 Sep 2018 11:20:45 +0200 From: Anton Haglund To: current@freebsd.org Subject: 12.0-ALPHA6-amd64-20180914-r338675 LOR? Message-ID: <20180917092045.GA16368@slartibartfast.lysator.liu.se> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline X-PGP-Key: https://www.lysator.liu.se/~aoh/pubkey.gpg.asc User-Agent: Mutt/1.5.24 (2015-08-30) X-Virus-Scanned: ClamAV using ClamSMTP 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, 17 Sep 2018 09:20:57 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I am trying out 12.0-ALPHA6-amd64-20180914-r338675 vmdk with a VM with two CPUs. When doing "shutdown -h now" I get a lock order reversal, is this expected? According to https://www.freebsd.org/doc/faq/troubleshoot.html#idp59076936 = it is possible to get false positives from witness. Attaching output: root@freebsd:~ # shutdown -h now shutdown -h now Shutdown NOW! Sep 17 11:05:04 Stopping cron. Waiting for PIDS: 676. Stopping devd. Waiting for PIDS: 420. Writing entropy file:. Writing early boot entropy file:. Terminated =2E Sep 17 11:05:05 freebsd syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `syncer' to stop...=20 Syncing disks, vnodes remaining... 2 0 done Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop... do= ne All buffers synced. lock order reversal: 1st 0xfffff80003702ba8 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1343 2nd 0xfffff80003703248 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2590 stack backtrace: #0 0xffffffff80bf4203 at witness_debugger+0x73 #1 0xffffffff80bf3f53 at witness_checkorder+0xab3 #2 0xffffffff80b60bea at lockmgr_lock_fast_path+0x17a #3 0xffffffff811df192 at VOP_LOCK1_APV+0xa2 #4 0xffffffff80c6eae0 at _vn_lock+0x60 #5 0xffffffff80c5d5ff at vget+0x5f #6 0xffffffff80a4646d at devfs_allocv+0xdd #7 0xffffffff80a45f73 at devfs_root+0x43 #8 0xffffffff80c5e09a at vflush+0x6a #9 0xffffffff80a45e73 at devfs_unmount+0x43 #10 0xffffffff80c55e45 at dounmount+0x515 #11 0xffffffff80c5f4d4 at vfs_unmountall+0xc4 #12 0xffffffff80c3bc05 at bufshutdown+0x2c5 #13 0xffffffff80b8bec8 at kern_reboot+0x218 #14 0xffffffff80b8bc59 at sys_reboot+0x3a9 #15 0xffffffff8105feec at amd64_syscall+0x28c #16 0xffffffff8103c65d at fast_syscall_common+0x101 Uptime: 1m0s The operating system has halted. Please press any key to reboot. BR, Anton Haglund --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJbn3HtAAoJEP8fn3mo5yjl+hsP/R+k1znz4HopuarCC+6/48Id YqjXBJlzIbpvEv5DUOTa4YMQ8I3oQtVxGBoY11wfXYMlULipEB/pkNMt9mY+HVS5 1yi4RT+/Dh1FSrxePUO7l1Qy+l6fN9a+Z6R/cGLpHG2v6NoMhQt1idFneCI0Bshd QMBfUAJTxLziInl0L/QNCo5YwZyPxyV78aCfwsJChLZKMQHxMnAu0BU8aCQ/SuHT 4yoe9OSru3AM1RvDio5L6lKBHndqN7weaa1xc1BSRkoyTwzJxPOXFPWh90Y9sHMF U3gTxrQGQ8JW/0Po0HCwU1DweeMwRm51bjOm1qmXlgPXO4l34cC3kUmXGgbi6cUy EY8lnGvbi3FKwZ5VkMUEhzcGgptMau1Rco2O2Pl6HGKMUk6Z9TRBvvI+g+akwYP9 fhdTv+kzQ/EbgWFjp0n8o5QnKMQDS5zN72if/iU9ws3TrGcy62J2kSsNfWr1ORST kYp6BZzSXKXEKnGQI9/Q5v+7pDnrn6em+U2xtdKAw6/gfvxDY9UvrHSGIZWPJhcA jvE4ezxxCDFak1UmzHYCYkGCYQB9ohtzNwVcT0ly43NvMFqUDsYl1GiSpJlMtvBg txIhX1Nmk3eWRTimTcPl6ttlL8QkZMzq9Vf0y/2pcsg8zbyeyzNoFTyr3y8hu5pb snyZaXtWqGmk2U34PCb6 =v8GE -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- From owner-freebsd-current@freebsd.org Mon Sep 17 09:21:45 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 2B365109755B for ; Mon, 17 Sep 2018 09:21:45 +0000 (UTC) (envelope-from lev@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 AA54574E0E for ; Mon, 17 Sep 2018 09:21:44 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6FD7A109755A; Mon, 17 Sep 2018 09:21:44 +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 4E0471097559 for ; Mon, 17 Sep 2018 09:21:44 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id C22AC74E09; Mon, 17 Sep 2018 09:21:43 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 885E4C14; Mon, 17 Sep 2018 12:21:36 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: Speed problems with both system openssl and security/openssl-devel To: Daniel Nebdal Cc: John Baldwin , Kevin Oberman , current@freebsd.org, brnrd@freebsd.org, jkim@freebsd.org References: <43892083.20180913024646@serebryakov.spb.ru> <7316152.20180913112742@serebryakov.spb.ru> <73a0934b-136f-785e-57bc-1f5624eea4fa@FreeBSD.org> <594107633.20180914031133@serebryakov.spb.ru> From: Lev Serebryakov Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: <31f8d0b9-ebda-92e5-80a2-efa1e8304c07@FreeBSD.org> Date: Mon, 17 Sep 2018 12:21:35 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; 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: Mon, 17 Sep 2018 09:21:45 -0000 On 17.09.2018 10:40, Daniel Nebdal wrote: > Could it be relevant that the Debian binary was probably compiled with > gcc, and the FreeBSD binary with clang? Maybe. Now I'm trying to trace codepath of "openssl speed -evp aes-256-cbc" on FreeBSD to understand where and why it refuses to use AES. No much luck, though, openssl sources are very convoluted :-( > This seems like the sort of code that plausibly could bring out some > compiler corner cases. (It's weird that 1.1.1 is fine, though.) -- // Lev Serebryakov From owner-freebsd-current@freebsd.org Mon Sep 17 12:27: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 925EE109BFAC; Mon, 17 Sep 2018 12:27:59 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id 0A9447A8CB; Mon, 17 Sep 2018 12:27:58 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id B4E06C6F; Mon, 17 Sep 2018 15:27:57 +0300 (MSK) Reply-To: lev@FreeBSD.org To: freebsd-net@freebsd.org, freebsd-current@freebsd.org From: Lev Serebryakov Subject: vtnet + gif (IPv4 in IPv4) + iperf3 leads to crash on ALPHA6 Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: Date: Mon, 17 Sep 2018 15:27:56 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US 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: Mon, 17 Sep 2018 12:27:59 -0000 I'm preparing some benchmarking setup, which includes gif tunnel from FreeBSD to FreeBSD, where one end is 12.0-ALPHA6/r338707 installed as guest in VirtualBox with virtual NIC (vtnet). This tunnel works for simple pings, but when I run iperf3 on this "link" ALPHA4 system crashes. It is 100% reproducible for me. panic: Assertion !in_epoch(net_epoch_preempt) && !mtx_owned(&(&(tcbinfo))->ipi_lock) failed at /data/src/sys/netinet/tcp_input.c:803 cpuid = 0 time = 1537187018 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe000044a310 vpanic() at vpanic+0x1a3/frame 0xfffffe000044a370 panic() at panic+0x43/frame 0xfffffe000044a3d0 tcp_input() at tcp_input+0x16a9/frame 0xfffffe000044a520 ip_input() at ip_input+0x126/frame 0xfffffe000044a5a0 netisr_dispatch_src() at netisr_dispatch_src+0x83/frame 0xfffffe000044a600 gif_input() at gif_input+0x2db/frame 0xfffffe000044a640 in_gif_input() at in_gif_input+0x73/frame 0xfffffe000044a680 encap_input() at encap_input+0x1cf/frame 0xfffffe000044a6f0 encap4_input() at encap4_input+0x28/frame 0xfffffe000044a720 ip_input() at ip_input+0x126/frame 0xfffffe000044a7a0 netisr_dispatch_src() at netisr_dispatch_src+0x83/frame 0xfffffe000044a800 ether_demux() at ether_demux+0x15e/frame 0xfffffe000044a830 ether_nh_input() at ether_nh_input+0x373/frame 0xfffffe000044a880 netisr_dispatch_src() at netisr_dispatch_src+0x83/frame 0xfffffe000044a8e0 ether_input() at ether_input+0x42/frame 0xfffffe000044a900 vtnet_rxq_eof() at vtnet_rxq_eof+0x736/frame 0xfffffe000044a9a0 vtnet_rx_vq_intr() at vtnet_rx_vq_intr+0x58/frame 0xfffffe000044a9d0 vtpci_legacy_intr() at vtpci_legacy_intr+0xb0/frame 0xfffffe000044aa10 ithread_loop() at ithread_loop+0x140/frame 0xfffffe000044aa70 fork_exit() at fork_exit+0x84/frame 0xfffffe000044aab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe000044aab0 -- // Lev Serebryakov From owner-freebsd-current@freebsd.org Mon Sep 17 18: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 6B7F310A3758 for ; Mon, 17 Sep 2018 18:17:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 03FF385E8F for ; Mon, 17 Sep 2018 18:17:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22b.google.com with SMTP id p129-v6so12202445ite.3 for ; Mon, 17 Sep 2018 11:17:37 -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=F6qEWEwg5E5Eq7VqQwyW2Rwh40kr+oNNb0iAedBRXcg=; b=KTLrcnjedoioyb13JfAyRmx4a4jO5LwKKcRsqmLxmNGQe+F9Bngay7yibQiFcx2GeO 5vONUIKQRYWlNX/+SyMa7OdDHKJQf2agXf8yspZzuhA0ycg5e5ACdXJ9H8qNwmbZsMmV 2f7W6/GKFXKp7reEOuxC3YUjT8CZkku+0RMugfYyM20FUwlzSDXd00vdWGV1UshP2KES 97LFkEPk8pqVILlmOCY0HSq4bPkCUifRjBhnWRVSm336qOTYI7/jEbYizar/RiNNVfmH I738xf2XogOj+MAQ1r1kofHjqu23REvdwIV2hSusTenn2y909w3MckGYLldyslBwVieN cFAg== 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=F6qEWEwg5E5Eq7VqQwyW2Rwh40kr+oNNb0iAedBRXcg=; b=cGoC6u86c0nQ9wsRSjwSPqmaXs7By6SSCe3z1BqF0+URQHWeGJzUSpUc5zY7iJM5kI hr2JEqSe/F7xjwGYSuH6rWK9zJJ2V70XnSIolrqQpT6bCZtbtNIAj3sVlHY4n92YPXMo iFpQYSOLzO4dFbpESXyVO/JBBV/9Xhn0qx1pAJQeZ/dZaER+OWtVBKzEmI0pzJCmIaaL hMkNPmubH5psb1m3HhnYWK3R9I2sLPaws5CJFY5BEvWwL1sYg+KNN2FsxgYjlYj8Laxh vzlXaU0JhuGpa+A7gUhVPGeeOAws3SybH59aV5W4lqoDOKAITcqSbI6gQxh45YWvknTP j4Aw== X-Gm-Message-State: APzg51Asp04CfLFgkluYMUtR38dQUmARsw1dBVa6MZNnThD2k9ZOO/hu 8I4U1FppsAVt7XYI8bHjYVy1tUZwRy5aZ/RuoVGYHObs X-Google-Smtp-Source: ANB0VdbkFYX/pjdKvY3t3HpoIvjnLMIP8/9Q+J3pZbUx/qYVK08QbetzmetucZN2fbWAo/BPBCaJXBFrLFhilVbU2n8= X-Received: by 2002:a24:9197:: with SMTP id i145-v6mr12816836ite.39.1537208257142; Mon, 17 Sep 2018 11:17:37 -0700 (PDT) MIME-Version: 1.0 References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> In-Reply-To: <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> From: Warner Losh Date: Mon, 17 Sep 2018 12:17:25 -0600 Message-ID: Subject: Re: FreeBSD EFI projects To: rebecca@bluestop.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: Mon, 17 Sep 2018 18:17:38 -0000 On Sun, Sep 16, 2018 at 11:29 PM Rebecca Cran wrote: > On 9/16/18 9:32 PM, Warner Losh wrote: > > > > > What did you have in mind working on? I have a few things that are in > > various stages of completeness around this issue that I've not had > > time to polish off for the tree. Some I'd like to, but some may > > benefit from a fresh perspective. Also, there's a fair number of > > hidden bugs in the stuff committed around finding the whole path > > sometimes and the like. > > > One thing I've started working on is switching the ESP to use FAT32 > everywhere except the ISO images (due to the limitation in the El Torito > format not supporting sufficiently large regions). The specifications > from EFI 1.10 onward have been clear that only FAT32 is supported for > the ESP (but that FAT12 and FAT16 must be supported for removable > devices), and I've read that some systems do enforce that. Unfortunately > that does mean the ESP must be a minimum of 33MB, but I think it's > worthwhile for increased compatibility. > I think this is a good change. We've seen issues with the tiny systems and FAT12 format, so we've switched to FAT16. But even with that, we're seeing some issues, so using FAT32 is great. > Related to that, I've also been working on removing the FAT filesystem > templates that are currently checked into svn, instead generating them > during the release stage. > I'd like to simply remove them entirely. They serve no useful purpose if we have an installer / script that can newfs + copy files. they were originally done so that we didn't have to change geom too much and could just DD something to a partition, which matched well the GPT boot code case. I've had some interest on #bsdmips about booting a 64-bit FreeBSD on old > Apple systems that use 32-bit EFI: it sounds like it should be possible, > and is something I'd like to try and get working. > That should be possible, but there's a number of issue dealing with the 32-bit EFI not having a direct map that we can use to generate the mapping tables we need for the loader early in our boot. It's why we can't call the EFI runtime on armv7, for example. > I'd also really like to help move the changes to mount an existing ESP > during installation instead of clobbering it towards being committed, if > possible. > Another very worthwhile project. > Another thing I'd like to work on is trying to catch corner cases like > in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210244 where > calling GetMemoryMap causes the memory map to become fragmented. I'd > also like to try and improve diagnostics, for example at the moment if > the system doesn't have enough memory to run the loader it silently > exits instead of displaying an error message. > That would be awesome. When things work today, they work. When they don't, it an be quite opaque to figure out, absent help from kib :). > And I would also be interested in taking a look at any projects you've > not completed yet, to see if I can help in any way. > Items on my list are: (1) Retiring boot1.efi entirely before 13.0. It was originally designed to be a small, never changing blob we'd toss into an ESP and have all the smarts in loader.efi. However, to support GELI encryption, ZFS, and other things, it's had to grow an increasingly frustrating amount of functionality. Better to just use loader.efi. This does, however, require that we solve the problem of updating loader.efi on installworld / freebsd-update times, even on systems with non-standard setups. Moving to a 'standard' setup for EFI would be a good first step, as well as having a script to do this both for when the ESP is mounted in a non-standard place, as well as for when it's not mounted. (2) Create a /dev/efi/boot for the drive/partition that we booted off of. This will allow us to have a standard fstab which is more resilient to oddities. NanoBSD could use this for it's ping-pong setup. I have some very basic code here, but it's more the stubs to add this to geom, and not so much on finding this information. Might be nice to also have a /dev/efi/esp to identify the ESP we booted off of as well to cope with systems that may have multiple potential ESP locations (at work we have this sort of setup for redundancy). (3) Add network interfaces to things that we know how to generate EFI DEVICE PATH entries for. I have some preliminary code that tries to match up the ifnet entries with a MAC DEVICE_PATH that I'd hoped to use to add netbooting support to efibootmgr. (4) Final integration of efibootmgr into the installer so we can generally install things robustly. Sadly, this has issues with some BIOSes not honoring BootOrder. I have no code, but have been working with nathanw@ on this. (5) For those systems that do honor BootOrder, having nextboot implemented using EFI variables would be sweet. I have vague ideas on this only. Warner From owner-freebsd-current@freebsd.org Mon Sep 17 18:32: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 2A83210A4033 for ; Mon, 17 Sep 2018 18:32:19 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (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 BF41B86A06; Mon, 17 Sep 2018 18:32:18 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1537209129; bh=rFv77Kv3 5zNIzxsmqUEewjKoQI/Fg83Y3EtqpkktYH4=; b=daHJ4i6w6jUeY/bK7WLCwN6u 7ZT75UGfW1TyCUNFBR/x1EASmrRiZ4ErDZI+ynEQEcBDTYta5M37jzs8z66h5Zbu dkX6Z5lATdpMaQo/4iRNyC87HDMBCpCRb219uH4sD4IsBLsyeNmclIE0+9OzR99A cZyeRcuXJnpCmoIcxVc= 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 475CD1CA7E; Mon, 17 Sep 2018 14:32:09 -0400 (EDT) Subject: Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted' To: John Baldwin , Konstantin Belousov Cc: Ian FREISLICH , freebsd-current References: <524214ac-e3ca-53cd-aee3-dac9212e9800@capeaugusta.com> <0aa35f96-9f62-bfca-c04a-f6ddcb1ce738@FreeBSD.org> <8ed7961e-e12a-9267-2bd0-a9bcbe383c7f@protected-networks.net> <20180831052805.GP2340@kib.kiev.ua> <04526140-c561-ae1c-cc0a-52bc8b4edb3c@protected-networks.net> <20180908194316.GI3161@kib.kiev.ua> <1918dda4-e9e5-a7bd-09e3-b3a70fcccd01@FreeBSD.org> From: Michael Butler Openpgp: preference=signencrypt Message-ID: Date: Mon, 17 Sep 2018 14:32:09 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <1918dda4-e9e5-a7bd-09e3-b3a70fcccd01@FreeBSD.org> 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: Mon, 17 Sep 2018 18:32:19 -0000 On 9/10/18 1:20 PM, John Baldwin wrote: > On 9/8/18 1:44 PM, Michael Butler wrote: >> On 9/8/18 3:43 PM, Konstantin Belousov wrote: >>> On Sat, Sep 08, 2018 at 02:07:41PM -0400, Michael Butler wrote: >>>> On 8/31/18 1:28 AM, Konstantin Belousov wrote: >>>>> On Fri, Aug 31, 2018 at 12:21:02AM -0400, Michael Butler wrote: >>>> >>>> [ .. snip .. ] >>>> >>>>>> I see another problem after using Ian's workaround of moving the #ifdef >>>>>> SMP; it seems I now run out of kernel stack on an i386 (Pentium-III) >>>>>> machine with only 512MB of RAM: >>>>>> >>>>>> Aug 29 23:29:19 sarah kernel: vm_thread_new: kstack allocation failed >>>>>> Aug 29 23:29:26 sarah kernel: vm_thread_new: kstack allocation failed >>>>>> Aug 29 23:29:30 sarah kernel: vm_thread_new: kstack allocation failed >>>>>> Aug 29 23:29:38 sarah kernel: vm_thread_new: kstack allocation failed >>>>>> Aug 29 23:29:38 sarah kernel: vm_thread_new: kstack allocation failed >>>>>> Aug 29 23:29:40 sarah kernel: vm_thread_new: kstack allocation failed >>>>> >>>>> What is the kernel revision for "now". What was the previous revision >>>>> where the kstack allocation failures did not happen. >>>>> >>>>> Also, what is the workload ? >>>> >>>> Sorry for the delay. Any version at or after SVN r338360 would either a) >>>> not boot at all or b) crash shortly after boot with a swarm of messages >>>> as above. It was stable before that. >>>> >>>> Unfortunately, this machine is remote and, being as old as it is, has no >>>> remote console facility. 'nextboot' has been my savior ;-) >>>> >>>> It is a 700MHz Pentium-III with 512MB of RAM and has 3 used interfaces, >>>> local ethernet (FXP), GIF for an IPv6 tunnel to HE and TAP for an >>>> OpenVPN endpoint. It has IPFW compiled into the kernel and acts as a >>>> router/firewall with few actual applications running. >>>> >>>> As another data point, I manually reversed both SVN r338360 and r338415 >>>> (a related change) and it is now stable running at SVN r338520, >>> >>> It is very unprobable. I do not see how could r338360 affect KVA allocation. >>> Double-check that you booted right kernels. >>> >> >> FreeBSD sarah.protected-networks.net 12.0-ALPHA5 FreeBSD 12.0-ALPHA5 #14 >> r338520M: Thu Sep 6 21:35:31 EDT 2018 >> >> 'svn diff' reports the only changes being the two reversals I noted above, > > Can you get the output of 'x num_io_irqs' at the DDB prompt after the > panic? > SVN r338725 fixed this - thanks! :-) imb From owner-freebsd-current@freebsd.org Mon Sep 17 18:43: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 E38CF10A44F4 for ; Mon, 17 Sep 2018 18:43:45 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (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 7FA9F871C7 for ; Mon, 17 Sep 2018 18:43:45 +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 E815610A87D; Mon, 17 Sep 2018 14:43:43 -0400 (EDT) Subject: Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted' To: Michael Butler , Konstantin Belousov References: <524214ac-e3ca-53cd-aee3-dac9212e9800@capeaugusta.com> <0aa35f96-9f62-bfca-c04a-f6ddcb1ce738@FreeBSD.org> <8ed7961e-e12a-9267-2bd0-a9bcbe383c7f@protected-networks.net> <20180831052805.GP2340@kib.kiev.ua> <04526140-c561-ae1c-cc0a-52bc8b4edb3c@protected-networks.net> <20180908194316.GI3161@kib.kiev.ua> <1918dda4-e9e5-a7bd-09e3-b3a70fcccd01@FreeBSD.org> Cc: Ian FREISLICH , freebsd-current From: John Baldwin Message-ID: <04dda74e-3b62-c4a1-0fed-9d2ceb7d5a7b@FreeBSD.org> Date: Mon, 17 Sep 2018 11:43:41 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; 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: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 17 Sep 2018 14:43:44 -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: Mon, 17 Sep 2018 18:43:46 -0000 On 9/17/18 11:32 AM, Michael Butler wrote: > On 9/10/18 1:20 PM, John Baldwin wrote: >> On 9/8/18 1:44 PM, Michael Butler wrote: >>> On 9/8/18 3:43 PM, Konstantin Belousov wrote: >>>> On Sat, Sep 08, 2018 at 02:07:41PM -0400, Michael Butler wrote: >>>>> On 8/31/18 1:28 AM, Konstantin Belousov wrote: >>>>>> On Fri, Aug 31, 2018 at 12:21:02AM -0400, Michael Butler wrote: >>>>> >>>>> [ .. snip .. ] >>>>> >>>>>>> I see another problem after using Ian's workaround of moving the #ifdef >>>>>>> SMP; it seems I now run out of kernel stack on an i386 (Pentium-III) >>>>>>> machine with only 512MB of RAM: >>>>>>> >>>>>>> Aug 29 23:29:19 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:26 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:30 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:38 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:38 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:40 sarah kernel: vm_thread_new: kstack allocation failed >>>>>> >>>>>> What is the kernel revision for "now". What was the previous revision >>>>>> where the kstack allocation failures did not happen. >>>>>> >>>>>> Also, what is the workload ? >>>>> >>>>> Sorry for the delay. Any version at or after SVN r338360 would either a) >>>>> not boot at all or b) crash shortly after boot with a swarm of messages >>>>> as above. It was stable before that. >>>>> >>>>> Unfortunately, this machine is remote and, being as old as it is, has no >>>>> remote console facility. 'nextboot' has been my savior ;-) >>>>> >>>>> It is a 700MHz Pentium-III with 512MB of RAM and has 3 used interfaces, >>>>> local ethernet (FXP), GIF for an IPv6 tunnel to HE and TAP for an >>>>> OpenVPN endpoint. It has IPFW compiled into the kernel and acts as a >>>>> router/firewall with few actual applications running. >>>>> >>>>> As another data point, I manually reversed both SVN r338360 and r338415 >>>>> (a related change) and it is now stable running at SVN r338520, >>>> >>>> It is very unprobable. I do not see how could r338360 affect KVA allocation. >>>> Double-check that you booted right kernels. >>>> >>> >>> FreeBSD sarah.protected-networks.net 12.0-ALPHA5 FreeBSD 12.0-ALPHA5 #14 >>> r338520M: Thu Sep 6 21:35:31 EDT 2018 >>> >>> 'svn diff' reports the only changes being the two reversals I noted above, >> >> Can you get the output of 'x num_io_irqs' at the DDB prompt after the >> panic? >> > > SVN r338725 fixed this - thanks! :-) Hmm, I'm not sure how that fixed this, but glad it is ok now. -- John Baldwin                                                                              From owner-freebsd-current@freebsd.org Mon Sep 17 20:09: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 91BA010A60A3 for ; Mon, 17 Sep 2018 20:09:55 +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 D94738AFF4 for ; Mon, 17 Sep 2018 20:09:54 +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 w8HK9ZLT080653 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 17 Sep 2018 23:09:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w8HK9ZLT080653 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w8HK9Z6R080652; Mon, 17 Sep 2018 23:09:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 17 Sep 2018 23:09:35 +0300 From: Konstantin Belousov To: Warner Losh Cc: rebecca@bluestop.org, FreeBSD Current Subject: Re: FreeBSD EFI projects Message-ID: <20180917200935.GD3161@kib.kiev.ua> References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.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: Mon, 17 Sep 2018 20:09:55 -0000 On Mon, Sep 17, 2018 at 12:17:25PM -0600, Warner Losh wrote: > On Sun, Sep 16, 2018 at 11:29 PM Rebecca Cran wrote: > I've had some interest on #bsdmips about booting a 64-bit FreeBSD on old > > Apple systems that use 32-bit EFI: it sounds like it should be possible, > > and is something I'd like to try and get working. > > > > That should be possible, but there's a number of issue dealing with the > 32-bit EFI not having a direct map that we can use to generate the mapping > tables we need for the loader early in our boot. It's why we can't call the > EFI runtime on armv7, for example. Having EFI RT working when 64bit kernel is booted from 32bit EFI environment is very non-trivial. DMAP is not an issue at all, loaders do not use or need it (in fact loaders run with the 1:1 mapping or disabled paging). RT requires calling into 32 bit mode from 64 bit. This is hard to do since kernel interrupt and fault handlers assume that kernel mode means flat 64bit. Interrupts would switch to 64 bit, but existing kernel code cannot handle such switch. Just do not provide RT for 32bit EFI. That said, making only the loader->kernel transition from EFI 32bit to 64bit kernel should be not too hard, and even significantly simpler than to make 32bit EFI load 32bit kernel. amd64 kernels already aware that there might be no BIOS and they do not try to make vm86 calls into real code, and only read memory map from the loader metadata etc. Besides old Macs, this should also benefit newer Intel embedded-like boards. From owner-freebsd-current@freebsd.org Mon Sep 17 20:34:44 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 DCE2610A6C68 for ; Mon, 17 Sep 2018 20:34:43 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 72DFD8C1E4 for ; Mon, 17 Sep 2018 20:34:43 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x230.google.com with SMTP id 139-v6so148250itf.0 for ; Mon, 17 Sep 2018 13:34:43 -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=A/Vvk97l/j+VrM1KgagWiKIF7T+RgHWKkdK2AyCF+nE=; b=WuY9Tnb0Y5+Zfrvi6lQkVwr51rnmDajeC8lDnwK7IiY7kzOZqTJ+occ6WubM3KIRGH /kseecuxxPj4QWkKTs6YxGMZvOLCxNn8UQck8NyVFn9W4Sn4cS42gPBRT3uO1zhvTn0U 5AFGcAyIyzyUekGTmMd0fJxC/zPOECjoZIY9UgthHIw6NaXWrW4YSA6ij8xxzEtr9IPZ 0Umi6DyGkAcAcLZR9s0pEVzpo7LVuG7jdSfGfVPBdzypY9dj76qJBDhTg0iI/FQiArSO l3w3OBS3ttvdtOZwe/iuhsbGa4tlCBGFR66BR+ZwiH4AGi1+7WleV/xiFddiL4K1/F6f jc3w== 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=A/Vvk97l/j+VrM1KgagWiKIF7T+RgHWKkdK2AyCF+nE=; b=Dv8mhXRMUY4wHjsKLLMSgKin2XlbNg/nXIxJctm2cTbRLT+loHhUbL+lNG7PYe2WoR jBLXhjv2Nndk4DDGLvy7emE6pY1ktNDcnptLCPeInZx1WTEnYgW7RhBjjT89XEdKxjyA 6wBFDgwhvFdmNIbjNKiQH5HOXcbEp/H2YgRwHEigvJUVqCYOLYie/9y1DKYL+NkIVFr+ MxWc7H/2diyrudiV5Kg/Cei8e2V4Jtwb2qMzObaH7KgOR6jDnXYis6T/VTTy3JlG9seE 5Z9R/GbotyUh4nYTyiJM8wSrHk2f3O9kXglmrVy2CJkWrY5BJuLMWYlznM8CRDkrip65 XqSQ== X-Gm-Message-State: APzg51D8fp8QU1ML9RshLZdHZJiy+ujL/xPPTVmTUtqMwXr5p8xoB/bS 0W7RZaTxKM57KZWzAzK1VEEyvSs3XRIfNUBUPfY= X-Google-Smtp-Source: ANB0VdbB9WFuxJERUtqN65jXsEbNLu0GMcKW5RbBD0IjpXHVv2kNUvd7hk9rpFRUB+aDaKEomxo2OmW0LdNDOlnpCCs= X-Received: by 2002:a24:728f:: with SMTP id x137-v6mr722458itc.40.1537216482850; Mon, 17 Sep 2018 13:34:42 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:404:0:0:0:0:0 with HTTP; Mon, 17 Sep 2018 13:34:22 -0700 (PDT) In-Reply-To: References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> From: Ed Maste Date: Mon, 17 Sep 2018 16:34:22 -0400 X-Google-Sender-Auth: T0qMniqOyoXauhgNNH-S8Gu_TXI Message-ID: Subject: Re: FreeBSD EFI projects To: Warner Losh Cc: Rebecca Cran , 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: Mon, 17 Sep 2018 20:34:44 -0000 On 17 September 2018 at 14:17, Warner Losh wrote: > Items on my list are: > > (1) Retiring boot1.efi entirely before 13.0. It was originally designed to > be a small, never changing blob we'd toss into an ESP and have all the > smarts in loader.efi. I'd go further than this: it was originally designed as a stopgap to have FreeBSD work in an EFI world when we didn't support the standard UEFI interfaces and did not have a straightforward way for loader.efi to find its script/configuration files in a different partition or filesystem. As far as I recall it was never intended to be a permanent part of the UEFI boot process. We'll probably reacquire a small first-stage UEFI boot component: the UEFI Secure Boot shim loader. But it can load loader.efi from the ESP and won't be used outside of Secure Boot configurations. > Moving to a > 'standard' setup for EFI would be a good first step, as well as having a > script to do this both for when the ESP is mounted in a non-standard place, > as well as for when it's not mounted. I'm not sure how far we have to go in catering to non-standard configurations. I completely agree we should have a standard EFI configuration and should support seamless upgrades in that configuration. For other cases I'd personally just ensure we've fully documented the components and processes. From owner-freebsd-current@freebsd.org Mon Sep 17 20:52: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 107C210A74C3 for ; Mon, 17 Sep 2018 20:52:24 +0000 (UTC) (envelope-from lev@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 8D6658CD06 for ; Mon, 17 Sep 2018 20:52:23 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5141510A74C2; Mon, 17 Sep 2018 20:52:23 +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 3FF3510A74C1 for ; Mon, 17 Sep 2018 20:52:23 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id D28FB8CD00; Mon, 17 Sep 2018 20:52:22 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:dcf4:3d3c:7e78:129b]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 23601CE8; Mon, 17 Sep 2018 23:52:21 +0300 (MSK) Date: Mon, 17 Sep 2018 23:52:20 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD Message-ID: <468346531.20180917235220@serebryakov.spb.ru> To: current@FreeBSD.org CC: brnrd@FreeBSD.org, jkim@FreeBSD.org Subject: Re: Speed problems with both system openssl and security/openssl-devel In-Reply-To: <43892083.20180913024646@serebryakov.spb.ru> References: <43892083.20180913024646@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Mon, 17 Sep 2018 20:52:24 -0000 Hello Lev, Thursday, September 13, 2018, 2:46:46 AM, you wrote: > Linux have openssl 1.1.0f, and I've tried both system /usr/bin/openssl (1.0.2p) > and /usr/local/bin/openssl from security/openssl-devel port (1.1.0i), results are > virtually the same. I have "ASM" and "SSE2" options enabled in port. > What happens here? Why does FreeBSD's build of openssl use AES-NI so > inefficient? More datapoints. (1) aes-256-cbc behaves really wired. Time output is completely bogus without "-elapsed" and speed is unbelievably low with "-elapsed". aes-256-gcm doesn't have this anomaly without "-elapsed" (please note "in 0.xxs" here): Doing aes-256-cbc for 3s on 16 size blocks: 503555 aes-256-cbc's in 0.60s Doing aes-256-cbc for 3s on 64 size blocks: 520386 aes-256-cbc's in 0.54s Doing aes-256-cbc for 3s on 256 size blocks: 435106 aes-256-cbc's in 0.44s Doing aes-256-cbc for 3s on 1024 size blocks: 242832 aes-256-cbc's in 0.38s Doing aes-256-cbc for 3s on 8192 size blocks: 49087 aes-256-cbc's in 0.09s ... aes-256-cbc 13393.26k 61782.64k 254599.17k 663093.25k 4289287.51k Doing aes-256-gcm for 3s on 16 size blocks: 12051311 aes-256-gcm's in 3.03s Doing aes-256-gcm for 3s on 64 size blocks: 6428598 aes-256-gcm's in 3.04s Doing aes-256-gcm for 3s on 256 size blocks: 2122316 aes-256-gcm's in 3.00s Doing aes-256-gcm for 3s on 1024 size blocks: 610443 aes-256-gcm's in 3.13s Doing aes-256-gcm for 3s on 8192 size blocks: 75836 aes-256-gcm's in 3.03s ... aes-256-gcm 63611.04k 135380.66k 181104.30k 199531.13k 204947.96k with "-elapsed": Doing aes-256-cbc for 3s on 16 size blocks: 493829 aes-256-cbc's in 3.01s Doing aes-256-cbc for 3s on 64 size blocks: 530550 aes-256-cbc's in 3.06s Doing aes-256-cbc for 3s on 256 size blocks: 426699 aes-256-cbc's in 3.01s Doing aes-256-cbc for 3s on 1024 size blocks: 243305 aes-256-cbc's in 3.03s Doing aes-256-cbc for 3s on 8192 size blocks: 48069 aes-256-cbc's in 3.01s ... aes-256-cbc 2626.91k 11087.41k 36317.07k 82191.94k 130919.48k Doing aes-256-gcm for 3s on 16 size blocks: 12041385 aes-256-gcm's in 3.08s Doing aes-256-gcm for 3s on 64 size blocks: 6445757 aes-256-gcm's in 3.05s Doing aes-256-gcm for 3s on 256 size blocks: 2129499 aes-256-gcm's in 3.01s Doing aes-256-gcm for 3s on 1024 size blocks: 587396 aes-256-gcm's in 3.01s Doing aes-256-gcm for 3s on 8192 size blocks: 75806 aes-256-gcm's in 3.03s ... aes-256-gcm 62590.75k 135047.68k 181245.26k 199977.06k 204866.89k (2) I've added debug output to 'crypto/evp/e_aes.c' and it shows, that AES-NIU should be used. (3) openssl111 from ports doesn't show these problems. -- Best regards, Lev mailto:lev@FreeBSD.org From owner-freebsd-current@freebsd.org Tue Sep 18 08:17: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 156D11096FEE for ; Tue, 18 Sep 2018 08:17:46 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 7D79E8414E for ; Tue, 18 Sep 2018 08:17:45 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm1-x336.google.com with SMTP id t25-v6so1580499wmi.3 for ; Tue, 18 Sep 2018 01:17:45 -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=qxEzZga+x6ja1iV1i6VdlTZCIZcWEaM03FR/PefPm58=; b=OP2xY8QjhtrzbO+bJQGububQlg5GMiN8LakBsEy4C9RSavTVmnL7U0+BF/x36uUs7f ynpvSWx/oW2TV77Sy3TxxB7DtBHohO9uTHw5jNSvZ7fAdS1Xsw9VCPMJsYMoOHSr7WwD TPf8bPcoht6zWdomQHGWcaiaP3hgZe4dcpq7CFzigwk7kmRBK1FFJ7+XeqVwM7zWYw8R 27CKfaHjmjQJtYW8piwEar7d6EVCX/9X4jVbI/L0FORp8FPksFzxlaew8JFAPtMunJDS 1rr59xKWGK7AmFpcd+hr4g/jOWCGbMoEzotmBamhIhLXAHJc0OBgDAuLvsz87h70hdqY AGqg== 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=qxEzZga+x6ja1iV1i6VdlTZCIZcWEaM03FR/PefPm58=; b=POqZMIoc85YCGa7kW6Y+VOhYXL/vhsKVfupocUTarYZNNrcq4zj5d5kGXx1DGh3sSu d/Vyhr0D+RbmZqODcpd6eyizA9KS8rs7rJrfTt1tLCTDoW+0O2UySyqVzmDKGLyGJIj3 nlpo7WsjHtV8d0LF9PTHM3MiKEeMjgQ3kwYDsZLQ1Y0X+Hj0rSq0tttfxKm0F/rZKTS2 nnShpfP/RChbFoZ6jhSRwO115A3vAgezfn26/Y/lxUT+/Fpl7S9xGIb1/P7J8Co9IfF9 nNEaxpdNVwp5zhj5f7uZ8FLlVjZSsjwv5JQcf6/Xq9gmyug7Q0k/c+r6euHV8FtMBmga IPqQ== X-Gm-Message-State: APzg51Bht5B+kbOmalM9Wtpn3FS5Reg+eXtwff8glt2/X6pcxbR/YSVc uIkh4nzaj760FEM20KhQpd7tuLBAU82aZQjTk3/AlAH5 X-Google-Smtp-Source: ANB0VdZDtvWgEw9clj0+SpT/5JY+BILtAUyqPLVQEam8AU2etSGoE0QI7Z673YPCYWiSixIUKLHoW1eIh5LSAlIX7vY= X-Received: by 2002:a1c:7412:: with SMTP id p18-v6mr14754026wmc.49.1537258663796; Tue, 18 Sep 2018 01:17:43 -0700 (PDT) MIME-Version: 1.0 From: Johannes Lundberg Date: Tue, 18 Sep 2018 09:17:07 +0100 Message-ID: Subject: usb rtwn not loaded properly at boot 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: Tue, 18 Sep 2018 08:17:46 -0000 Hi I have (with 12-ALPHA5) /boot/loader.conf rtwn_load="YES" if_urtw_usb_load="YES" /etc/rc.conf wlans_rtwn0="wlan0" ifconfig_wlan0="WPA DHCP" but still after boot only lo0 exists and all modules are loaded. Manually running ifconfig wlan0 create wlandev rtwn0 sets up the interface correctly. In my kernel config I have MODULES_OVERRIDE="....usb rtwn_usb rtwn ...." I'm pretty sure this has worked before... Any clues? From owner-freebsd-current@freebsd.org Tue Sep 18 08:27: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 797B6109751C for ; Tue, 18 Sep 2018 08:27:19 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.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 0C73784822 for ; Tue, 18 Sep 2018 08:27:18 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id F215C507; Tue, 18 Sep 2018 04:27:11 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 18 Sep 2018 04:27:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=CzPlWQyaN/JFy59v/3rmTS9uXJeQT 2IjwEDaZ9PemIY=; b=G39fTYEZWrzufgYp+Apf2gW0m4N0BBSv/qiExRIG89yAy 1ahcdbkkw/Z879UaDR86TlvDoe9eQHbpUffTcHYhOfs6Jdf3h0PmQfZVfl8PYiWG G4+RuPUk7fv14pAmoDNjVtRDd0sI/qnLQ5PHjQA7tS2aBONbYvpjcCWgLmSmyTq0 GOL1vAYXqRCFC/ZcSEZR/MVz95xDBe49qql7xdrXMhjWwo2ZzJVSoQ7RkNlNVvMw XaBBZxTdVvpF+vJRMQ1USkhGqLGIdKxK7wqWrfi2pyacWS26F9vniBUAXh3nQzRT 7L0Jx2opNYfJFj4JVLuUb+AAo0zL0d/Z56GGxQ4Ng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=CzPlWQ yaN/JFy59v/3rmTS9uXJeQT2IjwEDaZ9PemIY=; b=ipnmXPz0jJIBx892ZL6TJs pd1PXHct+UJbsbt/jUTacZha87PbiU/mjZqbGPxPHIUoQRD6cd74rWqZDwh/dLp/ GMDSrCf4DZbrFYYx+sojPe82dis2Z4OKZLIBYFVIeicvDldbrFuQ24rafPGl5JHA pgx3ZqURMj62OnHyXMCnETZCzTjQJ5Ps9fj7vY2Bz0AZCVXKD9aFeTHEMTPGBTSi 5cVuZcgJZeF8fsPInmTCMN8Pyaom8V1ooxiETPvDFwiOaPclogXA/ezXcNsmnPTq 63e/fjkIRBte0jjvv8mWTFRQhXlHUq4V8FTotxr1C1HOB3olv8JLh0KoQw/XxJTw == X-ME-Proxy: X-ME-Sender: Received: from odin.yuripv.net (unknown [62.183.127.178]) by mail.messagingengine.com (Postfix) with ESMTPA id A60A9102D6; Tue, 18 Sep 2018 04:27:10 -0400 (EDT) Subject: Re: usb rtwn not loaded properly at boot To: Johannes Lundberg , freebsd-current References: From: Yuri Pankov Message-ID: Date: Tue, 18 Sep 2018 11:27:08 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-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, 18 Sep 2018 08:27:19 -0000 Johannes Lundberg wrote: > Hi > > I have (with 12-ALPHA5) > > /boot/loader.conf > rtwn_load="YES" > if_urtw_usb_load="YES" rtwn(4) thinks this should be if_rtwn_usb_load="YES". > /etc/rc.conf > wlans_rtwn0="wlan0" > ifconfig_wlan0="WPA DHCP" > > but still after boot only lo0 exists and all modules are loaded. > > Manually running > ifconfig wlan0 create wlandev rtwn0 > sets up the interface correctly. > > In my kernel config I have > MODULES_OVERRIDE="....usb rtwn_usb rtwn ...." > > I'm pretty sure this has worked before... Any clues? From owner-freebsd-current@freebsd.org Tue Sep 18 08:33: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 7C8DA1097988 for ; Tue, 18 Sep 2018 08:33:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 EE86384E93 for ; Tue, 18 Sep 2018 08:33:21 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm1-x330.google.com with SMTP id t25-v6so1639376wmi.3 for ; Tue, 18 Sep 2018 01:33:21 -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=yI2XSR1WOEXElvyk+8xIDQ6eaWmVqdDT34U76veVjYA=; b=Q1xXr+9iFjZPBRIRdAM2aPTcMhevfVYCA7agMEL/7u9U6pok1prka8u0NzcSXiMedy 0p0yLXUdSTFHxrPskURwm9Buy8THhql6BHKNWzF2NXYve//6gzvpJA3SpL7HirG/yccn 3pqdQblvtMTYZSp2HvQAhiXq0QGIrug6eQcpHxGjTOR4BDPgLW4Bf8/dhwRiCfkGJ+uV IlX7vsQpBx8QLobABZlG+wEjmGJW5BrWBBj8h8V76GhVaOe6JLa6SD3eawLzblI3jGo1 +CVnWRgsJGHIfjUPu716pbxJD2lz9czQCEczqmKo1qsyEWP+qAQZggmlFinmj7Qjzbf5 fu3Q== 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=yI2XSR1WOEXElvyk+8xIDQ6eaWmVqdDT34U76veVjYA=; b=V4cftAD02Y57beXDy09dLczKf65dXrfKzGBBXIiYoqtRw9d1n4XmRGUanX9CmVkLYX sz+1YZ/aEPXEzfHYT/yF57HC/q1x8+RXK8ELH1EpoE6D21MMtmbVy+BgocBiTt5ULaDk m7fUGLEfdMUNLjjlUNFLJoqlNT93Ff5zojRoZaVByqAej0yjlRFvLoM3W0WJ/rkZwP8h BfwOuV/g6taeS9IJ3YPkQoTL5xXYZDKRpM4Jx+yw4uS93AZj+VYFhjY/0kxyNYMZxfE5 naN4whJyHFCO/qQQvxcA4uJ9WWnf9zywGfTSYIpcjNYKofMcpglxf+7O2BPo3HkMqJ0D NMTg== X-Gm-Message-State: APzg51D40veabO4o0pf9Mw4eSuiMHZw77XOocw0q1b39Y3IxH2//45o6 OEnsk+A1+y3ZLw0jwnjlokd5euLPBIPgDhtmkZJPlw== X-Google-Smtp-Source: ANB0Vdbj7nbAkxqD+dgKPhXtBmwzgEO0bTjAZ4mMxkn5bRVss6vld5qtNmF8C+etntQlwenCH+mnTk7+Tjuw58JAa4w= X-Received: by 2002:a1c:7412:: with SMTP id p18-v6mr14808186wmc.49.1537259600714; Tue, 18 Sep 2018 01:33:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Tue, 18 Sep 2018 09:32:43 +0100 Message-ID: Subject: Re: usb rtwn not loaded properly at boot To: yuripv@yuripv.net 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: Tue, 18 Sep 2018 08:33:22 -0000 On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: > Johannes Lundberg wrote: > > Hi > > > > I have (with 12-ALPHA5) > > > > /boot/loader.conf > > rtwn_load="YES" > > if_urtw_usb_load="YES" > > rtwn(4) thinks this should be if_rtwn_usb_load="YES". > Ah yes. Sorry about that. I still suffer confusion from the rename. Still, it doesn't change anything since if_rtwn_usb was loaded anyway. > > /etc/rc.conf > > wlans_rtwn0="wlan0" > > ifconfig_wlan0="WPA DHCP" > > > > but still after boot only lo0 exists and all modules are loaded. > > > > Manually running > > ifconfig wlan0 create wlandev rtwn0 > > sets up the interface correctly. > > > > In my kernel config I have > > MODULES_OVERRIDE="....usb rtwn_usb rtwn ...." > > > > I'm pretty sure this has worked before... Any clues? > From owner-freebsd-current@freebsd.org Tue Sep 18 08:39: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 788501097C27 for ; Tue, 18 Sep 2018 08:39:40 +0000 (UTC) (envelope-from danny@mail.hebrew.edu) Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 DF52E852B6 for ; Tue, 18 Sep 2018 08:39:39 +0000 (UTC) (envelope-from danny@mail.hebrew.edu) Received: by mail-wr1-x435.google.com with SMTP id v90-v6so1132830wrc.0 for ; Tue, 18 Sep 2018 01:39:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mail-hebrew-edu.20150623.gappssmtp.com; s=20150623; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vLjtaIUxvDhTlc/sG4hwugZxZmwAmbmu6iouN7JrG0o=; b=XEFxcmcLS29cwXDrbntv8QSIqAPSDeqkrgadjB5D3CSh81tz5SnKgm1nwLuz7YGmur QBSyevYmDFp0VuN7/A6XfZ1AiUIZe9iCPjbiePYM92lo3yGVQW6qt5xRRBAbwqVv1mj1 K7KV87Er0rFbu7O7qGqLCIX4MjfmKftAC6vXOCrvnEBc9UhoybzByrkQLfBC/kDf/xJS U3z/x/9LU5CL2kfGWzqfGRGaw69WZJ/oIfFUafgHIunrJ2tRs+He+yi8rvwrxy1nhbs9 JE4pl599803z4AjhKoCL24by0R1bPzf3x+Cv4wyvZbLYGmG5/Yr3vjhHynHe8/2q5XNM HBcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=vLjtaIUxvDhTlc/sG4hwugZxZmwAmbmu6iouN7JrG0o=; b=TV5y7purJpne/nW43KUaayAAEDmDxpF9pEaw52+7O4Hj2ldn6oHsc6JWqG0/DRkmcx cFFO7RQ9fCxScIRwHCPZqABivKWaj36HcZGNjgirCGp5vR2F6p4ZJhXkKvHL22pQL7+3 sX4pE0eiTrO9vWeQVflMJvXgUrC08L241h8C0i0kRSuRLJHYJPodBf61WooaKw8FRdEw fyEtgIiQfiVGvVH0TXz8JP99rdPBRVmQtNwqkQMEWJRYyN/MxngrIFXS5+w2DMfEtx4A jYnDNu3i5jkM6Fj5AXe/VZx78a90FN0lmApbDjnAy31ZD2YvGK7562O8e0lrDTu7/o8L y9Pw== X-Gm-Message-State: APzg51AYG3hoCNpFO2k2CjlA1yFve7FYPOoII4QaUDIlaWWDABRnvlo3 hjqkiMgjfERUaY/M77A7xOxM1g== X-Google-Smtp-Source: ANB0Vdb8It2MD+BY8sQDpcp+QHzxS3wjdAbFwN4nDhbkW9pbqAvsNovs0rLCbrNn8KMpkZgIAUZrDQ== X-Received: by 2002:a5d:488c:: with SMTP id g12-v6mr23188687wrq.0.1537259977996; Tue, 18 Sep 2018 01:39:37 -0700 (PDT) Received: from [192.168.1.128] (77.119.131.75.wireless.dyn.drei.com. [77.119.131.75]) by smtp.gmail.com with ESMTPSA id b124-v6sm997895wmg.47.2018.09.18.01.39.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Sep 2018 01:39:36 -0700 (PDT) Sender: Danny Braniss Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: usb rtwn not loaded properly at boot From: Daniel Braniss In-Reply-To: Date: Tue, 18 Sep 2018 10:39:32 +0200 Cc: yuripv@yuripv.net, freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: <4309D3E5-A2C2-450E-8C35-D3603E4A6080@cs.huji.ac.il> References: To: Johannes Lundberg X-Mailer: Apple Mail (2.3445.100.39) 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, 18 Sep 2018 08:39:40 -0000 > On 18 Sep 2018, at 10:32, Johannes Lundberg = wrote: >=20 > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: >=20 >> Johannes Lundberg wrote: >>> Hi >>>=20 >>> I have (with 12-ALPHA5) >>>=20 >>> /boot/loader.conf >>> rtwn_load=3D"YES" >>> if_urtw_usb_load=3D"YES" >>=20 >> rtwn(4) thinks this should be if_rtwn_usb_load=3D"YES". >>=20 >=20 > Ah yes. Sorry about that. I still suffer confusion from the rename. > Still, it doesn't change anything since if_rtwn_usb was loaded anyway. >=20 >=20 >>> /etc/rc.conf >>> wlans_rtwn0=3D"wlan0" >>> ifconfig_wlan0=3D"WPA DHCP" >>>=20 >>> but still after boot only lo0 exists and all modules are loaded. >>>=20 >>> Manually running >>> ifconfig wlan0 create wlandev rtwn0 >>> sets up the interface correctly. >>>=20 >>> In my kernel config I have >>> MODULES_OVERRIDE=3D"....usb rtwn_usb rtwn ...." >>>=20 >>> I'm pretty sure this has worked before... Any clues? >>=20 devd is not calling netif! try running =E2=80=99service netif start=E2=80=99 and see what happens. danny > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Tue Sep 18 08:41: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 140D21097CE1 for ; Tue, 18 Sep 2018 08:41:22 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.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 A246C856BC for ; Tue, 18 Sep 2018 08:41:21 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 8AEC84C1; Tue, 18 Sep 2018 04:41:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 18 Sep 2018 04:41:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=LkuWNomxIJwgZkLU5CyDsUEKWcs6I vS7bVmd7vJjuZY=; b=u9zHrPszrVmRRyx/H4njatpQgVOELFXSKbGTgFV8QVc5m nihIXbiDkiJ7Fh/AwB1cVvDE/4gwgkFR2T+i7/fRonXQpWLOMItlnraK6qqXR0j3 qMEnWotAuZCNuB+fR4hhb+6uou3dPXa3tcUx4Nn0ns0ibDiL58iwsjobxSpA3Ice QhJq05Qr8vwghRVKPFk8zil7H69FvkscWCcpTMNh3H9NL8XNR/dZMv3pn6zRgBZO 5abvIfgG3XpiFQMUZ75e7dIgEjmUj47li7cimpNvRqlm++WxJk9pB7HX6vlMXOsU f/tbcfn2RhTA+5b0iHAwFgChDMj2U5tFW9ypOV8/Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=LkuWNo mxIJwgZkLU5CyDsUEKWcs6IvS7bVmd7vJjuZY=; b=Sn3v8B6c2xvIffVlL8MAvX b1/0UOXnOnnIDEle77ZZeoGF4250qACpuxXfwodqSvWp52Udsb+krjIx/Ei9eKTz EFO6Jl9ttYmLG3YqSOU/g0LuUnL4uGQ6/bWsdbwm3wAlNUinEsBZTTQSnGfwfZGN J5wgUYiuLZuQ3oGDiBGU2LHnAlju5T8Df0gZsvHzz7t/yQN3eJbqv57+UANBkztN uc7VEz9v/Gdl+DdE6vlhuA8GxFqrzCsgQvxu2zxWvoTbdlPL7xXpYEle0PWbQjZH ZtnMjxU8b5RqFaogUgPSxoGf/VT2etHSS9XFyUEzvHz5OggWdLn2+zpaPoihQ6vQ == X-ME-Proxy: X-ME-Sender: Received: from odin.yuripv.net (unknown [62.183.127.178]) by mail.messagingengine.com (Postfix) with ESMTPA id 37B9D102D9; Tue, 18 Sep 2018 04:41:19 -0400 (EDT) Subject: Re: usb rtwn not loaded properly at boot To: Johannes Lundberg Cc: freebsd-current References: From: Yuri Pankov Message-ID: <3a31624f-7c3d-9286-ad28-039660eba212@yuripv.net> Date: Tue, 18 Sep 2018 11:41:18 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-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, 18 Sep 2018 08:41:22 -0000 Johannes Lundberg wrote: > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: > >> Johannes Lundberg wrote: >>> Hi >>> >>> I have (with 12-ALPHA5) >>> >>> /boot/loader.conf >>> rtwn_load="YES" >>> if_urtw_usb_load="YES" >> >> rtwn(4) thinks this should be if_rtwn_usb_load="YES". >> > > Ah yes. Sorry about that. I still suffer confusion from the rename. > Still, it doesn't change anything since if_rtwn_usb was loaded anyway. OK, just making sure. My guess based on experience with iwm where I need to specify both if_iwm_load="YES" *and* iwm8265fw_load="YES" would be explicitly loading the firmware you need from loader.conf. >>> /etc/rc.conf >>> wlans_rtwn0="wlan0" >>> ifconfig_wlan0="WPA DHCP" >>> >>> but still after boot only lo0 exists and all modules are loaded. >>> >>> Manually running >>> ifconfig wlan0 create wlandev rtwn0 >>> sets up the interface correctly. >>> >>> In my kernel config I have >>> MODULES_OVERRIDE="....usb rtwn_usb rtwn ...." >>> >>> I'm pretty sure this has worked before... Any clues? From owner-freebsd-current@freebsd.org Tue Sep 18 08:43: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 B5D651097E84 for ; Tue, 18 Sep 2018 08:43:55 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 2FA02859EF for ; Tue, 18 Sep 2018 08:43:55 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x42f.google.com with SMTP id k5-v6so1114789wre.10 for ; Tue, 18 Sep 2018 01:43:55 -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=dQJzmmAOmus8DkSJh7D28xfKshO4mOzvmD6DgrSDyQo=; b=aarS3DtsTP1597Lkak94lB5Tl2ZWU+SZoPA626BU5ZoELY3Obh+1qMwzN7ZJ2hYwwh FzBSuoc1BIq53no5kpaSmHFdv0Vjp8omFFKhBBwwEHJodE815rGxHQDl+Zzmj0WmjCh0 SR+tJiMHcsujAHdLMTZ06l/WKXqljf3otetcowK8uaXSCv0zKbR0HS9kgEfgLk6mPX2h sn0CLNp/1kFaHRGPVOC5Sc73LenB+8QL9kTOlisF9OBBWGfagw0w3CZERuxPsLOMlLPf AlvaeXnaXyceoOBWAT1x3TBjeOQEBCPHUqojmBddHSt6+AdTKmljLr8C6AQuftIBtAC2 P21w== 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=dQJzmmAOmus8DkSJh7D28xfKshO4mOzvmD6DgrSDyQo=; b=eeDbxGgaegRRp56nfTbBIQWetaBgjOh8g/vob9IEIrjTmUee9zdS5aGADWULgk7qAN HsYIqoSzHFrj059i3mTBv8P+vdVXlE81nIhsLX1cQRTK7LDWwLAsgYDcMli+LyvdKeUf AESEZcLzDlZUxcY89WJ1EqOsvDNWDBhddFu4QNVCDogZfSbQDu97eszSvHPiKfx4XO6Y QmGKEvABEPUwzwBAibS/0It/N+meIQOArelt5TkToBDI42HbPsByNYrguA3Wu1Zfj9qx uzXDSxZYVZwYVYyjHywFv+yO+E0UTq1Zzu7TfGgSZS2CoqNqnCNYksN1gUJ9OUxSToAD 05mA== X-Gm-Message-State: APzg51C89u0dFLypqTMyA7UUxjH5ycrl/0HkbnqUYkL62sJnaAFXxoeK pZdDw/Op1V7jDlnw0rNBSSiT/Lxx5XpGyqd1OAw= X-Google-Smtp-Source: ANB0Vdbhmy1xTuoCQ2oWK1ssypWB5kVpTLvtyrfCspbxcxknDrGWh1UXWXP0/rqBXy8svBVxgq3pQ2ue9tUzWwdFdMU= X-Received: by 2002:adf:fc44:: with SMTP id e4-v6mr22526703wrs.9.1537260233990; Tue, 18 Sep 2018 01:43:53 -0700 (PDT) MIME-Version: 1.0 References: <4309D3E5-A2C2-450E-8C35-D3603E4A6080@cs.huji.ac.il> In-Reply-To: <4309D3E5-A2C2-450E-8C35-D3603E4A6080@cs.huji.ac.il> From: Johannes Lundberg Date: Tue, 18 Sep 2018 09:43:17 +0100 Message-ID: Subject: Re: usb rtwn not loaded properly at boot To: danny@cs.huji.ac.il Cc: yuripv@yuripv.net, 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: Tue, 18 Sep 2018 08:43:55 -0000 On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss wrote: > > > > On 18 Sep 2018, at 10:32, Johannes Lundberg wrote: > > > > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: > > > >> Johannes Lundberg wrote: > >>> Hi > >>> > >>> I have (with 12-ALPHA5) > >>> > >>> /boot/loader.conf > >>> rtwn_load=3D"YES" > >>> if_urtw_usb_load=3D"YES" > >> > >> rtwn(4) thinks this should be if_rtwn_usb_load=3D"YES". > >> > > > > Ah yes. Sorry about that. I still suffer confusion from the rename. > > Still, it doesn't change anything since if_rtwn_usb was loaded anyway. > > > > > >>> /etc/rc.conf > >>> wlans_rtwn0=3D"wlan0" > >>> ifconfig_wlan0=3D"WPA DHCP" > >>> > >>> but still after boot only lo0 exists and all modules are loaded. > >>> > >>> Manually running > >>> ifconfig wlan0 create wlandev rtwn0 > >>> sets up the interface correctly. > >>> > >>> In my kernel config I have > >>> MODULES_OVERRIDE=3D"....usb rtwn_usb rtwn ...." > >>> > >>> I'm pretty sure this has worked before... Any clues? > >> > > > devd is not calling netif! > try running =E2=80=99service netif start=E2=80=99 and see what happens. > Yep that enables wlan0! > danny > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@freebsd.org Tue Sep 18 09:03: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 C28741098783 for ; Tue, 18 Sep 2018 09:03:40 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 3E76F865FF for ; Tue, 18 Sep 2018 09:03:40 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm1-x331.google.com with SMTP id n11-v6so1755042wmc.2 for ; Tue, 18 Sep 2018 02:03:40 -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=zvjofpmHLa2VOBD+DKoXqA2UfbwlaXVgUlUbIzXujT8=; b=KJHEEdvNoqt/m/RVk87XHdGs9K/qNbDxR+gWytr+Ww+ImnxVhxkvXvmItQNXo8jzZ1 a9dzvnKVdKwfu/uBRgfOPc1uTYzs7Zh+TsHhQMCdhRj5TOwGsW1nMdq4/QupZ15xXM72 Yh1ulF+/NxEb+eDUhbqDCFcmiC3ZszU9S+UiYB2iUPBJGu1OyI2RtJM9w9Eok8YNgYYL zDJgIAbau04RSEcb5+GgLE9+Bt6/ufYev5TqHCY6oGpFZqe2WYQjSaupRskOBTsd5I4l SIlZxecPXVp0HB5tVR3AgBcPrW3rsvkA42MD7LRTsgQWPmWLifPP0gDLGri1+bXp8t4p 3hiw== 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=zvjofpmHLa2VOBD+DKoXqA2UfbwlaXVgUlUbIzXujT8=; b=eP69n0eu6v/7ZurwqUNTuwycAf+7bnmQIOS0DGz6/HuNgco7A/oyChzJ3M6aisxJb2 fbE2dZHBmETFMnjJ61+zI0JJnkGBuDwbhLO1ZaqYwLAGgfP0tvml9KLG5rMFdwg4WM9J CnIIYUZgwieOOFs9Rwsp4oOfHRhFwODcPfH43bHUziKOOsSz3Lzr3FnDzWGG1a2jyVTn itVMD83vJGrZtgFdX0fpyS0bSGno1F8YyZXkAEYVUnDQREtn96jsImA9aEPVJLIeShLB WH2h3eirqJqw1SEd3jC7BzpKzqWfJXX2zRdns8LNIi40QEr0YxweqTr5Y3xIRUPBfplE 7v1Q== X-Gm-Message-State: APzg51B0G5c2up1StDci6J2H+2zXJhpacgHU6molcSj6BEC65blG3D2L 3acd2QNy4eyh57AK9sKT5XUx7JRuNbpfWecowBo= X-Google-Smtp-Source: ANB0VdZLWkH0270LA0FT2dUZLyLs/bnU9REcBULDYVC6Rk5JZoNzg2wCRW+OIPUvb5ltz/tyOZMB93HckN8NekKOItQ= X-Received: by 2002:a1c:780c:: with SMTP id t12-v6mr14135826wmc.133.1537261418962; Tue, 18 Sep 2018 02:03:38 -0700 (PDT) MIME-Version: 1.0 References: <4309D3E5-A2C2-450E-8C35-D3603E4A6080@cs.huji.ac.il> In-Reply-To: From: Johannes Lundberg Date: Tue, 18 Sep 2018 10:03:02 +0100 Message-ID: Subject: Re: usb rtwn not loaded properly at boot To: danny@cs.huji.ac.il Cc: yuripv@yuripv.net, 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: Tue, 18 Sep 2018 09:03:41 -0000 On Tue, Sep 18, 2018 at 9:43 AM Johannes Lundberg wrote: > > > On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss > wrote: > >> >> >> > On 18 Sep 2018, at 10:32, Johannes Lundberg wrote= : >> > >> > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote: >> > >> >> Johannes Lundberg wrote: >> >>> Hi >> >>> >> >>> I have (with 12-ALPHA5) >> >>> >> >>> /boot/loader.conf >> >>> rtwn_load=3D"YES" >> >>> if_urtw_usb_load=3D"YES" >> >> >> >> rtwn(4) thinks this should be if_rtwn_usb_load=3D"YES". >> >> >> > >> > Ah yes. Sorry about that. I still suffer confusion from the rename. >> > Still, it doesn't change anything since if_rtwn_usb was loaded anyway. >> > >> > >> >>> /etc/rc.conf >> >>> wlans_rtwn0=3D"wlan0" >> >>> ifconfig_wlan0=3D"WPA DHCP" >> >>> >> >>> but still after boot only lo0 exists and all modules are loaded. >> >>> >> >>> Manually running >> >>> ifconfig wlan0 create wlandev rtwn0 >> >>> sets up the interface correctly. >> >>> >> >>> In my kernel config I have >> >>> MODULES_OVERRIDE=3D"....usb rtwn_usb rtwn ...." >> >>> >> >>> I'm pretty sure this has worked before... Any clues? >> >> >> >> >> devd is not calling netif! >> try running =E2=80=99service netif start=E2=80=99 and see what happens. >> > > Yep that enables wlan0! > > With wlan0 up and running, unplug and re-plug the wifi adapter will create rtwn0 device but no wlan0. Firmware was missing so I added rtwnfw to MODULES_OVERRIDE but it makes no difference for this problem. >> danny >> >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to " >> freebsd-current-unsubscribe@freebsd.org" >> >> From owner-freebsd-current@freebsd.org Tue Sep 18 10:12:27 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 3D5181099AEC for ; Tue, 18 Sep 2018 10:12:27 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B6C2189151 for ; Tue, 18 Sep 2018 10:12:26 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=yc56KSN+7a+HbNJW1rTGaDuAeq4Yw6lpa33oOwVy1xk=; b=MxZtlbNKMsj+Vp2UCIU77qC86AE8SSSAh2Bcccb/KLoO16Qd2qVLjHBiIsG+/sn0gb3Yn2+tjmSCY8+nQ4CvdP9qEspoHfi41so0hA1y+cd9b2WL1lI6BgmUDQQDay3MI0YS4d000b5CA37VuqyUoTKyr4HrEOURFmIA2L3b52s= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 0bb11e17 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 18 Sep 2018 10:12:00 +0000 (UTC) Date: Tue, 18 Sep 2018 13:11:55 +0300 From: Greg V Subject: Re: FreeBSD EFI projects To: Konstantin Belousov Cc: Warner Losh , rebecca@bluestop.org, FreeBSD Current Message-Id: <1537265515.2378.0@hraggstad.unrelenting.technology> In-Reply-To: <20180917200935.GD3161@kib.kiev.ua> References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> <20180917200935.GD3161@kib.kiev.ua> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed 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, 18 Sep 2018 10:12:27 -0000 On Mon, Sep 17, 2018 at 11:09 PM, Konstantin Belousov wrote: > That said, making only the loader->kernel transition from EFI 32bit to > 64bit kernel should be not too hard, and even significantly simpler > than > to make 32bit EFI load 32bit kernel. amd64 kernels already aware that > there might be no BIOS and they do not try to make vm86 calls into > real > code, and only read memory map from the loader metadata etc. > > Besides old Macs, this should also benefit newer Intel embedded-like > boards. Hi, I can confirm that the kernel already worked fine when booted from 32-bit EFI. I booted an old Mac into HardenedBSD using a 32-bit-EFI build of GRUB2 :) From owner-freebsd-current@freebsd.org Tue Sep 18 11:54: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 7D8C2109BED1 for ; Tue, 18 Sep 2018 11:54:07 +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 EEA978CFCF for ; Tue, 18 Sep 2018 11:54:06 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x42c.google.com with SMTP id z96-v6so1769857wrb.8 for ; Tue, 18 Sep 2018 04:54:06 -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=JI3hz4Ycf9KzTpfNSCmZ01BTjF0A55UEOIKpzYSjy+o=; b=FmxU9t7JQkfnJ3ljiCpoNcu31++prwvS5TMpN3QxW1uSDDGWDw4YnngR1kiHvOWtbr XooeXHF3AdrtAwbGUy88cKDWEZgT5cBYow2OgE1k5yYwBUeYun3So0GaR6GyyDDT0QKf spaST0V7bfyFOlibgYYv+AX7iBHlMv5O6k6D+b9N0LsFqTh2buHSBeixBa4BixfBMNrj ZyMnwZ4Y7X51z/lm3PW49gyO+v5IZcjO98aWVh1SrJQZiH1l2FWucx637F3z3d5BuD3q CE2IfhLELthemGBi7c5rFeoe6PUAL5V4NTNvMnDecRdklwbPMUHebc/EqxUhN0u5c03Y MBLA== 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=JI3hz4Ycf9KzTpfNSCmZ01BTjF0A55UEOIKpzYSjy+o=; b=kbhZIoa7lgCToKI1YvMj4q5EjhQqugZ6ADR/PU2SMxUNDHqi6VsLjq667J6hb5jRJA wpGyDHE06r0nU1Eps7+o/JrrfZYhftGDWpsntU2hsRJyLQr9imZP9gHbpRnpkItE1r3i Nk7zqB+nWFMbtEJA9B/NQbHgqFbnkHJ9V8TeRvq6O0tynb0PhquFfx5MNMIZAdg6NWhN tyvL+cpv/GuRqdGESF0N1anFxgolWTUeK0rCawBeEkRWl9Q6qRq8eJk5sUOpiXveibOs BiM8PSRxktThM5vFOlfT1Wywx88IBP64fbC0XaDLTIC3/0DyeD3bXqo4hOAZUPL+AiFh 4Gzw== X-Gm-Message-State: APzg51ABM3JLGmi/OwOChKNIUdcFqYrMiitrIkEji9WKdDQ23RgFXkJr xbVG2M7SEl3CexWZfNoi0TmoOA0Fn9NkkdgVVkG/kzFd X-Google-Smtp-Source: ANB0Vdb9V9heEMI3UQnxhZHfwDOewgaTjP8IMAEz8+QG6ETHMogCvf5WI9p4VbO9xCgIgw7dOzPWFcFDd608qt68o/w= X-Received: by 2002:adf:fa4d:: with SMTP id y13-v6mr24026441wrr.155.1537271645564; Tue, 18 Sep 2018 04:54:05 -0700 (PDT) MIME-Version: 1.0 References: <4309D3E5-A2C2-450E-8C35-D3603E4A6080@cs.huji.ac.il> In-Reply-To: From: Johannes Lundberg Date: Tue, 18 Sep 2018 12:53:28 +0100 Message-ID: Subject: Re: usb rtwn not loaded properly at boot To: freebsd-current Cc: Warner Losh 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: Tue, 18 Sep 2018 11:54:07 -0000 On Tue, Sep 18, 2018 at 10:03 AM Johannes Lundberg wrote: > > > On Tue, Sep 18, 2018 at 9:43 AM Johannes Lundberg > wrote: > >> >> >> On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss >> wrote: >> >>> >>> >>> > On 18 Sep 2018, at 10:32, Johannes Lundberg >>> wrote: >>> > >>> > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov wrote= : >>> > >>> >> Johannes Lundberg wrote: >>> >>> Hi >>> >>> >>> >>> I have (with 12-ALPHA5) >>> >>> >>> >>> /boot/loader.conf >>> >>> rtwn_load=3D"YES" >>> >>> if_urtw_usb_load=3D"YES" >>> >> >>> >> rtwn(4) thinks this should be if_rtwn_usb_load=3D"YES". >>> >> >>> > >>> > Ah yes. Sorry about that. I still suffer confusion from the rename. >>> > Still, it doesn't change anything since if_rtwn_usb was loaded anyway= . >>> > >>> > >>> >>> /etc/rc.conf >>> >>> wlans_rtwn0=3D"wlan0" >>> >>> ifconfig_wlan0=3D"WPA DHCP" >>> >>> >>> >>> but still after boot only lo0 exists and all modules are loaded. >>> >>> >>> >>> Manually running >>> >>> ifconfig wlan0 create wlandev rtwn0 >>> >>> sets up the interface correctly. >>> >>> >>> >>> In my kernel config I have >>> >>> MODULES_OVERRIDE=3D"....usb rtwn_usb rtwn ...." >>> >>> >>> >>> I'm pretty sure this has worked before... Any clues? >>> >> >>> >>> >>> devd is not calling netif! >>> try running =E2=80=99service netif start=E2=80=99 and see what happens. >>> >> >> Yep that enables wlan0! >> >> > With wlan0 up and running, unplug and re-plug the wifi adapter will creat= e > rtwn0 device but no wlan0. > Firmware was missing so I added rtwnfw to MODULES_OVERRIDE but it makes n= o > difference for this problem. > > (cc: imp) Here's devd output: https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413 Not sure how to interpret this but it looks like it fails to match rtwn0 at https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413#file-gistf= ile1-txt-L761 >>> danny >>> >>> > _______________________________________________ >>> > freebsd-current@freebsd.org mailing list >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> > To unsubscribe, send any mail to " >>> freebsd-current-unsubscribe@freebsd.org" >>> >>> From owner-freebsd-current@freebsd.org Tue Sep 18 23:26: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 DDF0A10AB957 for ; Tue, 18 Sep 2018 23:26:45 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5F96A885CD for ; Tue, 18 Sep 2018 23:26:45 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (unknown [75.161.199.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 969BC1AF5DC for ; Tue, 18 Sep 2018 15:35:48 +0000 (UTC) To: freebsd-current From: Sean Bruno Subject: Some delete-old detrius Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: <6d84beba-60eb-16a6-d566-13519d20623d@freebsd.org> Date: Tue, 18 Sep 2018 17:26:29 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="zQYQlBFfZvK1u6KGa9opLq31T4A8f8EJw" 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, 18 Sep 2018 23:26:46 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --zQYQlBFfZvK1u6KGa9opLq31T4A8f8EJw Content-Type: multipart/mixed; boundary="MnAcMs8szK7cmVG5Q88mD0lRraJeSiLUE"; protected-headers="v1" From: Sean Bruno To: freebsd-current Message-ID: <6d84beba-60eb-16a6-d566-13519d20623d@freebsd.org> Subject: Some delete-old detrius --MnAcMs8szK7cmVG5Q88mD0lRraJeSiLUE Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable doing a delete-old run: drwxr-xr-x 2 root wheel 25 Sep 18 22:55 usr/lib/debug/usr/lib/i18n rm: usr/bin/indent/tests/nsac.0: Not a directory rm: usr/bin/indent/tests/nsac.0.pro: Not a directory rm: usr/bin/indent/tests/nsac.0.stdout: Not a directory rm: usr/bin/indent/tests/sac.0: Not a directory rm: usr/bin/indent/tests/sac.0.pro: Not a directory rm: usr/bin/indent/tests/sac.0.stdout: Not a directory rm: usr/lib/debug/usr/lib/i18n: is a directory =09 I'm not clear on how long we leave stuff lying around in Obsolete or whatever before we purge them. Is this output with us forever? sean --MnAcMs8szK7cmVG5Q88mD0lRraJeSiLUE-- --zQYQlBFfZvK1u6KGa9opLq31T4A8f8EJw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAluhiaVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LZN0Qf/c/WzrKNWdVzdjSRH2Gc6+QYnwlHHk4c8amZwJ7kckpytsCX3uWEc5UL8 Ctvt61FWw2GwXxvhA5QJZSyR+xVs/O1ZL56rlVvPHZm5M2aaUu6NScosMiPuraTW Fd/iJ+Wk3XtD3VrWElJ+eCqwmopknN3pTS4lRv8TeEflPWxSNw3x5cUL0O2lMnYq fFxE+VZonI13f25JYW9ASzBL9pKmOfTnnqRlv6z33I/rTLiuFzFDaiu2PVyKIK/0 kODozEmS8WQANjMUNTvvL3+DezLYJ/STcdARI6Q3shYRJsIc0n7I6tLidPREYxek lDvetbDVgN/ErjNoPorXq/Motpi9sA== =4Ew1 -----END PGP SIGNATURE----- --zQYQlBFfZvK1u6KGa9opLq31T4A8f8EJw-- From owner-freebsd-current@freebsd.org Wed Sep 19 00:38: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 8F89F10ACE85 for ; Wed, 19 Sep 2018 00:38:21 +0000 (UTC) (envelope-from doctorwhoguy@gmail.com) Received: from mail-io1-xd42.google.com (mail-io1-xd42.google.com [IPv6:2607:f8b0:4864:20::d42]) (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 02C738AB34 for ; Wed, 19 Sep 2018 00:38:21 +0000 (UTC) (envelope-from doctorwhoguy@gmail.com) Received: by mail-io1-xd42.google.com with SMTP id q5-v6so3107554iop.3 for ; Tue, 18 Sep 2018 17:38:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pNCrC8MI4/TPFWJ5R35gDSNcuj6EYFFhSGLxudRYybA=; b=FJqABE3lK3hK5V66HZ9YiFL+1O4UrdSA/Ow/G0LhIg+MGJNXKe1aOUBqvkHrKRDX+B oTp7Q/o5dcRM7w2s4d8bSqkRxIZ00gzEot7SwsODsgYAV8rFjuaOC8umDcCiqI7KfCxa VlMXTfHP7IFBAHOnjPQoUkB9TrN3Z/UmVF+Dhj7kV4maFwkSHHyOYKztY7vM6qB04QaX 7aI6n6fETsmCYX0h62vogoROvBtFnEA7L6qmeEErmhIChPrGLI+PdPucrjT9gIekTWop 3n6o72ActQ0fZE4pYbd4X2Ppv6O29Y2h4rfqC8GPF2KrUQKRVqgHWmH7D+IiSs7WzNd3 6Vcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=pNCrC8MI4/TPFWJ5R35gDSNcuj6EYFFhSGLxudRYybA=; b=nGIbDgJ8wuCfWQcHf6oIuEt6z76NtoV0uuOczZBL4+Yn150yttumM4HuL3nit8IvRQ VYc1Eqvarwmmv/+OpzV/xiYFT1lpF0NNixwlhOOPrQoGXsxX+0K/6YsNEyDmua9ZXN7i cLDmcpK0UGLTH2d406GAsv2VewHx1dSUrsAvv4nmBPCkKinpabfiG5aNudUigI3OqFMs W+UbroU2zcS3ainzcOZIL9Ue/pgFUeZuGFQGf4oZpjWXP7K68X6344OrhBhooeiIl/VH /YXBJhQaPl9EA6waATB7oZroNjEoxIot7ifCjI3E9AVTein1v7nMgmR7NYNuHbzey4wr yZXw== X-Gm-Message-State: APzg51CtXT2KxAhz0lGgLHAuUIU5KKNRlTDUCT+wXrDMwDtd23BnycxA 5YHfs/Lauc508h1niALQK4Sbx+oUVBF2S/CK9sJZqutQ X-Google-Smtp-Source: ANB0VdYe9iPLlICzBlxp3ycww4ua8z3Uqi/SJZ6mjXMHtJj/VkcOiyJ1xq59FPSiKNfEET/1kWUObbVFV18rWF5zWn8= X-Received: by 2002:a6b:6702:: with SMTP id b2-v6mr26075242ioc.22.1537317500013; Tue, 18 Sep 2018 17:38:20 -0700 (PDT) MIME-Version: 1.0 References: <4309D3E5-A2C2-450E-8C35-D3603E4A6080@cs.huji.ac.il> In-Reply-To: From: Patrick McMunn Date: Tue, 18 Sep 2018 19:38:08 -0500 Message-ID: Subject: Re: usb rtwn not loaded properly at boot To: freebsd-current@freebsd.org 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, 19 Sep 2018 00:38:21 -0000 I filed a bug about this issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231441 I have encounter= ed it with the run USB wireless driver. I haven't tested it with ethernet. Does this issue only affect wireless devices, only certain drivers, or all network connections? On Tue, Sep 18, 2018 at 6:55 AM Johannes Lundberg wrote: > On Tue, Sep 18, 2018 at 10:03 AM Johannes Lundberg > wrote: > > > > > > > On Tue, Sep 18, 2018 at 9:43 AM Johannes Lundberg > > wrote: > > > >> > >> > >> On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss > >> wrote: > >> > >>> > >>> > >>> > On 18 Sep 2018, at 10:32, Johannes Lundberg > >>> wrote: > >>> > > >>> > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov > wrote: > >>> > > >>> >> Johannes Lundberg wrote: > >>> >>> Hi > >>> >>> > >>> >>> I have (with 12-ALPHA5) > >>> >>> > >>> >>> /boot/loader.conf > >>> >>> rtwn_load=3D"YES" > >>> >>> if_urtw_usb_load=3D"YES" > >>> >> > >>> >> rtwn(4) thinks this should be if_rtwn_usb_load=3D"YES". > >>> >> > >>> > > >>> > Ah yes. Sorry about that. I still suffer confusion from the rename. > >>> > Still, it doesn't change anything since if_rtwn_usb was loaded > anyway. > >>> > > >>> > > >>> >>> /etc/rc.conf > >>> >>> wlans_rtwn0=3D"wlan0" > >>> >>> ifconfig_wlan0=3D"WPA DHCP" > >>> >>> > >>> >>> but still after boot only lo0 exists and all modules are loaded. > >>> >>> > >>> >>> Manually running > >>> >>> ifconfig wlan0 create wlandev rtwn0 > >>> >>> sets up the interface correctly. > >>> >>> > >>> >>> In my kernel config I have > >>> >>> MODULES_OVERRIDE=3D"....usb rtwn_usb rtwn ...." > >>> >>> > >>> >>> I'm pretty sure this has worked before... Any clues? > >>> >> > >>> > >>> > >>> devd is not calling netif! > >>> try running =E2=80=99service netif start=E2=80=99 and see what happen= s. > >>> > >> > >> Yep that enables wlan0! > >> > >> > > With wlan0 up and running, unplug and re-plug the wifi adapter will > create > > rtwn0 device but no wlan0. > > Firmware was missing so I added rtwnfw to MODULES_OVERRIDE but it makes > no > > difference for this problem. > > > > > (cc: imp) > > Here's devd output: > > https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413 > > Not sure how to interpret this but it looks like it fails to match rtwn0 = at > > https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413#file-gis= tfile1-txt-L761 > > > > > >>> danny > >>> > >>> > _______________________________________________ > >>> > freebsd-current@freebsd.org mailing list > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> > To unsubscribe, send any mail to " > >>> freebsd-current-unsubscribe@freebsd.org" > >>> > >>> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > --=20 Patrick McMunn - Learn more about the Catholic Faith: http://www.catholic.com/ - Pray with the Church: http://www.universalis.com/ From owner-freebsd-current@freebsd.org Wed Sep 19 02:48: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 99EEE108B2B7 for ; Wed, 19 Sep 2018 02:48:26 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-23.consmr.mail.gq1.yahoo.com (sonic312-23.consmr.mail.gq1.yahoo.com [98.137.69.204]) (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 0D0E08DEEB for ; Wed, 19 Sep 2018 02:48:25 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: uT0eDk8VM1le6SkaCHflyowLY3OD2Azw2rYf.o44CHEPi67fZ.MpxSJCXR0XvNH uIHf2pMZeb67H5L8b_8FyEkg4SCf0bnrsfZSeJsBclMzgoe8YRFHTDaveBhPSSxv.LFA3jNNLDV9 08Fm_tdI9Xe8AvdASFP3VRchA.2dePUHeXNRZN7gSuKwaRbmZSYB1zd_vaTFfb9lHy.3glQLclYx RiQgO00DpLceI953yIB1oII4ODXTGbdvR52L3vU_NjmFeXSUepBZYfucGTc3urN43VX58PDwpzaG cgDssZjsgrpfqkCDS3OF0BnRypbB_GQDIMW.FaSkNeEXUJN3plcSwPeamtr_Dl7hI_idRu83HNT. nyAIs5rqRM9KNWOaTR8WRLB7B8td7cS4I11bvJ9xyFhrAPvxi_kq9ImsvJbQscqjYVBlMJqtMyp9 V2tseXAg1zGaADKKN1X.ItiHF.W6Qk08EmbetPmyCTQDdfEmuemBUXsdEmwlnXr60IIcZvExIuA. 55beS5PnYEBg0o7N3Wcp_cbpSNGCoaLxnpdO1Of4HKTYTYVk.B_8tMAooLDnRtjjbPV9LSzXceNR W4GdEKlKMzn0.zh7h.15bc5dOu31dqtM7B8MlJn1zsk1x_aNq4enZe9dWlVmSVKFJoyebY0WAVXp I9bWvS_XFIRPKtqoyXUGYdU.eGkdnbhz8WfpFBcsrziBns501gR4wCj12GetQuu3kOP2bu_r32kQ 0Y41gHrzSkTlAYxW63OZvSB5qr3qbqJiLrKN1XmDucCd2MMGbObr2Bf8Yy78DtaJC9BmNLaMnAl. R8G7kB3F_hdwK2tBFNS.1Nl8.wEPugn_mkx0CZfPRCQWNC3NNUOnlcCIgnn1V3r4tx2x8d5St2Zb o6efBbFMhZB42U6JFHrVxPOjHgm4IRCBqYHetcTG9JOB1O8AVqHzayFIdaIoJ4xi4qBN64rMyyaw KRfTmtVis5vKIFlag08gutSMb.OcB7XV6O7Fp_NmR.3liGJxWUDHruK7sciekXCqH4y4eYwz1i8P Zka9Ze95k Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Wed, 19 Sep 2018 02:48:24 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp422.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID c312565208e74fd1d2d1b005b8676821; Wed, 19 Sep 2018 02:48:24 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Some delete-old detrius Message-Id: <26183B75-2CBD-4D98-A59F-85617D5D18E2@yahoo.com> Date: Tue, 18 Sep 2018 19:48:23 -0700 To: Sean Bruno , 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: Wed, 19 Sep 2018 02:48:26 -0000 A problem here is that the references should be to usr.bin instead of usr/bin . See: = https://lists.freebsd.org/pipermail/svn-src-head/2018-September/118426.htm= l which reports for svn commit: r336601 - head: QUOTE Looks like this head/ObsoleteFiles.inc update has a typo in each thing added to OLD_FILES . . . # ls -lTdt /usr/tests/usr.bin/indent/* -r--r--r-- 1 root wheel 121 Sep 13 22:53:30 2018 = /usr/tests/usr.bin/indent/Kyuafile . . . -r--r--r-- 1 root wheel 295 Sep 13 22:53:29 2018 = /usr/tests/usr.bin/indent/binary.0 -r--r--r-- 1 root wheel 92 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0.pro -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0.stdout -r--r--r-- 1 root wheel 122 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0 -r--r--r-- 1 root wheel 94 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0.pro -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0.stdout -r--r--r-- 1 root wheel 123 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0 vs. ( note usr.bin vs. usr/bin ): Modified: head/ObsoleteFiles.inc = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- head/ObsoleteFiles.inc Sun Jul 22 12:04:21 2018 = (r336600) +++ head/ObsoleteFiles.inc Sun Jul 22 12:45:02 2018 = (r336601) @@ -38,6 +38,13 @@ # xargs -n1 | sort | uniq -d; # done =20 +# 20180722: indent(1) option renamed, test files follow +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0 +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.pro +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.stdout +OLD_FILES+=3Dusr/bin/indent/tests/sac.0 +OLD_FILES+=3Dusr/bin/indent/tests/sac.0.pro +OLD_FILES+=3Dusr/bin/indent/tests/sac.0.stdout # 20180721: move of libmlx5.so.1 and libibverbs.so.1 OLD_LIBS+=3Dusr/lib/libmlx5.so.1 OLD_LIBS+=3Dusr/lib/libibverbs.so.1 END QUOTE This was after having the nsac and sac kyua tests report failures in my environment, long after they should have not existed. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Wed Sep 19 05:31: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 94DB5109017E for ; Wed, 19 Sep 2018 05:31:22 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 3440071A3D for ; Wed, 19 Sep 2018 05:31:22 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 9BBE2355D9; Tue, 18 Sep 2018 23:31:50 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id p7Wo967rFme6; Tue, 18 Sep 2018 23:31:49 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Tue, 18 Sep 2018 23:31:49 -0600 (MDT) Subject: Re: FreeBSD EFI projects To: Greg V , Konstantin Belousov Cc: Warner Losh , FreeBSD Current References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> <20180917200935.GD3161@kib.kiev.ua> <1537265515.2378.0@hraggstad.unrelenting.technology> From: Rebecca Cran Message-ID: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> Date: Tue, 18 Sep 2018 23:31:14 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <1537265515.2378.0@hraggstad.unrelenting.technology> Content-Type: text/plain; charset=utf-8 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, 19 Sep 2018 05:31:22 -0000 On 9/18/18 4:11 AM, Greg V wrote: > > I can confirm that the kernel already worked fine when booted from > 32-bit EFI. > > I booted an old Mac into HardenedBSD using a 32-bit-EFI build of GRUB2 :) Was that a 64-bit version of FreeBSD? My understanding is the 32-bit FreeBSD boots fine, but 64-bit needs work. -- Rebecca From owner-freebsd-current@freebsd.org Wed Sep 19 08:35: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 CDBDB1093CC9 for ; Wed, 19 Sep 2018 08:35:49 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (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 3662F77670 for ; Wed, 19 Sep 2018 08:35:49 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm1-x32a.google.com with SMTP id f21-v6so5274938wmc.5 for ; Wed, 19 Sep 2018 01:35: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=ZOt3xJl61ClqLvZQF5qLFp7taZTTYLVxn1Q6ohj95zg=; b=m/wy6fCnCNmszJbdaL5zL5NwTqz2719Tvyp6x6MLcKucHGV3F9Aaaj22HpHAyTf0q/ Ao6/LpIjJOp0KOcyK+mH7AX4L2EG60w4nb3JYBRoEfzbmUi+n4x8+BAwFyeb1WtxJW50 ddiy2RDdV4ZZpmKklDwUlvHobBo1mL9PfNMZN9E3d+gV9EscuDun0KbtI2cnXC1lqO4Y bF7HdPJy0IuA2Sxi3iEEPKmFrM4Wdkv4PXlLJoYardQjRIxwGZFgXzom29QOgBH8NEtC YWcjnSiLz30WLsnNP89dOdswwba9oxfsZE2CrJmtONudWrmU714swP0/waarIPInyrsu 7KuA== 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=ZOt3xJl61ClqLvZQF5qLFp7taZTTYLVxn1Q6ohj95zg=; b=XTlOUUedd4NB3nt6yD7JHf+2Gv2gMLsXxi6gg90prUvS91RPBw1HzgIIiPXeCOtyM2 lEsH6Ucp40xXsjkba2YMyPmUZ7zzFeGLVSmFh2GoraeY0+OX9jhsJ/LlVZMROXso1Bzf stHWUNqm+j8Y5HFy06JKE+CPubigvd/EEZE+Iw8U/nKBQk4jWzHFaS2df/gQyiqkigqF i/2570i44yj7zcBovxaYhimnokhT2X1rm8eiQohXPDf0JqSWpF90gWqs8TRgob07/bTW 8XQvgbfIqQ4TD1vyrGn4s6/XAh7/9Gp3qnYRJwtxawI6tbXdFRdz2C6/suxMned5ByWO WSMA== X-Gm-Message-State: APzg51AxQ+V+51y2Td/N3MkmwxQ3ai98RmCor/B913omUJMzg3TERrQO /lRLMYHvXuH0oJ5so1fkhbVnTSmfG1F1R8SLjLQ= X-Google-Smtp-Source: ANB0VdZEJSwqGL92csc+c7Ia1ep+2XgsZP/lStpHW8eHdhk6CHUfzJ1CabehGChr1c+9zEJS5RW8BUzpqiA3EUtY+X0= X-Received: by 2002:a1c:780c:: with SMTP id t12-v6mr18501362wmc.133.1537346147813; Wed, 19 Sep 2018 01:35:47 -0700 (PDT) MIME-Version: 1.0 References: <4309D3E5-A2C2-450E-8C35-D3603E4A6080@cs.huji.ac.il> In-Reply-To: From: Johannes Lundberg Date: Wed, 19 Sep 2018 09:35:09 +0100 Message-ID: Subject: Re: usb rtwn not loaded properly at boot To: doctorwhoguy@gmail.com 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, 19 Sep 2018 08:35:50 -0000 On Wed, Sep 19, 2018 at 1:40 AM Patrick McMunn wrote: > I filed a bug about this issue: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231441 I have > encountered > it with the run USB wireless driver. I haven't tested it with ethernet. > Does this issue only affect wireless devices, only certain drivers, or al= l > network connections? > It looks like the regexps are messed up. In this case none of those wifi and scsi driver would do what's intended. https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413#file-gistf= ile1-txt-L761-L762 > > On Tue, Sep 18, 2018 at 6:55 AM Johannes Lundberg > wrote: > > > On Tue, Sep 18, 2018 at 10:03 AM Johannes Lundberg > > wrote: > > > > > > > > > > > On Tue, Sep 18, 2018 at 9:43 AM Johannes Lundberg > > > wrote: > > > > > >> > > >> > > >> On Tue, Sep 18, 2018 at 9:39 AM Daniel Braniss > > >> wrote: > > >> > > >>> > > >>> > > >>> > On 18 Sep 2018, at 10:32, Johannes Lundberg > > >>> wrote: > > >>> > > > >>> > On Tue, Sep 18, 2018 at 9:27 AM Yuri Pankov > > wrote: > > >>> > > > >>> >> Johannes Lundberg wrote: > > >>> >>> Hi > > >>> >>> > > >>> >>> I have (with 12-ALPHA5) > > >>> >>> > > >>> >>> /boot/loader.conf > > >>> >>> rtwn_load=3D"YES" > > >>> >>> if_urtw_usb_load=3D"YES" > > >>> >> > > >>> >> rtwn(4) thinks this should be if_rtwn_usb_load=3D"YES". > > >>> >> > > >>> > > > >>> > Ah yes. Sorry about that. I still suffer confusion from the renam= e. > > >>> > Still, it doesn't change anything since if_rtwn_usb was loaded > > anyway. > > >>> > > > >>> > > > >>> >>> /etc/rc.conf > > >>> >>> wlans_rtwn0=3D"wlan0" > > >>> >>> ifconfig_wlan0=3D"WPA DHCP" > > >>> >>> > > >>> >>> but still after boot only lo0 exists and all modules are loaded= . > > >>> >>> > > >>> >>> Manually running > > >>> >>> ifconfig wlan0 create wlandev rtwn0 > > >>> >>> sets up the interface correctly. > > >>> >>> > > >>> >>> In my kernel config I have > > >>> >>> MODULES_OVERRIDE=3D"....usb rtwn_usb rtwn ...." > > >>> >>> > > >>> >>> I'm pretty sure this has worked before... Any clues? > > >>> >> > > >>> > > >>> > > >>> devd is not calling netif! > > >>> try running =E2=80=99service netif start=E2=80=99 and see what happ= ens. > > >>> > > >> > > >> Yep that enables wlan0! > > >> > > >> > > > With wlan0 up and running, unplug and re-plug the wifi adapter will > > create > > > rtwn0 device but no wlan0. > > > Firmware was missing so I added rtwnfw to MODULES_OVERRIDE but it mak= es > > no > > > difference for this problem. > > > > > > > > (cc: imp) > > > > Here's devd output: > > > > https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413 > > > > Not sure how to interpret this but it looks like it fails to match rtwn= 0 > at > > > > > https://gist.github.com/johalun/c9383ff03cb29e12c3f4978e06ca6413#file-gis= tfile1-txt-L761 > > > > > > > > > > >>> danny > > >>> > > >>> > _______________________________________________ > > >>> > freebsd-current@freebsd.org mailing list > > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > >>> > To unsubscribe, send any mail to " > > >>> freebsd-current-unsubscribe@freebsd.org" > > >>> > > >>> > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > > > -- > Patrick McMunn > > - Learn more about the Catholic Faith: http://www.catholic.com/ > - Pray with the Church: http://www.universalis.com/ > _______________________________________________ > 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 Sep 19 09:54: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 5D1791095B39 for ; Wed, 19 Sep 2018 09:54:25 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF65E7A515 for ; Wed, 19 Sep 2018 09:54:24 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:to:subject:message-id; s=default; bh=jynrH8dWD0Vs+aGRZ31hG2Vu2wYL3lMEdfinQjdLSSs=; b=dkwRRZqXjniT3H/R0oLouMVuq60Mgr51Z5EsZJq/bPyy48HCjJxzZQgw5sLC3xiMieRrQRRSzjZ4zM0Tx+niRg41vp3/ekv8oLfvlChkm21PeFyGEMoEHeKn0HTZ5I0wJLZG90u9Nvokb8e6CrgrEj3u2Scn327LhQ29coJTwxw= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 29733cd7 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 19 Sep 2018 09:54:10 +0000 (UTC) Received: from ruunvald.lan (localhost.lan [127.0.0.1]) by ruunvald.lan (OpenSMTPD) with ESMTP id 34fda74e; Wed, 19 Sep 2018 12:54:04 +0300 (MSK) Received: (from greg@localhost) by ruunvald.lan (8.15.2/8.15.2/Submit) id w8J9rw8u003297; Wed, 19 Sep 2018 12:53:58 +0300 (MSK) (envelope-from greg@unrelenting.technology) X-Authentication-Warning: ruunvald.lan: greg set sender to greg@unrelenting.technology using -f Date: Wed, 19 Sep 2018 12:53:58 +0300 From: Greg V To: Rebecca Cran Cc: Konstantin Belousov , Warner Losh , FreeBSD Current Subject: Re: FreeBSD EFI projects Message-ID: <20180919095357.qwmm6p3pkbli4zww@unrelenting.technology> References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> <20180917200935.GD3161@kib.kiev.ua> <1537265515.2378.0@hraggstad.unrelenting.technology> <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> OpenPGP: url=https://unrelenting.technology/pub/3B011BAF.asc User-Agent: the one that sucks less X-Hashcash: 1:20:180919:kostikbel@gmail.com::eBcHWGuNaI/3gH3M:4trR X-Hashcash: 1:20:180919:rebecca@bluestop.org::cor6Hr3F/UTpFgId:758 X-Hashcash: 1:20:180919:freebsd-current@freebsd.org::o81QC2Epmu8yLWqB:2gPI X-Hashcash: 1:20:180919:imp@bsdimp.com::1LGdoQhvbgQH4ymq:IWX 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, 19 Sep 2018 09:54:25 -0000 On 09/18, Rebecca Cran wrote: >On 9/18/18 4:11 AM, Greg V wrote: > >> >> I can confirm that the kernel already worked fine when booted from >> 32-bit EFI. >> >> I booted an old Mac into HardenedBSD using a 32-bit-EFI build of GRUB2 :) > > >Was that a 64-bit version of FreeBSD? My understanding is the 32-bit >FreeBSD boots fine, but 64-bit needs work. Yes, of course it was 64-bit. I don't think I ever downloaded the 32-bit one... From owner-freebsd-current@freebsd.org Wed Sep 19 13:28: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 CFE7B109B220 for ; Wed, 19 Sep 2018 13:28:30 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.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 7410F80B03 for ; Wed, 19 Sep 2018 13:28:30 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 350AC109B21D; Wed, 19 Sep 2018 13:28:30 +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 23DAD109B21B for ; Wed, 19 Sep 2018 13:28:30 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD07680B02 for ; Wed, 19 Sep 2018 13:28:29 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.128] (helo=rmmprod06.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1g2cWk-00059A-AE for current@freebsd.org; Wed, 19 Sep 2018 15:28:22 +0200 Received: from mail by rmmprod06.runbox with local (Exim 4.86_2) (envelope-from ) id 1g2cWk-0005mY-8K for current@freebsd.org; Wed, 19 Sep 2018 15:28:22 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); for ; Wed, 19 Sep 2018 13:28:22 GMT From: "Jeffrey Bouquet" To: "current" Subject: just a FYI Date: Wed, 19 Sep 2018 06:28:22 -0700 (PDT) X-Mailer: RMM6 Message-Id: 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, 19 Sep 2018 13:28:31 -0000 /usr/ports/security/lockdown [ sorry if this is a PR or for ports- ] altered fstab, login.conf and ttys locking me out of my main machine, proba= bly due to the password hash, but only a daily backup helped me login again and fix= the=20 damages, with a few files "hardened" maybe but at a cost of uncertainty=20 as to whether the net benefit was good/bad once the system is back up, as it is now. It fortunately only took me about an hour. This would have been much mor= e=20 problematic if I had not had 14 years experience in FreeBSD. Can someone alter the port to log its actions, create backups, ask permis= sion for each block of edits it is about to undertake, etc, so someone with critical= server data or less of a backup doesn't suffer the same? Something like a mergemaster w= ould...=20= From owner-freebsd-current@freebsd.org Wed Sep 19 13:58: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 9863A109BD64 for ; Wed, 19 Sep 2018 13:58:41 +0000 (UTC) (envelope-from carpeddiem@gmail.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 33FEA8199C for ; Wed, 19 Sep 2018 13:58:41 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id ECBB8109BD63; Wed, 19 Sep 2018 13:58:40 +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 DB5F4109BD62 for ; Wed, 19 Sep 2018 13:58:40 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 745B08199A for ; Wed, 19 Sep 2018 13:58:40 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x230.google.com with SMTP id d10-v6so8355935itj.5 for ; Wed, 19 Sep 2018 06:58:40 -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=EgrbTDKppo3THq51ftSEcNdCZ9pEfWnYp9+kjGkTT0E=; b=bbdGtO3FqqZA+qW2/oHvXuLBNdZNzjFpMKC2g7EIEHl5oiU/BJU9D7XiDt05knMGSt tHcWaJNmZ38xF9UiFscT3t4qfFAZZGhB8xMGvmX+d1j5yDioVpqRmW+DJw4GNYgYqO3y XPH6BqDRrVoKcsosglvSuoP+WHk15Ntc+p5H/1Vi1Yy9uF3X6ErGXGtK8Ndx1LV0JsJ7 o/0WKD7NiDVLno22RBRvy9qJfs164l2uNHosOgJO5YRnZ6Nk217/qbeXQ6+AX7PnS02y MWF2jhJioO6Ng6G/vGtX5Xg1VQyzBY7nStXA+UvZf7wtmQbepN7RqiXuJK1d3EyyuES9 colA== 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=EgrbTDKppo3THq51ftSEcNdCZ9pEfWnYp9+kjGkTT0E=; b=VDCM4oJfwwnkj9YJ7XCKwSxnWuv1vKKMmlPF3V45K+Cd9GfSutEiYG0oYPwlpk/60C w+W3mykGkQv8xXbWb6jgd3ztrFkxUUtXQVFlMyYbFO/k74ceGXVtK97Xl3sdm2edWCDz vjaw5u/C7FNC/cx9n46aeNcPEhVdA9eQOs+U5rcYNf6pEApx/kEhzN/Mug1oqOBHLRus 019jHJqBLQMVHTf8A/e8ADsnSXnlPL0lJ5r/2AjqfXGDQBQpWRyJwHGszG5B11stRWKB H7cTVfWsQF87Ck9MsgbYEC7EOd/hIXMOf5ZLYnvsdNKpXU8OnOtKBUjctfjJLiTWLAf4 YQgQ== X-Gm-Message-State: APzg51B2wFa8vBb2titlWT+JzFGwWdoZO9KmySEmZBLEwBty3m1XsVgT +tnDbwMRlY8T29OYcXiCJMIoW2pcnJnhi8hiMHYdvp5P X-Google-Smtp-Source: ANB0VdZpBw9YlgbZJuqHBNAZqUv0SWTz6ss+dWentxysq/wRAtodYaVNdNRxFOL/wa7kf+O61m6ecuCXDspJ3+kbRRg= X-Received: by 2002:a24:e9c6:: with SMTP id f189-v6mr19987907ith.118.1537365519860; Wed, 19 Sep 2018 06:58:39 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:404:0:0:0:0:0 with HTTP; Wed, 19 Sep 2018 06:58:19 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Wed, 19 Sep 2018 09:58:19 -0400 X-Google-Sender-Auth: ShN3hyM2Bkf7R4HjDHPf74yroJY Message-ID: Subject: Re: just a FYI To: Jeffrey Bouquet Cc: 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, 19 Sep 2018 13:58:41 -0000 On 19 September 2018 at 09:28, Jeffrey Bouquet wrote: > /usr/ports/security/lockdown [ sorry if this is a PR or for ports- ] Unfortunately this port has no maintainer, so fixing this is going to need someone to take an interest in the port. I had a quick look at the script and it looks like it sets obsolete flags that would result in an unbootable system. In any case, would you kindly submit a PR for the issue to track it? I'll try to get it marked FORBIDDEN (or similar) for now. From owner-freebsd-current@freebsd.org Wed Sep 19 14:34: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 22E99109D11C for ; Wed, 19 Sep 2018 14:34:11 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 9156A83075 for ; Wed, 19 Sep 2018 14:34:10 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w8JEY5Ej024164; Wed, 19 Sep 2018 07:34:05 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w8JEY41Z024163; Wed, 19 Sep 2018 07:34:04 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> Subject: Re: FreeBSD EFI projects In-Reply-To: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> To: Rebecca Cran Date: Wed, 19 Sep 2018 07:34:04 -0700 (PDT) CC: Greg V , Konstantin Belousov , Warner Losh , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 19 Sep 2018 14:34:11 -0000 > On 9/18/18 4:11 AM, Greg V wrote: > > > > > I can confirm that the kernel already worked fine when booted from > > 32-bit EFI. > > > > I booted an old Mac into HardenedBSD using a 32-bit-EFI build of GRUB2 :) > > > Was that a 64-bit version of FreeBSD? My understanding is the 32-bit > FreeBSD boots fine, but 64-bit needs work. You would be hard pressed to find a system with a 64 bit CPU that could run 64 bit FreeBSD that had a 32 bit EFI implementation. Even finding a 32 bit EFI implementation, at least in the x86 world is very hard to do. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Wed Sep 19 14:42: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 8C7B8109D770 for ; Wed, 19 Sep 2018 14:42:24 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 12867838EE for ; Wed, 19 Sep 2018 14:42:23 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=TKHO7Z8cAXotV4SCJL8JobBDShmlj5FrL63q6RuxtT4=; b=cdDB9Z6AH/19e5stJqYC7st6SsOCHxqquOaxdz65hWxHh6jTIGbCsvJKVjjOgqwn0oH99m78P6OIycnUSpX2XZErfdHXIoHYyPHRcoDyWnrzQ8CmENrYihaqFMpw5O1nklhsK4DqXNDaD+UHzNQvH7sslKSXEPvQvgU/BAVlL3g= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 5145138f TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 19 Sep 2018 14:42:08 +0000 (UTC) Date: Wed, 19 Sep 2018 17:42:01 +0300 From: Greg V Subject: Re: FreeBSD EFI projects To: "Rodney W. Grimes" Cc: Rebecca Cran , Konstantin Belousov , Warner Losh , FreeBSD Current Message-Id: <1537368121.5568.1@hraggstad.unrelenting.technology> In-Reply-To: <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> References: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed 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, 19 Sep 2018 14:42:24 -0000 On Wed, Sep 19, 2018 at 5:34 PM, Rodney W. Grimes wrote: >> On 9/18/18 4:11 AM, Greg V wrote: >> >> > >> > I can confirm that the kernel already worked fine when booted from >> > 32-bit EFI. >> > >> > I booted an old Mac into HardenedBSD using a 32-bit-EFI build of >> GRUB2 :) >> >> >> Was that a 64-bit version of FreeBSD? My understanding is the 32-bit >> FreeBSD boots fine, but 64-bit needs work. > > You would be hard pressed to find a system with a 64 bit CPU that > could run 64 bit FreeBSD that had a 32 bit EFI implementation. Mac mini 2006 with a Core2Duo instead of the stock CoreDuo (and the 2007 model's firmware flashed, but I don't think that impacts FreeBSD). And probably just the 2007 model as well :) Also, IIRC there were some Intel Atom tablets with 32-bit EFI. From owner-freebsd-current@freebsd.org Wed Sep 19 15:06: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 9A1BD109E445 for ; Wed, 19 Sep 2018 15:06:39 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 0CC5784931 for ; Wed, 19 Sep 2018 15:06:38 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w8JF6XVG024281; Wed, 19 Sep 2018 08:06:33 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w8JF6W10024280; Wed, 19 Sep 2018 08:06:32 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201809191506.w8JF6W10024280@pdx.rh.CN85.dnsmgr.net> Subject: Re: FreeBSD EFI projects In-Reply-To: <1537368121.5568.1@hraggstad.unrelenting.technology> To: Greg V Date: Wed, 19 Sep 2018 08:06:32 -0700 (PDT) CC: Rebecca Cran , Konstantin Belousov , Warner Losh , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 19 Sep 2018 15:06:39 -0000 > On Wed, Sep 19, 2018 at 5:34 PM, Rodney W. Grimes > wrote: > >> On 9/18/18 4:11 AM, Greg V wrote: > >> > >> > > >> > I can confirm that the kernel already worked fine when booted from > >> > 32-bit EFI. > >> > > >> > I booted an old Mac into HardenedBSD using a 32-bit-EFI build of > >> GRUB2 :) > >> > >> > >> Was that a 64-bit version of FreeBSD? My understanding is the 32-bit > >> FreeBSD boots fine, but 64-bit needs work. > > > > You would be hard pressed to find a system with a 64 bit CPU that > > could run 64 bit FreeBSD that had a 32 bit EFI implementation. > > Mac mini 2006 with a Core2Duo instead of the stock CoreDuo (and the > 2007 model's firmware flashed, but I don't think that impacts FreeBSD). Yes, that is one of the catagories of rare, a EFI-32 bit system that was originally shipped with a 32 bit only CPU, that later got upgraded in the field with a 64 bit CPU, that still runs a EFI-32 bios. Are you sure the 2007 firmware is EFI32? I would of thought since they upgraded the base system to a 64 bit CPU they would of shipped it with a EFI-64 bios. > > And probably just the 2007 model as well :) > > Also, IIRC there were some Intel Atom tablets with 32-bit EFI. Atom N2xx and Z5xx series Atom models cannot run x86-64 -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Wed Sep 19 15:17: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 ED7D9109E92E for ; Wed, 19 Sep 2018 15:17:34 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 740C484EDE for ; Wed, 19 Sep 2018 15:17:34 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=enmsWA/c3GCjAwRocM5j65m9G6xy9VcbtZ0JDG1NhK0=; b=kkyTblaMZ0EibuU/yAoXsIKICkOYODh7Ww1iS4QG7ukNlyV8zTVfdl/4txK5ySfWDc3oFHyeZ/s0UmBghUxVcu6mgP4iZkSRknBcJvOb5bg87dBolb6cTHbXqHStMJhL5I5JCl31rnk46ISxqje2nlgqQW+SvABdzyl9fc2GNbI= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 1417a9d4 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 19 Sep 2018 15:17:25 +0000 (UTC) Date: Wed, 19 Sep 2018 18:17:18 +0300 From: Greg V Subject: Re: FreeBSD EFI projects To: "Rodney W. Grimes" Cc: Rebecca Cran , Konstantin Belousov , Warner Losh , FreeBSD Current Message-Id: <1537370238.5568.2@hraggstad.unrelenting.technology> In-Reply-To: <201809191506.w8JF6W10024280@pdx.rh.CN85.dnsmgr.net> References: <1537368121.5568.1@hraggstad.unrelenting.technology> <201809191506.w8JF6W10024280@pdx.rh.CN85.dnsmgr.net> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; 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: Wed, 19 Sep 2018 15:17:35 -0000 On Wed, Sep 19, 2018 at 6:06 PM, Rodney W. Grimes=20 wrote: >> On Wed, Sep 19, 2018 at 5:34 PM, Rodney W. Grimes >> wrote: >> >> On 9/18/18 4:11 AM, Greg V wrote: >> >> >> >> > >> >> > I can confirm that the kernel already worked fine when booted=20 >> from >> >> > 32-bit EFI. >> >> > >> >> > I booted an old Mac into HardenedBSD using a 32-bit-EFI build=20 >> of >> >> GRUB2 :) >> >> >> >> >> >> Was that a 64-bit version of FreeBSD? My understanding is the=20 >> 32-bit >> >> FreeBSD boots fine, but 64-bit needs work. >> > >> > You would be hard pressed to find a system with a 64 bit CPU that >> > could run 64 bit FreeBSD that had a 32 bit EFI implementation. >>=20 >> Mac mini 2006 with a Core2Duo instead of the stock CoreDuo (and the >> 2007 model's firmware flashed, but I don't think that impacts=20 >> FreeBSD). >=20 > Yes, that is one of the catagories of rare, a EFI-32 bit system that > was originally shipped with a 32 bit only CPU, that later got upgraded > in the field with a 64 bit CPU, that still runs a EFI-32 bios. > Are you sure the 2007 firmware is EFI32? I would of thought > since they upgraded the base system to a 64 bit CPU they would > of shipped it with a EFI-64 bios. The EFI firmware is technically 64 bit=85 but it only boots 32-bit=20 binaries. https://everymac.com/mac-answers/snow-leopard-mac-os-x-faq/mac-os-x-snow-le= opard-64-bit-macs-64-bit-efi-boot-in-64-bit-mode.html 'Furthermore, it appears that although subsequently released MacBook,=20 MacBook Air, and pre-"Mid-2010" Mac mini models all are equipped with=20 "Core 2 Duo" 64-bit processors and 64-bit EFIs, Apple has blocked these=20 "consumer-targeted" Macs from booting in 64-bit mode. iMac and MacBook=20 Pro models released in 2007 with 64-bit EFIs seem to have been blocked=20 as well.' >> And probably just the 2007 model as well :) >>=20 >> Also, IIRC there were some Intel Atom tablets with 32-bit EFI. >=20 > Atom N2xx and Z5xx series Atom models cannot run x86-64 Atom Z3740 =97 "Instruction Set: 64-bit" https://ark.intel.com/products/76759/Intel-Atom-Processor-Z3740-2M-Cache-up= -to-1_86-GHz The tablet in question: ASUS VivoTab Note 8 (M80TA) https://www.asus.com/us/Tablets/ASUS_VivoTab_Note_8_M80TA/ = From owner-freebsd-current@freebsd.org Wed Sep 19 15:31: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 58615109EEBA for ; Wed, 19 Sep 2018 15:31:47 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 C9D1185849 for ; Wed, 19 Sep 2018 15:31:46 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w8JFVfnw024427; Wed, 19 Sep 2018 08:31:41 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w8JFVeDN024426; Wed, 19 Sep 2018 08:31:40 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201809191531.w8JFVeDN024426@pdx.rh.CN85.dnsmgr.net> Subject: Re: FreeBSD EFI projects In-Reply-To: <1537370238.5568.2@hraggstad.unrelenting.technology> To: Greg V Date: Wed, 19 Sep 2018 08:31:40 -0700 (PDT) CC: Rebecca Cran , Konstantin Belousov , Warner Losh , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 19 Sep 2018 15:31:47 -0000 > On Wed, Sep 19, 2018 at 6:06 PM, Rodney W. Grimes > wrote: > >> On Wed, Sep 19, 2018 at 5:34 PM, Rodney W. Grimes > >> wrote: > >> >> On 9/18/18 4:11 AM, Greg V wrote: > >> >> > >> >> > > >> >> > I can confirm that the kernel already worked fine when booted > >> from > >> >> > 32-bit EFI. > >> >> > > >> >> > I booted an old Mac into HardenedBSD using a 32-bit-EFI build > >> of > >> >> GRUB2 :) > >> >> > >> >> > >> >> Was that a 64-bit version of FreeBSD? My understanding is the > >> 32-bit > >> >> FreeBSD boots fine, but 64-bit needs work. > >> > > >> > You would be hard pressed to find a system with a 64 bit CPU that > >> > could run 64 bit FreeBSD that had a 32 bit EFI implementation. > >> > >> Mac mini 2006 with a Core2Duo instead of the stock CoreDuo (and the > >> 2007 model's firmware flashed, but I don't think that impacts > >> FreeBSD). > > > > Yes, that is one of the catagories of rare, a EFI-32 bit system that > > was originally shipped with a 32 bit only CPU, that later got upgraded > > in the field with a 64 bit CPU, that still runs a EFI-32 bios. > > Are you sure the 2007 firmware is EFI32? I would of thought > > since they upgraded the base system to a 64 bit CPU they would > > of shipped it with a EFI-64 bios. > > The EFI firmware is technically 64 bit? but it only boots 32-bit > binaries. > > https://everymac.com/mac-answers/snow-leopard-mac-os-x-faq/mac-os-x-snow-leopard-64-bit-macs-64-bit-efi-boot-in-64-bit-mode.html > 'Furthermore, it appears that although subsequently released MacBook, > MacBook Air, and pre-"Mid-2010" Mac mini models all are equipped with > "Core 2 Duo" 64-bit processors and 64-bit EFIs, Apple has blocked these > "consumer-targeted" Macs from booting in 64-bit mode. iMac and MacBook > Pro models released in 2007 with 64-bit EFIs seem to have been blocked > as well.' That is not EFI32, so that is not a test case for how FreeBSD boots on EFI32 systems. That is a restriction apple artificially placed in the implementation. > >> And probably just the 2007 model as well :) > >> > >> Also, IIRC there were some Intel Atom tablets with 32-bit EFI. > > > > Atom N2xx and Z5xx series Atom models cannot run x86-64 > > Atom Z3740 ? "Instruction Set: 64-bit" > https://ark.intel.com/products/76759/Intel-Atom-Processor-Z3740-2M-Cache-up-to-1_86-GHz The above does not say Atom Z3xxx. If you find a Atom N2xx or Z5xx based system it most certainly has a EFI32. > > The tablet in question: ASUS VivoTab Note 8 (M80TA) > https://www.asus.com/us/Tablets/ASUS_VivoTab_Note_8_M80TA/ I can not find enough detail to know for certain that tablet actually has which version of EFI. You are saying it has EFI32? And if so based on what information? -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Wed Sep 19 15:51: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 9D0C8109F9D9 for ; Wed, 19 Sep 2018 15:51:25 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D07C86747 for ; Wed, 19 Sep 2018 15:51:24 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=y2Pb06pNYJUhfFHb/rgXU9NKQiOmAuUM7Ml6RXN2mdQ=; b=e25ZFOzCJTMKVGDNQOtOJuk0flZ2n48cGPynHgoHh50mncGDZeV/jmT51zsREWWdSCwjPWUbZ3BVLBTSNbxM/LAs/fTMSn0UpMSrSZRgec3HqEIE5XM1JeGTu6z74F2qqKMGNLmZly1xUP7/xqaywwdHwgxIR/1GSik9dJx123Y= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 4eb20019 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 19 Sep 2018 15:51:06 +0000 (UTC) Date: Wed, 19 Sep 2018 18:50:59 +0300 From: Greg V Subject: Re: FreeBSD EFI projects To: "Rodney W. Grimes" Cc: Rebecca Cran , Konstantin Belousov , Warner Losh , FreeBSD Current Message-Id: <1537372259.5568.3@hraggstad.unrelenting.technology> In-Reply-To: <201809191531.w8JFVeDN024426@pdx.rh.CN85.dnsmgr.net> References: <1537370238.5568.2@hraggstad.unrelenting.technology> <201809191531.w8JFVeDN024426@pdx.rh.CN85.dnsmgr.net> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed 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, 19 Sep 2018 15:51:25 -0000 On Wed, Sep 19, 2018 at 6:31 PM, Rodney W. Grimes wrote: >> On Wed, Sep 19, 2018 at 6:06 PM, Rodney W. Grimes >> wrote: >> >> On Wed, Sep 19, 2018 at 5:34 PM, Rodney W. Grimes >> >> wrote: >> >> >> On 9/18/18 4:11 AM, Greg V wrote: >> >> >> >> >> >> > >> >> >> > I can confirm that the kernel already worked fine when >> booted >> >> from >> >> >> > 32-bit EFI. >> >> >> > >> >> >> > I booted an old Mac into HardenedBSD using a 32-bit-EFI >> build >> >> of >> >> >> GRUB2 :) >> >> >> >> >> >> >> >> >> Was that a 64-bit version of FreeBSD? My understanding is >> the >> >> 32-bit >> >> >> FreeBSD boots fine, but 64-bit needs work. >> >> > >> >> > You would be hard pressed to find a system with a 64 bit CPU >> that >> >> > could run 64 bit FreeBSD that had a 32 bit EFI implementation. >> >> >> >> Mac mini 2006 with a Core2Duo instead of the stock CoreDuo (and >> the >> >> 2007 model's firmware flashed, but I don't think that impacts >> >> FreeBSD). >> > >> > Yes, that is one of the catagories of rare, a EFI-32 bit system >> that >> > was originally shipped with a 32 bit only CPU, that later got >> upgraded >> > in the field with a 64 bit CPU, that still runs a EFI-32 bios. >> > Are you sure the 2007 firmware is EFI32? I would of thought >> > since they upgraded the base system to a 64 bit CPU they would >> > of shipped it with a EFI-64 bios. >> >> The EFI firmware is technically 64 bit? but it only boots 32-bit >> binaries. >> >> >> https://everymac.com/mac-answers/snow-leopard-mac-os-x-faq/mac-os-x-snow-leopard-64-bit-macs-64-bit-efi-boot-in-64-bit-mode.html >> 'Furthermore, it appears that although subsequently released >> MacBook, >> MacBook Air, and pre-"Mid-2010" Mac mini models all are equipped >> with >> "Core 2 Duo" 64-bit processors and 64-bit EFIs, Apple has blocked >> these >> "consumer-targeted" Macs from booting in 64-bit mode. iMac and >> MacBook >> Pro models released in 2007 with 64-bit EFIs seem to have been >> blocked >> as well.' > > That is not EFI32, so that is not a test case for how FreeBSD boots > on EFI32 systems. That is a restriction apple artificially placed > in the implementation. Yeah, maybe not the best test case, but probably the most common one. What matters to users is that a 32-bit loader (bootia32.efi) is required, whether artificially or not. >> >> And probably just the 2007 model as well :) >> >> >> >> Also, IIRC there were some Intel Atom tablets with 32-bit EFI. >> > >> > Atom N2xx and Z5xx series Atom models cannot run x86-64 >> >> Atom Z3740 ? "Instruction Set: 64-bit" >> >> https://ark.intel.com/products/76759/Intel-Atom-Processor-Z3740-2M-Cache-up-to-1_86-GHz > > The above does not say Atom Z3xxx. If you find a Atom > N2xx or Z5xx based system it most certainly has a EFI32. > >> >> The tablet in question: ASUS VivoTab Note 8 (M80TA) >> https://www.asus.com/us/Tablets/ASUS_VivoTab_Note_8_M80TA/ > > I can not find enough detail to know for certain that tablet > actually has which version of EFI. > You are saying it has EFI32? And if so based on what information? Heard from someone that it only took 32-bit efi binaries. Other Z3xxx users report the same: https://askubuntu.com/questions/775498/ubuntu-on-32-bit-uefi-only-based-tablet-pc From owner-freebsd-current@freebsd.org Wed Sep 19 16:14: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 8047A10A06E1 for ; Wed, 19 Sep 2018 16:14:17 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1F9C988525 for ; Wed, 19 Sep 2018 16:14:16 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (unknown [75.161.199.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 4E2631AF5DC; Wed, 19 Sep 2018 08:23:52 +0000 (UTC) Subject: Re: Some delete-old detrius To: Mark Millard , FreeBSD Current References: <26183B75-2CBD-4D98-A59F-85617D5D18E2@yahoo.com> From: Sean Bruno Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: Date: Wed, 19 Sep 2018 10:14:11 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <26183B75-2CBD-4D98-A59F-85617D5D18E2@yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gkGJ5Hwu4GcXO3RJyySDbHsXyae6fQBKA" 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, 19 Sep 2018 16:14:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gkGJ5Hwu4GcXO3RJyySDbHsXyae6fQBKA Content-Type: multipart/mixed; boundary="456DsBBUd8VIHQVccdDm6Bv8inIk63ahS"; protected-headers="v1" From: Sean Bruno To: Mark Millard , FreeBSD Current Message-ID: Subject: Re: Some delete-old detrius References: <26183B75-2CBD-4D98-A59F-85617D5D18E2@yahoo.com> In-Reply-To: <26183B75-2CBD-4D98-A59F-85617D5D18E2@yahoo.com> --456DsBBUd8VIHQVccdDm6Bv8inIk63ahS Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 9/18/18 8:48 PM, Mark Millard wrote: > A problem here is that the references should be to usr.bin instead > of usr/bin . See: >=20 > https://lists.freebsd.org/pipermail/svn-src-head/2018-September/118426.= html >=20 > which reports for svn commit: r336601 - head: >=20 > QUOTE > Looks like this head/ObsoleteFiles.inc update has a typo > in each thing added to OLD_FILES . . . >=20 > # ls -lTdt /usr/tests/usr.bin/indent/* > -r--r--r-- 1 root wheel 121 Sep 13 22:53:30 2018 /usr/tests/usr.bin= /indent/Kyuafile > . . . > -r--r--r-- 1 root wheel 295 Sep 13 22:53:29 2018 /usr/tests/usr.bin= /indent/binary.0 > -r--r--r-- 1 root wheel 92 May 1 19:35:24 2018 /usr/tests/usr.bin= /indent/sac.0.pro > -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 /usr/tests/usr.bin= /indent/sac.0.stdout > -r--r--r-- 1 root wheel 122 May 1 19:35:24 2018 /usr/tests/usr.bin= /indent/sac.0 > -r--r--r-- 1 root wheel 94 May 1 19:35:24 2018 /usr/tests/usr.bin= /indent/nsac.0.pro > -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 /usr/tests/usr.bin= /indent/nsac.0.stdout > -r--r--r-- 1 root wheel 123 May 1 19:35:24 2018 /usr/tests/usr.bin= /indent/nsac.0 >=20 > vs. ( note usr.bin vs. usr/bin ): >=20 > Modified: head/ObsoleteFiles.inc > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > --- head/ObsoleteFiles.inc Sun Jul 22 12:04:21 2018 (r336600) > +++ head/ObsoleteFiles.inc Sun Jul 22 12:45:02 2018 (r336601) > @@ -38,6 +38,13 @@ > # xargs -n1 | sort | uniq -d; > # done > =20 > +# 20180722: indent(1) option renamed, test files follow > +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0 > +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.pro > +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.stdout > +OLD_FILES+=3Dusr/bin/indent/tests/sac.0 > +OLD_FILES+=3Dusr/bin/indent/tests/sac.0.pro > +OLD_FILES+=3Dusr/bin/indent/tests/sac.0.stdout > # 20180721: move of libmlx5.so.1 and libibverbs.so.1 > OLD_LIBS+=3Dusr/lib/libmlx5.so.1 > OLD_LIBS+=3Dusr/lib/libibverbs.so.1 > END QUOTE >=20 > This was after having the nsac and sac kyua tests report > failures in my environment, long after they should have > not existed. >=20 >=20 >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) >=20 >=20 So, what should we even do here? It sort of looks like this entire section should be purged or something. There was a bit of error committing this section I guess. sean --456DsBBUd8VIHQVccdDm6Bv8inIk63ahS-- --gkGJ5Hwu4GcXO3RJyySDbHsXyae6fQBKA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAluiddNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LbNaAgAlsBRkfMZWRp0dtZV7lItyjxl+Zs6FfyME/5AsXzz2OYL1/Q6//BfQ7GQ RaFNApuNhw+tMZ7Y6Nxv/ghU/oG6Qe1u0xDBhzg5ABbOdR3zGApyFGCkv62WgTvv TwqQxqvsA2Jckz8yPYZ1Ga5G0L7eSmTeFlolcNCkiKuiF2W9NUCQtWJem7djbgP5 WiOAndJgoklffxvw9DM1fej6fLt+jSzQ8jwC3lZ/e7mJVf8bake3EM/8lFnuadn6 DdkzaoN6Wllt5K/kAoHbLok2Sdz4Z1dhvSeEVcfmzP7KKNXhRUgw5/CXZvgxyTNo qtQNTphL/UtlzW6tRlEU1lVR6QTeDA== =pHi+ -----END PGP SIGNATURE----- --gkGJ5Hwu4GcXO3RJyySDbHsXyae6fQBKA-- From owner-freebsd-current@freebsd.org Wed Sep 19 16:22: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 318C610A0F28 for ; Wed, 19 Sep 2018 16:22:49 +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 D69F688D14; Wed, 19 Sep 2018 16:22:48 +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 9DD151C7FB; Wed, 19 Sep 2018 16:22:48 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Wed, 19 Sep 2018 16:22:46 +0000 From: Glen Barber To: freebsd-current@freebsd.org Cc: FreeBSD Release Engineering Team Subject: Update to 12.0-RELEASE schedule Message-ID: <20180919162246.GC52847@FreeBSD.org> Reply-To: FreeBSD Release Engineering Team MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BeiMt4EphvRJ5ehf" Content-Disposition: inline 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, 19 Sep 2018 16:22:49 -0000 --BeiMt4EphvRJ5ehf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The 12.0-RELEASE schedule will slip while we wait for some last-minute work-in-progress to be completed before branching stable/12. The most notable work-in-progress is upgrading the in-tree OpenSSL to version 1.1.1, to avoid being stuck with an outdated OpenSSL when 1.0.x reaches end of life on January 1, 2020. There is a bit of non-trivial intrusiveness with this update, notably incompatibility with other in-tree utilities such as OpenSSH, Kerberos, and NTP. At present, the 12.0-RELEASE schedule will slip by at least one week to allow time for this work to be completed so the changes are in the tree prior to the stable/12 branch. The 12.0 schedule has been updated on the website at: https://www.freebsd.org/releases/12.0R/schedule.html Thank you in advance for your patience. Glen On behalf of: re@ --BeiMt4EphvRJ5ehf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAluid9YACgkQAxRYpUeP 4pOsCBAAneHwemD5vKTXpuqqm+Yw8jII0euj46JWf4EXlthyGpknC3Dmpz3xJEdl zyT7utGAm2n4eb5YkePnFD0yKPtj/6xaeTaaOmxKzl6wKqlgUZmzGstIwHc0ynOZ qhAykYBNPMlxtOtotSBpo6pHVXr632kCxM6As9b9GELLLoutd0m/Nr+M2jjRIAvh w8DGSgoe7OIbExuXFb7qhTC7WdpP6Zk9RVzs2AreBsHD/tpIq1JcdQVG2k5Llz+F qG3U/BDlKsvS3RxAuzf82OrvdOdf3+davUi2k6dNrx4wTk7sgnx3tvF5mjYcvIyh tQGH/Vi7rAprpCPylOrdRBSNWVmyxMvZjW3Hqo1daM5yOEsziNRBvajsfYbAmjwV HvWu1ogzstr/GHdpFpk0L04wrvbu9B0diYzy4dfM3hV3Zssvz68ipRhc2g7g1uh2 mHBw/4WENV58nMs7uK/jHAtdo3athjs3TDQXOLAUyHy0KSqnhuG6bkPvLCRDFPsj +ft39mqw3MXc/n5EWftM+FAIndRfJpa90Ku8+TQCcy209DnlwG04VIWE+PWzBCQ0 57ssv/J4AfZuGapm5h4KVn1AmnvXHJzAGe54OVEJ22O4DTLdheL/10vnUKnO2znd bivekU9G9YE5KpYSCQYfByd+0tGRP97zgJ02FCuwFXcjVNS34kc= =tEi/ -----END PGP SIGNATURE----- --BeiMt4EphvRJ5ehf-- From owner-freebsd-current@freebsd.org Wed Sep 19 16:46: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 F091010A1618 for ; Wed, 19 Sep 2018 16:46:12 +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 90530897B5 for ; Wed, 19 Sep 2018 16:46:12 +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 <0PFB00K005I24Q00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Wed, 19 Sep 2018 15:46:05 +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 <0PFB00EPZ7SL4O10@st13p35im-asmtp002.me.com>; Wed, 19 Sep 2018 15:46:00 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=2 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=934 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809190153 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-09-19_09:,, signatures=0 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: FreeBSD EFI projects Date: Wed, 19 Sep 2018 18:45:56 +0300 In-reply-to: <201809191531.w8JFVeDN024426@pdx.rh.CN85.dnsmgr.net> Cc: Greg V , Rebecca Cran , Konstantin Belousov , Warner Losh , FreeBSD Current To: "Rodney W. Grimes" References: <201809191531.w8JFVeDN024426@pdx.rh.CN85.dnsmgr.net> 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: Wed, 19 Sep 2018 16:46:13 -0000 > On 19 Sep 2018, at 18:31, Rodney W. Grimes = wrote: >=20 >> On Wed, Sep 19, 2018 at 6:06 PM, Rodney W. Grimes=20 >> wrote: >>>> On Wed, Sep 19, 2018 at 5:34 PM, Rodney W. Grimes >>>> wrote: >>>>>> On 9/18/18 4:11 AM, Greg V wrote: >>>>>>=20 >>>>>>>=20 >>>>>>> I can confirm that the kernel already worked fine when booted=20 >>>> from >>>>>>> 32-bit EFI. >>>>>>>=20 >>>>>>> I booted an old Mac into HardenedBSD using a 32-bit-EFI build=20 >>>> of >>>>>> GRUB2 :) >>>>>>=20 >>>>>>=20 >>>>>> Was that a 64-bit version of FreeBSD? My understanding is the=20 >>>> 32-bit >>>>>> FreeBSD boots fine, but 64-bit needs work. >>>>>=20 >>>>> You would be hard pressed to find a system with a 64 bit CPU that >>>>> could run 64 bit FreeBSD that had a 32 bit EFI implementation. >>>>=20 >>>> Mac mini 2006 with a Core2Duo instead of the stock CoreDuo (and the >>>> 2007 model's firmware flashed, but I don't think that impacts=20 >>>> FreeBSD). >>>=20 >>> Yes, that is one of the catagories of rare, a EFI-32 bit system that >>> was originally shipped with a 32 bit only CPU, that later got = upgraded >>> in the field with a 64 bit CPU, that still runs a EFI-32 bios. >>> Are you sure the 2007 firmware is EFI32? I would of thought >>> since they upgraded the base system to a 64 bit CPU they would >>> of shipped it with a EFI-64 bios. >>=20 >> The EFI firmware is technically 64 bit? but it only boots 32-bit=20 >> binaries. >>=20 >> = https://everymac.com/mac-answers/snow-leopard-mac-os-x-faq/mac-os-x-snow-l= eopard-64-bit-macs-64-bit-efi-boot-in-64-bit-mode.html >> 'Furthermore, it appears that although subsequently released MacBook,=20= >> MacBook Air, and pre-"Mid-2010" Mac mini models all are equipped with=20= >> "Core 2 Duo" 64-bit processors and 64-bit EFIs, Apple has blocked = these=20 >> "consumer-targeted" Macs from booting in 64-bit mode. iMac and = MacBook=20 >> Pro models released in 2007 with 64-bit EFIs seem to have been = blocked=20 >> as well.' >=20 > That is not EFI32, so that is not a test case for how FreeBSD boots = = =20 > on EFI32 systems. That is a restriction apple artificially placed > in the implementation. >=20 >>>> And probably just the 2007 model as well :) >>>>=20 >>>> Also, IIRC there were some Intel Atom tablets with 32-bit EFI. >>>=20 >>> Atom N2xx and Z5xx series Atom models cannot run x86-64 >>=20 >> Atom Z3740 ? "Instruction Set: 64-bit" >> = https://ark.intel.com/products/76759/Intel-Atom-Processor-Z3740-2M-Cache-u= p-to-1_86-GHz = >=20 > The above does not say Atom Z3xxx. If you find a Atom > N2xx or Z5xx based system it most certainly has a EFI32. >=20 >>=20 >> The tablet in question: ASUS VivoTab Note 8 (M80TA) >> https://www.asus.com/us/Tablets/ASUS_VivoTab_Note_8_M80TA/ = >=20 > I can not find enough detail to know for certain that tablet > actually has which version of EFI. > You are saying it has EFI32? And if so based on what information? >=20 I have Lenovo MIIX-300 and it has UEFI32. rgds, toomas From owner-freebsd-current@freebsd.org Wed Sep 19 17:08: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 58C2410A1DA1 for ; Wed, 19 Sep 2018 17:08:22 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-14.consmr.mail.bf2.yahoo.com (sonic311-14.consmr.mail.bf2.yahoo.com [74.6.131.124]) (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 00B4E8A115 for ; Wed, 19 Sep 2018 17:08:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: Q.L4NZQVM1mOjI4mL.g4zrH59cEdMSdl.DzL7c5ACcJyJfqgctPZXZcBNwWmegH pc5uiReV_OZJ.82PKt234LUtJaCaiwxJeu_EyRe.RmegxyAsrhl8WpHBT2O.R2UUrb1Xg_gmSMy6 rlrD8gQZx_RskVlMoWpEjCQGv5oSJg9NTwAe5UmY6qq83sXGPtdcQcZxUJBJaHSsIOxgBmK4ODzr zR6TBdDwdpvAQ4r9ak1yXR1Ix_hgdiTMM4gvZSsDSbHfEasiMGj44E.GZ_pyQfQiCnWKa0evSfB5 VsSoIuQ.lKtQ7lretbnrTmdQt6C.rPhWX3_fISjW39lgwM9.bbwY_TI_Gv7PqFOzklQ9XKesBw4J qwT5XaOR5lv.qTdupQW6jYm.wWnVMFzhvBCEg37RcAQb8wrtiPsbrlHVOE2g8FC_MgZJJKg.rVmU hzPPLNxAS20ZBbiI0oZCNe6zctEN1yQjdGDQBHj4PaEAsdMSWK6SXtCc_RTV0N5_37Ek6m0Z_MTR .pt_oyFfXgArN4BvUlGuU7z.Cv_743lWBUUPG.sqQxQXgncJQNcy3YmwEdL4nC6ejmR2_n28ZLTv ku8JiFqbgoif_leYLmXPPRuufnYDZQT6jgmbIC14I0fL4GlRIPgo_bpiNKQEV1CjBoqsDSNZahUf 0oMkwQusoG789GaHRZOZ8nITXbsGmw9hvVB5wqaRfok7pqXGaqbVKdu4hRPKRuwygdBrjlGWDVCj vn7iPIC.xIoDSpxG8YBJdS_FO2nglwWfQAqnWPEmilofqqOX3KtXV5PkhpZEK3fAkQnk6M3X2o4B NwjMKaF_OaCIF1ldK.o04a23JChv.XdW8OX4LbPwME2cSjEc2eH4Zo.GOrwTKNY0zFvYCzRuQM2. 0Uy9.tLO0pYJFHWS.ZfiQv2YrklEFhyhysLuWWNpCoNvwnhQNH94t_yWR4Z47itS2IZpZgOlZHdF hFSLUPrvgUN.AVqOf7eD9HOZOdj.QzQz_TcH__WNECqPOv51AclDsMEi85uTcnY21fWYVJQa3GYc UEaSdWa53QVY- Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.bf2.yahoo.com with HTTP; Wed, 19 Sep 2018 17:08:21 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp414.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 9b40400b4fba9e6a27c69837c3431738; Wed, 19 Sep 2018 17:08:18 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Some delete-old detrius From: Mark Millard In-Reply-To: Date: Wed, 19 Sep 2018 10:08:16 -0700 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <446D76C1-4563-43FA-8B25-3A84245385F7@yahoo.com> References: <26183B75-2CBD-4D98-A59F-85617D5D18E2@yahoo.com> To: Sean Bruno 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: Wed, 19 Sep 2018 17:08:22 -0000 On 2018-Sep-19, at 9:14 AM, Sean Bruno wrote: > On 9/18/18 8:48 PM, Mark Millard wrote: >> A problem here is that the references should be to usr.bin instead >> of usr/bin . See: >>=20 >> = https://lists.freebsd.org/pipermail/svn-src-head/2018-September/118426.htm= l >>=20 >> which reports for svn commit: r336601 - head: >>=20 >> QUOTE >> Looks like this head/ObsoleteFiles.inc update has a typo >> in each thing added to OLD_FILES . . . >>=20 >> # ls -lTdt /usr/tests/usr.bin/indent/* >> -r--r--r-- 1 root wheel 121 Sep 13 22:53:30 2018 = /usr/tests/usr.bin/indent/Kyuafile >> . . . >> -r--r--r-- 1 root wheel 295 Sep 13 22:53:29 2018 = /usr/tests/usr.bin/indent/binary.0 >> -r--r--r-- 1 root wheel 92 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0.pro >> -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0.stdout >> -r--r--r-- 1 root wheel 122 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/sac.0 >> -r--r--r-- 1 root wheel 94 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0.pro >> -r--r--r-- 1 root wheel 130 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0.stdout >> -r--r--r-- 1 root wheel 123 May 1 19:35:24 2018 = /usr/tests/usr.bin/indent/nsac.0 >>=20 >> vs. ( note usr.bin vs. usr/bin ): >>=20 >> Modified: head/ObsoleteFiles.inc >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >> --- head/ObsoleteFiles.inc Sun Jul 22 12:04:21 2018 = (r336600) >> +++ head/ObsoleteFiles.inc Sun Jul 22 12:45:02 2018 = (r336601) >> @@ -38,6 +38,13 @@ >> # xargs -n1 | sort | uniq -d; >> # done >>=20 >> +# 20180722: indent(1) option renamed, test files follow >> +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0 >> +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.pro >> +OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.stdout >> +OLD_FILES+=3Dusr/bin/indent/tests/sac.0 >> +OLD_FILES+=3Dusr/bin/indent/tests/sac.0.pro >> +OLD_FILES+=3Dusr/bin/indent/tests/sac.0.stdout >> # 20180721: move of libmlx5.so.1 and libibverbs.so.1 >> OLD_LIBS+=3Dusr/lib/libmlx5.so.1 >> OLD_LIBS+=3Dusr/lib/libibverbs.so.1 >> END QUOTE >>=20 >> This was after having the nsac and sac kyua tests report >> failures in my environment, long after they should have >> not existed. >>=20 >>=20 >>=20 >> =3D=3D=3D >> Mark Millard >> marklmi at yahoo.com >> ( dsl-only.net went >> away in early 2018-Mar) >>=20 >>=20 >=20 > So, what should we even do here? It sort of looks like this entire > section should be purged or something. >=20 > There was a bit of error committing this section I guess. As near as I can tell the fix would be something like: # svnlite diff /usr/src/ObsoleteFiles.inc Index: /usr/src/ObsoleteFiles.inc =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/ObsoleteFiles.inc (revision 338675) +++ /usr/src/ObsoleteFiles.inc (working copy) @@ -48,12 +48,12 @@ # 20180725: Cleanup old libcasper.so.0 OLD_LIBS+=3Dlib/libcasper.so.0 # 20180722: indent(1) option renamed, test files follow -OLD_FILES+=3Dusr/bin/indent/tests/nsac.0 -OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.pro -OLD_FILES+=3Dusr/bin/indent/tests/nsac.0.stdout -OLD_FILES+=3Dusr/bin/indent/tests/sac.0 -OLD_FILES+=3Dusr/bin/indent/tests/sac.0.pro -OLD_FILES+=3Dusr/bin/indent/tests/sac.0.stdout +OLD_FILES+=3Dusr/tests/usr.bin/indent/nsac.0 +OLD_FILES+=3Dusr/tests/usr.bin/indent/nsac.0.pro +OLD_FILES+=3Dusr/tests/usr.bin/indent/nsac.0.stdout +OLD_FILES+=3Dusr/tests/usr.bin/indent/sac.0 +OLD_FILES+=3Dusr/tests/usr.bin/indent/sac.0.pro +OLD_FILES+=3Dusr/tests/usr.bin/indent/sac.0.stdout # 20180721: move of libmlx5.so.1 and libibverbs.so.1 OLD_LIBS+=3Dusr/lib/libmlx5.so.1 OLD_LIBS+=3Dusr/lib/libibverbs.so.1 This is sort of like the older part of the file: # 20170322: rename to _test to match the FreeBSD test suite name = scheme OLD_FILES+=3Dusr/tests/usr.bin/col/col OLD_FILES+=3Dusr/tests/usr.bin/diff/diff OLD_FILES+=3Dusr/tests/usr.bin/ident/ident OLD_FILES+=3Dusr/tests/usr.bin/mkimg/mkimg OLD_FILES+=3Dusr/tests/usr.bin/sdiff/sdiff OLD_FILES+=3Dusr/tests/usr.bin/soelim/soelim OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_config OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_etcdir OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_groupadd OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_groupdel OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_groupmod OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_lock OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_useradd OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_userdel OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_usermod OLD_FILES+=3Dusr/tests/usr.sbin/pw/pw_usernext =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Wed Sep 19 20:02: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 9706C10A5618 for ; Wed, 19 Sep 2018 20:02:38 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A68F9016A for ; Wed, 19 Sep 2018 20:02:38 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w8JK1qiJ001191 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 19 Sep 2018 13:01:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w8JK1qHP001190 for freebsd-current@freebsd.org; Wed, 19 Sep 2018 13:01:52 -0700 (PDT) (envelope-from sgk) Date: Wed, 19 Sep 2018 13:01:52 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: ALPHA4 panic in VM Message-ID: <20180919200152.GA1164@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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, 19 Sep 2018 20:02:38 -0000 I have the kernel and core file if more information is needed. % cat info.2 Dump header from device: /dev/ada0p3 Architecture: amd64 Architecture Version: 2 Dump Length: 2348281856 Blocksize: 512 Compression: none Dumptime: Wed Sep 19 12:29:59 2018 Hostname: troutmask.apl.washington.edu Magic: FreeBSD Kernel Dump Version String: FreeBSD 12.0-ALPHA4 #0 r338505: Thu Sep 6 13:45:34 PDT 2018 kargl@troutmask.apl.washington.edu:/usr/obj/usr/src/amd64.amd64/sys/SPEW Panic String: page fault Dump Parity: 2676008548 Bounds: 2 Dump Status: good % more core.txt.2 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 11 fault virtual address = 0xffffb8000719a428 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff808213ab stack pointer = 0x28:0xfffffe0099d0b710 frame pointer = 0x28:0xfffffe0099d0b730 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 = 65343 (Web Content) trap number = 12 panic: page fault cpuid = 1 time = 1537385399 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0099d0b3c0 vpanic() at vpanic+0x1a3/frame 0xfffffe0099d0b420 panic() at panic+0x43/frame 0xfffffe0099d0b480 trap_fatal() at trap_fatal+0x35f/frame 0xfffffe0099d0b4d0 trap_pfault() at trap_pfault+0x49/frame 0xfffffe0099d0b530 trap() at trap+0x2a3/frame 0xfffffe0099d0b640 calltrap() at calltrap+0x8/frame 0xfffffe0099d0b640 --- trap 0xc, rip = 0xffffffff808213ab, rsp = 0xfffffe0099d0b710, rbp = 0xfffffe0099d0b730 --- swap_release_by_cred() at swap_release_by_cred+0x1b/frame 0xfffffe0099d0b730 vm_object_terminate() at vm_object_terminate+0x27d/frame 0xfffffe0099d0b780 vm_object_deallocate() at vm_object_deallocate+0x457/frame 0xfffffe0099d0b7e0 _vm_map_unlock() at _vm_map_unlock+0xb9/frame 0xfffffe0099d0b800 vm_map_remove() at vm_map_remove+0x99/frame 0xfffffe0099d0b830 vmspace_exit() at vmspace_exit+0xcd/frame 0xfffffe0099d0b870 exit1() at exit1+0x4ab/frame 0xfffffe0099d0b8e0 sys_sys_exit() at sys_sys_exit+0xd/frame 0xfffffe0099d0b8f0 amd64_syscall() at amd64_syscall+0x219/frame 0xfffffe0099d0ba30 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0099d0ba30 --- syscall (1, FreeBSD ELF64, sys_sys_exit), rip = 0x2013433da, rsp = 0x7fffffffdc98, rbp = 0x3 --- Uptime: 12d22h19m36s __curthread () at ./machine/pcpu.h:230 230 __asm("movq %%gs:%1,%0" : "=r" (td) (kgdb) #0 __curthread () at ./machine/pcpu.h:230 #1 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff805c595b in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:446 #3 0xffffffff805c5d93 in vpanic (fmt=, ap=0xfffffe0099d0b460) at /usr/src/sys/kern/kern_shutdown.c:872 #4 0xffffffff805c5b83 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:799 #5 0xffffffff8087cd7f in trap_fatal (frame=0xfffffe0099d0b650, eva=18446664908991472680) at /usr/src/sys/amd64/amd64/trap.c:928 #6 0xffffffff8087cdd9 in trap_pfault (frame=0xfffffe0099d0b650, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:760 #7 0xffffffff8087c483 in trap (frame=0xfffffe0099d0b650) at /usr/src/sys/amd64/amd64/trap.c:441 #8 #9 0xffffffff808213ab in swap_release_by_cred (decr=28672, cred=0xffffb8000719a400) at /usr/src/sys/vm/swap_pager.c:296 #10 0xffffffff8083e07d in vm_object_destroy (object=) at /usr/src/sys/vm/vm_object.c:703 #11 vm_object_terminate (object=0xfffff807cecf7400) at /usr/src/sys/vm/vm_object.c:836 #12 0xffffffff8083d357 in vm_object_deallocate (object=0xfffff807cecf7400) at /usr/src/sys/vm/vm_object.c:684 #13 0xffffffff80833459 in vm_map_entry_deallocate ( system_map=, entry=) at /usr/src/sys/vm/vm_map.c:3001 #14 vm_map_process_deferred () at /usr/src/sys/vm/vm_map.c:541 #15 _vm_map_unlock (map=, file=, line=) at /usr/src/sys/vm/vm_map.c:554 #16 0xffffffff80837989 in vm_map_remove (map=0xfffff8019c580000, start=4096, end=140737488355328) at /usr/src/sys/vm/vm_map.c:3199 #17 0xffffffff8083322d in vmspace_dofree (vm=) at /usr/src/sys/vm/vm_map.c:342 #18 vmspace_exit (td=0xfffff80007524000) at /usr/src/sys/vm/vm_map.c:423 #19 0xffffffff8058c7ab in exit1 (td=0xfffff80007524000, rval=, signo=) at /usr/src/sys/kern/kern_exit.c:402 #20 0xffffffff8058c2fd in sys_sys_exit (td=0x7000, uap=) at /usr/src/sys/kern/kern_exit.c:180 #21 0xffffffff8087d609 in syscallenter (td=0xfffff80007524000) at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:135 #22 amd64_syscall (td=0xfffff80007524000, traced=0) at /usr/src/sys/amd64/amd64/trap.c:1043 #23 #24 0x00000002013433da in ?? () -- Steve From owner-freebsd-current@freebsd.org Wed Sep 19 21:02: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 7B71C10A6C27 for ; Wed, 19 Sep 2018 21:02:17 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) (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 F15BA91FED for ; Wed, 19 Sep 2018 21:02:16 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pg1-x544.google.com with SMTP id r1-v6so3301722pgp.11 for ; Wed, 19 Sep 2018 14:02:16 -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=pWddn/QWkpy8z0+vdtUHL7VlDU8QeZH+BE5YufhlRUc=; b=D51ztrmDUoRt2eOwMVGpDI4/4u7uHoqlvg7J3K8S48Qq16P1nHKlHKdsICmmfYrJee L5OHOH4+gaDBpEHEaj7LEQ9qscwe5Ja8B4VhUw1GySBD5834hTYFRxg66E893rDKhzUj A37mxY+o80wlD554nn4cKsTDN3IxqoPPbDNCpbhSUI3EHlGtvU1ZKO26xKB21LI2hRRO j1mqvm2TR/rFgwdP5QJTdDzUv3myoG79SULKlt7Yb5Dv74pl8z4/qcKMDZggOyWdE8RW sNOCWJsyP3WoYW0bAL+Je6XFGOkDQOg/N0mADSLvkTDvBBPWCO0hZpcqvmdOC+AiWFAO WKJg== 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=pWddn/QWkpy8z0+vdtUHL7VlDU8QeZH+BE5YufhlRUc=; b=jgaTkeJWyKK0dmvps+x3KEuljXvlLFXK6qXiw9NYIFSIGUnkhstrhey2XKPEnDbKsh d+tdCRb3qzeuvCHs6NXzpT91KTq2DBxf4F1RLfrP15Ovt2LKJKe6GAyc/XFCzGqVfCMG 1D1LVoxOvU9yo2lnRaHnXgX2JbqUncYNPyCjiRpqLYMdN3DesXOvKAtvYwPVe8XiCtno eftosUJwPeCc9eScE0GDm7XZtSozG7KRrla8A2kB4n1tViuxJj9PruWukpVb7YRlYoGo Az/VNXxea9w4eOVSBZ3oHa006HuriIftxXNx/Tl2UL4ueiLPyEghZSWvq+DPE0RkejKc golA== X-Gm-Message-State: APzg51Bu6qq1Jm0EO4eqAaD1orKeCar4B9VmAHA+66lrJ2Wij2uFijqW epOo2IMABQGN69AIja2C74KvCVK1 X-Google-Smtp-Source: ANB0VdZFeZZ2+K+X0aHT5TYXVDEHQM5MckortaFFLVbN/Qe6B3wfJWjpHAy2ukXnVeIK6uaxk6KXUA== X-Received: by 2002:a65:654d:: with SMTP id a13-v6mr33313602pgw.35.1537390935809; Wed, 19 Sep 2018 14:02:15 -0700 (PDT) Received: from raichu (toroon0560w-lp130-01-174-88-78-8.dsl.bell.ca. [174.88.78.8]) by smtp.gmail.com with ESMTPSA id j5-v6sm27738513pff.139.2018.09.19.14.02.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Sep 2018 14:02:14 -0700 (PDT) Sender: Mark Johnston Date: Wed, 19 Sep 2018 17:02:11 -0400 From: Mark Johnston To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: ALPHA4 panic in VM Message-ID: <20180919210211.GC99168@raichu> References: <20180919200152.GA1164@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180919200152.GA1164@troutmask.apl.washington.edu> 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, 19 Sep 2018 21:02:17 -0000 On Wed, Sep 19, 2018 at 01:01:52PM -0700, Steve Kargl wrote: > I have the kernel and core file if more information is needed. > > % cat info.2 > Dump header from device: /dev/ada0p3 Architecture: amd64 > Architecture Version: 2 > Dump Length: 2348281856 > Blocksize: 512 > Compression: none > Dumptime: Wed Sep 19 12:29:59 2018 > Hostname: troutmask.apl.washington.edu > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 12.0-ALPHA4 #0 r338505: Thu Sep 6 13:45:34 PDT 2018 > kargl@troutmask.apl.washington.edu:/usr/obj/usr/src/amd64.amd64/sys/SPEW > Panic String: page fault > Dump Parity: 2676008548 > Bounds: 2 > Dump Status: good > > % more core.txt.2 > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 11 > fault virtual address = 0xffffb8000719a428 This seems to be the result of a bit-flip. cred is 0xffffb8000719a400, which is almost but not quite in the direct map. In particular we have: (kgdb) frame 10 #10 0xffffffff8083e07d in vm_object_destroy (object=) at /usr/src/sys/vm/vm_object.c:703 703 swap_release_by_cred(object->charge, object->cred); (kgdb) p object $8 = (kgdb) p *(vm_object_t)$r13 $9 = { ... cred = 0xffffb8000719a400, charge = 28672, umtx_data = 0x0 } (kgdb) p *(struct ucred *)0xfffff8000719a400 $10 = { cr_ref = 5737, cr_uid = 1001, cr_ruid = 1001, cr_svuid = 1001, cr_ngroups = 7, cr_rgid = 1001, cr_svgid = 1001, cr_uidinfo = 0xfffff80007285500, cr_ruidinfo = 0xfffff80007285500, cr_prison = 0xffffffff80a9de10 , ... That is, flipping one of the bits in the fault address leads me to a valid ucred. This could in principle be the result of a software bug, but I'd be more inclined to suspect the hardware. From owner-freebsd-current@freebsd.org Wed Sep 19 21:11: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 25BCB10A704A for ; Wed, 19 Sep 2018 21:11:59 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B0D0192573; Wed, 19 Sep 2018 21:11:58 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w8JLBu6r001747 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 Sep 2018 14:11:56 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w8JLBu2t001746; Wed, 19 Sep 2018 14:11:56 -0700 (PDT) (envelope-from sgk) Date: Wed, 19 Sep 2018 14:11:56 -0700 From: Steve Kargl To: Mark Johnston Cc: freebsd-current@freebsd.org Subject: Re: ALPHA4 panic in VM Message-ID: <20180919211156.GA1677@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180919200152.GA1164@troutmask.apl.washington.edu> <20180919210211.GC99168@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180919210211.GC99168@raichu> 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, 19 Sep 2018 21:11:59 -0000 On Wed, Sep 19, 2018 at 05:02:11PM -0400, Mark Johnston wrote: > On Wed, Sep 19, 2018 at 01:01:52PM -0700, Steve Kargl wrote: > > I have the kernel and core file if more information is needed. > > > > % cat info.2 > > Dump header from device: /dev/ada0p3 > Architecture: amd64 > > Architecture Version: 2 > > Dump Length: 2348281856 > > Blocksize: 512 > > Compression: none > > Dumptime: Wed Sep 19 12:29:59 2018 > > Hostname: troutmask.apl.washington.edu > > Magic: FreeBSD Kernel Dump > > Version String: FreeBSD 12.0-ALPHA4 #0 r338505: Thu Sep 6 13:45:34 PDT 2018 > > kargl@troutmask.apl.washington.edu:/usr/obj/usr/src/amd64.amd64/sys/SPEW > > Panic String: page fault > > Dump Parity: 2676008548 > > Bounds: 2 > > Dump Status: good > > > > % more core.txt.2 > > Fatal trap 12: page fault while in kernel mode > > cpuid = 1; apic id = 11 > > fault virtual address = 0xffffb8000719a428 > > This seems to be the result of a bit-flip. cred is 0xffffb8000719a400, > which is almost but not quite in the direct map. In particular we have: > > (kgdb) frame 10 > #10 0xffffffff8083e07d in vm_object_destroy (object=) at /usr/src/sys/vm/vm_object.c:703 > 703 swap_release_by_cred(object->charge, object->cred); > (kgdb) p object > $8 = > (kgdb) p *(vm_object_t)$r13 > $9 = { > ... > cred = 0xffffb8000719a400, > charge = 28672, > umtx_data = 0x0 > } > (kgdb) p *(struct ucred *)0xfffff8000719a400 > $10 = { > cr_ref = 5737, > cr_uid = 1001, > cr_ruid = 1001, > cr_svuid = 1001, > cr_ngroups = 7, > cr_rgid = 1001, > cr_svgid = 1001, > cr_uidinfo = 0xfffff80007285500, > cr_ruidinfo = 0xfffff80007285500, > cr_prison = 0xffffffff80a9de10 , > ... > > That is, flipping one of the bits in the fault address leads me to a > valid ucred. This could in principle be the result of a software bug, > but I'd be more inclined to suspect the hardware. Mark, Thanks for looking into the problem. This system has been running for probably 2 years or so without issues. I guess it's time to pull out memtest86+ (or similar) to see if hardware is starting to fail. -- Steve From owner-freebsd-current@freebsd.org Wed Sep 19 21:20: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 4B81F10A7300 for ; Wed, 19 Sep 2018 21:20:40 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf1-x442.google.com (mail-pf1-x442.google.com [IPv6:2607:f8b0:4864:20::442]) (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 C2696929D6 for ; Wed, 19 Sep 2018 21:20:39 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf1-x442.google.com with SMTP id k19-v6so3295938pfi.1 for ; Wed, 19 Sep 2018 14:20:39 -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=ghtrHvVclQpavdc4n9qN4ihwCjvG/IHw9n42hpRRYP8=; b=AMBtPfge6oNvqY9DKijTm49T3DDFCQkX1aUFPYko0O456KM7JBin3orf9q162ZM3Hz d6lWXMNDmaZO1ek4eWZD0pUpYWWQ7F9W7J4w8o0A/uDcjCi8W9qNZdotUIHOyfNXRq7t uhtprgIF8Gk2zmrJlkJ/4fVffqnKzN7glkqbbw/W550ZQbKY9uZByoe9HgsR7YbqvUFz ujovZUf+7dwippYdzP48FKYT7BzsJ9hut5wsRSK0m8ETpPdW7dN5OU+vThOpsbY8wPdJ KcPFlVK9yz80W9ra6JfeZ52qDCQ7Q5goG3VCX4wxqA+NOj3xofA16tLwpAYrC3Fg2qjJ a4OQ== 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=ghtrHvVclQpavdc4n9qN4ihwCjvG/IHw9n42hpRRYP8=; b=amPTjXLNM2BN7Q8g04Ie3vJKvWq/bLvHBohlvQkjBpSEeyE6GOZVl5/KKlux2wOATh 12JcL7oZIQsSNy/mATSD8u84Xm6H+MUZn49KTiO4p27nAnmXetYZ+80tj0x8iDEucSmQ P5bLy+d4EVJopUS/h7F9c9kyQE6iUf6v1E5vz1r8l4icNhxiLcMfGBfmMTZKSxMRceog xaLOVz7kq8IJKjYtKA1MMS0+u8Q4hyj4S7NN2uoFXkxAxbr4oNZre3z7Dn4nC+NZ3FEF UrOiDHNDBDNxWGTi2bvVjQ63mcA1EZ05rl6mww1s5w7HUjCVeGyZeIMnMPDKssCs4Gli gQGw== X-Gm-Message-State: APzg51Cw3b9hHMxytaYQu+Vpmbay7T8LV/6nzITsGMvPdJjJnZaMYfM9 enYBTy1+LdscU9l9tqV2NLXjw+XS X-Google-Smtp-Source: ANB0VdZzGjz7Ko79S3n/iPPQfq2guIOdDgheCisb8/Y6JamMYn6Yeibva/E+5CiktbjmbhOUSGTjJQ== X-Received: by 2002:a62:dbc5:: with SMTP id f188-v6mr38448775pfg.182.1537392038544; Wed, 19 Sep 2018 14:20:38 -0700 (PDT) Received: from raichu (toroon0560w-lp130-01-174-88-78-8.dsl.bell.ca. [174.88.78.8]) by smtp.gmail.com with ESMTPSA id o21-v6sm36072151pfa.54.2018.09.19.14.20.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Sep 2018 14:20:37 -0700 (PDT) Sender: Mark Johnston Date: Wed, 19 Sep 2018 17:20:34 -0400 From: Mark Johnston To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: ALPHA4 panic in VM Message-ID: <20180919212034.GD99168@raichu> References: <20180919200152.GA1164@troutmask.apl.washington.edu> <20180919210211.GC99168@raichu> <20180919211156.GA1677@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180919211156.GA1677@troutmask.apl.washington.edu> 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, 19 Sep 2018 21:20:40 -0000 On Wed, Sep 19, 2018 at 02:11:56PM -0700, Steve Kargl wrote: > On Wed, Sep 19, 2018 at 05:02:11PM -0400, Mark Johnston wrote: > > On Wed, Sep 19, 2018 at 01:01:52PM -0700, Steve Kargl wrote: > > > I have the kernel and core file if more information is needed. > > > > > > % cat info.2 > > > Dump header from device: /dev/ada0p3 > > Architecture: amd64 > > > Architecture Version: 2 > > > Dump Length: 2348281856 > > > Blocksize: 512 > > > Compression: none > > > Dumptime: Wed Sep 19 12:29:59 2018 > > > Hostname: troutmask.apl.washington.edu > > > Magic: FreeBSD Kernel Dump > > > Version String: FreeBSD 12.0-ALPHA4 #0 r338505: Thu Sep 6 13:45:34 PDT 2018 > > > kargl@troutmask.apl.washington.edu:/usr/obj/usr/src/amd64.amd64/sys/SPEW > > > Panic String: page fault > > > Dump Parity: 2676008548 > > > Bounds: 2 > > > Dump Status: good > > > > > > % more core.txt.2 > > > Fatal trap 12: page fault while in kernel mode > > > cpuid = 1; apic id = 11 > > > fault virtual address = 0xffffb8000719a428 > > > > This seems to be the result of a bit-flip. cred is 0xffffb8000719a400, > > which is almost but not quite in the direct map. In particular we have: > > > > (kgdb) frame 10 > > #10 0xffffffff8083e07d in vm_object_destroy (object=) at /usr/src/sys/vm/vm_object.c:703 > > 703 swap_release_by_cred(object->charge, object->cred); > > (kgdb) p object > > $8 = > > (kgdb) p *(vm_object_t)$r13 > > $9 = { > > ... > > cred = 0xffffb8000719a400, > > charge = 28672, > > umtx_data = 0x0 > > } > > (kgdb) p *(struct ucred *)0xfffff8000719a400 > > $10 = { > > cr_ref = 5737, > > cr_uid = 1001, > > cr_ruid = 1001, > > cr_svuid = 1001, > > cr_ngroups = 7, > > cr_rgid = 1001, > > cr_svgid = 1001, > > cr_uidinfo = 0xfffff80007285500, > > cr_ruidinfo = 0xfffff80007285500, > > cr_prison = 0xffffffff80a9de10 , > > ... > > > > That is, flipping one of the bits in the fault address leads me to a > > valid ucred. This could in principle be the result of a software bug, > > but I'd be more inclined to suspect the hardware. > > Mark, > > Thanks for looking into the problem. This system has > been running for probably 2 years or so without issues. > I guess it's time to pull out memtest86+ (or similar) > to see if hardware is starting to fail. I'm not sure whether you're using ECC RAM, but if not, the system is susceptible to silent random bit flips. From owner-freebsd-current@freebsd.org Wed Sep 19 21:22: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 D0C7C10A7500 for ; Wed, 19 Sep 2018 21:22:50 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 30BEF92E41 for ; Wed, 19 Sep 2018 21:22:49 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 909F935D94; Wed, 19 Sep 2018 15:23:22 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id t0gzUm-JFOzW; Wed, 19 Sep 2018 15:23:21 -0600 (MDT) Received: from c02t93w9h03m.hgst.com (unknown [199.255.45.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Wed, 19 Sep 2018 15:23:21 -0600 (MDT) Subject: Re: FreeBSD EFI projects To: "Rodney W. Grimes" , Greg V Cc: Konstantin Belousov , Warner Losh , FreeBSD Current References: <201809191506.w8JF6W10024280@pdx.rh.CN85.dnsmgr.net> From: Rebecca Cran Message-ID: <8d0769ac-e2cc-a063-978d-2db9116655b5@bluestop.org> Date: Wed, 19 Sep 2018 15:22:44 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <201809191506.w8JF6W10024280@pdx.rh.CN85.dnsmgr.net> 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, 19 Sep 2018 21:22:51 -0000 On 9/19/18 9:06 AM, Rodney W. Grimes wrote: > Yes, that is one of the catagories of rare, a EFI-32 bit system that > was originally shipped with a 32 bit only CPU, that later got upgraded > in the field with a 64 bit CPU, that still runs a EFI-32 bios. > Are you sure the 2007 firmware is EFI32? I would of thought > since they upgraded the base system to a 64 bit CPU they would > of shipped it with a EFI-64 bios. I'm not sure if there's a firmware upgrade for it, but I have a MacBook Pro from around that time that definitely has a 32-bit EFI: it only runs 32-bit binaries, and had a 32-bit version of MacOS X installed despite having a 64-bit Core2Duo CPU. -- Rebecca From owner-freebsd-current@freebsd.org Wed Sep 19 21:24: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 693FB10A75DB for ; Wed, 19 Sep 2018 21:24:21 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 F23E992FB1 for ; Wed, 19 Sep 2018 21:24:20 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id DAF1135D9C; Wed, 19 Sep 2018 15:24:54 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3Djf6CboCJKV; Wed, 19 Sep 2018 15:24:54 -0600 (MDT) Received: from c02t93w9h03m.hgst.com (unknown [199.255.45.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Wed, 19 Sep 2018 15:24:53 -0600 (MDT) Subject: Re: FreeBSD EFI projects To: Greg V Cc: Konstantin Belousov , Warner Losh , FreeBSD Current References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> <20180917200935.GD3161@kib.kiev.ua> <1537265515.2378.0@hraggstad.unrelenting.technology> <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> <20180919095357.qwmm6p3pkbli4zww@unrelenting.technology> From: Rebecca Cran Message-ID: Date: Wed, 19 Sep 2018 15:24:17 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180919095357.qwmm6p3pkbli4zww@unrelenting.technology> 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, 19 Sep 2018 21:24:21 -0000 On 9/19/18 3:53 AM, Greg V wrote: > > Yes, of course it was 64-bit. > > I don't think I ever downloaded the 32-bit one... And are you sure it was booted via EFI and not the BIOS emulation CSM (Compatibility Support Module)? I'm fairly sure we _don't_ support booting a 64-bit kernel from 32-bit EFI yet. -- Rebecca From owner-freebsd-current@freebsd.org Wed Sep 19 21:41: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 09FEF10A7F4E for ; Wed, 19 Sep 2018 21:41:46 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.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 A399293D51 for ; Wed, 19 Sep 2018 21:41:45 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 674D710A7F4D; Wed, 19 Sep 2018 21:41:45 +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 55FEA10A7F4C for ; Wed, 19 Sep 2018 21:41:45 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F006693D4B; Wed, 19 Sep 2018 21:41:44 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.128] (helo=rmmprod06.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1g2kEB-0004A3-2Y; Wed, 19 Sep 2018 23:41:43 +0200 Received: from mail by rmmprod06.runbox with local (Exim 4.86_2) (envelope-from ) id 1g2kEA-0007h4-SF; Wed, 19 Sep 2018 23:41:42 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Wed, 19 Sep 2018 21:41:42 GMT From: "Jeffrey Bouquet" To: "Ed Maste" CC: "current" Subject: Re: just a FYI Date: Wed, 19 Sep 2018 14:41:42 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: Message-Id: 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, 19 Sep 2018 21:41:46 -0000 On Wed, 19 Sep 2018 09:58:19 -0400, Ed Maste wrote: > On 19 September 2018 at 09:28, Jeffrey Bouquet > wrote: > > /usr/ports/security/lockdown [ sorry if this is a PR or for ports- ] >=20 > Unfortunately this port has no maintainer, so fixing this is going to > need someone to take an interest in the port. I had a quick look at > the script and it looks like it sets obsolete flags that would result > in an unbootable system. >=20 > In any case, would you kindly submit a PR for the issue to track it? > I'll try to get it marked FORBIDDEN (or similar) for now. > _______________________________________________ > 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" Bug # 231489 submitted.=20= From owner-freebsd-current@freebsd.org Wed Sep 19 23:13: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 7074710A9DA1 for ; Wed, 19 Sep 2018 23:13:25 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::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 05924970E3 for ; Wed, 19 Sep 2018 23:13:25 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x235.google.com with SMTP id j81-v6so10724890ite.0 for ; Wed, 19 Sep 2018 16:13:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=wq1UWSWCnx0LOAx9ywdJHomx5R5Va6RM+vKeCv/YqSo=; b=NJWq+uovVWfOTGghBeaa1owpUmObaJeF3WwZ4Abkrs0lqL5RPcZ5hIg8u1HeOP8oYL /UN6YZn+s9apEFvBBqmjMToH2t2KBqsnc9jhytWwZe4y6xn/tyTnEdKZYbQH7foCGEFh aXTSrvc7Yn/rc7iQiahvJJVTAeyDUcvMmfbv+aRr7hQuM8m1OTjD/EFJCchiM1i7AQkh WDJWlK+bXSUiEYYauCjkSHCVDcMlQphSyAZWtEwlhLnRtkJf4CRMwtN5OYaO9nD6nPu1 /ljmQGTPzAECKww06lqnscQ4LpylQawWu4MHXXTXTcNGVBi4ZBN7buu3IQtPOtvyWLpf p+lQ== 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=wq1UWSWCnx0LOAx9ywdJHomx5R5Va6RM+vKeCv/YqSo=; b=BRAFWweLj/GMI3Pu8GP9W2kPxF8CHUghDReZDrq00vkmzn7YtmWhM5HpRpCUYzVxSq Fx09y5cz4iyZWP2egjL8X9H1prDId4ojpXldREodGtTzEX/pCYbY6QldsBT/zFF7RABe TJR4Xg+KQxXxC+UaWIK/3AazpCKAWa3mHZc+1nIddsNW7EjsJdSKD1fX9wqH6MCVXSnn fXfuqoTz5X/ZCEDxcM8+FSBAo1My0N5EOq2PCDReDQtaw7vDt5AFGMMnUIPFGgEFOsi5 QRg2eqjvC7+KcIqln5yRboH9N4KQXXNYKPCGGPuRNF7Fih96O+PlsWFzEAZEKlrEViZP +ZPA== X-Gm-Message-State: APzg51BP+JvozcPEqzCFPvjFlDyI0YZBlVjythk6mmh20AJkAjETsNHx RAwhfu9JOoVDw1htQ9M3AOHYeD1B8ui/LhmQORY= X-Google-Smtp-Source: ANB0VdYY7F/3MKw598yU/MxPyMR0eaHGv7XJar63dGO9EwTGQLIlHDlRGTN7qtCnuFzsDxtWV2C0MpyuxpjFRhbSB1U= X-Received: by 2002:a24:e9c6:: with SMTP id f189-v6mr175959ith.118.1537398804500; Wed, 19 Sep 2018 16:13:24 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:404:0:0:0:0:0 with HTTP; Wed, 19 Sep 2018 16:13:03 -0700 (PDT) In-Reply-To: <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> References: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> From: Ed Maste Date: Wed, 19 Sep 2018 19:13:03 -0400 X-Google-Sender-Auth: j0hF71AC0BDZbrOeianzg_i45Pk Message-ID: Subject: Re: FreeBSD EFI projects To: "Rodney W. Grimes" Cc: Rebecca Cran , Greg V , Konstantin Belousov , Warner Losh , 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, 19 Sep 2018 23:13:25 -0000 On 19 September 2018 at 10:34, Rodney W. Grimes wrote: > > You would be hard pressed to find a system with a 64 bit CPU that > could run 64 bit FreeBSD that had a 32 bit EFI implementation. The Minnowboard Turbot has an Atom E3826, and has four precompiled Tianocore UEFI firmware releases available: 32 and 64 bit in release and debug builds. It's probably the most approachable development platform for UEFI work on FreeBSD. From owner-freebsd-current@freebsd.org Wed Sep 19 23:26: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 3CF4310AA110 for ; Wed, 19 Sep 2018 23:26:50 +0000 (UTC) (envelope-from tim.rice@xinuos.com) Received: from zhost.uxsglobal.com (zhost.xinuos.com [144.202.236.63]) (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 E19B3976EA for ; Wed, 19 Sep 2018 23:26:49 +0000 (UTC) (envelope-from tim.rice@xinuos.com) Received: from zhost.uxsglobal.com (localhost [127.0.0.1]) by zhost.uxsglobal.com (Postfix) with ESMTPS id 1354388031C for ; Wed, 19 Sep 2018 19:26:43 -0400 (EDT) Received: from zhost.uxsglobal.com (localhost [127.0.0.1]) by zhost.uxsglobal.com (Postfix) with ESMTPS id EF16A880682 for ; Wed, 19 Sep 2018 19:26:42 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.9.2 zhost.uxsglobal.com EF16A880682 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xinuos.com; s=710E410E-A6C0-11E6-9C55-A8275FB0EC07; t=1537399603; bh=xJyeICvIWtVvgo8PN/pgxspq4snGvhZ9NHvxZPzduCg=; h=Subject:To:From:Message-ID:Date:MIME-Version:Content-Type; b=AiE+UeBTlCCq9i+KGoP5A3rHsBiSci3ozZAgflsqepvD4SkKBaj8Rc3m+veXXHpEk BuOidNiBM6rZioTY2vtI5ZaD6od55eqBzbHyopbJ8QfqQMhnE44rQYZsQ6DuwFi7Ph jVIRBC+5iBx4dnU7vOF++XJmaFqFW1dMwKZfw1r0= Received: from ws10.int.multitalents.net (fw01.multitalents.net [173.164.249.129]) by zhost.uxsglobal.com (Postfix) with ESMTPSA id A73F788031C for ; Wed, 19 Sep 2018 19:26:42 -0400 (EDT) Subject: Re: Update to 12.0-RELEASE schedule To: freebsd-current@freebsd.org References: <20180919162246.GC52847@FreeBSD.org> From: Tim Rice Message-ID: <25333f00-4de5-2f65-e4db-b16558739b8e@xinuos.com> Date: Wed, 19 Sep 2018 16:26:41 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20180919162246.GC52847@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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, 19 Sep 2018 23:26:50 -0000 On 09/19/18 09:22, Glen Barber wrote: > The 12.0-RELEASE schedule will slip while we wait for some last-minute > work-in-progress to be completed before branching stable/12. > > The most notable work-in-progress is upgrading the in-tree OpenSSL to > version 1.1.1, to avoid being stuck with an outdated OpenSSL when 1.0.x > reaches end of life on January 1, 2020. There is a bit of non-trivial > intrusiveness with this update, notably incompatibility with other > in-tree utilities such as OpenSSH, Kerberos, and NTP. FYI, OpenSSH got openssl-1.1.x API support on Sep 13 starting with this commit. > commit 482d23bcacdd3664f21cc82a5135f66fc598275f > Author: djm@openbsd.org > Date: Thu Sep 13 02:08:33 2018 +0000 > > upstream: hold our collective noses and use the openssl-1.1.x API in > > OpenSSH; feedback and ok tb@ jsing@ markus@ > > OpenBSD-Commit-ID: cacbcac87ce5da0d3ca7ef1b38a6f7fb349e4417 > At present, the 12.0-RELEASE schedule will slip by at least one week to > allow time for this work to be completed so the changes are in the tree > prior to the stable/12 branch. > > The 12.0 schedule has been updated on the website at: > > https://www.freebsd.org/releases/12.0R/schedule.html > > Thank you in advance for your patience. > > Glen > On behalf of: re@ > -- Tim Rice From owner-freebsd-current@freebsd.org Wed Sep 19 23:33:53 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 3950710AA3AF for ; Wed, 19 Sep 2018 23:33:53 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 BED5897B27; Wed, 19 Sep 2018 23:33:52 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 83F6E35E4C; Wed, 19 Sep 2018 17:34:26 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7ZhTEBzOZzfj; Wed, 19 Sep 2018 17:34:24 -0600 (MDT) Received: from c02t93w9h03m.hgst.com (unknown [199.255.45.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Wed, 19 Sep 2018 17:34:24 -0600 (MDT) Subject: Re: FreeBSD EFI projects To: Ed Maste , "Rodney W. Grimes" Cc: Greg V , Konstantin Belousov , Warner Losh , FreeBSD Current References: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> From: Rebecca Cran Message-ID: <4f40c03a-1e7a-0f09-5780-3ce6b0ec1a4e@bluestop.org> Date: Wed, 19 Sep 2018 17:33:48 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; 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: Wed, 19 Sep 2018 23:33:53 -0000 On 9/19/18 5:13 PM, Ed Maste wrote: > > The Minnowboard Turbot has an Atom E3826, and has four precompiled > Tianocore UEFI firmware releases available: 32 and 64 bit in release > and debug builds. It's probably the most approachable development > platform for UEFI work on FreeBSD. Oh, that's a really good point - thanks! I happen to have a Minnowboard Turbot currently sitting unused. -- Rebecca From owner-freebsd-current@freebsd.org Wed Sep 19 23:37: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 BE6A810AA4E9 for ; Wed, 19 Sep 2018 23:37:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (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 5C01797D9F for ; Wed, 19 Sep 2018 23:37:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x242.google.com with SMTP id p79-v6so10760488itp.3 for ; Wed, 19 Sep 2018 16:37:34 -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=pv1g3ps/+nMclZ4h+BIh4uRsGo0zhfwz3T9kLyBXxvw=; b=W/WzMwUtSEv7Z0Bzw2Ft+U/u/hBAY2Zjfk66Hwkm6jUYw5hbparPOfOTV3rhAgQ6ob dzpEzWl8Ck1uPFZyAUAeuJMlxeUlQRT6IxtGYCayvpYXAGu+YdlsvL6WvReX8kn2ogTH xBFvDGcsw5hf7oxB6X4Pjfw714WEhDWg6j6mACvVCRHULxkqq8WcgxZfxPomxquFj57v 4pGMjFVNURMFmA3K4dS7nOAFM6mFO0+xzrECLhvd34U5uJfi7PXdpzKqbATuBEoQVGPK KfouoBlORyueXRT+Kl+b/ca3AeZNreSfGtA6xkdYtSSoqG13sa7VZ5lKW1li4Qo8CNKw 60Ww== 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=pv1g3ps/+nMclZ4h+BIh4uRsGo0zhfwz3T9kLyBXxvw=; b=PTi6baFfHFLkhYN2FcuXqgegrfbB2Ppmh7ypOU4sdMlmDipnkGivw7NjUSWY1omLtQ IOFHjqPLrNliW7/In/Vr8XbDlFc6Nx7jm9yAu1TOSzNSl96sFDp++w5OlR6VdrlJ85Jh SLejvCOm9DqDUpzSjsjy7OJMpGkp6IHSeWCeTQO0gJszDceWF+ZIoD4tgw9XdZtlD61S tFd8X+/SI7Wlg4rRIhHs+83QE/FFssj57Qp6dYh3Ixb+Jo/KRXF5L+YPeCNnF1YPWiBa WgSFHivyVjhv2MUlQQ/sa95Z/UTvCMmG3fTaNUDS8qAzeV+CK3O0ZEmTUMpoq7GCr/3T b0cw== X-Gm-Message-State: APzg51DaMQmi3BwoZsS5J0nlSrustyoSfLMs4lSyyneoXXi2CJuo50Kz 2O5H+rphezd3rTOjGX8YJhikkuOX/V2YF4p5xhfMqA== X-Google-Smtp-Source: ANB0VdZsLR00BSgqcenC33LqyaL0147z7lBLqt1yzxp++2Z9lxpraIjUGFO8s2GUX9BiIjva3dkIIhTxxBRu3RG2uA8= X-Received: by 2002:a02:4306:: with SMTP id s6-v6mr34164492jab.140.1537400253276; Wed, 19 Sep 2018 16:37:33 -0700 (PDT) MIME-Version: 1.0 References: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> <4f40c03a-1e7a-0f09-5780-3ce6b0ec1a4e@bluestop.org> In-Reply-To: <4f40c03a-1e7a-0f09-5780-3ce6b0ec1a4e@bluestop.org> From: Warner Losh Date: Wed, 19 Sep 2018 16:37:22 -0700 Message-ID: Subject: Re: FreeBSD EFI projects To: rebecca@bluestop.org Cc: Ed Maste , "Rodney W. Grimes" , greg@unrelenting.technology, Konstantin Belousov , 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, 19 Sep 2018 23:37:35 -0000 On Wed, Sep 19, 2018 at 4:33 PM Rebecca Cran wrote: > Oh, that's a really good point - thanks! I happen to have a Minnowboard > Turbot currently sitting unused. > One other idea, unrelated to the 32-bit UEFI to boot 64-bit kernel, is to see about mining tsoome@'s port of FreeBSD boot loader to OpenIndiana. He's done a lot of cool things that would be useful to bring in, but need someone with a UEFI clue to do it. He's not had the time to get them reviewed and tested in our environment, if I understand correctly. You might want to reach out to him to see if there's things that would be useful. The biggest one I can think of is that his efi show variable code knows about standard UEFI variables and prints them out interpreted, not in unhelpful without the standard handy binary form like our loader does. Warner From owner-freebsd-current@freebsd.org Wed Sep 19 23:53: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 996B710AABD0 for ; Wed, 19 Sep 2018 23:53:01 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 11A1D70BDC for ; Wed, 19 Sep 2018 23:53:00 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w8JNqrxv026292; Wed, 19 Sep 2018 16:52:53 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w8JNqqce026291; Wed, 19 Sep 2018 16:52:52 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201809192352.w8JNqqce026291@pdx.rh.CN85.dnsmgr.net> Subject: Re: FreeBSD EFI projects In-Reply-To: <8d0769ac-e2cc-a063-978d-2db9116655b5@bluestop.org> To: Rebecca Cran Date: Wed, 19 Sep 2018 16:52:52 -0700 (PDT) CC: Greg V , Konstantin Belousov , Warner Losh , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 19 Sep 2018 23:53:01 -0000 > > On 9/19/18 9:06 AM, Rodney W. Grimes wrote: > > Yes, that is one of the catagories of rare, a EFI-32 bit system that > > was originally shipped with a 32 bit only CPU, that later got upgraded > > in the field with a 64 bit CPU, that still runs a EFI-32 bios. > > Are you sure the 2007 firmware is EFI32? I would of thought > > since they upgraded the base system to a 64 bit CPU they would > > of shipped it with a EFI-64 bios. > > > I'm not sure if there's a firmware upgrade for it, but I have a MacBook > Pro from around that time that definitely has a 32-bit EFI: it only runs > 32-bit binaries, and had a 32-bit version of MacOS X installed despite > having a 64-bit Core2Duo CPU. I am courous as to what people are using to decide that it is a EFI32 bios. I see some things that can be run under OSX that tells you, but I am looking for something more generic. I did find this little tid bit about Apple and what they did with some EFI implementations: http://refit.sourceforge.net/info/apple_efi.html It does appear as if Apple did ship EFI32 for a long time compared to other x86 vendors, even making them special fat binaries that can run on either EFI32 or EFI64, but that only works if you have an Apple EFI implementation. Apple defanitly has made Chaos of EFI, you can't even use the version being 1.10 as an indicator, as they shipped 64 bit EFI with a 1.10 version, EFI did not officially at 64 bit support until 2.0. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Wed Sep 19 23:54: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 E70AC10AAC31 for ; Wed, 19 Sep 2018 23:54:12 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 74BF870CCE for ; Wed, 19 Sep 2018 23:54:12 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w8JNs7nM026306; Wed, 19 Sep 2018 16:54:07 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w8JNs7ua026305; Wed, 19 Sep 2018 16:54:07 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201809192354.w8JNs7ua026305@pdx.rh.CN85.dnsmgr.net> Subject: Re: FreeBSD EFI projects In-Reply-To: To: Rebecca Cran Date: Wed, 19 Sep 2018 16:54:07 -0700 (PDT) CC: Greg V , Konstantin Belousov , Warner Losh , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 19 Sep 2018 23:54:13 -0000 > On 9/19/18 3:53 AM, Greg V wrote: > > > > > Yes, of course it was 64-bit. > > > > I don't think I ever downloaded the 32-bit one... > > > And are you sure it was booted via EFI and not the BIOS emulation CSM > (Compatibility Support Module)? I'm fairly sure we _don't_ support > booting a 64-bit kernel from 32-bit EFI yet. I concur. Infact I think we fall pretty hard on our face in the loader code if you run on EFI32 without CSM. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu Sep 20 05:24: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 48FE8109097D for ; Thu, 20 Sep 2018 05:24:16 +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 DD9F27D105; Thu, 20 Sep 2018 05:24:15 +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 <0PFC001006VO1400@st13p35im-asmtp001.me.com>; Thu, 20 Sep 2018 04:24:09 +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 <0PFC00CHI6W60O10@st13p35im-asmtp001.me.com>; Thu, 20 Sep 2018 04:24:08 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=2 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809200046 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-09-20_02:,, signatures=0 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (1.0) Subject: Re: FreeBSD EFI projects From: Toomas Soome X-Mailer: iPhone Mail (16A366) In-reply-to: Date: Thu, 20 Sep 2018 07:24:05 +0300 Cc: rebecca@bluestop.org, Ed Maste , "Rodney W. Grimes" , greg@unrelenting.technology, Konstantin Belousov , FreeBSD Current Content-transfer-encoding: quoted-printable Message-id: References: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> <4f40c03a-1e7a-0f09-5780-3ce6b0ec1a4e@bluestop.org> To: Warner Losh 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, 20 Sep 2018 05:24:16 -0000 I still have it all in the queue, just the paid work is taking its toll and t= hen FreeBSD and illumos .... :) Next week I am on vacation trip but then I=E2=80=99ll be back and kicking.=20= Rgds, Toomas Sent from my iPhone > On 20 Sep 2018, at 02:37, Warner Losh wrote: >=20 >> On Wed, Sep 19, 2018 at 4:33 PM Rebecca Cran wrote= : >>=20 >> Oh, that's a really good point - thanks! I happen to have a Minnowboard >> Turbot currently sitting unused. >>=20 >=20 > One other idea, unrelated to the 32-bit UEFI to boot 64-bit kernel, is to > see about mining tsoome@'s port of FreeBSD boot loader to OpenIndiana. He'= s > done a lot of cool things that would be useful to bring in, but need > someone with a UEFI clue to do it. He's not had the time to get them > reviewed and tested in our environment, if I understand correctly. You > might want to reach out to him to see if there's things that would be > useful. The biggest one I can think of is that his efi show variable code > knows about standard UEFI variables and prints them out interpreted, not i= n > unhelpful without the standard handy binary form like our loader does. >=20 > Warner > _______________________________________________ > 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 Sep 20 10:02:54 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 14F8B1097312 for ; Thu, 20 Sep 2018 10:02:54 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [IPv6:2605:2700:0:3:a800:ff:fee9:2feb]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 865BD85D26 for ; Thu, 20 Sep 2018 10:02:53 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=zUwlveLF3IpuLhlSHbjue+hkUTmVBTMT27NidUkTe44=; b=RaexCI101BeZ96+PVcQa3vFduba4x+g8FIojav/mFt54bdgA9udzz5YN9HyXqy7N3T3yXyr9kH+uIES+AyI8eMrESt1nFAiDTIopWGnlHWPq+P5txWGIc2K/ZvL8VTazVNKgx8qmkjV3cRtBe43VC8KTnp0k5JjKQfQkPWD1qZ0= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 2bab2bfe TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 20 Sep 2018 10:02:45 +0000 (UTC) Date: Thu, 20 Sep 2018 13:02:40 +0300 From: Greg V Subject: Re: FreeBSD EFI projects To: Rebecca Cran Cc: Konstantin Belousov , Warner Losh , FreeBSD Current Message-Id: <1537437760.11347.0@hraggstad.unrelenting.technology> In-Reply-To: References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> <20180917200935.GD3161@kib.kiev.ua> <1537265515.2378.0@hraggstad.unrelenting.technology> <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> <20180919095357.qwmm6p3pkbli4zww@unrelenting.technology> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed 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, 20 Sep 2018 10:02:54 -0000 On Thu, Sep 20, 2018 at 12:24 AM, Rebecca Cran wrote: > On 9/19/18 3:53 AM, Greg V wrote: > >> >> Yes, of course it was 64-bit. >> >> I don't think I ever downloaded the 32-bit one... > > > And are you sure it was booted via EFI and not the BIOS emulation CSM > (Compatibility Support Module)? I'm fairly sure we _don't_ support > booting a 64-bit kernel from 32-bit EFI yet. Well, I said I built a 32-bit-EFI version of GRUB 2, and told *that* to boot 64-bit FreeBSD kernel :) Our loader.efi wasn't used. From owner-freebsd-current@freebsd.org Thu Sep 20 11:53: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 67FC510998AA for ; Thu, 20 Sep 2018 11:53:25 +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 0752089DAA for ; Thu, 20 Sep 2018 11:53:24 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1537444402; bh=ovit2pf/ 2oxyYs/m234x1RU+Uf9Mvf9b1WwxElZzjP8=; b=ArUVvxy2RjkUi813e8bpaPG4 LeNcjtbG83/kOB+VcZdSUapAj+rnC4UaRlrKDPx1aWNudsulgGSlu5YxYRPfDAQT 7Z6EhNafHItYr6r1Qv/TDMTf2fMoEDFCh1DQa7fwQERocKjoj43yV5bZMAmyU90a XbLDhWm/NypWMYwEWDs= 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 CDFB91CBE6 for ; Thu, 20 Sep 2018 07:53:22 -0400 (EDT) Subject: Re: udp6: Page fault panics To: freebsd-current@freebsd.org References: <20180916000455.isqioezu6oovhjzg@ler-imac.local> From: Michael Butler Openpgp: preference=signencrypt Message-ID: <895cd59b-a09e-4af0-f316-56e966354ba2@protected-networks.net> Date: Thu, 20 Sep 2018 07:53:22 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.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, 20 Sep 2018 11:53:25 -0000 On 9/17/18 4:17 AM, Andrey V. Elsukov wrote: > On 16.09.2018 03:04, Larry Rosenman wrote: >> vpanic() at vpanic+0x1a3/frame 0xfffffe00ca17c150 >> panic() at panic+0x43/frame 0xfffffe00ca17c1b0 >> trap_fatal() at trap_fatal+0x35f/frame 0xfffffe00ca17c200 >> trap_pfault() at trap_pfault+0x49/frame 0xfffffe00ca17c260 >> trap() at trap+0x2ba/frame 0xfffffe00ca17c370 >> calltrap() at calltrap+0x8/frame 0xfffffe00ca17c370 >> --- trap 0xc, rip = 0xffffffff80631428, rsp = 0xfffffe00ca17c440, rbp = 0xfffffe00ca17c480 --- >> selectroute() at selectroute+0x198/frame 0xfffffe00ca17c480 >> in6_selectroute_fib() at in6_selectroute_fib+0xf/frame 0xfffffe00ca17c4a0 >> ip6_output() at ip6_output+0xfd7/frame 0xfffffe00ca17c710 > > (kgdb) l *selectroute+0x198 > 0xffffffff80de14c8 is in selectroute > (/home/devel/freebsd/base/head/sys/netinet6/in6_src.c:736). > 731 * Use a cached route if it exists and is valid, else try to allocate > 732 * a new one. Note that we should check the address family of the > 733 * cached destination, in case of sharing the cache with IPv4. > 734 */ > 735 if (ro) { > 736 if (ro->ro_rt && > 737 (!(ro->ro_rt->rt_flags & RTF_UP) || > 738 ((struct sockaddr *)(&ro->ro_dst))->sa_family != AF_INET6 || > 739 !IN6_ARE_ADDR_EQUAL(&satosin6(&ro->ro_dst)->sin6_addr, > 740 dst))) { > >> calltrap() at calltrap+0x8/frame 0xfffffe00c9d863e0 >> --- trap 0xc, rip = 0xffffffff80636b2b, rsp = 0xfffffe00c9d864b0, rbp = 0xfffffe00c9d86710 --- >> ip6_output() at ip6_output+0xeeb/frame 0xfffffe00c9d86710 >> udp6_send() at udp6_send+0x720/frame 0xfffffe00c9d868d0 > (kgdb) l *ip6_output+0xeeb > 0xffffffff80de75bb is in ip6_output > (/home/devel/freebsd/base/head/sys/netinet6/ip6_output.c:531). > 526 */ > 527 if (inp) { > 528 ro->ro_dst.sin6_family = AF_INET6; > 529 RT_VALIDATE((struct route *)ro, &inp->inp_rt_cookie, fibnum); > 530 } > 531 if (ro->ro_rt && fwd_tag == NULL && (ro->ro_rt->rt_flags & RTF_UP) && > 532 ro->ro_dst.sin6_family == AF_INET6 && > 533 IN6_ARE_ADDR_EQUAL(&ro->ro_dst.sin6_addr, &ip6->ip6_dst)) { > 534 rt = ro->ro_rt; > 535 ifp = ro->ro_rt->rt_ifp; > > It looks like Ryan's assumption is correct and panics happen due to > several threads use the same PCB and then route cache invalidation happens. > https://lists.freebsd.org/pipermail/freebsd-net/2018-September/051563.html > > But IPv6 path also needs similar patch. > I can confirm that SVN r338804 resolves this issue, imb From owner-freebsd-current@freebsd.org Thu Sep 20 12:18:44 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 E4312109AED1 for ; Thu, 20 Sep 2018 12:18:43 +0000 (UTC) (envelope-from schmiedgen@gmx.net) 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 3DE278ABB1 for ; Thu, 20 Sep 2018 12:18:43 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MJmcS-1g44NR1hky-0016qY for ; Thu, 20 Sep 2018 14:18:33 +0200 To: freebsd-current@FreeBSD.org From: Michael Schmiedgen Subject: 12.0-ALPHA6 dumps with 'Fatal double fault' Message-ID: Date: Thu, 20 Sep 2018 14:18:35 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; 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-Provags-ID: V03:K1:oOJVymbfi6AePUcKJ1UuqhMnXQHbw6F1OH4IaQP2up6PMcKTq7E n7x3zFwB0p8f9fUd9DtgOff0sNoodhcbmYlNCzmeer5oJlvJtoL6AtKA2MuXjkCUHvGDUJE JCi3N3prxNkuoAj+BKzkYVHCyf0AusoMGzaMiEakUC7yLgmecG+Nf75ZwwS44dnCWrAaS9h nI9oNIp7+ffq+y1ajfjyw== X-UI-Out-Filterresults: notjunk:1;V01:K0:trEIXetj6k4=:qRMjz+cOg1sz85GTZZ7cdK yf0u+UvFrQHRPUKfZXZWKK45RTldDlQmYJrQwgYxHc/z3ZBCwxYHkXD4SU9GxKzJyVm9I+3D0 J3Br8OoqBFkq5SI09A+lH993AO01jKbl5PZUuCqv3rVkcCxNpSPMjSZhJytOaSzBrjcJemWig OfHxOADSMhfJmqTFjIVp0PX7jHm2f9z2CB9zmuSvEt8WrgG1XpVsXXL1duqBCoeu7Yv/P0bn3 B55P4pS50eBekg2SmLxxmWdVD01FMLHyc8rSsSNosxOWcAw6iFnkDoXfnDy3O76i5HZu1r404 Zn9uphQp3OUEL6dHE/uKPHevLmni9FZpRywgcUjc6MsKv4qkthiYd+8KDqgRQaI12cVLDoj+k /v/svdKIlUcLECtecyDT+5OhP73MUPYucB6kdJRVAq4QA9aKbwS3Pnip3rq8iHfalQIfFy/kj bf0vWknXxfbCrxzNmPAPwwURW/1hOdtiP/B+ySXehh9kGNN1VKnCp6ILrfVcMM4gT2cykVUqW kIJfH0Ub9/0yJ3ANMCWiCKxMHkY28nv9YN4bRxytKpNFPfbwyPscmFSpeECKa6AnxBQQ4bV1N saNy+L4qN9SnlLPonRTxfRIJ89N+5B+uUJwlJe7yxmVYrQzd+LA3kbOK5h43aZT+cQPLaK+nb Ghj+gEtEPZIPDKKSWpPvbkkSmjpuG/EL8us6Wr/sKuVpiGmLbpKtxfKPjF55UjbZLWkPTda1+ 3/YXT0TVkKq+Awy2m+3phlhK/lDWe+fqsqaCjNpdLMzL/3hH4XpN8oI7vxn7tJRDx6pn4Lj3Y n8FB9VoMQVkZGr1MbQ6YEnSmPALE1E+X88C0/0mAn6FEqGm8l0= 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, 20 Sep 2018 12:18:44 -0000 Hi List, if compiling ports and configure script checks for SCTP with 'checking whether SCTP is supported...' 12.0-ALPHA6 dumps core with message: Fatal double fault rip 0xffffffff80b96297 rsp 0xfffffe00be241bb0 rbp 0xfffffe00be245490 rax 0x1 rdx 0x3 rbx 0x7fffffffd198 rcx 0xffffffff80b9620b rsi 0xfffff8029eeb0368 rdi 0x4 r8 0xfffff801c925c580 r9 0xfffffe00be2456d4 r10 0x4 r11 0xfffffe00be245b80 r12 0x7fffffffd190 r13 0 r14 0x1 r15 0x7fffffffd1a8 rflags 0x10293 cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b fsbase 0x8002318d0 gsbase 0xffffffff81648a00 kgsbase 0 cpuid = 0; apic id = 00 panic: double fault cpuid = 0 I can provide crash dumps if desired, but without debug information. Thanks, Michael From owner-freebsd-current@freebsd.org Thu Sep 20 14:20: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 D70BF109E2BE for ; Thu, 20 Sep 2018 14:20:07 +0000 (UTC) (envelope-from schmiedgen@gmx.net) 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 4603B8F11B for ; Thu, 20 Sep 2018 14:20:07 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lp8h6-1fZAlu1Uk0-00erQT for ; Thu, 20 Sep 2018 16:19:58 +0200 Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault' From: Michael Schmiedgen To: freebsd-current@FreeBSD.org References: Message-ID: <5c9ea80f-46b3-7ae9-c35a-f60d3aff743f@gmx.net> Date: Thu, 20 Sep 2018 16:20:00 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; 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-Language: en-US Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:NGKKw1JXRtDkMjq7HEqhPikUS7q7pK6BMKKgB2T5pHws80zOZBA ZqZE/6sgteEyVqiCgAl98TCOaJ9YLDVWDqS6Z95iVzO+ZLjLhumGW7x9jul8sFYuGqmMaiI q+OSCVvDiIDVn4sbNlzwTlLPNNwNrqxtx2kfZcR0JVBvxMG7RUX6xuz8bK/2dabo+HXDbY1 9ExXvenXjxY8mDdwaIeyA== X-UI-Out-Filterresults: notjunk:1;V01:K0:T8bASwyZirw=:HmVnSOo78n/0ipjbEi22B/ d1Vbb4IDOVfxtlACsXWZjJedVIA+D4DgSx6MdYrRs6lKMnqc8DhQoHombdA53spgSjMc7ibBS 7vkERvYtWJcUTKdS1isYZDWJzqGiQNu2ag5o4LtCsBLxvvjDbwQt5MKG47b4V9QwtZ8Q6jTmT sfDKlNIVdHcpHqzqLz6GCCNY7ASd5DFFMCqyzlLDjAhNlu9UtaEzDCqufNUD/VgNW1U/ar1wb /U2Kb+fwQTOI6noLne32Da95g6vuGyXd9W7kL2PoIc1BTDUha+bhQDy+teReMZFC3Xi3byUBu SQNL2ibpfqRmgd1LJjaFUMPIvdqwns3rA2vHa9vQe9zWdvKtsPwZKui2S0fMwCXkHImO50hvt qYEHMpk4xOmdA8W/FsNj7H8uzDidqX4yLok1hZ+ECj8WP5WaBa51j9zKDBytgzAbmhvpcKOWx EUWgDh3Ag2Zmhods+mPZ9ZdDCoVZtyMKadKE3f2Pw62xXAcQTLBkZdWU8azPrIsBW23kURq91 EdI0mKWW8JWm4njsxQDO+7PDKESaBQVrE15cnkkjqIrPE8oymrNkAWLbCoN1s+7mEarblQNls mH44hL3nmy/lN5samQ076nJxA5SZ46iMvF7+XIpQRSKdwngMq8uEwpgzCJYzfZTYM03Zt0Egh 3B+vPdLuZrMFntepvY95V5FwQuRDBGdecHD7oEgwa+Csrik3McoNzPmRMmyYTAfsqB2CKzitk 2SlS2e6YLx631FPjICFVFdmuRX77VWRZfOjhu2ccucAXASn4nYGvvRQPbu7bqnlRHRwmeMmc8 Fe6AYW9zuAUeV8TCxhp4hEYGvsREWzCj0WKDZ9ogjcUcaWloUQ= 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, 20 Sep 2018 14:20:08 -0000 I removed SCTP from kernel and updated from r338797 to r338827 and the problem seems to be gone. Michael On 20.09.2018 14:18, Michael Schmiedgen wrote: > Hi List, > > if compiling ports and configure script checks for SCTP with > > 'checking whether SCTP is supported...' > > 12.0-ALPHA6 dumps core with message: > > Fatal double fault > rip 0xffffffff80b96297 rsp 0xfffffe00be241bb0 rbp 0xfffffe00be245490 > rax 0x1 rdx 0x3 rbx 0x7fffffffd198 > rcx 0xffffffff80b9620b rsi 0xfffff8029eeb0368 rdi 0x4 > r8 0xfffff801c925c580 r9 0xfffffe00be2456d4 r10 0x4 > r11 0xfffffe00be245b80 r12 0x7fffffffd190 r13 0 > r14 0x1 r15 0x7fffffffd1a8 rflags 0x10293 > cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b > fsbase 0x8002318d0 gsbase 0xffffffff81648a00 kgsbase 0 > cpuid = 0; apic id = 00 > panic: double fault > cpuid = 0 > > I can provide crash dumps if desired, but without debug information. > > Thanks, >   Michael From owner-freebsd-current@freebsd.org Thu Sep 20 14:38:29 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 B5057109EA1A for ; Thu, 20 Sep 2018 14:38:29 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (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 4EF828FC8C for ; Thu, 20 Sep 2018 14:38:29 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.9] (p57BB4525.dip0.t-ipconnect.de [87.187.69.37]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 05B0E721E280D; Thu, 20 Sep 2018 16:38:26 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault' From: Michael Tuexen In-Reply-To: Date: Thu, 20 Sep 2018 16:38:25 +0200 Cc: freebsd-current@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Michael Schmiedgen 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: Thu, 20 Sep 2018 14:38:29 -0000 > On 20. Sep 2018, at 14:18, Michael Schmiedgen = wrote: >=20 > Hi List, >=20 > if compiling ports and configure script checks for SCTP with >=20 > 'checking whether SCTP is supported...' >=20 > 12.0-ALPHA6 dumps core with message: >=20 > Fatal double fault > rip 0xffffffff80b96297 rsp 0xfffffe00be241bb0 rbp 0xfffffe00be245490 > rax 0x1 rdx 0x3 rbx 0x7fffffffd198 > rcx 0xffffffff80b9620b rsi 0xfffff8029eeb0368 rdi 0x4 > r8 0xfffff801c925c580 r9 0xfffffe00be2456d4 r10 0x4 > r11 0xfffffe00be245b80 r12 0x7fffffffd190 r13 0 > r14 0x1 r15 0x7fffffffd1a8 rflags 0x10293 > cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b > fsbase 0x8002318d0 gsbase 0xffffffff81648a00 kgsbase 0 > cpuid =3D 0; apic id =3D 00 > panic: double fault > cpuid =3D 0 >=20 > I can provide crash dumps if desired, but without debug information. Can you elaborate which port was triggering the fault and which platform = you are using? I would like to reproduce the issue and fix it. Best regards Michael >=20 > Thanks, > Michael > _______________________________________________ > 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 Sep 20 15:12: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 7077D109FB48 for ; Thu, 20 Sep 2018 15:12:10 +0000 (UTC) (envelope-from schmiedgen@gmx.net) 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 C65AD711E9; Thu, 20 Sep 2018 15:12:09 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MMGWH-1gAPgQ2OBZ-007zU1; Thu, 20 Sep 2018 17:12:07 +0200 Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault' To: Michael Tuexen Cc: freebsd-current@FreeBSD.org References: From: Michael Schmiedgen Message-ID: Date: Thu, 20 Sep 2018 17:12:07 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; 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-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:ShmmXRoqpikuROCTlYHkeC472r4ZuTCXFNi1CJWPZDRU/FE8gV+ f3rF7CMXU+DoHZBS3HA80/KkAre+PTJyXiFh4XoPllLddhUczWqf98G5gqjaYvuJ2oamTIL Vq4iKQ5dSXUtL4OGUomL3SP/WK/7fsxETWtm5gVQd4BT6Y+0Jnq2rqYy1Oljoi9Bm4C3lYz 9/ozGmqo8B+BVASEqV2JA== X-UI-Out-Filterresults: notjunk:1;V01:K0:cRX6ZYmdd7s=:vlgig4DZvqHLIXJF4n79a6 a4ss8zHbf4QVJ8OYmBfJ2xXkhgk8cLckVq/I0c9Xthe4i1f40ho7INfUxn7y/bddrThU3KzZA n8My0fqQd+XgvH/UDut7wo6x1uuMI8QyWcKXuPtdm624xKN5ARz3gKUW42x7MGugb8XnWJKlQ 9k7hNyf0554qIg2Wu1xHecIM7P+nwrYm8uqO8GWfqSBXyzajzjolKKfL1TqGzbkQ6UhrtQ2MW a1M/08lVfNRbwB+0VOalEYeCyl5aCxUdSDiuykQYO2l4g3DZNKa4FTWZNCBdu0hyea8wKNzzk NFQWRL713kRyvu26yBtt5QG/GSypKgD7+CxdGKQoetP2fvKh2/wNLYrJjqWXimw3smP2qPpn5 +MumMT4+Sh9K3vZi4s6F8duZtN5GNzANFImD1veuMLbYGHxnPgvc40PEyEvvb29b662+cXf9X dkQ6n4Km3vDyOmI0FbD3ZhRflMvSrLeHsVfUYtswq+hMWisV+mrul5ez+1tcJU1/XBEt5/ZuQ qDP/8ZzOjeviQnjNpJHYwU5nRbyxViQ8pAYvlIkV+i1eMDj8gc9pDge3iTZJroMJDz3+ulAa7 o7Bn8qQ56uxYWGlP2fCen3dmDs72vvxlDQnLp/PK6NTPIx0i7b8OGWEe6EGoVJjXJPsQoi9w1 V4LEGUT4uwfgkKeJjqU53hwwetsodC3gJKpn/iXShQTklSbTHjZwY1lftDGbS1dJqb0LZGNEN jFNMGBXfikYGsn+zDjxhvET0l7jgJTV5AJFxu2Yv9e/gcezQjyghbeFT4FqBGk9PCvyFKcrdd LGvMhS1I89Jm7ESullaRSENs4I7F7PCZwkq8mR65QKSA7svG3g= 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, 20 Sep 2018 15:12:10 -0000 > Can you elaborate which port was triggering the fault and which platform you are using? > I would like to reproduce the issue and fix it. Port is devel/apr1 and platform is amd64. CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.10-MHz K8-class CPU) Origin="GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7 Features=0xbfebfbff Features2=0x1fbae3ff AMD Features=0x28100800 AMD Features2=0x1 XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics It crashed multiple times randomly under heavy load when compiling ports. But I observed a crash two times exactly in the same place: configure script SCTP test in devel/apr1. Thanks, Michael From owner-freebsd-current@freebsd.org Thu Sep 20 16:15: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 71B3810A13D0 for ; Thu, 20 Sep 2018 16:15:32 +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 1471873626 for ; Thu, 20 Sep 2018 16:15:31 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.9] (p57BB4525.dip0.t-ipconnect.de [87.187.69.37]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 9F200721E280D; Thu, 20 Sep 2018 18:15:29 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault' From: Michael Tuexen In-Reply-To: Date: Thu, 20 Sep 2018 18:15:28 +0200 Cc: freebsd-current@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <00082772-8AA0-415B-A4C5-B8BC8D4D7BFC@freebsd.org> References: To: Michael Schmiedgen 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: Thu, 20 Sep 2018 16:15:32 -0000 > On 20. Sep 2018, at 17:12, Michael Schmiedgen = wrote: >=20 >=20 >> Can you elaborate which port was triggering the fault and which = platform you are using? >> I would like to reproduce the issue and fix it. >=20 > Port is devel/apr1 and platform is amd64. Works fine on my side. It would be helpful if you could build a kernel = with debug symbols, reproduce the problem and provide a stack strace. Since you said that it crashed multiple times makes me wonder if this = problem is related to SCTP in particular or if there is some other generic = issue... Best regards Michael >=20 > CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.10-MHz K8-class CPU) > Origin=3D"GenuineIntel" Id=3D0x206a7 Family=3D0x6 Model=3D0x2a = Stepping=3D7 > = Features=3D0xbfebfbff > = Features2=3D0x1fbae3ff > AMD Features=3D0x28100800 > AMD Features2=3D0x1 > XSAVE Features=3D0x1 > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics >=20 > It crashed multiple times randomly under heavy load when compiling = ports. But I > observed a crash two times exactly in the same place: configure script = SCTP test > in devel/apr1. >=20 > Thanks, > Michael From owner-freebsd-current@freebsd.org Thu Sep 20 17:11: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 0C70410A2CD0 for ; Thu, 20 Sep 2018 17:11:30 +0000 (UTC) (envelope-from schmiedgen@gmx.net) 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 6B96275593; Thu, 20 Sep 2018 17:11:29 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MNf1y-1g959j3fy6-007ASu; Thu, 20 Sep 2018 19:11:25 +0200 Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault' To: Michael Tuexen Cc: freebsd-current@FreeBSD.org References: <00082772-8AA0-415B-A4C5-B8BC8D4D7BFC@freebsd.org> From: Michael Schmiedgen Message-ID: <8be8d63e-6f42-6350-eadb-c417496a1707@gmx.net> Date: Thu, 20 Sep 2018 19:11:25 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <00082772-8AA0-415B-A4C5-B8BC8D4D7BFC@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:FFH1Rf27EV7l8aHRyWmpnR1lgUV1AMry2eMkIkpBfmM2AFWCotb fkFAMjnaYALkM9nq/oaIjr2kq1f+rBHCxfZakbt6ee9ebV3fww8snMX+RV64J+IZECu0/b8 1lIEDrOdbPB7wX+e7sJnkYJ0aT78aJrWkhzukI7Zh6seEufL52S2MBOTZLcUzoTL0XDaP+k 1qcOAdpivYEnVJ3jzl/FA== X-UI-Out-Filterresults: notjunk:1;V01:K0:n0SpR7ktq4U=:JVV5kueYmrwhL5e8dJ2Z8u 4uPJ7Hueh7RqLWcr6fLWffDmMnJlYUmrQ7LqXHvN6SPUXsHNtlSoFIA5XsbBy4cOuHXDl4GKC peVkY9QSZvQgY54e3/6IuZKag84u8acJK3xiz5LDnBL59TtQTSDAJV4V30WSEXnsmki5ZAQJr kf5FnFk/VMYP/fhe9qjksC5SK0cmHCfDu44hbLmG16in6Ok0czGErlcQYr60iNP1bYtmDNLDh Lfo/ZoAxYrKwDHIbCPkzwq5TBLaRlvGaSa/ZCU/rFqgomdNSsbWXNb3CPIMgVllJusaDsRRXy dJuo8A9gqcLyO9CePLuJL2syoNTub+X4xMHgN/khPSWJcNksCB1mJOgdw80p30D1ilriorlNy aVdaT7ci2fzXBt+32q1pivAzZcPkhJHt/A4duOHZJkXZf47m8I60p49KgV0rLy9lBru1foqW5 g7fB6wRKLhSvkcmA4eHWZRNbZ0/fcARgTJUk+39TNC7T70a/ZMn1/Uz5Fffo2DuB6Dne697x6 e/KXg9CIPgFSbg7BYDhdC1rKabG8fVQBZs+HOvAPbZ/wsgSzj0/jpu5vITE6HJDMluLK9EM52 o0qYOyfMObmWk3O2+YPCImKgnEomB0FZ3ozZuD6fSwp17IrnhBLwZ7xIGhcUPvFWKWWjwLgcs OZ+raNGxqIX1AJGvPoanQkU3JASSTCEMakRseiDvbCIZchWH5EudMBfnagt4XJT8oOqVe+GTy FsHllT9kYQihLWI7+K6B8RUfBpBmH3OH3xOgaMBnh6Bps045lipdwmiVl0w8f5nX9EUZrwu7L Vwt5SDVOP0R210ju5HIAc5RkhvJQDCXZ7qIdSq+KOrrHY9FLN8= 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, 20 Sep 2018 17:11:30 -0000 Hi Michael, many thanks for your help. On 20.09.2018 18:15, Michael Tuexen wrote: >> On 20. Sep 2018, at 17:12, Michael Schmiedgen wrote: >> >> >>> Can you elaborate which port was triggering the fault and which platform you are using? >>> I would like to reproduce the issue and fix it. >> >> Port is devel/apr1 and platform is amd64. > Works fine on my side. It would be helpful if you could build a kernel with > debug symbols, reproduce the problem and provide a stack strace. Unfortunately I cannot. It is a production machine without debug that does not like to run on 11.1 OR 11.2 for some strange reason [1]. And I really do not want to run it on 11.0 anymore. Perhaps it is some crappy hardware from our hoster, I don't know. Anyway, after minimal-updating SVN to very-latest and removing SCTP it behaves just fine under load. > Since you said that it crashed multiple times makes me wonder if this problem > is related to SCTP in particular or if there is some other generic issue... The mentioned commit [2] lies exactly in my SVN update delta. So this could be the reason, too(?) Sadly I am to busy right now to investigate further, sorry. Thanks again, Michael [1] https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081192.html [2] https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071283.html From owner-freebsd-current@freebsd.org Thu Sep 20 17:27:44 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 59B8910A325C for ; Thu, 20 Sep 2018 17:27:44 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (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 EC2BD75D88 for ; Thu, 20 Sep 2018 17:27:43 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.9] (p57BB4525.dip0.t-ipconnect.de [87.187.69.37]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id DAA81721E280D; Thu, 20 Sep 2018 19:27:39 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault' From: Michael Tuexen In-Reply-To: <8be8d63e-6f42-6350-eadb-c417496a1707@gmx.net> Date: Thu, 20 Sep 2018 19:27:38 +0200 Cc: freebsd-current@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <3F80F987-397C-4CF1-9421-BA1AF0376B6C@freebsd.org> References: <00082772-8AA0-415B-A4C5-B8BC8D4D7BFC@freebsd.org> <8be8d63e-6f42-6350-eadb-c417496a1707@gmx.net> To: Michael Schmiedgen 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: Thu, 20 Sep 2018 17:27:44 -0000 > On 20. Sep 2018, at 19:11, Michael Schmiedgen = wrote: >=20 > Hi Michael, >=20 > many thanks for your help. >=20 >=20 > On 20.09.2018 18:15, Michael Tuexen wrote: >>> On 20. Sep 2018, at 17:12, Michael Schmiedgen = wrote: >>>=20 >>>=20 >>>> Can you elaborate which port was triggering the fault and which = platform you are using? >>>> I would like to reproduce the issue and fix it. >>>=20 >>> Port is devel/apr1 and platform is amd64. >> Works fine on my side. It would be helpful if you could build a = kernel with >> debug symbols, reproduce the problem and provide a stack strace. >=20 > Unfortunately I cannot. It is a production machine without debug that = does not > like to run on 11.1 OR 11.2 for some strange reason [1]. And I really = do not I'm not referring to 11.1 or 11.2. Just the kernel you use with debug = symbols. > want to run it on 11.0 anymore. Perhaps it is some crappy hardware = from our > hoster, I don't know. Anyway, after minimal-updating SVN to = very-latest and > removing SCTP it behaves just fine under load. Removing SCTP means removing it from the kernel or disabling it in the = port? >=20 >=20 >> Since you said that it crashed multiple times makes me wonder if this = problem >> is related to SCTP in particular or if there is some other generic = issue... >=20 > The mentioned commit [2] lies exactly in my SVN update delta. So this = could > be the reason, too(?) >=20 > Sadly I am to busy right now to investigate further, sorry. OK. If you have some spare time, enable SCTP again and see if the = problem is related to it... Best regards Michael >=20 > Thanks again, > Michael >=20 >=20 >=20 > [1] > = https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.ht= ml > = https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081192.ht= ml >=20 > [2] > = https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071283.= html From owner-freebsd-current@freebsd.org Thu Sep 20 18:09: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 9442410A4293 for ; Thu, 20 Sep 2018 18:09:11 +0000 (UTC) (envelope-from schmiedgen@gmx.net) 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 DBBCB77525; Thu, 20 Sep 2018 18:09:10 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M51eM-1fsQVs05qo-00zGze; Thu, 20 Sep 2018 20:09:05 +0200 Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault' To: Michael Tuexen Cc: freebsd-current@FreeBSD.org References: <00082772-8AA0-415B-A4C5-B8BC8D4D7BFC@freebsd.org> <8be8d63e-6f42-6350-eadb-c417496a1707@gmx.net> <3F80F987-397C-4CF1-9421-BA1AF0376B6C@freebsd.org> From: Michael Schmiedgen Message-ID: Date: Thu, 20 Sep 2018 20:09:01 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <3F80F987-397C-4CF1-9421-BA1AF0376B6C@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:B2AUyTZ8OrVx2XH2jtYVqn/0F16j7u74s/mcaiq5sxN6yQTgfe6 n13CODdE4+XPns+c3F3vaSxX2qsmGJBplfv6JT/DzBkY6iFbRr6oRQ0s7Mi2a9KP21LLQfY Jz7f1mDdbK7IRUUMa79+OPmYYazKCg+tQQoqrSZeq7LX6ccyV0YC7ectYu/5cCNyfApbNAG 7GhZavBZoQx7gXItEsKUQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:y9hhvw5dYxw=:qiT/h1Z3bXc+6OxT1pyXGz 7ADdGhuRqgCS38XnUIK9ZKrQSEWW0/l1LM/nKvk0HiByPdpV7nIIjq8KIBr6C7VihOOJ+jSrI f3RPBCpEbGtqSn8TJOEMVcjw4umolb3rf3CadP3/X7BYkiGJqCcmgb+nnnfwVOg4LJwVlDVa6 tV8+wDduNesXantQNWPVPZApFeDNYlHwhy0PValuJjCkkeyKocc+BLlAgJAQ2Hr+H/qZkmYB1 VOXwSnSLGFEI2yWev6eHQGx4CA8dv9wVzd7BAl9DuWJ8LpoJx94QzjM6qPEV058I2OFpxdD4c 0cGHreMVar2SOhLO3SQh5bdwGcDNHwBP+sYGZFxq7QYos9lhf/WOyfuM0/68eMKkwDqGYzSUO bwSfVIgSPCL0M7E0+uUYCgPZmHee4JOfuivXS0Wf0/8aBahMQ42nmjvYTui4TDJ7JJgNBn9vh ddCThTJvUBAdttaGu0xutb2hIMFNfDk3qyslbrUIE7MogQdjpU44VYU6c/9ZOgOupEUKVOaHk 1i34i+Rs49JfR1vAlj2Otkt36qCq31G6bETTAx5uAQ/BCgoY0zIy1pYtec3hztH1c65XSYkqp P28o7esSYSNAjd21EpExs8Zs0zOJjHIoNAZkZQL4/pqylZGfFgfH4ctCEfv1GvIFGEMdWJvTW t9+UPJv5iDnc2jOEvaApVjHbR92rlwVoU9cnCIlAPcpmoY67qMwAhap9otTjuXro98LkJ0Pld iKiRBnWOAAV0BwM+k55xE4B663i/YeJGzadfZSXs5YNHEsz8rGguv5lhYplFnJFko822ECqRQ 9/AsO2bWqdcPA28PHEwzaTklppyIfJKH4gGk6Okj12u6pNoilg= 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, 20 Sep 2018 18:09:11 -0000 >>>> Port is devel/apr1 and platform is amd64. >>> Works fine on my side. It would be helpful if you could build a kernel with >>> debug symbols, reproduce the problem and provide a stack strace. >> >> Unfortunately I cannot. It is a production machine without debug that does not >> like to run on 11.1 OR 11.2 for some strange reason [1]. And I really do not > I'm not referring to 11.1 or 11.2. Just the kernel you use with debug symbols. I know, this was only some background information. >> want to run it on 11.0 anymore. Perhaps it is some crappy hardware from our >> hoster, I don't know. Anyway, after minimal-updating SVN to very-latest and >> removing SCTP it behaves just fine under load. > Removing SCTP means removing it from the kernel or disabling it in the port? From the kernel. I commented out 'options SCTP' and recompiled. >>> Since you said that it crashed multiple times makes me wonder if this problem >>> is related to SCTP in particular or if there is some other generic issue... >> >> The mentioned commit [2] lies exactly in my SVN update delta. So this could >> be the reason, too(?) >> >> Sadly I am to busy right now to investigate further, sorry. > OK. If you have some spare time, enable SCTP again and see if the problem > is related to it... Yes, if time and point in time permits, because that's a production server and I can only mess around with it late night. Michael From owner-freebsd-current@freebsd.org Thu Sep 20 20:23: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 8996510A8CD8 for ; Thu, 20 Sep 2018 20:23:12 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic314-20.consmr.mail.gq1.yahoo.com (sonic314-20.consmr.mail.gq1.yahoo.com [98.137.69.83]) (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 07CB17E5A7 for ; Thu, 20 Sep 2018 20:23:11 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: hldD.FoVM1mbl3Flxt3PcdblI0DWEnBLVoA4z9tajcm6Z84Q6JHu1LMsCPhiTUn Hjq397PoKCvu5IT0MG9rbxnLlI9opFrY6DhCZNwKvjtqS5QI5vF38.DLAKVMyO.VSBWytczUQg2u FA09CXNlfTEG6n9Gt5KJCPeeV9_JjwYLVoy3X5Qjx0_XwEOzsGiWBlUGY_mC1tcCNR_Z5QqLDccp 8a7Y29q8Ieyv796LP1qpIqq.8L0ltJTPVJkEMp4FElsFMSaJI2J2t5IpsnRdX92s17Bx_8jsWdGE VrRbaWPIHADtvN.v6sCPwRk70v72opdSsgw6_iJK86eg.jS9oK8HyUT3rsplre5oQLRxWGf8AkQB BHuZ0wHacx9DQcP.Xfm0Rm_8GYV8w.SHDm1qr6_NCzUk0W6W9fZ6YN_iHxL.MB5hoBC.LkDZoGKr 8umyeUWjySEEDK_8wkx9lSBlrfMq4JvY1hRqg09Iwa_PLjNiF7ngaYKrxPRJIbhuwmArTLzCSBpL mqfbjpg_uZC0igcgCHcRdYvDgc1p3xJ9O9SJWveBfXo1Wr0Xfcft5Do0BZ08V.PmDdw5Ic4920RE .JIrS0YBGQUN6cDq6gihulPY_PYB16aLlgiyaw.pzrtbAe3Tjr476f8Wd0ofNBVXowf7Q3.GuFIJ zAH.a_EXC7VinWitT4ocx47E8w0yLpZFtya.zHRMlRuIRBjIBUfq4oa5B1yYf5z9sijK67_dn_Rj oTUdYp5FOCPkEO3T5lUK0mBGctG6nE7WTvi42RnDB7GmZF0xrJidBxH7yz3Aal3he4ZVaNKoNCmB USVGgjZl2YkKKQpwZPL_rQMjplStUbGFLQi.jfnsB9MEMBbMSjHBSYgCsjQkGk3a_ePammiz6rIo CfsQiyZTR74qEv1UPKGPwHdR.qHCVoxD3e6LY_wlcEQpJW3bjujgyAcR1mceMmNDNQL_cQiGpudx d1l.l6_1t.A.v_S0O61PnDs7Nvo57M4U2W.RrxRmTml4qjVN8ZEEFWXzdsfRvx3b1PDDw96YzFDD cCjVigvda Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.gq1.yahoo.com with HTTP; Thu, 20 Sep 2018 20:23:10 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp415.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 6eeb75c21f392daf911b8d7c31fc3ebb; Thu, 20 Sep 2018 20:23:06 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Use of cbp->tbd[-1].tb_size in /usr/src/sys/dev/fxp/if_fxp.c : clang 7 rejects it Message-Id: <3EBF1660-6CD5-4C80-A36D-4DE945073006@yahoo.com> Date: Thu, 20 Sep 2018 13:23:05 -0700 To: yongari@FreeBSD.org, 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: Thu, 20 Sep 2018 20:23:12 -0000 The sources listed here are from head -r338675 . /usr/src/sys/dev/fxp/if_fxpreg.h:297 is in: struct fxp_cb_tx { uint16_t cb_status; uint16_t cb_command; uint32_t link_addr; uint32_t tbd_array_addr; uint16_t byte_count; uint8_t tx_threshold; uint8_t tbd_number; /* * The following structure isn't actually part of the TxCB, * unless the extended TxCB feature is being used. In this * case, the first two elements of the structure below are * fetched along with the TxCB. */ union { struct fxp_ipcb ipcb; struct fxp_tbd tbd[FXP_NTXSEG + 1]; } tx_cb_u; }; /usr/src/sys/dev/fxp/if_fxp.c:1630 is in: /* Configure TSO. */ if (m->m_pkthdr.csum_flags & CSUM_TSO) { cbp->tbd[-1].tb_size =3D htole32(m->m_pkthdr.tso_segsz << = 16); cbp->tbd[1].tb_size |=3D htole32(tcp_payload << 16); cbp->ipcb_ip_schedule |=3D FXP_IPCB_LARGESEND_ENABLE | FXP_IPCB_IP_CHECKSUM_ENABLE | FXP_IPCB_TCP_PACKET | FXP_IPCB_TCPUDP_CHECKSUM_ENABLE; } But this cbp->tbd[-1].tb_size use goes back to -r185330 in 2008-Nov-26. This is also when the "+ 1" was added to the: struct fxp_tbd tbd[FXP_NTXSEG + 1] above. clang 7's report was: --- if_fxp.o --- /usr/src/sys/dev/fxp/if_fxp.c:1630:3: error: array index -1 is before = the beginning of the array [-Werror,-Warray-bounds] cbp->tbd[-1].tb_size =3D htole32(m->m_pkthdr.tso_segsz << = 16); ^ ~~ /usr/src/sys/dev/fxp/if_fxpreg.h:297:3: note: array 'tbd' declared here struct fxp_tbd tbd[FXP_NTXSEG + 1]; ^ 1 error generated. *** [if_fxp.o] Error code 1 It does look odd to me. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Fri Sep 21 04:54: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 6FE98108E309 for ; Fri, 21 Sep 2018 04:54:37 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (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 E7D078E0D5; Fri, 21 Sep 2018 04:54:36 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [88.217.120.246] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1g3DSW-0007QS-Bt; Fri, 21 Sep 2018 06:54:28 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w8L4sQA5003047 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 21 Sep 2018 06:54:26 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w8L4sQtN003046; Fri, 21 Sep 2018 06:54:26 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Fri, 21 Sep 2018 06:54:25 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org Cc: kde@FreeBSD.org Subject: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4 Message-ID: <20180921045425.GA2970@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org, kde@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 88.217.120.246 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, 21 Sep 2018 04:54:37 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I have here a reproducible Segmentation fault in staging phase of the port x11/kde-workspace-kde4; the full log file is here: http://www.unixarea.de/kde-workspace-kde4-4.11.22_26.log The first few lines and the end of the log are below; any comments or hints how to nail this down? Thanks matthias =3D>> Building x11/kde-workspace-kde4 build started at Fri Sep 21 05:23:49 CEST 2018 port directory: /usr/ports/x11/kde-workspace-kde4 package name: kde-workspace-kde4-4.11.22_26 building for: FreeBSD freebsd-r338641-ports-20180920-job-03 12.0-ALPHA5 Fre= eBSD 12.0-ALPHA5 1200084 amd64 maintained by: kde@FreeBSD.org Makefile ident: $FreeBSD: head/x11/kde-workspace-kde4/Makefile 479538 = 2018-09-11 18:34:27Z zeising $ Poudriere version: 3.2.99.20180601 Host OSVERSION: 1200084 Jail OSVERSION: 1200084 Job Id: 03 ---Begin Environment--- SHELL=3D/bin/csh OSVERSION=3D1200084 UNAME_v=3DFreeBSD 12.0-ALPHA5 1200084 UNAME_r=3D12.0-ALPHA5 BLOCKSIZE=3DK MAIL=3D/var/mail/root STATUS=3D1 HOME=3D/root PATH=3D/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/b= in LOCALBASE=3D/usr/local USER=3Droot LIBEXECPREFIX=3D/usr/local/libexec/poudriere POUDRIERE_VERSION=3D3.2.99.20180601 MASTERMNT=3D/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref POUDRIERE_BUILD_TYPE=3Dbulk PACKAGE_BUILDING=3Dyes SAVED_TERM=3Dscreen GID=3D0 UID=3D0 PWD=3D/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref/.p/po= ol P_PORTS_FEATURES=3DFLAVORS SELECTED_OPTIONS MASTERNAME=3Dfreebsd-r338641-ports-20180920 SCRIPTPREFIX=3D/usr/local/share/poudriere OLDPWD=3D/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref/.p SCRIPTPATH=3D/usr/local/share/poudriere/bulk.sh POUDRIEREPATH=3D/usr/local/bin/poudriere ---End Environment--- ---Begin Poudriere Port Flags/Env--- PORT_FLAGS=3D PKGENV=3D FLAVOR=3D DEPENDS_ARGS=3D MAKE_ARGS=3D ---End Poudriere Port Flags/Env--- ---Begin OPTIONS List--- =3D=3D=3D> The following configuration options are available for kde-worksp= ace-kde4-4.11.22_26: GLES=3Don: OpenGL ES 2.0 support in kwin and kinfocenter GPS=3Don: GPS geolocation via gpsd KACTIVITY=3Don: Activity Manager daemon UPOWER=3Don: Power management via UPower WALLPAPERS=3Don: Install official KDE wallpapers =3D=3D=3D=3D> Multimedia support via Phonon GSTREAMER=3Doff: Multimedia via Phonon-GStreamer VLC=3Don: Multimedia via Phonon-VLC =3D=3D=3D=3D> Options available for the group PLASMA PYTHON=3Doff: Python plasmoids support RUBY=3Doff: Ruby plasmoids support =3D=3D=3D> Use 'make config' to modify these settings ---End OPTIONS List--- --MAINTAINER-- kde@FreeBSD.org --End MAINTAINER-- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- =2E.. -- Installing: /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/loc= al/share/apps/kstyle/themes/qtplastique.themerc -- Installing: /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/loc= al/share/apps/kstyle/themes/qtwindows.themerc -- Installing: /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/loc= al/share/apps/kstyle/themes/qtgtk.themerc gmake[1]: Leaving directory '/wrkdirs/usr/ports/x11/kde-workspace-kde4/work= /.build' install -l rs /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/loca= l/bin/startkde /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/loc= al/bin/startkde4 /bin/mkdir -p /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/loca= l/share/xsessions install -m 0644 /usr/ports/x11/kde-workspace-kde4/files/kde4.desktop /wrkd= irs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions =3D=3D=3D=3D> Compressing man pages (compress-man) =3D=3D=3D> Staging rc.d startup script(s) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D> Building package for kde-workspace-kde4-4.11.22_26 Child process pid=3D81309 terminated abnormally: Segmentation fault *** Error code 1 Stop. make: stopped in /usr/ports/x11/kde-workspace-kde4 =3D>> Cleaning up wrkdir =3D=3D=3D> Cleaning for kde-workspace-kde4-4.11.22_26 build of x11/kde-workspace-kde4 | kde-workspace-kde4-4.11.22_26 ended at Fr= i Sep 21 05:40:40 CEST 2018 build time: 00:16:51 !!! build failure encountered !!! --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, http://www.unixarea.de/ +49-176= -38902045 Public GnuPG key: http://www.unixarea.de/key.pub --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlukeX8ACgkQR8z35Hb+ nRHK3Q//bHeeSRe2Ej8XLxZCmGqRBOFLCoeRUweYy6RQ7Q6ic9KsXfYxgRfHvYW/ SAk7FHeHs6AAbXyIfvAAVFPRsk89bd7F4H1ZcrEfJn1daupeP6msKZL4EnF6lPIG f8o3g72zs6Knquq+xTJ//i967jtYitHLrehvOC2vCuxDqZ3flHKKZZEfpoa6ivU0 C5bYpgFF8WYZlbIy/1p0NWZZtpXEApggQXRmM2uGb9aVNPtCCdowlgB0WOzB/mq2 CGPvwTz/TeCkST0cojexqegWTAdBv4S0K4YeS22p8PCcmkU5BUynbn2BjR/dCXQk vvF+8PdYBUgR25tg/RudxnEiHbMeaYBaCgFo2ZlNYmvkhwbhqyTUSCCpqmfauln7 Ft63gLMxzc5r+XPWNv3pRjx50PPK0A+xSfGZtfa6kVO1hcxes9eWMh/b386IWMyG iH2B4+Mg217g5ZhdlcsrvWEPeZifuzgSIK+5p1QJGMzICzdCJrsaBimH5pihCMl8 JOKdGSmb04cbBJ+EhddDfwVPNUVnIhbw5Xkerw0QfpPbUqyNGiWcR6CgNbUMdO3m ornktsk2WZW3W/VjXE/u7FQJ8jc0cblenBwt9XaFDjdkQnmGkNZS3Z5pckG3T/C7 zd7LibjBKzEcIGd7ITEzM0ypKJ1RUUaxcyOkqHU+5cUOdNoE9u0= =wRFm -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5-- From owner-freebsd-current@freebsd.org Fri Sep 21 05:59: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 B0A39108FCC9 for ; Fri, 21 Sep 2018 05:59:33 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic303-2.consmr.mail.bf2.yahoo.com (sonic303-2.consmr.mail.bf2.yahoo.com [74.6.131.41]) (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 356837000E for ; Fri, 21 Sep 2018 05:59:33 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: ROfMqRMVM1mO6RQ8i_PBd9wmoqdEOXfioYrU7iQd638XDiS0QbOl8HRhTymuN7N vstVjneVDpYyrtFLHxpoIGtwBy_b4OCUH5tSE.nBrJqbQSff6iZwN3CsAr6iDCnkpGM8VTkGBEsi a3s8bafmLOOMQrhTyGgwdEHu3u98eULgMyQHW7uX1tS0fCCPG2pm1CxuGE4LTf6z0Zt.t34h3vcx BMuQVN0eKotXTsG3EigSxMKBtKPnm6tMeIWqNW5cgpgykRKGGZ45tQsveZGblHNkuH8G9B4XMxLK 11qcbUqtBqUejpFs3tsHhJfI8UOerFcefKVNTSRw5B39Oa1s8qd1nvqlOfOkI3XVU8qEqxCDPZdk ngmIARWR0qi6Y7Xf_6fLK1OF2Oohg_aqsaIqnKBqPZtdS9JAItiKL7ixkl3DGxgu0FH9Yk0Ydgwq pZFxsP5y9D28HXyEpcm923yOW7WhbxNXIAKWL1FS1snwYWTfsOCLMpLeAFgkAu7ud2uHO4QNYEdZ TtOMyDM9l2vJM09oIpm7joNoUb6m5ZGHZPE7KxmIBiuNt1J30ieIfzeThpCTX3AgvTSXEcW0yfI0 GTmApdCCrpKZWaShcg1qR3ZtoPvtRbdATx7EpWMrhQL.XMifOP0FLQTnZs8quKjkHSiaOTHWRtiw 31ZdEbzheKbgd3W44HVjp0KNVBHzexLDBtrNMVfs8LSkk4oU7IcDEwpbuCnhlj51IYsGTX59ibUZ LRaJqPr0alxH5I4MI7ktGZ6wIZzFwSkAu.7OidfYy4OCjw..e8uD_sb_eLY0J7CT.hQZ0EOuOgqx z4uYfC95x0j7EtNEWjY95.btWrbWwW4RZMoWiAa.CPm9JFKw4NgGzwZ.aqzBPn.iJqa8hgdHHbts eUov89_iCLdJ6ZByAnT2iFppckP9Ry7teuV.knOzj9sa_Fan7DiAeL_A3aLKRaDAy3gIr2kUjFB3 EPsXVhvDJZJxBKrWmJFVcqNhIsm15De0tiCaF2Qbvsip8DwM7t3OQajNp_GE80_SDtGvnbvxKvgm hZ_ei0Y08E9i2 Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.bf2.yahoo.com with HTTP; Fri, 21 Sep 2018 05:59:32 +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 1b896f0369b0bd9927722a0805441e41; Fri, 21 Sep 2018 05:59:29 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored Message-Id: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> Date: Thu, 20 Sep 2018 22:59:27 -0700 To: FreeBSD Toolchain , 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, 21 Sep 2018 05:59:33 -0000 In looking into another report about using devel/amd64-gcc to buld head I tried a build of -r338675 ( with WERROR=3D ). It got: --- kernel.full --- linking kernel.full /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt = ignored. ctfmerge -L VERSION -g -o kernel.full ... text data bss dec hex filename 23518632 11771030 5673808 40963470 2710d8e = kernel.full Building = /usr/obj/amd64_xtoolchain-gcc/amd64.amd64/usr/src/amd64.amd64/sys/GENERIC-= NODBG/kernel.debug Building = /usr/obj/amd64_xtoolchain-gcc/amd64.amd64/usr/src/amd64.amd64/sys/GENERIC-= NODBG/kernel -------------------------------------------------------------- >>> Kernel build for GENERIC-NODBG completed on Thu Sep 20 18:38:29 PDT = 2018 -------------------------------------------------------------- Question: Is ignoring "-z ifunc-noplt" a problem for using what is built? =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Fri Sep 21 07:52: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 61D28109217A for ; Fri, 21 Sep 2018 07:52:01 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D517D73389; Fri, 21 Sep 2018 07:52:00 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id 3GBZgNFw3WppD3GBag60Md; Fri, 21 Sep 2018 01:49:11 -0600 X-Authority-Analysis: v=2.3 cv=YIcrNiOx c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=JBFolyDoGHsA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=VVlED5B4AAAA:8 a=qv9gKUOmzKf8bqhhoRQA:9 a=zWhUtyuNPw8JVNoh:21 a=_8-0VxMFGdcLwzs8:21 a=CjuIK1q_8ugA:10 a=ghGntGQLgtomCdYT4AgA:9 a=f4a35Hd5Ucwn1oq1:21 a=qxaMvCUV2CxkM4fV:21 a=FuwTnEkQqz4nje-H:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from [25.169.23.195] (unknown [24.114.41.82]) by spqr.komquats.com (Postfix) with ESMTPSA id E7B1F31E; Fri, 21 Sep 2018 00:50:27 -0700 (PDT) MIME-Version: 1.0 From: Cy Schubert Subject: RE: 12.0-ALPHA6 dumps with 'Fatal double fault' Date: Fri, 21 Sep 2018 00:49:11 -0700 To: Michael Tuexen , Michael Schmiedgen CC: "freebsd-current@FreeBSD.org" Message-Id: <20180921075027.E7B1F31E@spqr.komquats.com> X-CMAE-Envelope: MS4wfDMYUXO+uGMO4dXB4b9eO58C+qJILEx3phP8IEXOAPb+lr3nwN2hO8jYCz2J0NaE27VrbkZkC3+Sz3nU4KEDiginryD5aCL1BT9UChxyN8tomx+nKTng VYIM881cRzxGK0/1m2g4G2Dq8Zc0cy2H/wDC1p1REDIrWc0X2QfiHtnaDDP8SmfUjGC0smOyM2vHXiRdXk+Svzrq3yeBUULKTpBfaRt0htV29YyFOYi9/4YG 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: Fri, 21 Sep 2018 07:52:01 -0000 Yes, I was thinking that myself. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: Michael Tuexen Sent: 20/09/2018 07:41 To: Michael Schmiedgen Cc: freebsd-current@FreeBSD.org Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault' > On 20. Sep 2018, at 14:18, Michael Schmiedgen wrote: >=20 > Hi List, >=20 > if compiling ports and configure script checks for SCTP with >=20 > 'checking whether SCTP is supported...' >=20 > 12.0-ALPHA6 dumps core with message: >=20 > Fatal double fault > rip 0xffffffff80b96297 rsp 0xfffffe00be241bb0 rbp 0xfffffe00be245490 > rax 0x1 rdx 0x3 rbx 0x7fffffffd198 > rcx 0xffffffff80b9620b rsi 0xfffff8029eeb0368 rdi 0x4 > r8 0xfffff801c925c580 r9 0xfffffe00be2456d4 r10 0x4 > r11 0xfffffe00be245b80 r12 0x7fffffffd190 r13 0 > r14 0x1 r15 0x7fffffffd1a8 rflags 0x10293 > cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b > fsbase 0x8002318d0 gsbase 0xffffffff81648a00 kgsbase 0 > cpuid =3D 0; apic id =3D 00 > panic: double fault > cpuid =3D 0 >=20 > I can provide crash dumps if desired, but without debug information. Can you elaborate which port was triggering the fault and which platform yo= u are using? I would like to reproduce the issue and fix it. Best regards Michael >=20 > Thanks, > Michael > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Fri Sep 21 08:09: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 BA5E81092913 for ; Fri, 21 Sep 2018 08:09:06 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from smh-06.1blu.de (smh-06.1blu.de [178.254.0.206]) (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 5A44773BD5; Fri, 21 Sep 2018 08:09:06 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [172.16.29.5] (helo=sh4-5.1blu.de) by smh-06.1blu.de with esmtp (Exim 4.86_2) (envelope-from ) id 1g3GUj-0001m1-Sx; Fri, 21 Sep 2018 10:08:58 +0200 Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.86_2) (envelope-from ) id 1g3GUj-000286-Pn; Fri, 21 Sep 2018 10:08:57 +0200 Date: Fri, 21 Sep 2018 10:08:57 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org, kde@FreeBSD.org Subject: Re: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4 Message-ID: <20180921080857.GA4870@sh4-5.1blu.de> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org, kde@FreeBSD.org References: <20180921045425.GA2970@c720-r314251> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180921045425.GA2970@c720-r314251> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.5.24 (2015-08-30) 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, 21 Sep 2018 08:09:06 -0000 El día Friday, September 21, 2018 a las 06:54:25AM +0200, Matthias Apitz escribió: > > Hello, > > I have here a reproducible Segmentation fault in staging phase of the > port x11/kde-workspace-kde4; the full log file is here: > http://www.unixarea.de/kde-workspace-kde4-4.11.22_26.log > > The first few lines and the end of the log are below; any comments or > hints how to nail this down? Thanks I filed a PR re/ ports: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231532 but I think the culprit is the base system because the component which segfaults is 'pkg-static': ... =================================================== ===> Building package for kde-workspace-kde4-4.11.22_26 Child process pid=67229 terminated abnormally: Segmentation fault *** Error code 1 /var/log/messages: Sep 21 09:19:51 jet kernel: pid 67229 (pkg-static), uid 65534: exited on signal 11 As this is running in a poudriere jail, how could I get a core file of this? matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From owner-freebsd-current@freebsd.org Fri Sep 21 09:18: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 DC3251093F60 for ; Fri, 21 Sep 2018 09:18:02 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from smh-06.1blu.de (smh-06.1blu.de [178.254.0.206]) (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 7464D75C26; Fri, 21 Sep 2018 09:18:02 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [172.16.29.5] (helo=sh4-5.1blu.de) by smh-06.1blu.de with esmtp (Exim 4.86_2) (envelope-from ) id 1g3HZX-0002o8-Iv; Fri, 21 Sep 2018 11:17:59 +0200 Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.86_2) (envelope-from ) id 1g3HZX-0003Sy-Gi; Fri, 21 Sep 2018 11:17:59 +0200 Date: Fri, 21 Sep 2018 11:17:59 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org, kde@FreeBSD.org Subject: Re: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4 Message-ID: <20180921091759.GA8714@sh4-5.1blu.de> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org, kde@FreeBSD.org References: <20180921045425.GA2970@c720-r314251> <20180921080857.GA4870@sh4-5.1blu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180921080857.GA4870@sh4-5.1blu.de> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.5.24 (2015-08-30) 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, 21 Sep 2018 09:18:03 -0000 El día Friday, September 21, 2018 a las 10:08:57AM +0200, Matthias Apitz escribió: > I filed a PR re/ ports: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231532 > > but I think the culprit is the base system because the component which > segfaults is 'pkg-static': > > ... > =================================================== > ===> Building package for kde-workspace-kde4-4.11.22_26 > Child process pid=67229 terminated abnormally: Segmentation fault > *** Error code 1 > > /var/log/messages: > > Sep 21 09:19:51 jet kernel: pid 67229 (pkg-static), uid 65534: exited on signal 11 > > As this is running in a poudriere jail, how could I get a core file of > this? This is ofc a bit wrong because poudriere is installing the port to have pkg: =================================================== ===> kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg - not found ===> Installing existing package /packages/All/pkg-1.10.5_3.txz [freebsd-r338641-ports-20180920-job-03] Installing pkg-1.10.5_3... [freebsd-r338641-ports-20180920-job-03] Extracting pkg-1.10.5_3: .......... done I will remove this pkg /packages/All/pkg-1.10.5_3.txz again and will poudriere ask to build ports-mgmt/pkg-devel instead of this, because this is already on level 1.10.99. matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From owner-freebsd-current@freebsd.org Fri Sep 21 15:36: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 65195109CFEA for ; Fri, 21 Sep 2018 15:36:30 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from smh-06.1blu.de (smh-06.1blu.de [178.254.0.206]) (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 07EB083BF5; Fri, 21 Sep 2018 15:36:29 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [172.16.29.5] (helo=sh4-5.1blu.de) by smh-06.1blu.de with esmtp (Exim 4.86_2) (envelope-from ) id 1g3NTn-0007uH-FJ; Fri, 21 Sep 2018 17:36:27 +0200 Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.86_2) (envelope-from ) id 1g3NTn-0006BV-Br; Fri, 21 Sep 2018 17:36:27 +0200 Date: Fri, 21 Sep 2018 17:36:27 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org Cc: kde@FreeBSD.org Subject: Re: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4 Message-ID: <20180921153627.GA21294@sh4-5.1blu.de> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org, kde@FreeBSD.org References: <20180921045425.GA2970@c720-r314251> <20180921080857.GA4870@sh4-5.1blu.de> <20180921091759.GA8714@sh4-5.1blu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180921091759.GA8714@sh4-5.1blu.de> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.5.24 (2015-08-30) 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, 21 Sep 2018 15:36:30 -0000 El día Friday, September 21, 2018 a las 11:17:59AM +0200, Matthias Apitz escribió: > =================================================== > ===> kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg - not found > ===> Installing existing package /packages/All/pkg-1.10.5_3.txz > [freebsd-r338641-ports-20180920-job-03] Installing pkg-1.10.5_3... > [freebsd-r338641-ports-20180920-job-03] Extracting pkg-1.10.5_3: .......... done > > I will remove this pkg /packages/All/pkg-1.10.5_3.txz again and will > poudriere ask to build ports-mgmt/pkg-devel instead of this, because > this is already on level 1.10.99. I found no way that poudriere uses ports-mgmt/pkg-devel, it always compiles again ports-mgmt/pkg before kde-workspace-kde4-4.11.22_26, which crashes :-( Any hints? matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From owner-freebsd-current@freebsd.org Fri Sep 21 18:54: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 5A89A10A120A; Fri, 21 Sep 2018 18:54:26 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it1-x12d.google.com (mail-it1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 E4B5A8BA08; Fri, 21 Sep 2018 18:54:25 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it1-x12d.google.com with SMTP id j81-v6so3188734ite.0; Fri, 21 Sep 2018 11:54:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Iy1bXpBu6GjVbEJkyTTA/WcMaRQYBAsqp6AoCrKq2i8=; b=WCrP9Uu7AlyqUOQgAfnDCV/kQ5NqG3hVwGEwr60GP0ICoHmU57yR0jT+Dbg5QtjqUK mDErZ96DP7145htDzF2wARTGhrs9yYnNFQIgYiS39gSbN4PozlOi088JO8UkkrLhWeEF I4Cy2RI8lQuRwAZwR0mLRQXNNEsyaQ9fkuIYBjEm7mR6BI5I2w5n8vLX+bguVMBoYR7b ns2iRjhSrzLzd0ILh3VKXOmrJpvWepaj+di9AhTrq4wAg9+6icKQ2VAR+3YpLczaLoYW yaxj+RJpkzhlvRzGNa65sAUMLVQszz9dQsRYkZnaNcnG/YEwW1Ef4/nrY68a5dZgbO7R 246Q== 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=Iy1bXpBu6GjVbEJkyTTA/WcMaRQYBAsqp6AoCrKq2i8=; b=YIwQgmoEH/DrG/K8zUX3NX9D2l0kL4ytLhJvPLxvuQKiE8Fwxkla9JM1OJ5dlHvICc NxK8SnE/fm/6DzmoxFzSeP2km3YzTDm4++T7fCmrmhVPOfUtdm7Vs5FlGA5KWv34b7gG Jq35rl14c7Vre5tyt8aCsBrN5NN2OLBvUZg8Mk8QCZEsfyFVsuiFCnXlBXA7+kbi8yhj Oygdn37gObp2Gwn3M58suS2Ux0eGE5M8DINLJOrtwMbQQAi2PyEmwwUqsmE/93LrgnsS MfBz4DYPrJIwzIPwsPjJV3hpcpDbCPYIBV0ApV4X6GtsbFMEDKUaKw77XLcAxCpd4DAe CiUQ== X-Gm-Message-State: APzg51Ci6Ckb4S5mR48n2tBv3eeC2sN269ZzUHPdh6NKySOVfzdIj+Pq CqoBx5Au2xqGMsNQGzHsERB2A+4clm25CjJOLJYtAGyY X-Google-Smtp-Source: ANB0VdY9FPTD7DaKkRUO54sC3q9aI25IF/V7D3O8i83W22etTlqiQb6zeqdLJzQ648MC8q1lNJgMZhygxm/IQ3+Xo2E= X-Received: by 2002:a02:9a10:: with SMTP id b16-v6mr3103jal.4.1537556065327; Fri, 21 Sep 2018 11:54:25 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:404:0:0:0:0:0 with HTTP; Fri, 21 Sep 2018 11:54:04 -0700 (PDT) In-Reply-To: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> From: Ed Maste Date: Fri, 21 Sep 2018 14:54:04 -0400 X-Google-Sender-Auth: FG8wQ974Q7woirdOuxr1-GXEPy4 Message-ID: Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Mark Millard Cc: FreeBSD Toolchain , 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, 21 Sep 2018 18:54:26 -0000 On 21 September 2018 at 01:59, Mark Millard via freebsd-toolchain wrote: > In looking into another report about using devel/amd64-gcc to buld > head I tried a build of -r338675 ( with WERROR= ). It got: > ... > > Question: > > Is ignoring "-z ifunc-noplt" a problem for using what > is built? This will have no functional impact, should just result in a missed optimization. (We ought to avoid passing it to non-lld linkers though.) From owner-freebsd-current@freebsd.org Fri Sep 21 19:31:45 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 8C39E10A216C; Fri, 21 Sep 2018 19:31:45 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) (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 0BAB98D0FD; Fri, 21 Sep 2018 19:31:45 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pg1-x544.google.com with SMTP id r77-v6so1362023pgr.5; Fri, 21 Sep 2018 12:31:45 -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=3EUtzWnNKnTGrAQoghiXftRK7g0YWSB2jzzQiPcTRYo=; b=a4p5Lp2ykCm6i78Ir2vu+jtM4x4JMksSH2i3DWlkGlAORSSyUu5jixzbaldihvChym vm3plROIE63/afM9ifIiKWLWTXphJUS9gzpj9+B2yFnlkyrDT6ZIMyTmeLOprUnP8Tc5 k/DWFxgoqBIj1zii6sFBCBS3g6Ui5IL3A48/4OyYiNAR2PZpw4VP9GhEZqJioU+2Hb6A /jvdaTiqqEDJa7v6AK24PKy6PXAT9csRCshhVRe/VhY7/0J+yPHnW8+VUNvbQNwJCCl2 mLDNQDCwmHvcan551vcdbEGGt3akWDlv8AX0oT5c5R20cnIEn+j5TTrI7Lq+zejKbW0z AyBA== 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=3EUtzWnNKnTGrAQoghiXftRK7g0YWSB2jzzQiPcTRYo=; b=LlGH3TmJunYzO9c6z3vUcFvi9CWZ0enc8dUq5GWlzqgidBKkrGTKvw3TaQnjM9n+wR qHtIDkDKyZ+EL1VugaXNk/UVmo3jQILWTY8gHdvbG7N+t/O+Qr16nJjGbUVNVSRymS8r XTQSgGvaJW4+Bvo2av4WTs/z0wax2AKlkAZbw+VZty5a45UmcJ0K24fLGEbvm+tKnEVR sgEAaDmg45z3f9PpZXjVwC8wSpWDfacRi7eAEOPLo6l1KZwMZvxeXCQVjvyd4Eb7ku5B nGc+ABIfLAx+YV9GQrWluPJVqyBVBzxePtYqMqOR60ydXsLj6Sfyrs0Bu6CHAxTphPPk p0aw== X-Gm-Message-State: APzg51BVP/Q7A2eR53RHYBrwkNGEgwPG8LmqK6+zlVWQ9RqtC+CH/DdI zV3+TR9JSMSIvSFng6R8oRaHBzCL X-Google-Smtp-Source: ANB0VdZAjrNjYkPIt2nqf+5uwskelR5/R6oZgE3IBhxb8BWm+g2Km6a9AkNn4DU6RrLbkamxOs7SAw== X-Received: by 2002:a63:4663:: with SMTP id v35-v6mr42885592pgk.178.1537558303560; Fri, 21 Sep 2018 12:31:43 -0700 (PDT) Received: from raichu (toroon0560w-lp130-01-174-88-78-8.dsl.bell.ca. [174.88.78.8]) by smtp.gmail.com with ESMTPSA id z11-v6sm47574136pfi.4.2018.09.21.12.31.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Sep 2018 12:31:42 -0700 (PDT) Sender: Mark Johnston Date: Fri, 21 Sep 2018 15:31:39 -0400 From: Mark Johnston To: Ed Maste Cc: Mark Millard , FreeBSD Toolchain , FreeBSD Current Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored Message-ID: <20180921193139.GB5120@raichu> References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.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-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, 21 Sep 2018 19:31:45 -0000 On Fri, Sep 21, 2018 at 02:54:04PM -0400, Ed Maste wrote: > On 21 September 2018 at 01:59, Mark Millard via freebsd-toolchain > wrote: > > In looking into another report about using devel/amd64-gcc to buld > > head I tried a build of -r338675 ( with WERROR= ). It got: > > > ... > > > > Question: > > > > Is ignoring "-z ifunc-noplt" a problem for using what > > is built? > > This will have no functional impact, should just result in a missed > optimization. (We ought to avoid passing it to non-lld linkers > though.) Perhaps the following? It's not quite right since it'll still use -zifunc-noplt with an external LLVM toolchain, but I can't seem to figure out how to define a linker feature for only non-cross toolchains. In any case, we're going to upstream the option soon. diff --git a/share/mk/bsd.linker.mk b/share/mk/bsd.linker.mk index caf4fccbae0f..bee6a9e345dc 100644 --- a/share/mk/bsd.linker.mk +++ b/share/mk/bsd.linker.mk @@ -13,6 +13,9 @@ # linker support for that feature: # # - build-id: support for generating a Build-ID note +# - filter: support for filter DSOs +# - ifunc: support for GNU ifuncs +# - ifunc-noplt: support for optimized ifunc calls # - retpoline: support for generating PLT with retpoline speculative # execution vulnerability mitigation # @@ -85,6 +88,7 @@ ${X_}LINKER_FEATURES+= filter .endif .if ${${X_}LINKER_TYPE} == "lld" && ${${X_}LINKER_VERSION} >= 60000 ${X_}LINKER_FEATURES+= retpoline +${X_}LINKER_FEATURES+= ifunc-noplt .endif .endif .else diff --git a/sys/conf/kern.pre.mk b/sys/conf/kern.pre.mk index 523cea605afd..911f1accf1f6 100644 --- a/sys/conf/kern.pre.mk +++ b/sys/conf/kern.pre.mk @@ -121,12 +121,16 @@ CFLAGS+= ${CONF_CFLAGS} LDFLAGS+= -Wl,--build-id=sha1 .endif -.if (${MACHINE_CPUARCH} == "amd64" || ${MACHINE_CPUARCH} == "i386") && \ - defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc} == "" +.if ${MACHINE_CPUARCH} == "amd64" || ${MACHINE_CPUARCH} == "i386" +.if defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc} == "" .error amd64/i386 kernel requires linker ifunc support .endif +.if defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc-noplt} != "" +LDFLAGS+= -Wl,-z -Wl,ifunc-noplt +.endif +.endif .if ${MACHINE_CPUARCH} == "amd64" -LDFLAGS+= -Wl,-z max-page-size=2097152 -Wl,-z common-page-size=4096 -Wl,-z -Wl,ifunc-noplt +LDFLAGS+= -Wl,-z max-page-size=2097152 -Wl,-z common-page-size=4096 .endif NORMAL_C= ${CC} -c ${CFLAGS} ${WERROR} ${PROF} ${.IMPSRC} From owner-freebsd-current@freebsd.org Fri Sep 21 20:37: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 1070710A3816; Fri, 21 Sep 2018 20:37:30 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it1-x143.google.com (mail-it1-x143.google.com [IPv6:2607:f8b0:4864:20::143]) (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 9AA5B8F56B; Fri, 21 Sep 2018 20:37:29 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it1-x143.google.com with SMTP id u13-v6so3481844iti.1; Fri, 21 Sep 2018 13:37:29 -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=ewg150DxSHkNuGgy6/mzZJjwSSCVShTZKD1CAs99/TI=; b=bAmq00249kEt86VYUrrFcH5r8sq2JPFhXYL17PB3NCcI8sxvqGjaownHd8AG75oUqd Xy9LoS9UbNuYqAd3AkJnq08mVuJgaG9cK9YJftyagnln6x+RWQWzeZoaZ+qPAMFLRu+F nFBalNGuwKdGD/UljSymAu8aUp/9vjFDWXm4l0rJchtu0HMc3UqRD7yjukcG7CXk37mY 41PBjUDlGc/UnCzP1Fla8gawSClVsUsa/EkfZbxGAc77JhvhfB1OLdx3cZp469oCCELi vQcHgsDd0WVvIcdill9O2QzKG0YH28ZSXsve6+zGknyHlk52ZFkj+NTA1wYXCMaU3Pig ihqw== 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=ewg150DxSHkNuGgy6/mzZJjwSSCVShTZKD1CAs99/TI=; b=eJQrmbov1if8b8YhMjhvPsXS47/L09V5C9JpQvaVXM7zPcTRZOhy0AFrrodlna6h67 mebUAQKZYJe1wlBu31H4lFjvEp0GhHKw04/unGs4okj/XHFQxOWmZ+C7ZD3CVglSr9/u B6LsB1qbe5mmIHO1pWV0bsSWm5guiPxtxbFmDE08PMFgOGlyopz/8BCDsdfYIPQUy+TP ggaXqvXjZKl97eb4MWBZV9KTN95q3GCKg32TU6YzXE2BwZg0XsJA3Bnz7LuTJF1aWM4v gSygrTVrnEFzx2Av+D+5SuaiqadxSHKyr8s6nBHG3DwUWlKRQxHAu2FV8IxrSb1btta9 o99Q== X-Gm-Message-State: APzg51DOApaOFflhniWvIPy3kbymRUrfeYUs9nxOOlD+kCLAj9aljDgq LtrX6htyvOmvaYHq4iHmSkZLNhp2qmDwSqt4JK0n5Amo X-Google-Smtp-Source: ANB0VdaCMXd5zW62yxm8iML20NgnGLUuu0d7452IMwirbEQ7LdnINcuoC3MTszm6UToOZqv6zu4GZwFgiJ7gGZq9nbA= X-Received: by 2002:a02:9a10:: with SMTP id b16-v6mr431395jal.4.1537562248760; Fri, 21 Sep 2018 13:37:28 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:404:0:0:0:0:0 with HTTP; Fri, 21 Sep 2018 13:37:08 -0700 (PDT) In-Reply-To: <20180921193139.GB5120@raichu> References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> From: Ed Maste Date: Fri, 21 Sep 2018 16:37:08 -0400 X-Google-Sender-Auth: BgY9uEC6snM6MwmAD8fttdZCDms Message-ID: Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Mark Johnston Cc: Mark Millard , FreeBSD Toolchain , 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, 21 Sep 2018 20:37:30 -0000 On 21 September 2018 at 15:31, Mark Johnston wrote: > > Perhaps the following? It's not quite right since it'll still use > -zifunc-noplt with an external LLVM toolchain, but I can't seem to > figure out how to define a linker feature for only non-cross toolchains. > In any case, we're going to upstream the option soon. I wouldn't worry too much about out-of-tree since it will be upstream soon as you say, otherwise looks good. > +.if ${MACHINE_CPUARCH} == "amd64" || ${MACHINE_CPUARCH} == "i386" > +.if defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc} == "" > .error amd64/i386 kernel requires linker ifunc support > .endif > +.if defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc-noplt} != "" Maybe roll && defined(LINKER_FEATURES) into the outer .if? From owner-freebsd-current@freebsd.org Fri Sep 21 21:12: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 AA8A110A4363 for ; Fri, 21 Sep 2018 21:12:38 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 3822A70856 for ; Fri, 21 Sep 2018 21:12:37 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 0E4A71FC1B; Sat, 22 Sep 2018 06:12:28 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 88C262F369; Sat, 22 Sep 2018 06:12:27 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 908442F368; Sat, 22 Sep 2018 06:12:26 +0900 (JST) Date: Sat, 22 Sep 2018 06:11:33 +0900 (JST) Message-Id: <20180922.061133.1464690041529413417.yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: Fatal trap 9 when rebooting after installkernel on VirtualBox VM From: Yasuhiro KIMURA In-Reply-To: <20180902.235145.884190297314863097.yasu@utahime.org> References: <20180902.235145.884190297314863097.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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, 21 Sep 2018 21:12:38 -0000 From: Yasuhiro KIMURA Subject: Fatal trap 9 when rebooting after installkernel on VirtualBox VM Date: Sun, 02 Sep 2018 23:51:45 +0900 (JST) > I'm tracking head with VirtualBox VM. Everytime new snapshot is > released I update to same revision. So buildworld, buildkernel and > installkernel always completes sucsessfully. But when rebooting system > always crashes with 'Fatal trap 9: general protection fault while in > kernel mode' message. And I closed VM window and restart VM, new > kernel start up without any problem. > https://www.utahime.org/FreeBSD/VirtualBox_FreeBSD_12.0-ALPHA3.png > This is a screenshot of latest update (ALPHA3 -> ALPHA4). > Does anyone else experienced it? I submitted this problem to bugzilla. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231430 Screenshots when updateing to ALPHA5, ALPHA6 and ALPHA7 are also attached. According to the advice of Mark Johnston (markj@freebsd.org) they include output of 'bt' command. Just FYI. --- Yasuhiro KIMURA From owner-freebsd-current@freebsd.org Fri Sep 21 22:06:45 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 4E62710A5CA4; Fri, 21 Sep 2018 22:06:45 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 A20D972CEF; Fri, 21 Sep 2018 22:06:44 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pg1-x530.google.com with SMTP id d1-v6so6635380pgo.3; Fri, 21 Sep 2018 15:06:44 -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=2516+QDjEhD1sfCZ75g2L281nMOhCPm+smD2EO186ag=; b=EFzkTYpaGhe66fmNJFeFt9sqbU82/ccGqLCw7E1BMdTVx5Ott2Fl1znGINeoUKgWE7 UxoUa40F9Ird85mcSgHjywUOZoLAuAHOK8TiJjyHFlcdKhDCrUEpB1fwTpTAiollSgNj jSGtXZ54QCWwJ0L+EsW7rainLK+s/QrNug+kaJt1w0FxTC8cKWLpwclHhh4PRu8oYibA OpqD98JkXEGu6NoCqCsTA4B7dYs0uJa5zd4+wY0lhQqzARwVaHTyjLd28cBUGH2O/BmH fmxaNyiBCNLowllZZlv0uWUanLsZyKf65QDdiYjlVsexuXL2hQA92CDz4facn92GqfKZ dEYw== 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=2516+QDjEhD1sfCZ75g2L281nMOhCPm+smD2EO186ag=; b=LEcP29hmXCyXaC7gr6gEpM7BxQ2xd5I25El0lXQdnyx2sRe0bgdexoipRUxWD2O/1L mbCueRV+9/IP7DnbAdsrJWdvkpe813YCFzs9lNYXjS8cWbP0H/SDfizYCjs1oosw14oh qklL77PL8iTT0eIzycRiDjQTJOPT5v2Vvc7W1vPvSJMejcRzOCyRuKs0+TMi1J0u4cyF CoYMP78u/pgMHJd1No7QYQurMUN1HfC7TH0UJeOZuIlO43tKCVG21bl7boJsaiowZPzC Pe9c/wFNrMAjpOr8WwLnKnH1uCEJPevNdLvl6rws8NqkJd3+Sx1syZxeSQNMgOyNWbGa B1NQ== X-Gm-Message-State: APzg51A/gtsWxt1JrnxL3a95cOlm50K0UYaY5NrsddSYRl4BCQHOJljD 34T581zSWumfLj1G2vOS4JUpqMIfSE4= X-Google-Smtp-Source: ANB0VdY3DkQcWUU7Mwc5EW4J51PJlUHxsjJgiTO2G2X9qOGr9kq+PAue6bdBDfoKHlz25PJtszVLSQ== X-Received: by 2002:a62:3184:: with SMTP id x126-v6mr47992836pfx.49.1537567603151; Fri, 21 Sep 2018 15:06:43 -0700 (PDT) Received: from raichu (toroon0560w-lp130-01-174-88-78-8.dsl.bell.ca. [174.88.78.8]) by smtp.gmail.com with ESMTPSA id t123-v6sm35012025pfd.51.2018.09.21.15.06.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Sep 2018 15:06:42 -0700 (PDT) Sender: Mark Johnston Date: Fri, 21 Sep 2018 18:06:39 -0400 From: Mark Johnston To: Ed Maste Cc: Mark Millard , FreeBSD Toolchain , FreeBSD Current Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored Message-ID: <20180921220639.GF5120@raichu> References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> 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-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, 21 Sep 2018 22:06:45 -0000 On Fri, Sep 21, 2018 at 04:37:08PM -0400, Ed Maste wrote: > On 21 September 2018 at 15:31, Mark Johnston wrote: > > > > Perhaps the following? It's not quite right since it'll still use > > -zifunc-noplt with an external LLVM toolchain, but I can't seem to > > figure out how to define a linker feature for only non-cross toolchains. > > In any case, we're going to upstream the option soon. > > I wouldn't worry too much about out-of-tree since it will be upstream > soon as you say, otherwise looks good. > > > +.if ${MACHINE_CPUARCH} == "amd64" || ${MACHINE_CPUARCH} == "i386" > > +.if defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc} == "" > > .error amd64/i386 kernel requires linker ifunc support > > .endif > > +.if defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc-noplt} != "" > > Maybe roll && defined(LINKER_FEATURES) into the outer .if? https://reviews.freebsd.org/D17279 for anyone else that would like to review. From owner-freebsd-current@freebsd.org Fri Sep 21 23:49: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 7C05A10A7747 for ; Fri, 21 Sep 2018 23:49:49 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B26875F5B; Fri, 21 Sep 2018 23:49:49 +0000 (UTC) (envelope-from agh@riseup.net) Received: from piha.riseup.net (piha-pn.riseup.net [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 32DC41A19E7; Fri, 21 Sep 2018 16:49:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1537573781; bh=/hkaWEGZkZgJwVTI5otl7hd3GXlbMM5Zy0HX0zdcgqA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=leRQhHa7a5NDEsmiexhABjcEfzD6Cpg33ETUodYE8ExctRtf0YWPrl4KngcvaeG5u iAJyGHdLVyOsuLbSxx1b9kOAKRUVO0pypWcQslIoDNaapuBcEIgWPQWO28coGuFUlI SX41+X0CsyedGkhSJahex+giPqX5Q2jQiQrsqZlc= X-Riseup-User-ID: 20420581C562416658DBD61EBCF65938362D68A0D2C249DCEEB324FCD23C03BC Received: from [127.0.0.1] (localhost [127.0.0.1]) by piha.riseup.net with ESMTPSA id 174EB4F251; Fri, 21 Sep 2018 16:49:39 -0700 (PDT) From: Alastair Hogge To: freebsd-current@freebsd.org, Matthias Apitz Cc: kde@freebsd.org Subject: Re: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4 Date: Sat, 22 Sep 2018 07:49:35 +0800 Message-ID: <8530261.T80LyP3VS6@direwolf.local.> In-Reply-To: <20180921153627.GA21294@sh4-5.1blu.de> References: <20180921045425.GA2970@c720-r314251> <20180921091759.GA8714@sh4-5.1blu.de> <20180921153627.GA21294@sh4-5.1blu.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3016355.xEf1mJfsrZ"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-Mailman-Approved-At: Sat, 22 Sep 2018 02:39:21 +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, 21 Sep 2018 23:49:49 -0000 --nextPart3016355.xEf1mJfsrZ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" On Friday, 21 September 2018 11:36:27 PM AWST Matthias Apitz wrote: > El d=C3=ADa Friday, September 21, 2018 a las 11:17:59AM +0200, Matthias A= pitz=20 escribi=C3=B3: > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > =3D=3D=3D> kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/= sbin/pkg > > - not found =3D=3D=3D> Installing existing package > > /packages/All/pkg-1.10.5_3.txz > > [freebsd-r338641-ports-20180920-job-03] Installing pkg-1.10.5_3... > > [freebsd-r338641-ports-20180920-job-03] Extracting pkg-1.10.5_3: > > .......... done > >=20 > > I will remove this pkg /packages/All/pkg-1.10.5_3.txz again and will > > poudriere ask to build ports-mgmt/pkg-devel instead of this, because > > this is already on level 1.10.99. >=20 > I found no way that poudriere uses ports-mgmt/pkg-devel, it always > compiles again ports-mgmt/pkg before kde-workspace-kde4-4.11.22_26, > which crashes :-( >=20 > Any hints? What is the contents of make.conf used for the build? On my build host: $ grep WITH_PKG /etc/make.conf=20 WITH_PKG=3Ddevel =2D-=20 To health and anarchy --nextPart3016355.xEf1mJfsrZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEE80irLEPKImKGBmXVQ4G2pXKbobwFAlulg48ACgkQQ4G2pXKb obzjLQgAp4hntSYdPZf4IJNM3krnbD72WyQOyqK16PszAFKQW/sCH5VEh3EByAXl xHdfbIl6o9ByIqx/sIGOjobGdBjQrU4FQsnq1D/LCZftgR3n5HV+oBspnv67xWG4 GJpwW+I6R9MW4omTGraBVIa2WodTmznpH2uGAYeh5yjll5cMJ9n2hWVaXXlKg4Lu v21QdbwW58tYcsMj1UNIkFE6Y9P4JabcvSSKp4dY9ifXJZLfr/njJuZkAVeR0TON TJglQgkTfqlIIP510HAqCctjHnqIpZTYJBIPJk8vljkLbttSQivOkAviQoQCmuNY hb9CAyTnZGJa0JgOuSMs8Je8BA3+aA== =rfm3 -----END PGP SIGNATURE----- --nextPart3016355.xEf1mJfsrZ-- From owner-freebsd-current@freebsd.org Sat Sep 22 02:53: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 7B66210ADCB4; Sat, 22 Sep 2018 02:53:23 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (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 26E3A7C808; Sat, 22 Sep 2018 02:53:23 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from hammy.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id CF8A1564EC; Fri, 21 Sep 2018 21:53:21 -0500 (CDT) To: freebsd-stable@FreeBSD.org, freebsd-current@freebsd.org From: Eric van Gyzen Subject: Good motherboard for Ryzen (first-gen) Message-ID: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> Date: Fri, 21 Sep 2018 21:53:20 -0500 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: 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: Sat, 22 Sep 2018 02:53:23 -0000 I would like to build a Ryzen desktop.  Can anyone recommend a good motherboard? I'm planning on a first-gen, because the second-gen has similar stability problems as the first-gen had, and AMD hasn't released errata for the second-gen yet (as far as I know...I would love to be wrong). I would like to be a cool kid with a Threadripper, but I can't justify the cost, so I'm thinking maybe a Ryzen 7 with /only/ 8 cores.  :) Ideally, I want an Intel NIC, ECC memory support, and a 3-year warranty. Thanks in advance, Eric From owner-freebsd-current@freebsd.org Sat Sep 22 03:02:09 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 608D010AE40D; Sat, 22 Sep 2018 03:02:09 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 0009B7D113; Sat, 22 Sep 2018 03:02:08 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 6CA6737640; Fri, 21 Sep 2018 21:02:37 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Sct5AMorMz5z; Fri, 21 Sep 2018 21:02:37 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Fri, 21 Sep 2018 21:02:36 -0600 (MDT) Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Mark Johnston , Ed Maste Cc: Mark Millard , FreeBSD Toolchain , FreeBSD Current References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> From: Rebecca Cran Message-ID: <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> Date: Fri, 21 Sep 2018 21:02:01 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <20180921220639.GF5120@raichu> Content-Type: text/plain; charset=utf-8 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: Sat, 22 Sep 2018 03:02:09 -0000 On 9/21/18 4:06 PM, Mark Johnston wrote: > > https://reviews.freebsd.org/D17279 for anyone else that would like to > review. Is that possibly related to the error I'm getting trying to build -CURRENT on 11.2? make[4]: "/usr/home/bcran/workspace/freebsd/lib/libc/Makefile" line 26: amd64 libc requires linker ifunc support -- Rebecca From owner-freebsd-current@freebsd.org Sat Sep 22 03:10: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 4D47B10AE8C4 for ; Sat, 22 Sep 2018 03:10:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 D05D57D4CC for ; Sat, 22 Sep 2018 03:10:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd2b.google.com with SMTP id e12-v6so13860957iok.12 for ; Fri, 21 Sep 2018 20:10:05 -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=z1MwhWFImjFHyfTRNPfx8Vt+70Tbg2+HxIuJnsCGVvU=; b=Yv5QfIn/+GYFyd8CModurZhtO6ZnXro4I7wNSv/hrzv/U6IId+Eh/oXFO/y+frRpLy pVUiUAe0J181LR74s60urjiYg6K/adHg36hFbt88q/3TxUbUAYFlwAUEkgk9H12C/7al czSIBaUY9Xzmr6xGZ4aNEfY5bVbGYaevFUBd9RFnUgc8ezyYUKtyeKGzgJTxJtgBvFvc NcebB57LoyZJ4hZPZANhkYbm9P54k26qvnRk4r1sbXeX3o1bIVJ1p3plEjs1KRud/1CH ZcFalCuyK3e1U+y3eJNXGB9/cGw6jERKSyGA/8asc6cAEBZ7rAdNfWC3uEfDNEzfVRs/ QtlA== 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=z1MwhWFImjFHyfTRNPfx8Vt+70Tbg2+HxIuJnsCGVvU=; b=fMgAkDT7tXNH4W+biXA8SzqPz9NvL7l1KQZE5C9CEL30h7U0DDZR4MKdneIqXFQlsa /WQ4z8CCEp0cxudQibRlEBkipYFYaq1W6FN28q2e0Nq5zv9N5GDDbfhUXd8X/Ghcgwyg GdjmiQC0xiCAfpgbmXgCPhgBrwhB42XJvyAQwriFW84915FFUbhjm2GmCgFQ8hf5E/aH LehVK9KkSa8AUU/x8tN+QZOktrbkZkbFFd+zx/Pt66zboB6Et3lc2Gl0IrhPBDaooS66 7BjWUhRM1AaSEsHP3CfS0lGsKy9P+d6Den0K5TELmR3Dho0ZR475PKGdDOx2ph6j2A4Y Mw1A== X-Gm-Message-State: ABuFfoiNlTJjfILShz7G7MVovQzTCWNUroJN6DatOlwKLaxfISHe9RQe 9uV7+UONFJmGERpf9g3GpIC87ha7LuywmHMjhswPow== X-Google-Smtp-Source: ACcGV62+gzQqygQwNpV7xAwxI2xSH7fHRfi9KDYIr/82z+iqEwTVbriF8vl4EgkL4BdKgq7KwX4mly2sQtxuGz8Ar1M= X-Received: by 2002:a6b:3902:: with SMTP id g2-v6mr439770ioa.168.1537585804971; Fri, 21 Sep 2018 20:10:04 -0700 (PDT) MIME-Version: 1.0 References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> In-Reply-To: <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> From: Warner Losh Date: Fri, 21 Sep 2018 21:09:48 -0600 Message-ID: Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: rebecca@bluestop.org Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" 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, 22 Sep 2018 03:10:06 -0000 On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain < freebsd-toolchain@freebsd.org> wrote: > On 9/21/18 4:06 PM, Mark Johnston wrote: > > > > https://reviews.freebsd.org/D17279 for anyone else that would like to > > review. > > > Is that possibly related to the error I'm getting trying to build > -CURRENT on 11.2? > > > make[4]: "/usr/home/bcran/workspace/freebsd/lib/libc/Makefile" line 26: > amd64 libc requires linker ifunc support > Yea, that should absolutely work. If it doesn't, that's a big big problem. Warner From owner-freebsd-current@freebsd.org Sat Sep 22 03:30: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 86F3110AF306; Sat, 22 Sep 2018 03:30:52 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 22C5C7DF80; Sat, 22 Sep 2018 03:30:52 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id D9EFE37671; Fri, 21 Sep 2018 21:31:25 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RYL1yypgVYZu; Fri, 21 Sep 2018 21:31:25 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Fri, 21 Sep 2018 21:31:25 -0600 (MDT) Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Warner Losh Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> From: Rebecca Cran Message-ID: <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> Date: Fri, 21 Sep 2018 21:30:50 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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: Sat, 22 Sep 2018 03:30:52 -0000 On 9/21/18 9:09 PM, Warner Losh wrote: > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain < > freebsd-toolchain@freebsd.org> wrote: > >> On 9/21/18 4:06 PM, Mark Johnston wrote: >>> https://reviews.freebsd.org/D17279 for anyone else that would like to >>> review. >> >> Is that possibly related to the error I'm getting trying to build >> -CURRENT on 11.2? >> >> >> make[4]: "/usr/home/bcran/workspace/freebsd/lib/libc/Makefile" line 26: >> amd64 libc requires linker ifunc support >> > Yea, that should absolutely work. If it doesn't, that's a big big problem. I see, it was introduced earlier today in lib/libc/Makefile: commit ef8030831eccec4e481a1766fc1c67f7cadadac9 Author: emaste Date:   Fri Sep 21 17:49:37 2018 +0000     libc: require ifunc-capable linker for amd64/i386         We expect to introduce optimized libc routines in the near future,     which requires use of a linker that supports ifuncs.         Approved by:    re (gjb, kib)     Sponsored by:   The FreeBSD Foundation And /usr/bin/ld -v on my 11.2 system says: GNU ld 2.17.50 [FreeBSD] 2007-07-03 -- Rebecca From owner-freebsd-current@freebsd.org Sat Sep 22 03:34: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 7991110AF446 for ; Sat, 22 Sep 2018 03:34:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it1-x132.google.com (mail-it1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 058CA7E334 for ; Sat, 22 Sep 2018 03:34:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it1-x132.google.com with SMTP id p79-v6so4392249itp.3 for ; Fri, 21 Sep 2018 20:34:25 -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=TxfUbbwf3tCPr5N83UPGqNMUvSxqnN6g8D0r3AEKsPc=; b=tDBZRDIXKUoy3fJV3cQYR0S8MukGBjP2XOVsPyv7zCMYWnE2rCCejJc3r8BKOfSNou BKttq4/ZBYfZ5V2M+24T95oz5EX1myl8J0rnm1iQ/1/C9O01kDLWpU2qCtwzyo0TN/Qr 4gCqiS9cH72Ayx1OO/7q93PgFXqy+o1E4iVc28oA7RO7q378t/fq74apdKowOt35iAO9 3+WVuJ+kAqeJIkzS9LS35+BEZurg+DtAObChmHAXcSeGSlRzsdjSTN3CUPAgq0Uop578 3uBnsbfNFO53VAzEvYezuuHYnIO7aDNekLaLG0ITk1riAmYe9PWKDaxUNO+Vcw6cmnuc QZxA== 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=TxfUbbwf3tCPr5N83UPGqNMUvSxqnN6g8D0r3AEKsPc=; b=LHDai+TZz8Ozj8aLYe1gBWvhxp4VtPcGTa3SYAMGwRmmaO0UUJg7GJdG7KWG5UTq8w BQxc/SjJsXieWS9KSrItCFyvntHAdP621gXdlt49Otcmu5BUs3E+DYQoshZZLTS3cyGD t53xScNRN/I2cV8zqwEZ2pCpXAQ8TIq6jHiIKuLFgCanfU7rm23ZKEmWU5PtFzSAZcmr 2vPVESLoYP8OSM6wI/B+HZuEcO2tXnp+QUMOTu+T3CatxDgl4ErM6gqtsjpDIYOH5jWq aMdmv+VnNZ8v9fWEUyIDNircNSqgtmyXY8FkXvzH7qrAzIGM4Vo6POgwQ9Ro9wmy8KSF t50A== X-Gm-Message-State: APzg51D6P5C1sgN7jYx2K/HE+dTQ79RxPru27CfXYE5EBwDRQbVlwQzF eGezNZn3MLB+Lrr9v3ToIgZqgfuYPhbEOG614i7l3w== X-Google-Smtp-Source: ANB0VdZ6/3KOaAQ7gsFE2f597RX9azbec7XLhsXdpa+ThNj0oze+IzTFh7qBfVp7F3faMKaEVmLHWqmvEHkiYL4Q8RA= X-Received: by 2002:a02:59cc:: with SMTP id v73-v6mr536313jad.5.1537587264157; Fri, 21 Sep 2018 20:34:24 -0700 (PDT) MIME-Version: 1.0 References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> In-Reply-To: <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> From: Warner Losh Date: Fri, 21 Sep 2018 21:34:13 -0600 Message-ID: Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: rebecca@bluestop.org Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" 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, 22 Sep 2018 03:34:25 -0000 On Fri, Sep 21, 2018 at 9:30 PM Rebecca Cran wrote: > On 9/21/18 9:09 PM, Warner Losh wrote: > > > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain < > > freebsd-toolchain@freebsd.org> wrote: > > > >> On 9/21/18 4:06 PM, Mark Johnston wrote: > >>> https://reviews.freebsd.org/D17279 for anyone else that would like to > >>> review. > >> > >> Is that possibly related to the error I'm getting trying to build > >> -CURRENT on 11.2? > >> > >> > >> make[4]: "/usr/home/bcran/workspace/freebsd/lib/libc/Makefile" line 26: > >> amd64 libc requires linker ifunc support > >> > > Yea, that should absolutely work. If it doesn't, that's a big big > problem. > > > I see, it was introduced earlier today in lib/libc/Makefile: > > > commit ef8030831eccec4e481a1766fc1c67f7cadadac9 > Author: emaste > Date: Fri Sep 21 17:49:37 2018 +0000 > > libc: require ifunc-capable linker for amd64/i386 > > We expect to introduce optimized libc routines in the near future, > which requires use of a linker that supports ifuncs. > > Approved by: re (gjb, kib) > Sponsored by: The FreeBSD Foundation > > > And /usr/bin/ld -v on my 11.2 system says: > > > GNU ld 2.17.50 [FreeBSD] 2007-07-03 > What does ld.lld say? However, it shouldn't matter: we don't build libc until *AFTER* we build ld.lld, so this error is bogusly triggering. I suspect that it needs to be limited to only building targets, since tree traversal ones, as well as install targets don't have this dependency. Warner From owner-freebsd-current@freebsd.org Sat Sep 22 03:35:29 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 28FA810AF4D9; Sat, 22 Sep 2018 03:35:29 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 B071D7E3E5; Sat, 22 Sep 2018 03:35:28 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 7153F37686; Fri, 21 Sep 2018 21:36:02 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id QbNh1d2KxiPg; Fri, 21 Sep 2018 21:36:02 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Fri, 21 Sep 2018 21:36:02 -0600 (MDT) Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Warner Losh Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> From: Rebecca Cran Message-ID: Date: Fri, 21 Sep 2018 21:35:26 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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: Sat, 22 Sep 2018 03:35:29 -0000 On 9/21/18 9:34 PM, Warner Losh wrote: > What does ld.lld say?  > > However, it shouldn't matter: we don't build libc until *AFTER* we > build ld.lld, so this error is bogusly triggering. I suspect that it > needs to be limited to only building targets, since tree traversal > ones, as well as install targets don't have this dependency. LLD 6.0.0 (FreeBSD 326565-1100001) (compatible with GNU linkers) -- Rebecca From owner-freebsd-current@freebsd.org Sat Sep 22 03:35: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 88AAD10AF515 for ; Sat, 22 Sep 2018 03:35:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 15D6C7E3FE for ; Sat, 22 Sep 2018 03:35:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it1-x130.google.com with SMTP id f14-v6so4393356ita.4 for ; Fri, 21 Sep 2018 20:35:40 -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=oLvxsvyJ8l2kYungGYkCQdf0/v4/WpnDqzIb7ZFY6pw=; b=a8VAhAFv+TAZLsCATF3AQQL14+KN02hanB2+676RzH1CZ/o96vkaz5xdOerHRlOhTZ wEYLdlasEht6RIVAtIZ8Jb08zQfhD57xaeoHvTlcGAlMfbPI4FQeZKgQIVZvWG8I15sf QsBX/irrQiHXty74D//fIrQiZEOJ3SkcJJPKclTsufX325n72Pvf8d/DF2HbPkUGg+Au gHJfMQcqSavDLVVYz6RSs1MFxexbkFky0VfSJ+13CNwXSFFLFeFssUoM+x/+cHDJKbrH qMCGkZDBSRBEaxnEyo7leDVnvnMEnwtLP/AGwNxhxxbVKenZqjMXvpddycCLj5sP4ydX vhVQ== 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=oLvxsvyJ8l2kYungGYkCQdf0/v4/WpnDqzIb7ZFY6pw=; b=bu1X/zH/6mfzYWr3mYdty/F9trjlpJWSkUW0H6/GWobryIUyOxPFJyz+07bmHYKlkm CbRSYmIRoevHzjJ4iYh5GEjwffp7RfcQL8Sb+9IYVox+2pRJuN/TkzO3e6WmbONx4eTa +QItjNs7AmhMYtjPU5GrsV2GcfIwhH6gUB29JKaqBR8gT5aMzN0WqfDSj2tCZHSm26RL gXPa6UXiOSnWIq5hOjRfKjWJk01PVe4V4LeLNMqW+o9g8Nw+py0gxqVXHwWoGU/wBAA1 9fFsI2pZMMg19newE4xdqDL7+YY7PiNav3PkVJhgjTIr9ZTWhfRjCXrgT5lWrNw5jK/K FoFg== X-Gm-Message-State: APzg51CqJjmYy3LG5oV/kAzIcEGBzUqyzeMOnT4EJLF5+93hkdNcv5rA 530/b9YknIbN+rFPk9+wSPyDoK8++nBIayym3nLIWA== X-Google-Smtp-Source: ANB0VdZC6cei0QiTAp/IDbWQ65JfxDR7a7ngCCauKHqAWAj8UZU998+cU+B3I2//ALzbUPvrWiSSDg9wrBVEPDeOWYo= X-Received: by 2002:a02:4306:: with SMTP id s6-v6mr525733jab.140.1537587339400; Fri, 21 Sep 2018 20:35:39 -0700 (PDT) MIME-Version: 1.0 References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> In-Reply-To: From: Warner Losh Date: Fri, 21 Sep 2018 21:35:28 -0600 Message-ID: Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: rebecca@bluestop.org Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" 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, 22 Sep 2018 03:35:40 -0000 On Fri, Sep 21, 2018 at 9:34 PM Warner Losh wrote: > > > On Fri, Sep 21, 2018 at 9:30 PM Rebecca Cran wrote: > >> On 9/21/18 9:09 PM, Warner Losh wrote: >> >> > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain < >> > freebsd-toolchain@freebsd.org> wrote: >> > >> >> On 9/21/18 4:06 PM, Mark Johnston wrote: >> >>> https://reviews.freebsd.org/D17279 for anyone else that would like to >> >>> review. >> >> >> >> Is that possibly related to the error I'm getting trying to build >> >> -CURRENT on 11.2? >> >> >> >> >> >> make[4]: "/usr/home/bcran/workspace/freebsd/lib/libc/Makefile" line 26: >> >> amd64 libc requires linker ifunc support >> >> >> > Yea, that should absolutely work. If it doesn't, that's a big big >> problem. >> >> >> I see, it was introduced earlier today in lib/libc/Makefile: >> >> >> commit ef8030831eccec4e481a1766fc1c67f7cadadac9 >> Author: emaste >> Date: Fri Sep 21 17:49:37 2018 +0000 >> >> libc: require ifunc-capable linker for amd64/i386 >> >> We expect to introduce optimized libc routines in the near future, >> which requires use of a linker that supports ifuncs. >> >> Approved by: re (gjb, kib) >> Sponsored by: The FreeBSD Foundation >> >> >> And /usr/bin/ld -v on my 11.2 system says: >> >> >> GNU ld 2.17.50 [FreeBSD] 2007-07-03 >> > > What does ld.lld say? > > However, it shouldn't matter: we don't build libc until *AFTER* we build > ld.lld, so this error is bogusly triggering. I suspect that it needs to be > limited to only building targets, since tree traversal ones, as well as > install targets don't have this dependency. > I meant to add, can you give a few lines before the error is spewed here in email? My IRC computer died before I could see any answers there... My 11.2-stable system has 6.0.1, so I can't test from there. Warner From owner-freebsd-current@freebsd.org Sat Sep 22 03:38: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 4342D10AF6B9; Sat, 22 Sep 2018 03:38:35 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 D41C47E5AA; Sat, 22 Sep 2018 03:38:34 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id A0F353769C; Fri, 21 Sep 2018 21:39:08 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Q4Q5gsbGB1wT; Fri, 21 Sep 2018 21:39:08 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Fri, 21 Sep 2018 21:39:08 -0600 (MDT) Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Warner Losh Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> From: Rebecca Cran Message-ID: <74775769-6810-63ab-d776-013bc72c8488@bluestop.org> Date: Fri, 21 Sep 2018 21:38:33 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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: Sat, 22 Sep 2018 03:38:35 -0000 On 9/21/18 9:35 PM, Warner Losh wrote: > > I meant to add, can you give a few lines before the error is spewed > here in email? My IRC computer died before I could see any answers > there... > > My 11.2-stable system has 6.0.1, so I can't test from there. I've uploaded the full 'buildworld' output to https://bluestop.org/files/typescript.txt . -- Rebecca From owner-freebsd-current@freebsd.org Sat Sep 22 03:57: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 02BCD10B002C for ; Sat, 22 Sep 2018 03:57:57 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd41.google.com (mail-io1-xd41.google.com [IPv6:2607:f8b0:4864:20::d41]) (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 772FA7F7E2 for ; Sat, 22 Sep 2018 03:57:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd41.google.com with SMTP id e12-v6so13900814iok.12 for ; Fri, 21 Sep 2018 20:57:56 -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=S36lH5revQv/fstuZqTN5rze1M8BIoaU/sV9Pp0Y9N0=; b=NFWpqi9b1t9tQ0Yf44VIyW/iABW63fB+6HTtz4082bsX6DYeA9GXIlozilQ5ziZzNs 2u5wRK5fhz4FnEiysd+HsyH7ZKg731gBFSdsn2UfMdbLJtXpqG4G8FZ8+R/AgAc16cQP lgoZjDNHJAA9EATli3+WfJgD0lFpVX0movFo/3qHcuqR5G3vDNCusHyyx6bmXg1G7djA jTymz/lEqIS+sh8JTWTUNzTe6tmM4SGTfzyNYUwxLu7k/LApBgFmPjQm+i+Ehst6ij2j Q+QsgwhwonI3W448mDV7gFvN+yWOYbcXWHpLCIVjlLqWc0J1fp5rnQbNGZ9hRfbtHnkP ORXg== 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=S36lH5revQv/fstuZqTN5rze1M8BIoaU/sV9Pp0Y9N0=; b=artw3QgO8uoIfbTURjPkVHeEs7W32Xjy5ND3vZIjJDb02OqCaLm42cuFjBN9Lg24J5 eFQZNSPKM9yJ86kHr3HCctBcf+yFvRfbdPinXnv50Ef/KyQfJ/BIRnh+VHDh2p2Yy3TN sf9COpPLlbfDiOijL8DeMx63PP1axcjJ3JBJzVUWXF45MqYK9P8vXnFV3R9QerCsbW2n WKDawedqKYyfpWUd4ggMcg1AzALKIyNHNWqNLG4H9hBuPWq7r8GoO+o9D/dbV8xzFk56 ZN3nCrsuKoLV9AhDxUXSbP12P5fJ5Gchf/ZR0S20WuApiy4+X5FTyvDpA5V7y7C6Rv7g 53Iw== X-Gm-Message-State: ABuFfohcVFlrE/jyoqU/8fEx5XhELH6VJg2zbAoW0D/oG1rmTMH4VJ0W JJ768fJSnSAO36grb0UDedDlzmD0PZRwHbZIPbaXFA== X-Google-Smtp-Source: ACcGV625+hnIZOeA/TaU+H1tYUufcLoJQlGCEkC+6PCRNmaxkZ6XC1u9Aew2Aa3C0CLvmT6ZRq2DbObWflul+hrHpD4= X-Received: by 2002:a6b:7117:: with SMTP id q23-v6mr491651iog.37.1537588675628; Fri, 21 Sep 2018 20:57:55 -0700 (PDT) MIME-Version: 1.0 References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> <74775769-6810-63ab-d776-013bc72c8488@bluestop.org> In-Reply-To: <74775769-6810-63ab-d776-013bc72c8488@bluestop.org> From: Warner Losh Date: Fri, 21 Sep 2018 21:57:44 -0600 Message-ID: Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: rebecca@bluestop.org Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" 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, 22 Sep 2018 03:57:57 -0000 Hmmm, what does make -V LINKER_TYPE and make -V LINKER_FEATURES say? They look good for me, but the only way you get this error is if they are wrong. Although from your typescript, I see: ===> lib/libc (cleandir) make[4]: "/usr/home/bcran/workspace/freebsd/lib/libc/Makefile" line 26: amd64 libc requires linker ifunc support which tells me that we need to exclude all the non-build targets from this check.... This will use the HOST linker rather than the TARGET linker. So something like: diff --git a/lib/libc/Makefile b/lib/libc/Makefile index a1ce123c0f33..11575e1cabff 100644 --- a/lib/libc/Makefile +++ b/lib/libc/Makefile @@ -21,10 +21,12 @@ LIBC_ARCH=${MACHINE_ARCH} LIBC_ARCH=${MACHINE_CPUARCH} .endif +.if build(all) .if (${LIBC_ARCH} == amd64 || ${LIBC_ARCH} == i386) && \ defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc} == "" .error ${LIBC_ARCH} libc requires linker ifunc support .endif +.endif # All library objects contain FreeBSD revision strings by default; they may be # excluded as a space-saving measure. To produce a library that does may be needed, but the problem may be related to caching these values from the host as well, even though we rebuild them... Warner On Fri, Sep 21, 2018 at 9:38 PM Rebecca Cran wrote: > On 9/21/18 9:35 PM, Warner Losh wrote: > > > > I meant to add, can you give a few lines before the error is spewed > > here in email? My IRC computer died before I could see any answers > > there... > > > > My 11.2-stable system has 6.0.1, so I can't test from there. > > > I've uploaded the full 'buildworld' output to > https://bluestop.org/files/typescript.txt . > > > -- > > Rebecca > > From owner-freebsd-current@freebsd.org Sat Sep 22 03:59: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 0567F10B00B5; Sat, 22 Sep 2018 03:59:17 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 9616F7F8EE; Sat, 22 Sep 2018 03:59:16 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 71857376CC; Fri, 21 Sep 2018 21:59:50 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id i24LHyjicN8n; Fri, 21 Sep 2018 21:59:50 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Fri, 21 Sep 2018 21:59:50 -0600 (MDT) Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Warner Losh Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> <74775769-6810-63ab-d776-013bc72c8488@bluestop.org> From: Rebecca Cran Message-ID: <11385a3d-f6ec-453d-8a21-a29c34c94b0f@bluestop.org> Date: Fri, 21 Sep 2018 21:59:14 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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: Sat, 22 Sep 2018 03:59:17 -0000 On 9/21/18 9:57 PM, Warner Losh wrote: > Hmmm, what does make -V LINKER_TYPE and make -V LINKER_FEATURES say? > > They look good for me, but the only way you get this error is if they > are wrong. bcran@cube:~/workspace/freebsd % make -V LINKER_TYPE bfd bcran@cube:~/workspace/freebsd % make -V LINKER_FEATURES  filter -- Rebecca From owner-freebsd-current@freebsd.org Sat Sep 22 04:00: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 4896A10B024D for ; Sat, 22 Sep 2018 04:00:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 CA5A77F963 for ; Sat, 22 Sep 2018 04:00:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd33.google.com with SMTP id l25-v6so835152ioj.0 for ; Fri, 21 Sep 2018 21:00:38 -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=YRcDA9+NgwFMohYFwuuHV2QeFCu/zfUmuQOR7f7CbeM=; b=W/xmn6P2u+VDqTzV6iIT0GRB1oc7hKYyxdBk5iFrWTQU+tLje3JOJvot4cleJJnPCf GmnH2iBR3rjs6NWE75bJ+WEs+cXgIlIW8ayFIz6aBq+BrTitIOpFIymZ9KhJdLxi07bD chMUKxxaDGtTw3cgj87+6Ku/FEm+0st6fjruFYQ7kvHcH49ZflYd4UoCvfoa5IMl+McW c9T0BhaEY4/7vXQ//VJg/p0MtJ5Q0/2lXvLIdHfxTtPXjKZPq/COw1NAAN79RGTpSRAL pEN6C70+u9aEvkNVf/Ep8M1CeSpp+kA5AucioI1b5P/yl6OVEAgY88I0GFi/7Xzpy2Mw /2AQ== 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=YRcDA9+NgwFMohYFwuuHV2QeFCu/zfUmuQOR7f7CbeM=; b=qknLY0GMUBFWCXfpfBe3iK0s571ZaRj3ZxZU/N3x/lYn4Mn9VU41mNkxNdF7mSXfgC ir1S599XLc+PYX7ZOi8wRufhHbtflkoVKVqHDPurForSkeX3TFfowcxa5m3t+MVbgr+5 z6wUqjlDL9WI8ur52/n8n4kHYPm/JqINFadb+fZg1Lg7WdouOi+/dV2WQxvuOqaJWk9U DFOmmWExFNdw30mHMChltyqshnffiimXz0e3/fSU+KyYoVO2HUmvuSsf2c375I4eiWme xWGmwNsmkbHBbdefUcOz6IBCzH2ngGFVK0Upj97hO+oWW71pUI0DceUELclvdHWbp1v7 9PhQ== X-Gm-Message-State: ABuFfoi9XByziNbV910ljlyqVmizDcfLCxah6TVCp2VfAZmjR5gxMo7G 28L6m7juaEKMipz0RF0QYioifUE5G4HXzGcRTNfO6w== X-Google-Smtp-Source: ACcGV61x/71B8ovuNQxL4o3aQXGGWfY8KApMTseMtUXvw0dKAsqBp7+E28mq0D5G1XpQL7n2N9e1CVNbg77k3cLed7g= X-Received: by 2002:a6b:7117:: with SMTP id q23-v6mr496565iog.37.1537588838164; Fri, 21 Sep 2018 21:00:38 -0700 (PDT) MIME-Version: 1.0 References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> <74775769-6810-63ab-d776-013bc72c8488@bluestop.org> <11385a3d-f6ec-453d-8a21-a29c34c94b0f@bluestop.org> In-Reply-To: <11385a3d-f6ec-453d-8a21-a29c34c94b0f@bluestop.org> From: Warner Losh Date: Fri, 21 Sep 2018 22:00:27 -0600 Message-ID: Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: rebecca@bluestop.org Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" 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, 22 Sep 2018 04:00:39 -0000 On Fri, Sep 21, 2018 at 9:59 PM Rebecca Cran wrote: > On 9/21/18 9:57 PM, Warner Losh wrote: > > > Hmmm, what does make -V LINKER_TYPE and make -V LINKER_FEATURES say? > > > > They look good for me, but the only way you get this error is if they > > are wrong. > > > bcran@cube:~/workspace/freebsd % make -V LINKER_TYPE > bfd > > bcran@cube:~/workspace/freebsd % make -V LINKER_FEATURES > filter > That may be the issue... Does the patch I included help? I'm building now on my stable system, but it's slow... Warner From owner-freebsd-current@freebsd.org Sat Sep 22 04:10: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 E18C210B05D4; Sat, 22 Sep 2018 04:10:03 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 7C5197FF89; Sat, 22 Sep 2018 04:10:03 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 335C2376E6; Fri, 21 Sep 2018 22:10:37 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BuFHjZ8KAiJD; Fri, 21 Sep 2018 22:10:36 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Fri, 21 Sep 2018 22:10:36 -0600 (MDT) Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Warner Losh Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> <74775769-6810-63ab-d776-013bc72c8488@bluestop.org> <11385a3d-f6ec-453d-8a21-a29c34c94b0f@bluestop.org> From: Rebecca Cran Message-ID: Date: Fri, 21 Sep 2018 22:10:01 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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: Sat, 22 Sep 2018 04:10:04 -0000 On 9/21/18 10:00 PM, Warner Losh wrote: > That may be the issue... Does the patch I included help? I'm building now > on my stable system, but it's slow... It does seem to have got further this time, so a cautious yes. -- Rebecca From owner-freebsd-current@freebsd.org Sat Sep 22 04:58: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 0673810B125C; Sat, 22 Sep 2018 04:58:15 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it1-x144.google.com (mail-it1-x144.google.com [IPv6:2607:f8b0:4864:20::144]) (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 790E6815CB; Sat, 22 Sep 2018 04:58:14 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it1-x144.google.com with SMTP id 139-v6so4464232itf.0; Fri, 21 Sep 2018 21:58:14 -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=7MWIASlK2BQJHyrkY8E6lMEMAmOGyi+XyInmDXqlbvE=; b=J86FYwwOv1DNJVbq1/12czHHL5IQSoAGsFFwaYzQCdNRjrrUsh8lYhFFBga+X2hD0X i6xFjR3OQQ3iK2PbmYIxMkNmVtnwk9iUTwFbxaCBSL16+1olwkpsEKmPb4n8lGe10t/2 T2GbdMwLJE2kWh7agkO0rpg3v6CjwcQnRn1D+GVNKBXH6mqDI9wYaxZhFXIosNeVi1nW adEHUoEmpou60rN/YRsI1wBWd3jwp7A1jjPGEZxSsIBlwUTfnT0RRVPtcEESDB6iLwQA LS5Slble4YAH7ZhIXmQ1urUMex6CnhAW7lKEjB+nr4Of6DCKNLVoTLs5AFjSCOT+fvVN MLKA== 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=7MWIASlK2BQJHyrkY8E6lMEMAmOGyi+XyInmDXqlbvE=; b=pZDkvb2n2b4eUbmRfDheU7LPP4326M6DlsLKkmJ8v729boAuflG268NqrPYTvHef9a MpPkjj2lPCqGRKRDqtz7xIG+Mj/RNkXVa5SivE4jY0GBeoGrkFmb0dcJu0wo2b8/a1Zp le7M+YdAcDjVLG96QBDduU7IPmAQ/yCVt/jd/6GW54HE1iytkGOkWX4stls4ve3RWpqH UWW+1Eq3joacVD76q5HX2HtlER1Lmo20nE2heu+rT409LaCgFYABHDk+4QBonl5cGg00 ZEEJ07v4gM8qt4HNPZu3okgiHflM2l7d6demujE0et4lQdIXm5LTa7wy3jmRR/eNMQgg TlMA== X-Gm-Message-State: ABuFfohjLdAvRcOoTcOursBmLVY7DnFBTMyo5Eluubz3MKtQwalTjFuq PStTBMSysOLcgUDK7W6na4TxTbB48eUwNq3Au7ECLGU4 X-Google-Smtp-Source: ACcGV61BWi9nkxwqepSU45m6yeLj6FL5a7FICyMhcJGAqK3MKpz0yfQG0bxyQTg5nNGIpk8FMm1AAkxmrjHGUnsLbis= X-Received: by 2002:a24:7c4a:: with SMTP id a71-v6mr510865itd.69.1537592293704; Fri, 21 Sep 2018 21:58:13 -0700 (PDT) MIME-Version: 1.0 References: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> In-Reply-To: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> From: blubee blubeeme Date: Sat, 22 Sep 2018 12:58:01 +0800 Message-ID: Subject: Re: Good motherboard for Ryzen (first-gen) To: eric@vangyzen.net Cc: freebsd-stable@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: Sat, 22 Sep 2018 04:58:15 -0000 On Sat, Sep 22, 2018 at 10:56 AM Eric van Gyzen wrote: > I would like to build a Ryzen desktop. Can anyone recommend a good > motherboard? > > I'm planning on a first-gen, because the second-gen has similar > stability problems as the first-gen had, and AMD hasn't released errata > for the second-gen yet (as far as I know...I would love to be wrong). > > I would like to be a cool kid with a Threadripper, but I can't justify > the cost, so I'm thinking maybe a Ryzen 7 with /only/ 8 cores. :) > > Ideally, I want an Intel NIC, ECC memory support, and a 3-year warranty. > > Thanks in advance, > > Eric > > _______________________________________________ > 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" > I purchased MSI B350 Gaming Pro with a Ryzen 2600 it's been great but if you plan to run FreeBSD you'll need a graphics card that's supported by the current graphics drivers. I found something quite old, it works with the drm2 drivers and there's no issues. There's list of supported cards here: https://wiki.freebsd.org/Graphics There's work being done on improving the graphics drivers, soon you won't need to get such old GPU. As for ECC I don't think you'll find many 1st gen ryzen motherboards that support that but I could be wrong, spec and datasheet here: https://www.msi.com/Motherboard/B350M-GAMING-PRO/Specification From owner-freebsd-current@freebsd.org Sat Sep 22 05:30: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 D38FC10B1DD3; Sat, 22 Sep 2018 05:30:51 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it1-f177.google.com (mail-it1-f177.google.com [209.85.166.177]) (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 644A882421; Sat, 22 Sep 2018 05:30:51 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it1-f177.google.com with SMTP id d10-v6so4561211itj.5; Fri, 21 Sep 2018 22:30:51 -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=SGD3fdiYIIHqQsooR/sg9s/Fj7zJinG34pDzwoce/vI=; b=grzFrZ/wIb2r67seNT7VOSkK0ldPOMdPaIFd1BZXobGFLtATUreCx/VHVUL1bzo6Vi R0wRjHL4IBzd2wmAiTU4/0DHP5gFJZcHzl5LwzeaBzluDTeEYabyMxry+cXb2NPb/sAd nw/Y5N8fSYrFRm8GDk7GfpsY5xgCGsHuAcVhgh8ach8Zf5GeqOkb3AnA/H17uG9P1xn2 yHRagnmKTXoHfKVv9FR/hCZMLhCfwWzMUdJkbjeUcvfl0xCydUb+is6Doi9KTcxETYEW /Anp26QSDnWyKU9pC2RZ0TXKZUpUKuHQVVW7LjT9cewcvKndCZPlEfaYS2KEkzEuBwFR rawQ== X-Gm-Message-State: ABuFfoiO1sK4nIVZ5b7+uzrx1ywl3oUpGmRUm1rd/EzyI8sbNr92oklN /3wLCELVtkDNK1zzLDia8uoRBbs5 X-Google-Smtp-Source: ACcGV60g7G+QXucH19wgwX47+J5+oWUbpjM5zIQZVUAtrlBrEzrW2ZX82MjLdWD3DpHH71GJuMD8Gg== X-Received: by 2002:a24:a388:: with SMTP id p130-v6mr559079ite.146.1537593818677; Fri, 21 Sep 2018 22:23:38 -0700 (PDT) Received: from mail-it1-f172.google.com (mail-it1-f172.google.com. [209.85.166.172]) by smtp.gmail.com with ESMTPSA id y189-v6sm3041782itd.26.2018.09.21.22.23.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Sep 2018 22:23:38 -0700 (PDT) Received: by mail-it1-f172.google.com with SMTP id h23-v6so4502079ita.5; Fri, 21 Sep 2018 22:23:37 -0700 (PDT) X-Received: by 2002:a02:10c6:: with SMTP id 189-v6mr747328jay.54.1537593817810; Fri, 21 Sep 2018 22:23:37 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:7049:0:0:0:0:0 with HTTP; Fri, 21 Sep 2018 22:23:37 -0700 (PDT) In-Reply-To: References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> <74775769-6810-63ab-d776-013bc72c8488@bluestop.org> <11385a3d-f6ec-453d-8a21-a29c34c94b0f@bluestop.org> From: Conrad Meyer Date: Fri, 21 Sep 2018 22:23:37 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored To: Rebecca Cran Cc: Warner Losh , FreeBSD Current , "freebsd-toolchain@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: Sat, 22 Sep 2018 05:30:52 -0000 One thing that may allow progress is explicitly passing the path to a new enough linker to make. In the past when some I encountered a similar problem (I use amd64-xtoolchain-gcc, amd64-gcc, and binutils for toolchain, and due to some miscommunication the wrong linker was selected automatically), I had good results passing an explicit linker LD like: LD=/usr/local/bin/ld make -sj4 buildkernel KERNCONF=foo CROSS_TOOLCHAIN=amd64-gcc Best, Conrad On Fri, Sep 21, 2018 at 9:10 PM, Rebecca Cran wrote: > On 9/21/18 10:00 PM, Warner Losh wrote: > >> That may be the issue... Does the patch I included help? I'm building now >> on my stable system, but it's slow... > > > It does seem to have got further this time, so a cautious yes. > > > -- > Rebecca > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sat Sep 22 06:35: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 9EB4C10B3298 for ; Sat, 22 Sep 2018 06:35:46 +0000 (UTC) (envelope-from jmg@gold.funkthat.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 3B850849AE for ; Sat, 22 Sep 2018 06:35:46 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: by mailman.ysv.freebsd.org (Postfix) id F154F10B3293; Sat, 22 Sep 2018 06:35:45 +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 CF80310B3291 for ; Sat, 22 Sep 2018 06:35:45 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CE7D849A7; Sat, 22 Sep 2018 06:35:44 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w8M6Za4G079802 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 21 Sep 2018 23:35:37 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w8M6ZavV079801; Fri, 21 Sep 2018 23:35:36 -0700 (PDT) (envelope-from jmg) Date: Fri, 21 Sep 2018 23:35:36 -0700 From: John-Mark Gurney To: Lev Serebryakov Cc: current@FreeBSD.org, brnrd@FreeBSD.org, jkim@FreeBSD.org Subject: Re: Speed problems with both system openssl and security/openssl-devel Message-ID: <20180922063536.GK75530@funkthat.com> Mail-Followup-To: Lev Serebryakov , current@FreeBSD.org, brnrd@FreeBSD.org, jkim@FreeBSD.org References: <43892083.20180913024646@serebryakov.spb.ru> <468346531.20180917235220@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <468346531.20180917235220@serebryakov.spb.ru> X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Fri, 21 Sep 2018 23:35:37 -0700 (PDT) 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, 22 Sep 2018 06:35:47 -0000 Lev Serebryakov wrote this message on Mon, Sep 17, 2018 at 23:52 +0300: > Thursday, September 13, 2018, 2:46:46 AM, you wrote: > > > Linux have openssl 1.1.0f, and I've tried both system /usr/bin/openssl (1.0.2p) > > and /usr/local/bin/openssl from security/openssl-devel port (1.1.0i), results are > > virtually the same. I have "ASM" and "SSE2" options enabled in port. > > > What happens here? Why does FreeBSD's build of openssl use AES-NI so > > inefficient? > More datapoints. > > (1) aes-256-cbc behaves really wired. Time output is > completely bogus without "-elapsed" and speed is unbelievably low with > "-elapsed". aes-256-gcm doesn't have this anomaly This is because you're likely using /dev/crypto for the operations instead of software... $openssl engine (cryptodev) BSD cryptodev engine (dynamic) Dynamic engine loading support The times below are mesured on how much cpu time openssl spent, while all the work was done in the kernel... if you disable cryptodev usage, you should see better performance... > without "-elapsed" (please note "in 0.xxs" here): > > Doing aes-256-cbc for 3s on 16 size blocks: 503555 aes-256-cbc's in 0.60s > Doing aes-256-cbc for 3s on 64 size blocks: 520386 aes-256-cbc's in 0.54s > Doing aes-256-cbc for 3s on 256 size blocks: 435106 aes-256-cbc's in 0.44s > Doing aes-256-cbc for 3s on 1024 size blocks: 242832 aes-256-cbc's in 0.38s > Doing aes-256-cbc for 3s on 8192 size blocks: 49087 aes-256-cbc's in 0.09s > ... > aes-256-cbc 13393.26k 61782.64k 254599.17k 663093.25k 4289287.51k > > Doing aes-256-gcm for 3s on 16 size blocks: 12051311 aes-256-gcm's in 3.03s > Doing aes-256-gcm for 3s on 64 size blocks: 6428598 aes-256-gcm's in 3.04s > Doing aes-256-gcm for 3s on 256 size blocks: 2122316 aes-256-gcm's in 3.00s > Doing aes-256-gcm for 3s on 1024 size blocks: 610443 aes-256-gcm's in 3.13s > Doing aes-256-gcm for 3s on 8192 size blocks: 75836 aes-256-gcm's in 3.03s > ... > aes-256-gcm 63611.04k 135380.66k 181104.30k 199531.13k 204947.96k > > with "-elapsed": > > Doing aes-256-cbc for 3s on 16 size blocks: 493829 aes-256-cbc's in 3.01s > Doing aes-256-cbc for 3s on 64 size blocks: 530550 aes-256-cbc's in 3.06s > Doing aes-256-cbc for 3s on 256 size blocks: 426699 aes-256-cbc's in 3.01s > Doing aes-256-cbc for 3s on 1024 size blocks: 243305 aes-256-cbc's in 3.03s > Doing aes-256-cbc for 3s on 8192 size blocks: 48069 aes-256-cbc's in 3.01s > ... > aes-256-cbc 2626.91k 11087.41k 36317.07k 82191.94k 130919.48k > > Doing aes-256-gcm for 3s on 16 size blocks: 12041385 aes-256-gcm's in 3.08s > Doing aes-256-gcm for 3s on 64 size blocks: 6445757 aes-256-gcm's in 3.05s > Doing aes-256-gcm for 3s on 256 size blocks: 2129499 aes-256-gcm's in 3.01s > Doing aes-256-gcm for 3s on 1024 size blocks: 587396 aes-256-gcm's in 3.01s > Doing aes-256-gcm for 3s on 8192 size blocks: 75806 aes-256-gcm's in 3.03s > ... > aes-256-gcm 62590.75k 135047.68k 181245.26k 199977.06k 204866.89k -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@freebsd.org Sat Sep 22 08:57:29 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 563F1109066E; Sat, 22 Sep 2018 08:57:29 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (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 E491D8A554; Sat, 22 Sep 2018 08:57:28 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g3djA-0008ZM-Dg; Sat, 22 Sep 2018 08:57:24 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g3djA-0004fN-Bx; Sat, 22 Sep 2018 09:57:24 +0100 Date: Sat, 22 Sep 2018 09:57:24 +0100 To: freebsd-stable@FreeBSD.org, freebsd-current@freebsd.org, eric@vangyzen.net Subject: Re: Good motherboard for Ryzen (first-gen) References: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> In-Reply-To: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-Id: From: Pete French X-Mailman-Approved-At: Sat, 22 Sep 2018 10:55:59 +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: Sat, 22 Sep 2018 08:57:29 -0000 > I would like to build a Ryzen desktop.? Can anyone recommend a good > motherboard? I have oe of these: https://www.msi.com/Motherboard/X370-XPOWER-GAMING-TITANIUM but I just saw how much they are charging for it these days! I got one at about half that. I did originally get a B370 based board, but chnaged up for the X370 after I decided on a higher power Ryzen 7 and someone on ths list (can't remember who, sorry) reminded me that it would be more stable with the better quality power supplies on the non budget boards. It's a great board though. Ignore MSI slighly silly (as usual) promotional blurb and look at the specs and it's an excellent piece of kit. > I'm planning on a first-gen, because the second-gen has similar > stability problems as the first-gen had, and AMD hasn't released errata > for the second-gen yet (as far as I know...I would love to be wrong). Note that the Ryzen problems on FreeBSD aren't 100% solved yet - the Linux emulator doesn't work in STABLE, which might affect you ? Since the last BIOS upgrade and the patches in STABLE the system is certainly stable enough for a desktop though. I have only had two lockups since the last set of upgrades and I suspect that might have been related to me running virtual machines under VirtualBox as I stopped doing that and it's been fine ever since. > I would like to be a cool kid with a Threadripper, but I can't justify > the cost, so I'm thinking maybe a Ryzen 7 with /only/ 8 cores.? :) heh, yes, 8 cores and SMT makes for a ridiculously fast machine. Try a buildworld with -j16 on it. > Ideally, I want an Intel NIC, ECC memory support, and a 3-year warranty. Don't know about ECC, but the Titanium has an Intel NIC in it that works fine with igb driver. I used to drop in a separate Intel NIC card as so many of the boards came with cheap Realtek, but I dont have to with this one. Let us know how you get on.... -pete. From owner-freebsd-current@freebsd.org Sat Sep 22 15:08: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 49290109A8C1; Sat, 22 Sep 2018 15:08:46 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.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 C6981761A7; Sat, 22 Sep 2018 15:08:45 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 64ECE379AE; Sat, 22 Sep 2018 09:09:19 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id HldBgG6eF1DM; Sat, 22 Sep 2018 09:09:18 -0600 (MDT) Received: from tau.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Sat, 22 Sep 2018 09:09:18 -0600 (MDT) Subject: Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored From: Rebecca Cran To: Warner Losh Cc: Mark Johnston , Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" References: <2E7136DD-9C25-44C1-8C9A-310C2D1D7189@yahoo.com> <20180921193139.GB5120@raichu> <20180921220639.GF5120@raichu> <83c3a1bd-6922-20d1-4559-26bca1995229@bluestop.org> <33ea78c3-7954-d30e-4f40-dcada55e7367@bluestop.org> <74775769-6810-63ab-d776-013bc72c8488@bluestop.org> <11385a3d-f6ec-453d-8a21-a29c34c94b0f@bluestop.org> Message-ID: Date: Sat, 22 Sep 2018 09:08:43 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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: Sat, 22 Sep 2018 15:08:46 -0000 On 9/21/18 10:10 PM, Rebecca Cran wrote: > On 9/21/18 10:00 PM, Warner Losh wrote: > >> That may be the issue... Does the patch I included help? I'm building now >> on my stable system, but it's slow... > > It does seem to have got further this time, so a cautious yes. I can change that to a definite yes: >>> World build completed on Fri Sep 21 22:48:30 MDT 2018 -- Rebecca From owner-freebsd-current@freebsd.org Sat Sep 22 18:28: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 31F97109F40A; Sat, 22 Sep 2018 18:28:46 +0000 (UTC) (envelope-from shoesoft@gmx.net) 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 8D38B7DDBB; Sat, 22 Sep 2018 18:28:45 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from walrus.pepperland ([81.217.71.61]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MUDXS-1gC8cu3P8c-00R47n; Sat, 22 Sep 2018 20:28:30 +0200 Subject: Re: Good motherboard for Ryzen (first-gen) To: Eric van Gyzen , freebsd-stable@FreeBSD.org, freebsd-current@freebsd.org References: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> From: Stefan Ehmann Message-ID: Date: Sat, 22 Sep 2018 20:28:22 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:b54JK+HC0sRpgfMVK0JaJGCGV5saGPLWGZfk4T7U7EZjTBvTDrX o12v9WXVOkbIRPdMmXHTiCAwnudS1IYk+WZc2PE5BJEp7DKk/phfBayfT/Fj4sGCpCzTx4K OkqKegjRt6cS2o2NKilZBsHCPZP3QWMNGI2GUtO7oM6Cne2rbR9YFpq6+nnQwyjOx417ntE eqtz/Gr6j3APL9UDFS3GQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:ADTU2Y4L6mM=:m3JoAKU9/lFX8w8NwkAZY+ whVROd5UYdD4Fjd4xP/e/pfYfcWrdVUD+QzTMglE6szT+8pSHuFlURRAoNnGd/SfA0VsTdpw3 vQuRj4+rm4/Vuvk7n4CazDK2sdkTDSLwCqmUj9OEZmDXYGXzkmGxLV+bc4UfT/32u85eeMA8U a9vmJoSiO5aT1orXkgzZxRDDZShtP4yjs2sCAfiWWj+PWMPlhM5b/Xt/oaD6CPuC/sMhvtdCV of16x7zu/H02BAhlewdX8SZFZpLTAm9iZJBldbOLb1f8bKMPapgZFADZuOlMRKJF8crL4lSkW J4GgEHgh+Td+9waG/zHY6WQ3fVQwJpimi9qWj9km4dT+ECzP9ODfFpIBtbvNuIGhT5Kv4sQCb oWwiP3NsDcQ8EpusCghg8dbf9L18dGPK9DujGnjJw73A0Xkfh/7qxx7dPe9BqghfypzeK2DBK 0n9Sh0awQPiJmFB9SIliWV2hjspjGlsRljao/MKmcsBdLh/XDnEt1uEJgDt4JC1aXyO0CxuDJ PSVxHmWBSS4MjISOaFurrxWaIvu3JNsqDpl1Fv586AOvX5guXZDND9+9gTxiUnGY56UdvQx3n jyyrqlyVmOnd95n/52Z/xCu7Xqjl/LCyqgOma/ClM2BMTeT73hruVvte4Tmgx8BeP14xfLHqG K4xkol5W6kzcmZ7fhkmerPQWSM7vWWuMZ4Oi8DSaO6DDyO+VKZGrOlBMNwGfM54qSauBUfssB FCsydXLzG5XqHM3EWOOXvkI0o/CUsRCWBcypptroWV3y8cgC5r0vogsOEHiMEKb3yzHfJ+ZUs mnxonKASfXl8jTzPEDz3sHo2Ia53bP2i4y6V26tWhWK0jN9fmc= 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, 22 Sep 2018 18:28:46 -0000 On 9/22/18 4:53 AM, Eric van Gyzen wrote: > I would like to build a Ryzen desktop.  Can anyone recommend a good > motherboard? > > I'm planning on a first-gen, because the second-gen has similar > stability problems as the first-gen had, and AMD hasn't released errata > for the second-gen yet (as far as I know...I would love to be wrong). > > I would like to be a cool kid with a Threadripper, but I can't justify > the cost, so I'm thinking maybe a Ryzen 7 with /only/ 8 cores.  :) Running Ryzen 7 2700 with Asus X470-PRO. No major problems so far. Minor issues: - powerd/amdtemp don't work correctly, I'll probably retest when 12-BETA is out - Linuxolator doesn't work (as petefrench pointed out) - Had a crash while backing up to external HDD but pretty sure the problem was a bad SATA connection The system does a lot of poudriere builds. Cannot comment on long-time stability, system is off at night. > Ideally, I want an Intel NIC, ECC memory support, and a 3-year warranty. Board has an Intel igb NIC. According to the vendor "ECC support varies by CPU". But only found reports of ECC not working, not a single success story. The X370 board is a bit cheaper. Went for X470 because X370 boards may require firmware update for 2nd gen Ryzen. From owner-freebsd-current@freebsd.org Sat Sep 22 18:44: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 954A5109FF02; Sat, 22 Sep 2018 18:44:48 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0728F7E9CA; Sat, 22 Sep 2018 18:44:47 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=UFlDI8wA7U8vqggrtEr7Ul7bONi524aGWGDay/HhoAw=; b=PCDnBEqkFjSivg4+GUu6wQpJN9KVX4OhnDpyvpGpyUSu3lgd9lSqhCZbxN+YIyr29jzZ/b84xjNKhipPXyXDbL8IgmJlQ/zVWzKoDcxgET1D38ehrjfo3OGBnj7LmO+wJ/mba6NxF6Eilh6iwphzozvkznl5BRuPemJJYgxRyhc= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 646367af TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 22 Sep 2018 18:44:37 +0000 (UTC) Date: Sat, 22 Sep 2018 21:44:31 +0300 From: Greg V Subject: Re: Good motherboard for Ryzen (first-gen) To: Eric van Gyzen Cc: freebsd-stable@FreeBSD.org, freebsd-current@freebsd.org Message-Id: <1537641871.2008.0@hraggstad.unrelenting.technology> In-Reply-To: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> References: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> X-Mailer: geary/0.12.2 MIME-Version: 1.0 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: Sat, 22 Sep 2018 18:44:48 -0000 On Sat, Sep 22, 2018 at 5:53 AM, Eric van Gyzen =20 wrote: > I would like to build a Ryzen desktop. Can anyone recommend a good=20 > motherboard? >=20 > I'm planning on a first-gen, because the second-gen has similar=20 > stability problems as the first-gen had, and AMD hasn't released=20 > errata for the second-gen yet (as far as I know...I would love to be=20 > wrong). IIRC the weird freeze/segfault bugs were only in the early batches of=20 1st gen. If you get 2nd gen, you're *definitely* getting a stable chip.=20 My R7 1700 is from Aug 2017, never had any issues. So a 1st gen bought=20 today should be fine too of course, unless *somehow* you get very very=20 very old stock. > I would like to be a cool kid with a Threadripper, but I can't=20 > justify the cost, so I'm thinking maybe a Ryzen 7 with /only/ 8=20 > cores. :) Yeah, yeah. Good discounts on 1st gen Threadripper can be found these=20 days though=E2=80=A6 but still there's board cost + RAM cost (you have to=20 fill up 4 memory channels on TR if you want performance to not suck). > Ideally, I want an Intel NIC, ECC memory support, and a 3-year=20 > warranty. For ECC, you can google board name + ecc ram. You can often find=20 reports on forums/subreddits/whatever. Since you care about warranty, you probably don't care about=20 overclocking, so do not watch the following videos: B450 boards =E2=80=94=20 https://youtu.be/yWAwOH-egFs X470 =E2=80=94 https://youtu.be/L8T2gzIkw78 :) But still, good power delivery is important for an 8-core even at stock=20 settings, so avoid the latest ASUS TUF board, and super cheap boards in=20 general. I have an MSI X370 SLI PLUS. The firmware is good, RGB lighting support=20 is good (most important thing! lol. controllable under FreeBSD with=20 https://github.com/nagisa/msi-rgb), the VRM is okay but not super great=20 (8-core @ 1.39V 3.95GHz =E2=86=92 ~100 =E2=84=83 without any direct airflow= over=20 the VRM heatsink). NIC is Realtek, recognized by re(4), I never tried=20 it (I use a Mellanox card). Audio is Realtek, works fine 99% of the=20 time (very occasionally sound stops working, sysctl=20 dev.hdac.0.polling=3D1 brings it back). There is a pin header for the SPI=20 flash chip to recover a failed firmware update (I actually did this=20 once :D), but the pins are tiny (2mm instead of the usual 2.54). = From owner-freebsd-current@freebsd.org Sat Sep 22 19:42:27 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 57C6510A1BFF; Sat, 22 Sep 2018 19:42:27 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B000080BA6; Sat, 22 Sep 2018 19:42:26 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-lf1-x12f.google.com with SMTP id l26-v6so13677461lfc.8; Sat, 22 Sep 2018 12:42:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=M+poUU7Hrs7cgJvjLMl+iNTPNgZYsAWMgrWDla4enf4=; b=Vz4a9aTfV37LLvhKeqx026ET0LZbXvChbHMX3P/pAXMURPJlRZdxAYYTgJpIVXpRLn tSQP/mma56zzI16o7dk0n40wyL98wFd8olYZbQDpehKMvxSQWdUEc+MOZMSgCk5wI8Dc VAafoPv+04+b0ByTaqb9MAaMEMgpKJNSSKMgmdKmE2ojNXjLy/KshL+b+vV6TxsjPv0i G88RtmBYQL1nYhI7DsLJfUa5JYzLiGQiYIJdKtjKNxnANKXi80fGNmue8oFYrplVETw/ VjNaibK3mmgiSsRTBnMm7mCVKRBRuB+xAWB3agiYAlzfAPDDkuAKUPGcdbYUlxCU+P2J J10A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=M+poUU7Hrs7cgJvjLMl+iNTPNgZYsAWMgrWDla4enf4=; b=qQLwIDffg456LxCb+SJutcg43MSRsV518NjpU/82dMahA9dhCTeAlJITUWp9ZGYudk PqYL90g8D2YIlvr/aY70/l6+F8AUfByNI/wv9r/2trxd7d0/xxPuVyL3buh9tTs9rQD8 vlhz2R/U59aUS8Xq4x/kpWCSN6G3sAHfGBajreeOUoiQ9t/4bsfPcBx2lYG00k/3KiE3 lifFIM25X0o+lkINmKY1hcAH4qOEI8qHF3+EfhHOeIt7lJWg15uxg5I9EYe1yNC+tG81 MPE3KJY80lMMRveu4/i1FR5P8lhLLmlhp1OrD8nLD0Hi+O95cqgZGOrQKDFzxkgg9wvE wc8g== X-Gm-Message-State: APzg51DCl/ZL74VC2+QID1ANb+mrLwE9TIPPdQBxSq/xk4F4NBpeMJY5 0pULUMTbdCPUFqT1/GEmM+0fcZbS X-Google-Smtp-Source: ANB0VdYa9o8ENmHS7No/FIZetphy18VNAln+KeeGZAxwDM8+UMY98e1O1gj4RuPXRd5wkzTCSteqyA== X-Received: by 2002:a19:288c:: with SMTP id o134-v6mr145198lfo.124.1537645345279; Sat, 22 Sep 2018 12:42:25 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id a17-v6sm2891696lfj.92.2018.09.22.12.42.23 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 22 Sep 2018 12:42:24 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Sat, 22 Sep 2018 22:42:15 +0300 To: Eric van Gyzen Cc: freebsd-stable@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: Good motherboard for Ryzen (first-gen) Message-ID: <20180922224215.0cc7008f@gmail.com> In-Reply-To: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> References: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 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, 22 Sep 2018 19:42:27 -0000 T24gRnJpLCAyMSBTZXAgMjAxOCAyMTo1MzoyMCAtMDUwMA0KRXJpYyB2YW4gR3l6ZW4gPGVyaWNA dmFuZ3l6ZW4ubmV0PiB3cm90ZToNCg0KPiBJIHdvdWxkIGxpa2UgdG8gYnVpbGQgYSBSeXplbiBk ZXNrdG9wLsKgIENhbiBhbnlvbmUgcmVjb21tZW5kIGEgZ29vZCANCj4gbW90aGVyYm9hcmQ/DQoN Cmh0dHBzOi8vd3d3LmhhcmR3YXJlbHV4eC5kZS9jb21tdW5pdHkvZjEyL3BnYS1hbTQtbWFpbmJv YXJkLXZybS1saXN0ZS0xMTU1MTQ2Lmh0bWwNCkFueSBNb0JvIGJhc2VkIG9uIElSMzUyMDEgb3Ig QVNQMTQwNUkuDQoNCiANCj4gSSdtIHBsYW5uaW5nIG9uIGEgZmlyc3QtZ2VuLCBiZWNhdXNlIHRo ZSBzZWNvbmQtZ2VuIGhhcyBzaW1pbGFyIA0KPiBzdGFiaWxpdHkgcHJvYmxlbXMgYXMgdGhlIGZp cnN0LWdlbiBoYWQsIGFuZCBBTUQgaGFzbid0IHJlbGVhc2VkDQo+IGVycmF0YSBmb3IgdGhlIHNl Y29uZC1nZW4geWV0IChhcyBmYXIgYXMgSSBrbm93Li4uSSB3b3VsZCBsb3ZlIHRvIGJlDQo+IHdy b25nKS4NCj4gDQoNCkkgZG9udCBzZWUgYW55IGlzc2llcyB3aXRoIFJ5emVuczogMTMwMHggKDI1 IHdlZWspLCAyMjAwRywgMjcwMHguDQoNCg== From owner-freebsd-current@freebsd.org Sat Sep 22 19:48: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 4044F10A20D4; Sat, 22 Sep 2018 19:48:30 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (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 8B36B80F35; Sat, 22 Sep 2018 19:48:29 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-ed1-x52d.google.com with SMTP id f38-v6so13271163edd.8; Sat, 22 Sep 2018 12:48:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=RVq4BBsXJAA05DMoesUkIj7D1roTgMj0RSKUOnJ0Dbg=; b=lSCqoLerm4d6l/WBK9HJ3ej9RvC/b9PphoEsrPwdiAU7DobshtgvL7LZ8GcXQQpGyV T+I9ZH9GUk464UgPVom0vIKtrcFJQc13HpJolYOezVyy4o0BpzQNNJxXlMgs4nHUP+bF d8ZDIUC0sY1WnszyDMkrXkqJ0UR1T+Fyf2BOAUCje3IKjk8msDRRXXsUJ0Qd7dIrt/Lx fmn2PHYICzJ4hro6JR0f+5xO5GUK91FJec/56FAWuSIbWd+DV6bJJMDNQtKOAWAUfET4 qBvEuRQtmXB5G1KDGfdYKPYcP7gGcJmFU6ZYpHcwTze5RtHvdDfI+/WiLf/2QTx9z9Hp LHaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=RVq4BBsXJAA05DMoesUkIj7D1roTgMj0RSKUOnJ0Dbg=; b=cv11xJGvUIrPogM4BgpqCMERMVUKxJ0z6GgAygsvy/t/ePJsaBo4yCSnKhCfWzmT2g v1GbfFgBJ5qqwB/Txors4hMJxLuz+sQrdni3j6vlade6Weo/OoVZ5K+GuUtznj+esJdK ZzgkzPr4b0xgpfZl1vucfnOaUKLTw1mvnseGKpsaybLMF4eROaPYtql8/TIAf3uobPfb qMmrP7ou22275xYu73rptYSgvSSEJUrcfTZmR4R/aLfQ56mDp6XQeWWxNVHpt8M7b5GI Fd8ENdvBbD4Bk9/6ZK3Gbuj6i66Nxl6C5xCuqzywY3xXVZgeyYajAF1sId4ENd6zusLx UDnQ== X-Gm-Message-State: ABuFfojfDnew0hHrtwglQ4y0ZCN3XfCWN3gk2k0eLu7Gugjcw/CzaK1v 6P7YVepkPBpEyAXtog9wbxQ9elNLfIA= X-Google-Smtp-Source: ACcGV60IndgX1AP9Nc6h2QZxAvfpX+MKYJrUp3fUX2/lTEzKRMsbNjsCvihcOos3BxDac4Hfdux/zA== X-Received: by 2002:a50:8843:: with SMTP id c3-v6mr5790211edc.146.1537645708616; Sat, 22 Sep 2018 12:48:28 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id s36-v6sm5908185edb.56.2018.09.22.12.48.27 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 22 Sep 2018 12:48:27 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Sat, 22 Sep 2018 22:48:26 +0300 To: Stefan Ehmann Cc: Eric van Gyzen , freebsd-stable@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: Good motherboard for Ryzen (first-gen) Message-ID: <20180922224826.17866a38@gmail.com> In-Reply-To: References: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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, 22 Sep 2018 19:48:30 -0000 On Sat, 22 Sep 2018 20:28:22 +0200 Stefan Ehmann wrote: > Minor issues: > - powerd/amdtemp don't work correctly, I'll probably retest when > 12-BETA is out Will not. We does not have rep CPU temp offset table. Not sure about thing in base, but mine AMDTemp: https://reviews.freebsd.org/D9759 have sysctl tune for temperature offset, you can use it.