From nobody Mon Feb 24 02:54:23 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1QLV2h6yz5pWdW for ; Mon, 24 Feb 2025 02:54:26 +0000 (UTC) (envelope-from bsd.lists@h8spam.org) Received: from mx1.wiredblade.com (mx1.wiredblade.com [162.216.242.38]) (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 4Z1QLT5S9Gz41gr for ; Mon, 24 Feb 2025 02:54:25 +0000 (UTC) (envelope-from bsd.lists@h8spam.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bsd.lists@h8spam.org has no SPF policy when checking 162.216.242.38) smtp.mailfrom=bsd.lists@h8spam.org Received: from webmail.dynu.com (webmail.dynu.com [162.216.242.204]) by mx1.wiredblade.com with ESMTPA ; Mon, 24 Feb 2025 02:54:23 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Mon, 24 Feb 2025 02:54:23 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: RainLoop/1.16.0 From: "Chris" Message-ID: <4f09507d6ddba4979a418e7f30f1f94a@h8spam.org> Subject: Re: RFC: mount_nfs failure due to dns not running yet To: "Rick Macklem" , "FreeBSD CURRENT" Cc: "Gleb Smirnoff" In-Reply-To: References: X-Originating-IP: 24.113.41.88 X-Spamd-Result: default: False [-2.89 / 15.00]; AUTH_NA(1.00)[]; RBL_SENDERSCORE_REPUT_9(-1.00)[162.216.242.38:from]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; NEURAL_HAM_SHORT(-1.00)[-0.997]; ONCE_RECEIVED(0.20)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; R_SPF_NA(0.00)[no SPF record]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; SUSPICIOUS_AUTH_ORIGIN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; DMARC_NA(0.00)[h8spam.org]; ASN(0.00)[asn:398019, ipnet:162.216.242.0/24, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; TAGGED_RCPT(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; HAS_XOIP(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4Z1QLT5S9Gz41gr X-Spamd-Bar: -- Sorry if this is a duplicate. This time with correct email address... February 19, 2025 10:40 PM, "Rick Macklem" wrote= : > Hi, >=20 >=20The subject line basically describes the problem glebius@ > ran into. When doing an NFS mount in /etc/fstab, it failed > since the DNS service was not yet working and, as such, > the DNS lookup of the server fqdn failed, causing the mount > to fail. Note that this behaviour has existed for decades. >=20 >=20He feels this is a bug and that mount_nfs(8) should retry > getaddrinfo(3) calls until success, instead of failing the > mount when the first attempt fails. > The problem with just retrying getaddrinfo(3) is that it > could retry forever for simple failures like a typo in the > server fqdn. > I can see several ways this can be handled and would > like feedback from others w.r.t. these alternatives. >=20 >=201) Simply document this case and encourage use of > host names in /etc/hosts for NFS servers along with > specifying use of file before dns in nsswitch.conf. > Doing this results in the mounts working whether or > not DNS is working. >=20 >=202) Call it a bug and patch mount_nfs(8) to retry getaddrinfo(3) > until it succeeds. (I feel this would be a POLA violation, > given that the current behaviour has existed for decades > and for simple cases where the fqdn will never resolve > the behaviour would be to hang at the mount attempt > during boot unless "bg" is specified for the /etc/fstab entry.) >=20 >=203) Add a new NFS mount option "retrydns=3D", which would enable > retries of getaddrinfo(3). This would avoid any POLA violation and > would allow for a convenient way to document the behaviour in > "man mount_nfs". >=20 >=204) ??? >=20 >=20So, what do you think is the preferred change? IMHO Not A Bug. This is the expected behavior -- if a dependent service is not up/complet= e, then return failure. This has always held true for services dependent on name resolution. Star= t DNS early, or dependent services late. For domains/hosts you control it might be prudent to manag= e hosts(5). In any case, maybe your best option is document the appropriate man pages. I can't speak to to your software features. But maybe adding a delay, or = retry attempts may seem a good choice of Feature to you. But IMHO the reported error is pilot err= or. Anyone running NFS should already know how to remedy the situation, or be directed to the appropria= te man pages. --Chris >=20 >=20rick > ps: I looked and the return value from getaddrinfo(3) does not > appear to be useful to discern the case of "DNS service not > running yet". (I think it replies EAI_FAIL for this case.) From nobody Mon Feb 24 04:42:33 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1SlJ3Qx1z5phxN for ; Mon, 24 Feb 2025 04:42:36 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Received: from mail-yw1-x1131.google.com (mail-yw1-x1131.google.com [IPv6:2607:f8b0:4864:20::1131]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1SlH5GJSz46rw for ; Mon, 24 Feb 2025 04:42:35 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=CIIjHkrp; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of ianfreislich@gmail.com designates 2607:f8b0:4864:20::1131 as permitted sender) smtp.mailfrom=ianfreislich@gmail.com Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-6f6ca9a3425so33771367b3.2 for ; Sun, 23 Feb 2025 20:42:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740372154; x=1740976954; darn=freebsd.org; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=DoVibmuc+xMk5iMYkEvA3v/XRt6lQ7XQ/NC4t8wYkbM=; b=CIIjHkrpRDXRBk/TVKjTQ1dqQZDenKixXK7Mjrtshf9iwlROxqnUQI3PwbDgfoTT/E 4DXj+H42R2PNGokCWJMD28AbmuQjDwZld74UxCfzI0xmrrRvl8qEBd22jGlo5SQo0K5Y fsL8MHSPaBUWrMLnEUQxlAtSNvssFRJEAIrXuv32l1/SRq4a1tMcUCis9P70u8qVvCF+ QblfhSuzCGaxDQk3Yka41KJLI93CTqh6SflR6ve+OeGJLl7SMm4UhjYa91fak8Wfx1NK wxGd024mJXeHQDTsbgMAL6yRW5RanC8sik8/lUrTZAcBhxtHE+2OdaDdaoieSAtaQ32J CI3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740372154; x=1740976954; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=DoVibmuc+xMk5iMYkEvA3v/XRt6lQ7XQ/NC4t8wYkbM=; b=gIMwhl5QxdbOJKnHyqbisIvhtByjrouKOMOzaekdFHGgQCFSNuqKHb6a67s+v/5vv7 WqP6iNT5JQDgPhKj9o8/EtkoNgaU3W2RpIpwQ7r8keVc2DnFGhuOO4bhayCYu11ymyvp 4hGb8iEP8qDQyZ4ca1Pfz0Hs9VKSjQNQwHsbBKgmHevmh1BiT7gflUKO0C7/wBXg4a4h +QIGMUusGEZBRfN836aGHJFJzxcVLSraZdIBX3Iscu4RWG0BxLsRyLTGXjwEEwaJebjQ sbDRtKgLaeCZksWjQwfUPC1DdqM8YDdmAhGV00k/hnhGlvYH5CshjXo3pZwmPStp7RYO CMvg== X-Gm-Message-State: AOJu0Yzi27mQn+7/kd5QOjN17HQd/5RoAVWz639tWlxyLZtHyQ4vf0kA lqaOm1gIA0EjMIpKtgN5O9CvUyHURx9nOYckftGclEqRqeoPqln2yi5CXQ== X-Gm-Gg: ASbGncstvHjos7fgJahyvIgPyBninXZqR8LqEte3m4XRVvNEc37sOraymCCI38dK1kV NL8XymmU9J2ZUVPD8wWqUu29kbeAtT9uqqb79fWuWHF0Vw1dgKEnyqXyRI86GxYnkpTjsuAiEIk Ckl1jdwLjZfGDlnZI5nY22QXw2msnakxn1wg/zzgoSYOogs4ZT1KTd+Cgn/aO7RAKhKrbAT8fSr T3puSafnLoVU0CNeuC/cJT+HnlKss46C2Yo1LVCjx/K4EUkIlHVid25lVBurLBAUFo3t6lB+EEM rG/2rKSR1cH77dHH8YAFF2jz8xhGCnMOXdVdDLRl1IwMQGxs9pT4cajcLtBSrW+NEzIPZ2GAIoN nIjjdOg== X-Google-Smtp-Source: AGHT+IHkoXNRE3/UDIgamEx7gaeZ3hJGV2hjlk3Wd1c0Ub/bg6RkPLwUFYAV1tyR+rn0DkkUYYtmfw== X-Received: by 2002:a05:690c:6a12:b0:6ef:5097:5daa with SMTP id 00721157ae682-6fbcc856ce4mr100767857b3.34.1740372154504; Sun, 23 Feb 2025 20:42:34 -0800 (PST) Received: from [10.0.0.5] (107-128-20-168.lightspeed.tukrga.sbcglobal.net. [107.128.20.168]) by smtp.gmail.com with ESMTPSA id 00721157ae682-6fb3619cabcsm53705397b3.74.2025.02.23.20.42.34 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 23 Feb 2025 20:42:34 -0800 (PST) Message-ID: <4858aa49-f102-49fc-90c7-9bd7480306c9@gmail.com> Date: Sun, 23 Feb 2025 23:42:33 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Thunderbird Daily Content-Language: en-US To: FreeBSD Current From: Ian FREISLICH Subject: buildkernel failure in net/toeplitz.c (commit 3b281d1421a78b588c5fc4182009ce62d8823d95) Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1131:from] X-Rspamd-Queue-Id: 4Z1SlH5GJSz46rw X-Spamd-Bar: --- Hi Building a kernel today failed with: -Werror /usr/src/sys/net/toeplitz.c In file included from /usr/src/sys/net/toeplitz.c:29: In file included from /usr/src/sys/net/rss_config.h:33: /usr/src/sys/netinet/in.h:692:23: error: call to undeclared function 'htonl'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration] 692 | return (in.s_addr == htonl(INADDR_BROADCAST) || | ^ In file included from /usr/src/sys/net/toeplitz.c:32: In file included from /usr/src/sys/sys/systm.h:98: /usr/src/sys/sys/param.h:343:13: error: conflicting types for 'htonl' 343 | __uint32_t htonl(__uint32_t); | ^ /usr/src/sys/netinet/in.h:692:23: note: previous implicit declaration is here 692 | return (in.s_addr == htonl(INADDR_BROADCAST) || I think this is a result of changes to netinet/in.h (3b281d1421a78) which added a static inline function using ntohl() which is not defined in kernel use. Ian From nobody Mon Feb 24 04:53:11 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1Szb1xp4z5pk11 for ; Mon, 24 Feb 2025 04:53:15 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta003.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (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 4Z1SzZ2bYNz3F4n for ; Mon, 24 Feb 2025 04:53:14 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=permerror reason="p tag has invalid value: quarantine rua=mailto:p[ostmaster@cschubert.com" header.from=cschubert.com (policy=permerror); spf=pass (mx1.freebsd.org: domain of cy.schubert@cschubert.com designates 3.97.99.32 as permitted sender) smtp.mailfrom=cy.schubert@cschubert.com Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTPS id mAyHtRm0A9JM2mQSvtg1xa; Mon, 24 Feb 2025 04:53:13 +0000 Received: from spqr.komquats.com ([70.66.136.217]) by cmsmtp with ESMTPSA id mQStt4J1k4k0omQSutAQbU; Mon, 24 Feb 2025 04:53:13 +0000 X-Auth-User: cschuber X-Authority-Analysis: v=2.4 cv=fLKa3oae c=1 sm=1 tr=0 ts=67bbfb39 a=h7br+8Ma+Xn9xscxy5znUg==:117 a=h7br+8Ma+Xn9xscxy5znUg==:17 a=kj9zAlcOel0A:10 a=T2h4t0Lz3GQA:10 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=YxBL1-UpAAAA:8 a=pGLkceISAAAA:8 a=ASre1B6bsTNvbFaSfpwA:9 a=CjuIK1q_8ugA:10 a=LK5xJRSDVpKd5WXXoEvA:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTP id 77EF218E8; Sun, 23 Feb 2025 20:53:11 -0800 (PST) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (Postfix) with ESMTP id 5D33B712; Sun, 23 Feb 2025 20:53:11 -0800 (PST) Date: Sun, 23 Feb 2025 20:53:11 -0800 From: Cy Schubert To: Lars Tunkrans Cc: Rick Macklem , FreeBSD CURRENT , Gleb Smirnoff Subject: Re: RFC: mount_nfs failure due to dns not running yet Message-ID: <20250223205311.7569a16a@slippy> In-Reply-To: References: Organization: KOMQUATS X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4xfKbWmLMw2pMReih4GbTnS7jH3aNiblzvFGmCmGLm5PsRdBHGsw+tr+IsWA8+kL129RDEeqwWg61S6Bvo4whiMQmDOpWo6HFw0vyAEQREHbxAvF11bHF5 LuZwJ5quVfRKsMvaaJuN6GvVDR3nBYeSVy9ZFbN2BDKYRL5leVqUaQotfaGWqiTykkGmsIpCYKrpzMB8SPj7VNtfh+fRhiMLkZd106br22KSZqBkvB2BkWzH XHQBQpQPeYsSQdt2zzOkhvxIy1YG5m6x59t5Wr+oMSAJfErNkS4gfYQE6b1QYf0g X-Spamd-Result: default: False [-1.57 / 15.00]; SUSPICIOUS_RECIPS(1.50)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.944]; NEURAL_HAM_LONG(-0.83)[-0.826]; MID_RHS_NOT_FQDN(0.50)[]; RWL_MAILSPIKE_EXCELLENT(-0.40)[3.97.99.32:from]; R_SPF_ALLOW(-0.20)[+ip4:3.97.99.32/31]; RCVD_IN_DNSWL_LOW(-0.10)[3.97.99.32:from]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; FROM_HAS_DN(0.00)[]; DMARC_BAD_POLICY(0.00)[cschubert.com : p tag has invalid value: quarantine rua=mailto:p[ostmaster@cschubert.com]; FREEMAIL_TO(0.00)[gmail.com]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org,glebi.us]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_DKIM_NA(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4Z1SzZ2bYNz3F4n X-Spamd-Bar: - Excuse the top posting. I am replying to a top post. Correct. This is not a bug. It's been NFS behaviour ever since I switched careers from IBM Mainframe to UNIX ~ 30 years ago. Sun Solaris behaved this way, as did Tru64, DG-UX and HP/UX. Typically a sysadmin needed to -- and needs to today -- put NFS server IPs in hosts(5). One person suggested using late for NFS shares. That too what Red Hat does. NFS mounts are flagged by systemd (and prior to that upstart [rc.d]), with _netserv. _netserv would cause the NFS mount to take place after the network is fully up, including DNS resolution. Solaris didn't do this when I last worked on it and AFAIK it still doesn't. I think our choices are to document that sysadmins must either use hosts(5) or ensure NFS shares are mounted late. Or, mount NFS shares after the network is fully up. A retry forever, until DNS finally provides a good answer, can potentially hang boot. This would be especially troublesome for remote unattended reboot in which remediation would require calling remote eyes and hands remote support to "fix" the situation on the console. BTW, with NFSv3 and v2, uninterruptible mounts, i.e. those without the intr option, did behave this way. NFSv4 doesn't support intr. I think the easiest solution would be some documentation. Next would be mounting NFS shares later at about the same time late mounts are processed (actually, immediately prior), like Red Hat Linux does. A _netserv fstab(5) option could serve the same purpose it does in linux, immediately prior to late option handling. Altering the kernel wait forever is undesirable. This would result in boot hangs requiring console access to work around the problem. This would be a PITA and POLA for unattended remote sites. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e^(i*pi)+1=0 On Thu, 20 Feb 2025 01:25:20 +0100 Lars Tunkrans wrote: > This situation has existed these past 40 years. You have to put your > ipadress : hostname pairs into /etc/hosts if you dont have accsss to a > working DNS. This is not a bug. Its the way name resolution works. > > Den ons 19 feb. 2025 23:40Rick Macklem skrev: > > > Hi, > > > > The subject line basically describes the problem glebius@ > > ran into. When doing an NFS mount in /etc/fstab, it failed > > since the DNS service was not yet working and, as such, > > the DNS lookup of the server fqdn failed, causing the mount > > to fail. Note that this behaviour has existed for decades. > > > > He feels this is a bug and that mount_nfs(8) should retry > > getaddrinfo(3) calls until success, instead of failing the > > mount when the first attempt fails. > > The problem with just retrying getaddrinfo(3) is that it > > could retry forever for simple failures like a typo in the > > server fqdn. > > I can see several ways this can be handled and would > > like feedback from others w.r.t. these alternatives. > > > > 1) Simply document this case and encourage use of > > host names in /etc/hosts for NFS servers along with > > specifying use of file before dns in nsswitch.conf. > > Doing this results in the mounts working whether or > > not DNS is working. > > > > 2) Call it a bug and patch mount_nfs(8) to retry getaddrinfo(3) > > until it succeeds. (I feel this would be a POLA violation, > > given that the current behaviour has existed for decades > > and for simple cases where the fqdn will never resolve > > the behaviour would be to hang at the mount attempt > > during boot unless "bg" is specified for the /etc/fstab entry.) > > > > 3) Add a new NFS mount option "retrydns=", which would enable > > retries of getaddrinfo(3). This would avoid any POLA violation and > > would allow for a convenient way to document the behaviour in > > "man mount_nfs". > > > > 4) ??? > > > > So, what do you think is the preferred change? > > > > rick > > ps: I looked and the return value from getaddrinfo(3) does not > > appear to be useful to discern the case of "DNS service not > > running yet". (I think it replies EAI_FAIL for this case.) > > > > From nobody Mon Feb 24 07:52:14 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1XyP6b2kz5q1D8 for ; Mon, 24 Feb 2025 07:52:29 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1XyP5jQFz3wpm; Mon, 24 Feb 2025 07:52:29 +0000 (UTC) (envelope-from zlei@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740383549; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=EBYMQRIP3ZExGTPAl5pi0UVnr/kcwUFllU7d5pZKvgc=; b=bOGBAtoXj8InVf7nzxzuDRAIlKaC8VzG4gMsVmBwCyhHbhv3dCniL0GCCgsPSSWXCai0MX 1vZ+vTrUrLeWt3RA7yWd86JHNx+ryj2jpVYvwnQdSDutjI++wGsXQzUg35vSkiuYwxcpTg FX1NiZJg349h8PpWMSegt/sBCuVOI4ailLlSavvIFw6D9OK6rIAkgTPFA0t031xD1Yo4oU 6vliLPVSyRVaWbBCVTr8/gtVSYUDrnDwVKsnwAmozBpETJQbYtclZZ/6GBnM+BxfjvmEbp v7TLzX0arZzFIcI7O/DfkD5M0TfI+MyPq/yiiz4oSCd6bgEnMYeAdjGGFjIu4g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740383549; a=rsa-sha256; cv=none; b=oncT0SJ3r5PzXJyIDd7+CJfFR6llEv5LMQaeT6A3o/RLOKKcW4OSW3/idE/QGPmjE9g4r/ QxzLHgWBEZM/LO81ad1fPANwWJoQyxz4LMYVhdnml4ItdTx9xM6PSX8jnFUDa0c5HDmpCZ MnO0xBrsTItME73vrNG7Ym+qKjFyRG/gQUtVAkgluWcemefeCh/gbLacVz+j93wDfNONWI v+/NC17HKY67S6URH+6U9GpT1o6Dxqjj4t0BGMtertokDmLZbwUpvFNXBdcTnRqZGwhUD+ ybMvXDWb4lTXp3xeLlZDjQkh//LDSVaNa1jrBqdXCeJsFAAP+3EZDN65kXo5Fw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740383549; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=EBYMQRIP3ZExGTPAl5pi0UVnr/kcwUFllU7d5pZKvgc=; b=Gk1IO0VfFMrpWB94DecrCTa8ZGVKpuffArH1gjqR3253JCOra9wBRtB1wPEJ/bBEeYtCyb F0iQFwK3sSAqFsJ4it26+8IGSpLVi2FGBk3XGSsWITirhZ1Rpi0e+rId4yspIbXLtjb3U3 KAGwioWvPDcVx+8aHHe3zg6kNsb4apZtGPVzHQDh70A/geRdh0uoUmjWkE3Ju74PvWkcMN A7e3L9lfxsJpyvhAaoQcfxlfIPhUjpIVqamMVAExa4QErYuiHkSA7vMP7TsUmKzu45C+qQ CVRKzVzJ9cJ7kOoI4+m9ep60HzYnPhV/HfQr2bvs0L2uAIvL1/+G8pQSjzYiOA== Received: from smtpclient.apple (unknown [IPv6:2001:19f0:6001:9db:98f0:9fe0:3545:10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: zlei/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Z1XyN05w7zQCN; Mon, 24 Feb 2025 07:52:27 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Content-Type: text/plain; charset=us-ascii List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.10\)) Subject: Re: buildkernel failure in net/toeplitz.c (commit 3b281d1421a78b588c5fc4182009ce62d8823d95) From: Zhenlei Huang In-Reply-To: <4858aa49-f102-49fc-90c7-9bd7480306c9@gmail.com> Date: Mon, 24 Feb 2025 15:52:14 +0800 Cc: FreeBSD Current , Gleb Smirnoff , Mark Johnston Content-Transfer-Encoding: quoted-printable Message-Id: References: <4858aa49-f102-49fc-90c7-9bd7480306c9@gmail.com> To: Ian FREISLICH X-Mailer: Apple Mail (2.3696.120.41.1.10) > On Feb 24, 2025, at 12:42 PM, Ian FREISLICH = wrote: >=20 > Hi >=20 > Building a kernel today failed with: >=20 > -Werror /usr/src/sys/net/toeplitz.c > In file included from /usr/src/sys/net/toeplitz.c:29: > In file included from /usr/src/sys/net/rss_config.h:33: > /usr/src/sys/netinet/in.h:692:23: error: call to undeclared function = 'htonl'; ISO C99 and later do not support implicit function declarations = [-Werror,-Wimplicit-function-declaration] > 692 | return (in.s_addr =3D=3D htonl(INADDR_BROADCAST) || > | ^ > In file included from /usr/src/sys/net/toeplitz.c:32: > In file included from /usr/src/sys/sys/systm.h:98: > /usr/src/sys/sys/param.h:343:13: error: conflicting types for 'htonl' > 343 | __uint32_t htonl(__uint32_t); > | ^ > /usr/src/sys/netinet/in.h:692:23: note: previous implicit declaration = is here > 692 | return (in.s_addr =3D=3D htonl(INADDR_BROADCAST) || >=20 > I think this is a result of changes to netinet/in.h (3b281d1421a78) = which added a static inline function using ntohl() which is not defined = in kernel use. >=20 > Ian >=20 May you please have a try with this patch ? ``` diff --git a/sys/netinet/in.h b/sys/netinet/in.h index 0925e3aa7669..4dad4e4fed4d 100644 --- a/sys/netinet/in.h +++ b/sys/netinet/in.h @@ -689,8 +689,8 @@ void in_ifdetach(struct ifnet *); static inline bool in_broadcast(struct in_addr in) { - return (in.s_addr =3D=3D htonl(INADDR_BROADCAST) || - in.s_addr =3D=3D htonl(INADDR_ANY)); + return (in.s_addr =3D=3D INADDR_BROADCAST || + in.s_addr =3D=3D INADDR_ANY); } ``` The `htonl` is pointless here, as INADDR_BROADCAST is all 1s, and = INADDR_ANY is all 0s. Best regards, Zhenlei From nobody Mon Feb 24 09:00:12 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1ZSb2TXkz5q6SQ for ; Mon, 24 Feb 2025 09:00:15 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1ZSb1vqJz3VWG; Mon, 24 Feb 2025 09:00:15 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740387615; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=YBaTQNNzbzMToayQRtHSCEzJLO2UjOPj8WIh5hWKseA=; b=lQzsEM8FoPf9v2ltYk8jHb7r7y0/EPkXK9EBGz1fNCcG0tJXL6r/bJ0+TVwEB+ALOpjPMf hiKqK6wVvK9cbyoT98Qi6TcHhFJkj39XvxQI+nVOsW2rtoMk0ehApYRk9typ+oMc2lIsgD Wd/kt6c2vo/jTXNoIvNLjxIslvAoUzvlc/16qT5HNGPF47FmgE7BwOwU/tCsdn5exWe7SR C14WWOOdnb695SErSah20lXgETN6UKnsr1wik5zzhytOtbJjn3g940ufQMfQai9E2oC+u0 EeKyTRzRC/igb/jGXz21/O5PbbZbA9wbVQruAT+8wbvXfbIw6KoibkUFad+9TQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740387615; a=rsa-sha256; cv=none; b=oKFf7rGIK60eBI6OITApxiqunp5P3oOOx+OK4jyGrVU6I0F6XuSndX0aXvk4WmujZi44x2 mma0jwTCNbQ64BmIsbpWCwn+vIB7zeu3tAyxo3XVqjBNEwpU2TYBtqA6cT057TFF70Z7qZ N9qY5ufJ5zGXgdhR+5ugfz//DMbgblpewSqvgdNniUONDwGjDH9NW5laa8QpzR4kDCStn5 yWvyfS/vIrygSUSjS2U7SzCGU3IWuF54aBBB5mXo0xrCcWlTXYzb4aMzCAu5/K9WGZ/lek JSIizGhSADodVT2PlnGaiyJ/BeZiJj1TlqZdG4HDTG+Z6Uvp6XHo2eJaL0Is4w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740387615; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=YBaTQNNzbzMToayQRtHSCEzJLO2UjOPj8WIh5hWKseA=; b=pqoKWTFSBgrU5A+8zxoUNkBmGgTmmn6MS8dH13x8fY5Cbtuwfdtsur0aIWh4OLonwc4MTQ Wdugo7awEBeBZY+dR3Md5Z5v5HgRHyWO54S1dwYJzlErGYSRMKCdn4Bzn1NSiQC+Xl+k4I 04LjIENVQSyuvCb9dA3uzoiKXKGGk/EXjNuXKIkQOA0dyT5H9bOoKPBso8qnD9hAStf2kx IkJ8M6nKWvLHPu2c61F7Gwygta8y+JQOOOJY4BV7hwJjCrljAGh4GwTST/5DFGFWTnfNU2 sz114eXb0u8UKrqptB34GeDhVhy/31tHKV5tOVe/6wdhabszTRoNzVyYUeUkZQ== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Z1ZSZ5vHGzQGh; Mon, 24 Feb 2025 09:00:14 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Mon, 24 Feb 2025 01:00:12 -0800 From: Gleb Smirnoff To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: February 2025 stabilization week Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi FreeBSD/main users & developers: This is an automated email to inform you that the February 2025 stabilization week started with FreeBSD/main at main-n275634-389265e3ca82, which was tagged as main-stabweek-2025-Feb. Those who want to participate in the stabilization week are encouraged to update to the above revision/tag and test their systems. The tag main-stabweek-2025-Feb has been published at Gleb Smirnoff's github repo. To connect this repo as an additional remote you need to run: git remote add glebius https://github.com/glebius/FreeBSD Once remote is configured, to checkout the tag run: git fetch glebius --tags git checkout main-stabweek-2025-Feb If you want to use only the official FreeBSD repo, then update to the revision: git pull git checkout 389265e3ca82 Developers are encouraged to avoid pushing new features to FreeBSD/main during the stabilization week, but focus on bugfixes instead. The stabilization week runs up to Friday 18:00 UTC, but if there is consensus that any regressions discovered by participants have been fixed, it will end early. Once that happens, the advisory freeze of FreeBSD/main branch is thawed. -- Gleb Smirnoff From nobody Mon Feb 24 13:04:53 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1fTR4kbYz5nxXh for ; Mon, 24 Feb 2025 12:01:15 +0000 (UTC) (envelope-from mohammad@thelightbird.com) Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1fTQ5xQfz3w36 for ; Mon, 24 Feb 2025 12:01:14 +0000 (UTC) (envelope-from mohammad@thelightbird.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=thelightbird-com.20230601.gappssmtp.com header.s=20230601 header.b=t0GYVDKm; dmarc=none; spf=fail (mx1.freebsd.org: domain of mohammad@thelightbird.com does not designate 2a00:1450:4864:20::235 as permitted sender) smtp.mailfrom=mohammad@thelightbird.com Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-30a29f4bd43so37731161fa.0 for ; Mon, 24 Feb 2025 04:01:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thelightbird-com.20230601.gappssmtp.com; s=20230601; t=1740398472; x=1741003272; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Gr8kJTXMv7Qutdi2fyXjO1eytc2KYJFn0PcAL4sMr3Q=; b=t0GYVDKmpskLelA64SN9a+s+daPNyWH0z4+Ol1Spi/e7HDrWwWAo2ZzsRh+eGz1sVm b0hf4HRB4wxYaDpjLF125QczQWGnOuGCvH8gHIK6k9IKNcHi51E/xC4TtZ2fEanWH8Yq RHXXorFRmBXbm8UgCJZKgZHim7S+ky9vFPF43qL1zp77zA4Ez5Qlw2O12QbMVnEdn/qW ZFDLAtwzOD1YvhDVF8yf3SRMgbAmzLvqPcXPT4Lm0yLuc2wwozpCnLB6OxNCRdMmaM5V nVhsbeLnEfkal19fGNAHrbMTqci3MA7ZnJ2jktplzwfIgpRQs/xRDUJtXBhTyoNg3Jht eNkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740398472; x=1741003272; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Gr8kJTXMv7Qutdi2fyXjO1eytc2KYJFn0PcAL4sMr3Q=; b=MDBrPGRbuKq7TAzioh25YFdZeCoi+HZDtfiq2/N25gSh88gH7Pjr53QPuL+mnPkGaT Tq+jodJH0RTEQZsMmHS87FhaVsoMQoAMqggtOBxCnfcq6BKoXknHWQH1PTJK54YFhnpv +CDd1Ha4ZfLuMF1eRr9/UZ0JlqLrlRXtinGWxj5lMQWyv+r0D8wdy1PSiCAFf/kueNMx xJqxAgWgR/QJ2tDVVa8BY258AP/Y5keHhUR2F/ftCmfmL/cVJTDPVkVswYN7p+c1yHdP AxRDM1dWm8AzJhzzPYyXDQp3LXzoSu2R1F7aCJxTf+Lg+u1ew1fMN+i8+i9IJOSGjv8Y CZYA== X-Gm-Message-State: AOJu0YwbjTe3T7Ro3EF5C7CE6k+0Rv9rSaIv8CSrAqtAdcM9d/6zW+SI bUaqb8cfZk5fNLGSQCFEQ7kL3HwkDIOJdbM0XDF3Ejb9R7by7DOcpicMoTzNvnHabHjlAkuY2QD 2CKeAY7eU+m6bkmfM4jm04KPdv2f27Qzj189osr0c7hctCH8= X-Gm-Gg: ASbGncsSa+VIw6LqqoNc7RZLtRdOpKnFn8clfQZZEPT25niL1RpRjM5pSoSgZVQAjfv R2PMiCoQ7qqn5CQx3SE/OwfPN36R5JZy1oBvjCGRheiEfkLDWcY5j4ypj5pa0JfobiM7fmXeNri HvaV0YEw== X-Google-Smtp-Source: AGHT+IHg6pxpN5HJwXU5i2iZ+rO4rXBR3Y+riDaMMkKudbb7KmDIMGg3yDjnuZMFWYwWlU4v/TYqjw5PK9orG9IsqjQ= X-Received: by 2002:a2e:9b0c:0:b0:309:20b4:b6d5 with SMTP id 38308e7fff4ca-30a5998bae8mr41816561fa.28.1740398472100; Mon, 24 Feb 2025 04:01:12 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <002301db8341$cd1ffc60$675ff520$@gmail.com> In-Reply-To: <002301db8341$cd1ffc60$675ff520$@gmail.com> From: Mohammad Noureldin Date: Mon, 24 Feb 2025 14:04:53 +0100 X-Gm-Features: AWEUYZnRX6-mNZyeoAzMNuVchQnJ-KB7bMyqtl8uztVIeNVviQpEdt61gfWgXjQ Message-ID: Subject: Re: Very poor -CURRENT boot performance on AMD To: Maku Bex Cc: Freebsd current Content-Type: multipart/alternative; boundary="000000000000b29bc0062ee218a2" X-Spamd-Result: default: False [-2.30 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_SPF_FAIL(1.00)[-all]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[thelightbird-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[thelightbird.com]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::235:from]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[thelightbird-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4Z1fTQ5xQfz3w36 X-Spamd-Bar: -- --000000000000b29bc0062ee218a2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Maku, On Thu, Feb 20, 2025 at 3:47=E2=80=AFAM Maku Bex wr= ote: > Hi Mohammad, > > > > The performance issue(s) have been noted on the UPDATING file. Here is a > snippet: > > > > > > NOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW: > > FreeBSD 15.x has many debugging features turned on, in both the kern= el > > 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 rebuil= d > > world, or to merely disable the most expensive debugging functionali= ty > > at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".) > > > > -----BEGIN PGP PUBLIC KEY BLOCK----- > > > > mJMEZlPMfxMFK4EEACMEIwQA/hAHZ4KNJLw5eRl6DAOyzkuHQ7PaK2hTYLVIPoxC > > sCe8lB/hzET5KxMW9GXgFgPaSP7Es+ul6ajyq8pr9DeGnXUAFymi7GoT1kLIqgrn > > X+rDAwMk9JNEElTmVNvgKWv/G+pSg2rAQ8sIw6smgckA0CaX1JdcNavrHDgKMO4u > > Duo44Te0BkpPTUlTTYjbBBMTCgBBFiEENyUvu5bQVBXM019e8anbed+sQ8YFAmZT > > zH8CGwMFCQHnaREFCwkIBwICIgIGFQoJCAsCBBYCAwECHgcCF4AACgkQ8anbed+s > > Q8Y5BgIHcX19jz0KP89uTmqvLGZcKsITDJKweAnccCZRS8hvXT8JBwR1LyxsBBKF > > ++eN2JJasZLo+s6sy7pDMN+9z4Gkdy0CCOj+arfLdvajfzdK4QeKpINfpa2SkQD1 > > CP98lvfI/luIbetUVW+qNDkzT1jZphYuzgsCaofTGCIQpFk19q22ZcZquJcEZlPM > > fxIFK4EEACMEIwQANy4VvpnTHneZipCPwzVJnMN82coCudRAiL2i2m3GPA06lRtU > > njcn9r9Sm26A0sajwc3kQw/ekWrHXpXV0aL076cAUW9GKYDljIHVlr76wgHbLt6q > > BX5VkA6xS0cq3skbMEI0QpIqIK81Yf0z8wfyF5uqAgNPUpY4nHMV9S856JB2VDQD > > AQoJiMEEGBMKACYWIQQ3JS+7ltBUFczTX17xqdt536xDxgUCZlPMfwIbDAUJAedp > > EQAKCRDxqdt536xDxjIuAgjacZCttPWpKGfMbnNWePz6t9rcMUb496tSWfKRActr > > Rco8lSaDNTVohT/6hLZ5wUX5NFUqTb+kOXJcUGHGbnw2KQIJAQu1m9zEP5XdWmFi > > SvGg1NHW2kzqAvFsG37flbwrGRu5fmTnS/LZ/oPzOCuwU6F+o1q0E7gLwFwnzD93 > > riKeabdd > > =3DiCV+ > > -----END PGP PUBLIC KEY BLOCK----- > > > --snip-- Thanks for the reference. I've made some more tests with 14.2 and I got the same results. Though 14.2 was relatively better but still I got the same poor performance as indicated in the video recording. --=20 Thanks - Mohammad Noureldin -- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein --000000000000b29bc0062ee218a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Maku,

On Thu, Feb= 20, 2025 at 3:47=E2=80=AFAM Maku Bex <zagazaw2004@gmail.com> wrote:

Hi Mohammad,

=C2=A0

The performance issue(s) have been noted on the UPDATING fi= le. Here is a snippet:

=C2=A0=

=C2=A0

NOTE TO PEOPLE WHO THINK THAT FreeBSD 15= .x IS SLOW:

=C2=A0=C2=A0=C2=A0=C2=A0 FreeBSD 15.x h= as many debugging features turned on, in both the kernel

=C2=A0=C2=A0=C2=A0=C2=A0 and userland.=C2=A0 These features attempt t= o detect incorrect use of

=C2=A0=C2=A0=C2=A0=C2=A0 = system primitives, and encourage loud failure through extra sanity

=C2=A0=C2=A0=C2=A0=C2=A0 checking and fail stop semantics.= =C2=A0 They also substantially impact

=C2=A0=C2=A0= =C2=A0=C2=A0 system performance.=C2=A0 If you want to do performance measur= ement,

=C2=A0=C2=A0=C2=A0=C2=A0 benchmarking, and o= ptimization, you'll want to turn them off.=C2=A0 This

=C2=A0=C2=A0=C2=A0=C2=A0 includes various WITNESS- related kernel op= tions, INVARIANTS, malloc

=C2=A0=C2=A0=C2=A0=C2=A0 = debugging flags in userland, and various verbose features in the<= /u>

=C2=A0=C2=A0=C2=A0=C2=A0 kernel.=C2=A0 Many developers choose= to disable these features on build

=C2=A0=C2=A0=C2= =A0=C2=A0 machines to maximize performance.=C2=A0 (To completely disable ma= lloc

=C2=A0=C2=A0=C2=A0=C2=A0 debugging, define WIT= H_MALLOC_PRODUCTION in /etc/src.conf and rebuild

= =C2=A0=C2=A0=C2=A0=C2=A0 world, or to merely disable the most expensive deb= ugging functionality

=C2=A0=C2=A0=C2=A0=C2=A0 at ru= ntime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf&qu= ot;.)

=C2=A0

-----BEGIN PGP PUBLIC KEY BLOCK-----

=C2=A0

mJMEZlPMfxMFK4EEACMEIwQA/h= AHZ4KNJLw5eRl6DAOyzkuHQ7PaK2hTYLVIPoxC

X+rDAwMk9JNEElTmVNvgKWv/G+pSg2rAQ8sIw6smgckA0= CaX1JdcNavrHDgKMO4u

Duo44Te0BkpPTUlTT= YjbBBMTCgBBFiEENyUvu5bQVBXM019e8anbed+sQ8YFAmZT

zH8CGwMFCQHnaREFCwkIBwICIgIGFQoJCAsCBBYCAwECHgcCF4AACgkQ8anbed+s=

Q8Y5BgIHcX19jz0KP89uTmqvLGZcKsITDJKw= eAnccCZRS8hvXT8JBwR1LyxsBBKF

++eN2JJa= sZLo+s6sy7pDMN+9z4Gkdy0CCOj+arfLdvajfzdK4QeKpINfpa2SkQD1

CP98lvfI/luIbetUVW+qNDkzT1jZphYuzgsCaofTGCIQpFk19q22ZcZ= quJcEZlPM

fxIFK4EEACMEIwQANy4VvpnTHne= ZipCPwzVJnMN82coCudRAiL2i2m3GPA06lRtU

njcn9r9Sm26A0sajwc3kQw/ekWrHXpXV0aL076cAUW9GKYDljIHVlr76wgHbLt6q=

BX5VkA6xS0cq3skbMEI0QpIqIK81Yf0z8wfyF5uqAgNPUp= Y4nHMV9S856JB2VDQD

AQoJiMEEGBMKACYWIQ= Q3JS+7ltBUFczTX17xqdt536xDxgUCZlPMfwIbDAUJAedp

EQAKCRDxqdt536xDxjIuAgjacZCttPWpKGfMbnNWePz6t9rcMUb496tSWfKRActr<= u>

Rco8lSaDNTVohT/6hLZ5wUX5NFUqTb+kOXJcU= GHGbnw2KQIJAQu1m9zEP5XdWmFi

= SvGg1NHW2= kzqAvFsG37flbwrGRu5fmTnS/LZ/oPzOCuwU6F+o1q0E7gLwFwnzD93

riKeabdd

= =3DiCV+

-----END PGP PUBLIC KEY BLOCK= -----

=C2=A0

=C2=A0--snip--
Thanks for the reference. I've made some more tests with = 14.2 and I got the same results. Though 14.2 was relatively better but stil= l I got the same poor performance as indicated in the video recording.

--
Thanks
- Mohammad Noureldin
--
&= quot;Life is like riding a bicycle. To keep your balance you must keep movi= ng"
- Albert Einstein

--000000000000b29bc0062ee218a2-- From nobody Mon Feb 24 13:11:01 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1fcW3cDPz5nyMd for ; Mon, 24 Feb 2025 12:07:23 +0000 (UTC) (envelope-from mohammad@thelightbird.com) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1fcV5HMcz40TB for ; Mon, 24 Feb 2025 12:07:22 +0000 (UTC) (envelope-from mohammad@thelightbird.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=thelightbird-com.20230601.gappssmtp.com header.s=20230601 header.b=MUEU6lwr; dmarc=none; spf=fail (mx1.freebsd.org: domain of mohammad@thelightbird.com does not designate 2a00:1450:4864:20::22f as permitted sender) smtp.mailfrom=mohammad@thelightbird.com Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-30a36eecb9dso43389341fa.2 for ; Mon, 24 Feb 2025 04:07:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thelightbird-com.20230601.gappssmtp.com; s=20230601; t=1740398841; x=1741003641; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uwtf/f1jcNT2e2REoHhtWdjN8bhvrcpQw3ykgE+Ulfg=; b=MUEU6lwrjHOkBHEi26cHKcuKv4sG2rWRwPaI9eBa+zPAJ5pJVz50UAIFbfoscmgBrX LIvbGwgCjRnj3ycTj47f7lELQLfSM0XXjRqr/7IyzYlKMjB6t+s3rf+MuMW+S/bSNWLe HBMqAUnclnG+DYR5OdT9zRQSJSXUS1gbOboyHOVbymYTaDUnc3F9oICg73VmPxgQewot w2uf91B4j0kRAW0yQdzHDxZ5Ks/+plqFCV9ZYfl/BzcZX/9DHBEurKCPUNlRYCcWdM09 DEojtdWsej1EX/JvJLZ3vOc59ZOnra6kYkgT45TTZdXxfMW9wywZh31yHcZkmtwGTDvr awzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740398841; x=1741003641; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uwtf/f1jcNT2e2REoHhtWdjN8bhvrcpQw3ykgE+Ulfg=; b=xLKSNlxtipfMSk3DXpblFob9V8pX0pQuswd2eECxUw83unGXcoUKAeQs1XkZyW/Wkc 9oVrAwDnpSEY/5g1uYrB75qdRTOxSrAhi81PS94vDiZX+exeGt+5jwWW2cIxyR4EgiAT 65YbnjLZHVbb6EkKTQc4M9IWB2D0brM/Kh3Rcbtz6hS5+im+5OmSaRwh8ZnWSKebMGSW XD+G1ULprtnzpDWMekBVzxr1jQuxjYJFPVBOeBFyqwK9CSOjjnWQs1pLYUjbvWRupTPO lE+hnxZ0NngLDjgO8g9wZdsICUyyLWgV4wK4WB7rfcD/uFvgSzg4Q3Vo/av8IyUVq7t0 3J+Q== X-Gm-Message-State: AOJu0Yzvt/0lVHynpiyhM+VAtUM/d5N2oB5w5QQcRlP1b/t0VvBJTaJa UId6fu5qv9EO9DOi7rLOysTGnmJAVNcNgjwytlZS+cq2PGtJZOTCyBRdqJjrWn3OmVf2TRtNrkn hOiD0JTN/Q4D09r08XyIkXOl8fd4gyDyJ0GKQC58UUaBpC0M= X-Gm-Gg: ASbGnctzSs6Jzegx29ydkY18hur4dk5qqhtjObVa6qZzPYufgSchZteA2j/mp+bdhvj H8RJ/d5JBdtc7/HqSxF7iHpUGJeGHXoG4vdHTLFtLv3/qyjUKAoBeVMrtgNbC2Jj6PipvHepmMk r6Q+EB3w== X-Google-Smtp-Source: AGHT+IEnbixsPwm8ZMdLdSNynkl9Bb1BORlx8aWGFS/uLlGaA5ov0gFROyirZyfajek22pasihS7fhaRvg0eDXdc6sE= X-Received: by 2002:a2e:b386:0:b0:308:e803:1175 with SMTP id 38308e7fff4ca-30a59777b35mr42339171fa.0.1740398840846; Mon, 24 Feb 2025 04:07:20 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Mohammad Noureldin Date: Mon, 24 Feb 2025 14:11:01 +0100 X-Gm-Features: AWEUYZmpQGAvJXTFM3_pYCsC7tJZ6vMB5bG6ymsH4RdQeeapJgCreQNP4loiHvA Message-ID: Subject: Re: Very poor -CURRENT boot performance on AMD To: Rupesh Pilania Cc: Freebsd current Content-Type: multipart/related; boundary="000000000000ad49e7062ee22ef6" X-Spamd-Result: default: False [-2.30 / 15.00]; R_SPF_FAIL(1.00)[-all]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[thelightbird-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/related,multipart/alternative,text/plain]; RCVD_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[thelightbird.com]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::22f:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[thelightbird-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4Z1fcV5HMcz40TB X-Spamd-Bar: -- --000000000000ad49e7062ee22ef6 Content-Type: multipart/alternative; boundary="000000000000ad49e7062ee22ef5" --000000000000ad49e7062ee22ef5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Rupesh, On Thu, Feb 20, 2025 at 5:11=E2=80=AFAM Rupesh Pilania wrote: > Hi Mohammad, > > I tried the same build on VMware and it came up very fast. I don't have > any AMD Ryzen based hw to confirm the behaviour. > IMO you should raise a PR. > [image: image.png] > > Thanks & Regards > Rupesh Pilania > > On Thu, Feb 20, 2025 at 8:00=E2=80=AFAM Mohammad Noureldin < > mohammad@thelightbird.com> wrote: > >> >> --snip-- Thanks a lot! I do confirm that it indeed runs pretty well on Intel. --=20 Thanks - Mohammad Noureldin -- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein --000000000000ad49e7062ee22ef5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Rupesh,

On Thu, Feb 20, 2025 = at 5:11=E2=80=AFAM Rupesh Pilania <rupeshpilania@gmail.com> wrote:
Hi=C2=A0Mohammad,

I tried the same build on VMware and it came up very fast. I don= 9;t have any AMD Ryzen based hw to confirm the behaviour.
IMO you= should raise a PR.
3D"image.pn=

Thanks &= =C2=A0Regards
Rupesh Pilania

On Thu, Feb 20, 2025 at 8:00=E2= =80=AFAM Mohammad Noureldin <mohammad@thelightbird.com> wrote:

--snip--

T= hanks a lot! I do confirm that it indeed runs pretty well on Intel.

--
Thanks
- Mohammad Noureldin
--
&qu= ot;Life is like riding a bicycle. To keep your balance you must keep moving= "
- Albert Einstein

--000000000000ad49e7062ee22ef5-- --000000000000ad49e7062ee22ef6 Content-Type: image/png; name="image.png" Content-Disposition: inline; filename="image.png" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: ii_m7ctpfym0 iVBORw0KGgoAAAANSUhEUgAAAsUAAAB5CAYAAADRXFw/AAAAAXNSR0IArs4c6QAAAARnQU1BAACx jwv8YQUAAAAJcEhZcwAAFiUAABYlAUlSJPAAABaMSURBVHhe7d0NkuQ2joZh71xg6nQ+pI/Qp/Ke YGfQNmq/hgkSlKi/1PtEKDqThECQUmbRFVnp//nzzz//77f/+vr6sn8AAACA1/nX3/8CAAAAr8Wm GAAAAK/HphgAAACvx6YYAAAAr8emGAAAAK/HphgAAACvx6YYAAAAr8emGAAAAK/3/T/v+PHjx8+G zO+///73o3P88ccffz86f+yz2Bxbc5udu8cfvU5nX5Oz5oV7yV4XqKusYfX13Hod6rlRzNU6HwDu 6B+/KdY3rivfxD79DXTmh8pd8EMNR+u9LlBTXcPK63m0obX2eETexrUFcHe/bIp7b2i4r+yH0dN9 6ryAJxhtiGd4DjbGAO7s++MTX19fPxtM782w9aa25U2zkkfryGqKeSo5TC9PNl4cy8Q8I60cJqsn q8VpvlG/m61ZVWtxMS7Wm+WLcUrP6cVV6Plmy1jVeuJYJstj4nOzaiwzimmNb2L7TB6NbcVEcexV RjWbVTEjniPL7e2jsVr9ZmvNWV2m15fZcg4AnGlqU9xqX/Xm2Gsz1j4aK+uP7bPPTbWtanSu9xuL 6cVnfa320bgje8YaPY96/bO5KrIclbFGMavOMVvO2xNjsrZKHpPl1hiTta+0tb4tMRV+jom5jbXN jNWrIfbNxCrvi1qxrpcPAO7gNt8+YW+U2Zvl6I3Wj0+05weIn6tr01vnN/r0+8ftve6ftEZ3fl08 ZZ19vfQwn3KPAHinR38lm78B65vy0fyH1lPe/PWH1VNqPouvx5n3z934fdG7N3RtsnWq5LmT6uui Mq9KTEVlnQEAx+F7iifZD6t43J3WufcHNz6L3sd6n0S9PqPnj2LvQuvMXhc6H41XlZiqvecDALa7 zaZ4xW9azraq5qPmHevzH7ZHjYf7ivdCSyWmYmWelr354/nV10Vl3ErMmfbU0luX2Xl6bLbhn80H AEf4xx/axTem+CbWeuPK3uh6Rnm0P7459+J6MdU8TvtNJWZGqw6j4/RqNrGmI2teMVa1nupY3h6f V+k4dm4rT2WsmRil/UZjrO+ssVxvHJeNr6rnxDjT6zOj/oqZmtWWmJFsPrF9Zqwsp9E81t+LNVl/ tZ5RflOJAYCjNb994u14gz4H64yt7N7hvgEArMRniv/LfsD6Bg3HYZ2xAhtiAMAR+E3x3+JmjR+6 x2CdAQDAHbEpBgAAwOvx8QkAAAC8HptiAAAAvN73xyd+/Pjxs6Fl5nOf+pnRvZ8Xbf1RVsxZian4 xLFaOZzmWjWvKh3vyHGcj7dnrLhGWa7KWL2YOI6JcZUYU615j1YtZkvNo5hsLFedX3VdVtTsemNa X5Y3q61iRY5VWnNUK+erNF+rhr3jjuZlKjF7jeYOoOb7N8X6ArLHW19Qq16I+mal9eiLvxJT8alj Oc2j+czqsSp0/KfRNYoqa9aLqVyLSozT/qNo/qyeI+bl9HFV5fyza26ds4fWdrXK3HprV6Hz9cPE fFvzt1RyrRwvU507gLHuxyf8xXWVq8ffw96QWm9K+qY1o3deNhb+snXNZ1TW/67X6En3T+s6Hn1t z7LqGniep62L13v0vfiUex3A+dJNcfbGau3xyFRiMlve0LeM07IqD7bR+8aPKPZV45S29+Iq7H4d 3bOVGOR6a3eXdd17jbfef1V6j/tjbXOxL/abUUxsa8VcZU8dlXltiTGxrRVjsnaTtQMYa26KRy82 f+P3N/8svhJTpWO37M3vVuXRubfYOH6YVqzGeFzLzFi9PHfg9fmcfF5ad4zR51GrzWluz+XP30Tn jusdef/Fe7x13bVP7w2tqxKj7SY+v5rWOqMyr0rMEbbOCcBfHvHtE/oG3DLqr+rl8TaL8WMPy+eH aeWrxPTo+VkebfMD16hciztfL63H63yTvdfk7DXz8ezfN12vT53rm197wCrNTfHoRbX3zX9G9YW+ 6o2gl8f69PgUnzqvJ6pci0rMFe5UyxVWzP/ta3iWT11n7h9gn/Q3xb0Xl/XF4wh32hDPOus/GsyZ Y+HzcP/85S5rcNT7KX71hHX2GvXe9Mexfu4bYL/dH5846gdq9sK/yqp5HrVeLZWxzqwHfZ9wvVo/ xJ/gafX23Pka9Gryvidu7iprHWPidcrmr3FZDIA10v95R/aiiy9sE2MrMSOtHE5zrRjLnDUv86lj VcXxttRTrbk6lrfH566aJ9K4rTGVsWKMGdW8go7h+b3trvNqjeNW1GxGca1xRm2zenldlj/GmRhb iXGj+Yz6K0b1tMbYO27l/FGM1r01j+ZwW+cEvNn3pvjr6+tnA/A0lR9MAHBHvH8B9/GIb58AlP0Q af1mBACehA0xcC/8phiPFDfF/FAB8CRsiIH7YVMMAACA1+PjEwAAAHg9NsUAAAB4vcs3xWf8wZSN 4Yc+BwAAAMylnyn2jWnvDw3i5nX2jxJ0DM215Y8bWrm25AEAAMC93HpTbP2xr9Vmztik6hhnjAcA AIBzfG+K/f9opxs+pxu/2GfixnAU0+o3Mcafa7y1aZ/zmNi+SlazmRkz1tmqW9t03DhOrCnrH7XH PCaes8qoZgAAgCt8f6Y4bpBamxXt88PoRqcSo+0mPld2Xq/fVWL20NzZ41U8Z5y7rqHxvqzfaXuM 8efVXHudNQ4AAMCM5h/a+YZFNy+4H9tQ+jFSjdtKa4mHytoBAACu9JivZLt6E6XjZ4/P5ONW/sNF +7NYy+fHFl5H63AzNQMAAJzpEZti20z5Jkofqz0bugodM3t8Z1Znr1bv1wMAAOAtbrMpjhta25T5 Btg3aGzWznH0f2AAAADczT++fcJlm8/WZinGVmKcx1bH+4RNsc7J5tNag9jWizGtPK1zTBan4jmr jGoGAAC4wqXfUwwAAADcwWP+0A4AAAA4CptiAAAAvB6bYgAAALwem2IAAAC8HptiAAAAvF76lWzq iq/Lan1NmIm1jL5OrJpnteyrxrJ6zGxNo7lXVdew15bNq3VOVIkxOpaeY6r1uHh+plLPmbJ6svVQ GlPNM8NzVmpxs+ON5lVVXZ9eWzav1jlRJcboWHqOqdbj4vl7tcZbPcYWcV2uMlqf3vWqXNNsftn8 R/WYSkzFTJ6Zep3GbhnLHDWvVTEjrRyulWvv3Ed69Rgb8+ga1Oz6uO/fFGuQPT664JGsHp2oP/b+ Voy3mSxmtUpur0WPGZW5V6zK4+eZLM+emKhaX8w3q1rPWbJ6dD38sfe3YrzNZDEzKuf5OHrMqMyr YlUeP89kefbERNX6Yr4tbCwfTx87f+71+jgx7q1m1ifGtGhMLzZb/0o9MzX3zOSp5NY8ms/M1qzn zqqMtSpmRsyTGfWvouPEMc+qwcQ6qmN3Pz5x5gRWubrmrTc2ctk1Ha1167wV9wevi19xz693t3v+ SWy+d5hzpYaVdd75ddi6JkfV2xrrSpV6tta8ep52TfZcl1Y9q2vco1JLuin2hdEkumD+WNtc7Iv9 phIz4rXFc6+8CDb2FeNvWb/MVXNo8Xll9WTz7tW/Z26teqzN2/2xtrnYF/tNJWbEa4vn7pl3j+U9 KnfPlrXJXDWHFp9XVk827179M3PT/NnjqNfXY+e1zo3t/jy2R70Ybe/FjVTyVNZ75f3m41dzxnqv YLWuXIOe7DopjenFnSXWE2uaudat81fr1ZP1teqKba2YLTxHrMXz+9HcFPvJkSfz/tZEtc8Pozkr Mcra9Ryl52bn35HXu6LuJ817RnVeZ80/Gyfev/EeNdrnh9GclRhl7XqO0nOz88/mtayo6S5zWq06 ryPnr/dS9litqEVztPLZ2H6YbMysRqPnVnJltuTxPo9t6cVYnx6qd15LPP8oWu+eMSt5ejH+XK9V i/d7TMyj7TpOK6fGeFzUi/Hno5qUnuNinpFq3ApWm4/Vm9cKWf7W+mz+9glPoMmOomO0JjfqvxOv VQ+ztW69qJH1ZceRdIxWXaYSM7L1vCN5Tfbv0fXpGK1rOuo/i9ehh9laU+++sb7sOJKO0arLVGJG tp53lL3zUbo+kfdl/avoOPHYys/dskZ2TjzM1np6tWhuPyLti0e0t2Y9f5SnEjPi88jO9fbKWKti PpnP+26am+IVxdoF9iNTiZnBzfUra8+OI1XynxmzyoqxKvd8JWaG170q3x1k18Las+NIlfxnxuyh 90n2WK2oR3PEfD6utR89dx+jdWyhtfdU43osh14jfax6Y/hc/Yhivx5Pput/p7n4Nc2updP68U+j ddE1Tn9TvHdx/ebSI6rE9FRulk83u2YVd1pXn1+vniPWILN3LDs/HlElpufTXxez61HBPf//NHf2 2K2sw3KtzHc1v35Hz8nXLa5fa9xWG+5Lr6sfR7rT++BqvbXT9d388YkZlYX+5IuhZub55DXxG7BX fyXGPHUNRirXtxJzdzNzePJ8uefh/Pr59e7pxVrfWffCmWNV3K2eq2Xr4W2Vew19tpbp/7wje4Gq 7CK0LlyMHcW0+s1ReVapjDeq2XlcVms1z0glzyhG+7091j8bE2XnmFabifli/0jl/OoYMc6M6jUa 0+o3R+WpqOQa1eM8LqujmmekkmcUo/3eHuufjYmyc0yrzcR8sX+VVt2zY43m4O06lrWNznPVvDFu ZJQn1qFGNUWtXNVYjavkmRmrZ+tY5oiaNcb6/Hk2ViXG9cZyR8WYVp1K81jMKH6vWLeOE2sxrXpW 1NyrQ8W4703x19fXzwYAAADgbU75+AQAAABwZ2yKAQAA8HpsigEAAPB6bIoBAADwemyKAQAA8Hqb v32i9xUZ8SsuzMxXabhRnla/2zKeyea1cqzZ9clqGmmdF9t68zK9uNl6TCXPipjevLbU/Xa2nndZ N722V9dUuVev4HXtreUOa31EDXe6h9C25Rqtuu9xvN711T7Xu6Yrr/um3xS3CnZanB+md07LTJ4Y s1WlRh1ry5iz61OpaQWdR5zTbM2ZSp5VMU5jNBZ1rXWNLEaPI93lGvo847119PzPovMzV83riOt9 RM67udt9OFvP0dfo6etztKPrya6vj2v9fpisntV1Tm+KRwXoJM4wM5bVftbCZmPNrM/qmjKteo66 hqvyHlUf5tl9atdDj7Pu3Sv5XO9odW13nutbZD9TWu72+jurnup9+tb1qbpbPdl1PaLOQz4+Ec3E uniOTr6XpzdWpY4spnKumolvxWrb7NhulDfK+raOXxFzZ89Nb/xRnk+h89K1MTrX2GfiWoxiWv0m xvhzjbc27/N2fexirkj7leaMRnmyemKu2Ncb01Vioko9rbzZWFmOGZrDZGNYey829pleve7KmIpR Hu+3thjbijMa26qp16dacbEty+XtKssTY2Mut3UsU4lxGpvFmFY9sa0VY0b16HkxNuZyR481yhNV 68n6R+2jerI8kcZVz2nReuz8w/7Qzgbyw2wp1mnRPaOxrH1PHUbn1atrNFbMobGttk80mqf3j/Ty WJ8eT+dzHM3ZWJ8fRudfidF2E58rOy/r9zYdM6rUU1HJo21ZTMyjzyPr88O0Ynp0fB/Pn28xO36L 5mjlizW2YrTPD6PzqsSoPXlizFaVsWJba7yYpxdrPK5nlKMn1uM5vN3EttE4WVxlLFWNGanW3VKp ObaNxsniVo1VyaN6uWZzmBij+VtjKIvVQ2meveKcDtsU+0A62BYrJ7+HzscPs3Veq/I81ei6Vq97 Fudrq4f5pHX2Oen87u6JNY/4XHw+b3st+7x1Dc7WWvsr61Few9H1VN8zM35edQ29PYvZW89qT1of b1s1lspiRutj/X6MVON6vE6vZ2++TKz1EV/Jll0k5ZOqxD5FvFj6+Mmq12rU/4nX/On23qN2vh97 rMqD/SrXohIz4u8De/M8kc9373vhqjVcVc8qT1yfVWNVjOrR/l7NRvtHsXvFtZldp9a8b78pXrmo cQGPtGcsm7MebuVa7LV1fn7OaC6j/moenMeuiV8PfTzDzonHFqvyYL/KtajEVOi5W96f7szm05qT t21ds2jvGq6uZ68nr8/esSqOuF5a9xE8fxxnxZjLN8W2wEddvMwRFzVaNa8r1ucuVl2nSp43r/OR 4praNbA2+9evhz7eY9U1XJUnmsm7twZfT8/h/25d5731bFUZd0tt8Zy4XrO21HClI15ve9ZwRT0r PW19Vo4VxdzmbtdrpdZ8e6a/fSJLrovaitmy6NU8Hrfnwt5xXibGzo5XHWs0zoq5t3I4zTUaa1We J4pzyuZTmfvM+nhsdTyNW1mzGeWr5PEYb4/PzUweFWNMK7+q1GN0vFEut6ce16vDVPOYUS5zRoz1 +fMsLra70Vixf2uelXQsG6M1x1XzqqjMvRKjWnOq0rHs/FauUT2xf0sdbtVYozxVmsfO9+eeKz53 WZxp5TEa42JeF2NH40fab483fyUbALzF6I31LHepA+txbefFNWMNsdcj/tAOAM5kP1z9B+xd8AP/ s9zxHgPejt8UA0BD3LBcuRllQ/yZ7nSPPRVriJXYFAMAAOD1+PgEAAAAXo9NMQAAAF6v+fEJ/YxO /HxO/PyO6X2G55M+Czeae6vfeZzFZGuqMZlRTMxtYmw2vmrlOZvWtbdmj7/DvAAAwP00f1OcbRx0 Y+GHaW1QTNaemY0/mtZTmbu3GY2JRvOs5MliWrljrKrM6yqxVjdb8x3mAgAA7m33xyd0U6JmNyJ3 27isqqe1NmY2f5YHf1l1HwIAgHf6ZVNsGwg/9vDzqxu5LF7r8UPNtunR4/2j+rONmBvlGdXhqvWs MppXxurUI6q2+/NW7Aw//6x1AwAAz/W9KdYNxGgToZsWP89pnoosXtu1pjjeyGyerJ5Z1TpHcdU8 dzC7xibG+HPNk7FYPZTmAQAAGNn08QnfsPiGI25Iqnobl1ZuHbNqJs/MRspi/dhidh49WsfKvLNm 1qQa1+PX0ee8Nx8AAHiv3Z8pzsRNT9yw+PPeJk43O/H8GZU8lXrUKK6S58yYo+n6jerR/qNrj9c8 u/4AAODdlm+KfVPkh9PHMxtQzbNnQ9PLM1PPjErdlTEreVaycY4ey+a0er2V54/jHDkmAAB4rsN+ Uzwy2pzEjZnH99r8X81dyWNG9WwVx9lqlCebFwAAAMZ++Z93xM2jP4+bzCjbUMbY2Y1ndaxYdzRT c08rj/FcWb+JMTp+bJvJY3q5Tcw36jcxpiLWFOsZ1RfjTCuP0RgX87oYm8UBAID3av4f7Z6mtWkC AAAAqi77+MQqbIgBAACw16M3xWyIAQAAsMJHfHwCAAAA2INN8clafyAW8ZtvAACAcz3+M8UAAADA Xpdviiu/Od3LxvBDnwMAAADm0k1xZWPqG9itG1k/xz+SEJ/P0Br0MQAAAJ7t1h+fsE2nbV71yDai 2SbVz9PH/hwAAAAw339o9+PHj58NtmGMm0vdRGYbTzWKafWbGOPPNd7atM95TGxfJavZzIzZy+OO mgMAAADavn9T7Bux3uZS+/wwutGrxGi7ic+Vndfrd5WYPTR39hgAAADP1Pz4hG/07F82fQAAAPh0 t/5MsdLfNF+h9dtwc3VdAAAA2O8Rm2L/CEV8rKz9yA2qjpk9BgAAwDPdZlMcN7S22fQNsG889TEA AACwyj++fcJlm8/Wb2NjbCXGeWx1vKdviltrEz19jgAAAE/zvSn++vr62YBjsSkGAAC4n8f8oR0A AABwFDbFAAAAeD02xQAAAHi9788U//vf//uzAQAAAHgbflMMAACAl/vtt/8A9U/sjj4Of/oAAAAA SUVORK5CYII= --000000000000ad49e7062ee22ef6-- From nobody Mon Feb 24 13:20:48 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1fqn2cVQz5p0p6 for ; Mon, 24 Feb 2025 12:17:09 +0000 (UTC) (envelope-from mohammad@thelightbird.com) Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1fqm4VwKz4632 for ; Mon, 24 Feb 2025 12:17:08 +0000 (UTC) (envelope-from mohammad@thelightbird.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=thelightbird-com.20230601.gappssmtp.com header.s=20230601 header.b=UGYAboWE; dmarc=none; spf=fail (mx1.freebsd.org: domain of mohammad@thelightbird.com does not designate 2a00:1450:4864:20::232 as permitted sender) smtp.mailfrom=mohammad@thelightbird.com Received: by mail-lj1-x232.google.com with SMTP id 38308e7fff4ca-307d1ab59c6so47969461fa.1 for ; Mon, 24 Feb 2025 04:17:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thelightbird-com.20230601.gappssmtp.com; s=20230601; t=1740399426; x=1741004226; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=R0ue4QFlCJmcvXuWaR+iUVbYckXIwGD9oY4i4SZK30I=; b=UGYAboWEh/gdOoeBbcDd1jaUTGJXrSzBDELNEBC6XY+ZM+A5PVlrtd5Y+nQEkUwc/e Yz+Zy6N0jTy9gHbL05kpwJ3yCNut62tNrjQECTklXWrVaC1jv1qTVrNkkDxnBgPGMNnu N2UUgUPT0vQKWg92evEtCpjDN9CDfn0fCXgAuhxSNJVFFjioQKHpAUhwAYE3PX0anj5a +RArxejrLYoZnN6eYK+QJm4L4OwOPBLF3Hd9sEVmS90ktj5BJy2HXFZNpAi9nwhAsRPt Zi0aN3ivR/S6IiJEmPe6VTPT5pIjjSpSbDiVwvVBKJAS+NiUUCOCoVCYIe3Lr5xGlu8e R5nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740399426; x=1741004226; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=R0ue4QFlCJmcvXuWaR+iUVbYckXIwGD9oY4i4SZK30I=; b=kZlNw4fWMYcieG04Ere2MTLm9pbNwpUsHPSGBioVNofEQpLXq585Ryhwp0MiMJcXIp YaVwmCzzQaRWVZoeDAmuk7qfj3LpUzmR62BMvhJzCKEsHbSbGoKIVdNX9uKw+3Jm1nMk lJRYqqyQxA84dUQyHyDpgEgYeXMvZXeYZF6ETfnobdtxfltx3f6VNkunHI+t6XcozfUH hj+/D3WefwPmrTdnZ5WmrVWyFfjjCIMZVYXqFmWWRgLRnRJDqz6A6xJhcfgUhwZytoZh ZjYgvtV4pMAMoAZL0OzZERRHvQXqJDpKT3vho3S6GnTIWPxVD2x+ahcGjfwXGI9wz46D zu2Q== X-Gm-Message-State: AOJu0YyRuVyNr5Swp+bL8UqgJ085CjXAGEH9v8MruXcwEfkPLPmx7ZN2 ILK/BWbUr0+r1/4fwbBtAB22h5hsbJnx0y8z+ojrTfMcXva4aCQtlr19ow3n5VPcJMI5XdbykwC gCYireqL4hZLwe9dsSvKUYoswICaa1UmzTNb7 X-Gm-Gg: ASbGncv54o6xdd8nnjOpf8jpqD18WM6UuloSgR60tgyjOs8ZphcB2UqmxJSH9Jdd7Gr osXDskSjZN52m4TEU8izTL4LYEdq90ZgAtNqFbTGXYubSgZWZdVdOeIE3lWu9nMeHo9hOKfpyuk /ZEA2/9Q== X-Google-Smtp-Source: AGHT+IE3dhtmGgU0gZ/VFD5Yz0NGOO3sddBTheAQkrC8Pqo6nfuW5Y4c4iExjnwFuB8+CzYMuZT50C1fK+F71JBOyZg= X-Received: by 2002:a2e:968b:0:b0:308:f0c9:c4cf with SMTP id 38308e7fff4ca-30a599bb2demr43604771fa.33.1740399426527; Mon, 24 Feb 2025 04:17:06 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <3c7dab54-ac92-4a65-8517-e1636361e33d@FreeBSD.org> In-Reply-To: <3c7dab54-ac92-4a65-8517-e1636361e33d@FreeBSD.org> From: Mohammad Noureldin Date: Mon, 24 Feb 2025 14:20:48 +0100 X-Gm-Features: AWEUYZkr1UGXAD2ugn3tQABctVovW8sUWLGD3OVznNQbagrnI2FtbJ3yh5EgYb4 Message-ID: Subject: Re: Very poor -CURRENT boot performance on AMD To: Jung-uk Kim Cc: Freebsd current Content-Type: multipart/alternative; boundary="00000000000095fde6062ee2519a" X-Spamd-Result: default: False [-2.30 / 15.00]; R_SPF_FAIL(1.00)[-all]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[thelightbird-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[thelightbird.com]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::232:from]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[thelightbird-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4Z1fqm4VwKz4632 X-Spamd-Bar: -- --00000000000095fde6062ee2519a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Jung-uk Kim, On Thu, Feb 20, 2025 at 5:22=E2=80=AFAM Jung-uk Kim wrot= e: > On 25. 2. 19., Mohammad Noureldin wrote: > > --snip-- > This happens because UEFI framebuffer access from boot loader is very > slow. Once the kernel is loaded and booted, everything is okay because > we properly set memory attribute. It's a long standing bug and there's > PR254381. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254381 > > Jung-uk Kim > Cool! Thanks a lot for sharing. --=20 Thanks - Mohammad Noureldin -- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein --00000000000095fde6062ee2519a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Jung-uk Kim,

On Thu, Feb 20, = 2025 at 5:22=E2=80=AFAM Jung-uk Kim <jkim@freebsd.org> wrote:
On 25. 2. 19., Mohammad Noureldin wrote:

--snip--=C2=A0
This happens because UEFI framebuffer access from boot loader is very
slow.=C2=A0 Once the kernel is loaded and booted, everything is okay becaus= e
we properly set memory attribute.=C2=A0 It's a long standing bug and th= ere's
PR254381.

https://bugs.freebsd.org/bugzilla/show_bu= g.cgi?id=3D254381

Jung-uk Kim

Cool! Thanks a lot for= sharing.

--
Thanks
- Mohammad Nourel= din
--
"Life is like riding a bicycle. To keep your balance you = must keep moving"
- Albert Einstein

--00000000000095fde6062ee2519a-- From nobody Mon Feb 24 14:46:21 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1k812Qtbz5pG2w for ; Mon, 24 Feb 2025 14:46:25 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1k8014WRz3G4Z; Mon, 24 Feb 2025 14:46:24 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-e545c1e8a15so5159733276.1; Mon, 24 Feb 2025 06:46:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740408383; x=1741013183; darn=freebsd.org; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:cc:to:from:date:from:to:cc:subject :date:message-id:reply-to; bh=RzeMNiNo4o1P4yTS1eVPJKdDslZjKZwlmkBmdlkZVpo=; b=gMcJSaCFZoJTtRvZoJzpcU8IlG6cX6sd+57hJXVniuNdM3F+QdP0sp7aDqxg6HbzE2 wzI8f49Hf8QLMttZdA8GkzD7RxPxMc2MjvyqoO67Cq5ETq28sLHoDbTiEYEcrjZI1EiR jwgZgkJD0nClK7nVCicrhUjXs3iamblb88wSDUahGSyihAnlB0bfc4asUMvhbrGIWzl7 slQRh+Iq+GQiQD1fcH6x9fpSMNZ81bXQ4o/jUrfekMMdSrmVZG7lklGe+Lud+t7W1GOQ A6JkO7cl4qOB6x9s5bvXWaDjv8RMPubeyMXiMQtDzxTVwtnhteViI6Yy4k55yIqhmTR3 aZ3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740408383; x=1741013183; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:cc:to:from:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=RzeMNiNo4o1P4yTS1eVPJKdDslZjKZwlmkBmdlkZVpo=; b=dZzQSneFCiejwWfEJ8UXmQKSJbdYOdJjhMMksM9b+7Omw+4MdvgAFz6x0TFrlC8DCj 91f7Zq2T6EosmDRT0+MX0aOKguK/smiM0PqvnyTnlLOLQKCrqH8WOZWaxfVZmZzax/7Q qhTtHNM6I1i+UOHwqwF2s7FGh11zKDjd7G2t/AAIGxEtJv2Y7ezHh9/4yyX5EQGs8tkE EGBUvQzGn1mKJifPKw/PaysqPUN1B14bs6IgA2A9h1PlYV+D4zklgx4lDOrjYFbNBTrX Gim87JVcMPh6YUwVJ25/qB8VJwnUbF+Xq+eg9BPLqwUcTj8YPT80NSqeOSDue3jfeMqx Vqfw== X-Forwarded-Encrypted: i=1; AJvYcCWX5P52YlXjaInayjUlh8/1nixqGvVhpsaer05C84P9ocHA+EHUr1WDIYwHjkNDT6L01MASLSzp@freebsd.org, AJvYcCWgka3YOJbejazbpuBivi/rzxNMM30riw+CTROQ7OyxgZzwN1jxq/QdpmxVuRcOiWxRQ4y1nqU=@freebsd.org X-Gm-Message-State: AOJu0Yy8r0pOh+IwP5/SOwbtMRyY+gUhrN1Tes5DIorhQ2wT2mvo3BLD BHL8dKSD1yAa6uXF01yT3eiFwMcCqZe7QKgocW/nt0AHxWiFAJeDTBaeQUiF X-Gm-Gg: ASbGncsvqXVlMh6ojm9IDnZPN46h8FpBSrI1pm0ePgFRurIaPxaVRqtZFFkxMMWN7Be mW7/wIM1cv+0F3nRCYP2dx5YRxDXEpXXaN8RSdph9QBoJDCeBbg3lmrMTS0LE7Bh69oGNpeC4Eq PmlH1uC8RP8sqdmbOIX8e9yqGSxUzP6h72OTITOsr4AYgxUOcrNo+SLFna2M69+us/cAvCtaZyM 8tvonb30tk0hLZUq1DHM9FKigaXsNqlMOCcPKoN3z9BWrLGJmoHVb8yFFsofulmtlIMsu6zCxps cWBCAzK/ULNr6VgswFmH2zIr8XmBpelc+wl1I8Vfwq00KC5Dgk81y18mL//HQJMoDSum5z5tLTd qRBsT9Q== X-Google-Smtp-Source: AGHT+IFENQ7l7mmXd91Wi9hJGN8WCC/XqDV7gDs0jaJLwbS/xGH+bIPnWDSo64uVutOsub4XuJvw1A== X-Received: by 2002:a05:6902:3483:b0:e5d:b88a:5532 with SMTP id 3f1490d57ef6-e5e24694600mr8169549276.40.1740408382611; Mon, 24 Feb 2025 06:46:22 -0800 (PST) Received: from [127.0.0.1] (107-128-20-168.lightspeed.tukrga.sbcglobal.net. [107.128.20.168]) by smtp.gmail.com with ESMTPSA id 3f1490d57ef6-e5dadea936dsm6214493276.17.2025.02.24.06.46.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 24 Feb 2025 06:46:22 -0800 (PST) Date: Mon, 24 Feb 2025 09:46:21 -0500 From: Ian FREISLICH To: Zhenlei Huang CC: FreeBSD Current , Gleb Smirnoff , Mark Johnston Subject: =?US-ASCII?Q?Re=3A_buildkernel_failure_in_net/toeplitz=2Ec_=28co?= =?US-ASCII?Q?mmit_3b281d1421a78b588c5fc4182009ce62d8823d95=29?= User-Agent: K-9 Mail for Android In-Reply-To: References: <4858aa49-f102-49fc-90c7-9bd7480306c9@gmail.com> Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Z1k8014WRz3G4Z X-Spamd-Bar: ---- On February 24, 2025 2:52:14 AM EST, Zhenlei Huang wr= ote: > > >> On Feb 24, 2025, at 12:42 PM, Ian FREISLICH = wrote: >>=20 >> Hi >>=20 >> Building a kernel today failed with: >>=20 >> -Werror /usr/src/sys/net/toeplitz=2Ec >> In file included from /usr/src/sys/net/toeplitz=2Ec:29: >> In file included from /usr/src/sys/net/rss_config=2Eh:33: >> /usr/src/sys/netinet/in=2Eh:692:23: error: call to undeclared function = 'htonl'; ISO C99 and later do not support implicit function declarations [-= Werror,-Wimplicit-function-declaration] >> 692 | return (in=2Es_addr =3D=3D htonl(INADDR_BROADCAST) || >> | ^ >> In file included from /usr/src/sys/net/toeplitz=2Ec:32: >> In file included from /usr/src/sys/sys/systm=2Eh:98: >> /usr/src/sys/sys/param=2Eh:343:13: error: conflicting types for 'htonl' >> 343 | __uint32_t htonl(__uint32_t); >> | ^ >> /usr/src/sys/netinet/in=2Eh:692:23: note: previous implicit declaration= is here >> 692 | return (in=2Es_addr =3D=3D htonl(INADDR_BROADCAST) || >>=20 >> I think this is a result of changes to netinet/in=2Eh (3b281d1421a78) w= hich added a static inline function using ntohl() which is not defined in k= ernel use=2E >>=20 >> Ian >>=20 > > >May you please have a try with this patch ? > >``` >diff --git a/sys/netinet/in=2Eh b/sys/netinet/in=2Eh >index 0925e3aa7669=2E=2E4dad4e4fed4d 100644 >--- a/sys/netinet/in=2Eh >+++ b/sys/netinet/in=2Eh >@@ -689,8 +689,8 @@ void in_ifdetach(struct ifnet *); > static inline bool > in_broadcast(struct in_addr in) > { >- return (in=2Es_addr =3D=3D htonl(INADDR_BROADCAST) || >- in=2Es_addr =3D=3D htonl(INADDR_ANY)); >+ return (in=2Es_addr =3D=3D INADDR_BROADCAST || >+ in=2Es_addr =3D=3D INADDR_ANY); > } >``` > >The `htonl` is pointless here, as INADDR_BROADCAST is all 1s, and INADDR_= ANY is all 0s=2E > >Best regards, >Zhenlei > That compiles=2E From nobody Mon Feb 24 14:54:02 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1kJw6SbTz5pH76 for ; Mon, 24 Feb 2025 14:54:08 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0: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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1kJw3637z3MT8; Mon, 24 Feb 2025 14:54:08 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-il1-x132.google.com with SMTP id e9e14a558f8ab-3d1a428471fso35570685ab.2; Mon, 24 Feb 2025 06:54:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740408847; x=1741013647; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=r7cwyS4oEutoo4HnCaUN2vbFfiszrmjmBIXbtAD3GQQ=; b=KjxXXMx2ZsfHVDHUWwoLvkhuX2gOPx8jdyygY3pmCFpiCZY4+0vtRIQOMnuIjKhd02 ENSe/HPXc/ZcznpKtSTfIw+pQT3q4GIyIbAcHc09dZJrJxWDY6HH1edsaLjghDgwUu89 9oehQ3MlzveaWH592quL0X2FTyKHxRNdhH+SlEfKD0b8ddUTpWoPBeZO6YIIWbvoyCqM DWOCHcFRpuln6iPu/86/qZDJWUH5UTtRYFllgchoRFECEkYeXwa/mXo2g2C3fcF2ws1/ eEuHLhBiOMOyt1go/Fb6pdRcaLU1QtNV3fD+e9gpk914umSfkvY8970TCuPHCOdkPwvn syvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740408847; x=1741013647; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=r7cwyS4oEutoo4HnCaUN2vbFfiszrmjmBIXbtAD3GQQ=; b=xJj5Az+tGVOsiMVF1+kofbCZK+/VYoQO9gHaCkbfoeoBQ0wxGgMoyaMbznU9yr5WJb /53fQmCQD7pxQ8GQ9YPHxBnTb1ch/t40da9Wfg33v840wRtseMJXxRmsvXbo6Pub5MTG EWP+OWpZeuMtgbRxDRAUpRmIXuf8m3BRNRXcLq6jtJEbjy1xgzApfcXtmEpg7TQg2Tyn 2YU0fOQUVOwsVFckCi6kYVWW2RCFPxlOntLUOoc6uJcG8amUnizbTgN63WHN7ey+JaBx b9UqoWNFr/VNDrbdDaMeMzr8uc9N4xzsdwsHHwnvBWo2m42s7Xqla0KVT9slfw5cjKxV SvVQ== X-Forwarded-Encrypted: i=1; AJvYcCUDv8m0rbcLD+oj+Qv+JnEDbkId6Bt0qQyRDEaJAJcs09x+OjCfeXHaA0TTi/0vQe4jIP58c41H@freebsd.org, AJvYcCVJmtqtnCoTuvngA28Det3NCk7YO3yLW+WkiZgH4h1vEtlHK3UZ8b/JyIiVf/wgnZ4t44fdFSW1iQ==@freebsd.org X-Gm-Message-State: AOJu0YziWqnTfDgPCZuosGaTZ/+EgX5X+uob7YTroHmpwUTQFQOyL7tB tO4pMxjvyWlB59zOiEWQMJfm4rl9yrAyTWYYjbGOV+i9ng+zJNCw8FTsTA== X-Gm-Gg: ASbGncszJrWvAR8/kuZARKxYICEWtuEDH3g9M32NBHWHVYaAVJRwmxtVTHh/jf3q0qn uzkDLUlZ1RyahwIJqsHE78sVnjn/eqNcl6/JvdVFEx94KkC7FRh4ZBfY0Ye27W2yVR8P8vKXq98 dJYuBMjWKiJHqtNYkDMqNAkp3pRnATpqFQgr1e4mu8jxbJike/B4NyDA+NpUhpkXbnRvt88XmlA zdBEz8bOf9STv5Cg40T4IEUjmQJQR3LZyfspqhQby5O9hU6ALdsdKuC6pC2MxQFRnY5AxXOruNX qWIX+WfNlFj7rqahZIoXT+jflGpv2+ADeupzLo1B X-Google-Smtp-Source: AGHT+IF33XJsYZkOLta/AC6821QqWJf7lDSAHg/owc2QBOA512G9O+pFhcIOE5voOoGEDyYVmQIEdg== X-Received: by 2002:a05:6e02:3f8c:b0:3d0:1fc4:edf0 with SMTP id e9e14a558f8ab-3d2caf18332mr143971435ab.15.1740408846944; Mon, 24 Feb 2025 06:54:06 -0800 (PST) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id e9e14a558f8ab-3d2a82455b8sm31646665ab.57.2025.02.24.06.54.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 Feb 2025 06:54:05 -0800 (PST) Date: Mon, 24 Feb 2025 09:54:02 -0500 From: Mark Johnston To: Zhenlei Huang Cc: Ian FREISLICH , FreeBSD Current , Gleb Smirnoff Subject: Re: buildkernel failure in net/toeplitz.c (commit 3b281d1421a78b588c5fc4182009ce62d8823d95) Message-ID: References: <4858aa49-f102-49fc-90c7-9bd7480306c9@gmail.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Z1kJw3637z3MT8 X-Spamd-Bar: ---- On Mon, Feb 24, 2025 at 03:52:14PM +0800, Zhenlei Huang wrote: > > > > On Feb 24, 2025, at 12:42 PM, Ian FREISLICH wrote: > > > > Hi > > > > Building a kernel today failed with: > > > > -Werror /usr/src/sys/net/toeplitz.c > > In file included from /usr/src/sys/net/toeplitz.c:29: > > In file included from /usr/src/sys/net/rss_config.h:33: > > /usr/src/sys/netinet/in.h:692:23: error: call to undeclared function 'htonl'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration] > > 692 | return (in.s_addr == htonl(INADDR_BROADCAST) || > > | ^ > > In file included from /usr/src/sys/net/toeplitz.c:32: > > In file included from /usr/src/sys/sys/systm.h:98: > > /usr/src/sys/sys/param.h:343:13: error: conflicting types for 'htonl' > > 343 | __uint32_t htonl(__uint32_t); > > | ^ > > /usr/src/sys/netinet/in.h:692:23: note: previous implicit declaration is here > > 692 | return (in.s_addr == htonl(INADDR_BROADCAST) || > > > > I think this is a result of changes to netinet/in.h (3b281d1421a78) which added a static inline function using ntohl() which is not defined in kernel use. > > > > Ian > > > > > May you please have a try with this patch ? > > ``` > diff --git a/sys/netinet/in.h b/sys/netinet/in.h > index 0925e3aa7669..4dad4e4fed4d 100644 > --- a/sys/netinet/in.h > +++ b/sys/netinet/in.h > @@ -689,8 +689,8 @@ void in_ifdetach(struct ifnet *); > static inline bool > in_broadcast(struct in_addr in) > { > - return (in.s_addr == htonl(INADDR_BROADCAST) || > - in.s_addr == htonl(INADDR_ANY)); > + return (in.s_addr == INADDR_BROADCAST || > + in.s_addr == INADDR_ANY); > } > ``` > > The `htonl` is pointless here, as INADDR_BROADCAST is all 1s, and INADDR_ANY is all 0s. See the review: it's formally unneeded, as you say, but I think the conversions should be there in case this function is ever augmented someday. I think this patch would also work: diff --git a/sys/netinet/in.h b/sys/netinet/in.h index fa710af7cd58..e42422341ada 100644 --- a/sys/netinet/in.h +++ b/sys/netinet/in.h @@ -689,8 +689,8 @@ void in_ifdetach(struct ifnet *); static inline bool in_broadcast(struct in_addr in) { - return (in.s_addr == htonl(INADDR_BROADCAST) || - in.s_addr == htonl(INADDR_ANY)); + return (in.s_addr == __htonl(INADDR_BROADCAST) || + in.s_addr == __htonl(INADDR_ANY)); } #define in_hosteq(s, t) ((s).s_addr == (t).s_addr) From nobody Mon Feb 24 16:01:01 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1lp80jMxz5pNk4 for ; Mon, 24 Feb 2025 16:01:04 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Received: from mail-yw1-x1129.google.com (mail-yw1-x1129.google.com [IPv6:2607:f8b0:4864:20::1129]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1lp74tSJz43Bd; Mon, 24 Feb 2025 16:01:03 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-6fbaf4cf2b5so32563097b3.3; Mon, 24 Feb 2025 08:01:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740412863; x=1741017663; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=CPJGdzZidjCH+rNFyB9dpQUjpGWZwm9vpE/w01jUkBA=; b=jnwHtyRIiGA5nkkIctV2QVRyR6rAgmyiHAoVwSxaevvrI8wb+SedbIdJpvPhyR1Q2F neTHzClRyiuyZTr5FZybn+TVdaoisn4OYQ6UZRbA74bJSg04UonvH6L6Io9HA6Z6rrMV 7g2txwe0dXVP3oTVAE8xvf0p06x2N/8//CESHGdkBG98G1BSUGRBBFyVgLvR2S4hrH13 lfiYnDogZMAyNPgkFbyZGkHb3bJqvqDim6HaeHoDqDbE2B0DJULY1HGvRxJrgwl/N54i wb7eOLxetL9JvoJMZFUuhIriQBHMKRz6nF2Tfs10SjtROokuvknnHdvcuxMtA7gr0/Dv 99Jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740412863; x=1741017663; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=CPJGdzZidjCH+rNFyB9dpQUjpGWZwm9vpE/w01jUkBA=; b=LWOHBdcqvikl5H7o6UrwPj64/ucSWvJcIcNnDOCobSeZDaJVyJo5JzPUHXMe4HsIDQ 9y3B92Ni+K1CvThs3gg5AQRz96YJhC4ronJaRYZLjbOm9LDlNxhjx2NkG6EukK3U+G/6 /v/Q7cYYi+M3py8WKjS9g0ep7XMo0CF2zA0M8BAzFTyGcE1MvnOLDmO/3COqDR5cI3No xrkvGdPZm4ADx+6/UPTUnP4OrB+tJ/9B7psOgFHWCt+NK5x00Q68+AK2BdaAsNwCdf3p g0P+jLpTQ7v9Pku/zPVknFrah+tI/dC1IatUbmiWVAw+iZnHuBv66CZD6pbmAApiDs5D eqgw== X-Forwarded-Encrypted: i=1; AJvYcCVP2NnMb/ARqZoA0sC3JVrbYIsQz+FenhVcNLmNjiHmLxAYNDRKu+7A5IsEJyI4gmPsUkD//A==@freebsd.org, AJvYcCVyS4rig+RA6aN6vUvRy8qBuZ8dSAftK7gmaQdp16LNhzdDOac92TFwDs95ucVX4cJjEhUn2IFr@freebsd.org X-Gm-Message-State: AOJu0Ywd1D0+HIyGKwQ9ZoeKBeuiJtNmzdgbYkSyWAV8aYYsDtoORFbl 8Ty0877Wsnflux9E/6HM14rs04reGf3rO+3QeNunL+jya+sDxNw7EAtCN0mS X-Gm-Gg: ASbGncsQfpReEbGCA4RnD7hO/vxXZRKB/s0xTnzFMBMqtVGTw7rDW6IgfMUn4bTZ48f CfCwAXNLHhAj0n3q3Tr6Yt1EjM2eAyttvdaPKpuCla0XDm15jJx3hkBw14fy5kOSjSJ95Y/fSKk JkChZQqtNfb7OjifrxyULcnr0SRHahhBc6M8xKFCVqLs7g83Rzu8rksBW2L/L85Lt08tNIyttoh b8biPSD+so0k42DVB96Ve3cnP2XC0PyB7dZf5+kjEuQiPfrGpojmb1Bni0l0LKLxFATH3UqEKJD 6A72G/MeDZHdHImWTRGZOpNKsZWAj7pCSOUmyTJZxeyzBcMeY1weSs3VfECnXGBOixWv/pxEAyt NyDLg5A== X-Google-Smtp-Source: AGHT+IE0wE/jpW2cQ1Uu3ZMiZg/wVvWLdPSCzaU6SnLWkjUqPOTKHdbVM5JC4T7WQE2DBSCREvbo9w== X-Received: by 2002:a05:690c:61c6:b0:6fb:9474:7b5f with SMTP id 00721157ae682-6fbcc23a926mr117619467b3.14.1740412862321; Mon, 24 Feb 2025 08:01:02 -0800 (PST) Received: from [10.0.0.5] (107-128-20-168.lightspeed.tukrga.sbcglobal.net. [107.128.20.168]) by smtp.gmail.com with ESMTPSA id 00721157ae682-6fbb4e77ad5sm25335577b3.26.2025.02.24.08.01.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 24 Feb 2025 08:01:02 -0800 (PST) Message-ID: <3cbb3d88-0a0d-4063-81df-f2d440d4b163@gmail.com> Date: Mon, 24 Feb 2025 11:01:01 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Thunderbird Daily Subject: Re: buildkernel failure in net/toeplitz.c (commit 3b281d1421a78b588c5fc4182009ce62d8823d95) To: Mark Johnston , Zhenlei Huang Cc: FreeBSD Current , Gleb Smirnoff References: <4858aa49-f102-49fc-90c7-9bd7480306c9@gmail.com> Content-Language: en-US From: Ian FREISLICH In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Z1lp74tSJz43Bd X-Spamd-Bar: ---- On 2025-02-24 09:54, Mark Johnston wrote: > On Mon, Feb 24, 2025 at 03:52:14PM +0800, Zhenlei Huang wrote: >> >> >>> On Feb 24, 2025, at 12:42 PM, Ian FREISLICH wrote: >>> >>> Hi >>> >>> Building a kernel today failed with: >>> >>> -Werror /usr/src/sys/net/toeplitz.c >>> In file included from /usr/src/sys/net/toeplitz.c:29: >>> In file included from /usr/src/sys/net/rss_config.h:33: >>> /usr/src/sys/netinet/in.h:692:23: error: call to undeclared function 'htonl'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration] >>> 692 | return (in.s_addr == htonl(INADDR_BROADCAST) || >>> | ^ >>> In file included from /usr/src/sys/net/toeplitz.c:32: >>> In file included from /usr/src/sys/sys/systm.h:98: >>> /usr/src/sys/sys/param.h:343:13: error: conflicting types for 'htonl' >>> 343 | __uint32_t htonl(__uint32_t); >>> | ^ >>> /usr/src/sys/netinet/in.h:692:23: note: previous implicit declaration is here >>> 692 | return (in.s_addr == htonl(INADDR_BROADCAST) || >>> >>> I think this is a result of changes to netinet/in.h (3b281d1421a78) which added a static inline function using ntohl() which is not defined in kernel use. >>> >>> Ian >>> >> >> >> May you please have a try with this patch ? >> >> ``` >> diff --git a/sys/netinet/in.h b/sys/netinet/in.h >> index 0925e3aa7669..4dad4e4fed4d 100644 >> --- a/sys/netinet/in.h >> +++ b/sys/netinet/in.h >> @@ -689,8 +689,8 @@ void in_ifdetach(struct ifnet *); >> static inline bool >> in_broadcast(struct in_addr in) >> { >> - return (in.s_addr == htonl(INADDR_BROADCAST) || >> - in.s_addr == htonl(INADDR_ANY)); >> + return (in.s_addr == INADDR_BROADCAST || >> + in.s_addr == INADDR_ANY); >> } >> ``` >> >> The `htonl` is pointless here, as INADDR_BROADCAST is all 1s, and INADDR_ANY is all 0s. > > See the review: it's formally unneeded, as you say, but I think the > conversions should be there in case this function is ever augmented > someday. I think this patch would also work: > > diff --git a/sys/netinet/in.h b/sys/netinet/in.h > index fa710af7cd58..e42422341ada 100644 > --- a/sys/netinet/in.h > +++ b/sys/netinet/in.h > @@ -689,8 +689,8 @@ void in_ifdetach(struct ifnet *); > static inline bool > in_broadcast(struct in_addr in) > { > - return (in.s_addr == htonl(INADDR_BROADCAST) || > - in.s_addr == htonl(INADDR_ANY)); > + return (in.s_addr == __htonl(INADDR_BROADCAST) || > + in.s_addr == __htonl(INADDR_ANY)); > } > > #define in_hosteq(s, t) ((s).s_addr == (t).s_addr) I was going to start a bikeshed: I prefer the style of the original because it shows that the author understands the importance of byte order. Perhaps the root issue is that htonl is define in both arpa/inet.h and netinet/in.h with conditional compilation in and out of the kernel. The reason existing uses of htonl work in this header file is that they're #defines and not functions and so they're not compiled unless they're used. Ian From nobody Mon Feb 24 16:19:20 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z1mCH3Xvwz5pQXf for ; Mon, 24 Feb 2025 16:19:23 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z1mCH2sdTz3D2T; Mon, 24 Feb 2025 16:19:23 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740413963; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4VqwvYhphOV30MP3ASlP7TXW0fLl1VH8Z6HTAz+3EZo=; b=nzSZXubTxiUzTj+SxyKsgCyG2dP+nXaYPrs4HxFA2u/sW8FbaQ5x1gbiXgweFzYDWPcNnh jBRY7Oqnbn0RwGOXDpHJQNpiKbqLchphuEMwcdAOOdbkNZyozawZfH9Unaw1vLaT8+THZY 71XhQetncrKDay1ehrnNO9SEletRGQiXCKviTMgi/1WBiP6AGKV2efWV4nqAxrq8twxywt JT1qkWSvdrrAruNNPImpX1D8CpcOLE/QZT14mvt2HP7bPffeN8LOtdmKfAvil0CH7terXB LXeAhtKSwcu2+KNgVfyIc7o+jXqCdknnTKDwvCggXyTvAJBWuv/R1fzXXDnHCw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740413963; a=rsa-sha256; cv=none; b=Bpp3GrgG/duimk/u2yLbEpCYKgG+7lsRzXRx4bVmt7DuxBnKw2ZooN5iYFPYApeXIJZRzr 6MhUdvGKx+FVHptBfothFDemQrJFGXWqzKvqZC+nDMYlLZ2NC+cx5t2zySh05ZGjxVLD5O lkuBN7f63bibwaVm6hwE2TieR/FLaIg0pxbbTmSvvKcV+Aa87/2RlTbVfXlubpRKpAu4Vf zdPKSzedShChWoqFY0J/lwDr8rjTjHnQr8gGWpD9W0iLCIhLUBgesoxkkjqpE+BB+h+P34 lWSZgtxH6YNpqPohkrnCrwY0ed4FypUKPqYvw6OVXsmoWh+1FNTfka1N1N/61g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740413963; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4VqwvYhphOV30MP3ASlP7TXW0fLl1VH8Z6HTAz+3EZo=; b=C0wWpB2hkxczDdxMKAM3+eS/jsU+LifjluiahCNX2Y/QUGGm2v1bmTsbCZ26Mmv5d2zTiL e1eZVP5Ap10/E2Uz4+EQ7ZwU3Ib1Hyqo3ZLoAnQJ30IBk6o3LyK/CF6i0ayQggDJyN/Wgc qDM7oA36OtvZzDN+lBKLIWkxOnIf2t0w/KiaQ7/dOsAMy4iC4VQSrE00MbMRfPkHrAKnTL GmY3kiuDiS8JTi/UqridhTPcjFdlMwaKYWmysm0YZhCNjvmTr39Q9nZC9NLq5Hv1N6g/ox 0avjWNyjIAdbKyQp4vgUi+HvYIaMyuhkWMII5OGQ/SwVZw7i1JBTtF6a1xG0EQ== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Z1mCG5dH4zrJY; Mon, 24 Feb 2025 16:19:22 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Mon, 24 Feb 2025 08:19:20 -0800 From: Gleb Smirnoff To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: February 2025 stabilization week Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Attention, those who participate in the stabweek! On Mon, Feb 24, 2025 at 01:00:12AM -0800, Gleb Smirnoff wrote: T> This is an automated email to inform you that the February 2025 stabilization week T> started with FreeBSD/main at main-n275634-389265e3ca82, which was tagged as T> main-stabweek-2025-Feb. The automatically chosen revision of 389265e3ca82 appeared to be uncompilable. By the way, this is my fault. We want to have a builable revision entering the stabweek, so I decided to shift the tag to the fixing revision. The new revision is: f510c5b2135b Let's start testing of this one. T> Those who want to participate in the stabilization week are encouraged to T> update to the above revision/tag and test their systems. T> T> The tag main-stabweek-2025-Feb has been published at Gleb Smirnoff's github repo. T> To connect this repo as an additional remote you need to run: T> T> git remote add glebius https://github.com/glebius/FreeBSD T> T> Once remote is configured, to checkout the tag run: T> T> git fetch glebius --tags T> git checkout main-stabweek-2025-Feb If you fetch again, you will observe new value for main-stabweek-2025-Feb. T> If you want to use only the official FreeBSD repo, then update to T> the revision: T> T> git pull T> git checkout 389265e3ca82 Should be: git pull git checkout f510c5b2135b -- Gleb Smirnoff From nobody Tue Feb 25 14:42:23 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z2L1G5PSNz5q0fT for ; Tue, 25 Feb 2025 14:42:42 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-19.consmr.mail.gq1.yahoo.com (sonic313-19.consmr.mail.gq1.yahoo.com [98.137.65.82]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z2L1F2N8bz3Gsd for ; Tue, 25 Feb 2025 14:42:41 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=a1XhQdM7; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.65.82 as permitted sender) smtp.mailfrom=marklmi@yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1740494558; bh=LkQavWl7eWqIOVoyGfMm7zSP6An6ENM5a6fM+vyQR/8=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=a1XhQdM7m0Xt9bVe6OQSOj/ZgDOqMTIupMHj9S64JQvFdNXBlhlxh5Yp/6Y7vqMHp3OjGD7PbAUSSkco9ScxelUJwYbLD6M3poy/b9TQy/cYkzdjcBQHdlQjm/ivZGAkkOa2oX1ujgF+evMDzT1Uspy+DFZkD1e1j9lNL8rrHQmgcVBc/4/h/0rbhczKovplvP8/Iq9VW65YICD23sJKiKL9LFZ1a5jf5JSo7MiGdV9QMl9B79n3paJgdsnOkdtvumIq2d4QfeJ12smJlq5ZoNXIE/jC4dz5AN5DU6g0Xke0k4a1rMp98P86GJbTElDCqJ0aeA3cIKYph+IkiNExPw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1740494558; bh=cKVh+dkHfeySLmsZ9IeAo/dteSDitQ36tD9mEbNstR4=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=FsyAWbmIi6VUvZP7CxvEjfmtkf0/Ig+T81DrmAxtgmbcLQhVJDTc6YMoB45l//EAcwQZD+B0Za7pGjfbktGvxdjEoovCaiSeuLY3wXPystW0fuPWM7Vy3aJdiJ4TGAx1VgJWv3lddzco/6damVFnZ6ghXSNKmuPDKZnzhK6AqiGY6Gu1Sa7T8L4xxgaY/rnguLL65macjBeEk3ql0ofVw7h+3PyPudsKvZ4YQ+KnQA1FZpmIPdfMARD7H5S7NEFQCkpskGc8O51aqjrUIUQR21TCgI9TdiZmhvUE9mlqI1Sv+OfbqB7SBMJOJlU65Z/GUGulCKsHAOYFmbKMIvJPkg== X-YMail-OSG: wxPZZGcVM1mg4vrbqW87q19CLE00zXxy_zOUEWPauq3QjtpU63hox1BmsUeJ2wd MuPgi_sow_c8gLa2XbnswMjVNMyjbKhL4IwyztoNQOTAc8dlwESsnlEKq4GO55ONEuZjTf3jZSLO QiACZXkFtMYmVwRH3YVW4QAFVFx.h6oE.ASGWf21CFyLfJRA2rFwipszVEw_a1nv.OBsqk7oaeNT lZAAQ3Tr.e.YQQQzWEYZ0Xsyla5bKxA27l4QkGOdcYFmhRQeQ3OjZjxEYnwbbBamAReE5LRD5Ybj g.yrz4AakO_CwIDpt39f4RpueWcJMUooueUPP_xuyeDUtOrAuXMk25m0i72QQBK1AIUmFLgujWiv 5IBFNs0fXfMD.AbGJGlkUS3MzIynHLb_qQqlAKDz5rdSsCoTznfMGzsE5zMOtSuNnLWBdlnCIX.F uiwAQgFkuzoUQ0gp1uH3sIuxJpic4zy84ABvKsCEcRmY.AJ2srsXaCWmSb9t.GARrFKe3ZYpjbMk JBtQ2_z.WTUDFEkUuCTuS95r7VDPYbd5.EWXFTRKkSd6uh7PJcWkuyUlhIIT.nBY6v6gRLhUgr6i LFLts1hbpDpqfmu2UO.o9Zc.N0ZkTbXzZtT_IGRnLMMcZMjwxyFICRQtNvzjve8V3PhDEYvbooUJ 9JUQeSZPPh3JP4fOrkEv86bbL8l2gBW5jia7K7OepIajdxiLzzljNfXvd6Tl3bIRimb_.TQkBS12 cwXfkEtuTPBiSzN_odCBNl8Ql6ldz8nImwp.tOF870anxm51G_Yy6ovoi56L0xBYh8Zw_bE7arYc 7APE.cfqfG49G0syzMCofec9VC0qDJMKDS7IRT9WZdI3LVRZWDpAwifC_ay2To4a.0_kzlHMvwTZ 9.PwVG5aCwqyMoHQMdVBcnEW3mp0WtQXTqSVSO3Zp7WB65Iq9TgY5I5EV.8rJ07ChArER9udVwj7 eSq47xpw9ifqDT2ZmLu8gu4p8fA6JPZt0DYTG4RR5eBWTsX2AN6q6bXfbAn1BxYhfZeD2T.xjRTw jPVZbierzqJLHC7qHY8.yBom9tu7ct6.Pc2zviyMTJUsv4QJBHIMsBuiIyRzWbaC20iD98Yfxosi CBMAuy0uY82KpjFZrgmpz4N5YegrWX5URTFn0XjdAHAC62jqmdF5agAvvGtsiho5NDy90ZBB2TY_ FUoT8B21OG6NyYOdc9zvuB0_v_mc9aTCsfCmYPloECuVWDwJDMVtsTq.UI.mj9YuhBgyabIyVA3t p.Baj4jXSucn__uQOM3ZrBC5jMSAaccysRp9gOzPYs2LCyBnrohUx2A0aTZPhKlK.glxOCMqix.m oHgNgSdBHKSUguDeKnEk0oIsCz_xOU7T.0YApsgUl9yVkBGXhRuIxiPKdN5aEFvfzgvIaEINxO5Z QL22FVPMmO3gUbMIrY0eDu3T2ROne_i.Vyv2ocH62RnXuz5AQzIqgLnsm0i2YUQhD8KzZIba5adi yyKp9Aa2zT4BFeS2xsygBFcM01McFiHuU_wubpqxbqVDm8rqhpufpJwLNCNTJY8cfmMJItN60G8S tWu94rd3N4_FnYNABZnQvtWd4B2T9HMB9bsAV0BjPt2CVJUJe2OOWt_8GXdGEnEvnNDj42b4kjHu wgI4vbbopyH8D7rKVTzPlOb2RUMQqhd3szCRNo3Be717HkvJjtm6sX6yFpuZwsSW9YUa3tyJvHAI oT56FAuE17hL.5t2dpd0.FbgohOtXXTjSXrBCMYWwtXpKgAdXz1OEm8uYPeKnRHRKQMrdRgE4ZFu gJ4CJtjG65D2jnO9qtyOUEj1SeROuGkw._JYi75OyiaVfg.L5GTG1jwxp7rcXTiSOy31Ddqyp8Le xgZkKY7mi8FS8u60Dz1tKUWBDsTmF1PyV7ICkX1uNnu.n70D_ZxYC3S2WeddEKjkWIUrcT29CxSI uBYchpjKdbojEy1X2ZRDycHcwW3QNkETwLm3Y3Sv40ktpbYvq7IBIPHobIP231wISPmDppcf4t1c QLmvLXesnJV5Nn7fWLcaxts54somuzhFfPfe5w7S8HJzLSOsINEnyPfxU5qUn31MhBJowoFXbmWP NXBtmfL.Krs3II_TL1q1NzJ7SyTanaaq4Bcgpnmq0lPMN8MFklUO.6RkOV0Tanaj2hJ4M_99K_FH nNOv7V9g_n5EhGVagD8nboMQvn99RxMxY1TbN99UqGkS6RM.2gMjH3mmHgOz6H9kW6uDjpxSR95p zIgARqUCmrP3xt5tkqIJ2P3IjASWHm9lNuSyjxwnq0k30syQWsftKCgDT.ISY X-Sonic-MF: X-Sonic-ID: f30cffcf-f33c-41fd-914f-905774cf2346 Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Tue, 25 Feb 2025 14:42:38 +0000 Received: by hermes--production-gq1-5dd4b47f46-ps69l (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID fb8030e4a9e1f03cb5a387f06f9b6906; Tue, 25 Feb 2025 14:42:33 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\)) Subject: aarch64 FreeBSD under Parallels on macOS on reboot after crash got: softdep_setup_inomapdep: dependency 0xffffa000c5d52a80 for newinode already exists Message-Id: <2B1D84FB-B01A-4BA1-955D-D9F97DD67C13@yahoo.com> Date: Tue, 25 Feb 2025 06:42:23 -0800 To: FreeBSD Current X-Mailer: Apple Mail (2.3826.400.131.1.6) References: <2B1D84FB-B01A-4BA1-955D-D9F97DD67C13.ref@yahoo.com> X-Spamd-Result: default: False [1.07 / 15.00]; RBL_SENDERSCORE_REPUT_9(-1.00)[98.137.65.82:from]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_SPAM_SHORT(0.87)[0.867]; NEURAL_SPAM_MEDIUM(0.70)[0.703]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_FROM(0.00)[yahoo.com]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RCVD_TLS_LAST(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.82:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.82:from]; DKIM_TRACE(0.00)[yahoo.com:+]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4Z2L1F2N8bz3Gsd X-Spamd-Bar: + Starting devd. panic: softdep_setup_inomapdep: dependency 0xffffa000c5d52a80 for = newinode already exists cpuid =3D 2 time =3D 1740518496 KDB: stack backtrace: db_trace_self() at db_trace_self db_trace_self_wrapper() at db_trace_self_wrapper+0x38 vpanic() at vpanic+0x1a8 panic() at panic+0x48 softdep_setup_inomapdep() at softdep_setup_inomapdep+0x28c ffs_nodealloccg() at ffs_nodealloccg+0x5c8 ffs_valloc() at ffs_valloc+0x3ac ufs_makeinode() at ufs_makeinode+0xd4 ufs_create() at ufs_create+0x3c VOP_CREATE_APV() at VOP_CREATE_APV+0x34 uipc_bindat() at uipc_bindat+0x3e0 sobind() at sobind+0x2c kern_bindat() at kern_bindat+0xc4 sys_bind() at sys_bind+0x98 do_el0_sync() at do_el0_sync+0x638 handle_el0_sync() at handle_el0_sync+0x4c --- exception, esr 0x56000000 KDB: enter: panic For reference: # uname -apKU FreeBSD aarch64-main-pbase 15.0-CURRENT FreeBSD 15.0-CURRENT #2 = main-n275290-9ef38a01aea8-dirty: Tue Feb 18 19:42:12 PST 2025 = root@aarch64-main-pbase:/usr/obj/BUILDs/main-CA76-nodbg-clang/usr/main-src= /arm64.aarch64/sys/GENERIC-NODBG-CA76 arm64 aarch64 1500031 1500031 So a personal build, not an official one. =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Tue Feb 25 18:08:53 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z2QbD6RRZz5qJhx for ; Tue, 25 Feb 2025 18:08:56 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z2QbD5bL9z3GZF; Tue, 25 Feb 2025 18:08:56 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740506936; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7frMCM6cwvdiv6hyonV0ofQXqyCZ/tynYUWtzGUn7lk=; b=LoU5GhctTcic3IaV0PWnd0MDlWeCVSyF5S6HV6utUdWf6ZV/LIBLHId6QeOOm7tSklJHaW Ns7ynY3BdzRNIR5Hc14lMgfUmv+N8KgvKeX+1UgSdUoQcXgLKPlPXcEtVev13r9jbOJ6V8 FlGiPvKbc1c2AnFFSjGboj2hGkCxrmvo3hEzKQzDbSqQCnMhS8xa3e91JLIRL6itKu8wry wzNylkRo9g+4Y/Gr5j4DlqbQ8FcuzayOocaszcCRPAhJeXirj5MTDZmP8Xlk1LMPkLrQ03 QgyAIIDM7IYkZdaiUwxcHUhYvOQBbdcatRWHlxzToomYzZr3nwlsrrgY8VgDQw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740506936; a=rsa-sha256; cv=none; b=AgBjy2En8cGWPV8kKsfJ8q0TSJDvtK7akfQWDLmmHyM9TRzRFWmMcW7kfrqQrROyvDf4qK ILLu7SVpokM6CMuOEFUf7Sg1vvGsaV8gwqwTwYPVuUF0lFRN6PJDDWFOcVApbuCHkBFBBi UzRoxO4smFgLxUaRABCJkW4u158P7avSssEC1ZnNk9e1RSoFs8HgDSTlOapj5gLc6cIuF1 z5gnue3YLPZA+WE12j/85fkAVu670rQBWETMAPh+7yt+S1PlYI6lXoufrsETGehyfUFNup IDW3YuhbpyFyIg2Ynt5xGJIPeo+46odcs4W48DVFOQ7pjgx9h0Dz19mAdAnYlQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740506936; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7frMCM6cwvdiv6hyonV0ofQXqyCZ/tynYUWtzGUn7lk=; b=ehnCG9hgLToYlzj/d1pCfZUPgzZgdme+zg/z08ctcO7SxBaGSt6Ern20nJ0B10y1gMIx/n 4F7V9HiBcaQUMBXcKXBryrlenqTzTUwe0A5AGKIv7EhQgNMTS68Xqn44BAenoJO18RYifH WTbdvctsnwLLk2jkpbCSJeWeysS06KKRpGJ6wZDlHjyoRepG4UqvIrlecQ+rO9JyfN5ckZ 6SLXeRp9kj78mRVbvpZ72WR8GR5DWdUGsWZhklNoqY64eLbZaYGVTiomi6Vwj1Gc3Vrohx hWuOReq7KN1PeX+j42wFBpsnX9sRFt7gcGIGy9ZY/b0REsFy3+L1HpojS6yX+Q== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Z2QbD2NG2z9t8; Tue, 25 Feb 2025 18:08:56 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Tue, 25 Feb 2025 10:08:53 -0800 From: Gleb Smirnoff To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: February 2025 stabilization week Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="X/r7qoxzRa2pY8Y+" Content-Disposition: inline In-Reply-To: --X/r7qoxzRa2pY8Y+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 24, 2025 at 08:19:20AM -0800, Gleb Smirnoff wrote: T> On Mon, Feb 24, 2025 at 01:00:12AM -0800, Gleb Smirnoff wrote: T> T> This is an automated email to inform you that the February 2025 stabi= lization week T> T> started with FreeBSD/main at main-n275634-389265e3ca82, which was tag= ged as T> T> main-stabweek-2025-Feb. T>=20 T> The automatically chosen revision of 389265e3ca82 appeared to be uncompi= lable. T> By the way, this is my fault. We want to have a builable revision enter= ing T> the stabweek, so I decided to shift the tag to the fixing revision. T>=20 T> The new revision is: f510c5b2135b T>=20 T> Let's start testing of this one. Testing at Netflix did not discover any stability neither performance regre= ssions. Thanks to David dhw@ and Olivier ocochard@! My personal experience with desktop, laptop and home router is also positiv= e. This email thread didn't receive any regression reports. None of the recent bug reports look like a recent regression. Thus, declaring the stabweek closed. The f510c5b2135b proved to be a good one without any cherry-picks. --=20 Gleb Smirnoff --X/r7qoxzRa2pY8Y+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQT+rgtjiRzq3LbQ3Nn+/1jAXQXMIgUCZ74HGwAKCRD+/1jAXQXM Iup0AQCV+Wqr7hdPEqfqrQcV7PSNAGLHnwZjVWK9p7Ij08lpugEAjTdFz8mFygqK tqJ7JaJiBl63hOaaBkgUWfsrHMCjzgY= =4XZy -----END PGP SIGNATURE----- --X/r7qoxzRa2pY8Y+-- From nobody Wed Feb 26 15:20:47 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z2yqK1h1xz5qHgd for ; Wed, 26 Feb 2025 15:21:17 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:313::1:5]) (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 ECDSA (prime256v1) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z2yqH29Fbz3SnF for ; Wed, 26 Feb 2025 15:21:15 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=zyhVSmqY; dmarc=pass (policy=quarantine) header.from=leidinger.net; spf=pass (mx1.freebsd.org: domain of Alexander@Leidinger.net designates 2a00:1828:2000:313::1:5 as permitted sender) smtp.mailfrom=Alexander@Leidinger.net List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1740583266; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=xtv+nrnG3nUspxsIB+JbBSBlQghtaUSlvQvh1BOzSB4=; b=zyhVSmqYvqBSvcyWbnNBOOgjXKAdkddVQxsq2Q3t5OkCvCq5UxRsOsYH/j3pVaX5q2SQfX qWjDmO6xv6XYoDmG1ivUcucUtQAGtB6JeC0Jj23F7NgFJcHS55SoAZopceRlo5vWyw0j5L AcIiabohL25MqHtgGu/ko9zqdIZleZ8AIcpU7K1icYr6rq/Ow8F7eLEbECvyD+Bs5DMATV W5+u6oZNF2Lb9sqykPaK2qCScERqwatWwR4lt1/w2FH2d4Apsu/S2zI4SePRtRYkyO5Fpe X+VndibZrWMEHgfq6cVNUGmKU18hETbp0DMD+hj23f4KiwkzkLkR+oV+4Sx83g== Date: Wed, 26 Feb 2025 16:20:47 +0100 From: Alexander Leidinger To: Current FreeBSD Subject: Strange file access issue in a recent -current (but not with the previous BE) Message-ID: <5ebbe12dc6cb4e3fc00f0a07c03856e4@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_306013e8d9b70e8b0dec959caad46006"; micalg=pgp-sha256 X-Spamd-Result: default: False [-3.09 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_SPAM_LONG(0.94)[0.937]; NEURAL_HAM_SHORT(-0.77)[-0.773]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_MEDIUM(-0.16)[-0.155]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:34240, ipnet:2a00:1828::/32, country:DE]; HAS_ORG_HEADER(0.00)[]; DKIM_TRACE(0.00)[leidinger.net:+]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; HAS_ATTACHMENT(0.00)[] X-Rspamd-Queue-Id: 4Z2yqH29Fbz3SnF X-Spamd-Bar: --- This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_306013e8d9b70e8b0dec959caad46006 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi, the working system is from 2025-01-25-141603, the non working system is from 2025-02-21-115311. I'm not sure what the issue is exactly. I have traced down the change of behavior to ---snip--- if not LIBC.setfstab(fstab_file_path.encode()): ---snip--- In the working case LIBC.setfstab returns true (so with the not it doesn't take this branch), and in the non-working case it returns false (so with the not it takes this branch). Is someone aware of a change in this area? Searching for it (https://cgit.freebsd.org/src/log/?qt=grep&q=setfstab) only brings the initial commit. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_306013e8d9b70e8b0dec959caad46006 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAme/MV8ACgkQEg2wmwP4 2Ibo0w/8D70S8f79rLskrBhyK1kgxiw3gIFUW5K7w9uuXN6iaqDADdTYmysgFaZ9 0GCmbP/nupYN8a8BqHcEVmSJBpqSp388COQWP/m5wMU2OCz/Qsi6hYZeAFgaKqzP FJFNJY1orCzCNO8u9NRLiqxqIJDCTsjS1OfGJqq3hL8MlYoFMwB3j53agdtxcxvB LiAjjlGkoom6iT4YDCfRHdzIaZwRclvEy8TCiQUoA7RfLypPrCYLJPtYj6VdRcYl olh56tLIIy3tKCDVfObZb3Ndlqk9wH+Ez9dpjWqSl4gvI5hqQY4QCh/E9bYWzw+B fdWz+Qu07oO2BvSdAa3er5K9IH2UeaJnRqyDY8upWKYnjeKrkza532kJMHIRLmgB ecO4MJ24s0zCzshOWNpw3nSeG7BwnsBO9jX7Io2ql4VHhY44mtzjcGUFgh2wjnEM 39c86CrAvVQ+zhEytggMZQt/v1gX9aahp8o6pSzD/yP5iVqkmc2cuHh72hBPsPBt dHf45DYgN0bchDGG40SSH8ftm7uU1v69uq37vhaPmm6UnGUFR8iEs00TVCn6IGqB rWM32zzI+CF0rTOAoG3/EPUA5jc0DzbHQ8chlNQddv34Tiz7UZV9/0VmMCZaSrc3 ePUL6Fs0cULeB7hOOoBrFd0J1JJ6WKqtLmyi0s75PAF7miDcNQE= =bQzp -----END PGP SIGNATURE----- --=_306013e8d9b70e8b0dec959caad46006-- From nobody Wed Feb 26 16:22:39 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z30B73vvgz5qN7h for ; Wed, 26 Feb 2025 16:22:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z30B73MD1z3xRr for ; Wed, 26 Feb 2025 16:22:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740586959; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bFjp8hilUx7tQL/81g2djBxGZOABCcykqk1LbXTfoYw=; b=wPvzavJVA74s4RFE6t/tqtRWiTzE0Gzac13L295HSFlnovt1ibIMVUmP2mGfa0g5O8L2Nc UkJRqozIKMfISXZg0ry+M5ILVqEU2EV9ZDm5m5wDeagnU1jyS39VU6bAmdTHz8kro1JGWA 4Ie/uZh3WgYaw5xuKkcI0bph4BmIqjgz564HDC6MZTV3NEvISulgbxXLINWmXGDJm0wHUU DLTkzucIkWFNJQmsrhXwbdT38mQedjXAercQr91B93oIWgp6vHrbFPOQ+4CbNey4kezV/1 Cz+yU4YGELEXSTp0Zc9suTHdgsxaipk5ILviAHfm2U59wWS8E8b1Y3GOi7NOqw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740586959; a=rsa-sha256; cv=none; b=tPBhXxr1Fr+yUQ6hzIuRYqtOxlg33AH0JIcJ5nM1cEGjSi2BmFdJOaxF8fdQxK51qD7M3I f2L9v+2V5hfa1GsexZAby9H6J7yVwlVM3mu5PPh0jtCaJgo9PpqWTJsCNzmI8P1irbmv9e 1NiidujCkFdpc+sTC6d96Eit3VvQATdWvHxCeCkeRyTKZYW32WEtdBmHkS5DRtxTent9mt T0pakBM7J72lrleK/5aHCBJD+sdzpATBtmJlAqnlhzb8yaQkNGdsPxuym4vszkckyW4q+S EaxbTTd4kLkSpORmV9usEp/PmBZzATVn9P31v41wcyRpySp7ErMgptiF4QrRXw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740586959; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bFjp8hilUx7tQL/81g2djBxGZOABCcykqk1LbXTfoYw=; b=KEh32NA08bxxCPYTsJriiJP4qYNiksUHy2OutcmLEoKLW0ov8xe9fYwqgrvTAzCX9xHye5 nSepHbZwC4jCfI9hJlrF1GTmEwIkDm8VoqMMK7v6f23d0nnpAkz53P4YbMeekxCRrn/TL8 8AtdmEU24s6eMjMOzbqGZRhnjK8GemHp+TfdVS/GdSTwOXLRIzqTzX7HQsT7VL1AoJdFjs wf8GxjgmFp6OJoF+QNlgbu0FwRR8upeV3X3kMSvAKXIUMV5+/lWOg1F+6BsWg1Ls3JtQ4e JlxXfWchOJWoJ/z731l8mFCHaUOLH673v9immDD1AjB79LHkncxriKcT6WSLqQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z30B72vdBz1JpL for ; Wed, 26 Feb 2025 16:22:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51QGMdP2095446 for ; Wed, 26 Feb 2025 16:22:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51QGMdC2095445 for current@FreeBSD.org; Wed, 26 Feb 2025 16:22:39 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 285044] legacy BIOS loader: lua logos gfx logos on 15-CURRENT are broken Date: Wed, 26 Feb 2025 16:22:39 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zarychtam@plan-b.pwste.edu.pl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285044 Marek Zarychta changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |current@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Wed Feb 26 16:23:17 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z30Bs5lfdz5qNXw for ; Wed, 26 Feb 2025 16:23:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z30Bs4T1hz40ML for ; Wed, 26 Feb 2025 16:23:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740586997; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/4lKoBrwsRFPJH/L1TTd2DXel+m4r4iIH4mgRayP2IE=; b=LCqNuM2M/Yq2i6lInYZ7DMHr/4tRxgo4fAdKIe3UI5AqKPa5XvBpAzbpt0CnTIypKnbYDP V6vyLFhT0qd8OKToVMfy0Y+S1oKGCa4SG1pjXf7E5mhDaOSqAWtoXD5LRmd6ojfNA7gEwm B64CkYGjyLos1fGYxQANyn5eya1wJwCuOWhyq9ovHuKo4QP5RDKw2eCs7OaVEcVNg5/gfW xYRQV0GndYqkHrxLhaWB2ziqGLFY/zue4Ch6AF6FkENUyTw3Wrqbcfh21u9KlIPJIckZmi f1DQPlWCSf1C23zxx+XsHDVClL7zJNKMmdeZXO7sWCSf4uwpgHhoXlbMqWY74A== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740586997; a=rsa-sha256; cv=none; b=mqq+etA/nVT2RmpHHpWVhpVNRBZYbQeDNYQzEQw5Hk9YfrUmXsRQcbjuIQUhyIkMYfo11V z8XP0vMoD0E+vGPvXhS7Qs9K8Io5JmL59rdtjFc3XvJKDE5iI4dpHpyZvlARRCxJdxKmhr jTWA4XHWUTGzE6m6dWLIK/LF4k/xCBsVe9+MSmyw1i81v2R744/H9rOozkeNSQxNUxAcup Reu1ylB7CoI6C3N1+GzujA+0oLg7lbPWaVvX+NT+Pow7ztMDhWcbI2hIwGTC7F3DwVxA5u pJFhAudT25f7w8JhXGmi3lt0bVOU5En71IIx0FkkA2P+f89vSO7HkZ9GX8CxxA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740586997; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/4lKoBrwsRFPJH/L1TTd2DXel+m4r4iIH4mgRayP2IE=; b=ilZ8K+5o1FIAW12JftPazFp6zr9S1t8psmyr2+QK8EYRaeayhB3q/42zammDq4G9hVMO1s fpEZN+taoq9BLhtfPZ5X1wqWbD6ldYBuUdcbTZ2uL9kWmLjEFM1Hh7omt9iT8SCmz9/96f XU/v3nA0vsv0YLEuKfq7aY7AwOQzDji7GeENztegCoHOgaxS3Wj8NkqdToLvl8KQVd9N/G Z+C9+8yUD7U+ZySureAKWxPi7sH2Ecj/Qlgsl10cOCr9mR9Wp+Ll3IgUdcMfOV6AFp+KLJ kbQkF8kU4PBdseBzfbxe12CwsOn8Yi/xl+5Swb2xKdmUm9T6kzvyHLG+CcGfGw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z30Bs44npz1JWV for ; Wed, 26 Feb 2025 16:23:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51QGNHFZ096050 for ; Wed, 26 Feb 2025 16:23:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51QGNHwj096049 for current@FreeBSD.org; Wed, 26 Feb 2025 16:23:17 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken Date: Wed, 26 Feb 2025 16:23:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zarychtam@plan-b.pwste.edu.pl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285044 Marek Zarychta changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|legacy BIOS loader: lua |legacy BIOS loader: lua gfx |logos gfx logos on |logos on 15-CURRENT are |15-CURRENT are broken |broken --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Wed Feb 26 16:43:06 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z30dk4PWVz52ffd for ; Wed, 26 Feb 2025 16:43:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z30dk2K5jz4676 for ; Wed, 26 Feb 2025 16:43:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740588186; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Yno5B/e14YQeJxb57K12in8qbf9+0Zzy22z8sO9W4d4=; b=s+IAVqS0xqtQ4SeaRbbvuYyPkjPheaq3QCeU1QtyvXLbyZCv5R/dCjmsouCQmwUUd8T5Ax ImpFsCXQvgy50OuOjAL+023DYkGu2OZKYD/LJVyuSaV8GPZBqDBm78ss4VxGnscb3yeSkb c2mf2niIVw2MMX+yleOApuf9ZwR9OEcOLBdacz63pxkNeKnFUdrbi+QCbjPbPYfiwGhtJt 6+3T79GWr5KrSLjoy2pH2JABxnDjb/ioT4/W0Bfciwm3w9DyGyCmTcCqPQU/923l6ZIDPf zqd9lBoDxeRk5BHRaRMEE35PySlqA2Bs6gvK4kquLwPbQv91NjdGbLpk9MSABA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740588186; a=rsa-sha256; cv=none; b=v/8qQlT6fI/lPt46I1W2ubuuXFnvPSLGCJ2Ky0wwJkqio/nhlICR7lhkFi9NpLzpFyVLai QJhRhcVDsFtYM61TyagAPLDpXI0L1zMmpkzNhLkPYgygOUwVOfUMiECbx+u6kC2X6lduDR K/ptbyJJ3cEB9sLWSf775Uzbw3PZBD52bMUb3OTErMFhwzH5EYJr0CjusctOII3F3Ooo3r qFtk/3VblnX2fQwMu8Iy1wQktz1wC+uy86seqmbG2DeCoZebLnrSdblSD0T2UzYAxDjUna 4lUnCsNO46GbmlJUXq7jl0mF3s8fbje2YEIcbJYKPCSMz6SqR+lt5wxRwVMoxA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740588186; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Yno5B/e14YQeJxb57K12in8qbf9+0Zzy22z8sO9W4d4=; b=YSUOYxqLpRLdU5x1hIZdbgAbpDTeHoEwGVLex+xzcXNcWfaDLlXWmobIVEtNySIdlAt2VP 5A1JGZ3T8OekQSp0OnTXMW9jJ1q8dEwihroLzcdpP5Qe6+Uvgt+6Ge9UtVgfmwy7GkmUU8 zqMxvBsBT6hrFPOOlut0W1jSf91QaBTiVRzmtirIpC/JLuhXtgzmjgQi8ohQO9GthFG8y7 IwULRAapqaXswPuZr67aOVGWT/KQ23iwEAC/M7as62N3jPtgwGYVMlrMTEfrtb7zCOwrcY paGFzFoWeYU1t0w+tMciyjy1bLN9yx3TGFbAtpbCkdQUkdzObiSFSsvBfr9Ffg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z30dk1n6Wz1Jqm for ; Wed, 26 Feb 2025 16:43:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51QGh6lc032882 for ; Wed, 26 Feb 2025 16:43:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51QGh6Zd032881 for current@FreeBSD.org; Wed, 26 Feb 2025 16:43:06 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken Date: Wed, 26 Feb 2025 16:43:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: imp@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285044 Warner Losh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org, | |manu@freebsd.org --- Comment #3 from Warner Losh --- Just to confirm: this problem --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Wed Feb 26 16:44:25 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z30gH0KCMz52fZK for ; Wed, 26 Feb 2025 16:44:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z30gG0nmWz49X7 for ; Wed, 26 Feb 2025 16:44:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740588266; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9DFkll1dzeXazBqTjQSaX8IoHqNtEvdExu2S2Zr2IMY=; b=VopuTNsQ1+LR1WtW6eAjDwcqGcTnAgWbPKOWUVCiTyXPmj6RxqzIfuzX/rEPIggeCuBpRt WeacgcSOAOX9RybzyjxOAKA8miTpNUptbOzPzdOv12Jf6AeM/FXhOOYDFAGnjrQKxWcBNE kifSlb+YXMrJUTtH0yDOd0BL6S+T/K8OIUBcxlMD+LZ7du9us2Tb8FJHaOS4Pycy+VWKHR 5yv49EbZkgiMNf0HPfqQbhbc3mExcTmouGbYj1Tl9KFXu5Znh7h6uxg64gl9sqaJ6lps/s SnINm/ZEkOx+NCTEvPhcy4JczHRB2HlYjtUwLtnW7Mkc8CQim0EnFFxM533jig== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740588266; a=rsa-sha256; cv=none; b=lyOszlLiiPY3otZyg+LczCFloBDME/qb1DmIqDxjvpdJosKvJHhxVOcqhDPZNEl/NoG64h ycUxwNcKdokTBj0Vg/ik8reua5pWky/0/htWIOWOsW+7qten81MSYSfN8eJdNuUeMGPABb jJto6Q+VQ2Nwi13WEzYw++k8NjuRuq/MUyr0JYBeCjNv+DRMjhva2cAY+25+NAvHk4InPb 9n6esSz+GjfqC+De1ILWp5enWZ51OloFAOwPtWCqOJ3iaOIY/jyw0gZQd0iUrDYkgwxl55 kWiBcthFauiR1wgmsvYrUZnCU/bOAPTQwcWy0Fms8FhkP0S/yZ+06pJFqcbmRw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740588266; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9DFkll1dzeXazBqTjQSaX8IoHqNtEvdExu2S2Zr2IMY=; b=uMLyShtazewyBcyIvIlUTtng5AoaCvctDCdsIwHN0uNA38/pKd+d8AjvDF36HcY0XoBdZ2 DoG9VOu7U6H6tcrpWjQDUCYU0Xs9DGzGQ/mNL9Ua80snxDel4nTuCmpCOMf7rdTx3wbZ3K p9B0lxShN+tx/w4+QGhuLE18X7gEUKTPeOh4SHjNoWNWB1TflwLntb4WimdjVcYEcHkz9P 08OD8qC6tttFrrE5sObnHDANna/EVJFzfORFQkNO53w0e8GhjHiWaKmXsq3kmZ7A5jCQq3 kj70LRNFQYs5/WdyeDdAvdYZO1JA68kGXMz215jUwoC3ws3em//nQjfxlmXNsg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z30gG0PQXz1KHw for ; Wed, 26 Feb 2025 16:44:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51QGiP2b034088 for ; Wed, 26 Feb 2025 16:44:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51QGiPUN034087 for current@FreeBSD.org; Wed, 26 Feb 2025 16:44:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken Date: Wed, 26 Feb 2025 16:44:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: imp@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285044 --- Comment #4 from Warner Losh --- So this problem is with a BIOS loader, that's been compiled to enable graph= ics, correct? But the problems aren't present for the text version? cc'd manu since he made the alleged breaking changes. --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Wed Feb 26 16:49:47 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z30nS24mMz52frN for ; Wed, 26 Feb 2025 16:49:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z30nR4hMzz3FYy for ; Wed, 26 Feb 2025 16:49:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740588587; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iyz/zA/Gy87gx9iDyBp5mzdNUEk5c01us4GktOpuWH8=; b=KNv6mN0PdrQNhn9K8h2fuUde8pjhVlL4aIV0a1o2AjrrsM/BDbmOf0wIzU4/BbpwF0Lf5/ 6cBUzj5SEZkXV6mRQObzsyBL4uAOB9AfS4IpnEh4/RiH4OYkIWDiLfisQ5rxbF76oSfhOc /UT9Q+UqzlMesHh6GVGpJKgaFoJiVTe+tp2DC3lQyxw+n1Gx82FZeqaqNOxMxaqIA1UPEm WeSPpcY9JzbEdigoK4oQkFREZ7mvuO9m2mxZbn1p7bG2OQEHJQIMwWkScVTqZtOwONMsg/ eL1Y4HOfam/vgLUwAirM4WaNQOAhU4Ln7dfcpTwN1rg3Ga+zKGGcgFQ5OCzlvw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740588587; a=rsa-sha256; cv=none; b=QCN+lhJtzjKeBJTKvuBTUnYz7Sv2yKXJf/bTwMLSoTRK/KduW3tu8Q81Pbwomd2geYX/xC TSXMkgA37wHtH19jhHdNL7Ua8o/qoeZFQ9qOvsVcANFIdUiNpsUyDTVDiDbEd9kfkOfyf2 tCjl+zksDb/EZfbyXWfLtHKe7/HPNuar21xhcolubt9pMYJujS+DnF/SgAatxt5B08PhfH Kkip9sc540GxdRO7rYe/wa7TrXmS31CEMz8rgQ+eodTGveB48oBdytBm05b+d4o1kcpW0C niq0DWPuXE9SAu+s4pTA3rr3g7WQa9IuquwkAB0QLJRxomKmX3Vkbt17w8nwvA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740588587; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iyz/zA/Gy87gx9iDyBp5mzdNUEk5c01us4GktOpuWH8=; b=K8xQUx/Br4+PmXRRPLbW5h2SFomnFX+dJSDv8zB3Eokdx0gckmaKaofn1txB6F8925jLB8 Cf5DbcDu2N9H3SYENPTVHae8fiGS/TtJdYRzHHXwUxE+sXxi6MOeNzgSV/sXnXPPGODwX9 uVClmtUO29Ur99Hi/NI3kDrfnjuRgoOO1TYA+dQFEKvm4xdvEDqDPmqyA2DaByE7WPauXu QEbHXpduJhQfUbIWCGFIJXqfP0pFHQtETU5qj0qThlxQAkj4EwDhKpz0XulQOBn24052lo 9A4SrdG26xXU6qqkM9D9y8gqB3E6CVo9g9KdnkwtdrxGYyxwrt2kXeMms55Edg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z30nR3llPz1KLX for ; Wed, 26 Feb 2025 16:49:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51QGnlhu039205 for ; Wed, 26 Feb 2025 16:49:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51QGnlBT039204 for current@FreeBSD.org; Wed, 26 Feb 2025 16:49:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken Date: Wed, 26 Feb 2025 16:49:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zarychtam@plan-b.pwste.edu.pl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285044 --- Comment #5 from Marek Zarychta --- (In reply to Warner Losh from comment #4) I am booting this machine from BIOS and exceptionally it's drawing beastie,= so an error in the text version logo is reported here. --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Wed Feb 26 23:25:34 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z39ZC354lz5p9Db for ; Wed, 26 Feb 2025 23:25:39 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z39ZC298Zz3Xnx; Wed, 26 Feb 2025 23:25:39 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740612339; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=DePFCXYFCY9oxrLrarigEeHGGPGjX3yjuzgr32wGL1c=; b=AnHukl9XYF5VzAzElKyUKoxrd6Y1aNDZjaLX0PNDzhSFXSqCH3El8gMtBm7O31ongeTsJh mf6sJQGLbVGXGEs4FZQlwn8HB4/PMp3LtXuVzZwOeo9QEPg/cCcvArzuo6UNdsnlbYzA90 kL86rOo+5omYG3iPQxxr1ajHHwfblkDHa64n9iHexki3ShDqEQJgQeFzJvDk/oHxdd+Fga ZwrFDTbuQrGPjrBwQf3QdRFtGUMsva+OEtgKd1qfy2n6wKvjXL39ZX/dXzNb+OgLjb4wlf tILJjPwCxKIQfafHQ6mRayZ2mN6Ig06OGdXwaTSNjwe/ehGrwibduMk+hpHNyw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740612339; a=rsa-sha256; cv=none; b=A5/TFEdKiH9R+SYiAJ8F13F5xwhKCvgbIuet6uNxDEWUenS5hLt8TNRpwRHbTmsImL/EXn mTO20cVsA+RonwtIq9QooSeBW8hBiPc0hSy9BTdBOcFxQz1y7KgMDmBCid8ECgAkGWTNXR dF9RIK5rWzo9oH7t2nU8wcTIFiRZgaBrbmU9L8Gonh2PSvwx4l6UnlCWeq+1XoR8iRXoqd EMm95OeqYcu4YpWQA7gpqpZj40/5p0JUtyn5Im7mMqndRrO1gZdYZSNccwmhJfFVEz2TSB 5zSSkhGHdQySU3vjI8KYMEEHzDh/pfSz75g+kSzsOPGQi0haqMJGbVn0P9pULQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740612339; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=DePFCXYFCY9oxrLrarigEeHGGPGjX3yjuzgr32wGL1c=; b=UapUNK2suLUCtTIFxuCPckwtOVWVcAGH11vGS3UtUcydB58y4XVrzCfrAP4MorzXF93Xb7 I8ziayIykInG99/+tEn5aYn/PYIH/PMp5gKW1RSxRf797kwKRdYMNNXNXG0402n5Qa7WIc zuT2Bc8+i2+Nmh7opQm7Q+niWff8FRPre4tllLhoundBoqNhU6aFFYOQxr54lzL3s9bblU KZupa8nLqqWa9l/KL/xcf/kz/Ky+6nuxTNxHJbBcLKdzzAPmTYG8WQ6p9V20qlCPXZKS8M UhCvHcO5xwkWspk/1kZhH5gfGjonZzyzJAGZR3ZlJQC3Du5+L8lE5hcAUw58OA== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Z39Z921pgz15yY; Wed, 26 Feb 2025 23:25:37 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Wed, 26 Feb 2025 15:25:34 -0800 From: Gleb Smirnoff To: Cy Schubert , Rick Macklem , Chris Cc: Lars Tunkrans , FreeBSD CURRENT , Toomas Soome , Steve Rikli Subject: Re: RFC: mount_nfs failure due to dns not running yet Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4f09507d6ddba4979a418e7f30f1f94a@h8spam.org> <20250223205311.7569a16a@slippy> Hi guys, replying to all, asnwering Chris and Cy emails that I did not reply earlier. I trimmed quoting, but of course I've read your emails! Point 1. Please let's forget about 'late' option and any other rc(8) hints and magic. As I already explained the problem can (and usually does) live outside of the particular host that does the mount. It could be a boot race of a bunch of networking equipment, it could be some other network outage, etc. Point 2. Both Chris and Cy said that this is not a bug, since it was there for so many years. Sorry, this argument doesn't buys me. It is a typical cognitive distortion named "normalization" or "desensitization," where an individual becomes so accustomed to a negative situation that they no longer recognize it as problematic. I am also affected by that, and it is very good practice sometimes to force yourself to look at something with a fresh look. With a fresh look a suggestion to hardcode IP addresses in hosts(5) or doesn't look scalable neither modern option. I totally agree that in certain setups it is the right way to do, but not always. Point 3. I got our concern on a mount_nfs(8) blocking on a DNS resolution viewed as a POLA violation. So I suggest a trade-off: let's isolate the retrying behavior only to the background mode. That would fix the problem of machine booting without mounts and is very unlikely to affect anyones POLA feelings: https://reviews.freebsd.org/D49145 As the review text notes at the end we got a problem in the libc getaddrinfo(3). Rick also noticed it earlier when making his patch. Our resolver can't tell us a negative answer versus a timeour. This definitely is a problem and I already started investigating it. But definitely out of scope of NFS. -- Gleb Smirnoff From nobody Thu Feb 27 01:54:02 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z3DsR3Kv6z5pS1k for ; Thu, 27 Feb 2025 01:54:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z3DsR2qLWz3Hbv for ; Thu, 27 Feb 2025 01:54:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740621243; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n1Sp6sGwLJCmcRUU7N8KwXzd3jrWT1/oS29uM69cHS0=; b=h5prJhQPk1m9AWKuNhNUxiAuT4E475mxAJ8Kjrnr1NtuSfN90gVYqTL80zWrl7T+qfykQM AelhA4N0DovY2lYV6rAdZK8BHBtYmI27ixSBp5ACobJbExsQcTZPWM2nO093UT5BWM9Oqp G5Dabcj6V/qy+219yzL+cuB1qGHPvMH394cf9/i2yd9XW7o9fshBUZlwbnaoii9m9e+qFI Nj0a8EeyJNSH1unTWz6JO2kN33/wyCsyBc9YyJaG0g7w+7MZnyg7neCdylEIzToYPKpjlc 9tpW2BYW7n/gZzHiBdhCCUw93dSZApLewzjchRRq9F4GTXfLuo92lKpHw8Nmtw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740621243; a=rsa-sha256; cv=none; b=d5kJZrFMePJxTWY/QjqqvFYBhV8IYSM0TokjLSALiPLHx5cAQo3DXQOijmOq3nmEz+beOq Hv74Nkq07XI1alkDhte4NGZQjAJh50YCwz8Yeu7//0IzBzZ14Ls3pTNVgeK/bARhNy/MiW N7pA3XOOCPopqlbECz2btr/o3L77AIiuf8iQ3ao5WHehWOkIN4wkpw1OOuuQUoousQNcVj /arYABEj1VEf0td9xyKLKHRXgE1f4/Gb8i7ir/Nv2ndqWrgyYGzN07zSXXFt14Tt+9ByNk LAmqQoC2MVngUYZd/bMfQmpTOzAem4oyFwwQgmoiNbhfQH+TKPHGk/9e9DLYwg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740621243; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n1Sp6sGwLJCmcRUU7N8KwXzd3jrWT1/oS29uM69cHS0=; b=mp6/NGzaN0B0faJBOCpEcXH8rraeStQDXJXmTv+3amfxZWtUFVhE8ReqevuYibRZRAA6YR VzQSWfWrU7/2zjAAc2NP2G36s/9lT33ltUigz+PVdh+mLNUcFu45RHiFeNp3FpuFdaQs0M 0Jzqns8Q1WTMGqtLQdOFAlFDGhAVQMJCkH/IHBDBsq/6XGw7DUk1Z4G14oCUFOSa3lNsDM GRGVYgQulmEE8IZqVFAP5nN2uF2Ks78YkL6wCn6z3M/PtUIyYqZorm3R0OGqF1LO81u47Z 6JXdfAEkxv1joI0LfT7sMJBph10lB4adS+WYboSK1a5n0rO5+UBOyl7y/V4DfA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z3DsR2NNvz6VL for ; Thu, 27 Feb 2025 01:54:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51R1s3oK032316 for ; Thu, 27 Feb 2025 01:54:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51R1s32Z032315 for current@FreeBSD.org; Thu, 27 Feb 2025 01:54:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken Date: Thu, 27 Feb 2025 01:54:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ziaee@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285044 --- Comment #6 from Alexander Ziaee --- That color ASCII loader is just so beautiful. If I knew how to make the relevant file, I would add this back as an option, maybe `gfx-ascii.lua`. --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Thu Feb 27 03:24:05 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z3HHb1XT9z5pdR3 for ; Thu, 27 Feb 2025 03:43:23 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta003.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (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 4Z3HHZ6DXpz47mL; Thu, 27 Feb 2025 03:43:22 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Authentication-Results: mx1.freebsd.org; none Received: from shw-obgw-4004a.ext.cloudfilter.net ([10.228.9.227]) by cmsmtp with ESMTPS id nL2MtUzaJ9JM2nUnytwMAY; Thu, 27 Feb 2025 03:43:22 +0000 Received: from spqr.komquats.com ([70.66.136.217]) by cmsmtp with ESMTPSA id nUnjtVHDsJhBPnUnkthjFW; Thu, 27 Feb 2025 03:43:22 +0000 X-Auth-User: cschuber X-Authority-Analysis: v=2.4 cv=QY3Fvdbv c=1 sm=1 tr=0 ts=67bfdf5a a=h7br+8Ma+Xn9xscxy5znUg==:117 a=h7br+8Ma+Xn9xscxy5znUg==:17 a=kj9zAlcOel0A:10 a=T2h4t0Lz3GQA:10 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=YxBL1-UpAAAA:8 a=5RMlkMYnFiPG8oxYCK0A:9 a=CjuIK1q_8ugA:10 a=LK5xJRSDVpKd5WXXoEvA:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTP id BD18B1DF; Wed, 26 Feb 2025 19:24:05 -0800 (PST) Received: by slippy.cwsent.com (Postfix, from userid 1000) id B41B9313; Wed, 26 Feb 2025 19:24:05 -0800 (PST) X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.8+dev Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Gleb Smirnoff cc: Cy Schubert , Rick Macklem , Chris , Lars Tunkrans , FreeBSD CURRENT , Toomas Soome , Steve Rikli Subject: Re: RFC: mount_nfs failure due to dns not running yet In-reply-to: References: Comments: In-reply-to Gleb Smirnoff message dated "Wed, 26 Feb 2025 15:25:34 -0800." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Feb 2025 19:24:05 -0800 Message-Id: <20250227032405.B41B9313@slippy.cwsent.com> X-CMAE-Envelope: MS4xfCnAFfJRDLumDIi9WB8Ea30o48zQCpDeokpW+Bi3/HKrGmGjuGhpa3Ygn4zNfknwDOppa461F745j03LEHZoYlELqB3RznXhQvmB4u/Esc9wIPxvqUdt 7da3MA8jnAtwT6Dw1W+6y4IdAgfm8WJ2gY2u0A2KQIlUq1+MywGNZsmIB1wW0m3BeB4W89cCJxbcKFV4HH4qzdqeXrs90KbR5bMGxzMOlYj3kBQc12Y1ZbIi 0tm4S3EVqCgDp+xvi6hxnjS1YRskztoC0JXWZbGnORTb8X5W6WPFbC9+tW39/oVfoIMw+7S2OlIVSnrNwboigz9csx1h6Daf73nOtthreGpaRa7DoiHTUsuD FGsZpkXf X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US] X-Rspamd-Queue-Id: 4Z3HHZ6DXpz47mL X-Spamd-Bar: ---- In message , Gleb Smirnoff writes: > Hi guys, > > replying to all, asnwering Chris and Cy emails that I did not reply earlier. > I > trimmed quoting, but of course I've read your emails! > > Point 1. Please let's forget about 'late' option and any other rc(8) hints a > nd > magic. As I already explained the problem can (and usually does) live outsid > e > of the particular host that does the mount. It could be a boot race of a bun > ch > of networking equipment, it could be some other network outage, etc. > > Point 2. Both Chris and Cy said that this is not a bug, since it was there fo > r > so many years. Sorry, this argument doesn't buys me. It is a typical > cognitive distortion named "normalization" or "desensitization," where an > individual becomes so accustomed to a negative situation that they no longer > recognize it as problematic. I am also affected by that, and it is very good > practice sometimes to force yourself to look at something with a fresh look. > With a fresh look a suggestion to hardcode IP addresses in hosts(5) or doesn' > t > look scalable neither modern option. I totally agree that in certain setups > it > is the right way to do, but not always. This argument makes the point that the industry is wrong. I don't quite buy that either. I suppose more investigation would be required to find out why. On the flip side, when I was working on Solaris we didn't rely solely on DNS. We used NIS+ built on top of ONC+ (not to be confused with NIS built on top of ONC). There we had multiple NIS+ replicas on each network segment. In today's world we use LDAP. > > Point 3. I got our concern on a mount_nfs(8) blocking on a DNS resolution > viewed as a POLA violation. So I suggest a trade-off: let's isolate the > retrying behavior only to the background mode. That would fix the problem of > machine booting without mounts and is very unlikely to affect anyones POLA > feelings: > > https://reviews.freebsd.org/D49145 This would be acceptable. If an admin does have a chronic DNS issues, said admin could add the IP to hosts(5). > > As the review text notes at the end we got a problem in the libc > getaddrinfo(3). Rick also noticed it earlier when making his patch. Our > resolver can't tell us a negative answer versus a timeour. This definitely i > s > a problem and I already started investigating it. But definitely out of scop > e > of NFS. > > -- > Gleb Smirnoff -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e^(i*pi)+1=0 From nobody Thu Feb 27 14:07:22 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z3Y7z4mkZz5qF9K; Thu, 27 Feb 2025 14:07:43 +0000 (UTC) (envelope-from dch@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z3Y7z3qj3z3wrV; Thu, 27 Feb 2025 14:07:43 +0000 (UTC) (envelope-from dch@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740665263; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=h1TR4rxFFaNbiZHeTZ6hjflkG/SZSIQqRlQwRjAdTOQ=; b=mydzBLDyLMNBrECoabZKGTihDYmUtkxrLysCb3CFPDb5q48RfqwNmwIySMsozsSFs3ldL0 V94/Beo7pHT6f/j6f1CJZd079KmGJrQpA3003/GDKE3o+j9atyEux6Sl0XaOd+aZV3pN+S oR/qrJBZoc0uM+vizvIgxFj3hRAqnwntUy5XfEgywcq3LbMOJKogGDj52iyc1d/TbRCS0s y4j0KcbmxkWlhHVIo6mRi/dcOIzuLGysmatC97RFwwyUk6/qHVhSVcd3naAd3yDn+Etok3 so/oZr8lw4CJqWxLnt2jy6Z1J5nezMGiEY4oOecXmJuz8d7RiniUuSuWvZNAuA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740665263; a=rsa-sha256; cv=none; b=Y1oUiEENQNi35LhcAAjV0oT52jNhAl9g35AzqG+1yzqd0tskvN2ZYZIDMslaYziY+D/XzX tGhYinvh0IxMG5PM3Xts0nqsj++XHxW34Jha8gD3UI4EafXC4Myo1ohFq3Skn+crvSuwIF LJ1K/07QGVUz3aTU/pXJwJoA/vEv+F7MvTYnsbX6iXc0bCli2DREZAmPu/DHTM4saH4Xcp uJjLjSnnCIemz0XGcynnTlfPn43fLcYz6Iace2Mjl6Vm+niQrnqJcxAR4xQI4ZyQqoRNtP QWW6a0yiD1P7xrlHxQX4RXlkvBsTVOnDtxnwN40ctf+KULyG8gfsLl+79OIfpA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740665263; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=h1TR4rxFFaNbiZHeTZ6hjflkG/SZSIQqRlQwRjAdTOQ=; b=v7RYOdwyuH9KyWJWOneMcthK3ugWOkbAm9x2bThS61qEJWuSrKBQJXAN2Ja1W9/+/Fj17K NnArnbXEczDcBigO6LPbfwIW7IvM8Vcj6FhK4cRR+SxRBWH4KcbWi9fpWnuwhFoOenuZP9 e2Q1TgbnZVrvudtH8CKEE4ZZs/ErqtdSc8Q6DgmFxSlhl5a4Giaos+vANwcxczMIcZ19X3 WHJmqeTIp0lc/q/suMXbiBs+G6SqECMjNyhf+DIE7Rt7UVE7/Oog7WiWelAcVGDehfLD5o Ff0cfFsRFIEvt22RW8hVDaHMOBcHZhnAXliRUBoXXxn3+rO0G7XlJoJnlsBoaw== Received: from fauth-a1-smtp.messagingengine.com (fauth-a1-smtp.messagingengine.com [103.168.172.200]) (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) (Authenticated sender: dch/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Z3Y7z2fwLz8mw; Thu, 27 Feb 2025 14:07:43 +0000 (UTC) (envelope-from dch@FreeBSD.org) Received: from phl-compute-10.internal (phl-compute-10.phl.internal [10.202.2.50]) by mailfauth.phl.internal (Postfix) with ESMTP id 244E11200043; Thu, 27 Feb 2025 09:07:43 -0500 (EST) Received: from phl-imap-02 ([10.202.2.81]) by phl-compute-10.internal (MEProxy); Thu, 27 Feb 2025 09:07:43 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgdekjeeiiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefoggffhffvvefkjghfufgtgfesthejredtredt tdenucfhrhhomhepfdffrghvvgcuvehothhtlhgvhhhusggvrhdfuceouggthheshfhrvg gvuefuffdrohhrgheqnecuggftrfgrthhtvghrnhepffdukeelkeekueeludelteetvdeg ffejudelgedugfdtleehteelgeevtdefvdehnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepuggthhdomhgvshhmthhprghuthhhphgvrhhsohhn rghlihhthidquddvgeeluddtfeeguddquddvudefuddujeejqdgutghhpeephfhrvggvue fuffdrohhrghesfhgrshhtmhgrihhlrdhfmhdpnhgspghrtghpthhtohephedpmhhouggv pehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqtghurhhrvghnthesfhhrvg gvsghsugdrohhrghdprhgtphhtthhopehfrhgvvggsshguqdhhrggtkhgvrhhssehfrhgv vggsshgurdhorhhgpdhrtghpthhtohepfhhrvggvsghsugdqshhtrggslhgvsehfrhgvvg gsshgurdhorhhgpdhrtghpthhtohepshgrlhhvrgguohhrvgesfhhrvggvsghsugdrohhr ghdprhgtphhtthhopehfrhgvvggsshgusehnhidqtggvnhhtrhgrlhdrohhrgh X-ME-Proxy: Feedback-ID: icedc46df:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id EE740B0006A; Thu, 27 Feb 2025 09:07:42 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Thu, 27 Feb 2025 14:07:22 +0000 From: "Dave Cottlehuber" To: "Lorenzo Salvadore" , "FreeBSD Hackers" Cc: freebsd-current , "FreeBSD Stable" Message-Id: In-Reply-To: References: Subject: Re: FreeBSD Status Report - Fourth Quarter 2024 Content-Type: text/plain Content-Transfer-Encoding: 7bit On Thu, 27 Feb 2025, at 11:51, Lorenzo Salvadore wrote: > FreeBSD Status Report Fourth Quarter 2024 > > Here is the fourth and last 2024 status report, with 44 entries. > > It shows: 2024 has been a tremendously successful and busy year. Usually, one > would expect the final months in a year to be less busy, with people leaving > for holidays and New Years celebration. We still managed to deliver and see > great progress on so many things! > > Collecting and compiling this report took longer than planned, but it was worth > the wait. > > Thank you to the whole community for your amazing work and an especially big > thanks to those who contributed updates to this report! > > Enjoy the read! > > Chris Moerz, on behalf of the Status Team. Thanks Lorenzo, Chris, and everybody (including me ;-) who contributed a section, chased, curated, or edited the whole report as well. I am only half-way through. A+ Dave -- O for a muse of fire, that would ascend the brightest heaven of invention! From nobody Thu Feb 27 11:51:34 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z3V6t5l3nz5q82s; Thu, 27 Feb 2025 11:51:34 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z3V6t4qcNz3prj; Thu, 27 Feb 2025 11:51:34 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740657094; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=AIo0flFKV+/50gUnIXtuiNm49bXt8EsgFkj6or4Gx2M=; b=Gd0cq2wSpLbE8gbh+2T/zi2qRYjWzS08jxNDO6zmuIXxvvmYqoFMYh5SgZA9U12PILA4m9 Rj2M8anWAdzUcXfcx1QHEEeUoM5zSNzSHf7IE5hf9H4cQT1gmBd/eqECXU8jIWhhYeqfBK Q0MYmtPcXfZ75oQiz5IfJMbImndE5wVcytNWcocVLXRaNVOMGsDjZYDvz2snVJgmrRna6x 8HFRJv3o495wZNT5PJzE29Wq8O+BHCJT5qk9zIJ5oOjOzmuQs3RHX8ptEVjLoSqpcxslcg eoUX9/4HVKlSqEtCj5SgbKrzQxmtZO8hwufmEGNBOdzSyu5O8hhS89r/TH5tVA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740657094; a=rsa-sha256; cv=none; b=ETUrx0v0aIlTV9xnSrO7HdDnyQDGt/OjyXpC3uZpd0xiulDKCa/KirbmOVwJ8hQg1MxV1S g0ch/obkXTWdR/Y3icHUO8CgkSnxjQJySNkXo3O1N6d7xcsrWKB5tsVVCuBpq2nf2OAbZy 9MJZEv3+HPhTjhq07oTtoEO5XlXV7dg3ESw6fOi9P2l234Hd+anNQ8MbsManLepOK72ete q5vDQmMPktLmVuSECIVv/51rQ7YvlMkhmNhtzyw/G4u/xYlertztB5pCwChzFzVIp+fj79 /Q13tyOXxq0EbSKGwqN1HXhmoB/gVDcIb2QsUXvwTZ7DKYsK0X5/xqsnsJzfvg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740657094; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=AIo0flFKV+/50gUnIXtuiNm49bXt8EsgFkj6or4Gx2M=; b=X5T727X39lbUXz+HsxJH9fX6tumbzoAMisOrwHfp1buqii6zQG53NY92ZOQFscWQ4LAXfk mLCmAaouubkvVVQIv6ru+P/vUvXvnkV8L70lCCWTl3hl6G6dGk9K0zf/EuO2b1+gwzq/is it0og/LQxph8YE/EHm9y0JxFs2xuAq22Zi18K1e7gEQ69zK62cx373/eaKyW4HHu4xgC/C yiTe4tuuyCRrp/4YETRjID8qqOt/gj/8AhLkuFtlmNTWqpfB9/uiAF//mUmjJwHxm2neaY UhbPVOMXOhIDtx/+ZSi/6I3ZpjKA4c/ikjJJ8B4894D9MbtFbC4B2xiGzoxyYQ== Received: by freefall.freebsd.org (Postfix, from userid 1472) id 8B8782065; Thu, 27 Feb 2025 11:51:34 +0000 (UTC) Date: Thu, 27 Feb 2025 11:51:34 +0000 From: Lorenzo Salvadore To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD Status Report - Fourth Quarter 2024 Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline; filename="report.txt" Content-Transfer-Encoding: 8bit FreeBSD Status Report Fourth Quarter 2024 Here is the fourth and last 2024 status report, with 44 entries. It shows: 2024 has been a tremendously successful and busy year. Usually, one would expect the final months in a year to be less busy, with people leaving for holidays and New Years celebration. We still managed to deliver and see great progress on so many things! Collecting and compiling this report took longer than planned, but it was worth the wait. Thank you to the whole community for your amazing work and an especially big thanks to those who contributed updates to this report! Enjoy the read! Chris Moerz, on behalf of the Status Team. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2024-10-2024-12/ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection □ Bugmeister Team □ New srcmgr team • Projects □ Infrastructure Modernization □ Laptop Support and Usability Improvements Project □ Security engineering at the FreeBSD Foundation □ Security Audits □ Framework Laptop support • Userland □ PkgBase-motivated improvements to pkg □ Progress on the FreeBSD installer • Kernel □ Audio Stack Improvements □ mac_do(4), setcred(2), mdo(1) □ Suspend/Resume Improvements □ umb(4) driver for MBIM USB 4G/5G modems □ LinuxKPI 802.11 Wireless Update □ Wireless Update □ Syzkaller Improvement on FreeBSD • Architectures □ Pinephone Pro Support • Cloud □ FreeBSD on Microsoft HyperV and Azure □ OpenStack on FreeBSD □ Containers and FreeBSD: Cloud Native Buildpacks □ FreeBSD on EC2 • Documentation □ Documentation Engineering Team • Ports □ Ports Collection Accessibility - Colors Low Vision □ Containers and FreeBSD: AppJail, Director, OCI and more □ Improving Common Lisp Infrastructure in FreeBSD Ports □ FreeBSD Erlang Ecosystem Ports update □ Improve OpenJDK on FreeBSD □ Xfce on FreeBSD □ LXQt on FreeBSD □ GCC on FreeBSD □ Tor-Browser □ Greenbone Vulnerability Management Community Edition □ Wazuh on FreeBSD □ A bhyve management GUI written in Freepascal/Lazarus □ BSD-USER 4 LINUX • Third Party Projects □ Laptop and Desktop Work Group (LDWG) □ Containers and FreeBSD: Pot, Potluck and Potman ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. Following up with the FreeBSD Foundation Core had a video conference with the FreeBSD Foundation on 2024-12-12 to follow-up on their in-person meeting held in Dublin during EuroBSDCon. Core and the Foundation continue discussing how to improve the collaboration and how to support developers and contributors: • The next round of community survey • Identifying projects where core would like help from the Foundation • Work on the technical roadmap with the Foundation Work in Progress Core is currently working on the following items: • Policy on generative AI created code and documentation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://freebsdfoundation.org/ Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://freebsdfoundation.org/journal/ Foundation Events URL: https://freebsdfoundation.org/our-work/events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to advancing FreeBSD through technical and non-technical support. Funded entirely by donations, the Foundation supports software development, infrastructure, security, and collaboration efforts; organizes events and developer summits; provides educational resources; and represents the FreeBSD Project in legal matters. The following report covers just some of the ways we supported FreeBSD in Q4. Deb Goodkin here. On behalf of the Foundation, I want to start out by saying thank you to this amazing community! Your financial contributions have allowed us to step up and take on some significant projects, including large, multi-phase software development work, greater security improvements, and important infrastructure improvements that will continue through 2025. We also increased our FreeBSD advocacy efforts over many different technical and social media platforms, including creating more content to promote and advocate for FreeBSD. You’ll find more information about all of this work below. For a more in-depth look at our efforts in 2024, be sure to check out the year-end blog posts and my year-end reflections in the advocacy section below. We are hiring! Check out our jobs page here for our Solutions Specialist and Technical Marketing Manager job postings. Plus, we are looking for part-time technical writers and will be opening up another position soon, so keep an eye on this page https://freebsdfoundation.org/open-positions/. We are still finalizing our 2024 fundraising numbers, but at this writing, we have raised around $1,324,000. You might be thinking, why do not we have a final tally now that it is 2025? First, we have not yet received all the checks postmarked 2024 . We are also waiting on a few payments from invoices issued last year. We will have a final report in the next quarterly status report. Thank you to the individuals and organizations that made a financial contribution in Q4! We received 325 donations from individuals totaling $120,841 and six financial contributions from organizations totaling $326,000. We also received a grant from the Silicon Valley Community Fund. I would also like to send a shoutout to the anonymous donor who wanted us to help get Framework laptops into developers' hands. Pietro Cerutti has been coordinating that effort, and we are close to finalizing the process with Framework so developers can place their orders directly with them. We also funded almost $5,000 worth of AV equipment for the BSDCon AV team to minimize the amount of equipment needed to rent at each of the two main BSD conferences. Now, back to our financials. We will be publishing 2024 financial documents and reports in Q1. Our updated Q1-Q3 2024 Financial reports will be published by the end of January and will better match the budget format. The Final 2024 financial reports will be published in early Q2. Going forward, our budget and financial reports will provide more details on how funding is allocated to the major software development projects. For example, we will include how much was spent on the laptop project each quarter. We are working with our accountant to improve our accounting systems to be more transparent on how we spend our money. We are excited about the opportunities for FreeBSD in 2025 and beyond, and are growing our team to help support the work needed to take advantage of these opportunities. However, we need your help to sustain this. Our investments will only carry on this work for a year or two at most. If your company is invested in the long-term sustainability of FreeBSD, please consider giving a financial contribution so we can ensure it stays the secure, reliable, and innovative platform you depend on. Not sure how to go about asking? Please reach out. We can help you navigate the process. Please go here to make a donation: https://freebsdfoundation.org/donate/. To find out more about our Partnership Program, go here: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/. Advocacy During the 4th quarter of 2024, we continued to raise awareness, advocate for the project, showcase users, while also providing educational content to the FreeBSD community. Here are some highlights of those efforts. • Sponsored and helped to organize the Fall 2024 FreeBSD Summit which took place November 7-8, 2024 in San Jose, CA. Check out the event recap. Videos are available on the FreeBSD YouTube channel. • Updated the community on two of the new releases: □ FreeBSD 13.4: What’s new, and how did we get here? □ FreeBSD 14.2: What’s new, and how did we get here? • Published the NYI Case Study • Shared the FreeBSD Foundation 2024 Report on the Security Audit of the Capsicum and bhyve subsystems. Learn more in the Security Audit. • Created a series of year end retrospectives on the work we did in 2024. □ Your Impact on FreeBSD: 2024 Milestones and What’s Next □ 2024: A Year of Advocacy and Growth for the FreeBSD Foundation □ Celebrating 2024’s Collaborative Achievements at the FreeBSD Foundation □ FreeBSD Foundation: A Year of Sponsored Development in 2024 □ Reflecting on a Successful 2024 • Published additional blogs including: □ Why Your Open Source Project Should Prioritize Security: Lessons from FreeBSD’s Proactive Approach □ Why FreeBSD Should Be the Foundation for Your Security Product □ Celebrating FreeBSD Day with Tara Stella: A Journey from Linux to FreeBSD □ Advancing Cloud Native Containers on FreeBSD: Podman Testing Highlights • Participated in the following contributed articles, interviews and podcasts: □ All Things Open Blog: Prioritizing Security: Lessons from FreeBSD’s Proactive Approach □ FreeBSD Foundation Releases Bhyve and Capsicum Security Audit Funded by Alpha-Omega Project □ Why We Use FreeBSD Over Linux: A CTO’s Perspective • Published the October 2024, November 2024, and December 2024 FreeBSD Foundation Newsletters. • Released the September/October 2024 issue of the FreeBSD Journal with HTML versions of the articles. OS Improvements During the fourth quarter of 2024, 382 src, 135 ports, and 17 doc tree commits identified The FreeBSD Foundation as a sponsor. The Foundation and its investment partners supported four major projects: • Konstantin Belousov continued work on an AMD IOMMU driver for FreeBSD, a project jointly funded by AMD and the Foundation. This effort aims to enhance support for large-core AMD systems and other scenarios requiring interrupt remapping. The driver was pushed to the src tree in early November and continues to undergo testing and refinement. • Alpha-Omega and the Foundation have been jointly funding a project to improve FreeBSD security. For the latest updates, refer to the Security Engineering at the FreeBSD Foundation entry for the latest updates. • A project to improve FreeBSD laptop usability began this quarter. For details, refer to the Laptop Support and Usability Improvements Project report entry. • Work commissioned by the Sovereign Tech Agency to modernize FreeBSD’s infrastructure continued this quarter. The goal of this work is to help achieve and sustain a manageable bug backlog. As part of this effort, The Foundation worked with Bitergia to analyze and assess open Bugzilla bugs. Muhammad Moinur Rahman finished porting Grimoirelab and deploying Grimoire in the FreeBSD cluster. Other projects: • Alfonso S. Siciliano provided a FreeBSD Accessibility Project update. • Aymeric Wibo began implementing suspend-to-idle and S0ix sleep support. • Bjoern A. Zeeb shared a LinuxKPI 802.11 Wireless Update. • Chih-Hsin Chang continued work to improve OpenStack on FreeBSD. • Christos Margiolis shared an update on work to improve the FreeBSD audio stack. • Harald Eilersten began working on a project to improve OpenJDK on FreeBSD. • Isaac Freund worked on PkgBase-motivated improvements to pkg. • Jian-Lin Li began a project to improve Syzkaller on FreeBSD. • Joseph Mingrone spent time on a personal project to improve Common Lisp support in the ports tree. • Olivier Certner submitted a report entry describing the work he completed with Baptiste Daroussin to allow controlled process credentials transitions using the MAC framework. • Pierre Pronchery returned to working on a umb(4) driver for MBIM USB 4G/5G modems and he shared an update on work to improve the FreeBSD Installer. • Tom Jones started porting the iwx WiFi driver from OpenBSD (via Haiku). Other members of the Foundation’s development team contributed to FreeBSD development efforts. For example: • Mitchell Horne worked with community contributor Julien Cassette to add a RISC-V Allwinner D1 clock and reset driver. • Chuck Tuffli, John Baldwin, and Pierre Pronchery fixed a few bhyve issues: □ bounds checks in hda_codec □ out-of-bounds read in NVMe log page □ infinite loop in queue processing □ buffer overflow in pci_vtcon_control_send □ robustness of TRIM handling. • In the ports tree, Muhammad Moinur Rahman converted USE_OCAML and USE_JAVA to the USES framework. • Ed Maste squashed a couple of makefs(8) bugs related to creating ISO9660 filesystems via the cd9660(4) driver: □ cd9660 filename buffer maximum length □ cd9660 duplicate directory names. Continuous Integration and Workflow Improvement As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project’s continuous integration system and test infrastructure. Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. Go to https://freebsdfoundation.org to find more about how we support FreeBSD and how we can help you! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Release Engineering Team Links: FreeBSD 14.2-RELEASE announcement URL: https://www.freebsd.org/releases/14.2R/announce/ FreeBSD 13.5-RELEASE schedule URL: https://www.freebsd.org/releases/13.5R/schedule/ FreeBSD releases URL: https://download.freebsd.org/releases/ISO-IMAGES/ FreeBSD development snapshots URL: https://download.freebsd.org/snapshots/ISO-IMAGES/ Contact: FreeBSD Release Engineering Team, The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. The Team managed 14.2-RELEASE, leading to the official RELEASE build and announcement in December. Planning has started for the upcoming 13.5-RELEASE cycle, which is expected to be the final release from the legacy stable/13 branch; as such it will include updates to "contrib" code and some bug fixes, but is not expected to have any significant new features. In addition to previously shipped release artifacts (ISO and memory stick images, VM images, cloud offerings, etc.) the Team is now also providing OCI compatible container images. The Release Engineering Team continued providing weekly development snapshot builds for the main, stable/14, and stable/13 branches. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cluster Administration Team Links: Cluster Administration Team members URL: https://www.freebsd.org/administration/#t-clusteradm Contact: Cluster Administration Team FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications. In this quarter, the team has worked on the following: • Regular support for FreeBSD.org user accounts. • Regular disk and parts support (and replacement) for all physical hosts and mirrors. • Cluster software refresh. • Moving more cluster services to Chicago. • Supporting the Grimoirelab dashboard effort. Cluster software refresh Except for the package builders and developer-facing ("dogfood") machines, the FreeBSD cluster mostly tracks stable/X branches. At the time of this writing, there are 131 physical machines in the cluster. We have 54 machines on current, 61 on stable/14 and 14 on stable/13. Work continues to upgrade the remaining stable/13 machines to stable/14. The stable/ 12 machines have been slated for decommissioning for a while; they do not run production workloads. The remaining machines are slated for upgrading or decommissioning in the near future. Of the 297 jails in the cluster, 222 are now on stable/14. 12.x: Regular 2, Jails 7 13.x: Regular 14, Jails 59 14.x: Regular 61, Jails 222 >15.x: Regular 54, Jails 9 Total: Regular 131, Jails 297 Total installations: 428 Running -RELEASE|{-p*}: 0 Total geographic sites: 15 Moving cluster services to Chicago Earlier this year, we started building up our new site in Chicago. This quarter, we began decommissioning older machines in New Jersey and moving services to the newer machines in Chicago. Our long-term goal is for Chicago to become our primary location. This work will take several more months to complete. FreeBSD Official Mirrors Overview Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America — California, Chicago, New Jersey (primary site), and Washington. Our mirror site in Taiwan is experiencing an extended outage. We hope to have it back online during the first quarter of 2025. Also during the first quarter of 2025, we expect a second mirror site in California, generously hosted by Sonic. The hardware and network connection have been generously provided by: • Cloud and SDN Laboratory at BroadBand Tower, Inc • Department of Computer Science, National Yang Ming Chiao Tung University • Equinix • Internet Association of Australia • Internet Systems Consortium • INX-ZA • KDDI Web Communications Inc • Malaysian Research & Education Network • MetaPeer • New York Internet • NIC.br • Teleservice Skåne AB • Your.Org New official mirrors are always welcome. We have noted the benefits of hosting single mirrors at Internet Exchange Points globally, as evidenced by our existing mirrors in Australia, Brazil, and South Africa. If you are affiliated with or know of any organizations willing to sponsor a single mirror server, please contact us. We are particularly interested in locations on the United States West Coast and throughout Europe. See generic mirrored layout for full mirror site specs and tiny-mirror for a single mirror site. Sponsors: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Continuous Integration Links: FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD CI Tinderbox view URL: https://tinderbox.freebsd.org FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org Hosted CI wiki URL: https://wiki.FreeBSD.org/HostedCI 3rd Party Software CI URL: https://wiki.FreeBSD.org/3rdPartySoftwareCI Tickets related to freebsd-testing@ URL: https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci dev-ci Mailing List URL: https://lists.FreeBSD.org/subscription/dev-ci Contact: Jenkins Admin Contact: Li-Wen Hsu Contact: freebsd-testing Mailing List Contact: IRC #freebsd-ci channel on EFNet In the fourth quarter of 2024, we worked with the project contributors and developers to address their testing requirements. Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. Important completed tasks: • Update main and stable/14 build environment to 14.2-RELEASE • Update stable/13 build environment to 13.4-RELEASE • Fixed an old but not revealed bug about pw(1) usage in jail setup. Work in progress tasks: • Designing and implementing pre-commit CI building and testing and pull/ merge-request based system (to support the workflow working group) □ Improving the src/tests/ci work to support running test suites ☆ Merging CI: Add full test support □ Merging Pre-commit CI with CIRRUS-CI • Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds • Simplifying CI/test environment setting up for contributors and developers • Setting up the CI stage environment and putting the experimental jobs on it • Redesigning the hardware test lab and adding more hardware for testing Open or queued tasks: • Collecting and sorting CI tasks and ideas • Setting up public network access for the VM guest running tests • Implementing use of bare-metal hardware to run test suites • Adding drm ports building tests against -CURRENT • Helping more software get FreeBSD support in its CI pipeline (Wiki pages: 3rdPartySoftwareCI, HostedCI) • Working with hosted CI providers to have better FreeBSD support Please see freebsd-testing@ related tickets for more WIP information, and do not hesitate to join the effort! Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Collection Links: About FreeBSD Ports URL:https://www.FreeBSD.org/ports/ Contributing to Ports URL: https://docs.freebsd.org/en/articles/contributing/#ports-contributing Ports Management Team URL: https://www.freebsd.org/portmgr/ Ports Tarball URL: http://ftp.freebsd.org/pub/FreeBSD/ports/ports/ Contact: Tobias C. Berner Contact: FreeBSD Ports Management Team The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. Below is what happened in the last quarter. In the last quarter, we welcomed Xavier Beaudouin (kiwi@) as a new ports committer. According to INDEX, there are currently 36,332 (down from 36,504) ports in the Ports Collection. There are currently about 3,368 (down from 3,379) open ports PRs, of which 809 are unassigned. The last quarter saw 10,640 commits (down from 11,594) by 155 committers (one less) on the main branch and 733 commits (down from 832) by 61 committers (down from 78) on the 2024Q4 branch. The number of ports also decreased (down from 36,504). The most active committers to main were: • 3867 sunpoet@FreeBSD.org • 1156 yuri@FreeBSD.org • 368 jbeich@FreeBSD.org • 361 bofh@FreeBSD.org • 273 fuz@FreeBSD.org • 247 fluffy@FreeBSD.org • 209 vvd@FreeBSD.org • 206 eduardo@FreeBSD.org • 201 rene@FreeBSD.org • 157 uzsolt@FreeBSD.org A lot has happened in the ports tree in the last three months, an excerpt of the major software upgrades are: • Default version of Lazarus switched to 3.6.0 • Default version of PHP switched to 8.3 • Chromium 131.0.6778.204 • Electron 33.3.0 • Firefox 134.0 • Firefox-esr 128.6.0 • KDE Frameworks 6.9.0 • KDE Plasma 6.2.4 • Qt6 6.8.1 • Python 3.9.21 • Python 3.10.16 • Python 3.11.11 • Ruby 3.2.6 • Ruby 3.3.6 • Rust 1.83.0 • SDL 2.30.10 • SDL 3.1.6 • Sway 1.10 Three new USES were introduced: • cl to provide support for Common Lisp ports. • java to provide support for Java. • sbrk to handle ports requiring sbrk() During the last quarter, pkgmgr@ ran 14 exp-runs to test various ports upgrades and changes to bsd.port.mk. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Bugmeister Team Links: FreeBSD Bugzilla URL: https://wiki.freebsd.org/Bugzilla Contact: Bugmeister In this quarter we came even closer to steady-state; we are dealing with incoming PRs more quickly these days. For reference: https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=90 The overall number of PRs came down from slightly over 11,600 to right at 11,000. This was due to work from several people to go over entire groups of PRs (see below). Mark Linimon attended several video calls with various src committers. They are doing some experimentation to learn what kind of effort is sustainable. The most recent effort was to evaluate the latest incoming src PRs; you will note that many of them from the past few weeks have been marked as requesting feedback. Bugmeister folks also did some passes through the database to clean up metadata: • reassigned bugs away from committers who had had their commit bits safekept over the last year. • cleaned up bugs for Product: Base System Status: In Progress. A number of these were not being actively worked on. The count is down to 184. □ In particular, Mark Linimon believes "assigned to mailing list" means "it is not really In Progress". Perhaps it has been discussed, but we do not really have a state for that. (We can make an argument that that itself is a bug.) □ We are now down to only a handful of the above, from "too many". The concept is to make sure In Progress has some real meaning. • evaluated PRs for mfc-stableN. In particular, any having mfc-stable12 had that flag cleared. □ The concept is to make sure these metadata have some real meaning as well: e.g. "a commit has been made and should be evaluated for MFCs". □ There are now a much smaller number of these. • closed numerous PRs as "Overcome By Events": □ (old version) + (contains the string "boot") □ (old version) + (contains the strings "alpha" or "beta") • evaluated "PR shows a commit" (possibly via Phabricator)" and "there was no trailing discussion". □ In a few cases of the above we simply assigned them and made sure that mfc-stable[13|14] was set, if it seemed appropriate. □ This does leave many that have a commit and then have trailing discussion. I think we will need more volunteers to go through those. • removed many of the 'patch' keywords from PRs. In the optimal case these should now be imputed by metadata in each attachment. In a few cases where patches are submitted inline instead of as an attachment, the keyword stays. There may be a few of these left over from the GNATS conversion. The use of inline patches should be discouraged, as automation has no way to detect them. Thanks to our triagers, especially Alexander Ziaee. There were various discussions about bug futures that came up in various video chats. One is that there is a (supported) successor to Phabricator, which itself is now no longer developed. Multiple groups will need to coordinate to evaluate it. Jan Bramkamp has volunteered to help with the task "automate harvesting PRs and evaluating whether they still apply". Mark Linimon to collaborate. Clusteradm@ helped us fend off yet another crawler site. While that was ongoing, bugzilla was nearly unusable due to timeouts, as were other services hosted on the same machine (wiki and cgit among others). We also welcomed our newest Triage member, Lexi (aka 'ivy' on Discord). Finally, glebius was added to bugmeister@ alias as core.13 liaison. See also: https://wiki.freebsd.org/Bugzilla/SearchQueries ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ New srcmgr team Contact: srcmgr A new source management team has been ratified by core@ to handle management of the FreeBSD src tree, akin to portmgr@ and doceng@ for the ports and docs trees, respectively. The initial members are Ed Maste, Mark Johnston, John Baldwin, and Warner Losh. srcmgr@ is currently focused on finding ways to make src developers more productive, and to try and manage the large numbers of bug reports and pull requests that we receive. The team meets every two weeks to discuss src-related issues and spend time triaging bug reports and pull requests. Meeting minutes are available on GitHub. The srcmgr@ team has a charter and is working on developing and documenting policies to help manage the src tree. In December, srcmgr@ ran an online bug-busting session, attended by 15 developers. We spent time going through recent bug reports, plus a list of older ones with patches. The team plans to host monthly sessions of this type, and aims to open them to a wider audience in the future. The team plans to develop a lurker program similar to portmgr@'s in the first half of 2025. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Projects Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Infrastructure Modernization Contact: Ed Maste Contact: Alice Sowerby The project started in Q3 of 2024 and was commissioned by the Sovereign Tech Agency with a budget of $745,000, to be spent over about one year. The main goals are to improve security tools for the base system, ports, and packages, update the project’s infrastructure to speed up development, enhance build security, and make it easier for new developers to get started. Q4 update • Work Package A: Technical Debt reduction. The Foundation collaborated with the Source Management team to commission and deploy a number of dashboards that characterize the bug backlog for the FreeBSD Project. These were created to the team’s specifications by our project partner, Bitergia, who used an open source tool called GrimoireLab to create the dashboards. Foundation staff have hosted the dashboards on a FreeBSD deployment and they can be seen at https://grimoire.freebsd.org/. More information about the dashboards can be found at https://github.com/freebsd/grimoire. The Source Management team has also used these dashboards to support their new, evolving approach to bug triage and it has been included as a key tool for collaborative bug-squashing events. • Work Package B: Zero Trust Builds, and Work Package C: CI/CD Automation. The Foundation collaborated with various key management and administration teams within the FreeBSD Project to co-create the details of the scope for these two projects. They are scheduled to start in January and will conclude in Q2/3. • Work Package D: Security Controls in Ports and Packages, and Work Package E: Improve Software Bill of Materials (SBOM). These have not started yet as they are scheduled for February and March starts respectively. Commissioning body: Sovereign Tech Agency ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Laptop Support and Usability Improvements Project Contact: Ed Maste Contact: Alice Sowerby The project began in Q4 of 2024 and is funded by the FreeBSD Foundation and Quantum Leap Research. It has a budget of $750,000, which will be used over one to two years. The goal is to improve key features like WiFi, audio usability, suspend and resume functions, graphics, and Bluetooth. The team will also create clear documentation and step-by-step guides to help people use the new features. Q4 Update • The Foundation initiated the project, created a public roadmap, and allocated contractors to relevant workstreams. December was the first monthly iteration of development, covering: □ Implement S0ix low power states □ Put a VM into hibernation □ Create a list of supported laptops □ Create a translation layer for Linux drivers on FreeBSD □ Create a list of supported window environments □ wireless_update,POC driver for Intel WiFi interfaces (based on OpenBSD/ Haiku) □ Resolve tech debt in pkg to enable PkgBase development □ Document how to update graphic drivers □ Implement s2idle low power state □ Bring in camera code donation from Dell • The FreeBSD project started a community group called the "Laptop and Desktop Working Group" (LDWG) to help people working on Laptop- and Desktop-related projects to connect and collaborate with others in the community working on similar efforts. The group held its first monthly meeting in December 2024. To stay updated on LDWG activities, you can join the Desktop mailing list. Sponsor: The FreeBSD Foundation Sponsor: Quantum Leap Research ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Security engineering at the FreeBSD Foundation Links: FreeBSD Foundation Releases Bhyve and Capsicum Security Audit Funded by Alpha-Omega Project URL: https://freebsdfoundation.org/news-and-events/latest-news/ freebsd-foundation-releases-bhyve-and-capsicum-security-audit-funded-by-alpha-omega-project / How FreeBSD security audits have improved our security culture URL: https://fosdem.org/2025/schedule/event/fosdem-2025-6152-how-freebsd-security-audits-have-improved-our-security-culture / Home of the ORC WG URL: https://github.com/orcwg/orcwg FreeBSD Foundation: Contact Us URL: https://freebsdfoundation.org/about-us/contact-us/ Open Source Vulnerability schema (OSV Schema) URL: https://openssf.org/projects/osv-schema/ ossf/osv-schema tools: import a conversion tool to and from VuXML (#237) URL: https://github.com/ossf/osv-schema/pull/237 Contact: Pierre Pronchery My tasks at the FreeBSD Foundation continue to revolve around Security Engineering for the FreeBSD Project. First, we keep working on the outcome of the source code audit on bhyve and Capsicum, documenting and researching how to prevent and mitigate similar issues from occurring again in the future. This includes the processes relevant for contributions to the FreeBSD Project, as well as the preparation of a joint presentation with Alpha-Omega at the BSD Devroom during the coming FOSDEM conference in 2025. At the same time, I am liaising with the Open Regulatory Compliance Working Group (ORC WG), where an FAQ is being elaborated jointly by a number of stakeholders on the European Union’s newly introduced Cyber Resilience Act (CRA). This is all related to our ongoing collaboration with OpenSSF, notably the self-assessment initiative; note that the FreeBSD Foundation can provide assistance in this regard for projects deploying FreeBSD. Finally, possibilities around the integration of OSV tooling into the FreeBSD ecosystem are under investigation as well. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Security Audits Contact: Ed Maste Contact: Alice Sowerby The project began in Q2 of 2024 and was funded by Alpha Omega with a budget of $137,500, which was used over about six months and is now complete. The focus was on conducting a code audit for key subsystems, bhyve and Capsicum, as well as performing a security audit of the development process. The funds were used to hire a specialist offensive security firm to perform the code audit, to contract developers to address issues found, and for Foundation staff’s work on both audits. Q4 update The project is complete. The Code Audit and subsequent reports were released after the related Security Advisories were published. The Process Audit is complete. It was created by FreeBSD Foundation staff who ran an outreach exercise to gather information about the current FreeBSD development process. The teams consulted were: Security Team, Source Management Team, Cluster Administrators, Release Engineering Team. Information was gathered through an online long-form survey which was structured around existing frameworks for analysing security in software development. Teams were asked to describe current development processes and appraise the current security practices, as well as to make suggestions for improvements. The responses were collated and synthesised into the report by Foundation staff. The report was reviewed for accuracy by the original respondents. The report will now be made available to the Security Team and other teams previously mentioned, as well as to the Foundation executive team. This will be a useful tool in identifying areas for investment and prioritisation going forward as more security projects are planned and funded. The report is intended primarily for FreeBSD Project and Foundation planning purposes and as such there is no plan to promote it to an external audience. Interested readers should contact the Security Team to request a copy of the report. To learn about the project, and to see historical monthly updates visit: https://github.com/ossf/alpha-omega/tree/main/alpha/engagements/2024/FreeBSD. Sponsor: Alpha Omega Project ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Framework Laptop support Links: Framework Laptop page on FreeBSD Wiki URL: https://wiki.freebsd.org/Laptops/Framework_Laptop/ Guide on installing and using FreeBSD on Framework systems URL: https://github.com/FrameworkComputer/freebsd-on-framework Tracking ticket: Framework Laptop: Feature support, bugs and improvements URL: https://bugs.freebsd.org/262152 Contact: Daniel Schaefer Contact: Li-Wen Hsu Contact: Sheng-Yi Hong For a long time, Framework Laptop Inc is friendly to the FreeBSD project in many aspects, including providing engineering samples to Foundation for testing and working on support. Since 2024 summer, there are several small hackathons in Framework’s Taipei office on testing FreeBSD on different models of Framework laptop, and the peripheral devices. Sheng-Yi is using the laptop provided by Framework Computer to add more device support, e.g. d3b05d0ea10a: Add smbus and i2c device IDs for Meteor Lake. Daniel from Framework Computer Inc started a repository under Framework Computer’s GitHub organization to keep the notes of installation and miscellaneous information. He fixed fingerprint readers (libfprint) not just for Framework, but in general on FreeBSD. And working on the support and fix to many related drivers on FreeBSD. In November, Foundation people and some FreeBSD developers visited Framework’s San Francisco office and had a meeting for checking the current FreeBSD support status and discussing the possible future collaboration plans. Foundation will continue working on improving the general laptop support and using Framework as one of the target platforms for the Laptop Support and Usability Project. Sponsor: The FreeBSD Foundation for Li-Wen’s work Sponsor: Framework Computer Inc for Daniel’s work, hardware and space support ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Userland Changes affecting the base system and programs in it. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PkgBase-motivated improvements to pkg Contact: Isaac Freund Some problems blocking progress on the PkgBase project are caused by shortcomings of pkg(8). The primary goal of my work on pkg is to unblock PkgBase progress. However, all users of pkg will benefit even if they do not use PkgBase. The scheduler for pkg’s install/upgrade/delete jobs has been rewritten, motivated by solving PR259785. The new scheduler models the scheduling problem as a directed graph and splits upgrade jobs into delete/install halves only when necessary to break a cycle in the graph. This formal model gives strong guarantees about ordering that the old scheduler was not able to provide and prevents unnecessary splitting of upgrade jobs. It also fixes longstanding bugs where the old scheduler would bail out and cause the entire upgrade to fail. The new scheduler is included in pkg version 1.21.99.3 (pkg-devel). The rest of my work this quarter has been related to pkg’s automatic tracking of shared library dependencies, which PkgBase heavily relies on. The initial motivating problem was PR265061 but it was necessary to make more fundamental changes to how pkg tracks shlibs before cleanly solving that problem became possible. When a package is created with pkg-create(8), pkg scans the included files and generates shlibs_provided/shlibs_required lists based on the executables/shared libraries found. Before my changes, pkg would use the elf hints file of the host system as an input to pkg-create in order to filter out shlibs provided by the base system from the generated shlibs_required list. An ALLOW_BASE_SHLIBS option disabled this filtering for the purpose of building PkgBase packages. After my changes, pkg-create no longer reads the elf hints file of the host system and base system shlibs are included in the generated shlibs_required list. When pkg-install(8)/pkg-upgrade(8)/etc. invoke the solver on an non-PkgBase system, pkg generates a list of shlibs provided by the base system as an input to the solver by scanning /lib and /usr/lib. On a PkgBase system, the PkgBase packages provide all base system shlibs. This allows the ALLOW_BASE_SHLIBS option to be eliminated. It also gives better integration between the ports packages and PkgBase packages as shlib dependencies of ports packages on PkgBase packages are now tracked rather than ignored. Finally, this change significantly simplifies the pkg codebase and improves portability. This change was implemented in https://github.com/freebsd/pkg/pull/2386 and is not yet included in a pkg release. With that change and other internal improvements I was able to add support for tracking lib32 and Linuxulator shlibs, which should resolve the problem that originally motivated my work on pkg’s shlib handling (PR265061). This support is implemented in https://github.com/freebsd/pkg/pull/2387 and is not yet included in a pkg release. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Progress on the FreeBSD installer Links: Improving Repair Ability of the FreeBSD Installer URL: https://wiki.freebsd.org/SummerOfCode2024Projects/ImprovingRepairAbilityOfTheFreeBSDInstaller GSoC 2024 - Improving Installer with Repair and Upgrade Ability (#1395) URL: https://github.com/freebsd/freebsd-src/pull/1395 bsdinstall: Add pkg install support in live env (#1424) URL: https://github.com/freebsd/freebsd-src/pull/1424 bsdinstall: Add repair scripts to installer menu (#1427) URL: https://github.com/freebsd/freebsd-src/pull/1427 Laptop and Desktop Working Group URL: https://wiki.freebsd.org/LaptopDesktopWorkingGroup Contact: Pierre Pronchery As part of 2024’s GSoC Project on the FreeBSD installer, I had the pleasure to mentor Chun Cheng Yeh (aka "Leaf") with his implementation of additional capabilities. The aim was to add support for repairing or updating an existing installation of FreeBSD, as well as allowing packages to be installed in the Live environment. This work has been consolidated into three distinct pull-requests, available on GitHub. While some aspects probably still require additional polishing before a possible merge, the possibility to significantly extend the installer images into a potentially life-saving tool is within reach. This is particularly relevant given the ongoing efforts to improve support for laptop and desktop use of FreeBSD. In this context, I am currently resuming work on the graphical version of the installer. The most immediate challenge includes shaping it suitably for integration into the next major release. Combining the two initiatives above should help FreeBSD close some gaps with its competition amongst other modern Operating Systems, for the enterprise as well as for laptop and desktop use. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Audio Stack Improvements Contact: Christos Margiolis The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement — from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs. This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature. Important work since last report: • sound(4) and driver bug fixes, including panics and races. Several cleanup and refactor patches. • Committed mididump(1). Ships with 14.2-RELEASE and 14-STABLE. • Implementing AFMT_FLOAT support. This fixes ports, such as emulators/wine, that require AFMT_FLOAT support from OSS. Related bug reports: PR 184380, PR 281390, PR 264973, PR 157050. Future work includes: • More bug fixes, optimizations and general improvements. • Implement a generic MIDI layer, similar to pcm/, and improve/modernize the MIDI codebase in general. • Implement a bluetooth device management utility. • virtual_oss patches and improvements. • Attempt to automate snd_hda(4) pin-patching. • Investigate SOF/DMIC support. You can also follow the development process in freebsd-multimedia@, where I post regular reports. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ mac_do(4), setcred(2), mdo(1) Contact: Olivier Certner Contact: Baptiste Daroussin This project aims at allowing controlled process credentials transitions without using setuid executables but instead leveraging our MAC framework. For an overall presentation, we refer the reader to the previous quarter’s report. As this is a progress report, we only recall the outline here. In a nutshell, this project comprises two components: • mac_do(4) is the kernel module that checks credentials transition requests and authorizes those that match rules configured by the administrator. • mdo(1) is the userland program playing the role of a mediator between processes wanting to launch other processes with changed credentials and mac_do(4), whose function is to authorize only specific such changes. setcred(2) is the new system call at the interface between them. It enables userland to request various credentials changes atomically, allowing mac_do (4) to base its decision on the transition between the initial and desired final credentials. Both prerequisite commits and changes in MAC/do proper have been reviewed and all commits have finally been pushed to FreeBSD’s main branch, including documentation in the form of a new manual page for setcred(2) and changes to the mac_do(4) one to match the new sysctl(8) knobs and rules syntax. Rules can now express finely which groups are allowed in the resulting credentials for a given UID or GID, notably making it possible to specify which target primary and supplementary groups the final credentials can, or must, or must not include. Please consult mac_do(4) for a description of the new syntax and examples. Future work, in no particular order and timeframe, may include: • For the mac_do(4) component: □ Currently, it can only grant credentials transitions for processes spawned from the /usr/bin/mdo executable. The possibility to tweak this path may be interesting for custom thin jail layouts. The ability to have several such paths is one of the missing pieces to be able to use mac_do(4) in conjunction with other credentials-granting programs such as sudo(1) and doas(1). □ mac_do(4) currently can only grant new credentials if they are requested via the new setcred(2), as it needs to see the current and desired final credentials to make a decision. However, each call to traditional and standard credentials-changing functions, such as setuid (2), seteuid(2), etc., can be considered as a (limited) full transition on its own, which mac_do(4) could decide upon. This functionality could allow to more finely control transitions to root and, combined with that of the previous point, to install and use credentials-granting programs without the "setuid" bit. However, the full power of this new mac_do(4) module version cannot be harnessed without modifying these programs to use setcred(2). • For the mdo(1) component: □ The credentials transitions that can be requested are fairly limited compared to what mac_do(4)'s rules can allow. It would be useful to make it possible to: ☆ Specify any list of target groups (primary or supplementary), possibly based on user names (with the implicit list coming from the contents of /etc/passwd and /etc/group) but allowing some tweaks (such as excluding a particular group in the final credentials). ☆ Allow changes of groups only. ☆ Request a password before calling setcred(2) in certain cases. This weakens the security paradigm of the mac_do(4)/mdo(1) combination, as it would now rely on userland for part of the gating process, but seems acceptable in many cases. ☆ Grow a mode producing the target part of rules corresponding to the contents of the password and group databases for some users. We welcome any feedback on this new version and the future-work list above. Sponsor: The FreeBSD Foundation Sponsor: Kumacom SARL ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Suspend/Resume Improvements Links: Blog URL: https://obiw.ac/s0ix/ Working Branch URL: https://github.com/obiwac/freebsd-s0ix Contact: obiwac Suspend-to-idle and support for S0ix sleep is in the process of being added to FreeBSD. This will allow modern Intel and AMD laptops (e.g. AMD and newer Intel Framework laptops), some of which do not support ACPI S3 sleep, to enter low power states to increase battery life. Ben Widawsky from Intel started working on this in 2018 but his work was never finished and is now outdated. His work has now been picked up and the first goal is to get suspend/resume working on the Framework 13 AMD Ryzen 7040 series by end of January. There are plans for presenting initial results at a talk at FOSDEM. Currently, all device power constraints on AMD can already be parsed to enter a system’s low power states. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ umb(4) driver for MBIM USB 4G/5G modems Links: UMB(4) - OpenBSD Device Drivers Manual URL: https://man.openbsd.org/umb UMB(4) - NetBSD Kernel Interfaces Manual URL: https://man.netbsd.org/umb.4 Bug 263783 - USB MBIM: Support for LTE/4G USB modems URL: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263783 Introduce the USB umb(4) network driver URL: https://reviews.freebsd.org/D48167 Contact: Pierre Pronchery The Mobile Broadband Interface Model (MBIM) is a protocol for communication with network USB devices, transmitting packet data over mobile broadband networks. Implementing this protocol adds support for a whole range of USB devices providing connectivity to mobile networks, such as 4G, 5G, and their subsequent technological evolutions. A first implementation for this protocol was performed for OpenBSD in 2016, under the name umb(4). I have ported it myself to NetBSD under the same name, back in 2019. I was then contracted to make it work with OPNSense, and authorized to publish it as Open Source in 2022. Unfortunately, by this time, some changes in FreeBSD effectively broke the driver, and it could not be merged until fixed. This quarter I have managed to offer an updated version and confirmed it working (thanks Mike and Zhenlei!). This version is now under review in Phabricator as D48167. The submission is still based on code from 2020, and behind progress made by OpenBSD since that time. As such, it is currently restricted to IPv4. However, I believe it makes sense to keep the review simple and focus on the design decisions and integration, before progressively importing the improvements made upstream since then in OpenBSD (notably IPv6 support). In its current form, the driver was modified from being out of tree and available as a plug-in for OPNSense, into a kernel module and its companion binary, umbconfig(8). This management binary effectively allows the umb(4) driver to be configured beyond the capabilities of ifconfig(8): the PIN or PUK code, APN, username/password, or roaming parameters can be setup, and the connectivity tracked as well (network provider, speed…​). Should you want to give it a spin yourself and get hardware supported by this driver, the single most important feature to look for is support for the MBIM specification. The manual page for OpenBSD provides a list of devices that should be compliant; note that some of them require preliminary configuration in order to effectively expose the MBIM interface. The exact procedure is vendor-specific, and can also depend on the model and current configuration of the device. You should refer to the documentation offered for your device for any steps necessary. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ LinuxKPI 802.11 Wireless Update Links: Categorised Wireless Problem Reports URL: https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0 Overview of drivers URL: https://people.freebsd.org/~bz/wireless/ Contact: Bjoern A. Zeeb Contact: The FreeBSD wireless mailing list With multiple wireless projects ongoing, this report focuses on the efforts using permissively licensed Linux wireless drivers mostly unmodified on FreeBSD. Drivers previously committed directly to FreeBSD src.git were retroactively imported in vendor branches and merged to main. This makes maintenance and identifying local changes a lot easier. The iwlwifi(4), rtw88(4), and rtw89(4) drivers got updated in main to match Linux 6.11. The rtw89(4) driver, which had been ported and in the tree for a while, got connected to the build. Thanks for that goes to the efforts of the community finding two bugs preventing it from working before. Wireless firmware in ports got updated and a release flavor was added. The release building framework got enhanced to install the firmware packages onto the release media. The installer grew support to run fwget(8) on the installed system to install the firmware. This all together ensures that (wireless) drivers with external firmware can be used from the installer and right away on the installed system without the need for alternate connectivity. With the framework in place for iwlwifi(4), rtw88(4), and rtw89(4) support for more drivers can easily be added in the future. These changes shipped the first time with 14.2-RELEASE. Having a lot of these requested necessities out of the way, time was spent on HT(802.11n) and VHT(802.11ac) improvements to the LinuxKPI framework synching between driver and net80211. Hardware crypto offload got sorted along with A-MPDU RX/BA offload right at the end of the year. Both were needed towards the goal to achieve higher throughput with iwlwifi(4). A half-year old bug, which stayed unnoticed preventing packets to be sent beyond scanning with rtw88(4) in main and stable/14, received a patch to fix the situation. Work for the first quarter of 2025 should include: • finishing basic HT and VHT support, and • looking at finishing the code for generic LinuxKPI 802.11 suspend/resume support Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Wireless Update Contact: Tom Jones Contact: The FreeBSD wireless mailing list With Support from the FreeBSD Foundation this quarter I started working on porting the iwx WiFi driver from OpenBSD (via Haiku). The iwx driver supports many of the chipsets supported by iwlwifi, but rather than make that driver more complex the OpenBSD developers decided to support these devices in a new driver. iwx on OpenBSD currently supports running as a station in 80211abgn and ac, it does not yet support ax rates. The goals of this project are to import a maintainable driver from OpenBSD and to gradually increase support until we have a native driver in FreeBSD with support for 80211ac (and potentially 80211ax). Currently the driver supports 80211a and 80211g and is able to saturate the practical limits of the rates these standards offers (roughly 28Mbit down and 25 Mbit up). The driver is under active development and moving quite quickly. The plan for the next quarter is to add support for high throughput rates, implement monitor mode and stabilise the driver for a public call for testing. Once the driver is stable enough a call for testing will be posted to the freebsd-current and freebsd-wireless mailing lists. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Syzkaller Improvement on FreeBSD Links: google/syzkaller URL: https://github.com/google/syzkaller Contact: Jian-Lin Li Contact: Li-Wen Hsu Syzkaller is an operating system kernel fuzzer that can look for vulnerabilities in the kernel. This project aims to improve the support of Syzkaller on FreeBSD. Based on the existing WiFi fuzzer designed for Linux, we drafted a WiFi fuzzer for FreeBSD. We planned to use wtap(4), a virtual wifi driver for testing, in order to support WiFi fuzzing. Some of the design details include: • Introduce a new netlink command to wtap in order to realize frame injection, which is essential for WiFi fuzzing. • Initialize wtap devices in Syzkaller before WiFi fuzzing. We are developing some prototypes and discussing the feasible design plan with some experts. There is not much progress yet. We hope to have more progress on this project in the next few months. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Architectures Updating platform-specific features and bringing in support for new hardware platforms. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Pinephone Pro Support Links: Repository on Codeberg URL: https://codeberg.org/Honeyguide/freebsd-pinephonepro Contact: Toby Kurien The project to port FreeBSD over to the Pinephone Pro is progressing. The aim of this project is to step by step support components of the Pinephone Pro in FreeBSD so that the device one day might be usable as a highly mobile FreeBSD device. In this quarter: • A driver for the RK818 power management IC was implemented, enabling the device regulators. • A driver for the real-time clock was also implemented, allowing the system to keep time between reboots. • A driver for the RK818 battery charger and battery monitor was written to allow the battery to be charged via USB, and to retrieve some battery information like voltage and charging status via sysctl. • The code repository has been updated with scripts and documentation on how to compile the custom kernel and device tree, and patch a FreeBSD 15-CURRENT image with them so that it boots on the Pinephone Pro. The next steps are to enable UEFI-based framebuffer support to enable output to the screen, and to enable USB on-the-go functionality, which might allow for plugging in a USB keyboard and/or Ethernet. Porting the Linux driver for WiFi will also be looked into. Any developers wanting to assist are encouraged to get in touch. Additional feedback and testers are welcome. Also see this thread on the FreeBSD Forum if you want to participate. Sponsor: Honeyguide Group ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cloud Updating cloud-specific features and bringing in support for new cloud platforms. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD on Microsoft HyperV and Azure Links: Microsoft Azure article on FreeBSD wiki URL: https://wiki.freebsd.org/MicrosoftAzure Microsoft HyperV article on FreeBSD wiki URL: https://wiki.freebsd.org/HyperV Contact: Microsoft FreeBSD Integration Services Team Contact: freebsd-cloud Mailing List Contact: The FreeBSD Azure Release Engineering Team Contact: Wei Hu , Contact: Souradeep Chakrabarti Contact: Colin Su Contact: Li-Wen Hsu In this quarter, we have published the 14.2-RELEASE on Azure Marketplace. Colin Su has presented at the FreeBSD 2024 Fall Summit about Azure DevOps Pipeline. Souradeep Chakrabarti from Microsoft has added a feature to use hypercalls for TLB shootdown on Hyper-V and Azure. Wei Hu root-caused an issue on missing CDROM device when booting FreeBSD on the latest Azure v6 VM SKU. V6 type only offers NVMe disks to guest OS. He also continues bug fixing for FreeBSD MANA NIC device. Work in progress tasks: • Automating the image publishing process and merging to src/release/. (Li-Wen Hsu) • Colin Su is testing adding FreeBSD support in Azure Pipelines □ https://github.com/microsoft/azure-pipelines-agent/pull/3266 □ Building and publishing snapshot builds to Azure community gallery. Open tasks: • Update FreeBSD-related doc at Microsoft Learn • Update sysutils/azure-agent to the latest version • Upstream local modifications of Azure agent • Port Linux Virtual Machine Extensions for Azure Sponsor: Microsoft for people in Microsoft, and for resources for the rest Sponsor: The FreeBSD Foundation for everything else ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OpenStack on FreeBSD Links: OpenStack URL: https://www.openstack.org/ OpenStack on FreeBSD URL: https://github.com/openstack-on-freebsd Contact: Chih-Hsin Chang Contact: Li-Wen Hsu The OpenStack on FreeBSD project aims to merge the capabilities of the OpenStack cloud infrastructure with the robust features of FreeBSD. Our objective is to harness FreeBSD’s unique features while ensuring compatibility with OpenStack’s operations. In the fourth quarter, our primary goal was to finalize the tasks promised under milestone 1 by establishing a new environment for a demonstrable Proof of Concept (POC) site. However, the simultaneous aim to set up another deployment based on FreeBSD Jail within the same environment led us to spend considerable time on network design and tuning. Fortunately, we successfully established external network connectivity for guest VMs by the end of this period. The remaining challenge now is to enable guest VMs to automatically acquire IP addresses through cloud-init. On another note, we attempted to obtain the domain XML of VMs from the Linux-based OpenStack to compare with the XML used for bhyve VMs. These domain XMLs are utilized by Libvirt, defining each virtual machine’s configuration and operational parameters. Comparing the differences between the two will aid in developing the "bhyve serial console over TCP" work. In the first quarter of the upcoming year, we will continue to conclude the tasks related to milestone 1 of our project. Additionally, we will persist in developing FreeBSD Ports for OpenStack components, further integrating and enhancing the system’s capabilities. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Containers and FreeBSD: Cloud Native Buildpacks Contact: Robert Gogolok Cloud Native Buildpacks (CNBs) transform application source code into container images. Those images can run on any cloud. With buildpacks, organizations can concentrate the knowledge of container build best practices within a specialized team, instead of having application developers across the organization individually maintain their own Dockerfiles. A few weeks ago, I’ve started to look into FreeBSD support for buildpacks. My goal is to have working versions of the tools lifecycle and pack in the next few months. There were previous attempts to bring support for FreeBSD to buildpacks, for example to lifecycle: • Add support for FreeBSD #1087 • Add FreeBSD Support #1271 After looking into those changes, I’ve decided to first introduce some general cleanup steps to keep the required changes for FreeBSD small. This resulted in the following changes that were successfully integrated: • Remove obsolete // +build lines #1431 • Use unix build constraint #1432 • Support FreeBSD build phase #1439 With these steps, it is now possible to compile lifecycle under FreeBSD. The next steps are: • Provide missing FreeBSD functionality to lifecycle. • Further investigate FreeBSD as a build target in lifecycle. • Investigate and get the tool pack to compile and run under FreeBSD. • Provide lifecycle and/or pack via FreeBSD ports. • Investigate the idea of FreeBSD buildpacks for some popular languages, similar to paketo buildpacks. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD on EC2 Links: EC2 Boot performance over time URL: https://www.daemonology.net/freebsd-ec2-boot-performance/ Contact: Colin Percival FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances. In the past quarter, first boot performance of ZFS AMIs has been significantly improved, e.g. from about 22 seconds to about 11 seconds for 15.0 "base" AMIs on amd64. Graphs of boot performance over time are now being generated and published automatically; typical times are around 9-12 seconds for "base" and "small" AMIs and 14-18 seconds for "cloud-init" AMIs. On Graviton systems, the EC2 "shutdown" and "reboot" operations now work as intended (starting with FreeBSD 14.2). On Graviton systems, adding new devices (e.g. EBS volumes) while the system is running now works in HEAD and support is expected to be merged in time for FreeBSD 14.3. Sponsor: Amazon Sponsor: https://www.patreon.com/cperciva ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Documentation Noteworthy changes in the documentation tree, manual pages, or new external books/documents. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Documentation Engineering Team Link: FreeBSD Documentation Project URL: https://www.freebsd.org/docproj/ Link: FreeBSD Documentation Project Primer for New Contributors URL: https://docs.freebsd.org/en/books/fdp-primer/ Link: Documentation Engineering Team URL: https://www.freebsd.org/administration/#t-doceng Contact: FreeBSD Doceng Team The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see FreeBSD Doceng Team Charter. Document changes • Handbook: □ Add warning about custom kernel configurations. □ Mention Rocky Linux 9 userland. □ Add notes to VMWare related setup guide. • Committer’s guide: Document "Discussed with" Improve "Fixes:" metadata. • Porter’s Handbook: Document new TCL_ variables. • Website: Remove Turkish links. • Documentation repository: □ Added OpenBSD 7.6 manual pages. □ Updated Debian 11/12 manpages. FreeBSD Translations on Weblate Link: Translate FreeBSD on Weblate URL: https://wiki.freebsd.org/Doc/Translation/Weblateurl Link: FreeBSD Weblate Instance URL: https://translate-dev.freebsd.org/url Q3 2024 Status • 18 team languages • 215 registered users 1 new translator joined Weblate: • Sean Markham (ES) Languages • Chinese (Simplified) (zh-cn) (progress: 14%) • Chinese (Traditional) (zh-tw) (progress: 11%) • Dutch (nl) (progress: 1%) • French (fr) (progress: 1%) • German (de) (progress: 1%) • Greek (el) (progress: 1%) • Indonesian (id) (progress: 1%) • Italian (it) (progress: 11%) • Korean (ko) (progress: 30%) • Norwegian (nb-no) (progress: 1%) • Persian (fa-ir) (progress: 6%) • Polish (progress: 2%) • Portuguese (progress: 0%) • Portuguese (pt-br) (progress: 31%) • Sinhala (progress: 1%) • Spanish (es) (progress: 39%) • Spanish (Chile) (progress: 0%) • Turkish (tr) (progress: 5%) We want to thank everyone who contributed, translating, or reviewing documents. And please, help promote this effort on your local user group; we always need more volunteers. Packages maintained by DocEng During this quarter the following work was done in packages maintained by doceng@: • www/gohugo: update to 0.140.2 • misc/freebsd-doc-ja: fix build Open issues There is 1 open PR in Bugzilla assigned to doceng@: • 276923 www/gohugo link error under poudriere ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Collection Accessibility - Colors Low Vision Link: Project wiki page URL: https://wiki.freebsd.org/portconfig Contact: FreeBSD Accessibility mailing list Contact: Alfonso Sabato Siciliano FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications. The collection provides tens of thousands of ports; port configuration is a key feature. It is possible to configure a port before the building and installation. The command "make config" uses a text user interface (TUI) to set up port options interactively. Recently low vision users (mainly with cataracts) have requested new features to easily change the colors of the TUI. Several features have been implemented to allow changing colors, for example: a new environment variable to set the UI to black and white, or the ability to set colors by reading a configuration file at runtime. All features have been described in portconfig(1) since version 0.6.2. To note, blind users can refer to PortOptsCLI - Ports Collection Accessibility, Status Report Third Quarter 2023 to use the Ports Collection. Tips and new ideas are welcome. If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Containers and FreeBSD: AppJail, Director, OCI and more Links: AppJail on GitHub URL: https://github.com/DtxdF/AppJail Director on GitHub URL: https://github.com/DtxdF/Director LittleJet on GitHub URL: https://github.com/DtxdF/LittleJet Reproduce on GitHub URL: https://github.com/DtxdF/reproduce Contact: Jesús Daniel Colmenares Oviedo AppJail is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. Director is a tool for running multi-jail environments on AppJail using a simple YAML specification. A Director file is used to define how one or more jails that make up your application are configured. Once you have a Director file, you can create and start your application with a single command: appjail-director up. LittleJet is an open source, easy-to-use orchestrator for managing, deploying, scaling and interconnecting FreeBSD jails anywhere in the world. Their goals are to simplify life for sysadmins and developers by providing a unified interface that automates the jail workflow by combining the base FreeBSD tools. AppJail and all its meta-projects extensively follow The Ephemeral Concept which helps update/upgrade jails more easily as they become disposable. I have used this extensively to deploy my jails with services since this concept was implemented in AppJail. Although there have been great people working on OCI for a long time, this month the featured topic is OCI, and the advances related to this technology in FreeBSD make it possible to implement it in AppJail. The latest release adds more useful features, improves on existing things and implements OCI. I’m continually adding more Makejails, a simple text file that automates the deployment of services in jails. There is an organization on GitHub that I call The Centralized Repository if you want to make a contribution. The last improvement was to implement BuildBot as the CI/CD of AppJail images, so any change made to a repository that is tracked by BuildBot will generate a new task to build and deploy an image to the mirrors. And if mirrors are not an option, appjail-reproduce can be used to build images using your own resources. Sponsor: https://www.patreon.com/appjail ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Improving Common Lisp Infrastructure in FreeBSD Ports Contact: Joe Mingrone Common Lisp (CL) is a general-purpose, multi-paradigm programming language first conceived in the early 1980s. Although it predates many modern programming languages, it remains a viable option for many different projects. One contemporary example is Grammarly, a widely used grammar engine reportedly implemented in CL and capable of processing over a thousand sentences per second. The FreeBSD ports tree has provided CL support for many years. The initial work was contributed by Henrik Motakef in 2003, and then enhanced and maintained by Jimmy Olgeni. The infrastructure facilitated building and installing CL libraries using ASDF so that multiple CL implementations could load compiled object code files (fasl) at run-time without conflicts. However, many issues crept in over the years. Support dwindled to only one CL implementation, SBCL, and users encountered longstanding bugs such as conflicting ASDF versions and write errors when loading libraries outside the ports tree. Also, managing dependencies was cumbersome because most infrastructure code was included as part of the devel/cl-asdf port. A long overdue update of the FreeBSD CL infrastructure was completed this quarter. The primary outcome is that users can, once again, easily and reliably work with CL on FreeBSD. For example, installing and loading the popular Alexandria library under SBCL requires only a few simple steps. % pkg install cl-alexandria-sbcl % sbcl * (asdf:load-system :alexandria) Similar steps can be used to load libraries for the other two newly supported implementations: CCL, and CLISP. Most users will likely prefer to work with the fasl ports, although there is no obligation to do so. Because ASDF is now configured to fall back to its default caching mechanism of writing fasl to a cache under ${HOME}, users can also install CL source ports without the associated fasl port or load CL sources from outside of the ports tree. Other highlights of the update include: • decoupling ASDF initialization from devel/cl-asdf by creating a dedicated port: devel/freebsd-cl-asdf-init • creating USES=cl • adding and updating various CL library ports for the three supported implementations • updating and modernizing lang/ccl and lang/clisp For details, refer to these commit logs: • 4c954c1522cbf4d05013caaf40c36458d82f1480 • f6a75a8f9bf20dbf1e9a4d5bc171d58f595c1ec1 • 1d7c75a5cde6792b3872340edeaf8f278add291a • 148251b431b8d972623bb3adaa5a71355f47ac26 • 7f68336ed19be61027dfb7b461aacd056733eba4 The tentative plan is to add support for ECL after an ASDF output translation issue is solved and to create ports for other CL libraries. Feedback, testing, and contributions are welcome. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Erlang Ecosystem Ports update Links: FreeBSD Erlang wiki URL: https://wiki.freebsd.org/Erlang Erlang/OTP language URL: https://erlang.org/ Elixir language URL: https://elixir-lang.org/ Gleam language URL: https://gleam.run/ Contact: FreeBSD Erlang mailing list The Erlang runtime system, commonly known as the BEAM, provides a runtime that is used by a number of programming languages and applications in the FreeBSD ports collection. In the final update for 2024, the Erlang ecosystem team has been busy: • Regular updates to all Erlang/OTP releases, to stay current • Elixir 1.18.1, Gleam 1.6.3, and RabbitMQ updates Users of RabbitMQ need to update each quarter to avoid being stuck on an unsupported release of Erlang/OTP + RabbitMQ, without a supported migration path. Note that as the upstream Erlang OTP team only commit to supporting the two latest major releases, more and more point updates are arriving for OTP26-27, but not for the older Erlang runtime releases, which are now unlikely to get security and bug fixes. The Erlang team will be updating the default Erlang runtime to OTP26, to lang/ erlang, along with the usual dependencies and tooling. Additional testing and community contributions are welcome; please reach out on the mailing list, especially if you are able to help testing of specific port updates. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Improve OpenJDK on FreeBSD Links: Project description URL: https://freebsdfoundation.org/project/ improving-openjdk-on-freebsd/ Contact: Harald Eilertsen The aim of this project is to improve support for Java in FreeBSD, by working with the upstream OpenJDK community, as well as the FreeBSD community in getting the changes and additions needed for fully supporting FreeBSD accepted upstream. As this is a new project, there is not much to report yet, but here’s what has been achieved so far: • The Java Test Regression harness (jtreg) now builds and runs on FreeBSD, and the process of upstreaming the changes has started. • OpenJDK 23 builds and runs on FreeBSD, and work on adding it to the ports collection has started; this is still considered experimental. https://reviews.freebsd.org/D48194 • Work on porting the next OpenJDK (version 24) has started. https://github.com/snake66/jdk/tree/jdk24-freebsd Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Xfce on FreeBSD Links: Xfce 4.20 Upstream Release Announcement URL: https://xfce.org/about/news/?post=1734220800 Xfce meta-port on FreshPorts URL: https://www.freshports.org/x11-wm/xfce4 Contact: Xfce team Contact: Guido Falsi The FreeBSD Xfce team (xfce@) works to ensure the Xfce desktop environment is maintained and fully functional on FreeBSD. This quarter the Xfce team members are pleased to welcome Xfce 4.20 to the FreeBSD ports tree! This new release adds many stability improvements and some new functionality. Upstream work for this release was focused on getting the code base ready for Wayland support. This release brings experimental Wayland support, although not all components have been migrated, so it may not work for you. For further details, refer to the Xfce 4.20 Upstream Release Announcement. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ LXQt on FreeBSD Links: LXQt Project URL: https://lxqt-project.org/ LXQt Project GitHub URL: https://github.com/lxqt Contact: LXQt Team LXQt is an advanced, easy-to-use, and fast desktop environment based on Qt technologies. It has been tailored for users who value simplicity, speed, and an intuitive interface. Unlike most desktop environments, LXQt also works fine with less powerful machines. During this quarter, the x11-wm/lxqt metaport was updated to 2.1.0. This update adds initial Wayland support to the LXQt desktop. You can read some release highlights here. Anyone interested in helping with the project is welcome. Current version: 2.1.0 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ GCC on FreeBSD Links: GCC Project URL: https://gcc.gnu.org/ GCC 11 release series URL: https://gcc.gnu.org/gcc-11/ GCC 12 release series URL: https://gcc.gnu.org/gcc-12/ GCC 13 release series URL: https://gcc.gnu.org/gcc-13/ GCC 14 release series URL: https://gcc.gnu.org/gcc-14/ Contact: Lorenzo Salvadore The exp-run to update GCC default version from 13 to 14 is getting forward. As usual, thanks to everyone involved. If you maintain any of the affected ports or want to give a hand preparing and testing some patches, you can consider trying adding -fpermissive to CFLAGS in affected ports as a temporary solution: GCC 14 has transformed some warnings into errors, which is the cause of many of the failed builds. The -fpermissive flag switches those errors back to warnings. However, it is preferable that upstream updates its code to remove those warnings completely so that -fpermissive is not necessary, possibly with FreeBSD ports maintainers support. If the code is not maintained upstream anymore, the time might have come to deprecate the port. Work has been done on some bugs too, mainly upstream: • https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210 has been fixed: a recent change in the FreeBSD headers caused a regression in the GCC 15 development version; • https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115008 has been fixed: this was an issue with posix_fallocate failing on FreeBSD on a ZFS filesystem; • an attempt to fix bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282797 specific to aarch64 for -devel ports has failed. If you are able to give a hand on this, it would be very much appreciated. Thanks to everyone who has helped with these issues. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Tor-Browser Links: Tor Project Homepage URL: https://www.torproject.org/ GitLab Repository URL: https://gitlab.torproject.org/tpo/applications/ tor-browser Contact: Martin Filla Since the last report, significant progress has been made in building and packaging Tor Browser for FreeBSD. Additionally, the Tor Browser version has been updated to 14.0.3, which is now available from the Tor Browser download page and also from our distribution directory. This update includes important security updates to Firefox, ensuring that users benefit from enhanced security and privacy features. Expanding FreeBSD compatibility remains a priority to provide seamless and native privacy solutions for the platform. What is new: Tor Browser version 14.0.3 includes: • Rebase to Firefox 128.5.0esr. • Backporting of security fixes from Firefox 133. • Platform-specific updates such as disabling Microsoft SSO on macOS and updating GeckoView for Android. • Updated Go to version 1.22.9 in the build system. Help Needed: To move forward, assistance is required in the following areas: Code Review: Ensure patches meet the required coding and security standards. Testing: Volunteers are needed to test Tor Browser 14.0.3 on FreeBSD to identify edge cases. Bug Fixing: Developers familiar with FreeBSD and Firefox’s codebase are encouraged to resolve known issues. Feedback: If you find a bug or have suggestions for improving this release, please let us know through the GitLab Repository or the provided contact email. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Greenbone Vulnerability Management Community Edition Links: Greenbone URL: https://www.greenbone.net/en/ Greenbone GitHub URL: https://github.com/greenbone/ Contact: José Alonso Cárdenas Márquez The Greenbone Community Edition (GVM) covers the actual source code of the Greenbone Vulnerability Management software stack, which is also known as OpenVAS scanner, a security feed with more than 160.000 vulnerability tests, a vulnerability management application, and much more. During this quarter, security/gvm metaport was updated to 24.1.2. This update includes the following: • databases/pg-gvm: Updated to 22.6.6 • security/gsa: Updated to 24.1.0 (Only amd64 and aarch64) • security/gsad: Updated to 24.1.0 • security/openvas: Updated to 23.14.0 • security/gvmd: Updated to 24.1.2 • security/gvm-libs: Updated to 22.15.0 • security/py-notus-scanner: Updated to 22.6.5 • security/py-greenbone-feed-sync: Updated to 24.9.0 • security/py-ospd-openvas: Bump PORTREVISION • security/py-gvm-tools: Updated to 24.12.1 • security/py-python-gvm: Updated to 24.12.0 A quick GVM jail installation to test it can be done using AppJail, makejail, or https://github.com/AppJail-makejails/greenbone-openvas. Anyone interested in helping with the project or interested in aarch64 device donation for testing is welcome. Current version: 24.1.2 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Wazuh on FreeBSD Links: Wazuh URL: https://www.wazuh.com/ Contact: José Alonso Cárdenas Márquez Wazuh is a free and open source platform used for threat prevention, detection, and response. It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments. Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data gathered by the agents. Besides, Wazuh has been fully integrated with the Elastic Stack or OpenSearch Stack, providing a search engine and data visualization tool that allows users to navigate through their security alerts. After a long break, ports has been updated to include Wazuh version 4.9.2. This version of Wazuh uses Python 3.11 instead of 3.10, and it includes some new features: • support to get ports info, • support to get processes info, • improved memory info, • FreeBSD decoder and rule files, and • FreeBSD Security Configuration Assessment files for 13.x, 14.x and 15-CURRENT. Also, FreeBSD ports include a custom version of wazuh-dashboard-plugins for a better integration with FreeBSD. Wazuh can easily be installed in a jail by following the Wazuh AppJail-Makejails tutorial. Anyone interested in helping with the project or interested in aarch64 device donation for testing/packaging is welcome. Current version: 4.9.2 TODO • Add Wazuh cluster-mode infrastructure AppJail makejails • Add vulnerability detection support to FreeBSD Wazuh agent • Add FreeBSD as officially supported platform by Wazuh Inc • Update FreeBSD SCA Policies to new FreeBSD CIS Benchmark ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A bhyve management GUI written in Freepascal/Lazarus Links: Bhyvemgr URL: https://github.com/alonsobsd/bhyvemgr/ Contact: José Alonso Cárdenas Márquez Bhyvemgr is a bhyve management GUI written in Freepascal/Lazarus on FreeBSD. It needs a bunch of tools mostly installed on base system and some installed from ports/packages. The application is being developed for desktop users to easily and quickly setup and run virtual machines on FreeBSD hosts. During this quarter, there were many bugfixes and improvements to Bhyvemgr. These are some new features that were added: • Support for Trusted Platform Module (TPM through software via swtpm) on CURRENT • Bootvars support • Bios, system, board and chassis information can be modified • Systray icon support on almost all desktop environment (tested on Plasma, Gnome, Xfce, LXQt and IceWM) Bhyvemgr supports aarch64 only on 15-CURRENT and amd64 from FreeBSD 13.x to 15-CURRENT. Also bhyvemgr can be • compiled and installed from ports, • installed as binaries through pkg with gtk2, qt5 or qt6 interface support. Anyone interested in helping or supporting the project are welcome. Current version: 1.3.1 TODO • Testing on real aarch64 hardware (aarch64 device donation for testing is welcome) • Add uart device support ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BSD-USER 4 LINUX Contact: Maksym Sobolyev Links: Project Page URL: https://github.com/sobomax/qemu-bsd-user-l4b Tooling URL: https://github.com/sobomax/qemu_l4b The bsd-user-4-linux project ports BSD user-mode emulation for QEMU to Linux. The primary goal is to enable unmodified FreeBSD binaries to run on modern Linux systems. Additionally, the project aims to provide multi-platform container images with a functional FreeBSD environment and ready-to-use GitHub Actions templates. Current Status: • The initial port successfully runs make -jN buildworld. • Most command-line tools are working as expected (sh, bash, find, grep, git, clang, etc). • A GitHub Actions pipeline builds x86_64 emulation images for: □ linux/386 □ linux/amd64 □ linux/arm/v5 □ linux/arm64/v8 Next Steps: * Implement container integration. How You Can Help: • Test with your preferred toolchain, report issues, or contribute fixes. • Build and test non-x86_64 emulation images (e.g., FreeBSD/arm64 on Linux/ x86_64). The code works on BSD but needs testing on Linux. • Support us on Patreon. Sponsor: Sippy Software, Inc. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Third Party Projects Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Laptop and Desktop Work Group (LDWG) Links: Desktop mailing list URL: https://lists.freebsd.org/archives/freebsd-desktop/ Wiki Page URL: https://wiki.freebsd.org/LaptopDesktopWorkingGroup Contact: Chris Moerz October 2024 marked the inception of the Laptop and Desktop Work Group (LDWG), affectionately known as "Ludwig". This initiative provides a collaborative platform for the community to engage in development, testing, knowledge exchange, and advocacy for FreeBSD on laptops and desktops. Everyone is welcome to join, if interested. Scope of Work: • Content Creation: Develop recordings, articles, tutorials, documentation, and system configurations for stakeholders interested in FreeBSD on laptops and desktops. • Encouraging Contributions: Invite developers, testers, and industry experts to enhance the usability of FreeBSD on laptops and desktops. • Facilitating Collaboration: Promote code contributions, testing initiatives, operational support, and hardware insights. • Supporting User Stories and Ongoing Projects: Assist in the creation, validation, prioritization, and delivery of user stories identified in the FreeBSD Foundation’s “Laptop” investment work package. On November 16, 2024, the LDWG held its inaugural virtual meeting. The strong interest in FreeBSD for laptops and desktops was evident from the diverse group of participants, including developers, contributors, Discord community moderators, users, and FreeBSD Foundation members. Meeting slides, minutes, and recordings are available on the Group’s wiki page. During the meeting, the group identified prioritized gaps and potential improvements in the following areas: • Console • Desktop Environment • Documentation • Hardware □ Graphics □ Wireless (WiFi and Bluetooth) □ USB/Thunderbolt • Installer • Performance • Software and Port Availability All activities are documented on the Group’s worksheet. The Group encourages anyone interested in contributing to add their name. If there is any planned or ongoing work, please include it in the worksheet. Alice Sowerby provided an update on the The Foundation’s Laptop project, highlighting the need for volunteers to support testing efforts. The Group is running an online survey to gather input from non-participants. The survey will remain open until the next call in January, where results will be presented and discussed. Hope to see you there! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Containers and FreeBSD: Pot, Potluck and Potman Links: Pot organization on GitHub URL: https://github.com/bsdpot Contact: Luca Pizzamiglio (Pot) Contact: Bretton Vine (Potluck) Contact: Michael Gmelin (Potman) Pot is a jail management tool that also supports orchestration through Nomad. Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad. During this quarter, there was no new Pot release. The tool is stable and used in production for quite some time already. Potluck got a new Netbox image. Additionally, various images have received improvements and bug fixes, e.g. improving their syslog-ng integration. Last not least, all images have been rebuilt several times: for FreeBSD 14.1, to include security fixes, then again for 14.2 and also for the new quarterly packages. As always, feedback and patches are welcome. Sponsors: Nikulipe UAB, Honeyguide Group From nobody Fri Feb 28 15:35:43 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z4C336kr8z5m67J for ; Fri, 28 Feb 2025 15:35:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z4C335zx5z3pvk for ; Fri, 28 Feb 2025 15:35:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740756943; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6bE+z/QAk73xWK8bxflq3ltHBPgpF9p/Auy+qGnsBlg=; b=x7Q03k2RCTQWUfOj6amxuVpM+9hyoEllZPzAnyIuF38/us1WIgHX6uPPpwWVDfsEObMSfp ZaR1efjgAYrMdHybuE03tprnfUujObkwvroSH1miUdEaa43cnfBTKQL+pRE8dhTwpi05Lk MgPaQs+ChxcSIZoyEtRt492CuQ5qDW7ajZIvUGS5hToFuS0r21ns1AmgqGt0R2dPvyu/x8 35bSGi/h4jdSRS6gBiRO/1+DEMg8ECncPw3+VlvFtz0mqXeEwA52ZSQX5lEeXZbYxoK5hk DKZ5OkWhULmN3PpsV+G4onAAjOs1UMrlvq17Ok3i900kySMyVc5I9+kZK3qN7Q== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740756943; a=rsa-sha256; cv=none; b=jw75dfLPur0fn1pRzf5Pc3QLh1kxnlwnyn83fkd1DOte/1FMPVwt4Uf3Z+5bhGdkY9iIQE +Pe5hiHaM55Rvvm7q+tRM0EBTKaLKuM77bAQVlbTjUmM+Vkp6cVTvOtNbOGka7KA9vIRXC C/NiYo+oz16t9tjTXZFnJMA7FBc776xB0sTHoUXD9AGbeHPwlBbj1JOqf886suSeQH8gFj Imhn7zd5dx3JuhWRzz+LnQgjJgv8Qfv4QjbYqg/lFGmJG/Oo3O506U86N/9MZAA5hAqp+g ymQt3xLZ1SUGvdrRwX5/SdxuFShsXVsfoLvM24A+/XUZBseoYNlNT+m0FD422w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740756943; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6bE+z/QAk73xWK8bxflq3ltHBPgpF9p/Auy+qGnsBlg=; b=bm7zctq1E1FkQt8lcHyOpX9prTFFVD+8MCmTGaehDDXyFqp57rkOGn7WuGOmZBMu0lZft+ 9STXMq937vi+B3jQiADYIKevRRW2IsiMaojhiC3xGV8l0K8tgexb4xk1mc6zKbPttytNPk aIwGoajVt0DUmtMRoirbBsT13QYsdAk/bjmH/FTND2J5vE7hicSFMnqRZ32z27Cvprrvi6 PSd8IQV+DdZCpCYwudVkV/v1oyhooZ+USHLyXnWfkHIG3GoQKTG1B2xglBttxu7UH2wAPj O9rm5FBedMwnxmQeZtREiRF6/VGyWgF+Oe0fKbTCmShZ6tLLVWtuGEfNdHEwDg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z4C335MBgzbK1 for ; Fri, 28 Feb 2025 15:35:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51SFZh5R013877 for ; Fri, 28 Feb 2025 15:35:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51SFZh8S013876 for current@FreeBSD.org; Fri, 28 Feb 2025 15:35:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken Date: Fri, 28 Feb 2025 15:35:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285044 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Sat Mar 1 00:01:14 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z4QGL67Nbz59WnG; Sat, 01 Mar 2025 00:01:14 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z4QGL5Kbtz46M0; Sat, 01 Mar 2025 00:01:14 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740787274; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=MOt3JUbsSwogspikhDU3md59jyyBtFNCoGPaPtNHItw=; b=oTI1TeRkS444pryzdiavCfjY7Y4GnL/OMapz92rpvxFWGgBP/baIDGGpdlt5eoAKAfxQIZ UAGjUHKMLPZL+lWJijMXRjNGTNrVhkLZR/9NKkIXxoJHwHfmpDv1WojXOsx36QQowS6n0E aSsRpw6+ia6a0d4zFKHywgznBatfORp7b81wr3xUy8HGyBA6OTFnIjzS6WxFgVGBPpxhcT VLEot1HHNzjuC6xTWcdTxw2/MCEHCoPTgb1oRBrTD5TRZcxZdaZsFEjI1wx/hfC8guqMxe f5sZh5C6+x1sXbqHx0W2Wqun6JKUDSWqHRE+C9G419iX9wyUN4Tyh0wizcickA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740787274; a=rsa-sha256; cv=none; b=K8xVMTU7hR8XnoLncomOZcf9x7Ta2DIhFgVe4r0nrz+8xAYiac8LJ3Xsr/pnHEOnG25SC8 /DCYvAgsGZ8Nh0T8OZpOjjVAmH3cTibhcmp+3JW03YoqvQBmHbTMpPVrdUaXA6KO85n/OF sJn+RfTMEiVQJG4e1U2E6vCNt+aDMW2g2c7K137IFWtiyB1czg23Nv6iZx/0d6ZN3sT5y0 tlBhPeZWQVHOQNTjOHXu9mdIEFC78DWGvZ8EplC+HqbjnTU523hBcYx/QWGWoETm3IzbbI PaMznVF5YdfUVtp1J6w+vGlA+oTFWdDtERO3lu12fn1yt0qIIAjNR7SAIClvGA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740787274; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=MOt3JUbsSwogspikhDU3md59jyyBtFNCoGPaPtNHItw=; b=KgB+rbgI4Dtei1l/6RkTaqnSRGoaigJGknxxKOOVraIyvd1i4jys0LTSRwlA7kAF1iNZcU VSLjuuVe0k/CDbzzm2OQArB/zMg8U8BpjOVHmDRD3ajEXB3N4+ixRcu8nD0EYMIpfJLDa8 zCutJz3Eb84bIriQl/mqZdtwEvyeGHV+cMV0yC2KArLO5mh+3NJY9qSvh75/N3Vs7hCNH6 IwLSVXw2pktEqnH37OH5QF71J360p7Y9QgmPMxQlmTugjkCkmCYYZTJRc4I5330v6KwAA8 zy22EMqI8hUnUmr2uBtBadP9jgnrAQ6/EOLTSgicDHnA1RzL/41cDoV7qnGICA== Received: by freefall.freebsd.org (Postfix, from userid 1472) id 9825CBA3C; Sat, 01 Mar 2025 00:01:14 +0000 (UTC) To: freebsd-status-calls@FreeBSD.org Subject: Call for 2025Q1 status reports Cc: freebsd-current@FreeBSD.org,freebsd-hackers@FreeBSD.org,devsummit@FreeBSD.org,secretary@asiabsdcon.org Message-Id: <20250301000114.9825CBA3C@freefall.freebsd.org> Date: Sat, 01 Mar 2025 00:01:14 +0000 (UTC) From: Lorenzo Salvadore List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2025 for work done since the last round of quarterly reports: January 2025 - March 2025. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2025-01-2025-03/ (create it if it is missing); * submit a pull request at . You should put your reports in the directory doc/website/content/en/status/report-2025-01-2025-03/ (create it if it is missing); * send an email to status-submissions@FreeBSD.org including your report. An AsciiDoc template is available at . We look forward to seeing your 2025Q1 reports! Thanks, Lorenzo Salvadore (on behalf of status@) From nobody Sun Mar 2 09:45:24 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z5HB05ggFz5nytJ for ; Sun, 02 Mar 2025 09:45:28 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z5H9z2n9Zz3Gnc for ; Sun, 02 Mar 2025 09:45:27 +0000 (UTC) (envelope-from guru@unixarea.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unixarea.de header.s=blu3434000 header.b=ixDFFuxw; dmarc=none; spf=pass (mx1.freebsd.org: domain of guru@unixarea.de designates 178.254.4.101 as permitted sender) smtp.mailfrom=guru@unixarea.de DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=unixarea.de ; s=blu3434000; h=Content-Transfer-Encoding:Content-Type:MIME-Version: Reply-To:Message-ID:Subject:To:From:Date:Sender:Cc:Content-ID: Content-Description:In-Reply-To:References; bh=y+Na+aszlCp8mAbki4keVtJE6mBOuhVwocA1IRtr8eY=; b=ixDFFuxwfQgmy8BtfToCyyZS88 fC+WjJwTr8fngWhT8aHbokm7vmUVAyNvtifyTdIEW31YxxUdaCgVP7RPInkVt6nVN3JVcJ6cC7cNl xR3SsHxXTK6Pq8BOAOCa8xEbEG+DMEvDO+AALLDI1KjoGizAyJ8FjoMT6+n3ar1BD9L/31rryKDs9 YHzJx8qDo1agknz0UJhczJDLeCvVrc/jWMFNdVVhxOCJgfIlk15J75yS7J0fb3Z+rMFym9qIzBI2S +DR7jD74SN0QQkvoTBux+OAkJVdmA93lgr/aNzjpHm59Vm4nEIE+hvBD+0Y2XXbhncxG9+yRtJ7ph n/IhPpTA==; Received: from [62.216.210.102] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1tofsy-00HSNj-Ua for freebsd-current@freebsd.org; Sun, 02 Mar 2025 10:45:25 +0100 Received: from localhost.my.domain (c720-1400094 [127.0.0.1]) by localhost.unixarea.de (8.17.1/8.14.9) with ESMTP id 5229jOBL004066 for ; Sun, 2 Mar 2025 10:45:24 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.17.1/8.14.9/Submit) id 5229jOqS004065 for freebsd-current@freebsd.org; Sun, 2 Mar 2025 10:45:24 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Sun, 2 Mar 2025 10:45:24 +0100 From: Matthias Apitz To: freebsd-current@freebsd.org Subject: No working interface bce0 after updating to CURRENT of March 1 Message-ID: Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: FreeBSD 14.0-CURRENT r1400094 (amd64) X-message-flag: Mails in HTML will not be read! Please, only plain text. X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 62.216.210.102 X-Spamd-Result: default: False [-0.73 / 15.00]; RBL_SENDERSCORE_REPUT_5(1.50)[178.254.4.101:from]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_SHORT(-1.00)[-0.996]; NEURAL_HAM_LONG(-0.63)[-0.631]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_IN_DNSWL_LOW(-0.10)[178.254.4.101:from]; BAD_REP_POLICIES(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_DKIM_ALLOW(0.00)[unixarea.de:s=blu3434000]; RCVD_COUNT_THREE(0.00)[3]; SUSPICIOUS_AUTH_ORIGIN(0.00)[]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[unixarea.de]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[unixarea.de:+]; HAS_XAW(0.00)[]; MISSING_XM_UA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_REPLYTO(0.00)[guru@unixarea.de]; HAS_XOIP(0.00)[]; R_SPF_ALLOW(0.00)[+ip4:178.254.4.101]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:42730, ipnet:178.254.0.0/19, country:DE]; RCVD_VIA_SMTP_AUTH(0.00)[]; REPLYTO_EQ_FROM(0.00)[] X-Rspamd-Queue-Id: 4Z5H9z2n9Zz3Gnc X-Spamd-Bar: / Hello, Last night I updated a server from a 14.0-CURRENT amd64 1400094 #2 main-n264568-1d7ffb373c9d-dirty: Wed Sep 6 07:13:22 CEST 2023 to the CURRENT of March 1, 2025. All went fine. # git clone https://git.freebsd.org/src.git /usr/src # cd /usr/src # make -j8 buildworld ... --- buildworld_epilogue --- -------------------------------------------------------------- >>> World build completed on Sat Mar 1 23:13:55 CET 2025 >>> World built in 12817 seconds, ncpu: 8, make -j8 # make -j8 buildkernel ... -------------------------------------------------------------- >>> Kernel build for GENERIC completed on Sun Mar 2 01:13:25 CET 2025 -------------------------------------------------------------- >>> Kernel(s) GENERIC built in 769 seconds, ncpu: 8, make -j8 This morning I ssh'ed into the server, installed the kernel and world the usual way and now the bce0 interface (connected via RJ-45 with my router) does not work anymore. I'm clueless. The data and logs are from the server, transfered via an USB gadget: Mar 2 07:27:17 jet kernel: bce0: mem 0xc0000000-0xc1ffffff irq 16 at device 0.0 on pci2 Mar 2 07:27:17 jet kernel: miibus0: on bce0 Mar 2 07:27:17 jet kernel: bce0: Using defaults for TSO: 65518/35/2048 Mar 2 07:27:17 jet kernel: bce0: Ethernet address: d4:ae:52:bf:79:cc Mar 2 07:27:17 jet kernel: bce0: ASIC (0x57092008); Mar 2 07:27:17 jet kernel: bce0: link state changed to DOWN Mar 2 07:27:19 jet kernel: bce0: Gigabit link up! Mar 2 07:27:19 jet kernel: bce0: link state changed to UP Mar 2 07:27:19 jet kernel: bce0: Gigabit link up! First boot after install kernel and world: Mar 2 08:49:53 jet kernel: bce0: mem 0xc0000000-0xc1ffffff irq 16 at device 0.0 on pci2 Mar 2 08:49:53 jet kernel: miibus0: on bce0 Mar 2 08:49:53 jet kernel: bce0: Using defaults for TSO: 65518/35/2048 Mar 2 08:49:53 jet kernel: bce0: Ethernet address: d4:ae:52:bf:79:cc Mar 2 08:49:53 jet kernel: bce0: ASIC (0x57092008); Mar 2 08:49:53 jet kernel: bce0: link state changed to DOWN Mar 2 08:49:55 jet kernel: bce0: Gigabit link up! Mar 2 08:49:55 jet kernel: bce0: link state changed to UP Mar 2 08:49:55 jet kernel: bce0: Gigabit link up! Mar 2 08:56:08 jet kernel: bce0: link state changed to DOWN Mar 2 08:56:17 jet kernel: bce0: Gigabit link up! Mar 2 08:56:17 jet kernel: bce0: link state changed to UP Mar 2 08:57:17 jet kernel: bce0: link state changed to DOWN Mar 2 08:57:33 jet kernel: bce0: Gigabit link up! Mar 2 08:57:33 jet kernel: bce0: link state changed to UP Mar 2 08:57:56 jet kernel: bce0: link state changed to DOWN Mar 2 08:58:00 jet kernel: bce0: Gigabit link up! Mar 2 08:58:00 jet kernel: bce0: link state changed to UP A test with DHCP, the interface gets an IP addr assigned, i.e. the RJ-45 cable is fine (was fine and connected for years): Mar 2 09:05:49 jet dhclient[1613]: New IP Address (bce0): 192.168.178.31 Mar 2 09:05:49 jet dhclient[1617]: New Subnet Mask (bce0): 255.255.255.0 Mar 2 09:05:49 jet dhclient[1621]: New Broadcast Address (bce0): 192.168.178.255 Mar 2 09:05:49 jet dhclient[1625]: New Routers (bce0): 192.168.178.1 reboot, the interface gets the IP addr from /etc/rc.conf: # ifcpnfig bce0 bce0: flags=1008843 metric 0 mtu 1500 options=c01bb ether d4:ae:52:bf:79:cc inet 192.168.178.5 netmask 0xffffff00 broadcast 192.168.178.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 # netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default 192.168.178.1 UGS bce0 127.0.0.1 link#3 UH lo0 192.168.178.0/24 link#2 U bce1 192.168.178.5 link#3 UHS lo0 192.168.178.6 link#3 UHS lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 link#3 URS lo0 ::1 link#3 UHS lo0 ::ffff:0.0.0.0/96 link#3 URS lo0 fe80::%lo0/10 link#3 URS lo0 fe80::%lo0/64 link#3 U lo0 fe80::1%lo0 link#3 UHS lo0 ff02::/16 link#3 URS lo0 Pinging the gateway 192.168.178.1 gives: PING 192.168.178.1 (192.168.178.1): 56 data bytes --- 192.168.178.1 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host PING 192.168.178.1 (192.168.178.1): 56 data bytes --- 192.168.178.1 ping statistics --- 6 packets transmitted, 0 packets received, 100.0% packet loss In the admin interface of the router the server shows up as not connected. IP-Adresse: 192.168.178.1 ----(disconnected) --- jet What can I check and do? Thanks matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From nobody Sun Mar 2 13:04:30 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z5Mbm1R8kz5pJMf for ; Sun, 02 Mar 2025 13:04:36 +0000 (UTC) (envelope-from drsnx60@gmail.com) Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z5Mbl1Nx1z3JGD for ; Sun, 02 Mar 2025 13:04:35 +0000 (UTC) (envelope-from drsnx60@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=aaqXNrkP; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of drsnx60@gmail.com designates 2a00:1450:4864:20::22d as permitted sender) smtp.mailfrom=drsnx60@gmail.com Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-3061513d353so37428341fa.2 for ; Sun, 02 Mar 2025 05:04:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740920673; x=1741525473; darn=freebsd.org; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=9c9PbQgbVaydAwPuSnmSWW/66vnVUzRWwmTEmfdnxjY=; b=aaqXNrkPfyKVUFD0ZEhWQDdlPqRstKm3Vf0uXtrVqH7LmIr06inlWXHv670RfHMA9B ao+KSq9Vio9PEbwO0o6PWxUbLThlP+ePsZ+SqVkliR9Wc8kLHenQy7NVVCextE2GRFIh 7gm0076MV6050J7Sx9bBFFtdbY26ZgP1GzodfvkLIc57qdnyr6F8w4sW0raBWn5J1mzj FFltTUosT148NOkWi28NpzS9eKFxdfWDOGKBJR45hr3ENJFyP1MZDAYUasQ4FcNkmNcC 0Jdr4n+QVYxdt60hpBvI4H2LHatfyOUC0vSY/NxWV5EYaDhpfUgrQA8ZpfCa8xmSIww0 fTpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740920673; x=1741525473; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=9c9PbQgbVaydAwPuSnmSWW/66vnVUzRWwmTEmfdnxjY=; b=P78Ns/2UxzYFb4y2SLQy3vDHcgtwjSVka1aox4B+wuwzNh+m9ZNJfmw1LE4iKNVPtS oPqXpJfP9zhi9+BkH4j/6tuZXubw14geEBOBKEuAe/BKM1b8XNjMCfs3AGcLvf5esE2S i3dfSFFLpc36QGZT7qLdKlVim/qA0IHM0FdQfJkTxOnLHGGywz4ouniIPvP+t8PGnhYU 4BOyUMZXfzWDg1Wv/nHm9dVaRGsUBW8sDXGQQILHP7G/rfVGv7RE2yMucYI5jFyKcDGv TkfSFHf3M6rxDeeiqiKlMwIGRFsi9gnzqum7kOx/SXB/ZJ23tS1sQB5+s+tTy6MgN9m8 CFuQ== X-Gm-Message-State: AOJu0Yz97Snpz2XV8WQlQ4uS/PBTwygtKMfRaRTyHGwEOxHVep7XYhqn hwC9bHJTzKzEqG/i1NnfnEJGzCuNLLkIIXMIjIH390mVZl0UwHYi70ObbA== X-Gm-Gg: ASbGncszsDXNeSd9K1w00vlEx46R3u3ZpV12gu2oJ1qgzq7I0AFL7Bk97bfECw1xWI0 7X/oEjjmQvf+HoPFwBhLNpJmW+MhedC/i/1aMKKey8VRg8Jhux1zvE7C2pZG0rLR1uahxTVdP+t UXx+zD5JrY+/9ZodqWe4Wb40PWlgBN2I1v0GfPfd2YWp5KNkYEvNV2ZyGB8ofI5kdXLEoiX8vjU HjNu8CifBd2AF9SIwSmn1ZFuRVFse1EkRcXb/b+3HJ/GfCYr6kRiwxADUsK/4R1wf2sy0wN1VGU GLd43i1KvKnoBUVkhneJwIwN7tNfsM5Po0i8ovJ5uJr557BTGiJf4R1sSs5W/id9V7lE8SpZgv8 = X-Google-Smtp-Source: AGHT+IFxJKiW7EboIVDeQartL65n2q+05575CZHXx1XDMQsRF223g5lXGErR5fotmKva1R/77JpX0g== X-Received: by 2002:a05:6512:2213:b0:549:5c5f:c0c0 with SMTP id 2adb3069b0e04-5495c5fc3e3mr1934884e87.41.1740920673020; Sun, 02 Mar 2025 05:04:33 -0800 (PST) Received: from [192.168.0.234] (c83-254-16-48.bredband.tele2.se. [83.254.16.48]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-549515bf916sm701557e87.94.2025.03.02.05.04.31 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 02 Mar 2025 05:04:32 -0800 (PST) Content-Type: multipart/alternative; boundary="------------ljgOXk8q0Rso0XHQeZNYOiCH" Message-ID: <1c2ef378-ef05-4bf7-989e-11ca28668f41@gmail.com> Date: Sun, 2 Mar 2025 14:04:30 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: No working interface bce0 after updating to CURRENT of March 1 To: freebsd-current@freebsd.org References: Content-Language: en-US From: Lars Tunkrans In-Reply-To: X-Spamd-Result: default: False [0.76 / 15.00]; NEURAL_SPAM_LONG(0.99)[0.988]; NEURAL_SPAM_MEDIUM(0.98)[0.984]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.21)[-0.212]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::22d:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4Z5Mbl1Nx1z3JGD X-Spamd-Bar: / This is a multi-part message in MIME format. --------------ljgOXk8q0Rso0XHQeZNYOiCH Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi You wrote : ---------------------------------- # netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default 192.168.178.1 UGS*bce0* 127.0.0.1 link#3 UH lo0 192.168.178.0/24 link#2 U*bce1* --------------------------------------------- bce1 is not bce0 your HOST and the Gateway are connected to two different interfaces. This explains why there is no connection.      but  not  why  this   issue  occurred .            //Lars --------------ljgOXk8q0Rso0XHQeZNYOiCH Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 
   Hi  

    You  wrote  : 
----------------------------------

# netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags         Netif Expire
default            192.168.178.1      UGS            bce0
127.0.0.1          link#3             UH              lo0
192.168.178.0/24   link#2             U              bce1

---------------------------------------------


   bce1   is not  bce0   

   your HOST  and  the   Gateway    are  connected to two  different  interfaces. 
   This  explains why  there  is  no  connection.

     but  not  why  this   issue  occurred .

           //Lars 

 

--------------ljgOXk8q0Rso0XHQeZNYOiCH-- From nobody Sun Mar 2 13:09:49 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z5Mjs3bHzz5pKH8 for ; Sun, 02 Mar 2025 13:09:53 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z5Mjq5H61z3L6t for ; Sun, 02 Mar 2025 13:09:51 +0000 (UTC) (envelope-from guru@unixarea.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unixarea.de header.s=blu3434000 header.b=YlE65bxE; dmarc=none; spf=pass (mx1.freebsd.org: domain of guru@unixarea.de designates 178.254.4.101 as permitted sender) smtp.mailfrom=guru@unixarea.de DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=unixarea.de ; s=blu3434000; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Reply-To:Message-ID:Subject:To:From:Date:Sender:Cc: Content-ID:Content-Description; bh=suD89IrGPg4b4YAlmgw5abA9ko0RC4F4Ac3HFfEpq1Q=; b=YlE65bxE8LGONGTVF3+joI5Y6x f84Ed47j+jFzmMFNeOShruA8sU0GuZ1x0mzIaq0ctlzPwSs52OeGkaq+7cStIY4muisaywZb+Lswl 0Tvlg6s1eRp0DWpSgtikwDRKRX0IxA0eqVI4n3imMeg1UqCcdaqz/xPJXP11l/TubNbNy+RLM+PUp LzsGceZEpfmBqyyJujvBg+tumhlK8+PlomLs1wVy7NXBnQnrUhgBLlCXWQM1kS+3f/sVAaQsji/CA Mqr2mIhc0+m90iVOrrjnni/j4mdu0fILGLZ1YvY0pInrL9otukfVAuFIvm3GfbEn4vHpf2DCwSEw6 Hi3RJYjA==; Received: from [80.130.223.153] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1toj4o-007eud-2d for freebsd-current@freebsd.org; Sun, 02 Mar 2025 14:09:50 +0100 Received: from c720-1400094.speedport.ip (c720-1400094 [127.0.0.1]) by localhost.unixarea.de (8.17.1/8.14.9) with ESMTP id 522D9nwk005123 for ; Sun, 2 Mar 2025 14:09:49 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by c720-1400094.speedport.ip (8.17.1/8.14.9/Submit) id 522D9nke005122 for freebsd-current@freebsd.org; Sun, 2 Mar 2025 14:09:49 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: c720-1400094.speedport.ip: guru set sender to guru@unixarea.de using -f Date: Sun, 2 Mar 2025 14:09:49 +0100 From: Matthias Apitz To: freebsd-current@freebsd.org Subject: Re: No working interface bce0 after updating to CURRENT of March 1 Message-ID: Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 14.0-CURRENT r1400094 (amd64) X-message-flag: Mails in HTML will not be read! Please, only plain text. X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 80.130.223.153 X-Spamd-Result: default: False [-0.80 / 15.00]; RBL_SENDERSCORE_REPUT_5(1.50)[178.254.4.101:from]; NEURAL_HAM_SHORT(-0.99)[-0.992]; NEURAL_HAM_LONG(-0.93)[-0.928]; NEURAL_HAM_MEDIUM(-0.78)[-0.783]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_IN_DNSWL_LOW(-0.10)[178.254.4.101:from]; BAD_REP_POLICIES(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_DKIM_ALLOW(0.00)[unixarea.de:s=blu3434000]; RCVD_COUNT_THREE(0.00)[3]; SUSPICIOUS_AUTH_ORIGIN(0.00)[]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[unixarea.de]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[unixarea.de:+]; HAS_XAW(0.00)[]; MISSING_XM_UA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_REPLYTO(0.00)[guru@unixarea.de]; HAS_XOIP(0.00)[]; R_SPF_ALLOW(0.00)[+ip4:178.254.4.101]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:42730, ipnet:178.254.0.0/19, country:DE]; RCVD_VIA_SMTP_AUTH(0.00)[]; REPLYTO_EQ_FROM(0.00)[] X-Rspamd-Queue-Id: 4Z5Mjq5H61z3L6t X-Spamd-Bar: / I had a wild guess and plug'ed in the RJ-45 into the server's 2nd port, modified /etc/rc.conf, booted and all was fine: $ ssh 192.168.178.5 $ uname -a FreeBSD jet 15.0-CURRENT FreeBSD 15.0-CURRENT #0 main-n275738-7ee310c80ea7: Sun Mar 2 01:13:00 CET 2025 guru@jet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 /etc/rc.conf: # ifconfig_bce0="inet 192.168.178.5 netmask 255.255.255.0" ifconfig_bce1="inet 192.168.178.5 netmask 255.255.255.0" defaultrouter="192.168.178.1" $ netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default 192.168.178.1 UGS bce1 127.0.0.1 link#3 UH lo0 192.168.178.0/24 link#2 U bce1 192.168.178.5 link#3 UHS lo0 ... $ ifconfig bce0 bce0: flags=8802 metric 0 mtu 1500 options=c01bb ether d4:ae:52:bf:79:cc media: Ethernet autoselect nd6 options=29 $ ifconfig bce1 bce1: flags=1008843 metric 0 mtu 1500 options=c01bb ether d4:ae:52:bf:79:cd inet 192.168.178.5 netmask 0xffffff00 broadcast 192.168.178.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 If I compare the ifconfig-values of the not working bce0 (see below) and now bce1, there is no difference. It is somewhat magic, that bce0 stopped working after the first boot of the new kernel. matthias El día domingo, marzo 02, 2025 a las 10:45:24a. m. +0100, Matthias Apitz escribió: > Hello, > > > Last night I updated a server from a > > 14.0-CURRENT amd64 1400094 #2 main-n264568-1d7ffb373c9d-dirty: Wed Sep 6 07:13:22 CEST 2023 > > to the CURRENT of March 1, 2025. > All went fine. > > # git clone https://git.freebsd.org/src.git /usr/src > > # cd /usr/src > # make -j8 buildworld > ... > --- buildworld_epilogue --- > > -------------------------------------------------------------- > >>> World build completed on Sat Mar 1 23:13:55 CET 2025 > >>> World built in 12817 seconds, ncpu: 8, make -j8 > > > # make -j8 buildkernel > ... > -------------------------------------------------------------- > >>> Kernel build for GENERIC completed on Sun Mar 2 01:13:25 CET 2025 > -------------------------------------------------------------- > >>> Kernel(s) GENERIC built in 769 seconds, ncpu: 8, make -j8 > > > This morning I ssh'ed into the server, installed the kernel and world the usual way > and now the bce0 interface (connected via RJ-45 with my router) does > not work anymore. I'm clueless. > > The data and logs are from the server, transfered via an USB gadget: > > Mar 2 07:27:17 jet kernel: bce0: mem 0xc0000000-0xc1ffffff irq 16 at device 0.0 on pci2 > Mar 2 07:27:17 jet kernel: miibus0: on bce0 > Mar 2 07:27:17 jet kernel: bce0: Using defaults for TSO: 65518/35/2048 > Mar 2 07:27:17 jet kernel: bce0: Ethernet address: d4:ae:52:bf:79:cc > Mar 2 07:27:17 jet kernel: bce0: ASIC (0x57092008); > Mar 2 07:27:17 jet kernel: bce0: link state changed to DOWN > Mar 2 07:27:19 jet kernel: bce0: Gigabit link up! > Mar 2 07:27:19 jet kernel: bce0: link state changed to UP > Mar 2 07:27:19 jet kernel: bce0: Gigabit link up! > > First boot after install kernel and world: > > Mar 2 08:49:53 jet kernel: bce0: mem 0xc0000000-0xc1ffffff irq 16 at device 0.0 on pci2 > Mar 2 08:49:53 jet kernel: miibus0: on bce0 > Mar 2 08:49:53 jet kernel: bce0: Using defaults for TSO: 65518/35/2048 > Mar 2 08:49:53 jet kernel: bce0: Ethernet address: d4:ae:52:bf:79:cc > Mar 2 08:49:53 jet kernel: bce0: ASIC (0x57092008); > Mar 2 08:49:53 jet kernel: bce0: link state changed to DOWN > Mar 2 08:49:55 jet kernel: bce0: Gigabit link up! > Mar 2 08:49:55 jet kernel: bce0: link state changed to UP > Mar 2 08:49:55 jet kernel: bce0: Gigabit link up! > Mar 2 08:56:08 jet kernel: bce0: link state changed to DOWN > Mar 2 08:56:17 jet kernel: bce0: Gigabit link up! > Mar 2 08:56:17 jet kernel: bce0: link state changed to UP > Mar 2 08:57:17 jet kernel: bce0: link state changed to DOWN > Mar 2 08:57:33 jet kernel: bce0: Gigabit link up! > Mar 2 08:57:33 jet kernel: bce0: link state changed to UP > Mar 2 08:57:56 jet kernel: bce0: link state changed to DOWN > Mar 2 08:58:00 jet kernel: bce0: Gigabit link up! > Mar 2 08:58:00 jet kernel: bce0: link state changed to UP > > A test with DHCP, the interface gets an IP addr assigned, i.e. the > RJ-45 cable is fine (was fine and connected for years): > > Mar 2 09:05:49 jet dhclient[1613]: New IP Address (bce0): 192.168.178.31 > Mar 2 09:05:49 jet dhclient[1617]: New Subnet Mask (bce0): 255.255.255.0 > Mar 2 09:05:49 jet dhclient[1621]: New Broadcast Address (bce0): 192.168.178.255 > Mar 2 09:05:49 jet dhclient[1625]: New Routers (bce0): 192.168.178.1 > > reboot, the interface gets the IP addr from /etc/rc.conf: > > # ifcpnfig bce0 > bce0: flags=1008843 metric 0 mtu 1500 > options=c01bb > ether d4:ae:52:bf:79:cc > inet 192.168.178.5 netmask 0xffffff00 broadcast 192.168.178.255 > media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=29 > > # netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Netif Expire > default 192.168.178.1 UGS bce0 > 127.0.0.1 link#3 UH lo0 > 192.168.178.0/24 link#2 U bce1 > 192.168.178.5 link#3 UHS lo0 > 192.168.178.6 link#3 UHS lo0 > > Internet6: > Destination Gateway Flags Netif Expire > ::/96 link#3 URS lo0 > ::1 link#3 UHS lo0 > ::ffff:0.0.0.0/96 link#3 URS lo0 > fe80::%lo0/10 link#3 URS lo0 > fe80::%lo0/64 link#3 U lo0 > fe80::1%lo0 link#3 UHS lo0 > ff02::/16 link#3 URS lo0 > > Pinging the gateway 192.168.178.1 gives: > > PING 192.168.178.1 (192.168.178.1): 56 data bytes > > --- 192.168.178.1 ping statistics --- > 3 packets transmitted, 0 packets received, 100.0% packet loss > ping: sendto: No route to host > ping: sendto: No route to host > ping: sendto: No route to host > ping: sendto: No route to host > ping: sendto: No route to host > ping: sendto: No route to host > PING 192.168.178.1 (192.168.178.1): 56 data bytes > > --- 192.168.178.1 ping statistics --- > 6 packets transmitted, 0 packets received, 100.0% packet loss > > In the admin interface of the router the server shows up as not > connected. > > IP-Adresse: 192.168.178.1 ----(disconnected) --- jet > > What can I check and do? Thanks > > matthias > > > -- > Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub