From owner-freebsd-current@freebsd.org Sun Jan 17 01:50:04 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0570B4D5F27 for ; Sun, 17 Jan 2021 01:50:04 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJHt25pldz3kgr for ; Sun, 17 Jan 2021 01:50:02 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr1-x436.google.com with SMTP id 7so5838939wrz.0 for ; Sat, 16 Jan 2021 17:50:02 -0800 (PST) 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:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=tnOb+xx37EGjMVt5wgVA/xID7PPVr3quQjdsmwZR2B8=; b=K93IsPBNQJ58jYkBOHAmnEAlyvQfgP4xAZc8fOj8kwNtGspYcu7+3g6ZPbuLovqIZI qvKzdzGzotNXlBZv/ivGHVIBi7taNBWydt19/LTvlq1uxwcdlpZticMwo8vFo3rZAf7y f6f+aFeCrUCEDjOd93JrFW9UuD7hRn9sc+AY6G623arcUGuyxwNcfqjOVXp3diiiNkXe FFcXj84BbYpwVG4L+EzgNb4RLlHcCrDCi7GUgLCYL8PFyCq5N/vEC0nShdHf6tiFxOgB GGCtUNLnCQqNo0zYgxSi0d5SEHoVesVsP5snxk1w/RNgBv4g8C7PuXikrLtpXs0pisid IP2A== X-Gm-Message-State: AOAM53042L3M+2kd/Z0gQ7dDE+b0obWPqD5aFgkj9nlxAQevaB0j6gEE bqzPGPVHAvtAeEKANtPOrltATe20kL12dA== X-Google-Smtp-Source: ABdhPJz2ZeVqpt7f7RYoKRGglQhbGng86hp9cwyiY9+92dXeSKfVrxmrXiWCR89NYPar8zGAOw0h/Q== X-Received: by 2002:adf:9525:: with SMTP id 34mr20297699wrs.389.1610848201101; Sat, 16 Jan 2021 17:50:01 -0800 (PST) Received: from gumby.homeunix.com ([2.125.48.115]) by smtp.gmail.com with ESMTPSA id x13sm21322414wrp.80.2021.01.16.17.49.59 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 16 Jan 2021 17:50:00 -0800 (PST) Date: Sun, 17 Jan 2021 01:49:56 +0000 From: RW To: freebsd-current@freebsd.org Subject: Re: service -e doesn't really sort does it? the cool tip is slightly off Message-ID: <20210117014956.5c957997@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; amd64-portbld-freebsd12.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DJHt25pldz3kgr X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[googlemail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::436:from]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; SUBJECT_HAS_QUESTION(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[2.125.48.115:received]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::436:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::436:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 01:50:04 -0000 On Sat, 16 Jan 2021 23:28:48 +0000 Dennis Clarke wrote: > Saw this pop up : > > rhea$ su - admsys > Password: > If you want to get a sorted list of all services that are started when > FreeBSD boots, > enter "service -e". > ... > > To which I thought "sorted? really?" > .. > Nope. That doesn't look sorted. Unless the sorted means "order in > which they start" perhaps. To me that's the obvious interpretation of 'sorted' because it's the only meaning that's relevant to the context. If it simply meant alphabetical order, it wouldn't have been worth mentioning. In any case, it's clear in service(8). From owner-freebsd-current@freebsd.org Sun Jan 17 04:11:08 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 04F5C4D9CD7 for ; Sun, 17 Jan 2021 04:11:08 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DJM0q5B7Wz3sX6 for ; Sun, 17 Jan 2021 04:11:07 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: by mailman.nyi.freebsd.org (Postfix) id B1BBD4D9CD6; Sun, 17 Jan 2021 04:11:07 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B16AC4D9CD5 for ; Sun, 17 Jan 2021 04:11:07 +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 4DJM0p4cF7z3sth for ; Sun, 17 Jan 2021 04:11:06 +0000 (UTC) (envelope-from roberthuff@rcn.com) X_CMAE_Category: , , X-CNFS-Analysis: v=2.3 cv=KJsk82No c=1 sm=1 tr=0 cx=a_idp_x a=9TgA2UwI6Wy+6BV4wQM/cQ==:117 a=9TgA2UwI6Wy+6BV4wQM/cQ==:17 a=KGjhK52YXX0A:10 a=kj9zAlcOel0A:10 a=XRQyMpdBKAEA:10 a=EmqxpYm9HcoA:10 a=48faUk6PgeAA:10 a=raTeMDPqTwUbpX1SFsIA:9 a=CjuIK1q_8ugA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine X-Authed-Username: cm9iZXJ0aHVmZkByY24uY29t Received: from [209.6.230.48] ([209.6.230.48:57109] 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 69/A0-38641-8D8B3006; Sat, 16 Jan 2021 23:11:05 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <24579.47318.840293.98517@jerusalem.litteratus.org> Date: Sat, 16 Jan 2021 23:11:02 -0500 From: Robert Huff To: current@freebsd.org Subject: Re: Current kernel build broken with linuxkpi? In-Reply-To: <24576.35364.293160.210700@jerusalem.litteratus.org> References: <24576.35364.293160.210700@jerusalem.litteratus.org> X-Mailer: VM 8.2.0b under 27.1 (amd64-portbld-freebsd13.0) X-Vade-Verditct: clean X-Vade-Analysis: gggruggvucftvghtrhhoucdtuddrgeduledrtdehgdeiiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfujgfpteevqfftnfgvrghrnhhinhhgpdftvefppdfqfgfvnecuuegrihhlohhuthemuceftddunecunecujfgurhepgggtgffkfffhvffujghfofesthejredtredtvdenucfhrhhomheptfhosggvrhhtucfjuhhffhcuoehrohgsvghrthhhuhhffhesrhgtnhdrtghomheqnecuggftrfgrthhtvghrnheptddtleektefhgeeggfevleeugedvleduheeuuedvgeejiedvffeiffeftefhgfeunecukfhppedvtdelrdeirddvfedtrdegkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpedvtdelrdeirddvfedtrdegkeenpdhmrghilhhfrhhomheprhhosggvrhhthhhufhhfsehrtghnrdgtohhmnedprhgtphhtthhopegtuhhrrhgvnhhtsehfrhgvvggsshgurdhorhhgne X-Rspamd-Queue-Id: 4DJM0p4cF7z3sth X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:69.168.97.0/24]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[rcn.com:+]; DMARC_POLICY_ALLOW(-0.50)[rcn.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_LOW(-0.10)[69.168.97.78:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[69.168.97.78:from]; INTRODUCTION(2.00)[]; ASN(0.00)[asn:36271, ipnet:69.168.97.0/24, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[rcn.com:s=20180516]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[69.168.97.78:from:127.0.2.255]; DWL_DNSWL_LOW(-1.00)[rcn.com:dkim]; RWL_MAILSPIKE_POSSIBLE(0.00)[69.168.97.78:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 04:11:08 -0000 And ... we have a winner. (So far.) The system in question has 11+ hours uptime running: FreeBSD 13.0-ALPHA1 #1 main-c1149-g79a5c790bd: Sat Jan 16 09:02:47 EST 2021 amd64 (Now rebuilding 1100+ ports ....) I commented out the IGNORE line from drm-current-kmod; built successfully; built the kernel - successfully; and installed kernel then world with no hiccups. Thanks to everyone for their help. Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! From owner-freebsd-current@freebsd.org Sun Jan 17 04:33:12 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5535E4DAC9D for ; Sun, 17 Jan 2021 04:33:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJMVH0Jbxz3tll; Sun, 17 Jan 2021 04:33:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 10H4X2gd022749 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 17 Jan 2021 06:33:05 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 10H4X2gd022749 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 10H4X21d022748; Sun, 17 Jan 2021 06:33:02 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 17 Jan 2021 06:33:01 +0200 From: Konstantin Belousov To: rhurlin@freebsd.org Cc: freebsd-current Subject: Re: Waiting for bufdaemon Message-ID: References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4DJMVH0Jbxz3tll X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:d5e7:1::1:from]; R_SPF_SOFTFAIL(0.00)[~all]; SPAMHAUS_ZRD(0.00)[2001:470:d5e7:1::1:from:127.0.2.255]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 04:33:12 -0000 On Sat, Jan 16, 2021 at 07:41:01PM +0100, Rainer Hurling wrote: > During another shutdown after heavy usage of the box, the following > messages were also seen: > > > [...] > Syncing disks, vnodes remaining... 22 EFI rt_settime call faulted, error 14 > efirtc0: CLOCK_SETTIME error 14 This means that BIOS code faulted during RTC settime call. I doubt that it is related. On the other hand, it is good that the onfault EFI RT code got tested finally. From owner-freebsd-current@freebsd.org Sun Jan 17 09:37:25 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D4AE04E23B3 for ; Sun, 17 Jan 2021 09:37:25 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4DJVFK5kXzz4fVP for ; Sun, 17 Jan 2021 09:37:25 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-13.um.gwdg.de ([134.76.9.222] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1l14Ut-0000gn-Q1; Sun, 17 Jan 2021 10:37:23 +0100 Received: from krabat.raven.hur (10.250.9.200) by EXCMBX-13.um.gwdg.de (134.76.9.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2044.4; Sun, 17 Jan 2021 10:37:23 +0100 Subject: Re: Waiting for bufdaemon To: Konstantin Belousov CC: freebsd-current References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> Reply-To: From: Rainer Hurling Message-ID: Date: Sun, 17 Jan 2021 10:37:18 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.200] X-ClientProxiedBy: EXCMBX-23.um.gwdg.de (134.76.9.233) To EXCMBX-13.um.gwdg.de (134.76.9.222) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4DJVFK5kXzz4fVP X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 09:37:25 -0000 Am 17.01.21 um 05:33 schrieb Konstantin Belousov: > On Sat, Jan 16, 2021 at 07:41:01PM +0100, Rainer Hurling wrote: >> During another shutdown after heavy usage of the box, the following >> messages were also seen: >> >> >> [...] >> Syncing disks, vnodes remaining... 22 EFI rt_settime call faulted, error 14 >> efirtc0: CLOCK_SETTIME error 14 > > This means that BIOS code faulted during RTC settime call. I doubt that > it is related. > > On the other hand, it is good that the onfault EFI RT code got tested finally. > Thanks for clarification :) Any chance of getting a fix for the AMD CPUs in the foreseeable future? Or should I revert commit 9e680e4005b7 on affected boxes until further notice (as a workaround)? From owner-freebsd-current@freebsd.org Sun Jan 17 09:49:48 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9C7D4E2B10 for ; Sun, 17 Jan 2021 09:49:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJVWb6C3hz4gD1; Sun, 17 Jan 2021 09:49:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 10H9neDv098998 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 17 Jan 2021 11:49:43 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 10H9neDv098998 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 10H9ne0t098997; Sun, 17 Jan 2021 11:49:40 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 17 Jan 2021 11:49:40 +0200 From: Konstantin Belousov To: rhurlin@freebsd.org Cc: freebsd-current Subject: Re: Waiting for bufdaemon Message-ID: References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4DJVWb6C3hz4gD1 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.88 / 15.00]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:d5e7:1::1:from]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_SHORT(0.12)[0.123]; SPAMHAUS_ZRD(0.00)[2001:470:d5e7:1::1:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 09:49:48 -0000 On Sun, Jan 17, 2021 at 10:37:18AM +0100, Rainer Hurling wrote: > Am 17.01.21 um 05:33 schrieb Konstantin Belousov: > > On Sat, Jan 16, 2021 at 07:41:01PM +0100, Rainer Hurling wrote: > >> During another shutdown after heavy usage of the box, the following > >> messages were also seen: > >> > >> > >> [...] > >> Syncing disks, vnodes remaining... 22 EFI rt_settime call faulted, error 14 > >> efirtc0: CLOCK_SETTIME error 14 > > > > This means that BIOS code faulted during RTC settime call. I doubt that > > it is related. > > > > On the other hand, it is good that the onfault EFI RT code got tested finally. > > > > Thanks for clarification :) > > > Any chance of getting a fix for the AMD CPUs in the foreseeable future? > > Or should I revert commit 9e680e4005b7 on affected boxes until further > notice (as a workaround)? I am working on it, no ETA. Interesting point would be to check on machines of other testers, if the following hides the problem. diff --git a/sys/x86/x86/tsc.c b/sys/x86/x86/tsc.c index 85924df98312..5700a8ca98e5 100644 --- a/sys/x86/x86/tsc.c +++ b/sys/x86/x86/tsc.c @@ -639,7 +639,7 @@ init_TSC_tc(void) * on Intel, and MFENCE;RDTSC on AMD. * - For really old CPUs, just use RDTSC. */ - if ((cpu_vendor_id == CPU_VENDOR_AMD || + if (false && (cpu_vendor_id == CPU_VENDOR_AMD || cpu_vendor_id == CPU_VENDOR_HYGON) && CPUID_TO_FAMILY(cpu_id) >= 0x17) { tsc_timecounter.tc_get_timecount = shift > 0 ? From owner-freebsd-current@freebsd.org Sun Jan 17 13:19:59 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 78FA64E8F0A for ; Sun, 17 Jan 2021 13:19:59 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DJbB72BcJz4tQ7 for ; Sun, 17 Jan 2021 13:19:59 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.nyi.freebsd.org (Postfix) id 4B29E4E8F80; Sun, 17 Jan 2021 13:19:59 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4AEFB4E88FC for ; Sun, 17 Jan 2021 13:19:59 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [107.204.234.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJbB646Vqz4tpw for ; Sun, 17 Jan 2021 13:19:58 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.16.1/8.15.2) with ESMTP id 10HDJu9x002909 for ; Sun, 17 Jan 2021 13:19:56 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.16.1/8.16.1/Submit) id 10HDJuKq002908 for current@freebsd.org; Sun, 17 Jan 2021 05:19:56 -0800 (PST) (envelope-from david) Date: Sun, 17 Jan 2021 05:19:56 -0800 From: David Wolfskill To: current@freebsd.org Subject: wlan0 (iwn(4)) needed encouragement to associate Message-ID: Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yw+ZI5z1v7gXTTZL" Content-Disposition: inline X-Rspamd-Queue-Id: 4DJbB646Vqz4tpw X-Spamd-Bar: / X-Spamd-Result: default: False [-0.37 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[current@freebsd.org]; FREEFALL_USER(0.00)[david]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[107.204.234.170:from]; R_SPF_ALLOW(-0.20)[+ip4:107.204.234.170:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[107.204.234.170:from:127.0.2.255]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.967]; DMARC_NA(0.00)[catwhisker.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:7018, ipnet:107.192.0.0/12, country:US]; REPLYTO_EQ_TO_ADDR(5.00)[]; MAILMAN_DEST(0.00)[current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 13:19:59 -0000 --yw+ZI5z1v7gXTTZL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable After this morning's update of head from: FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #124 main-c256= 006-g8ca9ff4f28d2-dirty: Sat Jan 16 05:47:48 PST 2021 root@g1-55.catwhi= sker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1300135 13001= 35 to: FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #125 main-c256= 026-gb7ab6832cd98-dirty: Sun Jan 17 04:49:26 PST 2021 root@g1-55.catwhi= sker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1300135 13001= 35 on my laptop, the wireless link failed to associate by the time the xdm login screen came up. But when I logged in (on vty1) and issued: service netif restart wlan0 it associated right away. (There was no issue with the corresponding update for stable/12, so I have no reason to believe that there is an issue with the access point or the laptop -- with respect to associating properly, at least). And whether in head or stable/12, the woreless link has (for the past several months of daily tracking both head and stable/12) almost always associated by the time the xdm login screen comes up. I tried it 3 times; each time, it failed to associate. (I only tried the "service netif restart wlan0" the last 2 times -- the first time, vty1 wasn't usable because I had experimented with a /boot/loader.conf setting, which (as far as I know) is not relevant to this issue.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Mr. Trump: We did not need you to demonstrate the efficacy of the "big lie" propaganda technique quite so well -- really. Please stop. See https://www.catwhisker.org/~david/publickey.gpg for my public key. --yw+ZI5z1v7gXTTZL Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAmAEOXxfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 PcnS7Af/VospTFiOi1MliGCDxE9wh0snYq4P8ofxtcwL1fpNnSG1iSR3LlEi+mBH fbMEiBAiaU4Dn5Azi4HXEOii9sgLfgXEfl3UUzR4naWq6jc9dRUKlfZfCU8z7dIF WCNbNBbDNCa7N0+hKYXNWAa3YiScuuDaWTBjarhc2SsmNzCnaocAL8ugFfjzojR/ ZSlAuOiUSm+3LYzLSOq2UeyM6xGv8OEpe6znkbUIBGI3PG3hw8tdn1bQlohs3ieF 26m278Hy5IyEqDGP5l12PYpKjv/sVMvfgp6CwllwbKcxP0Lsi7FWeeo5d9SbwBjM apvuKoIZgih9GUIe4A9SN2i4gsC7IQ== =s6gr -----END PGP SIGNATURE----- --yw+ZI5z1v7gXTTZL-- From owner-freebsd-current@freebsd.org Sun Jan 17 13:47:04 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EDEEA4EA121 for ; Sun, 17 Jan 2021 13:47:04 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJbnM4ln5z3DD6 for ; Sun, 17 Jan 2021 13:47:03 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x430.google.com with SMTP id y17so13914818wrr.10 for ; Sun, 17 Jan 2021 05:47:03 -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:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=/d53qG8IWx2vyq410fZUxA+tntyaxVrrPrUEdXH5NY8=; b=la/DTyu6S49bGJaNSn/bc9SxfcZn86ca7QNG+38I9a3sS4zIFrl7zkQijuOa2iE2ey hNGchIw5u6KVC4KwY5g/Bql0FEz+lLu0FntuKvwUFbGDnUj60X3jXxqjIvzg6P7bU2GY 4mwX46p8mVlofvI/qqZlYAOLsCjM2DzmllfZzZZNWMwfddOvP/cYHHuhJde9JeUfOop9 lynQ2Bqcbp2pA3a+Snqir5DbVF7D5CHKpDynJ3vPgPMuiN/efZ5VKVEIz6nvobf7P5Q5 0hRh5GcsbA+Gpzk6//wnmlhW/OIBFQmmRFY2md+ggWvcX8tLFG3pBFdHnc3MT41mPpKi J/Ig== X-Gm-Message-State: AOAM532dlI5s+SFCad0EdC7pHnTjigoZgChbojeejZS0O9SGOGrFs68Q vjj3hxlwHLlnoB+XAAk0M3vpOd5Y5q2t+g== X-Google-Smtp-Source: ABdhPJzRWqJSrLyfZ7tNf20RcoCsm134Kr34YOFl9GZqdsc3Wn75jKE+jW9XFACen2XTvCseRD0rKg== X-Received: by 2002:a5d:6749:: with SMTP id l9mr21985279wrw.395.1610891222015; Sun, 17 Jan 2021 05:47:02 -0800 (PST) Received: from [192.168.1.11] (88-105-96-80.dynamic.dsl.as9105.com. [88.105.96.80]) by smtp.gmail.com with ESMTPSA id z21sm19782392wmk.20.2021.01.17.05.47.00 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 17 Jan 2021 05:47:01 -0800 (PST) Subject: Re: service -e doesn't really sort does it? the cool tip is slightly off To: freebsd-current@freebsd.org References: From: Graham Perrin Message-ID: Date: Sun, 17 Jan 2021 13:46:57 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-Rspamd-Queue-Id: 4DJbnM4ln5z3DD6 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::430:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[88.105.96.80:received]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::430:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[0.999]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::430:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 13:47:05 -0000 On 16/01/2021 23:28, Dennis Clarke wrote: > … maybe take out the word "sorted". Either that or > insert the "started order" as the manpage claims : > > root@rhea:/usr/src/freebsd-src # diff -u > usr.bin/fortune/datfiles/freebsd-tips.orig > usr.bin/fortune/datfiles/freebsd-tips > --- usr.bin/fortune/datfiles/freebsd-tips.orig 2021-01-15 > 00:37:37.863506000 +0000 > +++ usr.bin/fortune/datfiles/freebsd-tips 2021-01-16 > 07:46:57.335803000 +0000 > @@ -517,7 +517,7 @@ > > -- Lars Engels > % > -If you want to get a sorted list of all services that are started when > FreeBSD boots, > +If you want to get a list of all services that are started when FreeBSD > boots, > enter "service -e". > > -- Lars Engels > root@rhea:/usr/src/freebsd-src # > > Sorry for being all OCD here. Perhaps it should say sorted in the order > in which they were started. Something like that. > In lieu of 'sorted', how about 'dependency-ordered'? From owner-freebsd-current@freebsd.org Sun Jan 17 13:50:03 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2813E4EA2D3 for ; Sun, 17 Jan 2021 13:50:03 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 4DJbrn5kWwz3DVm for ; Sun, 17 Jan 2021 13:50:01 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-f649235c.06-431-73746f70.bbcust.telenor.se ([92.35.73.246] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l18RG-000Bp1-8v for freebsd-current@freebsd.org; Sun, 17 Jan 2021 14:49:54 +0100 Received: from [192.168.67.33] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l18RF-0006WI-O3 for freebsd-current@freebsd.org; Sun, 17 Jan 2021 14:49:53 +0100 Subject: Re: wlan0 (iwn(4)) needed encouragement to associate To: freebsd-current@freebsd.org References: From: Jakob Alvermark Message-ID: <6b319f64-f457-47dc-bdcf-fd160b1ba90f@alvermark.net> Date: Sun, 17 Jan 2021 14:49:53 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4DJbrn5kWwz3DVm X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.49 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[185.34.136.138:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[alvermark.net:+]; NEURAL_HAM_SHORT(-0.99)[-0.987]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[185.34.136.138:from]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/23, country:IT]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 13:50:03 -0000 On 1/17/21 2:19 PM, David Wolfskill wrote: > After this morning's update of head from: > > FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #124 main-c256006-g8ca9ff4f28d2-dirty: Sat Jan 16 05:47:48 PST 2021 root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1300135 1300135 > > > to: > > FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #125 main-c256026-gb7ab6832cd98-dirty: Sun Jan 17 04:49:26 PST 2021 root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1300135 1300135 > > on my laptop, the wireless link failed to associate by the time the > xdm login screen came up. But when I logged in (on vty1) and issued: > > service netif restart wlan0 > > it associated right away. (There was no issue with the corresponding > update for stable/12, so I have no reason to believe that there is an > issue with the access point or the laptop -- with respect to associating > properly, at least). And whether in head or stable/12, the woreless > link has (for the past several months of daily tracking both head and > stable/12) almost always associated by the time the xdm login screen > comes up. > > I tried it 3 times; each time, it failed to associate. (I only tried > the "service netif restart wlan0" the last 2 times -- the first time, > vty1 wasn't usable because I had experimented with a /boot/loader.conf > setting, which (as far as I know) is not relevant to this issue.) > > Peace, > david +1 I have the same issue. This is on an Intel Centrino Advanced 6235 I also noticed that wpa_supplicant is using 100% CPU on one core. Jakob From owner-freebsd-current@freebsd.org Sun Jan 17 15:18:13 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BD0884EC904 for ; Sun, 17 Jan 2021 15:18:13 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DJdpY427Gz3LFW for ; Sun, 17 Jan 2021 15:18:13 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: by mailman.nyi.freebsd.org (Postfix) id 8A5064EC903; Sun, 17 Jan 2021 15:18:13 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8A1934EC902 for ; Sun, 17 Jan 2021 15:18:13 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (noc.quadranet.com [66.63.164.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "sigill.theweb.org.ua", Issuer "sigill.theweb.org.ua" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJdpX5qJ9z3L2G for ; Sun, 17 Jan 2021 15:18:12 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (localhost [127.0.0.1]) by sigill.theweb.org.ua (8.16.1/8.16.1) with ESMTPS id 10HFI21m043416 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sun, 17 Jan 2021 17:18:02 +0200 (EET) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by sigill.theweb.org.ua (8.16.1/8.16.1/Submit) id 10HFI1Rt043413 for current@freebsd.org; Sun, 17 Jan 2021 17:18:01 +0200 (EET) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: sigill.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: current@freebsd.org Subject: run(4) fails to associate Re: wlan0 (iwn(4)) needed encouragement to associate Date: Sun, 17 Jan 2021 17:18:01 +0200 Message-ID: <3745430.kAAoriTUSa@sigill.theweb.org.ua> Organization: Private persom In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 4DJdpX5qJ9z3L2G X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 15:18:13 -0000 On 2021 M01 17, Sun 15:19:56 EET David Wolfskill wrote: > After this morning's update of head from: > > FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #124 > main-c256006-g8ca9ff4f28d2-dirty: Sat Jan 16 05:47:48 PST 2021 > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > amd64 1300135 1300135 > > > to: > > FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #125 > main-c256026-gb7ab6832cd98-dirty: Sun Jan 17 04:49:26 PST 2021 > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > amd64 1300135 1300135 > > on my laptop, the wireless link failed to associate by the time the > xdm login screen came up. But when I logged in (on vty1) and issued: > > service netif restart wlan0 > > it associated right away. (There was no issue with the corresponding > update for stable/12, so I have no reason to believe that there is an > issue with the access point or the laptop -- with respect to associating > properly, at least). And whether in head or stable/12, the woreless > link has (for the past several months of daily tracking both head and > stable/12) almost always associated by the time the xdm login screen > comes up. > > I tried it 3 times; each time, it failed to associate. (I only tried > the "service netif restart wlan0" the last 2 times -- the first time, > vty1 wasn't usable because I had experimented with a /boot/loader.conf > setting, which (as far as I know) is not relevant to this issue.) I can confirm that run(4) fails to associate on FreeBSD 13.0-ALPHA1 #38 main- c256026-gb7ab6832cd98-dirty Jan 17 kernel: ugen0.3: at usbus0 kernel: run0 on uhub0 kernel: run0: on usbus0 kernel: run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 00:26:5a:0a:cb:fa kernel: run0: [HT] Enabling 802.11n webcamd[5382]: webcamd: Cannot find USB device kernel: wlan0: Ethernet address: 00:26:5a:0a:cb:fa root[6113]: /etc/rc.d/dhclient: WARNING: failed to start dhclient while it works with with one week old kernel FreeBSD 13.0-CURRENT #37 main-c255825-g2a4b22514635-dirty Jan 10 kernel: run0 on uhub0 kernel: run0: on usbus0 kernel: run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 00:26:5a:0a:cb:fa kernel run0: [HT] Enabling 802.11n kernel run0: firmware RT2870 ver. 0.33 loaded kernel: wlan0: link state changed to UP > > Peace, > david From owner-freebsd-current@freebsd.org Sun Jan 17 16:42:06 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 19F974EF885 for ; Sun, 17 Jan 2021 16:42:06 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4DJggL0HYbz3R5m for ; Sun, 17 Jan 2021 16:42:05 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-03.um.gwdg.de ([134.76.9.218] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1l1B7r-0005bg-RQ; Sun, 17 Jan 2021 17:42:03 +0100 Received: from krabat.raven.hur (10.250.9.200) by EXCMBX-03.um.gwdg.de (134.76.9.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2044.4; Sun, 17 Jan 2021 17:42:03 +0100 Subject: Re: Waiting for bufdaemon To: Konstantin Belousov CC: freebsd-current References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> Reply-To: From: Rainer Hurling Message-ID: <0699bacf-f0ae-8766-0a3d-ee292fe5c06d@gwdg.de> Date: Sun, 17 Jan 2021 17:41:58 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.200] X-ClientProxiedBy: excmbx-11.um.gwdg.de (134.76.9.220) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4DJggL0HYbz3R5m X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 16:42:06 -0000 Am 17.01.21 um 10:49 schrieb Konstantin Belousov: > On Sun, Jan 17, 2021 at 10:37:18AM +0100, Rainer Hurling wrote: >> Am 17.01.21 um 05:33 schrieb Konstantin Belousov: >>> On Sat, Jan 16, 2021 at 07:41:01PM +0100, Rainer Hurling wrote: >>>> During another shutdown after heavy usage of the box, the following >>>> messages were also seen: >>>> >>>> >>>> [...] >>>> Syncing disks, vnodes remaining... 22 EFI rt_settime call faulted, error 14 >>>> efirtc0: CLOCK_SETTIME error 14 >>> >>> This means that BIOS code faulted during RTC settime call. I doubt that >>> it is related. >>> >>> On the other hand, it is good that the onfault EFI RT code got tested finally. >>> >> >> Thanks for clarification :) >> >> >> Any chance of getting a fix for the AMD CPUs in the foreseeable future? >> >> Or should I revert commit 9e680e4005b7 on affected boxes until further >> notice (as a workaround)? > > I am working on it, no ETA. > > Interesting point would be to check on machines of other testers, > if the following hides the problem. > > diff --git a/sys/x86/x86/tsc.c b/sys/x86/x86/tsc.c > index 85924df98312..5700a8ca98e5 100644 > --- a/sys/x86/x86/tsc.c > +++ b/sys/x86/x86/tsc.c > @@ -639,7 +639,7 @@ init_TSC_tc(void) > * on Intel, and MFENCE;RDTSC on AMD. > * - For really old CPUs, just use RDTSC. > */ > - if ((cpu_vendor_id == CPU_VENDOR_AMD || > + if (false && (cpu_vendor_id == CPU_VENDOR_AMD || > cpu_vendor_id == CPU_VENDOR_HYGON) && > CPUID_TO_FAMILY(cpu_id) >= 0x17) { > tsc_timecounter.tc_get_timecount = shift > 0 ? > I tried the above patch on a Ryzen 3950X. After reboot (again with long waiting for bufdaemon and more) the box had some heavy load with several jobs (llvm on Poudriere, building qt5-webengine, libreoffice and some more in parallel). All went fine. Afterwards I rebooted again. This time, the shutdown was fast without any unusual delays :) Many thanks! From owner-freebsd-current@freebsd.org Sun Jan 17 17:40:10 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 88C064D159E; Sun, 17 Jan 2021 17:40:10 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJhyK4pvnz3lQY; Sun, 17 Jan 2021 17:40:09 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 10HHe6Zg030969 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 17 Jan 2021 09:40:07 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 10HHe6C5030968; Sun, 17 Jan 2021 09:40:06 -0800 (PST) (envelope-from fbsd) Date: Sun, 17 Jan 2021 09:40:06 -0800 From: bob prohaska To: bob prohaska Cc: Current FreeBSD , freebsd-arm@freebsd.org Subject: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld Message-ID: <20210117174006.GA30728@www.zefox.net> References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4DJhyK4pvnz3lQY X-Spamd-Bar: - X-Spamd-Result: default: False [-1.06 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.96)[-0.963]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-arm]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 17:40:10 -0000 On Sat, Jan 16, 2021 at 03:04:04PM -0800, Mark Millard wrote: > > Other than -j1 style builds (or equivalent), one pretty much > always needs to go looking around for a non-panic failure. It > is uncommon for all the material to be together in the build > log in such contexts. Running make cleandir twice and restarting -j4 buildworld brought the process full circle: A silent hang, no debugger response, no console warnings. That's what sent me down the rabbit hole of make without clean, which worked at least once... The residue of the top screen shows last pid: 63377; load averages: 4.29, 4.18, 4.15 up 1+07:11:07 04:46:46 60 processes: 5 running, 55 sleeping CPU: 70.7% user, 0.0% nice, 26.5% system, 2.8% interrupt, 0.0% idle Mem: 631M Active, 4932K Inact, 92M Laundry, 166M Wired, 98M Buf, 18M Free Swap: 2048M Total, 119M Used, 1928M Free, 5% Inuse, 16K In, 3180K Out packet_write_wait: Connection to 50.1.20.26 port 22: Broken pipe bob@raspberrypi:~ $ ssh www.zefox.com RES STATE C TIME WCPU COMMAND ssh: connect to host www.zefox.com port 22: Connection timed out86.17% c++ bob@raspberrypi:~ $ 1 99 0 277M 231M RUN 0 3:26 75.00% c++ 63245 bob 1 99 0 219M 173M CPU0 0 2:10 73.12% c++ 62690 bob 1 98 0 354M 234M RUN 3 9:42 47.06% c++ 63377 bob 1 30 0 5856K 2808K nanslp 0 0:00 3.13% gstat 38283 bob 1 24 0 5208K 608K wait 2 2:00 0.61% sh 995 bob 1 20 0 6668K 1184K CPU3 3 8:46 0.47% top 990 bob 1 20 0 12M 1060K select 2 0:48 0.05% sshd .... [apologies for typing over the remnants] I've put copies of the build and swap logs at http://www.zefox.net/~fbsd/rpi2/buildworld/ The last vmstat entry (10 second repeat time) reports: procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 sd0 in sy cs us sy id 4 0 14 969160 91960 685 2 2 1 707 304 0 0 11418 692 1273 45 5 50 Does that point to the memory exhaustion suggested earlier in the thread? At this point /boot/loader.conf contains vm.pfault_oom_attempts="-1", but that's a relic of long-ago attempts to use USB flash for root and swap. Might removing it stimulate more warning messages? Thanks for reading! bob prohaska From owner-freebsd-current@freebsd.org Sun Jan 17 18:22:19 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 87B8D4D31CF for ; Sun, 17 Jan 2021 18:22:19 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJjty45G8z3qXc for ; Sun, 17 Jan 2021 18:22:18 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x32c.google.com with SMTP id u14so7770096wmq.4 for ; Sun, 17 Jan 2021 10:22:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=j/sBhAFS2njVDa1nZHtNSnTHNPDfVepQJN/mSfV+uN4=; b=m4ynIr3aNhXEhLmFkOYY4GlfPbb/kcKQfe5O5Z9Lt6luX5lD4f1+nL8ArYno0JFdNF KVEpDBy4zlMGQHyec3jkuyaA3EGQgSX2ovByE6axL6Jbn2j/vD2feS1zbZce3ZqCbcbr q0Fj7ymCuKhs3U3DE9TUjae1LXPRX5sxm0W7j+73EK/uM4tiAmzNuSho2G4YlJwyuaPb +yAZpdN6W+P9u5WsVzMQsrrS1JAnfsCkvKp7O+9ds1xGerL0P7vWdUi2zYTlaTKxsh6v oQ5avFK1RSSX3VK4j0IniD0RXiNIdB+QSC2pmPoms4pmWSLGXrJtcih/UZEy3RWXd32/ GvxA== X-Gm-Message-State: AOAM530RHaLg9kbWRxrowQsbQEL3ktlonIHqomnbvIAQcmD826AN5Ovn o3kfiAT3xcYBMp4ZEynKNxxrFT8aIQxNeA== X-Google-Smtp-Source: ABdhPJwkwwsTgIT1PEKpiBfptr+CCp8TOVQMMtXkBLDVdQAiJJ4cJZKz00JJX4hhE/cKrGvasLgGvA== X-Received: by 2002:a1c:cb:: with SMTP id 194mr8687517wma.30.1610907735722; Sun, 17 Jan 2021 10:22:15 -0800 (PST) Received: from [192.168.1.11] (88-105-96-80.dynamic.dsl.as9105.com. [88.105.96.80]) by smtp.gmail.com with ESMTPSA id s3sm19922580wmc.44.2021.01.17.10.22.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 17 Jan 2021 10:22:14 -0800 (PST) To: freebsd-current@freebsd.org From: Graham Perrin Subject: FreeBSD-provided .vhd with VirtualBox: gpart I/O errors after resizing the virtual hard disk Message-ID: Date: Sun, 17 Jan 2021 18:22:14 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-Rspamd-Queue-Id: 4DJjty45G8z3qXc X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.17 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[88.105.96.80:received]; FROM_EQ_ENVFROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::32c:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::32c:from:127.0.2.255]; MIME_TRACE(0.00)[0:+]; NEURAL_SPAM_SHORT(0.83)[0.828]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32c:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 18:22:19 -0000 VirtualBox 5.2.44 r139111 on FreeBSD-CURRENT. 01. Add FreeBSD-12.2-RELEASE-amd64.vhd to a machine 02. use Virtual Disk Manager to resize it to 2.0 TB 03. apply, close 04. boot single user 05. gpart show /dev/ada0 07. observe reported corruption 08. gpart recover /dev/ada0 09. I/O error 10. gpart show /dev/ada0 11. no reported corruption 12. shutdown -r now 13. observe reported corruption: > gptboot: invalid backup GPT header For me, this seems to be consistently reproducible. Thoughts? Boot proceeds and I guess that the UFS file system is automatically grown, but the reported I/O errors make me nervous. % uname -v FreeBSD 13.0-CURRENT #75 main-c572-g82397d791: Sun Jan  3 20:00:09 GMT 2021 root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG % From owner-freebsd-current@freebsd.org Sun Jan 17 20:02:51 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4FAB34D64A7 for ; Sun, 17 Jan 2021 20:02:51 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from maybe.home.utahime.org (gate.home.utahime.org [183.180.29.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJm6y25sjz4RTG for ; Sun, 17 Jan 2021 20:02:49 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by maybe.home.utahime.org (Postfix) with ESMTPS id F20224B6B7 for ; Mon, 18 Jan 2021 05:02:40 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384)) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 239473D4A0; Mon, 18 Jan 2021 05:02:40 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.0 at eastasia.home.utahime.org Date: Mon, 18 Jan 2021 05:02:20 +0900 (JST) Message-Id: <20210118.050220.1366260423028970742.yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: Waiting for bufdaemon From: Yasuhiro Kimura In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 27.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DJm6y25sjz4RTG X-Spamd-Bar: / X-Spamd-Result: default: False [-0.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:spf-authorized.utahime.org]; TO_DN_NONE(0.00)[]; HFILTER_HELO_IP_A(1.00)[maybe.home.utahime.org]; HFILTER_HELO_NORES_A_OR_MX(0.30)[maybe.home.utahime.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[utahime.org:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[183.180.29.210:from]; ASN(0.00)[asn:2519, ipnet:183.180.0.0/16, country:JP]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[utahime.org:s=maybe2019112701]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[utahime.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[183.180.29.210:from:127.0.2.255]; MID_CONTAINS_FROM(1.00)[]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 20:02:51 -0000 From: Konstantin Belousov Subject: Re: Waiting for bufdaemon Date: Sun, 17 Jan 2021 11:49:40 +0200 > I am working on it, no ETA. > > Interesting point would be to check on machines of other testers, > if the following hides the problem. I tried this patch but unfortunately the problem still happens with my environment. --- Yasuhiro Kimura From owner-freebsd-current@freebsd.org Sun Jan 17 20:30:58 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A69254D7084 for ; Sun, 17 Jan 2021 20:30:58 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic302-22.consmr.mail.gq1.yahoo.com (sonic302-22.consmr.mail.gq1.yahoo.com [98.137.68.148]) (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 4DJmlP3G7Hz4T4m for ; Sun, 17 Jan 2021 20:30:57 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1610915456; bh=Cd2HaY4Pnd1u+IWNtkuP7CHU02P5U0AOnKgCrsv2vI5=; h=Subject:From:Date:To:From:Subject:Reply-To; b=NjF+cjhm5hfrVcsqBj0yRBMSaJq23g5QVpCcqboDwl/Fp2BY8XQag9oT8j3jxicJQmcuVln9lWBX1L9RvqF5lvmyaLoNtmPikuzyLFH+XuHgh/0/RZLubNFs7z17QrC3wi7G0as81pZ0KuAohBwuHICVlGwXETpSlr1+JQED9W4I/iY4yQVyddzroV17ZruX517gGcevXPqK3LWgSZLoirJMkFHK5K9pI+db9V8rM/H6AsVTkx3k1yJXRAx01NH2IRErAvnnOI6z4a4zBeK8jsYyGI1795ZJZYrFbjh1aSWpVqE5Afr9DGePDsDN8R8CPFb6ojlfOiAvErBmePUzsA== X-YMail-OSG: ixDoYs4VM1nPq2scFH9FyUhGO52i17OD8nKkE52E3SaWai2JoSAXdagKcXvNz2y UgbRDViElKbOFzO9lsxI0ubPDIc1gwCmZfb8t6aiDYK_n5jW3dvaV.Qe4iE_QHTDD2dIpB4pAC4Z WOoEIQUV_a_KfBu_WRfbeIEvTD9MWWwZy5n0KpNl6R2yqSYX50rsCcyR7W.ehi9EIKE6CQR9BSK4 fCqGCOZNgAQMMnh6MkIQuPNk5HRWypMHgcBmdAyCyRa8PSPgguSzil0WU7RGJ01kYXbGpMTbyJsA a.Ed0lNZzshKBWzNZA5hMKHbC8.ce1MgEatz9BdVEa4yawMgsVyWYXgNrGthQem7T_gnQ_Wqmfw5 dvscH8cUwvU_fXH8iyFSZbWL3UyuvTpRAmHnLE2onjOnjpm2OhPVksk..rZ6V5KzvrBVqVVyHl96 yHg5MovSVN.Lo9Ds2VX2H_RrRtJwGXASqtCCllpCuA.gmr5c.7eXY5chAFFSbNA8oxT2Z8rHGATC pxIMoDMra19zEspdFsT91fOmJUs1gpFGcyZrmLmlUmdazKWAurjVyZT1OzskVPk7nKMkydD3jGu8 1cwToJQgfpBoRsdaCDJ6bCfx0vQ3lVDgRC9krQR5VCSDgIcMONHrxHxSnIzS2AWYdpGq1gn3K.Oy G5jVgDwakBy3m3xZS9hidM2m3jzsJai3wsJz9eRSuQApJlnLa1EiBqiSGhHhRZd2sItn736VJyuY s7niPlhqfGZNB7Ovk93DUEG_mu7WBCDzO86R2BK_336QkIBORyjrLHcwg_.Pw.es9JOVsmSRofU0 eM6rkfX5bccjX8go3qbNx6WC_QfBMjvDLLkF9l.nrKxAfadJZsgcbxmLG5aKqrgweO99vU16Hrcu 6d_GH2W.Pd9_G6IPFVrvp9szwEWewiy8.TWk3ARh9X_jfkUUgczpZge8ytgRyB1P9cNXG9PYMCzI xUiD.FEYhCbjporqfQBeTHRt08CODqbFY0yU77IfN.8J5W0oEc0ytZ5EDCJZMzGki7h_t1bpcOS0 RoDkZpjRJJzhVCa2aY_XdlSN985KaNRrm31hmt0doHyRXBge9QYu4Ig5vU7fbi7cSEu8GyK1VC6X 4uuxNaaJKMEwX5lXiJoZiBc0fsBsWyFhKLd79ZPt8JIlQE7noSruqO3DEPiAvennfFlNPjjL.b8. hjLcnXEssS_zigoatzaXDNVGaWWKjAoPyJ5nca7pBy6HCC96MQUsfrrY6sQN2bwVcI0.HUku394f KzpnNbkOfPkv32hNiKYU3TmC2AbZH3TSML6LatCyOQ_9sJAJsIcff8oO.MnzOCIfvmqyJALCg6Cr QlxXgxK1e3_AN6qfjiV.MkjBfUCj0dUvq5xNQD7Ei3A.4b2yNr49r3TtFtpsRHb6TIJQjCn0M151 9512gIbUCF6C8BkBUOF_pEfcqanyG1_9cpEvwpBesMnDDsrZ_qp8mxygFgAwCCm0C0wjsCqGhbny r2bnB6Lwe9kbduznvoIYsMvU9pUVYwTngP4UoWtlnkyQF5VA.kiVbfVSA5mt8uwZbuRExNKb9ggi 0Qn1M04M.KL2cq.ciANQSCxJ1rJ1MSH5Q0MuOBtcsq.PO7e8nHZMWrBnPs7aiCyYQ5VYMmpOGvyL pqIqRl.8YAkf_vKHuaxFbsNAMJjK1k0Utc0VtiqFyWoLlZqlFGAAspEwbrjtXLxmcCPfQQnVlQiA IWpdLDKVwJHnFkINlwu825VeTJKxVghuxcnz2jkEI0q23d_4usU5QWv19s9cs2hBufYfzXbbMuZ2 FUagyMWhVUUvTBCwANyPQZreE99kwDRDVRatm8gxhZ1l5Bcb3iQWDAnYeITvoYmXNVhszodbIzDZ blLUjh..U5XR602sn_SH9Au4saZJHogxTr74U1h2V6ilUDZF2gpz1DDrQlrMkfSLitqv4GRj1cU0 DV.Z3m57LwSz_gIpgvcyJxPduY0.jcpOEupsT7jWzIb.Qd9Pw5DD_G3GyTC4rljt7s7VdjZ_4XVX zTzzilVPojnr7nzBolOmdyzXdohVq0SDG54nCmskjl.VgWM0_c5zJXmD5COScUL0YYmBwco4VOQ_ HcQlHMoMGtRyUYerqDPb0xpEqzQ8OOF_XKRfEKFd.rvA0vFWtfCN9PCEbfFNrXlCiNZUPGXhklTi 8qAy7HeSnjdkI4j80Nlcd5CVMBrI8LKJ1h5TDR2m5kWtpLJtFkpXcMYcbg3I0va6ma4vZG0OKrMl OYE0aRgAScyIeEbcEpHA8NkIEaglp80Lzhlzk469BAKrkf94QTSRLPcDsBj4voYUwvycsgg_1D3o _AD96FmcQ0zKPoZfud7XSgZsonIDNk72qR9kBIA1AvKk7.f6TmIyJPSTAiMRvCoS7rYgU0nj6nPi 2VL6oVwp.fXehH3UEmjuwEzqoGnIvQhGcDvP1AiG4b6_YOQqJwYGAC_o70dSciHWG8F93rCAY0cB 3zaifIrN_ecLvAr8TaozHAxSnEnOFfacpLZMdf7fUW9PpJuv3AJ_vhgd.8DVGYZZ641ugUQyfakq Gy2c0vXxZSeUkQbBP9SdZcLsH3lDVzgRTDQWp9sx5P72QlHt_NktdCDU6SXiA27L7qUaNOG4BmHL qqg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.gq1.yahoo.com with HTTP; Sun, 17 Jan 2021 20:30:56 +0000 Received: by smtp409.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID ae0a4229a77b65e188d5e772bbde91a7; Sun, 17 Jan 2021 20:30:52 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld From: Mark Millard In-Reply-To: <20210117174006.GA30728@www.zefox.net> Date: Sun, 17 Jan 2021 12:30:51 -0800 Cc: Current FreeBSD , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> <20210117174006.GA30728@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DJmlP3G7Hz4T4m X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.68.148:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.68.148:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.68.148:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.68.148:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 17 Jan 2021 20:30:58 -0000 On 2021-Jan-17, at 09:40, bob prohaska wrote: > On Sat, Jan 16, 2021 at 03:04:04PM -0800, Mark Millard wrote: >>=20 >> Other than -j1 style builds (or equivalent), one pretty much >> always needs to go looking around for a non-panic failure. It >> is uncommon for all the material to be together in the build >> log in such contexts. >=20 > Running make cleandir twice and restarting -j4 buildworld brought > the process full circle: A silent hang, no debugger response, no > console warnings. That's what sent me down the rabbit hole of make > without clean, which worked at least once... Unfortunately, such a hang tends to mean that log files and such were not completely written out to media. We do not get to see evidence of the actual failure time frame, just somewhat before. (compiler/linker output and such can have the same issues of ending up with incomplete updates.) So, pretty much my notes are unlikely to be strongly tied to any solid evidence: more like alternatives to possibly explore that could be far off the mark. It is not clear if you were using: LDFLAGS.lld+=3D -Wl,--threads=3D1 or some such to limit the multi-thread linking and its memory. I'll note that if -j4 gets 4 links running in parallel it used to be each could have something like 5 threads active on a 4 core machine, so 20 or so threads. (I've not checked llvm11's lld behavior. It might avoid such for defaults.) You have not reported any testing of -j2 or -j3 so far, just -j4 . (Another way of limiting memory use, power use, temperature, etc. .) You have not reported if your boot complained about the swap space size or if you have adjusted related settings to make non-default tradeoffs for swap amanagment for these specific tests. I recommend not tailoring and using a swap size total that is somewhat under what starts to complain when there is no tailoring. > The residue of the top screen shows >=20 > last pid: 63377; load averages: 4.29, 4.18, 4.15 = up 1+07:11:07 04:46:46 > 60 processes: 5 running, 55 sleeping > CPU: 70.7% user, 0.0% nice, 26.5% system, 2.8% interrupt, 0.0% idle > Mem: 631M Active, 4932K Inact, 92M Laundry, 166M Wired, 98M Buf, 18M = Free > Swap: 2048M Total, 119M Used, 1928M Free, 5% Inuse, 16K In, 3180K Out > packet_write_wait: Connection to 50.1.20.26 port 22: Broken pipe > bob@raspberrypi:~ $ ssh www.zefox.com RES STATE C TIME WCPU = COMMAND > ssh: connect to host www.zefox.com port 22: Connection timed out86.17% = c++ > bob@raspberrypi:~ $ 1 99 0 277M 231M RUN 0 3:26 75.00% = c++ > 63245 bob 1 99 0 219M 173M CPU0 0 2:10 73.12% = c++ > 62690 bob 1 98 0 354M 234M RUN 3 9:42 47.06% = c++ > 63377 bob 1 30 0 5856K 2808K nanslp 0 0:00 3.13% = gstat > 38283 bob 1 24 0 5208K 608K wait 2 2:00 0.61% = sh > 995 bob 1 20 0 6668K 1184K CPU3 3 8:46 0.47% = top > 990 bob 1 20 0 12M 1060K select 2 0:48 0.05% = sshd > .... This does not look like ld was in use as of the last top display update's content. But the time between reasonable display updates is fairly long relative to CPU activity so it is only suggestive. > [apologies for typing over the remnants] >=20 > I've put copies of the build and swap logs at >=20 > http://www.zefox.net/~fbsd/rpi2/buildworld/ >=20 > The last vmstat entry (10 second repeat time) reports: > procs memory page disks faults = cpu > r b w avm fre flt re pi po fr sr da0 sd0 in sy = cs us sy id > 4 0 14 969160 91960 685 2 2 1 707 304 0 0 11418 = 692 1273 45 5 50 >=20 > Does that point to the memory exhaustion suggested earlier in the = thread? > At this point /boot/loader.conf contains vm.pfault_oom_attempts=3D"-1", = but=20 > that's a relic of long-ago attempts to use USB flash for root and = swap. > Might removing it stimulate more warning messages? >=20 vm.pfault_oom_attempts=3D"-1" should only be used in contexts where running out of swap will not happen. Otherwise a deadlocked system can result if it does run out of swap. (Run-out has more senses the just the swap partition being fully used: other internal resources for keeping track of the swap can run into its limits.) I've no evidence that the -1 was actually a problem. I do not find any 1000+ ms/w or ms/r figures in swapscript.log . I found 3 examples of a little under 405 (on sdda0*), 3 between 340 and 345 (da0*), 4 in the 200s (da0*), under 60 in the 100s (da0*). It does not look to me like the recorded part had problems with the long latencies that you used to have happen. So I've not found any specific evidence about what led to the hangup. So my earlier questions/suggestions are basically arbitrary and I would not know what to do with any answers to the questions. The only notes that are fairly solid are about the hangup leading to there being some files that were likely incompletely updated (logs, compiler output files, etc.). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Jan 18 01:50:09 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4CE654DDDF2; Mon, 18 Jan 2021 01:50:09 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJvqh0Lzhz4mQy; Mon, 18 Jan 2021 01:50:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 10I1oA88032823 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 17 Jan 2021 17:50:10 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 10I1oApG032822; Sun, 17 Jan 2021 17:50:10 -0800 (PST) (envelope-from fbsd) Date: Sun, 17 Jan 2021 17:50:10 -0800 From: bob prohaska To: bob prohaska Cc: Current FreeBSD , freebsd-arm@freebsd.org Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld Message-ID: <20210118015009.GA31353@www.zefox.net> References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> X-Rspamd-Queue-Id: 4DJvqh0Lzhz4mQy X-Spamd-Bar: - X-Spamd-Result: default: False [-1.10 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-arm]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 01:50:09 -0000 On Sun, Jan 17, 2021 at 12:30:51PM -0800, Mark Millard wrote: > > > On 2021-Jan-17, at 09:40, bob prohaska wrote: > > > On Sat, Jan 16, 2021 at 03:04:04PM -0800, Mark Millard wrote: > >> > >> Other than -j1 style builds (or equivalent), one pretty much > >> always needs to go looking around for a non-panic failure. It > >> is uncommon for all the material to be together in the build > >> log in such contexts. > > > > Running make cleandir twice and restarting -j4 buildworld brought > > the process full circle: A silent hang, no debugger response, no > > console warnings. That's what sent me down the rabbit hole of make > > without clean, which worked at least once... > > Unfortunately, such a hang tends to mean that log files and such > were not completely written out to media. We do not get to see > evidence of the actual failure time frame, just somewhat before. > (compiler/linker output and such can have the same issues of > ending up with incomplete updates.) > > So, pretty much my notes are unlikely to be strongly tied to > any solid evidence: more like alternatives to possibly explore > that could be far off the mark. > > It is not clear if you were using: > > LDFLAGS.lld+= -Wl,--threads=1 > > or some such to limit the multi-thread linking and its memory. No, I wasn't trying to limit ld.lld thread number. > I'll note that if -j4 gets 4 links running in parallel it used > to be each could have something like 5 threads active on a 4 > core machine, so 20 or so threads. (I've not checked llvm11's > lld behavior. It might avoid such for defaults.) > > You have not reported any testing of -j2 or -j3 so far, just > -j4 . (Another way of limiting memory use, power use, temperature, > etc. .) > Not recently, simply because it's so slow to build. On my "production" armv7 machines running stable/12 I do use -j2. But, they get updated only a couple times per year, when there's a security issue. > You have not reported if your boot complained about the swap > space size or if you have adjusted related settings to make > non-default tradeoffs for swap amanagment for these specific > tests. I recommend not tailoring and using a swap size total > that is somewhat under what starts to complain when there is > no tailoring. > Both Pi2 and Pi3 have been complaining about too much swap since I first got them. Near as can be told it's never been a demonstrated problem, thus far. Now, as things like LLVM get bigger and bigger, it seems possible excess swap might cause, or obscure, other problems. For the Pi2 I picked 2 GB from the old "2x physical RAM" rule. > > > The residue of the top screen shows > > > > last pid: 63377; load averages: 4.29, 4.18, 4.15 up 1+07:11:07 04:46:46 > > 60 processes: 5 running, 55 sleeping > > CPU: 70.7% user, 0.0% nice, 26.5% system, 2.8% interrupt, 0.0% idle > > Mem: 631M Active, 4932K Inact, 92M Laundry, 166M Wired, 98M Buf, 18M Free > > Swap: 2048M Total, 119M Used, 1928M Free, 5% Inuse, 16K In, 3180K Out > > packet_write_wait: Connection to 50.1.20.26 port 22: Broken pipe > > bob@raspberrypi:~ $ ssh www.zefox.com RES STATE C TIME WCPU COMMAND > > ssh: connect to host www.zefox.com port 22: Connection timed out86.17% c++ > > bob@raspberrypi:~ $ 1 99 0 277M 231M RUN 0 3:26 75.00% c++ > > 63245 bob 1 99 0 219M 173M CPU0 0 2:10 73.12% c++ > > 62690 bob 1 98 0 354M 234M RUN 3 9:42 47.06% c++ > > 63377 bob 1 30 0 5856K 2808K nanslp 0 0:00 3.13% gstat > > 38283 bob 1 24 0 5208K 608K wait 2 2:00 0.61% sh > > 995 bob 1 20 0 6668K 1184K CPU3 3 8:46 0.47% top > > 990 bob 1 20 0 12M 1060K select 2 0:48 0.05% sshd > > .... > > This does not look like ld was in use as of the last top > display update's content. But the time between reasonable > display updates is fairly long relative to CPU activity > so it is only suggestive. > > > [apologies for typing over the remnants] > > > > I've put copies of the build and swap logs at > > > > http://www.zefox.net/~fbsd/rpi2/buildworld/ > > > > The last vmstat entry (10 second repeat time) reports: > > procs memory page disks faults cpu > > r b w avm fre flt re pi po fr sr da0 sd0 in sy cs us sy id > > 4 0 14 969160 91960 685 2 2 1 707 304 0 0 11418 692 1273 45 5 50 > > > > Does that point to the memory exhaustion suggested earlier in the thread? > > At this point /boot/loader.conf contains vm.pfault_oom_attempts="-1", but > > that's a relic of long-ago attempts to use USB flash for root and swap. > > Might removing it stimulate more warning messages? > > > > vm.pfault_oom_attempts="-1" should only be used in contexts where > running out of swap will not happen. Otherwise a deadlocked system > can result if it does run out of swap. (Run-out has more senses the > just the swap partition being fully used: other internal resources > for keeping track of the swap can run into its limits.) I've no > evidence that the -1 was actually a problem. > > I do not find any 1000+ ms/w or ms/r figures in swapscript.log . > I found 3 examples of a little under 405 (on sdda0*), 3 between > 340 and 345 (da0*), 4 in the 200s (da0*), under 60 in the 100s > (da0*). It does not look to me like the recorded part had problems > with the long latencies that you used to have happen. > > So I've not found any specific evidence about what led to the > hangup. So my earlier questions/suggestions are basically > arbitrary and I would not know what to do with any answers > to the questions. > > The only notes that are fairly solid are about the hangup leading > to there being some files that were likely incompletely updated > (logs, compiler output files, etc.). > The notion that log files might be truncated didn't didn't register until you brought it up. The obvious things to try seem to be: Disable vm.pfault_oom_attempts="-1" Decrease swap partition size Try using WITH_META_MODE WITH_META_MODE seems relatively easy; just add -DWITH_META_MODE to the make command line for buildworld and add filemon_load="YES" to boot/loader.conf, but I wonder about the burdens it'll impose on CPU and disk space/throughput. There's nothing to lose at this stage, but I'm all ears if there's a better approach. Many thanks for your patient good counsel! bob prohaska From owner-freebsd-current@freebsd.org Mon Jan 18 02:13:30 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 538EB4DF30E for ; Mon, 18 Jan 2021 02:13:30 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.oetec.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJwLd1G95z4ndQ for ; Mon, 18 Jan 2021 02:13:28 +0000 (UTC) (envelope-from dclarke@blastwave.org) X-Spam-Status: No X-oetec-MailScanner-From: dclarke@blastwave.org X-oetec-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.351, required 6, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, DKIM_VALID_EF -0.10, NICE_REPLY_A -0.25, URIBL_BLOCKED 0.00) X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-ID: 10I2ClSD009773 X-oetec-MailScanner-Information: Please contact oetec for more information Received: from [172.16.35.2] (cpeac202e7325b3-cmac202e7325b0.cpe.net.cable.rogers.com [99.253.170.241]) (authenticated bits=0) by mail.oetec.com (8.15.2/8.15.2/Debian-8) with ESMTPSA id 10I2ClSD009773 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sun, 17 Jan 2021 21:12:48 -0500 Subject: Re: service -e doesn't really sort does it? the cool tip is slightly off To: freebsd-current@freebsd.org References: From: Dennis Clarke Message-ID: <57364ba6-b680-c8cb-4303-63dbcdd8a187@blastwave.org> Date: Mon, 18 Jan 2021 02:12:46 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4DJwLd1G95z4ndQ X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; NEURAL_HAM_SHORT(-0.98)[-0.978]; RECEIVED_SPAMHAUS_PBL(0.00)[99.253.170.241:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[108.160.241.186:from]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[108.160.241.186:from:127.0.2.255]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 02:13:30 -0000 On 1/17/21 1:46 PM, Graham Perrin wrote: > On 16/01/2021 23:28, Dennis Clarke wrote: > >> … maybe take out the word "sorted". Either that or >> insert the "started order" as the manpage claims  : >> >> root@rhea:/usr/src/freebsd-src # diff -u >> usr.bin/fortune/datfiles/freebsd-tips.orig >> usr.bin/fortune/datfiles/freebsd-tips >> --- usr.bin/fortune/datfiles/freebsd-tips.orig  2021-01-15 >> 00:37:37.863506000 +0000 >> +++ usr.bin/fortune/datfiles/freebsd-tips       2021-01-16 >> 07:46:57.335803000 +0000 >> @@ -517,7 +517,7 @@ >> >>                  -- Lars Engels >>   % >> -If you want to get a sorted list of all services that are started when >> FreeBSD boots, >> +If you want to get a list of all services that are started when FreeBSD >> boots, >>   enter "service -e". >> >>                  -- Lars Engels >> root@rhea:/usr/src/freebsd-src # >> >> Sorry for being all OCD here. Perhaps it should say sorted in the order >> in which they were started. Something like that. >> > > In lieu of 'sorted', how about 'dependency-ordered'? > Anything that makes obvious sense would be nice. When I say "obvious" here I mean "really obvious to a new user that just installed FreeBSD yesterday" and not "obvious to a twenty year expert." Dennis From owner-freebsd-current@freebsd.org Mon Jan 18 03:19:40 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 064C54E061C for ; Mon, 18 Jan 2021 03:19:40 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic314-21.consmr.mail.gq1.yahoo.com (sonic314-21.consmr.mail.gq1.yahoo.com [98.137.69.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJxpy6VnDz4rT6 for ; Mon, 18 Jan 2021 03:19:38 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1610939976; bh=mMtz4Pmk/Q13cf2An/iYxt93mJQsuApiWkqsj1E+/oQ=; h=Subject:From:Date:To:From:Subject:Reply-To; b=MULPrbu3QAFfg7UKvW626PrjoraGm+VfW77T2LWjPbulgaq78xlEQLy+kyvp01vXMIRuVkJZ2LP1kEmF3BWMnKR50Hq79g0iuATZfaom6SZBCEU48uAYsTa2LLpPn8C53TstsC8eQKi7mPAPqh0itQsETOTvc2S6QS9987Ehvquf6Ud+B+BKvwh4Mz/X6sMK4Vkx0X5im/G9iYHRo9djfNDogpqcvO9wLsWSTQxXxjzXYi2GNoVwDP7G5iaKAVKRQJlwzOsuCg59/j8eHJNTnN8+fXYMSerth/ERfhOB7TWsa6DvbsCdOTKhJfFjcnro2yYFPTu+wU1LICnD0MsRow== X-YMail-OSG: lERwqYgVM1n7RAbmxdOGMztN2sTDsgg6Iy7CrRLtRBnJzKGZ9zYcUuIMx5csGwJ QscIuBHaUvd68oUHGleaz0p4yf122CIbz9ACoGrwAY8kqz6V5wrtRtXA0CaHA_r.TXxtZcmMGpIS Ih.28jKhYy6kAUMmnUm2ye4dxuzqpwhQaH3bUGe3TDYhBOVxml84AdlWOuO5rhvWn9xiztVuxmD0 CRYUQv5VCSP3hvmmiW.K.A68xGbiwMwpnXnxBa36BLZInBzsvesY.p8djmaezzfrO8YLGSSmqiaG 70bi5cUzhB_PALBwGKIGIKGsJy8JtYyus7ldkFrNz.WidJxrhuzyNPejssxu_3P_7vWu5z9zDCqD JLSOaLtuLP9aaQRQMkhzFj256hF_JaMvbV0VRGeiT279AmqWLJFhHCMclbItuxFXlnd8RjRtPXRd NCZ.5uvfdfrN4lYT4kZEMiPTlxD8JIX73q1IAj7PSvw_LEcRKfz_X.HU7qLyCafjSTcn4aboeOdv bSC73K4o1slcpty_ZIGRjrZGBUofPp9QLwy7JY_cYdXLXXn7i.NngwaWmPUu3qQopb0oMPqu26BR 6OyUxEoVqYPA0LDHpF4KylhiqLY999DMMyykxJzx221OmFukWdjBg8HQc9yTrATzj6.SiqBZ0T4D Te9O5wgeod4zgwkNMiRjNy4FB.bAHAAlBOtNefVb78CbMVEtb3GNUMlYihOmKJ0JVR.uUy0N99_D 33XfbLWiUJuCom.NM3RmnFwccg6HNgC.gYObe.gMt_Dil..Ll6uQxud8JJGQY8c9y0W7L12WO37s dY9lQdSnL9p8WkeJSmTcULUEgv3z0U8.ZNd8B8noYyLafmeUmHJMVd0_LvVThcygwgq_iJM0PFiw L.4xjm5CZMQ8PlZtn4pXGYyEN9BS2O5IW8V0ZIpyQXTqxM2tgxIbgm_yCQoVNO1wEB8z4p_4KXHs zCwVwKGiMi_1.9HOp34DbJVe1zyr3LXfyi8A1bQnt5b6.r2ks91zvZC6ozJ2HaskvZu98TTQ47Ok 2oOejzhmRCXo9BW2ZN_TFQqrEKZbWtDzb5ufEYjr4iohgr5fPfcOc5_tOwTLvjfnR5o529x1EGO_ kaA6KD4NKkviUXlmJWkf3VJ7QoAysBjshd2bhmXLGinbsXbq49SYsPuyEH8pb0h3DS65m1voe7Af Odrcj3s3wUip6fTbplOlCcIO3y7AOf2nGgDz00OZLCC09Se6Pl6SzM8o_ylzgbP19lBNzdZ8aeua sGq2mdy8wJYY6bMT3rWK9ir1rUAj6CLtqbUNr7zBIT614BAAKhcbs.NihcXpw9jxkuLewv7K2zHz o0.Y27kUAk8CnWMRX105AIlM9fk9BHOFoVc1DR1gOfv5.J2habCbTBxLhRTC42M1XKAYvH4iKQHD j945vEjQzgPH.DjMjqsxTOMj_LQrQFqyaNsdPA7eCIjyeko44QDl7AgOICj7upG87xb5pNNCxifp 4k9u5n8gFeogNdK7tY36dPokKXskpEc2YgE.8ZBNYbDdRn_PLGC4AzAPVRHs_nJGFDGXVkjtsayL pkqiqyI.8BXeQTqmvCA31ivhIKd0zkVOxC17RKmBQHPUIuo_ehTSYB_FQnb4aI8CRR77Iw2fRfsT ax_JvDcgjiYE_VcieYTBIgwZ7WWF5I.LrQHVSkTWFKhWU5SCAid_UY8J18TsTsPiAx7rQY6G_9ir iz8nHx9asiIFnFjCPRq7dMHLeet1UJFNYVEVkDRa5cqOThm8zexxt8Io9wajUCloNChUqeoE.5Rq Ym0gzqOxyDMYHWdaikWm7PZT4qakGoBtOCm1gqdqfvaGpsD.J3LNyZ3xZW23qPpAxIxxvbIq0gRd IbTD.Dms3MgFtg7yzY0Yyflci_EDprzCVzrArciD9VvclRw8p3b1IvU24M8W6iuyZI6WGWg0IF.o U5uitQJsaQudloz2TdJ9.KANEuFj6arT_iRxV84tn6fgYINXgZUi9ms29xE6Y3asq3gFMA1MhCDh yEPQtJ93rhvcqZHu3nQ.koGZLnFQbTFG6y_hhVj0XcTHprqZdjhNp_1E6O5IBNviCtrGpdJWMqoH Zg4O32qPLDlhmkZzjesuP36ulHrPVuKqBnQ28sulJF0IzbqjpqTRZa7lAEFGSht.WMHnLzmshooZ xm3vPqLVgXeAKXoK6JvaqHILrLjB6yuhyfyr8w4b8MqbmbYAKChSHqKg.zRVlBRnZO8YY_nVznP8 Q7PrXV7QtVc8P8mc85tSK3o82wQwtW4NEEnO12LyK2Ic_fcNZQtWl4RO6VvCgi1knmoQ90OsZqOD HXYOePVRIv3bZCM6Q7zvdn2iWntqLvOF.Sf.RIx0Hn_0coZFMxoJdlEGXhGVdHR2Auckkuvpgz9a N_oJwGDZFPW3X_OwNZ4O15bzlrX1EJF7fZhZ6PrZPQOZoQTkPs7mPNxoKXDDQfv9KNQc5tFXl0Wf F8_AiDnOElik_lTHKVL2a8Ayg9MCxIPUXjUdnnnWQn4ca8uD.10MpGpR20V0rIYPxS15eSDRC0UO 2m5EhhzT8D3aPOLyjuNQ4F6M8nsu.Vm5ocf0NYjB8Idn1YURzEgUfoz4b.iXGtXyw3eZVbo.j0ov J_jU- Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.gq1.yahoo.com with HTTP; Mon, 18 Jan 2021 03:19:36 +0000 Received: by smtp403.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID b43a1661d3f58183e7d34af0db0876b0; Mon, 18 Jan 2021 03:19:34 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld From: Mark Millard In-Reply-To: <20210118015009.GA31353@www.zefox.net> Date: Sun, 17 Jan 2021 19:19:33 -0800 Cc: Current FreeBSD , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> <20210118015009.GA31353@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DJxpy6VnDz4rT6 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.69.84:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.69.84:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.84:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.84:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 03:19:40 -0000 On 2021-Jan-17, at 17:50, bob prohaska wrote: > On Sun, Jan 17, 2021 at 12:30:51PM -0800, Mark Millard wrote: >>=20 >>=20 >> On 2021-Jan-17, at 09:40, bob prohaska wrote: >>=20 >>> On Sat, Jan 16, 2021 at 03:04:04PM -0800, Mark Millard wrote: >>>>=20 >>>> Other than -j1 style builds (or equivalent), one pretty much >>>> always needs to go looking around for a non-panic failure. It >>>> is uncommon for all the material to be together in the build >>>> log in such contexts. >>>=20 >>> Running make cleandir twice and restarting -j4 buildworld brought >>> the process full circle: A silent hang, no debugger response, no >>> console warnings. That's what sent me down the rabbit hole of make >>> without clean, which worked at least once... >>=20 >> Unfortunately, such a hang tends to mean that log files and such >> were not completely written out to media. We do not get to see >> evidence of the actual failure time frame, just somewhat before. >> (compiler/linker output and such can have the same issues of >> ending up with incomplete updates.) >>=20 >> So, pretty much my notes are unlikely to be strongly tied to >> any solid evidence: more like alternatives to possibly explore >> that could be far off the mark. >>=20 >> It is not clear if you were using: >>=20 >> LDFLAGS.lld+=3D -Wl,--threads=3D1 >>=20 >> or some such to limit the multi-thread linking and its memory. > No, I wasn't trying to limit ld.lld thread number. You might want to try a significant change in the memory use just to see if it makes a difference or not --despite the extra time. This could included limiting lld thread usage and limiting to a smaller -jN . >> I'll note that if -j4 gets 4 links running in parallel it used >> to be each could have something like 5 threads active on a 4 >> core machine, so 20 or so threads. (I've not checked llvm11's >> lld behavior. It might avoid such for defaults.) >>=20 >> You have not reported any testing of -j2 or -j3 so far, just >> -j4 . (Another way of limiting memory use, power use, temperature, >> etc. .) >>=20 > Not recently, simply because it's so slow to build. On my "production" > armv7 machines running stable/12 I do use -j2. But, they get updated > only a couple times per year, when there's a security issue.=20 See the earlier note about possibly deliberate test of using less memory space. (And more later, below.) >> You have not reported if your boot complained about the swap >> space size or if you have adjusted related settings to make >> non-default tradeoffs for swap amanagment for these specific >> tests. I recommend not tailoring and using a swap size total >> that is somewhat under what starts to complain when there is >> no tailoring. >>=20 > Both Pi2 and Pi3 have been complaining about too much swap > since I first got them. Near as can be told it's never been > a demonstrated problem, thus far. Now, as things like LLVM > get bigger and bigger, it seems possible excess swap might > cause, or obscure, other problems. For the Pi2 I picked 2 > GB from the old "2x physical RAM" rule.=20 I'd take those warnings as FreeSD reporting that the system is expected to be in a mistuned configuration by "normal" criteria. Doing the tuning to allow more swap has the documented tradeoffs: kern.maxswzone . . . Note that swap metadata can be fragmented, which means = that the system can run out of space before it reaches the theoretical limit. Therefore, care should be taken to = not configure more swap than approximately half of the theoretical maximum. (The above is what the warning is about. But then there is . . .) Running out of space for swap metadata can leave the = system in an unrecoverable state. Therefore, you should only change this parameter if you need to greatly extend the = KVM reservation for other resources such as the buffer cache = or kern.ipc.nmbclusters. Modifies kernel option VM_SWZONE_SIZE_MAX. (NOTE: That last paragraph is talking about *decreasing* kern.maxswzone to get more room for non-swap-managment things in KVM. [Too bad the wording says "change".] But increasing kern.maxswzone to allow more swap leaves less space for the buffer cache or like, making for tradeoffs being involved.) >>> The residue of the top screen shows >>>=20 >>> last pid: 63377; load averages: 4.29, 4.18, 4.15 = up 1+07:11:07 04:46:46 >>> 60 processes: 5 running, 55 sleeping >>> CPU: 70.7% user, 0.0% nice, 26.5% system, 2.8% interrupt, 0.0% = idle >>> Mem: 631M Active, 4932K Inact, 92M Laundry, 166M Wired, 98M Buf, 18M = Free >>> Swap: 2048M Total, 119M Used, 1928M Free, 5% Inuse, 16K In, 3180K = Out >>> packet_write_wait: Connection to 50.1.20.26 port 22: Broken pipe >>> bob@raspberrypi:~ $ ssh www.zefox.com RES STATE C TIME = WCPU COMMAND >>> ssh: connect to host www.zefox.com port 22: Connection timed = out86.17% c++ >>> bob@raspberrypi:~ $ 1 99 0 277M 231M RUN 0 3:26 = 75.00% c++ >>> 63245 bob 1 99 0 219M 173M CPU0 0 2:10 = 73.12% c++ >>> 62690 bob 1 98 0 354M 234M RUN 3 9:42 = 47.06% c++ >>> 63377 bob 1 30 0 5856K 2808K nanslp 0 0:00 = 3.13% gstat >>> 38283 bob 1 24 0 5208K 608K wait 2 2:00 = 0.61% sh >>> 995 bob 1 20 0 6668K 1184K CPU3 3 8:46 0.47% = top >>> 990 bob 1 20 0 12M 1060K select 2 0:48 0.05% = sshd >>> .... >>=20 >> This does not look like ld was in use as of the last top >> display update's content. But the time between reasonable >> display updates is fairly long relative to CPU activity >> so it is only suggestive. >>=20 >>> [apologies for typing over the remnants] >>>=20 >>> I've put copies of the build and swap logs at >>>=20 >>> http://www.zefox.net/~fbsd/rpi2/buildworld/ >>>=20 >>> The last vmstat entry (10 second repeat time) reports: >>> procs memory page disks faults = cpu >>> r b w avm fre flt re pi po fr sr da0 sd0 in sy = cs us sy id >>> 4 0 14 969160 91960 685 2 2 1 707 304 0 0 11418 = 692 1273 45 5 50 >>>=20 >>> Does that point to the memory exhaustion suggested earlier in the = thread? >>> At this point /boot/loader.conf contains = vm.pfault_oom_attempts=3D"-1", but=20 >>> that's a relic of long-ago attempts to use USB flash for root and = swap. >>> Might removing it stimulate more warning messages? >>>=20 >>=20 >> vm.pfault_oom_attempts=3D"-1" should only be used in contexts where >> running out of swap will not happen. Otherwise a deadlocked system >> can result if it does run out of swap. (Run-out has more senses the >> just the swap partition being fully used: other internal resources >> for keeping track of the swap can run into its limits.) I've no >> evidence that the -1 was actually a problem. >>=20 >> I do not find any 1000+ ms/w or ms/r figures in swapscript.log . >> I found 3 examples of a little under 405 (on sdda0*), 3 between >> 340 and 345 (da0*), 4 in the 200s (da0*), under 60 in the 100s >> (da0*). It does not look to me like the recorded part had problems >> with the long latencies that you used to have happen. >>=20 >> So I've not found any specific evidence about what led to the >> hangup. So my earlier questions/suggestions are basically >> arbitrary and I would not know what to do with any answers >> to the questions. >>=20 >> The only notes that are fairly solid are about the hangup leading >> to there being some files that were likely incompletely updated >> (logs, compiler output files, etc.). >>=20 >=20 > The notion that log files might be truncated didn't didn't register=20 > until you brought it up.=20 >=20 > The obvious things to try seem to be: > Disable vm.pfault_oom_attempts=3D"-1" > Decrease swap partition size > Try using WITH_META_MODE I'll note that you may well have already spent more time not getting complete builds than doing one "use less memory" test would have taken (linker thread count limits, smaller -jN). To find fairly optimal settings for building on the RPi2 V1.1, you may have to explore on both sides of the optimal settings range, just to identify the optimal range for the settings as being between known bounds. Of course, for all I know, the "use less memory" tests might also fail. If that happened, it would tend to stop spending time testing configurations even less likely to finish building. > WITH_META_MODE seems relatively easy; just add -DWITH_META_MODE to = the make > command line for buildworld and add filemon_load=3D"YES" to = boot/loader.conf, > but I wonder about the burdens it'll impose on CPU and disk = space/throughput.=20 > There's nothing to lose at this stage, but I'm all ears if there's a = better > approach. You could trade off some I/O by not generating swapscript.log since it seems to not be of much help for the current issue. I'll also note that META_MODE by default does not generate as much stdout text but stores more across the various .meta files. So, by default, buildworld.log (by itself) would be much smaller. (So disabling recording of buildworld.log would not make much of a difference.) I'll remind of the things that are environment-only variables, including WITH_META_MODE : QUOTE The environment of make(1) for the build can be controlled via the SRC_ENV_CONF variable, which defaults to /etc/src-env.conf. Some examples that may only be set in this file are WITH_DIRDEPS_BUILD, = and WITH_META_MODE, and MAKEOBJDIRPREFIX as they are environment-only variables. END QUOTE "may only be set in this file" is false relative to setting the enviromnent on the command line but true compared to the likes of putting the text in /etc/src.conf or the like. My script for building for armv7 in a armv7 context looks something like: script = ~/sys_typescripts/typescript_make_armv7_nodebug_clang_bootstrap-armv7-host= -$(date +%Y-%m-%d:%H:%M:%S) \ env __MAKE_CONF=3D"/root/src.configs/make.conf" SRCCONF=3D"/dev/null" = SRC_ENV_CONF=3D"/root/src.configs/src.conf.armv7-clang-bootstrap.armv7-hos= t" \ WITH_META_MODE=3Dyes \ MAKEOBJDIRPREFIX=3D"/usr/obj/armv7_clang/arm.armv7" \ make $* (So I happened to not use -DWITH_META_MODE . The context is /bin/sh based, by the way.) There are contexts for which I control UBLR_LOADADDR via an additional line in the above, such as: WORLD_FLAGS=3D"${WORLD_FLAGS} UBLDR_LOADADDR=3D0x42000000" \ (But such is old material that I've not validated as being needed in even remotely modern times.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Jan 18 07:01:27 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 908E74E35F4 for ; Mon, 18 Jan 2021 07:01:27 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DK2kt5z2gz3HgR for ; Mon, 18 Jan 2021 07:01:26 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-lf1-x12f.google.com with SMTP id x20so22487808lfe.12 for ; Sun, 17 Jan 2021 23:01:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:from:to:subject:date:message-id :mime-version; bh=A4K08qFwAckC+jEjPGlmTaYyLUkp2MAMA9Y+16UZ0/g=; b=MLYRWVm4SYJ6mw1WRCVpFELJBwxnv6fRlIpgmicN5s3hkwMVtIYmoGyfQuTrgJ4328 ocv3tjb8S3PjqH//hPzpjK+ys+gDV31ppwHo8q+a14yzlzvCEAqzuZQ6EqCWr+6H0sAa XNmh71MTyfLEV6j308Y5LSiY658wGFzVwntUxpAvL9GxuShAFo375ON3BFY2FJe8sEEu +RWejCwJUve21tJkhjH6enR9pcwd15aD9GstdruxmVYwnAjQ44h8kUj2dghwW7p9knT2 DYmXhnjHfp0uf1hkGvSjDYl/lWrbTzj1N2RzhjMKWs/fkue4/ZGHpkl8npFoUnXXAx9w W3cw== X-Gm-Message-State: AOAM532Y/aMZuvwZjj2XubhcCUfO/zWaSYddnaiIB7Fq/JhdvGprFXxJ buBjRYtR7NtD+vnxuq59NfV6Yz5qsWc= X-Google-Smtp-Source: ABdhPJyrjNii9ujwFbkElP0u5WloekKkKmOMSEURZ6vzZ4gKujwmYAQuRAilIv8KbiFFVspZjkovvQ== X-Received: by 2002:a05:6512:52c:: with SMTP id o12mr11053974lfc.559.1610953284947; Sun, 17 Jan 2021 23:01:24 -0800 (PST) Received: from localhost (customer-109-238-136-64.stosn.net. [109.238.136.64]) by smtp.gmail.com with ESMTPSA id c8sm1799759lfr.138.2021.01.17.23.01.23 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 17 Jan 2021 23:01:24 -0800 (PST) User-agent: mu4e 1.2.0; emacs 27.1 From: Malcolm Matalka To: FreeBSD Current Subject: Name of touchpad changed in latest rev Date: Mon, 18 Jan 2021 08:01:23 +0100 Message-ID: <86czy2n2yk.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 4DK2kt5z2gz3HgR X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.97 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.97)[-0.967]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::12f:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::12f:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::12f:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 07:01:27 -0000 I just installed the below revision, and looks like the name the mouse shows up as has changed. Not sure if this is intended or not. What was "SynPS/2 Synaptics TouchPad" and now it is "DELL07E6:00 06CB:76AF TouchPad". Rev: de57c3d8825896ee6dfbb4934095459f6836bf65 Xorg log below. [ 25.219] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6) [ 25.219] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev pointer catchall" [ 25.219] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall" [ 25.219] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput pointer catchall" [ 25.219] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall" [ 25.219] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics TouchPad' [ 25.219] (**) SynPS/2 Synaptics TouchPad: always reports core events [ 25.219] (**) Option "Device" "/dev/input/event6" [ 25.219] (**) Option "_source" "server/udev" [ 27.447] (EE) xf86OpenSerial: Cannot open device /dev/input/event6 Input/output error. [ 27.447] (II) event6: opening input device '/dev/input/event6' failed (Input/output error). [ 27.447] (II) event6 - failed to create input device '/dev/input/event6'. [ 27.447] (EE) libinput: SynPS/2 Synaptics TouchPad: Failed to create a device for /dev/input/event6 [ 27.447] (EE) PreInit returned 2 for "SynPS/2 Synaptics TouchPad" [ 27.447] (II) UnloadModule: "libinput" [ 27.447] (II) config/udev: Adding input device DELL07E6:00 06CB:76AF Mouse (/dev/input/event7) [ 27.447] (**) DELL07E6:00 06CB:76AF Mouse: Applying InputClass "evdev pointer catchall" [ 27.447] (**) DELL07E6:00 06CB:76AF Mouse: Applying InputClass "libinput pointer catchall" [ 27.447] (II) Using input driver 'libinput' for 'DELL07E6:00 06CB:76AF Mouse' [ 27.447] (**) DELL07E6:00 06CB:76AF Mouse: always reports core events [ 27.447] (**) Option "Device" "/dev/input/event7" [ 27.447] (**) Option "_source" "server/udev" [ 27.448] (II) event7 - DELL07E6:00 06CB:76AF Mouse: is tagged by udev as: Mouse [ 27.448] (II) event7 - DELL07E6:00 06CB:76AF Mouse: device is a pointer [ 27.448] (II) event7 - DELL07E6:00 06CB:76AF Mouse: device removed [ 27.448] (**) Option "config_info" "udev:/dev/input/event7" [ 27.448] (II) XINPUT: Adding extended input device "DELL07E6:00 06CB:76AF Mouse" (type: MOUSE, id 11) [ 27.449] (**) Option "AccelerationScheme" "none" [ 27.449] (**) DELL07E6:00 06CB:76AF Mouse: (accel) selected scheme none/0 [ 27.449] (**) DELL07E6:00 06CB:76AF Mouse: (accel) acceleration factor: 2.000 [ 27.449] (**) DELL07E6:00 06CB:76AF Mouse: (accel) acceleration threshold: 4 [ 27.449] (II) event7 - DELL07E6:00 06CB:76AF Mouse: is tagged by udev as: Mouse [ 27.449] (II) event7 - DELL07E6:00 06CB:76AF Mouse: device is a pointer [ 27.450] (II) config/udev: Adding input device DELL07E6:00 06CB:76AF TouchPad (/dev/input/event8) [ 27.450] (**) DELL07E6:00 06CB:76AF TouchPad: Applying InputClass "evdev pointer catchall" [ 27.450] (**) DELL07E6:00 06CB:76AF TouchPad: Applying InputClass "evdev touchpad catchall" [ 27.450] (**) DELL07E6:00 06CB:76AF TouchPad: Applying InputClass "libinput pointer catchall" [ 27.450] (**) DELL07E6:00 06CB:76AF TouchPad: Applying InputClass "libinput touchpad catchall" [ 27.450] (II) Using input driver 'libinput' for 'DELL07E6:00 06CB:76AF TouchPad' [ 27.450] (**) DELL07E6:00 06CB:76AF TouchPad: always reports core events [ 27.450] (**) Option "Device" "/dev/input/event8" [ 27.450] (**) Option "_source" "server/udev" [ 27.451] (II) event8 - DELL07E6:00 06CB:76AF TouchPad: is tagged by udev as: Mouse Touchpad [ 27.452] (II) event8 - DELL07E6:00 06CB:76AF TouchPad: device is a touchpad [ 27.452] (II) event8 - DELL07E6:00 06CB:76AF TouchPad: device removed [ 27.452] (**) Option "config_info" "udev:/dev/input/event8" [ 27.452] (II) XINPUT: Adding extended input device "DELL07E6:00 06CB:76AF TouchPad" (type: TOUCHPAD, id 12) [ 27.454] (**) Option "AccelerationScheme" "none" [ 27.454] (**) DELL07E6:00 06CB:76AF TouchPad: (accel) selected scheme none/0 [ 27.454] (**) DELL07E6:00 06CB:76AF TouchPad: (accel) acceleration factor: 2.000 [ 27.454] (**) DELL07E6:00 06CB:76AF TouchPad: (accel) acceleration threshold: 4 [ 27.455] (II) event8 - DELL07E6:00 06CB:76AF TouchPad: is tagged by udev as: Mouse Touchpad [ 27.456] (II) event8 - DELL07E6:00 06CB:76AF TouchPad: device is a touchpad From owner-freebsd-current@freebsd.org Mon Jan 18 14:16:19 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1EC144ECD4B for ; Mon, 18 Jan 2021 14:16:19 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKDNd6sGmz4TMk; Mon, 18 Jan 2021 14:16:17 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-ed1-x52a.google.com with SMTP id p22so17727067edu.11; Mon, 18 Jan 2021 06:16:17 -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:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=KsqUZW04/KDYcMFWoVh7HW2q7UyYA48c7NE8W1cw5EA=; b=ivJ4lqCn7rg7ivX7lxIrQDLT1HnBzlrTE5F7F8fYxiXVI+yVaoAYoskWwiThLYUd9c OummEsKrr8SIapBmEUV5YQnqCAS3b7nAQqAwAzQdfVASy7ZdmdZjFcPwNLgc0uqz9gDV kWe2x6H+CnAZnS+vA2BIMbq5YqYfcDG7aEGNHbyJ+5ZjPgakyU2n4xhI/y9+dREu/w5O A59Qij2aX+l5JIjU6QLvkdLOrTcVth/59y4M10iYcDt3LR+Db98VBLXNAgJDePf/ItXg 0/aBXljgT4y0Az8ZeeJE3sbG+oPbwOp5yp487G4Ljk+g82Vbai7HjV3EgTLb2CN1p8fb /VpA== X-Gm-Message-State: AOAM531EmW6JUvcL4/ymBeBa8yJfSjxe3mKAXtXgxZ3w3v7FAtkYAPHa QBYXfxWtO1a6PuFM+b8HntyA0Vn7g5Z4Iw== X-Google-Smtp-Source: ABdhPJzvNSjBRHZ9SYftb9xrf97tDLhdKKwr/DYZFVdKENhbrBS3+dSrlhVvuvkuoFhzt9eDY4lLTg== X-Received: by 2002:a50:fe0e:: with SMTP id f14mr19956888edt.159.1610979376387; Mon, 18 Jan 2021 06:16:16 -0800 (PST) Received: from MacBook-Pro-van-Johan.local (85-147-130-226.cable.dynamic.v4.ziggo.nl. [85.147.130.226]) by smtp.gmail.com with ESMTPSA id dm6sm6066796ejc.32.2021.01.18.06.16.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Jan 2021 06:16:15 -0800 (PST) Subject: Re: boot loader blank screen To: Alan Somers , freebsd Current References: <358513ba-699f-8af8-ed4e-a08fd1012db0@codenetworks.net> From: Johan Hendriks Message-ID: <103b8db6-09bc-5ff9-d355-4c0f4e759fc2@gmail.com> Date: Mon, 18 Jan 2021 15:16:14 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 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-Rspamd-Queue-Id: 4DKDNd6sGmz4TMk X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::52a:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_SHORT(1.00)[0.999]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::52a:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52a:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 14:16:19 -0000 On 16/01/2021 21:15, Alan Somers wrote: > On Sat, Jan 16, 2021 at 8:39 AM John Kennedy wrote: > >> On Fri, Jan 15, 2021 at 03:51:38PM +0200, Toomas Soome wrote: >>> Could you please check latest current now?:) >> Success! With main-c255999-g0bc776f3da70, I've been able to comment out >> the >> screen.textmode=0 (so, back to the default like I originally was). >> I needed to set vbe_max_resolution="800x600" to get the non text version of the boot loader. From owner-freebsd-current@freebsd.org Mon Jan 18 17:27:47 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0C2D24F0A7D for ; Mon, 18 Jan 2021 17:27:47 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f170.google.com (mail-oi1-f170.google.com [209.85.167.170]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKJdZ6pc9z4j8W for ; Mon, 18 Jan 2021 17:27:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f170.google.com with SMTP id p5so18399885oif.7 for ; Mon, 18 Jan 2021 09:27:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BdRRPjhCwFPyVeNxExg077nn6IHQhbycHeUR8qhAMQ0=; b=WRYKA74p2P2KO09nuyq06aOtjFA7IS6AtQCoYGX4In3XEsncu3bsKlI8P9fOsx6dQM bB3k71SWB8hTUO8sqGwODdOptLVf72G0CUMhXfO8fUEjRgStYFpHoQ2QGSWxbFiHT23H 5GEkGP5P4Xq3UyhSMPrYKjXGWDpt4/m7TV9HOUuRLhrl+zPEFe4etb9/i5AEGWh9pxRX Ytf+2jEP9e2ki75Ef6e2Fj9EH+I+eyb3D72FRA83GPpn74wOQzeHCwucbX8UUeG9Q3nn fdAPGmnm6X0nte7g/TrPisvqqwF+tADFEEZx8CXoKAhjvlst87TvkiMe6JUW6P+B/2J6 ugrA== X-Gm-Message-State: AOAM532IXm6I+iPE5r5MKiXX+5OIeWkIn2KbxF77a1zPJGtkoWF2kVj/ 6NQnRnPhhwnoOAefTv0ByDq2mZtFnjcif3myDaM= X-Google-Smtp-Source: ABdhPJwVdEieLtKjMjsLkXQvzvY5fqcQgnmYflbUCHREIJoiYQF/dIFjFVI9J/l8l/05SPYfp3NIab3JluqdolZwa+Q= X-Received: by 2002:aca:6708:: with SMTP id z8mr256603oix.55.1610990865675; Mon, 18 Jan 2021 09:27:45 -0800 (PST) MIME-Version: 1.0 References: <358513ba-699f-8af8-ed4e-a08fd1012db0@codenetworks.net> <103b8db6-09bc-5ff9-d355-4c0f4e759fc2@gmail.com> In-Reply-To: <103b8db6-09bc-5ff9-d355-4c0f4e759fc2@gmail.com> From: Alan Somers Date: Mon, 18 Jan 2021 10:27:34 -0700 Message-ID: Subject: Re: boot loader blank screen To: Johan Hendriks Cc: freebsd Current X-Rspamd-Queue-Id: 4DKJdZ6pc9z4j8W X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 17:27:47 -0000 On Mon, Jan 18, 2021 at 7:16 AM Johan Hendriks wrote: > > On 16/01/2021 21:15, Alan Somers wrote: > > On Sat, Jan 16, 2021 at 8:39 AM John Kennedy wrote: > > > >> On Fri, Jan 15, 2021 at 03:51:38PM +0200, Toomas Soome wrote: > >>> Could you please check latest current now?:) > >> Success! With main-c255999-g0bc776f3da70, I've been able to comment > out > >> the > >> screen.textmode=0 (so, back to the default like I originally was). > >> > I needed to set vbe_max_resolution="800x600" to get the non text version > of the boot loader. > Oh, I see. "hw.vga.textmode" got renamed to "screen.textmode". And it works both ways now. No need to set vbe_max_resolution. -Alan From owner-freebsd-current@freebsd.org Mon Jan 18 17:51:42 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D872D4F17AF for ; Mon, 18 Jan 2021 17:51:42 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKK993fHrz4lZr for ; Mon, 18 Jan 2021 17:51:41 +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.16.1/8.16.1) with ESMTPS id 10IHpXth049579 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 18 Jan 2021 09:51:33 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 10IHpXNV049578 for freebsd-current@freebsd.org; Mon, 18 Jan 2021 09:51:33 -0800 (PST) (envelope-from sgk) Date: Mon, 18 Jan 2021 09:51:33 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: bus_dmamem_alloc failed to align memory properly Message-ID: <20210118175133.GA49553@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 4DKK993fHrz4lZr X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.95.76.21:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[128.95.76.21:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM, none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 17:51:42 -0000 I've used a SCHED_BSD for a long time on my i586-*-freebsd laptop. Recently, FreeBSD just locks up on this system. No panic. No screen. No keyboard. Nothing. So, yesterday, while trying to deal with the blank console problem, I switch to SCHED_ULE to see if solved this lock-up issue. It doesn't. :-( I now have a number of messages during boot. % dmesg | grep align bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. I never seen these messages, so is this normal for SCHED_ULE. In addition, to the mystrey lock-up. It now seems that wpa_supplicant is broken. The initial instances, started at boot, is using 100% CPU. I need to kill that instance along with openvpn (which of course needs the network). The D-Link cardbud ath NIC is ejected, re-insert it, and the network start up as normal. -- Steve From owner-freebsd-current@freebsd.org Mon Jan 18 17:51:47 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 038534F1962 for ; Mon, 18 Jan 2021 17:51:46 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-54.consmr.mail.gq1.yahoo.com (sonic315-54.consmr.mail.gq1.yahoo.com [98.137.65.30]) (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 4DKK9F3Q9Hz4lKQ for ; Mon, 18 Jan 2021 17:51:45 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1610992303; bh=lEsg7elEJjOot9rQJVWtswqAdIIFpiPo+Sy4U6L8lLe=; h=Subject:From:Date:To:From:Subject:Reply-To; b=rMqpstJcLvy8BhnafafFoqPwv7uPZF4P33SvW95QDDZPZV6hJlbdJiw4NfZ3j8eiYbCUBBCipL6KyK0rYHEyPFuEPqjLZv3L9F6NibX6BkLkd/2q6CxduYPxK7mijFP45bDxtfWXpemjd1u+jfBHDZzFkr/Q6LTu3YzuUHC3PjG+pSLfrlKh3YHxajscuGPGNm2/y7QdRcNFmPIyj8as2fqmPeF3A/lkikA9jocBXrO5bqRG9BxiOyIG8le35qilRznEaOTK1OF67ql3ATrCnAqtx0UQ329eQhgh2tjba/uVOj02zm108K/idpRo+odT4yyPUyYqu2X+Vc3fF1VifA== X-YMail-OSG: zYlgZD8VM1kZwzhiI.afT6.0PTu.97QtdJqE1JxAL82DzaIM8VDB3eH_4X2Lm51 .QuIJkcWmRCfI8pmAZb18f5VKRbwx.U9ZKbPtHqe3Gi4GzTN3bOJYUqkEdBmAB2hJXwfFGqOqSY0 Bm08sspkkhl1QM0rq4EFX06wn7vpeUp_iHDanAtoLyle3Blj7Ml4wqFzaaZAYm0_ms4lIbyrI7if CauK7gtaxU2o06YpYKMeO7pIJUYL56vnAKMUrsvQ7TXtHXyZNcN668AhJdNZc.mjI6XtM3pwehzH wQ0xa35MibKz9TX8EHmgmvW2MgVh9allbDwcD3qbvTd6Dl5S8aBSPcTDcVyNfMkPJCL0nzK0r85u TyAPYJx.Q0VzMGimFVO4xBDETewConbWeNftR14m_XUtF29JRwbYzFe5.KQssDb_2yibd5Fr47om O6rXf.ZbpQ3h35CnhUD8qNApSSUldBiGUnkvmc.2aY.wvcfNpkYwJxnTOJzimF.h0oUANcFkkUFD bQZ0cMAdNiLhivOSfXuPqAmthgKf8ux7.l4LHwW2pJLYrKs4SNs1UekDLwZlKlAfHMbt_2tvHhpi HnEZeR10IPOPxT.PxSR0UyFl3b8cGLPKMBeRfY1HDH8eSlMpMHL_yzfHeyniuDKFSbruZtshmCDP n3jJWAhACpVHSxccsbM3yrJfH6bKksgqrEzGiR4bIjUGkr4zDiAj9MxXmnopw8oI1AouSv.E9NeX Rk27bI9aGsvmGBVT_MlELRPEkP93nIuadKKHCjBBAn7aXulBnDhS_D65hc5ukLYzClPqNBaHbyd0 BJr5NVvTPMgzYw3qpU3X9jlXXToirwTxnPkCqR6EmH56mkHZ1esxmnlKCaZVpaBIVt4EvXwMkwwV 1pLRj7P3VEUqAVG65EboxO4qcT0A.AciqPt.ozAatiBSco_pyq03Uaasz1cPFBIdB5xsUUjdW605 zKnkHTOS9lQNSUL6QXGboqL8M6oHTyKhzzkk8ATdcdOKLHWXD6hONVOKZmy6vp8X14rmYkBlGXsR bHOF7Qv3T.nG9dnBTsmxVhYPb1hQZnsezloRszhoLB7N16K1wtNbZGHEqIshnzhthRl9f5UR97uy fAIyO9PLwCoFEG9j0PmVk1P_Etv15VrWZr25U6NkHo9wMHBOpzzpY02BubcVRjIpMrw7nai8mUOU 6FIW9nkbE9x5wj7TL7uzvtLWP7Q4CjxbRTlOt7ckZiGQOD.Fpk64StYC6W9_GZD5hdR9gdXcXtmT ltqexgGB3eVJ382vF.1olA79KqztH3C2YLZC7xzqUApnPiFZCg2IRlifyqWkg.g.VrkwX09HRX8v wJWW4GLzPjAsV7dbAJYbdtXEjMoQKTVJ5lUnO6Ddt4Uf3P.kWibBjLVGpDgtOi8GJX1BzwDnvo1n V2vKpF9f.hyE0LL1DI56545RNQPH91hNdYBhlruSlAlmkSiVqeHq9pzRIPm5Lgnhhw2v9Z_w8ulV DcWDfb2ylGZiHCbNtEe4gVJMMP.Z2p1WL.rY2JlQbHYFVOnlGfqlJh_FnwyL1Zq3ibQBWKX9WNoW 90zP58YDlYd9XmHU8uBSlhLVubZ_Lpny4pbUlpn_3GsBPz8a9tNKYJHVddW1s76cOUYeAYMgK8N. smWzDL_VeEc2EZIbdIElLzi4dYOmCCpSEMEI775_HshJXLV6vZgWQcgJYCJEKPcYViwGUq2mcmm7 3khoqkttO0JE02aqcxjc7QLP.mkcWtUWlRWJ2pEpEVvq3oVG96vDiAKWkmEuVILvlPoPi_Xh7ib5 vS0YYeFATCas7zFma5e0ZKTEO4Eoui.BAHTeXgwLA7FpjbDB8PD_VflYRtHEC_thzmPnuRhKyfOm dOQIOxxRMad1u0c.jfR1jwpUllLjFC5O6EmZcxqbjeEfKW6QKPMIZCX54aOsE0xDImhwT8ergT6Y G5ku.stm.k6XR5Rr9CZ6ybs47kM6IlH2XmU5y733yCrhZbvpfzzl6lGAif44pSBr0rqc35XFvR7l Ttrni3BcbVld0UHy2cq3ruh_lwTf.Tm1jNJMjec13hVWnMxndkUVDQrTbu2MgfkrcGgtudMbF_iS WF0AzHmXaexyJTF6sgJx_nZmCTHyzZtczXsXAheU7hBvHARLXEdwIPe15MedLN2ddj3hLK4FlDhS Ee5JCMgs7n2zwlULCp0KtBD2p7iZnBjGDrUySi6c2iAvCU8hdsITMqcLN9SxjV5r022nJ_WlkNnZ wRDQX2bPpz6_OAXzjinscOBph_npGc3tEsYZWM_rTxFmd7Vlgugd3rvJTR8iVVPdApr8UfEqsLmI tf7aUYrT_mpghEBbpDlt6o02Nq6TepNDB3o60m_V.j8QzIMYG1qzFTWyEG7J94yDBNR5c0gzKgab pfimAPNqJ5CJ0WP6xtVhugGpGG1aE7FdtzW5wRNxm4vtghmpcAYd1.PV_kPMmjmH8FSUbaZAP4co muRdN90NFwkEPp9UZrtS3UCoNfoyaerIZX0dzp4fdUc0oBTWI.vkTTAM1mYGqFjgQ4uMMW0YvGiL 8voj2Nlj6hDPtB1dPcbLUeTdFPlcmAnrFWxiu9D.pmLsoYI2CdM6Z9_aRB0H1Di_5b17ldBoCZ8L 4tPDDqpSHW0f8DgmODuNGKFDuhj1z3rKXKmLgP5A6ZIMCAqAgcxTwyXI- Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Mon, 18 Jan 2021 17:51:43 +0000 Received: by smtp423.mail.bf1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 8cef55378b27df9b86ffdc22876e24e7; Mon, 18 Jan 2021 17:51:39 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld From: Mark Millard In-Reply-To: <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> Date: Mon, 18 Jan 2021 09:51:36 -0800 Cc: Current FreeBSD , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> <20210118015009.GA31353@www.zefox.net> <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DKK9F3Q9Hz4lKQ X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.65.30:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.65.30:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.30:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.30:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 17:51:47 -0000 On 2021-Jan-17, at 19:19, Mark Millard wrote: > On 2021-Jan-17, at 17:50, bob prohaska wrote: >=20 >> On Sun, Jan 17, 2021 at 12:30:51PM -0800, Mark Millard wrote: >>>=20 >>>=20 >>> On 2021-Jan-17, at 09:40, bob prohaska = wrote: >>>=20 >>>> On Sat, Jan 16, 2021 at 03:04:04PM -0800, Mark Millard wrote: >>>>>=20 >>>>> Other than -j1 style builds (or equivalent), one pretty much >>>>> always needs to go looking around for a non-panic failure. It >>>>> is uncommon for all the material to be together in the build >>>>> log in such contexts. >>>>=20 >>>> Running make cleandir twice and restarting -j4 buildworld brought >>>> the process full circle: A silent hang, no debugger response, no >>>> console warnings. That's what sent me down the rabbit hole of make >>>> without clean, which worked at least once... >>>=20 >>> Unfortunately, such a hang tends to mean that log files and such >>> were not completely written out to media. We do not get to see >>> evidence of the actual failure time frame, just somewhat before. >>> (compiler/linker output and such can have the same issues of >>> ending up with incomplete updates.) >>>=20 >>> So, pretty much my notes are unlikely to be strongly tied to >>> any solid evidence: more like alternatives to possibly explore >>> that could be far off the mark. >>>=20 >>> It is not clear if you were using: >>>=20 >>> LDFLAGS.lld+=3D -Wl,--threads=3D1 >>>=20 >>> or some such to limit the multi-thread linking and its memory. >> No, I wasn't trying to limit ld.lld thread number. >=20 > You might want to try a significant change in the memory use > just to see if it makes a difference or not --despite the > extra time. This could included limiting lld thread usage > and limiting to a smaller -jN . >=20 >>> I'll note that if -j4 gets 4 links running in parallel it used >>> to be each could have something like 5 threads active on a 4 >>> core machine, so 20 or so threads. (I've not checked llvm11's >>> lld behavior. It might avoid such for defaults.) >>>=20 >>> You have not reported any testing of -j2 or -j3 so far, just >>> -j4 . (Another way of limiting memory use, power use, temperature, >>> etc. .) >>>=20 >> Not recently, simply because it's so slow to build. On my = "production" >> armv7 machines running stable/12 I do use -j2. But, they get updated >> only a couple times per year, when there's a security issue.=20 >=20 > See the earlier note about possibly deliberate test of > using less memory space. (And more later, below.) >=20 >>> You have not reported if your boot complained about the swap >>> space size or if you have adjusted related settings to make >>> non-default tradeoffs for swap amanagment for these specific >>> tests. I recommend not tailoring and using a swap size total >>> that is somewhat under what starts to complain when there is >>> no tailoring. >>>=20 >> Both Pi2 and Pi3 have been complaining about too much swap >> since I first got them. Near as can be told it's never been >> a demonstrated problem, thus far. Now, as things like LLVM >> get bigger and bigger, it seems possible excess swap might >> cause, or obscure, other problems. For the Pi2 I picked 2 >> GB from the old "2x physical RAM" rule.=20 >=20 > I'd take those warnings as FreeSD reporting that the system is > expected to be in a mistuned configuration by "normal" criteria. > Doing the tuning to allow more swap has the documented tradeoffs: >=20 > kern.maxswzone > . . . >=20 > Note that swap metadata can be fragmented, which means = that > the system can run out of space before it reaches the > theoretical limit. Therefore, care should be taken to = not > configure more swap than approximately half of the > theoretical maximum. >=20 > (The above is what the warning is about. But then there is . . .) >=20 > Running out of space for swap metadata can leave the = system > in an unrecoverable state. Therefore, you should only > change this parameter if you need to greatly extend the = KVM > reservation for other resources such as the buffer = cache or > kern.ipc.nmbclusters. Modifies kernel option > VM_SWZONE_SIZE_MAX. >=20 > (NOTE: That last paragraph is talking about *decreasing* = kern.maxswzone > to get more room for non-swap-managment things in KVM. [Too bad the > wording says "change".] But increasing kern.maxswzone to allow more = swap > leaves less space for the buffer cache or like, making for tradeoffs > being involved.) FYI: I re-established my access to a RPi2B V1.1 and made it report: "maximum recommended amount (468832 pages)" (The figure can vary some from release to release.) 468832*4096 =3D=3D 1920335872 or a little over 1831 MiBytes For the 4096 Byte pages, that means that the following from gpart fits without complaint (size is in blocks, not pages): 413140992 3686400 da0p2 freebsd-swap (1.8G) 3686400*512 is a little over 1.75 GiByte or 1800 MiByte. So I've left some room below 1831 MiBytes, but not a lot. FYI about my build experiment that is running: # sysctl hw.physmem hw.physmem: 979042304 which, in recent times for armv7, I can (and did) set in /boot/loader.conf on a faster cortex-A7 SBC (that can boot the same media but has more RAM). So I tried a -j4 build, but with LDFLAGS.lld+=3D -Wl,--threads=3D1 in use and my other particular src.conf/make.conf like content (so the builds do likely differ from yours in various ways). My build is producing a non-debug build (but with -g symbols). Somewhat after where your buildworld.log stops, my odd variant of top was reporting: Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) Swap: . . . , 145832Ki MaxObsUsed and top was also showing lots of processes as having "0B" RES in STATE "wait" or "nanslp" (so, apparently swapped out, not paging). ("MaxObs" is short for "maximum observed".) For comparison, your swapscript.log reported a maximum total of 346192 KiBytes "Used" for swap, about 98% into the log file. (Time goes by . . .) It finished with building libllvm and is part way into building libclang. This is probably well past where your hangup happened, given that your published buildworldlog file stopped with libllvm's Target/ARM/ARMMCInstLower.o . My odd top now shows: Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) Swap: . . . , 392328Ki MaxObsUsed The build continues to run. I'll let you know how it goes. >>>> The residue of the top screen shows >>>>=20 >>>> last pid: 63377; load averages: 4.29, 4.18, 4.15 = up 1+07:11:07 04:46:46 >>>> 60 processes: 5 running, 55 sleeping >>>> CPU: 70.7% user, 0.0% nice, 26.5% system, 2.8% interrupt, 0.0% = idle >>>> Mem: 631M Active, 4932K Inact, 92M Laundry, 166M Wired, 98M Buf, = 18M Free >>>> Swap: 2048M Total, 119M Used, 1928M Free, 5% Inuse, 16K In, 3180K = Out >>>> packet_write_wait: Connection to 50.1.20.26 port 22: Broken pipe >>>> bob@raspberrypi:~ $ ssh www.zefox.com RES STATE C TIME = WCPU COMMAND >>>> ssh: connect to host www.zefox.com port 22: Connection timed = out86.17% c++ >>>> bob@raspberrypi:~ $ 1 99 0 277M 231M RUN 0 3:26 = 75.00% c++ >>>> 63245 bob 1 99 0 219M 173M CPU0 0 2:10 = 73.12% c++ >>>> 62690 bob 1 98 0 354M 234M RUN 3 9:42 = 47.06% c++ >>>> 63377 bob 1 30 0 5856K 2808K nanslp 0 0:00 = 3.13% gstat >>>> 38283 bob 1 24 0 5208K 608K wait 2 2:00 = 0.61% sh >>>> 995 bob 1 20 0 6668K 1184K CPU3 3 8:46 = 0.47% top >>>> 990 bob 1 20 0 12M 1060K select 2 0:48 = 0.05% sshd >>>> .... >>>=20 >>> This does not look like ld was in use as of the last top >>> display update's content. But the time between reasonable >>> display updates is fairly long relative to CPU activity >>> so it is only suggestive. >>>=20 >>>> [apologies for typing over the remnants] >>>>=20 >>>> I've put copies of the build and swap logs at >>>>=20 >>>> http://www.zefox.net/~fbsd/rpi2/buildworld/ >>>>=20 >>>> The last vmstat entry (10 second repeat time) reports: >>>> procs memory page disks faults = cpu >>>> r b w avm fre flt re pi po fr sr da0 sd0 in sy = cs us sy id >>>> 4 0 14 969160 91960 685 2 2 1 707 304 0 0 11418 = 692 1273 45 5 50 >>>>=20 >>>> Does that point to the memory exhaustion suggested earlier in the = thread? >>>> At this point /boot/loader.conf contains = vm.pfault_oom_attempts=3D"-1", but=20 >>>> that's a relic of long-ago attempts to use USB flash for root and = swap. >>>> Might removing it stimulate more warning messages? >>>>=20 >>>=20 >>> vm.pfault_oom_attempts=3D"-1" should only be used in contexts where >>> running out of swap will not happen. Otherwise a deadlocked system >>> can result if it does run out of swap. (Run-out has more senses the >>> just the swap partition being fully used: other internal resources >>> for keeping track of the swap can run into its limits.) I've no >>> evidence that the -1 was actually a problem. >>>=20 >>> I do not find any 1000+ ms/w or ms/r figures in swapscript.log . >>> I found 3 examples of a little under 405 (on sdda0*), 3 between >>> 340 and 345 (da0*), 4 in the 200s (da0*), under 60 in the 100s >>> (da0*). It does not look to me like the recorded part had problems >>> with the long latencies that you used to have happen. >>>=20 >>> So I've not found any specific evidence about what led to the >>> hangup. So my earlier questions/suggestions are basically >>> arbitrary and I would not know what to do with any answers >>> to the questions. >>>=20 >>> The only notes that are fairly solid are about the hangup leading >>> to there being some files that were likely incompletely updated >>> (logs, compiler output files, etc.). >>>=20 >>=20 >> The notion that log files might be truncated didn't didn't register=20= >> until you brought it up.=20 >>=20 >> The obvious things to try seem to be: >> Disable vm.pfault_oom_attempts=3D"-1" >> Decrease swap partition size >> Try using WITH_META_MODE >=20 > I'll note that you may well have already spent more time > not getting complete builds than doing one "use less memory" > test would have taken (linker thread count limits, smaller > -jN). To find fairly optimal settings for building on the > RPi2 V1.1, you may have to explore on both sides of the > optimal settings range, just to identify the optimal range > for the settings as being between known bounds. >=20 > Of course, for all I know, the "use less memory" tests might > also fail. If that happened, it would tend to stop spending > time testing configurations even less likely to finish > building. >=20 >> WITH_META_MODE seems relatively easy; just add -DWITH_META_MODE to = the make >> command line for buildworld and add filemon_load=3D"YES" to = boot/loader.conf, >> but I wonder about the burdens it'll impose on CPU and disk = space/throughput.=20 >> There's nothing to lose at this stage, but I'm all ears if there's a = better >> approach. >=20 > You could trade off some I/O by not generating swapscript.log > since it seems to not be of much help for the current issue. >=20 > I'll also note that META_MODE by default does not generate as > much stdout text but stores more across the various .meta files. > So, by default, buildworld.log (by itself) would be much > smaller. (So disabling recording of buildworld.log would not > make much of a difference.) >=20 > I'll remind of the things that are environment-only variables, > including WITH_META_MODE : >=20 > QUOTE > The environment of make(1) for the build can be controlled via the > SRC_ENV_CONF variable, which defaults to /etc/src-env.conf. Some > examples that may only be set in this file are WITH_DIRDEPS_BUILD, = and > WITH_META_MODE, and MAKEOBJDIRPREFIX as they are environment-only > variables. > END QUOTE >=20 > "may only be set in this file" is false relative to setting the > enviromnent on the command line but true compared to the likes > of putting the text in /etc/src.conf or the like. My script for > building for armv7 in a armv7 context looks something like: >=20 > script = ~/sys_typescripts/typescript_make_armv7_nodebug_clang_bootstrap-armv7-host= -$(date +%Y-%m-%d:%H:%M:%S) \ > env __MAKE_CONF=3D"/root/src.configs/make.conf" SRCCONF=3D"/dev/null" = SRC_ENV_CONF=3D"/root/src.configs/src.conf.armv7-clang-bootstrap.armv7-hos= t" \ > WITH_META_MODE=3Dyes \ > MAKEOBJDIRPREFIX=3D"/usr/obj/armv7_clang/arm.armv7" \ > make $* >=20 > (So I happened to not use -DWITH_META_MODE . The context is > /bin/sh based, by the way.) >=20 > There are contexts for which I control UBLR_LOADADDR via > an additional line in the above, such as: >=20 > WORLD_FLAGS=3D"${WORLD_FLAGS} UBLDR_LOADADDR=3D0x42000000" \ >=20 > (But such is old material that I've not validated as > being needed in even remotely modern times.) >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Jan 18 19:21:25 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E9A414F3C4D for ; Mon, 18 Jan 2021 19:21:25 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKM8j2kGhz4s7s for ; Mon, 18 Jan 2021 19:21:25 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-ej1-x62d.google.com with SMTP id ox12so911899ejb.2 for ; Mon, 18 Jan 2021 11:21:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=LvLQlw6tlodnBQSEeU9yt+rpBdRuK421IGsyui5kyzo=; b=hTQyhX/lazGUYdt+2k3xssvg8NkuuG2lXSo148U2vfcd+IT/JgLb7d68gmfFm6sc3T 14tYgJdhP6BJiIz6g5b2CFKW/fIEtW7iLKbrkPj6PojW10N7vTnNUFDZewVb5T4a869A unH57dqbOAF93sep7jdyuKCYaa9tyUKMjaKsxbhN01HHQPRVjHb7mx+woAWDPdpXq3AS JlaBxhzzg/pZT7WJb7MfbEhWAiDbsnN0pWy9+XvP1FqcnY3t4JbSfB3t1++2mQVIYuVX AepMO4AB0+MlsIkNpm/Fhgpoyk8Jo53oZoxeMXXs0Z34XfTWOUnIbF4p6pQ1N0uZ6Bio etWQ== X-Gm-Message-State: AOAM530/LGYsutSk7RKg8t+APmYuhPtge5RftYtHNKEtkFAcw8xeCvOs ahLxr5vtxIYepLGDELrG+PxV8TMiUYDIYQ== X-Google-Smtp-Source: ABdhPJwdz7gYsX7CVSIdQ5b5p9zEU60vAH/iy0clyCvnKD+m4rl39e+pMSuy9S6cQKr3YMosUi7nYg== X-Received: by 2002:a17:906:bc8f:: with SMTP id lv15mr756546ejb.180.1610997683724; Mon, 18 Jan 2021 11:21:23 -0800 (PST) Received: from MacBook-Pro-van-Johan.local (85-147-130-226.cable.dynamic.v4.ziggo.nl. [85.147.130.226]) by smtp.gmail.com with ESMTPSA id pj11sm6962609ejb.58.2021.01.18.11.21.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Jan 2021 11:21:23 -0800 (PST) To: FreeBSD Current From: Johan Hendriks Subject: shutting down jails gives Lost 1 pages of memory error on console. Message-ID: <2ca53760-440e-6390-42f7-2975c14be607@gmail.com> Date: Mon, 18 Jan 2021 20:21:22 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4DKM8j2kGhz4s7s X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.996]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::62d:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::62d:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62d:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 19:21:26 -0000 I have just update my system to FreeBSD srv-01.thuis.local 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #28 main-c256051-g7c7c231c1424: Mon Jan 18 14:12:01 CET 2021 root@srv-01.thuis.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64 Now when i shutdown a jail i see the following appear on the console. Stopping jails: haproxy Freed UMA keg (rtentry) was not empty (1 items). Lost 1 pages of memory. regards, Johan From owner-freebsd-current@freebsd.org Mon Jan 18 19:37:57 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F03AB4F423F for ; Mon, 18 Jan 2021 19:37:57 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10021201.me.com (pv50p00im-ztdg10021201.me.com [17.58.6.45]) (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 4DKMWm6jlbz4t3p for ; Mon, 18 Jan 2021 19:37:56 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10021201.me.com (Postfix) with ESMTPSA id 9FB96A40742; Mon, 18 Jan 2021 19:37:54 +0000 (UTC) From: Toomas Soome Message-Id: Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: boot loader blank screen Date: Mon, 18 Jan 2021 21:37:45 +0200 In-Reply-To: Cc: Johan Hendriks , freebsd Current To: Alan Somers References: <358513ba-699f-8af8-ed4e-a08fd1012db0@codenetworks.net> <103b8db6-09bc-5ff9-d355-4c0f4e759fc2@gmail.com> X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-18_14:2021-01-18, 2021-01-18 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=950 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2006250000 definitions=main-2101180118 X-Rspamd-Queue-Id: 4DKMWm6jlbz4t3p X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[17.58.6.45:from]; DWL_DNSWL_NONE(0.00)[me.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FREEFALL_USER(0.00)[tsoome]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SPAMHAUS_ZRD(0.00)[17.58.6.45:from:127.0.2.255]; RECEIVED_SPAMHAUS_PBL(0.00)[80.235.52.148:received]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[17.58.6.45:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[17.58.6.45:from]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 19:37:58 -0000 > On 18. Jan 2021, at 19:27, Alan Somers wrote: >=20 > On Mon, Jan 18, 2021 at 7:16 AM Johan Hendriks > > wrote: >=20 >>=20 >> On 16/01/2021 21:15, Alan Somers wrote: >>> On Sat, Jan 16, 2021 at 8:39 AM John Kennedy = wrote: >>>=20 >>>> On Fri, Jan 15, 2021 at 03:51:38PM +0200, Toomas Soome wrote: >>>>> Could you please check latest current now?:) >>>> Success! With main-c255999-g0bc776f3da70, I've been able to = comment >> out >>>> the >>>> screen.textmode=3D0 (so, back to the default like I originally = was). >>>>=20 >> I needed to set vbe_max_resolution=3D"800x600" to get the non text = version >> of the boot loader. >>=20 >=20 > Oh, I see. "hw.vga.textmode" got renamed to "screen.textmode". And = it > works both ways now. No need to set vbe_max_resolution. > -Alan That is good. and btw, hw.vga.textmode is still there, it is doing what = it has been done before =E2=80=94 controlling VGA gfx or text mode when = you are starting kernel with text mode. rgds, toomas From owner-freebsd-current@freebsd.org Mon Jan 18 21:03:58 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 610314F557A for ; Mon, 18 Jan 2021 21:03:58 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKPR02sxtz3F8m; Mon, 18 Jan 2021 21:03:54 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id A0555260599; Mon, 18 Jan 2021 22:03:51 +0100 (CET) Subject: Re: bus_dmamem_alloc failed to align memory properly To: Steve Kargl , freebsd-current@freebsd.org, Konstantin Belousov References: <20210118175133.GA49553@troutmask.apl.washington.edu> From: Hans Petter Selasky Message-ID: <6cc7ae53-5898-3802-469b-6b55613519f7@selasky.org> Date: Mon, 18 Jan 2021 22:03:38 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <20210118175133.GA49553@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DKPR02sxtz3F8m X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net:c]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[88.99.82.50:from]; TO_DN_SOME(0.00)[]; SPAMHAUS_ZRD(0.00)[88.99.82.50:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 18 Jan 2021 21:03:58 -0000 On 1/18/21 6:51 PM, Steve Kargl wrote: > I've used a SCHED_BSD for a long time on my i586-*-freebsd > laptop. Recently, FreeBSD just locks up on this system. No > panic. No screen. No keyboard. Nothing. So, yesterday, while > trying to deal with the blank console problem, I switch to > SCHED_ULE to see if solved this lock-up issue. It doesn't. :-( > > I now have a number of messages during boot. > > % dmesg | grep align > bus_dmamem_alloc failed to align memory properly. > bus_dmamem_alloc failed to align memory properly. > bus_dmamem_alloc failed to align memory properly. > bus_dmamem_alloc failed to align memory properly. > bus_dmamem_alloc failed to align memory properly. > > I never seen these messages, so is this normal for SCHED_ULE. > > In addition, to the mystrey lock-up. It now seems that > wpa_supplicant is broken. The initial instances, started > at boot, is using 100% CPU. I need to kill that instance > along with openvpn (which of course needs the network). > The D-Link cardbud ath NIC is ejected, re-insert it, and > the network start up as normal. > Hi, This appears to be a known issue. I think kib@ is working on it. --HPS From owner-freebsd-current@freebsd.org Tue Jan 19 03:19:49 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 490A24E2073 for ; Tue, 19 Jan 2021 03:19:49 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic307-8.consmr.mail.gq1.yahoo.com (sonic307-8.consmr.mail.gq1.yahoo.com [98.137.64.32]) (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 4DKYmh1ChZz4QqP for ; Tue, 19 Jan 2021 03:19:47 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1611026385; bh=yFXLIUsI8eX/uN6ZMXfmpHOdRa+4/k+Twd4V7vESv3u=; h=Subject:From:Date:To:From:Subject:Reply-To; b=jZEvyuzRBiHME1p00S/jAnlWUgELSnHZiqgcrxhqlmyDLw28mLw3pzisWfbjtuhzgBHTpgoRfApzH9EEYfWrpMjnv2Lewx9VFuihI80e/oga/aFpyfVES9vLKw31LfBooYr1gIHEkRyjE/tccE2d4OQTA22DkF2opOjUIiXOcm1i9oQdgbhWW2XTyDt3ZyqIAiJ6j71EzO2UTKEVJqm6X34rv1R8KDVztHAsbYO3DLzKVGAkJc5PodMU8F7vbpFdBo3RFeuN+6F8aQBGNOvRiJhavvnWtjB1go3/ESXxrwsN1xiLFK7+OJdZ7tp4nRwoeo0p2hFizmkGjhWFHZlnOQ== X-YMail-OSG: R8DN1hcVM1mM_dB1GYazaGsv05kQAcPIGspj6HGj8xQ8ZuRGKXNWemLS3HDVy6N N1uQPBvIGUy61IC8R7zolbJfaf_YANGZzTUPEGbKfTeYtqmuePdJisQ0rQtsFEukznRiezdO.Cow SysPt9gjhMCwFLDjT97HlAwtKyX7xLVM0WT6ZewYQ1blICbMVIewdggIDeNU0nhWiPLY_Vul99wf FCs4m252QLB9Xj0z.jAjx6hcjIj94FrvwlHb_yTHRlCpnAXB.M6kmsIQxEiJ.K2stzM8_zn_HPH_ VdHgI97oYfvvWETfjHYUtBaqYYagkOBvtlGxSfXtppbF.tu6S9lzRpcyvQVYyeaXVSZV9cV92c9l 6abd0lPueupYkdvjRdIscUeykTGeRJXKA2pvtu2DAhSmyT_aFf9LLDLhimOnoe5J83dkIMV4vdMH rbS1F.aQdmpHnEMBjyE.oiA1Wezjg3UZpPxjjRgDeiMsDhld6fJYYkmykBfXKzHPE5ABQVuXPVRE CjKScpKyvlK8CSqa71iwrS9TgCvkQGQE5H3EvjsUDHDWDQJY.NgC0PvyoH54OL2aarLw1YurpRMV WrTs65yj.BakKZvX3Slb9l5O2liVD_8G4Ujb7p48yNBKIYFzvZArjwG06K1RsiTDM.AL3Yhv5eDe Jg3MDv7QSTD61dYyDnCHSg5JYTr25T8429gRIDUlug.3uIJfLqu1iK205C0sK61ma_vwcLGRQQhr 3YIB2pxszVQE3Bhnqw4ab1surbTqwjY1cFQAzvtZFO7ttCRiLSDQxVpurTGRBppHhiDnfIcwKtta Z87gqGp9FifGp.KV9Sj4xf_61Lsj0ZGS4HZoQqfVy3_0Y5RBQU.0TQro_VEcYsrrXk65jk8qrmkc _bX1tmpNfZDWGwcjnGIIcwT.Qecz3qznqkVH58FRyYp9Tz3ml.tSrFzoPIwXHvYS4.QqnYerHgB2 hMrXoDlansOwGhWvtnaxeqDylORYdAxKqqNv6S_WPtp..WRVBHwCi7ZrqcvwuZ6mewclJ0KAqFMS _7qVchXUGYdjKJgdnfu9ryq3xqGQwx9nZJQfO4KgapMYxrZH.0WyVWdNT2XvBnwY0loFqaQqKBoI RXtaBne4RVnaBJ6.vpKTjyXCGd2y0ZYNa9gkPMSUIMcxAY2p4xIe8_xsUipuKfHp7ZF4ow9kAg4B z6PD_vdxaUUT3NbYkfZqczLphMAsjCriTcszbc1HTfW_pYgB5kP6u2J4ln64F2mr4r4GwMuAAi2K 0JlnLV2m8q17wJyBJb8Yh33LWr0VBDHQ.ES_wDsreOrO8fHFM9lRMsEnufRZ62kZ4ChruqBAFI6y 5._p6A5Et7pUgReHZ5FLOIu5ryCF1whUBzYrRu6B4ukz2RWK0WJJkDErkiGDilZTBaZQr3s7eRwU oKiYu08A8gPoTQpDme1I.yoOyWK9SCSzSjlJdHtLsDSZhL2o1L_RIuTM_wIAJ61N0WBMCaqZT6uK OimzlGGEWdMpHpd_oJG8g1vrV0zCL5DQ5.bQatj2wHYN0Yiblu9MVMdXlqRo2pfcISAwDZXREAQn iC8g_ssfViFRgVTvvyqRj.oCp7mMPIwMG6fADvTxmNJj8Sx0_BIv7f0gTl1zInxMjvyejfEvuROG _y4BoIh3aSiJA61fR6T5Y7nbNUXIls8ih4pUb19c15nyDBfcVcsaISs_AJIKmA4nxo2bOTkNv6wl XQj_47OVzUJRpbaJQ5UbRT_f41q6v4_.oHHXLaf2ZoqjKRaAOgz3LtKYVdmC2SIC2nFzlAbPg4Cm mm8E7LBGBUt3a.WtRlepK9InC.Xa2M9C9TRMn273IK7qz9iuHp8WnYOnhdQa96dCs_SiamGhA7.3 BJruE8qegx.lOypSnm32V0mUqJueNK7yeF5G3pgbO9lXbN3vohefToZr5BJkSIfMYXXZI6Z3J1GC Ei0SAZ2aPxlGsA1SjjnlYhdHdKBqBNPSGEsEUnq6ed1j.wfQ5R9tYvdL6LdGxK_kGjK1iENlpPGp c4w6DrbbX.4wt3lyAP8Sgcm06X4v1OFCywk1DCrkn3vnm47hjMZqFwBZc8HCinuFopJ_IUqG6qM. shAs5gNLmOBdyRN3qmMGsQSWFW6rm0yjB6gK4jTbkqZ.WMVw57wIMxuQ9XBE7W60hIWnjcpWSm8F OAdEFORIVLaEEQASVlE1pzqBjLJ7TG4bkC3XF1tNog5v13pv0rZ42cXTrLbhPHOlfDbSIkx6Cap2 jB5m_vhDeAKWMXcGvSQhogMvB.gtDonql3QI2ERRgwgemDK3u9iHPNnBhUNyb6xYv4AmLoze0PTN cveYi2XKh0001putGTyxLZeGi_pCqy3D6oJbuUX_QBzMr38K3wS.PVlS4Z9_38Mrg.t20g7wMGMG 4PhoAw9FdBFcBy3szmGnBTxvL0dSxoTtdyrHWd.cv5A5exZ4Qxs_NltzOPr57XxSQXqzdASe.iGu lyS0vT5Js7zquvMnGHfbreHW0Nnf1tDBeflont_W0EvgagSxEpd5CTL5vSLto4KzAVfs3hGwV5gp kqbwJcGXHQYJt92yLqSI6GzhxY9b0uOaA6F6G8wGDaLOtz6IGw3_V.yRZ6LBffKLBTYzBGY_uoTl lWcvq.lB8dSlsMToiFB.pjWNkshyYkvB8N1WqT4hZXng.zpUIxwHMjO.E.FM- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.gq1.yahoo.com with HTTP; Tue, 19 Jan 2021 03:19:45 +0000 Received: by smtp423.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 026f41280f733af56340d295a8697653; Tue, 19 Jan 2021 03:19:41 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld From: Mark Millard In-Reply-To: Date: Mon, 18 Jan 2021 19:19:40 -0800 Cc: Current FreeBSD , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <00104FAD-E32B-4DDE-80DD-FCEF14CEC06B@yahoo.com> References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> <20210118015009.GA31353@www.zefox.net> <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DKYmh1ChZz4QqP X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.64.32:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.64.32:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.32:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.32:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 03:19:49 -0000 > . . . > FYI: I re-established my access to a RPi2B V1.1 and made > it report: "maximum recommended amount (468832 pages)" >=20 > (The figure can vary some from release to release.) >=20 > 468832*4096 =3D=3D 1920335872 or a little over 1831 MiBytes >=20 > For the 4096 Byte pages, that means that the following from > gpart fits without complaint (size is in blocks, not pages): >=20 > 413140992 3686400 da0p2 freebsd-swap (1.8G) >=20 > 3686400*512 is a little over 1.75 GiByte or 1800 MiByte. So > I've left some room below 1831 MiBytes, but not a lot. >=20 > FYI about my build experiment that is running: >=20 > # sysctl hw.physmem > hw.physmem: 979042304 >=20 > which, in recent times for armv7, I can (and did) set in > /boot/loader.conf on a faster cortex-A7 SBC (that can boot > the same media but has more RAM). >=20 > So I tried a -j4 build, but with LDFLAGS.lld+=3D -Wl,--threads=3D1 > in use and my other particular src.conf/make.conf like content > (so the builds do likely differ from yours in various ways). > My build is producing a non-debug build (but with -g symbols). > Somewhat after where your buildworld.log stops, my odd variant > of top was reporting: >=20 > Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) > Swap: . . . , 145832Ki MaxObsUsed >=20 > and top was also showing lots of processes as having "0B" RES > in STATE "wait" or "nanslp" (so, apparently swapped out, not paging). > ("MaxObs" is short for "maximum observed".) >=20 > For comparison, your swapscript.log reported a maximum total of > 346192 KiBytes "Used" for swap, about 98% into the log file. >=20 > (Time goes by . . .) >=20 > It finished with building libllvm and is part way into building > libclang. This is probably well past where your hangup happened, > given that your published buildworldlog file stopped with > libllvm's Target/ARM/ARMMCInstLower.o . My odd top now shows: >=20 > Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) > Swap: . . . , 392328Ki MaxObsUsed >=20 > The build continues to run. I'll let you know how it goes. > . . . Just after libclang finished my odd top showed: Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892736Ki = MaxObs(Act+Wir) Swap: . . . , 537588Ki MaxObsUsed After liblldb: Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 899276Ki = MaxObs(Act+Wir) Swap: . . . , 537588Ki MaxObsUsed Much later, after the lldb program had been built: Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki = MaxObs(Act+Wir) Swap: . . . , 537588Ki MaxObsUsed >>> World build completed on Mon Jan 18 19:10:08 PST 2021 >>> World built in 72960 seconds, ncpu: 4, make -j4 This was building from scratch what was already installed: # ~/fbsd-based-on-what-freebsd-main.sh=20 merge-base: 818390ce0ca539300dd15d7a817784f1e3f7a9b8 merge-base: CommitDate: 2021-01-13 21:27:44 +0000 4180404713ec (HEAD -> mm-src) mm-src snapshot for mm's patched build in = git context. 818390ce0ca5 (freebsd/main, freebsd/HEAD, pure-src, main) arm64: fix = early devmap assertion FreeBSD OPiP2E_RPi2v11 13.0-CURRENT FreeBSD 13.0-CURRENT = mm-src-c255938-g4180404713ec GENERIC-NODBG arm armv7 1300135 1300135 This suggests that you should be able to build on the RPi2B v1.1, using -j4, with appropriate configuration for what and how to build. It is now building the matching kernel, my GENERIC-NODBG style. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Tue Jan 19 05:13:01 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 087A94E609C for ; Tue, 19 Jan 2021 05:13:00 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-22.consmr.mail.gq1.yahoo.com (sonic317-22.consmr.mail.gq1.yahoo.com [98.137.66.148]) (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 4DKcH668rqz4bHb for ; Tue, 19 Jan 2021 05:12:49 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1611033166; bh=71ym+CwJ0Xy40YBornWgs7rKnILinxCHGxAk9dmVSS0=; h=Subject:From:Date:To:From:Subject:Reply-To; b=JVqa21Jzd9QbU6tFQXfCsdXR0LSLVsavr5d8EQH8QiWfrORCUqfoyZZLrVytrF+RS1g5toSDY/aWJOAZVGU6Mzl9UIpdy4m1a52Zaz3FXcuPKNcVi88cMKQFRaSzofo34vaND+fjXNMS1fYLHNjCJieA4XuaTCpirrbHZzcZoY9Pf4aAoZw2LmqcrgsNusCcUDh19e1sWlKvd7IPPh2hF5rWlFVC/suVG2xIMay4Lzay2b8jrKsv7OB3UPCCsyLBxICidrqE5a0QIys6iE0Lb8DS8TIlJTioib12U5+esHM7fDwGKZbYgGIu37tKNrG8JEPYBd38OOAlVDXXJvPgDg== X-YMail-OSG: D2TtJqkVM1nlN8VttsSHAnzth5gh_0QgFXmTgf24MUVTINFIA0rzvIEoMIYJwEp LlRLeUfLbJ8Zke9TJ0KwJg4d5CgkNyBejvfyazV4rmXeU9zuxjA7U_svDS1Z_s2jMx.3uaFWw2he qMEZzyvLgTdx.augUm6Vws5Rhws3D5COeqdWtGtuJmMLlyryP6T.AeKBIPD1orBzz0vCuPzT.C__ 0bcA820XOif3HE.TwtyUduHVxQfgHNZabhwcn5zxsj7zvk4Od4gDHVo8t28C2NPrS8_eazHY643W Mu6GHDQ5VQsU7qlbgoemLwQuJU871En1IAXXeSWbFLMPeWMBDBVr1aM8.XgDGLY.B_rNWHNIRCPF RgT5AFmUyYmUvXe8XG3kyn_xj7aXJ8_1qnHkFGy5.d8VbQZ_JOv1MhB9OTzxOUX0dG_UtxJwN_zD EOnz0Qhi17GPsOLp7Kx1j299cIzQAREr9awim9.LLy_fATps7R1UbadQ3HTA6g9IadCoT.aVq7VD yOeupIWzB2ru0TWeHON.AkqxqkzhaTJ69Q2KjZKLekdJHrWH.QZHuVYmv3NzZIbYzZMtaumpNZ00 G.p6bqLY6TKyzJ2UrctvBoWDVmnEJcZAmVKKd4li5pLeBXHPzNe3wXzlcUXbtO9xksJUyEJLdr_4 i42h3W.Ws8ZhB9xNi5gsS6DmM8L0ko12ECZGONi5cL3IYvyMG4IwxBiPMLyE9zytYolcQRB24Z6G LRPjQ_Ox5mD7s3z499X6ayE21HAYpblTA3gx3jo9XhPtn1VeFV1igMgHaeACZk0kc6mDRQ8XeAB9 6gHkuzvNgWtnqxQwClkXofFoLlnI09Upm0xyiBqPRDWVstC1ba5OvyY.goDP5KP4qNlTrI66HoA6 3bpOOPPaLtvIUGbaU.AdezSNjIMLUm9l1qZlHC3Jwt5IucUzLLE9Pt1R.DfT7Tm6fwKyEiKD6Vgx .x3j530iuta1xYvDPlf6gO_79s1b.897V1o3udOjB97w2ABRq3zqUY6pqHjl3c.JV4_SLacPfcaA QjI5JO9B7wbdJfzdqk._CvAONCOO_1__ZzlsFslrw_CJlUHjwV4rTbnorjR_JkADnRC_P34SzFyq QiIRPPE0HFZwhWeoWx90XeHCZwCUktkfNlKn.aGMEPdermngEshx5V3yLy.2AuH0HhnkAreHqVxk OA1awWuzaVc24ibs_zlEcaqoGuyQENpSEYES1.jzyNi6rMai09rOVDnFYOUBJos82HPQCMMy9rSu hxtHMgWJ.GOuuJDelu9SlI7if.ZGGzx3.g0214mtyKZt0z7aC5cGly2EI9LPwAeFGh62UolIdLzi u3tnJTgTkTkKdGX7.WoCVp_dilLr4FngSQ43xijeQtsx6Fwh6axGJ15rokItD1InrbpK_DYBFAmK LEW2YlO10zeTA83wsvToHw0_0T0E7ffZWSGiiEmYTdyx6QT6.Gl1Z9.2u3AdxtRzDq.TbhQ7LghT efl0yPaQvDJfh6C07lDLKyFcMap7t.OAOoC3OrwLV0jWZpev90a4DDaPwYTgzlf0eQTlhDG1PDwH ajPZLET2EjefzfIfO5BfdIglqZu9E9yzqTHV_IJN8Al7xg0bn54Nzcea6LJMfXr2g.KhifkCZorP O04BQeykGwVz2x0hFqEiOuaHaLplMMg4mgSQzbqaYKJiio4HLVUMyHJiuELNn4QjT.2EEL76_qPc SEhAsYwUlGYwj3xwACqCj5oRzFoHI77EU5rSZw24KNSPhh1rybG.E41K6T9wpM14RHTQtirA2MwR yVToWh1BFvSo.5q1y_nmZZZpK1V5EgGCl1tSd5yr3.JFOAcye9oZzVLIUvFnfD.Gqu35F._tA8wg 72rginYleNKuxIwTFAgOJ9NEOwkW0OLIQ.Uteu7XkJWtEj7Nd9OHPc9a0b9VcgPJhU7yRbAdM93y DNIe75ZCOKqElA2vf4EV4lHNVJe7fhYKTHASKJig6hKW5rdSijOE8a9HFn._Gqlb0.99WKP18UYf Xy8BZTmB7U4WpLuP91Z1y4ZzCA7X8fbpIp2foQtIHnyef0W_zBhRP9PZ2MKV1al77fPfxlmfBwUj LFD.AKilwKtZJDjdqF5r7LSbTWZtmMN3GRcPGWvG3Vpr.Px5_ooIXpubPKdwvBsHzEpIhB1rAXmO XHLNLjRKdUmCTtqFSl1cj0nGuuZXBBQ.Znf04ykzIrcgsjeZNbOXEC5FsSpvveOuNkRBhWJWI7oV TBg3JiOT9pWBpoDRP35rVnthzCfr1dwbhOrnQWRb3Y6BdoaJjhn5Ky8ZuIb78I1CUxVXrhOfb5K7 v74RX.qVZsJB_717JWIzaVAIn7eJkg3mpWqHDJjov1hYASA91XGd9cDAPQhHRfde2Y9cGgwmkLHb lsA5cwkUkEX_yK6qoi8NFHheZu2PZXq4auNbykkVOf8qOfzx1l3YbDfKKMUVxb.2kCdaF8qKShDY xweqaoSVa_ZzQAGJpKHYaOE9nHh1X_MMJrISWYdbP9_rcMURGAr0eAl.EF6OPm7LU3sSBkSslE.o Fag1PgcA93TcqZ59mkXv.1iMm3a2Ktlngkr.31s3Pi3qzGKfJ0XMfVEXL2gKdMQ1i7sw67Tlmkvi 3UtG0 Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Tue, 19 Jan 2021 05:12:46 +0000 Received: by smtp416.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 72328f8d3653c35cee212499c9c77b5e; Tue, 19 Jan 2021 05:12:44 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld From: Mark Millard In-Reply-To: <00104FAD-E32B-4DDE-80DD-FCEF14CEC06B@yahoo.com> Date: Mon, 18 Jan 2021 21:12:43 -0800 Cc: Current FreeBSD , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> <20210118015009.GA31353@www.zefox.net> <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> <00104FAD-E32B-4DDE-80DD-FCEF14CEC06B@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DKcH668rqz4bHb X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.66.148:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.66.148:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.66.148:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.66.148:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 05:13:01 -0000 On 2021-Jan-18, at 19:19, Mark Millard wrote: > . . . >> FYI: I re-established my access to a RPi2B V1.1 and made >> it report: "maximum recommended amount (468832 pages)" >>=20 >> (The figure can vary some from release to release.) >>=20 >> 468832*4096 =3D=3D 1920335872 or a little over 1831 MiBytes >>=20 >> For the 4096 Byte pages, that means that the following from >> gpart fits without complaint (size is in blocks, not pages): >>=20 >> 413140992 3686400 da0p2 freebsd-swap (1.8G) >>=20 >> 3686400*512 is a little over 1.75 GiByte or 1800 MiByte. So >> I've left some room below 1831 MiBytes, but not a lot. >>=20 >> FYI about my build experiment that is running: >>=20 >> # sysctl hw.physmem >> hw.physmem: 979042304 >>=20 >> which, in recent times for armv7, I can (and did) set in >> /boot/loader.conf on a faster cortex-A7 SBC (that can boot >> the same media but has more RAM). >>=20 >> So I tried a -j4 build, but with LDFLAGS.lld+=3D -Wl,--threads=3D1 >> in use and my other particular src.conf/make.conf like content >> (so the builds do likely differ from yours in various ways). >> My build is producing a non-debug build (but with -g symbols). >> Somewhat after where your buildworld.log stops, my odd variant >> of top was reporting: >>=20 >> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) >> Swap: . . . , 145832Ki MaxObsUsed >>=20 >> and top was also showing lots of processes as having "0B" RES >> in STATE "wait" or "nanslp" (so, apparently swapped out, not paging). >> ("MaxObs" is short for "maximum observed".) >>=20 >> For comparison, your swapscript.log reported a maximum total of >> 346192 KiBytes "Used" for swap, about 98% into the log file. >>=20 >> (Time goes by . . .) >>=20 >> It finished with building libllvm and is part way into building >> libclang. This is probably well past where your hangup happened, >> given that your published buildworldlog file stopped with >> libllvm's Target/ARM/ARMMCInstLower.o . My odd top now shows: >>=20 >> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) >> Swap: . . . , 392328Ki MaxObsUsed >>=20 >> The build continues to run. I'll let you know how it goes. >> . . . >=20 > Just after libclang finished my odd top showed: >=20 > Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892736Ki = MaxObs(Act+Wir) > Swap: . . . , 537588Ki MaxObsUsed >=20 > After liblldb: >=20 > Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 899276Ki = MaxObs(Act+Wir) > Swap: . . . , 537588Ki MaxObsUsed >=20 > Much later, after the lldb program had been built: >=20 > Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki = MaxObs(Act+Wir) > Swap: . . . , 537588Ki MaxObsUsed >=20 >>>> World build completed on Mon Jan 18 19:10:08 PST 2021 >>>> World built in 72960 seconds, ncpu: 4, make -j4 >=20 > This was building from scratch what was already installed: >=20 > # ~/fbsd-based-on-what-freebsd-main.sh=20 > merge-base: 818390ce0ca539300dd15d7a817784f1e3f7a9b8 > merge-base: CommitDate: 2021-01-13 21:27:44 +0000 > 4180404713ec (HEAD -> mm-src) mm-src snapshot for mm's patched build = in git context. > 818390ce0ca5 (freebsd/main, freebsd/HEAD, pure-src, main) arm64: fix = early devmap assertion > FreeBSD OPiP2E_RPi2v11 13.0-CURRENT FreeBSD 13.0-CURRENT = mm-src-c255938-g4180404713ec GENERIC-NODBG arm armv7 1300135 1300135 >=20 > This suggests that you should be able to build on the RPi2B v1.1, > using -j4, with appropriate configuration for what and how to build. >=20 >=20 > It is now building the matching kernel, my GENERIC-NODBG style. Done: >>> Kernel build for GENERIC-NODBG completed on Mon Jan 18 20:33:26 PST = 2021 >>> Kernel(s) GENERIC-NODBG built in 4998 seconds, ncpu: 4, make -j4 So, World+Kernel in somewhat under 22 hours. The "MaxObs*" figures were unchanged, so: Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki = MaxObs(Act+Wir) Swap: . . . , 537588Ki MaxObsUsed This suggests that, for now, 800 MiByte of swap would be something more than 1.5 times what it actually used and 1050 MiBytes would be something like 2.0 times what it actually used, so leaving some notable margin for variations in peek usage, at least when linker threading is avoided. As for what I used to control "what and how to build" . . . # more = ~/sys_build_scripts.armv7-host/make_armv7_nodebug_clang_bootstrap-armv7-ho= st.sh=20 kldload -n filemon && \ script = ~/sys_typescripts/typescript_make_armv7_nodebug_clang_bootstrap-armv7-host= -$(date +%Y-%m-%d:%H:%M:%S) \ env __MAKE_CONF=3D"/root/src.configs/make.conf" SRCCONF=3D"/dev/null" = SRC_ENV_CONF=3D"/root/src.configs/src.conf.armv7-clang-bootstrap.armv7-hos= t" \ WITH_META_MODE=3Dyes \ WORLD_FLAGS=3D"${WORLD_FLAGS} UBLDR_LOADADDR=3D0x42000000" \ MAKEOBJDIRPREFIX=3D"/usr/obj/armv7_clang/arm.armv7" \ make $* (In my context, UBLDR_LOADADDR is ignored by anything that can not use the figure given. So I've no bothered to be more selective about having it in the armv7 builds.) # more ~/src.configs/make.conf LDFLAGS.lld+=3D -Wl,--threads=3D1 # more ~/src.configs/src.conf.armv7-clang-bootstrap.armv7-host TO_TYPE=3Darmv7 # KERNCONF=3DGENERIC-NODBG TARGET=3Darm .if ${.MAKE.LEVEL} =3D=3D 0 TARGET_ARCH=3D${TO_TYPE} .export TARGET_ARCH .endif # #WITH_CROSS_COMPILER=3D WITH_SYSTEM_COMPILER=3D WITH_SYSTEM_LINKER=3D # WITH_LIBCPLUSPLUS=3D WITHOUT_BINUTILS_BOOTSTRAP=3D WITH_ELFTOOLCHAIN_BOOTSTRAP=3D #Disables avoiding bootstrap: WITHOUT_LLVM_TARGET_ALL=3D WITHOUT_LLVM_TARGET_AARCH64=3D WITH_LLVM_TARGET_ARM=3D WITHOUT_LLVM_TARGET_MIPS=3D WITHOUT_LLVM_TARGET_POWERPC=3D WITHOUT_LLVM_TARGET_RISCV=3D WITHOUT_LLVM_TARGET_X86=3D WITH_CLANG=3D WITH_CLANG_IS_CC=3D WITH_CLANG_FULL=3D WITH_CLANG_EXTRAS=3D WITH_LLD=3D WITH_LLD_IS_LD=3D WITHOUT_BINUTILS=3D # WITH_LLDB=3D # WITH_BOOT=3D WITHOUT_LIB32=3D # # WITHOUT_WERROR=3D #WERROR=3D MALLOC_PRODUCTION=3D WITH_MALLOC_PRODUCTION=3D WITHOUT_ASSERT_DEBUG=3D WITHOUT_LLVM_ASSERTIONS=3D # # Avoid stripping but do not control host -g status as well: DEBUG_FLAGS+=3D # WITH_REPRODUCIBLE_BUILD=3D WITH_DEBUG_FILES=3D # # Use of the .clang 's here avoids # interfering with other CFLAGS # usage, such as ?=3D usage. CFLAGS.clang+=3D -mcpu=3Dcortex-a7 CXXFLAGS.clang+=3D -mcpu=3Dcortex-a7 CPPFLAGS.clang+=3D -mcpu=3Dcortex-a7 (I do not claim that you would want WITH_REPRODUCIBLE_BUILD . I just happen to have been experimenting with it. You might not want to be explicit about the cpu to target. You might not want WITH_CLANG_EXTRAS .) # more /usr/fbsd/mm-src/sys/arm/conf/GENERIC-NODBG include "GENERIC" ident GENERIC-NODBG makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols options AUDIT # Not enabled by default in = armv7/v6 kernels # Enabled here to allow kyua = test runs to # possibly report auditing = works. options ALT_BREAK_TO_DEBUGGER options KDB # Enable kernel debugger support # For minimum debugger support (stable branch) use: options KDB_TRACE # Print a stack trace for a = panic options DDB # Enable the kernel debugger # Extra stuff: #options VERBOSE_SYSINIT=3D0 # Enable verbose sysinit = messages #options BOOTVERBOSE=3D1 #options BOOTHOWTO=3DRB_VERBOSE options ALT_BREAK_TO_DEBUGGER # Enter debugger on keyboard = escape sequence options KLD_DEBUG #options KTR #options KTR_MASK=3DKTR_TRAP ##options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # Disable any extra checking for. . . nooptions INVARIANTS # Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks = for speed nooptions DEADLKRES # Enable the deadlock resolver nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones nooptions DIAGNOSTIC nooptions BUF_TRACKING nooptions FULL_BUF_TRACKING nooptions USB_DEBUG nooptions USB_REQ_DEBUG nooptions USB_VERBOSE The /boot/loader.conf file and the /etc/sysctl.conf files both contained: vm.pageout_oom_seq=3D120 vm.pfault_oom_attempts=3D-1 (The hw.physmem=3D979042304 in /boot/loader.conf was very-special, to better approximate your environment. I also controlled the cpu frequency used via a line in /etc/sysctl.conf . I do not bother with such non-default frequency usage [or related settings] for RPi*'s with the pre-RPi4B style power connections but do control the frequency for the OPi+2E.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Tue Jan 19 11:45:31 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9C61D4F0FB8 for ; Tue, 19 Jan 2021 11:45:31 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out2.migadu.com (out2.migadu.com [188.165.223.204]) (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 4DKn0B4z8Mz3JVg for ; Tue, 19 Jan 2021 11:45:30 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Tue, 19 Jan 2021 14:45:14 +0300 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Greg V Subject: Re: Name of touchpad changed in latest rev To: Malcolm Matalka Cc: FreeBSD Current Message-Id: In-Reply-To: <86czy2n2yk.fsf@gmail.com> References: <86czy2n2yk.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: greg@unrelenting.technology X-Rspamd-Queue-Id: 4DKn0B4z8Mz3JVg X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:188.165.223.204]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[188.165.223.204:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[188.165.223.204:from]; ASN(0.00)[asn:16276, ipnet:188.165.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 11:45:31 -0000 On Mon, Jan 18, 2021 at 08:01, Malcolm Matalka wrote: > I just installed the below revision, and looks like the name the mouse > shows up as has changed. Not sure if this is intended or not. What > was > "SynPS/2 Synaptics TouchPad" and now it is "DELL07E6:00 06CB:76AF > TouchPad". Congratulations, you are now using the touchpad over I2C instead of PS/2 :) The iichid code has finally landed in current so we have much better HID support now. From owner-freebsd-current@freebsd.org Tue Jan 19 12:44:22 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AFAE24F32A0 for ; Tue, 19 Jan 2021 12:44:22 +0000 (UTC) (envelope-from SRS0=hAtcM2=GW=codenetworks.net=sm@eigbox.net) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DKpJ63LYBz3P7D for ; Tue, 19 Jan 2021 12:44:22 +0000 (UTC) (envelope-from SRS0=hAtcM2=GW=codenetworks.net=sm@eigbox.net) Received: by mailman.nyi.freebsd.org (Postfix) id 72CA74F33E2; Tue, 19 Jan 2021 12:44:22 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 729234F321E for ; Tue, 19 Jan 2021 12:44:22 +0000 (UTC) (envelope-from SRS0=hAtcM2=GW=codenetworks.net=sm@eigbox.net) Received: from bosmailout07.eigbox.net (bosmailout07.eigbox.net [66.96.184.7]) (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 4DKpJ55BxMz3PRY for ; Tue, 19 Jan 2021 12:44:21 +0000 (UTC) (envelope-from SRS0=hAtcM2=GW=codenetworks.net=sm@eigbox.net) Received: from bosmailscan01.eigbox.net ([10.20.15.1]) by bosmailout07.eigbox.net with esmtp (Exim) id 1l1qMu-0000YK-O6 for current@freebsd.org; Tue, 19 Jan 2021 07:44:20 -0500 Received: from [10.115.3.33] (helo=bosimpout13) by bosmailscan01.eigbox.net with esmtp (Exim) id 1l1qMu-0002oK-Ex for current@freebsd.org; Tue, 19 Jan 2021 07:44:20 -0500 Received: from bosauthsmtp07.yourhostingaccount.com ([10.20.18.7]) by bosimpout13 with id JckH2400B099BUA01ckL8A; Tue, 19 Jan 2021 07:44:20 -0500 X-Authority-Analysis: v=2.3 cv=Ep1JURUA c=1 sm=1 tr=0 a=x8qw8EAkfcRkIpZA8Q87Bg==:117 a=BXB5eCltbCg0Q+nSw1Bwcw==:17 a=EmqxpYm9HcoA:10 a=jXMol9EDn2QA:10 a=13zjGPudsaEWiJwPRgMA:9 a=Xg5zmNnJsfgq4W8_pxIA:9 a=QEXdDO2ut3YA:10 a=-L-VojeSQvdfXmou6_gA:9 a=FfaGCDsud1wA:10 Received: from cm-81-9-160-236.telecable.es ([81.9.160.236]:59019 helo=[192.168.1.100]) by bosauthsmtp07.eigbox.net with esmtpa (Exim) id 1l1qMr-0008Ps-5u for current@freebsd.org; Tue, 19 Jan 2021 07:44:17 -0500 To: FreeBSD Current From: Santiago Martinez Subject: VM UMA counters. Message-ID: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> Date: Tue, 19 Jan 2021 12:44:14 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2dMJMI37oicQhT4VuPjHKZdYKspwCrfjR" X-EN-UserInfo: d3bdfab0736480cedf04ed92aaea2ef5:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: sm@codenetworks.net Sender: Santiago Martinez X-EN-OrigIP: 81.9.160.236 X-EN-OrigHost: cm-81-9-160-236.telecable.es X-Rspamd-Queue-Id: 4DKpJ55BxMz3PRY X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.96.128.0/18]; HAS_ATTACHMENT(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[codenetworks.net:~]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FORGED_SENDER(0.30)[sm@codenetworks.net,SRS0=hAtcM2=GW=codenetworks.net=sm@eigbox.net]; RECEIVED_SPAMHAUS_PBL(0.00)[81.9.160.236:received]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[66.96.184.7:from]; ASN(0.00)[asn:29873, ipnet:66.96.128.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[sm@codenetworks.net,SRS0=hAtcM2=GW=codenetworks.net=sm@eigbox.net]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; DMARC_NA(0.00)[codenetworks.net: no valid DMARC record]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[66.96.184.7:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[66.96.184.7:from]; R_DKIM_PERMFAIL(0.00)[codenetworks.net:s=dkim]; MAILMAN_DEST(0.00)[current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 12:44:22 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2dMJMI37oicQhT4VuPjHKZdYKspwCrfjR Content-Type: multipart/mixed; boundary="nzXVNn16ybysMA07zg4Iks7cIzRUDB6hZ"; protected-headers="v1" From: Santiago Martinez To: FreeBSD Current Message-ID: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> Subject: VM UMA counters. --nzXVNn16ybysMA07zg4Iks7cIzRUDB6hZ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hi there, sorry to ask this as it might be a silly question... Since a few weeks im seeing random locks on application and sometimes when using truss it show resource temporally unavailable. Now, checking random things, i see that the vm.uma.256_Bucket.stats.fails counter is increasing while the other are not (at least for now). Here goes the output: vm.uma.256_Bucket.stats.xdomain: 0 vm.uma.256_Bucket.stats.fails: 762142 vm.uma.256_Bucket.stats.frees: 41935 vm.uma.256_Bucket.stats.allocs: 42721 vm.uma.256_Bucket.stats.current: 786 root@tucho:/home/smartinez # uname -a FreeBSD tucho 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #13 main-c256107-g7d3310c4fcdd: Tue Jan 19 10:50:12 GMT 2021=C2=A0=C2=A0=C2=A0= =C2=A0 smartinez@tucho:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG=C2=A0 am= d64 My question is, is this the expected behavior? Regards. Santi --nzXVNn16ybysMA07zg4Iks7cIzRUDB6hZ-- --2dMJMI37oicQhT4VuPjHKZdYKspwCrfjR Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEk06QWJzNAs9NTrFjWBFqYkyC55EFAmAG1B4FAwAAAAAACgkQWBFqYkyC55GY BhAAh/pd5+Xu4CnpEYquNC8D1J68VajKmRquplSN20PFIEzueySPyEdwvR+lcexkL+r4eDyz3IlD V/jN/ptNIMYk3okL9H3dBDSf/9TH99hsZ1nK3+m3dWURNt/2XgUiGtjR+cLyMDfz8r/t68fgkCSy 7wtipXJDc4d79Xa7qCsxHwnHDCYyCQyMK7xHvzq9CoJN6sBxblMzR9Zc+rxi8DJXB+B1x51GuLnb VT6DxPQgykDdZnhTyo6IOB/+Gn8KGNQX+OpjvE1okEDqC+6/IhIt6qZZwUkCd7uGfqrHs1iSoINq bRUcoq5waz3/394MJhR5e1P1dpByt1UtcTt5z3qPcXRq5b1UTrpWxll3KJDidWsypbX18Q6C8TFI YbcmfDkMl1oLadAlwOFFzA0xaJzM4HROwgzjGwfHITWV0vGgt/2FMczgKyv87KR5cMhZDxCvPvWJ vVH/kQVx3DhsmRZ3kzUwVcOy7EiR5MGMWw+3Xh0/hXGNt1Y/bh2jZ8rpKLVQ1fc8NGq03DYY0bgh QPM0fFfmYbXPxemEbhL9a81V1AkGslTS8V+kiP3iFTvCGmaJ6K3/xzVeAsm2aylqMcn5f9sPXHwe ZRHphHpuLt2YN3bjmBVhmFn0Sb8pyCUm/MCQ4Sjfkh0cb3+iGLq7sBMcsTu6hhZLsX1FqHMbKHsb uQ4= =HYwh -----END PGP SIGNATURE----- --2dMJMI37oicQhT4VuPjHKZdYKspwCrfjR-- From owner-freebsd-current@freebsd.org Tue Jan 19 12:53:24 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 869484F3539 for ; Tue, 19 Jan 2021 12:53:24 +0000 (UTC) (envelope-from contact@evilham.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DKpVX2VZnz3Pll for ; Tue, 19 Jan 2021 12:53:24 +0000 (UTC) (envelope-from contact@evilham.com) Received: by mailman.nyi.freebsd.org (Postfix) id 55CC94F34C7; Tue, 19 Jan 2021 12:53:24 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 558FD4F35A5 for ; Tue, 19 Jan 2021 12:53:24 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [IPv6:2a02:2770::216:3eff:fee1:cf9]) (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 4DKpVW29x3z3Pp0 for ; Tue, 19 Jan 2021 12:53:22 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (localhost [IPv6:::1]) by yggdrasil.evilham.com (Postfix) with ESMTP id 4DKpVL1gKDzCvW; Tue, 19 Jan 2021 13:53:14 +0100 (CET) Received: from yggdrasil.evilham.com (unknown [IPv6:2a0a:e5c1:121:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 4DKpVK6bDnzCvV; Tue, 19 Jan 2021 13:53:13 +0100 (CET) From: Evilham To: current@freebsd.org Cc: Robert Huff , Hans Petter Selasky Subject: Re: Current kernel build broken with linuxkpi? References: <3c0d77d7-6b99-d48e-6e8a-92134b2fac7e@selasky.org> <24575.20352.153922.53339@jerusalem.litteratus.org> In-reply-to: Date: Tue, 19 Jan 2021 13:53:12 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 4DKpVW29x3z3Pp0 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a02:2770::216:3eff:fee1:cf9:from]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_DKIM_REJECT(0.00)[evilham.com:s=mail]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[2a02:2770::216:3eff:fee1:cf9:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[evilham.com:-]; DMARC_POLICY_ALLOW(0.00)[evilham.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:196752, ipnet:2a02:2770::/32, country:NL]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 12:53:24 -0000 On dc., gen. 13 2021, David Wolfskill wrote: > On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote: >> >> Hans Petter Selasky : >> >> > You need to update that DRM port you are using before the >> > issue >> > will be fixed. >> >> I'm confused. >> I have drm-current-kmod listed in PORTS_MODULES; things on >> that >> list get built _after_ buildkernel (installkernel??) for >> reasons I >> thought I understood. >> You are telling me I need to update this _before_ buildkernel? >> >> >> Perplexedly, >> .... > > He telling you to update the port itself -- e.g., > /usr/ports/graphics/drm-kmod, as the port was recently updated: > > ------------------------------------------------------------------------ > r561457 | manu | 2021-01-13 03:22:25 -0800 (Wed, 13 Jan 2021) | > 6 lines > > graphics/drm-{current,devel}-kmod: Update to latest source > > This fix a compilation problem with a pre 1300135 source tree. > > Reported by: Filippo Moretti > > > So you need to update the "ports files" to get that update, then > rebuild > the port (in concert with rebuilding the kernel, as you are > doing). > > Peace, > david Just as a curiosity because I was hit by this and the thread was helpful: I was unable to build the kernel with an up to date drm-current-kmod, but as soon as I switched to drm-devel-kmod, I was able to. The running kernel was uname -K: 1300133. Thanks everyone for having added their input here. -- Evilham From owner-freebsd-current@freebsd.org Tue Jan 19 12:59:56 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F11654F3929 for ; Tue, 19 Jan 2021 12:59:56 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKpf41rrXz3QQv for ; Tue, 19 Jan 2021 12:59:56 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-lf1-x132.google.com with SMTP id b26so28939661lff.9 for ; Tue, 19 Jan 2021 04:59:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=U17tDD6BPpPxR6iXeFizWJzRAIbGmet7osm/s6NyouI=; b=ZUDJYBEu3gBGw0NiMMTBYrsfn3ca3i35vpzO4XlJpfCLQcyHv/DaWv+kagTwcH1Oc+ uarMD1+A0WoNJv2tplcaNkiAMoPmUKcUsNV01HNwKP8qh2eVZ8N8ak+uTWMXlgEqFelE 8TLU0uyqS0Tg2WqWJCfkpDOhmx+XaICynoLmMttzmZEaBf+gasuw2dLOgoAP3C1ac3hu ja7rB5ZglzSGfsLM8zJXVNvPJ7b9W2T6zP2jpPsn0pECQpTstN9JaXpS6qbkCENMF9se O75bm+16RamGXgxpuWFqFo2P2Csp3Pc4BqblT0aecwZvJJrHs/rqsQSLt4WQJDqavMC8 M3OA== X-Gm-Message-State: AOAM533mfPEg9JEURyG26dO86rfVeJfvoyEYUEdzEyn1bP5spjkKJjYQ CLAtUIUYDqa5btSJoBVxpTQ= X-Google-Smtp-Source: ABdhPJztAx1B9ig9J+wbuzEbLzTbOhWYfU8VGhgpcnz1RiquSu0NINKz508/9P2WiCMefp4YUqwlQA== X-Received: by 2002:a19:991:: with SMTP id 139mr1830248lfj.637.1611061194269; Tue, 19 Jan 2021 04:59:54 -0800 (PST) Received: from localhost (customer-109-238-136-64.stosn.net. [109.238.136.64]) by smtp.gmail.com with ESMTPSA id a15sm2284766lfr.68.2021.01.19.04.59.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 Jan 2021 04:59:53 -0800 (PST) References: <86czy2n2yk.fsf@gmail.com> User-agent: mu4e 1.2.0; emacs 27.1 From: Malcolm Matalka To: Greg V Cc: FreeBSD Current Subject: Re: Name of touchpad changed in latest rev In-reply-to: Date: Tue, 19 Jan 2021 13:59:53 +0100 Message-ID: <86sg6xulo6.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 4DKpf41rrXz3QQv X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.98)[-0.984]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::132:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::132:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::132:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 12:59:57 -0000 Greg V writes: > On Mon, Jan 18, 2021 at 08:01, Malcolm Matalka wrote: >> I just installed the below revision, and looks like the name the mouse >> shows up as has changed. Not sure if this is intended or not. What was >> "SynPS/2 Synaptics TouchPad" and now it is "DELL07E6:00 06CB:76AF >> TouchPad". > > Congratulations, you are now using the touchpad over I2C instead of PS/2 :) > The iichid code has finally landed in current so we have much better HID support > now. Oh wow! Great! That opens up a bunch of laptop options too as I've had other laptops where I couldn't use the trackpad because it was i2c. Glad to see it's landed! Thank you all involved! From owner-freebsd-current@freebsd.org Tue Jan 19 14:26:29 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8D19B4F5F09 for ; Tue, 19 Jan 2021 14:26:29 +0000 (UTC) (envelope-from 010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@amazonses.com) Received: from a8-24.smtp-out.amazonses.com (a8-24.smtp-out.amazonses.com [54.240.8.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKrYx0Kc9z3lw9 for ; Tue, 19 Jan 2021 14:26:28 +0000 (UTC) (envelope-from 010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@amazonses.com) To: freebsd-current@freebsd.org From: Thomas Laus Subject: DRM problem installing kernel on main-c561-gc3e75b6c1 Message-ID: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> Date: Tue, 19 Jan 2021 14:26:27 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-SES-Outgoing: 2021.01.19-54.240.8.24 Feedback-ID: 1.us-east-1.9pbSdi8VQuDGy3n7CRAr3/hYnLCug78GrsPo0xSgBOs=:AmazonSES X-Rspamd-Queue-Id: 4DKrYx0Kc9z3lw9 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[amazonses.com:s=224i4yxa5dv7c2xz3womw6peuasteono]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[acm.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; DKIM_TRACE(0.00)[amazonses.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[54.240.8.24:from]; FORGED_SENDER(0.30)[lausts@acm.org,010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@amazonses.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[54.240.8.24:from]; ASN(0.00)[asn:14618, ipnet:54.240.8.0/21, country:US]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; FROM_NEQ_ENVFROM(0.00)[lausts@acm.org,010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@amazonses.com]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 14:26:29 -0000 I perform a CURRENT build weekly on a more powerful build machine and then export /usr/src and /usr/obj via NFS to other slower PC's. The 'installkernel' phase failed with 'linuxkpi_gplv2.ko' not found. It looks like this file is not installed before the rest of the 'drm-current-kmod' files. This causes the 'installkernel' over NFS to fail. My fis was to un-install drm-current-kmod, install the kernel and then re-install drm-current-kmod. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Tue Jan 19 19:34:07 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 98DD44DCA84 for ; Tue, 19 Jan 2021 19:34:07 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKzNt3GjGz4Zsn for ; Tue, 19 Jan 2021 19:34:06 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from MacBook-Pro.nomadlogic.org (cpe-24-24-163-126.socal.res.rr.com [24.24.163.126]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 051fdfff (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Tue, 19 Jan 2021 19:33:58 +0000 (UTC) Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 To: freebsd-current@freebsd.org References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> From: Pete Wright Message-ID: Date: Tue, 19 Jan 2021 11:33:53 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4DKzNt3GjGz4Zsn X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[174.136.98.114:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[174.136.98.114:from:127.0.2.255]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 19:34:07 -0000 On 1/19/21 6:26 AM, Thomas Laus wrote: > I perform a CURRENT build weekly on a more powerful build machine and > then export /usr/src and /usr/obj via NFS to other slower PC's. The > 'installkernel' phase failed with 'linuxkpi_gplv2.ko' not found. It > looks like this file is not installed before the rest of the > 'drm-current-kmod' files. This causes the 'installkernel' over NFS to fail. > > My fis was to un-install drm-current-kmod, install the kernel and then > re-install drm-current-kmod. hrm, i'm not sure this is specifically an NFS issue.  I am building/installing locally on my workstation but am getting similar errors trying to load drm-devel-kmod's amdgpu mod.  at this point even uninstalling drm-devel-kmod, make installkernel, install drm-devel-kmod pkg results in the same problem. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue Jan 19 19:40:06 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D5F464DCC3F for ; Tue, 19 Jan 2021 19:40:06 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKzWp0M3cz4bJt for ; Tue, 19 Jan 2021 19:40:05 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from MacBook-Pro.nomadlogic.org (cpe-24-24-163-126.socal.res.rr.com [24.24.163.126]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id dd0e2794 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Tue, 19 Jan 2021 19:40:05 +0000 (UTC) Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 From: Pete Wright To: freebsd-current@freebsd.org References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> Message-ID: <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> Date: Tue, 19 Jan 2021 11:40:04 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.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-Rspamd-Queue-Id: 4DKzWp0M3cz4bJt X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[174.136.98.114:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[174.136.98.114:from:127.0.2.255]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 19:40:06 -0000 On 1/19/21 11:33 AM, Pete Wright wrote: > > > On 1/19/21 6:26 AM, Thomas Laus wrote: >> I perform a CURRENT build weekly on a more powerful build machine and >> then export /usr/src and /usr/obj via NFS to other slower PC's. The >> 'installkernel' phase failed with 'linuxkpi_gplv2.ko' not found.  It >> looks like this file is not installed before the rest of the >> 'drm-current-kmod' files.  This causes the 'installkernel' over NFS >> to fail. >> >> My fis was to un-install drm-current-kmod, install the kernel and then >> re-install drm-current-kmod. > hrm, i'm not sure this is specifically an NFS issue.  I am > building/installing locally on my workstation but am getting similar > errors trying to load drm-devel-kmod's amdgpu mod.  at this point even > uninstalling drm-devel-kmod, make installkernel, install > drm-devel-kmod pkg results in the same problem. > forgot to include dmesg error: KLD drm.ko: depends on linuxkpi_gplv2 - not available or version mismatch linker_load_file: /boot/modules/drm.ko - unsupported file type KLD amdgpu.ko: depends on drmn - not available or version mismatch linker_load_file: /boot/modules/amdgpu.ko - unsupported file type -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue Jan 19 20:12:27 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D58574DDB4E for ; Tue, 19 Jan 2021 20:12:27 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DL0F66ZTNz4d78 for ; Tue, 19 Jan 2021 20:12:26 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from amy.home (lfbn-idf2-1-745-114.w86-247.abo.wanadoo.fr [86.247.192.114]) by mx.blih.net (OpenSMTPD) with ESMTPSA id a752860d (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 19 Jan 2021 20:12:18 +0000 (UTC) Date: Tue, 19 Jan 2021 21:11:59 +0100 From: Emmanuel Vadot To: Pete Wright Cc: freebsd-current@freebsd.org Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 Message-Id: <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> In-Reply-To: <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4DL0F66ZTNz4d78 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; FREEFALL_USER(0.00)[manu]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; ARC_NA(0.00)[]; SPAMHAUS_ZRD(0.00)[212.83.155.74:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.83.155.74:from]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 20:12:27 -0000 On Tue, 19 Jan 2021 11:40:04 -0800 Pete Wright wrote: >=20 >=20 > On 1/19/21 11:33 AM, Pete Wright wrote: > > > > > > On 1/19/21 6:26 AM, Thomas Laus wrote: > >> I perform a CURRENT build weekly on a more powerful build machine and > >> then export /usr/src and /usr/obj via NFS to other slower PC's. The > >> 'installkernel' phase failed with 'linuxkpi_gplv2.ko' not found.=A0 It > >> looks like this file is not installed before the rest of the > >> 'drm-current-kmod' files.=A0 This causes the 'installkernel' over NFS= =20 > >> to fail. > >> > >> My fis was to un-install drm-current-kmod, install the kernel and then > >> re-install drm-current-kmod. > > hrm, i'm not sure this is specifically an NFS issue.=A0 I am=20 > > building/installing locally on my workstation but am getting similar=20 > > errors trying to load drm-devel-kmod's amdgpu mod.=A0 at this point eve= n=20 > > uninstalling drm-devel-kmod, make installkernel, install=20 > > drm-devel-kmod pkg results in the same problem. > > > forgot to include dmesg error: > KLD drm.ko: depends on linuxkpi_gplv2 - not available or version mismatch > linker_load_file: /boot/modules/drm.ko - unsupported file type > KLD amdgpu.ko: depends on drmn - not available or version mismatch > linker_load_file: /boot/modules/amdgpu.ko - unsupported file type >=20 > -pete >=20 > --=20 > Pete Wright > pete@nomadlogic.org > @nomadlogicLA Sound like you have an old linuxkpi_gplv2.ko in /boot/kernel/ --=20 Emmanuel Vadot From owner-freebsd-current@freebsd.org Tue Jan 19 20:18:13 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 002C24DE42F for ; Tue, 19 Jan 2021 20:18:13 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DL0Mm2Gwkz4f1k for ; Tue, 19 Jan 2021 20:18:11 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from MacBook-Pro.nomadlogic.org (cpe-24-24-163-126.socal.res.rr.com [24.24.163.126]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id fbeb6122 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 19 Jan 2021 20:18:10 +0000 (UTC) Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 To: Emmanuel Vadot Cc: freebsd-current@freebsd.org References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> From: Pete Wright Message-ID: <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> Date: Tue, 19 Jan 2021 12:18:10 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4DL0Mm2Gwkz4f1k X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; ARC_NA(0.00)[]; SPAMHAUS_ZRD(0.00)[174.136.98.114:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[174.136.98.114:from]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 20:18:13 -0000 On 1/19/21 12:11 PM, Emmanuel Vadot wrote: > On Tue, 19 Jan 2021 11:40:04 -0800 > Pete Wright wrote: > >> >> On 1/19/21 11:33 AM, Pete Wright wrote: >>> >>> On 1/19/21 6:26 AM, Thomas Laus wrote: >>>> I perform a CURRENT build weekly on a more powerful build machine and >>>> then export /usr/src and /usr/obj via NFS to other slower PC's. The >>>> 'installkernel' phase failed with 'linuxkpi_gplv2.ko' not found.  It >>>> looks like this file is not installed before the rest of the >>>> 'drm-current-kmod' files.  This causes the 'installkernel' over NFS >>>> to fail. >>>> >>>> My fis was to un-install drm-current-kmod, install the kernel and then >>>> re-install drm-current-kmod. >>> hrm, i'm not sure this is specifically an NFS issue.  I am >>> building/installing locally on my workstation but am getting similar >>> errors trying to load drm-devel-kmod's amdgpu mod.  at this point even >>> uninstalling drm-devel-kmod, make installkernel, install >>> drm-devel-kmod pkg results in the same problem. >>> >> forgot to include dmesg error: >> KLD drm.ko: depends on linuxkpi_gplv2 - not available or version mismatch >> linker_load_file: /boot/modules/drm.ko - unsupported file type >> KLD amdgpu.ko: depends on drmn - not available or version mismatch >> linker_load_file: /boot/modules/amdgpu.ko - unsupported file type >> >> -pete >> >> -- >> Pete Wright >> pete@nomadlogic.org >> @nomadlogicLA > Sound like you have an old linuxkpi_gplv2.ko in /boot/kernel/ > Thanks Manu - so it looks like i don't have that file under /boot/kernel/ but in /boot/modules instead: $ find /boot/ -name '*linuxkpi*' -print /boot/modules/linuxkpi_gplv2.ko /boot/kernel/linuxkpi.ko /boot/kernel.old/linuxkpi.ko $ pkg which /boot/modules/linuxkpi_gplv2.ko /boot/modules/linuxkpi_gplv2.ko was installed by package drm-current-kmod-5.4.62.g20210118 $ above is after installing the current kmod to see if it behaved differently than the devel one. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue Jan 19 21:06:40 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C0D814DF820 for ; Tue, 19 Jan 2021 21:06:40 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DL1Rg3B80z4jWJ for ; Tue, 19 Jan 2021 21:06:39 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.223] (cpe-24-24-163-126.socal.res.rr.com [24.24.163.126]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 877ce9f7 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 19 Jan 2021 21:06:37 +0000 (UTC) Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 From: Pete Wright To: Emmanuel Vadot Cc: freebsd-current@freebsd.org References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> Message-ID: <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> Date: Tue, 19 Jan 2021 13:06:37 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4DL1Rg3B80z4jWJ X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[174.136.98.114:from]; SPAMHAUS_ZRD(0.00)[174.136.98.114:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 21:06:40 -0000 On 1/19/21 12:18 PM, Pete Wright wrote: > > > On 1/19/21 12:11 PM, Emmanuel Vadot wrote: >> On Tue, 19 Jan 2021 11:40:04 -0800 >> Pete Wright wrote: >> >>> >>> On 1/19/21 11:33 AM, Pete Wright wrote: >>>> >>>> On 1/19/21 6:26 AM, Thomas Laus wrote: >>>>> I perform a CURRENT build weekly on a more powerful build machine and >>>>> then export /usr/src and /usr/obj via NFS to other slower PC's. The >>>>> 'installkernel' phase failed with 'linuxkpi_gplv2.ko' not found.  It >>>>> looks like this file is not installed before the rest of the >>>>> 'drm-current-kmod' files.  This causes the 'installkernel' over NFS >>>>> to fail. >>>>> >>>>> My fis was to un-install drm-current-kmod, install the kernel and >>>>> then >>>>> re-install drm-current-kmod. >>>> hrm, i'm not sure this is specifically an NFS issue.  I am >>>> building/installing locally on my workstation but am getting similar >>>> errors trying to load drm-devel-kmod's amdgpu mod.  at this point even >>>> uninstalling drm-devel-kmod, make installkernel, install >>>> drm-devel-kmod pkg results in the same problem. >>>> >>> forgot to include dmesg error: >>> KLD drm.ko: depends on linuxkpi_gplv2 - not available or version >>> mismatch >>> linker_load_file: /boot/modules/drm.ko - unsupported file type >>> KLD amdgpu.ko: depends on drmn - not available or version mismatch >>> linker_load_file: /boot/modules/amdgpu.ko - unsupported file type >>> >>> -pete >>> >>> -- >>> Pete Wright >>> pete@nomadlogic.org >>> @nomadlogicLA >>   Sound like you have an old linuxkpi_gplv2.ko in /boot/kernel/ >> > > Thanks Manu - so it looks like i don't have that file under > /boot/kernel/ but in /boot/modules instead: > $ find /boot/ -name '*linuxkpi*' -print > /boot/modules/linuxkpi_gplv2.ko > /boot/kernel/linuxkpi.ko > /boot/kernel.old/linuxkpi.ko > $ pkg which /boot/modules/linuxkpi_gplv2.ko > /boot/modules/linuxkpi_gplv2.ko was installed by package > drm-current-kmod-5.4.62.g20210118 > $ > > above is after installing the current kmod to see if it behaved > differently than the devel one. > > -pete > > interesting - so it seems like if i have drm-devel-kmod installed this will fail (missing or wrong linuxkpi_gplv2.ko).  this happens both if i install the pkg and rebuild the kernel, and if i build the kernel w/o the pkg installed. yet, if i have the drm-current-kmod pkg installed, then "make buildkernel" it looks like the i915/amdgpu modules get build and an "installkernel" drops the linuxkpi_gplv2.ko module under /boot/kernel.  at that point i am able to successfully load the amdgpu.ko. finally, i install the drm-current-pkg fresh (without doing the above buildkernel/installkernel) i get the linuxkpi_gplv2 error as above. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue Jan 19 21:18:06 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BAFCF4DFC5D for ; Tue, 19 Jan 2021 21:18:06 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DL1hq4XgHz4kD8 for ; Tue, 19 Jan 2021 21:18:03 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from amy.home (lfbn-idf2-1-745-114.w86-247.abo.wanadoo.fr [86.247.192.114]) by mx.blih.net (OpenSMTPD) with ESMTPSA id dcedf4b6 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 19 Jan 2021 21:18:01 +0000 (UTC) Date: Tue, 19 Jan 2021 22:18:01 +0100 From: Emmanuel Vadot To: Pete Wright Cc: freebsd-current@freebsd.org Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 Message-Id: <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> In-Reply-To: <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4DL1hq4XgHz4kD8 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; FREEFALL_USER(0.00)[manu]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; ARC_NA(0.00)[]; SPAMHAUS_ZRD(0.00)[212.83.155.74:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.83.155.74:from]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 21:18:06 -0000 On Tue, 19 Jan 2021 13:06:37 -0800 Pete Wright wrote: >=20 >=20 > On 1/19/21 12:18 PM, Pete Wright wrote: > > > > > > On 1/19/21 12:11 PM, Emmanuel Vadot wrote: > >> On Tue, 19 Jan 2021 11:40:04 -0800 > >> Pete Wright wrote: > >> > >>> > >>> On 1/19/21 11:33 AM, Pete Wright wrote: > >>>> > >>>> On 1/19/21 6:26 AM, Thomas Laus wrote: > >>>>> I perform a CURRENT build weekly on a more powerful build machine a= nd > >>>>> then export /usr/src and /usr/obj via NFS to other slower PC's. The > >>>>> 'installkernel' phase failed with 'linuxkpi_gplv2.ko' not found.=A0= It > >>>>> looks like this file is not installed before the rest of the > >>>>> 'drm-current-kmod' files.=A0 This causes the 'installkernel' over N= FS > >>>>> to fail. > >>>>> > >>>>> My fis was to un-install drm-current-kmod, install the kernel and=20 > >>>>> then > >>>>> re-install drm-current-kmod. > >>>> hrm, i'm not sure this is specifically an NFS issue.=A0 I am > >>>> building/installing locally on my workstation but am getting similar > >>>> errors trying to load drm-devel-kmod's amdgpu mod.=A0 at this point = even > >>>> uninstalling drm-devel-kmod, make installkernel, install > >>>> drm-devel-kmod pkg results in the same problem. > >>>> > >>> forgot to include dmesg error: > >>> KLD drm.ko: depends on linuxkpi_gplv2 - not available or version=20 > >>> mismatch > >>> linker_load_file: /boot/modules/drm.ko - unsupported file type > >>> KLD amdgpu.ko: depends on drmn - not available or version mismatch > >>> linker_load_file: /boot/modules/amdgpu.ko - unsupported file type > >>> > >>> -pete > >>> > >>> --=20 > >>> Pete Wright > >>> pete@nomadlogic.org > >>> @nomadlogicLA > >> =A0 Sound like you have an old linuxkpi_gplv2.ko in /boot/kernel/ > >> > > > > Thanks Manu - so it looks like i don't have that file under=20 > > /boot/kernel/ but in /boot/modules instead: > > $ find /boot/ -name '*linuxkpi*' -print > > /boot/modules/linuxkpi_gplv2.ko > > /boot/kernel/linuxkpi.ko > > /boot/kernel.old/linuxkpi.ko > > $ pkg which /boot/modules/linuxkpi_gplv2.ko > > /boot/modules/linuxkpi_gplv2.ko was installed by package=20 > > drm-current-kmod-5.4.62.g20210118 > > $ > > > > above is after installing the current kmod to see if it behaved=20 > > differently than the devel one. > > > > -pete > > > > >=20 > interesting - so it seems like if i have drm-devel-kmod installed this=20 > will fail (missing or wrong linuxkpi_gplv2.ko).=A0 this happens both if i= =20 > install the pkg and rebuild the kernel, and if i build the kernel w/o=20 > the pkg installed. Don't use the package, always rebuild from the latest ports. > yet, if i have the drm-current-kmod pkg installed, then "make=20 > buildkernel" it looks like the i915/amdgpu modules get build and an=20 > "installkernel" drops the linuxkpi_gplv2.ko module under /boot/kernel.=A0= =20 > at that point i am able to successfully load the amdgpu.ko. drm-current-kmod will also install its sources in /usr/local/sys/ and this will get built with buildkernel. The problem is that if the package is old (and it is right now) you might have sources that either don't compile or don't work correctly. > finally, i install the drm-current-pkg fresh (without doing the above=20 > buildkernel/installkernel) i get the linuxkpi_gplv2 error as above. >=20 > -pete >=20 > --=20 > Pete Wright > pete@nomadlogic.org > @nomadlogicLA >=20 --=20 Emmanuel Vadot From owner-freebsd-current@freebsd.org Tue Jan 19 21:29:14 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AD94B4E017F for ; Tue, 19 Jan 2021 21:29:14 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DL1xk096Sz4kyw for ; Tue, 19 Jan 2021 21:29:13 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.223] (cpe-24-24-163-126.socal.res.rr.com [24.24.163.126]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 9d0f3fdc (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 19 Jan 2021 21:29:12 +0000 (UTC) Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 To: Emmanuel Vadot Cc: freebsd-current@freebsd.org References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> From: Pete Wright Message-ID: <1922f880-1bd3-65d0-b816-73623fa62f33@nomadlogic.org> Date: Tue, 19 Jan 2021 13:29:12 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4DL1xk096Sz4kyw X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[174.136.98.114:from]; SPAMHAUS_ZRD(0.00)[174.136.98.114:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 19 Jan 2021 21:29:14 -0000 On 1/19/21 1:18 PM, Emmanuel Vadot wrote: > >> interesting - so it seems like if i have drm-devel-kmod installed this >> will fail (missing or wrong linuxkpi_gplv2.ko).  this happens both if i >> install the pkg and rebuild the kernel, and if i build the kernel w/o >> the pkg installed. > Don't use the package, always rebuild from the latest ports. see bellow >> yet, if i have the drm-current-kmod pkg installed, then "make >> buildkernel" it looks like the i915/amdgpu modules get build and an >> "installkernel" drops the linuxkpi_gplv2.ko module under /boot/kernel. >> at that point i am able to successfully load the amdgpu.ko. > drm-current-kmod will also install its sources in /usr/local/sys/ and > this will get built with buildkernel. The problem is that if the > package is old (and it is right now) you might have sources that either > don't compile or don't work correctly. OK interesting, in both cases I was building the package from my local ports tree (via "make package").  i should have better explained that in previous emails. i verified my checkout was up to date as well (it includes your latest commits from Sunday and Monday). i'm happy now running the current-kmod but let me know if it'd be helpful to do any more tests or provide additional info. cheers, -pete > -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Jan 20 01:42:28 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 349F34E5B78 for ; Wed, 20 Jan 2021 01:42:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-55.consmr.mail.gq1.yahoo.com (sonic315-55.consmr.mail.gq1.yahoo.com [98.137.65.31]) (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 4DL7Yt2ddmz3GgS for ; Wed, 20 Jan 2021 01:42:25 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1611106944; bh=KFPXpALPxR/GAi5tkYuVizVV/DP6N2LVmO92bloGEu7=; h=Subject:From:Date:To:From:Subject:Reply-To; b=oys/EgIvY06uJ3Pf2JfKLPFTcz7ejFxDwPyaXhGnZAUBT1mPldVZykadHdo+/n1ImA0I0yycXMVTl+omhGAJslQjJjlBRlOm/iBbsJoSi+CE02DPYn47coeuf2dxe0z2C+KsiRPaf4ByCydVzj54kZhfqfXy5RdqzzKVWwq0KFyr3V/6WfOD70sXkL88ypKhFd4PPx62i3hppdGe2tb0/5ys/9MiNHrsP5dryxIPnK/Kumt9QCzIKhaGVvuocAfu0gVvZp29fFT6cOzJFMO879MEYH7YCqNiyZeNTiJEeX4vBMHEgAOIest1B93AYCYQ3zHzguCyCLXgN1a3fT5IMQ== X-YMail-OSG: iHSptXsVM1mVwaFY.D9rVclZJSU8HiWlxzLa57yRvQKdv2CxorzuefYXjnmBMLH LEmApRaNCJUSQ.o1W0IMiadeQbmnDC18kyiTYY3qG1AzoPdcAyYM16f7N.IBSE8DdJMCzkksNooi .zAs.fKL.9Kp3ZGmQVD5y3WUJMylIzkJgkAmZ_pNgFoQF5imI5O.gIAFvBe4CMFdH2WSMrjgFiJY 3ZZQUP1lPWKVA8s7hhSmI.N6L6KNafU0HwPsHRXeqPr3Rl5XA43ZwyW81OW9LEGdbyDAwkHZY9HF aM_NTPWl_wWa70jyAd9CK7HS4JLlmPtIvCs8.Jmwb2ESHPvzI31i4cJLQ4Sw7ffSQvtwN_JPtNIq ocEkGEIUE29BFJil08dNJhcPMAuuS8HV.G5n2fBP4PdqllesJ9ANndn3SPE_OrlcC0DsZnztN_Bu SPxV_JTrwTj.Q1AZToE_XsUDmf7AS3T32pr3OIJ9RZqxOMArEf2kfIjSOzPxunAzt9rhhiG0pjZD qjnqpZX.xxPI7Gjj1fOU9SlXq9jZYwIkv5BejKj6MNn80HKkxfhmMT2Q1tPIiD8UQG58qKPm2mJc bIMEkQ_z8T4gzJImqTq52HkMStQMHBKg_v8Pj42qCLNtSvglp2982495NXcEuJZ7k1SKAIs7lYPQ JhDqL6Gc5ar06v7PO8f2dq92LdoxkcfEckbDLQJ6eqDOnC2yCyW3bua469rhrW8vtdCyfxYWnsph 52WgW2Mm.z7ymf4wnWRY4pfO8D42Lz89nP1kQACzfLW.sh_zNyZlDCr6MKDL8BM3vLD0mvaamwbi REU1T0Xt9eVd6gLQ30xeRNsF0U9PUFz5KzTi.g.1cKLet9Uz6VxjckZ4L1844Wf0nHau0s2OVzf8 uoI4NvKfqPR3IMAO2i4BIZTnqcY2syjowsQKKlhcGSOD1zJ9bA8kp8vkK8WzkUnKt6_1AKZt_QGN mPhwEU6hBzY43zCe31PWigJVhQouw1arJXaMfPsvfL1NEa1m8KyGyJKbiJ1JP6nDVXmKfPvgiSeA oha9RF85YntQWVDSb9vBmT34UXeScn2CEHgpI7Zi96cQOzXY4q7RNHRAlrBCvqP9afITL4mKAXSP PJ3weSRzUJ0xsd.XKuVnc6UJ9eIT6Zw6WdJ0AIP_T7gVniYSsh1nOXA5W.5C0ZA9hBQCieayiWja JhoTLAjtjYNuVx7d_PC0VrLo5pcIyf92oLGCluQ9ywjnk_5Xt0IGze4JSNqPTn2Am6mIbarx.V01 Li7Tr1ufc8cOgBIGbDhGIN9nIHLKu8YVn__6jdc8JF96qXznjjlUT49i.9std4wF5YZP7DQL0Fwe KoImymLPININSyWUo.aZ_mIYQkb02Fa19LTHJVlQX4iBbUPvlEvqzbJnRatgFgnIwAKhBaCnzqZq euC59Md.SsnOdpMmmO1Il5.3DSo0gWSBT2drcmwJIlSdKbcl_KwywUe1YIqLmXOVsT0Z1Ox1VRgx y3F9pPN3XFQf2rhsTcUJ0f.T2tiK73JofypPOay7mET3AHFmaCs.vks.G26_itwA99LEuJkE1rJd I4b1Jf0Hbhf4QIuU839hPYUQkfhcZBR3JYqiSWG9fOa5a5LRwvyYxUBlHSeV39lYXXnGeZnWs.8. b6NEfe5mN_F8YBZj6tQQnI8SUa9mc53m.0S2bQiIT7k5ZbWAGY3QYxeCDe7mA9zP1fDIu.26SyOq wf8NZ5ba_g4JaMQRzS2gldJMK3FiwDDNZizFtoihHzOd5fnmTw2dKTXovao4fYKhoQNmnExUxY4V lybGwwL7ROzzBNsZkaFLAgXnTPQTOOqmbP12lKk4_FZdgJHGSBC8utVFtDhKIaDuntr5dcCXmUnB oj4zVISkgLrK360xcfNxJBM8LD8v9RUBCtBpQjNGQR1SN45_TzTVRhXKZ3tNkSvbskJrtvPCfsmN DNKfb_QHOGgREfWqLF9LGZkQ.e3OHSfz0AhGvkB_Tc0XZ.TPAgIQDdUtWHs4JCx48wGvy64gNmHO jgpXMXxxf5RqFRTF1hoD5HpS6Z8XEkgpjQ09WJ4tA1z1ZY1s9No_G2rvJuUbmgYTO2FwV9g9fhsH MyMGwNcGP5Qjn_91DHndR7gc7LFC12DxN7rBCIN8vuYqafFMF04ks9QV9TFRJOgwbf.8SPmVSpxg M.ECpbY88cJdmD2PFp13oQWL1b5mabCBvtMWmyS8bPLStTtqcIDSJNRJHK8U0DCs9GFA.5KpjQfG PCoZucENTIvB9hXD.5JP1vuScNYydoD.PxJp38nbtJjLfWiTlpYiYlQl54dDAGkcafG8xv1esVO3 c5o2tEy7XOWl5muqamKYR3dpTf_3XeTJNgumB8nGIOpDnVkFb6digzxGCbFSjSBvEfsbEU4oZaNI Ol3ZbI7nCtu_fDGRwUMpNku4XNU_eTRhtgMVFrEoshU_fHQzpmSVBZWvAs6OkHdDfjvvtbpFF7.v MoVDl6CbPbNa9ECg4Xi8dmRt0vaYnYiX7lyIez72fNVHbx_HiE83o922FV48QDSc4e8sPIs_D4tB j4rT81_3n6bicbMYJsL_lrLDmQ8R3RmihovYoVH0G_6aGH95yhixd2_QhXC9aWqS2f2o9qeDghth WAfjjVkv2RWJqBSuXyEQGCdiPuZ61UG6lZi55_rjuz.MbGYBHiCfNSMxw Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Wed, 20 Jan 2021 01:42:24 +0000 Received: by smtp405.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 6ab45ba876346170a3cb4d9f66d6453d; Wed, 20 Jan 2021 01:42:23 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld From: Mark Millard In-Reply-To: Date: Tue, 19 Jan 2021 17:42:22 -0800 Cc: Current FreeBSD , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <056845FE-7131-4951-96AF-805D07F7BE0D@yahoo.com> References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> <20210118015009.GA31353@www.zefox.net> <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> <00104FAD-E32B-4DDE-80DD-FCEF14CEC06B@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DL7Yt2ddmz3GgS X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.43 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.93)[-0.932]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.65.31:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.65.31:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.31:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.31:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 01:42:28 -0000 On 2021-Jan-18, at 21:12, Mark Millard wrote: > On 2021-Jan-18, at 19:19, Mark Millard wrote: >=20 >> . . . >>> FYI: I re-established my access to a RPi2B V1.1 and made >>> it report: "maximum recommended amount (468832 pages)" >>>=20 >>> (The figure can vary some from release to release.) >>>=20 >>> 468832*4096 =3D=3D 1920335872 or a little over 1831 MiBytes >>>=20 >>> For the 4096 Byte pages, that means that the following from >>> gpart fits without complaint (size is in blocks, not pages): >>>=20 >>> 413140992 3686400 da0p2 freebsd-swap (1.8G) >>>=20 >>> 3686400*512 is a little over 1.75 GiByte or 1800 MiByte. So >>> I've left some room below 1831 MiBytes, but not a lot. >>>=20 >>> FYI about my build experiment that is running: >>>=20 >>> # sysctl hw.physmem >>> hw.physmem: 979042304 >>>=20 >>> which, in recent times for armv7, I can (and did) set in >>> /boot/loader.conf on a faster cortex-A7 SBC (that can boot >>> the same media but has more RAM). >>>=20 >>> So I tried a -j4 build, but with LDFLAGS.lld+=3D -Wl,--threads=3D1 >>> in use and my other particular src.conf/make.conf like content >>> (so the builds do likely differ from yours in various ways). >>> My build is producing a non-debug build (but with -g symbols). >>> Somewhat after where your buildworld.log stops, my odd variant >>> of top was reporting: >>>=20 >>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) >>> Swap: . . . , 145832Ki MaxObsUsed >>>=20 >>> and top was also showing lots of processes as having "0B" RES >>> in STATE "wait" or "nanslp" (so, apparently swapped out, not = paging). >>> ("MaxObs" is short for "maximum observed".) >>>=20 >>> For comparison, your swapscript.log reported a maximum total of >>> 346192 KiBytes "Used" for swap, about 98% into the log file. >>>=20 >>> (Time goes by . . .) >>>=20 >>> It finished with building libllvm and is part way into building >>> libclang. This is probably well past where your hangup happened, >>> given that your published buildworldlog file stopped with >>> libllvm's Target/ARM/ARMMCInstLower.o . My odd top now shows: >>>=20 >>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) >>> Swap: . . . , 392328Ki MaxObsUsed >>>=20 >>> The build continues to run. I'll let you know how it goes. >>> . . . >>=20 >> Just after libclang finished my odd top showed: >>=20 >> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892736Ki = MaxObs(Act+Wir) >> Swap: . . . , 537588Ki MaxObsUsed >>=20 >> After liblldb: >>=20 >> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 899276Ki = MaxObs(Act+Wir) >> Swap: . . . , 537588Ki MaxObsUsed >>=20 >> Much later, after the lldb program had been built: >>=20 >> Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki = MaxObs(Act+Wir) >> Swap: . . . , 537588Ki MaxObsUsed >>=20 >>>>> World build completed on Mon Jan 18 19:10:08 PST 2021 >>>>> World built in 72960 seconds, ncpu: 4, make -j4 >>=20 >> This was building from scratch what was already installed: >>=20 >> # ~/fbsd-based-on-what-freebsd-main.sh=20 >> merge-base: 818390ce0ca539300dd15d7a817784f1e3f7a9b8 >> merge-base: CommitDate: 2021-01-13 21:27:44 +0000 >> 4180404713ec (HEAD -> mm-src) mm-src snapshot for mm's patched build = in git context. >> 818390ce0ca5 (freebsd/main, freebsd/HEAD, pure-src, main) arm64: fix = early devmap assertion >> FreeBSD OPiP2E_RPi2v11 13.0-CURRENT FreeBSD 13.0-CURRENT = mm-src-c255938-g4180404713ec GENERIC-NODBG arm armv7 1300135 1300135 >>=20 >> This suggests that you should be able to build on the RPi2B v1.1, >> using -j4, with appropriate configuration for what and how to build. >>=20 >>=20 >> It is now building the matching kernel, my GENERIC-NODBG style. >=20 > Done: >=20 >>>> Kernel build for GENERIC-NODBG completed on Mon Jan 18 20:33:26 PST = 2021 >>>> Kernel(s) GENERIC-NODBG built in 4998 seconds, ncpu: 4, make -j4 >=20 > So, World+Kernel in somewhat under 22 hours. >=20 > The "MaxObs*" figures were unchanged, so: >=20 > Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki = MaxObs(Act+Wir) > Swap: . . . , 537588Ki MaxObsUsed >=20 > This suggests that, for now, 800 MiByte of swap would be something > more than 1.5 times what it actually used and 1050 MiBytes would > be something like 2.0 times what it actually used, so leaving some > notable margin for variations in peek usage, at least when linker > threading is avoided. >=20 >=20 >=20 > As for what I used to control "what and how to build" . . . >=20 > # more = ~/sys_build_scripts.armv7-host/make_armv7_nodebug_clang_bootstrap-armv7-ho= st.sh=20 > kldload -n filemon && \ > script = ~/sys_typescripts/typescript_make_armv7_nodebug_clang_bootstrap-armv7-host= -$(date +%Y-%m-%d:%H:%M:%S) \ > env __MAKE_CONF=3D"/root/src.configs/make.conf" SRCCONF=3D"/dev/null" = SRC_ENV_CONF=3D"/root/src.configs/src.conf.armv7-clang-bootstrap.armv7-hos= t" \ > WITH_META_MODE=3Dyes \ > WORLD_FLAGS=3D"${WORLD_FLAGS} UBLDR_LOADADDR=3D0x42000000" \ > MAKEOBJDIRPREFIX=3D"/usr/obj/armv7_clang/arm.armv7" \ > make $* >=20 > (In my context, UBLDR_LOADADDR is ignored by anything that > can not use the figure given. So I've no bothered to be > more selective about having it in the armv7 builds.) >=20 > # more ~/src.configs/make.conf > LDFLAGS.lld+=3D -Wl,--threads=3D1 >=20 > # more ~/src.configs/src.conf.armv7-clang-bootstrap.armv7-host > TO_TYPE=3Darmv7 > # > KERNCONF=3DGENERIC-NODBG > TARGET=3Darm > .if ${.MAKE.LEVEL} =3D=3D 0 > TARGET_ARCH=3D${TO_TYPE} > .export TARGET_ARCH > .endif > # > #WITH_CROSS_COMPILER=3D > WITH_SYSTEM_COMPILER=3D > WITH_SYSTEM_LINKER=3D > # > WITH_LIBCPLUSPLUS=3D > WITHOUT_BINUTILS_BOOTSTRAP=3D > WITH_ELFTOOLCHAIN_BOOTSTRAP=3D > #Disables avoiding bootstrap: WITHOUT_LLVM_TARGET_ALL=3D > WITHOUT_LLVM_TARGET_AARCH64=3D > WITH_LLVM_TARGET_ARM=3D > WITHOUT_LLVM_TARGET_MIPS=3D > WITHOUT_LLVM_TARGET_POWERPC=3D > WITHOUT_LLVM_TARGET_RISCV=3D > WITHOUT_LLVM_TARGET_X86=3D > WITH_CLANG=3D > WITH_CLANG_IS_CC=3D > WITH_CLANG_FULL=3D > WITH_CLANG_EXTRAS=3D > WITH_LLD=3D > WITH_LLD_IS_LD=3D > WITHOUT_BINUTILS=3D > # > WITH_LLDB=3D > # > WITH_BOOT=3D > WITHOUT_LIB32=3D > # > # > WITHOUT_WERROR=3D > #WERROR=3D > MALLOC_PRODUCTION=3D > WITH_MALLOC_PRODUCTION=3D > WITHOUT_ASSERT_DEBUG=3D > WITHOUT_LLVM_ASSERTIONS=3D > # > # Avoid stripping but do not control host -g status as well: > DEBUG_FLAGS+=3D > # > WITH_REPRODUCIBLE_BUILD=3D > WITH_DEBUG_FILES=3D > # > # Use of the .clang 's here avoids > # interfering with other CFLAGS > # usage, such as ?=3D usage. > CFLAGS.clang+=3D -mcpu=3Dcortex-a7 > CXXFLAGS.clang+=3D -mcpu=3Dcortex-a7 > CPPFLAGS.clang+=3D -mcpu=3Dcortex-a7 >=20 > (I do not claim that you would want WITH_REPRODUCIBLE_BUILD . > I just happen to have been experimenting with it. You might > not want to be explicit about the cpu to target. You might > not want WITH_CLANG_EXTRAS .) >=20 > # more /usr/fbsd/mm-src/sys/arm/conf/GENERIC-NODBG > include "GENERIC" >=20 > ident GENERIC-NODBG >=20 > makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols >=20 > options AUDIT # Not enabled by default in = armv7/v6 kernels > # Enabled here to allow kyua = test runs to > # possibly report auditing = works. >=20 > options ALT_BREAK_TO_DEBUGGER >=20 > options KDB # Enable kernel debugger = support >=20 > # For minimum debugger support (stable branch) use: > options KDB_TRACE # Print a stack trace for a = panic > options DDB # Enable the kernel debugger >=20 > # Extra stuff: > #options VERBOSE_SYSINIT=3D0 # Enable verbose sysinit = messages > #options BOOTVERBOSE=3D1 > #options BOOTHOWTO=3DRB_VERBOSE > options ALT_BREAK_TO_DEBUGGER # Enter debugger on keyboard = escape sequence > options KLD_DEBUG > #options KTR > #options KTR_MASK=3DKTR_TRAP > ##options KTR_CPUMASK=3D0xF > #options KTR_VERBOSE >=20 > # Disable any extra checking for. . . > nooptions INVARIANTS # Enable calls of extra sanity = checking > nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS > nooptions WITNESS # Enable checks to detect = deadlocks and cycles > nooptions WITNESS_SKIPSPIN # Don't run witness on = spinlocks for speed > nooptions DEADLKRES # Enable the deadlock resolver > nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones > nooptions DIAGNOSTIC > nooptions BUF_TRACKING > nooptions FULL_BUF_TRACKING > nooptions USB_DEBUG > nooptions USB_REQ_DEBUG > nooptions USB_VERBOSE >=20 > The /boot/loader.conf file and the /etc/sysctl.conf files > both contained: >=20 > vm.pageout_oom_seq=3D120 > vm.pfault_oom_attempts=3D-1 >=20 > (The hw.physmem=3D979042304 in /boot/loader.conf was very-special, > to better approximate your environment. I also controlled the > cpu frequency used via a line in /etc/sysctl.conf . I do not > bother with such non-default frequency usage [or related settings] > for RPi*'s with the pre-RPi4B style power connections but do > control the frequency for the OPi+2E.) The following had been left implicit about my context and how it manages memory space use. I'll note that I do not use tmpfs or other such memory based file system techniques that could compete for RAM/swap. What is in use for the only file system involved is just the root file system: # df -m Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/gpt/BPIM3root 195378 63940 115808 36% / devfs 0 0 0 100% /dev It is a USB SSD. The swap partition is also on that same media. (The BPIM3 based name dates back to before the BPI-M3 power connection failed and I switched to the OPi+2E.) I'll note that I've started a new from-scratch build without LDFLAGS.lld+=3D -Wl,--threads=3D1 . So at some point I'll have information about how much of a difference (+/-) in swap usage it actually made for with vs. without, if any. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Wed Jan 20 07:55:40 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4EC934ECFD6 for ; Wed, 20 Jan 2021 07:55:40 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLHrV4jRVz3qXt for ; Wed, 20 Jan 2021 07:55:38 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from amy.home (lfbn-idf2-1-745-114.w86-247.abo.wanadoo.fr [86.247.192.114]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 9e1d3f79 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 20 Jan 2021 07:55:35 +0000 (UTC) Date: Wed, 20 Jan 2021 08:55:35 +0100 From: Emmanuel Vadot To: Pete Wright Cc: freebsd-current@freebsd.org Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 Message-Id: <20210120085535.d3b6ccb33f9c8b111922b422@bidouilliste.com> In-Reply-To: <1922f880-1bd3-65d0-b816-73623fa62f33@nomadlogic.org> References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> <1922f880-1bd3-65d0-b816-73623fa62f33@nomadlogic.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4DLHrV4jRVz3qXt X-Spamd-Bar: - X-Spamd-Result: default: False [-1.62 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; FREEFALL_USER(0.00)[manu]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; ARC_NA(0.00)[]; NEURAL_SPAM_SHORT(0.88)[0.879]; SPAMHAUS_ZRD(0.00)[212.83.155.74:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.83.155.74:from]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 07:55:40 -0000 On Tue, 19 Jan 2021 13:29:12 -0800 Pete Wright wrote: >=20 >=20 > On 1/19/21 1:18 PM, Emmanuel Vadot wrote: > > > >> interesting - so it seems like if i have drm-devel-kmod installed this > >> will fail (missing or wrong linuxkpi_gplv2.ko).=A0 this happens both i= f i > >> install the pkg and rebuild the kernel, and if i build the kernel w/o > >> the pkg installed. > > Don't use the package, always rebuild from the latest ports. > see bellow > >> yet, if i have the drm-current-kmod pkg installed, then "make > >> buildkernel" it looks like the i915/amdgpu modules get build and an > >> "installkernel" drops the linuxkpi_gplv2.ko module under /boot/kernel. > >> at that point i am able to successfully load the amdgpu.ko. > > drm-current-kmod will also install its sources in /usr/local/sys/ and > > this will get built with buildkernel. The problem is that if the > > package is old (and it is right now) you might have sources that either > > don't compile or don't work correctly. > OK interesting, in both cases I was building the package from my local=20 > ports tree (via "make package").=A0 i should have better explained that i= n=20 > previous emails. Ok > i verified my checkout was up to date as well (it includes your latest=20 > commits from Sunday and Monday). Ok > i'm happy now running the current-kmod but let me know if it'd be=20 > helpful to do any more tests or provide additional info. So what did you change ? > cheers, > -pete >=20 > > >=20 > --=20 > Pete Wright > pete@nomadlogic.org > @nomadlogicLA >=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 Emmanuel Vadot From owner-freebsd-current@freebsd.org Wed Jan 20 10:02:30 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E87174F041D for ; Wed, 20 Jan 2021 10:02:30 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 4DLLft09Lfz4Tvh for ; Wed, 20 Jan 2021 10:02:29 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-f649235c.06-431-73746f70.bbcust.telenor.se ([92.35.73.246] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l2AJi-000Fsx-0I; Wed, 20 Jan 2021 11:02:22 +0100 Received: from [192.168.67.27] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l2AJh-0005aX-FL; Wed, 20 Jan 2021 11:02:21 +0100 Subject: Re: Waiting for bufdaemon To: Konstantin Belousov Cc: freebsd-current References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> From: Jakob Alvermark Message-ID: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> Date: Wed, 20 Jan 2021 11:02:21 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 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-Rspamd-Queue-Id: 4DLLft09Lfz4Tvh X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.48 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[185.34.136.138:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[alvermark.net:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.98)[-0.980]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[185.34.136.138:from]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/23, country:IT]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 10:02:31 -0000 On 1/17/21 10:49 AM, Konstantin Belousov wrote: > On Sun, Jan 17, 2021 at 10:37:18AM +0100, Rainer Hurling wrote: >> Am 17.01.21 um 05:33 schrieb Konstantin Belousov: >>> On Sat, Jan 16, 2021 at 07:41:01PM +0100, Rainer Hurling wrote: >>>> During another shutdown after heavy usage of the box, the following >>>> messages were also seen: >>>> >>>> >>>> [...] >>>> Syncing disks, vnodes remaining... 22 EFI rt_settime call faulted, error 14 >>>> efirtc0: CLOCK_SETTIME error 14 >>> This means that BIOS code faulted during RTC settime call. I doubt that >>> it is related. >>> >>> On the other hand, it is good that the onfault EFI RT code got tested finally. >>> >> Thanks for clarification :) >> >> >> Any chance of getting a fix for the AMD CPUs in the foreseeable future? >> >> Or should I revert commit 9e680e4005b7 on affected boxes until further >> notice (as a workaround)? > I am working on it, no ETA. > > Interesting point would be to check on machines of other testers, > if the following hides the problem. > > diff --git a/sys/x86/x86/tsc.c b/sys/x86/x86/tsc.c > index 85924df98312..5700a8ca98e5 100644 > --- a/sys/x86/x86/tsc.c > +++ b/sys/x86/x86/tsc.c > @@ -639,7 +639,7 @@ init_TSC_tc(void) > * on Intel, and MFENCE;RDTSC on AMD. > * - For really old CPUs, just use RDTSC. > */ > - if ((cpu_vendor_id == CPU_VENDOR_AMD || > + if (false && (cpu_vendor_id == CPU_VENDOR_AMD || > cpu_vendor_id == CPU_VENDOR_HYGON) && > CPUID_TO_FAMILY(cpu_id) >= 0x17) { > tsc_timecounter.tc_get_timecount = shift > 0 ? This patch hides the problem for me. The system seems to work better now. No waiting on reboot, and the webcam works better. Jakob From owner-freebsd-current@freebsd.org Wed Jan 20 10:14:14 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C0C174F090C for ; Wed, 20 Jan 2021 10:14:14 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 4DLLwP6Fvnz4VGr for ; Wed, 20 Jan 2021 10:14:13 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-f649235c.06-431-73746f70.bbcust.telenor.se ([92.35.73.246] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l2AVA-000FtP-GQ for freebsd-current@freebsd.org; Wed, 20 Jan 2021 11:14:12 +0100 Received: from [192.168.67.27] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l2AVA-0005mY-0Z for freebsd-current@freebsd.org; Wed, 20 Jan 2021 11:14:12 +0100 Subject: Re: boot loader blank screen To: freebsd-current@freebsd.org References: <83EB3B04-EAE8-4EC3-820B-2F5C3BADE948@me.com> <66908803-BA6F-4538-9D93-6F85A95108C9@me.com> <831788F9-F97F-4A02-A6F9-AE05219DA2E9@me.com> From: Jakob Alvermark Message-ID: Date: Wed, 20 Jan 2021 11:14:11 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 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-Rspamd-Queue-Id: 4DLLwP6Fvnz4VGr X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[185.34.136.138:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[alvermark.net:+]; NEURAL_HAM_SHORT(-1.00)[-0.996]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[185.34.136.138:from]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/23, country:IT]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 10:14:14 -0000 On 1/14/21 8:15 AM, Jakob Alvermark wrote: > > On 1/14/21 4:49 AM, monochrome wrote: >> I should add my experience to this since its different and haven't >> seen anyone else mention it. >> I see the new boot loader, it's not blank, but its large text, and >> it's very SLOW. >> I can see each char drawn, and then when it gets to the bottom and >> has to redraw all the lines to scroll up for new lines, it loads so >> slowly it's like watching an 8086 on a 300 baud modem, or slower! >> Takes like an extra 30 seconds to get through all the loaded modules, >> then back to normal speed boot with the same large font. >> >> added these lines and everything is back to normal with new >> appearance and small font like before, and at normal speed. >> hw.vga.textmode="0" >> vbe_max_resolution=1280x800 >> >> also removed the old lines for the amdgpu efi problem with no effect >> so I assume those are no longer necessary and why I'm seeing this >> change? >> #hw.syscons.disable=1 >> #kern.vty=vt >> #hw.vga.textmode=1 >> >> am using X and everything seems fine for now >> >> system: >> AMD Ryzen 5 2400G, using integrated vega GPU >> ASRock B450M Pro4 >> 13-current >> >> >> >> On 1/5/21 8:54 PM, David Wolfskill wrote: >>> On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: >>>> ... >>>>> the 58661b3ba9eb should hopefully fix the loader text mode issue, >>>>> it would be cool if you can verify:) >>>>> >>>>> thanks, >>>>> toomas >>>> >>>> I think, I got it fixed (at least idwer did confirm for his system, >>>> thanks). If you can test this patch: >>>> http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch >>>> >>>> it would be really nice. >>>> >>>> thanks, >>>> toomas >>> >>> I tested with each of the following "stanzas' in /boot/loader.conf, >>> using vt (vs. syscons) in each case (though that breaks video reset >>> on resume after suspend): >>> >>> # hw.vga.textmode="0" >>> vbe_max_resolution=1280x800 >>> >>> This works, and provides a graphical console (depth 32). >>> >>> >>> hw.vga.textmode="0" >>> # vbe_max_resolution=1280x800 >>> >>> This also works, and provides a low-resolution (and depth 16) >>> graphical console (800x320 or something similar, IIRC). >>> >>> >>> # hw.vga.textmode="0" >>> # vbe_max_resolution=1280x800 >>> >>> (That is, not specifying anything for hw.vga.textmode or >>> vbe_max_resolution.) >>> >>> This boots OK, but I see no kernel probe messages or single- to >>> multi-user mode messages.  I can use (e.g.) Ctl+Alt+F2 to switch to >>> vty1, see a "login: " prompt, and that (also) works.  (This is the >>> initial symptom I had reported.) >>> >>> >>> hw.vga.textmode="1" >>> # vbe_max_resolution=1280x800 >>> >>> This works -- boots OK, and I see kernel probe (&c.) messages; this >>> is a >>> text console (mostly blue text; some white, against a dark background. >>> It's a medium-light blue, so it's easy enough to read (unlike a navy >>> blue, for example). >>> >>> >>> FreeBSD g1-55.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #113 >>> main-c255601-g9fd96b416c45-dirty: Tue Jan  5 17:24:45 PST 2021 >>> root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >>> amd64 > > > +1 on the slowness. > > I like the graphics mode, it's very pretty. > > But slow. It seems to depend a lot on the screen resolution. On my > small laptop, 1366x768, it's fairly OK. On the 1080p laptop it is very > much slower, it takes about 35 seconds longer compared to the old loader. > > Booting on a 4K monitor, well, I didn't time it... Observations with the current version: 1. The font is now a lot smaller. 2. It feels quicker. However, still a bit slow. Something that seems very slow is clearing the screen. It's like pulling down a curtain slowly. 3. Booting on the 4k monitor does not work now. Loader looks alright, but when it hands over to the kernel, the screen just goes blank, and the machine hangs. This worked before. Jakob From owner-freebsd-current@freebsd.org Wed Jan 20 10:18:53 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9D2194F0D83 for ; Wed, 20 Jan 2021 10:18:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLM1n085dz4Vrk for ; Wed, 20 Jan 2021 10:18:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 10KAIiTg078614 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 20 Jan 2021 12:18:47 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 10KAIiTg078614 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 10KAIiDF078613; Wed, 20 Jan 2021 12:18:44 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 20 Jan 2021 12:18:44 +0200 From: Konstantin Belousov To: Jakob Alvermark Cc: freebsd-current Subject: Re: Waiting for bufdaemon Message-ID: References: <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4DLM1n085dz4Vrk X-Spamd-Bar: / X-Spamd-Result: default: False [-1.00 / 15.00]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:d5e7:1::1:from]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2001:470:d5e7:1::1:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 10:18:53 -0000 On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: > This patch hides the problem for me. The system seems to work better now. > > No waiting on reboot, and the webcam works better. I am curious what do you mean by the above reference to webcam. Can you explain it with more details, even if only the impressions? I probably going to commit the following patch in the next 24 hours. commit 02505d07bca320a638c96918ac9076c6eece2fff Author: Konstantin Belousov Date: Wed Jan 20 11:32:21 2021 +0200 AMD Zen CPUs: switch TSC timecounter to RDTSCP Reported by: many MFC after: 1 weel Sponsored by: The FreeBSD Foundation diff --git a/lib/libc/x86/sys/__vdso_gettc.c b/lib/libc/x86/sys/__vdso_gettc.c index 7f224f8758cb..7a64f2a0b556 100644 --- a/lib/libc/x86/sys/__vdso_gettc.c +++ b/lib/libc/x86/sys/__vdso_gettc.c @@ -125,7 +125,7 @@ struct tsc_selector_tag { }; static const struct tsc_selector_tag tsc_selector[] = { - [0] = { /* Intel or AMD Zen+, LFENCE */ + [0] = { /* Intel, LFENCE */ .ts_rdtsc32 = rdtsc32_mb_lfence, .ts_rdtsc_low = rdtsc_low_mb_lfence, }, @@ -164,9 +164,6 @@ tsc_selector_idx(u_int cpu_feature) do_cpuid(1, p); cpu_id = p[0]; - if (amd_cpu && CPUID_TO_FAMILY(cpu_id) >= 0x17) - return (0); - if (cpu_feature != 0) { do_cpuid(0x80000000, p); cpu_exthigh = p[0]; diff --git a/sys/x86/x86/tsc.c b/sys/x86/x86/tsc.c index 85924df98312..de0a1505c2f6 100644 --- a/sys/x86/x86/tsc.c +++ b/sys/x86/x86/tsc.c @@ -633,19 +633,12 @@ init_TSC_tc(void) /* * Timecounter implementation selection, top to bottom: - * - For AMD Zens and newer, use LFENCE;RDTSC. * - If RDTSCP is available, use RDTSCP. * - If fence instructions are provided (SSE2), use LFENCE;RDTSC * on Intel, and MFENCE;RDTSC on AMD. * - For really old CPUs, just use RDTSC. */ - if ((cpu_vendor_id == CPU_VENDOR_AMD || - cpu_vendor_id == CPU_VENDOR_HYGON) && - CPUID_TO_FAMILY(cpu_id) >= 0x17) { - tsc_timecounter.tc_get_timecount = shift > 0 ? - tsc_get_timecount_low_lfence : - tsc_get_timecount_lfence; - } else if ((amd_feature & AMDID_RDTSCP) != 0) { + if ((amd_feature & AMDID_RDTSCP) != 0) { tsc_timecounter.tc_get_timecount = shift > 0 ? tscp_get_timecount_low : tscp_get_timecount; } else if ((cpu_feature & CPUID_SSE2) != 0 && mp_ncpus > 1) { From owner-freebsd-current@freebsd.org Wed Jan 20 10:37:07 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 42C274F1312 for ; Wed, 20 Jan 2021 10:37:07 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 4DLMQp4JFfz4WQF for ; Wed, 20 Jan 2021 10:37:06 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-f649235c.06-431-73746f70.bbcust.telenor.se ([92.35.73.246] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l2ArJ-000FuV-9I; Wed, 20 Jan 2021 11:37:05 +0100 Received: from [192.168.67.27] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l2ArI-0006Br-PG; Wed, 20 Jan 2021 11:37:04 +0100 Subject: Re: Waiting for bufdaemon To: Konstantin Belousov Cc: freebsd-current References: <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> From: Jakob Alvermark Message-ID: <1c4608c3-6116-c110-236c-3a70967d2edb@alvermark.net> Date: Wed, 20 Jan 2021 11:37:04 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 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-Rspamd-Queue-Id: 4DLMQp4JFfz4WQF X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[185.34.136.138:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[alvermark.net:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[185.34.136.138:from]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/23, country:IT]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 10:37:07 -0000 On 1/20/21 11:18 AM, Konstantin Belousov wrote: > On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >> This patch hides the problem for me. The system seems to work better now. >> >> No waiting on reboot, and the webcam works better. > I am curious what do you mean by the above reference to webcam. > Can you explain it with more details, even if only the impressions? > > I probably going to commit the following patch in the next 24 hours. > > commit 02505d07bca320a638c96918ac9076c6eece2fff > Author: Konstantin Belousov > Date: Wed Jan 20 11:32:21 2021 +0200 > > AMD Zen CPUs: switch TSC timecounter to RDTSCP > > Reported by: many > MFC after: 1 weel > Sponsored by: The FreeBSD Foundation > > diff --git a/lib/libc/x86/sys/__vdso_gettc.c b/lib/libc/x86/sys/__vdso_gettc.c > index 7f224f8758cb..7a64f2a0b556 100644 > --- a/lib/libc/x86/sys/__vdso_gettc.c > +++ b/lib/libc/x86/sys/__vdso_gettc.c > @@ -125,7 +125,7 @@ struct tsc_selector_tag { > }; > > static const struct tsc_selector_tag tsc_selector[] = { > - [0] = { /* Intel or AMD Zen+, LFENCE */ > + [0] = { /* Intel, LFENCE */ > .ts_rdtsc32 = rdtsc32_mb_lfence, > .ts_rdtsc_low = rdtsc_low_mb_lfence, > }, > @@ -164,9 +164,6 @@ tsc_selector_idx(u_int cpu_feature) > do_cpuid(1, p); > cpu_id = p[0]; > > - if (amd_cpu && CPUID_TO_FAMILY(cpu_id) >= 0x17) > - return (0); > - > if (cpu_feature != 0) { > do_cpuid(0x80000000, p); > cpu_exthigh = p[0]; > diff --git a/sys/x86/x86/tsc.c b/sys/x86/x86/tsc.c > index 85924df98312..de0a1505c2f6 100644 > --- a/sys/x86/x86/tsc.c > +++ b/sys/x86/x86/tsc.c > @@ -633,19 +633,12 @@ init_TSC_tc(void) > > /* > * Timecounter implementation selection, top to bottom: > - * - For AMD Zens and newer, use LFENCE;RDTSC. > * - If RDTSCP is available, use RDTSCP. > * - If fence instructions are provided (SSE2), use LFENCE;RDTSC > * on Intel, and MFENCE;RDTSC on AMD. > * - For really old CPUs, just use RDTSC. > */ > - if ((cpu_vendor_id == CPU_VENDOR_AMD || > - cpu_vendor_id == CPU_VENDOR_HYGON) && > - CPUID_TO_FAMILY(cpu_id) >= 0x17) { > - tsc_timecounter.tc_get_timecount = shift > 0 ? > - tsc_get_timecount_low_lfence : > - tsc_get_timecount_lfence; > - } else if ((amd_feature & AMDID_RDTSCP) != 0) { > + if ((amd_feature & AMDID_RDTSCP) != 0) { > tsc_timecounter.tc_get_timecount = shift > 0 ? > tscp_get_timecount_low : tscp_get_timecount; > } else if ((cpu_feature & CPUID_SSE2) != 0 && mp_ncpus > 1) { I have a Logitech C270 USB webcam that I use for all the online meetings now that everyone is working from home. (MS Teams, Google Meet, Slack, Zoom, whatever...). It is supported by multimedia/webcamd and has been working mostly fine. (just some rare, occasional hickups) When I started to notice the bufdaemon problems, I also noticed the webcam not behaving as before. It sometimes took me two or three tries to start the camera when joining a meeting and once it started my video would freeze sometimes, being frozen for a minute or so. Sometimes when I noticed that it frooze I would try to restart it, and again it might take a couple of tries to get it working again. With the patch it seems to work better again. Jakob From owner-freebsd-current@freebsd.org Wed Jan 20 12:17:56 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1D9114F4001 for ; Wed, 20 Jan 2021 12:17:56 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4DLPg71PpRz4dY6 for ; Wed, 20 Jan 2021 12:17:54 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-03.um.gwdg.de ([134.76.9.218] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1l2CQq-00017b-4I; Wed, 20 Jan 2021 13:17:52 +0100 Received: from krabat.raven.hur (10.250.9.200) by EXCMBX-03.um.gwdg.de (134.76.9.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.2044.4; Wed, 20 Jan 2021 13:17:51 +0100 Subject: Re: Waiting for bufdaemon To: Konstantin Belousov CC: freebsd-current References: <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> Reply-To: From: Rainer Hurling Message-ID: <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> Date: Wed, 20 Jan 2021 13:17:51 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.200] X-ClientProxiedBy: EXCMBX-02.um.gwdg.de (134.76.9.217) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4DLPg71PpRz4dY6 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; HAS_REPLYTO(0.00)[rhurlin@FreeBSD.org]; HAS_XOIP(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:134.76.10.0/23]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[134.76.11.17:from]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:680, ipnet:134.76.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[rhurlin]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; DMARC_NA(0.00)[gwdg.de]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[134.76.11.17:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 12:17:56 -0000 Am 20.01.21 um 11:18 schrieb Konstantin Belousov: > On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >> This patch hides the problem for me. The system seems to work better now. >> >> No waiting on reboot, and the webcam works better. > I am curious what do you mean by the above reference to webcam. > Can you explain it with more details, even if only the impressions? I should mention, that beside the already discussed timing problem with bufdaemon, I also have problems with several apps: After a high system load, several programs only react very slowly (e.g. Firefox). Several dockable apps from WindowMaker, but also e.g. conky do not update their windows anymore, they freeze. After some time, Firefox updates its screen content only after switching back from another window ... When such frozen programs are killed and restarted, they run normally again for an indefinite time before they freeze again. These symptoms completely disappeared, after I patched the Ryzen box as suggested on 01/17: diff --git a/sys/x86/tsc.c b/sys/x86/tsc.c index 85924df98312..5700a8ca98e5 100644 --- a/sys/x86/x86/tsc.c +++ b/sys/x86/x86/tsc.c @@ -639,7 +639,7 @@ init_TSC_tc(void) * on Intel, and MFENCE;RDTSC on AMD. * - For really old CPUs, just use RDTSC. */ - if ((cpu_vendor_id == CPU_VENDOR_AMD || + if (false && (cpu_vendor_id == CPU_VENDOR_AMD || cpu_vendor_id == CPU_VENDOR_HYGON) && CPUID_TO_FAMILY(cpu_id) >= 0x17) { tsc_timecounter.tc_get_timecount = shift > 0 ? HTH, Rainer > > I probably going to commit the following patch in the next 24 hours. > > commit 02505d07bca320a638c96918ac9076c6eece2fff > Author: Konstantin Belousov > Date: Wed Jan 20 11:32:21 2021 +0200 > > AMD Zen CPUs: switch TSC timecounter to RDTSCP > > Reported by: many > MFC after: 1 weel > Sponsored by: The FreeBSD Foundation > > diff --git a/lib/libc/x86/sys/__vdso_gettc.c b/lib/libc/x86/sys/__vdso_gettc.c > index 7f224f8758cb..7a64f2a0b556 100644 > --- a/lib/libc/x86/sys/__vdso_gettc.c > +++ b/lib/libc/x86/sys/__vdso_gettc.c > @@ -125,7 +125,7 @@ struct tsc_selector_tag { > }; > > static const struct tsc_selector_tag tsc_selector[] = { > - [0] = { /* Intel or AMD Zen+, LFENCE */ > + [0] = { /* Intel, LFENCE */ > .ts_rdtsc32 = rdtsc32_mb_lfence, > .ts_rdtsc_low = rdtsc_low_mb_lfence, > }, > @@ -164,9 +164,6 @@ tsc_selector_idx(u_int cpu_feature) > do_cpuid(1, p); > cpu_id = p[0]; > > - if (amd_cpu && CPUID_TO_FAMILY(cpu_id) >= 0x17) > - return (0); > - > if (cpu_feature != 0) { > do_cpuid(0x80000000, p); > cpu_exthigh = p[0]; > diff --git a/sys/x86/x86/tsc.c b/sys/x86/x86/tsc.c > index 85924df98312..de0a1505c2f6 100644 > --- a/sys/x86/x86/tsc.c > +++ b/sys/x86/x86/tsc.c > @@ -633,19 +633,12 @@ init_TSC_tc(void) > > /* > * Timecounter implementation selection, top to bottom: > - * - For AMD Zens and newer, use LFENCE;RDTSC. > * - If RDTSCP is available, use RDTSCP. > * - If fence instructions are provided (SSE2), use LFENCE;RDTSC > * on Intel, and MFENCE;RDTSC on AMD. > * - For really old CPUs, just use RDTSC. > */ > - if ((cpu_vendor_id == CPU_VENDOR_AMD || > - cpu_vendor_id == CPU_VENDOR_HYGON) && > - CPUID_TO_FAMILY(cpu_id) >= 0x17) { > - tsc_timecounter.tc_get_timecount = shift > 0 ? > - tsc_get_timecount_low_lfence : > - tsc_get_timecount_lfence; > - } else if ((amd_feature & AMDID_RDTSCP) != 0) { > + if ((amd_feature & AMDID_RDTSCP) != 0) { > tsc_timecounter.tc_get_timecount = shift > 0 ? > tscp_get_timecount_low : tscp_get_timecount; > } else if ((cpu_feature & CPUID_SSE2) != 0 && mp_ncpus > 1) { From owner-freebsd-current@freebsd.org Wed Jan 20 12:32:45 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D152F4F457F for ; Wed, 20 Jan 2021 12:32:45 +0000 (UTC) (envelope-from 010001771fc86afe-607c8bb1-5ba3-4302-9873-dbd81b4b39fb-000000@amazonses.com) Received: from a48-106.smtp-out.amazonses.com (a48-106.smtp-out.amazonses.com [54.240.48.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLQ0F1LT9z4fY6 for ; Wed, 20 Jan 2021 12:32:44 +0000 (UTC) (envelope-from 010001771fc86afe-607c8bb1-5ba3-4302-9873-dbd81b4b39fb-000000@amazonses.com) Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 To: freebsd-current@freebsd.org References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> From: Thomas Laus Message-ID: <010001771fc86afe-607c8bb1-5ba3-4302-9873-dbd81b4b39fb-000000@email.amazonses.com> Date: Wed, 20 Jan 2021 12:32:44 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-SES-Outgoing: 2021.01.20-54.240.48.106 Feedback-ID: 1.us-east-1.9pbSdi8VQuDGy3n7CRAr3/hYnLCug78GrsPo0xSgBOs=:AmazonSES X-Rspamd-Queue-Id: 4DLQ0F1LT9z4fY6 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[amazonses.com:s=224i4yxa5dv7c2xz3womw6peuasteono]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[acm.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; DKIM_TRACE(0.00)[amazonses.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[54.240.48.106:from]; FORGED_SENDER(0.30)[lausts@acm.org,010001771fc86afe-607c8bb1-5ba3-4302-9873-dbd81b4b39fb-000000@amazonses.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[54.240.48.106:from]; ASN(0.00)[asn:14618, ipnet:54.240.48.0/23, country:US]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; FROM_NEQ_ENVFROM(0.00)[lausts@acm.org,010001771fc86afe-607c8bb1-5ba3-4302-9873-dbd81b4b39fb-000000@amazonses.com]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 12:32:45 -0000 On 1/19/21 4:18 PM, Emmanuel Vadot wrote: > > drm-current-kmod will also install its sources in /usr/local/sys/ and > this will get built with buildkernel. The problem is that if the > package is old (and it is right now) you might have sources that either > don't compile or don't work correctly. > For years, I have been building world and kernel on a faster PC and just exporting /usr/src and /usr/obj for installation on other computers. Now it looks like it will require exporting /usr/local/sys as well to allow a installation of the kernel on the slower PC's. Does placing the drm-current-kmod files in /usr/local/sys during the kernel build agree with hier(7)layout ? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Wed Jan 20 12:34:15 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D94C84F4867 for ; Wed, 20 Jan 2021 12:34:15 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLQ1y6ZLzz4fbf; Wed, 20 Jan 2021 12:34:14 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 10KCY1HX011027 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 20 Jan 2021 14:34:04 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 10KCY1HX011027 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 10KCY1OV011026; Wed, 20 Jan 2021 14:34:01 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 20 Jan 2021 14:34:01 +0200 From: Konstantin Belousov To: rhurlin@freebsd.org Cc: freebsd-current Subject: Re: Waiting for bufdaemon Message-ID: References: <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4DLQ1y6ZLzz4fbf X-Spamd-Bar: - X-Spamd-Result: default: False [-1.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:d5e7:1::1:from]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2001:470:d5e7:1::1:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 12:34:15 -0000 On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: > Am 20.01.21 um 11:18 schrieb Konstantin Belousov: > > On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: > >> This patch hides the problem for me. The system seems to work better now. > >> > >> No waiting on reboot, and the webcam works better. > > I am curious what do you mean by the above reference to webcam. > > Can you explain it with more details, even if only the impressions? > > I should mention, that beside the already discussed timing problem with > bufdaemon, I also have problems with several apps: > > > After a high system load, several programs only react very slowly (e.g. > Firefox). Several dockable apps from WindowMaker, but also e.g. conky do > not update their windows anymore, they freeze. After some time, Firefox > updates its screen content only after switching back from another window ... > > When such frozen programs are killed and restarted, they run normally > again for an indefinite time before they freeze again. > > These symptoms completely disappeared, after I patched the Ryzen box as > suggested on 01/17: Do you load latest microcode update from devcpu-data? It might be not enough, which means that additionally latest BIOS needs to be flushed. From owner-freebsd-current@freebsd.org Wed Jan 20 12:56:59 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DDCDF4F5278 for ; Wed, 20 Jan 2021 12:56:59 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4DLQXC5zFvz4hCP for ; Wed, 20 Jan 2021 12:56:59 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-03.um.gwdg.de ([134.76.9.218] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1l2D2g-0004rD-9a; Wed, 20 Jan 2021 13:56:58 +0100 Received: from krabat.raven.hur (10.250.9.200) by EXCMBX-03.um.gwdg.de (134.76.9.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.2044.4; Wed, 20 Jan 2021 13:56:57 +0100 Subject: Re: Waiting for bufdaemon To: Konstantin Belousov CC: freebsd-current References: <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> Reply-To: From: Rainer Hurling Message-ID: Date: Wed, 20 Jan 2021 13:56:57 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.200] X-ClientProxiedBy: excmbx-08.um.gwdg.de (134.76.9.215) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4DLQXC5zFvz4hCP X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 12:56:59 -0000 Am 20.01.21 um 13:34 schrieb Konstantin Belousov: > On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: >> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: >>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >>>> This patch hides the problem for me. The system seems to work better now. >>>> >>>> No waiting on reboot, and the webcam works better. >>> I am curious what do you mean by the above reference to webcam. >>> Can you explain it with more details, even if only the impressions? >> >> I should mention, that beside the already discussed timing problem with >> bufdaemon, I also have problems with several apps: >> >> >> After a high system load, several programs only react very slowly (e.g. >> Firefox). Several dockable apps from WindowMaker, but also e.g. conky do >> not update their windows anymore, they freeze. After some time, Firefox >> updates its screen content only after switching back from another window ... >> >> When such frozen programs are killed and restarted, they run normally >> again for an indefinite time before they freeze again. >> >> These symptoms completely disappeared, after I patched the Ryzen box as >> suggested on 01/17: > > Do you load latest microcode update from devcpu-data? Yes, sysutils/devcpu-data is installed and the following to lines are in /boot/loader.conf cpu_microcode_load="YES" cpu_microcode_name="/boot/firmware/intel-ucode.bin" But isn't this just for Intel (i387 and amd64), not AMD cpus? > It might be not enough, which means that additionally latest BIOS needs > to be flushed. > I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite" mainboard. From owner-freebsd-current@freebsd.org Wed Jan 20 13:12:36 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1617B4F5A09 for ; Wed, 20 Jan 2021 13:12:36 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLQtC2tt3z4j9f; Wed, 20 Jan 2021 13:12:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 10KDCRt6020495 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 20 Jan 2021 15:12:31 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 10KDCRt6020495 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 10KDCRrR020494; Wed, 20 Jan 2021 15:12:27 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 20 Jan 2021 15:12:27 +0200 From: Konstantin Belousov To: rhurlin@freebsd.org Cc: freebsd-current Subject: Re: Waiting for bufdaemon Message-ID: References: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4DLQtC2tt3z4j9f X-Spamd-Bar: - X-Spamd-Result: default: False [-1.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:d5e7:1::1:from]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2001:470:d5e7:1::1:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 13:12:36 -0000 On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: > Am 20.01.21 um 13:34 schrieb Konstantin Belousov: > > On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: > >> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: > >>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: > >>>> This patch hides the problem for me. The system seems to work better now. > >>>> > >>>> No waiting on reboot, and the webcam works better. > >>> I am curious what do you mean by the above reference to webcam. > >>> Can you explain it with more details, even if only the impressions? > >> > >> I should mention, that beside the already discussed timing problem with > >> bufdaemon, I also have problems with several apps: > >> > >> > >> After a high system load, several programs only react very slowly (e.g. > >> Firefox). Several dockable apps from WindowMaker, but also e.g. conky do > >> not update their windows anymore, they freeze. After some time, Firefox > >> updates its screen content only after switching back from another window ... > >> > >> When such frozen programs are killed and restarted, they run normally > >> again for an indefinite time before they freeze again. > >> > >> These symptoms completely disappeared, after I patched the Ryzen box as > >> suggested on 01/17: > > > > Do you load latest microcode update from devcpu-data? > > Yes, sysutils/devcpu-data is installed and the following to lines are in > /boot/loader.conf > > cpu_microcode_load="YES" > cpu_microcode_name="/boot/firmware/intel-ucode.bin" > > But isn't this just for Intel (i387 and amd64), not AMD cpus? You need microcode_update_enable="YES" in /etc/rc.conf for late microcode update. I think that early boot update should work on AMD, bit for this you need to select and put right blob. It is enough to load late to answer my question. > > > It might be not enough, which means that additionally latest BIOS needs > > to be flushed. > > > > I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite" > mainboard. From owner-freebsd-current@freebsd.org Wed Jan 20 13:36:06 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 79EE14F63B0 for ; Wed, 20 Jan 2021 13:36:06 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4DLRPL2zHqz4kS6 for ; Wed, 20 Jan 2021 13:36:06 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-03.um.gwdg.de ([134.76.9.218] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1l2DeW-0002jh-BP; Wed, 20 Jan 2021 14:36:04 +0100 Received: from krabat.raven.hur (10.250.9.200) by EXCMBX-03.um.gwdg.de (134.76.9.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.2044.4; Wed, 20 Jan 2021 14:36:04 +0100 Subject: Re: Waiting for bufdaemon To: Konstantin Belousov CC: freebsd-current References: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> Reply-To: From: Rainer Hurling Message-ID: <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> Date: Wed, 20 Jan 2021 14:35:59 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.200] X-ClientProxiedBy: EXCMBX-05.um.gwdg.de (134.76.9.209) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4DLRPL2zHqz4kS6 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 13:36:06 -0000 Am 20.01.21 um 14:12 schrieb Konstantin Belousov: > On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: >> Am 20.01.21 um 13:34 schrieb Konstantin Belousov: >>> On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: >>>> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: >>>>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >>>>>> This patch hides the problem for me. The system seems to work better now. >>>>>> >>>>>> No waiting on reboot, and the webcam works better. >>>>> I am curious what do you mean by the above reference to webcam. >>>>> Can you explain it with more details, even if only the impressions? >>>> >>>> I should mention, that beside the already discussed timing problem with >>>> bufdaemon, I also have problems with several apps: >>>> >>>> >>>> After a high system load, several programs only react very slowly (e.g. >>>> Firefox). Several dockable apps from WindowMaker, but also e.g. conky do >>>> not update their windows anymore, they freeze. After some time, Firefox >>>> updates its screen content only after switching back from another window ... >>>> >>>> When such frozen programs are killed and restarted, they run normally >>>> again for an indefinite time before they freeze again. >>>> >>>> These symptoms completely disappeared, after I patched the Ryzen box as >>>> suggested on 01/17: >>> >>> Do you load latest microcode update from devcpu-data? >> >> Yes, sysutils/devcpu-data is installed and the following to lines are in >> /boot/loader.conf >> >> cpu_microcode_load="YES" >> cpu_microcode_name="/boot/firmware/intel-ucode.bin" >> >> But isn't this just for Intel (i387 and amd64), not AMD cpus? > You need microcode_update_enable="YES" in /etc/rc.conf for late microcode > update. > > I think that early boot update should work on AMD, bit for this you need to > select and put right blob. It is enough to load late to answer my question. Ah, ok. Thanks for clarification. I also put cpu_microcode_load="YES" in /etc/rc.conf for a late update. Should I try again without your patch of sys/x86/tsc.c, whether the problem still occurs? And for the early boot update, how do I know about the right blob? > >> >>> It might be not enough, which means that additionally latest BIOS needs >>> to be flushed. >>> >> >> I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite" >> mainboard. From owner-freebsd-current@freebsd.org Wed Jan 20 13:52:22 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 49A624F6756 for ; Wed, 20 Jan 2021 13:52:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLRm50hdfz4lSL; Wed, 20 Jan 2021 13:52:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 10KDqCbU030095 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 20 Jan 2021 15:52:15 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 10KDqCbU030095 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 10KDqCfQ030094; Wed, 20 Jan 2021 15:52:12 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 20 Jan 2021 15:52:12 +0200 From: Konstantin Belousov To: rhurlin@freebsd.org Cc: freebsd-current Subject: Re: Waiting for bufdaemon Message-ID: References: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4DLRm50hdfz4lSL X-Spamd-Bar: - X-Spamd-Result: default: False [-1.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:d5e7:1::1:from]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2001:470:d5e7:1::1:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 13:52:22 -0000 On Wed, Jan 20, 2021 at 02:35:59PM +0100, Rainer Hurling wrote: > Am 20.01.21 um 14:12 schrieb Konstantin Belousov: > > On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: > >> Am 20.01.21 um 13:34 schrieb Konstantin Belousov: > >>> On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: > >>>> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: > >>>>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: > >>>>>> This patch hides the problem for me. The system seems to work better now. > >>>>>> > >>>>>> No waiting on reboot, and the webcam works better. > >>>>> I am curious what do you mean by the above reference to webcam. > >>>>> Can you explain it with more details, even if only the impressions? > >>>> > >>>> I should mention, that beside the already discussed timing problem with > >>>> bufdaemon, I also have problems with several apps: > >>>> > >>>> > >>>> After a high system load, several programs only react very slowly (e.g. > >>>> Firefox). Several dockable apps from WindowMaker, but also e.g. conky do > >>>> not update their windows anymore, they freeze. After some time, Firefox > >>>> updates its screen content only after switching back from another window ... > >>>> > >>>> When such frozen programs are killed and restarted, they run normally > >>>> again for an indefinite time before they freeze again. > >>>> > >>>> These symptoms completely disappeared, after I patched the Ryzen box as > >>>> suggested on 01/17: > >>> > >>> Do you load latest microcode update from devcpu-data? > >> > >> Yes, sysutils/devcpu-data is installed and the following to lines are in > >> /boot/loader.conf > >> > >> cpu_microcode_load="YES" > >> cpu_microcode_name="/boot/firmware/intel-ucode.bin" > >> > >> But isn't this just for Intel (i387 and amd64), not AMD cpus? > > You need microcode_update_enable="YES" in /etc/rc.conf for late microcode > > update. > > > > I think that early boot update should work on AMD, bit for this you need to > > select and put right blob. It is enough to load late to answer my question. > > Ah, ok. Thanks for clarification. I also put cpu_microcode_load="YES" in > /etc/rc.conf for a late update. > > Should I try again without your patch of sys/x86/tsc.c, whether the > problem still occurs? Yes. > > > And for the early boot update, how do I know about the right blob? I am not aware of the mechanism. My best suggestion is that you match the blob against your CPU family/model id manually. > > > > >> > >>> It might be not enough, which means that additionally latest BIOS needs > >>> to be flushed. > >>> > >> > >> I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite" > >> mainboard. From owner-freebsd-current@freebsd.org Wed Jan 20 13:58:12 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8CD854F6CB1 for ; Wed, 20 Jan 2021 13:58:12 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailout09.eigbox.net (bosmailout09.eigbox.net [66.96.184.9]) (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 4DLRtq59z2z4lZB for ; Wed, 20 Jan 2021 13:58:11 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailscan08.eigbox.net ([10.20.15.8]) by bosmailout09.eigbox.net with esmtp (Exim) id 1l2Dzs-0001pV-AN for freebsd-current@freebsd.org; Wed, 20 Jan 2021 08:58:09 -0500 Received: from [10.115.3.33] (helo=bosimpout13) by bosmailscan08.eigbox.net with esmtp (Exim) id 1l2Dzr-0000NZ-3g for freebsd-current@freebsd.org; Wed, 20 Jan 2021 08:58:07 -0500 Received: from bosauthsmtp03.yourhostingaccount.com ([10.20.18.3]) by bosimpout13 with id K1y32401r03yW76011y6j7; Wed, 20 Jan 2021 08:58:07 -0500 X-Authority-Analysis: v=2.3 cv=Ep1JURUA c=1 sm=1 tr=0 a=6uKCkKhFq2wXOH2GoQX8aA==:117 a=BXB5eCltbCg0Q+nSw1Bwcw==:17 a=EmqxpYm9HcoA:10 a=jXMol9EDn2QA:10 a=13zjGPudsaEWiJwPRgMA:9 a=6I5d2MoRAAAA:8 a=68TiLBT2nmH7sNCOSEgA:9 a=QEXdDO2ut3YA:10 a=gH7hWQfftoCltWxL3N4A:9 a=FfaGCDsud1wA:10 a=IjZwj45LgO3ly-622nXo:22 Received: from cm-81-9-160-236.telecable.es ([81.9.160.236]:7928 helo=[192.168.1.100]) by bosauthsmtp03.eigbox.net with esmtpa (Exim) id 1l2Dzn-0000eq-PH for freebsd-current@freebsd.org; Wed, 20 Jan 2021 08:58:03 -0500 Subject: Re: Waiting for bufdaemon To: freebsd-current@freebsd.org References: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> From: Santiago Martinez Message-ID: Date: Wed, 20 Jan 2021 13:58:01 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bjkR96Rl37SlEUWAAWUHSJZAsqDaYUsWd" X-EN-UserInfo: d3bdfab0736480cedf04ed92aaea2ef5:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: sm@codenetworks.net Sender: Santiago Martinez X-EN-OrigIP: 81.9.160.236 X-EN-OrigHost: cm-81-9-160-236.telecable.es X-Rspamd-Queue-Id: 4DLRtq59z2z4lZB X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.96.128.0/18:c]; HAS_ATTACHMENT(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[codenetworks.net:~]; SIGNED_PGP(-2.00)[]; FORGED_SENDER(0.30)[sm@codenetworks.net,SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net]; RECEIVED_SPAMHAUS_PBL(0.00)[81.9.160.236:received]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29873, ipnet:66.96.128.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[sm@codenetworks.net,SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[66.96.184.9:from]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[codenetworks.net: no valid DMARC record]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[66.96.184.9:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[66.96.184.9:from]; R_DKIM_PERMFAIL(0.00)[codenetworks.net:s=dkim]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.96.184.9:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 13:58:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bjkR96Rl37SlEUWAAWUHSJZAsqDaYUsWd Content-Type: multipart/mixed; boundary="WGDCUzb3ODMOA9cVG0hXe2jsea8gxbbv1"; protected-headers="v1" From: Santiago Martinez To: freebsd-current@freebsd.org Message-ID: Subject: Re: Waiting for bufdaemon References: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> In-Reply-To: --WGDCUzb3ODMOA9cVG0hXe2jsea8gxbbv1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hi Everyone, i have exactly the same behavior as Rainer described. "After a high system load, several programs only react very slowly (e.g. Firefox)......" I will try with the patch and see if it also clear this on my machine (AMD R7). Santiago On 1/20/21 1:52 PM, Konstantin Belousov wrote: > On Wed, Jan 20, 2021 at 02:35:59PM +0100, Rainer Hurling wrote: >> Am 20.01.21 um 14:12 schrieb Konstantin Belousov: >>> On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: >>>> Am 20.01.21 um 13:34 schrieb Konstantin Belousov: >>>>> On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: >>>>>> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: >>>>>>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >>>>>>>> This patch hides the problem for me. The system seems to work be= tter now. >>>>>>>> >>>>>>>> No waiting on reboot, and the webcam works better. >>>>>>> I am curious what do you mean by the above reference to webcam. >>>>>>> Can you explain it with more details, even if only the impression= s? >>>>>> I should mention, that beside the already discussed timing problem= with >>>>>> bufdaemon, I also have problems with several apps: >>>>>> >>>>>> >>>>>> After a high system load, several programs only react very slowly = (e.g. >>>>>> Firefox). Several dockable apps from WindowMaker, but also e.g. co= nky do >>>>>> not update their windows anymore, they freeze. After some time, Fi= refox >>>>>> updates its screen content only after switching back from another = window ... >>>>>> >>>>>> When such frozen programs are killed and restarted, they run norma= lly >>>>>> again for an indefinite time before they freeze again. >>>>>> >>>>>> These symptoms completely disappeared, after I patched the Ryzen b= ox as >>>>>> suggested on 01/17: >>>>> Do you load latest microcode update from devcpu-data? >>>> Yes, sysutils/devcpu-data is installed and the following to lines ar= e in >>>> /boot/loader.conf >>>> >>>> cpu_microcode_load=3D"YES" >>>> cpu_microcode_name=3D"/boot/firmware/intel-ucode.bin" >>>> >>>> But isn't this just for Intel (i387 and amd64), not AMD cpus? >>> You need microcode_update_enable=3D"YES" in /etc/rc.conf for late mic= rocode >>> update. >>> >>> I think that early boot update should work on AMD, bit for this you n= eed to >>> select and put right blob. It is enough to load late to answer my qu= estion. >> Ah, ok. Thanks for clarification. I also put cpu_microcode_load=3D"YES= " in >> /etc/rc.conf for a late update. >> >> Should I try again without your patch of sys/x86/tsc.c, whether the >> problem still occurs? > Yes. > >> >> And for the early boot update, how do I know about the right blob? > I am not aware of the mechanism. My best suggestion is that you match > the blob against your CPU family/model id manually. > >>>>> It might be not enough, which means that additionally latest BIOS n= eeds >>>>> to be flushed. >>>>> >>>> I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite"= >>>> mainboard. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" --WGDCUzb3ODMOA9cVG0hXe2jsea8gxbbv1-- --bjkR96Rl37SlEUWAAWUHSJZAsqDaYUsWd Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEk06QWJzNAs9NTrFjWBFqYkyC55EFAmAINukFAwAAAAAACgkQWBFqYkyC55F0 CQ/9GJQm0YagKdb+Vfrp/Fhb6iQ3e/ZDM6Qgvg3UwvcrOq4XBib+aHekMkTNz+N5oiuaaJBA1tUJ W2m9l3s9oMTdgwn6SyDUrhVRL3bP/luhwegCk2AapDeqU6GpWi1a6xB7NI9GFCnfjY1WsQZw01O3 11qWG0jppJJ0ZFi30YTJLeMMp8Wf7yQU/njMzDMNrNLG9Ways+QPhX99gcP7nlpMfYc5qomUeBcH HSznvraamzHJODx+e3itnlckA+uBdgRcT7aToZ2tjF+jYgyu/R7R3rU6xGxlS1ouhxGJbG3bFXw7 XLdxXXxtWM1hFlMJM80GZdCyftM9elwTw2vf+9WlOGnHtFNKlGnkjM7jjUKpvrRqxFX46izD2KIs lt+W85UIhjAgH2xuU6arULSu7OpXMW9Eykxeob0GR5YzwBdd3gJ86MEkRdqYe27sePfciSj/j4zD 8P8DHqWKn7Xx9QBdRUaQxk7gBSEFucKRofPTO6nLi6ArAcqvQYrZTlVt5svFCwXEwEOXFtTyGU5h tariH8G9RYODgjkjo+t9L+IFi6epgQfgEHVmf9W0quB5q2ociOkQWMG4s/hhdLnv7FB0NvJ1kBGL IXEFmKXb2vUmh5M20xNoG5PGIPpATxOyiGXn5AZTrErSUfo+9qbs9tNA6qz9Fia7Y59VwMHXUTGO vwM= =FHEO -----END PGP SIGNATURE----- --bjkR96Rl37SlEUWAAWUHSJZAsqDaYUsWd-- From owner-freebsd-current@freebsd.org Wed Jan 20 14:17:38 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A51CB4F7196 for ; Wed, 20 Jan 2021 14:17:38 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DLSKG38dNz4mj8 for ; Wed, 20 Jan 2021 14:17:38 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 6A7084F7385; Wed, 20 Jan 2021 14:17:38 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6A35C4F7384 for ; Wed, 20 Jan 2021 14:17:38 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLSKF5LfBz4mVl for ; Wed, 20 Jan 2021 14:17:37 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io1-xd2d.google.com with SMTP id z22so20446325ioh.9 for ; Wed, 20 Jan 2021 06:17:37 -0800 (PST) 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 :content-transfer-encoding:in-reply-to; bh=OPAu87kLA40E4nzXq0tmDeIX5L9ecdeyHtQyLPkfUgg=; b=Zx57LlQWfkBX46UFYeaL9n842VuqFAYivDM7CLATZBWVy1kGAKvmYa0hU7ejitpOes VkbqYUhRrrUywJjubGA8XUdrVs1WHwFR0qxa8jOmJ3DqLz634vQEahO5bZiXm4TFdwTt bexA81TXZWWK5B/LdA+ol1W57+PltIgwmlRwudmCwV+WCmRtJQQO28H22+FxaYN5oNBS fACCPNYv05ZJ4HyhNt4mgnW9V1d/btc4lBPUcDCaI+XdFNPKNUjHqLlGwCNkq91VITnS 1Tk7nqIL+7e9RJRGL55QPsydVuVwW32zYdCETqXsjoFIm1mxgpLzU6V2el7QigUj3wcl pBtQ== X-Gm-Message-State: AOAM53369eGtQI4KXHYIoDhgG6Z8FPR9K/YbUeIWpvBuRwIr5KOw+QuC Eu62jQf/HHdbEUMh5tpYUctURTzQNZW3TA== X-Google-Smtp-Source: ABdhPJxAEbrenolO0vJEnxX3j3Tza+wSDfqIF3Wwc4SfLy9dzPLVS3g3gP/O/wPKcyoQe7U3O8jTGw== X-Received: by 2002:a05:6e02:b47:: with SMTP id f7mr7741156ilu.96.1611152256588; Wed, 20 Jan 2021 06:17:36 -0800 (PST) Received: from raichu ([142.126.164.150]) by smtp.gmail.com with ESMTPSA id y19sm505467ilk.35.2021.01.20.06.17.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Jan 2021 06:17:35 -0800 (PST) Sender: Mark Johnston Date: Wed, 20 Jan 2021 09:17:33 -0500 From: Mark Johnston To: Santiago Martinez Cc: FreeBSD Current Subject: Re: VM UMA counters. Message-ID: References: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> X-Rspamd-Queue-Id: 4DLSKF5LfBz4mVl X-Spamd-Bar: / X-Spamd-Result: default: False [-0.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::d2d:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::d2d:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d2d:from]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:17:38 -0000 On Tue, Jan 19, 2021 at 12:44:14PM +0000, Santiago Martinez wrote: > Hi there, sorry to ask this as it might be a silly question... > > Since a few weeks im seeing random locks on application and sometimes > when using truss it show resource temporally unavailable. > > Now, checking random things, i see that the > vm.uma.256_Bucket.stats.fails counter is increasing while the other are > not (at least for now). > > Here goes the output: > > vm.uma.256_Bucket.stats.xdomain: 0 > vm.uma.256_Bucket.stats.fails: 762142 > vm.uma.256_Bucket.stats.frees: 41935 > vm.uma.256_Bucket.stats.allocs: 42721 > vm.uma.256_Bucket.stats.current: 786 > > root@tucho:/home/smartinez # uname -a > FreeBSD tucho 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #13 > main-c256107-g7d3310c4fcdd: Tue Jan 19 10:50:12 GMT 2021     > smartinez@tucho:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG  amd64 > > My question is, is this the expected behavior? There are situations where bucket allocations must fail to avoid recursing back into the VM. For instance, allocation of a UMA slab may require allocation of a radix node entry from UMA, which may attempt allocation of a bucket, which could trigger allocation of a slab. It's therefore normal to see a non-zero number of failures after booting, but after that the bucket zone's caches are populated and failures should become rare. Failures might also be triggered during severe memory shortages. Could you show vmstat -s from an affected system? Are you using any DRM graphics drivers by any chance? From owner-freebsd-current@freebsd.org Wed Jan 20 14:22:23 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2EA714F753F for ; Wed, 20 Jan 2021 14:22:23 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailout03.eigbox.net (bosmailout03.eigbox.net [66.96.186.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLSQk468Pz4nGv for ; Wed, 20 Jan 2021 14:22:22 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailscan05.eigbox.net ([10.20.15.5]) by bosmailout03.eigbox.net with esmtp (Exim) id 1l2ENK-0008Pj-2p for freebsd-current@freebsd.org; Wed, 20 Jan 2021 09:22:22 -0500 Received: from [10.115.3.31] (helo=bosimpout11) by bosmailscan05.eigbox.net with esmtp (Exim) id 1l2ENJ-0005qL-QF for freebsd-current@freebsd.org; Wed, 20 Jan 2021 09:22:21 -0500 Received: from bosauthsmtp03.yourhostingaccount.com ([10.20.18.3]) by bosimpout11 with id K2NJ2401003yW76012NMot; Wed, 20 Jan 2021 09:22:21 -0500 X-Authority-Analysis: v=2.3 cv=DtjNBF3+ c=1 sm=1 tr=0 a=6uKCkKhFq2wXOH2GoQX8aA==:117 a=BXB5eCltbCg0Q+nSw1Bwcw==:17 a=EmqxpYm9HcoA:10 a=jXMol9EDn2QA:10 a=13zjGPudsaEWiJwPRgMA:9 a=6I5d2MoRAAAA:8 a=ir_SxBTIcT3EMyWmvfQA:9 a=QEXdDO2ut3YA:10 a=kDb1y1on7dRCu8Z9Cl4A:9 a=FfaGCDsud1wA:10 a=IjZwj45LgO3ly-622nXo:22 Received: from cm-81-9-160-236.telecable.es ([81.9.160.236]:44872 helo=[192.168.1.100]) by bosauthsmtp03.eigbox.net with esmtpa (Exim) id 1l2ENG-0003Kv-K3 for freebsd-current@freebsd.org; Wed, 20 Jan 2021 09:22:18 -0500 Subject: Re: Waiting for bufdaemon From: Santiago Martinez To: freebsd-current@freebsd.org References: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> Message-ID: <9d2858a4-8036-0b0d-90fe-115bfe267409@codenetworks.net> Date: Wed, 20 Jan 2021 14:22:16 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="w2sUocPzL4UmedI0KuzAv56idb7eoBsMZ" X-EN-UserInfo: d3bdfab0736480cedf04ed92aaea2ef5:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: sm@codenetworks.net Sender: Santiago Martinez X-EN-OrigIP: 81.9.160.236 X-EN-OrigHost: cm-81-9-160-236.telecable.es X-Rspamd-Queue-Id: 4DLSQk468Pz4nGv X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.96.128.0/18:c]; HAS_ATTACHMENT(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[codenetworks.net:~]; SIGNED_PGP(-2.00)[]; FORGED_SENDER(0.30)[sm@codenetworks.net,SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net]; RECEIVED_SPAMHAUS_PBL(0.00)[81.9.160.236:received]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[66.96.186.3:from]; ASN(0.00)[asn:29873, ipnet:66.96.128.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[sm@codenetworks.net,SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; DMARC_NA(0.00)[codenetworks.net: no valid DMARC record]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[66.96.186.3:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[66.96.186.3:from]; R_DKIM_PERMFAIL(0.00)[codenetworks.net:s=dkim]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.96.186.3:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:22:23 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --w2sUocPzL4UmedI0KuzAv56idb7eoBsMZ Content-Type: multipart/mixed; boundary="SfxMYtCuFiSQjBhv0UEkcmut1kSOAUkmb"; protected-headers="v1" From: Santiago Martinez To: freebsd-current@freebsd.org Message-ID: <9d2858a4-8036-0b0d-90fe-115bfe267409@codenetworks.net> Subject: Re: Waiting for bufdaemon References: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> In-Reply-To: --SfxMYtCuFiSQjBhv0UEkcmut1kSOAUkmb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hi, excellent the patch clear the problem for me when rebooting after a kern compile, etc, etc. Also seems that Firefox and pycharm or any other java related tools are not freezing any more, but its maybe to early to confirm this 100%. Will keep you posted. Santiago On 1/20/21 1:58 PM, Santiago Martinez wrote: > Hi Everyone, i have exactly the same behavior as Rainer described. > > "After a high system load, several programs only react very slowly (e.g= =2E > Firefox)......" > > I will try with the patch and see if it also clear this on my machine > (AMD R7). > > Santiago > > > On 1/20/21 1:52 PM, Konstantin Belousov wrote: >> On Wed, Jan 20, 2021 at 02:35:59PM +0100, Rainer Hurling wrote: >>> Am 20.01.21 um 14:12 schrieb Konstantin Belousov: >>>> On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: >>>>> Am 20.01.21 um 13:34 schrieb Konstantin Belousov: >>>>>> On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: >>>>>>> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: >>>>>>>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote:= >>>>>>>>> This patch hides the problem for me. The system seems to work b= etter now. >>>>>>>>> >>>>>>>>> No waiting on reboot, and the webcam works better. >>>>>>>> I am curious what do you mean by the above reference to webcam. >>>>>>>> Can you explain it with more details, even if only the impressio= ns? >>>>>>> I should mention, that beside the already discussed timing proble= m with >>>>>>> bufdaemon, I also have problems with several apps: >>>>>>> >>>>>>> >>>>>>> After a high system load, several programs only react very slowly= (e.g. >>>>>>> Firefox). Several dockable apps from WindowMaker, but also e.g. c= onky do >>>>>>> not update their windows anymore, they freeze. After some time, F= irefox >>>>>>> updates its screen content only after switching back from another= window ... >>>>>>> >>>>>>> When such frozen programs are killed and restarted, they run norm= ally >>>>>>> again for an indefinite time before they freeze again. >>>>>>> >>>>>>> These symptoms completely disappeared, after I patched the Ryzen = box as >>>>>>> suggested on 01/17: >>>>>> Do you load latest microcode update from devcpu-data? >>>>> Yes, sysutils/devcpu-data is installed and the following to lines a= re in >>>>> /boot/loader.conf >>>>> >>>>> cpu_microcode_load=3D"YES" >>>>> cpu_microcode_name=3D"/boot/firmware/intel-ucode.bin" >>>>> >>>>> But isn't this just for Intel (i387 and amd64), not AMD cpus? >>>> You need microcode_update_enable=3D"YES" in /etc/rc.conf for late mi= crocode >>>> update. >>>> >>>> I think that early boot update should work on AMD, bit for this you = need to >>>> select and put right blob. It is enough to load late to answer my q= uestion. >>> Ah, ok. Thanks for clarification. I also put cpu_microcode_load=3D"YE= S" in >>> /etc/rc.conf for a late update. >>> >>> Should I try again without your patch of sys/x86/tsc.c, whether the >>> problem still occurs? >> Yes. >> >>> And for the early boot update, how do I know about the right blob? >> I am not aware of the mechanism. My best suggestion is that you match= >> the blob against your CPU family/model id manually. >> >>>>>> It might be not enough, which means that additionally latest BIOS = needs >>>>>> to be flushed. >>>>>> >>>>> I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite= " >>>>> mainboard. >> _______________________________________________ >> 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" --SfxMYtCuFiSQjBhv0UEkcmut1kSOAUkmb-- --w2sUocPzL4UmedI0KuzAv56idb7eoBsMZ Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEk06QWJzNAs9NTrFjWBFqYkyC55EFAmAIPJgFAwAAAAAACgkQWBFqYkyC55ES tg/+NMU8gixr5RFE959o87TtIYxmBSCCO+IWDz73JQIOaQwKCMFtpdWZKbokEu16X2DFUEmjSqLS m3wJNbTcnSeIopF6drRDlxwN7wzTiGE0vUOXwZ+c5AdTK655xmIxQu80Mv4esD2mrWssXyczG42j 6gHKia+b1iFWZ67AxLVLi4ASIr4XPovt0stDx3L0TEV9sQG0/8yG32mI5g7/Z7UBIrKyQGysiBGn zHrGZbWiWL2G4GQrgTHAsg/erGnFMROIO8fNrFjZGALQEUt/pKKKVdyieAk1GlKNs1qM5pfYzHOd E4DtCohPKcgYVpmnq0VYhamYKDtClwwRuxjPa3os267RRTzoZZscYRn7iJaV4G5PmBJSlm9xdxkD ba2oQMO/KH73vERbiJEZfU8SH8AzpNKn4yBFwuKMISNGD8hddj+DaKA40mocsQNqrXbbWwfIIFeL DciUHARz/0bzi3qnbNF+NJSiR/gsh5L0SvoZNbPATl5g1cX29YTGgSQ9PKliXdCDowxsTUNp+CWP w8DWaTnjxpNoAvWBUo0PqvWSuF5f+K2BeVwb7WGmKEIlv9A7Vd0XcO/Oo13x6co7QymaPz6ICIsb 3ZY4EKCK2DfenzIufKE165nyJZCtgjRe9WEzpPn2+ef8AX4nLSeSrw9R/c7Ulvcv45jIQQOR8UYF /yU= =vjQg -----END PGP SIGNATURE----- --w2sUocPzL4UmedI0KuzAv56idb7eoBsMZ-- From owner-freebsd-current@freebsd.org Wed Jan 20 14:25:07 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3B9314F798E for ; Wed, 20 Jan 2021 14:25:07 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DLSTt72xYz4nrK for ; Wed, 20 Jan 2021 14:25:06 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: by mailman.nyi.freebsd.org (Postfix) id F1BF14F76CF; Wed, 20 Jan 2021 14:25:06 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F18454F7910 for ; Wed, 20 Jan 2021 14:25:06 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailout08.eigbox.net (bosmailout08.eigbox.net [66.96.186.8]) (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 4DLSTt60xCz4nP7; Wed, 20 Jan 2021 14:25:06 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailscan06.eigbox.net ([10.20.15.6]) by bosmailout08.eigbox.net with esmtp (Exim) id 1l2EPy-0000gP-KD; Wed, 20 Jan 2021 09:25:06 -0500 Received: from [10.115.3.33] (helo=bosimpout13) by bosmailscan06.eigbox.net with esmtp (Exim) id 1l2EPy-0003LR-Bz; Wed, 20 Jan 2021 09:25:06 -0500 Received: from bosauthsmtp03.yourhostingaccount.com ([10.20.18.3]) by bosimpout13 with id K2R32400i03yW76012R6d2; Wed, 20 Jan 2021 09:25:06 -0500 X-Authority-Analysis: v=2.3 cv=Ep1JURUA c=1 sm=1 tr=0 a=6uKCkKhFq2wXOH2GoQX8aA==:117 a=BXB5eCltbCg0Q+nSw1Bwcw==:17 a=EmqxpYm9HcoA:10 a=jXMol9EDn2QA:10 a=13zjGPudsaEWiJwPRgMA:9 a=6I5d2MoRAAAA:8 a=mcNz9rVCXS-7ZG6B7XkA:9 a=QEXdDO2ut3YA:10 a=VnHsSu0nTgry8A9KpFQA:9 a=FfaGCDsud1wA:10 a=IjZwj45LgO3ly-622nXo:22 Received: from cm-81-9-160-236.telecable.es ([81.9.160.236]:12469 helo=[192.168.1.100]) by bosauthsmtp03.eigbox.net with esmtpa (Exim) id 1l2EPv-0006Q5-0f; Wed, 20 Jan 2021 09:25:03 -0500 Subject: Re: VM UMA counters. To: Mark Johnston Cc: FreeBSD Current References: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> From: Santiago Martinez Message-ID: Date: Wed, 20 Jan 2021 14:24:59 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wLJrgnzXsGxIObZ6XKZ6u4FUHXC4LrPv4" X-EN-UserInfo: d3bdfab0736480cedf04ed92aaea2ef5:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: sm@codenetworks.net Sender: Santiago Martinez X-EN-OrigIP: 81.9.160.236 X-EN-OrigHost: cm-81-9-160-236.telecable.es X-Rspamd-Queue-Id: 4DLSTt60xCz4nP7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:25:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wLJrgnzXsGxIObZ6XKZ6u4FUHXC4LrPv4 Content-Type: multipart/mixed; boundary="ibvo0trIwLDH5ENDDYf0mrB1y47r3bhbf"; protected-headers="v1" From: Santiago Martinez To: Mark Johnston Cc: FreeBSD Current Message-ID: Subject: Re: VM UMA counters. References: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> In-Reply-To: --ibvo0trIwLDH5ENDDYf0mrB1y47r3bhbf Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hi Mark, To the DRM question, indeed I am using drm-devel with amdgpu. Here is the vmstat -s output. Cheers Santiago root@tucho:/home/smartinez # vmstat -s 1882578 cpu context switches 100445 device interrupts 23777 software interrupts 1054356 traps 13811750 system calls 39 kernel threads created 1398=C2=A0 fork() calls 343 vfork() calls 84 rfork() calls 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 12579 vnode pager pageins 138821 vnode pager pages paged in 4 vnode pager pageouts 37 vnode pager pages paged out 0 page daemon wakeups 160056 pages examined by the page daemon 0 clean page reclamation shortfalls 0 pages reactivated by the page daemon 194549 copy-on-write faults 190 copy-on-write optimized faults 697804 zero fill pages zeroed 0 zero fill pages prezeroed 2559 intransit blocking page faults 1018606 total VM faults taken 12262 page faults requiring I/O 0 pages affected by kernel thread creation 138718 pages affected by=C2=A0 fork() 12177 pages affected by vfork() 14704 pages affected by rfork() 746501 pages freed 0 pages freed by daemon 338813 pages freed by exiting processes 418069 pages active 200941 pages inactive 1123 pages in the laundry queue 513309 pages wired down 32 virtual user pages wired down 7003759 pages free 4096 bytes per page 4311229 total name lookups cache hits (94% pos + 2% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% On 1/20/21 2:17 PM, Mark Johnston wrote: > On Tue, Jan 19, 2021 at 12:44:14PM +0000, Santiago Martinez wrote: >> Hi there, sorry to ask this as it might be a silly question... >> >> Since a few weeks im seeing random locks on application and sometimes >> when using truss it show resource temporally unavailable. >> >> Now, checking random things, i see that the >> vm.uma.256_Bucket.stats.fails counter is increasing while the other ar= e >> not (at least for now). >> >> Here goes the output: >> >> vm.uma.256_Bucket.stats.xdomain: 0 >> vm.uma.256_Bucket.stats.fails: 762142 >> vm.uma.256_Bucket.stats.frees: 41935 >> vm.uma.256_Bucket.stats.allocs: 42721 >> vm.uma.256_Bucket.stats.current: 786 >> >> root@tucho:/home/smartinez # uname -a >> FreeBSD tucho 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #13 >> main-c256107-g7d3310c4fcdd: Tue Jan 19 10:50:12 GMT 2021=C2=A0=C2=A0=C2= =A0=C2=A0 >> smartinez@tucho:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG=C2=A0= amd64 >> >> My question is, is this the expected behavior? > There are situations where bucket allocations must fail to avoid > recursing back into the VM. For instance, allocation of a UMA slab may= > require allocation of a radix node entry from UMA, which may attempt > allocation of a bucket, which could trigger allocation of a slab. > > It's therefore normal to see a non-zero number of failures after > booting, but after that the bucket zone's caches are populated and > failures should become rare. Failures might also be triggered during > severe memory shortages. Could you show vmstat -s from an affected > system? Are you using any DRM graphics drivers by any chance? > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" --ibvo0trIwLDH5ENDDYf0mrB1y47r3bhbf-- --wLJrgnzXsGxIObZ6XKZ6u4FUHXC4LrPv4 Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEk06QWJzNAs9NTrFjWBFqYkyC55EFAmAIPTsFAwAAAAAACgkQWBFqYkyC55Fb mA//UD0w4Jo4TIkbeXN0vkT3nC8XonNSGfeoAdE7PaUBV/MJQYDBKAY/g4aHAH1J/SX3BCRMN7J0 v9r+Uhpbpr2DR/o4EqCyhGIzU/8CO97FDPqNgMJln4jnDHUsYeTDmLnwCJ9FWUPckqaAGlUf7xAk bnswFHcKjhCp0rdLwBxCjWnJsrIC3+RY1DRaOQ9pi5ceWvOvYLf+SlfHuTi6HmEwT4tjsVBdDdDS 0J9BIlyMgVR7p5EOCx7DfOl8jA1oY10zqaj2zQcOZ+3KpY1vBNj57iMOuDF+H+N1+uSHkuiyhsnS 5wrd5MfKQisZIqYbfbVki/6dZBqyxhs5gErfiUq3SKNV48XI2Esz42CWc5EmZ1rO0PoJM7guE2JY NMy0EVLGTwIsPwF/MqQ67Ka3oOsyXz+K3Vz7KvYRWuM/SrVLvEcNjHMU/fYoghPg6gPjY/+YMqfm oV5F85a/WR9ZXVWpIIOJuSbSjjgv+Udx9merXEwkM0sQkD9xBBna1xbpc63bdziY1EVOp6o/jqS7 h7mQXpeUme7lji3ee9FDE2QQOPPrNnKa+ozdbvWjS1AbD/2y2OW3GcKEodCUCqMgfn5BBes1PCig XuJ0CstmKgBA2vEcZZDWUOgRQREVmdq1N7+ZULyDWZxpWSc23GhkH03H7QAOAVO7X5fGQ9KPeKOz CIQ= =wzNt -----END PGP SIGNATURE----- --wLJrgnzXsGxIObZ6XKZ6u4FUHXC4LrPv4-- From owner-freebsd-current@freebsd.org Wed Jan 20 14:30:42 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4ACD84F7A50 for ; Wed, 20 Jan 2021 14:30:42 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DLScL0mZKz4p91 for ; Wed, 20 Jan 2021 14:30:42 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 187FD4F7AFC; Wed, 20 Jan 2021 14:30:42 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 184424F7A4F for ; Wed, 20 Jan 2021 14:30:42 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLScL00Q3z4nyZ for ; Wed, 20 Jan 2021 14:30:41 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qv1-xf34.google.com with SMTP id l14so10944634qvh.2 for ; Wed, 20 Jan 2021 06:30:41 -0800 (PST) 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; bh=qSpQ2mfBe80nd4hDJ930X36767bJVb/vgvBy0nVNAnU=; b=Ch+EZNtIdYARO7jOp0o9BP0TxxEQBg5AxNS40e+pKKTBKwKNQG+clDaqpBx9jg1p6J UStf/OnZJgkDnddirTtw9+UEAzMLtulrmbYOSZrSClJmc6+DZ4z7u72W1H9fEZFbdxtU gH0/FBX+rsVp0nkpXMXl9VetilPYNT3XW3QCZbVIREzt8O0vNUcD4PdpIG7BQ0hkVajP G/6Gjzmaa6Pt05F53hJhAiJ09asIsCmjW3FRQNMBzO0K2DNin2esyPhNd734VQr9GHy+ ioH8frk98ZYd8Fx709kAIgIyh8aKl2SXAYd3o71J4qCyrBg7TJME1hEQ5tVF/Rq9KqfE cMGw== X-Gm-Message-State: AOAM532+BemOKk0rmzn4+4eFMtVImAYtkPrxNdBGi9H1Yvn2o37jFsLg H9HFq2NjvtP6kOel6OBPTfwXg4roDfbSlg== X-Google-Smtp-Source: ABdhPJz2oVy6xqe3BEfPS/fVv4+aWa1m7QhRKOmSr0tvVEgyZEaz/EmDETER/OYDPOLg83F6nUq0mQ== X-Received: by 2002:a0c:e7cb:: with SMTP id c11mr9519246qvo.19.1611153041035; Wed, 20 Jan 2021 06:30:41 -0800 (PST) Received: from raichu ([142.126.164.150]) by smtp.gmail.com with ESMTPSA id a17sm1239051qto.27.2021.01.20.06.30.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Jan 2021 06:30:40 -0800 (PST) Sender: Mark Johnston Date: Wed, 20 Jan 2021 09:30:38 -0500 From: Mark Johnston To: Santiago Martinez Cc: FreeBSD Current Subject: Re: VM UMA counters. Message-ID: References: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4DLScL00Q3z4nyZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:30:42 -0000 On Wed, Jan 20, 2021 at 02:24:59PM +0000, Santiago Martinez wrote: > Hi Mark, > > To the DRM question, indeed I am using drm-devel with amdgpu. Have you updated to commit 4af932354260 or later? That helps address a memory reclamation bug triggered by amdgpu. > Here is the vmstat -s output. I guess this is from a fresh boot? It would be most useful to see vmstat -s output taken at a time when the number of bucket allocation failures is also increasing. But, please try updating first to see if the lockups persist. From owner-freebsd-current@freebsd.org Wed Jan 20 14:34:36 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6438C4F7F37 for ; Wed, 20 Jan 2021 14:34:36 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DLShr1Kh1z4pVj for ; Wed, 20 Jan 2021 14:34:36 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: by mailman.nyi.freebsd.org (Postfix) id 2BD214F7CCD; Wed, 20 Jan 2021 14:34:36 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2B9724F7D57 for ; Wed, 20 Jan 2021 14:34:36 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailout03.eigbox.net (bosmailout03.eigbox.net [66.96.186.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLShr0PGKz4pR1; Wed, 20 Jan 2021 14:34:35 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailscan06.eigbox.net ([10.20.15.6]) by bosmailout03.eigbox.net with esmtp (Exim) id 1l2EZ9-0006tU-E7; Wed, 20 Jan 2021 09:34:35 -0500 Received: from [10.115.3.31] (helo=bosimpout11) by bosmailscan06.eigbox.net with esmtp (Exim) id 1l2EZ9-0006DE-33; Wed, 20 Jan 2021 09:34:35 -0500 Received: from bosauthsmtp03.yourhostingaccount.com ([10.20.18.3]) by bosimpout11 with id K2aY2400303yW76012abqm; Wed, 20 Jan 2021 09:34:35 -0500 X-Authority-Analysis: v=2.3 cv=DtjNBF3+ c=1 sm=1 tr=0 a=6uKCkKhFq2wXOH2GoQX8aA==:117 a=BXB5eCltbCg0Q+nSw1Bwcw==:17 a=EmqxpYm9HcoA:10 a=jXMol9EDn2QA:10 a=13zjGPudsaEWiJwPRgMA:9 a=6I5d2MoRAAAA:8 a=p5eWsvob15OsZAG3Cj0A:9 a=QEXdDO2ut3YA:10 a=JFuCmry13DhIKbAXGtQA:9 a=FfaGCDsud1wA:10 a=IjZwj45LgO3ly-622nXo:22 Received: from cm-81-9-160-236.telecable.es ([81.9.160.236]:24756 helo=[192.168.1.100]) by bosauthsmtp03.eigbox.net with esmtpa (Exim) id 1l2EZ5-0007sp-UW; Wed, 20 Jan 2021 09:34:32 -0500 Subject: Re: VM UMA counters. To: Mark Johnston Cc: FreeBSD Current References: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> From: Santiago Martinez Message-ID: <49ec694a-7215-c28b-8372-56343df8e30c@codenetworks.net> Date: Wed, 20 Jan 2021 14:34:28 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yAIOT2Z2wMkqdm5oNc9PsHupFLrKNzg7B" X-EN-UserInfo: d3bdfab0736480cedf04ed92aaea2ef5:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: sm@codenetworks.net Sender: Santiago Martinez X-EN-OrigIP: 81.9.160.236 X-EN-OrigHost: cm-81-9-160-236.telecable.es X-Rspamd-Queue-Id: 4DLShr0PGKz4pR1 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:34:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --yAIOT2Z2wMkqdm5oNc9PsHupFLrKNzg7B Content-Type: multipart/mixed; boundary="Qlojj3F4F1jyarkuHpKgZSGaadQ2sIQYd"; protected-headers="v1" From: Santiago Martinez To: Mark Johnston Cc: FreeBSD Current Message-ID: <49ec694a-7215-c28b-8372-56343df8e30c@codenetworks.net> Subject: Re: VM UMA counters. References: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> In-Reply-To: --Qlojj3F4F1jyarkuHpKgZSGaadQ2sIQYd Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US yes that correct, just booted with the patch applied for the bufdaemon . Will keep an eye on it, and let you know how it goes. Any specific values that i should look on vmstat? Santiago On 1/20/21 2:30 PM, Mark Johnston wrote: > On Wed, Jan 20, 2021 at 02:24:59PM +0000, Santiago Martinez wrote: >> Hi Mark, >> >> To the DRM question, indeed I am using drm-devel with amdgpu. > Have you updated to commit 4af932354260 or later? That helps address a= > memory reclamation bug triggered by amdgpu. > >> Here is the vmstat -s output. > I guess this is from a fresh boot? It would be most useful to see=20 > vmstat -s output taken at a time when the number of bucket allocation > failures is also increasing. But, please try updating first to see if > the lockups persist. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" --Qlojj3F4F1jyarkuHpKgZSGaadQ2sIQYd-- --yAIOT2Z2wMkqdm5oNc9PsHupFLrKNzg7B Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEk06QWJzNAs9NTrFjWBFqYkyC55EFAmAIP3QFAwAAAAAACgkQWBFqYkyC55Fy cg//Qf/nsG3bxVWDDTc7VkJZeMcROnff+eOHCozLY5cBeaQzGJBxfynGuQ79aV/HicN/ITex1dDJ 8kWQHz4u21yfA8y73a7JMfv0FId5mhz3M11xiqsYxQffKxr5cMWF9E3RV+mfVKumFrzNu1l+CuLK C6E0h6bFVqCeZNWeQ5Z4zq638FbrwLoqc8zKin8XTVXL7F8TXGcVzCHBGfgB9tbMj/li4bgGV+uB aR3h/thirallCKMo7quBOplICvVECuIom8/Awvj7swfxDoVBedf42og3s65AHyNRS/q674C+wOtr AkwTTl5NOE8q3/mIiXH80qhrgXurLf3xgnjAtaYazFo28+QLVw/5BA1bmiqxF+ejictSGjtYraDJ RiwoobQ9jECMN5sarAlOW7CzcdECUKLG4BJeOcpvaxD8azRXi7XDvMk8O91tPD1UTLh1cVM1kbHE dOpGQzU31nqi8uczM55+Zx6PUBCs1lOUYwOesH+Cl6hSgaqALO41yyhwxs+6bN4zVk+bbCKP1bpP Ik4AwljmIE5NWcO6YOAwMeN/uPaqD0I5GQj2XyzuFJB+XChANTVEYhPhQ2XQJCm1brEUU1PWOYby DBC0z0SyEemNAvauiDYZzhza97F5mzJJEIWuz4Nkq78mskky8uERxrBOq9xelekLEFDPvGlUS3sQ xOo= =zhZX -----END PGP SIGNATURE----- --yAIOT2Z2wMkqdm5oNc9PsHupFLrKNzg7B-- From owner-freebsd-current@freebsd.org Wed Jan 20 14:36:49 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 47F384F8044 for ; Wed, 20 Jan 2021 14:36:49 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4DLSlP1ddZz4q4j for ; Wed, 20 Jan 2021 14:36:48 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-03.um.gwdg.de ([134.76.9.218] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1l2EbH-00086v-2z; Wed, 20 Jan 2021 15:36:47 +0100 Received: from krabat.raven.hur (10.250.9.200) by EXCMBX-03.um.gwdg.de (134.76.9.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.2044.4; Wed, 20 Jan 2021 15:36:46 +0100 Subject: Re: Waiting for bufdaemon To: Konstantin Belousov CC: freebsd-current References: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> Reply-To: From: Rainer Hurling Message-ID: Date: Wed, 20 Jan 2021 15:36:26 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.200] X-ClientProxiedBy: excmbx-08.um.gwdg.de (134.76.9.215) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4DLSlP1ddZz4q4j X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:36:49 -0000 Am 20.01.21 um 14:52 schrieb Konstantin Belousov: > On Wed, Jan 20, 2021 at 02:35:59PM +0100, Rainer Hurling wrote: >> Am 20.01.21 um 14:12 schrieb Konstantin Belousov: >>> On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: >>>> Am 20.01.21 um 13:34 schrieb Konstantin Belousov: >>>>> On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: >>>>>> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: >>>>>>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >>>>>>>> This patch hides the problem for me. The system seems to work better now. >>>>>>>> >>>>>>>> No waiting on reboot, and the webcam works better. >>>>>>> I am curious what do you mean by the above reference to webcam. >>>>>>> Can you explain it with more details, even if only the impressions? >>>>>> >>>>>> I should mention, that beside the already discussed timing problem with >>>>>> bufdaemon, I also have problems with several apps: >>>>>> >>>>>> >>>>>> After a high system load, several programs only react very slowly (e.g. >>>>>> Firefox). Several dockable apps from WindowMaker, but also e.g. conky do >>>>>> not update their windows anymore, they freeze. After some time, Firefox >>>>>> updates its screen content only after switching back from another window ... >>>>>> >>>>>> When such frozen programs are killed and restarted, they run normally >>>>>> again for an indefinite time before they freeze again. >>>>>> >>>>>> These symptoms completely disappeared, after I patched the Ryzen box as >>>>>> suggested on 01/17: >>>>> >>>>> Do you load latest microcode update from devcpu-data? >>>> >>>> Yes, sysutils/devcpu-data is installed and the following to lines are in >>>> /boot/loader.conf >>>> >>>> cpu_microcode_load="YES" >>>> cpu_microcode_name="/boot/firmware/intel-ucode.bin" >>>> >>>> But isn't this just for Intel (i387 and amd64), not AMD cpus? >>> You need microcode_update_enable="YES" in /etc/rc.conf for late microcode >>> update. >>> >>> I think that early boot update should work on AMD, bit for this you need to >>> select and put right blob. It is enough to load late to answer my question. >> >> Ah, ok. Thanks for clarification. I also put cpu_microcode_load="YES" in >> /etc/rc.conf for a late update. >> >> Should I try again without your patch of sys/x86/tsc.c, whether the >> problem still occurs? Unfornately, without the patch from 01/17 the problem is _not_ solved. Next I will try your patch from today, f lib/libc/x86/sys/__vdso_gettc.c an lib/libc/x86/sys/__vdso_gettc.c ... > Yes. > >> >> >> And for the early boot update, how do I know about the right blob? > I am not aware of the mechanism. My best suggestion is that you match > the blob against your CPU family/model id manually. > >> >>> >>>> >>>>> It might be not enough, which means that additionally latest BIOS needs >>>>> to be flushed. >>>>> >>>> >>>> I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite" >>>> mainboard. From owner-freebsd-current@freebsd.org Wed Jan 20 14:39:59 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7BCF04F8269 for ; Wed, 20 Jan 2021 14:39:59 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DLSq32853z4q6n for ; Wed, 20 Jan 2021 14:39:59 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 47DA74F8268; Wed, 20 Jan 2021 14:39:59 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 47A074F81E3 for ; Wed, 20 Jan 2021 14:39:59 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLSq31KZ7z4qBl for ; Wed, 20 Jan 2021 14:39:59 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk1-x730.google.com with SMTP id n142so25535280qkn.2 for ; Wed, 20 Jan 2021 06:39:59 -0800 (PST) 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; bh=xt7ou37e5gILIkEZW2TQwVDbzXD60G9Flh4yca33dmc=; b=Co2gpzch397id1KUtlKD1VOGoI+CGIU6KC7Pc3z1zTJhTD61iFfL8d50eylHcHPjOt kNK+jbHSSX2CEinbQnI1L4qsN8Jo7d34VOh6m+Xi91oEhDBXgZ6hAp7D8hihaiCSCq2l 9J+tcRYb6cmRyZcVJlDiLN/4dOUp8r/2BWMil9rDQmi+5hwhpe26qMk5GMlSejpGroAA qIAPCBQQ3dF8+iiWdc8AzeyXhe34JCzeXbpn7OZ2rSCwqxNb60EsCBy9b0X2oonINIED ZwhezaZIUHwDYavKzRDm+XrBJAPxYId8NqAKKm0lQAMhtV6NqUxV89ecbv2aJm6fyxwY xCug== X-Gm-Message-State: AOAM533BHDgXP4rJ4rdOqLakmCHqm9vAu/S6FY+mhHwaaPDAFU6RTH+G Kg20KdOTcpbd84FoGsY0/8tYIOhbjhgxsQ== X-Google-Smtp-Source: ABdhPJyTrpBzGR9zOrB4/bcBi0+KPVVPoERwhuAVbd8fBjaP1mZgzU8FtClgv/F9aMb2dQEjXCwjoQ== X-Received: by 2002:a37:be84:: with SMTP id o126mr5858758qkf.138.1611153598373; Wed, 20 Jan 2021 06:39:58 -0800 (PST) Received: from raichu ([142.126.164.150]) by smtp.gmail.com with ESMTPSA id j27sm428637qtc.41.2021.01.20.06.39.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Jan 2021 06:39:57 -0800 (PST) Sender: Mark Johnston Date: Wed, 20 Jan 2021 09:39:55 -0500 From: Mark Johnston To: Santiago Martinez Cc: FreeBSD Current Subject: Re: VM UMA counters. Message-ID: References: <0996195a-6d7f-b058-e95c-b2446688940f@codenetworks.net> <49ec694a-7215-c28b-8372-56343df8e30c@codenetworks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49ec694a-7215-c28b-8372-56343df8e30c@codenetworks.net> X-Rspamd-Queue-Id: 4DLSq31KZ7z4qBl X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:39:59 -0000 On Wed, Jan 20, 2021 at 02:34:28PM +0000, Santiago Martinez wrote: > yes that correct, just booted with the patch applied for the bufdaemon . > > Will keep an eye on it, and let you know how it goes. > > Any specific values that i should look on vmstat? The ones I'm interested in are: 0 page daemon wakeups 160056 pages examined by the page daemon 0 clean page reclamation shortfalls 0 pages reactivated by the page daemon 0 pages freed by daemon In particular I wanted to see if any clean page reclamation shortfalls had occurred, since that indicates a severe free memory shortage which could be responsible for UMA allocation failures. > > On 1/20/21 2:30 PM, Mark Johnston wrote: > > On Wed, Jan 20, 2021 at 02:24:59PM +0000, Santiago Martinez wrote: > >> Hi Mark, > >> > >> To the DRM question, indeed I am using drm-devel with amdgpu. > > Have you updated to commit 4af932354260 or later? That helps address a > > memory reclamation bug triggered by amdgpu. > > > >> Here is the vmstat -s output. > > I guess this is from a fresh boot? It would be most useful to see > > vmstat -s output taken at a time when the number of bucket allocation > > failures is also increasing. But, please try updating first to see if > > the lockups persist. > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Wed Jan 20 14:42:32 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F0F84F84D6 for ; Wed, 20 Jan 2021 14:42:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLSt02VXjz4qmD; Wed, 20 Jan 2021 14:42:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk1-x733.google.com with SMTP id 143so25442865qke.10; Wed, 20 Jan 2021 06:42:32 -0800 (PST) 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; bh=/hH6d7s/dCwFJoYIluIIifTk+Ts4qHPj06xWMk9RR2w=; b=qbHSSdN9+QKs8LzQCD7OBu2b1O4OwA6B6r7jnHldZM1XLe6WSgMFxmdf5NaB8i6QUX z3DNuAwNTl0AqznSMLa06kf2spBenLswY8/f1XlCNjji/DqkxFxFgUmSSpmOAi1l0YQ0 92oTsM5/bWLp/OEe+No/BXwnVS0vQLDl0LUkyvni8MHmtltatxR9z5S98Hg9FttSfY1x IWQCCHMLL/Yr9DRzdnsnqDyv+CdKHgqgNGjgY4xWyA+li9DvSFVZrZ8s92Qu8LRwRVj/ ld45+xLTnWyMA/+ZOsDB+gEcidDx76Hqd4f+RMs0usJdUFrntLlf1FyKrOIaM+Y7nvEZ o+eg== X-Gm-Message-State: AOAM531ryKxZouvg/I24jSufmeXNm70wycCJmchWpqpDUaq+eGBWHQLQ fKucImZ7PLMWNni/vGuwNos= X-Google-Smtp-Source: ABdhPJyx9ArsJXymDR+yl+b1TPufOVA+jWDGcNNHGQtqI9StY1b3aHIgsjXicH5xuz6W/DR0acQ79A== X-Received: by 2002:a05:620a:51:: with SMTP id t17mr9482908qkt.414.1611153751628; Wed, 20 Jan 2021 06:42:31 -0800 (PST) Received: from raichu ([142.126.164.150]) by smtp.gmail.com with ESMTPSA id f125sm1403383qkd.22.2021.01.20.06.42.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Jan 2021 06:42:30 -0800 (PST) Sender: Mark Johnston Date: Wed, 20 Jan 2021 09:42:28 -0500 From: Mark Johnston To: Konstantin Belousov Cc: rhurlin@freebsd.org, freebsd-current Subject: Re: Waiting for bufdaemon Message-ID: References: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4DLSt02VXjz4qmD X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:42:32 -0000 On Wed, Jan 20, 2021 at 03:12:27PM +0200, Konstantin Belousov wrote: > On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: > > Am 20.01.21 um 13:34 schrieb Konstantin Belousov: > > > On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: > > >> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: > > >>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: > > >>>> This patch hides the problem for me. The system seems to work better now. > > >>>> > > >>>> No waiting on reboot, and the webcam works better. > > >>> I am curious what do you mean by the above reference to webcam. > > >>> Can you explain it with more details, even if only the impressions? > > >> > > >> I should mention, that beside the already discussed timing problem with > > >> bufdaemon, I also have problems with several apps: > > >> > > >> > > >> After a high system load, several programs only react very slowly (e.g. > > >> Firefox). Several dockable apps from WindowMaker, but also e.g. conky do > > >> not update their windows anymore, they freeze. After some time, Firefox > > >> updates its screen content only after switching back from another window ... > > >> > > >> When such frozen programs are killed and restarted, they run normally > > >> again for an indefinite time before they freeze again. > > >> > > >> These symptoms completely disappeared, after I patched the Ryzen box as > > >> suggested on 01/17: > > > > > > Do you load latest microcode update from devcpu-data? > > > > Yes, sysutils/devcpu-data is installed and the following to lines are in > > /boot/loader.conf > > > > cpu_microcode_load="YES" > > cpu_microcode_name="/boot/firmware/intel-ucode.bin" > > > > But isn't this just for Intel (i387 and amd64), not AMD cpus? > You need microcode_update_enable="YES" in /etc/rc.conf for late microcode > update. > > I think that early boot update should work on AMD, bit for this you need to > select and put right blob. It is enough to load late to answer my question. The early microcode loader still doesn't support AMD. I did not do it for lack of a test system at the time. From owner-freebsd-current@freebsd.org Wed Jan 20 14:54:43 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 27BFB4F94EC for ; Wed, 20 Jan 2021 14:54:43 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4DLT830Yn8z4ssL; Wed, 20 Jan 2021 14:54:42 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-03.um.gwdg.de ([134.76.9.218] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1l2Esb-0005jR-Ns; Wed, 20 Jan 2021 15:54:41 +0100 Received: from krabat.raven.hur (10.250.9.200) by EXCMBX-03.um.gwdg.de (134.76.9.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2044.4; Wed, 20 Jan 2021 15:54:41 +0100 Subject: Re: Waiting for bufdaemon To: Mark Johnston CC: freebsd-current References: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> Reply-To: From: Rainer Hurling Message-ID: Date: Wed, 20 Jan 2021 15:54:35 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.200] X-ClientProxiedBy: excmbx-21.um.gwdg.de (134.76.9.231) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4DLT830Yn8z4ssL X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 14:54:43 -0000 Am 20.01.21 um 15:42 schrieb Mark Johnston: > On Wed, Jan 20, 2021 at 03:12:27PM +0200, Konstantin Belousov wrote: >> On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: >>> Am 20.01.21 um 13:34 schrieb Konstantin Belousov: >>>> On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: >>>>> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: >>>>>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >>>>>>> This patch hides the problem for me. The system seems to work better now. >>>>>>> >>>>>>> No waiting on reboot, and the webcam works better. >>>>>> I am curious what do you mean by the above reference to webcam. >>>>>> Can you explain it with more details, even if only the impressions? >>>>> >>>>> I should mention, that beside the already discussed timing problem with >>>>> bufdaemon, I also have problems with several apps: >>>>> >>>>> >>>>> After a high system load, several programs only react very slowly (e.g. >>>>> Firefox). Several dockable apps from WindowMaker, but also e.g. conky do >>>>> not update their windows anymore, they freeze. After some time, Firefox >>>>> updates its screen content only after switching back from another window ... >>>>> >>>>> When such frozen programs are killed and restarted, they run normally >>>>> again for an indefinite time before they freeze again. >>>>> >>>>> These symptoms completely disappeared, after I patched the Ryzen box as >>>>> suggested on 01/17: >>>> >>>> Do you load latest microcode update from devcpu-data? >>> >>> Yes, sysutils/devcpu-data is installed and the following to lines are in >>> /boot/loader.conf >>> >>> cpu_microcode_load="YES" >>> cpu_microcode_name="/boot/firmware/intel-ucode.bin" >>> >>> But isn't this just for Intel (i387 and amd64), not AMD cpus? >> You need microcode_update_enable="YES" in /etc/rc.conf for late microcode >> update. >> >> I think that early boot update should work on AMD, bit for this you need to >> select and put right blob. It is enough to load late to answer my question. > > The early microcode loader still doesn't support AMD. I did not do it > for lack of a test system at the time. > Thanks for the info. So for now, I can remove microcode_update_enable="YES" in /boot/loader.conf ... Is there anything, I can test for you (without having skills in the area ;) )? From owner-freebsd-current@freebsd.org Wed Jan 20 15:33:58 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5636C4FA04F for ; Wed, 20 Jan 2021 15:33:58 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailout07.eigbox.net (bosmailout07.eigbox.net [66.96.185.7]) (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 4DLV1K4Y9xz3Btd; Wed, 20 Jan 2021 15:33:57 +0000 (UTC) (envelope-from SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net) Received: from bosmailscan06.eigbox.net ([10.20.15.6]) by bosmailout07.eigbox.net with esmtp (Exim) id 1l2FUb-0000lY-4p; Wed, 20 Jan 2021 10:33:57 -0500 Received: from [10.115.3.32] (helo=bosimpout12) by bosmailscan06.eigbox.net with esmtp (Exim) id 1l2FUa-0004Ah-Rd; Wed, 20 Jan 2021 10:33:56 -0500 Received: from bosauthsmtp03.yourhostingaccount.com ([10.20.18.3]) by bosimpout12 with id K3Zt2400Z03yW76013ZwhH; Wed, 20 Jan 2021 10:33:56 -0500 X-Authority-Analysis: v=2.3 cv=WuawzeXv c=1 sm=1 tr=0 a=6uKCkKhFq2wXOH2GoQX8aA==:117 a=BXB5eCltbCg0Q+nSw1Bwcw==:17 a=EmqxpYm9HcoA:10 a=jXMol9EDn2QA:10 a=13zjGPudsaEWiJwPRgMA:9 a=6I5d2MoRAAAA:8 a=dL2ud52vqZqYPUsrl3oA:9 a=QEXdDO2ut3YA:10 a=ejY4BFkGPQtpa8mFhw0A:9 a=FfaGCDsud1wA:10 a=IjZwj45LgO3ly-622nXo:22 Received: from cm-81-9-160-236.telecable.es ([81.9.160.236]:17103 helo=[192.168.1.100]) by bosauthsmtp03.eigbox.net with esmtpa (Exim) id 1l2FUX-0003lh-NO; Wed, 20 Jan 2021 10:33:53 -0500 Subject: Re: Waiting for bufdaemon To: rhurlin@freebsd.org, Mark Johnston Cc: freebsd-current References: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> From: Santiago Martinez Message-ID: Date: Wed, 20 Jan 2021 15:33:49 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DGmmfebOsAouJg47SlKI8vlgncvIp68rK" X-EN-UserInfo: d3bdfab0736480cedf04ed92aaea2ef5:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: sm@codenetworks.net Sender: Santiago Martinez X-EN-OrigIP: 81.9.160.236 X-EN-OrigHost: cm-81-9-160-236.telecable.es X-Rspamd-Queue-Id: 4DLV1K4Y9xz3Btd X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.96.128.0/18]; HAS_ATTACHMENT(0.00)[]; DKIM_TRACE(0.00)[codenetworks.net:~]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FORGED_SENDER(0.30)[sm@codenetworks.net,SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net]; RECEIVED_SPAMHAUS_PBL(0.00)[81.9.160.236:received]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29873, ipnet:66.96.128.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[sm@codenetworks.net,SRS0=Efj8N1=GX=codenetworks.net=sm@eigbox.net]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[codenetworks.net: no valid DMARC record]; RCVD_IN_DNSWL_NONE(0.00)[66.96.185.7:from]; R_DKIM_PERMFAIL(0.00)[codenetworks.net:s=dkim]; RWL_MAILSPIKE_VERYGOOD(0.00)[66.96.185.7:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 15:33:58 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DGmmfebOsAouJg47SlKI8vlgncvIp68rK Content-Type: multipart/mixed; boundary="5wcuelIe0Pm24AVEpWBiD4brWaS4XXdfY"; protected-headers="v1" From: Santiago Martinez To: rhurlin@freebsd.org, Mark Johnston Cc: freebsd-current Message-ID: Subject: Re: Waiting for bufdaemon References: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> In-Reply-To: --5wcuelIe0Pm24AVEpWBiD4brWaS4XXdfY Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Same here Mark, and if you need remote access to a AMD Ryzen let me know.= Santi On 1/20/21 2:54 PM, Rainer Hurling wrote: > Thanks for the info. So for now, I can remove > microcode_update_enable=3D"YES" in /boot/loader.conf ... > > Is there anything, I can test for you (without having skills in the are= a > ;) )? > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" --5wcuelIe0Pm24AVEpWBiD4brWaS4XXdfY-- --DGmmfebOsAouJg47SlKI8vlgncvIp68rK Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEk06QWJzNAs9NTrFjWBFqYkyC55EFAmAITV0FAwAAAAAACgkQWBFqYkyC55HI 6w//UcNfJEUR7lAGOYsSSkrT/nagTHezpuLZwF+EnJ5fXpwDXGFkfNjNuNDmyFzRSq504X/jNFZC vgF6F2ShDVGlR2lifJcYGdvRH3qE18FXuBbKd4yYweANCzqAYfk7t1uEJ6AMkfBParqMYU3IXzW3 fi+m/Oc/duw8gwztokWM9DC9O2MNijz+t/K6wz1jet167gnT+jMA3UCrpaqHiLec4ihl1zhPYrla lT0eewNr+jH6nCSrDOnHUDIyFHek0fxsIYQrBpmlZZfLTTpiknA3bxEgE2CernzQX1ulf/WtlCli rNIBFZLqx0zVhXLIJ/ScghsH9e4vU4FwJsfXSMJY4jCGfYfu4CKUoU+hT1dbEwvobOTk0E63t9FN Dzr8voEdj7+5UtCLJLH8EYnNPN1Gb8ghG7B5+lSC/0Luq9AoRea4Sg2lKkmh7ChIz/G5LxhCWBvm 4TgDVBYXZYnAJkfB/dxtpiloCym0xy+twFuLyCicGVTiA8xFdL4nqRT+HlkwrBeaqD6kPWn2jcDV fLgG9lM/YBfEOAUGOTZmrrjPcigu7XAY6T4rRcc1wC4lRkTI2un1pmaCERSE6fTlOhX9Sq6K1XXb O0kajEoiCPRi/IP75i8AS6IZ21NzVO+5k2JjwLNa8DZc1ASt1SVjKGoYgHAH1iaWfBur8XvifQ6e Tqk= =Y4EX -----END PGP SIGNATURE----- --DGmmfebOsAouJg47SlKI8vlgncvIp68rK-- From owner-freebsd-current@freebsd.org Wed Jan 20 17:47:35 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 231094FD11F for ; Wed, 20 Jan 2021 17:47:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLXzR5r3Bz3MGc for ; Wed, 20 Jan 2021 17:47:31 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.160] (cpe-24-24-163-126.socal.res.rr.com [24.24.163.126]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 36c11445 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 20 Jan 2021 17:47:29 +0000 (UTC) Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 To: Emmanuel Vadot Cc: freebsd-current@freebsd.org References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> <1922f880-1bd3-65d0-b816-73623fa62f33@nomadlogic.org> <20210120085535.d3b6ccb33f9c8b111922b422@bidouilliste.com> From: Pete Wright Message-ID: Date: Wed, 20 Jan 2021 09:47:28 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <20210120085535.d3b6ccb33f9c8b111922b422@bidouilliste.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4DLXzR5r3Bz3MGc X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.28 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[174.136.98.114:from]; SPAMHAUS_ZRD(0.00)[174.136.98.114:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.975]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 17:47:35 -0000 On 1/19/21 11:55 PM, Emmanuel Vadot wrote: > >> i'm happy now running the current-kmod but let me know if it'd be >> helpful to do any more tests or provide additional info. > So what did you change ? ok i think i spot the issue - in my checkout of the ports tree via the github mirror at git://github.com/freebsd/freebsd-ports.git it looks like the pkg-plist doesn't include the %%SOURCE%%KMODSRC%% statements: $ cat pkg-plist %%AMDGPU%%/%%KMODDIR%%/amdgpu.ko %%AMDKFD%%/%%KMODDIR%%/amdkfd.ko /%%KMODDIR%%/drm.ko %%I915%%/%%KMODDIR%%/i915kms.ko /%%KMODDIR%%/linuxkpi_gplv2.ko /%%KMODDIR%%/radeonkms.ko /%%KMODDIR%%/ttm.ko $ on the drm-current-kmod plist things look as we would expect them i believe: $ head pkg-plist %%AMDGPU%%/%%KMODDIR%%/amdgpu.ko /%%KMODDIR%%/drm.ko %%I915%%/%%KMODDIR%%/i915kms.ko /%%KMODDIR%%/linuxkpi_gplv2.ko /%%KMODDIR%%/radeonkms.ko /%%KMODDIR%%/ttm.ko %%SOURCE%%%%KMODSRC%%/Makefile %%SOURCE%%%%KMODSRC%%/kconfig.mk %%SOURCE%%%%KMODSRC%%/amd/Makefile %%SOURCE%%%%KMODSRC%%/amd/amdgpu/Makefile $ I can file a PR with a patch later today if that's helpful, if this isn't due to bad git workspace on my end. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Jan 20 17:51:42 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 704504FD51B for ; Wed, 20 Jan 2021 17:51:42 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic303-24.consmr.mail.gq1.yahoo.com (sonic303-24.consmr.mail.gq1.yahoo.com [98.137.64.205]) (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 4DLY4F31gqz3N3X for ; Wed, 20 Jan 2021 17:51:40 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1611165099; bh=VdWB9QPZLbVOyibkq4OBU5ZqvO3h4LnxoqxvTIA3FvM=; h=Subject:From:Date:To:From:Subject:Reply-To; b=GvvdSeDEUF4npWF1pfDve63abiaXD93NNAJaX3MG3d5UnYgwyYqj/TJ5liu6gsQS4l4pwM/RabB99nq1Yn6R4JsWNAOsaT8aC7nRWJ2m0SD0bpUBmVRPMrX+ED89zxCkzfHDnlh9qVttPQyoKeR6C8F80Fd/OLvUUAnsozxXEO5BIfSWzRE8gFx93S6dvaSGBHrwd0gNftPJtGQwGQgbgKsU7+EViTUdt4Ptvmh3jQeSr4ybO0HaQSBak46fwBNiRD8Ick3BcM2vLpA5GljYg5vDUy9yAYPm/ew83EaSt/9ViWdxUITzWo6TXy8p0JJoOGARyqiY0xKrRmMiBLEUZw== X-YMail-OSG: _si0DgIVM1k8S3TQnyoeSbPnD4M9f5VLxK3zDUDzsX4N8IHZerps.NZptD4nTOp OPvExTaX19gVSlZyABusKQmzKKP2cJ60DqIA4nLwgPITqBVVlynXEG__YXH9tK_qqyttu5w6aqHv r59_CVHM9wAYQeobIwWcn1vS.uNgz7UytR72KqPM.G3st2tuTbh.X3hSx.6Km24IwXl3YAw4IXKL 4YiG_HDWcgoPZxyHTJqhy5zYJ6XC35GC_PDnRks_Iy4EcE9.r6moxL.TZyuI3CtaWFooXaip4yMk QzI70TQyfylQ9Lns8LSOzo8wvH4OPbkNSrjDqKKeLgzXqJcnFlMTVUiBEDiQEla2c.enOYIpFN_f mM6boNuxBN00S1ZPHGWN3JjmTjH_ZuB.uftVZx2I7QiF1yLC6Xf8FeKUnRLdb78.1xORdy_heAE4 qGBhtu24hey9HW58xp4kf7t3puzA91VxVua8KE56FmzyZ1aVX9UhhP24eB5kt.7QUuEmha7qRnNU Fiuq0mtQPpH6GC9dCoaVqDJo0Do647nJ_PQCBHgI4Q1.qnW4_98xMz.O4mUWzDavGAuXcqAvkJ.H TgT07DTwwexoUQHwEsVZHiOUbrNyQt7x3ua00DBzyek5LDFQAF7UlNfAloV8N_bFI4KGsnlhXvPp zOUvK2yAL.XvtGGp.F2dmz5yQfvJKu3lZAelpQ9Oq4TZYqolPO.2euhJeZzsFo2epU5j58DfyXKP 3T8eExag6AVEF6rkyc0yfIRhcPIjIqO8FEaTOyY1ssbVXjDsBSEqEXCqWk.fAE39pZzHTqNz2CRR kmMpf1Nx65kZkVI0PrC5T_lPgiqhfaG7DRx3OfTdNUneUXwFhHCkaag2kcTFgwif9aMaH.ej9fEP xGfik91JsrT_CmLzxzpEyX66cMDvmKBJxhV95KgeZd3UMOb9llKuA2rjPfVciKA7yCTcAnVu0DR9 vnMzSg3oRBRuWQ00rr16SXhjt9qBQeyZQ92lKHmdUQQ6Sd3IXytVPyNSRuwRBdbzyVOysy35auga QUtrnBtktiAptk9j9lYiNK1jY7lBFgBJ3Kc3vmx5UQ984n2AKOSMnflLRHhX__b0kasjIEYC8ZZZ B1tPSXId_RS4PGfRP1H5tp4pDExMtWuGXAXSV9ANaBytmH59fLjZDn9mGdLrt5BaIVFbn0g463ZL DPJpScT3Nz.6bSHrMF2Voi.lvFIV_m_FGy90dQD.nNrWKc0Fx.WPH9guEkobvzN6G2GL6YvNHA9L 6CPvtAPJCkFLMVfukDkOZGiGQf7OTrlHJVWLwOqCFzix_uxIcChlZKtrJl4Vp7GQoNGFJvX72al5 x2W8xT.7okdh.h919BH1iXn5lYY8tXA_rhfYMzx9d9xxie.5nSBYhXhFduQs9zkEqoDS63ZwXH8L kWiUp7j9O37AqVBx.WZg9WFu6f57nPZrrGgng_GDX48PL0wHvjKLSEAJL9D9GxBzWSukQORY222R MSp0qJZ6KL7QRWkrHrhenbYnemA3OyetTH6WrgNvHf6.RH3PMgyv399K7PkrD6hT4CmO0miwF98Q As_OB56E5mC6ZLoMYcGB8ZXkY.Xbpxx5mAkeeOGWW6lqzHHIKmIwAac73k88vWnYAzi7aj9wOGVm u_zkI38oxnbrgOeGexKX0rCXLyq9_yPrqNpdCw20B2Qm49kVETtIMceDlAKZZkHWhBw0wpokwpVQ I23xdvNEPu050Gv4Jskw6rie2ALTUOOtNlcTDlqfk_DEIcjcyaOCRhkQe85X6.MN.elfgeKQjDC0 4jmizYxwmZfTr4j0zZm6uF96_2B.MFQSZHv2qa.HD8J92Ki67myGIZB199MMZ1BhDpI4C25WgKxA KSE81XoWQtej_nZS.YMAB3BcO9SVu8tLA6ZkoBvNiCJPjECgYs0Hvg4MSEm8fH_ck3ukIuuCD_g9 oLTazAiv2Y0CnCht58sVwR.kW2klfsuxZCJMUk4dFK72EwTWiBbhb3sfn4NjYfgGaobUSTwwVyj1 k.h6Gcfd7SI8bHa.yCpSuehMJEo3Yj6FJ1RAUooTKxBO5DC4L12rK8UYqUupKt1I4HKLUJF9FU0P mxgFpK2p3O4dVXMatRcUqjC.1ZrTX9KCowhM5IOFGZhJj8kllo.CfHj8XvAIQuRHj7YJShSOISOQ RJjh9h8tiVklLdrdWQBzMewZpppk8P4X_4d7kTpR2QpkqFQ9Gfx3a3XbJEvZShoDNA7n0i.iqJEa 4ZgRp6h9e864RLS9U1dOjcPheQoRXuWDDdsRN3O3PO6_fmE0nuSpy.xS2t26VLIhW8u8B0yfh91J nnFqINQJ_Oab1Wv923wNgTUkaHDNIFiVXzUfhmNkrRgrzB.Nd60nCyyK8loUGRw5YMvC83TfsIH3 L3LfWyXDDB__b6yWQZZu8UA9GvZXmn4EqqCEL.FanWngSxL8rBwGFw6Ig1kn9i1vLVqae0qwkS9n T5AIOxuShUOADcm_bfQOdCSSe5sWDc6i9ibe0_PjmHtmwNl5vSKZxbld5X4JCKkRbIDC.cNaFWh5 qW4e00N8q7pZaGRoEAT0iHYisNAUVHUVk4NpcSUJp.KwilhY81w0U2A4CPAECRkN7SGcqDi973kw aaz_.3M.WMV9AZ0zet5hYhg0oobu_6h4mfqOT5Y70ORaA1s2TOUSa360l Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.gq1.yahoo.com with HTTP; Wed, 20 Jan 2021 17:51:39 +0000 Received: by smtp402.mail.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 7410524d06d0214790ba9d4f554a1e90; Wed, 20 Jan 2021 17:51:34 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld From: Mark Millard In-Reply-To: <056845FE-7131-4951-96AF-805D07F7BE0D@yahoo.com> Date: Wed, 20 Jan 2021 09:51:33 -0800 Cc: Current FreeBSD , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20210116043740.GA19523@www.zefox.net> <20210116155538.GA24259@www.zefox.net> <20210116220334.GA26756@www.zefox.net> <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> <20210118015009.GA31353@www.zefox.net> <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> <00104FAD-E32B-4DDE-80DD-FCEF14CEC06B@yahoo.com> <056845FE-7131-4951-96AF-805D07F7BE0D@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DLY4F31gqz3N3X X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.31 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.81)[-0.807]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.64.205:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.64.205:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.205:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.205:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 17:51:42 -0000 On 2021-Jan-19, at 17:42, Mark Millard wrote: > On 2021-Jan-18, at 21:12, Mark Millard wrote: >=20 >> On 2021-Jan-18, at 19:19, Mark Millard wrote: >>=20 >>> . . . >>>> FYI: I re-established my access to a RPi2B V1.1 and made >>>> it report: "maximum recommended amount (468832 pages)" >>>>=20 >>>> (The figure can vary some from release to release.) >>>>=20 >>>> 468832*4096 =3D=3D 1920335872 or a little over 1831 MiBytes >>>>=20 >>>> For the 4096 Byte pages, that means that the following from >>>> gpart fits without complaint (size is in blocks, not pages): >>>>=20 >>>> 413140992 3686400 da0p2 freebsd-swap (1.8G) >>>>=20 >>>> 3686400*512 is a little over 1.75 GiByte or 1800 MiByte. So >>>> I've left some room below 1831 MiBytes, but not a lot. >>>>=20 >>>> FYI about my build experiment that is running: >>>>=20 >>>> # sysctl hw.physmem >>>> hw.physmem: 979042304 >>>>=20 >>>> which, in recent times for armv7, I can (and did) set in >>>> /boot/loader.conf on a faster cortex-A7 SBC (that can boot >>>> the same media but has more RAM). >>>>=20 >>>> So I tried a -j4 build, but with LDFLAGS.lld+=3D -Wl,--threads=3D1 >>>> in use and my other particular src.conf/make.conf like content >>>> (so the builds do likely differ from yours in various ways). >>>> My build is producing a non-debug build (but with -g symbols). >>>> Somewhat after where your buildworld.log stops, my odd variant >>>> of top was reporting: >>>>=20 >>>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) >>>> Swap: . . . , 145832Ki MaxObsUsed >>>>=20 >>>> and top was also showing lots of processes as having "0B" RES >>>> in STATE "wait" or "nanslp" (so, apparently swapped out, not = paging). >>>> ("MaxObs" is short for "maximum observed".) >>>>=20 >>>> For comparison, your swapscript.log reported a maximum total of >>>> 346192 KiBytes "Used" for swap, about 98% into the log file. >>>>=20 >>>> (Time goes by . . .) >>>>=20 >>>> It finished with building libllvm and is part way into building >>>> libclang. This is probably well past where your hangup happened, >>>> given that your published buildworldlog file stopped with >>>> libllvm's Target/ARM/ARMMCInstLower.o . My odd top now shows: >>>>=20 >>>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki = MaxObs(Act+Wir) >>>> Swap: . . . , 392328Ki MaxObsUsed >>>>=20 >>>> The build continues to run. I'll let you know how it goes. >>>> . . . >>>=20 >>> Just after libclang finished my odd top showed: >>>=20 >>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892736Ki = MaxObs(Act+Wir) >>> Swap: . . . , 537588Ki MaxObsUsed >>>=20 >>> After liblldb: >>>=20 >>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 899276Ki = MaxObs(Act+Wir) >>> Swap: . . . , 537588Ki MaxObsUsed >>>=20 >>> Much later, after the lldb program had been built: >>>=20 >>> Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki = MaxObs(Act+Wir) >>> Swap: . . . , 537588Ki MaxObsUsed >>>=20 >>>>>> World build completed on Mon Jan 18 19:10:08 PST 2021 >>>>>> World built in 72960 seconds, ncpu: 4, make -j4 >>>=20 >>> This was building from scratch what was already installed: >>>=20 >>> # ~/fbsd-based-on-what-freebsd-main.sh=20 >>> merge-base: 818390ce0ca539300dd15d7a817784f1e3f7a9b8 >>> merge-base: CommitDate: 2021-01-13 21:27:44 +0000 >>> 4180404713ec (HEAD -> mm-src) mm-src snapshot for mm's patched build = in git context. >>> 818390ce0ca5 (freebsd/main, freebsd/HEAD, pure-src, main) arm64: fix = early devmap assertion >>> FreeBSD OPiP2E_RPi2v11 13.0-CURRENT FreeBSD 13.0-CURRENT = mm-src-c255938-g4180404713ec GENERIC-NODBG arm armv7 1300135 1300135 >>>=20 >>> This suggests that you should be able to build on the RPi2B v1.1, >>> using -j4, with appropriate configuration for what and how to build. >>>=20 >>>=20 >>> It is now building the matching kernel, my GENERIC-NODBG style. >>=20 >> Done: >>=20 >>>>> Kernel build for GENERIC-NODBG completed on Mon Jan 18 20:33:26 = PST 2021 >>>>> Kernel(s) GENERIC-NODBG built in 4998 seconds, ncpu: 4, make -j4 >>=20 >> So, World+Kernel in somewhat under 22 hours. >>=20 >> The "MaxObs*" figures were unchanged, so: >>=20 >> Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki = MaxObs(Act+Wir) >> Swap: . . . , 537588Ki MaxObsUsed >>=20 >> This suggests that, for now, 800 MiByte of swap would be something >> more than 1.5 times what it actually used and 1050 MiBytes would >> be something like 2.0 times what it actually used, so leaving some >> notable margin for variations in peek usage, at least when linker >> threading is avoided. >>=20 >>=20 >>=20 >> As for what I used to control "what and how to build" . . . >>=20 >> # more = ~/sys_build_scripts.armv7-host/make_armv7_nodebug_clang_bootstrap-armv7-ho= st.sh=20 >> kldload -n filemon && \ >> script = ~/sys_typescripts/typescript_make_armv7_nodebug_clang_bootstrap-armv7-host= -$(date +%Y-%m-%d:%H:%M:%S) \ >> env __MAKE_CONF=3D"/root/src.configs/make.conf" SRCCONF=3D"/dev/null" = SRC_ENV_CONF=3D"/root/src.configs/src.conf.armv7-clang-bootstrap.armv7-hos= t" \ >> WITH_META_MODE=3Dyes \ >> WORLD_FLAGS=3D"${WORLD_FLAGS} UBLDR_LOADADDR=3D0x42000000" \ >> MAKEOBJDIRPREFIX=3D"/usr/obj/armv7_clang/arm.armv7" \ >> make $* >>=20 >> (In my context, UBLDR_LOADADDR is ignored by anything that >> can not use the figure given. So I've no bothered to be >> more selective about having it in the armv7 builds.) >>=20 >> # more ~/src.configs/make.conf >> LDFLAGS.lld+=3D -Wl,--threads=3D1 >>=20 >> # more ~/src.configs/src.conf.armv7-clang-bootstrap.armv7-host >> TO_TYPE=3Darmv7 >> # >> KERNCONF=3DGENERIC-NODBG >> TARGET=3Darm >> .if ${.MAKE.LEVEL} =3D=3D 0 >> TARGET_ARCH=3D${TO_TYPE} >> .export TARGET_ARCH >> .endif >> # >> #WITH_CROSS_COMPILER=3D >> WITH_SYSTEM_COMPILER=3D >> WITH_SYSTEM_LINKER=3D >> # >> WITH_LIBCPLUSPLUS=3D >> WITHOUT_BINUTILS_BOOTSTRAP=3D >> WITH_ELFTOOLCHAIN_BOOTSTRAP=3D >> #Disables avoiding bootstrap: WITHOUT_LLVM_TARGET_ALL=3D >> WITHOUT_LLVM_TARGET_AARCH64=3D >> WITH_LLVM_TARGET_ARM=3D >> WITHOUT_LLVM_TARGET_MIPS=3D >> WITHOUT_LLVM_TARGET_POWERPC=3D >> WITHOUT_LLVM_TARGET_RISCV=3D >> WITHOUT_LLVM_TARGET_X86=3D >> WITH_CLANG=3D >> WITH_CLANG_IS_CC=3D >> WITH_CLANG_FULL=3D >> WITH_CLANG_EXTRAS=3D >> WITH_LLD=3D >> WITH_LLD_IS_LD=3D >> WITHOUT_BINUTILS=3D >> # >> WITH_LLDB=3D >> # >> WITH_BOOT=3D >> WITHOUT_LIB32=3D >> # >> # >> WITHOUT_WERROR=3D >> #WERROR=3D >> MALLOC_PRODUCTION=3D >> WITH_MALLOC_PRODUCTION=3D >> WITHOUT_ASSERT_DEBUG=3D >> WITHOUT_LLVM_ASSERTIONS=3D >> # >> # Avoid stripping but do not control host -g status as well: >> DEBUG_FLAGS+=3D >> # >> WITH_REPRODUCIBLE_BUILD=3D >> WITH_DEBUG_FILES=3D >> # >> # Use of the .clang 's here avoids >> # interfering with other CFLAGS >> # usage, such as ?=3D usage. >> CFLAGS.clang+=3D -mcpu=3Dcortex-a7 >> CXXFLAGS.clang+=3D -mcpu=3Dcortex-a7 >> CPPFLAGS.clang+=3D -mcpu=3Dcortex-a7 >>=20 >> (I do not claim that you would want WITH_REPRODUCIBLE_BUILD . >> I just happen to have been experimenting with it. You might >> not want to be explicit about the cpu to target. You might >> not want WITH_CLANG_EXTRAS .) >>=20 >> # more /usr/fbsd/mm-src/sys/arm/conf/GENERIC-NODBG >> include "GENERIC" >>=20 >> ident GENERIC-NODBG >>=20 >> makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols >>=20 >> options AUDIT # Not enabled by default in = armv7/v6 kernels >> # Enabled here to allow kyua = test runs to >> # possibly report auditing = works. >>=20 >> options ALT_BREAK_TO_DEBUGGER >>=20 >> options KDB # Enable kernel debugger = support >>=20 >> # For minimum debugger support (stable branch) use: >> options KDB_TRACE # Print a stack trace for a = panic >> options DDB # Enable the kernel debugger >>=20 >> # Extra stuff: >> #options VERBOSE_SYSINIT=3D0 # Enable verbose sysinit = messages >> #options BOOTVERBOSE=3D1 >> #options BOOTHOWTO=3DRB_VERBOSE >> options ALT_BREAK_TO_DEBUGGER # Enter debugger on keyboard = escape sequence >> options KLD_DEBUG >> #options KTR >> #options KTR_MASK=3DKTR_TRAP >> ##options KTR_CPUMASK=3D0xF >> #options KTR_VERBOSE >>=20 >> # Disable any extra checking for. . . >> nooptions INVARIANTS # Enable calls of extra = sanity checking >> nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS >> nooptions WITNESS # Enable checks to detect = deadlocks and cycles >> nooptions WITNESS_SKIPSPIN # Don't run witness on = spinlocks for speed >> nooptions DEADLKRES # Enable the deadlock = resolver >> nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones >> nooptions DIAGNOSTIC >> nooptions BUF_TRACKING >> nooptions FULL_BUF_TRACKING >> nooptions USB_DEBUG >> nooptions USB_REQ_DEBUG >> nooptions USB_VERBOSE >>=20 >> The /boot/loader.conf file and the /etc/sysctl.conf files >> both contained: >>=20 >> vm.pageout_oom_seq=3D120 >> vm.pfault_oom_attempts=3D-1 >>=20 >> (The hw.physmem=3D979042304 in /boot/loader.conf was very-special, >> to better approximate your environment. I also controlled the >> cpu frequency used via a line in /etc/sysctl.conf . I do not >> bother with such non-default frequency usage [or related settings] >> for RPi*'s with the pre-RPi4B style power connections but do >> control the frequency for the OPi+2E.) >=20 > The following had been left implicit about my context and > how it manages memory space use. >=20 > I'll note that I do not use tmpfs or other such memory based > file system techniques that could compete for RAM/swap. What > is in use for the only file system involved is just the > root file system: >=20 > # df -m > Filesystem 1M-blocks Used Avail Capacity Mounted on > /dev/gpt/BPIM3root 195378 63940 115808 36% / > devfs 0 0 0 100% /dev >=20 > It is a USB SSD. The swap partition is also on that same > media. (The BPIM3 based name dates back to before the > BPI-M3 power connection failed and I switched to the > OPi+2E.) >=20 > I'll note that I've started a new from-scratch build without > LDFLAGS.lld+=3D -Wl,--threads=3D1 . So at some point I'll have > information about how much of a difference (+/-) in swap > usage it actually made for with vs. without, if any. Looks like, for such 4-core contexts, that bothering with LDFLAGS.lld+=3D -Wl,--threads=3D1 is typically a waste of effort for both swap usage and time . . . With LDFLAGS.lld+=3D -Wl,--threads=3D1 : Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki = MaxObs(Act+Wir) Swap: . . . , 537588Ki MaxObsUsed without: Mem: . . ., 715756Ki MaxObsActive, 194816Ki MaxObsWired, 903132Ki = MaxObs(Act+Wir) Swap: . . ., 557208Ki MaxObsUsed With LDFLAGS.lld+=3D -Wl,--threads=3D1 : World built in 72960 seconds, ncpu: 4, make -j4 Kernel(s) GENERIC-NODBG built in 4998 seconds, ncpu: 4, make -j4 without: World built in 72804 seconds, ncpu: 4, make -j4 Kernel(s) GENERIC-NODBG built in 4824 seconds, ncpu: 4, make -j4 So, just not that much of a difference compared to the overall sizes or times involved. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Wed Jan 20 18:05:10 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1F1314FDA6B for ; Wed, 20 Jan 2021 18:05:10 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4DLYMn1JNzz3PD7 for ; Wed, 20 Jan 2021 18:05:08 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-03.um.gwdg.de ([134.76.9.218] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1l2Hqt-00070N-3x; Wed, 20 Jan 2021 19:05:07 +0100 Received: from krabat.raven.hur (10.250.9.200) by EXCMBX-03.um.gwdg.de (134.76.9.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2044.4; Wed, 20 Jan 2021 19:05:06 +0100 Subject: Re: Waiting for bufdaemon From: Rainer Hurling To: Konstantin Belousov CC: freebsd-current Reply-To: References: <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> Message-ID: <49e151f1-499e-9181-fde0-31591bc1a4eb@gwdg.de> Date: Wed, 20 Jan 2021 19:05:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.200] X-ClientProxiedBy: excmbx-21.um.gwdg.de (134.76.9.231) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4DLYMn1JNzz3PD7 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; HAS_REPLYTO(0.00)[rhurlin@FreeBSD.org]; HAS_XOIP(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:134.76.10.0/23]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[134.76.11.17:from]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:680, ipnet:134.76.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[rhurlin]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; DMARC_NA(0.00)[gwdg.de]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[134.76.11.17:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 18:05:10 -0000 Am 20.01.21 um 15:36 schrieb Rainer Hurling: > Am 20.01.21 um 14:52 schrieb Konstantin Belousov: >> On Wed, Jan 20, 2021 at 02:35:59PM +0100, Rainer Hurling wrote: >>> Am 20.01.21 um 14:12 schrieb Konstantin Belousov: >>>> On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: >>>>> Am 20.01.21 um 13:34 schrieb Konstantin Belousov: >>>>>> On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: >>>>>>> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: >>>>>>>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >>>>>>>>> This patch hides the problem for me. The system seems to work better now. >>>>>>>>> >>>>>>>>> No waiting on reboot, and the webcam works better. >>>>>>>> I am curious what do you mean by the above reference to webcam. >>>>>>>> Can you explain it with more details, even if only the impressions? >>>>>>> >>>>>>> I should mention, that beside the already discussed timing problem with >>>>>>> bufdaemon, I also have problems with several apps: >>>>>>> >>>>>>> >>>>>>> After a high system load, several programs only react very slowly (e.g. >>>>>>> Firefox). Several dockable apps from WindowMaker, but also e.g. conky do >>>>>>> not update their windows anymore, they freeze. After some time, Firefox >>>>>>> updates its screen content only after switching back from another window ... >>>>>>> >>>>>>> When such frozen programs are killed and restarted, they run normally >>>>>>> again for an indefinite time before they freeze again. >>>>>>> >>>>>>> These symptoms completely disappeared, after I patched the Ryzen box as >>>>>>> suggested on 01/17: >>>>>> >>>>>> Do you load latest microcode update from devcpu-data? >>>>> >>>>> Yes, sysutils/devcpu-data is installed and the following to lines are in >>>>> /boot/loader.conf >>>>> >>>>> cpu_microcode_load="YES" >>>>> cpu_microcode_name="/boot/firmware/intel-ucode.bin" >>>>> >>>>> But isn't this just for Intel (i387 and amd64), not AMD cpus? >>>> You need microcode_update_enable="YES" in /etc/rc.conf for late microcode >>>> update. >>>> >>>> I think that early boot update should work on AMD, bit for this you need to >>>> select and put right blob. It is enough to load late to answer my question. >>> >>> Ah, ok. Thanks for clarification. I also put cpu_microcode_load="YES" in >>> /etc/rc.conf for a late update. >>> >>> Should I try again without your patch of sys/x86/tsc.c, whether the >>> problem still occurs? > > Unfornately, without the patch from 01/17 the problem is _not_ solved. > > Next I will try your patch from today, f lib/libc/x86/sys/__vdso_gettc.c > an lib/libc/x86/sys/__vdso_gettc.c ... I can confirm that this patch also works for me on Ryzen 3950X. No more bufdaemon waitings, no frozen apps, ... > > >> Yes. >> >>> >>> >>> And for the early boot update, how do I know about the right blob? >> I am not aware of the mechanism. My best suggestion is that you match >> the blob against your CPU family/model id manually. >> >>> >>>> >>>>> >>>>>> It might be not enough, which means that additionally latest BIOS needs >>>>>> to be flushed. >>>>>> >>>>> >>>>> I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite" >>>>> mainboard. From owner-freebsd-current@freebsd.org Wed Jan 20 19:09:31 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E36434FF1D1 for ; Wed, 20 Jan 2021 19:09:31 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLZp259Xhz3jC0 for ; Wed, 20 Jan 2021 19:09:30 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from skull.home.blih.net (lfbn-idf2-1-745-114.w86-247.abo.wanadoo.fr [86.247.192.114]) by mx.blih.net (OpenSMTPD) with ESMTPSA id f5a2f100 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 20 Jan 2021 19:09:27 +0000 (UTC) Date: Wed, 20 Jan 2021 20:09:23 +0100 From: Emmanuel Vadot To: Pete Wright Cc: freebsd-current@freebsd.org Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 Message-Id: <20210120200923.40ed0107802b68f0c73dad28@bidouilliste.com> In-Reply-To: References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> <1922f880-1bd3-65d0-b816-73623fa62f33@nomadlogic.org> <20210120085535.d3b6ccb33f9c8b111922b422@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DLZp259Xhz3jC0 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; FREEFALL_USER(0.00)[manu]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; ARC_NA(0.00)[]; SPAMHAUS_ZRD(0.00)[212.83.155.74:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.83.155.74:from]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 19:09:31 -0000 On Wed, 20 Jan 2021 09:47:28 -0800 Pete Wright wrote: > > > On 1/19/21 11:55 PM, Emmanuel Vadot wrote: > > > >> i'm happy now running the current-kmod but let me know if it'd be > >> helpful to do any more tests or provide additional info. > > So what did you change ? > > > ok i think i spot the issue - in my checkout of the ports tree via the > github mirror at git://github.com/freebsd/freebsd-ports.git it looks > like the pkg-plist doesn't include the %%SOURCE%%KMODSRC%% statements: > > $ cat pkg-plist > %%AMDGPU%%/%%KMODDIR%%/amdgpu.ko > %%AMDKFD%%/%%KMODDIR%%/amdkfd.ko > /%%KMODDIR%%/drm.ko > %%I915%%/%%KMODDIR%%/i915kms.ko > /%%KMODDIR%%/linuxkpi_gplv2.ko > /%%KMODDIR%%/radeonkms.ko > /%%KMODDIR%%/ttm.ko > $ > > on the drm-current-kmod plist things look as we would expect them i believe: > $ head pkg-plist > %%AMDGPU%%/%%KMODDIR%%/amdgpu.ko > /%%KMODDIR%%/drm.ko > %%I915%%/%%KMODDIR%%/i915kms.ko > /%%KMODDIR%%/linuxkpi_gplv2.ko > /%%KMODDIR%%/radeonkms.ko > /%%KMODDIR%%/ttm.ko > %%SOURCE%%%%KMODSRC%%/Makefile > %%SOURCE%%%%KMODSRC%%/kconfig.mk > %%SOURCE%%%%KMODSRC%%/amd/Makefile > %%SOURCE%%%%KMODSRC%%/amd/amdgpu/Makefile > $ > > > I can file a PR with a patch later today if that's helpful, if this > isn't due to bad git workspace on my end. > > cheers, > -pete > > -- > Pete Wright > pete@nomadlogic.org > @nomadlogicLA drm-devel-kmod doesn't install the sources on purpose. It never had and never will. So, did you "solve" the problem by switching to drm-current-kmod or to drm-devel-kmod ? -- Emmanuel Vadot From owner-freebsd-current@freebsd.org Wed Jan 20 19:16:28 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B565E4FF64A for ; Wed, 20 Jan 2021 19:16:28 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLZy35gTnz3jys for ; Wed, 20 Jan 2021 19:16:27 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.160] (cpe-24-24-163-126.socal.res.rr.com [24.24.163.126]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 2e7c18cd (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 20 Jan 2021 19:16:26 +0000 (UTC) Subject: Re: DRM problem installing kernel on main-c561-gc3e75b6c1 To: Emmanuel Vadot Cc: freebsd-current@freebsd.org References: <010001771b0a2c68-7bb71129-e451-4d4c-a3b4-d022c375a36e-000000@email.amazonses.com> <301b529c-6953-0e72-8da4-2e1c289df54e@nomadlogic.org> <20210119211159.d6395f9ed3b6e038f5f40b15@bidouilliste.com> <629d42c7-da2e-8285-09d6-b952b6556562@nomadlogic.org> <01b20079-1117-f51c-b78a-598d573403b9@nomadlogic.org> <20210119221801.d397abc940082f21bf93a42c@bidouilliste.com> <1922f880-1bd3-65d0-b816-73623fa62f33@nomadlogic.org> <20210120085535.d3b6ccb33f9c8b111922b422@bidouilliste.com> <20210120200923.40ed0107802b68f0c73dad28@bidouilliste.com> From: Pete Wright Message-ID: Date: Wed, 20 Jan 2021 11:16:25 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <20210120200923.40ed0107802b68f0c73dad28@bidouilliste.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4DLZy35gTnz3jys X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[174.136.98.114:from]; SPAMHAUS_ZRD(0.00)[174.136.98.114:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 19:16:28 -0000 On 1/20/21 11:09 AM, Emmanuel Vadot wrote: > On Wed, 20 Jan 2021 09:47:28 -0800 > Pete Wright wrote: > >> >> On 1/19/21 11:55 PM, Emmanuel Vadot wrote: >>>> i'm happy now running the current-kmod but let me know if it'd be >>>> helpful to do any more tests or provide additional info. >>> So what did you change ? >> >> ok i think i spot the issue - in my checkout of the ports tree via the >> github mirror at git://github.com/freebsd/freebsd-ports.git it looks >> like the pkg-plist doesn't include the %%SOURCE%%KMODSRC%% statements: >> >> $ cat pkg-plist >> %%AMDGPU%%/%%KMODDIR%%/amdgpu.ko >> %%AMDKFD%%/%%KMODDIR%%/amdkfd.ko >> /%%KMODDIR%%/drm.ko >> %%I915%%/%%KMODDIR%%/i915kms.ko >> /%%KMODDIR%%/linuxkpi_gplv2.ko >> /%%KMODDIR%%/radeonkms.ko >> /%%KMODDIR%%/ttm.ko >> $ >> >> on the drm-current-kmod plist things look as we would expect them i believe: >> $ head pkg-plist >> %%AMDGPU%%/%%KMODDIR%%/amdgpu.ko >> /%%KMODDIR%%/drm.ko >> %%I915%%/%%KMODDIR%%/i915kms.ko >> /%%KMODDIR%%/linuxkpi_gplv2.ko >> /%%KMODDIR%%/radeonkms.ko >> /%%KMODDIR%%/ttm.ko >> %%SOURCE%%%%KMODSRC%%/Makefile >> %%SOURCE%%%%KMODSRC%%/kconfig.mk >> %%SOURCE%%%%KMODSRC%%/amd/Makefile >> %%SOURCE%%%%KMODSRC%%/amd/amdgpu/Makefile >> $ >> >> >> I can file a PR with a patch later today if that's helpful, if this >> isn't due to bad git workspace on my end. >> >> cheers, >> -pete >> >> -- >> Pete Wright >> pete@nomadlogic.org >> @nomadlogicLA > drm-devel-kmod doesn't install the sources on purpose. > It never had and never will. > > So, did you "solve" the problem by switching to drm-current-kmod or to > drm-devel-kmod ? ah i see, thanks for the clarification. so as of now i'm using the drm-current-kmod on my amdgpu system. using the drm-devel-kmod throws the previously reported error trying to load linuxkpi_gplv2.ko: KLD drm.ko: depends on linuxkpi_gplv2 - not available or version mismatch linker_load_file: /boot/modules/drm.ko - unsupported file type KLD amdgpu.ko: depends on drmn - not available or version mismatch linker_load_file: /boot/modules/amdgpu.ko - unsupported file type -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Jan 20 20:21:24 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E09894D8ED0 for ; Wed, 20 Jan 2021 20:21:24 +0000 (UTC) (envelope-from nc@freebsd.org) Received: from rainpuddle.neelc.org (rainpuddle.neelc.org [IPv6:2001:19f0:8001:fed:5400:2ff:fe73:c622]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLcP046Svz3nML for ; Wed, 20 Jan 2021 20:21:24 +0000 (UTC) (envelope-from nc@freebsd.org) Received: from mail.neelc.org (rainpuddle.neelc.org [IPv6:2001:19f0:8001:fed:5400:2ff:fe73:c622]) by rainpuddle.neelc.org (Postfix) with ESMTPSA id 610A5EB2A5 for ; Wed, 20 Jan 2021 12:21:15 -0800 (PST) MIME-Version: 1.0 Date: Wed, 20 Jan 2021 12:21:15 -0800 From: Neel Chauhan To: freebsd-current@freebsd.org Subject: Can In-Kernel TLS (kTLS) work with any OpenSSL Application? User-Agent: Roundcube Webmail/1.4.9 Message-ID: X-Sender: nc@freebsd.org Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_938932f26e3bde6087a5ec59cc437c39"; micalg=pgp-sha256 X-Rspamd-Queue-Id: 4DLcP046Svz3nML X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:20473, ipnet:2001:19f0:8000::/38, country:US]; local_wl_from(0.00)[freebsd.org] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 20 Jan 2021 20:21:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_938932f26e3bde6087a5ec59cc437c39 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi freebsd-current@, I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while back. With 13.0-RELEASE around the corner, I'm thinking about upgrading my home server, well if I can accelerate any SSL application. I'm asking because I have a home server on a symmetrical Gigabit connection (Google Fiber/Webpass), and that server runs a Tor relay. If you're interested in how Tor works, the EFF has a writeup: https://www.eff.org/pages/what-tor-relay But the main point for you all is: more-or-less Tor relays deal with 1000s TLS connections going into and out of the server. Would In-Kernel TLS help with an application like Tor (or even load balancers/TLS termination), or is it more for things like web servers sending static files via sendfile() (e.g. CDN used by Netflix). My server could also work with Intel's QuickAssist (since it has an Intel Xeon "Scalable" CPU). Would QuickAssist SSL be more helpful here? I'm asking since I don't know whether to upgrade my home server to 13.x or leave it at 12.x. Yes, I do know we need a special OpenSSL to use kTLS. -Neel --=_938932f26e3bde6087a5ec59cc437c39 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=488 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEFpeUj+sDItoNIly9vzSRBRPfYX0FAmAIkLsACgkQvzSRBRPf YX32lQgAmubLcb2ZwNDhct9DyQyPlfEzKNdWZeM0tmO8js/CgxGz8OmRSWxUYTP3 INsihSVd1TBHGsYqHwFR0jMYB4yy26rlGZO+F7jz8WsZN+R//MH3jE68CwNKMYPk ww622KczuxLdSLrhek/Dyq927teOYJE9BKJMed6Rlhx0eMN9Ic7OZrbhgrPwdM9M LbWusAP/4aLDtyTRE9ANjzsyoGH30K/SQoSTEihODLx3zd0sNo1NJVu70Vn53TWj 0/6XQr296mh7q5zA56bqkcuFqInlghF1OTIm7f82UR+tSZ2xpJWW7Yb/YwKvzcTH X7zuKROAevTrMfXTnjO5lmFtB8B8Bg== =/yZF -----END PGP SIGNATURE----- --=_938932f26e3bde6087a5ec59cc437c39-- From owner-freebsd-current@freebsd.org Thu Jan 21 01:48:00 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D0BA94E13A8 for ; Thu, 21 Jan 2021 01:48:00 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLldr0sy8z4cR2 for ; Thu, 21 Jan 2021 01:47:59 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: by mail-pg1-x529.google.com with SMTP id 15so281394pgx.7 for ; Wed, 20 Jan 2021 17:47:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=NZGd/8u/+ebYCs8/bBcgJ1AnczsBCQh5qg8b/BL7cZI=; b=F8csoM/5JV6yhoODKNnE+9LQLqnZnucYPggfhOL/FwUMLnj7ogcQ5+GRvKYWNkg5vo pphgqjXbN3Jedh3C+/NKFcqajf4gfhduLraT9J/JvHwAynSirHUx2388sFaZyU3up8cQ FsFNKOJ+mQSOesVEDlq5c+t2YHP1R3jInZ4fzes8M6WfJCzgv3I7yT4IL5pNkTszCQCB AjsGSK5wuWhQkMSA9cu53FLB24YhwIad9aay1pj1i1eKQ0SmxcLKqXYwvUhEY1uDrsyH 4jrc2aBMw5VY7PUZQK3WX8DgMiNWM4eUblHlzImq/yYBRyWUxdG2vFrlpOMVDRcPjNvL bxTA== X-Gm-Message-State: AOAM532EX3k6DqHCPnnJsoihflo5H3iJMYXsflgN8j4l0pYyuwwRwaZV oqolHDqIjuOHpVYoelswCJx/yClBkGbs80rm X-Google-Smtp-Source: ABdhPJxiE76x4QVg2jVnciAz0+uzEe0dqiKYHTxQjOdIDRUEWlxNnPjR0ciFnH3HDLHPupvSRbP8Lw== X-Received: by 2002:a63:5014:: with SMTP id e20mr12137620pgb.152.1611193677980; Wed, 20 Jan 2021 17:47:57 -0800 (PST) Received: from macbook-2.local (c-71-238-26-71.hsd1.or.comcast.net. [71.238.26.71]) by smtp.gmail.com with ESMTPSA id u1sm3462261pjr.51.2021.01.20.17.47.55 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 17:47:56 -0800 (PST) To: freebsd-current@freebsd.org From: Michael Dexter Subject: FreeBSD 13.0 Build Option Sweep Message-ID: Date: Wed, 20 Jan 2021 17:47:51 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DLldr0sy8z4cR2 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.82 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[callfortesting-org.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::529:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[71.238.26.71:received]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.52)[-0.524]; R_DKIM_ALLOW(-0.20)[callfortesting-org.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[callfortesting.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::529:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::529:from]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 01:48:00 -0000 Hello all, I have been experimenting with FreeBSD build options on and off since FreeBSD 4.8/5.0 for use with minimum jails and later virtual machines. If you have ever tried to build "without all" and working your way back up, you have probably found this to be a very frustrating adventure in make-related failures after hours of compilation and, on the darkest days, concurrent deletion bugs which would give a different error every time you run a build. Fortunately, with the help of people like Ed Maste, Bryan Drewery, Bjoern Zeeb, Kyle Evans, and others, we have been gradually knocking broken build options off of the lists generated by the tools/tools/build_option_survey that PHK wrote long ago. An annotated list of working and failing build options in FreeBSD 13.0-ALPHA1 can be found here: https://callfortesting.org/results/bos-FreeBSD-13A1/ Two have been fixed and PRs exist for the majority of them with some possible fixes for those who know the code best to consider. One broken option is a recent regression while one pair, WITHOUT_LIBTHR/WITHOUT_LIBPTHREAD is quite stale and is a candidate for significant attention or possibly removal. If you are wondering, as of 13.0-ALPHA1, the following KERNCONF and generated /usr/src.conf are the minimum to build FreeBSD and build it in a bhyve VM from a UFS-formatted disk image: cpu HAMMER ident LESSBSD makeoptions MODULES_OVERRIDE="virtio" options SCHED_ULE device pci device loop device ether device uart device atpic device ahci device scbus options GEOM_PART_GPT options FFS sh /usr/src/tools/tools/build_option_survey/listallopts.sh \ | grep -v WITH_ | sed 's/$/=YES/' | \ grep -v WITHOUT_AUTO_OBJ | \ grep -v WITHOUT_UNIFIED_OBJDIR | \ grep -v WITHOUT_CRYPT | \ grep -v WITHOUT_DYNAMICROOT | \ grep -v WITHOUT_LIBCPLUSPLUS | \ grep -v WITHOUT_INSTALLLIB | \ grep -v WITHOUT_LIBTHR | \ grep -v WITHOUT_LIBPTHREAD | \ grep -v WITHOUT_BOOT | \ grep -v WITHOUT_LOADER_LUA | \ grep -v WITHOUT_LOCALES | \ grep -v WITHOUT_ZONEINFO | \ grep -v WITHOUT_VI \ > /etc/src.conf Explanation/Status: WITHOUT_AUTO_OBJ and WITHOUT_UNIFIED_OBJDIR belong in src-env.conf and kindly instantly warn you of this and terminate the build. WITHOUT_DYNAMICROOT and WITHOUT_LIBCPLUSPLUS are fixed in CURRENT. WITHOUT_INSTALLLIB and WITHOUT_LIBCPLUSPLUS should be easy to fix and candidate syntax is in the PRs linked in the above link. WITHOUT_CRYPT has regressed in recent months. WITHOUT_LIBTHR and WITHOUT_LIBPTHREAD are challenges. WITHOUT_BOOT onward are optional to build but are needed to boot the VM, see a console, set the time zone, and optionally edit files. The resulting kernel is 5M in size and the world and kernel are 90M. Basic networking adds another 1M. The build times on an EPYC 7402p are: buildworld 1m43.34s Warm ARC: 1m33.73s buildkernel 9.35s installworld 18.75s installkernel 0.32s Total: 3m23.44s Boot time: About three seconds I sincerely hope that all build options worked at some point and, given how much progress has been made, FreeBSD 13.0 can also support all options, or at a minimum, abort the build early as appropriate as the src-env.conf ones do. Think of the Developers! Spare them continued frustration with these. We can do this. I am happy to test any patches on multiple platforms. I am also happy to send individuals my minimum VM script and fortunately, it is out-of-date with every build option fix. All the best, Michael From owner-freebsd-current@freebsd.org Thu Jan 21 02:34:02 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B65BD4E3ED0; Thu, 21 Jan 2021 02:34:02 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLmfx3mtzz4hLm; Thu, 21 Jan 2021 02:34:01 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 10L2XwVZ059488 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 20 Jan 2021 18:33:58 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 10L2XwRG059485; Wed, 20 Jan 2021 18:33:58 -0800 (PST) (envelope-from fbsd) Date: Wed, 20 Jan 2021 18:33:58 -0800 From: bob prohaska To: Mark Millard Cc: Current FreeBSD , freebsd-arm@freebsd.org Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld Message-ID: <20210121023358.GA58854@www.zefox.net> References: <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> <20210118015009.GA31353@www.zefox.net> <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> <00104FAD-E32B-4DDE-80DD-FCEF14CEC06B@yahoo.com> <056845FE-7131-4951-96AF-805D07F7BE0D@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4DLmfx3mtzz4hLm X-Spamd-Bar: - X-Spamd-Result: default: False [-1.10 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-arm]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 02:34:02 -0000 On Wed, Jan 20, 2021 at 09:51:33AM -0800, Mark Millard wrote: > On 2021-Jan-19, at 17:42, Mark Millard wrote: > > > On 2021-Jan-18, at 21:12, Mark Millard wrote: > > > >> On 2021-Jan-18, at 19:19, Mark Millard wrote: > >> > >>> . . . > >>>> FYI: I re-established my access to a RPi2B V1.1 and made > >>>> it report: "maximum recommended amount (468832 pages)" > >>>> > >>>> (The figure can vary some from release to release.) > >>>> > >>>> 468832*4096 == 1920335872 or a little over 1831 MiBytes > >>>> > >>>> For the 4096 Byte pages, that means that the following from > >>>> gpart fits without complaint (size is in blocks, not pages): > >>>> > >>>> 413140992 3686400 da0p2 freebsd-swap (1.8G) > >>>> > >>>> 3686400*512 is a little over 1.75 GiByte or 1800 MiByte. So > >>>> I've left some room below 1831 MiBytes, but not a lot. > >>>> > >>>> FYI about my build experiment that is running: > >>>> > >>>> # sysctl hw.physmem > >>>> hw.physmem: 979042304 > >>>> > >>>> which, in recent times for armv7, I can (and did) set in > >>>> /boot/loader.conf on a faster cortex-A7 SBC (that can boot > >>>> the same media but has more RAM). > >>>> > >>>> So I tried a -j4 build, but with LDFLAGS.lld+= -Wl,--threads=1 > >>>> in use and my other particular src.conf/make.conf like content > >>>> (so the builds do likely differ from yours in various ways). > >>>> My build is producing a non-debug build (but with -g symbols). > >>>> Somewhat after where your buildworld.log stops, my odd variant > >>>> of top was reporting: > >>>> > >>>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki MaxObs(Act+Wir) > >>>> Swap: . . . , 145832Ki MaxObsUsed > >>>> > >>>> and top was also showing lots of processes as having "0B" RES > >>>> in STATE "wait" or "nanslp" (so, apparently swapped out, not paging). > >>>> ("MaxObs" is short for "maximum observed".) > >>>> > >>>> For comparison, your swapscript.log reported a maximum total of > >>>> 346192 KiBytes "Used" for swap, about 98% into the log file. > >>>> > >>>> (Time goes by . . .) > >>>> > >>>> It finished with building libllvm and is part way into building > >>>> libclang. This is probably well past where your hangup happened, > >>>> given that your published buildworldlog file stopped with > >>>> libllvm's Target/ARM/ARMMCInstLower.o . My odd top now shows: > >>>> > >>>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892732Ki MaxObs(Act+Wir) > >>>> Swap: . . . , 392328Ki MaxObsUsed > >>>> > >>>> The build continues to run. I'll let you know how it goes. > >>>> . . . > >>> > >>> Just after libclang finished my odd top showed: > >>> > >>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 892736Ki MaxObs(Act+Wir) > >>> Swap: . . . , 537588Ki MaxObsUsed > >>> > >>> After liblldb: > >>> > >>> Mem: . . . , 753672Ki MaxObsActive, 200412Ki MaxObsWired, 899276Ki MaxObs(Act+Wir) > >>> Swap: . . . , 537588Ki MaxObsUsed > >>> > >>> Much later, after the lldb program had been built: > >>> > >>> Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki MaxObs(Act+Wir) > >>> Swap: . . . , 537588Ki MaxObsUsed > >>> > >>>>>> World build completed on Mon Jan 18 19:10:08 PST 2021 > >>>>>> World built in 72960 seconds, ncpu: 4, make -j4 > >>> > >>> This was building from scratch what was already installed: > >>> > >>> # ~/fbsd-based-on-what-freebsd-main.sh > >>> merge-base: 818390ce0ca539300dd15d7a817784f1e3f7a9b8 > >>> merge-base: CommitDate: 2021-01-13 21:27:44 +0000 > >>> 4180404713ec (HEAD -> mm-src) mm-src snapshot for mm's patched build in git context. > >>> 818390ce0ca5 (freebsd/main, freebsd/HEAD, pure-src, main) arm64: fix early devmap assertion > >>> FreeBSD OPiP2E_RPi2v11 13.0-CURRENT FreeBSD 13.0-CURRENT mm-src-c255938-g4180404713ec GENERIC-NODBG arm armv7 1300135 1300135 > >>> > >>> This suggests that you should be able to build on the RPi2B v1.1, > >>> using -j4, with appropriate configuration for what and how to build. > >>> > >>> > >>> It is now building the matching kernel, my GENERIC-NODBG style. > >> > >> Done: > >> > >>>>> Kernel build for GENERIC-NODBG completed on Mon Jan 18 20:33:26 PST 2021 > >>>>> Kernel(s) GENERIC-NODBG built in 4998 seconds, ncpu: 4, make -j4 > >> > >> So, World+Kernel in somewhat under 22 hours. > >> > >> The "MaxObs*" figures were unchanged, so: > >> > >> Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki MaxObs(Act+Wir) > >> Swap: . . . , 537588Ki MaxObsUsed > >> > >> This suggests that, for now, 800 MiByte of swap would be something > >> more than 1.5 times what it actually used and 1050 MiBytes would > >> be something like 2.0 times what it actually used, so leaving some > >> notable margin for variations in peek usage, at least when linker > >> threading is avoided. > >> > >> > >> > >> As for what I used to control "what and how to build" . . . > >> > >> # more ~/sys_build_scripts.armv7-host/make_armv7_nodebug_clang_bootstrap-armv7-host.sh > >> kldload -n filemon && \ > >> script ~/sys_typescripts/typescript_make_armv7_nodebug_clang_bootstrap-armv7-host-$(date +%Y-%m-%d:%H:%M:%S) \ > >> env __MAKE_CONF="/root/src.configs/make.conf" SRCCONF="/dev/null" SRC_ENV_CONF="/root/src.configs/src.conf.armv7-clang-bootstrap.armv7-host" \ > >> WITH_META_MODE=yes \ > >> WORLD_FLAGS="${WORLD_FLAGS} UBLDR_LOADADDR=0x42000000" \ > >> MAKEOBJDIRPREFIX="/usr/obj/armv7_clang/arm.armv7" \ > >> make $* > >> > >> (In my context, UBLDR_LOADADDR is ignored by anything that > >> can not use the figure given. So I've no bothered to be > >> more selective about having it in the armv7 builds.) > >> > >> # more ~/src.configs/make.conf > >> LDFLAGS.lld+= -Wl,--threads=1 > >> > >> # more ~/src.configs/src.conf.armv7-clang-bootstrap.armv7-host > >> TO_TYPE=armv7 > >> # > >> KERNCONF=GENERIC-NODBG > >> TARGET=arm > >> .if ${.MAKE.LEVEL} == 0 > >> TARGET_ARCH=${TO_TYPE} > >> .export TARGET_ARCH > >> .endif > >> # > >> #WITH_CROSS_COMPILER= > >> WITH_SYSTEM_COMPILER= > >> WITH_SYSTEM_LINKER= > >> # > >> WITH_LIBCPLUSPLUS= > >> WITHOUT_BINUTILS_BOOTSTRAP= > >> WITH_ELFTOOLCHAIN_BOOTSTRAP= > >> #Disables avoiding bootstrap: WITHOUT_LLVM_TARGET_ALL= > >> WITHOUT_LLVM_TARGET_AARCH64= > >> WITH_LLVM_TARGET_ARM= > >> WITHOUT_LLVM_TARGET_MIPS= > >> WITHOUT_LLVM_TARGET_POWERPC= > >> WITHOUT_LLVM_TARGET_RISCV= > >> WITHOUT_LLVM_TARGET_X86= > >> WITH_CLANG= > >> WITH_CLANG_IS_CC= > >> WITH_CLANG_FULL= > >> WITH_CLANG_EXTRAS= > >> WITH_LLD= > >> WITH_LLD_IS_LD= > >> WITHOUT_BINUTILS= > >> # > >> WITH_LLDB= > >> # > >> WITH_BOOT= > >> WITHOUT_LIB32= > >> # > >> # > >> WITHOUT_WERROR= > >> #WERROR= > >> MALLOC_PRODUCTION= > >> WITH_MALLOC_PRODUCTION= > >> WITHOUT_ASSERT_DEBUG= > >> WITHOUT_LLVM_ASSERTIONS= > >> # > >> # Avoid stripping but do not control host -g status as well: > >> DEBUG_FLAGS+= > >> # > >> WITH_REPRODUCIBLE_BUILD= > >> WITH_DEBUG_FILES= > >> # > >> # Use of the .clang 's here avoids > >> # interfering with other CFLAGS > >> # usage, such as ?= usage. > >> CFLAGS.clang+= -mcpu=cortex-a7 > >> CXXFLAGS.clang+= -mcpu=cortex-a7 > >> CPPFLAGS.clang+= -mcpu=cortex-a7 > >> > >> (I do not claim that you would want WITH_REPRODUCIBLE_BUILD . > >> I just happen to have been experimenting with it. You might > >> not want to be explicit about the cpu to target. You might > >> not want WITH_CLANG_EXTRAS .) > >> > >> # more /usr/fbsd/mm-src/sys/arm/conf/GENERIC-NODBG > >> include "GENERIC" > >> > >> ident GENERIC-NODBG > >> > >> makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols > >> > >> options AUDIT # Not enabled by default in armv7/v6 kernels > >> # Enabled here to allow kyua test runs to > >> # possibly report auditing works. > >> > >> options ALT_BREAK_TO_DEBUGGER > >> > >> options KDB # Enable kernel debugger support > >> > >> # For minimum debugger support (stable branch) use: > >> options KDB_TRACE # Print a stack trace for a panic > >> options DDB # Enable the kernel debugger > >> > >> # Extra stuff: > >> #options VERBOSE_SYSINIT=0 # Enable verbose sysinit messages > >> #options BOOTVERBOSE=1 > >> #options BOOTHOWTO=RB_VERBOSE > >> options ALT_BREAK_TO_DEBUGGER # Enter debugger on keyboard escape sequence > >> options KLD_DEBUG > >> #options KTR > >> #options KTR_MASK=KTR_TRAP > >> ##options KTR_CPUMASK=0xF > >> #options KTR_VERBOSE > >> > >> # Disable any extra checking for. . . > >> nooptions INVARIANTS # Enable calls of extra sanity checking > >> nooptions INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS > >> nooptions WITNESS # Enable checks to detect deadlocks and cycles > >> nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > >> nooptions DEADLKRES # Enable the deadlock resolver > >> nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones > >> nooptions DIAGNOSTIC > >> nooptions BUF_TRACKING > >> nooptions FULL_BUF_TRACKING > >> nooptions USB_DEBUG > >> nooptions USB_REQ_DEBUG > >> nooptions USB_VERBOSE > >> > >> The /boot/loader.conf file and the /etc/sysctl.conf files > >> both contained: > >> > >> vm.pageout_oom_seq=120 > >> vm.pfault_oom_attempts=-1 > >> > >> (The hw.physmem=979042304 in /boot/loader.conf was very-special, > >> to better approximate your environment. I also controlled the > >> cpu frequency used via a line in /etc/sysctl.conf . I do not > >> bother with such non-default frequency usage [or related settings] > >> for RPi*'s with the pre-RPi4B style power connections but do > >> control the frequency for the OPi+2E.) > > > > The following had been left implicit about my context and > > how it manages memory space use. > > > > I'll note that I do not use tmpfs or other such memory based > > file system techniques that could compete for RAM/swap. What > > is in use for the only file system involved is just the > > root file system: > > > > # df -m > > Filesystem 1M-blocks Used Avail Capacity Mounted on > > /dev/gpt/BPIM3root 195378 63940 115808 36% / > > devfs 0 0 0 100% /dev > > > > It is a USB SSD. The swap partition is also on that same > > media. (The BPIM3 based name dates back to before the > > BPI-M3 power connection failed and I switched to the > > OPi+2E.) > > > > I'll note that I've started a new from-scratch build without > > LDFLAGS.lld+= -Wl,--threads=1 . So at some point I'll have > > information about how much of a difference (+/-) in swap > > usage it actually made for with vs. without, if any. > > Looks like, for such 4-core contexts, that bothering > with LDFLAGS.lld+= -Wl,--threads=1 is typically a > waste of effort for both swap usage and time . . . > > With LDFLAGS.lld+= -Wl,--threads=1 : > > Mem: . . . , 765700Ki MaxObsActive, 200412Ki MaxObsWired, 954116Ki MaxObs(Act+Wir) > Swap: . . . , 537588Ki MaxObsUsed > > without: > > Mem: . . ., 715756Ki MaxObsActive, 194816Ki MaxObsWired, 903132Ki MaxObs(Act+Wir) > Swap: . . ., 557208Ki MaxObsUsed > > > With LDFLAGS.lld+= -Wl,--threads=1 : > > World built in 72960 seconds, ncpu: 4, make -j4 > Kernel(s) GENERIC-NODBG built in 4998 seconds, ncpu: 4, make -j4 > > without: > > World built in 72804 seconds, ncpu: 4, make -j4 > Kernel(s) GENERIC-NODBG built in 4824 seconds, ncpu: 4, make -j4 > > > So, just not that much of a difference compared to the overall > sizes or times involved. > A first OS build/install cycle on armv7 (RPI2) using meta mode finished without trouble. Sources were a day or two newer than the kernel, -j4 buildworld took 157121 seconds. Peak swap use was half again as much at 732932. No constraints on ld.lld beyond defaults. I'm a little surprised at the extreme slowness, but this was a fully-debug'd-current kernel and sources were slightly newer than existing world. In case there's interest I've put what log files I could gather at http://www.zefox.net/~fbsd/rpi2/buildworld/main-c950-gff1a307801/ Thanks for your attention and help!! bob prohaska > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > From owner-freebsd-current@freebsd.org Thu Jan 21 03:20:12 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 12EFC4E6354 for ; Thu, 21 Jan 2021 03:20:12 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLnhB4R1tz4lsk for ; Thu, 21 Jan 2021 03:20:10 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: by mail-pg1-x52e.google.com with SMTP id p18so446827pgm.11 for ; Wed, 20 Jan 2021 19:20:10 -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:from:to:references:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=28ALQSLuS6N8TF3QX6x3A5MCbjMbvuhb3957YCNvJC0=; b=cPOfz7bx14bL/EuXuf0siF7MwJOqztcYjTJ+8EgY/sY3GqC5UNz4nvY7abG9ReMpZr K18nP1RFQWeiNpkqHjCmOvFy6WRv0QjUQ0J7JATepNnorn/ibeJdQBaRwm2uoRHfwpjt gDAxluaS7AkybeFZPqKVymL0frmVxY3oNFpKTK6PlG6orKepAYpSg4oMCZpyWSfyZijq A5+eyNMK1jIhf1G3bevncMhli6Fw5MJ7eahBrCgoNl3tin2GgJRFWiTrS54sboWOPGdh 9eR/iIUIw/6TTn5gIwXDX/9Nu//iimV2mqQjcJdkhUVO2CP4ISVQbfendFewUtYkpnTi mNZw== X-Gm-Message-State: AOAM531AkQlQIfqjjFRmsWldUwQgASOybIcrKsmD05tjQ6NdPhoYvK3S aA8F6BepJh5sHI947W1E91aGLA== X-Google-Smtp-Source: ABdhPJzdqDpyq6x7Z605/Yi1UE/D3hY+C7DdjCy/XV/ZuOdoNI2UVLR5HNKycUedcmhK08FWC8Q8yA== X-Received: by 2002:a62:1896:0:b029:197:491c:be38 with SMTP id 144-20020a6218960000b0290197491cbe38mr12177867pfy.15.1611199209054; Wed, 20 Jan 2021 19:20:09 -0800 (PST) Received: from macbook-2.local (c-71-238-26-71.hsd1.or.comcast.net. [71.238.26.71]) by smtp.gmail.com with ESMTPSA id m4sm3768745pgu.4.2021.01.20.19.20.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 19:20:07 -0800 (PST) Subject: Re: FreeBSD 13.0 Build Option Sweep From: Michael Dexter To: freebsd-current@freebsd.org References: Cc: kevans@freebsd.org Message-ID: Date: Wed, 20 Jan 2021 19:20:04 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DLnhB4R1tz4lsk X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[callfortesting-org.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::52e:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[71.238.26.71:received]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[callfortesting-org.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[callfortesting.org]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::52e:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::52e:from]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 03:20:12 -0000 On 1/20/21 5:47 PM, Michael Dexter wrote: > Two have been fixed and PRs exist for the majority of them with some > possible fixes for those who know the code best to consider. One broken > option is a recent regression while one pair, > WITHOUT_LIBTHR/WITHOUT_LIBPTHREAD is quite stale and is a candidate for > significant attention or possibly removal. Thank you Kyle for addressing the single greatest challenge I have described, with this review: https://reviews.freebsd.org/D28263 I have closed the PR. All the best, Michael From owner-freebsd-current@freebsd.org Thu Jan 21 04:46:36 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 818394E94BA for ; Thu, 21 Jan 2021 04:46:36 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic314-21.consmr.mail.gq1.yahoo.com (sonic314-21.consmr.mail.gq1.yahoo.com [98.137.69.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLqbv2clVz4s64 for ; Thu, 21 Jan 2021 04:46:35 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1611204393; bh=Q6tdiBSh+pauA23v9tIrkUHL/B4LX3+QPAg65MIhzer=; h=Subject:From:Date:To:From:Subject:Reply-To; b=b8WnBwO06FhSMjlc08nemK5jTsrV4t4MsaNksxyVrBbzRbl7pvEVJPQ3dSVh+p1ThnEYxKvjxu07HXhW1pHsM2z/3s61cUWk5yyRAw/Arl52F/TUEUC8JHHpfIXrfhpr8NGi8kcBo8PDah5ItdqOMwnS7QrJHEYJY3gboIsthXv0NyvYUGYUOHWvBYf/Hoa/bGK1Rs7ea1u7sYwMfeTYVoYrvKTnvouoLIAGyxCFJ7DjFuDLNj+tPgIc4vYS0HzlFVe2Jeogx6MnoNyZD+hRZoJpC+suiyOw8xx6twvJbWUum98CIc6lJX1hWhsvmHmSCbN+VO8z/Hfpkq4HMDdfsQ== X-YMail-OSG: dR.cp7kVM1mrszuCozoPelNESZsn5jRNjG7R9ChN8PFgBRsfj4vUzGa2ThJRjKX Cwf2mB1WBTP6ry16JUN8Q.IfLzl_mTMVYF1TC6w5XGZWoYuqN8kVl9Daew9aL.NSlMxA0pknnKdg biQNiWbkPb_Dkj8ByXKHcINnIBZ5hjOS0Fw6acrwXpi9F7IiKHN9zt9jT4UCAEPysqGSLOYze1Fn 15UaM6pX77M7e_ZpXPZM0SZHRn2zCEmiHTu3ayqkOGE_4KeaDVDPbdJ5vmdIhCAZ0NPdHc9WPu7a PAvhQOrgvh2kidKWwSlMXFhvVDLCYz1C_B4tPOQqArhqiHhBDjJqqvmceAfyvl69A9p.3h9wLSmr HwY0eK7lilD8ABMjiLkIb_55WEacaM7IPikhIMsN8cs0.ST0kjm7mr5CAhyZ3goyOjZH6kr6q7k5 _eaHU1ahJyT9WZh0Ab60KyrJFRVHNJjO5W7Ac7WWHgNfytTbNqQkugg0ujgQOtu7kUdsXVdv9QBx ubKNI.w38FFPmxkqBfkZ3tckoCQ7BDxRoVw_eOp2yf4alewdinHWpT3Ndglnl2_87PsP9aukwdFV 6D3.von5CaGYGDyBDXdmKB6BcVeVQzk1tYwa.H9J__XGPNc2GJopZx3Y02_10B4BIF82pLIXxhX_ 42boNP6tss68SaXNsTE99UFOj9JBLjc4GCKSDIwLLNFeb346q3j4FF0AhxOloHsiKlvmXGXlo3Qo NxNsAdu3DnrMO35483GWSJUNHPvIYNM.i5SlCWE95pwLzxTH8uUskJNpbkYF3DcbMfdpE28bneUK oiLwyu6CMp1hwS6dBSItLyXxEBWcLBlf8t9w_7kp64oSiEALgetkvOYXSaM3KJMcuBWKnQ0a1gD8 GmMDNEL_DRQtGsCxNmM_p.VDP.XBSOOPhiApAlFi1UtvHK_IwACbXVmgdeUYBm9uCp1IZknW5qus ndduKh2lNdnphvmzm3x14bUdMpghhJkNzV6kBxnjON.k8kAVjfLNy1Hhd820MNroWjp0BFjLNs3K O1.CgyZX58hZD.aNH8fsJArhmYuo4x_OHfMQvBvtNVwV_ls18OhI7UpP17JtbPtKdtsyAAgA7mCN LEAvO_IIYVr3y_peOkiVp5WSdnIgZ0YJN3LfjyynjlFuGcoATrcz2O1.koxPEejafDx7LoLdk06H iwjLEgpBG7VkhqoazihQP3lIvzHDAoOb2m47BH7_cBvfwFJZY5ng5G4JZl1vr3jLLQmLvtsNeRSq 7hBTDBRPWC_9o9Ea_f1.z2dw9aW98o_jIwtnb4qDflOnwqIkCmNx93uKUJp5n2OCEbyYm_aGWZtX S8dOLJ42qUrjtlXdyTHrwaje1A8OQOE4gCbtbEqO_BA0UcywSD38kkKDKfD7DD6GR.xaeyYQyEm5 gwCmUUKKJrXFBdPJ0OMoK8EIS.ghW2Uk79.2Luz0KtjeCFwvJmHcEvdXruK1J1bQdQg2gT0MS7r0 UqGf4coEdnFsDsLIllZiQ2nS3TfQ5Ac8VMb4nf8KN8HiOrucoZGesslks166WkSJY3fGeBZDmS.Y iS5w4RRKNq4G7DPd5nH.zZJetx6VyTtopgLxMSUJWiSLZs8gFgrbvCljy9oySC.Jh8IGjV1Ltjnl bjCU.IJbIpXo1zetOEAcGBI3atVmY.849jnt6qdi.BXnqgkVULAxv5CTK6EqJwjDcPdrwkQk7Tnd DSOWA0nPcnfrynG.SfrmxpRatqJbNtSNInZGfn5a.3MyZR37WTLePUKb4S9rvTa3Lv9Y04xTqkCq OpultnUJkNNVm1exjiRzOaeVr5pUScZQayJ5CnK8gC8DxsUZ93MhUPKo3ctwwiyc76TWrIW3JJX7 zscq.m4hCxgba4V1lBwre3.w9y8iMbRuYsd2WvZUWOPqy6UjkhZHBa8AN0TdWPwkEMH38lk2gpDY 5hO4eiWz.xeWQobdK86FZ2ParI9XpBr59QGnTrL3xdU.Pu1_1cAzYrzeeeBoMpo8pKiRHMV6_bj1 Ugy_xxbEkWRDVbDGVK1AwivTn4V6xa_uEH3goGvMFBtq5N7M.128dRWviEhx2V09h8D9rU_c2baq nun8q4iQk9Dfx7kqbHizQyxMddUsQAgoAILSCKzMP2JFOfhN9_W2CuSVyMx0Ufo0KhNmay9FjqTO 3gs.V2FAVjyPZ.znTi6ViaVcyI1p9HLw05MjBi.0lim1Flx_vEnN4EuzsXB4gRW6z6FXy2F_KF6J qgrAU89TDzdSVkra9.8qq.C2Z3WUMKnesczTS4OJ2hqUKV45Ya_0.0KVipnlzWlDeIWGf5rC05ft 0oPLB_iUVXuvG1Pbj508WKd1oTN2tjD9u2k0OB3jREjiPyVTbE3FMEu.6NW7BaMegdyn_LrIIyA7 .nyKMhvmc09s1PoQKWgvv01V5.ZHK.KOvwBpXzSfbkEU.RmA2m7G2k0Dzk8GsIimsTWvkyvIkSFk vXpIAk_RqstMwzBOZzGongsjO_3sd7deLZVDcU_5iEQAV6FAam3NrZrYsj12iM6X5zRycHaCdStP siTpdXHKzoC0fxuP_US2S2mpJwUVOrqRa4eSMcL8xj2gCz8HkILanV9XY1PPYNQTiXVDE.AAQlfF MxPZqLqZw8BvVtW8EuLxX3PODetB4yr8H9euiHYFrc9WXVrAPPYY9N7_TCAI- Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.gq1.yahoo.com with HTTP; Thu, 21 Jan 2021 04:46:33 +0000 Received: by smtp425.mail.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 209cfd8f6f68de0991eb03b51cd3fcc5; Thu, 21 Jan 2021 04:46:30 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Silent hang in buildworld, was Re: Invoking -v for clang during buildworld From: Mark Millard In-Reply-To: <20210121023358.GA58854@www.zefox.net> Date: Wed, 20 Jan 2021 20:46:28 -0800 Cc: Current FreeBSD , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8D0C2A4C-B616-47B9-864E-D846A6EBA3D6@yahoo.com> References: <20210117174006.GA30728@www.zefox.net> <85889EAE-F579-4220-9185-944D9AA5075A@yahoo.com> <20210118015009.GA31353@www.zefox.net> <60CCCDE8-E3D3-4920-9FC0-A945330F6830@yahoo.com> <00104FAD-E32B-4DDE-80DD-FCEF14CEC06B@yahoo.com> <056845FE-7131-4951-96AF-805D07F7BE0D@yahoo.com> <20210121023358.GA58854@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DLqbv2clVz4s64 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.69.84:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.69.84:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.84:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.84:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 04:46:36 -0000 On 2021-Jan-20, at 18:33, bob prohaska wrote: >> . . . > A first OS build/install cycle on armv7 (RPI2) using meta mode=20 > finished without trouble. Sources were a day or two newer than=20 > the kernel, -j4 buildworld took 157121 seconds. Peak swap use=20 > was half again as much at 732932. No constraints on ld.lld=20 > beyond defaults. I'm a little surprised at the extreme slowness, > but this was a fully-debug'd-current kernel and sources were > slightly newer than existing world. >=20 > In case there's interest I've put what log files I could gather at > http://www.zefox.net/~fbsd/rpi2/buildworld/main-c950-gff1a307801/ The first META_MODE build has no META_MODE information from the prior build. You might want to have META_MODE do a build without updating sources and leaving the existing build materials in place. It would give you an idea of the lower bound on how much time a minimal build would take in your context. On the OPi+2E, for my context, for no linking-thread constraint, an example was: World built in 1468 seconds, ncpu: 4, make -j4 Kernel(s) GENERIC-NODBG built in 116 seconds, ncpu: 4, make -j4 So, somewhat under 30 minutes total. (There can be some things that do get some rebuild activity in such a build. Lots of things can end up relinked, so .full and .debug and such regenerated.) I'll note that for META_MODE to work well, you need to keep using it so that its records stay up to date as a description of the build materials that are to be the basis for the next update. Forgetting to supply WITH_META_MODE would not be good for approximately minimizing the rebuild work done. I've never tried to compare how much more memory is used under a debug kernel than a non-debug one. My use of non-debug vs. your use of debug could explain a lot for both memory use and some part of the time difference compared to my reports. I've only used a debug kernel to buildworld or buildkernel when trying to get evidence for a system problem that was occurring during build* operation(s). QUOTE (from UPDATING) NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW: FreeBSD 13.x has many debugging features turned on, in both the = kernel and userland. These features attempt to detect incorrect use of system primitives, and encourage loud failure through extra = sanity checking and fail stop semantics. They also substantially = impact system performance. If you want to do performance measurement, benchmarking, and optimization, you'll want to turn them off. = This includes various WITNESS- related kernel options, INVARIANTS, = malloc debugging flags in userland, and various verbose features in the kernel. Many developers choose to disable these features on = build machines to maximize performance. (To completely disable malloc debugging, define WITH_MALLOC_PRODUCTION in /etc/src.conf and = rebuild world, or to merely disable the most expensive debugging = functionality at runtime, run "ln -s 'abort:false,junk:false' = /etc/malloc.conf".) END QUOTE I was using a 1008 MHz clocked OPi+2E. You may well have been using a 600 MHz clocked RPi2B. I do not know if there are L1 or L2 RAM caching differences involved. There are enough differences to not make the variations in figures from our runs all that surprising. I see that you kept the 2048 MiByte total swap space, so still exceeding the documented recommended-maximum for the context. Since it used under 800 MiBytes, it would seem that it would fit to use more like <=3D1800 MiByte to avoid what the documentation warns about for tradeoffs for having too much swap space. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Thu Jan 21 05:46:55 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E587B4EAF5C for ; Thu, 21 Jan 2021 05:46:55 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLrxV47mRz4vqP for ; Thu, 21 Jan 2021 05:46:54 +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.16.1/8.16.1) with ESMTPS id 10L5kkBM061724 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Wed, 20 Jan 2021 21:46:46 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 10L5kkI2061723 for freebsd-current@freebsd.org; Wed, 20 Jan 2021 21:46:46 -0800 (PST) (envelope-from sgk) Date: Wed, 20 Jan 2021 21:46:46 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: make buildkernel is broken (linuxkpi vs drm) Message-ID: <20210121054646.GA61716@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 4DLrxV47mRz4vqP X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.97 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.95.76.21:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[128.95.76.21:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.971]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM, none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 05:46:56 -0000 My buildkernel after a buildworld is dying with In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/pci.h:10: In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/pci.h:51: In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/dmapool.h:36: In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/scatterlist.h:32: In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/scatterlist.h:36: In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/slab.h:43: In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/llist.h:64: In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/kernel.h:4: In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/kernel.h:49: In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/sched.h:4: In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/sched.h:41: /usr/src/sys/compat/linuxkpi/common/include/linux/bitmap.h:338:10: error: implicit declaration of function 'kmalloc_array' is invalid in C99 [-Werror,-Wimplicit-function-declaration] I have removed the drm-current-kmod port and still get this error. -- Steve From owner-freebsd-current@freebsd.org Thu Jan 21 06:07:44 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5051D4EB664 for ; Thu, 21 Jan 2021 06:07:44 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLsPW2jkTz3CrL for ; Thu, 21 Jan 2021 06:07:43 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 54F6B2604A4; Thu, 21 Jan 2021 07:07:38 +0100 (CET) Subject: Re: make buildkernel is broken (linuxkpi vs drm) To: Steve Kargl , freebsd-current@freebsd.org References: <20210121054646.GA61716@troutmask.apl.washington.edu> From: Hans Petter Selasky Message-ID: Date: Thu, 21 Jan 2021 07:07:27 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <20210121054646.GA61716@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DLsPW2jkTz3CrL X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.29 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net:c]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:4f8:c17:6c4b::2:from]; SPAMHAUS_ZRD(0.00)[2a01:4f8:c17:6c4b::2:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.99)[-0.989]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 06:07:44 -0000 On 1/21/21 6:46 AM, Steve Kargl wrote: > My buildkernel after a buildworld is dying with > > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/pci.h:10: > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/pci.h:51: > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/dmapool.h:36: > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/scatterlist.h:32: > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/scatterlist.h:36: > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/slab.h:43: > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/llist.h:64: > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/kernel.h:4: > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/kernel.h:49: > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/sched.h:4: > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/sched.h:41: > /usr/src/sys/compat/linuxkpi/common/include/linux/bitmap.h:338:10: error: implicit declaration of function 'kmalloc_array' is invalid in C99 [-Werror,-Wimplicit-function-declaration] > > I have removed the drm-current-kmod port and still get this error. > Is /usr/src and /usr/ports up-to-date ? --HPS From owner-freebsd-current@freebsd.org Thu Jan 21 06:13:12 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B73A04EBE35 for ; Thu, 21 Jan 2021 06:13:12 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLsWr0rs1z3D8q for ; Thu, 21 Jan 2021 06:13:11 +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.16.1/8.16.1) with ESMTPS id 10L6DAoN061895 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 20 Jan 2021 22:13:10 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 10L6DASZ061894; Wed, 20 Jan 2021 22:13:10 -0800 (PST) (envelope-from sgk) Date: Wed, 20 Jan 2021 22:13:10 -0800 From: Steve Kargl To: Hans Petter Selasky Cc: freebsd-current@freebsd.org Subject: Re: make buildkernel is broken (linuxkpi vs drm) Message-ID: <20210121061310.GA61889@troutmask.apl.washington.edu> References: <20210121054646.GA61716@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4DLsWr0rs1z3D8q X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.95.76.21:from]; SPAMHAUS_ZRD(0.00)[128.95.76.21:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM, none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 06:13:12 -0000 On Thu, Jan 21, 2021 at 07:07:27AM +0100, Hans Petter Selasky wrote: > On 1/21/21 6:46 AM, Steve Kargl wrote: > > My buildkernel after a buildworld is dying with > > > > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/pci.h:10: > > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/pci.h:51: > > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/dmapool.h:36: > > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/scatterlist.h:32: > > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/scatterlist.h:36: > > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/slab.h:43: > > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/llist.h:64: > > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/kernel.h:4: > > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/kernel.h:49: > > In file included from /media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/sched.h:4: > > In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/sched.h:41: > > /usr/src/sys/compat/linuxkpi/common/include/linux/bitmap.h:338:10: error: implicit declaration of function 'kmalloc_array' is invalid in C99 [-Werror,-Wimplicit-function-declaration] > > > > I have removed the drm-current-kmod port and still get this error. > > > > Is /usr/src and /usr/ports up-to-date ? > It is 'make buildkernel' in /usr/src after a 'make buildworld'. I have 'PORTS_MODULES+= graphics/drm-current-kmod' in /etc/make.conf. -- Steve From owner-freebsd-current@freebsd.org Thu Jan 21 06:18:20 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8552A4EBF8F for ; Thu, 21 Jan 2021 06:18:20 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLsdl4QM3z3DVt for ; Thu, 21 Jan 2021 06:18:19 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id DAA392604A4; Thu, 21 Jan 2021 07:18:17 +0100 (CET) Subject: Re: make buildkernel is broken (linuxkpi vs drm) To: Steve Kargl Cc: freebsd-current@freebsd.org References: <20210121054646.GA61716@troutmask.apl.washington.edu> <20210121061310.GA61889@troutmask.apl.washington.edu> From: Hans Petter Selasky Message-ID: Date: Thu, 21 Jan 2021 07:18:07 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <20210121061310.GA61889@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DLsdl4QM3z3DVt X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.29 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net:c]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:4f8:c17:6c4b::2:from]; SPAMHAUS_ZRD(0.00)[2a01:4f8:c17:6c4b::2:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.99)[-0.990]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 06:18:20 -0000 On 1/21/21 7:13 AM, Steve Kargl wrote: > It is 'make buildkernel' in /usr/src after a 'make buildworld'. > I have 'PORTS_MODULES+= graphics/drm-current-kmod' in /etc/make.conf. Try to update the ports tree. I'm not aware of any current build issues in this area. --HPS From owner-freebsd-current@freebsd.org Thu Jan 21 06:21:11 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5C5014EC29B for ; Thu, 21 Jan 2021 06:21:11 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLsj25Sfzz3Dcg for ; Thu, 21 Jan 2021 06:21:10 +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.16.1/8.16.1) with ESMTPS id 10L6L9Ko061992 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 20 Jan 2021 22:21:09 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 10L6L9rY061991; Wed, 20 Jan 2021 22:21:09 -0800 (PST) (envelope-from sgk) Date: Wed, 20 Jan 2021 22:21:09 -0800 From: Steve Kargl To: Hans Petter Selasky Cc: freebsd-current@freebsd.org Subject: Re: make buildkernel is broken (linuxkpi vs drm) Message-ID: <20210121062109.GB61941@troutmask.apl.washington.edu> References: <20210121054646.GA61716@troutmask.apl.washington.edu> <20210121061310.GA61889@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4DLsj25Sfzz3Dcg X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.95.76.21:from]; SPAMHAUS_ZRD(0.00)[128.95.76.21:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 06:21:11 -0000 On Thu, Jan 21, 2021 at 07:18:07AM +0100, Hans Petter Selasky wrote: > On 1/21/21 7:13 AM, Steve Kargl wrote: > > It is 'make buildkernel' in /usr/src after a 'make buildworld'. > > I have 'PORTS_MODULES+= graphics/drm-current-kmod' in /etc/make.conf. > > Try to update the ports tree. I'm not aware of any current build issues in > this area. > I tried that. I did not fix the problem. Commenting out the PORTS_MODULES line in /etc/make.conf allows me to finish building the new kernel. I re-install the port after I install world/kernel. -- Steve From owner-freebsd-current@freebsd.org Thu Jan 21 10:50:24 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CA4784F12F9 for ; Thu, 21 Jan 2021 10:50:24 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLzgg5MsCz3kPX; Thu, 21 Jan 2021 10:50:23 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from skull.home.blih.net (lfbn-idf2-1-745-114.w86-247.abo.wanadoo.fr [86.247.192.114]) by mx.blih.net (OpenSMTPD) with ESMTPSA id f9311d74 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 21 Jan 2021 10:50:15 +0000 (UTC) Date: Thu, 21 Jan 2021 11:50:15 +0100 From: Emmanuel Vadot To: Steve Kargl Cc: Hans Petter Selasky , freebsd-current@freebsd.org, John Baldwin Subject: Re: make buildkernel is broken (linuxkpi vs drm) Message-Id: <20210121115015.460ecc9b854480f41b7cc97d@bidouilliste.com> In-Reply-To: <20210121062109.GB61941@troutmask.apl.washington.edu> References: <20210121054646.GA61716@troutmask.apl.washington.edu> <20210121061310.GA61889@troutmask.apl.washington.edu> <20210121062109.GB61941@troutmask.apl.washington.edu> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DLzgg5MsCz3kPX X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; FREEFALL_USER(0.00)[manu]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MV_CASE(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; SPAMHAUS_ZRD(0.00)[212.83.155.74:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.83.155.74:from]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 10:50:24 -0000 On Wed, 20 Jan 2021 22:21:09 -0800 Steve Kargl wrote: > On Thu, Jan 21, 2021 at 07:18:07AM +0100, Hans Petter Selasky wrote: > > On 1/21/21 7:13 AM, Steve Kargl wrote: > > > It is 'make buildkernel' in /usr/src after a 'make buildworld'. > > > I have 'PORTS_MODULES+= graphics/drm-current-kmod' in /etc/make.conf. > > > > Try to update the ports tree. I'm not aware of any current build issues in > > this area. > > > > I tried that. I did not fix the problem. Commenting > out the PORTS_MODULES line in /etc/make.conf allows > me to finish building the new kernel. I re-install > the port after I install world/kernel. > > -- > Steve Does it works now ? I think that PORTS_MODULES shouldn't be used for drm-current-kmod or we should not install the source with it if PORTS_MODULES is the right way. The problem is that drm-current-kmod install its sources in /usr/local/sys and by default all modules there will be rebuild when doing make buildkernel unless LOCAL_MODULES is defined. The problem with installing sources is that if something changed in base that broke the build with a certain version of drm-current-kmod you first need to upgrade the ports/package to have the new sources to be able to make buildkernel correctly. I personally hate the fact that we install the sources as it only causes problems for users but some people seems to like it. It seems that if we don't install the sources and one uses PORTS_MODULES we just need to upgrade the ports tree before running make buildkernel if there is a conflicting changes which seems saner to me tbh. For now I've been focusing the rage that LOCAL_MODULES exists and cause this kind of problems on migrating more stuff into base so that one day we will finally have drm in base again. But I'm a bit tired of dealing with all those problems and I've wondered a lot of times about removing installing sources for drm-current-kmod. Adding jhb@ to cc as I know he uses LOCAL_MODULES so maybe he can explain the advantage over PORTS_MODULES. -- Emmanuel Vadot From owner-freebsd-current@freebsd.org Thu Jan 21 17:14:42 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 408C24D9ECF for ; Thu, 21 Jan 2021 17:14:42 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DM8C5491nz4dKW; Thu, 21 Jan 2021 17:14:40 +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.16.1/8.16.1) with ESMTPS id 10LHEXbL063915 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 21 Jan 2021 09:14:33 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 10LHEWwS063914; Thu, 21 Jan 2021 09:14:32 -0800 (PST) (envelope-from sgk) Date: Thu, 21 Jan 2021 09:14:32 -0800 From: Steve Kargl To: Emmanuel Vadot Cc: Hans Petter Selasky , freebsd-current@freebsd.org, John Baldwin Subject: Re: make buildkernel is broken (linuxkpi vs drm) Message-ID: <20210121171432.GA63900@troutmask.apl.washington.edu> References: <20210121054646.GA61716@troutmask.apl.washington.edu> <20210121061310.GA61889@troutmask.apl.washington.edu> <20210121062109.GB61941@troutmask.apl.washington.edu> <20210121115015.460ecc9b854480f41b7cc97d@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210121115015.460ecc9b854480f41b7cc97d@bidouilliste.com> X-Rspamd-Queue-Id: 4DM8C5491nz4dKW X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 17:14:42 -0000 On Thu, Jan 21, 2021 at 11:50:15AM +0100, Emmanuel Vadot wrote: > On Wed, 20 Jan 2021 22:21:09 -0800 > Steve Kargl wrote: > > > On Thu, Jan 21, 2021 at 07:18:07AM +0100, Hans Petter Selasky wrote: > > > On 1/21/21 7:13 AM, Steve Kargl wrote: > > > > It is 'make buildkernel' in /usr/src after a 'make buildworld'. > > > > I have 'PORTS_MODULES+= graphics/drm-current-kmod' in /etc/make.conf. > > > > > > Try to update the ports tree. I'm not aware of any current build issues in > > > this area. > > > > > > > I tried that. I did not fix the problem. Commenting > > out the PORTS_MODULES line in /etc/make.conf allows > > me to finish building the new kernel. I re-install > > the port after I install world/kernel. > > > > -- > > Steve > > Does it works now ? Haven't got to the point of re-installing drm-current-kmod. For some reason, the newly built kernel is panicking, and it panics either before or during keyboard probe so I have no keyboard. Need to figure out to use git to back up to mid-december source tree. -- Steve From owner-freebsd-current@freebsd.org Thu Jan 21 18:09:53 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 618DD4DAECE for ; Thu, 21 Jan 2021 18:09:53 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DM9Qn0t53z4h4m for ; Thu, 21 Jan 2021 18:09:53 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: by mailman.nyi.freebsd.org (Postfix) id 1C1134DAE44; Thu, 21 Jan 2021 18:09:53 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1ABC24DB2C7 for ; Thu, 21 Jan 2021 18:09:53 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DM9Ql6Z4Jz4hLR for ; Thu, 21 Jan 2021 18:09:51 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from outgoing.leidinger.net (p5b1652bf.dip0.t-ipconnect.de [91.22.82.191]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (Client did not present a certificate) by mailgate.Leidinger.net (Postfix) with ESMTPSA id ECD34282D for ; Thu, 21 Jan 2021 19:09:41 +0100 (CET) Received: from webmail.leidinger.net (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (Client did not present a certificate) by outgoing.leidinger.net (Postfix) with ESMTPS id D8EF92287 for ; Thu, 21 Jan 2021 19:09:38 +0100 (CET) Date: Thu, 21 Jan 2021 19:09:38 +0100 Message-ID: <20210121190938.Horde.t6HhHqNSRjmOYQcnkW-1Rf4@webmail.leidinger.net> From: Alexander Leidinger To: current@freebsd.org Subject: panic rtentry / hashdestroy /in6_purgeaddr related? Accept-Language: de,en Content-Type: multipart/signed; boundary="=_1WGw09thKtKuprmhhWl_MCm"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-Rspamd-Queue-Id: 4DM9Ql6Z4Jz4hLR X-Spamd-Bar: - X-Spamd-Result: default: False [-1.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[89.238.82.207:from]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[89.238.82.207:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(1.00)[1.000]; DKIM_TRACE(0.00)[leidinger.net:+]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[current]; RECEIVED_SPAMHAUS_PBL(0.00)[91.22.82.191:received] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 18:09:53 -0000 This message is in MIME format and has been PGP signed. --=_1WGw09thKtKuprmhhWl_MCm Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, -current at d7fc908cffa as of 2021-01-20-154143. I've seen several failures to free an rtentry on the console shortly=20=20 before=20the panic. May or may not be related..._ ---snip--- in6_purgeaddr: err=3D65, destination address delete failed Freed UMA keg (rtentry) was not empty (1 items). Lost 1 pages of memory. j_gallery_hif: link state changed to DOWN j_gallery_jif: link state changed to DOWN samba.leidinger.net in6_purgeaddr: err=3D65, destination address delete failed Freed UMA keg (rtentry) was not empty (1 items). Lost 1 pages of memory. j_samba_hif: link state changed to DOWN j_samba_jif: link state changed to DOWN ---snip--- This is on shutdown with 22 vnet jails: ---snip--- Unread portion of the kernel message buffer: <6>in6_purgeaddr: err=3D65, destination address delete failed panic: hashdestroy: hashtbl 0xfffff80be7108800 not empty (malloc type ifadd= r) cpuid =3D 14 time =3D 1611248408 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0064b55= b10 vpanic() at vpanic+0x181/frame 0xfffffe0064b55b60 panic() at panic+0x43/frame 0xfffffe0064b55bc0 hashdestroy() at hashdestroy+0x54/frame 0xfffffe0064b55bd0 vnet_destroy() at vnet_destroy+0x146/frame 0xfffffe0064b55c00 prison_deref() at prison_deref+0x28e/frame 0xfffffe0064b55c40 taskqueue_run_locked() at taskqueue_run_locked+0xb0/frame 0xfffffe0064b55cc= 0 taskqueue_thread_loop() at taskqueue_thread_loop+0x97/frame 0xfffffe0064b55= cf0 fork_exit() at fork_exit+0x85/frame 0xfffffe0064b55d30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0064b55d30 ---snip--- Full crashinfo output available on request. Kerneldump is also=20=20 available=20if you want I peek into it at some specific place. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_1WGw09thKtKuprmhhWl_MCm Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJgCcNiAAoJEBINsJsD+NiGm6gP/ArKAyCBAudGdJ8gvyeBSXf8 jSLJDKd6YyRsQoo31WkCh/yQmDv/j867q1ti4Nm8VasXhxgC26mD1bSehXx0gA8O pL3LZjyegqIG3joX0sjqi5p4f+Ps405gd0Gfw+XVhCnNNf/+REchmxQdDKaSG8/s BSlnDE8VBI2MI+GP9DfyN1I+bDiOLbEYB4iGXEpP1yN3YF/Y7QDIE+nWKo6jU9M+ AqxkhT0e/5269kIvcJcUyABVunCJZ9dkwqd7DxORB/bX+X6ZNnA5DGTx7TWY4ixv ttIa7EK6n46vFzAnjhfnlZqdBwy/OvunhiIFD/zCsfDDNx8ytAyULdbQvXtDUk8T HXF3lNkXpJiGDLoXEj+1SloOJP1/rOJlICvKNecAfx6GLnMR0XlNszOYrphHv2FG kPqpJHmf7m/UrefTQskD09nXo4iK833c++EJv8goV3KY/RFY13wM26QHjYeVx3Cr v3fAAc3WYtYapPL27oEjkdS1xdMmZcoSpaaOgZ7F8eoM2Me0YDGTKvgDkbD1+Zlu dPSJ/AXXGIj+zjf7AUs/pxFHlsxO5S5Mp2wAwA1ykdrnyTUOVu8JGuHyMt/I+tui QaXhNCiMHH6CsIqVoNpyKYhdEk6DoSEInIkkaRS0owGOPpXDS5bqOdwFiLlY/rSo eoYT9+WNmDsyNzLYew24 =SOTK -----END PGP SIGNATURE----- --=_1WGw09thKtKuprmhhWl_MCm-- From owner-freebsd-current@freebsd.org Thu Jan 21 21:59:51 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A34BA4E1266 for ; Thu, 21 Jan 2021 21:59:51 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic301-22.consmr.mail.gq1.yahoo.com (sonic301-22.consmr.mail.gq1.yahoo.com [98.137.64.148]) (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 4DMGX55m7dz3FhP for ; Thu, 21 Jan 2021 21:59:49 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1611266387; bh=67KwvQ+fpXbiAkAFiVa7r/N0rI2PpPCwX2cuEz0zphA=; h=Subject:From:Date:To:From:Subject:Reply-To; b=IG0j6QZ5T/Lirp6QKtiT8O3qt1OVDO3/m7C/9Jnla6XL3k+RbP2JAv5hXIqIzWMWT5I1+MVm+UsFhW10/GQWD2tF36WTlHBpR9Yikx3YjSWMHj7/lkmHJTu7s2I3f2ulim0KFLOASIma1bgwFSqW9hIqFa95qwvFkOtOANgqzI6OLjdeilLIYlPrh3VEEMp/1SHXXAp4SIUUivlAwxpxSjV2H6FzD+6BYD1FWLfptFWuyCoX3lQ58HlP5w78ThPKIFhGRPWaBgeXFWFnvXA6p0UaegWoMcJlXr8xP4A3iRWCrOk9e7jK1OfFYYOnebkklc5r1TKFXvAOmwDDrBxoFg== X-YMail-OSG: ukV8NGwVM1kMTsnyY5.T4hLEAzpnSfv8JXMleGdXhn4utcB585QGr83gcqgPQuo 6nrw8lxrnc0VZhjs5mBGKCOjE2Vl4EeWY2o09MMRl89ixq9wIhDMQHK5ZhOWGeD3dY8Av.hwGeSb 0bd7sYVu7oD0KTWnTXDiN66pyokMYD3CLoZr015fxUyh5uxLpuVKQUTzn2CbHKKVPr35HTJPDblb ntnYsxgoPynIHDvs_43AX9YvJpdVyMNdGWIl1crhCHO0u.YwdyjTouescB7lPNvk.U5Ckt6yX3IT QTRO434UnjeAtlOyLrbZaUI9Fz5pdBe2ZGyk2x3RqQ3JUMibyRyjfe9p8KqF7TAqKqJZQv7Veby5 3XPSddmPzqgEmoDjuc43Q8dCRex4Z_mz4MPSqAYGiAIUTaGS9jx25.CUwDm0FtR9wqYNnBGwCR90 WgSlIdinu_z.Y8An5Bfwv304BrbjN.mZgH_FsWEUr7uTj5eRbNBOjrRdz9P_Tvqyny42jyepDU1Y ow9TBFZxLy67IKcQ7KtK.JjEO4cZJvuBnyXsvfctSSzL4bO5pPZuUX6cH25Ibpsf.AmSTn6LJO8r j9mSCfmg3xcu7ipkjROX6HyDOqqktpFLIf.lqbFLZmWOpeh2WEQoa8TpgpEiOXlPkvenWNNNsEhD YLwDWjLgJVTu.G94oPWNjHFg81.vLqLbwK84UctNPE5a.6smq7vvYAWRz84eCMJQ023CUkRYLnIh uFx9gTVuchts9P_K6il6sGXD.vRld87.0rUu1io9FGTruyZ2idAnfDonLeddGzMKf3tPxWE0iwZ7 UD7xZ8wjJ1NMoRthuPE2m0zxEQGUFxf7OmmXrQD5BFCHIEhUKBoC4RkQz3rMgnhATY2ezOkm7BDv Hor9d0oDWaGQ3DDmrTHJhF5KuKhBG4tQfvCPcHwndh3LA1O3AsQ762813rA8uxVQHIm2t6yY22zl rlhH0ghcPNcQFErqlWJSve.Uh9JtsLMyuFRK6ck9ZMNezBhiVqRXOKch9WyXhX4d8LWJFZ0ZsyTc PmFczCtFrVzD5rfjCqA6h0X7QHb1BGxSwdhXztPraSkubQ.CeSE9Nz1aMzENuS7sI100X5x9YDHo 155pFJSrfLMMEYlq4eOe99EjU3WgJA7PiQ99fA1F3gcNRMGPK057820gUcEp0YcBufjYwu3zMhXp XVVyyz1d3g1kY1hrK5n.O0wlQIlNhA6XhrH3I5JieyKOK7nve2TynRsEg0hXK70dQcWK_ZJboIpa jjU8QmbVj7H3LVEDKgVaLU3EtU4BuHL8MUpSzJfyUeUntmhTlhGvdcrrFH2vgluqTF3_nwROtfpf s5gwVqn_IFvD15YtKPK.RIbyYvcXHW093vxivTOSkrVNU5cb41kP8QQ5o_N34jGEnJP8kq4jATtL yGzqSn51g.n2mh3o3TBe__WL3ZvPf1SnW1vMmPup9BKycge2rcuGootY6WsKq1UEfQcn7PH0o6.e VG0Utj85cnF25b7XGeK0B3TVn48Z2pwTBLM3LqOgwYmb1fmAmGgdOFnVIis1BXMo3IVTw0iJW2Kq aczZi3..ScHY_q7BA9DWM_XCuSSbTQxsFK3736rtxmxpAGdlvBdVrMutxnd8iGqMIMqIpx6ar4BN RY0Ns5uTXnDmemtoZxHrzoQ9PVjb2_iwrxE7U7AW3eSy5valIzG2BDz9WvGmLFbtqTHNn4xFJm3i zll1l_2VdmlXKFajsMIhmNbC9P93irmO3zhgRUc_2HtliVNCODpHKEca4njSUw6MPDP_QEcBO9WI xdQQPs522CDTuzUvgGT3zUsIRR4XHcUqCp7KFKyewy8snKMGxOIgIjXM11qyaR2MzmZ1n8UjvCvy .xmfo_DHbRxMLEZbeMo.HILDabBAO3sC9Xs.LPHLu.X_ARnZ5rJSWOFxJcX03JEvz6w8DOvwUXOt YW3kFMF8NVFnr0_L8dbh4hWCiJcuWRtoA8en6v50Sw_dMDpA3XtMM.VebTwZZ3hY_db4pH06sOpk vEM.7HGmSneiXL7hdziVq6ha.pG72PP8.3KBD.jermo1c3OE2gsDu4UJmFbv6NAURpbT6LqLjjKR jTbQdLonCys_LHbmsQdJYinMfIOiME8ikB6PmaHqIoGcjJj28.tAAqOeQbXsS4joOrDb_euagFeq BtADkqwogwUzoBaL8QWdbGDagM8HVBF5YAsbg.Zlmy.88ugIVd2EVMM9Ypz6HpM1fQLthLebKc_U VuuX7oUA55AF9E1hf.4Fm4OvPXEO8lJIS0cXDOMDAn_oeOg4rM2hfoCUoJzcJxOfkdWh4OMyiNri ArL6PiLfwC29Pt8JyIxyEpS_33NdqSEzVPMposWWoVASCYlcjQOA_9MU1zUK21tQZqeQOyacwGh8 Tu9a4OJu5T3O01h6ZuXDqc7kxbQOkxRMpyOrhx5G4DMHA.fNYbYgXQghxk5cIcdIaEA4g.7gQm7c MVrmuVmv5NdlTHlvYUWKYOB76jCn.P2MdI.GgosKihLWtmyYMpq4WF2U3QsmU50UdRBm1V7kOu8T HRUSXWXfWvBUU3GhKQrcEpFV1jTEzmhHE_SF_h4MCpfvwwtOZOAubpA33qjRiuN9MKF4jWf8- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.gq1.yahoo.com with HTTP; Thu, 21 Jan 2021 21:59:47 +0000 Received: by smtp417.mail.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 9a6415102952294e6c6cf7b792cd5d1a; Thu, 21 Jan 2021 21:59:43 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: git: a9fc14fbf445 - main - newvers.sh: add support for gitup(1) [the removal of git branch information] From: Mark Millard In-Reply-To: <38C7FD1F-4C7D-4EFC-8217-95CF4ECDB5A5@yahoo.com> Date: Thu, 21 Jan 2021 13:59:41 -0800 Cc: Current FreeBSD Content-Transfer-Encoding: quoted-printable Message-Id: References: <38C7FD1F-4C7D-4EFC-8217-95CF4ECDB5A5@yahoo.com> To: dev-commits-src-main@freebsd.org X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4DMGX55m7dz3FhP X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.03 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.53)[-0.531]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.64.148:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.64.148:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.148:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.148:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 21:59:51 -0000 On 2021-Jan-21, at 09:24, Mark Millard wrote: > Ulrich Sp=C3=83=C2=B6rlein uqs at FreeBSD.org wrote on > Wed Jan 20 09:49:49 UTC 2021 : >=20 >> While here, drop the redundant branch name from the git output and = don't >> count commits in shallow clones. >>=20 >=20 > The branch name part of the patch breaks how I work with multiple > branches and I will be locally "reverting" it in my branches > unless FreeBSD itself reverts it. For my context it even breaks > how I would work for main vs. stable/12 if I ever did something > with stable/12 . (I'm not using shallow clones, it is the branch > name removal that messes up my specific way of working.) In other > words, for how I choose to work, the branch name is not redundant. >=20 > Going in another direction: mixing gitup/clone-counting and the > branch name removal in the same commit and in the code structure > means that I'm unable to just skip a commit to deal with the > branch name issue. I had an exchange with Michael Osipov and he reports that he "advocated to have" the git branch information. So, for: "While here, drop the redundant branch name from the git output" do not take the content of the commit log as indicating that Michael Osipov was asking for this part of the change. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Thu Jan 21 23:10:22 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AC4974E29B5 for ; Thu, 21 Jan 2021 23:10:22 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DMJ5V2tnMz3Kht for ; Thu, 21 Jan 2021 23:10:22 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: by mailman.nyi.freebsd.org (Postfix) id 616C74E2ABF; Thu, 21 Jan 2021 23:10:22 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 612F14E2ABE for ; Thu, 21 Jan 2021 23:10:22 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward501j.mail.yandex.net (forward501j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::111]) (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 4DMJ5V1Pqnz3KNM for ; Thu, 21 Jan 2021 23:10:21 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from vla1-765d064640cd.qloud-c.yandex.net (vla1-765d064640cd.qloud-c.yandex.net [IPv6:2a02:6b8:c0d:90b:0:640:765d:646]) by forward501j.mail.yandex.net (Yandex) with ESMTP id 1463633800AC; Fri, 22 Jan 2021 02:10:18 +0300 (MSK) Received: from localhost (localhost [::1]) by vla1-765d064640cd.qloud-c.yandex.net (mxback/Yandex) with ESMTP id GaDRnogfne-AHHGc3c4; Fri, 22 Jan 2021 02:10:17 +0300 Received: by vla5-7c367a15a176.qloud-c.yandex.net with HTTP; Fri, 22 Jan 2021 02:10:17 +0300 From: Alexander V. Chernikov To: Alexander Leidinger , "current@freebsd.org" In-Reply-To: <20210121190938.Horde.t6HhHqNSRjmOYQcnkW-1Rf4@webmail.leidinger.net> References: <20210121190938.Horde.t6HhHqNSRjmOYQcnkW-1Rf4@webmail.leidinger.net> Subject: Re: panic rtentry / hashdestroy /in6_purgeaddr related? MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 21 Jan 2021 23:10:17 +0000 Message-Id: <25511611270529@mail.yandex.ru> Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-Rspamd-Queue-Id: 4DMJ5V1Pqnz3KNM X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 21 Jan 2021 23:10:22 -0000 21.01.2021, 18:10, "Alexander Leidinger" : > Hi, > > -current at d7fc908cffa as of 2021-01-20-154143. > > I've seen several failures to free an rtentry on the console shortly > before the panic. May or may not be related..._ Sorry for the breakage, should be fixed by 130aebbab0d3. > ---snip--- > in6_purgeaddr: err=65, destination address delete failed > Freed UMA keg (rtentry) was not empty (1 items). Lost 1 pages of memory. > j_gallery_hif: link state changed to DOWN > j_gallery_jif: link state changed to DOWN >   samba.leidinger.net > in6_purgeaddr: err=65, destination address delete failed > Freed UMA keg (rtentry) was not empty (1 items). Lost 1 pages of memory. > j_samba_hif: link state changed to DOWN > j_samba_jif: link state changed to DOWN > ---snip--- > > This is on shutdown with 22 vnet jails: > ---snip--- > Unread portion of the kernel message buffer: > <6>in6_purgeaddr: err=65, destination address delete failed > panic: hashdestroy: hashtbl 0xfffff80be7108800 not empty (malloc type ifaddr) > cpuid = 14 > time = 1611248408 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0064b55b10 > vpanic() at vpanic+0x181/frame 0xfffffe0064b55b60 > panic() at panic+0x43/frame 0xfffffe0064b55bc0 > hashdestroy() at hashdestroy+0x54/frame 0xfffffe0064b55bd0 > vnet_destroy() at vnet_destroy+0x146/frame 0xfffffe0064b55c00 > prison_deref() at prison_deref+0x28e/frame 0xfffffe0064b55c40 > taskqueue_run_locked() at taskqueue_run_locked+0xb0/frame 0xfffffe0064b55cc0 > taskqueue_thread_loop() at taskqueue_thread_loop+0x97/frame 0xfffffe0064b55cf0 > fork_exit() at fork_exit+0x85/frame 0xfffffe0064b55d30 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0064b55d30 > ---snip--- > > Full crashinfo output available on request. Kerneldump is also > available if you want I peek into it at some specific place. > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF From owner-freebsd-current@freebsd.org Fri Jan 22 06:24:52 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A93B54EB584 for ; Fri, 22 Jan 2021 06:24:52 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DMTkq6gFdz4STq; Fri, 22 Jan 2021 06:24:51 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x436.google.com with SMTP id b5so3969644wrr.10; Thu, 21 Jan 2021 22:24:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:cc:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=hDVvYoP+rxmpbnTDWsf53D6H3FyEkcCGmvcSaJ63024=; b=aIXa4Xd8HpkYOBoDJk1QtECo6/sgDRmyInbsVm0jE6kmsE0JOQieSpfLF/2tIfbD80 ryMdF9gNkD6tqzNQVnnniuid9134ryqXLG6AugEt+G6ghkmmv7Tp4VRJA5IpNQDebpyh QdCfCpDd6WbmaJKeKN869waz5g0SwmAzEBHUBJvQkE3baEajnTaCEsi22kPZPWc8k1On vpLvK3bu+EOrzl+AIAvT/r2fDPL1RGRD3MT4eSp5rZ9i0EE4d3wknIARIxG8UUxj1Dhz S6+eLhDKlA7phWUZfJ80DmldhXcYXN5kd6w0qNefU85c3R7r7CuIca+SpQYEzgaN/kBV wlqg== X-Gm-Message-State: AOAM532g2al2XIBhbbSnR2Mmv+xjGr4xzaA3qqxiTi7m6lSGD1UEOUKg OSfTkIBON9VBZM00O/9fQGfqNwcnHCkJqAci X-Google-Smtp-Source: ABdhPJwCQ06hoyXMwCk2dQLBm6GhzmuAGg0jyaKlAeQQ68dFVxpigz3z+GOf7252CS8mZIPEQJZASA== X-Received: by 2002:adf:f403:: with SMTP id g3mr2849807wro.212.1611296689905; Thu, 21 Jan 2021 22:24:49 -0800 (PST) Received: from [192.168.1.11] (88-105-96-80.dynamic.dsl.as9105.com. [88.105.96.80]) by smtp.gmail.com with ESMTPSA id n16sm10437208wmi.5.2021.01.21.22.24.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 21 Jan 2021 22:24:48 -0800 (PST) To: Ed Maste , Li-Wen Hsu , =?UTF-8?Q?Ulrich_Sp=c3=b6rlein?= , Warner Losh From: Graham Perrin Subject: Beta Git repo for ports Cc: freebsd-current@freebsd.org Message-ID: <142a3cd9-7f20-7285-b713-3d53ff36a633@gmail.com> Date: Fri, 22 Jan 2021 06:24:47 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB X-Rspamd-Queue-Id: 4DMTkq6gFdz4STq X-Spamd-Bar: - X-Spamd-Result: default: False [-1.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[88.105.96.80:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::436:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; URL_IN_SUBJECT(1.00)[cgit-dev.freebsd.org]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_SHORT(0.20)[0.198]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::436:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::436:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 22 Jan 2021 06:24:52 -0000 Via : Please: where to file enhancement requests (or bugs) for development of this cgit service for ports? Is there a GitHub repo where issues might be raised? Or, are group e-mails (all four of you) preferred? TIA Graham From owner-freebsd-current@freebsd.org Fri Jan 22 09:45:37 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4B0C54EF380 for ; Fri, 22 Jan 2021 09:45:37 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-20.consmr.mail.gq1.yahoo.com (sonic310-20.consmr.mail.gq1.yahoo.com [98.137.69.146]) (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 4DMZBS2RXjz4cYP for ; Fri, 22 Jan 2021 09:45:36 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1611308734; bh=snHL0uY8Kt9wECQ/GMG1Cw+AVga5zaGd7GKeJRHJHA2=; h=From:Subject:Date:To:From:Subject:Reply-To; b=Xe7jhfAHKOkeLXNyN+mEHEgcAhEXE0EB/lRlbfL+sbtZNBGeEQB1BLuo8WUpitrNU37ZjsVaCNkFUZhMmQHVliYrsp5/jiL12i2KdUE7muaBDEeQEmF5PgpdjZsRZmhqDJUJQbDIdq3yP1HLqzuiJUUVcMcKfuoeTh7yp6rsaEywXkBn5TZc/mIDYpB9TmZNxfVWhZ3MDeeqOOPrrmTC5okBeg6yzkRfDHv5H94SQsna1IaKTysZXH9R3nyEtQLMs+MTGRMXMGjav5ynhEzKdYmYmfs/bhejUh2nAXvY+3NnVnGvQUI73TusZotAiS+tv+4pV+UWqb8ZtHJ2Udw9DQ== X-YMail-OSG: gcK3EewVM1n1qtA_m66ie1WMvTD_Z3XJkM7aBln2mifEgRF5PkggCDD2jxde2TC 8n894YxQtckWd6cmkkaCpfXXtea9V6GJ_RAZL4fsX6RZwFDefW81Lf9vHaAGO2OWU7SAREDgjXAg d4HVvzcjhkSBDKv7CYlvnnytPOKzghb0FQnBWmC6DsXWX0CxYhAC5WcYZpBSPCKtuVDNQzoZNSGr SKWXw_5Ew9N95AFfEH1fR6E4TfEI3W6nZQCSSura8g7qRXRpXe460TABgToheLWsbsmneNjGSGEB 0KF62E2kIJg_EGgrGHo.VNjVV1AXGvaTrlhzUdfskIB8SGGh0Y3x2_rNQbAo0H4usckK.pka.MB0 l_cniXKbS0w.tw2JL6g6vgFRgp.7HGyHqifH0jOZewb.KTLCtrqQyJJiBINCF2UXD5swbHUGGHMX Vwu8yivWovL2Pqz2HAJ6djU_mnluuFVaY7artqT1uEXKfLUpqMu.utUhKlaoM6485Vsc_HyOuuKV fHqmQDQm6hM84o32YX0fxsmVN0qzblu076cTXkmpeVViS1cdcs7VXLohj4N7QjioEQhzwx2T1lXH .XuvKkxd3A7eiglXwnbe.8fSXWjpWcyBkS5Up5IxIflzscgE1l.PfKn.IXtcn.0NgGSjg.fOE194 3FgRaPTeGDz8lfBgAZ0mv0okzWjMogbZpty0yYunF7g8yy8t_K3wKcWA07zs7n_zzTjj_I1D0U4c tIeIFoAea4dpeuicc2ci_epP1.LXZDZNYuzhplR83v_u1iLxqTJucEGhWtHpi5AcTaYuoYnl1gI3 4oVDxPi.SnoMaG2PCEUUDPYIPSggAquWsq1n.2WjVksogJ.99mY8vwsQeYHjX0OSpoL2XhvCPJ2g W8chDUHRQgUxsCBnuTEOpfeZgmCRKsqu74BFxQSY_ziRu2EAVeeub5793lwZ5pmRPDH5xo6xRrtt zLOoGBKWCXxvjVNyqeD6SxEZyFxHeFL_9OOQz8E26Fjkb4RIa2jlZLDWbuQM7Z1dTPnCSi1r_XSM c8i5n.w1HO6Z.XSk26MPaW6qoHdCaejJNPecK3SlBHS0uIKm3oq14OdoErJNq4fOyUmjFNJ_9aTx uOzRVHldpZec3Cagpv_yy_UkkDrbzMc_F2fEEg7favydYfkQMfao.JYZpQlbkBFFHr_l_zQzResJ PP8is8IxHaA.oiULqaiVeD2KLUDporJCuBVn1EXbMjc_sSaKeHHRXKqMlTzPzPNJUEAe8VD4EK1V yn8MWCsDp2SbQ6R7hroS0bmysINfFRMCCpLnafQVVSeV0tOlIhG7_EFvxypYPtcARXs5ApM4GUNF EiJzmbYyPf4bu.Is9Xew1ziOyPybyX7nykcyfG65FkLeQJwI0E2zA25pK5FrRnQO.Rf7gkC3Cio5 1v9CRozChF2nhoWGYSCvHU8CrA78dYbrNY.ndYH.BD92pf8VC2mKfcmdo3yego2kXMD4gcLdvHpV IoFBp1zmCCpfnBXjzWmK6TL.8DpTpZ3D0rMgTqUhREooPQU1WtnC3rm3e7pG0v8u4DoLYWQXP1FG 8acMpoe0wCGIf9KLG_sD1E2sK0IooILNS_GV6pkDOEFFQABlvNSDOjAM4VJa7FwHcbzUgOkHojM6 7i9kJdhpj183hr3XIdd913Sg6pXwZ7_K9WTWW_rbBZb1IemMjiZHIBULMjutqPkk7wO0Dzud.zmx y32D1qzEEjpvtG.UsydXN2r0.UlOJSK3dI17ehVgXKp8BtoHUi10yZyeQNl.W420x6AJItTi.gq2 mGx8Dj59tTGfsNyt9L5F0VoqckE1z1S6fFFoZKqHEAEDFE9WP60lHmRfnciLisq54pqty3WvVgkv vNBIHx7q8GN2I9XwJO3JJhIWUS8XLrqegj4Wvnln6bcMcyplQsq_ge2dT_5RV3a4Rpg2r03KAJno I5sOCPEGeN8B_EzvrRcuui0i2_rL2pmpibYwhr.m9krNtYRJtWrnACqHr00Kvm6.PYWlhOH0cowO Z2irRPuWUsJt0Ky2j.LhYBvZNcTTA6IvpiaBWMzKGIJxqiZZ8o5634ACK8WSTRTZkwzndMV7CB_4 EYcdwOQsQyGAd.oz1JrPrzrBfjlt8ogfNBBRhk2JbCgUS.f86vR7rX5BWo5rcjB09osk3.wvulmM FsuUtpVPg6zc31AqrbPvfacu5zZ8vWNTtdnR1zFzSduweGQHV6TFpim4_lKiwJgbmuTxW_zhajHf X.Gmeudq22zSBAbN2vIMYpDTes8aMTQmTiaaAC_SNgAnscCw24WOKJxpr5JOLe0wPvY2EgdnvVE7 Y8BkhZla.VDL3zZVri6niproP_6i617mjNy4kCO9Yo5nF9Y3KJeuEG49VlFfju6pxbW8xb5pQ1xI Z7w2wp6zzwlLFXqs3E9bmbGuKjPAcKWhRxx1_E2isxufe8RQ_NbHsykcs9cXLjfx.9lcS2BSFl37 ZNTb9Qm0KGRYm1LI.l1uRehj_n.LXDniyl4lKBCHE7g_AKv.Xnb3Xs2UbLhDPPpL2RreL5K1VNp_ 9i2aCke0iWPGTIKp_8kRI280TVFuX Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Fri, 22 Jan 2021 09:45:34 +0000 Received: by smtp415.mail.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 3cda624c97969f597ae7530c7e696a41; Fri, 22 Jan 2021 09:45:31 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: FYI: Why META_MODE rebuilds so much for building again after installworld (no source changes) Message-Id: Date: Fri, 22 Jan 2021 01:45:29 -0800 To: Bryan Drewery , Current FreeBSD X-Mailer: Apple Mail (2.3654.40.0.2.32) References: X-Rspamd-Queue-Id: 4DMZBS2RXjz4cYP X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.69 / 15.00]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.19)[-0.187]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.69.146:from]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.69.146:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.146:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.146:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 22 Jan 2021 09:45:37 -0000 Given an already built, installed and booted system version, I've noted a big difference for META_MODE in 2 rebuild contexts (no source updates involved): *) Prior buildworld buildkernel, installkernel, installworld, boot presumed before (A) and before (B) below. A) make . . . buildworld buildkernel make . . . buildworld buildkernel (the 2nd buildworld buildkernel in (A) builds far less than the = first) (that means that the first built more than I would have guessed) vs. B) make . . . buildworld buildkernel make . . . installworld make . . . buildworld buildkernel (the 2nd buildworld buildkernel in (B) builds far more than it did in = (A)) (so, more like the 1st buildworld buildkernel in (A) and (B), given the specified prior context) So I used make -dM for the commented buildworld buildkernel lines, = logging the build output and later diff'ing them. Result that I noticed? Lots of lines uniquely from (B)'s case, ending = with one of: file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/awk' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/cap_mkdb' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/cat' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/cp' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/crunchgen' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/crunchide' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/dd' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/egrep' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/env' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/file2c' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/gencat' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/grep' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/gzip' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/jot' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/lex' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/ln' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/m4' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/mv' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/patch' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/rm' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/sed' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/sh' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/touch' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/truncate' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/uudecode' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/uuencode' is newer than the target... file = '/usr/obj/amd64_clang/amd64.amd64/usr/fbsd/mm-src/amd64.amd64/tmp/legacy/u= sr/sbin/xargs' is newer than the target... The lines with these lead to more files being updated and so causing = more indirect rebuild activity (that cascades). Many/most/all(?) of these seem to me to be unlikely to actually need to contribute to what needs to be rebuilt (just based on being newer). So the option to ignore (some of?) them could be useful in making META_MODE builds quicker. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Fri Jan 22 15:16:47 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D3E274F7814 for ; Fri, 22 Jan 2021 15:16:47 +0000 (UTC) (envelope-from hlh@restart.be) Received: from tignes.restart.be (tignes.restart.be [IPv6:2001:41d0:a:f40b::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "tignes.restart.be", Issuer "CA master" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DMjXZ43Kfz3KKp for ; Fri, 22 Jan 2021 15:16:46 +0000 (UTC) (envelope-from hlh@restart.be) X-Comment: SPF check N/A for local connections - client-ip=192.168.25.127; helo=restart.be; envelope-from=hlh@restart.be; receiver= DKIM-Filter: OpenDKIM Filter v2.10.3 tignes.restart.be 4DMjXR114TzZS Received: from restart.be (norquay.tunnel.bel [192.168.25.127]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.restart.be", Issuer "CA master" (verified OK)) by tignes.restart.be (Postfix) with ESMTPS id 4DMjXR114TzZS for ; Fri, 22 Jan 2021 16:16:35 +0100 (CET) Received: from morzine.restart.bel (morzine.restart.be [IPv6:2001:41d0:a:f40b:1:1:0:1]) (authenticated bits=0) by restart.be (8.16.1/8.16.1) with ESMTPSA id 10MFGTZs061106 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=OK) for ; Fri, 22 Jan 2021 16:16:33 +0100 (CET) (envelope-from hlh@restart.be) X-Authentication-Warning: norquay.restart.bel: Host morzine.restart.be [IPv6:2001:41d0:a:f40b:1:1:0:1] claimed to be morzine.restart.bel To: freebsd-current@freebsd.org From: Henri Hennebert Subject: RTC on ROCKPRO64 Message-ID: <59aa70f6-73fa-4c8f-c6eb-72a05ab9586f@restart.be> Date: Fri, 22 Jan 2021 16:16:29 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DMjXZ43Kfz3KKp X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[restart.be:s=tignes]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:a:f40b::1/128]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2001:41d0:a:f40b::1:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[restart.be:+]; DMARC_POLICY_ALLOW(-0.50)[restart.be,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:41d0:a:f40b::1:from]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 22 Jan 2021 15:16:47 -0000 Hello, I have tested https://reviews.freebsd.org/D22692 on my ROCKPRO64 with a battery and it works. (After correcting the typo at line 516 of rk805.c) Is it possible to merge it for 13.0-RELEASE ? Henri From owner-freebsd-current@freebsd.org Fri Jan 22 16:38:23 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C62704F8DD1 for ; Fri, 22 Jan 2021 16:38:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DMlLk4r2Dz3PGW for ; Fri, 22 Jan 2021 16:38:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x831.google.com with SMTP id e17so4542563qto.3 for ; Fri, 22 Jan 2021 08:38:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tLiipcI5K4nHwd4vkSGKt+4s9jdOpXMABGp7bnzv/Gk=; b=XOlnmToQR16LyCFq68kbHFELxHBHSVBsJJWqDnxYhlR+EwvF+HKg7ARyKg65GQzi5l T3+K5MABrAixfJtGjt0lJ1WUBKNJbbdv51RQlzSNsarEZbsb9QJSQa/4opW0p6UmaQEs WTU0eN+ALBQoYNqauBNnIf6FM8HuWZ48ifCwFHuJTolCQZFB1sIdzbFC8X627oPXFctY 0TITZABuBIwIMblNtY2g3ZksNloEdb1NfBHQo8F1GdO80+M8G/XcACEqD+LguYM1sfzT e7uJcI3uEd+y7qXSeXAu+CPG5M5RVV8eywZIgaaigUDMyZ44aOVIhpMVGHtjb3+8k0LZ slfw== X-Gm-Message-State: AOAM531xwfH7ABk8TM7t1SNUWcBf7FcEw/cn+BrBUUreT2dKzzAp8ECu qZFFxMnzjzlo2W/cpTk4stVIP/mC5xlLPD9RnpYOjg== X-Google-Smtp-Source: ABdhPJzlInnUSOAOkZL3mc4SRtykqfLAeDs/sBicLBJaLVKtpOrsSL0yKPg8IMWpAVQwjLzOYbhLobphLe/SZblJ1yE= X-Received: by 2002:ac8:4894:: with SMTP id i20mr1386255qtq.244.1611333501703; Fri, 22 Jan 2021 08:38:21 -0800 (PST) MIME-Version: 1.0 References: <20210121054646.GA61716@troutmask.apl.washington.edu> <20210121061310.GA61889@troutmask.apl.washington.edu> <20210121062109.GB61941@troutmask.apl.washington.edu> <20210121115015.460ecc9b854480f41b7cc97d@bidouilliste.com> In-Reply-To: <20210121115015.460ecc9b854480f41b7cc97d@bidouilliste.com> From: Warner Losh Date: Fri, 22 Jan 2021 09:38:10 -0700 Message-ID: Subject: Re: make buildkernel is broken (linuxkpi vs drm) To: Emmanuel Vadot Cc: Steve Kargl , Hans Petter Selasky , FreeBSD Current , John Baldwin X-Rspamd-Queue-Id: 4DMlLk4r2Dz3PGW X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_FIVE(0.00)[5]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::831:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::831:from]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::831:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 22 Jan 2021 16:38:23 -0000 On Thu, Jan 21, 2021 at 3:50 AM Emmanuel Vadot wrote: > On Wed, 20 Jan 2021 22:21:09 -0800 > Steve Kargl wrote: > > > On Thu, Jan 21, 2021 at 07:18:07AM +0100, Hans Petter Selasky wrote: > > > On 1/21/21 7:13 AM, Steve Kargl wrote: > > > > It is 'make buildkernel' in /usr/src after a 'make buildworld'. > > > > I have 'PORTS_MODULES+= graphics/drm-current-kmod' in /etc/make.conf. > > > > > > Try to update the ports tree. I'm not aware of any current build > issues in > > > this area. > > > > > > > I tried that. I did not fix the problem. Commenting > > out the PORTS_MODULES line in /etc/make.conf allows > > me to finish building the new kernel. I re-install > > the port after I install world/kernel. > > > > -- > > Steve > > Does it works now ? > > I think that PORTS_MODULES shouldn't be used for drm-current-kmod or > we should not install the source with it if PORTS_MODULES is the right > way. > > The problem is that drm-current-kmod install its sources > in /usr/local/sys and by default all modules there will be rebuild when > doing make buildkernel unless LOCAL_MODULES is defined. > The problem with installing sources is that if something changed in > base that broke the build with a certain version of drm-current-kmod > you first need to upgrade the ports/package to have the new sources to > be able to make buildkernel correctly. > I personally hate the fact that we install the sources as it only > causes problems for users but some people seems to like it. > It seems that if we don't install the sources and one uses > PORTS_MODULES we just need to upgrade the ports tree before running > make buildkernel if there is a conflicting changes which seems saner to > me tbh. > I started out liking this, but kinda hate it now. We need a solution that always builds the .ko file, but the current hodge-podge is confusing and difficult to get right. -current is such we can't ship pre-compiled things, and the number of kernel options that subtly break binaries ebbs and flows. It was a solution for people that installed from the package: the sources would be there and they'd always rebuild. In theory this is great! In practice, though, current and drm are moving fast enough together that a source package grows stale quickly so rebuilding old sources doesn't work because they don't know about the new API requirements. Making the APIs grok recent history of drm modules is harder than it sounds, alas. > For now I've been focusing the rage that LOCAL_MODULES exists and > cause this kind of problems on migrating more stuff into base so that > one day we will finally have drm in base again. But I'm a bit > tired of dealing with all those problems and I've wondered a lot of > times about removing installing sources for drm-current-kmod. > I think that might be best. I use LOCAL_MODULES all the time. However, I use it with symlinks to a git tree that I keep up to date from there. You can't do that with PORTS_MODULES. And it's a better match for the current development style. It worked great for the iichid work as well before it went into the tree, though it wasn't so fast moving that an occasionally stale update would trip you up. > Adding jhb@ to cc as I know he uses LOCAL_MODULES so maybe he can > explain the advantage over PORTS_MODULES. > So long as PORTS_MODULES always builds from source with every kernel build you plan to install on the system, it works... But you also have to be careful about making sure you always update ports before building the kernel. Otherwise, you run into exactly the same issues you have with LOCAL_MODULES... Now, having said all that, this stuff (all the drm) should be in base, with relaxed MFC constraints. It's too tightly coupled, and we don't have any solution to the current de-facto requirement that you must update both at the same time. The proffered advantage (being able to run new DRM drivers on old systems) gives less benefit than the real problem of "I didn't update my sources or knew that I needed to and now it won't build anymore". Warner From owner-freebsd-current@freebsd.org Sat Jan 23 01:13:25 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 288CE4DBE83 for ; Sat, 23 Jan 2021 01:13:25 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DMymz5hTwz4g4s for ; Sat, 23 Jan 2021 01:13:23 +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.16.1/8.16.1) with ESMTPS id 10N1DGme069131 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Fri, 22 Jan 2021 17:13:16 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 10N1DGAK069130 for freebsd-current@freebsd.org; Fri, 22 Jan 2021 17:13:16 -0800 (PST) (envelope-from sgk) Date: Fri, 22 Jan 2021 17:13:16 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: elfctl is broken Message-ID: <20210123011316.GA69125@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4DMymz5hTwz4g4s X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.29 / 15.00]; RCVD_TLS_ALL(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.95.76.21:from]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[128.95.76.21:from:127.0.2.255]; ARC_NA(0.00)[]; NEURAL_HAM_SHORT(-0.29)[-0.288]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM, none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 01:13:25 -0000 =3D=3D=3D> usr.bin/elfctl (all) cc -target i386-unknown-freebsd14.0 --sysroot=3D/usr/obj/usr/src/i386.i386/= tmp -B/usr/obj/usr/src/i386.i386/tmp/usr/bin -O2 -pipe -fno-common -I/usr/= src/contrib/elftoolchain/li belftc -I/usr/src/contrib/elftoolchain/common -= march=3Dcore2 -MD -MF.depend.elfctl.o -MTelfctl.o -std=3Dgnu99 -Wno-forma= t-zero-length -fstack-protector-strong -Wsystem-headers - Werror -Wall -Wno= -format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototyp= es -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wsha= dow -Wun used-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-ex= terns -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-= variable-declarations -Wthread-saf ety -Wno-empty-body -Wno-string-plus-int= -Wno-unused-const-variable -Qunused-arguments -c /usr/src/usr.bin/elfc= tl/elfctl.c -o elfctl.o /usr/src/usr.bi= n/elfctl/elfctl.c:258:18: error: comparison of integers of different signs:= 'long' and 'unsigned int' [-Werror,-Wsign-compare] = else if (val > UINT_MAX) ~~~ ^ ~~~~~~~~ = =20 1 error generated. = = =20 *** Error code 1 =20 --=20 Steve From owner-freebsd-current@freebsd.org Sat Jan 23 06:31:12 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A185F4E7B3A for ; Sat, 23 Jan 2021 06:31:12 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DN5qg47CHz3J3F for ; Sat, 23 Jan 2021 06:31:11 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: by mail-lj1-x231.google.com with SMTP id f2so3860339ljp.11 for ; Fri, 22 Jan 2021 22:31:11 -0800 (PST) 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=GKh0Uw5ttFHAgND7CHU+UGVWjrS/9TnCMz0C0pRwDW4=; b=TMlQ3cgHpk6ez4ZqvH6Pf7LtNFcDDWndBwuo5h3opShuBjm8zqYACWDj0EjR2kAelY u97M2nVzptLSaDM6E6V9irrrVA4vsHN6ZIOWhwP2x4Qzdjj6xo4YjCyvcq+ESDE4b15H unOJYXuY3rY10Z8oihz2+zcnElYeHIUpSjlBIhiQ0IwL+XYALW+Mq4Hk17wX5aZo3e+1 baQlsAYufROkNzMfiEtgcMVxr7UaN0EQVHJlygStEJ2mVqTac5Xl8YN42iilJ/Y4SYbR SYaemBcmbiVwnYLFF6uYbx+Tp03k07/pbF7Y/bxGmKGLLw9dmqLov/PUyIwkCA9SwpM7 KkFw== X-Gm-Message-State: AOAM5321xCDFR5mYUaxk+NoePtKRmuCj71uVcdughucC6NUtTCMAa95H /VABQz1ZRgngpPy8oSb9uttKhsw2A3SWrFI6jIciTp1zBA== X-Google-Smtp-Source: ABdhPJyuBMjgRb1Wh4fdRoM3tkPNxhzRbC1v/9kWOocktZ2BV/XKbQtxZQnMf/YGlzPrPYXzBH8RtTq7EE/MuIgAub8= X-Received: by 2002:a2e:9dd2:: with SMTP id x18mr287724ljj.359.1611383469319; Fri, 22 Jan 2021 22:31:09 -0800 (PST) MIME-Version: 1.0 From: Clay Daniels Date: Sat, 23 Jan 2021 00:30:58 -0600 Message-ID: Subject: 13.0-ALPHA2 is a Winner! To: "freebsd-current@freebsd.org" X-Rspamd-Queue-Id: 4DN5qg47CHz3J3F X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.86 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.86)[-0.862]; SUBJECT_ENDS_EXCLAIM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::231:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::231:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::231:from]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 06:31:12 -0000 The bufdaemon has been tamed! 13.0 really is impressive, no joke. Thanks to all the developers and such. From owner-freebsd-current@freebsd.org Sat Jan 23 10:51:57 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0F4944F05A5 for ; Sat, 23 Jan 2021 10:51:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNCcW6NzVz3qb5 for ; Sat, 23 Jan 2021 10:51:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 10NApjLg015978 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 23 Jan 2021 12:51:48 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 10NApjLg015978 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 10NApi3R015977; Sat, 23 Jan 2021 12:51:44 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 23 Jan 2021 12:51:44 +0200 From: Konstantin Belousov To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: elfctl is broken Message-ID: References: <20210123011316.GA69125@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20210123011316.GA69125@troutmask.apl.washington.edu> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4DNCcW6NzVz3qb5 X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:d5e7:1::1:from]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_SOFTFAIL(0.00)[~all:c]; SPAMHAUS_ZRD(0.00)[2001:470:d5e7:1::1:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.996]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 10:51:57 -0000 On Fri, Jan 22, 2021 at 05:13:16PM -0800, Steve Kargl wrote: > =3D=3D=3D> usr.bin/elfctl (all) > cc -target i386-unknown-freebsd14.0 --sysroot=3D/usr/obj/usr/src/i386.i38= 6/tmp -B/usr/obj/usr/src/i386.i386/tmp/usr/bin -O2 -pipe -fno-common -I/us= r/src/contrib/elftoolchain/li belftc -I/usr/src/contrib/elftoolchain/common= -march=3Dcore2 -MD -MF.depend.elfctl.o -MTelfctl.o -std=3Dgnu99 -Wno-for= mat-zero-length -fstack-protector-strong -Wsystem-headers - Werror -Wall -W= no-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-protot= ypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Ws= hadow -Wun used-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-= externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissin= g-variable-declarations -Wthread-saf ety -Wno-empty-body -Wno-string-plus-i= nt -Wno-unused-const-variable -Qunused-arguments -c /usr/src/usr.bin/el= fctl/elfctl.c -o elfctl.o /usr/src/usr.= bin/elfctl/elfctl.c:258:18: error: comparison of integers of different sign= s: 'long' and 'unsigned int' [- > Werror,-Wsign-compare] else if (val > U= INT_MAX) > ~~~ ^ ~~~~~~~~ = = =20 > 1 error generated. = = =20 > *** Error code 1 =20 >=20 https://reviews.freebsd.org/D28301 From owner-freebsd-current@freebsd.org Sat Jan 23 12:42:09 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A02D74F3392 for ; Sat, 23 Jan 2021 12:42:09 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (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 4DNG3h4Kp0z4S29 for ; Sat, 23 Jan 2021 12:42:08 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-current@freebsd.org Subject: Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application? References: Date: Sat, 23 Jan 2021 13:42:05 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: bdb49c4ff80bd276e321aade33e76e02752072e2 X-Virus-Scanned: by clamav at smarthost1.greenhost.nl X-Spam-Level: --- X-Spam-Score: -3.1 X-Spam-Status: No, score=-3.1 required=5.0 tests=ALL_TRUSTED, BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF autolearn=disabled version=3.4.2 X-Scan-Signature: a2d32f98be707cbcda8602d5fffa976a X-Rspamd-Queue-Id: 4DNG3h4Kp0z4S29 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.50 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[195.190.28.88:from]; R_DKIM_ALLOW(-0.20)[klop.ws:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[195.190.28.88:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.190.28.64/27]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[195.190.28.88:from:127.0.2.255]; DKIM_TRACE(0.00)[klop.ws:+]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,none]; RCVD_IN_DNSWL_NONE(0.00)[195.190.28.88:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:47172, ipnet:195.190.28.0/24, country:NL]; SUBJECT_ENDS_QUESTION(1.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 12:42:09 -0000 On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan wrote: > Hi freebsd-current@, > > I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while > back. > > With 13.0-RELEASE around the corner, I'm thinking about upgrading my > home server, well if I can accelerate any SSL application. > > I'm asking because I have a home server on a symmetrical Gigabit > connection (Google Fiber/Webpass), and that server runs a Tor relay. If > you're interested in how Tor works, the EFF has a writeup: > https://www.eff.org/pages/what-tor-relay > > But the main point for you all is: more-or-less Tor relays deal with > 1000s TLS connections going into and out of the server. > > Would In-Kernel TLS help with an application like Tor (or even load > balancers/TLS termination), or is it more for things like web servers > sending static files via sendfile() (e.g. CDN used by Netflix). > > My server could also work with Intel's QuickAssist (since it has an > Intel Xeon "Scalable" CPU). Would QuickAssist SSL be more helpful here? > > I'm asking since I don't know whether to upgrade my home server to 13.x > or leave it at 12.x. Yes, I do know we need a special OpenSSL to use > kTLS. > > -Neel According to the history of the openssl port it has support for KTLS. https://www.freshports.org/security/openssl I don't know about the openssl in base. But I think for Tor to support KTLS it needs to implement some things itself. More information about that could be asked at the maintainer of the port (https://www.freshports.org/security/tor/) or upstream at the Tor project. Regards, Ronald. From owner-freebsd-current@freebsd.org Sat Jan 23 15:26:09 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D99CA4F60C7 for ; Sat, 23 Jan 2021 15:26:09 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-to1can01on0619.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe5d::619]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNKhx0TLRz4bLN for ; Sat, 23 Jan 2021 15:26:08 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=N6ASvsj+FGRNnzbMkZQ/1oloFZSVvMZ8805xElJivcq3C/YG5fNSVQEz/FAt5VYPg61Y8WOObQWFu54QtnOWGXFRD2dtQ5eRCMu5JfnOyfzTikFwDgctRNaP1q3wCRwqXQpDvpW/pJ1GfIzi6WKg/dyODGcIU0u5jdEFAW7ZXpxGZaEywzCBG3Qzr5zdstuwPBAZmzr7X3JoyFNN2Fdmi7f0ribET3prhSC/nMA7ECobDYc73zif1vGzHxZ7XAuCu5tDkR1Ga8dwDKWYvGdPadp9HsWfwY4GKmRGTMJ6MGwJHpsjmpphwjHs22Gjuxz8r+SWFveNpU7fNRYXmiSDZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jN4vl++lwL6p9ySvShpOiHx3r50lyNB0xAGAtFy+Umk=; b=iwQJcQHl+p9SDGSq519SEfBYY9FMMqz76RSHTpkxCKaPc2k/GEhfuMzo0tqxfHXudTieawqgxLQjpmujrt5sWaXJwcKl1MF1ezHtX89IuhY32OZ4mQZoyvWUN+7OkrqcRWY9sEOLeQEx1nS1PNqWsOHhICX8j00dQaNh5EDUlwd1symEvQQz05J3GNCMoQbj1MqhELS58INg05TM4LgaorM4mCo/pENSbHQUEFdb/sCHOodvGX6wmM1Eg4Fu1VdH8KnowZGh751FIuu9E5FvOGN9fi35yITxP1+/1ugWxK3rXks1I1htZJSf6/DqGDsvu0s5TtNpO5EgpxKBMqJSgw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uoguelph.ca; dmarc=pass action=none header.from=uoguelph.ca; dkim=pass header.d=uoguelph.ca; arc=none Received: from YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00:19::29) by QB1PR01MB2913.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00:3d::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.12; Sat, 23 Jan 2021 15:26:07 +0000 Received: from YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM ([fe80::3d86:c7f9:bc4c:40c0]) by YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM ([fe80::3d86:c7f9:bc4c:40c0%6]) with mapi id 15.20.3763.014; Sat, 23 Jan 2021 15:25:59 +0000 From: Rick Macklem To: Ronald Klop , "freebsd-current@freebsd.org" Subject: Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application? Thread-Topic: Can In-Kernel TLS (kTLS) work with any OpenSSL Application? Thread-Index: AQHW72nXjq3dxqCEc0+vdfHyry1d96o1K3uAgAAlSjU= Date: Sat, 23 Jan 2021 15:25:59 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: b802de30-a522-4e89-dad5-08d8bfb32fe4 x-ms-traffictypediagnostic: QB1PR01MB2913: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: YVW9mSLbYTRI3ibWuqtdIhNmH1Hvxtj4mp+rfmHgHG+polubyMtk55BF7qzAgi1JDifAYk2D3oeJA6OVgNOAvBOWg25G4RQu0U6pgI9BYc8Zi41b37/PRKjR7GpitmdJw0nNVBbUTank+jMr/elwwxxlzhd8IArV7qxb8C3izGUQ4RNs6i55uEWTyDWpLAUeOv5XOdF442inj024vEdz6KoatTDNiKQgFIaJjoNNKOpk5X9CseuCYm8ZBP2sbplBJUpxB2zTm2LfhD6m8DrUHKDaxDCmEd0fP9c5CXI+ZlKyo6y7TNCfne0ZxmQkTOWEeExiNqrqVVUgq/L9Us1xcNYtgF/FIVjkX/Nme8wMG/9j4XHqXmunf+S0OrfiFxsBfbajQD2zhmUMQp2Ui54FbgQ3erXCSBp71mQY7CXt9Mx6oh4ClqG+vZx13O6lMhiK1nvGiXhCJrkq90gferqeyeFTIeEhC3n2jqQSdv4NePG1ylw5vrvz0f55lSg+LGW3vtsT9xAoa9Y0NdiHdc99XQ== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(39860400002)(366004)(376002)(396003)(136003)(346002)(5660300002)(316002)(52536014)(110136005)(66556008)(9686003)(83380400001)(2906002)(71200400001)(786003)(966005)(64756008)(478600001)(66446008)(8676002)(8936002)(66946007)(186003)(55016002)(76116006)(7696005)(91956017)(33656002)(6506007)(66476007)(86362001)(19400905002); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?btq637tGFsil6/LnQs7FGV3zHJ+udSk88GefbszFtttrqs25k3rUvK+/jQ?= =?iso-8859-1?Q?laGyGl53PSbvCNBGnHrqHod+01wYehU+9b+aUmpt41zxThite7hLxfQiz/?= =?iso-8859-1?Q?yi7/2+ELzIKBonfLrL5jsOODIyfqeJxHADuHOZnQVV/SP+GQ+0BztsfTWe?= =?iso-8859-1?Q?TkMtso5MnhNzEWjSxUAeBl+ck6HcrQIvaCYD7ibOkhLerLuZ7sXv6ZHYML?= =?iso-8859-1?Q?wKIH8FU5/KzIx5H8Hc4jsYrtQzX+gfLfTMh4YaUXvncoNRlfEg2hPI0eh1?= =?iso-8859-1?Q?WpGDcRbJLtBMnSC0cUbwyFPtVQZ0FYjG6NBG84fbQB8y/EWwpiRqyZNrSh?= =?iso-8859-1?Q?t46hJmvT6Qmsd2DUSZtVM2zjwJ000eomyUBaA+Y5sdUfyLlti9PRhS/NsS?= =?iso-8859-1?Q?KjueetGwRZYhg9YGxyoRhQFwHvIXuLvZUROsFDwqzYgltONoCXH3AvKs59?= =?iso-8859-1?Q?YMV3iFrGqcFqSiqAkcTyMAROZsffs4bFHkKlNq8QHTRF/YqdQhqD6E1D1G?= =?iso-8859-1?Q?s/lTGJNKkO0RILL7vHKcZMoGObwQDm7RuMDtLFVZmcgxXJDN+mnE1A3DPE?= =?iso-8859-1?Q?EZOMJvfQT9d8oUdBDzC7KHMxhlkCRTA7+Q57OE6feepyAMTiIh36uMm6Qn?= =?iso-8859-1?Q?e1gophRb9DJVnkvDNH+5QktgJUG0ZqVjd9WPL9mWqR07fvAZlKmlhkZ2i+?= =?iso-8859-1?Q?0HmlGGXbUrKWsWuZug1sfOF+O5ecdm8eXPfxuKzhLNhC04A2IlfXSQzHWc?= =?iso-8859-1?Q?ADXkezH4zjWg6Nkvt4UiQ9+m4I4bpt16uQQubEhDfs3lib5V1DZcsTEdDv?= =?iso-8859-1?Q?mZGxeAKj4W4aVdvFWRfa2bVTvOPptRL2xlWuKqadbPrzb0XI/3wIYmZxBB?= =?iso-8859-1?Q?6VHWfrTsUb4L0LsAs8fMHmTfRqz5fbWo3JU+7Tr0twzUr7AZX9FVCb/2qh?= =?iso-8859-1?Q?GwXGMVXmxU1ld2htTDPBGNW1xOLkfvZFZjdyRKrlU+CtdV8ByqpoURkZXQ?= =?iso-8859-1?Q?dFadJPgKbcbw1cvPDKwD7kVa1PgbiExIC8EHJW11WNhYOrtFvaAFSDr//Q?= =?iso-8859-1?Q?h96zMj1AFxXEBvKRzxUgUPLTq43jdM6wgZlQdeCzN7GOWtzt7WjUvRQS01?= =?iso-8859-1?Q?P66pnz+4YV2mxHPNspWIo2Iv/k4JQEK+k+YhOMdq9FlC/V6hUv?= x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-Network-Message-Id: b802de30-a522-4e89-dad5-08d8bfb32fe4 X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jan 2021 15:25:59.6133 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: dUVH+dujni+EtcRCHYQ4jvTjkhvygh9tMvw7KhZdJ6PFpvLTYEiYUW/Oddmg6a8Sx7orjOjrV5H7J2KHAOTPQA== X-MS-Exchange-Transport-CrossTenantHeadersStamped: QB1PR01MB2913 X-Rspamd-Queue-Id: 4DNKhx0TLRz4bLN X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:111:f400:fe5d::619:from]; R_DKIM_ALLOW(-0.20)[uoguelph.ca:s=selector1]; FREEFALL_USER(0.00)[rmacklem]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:111:f400::/48]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[2a01:111:f400:fe5d::619:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_LOW(-1.00)[uoguelph.ca:dkim]; DKIM_TRACE(0.00)[uoguelph.ca:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[uoguelph.ca,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:8075, ipnet:2a01:111:f000::/36, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; ARC_ALLOW(-1.00)[microsoft.com:s=arcselector9901:i=1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 15:26:09 -0000 Ronald Klop wrote:=0A= >On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan wrote:= =0A= >=0A= >> Hi freebsd-current@,=0A= >>=0A= >> I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while= =0A= >> back.=0A= >>=0A= >> With 13.0-RELEASE around the corner, I'm thinking about upgrading my=0A= >> home server, well if I can accelerate any SSL application.=0A= >>=0A= >> I'm asking because I have a home server on a symmetrical Gigabit=0A= >> connection (Google Fiber/Webpass), and that server runs a Tor relay. If= =0A= >> you're interested in how Tor works, the EFF has a writeup:=0A= >> https://www.eff.org/pages/what-tor-relay=0A= >>=0A= >> But the main point for you all is: more-or-less Tor relays deal with=0A= >> 1000s TLS connections going into and out of the server.=0A= >>=0A= >> Would In-Kernel TLS help with an application like Tor (or even load=0A= >> balancers/TLS termination), or is it more for things like web servers=0A= >> sending static files via sendfile() (e.g. CDN used by Netflix).=0A= >>=0A= >> My server could also work with Intel's QuickAssist (since it has an=0A= >> Intel Xeon "Scalable" CPU). Would QuickAssist SSL be more helpful here?= =0A= There is now qat(4), which KTLS should be able to use, but I do=0A= not think it has been tested for this. I also have no idea=0A= if it can be used effectively for userland encryption?=0A= =0A= >>=0A= >> I'm asking since I don't know whether to upgrade my home server to 13.x= =0A= >> or leave it at 12.x. Yes, I do know we need a special OpenSSL to use=0A= >> kTLS.=0A= >>=0A= >> -Neel=0A= =0A= I cannot answer your main question. All I can tell you is this...=0A= KTLS works very well for NFS, but that is, at least in part, because the da= ta=0A= never needs to move up to userspace. For server side read, the data is read= =0A= into anonymous pages by VOP_READ() and then those are handed to the=0A= socket hanging off of MEXTPG mbufs. The KTLS then creates/encrypts the=0A= application data records that go on the wire.=0A= =0A= Since I assume Tor does SSL_write() or similar in userspace, the question= =0A= becomes "is doing the encryption in the kernel instead of userspace going= =0A= to perform better?". For something like a Chelsio-T6, I'd guess yes. For=0A= software encryption, I have no idea?=0A= =0A= The KTLS software encryption creates one kernel thread per CPU and then=0A= sockets that are KTLS enabled are assigned to one of these threads. Does=0A= this help w.r.t. your load balancing issue? Again, I have no idea.=0A= =0A= >According to the history of the openssl port it has support for KTLS.=0A= >https://www.freshports.org/security/openssl=0A= >I don't know about the openssl in base.=0A= I believe both openssl and openssl-devel in ports have the KTLS support=0A= in them, although you might need to click on "KTLS" during the port=0A= build to enable it. (I use openssl-devel, which is OpenSSL3, still in alpha= =0A= test, but seems to work well.)=0A= openssl in base does not have KTLS support, as far as I know.=0A= =0A= >But I think for Tor to support KTLS it needs to implement some things=0A= >itself. More information about that could be asked at the maintainer of=0A= >the port (https://www.freshports.org/security/tor/) or upstream at the Tor= =0A= >project.=0A= To just make it work, I don't think changes are needed beyond linking to=0A= the correct OpenSSL libraries (assuming it uses OpenSSL, of course).=0A= (There are new library calls an application can use to check to see if=0A= KTLS is enabled for the connection, but if it doesn't care, I don't think= =0A= those calls are needed?)=0A= =0A= You do need to run a kernel with "options KERN_TLS" and set=0A= kern.ipc.tls.enable=3D1=0A= kern.ipc.mb_use_ext_pgs=3D1=0A= =0A= rick=0A= =0A= Regards,=0A= Ronald.=0A= _______________________________________________=0A= freebsd-current@freebsd.org mailing list=0A= https://lists.freebsd.org/mailman/listinfo/freebsd-current=0A= To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= =0A= =0A= From owner-freebsd-current@freebsd.org Sat Jan 23 16:43:17 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E78564F7642 for ; Sat, 23 Jan 2021 16:43:17 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNMPx3103z4g80 for ; Sat, 23 Jan 2021 16:43:17 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-lf1-x129.google.com with SMTP id o10so11851307lfl.13 for ; Sat, 23 Jan 2021 08:43:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:from:to:subject:date:message-id :mime-version; bh=endXSEW2gNbCSwxjMHbthoIE9CtV+EguBriOLkpYRgU=; b=n6wQToMFK7pHmWoRqbRepTDBFYl0U/yNjMu7Vr2ApdYTn1V7cY5N6RYQ4lWw2yEDli 8q/4xboKRRxuD63S6S8A+7C8jCtL68i1g1Hz9qdvaIu+up4ps/CLBEnRmT092zFAgto2 /a0zDuFF0tqUaEovOJ8iodhuDC9y2INg8UHUC/jJp6uY1EIm4T0vxZN1CfZpUPqeoo3Y BNME8PRD0nlCtM8+fd1DWGSgJXp6HgUCdjQLkoyLONW7vFa5QAt+VBiwRia9wzn2SgsM ZIyC5ey6OoE6jdog8KSXuYBKMWjbuxhEQFJK0bCN8HDyH2IYEP3hfRQf/CMP7LnkQtH9 4s7A== X-Gm-Message-State: AOAM531SNu0MS5kxjGjvtuAb7zZjRDQUdDe726lLtki0t3N/Pha/VVI9 rTkdfB4soO/0jm2U+yMjYNeYMA9qyls= X-Google-Smtp-Source: ABdhPJx8cVNKN8204JnHVUtPOOo+Rplqi9Tiq4WqGx6mOF/cLuMfvdh3YJxqVHWQG9uXKJ45f4wHcg== X-Received: by 2002:a05:6512:5c6:: with SMTP id o6mr2212535lfo.281.1611420195426; Sat, 23 Jan 2021 08:43:15 -0800 (PST) Received: from localhost (customer-109-238-136-64.stosn.net. [109.238.136.64]) by smtp.gmail.com with ESMTPSA id l28sm1366200ljb.42.2021.01.23.08.43.14 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 23 Jan 2021 08:43:14 -0800 (PST) User-agent: mu4e 1.2.0; emacs 27.1 From: Malcolm Matalka To: FreeBSD Current Subject: Which branch in git is 13.0-current? Date: Sat, 23 Jan 2021 17:43:14 +0100 Message-ID: <86h7n7a9jx.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 4DNMPx3103z4g80 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::129:from]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::129:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::129:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 16:43:18 -0000 I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT? FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33 main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021 root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I am in the main branch, which I got by following the docs on transitioning to git. The main issue is I can't use pkg now. Thanks! From owner-freebsd-current@freebsd.org Sat Jan 23 16:45:10 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5D6344F7A34 for ; Sat, 23 Jan 2021 16:45:10 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNMS51lqKz4gWN for ; Sat, 23 Jan 2021 16:45:08 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by mail-io1-xd2d.google.com with SMTP id u8so4673697ior.13 for ; Sat, 23 Jan 2021 08:45:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4Df4KonBDQ9YVKPSY3q7XmE1Un8eXhUx50eE4ybfuyY=; b=PbSHLgFdScMNFn3l41YWYLLKj10dR0mZ7KgTGj/8y8rKd0kdNaew+8Im4hruIkCVTE a3Ksdg/XD5UAFFaoI4sgMJHHrMIJ4j677MJdT8yd3bBy/waMqWv6pd5fDw2LN+zelmub /wx7k6zOuqfO7/orYJ95BijeZRs0GSZLFVxCjDUXFZbypPy8eFPn9teFehOMQd1RiM3r m+io069RE9Tzfi+ID690TFnFy8wz4UPDhByQbxqDd72xADrm2aSk6QnJ22P392q3q/dt E/bLXeT6wM6EHmfxR5XkdYxyRiYE91mgz3Nie7oYzx2kSuH3BrM+KV754Bm7nwVAJ8op 1Ekw== X-Gm-Message-State: AOAM532sI+Wwt++vficdDqv6loDPVxyDrqtER3GtzKEz9Cnbg+bxkY6l uB8hjngdFpdEiVMuGZnhC3tgYNUPrFhmqhJPHEGrNw== X-Google-Smtp-Source: ABdhPJy83uGIWQGsNDHzSgwDfwQcK6dc+k2A0z0BYHEEki1I3Fb8WGAG7uwfFAlCFmaepynXbUWC4i8QLICXqBEFQ78= X-Received: by 2002:a5e:c702:: with SMTP id f2mr85871iop.133.1611420307732; Sat, 23 Jan 2021 08:45:07 -0800 (PST) MIME-Version: 1.0 References: <86h7n7a9jx.fsf@gmail.com> In-Reply-To: <86h7n7a9jx.fsf@gmail.com> From: Mario Lobo Date: Sat, 23 Jan 2021 13:44:56 -0300 Message-ID: Subject: Re: Which branch in git is 13.0-current? To: Malcolm Matalka Cc: FreeBSD Current X-Rspamd-Queue-Id: 4DNMS51lqKz4gWN X-Spamd-Bar: / X-Spamd-Result: default: False [-0.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::d2d:from]; R_DKIM_ALLOW(-0.20)[bsd.com.br:s=capeta]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsd.com.br]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::d2d:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsd.com.br:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d2d:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 16:45:10 -0000 Stable/13 On Sat, Jan 23, 2021, 13:43 Malcolm Matalka wrote: > I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT? > > > FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33 > main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021 > root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > I am in the main branch, which I got by following the docs on > transitioning to git. > > The main issue is I can't use pkg now. > > Thanks! > _______________________________________________ > 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 Jan 23 16:57:43 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5057D4F7976 for ; Sat, 23 Jan 2021 16:57:43 +0000 (UTC) (envelope-from driesm.michiels@gmail.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNMkZ2s9bz4gpv for ; Sat, 23 Jan 2021 16:57:42 +0000 (UTC) (envelope-from driesm.michiels@gmail.com) Received: by mail-ed1-x531.google.com with SMTP id bx12so10186176edb.8 for ; Sat, 23 Jan 2021 08:57:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=KDtZZp3Iq+KRj3wurPGja7Nd+xvjgCU34lOZGOVm6ok=; b=r3u3k/uPWoTVZGqrJbFcK/JHclDMXrT63Piv2UrI5yTRkz4NfFc3/yPApZV5DFQLni GEqMjlDs5JtbrKFJZdqL895ypqh8yGkwxK6icM6L8pFF6GxdL9X0yguVp+a2ewMu8qnK pWwA1tRDKHiQWtgzlZb/E6MWPS3g+wUCi2AEkjOS9ptSzTe2/zuEOFkmUlz/P6/COjqv So0bjtyA6hNkX5+Qai8eiUO2p/weUSYO++Becr/Xeq4XwJBB1KLRbq3F9+QzcW8tDjGh NU2FpE7JkNhIX5KjIgC3nv83chEaHYB3YJTtcxSUl8sQZJUipPK/rOP0Ln9yT/+PxRY7 Ezfw== X-Gm-Message-State: AOAM530LyIzncxt5yHf6mNcFJDBTXsIEMx9ovjYXXB+If0vcUUf/eZuq 2KPh1lkAUemcjBTXzhYdOBVUWEOSXhEZqrUj X-Google-Smtp-Source: ABdhPJzEmKUKmoQELTEACMY6mr311USomy6u2m4YqzIw9K7rkfT97TLotmJA26hvnJCfZ7qVi6kVrA== X-Received: by 2002:a50:8004:: with SMTP id 4mr2170158eda.155.1611421060701; Sat, 23 Jan 2021 08:57:40 -0800 (PST) Received: from DRIESPC (ptr-8sijbm4urc6wbdd8g5z.18120a2.ip6.access.telenet.be. [2a02:1811:2505:1601:17b:f68f:3491:34d7]) by smtp.gmail.com with ESMTPSA id k22sm7674400edv.33.2021.01.23.08.57.39 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Jan 2021 08:57:39 -0800 (PST) From: To: "'Malcolm Matalka'" , "'FreeBSD Current'" References: <86h7n7a9jx.fsf@gmail.com> In-Reply-To: <86h7n7a9jx.fsf@gmail.com> Subject: RE: Which branch in git is 13.0-current? Date: Sat, 23 Jan 2021 17:57:41 +0100 Message-ID: <000001d6f1a8$dcd03280$96709780$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQKtrAdG+ll7tl9/frGFwE9XjGtR3aiH+Wog Content-Language: en-be X-Rspamd-Queue-Id: 4DNMkZ2s9bz4gpv X-Spamd-Bar: - X-Spamd-Result: default: False [-1.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::531:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::531:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NO_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::531:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 16:57:43 -0000 > -----Original Message----- > From: owner-freebsd-current@freebsd.org current@freebsd.org> On Behalf Of Malcolm Matalka > Sent: Saturday, 23 January 2021 17:43 > To: FreeBSD Current > Subject: Which branch in git is 13.0-current? > > I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT? > > > FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33 > main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021 > root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > I am in the main branch, which I got by following the docs on transitioning to > git. > > The main issue is I can't use pkg now. Build pkg from ports or wait a bit till the clusters have caught up building the packages with the base version change. Dries > > Thanks! > _______________________________________________ > 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 Jan 23 17:16:26 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 227384D8540 for ; Sat, 23 Jan 2021 17:16:26 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNN891NsPz4jDq for ; Sat, 23 Jan 2021 17:16:24 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-lf1-x133.google.com with SMTP id v67so11993037lfa.0 for ; Sat, 23 Jan 2021 09:16:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=E5Zf6pF4vP2wg0GA/DQxmsQLTd8rr9d64WBo9g/zNNk=; b=X+YuPO0g9izdDCdVjzH9voK7hbKwBCutm4x3PIKHG8va3XvLGkKddJs5c40LcJeUSv JLYc77KMo93J2VTSB0EYo0QT/HtjuOqHMje46KFrBQNhpmg4q2tGA+P/gBKDaX5kZ3Ng ABIXmD4LYaJwSgp6WnRwGIAVRe4rMNiX+KVlN+cu8CLQU24BaBSLihV5dvdntFdbr9lt ABX05srKTNXeYPSoCxtpd74saX7vnHM9mE24TyE6oXngZDQ+37FCLcOHw/jMvSq8KMIr 1U2CNTdFHcGuUBYO/wqRL/OY2dCUyVL5bIVb+eSthRnbPLOfj1cIeMJDhqfP9bv+/rsc WtAA== X-Gm-Message-State: AOAM533aixNskUvkfGO8bvVcBm5emVpgmHkt3PrBiIDs6e6kwuIXnSV6 tf7ndAw1C3uzLHPbosOQvjM= X-Google-Smtp-Source: ABdhPJwsyDP3mXFk8H9wdlBhD0tHPsH4lT7Sww3sZvvFXaun/+IL3YRmD93C41VvEtFayhQayIE05Q== X-Received: by 2002:a05:6512:944:: with SMTP id u4mr182020lft.433.1611422182950; Sat, 23 Jan 2021 09:16:22 -0800 (PST) Received: from localhost (customer-109-238-136-64.stosn.net. [109.238.136.64]) by smtp.gmail.com with ESMTPSA id y3sm1182661ljy.98.2021.01.23.09.16.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 23 Jan 2021 09:16:22 -0800 (PST) References: <86h7n7a9jx.fsf@gmail.com> <000001d6f1a8$dcd03280$96709780$@gmail.com> User-agent: mu4e 1.2.0; emacs 27.1 From: Malcolm Matalka To: driesm.michiels@gmail.com Cc: 'FreeBSD Current' Subject: Re: Which branch in git is 13.0-current? In-reply-to: <000001d6f1a8$dcd03280$96709780$@gmail.com> Date: Sat, 23 Jan 2021 18:16:21 +0100 Message-ID: <86ft2ra80q.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 4DNN891NsPz4jDq X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::133:from]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::133:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::133:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 17:16:26 -0000 driesm.michiels@gmail.com writes: >> -----Original Message----- >> From: owner-freebsd-current@freebsd.org > current@freebsd.org> On Behalf Of Malcolm Matalka >> Sent: Saturday, 23 January 2021 17:43 >> To: FreeBSD Current >> Subject: Which branch in git is 13.0-current? >> >> I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT? >> >> >> FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33 >> main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021 >> root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >> >> I am in the main branch, which I got by following the docs on > transitioning to >> git. >> >> The main issue is I can't use pkg now. > > Build pkg from ports or wait a bit till the clusters have caught up building > the packages with the base version change. Does that mean CURRENT is now 14.0? I must have missed the announcement. > > Dries > > >> >> Thanks! >> _______________________________________________ >> 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 Jan 23 17:22:42 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A86B94D8B20 for ; Sat, 23 Jan 2021 17:22:42 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from maybe.home.utahime.org (gate.home.utahime.org [183.180.29.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNNHP3js5z4jYK for ; Sat, 23 Jan 2021 17:22:41 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by maybe.home.utahime.org (Postfix) with ESMTPS id AA4424D2CF for ; Sun, 24 Jan 2021 02:22:31 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384)) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id A0B404BBB8; Sun, 24 Jan 2021 02:22:30 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.0 at eastasia.home.utahime.org Date: Sun, 24 Jan 2021 02:21:42 +0900 (JST) Message-Id: <20210124.022142.126273573648496676.yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: Which branch in git is 13.0-current? From: Yasuhiro Kimura In-Reply-To: <86ft2ra80q.fsf@gmail.com> References: <86h7n7a9jx.fsf@gmail.com> <000001d6f1a8$dcd03280$96709780$@gmail.com> <86ft2ra80q.fsf@gmail.com> X-Mailer: Mew version 6.8 on Emacs 27.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DNNHP3js5z4jYK X-Spamd-Bar: + X-Spamd-Result: default: False [1.28 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:spf-authorized.utahime.org]; TO_DN_NONE(0.00)[]; HFILTER_HELO_IP_A(1.00)[maybe.home.utahime.org]; HFILTER_HELO_NORES_A_OR_MX(0.30)[maybe.home.utahime.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[utahime.org:+]; NEURAL_HAM_SHORT(-0.02)[-0.018]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[183.180.29.210:from]; ASN(0.00)[asn:2519, ipnet:183.180.0.0/16, country:JP]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[utahime.org:s=maybe2019112701]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[utahime.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[183.180.29.210:from:127.0.2.255]; MID_CONTAINS_FROM(1.00)[]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 17:22:42 -0000 From: Malcolm Matalka Subject: Re: Which branch in git is 13.0-current? Date: Sat, 23 Jan 2021 18:16:21 +0100 >> Build pkg from ports or wait a bit till the clusters have caught up building >> the packages with the base version change. > > Does that mean CURRENT is now 14.0? I must have missed the > announcement. https://lists.freebsd.org/pipermail/dev-commits-src-all/2021-January/001588.html --- Yasuhiro Kimura From owner-freebsd-current@freebsd.org Sat Jan 23 17:22:56 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 168D34D8B98 for ; Sat, 23 Jan 2021 17:22:56 +0000 (UTC) (envelope-from driesm.michiels@gmail.com) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNNHg1pGHz4jbg for ; Sat, 23 Jan 2021 17:22:55 +0000 (UTC) (envelope-from driesm.michiels@gmail.com) Received: by mail-ed1-x52c.google.com with SMTP id s3so1894599edt.7 for ; Sat, 23 Jan 2021 09:22:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=zW4w+gLQDhjWpFdBJ2JgE1kx8uk0/WBMfYiZkXj/61I=; b=SeLc/J/tf7lHKtV+GBDCNtvuX0hY7qz1f6lZ2BCDITVwbgqJjlNxoloQair5VUBw5Y cDcJPV/vjjGTehMM/jiyuwJjXKtSvuOdr1eMDk/EQjk5pGubizIZ1mYZjMWtqxw7cV94 P/dYb1B/f9UeZvkspqJ0MG1YzRkuyEeOvZAW72IgkaqVjhUrPmELBcW4UFpieHQxZ4+4 Ef+ra3hw27xp2euSa6s7T9NnEzKe4y6d/VCC2BHPba4zD3IcAMhInSu6/V1mUu9WcSoL tydmnbcxtLIIOOEQCDNGOLqzmUxfS+DBFmR5PxuENt+YCYhIyf9/WUofuqu65vuVBuKz HB5Q== X-Gm-Message-State: AOAM5306vH6vf9IPhTeQtdd+st1hIwxo638cAUxuvZtJj7p4UolRSa0K wp7I9TqsvDJ+Gqb4Q2Fm/PCubeTFNA0XdDfA X-Google-Smtp-Source: ABdhPJxKCADI2LB+mGCft1KxAiyTopCcW4lJyx3oOpNZGGmd5cWSo0SK/zW3F8kKh1L1KGHUvWm8fA== X-Received: by 2002:a05:6402:4391:: with SMTP id o17mr1188857edc.196.1611422573706; Sat, 23 Jan 2021 09:22:53 -0800 (PST) Received: from DRIESPC (ptr-8sijbm4urc6wbdd8g5z.18120a2.ip6.access.telenet.be. [2a02:1811:2505:1601:17b:f68f:3491:34d7]) by smtp.gmail.com with ESMTPSA id j18sm6130316ejv.18.2021.01.23.09.22.52 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Jan 2021 09:22:52 -0800 (PST) From: To: "'Malcolm Matalka'" Cc: "'FreeBSD Current'" References: <86h7n7a9jx.fsf@gmail.com> <000001d6f1a8$dcd03280$96709780$@gmail.com> <86ft2ra80q.fsf@gmail.com> In-Reply-To: <86ft2ra80q.fsf@gmail.com> Subject: RE: Which branch in git is 13.0-current? Date: Sat, 23 Jan 2021 18:22:53 +0100 Message-ID: <004101d6f1ac$62a619d0$27f24d70$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQKtrAdG+ll7tl9/frGFwE9XjGtR3QHkvjONAbmImF6oawzBYA== Content-Language: en-be X-Rspamd-Queue-Id: 4DNNHg1pGHz4jbg X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::52c:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::52c:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NO_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52c:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 17:22:56 -0000 > >> -----Original Message----- > >> From: owner-freebsd-current@freebsd.org >> current@freebsd.org> On Behalf Of Malcolm Matalka > >> Sent: Saturday, 23 January 2021 17:43 > >> To: FreeBSD Current > >> Subject: Which branch in git is 13.0-current? > >> > >> I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT? > >> > >> > >> FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33 > >> main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021 > >> root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > >> > >> I am in the main branch, which I got by following the docs on > > transitioning to > >> git. > >> > >> The main issue is I can't use pkg now. > > > > Build pkg from ports or wait a bit till the clusters have caught up > > building the packages with the base version change. > > Does that mean CURRENT is now 14.0? I must have missed the > announcement. That is correct, 13-stable has been branched from 13-current which has now been bumped to 14-current. Because it's a major version change going from 13 to 14, pkg is a bit agitated regarding the ABI. > > > > Dries > > > > > >> > >> Thanks! > >> _______________________________________________ > >> 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 Jan 23 21:48:26 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 416904DF059 for ; Sat, 23 Jan 2021 21:48:26 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from p-impout005.msg.pkvw.co.charter.net (p-impout005aa.msg.pkvw.co.charter.net [47.43.26.136]) (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 4DNVB104Xgz3FsJ for ; Sat, 23 Jan 2021 21:48:24 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([96.28.177.163]) by cmsmtp with ESMTP id 3QZglZBoNbGHJ3QZgl3fKa; Sat, 23 Jan 2021 21:36:05 +0000 X-Authority-Analysis: v=2.3 cv=A5oSwJeG c=1 sm=1 tr=0 a=xqrt2BZAGHte7XHhrxJgbA==:117 a=xqrt2BZAGHte7XHhrxJgbA==:17 a=HpEJnUlJZJkA:10 a=OsXUjnJtyZBgATbdD1sA:9 Date: Sat, 23 Jan 2021 21:34:56 +0000 From: "Thomas Mueller" To: freebsd-current@freebsd.org Reply-To: freebsd-current@freebsd.org Subject: RE: Which branch in git is 13.0-current? References: <86h7n7a9jx.fsf@gmail.com> <000001d6f1a8$dcd03280$96709780$@gmail.com> <86ft2ra80q.fsf@gmail.com> <004101d6f1ac$62a619d0$27f24d70$@gmail.com> X-CMAE-Envelope: MS4wfNDOatjU1aRSQEVT+oONmkMHXqEdzQEqEctM9+TEHJxgWR3xrm2BD68I/x+oLG8yedDdTkQSM2mBiA9tryUrXjpyMpPOgPdWi6KVuavQVALC0R05eI1Q WKNtjYOgDIvxyvZiLbNyLwSN7k4IZBHOjQN1etskvD/LBnaKehqphVX1 X-Rspamd-Queue-Id: 4DNVB104Xgz3FsJ X-Spamd-Bar: ++++++++++ X-Spamd-Result: default: False [11.00 / 15.00]; HAS_REPLYTO(0.00)[freebsd-current@freebsd.org]; FREEMAIL_FROM(0.00)[twc.com]; R_SPF_ALLOW(-0.20)[+ip4:47.43.26.0/24]; TO_DN_NONE(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[96.28.177.163:received]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[47.43.26.136:from]; FREEMAIL_ENVFROM(0.00)[twc.com]; ASN(0.00)[asn:40294, ipnet:47.43.24.0/21, country:US]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; REPLYTO_EQ_TO_ADDR(5.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.80)[0.798]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; DMARC_NA(0.00)[twc.com]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[47.43.26.136:from:127.0.2.255]; SUBJECT_ENDS_QUESTION(1.00)[]; MISSING_MID(2.50)[]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_TLS_LAST(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[47.43.26.136:from]; RCVD_COUNT_TWO(0.00)[2]; GREYLIST(0.00)[pass,body]; MAILMAN_DEST(0.00)[freebsd-current] X-Spam: Yes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 21:48:26 -0000 > > Does that mean CURRENT is now 14.0? I must have missed the > > announcement. > That is correct, 13-stable has been branched from 13-current which has now > been bumped to 14-current. > Because it's a major version change going from 13 to 14, pkg is a bit > agitated regarding the ABI. > > > Dries There should have been announcements of the src tree branch on current and stable emailing lists! My question is how, using git, to track both 13-stable and 14-current without having entirely separate trees as I had to do with cvs and svn. I think there is a git worktree command but can't remember how I used it, with Haiku in that case. Then I will want to know how to determine which tree I will be compiling. Tom From owner-freebsd-current@freebsd.org Sat Jan 23 22:41:03 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E78364DF6C8 for ; Sat, 23 Jan 2021 22:41:03 +0000 (UTC) (envelope-from bergerkos@yahoo.co.uk) Received: from sonic311-31.consmr.mail.ir2.yahoo.com (sonic311-31.consmr.mail.ir2.yahoo.com [77.238.176.163]) (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 4DNWLk3BcMz3Hrb for ; Sat, 23 Jan 2021 22:41:01 +0000 (UTC) (envelope-from bergerkos@yahoo.co.uk) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1611441659; bh=XIyS+rOKU1gEtJJWrY9RR8tv/KKvNfaiRLh2fvwXbpO=; h=Date:From:To:Subject:From:Subject:Reply-To; b=hT3b0Gw/NWHJGjmxqguvmY3qVWDeXp9ZZXFOyZMWaHbq0GyURVsQjkcZkkRT2OWDNwS3NLqinJgIUGRyA4V2ugXhelt8ByPp3vujiJCGF721aRyTN1MR2+Zk9/3oEwdzzgIKTdqgdVxyy04fGGMp3Tf3COoYwkM6AZHzpFFJRBnhPuSF2zVSPv0VfS2glHv4438hrjzohAimJW/2tZ25ZDswWCdbe/zqgW/dDDAVvCKc9DQUkdz+fHyhwtZXxhOO93lLtJjxjkc0kAftuxDcFGVTPAQuzDS+lkS+i03R+Rl/ohugcVI2v91J7HDeovJ9cuSlN0FtxDQ8GR89m30Scg== X-YMail-OSG: 5awHhvMVM1mt0_Gf_ojLQMC6mZgH.lgEVoW.ODwXFta6XbB.aTIrk5hCa1ltOIb dK2HMqgAJQ1b_i5JGjatjI.cgfVtLdTs5a9KRUnJniN4WHvCBcsDAb4ren_v0Rjd5VohPiVH4PK6 pujzRP.sr9x3nthnBtHfnT60WTccauasfKWDmK4o1YpMVcWiMH7Q_4W3A3lH2y8ekl1IOHOjSSTS D.8bphHAMZZTlBsYF58Fhi.osEDBjNZX9biQN2yPDKkAoVXdRpFRX8EFrxDXAQhH33HSLD0kh3x6 0CYP_anNqT.s97dXdwmmsa1VWwGW3cQPyrpmnQYKZDzXzpeaUeBfggFuixtAy7pH2nK592SL.YOj Ihmh25hAnQtopkMDpnn_qmCehXO3KCYvRoe2p0Es7zByym.sw1XRuXI4C0hK5Kyc5wiajN_VVL3o Hy.Z.RZ_rxc9fsPD6nzT.nFYODUKJ3hLDhF4rIpyFY1KEXM8A2ptyLQ8hREFG7o0h.BlLTDwpuQF km8qQi4o86LFQACLACb_3FFsaATpbmssOkaEs.YS6INhU5yujdd8wzgxCQamZA5V6tQLowcc7SVb s_SSOoR08JaIHe0yAi.XwRGfOIiLmRf5Te6LhFITsgF61Tjw8qvEIOmWLM6lm._8K92TpU4Wehau Bydo10Xsuv0qekegFUw1b8MAqGkJXf4Y_6ZFZ32qs9Ey7hK8C0jXnNb4cvvKJ66CLyx6.RH.Pwy7 VYCaG1L2YUxzvZfBfV2dmdurcIQM9nPyT0HpgiDlREOFl_qB7ER8xCe2.5t7fUwLbrVDsQl8CuP9 ZvcPf2S78hHlpzGP2O_c8z0nqrcURivKEAIpqx_npbMyC7lQkoxFTHRwD3GhAGWSjVnZKdI7ysKH C8CED08TUg6Sxn2O9f5v.AVpuKhlhs_yQ4.v9YLptBszwUBArvAKdoWRofLx5H96roqk.AEdx.eL faXOW20Z16v11KrbJMogmFaxhlnY2yZqOyb45iCogsE4xWfx8Iy8FhQ6SZ22zR.a1.IQKuUsFm4x IGSYeZXGY71v2TWkFV62vixbgvzzR215PEd1V8c4LPpKwOw7Y7JG1kKXxeEFW8joKeV73hrP_OSW tsxZfEr5hKphgGEudn9zXpIhONpnsDCNagqNuelg.MrHe3ezregw1ckMZ5bvrcUVdPNazQwBECJE jP.VSLkFwk0N8PpeWKTEow3eRRdQ4D9VdLjBYqHgHnXfSwalvg3uD5NOwvOsDAcgTBuH1XGI2YM2 6XzqCwBYlzYowmahpQZkfWSNTyNgwFHAOGAwyBg4dyo2_qNJ.sVzBbQ1ROXugLbgjK7FTgiHGZXF GUbobBHtw3dwczUdl.yeOVeVlsVfEV8GcRIFiKDnD48a72v59QOEx1fiv4oxkqrVB5YnqeggssYi GWbjFcvpWNeDBABMSNkHCllk77qQVcT9EiV1thaSL3w5HSZsMWNXbjU6kwTAcD_RbTP9ILSnxGvu QWJw8CloM4jnUeLFLlI1g8ELo5v0vOVnASpPAEPm9kkhyMJxiUv4jf.9M_Ng9aMbKZs.b3Af4glQ 40o2mbV3Qd8jqOVUGbYr_FSbkMZEPpj2nke5n2xHquvLSVgQMHWvWcKo81OX4kOQb8KFHHtm8NoH FuXTEZOIWYLJY0ZV3t2WQ3EULTb1em5NKkNLFEpFX76vFdwz3GM1ghhx8qaaG16TKp1WD5VJzz2k yE3un.k6oFQfMXGNMiY.oqPlrQG52qUfHndqv8ekOtpBFpectBt0Cm2hpmTT.BdejEwpgVYGf1c_ svlbeo4n86IDDZlUs.qKqHotN4AW28NsjvvzAFK.JsC.wbfBKDB_qtwhTBzW2SZikNzx2K3chxXC TZ9QevFj2pPH9S26Qr.FU942Scp2c59IlOlXdFIauH_SUAUJYZAEsxwewIDEtpccrfIM5u8Zwv7k Kk0onz5yC9HTgfRdQg_cCY77ZvFF_jX4v32KwzT4PFoe6jqUtN9t_hE7EsHo2ZGm12vZubr6E3Ag .O5VGrm24ys06UnRpkV0C.3CEgwW4maCwmhU1k5MDP_tydGryjcHliZSeYo9AB5gmrckt02UHMWK LyFmGKfMYxQFiXU4Y9rt1BKan_f.X4iyRn7jj5aGlcwSKS44YWt7m52Pxvy962au6y6JefbuU_kU 1OxMh2kXQI737mFpgb_dhmv9.J6ePnQJB2ttuvEOltwPmaKef9pejnN5GGIgtt2eIyqEBcoj8HK9 F72qtrzhSiisjYDatcmdvNUa0zPk9nJmzuRllouSPyjaXtFkp.C1diCSx2Ryf1jx5xtz89yFZZ9G CjhTIPqawF1B4jYlbp9_0dBs_vh2BEGIbI8OKywK22huLkJ4NnsE21cI6W14PlEvbnHvLPL6mm2u 1zU7SnvVnocLBeDlQntRbOaDdASuROHeMAidpPhjSFpxZ Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.ir2.yahoo.com with HTTP; Sat, 23 Jan 2021 22:40:59 +0000 Date: Sat, 23 Jan 2021 22:40:57 +0000 (UTC) From: Kostya Berger To: FreeBSD Current Message-ID: <992972141.8836030.1611441657314@mail.yahoo.com> Subject: 13-alpha2 libncurses removal breaks ports build MIME-Version: 1.0 References: <992972141.8836030.1611441657314.ref@mail.yahoo.com> X-Mailer: WebService/1.1.17501 YMailNorrin Mozilla/5.0 (X11; FreeBSD amd64; rv:84.0) Gecko/20100101 Firefox/84.0 X-Rspamd-Queue-Id: 4DNWLk3BcMz3Hrb X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.02 / 15.00]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[77.238.176.163:from]; R_DKIM_ALLOW(-0.20)[yahoo.co.uk:s=s2048]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.co.uk]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[77.238.176.163:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.co.uk:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.uk,reject]; RCVD_IN_DNSWL_NONE(0.00)[77.238.176.163:from]; NEURAL_SPAM_SHORT(0.98)[0.984]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[yahoo.co.uk]; ASN(0.00)[asn:34010, ipnet:77.238.176.0/22, country:GB]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current]; RWL_MAILSPIKE_POSSIBLE(0.00)[77.238.176.163:from] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 22:41:04 -0000 Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING = about how one should handle the removal of libncurses.so.9 from base.=20 Source UPDATING only says:ncurses installation has been modified to only ke= ep the widechar =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 enabled version.=C2=A0 Increment= al build is broken for that change, so it =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 requires a clean build. If that means to just build all ports anew, then it doesn't work as ports d= on't seem to incorporate any change related to this one. It would seem defa= ult configuration should take into account this, but it doesn't. The ports just use --with-libncurses-prefix=3D/usr, and there is no ncurses= libs found there. This make it skip MOST of the ports I'm using. Working Copy Root Path: /usr/ports URL: https://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 562417 Node Kind: directory Schedule: normal Last Changed Author: 0mp Last Changed Rev: 562417 Last Changed Date: 2021-01-23 23:01:38 +0300 (Sat, 23 Jan 2021) With kindest regards, Kostya Berger =20 From owner-freebsd-current@freebsd.org Sat Jan 23 23:14:14 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1EB7C4E1B64 for ; Sat, 23 Jan 2021 23:14:14 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNX511vNmz3Lwp for ; Sat, 23 Jan 2021 23:14:12 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.16.1/8.16.1) with ESMTPS id 10NNCtRR040092 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 23 Jan 2021 15:12:55 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.16.1/8.16.1/Submit) id 10NNCtTR040091; Sat, 23 Jan 2021 15:12:55 -0800 (PST) (envelope-from warlock) Date: Sat, 23 Jan 2021 15:12:55 -0800 From: John Kennedy To: Kostya Berger Cc: FreeBSD Current Subject: Re: 13-alpha2 libncurses removal breaks ports build Message-ID: References: <992972141.8836030.1611441657314.ref@mail.yahoo.com> <992972141.8836030.1611441657314@mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <992972141.8836030.1611441657314@mail.yahoo.com> X-Rspamd-Queue-Id: 4DNX511vNmz3Lwp X-Spamd-Bar: / X-Spamd-Result: default: False [-0.45 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[107.170.196.116:from]; NEURAL_SPAM_SHORT(0.35)[0.352]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[phouka.net]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[107.170.196.116:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.co.uk]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 23:14:14 -0000 On Sat, Jan 23, 2021 at 10:40:57PM +0000, Kostya Berger wrote: > Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING about how one should handle the removal of libncurses.so.9 from base. > Source UPDATING only says:ncurses installation has been modified to only keep the widechar >         enabled version.  Incremental build is broken for that change, so it >         requires a clean build. > If that means to just build all ports anew, then it doesn't work as ports don't seem to incorporate any change related to this one. It would seem default configuration should take into account this, but it doesn't. So you found the right note, but yes, it sort of buried the lead. I've found with that and a few other libraries that I tend to get burned when you hit the "make delete-old-libs" phase of kernel installation, where the first clean-room poudriere port build still has them available for the ports to find. I usually end up re-rebuilding the kernel+world (so everything is now rebuilt without those removed libraries), updating poudriere with that, and doing a full ports recompile. If you're not rebuilding your own ports (probably really dodgy during this part of the release schedule) then you're probably just going to have to wait. From owner-freebsd-current@freebsd.org Sat Jan 23 23:24:57 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EED3F4E1C78 for ; Sat, 23 Jan 2021 23:24:57 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNXKP0sdkz3MK1 for ; Sat, 23 Jan 2021 23:24:56 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: by mail-pg1-x530.google.com with SMTP id i7so6417131pgc.8 for ; Sat, 23 Jan 2021 15:24:56 -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:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9guu7lK/o8LbcpI9rUCWgtKJ3w6mQhzdAGbv3B10FAY=; b=W8L4BsVyoEGSERVxBAUj3C7r/tIg81mQPLcQGIrUsXWHu9+R4DX/OoMuqTwTU1/xT9 IYdyss7YO20qX8OZZvB6bAf2b1OUSrzZsK5ZPDTe7PHA0GOnG0QM7zIO3Ir+44p9Qxq5 sYlp3HmYSu7pYXNpHx3kG0sfNXiLz6yC0iMzisgubVZG9punwdVW4Bqe0cFrHgMqv1Ec qP0TzroqUsgnCANiTjiKh/wJYH18r7Mgrjqr4wPZ5nABWI8Bk2GJFzlKlmLgNBh2+Khz cGiIhDXQU36zPq0BYwWramk5+RvKBAQa+ZiX6Cx6R8Oh++V0OiPp/PM9WVdAF9+fd1YF 3bcg== X-Gm-Message-State: AOAM531dW31ZUlTUdEBvhg1Dn6RoDztJaNzTV8CmOjNKdUOaKu4AZhVz Gvq5gnZ9zgeVb8IpjbVikgL6rCvylmS+4GnG X-Google-Smtp-Source: ABdhPJwrGOZmYcTKI0o4utNEaL6cL6kw+6zLJjzVTTyOvSJQ3S1fgRmYpSSnA51sgPiV9mbxnDw8sQ== X-Received: by 2002:a62:ee0c:0:b029:1a8:db14:927e with SMTP id e12-20020a62ee0c0000b02901a8db14927emr11479589pfi.14.1611444295761; Sat, 23 Jan 2021 15:24:55 -0800 (PST) Received: from macbook-2.local (c-71-238-26-71.hsd1.or.comcast.net. [71.238.26.71]) by smtp.gmail.com with ESMTPSA id r30sm12917938pfq.12.2021.01.23.15.24.55 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 23 Jan 2021 15:24:55 -0800 (PST) Subject: Re: FreeBSD 13.0 Build Option Sweep (13.0-ALPHA2 Update) From: Michael Dexter To: freebsd-current@freebsd.org References: Message-ID: <75c17848-17f6-4c3e-bf97-19ee1dc4493c@callfortesting.org> Date: Sat, 23 Jan 2021 15:24:55 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DNXKP0sdkz3MK1 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[callfortesting-org.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::530:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[71.238.26.71:received]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[callfortesting-org.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[callfortesting.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::530:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::530:from]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: 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, 23 Jan 2021 23:24:58 -0000 Hello all, I have re-run every option that failed under 13.0-ALPHA1 build under 12.2, on 13.0-ALPHA2 under 13.0-ALPHA2. HUGE thanks to everyone who has helped resolve failing build options! I have linked a list of annotated remaining failures plus an archive of the full build here: https://callfortesting.org/results/bos-FreeBSD-13A1/ Notably: WITHOUT_CRYPT WITHOUT_OPENSSL (Regression: Worked in May 2020) PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252841 WITHOUT_INSTALLLIB PR with a possible fix but it requires a decision by someone familiar with the repercussions: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252757 WITHOUT_TESTS_SUPPORT PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252843 I am happy to test patches! All the best, Michael