From owner-freebsd-current@freebsd.org Sun Dec 3 01:45:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1374E6FE4B for ; Sun, 3 Dec 2017 01:45:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8038D63F80 for ; Sun, 3 Dec 2017 01:45:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id c3c7993f TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sat, 2 Dec 2017 17:45:09 -0800 (PST) Subject: Re: Error attempting to link during buildworld To: Warner Losh Cc: FreeBSD Current References: <520eb756-6d01-23d2-3321-b3db6dc3438c@nomadlogic.org> <2e3d1848-81ed-6112-33c6-424b33a85fd6@nomadlogic.org> From: Pete Wright Message-ID: <23a00406-e318-7775-29a4-88f884a51f2a@nomadlogic.org> Date: Sat, 2 Dec 2017 17:45:17 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.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.25 Precedence: 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, 03 Dec 2017 01:45:22 -0000 On 12/02/2017 12:30, Warner Losh wrote: > On Sat, Dec 2, 2017 at 12:50 PM, Pete Wright wrote: > >> >> On 12/01/2017 11:43, Pete Wright wrote: >> >>> Hi All, >>> >>> I am running into this error when attempting to buildworld from a >>> checkout I made recently (git hash 76ca06b62f3bfb21f1f2e1295eb89e >>> 3c235bdda7) >>> >>> --- all_subdir_stand --- >>> /usr/home/pete/git/freebsd/stand/i386/libi386/libi386.a(bootinfo64.o): >>> In function `bi_checkcpu': >>> /usr/home/pete/git/freebsd/stand/i386/libi386/bootinfo64.c:149: >>> undefined reference to `read_eflags' >>> /usr/home/pete/git/freebsd/stand/i386/libi386/bootinfo64.c:150: >>> undefined reference to `write_eflags' >>> /usr/home/pete/git/freebsd/stand/i386/libi386/bootinfo64.c:151: >>> undefined reference to `read_eflags' >>> cc: error: linker command failed with exit code 1 (use -v to see >>> invocation) >>> *** [loader.sym] Error code 1 >>> >>> >>> Has anyone else seen this? I'm not sure if I have some stale files that >>> need to be purged, or if this is a bug due to me using ccache. I'm asking >>> here tho as I'd love to preserve my ccache and save some cycles rebuilding >>> LLVM :) >>> >> just following up on this thread - i assume others have been able to >> buildworld on amd64, and have not been getting this linker error? i have a >> fresh checkout from this morning, tested with and without ccache and am >> still getting this same error. my system is currently at this revision: >> >> $ uname -ar >> FreeBSD runner 12.0-CURRENT FreeBSD 12.0-CURRENT #1 63d5d6c71fb(master): >> Sat Nov 18 08:36:45 PST 2017 pwright@runner:/usr/obj/usr/ho >> me/pwright/git/freebsd/amd64.amd64/sys/GENERIC-EVDEV amd64 >> >> >> any tips on helping debug this as well would be appreciated - as i'm not >> %100 sure where to start (i.e. how to invoke the linker with the "-v" flag >> for buildworld :) > > With today's tree, I can both build the loader by hand and as part of > buildworld. I'm keen on fixing this, but I've no clue why it's failing for > you. > > Have any weird optimizer settings? Do you get any reports of functions not > declared? thanks for getting back to me Warner. I do not have any optimization flags, although while i do use ccache i am able to reproduce this by disabling it in src.conf. i also am not seeing any reports of functions not being declared, although i'm currently re-testing the build now with a single worker passed to make so that i can get clearer output to validate this. i'm also going to try on another box running current i have to see if this is just my laptop being silly or if there is a real issue. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Sun Dec 3 06:42:26 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 559A9DF09D9 for ; Sun, 3 Dec 2017 06:42:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3CF346DCAE for ; Sun, 3 Dec 2017 06:42:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 3B53BDF09D8; Sun, 3 Dec 2017 06:42:26 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AE98DF09D7 for ; Sun, 3 Dec 2017 06:42:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E43286DCAD for ; Sun, 3 Dec 2017 06:42:25 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from e-bsd.cs.huji.ac.il ([132.65.80.241] helo=outmail.cs.huji.ac.il ident=exim) by kabab.cs.huji.ac.il with esmtp id 1eLNyg-000Llx-DS; Sun, 03 Dec 2017 08:42:14 +0200 Received: from [132.65.179.42] (helo=imac.bk.cs.huji.ac.il) by outmail.cs.huji.ac.il with esmtpsa id 1eLNyg-00013v-4q; Sun, 03 Dec 2017 08:42:14 +0200 From: Daniel Braniss Message-Id: <42427F81-E6FE-43CE-87D5-2560CC66F866@cs.huji.ac.il> Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: what happened to src/sys/boot? Date: Sun, 3 Dec 2017 08:42:13 +0200 In-Reply-To: Cc: FreeBSD Current To: Warner Losh References: <39F80CE7-BECF-4D4F-ACEB-5B6C52FC241B@cs.huji.ac.il> X-Mailer: Apple Mail (2.3445.4.7) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Dec 2017 06:42:26 -0000 > On 2 Dec 2017, at 22:31, Warner Losh wrote: >=20 >=20 >=20 > On Sat, Dec 2, 2017 at 1:26 PM, Daniel Braniss > wrote: >=20 >=20 >> On 2 Dec 2017, at 17:42, Warner Losh > wrote: >>=20 >>=20 >>=20 >> On Sat, Dec 2, 2017 at 6:42 AM, Daniel Braniss > wrote: >> Hi, >> it seems to have disappeared. >>=20 >> After discussion on arch@, they were move to src/stand. They aren't = part of the kernel, and this was the previous historic place for them. = This will make things like the lua boot loader a bit easier, though we = still have a bit too much accumulated debt in the boot loader that needs = to be addressed first. >>=20 >> Warner=20 >=20 > this is what happens when you are at the BEOT :-) > now lets see how difficult it is to get ubldr for allwinner to = compile. >=20 > Builds for me. Lemme know if that's not true for you. >=20 > Warner=20 changed sys/boot to stand in crochet/lib/freebsd.sh, now will check if all this works! thanks, danny From owner-freebsd-current@freebsd.org Sun Dec 3 08:28:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19C7DDF3E61 for ; Sun, 3 Dec 2017 08:28:02 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCFF17064A for ; Sun, 3 Dec 2017 08:28:01 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x231.google.com with SMTP id w128so5637093ywa.1 for ; Sun, 03 Dec 2017 00:28:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uJNzOgzuhCRBhlZSql3wzseJ7CLzp5imX80xNBP3ahA=; b=A8700NJ2k/27tXWEKMO/faGK59LWhzUjPD9mb2GTAZ9EcaBbRt0Fovxx9beWzYSKJD jZwsQQDT729sBIa6ert28uY040pNJIj2nFobbTvWiT/Fd8Vgr5XDdadhCrQkneH7WnDg dbHDKx0fHeEvXEVeux9RBoUyb/Z6vyqRsieso= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uJNzOgzuhCRBhlZSql3wzseJ7CLzp5imX80xNBP3ahA=; b=aGOeQk7uuOmWnx7UTHbBM7Ztoz1zy05gB2CrBA6p3LFAyJ14o2zvtECtvz/m8MSshx wr4wAnz+01ztQCTflBuHT85a0a3oev/F5BGA15wt+Wfam19aDwkmHB+FbrDXIHlAzmco JDoIK8Q1rUpmrkupU6AXccY5NGMyFgHDPW40zR+MHah12zL1T6J82s3BEcQeEelL2kvA +o/EFTkalyKkm3EIVCthhzL5EGIDCAsGzl/pmcO+ilbpTt4wDs71ZSEsxVF0KeTKMgu1 ABPYHdlSZS6NqovjVMVRekBlPvRIEgzsWmGjelj/sf41b7AHV6TNu9Ho1Tfb83crFg0p 84+A== X-Gm-Message-State: AJaThX4qEvWL6mUApzmVInnNhXJAJ7vClqrKknTPo4gVmqnAwfURiSAX 2He0XAQ7iAr5ioUNV+9fSrOm0sG9Rz7HjQ303hTELQ== X-Google-Smtp-Source: AGs4zMZftVI/N84+F1SGPdt22/cDa+z/RV8Xf6GHgVpC0bkwhQdFz+X67u+TAwRThGiSNeibQSfqGodBCw1E6oTDoLA= X-Received: by 10.129.122.194 with SMTP id v185mr8070465ywc.204.1512289680838; Sun, 03 Dec 2017 00:28:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.15.66 with HTTP; Sun, 3 Dec 2017 00:27:30 -0800 (PST) In-Reply-To: <23a00406-e318-7775-29a4-88f884a51f2a@nomadlogic.org> References: <520eb756-6d01-23d2-3321-b3db6dc3438c@nomadlogic.org> <2e3d1848-81ed-6112-33c6-424b33a85fd6@nomadlogic.org> <23a00406-e318-7775-29a4-88f884a51f2a@nomadlogic.org> From: Eitan Adler Date: Sun, 3 Dec 2017 00:27:30 -0800 Message-ID: Subject: Re: Error attempting to link during buildworld To: Pete Wright Cc: Warner Losh , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Dec 2017 08:28:02 -0000 On 2 December 2017 at 17:45, Pete Wright wrote: > i also am not seeing any reports of functions not being declared, although > i'm currently re-testing the build now with a single worker passed to make > so that i can get clearer output to validate this. i'm also going to try on > another box running current i have to see if this is just my laptop being > silly or if there is a real issue. Just ran into this though it went away after a 'svn up'. -- Eitan Adler From owner-freebsd-current@freebsd.org Sun Dec 3 11:43:43 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E0C3DF8628; Sun, 3 Dec 2017 11:43:43 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC8D975C7C; Sun, 3 Dec 2017 11:43:42 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id u42so15698115ioi.9; Sun, 03 Dec 2017 03:43:42 -0800 (PST) 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=hqxT3pmHQDT1GRnBKJgL08bcMzFIQIa6Ct+8fwx/aec=; b=UvjFOD02RGAdDU0MAbK9VYF1hZMeRmPmlpmMHP9g4dQDKYljxWask8aPGfykpAMOqL HMFqQqBS5HlMNmGQ7pdH2YGqaPCYYhb4jVZcu6M67s3IogPn6IykJFH7in80d3nWaLCW lS4fpMkPjU8YYE+1pDEg4JIH6ngDlILBuq9zSfGheLwWVSWkeWQDA3KMTlFdpvXIxCrU CUgseuPvOIki7qKi6x+nyQb4EC44RA+sAmRTOmiX0dduGO+KUqlO9pVVOGhAeSx8XQSU F3A4ln4kL5KfbQNqBBcbKZ76ni9xWdeG2A2JB0499K7zAJhoC8xXttJWKoD1DjMuA19C 8zjg== 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=hqxT3pmHQDT1GRnBKJgL08bcMzFIQIa6Ct+8fwx/aec=; b=mdQvy0koA6UgUbJujwcef0xtpPHRll8bnWMl6283LFOgmX2kONXwMXMFKxK/FxZz2d 3hpCJTSiGZS6t2a3hwCTg6INF54vXVidpQDI2G9XNEWDk4geeCJlOit6Ep4vdwHUfkPK wk/Q4b4zjFXnM7GwZQbTAOtMGQTNsi8HoFHZpRsSj+LWwfAdkemP0cRyV4U+jQvEq0A4 YgDodB6p8CmO/dPHKKn/QuW2qZwgBV5vi8eCYMu9lRP79Sb5wI8bhlrHYPZywazktUlo iv7xREx+LfoqmXYEII9lyUQ6ezWMPc1J3ebLSCVBiFQ9I95Xr4JZaaFhXvKC54BjYAez fnjg== X-Gm-Message-State: AJaThX4mHpdu3Jd1eHMLLp2/MjgnzF469XjaFka1D6GZuTs8LQd+CTrR ewjSjbpErlTOD2CzpKxWTz3OKwC8uaR7eedaw4Vlwg== X-Google-Smtp-Source: AGs4zManUXEeHLmmYlnhldQ1ofNj8/XEryOZNbXaAafIhZ15G8lTCXC2GNaAKpCa2FtRvzd8PJ+F+4slgpr1j9cHT48= X-Received: by 10.107.5.147 with SMTP id 141mr17291520iof.213.1512301421849; Sun, 03 Dec 2017 03:43:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.11.31 with HTTP; Sun, 3 Dec 2017 03:43:41 -0800 (PST) From: blubee blubeeme Date: Sun, 3 Dec 2017 19:43:41 +0800 Message-ID: Subject: Linux KMS/DRM and Google DRM To: FreeBSD current , FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Dec 2017 11:43:43 -0000 Google is trying to get HDMI drm upstream into the linux kernel: https://www.phoronix.com/scan.php?page=news_item&px=2017-Google-Intel-HDCP-DRM As we see this coming, how would the guys on FreeBSD working on that Linux kmod stuff deal when this stuff starts to creep into the linux kernel? From owner-freebsd-current@freebsd.org Sun Dec 3 12:49:23 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D9C8DFA59F; Sun, 3 Dec 2017 12:49:23 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv73.fwdcdn.com (frv73.fwdcdn.com [212.42.77.73]) by mx1.freebsd.org (Postfix) with ESMTP id 0A60C77BDE; Sun, 3 Dec 2017 12:49:22 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from [10.10.17.72] (helo=frv157.fwdcdn.com) by frv73.fwdcdn.com QID:1eLTST-000N2V-UA/RC:2; Sun, 03 Dec 2017 14:33:21 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=LtC7LI1YnI7lG8qP4dUOL9EJwMacJwlJtyYcSnTD9Hw=; b=HeDWIPBJKLZoz66ns2ZXg7ZCcF 7TBQ3X1lhz3f7i0OoUWkekvqxi2+sgTvpt8O4A8nKFMA5WLyIs5+MgKU/ell3C6mJdob2ZHwN4Mae mSBdMMbhL8+Rjd9qLyAzSDzwAiX1Nt2bVQ6z2U4abzxIp331kVFBosObslE32hC573lU=; Received: from [109.122.31.98] (helo=nonamehost) by frv157.fwdcdn.com with esmtpsa ID 1eLTSK-000E1j-2E ; Sun, 03 Dec 2017 14:33:12 +0200 Date: Sun, 3 Dec 2017 14:33:11 +0200 From: Ivan Klymenko To: blubee blubeeme Cc: FreeBSD current , FreeBSD Ports Subject: Re: Linux KMS/DRM and Google DRM Message-ID: <20171203143311.636f5f61@nonamehost> In-Reply-To: References: X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Authentication-Result: IP=109.122.31.98; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-Ukrnet-Yellow: 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Dec 2017 12:49:23 -0000 =D0=92 Sun, 3 Dec 2017 19:43:41 +0800 blubee blubeeme =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > Google is trying to get HDMI drm upstream into the linux kernel: > https://www.phoronix.com/scan.php?page=3Dnews_item&px=3D2017-Google-Intel= -HDCP-DRM >=20 > As we see this coming, how would the guys on FreeBSD working on that > Linux kmod stuff deal when this stuff starts to creep into the linux > kernel? Why do not they arrange DRM directly into the eyes or brain? From owner-freebsd-current@freebsd.org Sun Dec 3 16:36:55 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2211DFF62D for ; Sun, 3 Dec 2017 16:36:55 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A96AF7D94F for ; Sun, 3 Dec 2017 16:36:55 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 2e34a2e0 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sun, 3 Dec 2017 08:36:42 -0800 (PST) Subject: Re: Error attempting to link during buildworld To: Eitan Adler Cc: Warner Losh , FreeBSD Current References: <520eb756-6d01-23d2-3321-b3db6dc3438c@nomadlogic.org> <2e3d1848-81ed-6112-33c6-424b33a85fd6@nomadlogic.org> <23a00406-e318-7775-29a4-88f884a51f2a@nomadlogic.org> From: Pete Wright Message-ID: Date: Sun, 3 Dec 2017 08:36:53 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: 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.25 Precedence: 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, 03 Dec 2017 16:36:55 -0000 On 12/03/2017 00:27, Eitan Adler wrote: > On 2 December 2017 at 17:45, Pete Wright wrote: >> i also am not seeing any reports of functions not being declared, although >> i'm currently re-testing the build now with a single worker passed to make >> so that i can get clearer output to validate this. i'm also going to try on >> another box running current i have to see if this is just my laptop being >> silly or if there is a real issue. > Just ran into this though it went away after a 'svn up'. > i'm starting to suspect my current world must be in a broken state. i've tried a fresh checkout, same error.  then checked out the revision of my currently running world/kernel and get a similar linker error - which seems to indicate last time i updated my system something went bad with llvm/clang maybe?  now i just need to figure out how to get myself out of this whole i've apparently dug myself into :) -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Sun Dec 3 18:55:36 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B9C3E5EF87 for ; Sun, 3 Dec 2017 18:55:36 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 01C2930FF for ; Sun, 3 Dec 2017 18:55:36 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id F23AFE5EF84; Sun, 3 Dec 2017 18:55:35 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1D38E5EF7E for ; Sun, 3 Dec 2017 18:55:35 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8573130FE for ; Sun, 3 Dec 2017 18:55:35 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from e-bsd.cs.huji.ac.il ([132.65.80.241] helo=outmail.cs.huji.ac.il ident=exim) by kabab.cs.huji.ac.il with esmtp id 1eLZQ9-000CrK-6t; Sun, 03 Dec 2017 20:55:21 +0200 Received: from [132.65.179.42] (helo=imac.bk.cs.huji.ac.il) by outmail.cs.huji.ac.il with esmtpsa id 1eLZQ8-0003V7-WB; Sun, 03 Dec 2017 20:55:21 +0200 From: Daniel Braniss Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: what happened to src/sys/boot? Date: Sun, 3 Dec 2017 20:55:20 +0200 In-Reply-To: <42427F81-E6FE-43CE-87D5-2560CC66F866@cs.huji.ac.il> Cc: FreeBSD Current To: Warner Losh References: <39F80CE7-BECF-4D4F-ACEB-5B6C52FC241B@cs.huji.ac.il> <42427F81-E6FE-43CE-87D5-2560CC66F866@cs.huji.ac.il> X-Mailer: Apple Mail (2.3445.4.7) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Dec 2017 18:55:36 -0000 > On 3 Dec 2017, at 8:42, Daniel Braniss wrote: >=20 >=20 >=20 >> On 2 Dec 2017, at 22:31, Warner Losh > wrote: >>=20 >>=20 >>=20 >> On Sat, Dec 2, 2017 at 1:26 PM, Daniel Braniss >> wrote: >>=20 >>=20 >>> On 2 Dec 2017, at 17:42, Warner Losh >> = wrote: >>>=20 >>>=20 >>>=20 >>> On Sat, Dec 2, 2017 at 6:42 AM, Daniel Braniss >> wrote: >>> Hi, >>> it seems to have disappeared. >>>=20 >>> After discussion on arch@, they were move to src/stand. They aren't = part of the kernel, and this was the previous historic place for them. = This will make things like the lua boot loader a bit easier, though we = still have a bit too much accumulated debt in the boot loader that needs = to be addressed first. >>>=20 >>> Warner=20 >>=20 >> this is what happens when you are at the BEOT :-) >> now lets see how difficult it is to get ubldr for allwinner to = compile. >>=20 >> Builds for me. Lemme know if that's not true for you. >>=20 >> Warner=20 >=20 > changed sys/boot to stand in crochet/lib/freebsd.sh, > now will check if all this works! ok, the image created now boots on both orangepi-one and nanopi-neo, but without ethernet!=20 time to figure out what=E2=80=99s missing in the dtb=E2=80=99s cheers, danny >=20 > thanks, > danny >=20 > _______________________________________________ > freebsd-current@freebsd.org = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current = > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org = " From owner-freebsd-current@freebsd.org Sun Dec 3 20:22:28 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53CFBE66A6E for ; Sun, 3 Dec 2017 20:22:28 +0000 (UTC) (envelope-from linimon@lonesome.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 3CD2D654F5 for ; Sun, 3 Dec 2017 20:22:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3BE70E66A6D; Sun, 3 Dec 2017 20:22:28 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3ADD1E66A6C for ; Sun, 3 Dec 2017 20:22:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 201E6654F4 for ; Sun, 3 Dec 2017 20:22:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 1E037BFA; Sun, 3 Dec 2017 14:22:27 -0600 (CST) Date: Sun, 3 Dec 2017 14:22:26 -0600 From: Mark Linimon To: Daniel Braniss Cc: Warner Losh , FreeBSD Current , freebsd-arm@lonesome.com Subject: orangepi [was: what happened to src/sys/boot?] Message-ID: <20171203202225.GB4725@lonesome.com> References: <39F80CE7-BECF-4D4F-ACEB-5B6C52FC241B@cs.huji.ac.il> <42427F81-E6FE-43CE-87D5-2560CC66F866@cs.huji.ac.il> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Dec 2017 20:22:28 -0000 On Sun, Dec 03, 2017 at 08:55:20PM +0200, Daniel Braniss wrote: > ok, the image created now boots on both orangepi-one and nanopi-neo, > but without ethernet! So w/rt orangepi-one testing I think I'm now at parity with your build -- with whatever bits I had a week ago. e.g. I also do not detect the ethernet. I am currently testing a bad hack for orangepi-plus2e that disables attaching the mixer to see if I can avoid a panic on boot, so I can get at least as far as the orangepi-one results. That's with the very latest code checkout. I'll let the list know if I get anywhere. mcl From owner-freebsd-current@freebsd.org Sun Dec 3 20:33:20 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9141DE67108 for ; Sun, 3 Dec 2017 20:33:20 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (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 2BD9865B00 for ; Sun, 3 Dec 2017 20:33:19 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Sun, 03 Dec 2017 21:33:10 +0100 id 00DD603A.5A245F86.00007AF3 Date: Sun, 3 Dec 2017 21:33:09 +0100 From: Milan Obuch To: Mark Linimon Cc: Daniel Braniss , Warner Losh , freebsd-current@freebsd.org Subject: Re: orangepi [was: what happened to src/sys/boot?] Message-ID: <20171203213309.77b3aa40@zeta.dino.sk> In-Reply-To: <20171203202225.GB4725@lonesome.com> References: <39F80CE7-BECF-4D4F-ACEB-5B6C52FC241B@cs.huji.ac.il> <42427F81-E6FE-43CE-87D5-2560CC66F866@cs.huji.ac.il> <20171203202225.GB4725@lonesome.com> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; i386-portbld-freebsd10.4) 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.25 Precedence: 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, 03 Dec 2017 20:33:20 -0000 On Sun, 3 Dec 2017 14:22:26 -0600 Mark Linimon wrote: > On Sun, Dec 03, 2017 at 08:55:20PM +0200, Daniel Braniss wrote: > > ok, the image created now boots on both orangepi-one and nanopi-neo, > > but without ethernet! > > So w/rt orangepi-one testing I think I'm now at parity with your > build -- with whatever bits I had a week ago. e.g. I also do not > detect the ethernet. > > I am currently testing a bad hack for orangepi-plus2e that disables > attaching the mixer to see if I can avoid a panic on boot, so I can > get at least as far as the orangepi-one results. That's with the > very latest code checkout. > > I'll let the list know if I get anywhere. > > mcl > Please see thread on freebsd-arm mailing list starting with my message titled 'Allwinner H3/H2+ dts question - regression?' from Sun, 26 Nov 2017. One small point to add - while with revision 326187 and some older dtb (or with dtb gained via this thread) ethernet works, with revision 326310 and the same dtb it does not. I noticed when doing svn upgrade some changes in Allwinner awg sources, but did not analyze them yet. All dts currently in our source tree are totally ethernet-less when coming to Allwinner SoCs. That all for now, If I find anything interesting/usefull, I'll keep you informed. Regards, Milan From owner-freebsd-current@freebsd.org Sun Dec 3 23:50:07 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52AFFE6C31B for ; Sun, 3 Dec 2017 23:50:07 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 24ABF6EC68 for ; Sun, 3 Dec 2017 23:50:06 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D9DFE209F3 for ; Sun, 3 Dec 2017 18:49:58 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Sun, 03 Dec 2017 18:49:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=Ds7Vri9le2MAn6/9aiZqsNZ6MP2FjPWkHfyWece1nV0=; b=H/60rZ7C KIIDhxYnCtKFgC5y3WKJoxj/G+JT4LR1LQmhggN62cint0teWYS4M8Uuk2PX4ZzX EFsejE0N0aaecf0iVgN+JlgA0r1ZTBnEv1cVqlpH0H4wVt9azmNq9thhanMdWGnL ThhmBmiVfngjegoahC8JjH/4MKdFjEW5Lj+0JAU1L1tiQXZtJN5yaBVekut8+b9v K3+L+FM8DkcY9MFjyX4gvzCXMNmTPK4Dsv1rzBnp0oIo4y6QdrasqS5tkOUkQO8e f/MYk7cqcfYs7nqNRUrSZ/P4bFr1CuZLAh/WOGd1rOObDreaN3y/bjWpJZo1/+Xm nv8ozBgC5wkTMQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=Ds7Vri9le2MAn6/9aiZqsNZ6MP2Fj PWkHfyWece1nV0=; b=bEwdetB6DbmUYWa7uoKud1EuIEcMI00TUDs11Ek0uEpII RroPTcL4HAdv3NZoIdGHa/U5qf/9GGaraDI5bGxt+UGChxovQM7jplqW1ENZcchS /xetNEfBOmrqVv2TV1h5UpIDQzGv3bRxXneoTfpj7kQ//lp2yawRtQ4px5gvLqXI 9fRriKx4XEhOMlGGkSMgFK+tbeFm8lkqrBtJb7I81H7i1GT6iftjoOgi6t9SLgFv cLMXMP0Ggzdzd4BvyzOO7dg3SqJMStK9tBRgaKh244ATiycbGKdxYiSI/TKd5AmG +vbc0c9QFnsC8Xc9C+GlNiApjmEc/xArnIRpbE65Q== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id BD5B14125; Sun, 3 Dec 2017 18:49:58 -0500 (EST) Message-Id: <1512344998.2249959.1192664520.6B278E9D@webmail.messagingengine.com> From: Dave Cottlehuber To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-f34a76a1 Date: Mon, 04 Dec 2017 00:49:58 +0100 Subject: panic: Lock PFil shared rmlock not read locked @ /usr/src/sys/net/pfil.c:116 prior to r326363 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Dec 2017 23:50:07 -0000 I'm seeing this repeatedly in the last ~ 2 weeks, present in r326363 and typically panics 1-15m post boot since this weekend's update. I'm currently bisecting my way back; it looks like its not in r325755, but I can't be sure for a few more hours. https://s3.amazonaws.com/uploads.hipchat.com/8784/2508819/MGim1y8pQt1o1xK/IMG_2698.JPG # uname -a FreeBSD wintermute.skunkwerks.at 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r326363+fcb3a5a8a12d(master): Wed Nov 29 11:37:17 UTC 2017 root@wintermute:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 # dmesg https://gist.github.com/dch/68dd6f8d44dd76c558908e71dc3e1f87#file-dmesg-log + other logs in same gist Suggestions how to get from X to debugger would help, as would setting up serial console over ipmi - this is a supermicro motherboard. A+ Dave From owner-freebsd-current@freebsd.org Mon Dec 4 00:24:25 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF004E6D845 for ; Mon, 4 Dec 2017 00:24:25 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88B4870018 for ; Mon, 4 Dec 2017 00:24:25 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qk0-x22d.google.com with SMTP id t187so19512673qkh.3 for ; Sun, 03 Dec 2017 16:24:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=P+4NBjY525LxnFvU0vqASt98lcI+Jf7a5aAG1DLIXeQ=; b=pPNnRYPqRa/IJzbbkFjv1gvIIo+21087v+H9sILoAJI1VP+Vsy0RDIfAncpL0i/jZA A/gxiDiMwYHIDuIKP5PNh2xHPFq1OtbKxaxv5hsXeDhzWpJs7PlRR8vkTua+vk83k9ff TM1ovvhMXUxVN7pqtngoizMbFOdRGIGisUaVM75xKg+4XeZUoXY741ms6+qCXaR22exo zF0t88nxoN83/o+Y0Dj92Xgp0zIZvp0hUmAicRGd5rotNzSWec1+wvgVVTMCdC3A35Q9 AR9ntCsYOmtfXmqsm1/A9VmR0zStjxb86oann4Sp+zgkV4QVvCpjq8sfXBGwjLFI+8MZ eaEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=P+4NBjY525LxnFvU0vqASt98lcI+Jf7a5aAG1DLIXeQ=; b=W8W+bsycNqecTDeejFov/OuqnzLnlyCzmNltQaK+9vKXnDBq5kUTjEYypLixXQhEfW u8sj3hQuRHcSz5bAt1ldc/ZSQQ7H0D6AyeUOi+wbwKJPVnP+nYEd86j2Gk4TRn1ljur0 BNWUTT/AO08lDcEOYQUfG342HGOXMuBlWrAPK/IAXAZmQnx0tV1NMb89/7G4+lV0r0kL 3eyzX05ouNLgnOlETz1B8XETn4RCbkBq3gVmAy9wJuAqKmPF0JoZWp6CTEjZr8FWjmgM AbihOm1uu2ULwTStcT2pbqlZ7dS81/YJBKY8mDFtTceyrMm9JffGGy6qaxmWYPIRpOZm u0xw== X-Gm-Message-State: AKGB3mLFtX8EXKHFkHRItMAEMNVy2TNMKk7UWYllG2I1iuknII6KX2xT a+70rVEjkAymWh6Ic+qUSk0mgHsXmI75DzEQVl17iw== X-Google-Smtp-Source: AGs4zMb24SCjQuEdxWztartGt53emr+pPtoVMvy5402p3IENytUKfbnR6YZE3LxB1Tp+6qOniDn0DEZW76R8IqQCQYk= X-Received: by 10.233.220.199 with SMTP id q190mr18379783qkf.72.1512347064609; Sun, 03 Dec 2017 16:24:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.39.211 with HTTP; Sun, 3 Dec 2017 16:24:24 -0800 (PST) In-Reply-To: <1512344998.2249959.1192664520.6B278E9D@webmail.messagingengine.com> References: <1512344998.2249959.1192664520.6B278E9D@webmail.messagingengine.com> From: Ryan Stone Date: Sun, 3 Dec 2017 19:24:24 -0500 Message-ID: Subject: Re: panic: Lock PFil shared rmlock not read locked @ /usr/src/sys/net/pfil.c:116 prior to r326363 To: Dave Cottlehuber Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 00:24:25 -0000 Please update to r326376 or later. That will likely fix you issue. On Sun, Dec 3, 2017 at 6:49 PM, Dave Cottlehuber wrote: > I'm seeing this repeatedly in the last ~ 2 weeks, present in r326363 > and typically panics 1-15m post boot since this weekend's update. I'm > currently bisecting my way back; it looks like its not in r325755, but I > can't be sure for a few more hours. > > https://s3.amazonaws.com/uploads.hipchat.com/8784/2508819/MGim1y8pQt1o1xK/IMG_2698.JPG > > # uname -a > FreeBSD wintermute.skunkwerks.at 12.0-CURRENT FreeBSD 12.0-CURRENT #2 > r326363+fcb3a5a8a12d(master): Wed Nov 29 11:37:17 UTC 2017 > root@wintermute:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > # dmesg > > https://gist.github.com/dch/68dd6f8d44dd76c558908e71dc3e1f87#file-dmesg-log > + other logs in same gist > > Suggestions how to get from X to debugger would help, as would setting > up serial console over ipmi - this is a supermicro motherboard. > > A+ > Dave > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Mon Dec 4 03:43:50 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A86D0DEBE7D for ; Mon, 4 Dec 2017 03:43:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D0E77682F for ; Mon, 4 Dec 2017 03:43:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 06996CC3; Sun, 3 Dec 2017 21:43:49 -0600 (CST) Date: Sun, 3 Dec 2017 21:43:47 -0600 From: Mark Linimon To: Milan Obuch Cc: Daniel Braniss , Warner Losh , freebsd-current@freebsd.org Subject: Re: orangepi [was: what happened to src/sys/boot?] Message-ID: <20171204034347.GA6310@lonesome.com> References: <39F80CE7-BECF-4D4F-ACEB-5B6C52FC241B@cs.huji.ac.il> <42427F81-E6FE-43CE-87D5-2560CC66F866@cs.huji.ac.il> <20171203202225.GB4725@lonesome.com> <20171203213309.77b3aa40@zeta.dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171203213309.77b3aa40@zeta.dino.sk> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 03:43:50 -0000 On Sun, Dec 03, 2017 at 09:33:09PM +0100, Milan Obuch wrote: > Please see thread on freebsd-arm mailing list starting with my message > titled 'Allwinner H3/H2+ dts question - regression?' Ah, ok. My brain did not associate "H3/H2+" with "Orange Pi" so I simply skipped it. In any case I can now get the Orange Pi + 2E to boot multiuser and have it work the same as the Orange Pi One, with the following hack. Actually fixing the problem is "left as an exercise for the reader" :-) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224070 mcl From owner-freebsd-current@freebsd.org Mon Dec 4 06:37:54 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D2F9DF030A for ; Mon, 4 Dec 2017 06:37:54 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 15FE07AE53 for ; Mon, 4 Dec 2017 06:37:54 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x231.google.com with SMTP id p139so10157266itb.1 for ; Sun, 03 Dec 2017 22:37:54 -0800 (PST) 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=hkJIZssEPy1EOkABtiQf3NK5b8PG8wlppP5dg3Fiib8=; b=N4f2fIS3/AYfiftefrjD8IBvVLwZjCJHfBlPfzk6SYtgoOlB/pWIBO88G3vOLNZ2g3 rqSl/ji6lKp3Qn+tCFaN4gE9VxVSfrEp6vaFQU/Uln+OB1jplgIuByVkIRMpg/2MLozT 9sO+7ZWX+C45/Ic/gTSXbdPr2UfSXwwIy3mpqWDIHxcO8COfgY9BlxkwO8GtK0OPM3FC VnZwAwDXsj0OMqNnzDqG6kGqrbNelBKqsmd3S0HunFnrpC79lunCAitBr0bkaYl7wzTo hU1GouzVpQiLtzO1TwSgBxtCdPF0LY6V6PT724f5RXRajsOlhE6OISfbbcRwco1dqLMV CV8Q== 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=hkJIZssEPy1EOkABtiQf3NK5b8PG8wlppP5dg3Fiib8=; b=rr/0y6/QWtGaCDTmlAP6tEVc54Arqy0Yn7UVjKC8kJGELXJzsFGwHoSC3b2nRlCKim rNExIFk/SjOA96yCxf6/eR3ps20tMksG0yDHeLAFdEGnu45rgSFT3o7tLnR3cctvZk7m jGBalrOZMwS+11qp+9H71oD8bbr2Z9XpVLOopq5o1ciLtYLtnw5vubJLvoXXlHrDdgT+ R0uqOiYuYBfKnFxgyTBpXu+D0UO8831gP1ivaTZFMPsEKo5qZNKoT7pL4dJQKy7Q5Eue 8AWpHnV8aWAG+aiKuoaQErQLfW704oajYMUEQrm+SWqE5hlSygCw2Us1yAeJ+GP6iKya vR0g== X-Gm-Message-State: AKGB3mKcA8MRvhwxYvOVxQrNoMR5OaDA+UMxxJWeT9qNVeUJZ3KUbkGm YmccYiP2QEy2EeyBY5w58XEyzsvUO9lzzvLbVYBPqA== X-Google-Smtp-Source: AGs4zMZ439E2qFgmL9IfX7wQD7q5wW6WONaRPUhQ43A9SWGondk7NEHl/GtxfNuJFX2gV94L/7Idyx6FwbqEnjA6EFM= X-Received: by 10.36.167.77 with SMTP id s13mr3381911iti.51.1512369473165; Sun, 03 Dec 2017 22:37:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.11.31 with HTTP; Sun, 3 Dec 2017 22:37:52 -0800 (PST) From: blubee blubeeme Date: Mon, 4 Dec 2017 14:37:52 +0800 Message-ID: Subject: xdg-desktop-menu-dummy.menu causes Firefox to crash To: FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 06:37:54 -0000 This issue started happening recently I think after updating to the latest version of Firefox. Every so often I'll come back to my machine and Firefox has died, then in one of my terminals I'll see this message: kbuildsycoca4 running... kbuildsycoca4(51442) VFolderMenu::loadDoc: Parse error in "/usr/home/blubee/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" When I look at the file in question it's just an empty file. I tried grepping around finding that xdg-desktop-menu file but nothing came up. Anyone have any idea what it's about or why is it crashing Firefox? Firefox version: 57.0 (64-bit) from ports tree. From owner-freebsd-current@freebsd.org Mon Dec 4 09:26:32 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BCF4DF5758 for ; Mon, 4 Dec 2017 09:26:32 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6BBA87F2D2 for ; Mon, 4 Dec 2017 09:26:31 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id BE27720AE6; Mon, 4 Dec 2017 04:26:29 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Mon, 04 Dec 2017 04:26:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; 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=fm1; bh=64afrxuiHpftn87G6 OBUXeXPzPH5Axd78TOw7frj7VE=; b=pM3FcGnhwE31mug1v+F/ltm+bWSPfkOdt IW98NpxH3e4KlngLBLYsLDK50P++d/29z70m2BCKuBdddVQQtdlPsfi8i4IRpmgz qHVScgSv+rDa3nTMY2WNfQZ4bsdtFc2CPhPT77rfXMDamf8aDk3sl1RG5W8r7LDt 1RGygSfKDdWTsPZwmOfF96nsw9wRuseMluBH54Sx1eTaslTFAvSILeV6bbpd+sCn tKj3aZrLw1SyGh7HKenmX2M6uaM68I6WQaNeGd/BcczXzQsZlwBsAaIJx6tAETxs 2z5e/LtZxi1VFkPKNnxg0msDbUOkD53gdb5hYy8FFNLovp3S7RQ1g== 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=fm1; bh=64afrx uiHpftn87G6OBUXeXPzPH5Axd78TOw7frj7VE=; b=RItyUuCj8o0OCTIwqyLfNS nZialb2ixND3/0/vjVeKZku+EtYhCQ4i3iVs3DcRsu00kdX2TXTkCVX4LLE+qLaK Di6wrMvmPA8IIAdaU1PqQihDRAc/sFFIe+GATXnNgLhbJirGjvydGo1dVp2JdzN3 92gIiJe8SxEoTY1/V/K13YJzCLjQcrebslxosTgP4dAGN76RRYRh1jWejNOJfjYE iKo1fjqTPhzeM0b5Oah+J+zxadPo/qf965pzxhUEebcEqbzO42POi/yuRrbJ9K0m P/4bDfC0z9JXgSCknz5zem37BxnsJw/ldB3yEQOTEId4uvJGcdHLTROPmWqdGN9A == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 9DD9840E7; Mon, 4 Dec 2017 04:26:29 -0500 (EST) Message-Id: <1512379589.2381426.1193052584.122242EB@webmail.messagingengine.com> From: Dave Cottlehuber To: Ryan Stone Cc: FreeBSD Current MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-1b87d328 Subject: [SOLVED] Re: panic: Lock PFil shared rmlock not read locked @ /usr/src/sys/net/pfil.c:116 prior to r326363 References: <1512344998.2249959.1192664520.6B278E9D@webmail.messagingengine.com> In-Reply-To: Date: Mon, 04 Dec 2017 10:26:29 +0100 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 09:26:32 -0000 On Mon, 4 Dec 2017, at 01:24, Ryan Stone wrote: > Please update to r326376 or later. That will likely fix you issue. > Indeed it does -- thanks! A+ Dave From owner-freebsd-current@freebsd.org Mon Dec 4 11:26:51 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47EA3DF913F; Mon, 4 Dec 2017 11:26:51 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fry.fubar.geek.nz (fry.fubar.geek.nz [139.59.165.16]) by mx1.freebsd.org (Postfix) with ESMTP id 18AFD63DCF; Mon, 4 Dec 2017 11:26:50 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from [10.0.0.69] (host81-149-102-120.in-addr.btopenworld.com [81.149.102.120]) by fry.fubar.geek.nz (Postfix) with ESMTPSA id 850424EBD3; Mon, 4 Dec 2017 11:26:44 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Booting UEFI ZFS is broken on arm64 From: Andrew Turner In-Reply-To: <20171130002135.q7p27hh6qkog4slr@mutt-hbsd> Date: Mon, 4 Dec 2017 11:26:42 +0000 Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <87F57386-EE82-4DA4-AFB4-9D90ED1FA1BC@fubar.geek.nz> References: <20171130002135.q7p27hh6qkog4slr@mutt-hbsd> To: Shawn Webb X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 11:26:51 -0000 > On 30 Nov 2017, at 00:21, Shawn Webb wrote: > > It appears that in the latest FreeBSD 12-CURRENT/arm64 snapshot, > booting UEFI GPT ZFS on my OverDrive 1000 is broken. It boots up to > this line: > > Using DTB provided by EFI at 0x801fe00000. > > Then all output stops. I'm in the process of building a custom install > ISO that has DEBUG turned on in the fdt code. I hope to report back > soon-ish, unless anyone else has any ideas as to what could be wrong. This should be fixed in r326525. Andrew From owner-freebsd-current@freebsd.org Mon Dec 4 17:06:52 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A203DE5DFC7 for ; Mon, 4 Dec 2017 17:06:52 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8B01F705EF for ; Mon, 4 Dec 2017 17:06:52 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 8716DE5DFC6; Mon, 4 Dec 2017 17:06:52 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86BDDE5DFC5 for ; Mon, 4 Dec 2017 17:06:52 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3E66B705EE for ; Mon, 4 Dec 2017 17:06:51 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from e-bsd.cs.huji.ac.il ([132.65.80.241] helo=outmail.cs.huji.ac.il ident=exim) by kabab.cs.huji.ac.il with esmtp id 1eLuCc-000Meh-Ik for current@freebsd.org; Mon, 04 Dec 2017 19:06:46 +0200 Received: from [132.65.179.42] (helo=imac.bk.cs.huji.ac.il) by outmail.cs.huji.ac.il with esmtpsa id 1eLuCc-0003D6-Gp for current@freebsd.org; Mon, 04 Dec 2017 19:06:46 +0200 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: how to produce dtb from dts? Message-Id: Date: Mon, 4 Dec 2017 19:06:46 +0200 To: FreeBSD Current X-Mailer: Apple Mail (2.3445.4.7) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 17:06:52 -0000 Hi, what=E2=80=99s the current official procedure to compile/convert a dts = file, I=E2=80=99m my case sun8i-h3-nanopi-neo.dts to its dtb? thanks, danny From owner-freebsd-current@freebsd.org Mon Dec 4 17:34:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1E88E5F081 for ; Mon, 4 Dec 2017 17:34:04 +0000 (UTC) (envelope-from manu@bidouilliste.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 C1CC371E96 for ; Mon, 4 Dec 2017 17:34:04 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: by mailman.ysv.freebsd.org (Postfix) id BE22AE5F080; Mon, 4 Dec 2017 17:34:04 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD815E5F07F for ; Mon, 4 Dec 2017 17:34:04 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AA9E71E87 for ; Mon, 4 Dec 2017 17:34:03 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 93089396; Mon, 4 Dec 2017 18:33:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=B4EHY0iHh9nS3W41e6WnFEmV0QI=; b=WmUW1p/Q6gPA+3jFmJ93nVEdJRth k7FZlbjWnCPhlaW4IXecgZy2MAr5Ml86wcq4cFMJ5Yay4K1lQi0PiCaHZB8UFjOD eWHe534/X271JG1tYeHwZBYJqR4FuR5312Ce+R40cY15Gq2raoDQ8fEHnDIoKnnP r+QPoxjDmsSfytM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=d+7DjyC+4BgxAScD05dXEI2Ym8WkG7X/SFKuFLlEWDh9h9wR6R9fcB7n cSUKwLSaSElSdQirJU2lXxBPuME9fSrlkZAeM11xRI0J/93qOn3UV28YgdJ1tf6K 2SZLSKeIZyRzmHS1Fx6RxI6Qox4e2O641QpX1dlnmWRCZGZT9Go= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 4ca65c2e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 4 Dec 2017 18:33:54 +0100 (CET) Date: Mon, 4 Dec 2017 18:33:51 +0100 From: Emmanuel Vadot To: Daniel Braniss Cc: FreeBSD Current Subject: Re: how to produce dtb from dts? Message-Id: <20171204183351.8f42a20d8a0798c3871139c3@bidouilliste.com> In-Reply-To: References: X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 17:34:05 -0000 On Mon, 4 Dec 2017 19:06:46 +0200 Daniel Braniss wrote: > Hi, > what?s the current official procedure to compile/convert a dts file, I?m = my case sun8i-h3-nanopi-neo.dts > to its dtb? >=20 > thanks, > danny You can use sys/tools/fdt/make_dtb.sh This is what the build system uses. --=20 Emmanuel Vadot From owner-freebsd-current@freebsd.org Mon Dec 4 18:33:13 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDFAAE67B35 for ; Mon, 4 Dec 2017 18:33:13 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id C6FC8743C3 for ; Mon, 4 Dec 2017 18:33:13 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C643DE67B34; Mon, 4 Dec 2017 18:33:13 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5DCDE67B33 for ; Mon, 4 Dec 2017 18:33:13 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A9DA7743C2 for ; Mon, 4 Dec 2017 18:33:13 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 75ee5457-d921-11e7-97f4-9d8903e843e3 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 75ee5457-d921-11e7-97f4-9d8903e843e3; Mon, 04 Dec 2017 18:32:19 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id vB4IVx7f001581; Mon, 4 Dec 2017 11:32:00 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1512412319.27882.14.camel@freebsd.org> Subject: Re: how to produce dtb from dts? From: Ian Lepore To: Daniel Braniss , FreeBSD Current Date: Mon, 04 Dec 2017 11:31:59 -0700 In-Reply-To: References: Content-Type: text/plain; charset="iso-8859-7" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 18:33:14 -0000 On Mon, 2017-12-04 at 19:06 +0200, Daniel Braniss wrote: > Hi, > whats the current official procedure to compile/convert a dts file, > Im my case sun8i-h3-nanopi-neo.dts > to its dtb? > > thanks, > danny > make builddtb FDT_DTS_FILE=DTBOUTPUTPATH= -- Ian From owner-freebsd-current@freebsd.org Mon Dec 4 22:32:34 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6174BE6CCC1 for ; Mon, 4 Dec 2017 22:32:34 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F7437C844 for ; Mon, 4 Dec 2017 22:32:34 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x236.google.com with SMTP id u42so24786921qte.7 for ; Mon, 04 Dec 2017 14:32:34 -0800 (PST) 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=1qEYNBMd7Abv7CRnOpwoSQO8BqnNQqIZcJRnHYZwo88=; b=Cxu2ANUHDtmyR1mxPScV3XKTfbxYzYHzLq9V/kZRj64bm3l0eIiuJmp5ZksdbKOjIo 2kpSPgGDndxRAKY9JODPnjNmIRlJJWYe6wK1V6XOloRuaYXTYcN/yTVVw5/aeccBOVOe gqGEd6+bd9pr3Xibz5qCgwnB5v73WUiMYPbFnZmoXk5+UF3y1Db9J20PxowPAS8fVslH qGxdDPyznQ73FUlSKHMAjr7fiKaHIVj9rMmAKHo9+otONW8u4bfI+ygWrajkoxGwf5GE PdWuqeI1bTApN15TR5uRrB5RxwG5GbEU7qmcQD5QIV+iD+t3y3wg2+Qyj6CWx9DEF09v wryg== 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=1qEYNBMd7Abv7CRnOpwoSQO8BqnNQqIZcJRnHYZwo88=; b=iLWzP4E+4A90Kj61TLduQmaafXW0eEeXqTGizRAVlhubTZpRUn2Lz1W4rGTnjI5N33 8Ox2pFwWix5otPJFxLtvcU8TPdZasf9G0ADSmzeJNH7pACo49H5eSofpdE4NtEB1OOSU FJTNCAI0/g8UYj6pE/IJ2pKLT4H9P5WpiDFNbU1Sr/d8BHaVQiJb6VoVoyJJJJhpgy3z DSYH+ZtgKwsxV1dgHCs2c5lXz35ckuQS0PKsZSELhfsgwoNkzLQUUU5EEiFDm3mls5uK AsFq/4zFdYMSMnevbhvGIqxQlTqvTkbPNUMhicr7Gfq62UjknrM3pxKdm3IwwofjLdOr p52w== X-Gm-Message-State: AKGB3mLZ4zLVQP5gGbMJXrgnFb/jFf+T6PgnMahTOXKneefANqEVbjQz kATwI76p11/2GwRveNBVTbPV52znMDlrarBcA39WfA== X-Google-Smtp-Source: AGs4zMaQAuTQmGmgZSEa9Hjz5xCnttfNPOuv/1UUvxJ8/Pv7I9us8J2DYPbFTmaNUC6zvAvzPEJ3PKZlVqMpPRdWiro= X-Received: by 10.200.45.89 with SMTP id o25mr237680qta.227.1512426752884; Mon, 04 Dec 2017 14:32:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.39.211 with HTTP; Mon, 4 Dec 2017 14:32:32 -0800 (PST) From: Ryan Stone Date: Mon, 4 Dec 2017 17:32:32 -0500 Message-ID: Subject: Build failure in stand To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 22:32:34 -0000 I'm seeing the following build failure when doing a buildworld of head: In file included from /repos/users/rstone/bsd-worktree/route-change/stand/ficl/i386/sysdep.c:18: /repos/users/rstone/bsd-worktree/route-change/stand/libsa/machine/cpufunc.h:491:13: error: shift count >= width of type [-Werror,-Wshift-count-overflow] high = val >> 32; ^ ~~ 1 error generated. My make.conf looks like: PERL_VERSION=5.14.2 DEBUG_FLAGS=-g CFLAGS+=-fno-omit-frame-pointer #BTX_SERIAL=yes #BOOT_PXELDR_ALWAYS_SERIAL=yes # src/sys/boot/i386/libi386/Makefile (loader) #BOOT_COMCONSOLE_SPEED=115200 ## src/sys/boot/i386/libi386/comconsole.c (loader) COMSPEED=115200 # src/sys/dev/sio/sioreg.h (kernel) #CONSPEED=115200 WITHOUT_DEBUG_FILES=yes and my src.conf is: WITH_TESTS=yes WITHOUT_DEBUG_FLAGS=yes WITHOUT_INFO=yes From owner-freebsd-current@freebsd.org Mon Dec 4 23:00:00 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 193BEE6D6E1 for ; Mon, 4 Dec 2017 23:00:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C40847D42A for ; Mon, 4 Dec 2017 22:59:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x244.google.com with SMTP id d137so10755955itc.2 for ; Mon, 04 Dec 2017 14:59:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=G6tLPzE9RqbYEKbx9YF+q9xm/Wa3CO1UXo0oT8NVH9A=; b=nYgCrgc3GUzjG3V+FzQozNOiH5u6Wn5QJYXfY0aw5KagX5HrcQrbeLnd24yabwVZNG keCn6/UqCZezrEm2j8TXb4Ei/jRmUcLeCqoigU8RuxoZaF0al0hrRU9rG0HX6ZAxCu8j AChoituwmMD3qlNvDgm0NQqbYyyhzUMbrUIIzBYNpw4mTOIpz0tMxM98nd/rUJ7qq/FG raMxW+SNpYow1E1seDCjAYGbglsVoJYnwcGNn2IFJpTNK60et4yxvuoqqJxONKB4qbti bi6ImjpJ70aYjpQiruqNYOwJa2T/IUk1L4VUlVRVjEJeS0DDJv8aej6+aWe3M7nzbVbm yUMw== 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=G6tLPzE9RqbYEKbx9YF+q9xm/Wa3CO1UXo0oT8NVH9A=; b=AGLLkRe8TNR9vuwT9F+cSK1eyOSA/G42EbUVpe2fjapED9z1ZxqiuLF4+1FHMNyBZY sFXeBThPFOx8SFHzKAFhqSkGYY8E5s9Eq8pubGfj1Ux/JbzY05tv9zHJYr9xSXspNmLr pAjeJpeGXGoj7gSl+31GRwmLhn3Gft8WLokkZ1NFvaYDjQXOU2PGf8Y8rKLyhlCJ23nK Rk9QQLaSHvu7vEbz7ne0nNEFF0lVWcPGdv1qe3gRUl/8jfymZJmCrSBKxUfvTDZ97Ldw ub0Fl3NWsS3YqDB9PUnr7TR41n2tvuYf2NXxmscSVzZiOjOp0VpeKKq0rTLnV5rb6Uql kiLQ== X-Gm-Message-State: AJaThX6UYHNjRvpaXbCVnst/LeAUgdqRa6tjGRwZzQ0AIRn9Fo3EZ4WG U07UAXRHr0to/azoF3nEoOGHMyxTQIQ7ymowvBqeLw== X-Google-Smtp-Source: AGs4zMaWCT5gamIqPFa8NhvyE85roqlOJNWAU4nRvHpw7xSqY9VOLnkQHSLctF+O8zcX6avzoEXIiAGO8iTd1O5dcV0= X-Received: by 10.36.164.13 with SMTP id z13mr16268536ite.115.1512428399060; Mon, 04 Dec 2017 14:59:59 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 4 Dec 2017 14:59:58 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Mon, 4 Dec 2017 15:59:58 -0700 X-Google-Sender-Auth: L4YIFTGnUtVlg-1Fz2WwW77Q5J0 Message-ID: Subject: Re: Build failure in stand To: Ryan Stone Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 23:00:00 -0000 Please remove the DEBUG_FLAGS and try again. Trying to see if that's the culprit. It works for me with the default build. Warner On Mon, Dec 4, 2017 at 3:32 PM, Ryan Stone wrote: > I'm seeing the following build failure when doing a buildworld of head: > > In file included from > /repos/users/rstone/bsd-worktree/route-change/stand/ficl/i386/sysdep.c:18: > /repos/users/rstone/bsd-worktree/route-change/stand/ > libsa/machine/cpufunc.h:491:13: > error: shift count >= width of type [-Werror,-Wshift-count-overflow] > high = val >> 32; > ^ ~~ > 1 error generated. > > > My make.conf looks like: > > PERL_VERSION=5.14.2 > > DEBUG_FLAGS=-g > CFLAGS+=-fno-omit-frame-pointer > > #BTX_SERIAL=yes > #BOOT_PXELDR_ALWAYS_SERIAL=yes > # src/sys/boot/i386/libi386/Makefile (loader) > #BOOT_COMCONSOLE_SPEED=115200 > ## src/sys/boot/i386/libi386/comconsole.c (loader) > COMSPEED=115200 > # src/sys/dev/sio/sioreg.h (kernel) > #CONSPEED=115200 > > WITHOUT_DEBUG_FILES=yes > > and my src.conf is: > > WITH_TESTS=yes > WITHOUT_DEBUG_FLAGS=yes > WITHOUT_INFO=yes > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Mon Dec 4 23:20:55 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFCEFE6DFF3 for ; Mon, 4 Dec 2017 23:20:55 +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 G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 944EB7DF18 for ; Mon, 4 Dec 2017 23:20:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x242.google.com with SMTP id t1so17038901ite.5 for ; Mon, 04 Dec 2017 15:20:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Oi+gr8trj9ZMhO5+mE7PX5/4JpIlbBq/6BJpnigeNuQ=; b=w2fLZLrY8qyU2CJ0PBLwKmzSiByUv6EmRlDv6aa8mFExWChg2FnhreR15xw6fCQ5Jz Y4Le7fUPrbewpa+TObFZJvjtiXh64h4JlyvRDxp3SspdUMcbm4pD3XkEOLijZwYLNit3 BNz5jsuvMW+/SnVfGbC5Xq/1IzT5NdvSJEcRHuKDjJKJbvL05szPcHztQvKAsOo2qq0Y Y6mvGHroyYsaSwUo2WQ7V8JLLOBj1KWxDgxb9+oO/+cFWRsSfvQDKWkklQ2j1Qb/j4hA /V+aA/CTYKvjadZfV+QgXvL8iCv2+p8fsum72twu/uoQ4ir2l455LLR3xjNCqTCN7uSp l+wA== 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=Oi+gr8trj9ZMhO5+mE7PX5/4JpIlbBq/6BJpnigeNuQ=; b=Dl0ECHAJBhxD8vEzLz/bL1Ij/wNP84Oxka2Px35SV26cRglx2r8NeymMXM4JVrRbKp 3/aloDhPRGNb4AcsYD9gRHTC3lWW/tGVrTWXeWpoHwac0gOWoxLZ5wPmTMel4QHNQVx3 +tDlzG/X+RnV5Oet/Tl7z7kpUfkbLWq1DqoAatgWxSfFL3DjcyB/vP4o+P382ZV+yKTz hV3p/zvNQ99NvIYShjqH3ST9GjiEbcx9N+pEpIzt/KGW2fUnjH+muB9UcCGv6lYojnTJ ngeyI96fE+vwvUvhMD1Xwvxv5Jq/gk/bxytSnWb/20wZWiSkIm53FefaMrwhuKBd6xmK 1vAA== X-Gm-Message-State: AJaThX6ZSh5HqLxfo4uCR9o+RV6GNhO/+SDtr3uG/WfuFbUADkPaS4vy zjCvzsN+o2jikprcAerWmuu0OJpZI3XbrfZhcytqwQ== X-Google-Smtp-Source: AGs4zMaQb3CtVY+j2SCyE/FsRFZ4K74AugOkoT9cHHQjnv36ftLjiKiC0+/8B6kkNwm/bGiLrET2cj7YproJrluLs94= X-Received: by 10.107.81.24 with SMTP id f24mr25542045iob.63.1512429654746; Mon, 04 Dec 2017 15:20:54 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 4 Dec 2017 15:20:54 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Mon, 4 Dec 2017 16:20:54 -0700 X-Google-Sender-Auth: vWLUx37d9rG3aWLKlcGiiAt1JjA Message-ID: Subject: Re: Build failure in stand To: Ryan Stone Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 23:20:55 -0000 Also, can you make the full logs available? I can't recreate this with or without DEBUG_FLAGS or CFLAGS setting in my make.conf file. Warner On Mon, Dec 4, 2017 at 3:59 PM, Warner Losh wrote: > Please remove the DEBUG_FLAGS and try again. Trying to see if that's the > culprit. It works for me with the default build. > > Warner > > On Mon, Dec 4, 2017 at 3:32 PM, Ryan Stone wrote: > >> I'm seeing the following build failure when doing a buildworld of head: >> >> In file included from >> /repos/users/rstone/bsd-worktree/route-change/stand/ficl/ >> i386/sysdep.c:18: >> /repos/users/rstone/bsd-worktree/route-change/stand/libsa/ >> machine/cpufunc.h:491:13: >> error: shift count >= width of type [-Werror,-Wshift-count-overflow] >> high = val >> 32; >> ^ ~~ >> 1 error generated. >> >> >> My make.conf looks like: >> >> PERL_VERSION=5.14.2 >> >> DEBUG_FLAGS=-g >> CFLAGS+=-fno-omit-frame-pointer >> >> #BTX_SERIAL=yes >> #BOOT_PXELDR_ALWAYS_SERIAL=yes >> # src/sys/boot/i386/libi386/Makefile (loader) >> #BOOT_COMCONSOLE_SPEED=115200 >> ## src/sys/boot/i386/libi386/comconsole.c (loader) >> COMSPEED=115200 >> # src/sys/dev/sio/sioreg.h (kernel) >> #CONSPEED=115200 >> >> WITHOUT_DEBUG_FILES=yes >> >> and my src.conf is: >> >> WITH_TESTS=yes >> WITHOUT_DEBUG_FLAGS=yes >> WITHOUT_INFO=yes >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> > > From owner-freebsd-current@freebsd.org Mon Dec 4 23:27:59 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C084E6E1FF for ; Mon, 4 Dec 2017 23:27:59 +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 G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DD127E3AF for ; Mon, 4 Dec 2017 23:27:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x242.google.com with SMTP id d16so10923271itj.1 for ; Mon, 04 Dec 2017 15:27:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=emdrYHtXVoj/uzCU7ICZOvoNNYu5dOX9NlqCSHQ8l04=; b=A+Isg9P8dbWF84Pc1rBa81SbrMRZxV9pYx6dPw4VNfiCTznlDaZI6UY8PON79PmnZf RJjJq8shh+FQrLnW/yiN5jMUhlB1u+xOFDnaMwAE8+E5WMTozP3q7lQ2dyzzaSckODj0 WAnWNeD71t0m7vheQiC0NwKDH0WbDH0kPdL/VrsQgNDyL+AZ8K7Gy8nhA/6mx3hXl2tx MyIs7xZQeO+Y2vJpkv2LKGI7vO13zb3YqbHwMsJuwfGmv1X/N7VlagD7l6gXtTBCucaL kjqjhf0yIKHmGTXngW67ump6RtM85ehww7sb1cULaIXQAG+fsWhcNPCvy1EZpYqbJL9u FuAA== 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=emdrYHtXVoj/uzCU7ICZOvoNNYu5dOX9NlqCSHQ8l04=; b=PJHRtsi6w58XAo/l7f0LGJUt5ptXP5Z7F9Uajv+VNj7hwX/pPMVpbVYPCv81mK77pd pi/hvUVuHoNhvD9PudHa75HoB1oT25N4Pa57xh8yWRcZTnpRFakSs/t2ojXXQ7VWW33M B0hJWrynMmBYB1g57j53suI8AynUjq8dux61xgv1zr5CaO+8xfFSKLHt9YYXLW45Wb4h 52dwLuQaxIg76/HwERjP5DevMN1ZMRrXYDcKKZQ1nHb91a3p3JTslNGyERgJ19xQgLjW me08Ox/snnOmNFNSDT1ydgEFWG1xP8mMnonmofIXo22fx+EBNXa5mmQECawKtVnwuqDw 2UJw== X-Gm-Message-State: AJaThX4uVNFwM9KR1XgxylVJhwR2+CJ5lSWT5Djwl735r8gMCidYWwfW GgBN1QIAiTOGa6IlnitectgVd8YjTdqVdBKMZXuqRg== X-Google-Smtp-Source: AGs4zMYLxlMmndOqld4THRi9UNw8vCcnI17vNYvdIpBpn2pgYo+zwhOfYeXlqi4N8SA2igVf7oPnhOJJTh+GpaycZQU= X-Received: by 10.107.81.24 with SMTP id f24mr25564812iob.63.1512430078348; Mon, 04 Dec 2017 15:27:58 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 4 Dec 2017 15:27:57 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Mon, 4 Dec 2017 16:27:57 -0700 X-Google-Sender-Auth: oJzGynNT0hWv9ABthIVPNdwbVxU Message-ID: Subject: Re: Build failure in stand To: Ryan Stone Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 04 Dec 2017 23:27:59 -0000 Oh, and one more btw, can you cd stand; cd ` make -V .OBJDIR ` ; find . -name machine | xargs ls -l The only way I can see this happening is if we're doing a 32-bit build, but pulling in the amd64 header files for some bogus reason... Finally, what's the host OS? Warner On Mon, Dec 4, 2017 at 4:20 PM, Warner Losh wrote: > Also, can you make the full logs available? I can't recreate this with or > without DEBUG_FLAGS or CFLAGS setting in my make.conf file. > > Warner > > On Mon, Dec 4, 2017 at 3:59 PM, Warner Losh wrote: > >> Please remove the DEBUG_FLAGS and try again. Trying to see if that's the >> culprit. It works for me with the default build. >> >> Warner >> >> On Mon, Dec 4, 2017 at 3:32 PM, Ryan Stone wrote: >> >>> I'm seeing the following build failure when doing a buildworld of head: >>> >>> In file included from >>> /repos/users/rstone/bsd-worktree/route-change/stand/ficl/i38 >>> 6/sysdep.c:18: >>> /repos/users/rstone/bsd-worktree/route-change/stand/libsa/ma >>> chine/cpufunc.h:491:13: >>> error: shift count >= width of type [-Werror,-Wshift-count-overflow] >>> high = val >> 32; >>> ^ ~~ >>> 1 error generated. >>> >>> >>> My make.conf looks like: >>> >>> PERL_VERSION=5.14.2 >>> >>> DEBUG_FLAGS=-g >>> CFLAGS+=-fno-omit-frame-pointer >>> >>> #BTX_SERIAL=yes >>> #BOOT_PXELDR_ALWAYS_SERIAL=yes >>> # src/sys/boot/i386/libi386/Makefile (loader) >>> #BOOT_COMCONSOLE_SPEED=115200 >>> ## src/sys/boot/i386/libi386/comconsole.c (loader) >>> COMSPEED=115200 >>> # src/sys/dev/sio/sioreg.h (kernel) >>> #CONSPEED=115200 >>> >>> WITHOUT_DEBUG_FILES=yes >>> >>> and my src.conf is: >>> >>> WITH_TESTS=yes >>> WITHOUT_DEBUG_FLAGS=yes >>> WITHOUT_INFO=yes >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>> reebsd.org" >>> >> >> > From owner-freebsd-current@freebsd.org Tue Dec 5 07:22:15 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E85CBDF96F2 for ; Tue, 5 Dec 2017 07:22:15 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D52096EA74 for ; Tue, 5 Dec 2017 07:22:15 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id D468CDF96F1; Tue, 5 Dec 2017 07:22:15 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D40A9DF96F0 for ; Tue, 5 Dec 2017 07:22:15 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 907406EA72; Tue, 5 Dec 2017 07:22:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1eM7YH-0001P2-D5; Tue, 05 Dec 2017 09:22:01 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: how to produce dtb from dts? From: Daniel Braniss In-Reply-To: <1512412319.27882.14.camel@freebsd.org> Date: Tue, 5 Dec 2017 09:22:00 +0200 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <2E7EE01D-A343-4F21-BF43-A3BE66053DC8@cs.huji.ac.il> References: <1512412319.27882.14.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3445.4.7) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 07:22:16 -0000 > On 4 Dec 2017, at 20:31, Ian Lepore wrote: >=20 > On Mon, 2017-12-04 at 19:06 +0200, Daniel Braniss wrote: >> Hi, >> what=E2=80=99s the current official procedure to compile/convert a = dts file, >> I=E2=80=99m my case sun8i-h3-nanopi-neo.dts >> to its dtb? >>=20 >> thanks, >> danny >>=20 >=20 > make builddtb FDT_DTS_FILE=3D DTBOUTPUTPATH=3D >=20 > -- Ian thanks, will try ASAP. danny From owner-freebsd-current@freebsd.org Tue Dec 5 17:03:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87D30E7104B for ; Tue, 5 Dec 2017 17:03:16 +0000 (UTC) (envelope-from yuripv@gmx.com) 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 E7C9A3D4C; Tue, 5 Dec 2017 17:03:15 +0000 (UTC) (envelope-from yuripv@gmx.com) Received: from thor.xvoid.org ([85.173.23.68]) by mail.gmx.com (mrgmx103 [212.227.17.174]) with ESMTPSA (Nemesis) id 0Ln8gj-1f165R0D9x-00hPDI; Tue, 05 Dec 2017 18:03:08 +0100 To: freebsd-current , Bryan Drewery From: Yuri Pankov Subject: buildkernel broken after r326553 Message-ID: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> Date: Tue, 5 Dec 2017 20:03:07 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.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:K0:+WkF3uv/8HhvWFPZPaHbsaJg7qsSHaRiEPRwLuT0IpxZDKDWT27 wpxpJG2VOIItwXPj4ZiLKsDAWJV4pJOKfQY5JiBjt6Sek7jH9uMBL8SbjONsnh/2dD0yoNo EM1wWgMpsKQIdTfeYOIWHa4+dWExCuBiPp6/NnEeY+wdwGpkw+yjTJxSDM1/w/8ynrcWfa7 TQvGZc8b7oNHcv5s8iGiw== X-UI-Out-Filterresults: notjunk:1;V01:K0:dRJXVyRmYTU=:9W41wOlyytprLuH+jaM/lS ibZSctnangZJjaeiF4FaxeT5yoJgxP0y5rGUQNJjGTWKrHaw8+tSrtH7ShZnGnx17TYWmgqwY 3slZcbmD0DAXRdBKRGibTByss6+ejZOZFQEZIGi0jA6UHOu7FNWS6zdM/J2vkeMQpUkP2s5Uc /y0dw0dh3851CLZsF6ybwv9ng6E0SUPHlQ4S/I+68Wh9vitJGP/Ktz+bMcGJaY4NazqYMWqoR f/+CzKiDRpsEeU4PfgaxglsFCs7rVJVUBwZFMJFv930MNhWVjni8JP5u/55JHRXitJev0rqAC h8TY6Eo5YwcIF8Shw0fQzr4/fBKnhNR4QqI2kfCFd0N5inf/SGBFv4INXbGjMUxcOHg9Mi2cw CwMnp/eTUraDk25SmoXnHN5SamSZ90Q3vewWxLoOswQVObhbhs2YWOYTzJ0vAesjBI8bn7nMP X3rSuseGgTh1YGrzDYpGW0T+uNShv0ONc1k3NI/zN1+47c0IBI7WlB4djksrMHagq6hVe38jq uASmSLbStvZP57ku6pv8XVWH4AXBmqSMnb6l8iBUoKy3Rr2kWYi86MA2iBHFL6nWQyFg58tms Z/Gro2VewRsSgmDGT8Sq4xLej6WVufsBSIQK+h4vf6KSMeHLAxf+MaJz2Jj7R/79J1yGP6sIj yAHza/Ds1XGJhORDAnJnnu35WZeeFVzjRniDNG+TtGV8nZmpM5HVEMuJFuY05FBZxlGsZ+WTP ja91NHDzkd0x/JDfBvb5r4iLWrMAyN6xbZTfkAtqiXxsTY+5yocJdY3t8M/jQFaC4aliAvghi afl37b5vGl5tNJJaBmG9C/Sb1MNuPrJYSEQfQBB0Sa+LJQVtU8= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 17:03:16 -0000 Hi, Looks like one of the commits by Bryan (r326549-r326553) has broken the kernel build for me (using -j32, but serial build did fail as well) -- checking out r326547 make it work again. I can't pinpoint the exact error in the build log, as it seems to be some make weirdness, so here's a guess, please let me know if you need full build log: --- all_subdir_vmm --- make[4]: Graph cycles through `vmx_assym.h' make[4]: Graph cycles through `vmx_genassym.o' make[4]: Graph cycles through `svm_assym.h' make[4]: Graph cycles through `svm_genassym.o' `svm_genassym.c' is up to date. `vmx_genassym.c' is up to date. `vmm.c' is up to date. `vmm_dev.c' is up to date. `vmm_host.c' is up to date. `vmm_instruction_emul.c' is up to date. `vmm_ioport.c' is up to date. `vmm_lapic.c' is up to date. `vmm_mem.c' is up to date. `vmm_stat.c' is up to date. `vmm_util.c' is up to date. `x86.c' is up to date. `iommu.c' is up to date. `ppt.c' is up to date. `vatpic.c' is up to date. `vatpit.c' is up to date. `vhpet.c' is up to date. `vioapic.c' is up to date. `vlapic.c' is up to date. `vpmtmr.c' is up to date. `vrtc.c' is up to date. `ept.c' is up to date. `vmcs.c' is up to date. `vmx_msr.c' is up to date. `vmx_support.S' is up to date. `vmx.c' is up to date. `vtd.c' is up to date. `vmcb.c' is up to date. `svm.c' is up to date. `svm_support.S' is up to date. `npt.c' is up to date. `ivrs_drv.c' is up to date. `amdvi_hw.c' is up to date. `svm_msr.c' is up to date. `afterdepend' was not built (made 1, flags 2019, type 3018001)! `afterdepend' has .ORDER dependency against .depend (made 1, flags 301b, type 3020001) `opt_global.h' was not built (made 0, flags 2009, type 3000000)! *** [all_subdir_vmm] Error code 1 From owner-freebsd-current@freebsd.org Tue Dec 5 17:10:10 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C96EE712FA for ; Tue, 5 Dec 2017 17:10:10 +0000 (UTC) (envelope-from bdrewery@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 D126E63413; Tue, 5 Dec 2017 17:10:09 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id F096814FAE; Tue, 5 Dec 2017 17:10:08 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id DFFFA17BA; Tue, 5 Dec 2017 17:10:07 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id 3R36rnRICYxC; Tue, 5 Dec 2017 17:10:01 +0000 (UTC) Subject: Re: buildkernel broken after r326553 DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 27915148D To: Yuri Pankov , freebsd-current References: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> Date: Tue, 5 Dec 2017 09:10:03 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Fq1fwM0NxmHTsRuIlCd5h6NGfhHjvpRaA" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 17:10:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Fq1fwM0NxmHTsRuIlCd5h6NGfhHjvpRaA Content-Type: multipart/mixed; boundary="XRdVnK4Ik1wrrRrs7mlromOIRGCXUk7Mv"; protected-headers="v1" From: Bryan Drewery To: Yuri Pankov , freebsd-current Message-ID: <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> Subject: Re: buildkernel broken after r326553 References: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> In-Reply-To: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> --XRdVnK4Ik1wrrRrs7mlromOIRGCXUk7Mv Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 12/5/2017 9:03 AM, Yuri Pankov wrote: > Hi, >=20 > Looks like one of the commits by Bryan (r326549-r326553) has broken the= > kernel build for me (using -j32, but serial build did fail as well) -- > checking out r326547 make it work again. >=20 > I can't pinpoint the exact error in the build log, as it seems to be > some make weirdness, so here's a guess, please let me know if you need > full build log: >=20 > --- all_subdir_vmm --- > make[4]: Graph cycles through `vmx_assym.h' > make[4]: Graph cycles through `vmx_genassym.o' > make[4]: Graph cycles through `svm_assym.h' > make[4]: Graph cycles through `svm_genassym.o' > `svm_genassym.c' is up to date. > `vmx_genassym.c' is up to date. > `vmm.c' is up to date. > `vmm_dev.c' is up to date. > `vmm_host.c' is up to date. > `vmm_instruction_emul.c' is up to date. > `vmm_ioport.c' is up to date. > `vmm_lapic.c' is up to date. > `vmm_mem.c' is up to date. > `vmm_stat.c' is up to date. > `vmm_util.c' is up to date. > `x86.c' is up to date. > `iommu.c' is up to date. > `ppt.c' is up to date. > `vatpic.c' is up to date. > `vatpit.c' is up to date. > `vhpet.c' is up to date. > `vioapic.c' is up to date. > `vlapic.c' is up to date. > `vpmtmr.c' is up to date. > `vrtc.c' is up to date. > `ept.c' is up to date. > `vmcs.c' is up to date. > `vmx_msr.c' is up to date. > `vmx_support.S' is up to date. > `vmx.c' is up to date. > `vtd.c' is up to date. > `vmcb.c' is up to date. > `svm.c' is up to date. > `svm_support.S' is up to date. > `npt.c' is up to date. > `ivrs_drv.c' is up to date. > `amdvi_hw.c' is up to date. > `svm_msr.c' is up to date. > `afterdepend' was not built (made 1, flags 2019, type 3018001)! > =C2=A0=C2=A0=C2=A0 `afterdepend' has .ORDER dependency against .depend = (made 1, flags > 301b, type 3020001) > `opt_global.h' was not built (made 0, flags 2009, type 3000000)! > *** [all_subdir_vmm] Error code 1 I'll have a fix in shortly. Sorry about that. --=20 Regards, Bryan Drewery --XRdVnK4Ik1wrrRrs7mlromOIRGCXUk7Mv-- --Fq1fwM0NxmHTsRuIlCd5h6NGfhHjvpRaA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJaJtLrAAoJEDXXcbtuRpfPtJUIAJxHxCjVuYK2rRHM5LIj4zy0 MndqDLnRMOydxtEvSHElUJybC4J+OwcPG73PshcFUrHKlF3ef9s7LG1cIvbhjXwi rYRRERzOOl5QJHU/6/eSoPDaY5gmtB+OrNkBMuI2NopFZPo6GYVPfVA9iIRoU/mf mQOYnuOKArxCq9Vpq1FHnd+1LyjMzUWACN52FgPU+5hgbTZuuPbkHe7IKsQhLZ/7 BOUSXYtkHRXfSu7YfJN9Lij4soICyesKpG3Xh4mlbvk+sGnFz4R+moyN6PiaCka2 GOg7s64+mGUpSPan+fjdzf/6kbYgni0idFrMWNtKIYCafgnMjm7omtPipl2Zndk= =Sp1D -----END PGP SIGNATURE----- --Fq1fwM0NxmHTsRuIlCd5h6NGfhHjvpRaA-- From owner-freebsd-current@freebsd.org Tue Dec 5 17:24:31 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 030F4E71CD0 for ; Tue, 5 Dec 2017 17:24:31 +0000 (UTC) (envelope-from bdrewery@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 C792E6456A; Tue, 5 Dec 2017 17:24:30 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 03224158E0; Tue, 5 Dec 2017 17:24:30 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 3A71D1823; Tue, 5 Dec 2017 17:24:29 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id OximZ-P1QLbs; Tue, 5 Dec 2017 17:24:26 +0000 (UTC) Subject: Re: buildkernel broken after r326553 DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com C3196181E From: Bryan Drewery To: Yuri Pankov , freebsd-current References: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: Date: Tue, 5 Dec 2017 09:24:28 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UamMcBqMJCjRWRU8bubBOu4KE9fGawdgu" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 17:24:31 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UamMcBqMJCjRWRU8bubBOu4KE9fGawdgu Content-Type: multipart/mixed; boundary="NnRHhR9HkMm3iEN2nAHFMduiv9D1OrM3h"; protected-headers="v1" From: Bryan Drewery To: Yuri Pankov , freebsd-current Message-ID: Subject: Re: buildkernel broken after r326553 References: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> In-Reply-To: <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> --NnRHhR9HkMm3iEN2nAHFMduiv9D1OrM3h Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 12/5/2017 9:10 AM, Bryan Drewery wrote: > On 12/5/2017 9:03 AM, Yuri Pankov wrote: >> Hi, >> >> Looks like one of the commits by Bryan (r326549-r326553) has broken th= e >> kernel build for me (using -j32, but serial build did fail as well) --= >> checking out r326547 make it work again. >> >> I can't pinpoint the exact error in the build log, as it seems to be >> some make weirdness, so here's a guess, please let me know if you need= >> full build log: >> >> --- all_subdir_vmm --- >> make[4]: Graph cycles through `vmx_assym.h' >> make[4]: Graph cycles through `vmx_genassym.o' >> make[4]: Graph cycles through `svm_assym.h' >> make[4]: Graph cycles through `svm_genassym.o' >> `svm_genassym.c' is up to date. >> `vmx_genassym.c' is up to date. >> `vmm.c' is up to date. >> `vmm_dev.c' is up to date. >> `vmm_host.c' is up to date. >> `vmm_instruction_emul.c' is up to date. >> `vmm_ioport.c' is up to date. >> `vmm_lapic.c' is up to date. >> `vmm_mem.c' is up to date. >> `vmm_stat.c' is up to date. >> `vmm_util.c' is up to date. >> `x86.c' is up to date. >> `iommu.c' is up to date. >> `ppt.c' is up to date. >> `vatpic.c' is up to date. >> `vatpit.c' is up to date. >> `vhpet.c' is up to date. >> `vioapic.c' is up to date. >> `vlapic.c' is up to date. >> `vpmtmr.c' is up to date. >> `vrtc.c' is up to date. >> `ept.c' is up to date. >> `vmcs.c' is up to date. >> `vmx_msr.c' is up to date. >> `vmx_support.S' is up to date. >> `vmx.c' is up to date. >> `vtd.c' is up to date. >> `vmcb.c' is up to date. >> `svm.c' is up to date. >> `svm_support.S' is up to date. >> `npt.c' is up to date. >> `ivrs_drv.c' is up to date. >> `amdvi_hw.c' is up to date. >> `svm_msr.c' is up to date. >> `afterdepend' was not built (made 1, flags 2019, type 3018001)! >> =C2=A0=C2=A0=C2=A0 `afterdepend' has .ORDER dependency against .depend= (made 1, flags >> 301b, type 3020001) >> `opt_global.h' was not built (made 0, flags 2009, type 3000000)! >> *** [all_subdir_vmm] Error code 1 >=20 > I'll have a fix in shortly. Sorry about that. >=20 Fixed in r326569. --=20 Regards, Bryan Drewery --NnRHhR9HkMm3iEN2nAHFMduiv9D1OrM3h-- --UamMcBqMJCjRWRU8bubBOu4KE9fGawdgu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJaJtZMAAoJEDXXcbtuRpfPuXMH/RuF53A4ngrW29R+rYwAyfAT M+Z9m4e1MKcpC9+Hz5Iajm+ENkhCq9Kt06V26XyTRXPNmWvEqrLkdqLFth8M5IhN H+XtSHAvFXjz0tBIyHAVi040bPTn4/bpdybN7SiseStuqt478jiQ7oplMsLADrjt aiMPofHe1ml/TENLx+8dYeSH43wptpr7tzavm1qe6oqjRJsLlsv6zTPjYewjNo1q NvRQMmwU7SIrzevFp0xVroYt5o9OZvfirmF0xOBBG6EiRDoS1HgrZPyfCqyfcKwk I0gcBfvWMG+2ih7kF0qvViZBzVieCwS6ViHdS1px6B6uBBYlmNLvqsZRheldOoA= =DuJF -----END PGP SIGNATURE----- --UamMcBqMJCjRWRU8bubBOu4KE9fGawdgu-- From owner-freebsd-current@freebsd.org Tue Dec 5 17:56:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B267E727C5 for ; Tue, 5 Dec 2017 17:56:06 +0000 (UTC) (envelope-from yuripv@gmx.com) 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 D879B657D3; Tue, 5 Dec 2017 17:56:05 +0000 (UTC) (envelope-from yuripv@gmx.com) Received: from thor.xvoid.org ([85.173.23.68]) by mail.gmx.com (mrgmx102 [212.227.17.174]) with ESMTPSA (Nemesis) id 0M6874-1fItdx2mPS-00y5O5; Tue, 05 Dec 2017 18:56:03 +0100 Subject: Re: buildkernel broken after r326553 To: Bryan Drewery , freebsd-current References: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> From: Yuri Pankov Message-ID: <6eed7632-9626-37e1-773e-5dbe93193ebe@gmx.com> Date: Tue, 5 Dec 2017 20:56:02 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.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:K0:WGxCepiV97q8mMSlMp/zKQgvOPKCJPmLPsQa/37rQtBwk2JMXiA cW4ZaLhgGuWnPCZEDpIVj4gAhclMIlJg2KCLSwkFJQtzD1QbQT3lz4VIobyvZydG270nTdf lowoXlxOqk+y70G2lmeWMhV8OAIYdCCR94xw0s4Am+0W4ZJosLUmy/5uzM1boxqOcY5nDi6 +k3m1HgizHXuO5A1vljbA== X-UI-Out-Filterresults: notjunk:1;V01:K0:6EYBCDPIs6A=:lJvQBhfdqAXJvX5sEXn28W JUJgka64ItExsVo+MYgsPp9iubThoWu+D1smPlOTfC+dbgIGRMDM70LguA7iqoCVn1W5gy1WE ur5gZXphWuiQL4SveS3Q0OyAmSk9TVE0ZLEvfOYohXmOcKkZvbcT86+tHe9ipI7v1WQL2RQi6 VWKx8qrByCbRUYdST4riHJxM0P7uA82H5Y9lNBYV6qj5lxmcPI+WHT63xTT8AD4lshqB+AlW7 3msrjPrp06UwqxK46MLzfy5gDzutFCwRLlBPd+1/KOEJgWii/rWBNOh3MYpEE+UKnPEze4Okm oK9VEo8S3qxTGRmxcFFcq8WJ31m2QKjdPdmVkH0MT/g0nJ1t1uHy21bDWdh0uoz9Q5r5msAjZ 3nOghB1F4BI8XSoGSth5F7nmxOlXd/cdcwgV02VQTUXAhIeg+oAwAijNDtnxWdUdJC1SdEmUA f4J898O12fyN/D9pvWCV0UdrY6oCn/QpYTUik0UQ9ZuKpRFJ7Fm7w8o0t/pPRTdHTEbcgEok3 8gi9Lx+NNjSsC98qAr6JH8XfGuoERLryW1F1WveWnYbbbyMvAIXAed0RlPO9n6Xm0M5O6TvmE kF1xxIlufBYpbOCeg3BZtwEW3vrRg6SbA/fNdxrfc7Sy756Paa1E+HVx/OONDNbccYgS9fgrN +FD8jy6tdN+OfeFQFgEhDFLOypXTqK1DpVn15NKacj1ozi79YocMidNMrT5BTXyJ0o+3DVMKW uUnYasS4bbEi7oQNC4qJliAbKT3yKtYKZcK3uLufqaCxOLyDpPdbIW6u6XQqS5fRdXoJRkZi+ PH/T+C3r9cnwzf6i4gsym7XGTvPk/Td1YhEtkwJOXvS1NQDuks= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 17:56:06 -0000 On Tue, Dec 5, 2017 at 09:24:28AM -0800, Bryan Drewery wrote: > On 12/5/2017 9:10 AM, Bryan Drewery wrote: >> On 12/5/2017 9:03 AM, Yuri Pankov wrote: >>> Hi, >>> >>> Looks like one of the commits by Bryan (r326549-r326553) has broken the >>> kernel build for me (using -j32, but serial build did fail as well) -- >>> checking out r326547 make it work again. >>> >>> I can't pinpoint the exact error in the build log, as it seems to be >>> some make weirdness, so here's a guess, please let me know if you need >>> full build log: >>> >>> --- all_subdir_vmm --- >>> make[4]: Graph cycles through `vmx_assym.h' >>> make[4]: Graph cycles through `vmx_genassym.o' >>> make[4]: Graph cycles through `svm_assym.h' >>> make[4]: Graph cycles through `svm_genassym.o' >>> `svm_genassym.c' is up to date. >>> `vmx_genassym.c' is up to date. >>> `vmm.c' is up to date. >>> `vmm_dev.c' is up to date. >>> `vmm_host.c' is up to date. >>> `vmm_instruction_emul.c' is up to date. >>> `vmm_ioport.c' is up to date. >>> `vmm_lapic.c' is up to date. >>> `vmm_mem.c' is up to date. >>> `vmm_stat.c' is up to date. >>> `vmm_util.c' is up to date. >>> `x86.c' is up to date. >>> `iommu.c' is up to date. >>> `ppt.c' is up to date. >>> `vatpic.c' is up to date. >>> `vatpit.c' is up to date. >>> `vhpet.c' is up to date. >>> `vioapic.c' is up to date. >>> `vlapic.c' is up to date. >>> `vpmtmr.c' is up to date. >>> `vrtc.c' is up to date. >>> `ept.c' is up to date. >>> `vmcs.c' is up to date. >>> `vmx_msr.c' is up to date. >>> `vmx_support.S' is up to date. >>> `vmx.c' is up to date. >>> `vtd.c' is up to date. >>> `vmcb.c' is up to date. >>> `svm.c' is up to date. >>> `svm_support.S' is up to date. >>> `npt.c' is up to date. >>> `ivrs_drv.c' is up to date. >>> `amdvi_hw.c' is up to date. >>> `svm_msr.c' is up to date. >>> `afterdepend' was not built (made 1, flags 2019, type 3018001)! >>>     `afterdepend' has .ORDER dependency against .depend (made 1, flags >>> 301b, type 3020001) >>> `opt_global.h' was not built (made 0, flags 2009, type 3000000)! >>> *** [all_subdir_vmm] Error code 1 >> >> I'll have a fix in shortly. Sorry about that. >> > > Fixed in r326569. Thank you! From owner-freebsd-current@freebsd.org Tue Dec 5 18:18:31 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB9FBE732B0 for ; Tue, 5 Dec 2017 18:18:31 +0000 (UTC) (envelope-from gurenchan@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 G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AAEAE66818 for ; Tue, 5 Dec 2017 18:18:31 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x235.google.com with SMTP id 68so3699705ite.4 for ; Tue, 05 Dec 2017 10:18:31 -0800 (PST) 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=bYduQhaUi2OIUE5Am21o1TC2ExnAJeVzB+Y5+6fykDU=; b=VaSvxXemX0wKdHVRKKu/lTfN7p4rU5Dckosy1m/N6HrIvdBy9O4zHRIEnzL38yybiw jqEohOabcaYBD5cLmunG/xbWoO+9eyWE/ZVtrdcLC2G18XSgtQeuAaZulWzGsPjAZQqE kDSGKZqTR6wLydYixr7d61NEmVYH5onPy+qy8yYvPE95bcUxuDvDiHCrihTQ/FdUyv9H eOD0/EodHfx/ekRAroxxa8/+ztSICztuNG2p2v3K0vOe887DFHqgANToq1GnWMPfDiRh D/yjnArb8LooZfUDA5ocryh9j5lnn9GcVfxLBplflp2640ea7uyW1TwvADdM4VxAMbc6 3AGw== 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=bYduQhaUi2OIUE5Am21o1TC2ExnAJeVzB+Y5+6fykDU=; b=dXQP99kOyduc6wtIw5LeU8xcZzT2D0gwkPz2T7XYPYiWk2O7k3IFUrmW9NsZaKuNfy Psre708y6c5qjQ2WQYznsrnmkbiGFv1SlCRQ1o438z9D6xoWG1nEYgGXUW6lSLxO65sE 7Pa8fkDI4am3am0LcK/dGW50L2C55rSsJuy/upggxo5GVfVhpm+gQBPgYa1oqKJmFPXi zcojYAKY+jq3RLoni9nzLiBF/BTCxz/M88O2m7AnOvlsQxCapTXTl8l+lQtrH3sKFTY3 nC7AiG5C4R4CQ7hFOT47DP0qEtdhBtg3TRKXUPTOy0tbKiYkxa+e1AOx9dnHy3B+gdk3 nsgg== X-Gm-Message-State: AJaThX49sbKQSOVR/pSD1ifF/PLfhBMM2zhy213+SZK9gXHLQzg+X9y6 sFHvGHsqrZ5ZY/F450jBq6WpLQzZHCCr9sNRPHCbuA== X-Google-Smtp-Source: AGs4zMaeL0P8gd0LdfpLff7cWGEp0LYmnBjKDgpA228wiZfKHlrkhCUnDrOBSYS6N6CXywBW3HnfbB49NFo6zSDrl0A= X-Received: by 10.107.85.5 with SMTP id j5mr29245222iob.296.1512497910461; Tue, 05 Dec 2017 10:18:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.11.31 with HTTP; Tue, 5 Dec 2017 10:18:29 -0800 (PST) From: blubee blubeeme Date: Wed, 6 Dec 2017 02:18:29 +0800 Message-ID: Subject: valloric YCM [header definitions] To: FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 18:18:32 -0000 I'm looking for where the u_int, u_long headers are defined? for instance MOD_LOAD, UNLOAD, ENOTSUP along with u_int and u_long aren't being picked up by libclang module_t isn't being found either but I located that header file in /usr/include/sys/module.h snd_modevent(module_t mod, int type, void *data) { switch (type) { case MOD_LOAD: break; case MOD_UNLOAD: break; default: return (ENOTSUP); break; } return 0; } Anyone here uses YCM? Here's a verbose output of my global ycm_config. I hard coded the values to test but still some headers like u_int, u_long and the above mentioned MOD_* aren't being picked up. Any ideas why? '-std=c99', '-x', 'c', '-I', '/usr/local/include', '-I', '/usr/include', '-I', '/usr/include/teken', '-I', '/usr/include/geom', '-I', '/usr/include/netgraph', '-I', '/usr/include/isofs', '-I', '/usr/include/net80211', '-I', '/usr/include/gssapi', '-I', '/usr/include/xlocale', '-I', '/usr/include/netpfil', '-I', '/usr/include/gcc', '-I', '/usr/include/bsnmp', '-I', '/usr/include/libxo', '-I', '/usr/include/ssp', '-I', '/usr/include/devdctl', '-I', '/usr/include/security', '-I', '/usr/include/crypto', '-I', '/usr/include/cam', '-I', '/usr/include/rdma', '-I', '/usr/include/infiniband', '-I', '/usr/include/rpcsvc', '-I', '/usr/include/atf-c', '-I', '/usr/include/netnatm', '-I', '/usr/include/ufs', '-I', '/usr/include/edit', '-I', '/usr/include/nfsserver', '-I', '/usr/include/netsmb', '-I', '/usr/include/gnu', '-I', '/usr/include/net', '-I', '/usr/include/private', '-I', '/usr/include/nfsclient', '-I', '/usr/include/openssl', '-I', '/usr/include/libmilter', '-I', '/usr/include/atf-c++', '-I', '/usr/include/netinet6', '-I', '/usr/include/x86', '-I', '/usr/include/dev', '-I', '/usr/include/bsm', '-I', '/usr/include/netipsec', '-I', '/usr/include/netinet', '-I', '/usr/include/krb5', '-I', '/usr/include/casper', '-I', '/usr/include/protocols', '-I', '/usr/include/lib80211', '-I', '/usr/include/arpa', '-I', '/usr/include/pcap', '-I', '/usr/include/nfs', '-I', '/usr/include/machine', '-I', '/usr/include/fs', '-I', '/usr/include/sys', '-I', '/usr/include/rpc', '-I', '/usr/include/kadm5', '-I', '/usr/include/vm', '-I', '/usr/include/c++', '-I', '/usr/include/lzma', '-I', '/sys', '-I', '/dev', '-I', '/usr/src', From owner-freebsd-current@freebsd.org Tue Dec 5 18:26:09 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62309E73ACA for ; Tue, 5 Dec 2017 18:26:09 +0000 (UTC) (envelope-from roberthuff@rcn.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 12740671EF for ; Tue, 5 Dec 2017 18:26:09 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0EB89E73AC9; Tue, 5 Dec 2017 18:26:09 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E3C8E73AC8 for ; Tue, 5 Dec 2017 18:26:09 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp.rcn.com (smtp.rcn.com [69.168.97.78]) (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 BE33B671E0 for ; Tue, 5 Dec 2017 18:26:08 +0000 (UTC) (envelope-from roberthuff@rcn.com) X_CMAE_Category: , , X-CNFS-Analysis: v=2.2 cv=Tsikv3fh c=1 sm=1 tr=0 a=9TgA2UwI6Wy+6BV4wQM/cQ==:117 a=9TgA2UwI6Wy+6BV4wQM/cQ==:17 a=KGjhK52YXX0A:10 a=L9H7d07YOLsA:10 a=kj9zAlcOel0A:10 a=XRQyMpdBKAEA:10 a=ocR9PWop10UA:10 a=48faUk6PgeAA:10 a=6I5d2MoRAAAA:8 a=VCwKYgjEwBGrukH0sWEA:9 a=CjuIK1q_8ugA:10 a=FL76T4nP6cMA:10 a=EldiDC-a73cA:10 a=IjZwj45LgO3ly-622nXo:22 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine X-Authed-Username: cm9iZXJ0aHVmZkByY24uY29t Authentication-Results: smtp01.rcn.cmh.synacor.com smtp.mail=roberthuff@rcn.com; spf=softfail; sender-id=softfail Authentication-Results: smtp01.rcn.cmh.synacor.com smtp.user=roberthuff; auth=pass (PLAIN) Received-SPF: softfail (smtp01.rcn.cmh.synacor.com: transitional domain rcn.com does not designate 209.6.230.48 as permitted sender) Received: from [209.6.230.48] ([209.6.230.48:38115] helo=jerusalem.litteratus.org.litteratus.org) by smtp.rcn.com (envelope-from ) (ecelerity 3.6.25.56547 r(Core:3.6.25.0)) with ESMTPSA (cipher=AES256-GCM-SHA384) id 55/C3-27650-EB4E62A5; Tue, 05 Dec 2017 13:26:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <23078.58557.784694.890899@jerusalem.litteratus.org> Date: Tue, 5 Dec 2017 13:26:05 -0500 To: current@freebsd.org CC: roberthuff@rcn.com Subject: buildkernel fails for rev 326557 X-Mailer: VM 8.2.0b under 25.3.1 (amd64-portbld-freebsd11.0) X-Mailman-Approved-At: Tue, 05 Dec 2017 18:45:36 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 18:26:09 -0000 Hello: I am trying to update a system from: FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64 to: huff@> svn info Path: . Working Copy Root Path: /usr/src URL: http://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 326557 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 326557 Last Changed Date: 2017-12-04 23:43:39 -0500 (Mon, 04 Dec 2017) After "rm -rf /usr/obj": Buildworld completes successfully. Buildkernel, with "-j1", fails with: `svm.c' is up to date. `svm_support.S' is up to date. `npt.c' is up to date. `ivrs_drv.c' is up to date. `amdvi_hw.c' is up to date. `svm_msr.c' is up to date. `afterdepend' was not built (made 1, flags 2019, type 3018001)! `afterdepend' has .ORDER dependency against .depend (made 1, flags 301b, type 3020001) `opt_global.h' was not built (made 0, flags 2009, type 3000000)! *** [all_subdir_vmm] Error code 1 make[3]: stopped in /usr/src/sys/modules 1 error make[3]: stopped in /usr/src/sys/modules *** [modules-all] Error code 2 make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/JERUSALEM 1 error make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/JERUSALEM *** [buildkernel] Error code 2 Rechecking src/UPDATING shows nothing interesting. The kernel config file is appended. Have I screwed something up, or is there a problem elsewhere? Respectfully, Robert Huff # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (https://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: head/sys/amd64/conf/GENERIC 326377 2017-11-29 23:41:49Z scottl $ cpu HAMMER ident JERUSALEM makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols makeoptions WITH_CTF=1 # Run ctfconvert(1) for DTrace support options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options VIMAGE # Subsystem virtualization, e.g. VNET options INET # InterNETworking options INET6 # IPv6 communications protocols options IPSEC # IP (v4/v6) security options IPSEC_SUPPORT # Allow kldload of ipsec and tcpmd5 options TCP_OFFLOAD # TCP offload options TCP_HHOOK # hhook(9) framework for TCP options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options QUOTA # Enable disk quotas for UFS options MD_ROOT # MD is a potential root device options NFSCL # Network Filesystem Client options NFSD # Network Filesystem Server options NFSLOCKD # Network Lock Manager options NFS_ROOT # NFS usable as /, requires NFSCL options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_RAID # Soft RAID functionality. options GEOM_LABEL # Provides labelization options COMPAT_FREEBSD32 # Compatible with i386 binaries #options COMPAT_FREEBSD4 # Compatible with FreeBSD4 #options COMPAT_FREEBSD5 # Compatible with FreeBSD5 #options COMPAT_FREEBSD6 # Compatible with FreeBSD6 #options COMPAT_FREEBSD7 # Compatible with FreeBSD7 #options COMPAT_FREEBSD9 # Compatible with FreeBSD9 options COMPAT_FREEBSD10 # Compatible with FreeBSD10 options COMPAT_FREEBSD11 # Compatible with FreeBSD11 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed. options KBD_INSTALL_CDEV # install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options CAPABILITY_MODE # Capsicum capability mode options CAPABILITIES # Capsicum capabilities options MAC # TrustedBSD MAC Framework options KDTRACE_FRAME # Ensure frames are compiled in options KDTRACE_HOOKS # Kernel DTrace hooks options DDB_CTF # Kernel ELF linker loads CTF data options INCLUDE_CONFIG_FILE # Include this file in kernel options RACCT # Resource accounting framework options RACCT_DEFAULT_TO_DISABLED # Set kern.racct.enable=0 by default options RCTL # Resource limits # Debugging support. Always need this: options KDB # Enable kernel debugger support. options KDB_TRACE # Print a stack trace for a panic. # For full debugger support use (turn off in stable branch): options BUF_TRACKING # Track buffer history options DDB # Support DDB. options FULL_BUF_TRACKING # Track more buffer history options GDB # Support remote GDB. options DEADLKRES # Enable the deadlock resolver options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel options DEVICE_NUMA # I/O Device Affinity options EARLY_AP_STARTUP # CPU frequency control device cpufreq # Bus support. device acpi options ACPI_DMAR device pci options PCI_HP # PCI-Express native HotPlug options PCI_IOV # PCI SR-IOV support # Floppy drives device fdc # ATA controllers device ahci # AHCI-compatible SATA controllers device ata # Legacy ATA/SATA controllers device mvs # Marvell 88SX50XX/88SX60XX/88SX70XX/SoC SATA device siis # SiliconImage SiI3124/SiI3132/SiI3531 SATA # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device esp # AMD Am53C974 (Tekram DC-390(T)) device hptiop # Highpoint RocketRaid 3xxx series device isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module device mpt # LSI-Logic MPT-Fusion device mps # LSI-Logic MPT-Fusion 2 device mpr # LSI-Logic MPT-Fusion 3 #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters device adv # Advansys SCSI adapters device adw # Advansys wide SCSI adapters device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device bt # Buslogic/Mylex MultiMaster SCSI adapters device isci # Intel C600 SAS controller # ATA/SCSI peripherals device scbus # SCSI bus (required for ATA/SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct ATA/SCSI access) device ses # Enclosure Services (SES and SAF-TE) #device ctl # CAM Target Layer # RAID controllers interfaced to the SCSI subsystem device amr # AMI MegaRAID device arcmsr # Areca SATA II RAID device ciss # Compaq Smart RAID 5* device dpt # DPT Smartcache III, IV - See NOTES for options device hptmv # Highpoint RocketRAID 182x device hptnr # Highpoint DC7280, R750 device hptrr # Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx device hpt27xx # Highpoint RocketRAID 27xx device iir # Intel Integrated RAID device ips # IBM (Adaptec) ServeRAID device mly # Mylex AcceleRAID/eXtremeRAID device twa # 3ware 9000 series PATA/SATA RAID device tws # LSI 3ware 9750 SATA+SAS 6Gb/s RAID controller # RAID controllers device aac # Adaptec FSA RAID device aacp # SCSI passthrough for aac (requires CAM) device aacraid # Adaptec by PMC RAID device ida # Compaq Smart RAID device mfi # LSI MegaRAID SAS device mlx # Mylex DAC960 family device mrsas # LSI/Avago MegaRAID SAS/SATA, 6Gb/s and 12Gb/s device pmspcv # PMC-Sierra SAS/SATA Controller driver #XXX pointer/int warnings #device pst # Promise Supertrak SX6000 device twe # 3ware ATA RAID # NVM Express (NVMe) support device nvme # base NVMe driver device nvd # expose NVMe namespaces as disks, depends on nvme # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver options VESA # Add support for VESA BIOS Extensions (VBE) device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc options SC_PIXEL_MODE # add support for the raster text mode # vt is the new video console driver device vt device vt_vga device vt_efifb device agp # support several AGP chipsets # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device uart # Generic UART driver # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device vpo # Requires scbus and da device puc # Multi I/O cards and multi-channel UARTs # PCI Ethernet NICs. device bxe # Broadcom NetXtreme II BCM5771X/BCM578XX 10GbE device de # DEC/Intel DC21x4x (``Tulip'') device em # Intel PRO/1000 Gigabit Ethernet Family device ix # Intel PRO/10GbE PCIE PF Ethernet device ixv # Intel PRO/10GbE PCIE VF Ethernet device ixl # Intel XL710 40Gbe PCIE Ethernet options IXL_IW # Enable iWARP Client Interface in ixl(4) device ixlv # Intel XL710 40Gbe VF PCIE Ethernet device le # AMD Am7900 LANCE and Am79C9xx PCnet device ti # Alteon Networks Tigon I/II gigabit Ethernet device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device ae # Attansic/Atheros L2 FastEthernet device age # Attansic/Atheros L1 Gigabit Ethernet device alc # Atheros AR8131/AR8132 Ethernet device ale # Atheros AR8121/AR8113/AR8114 Ethernet device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device cas # Sun Cassini/Cassini+ and NS DP83065 Saturn device dc # DEC/Intel 21143 and various workalikes device et # Agere ET1310 10/100/Gigabit Ethernet device fxp # Intel EtherExpress PRO/100B (82557, 82558) device gem # Sun GEM/Sun ERI/Apple GMAC device hme # Sun HME (Happy Meal Ethernet) device jme # JMicron JMC250 Gigabit/JMC260 Fast Ethernet device lge # Level 1 LXT1001 gigabit Ethernet device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet device nfe # nVidia nForce MCP on-board Ethernet device nge # NatSemi DP83820 gigabit Ethernet device pcn # AMD Am79C97x PCI 10/100 (precedence over 'le') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sge # Silicon Integrated Systems SiS190/191 device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet device ste # Sundance ST201 (D-Link DFE-550TX) device stge # Sundance/Tamarack TC9021 gigabit Ethernet device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vge # VIA VT612x gigabit Ethernet device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Wireless NIC cards device wlan # 802.11 support options IEEE80211_DEBUG # enable debug msgs options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's options IEEE80211_SUPPORT_MESH # enable 802.11s draft support device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device wlan_amrr # AMRR transmit rate control algorithm device an # Aironet 4500/4800 802.11 wireless NICs. device ath # Atheros NICs device ath_pci # Atheros pci/cardbus glue device ath_hal # pci/cardbus chip support options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors options AH_AR5416_INTERRUPT_MITIGATION # AR5416 interrupt mitigation options ATH_ENABLE_11N # Enable 802.11n support for AR5416 and later device ath_rate_sample # SampleRate tx rate control for ath #device bwi # Broadcom BCM430x/BCM431x wireless NICs. #device bwn # Broadcom BCM43xx wireless NICs. device ipw # Intel 2100 wireless NICs. device iwi # Intel 2200BG/2225BG/2915ABG wireless NICs. device iwn # Intel 4965/1000/5000/6000 wireless NICs. device malo # Marvell Libertas wireless NICs. device mwl # Marvell 88W8363 802.11n wireless NICs. device ral # Ralink Technology RT2500 wireless NICs. device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. device wpi # Intel 3945ABG wireless NICs. # Pseudo devices. device loop # Network loopback device random # Entropy device device padlock_rng # VIA Padlock RNG device rdrand_rng # Intel Bull Mountain RNG device ether # Ethernet support device vlan # 802.1Q VLAN support device tun # Packet tunnel. device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support options USB_DEBUG # enable debug msgs device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device xhci # XHCI PCI->USB interface (USB 3.0) device usb # USB Bus (required) device ukbd # Keyboard device umass # Disks/Mass storage - Requires scbus and da # Sound support device sound # Generic sound driver (required) device snd_cmi # CMedia CMI8338/CMI8738 device snd_csa # Crystal Semiconductor CS461x/428x device snd_emu10kx # Creative SoundBlaster Live! and Audigy device snd_es137x # Ensoniq AudioPCI ES137x device snd_hda # Intel High Definition Audio device snd_ich # Intel, NVidia and other ICH AC'97 Audio device snd_via8233 # VIA VT8233x Audio # MMC/SD device mmc # MMC/SD bus device mmcsd # MMC/SD memory card device sdhci # Generic PCI SD Host Controller # VirtIO support device virtio # Generic VirtIO bus (required) device virtio_pci # VirtIO PCI device device vtnet # VirtIO Ethernet device device virtio_blk # VirtIO Block device device virtio_scsi # VirtIO SCSI device device virtio_balloon # VirtIO Memory Balloon device # HyperV drivers and enhancement support device hyperv # HyperV drivers # Xen HVM Guest Optimizations # NOTE: XENHVM depends on xenpci. They must be added or removed together. options XENHVM # Xen HVM kernel infrastructure device xenpci # Xen HVM Hypervisor services driver # VMware support device vmx # VMware VMXNET3 Ethernet # Netmap provides direct access to TX/RX rings on supported NICs device netmap # netmap(4) support # The crypto framework is required by IPSEC device crypto # Required by IPSEC From owner-freebsd-current@freebsd.org Tue Dec 5 18:52:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFE2AE74B1D for ; Tue, 5 Dec 2017 18:52:58 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C811D68D35 for ; Tue, 5 Dec 2017 18:52:57 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 26CE7D32; Tue, 5 Dec 2017 12:52:51 -0600 (CST) Date: Tue, 5 Dec 2017 12:52:50 -0600 From: Mark Linimon To: blubee blubeeme Cc: FreeBSD current Subject: Re: valloric YCM [header definitions] Message-ID: <20171205185249.GA10609@lonesome.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 18:52:59 -0000 On Wed, Dec 06, 2017 at 02:18:29AM +0800, blubee blubeeme wrote: > I'm looking for where the u_int, u_long headers are defined? Although it seems to be out-of-date, for something fundamental like this you should be able to use the FXR instance: http://fxr.watson.org/fxr/search mcl From owner-freebsd-current@freebsd.org Tue Dec 5 21:03:42 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4A82E81E2A for ; Tue, 5 Dec 2017 21:03:42 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C78B6FD2D for ; Tue, 5 Dec 2017 21:03:42 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id w10so4120032qtb.10 for ; Tue, 05 Dec 2017 13:03:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QVVK7MMPooF8sAoh6t+z8xslEHTIfeUX00QbZXTHDJE=; b=B8EmcG7UeSZkH0ptZ+3KTY2sC7IOSSkZpnR7+Wz5ub47yRXIu9ktWGXMNCUpTP6GYn jrRjZBIGlfATM485bXQhtjg967pf/S/Ojbsf4xB+8yBi6I1EjzFcVKtN6Xh7bRjGYBe6 XLJie8QAOa38NmyNpBS+SpPHIZjMbXcHCRtE8ADp/MYA5lfU/O5Z0A/+eskmEhQ92zLg 4oB4znWjnzhXiO/HPt9+np7u2VgoqeOHX3fd81Dm4fZo8l49daQhj2ehatRkn/bnT+eM Ehov53JbdPMH6J87Zgsrku7OZ2Ker2NkFnUhSi2j21cHl2vycPVv7T6ocRhZ2a5yy/Sv XKbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QVVK7MMPooF8sAoh6t+z8xslEHTIfeUX00QbZXTHDJE=; b=ollqBs7wmK+YXHENGFVvMASeNKLD1Mm4qmPGNUxrZxRsJBX/rPb+NLwuKsel5bam0X Yjd6lpq0WlGMh9frJRhyJ4IpslHppkX28lKguarnFvPgiNCyna+XwylQ7zKun5iEAkxo FpoGVHJjFqOcGLKWvRpIZNYjEKXnBRAugfNy5qDSDRtqiyNI9fACepfOA6B+APkoHE58 AdW3Bav5IaX4JWUdPX6c1+ndQz36qVc4xuulPXrGV39EOFQJKBdIbcvCHKYXXWBQ/EnZ qN5372t/jn3fE8h7pUbaG8KftiRmezhtYQIm2CER7PKPhoIM15Mw+bjogegDtjJG7C1v dwjA== X-Gm-Message-State: AKGB3mLeFVZzYA7uBiS40vQs8ljlJ79kz84C84peAEGTMO/Yxj9mvSaE HEmcuUE1oGdQ9SBWcl/Vtnbd1UlNy09HXIRkCvI= X-Google-Smtp-Source: AGs4zMbzL3QnIK+zd4IbaXDWcBzafD/ifysnBDHlL/YCZ1MRdK67wbxwJ3Qxnn+w/E3a+uuKT4kryLSfjOsBC/+9V+s= X-Received: by 10.200.50.39 with SMTP id x36mr3356859qta.255.1512507821246; Tue, 05 Dec 2017 13:03:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.39.211 with HTTP; Tue, 5 Dec 2017 13:03:40 -0800 (PST) In-Reply-To: References: From: Ryan Stone Date: Tue, 5 Dec 2017 16:03:40 -0500 Message-ID: Subject: Re: Build failure in stand To: Warner Losh Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 21:03:42 -0000 So I don't fully understand why this build failure happened, but I did manage to find root cause. It turns out that there was a bug in make that caused our build infrastructure to write objects and other build output to the srcdir rather than the objdir in certain cases when using make -C. I have a workaround in place for now and bdrewery@ is working on a fix for the build infrastructure. From owner-freebsd-current@freebsd.org Tue Dec 5 21:06:56 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF08CE821DF for ; Tue, 5 Dec 2017 21:06:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F14C70332 for ; Tue, 5 Dec 2017 21:06:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id f190so4569544ita.5 for ; Tue, 05 Dec 2017 13:06:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=TJZdjSBfV1y4BkCCFMfLhO5i+Pf1fM5bQqgPGR2RMqk=; b=XS49jLCJNzhtcYKMI6QFBXF0agaK9V/ro+wYOsfO+fIfUV+leDcE5/xvWxLEy5hQJ8 +bPP8jeSJNJJSva3N4MuRaU3ARYF3JB3STuAoJALdiDoyY0nyhOMGWbRo9efuoB8QGoO eqngM/Jq+vD25vhHbDnE1L7J6TWM+FIbA32c6qSn3dea1bOmH8luWAkr0byWNSoGDeP+ +X1y0D4Z6HbzMXmommopRYADKDOh2rgC/PQm7KbjfLcThsdPifWYRIQiCYj6oOJQrxXS P3FKKBEuY/Tu3REQWbKqorxR19nZGq3xis3/mpNKRymwlaZRhvMBylvtxscZ4GMoohtX c6Ww== 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=TJZdjSBfV1y4BkCCFMfLhO5i+Pf1fM5bQqgPGR2RMqk=; b=SyqDdF2ahxuFMKPaB7BbV8W/WYhmqc8cvUlIPjZCdumJk06RygpDOYu7Colw3hZiVb n6MOgCKsm7D0h+j/GGXbTkqkEdYttu9ITgKQ8/8HAxu9V9SFmR4GR/Y6AuHgAu6dLzEp WWjetn/b56YjWRaA2b+q5ttyLcB+vZJ+43ZVyzWSQ9VvAkZUPDWR40juGNNpS2FFaV/2 FA0/zTvSwKuuFqxdEtJ6U0ek/xCjcV0qMKtO/GYncA0KfieNsqSKuclguUd21kQ9PEFL WCpBfZfhDgDHmJeTE7iQLpja+sM6+Mvrwzb02arISrm1dVcQFxu96wQfVVfA7//XiLIg x4iw== X-Gm-Message-State: AKGB3mLdqu0mpmzPBkFbG6TEhEpKxdNFGLJnczUnpNDO8Tpc3hcmuyEE YsUZWcs6dqyYBbw1RKLOh1HrIEfWSNZJFop/uoSlsA== X-Google-Smtp-Source: AGs4zMZM9n9E7rulkABcDg3g18aAJu4L65XahN/KG/LRgz83ca78n4yPF6BVYMTkji1ZfdrEcfrG3ISbkzeWkmWv+pw= X-Received: by 10.36.147.193 with SMTP id y184mr10427412itd.64.1512508015543; Tue, 05 Dec 2017 13:06:55 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Tue, 5 Dec 2017 13:06:54 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Tue, 5 Dec 2017 14:06:54 -0700 X-Google-Sender-Auth: 09FVGw2zt-o9tlMnJP64ZiP0xfc Message-ID: Subject: Re: Build failure in stand To: Ryan Stone Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 05 Dec 2017 21:06:57 -0000 On Tue, Dec 5, 2017 at 2:03 PM, Ryan Stone wrote: > So I don't fully understand why this build failure happened, but I did > manage to find root cause. It turns out that there was a bug in make > that caused our build infrastructure to write objects and other build > output to the srcdir rather than the objdir in certain cases when > using make -C. I have a workaround in place for now and bdrewery@ is > working on a fix for the build infrastructure. > OK. That makes sense. It's caused by using the amd64 cpufuncs file being used when compiling on i386 (aka -m32). I have some fixes that should make it less likely to be an issue in the works... Warner From owner-freebsd-current@freebsd.org Wed Dec 6 08:44:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD46BE99907 for ; Wed, 6 Dec 2017 08:44:44 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-148.reflexion.net [208.70.210.148]) (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 7BA4D68E2A for ; Wed, 6 Dec 2017 08:44:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 16881 invoked from network); 6 Dec 2017 05:57:57 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 6 Dec 2017 05:57:57 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Wed, 06 Dec 2017 00:57:57 -0500 (EST) Received: (qmail 18392 invoked from network); 6 Dec 2017 05:57:57 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 6 Dec 2017 05:57:57 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A135AEC8B7B; Tue, 5 Dec 2017 21:57:56 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: rpi2 hangup during poudriere build: lots of pfault wmseg status Message-Id: <05BEA04B-249B-4E7D-855A-46DA1A0DEA16@dsl-only.net> Date: Tue, 5 Dec 2017 21:57:56 -0800 To: Freebsd-arm , freebsd-hackers , FreeBSD Current X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 08:44:44 -0000 I tried to build some ports on a rpi2 (via poudriere) but it hung up: Ethernet and normal console use. (Note: the root file system is on a USB SSD and the swap partition is also on that USB SSD.) But ~^b worked for getting to the db> prompt on the console. =46rom there a ps suggests that it got hung up in pfault activity. (Possibly insufficient RAM+swap-partition space?) But it is not clear to me that it should end up hung up vs. killing processes or other such. db> ps pid ppid pgrp uid state wmesg wchan cmd 36369 36770 36588 0 D+ pfault 0xc0832880 sh 36368 36770 36588 0 D+ pfault 0xc0832880 awk 36367 36770 36588 0 D+ pfault 0xc0832880 awk 36353 88873 36588 0 D+J pfault 0xc0832880 gmake 35115 35107 36588 0 D+J pfault 0xc0832880 ld 35107 76552 36588 0 SW+J wait 0xc4a52398 c++ 35071 35066 36588 0 D+J pfault 0xc0832880 ld 35066 76552 36588 0 SW+J wait 0xc64d6730 c++ 35047 35036 36588 0 D+J pfault 0xc0832880 ld 35036 76552 36588 0 SW+J wait 0xc5efc000 c++ 88873 88868 36588 0 S+J select 0xc5ea0b24 gmake 88868 88867 36588 0 SW+J wait 0xc3da1ac8 sh 88867 88674 36588 0 SW+J wait 0xc5904398 gmake 88674 28839 36588 0 SW+J wait 0xc66e4730 gmake 76552 76450 36588 0 SW+J wait 0xc5eb5ac8 gmake 76450 76438 36588 0 SW+J wait 0xc3aa2730 sh 76438 76380 36588 0 SW+J wait 0xc64d6000 gmake 76380 28839 36588 0 SW+J wait 0xc66e4ac8 gmake 28839 28828 36588 0 SW+J wait 0xc5f78ac8 gmake 28828 28826 36588 0 SW+J wait 0xc4a52000 sh 28826 28825 36588 0 SW+J wait 0xc5eb5398 gmake 28825 28793 36588 0 SW+J wait 0xc5c5d730 sh 28793 28792 36588 0 SW+J wait 0xc4262ac8 make 28792 23997 36588 0 SW+ wait 0xc56fb000 sh 23997 36588 36588 0 D+ pfault 0xc0832880 sh 40786 36588 36588 0 S+ piperd 0xc422c5b8 sh 36770 36588 36588 0 S+ wait 0xc5f78000 sh 36588 748 36588 0 D+ pfault 0xc0832880 sh 36387 748 36387 0 TW+ vi 748 747 748 0 SW+ wait 0xc4205000 sh 747 741 747 1001 SW+ wait 0xc4261398 su 741 740 741 1001 SWs+ wait 0xc3da0000 sh 740 737 737 1001 S select 0xc4227524 sshd 737 670 737 0 Ss select 0xc42275a4 sshd 723 722 723 0 D+ pfault 0xc0832880 sh 722 1 722 0 SWs+ wait 0xc4260398 login 721 1 721 0 Ss+ ttyin 0xc39d9474 getty 674 1 674 0 ?Ws cron 670 1 670 0 Ds pfault 0xc0832880 sshd 639 1 639 0 Ss select 0xc4227724 powerd 636 1 636 0 Ss (threaded) ntpd 100106 S select 0xc4227764 ntpd 588 587 587 0 S (threaded) nfsd 100098 S rpcsvc 0xc42ecc50 nfsd: master 100110 S rpcsvc 0xc3995250 nfsd: service 100111 S rpcsvc 0xc41721d0 nfsd: service 100112 S rpcsvc 0xc4171d50 nfsd: service 100113 S rpcsvc 0xc39952d0 nfsd: service 100114 S rpcsvc 0xc41725d0 nfsd: service 100115 S rpcsvc 0xc4171dd0 nfsd: service 100116 S rpcsvc 0xc39956d0 nfsd: service 100117 S rpcsvc 0xc3995350 nfsd: service 100118 S rpcsvc 0xc4172550 nfsd: service 100119 S rpcsvc 0xc3995750 nfsd: service 100120 S rpcsvc 0xc41726d0 nfsd: service 100121 S rpcsvc 0xc39953d0 nfsd: service 100122 S rpcsvc 0xc4172650 nfsd: service 100123 S rpcsvc 0xc41723d0 nfsd: service 100124 S rpcsvc 0xc4172450 nfsd: service 100125 S rpcsvc 0xc3995450 nfsd: service 100126 S rpcsvc 0xc4171cd0 nfsd: service 100127 S rpcsvc 0xc4172350 nfsd: service 100128 S rpcsvc 0xc41724d0 nfsd: service 100129 S rpcsvc 0xc39954d0 nfsd: service 100130 S rpcsvc 0xc4172250 nfsd: service 100131 S rpcsvc 0xc41720d0 nfsd: service 100132 S rpcsvc 0xc41722d0 nfsd: service 100133 S rpcsvc 0xc3995550 nfsd: service 100134 S rpcsvc 0xc4172050 nfsd: service 100135 S rpcsvc 0xc4171e50 nfsd: service 100136 S rpcsvc 0xc4172150 nfsd: service 100137 S rpcsvc 0xc39955d0 nfsd: service 100138 S rpcsvc 0xc4171f50 nfsd: service 100139 S rpcsvc 0xc4171ed0 nfsd: service 100140 S rpcsvc 0xc3995650 nfsd: service 587 1 587 0 Ss select 0xc42277a4 nfsd 585 1 585 0 Ss select 0xc4227624 mountd 455 1 455 0 Ss select 0xc4103d64 rpcbind 446 1 446 0 Ds pfault 0xc0832880 syslogd 375 1 375 0 Ss select 0xc4103fa4 devd 374 1 374 65 Ds pfault 0xc0832880 dhclient 328 1 328 0 Ss select 0xc4227f64 dhclient 325 1 325 0 Ss select 0xc3dec4e4 dhclient 31 0 0 0 DL vlruwt 0xc3da0730 [vnlru] 30 0 0 0 DL syncer 0xc095a6dc [syncer] 29 0 0 0 DL - 0xc095a0c8 [bufspacedaemon] 28 0 0 0 DL (threaded) [bufdaemon] 100070 D psleep 0xc0959fc0 [bufdaemon] 100092 D sdflush 0xc42ae884 [/ worker] 27 0 0 0 DL psleep 0xc095ecb4 [vmdaemon] 26 0 0 0 RL (threaded) [pagedaemon] 100068 RunQ [pagedaemon] 100074 D launds 0xc095ebb4 [laundry: dom0] 100075 D umarcl 0xc095e8fc [uma] 25 0 0 0 SL worker_ 0xc3757a90 = [bcm2835_audio_worke] 24 0 0 0 SL VCHI co 0xc3a9980c [VCHIQka-0] 23 0 0 0 DL mmcsd d 0xc3fe4800 [mmcsd0boot1: = mmc/sd] 22 0 0 0 DL mmcsd d 0xc3fe4a00 [mmcsd0boot0: = mmc/sd] 21 0 0 0 DL mmcsd d 0xc3fe4c00 [mmcsd0: mmc/sd = card] 20 0 0 0 DL - 0xc0959c34 [soaiod4] 19 0 0 0 DL - 0xc0959c34 [soaiod3] 18 0 0 0 DL - 0xc0959c34 [soaiod2] 17 0 0 0 DL - 0xc0959c34 [soaiod1] 16 0 0 0 DL - 0xc0841298 [rand_harvestq] 15 0 0 0 DL waiting 0xc0968ef0 [sctp_iterator] 14 0 0 0 DL (threaded) [usb] 100049 D - 0xc3a9f02c [usbus0] 100050 D - 0xc3a9f05c [usbus0] 100051 D - 0xc3a9f08c [usbus0] 100052 D - 0xc3a9f0bc [usbus0] 100053 D - 0xc3a9f0ec [usbus0] 100067 D - 0xc3a5d428 [smsc0] 13 0 0 0 SL sema cv 0xc0980d80 [VCHIQs-0] 9 0 0 0 SL sema cv 0xc0980d5c [VCHIQr-0] 8 0 0 0 SL sema cv 0xc0980d38 [VCHIQ-0] 7 0 0 0 DL (threaded) [cam] 100031 D - 0xc083e140 [doneq0] 100057 D - 0xc083e06c [scanner] 6 0 0 0 DL crypto_ 0xc39b50c4 [crypto returns 3] 5 0 0 0 DL crypto_ 0xc39b508c [crypto returns 2] 4 0 0 0 DL crypto_ 0xc39b5054 [crypto returns 1] 3 0 0 0 DL crypto_ 0xc39b501c [crypto returns 0] 2 0 0 0 DL crypto_ 0xc095e23c [crypto] 12 0 0 0 DL (threaded) [geom] 100018 D - 0xc0967758 [g_event] 100019 D - 0xc096775c [g_up] 100020 D - 0xc0967760 [g_down] 11 0 0 0 WL (threaded) [intr] 100006 I [swi6: Giant taskq] 100009 I [swi5: fast taskq] 100011 I [swi6: task queue] 100012 I [swi4: clock (0)] 100013 I [swi4: clock (1)] 100014 I [swi4: clock (2)] 100015 I [swi4: clock (3)] 100016 I [swi3: vm] 100017 I [swi1: netisr 0] 100032 I [intc0,69: bcmrng0] 100033 I [intc0,61: iichb0+] 100034 I [intc0,62: spi0] 100035 I [intc0,28: = bcm_dma0] 100036 I [intc0,29: = bcm_dma0] 100037 I [intc0,32: = bcm_dma0] 100038 I [intc0,33: = bcm_dma0] 100039 I [intc0,34: = bcm_dma0] 100040 I [intc0,35: = bcm_dma0] 100041 I [intc0,1: mbox0] 100042 I [intc0,70: +] 100043 I [swi0: uart] 100044 I [intc0,2: vchiq0] 100048 I [intc0,17: +] 10 0 0 0 RL (threaded) [idle] 100002 Run CPU 0 [idle: cpu0] 100003 Run CPU 1 [idle: cpu1] 100004 CanRun [idle: cpu2] 100005 Run CPU 3 [idle: cpu3] 1 0 1 0 SLs wait 0xc38b5000 [init] 0 0 0 0 RLs (threaded) [kernel] 100000 D vmwait 0xc0832880 [swapper] 100007 D - 0xc38ada00 [thread taskq] 100008 D - 0xc38ad980 [aiod_kick taskq] 100010 D - 0xc38ad880 [kqueue_ctx taskq] 100021 D - 0xc38ad780 [firmware taskq] 100022 D - 0xc38ad700 [crypto_0] 100023 D - 0xc38ad700 [crypto_1] 100024 D - 0xc38ad700 [crypto_2] 100025 D - 0xc38ad700 [crypto_3] 100056 D - 0xc38ad680 [CAM taskq] 100076 D - 0xc3fa1f00 [if_config_tqg_0] 100077 D - 0xc40c4100 [softirq_0] 100078 D - 0xc40c4080 [softirq_1] 100079 RunQ [softirq_2] 100080 D - 0xc40c3f00 [softirq_3] 100081 D - 0xc3fa1e00 [if_io_tqg_0] 100082 D - 0xc3fa1d80 [if_io_tqg_1] 100083 RunQ [if_io_tqg_2] 100084 D - 0xc3fa1c80 [if_io_tqg_3] Exploring some commands. . . db> show pageq pq_free 599 dom 0 page_cnt 205724 free 599 pq_act 160929 pq_inact 3178 pq_laund 0 = pq_unsw 0 db> show page vm_cnt.v_free_count: 599 vm_cnt.v_inactive_count: 3178 vm_cnt.v_active_count: 160929 vm_cnt.v_laundry_count: 0 vm_cnt.v_wire_count: 41018 vm_cnt.v_free_reserved: 333 vm_cnt.v_free_min: 1360 vm_cnt.v_free_target: 4441 vm_cnt.v_inactive_target: 6661 db> show freepages DOMAIN: 0 FREE LIST 0: ORDER (SIZE) | NUMBER | POOL 0 -- -- -- -- 08 (001024K) | 000000 07 (000512K) | 000000 06 (000256K) | 000000 05 (000128K) | 000002 04 (000064K) | 000000 03 (000032K) | 000000 02 (000016K) | 000001 01 (000008K) | 000001 00 (000004K) | 000002 db> show allpcpu Current CPU: 0 cpuid =3D 0 dynamic pcpu =3D 0x3d3f00 curthread =3D 0xc38b8ae0: pid 10 tid 100002 "idle: cpu0" curpcb =3D 0xe4c6de98 fpcurthread =3D 0xc4267ae0: pid 639 "powerd" idlethread =3D 0xc38b8ae0: tid 100002 "idle: cpu0" curpmap =3D 0xc0967fa4 curvnet =3D 0 cpuid =3D 1 dynamic pcpu =3D 0x13accf00 curthread =3D 0xc38b8740: pid 10 tid 100003 "idle: cpu1" curpcb =3D 0xe4c70e98 fpcurthread =3D 0xc4028740: pid 636 "ntpd" idlethread =3D 0xc38b8740: tid 100003 "idle: cpu1" curpmap =3D 0xc0967fa4 curvnet =3D 0 cpuid =3D 2 dynamic pcpu =3D 0x13acdf00 curthread =3D 0xc38b83a0: pid 10 tid 100004 "idle: cpu2" curpcb =3D 0xe4c73e98 fpcurthread =3D none idlethread =3D 0xc38b83a0: tid 100004 "idle: cpu2" curpmap =3D 0 curvnet =3D 0 cpuid =3D 3 dynamic pcpu =3D 0x24426f00 curthread =3D 0xc38b8000: pid 10 tid 100005 "idle: cpu3" curpcb =3D 0xe4c76e98 fpcurthread =3D 0xc4267ae0: pid 639 "powerd" idlethread =3D 0xc38b8000: tid 100005 "idle: cpu3" curpmap =3D 0xc0967fa4 curvnet =3D 0 db>=20 At one point before the hangup top -CawPores showed: Mem: 8308K Active, 363M Inact, 11M Laundry, 168M Wired, 88M Buf, 253M = Free Swap: 1536M Total, 1244K Used, 1535M Free Sometime before it hung up there was: # poudriere status SET PORTS JAIL BUILD STATUS QUEUE BUILT = FAIL SKIP IGNORE REMAIN TIME LOGS - default FBSDjailRPI2 2017-12-03_20h38m29s parallel_build 87 32 = 0 0 0 55 04:32:21 = /usr/local/poudriere/data/logs/bulk/FBSDjailRPI2-default/2017-12-03_20h38m= 29s The end of the poudriere output looked like: . . . [07:59:07] [01] [00:00:00] Building sysutils/dtc | dtc-1.4.5 [08:00:12] [01] [00:01:05] Saved sysutils/dtc | dtc-1.4.5 wrkdir to: = /usr/local/poudriere/data/wrkdirs/FBSDjailRPI2-default/default/dtc-1.4.5.t= bz [08:00:14] [01] [00:01:07] Finished sysutils/dtc | dtc-1.4.5: Failed: = build [08:00:14] [01] [00:01:07] Skipping sysutils/u-boot-rpi2 | = u-boot-rpi2-2017.09.00: Dependent port sysutils/dtc | dtc-1.4.5 failed [08:00:15] [01] [00:00:00] Building devel/binutils | binutils-2.28,1 (It looks like a rpi2 does not build its own sysutils/u-boot-rpi2 .) The world and kernel were head -r326192: FreeBSD 12.0-CURRENT r326192M arm FreeBSD clang vers 5.0.0svn) (M is mostly from some powerpc64 and powerpc material: I build the same source for everything generally.) /usr/ports for the ports build was at -r455204 (last before FLAVORS being enabled). I historically have not built ports on a rpi2. So this is not a comparison with past results. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-current@freebsd.org Wed Dec 6 13:12:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4760EA03BB for ; Wed, 6 Dec 2017 13:12:53 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9D88471C0E for ; Wed, 6 Dec 2017 13:12:53 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9CCE7EA03BA; Wed, 6 Dec 2017 13:12:53 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C67FEA03B9 for ; Wed, 6 Dec 2017 13:12:53 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7028071C0D for ; Wed, 6 Dec 2017 13:12:52 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id vB6DCkG7043180 for ; Wed, 6 Dec 2017 13:12:46 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id vB6DCkRL043179 for current@freebsd.org; Wed, 6 Dec 2017 05:12:46 -0800 (PST) (envelope-from david) Date: Wed, 6 Dec 2017 05:12:46 -0800 From: David Wolfskill To: current@freebsd.org Subject: logger(1) exited on signal 11 after r326525 -> r326622 Message-ID: <20171206131246.GO41364@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="acOuGx3oQeOcSZJu" Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 13:12:53 -0000 --acOuGx3oQeOcSZJu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I noticed among the messages on the console during the final stages of the transition from single- to multi-user mode: =2E.. Dec 6 12:53:13 g1-252 kernel: ugen2.3: at usbus2 Dec 6 12:53:13 g1-252 kernel: ugen1.3: at usbus1 Dec 6 12:53:13 g1-252 kernel: pid 334 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: iwn0: iwn_read_firmware: ucode rev=3D0x08530= 501 Dec 6 12:53:13 g1-252 kernel: wlan0: link state changed to UP Dec 6 12:53:13 g1-252 kernel: pid 398 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 400 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 403 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 407 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 409 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 410 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 413 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 414 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 417 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 418 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 419 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 420 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 475 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 477 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 544 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 545 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 547 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: pid 554 (logger), uid 0: exited on signal 11= (core dumped) Dec 6 12:53:13 g1-252 kernel: Linux x86-64 ELF exec handler installed Dec 6 12:53:13 g1-252 dbus[170]: [system] Activating service name=3D'org.f= reedesktop.ConsoleKit' (using servicehelper) =2E... I don't see any similar issues on my (headless) build machine; I just checked further, and verified that booting head @r326622 is the only time I see them. (The laptop spends most of its time running stable/11.) And the laptop didn't whine when booting head @r326525. I'm trying to extract useful information from /logger.core, but not doing so well on the "useful" part of that -- e.g.: g1-252(12.0-C)[10] sudo lldb -c logger.core=20 Password: (lldb) target create --core "logger.core" Core file '/logger.core' (x86_64) was loaded. (lldb) bt * thread #1, name =3D 'logger', stop reason =3D signal SIGSEGV * frame #0: 0x0000000000402152 frame #1: 0x0000000800603618 (lldb)=20 Actually writing to the log (obviously!) works.... As far as I can tell, the laptop is otherwise functioning normally. Strange.... Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is an incompetent, lying bully who is unfit for any public office. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --acOuGx3oQeOcSZJu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJaJ+zOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XZsEH/Ay4nF5uH6Ft4oFCsDOhdVKs yhdGsTQ8pRSzvR4nOGi1lD9aoF1EJRjTdvVEDuCa0bsiC98P2JPA7IYIer4YGxoc ime2LjPUa0dA9HaeCvHdBoYYDZv3lLrkOCLG8F1JxcN5Jetov4JoANghXtEz9QRx aaxZ+Xmbl9/4FUbBxqd/5J4QKup5wu8LGt2wR8sAZ2PJgQsAB6L7RbT6sxC4H6Du thvox+0iocmhCh1+SGGav4Azg74a7HS6o3S3LpcyIjbhycPq4EWUoG6TNiuecqZV EY1IsxeGbWNbCmnXjeWoItfgIzabNTttF5HMp8maNQbpX5yd8tpeadwUAI1WGHc= =c50w -----END PGP SIGNATURE----- --acOuGx3oQeOcSZJu-- From owner-freebsd-current@freebsd.org Wed Dec 6 15:35:43 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22CBCE834E6 for ; Wed, 6 Dec 2017 15:35:43 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.227]) (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 E57AF76794 for ; Wed, 6 Dec 2017 15:35:42 +0000 (UTC) (envelope-from lausts@acm.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id Mbkoe9e91Tp7WMbkreC9ze; Wed, 06 Dec 2017 15:37:01 +0000 Received: from [192.168.1.100] (presario [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB6FZbO5000920 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 6 Dec 2017 10:35:38 -0500 (EST) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host presario [192.168.1.100] claimed to be [192.168.1.100] Reply-To: lausts@acm.org To: FreeBSD Current From: Thomas Laus Subject: GPTZFSBOOT in Current r326622 has problems Message-ID: Date: Wed, 6 Dec 2017 10:35:37 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfKdzv426z+WW6Bc1hoXDq317nw2+8wy5Nn6Z9YITCocs9lZzSM1os6YDPLIVosO0ZWH0kfclZUgOti4oYY4uXP7xZbJhAUF4X4QcEKm1fBd2lI7KUpd0 xeiB6nGhvjDggaCdrZbnOxhvAI6UbEjBRqworrDVbrENktXCumyFVCdK X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 15:35:43 -0000 Group: I updated my amd64 computer today to r326622 and copied the /boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The BTX loader stopped and could not load. This rendered my system 'un-bootable'. I copied this file from an earlier live filesystem CD, which restored my computer and enabled me to boot. I also see the problem with the loader logs dumping core that others have reported recently. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Wed Dec 6 15:54:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F111EE83C07 for ; Wed, 6 Dec 2017 15:54:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B944277228 for ; Wed, 6 Dec 2017 15:54:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x234.google.com with SMTP id d14so3145206ioc.5 for ; Wed, 06 Dec 2017 07:54:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=IBwJgAUF+ZgVbwKQfnxo110M2VGybgvT7INpevr1vLo=; b=L0xsgfa3rm86lOm7VMGt0YLT1oGN6soowTG3CdxfQQRedT7FbxNuz+2110ozbVoBRr fH/lDAZzEyZllJhpM8xla3LqBwMS5OiyeJOJfCoUzV56QsF5NAZXvkds3uP7FitGPLOO IxWd93qwaNO2iWfyU22tgURQucBwW1T6F1/17nhFW0bcgdd5TnAjs/XOrYFj5ZiVlk7h hTI3N8GTY7AZZEwvB0QdVsph4r9/E4JaDgvxtQ+FVNNppiX9COe/ua0Mr3CjUVyh2qop 8bWN7/ujFe0Xb2VXoo6J8zv7JtROPZ196MBJWAhvWrAUQKtInLWHJfCyVr40jcmBpMG7 DQjQ== 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=IBwJgAUF+ZgVbwKQfnxo110M2VGybgvT7INpevr1vLo=; b=ATHUKv3Frq9ouPES1p/Y9olubAxiA/ENhTKDfMKMQ0vqZcL8HY+mLE4Iu9SB49BNOy rqUnkkGCdCf8lRvnO1TGsWG0KWSgH/4iH4GXmL2Wc/fCdMQ7XFrcE8NGpOPS0fz2gNcD hBtOO8iHM47wsZ4UCfYEN4DWdRXKOzz4/pZX4bY2DJZUVEOk+ZNYyNx/V7PK/v2WSWyG amqDFAwgklfTHH+hpnhO34r6v4ivX/cbudeNQUwjqE2AN7ZOHv/FaYyb+kiPV69IOW41 P8Kl80ISxbcxl33DLm3JlqZuEAtVoOu/4EnA0j3aCQxK93Mon1iWn87lwdR6BFSA07J3 F1Vw== X-Gm-Message-State: AJaThX7RUS3zOrp7v6tgMHwGc01kc4INligYlE5F6Zkz2empHsS78Rxo 0OJTfArnXSfAVc62CghxA+1q3J1YX5viR5oTYFs50Q== X-Google-Smtp-Source: AGs4zMZWLqei0QglGqcmvtvou69CaZk0hrLaN8pmeekQGdMkQcOSMT61mZzcvLz9R8XIDzTgdOdJbdwrEeTTbJHtSrM= X-Received: by 10.107.104.18 with SMTP id d18mr31064015ioc.136.1512575683744; Wed, 06 Dec 2017 07:54:43 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Wed, 6 Dec 2017 07:54:42 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Wed, 6 Dec 2017 08:54:42 -0700 X-Google-Sender-Auth: aKwSj-kjyF1sF-m7M6Y9vxmrh2I Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 15:54:45 -0000 On Wed, Dec 6, 2017 at 8:35 AM, Thomas Laus wrote: > Group: > > I updated my amd64 computer today to r326622 and copied the > /boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The > BTX loader stopped and could not load. This rendered my system > 'un-bootable'. I copied this file from an earlier live filesystem CD, > which restored my computer and enabled me to boot. > Any chance you can bisect when this happened? I think I'll need more details to see what happened. What was your old loader that world based on? > I also see the problem with the loader logs dumping core that others > have reported recently. > I've not seen these reports, nor do I see if on my loader testing. More details please? Last I had heard, everything was working... Warner From owner-freebsd-current@freebsd.org Wed Dec 6 16:48:07 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FAE6E85258 for ; Wed, 6 Dec 2017 16:48:07 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.227]) (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 5BAB1792F6 for ; Wed, 6 Dec 2017 16:48:06 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id McsseFASJTp7WMcsveDAeG; Wed, 06 Dec 2017 16:49:26 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB6Gm13Y001083 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Dec 2017 11:48:01 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB6Gm1pG001082; Wed, 6 Dec 2017 11:48:01 -0500 (EST) (envelope-from lausts) Date: Wed, 6 Dec 2017 11:48:01 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171206164801.GA1055@mail.laus.org> Reply-To: lausts@acm.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfL+lAZzjThwUxO9hMPaGgcpT0xRZ+S8yH1aGfa+cYtUKw/aRbHuA1HJhoNvabT7OZB02f4uLK0hcSelDDDQB8OOJqXbX0Q5SV5WuyBhkk1P/vLEMOXPf grPSWND/9/yZlA20uXKoq1yxPAjFyIO8KwwZdFrgv0hTXlb2WwC6UjwREZDxOjCse1dsZ4cAHyNsgimXRva87fMWEOzGD77nVKQ= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 16:48:07 -0000 Warner Losh [imp@bsdimp.com] wrote: > > Any chance you can bisect when this happened? I think I'll need more > details to see what happened. What was your old loader that world based on? > My last good gptzfsboot was r326070. I had not built anything since then until this morning when I built world and kernel at r326622. I'll look at the svn history and see where I should start. > > I also see the problem with the loader logs dumping core that others > > have reported recently. > > > > I've not seen these reports, nor do I see if on my loader testing. More > details please? Last I had heard, everything was working... > That was a typo. I had loader on my mind and the core dumps are dealing with logger. I have seen recent messages to this group about logger dumping core and someone is bisecting the issue. I was just reporting that it was still occurring at r326622. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Wed Dec 6 17:28:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98ED3E85FB8 for ; Wed, 6 Dec 2017 17:28:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 58E727A813 for ; Wed, 6 Dec 2017 17:28:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id r6so7987729itr.3 for ; Wed, 06 Dec 2017 09:28:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=UK40P0gYSap52KjOM2ZIk8GyfArviPIttQD6Uz98G/Y=; b=qgpjbuVpjhEVqv4sT5YikrSKgkB0glo1SEn21Y7/KYea5cdaKcnqS0IcIKam0cKJe5 AtB5IxvEdo41BdYUqr91v4MntxnvbYHVREmS73rFH85h9hMuhfgKJYmTJ0t9XaorRmBL IpyuEXoFK5OThYmGqC2VGLtGHIMGTxra2GGcVKbQvMr0gkIN0B8jHg22zi1ub6+w2fvc 9QIGXvXnZDXqDNKSNpRzIKI/1AF9PUcbbRROGFWFNHAc++DTcPtcbW7lMV6+NWzyVKnf +YyJzEIm0CM8iCNZL+bQaGZ/SMir+m6dfKh0vXGEhKyfHQnUMP1xPROIRjX1lXbj64xj v9Xg== 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=UK40P0gYSap52KjOM2ZIk8GyfArviPIttQD6Uz98G/Y=; b=CjOuiLeQC0RJRPqWD6zCTALHlKLA1OGvvxxLTd1cfeZ7JB/FJSmwmDQqjyIewyW47d oRdhCyobMrxU8+MvhyIoBV2hZLaArOcN9dr0w7V2PKURN0/sLD5s7/MMM+5a1KB/+Leq oOaEKSWaDom+26xJHIAfiJVi4brq9P5Q3f8ASIXmlGlBroc19XI0Z+AbmGoc9vcLBSG/ b8AQ8xEPMxM0E6MMgrrMGVR+Eu5b4HvEy9AWWmnredgVfNyCWoUV+sBtIDJqF9L6Ajky rYomyQR/6GwjgJ5/2VsSzmGYz6l7YrjFFPiC0vMxp1CZiUpKLKMses3u2KvZvuv3MrhE hcIg== X-Gm-Message-State: AKGB3mIm1V0Zyux0aZRj6lN2l7/erwYwO8hJr5HXXvflCaL3//q+rMqi itqdpANSe0MnnNxjSq8oVf6fs2+uC2b3CPZMkFbelA== X-Google-Smtp-Source: AGs4zMb/n4C+U1LJrx4qFy4XRyIHX1J6oU9EUDIodYenmSnbDGIyW+4AXSABjIUTAhPe251ETCQLuafXvc4TA45CxTI= X-Received: by 10.36.147.193 with SMTP id y184mr13967520itd.64.1512581301260; Wed, 06 Dec 2017 09:28:21 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Wed, 6 Dec 2017 09:28:20 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171206164801.GA1055@mail.laus.org> References: <20171206164801.GA1055@mail.laus.org> From: Warner Losh Date: Wed, 6 Dec 2017 10:28:20 -0700 X-Google-Sender-Auth: jzLzcaTC_KW-I-Jj4swtYhYB1vA Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 17:28:22 -0000 On Wed, Dec 6, 2017 at 9:48 AM, Thomas Laus wrote: > Warner Losh [imp@bsdimp.com] wrote: > > > > Any chance you can bisect when this happened? I think I'll need more > > details to see what happened. What was your old loader that world based > on? > > > My last good gptzfsboot was r326070. I had not built anything since > then until this morning when I built world and kernel at r326622. > I'll look at the svn history and see where I should start. I've been *VERY* busy between then and now cleaning up the boot loader "accumulated technical debt". Alas, sounds like I've broken something. So I think it's a binary search: I'd start with 326370 as the pivot and 326500 / 326250 as the next steps if it succeeds / fails. So you are seeing a BTX error? Before we even get to running /boot/loader, correct? Any chance you can get me that error? > > I also see the problem with the loader logs dumping core that others > > > have reported recently. > > > > > > > I've not seen these reports, nor do I see if on my loader testing. More > > details please? Last I had heard, everything was working... > > > That was a typo. I had loader on my mind and the core dumps are > dealing with logger. I have seen recent messages to this group about > logger dumping core and someone is bisecting the issue. I was just > reporting that it was still occurring at r326622. Good! One less problem for me to track... Warner From owner-freebsd-current@freebsd.org Wed Dec 6 17:48:34 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85105E87083 for ; Wed, 6 Dec 2017 17:48:34 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.229]) (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 4C8FD7B77B for ; Wed, 6 Dec 2017 17:48:33 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id MdpOeJgHoTp7WMdpReDzMX; Wed, 06 Dec 2017 17:49:53 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB6HmTo1001234 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Dec 2017 12:48:29 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB6HmT3U001233; Wed, 6 Dec 2017 12:48:29 -0500 (EST) (envelope-from lausts) Date: Wed, 6 Dec 2017 12:48:29 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171206174829.GA1204@mail.laus.org> Reply-To: lausts@acm.org References: <20171206164801.GA1055@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfCL99vI3mVjpVXwsvY7KJ6skb/AjtWKAri6dJdSw5za0XqvVu0A5/cDzJ50wURVD7jU2XLGDREv6IPcE6o4cTvLt5gYczkZ3nJfM7wt/pRKeaGpYSUl2 jHp/3TB+72X9wQVIXP9tNqUh99bVAcViAOnhI3sGYx+5dM/2u9LTPSwaUg9rzpMiWim8ZX1AjmKqmO4O+irGgyauR9WKy6vHGdE= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 17:48:34 -0000 Warner Losh [imp@bsdimp.com] wrote: > I've been *VERY* busy between then and now cleaning up the boot loader > "accumulated technical debt". Alas, sounds like I've broken something. So I > think it's a binary search: I'd start with 326370 as the pivot and 326500 / > 326250 as the next steps if it succeeds / fails. > > So you are seeing a BTX error? Before we even get to running /boot/loader, > correct? Any chance you can get me that error? > I get a screen full of register and hex numbers followed by BTX halted. I can do my best to transcribe all of the numbers, but that may be very error prone to do by hand. At this point in the boot process, it is a little hard to fire up a serial console and capture the output to a file. I run Geli encrypted disks and the BTX halt comes even before the prompt for a password. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Wed Dec 6 18:21:40 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D473BE88409 for ; Wed, 6 Dec 2017 18:21:40 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id BBA137D3DA for ; Wed, 6 Dec 2017 18:21:40 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id BAB73E88408; Wed, 6 Dec 2017 18:21:40 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA548E88407 for ; Wed, 6 Dec 2017 18:21:40 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 887047D3D8 for ; Wed, 6 Dec 2017 18:21:40 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id vB6ILd3V045673; Wed, 6 Dec 2017 18:21:39 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id vB6ILdGC045672; Wed, 6 Dec 2017 10:21:39 -0800 (PST) (envelope-from david) Date: Wed, 6 Dec 2017 10:21:39 -0800 From: David Wolfskill To: Maxim Konovalov Cc: current@freebsd.org Subject: Re: logger(1) exited on signal 11 after r326525 -> r326622 Message-ID: <20171206182139.GU41364@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Maxim Konovalov , current@freebsd.org References: <20171206131246.GO41364@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="iBHcHRCIarfY7C0j" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 18:21:40 -0000 --iBHcHRCIarfY7C0j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 06, 2017 at 08:54:52PM +0300, Maxim Konovalov wrote: > Hi David, >=20 > On Wed, 6 Dec 2017, 05:12-0800, David Wolfskill wrote: >=20 > > I noticed among the messages on the console during the final stages of > > the transition from single- to multi-user mode: > > > [...] >=20 > https://lists.freebsd.org/pipermail/svn-src-all/2017-December/154807.html >=20 > --=20 > Maxim Konovalov Thanks for the pointer; that resolved the issue for me. :-) Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is an incompetent, lying bully who is unfit for any public office. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --iBHcHRCIarfY7C0j Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJaKDUzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XFn8H/3K2jhMZ9/Hs3/sw9LzTGOhk LUXhj3vcGs2Prya8OjQ/pNfXLQv+gfZabLHB3r7M5z4gaZx5AWntd7F6E0gXPueg 5kqV5XgIE4MQzLYKN3tJDkJ2OpluBhyVCAU0oOSBRzreYonc1UJ1D1e9yKozefkw +hc2GL8LOlayUmv0kzhuLbw5XbLd1zjjt7hB0zw2yB/OQo8q8G1m8fLgb5bfhQ56 MqWg0Z3xhKcMafPcQ3N6xiSRK/Qt6Cdx8UGrYq4RxtAQ0nXy5vClNUOJYZm1/JSa +0CP4PWjoBBS3RsoYl88mCTmDhq6qsTBLEopb+rAfzdzCx0mezE29zc3KDmyM6A= =hb8d -----END PGP SIGNATURE----- --iBHcHRCIarfY7C0j-- From owner-freebsd-current@freebsd.org Wed Dec 6 22:04:14 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3EF71E8D40B; Wed, 6 Dec 2017 22:04:14 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:a:dead:bad:faff]) (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 028D564311; Wed, 6 Dec 2017 22:04:13 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id vB6M4CXC026346; Wed, 6 Dec 2017 22:04:12 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id vB6M4B03026339; Wed, 6 Dec 2017 22:04:11 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201712062204.vB6M4B03026339@donotpassgo.dyslexicfish.net> Date: Wed, 06 Dec 2017 22:04:11 +0000 Organization: Dyslexic Fish To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org, by@meetlost.com Cc: jamie@catflap.org Subject: Re: Strange behavior about pattern matching on manual pages [FIXED] References: <620CD9B7-201A-46FD-8C9D-DD8DDA3A05C3@meetlost.com> In-Reply-To: <620CD9B7-201A-46FD-8C9D-DD8DDA3A05C3@meetlost.com> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Wed, 06 Dec 2017 22:04:12 +0000 (GMT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 22:04:14 -0000 by wrote: > Hi, > > I encounter a problem when viewing manuals via man(1) command. > > The case is simple, when I try to search something, I press ‘/’, and then input the pattern, If it got something in the page, it will direct me into the specified place, and then, I continue with ’n’, and it goes well. > But the problem is, after a sequence of ’n’, the screen go to the end of the manual pages, and keeping press ’n’, I got annoying “...skipping...”, the page is full of skipping and parts of the end of the manual page. Yes. This has been annoying me too - your email prompted me to finally work on a fix for it! Firstly, it isn't man(1) itself - man(1) uses more(1) as the pager. more(1) is in itself actually the program less(1), running in "more emulation mode". And less(1) isn't FreeBSD native code - it's imported into the project from http://www.greenwoodsoftware.com/less/ I noticed the very latest version of less(1) has been checked into freebsd-current, and the issue still occurs there. Anyway, the fix is two small patches to less(1), please let me know if they work for you, and if you see any bad side-effects in man(1) / more(1) and less(1) and I'll then try and get them applied upstream. The patches have been tested against FreeBSD 11.1-STABLE and 12-CURRENT cheers! Jamie --- contrib/less/forwback.c.orig 2017-11-20 08:52:33.978356000 +0000 +++ contrib/less/forwback.c 2017-12-05 15:53:50.517550000 +0000 @@ -255,7 +255,7 @@ * start the display after the beginning of the file, * and it is not appropriate to squish in that case. */ - if ((first_time || less_is_more) && + if ((first_time) && pos == NULL_POSITION && !top_scroll && #if TAGS tagoption == NULL && --- contrib/less/main.c.orig 2017-11-20 08:52:33.978356000 +0000 +++ contrib/less/main.c 2017-12-05 15:53:57.291394000 +0000 @@ -168,7 +168,10 @@ } if (less_is_more) + { no_init = TRUE; + scan_option("--tilde"); + } #if EDITOR editor = lgetenv("VISUAL"); From owner-freebsd-current@freebsd.org Wed Dec 6 22:04:26 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFC9FE8D44A; Wed, 6 Dec 2017 22:04:26 +0000 (UTC) (envelope-from laurent@nuxi.ca) Received: from mail.nuxi.ca (nuxi.ca [142.44.162.10]) by mx1.freebsd.org (Postfix) with ESMTP id AD4EC64455; Wed, 6 Dec 2017 22:04:26 +0000 (UTC) (envelope-from laurent@nuxi.ca) Received: from [192.168.0.174] (modemcable058.143-202-24.mc.videotron.ca [24.202.143.58]) (Authenticated sender: laurent) by mail.nuxi.ca (Postfix) with ESMTPSA id 87FD320967; Wed, 6 Dec 2017 16:54:37 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: rpi2 hangup during poudriere build: lots of pfault wmseg status From: Laurent Cimon In-Reply-To: <05BEA04B-249B-4E7D-855A-46DA1A0DEA16@dsl-only.net> Date: Wed, 6 Dec 2017 16:54:36 -0500 Cc: freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <05BEA04B-249B-4E7D-855A-46DA1A0DEA16@dsl-only.net> To: Mark Millard X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 22:04:26 -0000 > On Dec 6, 2017, at 00:57, Mark Millard wrote: >=20 > I tried to build some ports on a rpi2 > (via poudriere) but it hung up: > Ethernet and normal console use. (Note: > the root file system is on a USB SSD > and the swap partition is also on that > USB SSD.) >=20 > But ~^b worked for getting to the db> > prompt on the console. >=20 > =46rom there a ps suggests that it got hung > up in pfault activity. (Possibly insufficient > RAM+swap-partition space?) But it is not > clear to me that it should end up hung up > vs. killing processes or other such. Hi, =46rom what I know the raspberry pis use the same controller for = ethernet and the USB hub on which you=E2=80=99re hosting an SSD. It seems like you = make very heavy use of the USB ports, and all of the resources used by poudriere except = for the CPU and the (very limited) memory that=E2=80=99s not in swap is attached = to them. If you really didn=E2=80=99t have enough memory and swap, the linkers = would=E2=80=99ve been stopped. I think it might just be a swap death. Poudriere compiles and fetches in = parallel a lot, ethernet and disk I/O is slow because it=E2=80=99s very limited, = so linking takes longer. You end up linking a few very big binaries at the same time, and = they all fight for the memory, to get out of swap through page faults, but = there are too many page faults, all too big, requesting for more CPU time = that=E2=80=99s allowed to them. This would explain why you have 3 linkers waiting on a page fault out of = the 4 CPUs poudriere allows builds on, on top of the awk processes. It would = also explain why you had easy access to the debugger: it was in memory = already with the kernel. I=E2=80=99d advise you to disable parallel builds and see if it happens = again, but it would make building much slower. Using makejobs would help if you can afford watching the build. Otherwise be patient, it should resolve = itself eventually, but it will take a while and it will happen again. Good luck, Laurent= From owner-freebsd-current@freebsd.org Wed Dec 6 22:22:01 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1088FE8DFA6 for ; Wed, 6 Dec 2017 22:22:01 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) (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 CB6B965276 for ; Wed, 6 Dec 2017 22:22:00 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id Mi61ecJCATp7WMi63eHQZ2; Wed, 06 Dec 2017 22:23:20 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB6MLtt0001804 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Dec 2017 17:21:55 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB6MLtUi001803; Wed, 6 Dec 2017 17:21:55 -0500 (EST) (envelope-from lausts) Date: Wed, 6 Dec 2017 17:21:55 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171206222155.GA1792@mail.laus.org> Reply-To: lausts@acm.org References: <20171206164801.GA1055@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfOyFro8skG7TAuUYYjZyKFAV5cOJ0bvHMFOUtsKcYgZx2t7PKnDKx7ue1SP1c775fYDSKqqEtY20jeX1nyiP9fS7V1nS3oESe+XHc3XNCb/L3lR+4lvL SC8/tjYdvYjO1Qd427/C4EKByKMeVuFgysj389bfQ+s1UQFl6msLPn31Bfoq0XJtLcBbHNQ/SIipVamT86t8o18kd/5IdIMa9xE= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 22:22:01 -0000 Warner Losh [imp@bsdimp.com] wrote: > I've been *VERY* busy between then and now cleaning up the boot loader > "accumulated technical debt". Alas, sounds like I've broken something. So I > think it's a binary search: I'd start with 326370 as the pivot and 326500 / > 326250 as the next steps if it succeeds / fails. > Warren: I reverted my system to r326370 and it booted normally. It looks like something broke after that revision. I'll cue up another buildworld after updating the system to r326500. I received a couple of suggestions to take a picture and post my console screen of the BTX fault. My camera battery has died and is on the charger for a while. I'll build r326500 and post a picture if it shows the same BTX issue. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Wed Dec 6 22:23:41 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51440E8E1C7; Wed, 6 Dec 2017 22:23:41 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x241.google.com (mail-lf0-x241.google.com [IPv6:2a00:1450:4010:c07::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C79216546A; Wed, 6 Dec 2017 22:23:40 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x241.google.com with SMTP id f20so6001013lfe.3; Wed, 06 Dec 2017 14:23:40 -0800 (PST) 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=APkbrG3xZofywJ8qjIraM1jtmVUZ+pJLVuPWHilzzKI=; b=Lh8lp1s2d4t/cG1Hed9rbBezIpQpLfS7tlHIJ+/rLC3/inOXdGm/3uwyt5OO9W2AAs SsMJ36SmCQ83a3+hKcLkbWjaIy2ViekwF3oBX0tMu5SFbGpMHMQ1r1v9+VeeBfM42n57 q87YqOiYFrPiOp4HXfweWhol4YgrjMrPXjY+3UCUKLcENhwQyzaOf2CO1MgofxOLdno7 Gzigd5Jg3K6XTAPQBlw18nWhdgzAuJNbPvI8p6HCe/QqlapvmP2QJRWzyHQaWbme+6Na sH9KX/Vw7W/AQ+c8iFft9EgvJJ+E7j29uokIAyfsAXC4dm7LKhBe/u49BQkM1iYs6XJV e4KA== 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=APkbrG3xZofywJ8qjIraM1jtmVUZ+pJLVuPWHilzzKI=; b=RpWHW6o71E3JVg0VPqKwfMAzlQ+qZ6MIAptuAvLka6lQoR0GmhcsBkvXsgql5tsPNw F87C8dWIOMiOv/SKd7RLGJ0Da9X7X0ITJuhUSTqCiCRn8gLsfJQsvZFWy6iNG9q92wsk YZ/DQ032W8EwgqO5mxbSzWBwcYEMIxAVK41b7P0TDGBKLPU+Q2xoWCFuLzvETZMR5NUV lDJ85SOskasD5EbB7ZePnRUjt7cVbwYTenvuu5933atyUbrvXpYeqKSgKdxWRZ9wyFRB jJfuVk1Tyzqz0u9DhitkN0jcSDvd8g/QHz4dR/vUPWTKmkcqwp732O9XjgEckD02XihY Yxrw== X-Gm-Message-State: AJaThX6nZKZyTIsW0PDv/zUjR1AE0jYsPH3K+iMIJmjq99J/ClK0vfTM Vr0e8tHZsPVB8J5BqRpGv6mv4XHqHgTcDhtNR3g= X-Google-Smtp-Source: AGs4zMbXTfM91peHPELjflGn3rKilQ5QJdTOlY6/DAkYeqeKM1j+Wg7Mfx5adwHvqp6s1LzlFxj4uT87ToYpC7AfwKM= X-Received: by 10.25.27.18 with SMTP id b18mr10864510lfb.177.1512599013965; Wed, 06 Dec 2017 14:23:33 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.76.19 with HTTP; Wed, 6 Dec 2017 14:23:33 -0800 (PST) In-Reply-To: <201712062204.vB6M4B03026339@donotpassgo.dyslexicfish.net> References: <620CD9B7-201A-46FD-8C9D-DD8DDA3A05C3@meetlost.com> <201712062204.vB6M4B03026339@donotpassgo.dyslexicfish.net> From: Alan Somers Date: Wed, 6 Dec 2017 15:23:33 -0700 X-Google-Sender-Auth: PbHdgm82FpjFJisFwVRSJ66iRhc Message-ID: Subject: Re: Strange behavior about pattern matching on manual pages [FIXED] To: Jamie Landeg-Jones Cc: FreeBSD CURRENT , "freebsd-hackers@freebsd.org" , by@meetlost.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 22:23:41 -0000 On Wed, Dec 6, 2017 at 3:04 PM, Jamie Landeg-Jones wrote: > by wrote: > > > Hi, > > > > I encounter a problem when viewing manuals via man(1) command. > > > > The case is simple, when I try to search something, I press =E2=80=98/= =E2=80=99, and > then input the pattern, If it got something in the page, it will direct m= e > into the specified place, and then, I continue with =E2=80=99n=E2=80=99, = and it goes well. > > But the problem is, after a sequence of =E2=80=99n=E2=80=99, the screen= go to the end of > the manual pages, and keeping press =E2=80=99n=E2=80=99, I got annoying = =E2=80=9C...skipping...=E2=80=9D, > the page is full of skipping and parts of the end of the manual page. > > Yes. This has been annoying me too - your email prompted me to finally wo= rk > on a fix for it! > > Firstly, it isn't man(1) itself - man(1) uses more(1) as the pager. > more(1) is in itself actually the program less(1), running in "more > emulation mode". > > And less(1) isn't FreeBSD native code - it's imported into the project > from http://www.greenwoodsoftware.com/less/ > > I noticed the very latest version of less(1) has been checked into > freebsd-current, and the issue still occurs there. > > Anyway, the fix is two small patches to less(1), please let me know > if they work for you, and if you see any bad side-effects in man(1) / > more(1) and less(1) and I'll then try and get them applied upstream. > > The patches have been tested against FreeBSD 11.1-STABLE and 12-CURRENT > > cheers! Jamie > > --- contrib/less/forwback.c.orig 2017-11-20 08:52:33.978356000 +00= 00 > +++ contrib/less/forwback.c 2017-12-05 15:53:50.517550000 +0000 > @@ -255,7 +255,7 @@ > * start the display after the beginning of the file, > * and it is not appropriate to squish in that case. > */ > - if ((first_time || less_is_more) && > + if ((first_time) && > pos =3D=3D NULL_POSITION && !top_scroll && > #if TAGS > tagoption =3D=3D NULL && > --- contrib/less/main.c.orig 2017-11-20 08:52:33.978356000 +0000 > +++ contrib/less/main.c 2017-12-05 15:53:57.291394000 +0000 > @@ -168,7 +168,10 @@ > } > > if (less_is_more) > + { > no_init =3D TRUE; > + scan_option("--tilde"); > + } > > #if EDITOR > editor =3D lgetenv("VISUAL"); > > How about just setting MANPAGER=3Dless in your environment? From owner-freebsd-current@freebsd.org Wed Dec 6 22:31:09 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1B20E8E563 for ; Wed, 6 Dec 2017 22:31:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F12B65913 for ; Wed, 6 Dec 2017 22:31:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22e.google.com with SMTP id r6so10000585itr.3 for ; Wed, 06 Dec 2017 14:31:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=m5UGhhAqvwwvhu6BAp9ZzLE5YDpHMYf4Mq68OaTfvhs=; b=kCdyPqQXaAEKZoLLeSsfVlNObAg8TMLMwbICas+LNrMlETsYBebtMv3N5XLTODEgGT BEKNvdNl2J93iTWGdY1AhubP4SWfahbru5vtS565EpoHB2A8xp3mqY9qeGaxl+cb0MI6 y4p9II6fQQ25wrhwtbwH3yRXkjeRedy3Y6SfCgFRSsAYhJlA9QdEodQAqeTOTTLh4LXE pOV+9iIje9B9aOZGnnWqo2mygpiIuRGBrO5kH9FGIrIR15ChZBZ/1qzZCACImuVuR8u/ skjdviJcZZ6W+XkUDoRZipQSGdwUM2iHoYiI2TMyWqkYKKa+5hQ8RzgY1PNXJf3yUr8K 1HlQ== 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=m5UGhhAqvwwvhu6BAp9ZzLE5YDpHMYf4Mq68OaTfvhs=; b=kV/xNC/NSK4IKR9VuhUysVV2uLW/xlWM0tQGnlUHiAWiAujY0oI36a59Zk3coLD5er lHFPZhXmhHoH+NhIj4FzJ/htcDn0oWL8Zgco+UEgXbXArZp+0KPWECNkrRw5302r+G4L tvh51IAyISkQKoBs1w04QRHCqk0M1TuVzhF/WANpNf1y4YsYrbbYehzKUmkwgy+N9cjq 7yqCBZmOzphnUvBbvVP6TuSq2nLafHesVzvSrj3iWW29JGtFLREYqJ136p3Qv5CdNV0C P+gESrRnUGSU8+GNsCXIl/sA5XJqDHBhjd6Oupz9EZB8dQFtrjmXINyvDrig8PtgeAeA 6Pqw== X-Gm-Message-State: AJaThX4Eh5WaUJPay3k8TdMs5YRppsHam0zhVDw1b0oPXXjfVTDnPFK3 mRJlZkS06JBvHvZISz3IygjJI8OwiL01mhc23wWT9Q== X-Google-Smtp-Source: AGs4zMatrmNndCBvbIztiNFOPqbW3ADLZIuqtupMHEoJLHqqye6NWN7o3BOqwVzzkJ1p10YX8XdMJppfqtMZPRnaJV8= X-Received: by 10.107.30.81 with SMTP id e78mr33803025ioe.130.1512599463500; Wed, 06 Dec 2017 14:31:03 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Wed, 6 Dec 2017 14:31:02 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171206222155.GA1792@mail.laus.org> References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> From: Warner Losh Date: Wed, 6 Dec 2017 15:31:02 -0700 X-Google-Sender-Auth: rdmWdGoEfKpAqpDSbpgNKDtEuVU Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 22:31:09 -0000 On Wed, Dec 6, 2017 at 3:21 PM, Thomas Laus wrote: > Warner Losh [imp@bsdimp.com] wrote: > > I've been *VERY* busy between then and now cleaning up the boot loader > > "accumulated technical debt". Alas, sounds like I've broken something. > So I > > think it's a binary search: I'd start with 326370 as the pivot and > 326500 / > > 326250 as the next steps if it succeeds / fails. > > > Warren: > > I reverted my system to r326370 and it booted normally. It looks like > something broke after that revision. I'll cue up another buildworld > after updating the system to r326500. > > I received a couple of suggestions to take a picture and post my > console screen of the BTX fault. My camera battery has died and is on > the charger for a while. I'll build r326500 and post a picture if it > shows the same BTX issue. You can just build the boot blocks at each step if you'd like to save some time on the binary search. cd stand make cleandir obj depend make -j XX sudo -E make install should suffice. There's no compiler dependency that I'm aware of. Warner From owner-freebsd-current@freebsd.org Wed Dec 6 22:35:50 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 004B6E8E86D; Wed, 6 Dec 2017 22:35:50 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:a:dead:bad:faff]) (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 BE8F765E83; Wed, 6 Dec 2017 22:35:49 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id vB6MZmlY034659; Wed, 6 Dec 2017 22:35:48 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id vB6MZlQv034650; Wed, 6 Dec 2017 22:35:47 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201712062235.vB6MZlQv034650@donotpassgo.dyslexicfish.net> Date: Wed, 06 Dec 2017 22:35:47 +0000 Organization: Dyslexic Fish To: jamie@catflap.org, asomers@freebsd.org Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, by@meetlost.com Subject: Re: Strange behavior about pattern matching on manual pages [FIXED] References: <620CD9B7-201A-46FD-8C9D-DD8DDA3A05C3@meetlost.com> <201712062204.vB6M4B03026339@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Wed, 06 Dec 2017 22:35:48 +0000 (GMT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 22:35:50 -0000 Alan Somers wrote: > How about just setting MANPAGER=less in your environment? Because some of us prefer "more"? And as I said, it's related to searching using the more(1) command generally. I was under the impression that fixing bugs in existing commands was a better solution than telling someone to simply use something else. From owner-freebsd-current@freebsd.org Wed Dec 6 22:53:52 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AC43E8EFDA; Wed, 6 Dec 2017 22:53:52 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7CFC76692C; Wed, 6 Dec 2017 22:53:51 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id x20so6075711lff.1; Wed, 06 Dec 2017 14:53:51 -0800 (PST) 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=4WXC7h69CzMO1gwH2Rw5KbMmhC4SIBd3aGKANq5T/9Y=; b=u86CjR2RyZwFDjw/ZONYFRn/0kmOCHIbZzE/NKYdsjx7KaDMdWbRFfKaCVihMvAdOM TYPChf3ZqNCpgvKrYKbdj5RuJvFf8x1HHbqGM4DHjEgqC3OmNs1qo4fiGG3sR7RqTwNo ZEZfgtzJT/UzM6c7YjjzxGpmO9eNLscxbFzFnsiw5Y0g4y8sVhN8MpHnnYHHpGKEzOQJ vaPvB8Ia/1uSHivFORLV2N/0Ak3YtIb+8jgvaPDtJJuvIIR8/FAHdfKmZB+yalKxxoaX a0lGFK1DzBXTh+s7B9MRww2eNYz3BBv/Y7U+gnMJgesZ304zf5meACS8mJQZ3oSEM4Wt gqBA== 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=4WXC7h69CzMO1gwH2Rw5KbMmhC4SIBd3aGKANq5T/9Y=; b=Kq37Rx+injsY9v42xEa6AUiDe9jHw/eEJeYzeRjmgQEPmZ+cumq/GH56D/tKL7jWwC tr03ibjPBW5B4uJYcN7FhVV1ln4DEsGMYG/APgH3R4OzkSFqrKam5QDwoLyCjP+IowCh /OMMAd6nc5Y9OcRNPPU3g2D33WxjGB2gRRFpEtwvUWJihpWVx/uj/JEZeGNdkBFRyYwX dUaCdVC83XfizRe/t9RRl91d8aHVclvfxpWjfX2xJAUjAGm+ZuxIy7h14XnUqHZWTZ4R I/TyyPu+q/Ys/EtLM6iMzuw0MvNakQExJ2S9cGuVZ7zmQZKlwoLm7QYPlAoVWhZF0HRI 9fPQ== X-Gm-Message-State: AJaThX6KHcoa3xGTMvlCZbxrSHRrtVVgQ7qWjTDT/T4uA3XSAVNBBf0n 6ZQ1EyRGeWu4oJAhoWnwDL9qZsnkBmujr77lOlQ= X-Google-Smtp-Source: AGs4zMbbDEmW4tflTzEVzUMY8MOiHdoNJhxHo+VYilQR9fGG1ZTbOPP4rixW8WONz8KU5Pcb/uGBy4aLdKp3TcbJhi8= X-Received: by 10.25.27.18 with SMTP id b18mr10885802lfb.177.1512600824619; Wed, 06 Dec 2017 14:53:44 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.76.19 with HTTP; Wed, 6 Dec 2017 14:53:44 -0800 (PST) In-Reply-To: <201712062235.vB6MZlQv034650@donotpassgo.dyslexicfish.net> References: <620CD9B7-201A-46FD-8C9D-DD8DDA3A05C3@meetlost.com> <201712062204.vB6M4B03026339@donotpassgo.dyslexicfish.net> <201712062235.vB6MZlQv034650@donotpassgo.dyslexicfish.net> From: Alan Somers Date: Wed, 6 Dec 2017 15:53:44 -0700 X-Google-Sender-Auth: Nytb_VP6cwKrILV9mWvqZO4iNwg Message-ID: Subject: Re: Strange behavior about pattern matching on manual pages [FIXED] To: Jamie Landeg-Jones Cc: "freebsd-hackers@freebsd.org" , FreeBSD CURRENT , by@meetlost.com Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 22:53:52 -0000 On Wed, Dec 6, 2017 at 3:35 PM, Jamie Landeg-Jones wrote: > Alan Somers wrote: > > > How about just setting MANPAGER=less in your environment? > > Because some of us prefer "more"? > > And as I said, it's related to searching using the more(1) command > generally. > > I was under the impression that fixing bugs in existing commands was a > better > solution than telling someone to simply use something else. > Yes, it certainly is. Are you sure this is actually a bug in less, or is it just weird-but-intended behavior when less is emulating some old version of more? It would be worth comparing our less sources to upstream's to see what differences have crept in, and svn blaming them to see why. -Alan From owner-freebsd-current@freebsd.org Wed Dec 6 23:32:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8042E9033F for ; Wed, 6 Dec 2017 23:32:53 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) (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 802BA684E9 for ; Wed, 6 Dec 2017 23:32:52 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id MjBIep3gsj1UsMjBKehXJI; Wed, 06 Dec 2017 23:32:51 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB6NWlw8001967 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Dec 2017 18:32:47 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB6NWlYN001966; Wed, 6 Dec 2017 18:32:47 -0500 (EST) (envelope-from lausts) Date: Wed, 6 Dec 2017 18:32:47 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171206233247.GA1948@mail.laus.org> Reply-To: lausts@acm.org References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfAG5qXBe8Ir0xC9Qj/oEaVeB/evCfL4/kzk9OjAchBLP/3MqvABx0pEg0w9JAUgdYqDtYzhWRn/Cd680ZhdGz4iiXwlN4/Ocg+d/+rctiQ/MVyNF4kJg Gona6p2M6W4aMS4h0zmJNOH0zeD19WQ8KeInWo4Nxs9K8I7KxAkxVrhv71bxZUczcGj3kcMKS3yc5soljC2r2bOP9LAQW6/EE6w= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 06 Dec 2017 23:32:53 -0000 Warner Losh [imp@bsdimp.com] wrote: > > You can just build the boot blocks at each step if you'd like to save some > time on the binary search. > > cd stand > make cleandir obj depend > make -j XX > sudo -E make install > > should suffice. There's no compiler dependency that I'm aware of. > I have started another buildworld. I should probably let it run to completion and then test whether it boots. Thanks for the suggestion on further builds. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Thu Dec 7 00:17:30 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D84B3E9153A for ; Thu, 7 Dec 2017 00:17:30 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.232]) (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 A167D69CAF for ; Thu, 7 Dec 2017 00:17:29 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id MjsPerqYij1UsMjsRehwhT; Thu, 07 Dec 2017 00:17:23 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB70HKvx002076 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Dec 2017 19:17:20 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB70HKVf002075; Wed, 6 Dec 2017 19:17:20 -0500 (EST) (envelope-from lausts) Date: Wed, 6 Dec 2017 19:17:20 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171207001720.GA2058@mail.laus.org> Reply-To: lausts@acm.org References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfDw7w0ZKp4gWW/r160CPrieSBggZ8sV+zA6+ZWjXLCVxVM6+dsuDeqv39LAwjM5DZwjEarIb+K6re7xYy0S8Xxfj4vzRnJt+7QhC0ujLqOob46frAoDW Vh9nMRY3Ej8YC5wXl8tYPyQv+xI9Lnys+xGqF15Evfyllp6mRej/gqK4Xc+NKaPDnxh0/TB4YiJN/B7yGcYQz0NwPFfzaMoj1ec= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 00:17:30 -0000 Warner Losh [imp@bsdimp.com] wrote: > You can just build the boot blocks at each step if you'd like to save some > time on the binary search. > > cd stand > make cleandir obj depend > make -j XX > sudo -E make install > Warren: I built and loaded r326500 successfully. It looks like the problem is after r326500 and before r326662. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Thu Dec 7 00:38:23 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C069AE92163 for ; Thu, 7 Dec 2017 00:38:23 +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 G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 307426AC57 for ; Thu, 7 Dec 2017 00:38:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x234.google.com with SMTP id b5so10794426itc.3 for ; Wed, 06 Dec 2017 16:38:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=g5q7XyuMrVXHTmbWJe12Tg7pZtDCcDzLlghjVdoemGA=; b=dz6+ysUtj33HbZfuvvrMU/bCYqfdI8nvLhYn+uT/55ZtpDNcRGctSXkWcoSXUZHWyR 23yCYDPyamrFJFg+5iqybh11xZYKd8zvfNMvZMSJQbRTiUaPhutOY478dwyK4ovDftP/ qvX+9X8ffCq9gfU7dWKc1/25TNuVSuzzotXrhfFmXOjyPnnadU6w6lsh15k0V2azGN++ zcAhgfBy5b8jAZRwRl/R6cpsN02Z4LqEUKWMnt1hZrsngNMGj11QQqhYNHPvYONySzbF 1qaRMy0eipbSvaw2SjLtodBepGMMzz4y8Tm6fD4DrEoxuoSoz8amZAmZy31TEcqtPhuF WP+Q== 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=g5q7XyuMrVXHTmbWJe12Tg7pZtDCcDzLlghjVdoemGA=; b=Tk45nujofp0YaxjMx/Nzv8zn3+7zzrroDX3fmJ/xPkO5kB0Qguk2OoV+LE9/hn9S7P lVD/hfPgLcYA0pAMMmSqz6ihO+YT0nRpNPFK9QYwwDwr2b4DcO4DGiXnMNcshfURK+g5 OvWNk3HVJ0u/ugkTO2ENCcPd/83BkWR2FoyIqG1Ma+KhUe4Bv6zHDZM4yrGj3w04PNIF 2Xk4JQ04n/HgDnW6NugUNnZSFjCwDHVFPi/B+LGzUIkkE9usrKhw6jMYInaQ/817Cyb+ zPL9GCYoyedFwz/2TarFpqiQaF8OFLqVs7pLzF95yL7MNyQqlHrVVe0SJCA5Mj/rivD9 OMdg== X-Gm-Message-State: AJaThX5NqJL6towiIDMtijqjzThYx9jOUS1fgqL57br16Idi0v6gtgYK 5Mt2zujvmplTP598r4CerYeRHbI6tWMblIu+6jY67A== X-Google-Smtp-Source: AGs4zMavnVbcwVyYD+Zxr6yj7j5OXA67pZnzW0yJdDRu7Ks5a0+RgkqwDg6p3Ol1Jnun20fqkmD4mYgHYEDeapUNzHQ= X-Received: by 10.107.81.24 with SMTP id f24mr34711985iob.63.1512607102278; Wed, 06 Dec 2017 16:38:22 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Wed, 6 Dec 2017 16:38:21 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171207001720.GA2058@mail.laus.org> References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> From: Warner Losh Date: Wed, 6 Dec 2017 17:38:21 -0700 X-Google-Sender-Auth: wIkDxUWxPhseV0JT1l7rW8Iq3Zs Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 00:38:24 -0000 On Wed, Dec 6, 2017 at 5:17 PM, Thomas Laus wrote: > Warner Losh [imp@bsdimp.com] wrote: > > You can just build the boot blocks at each step if you'd like to save > some > > time on the binary search. > > > > cd stand > > make cleandir obj depend > > make -j XX > > sudo -E make install > > > Warren: > > I built and loaded r326500 successfully. It looks like the problem is > after r326500 and before r326662. OK. Still a fair number of changes, including changes to geli to fix warnings... 326585-326594 is a flurry of changes. Then another in the 326609-326610 range. There's one other trivial one. I'd wager that if '500 works, the breakage will be somewhere in the first range, which suggests 326590 might be a good, next pivot. There's also a few just after '500 that might break things as well if I messed something up. '504 and '507 both touch this stuff directly... Good luck! Warner From owner-freebsd-current@freebsd.org Thu Dec 7 01:01:45 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC4EAE92F47 for ; Thu, 7 Dec 2017 01:01:45 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-128.reflexion.net [208.70.210.128]) (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 7B5966BF3B for ; Thu, 7 Dec 2017 01:01:44 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29089 invoked from network); 7 Dec 2017 01:01:38 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 7 Dec 2017 01:01:38 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Wed, 06 Dec 2017 20:01:38 -0500 (EST) Received: (qmail 11093 invoked from network); 7 Dec 2017 01:01:38 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 7 Dec 2017 01:01:38 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id D0409EC861A; Wed, 6 Dec 2017 17:01:37 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: rpi2 hangup during poudriere build: lots of pfault wmseg status From: Mark Millard In-Reply-To: Date: Wed, 6 Dec 2017 17:01:36 -0800 Cc: freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <36A8BDCC-4ECE-4187-8705-54A9E38E8AD5@dsl-only.net> References: <05BEA04B-249B-4E7D-855A-46DA1A0DEA16@dsl-only.net> To: Laurent Cimon X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 01:01:45 -0000 On 2017-Dec-6, at 1:54 PM, Laurent Cimon wrote: >> On Dec 6, 2017, at 00:57, Mark Millard = wrote: >>=20 >> I tried to build some ports on a rpi2 >> (via poudriere) but it hung up: >> Ethernet and normal console use. (Note: >> the root file system is on a USB SSD >> and the swap partition is also on that >> USB SSD.) >>=20 >> But ~^b worked for getting to the db> >> prompt on the console. >>=20 >> =46rom there a ps suggests that it got hung >> up in pfault activity. (Possibly insufficient >> RAM+swap-partition space?) But it is not >> clear to me that it should end up hung up >> vs. killing processes or other such. >=20 > Hi, >=20 > =46rom what I know the raspberry pis use the same controller for = ethernet and > the USB hub on which you=E2=80=99re hosting an SSD. It seems like you = make very heavy > use of the USB ports, and all of the resources used by poudriere = except for the > CPU and the (very limited) memory that=E2=80=99s not in swap is = attached to them. If you > really didn=E2=80=99t have enough memory and swap, the linkers = would=E2=80=99ve been stopped. >=20 > I think it might just be a swap death. Poudriere compiles and fetches = in parallel > a lot, ethernet and disk I/O is slow because it=E2=80=99s very = limited, so linking takes > longer. You end up linking a few very big binaries at the same time, = and they > all fight for the memory, to get out of swap through page faults, but = there > are too many page faults, all too big, requesting for more CPU time = that=E2=80=99s > allowed to them. >=20 > This would explain why you have 3 linkers waiting on a page fault out = of the 4 > CPUs poudriere allows builds on, on top of the awk processes. It would = also > explain why you had easy access to the debugger: it was in memory = already with > the kernel. >=20 > I=E2=80=99d advise you to disable parallel builds and see if it = happens again, > but it would make building much slower. Using makejobs would help if = you > can afford watching the build. Otherwise be patient, it should resolve = itself > eventually, but it will take a while and it will happen again. My post was more about how FreeBSD handled the heavy-use context and less about getting the builds to finish: it managed to to get to a state of no-progress for processes and a loss of normal control as far as I could tell. I did a "c" to ddb and left it until just before this note then did ~ ^B again. Things looked the same. [I've finally rebooted the rpi2.] PARALLEL_JOBS=3D1 was already in use but ALLOW_MAKE_JOBS=3Dyes was also in use. USE_TMPFS=3Dno was already in use. While an ssh session was monitoring the build, Ethernet was not in heavy use. (No nfs mounts to its disks, for example.) I may try without ALLOW_MAKE_JOBS=3Dyes and with ALLOW_MAKE_JOBS_PACKAGES empty/undefined to see if it can complete for such a context without having the same sort of problem. Ultimately I can cross-build and install from those materials when I really want updates. I have the context for such. This was more about seeing how well the rpi2 did for self-hosted. Classically I've used a BPI-M3 with 2 GiBytes of RAM and a proportionally bigger swap partition instead (approximately). FYI (rpi2 after rebooting): # swapinfo Device 1K-blocks Used Avail Capacity /dev/label/RPI2swap 1572860 0 1572860 0% # df -m Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/ufs/RPI2rootfs 195378 30791 148957 17% / devfs 0 0 0 100% /dev /dev/label/RPI2Aboot 49 12 37 25% /boot/msdos An rpi3 (aarch64) with the same amount of RAM, same type of USB SSD, etc., but well more swap completed building basically the same set of ports for the same poudriere settings just fine. Interestingly for the default kern.maxswzone: (Just to show the reported recommended maximum figures for swap.) rpi2: . . . exceeds maximum recommended amount (411488 pages). rpi3: . . . exceeds maximum recommended amount (925680 pages). (I was running with somewhat under those maximums for the tests.) # swapinfo Device 1K-blocks Used Avail Capacity /dev/gpt/RPI3swap 3702784 0 3702784 0% # df -m Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/ufs/RPI3rootfs 195378 14937 164811 8% / devfs 0 0 0 100% /dev /dev/label/RPI3Aboot 49 7 42 15% /boot/efi If I restricted the rpi3 to somewhat under what the rpi2 allows for swap, I do not know if it would also hang up vs. not. If having more swap makes the difference, then it would not seem to be being I/O-bound that would explain the hangup. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-current@freebsd.org Thu Dec 7 01:22:51 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3641E94285 for ; Thu, 7 Dec 2017 01:22:51 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.228]) (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 90D006D2F9 for ; Thu, 7 Dec 2017 01:22:50 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id MkqleKfaefiK5MkqneXD1D; Thu, 07 Dec 2017 01:19:46 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB71Mfi0002218 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Dec 2017 20:22:41 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB71MfZr002217; Wed, 6 Dec 2017 20:22:41 -0500 (EST) (envelope-from lausts) Date: Wed, 6 Dec 2017 20:22:41 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171207012241.GA2170@mail.laus.org> Reply-To: lausts@acm.org References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfC8sY+Ne1ZRPjmLg2+DPJVsFRGA8Ozba9mPOHH+30A0q9ptMjIXPO80qOWjWBULLQ/okWyVb1CUx2UIS9a++1F4gmDwCSxagRD+j8qriqAT/PPE+lM1q 7LMQhJ+heIGqbu2aFVoIW9xMCPlo7IHvrs8tsbk4AcZqHCEC0umgXqce5QuokJ9pqY1eLcceRPMtSn2w+oEjuoNpvAsrnlO2VFo= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 01:22:51 -0000 Warner Losh [imp@bsdimp.com] wrote: > > > You can just build the boot blocks at each step if you'd like to save > > > some time on the binary search. > > > > > > cd stand > > > make cleandir obj depend > > > make -j XX > > > sudo -E make install > > > > > OK. Still a fair number of changes, including changes to geli to fix > warnings... > > 326585-326594 is a flurry of changes. Then another in the 326609-326610 > range. There's one other trivial one. I'd wager that if '500 works, the > breakage will be somewhere in the first range, which suggests 326590 might > be a good, next pivot. There's also a few just after '500 that might break > things as well if I messed something up. '504 and '507 both touch this > stuff directly... > Warren: Building just 'stand' had an error in /usr/src/stand/geli concerning geli hmac conflicting type for 'ngets'. I am doing a full buildworld for r326590. It should be complete before 9:30 PM EST. I'll post the results and look for replies tomorrow morning and proceed with the disscetion. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Thu Dec 7 01:47:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80ACDE95830; Thu, 7 Dec 2017 01:47:16 +0000 (UTC) (envelope-from laurent@nuxi.ca) Received: from mail.nuxi.ca (nuxi.ca [142.44.162.10]) by mx1.freebsd.org (Postfix) with ESMTP id 322B06E422; Thu, 7 Dec 2017 01:47:15 +0000 (UTC) (envelope-from laurent@nuxi.ca) Received: from [192.168.0.174] (modemcable058.143-202-24.mc.videotron.ca [24.202.143.58]) (Authenticated sender: laurent) by mail.nuxi.ca (Postfix) with ESMTPSA id 24575209E2; Wed, 6 Dec 2017 20:47:14 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: rpi2 hangup during poudriere build: lots of pfault wmseg status From: Laurent Cimon In-Reply-To: <36A8BDCC-4ECE-4187-8705-54A9E38E8AD5@dsl-only.net> Date: Wed, 6 Dec 2017 20:47:12 -0500 Cc: freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5014B6E6-68BA-4499-8728-EF80237F3269@nuxi.ca> References: <05BEA04B-249B-4E7D-855A-46DA1A0DEA16@dsl-only.net> <36A8BDCC-4ECE-4187-8705-54A9E38E8AD5@dsl-only.net> To: Mark Millard X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 01:47:16 -0000 > On Dec 6, 2017, at 20:01, Mark Millard wrote: >=20 > On 2017-Dec-6, at 1:54 PM, Laurent Cimon wrote: >=20 >>> On Dec 6, 2017, at 00:57, Mark Millard = wrote: >>>=20 >>> I tried to build some ports on a rpi2 >>> (via poudriere) but it hung up: >>> Ethernet and normal console use. (Note: >>> the root file system is on a USB SSD >>> and the swap partition is also on that >>> USB SSD.) >>>=20 >>> But ~^b worked for getting to the db> >>> prompt on the console. >>>=20 >>> =46rom there a ps suggests that it got hung >>> up in pfault activity. (Possibly insufficient >>> RAM+swap-partition space?) But it is not >>> clear to me that it should end up hung up >>> vs. killing processes or other such. >>=20 >> Hi, >>=20 >> =46rom what I know the raspberry pis use the same controller for = ethernet and >> the USB hub on which you=E2=80=99re hosting an SSD. It seems like you = make very heavy >> use of the USB ports, and all of the resources used by poudriere = except for the >> CPU and the (very limited) memory that=E2=80=99s not in swap is = attached to them. If you >> really didn=E2=80=99t have enough memory and swap, the linkers = would=E2=80=99ve been stopped. >>=20 >> I think it might just be a swap death. Poudriere compiles and fetches = in parallel >> a lot, ethernet and disk I/O is slow because it=E2=80=99s very = limited, so linking takes >> longer. You end up linking a few very big binaries at the same time, = and they >> all fight for the memory, to get out of swap through page faults, but = there >> are too many page faults, all too big, requesting for more CPU time = that=E2=80=99s >> allowed to them. >>=20 >> This would explain why you have 3 linkers waiting on a page fault out = of the 4 >> CPUs poudriere allows builds on, on top of the awk processes. It = would also >> explain why you had easy access to the debugger: it was in memory = already with >> the kernel. >>=20 >> I=E2=80=99d advise you to disable parallel builds and see if it = happens again, >> but it would make building much slower. Using makejobs would help if = you >> can afford watching the build. Otherwise be patient, it should = resolve itself >> eventually, but it will take a while and it will happen again. >=20 > My post was more about how FreeBSD handled the > heavy-use context and less about getting the > builds to finish: it managed to to get to a > state of no-progress for processes and a loss > of normal control as far as I could tell. >=20 > I did a "c" to ddb and left it until just before > this note then did ~ ^B again. Things looked the > same. [I've finally rebooted the rpi2.] >=20 > PARALLEL_JOBS=3D1 was already in use but > ALLOW_MAKE_JOBS=3Dyes was also in use. > USE_TMPFS=3Dno was already in use. >=20 > While an ssh session was monitoring the > build, Ethernet was not in heavy use. > (No nfs mounts to its disks, for example.) >=20 > I may try without ALLOW_MAKE_JOBS=3Dyes and > with ALLOW_MAKE_JOBS_PACKAGES empty/undefined > to see if it can complete for such a context > without having the same sort of problem. >=20 > Ultimately I can cross-build and install from > those materials when I really want updates. I > have the context for such. This was more about > seeing how well the rpi2 did for self-hosted. > Classically I've used a BPI-M3 with 2 GiBytes > of RAM and a proportionally bigger swap partition > instead (approximately). >=20 >=20 > FYI (rpi2 after rebooting): >=20 > # swapinfo > Device 1K-blocks Used Avail Capacity > /dev/label/RPI2swap 1572860 0 1572860 0% >=20 > # df -m > Filesystem 1M-blocks Used Avail Capacity Mounted on > /dev/ufs/RPI2rootfs 195378 30791 148957 17% / > devfs 0 0 0 100% /dev > /dev/label/RPI2Aboot 49 12 37 25% /boot/msdos >=20 >=20 > An rpi3 (aarch64) with the same amount of RAM, > same type of USB SSD, etc., but well more swap > completed building basically the same set of > ports for the same poudriere settings just > fine. >=20 > Interestingly for the default kern.maxswzone: > (Just to show the reported recommended maximum > figures for swap.) >=20 > rpi2: . . . exceeds maximum recommended amount (411488 pages). > rpi3: . . . exceeds maximum recommended amount (925680 pages). >=20 > (I was running with somewhat under those maximums for > the tests.) >=20 > # swapinfo > Device 1K-blocks Used Avail Capacity > /dev/gpt/RPI3swap 3702784 0 3702784 0% >=20 > # df -m > Filesystem 1M-blocks Used Avail Capacity Mounted on > /dev/ufs/RPI3rootfs 195378 14937 164811 8% / > devfs 0 0 0 100% /dev > /dev/label/RPI3Aboot 49 7 42 15% /boot/efi >=20 > If I restricted the rpi3 to somewhat under what the > rpi2 allows for swap, I do not know if it would also > hang up vs. not. >=20 > If having more swap makes the difference, then it > would not seem to be being I/O-bound that would > explain the hangup. >=20 >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net There are a few factors that could have prevented this on your raspberry = pi 3. It has a faster, 64 bit CPU instead of the raspberry pi 2=E2=80=99s 32 = bit CPU and the RAM is twice as fast. These make it less likely for this to happen, = because it makes both building and linking faster, which reduces the odds of = linking 2 binaries at once, let alone 3. There are many things that could have = gone differently in the build that didn=E2=80=99t make it end up linking 3 = big binaries at the same time to cause the same behaviour. What I think happened on your raspberry pi 2 is just likely bad luck = that could also happen on your raspberry pi 3. The odds of 3 parallel builds = needing so much ram to link at the exact same time are still very low, just less = low on faster hardware. Keep in mind that this is still entirely theoretical, I don=E2=80=99t = present it as an absolute explanation. It=E2=80=99s simply what I understand from this. I=E2=80=99d be curious seeing how a different operating system using a = system similar to poudriere where builds are done on one CPU but in parallel would be = handled on the rpi2. My understanding is that this is simply a mix of hardware = limitation and conceptual flaws with the swap. And by flaws I mean, your operating = system cannot save you when you try to do something that your hardware cannot = possibly do. Laurent= From owner-freebsd-current@freebsd.org Thu Dec 7 02:28:21 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECEACE97C08 for ; Thu, 7 Dec 2017 02:28:21 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) (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 B377270874 for ; Thu, 7 Dec 2017 02:28:20 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id Mlv1e04Ucj1UsMlv4eiy6h; Thu, 07 Dec 2017 02:28:14 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB72SBT1002365 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Dec 2017 21:28:11 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB72SBea002364; Wed, 6 Dec 2017 21:28:11 -0500 (EST) (envelope-from lausts) Date: Wed, 6 Dec 2017 21:28:11 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171207022811.GA2335@mail.laus.org> Reply-To: lausts@acm.org References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> <20171207012241.GA2170@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171207012241.GA2170@mail.laus.org> X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfMWdMbb0GQttsLxEBctI18CMLAua66IR4q0LMD1i+x5jjhNs670MHq2EaguqpFJz1jjiUEQTFBnxO2WHiGTPd+bnOgqVWyohUwf4GLaDswaHZQArIYUb +8n5tKHxac1xMXINa3X76CZaMTHJifqaNUUh9IXptMuwDKZNzhpzz4iwBOhlLJCjR3w1kJawBXZvKftmnVtEg5CoaD7pclPwtys= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 02:28:22 -0000 > Warner Losh [imp@bsdimp.com] wrote: > > > > You can just build the boot blocks at each step if you'd like to save > > > > some time on the binary search. > > > > > > > > cd stand > > > > make cleandir obj depend > > > > make -j XX > > > > sudo -E make install > > > > > > > > OK. Still a fair number of changes, including changes to geli to fix > > warnings... > > > > 326585-326594 is a flurry of changes. Then another in the 326609-326610 > > range. There's one other trivial one. I'd wager that if '500 works, the > > breakage will be somewhere in the first range, which suggests 326590 might > > be a good, next pivot. There's also a few just after '500 that might break > > things as well if I messed something up. '504 and '507 both touch this > > stuff directly... > > > Warren: > > Building just 'stand' had an error in /usr/src/stand/geli concerning > geli hmac conflicting type for 'ngets'. > > I am doing a full buildworld for r326590. It should be complete > before 9:30 PM EST. I'll post the results and look for replies tomorrow > morning and proceed with the disscetion. > Warren: The r326590 buildworld failed due to a problem in the 'geli' code. The specific error: /usr/src/sys/geom/eli/g-eli_hmac.c line 46. It complained about a missing type specifier. I'll try this again tomorrow morning from an xterm so I can capture and post the exact message. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Thu Dec 7 05:00:20 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94C2AE9CDE9 for ; Thu, 7 Dec 2017 05:00:20 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-170.reflexion.net [208.70.210.170]) (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 594647605C for ; Thu, 7 Dec 2017 05:00:19 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 4474 invoked from network); 7 Dec 2017 05:00:13 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 7 Dec 2017 05:00:13 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Thu, 07 Dec 2017 00:00:13 -0500 (EST) Received: (qmail 2504 invoked from network); 7 Dec 2017 05:00:13 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 7 Dec 2017 05:00:13 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 7F00BEC932D; Wed, 6 Dec 2017 21:00:12 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: rpi2 hangup during poudriere build: lots of pfault wmseg status From: Mark Millard In-Reply-To: <5014B6E6-68BA-4499-8728-EF80237F3269@nuxi.ca> Date: Wed, 6 Dec 2017 21:00:11 -0800 Cc: freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <05BEA04B-249B-4E7D-855A-46DA1A0DEA16@dsl-only.net> <36A8BDCC-4ECE-4187-8705-54A9E38E8AD5@dsl-only.net> <5014B6E6-68BA-4499-8728-EF80237F3269@nuxi.ca> To: Laurent Cimon X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 05:00:20 -0000 > On 2017-Dec-6, at 5:47 PM, Laurent Cimon wrote: >=20 >> On Dec 6, 2017, at 20:01, Mark Millard = wrote: >>=20 >> On 2017-Dec-6, at 1:54 PM, Laurent Cimon wrote: >>=20 >>>> On Dec 6, 2017, at 00:57, Mark Millard = wrote: >>>>=20 >>>> I tried to build some ports on a rpi2 >>>> (via poudriere) but it hung up: >>>> Ethernet and normal console use. (Note: >>>> the root file system is on a USB SSD >>>> and the swap partition is also on that >>>> USB SSD.) >>>>=20 >>>> But ~^b worked for getting to the db> >>>> prompt on the console. >>>>=20 >>>> =46rom there a ps suggests that it got hung >>>> up in pfault activity. (Possibly insufficient >>>> RAM+swap-partition space?) But it is not >>>> clear to me that it should end up hung up >>>> vs. killing processes or other such. >>>=20 >>> Hi, >>>=20 >>> =46rom what I know the raspberry pis use the same controller for = ethernet and >>> the USB hub on which you=E2=80=99re hosting an SSD. It seems like = you make very heavy >>> use of the USB ports, and all of the resources used by poudriere = except for the >>> CPU and the (very limited) memory that=E2=80=99s not in swap is = attached to them. If you >>> really didn=E2=80=99t have enough memory and swap, the linkers = would=E2=80=99ve been stopped. >>>=20 >>> I think it might just be a swap death. Poudriere compiles and = fetches in parallel >>> a lot, ethernet and disk I/O is slow because it=E2=80=99s very = limited, so linking takes >>> longer. You end up linking a few very big binaries at the same time, = and they >>> all fight for the memory, to get out of swap through page faults, = but there >>> are too many page faults, all too big, requesting for more CPU time = that=E2=80=99s >>> allowed to them. >>>=20 >>> This would explain why you have 3 linkers waiting on a page fault = out of the 4 >>> CPUs poudriere allows builds on, on top of the awk processes. It = would also >>> explain why you had easy access to the debugger: it was in memory = already with >>> the kernel. >>>=20 >>> I=E2=80=99d advise you to disable parallel builds and see if it = happens again, >>> but it would make building much slower. Using makejobs would help if = you >>> can afford watching the build. Otherwise be patient, it should = resolve itself >>> eventually, but it will take a while and it will happen again. >>=20 >> My post was more about how FreeBSD handled the >> heavy-use context and less about getting the >> builds to finish: it managed to to get to a >> state of no-progress for processes and a loss >> of normal control as far as I could tell. >>=20 >> I did a "c" to ddb and left it until just before >> this note then did ~ ^B again. Things looked the >> same. [I've finally rebooted the rpi2.] >>=20 >> PARALLEL_JOBS=3D1 was already in use but >> ALLOW_MAKE_JOBS=3Dyes was also in use. >> USE_TMPFS=3Dno was already in use. >>=20 >> While an ssh session was monitoring the >> build, Ethernet was not in heavy use. >> (No nfs mounts to its disks, for example.) >>=20 >> I may try without ALLOW_MAKE_JOBS=3Dyes and >> with ALLOW_MAKE_JOBS_PACKAGES empty/undefined >> to see if it can complete for such a context >> without having the same sort of problem. >>=20 >> Ultimately I can cross-build and install from >> those materials when I really want updates. I >> have the context for such. This was more about >> seeing how well the rpi2 did for self-hosted. >> Classically I've used a BPI-M3 with 2 GiBytes >> of RAM and a proportionally bigger swap partition >> instead (approximately). >>=20 >>=20 >> FYI (rpi2 after rebooting): >>=20 >> # swapinfo >> Device 1K-blocks Used Avail Capacity >> /dev/label/RPI2swap 1572860 0 1572860 0% >>=20 >> # df -m >> Filesystem 1M-blocks Used Avail Capacity Mounted on >> /dev/ufs/RPI2rootfs 195378 30791 148957 17% / >> devfs 0 0 0 100% /dev >> /dev/label/RPI2Aboot 49 12 37 25% /boot/msdos >>=20 >>=20 >> An rpi3 (aarch64) with the same amount of RAM, >> same type of USB SSD, etc., but well more swap >> completed building basically the same set of >> ports for the same poudriere settings just >> fine. >>=20 >> Interestingly for the default kern.maxswzone: >> (Just to show the reported recommended maximum >> figures for swap.) >>=20 >> rpi2: . . . exceeds maximum recommended amount (411488 pages). >> rpi3: . . . exceeds maximum recommended amount (925680 pages). >>=20 >> (I was running with somewhat under those maximums for >> the tests.) >>=20 >> # swapinfo >> Device 1K-blocks Used Avail Capacity >> /dev/gpt/RPI3swap 3702784 0 3702784 0% >>=20 >> # df -m >> Filesystem 1M-blocks Used Avail Capacity Mounted on >> /dev/ufs/RPI3rootfs 195378 14937 164811 8% / >> devfs 0 0 0 100% /dev >> /dev/label/RPI3Aboot 49 7 42 15% /boot/efi >>=20 >> If I restricted the rpi3 to somewhat under what the >> rpi2 allows for swap, I do not know if it would also >> hang up vs. not. >>=20 >> If having more swap makes the difference, then it >> would not seem to be being I/O-bound that would >> explain the hangup. >>=20 >>=20 >> =3D=3D=3D >> Mark Millard >> markmi at dsl-only.net >=20 > There are a few factors that could have prevented this on your = raspberry pi 3. >=20 > It has a faster, 64 bit CPU instead of the raspberry pi 2=E2=80=99s 32 = bit CPU and the > RAM is twice as fast. These make it less likely for this to happen, = because it > makes both building and linking faster, which reduces the odds of = linking 2 > binaries at once, let alone 3. There are many things that could have = gone > differently in the build that didn=E2=80=99t make it end up linking 3 = big binaries at > the same time to cause the same behaviour. >=20 > What I think happened on your raspberry pi 2 is just likely bad luck = that could > also happen on your raspberry pi 3. The odds of 3 parallel builds = needing so > much ram to link at the exact same time are still very low, just less = low on > faster hardware. >=20 > Keep in mind that this is still entirely theoretical, I don=E2=80=99t = present it as an > absolute explanation. It=E2=80=99s simply what I understand from this. >=20 > I=E2=80=99d be curious seeing how a different operating system using a = system similar to > poudriere where builds are done on one CPU but in parallel would be = handled on > the rpi2. My understanding is that this is simply a mix of hardware = limitation > and conceptual flaws with the swap. And by flaws I mean, your = operating system > cannot save you when you try to do something that your hardware cannot = possibly > do. For reference: The rpi2 hung up during: [08:00:15] [01] [00:00:00] Building devel/binutils | binutils-2.28,1 (Only one builder, no prior builds should matter. All 4 cores allowed.) On the rpi3 this was: [08:13:38] [01] [00:00:00] Building devel/binutils | binutils-2.28,1 [10:17:12] [01] [02:03:34] Finished devel/binutils | binutils-2.28,1: = Success (Only one builder, no prior or following builds should matter. All 4 cores allowed.) Comparing a couple of examples that both completed: rpi2: [00:43:40] [01] [00:00:00] Building lang/perl5.24 | perl5-5.24.3 [01:38:37] [01] [00:54:57] Finished lang/perl5.24 | perl5-5.24.3: = Success vs. rpi3: [00:26:35] [01] [00:00:00] Building lang/perl5.24 | perl5-5.24.3 [00:56:14] [01] [00:29:39] Finished lang/perl5.24 | perl5-5.24.3: = Success rpi2: [07:12:51] [01] [00:00:00] Building databases/sqlite3 | sqlite3-3.21.0_1 [07:59:04] [01] [00:46:13] Finished databases/sqlite3 | = sqlite3-3.21.0_1: Success vs. rpi3: [07:43:31] [01] [00:00:00] Building databases/sqlite3 | sqlite3-3.21.0_1 [08:13:35] [01] [00:30:04] Finished databases/sqlite3 | = sqlite3-3.21.0_1: Success The rpi2 lasting days longer than the rpi3 2hr figure for devel/binutils is likely out of scale for processor and RAM differences in speed. (The USB-tied performance likely is not all that different.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-current@freebsd.org Thu Dec 7 10:01:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABCACE82146; Thu, 7 Dec 2017 10:01:02 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC3927F82F; Thu, 7 Dec 2017 10:01:01 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f51.google.com with SMTP id a12so7478929lfe.4; Thu, 07 Dec 2017 02:01:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eey9dYtbB+DTTbhovoI5BWO32O9wW5FafkNk0tGEw6g=; b=eyQjCFsKMeNWJHTEte1VQ2WY5MdypWR5LTwfu6Gg8UeVIp7XRDwyWYrDb3TILvTOh4 126WTmF6MjfShRiQYmhYVKliDsxM5lKraqHT4JQbgDCQ6LegPv8Sv7/Wc3haq5G9UBQX vExot7tjwOl2xtW9VhVyzyi6F7PIn9YG+ph+bo4DTBzqIqfNLx+F0j7sheJPCfgmESVR Aor03242PdEkw4aIfLTrIwCwNAvey6kRfHTIS/9Rg41fjlIuyhrmFWhwacKv8n6Ip4SC EPvAgfwijTXwV4IORs2U5Hma4oLlbZdR6TJnU2m82FW+57or7NHGKnc81CgbE8p2Rlv7 JfCw== X-Gm-Message-State: AJaThX6IcFYPTtILrliDVp7v6baP+gP3Y6R/SHibOjm7rWS0e/Xj/Vgp WrgbZ/I88KmO1k1wuppbQMowaOOE X-Google-Smtp-Source: AGs4zMbz0wbvr9Ah1vXmn8vHw75xu6444/OBkQ2X/DFupjFDAmASeB0WF4cxltG/a9KontmTrkq0cA== X-Received: by 10.46.64.76 with SMTP id n73mr15745109lja.33.1512639233838; Thu, 07 Dec 2017 01:33:53 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id p21sm947366ljb.85.2017.12.07.01.33.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Dec 2017 01:33:53 -0800 (PST) Subject: Re: couple of nvidia-driver issues To: Alexey Dokuchaev Cc: freebsd-x11 , FreeBSD Current References: <07b9dbda-60ef-3643-308f-18a05e8ca958@FreeBSD.org> <20171205140308.GA94043@FreeBSD.org> From: Andriy Gapon Message-ID: <5e95dc14-9d3b-e2eb-b89c-f66f7857eb58@FreeBSD.org> Date: Thu, 7 Dec 2017 11:33:51 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171205140308.GA94043@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.25 Precedence: 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, 07 Dec 2017 10:01:02 -0000 [cc-ing current@ to raise more awareness] On 05/12/2017 16:03, Alexey Dokuchaev wrote: > On Fri, Nov 24, 2017 at 11:31:51AM +0200, Andriy Gapon wrote: >> >> I have reported a couple of nvidia-driver issues in the FreeBSD section >> of the nVidia developer forum, but no replies so far. >> >> Well, the first issue is not with the driver, but with a utility that >> comes with it, nvidia-smi: >> https://devtalk.nvidia.com/default/topic/1026589/freebsd/nvidia-smi-query-gpu-spins-forever-on-freebsd-head-amd64-/ >> I wonder if I am the only one affected or if I see the problem because >> I am on head or something else. >> I am pretty sure that the problem is caused by a programming bug related >> to strtok_r. > > I'll try to reproduce it and report back. I've done some work with a debugger and it seems that there is code that does something like this: char *last = NULL; while (1) { if (last == NULL) p = strtok_r(str, sep, &last); else p = strtok_r(NULL, sep, &last); if (p == NULL) break; ... } The problem is that when 'p' points to the last token, 'last' is NULL (in FreeBSD implementation of strtok_r). That means that when we go to the next iteration the parsing starts all over again leading to the endless loop. The code is incorrect from the standards point of view, because the value of 'last' is completely opaque and should not be used for anything else but passing it back to strtok_r. I used gdb -w to change the logic to: char *last = 1; While (1) { if (last == 1) p = strtok_r(str, sep, &last); else p = strtok_r(NULL, sep, &last); ... } Where 1 is used as an "impossible" pointer value which is neither NULL nor a valid pointer that can be set by strtok_r. It's not ideal, but binary code editing is not as easy as that of source code. The binary patch is here: https://people.freebsd.org/~avg/nvidia-smi.bsdiff >> The second issue is with the FreeBSD support for the kernel driver: >> https://devtalk.nvidia.com/default/topic/1026645/freebsd/panic-related-to-nvkms_timers-lock-sx-lock-/ >> I would like to get some feedback on my analysis. >> I am testing this patch right now: >> https://people.freebsd.org/~avg/extra-patch-src_nvidia-modeset_nvidia-modeset-freebsd.c > > Unfortunately, I'm not an expert on kernel locking primitives to give you > a proper review, let's see what others have to say. It's been a while since I posted the patch and there are no comments yet. I can only add that I am running an INVARIANTS and WITNESS enabled kernel all the time and before the patch I was getting kernel panics every now and then. Since I started using the patch I haven't had a single nvidia panic yet. >> Also, what's the best place or who are the best people with whom to >> discuss such issues? > > Yes, this is a problem now: since Christian Zander had left nVidia, he > could not tell me who'd be their next liaison to talk to from FreeBSD > community. :-( Oh, I didn't know about Christian's departure. So, we are not in a very good position now. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu Dec 7 10:07:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01E0EE823EE; Thu, 7 Dec 2017 10:07:15 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B38EC7FDA5; Thu, 7 Dec 2017 10:07:15 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id F01CD1F7E7; Thu, 7 Dec 2017 10:07:14 +0000 (UTC) Date: Thu, 7 Dec 2017 10:07:14 +0000 From: Alexey Dokuchaev To: Andriy Gapon Cc: freebsd-x11 , FreeBSD Current Subject: Re: couple of nvidia-driver issues Message-ID: <20171207100714.GB59559@FreeBSD.org> References: <07b9dbda-60ef-3643-308f-18a05e8ca958@FreeBSD.org> <20171205140308.GA94043@FreeBSD.org> <5e95dc14-9d3b-e2eb-b89c-f66f7857eb58@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5e95dc14-9d3b-e2eb-b89c-f66f7857eb58@FreeBSD.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 10:07:16 -0000 On Thu, Dec 07, 2017 at 11:33:51AM +0200, Andriy Gapon wrote: > ... > > I've done some work with a debugger and it seems that there is code that does > something like this: > > char *last = NULL; > > while (1) { > ... > > The binary patch is here: https://people.freebsd.org/~avg/nvidia-smi.bsdiff Appreciate taking very close look Andriy. > It's been a while since I posted the patch and there are no comments yet. > I can only add that I am running an INVARIANTS and WITNESS enabled kernel all > the time and before the patch I was getting kernel panics every now and then. > Since I started using the patch I haven't had a single nvidia panic yet. I'll collect all the feedback from you over past few weeks and try to update the driver within couple of days. Thanks! ./danfe From owner-freebsd-current@freebsd.org Thu Dec 7 12:44:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18BDBE85C42 for ; Thu, 7 Dec 2017 12:44:58 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) (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 D5D1C3CE3 for ; Thu, 7 Dec 2017 12:44:57 +0000 (UTC) (envelope-from lausts@acm.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id MvZ7ebUGl1nLrMvZAePP8i; Thu, 07 Dec 2017 12:46:16 +0000 Received: from [192.168.1.100] (presario [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB7Ciqcc004464 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Dec 2017 07:44:52 -0500 (EST) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host presario [192.168.1.100] claimed to be [192.168.1.100] Reply-To: lausts@acm.org Subject: Re: GPTZFSBOOT in Current r326622 has problems To: Warner Losh Cc: FreeBSD Current References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> From: Thomas Laus Message-ID: Date: Thu, 7 Dec 2017 07:44:51 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfHCfdBgVMnI3cyNsXEYTE9Z8mmCHG7G13vU6UrckEJiBvxfrlt80YibuaZ1PRmha1UrUQHjDH6g1l16YMjq8XqyEHWJ/TVcKyhok7BSltA9CqCFYwmA3 bTWuLHv4vNaIX/342wncxhu6JfpVt4nlWgwFAqRHIiZUNrRntM9ORfTk9UyiDSOUTmRRH0ZTAihNAnyFPW3xvVxWadp36NxKJh8= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 12:44:58 -0000 On 12/06/17 19:38, Warner Losh wrote: > > OK. Still a fair number of changes, including changes to geli to fix > warnings... > > 326585-326594 is a flurry of changes. Then another in the 326609-326610 > range. There's one other trivial one. I'd wager that if '500 works, the > breakage will be somewhere in the first range, which suggests 326590 > might be a good, next pivot. There's also a few just after '500 that > might break things as well if I messed something up. '504 and '507 both > touch this stuff directly... > Warren: I reverted my system back to r326585 and 'stand' still won't compile; I get this output: --- g_eli_hmac.o --- In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: In file included from /usr/src/sys/geom/eli/g_eli.h:49: /usr/include/stdio.h:267:12: error: type specifier missing, defaults to 'int' [-Werror,-Wimplicit-int] char *gets(char *); ^ /usr/include/stdio.h:267:7: error: expected parameter declarator char *gets(char *); ^ /usr/src/stand/libsa/stand.h:271:28: note: expanded from macro 'gets' #define gets(x) ngets((x), 0) ^ In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: In file included from /usr/src/sys/geom/eli/g_eli.h:49: /usr/include/stdio.h:267:7: error: expected ')' /usr/src/stand/libsa/stand.h:271:28: note: expanded from macro 'gets' #define gets(x) ngets((x), 0) ^ /usr/include/stdio.h:267:7: note: to match this '(' /usr/src/stand/libsa/stand.h:271:22: note: expanded from macro 'gets' #define gets(x) ngets((x), 0) ^ In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: In file included from /usr/src/sys/geom/eli/g_eli.h:49: /usr/include/stdio.h:267:7: error: conflicting types for 'ngets' char *gets(char *); ^ /usr/src/stand/libsa/stand.h:271:17: note: expanded from macro 'gets' #define gets(x) ngets((x), 0) ^ /usr/src/stand/libsa/stand.h:270:13: note: previous declaration is here extern void ngets(char *, int); ^ In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: In file included from /usr/src/sys/geom/eli/g_eli.h:49: /usr/include/stdio.h:271:6: error: conflicting types for 'putchar' int putchar(int); ^ /usr/src/stand/libsa/stand.h:382:14: note: previous declaration is here extern void putchar(int); ^ In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: In file included from /usr/src/sys/geom/eli/g_eli.h:49: /usr/include/stdio.h:286:6: error: conflicting types for 'vprintf' int vprintf(const char * __restrict, __va_list); ^ /usr/src/stand/libsa/stand.h:262:13: note: previous declaration is here extern void vprintf(const char *fmt, __va_list); ^ In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: /usr/src/stand/libsa/stand.h:265:13: note: previous declaration is here extern void vsprintf(char *buf, const char *cfmt, __va_list); ^ 7 errors generated. *** [g_eli_hmac.o] Error code 1 make[1]: stopped in /usr/src/stand/geli 1 error make[1]: stopped in /usr/src/stand/geli *** [all_subdir_geli] Error code 2 make: stopped in /usr/src/stand 1 error make: stopped in /usr/src/stand Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Thu Dec 7 15:35:49 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0EC25E8A52D; Thu, 7 Dec 2017 15:35:49 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81B5A68A64; Thu, 7 Dec 2017 15:35:48 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id a12so8609322lfe.4; Thu, 07 Dec 2017 07:35:48 -0800 (PST) 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=0xXnogy0dgxGVvel8hclkxs0Zi0brXreI5z7rNweKqc=; b=HFfdDakLbpjnMtIUqF6QW8nNkQfUWPObOqFEli7wbjP5odfZjCV1hAJSj7m0QKYxMl 4/Myx3ZvI2gSOvgPtM4Xxv03C6rwirnVM3lrxwJeLOno6G/cgJLWI/1ZaAGGXR8r8cCQ 4FOHgUGSEthhazzt8OYomV/peNFFgx/pelOF2ZYgomLtbQKHGIXPhoMqUgPpoTQoqElv wrdMBRyjQzBvmMoQpRB4qw5O9o/FtqX89BK7Tko0YESXUNfft+9xMhRmUkoYW3kNJwqY 23euePtPo2rSDyjZ/oEC6Ep/PYeLpVhBhmKyIIPhimarUZOCysVeICNuBwhUhc15aqhR FN2Q== 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=0xXnogy0dgxGVvel8hclkxs0Zi0brXreI5z7rNweKqc=; b=CjpZ9wGwchc3VrN95OzwTn0TjwzwGqlbz+l82NWs4/I7CUNagbbqkcgq6yc9Ozsb5D fr1gjs6an0mdWFRzPteuoXzwarMs3qe8AGGLHOE9bCz/0/JXNx6qJFL+FwuUbcOkTbCO UvbjQlmtY2UHOMe1OobX2SadrZ9ySzk1AbsgOpphh2WS+0jp5VGrWAn0/1HR06gWiits KRosxhQlXN5zov6+CH01Sa8Bv+LAQhVzIlUdMsT5LyDIVKYdq34S5lziLSI5Sd7vy0NH /ieojMftSgIY2q6rCq+cgaxdwSbwRZamnaJLiWU5oRdAyctL1s2HWt0B/v3IckjaCzNJ 2aSw== X-Gm-Message-State: AJaThX7Q/c13jP9XVCu8T7yzOQebEDLu11BbLseiUEXHDrskDvHo09hl nWuz4SnPjvoKkkbzu6X+ISRgbRurYPCsyyfHtEI= X-Google-Smtp-Source: AGs4zMYEilIn5ZdB0LT5lu00HR4iYe76UIVFgemS62ZovSPdY3DPcA8nAPFbhhOlkhWJM/AThYvSBD/4vkW6FBqc3Ic= X-Received: by 10.25.196.202 with SMTP id u193mr12707409lff.169.1512660945720; Thu, 07 Dec 2017 07:35:45 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.76.19 with HTTP; Thu, 7 Dec 2017 07:35:45 -0800 (PST) In-Reply-To: <5e95dc14-9d3b-e2eb-b89c-f66f7857eb58@FreeBSD.org> References: <07b9dbda-60ef-3643-308f-18a05e8ca958@FreeBSD.org> <20171205140308.GA94043@FreeBSD.org> <5e95dc14-9d3b-e2eb-b89c-f66f7857eb58@FreeBSD.org> From: Alan Somers Date: Thu, 7 Dec 2017 08:35:45 -0700 X-Google-Sender-Auth: 9y2go0WvCUUnyHF8oKSYDUt1Iyo Message-ID: Subject: Re: couple of nvidia-driver issues To: Andriy Gapon Cc: Alexey Dokuchaev , freebsd-x11 , FreeBSD Current , Aaron Plattner Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 15:35:49 -0000 On Thu, Dec 7, 2017 at 2:33 AM, Andriy Gapon wrote: > > [cc-ing current@ to raise more awareness] > > On 05/12/2017 16:03, Alexey Dokuchaev wrote: > > On Fri, Nov 24, 2017 at 11:31:51AM +0200, Andriy Gapon wrote: > >> > >> I have reported a couple of nvidia-driver issues in the FreeBSD section > >> of the nVidia developer forum, but no replies so far. > >> > >> Well, the first issue is not with the driver, but with a utility that > >> comes with it, nvidia-smi: > >> https://devtalk.nvidia.com/default/topic/1026589/freebsd/ > nvidia-smi-query-gpu-spins-forever-on-freebsd-head-amd64-/ > >> I wonder if I am the only one affected or if I see the problem because > >> I am on head or something else. > >> I am pretty sure that the problem is caused by a programming bug related > >> to strtok_r. > > > > I'll try to reproduce it and report back. > > I've done some work with a debugger and it seems that there is code that > does > something like this: > > char *last = NULL; > > while (1) { > if (last == NULL) > p = strtok_r(str, sep, &last); > else > p = strtok_r(NULL, sep, &last); > if (p == NULL) > break; > ... > } > > The problem is that when 'p' points to the last token, 'last' is NULL (in > FreeBSD implementation of strtok_r). That means that when we go to the > next > iteration the parsing starts all over again leading to the endless loop. > The code is incorrect from the standards point of view, because the value > of > 'last' is completely opaque and should not be used for anything else but > passing > it back to strtok_r. > > I used gdb -w to change the logic to: > > char *last = 1; > > While (1) { > if (last == 1) > p = strtok_r(str, sep, &last); > else > p = strtok_r(NULL, sep, &last); > ... > } > > Where 1 is used as an "impossible" pointer value which is neither NULL nor > a > valid pointer that can be set by strtok_r. It's not ideal, but binary code > editing is not as easy as that of source code. > > The binary patch is here: https://people.freebsd.org/~ > avg/nvidia-smi.bsdiff > > >> The second issue is with the FreeBSD support for the kernel driver: > >> https://devtalk.nvidia.com/default/topic/1026645/freebsd/ > panic-related-to-nvkms_timers-lock-sx-lock-/ > >> I would like to get some feedback on my analysis. > >> I am testing this patch right now: > >> https://people.freebsd.org/~avg/extra-patch-src_nvidia- > modeset_nvidia-modeset-freebsd.c > > > > Unfortunately, I'm not an expert on kernel locking primitives to give you > > a proper review, let's see what others have to say. > > It's been a while since I posted the patch and there are no comments yet. > I can only add that I am running an INVARIANTS and WITNESS enabled kernel > all > the time and before the patch I was getting kernel panics every now and > then. > Since I started using the patch I haven't had a single nvidia panic yet. > > >> Also, what's the best place or who are the best people with whom to > >> discuss such issues? > > > > Yes, this is a problem now: since Christian Zander had left nVidia, he > > could not tell me who'd be their next liaison to talk to from FreeBSD > > community. :-( > > Oh, I didn't know about Christian's departure. > So, we are not in a very good position now. How about Aaron Plattner (CC'd). Aaron, are you still working on FreeBSD driver issues? -Alan From owner-freebsd-current@freebsd.org Thu Dec 7 16:05:49 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA938E8B5FF; Thu, 7 Dec 2017 16:05:49 +0000 (UTC) (envelope-from aplattner@nvidia.com) Received: from hqemgate15.nvidia.com (hqemgate15.nvidia.com [216.228.121.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hqemgate15.nvidia.com", Issuer "RapidSSL SHA256 CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 98F006B54F; Thu, 7 Dec 2017 16:05:49 +0000 (UTC) (envelope-from aplattner@nvidia.com) Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate15.nvidia.com id ; Thu, 07 Dec 2017 08:00:32 -0800 Received: from HQMAIL101.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Thu, 07 Dec 2017 08:00:42 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Thu, 07 Dec 2017 08:00:42 -0800 Received: from HQMAIL102.nvidia.com (172.18.146.10) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 7 Dec 2017 16:00:42 +0000 Received: from krypton.plattnerplace.us (10.124.1.5) by HQMAIL102.nvidia.com (172.18.146.10) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 7 Dec 2017 16:00:41 +0000 Subject: Re: couple of nvidia-driver issues To: Alan Somers , Andriy Gapon CC: Alexey Dokuchaev , freebsd-x11 , FreeBSD Current References: <07b9dbda-60ef-3643-308f-18a05e8ca958@FreeBSD.org> <20171205140308.GA94043@FreeBSD.org> <5e95dc14-9d3b-e2eb-b89c-f66f7857eb58@FreeBSD.org> From: Aaron Plattner X-Nvconfidentiality: public Message-ID: Date: Thu, 7 Dec 2017 08:00:40 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL108.nvidia.com (172.18.146.13) To HQMAIL102.nvidia.com (172.18.146.10) X-Mailman-Approved-At: Thu, 07 Dec 2017 17:26:32 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 16:05:49 -0000 On 12/07/2017 07:35 AM, Alan Somers wrote: > On Thu, Dec 7, 2017 at 2:33 AM, Andriy Gapon > wrote: >=20 >=20 > [cc-ing current@ to raise more awareness] >=20 > On 05/12/2017 16:03, Alexey Dokuchaev wrote: > > On Fri, Nov 24, 2017 at 11:31:51AM +0200, Andriy Gapon wrote: > >> > >> I have reported a couple of nvidia-driver issues in the FreeBSD > section > >> of the nVidia developer forum, but no replies so far. > >> > >> Well, the first issue is not with the driver, but with a utility > that > >> comes with it, nvidia-smi: > >> > https://devtalk.nvidia.com/default/topic/1026589/freebsd/nvidia-smi-q= uery-gpu-spins-forever-on-freebsd-head-amd64-/ > > >> I wonder if I am the only one affected or if I see the problem > because > >> I am on head or something else. > >> I am pretty sure that the problem is caused by a programming bug > related > >> to strtok_r. > > > > I'll try to reproduce it and report back. >=20 > I've done some work with a debugger and it seems that there is code > that does > something like this: >=20 > char *last =3D NULL; >=20 > while (1) { > =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (last =3D=3D NULL) > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 p =3D strtok= _r(str, sep, &last); > =C2=A0 =C2=A0 =C2=A0 =C2=A0 else > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 p =3D strtok= _r(NULL, sep, &last); > =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (p =3D=3D NULL) > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 break; > =C2=A0 =C2=A0 =C2=A0 =C2=A0 ... > } >=20 > The problem is that when 'p' points to the last token, 'last' is > NULL (in > FreeBSD implementation of strtok_r).=C2=A0 That means that when we go= to > the next > iteration the parsing starts all over again leading to the endless lo= op. > The code is incorrect from the standards point of view, because the > value of > 'last' is completely opaque and should not be used for anything else > but passing > it back to strtok_r. >=20 > I used gdb -w to change the logic to: >=20 > char *last =3D 1; >=20 > While (1) { > =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (last =3D=3D 1) > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 p =3D strtok= _r(str, sep, &last); > =C2=A0 =C2=A0 =C2=A0 =C2=A0 else > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 p =3D strtok= _r(NULL, sep, &last); > =C2=A0 =C2=A0 =C2=A0 =C2=A0 ... > } >=20 > Where 1 is used as an "impossible" pointer value which is neither > NULL nor a > valid pointer that can be set by strtok_r.=C2=A0 It's not ideal, but > binary code > editing is not as easy as that of source code. >=20 > The binary patch is here: > https://people.freebsd.org/~avg/nvidia-smi.bsdiff > >=20 > >> The second issue is with the FreeBSD support for the kernel drive= r: > >> > https://devtalk.nvidia.com/default/topic/1026645/freebsd/panic-relate= d-to-nvkms_timers-lock-sx-lock-/ > > >> I would like to get some feedback on my analysis. > >> I am testing this patch right now: > >> > https://people.freebsd.org/~avg/extra-patch-src_nvidia-modeset_nvidia= -modeset-freebsd.c > > > > > Unfortunately, I'm not an expert on kernel locking primitives to > give you > > a proper review, let's see what others have to say. >=20 > It's been a while since I posted the patch and there are no comments > yet. > I can only add that I am running an INVARIANTS and WITNESS enabled > kernel all > the time and before the patch I was getting kernel panics every now > and then. > Since I started using the patch I haven't had a single nvidia panic y= et. >=20 > >> Also, what's the best place or who are the best people with whom = to > >> discuss such issues? > > > > Yes, this is a problem now: since Christian Zander had left > nVidia, he > > could not tell me who'd be their next liaison to talk to from Free= BSD > > community. :-( >=20 > Oh, I didn't know about Christian's departure. > So, we are not in a very good position now. >=20 >=20 > How about Aaron Plattner (CC'd).=C2=A0 Aaron, are you still working on=20 > FreeBSD driver issues? Thanks for the heads up, Alan. I filed bug 2032249 to track this. -- Aaron From owner-freebsd-current@freebsd.org Thu Dec 7 19:59:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48650E8FA24; Thu, 7 Dec 2017 19:59:16 +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 2E4397366D; Thu, 7 Dec 2017 19:59:16 +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 vB7JxFPA096237 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Dec 2017 11:59:15 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id vB7JxFSM096236; Thu, 7 Dec 2017 11:59:15 -0800 (PST) (envelope-from sgk) Date: Thu, 7 Dec 2017 11:59:15 -0800 From: Steve Kargl To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: [PATCH] update math.3 for reality Message-ID: <20171207195915.GA96227@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.7.2 (2016-11-26) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 19:59:16 -0000 The following patch updates math.3 to reflect the current state of reality. Index: msun/man/math.3 =================================================================== --- msun/man/math.3 (revision 2046) +++ msun/man/math.3 (working copy) @@ -28,7 +28,7 @@ .\" from: @(#)math.3 6.10 (Berkeley) 5/6/91 .\" $FreeBSD: head/lib/msun/man/math.3 226460 2011-10-17 06:10:32Z das $ .\" -.Dd December 5, 2010 +.Dd December 7, 2017 .Dt MATH 3 .Os .Sh NAME @@ -235,12 +235,6 @@ .Vt long double values, were written for or imported into subsequent versions of FreeBSD. .Sh BUGS -Some of the -.Vt "long double" -math functions in -.St -isoC-99 -are not available. -.Pp Many of the routines to compute transcendental functions produce inaccurate results in other than the default rounding mode. .Pp -- Steve From owner-freebsd-current@freebsd.org Thu Dec 7 20:03:20 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2FAFE8FE62; Thu, 7 Dec 2017 20:03:20 +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 8F78473E87; Thu, 7 Dec 2017 20:03:20 +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 vB7K3JmW096331 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Dec 2017 12:03:19 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id vB7K3JKj096330; Thu, 7 Dec 2017 12:03:19 -0800 (PST) (envelope-from sgk) Date: Thu, 7 Dec 2017 12:03:19 -0800 From: Steve Kargl To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: [PATCH] Remove unused include file Message-ID: <20171207200319.GA96323@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.7.2 (2016-11-26) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 20:03:20 -0000 The following patch removes an unused include. Index: msun/bsdsrc/b_log.c =================================================================== --- msun/bsdsrc/b_log.c (revision 2046) +++ msun/bsdsrc/b_log.c (working copy) @@ -36,7 +36,6 @@ __FBSDID("$FreeBSD: head/lib/msun/bsdsrc/b_log.c 176449 2008-02-22 02:26:51Z das $"); #include -#include #include "mathimpl.h" -- Steve From owner-freebsd-current@freebsd.org Thu Dec 7 20:49:36 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 799B5E90EA8; Thu, 7 Dec 2017 20:49:36 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C21D7586A; Thu, 7 Dec 2017 20:49:35 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 428961C9E7; Thu, 7 Dec 2017 21:42:41 +0100 (CET) From: Dimitry Andric Message-Id: <1BC2754C-0A91-4214-84A2-5F5DE0E9A6EB@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_0908F8A0-83F2-4C48-8DE4-E431E9F13E0F"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [PATCH] Remove unused include file Date: Thu, 7 Dec 2017 21:42:40 +0100 In-Reply-To: <20171207200319.GA96323@troutmask.apl.washington.edu> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org To: sgk@troutmask.apl.washington.edu References: <20171207200319.GA96323@troutmask.apl.washington.edu> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 20:49:36 -0000 --Apple-Mail=_0908F8A0-83F2-4C48-8DE4-E431E9F13E0F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 7 Dec 2017, at 21:03, Steve Kargl = wrote: >=20 > The following patch removes an unused include. >=20 > Index: msun/bsdsrc/b_log.c Thanks, committed in r326670. -Dimitry --Apple-Mail=_0908F8A0-83F2-4C48-8DE4-E431E9F13E0F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWimnwAAKCRCwXqMKLiCW o3qYAJ9YkjgfYGBKMZuGRTFeQcjuw56qLACbBYqVvkS8g2sA6hWmNLErmsKVfLY= =WSVq -----END PGP SIGNATURE----- --Apple-Mail=_0908F8A0-83F2-4C48-8DE4-E431E9F13E0F-- From owner-freebsd-current@freebsd.org Thu Dec 7 20:49:36 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7ADC3E90EA9; Thu, 7 Dec 2017 20:49:36 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C2AA7586B; Thu, 7 Dec 2017 20:49:35 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id DED151C9E6; Thu, 7 Dec 2017 21:42:35 +0100 (CET) From: Dimitry Andric Message-Id: <334CF113-1392-4318-B9E0-82C0D90C5C19@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_72A04102-1371-42ED-AACF-FBACD5F44A93"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [PATCH] update math.3 for reality Date: Thu, 7 Dec 2017 21:42:35 +0100 In-Reply-To: <20171207195915.GA96227@troutmask.apl.washington.edu> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org To: sgk@troutmask.apl.washington.edu References: <20171207195915.GA96227@troutmask.apl.washington.edu> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 07 Dec 2017 20:49:36 -0000 --Apple-Mail=_72A04102-1371-42ED-AACF-FBACD5F44A93 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 7 Dec 2017, at 20:59, Steve Kargl = wrote: > The following patch updates math.3 to reflect the current > state of reality. >=20 > Index: msun/man/math.3 Thanks, committed in r326669. -Dimitry --Apple-Mail=_72A04102-1371-42ED-AACF-FBACD5F44A93 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWimnuwAKCRCwXqMKLiCW ozR3AJsHfi9STm94fDJLImwdTAJT254kbQCePsr9sWt7uPgi2knBI3D3S918mDQ= =DziV -----END PGP SIGNATURE----- --Apple-Mail=_72A04102-1371-42ED-AACF-FBACD5F44A93-- From owner-freebsd-current@freebsd.org Fri Dec 8 13:23:05 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE76EE83575 for ; Fri, 8 Dec 2017 13:23:05 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8013D71D8D for ; Fri, 8 Dec 2017 13:23:05 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x233.google.com with SMTP id t1so4753861ite.5 for ; Fri, 08 Dec 2017 05:23:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=c0m3YE+VfA6qa6F2HzLqYzmCn9kurRqHnmCo/wnlrjQ=; b=A73EgSyhaVZOcpGFOlsJlM6MCTAWh8/DmHHa+0l7G9V7Ag7LLmDWa6FcOWiZRs7Pnv hhmNqkrhMxP1Yq457+WnSJTi2ZvARYx4VmRcxyo/QUc4ToJQ1DosPsStvFynlb89Lsh9 icvaXGtEubBTubZIYYDHEdkKts4YV8nYXjurxc9bJtqrQKAF/LSDSRinX3qX++gE2AYb LVbo5e0iMZnV3kWFLpQXZ5DtHg/wiTHnhj5AR6KtWeEassG8c90FlZARjkhXWnErRIay cPCZifE80I9tvTJbAg43H2eOwZ7FQ2oee/jD7U3xAasT1+UZb7X00gysLU+od7B0Ofer m4LA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=c0m3YE+VfA6qa6F2HzLqYzmCn9kurRqHnmCo/wnlrjQ=; b=hJw2ndPbpw/LwsVpGW7dS1/3rkkZw5ceijoXwINEcrIqvc18UX6rCGk29YMQYVriJk WsVuCWPd/eEPBRM26RpDypIfNVRyN/cO0I1/P9WL+XGpxJZ7kl/Qck1sXUFjCX/mxdgU y/f6TgDrWbkHjTLVypem3OkZEcKbFy2x80GRXmAmbXK/sQQyneBRCtzDErcFpaGMZ1Sx cVfFSEkRRFabtwDpcjWb/XjVa09xaQj6biURzlOuVCeTEj29D8sBPA8H9/ST0zJiJFpl itS6htaeRX4Imb4R5+zStCWnDLbaVou/eKtATjSF84xQ+KOFM9AEOzVWk1CG8sBcjSPJ 83qw== X-Gm-Message-State: AKGB3mJf8rk9wG5tAhaGDNy2CislPgNFRA6GGPNqDAzJ/UPGeVGXF6dh TW95kr+J+WyEMxB9Wi7Q21UPfsyBqMm1LkM4iVE= X-Google-Smtp-Source: AGs4zMbMxrvoESMnH2KYLW1I6Ef3JSOqGtDYrDoVKoLnFbR9HdaIHo/PLEYa45TWnnu5Ato/Lk5n+/lBd7Aaw7mAoIU= X-Received: by 10.36.221.147 with SMTP id t141mr5558037itf.140.1512739384558; Fri, 08 Dec 2017 05:23:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.11.31 with HTTP; Fri, 8 Dec 2017 05:23:04 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Fri, 8 Dec 2017 21:23:04 +0800 Message-ID: Subject: Re: valloric YCM [header definitions] To: FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 08 Dec 2017 13:23:05 -0000 On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme wrote: > I'm looking for where the u_int, u_long headers are defined? > > for instance MOD_LOAD, UNLOAD, ENOTSUP along with u_int and u_long aren't > being picked up by libclang > > module_t isn't being found either but I located that header file in > /usr/include/sys/module.h > > snd_modevent(module_t mod, int type, void *data) > { > > switch (type) { > case MOD_LOAD: > break; > case MOD_UNLOAD: > break; > default: > return (ENOTSUP); > break; > } > return 0; > } > > Anyone here uses YCM? > > Here's a verbose output of my global ycm_config. I hard coded the values > to test but still some headers like u_int, u_long and the above mentioned > MOD_* aren't being picked up. > > Any ideas why? > > '-std=c99', > '-x', > 'c', > '-I', > '/usr/local/include', > '-I', > '/usr/include', > '-I', > '/usr/include/teken', > '-I', > '/usr/include/geom', > '-I', > '/usr/include/netgraph', > '-I', > '/usr/include/isofs', > '-I', > '/usr/include/net80211', > '-I', > '/usr/include/gssapi', > '-I', > '/usr/include/xlocale', > '-I', > '/usr/include/netpfil', > '-I', > '/usr/include/gcc', > '-I', > '/usr/include/bsnmp', > '-I', > '/usr/include/libxo', > '-I', > '/usr/include/ssp', > '-I', > '/usr/include/devdctl', > '-I', > '/usr/include/security', > '-I', > '/usr/include/crypto', > '-I', > '/usr/include/cam', > '-I', > '/usr/include/rdma', > '-I', > '/usr/include/infiniband', > '-I', > '/usr/include/rpcsvc', > '-I', > '/usr/include/atf-c', > '-I', > '/usr/include/netnatm', > '-I', > '/usr/include/ufs', > '-I', > '/usr/include/edit', > '-I', > '/usr/include/nfsserver', > '-I', > '/usr/include/netsmb', > '-I', > '/usr/include/gnu', > '-I', > '/usr/include/net', > '-I', > '/usr/include/private', > '-I', > '/usr/include/nfsclient', > '-I', > '/usr/include/openssl', > '-I', > '/usr/include/libmilter', > '-I', > '/usr/include/atf-c++', > '-I', > '/usr/include/netinet6', > '-I', > '/usr/include/x86', > '-I', > '/usr/include/dev', > '-I', > '/usr/include/bsm', > '-I', > '/usr/include/netipsec', > '-I', > '/usr/include/netinet', > '-I', > '/usr/include/krb5', > '-I', > '/usr/include/casper', > '-I', > '/usr/include/protocols', > '-I', > '/usr/include/lib80211', > '-I', > '/usr/include/arpa', > '-I', > '/usr/include/pcap', > '-I', > '/usr/include/nfs', > '-I', > '/usr/include/machine', > '-I', > '/usr/include/fs', > '-I', > '/usr/include/sys', > '-I', > '/usr/include/rpc', > '-I', > '/usr/include/kadm5', > '-I', > '/usr/include/vm', > '-I', > '/usr/include/c++', > '-I', > '/usr/include/lzma', > '-I', > '/sys', > '-I', > '/dev', > '-I', > '/usr/src', > > There's no one on this mailing list that uses YCM for their FreeBSD development? From owner-freebsd-current@freebsd.org Fri Dec 8 13:53:13 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B02C8E83FC0 for ; Fri, 8 Dec 2017 13:53:13 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A29E72CBB for ; Fri, 8 Dec 2017 13:53:13 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 3FDED2603A1; Fri, 8 Dec 2017 14:53:10 +0100 (CET) Subject: Re: valloric YCM [header definitions] To: blubee blubeeme , FreeBSD current References: From: Hans Petter Selasky Message-ID: <91931def-9693-84dc-3252-0e2fda1f0e3d@selasky.org> Date: Fri, 8 Dec 2017 14:50:20 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.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-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 08 Dec 2017 13:53:13 -0000 On 12/08/17 14:23, blubee blubeeme wrote: > On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme wrote: Hi, These questions are better off at questions@freebsd.org :-) >> I'm looking for where the u_int, u_long headers are defined? Anyway, it appears you are having some fun figuring out how the FreeBSD sources are organized. Everything in /usr/include is only meant for user-space. Integer types are defined by and . grep -rE "^typedef.*u_int" /usr/include/ >> >> for instance MOD_LOAD, UNLOAD, ENOTSUP along with u_int and u_long aren't >> being picked up by libclang >> >> module_t isn't being found either but I located that header file in >> /usr/include/sys/module.h >> >> snd_modevent(module_t mod, int type, void *data) >> { >> >> switch (type) { >> case MOD_LOAD: >> break; >> case MOD_UNLOAD: >> break; >> default: >> return (ENOTSUP); >> break; >> } >> return 0; >> } >> >> Anyone here uses YCM? >> I recommend not compiling kernel code outside the Makefile environment. Examples of valid kernel-side Makefiles you find in /usr/src/sys/modules make -C /usr/src/sys/modules/sound clean make -C /usr/src/sys/modules/sound depend make -C /usr/src/sys/modules/sound all >> Here's a verbose output of my global ycm_config. I hard coded the values >> to test but still some headers like u_int, u_long and the above mentioned >> MOD_* aren't being picked up. --HPS From owner-freebsd-current@freebsd.org Fri Dec 8 14:02:54 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D0B0E84419 for ; Fri, 8 Dec 2017 14:02:54 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F192732F6 for ; Fri, 8 Dec 2017 14:02:53 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id i11so3344507wmf.4 for ; Fri, 08 Dec 2017 06:02:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=CgYw9qS7zVl2RwLDkbjEFQvOK6+Jc/GdrRDKkj4COJI=; b=mqYAb6pdVugiHSjVjVSSiRqrqmHsGj9PN+Ezpjxm0sWNEa4prfgUiK+HesLImxzvuK rrV0o7hQC65mNVog3rDDw/NlGXy+mnmZCISeybxXdznPfb8yd1pYLnsS68WUMFuB+hxE HZu1G6V3awKUeUM5NBt/sO9VwXuM0Vs+kfQMuEjB6T5rbaFkME5S7KNVhvTIMXu81brA Pbg05JsNQiQN/xEYUpiCGrDLTQSQ5pk0NWsJi+buboRzUdrtqz0xlgsApR4cdau//LJV j1AE4jfZdpXHG5LuEnWP8aSM4djw2wzscUiehoW0nl7glUKdgM4zBEJwav7sHQ0BOsLN i7cQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=CgYw9qS7zVl2RwLDkbjEFQvOK6+Jc/GdrRDKkj4COJI=; b=aMLuDcho4EctTpe5a0p7UdW7H8/GN0GyabqYDgdT4o9a/dWKuOhZ3bnx0H688cJyTO JcqFCPr9sHEESleVAIqZMsGfAp3l9hRpvauR5F55r0sgPDuLQ4k1JtRcoR3Cbppt/oMc ekdnnESB4Bc3xZPgjVrXI/B94jRoe/duRruDYt7bVRRBOmEhDKBHjtO/kFncrpXx1MQ1 POyBS/NNRxCv7HVoennsjlGIyAdMY8/uQBK6kqlaVR1nyD7k2icVlnX1PgcOzPRUwxyv 2gMzPKWe8h9gcYfXPjOyd7bx4j2Yv6tmPX0eDHr6WEXYYdDzAASZ6CJbSPYywTowVWRJ ArpQ== X-Gm-Message-State: AKGB3mJvcK07o4Qg2qUEgi9CXWajqslwZad9pnRM9yFt6juXNym565Cg TnVUFWD0F+DTct3AjDkLDQo= X-Google-Smtp-Source: AGs4zMYhq+YdjOwomgQV9RjXTktVJRY+lxOA+ksQKPwphUUYWNMaTMc6dDT6exGGJQd0jTNSgyPdeA== X-Received: by 10.28.126.201 with SMTP id z192mr3171711wmc.121.1512741771941; Fri, 08 Dec 2017 06:02:51 -0800 (PST) Received: from ernst.home (p5B023D43.dip0.t-ipconnect.de. [91.2.61.67]) by smtp.gmail.com with ESMTPSA id o135sm1756882wmg.1.2017.12.08.06.02.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 08 Dec 2017 06:02:50 -0800 (PST) Date: Fri, 8 Dec 2017 15:02:48 +0100 From: Gary Jennejohn To: blubee blubeeme Cc: FreeBSD current Subject: Re: valloric YCM [header definitions] Message-ID: <20171208150248.3338c2cc@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 08 Dec 2017 14:02:54 -0000 On Fri, 8 Dec 2017 21:23:04 +0800 blubee blubeeme wrote: > On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme wrote: > > > I'm looking for where the u_int, u_long headers are defined? > > These are not headers, they're typedefs. These are defined in /usr/include/sys/types.h. This is the standard loacation for globally used typedefs. > > for instance MOD_LOAD, UNLOAD, ENOTSUP along with u_int and u_long aren't > > being picked up by libclang > > Errors like ENOTSUP are defined in /usr/include/sys/errno.h. This is the standard location for globally used error codes. > > module_t isn't being found either but I located that header file in > > /usr/include/sys/module.h > > > > snd_modevent(module_t mod, int type, void *data) > > { > > > > switch (type) { > > case MOD_LOAD: > > break; > > case MOD_UNLOAD: > > break; > > default: > > return (ENOTSUP); > > break; > > } > > return 0; > > } > > > > Anyone here uses YCM? > > [snip] Apparently not. You seem to have all the usual include paths in the list. No idea why it's not working. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Fri Dec 8 20:00:11 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8219E8DA1D for ; Fri, 8 Dec 2017 20:00:11 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D9292201; Fri, 8 Dec 2017 20:00:11 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qt0-x22c.google.com with SMTP id g9so28281857qth.9; Fri, 08 Dec 2017 12:00:11 -0800 (PST) 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=DjqelNa9zahmNRdCRfsRKsiLeCqIGcM4VqEO2koudZg=; b=cAlgKGpDPqFoHoT8Gn+mVIj8YNQ4TaIlruxtN5/zcNkjtoYhoDVgnkspypT8mzxtrS WOv47QD/Va5NLoORx8gNnFKmYlJCdatHC/BDmrypzXxlaYWhozC3rdz8MuYzbgh13twj qZn4qw1xS3Iq08qI7eHC+EgXaKT6eFBPjTtdP91iesevepZiW0j7T2ljQtsJx18E/Nrv 5i+vAtKtCveRALJTKfmaLBZ06kuhYgs0qvC5noqd8owM9G4OwKt0OLqo4NrxelmyTOMf 6qsiQk0tLsiS5Vpybe4gT4lo8XTSCEwL/yjmN2kpCXbaY2xL2uygiiSHMy0KN8kqLbGj 6zyQ== 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=DjqelNa9zahmNRdCRfsRKsiLeCqIGcM4VqEO2koudZg=; b=PfJmMqVV+FlzNVk/kT+IFgFPhW8PEbQCvK2MpDvRG5drYxrzhBn1KfP7BhbvYgNMLz dRS5ALLYPRbbR0vjf1HsNvdpF5yDQ9x3+U3VMRYIF03D67C1uSvNG6XPXFGS7Ln4yh/W XOqiv6FAaQajqDnvPqKTbG6d3jQTj2wy2sy/hyZ6yiNDDm4EdxnqIV1vQ11Memuc/p7g qMr/1mAz8eoEMWT+hJ6LmKl8nfz0JibMZm0bo1kp0VxzFP95x3EYgQ6QgScZDSgtISvk Vxft4vDznkZg+A9GO3ipuHxZ1UZ4EEBeuyoAkRGCzlcH0N2B8ih0qET9ersVYxo9SF4b 3zLw== X-Gm-Message-State: AKGB3mLm5/AUZoP9sKl3N4hqo7L6RaWi7+vJSMERbESjjLmtiOGsVP8T HNv8SRt0jQGFWsaAmadY3Ukc6g== X-Google-Smtp-Source: AGs4zMbREJfApdfmfSgIBFJFy/EdcZfLUGAfLroQne2QUe4iackqi+8Zt8dQHvbRnKGgRxwqlnFLIw== X-Received: by 10.237.58.167 with SMTP id o36mr18393403qte.333.1512763210358; Fri, 08 Dec 2017 12:00:10 -0800 (PST) Received: from raichu (toroon0560w-lp140-01-69-159-38-22.dsl.bell.ca. [69.159.38.22]) by smtp.gmail.com with ESMTPSA id v8sm470741qtc.67.2017.12.08.12.00.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Dec 2017 12:00:09 -0800 (PST) Sender: Mark Johnston Date: Fri, 8 Dec 2017 15:00:07 -0500 From: Mark Johnston To: Mateusz Guzik Cc: FreeBSD Current , John Baldwin Subject: Re: Breakage with sys.kern.ptrace_test.{ptrace__parent_sees_exit_after_child_debugger, parent_sees_exit_after_unrelated_debugger} after r325719:325721 Message-ID: <20171208200007.GC8378@raichu> References: <7567DDF3-6E53-455F-B25E-AE2082F74F40@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7567DDF3-6E53-455F-B25E-AE2082F74F40@gmail.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 08 Dec 2017 20:00:12 -0000 On Thu, Nov 16, 2017 at 09:07:56AM -0800, Ngie Cooper (yaneurabeya) wrote: > Hi Mateusz, > Per Jenkins, these two tests are broken after r325719:325721: https://ci.freebsd.org/job/FreeBSD-head-amd64-test/4987/ . > Thanks, > -Ngie Ping? These tests are still failing. From owner-freebsd-current@freebsd.org Fri Dec 8 20:08:59 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C1F0E8DE69 for ; Fri, 8 Dec 2017 20:08:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2020D2A67 for ; Fri, 8 Dec 2017 20:08:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22e.google.com with SMTP id f190so7046195ita.5 for ; Fri, 08 Dec 2017 12:08:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=UJ1EmXPHoOwGPUNb50e3uuKJKeWhwsD4XLedcHNuYnc=; b=ludvwp/HNvUioseolXujVly7xilj409b0+ReDbx71bT+iGQ1vLzc6LWKhRwHnhxCfi Jw3JIzB9budl3qsRq9AZFYzYQVRNdGMwkR1/GAyZhDCOBN96ktrXwvqTuXxu3a6SnqaF gavq8iYqy9ogPDqBgnctSFUaiaV0kFjhHtdX7lalqn/EsCf/ELlKZRlwI6vlI6Sf4zfb HUQVZYSN9r5RmOe+odJkxquCdCo5IE6HFwRnKbnEPyuiUNfb6uyM96MKFMBtGf2cMTkg LQmCiVo5LkRO6ykrVkkT7lr8ICh9aCGmhprfcEAvQf+VtFTFV26fTzvmZyg7e7QUuHpi 09DQ== 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=UJ1EmXPHoOwGPUNb50e3uuKJKeWhwsD4XLedcHNuYnc=; b=mbWwhyeH9HCTL6sSaHJlpXmNm/7w/+XLGci4C9gugLLD8RRrZ2KQFnBP2KSBnflorn /SKgjpCyc56B3fBfVjs+9DsPsivaJlMrFAnMZwiwBRPBTHv6N4HyHOeARs4dkCoh3k/f xhv9fDRm6gc7qp1lKazR7bc3+XLqnbwjwT80yW8uqu/MgyBaqGR83bQQqPSf7vHp3ScS /jUIEeXvPoTMtPCbdarTdZqqG7pQjNTXShKx/gVH5jM/M7OB3ZPHT+FACNg6yF958CDQ koCGn9BqHnSXsKhRwT7fx0m3OBtMsgk3qW4JZMXni+sslA02hFSgRQgUx0FW6AzrIKST A8wg== X-Gm-Message-State: AKGB3mLQBbxRj3eNCIplQGfD0C936RA5VHNxjrbDrvYhwx5YxwqVQnLj dApJuXaYTeh/cQa3i0EwLWier54q9cJp/BM67fFCWw== X-Google-Smtp-Source: AGs4zMYmY5zvEaCZ9TbvxGFGH10yuRJatSZv2sqherPLABvGTXKMEB9Bmp+nOiZZUNr2Xl6skduTpe+FYe0zeZ9AhJ8= X-Received: by 10.36.77.143 with SMTP id l137mr7597868itb.50.1512763738436; Fri, 08 Dec 2017 12:08:58 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Fri, 8 Dec 2017 12:08:57 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> From: Warner Losh Date: Fri, 8 Dec 2017 13:08:57 -0700 X-Google-Sender-Auth: -d2_xZo3b0JN_ct84cnHsUxc_kE Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 08 Dec 2017 20:08:59 -0000 Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've fixed it in r326714. Warner On Thu, Dec 7, 2017 at 5:44 AM, Thomas Laus wrote: > On 12/06/17 19:38, Warner Losh wrote: > > > > OK. Still a fair number of changes, including changes to geli to fix > > warnings... > > > > 326585-326594 is a flurry of changes. Then another in the 326609-326610 > > range. There's one other trivial one. I'd wager that if '500 works, the > > breakage will be somewhere in the first range, which suggests 326590 > > might be a good, next pivot. There's also a few just after '500 that > > might break things as well if I messed something up. '504 and '507 both > > touch this stuff directly... > > > Warren: > > I reverted my system back to r326585 and 'stand' still won't compile; I > get this output: > > --- g_eli_hmac.o --- > In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: > In file included from /usr/src/sys/geom/eli/g_eli.h:49: > /usr/include/stdio.h:267:12: error: type specifier missing, defaults to > 'int' [-Werror,-Wimplicit-int] > char *gets(char *); > ^ > /usr/include/stdio.h:267:7: error: expected parameter declarator > char *gets(char *); > ^ > /usr/src/stand/libsa/stand.h:271:28: note: expanded from macro 'gets' > #define gets(x) ngets((x), 0) > ^ > In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: > In file included from /usr/src/sys/geom/eli/g_eli.h:49: > /usr/include/stdio.h:267:7: error: expected ')' > /usr/src/stand/libsa/stand.h:271:28: note: expanded from macro 'gets' > #define gets(x) ngets((x), 0) > ^ > /usr/include/stdio.h:267:7: note: to match this '(' > /usr/src/stand/libsa/stand.h:271:22: note: expanded from macro 'gets' > #define gets(x) ngets((x), 0) > ^ > In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: > In file included from /usr/src/sys/geom/eli/g_eli.h:49: > /usr/include/stdio.h:267:7: error: conflicting types for 'ngets' > char *gets(char *); > ^ > /usr/src/stand/libsa/stand.h:271:17: note: expanded from macro 'gets' > #define gets(x) ngets((x), 0) > ^ > /usr/src/stand/libsa/stand.h:270:13: note: previous declaration is here > extern void ngets(char *, int); > ^ > In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: > In file included from /usr/src/sys/geom/eli/g_eli.h:49: > /usr/include/stdio.h:271:6: error: conflicting types for 'putchar' > int putchar(int); > ^ > /usr/src/stand/libsa/stand.h:382:14: note: previous declaration is here > extern void putchar(int); > ^ > In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: > In file included from /usr/src/sys/geom/eli/g_eli.h:49: > /usr/include/stdio.h:286:6: error: conflicting types for 'vprintf' > int vprintf(const char * __restrict, __va_list); > ^ > /usr/src/stand/libsa/stand.h:262:13: note: previous declaration is here > extern void vprintf(const char *fmt, __va_list); > ^ > In file included from /usr/src/sys/geom/eli/g_eli_hmac.c:46: > /usr/src/stand/libsa/stand.h:265:13: note: previous declaration is here > extern void vsprintf(char *buf, const char *cfmt, __va_list); > ^ > 7 errors generated. > *** [g_eli_hmac.o] Error code 1 > > make[1]: stopped in /usr/src/stand/geli > 1 error > > make[1]: stopped in /usr/src/stand/geli > *** [all_subdir_geli] Error code 2 > > make: stopped in /usr/src/stand > 1 error > > make: stopped in /usr/src/stand > > > Tom > > -- > Public Keys: > PGP KeyID = 0x5F22FDC1 > GnuPG KeyID = 0x620836CF > From owner-freebsd-current@freebsd.org Sat Dec 9 01:02:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3210E93C46; Sat, 9 Dec 2017 01:02:06 +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 92B116BB21; Sat, 9 Dec 2017 01:02:06 +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 vB9125ea042299 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 8 Dec 2017 17:02:05 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id vB9125mf042298; Fri, 8 Dec 2017 17:02:05 -0800 (PST) (envelope-from sgk) Date: Fri, 8 Dec 2017 17:02:05 -0800 From: Steve Kargl To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: [PATCH] Document powl and tgammal kludges Message-ID: <20171209010205.GA42226@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.7.2 (2016-11-26) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 01:02:06 -0000 The following patch documents the remaining kludges that theraven@ committed in r255294 on 2013-09-06. I have cleaned up all of the others, but powl and tgammal remain. ngie@ seems to have documented the existence of powl with r290605, but did not document the rather poor numerical accuracy of the result. tgammal remains undocumented. As it is unlikely that theraven@ will document the nature of his kludge nor the existence of tgammal, I have have prepared a patch that documents the expected numerical accuracy in BUGS sections, and have also documented tgammal. Index: msun/man/exp.3 =================================================================== --- msun/man/exp.3 (revision 2046) +++ msun/man/exp.3 (working copy) @@ -28,7 +28,7 @@ .\" from: @(#)exp.3 6.12 (Berkeley) 7/31/91 .\" $FreeBSD: head/lib/msun/man/exp.3 290606 2015-11-09 10:41:27Z ngie $ .\" -.Dd November 9, 2015 +.Dd December 8, 2017 .Dt EXP 3 .Os .Sh NAME @@ -180,6 +180,15 @@ then \*(Na**0 = 1 too because x**0 = 1 for all finite and infinite x, i.e., independently of x. .El +.Sh BUGS +To conform with newer C/C++ standards, a stub implementation for +.Nm powl +was committed to the math library, where +.Nm powl +is mapped to +.Nm pow . +Thus, the numerical accuracy is at most that of the 53-bit double +precision implementation. .Sh SEE ALSO .Xr fenv 3 , .Xr ldexp 3 , Index: msun/man/lgamma.3 =================================================================== --- msun/man/lgamma.3 (revision 2046) +++ msun/man/lgamma.3 (working copy) @@ -28,7 +28,7 @@ .\" from: @(#)lgamma.3 6.6 (Berkeley) 12/3/92 .\" $FreeBSD: head/lib/msun/man/lgamma.3 282015 2015-04-26 11:35:07Z bapt $ .\" -.Dd September 12, 2014 +.Dd December 8, 2017 .Dt LGAMMA 3 .Os .Sh NAME @@ -43,7 +43,8 @@ .Nm gammaf , .Nm gammaf_r , .Nm tgamma , -.Nm tgammaf +.Nm tgammaf , +.Nm tgammal , .Nd log gamma functions, gamma function .Sh LIBRARY .Lb libm @@ -76,6 +77,8 @@ .Fn tgamma "double x" .Ft float .Fn tgammaf "float x" +.Ft "long double" +.Fn tgammal "long double x" .Sh DESCRIPTION .Fn lgamma x , .Fn lgammaf x , @@ -106,9 +109,10 @@ but the caller must provide an integer to store the sign of \(*G(x). .Pp The -.Fn tgamma x +.Fn tgamma x , +.Fn tgammaf x , and -.Fn tgammaf x +.Fn tgammal x functions return \(*G(x), with no effect on .Fa signgam . .Pp @@ -166,6 +170,15 @@ For large non-integer negative values, .Fn tgamma will underflow. +.Sh BUGS +To conform with newer C/C++ standards, a stub implementation for +.Nm tgammal +was committed to the math library, where +.Nm tgammal +is mapped to +.Nm tgammal . +Thus, the numerical accuracy is at most that of the 53-bit double +precision implementation. .Sh SEE ALSO .Xr math 3 .Sh STANDARDS @@ -174,8 +187,9 @@ .Fn lgammaf , .Fn lgammal , .Fn tgamma , +.Fn tgammaf , and -.Fn tgammaf +.Fn tgammal functions are expected to conform to .St -isoC-99 . .Sh HISTORY -- Steve From owner-freebsd-current@freebsd.org Sat Dec 9 02:32:03 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5FBEE98DCC for ; Sat, 9 Dec 2017 02:32:03 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) (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 8D8B46FE12 for ; Sat, 9 Dec 2017 02:32:02 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id NUvhe3eb0dX1SNUvje2WLE; Sat, 09 Dec 2017 02:31:56 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB92Vro5009918 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 8 Dec 2017 21:31:53 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB92VrnW009917; Fri, 8 Dec 2017 21:31:53 -0500 (EST) (envelope-from lausts) Date: Fri, 8 Dec 2017 21:31:53 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171209023153.GA9904@mail.laus.org> Reply-To: lausts@acm.org References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfPhdCKfEZ2GwWQ6wfc//Q3pEkGDibPrIQ7x+jjUy1ZrwN8osvX1NimrZ+s0G1o4zDQo+dF0qHaytR3vEx5IKdfdv/Us/WVB42jcGXxozwYBmIjGhzCgu GEZdqEUS88JZ06i60b2u5t3ZGjb62Cmap4NC+wPeeHi9aecJUwSBuIuLAb+LS0gpz5fjKmCP0PFFho3pJ1q018OtjV2EpAIQxA0= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 02:32:03 -0000 Warner Losh [imp@bsdimp.com] wrote: > Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've fixed > it in r326714. > Warren: I just completed a buildworld on r326720 and it failed to boot again with a hex dump and BTX failure. I can take a photograph and post it somewhere of the hex dump if it would provide additional information. I can also send you an email with the photo attached. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Sat Dec 9 03:06:13 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D90AE9A72C for ; Sat, 9 Dec 2017 03:06:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D4D671443 for ; Sat, 9 Dec 2017 03:06:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22f.google.com with SMTP id d137so7858711itc.2 for ; Fri, 08 Dec 2017 19:06:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ocEEbGqCMOoxFcQQdX2DZZ5vN/YhZNSQfRSxFW9276Q=; b=Z6dU6ln2Zxu5veYBiJQnJB9j9NZJYpcjqHR2jONE1CWOMSTIusSeYG+0F+NfqRrvQH GALL0kySr7P0MbAnsNxYk74Yfvl3IFTdVS/XzdZYSiD+vlsyxxCyjeyRmubsGD2H70q/ 0YBnfIJ4oZKYtg5H6y3teOPDekg6MNj9NAXq9vRABxVaPidRIAJON+SSzzpf11eF1Dgp NfkcZ6UTBZRm2EhEADu80ze6kDOEFIvom9Iv7qRjZDgSB7uM4bC0J4QeF/IFzrR9HW0D yPWURfME9d8UD0GkHhWp59RNxJTUTArZ9JML+LDtMl8PtBs1FmaiO8D/DouqqmHYYi74 IU8A== 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=ocEEbGqCMOoxFcQQdX2DZZ5vN/YhZNSQfRSxFW9276Q=; b=jUExthHPoav8EsGbZZYE2rvWwQZRgpVDd+4nr2uC7yqnuSm7KycRcLMziC5+VAkXz6 1Shw349b/dMtu12QyhQ9t+Ekv9HNSlj9FoizzNKJBgSYsHwFA9naAy2S0ptjUcQOadxJ xu2wDgy7mB1i848KtDa6/FHhUDfoFDlyAdutV/mvq0vh8eDWz1hkGSCd27JjJZxTdyXC SW43wnpklhRXSXzD95yDEjeTenu015/e+AQSVFvIQIRDYSiRuLIrS3hZVEanHGTXZBfj hPrUZWUL2pPTjbA5fmO2R8RiaJ7qvEtosEbAegu/2Py8NVVe4Z11Nf1p2O/qKZKOxD+Q P72A== X-Gm-Message-State: AKGB3mJza+O3aLJe5bUPPsg3HNzIHQof+pOF3gl0Mt5SRVoXFxDzCyPI PlN1S23+xRMDfek8CMRwf0knkZD3fUP2r/exO5YvIg== X-Google-Smtp-Source: AGs4zMZq36dHJd4GsglWoLGjoUNzLsKMP+9qv/sZ+eSgXc9Yp4AxmxpP/W/HGQU1nglPlM4E9YRlSbprltqWvf3unIk= X-Received: by 10.36.147.193 with SMTP id y184mr8046675itd.64.1512788772321; Fri, 08 Dec 2017 19:06:12 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Fri, 8 Dec 2017 19:06:11 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171209023153.GA9904@mail.laus.org> References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> <20171209023153.GA9904@mail.laus.org> From: Warner Losh Date: Fri, 8 Dec 2017 20:06:11 -0700 X-Google-Sender-Auth: qjFUf61r1cOueHjlHmFLWKKVC1g Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 03:06:13 -0000 On Fri, Dec 8, 2017 at 7:31 PM, Thomas Laus wrote: > Warner Losh [imp@bsdimp.com] wrote: > > Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've > fixed > > it in r326714. > > > Warren: > > I just completed a buildworld on r326720 and it failed to boot again > with a hex dump and BTX failure. I can take a photograph and post it > somewhere of the hex dump if it would provide additional information. > I can also send you an email with the photo attached. > > Clean build? Warner From owner-freebsd-current@freebsd.org Sat Dec 9 03:57:14 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B792BE9CC02 for ; Sat, 9 Dec 2017 03:57:14 +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 855E573820 for ; Sat, 9 Dec 2017 03:57:14 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1512791826; bh=V9mWPK/rbEn7GGQzrDDxo96w3e2BcOfWYAiJCPg WcYE=; b=cjNAtXSvopLK5IkyRVictugFz/ckjx4OlI7giTs9Gz8Kh615Q6TcODj O2D91Ywc2chIJCqSpy0vPf4OhwN/yiJ4oORzR+YYmg5ZeJCmVM+rIGL/Euj7CykM r5LQOuOsS8d/vLR9e6BGF1rquZ98HVyl6QrRIoTg1Ur9js5sfQ0Y= 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 39E6D7C14 for ; Fri, 8 Dec 2017 22:57:06 -0500 (EST) To: FreeBSD Current From: Michael Butler Subject: reducing build times; selecting specific clang targets Message-ID: <4ff42e67-c045-4255-a96a-bcd3fb8d116c@protected-networks.net> Date: Fri, 8 Dec 2017 22:57:06 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 03:57:14 -0000 As clang builds for multiple targets unconditionally, it takes *days* to build on one of my devices (700MHz Pentium-3). Is there a way to restrict the build targets to i386 only? If not, can we implement one? imb From owner-freebsd-current@freebsd.org Sat Dec 9 07:51:31 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC2A8E823F0 for ; Sat, 9 Dec 2017 07:51:31 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A35C7B723 for ; Sat, 9 Dec 2017 07:51:31 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-yw0-x230.google.com with SMTP id y187so5318697ywg.6 for ; Fri, 08 Dec 2017 23:51:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1mODC+zptByOI+mpUt82ktSvrrJTtPzK22zKjpcEHck=; b=wbcqwRaNclBxEP/ODiccLfUx2f2t2QAW3UNkeErE4rjEjsGqs2X0ZgnDBZLmLY8P1N BqJc3tH79XZDJPsDK8qCF8adKVci51YtLOgTp3gAe8JR0r5TkVpKULinJ1LClKqxTlol zJeU6CgMN9BTs0K2DJkREMnw28iZKr3hrPCmnXn0RdlBN3Gd++YtfZPBigdBGvesjXgD OccphDXLN7Ke4lbX3k0KTu6iblUOzwef2X4ZcXWmkr/ARmupq+KDhcjpcVGCHP3SISfz rLu26mp4O54fTq4t5gaaK9S0S/Oh5fMwDfQd6A7ftuBmsyWENOOBI0qj5+P04BZnuC7D G6YA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1mODC+zptByOI+mpUt82ktSvrrJTtPzK22zKjpcEHck=; b=LSiUoQP8q6OocxvxNCCccHzKu2fgontFJhp21xn4jvqEu0BGzZzl5Q36CfdfIBzXXj mtGo7W6+zLjgDIitqVbHdcrYagt7/6mJoSI8XHFc4GWXI2SHNVtspNvK0oJKrdtBLTVg FzOu1VtS9av5OItRnDLe+8VVn3OQvLrt7d/Iqq8dGdzdoHX71C29PM8JHMmPUpZzHspI NOL7gc3l5MN+ifCpPZXPUTq8gX+opJFKkQugcOuUROkBSkCn0Cc2yYkO7401iY/yJRBg oIeZ9bCSs3Oydq7DnQPGmXHc5EsPXNjSDr7KuQTLFAruvs4+D6bbCEqMuKnLxUyXvR+e 5Tkg== X-Gm-Message-State: AJaThX5bzdQu3TJbLGCDQnOboT2kUek55NCG/RbdrPQufvwJ2uahJWCK Qfhpxbts8B8cuI8rB2pEUS5IIv/XPl5BzDj5PhsMRQ== X-Google-Smtp-Source: AGs4zMZPZ18GY3bEUmziZwhhzco073xlzRPKvaoTfDMATomgyhn8f9rE7UPAPbOTucJDRfd8O/EcRR13RZl0DTxCDa0= X-Received: by 10.129.131.133 with SMTP id t127mr23397804ywf.314.1512805890459; Fri, 08 Dec 2017 23:51:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.85.17 with HTTP; Fri, 8 Dec 2017 23:50:59 -0800 (PST) In-Reply-To: <4ff42e67-c045-4255-a96a-bcd3fb8d116c@protected-networks.net> References: <4ff42e67-c045-4255-a96a-bcd3fb8d116c@protected-networks.net> From: Ed Schouten Date: Sat, 9 Dec 2017 08:50:59 +0100 Message-ID: Subject: Re: reducing build times; selecting specific clang targets To: Michael Butler Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 07:51:31 -0000 Hi Michael, 2017-12-09 4:57 GMT+01:00 Michael Butler : > As clang builds for multiple targets unconditionally, it takes *days* to > build on one of my devices (700MHz Pentium-3). > > Is there a way to restrict the build targets to i386 only? If not, can we > implement one? Regardless of the discussion of how and whether this may be implemented, do take into consideration that the target specific bits in Clang only account for a minority of the build time. It is not as if Clang is literally built multiple times, once for every architecture. The build will likely still take several days, even if this got fixed. Have you considered doing builds on some other system and copying the results over? According to Wikipedia, they stopped producing Pentium III CPUs 14 years ago. Using these systems to do actual builds sounds like a waste of electricity. -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands From owner-freebsd-current@freebsd.org Sat Dec 9 13:40:21 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83AF8E8B96D for ; Sat, 9 Dec 2017 13:40:21 +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 4E1A96597E for ; Sat, 9 Dec 2017 13:40:20 +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=1512826818; bh=1yk4iW0f APk0hO7YS6xZA5/15t+8vOdd/xpEgVYJzAY=; b=SjPdfB4IGh7orDqFoGFFRXA9 yxkJDj5OdrsRFwKME5DX2JrhU1X0IonZ3ccM3p7yQinkvKaBKxjUqrUiYddANZ5s EYbpzP6egeJvjZNhAO8928Cq+lZRDcunweyI3z2EEzEpkLwwxbbJ9e5SzSujeIeu 8xcg4ELSTlzNh7/85Q8= 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 D44CB9D64; Sat, 9 Dec 2017 08:40:18 -0500 (EST) Subject: Re: reducing build times; selecting specific clang targets To: Ed Schouten Cc: FreeBSD Current References: <4ff42e67-c045-4255-a96a-bcd3fb8d116c@protected-networks.net> From: Michael Butler Message-ID: <8a3b8f49-5e10-09df-3682-b411a481f001@protected-networks.net> Date: Sat, 9 Dec 2017 08:40:17 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.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-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 13:40:21 -0000 On 12/09/17 02:50, Ed Schouten wrote: > Hi Michael, > > 2017-12-09 4:57 GMT+01:00 Michael Butler : >> As clang builds for multiple targets unconditionally, it takes *days* to >> build on one of my devices (700MHz Pentium-3). >> >> Is there a way to restrict the build targets to i386 only? If not, can we >> implement one? > > Regardless of the discussion of how and whether this may be > implemented, do take into consideration that the target specific bits > in Clang only account for a minority of the build time. It is not as > if Clang is literally built multiple times, once for every > architecture. The build will likely still take several days, even if > this got fixed. > > Have you considered doing builds on some other system and copying the > results over? According to Wikipedia, they stopped producing Pentium > III CPUs 14 years ago. Using these systems to do actual builds sounds > like a waste of electricity. > Far less than the electricity consumed by an entire planet's worth of BSD systems building for targets they'll never use. The target system is in a remote data-center to which I have limited access and is the only remaining one of its type in my network. The old installer used to be able to select a set of source archives from which to update but I don't see that functionality in any of the current tools. What did I miss? imb From owner-freebsd-current@freebsd.org Sat Dec 9 14:12:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19542E8C716 for ; Sat, 9 Dec 2017 14:12:58 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) (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 D366C66C58 for ; Sat, 9 Dec 2017 14:12:56 +0000 (UTC) (envelope-from lausts@acm.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id Nfs3ejKEqdX1SNfs5e5lEk; Sat, 09 Dec 2017 14:12:53 +0000 Received: from [192.168.1.100] (presario [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB9ECoIl014933 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 9 Dec 2017 09:12:51 -0500 (EST) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host presario [192.168.1.100] claimed to be [192.168.1.100] Reply-To: lausts@acm.org Subject: Re: GPTZFSBOOT in Current r326622 has problems To: Warner Losh Cc: FreeBSD Current References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> <20171209023153.GA9904@mail.laus.org> From: Thomas Laus Message-ID: Date: Sat, 9 Dec 2017 09:12:50 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfMdlIz2sGvvvE3kGa1FbdsNPNeREH7loHzWYjvPmFav547hK8o0bb7JOtKLrDDPl+xelUEYjl9FhG/WYyqA0GWifsPNK6DtLbrYKoVK2n1WkLLJ0hJlf UtsiDQsgIJXrlXJtKlgQ4SJk1enOuQHHQH9OXzTZLkrWipxJDpVqyIhwsuv5dP3DL+caU9xiWE9a5C7D3EOHoRSxc4gZR+Ejf5A= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 14:12:58 -0000 On 12/08/17 22:06, Warner Losh wrote: > > Clean build? > It was a clean build. I performed a rm -rf /usr/obj/* before starting the buildworld after cvs updating to r326720. A couple of notes on my hardware: I am not using UEFI and my CPU is an early Intel i5 Skylake that has the Silicon Debug flag turned on as a default. Most operating systems including FreeBSD turn off this flag during the boot process because of security concerns. Since BTX is very early in the boot process, the computer is powered up with SDBG turned on. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Sat Dec 9 15:24:59 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD676E8E33F for ; Sat, 9 Dec 2017 15:24:59 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) (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 7C98768EFC for ; Sat, 9 Dec 2017 15:24:58 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id NgzhenkCWdX1SNgzje6TQm; Sat, 09 Dec 2017 15:24:52 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vB9FOn1E033109 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 9 Dec 2017 10:24:49 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vB9FOn3j033108; Sat, 9 Dec 2017 10:24:49 -0500 (EST) (envelope-from lausts) Date: Sat, 9 Dec 2017 10:24:49 -0500 From: Thomas Laus To: Warner Losh Cc: FreeBSD Current Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <20171209152449.GA32688@mail.laus.org> Reply-To: lausts@acm.org References: <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> <20171209023153.GA9904@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p5 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfFt3VpkbyKjl1uSV1kUsnOLO0ptyC0z1d7zfeQd8gHeSSdZQEmpJCMS4lIOh3jbrh6CaWYyAqEvws+8r9MSlVrZuxWau/LBQm8J36jUXKcGkOA/yjBUw 6jT9MVk0YfxMvTI/w7fTNDYulCHKffsboREne8hhlMAAthopx7fI77dBSBR1pqF0DXSToS3e6q01WsyAFS/Pbdi9s3n8XH2gZig= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 15:24:59 -0000 On 12/08/17 22:06, Warner Losh wrote: > Clean build? > Here is the contents of my loader.conf: loader_logo="beastie" #Desired logo:orbbw, orb, fbsdbw, beastiebw, beastie, none aesni_load="YES" geom_eli_load="YES" kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" zfs_load="YES" Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Sat Dec 9 15:47:47 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26084E8F190 for ; Sat, 9 Dec 2017 15:47:47 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from sonic304-25.consmr.mail.bf2.yahoo.com (sonic304-25.consmr.mail.bf2.yahoo.com [74.6.128.48]) (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 E26EF6A007 for ; Sat, 9 Dec 2017 15:47:46 +0000 (UTC) (envelope-from pfg@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1512834464; bh=GHQ/TlvA5sen2RDwAIsqzslcr0IqXLiXQH5mJR93HaM=; h=To:From:Subject:Date:From:Subject; b=l2RZ0PBfmapn60Y4K796WBF+E3kEqu53ioBzYYthTH+ExaJnPTnkk1iCfpZCIA+QA3kMOhne/jcDKUbGrhD2pWzkbrEvGkYUgUITQ2+rAlx+gK5dhavyGLw3vkGcptf3EfeXddr446jLryUJ0l4evCdVDKvDAk0u8Fqot3PTTqp+c9QmK6I/cGVuQ9DOFpWmsizvwVbht/dcaYhEiBVGLVnrFx0PHiTx9fLscrLr8ppT1PT9Bu4HCpTzHXF+5EKtowKdpBBGWxfNf/7Kq4H9Gdr1mrNWppLIzOqyjUGFuNjNobo2B40vkMi2cUZg9LkzRmHcn/I/rGF5DMS9Z+jO8w== X-YMail-OSG: 5jkAQosVM1kMuRiWxzzQMY0dxT0QXOF5t4C60lbgAJND2gPMK6EDx4GuEGN7doP pOP3uRhS3FrjPZxceUQbaEuVb6GDJmihV_CIDUNWtJObSTuYqp3xFcZAdj4wDTKZ5uAQWPQXRkyM QO9c9OMqzYG2ck7ogD5Tv2lGyzWnV9ZXR239b8hg7L3NewKEdsfO1.epcM9ug1uKZpHFYB9puUW9 3dx_MjVfMeoG7Y9ffbY9rMgE_YN1gAa5S3jfCymoxBLta_EIei2h8PtOocA8dZ9xzf7lTMBooRR6 LvszhbD7BNZIrEJNgDc3za2Aw9_0a_ttIX5LyerW2Bv2Sr6tSyNBVJh6cWK98PpICNFxft8yvJj1 6bNQnwvQ844NHzmoqvwjwV18mwSRaAmYyRBE228CMZO5uszvd1ry3IApEgzg6VdgAQDa6vNDhZCp MtHoXeUJ4YuIRcAvcTBGACSyfEzyypzOjLgx5TAguL3DRyQ5vegi.gscyUdKHKllizjTPELDt Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Sat, 9 Dec 2017 15:47:44 +0000 Received: from smtp106.rhel.mail.bf1.yahoo.com (EHLO [192.168.0.5]) ([98.139.231.40]) by smtp405.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID -1098369153; Sat, 09 Dec 2017 15:27:29 +0000 (UTC) To: Michael Butler , FreeBSD Current From: Pedro Giffuni Subject: Re: reducing build times; selecting specific clang targets Organization: FreeBSD Project Message-ID: <92c1640c-a332-c4c7-6adf-57935fc2ea12@FreeBSD.org> Date: Sat, 9 Dec 2017 10:27:32 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 15:47:47 -0000 Just my $0.02: > On 12/09/17 02:50, Ed Schouten wrote: > > Hi Michael, > > > > 2017-12-09 4:57 GMT+01:00 Michael Butler : > >> As clang builds for multiple targets unconditionally, it takes *days* to > >> build on one of my devices (700MHz Pentium-3). > >> > >> Is there a way to restrict the build targets to i386 only? If not, can we > >> implement one? > > > > Regardless of the discussion of how and whether this may be > > implemented, do take into consideration that the target specific bits > > in Clang only account for a minority of the build time. It is not as > > if Clang is literally built multiple times, once for every > > architecture. The build will likely still take several days, even if > > this got fixed. > > > > Have you considered doing builds on some other system and copying the > > results over? According to Wikipedia, they stopped producing Pentium > > III CPUs 14 years ago. Using these systems to do actual builds sounds > > like a waste of electricity. > > > > Far less than the electricity consumed by an entire planet's worth of > BSD systems building for targets they'll never use. > > The target system is in a remote data-center to which I have limited > access and is the only remaining one of its type in my network. The old > installer used to be able to select a set of source archives from which > to update but I don't see that functionality in any of the current > tools. What did I miss? freebsd-update(8) pkg upgrade that would mean running a release, but it makes life so much easier. Cheers, Pedro. From owner-freebsd-current@freebsd.org Sat Dec 9 17:56:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A99FE92B15 for ; Sat, 9 Dec 2017 17:56:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62F946E7CA for ; Sat, 9 Dec 2017 17:56:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id e204so5565402iof.12 for ; Sat, 09 Dec 2017 09:56:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Jet1KdCLOv1nwXWXn6KhgBZnA6Vd+GRQTqpyK+81ALs=; b=b8TEcFYu9TkVc8oUHBM97N5rJzOFWqL/PEbKR7GWiDWIPqSwqkRFfBmQVXecjvzyt9 vsj1uWKGZTUJI8R0wV4rT8Us05S75st95MSPPCZqapmDbTVaorZL7GeKvExMm1QmerwT PmtKaJkJdIrYmwZbXgZzai9Pqa4EGN25xCaGnSFKVB1F9lfSWwcPnZ535iMf+8O/llM5 tcPu+xMEmdh4kBXrq8VQImMT4lzRSS8nPBArkVt6dwRMqHhJg3BTJ81sg285hjXc3dvU krC3wlf4ch8CjrzlFgP2J3+Ke+2vBm7iRcltfZxRqXYD5JXyBPMuvBr49QHnQPUhcajE ObQg== 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=Jet1KdCLOv1nwXWXn6KhgBZnA6Vd+GRQTqpyK+81ALs=; b=Nvn13Q75S9WXFPydlrvwebB22djJ1M4K2dvGG463jZNLBObk9Z0bO3kiHcHo6zzKTI onecc8GpBGFHJXlfLh8yk7gNYOL4y8Q9qR83jHHXlX7Did3L5zH4l0biDZyKMvFtzMyq 2GJGWY20iF/aMGWqYX/JFy9xsOeiW+S+qnrVxvAEkPcKHQiGAVGTUEvZpENiJic200AF YgvDvnZiG/coiJqRE6Qabm36f+Y6S48lk3xioF/eBfqiPITXZJ+VYirTiZTcXkDiLnoh 0YXsoVIY1UdHy6+WGgyjqHpsg2IBdJMHWBVRR8kFdw7gJ+K5YTWE+2Siej0wntdscQpQ +NDA== X-Gm-Message-State: AJaThX6gqn+N9gasFf5OxNTKR9qVombiM4q/lkpp9BBaI5euLYifqK6g oHTIQXMTZLMA+CoU/pIOoQ0ZLKYKlYoqN1VGuKw5qg== X-Google-Smtp-Source: AGs4zMbGbLnxtIAG50Ysiapwq+LC05s5abLI9G+CH3EH1770kvYfDTQzwrx+Bztt0i6zT6TQavglhRWt8OL93udvBvc= X-Received: by 10.107.30.81 with SMTP id e78mr45548739ioe.130.1512842181308; Sat, 09 Dec 2017 09:56:21 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Sat, 9 Dec 2017 09:56:20 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> <20171209023153.GA9904@mail.laus.org> From: Warner Losh Date: Sat, 9 Dec 2017 10:56:20 -0700 X-Google-Sender-Auth: SgVPvfbawob7ZcvHBJ0GgbrH8JY Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 17:56:22 -0000 On Sat, Dec 9, 2017 at 7:12 AM, Thomas Laus wrote: > On 12/08/17 22:06, Warner Losh wrote: > > > > Clean build? > > > It was a clean build. I performed a rm -rf /usr/obj/* before starting > the buildworld after cvs updating to r326720. > > A couple of notes on my hardware: > > I am not using UEFI and my CPU is an early Intel i5 Skylake that has the > Silicon Debug flag turned on as a default. Most operating systems > including FreeBSD turn off this flag during the boot process because of > security concerns. Since BTX is very early in the boot process, the > computer is powered up with SDBG turned on. OK. I don't recall seeing a screen shot of the entire boot. Can you send that too (privately if you like) so I know exactly what's failing? Is it gptzfsboot loading /boot/loader? Is it early in /boot/laoder or ???? Warner From owner-freebsd-current@freebsd.org Sat Dec 9 18:41:41 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 972ADE94380 for ; Sat, 9 Dec 2017 18:41:41 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDCCF707EC for ; Sat, 9 Dec 2017 18:41:40 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.223.140]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lu874-1f5M3j1vCY-011QO8 for ; Sat, 09 Dec 2017 19:41:37 +0100 Date: Sat, 9 Dec 2017 19:41:29 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Subject: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard Message-ID: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/A.e9KSUFZxBFML=ZUmSJPof"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:pIymIN50q4Izv0nu15RYvP9Xb1oqLIdIVoVBiXvJi63vBSWEsSh AQ/dloC4VDWQS6VO79RozztG0C4FpL/ktDIHKgQxNoWZXb2aWozk1jROoQocJsOFFZEPMFa gWS6wSiSp1ZREh5IGLSd5cqSzSrqzf3yh0atW9YJVLTJcVjZtx3H9p/lwEPBW564GAnkXvo QIcHDo14296g4uOfX3s9Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:VzETTeDIiE8=:p1WpVA9hbF7VhKlFxDSrD0 EJss1LVHJXZ6ky6A0CzvDb0IakG3IGG0D7ZPduqbNYL5jNMyO+BGeaH4xluEWLW2G/iEsLktm suo0Y/NB01A7ix9AttcQQSRZ3zzL2FrdbJS6WjodhOT5o2kE+fZejofHQ0hmFrKDoYsATevVc mxdJOvaZK6z4FtqKwKR6W3vVnVfh/9AN53PodlACT55gv0CdhX1d4Zq9BZ+ShU5QgPna/KL7z Mm+kvgMkQ68RICbIBC7xO0sYJCf/TYTFDrIBhmlnomjnw+OqILpjLZG7TC2F5+It4Xq+BS1gl ez8BegP9bbRTvtHiV/KLH2ri/Gq0agtzWklBQrukK28XR4f2W4VUHJSki7bbECRRrrVKBsmKt Sbghs5Xa7sxBxz/LYshdy/AwFk0nTngyHqcFNAJhz2yExA2K+4rDwdWZxJPg8cPAweJUyRubB wRg0KMx3iNQLSQKdCGchjS3PNCq/1yRgBX3IogLn1bGuoTtxySOafyq7rJdn8FbhWTpU2Hylb 8vPUe8e57uzzuC6ik98Af4UzzItPhJg+SJx8D0NTQLjGz6y+6iFyfKvXCLv3XL+XAraIn8BRN uJQCtxPNK8XtuHfgnwhTkQVkIAArYyRgwuIhqEY5kH5O/tNvAWCk/TJbsRZL8V/09GiaCSiIB xnxJVjxedbhV322QzqwROcrSvp8raEIEiuWphU0dg21pUZ537kqNBAvPVMid4qCZSJ4LKYr0B /oBDcQcbhlXFY1NpURL3pfLYgqaOP/0YUcULQPQMGMloBknCVL38YfyPXd/GfRefM/VtWQUDo UXncedmBYUsMfHlRIfdoGxkLtjycQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 18:41:41 -0000 --Sig_/A.e9KSUFZxBFML=ZUmSJPof Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to boot, it= gets stuck at the very first messages on the serial console prompting Consoles: internal video/keyboard and then nothing more. FreeBSD CURRENT FreeBSD 12.0-CURRENT #52 r324234: Tue Oct 3 11:00:53 CEST = 2017 amd64 works fine. What the heck has changed? Kind regards, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/A.e9KSUFZxBFML=ZUmSJPof Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWiwuWgAKCRDS528fyFhY lLflAgClomkekrVXURKE89CE3OjwB3pQoxMu/MO2Z5tNPL+uTxhwxLJxdsgGL/IK LiBy0za7I7fUOnNxMhkWWeWKV3o6Af0ZfUlmqd4w5l2JisQHfDcwi+vam5ttzRoJ gdVe+As4ObbfeBZqTalSbd0GeTtjkhntd3nn60UBxx0q0nTTzM/I =MW52 -----END PGP SIGNATURE----- --Sig_/A.e9KSUFZxBFML=ZUmSJPof-- From owner-freebsd-current@freebsd.org Sat Dec 9 19:04:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6237CE95078 for ; Sat, 9 Dec 2017 19:04:58 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 219E771783 for ; Sat, 9 Dec 2017 19:04:58 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-yw0-x230.google.com with SMTP id m81so6016323ywd.2 for ; Sat, 09 Dec 2017 11:04:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MAXDmP243LiJ5INslK/Z2PZRWDMplsBERNTSxbbRUEU=; b=VjKUAWtlw9rPqpiNooHMaqLMqLd7lIGxc7kHUUURH37m2ZXcUhQqH9uUl/1rtKHwwP QNGwKS6mUG1hY7RTMILrW5Dc+D3YN3wfFDb5HOHcxuQKg2y7ghxoHSX5Dodv48dantjJ T0DiGs2l7YEAahxg3ug3NOqcZM1spGC/+RKgCSgc5oNd2ls4agOiZX6+IkNhvOngHrF/ lLf+xe1gJP489C5KWHKBkZlmInY0pP26j+c/Ubc0qO5jHuetg9AAQ1rSkTxCgiurrL+x ghN61BUt6sVEODwPMf5Re2ruxyIsfcc+NpXVyts5sok5zg9N4ptvCHXLXwMlhb0K00Ij GbDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MAXDmP243LiJ5INslK/Z2PZRWDMplsBERNTSxbbRUEU=; b=swXgdt9ZtxvAmJU/+sIWKCwHo8mMyPNI8aoE3raUt3oTA8XmeAQWGrQIojPcCUpOZZ 8617W26Yztx/nEbcKuaTFYfSslyUf3OffK8V5VPYeq1mJ+nkzzqxtCtXqjLoshfCWC4+ TVysHIJwTW1koHPvhe0Vo/iao4toOCgkFUlu0KCtXN2ZnUGIW1sscCZq8nSieYMs0j4N Ax0Sq9swtYIWbTvqgl5adLWQoXLlFzn90VV3A4izYFZXbuTmI+hAxv9qaqG6RlsEpFuU GsTvd5gt46bq5/Vx+DbYbsbizlLEw+O8uUF+LHA8tj6mVdGlrCp3IP0jSsRUq2M+1nR8 IwYA== X-Gm-Message-State: AJaThX7qfcDYyWX35mJZThHTS1nXFJqnexS9JPVTjwWShBksfJk0tDKp IXKFVrKMIKjA5EBmqlhtKmbkbZHBd8RJOSuIqtofY4W9 X-Google-Smtp-Source: AGs4zMaIyC/RSvOvtIIANNrby2VXkUhSSEfpX2nO3WgjuKLn3eAJXpjbJzBhEkDQSXSb+cNSl+Fe5nPy9q1q2oIdaiU= X-Received: by 10.37.14.68 with SMTP id 65mr22485739ybo.310.1512846297036; Sat, 09 Dec 2017 11:04:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.85.17 with HTTP; Sat, 9 Dec 2017 11:04:26 -0800 (PST) In-Reply-To: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> From: Ed Schouten Date: Sat, 9 Dec 2017 20:04:26 +0100 Message-ID: Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard To: "O. Hartmann" Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 19:04:58 -0000 2017-12-09 19:41 GMT+01:00 O. Hartmann : > r326734 fails to boot, > r324234 works fine. > > What the heck has changed? Could you please try to bisect SVN revisions to figure out which exact commit causes the problem? -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands From owner-freebsd-current@freebsd.org Sat Dec 9 19:13:45 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A75AE953BD for ; Sat, 9 Dec 2017 19:13:45 +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 F3E9871C5D for ; Sat, 9 Dec 2017 19:13:44 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.204] (p57BB4B2C.dip0.t-ipconnect.de [87.187.75.44]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 94154721BBD15; Sat, 9 Dec 2017 20:13:42 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard From: Michael Tuexen In-Reply-To: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> Date: Sat, 9 Dec 2017 20:13:38 +0100 Cc: FreeBSD CURRENT Content-Transfer-Encoding: quoted-printable Message-Id: <728FB521-24EE-4628-9816-EB3DF0ACA14E@freebsd.org> References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> To: "O. Hartmann" X-Mailer: Apple Mail (2.3445.5.20) 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.25 Precedence: 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, 09 Dec 2017 19:13:45 -0000 > On 9. Dec 2017, at 19:41, O. Hartmann wrote: >=20 > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to = boot, it gets stuck at > the very first messages on the serial console prompting >=20 > Consoles: internal video/keyboard >=20 > and then nothing more. I don't think it is a general problem with r326734. I'm running on the = same hardware that revision (with some modifications to the TCP I'm testing): > uname -a FreeBSD nf3.testbed 12.0-CURRENT FreeBSD 12.0-CURRENT #31 r326734M: Sat = Dec 9 20:03:59 CET 2017 = tuexen@nf3.testbed:/usr/home/tuexen/head/sys/amd64/compile/TCP amd64 Best regards Michael >=20 > FreeBSD CURRENT FreeBSD 12.0-CURRENT #52 r324234: Tue Oct 3 11:00:53 = CEST 2017 amd64 > works fine. >=20 > What the heck has changed? >=20 > Kind regards, >=20 > oh >=20 > --=20 > O. Hartmann >=20 > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BC= r > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 = Abs. 4 BDSG). From owner-freebsd-current@freebsd.org Sat Dec 9 19:17:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87061E95540 for ; Sat, 9 Dec 2017 19:17:24 +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 576EC71E2B for ; Sat, 9 Dec 2017 19:17:24 +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.1.2.20170607 64bit (built Jun 7 2017)) id <0P0P00I00H7PF900@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Sat, 09 Dec 2017 18:17:04 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1512843424; bh=Rg5Rl0Or56kivQz34hd8JwfeZ/zrduSslI0QDeTs7yU=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=ULK629S9Uq7aFblV8sAYpirYCoSLLcBbwUM4gVipMJljo+MuRkIPh+pzJ/akd61v3 7p9YR9It9aXjavzWWdkYstang3Q2JpQpTkhVWVuZn3HmkiBCTrxrRN5M0WHw+L3FMB E4q9Jegw2bvftsVxHLMsfHao2TBpPaiiQ2z0V6uleY6gdznXtmCgHmZgJ1avRtjTUl UFLeEmLGl+8ooYW4DdQ0lbEWfOkDd2IV0qD4yhhCGR4ITpImKDxc7ZOcyI7CCt6rLp 3c+ha7AMdbY+siYhRQpAf535zDuP1RNyMFOrqim0ouSw8qv/Baq92BEjnOtBhNFq/B lypJCAcK246jA== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P0P00811HGAUS10@st13p35im-asmtp002.me.com>; Sat, 09 Dec 2017 18:17:00 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-12-09_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=4 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1712090264 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: GPTZFSBOOT in Current r326622 has problems From: Toomas Soome In-reply-to: Date: Sat, 09 Dec 2017 20:16:57 +0200 Cc: FreeBSD Current , Warner Losh Content-transfer-encoding: quoted-printable Message-id: References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> <20171209023153.GA9904@mail.laus.org> To: lausts@acm.org X-Mailer: Apple Mail (2.3445.4.7) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 19:17:24 -0000 > On 9 Dec 2017, at 19:56, Warner Losh wrote: >=20 > On Sat, Dec 9, 2017 at 7:12 AM, Thomas Laus wrote: >=20 >> On 12/08/17 22:06, Warner Losh wrote: >>>=20 >>> Clean build? >>>=20 >> It was a clean build. I performed a rm -rf /usr/obj/* before = starting >> the buildworld after cvs updating to r326720. >>=20 >> A couple of notes on my hardware: >>=20 >> I am not using UEFI and my CPU is an early Intel i5 Skylake that has = the >> Silicon Debug flag turned on as a default. Most operating systems >> including FreeBSD turn off this flag during the boot process because = of >> security concerns. Since BTX is very early in the boot process, the >> computer is powered up with SDBG turned on. >=20 >=20 > OK. I don't recall seeing a screen shot of the entire boot. Can you = send > that too (privately if you like) so I know exactly what's failing? Is = it > gptzfsboot loading /boot/loader? Is it early in /boot/laoder or ???? >=20 With BIOS boot you can try to press key (space or anything else except = enter) - if boot1 is good, you will get boot: prompt. rgds, toomas From owner-freebsd-current@freebsd.org Sat Dec 9 19:58:47 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BD3BE965E3 for ; Sat, 9 Dec 2017 19:58:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 00F40734AA for ; Sat, 9 Dec 2017 19:58:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x229.google.com with SMTP id d16so5755153iob.4 for ; Sat, 09 Dec 2017 11:58:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=qdhshlw9sSmL6FhpbN+OUiUJX53fwwlg2aUMxcfSx+s=; b=FKhf/myFAk8tobrQnvi2/yGfomsTWYhovZatYtnjhTtNPY60N0yFOjWmqRAlnAbnI0 1CQbjnCro2GUmnYHCwsgqt/z91WXRfgGrumRNqPZJZXRz+91AbKBBG8AjjSf2CEPYJpG bcJrsL/q8qDlIPrkbHYiaDWUJcXE2T8A14r+tALNlmBpPM7CHmI4IWgFOr9uvzDWmok+ b3NGj/knPku3hxbc/nChVvAe77NdNoVGi9uFUClxaUN6Stl+z0jLNS9QyldImWFAQ8zx Y4k7KWIgNVK89pc0B5CUzZ+Of6Nzq4Q9qZLYJfwBmSqnR+7z3lCiWZ8jg9JvROOSiauV bNgQ== 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=qdhshlw9sSmL6FhpbN+OUiUJX53fwwlg2aUMxcfSx+s=; b=B70ZNC+pTNXDJMEQ5k58jSZ/j2vgetNX6N/7mpic2+2gQNqXqyzRfo0NiSHgTUK3br TzZT1gtzvXyUjfuS57VA77g7nSf9O2SPjvptxtMEm2pAUYiXEgndjSPHUMyn7e7WDsyw jGUgZog7Xh/XwVYlbFvG8aayRpEZ0DgUsKhoCYQdOUo33BpZF44fGOnMM73RZenc5Cli ku+c9OEIBAFTCApZ5NMhKxwWwG/WBjufRWRbbgWrAPOiTKT7jkWfhy0CSD4KYeqx1CWT BynhCAcOLP7hFRPsSgKulIShq4CfqvTbhdvlkZ6XUOxuisGJA0Tq88Pj0qxp3Ml8AG3Z n1qg== X-Gm-Message-State: AJaThX4cCTNZHuD4jMFIxIF3h2++rdkeYltZkmNBrDWm7889CgJ79hh0 OQ4DRGv/eReJIs3qP8PDtMUV0EtXG8be+uQn4WUKFA== X-Google-Smtp-Source: AGs4zMaDQT/7roFutPEmJl0M4hVGeCtvCovYUIJu/ofKKRaPGf0DmKJQzQvN8HkJZghInwQT2KrrhqEDONEE5Xy69UQ= X-Received: by 10.107.81.24 with SMTP id f24mr46605045iob.63.1512849526091; Sat, 09 Dec 2017 11:58:46 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Sat, 9 Dec 2017 11:58:45 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Sat, 9 Dec 2017 12:58:45 -0700 X-Google-Sender-Auth: NBNQgtRn6a9zK1cJ6BV7shppss4 Message-ID: Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard To: Ed Schouten Cc: "O. Hartmann" , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 19:58:47 -0000 On Sat, Dec 9, 2017 at 12:04 PM, Ed Schouten wrote: > 2017-12-09 19:41 GMT+01:00 O. Hartmann : > > r326734 fails to boot, > > r324234 works fine. > > > > What the heck has changed? > > Could you please try to bisect SVN revisions to figure out which exact > commit causes the problem? > I'd start with r326550. And are your sure it didn't boot / got stuck there, versus the output went someplace crazy because I broke reading in some obscure boot file accidentally :) Also, UEFI or BIOS boot? Any of ZFS, GELI or GPT vs MBR in play? Warner From owner-freebsd-current@freebsd.org Sat Dec 9 20:00:14 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3896E96708 for ; Sat, 9 Dec 2017 20:00:14 +0000 (UTC) (envelope-from wlosh@bsdimp.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 G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96F1773627 for ; Sat, 9 Dec 2017 20:00:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id d16so9261381itj.1 for ; Sat, 09 Dec 2017 12:00:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=wUzNP43jRGgBcWDhy+kquBFDp6kKpoVxSHwGlnTfues=; b=aiFP5D1exMRxmhTnzuS9Y1fEOwu/226olmDCpylgJMIn8icHHpXvG84WPkiH+H3WRZ bEdTx+bs0DXbHCkkYIjBuZTaMKaegu9CsNd2RahQAhQvnsaAem4XKFLrv3AyEQq1CZtA T3TybyNj+SYcrTrEi6QWwIuoaGlRPpcfmGaYCMuhno/lLaHqiMHplUDRHaZJD7m1g2PJ QC8KH+FvPgKC0odcm+RGP5tchP7t4ESZmgPjUsgy/SZ67HZX9VvbRKFAQ1oZEX1sHlzQ LUICIfOD8+g923b4qQAva6jjz3mrACDG8KGuqoIh5t+N6PAWGILHNkhvW1GYtIRswryN +hfg== 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=wUzNP43jRGgBcWDhy+kquBFDp6kKpoVxSHwGlnTfues=; b=HBYixXu+vmeDf68k+aN1W8BAi9YSNoi5KzgQyr3Wtsd2z65tqLcKmFEUmT7U2GvhDC ee3N7pa1H55bc283vHHQEY/UXiyz0hk1RQmmBVXKdmG7LhqESlucOr6ImhRLpEJJCQJD lLSqFwFWC6WKD1zYxdphXl6F/9TghhcpfA+b3LUUGEIcD3AobwMJFiueH2+B5NN3dglz 0TAo2+AFSdkGUJAFUXLHiX1NlkPFgwWapgesNY/l77GQLzLzKBfzEageVuCkAhLIVQRP XUJ7Aymsk2Nfz20f0XVqJjsjMyBm4ncOpMwo+iCZglex+JNp+DKeNIoYW22LI4k87fGw 61cQ== X-Gm-Message-State: AKGB3mJAmuVtMt2MRJSa+aSWzeB2i+M/W5pBT7Y9Lf6DGEHsXu7Twit3 l5o6zdEeQu0g66u5//tY+l1/i1AQt8lp8FrsiqV2Jg== X-Google-Smtp-Source: ACJfBosS9wUoEZTQLmi7RqstEyncR7DdpQxHVa98vKDbDL9H+qI0EDal7y3DazG6XA55aN9Z0wG04j2CkUfEoMDNYQI= X-Received: by 10.36.131.200 with SMTP id d191mr3079323ite.97.1512849613754; Sat, 09 Dec 2017 12:00:13 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Sat, 9 Dec 2017 12:00:12 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <728FB521-24EE-4628-9816-EB3DF0ACA14E@freebsd.org> References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> <728FB521-24EE-4628-9816-EB3DF0ACA14E@freebsd.org> From: Warner Losh Date: Sat, 9 Dec 2017 13:00:12 -0700 X-Google-Sender-Auth: f7ONRXJU1xKhBjZG_GFdL5gqyeI Message-ID: Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard To: Michael Tuexen Cc: "O. Hartmann" , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 20:00:14 -0000 On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen wrote: > > On 9. Dec 2017, at 19:41, O. Hartmann wrote: > > > > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to boot= , > it gets stuck at > > the very first messages on the serial console prompting > > > > Consoles: internal video/keyboard > > > > and then nothing more. > I don't think it is a general problem with r326734. I'm running on the > same hardware > that revision (with some modifications to the TCP I'm testing): > > uname -a > FreeBSD nf3.testbed 12.0-CURRENT FreeBSD 12.0-CURRENT #31 r326734M: Sat > Dec 9 20:03:59 CET 2017 tuexen@nf3.testbed:/usr/home/ > tuexen/head/sys/amd64/compile/TCP amd64 > Hi Michael, What's your boot setup? BIOS vs UEFI? UFS vs ZFS? GELI? GPT vs MBR? Plants vs Zombies? And did you update your boot blocks or not? Warner > Best regards > Michael > > > > FreeBSD CURRENT FreeBSD 12.0-CURRENT #52 r324234: Tue Oct 3 11:00:53 > CEST 2017 amd64 > > works fine. > > > > What the heck has changed? > > > > Kind regards, > > > > oh > > > > -- > > O. Hartmann > > > > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3= =BCr > > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 = Abs. 4 > BDSG). > > _______________________________________________ > 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 Dec 9 20:00:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58995E96910 for ; Sat, 9 Dec 2017 20:00:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B9B8737DF for ; Sat, 9 Dec 2017 20:00:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id h12so5757916iof.6 for ; Sat, 09 Dec 2017 12:00:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=gFbAktiq814P4abqxuBY0Bp+DQaqSpf0h78cfL/M9pw=; b=wjpozEMUyIUvZ/ut5j3Jd/P5d+Gz4Y9gnAdEPbPvc8u6R0zCKl5MB1iD2J9BlWDZPB gKxS6yLV8/tvN2hV0e8ISyxfzmoZx8HVPPXV48f3RzYLWfhn3FV2/8TFjndzt/37NrQx NxfX0aUVNI2kebrDcDmh6KsDfWfE1z0QpjfNSzD1+zGUhJlJX+3kCOk5Ux3pEr5LY4Va pywaUik/jxGXQOdq1Hd1mL/41ep1FMPaSxlbA1+3hMugoMXB7ee8+A9IPyoSsn8AE34r ofq4t1sudIBqb1k0wxeLojnTNXqH4xbM9sQIABn2/yycrZ9H5owK7+EHksO3sr52y0Ea FdEw== 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=gFbAktiq814P4abqxuBY0Bp+DQaqSpf0h78cfL/M9pw=; b=rWaVxGX5vXuunVlHZDdVzTP3zpnbhCLnKMiVAzcJ/v96ch07KhEZ+Nk2tpZRKJlKH8 YgNZynujDCWSNkQPJsFa2P2UZRbDCAJcTbU8up8HP6mcbxRaRPz17YxyaHOyhgkrZu4l 5elr00KWUM4HobCkd4VaSODAQZ1MOLvAjmnnvSVxY5OGmw5YqZT4MxMkyG/hfW0x8Ouc nt5zHBkZTLTSLw8wha6+7g5MZGPD+Fr8oUuBDRdqNDqbwrIujXG0hgl9L4YWORA++nOT Oz7cmAZVOABSZfAvqmVxeUfuega7HpliN9WTNbH4Tcz0mKcE/gonSFVy5BNW3cgPmQ9T g3Gw== X-Gm-Message-State: AJaThX5S+UX6qByWQYi4kn2C5eLjEgio4FixasvTfuqcvovbA4cFDKx1 NhuguD263RGcOKYmpOaN1UIwhLqNM71vERyeEc5SNQ== X-Google-Smtp-Source: AGs4zMafHf6c4DdOXraRoT9KKVOYILZFdK3cBof794xGO2Ky4uZL3C+UONHy0zBtKsViQBJV6i6gWdmBLEzREGg5KAI= X-Received: by 10.107.104.18 with SMTP id d18mr43943988ioc.136.1512849652358; Sat, 09 Dec 2017 12:00:52 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Sat, 9 Dec 2017 12:00:51 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Sat, 9 Dec 2017 13:00:51 -0700 X-Google-Sender-Auth: oWx73QAhizpyfpTV_9LO9rTrRTI Message-ID: Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard To: Ed Schouten Cc: "O. Hartmann" , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 20:00:53 -0000 On Sat, Dec 9, 2017 at 12:58 PM, Warner Losh wrote: > > > On Sat, Dec 9, 2017 at 12:04 PM, Ed Schouten wrote: > >> 2017-12-09 19:41 GMT+01:00 O. Hartmann : >> > r326734 fails to boot, >> > r324234 works fine. >> > >> > What the heck has changed? >> >> Could you please try to bisect SVN revisions to figure out which exact >> commit causes the problem? >> > > I'd start with r326550. > > And are your sure it didn't boot / got stuck there, versus the output went > someplace crazy because I broke reading in some obscure boot file > accidentally :) Also, UEFI or BIOS boot? Any of ZFS, GELI or GPT vs MBR in > play? > And did you update your boot blocks / files in UEFI partition or not? Warner From owner-freebsd-current@freebsd.org Sat Dec 9 21:30:40 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 903A1E99021 for ; Sat, 9 Dec 2017 21:30:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 511D3766F4 for ; Sat, 9 Dec 2017 21:30:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x241.google.com with SMTP id r6so9347900itr.3 for ; Sat, 09 Dec 2017 13:30:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=x6w68XtqkqYzTsN+SEDJWitPMhW9aC4jjAdrLnUSfEA=; b=xHHEiPT+XmFhcltzfo8Doy7F0zEbZJvnvroTfCgtpwLLNQ8kkpZ5EJwjjyt8Tjp71m WYTT0evLPwncAAbb6wnN6WlvLIwFskn9Hl0JFgswaSH0W+AlBtrhttccrGsACqYl62i5 er6GPPj8Mbbky5U6Q/qf10s5RfWH04mmJBnLYL+eAefL7SuFXKJQEbM+0k/35duBdxlr KSQRw1tx10D7B5JDXCRF5vms2ouo7+2+OFHbx6/oVz/HEgkLIb3ixpPXMpnej4/tGgJs P+29yGVIY8wSV+r5Ru3o8RshLhjUmK4kWmXFS1UR1IYD8ZS2B8MDvV+FHVsArH00iw+T 2+Jw== 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=x6w68XtqkqYzTsN+SEDJWitPMhW9aC4jjAdrLnUSfEA=; b=Qax9V4uI6Dca+sk8Jy09py9PVk0xXbUmGZsi02FL/vthBwvDMqsXPs442w/fjvy5Py Kh00beTL9m4IWORUcyG0TOAIPYc+TMZbdFhSP02p+dkfDl4gxEUGu698qF76jy8suQDQ cUWCRDOQ72GGxuY8vhcRX1I4QZ+hqp1RBjSdpidy9Pk5kbwrvbxW9jjapwegm34TON10 nBSeHHhZW3Vc0JNr71Ap1+89soy3x1COi4cXVU3UuRm8ls3Fu7q+1jx0kybA8sLmVnZD vREwfRGL5X1H2yeeWP5tSCjoiFfTrzFdKLbVZqZdVJXjXpHa/ym/xYmgcU1r7NE2RbOw DxBQ== X-Gm-Message-State: AKGB3mIMiNnbdTN0rmXoHuvgpdQlhmxKkCuMWWOUTadZFtuBOa/0AZYW hRi2e+0u50wchFmhG1bsj52WFj8BBR50a+Qe5i9Low== X-Google-Smtp-Source: ACJfBovIISKteh3WBumv+XZ2ycEKnHldCERMLfkt57W50733q3UYesr0w1T0kMIRoR5rjufF5Golz2rG/cZeO5uhXRI= X-Received: by 10.36.131.200 with SMTP id d191mr3296856ite.97.1512855039242; Sat, 09 Dec 2017 13:30:39 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Sat, 9 Dec 2017 13:30:38 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171209214746.1debb72e@thor.intern.walstatt.dynvpn.de> References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> <728FB521-24EE-4628-9816-EB3DF0ACA14E@freebsd.org> <20171209214746.1debb72e@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Sat, 9 Dec 2017 14:30:38 -0700 X-Google-Sender-Auth: 8I7AqiQ9nfQgh-vM0PeGfiN18RQ Message-ID: Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard To: "O. Hartmann" Cc: Michael Tuexen , "O. Hartmann" , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 09 Dec 2017 21:30:40 -0000 On Sat, Dec 9, 2017 at 1:47 PM, O. Hartmann wrote= : > Am Sat, 9 Dec 2017 13:00:12 -0700 > Warner Losh schrieb: > > > On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen > wrote: > > > > > > On 9. Dec 2017, at 19:41, O. Hartmann > wrote: > > > > > > > > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to > boot, > > > it gets stuck at > > > > the very first messages on the serial console prompting > > > > > > > > Consoles: internal video/keyboard > > > > > > > > and then nothing more. > > > I don't think it is a general problem with r326734. I'm running on th= e > > > same hardware > > > that revision (with some modifications to the TCP I'm testing): > > > > uname -a > > > FreeBSD nf3.testbed 12.0-CURRENT FreeBSD 12.0-CURRENT #31 r326734M: S= at > > > Dec 9 20:03:59 CET 2017 tuexen@nf3.testbed:/usr/home/ > > > tuexen/head/sys/amd64/compile/TCP amd64 > > > > > > > Hi Michael, > > > > What's your boot setup? BIOS vs UEFI? UFS vs ZFS? GELI? GPT vs MBR? > Plants > > vs Zombies? And did you update your boot blocks or not? > > > > Warner > > All right, I got your point here, my bad, my apaologies. > > I boot from a NanoBSD-prepared image residing on a SD card. The partiton > scheme is GPT, > non UEFI (the SeaBIOS, latest version available for the APU2C2 available) > doesn't support > UEFI. NanoBSD scripts (legacy.sh) has been modified to fit our requests. > > The modifications target at most the creation of a GPT partition scheme > layout, > installing boot/pmbr as bootcode and boot/gptboot on a freebsd-boot > partition as well as > boot/boot1.efifat onto a dedicated efi-type partition. The UEFI partition > is usually > created before(!) the freebsd-boot partition, but in this specific > version, there is NO > EFI partition, only the gptboot containing partition. The binaries of the > above mentioned > bootcode/efi code images are taken from the newly build world. I do not > use boot0sio, the > portion where it is installed is excluded by some "if GPT; then" clause. > > The last known-good version I reported in working is the image I backuped > last time. I > lost the USB 2.0 flash device today containing the last version, that was > not far from > r326218, the version that corrupted FreeBSD, I guess it was r326184, but = I > really do not > know and I havn't a backup of that image. > > The buildworld process is maintained by a bunch of WITHOUT_ statements in > a file driving > NanoBSD. This just for the record just in case FreeBSD build system chang= ed > something significantly. > Should, but if you could share what those all are, I can tell you if any might cause an issue that would help us root cause. > Building a world takes 90 minutes or more, so bi-secting the problem woul= d > be a pain in > the arse (that said, I imply that world and kernel need to be in sync). > > I would appreciate hints or tipps where to look after or how to increase > verbosity > especially at the first boot stage. > OK. So you are booting with gptboot off an SD card on the PC Engines system via legacy methods for a UFS root partition. GELI is not involved, correct? Sadly, there's no easy way to increase the verbosity of the early boot since the boot blocks have to live in such a constrained environment there's a strong bias against including debug code. But what we know is encouraging. We know that gptboot properly loaded, and that it found /boot/loader, loaded it, and then we had the issue. This helps us constrain things somewhat in testing. For the moment, we'll assume that gptboot is good, and concentrate on when /boot/loader went south. Before we do that, can I get any loader.conf and /boot.config /boot/config files you have? src/stand is easily buildable standalone these days, so my thought is trying to build it at r326550 and putting that onto into your image. src/stand stakes 1 minute to build on my box, so 5 on yours max :). You can even build it standalone in a separate tree if that would help keep whatever world you're using to do the builds purer. If we can't get satisfaction doing that, then we'll drop back to plan B: if you give me all the WITH/WITHOUT you are using, I could send you a tarball with about two dozen /boot/loaders to try which should make bisecting not a total pain in the arse. I'd likely toss in gptboot as well, since it's small. Let me know :) Since this is very early in /boot/loader's purview, I don't think kernel/world matter at all (apart from the fact that loader is built as part of world). The PCengines APU with the most recent SeaBIOS isn't capable of booting > FreeBSD from USB > 3.0 devices. Even from USB 2.0 flashdrives working images fail at the boo= t > loader with > "failed with error 19". OK. I assume this is a different issue. :) Warner > > > > > > > > > Best regards > > > Michael > > > > > > > > FreeBSD CURRENT FreeBSD 12.0-CURRENT #52 r324234: Tue Oct 3 11:00:= 53 > > > CEST 2017 amd64 > > > > works fine. > > > > > > > > What the heck has changed? > > > > > > > > Kind regards, > > > > > > > > oh > > > > > > > > -- > > > > O. Hartmann > > > > > > > > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f= =C3=BCr > > > > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7= 28 Abs. 4 > > > BDSG). > > > > > > _______________________________________________ > > > 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" > > > > -- > O. Hartmann > > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Ab= s. 4 BDSG). > From owner-freebsd-current@freebsd.org Sat Dec 9 21:36:19 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 931CFE991F9 for ; Sat, 9 Dec 2017 21:36:19 +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 2BAC676AFC for ; Sat, 9 Dec 2017 21:36:19 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.204] (p57BB4B2C.dip0.t-ipconnect.de [87.187.75.44]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 13AAA71E3F910; Sat, 9 Dec 2017 22:36:16 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard From: Michael Tuexen In-Reply-To: Date: Sat, 9 Dec 2017 22:36:13 +0100 Cc: "O. Hartmann" , FreeBSD CURRENT Content-Transfer-Encoding: quoted-printable Message-Id: References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> <728FB521-24EE-4628-9816-EB3DF0ACA14E@freebsd.org> To: Warner Losh X-Mailer: Apple Mail (2.3445.5.20) 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.25 Precedence: 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, 09 Dec 2017 21:36:19 -0000 > On 9. Dec 2017, at 21:00, Warner Losh wrote: >=20 >=20 >=20 > On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen = wrote: > > On 9. Dec 2017, at 19:41, O. Hartmann = wrote: > > > > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to = boot, it gets stuck at > > the very first messages on the serial console prompting > > > > Consoles: internal video/keyboard > > > > and then nothing more. > I don't think it is a general problem with r326734. I'm running on the = same hardware > that revision (with some modifications to the TCP I'm testing): > > uname -a > FreeBSD nf3.testbed 12.0-CURRENT FreeBSD 12.0-CURRENT #31 r326734M: = Sat Dec 9 20:03:59 CET 2017 = tuexen@nf3.testbed:/usr/home/tuexen/head/sys/amd64/compile/TCP amd64 >=20 > Hi Michael, >=20 > What's your boot setup? BIOS vs UEFI? UFS vs ZFS? GELI? GPT vs MBR? = Plants vs Zombies? And did you update your boot blocks or not? I just do a "sudo make install" building the kernel the old way. > gpart show =3D> 40 250069600 ada0 GPT (119G) 40 1024 1 freebsd-boot (512K) 1064 241171456 2 freebsd-ufs (115G) 241172520 8388608 3 freebsd-swap (4.0G) 249561128 508512 - free - (248M) > gpart list Geom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 250069639 first: 40 entries: 152 scheme: GPT Providers: 1. Name: ada0p1 Mediasize: 524288 (512K) Sectorsize: 512 Stripesize: 0 Stripeoffset: 20480 Mode: r0w0e0 efimedia: HD(1,GPT,2951bfd0-e406-11e5-a569-000db941ce18,0x28,0x400) rawuuid: 2951bfd0-e406-11e5-a569-000db941ce18 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 524288 offset: 20480 type: freebsd-boot index: 1 end: 1063 start: 40 2. Name: ada0p2 Mediasize: 123479785472 (115G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 544768 Mode: r1w1e1 efimedia: = HD(2,GPT,295310f8-e406-11e5-a569-000db941ce18,0x428,0xe5ffc00) rawuuid: 295310f8-e406-11e5-a569-000db941ce18 rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: (null) length: 123479785472 offset: 544768 type: freebsd-ufs index: 2 end: 241172519 start: 1064 3. Name: ada0p3 Mediasize: 4294967296 (4.0G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 3221245952 Mode: r1w1e0 efimedia: = HD(3,GPT,2958486b-e406-11e5-a569-000db941ce18,0xe600028,0x800000) rawuuid: 2958486b-e406-11e5-a569-000db941ce18 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 4294967296 offset: 123480330240 type: freebsd-swap index: 3 end: 249561127 start: 241172520 Consumers: 1. Name: ada0 Mediasize: 128035676160 (119G) Sectorsize: 512 Mode: r2w2e3 >=20 I'm not using the internal SD card... Everything resides on the SSD. Best regards Michael >=20 > Warner >=20 > =20 > Best regards > Michael > > > > FreeBSD CURRENT FreeBSD 12.0-CURRENT #52 r324234: Tue Oct 3 = 11:00:53 CEST 2017 amd64 > > works fine. > > > > What the heck has changed? > > > > Kind regards, > > > > oh > > > > -- > > O. Hartmann > > > > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten = f=C3=BCr > > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 = 28 Abs. 4 BDSG). >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" >=20