From nobody Mon Jan 27 04:51:41 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 4YhGH04MmJz5mCR3 for ; Mon, 27 Jan 2025 04:51:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) (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 4YhGH02Wtdz4NbW; Mon, 27 Jan 2025 04:51:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-f45.google.com with SMTP id 2adb3069b0e04-5401bd6cdb4so4402868e87.2; Sun, 26 Jan 2025 20:51:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737953514; x=1738558314; 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=7kubJQUWKpLTrLDzcQkMbjLX6lr1PFQ2iFMMeB33QkE=; b=q7GqwDh7uZkAY7qZMyaOsL5q3SmID91fZlVVUUYCLXc/yvNJ9/itcsusAy3HJdFTqi 39aDa/+Upym/w7AsY+iZPnZ6QL0l9x1j0uPy1Ds31eUPaM4YT5wkGZx3bXZk04+KPkt/ ieHhQ4g98Da52m3zSqWKKZFnjtyE3w040YJKhgUg7OZivkfXjhMzQO5Eoc5vjQxQvuW7 nCyNiaVG81f8AIeHu2DS3Ursg7TL6vch3LjlqcDuZhS3MZ+OvAnCI6M1hxAsFmO5/zhg IwcmGaplPXYZV5Jg432O0LktKSTUAs+Pwa4h9r160UIHVsuvUFjkRLWGd/xwX9uWE7Wo D6ag== X-Forwarded-Encrypted: i=1; AJvYcCU6XkPcfz3wjAWoq+iL426KDpThjF2RPT2E30nmwU8Yy1PavzbWuu8OWnV8omaXuZi6W7KsWQ==@freebsd.org, AJvYcCUolsubJPOCIIxQKp91KpmcAGSk6chETMNcQoHPfxQ4KmV7CcPa/SdQ55oe4No+erW/iZtRFktENe7U6mzqtiQ=@freebsd.org X-Gm-Message-State: AOJu0YyKoparjnIHHwhy5bFINKnHQAz7lwA8wdLrNfnaiSm/nsJtVShA h/XSpKYsT5oAZaUfB1fokZDhUHTBw3GqyEnoJ+DU4n4++sJ8XRxud6wkjG66h3py5dP79DLsEie eb4pSD2VPxG7n/VvfvHEoz2AqfVg= X-Gm-Gg: ASbGnctpkQ+b7rJmBxp55y2r4yCkGbJ8UC2R9/4bmgCdGlq73vaZMA2vhBXhLV4GM5Z 2vm3TW0izA7nZY7BNuYykPc2UmKUZ23S0BYOZJ9t3Mi4RKs/4c9IJ4zX1gz75mbA= X-Google-Smtp-Source: AGHT+IEbEjlnjo9si8xQniYxAg5d9UVSNd4BDrXS10tz4UMBgFE/CX/IQG1d6GqFVjJtEHU0j8mOQMjYUzzCeJFIDhM= X-Received: by 2002:a05:6512:3b09:b0:542:2f0f:66d9 with SMTP id 2adb3069b0e04-5439c246297mr16126141e87.16.1737953513896; Sun, 26 Jan 2025 20:51:53 -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: <978176f7-270c-4603-b80a-e29c3b1b4b73@FreeBSD.org> <4FC807EC-10DD-49FD-AACE-9026B4925923@yahoo.com> <1B14894C-78E3-4696-9E4F-FBA97A356BF1@yahoo.com> In-Reply-To: <1B14894C-78E3-4696-9E4F-FBA97A356BF1@yahoo.com> From: Adrian Chadd Date: Sun, 26 Jan 2025 20:51:41 -0800 X-Gm-Features: AWEUYZmc2Fc68_tpq0Wr4iaj-QGIo49nvRxL8smvFAi4fkVbvecdDLldHxc1KbE Message-ID: Subject: Re: "don't know how to make /usr/main-src/sys/contrib/dev/iwm/iwm-3160-17.fw.uu. Stop" To: Mark Millard Cc: Stefan Esser , Emmanuel Vadot , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000d507a8062ca8d5c1" X-Rspamd-Queue-Id: 4YhGH02Wtdz4NbW X-Spamd-Bar: ---- 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_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] --000000000000d507a8062ca8d5c1 Content-Type: text/plain; charset="UTF-8" Hi! So, there's no longer a build target for the firmware uuencoded files -> kernel module. Being able to build iwm in the kernel rather than a module is broken. Now, the real issue(s) are that iwm needs firmware to initialise, and the firmware needs to exist, and thus it needs access to the rootfs for firmware_get() to find the now binary files in /boot/firmware instead of the kernel module old way, and that whole pipeline is broken if it's loaded at boot time or included in the kernel directly. There isn't a nice way to defer the firmware load attempt until /after/ rootfs is up. -adrian --000000000000d507a8062ca8d5c1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

=
Hi!

So, there's no longer a build t= arget for the firmware uuencoded files -> kernel module.

<= /div>
Being able to build iwm in the kernel rather than a module is bro= ken.

Now, the real issue(s) are that iwm needs fir= mware to initialise, and the firmware needs to exist, and thus it needs acc= ess to the rootfs for firmware_get() to find the now binary files in /boot/= firmware instead of the kernel module old way, and that whole pipeline is b= roken if it's loaded at boot time or included in the kernel directly. T= here isn't a nice way to defer the firmware load attempt until /after/ = rootfs is up.




-adrian

=C2=A0
--000000000000d507a8062ca8d5c1-- From nobody Mon Jan 27 04:55: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 4YhGLt4xD2z5mChv for ; Mon, 27 Jan 2025 04:55:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) (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 4YhGLs5zHDz4QWy; Mon, 27 Jan 2025 04:55:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of adrian.chadd@gmail.com designates 209.85.167.52 as permitted sender) smtp.mailfrom=adrian.chadd@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-lf1-f52.google.com with SMTP id 2adb3069b0e04-54024ecc33dso4071139e87.0; Sun, 26 Jan 2025 20:55:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737953716; x=1738558516; 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=25iQBlr3U/2QH5HgMLwvWYV/I3go+oXLfKpd3cVnQsw=; b=wOQpTAUCiLiy86DTwnlzfUMAQ2Hs5/LUvrjjkBdpxK5pp/Z9FQAY4TpbnP6IYubcbQ vcz9cmBYGyHjfoIZXyw1OaWSkMClcZHzCXVCuGfCLdWTwyk6hNS6FUdUPuLNOKJwCgNX h22azrFyFSM7mVDdORNLjIA4efN1isJm00AYtjVO59lUCjovwOaFqJ4vnuCyIExns2i9 NmARK8cDbEyaOehUxvlwMJa4nMDXVWQXRjousKLIU4izuuF9T+/iHjpxZmRvx9oIDhPN UD71UPNk0YdpuhSFITtQ8qhewOmzYArligE7zX9zs6gFthrydu0tXuhuxsauE4tFfCUT PMdg== X-Forwarded-Encrypted: i=1; AJvYcCVVt6Q3nKrwqj+xuCTOl7hgR2+eNWyUxl2WH8ruwOqGYCAflM881WnG8hkxWb+jUM0nuQ==@freebsd.org, AJvYcCW39OZCwTdQCtoqUJbpiFtPQ+JnxDIzFiH58Ntqks2xOSFtc6Ufp+XAjWzJ24nCcJ7alKv4RqZ7c2Kj51iASlRX@freebsd.org X-Gm-Message-State: AOJu0YzQQJWPVDnC/A0lV6TYaQQ+z+q/NrISOEeR8Z8uaHAMg5bZlNGm n6bugtdbZLFMxP76THFryi2orQTKIlzwYczuShCI5VF06GtTudLnd7878SdiBaPK0Z3MtXwtVfH V/X1KYWaljiy8A+ss+fPbOKzQCVg0gA== X-Gm-Gg: ASbGncvDUQDERvA7DZf7uGg+yOeRZtfyVOhtYYGCcFexiA6F40TxBdAGtj9msR13HWc H6I/tYgYybfoJjDDpgDgpsJhr8zMAF3jpm7MXDBZG0KN2ZQfnmC4hb0aY4XnLH2E= X-Google-Smtp-Source: AGHT+IGWhvtsiyAvk0qmbsaKViEKSUDCqQ4tjNvYmTRsix7j3MoLf2pd/zJiEZJft3wR1sWsTV/kLRD3qbFrsWfofk4= X-Received: by 2002:a05:6512:3b9d:b0:540:1be6:f15f with SMTP id 2adb3069b0e04-5439c1bfd49mr14840464e87.0.1737953714541; Sun, 26 Jan 2025 20:55:14 -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: <617a15f6-c3cc-4d56-902f-03ae084c5cd5@app.fastmail.com> In-Reply-To: From: Adrian Chadd Date: Sun, 26 Jan 2025 20:55:01 -0800 X-Gm-Features: AWEUYZl959FkA-lrCXju9MtFqZ3V_y7WPfgiWb3ot-xCKxIoHFlHFWi-nVhbC-M Message-ID: Subject: Re: WIFI compiling error: Can anyone fix it on main branch? To: "Chen, Alvin W" , "Bjoern A. Zeeb" Cc: Dave Cottlehuber , freebsd-current Content-Type: multipart/alternative; boundary="000000000000caa1a5062ca8e17c" X-Spamd-Result: default: False [-0.23 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-0.80)[-0.798]; NEURAL_HAM_SHORT(-0.78)[-0.780]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; NEURAL_SPAM_LONG(0.25)[0.249]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_ALL(0.00)[]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_THREE(0.00)[4]; RCVD_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; MISSING_XM_UA(0.00)[]; R_DKIM_NA(0.00)[]; RBL_SENDERSCORE_REPUT_8(0.00)[209.85.167.52:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.52:from]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.52:from] X-Spamd-Bar: / X-Rspamd-Queue-Id: 4YhGLs5zHDz4QWy --000000000000caa1a5062ca8e17c Content-Type: text/plain; charset="UTF-8" Hi, I'm sorry i only just saw this. is it still broken? I'm cc'ing bz@ as it looks like it's in the linuxkpi stuff. -adrian On Tue, 14 Jan 2025 at 22:10, Chen, Alvin W wrote: > For my case, It is due to different default compiling options for > different clang versions as I build it on FreeBSD 14.0 ENV. > > Please check the attached discussing thread. > > The macros defined for auto pointer free borrowed from Linux kernel would > be improved. > > > > Internal Use - Confidential > > *From:* Adrian Chadd > *Sent:* Wednesday, January 15, 2025 4:55 AM > *To:* Dave Cottlehuber > *Cc:* Chen, Alvin W ; freebsd-current < > freebsd-current@freebsd.org> > *Subject:* Re: WIFI compiling error: Can anyone fix it on main branch? > > > > [EXTERNAL EMAIL] > > I did temporarily break -head on some platforms for like 30 minutes like a > week ago? Is everything ok now? > > > > What was the error? > > > > -adrian > > > > > > On Tue, 7 Jan 2025 at 04:17, Dave Cottlehuber wrote: > > On Tue, 7 Jan 2025, at 09:39, Chen, Alvin W wrote: > > Thanks! > > > > Internal Use - Confidential > > Hi Alvin, > > Can you share your HEAD commit, & an error message? > > 749b3b2c0629 works fine on my machine, its current as of 2 hours ago. > > A+ > Dave > > --000000000000caa1a5062ca8e17c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi, I'm sorry i only just saw this.

is it still broken? I'm cc'ing bz@ as it looks like it's in th= e linuxkpi stuff.


-adrian


On Tue, 14 Jan 2025 at 22:10, Chen, Alvin = W <Weike.Chen@dell.com> wr= ote:

For my case, It is du= e to different default compiling options for different clang versions as I = build it on FreeBSD 14.0 ENV.

Please check the atta= ched discussing thread.

The macros defined fo= r auto pointer free borrowed from Linux kernel would be improved.

=C2=A0<= /span>


Internal Use - Confidential

From: Adrian Chadd <adrian@freebsd.org>
Sent: Wednesday, January 15, 2025 4:55 AM
To: Dave Cottlehuber <dch@skunkwerks.at>
Cc: Chen, Alvin W <Weike_Chen@Dell.com>; freebsd-current <<= a href=3D"mailto:freebsd-current@freebsd.org" target=3D"_blank">freebsd-cur= rent@freebsd.org>
Subject: Re: WIFI compiling error: Can anyone fix it on main branch?=

=C2=A0

[EXTERNAL EMAIL]

I did temporarily break -head on some platforms for = like 30 minutes like a week ago? Is everything ok now?

=C2=A0

What was the error?

=C2=A0

-adrian

=C2=A0

=C2=A0

On Tue, 7 Jan 2025 at 04:17, Dave Cottlehuber <dch@skunkwerks.at&= gt; wrote:

On Tue, 7 Jan 2025, at = 09:39, Chen, Alvin W wrote:
> Thanks!
>
> Internal Use - Confidential

Hi Alvin,

Can you share your HEAD commit, & an error message?

749b3b2c0629 works fine on my machine, its current as of 2 hours ago.

A+
Dave

--000000000000caa1a5062ca8e17c-- From nobody Mon Jan 27 09:01:16 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 4YhMpl3f6qz5mWQS for ; Mon, 27 Jan 2025 09:01:19 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YhMpl37K2z3Yfk; Mon, 27 Jan 2025 09:01:19 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1737968479; 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=a+R4UaKq5yS74iaI+xoQHDA7WsKciwDnmm0PLQkK7SU=; b=PdFRe5JseJrzEXRVwtYoFOphxfXEAx72JT/Tv4681N/A2tD1JiXrF6Lx/h6i7wlHEHPC29 lktGqbyKXRQtqJOKhXRbKQy6XKb+MZrbWuuPe6l6U7fmgq3pxDxymzhYNW/uvqf7fpBcIs MSnAbJrghuZRadmc2hDlmzrHfXJOJxAguiEmoMNW0stpezoHTlHPNl53F8BZpwzAvi5+fO of8AUTXeTJeaeMYSTuTpAfxxSXd7Vxc6uqvvwbYy2sFEEdLHK9G6lCs0I3PRIJ0rz+MjEZ ULpO7H7C4riFMd7evWeDiPi3azoS21zq/iqf1kA5Qsteox2Ta236++ShvlfwWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1737968479; 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=a+R4UaKq5yS74iaI+xoQHDA7WsKciwDnmm0PLQkK7SU=; b=pX1BLj/LcRnH/N+5r1JXplkM7jy+RIaOSRBPo+B4zRNikYDkje0fs/gq6eErT4FNkzc2N9 n6SmNgCarSIUv5g4IMrmJ/FsxDOxxCqzr3wlXUiU7Q2KrIp2SG+cTeONjWCeTqn3jMqHWv +YfPrXvNTXEMtPO8lHoE17xZjj4AuMKIuOk1OjXgzjBwH8VY3vbsghOwN5lGiQ+RNgBxRF 2J6vR0LZUp+PQOVDFI6sgcdO49k9B0KplIroWSMSSZknWgp+CDvouvsz3wSLyw872AzAiY rPaFlUg5k2aMLcnHlw1dVHsVHRpWaEBzYLfaRfYsb+Bn7m3PGeHVy8/2tadEkg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1737968479; a=rsa-sha256; cv=none; b=CSq0Wd/JqXHiQfxw2n7kiyNGYN+2dTjSuP86pmpq/sbbhgx6rFh/8WrWXm/A34+QgIOQ9a if5whbgZOW2w4PBBpmk2TWk1jp49qAxh6vuJqosRQ8zBQODoAIEB+AEC2SZJ8D94qMy/kY e+REykfD0TkWcUarNOojjEU/PwuSbBtRDHkF+PAKvIWRali1GHeefOCA89qwrPjv6IDQyb rTxaCSdcuIQT2jURwEIbgAjF3pkPNX6L1Xoa1u6LR/alzn1Qp/HgCr7bzvvhNWOsfkXQn5 N9r4vnYF9BI3NPLz15xVBPOCnemS6HHyKLMWanb6gvLSjLqh+eElVeCodfQKAA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YhMpk72xbz6x1; Mon, 27 Jan 2025 09:01:18 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Mon, 27 Jan 2025 01:01:16 -0800 From: Gleb Smirnoff To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: January 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 January 2025 stabilization week started with FreeBSD/main at main-n275044-c6767dc1f236, which was tagged as main-stabweek-2025-Jan. 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-Jan 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-Jan If you want to use only the official FreeBSD repo, then update to the revision: git pull git checkout c6767dc1f236 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 Jan 27 16:50:03 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 4YhZCy09qQz5lwcR for ; Mon, 27 Jan 2025 16:50:22 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-20.consmr.mail.gq1.yahoo.com (sonic317-20.consmr.mail.gq1.yahoo.com [98.137.66.146]) (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 4YhZCx4B7Jz3XDT for ; Mon, 27 Jan 2025 16:50:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1737996619; bh=nWcMCTzpYu6m7EK54DFTUtzR4Fg++UT5X6NZKpQIAFc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=X74CnqKovWqCFtf81urf651pW0rHAE/Ne/TrH08f6aySoQYHF8IcVJczzo8wYxgJ7tzm0/z/UKycINP9Bsz+tlaQ49ZRUrVaBLEWkuAT4EE3gOFUnn5WelJ7ozPyBIT+8LpF+HAlZXJrTwjOYynzvzJplj9tboEm0u2/IHOPbeR5aWuTGQt3s3fXZP4dP4/ALp3Nwl2bvc/LsgvAt0Khx/SocwvGGgVY0KJSIUsBUsC+AuIUKBfNn7qUmVp5MDz3mlZSPcfHTXjlI1fKQh8sxRH5oVwIqDAqqbu4s4TSy6Bvew1LvuJcWnWgQxMrJllen6o4XzV3tt8hn0Dbh9JDrw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1737996619; bh=8n7cblT4DCS6dVKRppbvrODdyy7pJJadcjrN4pnopd3=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=ei/UJ42TexmKswEggFRDutCtf/x+jt+MrxHJ/y0JKxvQ1R4vrbvmbtmbdt7mOOg69WE+x15p7haf1ggjCHOFWHzPaGP0fvbf/vaMAXQDNeSwqG7yP1Tjpof1EV+EOmSqyRBCaSsqe6JlhAxOSuvMEzYiaHtiSdQysCARA9xPbeKzns6O5zlFcpsTaT1e+nVwMap+u+FAdLePca8l2iQavUm2ni63fu9MJDVv/JeNqwFNGNVNmGyHTYk0UJq5SOD5TxRmURWlq00PkBwXblN1a/fYzGp/y1rn+mAxFnPE9cT+rMfU133bgZJHR4K780DH5NogjBJXTQ26z1R/1hubzQ== X-YMail-OSG: bpIBL2kVM1n_hPgf95Ir5gYAXZZuZgM6yiUj5HeIpM0wPIRQ95dCaAZ7iG1QzVo _dnYvtqq93gYrPkZFgHL4evYg41YibHvSe1AkdsQk2owNs6yG3WwdewbcMszqnwacJrqOWdiHyki djP_q9C5UU__cjYk2ZRWw75jE5AkWeDFH3czNpwsENH_du3shy9YcpsM5RZmnUFilVGXFjCHzppu pjOlRxyascsc9c_piaSPMl_pIT_rahFTq12hvTfRpVRcqELPV7qVEI8YxFkl8SXLRybTrpuqpw.M piQjlQ3RrdKJBxvpmyyZNM1XLZj0lRBbzBa75k1E5Rx2NXfC73S_1t3wyKkrquZdg4qhasCWKcBa wwoa1omTcwJxPc6kPV5wuV3BQChy0caiylns58RpXEMVOzNCfVEZaWKMqiGDddMeqCCem7Kh3DJz ysYrPFp5ILK8N57ovgQ9u0t0fBiBFmHtGQbi4HkdE126Md6h4obEeGRDhLST9zZVRR9DJFyP4OwO qRRwzeuromWNJtX4ilgpHjDVZzUCnBWVNVrfjAB6bxXc8XB77JtlTgpxCU7gH2AgzzKdIaT3SzQl JzaEE.BfHVpCgBzNVf2q5I3mZBwVFTVyotVxI7h3MkKPwpnhqZEgrLkn0RGa5ylqzxbVkiA6h1Dc 9biVPK7ZVW61BiPzjFM7xFnBK.nqWI10KAosGYEn2Wpk.3u5infMRKO3twy1Ar2KYGmfAfF9HOOY F3fT._.TBk4HHMAGOAp_NRyQV.OkyqgXwRR8_Jm44cobM4McarzjXqvDShAMqlbTl8nAbIWrx.o1 yURAfSR9hCUoZ8nqcd2Ci.SF7hQWsasmihLe21Ogs_C0iXf2XwE4A7wG.hHcZiySsipfMexPi42n RDznHJ_gg9wqK.bfHwhq61YV.1nS.WPTaIsH8gMsn9hfRlFsQHM1ITKXBFUi67qX1r5LUCm.6rz6 RZnA.8ppz0rQeUkY2ouXceyhoD.vKdAj_V585i5Hn4lcvgfiACnyNjPqSUK4OoP_Fq_fwb6CI0Zz u8KGgBIgNkHq2D9HRCHoE1AANHgXA_HVAjTfkN2snNnP2D6c.pannI3YHZ4PcjoHoV0qWwzbtSz9 OTtSFmuPFPSeSMSKbfpjNgzVNGsZaOaz7fSpLMR5ocSXPUvCGlEUdc5Ci8mjlF9J7e9QXhVOMUN5 U78Ot9rZErerWxy6CWPJ6l.TN5vtMuNJXo_04_gHjDUZtuQ1p2REBc8zgPazb2UHkw.ZrG6GUAhW oWnAN8QJbK5sCfwGfiOtX70tnbRYVHEHybEJtXcBMcTuizyMRtm0Nfe1oXH6tb60ONhhCcYWyPTY e_LFdImePtm_xodHvHY2oRrw.i1VQj1T6QSO3Rrt6iIASp70G2wA1E5dukYAAu7f9i2f0kNpL0c1 aC59qYcIwgnjOM1Z3mRgClMU92eAk_ve65j5mXHY3i9AYhqXNQ48eW9Z7yweYsYLAO.MVBhdhUfX FQDhnyUKM3fzXoVoDAmRdvb1p9Ay39_aUtaMbdIa_AldyS7UFOgnTLiU3VHadF8HDfOJ3IrvyVFj cnFOG.Qw17yFWD2fn1xPjiUbMznn1aH0V2elrhqmx7mbNu5F72aISa4XRh9lPzeK0G1cl63HEiAC afiQFSKqidLI3oY0bmH56Zx5eyn2VHGGcnZGKNt_WzdwseL72mEblRaxHwGGfhgiXLE84WZzVrlP HG2cQ3e_8z_ttqz9v8Hov1WTCtZtWkOAtmRgUPHoojseYDJY14eAQ9dlKxg.G0uuWK18Xuk2NwdQ st3Qv5yiQICStIpN3G6iROcYYyyO6f4SwIIdpwsoCcAvldA60PoCKtpiwPjFUmjxJKkxrSoXPGuA 3K15rnumxCUlnSJfhajKFa3BDXEXh1ZFAUEYsBdi7iAxtEH3qyCtnO5zWi3gyt1HcPhAryAWBIzc g.dSUnz56_M85GpeHYf3GRwz14ICzhiHqoJT595hFXN2_G9fKWWC7bkFYzOud9cASRoxzk9GHFHT 7fng95c4zRjWa9YLTXE6KO7ObAGRJns3gKO8GPTwjv8nBLnrjQcvceiohDBJpkwnM0HHpYPs79Lv NNFLaKrOc82xL.yco.Q3wRT_eB.G_E9jfPbXKxAsfZ9_MEKFgDQYdD.kK5Lnfk8lh8U4X7Xww41g kNi4.YrNQGZnyS28KkQwa2tH4Gb927SM6gf3OplkbKBfdWyijYA-- X-Sonic-MF: X-Sonic-ID: 31d82982-0ea4-486f-b618-a05573295a16 Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Mon, 27 Jan 2025 16:50:19 +0000 Received: by hermes--production-gq1-5dd4b47f46-zz6g6 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 459ef55e56b8846cbe73edd971cc077d; Mon, 27 Jan 2025 16:50:14 +0000 (UTC) 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 \(3826.300.87.4.3\)) Subject: Re: "don't know how to make /usr/main-src/sys/contrib/dev/iwm/iwm-3160-17.fw.uu. Stop" From: Mark Millard In-Reply-To: Date: Mon, 27 Jan 2025 08:50:03 -0800 Cc: Stefan Esser , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <978176f7-270c-4603-b80a-e29c3b1b4b73@FreeBSD.org> <4FC807EC-10DD-49FD-AACE-9026B4925923@yahoo.com> <1B14894C-78E3-4696-9E4F-FBA97A356BF1@yahoo.com> To: Adrian Chadd , Emmanuel Vadot X-Mailer: Apple Mail (2.3826.300.87.4.3) X-Rspamd-Queue-Id: 4YhZCx4B7Jz3XDT X-Spamd-Bar: ---- 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:36647, ipnet:98.137.64.0/20, country:US] On Jan 26, 2025, at 20:51, Adrian Chadd wrote: > Hi! Hello. > So, there's no longer a build target for the firmware uuencoded files = -> kernel module. Yea. But there are the sys/conf/files dependency lines in main that still list .fw.uu files. That includes a reference related to the error I get in my context unless I avoid "device iwmfw" in the kernel configuration: /. . ./sys/conf/files: dependency = "$S/contrib/dev/iwm/iwm-3160-17.fw.uu" \ It makes things look like the .fw.uu removal activity is still incomplete. > Being able to build iwm in the kernel rather than a module is broken. >=20 > Now, the real issue(s) are that iwm needs firmware to initialise, and = the firmware needs to exist, and thus it needs access to the rootfs for = firmware_get() to find the now binary files in /boot/firmware instead of = the kernel module old way, and that whole pipeline is broken if it's = loaded at boot time or included in the kernel directly. There isn't a = nice way to defer the firmware load attempt until /after/ rootfs is up. >=20 Yep. =20 =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Mon Jan 27 17:10: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 4YhZgT59Yjz5ly2b for ; Mon, 27 Jan 2025 17:10:45 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 4YhZgS6Dnfz3byv for ; Mon, 27 Jan 2025 17:10:44 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=PMZcyh3j; spf=pass (mx1.freebsd.org: domain of ianfreislich@gmail.com designates 2607:f8b0:4864:20::834 as permitted sender) smtp.mailfrom=ianfreislich@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qt1-x834.google.com with SMTP id d75a77b69052e-46785fbb949so45075121cf.3 for ; Mon, 27 Jan 2025 09:10:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737997844; x=1738602644; 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=na6ELqsrzkK6enCXwpaERXxh2CA6S2M5huu2yOQ2h+k=; b=PMZcyh3j1JphAi/t3rsU2aBpssWW8iEQX5S8sx87DNa/NAd1HxKEokYx51SzsV4ZIV V0asO4Zz36liDC1JsjbZLUsIz4GLKf00YAB9bNlzvUtAOSj+xXe7V916FDjw5CFgEsZH 7Vj4dmSTTpcrbabrZeKtxcwCa77JGupVpasli3Zv0OpjDZKS2tS647MvgzFeXUWPip+l nOsSIYvIdteF18ZOipxubs2u5xKgB2olaa+JVN8Jo91cYFdpxpnCZ3N0/baZzWka0m60 dLImDHWt7PSvW5CUrDF/qVyIKLlydMWAtXQKmcumJJEOLakO7aGUVvf+4h+5M1h48QIx Q2Hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737997844; x=1738602644; 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=na6ELqsrzkK6enCXwpaERXxh2CA6S2M5huu2yOQ2h+k=; b=nh6cHwj/e9kOAvyAjLznUWVGs/YQj1tONFANCXZdYzIW0jSM21jTupniEb/TjvyTlQ HLRawHYexycmH9QHoJJxHtgmYUEYVIwtmT+3und9Lm2u0aWKX9uGbhCg25cJPeZcXl1S lw7/Lq4Ph9JOTbvcgEPiEB5LNfEsjHIMDrW0S61j2s7a2EIAMJABkyUgxggIq0RkT+Ft 7IjKPmScpcZNBLlf4MpekygzxbkdhGVwrXRXA0/BxCp/KHNWgMtvPncsdSVSbjz/wYjF m9ub3U5sKc7aKhcJTDPbtz6O5Z2UlnI6E42JTtKbpwD/XQP9wU4Vl4bjJTq56d3cNbH+ Z/7A== X-Gm-Message-State: AOJu0YxGLg899uf1tzzf7hDRYdWRV+prKrOQ7kQmZqTJfs97+4Pk2S0b gzaGEy8/uRrLcRhVGm+E+0OvZLhv4dP7T2Hy2lyAPBRkKLRDu5++oeTopg== X-Gm-Gg: ASbGnctT0B9Ai65mQvY0wbcfghShoGYe7c0m0g31VavTekt0uGK6GLRHFNeJYYjImRx TXfxsNEtq1HlLB5yi/kCkj9CtgcsSXLFNw57LE92hg8eZadugvzKRzId+AnrkIL90DWutRxQ4j3 ApI5EBiPnzJBjh5+aTb//kM27j+zLy1cwmu6vXgJdlm+69ZhmtWLMF5XT33yNqmVvvlKQhh4MPH En5l2Fel8lmGkVJMaUohx7ZByGMmW4hwdhjckfjUiNCmwVUCVGakIzBfHLCXwEj8cY8sjVYSUKl 9SiYrCcsEYxoMpBGnCydnKztD+IUDOsJ9zp3EE0iG7jFD+OzUR8+KO8HY49H X-Google-Smtp-Source: AGHT+IGG9ve6DX/pXVskkvmdUtahesV+qvB81/nqZAOU/DSpF1wMmWRaTNyDGAv1YbUh2Xso3A6rQw== X-Received: by 2002:ad4:5d68:0:b0:6d8:883b:142a with SMTP id 6a1803df08f44-6e1b216ffadmr641644256d6.2.1737997843943; Mon, 27 Jan 2025 09:10:43 -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 6a1803df08f44-6e20514edb5sm36780296d6.29.2025.01.27.09.10.43 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 27 Jan 2025 09:10:43 -0800 (PST) Message-ID: Date: Mon, 27 Jan 2025 12:10:43 -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: UFS bad inode, mangled entry on Alder Lake-N(100) Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.54 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.99)[0.991]; NEURAL_HAM_MEDIUM(-0.84)[-0.838]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_HTML_ONLY(0.20)[]; XM_UA_NO_VERSION(0.01)[]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; 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::834:from] X-Spamd-Bar: - X-Rspamd-Queue-Id: 4YhZgS6Dnfz3byv I recently bought one of those mini-pc firewall devices (Topton 12th gen N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg or buildkernel without getting a slew of these messages, inode number changing and a panic shortly thereafter.

kernel: /: bad dir ino 4567815 at offset 0: mangled entry

I tried the FreeBSD-15.0-CURRENT-amd64-20250124 snapshot and 14.2-RELEASE, both with and without journal, trim and softupdates in every permitted permutation without success. The system has an NVME, but I experience the same problem with the install on a microsd and different known good NVME drive. Each time I had to reinstall because the filesystem was so corrupted it wouldn't boot after a fsck.

The system is now running fine with ZFS so I'm wondering if it's silently corrupting the ZFS or if there's a bug in UFS2 that's tickled by this CPU. I'll provide any debugging required.

Ian From nobody Mon Jan 27 17:38:03 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 4YhbHC32f9z5m0yb for ; Mon, 27 Jan 2025 17:38:15 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from cm0.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YhbH91vtZz3gvw for ; Mon, 27 Jan 2025 17:38:12 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd-current@dino.sk designates 84.245.65.72 as permitted sender) smtp.mailfrom=freebsd-current@dino.sk; dmarc=none Received: from dino.sk ([84.245.95.254]) (AUTH: LOGIN milan, TLS: TLSv1.3,256bits,TLS_AES_256_GCM_SHA384) by cm0.netlabit.sk with ESMTPSA id 00000000021C1AE8.000000006797C47D.00004A67; Mon, 27 Jan 2025 18:38:05 +0100 Date: Mon, 27 Jan 2025 18:38:03 +0100 From: Milan Obuch To: freebsd-current@freebsd.org Subject: Re: UFS bad inode, mangled entry on Alder Lake-N(100) Message-ID: <20250127183803.23683162.25648751.59233766@dino.sk> In-Reply-To: References: X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.3) 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-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:5578, ipnet:84.245.64.0/18, country:SK]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dino.sk]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4YhbH91vtZz3gvw On Mon, 27 Jan 2025 12:10:43 -0500 Ian FREISLICH wrote: > I recently bought one of those mini-pc firewall devices (Topton 12th > gen N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg > or buildkernel without getting a slew of these messages, inode number > changing and a panic shortly thereafter. > > kernel: /: bad dir ino 4567815 at offset 0: mangled entry > > I tried the FreeBSD-15.0-CURRENT-amd64-20250124 snapshot and > 14.2-RELEASE, both with and without journal, trim and softupdates in > every permitted permutation without success. The system has an NVME, > but I experience the same problem with the install on a microsd and > different known good NVME drive. Each time I had to reinstall because > the filesystem was so corrupted it wouldn't boot after a fsck. > > The system is now running fine with ZFS so I'm wondering if it's > silently corrupting the ZFS or if there's a bug in UFS2 that's > tickled by this CPU. I'll provide any debugging required. Just a "me too" message - I did test another device with the same CPU, mine is SZBOX. Only with 14.2-RELEASE, but I tested with both NVMe and M.2 SATA devices, both direct in miniPC and externally via USB-NVMe and USB-M.2 SATA converters. System installation went flawless, however, just building ports-mgmt/pkg port was enough to start generate mangled entry messages as you wrote. To me it look like there is some bug in UFS code when used with this CPU, I have no idea how such a bug could not manifest itself on another platform - I was convinced UFS code is hardware independent, this is really strange. I did not test with ZFS yet, I plan to do it. So, if I can test something, patch, different setup, provide some debugging, count me in. Regards, Milan From nobody Mon Jan 27 18:12:08 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 4Yhc2g3Ykrz5m3NB for ; Mon, 27 Jan 2025 18:12:27 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from mail2.pluspunkthosting.de (mail2.pluspunkthosting.de [217.29.33.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yhc2f6JkSz3nVk for ; Mon, 27 Jan 2025 18:12:26 +0000 (UTC) (envelope-from pmh@hausen.com) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (87.138.185.145) by mail2.pluspunkthosting.de (Axigen) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA id 123052; Mon, 27 Jan 2025 19:12:18 +0100 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 \(3776.700.51\)) Subject: Re: UFS bad inode, mangled entry on Alder Lake-N(100) From: "Patrick M. Hausen" In-Reply-To: <20250127183803.23683162.25648751.59233766@dino.sk> Date: Mon, 27 Jan 2025 19:12:08 +0100 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20250127183803.23683162.25648751.59233766@dino.sk> To: Milan Obuch X-Mailer: Apple Mail (2.3776.700.51) X-Rspamd-Queue-Id: 4Yhc2f6JkSz3nVk X-Spamd-Bar: ---- 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:16188, ipnet:217.29.32.0/20, country:DE] Hi all, > Am 27.01.2025 um 18:38 schrieb Milan Obuch : >=20 > On Mon, 27 Jan 2025 12:10:43 -0500 > Ian FREISLICH wrote: >=20 >> I recently bought one of those mini-pc firewall devices (Topton 12th >> gen N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg >> or buildkernel without getting a slew of these messages, inode number >> changing and a panic shortly thereafter. >>=20 >> kernel: /: bad dir ino 4567815 at offset 0: mangled entry >>=20 >> [...] >=20 > Just a "me too" message - I did test another device with the same CPU, > mine is SZBOX. > [...] In the OPNsense community we had frequent reports of UFS corruption with Alder Lake and Raptor Lake CPUs. Lots of embedded devices of varying manufacture and quality in use, apparently. The problems were fixed in all cases that I am aware of by applying the = current Intel microcode update (sysutils/cpu-microcode). Make sure to activate = early loading via /boot/loader.conf(.local). HTH, kind regards, Patrick= From nobody Mon Jan 27 18:28:28 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 4YhcPf1mj8z5m492 for ; Mon, 27 Jan 2025 18:28:54 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mailtransmit05.runbox.com (mailtransmit05.runbox.com [IPv6:2a0c:5a00:149::26]) (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 4YhcPd6lQVz3tbY for ; Mon, 27 Jan 2025 18:28:53 +0000 (UTC) (envelope-from lists@yamagi.org) Authentication-Results: mx1.freebsd.org; none Received: from mailtransmit02.runbox ([10.9.9.162] helo=aibo.runbox.com) by mailtransmit05.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1tcTqs-000dhr-KX for current@freebsd.org; Mon, 27 Jan 2025 19:28:50 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=yamagi.org; s=selector1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:To:Subject:MIME-Version:Date:Message-ID; bh=y/jiLk00OhoxIhgC4vlyGYPS+Ssc5kJxL4o30uCFUys=; b=Qorf9HH3UZn1KbK5mwFn+T3u3A wFT0lNghWvUVYwcS2gvybODr287Qhqn9a/U0/dsYA9m/O6HNII2CvRi9njI8lvoIIO8Jjn9G1Rd6e LDaHnpRwUukOKKvlUwQI2QCtgyig7eLa34nw3IsLG/fV/HH1R3dgA9/IO4QuFhLx8sLX1Xb2zBKAJ nGYx86y2nE+XorHmOZiO/Kg8kA6rkx5cYZAndrmAL70r+zm+nBLoAFahB6u6hvLzp0z22ys0SZD1x zEDa5SuuP2HevvnZ4DCxYnW1K87CIHszIFePq4Y/oFZcT6mhg6S3c4llcki/mh2mTpUdbIL0fXjt4 tZh3r3LA==; Received: from [10.9.9.74] (helo=submission03.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1tcTqs-0001cx-43; Mon, 27 Jan 2025 19:28:50 +0100 Received: by submission03.runbox with esmtpsa [Authenticated ID (1103314)] (TLS1.2:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.93) id 1tcTqX-00CzUI-Qg; Mon, 27 Jan 2025 19:28:29 +0100 Message-ID: <6530f044-486d-4128-9e23-ee03e6686aa9@yamagi.org> Date: Mon, 27 Jan 2025 19:28:28 +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: UFS bad inode, mangled entry on Alder Lake-N(100) To: Ian FREISLICH , FreeBSD Current References: Content-Language: de-DE From: Yamagi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4YhcPd6lQVz3tbY X-Spamd-Bar: ---- 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:50304, ipnet:2a0c:5a00::/29, country:NO] Hi, sounds like the Alder Lakes PCID bug in N100 flavor. On the small cores the INVLPG instruction is broken, failing to flush all (global?) TLP entries leading to cache corruption. FreeBSD has a work around for that: https://cgit.freebsd.org/src/commit/?id=cde70e312c3fde5b37a29be1dacb7fde9a45b94a However that work around never fully solved the problem on the N100 series. My own N100 board was never stable with PCID enabled and there are several other reports of the same problems. For example https://lists.freebsd.org/archives/freebsd-current/2023-August/004116.html Since Linux went with disabling PCID all together on all Alder Lake and Raptor LAKE CPUs, I did the same by setting vm.pmap.pcid_enabled=0 in loader.conf. Since I did that the system is running fine. The Linux commit disabling PCID is here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ae8373a5add4ea39f032563cf12a02946d1e3546 A microcode update might also help. I didn't test the updates released by Intel since early last year so I don't know for sure. Regards, Yamagi Am 27.01.25 um 18:10 schrieb Ian FREISLICH: > I recently bought one of those mini-pc firewall devices (Topton 12th gen > N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg or > buildkernel without getting a slew of these messages, inode number > changing and a panic shortly thereafter. > > kernel: /: bad dir ino 4567815 at offset 0: mangled entry > > I tried the FreeBSD-15.0-CURRENT-amd64-20250124 snapshot and 14.2- > RELEASE, both with and without journal, trim and softupdates in every > permitted permutation without success. The system has an NVME, but I > experience the same problem with the install on a microsd and different > known good NVME drive. Each time I had to reinstall because the > filesystem was so corrupted it wouldn't boot after a fsck. > > The system is now running fine with ZFS so I'm wondering if it's > silently corrupting the ZFS or if there's a bug in UFS2 that's tickled > by this CPU. I'll provide any debugging required. > > Ian -- Homepage: https://www.yamagi.org Github: https://github.com/yamagi GPG: 0xeb1472e71d502515 -- Homepage: https://www.yamagi.org Github: https://github.com/yamagi GPG: 0xeb1472e71d502515 From nobody Mon Jan 27 18:55:04 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 4Yhczv4Kd8z5m69M for ; Mon, 27 Jan 2025 18:55:07 +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 4Yhczt5zCnz42KS for ; Mon, 27 Jan 2025 18:55:06 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=YjwshnFH; spf=pass (mx1.freebsd.org: domain of ianfreislich@gmail.com designates 2607:f8b0:4864:20::b31 as permitted sender) smtp.mailfrom=ianfreislich@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-e549be93d5eso8444866276.1 for ; Mon, 27 Jan 2025 10:55:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738004105; x=1738608905; darn=freebsd.org; h=content-transfer-encoding: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=DSIBcweZdL6d+0q7KhKeVDPt2OvoC08Nk6+bXLHq5dA=; b=YjwshnFHpksK8+NPlGHPPjhw650ryeXDi7HRxMixZPzLCk5ZjOCrRjo0/SUq3q91z6 27gsM1NVZ0t1E7F8PIFDA4XAn+ylUoqxmtWN/oYTI1DnCS+SKnOXcqJaU6cdQxDrgI2C d3UeopXhXV+26ZbotkDlXFnEBgtp8CtjfDF5gtN49IfnnOG58MOc3XS51/9P4QcorRUS KQQRcJga0usvyBCADkycnKAKQ2VfggKNOu2U6ylCtIQvHCkTrqDeV8QjJm1zkNwyJYw3 iCrQWE9Px3RfrKluPbPphiWDPb/qTpDoc0bOHv6RE6yoUdPgn0ntiXGKtS3WpOyL/j12 Fi2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738004105; x=1738608905; h=content-transfer-encoding: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=DSIBcweZdL6d+0q7KhKeVDPt2OvoC08Nk6+bXLHq5dA=; b=ixIldapHs7/4jFe2WqGkA4uxy8twsJfyJG6HqMlIi+3vZsZqnTJDZ+1xFYqIF2t7rX be34sx+NxAXrU899SDZUgbBGHLTB4n2uHg/K9C6e/PJIkXrZY//tju5joTGrv/WRiMb2 zO8EBaqUnA6VVK0qkCAEJFXAgSRejm5n9l7Sny/pk59R/qB06MHSgZTpMG01Z5+L6SD9 06lPNWhHn5gFXWWsnzBqckoG66KsX9Hw8giu+q+c19wRb96iwPIlyRCyRHf6wCKWUldQ YlTAGdXE63R/UOl4t6T/xTRAY+sNRYbtQFEI3HchdNzivMsYb3OrcDBd1TGF1HqFgD+8 XdpA== X-Gm-Message-State: AOJu0YwRG2X9mgF7bXCgOcwy/CcgotofHFZk2iKGiLIgEcDACoXyyeIA Hr2yeb84jCzepG350JYakiedD4DhAwKXtZQPvW7g9lxG7SMkre9tKoI/Ag== X-Gm-Gg: ASbGncs9L+oR+8zn9elnyaA3xqxtcOV4swpBHkIzq2RLUdewudD1jbb1RAL/qXNTteP XkT2nac2YBYCbwvs0YOOvj8lTQcMnLdyzlj0f3lB/pvUgbnpRvSjenG3rvn2mnBO2Ba17LP7ROC +ZMEPPdX/SV6DOejiXukP33z1drJIdFH95RlgXoNGNbAsF3RZhx6ss2QdtHl5UU/oCZ33Tv+18I kAJz3NbHisEJwuyvVElmz5csEQOk1Pxbvyr8pRVBdFHUJcGZyVd1yeUUrMxobrvoVa6Bv7bGNkQ 0pqytn4CUflknzoW57BGPVqTMVrSsiVw2LhlAxg3n3ieXonFyUny0b00RR/l X-Google-Smtp-Source: AGHT+IF5dUowT0uJXGwgZ3RpPaoMzxHpFVvJv6BWVJM2XUamgk73BChomY8MYRgHsShNOanuDAnXNQ== X-Received: by 2002:a05:6902:2684:b0:e58:341d:50cd with SMTP id 3f1490d57ef6-e58341d5b13mr13768100276.49.1738004105373; Mon, 27 Jan 2025 10:55:05 -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 3f1490d57ef6-e583b862558sm1722003276.43.2025.01.27.10.55.04 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 27 Jan 2025 10:55:05 -0800 (PST) Message-ID: <93f885a3-1f96-403c-9739-ddb836fd4fa3@gmail.com> Date: Mon, 27 Jan 2025 13:55:04 -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: UFS bad inode, mangled entry on Alder Lake-N(100) To: freebsd-current@freebsd.org References: <20250127183803.23683162.25648751.59233766@dino.sk> Content-Language: en-US From: Ian FREISLICH In-Reply-To: Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.47 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.916]; NEURAL_HAM_MEDIUM(-0.87)[-0.865]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_HTML_ONLY(0.20)[]; XM_UA_NO_VERSION(0.01)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:~]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b31:from]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4Yhczt5zCnz42KS It might be timing related. UFS with a custom kernel (previously GENERIC) is less prone and I got these building world on an microSD:

Jan 27 12:35:54 router kernel: /: inode 1286411: check-hash failed
Jan 27 12:35:54 router syslogd: last message repeated 1 times
Jan 27 12:35:54 router kernel: /: inode 1286412: check-hash failed
Jan 27 12:35:54 router syslogd: last message repeated 1 times
Jan 27 12:35:54 router kernel: /: inode 1286413: check-hash failed
Jan 27 12:35:54 router syslogd: last message repeated 1 times

No panic so far, without the cpu microcode. I'll look into that shortly.

Ian

On 2025-01-27 13:12, Patrick M. Hausen wrote:
Hi all,


Am 27.01.2025 um 18:38 schrieb Milan Obuch <freebsd-current@dino.sk>:

On Mon, 27 Jan 2025 12:10:43 -0500
Ian FREISLICH <ianfreislich@gmail.com> wrote:


I recently bought one of those mini-pc firewall devices (Topton 12th
gen N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg
or buildkernel without getting a slew of these messages, inode number
changing and a panic shortly thereafter.

kernel: /: bad dir ino 4567815 at offset 0: mangled entry

[...]

Just a "me too" message - I did test another device with the same CPU,
mine is SZBOX.
[...]

In the OPNsense community we had frequent reports of UFS corruption
with Alder Lake and Raptor Lake CPUs. Lots of embedded devices of
varying manufacture and quality in use, apparently.

The problems were fixed in all cases that I am aware of by applying the current
Intel microcode update (sysutils/cpu-microcode). Make sure to activate early
loading via /boot/loader.conf(.local).

HTH, kind regards,
Patrick

From nobody Mon Jan 27 19:52:26 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 4YhfGT2TBTz5mB5n for ; Mon, 27 Jan 2025 19:52:49 +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 4YhfGS52Lzz3DNg for ; Mon, 27 Jan 2025 19:52:48 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=loLwTogd; 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; dmarc=pass (policy=quarantine) header.from=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=1738007566; 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=qcfRFvRn186q6T2XMuaTrla/ljHzFVjwryGxB3Zh7ik=; b=loLwTogdq/gwyEpWXvbxSr6TvcwnGQuVl3XLDVkGB2TbbjqsLZOLpvqx9MnHw/C78G/GZ8 vD9MIG2pPwNSDkgJgkQTTiPeD10MkahNKRZK3ewFb2uFiYyY1sZLBvD79ojuP1wJvESPzW 37XfF8cL08rx2c/+UnkotOu1y10zo9qdSaygagJYc6QPcYPBQ+Dvs4fSQdUK167Lp8B9jl I1uyucl6Te029F5S5kNwzSat4RnoACnP90m9DRxEC6AmwjBXDlHMFIAOzdGQzR+c6h17YS 6fwWPiUc+21T+SxdH/FfktGWcZ8RoCVmCngNLtolKKs4GHh1m3fevFq+c4I8hw== Date: Mon, 27 Jan 2025 20:52:26 +0100 From: Alexander Leidinger To: Current FreeBSD Subject: Re: Difference in "netstat -rn" output in the last 2 months In-Reply-To: References: Message-ID: <2a0706e3700fc26ebd16616320082c23@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_515b1dd9a2e2d5410e0c047c32d1d4f3"; micalg=pgp-sha256 X-Spamd-Result: default: False [-5.90 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.80)[-0.800]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx:c]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; ASN(0.00)[asn:34240, ipnet:2a00:1828::/32, country:DE]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DKIM_TRACE(0.00)[leidinger.net:+]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; 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)[]; HAS_ATTACHMENT(0.00)[] X-Spamd-Bar: ----- X-Rspamd-Queue-Id: 4YhfGS52Lzz3DNg This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_515b1dd9a2e2d5410e0c047c32d1d4f3 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2025-01-26 16:58, schrieb Alexander Leidinger: > Hi, > > something has changed in the output of "netstat -rn" between > 2024-11-23-195545 and 2025-01-22-151306. The default route is not > listed as "default" anymore, but with "0.0.0.0" resp. "::/0". This > breaks some tools (e.g. iocage). Iocage uses python, I'm not sure if it > uses netstat or some other interface, so it may not be directly related > to netstat itself but could be related to some other stuff (netlink > maybe?). For those which stumble upon this, a fix is here: https://github.com/freebsd/iocage/issues/60 Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_515b1dd9a2e2d5410e0c047c32d1d4f3 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmeX5AsACgkQEg2wmwP4 2Ia4mg/9HeFX7Lds9mT+Y6I0x2VAbYqmC25IhgdyxxI3ASqLuOLhz6XhCvmMCqph Qb79PSW2w/Jx/AcOBO3TC/Nmsu1zkNeefPWGOiuWrXndTKiyqSIzLpRsW4oOzY8B IPDTzBsVECc4+6Ssa3ifMp42L6YbBO5y3ydDlZLlQaRkJxB4TqLiD7489JI/QNj0 dfngQy3bjDdhedO+Fc5YgqchMALPrIHRM61uanXJNkFWyVbbXzzYiwM9HcoTpbNe EM/Rzo/EtHLLght1wXZs0C/qYo+FQcUMpU2ZA1OCpq5cYXDuq+vQ589Dz6nzHf+q grI40s9632fmpIpwBAZBa1KXKCW5peIpkc7YrvZJuO+I41V6NLV3qDO5yHEHUWCq T7wOvUqQ7TgluUkjWcr1v9+l2JtE8hH6T9aD42N+YPm+DSbuwyLF+wOkpl/SCYKO F/CNlFFF1MghUqaRH0Wuflnf34ztSJUWWW2+C3zeEcw1Mf+QoDk2jDGgpGmqAsRC otZ/XZf2oIu+VNxCWsK6KamF+9dP1pXn5JDdI+jUSaqmvaOFLGnu0ZmGRL5qBAch KnC7fLbS4bjx0hEBLBr9+LUJyHuiNq7l5FaMvXhVjn54ziNFZeTGHjgqK20g71Vw cUCHsnigU3qsS39+dSrwOavZw1K7/MNNejfiI+e5Y/RoyOSyV7s= =vkTK -----END PGP SIGNATURE----- --=_515b1dd9a2e2d5410e0c047c32d1d4f3-- From nobody Mon Jan 27 20:07: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 4Yhfb94L1Zz5mCLq for ; Mon, 27 Jan 2025 20:07:17 +0000 (UTC) (envelope-from grembo@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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yhfb82JVlz3HV8 for ; Mon, 27 Jan 2025 20:07:16 +0000 (UTC) (envelope-from grembo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738008436; 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=GesE+aL5jWR/R3GD/VPst/R9i2Zq13cUZ41KFfiO3RQ=; b=GjnpZUHxa/vXDZpT2fzgW+Ztw19OeZj3aYtApzcQRr+cUkVYpcL3ty1/wlcFOfWI70P6bB JJ8h1kWsRUNGBK8W7b8zMWeOBaOPGIe/XmubZbPRNdeDnXXrrqoHwQv7n5Qg7sulVXU0sQ XVqeGwL00survKWWa/s9EZ5X23mBRtuR7qav9vQTMQ/NQvaZ1v7BQ7xot81GjK1uE4vr3F lg2B1QbnN04tNwHEe2KlUT6lfPfQWE/FKLtXJ+4ocwW65aM4yRqCN+A1JzL2ue5z+Uek4T uf+vKsZAlsPfq7OtXqRTQrx/xbUZJf2O//YDQiNsqPN0s/6Q2KcgRiYMomTdTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738008436; 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=GesE+aL5jWR/R3GD/VPst/R9i2Zq13cUZ41KFfiO3RQ=; b=mzfHBW005nEwsS3skDtEbOi3csWeFPWmVhdmseVgiY19V0MQ+g1fAgnG7KQTENrLZIryj6 Z70lpuOoPdliw32SN6lDiBXTpjsHutlIfOEKy/1ar4rOtFm7Ykr9vyhzgi1ToZchUvJMvf 0vY+878Q3xb0D3fvJbGkJb58hHZM8eHbcumJ9EdS7WLSHR6imEdWy7fbv8cnGMoDVcEbGe NnAmtWdn+z+ELwH+GovMDz7o5K6uefLJxnSMOvxuLqj1pher+mEnf8Sve8bSUdMCareG3u ywGaTJCrkktGL7UX4YzXEUl6Lp6zoXzWdDCFKeteGUUEIiu/iupNH0kZEhzoJQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738008436; a=rsa-sha256; cv=none; b=jlruO9M1Y1ZlCZ0uIee1W7YLFAc4TruflIOTpjbCEn7e+7uOafbQplkE5hWS4N0Q4ym3PD IIIbjdV0TTqW2343fNT/D0kJmGFaHgFFs9/idqfP2mCDVytoPEtTM5ePyaURerTTRuudX3 XemBRdFJda18s7WjbYsPKAp48H9aUpgvQ8FezTj/7XAlbvayZ7AajjYswWBetkGWe862uR 22GA0gW//Pl5Ch25KaBKo+60YgdH1HLhInd1oCfxzdhfTzzBdcsC6uk2qN/sCy5j20ILQc iMlijqKvCRUjjRHKrGtHJB086I54rR3m/vow0YaJBncs86+mmPBsYHDDJUQfyw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (Client did not present a certificate) (Authenticated sender: grembo/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Yhfb76sh4zM1t for ; Mon, 27 Jan 2025 20:07:15 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id 70131a06 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Mon, 27 Jan 2025 20:07:13 +0000 (UTC) Date: Mon, 27 Jan 2025 21:07:01 +0100 From: Michael Gmelin To: freebsd-current@freebsd.org Subject: Re: Difference in "netstat -rn" output in the last 2 months Message-ID: <20250127210701.33c15ecc.grembo@freebsd.org> In-Reply-To: References: X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= 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 On Sun, 26 Jan 2025 16:58:57 +0100 Alexander Leidinger wrote: > Hi, > > something has changed in the output of "netstat -rn" between > 2024-11-23-195545 and 2025-01-22-151306. The default route is not > listed as "default" anymore, but with "0.0.0.0" resp. "::/0". This > breaks some tools (e.g. iocage). Iocage uses python, I'm not sure if > it uses netstat or some other interface, so it may not be directly > related to netstat itself but could be related to some other stuff > (netlink maybe?). > > Does this ring a bell for someone? > If there had been "iocage" in the subject, I would've looked into it earlier :) I'll produce a PR on the repo based on the issue you opened and also apply it to the port. Cheers -- Michael Gmelin From nobody Mon Jan 27 20:23:51 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 4YhfyL3StWz5mDdt for ; Mon, 27 Jan 2025 20:23:54 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 4YhfyK2z8nz3Mbg for ; Mon, 27 Jan 2025 20:23:53 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=l5tJM12w; spf=pass (mx1.freebsd.org: domain of ianfreislich@gmail.com designates 2607:f8b0:4864:20::72f as permitted sender) smtp.mailfrom=ianfreislich@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qk1-x72f.google.com with SMTP id af79cd13be357-7be49f6b331so464297885a.1 for ; Mon, 27 Jan 2025 12:23:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738009432; x=1738614232; darn=freebsd.org; h=content-transfer-encoding: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=NlY/jtVDZnyLBJm8BEwwiAh0YeGUULv6cu1avPOtSlw=; b=l5tJM12wDGfT/junoMaL6FXFH0iPprjU7BUelsiQ8ZHQhDoioHuw7EdqQXM1xPFgE2 M1D+t5usLkpnP2zvevKst++US/rjeEAkXE6UQMhrnEJH5u+n+ssb2yIPFpfkkN9fQV+t iy/1Df8/anLT4O2xtYGgq6c6eNC5G5Q9atCIBifgfIcUqhm2k5a19jW2mk9ZDAG+jkws t/8bn/hhBM0U6LZL0Cx2lyEuyEqAZFYrgrnbdi7QEGoG0WAXp2x70kmJtu6XsMPMCtU2 zFOU3+C+JvwPEBAgU4RLaPLzt+Lo/q0+r4Jw3bhGc6bpNbYK6F7KX672pjaHJvSPx/+E AnUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738009432; x=1738614232; h=content-transfer-encoding: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=NlY/jtVDZnyLBJm8BEwwiAh0YeGUULv6cu1avPOtSlw=; b=kfTRkv8DMLa75n3z2lQUTCZzROwCR0SvgYy+SjLSFjENI5qGJKPhAghIW8hMRlKUiG zOaUu3HXL8gnuLfyfckwk1ywuauDbTN+s+qq7mBl67ybiRmP3xBFphoFAoUsYMnVI136 SRElXl8HubcfuNafpFJOTJL21rhQaoM4UWEwI7hZrkW0M7hEMTgRLJL7hpL9Cz0LKRUE Z+tj/dUCponNyEIta6FAFnmTVc7fBbIeaS56/E3OS1jb/IXV5Qy2lgjTygjOSytyyKpb AKivOrX9OMMuSwQ9rfp7YEjRLAqkFKIYEcbGHzUQ0Z5Xpy9Fk2XvoOsc27v+XsUGcG9W F+0w== X-Gm-Message-State: AOJu0Ywdr6TzqwEs7p7JPTqoCwGPZcO6nm03UItY+gKj2hDJDpZDnWef o/ArP1qlZbeTrBcRQqFGh7yMU9rVLaGPqMYm339xs/TvyMfZWAtxBHcyiw== X-Gm-Gg: ASbGncswWFYub7moS8lfpX3DebLW7cVR8Y3KzPoWhs4k8gjnb2OgSgK6Bb/JAWgrsyM oNZFQ649iR9kXb+dCwuem71+cWjQ/V5cTljeTMu2t+HLB4Cjh/wXt25OKSvRZypSbL6xlD1Wj8+ u+zzXtfco2F1tjqZHgfVGXPAjWKC0bvz+RipxhBFizMdu4zQMKAHF5R0i1HkXBHy3hqBtCaWu9e e8R6u2Hq/U4N5oBVHWQVzY2LWK5UDJRuUBBkp669MJJPiyZtekWIZWzDtyp66mdJi3vpXD5yWy3 De5SuFkLXDGXJn3YwoBVxh0KXuTybFs6zFBsEfupV/tWc5tP/ULjxuXm9x4M X-Google-Smtp-Source: AGHT+IGK2jfg13N2Z3H/BxT+cY34n0JejmiR2WoZY+hkQcPaDj0VuqaOv1qWl7l0WEsc0UINcniVBw== X-Received: by 2002:a05:620a:2588:b0:7b7:ab7:ef1b with SMTP id af79cd13be357-7be63278e79mr6474022385a.44.1738009432016; Mon, 27 Jan 2025 12:23:52 -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 af79cd13be357-7be9af0d281sm425050785a.99.2025.01.27.12.23.51 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 27 Jan 2025 12:23:51 -0800 (PST) Message-ID: <15b16b38-2614-407a-b8a7-978eba0ae54f@gmail.com> Date: Mon, 27 Jan 2025 15:23:51 -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: UFS bad inode, mangled entry on Alder Lake-N(100) To: freebsd-current@freebsd.org References: <20250127183803.23683162.25648751.59233766@dino.sk> Content-Language: en-US From: Ian FREISLICH In-Reply-To: Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.72 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.996]; NEURAL_HAM_MEDIUM(-0.65)[-0.645]; NEURAL_SPAM_SHORT(0.61)[0.611]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_HTML_ONLY(0.20)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:~]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; 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)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72f:from] X-Spamd-Bar: - X-Rspamd-Queue-Id: 4YhfyK2z8nz3Mbg All,

I can confirm that the microcode loaded early fixes the issue.

Ian

On 2025-01-27 13:12, Patrick M. Hausen wrote:
Hi all,


Am 27.01.2025 um 18:38 schrieb Milan Obuch <freebsd-current@dino.sk>:

On Mon, 27 Jan 2025 12:10:43 -0500
Ian FREISLICH <ianfreislich@gmail.com> wrote:


I recently bought one of those mini-pc firewall devices (Topton 12th
gen N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg
or buildkernel without getting a slew of these messages, inode number
changing and a panic shortly thereafter.

kernel: /: bad dir ino 4567815 at offset 0: mangled entry

[...]

Just a "me too" message - I did test another device with the same CPU,
mine is SZBOX.
[...]

In the OPNsense community we had frequent reports of UFS corruption
with Alder Lake and Raptor Lake CPUs. Lots of embedded devices of
varying manufacture and quality in use, apparently.

The problems were fixed in all cases that I am aware of by applying the current
Intel microcode update (sysutils/cpu-microcode). Make sure to activate early
loading via /boot/loader.conf(.local).

HTH, kind regards,
Patrick

From nobody Mon Jan 27 21:23:29 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 4YhhH86Jxmz5mJJ9 for ; Mon, 27 Jan 2025 21:23:32 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YhhH85h3pz3VZZ; Mon, 27 Jan 2025 21:23:32 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738013012; 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=vf8DTBKPuuOoqpO4gr4tZVjwE++aeU2E+0fZs9QE8Z4=; b=vdWe0h8ilyAucEpLLVWRsnouBW4hjHdKGzEC8NFSIeGmmn+/tvg49794e2STXh9ac06wfk gVuHEHOEFfKnEIqvmIOB5+dZN80UUmQjAvOWo6mqVj7FKB9isxdzDBPg1d9560+cnb7mLu y1E0R+tlOV8K7C22Na1aR76e77e6T2sXqlvUncC6LgIdqxHbyNkAKFgfgyRe+ujY74sZbQ zG4V9fJRyf1oaGezuVzg2r9VhsChomOORWLlifZgy8hqfqEQc+v5uuUr+AsApGLKuu+GmW EpueWh8MRr5s9t4jJ8/3AgK9Flvnxe+HYUvXi3Vaf4zZE82Glg9vScfJ0B3xTw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738013012; 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=vf8DTBKPuuOoqpO4gr4tZVjwE++aeU2E+0fZs9QE8Z4=; b=xcXpPCk6uKJ1WbNAQxOP8xCqmVQhNBzAPQKs2tv+B62R9tMtW+YUmK6Cv4xVI9uDgEiCz7 bURMww42AAz3qMCEv6KaVPZd270braf7ep/zoyVf6/KlrdjSdv3iEZMV7VFjekf+XsuWu3 IIcA/Sdul/quKPtEggLZLktFwwoY1D//bImVf4Vb1yTEUvynktE0QBJRNv6FHkucVH5sGY u90j4o8IcBlbuowmpofUExhafyuKIxmbzd/UsiR59E55n/ZPlJVpercJNH2Qhbs/JApUU3 NMdb9mGW1BAwyMna1eraaZMqLsFpaWO/aRrTskzBG7lI6BZN7v6iYSRpftZ3Bw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738013012; a=rsa-sha256; cv=none; b=cr4HXByXdIObba+24FNy+Rp64edEA1Xp4DvyK6NEOJjV4UlZIm3z5hdi4ezp9LZufVFSoG QuTfejrDIkzm50rtHOAs4SoWNseQLfxa7+EO83xR1n6BUtkIYgQdQzXyPo6APvh5uFGZ9E 6GFM1NjQOMT5BIdzBMq4xwIzVv3Q7i5F0M2Jz4TtY4HvbAyji8OE4nNqLZS1p/wzb9BJTI RMOu687c8Em5Nbr0685BaC3388mckMw4L5oDjrHwAP/qoSfFVT6PsvJwbiexiznatMd6ov n+GICuEmwEaEaJdayhIAm/VsQoL+zp3w006v5MHrIYXjLw/JqQsmkmkwJe37Sw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YhhH82PrJzMfY; Mon, 27 Jan 2025 21:23:32 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Mon, 27 Jan 2025 13:23:29 -0800 From: Gleb Smirnoff To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: January 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: On Mon, Jan 27, 2025 at 01:01:16AM -0800, Gleb Smirnoff wrote: T> This is an automated email to inform you that the January 2025 stabilization week T> started with FreeBSD/main at main-n275044-c6767dc1f236, which was tagged as T> main-stabweek-2025-Jan. Quick status update: 1) No problems were found with a desktop & laptop experience. 2) We discovered a regression, panic with INVARIANTS, for network applications that use socket option SO_REUSEPORT_LB. We are working on the problem. -- Gleb Smirnoff From nobody Mon Jan 27 21:32:41 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 4YhhTv1svyz5mK4v for ; Mon, 27 Jan 2025 21:32:51 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "plan-b.pwste.edu.pl", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YhhTs3Z1Cz3YP5 for ; Mon, 27 Jan 2025 21:32:49 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=plan-b.pwste.edu.pl header.s=plan-b-mailer header.b=Tfmxx9Oh; spf=pass (mx1.freebsd.org: domain of zarychtam@plan-b.pwste.edu.pl designates 2001:678:618::40 as permitted sender) smtp.mailfrom=zarychtam@plan-b.pwste.edu.pl; dmarc=pass (policy=quarantine) header.from=plan-b.pwste.edu.pl Received: from [192.168.7.70] (dom.potoki.eu [62.133.140.50]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.18.1/8.17.2) with ESMTPSA id 50RLWfmr034868 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Mon, 27 Jan 2025 22:32:41 +0100 (CET) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1738013562; bh=Sz1TcbvZncQdINH9fNUCAkmjh/FZNCZiTYkr09iAxlc=; h=Date:Subject:To:References:From:In-Reply-To; b=Tfmxx9OhFJHDtocmmh+Es5fHYe19uy3OziXVsT/yuhKU7XpfmfbCUiaLN1mrVC4eI WQiF9ahbOJOfodBN2+s+7hfLTApCUFe/Ujt9Or4h6tZ/eJvpc0EmziFzrVoq5nUtHP lIg4AKD5BODrugV4XkGObzWLfrnqkaQCUOrqi6n2h6Ct04nQ02E4EQxqn3EsQPPnHz lkQggap2Od5uPN6yOI/dLzq9KI+zXgVcm/5E7vK/DuFEjIw8/jbkFf64U62e/hVg/6 YCFrCw2MhT7xVvFIzHNugJtn8C+fKuS5iVoQm/UyE7xd2g4kYrbqIFGGddkvRNERpI sA119BVhG5MJA== X-Authentication-Warning: plan-b.pwste.edu.pl: Host dom.potoki.eu [62.133.140.50] claimed to be [192.168.7.70] Message-ID: <36b8c7d4-df4e-41f5-89ea-eabb5a705204@plan-b.pwste.edu.pl> Date: Mon, 27 Jan 2025 22:32:41 +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: Difference in "netstat -rn" output in the last 2 months To: freebsd-current@freebsd.org References: <20250127210701.33c15ecc.grembo@freebsd.org> Content-Language: en-US From: Marek Zarychta Autocrypt: addr=zarychtam@plan-b.pwste.edu.pl; keydata= xsBNBFfi3cMBCADLecMTFXad4uDXqv3eRuB4qJJ8G9tzzFezeRnnwxOsPdytW5ES2z1ibSrR IsiImx6+PTqrAmXpTInxAi7yiZGdSiONRI4CCxKY9d1YFiNYT/2WyNXCekm9x29YeIU7x0JB Llbz0f/9HC+styBIu2H+PY/X98Clzm110CS+n/b9l1AtiGxTiVFj7/uavYAKxH6LNWnbkuc5 v8EVNc7NkEcl5h7Z9X5NEtzDxTOiBIFQ/kOT7LAtkYUPo1lqLeOM2DtWSXTXQgXl0zJI4iP1 OAu4qQYm2nXwq4b2AH9peknelvnt1mpfgDCGSKnhc26q6ibTfMwydp+tvUtQIQYpA6b9ABEB AAHNN01hcmVrIFphcnljaHRhIChQbGFuLWIpIDx6YXJ5Y2h0YW1AcGxhbi1iLnB3c3RlLmVk dS5wbD7CwHcEEwEIACEFAlfi4LkCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQHZW8 vIFppoJXdgf8D9X3VRFSNaR9lthSx/+uqas17J3FJKBo1xMQsC2a+44vzNvYJSuPGLLJ+LW2 HPVazjP/BWZJbxOYpliY4zxNRU0YCp0BLIVLibc//yax+mE42FND/+NiIZhqJscl6MLPrSwo sIwXec4XYkldkyqW/xBbBYXoIkBqdKB9j5j42Npy1IV/RizOSdmvTWY27ir8e/yGMR1RLr4F 8P5K3OWTdlGy2H2F/3J8bIPBLG6FpaIyLQw4dHSx8V02PYqDxK1cNo2kAOnU8PnZL/AGuMOH iv3MN1VYL8ehcmpBBsrZGebQJxrjY2/5IaTSgp9xHYT70kshuU6Qb97vk1mOjNZxgc7ATQRX 4t3DAQgA10h6RCXuBLMHxq5B8X/ZIlj9sgLoeyfRdDZEc9rT2KUeUJVHDsbvOFf4/7F1ovWY hJbA6GK/LUZeHHTjnbZcH1uDYQeHly4UOLxeEvhGoz4JhS2C7JzN/uRnwbdOAUbJr8rUj/IY a7gk906rktsc/Ldrxrxh7O6WO0JCh2XO/p4pDfEwwB37g4xHprSab28ECYJ9JMbtA8Sy4M55 g3+GQ28FvSlGnx48OoGXU2BZdc1vZKSQmNOlikB+9/hDX8zdYWVfDaX1TLQ8Ib4+xTUmapza mV/bxIsaZRBw+jFjLQHhTbIMfPEU+4mxFDvTdbKPruKPqVf1ydgMnPZWngowdwARAQABwsBf BBgBCAAJBQJX4t3DAhsMAAoJEB2VvLyBaaaC6qkIAJs9sDPqrqW0bYoRfzY6XjDWQ59p9tJi v8aogxacQNCfAu+WkJ8PNVUtC1dlVcG5NnZ80gXzd1rc8ueIvXlvdanUt/jZd8jbb3gaDbK3 wh1yMCGBl/1fOJTyEGYv1CRojv97KK89KP5+r8x1P1iHcSrunlDNqGxTMydNCwBH23QcOM+m u4spKnJ/s0VRBkw3xoKBZfZza6fTQ4gTpAipjyk7ldOGBV+PvkKATdhK2yLwuWXhKbg/GRlD 1r5P0gxzSqfV4My+KJuc2EDcrqp1y0wOpE1m9iZqCcd0fup5f7HDsYlLWshr7NQl28f6+fQb sylq/j672BHXsdeqf/Ip9V4= In-Reply-To: <20250127210701.33c15ecc.grembo@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-6.31 / 15.00]; DWL_DNSWL_MED(-2.00)[pwste.edu.pl:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.81)[-0.811]; DMARC_POLICY_ALLOW(-0.50)[plan-b.pwste.edu.pl,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_DKIM_ALLOW(-0.20)[plan-b.pwste.edu.pl:s=plan-b-mailer]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_IN_DNSWL_MED(-0.20)[2001:678:618::40:from]; ONCE_RECEIVED(0.20)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[plan-b.pwste.edu.pl:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ASN(0.00)[asn:206006, ipnet:2001:678:618::/48, country:PL]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; 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)[]; HAS_XAW(0.00)[] X-Spamd-Bar: ------ X-Rspamd-Queue-Id: 4YhhTs3Z1Cz3YP5 W dniu 27.01.2025 o 21:07, Michael Gmelin pisze: > > On Sun, 26 Jan 2025 16:58:57 +0100 > Alexander Leidinger wrote: > >> Hi, >> >> something has changed in the output of "netstat -rn" between >> 2024-11-23-195545 and 2025-01-22-151306. The default route is not >> listed as "default" anymore, but with "0.0.0.0" resp. "::/0". This >> breaks some tools (e.g. iocage). Iocage uses python, I'm not sure if >> it uses netstat or some other interface, so it may not be directly >> related to netstat itself but could be related to some other stuff >> (netlink maybe?). >> >> Does this ring a bell for someone? >> > If there had been "iocage" in the subject, I would've looked into it > earlier :) > > I'll produce a PR on the repo based on the issue you opened and also > apply it to the port. > > Cheers I was also hit by this change in a couple of ways. When 15.0 is released in future, it's probably worth adding information about the change to the relnotes. -- Marek Zarychta From nobody Tue Jan 28 02:10:42 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 4Yhpfp266Qz5lkPB for ; Tue, 28 Jan 2025 02:10:58 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yhpfn356tz3y9m; Tue, 28 Jan 2025 02:10:57 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=EIcIWrqh; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=rick.macklem@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5d3d143376dso7227690a12.3; Mon, 27 Jan 2025 18:10:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738030255; x=1738635055; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ADlBoALvJBNegqpxEOb1/qNZ85As10Wf/Rt+1x3mNCk=; b=EIcIWrqh38DTQXlPJEtVuntdFqoyVhwRSp25vkNKmd9GutNqpy0L0MUM/+FI4hp8Sv EONbIUtUMWKKRiBwdQ3IsX8CbYQ9bnThfgbPDweoqPZu48EOYZKEfR9dx2NLa2zJEzhM GxOpJfTxgTaWs8+lxrbUB8Z1rROaPawbbNyYr6XuAyzN1rstP5jwT6ZQQw5UtQYf9dKz V3827oi5JJl5dCnpdnBg6hORvvp550lTM859TRL9XXRLmbLNxiO0goeq+R7weWU2zYZ/ q0hN1o2e9NqIwL3rX8alJMgr+sIOkAaK19QMdHSN5OozNb+7Svd4f8acsi848lsTpga5 Tg2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738030255; x=1738635055; h=content-transfer-encoding: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=ADlBoALvJBNegqpxEOb1/qNZ85As10Wf/Rt+1x3mNCk=; b=E5pLmNhyoEJOn4KShwgUh+W33/cNNapEvwsCJSyz77LpTlHUt9OU8mCliQpmSju2yU M4uJY0osB/g/3eNzuSIjC6GvqK/eiM5gjsYWwKI38tn+63HJKn0ov26IfqLX0vq7r+Ap eG9Jq/ZnarA/CL+y2EPrxDvHLICluGrbTrNOXjifNumReell0Z0LCQvD+W2n0xb9KNc/ mIpa16E5+QzUafH8X9RF5Ni7qFuPSghshtp+EAdSbB2wM1JudjgE/mwPbOplS6ie8anC NDkSPrCtV38rX66HJ3KQ5zDedHy9KmZhpOVJOvNCCyk5K3YCNkqnbs8JYLkZNYRaVLBB UBVg== X-Forwarded-Encrypted: i=1; AJvYcCXquVA3G4JNuXyzVJlJjFwGPRB3167Sv8mfkIMmRbG9KiJy8FT2CdmQG+3cOTYKD9Mq+V/phnexrg==@freebsd.org X-Gm-Message-State: AOJu0Yyl/6+OqEAu5YeQyDHNdko3MX7mR8eraMAZCcoMp5cCHg5TcpEq qW0ayjt/u7A+4ZebIPN0w1vuaJdY6Em/MPqURs8FOowRRGVARYqyA3cYizOh6OPEWJ+hDUcLDiZ TCTylxI+kT5jORXn8DR98jKRh9DeI X-Gm-Gg: ASbGncvuXJpgbCgFbOCm4XPqP0DTLe28m4lVJl71pkp3003p55OpD0xBKZOtpxCfEGh qMBsuzexW82w0LTdw3uoWo+l1Jk958V7tsGR9csZ4NQkWjQVZjKA0LJ6YUUgziFT5Yibty+RDTV af5o17HJtZHGkhbhaeo5w= X-Google-Smtp-Source: AGHT+IFe0uZ2HmUPprWH+tHg3JFIAs5ywxbl631qLCM8xP3Yd6TQW5Gaacqx9MQbpTA7eJD7ofqbZrnbJveEQIAvz2I= X-Received: by 2002:a05:6402:50ca:b0:5d0:e9de:5415 with SMTP id 4fb4d7f45d1cf-5db7d2f89e0mr40623747a12.14.1738030255050; Mon, 27 Jan 2025 18:10:55 -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: Rick Macklem Date: Mon, 27 Jan 2025 18:10:42 -0800 X-Gm-Features: AWEUYZn5L-sPY6D_gGOMHArnn0MNpsIK5tQaQA7KmvjBo_54oLAgTyjL8hWfbl0 Message-ID: Subject: Re: HEADS UP: NFS changes coming into CURRENT early February To: Gleb Smirnoff Cc: current@freebsd.org, rmacklem@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_FROM(0.00)[gmail.com]; TAGGED_FROM(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52a:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4Yhpfn356tz3y9m On Tue, Jan 21, 2025 at 10:27=E2=80=AFPM Gleb Smirnoff wrote: > > CAUTION: This email originated from outside of the University of Guelph. = Do not click links or open attachments unless you recognize the sender and = know the content is safe. If in doubt, forward suspicious emails to IThelp@= uoguelph.ca. > > > Hi, > > TLDR version: > users of NFS with Kerberos (e.g. running gssd(8)) as well as users of NFS= with > TLS (e.g. running rpc.tlsclntd(8) or rpc.tlsservd(8)) as well as users of > network lock manager (e.g. having 'options NFSLOCKD' and running rpcbind(= 8)) > are affected. You would need to recompile & reinstall both the world and= the > kernel together. Of course this is what you'd normally do when you track > FreeBSD CURRENT, but better be warned. I will post hashes of the specifi= c > revisions that break API/ABI when they are pushed. > > Longer version: > last year I tried to check-in a new implementation of unix(4) SOCK_STREAM= and > SOCK_SEQPACKET in d80a97def9a1, but was forced to back it out due to seve= ral > kernel side abusers of a unix(4) socket. The most difficult ones are the= NFS > related RPC services, that act as RPC clients talking to an RPC servers i= n > userland. Since it is impossible to fully emulate a userland process > connection to a unix(4) socket they need to work with the socket internal > structures bypassing all the normal KPIs and conventions. Of course they > didn't tolerate the new implementation that totally eliminated intermedia= te > buffer on the sending side. > > While the original motivation for the upcoming changes is the fact that I= want > to go forward with the new unix/stream and unix/seqpacket, I also tried t= o make > kernel to userland RPC better. You judge if I succeeded or not :) Here a= re > some highlights: > > - Code footprint both in kernel clients and in userland daemons is reduce= d. > Example: gssd: 1 file changed, 5 insertions(+), 64 deletions(-) > kgssapi: 1 file changed, 26 insertions(+), 78 deletions(-) > 4 files changed, 1 insertion(+), 11 deletions(-) > - You can easily see all RPC calls from kernel to userland with genl(1): > # genl monitor rpcnl > - The new transport is multithreaded in kernel by default, so kernel clie= nts > can send a bunch of RPCs without any serialization and if the userland > figures out how to parallelize their execution, such parallelization wo= uld > happen. Note: new rpc.tlsservd(8) will use threads. > - One ad-hoc single program syscall is removed - gssd_syscall. Note: > rpctls syscall remains, but I have some ideas on how to improve that, t= oo. > Not at this step though. > - All sleeps of kernel RPC calls are now in single place, and they all ha= ve > timeouts. I believe NFS services are now much more resilient to hangs. > A deadlock when NFS kernel thread is blocked on unix socket buffer, and > the socket can't go away because its application is blocked in some oth= er > syscall is no longer possible. > > The code is posted on phabricator, reviews D48547 through D48552. > Reviewers are very welcome! > > I share my branch on Github. It is usually rebased on today's CURRENT: > > https://github.com/glebius/FreeBSD/commits/gss-netlink/ > > Early testers are very welcome! I think I've found a memory leak, but it shouldn't be a show stopper. What I did on the NFS client side is: # vmstat -m | fgrep -i rpc # mount -t nfs -o nfsv4,tls nfsv4-server:/ /mnt # ls --lR /mnt --> Then I network partitioned it from the server a few times, until the TCP connection closed. (My client is in bhyve and the server on the system the bhyve instance is running in. I just "ifconfig bridge0 down", waited for the TCP connection to close "netstat --a" then "ifconfig bridge0 up"= . Once done, I # umount /mnt # vmstat -m | fgrep -i rpc and say a somewhat larger allocation count The allocation count only goes up if I do the network partitioning and only on the NFS client side. Since the leak is slow and only happens when the TCP connection breaks, I do not think it is a show stopper and one of us can track it down someday. Other than that, I have not found any problems that you had not already fixed, rick > > -- > Gleb Smirnoff > From nobody Tue Jan 28 11:23:45 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 4Yj2wk486nz5mTmp for ; Tue, 28 Jan 2025 11:23:50 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from cm0.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yj2wj23jfz3wrc for ; Tue, 28 Jan 2025 11:23:49 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd-current@dino.sk designates 84.245.65.72 as permitted sender) smtp.mailfrom=freebsd-current@dino.sk; dmarc=none Received: from dino.sk ([84.245.95.254]) (AUTH: LOGIN milan, TLS: TLSv1.3,256bits,TLS_AES_256_GCM_SHA384) by cm0.netlabit.sk with ESMTPSA id 00000000022366B6.000000006798BE42.00002001; Tue, 28 Jan 2025 12:23:46 +0100 Date: Tue, 28 Jan 2025 12:23:45 +0100 From: Milan Obuch To: freebsd-current@freebsd.org Subject: Re: UFS bad inode, mangled entry on Alder Lake-N(100) Message-ID: <20250128122345.74075269.25648751.10101138@dino.sk> In-Reply-To: <6530f044-486d-4128-9e23-ee03e6686aa9@yamagi.org> References: <6530f044-486d-4128-9e23-ee03e6686aa9@yamagi.org> X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.3) 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-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:5578, ipnet:84.245.64.0/18, country:SK]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dino.sk]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4Yj2wj23jfz3wrc On Mon, 27 Jan 2025 19:28:28 +0100 Yamagi wrote: > Hi, > > sounds like the Alder Lakes PCID bug in N100 flavor. On the small > cores the INVLPG instruction is broken, failing to flush all > (global?) TLP entries leading to cache corruption. FreeBSD has a work > around for > that: https://cgit.freebsd.org/src/commit/?id=cde70e312c3fde5b37a29be1dacb7fde9a45b94a > > However that work around never fully solved the problem on the N100 > series. My own N100 board was never stable with PCID enabled and > there are several other reports of the same problems. For example > https://lists.freebsd.org/archives/freebsd-current/2023-August/004116.html > > Since Linux went with disabling PCID all together on all Alder Lake > and Raptor LAKE CPUs, I did the same by setting > vm.pmap.pcid_enabled=0 in loader.conf. Since I did that the system is > running fine. > > The Linux commit disabling PCID is here: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ae8373a5add4ea39f032563cf12a02946d1e3546 > > A microcode update might also help. I didn't test the updates > released by Intel since early last year so I don't know for sure. > It looks like the right thing, in my case adding vm.pmap.pcid_enabled=0 to /boot/loader.conf helps. I consider this easier than installing port for microcode update... That being said, could someone add some more pro/cons for those two approaches? Additionally, I am using M.2 SATA drive at the moment. While NVMe drive worked to some extent, if fsck was necessary for some reason, it was unpleasant - some 'waiting for nvme reset' event occured, this led to nvme drive detach, and the only way to fix it was unscrew the drive, put it in USB-NVMe converter, do fsck via USB drive, then mount it back into box... not acceptable. Regards, Milan From nobody Tue Jan 28 12: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 4Yj4xR2FHPz5mckl for ; Tue, 28 Jan 2025 12:54:35 +0000 (UTC) (envelope-from eduardo@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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yj4xR06KXz3KpV for ; Tue, 28 Jan 2025 12:54:35 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738068875; 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=uTXdrlpDJ9hqCLvPHZ5Zw9x0szAi7H1u6L7LpLNMsDE=; b=VFticwYdJNk+dsmf7CiD+oZaca7LMHYs+nH+0NXRb8O3TXSv/Zc3BXIphPKpDKh+n8ukZ3 epZon5EXtHVtguJjeocIIDx4iXYKg8JKLuAcIKIg2csHAjAcEcKUM4N0OnxfJrEmL+JLUg 172730xKmaGLIe0i3a6gc8AwoLW6suL8DpzzHEv3K8mhchyGYZQXf8EK3m3j4vz6Bn0qAf 4Qxmo8nXJNLlfQ2u99QoHudYuCbkNesTm/rNT+UmwxKIRHKn+aPinwGu5q7w/PZ8rKKUxR ilt8Pb2cDQyIZQ7ie6aGzLLOB62I7w4EWuwXV0wXT6Ylf9c8utwguSxBD/+BIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738068875; 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=uTXdrlpDJ9hqCLvPHZ5Zw9x0szAi7H1u6L7LpLNMsDE=; b=uiWNVNYPxIs7KL731GqipJJ+R1sn750q4nZZUY6NWSCtvUsMwVpA5skYbzv7P8eWdtf+hp NpocE/islliQ9bw4tUbTwEFrwzfM+I5Z/VkiSoGmS6VYDZl4nWfDl12CkXwb7srnfEAf/v fH9nK66h4yTtQgxABdGMRkaHtSEUFuKSfCYjnXIwMUbufTCm2yFc/hqQFwPuZyoK84CQ/V c0+iVdIJIURiiPGKoSguPbYyfTzJ9zFcOfPYU9XZqptwCFyOzh73/CQ7Uwibiz4gRWcXiI jvGsb/fZx9qvscfb1DII3zuhlgOTStTlBPOJIFGWl+VqtyZY9iJjdp4R8Pf6ag== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738068875; a=rsa-sha256; cv=none; b=LmEfMXFqUU3MiEDt4CJHEHJtdUF+PGvN6hyUw+GR0eigt9nwwpem/vTc5ssQcStofTGZP9 pOUKfABXLgdS7ZLK5ry5Ezc6/j5d4cZHCrL+s/JAhgCwxCATvXU2SVYjXrxdetSVoDeUGC r8se0yr1oYBJWXBlgCqDm7q3MWPlsilAT0Ob9E2HZNJeUgwav66LovlfRpcoaAu819XuHo s3ZfVN+CdEU7LX+My+Vd/5sIxwN5sPV18O+ve0oDFbTmiNDmMZhusMxF3ksIH+sT9ASd4y U9SFXBgcPutB0+tvjL0z+0pPnOknrSIgY2EKybZcipD2pFUFsS+NweP88AhPbA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from mail-qv1-f41.google.com (mail-qv1-f41.google.com [209.85.219.41]) (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)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Yj4xQ6KDBz10X7 for ; Tue, 28 Jan 2025 12:54:34 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-qv1-f41.google.com with SMTP id 6a1803df08f44-6d8983825a3so5740346d6.0 for ; Tue, 28 Jan 2025 04:54:34 -0800 (PST) X-Gm-Message-State: AOJu0Yzp7WOS72KSw91MFrCgEcdtKk+K6CCt+CucWf/ZeZSRW1GNNn3e ZAxC4Bz6ASksshNUl9njsVi0qAolvRUDKivD6ATzFmecNof3XG98hiTnjzciK7ylkR4aNSbpo1j zv0I0qKYP4Elasi9Q6azcuYZ1tt4= X-Google-Smtp-Source: AGHT+IEfamRW4fO2MnQ5fyRqx0MgYrQ6KANb2sDbOh1oUThWv7NsNYpxxRGLr+6lHfQL0KVpipUMcdqi/u2glcSB83A= X-Received: by 2002:a05:6214:1253:b0:6d8:98a4:cc5c with SMTP id 6a1803df08f44-6e1b19d8eafmr245340036d6.0.1738068874241; Tue, 28 Jan 2025 04:54:34 -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 From: Nuno Teixeira Date: Tue, 28 Jan 2025 12:54:23 +0000 X-Gmail-Original-Message-ID: X-Gm-Features: AWEUYZk_-qVJoukRh8nAMQP70nWkpIEMEVYz2_lzvKRLyYgxU-brREQD3bqqT8s Message-ID: Subject: WITH_META_MODE: base clang excessive compiles To: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000d83006062cc3b1e4" --000000000000d83006062cc3b1e4 Content-Type: text/plain; charset="UTF-8" Hello, Just to check that I'm using the correct setting for WITH_META_MODE since almost everytime I update main tree, I got clang compiled. Is that normal? -- $ kldstat | grep filemon 11 1 0xffffffff849f2000 3250 filemon.ko /etc/src-env.conf: WITH_META_MODE=yes --- (maybe usefull to show this as well) /etc/src.conf: WITH_MALLOC_PRODUCTION=yes WITHOUT_LLVM_ASSERTIONS=yes /etc/make.conf: KERNCONF=GENERIC-NODEBUG DEVELOPER=yes DEVELOPER_MODE=yes PORTSDIR=/home/nunotex/Work/freebsd/ports/main DISTDIR=/Arq/DISTFILES Thanks, -- Nuno Teixeira FreeBSD UNIX: Web: https://FreeBSD.org --000000000000d83006062cc3b1e4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

Just to check that I&= #39;m using the correct setting for WITH_META_MODE since almost everytime I= update main tree, I got clang compiled.

Is that n= ormal?

--
$ kldstat | grep filemon11 =C2=A0 =C2=A01 0xffffffff849f2000 =C2=A0 =C2=A0 3250 filemon.ko
<= div>
/etc/src-env.conf:
WITH_META_MODE=3Dyes
<= div>---

(maybe usefull to show this as well)
/etc/src.conf:
WITH_MALLOC_PRODUCTION=3Dyes
WITHOUT_L= LVM_ASSERTIONS=3Dyes

/etc/make.conf:
KER= NCONF=3DGENERIC-NODEBUG
DEVELOPER=3Dyes
DEVELOPER_MODE=3Dyes
PORTS= DIR=3D/home/nunotex/Work/freebsd/ports/main
DISTDIR=3D/Arq/DISTFILES

Thanks,
--
Nuno Tei= xeira
FreeBSD UNIX:=C2=A0 <eduardo@FreeBSD.org>=C2=A0 =C2=A0Web:=C2=A0 https://Fr= eeBSD.org
--000000000000d83006062cc3b1e4-- From nobody Tue Jan 28 16:46:04 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 4YjB4b4B2Wz5lkmG for ; Tue, 28 Jan 2025 16:46:07 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjB4b3Q0xz3yKk; Tue, 28 Jan 2025 16:46:07 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738082767; 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:references:references; bh=8DpA+PtgFzqkY5Qx7ZQDzklfAsijSlvmF8qwIBAVSKY=; b=KcwiJ94iKivWA3xC2hlMKqbXGSg4v9E3+Jc2rzY3qVTYAMNF/YEDWOjXFKiVuwCuVzSFFe 6MWulNFUbx105DfboD0JBmg2rhAvtHRgdRcW5detV+pAvfw1aGFfZ1vTiiRkK5S9rHN81b RH0cWZo04L6HAfDGnfPo4OO5h0zOXuERXd0u8txMbXAMb9+9Xi8crB5kpBTYt/kOSaO76q Zp/C8sE5exf4S9JyPEnRqtyWPyuhA2ThQN3eaGuuQtn2i0Nn6UvDdcFF5VA745iTh5d6Bu TbGyXTcr2ufWAAahsLl2LciZpVqVAzQQdzfIFlBxHf3sQgoI83N8bFzOXnw7vQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738082767; 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:references:references; bh=8DpA+PtgFzqkY5Qx7ZQDzklfAsijSlvmF8qwIBAVSKY=; b=pj5p6LZNr17bS160P2rgZZDQyQFsVAbWp61+nI5xPbbpMpnOwcGSQd/JNXqGgmkje/T9CB iiSWzOyIHIPYxTfJ02RIVpyYibKRKausJ9MsPx6gyalZOp1d8bg+F2cH5P+byaqg0bReBW 0ukKVMkN+QXXA+I89QQyHEH3uYO3Mn5V9yakp8i/WQTF/fkd6uP3qjeA68CvdRfEY3YsqC enTnKHqK7yVLOPqEYbyV2TvMxWdkmAc4p+Zen2vU2VqcXSvxOlD69jG1G1Hbgko1x/cwOo IZ/CbLPITDIhb26I0NV4iT9qJEyRBy/O9/ihVMNajz57m07MbjWxb1trY3v+Og== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738082767; a=rsa-sha256; cv=none; b=x+OJVYDr3Rkg/WJ888oXmgdy+zb0za/HSna7O7jXWzFJMoUhDQyXKj9vRbZi2hJB/SM27w u9Eyk2p5mIcuF5Mcs8lcOcNgRDAuW1DzbAXFLKdeSA9ZEEmxbsbbnM3DY5lQw5gduDMbMx I0l2cIv66Ez0k7LdHdgN048R30tNVU1/g7Odz/VHXliE8f4Z+iHgHrC4jIHyGrq4cN+0FS /4ZLBuAegw3EoavdbInBWe30eFXfGfbHoTIquT+nmdrRHk39eunzFXuIR8OVluQCc2hDyy kIVs39Ld7CY319tGmK9Ji32eN2YIutilC1kj9xp9Zm/N09LK7RqSCYVlP8gL7w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YjB4Z6dRQz14hh; Tue, 28 Jan 2025 16:46:06 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Tue, 28 Jan 2025 08:46:04 -0800 From: Gleb Smirnoff To: Alexander Leidinger , allanjude@freebsd.org Cc: Current FreeBSD Subject: Re: Difference in "netstat -rn" output in the last 2 months 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: On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote: A> something has changed in the output of "netstat -rn" between A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed as A> "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks some tools A> (e.g. iocage). Iocage uses python, I'm not sure if it uses netstat or some A> other interface, so it may not be directly related to netstat itself but A> could be related to some other stuff (netlink maybe?). A> A> Does this ring a bell for someone? This is very likely changed by 9206c79961986c2114a9a2cfccf009ac010ad259. Allan, may be make exclusion for the "default" to keep POLA? Otherwise, indeed at time of 15.0-RELEASE we will receive some negative feedback :) Maybe double -nn should introduce new behavior? -- Gleb Smirnoff From nobody Tue Jan 28 17:19:57 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 4YjBr05ZJyz5lpF6 for ; Tue, 28 Jan 2025 17:20:16 +0000 (UTC) (envelope-from freebsd-current-freebsd-org111@ketas.si.pri.ee) Received: from mail.ketas.si.pri.ee (d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13e8:21e:bff:fea2:d004]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjBqz3NH1z3Hnt for ; Tue, 28 Jan 2025 17:20:15 +0000 (UTC) (envelope-from freebsd-current-freebsd-org111@ketas.si.pri.ee) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ketas.si.pri.ee header.s=ketas-si-pri-ee-20240416002854-4096 header.b=J5MnNbV6; spf=pass (mx1.freebsd.org: domain of freebsd-current-freebsd-org111@ketas.si.pri.ee designates 2001:7d0:8437:13e8:21e:bff:fea2:d004 as permitted sender) smtp.mailfrom=freebsd-current-freebsd-org111@ketas.si.pri.ee; dmarc=pass (policy=reject) header.from=ketas.si.pri.ee X-Original-To: freebsd-current@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ketas.si.pri.ee; s=ketas-si-pri-ee-20240416002854-4096; t=1738084798; bh=Rd5i6otI4Tr/+NTW0+nwgDLo5vYX/1JAD9NCjhA78gM=; h=Date:From:To:Subject:In-Reply-To:References; b=J5MnNbV6x88mXr4oMtcucp9GeRj/luDjHDdGhLesIqHjG2bguHij1qmulGSfFtBoH cdEmw6UAmhITHrIORpua4NTLztq66IZjcn/rgzxP4k7LH7+fQqW97AKM9zbIEqPKfK qgroUH76RPlGZjLpica4YzL7C5cq0+nHFzuViKfFGYaMJAMhIPuwiFP/ZNE/8W0o6s fBSWGrXt5q17w7QrafZgjJKnJ1+n4z7CqVaP6CTD67irwndM3/SODtODgkJXN61nP+ F5+s9IwjaLiusO65nG/mM3kJ4Hwz36nYBxiIVGlDh/GNYU2GsgLq2aMMfWzJsmLNss KTIycY01AxfzLIZPBg1IztzfI4rntzpB7OGkzKCESEDhZXUkKE3QcH+zG9wyFWmaHH XeNfah1RHI31xZq/LtzYDVHCQ9J5tLgU9ego9UyxnYKhlWguLM+S/IZXV8zEIjOiau O4VGaZtsXWQKtwK7cn/Dq48BUs8XprjAr6EuHeH2ijsMW6B8otJ3Cc+59tVvBnqFej HkDC8ZvCHOW7JqLOfcdv9PxbAletraABNMiZOdH6t0H+qPVlkC9LdhTfnJ3Hrze9J4 wncOMDGh46gs1msOVPmUQKe82O8MU0sjvJ1vy52kM8dM0C/hKjf4MUZpmJ/Gj8JNla J5dRUHg8jQkEAJFkJ5xpgtKw= Received: from [IPv6:::1] (0114-0000-0000-0000-13c8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13c8::114]) (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) (No client certificate requested) by mail.ketas.si.pri.ee (Postfix) with ESMTPSA id B090B59B632 for ; Tue, 28 Jan 2025 19:19:58 +0200 (EET) Date: Tue, 28 Jan 2025 19:19:57 +0200 From: Sulev-Madis Silber To: freebsd-current@freebsd.org Subject: Re: Difference in "netstat -rn" output in the last 2 months User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: <3D8952B3-8F43-4F7A-B906-6C4EDF4409BD@ketas.si.pri.ee> 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-Spamd-Result: default: False [-0.79 / 15.00]; HFILTER_HOSTNAME_5(3.00)[d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.992]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; ONCE_RECEIVED(0.20)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ketas.si.pri.ee:+] X-Spamd-Bar: / X-Rspamd-Queue-Id: 4YjBqz3NH1z3Hnt while why is it 0=2E0=2E0=2E0 and not 0=2E0=2E0=2E0/0, 0/0 or 0? why is it ::/0 not ::, 0:0:0:0:0:0:0:0, 0:0:0:0:0:0:0:0/0, 0000:0000:0000:= 0000:0000:0000:0000:0000 or 0000:0000:0000:0000:0000:0000:0000:0000/0? realistically we need automated interfaces too=2E parsing everything out o= f human ui is very error prone! yet easy, hence why the changes are bad btw, half of tools (still?) crap out and do wharever silently when i speci= fy things like 10/8=2E hint: it doesn't expand into 10=2E0=2E0=2E0/8=2E tha= t's non-pola'ish too From nobody Tue Jan 28 18:05:03 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 4YjCrK62sXz5lslb for ; Tue, 28 Jan 2025 18:05:37 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjCrJ3sWvz3Pj1; Tue, 28 Jan 2025 18:05:36 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=HVxdl66O; spf=pass (mx1.freebsd.org: domain of Alexander@Leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@Leidinger.net; dmarc=pass (policy=quarantine) header.from=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=1738087533; 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:references:references; bh=MokIPqGOQD128IM5w70rxMyXgjrEnOtFm8AW/9H5Dl0=; b=HVxdl66OiVivQ8oad7zUH3zUieg4xl47GY4YnTDvFgXVOtlNyQ9yOLJRM4tfOTqzG+/Jxu OLjnHY6ac+01/Y0fpfvVpeHx1BXZUlDvCm9jYuCxVYko7E5A7Jsvp7olWmFa/6xFL0eyXJ SWLSgayPkMt69yZi35OBqY89bDPNaGDmx0KXaDo1QZD43pldNplEaHHpFjnxOXD2vTJkHb OTdFfJlXLVEylvpg6ZCuEKDr5REOJNY24L3dzqQxOWRKWGjSM/qY/5pxnjkW+zAK2XmFbE IYhqz2eaoZsG39j2rgMGOkDv1QsbBgXnNhUk1iqMwgUgn6R51VHCB37AGloOCg== Date: Tue, 28 Jan 2025 19:05:03 +0100 From: Alexander Leidinger To: Maxim Sobolev Cc: Gleb Smirnoff , Allan Jude , Current FreeBSD Subject: Re: Difference in "netstat -rn" output in the last 2 months In-Reply-To: References: Message-ID: <382bafe6ff9c04ab72d9e0c6f7fb39c3@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_d1d3067cbd48107adf43127468117635"; micalg=pgp-sha256 X-Spamd-Result: default: False [-4.69 / 15.00]; SIGNED_PGP(-2.00)[]; HTTP_TO_IP(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.69)[-0.692]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; ONCE_RECEIVED(0.10)[]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE]; DKIM_TRACE(0.00)[leidinger.net:+]; RCPT_COUNT_THREE(0.00)[4]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_MATCH_ENVRCPT_SOME(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-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4YjCrJ3sWvz3Pj1 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_d1d3067cbd48107adf43127468117635 Content-Type: multipart/alternative; boundary="=_d34c0128669efe86a6a3541dfe510c34" --=_d34c0128669efe86a6a3541dfe510c34 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed Am 2025-01-28 18:32, schrieb Maxim Sobolev: > I also think this should be reverted back to default. "-n" refers to IP > to name functionality, "default" is clearly a special case. If someone > wants it, some other option can be added to emit 0.0.0.0/0 [1] (not > sure why but ok). This was discussed in the review referenced in the commit. The -nn proposal was there too. Personally I agree with the rationales in favor of "-nn". Bye, Alexander. > -Max > > On Tue, Jan 28, 2025, 5:46 PM Gleb Smirnoff > wrote: > >> On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote: >> A> something has changed in the output of "netstat -rn" between >> A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not >> listed as >> A> "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks >> some tools >> A> (e.g. iocage). Iocage uses python, I'm not sure if it uses netstat >> or some >> A> other interface, so it may not be directly related to netstat >> itself but >> A> could be related to some other stuff (netlink maybe?). >> A> >> A> Does this ring a bell for someone? >> >> This is very likely changed by >> 9206c79961986c2114a9a2cfccf009ac010ad259. >> >> Allan, may be make exclusion for the "default" to keep POLA? >> Otherwise, >> indeed at time of 15.0-RELEASE we will receive some negative feedback >> :) >> >> Maybe double -nn should introduce new behavior? >> >> -- >> Gleb Smirnoff -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF Links: ------ [1] http://0.0.0.0/0 --=_d34c0128669efe86a6a3541dfe510c34 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

Am 2025-01-28 18:32, schrieb Maxim Sobolev:

I also think this should be reverted back to default. "-n= " refers to IP to name functionality, "default" is clearly a special case. = If someone wants it, some other option can be added to emit 0.0.0.0/0 (= not sure why but ok).
 
This was discussed in the review referenced in the commit= =2E The -nn proposal was there too. Personally I agree with the rationales = in favor of "-nn".
 
Bye,
Alexander.
 
-Max

On Tue, Jan 28, 2025, 5:46=E2=80=AF= PM Gleb Smirnoff <glebius@freebsd.org> wrote:
On Sun, Jan 26, 2025 at 04:58:57PM += 0100, Alexander Leidinger wrote:
A> something has changed in the ou= tput of "netstat -rn" between
A> 2024-11-23-195545 and 2025-01-22-1= 51306. The default route is not listed as
A> "default" anymore, but= with "0.0.0.0" resp. "::/0". This breaks some tools
A> (e.g. iocag= e). Iocage uses python, I'm not sure if it uses netstat or some
A> = other interface, so it may not be directly related to netstat itself butA> could be related to some other stuff (netlink maybe?).
A> =
A> Does this ring a bell for someone?

This is very like= ly changed by 9206c79961986c2114a9a2cfccf009ac010ad259.

Allan, m= ay be make exclusion for the "default" to keep POLA? Otherwise,
indeed= at time of 15.0-RELEASE we will receive some negative feedback :)
Maybe double -nn should introduce new behavior?

--
Gleb= Smirnoff


--
= http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http:/= /www.FreeBSD.org    n= etchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF
--=_d34c0128669efe86a6a3541dfe510c34-- --=_d1d3067cbd48107adf43127468117635 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmeZHGEACgkQEg2wmwP4 2Ib70w//XBeEj3JBN0ofGWpsM9omHXGGhKlumr3FtlVtdWvHyIy2hlBt+2JXDXbU v4TN3O7SNnXah1hHd15F/4jScVTQWmMJQShTdASM+29kGOR/bveNG63HyS6Q7xb9 Y1HdMXQ6hysehbDNBmmiQyZlcab5hvOIY7nqtUOSQ7Eh3M6SPv1ZcZJrkLrerEVB 7JAI4kvK7WgvUkYqhCypfFfFpII+bOyT2zdcHp3OMd8MfkkEwyB3Dd6xNIDy/thr /L9ospHngMy8rOiPVQ5LrkuC0Mg8YX6FlGLhOLIK3CmOmt/iCJLMJCihdz1k5YqF 0F805VQ/y0tfXFGZauFRvLfUVVUxwfhff5BeeoXG78NtcnRulmNyFGTliZK/nsE6 CSa/3htrflKfSZv9WyH7Dhf9cO2dWE8WWW1PElBjZMOuiBZ4b39KdBsiqQk5/DE9 7RQ+LmI47qFqfm62gF3mFSLTJFMqvYTV1LSHNSkrD1j9pgsCnF7AIjrmxNQL/wOc f6lSoU6hwwTGTxRvSOOjJIe6aSr7dDjW4qk1/c3c3moOvOTxPqxQZeSrmeoeN7Va 6PYfTFiFOjJpzA2hy+3z0QkxWWGp8bl1uo6P4FQNMBIXCYYXA9+8QVgs9iDOf4OJ Jo7xiyaH/+c/Z+O/AtpXNKq8vIzRNbaR6QRvZKvfYWhWj5NMNc8= =r/jQ -----END PGP SIGNATURE----- --=_d1d3067cbd48107adf43127468117635-- From nobody Tue Jan 28 18:12: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 4YjD0c264Lz5ltWH for ; Tue, 28 Jan 2025 18:12:48 +0000 (UTC) (envelope-from danfe@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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjD0c1WTrz3RF0; Tue, 28 Jan 2025 18:12:48 +0000 (UTC) (envelope-from danfe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738087968; 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:references:references; bh=sgBgFaAxFvdCij7BASY7gKVxCWD9zKXE6NyQIMWRB7Y=; b=u0d2/rBhN7AJf61vsWR+7mpYhOU2ct4Z8FmVAAgd19AT0j+zOVhzT1u8S5IWI+hlHv10pZ LfVuSBZ1lyhyAQk7eWHjb8udg7yrJOkKcLr8uO9qxSGUgHvxbrZS2Ttqqqu7F5nW5mOBul XEd5YCh+/eeCf+ylqY/1qz+00+pT5R66Rss8WuE3aT8YTEfEHl/XlS8O/aKsKZEjdBDFwY fms2TElg13Krk9iuEO80K7SAH69QlncLcUGk/AA58tZg0nkV8WH/Wzo7dRQTNm9n3XjCgp ap/eiMqty8C2Rjf5TSs/dp4dQgijbDgMbzYZiDPbYg4b0Hzi7AlGps/6//zafw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738087968; 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:references:references; bh=sgBgFaAxFvdCij7BASY7gKVxCWD9zKXE6NyQIMWRB7Y=; b=ECEeVRnh1+uzcdJJqSYmb8rFVGPVh2o7xIT9xzkdGuTPgnigTXPIHCs8Qxz5xpnmq2CCag jGrYjKfPpdprRP7MgGfW/hu6TL1Ty9Loqb0gm9iKvpsbwSQOOF6tCftBp7WkyKxpv90Kdn WEDSrOkOrsGtie1TJPaG1R9MMsW4+S/xJr9mA3XxMHHZoqwLPNdXNspwP3a+jFi/GWgZtz 4S96WEoKCh3XFnH6KTn1l3khOiGyyF9FtvSZHJagbxLC695qI0eqOW/oz9v7xgnF2dXQwX 9/F4KXHKep8SqMj2FMKWnz6C08oUXR0g+Xa2GGm2n6KTSNTYUy0LJLS2jin/ig== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738087968; a=rsa-sha256; cv=none; b=xmcB8foUfLIHm6gdZjDFaujGy5DvVqYoNxyJvDUx4PJjTlutFPwoGxAKlaCubJjbB02bql 48N9tNVKEXefVZgLfRvRH1bON/eJbTdJJCAlEBORFcCo7LR2+QXKYsIouxSjxAcW9ZYe7s hkXf+vxGRXjE0YZ+J8cHhio8TOgn2NA6Xf2RLKeuNaBw9EoxeQbaJCCDVDTxe6d/kLWDfL tqCWc9jPvnqkalHoZ6D4jnXaF+MXgJOLrSNqrqwI3AJG3nC6orHSOpbSTEqUCa1Cfo8Fdf tt0ZwHlCM/2qZZktx9QKsN30AXTnkMlYtb8va5BbPEQCvat2gyk03FbA3A43Nw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: by freefall.freebsd.org (Postfix, from userid 1033) id 236BDAFAC; Tue, 28 Jan 2025 18:12:48 +0000 (UTC) Date: Tue, 28 Jan 2025 18:12:48 +0000 From: Alexey Dokuchaev To: Gleb Smirnoff Cc: Alexander Leidinger , allanjude@freebsd.org, Current FreeBSD Subject: Re: Difference in "netstat -rn" output in the last 2 months 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: On Tue, Jan 28, 2025 at 08:46:04AM -0800, Gleb Smirnoff wrote: > On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote: > A> something has changed in the output of "netstat -rn" between > A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed as > A> "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks some tools > A> (e.g. iocage). Iocage uses python, I'm not sure if it uses netstat or some > A> other interface, so it may not be directly related to netstat itself but > A> could be related to some other stuff (netlink maybe?). > A> > A> Does this ring a bell for someone? > > This is very likely changed by 9206c79961986c2114a9a2cfccf009ac010ad259. > > Allan, may be make exclusion for the "default" to keep POLA? Otherwise, > indeed at time of 15.0-RELEASE we will receive some negative feedback :) I fully second this request. I was very much annoyed by this change, as "netstat -rn" is in my finger memory and seeing linuxish 0.0.0.0 instead of our usual "default" was totally unexpected and rather confusing. ./danfe From nobody Tue Jan 28 20:09:15 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 4YjGbC2WK5z5m3wN for ; Tue, 28 Jan 2025 20:09:27 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-pj1-f45.google.com (mail-pj1-f45.google.com [209.85.216.45]) (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 4YjGbC0gYCz3p6p for ; Tue, 28 Jan 2025 20:09:27 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-f45.google.com with SMTP id 98e67ed59e1d1-2ee989553c1so10386017a91.3 for ; Tue, 28 Jan 2025 12:09:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738094966; x=1738699766; 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=3anSG8TZy0LaV64jmxNH+YQ8Gl4pq3mwulnuXcv/6MA=; b=MxnGjmn4PgFlImkpd8m09T2odQIQ/GyF8qOEUB6Fr2mSoAUdfMCkpRAsr011oEJ4ms EcUvdZW19ZATAxqrpT58ToGizs801c5P9MPx11VGYVNqxUJtSpaxM8r0Wna1X4AArDFe tCPxYWrNUSO8uEvD1wQVpC+DUA1H4z26uov9FnfodbXnUCS1jI9xfESHRmMMjthUNg1R gO4IPQ+uu1wm+GH8ACJ9hscOBYS0QRiINqShyI41LSyhhMkCxRuehUrPD61VcqY0B8w/ drMg3ovXnxzxONE8MEwAvgjKD1VC/o4xo247NWLtJ1YFxbTv+EeWILmQ7d/uL1zCkJQl D/oQ== X-Forwarded-Encrypted: i=1; AJvYcCXhtlY+q6oYfkXc8YhE5s1TDKe5BAWmSaHDxZh0PlCEiSOampjdR5kIfwOEsn/rqpgi9P8JXDqDdwmhMl39hHI=@freebsd.org X-Gm-Message-State: AOJu0YwqmFXkSosvnutQVAoiRTS2ctyejO4x2SPxWcNBcbRg/wn8s+pY v/w/G+JCzT2K2tP5CyYIYyGb0dAG3FjlbbZz4JxReF1E32qcYUm21NnNFSOihdqp7f3o1hsccQ8 03IOSGGN5XOm5hlvqhsIyyytGcqgUlPP91imlow== X-Gm-Gg: ASbGncvS0oM9ycawKZNakLmVUJOTKYAPr46gXa22fcGPpfaROmpiob0rqiqGIt9bLxj Lkk44fnVzchDXyRzWgB4D6TL7AfN3xpgnY92q0hR/HG5mqYoBlaL/f4Z4RJYOSZrW1HzdUNN0 X-Google-Smtp-Source: AGHT+IHXQUzPJKXHsRWa0GWENVeOqZ3KpBE+9czP417eYtB64IRXA0zEo8O+lPevsrqtR9jT1UGwE1dW931DUDh+AKA= X-Received: by 2002:a17:90b:518d:b0:2ee:aef4:2c5d with SMTP id 98e67ed59e1d1-2f83ac5c201mr411968a91.26.1738094965794; Tue, 28 Jan 2025 12:09:25 -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: <382bafe6ff9c04ab72d9e0c6f7fb39c3@Leidinger.net> In-Reply-To: <382bafe6ff9c04ab72d9e0c6f7fb39c3@Leidinger.net> From: Maxim Sobolev Date: Tue, 28 Jan 2025 21:09:15 +0100 X-Gm-Features: AWEUYZmIV7hVtE0YoosGfpxiakG9aqZeiRvWWE73OHD3v7Tq9ngxcQcAwfejUd4 Message-ID: Subject: Re: Difference in "netstat -rn" output in the last 2 months To: Alexander Leidinger Cc: Gleb Smirnoff , Allan Jude , Current FreeBSD Content-Type: multipart/alternative; boundary="00000000000005c5c7062cc9c5cc" X-Rspamd-Queue-Id: 4YjGbC0gYCz3p6p X-Spamd-Bar: ---- 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:209.85.128.0/17, country:US] --00000000000005c5c7062cc9c5cc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Discussed between 3 people, creating the problem for 3,000. Great! -Max On Tue, Jan 28, 2025, 7:05=E2=80=AFPM Alexander Leidinger wrote: > Am 2025-01-28 18:32, schrieb Maxim Sobolev: > > I also think this should be reverted back to default. "-n" refers to IP t= o > name functionality, "default" is clearly a special case. If someone wants > it, some other option can be added to emit 0.0.0.0/0 (not sure why but > ok). > > > This was discussed in the review referenced in the commit. The -nn > proposal was there too. Personally I agree with the rationales in favor o= f > "-nn". > > Bye, > Alexander. > > > -Max > > On Tue, Jan 28, 2025, 5:46=E2=80=AFPM Gleb Smirnoff = wrote: > > On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote: > A> something has changed in the output of "netstat -rn" between > A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not > listed as > A> "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks some > tools > A> (e.g. iocage). Iocage uses python, I'm not sure if it uses netstat or > some > A> other interface, so it may not be directly related to netstat itself b= ut > A> could be related to some other stuff (netlink maybe?). > A> > A> Does this ring a bell for someone? > > This is very likely changed by 9206c79961986c2114a9a2cfccf009ac010ad259. > > Allan, may be make exclusion for the "default" to keep POLA? Otherwise, > indeed at time of 15.0-RELEASE we will receive some negative feedback :) > > Maybe double -nn should introduce new behavior? > > -- > Gleb Smirnoff > > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > --00000000000005c5c7062cc9c5cc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
<sarcasm>Discussed between 3 people, creating the p= roblem for 3,000. Great!</sarcasm>

-Max

On Tue, Jan 28, 2025, 7:05=E2=80= =AFPM Alexander Leidinger <Al= exander@leidinger.net> wrote:

Am 2025-01-28 18:32, schrieb Ma= xim Sobolev:

I also think this should be reverted back to default. &qu= ot;-n" refers to IP to name functionality, "default" is clea= rly a special case. If someone wants it, some other option can be added to = emit 0.0.0.0/0 (not sure why but ok).
=C2=A0
This was discussed in the review referenced in the commit= . The -nn proposal was there too. Personally I agree with the rationales in= favor of "-nn".
=C2=A0
Bye,
Alexander.
=C2=A0
-Max

On Tue, Jan 28, 2025, 5:46=E2=80=AFPM Gleb Smirnoff <glebius@freebsd.org> wrote:
On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrot= e:
A> something has changed in the output of "netstat -rn" = between
A> 2024-11-23-195545 and 2025-01-22-151306. The default route= is not listed as
A> "default" anymore, but with "0.0.= 0.0" resp. "::/0". This breaks some tools
A> (e.g. ioc= age). Iocage uses python, I'm not sure if it uses netstat or some
A&= gt; other interface, so it may not be directly related to netstat itself bu= t
A> could be related to some other stuff (netlink maybe?).
A> =
A> Does this ring a bell for someone?

This is very likely cha= nged by 9206c79961986c2114a9a2cfccf009ac010ad259.

Allan, may be make= exclusion for the "default" to keep POLA? Otherwise,
indeed a= t time of 15.0-RELEASE we will receive some negative feedback :)

May= be double -nn should introduce new behavior?

--
Gleb Smirnoff


--
= http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F318= 30F9F2772BF
http://www.FreeBSD.org =C2=A0 =C2=A0n= etchild@FreeBSD.org =C2=A0: PGP 0x8F31830F9F2772BF
--00000000000005c5c7062cc9c5cc-- From nobody Tue Jan 28 20:33: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 4YjH7132hSz5m5bS for ; Tue, 28 Jan 2025 20:33:33 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 4YjH702tvbz3tKM for ; Tue, 28 Jan 2025 20:33:32 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=E1j5TOcH; spf=pass (mx1.freebsd.org: domain of ianfreislich@gmail.com designates 2607:f8b0:4864:20::b35 as permitted sender) smtp.mailfrom=ianfreislich@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-e580d6211c8so10251365276.1 for ; Tue, 28 Jan 2025 12:33:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738096411; x=1738701211; darn=freebsd.org; h=content-transfer-encoding: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=p4kmPpjdDr7FWH0MCQ7bMgmHMwxbwthfX8hTiTi2PUQ=; b=E1j5TOcH71RGMwnaLWSygnKf0/vAUICaoS+H0sXOfvSoDomMgt8I+1gRx2jnwB2sEH zLQiX9Gd79AArS5KZHGcYKvub29I6x5doqan9uzm/Ug6LLL84Xkmpi3TklgkVzJSnP5h 8aVHD72oXrZc2VpE0euTvynOdu+QfSKDGLT2Cuo4Vto+AcqLHaJWRzoTJFRkFZc+FeTs sipFqfD3HN1TmQdcphb0vp8jLCUzTFNdOCEpMCgDIdXouGBJ2Hp5/2qijDhoyTCp4dfX 4P3HY0uL/0LSEb9v53NtEi/FBK5cUyyo2ntoxwrcg//POa44oCICC9zNXo4WajytdYVF 4CRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738096411; x=1738701211; h=content-transfer-encoding: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=p4kmPpjdDr7FWH0MCQ7bMgmHMwxbwthfX8hTiTi2PUQ=; b=nCo/T8xfoLaRoV8tllHAXstzHghHbKCk3RdfZpeZ3gYnLXPmt1aGGRtcthSSrNp41k QB805EJn5ToQTQ9he2F2GGG4EHkkeM/RoRB8ZNqRdMCB6uNUZ/G2sLyRyBdkaPnA+rje HVtvwToO7mjlLuA78Z+Ek9+iGMGutartaC/0U5i7xIvTwBuhavzYuAJvJ+SFSYfmzM/G 9OPoN4F3AFFli0qqCNEFeJDKOsoO0SfTBP9S8vpOWGesY0mhGq2aq1IiiQMyCkNfPXTG O5TCOllI8TMxLWnR4gbWYyjbeaSUI+3AkKlYcMbQZ1HWOtH5LwdPD1D12iqAXoN4wvxV S5zQ== X-Gm-Message-State: AOJu0Yz2Fiix9Dc2644V80QYkvryiVGCshgJBSJKwQkKYmuRl/d72/nm uAKxLuEBP1Wk1KVPDXuUNi9/9kOmcFh6EWGhboLmDUjqiTKFj07rfKfukQ== X-Gm-Gg: ASbGnctCuL9CsCRBWOHczGOPdhU+opIkvkDVo4mpf4Suo7L7jmQNabTI09MUyVQOHEG /RA/AUTV0tiNw1cOhP+nBiG26D3RTqYrp1hkq/pG0/rONqQjiodK2NeENA9xS47YVQjO8m5O9P/ XcN9702GV/PICmTpojFuxrMme3U3DaO3l8vTlPQtk3UB+buinDbLSTgMrjj6J4vRp1ahl/fwcD5 a1TW2RUtftHPMT5LBxvY2aAOOsCRYePBRox0HJ+L+xi+KABBg6IB0DsKY4Gqea0tssG9YbL5LAf LETDyxcd46ITj40nzuOXYz7VxtqljqC+oSrCCvkd5eDf2sT/B7MXifwSBHbLQax6haqQzgY= X-Google-Smtp-Source: AGHT+IHghMFRhw7lQYPjO6yzA4AbGyjuZ50wwiNy0pV3EW6huq/vcKasI5cP6Ui64PhuzH3ay8gN+w== X-Received: by 2002:a05:690c:6809:b0:6ef:63cb:61d0 with SMTP id 00721157ae682-6f7a834ec9amr3510477b3.10.1738096410870; Tue, 28 Jan 2025 12:33:30 -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-6f75787730fsm20126977b3.1.2025.01.28.12.33.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Jan 2025 12:33:30 -0800 (PST) Message-ID: <6024769d-1cac-439b-874d-c624112d30c9@gmail.com> Date: Tue, 28 Jan 2025 15:33:30 -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: UFS bad inode, mangled entry on Alder Lake-N(100) To: freebsd-current@freebsd.org References: <6530f044-486d-4128-9e23-ee03e6686aa9@yamagi.org> <20250128122345.74075269.25648751.10101138@dino.sk> Content-Language: en-US From: Ian FREISLICH In-Reply-To: <20250128122345.74075269.25648751.10101138@dino.sk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.37 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_MEDIUM(-0.39)[-0.387]; 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)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b35:from] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4YjH702tvbz3tKM On 2025-01-28 06:23, Milan Obuch wrote: > On Mon, 27 Jan 2025 19:28:28 +0100 > Yamagi wrote: > >> Hi, >> >> sounds like the Alder Lakes PCID bug in N100 flavor. On the small >> cores the INVLPG instruction is broken, failing to flush all >> (global?) TLP entries leading to cache corruption. FreeBSD has a work >> around for >> that: https://cgit.freebsd.org/src/commit/?id=cde70e312c3fde5b37a29be1dacb7fde9a45b94a >> >> However that work around never fully solved the problem on the N100 >> series. My own N100 board was never stable with PCID enabled and >> there are several other reports of the same problems. For example >> https://lists.freebsd.org/archives/freebsd-current/2023-August/004116.html >> >> Since Linux went with disabling PCID all together on all Alder Lake >> and Raptor LAKE CPUs, I did the same by setting >> vm.pmap.pcid_enabled=0 in loader.conf. Since I did that the system is >> running fine. >> >> The Linux commit disabling PCID is here: >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ae8373a5add4ea39f032563cf12a02946d1e3546 >> >> A microcode update might also help. I didn't test the updates >> released by Intel since early last year so I don't know for sure. >> > > It looks like the right thing, in my case adding vm.pmap.pcid_enabled=0 > to /boot/loader.conf helps. I consider this easier than installing port > for microcode update... > > That being said, could someone add some more pro/cons for those two > approaches? > > Additionally, I am using M.2 SATA drive at the moment. While NVMe drive > worked to some extent, if fsck was necessary for some reason, it was > unpleasant - some 'waiting for nvme reset' event occured, this led to > nvme drive detach, and the only way to fix it was unscrew the drive, > put it in USB-NVMe converter, do fsck via USB drive, then mount it back > into box... not acceptable. I chose microcode but that was hard to do because I only have one nvme slot and the installer panicked trying to install the package at the final part of the install. I had to install onto an SD and then use another FreeBSD install to do a pkg chroot install onto that temporary media and then use that to boot with the firmware update and chroot install the firmware and edit loader.conf on the nvme. The microcode update fixed it for me. I inferred from reading that enable PCID might have a performance advantage. Ian From nobody Tue Jan 28 20:37: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 4YjHCf3Jwjz5m5s4 for ; Tue, 28 Jan 2025 20:37:34 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjHCd75p7z3vRq; Tue, 28 Jan 2025 20:37:33 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738096654; 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=WOwL3BCqmrduO6IpgVT836RkHVwejhSW0h7G1P3Ktj8=; b=Cw2Vg/ZJTgTyD1yEmoXWA1YPU5fleYSpuaaK7+tiFojk3UAsJLE19Fo0eN24A0flgUkqQX hQXc+TtUZ7lbQYetj76u+LjEJtwbQcGdCWyzmQsok3Kv2/DXVeEo/kDOGYM7VbOegPW/WN XIbIvxKN5bxGxYxeT0chcatokUP8qUQc2X05jW47x/xoPflk6kmkdMmEUe0FNBbje+1MAy 98LV6U8evVIJKYlY+GbJqucOkW2ujgxgrlSj9k6iPc4u1GV3hs0ZXhpB92pGPIp2yL6eOH CafX/Td3ab+62LHmTbngab+FBSQlSIH5xO+Wo/KP9ZKdpZbeuNjkZLLDPdpV7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738096654; 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=WOwL3BCqmrduO6IpgVT836RkHVwejhSW0h7G1P3Ktj8=; b=GJ8M0xifZg2WAGOhsG7CAUaMwKcElbr+NEfsTUbvr2j0H+E4rJQs5CMTmWqJcX9Pp9sdr3 mlknC5MddMHrj2w526il4qeGG5CMuzxmejR12HmE5heLXQqVs/vmKGxRs5KrZJU0QOVp3T wrrfJdYDrhh/6VADTJrlKyvTiw1/YeuTb1AF58CIAyP7Hz3mj0yz5Th9c33xewnoXTqNiO d8jwd6hMvKkosgdjisBH+unL+JDZHTu+xQA1jqn1lVWDtNk8exZakl6xmPP5W8nQc35fKb EbjCeb/d10Px1Ee+hT+cqT92iIybDkIoaHZRpnl2Wi8uGnAHhlnRoz5YDLkDTQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738096654; a=rsa-sha256; cv=none; b=ea0u+u1wkg4vghXnFjMJzmAdEQs9UehpjlET/WAr9N/+aKrSrt0blNVtlgqHtCtnFVn1Tv LbYDzoTTu7Z/Fvbykv7RSdFdv+aI3cEM3W48sCUVTz3ZdxQg00hXRern3eOHq782k2cPV0 4hduRBmXvNgUAHyEcqffEXvyh75aKOSopx1OvSjMXtL+pfSJC7q5eD2+lY7fr9m30XbJOy ASKuVlyPv/mnKcpaNIHdEVTiK+fW6eXEpPIlnf0vP7tnYPTdpIvkraileVVBiFVu+bGLCW Jabn9vEyI2sLhEd62bMgmx5fwJ2rq/wXdTVSHqYejqqQT4Ey9yWg/uW8zJXplQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YjHCd3gxKz18Gt; Tue, 28 Jan 2025 20:37:33 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Tue, 28 Jan 2025 12:37:30 -0800 From: Gleb Smirnoff To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: January 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: On Mon, Jan 27, 2025 at 01:01:16AM -0800, Gleb Smirnoff wrote: T> This is an automated email to inform you that the January 2025 stabilization week T> started with FreeBSD/main at main-n275044-c6767dc1f236, which was tagged as T> main-stabweek-2025-Jan. Two regressions were identified: * Compilation failure on 32-bit platforms. Fix 5289625dfecb. * Instant panic with SO_REUSEPORT_LB and nginx. Fix 06bf119f265c. My personal experience with updating desktops & laptops went smooth, and several other people also reported their success. Same stands true for my home router. Testing at Neflix did not discover any stability regressions except mentioned above SO_REUSEPORT_LB. We observe significantly increased CPU load on a few specific hardware samples with INVARIANTS kernel. There is no data yet without INVARIANTS. We will investigate this deeper later, this doesn't warrant prolonging the code freeze. The advisory code freeze on main branch is thawed! Thanks everyone! -- Gleb Smirnoff From nobody Tue Jan 28 22:49:04 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 4YjLBf0QFZz5mHGs for ; Tue, 28 Jan 2025 22:51:54 +0000 (UTC) (envelope-from sjg@juniper.net) Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.pphosted.com", Issuer "Sectigo RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjLBd56rPz3LJQ; Tue, 28 Jan 2025 22:51:53 +0000 (UTC) (envelope-from sjg@juniper.net) Authentication-Results: mx1.freebsd.org; none Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 50SGA3pt026047; Tue, 28 Jan 2025 14:51:52 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h= cc:content-id:content-type:date:from:in-reply-to:message-id :mime-version:references:subject:to; s=PPS1017; bh=vg1Inbit+UEt2 9SJnuAzgPPYR6WRTD60ZqqMzG4hQpo=; b=vBaXwSjznLiMz4SMpSnffKHglY+7m EGEvm2ilUKgAQ/BfJzds0mPkYAWRZA8iwCDSFFPcnvY0fFHj/kA7xxGO+wpqEYnp TMOyD8UctJS7sYtuOr5slhQjwI/sW8G1mUBA+aTuAsIb3SKCL97y78ezzevA8FQ5 /PKP7KUMNj/JoQxr5+C6cBkdvaXeGDyeRdJbs6ke5bX7rx793YK+JrhIF09wSlNe ZW46i0P1OUFQJxnEdEZOBtnjFMqRNFrdFR0TETav7y7gEloK3IBYmb5Xu9S/eIdy Lj8MhdD3Zxwy9/eGAetPP/LV6jQXWxgYjJ9+Wa0/7DsbF5T4eoGUuzJIg== Received: from dm5pr21cu001.outbound.protection.outlook.com (mail-centralusazlp17011028.outbound.protection.outlook.com [40.93.13.28]) by mx0a-00273201.pphosted.com (PPS) with ESMTPS id 44f2h1rtr1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 28 Jan 2025 14:51:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=vzLMFlQK33szDSkhA6h1kfR0C4t/WfQ5NOTcwKvR3tuq6ogVr/15fIjQRNDiCH2OZ51iyrpOW8LGjEh2xuaB2sOZHEUsHFjQ/TeDEVHzIPBr6NCB6w7L9xiFNB282wESWpZOhxfX9DQJCIaPaE/+0xnyd4GVvK2Bmvb5ap72Dnm2oRGleyHRTawPXOLT5IqA7RO66zAuLPEXK0P1WgEvCEJgTozgTbphmJWlU3cgB1szJqna/doZZwDKjfcFVYXCtFaYdgP3FRSsvIhR4sy7pm43KNGnb+HtpGjk/OYbhfNSA+bWIA5eVap91ePyEWKKv+pdInrDj5u93Nmxv1dyeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=vg1Inbit+UEt29SJnuAzgPPYR6WRTD60ZqqMzG4hQpo=; b=E7lhMRsqyyLBSEFjSCZdUnsMrTU+aI35UoNFMbbbboVOEdt2mcFO/j94Z/w8tf/jtH61ho4GcCj5kfycQHIb0HWbc5PMROMFoRxoBBEDCWfWWe8IImJeOio8Mc8eZxoUtoosorkALhVX7/o2eddXkVpYzh6ZFxYmNpRF9F+UfiY8zSkYpAnKkvv+3FzCj8Sz+47V22eb2Ei/uPqdYgPBC71cmZhHA3Aloi2xHovoi9VUg62oMw9Dtk+A0lbxCSvsMSkbRBuFXPVC/KmDUVJEsCQRRYg0RoO3vELdNJsicxS4cD2Y1xMmWxBPwgpvcQbv1M2VvF2jTnaMkGIW/xqJWg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=softfail (sender ip is 66.129.239.14) smtp.rcpttodomain=freebsd.org smtp.mailfrom=juniper.net; dmarc=fail (p=reject sp=reject pct=100) action=oreject header.from=juniper.net; dkim=none (message not signed); arc=none (0) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vg1Inbit+UEt29SJnuAzgPPYR6WRTD60ZqqMzG4hQpo=; b=KncnFrLqaFvmuKEMfzn9DB7fa2pBlkAo1G11I69T6sjWWXjl5g1FnRda+oxSKIwTUKWFZNOcJR96Gvt4QNBACs3Rzrs9uF6nWoZYZoMlGm2p3rTU92am3hmEEnpVlg30uthkU2KVzxEbSnRSiXXrzoZvR8f2zz8hDVz80x0IvhM= Received: from SA1P222CA0111.NAMP222.PROD.OUTLOOK.COM (2603:10b6:806:3c5::8) by MWHPR05MB10815.namprd05.prod.outlook.com (2603:10b6:303:282::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8398.17; Tue, 28 Jan 2025 22:51:49 +0000 Received: from SN1PEPF0002636C.namprd02.prod.outlook.com (2603:10b6:806:3c5:cafe::d1) by SA1P222CA0111.outlook.office365.com (2603:10b6:806:3c5::8) with Microsoft SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.8377.24 via Frontend Transport; Tue, 28 Jan 2025 22:51:48 +0000 X-MS-Exchange-Authentication-Results: spf=softfail (sender IP is 66.129.239.14) smtp.mailfrom=juniper.net; dkim=none (message not signed) header.d=none;dmarc=fail action=oreject header.from=juniper.net; Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.14 as permitted sender) Received: from p-exchfe-eqx-01.jnpr.net (66.129.239.14) by SN1PEPF0002636C.mail.protection.outlook.com (10.167.241.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8398.14 via Frontend Transport; Tue, 28 Jan 2025 22:51:48 +0000 Received: from p-exchbe-eqx-02.jnpr.net (10.104.9.15) by p-exchfe-eqx-01.jnpr.net (10.104.9.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.4; Tue, 28 Jan 2025 16:51:47 -0600 Received: from p-mailhub01.juniper.net (10.104.20.6) by p-exchbe-eqx-02.jnpr.net (10.104.9.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.4 via Frontend Transport; Tue, 28 Jan 2025 16:51:47 -0600 Received: from kaos.jnpr.net (kaos.jnpr.net [172.23.255.201]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id 50SMplj8021193; Tue, 28 Jan 2025 14:51:47 -0800 (envelope-from sjg@juniper.net) Received: by kaos.jnpr.net (Postfix, from userid 1377) id 2E80C5318E; Tue, 28 Jan 2025 14:49:04 -0800 (PST) Received: from kaos.jnpr.net (localhost [127.0.0.1]) by kaos.jnpr.net (Postfix) with ESMTP id 2BD6253093; Tue, 28 Jan 2025 14:49:04 -0800 (PST) To: Nuno Teixeira CC: FreeBSD CURRENT , Subject: Re: WITH_META_MODE: base clang excessive compiles In-Reply-To: References: Comments: In-reply-to: Nuno Teixeira message dated "Tue, 28 Jan 2025 12:54:23 +0000." From: "Simon J. Gerraty" X-Mailer: MH-E 8.6+git; nmh 1.8; Emacs 29.3 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-ID: <72359.1738104544.1@kaos.jnpr.net> Date: Tue, 28 Jan 2025 14:49:04 -0800 Message-ID: <76824.1738104544@kaos.jnpr.net> X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: SN1PEPF0002636C:EE_|MWHPR05MB10815:EE_ X-MS-Office365-Filtering-Correlation-Id: 86c06e3c-5f96-4c4d-63b5-08dd3fee5909 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0;ARA:13230040|1800799024|36860700013|376014|82310400026; X-Microsoft-Antispam-Message-Info: =?us-ascii?Q?Uc3O9uJIoSxTNXsfP86rwCUWqdJM9PkHwVyq8E0pkT2EiyOgvtUxAUmkzXBE?= =?us-ascii?Q?Cb+7d2IVMY7FHZwm5UaclrLqfMjraMOyQyX2snRvcg2XFmiGU09xY3TCXdAa?= =?us-ascii?Q?IBQxYxuS/tXNlArducM/m3aFb5/IqSf0yShJL5MWzNwzJXvuZHHAZOHN/C1P?= =?us-ascii?Q?xt0r+RcmQXAhoE4omQUHWuy6BjW3R7d9B5IrfNT9wNpj+8h3hqd52KZgMW16?= =?us-ascii?Q?P4PAphmmaO/eMbRVG7hxI1JV9Yz4VvCdOUxWRCFwF/Hzd4eCYbcfFIHfJyNX?= =?us-ascii?Q?z3CVKo6vIdClrjiHRSQ+FfzHmIjlpSf8zgmIz6keKJyNgSpwXA5zmtoUHwkO?= =?us-ascii?Q?XQtl0N89GBQBTd50jC0GaPdP5rpFVlITHBMDtsoPs1S1+WS43W6JW9BRnaHf?= =?us-ascii?Q?STYH7hhaxKyJKt9HM5dp1Hc+kxYCZt0/qlPHDPaCQvcAdJJjhil7s+Kc1mZ8?= =?us-ascii?Q?I4kRC6j0/ANnco7lUmsifYsOBLUb91R8KVaFbakyQeyvqfke23gA5mLvcoLh?= =?us-ascii?Q?chA4M6YJTlEycatlNH7qQUu/vLWYECauSwLa3N8BSRCA6xd1VlF4mq2ha9n/?= =?us-ascii?Q?4sDuV/TO/tQMNg2OUmE0EIRR120hgsme7e/yPIUpECquiwiUGNxRgqC3VDWy?= =?us-ascii?Q?46GydPgl59JouBso37GsQJ7C82zqWSTgI5IoOzhY0LvRq9KTZVQs3G7HNoAr?= =?us-ascii?Q?e08KCiOWz7DSIUuN7aHYmfKsfIwRJA4vmRsjyy0WGRlI+TFk9taHknkharVU?= =?us-ascii?Q?Zsx7oNFIfAvu2XUKXA8LxiayjV8+c16DW0B/ALHCfCgo1pYxoxERAhfS5tsV?= =?us-ascii?Q?jLSYmZ6h8hA49JzI+uclkifiYthDs2ukYIoDxLzGQ9oPLSPb81yaN00B4taI?= =?us-ascii?Q?UFEgpcESzmShDf6cFNYiKJZYV9ckfgYrAYsbmMw3lCVI04LfQud669wlvDRT?= =?us-ascii?Q?w85Qyz7MIj76PelpRnKSN0Yp5xkB9yAjYRNP+tkrWnvMkdhuNd9bPtk6Qych?= =?us-ascii?Q?6NQ64f7mr1p4U9jq3oST7kYTw1TCuhnYSN9EcNeQgjuiko08bXFC/dRv9W1k?= =?us-ascii?Q?Dl/0lSAc8RCCzbwkMU5vuYJRCJ0nKSnohJobtkO0MVXjF/veC7XW2DCJV/Il?= =?us-ascii?Q?uuZ8M7Pplz11GT+QPP7fxcdLGXVzAQn0pzmbDaEgXU/6LaZiXl+mdJhevVDh?= =?us-ascii?Q?WrE0IwYhR877Hzf10Q6tCMkoB6vieT0ujrGFQCSCVRY7ShmfvKGeXum/hsUo?= =?us-ascii?Q?l02T+k2TWRoFr8000wNCV2esnJT0bfoOkVgUnTL8OMAL1qlsj5iH5cLztidG?= =?us-ascii?Q?l01x4ZZsEOHJ0OgQXE8GGUylxNg0Nz3V5WfHoTk4CNgfxY4ESfqMgHG8+e97?= =?us-ascii?Q?3Z4I++J3SD8lIW9eDU4csqy0RXCoUKR0DrKI5ugr5QK3qNHbamWygmlbBbLM?= =?us-ascii?Q?UVc1RD2u8VosKzo9zfjlS/EiF2cxOkcS17BAkWpg+1IHs+1DQM5i2A=3D=3D?= X-Forefront-Antispam-Report: CIP:66.129.239.14;CTRY:US;LANG:en;SCL:1;SRV:;IPV:CAL;SFV:NSPM;H:p-exchfe-eqx-01.jnpr.net;PTR:InfoDomainNonexistent;CAT:NONE;SFS:(13230040)(1800799024)(36860700013)(376014)(82310400026);DIR:OUT;SFP:1102; X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 28 Jan 2025 22:51:48.4251 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 86c06e3c-5f96-4c4d-63b5-08dd3fee5909 X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4;Ip=[66.129.239.14];Helo=[p-exchfe-eqx-01.jnpr.net] X-MS-Exchange-CrossTenant-AuthSource: SN1PEPF0002636C.namprd02.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB10815 X-Proofpoint-ORIG-GUID: RO4rgP7feLhEJ-KpNOgqfJqDfetcs0Ui X-Proofpoint-GUID: RO4rgP7feLhEJ-KpNOgqfJqDfetcs0Ui X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1057,Hydra:6.0.680,FMLib:17.12.68.34 definitions=2025-01-28_04,2025-01-27_01,2024-11-22_01 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 impostorscore=0 malwarescore=0 priorityscore=1501 adultscore=0 lowpriorityscore=0 mlxscore=0 phishscore=0 suspectscore=0 spamscore=0 bulkscore=0 clxscore=1011 mlxlogscore=766 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2411120000 definitions=main-2501280167 X-Rspamd-Queue-Id: 4YjLBd56rPz3LJQ X-Spamd-Bar: ---- 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:26211, ipnet:208.84.65.0/24, country:US] Nuno Teixeira wrote: > Just to check that I'm using the correct setting for WITH_META_MODE > since almost everytime I update main tree, I got clang compiled. > > Is that normal? Quite possibly. You can add -dM to your make command line and meta mode will explain why it thinks a target is out of date. If you see a target built without comment from meta mode, then the normal oodate rules said it was out-of-date. > > -- > $ kldstat | grep filemon > 11 1 0xffffffff849f2000 3250 filemon.ko > > /etc/src-env.conf: > WITH_META_MODE=yes > --- > > (maybe usefull to show this as well) > /etc/src.conf: > WITH_MALLOC_PRODUCTION=yes > WITHOUT_LLVM_ASSERTIONS=yes > > /etc/make.conf: > KERNCONF=GENERIC-NODEBUG > DEVELOPER=yes > DEVELOPER_MODE=yes > PORTSDIR=/home/nunotex/Work/freebsd/ports/main > DISTDIR=/Arq/DISTFILES > > Thanks, From nobody Tue Jan 28 23:16:52 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 4YjLlk0bPCz5mKCP for ; Tue, 28 Jan 2025 23:17:06 +0000 (UTC) (envelope-from eduardo@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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjLlj6g02z3PWM for ; Tue, 28 Jan 2025 23:17:05 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738106225; 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:references:references; bh=vpVOAwv9g3ag2PFwoZukTL6ijwgzth5os2O25NR5cxU=; b=uEEKUw7yJQfIDIRlD5AiX8ljP702wmx5nAarSZ0qZjBXwV7Jvce/mJ2WOq61sHDIlEkApx eGJu3rBvRFTkHUA9/l+KDkhgizDLQ8XYidXrG4CeP/mNaf3mLpUVGey+ls++6ZlhsBrKbq 3pRly6FyZbcaC1qkmGgI06/cNX5nx4myA5RiVrf7f3V1GbhKDTXWbMa1fwDfLwtV54rmBP UwlOVvH+bAhCfjLNab+vWGNTSEA8RE/rNbu8USwLxjqaCGXUbDhkD+hyfF4FFgu/2h58zg pJsPvgIrGvas9rN2jDDkSn63VU2qUQ0Bct44+65KKfzsHM2Xy2icAJEcoKZUkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738106225; 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:references:references; bh=vpVOAwv9g3ag2PFwoZukTL6ijwgzth5os2O25NR5cxU=; b=ZE3Hlihzi/wADAQqEut7YUPMgWgkwg/HiaGqZEI8KwHN4kL44obyVEMzM2zh8+1EJWxiUC mAr4jDLI2gSQtGKHtQruZOtWMCbDwTRNAlXe/nk++q5pWWBJbJE6jDVBt4aAXr1RVcCbQ4 qxwz4GJ02dpoz84X0l68NoCiF3jaO8WibAmrRNc/YE4p6PSVHsaXIOg9ZzisJqrGS6ekUV sDmphc8nVLYR9dYkyQSeQzWn7pnkRDN2wxzFScOq6DdgYCErM/4iMvF+rVKLng/GCuckX+ 8JTnwSJDRZINKBJs5lIdQbinjIaCz3aCpaRyHoJ/ZcoPxVHPfk4B7l7dptj+6w== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738106225; a=rsa-sha256; cv=none; b=MHbfqb2mcegsPWLkvqGuFB9jfAQX+HmQb4EbhHn38hSm3VtLKrv14YTtsY5q3vAWlPoEyL N3VpXWKOfxhBmDdrSwLZ8ptpqbcDphp80z/GrLglf/Kk4nSyJ8sZ2wGZB+XnGqmfaU0Kiw wU8p6ABYUM6+/8y66LQz4hV7fTU6SrW7UsAXS6mTzK60tlrM/12N1UtUQvapdrgVeHydRo dw9JPSnHPnRlPojqsLQkZLMn8JeA4VqiMImHDlMKQr0SLi7zPsRzztABzZjj9z6DB6tPUp Gcv9FOlT0NGq6kUeniG/jaihYEkqoSJYnOD4q6RJLSIxzjul9esOwEQBzX2MxA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from mail-qt1-f175.google.com (mail-qt1-f175.google.com [209.85.160.175]) (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)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4YjLlj5gCTz1BZ2 for ; Tue, 28 Jan 2025 23:17:05 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-qt1-f175.google.com with SMTP id d75a77b69052e-4679996ae50so4620831cf.3 for ; Tue, 28 Jan 2025 15:17:05 -0800 (PST) X-Gm-Message-State: AOJu0YxN8jR6ZrTIU7IE26jlSrupbotwLMLwcT9yCvBfZ3mWTXIJn4v+ xfduE+Z44+BrpEVJ7D2WUj1ptv4kezV4t3DRQb821zUPvctPiM3oeyvc5t7XcXkdNDQSFhX2xfS UPDVRCMGu5xPs1hD/81otsDifW3A= X-Google-Smtp-Source: AGHT+IHFnr9i3jCekdz20l3orSYSvOZ9T9naW8FpIMrvmO9dYAJFBHFSIXxo0vmvsCkqAHkrOzRbdhGDRgqd6Ol06R4= X-Received: by 2002:ac8:5841:0:b0:461:6599:b9a with SMTP id d75a77b69052e-46fd0b65a74mr6530931cf.11.1738106225422; Tue, 28 Jan 2025 15:17:05 -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: <76824.1738104544@kaos.jnpr.net> In-Reply-To: <76824.1738104544@kaos.jnpr.net> From: Nuno Teixeira Date: Tue, 28 Jan 2025 23:16:52 +0000 X-Gmail-Original-Message-ID: X-Gm-Features: AWEUYZm12B6PAIW9uZANfQ82TVa277NSTsjWywkEqnGOOkltrvmil7x64qsuTE8 Message-ID: Subject: Re: WITH_META_MODE: base clang excessive compiles To: "Simon J. Gerraty" Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="00000000000025f965062ccc64fe" --00000000000025f965062ccc64fe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello! So nice, I can see now: Skipping meta for ...: ... some_file.meta: 23: file 'other' is newer than the target... This is great! Thank you so much, Simon J. Gerraty escreveu (ter=C3=A7a, 28/01/2025 =C3=A0(= s) 22:51): > Nuno Teixeira wrote: > > Just to check that I'm using the correct setting for WITH_META_MODE > > since almost everytime I update main tree, I got clang compiled. > > > > Is that normal? > > Quite possibly. You can add -dM to your make command line and meta mode > will explain why it thinks a target is out of date. > If you see a target built without comment from meta mode, then the > normal oodate rules said it was out-of-date. > > > > > -- > > $ kldstat | grep filemon > > 11 1 0xffffffff849f2000 3250 filemon.ko > > > > /etc/src-env.conf: > > WITH_META_MODE=3Dyes > > --- > > > > (maybe usefull to show this as well) > > /etc/src.conf: > > WITH_MALLOC_PRODUCTION=3Dyes > > WITHOUT_LLVM_ASSERTIONS=3Dyes > > > > /etc/make.conf: > > KERNCONF=3DGENERIC-NODEBUG > > DEVELOPER=3Dyes > > DEVELOPER_MODE=3Dyes > > PORTSDIR=3D/home/nunotex/Work/freebsd/ports/main > > DISTDIR=3D/Arq/DISTFILES > > > > Thanks, > --=20 Nuno Teixeira FreeBSD UNIX: Web: https://FreeBSD.org --00000000000025f965062ccc64fe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello!

So nice, I can see no= w:

Skipping meta for ...: ...
some_file.meta: 2= 3: file 'other' is newer than the target...

This is great!

Thank you so much,

Simon J. Gerraty <sj= g@juniper.net> escreveu (ter=C3=A7a, 28/01/2025 =C3=A0(s) 22:51):
Nuno Teixeira <= eduardo@FreeBSD.org> wrote:
> Just to check that I'm using the correct setting for WITH_META_MOD= E
> since almost everytime I update main tree, I got clang compiled.
>
> Is that normal?

Quite possibly.=C2=A0 You can add -dM to your make command line and meta mo= de
will explain why it thinks a target is out of date.
If you see a target built without comment from meta mode, then the
normal oodate rules said it was out-of-date.

>
> --
> $ kldstat | grep filemon
> 11=C2=A0 =C2=A0 1 0xffffffff849f2000=C2=A0 =C2=A0 =C2=A03250 filemon.k= o
>
> /etc/src-env.conf:
> WITH_META_MODE=3Dyes
> ---
>
> (maybe usefull to show this as well)
> /etc/src.conf:
> WITH_MALLOC_PRODUCTION=3Dyes
> WITHOUT_LLVM_ASSERTIONS=3Dyes
>
> /etc/make.conf:
> KERNCONF=3DGENERIC-NODEBUG
> DEVELOPER=3Dyes
> DEVELOPER_MODE=3Dyes
> PORTSDIR=3D/home/nunotex/Work/freebsd/ports/main
> DISTDIR=3D/Arq/DISTFILES
>
> Thanks,


--
Nuno Teixeira
=
FreeBSD UNIX:=C2=A0 <eduardo@FreeBSD.org>=C2=A0 =C2=A0Web:=C2=A0 https://Fr= eeBSD.org
--00000000000025f965062ccc64fe-- From nobody Wed Jan 29 03:33:17 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 4YjSRZ3tXRz5lxKL for ; Wed, 29 Jan 2025 03:33:30 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx-01.divo.sbone.de (mx-01.divo.sbone.de [IPv6:2003:a:140a:2200:6:594:fffe:19]) (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 "mx-01.divo.sbone.de", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjSRY0GVyz437P; Wed, 29 Jan 2025 03:33:28 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zabbadoz.net header.s=20240622 header.b=cMxxRlFB; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2003:a:140a:2200:6:594:fffe:19 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net; dmarc=pass (policy=none) header.from=zabbadoz.net Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id 88010A64805; Wed, 29 Jan 2025 03:33:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=zabbadoz.net; s=20240622; t=1738121598; bh=rtIfS1aHtLAEKfmR2PPgFs0a39h11gZVAYsyV24MXnY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=cMxxRlFBX8j/Aykkst9AgZSTyJnqtnt/WPrQUNMsxd1ZPjREbaWHyQAyvumFZeL0R LHI6N4hQjQXcg+5suzGBilXXFx+GmiOQHkX6a250/q1PrRlHY/T1z+zZR2ztHIITnI /WIDOGE+A6m3Xy4Yp1hhkawgKf4bTvqrkbXUzzzdFEc4oPzMhWoh2hIgechVgT8ufY BwocJhzJHas76qBzxtljV3ncJfXCy4zMy2iuHjMlL6Pa8JAwRW7bvKM87dOo0TqGWd uN7LTMmtZOpbatsWCE0wIre3RE1ehZ6OFMmjMzF9yUMt43RLUyhO7Ca+SXsT0irWGt C3gw/8ZWjFhfOYar5CD0N9FynxvM9zs4LH025xROFi0b+GeGDrPoqzJKIKUfnif01C WNGi0vVFmCpT2+ICRQJYu7GVeTF44HRrlDHaw81RNGkLBKTqdQefqSPIj+FkH+bgKe P/h2hK2Xayq/97lD8xNOUMVENtYvMw70P5f2sMWSwtNRwo9tmIGqdPTfM7+Uimkn1h gifmnhtR1m9SKUkXOuj7+lnNdyoSyW2MjA6hWXUaG/L8PzDYgj2PKSzpu+ewY1XXYt ih2W0dYhfc+0zNB4mzzX5DMgVZA6Piwwb/GWxWMwtHqvyo33lOgFD/oH0guRrpVD68 vC9Sy1XkKylFa79sNQinXse0= Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 978422D029D8; Wed, 29 Jan 2025 03:33:18 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id XCROmEQjJvYL; Wed, 29 Jan 2025 03:33:17 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 852222D029DF; Wed, 29 Jan 2025 03:33:17 +0000 (UTC) Date: Wed, 29 Jan 2025 03:33:17 +0000 (UTC) From: "Bjoern A. Zeeb" To: Mark Millard cc: Emmanuel Vadot , FreeBSD Current Subject: Re: "don't know how to make /usr/main-src/sys/contrib/dev/iwm/iwm-3160-17.fw.uu. Stop" In-Reply-To: Message-ID: <597porsp-1p95-36on-04r1-95r8s6sq2nsn@yvfgf.mnoonqbm.arg> References: <978176f7-270c-4603-b80a-e29c3b1b4b73@FreeBSD.org> <4FC807EC-10DD-49FD-AACE-9026B4925923@yahoo.com> <1B14894C-78E3-4696-9E4F-FBA97A356BF1@yahoo.com> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 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; format=flowed X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[zabbadoz.net,none]; R_DKIM_ALLOW(-0.20)[zabbadoz.net:s=20240622]; R_SPF_ALLOW(-0.20)[+ip6:2003:a:140a:2200:6:594:fffe:19]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3320, ipnet:2003::/19, country:DE]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zabbadoz.net:+] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4YjSRY0GVyz437P On Mon, 27 Jan 2025, Mark Millard wrote: > On Jan 26, 2025, at 20:51, Adrian Chadd wrote: > > >> Hi! > > Hello. > >> So, there's no longer a build target for the firmware uuencoded files -> kernel module. > > Yea. But there are the sys/conf/files dependency lines in > main that still list .fw.uu files. That includes a reference > related to the error I get in my context unless I avoid > "device iwmfw" in the kernel configuration: > > /. . ./sys/conf/files: dependency "$S/contrib/dev/iwm/iwm-3160-17.fw.uu" \ > > It makes things look like the .fw.uu removal activity is still > incomplete. Yes it is, This commit missed them. Manu, will you remove them? commit af0a81b6470aba4af4a24ae9804053722846ded4 Author: Emmanuel Vadot AuthorDate: Thu Dec 12 17:13:58 2024 +0100 Commit: Emmanuel Vadot CommitDate: Mon Dec 16 10:44:47 2024 +0100 iwm: Stop shipping firmware as kernel module Since we can load raw firmware start shipping them as is. This also remove the uuencode format that don't add any value and garbage collect old firmwares version. For pkgbase users they are now in the FreeBSD-firmware-iwm package. >> Being able to build iwm in the kernel rather than a module is broken. >> >> Now, the real issue(s) are that iwm needs firmware to initialise, and the firmware needs to exist, and thus it needs access to the rootfs for firmware_get() to find the now binary files in /boot/firmware instead of the kernel module old way, and that whole pipeline is broken if it's loaded at boot time or included in the kernel directly. There isn't a nice way to defer the firmware load attempt until /after/ rootfs is up. The answer is not to load it from loader anymore really but let devd do it's job. That is monolithic kernels + firmware are still the problem but I am not generally thinking this is the problem here. But yes, there would also be ways for firmware laod to be defered but that's also a different story. > Yep. Firmware can still be loaded from loader. The following commit should have made that more easily possible without changes. commit a0f06dfb0d188966bee7265ec7d9f20093186bb6 Author: Emmanuel Vadot AuthorDate: Mon Jan 6 08:34:02 2025 +0100 Commit: Emmanuel Vadot CommitDate: Mon Jan 6 08:34:02 2025 +0100 loader: Add a list of firmware name mapping Since we started to ship raw firmware for iwm(4), users who loads the driver from loader are having problems as loader don't know that the firmwares are now raw files and not kernel modules anymore. Start a list of default entry for iwm(4) firmwares name mapping so it will still works when loaded from loader. Differential Revision: https://reviews.freebsd.org/D48211 Reviewed by: bz, imp, kevans /bz -- Bjoern A. Zeeb r15:7 From nobody Wed Jan 29 05:13:57 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 4YjVgX2xxcz5m5Ys for ; Wed, 29 Jan 2025 05:14:00 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjVgX2CfVz3JM6; Wed, 29 Jan 2025 05:14:00 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738127640; 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:references:references; bh=+g6scScMN2J3fJVNbLEHTJHSzvkykWAHaudlIQNN3Vc=; b=TTZwVJayLh6wKJRxBMKorRCwr2wOQMSsaeQDZolBA7YaD5xRlGAW78rprc0Qr981S2Akdp kX7fc5pDodkagj4HzGgbvly/Bel2nczYzAAqDtCSOTE4FhR5mx2TJPl2u5eg4tsHO/Ax+t DojaQU7F1lFyC762BGGV/dMyo7MdNI5+m7LYjV8BY3wCuccFLv8ENb7rGZCjG802+o+iKr Jwkli0OBYFXA8oT7yuQ/8aXFVMuVgZzBaOcAVhZLBICbYL+5mYh4x692FGXNc7u51/lpUC YBtC0SUOWTqIehOSoaB7xv+qUMyjjYF0mXkPyDKSUj/QdFoVkWacQmkT5DzHNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738127640; 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:references:references; bh=+g6scScMN2J3fJVNbLEHTJHSzvkykWAHaudlIQNN3Vc=; b=Hfw2xrcYt7xcYrMPgSoftutUdFLWL8dW7CzLZOyyfX2xmJRc1eko+FGiBRyTsM2veVujO9 KMjw4QmWA3jfvHeCxNCXEmzLFo+akSfx73MmBRycNcHM1Twqt8XmrP/uASbXH+xJB2qtbn 4yEGaksoxaBPO8RjbNdlc6q/KgYZjFO/8sGqt3o5v2hxliqAyT8Kr2lXbktVEyvFbsZRsR zyA+E0KWzyaba0J9lxDd02vViWetDHnztm2QZ9OnhAEAXMiJApuEmO7mnO83LEldsarZfV TXNbHbOoa3FPWcBxjT4T/4CduAVinw37YXCJtdRkV2w7ANsKSI1bYUtoBbFIXw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738127640; a=rsa-sha256; cv=none; b=S79un1KgPVBiaf8snSxFHxrk8lJJok6QIpmOgC+i/aQUFbBKiRM/Ejz6Ij5wjIZh3WuW3s mzITUXrnyuNeZiyo7UsjIwM42pf0nvKJ78iU8MWkam1WACW0l06u5sBglIPRBwhev0Tyyb RfEUiYyjSd9wPmI/YUSshNO56Zmt1My8k4FqporVNxSn3rXM5xVE68x0/HsuOlXMuiUO5w ZDRXxQHYfa2uP3Ay/mU8T9TaAr/UYz3g90LxaC3b6/ZNNQ3OhDK6jstXqfaIwxV3aOoSCy 5yUExGpvxaq4AeQojQZ04mZ9U+iCb2k30pcc3I8C6iIDtAK94MSXhpZ6mroYyw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YjVgW5PNqz5jW; Wed, 29 Jan 2025 05:13:59 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Tue, 28 Jan 2025 21:13:57 -0800 From: Gleb Smirnoff To: Rick Macklem Cc: current@freebsd.org, rmacklem@freebsd.org Subject: Re: HEADS UP: NFS changes coming into CURRENT early February 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/mixed; boundary="8/4KebHVP00ayBWE" Content-Disposition: inline In-Reply-To: --8/4KebHVP00ayBWE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jan 27, 2025 at 06:10:42PM -0800, Rick Macklem wrote: R> I think I've found a memory leak, but it shouldn't be a show stopper. R> R> What I did on the NFS client side is: R> # vmstat -m | fgrep -i rpc R> # mount -t nfs -o nfsv4,tls nfsv4-server:/ /mnt R> # ls --lR /mnt R> --> Then I network partitioned it from the server a few times, until R> the TCP connection closed. R> (My client is in bhyve and the server on the system the bhyve R> instance is running in. I just "ifconfig bridge0 down", waited for R> the TCP connection to close "netstat --a" then "ifconfig bridge0 up". R> Once done, I R> # umount /mnt R> # vmstat -m | fgrep -i rpc R> and say a somewhat larger allocation count R> R> The allocation count only goes up if I do the network partitioning R> and only on the NFS client side. R> R> Since the leak is slow and only happens when the TCP connection R> breaks, I do not think it is a show stopper and one of us can track it down R> someday. I reproduced the recipe and find two problems, but don't have a final solution for either. First, when we create backchannel in sys/fs/nfs/nfs_commonkrpc.c newnfs_connect(): if (nfs_numnfscbd > 0) { nfs_numnfscbd++; NFSD_UNLOCK(); xprt = svc_vc_create_backchannel( nfscbd_pool); CLNT_CONTROL(client, CLSET_BACKCHANNEL, xprt); NFSD_LOCK(); nfs_numnfscbd--; if (nfs_numnfscbd == 0) wakeup(&nfs_numnfscbd); } The svc_vc_create_backchannel() creates xprt with refcount=1. Then we link it to our client, CLNT_CONTROL() makes refcount=2. Then this functions forgets the pointer (but it owns refcount). Whenever the client is destroyed, it will do SVC_RELEASE() on the backchannel, refcount goes 2 to 1 and it is leaked. I made a patch against that and it does reduce amount of M_RPC leaked after your recipe, but once I got panic where the backchannel xprt is actually used after free. So looks like there is a case that my patch doesn't cover. What drives me crazy, can't reproduce it for the second time and can't get any clue from the single core. Patch attached. Second, with the patch the M_RPC leak count for me is 2. And I found that these two items are basically is a clnt_vc that belongs to a closed connection: fffff80029614a80 tcp4 0 0 10.6.6.9.772 10.6.6.9.2049 CLOSED There is no connection peer connection, as the server received a timeout trying to send. But rpc.tlsclntd doesn't try to send anything on the socket, it just keeps it select(2) fd set and doesn't garbage collect. So it is a bigger resource leak than just two pieces of M_RPC. I don't think this is related to my changes. -- Gleb Smirnoff --8/4KebHVP00ayBWE Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="backchannel-leak.diff" commit 1ca54035f1ab46884675fdbba7364624e1217c9e Author: Gleb Smirnoff Date: Tue Jan 28 20:13:19 2025 -0800 try diff --git a/sys/fs/nfs/nfs_commonkrpc.c b/sys/fs/nfs/nfs_commonkrpc.c index e5c658ce76d2..9f3583a09037 100644 --- a/sys/fs/nfs/nfs_commonkrpc.c +++ b/sys/fs/nfs/nfs_commonkrpc.c @@ -262,7 +262,6 @@ newnfs_connect(struct nfsmount *nmp, struct nfssockreq *nrp, struct socket *so; int one = 1, retries, error = 0; struct thread *td = curthread; - SVCXPRT *xprt; struct timeval timo; uint64_t tval; @@ -430,12 +429,15 @@ newnfs_connect(struct nfsmount *nmp, struct nfssockreq *nrp, */ NFSD_LOCK(); if (nfs_numnfscbd > 0) { + SVCXPRT *xprt; + nfs_numnfscbd++; NFSD_UNLOCK(); xprt = svc_vc_create_backchannel( nfscbd_pool); CLNT_CONTROL(client, CLSET_BACKCHANNEL, xprt); + SVC_RELEASE(xprt); NFSD_LOCK(); nfs_numnfscbd--; if (nfs_numnfscbd == 0) --8/4KebHVP00ayBWE-- From nobody Wed Jan 29 06:36:07 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 4YjXVL3p7pz5mCKN for ; Wed, 29 Jan 2025 06:36:10 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjXVL3JPQz3Txd; Wed, 29 Jan 2025 06:36:10 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738132570; 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:references:references; bh=7cIkCJEMAULHgcetrr8xTpCQ4r9Or0OM8UpO3OabObc=; b=F15kpTQl3tfj8KFui+ZXX+WDyFpNCvxP4FEy26m23sb0EfgUQ/6hxqgPN1fMS4Szb6NLh9 mxOlpAlqv+zQCwyoPFkN2hUIFe4G2hFyLt55kdjK4+NzOa1vcIwZ/ulfNKLlf6U3Onh35i nXu+jEFhE8WUOjsRSezai7jSnB1TH3v7qOZZX/Kt8cdk+V4jLMSWCcBI6gvDrzBaCW3tQu 1FGt2qG/u6RSzFeNxbq34RY1p3AgRj0BbSsDljiiS5lmAL6v+RIbvkf3z8z0fh4cqpfeZa ulQMvhiDKhrmiXWbJ7sRC/ML8/h+BpQ5KQLfqCQv4uJofe2Udp8rSkTy6VaB1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738132570; 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:references:references; bh=7cIkCJEMAULHgcetrr8xTpCQ4r9Or0OM8UpO3OabObc=; b=JAXNlsP5qMQioysdvEUiA7i2EF1pReur9M7TIlwFWr11FM/9sQaTj2SXlfUlfKN5GI8Am/ rVlYkrxikZFfxokIVI4r8nQNYmhA/ju33ZBlE5w4BYEfyGyyxr+s+rkujufIrYx3qo0NSD NehEQTi70Y8OI1yGPaEyT7lNaWY4IULpqZ9V+bojYEFjl8k+LqH/pQRRRA5R7Zyov8qs7b A9jffgLPc1zVKP1+syhDcLoK2Plo8oUstL5Cp+OOUuX7FEvAnc/Ue8H6yq/oCHZxl7/SWP 9NU7mXMuqaWBBluEtS9FfFmvh8raMYn+wOmmMxdIYywzuwdgXWF0IN4d9RFd1w== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738132570; a=rsa-sha256; cv=none; b=aG6o64LwulOtIhIMaLdTfWHKk3FvdvBRhk//TYYoZ0wETvVVxcxXTQkJPzp7rwTE/m/1Sp Ij1H3/2hcWeMA7KRD4w7J1qWkgnaqqugFf9ENjTf1RFMunwuq1F7LT78hYnNZZNkJcABQu 37K+SwoIjqfmcxkhpiO/UTUR9HPtJZv/PZd4U7qWb0u9KPYSh+xW20hN56w5MNSuUAGVmT BcuwIZo0wpWLj9RQV+0AAwjw3hDgwJNgtVacQXgEMv4HjN84sMgKc2lIcvdLk3Wlm9+Fpm rPbnd/M1kdZV1ME796uD+iw8NeZPsN6X1h45Eji8EoqJGbayIlx4+CiM/bW0cA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YjXVK6T2lz7gW; Wed, 29 Jan 2025 06:36:09 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Tue, 28 Jan 2025 22:36:07 -0800 From: Gleb Smirnoff To: Rick Macklem Cc: current@freebsd.org, rmacklem@freebsd.org Subject: Re: HEADS UP: NFS changes coming into CURRENT early February 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: On Tue, Jan 28, 2025 at 09:14:00PM -0800, Gleb Smirnoff wrote: T> Second, with the patch the M_RPC leak count for me is 2. And I found that these T> two items are basically is a clnt_vc that belongs to a closed connection: T> T> fffff80029614a80 tcp4 0 0 10.6.6.9.772 10.6.6.9.2049 CLOSED T> T> There is no connection peer connection, as the server received a timeout trying T> to send. But rpc.tlsclntd doesn't try to send anything on the socket, it just T> keeps it select(2) fd set and doesn't garbage collect. T> T> So it is a bigger resource leak than just two pieces of M_RPC. I don't think T> this is related to my changes. Here is what is going on here: - TCP connection is teared down and tcp_close() calls soisdisconnected() - soisdisconnected() calls clnt_vc_soupcall() to notify of error condition - clnt_vc_soupcall() tries soreceive() and gets so->so_error. - clnt_vc_soupcall() sets the client to error state. It doesn't wakeup anything cause there were no running RPC requests. It can't report back to clnt_rc that connection is dead. It doesn't mark itself for the clnt_vc_dotlsupcall() processing. So we end up with: (kgdb) p $tp->t_state $25 = 0 /* TCPS_CLOSED */ (kgdb) p/x $tp->t_inpcb.inp_flags & 0x04000000 /* INP_DROPPED */ $27 = 0x4000000 (kgdb) p/x $tp->t_inpcb.inp_socket->so_state $28 = 0x2000 /* SS_ISDISCONNECTED */ (kgdb) p/x $tp->t_inpcb.inp_socket->so_count $35 = 0x2 (kgdb) p/x $ct->ct_rcvstate $29 = 0x41 /* RPCRCVSTATE_UPCALLTHREAD | RPCRCVSTATE_NORMAL */ (kgdb) p $ct->ct_error $30 = {re_status = RPC_CANTRECV, ru = {RE_errno = 13, RE_why = RPCSEC_GSS_CREDPROBLEM, RE_vers = {low = 13, high = 0}, RE_lb = {s1 = 13, s2 = 0}}} (kgdb) p $ct->ct_pending $31 = {tqh_first = 0x0, tqh_last = 0xfffff80002838ea8} Note: In my case so->so_error was EACCESS, cause I used ipfw(4) rule to tear down connection, for normal TCP timeout should be ETIMEDOUT or ECONNRESET if remote has reset. That's why $ct->ct_error.ru.RE_errno == 13. So we need some mechanism for clnt_vc_soupcall() to report to upper clnt_rc that we are dead and ready to be garbage collected via CLNT_CLOSE() and then CLNT_RELEASE(). Once clnt_vc_destroy() is called the daemon will be notified that the TLS socket can be closed by the daemon, bringing so_count to 1 and then final sorele() will bring it to 0 and free. -- Gleb Smirnoff From nobody Wed Jan 29 06:42:19 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 4YjXdl2Rfqz5mCnQ for ; Wed, 29 Jan 2025 06:42:35 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjXdk33j6z3WY7; Wed, 29 Jan 2025 06:42:34 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none Received: from skull.home.blih.net (arennes-299-1-68-49.w92-159.abo.wanadoo.fr [92.159.163.49]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 8e28b1c9 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 29 Jan 2025 06:42:27 +0000 (UTC) Date: Wed, 29 Jan 2025 07:42:19 +0100 From: Emmanuel Vadot To: "Bjoern A. Zeeb" Cc: Mark Millard , FreeBSD Current , rea@freebsd.org Subject: Re: "don't know how to make /usr/main-src/sys/contrib/dev/iwm/iwm-3160-17.fw.uu. Stop" Message-Id: <20250129074219.c8c48eb025acc65e3dbbce72@bidouilliste.com> In-Reply-To: <597porsp-1p95-36on-04r1-95r8s6sq2nsn@yvfgf.mnoonqbm.arg> References: <978176f7-270c-4603-b80a-e29c3b1b4b73@FreeBSD.org> <4FC807EC-10DD-49FD-AACE-9026B4925923@yahoo.com> <1B14894C-78E3-4696-9E4F-FBA97A356BF1@yahoo.com> <597porsp-1p95-36on-04r1-95r8s6sq2nsn@yvfgf.mnoonqbm.arg> X-Mailer: Sylpheed 3.7.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-Rspamd-Queue-Id: 4YjXdk33j6z3WY7 X-Spamd-Bar: ---- 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:12876, ipnet:212.83.128.0/19, country:FR] Hello, On Wed, 29 Jan 2025 03:33:17 +0000 (UTC) "Bjoern A. Zeeb" wrote: > On Mon, 27 Jan 2025, Mark Millard wrote: > > > On Jan 26, 2025, at 20:51, Adrian Chadd wrote: > > > > > >> Hi! > > > > Hello. > > > >> So, there's no longer a build target for the firmware uuencoded files -> kernel module. > > > > Yea. But there are the sys/conf/files dependency lines in > > main that still list .fw.uu files. That includes a reference > > related to the error I get in my context unless I avoid > > "device iwmfw" in the kernel configuration: > > > > /. . ./sys/conf/files: dependency "$S/contrib/dev/iwm/iwm-3160-17.fw.uu" \ > > > > It makes things look like the .fw.uu removal activity is still > > incomplete. > > Yes it is, This commit missed them. Manu, will you remove them? There is actually two problems with my commits, the first one is that you cannot compile a kernel with iwm firmware in it, rea@ sent me some patches a few weeks ago that solves that so this will be fixed soon-ish. The second is people loading from loader who updates their box from 13/14 to current, as make installkernel doesn't install the firmware anymore it will fail, removing iwm_load from loader.conf for the upgrade phase is the way to go I think as I don't see any other way. > commit af0a81b6470aba4af4a24ae9804053722846ded4 > Author: Emmanuel Vadot > AuthorDate: Thu Dec 12 17:13:58 2024 +0100 > Commit: Emmanuel Vadot > CommitDate: Mon Dec 16 10:44:47 2024 +0100 > > iwm: Stop shipping firmware as kernel module > > Since we can load raw firmware start shipping them as is. > This also remove the uuencode format that don't add any value and garbage > collect old firmwares version. > For pkgbase users they are now in the FreeBSD-firmware-iwm package. > > > > >> Being able to build iwm in the kernel rather than a module is broken. > >> > >> Now, the real issue(s) are that iwm needs firmware to initialise, and the firmware needs to exist, and thus it needs access to the rootfs for firmware_get() to find the now binary files in /boot/firmware instead of the kernel module old way, and that whole pipeline is broken if it's loaded at boot time or included in the kernel directly. There isn't a nice way to defer the firmware load attempt until /after/ rootfs is up. > > The answer is not to load it from loader anymore really but let devd do > it's job. Yes agreed and I've done that for quite some time but it seems that we advertize for a long time that loading wifi module from loader wasthe way to go so a lot of people were bitten by this. > That is monolithic kernels + firmware are still the problem but I am not > generally thinking this is the problem here. > > But yes, there would also be ways for firmware laod to be defered but > that's also a different story. Agreed. > > Yep. > > Firmware can still be loaded from loader. The following commit should have > made that more easily possible without changes. > > commit a0f06dfb0d188966bee7265ec7d9f20093186bb6 > Author: Emmanuel Vadot > AuthorDate: Mon Jan 6 08:34:02 2025 +0100 > Commit: Emmanuel Vadot > CommitDate: Mon Jan 6 08:34:02 2025 +0100 > > loader: Add a list of firmware name mapping > > Since we started to ship raw firmware for iwm(4), users who loads > the driver from loader are having problems as loader don't know that > the firmwares are now raw files and not kernel modules anymore. > Start a list of default entry for iwm(4) firmwares name mapping so it will > still works when loaded from loader. > > Differential Revision: https://reviews.freebsd.org/D48211 > Reviewed by: bz, imp, kevans > > > /bz > > -- > Bjoern A. Zeeb r15:7 -- Emmanuel Vadot From nobody Wed Jan 29 08:23: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 4YjZvk66HJz5mLbp for ; Wed, 29 Jan 2025 08:24:50 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjZvk35x0z3kQR; Wed, 29 Jan 2025 08:24:50 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none 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=1738139080; 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:references:references; bh=kX14w+E+kXX4qv4gDDSLcpCj9lvQPgC/usYx54gGtCM=; b=xUPS7P7qv8W+SVP4KjoMjVsMer1v0YOJWOw0Vq8Zjvo+1iu4Q+i+D82Ug0uH7UQV6lkgEU I4Tc68VDQy1DcKrxyOoRfw5/WJEavQcICMly0nOAg+P61OHPkUscCo1jIJ9t3gU3NS8Jpq tSRK5HFZuAWwtXuRIQSQpnXMtMFn9OaBvG/4mI4dmyIXZeiBSYnO3L8LExY99p3HPpm262 qSxbfSByF7qs2zCBP7ZdiF0DXRKi2dJC/yHaS7fXODo6KwZgQOjz0vac73yNVVN10TnFqd WkJ8t7Nh/wspKHMqKadU8NFaol2e58kHRUyA2QhwPzH6CCHgnjGCQTO7lzv9Mw== Date: Wed, 29 Jan 2025 09:23:48 +0100 From: Alexander Leidinger To: Maxim Sobolev Cc: Gleb Smirnoff , Allan Jude , Current FreeBSD Subject: Re: Difference in "netstat -rn" output in the last 2 months In-Reply-To: References: <382bafe6ff9c04ab72d9e0c6f7fb39c3@Leidinger.net> Message-ID: <349e06fd64823b00aa4db36bb82a8de2@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_07829f6199b9ba45db211f1a65dbc26b"; micalg=pgp-sha256 X-Rspamd-Queue-Id: 4YjZvk35x0z3kQR X-Spamd-Bar: ---- 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:34240, ipnet:89.238.64.0/18, country:DE] This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_07829f6199b9ba45db211f1a65dbc26b Content-Type: multipart/alternative; boundary="=_5ac39ebfa48504bfb44c88e37431a324" --=_5ac39ebfa48504bfb44c88e37431a324 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed Am 2025-01-28 21:09, schrieb Maxim Sobolev: > Discussed between 3 people, creating the problem for 3,000. > Great! Sorry, but sarcasm doesn't help here. In the light of a lot of hot talk (and more) all around the globe, feel free to go the open source way and provide a patch. We all want to improve FreeBSD, sometimes it works on first try, sometimes we need to try more often. Bye, Alexander. > -Max > > On Tue, Jan 28, 2025, 7:05 PM Alexander Leidinger > wrote: > > Am 2025-01-28 18:32, schrieb Maxim Sobolev: > > I also think this should be reverted back to default. "-n" refers to IP > to name functionality, "default" is clearly a special case. If someone > wants it, some other option can be added to emit 0.0.0.0/0 [1] (not > sure why but ok). > > This was discussed in the review referenced in the commit. The -nn > proposal was there too. Personally I agree with the rationales in favor > of "-nn". > > Bye, > Alexander. > > -Max > > On Tue, Jan 28, 2025, 5:46 PM Gleb Smirnoff > wrote: On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger > wrote: > A> something has changed in the output of "netstat -rn" between > A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not > listed as > A> "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks some > tools > A> (e.g. iocage). Iocage uses python, I'm not sure if it uses netstat > or some > A> other interface, so it may not be directly related to netstat itself > but > A> could be related to some other stuff (netlink maybe?). > A> > A> Does this ring a bell for someone? > > This is very likely changed by > 9206c79961986c2114a9a2cfccf009ac010ad259. > > Allan, may be make exclusion for the "default" to keep POLA? Otherwise, > indeed at time of 15.0-RELEASE we will receive some negative feedback > :) > > Maybe double -nn should introduce new behavior? > > -- > Gleb Smirnoff -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF Links: ------ [1] http://0.0.0.0/0 --=_5ac39ebfa48504bfb44c88e37431a324 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

Am 2025-01-28 21:09, schrieb Maxim Sobolev:

<sarcasm>Discussed between 3 people, creating the p= roblem for 3,000. Great!</sarcasm>
 
Sorry, but sarcasm doesn't help here. In the light of a l= ot of hot talk (and more) all around the globe, feel free to go the open so= urce way and provide a patch. We all want to improve FreeBSD, sometimes it = works on first try, sometimes we need to try more often.
 
Bye,
Alexander.
 
-Max

On Tue, Jan 28, 2025, 7:05=E2=80=AF= PM Alexander Leidinger <Alexander@leidinger.net> wrote:

Am 2025-01-28 18:32, schrieb = Maxim Sobolev:

I also think this should be reverted back to default. "-n= " refers to IP to name functionality, "default" is clearly a special case. = If someone wants it, some other option can be added to emit 0.0.0.0/0 (= not sure why but ok).
 
This was discussed in the review referenced in the commit= =2E The -nn proposal was there too. Personally I agree with the rationales = in favor of "-nn".
 
Bye,
Alexander.
 
-Max

On Tue, Jan 28, 2025, 5:46=E2=80=AFPM Gleb Smirnoff <glebius@freebsd.org= > wrote:
On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinge= r wrote:
A> something has changed in the output of "netstat -rn" be= tween
A> 2024-11-23-195545 and 2025-01-22-151306. The default route= is not listed as
A> "default" anymore, but with "0.0.0.0" resp. ":= :/0". This breaks some tools
A> (e.g. iocage). Iocage uses python, = I'm not sure if it uses netstat or some
A> other interface, so it m= ay not be directly related to netstat itself but
A> could be relate= d to some other stuff (netlink maybe?).
A>
A> Does this ri= ng a bell for someone?

This is very likely changed by 9206c79961= 986c2114a9a2cfccf009ac010ad259.

Allan, may be make exclusion for= the "default" to keep POLA? Otherwise,
indeed at time of 15.0-RELEASE= we will receive some negative feedback :)

Maybe double -nn shou= ld introduce new behavior?

--
Gleb Smirnoff


--


--=_5ac39ebfa48504bfb44c88e37431a324-- --=_07829f6199b9ba45db211f1a65dbc26b Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmeZ5aUACgkQEg2wmwP4 2IZXuA//R5PjRZ9KJB+jG87GC19YRNLgF9JA4oQG1IBbr/sKZpu46fpFXT3XPq7a 5+Z0VRvaETTiho2cpBWuZjsOQ8u3ggfuvp11DU4uiq9Weix9VbA8fY5IX8CCbOnp 3RV8EvHZ9kEtGUztilujYlGlsmOtl2UjbFhUkWEC0a9fhWmYR5M+GBMxdK++R4Pl hqtmGC9htqmAp75Zoy3YjByV/piVUsVvN+gRbTbwCNlmaWCon0ADTcw1nZ3Rax66 6nuRW7QF0qk/O+tGpDTnCnQ1hKyQO5BURB597PbINOAf0BkxUcYzeNVfifxayj5j LH06wPt2FDUTzPulNIxDZ/Wdl29AOedEkOaE9Rr1Xmn+DmCzTf/3Ps9KNcPsRtFv 8wBVvfy9wSobfXEHiksPYElMo3E1CJT8aKUnDd92qHSFwBaNGiafjvsQZqQgELYI GSV9B0FraPcc7k5hiI4xSML8bs+yzxCAz1HJSV4hWcmIRYsx4TeigQN8qvylEsOe TIyH8pl8OCmLy0lko+n87PvOG7b2XCM9cCkq/I1TJdCb9B3SJnvRgb9/8i8zkoKd u7OFDoKbAAk8pj+Q637DGXSQvB6JH9A60XNglAn2usNKvzFjJta3wrOax02stiTj z/tpzntB8MeqVd5irbqqh4wb4VSXnf1tcdSYKVLR3H5T6gkgWW0= =8Vwh -----END PGP SIGNATURE----- --=_07829f6199b9ba45db211f1a65dbc26b-- From nobody Wed Jan 29 10:27: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 4Yjdcr3Wn7z5mWNw for ; Wed, 29 Jan 2025 10:27:08 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yjdcq3yhMz40R3 for ; Wed, 29 Jan 2025 10:27:07 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=kCpuej15; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.60 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 50AD8240DE1 for ; Wed, 29 Jan 2025 11:27:05 +0100 (CET) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 47D44240031 for ; Wed, 29 Jan 2025 11:27:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1738146423; 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; bh=/tzUJ9kRRoTxi2XFl3+zUI/WxUZlCnY4tptmrFsL8rs=; b=kCpuej15kN2YV/2UuL1O7sTA573B4XpEBeWaH8qgymJaqvps38t8KqDdPM3FhPrge3kDf3 5Owd5q6QKhVFS0TvZ9SiRCvE3guqKPbQ2RVckt5W5tQ6BwiyMPOnT0otA6z1rygdj9UcpA ZOi0sZZ6zKKjKSi9bNayjeZRIa58iJsSONRqqPRXhMRqRLf9duT2BDe4SfvofePNxZH8G6 1VBJlCST5Oh4sSCOelx9v9Du9klvhywFLjzCU//Ka0l2xEToGT8w+tPPmxdJVjiyYtyASH M9JLuq0rihNOGqSB33kB8PI+cw8WLRfulJ+rLhD0T19YX57qnOLm4g59ZCPZog== Received: from freyja (p4fc0ace3.dip0.t-ipconnect.de [79.192.172.227]) (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) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id F2E1024001B for ; Wed, 29 Jan 2025 11:27:02 +0100 (CET) Date: Wed, 29 Jan 2025 11:27:01 +0100 From: FreeBSD User To: freebsd-current@freebsd.org Subject: ZFS: Rescue FAULTED Pool Message-ID: <20250129112701.0c4a3236@freyja> Organization: Heimstatt X-Mailer: Claws Mail 4.3.0 (GTK 3.24.43; amd64-portbld-freebsd14.1) 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-Rspamd-UID: 6691f4 X-Rspamd-UID: deeec0 X-Spamd-Result: default: False [-4.10 / 15.00]; RBL_SENDERSCORE_REPUT_9(-1.00)[85.220.129.60:from]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.60:from]; MIME_GOOD(-0.10)[text/plain]; HAS_ORG_HEADER(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; RCVD_TLS_ALL(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4Yjdcq3yhMz40R3 Hello, a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable anymore. neither with import -F/-f. Although this pool is on an experimental system (no backup available) it contains some data to reconstruct them would take a while, so I'd like to ask whether there is a way to try to "de-fault" such a pool. The pool is comprised from 7 drives as a RAIDZ1, one of the SSDs faulted but I pulled the wrong one, so the pool ran into suspended state. The host is running the lates Xigmanas BETA, which is effectively FreeBSD 14.1-p2, just for the record. I do not want to give up, since I hoped there might be a rude but effective way to restore the pool even under datalosses ... Thanks in advance, Oliver From nobody Wed Jan 29 15:16:50 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 4Yjm3P53pVz5mskT; Wed, 29 Jan 2025 15:17:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yjm3P04tCz3SYJ; Wed, 29 Jan 2025 15:17:04 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 50TFGoh1044325; Wed, 29 Jan 2025 17:16:53 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 50TFGoh1044325 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 50TFGoe4044324; Wed, 29 Jan 2025 17:16:50 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 29 Jan 2025 17:16:50 +0200 From: Konstantin Belousov To: jenkins-admin@freebsd.org Cc: markj@freebsd.org, dev-ci@freebsd.org, current@freebsd.org Subject: Re: FreeBSD-main-amd64-test - Build #25976 - Still unstable Message-ID: References: <836411994.1827.1738118680596@jenkins.ci.freebsd.org> <1216833277.1845.1738128576212@jenkins.ci.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=us-ascii Content-Disposition: inline In-Reply-To: <1216833277.1845.1738128576212@jenkins.ci.freebsd.org> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on tom.home X-Rspamd-Queue-Id: 4Yjm3P04tCz3SYJ X-Spamd-Bar: ---- 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:6939, ipnet:2001:470::/32, country:US] On Wed, Jan 29, 2025 at 05:29:35AM +0000, jenkins-admin@FreeBSD.org wrote: > FreeBSD-main-amd64-test - Build #25976 (4da070ce6c015a994ec4ecf3d31ee94810ea19f1) - Still unstable > > Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25976/ > Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25976/changes > Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25976/console > > Status explanation: > "Unstable" - some tests are suspected being broken by the following changes > "Still Unstable" - the failing test cases have not been fixed by these > following changes and this is a notification to note that > these changes have not been fully tested by the CI system > > Change summaries: > (Those commits are likely but not certainly responsible) > > 6ee34bca48a9e0867d46b24a78855e225d46ddda by kib: > crtbegin: accurately check for the end of .dtors > > 21502f9a926c7e0c24ce230bb029fde4bf570a14 by kib: > crtend: accurately check for the start of .ctors > > 51688136b161089b317edc34c3a3e9b40d54a18a by markj: > libdtrace: Use designators to initialize the opcode array > > 70c067062217a5295ed321427b91cfd857c18b77 by markj: > dtrace/arm64: Simplify dtrace_getarg() slightly > > 4da070ce6c015a994ec4ecf3d31ee94810ea19f1 by markj: > dtrace/arm64: Fix enumeration of FBT return probes > > > > The failed test cases: > > 4 tests failed. > FAILED: lib.csu.dynamiclib.cxx_constructors.__test_cases_list__ > > Error Message: > Test program did not exit cleanly > > FAILED: lib.csu.dynamiclib.fini_test.__test_cases_list__ > > Error Message: > Test program did not exit cleanly > > FAILED: lib.csu.dynamiclib.init_test.__test_cases_list__ > > Error Message: > Test program did not exit cleanly Could anybody explain what does break there? I run the 'kyua test -k /usr/tests/lib/csu/Kyuafile' command locally after my recent changes to lib/csu/crtbegin/end.c, and it succeeds. I believe I saw the sporadic mails with the similar failures before. From nobody Wed Jan 29 16:11:40 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 4YjnGf3Pwtz5lV07 for ; Wed, 29 Jan 2025 16:11:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com [209.85.208.41]) (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 4YjnGf1j3wz3cf9 for ; Wed, 29 Jan 2025 16:11:54 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f41.google.com with SMTP id 4fb4d7f45d1cf-5d3e6274015so12997573a12.0 for ; Wed, 29 Jan 2025 08:11:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738167112; x=1738771912; h=content-transfer-encoding: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=FVI1lP2nYFc7GITLlvknp3warcpAnXjg9LXWT984QMk=; b=jXOAXGDYgz9g7/DLJa62uqUe+1Bz3/W2ZCA2mIpX8VpnbJuJPgJUODMyKQ6J0or5xS yxwoXX4MtriZTWAzLASFNHM5BLUHlPp4pqflHF7Kc/tkQwwh3SorpfW/8JYE/gnTGtr1 as+e3OgMur6br9/LWSavRE+LsYSsuGxy6jfyeEgzeXl+kjsWrp4Hadkbb83OQin8idOt RRqS1ZZ9uijGzEs1Y5yQqxPsOusf1rdGui13q7Ik22YYfwhK5AIn2T8f2Xyo26jHeJDz 1XE677wiCykuz9UsoVX7fIbWPB8mGRUIfZY4GGfuiS51B3Um7mMv/Idgn4yeIPGXhTD9 qoqw== X-Gm-Message-State: AOJu0YxFBxoJogKW+vHaGbiEi6xN6Fgp8Mqgjvv5j7a2Sx5+wHYdnsIL FxqKWldHBU/GvO6zw2ti+eD8rIrLgnp020CBERzJ+dBIzFQCpJTxZni8a+umf4HP/7oL7CKD0Ss AP4Uzb3965rXl7++XCetk8q2nq5kENA== X-Gm-Gg: ASbGncsvRtHFA86i8eefiPl5oD565/gbEwiTbys68CItS/ZYPmtmaP/CRZ+VQJbk8/x z5sW72c2y8AasMe2R7cv/F+f3S3WbbTCAGD0dooLy3XZvQV8Yi4j+Yw3XpzsUkLpFHCLBsrETxi QPMICgU0g= X-Google-Smtp-Source: AGHT+IFZUA8SonVHSIgemIfSB7rAc6rIb2ABuG/IDI2KaPq3a+dcqNWDmXs64s55pFlI6oxkZM5kM8HSayfLCIgrLu4= X-Received: by 2002:a05:6402:34c8:b0:5d4:1ac2:271b with SMTP id 4fb4d7f45d1cf-5dc5efc09acmr4166932a12.11.1738167112009; Wed, 29 Jan 2025 08:11:52 -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: <20250129112701.0c4a3236@freyja> In-Reply-To: <20250129112701.0c4a3236@freyja> From: Alan Somers Date: Wed, 29 Jan 2025 09:11:40 -0700 X-Gm-Features: AWEUYZlQxws04C-T637ftjevpDDwbbdUx0seerw23QFj_MVwdp_JKOEdYiZd8XM Message-ID: Subject: Re: ZFS: Rescue FAULTED Pool To: FreeBSD User Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YjnGf1j3wz3cf9 X-Spamd-Bar: ---- 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:209.85.128.0/17, country:US] On Wed, Jan 29, 2025 at 3:27=E2=80=AFAM FreeBSD User wrote: > > Hello, > > a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable > anymore. neither with import -F/-f. > Although this pool is on an experimental system (no backup available) > it contains some data to reconstruct them would take a while, so I'd > like to ask whether there is a way to try to "de-fault" such a pool. > > The pool is comprised from 7 drives as a RAIDZ1, one of the SSDs > faulted but I pulled the wrong one, so the pool ran into suspended > state. > The host is running the lates Xigmanas BETA, which is effectively > FreeBSD 14.1-p2, just for the record. > > I do not want to give up, since I hoped there might be a rude but > effective way to restore the pool even under datalosses ... > > Thanks in advance, > > Oliver Reinserting the wrongly pulled SSD and rebooting should be sufficient. Have you not yet tried that? If you really can't reboot for some reason, you could try "zpool clear". However, the only time I tried that to fix a suspended pool it resulted in some data corruption. So I recommend rebooting instead. From nobody Wed Jan 29 16:16:26 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 4YjnN817Tcz5lVWS; Wed, 29 Jan 2025 16:16:40 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ej1-f43.google.com (mail-ej1-f43.google.com [209.85.218.43]) (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 4YjnN74sVYz3fFP; Wed, 29 Jan 2025 16:16:39 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-f43.google.com with SMTP id a640c23a62f3a-aaef00ab172so1099557666b.3; Wed, 29 Jan 2025 08:16:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738167398; x=1738772198; h=content-transfer-encoding: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=JcZgqHPTMj8lRdVaDycts/ejZkfxVyALYG78XlCxaAg=; b=ICrm7cu5qry1xkeYjEykbpFsAMGMfGBh26fvTS2k066llm+qGUbwXfNtN/QLJx22FS pDlynPKC4C1FU20xWjJkFxni6tpb1DkQRNSqkFTGMFZ0E4oMbpxyZGtXi5PT+DWo5jn3 v7uerbRpHinFVpUuJ5HZQE8+eMTtthG2UqVTJXpnhg/8zeq3iMKzrc4ps9lae7I6Jn/f PUIpSCh5ze6dvQostQ52fmGEBSf07SfEaVLz4gC8EbwWQEjGAdMv5dnhKfnf0dfiswUh SCY7Zuv6Po9pmJ/IOy6Qg46FX1NRSiFnJdH/qMrQ2JQ7pr2pPM3KYF2/HM6PT2jsajGo EwYg== X-Forwarded-Encrypted: i=1; AJvYcCVHRBaCQz+eiogQxbxjkN3BpHQ9JmuuSIhJnqXva6reu5c911GRnpuCfj0pVAgzTlueNhasC2Hs@freebsd.org, AJvYcCVeUld64ziLpYG5/7GiQxrrUenRTaorfBiEyAnkH6qi+ez2/QLFz5vn+xY39izM12v2MSsbUcA1@freebsd.org, AJvYcCX/JUttEI0TvmGS3GslCMYdliUq67uJP7BeWUnqf8Joz8rPstZqXMqjNGsmSgX7wDZks8i/UY4=@freebsd.org X-Gm-Message-State: AOJu0Yw8wBDvEcx/XFf9RrPwl3yuF1KhFSKqP3cGWHJ9evG4T8rhAQUJ JeH5y9OZWdXhgyyByyELDaXtD5t1j2TttDiePrWOIZIyaYimRHfg+mYLiX7RpLvAK7E3w0LHCop DluPPSbshN5Mo+pqzfEnOlibTqn6uYF2t X-Gm-Gg: ASbGnctSK8AXqCYxt4+9Vtybqe08kDOANBrBOQ2cKjyfhqvh6PlWdnJRmRZCtOxhxtE Jv/FhKpr5NARv7Su3HzArIO+MtUo1xGijTgdvUn5DqlmQjzBKs0DhKejckJT/QtsyoBzryJRo X-Google-Smtp-Source: AGHT+IEcTdQAcjvyBov9ZR6+GBfSQaz+LxlHg9Uk8gnmpBP8heFzW25quUvq8WG0vMZjxxfYC2c8u4hD0M8AoToLBp4= X-Received: by 2002:a05:6402:5205:b0:5d9:ae5:8318 with SMTP id 4fb4d7f45d1cf-5dc5efec050mr7758671a12.20.1738167398043; Wed, 29 Jan 2025 08:16:38 -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: <836411994.1827.1738118680596@jenkins.ci.freebsd.org> <1216833277.1845.1738128576212@jenkins.ci.freebsd.org> In-Reply-To: From: Alan Somers Date: Wed, 29 Jan 2025 09:16:26 -0700 X-Gm-Features: AWEUYZmIka93exkeQhiW-Vq6FrAqlZl3GCWFp0RImBIbRM7AOTTqCzFGVDNWxXw Message-ID: Subject: Re: FreeBSD-main-amd64-test - Build #25976 - Still unstable To: Konstantin Belousov Cc: jenkins-admin@freebsd.org, markj@freebsd.org, dev-ci@freebsd.org, current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YjnN74sVYz3fFP X-Spamd-Bar: ---- 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:209.85.128.0/17, country:US] On Wed, Jan 29, 2025 at 8:17=E2=80=AFAM Konstantin Belousov wrote: > > On Wed, Jan 29, 2025 at 05:29:35AM +0000, jenkins-admin@FreeBSD.org wrote= : > > FreeBSD-main-amd64-test - Build #25976 (4da070ce6c015a994ec4ecf3d31ee94= 810ea19f1) - Still unstable > > > > Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/2= 5976/ > > Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/259= 76/changes > > Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/2597= 6/console > > > > Status explanation: > > "Unstable" - some tests are suspected being broken by the following cha= nges > > "Still Unstable" - the failing test cases have not been fixed by these > > following changes and this is a notification to note= that > > these changes have not been fully tested by the CI s= ystem > > > > Change summaries: > > (Those commits are likely but not certainly responsible) > > > > 6ee34bca48a9e0867d46b24a78855e225d46ddda by kib: > > crtbegin: accurately check for the end of .dtors > > > > 21502f9a926c7e0c24ce230bb029fde4bf570a14 by kib: > > crtend: accurately check for the start of .ctors > > > > 51688136b161089b317edc34c3a3e9b40d54a18a by markj: > > libdtrace: Use designators to initialize the opcode array > > > > 70c067062217a5295ed321427b91cfd857c18b77 by markj: > > dtrace/arm64: Simplify dtrace_getarg() slightly > > > > 4da070ce6c015a994ec4ecf3d31ee94810ea19f1 by markj: > > dtrace/arm64: Fix enumeration of FBT return probes > > > > > > > > The failed test cases: > > > > 4 tests failed. > > FAILED: lib.csu.dynamiclib.cxx_constructors.__test_cases_list__ > > > > Error Message: > > Test program did not exit cleanly > > > > FAILED: lib.csu.dynamiclib.fini_test.__test_cases_list__ > > > > Error Message: > > Test program did not exit cleanly > > > > FAILED: lib.csu.dynamiclib.init_test.__test_cases_list__ > > > > Error Message: > > Test program did not exit cleanly > > Could anybody explain what does break there? > I run the 'kyua test -k /usr/tests/lib/csu/Kyuafile' command locally afte= r > my recent changes to lib/csu/crtbegin/end.c, and it succeeds. > > I believe I saw the sporadic mails with the similar failures before. I have no idea. It works for me locally, too. The only way to find out would be to examine it in the failing environment. Running "/usr/tests/lib/csu/dynamiclib/init_test -l" might be revealing. From nobody Wed Jan 29 16:19:56 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 4YjnS22yKKz5lVX6; Wed, 29 Jan 2025 16:20:02 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 4YjnS14yTJz3g5R; Wed, 29 Jan 2025 16:20:01 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-io1-xd2c.google.com with SMTP id ca18e2360f4ac-844eac51429so537999539f.2; Wed, 29 Jan 2025 08:20:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738167601; x=1738772401; 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=/kGQZrH8Upv6hR0bfSH4wv2rmA2CCppqDwEvrWtS34g=; b=XyRgeUXPYmEb6v4+W1jf9T5jkO77PnM4xX4RpQPoUaK5tTHFaTm2uG80xLFbDil+Ab MCEwDrGLUCtSQRuzXHEr4h0PBNSEWfpT8F8TqnBGJcqJIwrWqMAe01YyKbNw3TFuwHfL R2KdUuENWkrPBUhom1mRNVaT6A+taY2npmtXD0m/pMHk9Db8nW2ml96T3M0NBoDJdGbN qabgyM1TB7khp8VmPgn4Yvav2VtbLDQG4hBz7fQh661o0/rZmyT7UEAWB0FMW5Yhq1Qc SdGt7UxIS/kNRJyloW38y+gPYAoIARytEOWF4EW5iUvZwOI59VLmiE0VxeN54lojZyQT 6kZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738167601; x=1738772401; 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=/kGQZrH8Upv6hR0bfSH4wv2rmA2CCppqDwEvrWtS34g=; b=UJNuymUg0Yh/jIKN9RpmutLbq7PZJQb1YPivuMdXCInneefSlB8O2YQD8sWQYr8a5+ n1VRcubgbCOfocanZ0ZDhVBZdo2AzaRKdjtui+ms+QbXo7qdqTmJK0VfAD90G97Rfqgt jrNFObxOlBHSwNV+U3f/uukiE/w1ipH14LhT3vmIQiUVl3QeFovbBybSgiryQl76QbxL biQp8Pt1OL0KW5jdp+EYi6cIbystbJBreeY7dYtE5Hvullx6gGOiFZbOCiFc2Z71KvUQ qSkezJiaYcEzjyCPhOeEmyWzhL4XZIP6TAdxA/YEA5Dd94TU0/MZ3eyhjw91edVMorS6 DBfQ== X-Forwarded-Encrypted: i=1; AJvYcCVFJZd259MZkbbq/eh+7fqf4+lSwaNgtf39OXHkQx15UsbFkzmqcLkN1w+rY3SW8yFGV11VIeF6@freebsd.org, AJvYcCVsDu1JRI92doxDGAyAEbDk5YTyjPvfHcH3DzpJD0teCF/Eq5mzdLxuZAwG0yMtJA1EsRwMp4UTHA==@freebsd.org, AJvYcCW1lP1GYLX6DSXTAOWA2m0gpR1kIGHcEyvofcL5osiuOp8K6U9C25zuPIoq+TUrX5x8Ev3QwAU=@freebsd.org, AJvYcCXCYpewecWwvLca5DiLRK5+T4uHlPfbuc8fTRleOeAzoNmI6GJJLdt6KLYsVEmAtXgUnhLE4d+S@freebsd.org X-Gm-Message-State: AOJu0Yx2haV3waeZKoDmatsS2C3V4GwfNFbOfSUGQcAoqJ9U0d8OMgaJ d9BR6lprTRO+ZuGV7hw9s1m4ushKfylqcV1fo4oz6AtiWpSuO5HlvEwI6g== X-Gm-Gg: ASbGnctxKUiA0nn5D66X3zgM5JrWpslUC7Gl4oehGjccipXPwblc/xTdKq+NDfU2Q+y u+HDs+/sdkKlOSpT5LBhL1bb/Okn2Mg2QL3MwBRocx/NoY+UxhXr1qRHOvAvrVcOaLCAlVlq38x Fig6piEwm+D+9UUhgu83P5rjR4Iz51q6K/lbNCSl8O5gZMdtg6u7AbWFiKbZD1tkZh3IcTjTwHO GxLfNjngRN76aVQMbGC2eQRxbOQsYhXQscYrGZe0t1QQo6PHhB5Z7fIH649jL+ym4vRGTXxzyi2 yZKriCBe1/UlCLxDLxjgNdd0SUF+LQ== X-Google-Smtp-Source: AGHT+IGzjsk8bLZ8La0NiL4eX1tnDzPskOXzDrWExgTjsjUfUU8ErpLubbFFvFc2KOYbMgQCHZXz3w== X-Received: by 2002:a05:6602:360d:b0:83a:b500:3513 with SMTP id ca18e2360f4ac-85427e400cbmr371860339f.8.1738167600675; Wed, 29 Jan 2025 08:20:00 -0800 (PST) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id ca18e2360f4ac-8521dde9f65sm401182439f.5.2025.01.29.08.19.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Jan 2025 08:19:59 -0800 (PST) Date: Wed, 29 Jan 2025 11:19:56 -0500 From: Mark Johnston To: Konstantin Belousov Cc: jenkins-admin@freebsd.org, dev-ci@freebsd.org, current@freebsd.org, emaste@freebsd.org, brooks@freebsd.org Subject: Re: FreeBSD-main-amd64-test - Build #25976 - Still unstable Message-ID: References: <836411994.1827.1738118680596@jenkins.ci.freebsd.org> <1216833277.1845.1738128576212@jenkins.ci.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=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4YjnS14yTJz3g5R X-Spamd-Bar: ---- 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] On Wed, Jan 29, 2025 at 05:16:50PM +0200, Konstantin Belousov wrote: > On Wed, Jan 29, 2025 at 05:29:35AM +0000, jenkins-admin@FreeBSD.org wrote: > > FreeBSD-main-amd64-test - Build #25976 (4da070ce6c015a994ec4ecf3d31ee94810ea19f1) - Still unstable > > > > Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25976/ > > Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25976/changes > > Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25976/console > > > > Status explanation: > > "Unstable" - some tests are suspected being broken by the following changes > > "Still Unstable" - the failing test cases have not been fixed by these > > following changes and this is a notification to note that > > these changes have not been fully tested by the CI system > > > > Change summaries: > > (Those commits are likely but not certainly responsible) > > > > 6ee34bca48a9e0867d46b24a78855e225d46ddda by kib: > > crtbegin: accurately check for the end of .dtors > > > > 21502f9a926c7e0c24ce230bb029fde4bf570a14 by kib: > > crtend: accurately check for the start of .ctors > > > > 51688136b161089b317edc34c3a3e9b40d54a18a by markj: > > libdtrace: Use designators to initialize the opcode array > > > > 70c067062217a5295ed321427b91cfd857c18b77 by markj: > > dtrace/arm64: Simplify dtrace_getarg() slightly > > > > 4da070ce6c015a994ec4ecf3d31ee94810ea19f1 by markj: > > dtrace/arm64: Fix enumeration of FBT return probes > > > > > > > > The failed test cases: > > > > 4 tests failed. > > FAILED: lib.csu.dynamiclib.cxx_constructors.__test_cases_list__ > > > > Error Message: > > Test program did not exit cleanly > > > > FAILED: lib.csu.dynamiclib.fini_test.__test_cases_list__ > > > > Error Message: > > Test program did not exit cleanly > > > > FAILED: lib.csu.dynamiclib.init_test.__test_cases_list__ > > > > Error Message: > > Test program did not exit cleanly > > Could anybody explain what does break there? > I run the 'kyua test -k /usr/tests/lib/csu/Kyuafile' command locally after > my recent changes to lib/csu/crtbegin/end.c, and it succeeds. > > I believe I saw the sporadic mails with the similar failures before. The logs from the test suite run are useless, and I cannot reproduce the problem locally either. I just remembered that one can fetch the test VM images from artifact.ci.freebsd.org. So, I tried that. The problem is that /usr/tests/lib/csu/dynamiclib/libh_csu.so is missing, and the test programs under /usr/tests/lib/csu/dynamiclib link against it, so they refuse to start. It looks like the CI scripts build the VM image using artifacts from "make packagesystem", which I'm unfamiliar with. It looks like the tests.txz snapshots are also missing libh_csu.so, so this is some bug in the release scripts and/or the csu test makefiles. The failures apparently started with commit 41adc5f29ba6955e09f46e4d2c25da6fcd263ba2, so maybe Ed or Brooks have some idea where the problem is. From nobody Thu Jan 30 02:37:53 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 4Yk3936zGrz5mv6Q for ; Thu, 30 Jan 2025 02:37:59 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx-01.divo.sbone.de (mx-01.divo.sbone.de [IPv6:2003:a:140a:2200:6:594:fffe:19]) (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 "mx-01.divo.sbone.de", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yk3930ZvGz3gyL for ; Thu, 30 Jan 2025 02:37:58 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zabbadoz.net header.s=20240622 header.b=P73ur5a3; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2003:a:140a:2200:6:594:fffe:19 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net; dmarc=pass (policy=none) header.from=zabbadoz.net Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id 5374FA64805 for ; Thu, 30 Jan 2025 02:37:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=zabbadoz.net; s=20240622; t=1738204674; bh=RaQKGP+8EcVXwo4lJv/jBOXJdaUbk0TFzdlrpg4C6sU=; h=Date:From:To:Subject; b=P73ur5a3rQ6EWGbUveA6hyVXuKbHAogyqY4ZUwPNdvJatxdO4cJXlrfLCHPFtxXnW FtVevPLQfFbYlM8A+6zRT5a/rGMNDi0hCiGRpxt41NwBHDdLvveAgAnP6+fJq0iE09 ofRG6j2Uz+GPHJoJxkg3AKtXh/k3kx4O5p87uaM/rYJ2sehs+1g2j8SmhUY+UEkfxg 5cCgOb5kSK4KKgOjmBJJj/c+nj835hZLLS1a1QPlLODRX5x8XzhqNuGlftZtdv1DzE b0WzhtVYjc0e/qfeopyqtwDeWfCtjud2XCGaOrl2pMI8r5Yh/9NgIhBAkmHNNDF87n fE+q1X/UDgWDfmxOEPrQvobnH4G+zxUgGbNutpW2tOlzM4D7v52ZTxk+My1KLHKwAe IS2UnTTHoANt/V4bnAPhUqkZxacaE1k96Av8WuiARqzWq/cyfBDi8X5qJQVQFwOGUj CjgITSo7DdHpxdfZKq1xsj+dIB/z09sr1oSgr77p10NBJXq34VyNM9CE0OnTP/qw5c gOSnzqcQ+zidx7l7fdHH/Gcto5e4LuIbxwiogCCXRzmBi5JNrCCTm+TWZh0YtDvzBp iqYBODaofTvFymMgxftdQd7PlJ3CDCkcyL9SiypjFUzQ4KOX2kUyNYkm3F/bN/YaQs uCTHlDsYuisDfRK2MK9wFrnE= Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 6E0D22D029DD for ; Thu, 30 Jan 2025 02:37:54 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id 80cWCeqCDAZg for ; Thu, 30 Jan 2025 02:37:53 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 654202D029D8 for ; Thu, 30 Jan 2025 02:37:53 +0000 (UTC) Date: Thu, 30 Jan 2025 02:37:53 +0000 (UTC) From: "Bjoern A. Zeeb" To: current@FreeBSD.org Subject: ddb reset command results in LOR and panic? (audit related?) Message-ID: X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 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; format=flowed; charset=US-ASCII X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; DMARC_POLICY_ALLOW(-0.50)[zabbadoz.net,none]; R_DKIM_ALLOW(-0.20)[zabbadoz.net:s=20240622]; R_SPF_ALLOW(-0.20)[+ip6:2003:a:140a:2200:6:594:fffe:19]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:3320, ipnet:2003::/19, country:DE]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[zabbadoz.net:+]; RCVD_COUNT_THREE(0.00)[4]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[current@FreeBSD.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4Yk3930ZvGz3gyL Hi. I broke into the kernel debugger after some driver went haywire. Upon typing reset to restart the machine I got the below. How can we still report a LOR and panic on a lock when we are resetting the machine from ddb? /bz db> reset lock order reversal: (sleepable after non-sleepable) 1st 0xfffff800031dfb40 thread (thread, sleep mutex) @ /sys/kern/subr_taskqueue.c:519 2nd 0xffffffff81cdecd0 audit_worker_lock (audit_worker_lock, sx) @ /sys/security/audit/audit_worker.c:512 panic: lock (sx) kernel linker not locked @ /sys/kern/kern_linker.c:1130 cpuid = 3 time = 1738203974 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0068c67180 vpanic() at vpanic+0x136/frame 0xfffffe0068c672b0 panic() at panic+0x43/frame 0xfffffe0068c67310 witness_unlock() at witness_unlock+0x154/frame 0xfffffe0068c67340 _sx_sunlock_int() at _sx_sunlock_int+0x4a/frame 0xfffffe0068c67370 linker_search_symbol_name_flags() at linker_search_symbol_name_flags+0x90/frame 0xfffffe0068c673a0 stack_sbuf_print_flags() at stack_sbuf_print_flags+0x8e/frame 0xfffffe0068c67430 witness_checkorder() at witness_checkorder+0xbf6/frame 0xfffffe0068c675f0 _sx_xlock() at _sx_xlock+0x60/frame 0xfffffe0068c67630 audit_rotate_vnode() at audit_rotate_vnode+0xd0/frame 0xfffffe0068c67740 kern_reboot() at kern_reboot+0x2a3/frame 0xfffffe0068c67780 db_reset() at db_reset+0x108/frame 0xfffffe0068c677b0 db_command() at db_command+0x30d/frame 0xfffffe0068c67870 db_command_loop() at db_command_loop+0x4d/frame 0xfffffe0068c67880 db_trap() at db_trap+0xe6/frame 0xfffffe0068c67910 kdb_trap() at kdb_trap+0x24f/frame 0xfffffe0068c67a60 trap() at trap+0x3cb/frame 0xfffffe0068c67b80 calltrap() at calltrap+0x8/frame 0xfffffe0068c67b80 --- trap 0x3, rip = 0xffffffff80ba6f4d, rsp = 0xfffffe0068c67c50, rbp = 0xfffffe0068c67c60 --- kdb_alt_break_internal() at kdb_alt_break_internal+0x15d/frame 0xfffffe0068c67c60 kdb_alt_break() at kdb_alt_break+0xb/frame 0xfffffe0068c67c70 uart_intr_rxready() at uart_intr_rxready+0xf4/frame 0xfffffe0068c67ca0 uart_intr() at uart_intr+0x138/frame 0xfffffe0068c67ce0 intr_event_handle() at intr_event_handle+0xc8/frame 0xfffffe0068c67d50 intr_execute_handlers() at intr_execute_handlers+0x63/frame 0xfffffe0068c67d80 Xapic_isr1() at Xapic_isr1+0xdc/frame 0xfffffe0068c67d80 --- interrupt, rip = 0xffffffff80bc0181, rsp = 0xfffffe0068c67e50, rbp = 0xfffffe0068c67ec0 --- taskqueue_run_locked() at taskqueue_run_locked+0x11/frame 0xfffffe0068c67ec0 taskqueue_thread_loop() at taskqueue_thread_loop+0xd3/frame 0xfffffe0068c67ef0 fork_exit() at fork_exit+0x82/frame 0xfffffe0068c67f30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0068c67f30 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- Uptime: 1h37m24s Automatic reboot in 15 seconds - press a key on the console to abort -- Bjoern A. Zeeb r15:7 From nobody Thu Jan 30 10:32:58 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 4YkFjL1HG5z5ltG4 for ; Thu, 30 Jan 2025 10:33:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkFjK4xJ2z3ZZt for ; Thu, 30 Jan 2025 10:33:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 50UAWxc8006741; Thu, 30 Jan 2025 12:33:02 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 50UAWxc8006741 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 50UAWwY5006734; Thu, 30 Jan 2025 12:32:58 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 30 Jan 2025 12:32:58 +0200 From: Konstantin Belousov To: "Bjoern A. Zeeb" Cc: current@freebsd.org Subject: Re: ddb reset command results in LOR and panic? (audit related?) 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: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on tom.home X-Rspamd-Queue-Id: 4YkFjK4xJ2z3ZZt X-Spamd-Bar: ---- 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:6939, ipnet:2001:470::/32, country:US] On Thu, Jan 30, 2025 at 02:37:53AM +0000, Bjoern A. Zeeb wrote: > Hi. > > I broke into the kernel debugger after some driver went haywire. > > Upon typing reset to restart the machine I got the below. > How can we still report a LOR and panic on a lock when we > are resetting the machine from ddb? > > /bz > > db> reset > lock order reversal: (sleepable after non-sleepable) > 1st 0xfffff800031dfb40 thread (thread, sleep mutex) @ /sys/kern/subr_taskqueue.c:519 > 2nd 0xffffffff81cdecd0 audit_worker_lock (audit_worker_lock, sx) @ /sys/security/audit/audit_worker.c:512 > panic: lock (sx) kernel linker not locked @ /sys/kern/kern_linker.c:1130 > cpuid = 3 > time = 1738203974 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0068c67180 > vpanic() at vpanic+0x136/frame 0xfffffe0068c672b0 > panic() at panic+0x43/frame 0xfffffe0068c67310 > witness_unlock() at witness_unlock+0x154/frame 0xfffffe0068c67340 > _sx_sunlock_int() at _sx_sunlock_int+0x4a/frame 0xfffffe0068c67370 > linker_search_symbol_name_flags() at linker_search_symbol_name_flags+0x90/frame 0xfffffe0068c673a0 > stack_sbuf_print_flags() at stack_sbuf_print_flags+0x8e/frame 0xfffffe0068c67430 > witness_checkorder() at witness_checkorder+0xbf6/frame 0xfffffe0068c675f0 > _sx_xlock() at _sx_xlock+0x60/frame 0xfffffe0068c67630 > audit_rotate_vnode() at audit_rotate_vnode+0xd0/frame 0xfffffe0068c67740 > kern_reboot() at kern_reboot+0x2a3/frame 0xfffffe0068c67780 > db_reset() at db_reset+0x108/frame 0xfffffe0068c677b0 This happens IMO due to audit shutdown hook which tried to do VFS ops during panic, then it went south. Perhaps something like this would fix your immediate issue. diff --git a/sys/security/audit/audit.c b/sys/security/audit/audit.c index 269e62db454a..8a9865bf233b 100644 --- a/sys/security/audit/audit.c +++ b/sys/security/audit/audit.c @@ -396,7 +396,8 @@ SYSINIT(audit_init, SI_SUB_AUDIT, SI_ORDER_FIRST, audit_init, NULL); void audit_shutdown(void *arg, int howto) { - + if (KERNEL_PANICED()) + return; audit_rotate_vnode(NULL, NULL); } (not even compiled). From nobody Thu Jan 30 11:35:42 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 4YkH6958crz5m54d for ; Thu, 30 Jan 2025 11:36:17 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [85.220.129.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkH670tQJz3lQV for ; Thu, 30 Jan 2025 11:36:14 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b="QeMl/fsh"; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.31 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id DFC47240F14; Thu, 30 Jan 2025 12:36:12 +0100 (CET) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id F3B5124050D; Thu, 30 Jan 2025 12:36:10 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1738236970; 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:references:references; bh=JSEs980FqFswRubeiFu9lWMtSuYmmaZIMPO2jH5lHFc=; b=QeMl/fsh/cQbQKtpXrvkP5pS2FVGOkeI2knDVZfl7M93W2VhTOeP7BhcFv45cZgkmFOoaE gvf9vcRViNkbj5fSO7Sbe5+5Y3FQxYiNJsgmOaLPi+Dm/FK1jy8vcjgowKnROlw6nMfX8t kQeq55LkydqKsANChjsYzG6lnCkXLu+vR5RkHdwmN8w3qda+VaPiFpbrfYCummVlwAencz nV/oeV+Ayl9m4cimaNthEhVU/KnJYU7CBYTpLAUSynr6RkI0surjnv5Adp2QHuxF8J9K1o +G12jdtHFlhXPSMQV6oxzCWGyVPGy8WxjodSA8HmzE/UQxKcDjdpKxzHfX5v7w== Received: from thor.sb211.local (dynamic-2a02-3100-24da-8d02-b536-28ce-4e02-f5af.310.pool.telefonica.de [IPv6:2a02:3100:24da:8d02:b536:28ce:4e02:f5af]) (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) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id B706A24001B; Thu, 30 Jan 2025 12:36:10 +0100 (CET) Date: Thu, 30 Jan 2025 12:35:42 +0100 From: A FreeBSD User To: David Wolfskill Cc: freebsd-current@freebsd.org Subject: Re: ZFS: Rescue FAULTED Pool Message-ID: <20250130123354.2d767c7c@thor.sb211.local> In-Reply-To: References: <20250129112701.0c4a3236@freyja> 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; boundary="Sig_/x9E+Jfrzy=ApROEyGk+XtpV"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: 100f5f X-Rspamd-UID: 6e4461 X-Spamd-Result: default: False [-6.70 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RBL_SENDERSCORE_REPUT_9(-1.00)[85.220.129.31:from]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.31:from]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Spamd-Bar: ------ X-Rspamd-Queue-Id: 4YkH670tQJz3lQV --Sig_/x9E+Jfrzy=ApROEyGk+XtpV Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Wed, 29 Jan 2025 03:45:25 -0800 David Wolfskill schrieb: Hello, thanks for responding. > On Wed, Jan 29, 2025 at 11:27:01AM +0100, FreeBSD User wrote: > > Hello, > >=20 > > a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable > > anymore. neither with import -F/-f. > > Although this pool is on an experimental system (no backup available) > > it contains some data to reconstruct them would take a while, so I'd > > like to ask whether there is a way to try to "de-fault" such a pool. =20 >=20 > Well, 'zpool clear ...' "Clears device errors in a pool." (from "man > zpool". >=20 > It is, however, not magic -- it doesn't actually fix anything. For the record: I tried EVERY network/search available method useful for c= ommon "administrators", but hoped people are abe to manipulate deeper stuff via z= db ... >=20 > (I had an issue with a zpool which had a single SSD device as a ZIL; the > ZIL device failed after it had accepted some data to be written to the > pool, but before the data could be read and transferred to the spinning > disks. ZFS was quite unhappy about that. I was eventually able to copy > the data elsewhere, destroy the old zpool, recreate it *without* that > single point of failure, then copy the data back. And I learned to > never create a zpool with a *single* device as a separate ZIL.) Well, in this case I do not use dedicated ZIL drives. I also made several e= xperiences with "single" ZIL drive setups, but a dedicated ZIL is mostly useful in cases we= re you have graveyard full of inertia-suffering, mass-spinning HDDs - if I'm right the = concept of SSD based ZIL would be of no use/effect in that case. So I ommited tose. >=20 > > The pool is comprised from 7 drives as a RAIDZ1, one of the SSDs > > faulted but I pulled the wrong one, so the pool ran into suspended > > state. =20 >=20 > Can you put the drive you pulled back in? Every single SSD originally plugged in is now back in place, even the fault= ed one (which doesn't report any faults at the moment). Although the pool isn't "importable", zdb reports its existence, amongst zr= oot (which resides on a dedicated drive). >=20 > > The host is running the lates Xigmanas BETA, which is effectively > > FreeBSD 14.1-p2, just for the record. > >=20 > > I do not want to give up, since I hoped there might be a rude but > > effective way to restore the pool even under datalosses ... > >=20 > > Thanks in advance, > >=20 > > Oliver > > .... =20 >=20 > Good luck! >=20 > Peace, > david Well, this is a hard and painful lecture to learn, if there is no chance to= get back the pool. A warning (but this seems to be useless in the realm of professionals): I u= sed a bunch of cheap spotmarket SATA SSDs, a brand called "Intenso" common also here in Go= od old Germany. Some of those SSDs do have working LED when used with a Fujitsu SAS HBA con= troller - but those died very quickly from suffering some bus errors. Another bunch of those SS= Ds do not have working LED (not blinking on access), but lasted a bit longer. The problem = with those SSDs is: I can not find the failing device easily by accessing the failed drive by w= riting massive data via dd, if possible.=20 I also ordered alternative SSDs from a more expensive brand - but bad Karma= ... Oliver --=20 A FreeBSD user --Sig_/x9E+Jfrzy=ApROEyGk+XtpV Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCZ5tkKQAKCRCxzvs8Oqok rw4JAP4lmC86YPOdB2uE6S/3kwNfKnZTqHBocfbsogaBPVvxMwEApkGuSYCXZh24 XlgNWo3K/WTYRYEmtmijWDewrxyIagE= =VLTO -----END PGP SIGNATURE----- --Sig_/x9E+Jfrzy=ApROEyGk+XtpV-- From nobody Thu Jan 30 12:05:54 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 4YkHmn5d1dz5m9DS for ; Thu, 30 Jan 2025 12:06:17 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gid2.gid.co.uk (ns0.gid.co.uk [IPv6:2001:470:94de::240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gid2.gid.co.uk", Issuer "gid2.gid.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkHmn2by6z3s3s for ; Thu, 30 Jan 2025 12:06:17 +0000 (UTC) (envelope-from rb@gid.co.uk) Authentication-Results: mx1.freebsd.org; none Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by gid2.gid.co.uk (8.15.2/8.15.2) with ESMTP id 50UC69AB041978; Thu, 30 Jan 2025 12:06:09 GMT (envelope-from rb@gid.co.uk) Received: from smtpclient.apple (moriarty.gid.co.uk [194.32.164.17]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 50UC64c7089441; Thu, 30 Jan 2025 12:06:04 GMT (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 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 \(3776.700.51.11.1\)) Subject: Re: ZFS: Rescue FAULTED Pool From: Bob Bishop In-Reply-To: <20250130123354.2d767c7c@thor.sb211.local> Date: Thu, 30 Jan 2025 12:05:54 +0000 Cc: "freebsd-current@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <075A3339-6327-4C96-91D9-2F225AA74B38@gid.co.uk> References: <20250129112701.0c4a3236@freyja> <20250130123354.2d767c7c@thor.sb211.local> To: A FreeBSD User X-Mailer: Apple Mail (2.3776.700.51.11.1) X-Rspamd-Queue-Id: 4YkHmn2by6z3s3s X-Spamd-Bar: ---- 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:6939, ipnet:2001:470::/32, country:US] Hi, > [trimmed] >=20 > Well, this is a hard and painful lecture to learn, if there is no = chance to get back the pool. Have you tried import -FX ? -FXn might tell you non-destructively whether that will work but I have = never been down this particular hole. > A warning (but this seems to be useless in the realm of = professionals): I used a bunch of > cheap spotmarket SATA SSDs, a brand called "Intenso" common also here = in Good old Germany. > Some of those SSDs do have working LED when used with a Fujitsu SAS = HBA controller - but those > died very quickly from suffering some bus errors. Another bunch of = those SSDs do not have > working LED (not blinking on access), but lasted a bit longer. The = problem with those SSDs is: > I can not find the failing device easily by accessing the failed drive = by writing massive data > via dd, if possible.=20 > I also ordered alternative SSDs from a more expensive brand - but bad = Karma ... Yeah well there=E2=80=99s quite enough things that might go wrong even = without throwing dodgy SSDs into the mix. > Oliver >=20 >=20 > --=20 >=20 > A FreeBSD user -- Bob Bishop rb@gid.co.uk From nobody Thu Jan 30 12:19: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 4YkJ4H2zGKz5mD36 for ; Thu, 30 Jan 2025 12:19:43 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from mail2.pluspunkthosting.de (mail2.pluspunkthosting.de [217.29.33.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkJ4H0hldz3w7T for ; Thu, 30 Jan 2025 12:19:42 +0000 (UTC) (envelope-from pmh@hausen.com) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (87.138.185.145) by mail2.pluspunkthosting.de (Axigen) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA id 254289; Thu, 30 Jan 2025 13:19:34 +0100 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 \(3776.700.51\)) Subject: Re: ZFS: Rescue FAULTED Pool From: "Patrick M. Hausen" In-Reply-To: <20250130123354.2d767c7c@thor.sb211.local> Date: Thu, 30 Jan 2025 13:19:23 +0100 Cc: David Wolfskill , freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20250129112701.0c4a3236@freyja> <20250130123354.2d767c7c@thor.sb211.local> To: A FreeBSD User X-Mailer: Apple Mail (2.3776.700.51) X-Rspamd-Queue-Id: 4YkJ4H0hldz3w7T X-Spamd-Bar: ---- 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:16188, ipnet:217.29.32.0/20, country:DE] Hi all, > Am 30.01.2025 um 12:35 schrieb A FreeBSD User = : > Well, in this case I do not use dedicated ZIL drives. I also made = several experiences with > "single" ZIL drive setups, but a dedicated ZIL is mostly useful in = cases were you have > graveyard full of inertia-suffering, mass-spinning HDDs - if I'm right = the concept of SSD > based ZIL would be of no use/effect in that case. So I ommited tose. Dedidated SLOG vdevs only make sense if your workload involves = synchronous writes like when running databases or VM virtual disks over NFS or iSCSI. > Every single SSD originally plugged in is now back in place, even the = faulted one (which > doesn't report any faults at the moment). >=20 > Although the pool isn't "importable", zdb reports its existence, = amongst zroot (which resides > on a dedicated drive). There a various things yet to try, but I have no personal experience = with them: - "force" read-only import - import referencing a past transaction group, i.e. a previous version = of the entire pool How to find these transaction groups - no idea, sorry. >>> The host is running the lates Xigmanas BETA, which is effectively >>> FreeBSD 14.1-p2, just for the record. This topic including sometimes successful recovery frequently pops up on = the TrueNAS forum. Did you ask in the Xigmanas community? Weren't they able to help? I know there are regulars on the TrueNAS forum who know what to do. = Maybe head over there? As I wrote there are threads going like: "please provide the output of `zdb something someting`" *output* "now to `zpool import something something`" ... etc. HTH, Patrick= From nobody Thu Jan 30 17:02: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 4YkQLM08Ghz5m2xH for ; Thu, 30 Jan 2025 17:02:19 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkQLL6NQZz3mq1; Thu, 30 Jan 2025 17:02:18 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738256538; 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:references:references; bh=i3zgnzcFNjaeJ2lYAWxHu15UgDc6tILdPEehAJTMlKE=; b=ucxUZCgUPXDmo6t1joOXgVsry782so1UOY5sYVEOL6Bp3JS8p2j941d0C+sZPO8mxu3Wbw yoonzoOhbtY2wDqW6C8ea+/2FVUjtNQB9jfR1FWoHChxix8EG/GeogThjVCxh/bb1Tjgol 657t2Yyd6pK8O5ZyE15cvdiUUleC5mMcQEb/KdeILZ13r7Hkxzl8vVta7imXsVQAgFDoby mT8gkWCzV5yvffeLiZAUBO4zaZLDGWxTFjFZpBZkqLOxjRNFIA/WTwYqcrd545BU8Stltp dXpRW7ESzEmjHbgBpqF7+VYYuebVBFzSMH3DK3mfu9JP7YwON9MLdPyf3l+m/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738256538; 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:references:references; bh=i3zgnzcFNjaeJ2lYAWxHu15UgDc6tILdPEehAJTMlKE=; b=eMn2L2oSII1GwHYkEHRzO9b5utW3Xj/bm3/pcbscWDybrUa2yVEsQ0cuGZUAsqzLE4CuQX KfpkZ77BmcLVWf2maohmX5mLc80aa0wqK3gbuMX1Y77O054tAUrfKP7xHRqZLaMalfZecV 3Yd8krowMPpMRFJw+MzCH+EOzB7rAfCoV6+3yRwmYcl6HbpRdNOR4OD6AGb4CBpuN6b4vF savNIV2HXIPWmtYf3ia+y8YiP6GWzCD1dTmQsQnDTHeod1a+foAhbUQV4sshzCqiTqmtEE 2utusQSCymnblZKdLgeDG3SZO5kkh7Mm6HI28YVAugncnCE22AoyfMjG2g3HWw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738256538; a=rsa-sha256; cv=none; b=C4y1gazdQgj4notYa4s/3BTrn5PYTzGzU8sBuLPVEakANpnSwqkuFuof0xHoHiDxIo3qE7 YESP7T4qeaAhLPz3eNJO8dlVmJEeN+hLXkNUKm8nzQL4FBjsbo/n3I5fGJdWAZAeSmYi6i +c+jOBd5noR1bHGTHjFG5AQf6xQTJEBdqRZBqlNERMCvOrNhCbzfpgObBi2wjr6vBDBb2J a3yrsGZpxpqw0MJCYga2lpETDDT3NHxma1YDYVIasCHRBOPYmY/IoFqXhWFe8ah5M3uj+9 PFf5+wbR68QkUUEuyEtDBnxOHfee2HCk0ML3d3lnW9Pw4M3J/qK/kQkUVyMhxw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YkQLL2vwNz18k0; Thu, 30 Jan 2025 17:02:18 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Thu, 30 Jan 2025 09:02:14 -0800 From: Gleb Smirnoff To: Alexander Leidinger Cc: Current FreeBSD Subject: Re: Difference in "netstat -rn" output in the last 2 months 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: On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote: A> something has changed in the output of "netstat -rn" between A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed as A> "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks some tools A> (e.g. iocage). Iocage uses python, I'm not sure if it uses netstat or some A> other interface, so it may not be directly related to netstat itself but A> could be related to some other stuff (netlink maybe?). A> A> Does this ring a bell for someone? I created review to restore the default behavior and make new behavior optional: https://reviews.freebsd.org/D48729 -- Gleb Smirnoff From nobody Thu Jan 30 20:58:28 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 4YkWb01BW8z5mjHZ for ; Thu, 30 Jan 2025 20:58:36 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from tor1-11.mx.scaleengine.net (tor1-11.mx.scaleengine.net [IPv6:2001:470:1:474::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkWZz2Wbxz3KMg for ; Thu, 30 Jan 2025 20:58:35 +0000 (UTC) (envelope-from allanjude@freebsd.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2001:470:1:474::25 is neither permitted nor denied by domain of allanjude@freebsd.org) smtp.mailfrom=allanjude@freebsd.org; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=freebsd.org (policy=none) Received: from [10.1.1.3] (senat1-01.HML3.ScaleEngine.net [209.51.186.5]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by tor1-11.mx.scaleengine.net (Postfix) with ESMTPSA id C24AE1DABB for ; Thu, 30 Jan 2025 20:58:28 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 tor1-11.mx.scaleengine.net C24AE1DABB Message-ID: <3ee5884e-f1e5-4911-bc07-6fd8b5460bb3@freebsd.org> Date: Thu, 30 Jan 2025 15:58:28 -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: Mozilla Thunderbird Subject: Re: Difference in "netstat -rn" output in the last 2 months To: freebsd-current@freebsd.org References: Content-Language: en-US From: Allan Jude Autocrypt: addr=allanjude@freebsd.org; keydata= xsFNBFVwZcYBEADwrZDH0xe0ZVjc9ORCc6PcBLwS/RTXA6NkvpD6ea02pZ8lPOVgteuuugFc D34LdDbiWr+479vfrKBh+Y38GL0oZ0/13j10tIlDMHSa5BU0y6ACtnhupFvVlQ57+XaJAb/q 7qkfSiuxVwQ3FY3PL3cl1RrIP5eGHLA9hu4eVbu+FOX/q/XVKz49HaeIaxzo2Q54572VzIo6 C28McX9m65UL5fXMUGJDDLCItLmehZlHsQQ+uBxvODLFpVV2lUgDR/0rDa0B9zHZX8jY8qQ7 ZdCSy7CwClXI054CkXZCaBzgxYh/CotdI8ezmaw7NLs5vWNTxaDEFXaFMQtMVhvqQBpHkfOD 7rjjOmFw00nJL4FuPE5Yut0CPyx8vLjVmNJSt/Y8WxxmhutsqJYFgYfWl/vaWkrFLur/Zcmz IklwLw35HLsCZytCN5A3rGKdRbQjD6QPXOTJu0JPrJF6t2xFkWAT7oxnSV0ELhl2g+JfMMz2 Z1PDmS3NRnyEdqEm7NoRGXJJ7bgxDbN+9SXTyOletqGNXj/bSrBvhvZ0RQrzdHAPwQUfVSU2 qBhQEi2apSZstgVNMan0GUPqCdbE2zpysg+zT7Yhvf9EUQbzPL4LpdK1llT9fZbrdMzEXvEF oSvwJFdV3sqKmZc7b+E3PuxK6GTsKqaukd/3Cj8aLHG1T1im1QARAQABzSJBbGxhbiBKdWRl IDxhbGxhbmp1ZGVAZnJlZWJzZC5vcmc+wsF/BBMBAgApBQJVcGXGAhsjBQkSzAMABwsJCAcD AgEGFQgCCQoLBBYCAwECHgECF4AACgkQGZU1PhKYC34Muw/+JOKpSfhhysWFYiRXynGRDe07 Z6pVsn7DzrPUMRNZfHu8Uujmmy3p2nx9FelIY9yjd2UKHhug+whM54MiIFs90eCRVa4XEsPR 4FFAm0DAWrrb7qhZFcE/GhHdRWpZ341WAElWf6Puj2devtRjfYbikvj5+1V1QmDbju7cEw5D mEET44pTuD2VMRJpu2yZZzkM0i+wKFuPxlhqreufA1VNkZXI/rIfkYWK+nkXd9Efw3YdCyCQ zUgTUCb88ttSqcyhik/li1CDbXBpkzDCKI6I/8fAb7jjOC9LAtrZJrdgONywcVFoyK9ZN7EN AVA+xvYCmuYhR/3zHWH1g4hAm1v1+gIsufhajhfo8/wY1SetlzPaYkSkVQLqD8T6zZyhf+AN bC7ci44UsiKGAplB3phAXrtSPUEqM86kbnHg3fSx37kWKUiYNOnx4AC2VXvEiKsOBlpyt3dw WQbOtOYM+vkfbBwDtoGOOPYAKxc4LOIt9r+J8aD+gTooi9Eo5tvphATf9WkCpl9+aaGbSixB tUpvQMRnSMqTqq4Z7DeiG6VMRQIjsXDSLJEUqcfhnLFo0Ko/RiaHd5xyAQ4DhQ9QpkyQjjNf /3f/dYG7JAtoD30txaQ5V8uHrz210/77DRRX+HJjEj6xCxWUGvQgvEZf5XXyxeePvqZ+zQyT DX61bYw6w6bOwU0EVXBlxgEQAMy7YVnCCLN4oAOBVLZ5nUbVPvpUhsdA94/0/P+uqCIh28Cz ar56OCX0X19N/nAWecxL4H32zFbIRyDB2V/MEh4p9Qvyu/j4i1r3Ex5GhOT2hnit43Ng46z5 29Es4TijrHJP4/l/rB2VOqMKBS7Cq8zk1cWqaI9XZ59imxDNjtLLPPM+zQ1yE3OAMb475QwN UgWxTMw8rkA7CEaqeIn4sqpTSD5C7kT1Bh26+rbgJDZ77D6Uv1LaCZZOaW52okW3bFbdozV8 yM2u+xz2Qs8bHz67p+s+BlygryiOyYytpkiK6Iy4N7FTolyj5EIwCuqzfk0SaRHeOKX2ZRjC qatkgoD/t13PNT38V9tw3qZVOJDS0W6WM8VSg+F+bkM9LgJ8CmKV+Hj0k3pfGfYPOZJ/v18i +SmZmL/Uw2RghnwDWGAsPCKu4uZR777iw7n9Io6Vfxndw2dcS0e9klvFYoaGS6H2F13Asygr WBzFNGFQscN4mUW+ZYBzpTOcHkdT7w8WS55BmXYLna+dYer9/HaAuUrONjujukN4SPS1fMJ2 /CS/idAUKyyVVX5vozoNK2JVC1h1zUAVsdnmhEzNPsvBoqcVNfyqBFROEVLIPwq+lQMGNVjH ekLTKRWf59MEhUC2ztjSKkGmwdg73d6xSXMuq45EgIJV2wPvOgWQonoHH/kxABEBAAHCwWUE GAECAA8FAlVwZcYCGwwFCRLMAwAACgkQGZU1PhKYC34w5A//YViBtZyDV5O+SJT9FFO3lb9x Zdxf0trA3ooCt7gdBkdnBM6T5EmjgVZ3KYYyFfwXZVkteuCCycMF/zVw5eE9FL1+zz9gg663 nY9q2F77TZTKXVWOLlOV2bY+xaK94U4ytogOGhh9b4UnQ/Ct3+6aviCF78Go608BXbmF/GVT 7uhddemk7ItxM1gE5Hscx3saxGKlayaOsdPKeGTVJCDEtHDuOc7/+jGh5Zxpk/Hpi+DUt1ot 8e6hPYLIQa4uVx4f1xxxV858PQ7QysSLr9pTV7FAQ18JclCaMc7JWIa3homZQL/MNKOfST0S 2e+msuRwQo7AnnfFKBUtb02KwpA4GhWryhkjUh/kbVc1wmGxaU3DgXYQ5GV5+Zf4kk/wqr/7 KG0dkTz6NLCVLyDlmAzuFhf66DJ3zzz4yIo3pbDYi3HB/BwJXVSKB3Ko0oUo+6/qMrOIS02L s++QE/z7K12CCcs7WwOjfCYHK7VtE0Sr/PfybBdTbuDncOuAyAIeIKxdI2nmQHzl035hhvQX s4CSghsP319jAOQiIolCeSbTMD4QWMK8RL/Pe1FI1jC3Nw9s+jq8Dudtbcj2UwAP/STUEbJ9 5rznzuuhPjE0e++EU/RpWmcaIMK/z1zZDMN+ce2v1qzgV936ZhJ3iaVzyqbEE81gDxg3P+IM kiYh4ZtPB4Q= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.75 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; NEURAL_HAM_LONG(-0.99)[-0.994]; NEURAL_HAM_SHORT(-0.96)[-0.962]; ONCE_RECEIVED(0.20)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : No valid SPF, No valid DKIM,none]; FREEFALL_USER(0.00)[allanjude]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[]; TO_DN_NONE(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; 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-Spamd-Bar: -- X-Rspamd-Queue-Id: 4YkWZz2Wbxz3KMg On 1/30/2025 12:02 PM, Gleb Smirnoff wrote: > On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote: > A> something has changed in the output of "netstat -rn" between > A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed as > A> "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks some tools > A> (e.g. iocage). Iocage uses python, I'm not sure if it uses netstat or some > A> other interface, so it may not be directly related to netstat itself but > A> could be related to some other stuff (netlink maybe?). > A> > A> Does this ring a bell for someone? > > I created review to restore the default behavior and make new behavior > optional: > > https://reviews.freebsd.org/D48729 > Hi Gleb, Thanks for catching this while I was traveling. I agree that too many things break with this change, and it makes sense to put the new behaviour behind the double flag (-nn). -- Allan Jude From nobody Thu Jan 30 21:13:56 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 4YkWwq6vG1z5mlJ9 for ; Thu, 30 Jan 2025 21:14:03 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from tor1-11.mx.scaleengine.net (tor1-11.mx.scaleengine.net [209.51.186.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkWwq2TzJz3NQl for ; Thu, 30 Jan 2025 21:14:03 +0000 (UTC) (envelope-from allanjude@freebsd.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 209.51.186.6 is neither permitted nor denied by domain of allanjude@freebsd.org) smtp.mailfrom=allanjude@freebsd.org; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=freebsd.org (policy=none) Received: from [10.1.1.3] (senat1-01.HML3.ScaleEngine.net [209.51.186.5]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by tor1-11.mx.scaleengine.net (Postfix) with ESMTPSA id 882281D5F9 for ; Thu, 30 Jan 2025 21:13:57 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 tor1-11.mx.scaleengine.net 882281D5F9 Message-ID: <980401eb-f8f6-44c7-8ee1-5ff0c9e1c35c@freebsd.org> Date: Thu, 30 Jan 2025 16:13:56 -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: Mozilla Thunderbird Subject: Re: ZFS: Rescue FAULTED Pool To: freebsd-current@freebsd.org References: <20250129112701.0c4a3236@freyja> <20250130123354.2d767c7c@thor.sb211.local> Content-Language: en-US From: Allan Jude Autocrypt: addr=allanjude@freebsd.org; keydata= xsFNBFVwZcYBEADwrZDH0xe0ZVjc9ORCc6PcBLwS/RTXA6NkvpD6ea02pZ8lPOVgteuuugFc D34LdDbiWr+479vfrKBh+Y38GL0oZ0/13j10tIlDMHSa5BU0y6ACtnhupFvVlQ57+XaJAb/q 7qkfSiuxVwQ3FY3PL3cl1RrIP5eGHLA9hu4eVbu+FOX/q/XVKz49HaeIaxzo2Q54572VzIo6 C28McX9m65UL5fXMUGJDDLCItLmehZlHsQQ+uBxvODLFpVV2lUgDR/0rDa0B9zHZX8jY8qQ7 ZdCSy7CwClXI054CkXZCaBzgxYh/CotdI8ezmaw7NLs5vWNTxaDEFXaFMQtMVhvqQBpHkfOD 7rjjOmFw00nJL4FuPE5Yut0CPyx8vLjVmNJSt/Y8WxxmhutsqJYFgYfWl/vaWkrFLur/Zcmz IklwLw35HLsCZytCN5A3rGKdRbQjD6QPXOTJu0JPrJF6t2xFkWAT7oxnSV0ELhl2g+JfMMz2 Z1PDmS3NRnyEdqEm7NoRGXJJ7bgxDbN+9SXTyOletqGNXj/bSrBvhvZ0RQrzdHAPwQUfVSU2 qBhQEi2apSZstgVNMan0GUPqCdbE2zpysg+zT7Yhvf9EUQbzPL4LpdK1llT9fZbrdMzEXvEF oSvwJFdV3sqKmZc7b+E3PuxK6GTsKqaukd/3Cj8aLHG1T1im1QARAQABzSJBbGxhbiBKdWRl IDxhbGxhbmp1ZGVAZnJlZWJzZC5vcmc+wsF/BBMBAgApBQJVcGXGAhsjBQkSzAMABwsJCAcD AgEGFQgCCQoLBBYCAwECHgECF4AACgkQGZU1PhKYC34Muw/+JOKpSfhhysWFYiRXynGRDe07 Z6pVsn7DzrPUMRNZfHu8Uujmmy3p2nx9FelIY9yjd2UKHhug+whM54MiIFs90eCRVa4XEsPR 4FFAm0DAWrrb7qhZFcE/GhHdRWpZ341WAElWf6Puj2devtRjfYbikvj5+1V1QmDbju7cEw5D mEET44pTuD2VMRJpu2yZZzkM0i+wKFuPxlhqreufA1VNkZXI/rIfkYWK+nkXd9Efw3YdCyCQ zUgTUCb88ttSqcyhik/li1CDbXBpkzDCKI6I/8fAb7jjOC9LAtrZJrdgONywcVFoyK9ZN7EN AVA+xvYCmuYhR/3zHWH1g4hAm1v1+gIsufhajhfo8/wY1SetlzPaYkSkVQLqD8T6zZyhf+AN bC7ci44UsiKGAplB3phAXrtSPUEqM86kbnHg3fSx37kWKUiYNOnx4AC2VXvEiKsOBlpyt3dw WQbOtOYM+vkfbBwDtoGOOPYAKxc4LOIt9r+J8aD+gTooi9Eo5tvphATf9WkCpl9+aaGbSixB tUpvQMRnSMqTqq4Z7DeiG6VMRQIjsXDSLJEUqcfhnLFo0Ko/RiaHd5xyAQ4DhQ9QpkyQjjNf /3f/dYG7JAtoD30txaQ5V8uHrz210/77DRRX+HJjEj6xCxWUGvQgvEZf5XXyxeePvqZ+zQyT DX61bYw6w6bOwU0EVXBlxgEQAMy7YVnCCLN4oAOBVLZ5nUbVPvpUhsdA94/0/P+uqCIh28Cz ar56OCX0X19N/nAWecxL4H32zFbIRyDB2V/MEh4p9Qvyu/j4i1r3Ex5GhOT2hnit43Ng46z5 29Es4TijrHJP4/l/rB2VOqMKBS7Cq8zk1cWqaI9XZ59imxDNjtLLPPM+zQ1yE3OAMb475QwN UgWxTMw8rkA7CEaqeIn4sqpTSD5C7kT1Bh26+rbgJDZ77D6Uv1LaCZZOaW52okW3bFbdozV8 yM2u+xz2Qs8bHz67p+s+BlygryiOyYytpkiK6Iy4N7FTolyj5EIwCuqzfk0SaRHeOKX2ZRjC qatkgoD/t13PNT38V9tw3qZVOJDS0W6WM8VSg+F+bkM9LgJ8CmKV+Hj0k3pfGfYPOZJ/v18i +SmZmL/Uw2RghnwDWGAsPCKu4uZR777iw7n9Io6Vfxndw2dcS0e9klvFYoaGS6H2F13Asygr WBzFNGFQscN4mUW+ZYBzpTOcHkdT7w8WS55BmXYLna+dYer9/HaAuUrONjujukN4SPS1fMJ2 /CS/idAUKyyVVX5vozoNK2JVC1h1zUAVsdnmhEzNPsvBoqcVNfyqBFROEVLIPwq+lQMGNVjH ekLTKRWf59MEhUC2ztjSKkGmwdg73d6xSXMuq45EgIJV2wPvOgWQonoHH/kxABEBAAHCwWUE GAECAA8FAlVwZcYCGwwFCRLMAwAACgkQGZU1PhKYC34w5A//YViBtZyDV5O+SJT9FFO3lb9x Zdxf0trA3ooCt7gdBkdnBM6T5EmjgVZ3KYYyFfwXZVkteuCCycMF/zVw5eE9FL1+zz9gg663 nY9q2F77TZTKXVWOLlOV2bY+xaK94U4ytogOGhh9b4UnQ/Ct3+6aviCF78Go608BXbmF/GVT 7uhddemk7ItxM1gE5Hscx3saxGKlayaOsdPKeGTVJCDEtHDuOc7/+jGh5Zxpk/Hpi+DUt1ot 8e6hPYLIQa4uVx4f1xxxV858PQ7QysSLr9pTV7FAQ18JclCaMc7JWIa3homZQL/MNKOfST0S 2e+msuRwQo7AnnfFKBUtb02KwpA4GhWryhkjUh/kbVc1wmGxaU3DgXYQ5GV5+Zf4kk/wqr/7 KG0dkTz6NLCVLyDlmAzuFhf66DJ3zzz4yIo3pbDYi3HB/BwJXVSKB3Ko0oUo+6/qMrOIS02L s++QE/z7K12CCcs7WwOjfCYHK7VtE0Sr/PfybBdTbuDncOuAyAIeIKxdI2nmQHzl035hhvQX s4CSghsP319jAOQiIolCeSbTMD4QWMK8RL/Pe1FI1jC3Nw9s+jq8Dudtbcj2UwAP/STUEbJ9 5rznzuuhPjE0e++EU/RpWmcaIMK/z1zZDMN+ce2v1qzgV936ZhJ3iaVzyqbEE81gDxg3P+IM kiYh4ZtPB4Q= In-Reply-To: <20250130123354.2d767c7c@thor.sb211.local> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.79 / 15.00]; RBL_SENDERSCORE_REPUT_9(-1.00)[209.51.186.6:from]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; ONCE_RECEIVED(0.20)[]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : No valid SPF, No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[allanjude]; ASN(0.00)[asn:6939, ipnet:209.51.160.0/19, country:US]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; R_SPF_SOFTFAIL(0.00)[~all:c]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_ALL(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4YkWwq2TzJz3NQl On 1/30/2025 6:35 AM, A FreeBSD User wrote: > Am Wed, 29 Jan 2025 03:45:25 -0800 > David Wolfskill schrieb: > > Hello, thanks for responding. > >> On Wed, Jan 29, 2025 at 11:27:01AM +0100, FreeBSD User wrote: >>> Hello, >>> >>> a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable >>> anymore. neither with import -F/-f. >>> Although this pool is on an experimental system (no backup available) >>> it contains some data to reconstruct them would take a while, so I'd >>> like to ask whether there is a way to try to "de-fault" such a pool. >> >> Well, 'zpool clear ...' "Clears device errors in a pool." (from "man >> zpool". >> >> It is, however, not magic -- it doesn't actually fix anything. > > For the record: I tried EVERY network/search available method useful for common > "administrators", but hoped people are abe to manipulate deeper stuff via zdb ... > >> >> (I had an issue with a zpool which had a single SSD device as a ZIL; the >> ZIL device failed after it had accepted some data to be written to the >> pool, but before the data could be read and transferred to the spinning >> disks. ZFS was quite unhappy about that. I was eventually able to copy >> the data elsewhere, destroy the old zpool, recreate it *without* that >> single point of failure, then copy the data back. And I learned to >> never create a zpool with a *single* device as a separate ZIL.) > > Well, in this case I do not use dedicated ZIL drives. I also made several experiences with > "single" ZIL drive setups, but a dedicated ZIL is mostly useful in cases were you have > graveyard full of inertia-suffering, mass-spinning HDDs - if I'm right the concept of SSD > based ZIL would be of no use/effect in that case. So I ommited tose. > >> >>> The pool is comprised from 7 drives as a RAIDZ1, one of the SSDs >>> faulted but I pulled the wrong one, so the pool ran into suspended >>> state. >> >> Can you put the drive you pulled back in? > > Every single SSD originally plugged in is now back in place, even the faulted one (which > doesn't report any faults at the moment). > > Although the pool isn't "importable", zdb reports its existence, amongst zroot (which resides > on a dedicated drive). > >> >>> The host is running the lates Xigmanas BETA, which is effectively >>> FreeBSD 14.1-p2, just for the record. >>> >>> I do not want to give up, since I hoped there might be a rude but >>> effective way to restore the pool even under datalosses ... >>> >>> Thanks in advance, >>> >>> Oliver >>> .... >> >> Good luck! >> >> Peace, >> david > > > Well, this is a hard and painful lecture to learn, if there is no chance to get back the pool. > > A warning (but this seems to be useless in the realm of professionals): I used a bunch of > cheap spotmarket SATA SSDs, a brand called "Intenso" common also here in Good old Germany. > Some of those SSDs do have working LED when used with a Fujitsu SAS HBA controller - but those > died very quickly from suffering some bus errors. Another bunch of those SSDs do not have > working LED (not blinking on access), but lasted a bit longer. The problem with those SSDs is: > I can not find the failing device easily by accessing the failed drive by writing massive data > via dd, if possible. > I also ordered alternative SSDs from a more expensive brand - but bad Karma ... > > Oliver > > The most useful thing to share right now would be the output of `zpool import` (with no pool name) on the rebooted system. That will show where the issues are, and suggest how they might be solved. -- Allan Jude From nobody Fri Jan 31 21:16:27 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 4Yl7xF10k0z5n82g for ; Fri, 31 Jan 2025 21:16:33 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (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 "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yl7xC6hzbz3bG9 for ; Fri, 31 Jan 2025 21:16:31 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=SbRRnVWy; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org; dmarc=pass (policy=quarantine) header.from=blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 50VLGSEU005642 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Fri, 31 Jan 2025 16:16:29 -0500 (EST) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1738358189; bh=WDpZkejGuNd0M+DXjpq/qst84B6wqCXcVs85vEUZ5ws=; h=Date:To:From:Subject; b=SbRRnVWyLJrHNZyvm+gZ1M+/LBeh2H+KUCoslLC1fr0k53vRjpT2mfziMbvAnezb2 cVAhjT4aeHk+wQGHW2vQ2fW4II6tWFyYbHR8IApy744ot7IGIL5ywmt7KSQTps+LQo PvpB5vZWq3gFUN8Dsq9ZR1U2yv++AW0EFdpHi+aluCTDSznYnVfYMX3ZXjkBVbyP1q 4Z8fEYoBrLdXtlAc0XfNi9X8QGCBZbckielJ5fL8gJkLlKkKgIMrhZNtgaTcd3OvDP wE56auJp5SzlF5B/r9LxD2pfVzoR7Nn30HLrcocv9psPrau883pTztiu7ci0isMy41 wdUabhBOK2uMQ== Message-ID: <94cb266f-d3ab-4277-8f89-c4bfbd17d96d@blastwave.org> Date: Fri, 31 Jan 2025 16:16:27 -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: Mozilla Thunderbird To: freebsd-current@freebsd.org Content-Language: en-CA From: Dennis Clarke Subject: Safe to do the usual end-of-month buildworld/buildkernel on RISC-V ? Organization: GENUNIX Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 50VLGSEU005642 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Result: default: False [-3.59 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.89)[-0.892]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; 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-Spamd-Bar: --- X-Rspamd-Queue-Id: 4Yl7xC6hzbz3bG9 All : Not sure if I heard rumours correctly but perhaps someone can chime in on this. Was there a problem wherein the SiFive RISC-V board would panic with the latest kernel updates? Here I mean the "Unmatched". I have the new P550 on order and should be able to look at that next month ( tomorrow? more like next week ) but for now it is nice to have the SiFive Unmatched in a usable state. -- -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken From nobody Fri Jan 31 23:28:43 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 4YlBsn0pW5z5lysV for ; Fri, 31 Jan 2025 23:28:45 +0000 (UTC) (envelope-from dim@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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YlBsn00CBz3tXM; Fri, 31 Jan 2025 23:28:45 +0000 (UTC) (envelope-from dim@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738366125; 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=43PuM+Md8MzmVTYIEn563h1rVmm4MyNfgnilK+dqFxg=; b=KaOgh8FH9v8q4AFaQQ29VjJCIx69o1fdK9zKoOWxVP0Pj1p8n21JIGHK9ram95Ppp2RwQB qe8yKDceDtekvplBMn4G9qv4Qrn1ltNOfGhYln5q0cV2U99OKt10ovbI2kCuOny6DNUmPh NIogvueHV/kH3tVNZzVZKLA0Byi0MGak4cigY1P8L+hBH51Hy+PHPEppB+JArth8579Uff VfEP8MWza0ru3StG1egYZUJTglAlIYPoprwJ1AEDFvAN4FGBPStawFoTmVgaSUur9im2Wa mbix2hj5uZCTYr7kTSJXhzhLxSzHkd01hTRGTfZ+PTO6B7dES4vzBiJwDaZq7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738366125; 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=43PuM+Md8MzmVTYIEn563h1rVmm4MyNfgnilK+dqFxg=; b=LQpTNlChaxcVU4QgIGeFRBJjTUClMKvLpdIKAOPRq8xACBlJBbtZkGhl6BpSs/ZBmRjasi WDVu0RTYBBGW9EQ968wiOIlV+kSwhIZB029g/0PUJ2mAfmzj5ohEiMZzdtPUby6a8qfwRK TWo6jtZBNZ/lnNPimu8nYtiBaC6ltEr7Zjh8VcruQwzOGXjzWdQrObfvPb9XNToou0j12D /rbU9aAL4F1t+/qWvA18e9wTB1W/knC3uwBs82Hxg4PeKcWg/bCk9t7uXUL6tBa4RxEjNS 6SXPOpNi9M1/YRsGvFx1OT8xZ0SZ8Q90UlutGjHJF9EJslVamzmXDSe+e6VgnA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738366125; a=rsa-sha256; cv=none; b=LYP6/mU+6bEvYSNOTxz/XuDomlsDxmKU6MC9qPMxhWVolm+tc5bChRT+PPMjKfxKPoDTCS /F0WTGX/Vggh3G6iLR212QyPZXRUpQoZisS6CdGY+8EqLDW4F3dUgO3wXtbbRBmZJfcC4V KjjWjGdMG3EMGW8pBWK5eIRQbgcdrVSfzbUGtlX7vz339jlVSaleUI0HSBtnfsJIgrCXI1 W+W+pVOx9Pgyu1JSoEyuP4ZnP6IzUW/WaOdQID89ntCYIJGx2ymRfh88vQawVETXE0lhw9 aTH5MlT3H/oE5rzPOQF622TTXjzVpfpBk66bdZ/USJt0mKpwFViZu3wbLb/A7Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "tensor.andric.com", Issuer "R10" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 4YlBsm5b6Vzqt6; Fri, 31 Jan 2025 23:28:44 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtpclient.apple (longrow.home.andric.com [192.168.0.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 750B86EB32; Sat, 01 Feb 2025 00:28:43 +0100 (CET) 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 \(3731.700.6.1.9\)) Subject: Re: Safe to do the usual end-of-month buildworld/buildkernel on RISC-V ? From: Dimitry Andric In-Reply-To: <94cb266f-d3ab-4277-8f89-c4bfbd17d96d@blastwave.org> Date: Sat, 1 Feb 2025 00:28:43 +0100 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <49C9D807-3449-4806-BD91-9D8F27A7A34B@FreeBSD.org> References: <94cb266f-d3ab-4277-8f89-c4bfbd17d96d@blastwave.org> To: Dennis Clarke X-Mailer: Apple Mail (2.3731.700.6.1.9) On 31 Jan 2025, at 22:16, Dennis Clarke wrote: >=20 > Not sure if I heard rumours correctly but perhaps someone can chime > in on this. Was there a problem wherein the SiFive RISC-V board would > panic with the latest kernel updates? Here I mean the "Unmatched". A similar panic for i386 was fixed by: = https://cgit.freebsd.org/src/commit/?id=3D4015ff43cbbe819316104258da6a79be= f76e52c2 so you should try to update to something after that. -Dimitry From nobody Sat Feb 1 08:57:15 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 4YlRVN6bbLz5mZbh for ; Sat, 01 Feb 2025 08:57:48 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YlRVM3H4cz3xrR; Sat, 01 Feb 2025 08:57:47 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=F6kWw7TW; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.60 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub1.goneo.de (hub1.goneo.de [IPv6:2001:1640:5::8:52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id AEEFF240E50; Sat, 1 Feb 2025 09:57:45 +0100 (CET) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id D1B2B2407EE; Sat, 1 Feb 2025 09:57:43 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1738400263; 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:references:references; bh=pjacg2clhcOtY3EtODr2rce+drQ/3YsZAGIFdl3szew=; b=F6kWw7TWWrmRZaeFHQuRh+frWov6HDUCGRQJr4GTi0I/PuZXIRyMpt/gNMR2D2eJWuIGxz iA1JJlbL181Iw4N4+As/6SrKFTS692R6gNT/T3vUTaZbQri6v7tT8KdswHCx7yOjwi3zPl kkLO/n1Xtk30q+9qXMmABfcBd84jGXk89dRoo+fzCK7mZb4ACucxvnfJGjXKuC4pYXYkXb uOASCzmQ3ZpR89d/nvhqq5cL6DI86ih+CrtMyaumLD0fgd1P0CJCNM6gYWDhUmpetTe12t lycK0cqc/krNMG20HXUZIqtcZ00KaFdZ+CLBle613kJr9oEEN8aNOUmknSwC+A== Received: from thor.sb211.local (dynamic-2a02-3100-1886-af02-e4c1-c283-6426-266f.310.pool.telefonica.de [IPv6:2a02:3100:1886:af02:e4c1:c283:6426:266f]) (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) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 7EBF4240638; Sat, 1 Feb 2025 09:57:43 +0100 (CET) Date: Sat, 1 Feb 2025 09:57:15 +0100 From: A FreeBSD User To: Allan Jude Cc: freebsd-current@freebsd.org Subject: Re: ZFS: Rescue FAULTED Pool Message-ID: <20250201095656.1bdfbe5f@thor.sb211.local> In-Reply-To: <980401eb-f8f6-44c7-8ee1-5ff0c9e1c35c@freebsd.org> References: <20250129112701.0c4a3236@freyja> <20250130123354.2d767c7c@thor.sb211.local> <980401eb-f8f6-44c7-8ee1-5ff0c9e1c35c@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: multipart/signed; boundary="Sig_/pfQSL+v5QfLrNu5ora.cKlu"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: 22558d X-Rspamd-UID: 476cf5 X-Spamd-Result: default: False [-6.70 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RBL_SENDERSCORE_REPUT_9(-1.00)[85.220.129.60:from]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.60:from]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_SOME(0.00)[]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Spamd-Bar: ------ X-Rspamd-Queue-Id: 4YlRVM3H4cz3xrR --Sig_/pfQSL+v5QfLrNu5ora.cKlu Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 30 Jan 2025 16:13:56 -0500 Allan Jude schrieb: > On 1/30/2025 6:35 AM, A FreeBSD User wrote: > > Am Wed, 29 Jan 2025 03:45:25 -0800 > > David Wolfskill schrieb: > >=20 > > Hello, thanks for responding. > > =20 > >> On Wed, Jan 29, 2025 at 11:27:01AM +0100, FreeBSD User wrote: =20 > >>> Hello, > >>> > >>> a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable > >>> anymore. neither with import -F/-f. > >>> Although this pool is on an experimental system (no backup available) > >>> it contains some data to reconstruct them would take a while, so I'd > >>> like to ask whether there is a way to try to "de-fault" such a pool. = =20 > >> > >> Well, 'zpool clear ...' "Clears device errors in a pool." (from "man > >> zpool". > >> > >> It is, however, not magic -- it doesn't actually fix anything. =20 > >=20 > > For the record: I tried EVERY network/search available method useful f= or common > > "administrators", but hoped people are abe to manipulate deeper stuff v= ia zdb ... > > =20 > >> > >> (I had an issue with a zpool which had a single SSD device as a ZIL; t= he > >> ZIL device failed after it had accepted some data to be written to the > >> pool, but before the data could be read and transferred to the spinning > >> disks. ZFS was quite unhappy about that. I was eventually able to co= py > >> the data elsewhere, destroy the old zpool, recreate it *without* that > >> single point of failure, then copy the data back. And I learned to > >> never create a zpool with a *single* device as a separate ZIL.) =20 > >=20 > > Well, in this case I do not use dedicated ZIL drives. I also made sever= al experiences with > > "single" ZIL drive setups, but a dedicated ZIL is mostly useful in case= s were you have > > graveyard full of inertia-suffering, mass-spinning HDDs - if I'm right = the concept of SSD > > based ZIL would be of no use/effect in that case. So I ommited tose. > > =20 > >> =20 > >>> The pool is comprised from 7 drives as a RAIDZ1, one of the SSDs > >>> faulted but I pulled the wrong one, so the pool ran into suspended > >>> state. =20 > >> > >> Can you put the drive you pulled back in? =20 > >=20 > > Every single SSD originally plugged in is now back in place, even the f= aulted one (which > > doesn't report any faults at the moment). > >=20 > > Although the pool isn't "importable", zdb reports its existence, amongs= t zroot (which > > resides on a dedicated drive). > > =20 > >> =20 > >>> The host is running the lates Xigmanas BETA, which is effectively > >>> FreeBSD 14.1-p2, just for the record. > >>> > >>> I do not want to give up, since I hoped there might be a rude but > >>> effective way to restore the pool even under datalosses ... > >>> > >>> Thanks in advance, > >>> > >>> Oliver > >>> .... =20 > >> > >> Good luck! > >> > >> Peace, > >> david =20 > >=20 > >=20 > > Well, this is a hard and painful lecture to learn, if there is no chanc= e to get back the > > pool. > >=20 > > A warning (but this seems to be useless in the realm of professionals):= I used a bunch of > > cheap spotmarket SATA SSDs, a brand called "Intenso" common also here i= n Good old Germany. > > Some of those SSDs do have working LED when used with a Fujitsu SAS HBA= controller - but > > those died very quickly from suffering some bus errors. Another bunch o= f those SSDs do not > > have working LED (not blinking on access), but lasted a bit longer. The= problem with those > > SSDs is: I can not find the failing device easily by accessing the fail= ed drive by writing > > massive data via dd, if possible. > > I also ordered alternative SSDs from a more expensive brand - but bad K= arma ... > >=20 > > Oliver > >=20 > > =20 >=20 > The most useful thing to share right now would be the output of `zpool=20 > import` (with no pool name) on the rebooted system. >=20 > That will show where the issues are, and suggest how they might be solved. >=20 Hello, this exactly happens when trying to import the pool. Prior to the lo= ss, device da1p1 has been faulted with numbers in the colum/columns "corrupted data"/further= not seen now. ~# zpool import pool: BUNKER00 id: XXXXXXXXXXXXXXXXXXXX state: FAULTED status: The pool metadata is corrupted. action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the '-f' flag. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-72 config: BUNKER00 FAULTED corrupted data raidz1-0 ONLINE da2p1 ONLINE da3p1 ONLINE da4p1 ONLINE da7p1 ONLINE da6p1 ONLINE da1p1 ONLINE da5p1 ONLINE ~# zpool import -f BUNKER00 cannot import 'BUNKER00': I/O error Destroy and re-create the pool from a backup source. ~# zpool import -F BUNKER00 cannot import 'BUNKER00': one or more devices is currently unavailable --=20 A FreeBSD user --Sig_/pfQSL+v5QfLrNu5ora.cKlu Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCZ53iBgAKCRCxzvs8Oqok r6sjAP4/5+HPz0EImGkLPE9Z2D5y5YNwlAJIg9c/DZrUF4UJCAD/QXeV+iCOl8f/ /23e1CzJFzdY8+/ARqKmeno7BAa0/gU= =konu -----END PGP SIGNATURE----- --Sig_/pfQSL+v5QfLrNu5ora.cKlu-- From nobody Sat Feb 1 14:06:27 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 4YlZLy1fyRz5lWMY for ; Sat, 01 Feb 2025 14:06:50 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 4YlZLx1lb8z3Qnk; Sat, 01 Feb 2025 14:06:49 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=nkhJUILh; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2a00:1450:4864:20::536 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-5dc89df7eccso1876664a12.3; Sat, 01 Feb 2025 06:06:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738418806; x=1739023606; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=JvvK25xGUYfenib+IPtYf+bPz8ujKw0O/303hLYNSys=; b=nkhJUILhtvHI+x8Dl9FNkihQgFhARMOSvJTc7eTkPaly1s/RjHFqT0209yO1XFxx8/ Utw5hsAxq7L8eCrf3g3pm31B0FE4k5y5mM2HqoFYkdWJ/r3NKlVlAbMUwV/ZWR7exBPA 2T91OhLyiJNh3gJLShdPzfnTPIDCrjkbLx0VvAzwwLI1NG43ujuo3ekswaxeTLL4zSCZ /Z1ELnR6qzRrqStEa+yOuNAZhoDOL4cdrTPozF+LpWvyJX/tYy6kiXKDB6UJWOnLVXsi eNOjsOtprKf3rz93EbWXt7KfE4t4Q1X0qqvR1LppVVR6ZFmSmlhTBqBboV0ZjipFyuQ/ sdow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738418806; x=1739023606; h=content-transfer-encoding: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=JvvK25xGUYfenib+IPtYf+bPz8ujKw0O/303hLYNSys=; b=D3tTpGQl1lmruC32auCX+bnr5fqLPZaoEIEy+r0bKo3Y4IFCpxRytW50G/el1gP0Eu 1y/gQMSf48075N+AijIe8Lc+pMR4Smx8a01+iWE4a9QJFN2v47KusBZssw0NsiqSbLXy yuuHlVxhzvqLMjpfEQtDWjkCSupvZfnxT+C7xYHCZXyjFpMyMgwE5p0VlNjYmOR74c3d a5jpWRVVo3kGv+TC9RfUqW5SC/YtcJ83pKdfrQC90jW6EZaLm54MEKliffjIppl4R1I1 APEpgzla7eOVXLFmX7g3sCjEPit2wHJ1i6SKBeBuPLwJoWaQmgJ0zIu1RVUwem/kNQUK BMfA== X-Forwarded-Encrypted: i=1; AJvYcCU7HSkaOcwkK+ZT4UhheSNyStu3AIYZEdXm4dpmX70d6r2WEXCIKo3MObBrjInCiVF4nESuTQb6oQ==@freebsd.org X-Gm-Message-State: AOJu0YxThSxQON0dTc9TnIffXyq2vC98jnTtEyoQkuHTl3cohl/mNii4 +VatIgHCM0BHXCpYCpgdHvgag2fhtooEf4ItdSOT1XY0IS8rA1iABpBrxn+eLo8qJ6teAiQXSYt WM9s3W35v1V2Jv8CD6P30WYPuGUX9 X-Gm-Gg: ASbGncvnT+Zby7cNVdLIt7GN3cDG3XtkMsim+W6ig91WxJt3lL+FjVHsBmHZE9EJmv6 P6wRDs51CXzg5BVX619ujElSzTn6alsXEULerkEzSlz+8iJVjPHg7wjSzJkTiu+4eiE4nZ1Ra+J 8aXbeLSTjuZSGUn6fwyW8Fkgo4zmCf3Q== X-Google-Smtp-Source: AGHT+IFBTZEk3QlylQOptK4KoHxM0Kx1psZTGqY9z4lEh9HACAzzGY88+QfwnKUBxam9WQ+AD1XOUBnfPFlo2wp/N44= X-Received: by 2002:a05:6402:13cc:b0:5d0:abb8:79d with SMTP id 4fb4d7f45d1cf-5dc5efbd4b8mr16134565a12.14.1738418804961; Sat, 01 Feb 2025 06:06:44 -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: Rick Macklem Date: Sat, 1 Feb 2025 06:06:27 -0800 X-Gm-Features: AWEUYZle4W-NS1Ee2nz_dl1XTnv2OFdgj_DC_o9j0yD9NF75oxWyvsYDqaHWMow Message-ID: Subject: Re: HEADS UP: NFS changes coming into CURRENT early February To: Gleb Smirnoff Cc: current@freebsd.org, rmacklem@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_FROM(0.00)[gmail.com]; TAGGED_FROM(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::536:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4YlZLx1lb8z3Qnk On Tue, Jan 21, 2025 at 10:27=E2=80=AFPM Gleb Smirnoff wrote: > > CAUTION: This email originated from outside of the University of Guelph. = Do not click links or open attachments unless you recognize the sender and = know the content is safe. If in doubt, forward suspicious emails to IThelp@= uoguelph.ca. > > > Hi, > > TLDR version: > users of NFS with Kerberos (e.g. running gssd(8)) as well as users of NFS= with > TLS (e.g. running rpc.tlsclntd(8) or rpc.tlsservd(8)) as well as users of > network lock manager (e.g. having 'options NFSLOCKD' and running rpcbind(= 8)) > are affected. You would need to recompile & reinstall both the world and= the > kernel together. Of course this is what you'd normally do when you track > FreeBSD CURRENT, but better be warned. I will post hashes of the specifi= c > revisions that break API/ABI when they are pushed. > > Longer version: > last year I tried to check-in a new implementation of unix(4) SOCK_STREAM= and > SOCK_SEQPACKET in d80a97def9a1, but was forced to back it out due to seve= ral > kernel side abusers of a unix(4) socket. The most difficult ones are the= NFS > related RPC services, that act as RPC clients talking to an RPC servers i= n > userland. Since it is impossible to fully emulate a userland process > connection to a unix(4) socket they need to work with the socket internal > structures bypassing all the normal KPIs and conventions. Of course they > didn't tolerate the new implementation that totally eliminated intermedia= te > buffer on the sending side. > > While the original motivation for the upcoming changes is the fact that I= want > to go forward with the new unix/stream and unix/seqpacket, I also tried t= o make > kernel to userland RPC better. You judge if I succeeded or not :) Here a= re > some highlights: > > - Code footprint both in kernel clients and in userland daemons is reduce= d. > Example: gssd: 1 file changed, 5 insertions(+), 64 deletions(-) > kgssapi: 1 file changed, 26 insertions(+), 78 deletions(-) > 4 files changed, 1 insertion(+), 11 deletions(-) > - You can easily see all RPC calls from kernel to userland with genl(1): > # genl monitor rpcnl > - The new transport is multithreaded in kernel by default, so kernel clie= nts > can send a bunch of RPCs without any serialization and if the userland > figures out how to parallelize their execution, such parallelization wo= uld > happen. Note: new rpc.tlsservd(8) will use threads. > - One ad-hoc single program syscall is removed - gssd_syscall. Note: > rpctls syscall remains, but I have some ideas on how to improve that, t= oo. > Not at this step though. > - All sleeps of kernel RPC calls are now in single place, and they all ha= ve > timeouts. I believe NFS services are now much more resilient to hangs. > A deadlock when NFS kernel thread is blocked on unix socket buffer, and > the socket can't go away because its application is blocked in some oth= er > syscall is no longer possible. > > The code is posted on phabricator, reviews D48547 through D48552. > Reviewers are very welcome! > > I share my branch on Github. It is usually rebased on today's CURRENT: > > https://github.com/glebius/FreeBSD/commits/gss-netlink/ > > Early testers are very welcome! Good work getting all this committed! You might want to put an entry in UPDATING noting that the daemons need to be upgraded with the kernel. Thanks for all your work on this, rick > > -- > Gleb Smirnoff > From nobody Sat Feb 1 14:10:25 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 4YlZRL1y3Qz5lWKp for ; Sat, 01 Feb 2025 14:10:38 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (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 "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YlZRK1x0fz3S6d for ; Sat, 01 Feb 2025 14:10:37 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=VbLNpfFL; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org; dmarc=pass (policy=quarantine) header.from=blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 511EAQlK018312 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Sat, 1 Feb 2025 09:10:27 -0500 (EST) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1738419027; bh=hEM17bQ3Y+WuiewKvkpw2WbA0a+c8kZrKEMkwAJ4wbo=; h=Date:Subject:To:References:From:In-Reply-To; b=VbLNpfFL+qgroVqEyrLfuzz0HaMx+isIpvxsv2R/E3nnoHig37rvl0ar4DEIb4JQN o7S27Ror0VjCkV9ljs9tMBT6ZVQfqLyDMfR7iu75MSNc+Q8eCAk+J/EtF0df8hgKVA 3eQ63ThmbgplEtKXcF10XwtgqHnEulc16yyjOll5GYTQP16VsWMqxSEzblw05yBjZL M+nsz+1q1HXTwYkjY14Iz66PAHSQFj0QW+Fal44ssRSr6uXGsI6NA5UBh0SZMJHSfA LusjuB/NGbrPF2HCBldJdthis1sc64hKksOXJfXeX3yQuqp+hdMqXwgTPSG5NW1lrO c+lqxd7iHSCXg== Message-ID: <62da6831-fbc8-4bab-9a4c-6b0ec9dd3585@blastwave.org> Date: Sat, 1 Feb 2025 09:10:25 -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: Mozilla Thunderbird Subject: Re: ZFS: Rescue FAULTED Pool Content-Language: en-CA To: freebsd-current@freebsd.org References: <20250129112701.0c4a3236@freyja> <20250130123354.2d767c7c@thor.sb211.local> <980401eb-f8f6-44c7-8ee1-5ff0c9e1c35c@freebsd.org> <20250201095656.1bdfbe5f@thor.sb211.local> From: Dennis Clarke Organization: GENUNIX In-Reply-To: <20250201095656.1bdfbe5f@thor.sb211.local> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 511EAQlK018312 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Result: default: False [-4.70 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4YlZRK1x0fz3S6d >> >> The most useful thing to share right now would be the output of `zpool >> import` (with no pool name) on the rebooted system. >> >> That will show where the issues are, and suggest how they might be solved. >> > > Hello, this exactly happens when trying to import the pool. Prior to the loss, device da1p1 > has been faulted with numbers in the colum/columns "corrupted data"/further not seen now. > > > ~# zpool import > pool: BUNKER00 > id: XXXXXXXXXXXXXXXXXXXX > state: FAULTED > status: The pool metadata is corrupted. > action: The pool cannot be imported due to damaged devices or data. > The pool may be active on another system, but can be imported using > the '-f' flag. > see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-72 > config: > > BUNKER00 FAULTED corrupted data > raidz1-0 ONLINE > da2p1 ONLINE > da3p1 ONLINE > da4p1 ONLINE > da7p1 ONLINE > da6p1 ONLINE > da1p1 ONLINE > da5p1 ONLINE > > > ~# zpool import -f BUNKER00 > cannot import 'BUNKER00': I/O error > Destroy and re-create the pool from > a backup source. > > > ~# zpool import -F BUNKER00 > cannot import 'BUNKER00': one or more devices is currently unavailable > This is indeed a sad situation. You have a raidz1 pool with one or MORE devices that seem to have left the stage. I suspect more than one. I can only guess what you see from "camcontrol devlist" as well as data from "gpart show -l" where we would see the partition data along with and GPT labels. If in fact you used GPT scheme. You have a list of devices that all say "p1" there and so I guess you made some sort of a partition table. ZFS does not need that but it can be nice to have. In any case, it really does look like you have _more_ than one failure in there somewhere and only dmesg and some separate tests on each device would reveal the truth. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken From nobody Sat Feb 1 17:26:28 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 4YlfnM6QmZz5mDgy for ; Sat, 01 Feb 2025 17:26:31 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YlfnM5sQ3z3q8V; Sat, 01 Feb 2025 17:26:31 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738430791; 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:references:references; bh=ulblCUpFXR+5zdND60QcycfUBYx7HX1rhA09eodDaWI=; b=OdsHe/AOkDJOOZFEDNGj6jF6XphlcNVY83eSX0DbAyQe425q+MOhu8XhB94wRwetWu4jA2 nyJMupk39Jlflte52iC6abGA57s36dHIaFLl1YWl+g2EJkSQ1U2cP8VX58VCIpqMe7vNCK rdigIJOMTbb7mctWGhyyMpzdQxKtKr0wiKVr8RU34VV3VDoUzRnzm+GqxwyCUJvgZ9kkS/ 3GQDo4YOEFlzPkGF6YzX+QPOFDDqKa4Wo1fkLIwpaBUJYIXosJZeGw46ER7T+MKT2zMALB nqfiXVKWnZs6eHr20Qw0q9TEDTvlXrLu/Av31xGbyanTsbIvaYHhpvt+PI30NA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738430791; 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:references:references; bh=ulblCUpFXR+5zdND60QcycfUBYx7HX1rhA09eodDaWI=; b=iQYVv1adlT4OU/y2gRMfuAEIQ26a30+eFVb55UfjXLbKpFLOOGyHpK3SlvbdW5L198ZlI9 /J6VccQbiIfs4wbJn9E+Uz4meNX5CkF1N+OHyIDyD65q9Dn9pREJr7wn2liEqSli8L1Dkr Q00CvwP7qwUjspmcXxT8E8Z+Q9s6xkvwqGLja/JiKTHdyw7x/WVVnRZqh22zrnCmbDXdju L187nyT3B2Sotkgj8sY3ah+d2q0ihEVj11JOTboRMyTEWfCae5EbcYDzKRwbNFnMt9/Bns CIbckmlIkhsYqsZ5+Tr7KZIbSqeLcqLTIHUNb/zrl2J6fljg6Xst093QlYg+Hg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738430791; a=rsa-sha256; cv=none; b=Q3niU7C9d6J3XBDuZ/h1Dx1RDkTXHMoNqpOMMEOs1bni4H1PQNmjD1Vm4Q+ffe75MPRxRT T29KfZwfHSCYuIUzkh1XTuQQ/2UvCaQHYXbIvqc2zriLXCPRRDUb/0E8CHSXaAIEJInIPF IX7unL1Ib56gRewRpKJlNH6dQWAzkiS0zuD2f3XoIJqaiTZSwMlgaUm+zX9iwHz8AASzIl 7h6BmHe/XNDNsNEmMant2JvBtXPRyn/NMjCtcr5q92T0MCzs/1CaeP9c+U8tanIkAxZ42m wEWULfIuj2q/OMnYetieVnuqFT69qkm8zCSekasz3sRBAHrHHj4X2kTvoQUSUA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YlfnM1f0GzCM; Sat, 01 Feb 2025 17:26:31 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Sat, 1 Feb 2025 09:26:28 -0800 From: Gleb Smirnoff To: Rick Macklem Cc: current@freebsd.org, rmacklem@freebsd.org Subject: Re: HEADS UP: NFS changes coming into CURRENT early February 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: On Sat, Feb 01, 2025 at 06:06:27AM -0800, Rick Macklem wrote: R> You might want to put an entry in UPDATING noting that the daemons R> need to be upgraded with the kernel. Of course I did :) Short update on the resource leaks. The patch that reduces refcount on the back channel proved to be incorrect, so disregard it. I think we should focus on the dead connection leak, where NFS RPC layer doesn't process garbage collecting of a TCP connection unless it actually needs to make a write on it, described here: https://lists.freebsd.org/archives/freebsd-current/2025-January/007005.html -- Gleb Smirnoff From nobody Sat Feb 1 23:15:52 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 4YlpXZ2l2Jz5mJY2 for ; Sat, 01 Feb 2025 23:15:58 +0000 (UTC) (envelope-from sgharms@stevengharms.com) Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "protonmail.com", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YlpXY4WHNz41W3 for ; Sat, 01 Feb 2025 23:15:57 +0000 (UTC) (envelope-from sgharms@stevengharms.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=stevengharms.com header.s=protonmail header.b=iWHI+OKv; spf=pass (mx1.freebsd.org: domain of sgharms@stevengharms.com designates 185.70.43.17 as permitted sender) smtp.mailfrom=sgharms@stevengharms.com; dmarc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stevengharms.com; s=protonmail; t=1738451756; x=1738710956; bh=zp8ne9531hP9eWcvOdxoz3B6D3qtwfkU9eN59G9ju54=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector: List-Unsubscribe:List-Unsubscribe-Post; b=iWHI+OKv8SLsXfSoUEA88TV903u6BiZ8BavD/eLzVR2qzkq95hFtUL83xCAfrm3Bq dwuqAIPzzf9ZKPUvN/xUM8ISr1SfbyOF2bC8IIYDMkks4TuL67pDXXxxbNuCZykswy Um0C4a9PDXfZZNQrDHHN/6JoFkL5mFa51VjgSlRA= Date: Sat, 01 Feb 2025 23:15:52 +0000 To: "freebsd-current@freebsd.org" From: "Steven Harms (High-Security Mail)" Subject: Adjustments to userland for a quieter startup (RC system) Message-ID: Feedback-ID: 16996530:user:proton X-Pm-Message-ID: 674802ad5ff5931d47348087d3e7869afd92e1d5 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/alternative; boundary="b1=_bsq7yX6329tBtWOQmqnyw2HCV7fRt94kPLF83AsV4" X-Spamd-Result: default: False [-3.47 / 15.00]; RBL_SENDERSCORE_REPUT_9(-1.00)[185.70.43.17:from]; MIME_BASE64_TEXT_BOGUS(1.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.99)[-0.987]; NEURAL_HAM_MEDIUM(-0.99)[-0.987]; R_DKIM_ALLOW(-0.20)[stevengharms.com:s=protonmail]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24:c]; MIME_BASE64_TEXT(0.10)[]; RWL_MAILSPIKE_GOOD(-0.10)[185.70.43.17:from]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; DMARC_NA(0.00)[stevengharms.com]; RCVD_IN_DNSWL_NONE(0.00)[185.70.43.17:from]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_DN_EQ_ADDR_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[stevengharms.com:+] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4YlpXY4WHNz41W3 --b1=_bsq7yX6329tBtWOQmqnyw2HCV7fRt94kPLF83AsV4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 R3JlZXRpbmdzLAoKSSBoYXZlIGNyZWF0ZWQgaHR0cHM6Ly9naXRodWIuY29tL2ZyZWVic2QvZnJl ZWJzZC1zcmMvcHVsbC8xNTgyIGluIGFuIGVmZm9ydCB0byBxdWlldCBkb3duIHNvbWUgb2YgdGhl IGNoYXR0aW5lc3Mgb2YgbW9kdWxlIGxpbmtpbmcgYW5kIG5ldHdvcmsgZGlhZ25vc3RpY3Mgb24g c3RhcnR1cC4gSSdtIHVzZWQgdG8gd29ya2luZyBpbiBhIGdpdC1iYXNlZCB3b3JrZmxvdyBhbmQg c2F3IG5vIGFjdGlvbiBvbiB0aGUgUFIsIHNvIEkgdGhvdWdodCBJIHdvdWxkIG5vdGlmeSBoZXJl LiBJZiB0aGF0J3Mgbm90IHRoZSBjb3JyZWN0IHByb2NlZHVyZSwgcGxlYXNlIGFkdmlzZS4KClRo YW5rcyBmb3IgYWxsIHRoZSB3b3JrIGV2ZXJ5b25lIG9uIHRoZSBsaXN0IGRvZXMhCgpTdGV2ZW4K Ci0tLQoKUHVibGljIEtleTogMjJCRTM5RTJGQTY4RDhCQThEQzRCNDNBNTVBMTZEOENFMkIwMzZE RQoKTWVzc2FnZXMgZnJvbSB0aGlzIGFjY291bnQgYXJlIGNvbnNpZGVyZWQgdGhlIGJlc3Qtc2Vj dXJlZCBhbmQgbW9zdCByZWxpYWJsZS4gU2VuZCBpbmZvcm1hdGlvbiByZWdhcmRpbmcgaGVhbHRo LCB3ZWFsdGgsIG9yIHJlcXVpcmluZyBoaWdoZXIgc3RhbmRhcmRzIG9mIHNlY3VyaXR5IHRvIHRo aXMgYWRkcmVzcy4KClNlbnQgd2l0aCBbUHJvdG9uIE1haWxdKGh0dHBzOi8vcHJvdG9uLm1lL21h aWwvaG9tZSkgc2VjdXJlIGVtYWlsLg== --b1=_bsq7yX6329tBtWOQmqnyw2HCV7fRt94kPLF83AsV4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0 cHg7Ij48ZGl2PkdyZWV0aW5ncyw8YnI+PGJyPkkgaGF2ZSBjcmVhdGVkIDxzcGFuPjxhIGhyZWY9 Imh0dHBzOi8vZ2l0aHViLmNvbS9mcmVlYnNkL2ZyZWVic2Qtc3JjL3B1bGwvMTU4MiIgcmVsPSJu b3JlZmVycmVyIG5vZm9sbG93IG5vb3BlbmVyIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9naXRo dWIuY29tL2ZyZWVic2QvZnJlZWJzZC1zcmMvcHVsbC8xNTgyPC9hPjwvc3Bhbj4NCiBpbiBhbiBl ZmZvcnQgdG8gcXVpZXQgZG93biBzb21lIG9mIHRoZSBjaGF0dGluZXNzIG9mIG1vZHVsZSBsaW5r aW5nIGFuZA0KIG5ldHdvcmsgZGlhZ25vc3RpY3Mgb24gc3RhcnR1cC4gSSdtIHVzZWQgdG8gd29y a2luZyBpbiBhIGdpdC1iYXNlZCANCndvcmtmbG93IGFuZCBzYXcgbm8gYWN0aW9uIG9uIHRoZSBQ Uiwgc28gSSB0aG91Z2h0IEkgd291bGQgbm90aWZ5IGhlcmUuIA0KSWYgdGhhdCdzIG5vdCB0aGUg Y29ycmVjdCBwcm9jZWR1cmUsIHBsZWFzZSBhZHZpc2UuPGJyPjxicj5UaGFua3MgZm9yIGFsbCB0 aGUgd29yayBldmVyeW9uZSBvbiB0aGUgbGlzdCBkb2VzITxicj48YnI+U3RldmVuPGJyPjwvZGl2 PjxzcGFuPjwvc3Bhbj48YnI+PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBz YW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij48YnI+PC9kaXY+DQo8ZGl2IGNsYXNzPSJwcm90 b25tYWlsX3NpZ25hdHVyZV9ibG9jayIgc3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCwgc2Fucy1z ZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQogICAgPGRpdiBjbGFzcz0icHJvdG9ubWFpbF9zaWdu YXR1cmVfYmxvY2stdXNlciI+DQogICAgICAgIDxkaXY+LS0tPGJyPjwvZGl2PjxkaXY+PGJyPjwv ZGl2PjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCwgc2Fucy1zZXJpZjsgZm9udC1zaXpl OiAxNHB4OyBjb2xvcjogcmdiKDAsIDAsIDApOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAy NTUsIDI1NSk7Ij5QdWJsaWMgS2V5OiA8YSB0aXRsZT0iMjJCRTM5RTJGQTY4RDhCQThEQzRCNDNB NTVBMTZEOENFMkIwMzZERSIgaHJlZj0iaHR0cHM6Ly8yMkJFMzlFMkZBNjhEOEJBOERDNEI0M0E1 NUExNkQ4Q0UyQjAzNkRFIj48c3Bhbj4yMkJFMzlFMkZBNjhEOEJBOERDNEI0M0E1NUExNkQ4Q0Uy QjAzNkRFPC9zcGFuPjwvYT48YnI+PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zdHlsZTogbm9ybWFs OyBmb250LXdlaWdodDogbm9ybWFsOyBsZXR0ZXItc3BhY2luZzogbm9ybWFsOyB0ZXh0LWluZGVu dDogMHB4OyB0ZXh0LXRyYW5zZm9ybTogbm9uZTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgd29yZC1z cGFjaW5nOiAwcHg7IHRleHQtZGVjb3JhdGlvbjogbm9uZTsgZm9udC1mYW1pbHk6IEFyaWFsLCBI ZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzQsIDM0LCAzNCk7Ij48YnI+PC9kaXY+ PGRpdj5NZXNzYWdlcyBmcm9tIHRoaXMgYWNjb3VudCBhcmUgY29uc2lkZXJlZCB0aGUgYmVzdC1z ZWN1cmVkIGFuZCBtb3N0IHJlbGlhYmxlLiBTZW5kIGluZm9ybWF0aW9uIHJlZ2FyZGluZyBoZWFs dGgsIHdlYWx0aCwgb3IgcmVxdWlyaW5nIGhpZ2hlciBzdGFuZGFyZHMgb2Ygc2VjdXJpdHkgdG8g dGhpcyBhZGRyZXNzLjxicj48L2Rpdj4NCiAgICA8L2Rpdj4NCiAgICA8ZGl2IHN0eWxlPSJmb250 LWZhbWlseTogQXJpYWwsIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPjxicj48L2Rpdj4N CiAgICA8ZGl2IGNsYXNzPSJwcm90b25tYWlsX3NpZ25hdHVyZV9ibG9jay1wcm90b24iPg0KICAg ICAgICBTZW50IHdpdGggPGEgdGFyZ2V0PSJfYmxhbmsiIGhyZWY9Imh0dHBzOi8vcHJvdG9uLm1l L21haWwvaG9tZSI+UHJvdG9uIE1haWw8L2E+IHNlY3VyZSBlbWFpbC4NCiAgICA8L2Rpdj4NCjwv ZGl2Pg0K --b1=_bsq7yX6329tBtWOQmqnyw2HCV7fRt94kPLF83AsV4-- From nobody Sun Feb 2 00:18:07 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 4Ylqwb5glQz5mRfk for ; Sun, 02 Feb 2025 00:18:23 +0000 (UTC) (envelope-from tomek@cedro.info) 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 4Ylqwb3vnWz3GrX for ; Sun, 02 Feb 2025 00:18:23 +0000 (UTC) (envelope-from tomek@cedro.info) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-6f14626c5d3so17210007b3.3 for ; Sat, 01 Feb 2025 16:18:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cedro.info; s=google; t=1738455502; x=1739060302; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5oqN7qmIAAIoCL6eWbLMwTznuvZU72sWfzGl5z359O8=; b=XEQZOrprAOa+7rPM18DBJJglkGnTNqmY9o6tpbO3SePeE4Mg9xMyaT9/DzF9fI5PfU 0e1y62aR4GqTedb00ezS4VHskwVmMzC7SVhdGhzDHKSyZ79LaznBB5ZKrKNphQzN4jEY TEk80iVSc4jbO92kKV1bmvYNUHdVkeSDAfA1bwwLJWjmW5FM9YhCHkseErlRUuyhpFbU qDYe2Y8b2o61WbuZt2qbeEYXuSpsnsF2bbtQ7lvwNnQP011LYSK0UUmSc+uTKEaXshnj HgGai2AMIuMNLjyxmLbg7v26THHerS5bQ3uPAFQXLPvXK7bQhL0EA2JiOnIhKGxJOVOz 2WjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738455502; x=1739060302; h=content-transfer-encoding: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=5oqN7qmIAAIoCL6eWbLMwTznuvZU72sWfzGl5z359O8=; b=ZS8yz/5Dfey267qfPHZnh0CSv1XJtk0bIiII0pXTdkakpkgdkRPH1lOXJFROk2ygeb yZulbTlRtjTZRicjapE5aFex0q0BbJ7TpDyTXRnmi0iZNrjcozLL3a96Lg1m/l0ycf0y 0LWmCn98nqPqj0tLDuul49MCYv7M/QzuN3MWqkv25nlC8PByTBmZLmJKuNi6M/FbsHdY wVOAoC6X8Za8hrelw1REIiHMLbrBERyUX9/+GRLtGbKNDKX5O2uJMPHUd7tftR5Ijpbn Ml5H7Insfda/FbIOZeuhF22ZjUYyKNH23MkG4iq1MSEGujoWP2SkLIYY3B3ZSGT9AYEK srZw== X-Gm-Message-State: AOJu0YxWLMNBcPAdA+Zi3DOc+2mIa3ZBT5C6lb/pACiEuUkf5ZCEG8G6 nUSA8cVxUxAN2ieUi4ziyoO6KKHevWdJuwJN9Hi5TlYQbyfntoRacYHx9yVUT6i9ty8uaY6pPZU = X-Gm-Gg: ASbGncv+zB20uF2wzVXCwV9I1mSdlVXW6izteDmErfZoMlIQkTVzZCkGMEhle6XACI/ PqcVPMTkOldzDCHBTgP4r/rKdSEFCz9okic3JlV57VV5b4dSSAYuQ/W9scmZ0ovoGXedK+GFkwl yhvLQ3uaM5jMUStJy2h7BW3EUu1zRaZ1edtVGxobMSkXyR4v3p+OCuqrCw6YL3wItjFMnHgsMdo 7Na44hc+yt+tBG/iV2suC5KOdGcbt2oUU8LyIf0BOlxQG3kD47NFmCBQUmCRv+9t5LjsTKIVwE3 PPHUsU8KXb9cEEq32zl7Mee1+zRi0sTtOqDFtWRZlydCP1jh6T+8 X-Google-Smtp-Source: AGHT+IFXXmIH9FjdLL4F7bvsc7FS7KiXOj52q7uZoyV5f40rNx6dwzP7kMSP7v49tI4Wr/Oon+aI+g== X-Received: by 2002:a05:690c:7109:b0:6f7:55a2:4cf5 with SMTP id 00721157ae682-6f7a8320bf4mr140661967b3.2.1738455501979; Sat, 01 Feb 2025 16:18:21 -0800 (PST) Received: from mail-yb1-f178.google.com (mail-yb1-f178.google.com. [209.85.219.178]) by smtp.gmail.com with ESMTPSA id 00721157ae682-6f8c465befdsm14607057b3.64.2025.02.01.16.18.20 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 01 Feb 2025 16:18:20 -0800 (PST) Received: by mail-yb1-f178.google.com with SMTP id 3f1490d57ef6-e46ac799015so3264865276.0 for ; Sat, 01 Feb 2025 16:18:20 -0800 (PST) X-Received: by 2002:a05:6902:e02:b0:e57:37d5:e275 with SMTP id 3f1490d57ef6-e58a4ac575dmr13099596276.18.1738455500324; Sat, 01 Feb 2025 16:18: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: Tomek CEDRO Date: Sun, 2 Feb 2025 01:18:07 +0100 X-Gmail-Original-Message-ID: X-Gm-Features: AWEUYZl7gZI2NW8RYbdBvvfPrkhMSucE0hyDzMMzHfnS184e9HwDC9o9gY6kzIc Message-ID: Subject: Re: Adjustments to userland for a quieter startup (RC system) To: "Steven Harms (High-Security Mail)" Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Ylqwb3vnWz3GrX X-Spamd-Bar: ---- 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] On Sun, Feb 2, 2025 at 12:16=E2=80=AFAM Steven Harms (High-Security Mail) wrote: > Greetings, > I have created https://github.com/freebsd/freebsd-src/pull/1582 in an eff= ort to quiet down some of the chattiness of module linking and network diag= nostics on startup. I'm used to working in a git-based workflow and saw no = action on the PR, so I thought I would notify here. If that's not the corre= ct procedure, please advise. > Thanks for all the work everyone on the list does! > Steven Thanks @sgharms :-) I am against the change in current form because: * The concept may be useful for someone but it shall be a manually selectable option like `rc_mute` (in analog to `boot_mute`) and not a default. Maybe `rc_loglevel` that can get `silent, error, warning, info, verbose, debug` levels to rc scripts and services? Change does not provide a choice. * Boot log messages are extremely useful, they contain important diagnostic messages, these need to be logged even if silenced, these cannot be just sent to `/dev/null`. Change alters (breaks) logging. * Why not just put a boot logo image if you really do not want to see the boot messages? It will provide better user experience as expected but will not break the diagnostic information that are usually useful. My 2 cents :-) --=20 CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From nobody Sun Feb 2 01:42: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 4YlspH5VCqz5md5M for ; Sun, 02 Feb 2025 01:43:03 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (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 "ultimatedns.net", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YlspH2tJkz3ZR9 for ; Sun, 02 Feb 2025 01:43:03 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Authentication-Results: mx1.freebsd.org; none Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 5121gnoH048830; Sat, 1 Feb 2025 17:42:55 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ultimatedns.net; s=mx99; t=1738460575; x=1738461175; r=y; bh=JqUTeV6fcHhUd+WYtpllJ8Foulvhh3xMJL9x2F5xQ8g=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=AZQp3sr8N+yu+ZOuLOtQGuVY3XlQ17EafHqRrH2FReAz8QOObIhVj2CyReUkI6WKu tiBkb5JelvXP0zfN2ou00uaTWK/qRt5LOuCKfLFjSwONs5pmAg9wvk9M1FyWk7DHQD nJhripBw9y/lSjGpCf5KK4zFJ1NeY9iG8Gt6Vf0TdSzJKV4f40XDr2y3RDGST7yE4f QC3Zmo81X9D1vj2dfRdRyB3iCRDioOECzaMuclLMWgdofQQd29HCCGtN/z9DkA6OL2 2x+dZsqsX6esL49H3OIByUZvKQTo01XvvfTbrez2VUpFPjsqNmZ73aB1sUQWEdml5V 5jwCzPcyZqt2Q== 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: Sat, 01 Feb 2025 17:42:48 -0800 From: Chris To: Tomek CEDRO Cc: "Steven Harms (High-Security Mail)" , freebsd-current@freebsd.org Subject: Re: Adjustments to userland for a quieter startup (RC system) In-Reply-To: References: User-Agent: UDNSMS/17.0 Message-ID: X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4YlspH2tJkz3ZR9 X-Spamd-Bar: ---- 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:11404, ipnet:24.113.0.0/16, country:US] On 2025-02-01 16:18, Tomek CEDRO wrote: > On Sun, Feb 2, 2025 at 12:16 AM Steven Harms (High-Security Mail) > wrote: >> Greetings, >> I have created https://github.com/freebsd/freebsd-src/pull/1582 in an >> effort to quiet down some of the chattiness of module linking and network >> diagnostics on startup. I'm used to working in a git-based workflow and saw >> no action on the PR, so I thought I would notify here. If that's not the >> correct procedure, please advise. >> Thanks for all the work everyone on the list does! >> Steven > > Thanks @sgharms :-) I am against the change in current form because: > * The concept may be useful for someone but it shall be a manually > selectable option like `rc_mute` (in analog to `boot_mute`) and not a > default. Maybe `rc_loglevel` that can get `silent, error, warning, > info, verbose, debug` levels to rc scripts and services? Change does > not provide a choice. > * Boot log messages are extremely useful, they contain important > diagnostic messages, these need to be logged even if silenced, these > cannot be just sent to `/dev/null`. Change alters (breaks) logging. > * Why not just put a boot logo image if you really do not want to see > the boot messages? It will provide better user experience as expected > but will not break the diagnostic information that are usually useful. > > My 2 cents :-) I'm in complete agreement with Tomek. This (proposed) change has security implications. One gets used to the messages that scroll by. Which makes it easier to notice different ones, which might implicate security related problems. "Ignorance is bliss". But has its cost. While I can see a possible interest by some for this change. I think 1) it should never be default, 2) the boot logo option already exists, and easily addresses the "noisiness" complaint some may have. Thanks for your interest. -- sent from a device written from and running on FreeBSD From nobody Sun Feb 2 03:20:26 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 4YlvzF4VLhz5mqJ6 for ; Sun, 02 Feb 2025 03:20:57 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YlvzD6f4pz3w5F for ; Sun, 02 Feb 2025 03:20:56 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (124-18-43-234.area1a.commufa.jp [124.18.43.234]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 5123KQdW084586; Sun, 2 Feb 2025 12:20:28 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1738466429; bh=y3PxRXgNP7HwAwOVTmNx5r1BUD8HaS6LmPQhfjd/b0s=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=lxjjyUEqJIVR7OFbn/XcXyBSB570fSas8Ft1wGXQvANYbqTaeksxToBXL7sPWIruf 62F0jkHE3Xo4wd1vgNb4hzF40qRzZx+fXAWalFsjq5/JQEEb/xFkY4Id3pZj2jdgXa b0NQWqlC3I7GBy/PjJB6d4JSr1fRGA25oj5TpPPA= Date: Sun, 2 Feb 2025 12:20:26 +0900 From: Tomoaki AOKI To: Chris Cc: Tomek CEDRO , "Steven Harms (High-Security Mail)" , freebsd-current@freebsd.org Subject: Re: Adjustments to userland for a quieter startup (RC system) Message-Id: <20250202122026.4156f4775c54efa17fcae949@dec.sakura.ne.jp> In-Reply-To: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.2) 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: 8bit X-Rspamd-Queue-Id: 4YlvzD6f4pz3w5F X-Spamd-Bar: ---- 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:7684, ipnet:153.125.128.0/18, country:JP] On Sat, 01 Feb 2025 17:42:48 -0800 Chris wrote: > On 2025-02-01 16:18, Tomek CEDRO wrote: > > On Sun, Feb 2, 2025 at 12:16 AM Steven Harms (High-Security Mail) > > wrote: > >> Greetings, > >> I have created https://github.com/freebsd/freebsd-src/pull/1582 in an > >> effort to quiet down some of the chattiness of module linking and network > >> diagnostics on startup. I'm used to working in a git-based workflow and saw > >> no action on the PR, so I thought I would notify here. If that's not the > >> correct procedure, please advise. > >> Thanks for all the work everyone on the list does! > >> Steven > > > > Thanks @sgharms :-) I am against the change in current form because: > > * The concept may be useful for someone but it shall be a manually > > selectable option like `rc_mute` (in analog to `boot_mute`) and not a > > default. Maybe `rc_loglevel` that can get `silent, error, warning, > > info, verbose, debug` levels to rc scripts and services? Change does > > not provide a choice. > > * Boot log messages are extremely useful, they contain important > > diagnostic messages, these need to be logged even if silenced, these > > cannot be just sent to `/dev/null`. Change alters (breaks) logging. > > * Why not just put a boot logo image if you really do not want to see > > the boot messages? It will provide better user experience as expected > > but will not break the diagnostic information that are usually useful. > > > > My 2 cents :-) > I'm in complete agreement with Tomek. This (proposed) change has security > implications. One gets used to the messages that scroll by. Which makes it > easier to notice different ones, which might implicate security related > problems. "Ignorance is bliss". But has its cost. While I can see a possible > interest by some for this change. I think 1) it should never be default, > 2) the boot logo option already exists, and easily addresses the "noisiness" > complaint some may have. > > Thanks for your interest. > > -- > sent from a device written from and running on FreeBSD +1. Some (especially IoTs / set top boxes) would want no messages unless unrecoverable error happenes, but OTOH, some (mainly developers and some admins) would be feeling even current verbose logging is insufficient. (Possibly want all dtrace probes to be printed in some cases?) So adding new log levels (including no massages) would be nice, but forcing no messages is not a good way to go. -- Tomoaki AOKI From nobody Sun Feb 2 04:45:55 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 4Ylxsf02Z1z5n12p for ; Sun, 02 Feb 2025 04:46:14 +0000 (UTC) (envelope-from tomek@cedro.info) Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 4Ylxsc4gG6z3Jwq for ; Sun, 02 Feb 2025 04:46:12 +0000 (UTC) (envelope-from tomek@cedro.info) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cedro.info header.s=google header.b=h0o4D3qj; spf=none (mx1.freebsd.org: domain of tomek@cedro.info has no SPF policy when checking 2607:f8b0:4864:20::b2d) smtp.mailfrom=tomek@cedro.info; dmarc=none Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-e46c6547266so3116409276.3 for ; Sat, 01 Feb 2025 20:46:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cedro.info; s=google; t=1738471571; x=1739076371; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ew4R/cry5rK6+NjOXmOXGCnKwL4CqYc7qBGkoghDEB0=; b=h0o4D3qjwYUGo46fvWm02bJ3ZuXL09QOa6HpAbaZftSAbWYNmAI8j9hZTekvLDtMHt UNUxRjDIbAcvRZIDEja5vkCMNHBPsHIKOxz6aWV516QHNGKhnwmV6DjxCbUxYFkHAemb rYfmMu+hTVM20MjJ3yM3KSUmqZbtji+fM4zcwM/tI/PjfoI0ks9iMvBh+UEj1Cwaf4xH HwQ6QPfBLOiLKLOZX6tu/7ZQ6YhGHyUG2lAZqybEobEVP0xBTVTgw1GNMABN/OTkT5/g E4/xx9Wgl/Q7qZ4V9qHUXOF365X4N7K9vtnoCNX4EgEXRAWT2ahy2wYxJsLuyTeC/3+g ueUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738471571; x=1739076371; h=content-transfer-encoding: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=ew4R/cry5rK6+NjOXmOXGCnKwL4CqYc7qBGkoghDEB0=; b=eQfRU8tUuvUwV3jBFXouz5ZUf1Hi5WWERSPwob3rdYj+tLnVqNytNUNMiWrMlkPARx 1saElT2yCT6Y2zGCJsIVisWGBXB2etMXEVFQ07M75/efqVgSucMNA1JFl2Vhnt4Klwot Wq9nNZ1LRKbDIC64+LF7dCYxjtBAsl6I0fjCnt1zl+avTZiYr3tL3UDaTAf6zrN3PHEc lYstgveRGBaDvpTITsvY7x16yurMzp/cnXVb7D2p9GRfErKSQWLQkGkwng6LAu4s2Dp3 8U0CUWCV5wTBc+N6eDGxU15Cj2YTfdF6j9myWmgpfBzNbQqRYAowrGQrTdUAvnoh6s+S xK/g== X-Gm-Message-State: AOJu0Yzr6eENcP8sAiFhjj1Wc1di6flqmv8s1Ep5moNE05DdhELC8EIT 8Lxmky/ih1e4LCU76hl/fnabUFZ1nGMuf1vwr84LCck1N1KNtBwFMS8bZhWDea4ep9ks++i9bSI = X-Gm-Gg: ASbGncu46/nD/M7LyJ7Y9Z/wA/q/2zv4zGB9JKCqimHok5mdBERqMweB6ThvtsByZ7T ZSlWwCeu/6xfsXxmbrL6SFw20Py1WP3KVPMUFzDh+iORrpRUuzBFpCgibMsByZFklKrI/kIeJml Gqiy7N/118uPfPh9oWN+nkh3gcLfbunD0tR8JUAFO4bOIs2NTWBWkYW1VpW4g8gOfZfiYxgmI+b o1USQNL9WuP5CovO1qqMiDqoXoDbOCntX4KvO1X9gaEtTpAIF0cPYMupx+o1jFcIgNMm+Z02YSu QsmMP1qIurisLNwL743japytUG7m8v5l9+MXdTgEr45lg27F0iJ1 X-Google-Smtp-Source: AGHT+IEQ4Sco49Hv1evOojhS3jyoqpYun58GuU/kiuvpKv5bimBaT5sE8qhbqECGiBqEo4ZFU8bI/g== X-Received: by 2002:a05:6902:1025:b0:e58:a25d:5696 with SMTP id 3f1490d57ef6-e58a4c20389mr13028546276.45.1738471570994; Sat, 01 Feb 2025 20:46:10 -0800 (PST) Received: from mail-yb1-f179.google.com (mail-yb1-f179.google.com. [209.85.219.179]) by smtp.gmail.com with ESMTPSA id 3f1490d57ef6-e5acb3dbcb0sm1480645276.50.2025.02.01.20.46.08 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 01 Feb 2025 20:46:09 -0800 (PST) Received: by mail-yb1-f179.google.com with SMTP id 3f1490d57ef6-e587cca1e47so3677131276.0 for ; Sat, 01 Feb 2025 20:46:08 -0800 (PST) X-Received: by 2002:a05:6902:2401:b0:e4b:b2bd:5f94 with SMTP id 3f1490d57ef6-e58a4adcdfemr13163904276.13.1738471568577; Sat, 01 Feb 2025 20:46:08 -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: Tomek CEDRO Date: Sun, 2 Feb 2025 05:45:55 +0100 X-Gmail-Original-Message-ID: X-Gm-Features: AWEUYZkl4GjTJxhy7bf7W2jDkQe7CDJ_sR1IuE5ZXQgxjO1yfs9h4TIL8TsSxBk Message-ID: Subject: Re: Adjustments to userland for a quieter startup (RC system) To: "Steven Harms (High-Security Mail)" Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.29 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; R_DKIM_ALLOW(-0.20)[cedro.info:s=google]; MIME_GOOD(-0.10)[text/plain]; TO_DN_EQ_ADDR_SOME(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2d:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[cedro.info]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[cedro.info:+] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4Ylxsc4gG6z3Jwq On Sun, Feb 2, 2025 at 1:18=E2=80=AFAM Tomek CEDRO wrote= : > On Sun, Feb 2, 2025 at 12:16=E2=80=AFAM Steven Harms (High-Security Mail) > wrote: > > Greetings, > > I have created https://github.com/freebsd/freebsd-src/pull/1582 in an e= ffort to quiet down some of the chattiness of module linking and network di= agnostics on startup. I'm used to working in a git-based workflow and saw n= o action on the PR, so I thought I would notify here. If that's not the cor= rect procedure, please advise. > > Thanks for all the work everyone on the list does! > > Steven > > Thanks @sgharms :-) I am against the change in current form because: > * The concept may be useful for someone but it shall be a manually > selectable option like `rc_mute` (in analog to `boot_mute`) and not a > default. Maybe `rc_loglevel` that can get `silent, error, warning, > info, verbose, debug` levels to rc scripts and services? Change does > not provide a choice. > * Boot log messages are extremely useful, they contain important > diagnostic messages, these need to be logged even if silenced, these > cannot be just sent to `/dev/null`. Change alters (breaks) logging. > * Why not just put a boot logo image if you really do not want to see > the boot messages? It will provide better user experience as expected > but will not break the diagnostic information that are usually useful. > > My 2 cents :-) Okay, I am sorry, I mixed the general idea with detailed PR that aims just updating routing and devmatch parts with user selectable option not changing a defaults, thus my previous remarks are invalid and updated, I apologize! :-) * There is already `rc_info` that may be used? https://github.com/freebsd/freebsd-src/blob/50c962d773705f60d32c29f8e4bb274= 3ab55733b/libexec/rc/rc.conf#L29 * There is already `rc_startmsg` that may be used? https://github.com/freebsd/freebsd-src/blob/50c962d773705f60d32c29f8e4bb274= 3ab55733b/libexec/rc/rc.conf#L30 * If really necessary `_msgs` can be replaced with `_verbose` suffix? https://github.com/freebsd/freebsd-src/blob/50c962d773705f60d32c29f8e4bb274= 3ab55733b/libexec/rc/rc.conf#L568 * Adding `routing_flags` seems okay as `-q` may be set that way :-) * I guess the idea is to silence the terminal? How many flags need to be put to silent instead just one? Why not just put a boot logo image if you really do not want to see the boot messages? It may provide expected user experience and will not impact diagnostic information that are usually useful :-) --=20 CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From nobody Sun Feb 2 10:19: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 4Ym5Fz2TBxz5mFdq for ; Sun, 02 Feb 2025 10:19:19 +0000 (UTC) (envelope-from sgharms@stevengharms.com) Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136]) (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 "protonmail.com", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ym5Fz0K8Yz3S91 for ; Sun, 02 Feb 2025 10:19:19 +0000 (UTC) (envelope-from sgharms@stevengharms.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stevengharms.com; s=protonmail; t=1738491555; x=1738750755; bh=LvvmW92WagU1WjMJcr5h1JZdt8RkohEC3NAcyb11jAg=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=iOdxDLhBNW1is8lgZDzMn8qfqbg5D0bxc8CMxkhK476WKgFOTuLtu1g6rVkVtQ8dV SAWblilYmdm8mDNIvPKdcPZEt3ke8UzKvklq55BBrkIvKYh3XH6IHSRiI8O9xT5YH1 KljWyK9fZMkH9PCgV2KjEPZz+ZEHRrpRqemnPCDs= Date: Sun, 02 Feb 2025 10:19:11 +0000 To: Tomek CEDRO From: "Steven Harms (High-Security Mail)" Cc: "freebsd-current@freebsd.org" Subject: Re: Adjustments to userland for a quieter startup (RC system) Message-ID: In-Reply-To: References: Feedback-ID: 16996530:user:proton X-Pm-Message-ID: 373a0bd3e9024a418dd71d3bbb857810827df4b6 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-Queue-Id: 4Ym5Fz0K8Yz3S91 X-Spamd-Bar: ---- 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:62371, ipnet:185.70.40.0/24, country:CH] > Okay, I am sorry, I mixed the general idea with detailed PR that aims > just updating routing and devmatch parts with user selectable option > not changing a defaults, thus my previous remarks are invalid and > updated, I apologize! :-) A goal of this PR was to flush out dialogue around whether there was a univ= ersal noise level-adjusting knob in the RC system. [jlduran]'s more ambitio= us PR, my PR, and the discussion to this post suggest "no." I think it's pr= obably right to generalize the discussion! I also realize that this is a probably a controversial perspective. My moti= vation here is ultimately service to the FreeBSD Laptop project. Windows an= d OSX have conditioned many in the population of the FreeBSD-curious to exp= ect a lot less text on startup if things are going well.=20 To those who say "Yes, seeing the diagnostic data is why FreeBSD is so grea= t," I say: In a server/device context, I'd not change anything (something m= y PR may have flubbed in its implementation). ***But***, I contend that for= FreeBSD to thrive on a wider population of laptops and access a wider popu= lation of users, some options (including such a noise knob for the RC syste= m) ought be available. The extent that [helloSystem] went to hide messages = suggests an unmet need.=20 [helloSystem]: https://hellosystem.github.io/docs/developer/boot.html#boot-= mute [jlduran]: https://github.com/jlduran/freebsd-src/pull/90/files > * There is already `rc_info` that may be used? > https://github.com/freebsd/freebsd-src/blob/50c962d773705f60d32c29f8e4bb2= 743ab55733b/libexec/rc/rc.conf#L29 I could see that and/or rc_debug replacing RC scripts' use of `echo`, thoug= h. But (per "it's controversial"), we'd need future RC authors to adopt a n= otion of "log level output" versus "printf/echo to the screen." My PR was m= odest in its aims and didn't want to edit all the `echo`s. [jlduran] *did* = dare more bravely :) Although it seems (from the comments) that rc_debug ha= s some complex interactions with rc.subr that might make this option (my fa= vorite thus far) more complex than expected. [rc.subr]: https://github.com/freebsd/freebsd-src/blob/50c962d773705f60d32c= 29f8e4bb2743ab55733b/libexec/rc/rc.conf#L26 =20 > * There is already `rc_startmsg` that may be used? > https://github.com/freebsd/freebsd-src/blob/50c962d773705f60d32c29f8e4bb2= 743ab55733b/libexec/rc/rc.conf#L30 This was insufficient. It only squelched the "Starting ${name}" line :-/. e= .g. all the data e.g. about setting up a default route / interface output w= ere still logged. =20 > * If really necessary `_msgs` can be replaced with `_verbose` suffix? > https://github.com/freebsd/freebsd-src/blob/50c962d773705f60d32c29f8e4bb2= 743ab55733b/libexec/rc/rc.conf#L568 Seems promising, but this would mean more conditional logic per each flag? = I think that's probably insufficiently general. `info` with its control in = `rc_info` per your earlier suggestion would seem the way to go. > * I guess the idea is to silence the terminal? How many flags need to > be put to silent instead just one? Why not just put a boot logo image > if you really do not want to see the boot messages? It may provide > expected user experience and will not impact diagnostic information > that are usually useful :-) Sadly boot_mute=3D"YES" was insufficient as well. It only seems to mute /k= ernel/-level diagnostics. Afterward, my screen was still full of RC-origina= ting content. And yes, suppose we /could/ do an overlay until the login pro= mpt -- I think that should be supported. It's what I _expected_ boot_mute= =3DYES to do by default, frankly. Perhaps the take-away should be: * Existing interfaces are insufficient to let people easily tune their leve= l of RC output * Resolve: Is this something that should be available? * If so: resolve via log level, per-function verbosity suffixes, provide = a longer overlay bitmap duration option, or some other means Thank you for your consideration, Steven Steven From nobody Sun Feb 2 11:39:27 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 4Ym72t4Bzxz5mQYx for ; Sun, 02 Feb 2025 11:39:50 +0000 (UTC) (envelope-from freebsd-current-freebsd-org111@ketas.si.pri.ee) Received: from mail.ketas.si.pri.ee (d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13e8:21e:bff:fea2:d004]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ym72s4BWHz3jp7 for ; Sun, 02 Feb 2025 11:39:49 +0000 (UTC) (envelope-from freebsd-current-freebsd-org111@ketas.si.pri.ee) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ketas.si.pri.ee header.s=ketas-si-pri-ee-20240416002854-4096 header.b=uyMOiTWu; spf=pass (mx1.freebsd.org: domain of freebsd-current-freebsd-org111@ketas.si.pri.ee designates 2001:7d0:8437:13e8:21e:bff:fea2:d004 as permitted sender) smtp.mailfrom=freebsd-current-freebsd-org111@ketas.si.pri.ee; dmarc=pass (policy=reject) header.from=ketas.si.pri.ee X-Original-To: freebsd-current@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ketas.si.pri.ee; s=ketas-si-pri-ee-20240416002854-4096; t=1738496368; bh=KYBqx52HEt2qWfo9Mv7FxHvnkIycHnZ9VqPrl8ZDP3I=; h=Date:From:To:Subject:In-Reply-To:References; b=uyMOiTWuppt6al8JkN9QNfJabOibH3FCqSuKtdbJu55ztf3kg6vdGBSdw0Sm+mTgX 6JjJ0A9JXfvFLJygf+TZmqZqfHV4VDLvBLy5dsDNyib1U6ckWifPDqG3Hkct2QOofO RmWdME2pl9O5s5ITUaC4x9eP63vFB99+vXZtDr4JyieH2Rasu4eNj+hua6iW/eojPD JkiuQjv3pjjKZXWDrEr88+iK8rMbvY59E6m60Qtp13LB4d5ZLm9Y/ZvdJT8dfL1Jl+ Ad2wNUmv1PrWUOzFUcrfqHLBgZs4JuH1gk+DLd935Y/BS2vOQwoqu2vjC1KgIYjDGv G85VE0EN+rLjD5LwUs00nd2DTwddfqYnkc4b7+r4OWCqcu5VjfJGfRV6IQhkuXH09I usBm3WZG9xH3z4nFJHyQMEwhMWeJZfCPfyZWCDRek2wQtAMzpQ5orY6CGDbW8EQLO0 kiKpGRppG0KXkd8yKAABrN9zSsxUWi+vulj28Irhba5NVs/7ksHRL/E5FVXuSfiqf3 J5Xa39DjN0Py/PQ0sXKbdZBQ52Zc4/HqSzffyD2p5SCUgKszOYqojH6mNQwJBd1tIo flqP2sjpoBo+Hu+hxpuNlB73kqtwsp2M8q9tmlKXafknPj3b26ZALzugp1KDF0Msya N0bXHtvsEnevJpVrlAhKRHPU= Received: from [IPv6:::1] (0114-0000-0000-0000-13c8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13c8::114]) (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) (No client certificate requested) by mail.ketas.si.pri.ee (Postfix) with ESMTPSA id 02E9758BAC1 for ; Sun, 02 Feb 2025 13:39:27 +0200 (EET) Date: Sun, 02 Feb 2025 13:39:27 +0200 From: Sulev-Madis Silber To: freebsd-current@freebsd.org Subject: Re: Adjustments to userland for a quieter startup (RC system) User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: <0EF11DA1-448F-4A5A-A6E2-7764985C5C95@ketas.si.pri.ee> 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-Spamd-Result: default: False [-0.70 / 15.00]; HFILTER_HOSTNAME_5(3.00)[d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee]; NEURAL_HAM_LONG(-1.00)[-0.997]; NEURAL_HAM_MEDIUM(-0.97)[-0.969]; NEURAL_HAM_SHORT(-0.94)[-0.939]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; ONCE_RECEIVED(0.20)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ketas.si.pri.ee:+] X-Spamd-Bar: / X-Rspamd-Queue-Id: 4Ym72s4BWHz3jp7 if i read what hellosystem did to whole init, i can't see how it could be i= mplemented easily, nevermind it being default=2E they also disabled ttys an= d everything unsure what the solution would be here there are number of custom fbsd inits, even i have it, with defaults unlik= ely to be suitable for anyone except me=2E i have plans to take some of tha= t and add as features to see if they would have use elsewhere i never looked, can you disable kernel output too? someone suggested redir= ecting output to serial where it disappears or using splashes=2E that, of c= ourse hides everything=2E can't even debug errors=2E it's like windows syst= em, if you ask someone to help you, they might ask what's on the screen, th= en you say nothing, it just sits the with empty screen=2E then helper would= be like oh bummer too=2E it's all nice quiet and dumb maybe there could be midpoint here=2E maybe some key or something=2E unsur= e how it would work tho=2E as it goes from loader to kernel to init/multius= er i get the issue, just can't think of easy solution here that wouldn't piss= off others=2E by watching init, it's easy to spot setup errors=2E yeah, gr= anted, if you even know what it all means i'm thinking of what linux distros do=2E they are more common on laptops= =2E i haven't heard them hiding all and nor do i hear massive complaints ab= out "machine scribberish"? who knows what the real solution is=2E patch init to hell and back, to inc= lude all that=2E make special desktop overlay, so the granny won't ask son,= what's the wlan0? remember, init still needs to be fast and usable after all this work and m= aybe it can't be default=2E nevermind that current install is inherently un= friendly and doesn't really allow one to boot into open firefox home page e= asily=2E and who can make it happen, are unlikely to be bothered with messa= ges i get the problem tho also, when people, maybe not on fbsd but else where, complained that it bo= ots over a minute, how can it be=2E who even boots machines that much=2E th= at was for servers=2E maybe laptops get booted nore often, esp=2E how the s= uspend doesn't often work and nevermind to disk, that's not even implemente= d=2E so people boot=2E also, is this recent or what=2E systems have booted = for some time since forever=2E ok this is about time, not messages=2E maybe= times indeed need blank screens with nice images i'm like, when i reboot android phone, i often wonder why does it shutdown= or init that long=2E i wish i could see, if i want, what it does=2E i bet = here it's similar, how to, like, get messages if needed, all, of one wants,= and definitely any irrecoverable errors, eg failed storage or so maybe i have use for it on my own even if somebody comes out with all arou= nd good solution From nobody Sun Feb 2 12:08:25 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 4Ym7h70WWxz5mTsT for ; Sun, 02 Feb 2025 12:08:39 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 4Ym7h64J5Bz3qSK for ; Sun, 02 Feb 2025 12:08:38 +0000 (UTC) (envelope-from allbery.b@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-ab6fb1851d4so398296966b.0 for ; Sun, 02 Feb 2025 04:08:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738498117; x=1739102917; 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=FgMSodiqUpCs9bU51h58Mlo1ppsFgx4Hf41RiNBU1XQ=; b=FBczL7Y3rFnejuvA0HOAy/7xuDFCrn4p1entcKM5pD0poCLE0GbFiMJTyvTyRlJGBe 5JSEb4hWq88EQXzfqry0HeKEoGy06SHqz/C1pVpjapXkGHSktHxML3p2Lm3nPuD3p2aq jnFN3XqQH4bHriN9XjUykUzjVWQUmZg5YiGlX+wgKg//KlFx9VeuYabPY8dtenmsICHk SI8JbdH5mIycyU1r1j4KEg8ucrLSKhsvbx0apNGIO9WumHM6p0dKsUaK+GtobeNovcu0 A3OhMk5AeU1D6WhpXtnOomto6Q7xgC7IP6pfm5fAFBBn6pXKFKFGmWxi3WFts8HOlD4p 0dow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738498117; x=1739102917; 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=FgMSodiqUpCs9bU51h58Mlo1ppsFgx4Hf41RiNBU1XQ=; b=CqmgErMaj34j+RlGr2SsJQuj7laE1plu4Ro+Qwlr2a+rGUwXoU9X93NJsdwOoFx2WP XsMHMoBBM8gVHXo1TJxKsM5x00DKX01Tn6SYz8bRS21W/NoxwDpfChn5cGv0UEk//gxa +ExQSrxJ4zADxorFo+jYpj66x3d7HMefdWIyRCNdbNQXAFLttbn/kXGSHbi04UezvGgx sIBzL2kGeXqTgbHYovO4AdVQM8iZrIF8/OOdnqkoiOpoU8ZaH+DjgsWssCi5q9SwPuQr R48LTOa485RqJzRm8xFe0pi3Mzl7rvLvByM/pIXxkzPtXeMJsx1hnP7LlQitXfPdCAP/ ok0w== X-Gm-Message-State: AOJu0Yx8Hm1V17po3LeXs9kMwSuLuNX8DMGy2HSJeOkD5grvL5gdT+vu VAPgcfsbwjSr1O2C6+46y8ok9I/kiHlgxZsbSZ3DYmDIVDwgi4s+lHzrCbY2i5e0Qe9DKj2M5gW arVhnEmWMBmTucfPY/IyCLPFGinOZiw== X-Gm-Gg: ASbGncsW3kMS/FS2qu4+LX/9sHjzHVW7msAU1EijfgdHl2ErE71CZSI+DyacDn6fKw8 /BueYWDBQpqo1Q7P4DqEHxR71dP+yJzJxfY1I9hA5qGMwG+Px2YsqRnFb3OxwO0N5WzrfRlRP X-Google-Smtp-Source: AGHT+IGVcvnwDO18ivYE7RwXWrJb9Ej5DG+nsDgd2ufmS5pUUqq+JVkhlJ2KJ2BIahcVjVMyvVgQozjV9i8UkNPhsEA= X-Received: by 2002:a17:907:7d9e:b0:ab6:f4eb:91aa with SMTP id a640c23a62f3a-ab6f7443f26mr1322637366b.10.1738498116615; Sun, 02 Feb 2025 04:08:36 -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: <0EF11DA1-448F-4A5A-A6E2-7764985C5C95@ketas.si.pri.ee> In-Reply-To: <0EF11DA1-448F-4A5A-A6E2-7764985C5C95@ketas.si.pri.ee> From: Brandon Allbery Date: Sun, 2 Feb 2025 07:08:25 -0500 X-Gm-Features: AWEUYZk5XuB-z-3AgJWZH42IwtRwF6kgdZKmnUznPJK5_WKEam9q6oBwaSTonZs Message-ID: Subject: Re: Adjustments to userland for a quieter startup (RC system) To: Sulev-Madis Silber Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000af073b062d27a2ed" X-Rspamd-Queue-Id: 4Ym7h64J5Bz3qSK X-Spamd-Bar: ---- 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_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --000000000000af073b062d27a2ed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Feb 2, 2025 at 6:40=E2=80=AFAM Sulev-Madis Silber < freebsd-current-freebsd-org111@ketas.si.pri.ee> wrote: > i'm thinking of what linux distros do. they are more common on laptops. i > haven't heard them hiding all and nor do i hear massive complaints about > "machine scribberish"? > systemd-journald captures all the logs and you use journalctl to access them. dmesg does most of the relevant things on fbsd. > also, when people, maybe not on fbsd but else where, complained that it > boots over a minute, how can it be. who even boots machines that much. th= at > was for servers. maybe laptops get booted nore often, esp. how the suspen= d > doesn't often work and nevermind to disk, that's not even implemented. so > people boot. also, is this recent or what. systems have booted for some > time since forever. ok this is about time, not messages. maybe times inde= ed > need blank screens with nice images > Linux systemd puts a UI up as quickly as possible while booting continues in the background. I'm not sure how trustworthy that is, TBH. --=20 brandon s allbery kf8nh allbery.b@gmail.com --000000000000af073b062d27a2ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Feb 2, 2025 at 6:40=E2=80=AFAM Su= lev-Madis Silber <freebsd-current-freebsd-org111@ketas.si.pri.ee> wrote:
i'm thinking of what linux distros do. they= are more common on laptops. i haven't heard them hiding all and nor do= i hear massive complaints about "machine scribberish"?

systemd-journald captures all the logs and you u= se journalctl to access them. dmesg does most of the relevant things on fbs= d.
=C2=A0
= also, when people, maybe not on fbsd but else where, complained that it boo= ts over a minute, how can it be. who even boots machines that much. that wa= s for servers. maybe laptops get booted nore often, esp. how the suspend do= esn't often work and nevermind to disk, that's not even implemented= . so people boot. also, is this recent or what. systems have booted for som= e time since forever. ok this is about time, not messages. maybe times inde= ed need blank screens with nice images

= Linux systemd puts a UI up as quickly as possible while booting continues i= n the background. I'm not sure how trustworthy that is, TBH.

--
brandon s allbery kf8nh
=
--000000000000af073b062d27a2ed-- From nobody Sun Feb 2 19:38: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 4YmKgq62Qqz5mnxV for ; Sun, 02 Feb 2025 19:39:03 +0000 (UTC) (envelope-from tomek@cedro.info) 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 4YmKgq3kjtz3Mgf for ; Sun, 02 Feb 2025 19:39:03 +0000 (UTC) (envelope-from tomek@cedro.info) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-6f7440444efso21295947b3.2 for ; Sun, 02 Feb 2025 11:39:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cedro.info; s=google; t=1738525142; x=1739129942; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=fqS01QU8/u18BBZ/KFor3h6C/X1xPlXvEwN193wj4iw=; b=cC/ljFSykpTRV4l+T81A4+zdztl4At6EpD7uRl/3M4NcwAiqbslDImNt69gSvRDP0B c0YQSo4bajBLIkXRFgGoXcp7xtFdGWhdZfRW9c451wzAc9RcqWPD1mw4gbADebXkrIeF iN+TRM8XIns/8Z/CblvXn4enu1RvWomSjKReW9VH0IlqbaBBXN+WM1TaFGT0oFtcYXz5 g7Oa5PhluyO4NAyRZV+bgXdw0lfrfJw3yDz5XENAsMw1NV+MGasnyvr+ZtxEwd7tPYzB hsvGY3nhOnUrZ8pOYzAJR30K9qpXV+dnFXwmQL6o7u6xPOnqQypP3KbOTCtOAkQ0lAcE p2oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738525142; x=1739129942; h=content-transfer-encoding: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=fqS01QU8/u18BBZ/KFor3h6C/X1xPlXvEwN193wj4iw=; b=By/XrpJmP8kPmu+BilHOdi8SdLTFqRN9UfHH5k9EWBDy72t6nMfH18i1i2vinx0sHd m5YlNnUrQHVC2RP3Ns+2OEvwMwOOjrgP+BpP9JrVswGBqj6qJ6crGxzifZXfIJY9Txhd 3+3wzhFCyr/c+7F14PBJrLYQT5vFzyFuyjnnyQ+/p4iBUsED9R3DzS5jM1Ie9ZkcGgSW /aFGvJ9nJIzD6hI4KFCs8yG+XYV16EfOpR0H6mtviUkJoJwv1+XBCRT6yK04pjNgM435 +bdlgcOgb2TVQ73M0XLT600DNkmJJCUd/tXbyymUmfBzTfCCS5tBGjx/UEmMGRLy/RZa 48SQ== X-Gm-Message-State: AOJu0YzC+AHMeuxXwR9LdH9NUJCjG+CQll5RafuZnLlOOGDjoDgytjUt XBatm+qbM93u5dCOSqQ0GSP/GMZAqipHfdALuYFyjECmkW0Q7c7sh5nGxQU4hEYdyWk9/WmYjdo = X-Gm-Gg: ASbGncutgr8m4qIA1arLYMEkTcjm+Ren6vCu9vsPSZWo+xe7gc/eZBdcLCQoQnnxYGl bNvwHGCYThFMm+YG2dd6fJWwPHEG2KspvNDJViW9ym9DmQJEZkocnsbg6CMkCUmtK6BEnQUKYF8 jCdq2n/4ZJsajF2fbo9aolIWcveTAUBV0G16b2928rEvmUhLLBI61uwSk/+1/tqTmrL0L4H2YC3 n90Ro8meCoIPPlIrlJeAPWE1CaM4m/lYYSdCNKF+Cn0JA/jGh0e8Gq6ABI5xaHjCKF3PabuoQbF jfgI3oeHgO9MUzeFaSZBZSuXShV2MZJcvQQSQAjI7Kt/Cl6x3Ssi X-Google-Smtp-Source: AGHT+IHrlDWPUtgbBPeAATy/I1LLbGdHJgfjvgm/pK1rdqHyh2HwPDtPnC0HR3Iy/xHUHO/k65pOiQ== X-Received: by 2002:a05:690c:4d44:b0:6ef:77e3:efe3 with SMTP id 00721157ae682-6f7a834ee68mr143312427b3.13.1738525141812; Sun, 02 Feb 2025 11:39:01 -0800 (PST) Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com. [209.85.219.181]) by smtp.gmail.com with ESMTPSA id 00721157ae682-6f8c4639a45sm18026717b3.34.2025.02.02.11.38.59 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 02 Feb 2025 11:39:00 -0800 (PST) Received: by mail-yb1-f181.google.com with SMTP id 3f1490d57ef6-e549be93d5eso4143560276.1 for ; Sun, 02 Feb 2025 11:38:59 -0800 (PST) X-Received: by 2002:a05:6902:2845:b0:e25:ca37:b669 with SMTP id 3f1490d57ef6-e58a4b12c0fmr11806736276.24.1738525139656; Sun, 02 Feb 2025 11:38:59 -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: Tomek CEDRO Date: Sun, 2 Feb 2025 20:38:47 +0100 X-Gmail-Original-Message-ID: X-Gm-Features: AWEUYZkDsO4cCMEz98CM95ElylqMgJhbF1DBfn_ii7b2_jhzhR1n3dS89J2AfYg Message-ID: Subject: Re: Adjustments to userland for a quieter startup (RC system) To: "Steven Harms (High-Security Mail)" Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YmKgq3kjtz3Mgf X-Spamd-Bar: ---- 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] On Sun, Feb 2, 2025 at 11:19=E2=80=AFAM Steven Harms (High-Security Mail) wrote: > > Okay, I am sorry, I mixed the general idea with detailed PR that aims > > just updating routing and devmatch parts with user selectable option > > not changing a defaults, thus my previous remarks are invalid and > > updated, I apologize! :-) > > A goal of this PR was to flush out dialogue around whether there was a un= iversal noise level-adjusting knob in the RC system. [jlduran]'s more ambit= ious PR, my PR, and the discussion to this post suggest "no." I think it's = probably right to generalize the discussion! > > I also realize that this is a probably a controversial perspective. My mo= tivation here is ultimately service to the FreeBSD Laptop project. Windows = and OSX have conditioned many in the population of the FreeBSD-curious to e= xpect a lot less text on startup if things are going well. Thank you Steven, and my apologies once again to mix things up badly, I feel ashamed, I need to sleep more as my 8-bit Neural Network CPU does not seem to cope with this surrounding world "innovation" and multitasking :-P Yes that would be a controversial decision to change defaults to mute and get rid of boot/rc messages, thus my inital allergic reaction, sorry :D But its always good to talk things over maybe a new solution can show up that way and will not flip everything upside down over and over again :-) One "black box" scenario that came to my mind we did not mention is some embedded system that we really do not want to show anything OS related just the final login prompt.. or was that the initial idea? > To those who say "Yes, seeing the diagnostic data is why FreeBSD is so gr= eat," I say: In a server/device context, I'd not change anything (something= my PR may have flubbed in its implementation). ***But***, I contend that f= or FreeBSD to thrive on a wider population of laptops and access a wider po= pulation of users, some options (including such a noise knob for the RC sys= tem) ought be available. The extent that [helloSystem] went to hide message= s suggests an unmet need. > > [helloSystem]: https://hellosystem.github.io/docs/developer/boot.html#boo= t-mute > [jlduran]: https://github.com/jlduran/freebsd-src/pull/90/files > (..) > > * I guess the idea is to silence the terminal? How many flags need to > > be put to silent instead just one? Why not just put a boot logo image > > if you really do not want to see the boot messages? It may provide > > expected user experience and will not impact diagnostic information > > that are usually useful :-) > > Sadly boot_mute=3D"YES" was insufficient as well. It only seems to mute = /kernel/-level diagnostics. Afterward, my screen was still full of RC-origi= nating content. And yes, suppose we /could/ do an overlay until the login p= rompt -- I think that should be supported. It's what I _expected_ boot_mute= =3DYES to do by default, frankly. Looks like the boot logo screen component needs an update, so it covers the rc scripts too, and maybe show some animated spinner indicating working stuff in the background, and this should fix the problem right? Most systems work that way already, and pressing Tab or Esc jumps to the log messages easily when necessary / possible / allowed. Log levels is just an idea for generic commonly practiced solution that may be applied to rc/init, you replace echo / printf with log(lvl, fmsg, ..), but its quite a big task and not sure if really critical right now / worth the time..? Thank you :-) Tomek --=20 CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From nobody Sun Feb 2 20:14:03 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 4YmLSM4Mt5z5msq3 for ; Sun, 02 Feb 2025 20:14:11 +0000 (UTC) (envelope-from sgharms@stevengharms.com) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (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 "protonmail.com", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YmLSM0pqhz3TkQ for ; Sun, 02 Feb 2025 20:14:11 +0000 (UTC) (envelope-from sgharms@stevengharms.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stevengharms.com; s=protonmail; t=1738527247; x=1738786447; bh=0JxC4mIjJURzOAq+73RMMEV0wMnoU+PZQqMJ25L2JY4=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=Q/ngI8ucWlUbd+vKYZeriIGGI/HhJXP3xd7P7AefIvWln6bUecBMocgBIUxpBd/tO vubpijbIKCoRhZYirMylAIJT6oktwEf1824Jif5J1Mc/gbknQVzsgGbGrNRRzdLkNM lBpSAU1ls1aR9RTZ92YeXWvF4eXcCorl7CABsLWE= Date: Sun, 02 Feb 2025 20:14:03 +0000 To: Tomek CEDRO From: "Steven Harms (High-Security Mail)" Cc: "freebsd-current@freebsd.org" Subject: Re: Adjustments to userland for a quieter startup (RC system) Message-ID: <44Sc-RwC_I83PwTD-UykFfG8EFcHnBwZscSteeNEqJ_sdnmc-wrhdj-kWf2XxYDln0qB70HW3AD9qqBLEkBNeohWxlugR68PuDNYVR85PBE=@stevengharms.com> In-Reply-To: References: Feedback-ID: 16996530:user:proton X-Pm-Message-ID: a4fe3b31aa72a75c15025c193a34e86a7f496345 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-Queue-Id: 4YmLSM0pqhz3TkQ X-Spamd-Bar: ---- 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:62371, ipnet:185.70.43.0/24, country:CH] On Sunday, February 2nd, 2025 at 2:38 PM, Tomek CEDRO wr= ote: > One "black box" scenario that came to my mind we did not mention is > some embedded system that we really do not want to show anything OS > related just the final login prompt.. or was that the initial idea? That wasn't one of my main drivers, but once you settle that position at one extreme (silence) versus say a class on learning kernel design (maximal verbosity using FreeBSD as platform), it suggests that an RC mechanism that supports the full range of verbosity is useful. > Log levels is just an idea for generic commonly practiced solution > that may be applied to rc/init, you replace echo / printf with > log(lvl, fmsg, ..), but its quite a big task and not sure if really > critical right now / worth the time..? Is it critical? Probably not. Supporting more video hardware and wifi cards= is critical. But is it more than just mere chrome polishing? I think so. It's the first chance to show the market what the FreeBSD way looks like; it's a chance to show that it's not _entirely_ spartan. There's some consideration to tas= te and design. While Apple represents an extreme case, how the box feels when = it's opened is a legitimate concern. How the laptop looks at boot, I think, is a similar concern. > > Sadly boot_mute=3D"YES" was insufficient as well. It only seems to mute= /kernel/-level diagnostics. Afterward, my screen was still full of RC-orig= inating content. And yes, suppose we /could/ do an overlay until the login = prompt -- I think that should be supported. It's what I expected boot_mute= =3DYES to do by default, frankly. >=20 >=20 > Looks like the boot logo screen component needs an update, so it > covers the rc scripts too, and maybe show some animated spinner > indicating working stuff in the background, and this should fix the > problem right? Most systems work that way already, and pressing Tab or > Esc jumps to the log messages easily when necessary / possible / > allowed. I support this implementation. boot_mute=3DYES hides all diagnostic data up to the prompt being ready (surely one could hook getty's code for an ioctl?). I also think that ESC as a means for getting to the full diagnostics as in status quo is a great place to debug uh-oh moments. It's beyond my capability to size this story, *but* I can't imagine it being a weeks-long effort. Steven From nobody Sun Feb 2 20:25:59 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 4YmLkB3ZThz5mvHv for ; Sun, 02 Feb 2025 20:26:10 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YmLk96zMYz3Yxg for ; Sun, 02 Feb 2025 20:26:09 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 9E95089295; Sun, 02 Feb 2025 20:26:02 +0000 (UTC) Received: (from phk@localhost) by critter.freebsd.dk (8.18.1/8.16.1/Submit) id 512KQ05r004151; Sun, 2 Feb 2025 20:26:00 GMT (envelope-from phk) Message-Id: <202502022026.512KQ05r004151@critter.freebsd.dk> To: "Steven Harms (High-Security Mail)" cc: Tomek CEDRO , "freebsd-current@freebsd.org" Subject: Re: Adjustments to userland for a quieter startup (RC system) In-reply-to: <44Sc-RwC_I83PwTD-UykFfG8EFcHnBwZscSteeNEqJ_sdnmc-wrhdj-kWf2XxYDln0qB70HW3AD9qqBLEkBNeohWxlugR68PuDNYVR85PBE=@stevengharms.com> From: "Poul-Henning Kamp" References: <44Sc-RwC_I83PwTD-UykFfG8EFcHnBwZscSteeNEqJ_sdnmc-wrhdj-kWf2XxYDln0qB70HW3AD9qqBLEkBNeohWxlugR68PuDNYVR85PBE=@stevengharms.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-ID: <4149.1738527959.1@critter.freebsd.dk> Date: Sun, 02 Feb 2025 20:25:59 +0000 X-Rspamd-Queue-Id: 4YmLk96zMYz3Yxg X-Spamd-Bar: ---- 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:1835, ipnet:130.225.0.0/16, country:EU] I'm just going to throw this idea out here: Various non-UNIX operating systems dedicate a small piece of raw disk to logging purposes, and stick everything on there, instead of blasting it at users, who seldom care and cannot read that fast anyway. The big advantage is that the log is incredibly robust, as long as the disk works, it gets recorded. But the log is also easy to get to, both from a running system and from a disk which is beyond repair. Admittedly, most of the systems I have seen this on, had simple disk-controller interfaces, whereas we have who knows how many different kinds of devices and interfaces which masqurade as "disks". But we already have infrastructure for swap-spaces and dumping to them, even when the kernel is pretty hosed, so one would not have to start the project from scratch. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.