From nobody Mon Feb 6 22:04:07 2023 X-Original-To: freebsd-stable@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 4P9gJv1Ts6z3nTgg for ; Mon, 6 Feb 2023 22:04:15 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 "smarthost1.sentex.ca", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P9gJt36jpz4DPN for ; Mon, 6 Feb 2023 22:04:14 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of mike@sentex.net designates 2607:f3e0:0:1::12 as permitted sender) smtp.mailfrom=mike@sentex.net; dmarc=none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.16.1/8.16.1) with ESMTPS id 316M47qD053070 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL) for ; Mon, 6 Feb 2023 17:04:07 -0500 (EST) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:186a:8e9b:a33f:ac0a] ([IPv6:2607:f3e0:0:4:186a:8e9b:a33f:ac0a]) by pyroxene2a.sentex.ca (8.16.1/8.15.2) with ESMTPS id 316M474e070785 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Mon, 6 Feb 2023 17:04:07 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <0600fbab-035f-fd23-a6d7-27cd2f58665e@sentex.net> Date: Mon, 6 Feb 2023 17:04:07 -0500 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Content-Language: en-US To: FreeBSD-STABLE Mailing List From: mike tancsa Subject: Raptor Lake / Alder lake on RELENG_13 ? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.84 X-Spamd-Result: default: False [-2.40 / 15.00]; SUBJECT_ENDS_QUESTION(1.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)[+ip6:2607:f3e0::/32]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[199.212.134.19:received]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[mike]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[sentex.net]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4P9gJt36jpz4DPN X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Hi All,     I have seen a couple of commits around these CPUs, but wondering if anyone is running 13 on these newer hybrid CPUs ? Do the slower cores just get disabled or are they made use of somehow ?     ---Mike From nobody Tue Feb 7 13:29:15 2023 X-Original-To: freebsd-stable@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 4PB3rM5QfDz3myyb for ; Tue, 7 Feb 2023 13:29:23 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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 "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PB3rM3G9rz3Mjx for ; Tue, 7 Feb 2023 13:29:23 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.16.1/8.16.1) with ESMTP id 317DTGcO030932; Tue, 7 Feb 2023 07:29:16 -0600 (CST) (envelope-from mike@karels.net) Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id X22eCyxS4mPSeAAAs/W3XQ (envelope-from ); Tue, 07 Feb 2023 07:29:16 -0600 From: Mike Karels To: mike tancsa Cc: FreeBSD-STABLE Mailing List Subject: Re: Raptor Lake / Alder lake on RELENG_13 ? Date: Tue, 07 Feb 2023 07:29:15 -0600 X-Mailer: MailMate (1.14r5937) Message-ID: In-Reply-To: <0600fbab-035f-fd23-a6d7-27cd2f58665e@sentex.net> References: <0600fbab-035f-fd23-a6d7-27cd2f58665e@sentex.net> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4PB3rM3G9rz3Mjx X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 6 Feb 2023, at 16:04, mike tancsa wrote: > Hi All, > > =C2=A0=C2=A0=C2=A0 I have seen a couple of commits around these CPUs, b= ut wondering if anyone is running 13 on these newer hybrid CPUs ? Do the = slower cores just get disabled or are they made use of somehow ? > > =C2=A0=C2=A0=C2=A0 ---Mike I have been testing the changes on -current, and they are working fine. = I have not tested on 13, but I would expect the same result. The workaro= und is on 13-stable, but not yet a RELENG branch. Presumably it will be = in 13.2 when it is branched. If no one else has reported, I will test th= e 13.2 branch. Also, I haven=E2=80=99t heard of tests on Raptor Lake, bu= t I have heard that the behavior should be the same as Alder Lake. The E-cores are not disabled. They are forced to use a less efficient me= thod of page invalidation. They are scheduled as if they were P-cores wi= thout threads, but they are less used because of the shared cache among 4= cores rather than 2. I have some preliminary scheduler changes that rec= ognize the slower cores, but there are still issues to be dealt with. Mike From nobody Tue Feb 7 13:41:07 2023 X-Original-To: freebsd-stable@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 4PB45x53Rfz3n0PG for ; Tue, 7 Feb 2023 13:41:09 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 "smarthost1.sentex.ca", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PB45x2wwmz3PqD for ; Tue, 7 Feb 2023 13:41:09 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.16.1/8.16.1) with ESMTPS id 317Df6PN019046 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Tue, 7 Feb 2023 08:41:06 -0500 (EST) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:d4f2:9647:fa6a:7176] ([IPv6:2607:f3e0:0:4:d4f2:9647:fa6a:7176]) by pyroxene2a.sentex.ca (8.16.1/8.15.2) with ESMTPS id 317Df6uK093623 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 7 Feb 2023 08:41:06 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <8b609a35-cd3c-b191-ec8e-a0819cfc013e@sentex.net> Date: Tue, 7 Feb 2023 08:41:07 -0500 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Raptor Lake / Alder lake on RELENG_13 ? Content-Language: en-US To: Mike Karels Cc: FreeBSD-STABLE Mailing List References: <0600fbab-035f-fd23-a6d7-27cd2f58665e@sentex.net> From: mike tancsa In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4PB45x2wwmz3PqD X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 2/7/2023 8:29 AM, Mike Karels wrote: > On 6 Feb 2023, at 16:04, mike tancsa wrote: > >> Hi All, >> >>     I have seen a couple of commits around these CPUs, but wondering if anyone is running 13 on these newer hybrid CPUs ? Do the slower cores just get disabled or are they made use of somehow ? >> >>     ---Mike > I have been testing the changes on -current, and they are working fine. I have not tested on 13, but I would expect the same result. The workaround is on 13-stable, but not yet a RELENG branch. Presumably it will be in 13.2 when it is branched. If no one else has reported, I will test the 13.2 branch. Also, I haven’t heard of tests on Raptor Lake, but I have heard that the behavior should be the same as Alder Lake. > > The E-cores are not disabled. They are forced to use a less efficient method of page invalidation. They are scheduled as if they were P-cores without threads, but they are less used because of the shared cache among 4 cores rather than 2. I have some preliminary scheduler changes that recognize the slower cores, but there are still issues to be dealt with. > Thank you very much for the detailed update!  Apart from some performance tweaking, would you say performance overall is pretty good, or will the scheduler enhancements need to be made still ?     ---Mike From nobody Tue Feb 7 14:09:26 2023 X-Original-To: freebsd-stable@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 4PB4kc368jz3n2F3 for ; Tue, 7 Feb 2023 14:09:28 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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 "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PB4kc2gpwz3hgd for ; Tue, 7 Feb 2023 14:09:28 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.16.1/8.16.1) with ESMTP id 317E9QCq031104; Tue, 7 Feb 2023 08:09:27 -0600 (CST) (envelope-from mike@karels.net) Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id C5LfN5Zb4mN+eQAAs/W3XQ (envelope-from ); Tue, 07 Feb 2023 08:09:26 -0600 From: Mike Karels To: mike tancsa Cc: FreeBSD-STABLE Mailing List Subject: Re: Raptor Lake / Alder lake on RELENG_13 ? Date: Tue, 07 Feb 2023 08:09:26 -0600 X-Mailer: MailMate (1.14r5937) Message-ID: <3E515D30-958F-4483-B02C-C124C6D108F5@karels.net> In-Reply-To: <8b609a35-cd3c-b191-ec8e-a0819cfc013e@sentex.net> References: <0600fbab-035f-fd23-a6d7-27cd2f58665e@sentex.net> <8b609a35-cd3c-b191-ec8e-a0819cfc013e@sentex.net> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4PB4kc2gpwz3hgd X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 7 Feb 2023, at 7:41, mike tancsa wrote: > On 2/7/2023 8:29 AM, Mike Karels wrote: >> On 6 Feb 2023, at 16:04, mike tancsa wrote: >> >>> Hi All, >>> >>> =C2=A0=C2=A0=C2=A0 I have seen a couple of commits around these CPUs= , but wondering if anyone is running 13 on these newer hybrid CPUs ? Do t= he slower cores just get disabled or are they made use of somehow ? >>> >>> =C2=A0=C2=A0=C2=A0 ---Mike >> I have been testing the changes on -current, and they are working fine= =2E I have not tested on 13, but I would expect the same result. The wo= rkaround is on 13-stable, but not yet a RELENG branch. Presumably it wil= l be in 13.2 when it is branched. If no one else has reported, I will te= st the 13.2 branch. Also, I haven=E2=80=99t heard of tests on Raptor Lak= e, but I have heard that the behavior should be the same as Alder Lake. >> >> The E-cores are not disabled. They are forced to use a less efficient= method of page invalidation. They are scheduled as if they were P-cores= without threads, but they are less used because of the shared cache amon= g 4 cores rather than 2. I have some preliminary scheduler changes that = recognize the slower cores, but there are still issues to be dealt with. >> > Thank you very much for the detailed update!=C2=A0 Apart from some perf= ormance tweaking, would you say performance overall is pretty good, or wi= ll the scheduler enhancements need to be made still ? > > =C2=A0=C2=A0=C2=A0 ---Mike Performance seems very good to me. As far as I can tell, the E-cores are= slower than P-cores with a single thread, but faster than the second thr= ead on a P-core. Hopefully scheduler improvements will help more for a w= orkload that uses fewer than all hardware threads. Software threading co= uld in theory be handled better by putting threads where they will share = cache, but that is not a simple addition. Mike From nobody Wed Feb 8 20:11:58 2023 X-Original-To: freebsd-stable@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 4PBrkf6vTxz3pCM3 for ; Wed, 8 Feb 2023 20:12:10 +0000 (UTC) (envelope-from mglazer2014@gmail.com) Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PBrkf4l2Yz3KN9 for ; Wed, 8 Feb 2023 20:12:10 +0000 (UTC) (envelope-from mglazer2014@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-xe2d.google.com with SMTP id y8so21246637vsq.0 for ; Wed, 08 Feb 2023 12:12:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=AEMKxFTK4+OnrWAQnYB7nFJ6Pw4nSr8uBcgflFmL3kk=; b=SsNjPSrELTYuFozmDge2L2JZHAYohbMmYspdNT7p+AxgP7riPzELPFTfRgm1otzljK s+t7vJ/qEoCVLOFl52LZJZt3M24jDRAq+mI2huvtx+hQdv/3oGlTeBnTN0YndlHx1Mdk OuFApi5WKQRQ++1KYsX6WpFt84RrqY/ph25INmUS41uzcGu/tQU3VGefxbjYli0Ilmz8 fB+Nffzcko2zxRkVXvypu2xeDZJ1lMAdU07UZm7PKEbR3QTgddq3NxqAvM1Q7Urw3XSB USqL3CeFSAEzTVKdd9JgnF16bn3gXFLnCqj+HgP/+ZyeHKLYaUUKPUf1H9wN4fIHfwGC KNoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=AEMKxFTK4+OnrWAQnYB7nFJ6Pw4nSr8uBcgflFmL3kk=; b=pxY+Q04ZbAqIcFGTHpfOq+UdaBPAtszh0+10bFs8SOBHjLGaaaGtgTe5E8CIah4aMZ uJTLIyc4aIj/kKGSMIL0RLZE0s+m0xeZ11EbuhG/dXRcL6HOgXwK84A0mIjM52Z/5WYb uBciT+Cp9QBJF8MmnnCIXhUKtZwuqoonL8RUAN1y4vqxrYwDbnm2FmljZDLxhL85OCjT wdcsMNndPnxLLjeC/1dwJFnYh5t5/vX7Au7lIcdz2wPV+4TW/HDKKiYRlJ8DtublemFx UUZDqEIH1Z/NMz5dvr+DkfVZc0/fp3ame41TimEhu/fJ4/f69WlwuJIsvsHUYHcs6ftf V1PA== X-Gm-Message-State: AO0yUKW9QrP2j9hrWEqvrUKar6ddenflOLEjwHpXHrGFabup3oG0HW5E uQu8955JDArka29C+d7TQNyj1kRkXLxMPANJCm5MylCg X-Google-Smtp-Source: AK7set/pVYxUODeWESbZo7m4sqMoeTgJ7xOOjLa/5Ala91fDoB//tY45+szRk0Un2SSKparY7ZEQwUeeHyngKNP0R64= X-Received: by 2002:a05:6102:3654:b0:3f7:fd86:face with SMTP id s20-20020a056102365400b003f7fd86facemr2303819vsu.6.1675887129451; Wed, 08 Feb 2023 12:12:09 -0800 (PST) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <20230208190751.A213687B0@freefall.freebsd.org> In-Reply-To: <20230208190751.A213687B0@freefall.freebsd.org> From: Martin Glazer Date: Wed, 8 Feb 2023 12:11:58 -0800 Message-ID: Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:01.tzdata To: freebsd-stable@freebsd.org Content-Type: multipart/alternative; boundary="00000000000008e06405f435e17e" X-Rspamd-Queue-Id: 4PBrkf4l2Yz3KN9 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000008e06405f435e17e Content-Type: text/plain; charset="UTF-8" unsubscribe On Wed, Feb 8, 2023 at 11:08 AM FreeBSD Errata Notices < errata-notices@freebsd.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > > ============================================================================= > FreeBSD-EN-23:01.tzdata Errata > Notice > The FreeBSD > Project > > Topic: Timezone database information update > > Category: contrib > Module: zoneinfo > Announced: 2022-02-08 > Affects: All supported versions of FreeBSD. > Corrected: 2022-12-01 01:36:29 UTC (stable/13, 13.1-STABLE) > 2023-02-08 16:08:28 UTC (releng/13.1, 13.1-RELEASE-p6) > 2022-12-01 01:40:23 UTC (stable/12, 12.4-STABLE) > 2023-02-08 18:30:20 UTC (releng/12.4, 12.4-RELEASE-p1) > 2023-02-08 18:28:25 UTC (releng/12.3, 12.3-RELEASE-p11) > > For general information regarding FreeBSD Errata Notices and Security > Advisories, including descriptions of the fields above, security > branches, and the following sections, please visit > . > > I. Background > > The IANA Time Zone Database (often called tz or zoneinfo) contains code and > data that represent the history of local time for many representative > locations around the globe. It is updated periodically to reflect changes > made by political bodies to time zone boundaries, UTC offsets, and > daylight-saving rules. > > FreeBSD releases install the IANA Time Zone Database in > /usr/share/zoneinfo. > The tzsetup(8) utility allows the user to specify the default local time > zone. Based on the selected time zone, tzsetup(8) copies one of the files > from /usr/share/zoneinfo to /etc/localtime. A time zone may also be > selected > for an individual process by setting its TZ environment variable to a > desired > time zone name. > > II. Problem Description > > Several changes to future and past timestamps have been recorded in the > IANA > Time Zone Database after previous FreeBSD releases were released. This > affects many users in different parts of the world. Because of these > changes, the data in the zoneinfo files need to be updated. If the local > timezone on the running system is affected, tzsetup(8) needs to be run to > update /etc/localtime. > > III. Impact > > An incorrect time will be displayed on a system configured to use one of > the > affected time zones if the /usr/share/zoneinfo and /etc/localtime files are > not updated, and all applications on the system that rely on the system > time, > such as cron(8) and syslog(8), will be affected. > > IV. Workaround > > The system administrator can install an updated version of the IANA Time > Zone > Database from the misc/zoneinfo port and run tzsetup(8). > > Applications that store and display times in Coordinated Universal Time > (UTC) > are not affected. > > V. Solution > > Upgrade your system to a supported FreeBSD stable or release / security > branch (releng) dated after the correction date. > > Please note that some third party software, for instance PHP, Ruby, Java, > Perl and Python, may be using different zoneinfo data sources, in such > cases > this software must be updated separately. Software packages that are > installed via binary packages can be upgraded by executing 'pkg upgrade'. > > Following the instructions in this Errata Notice will only update the IANA > Time Zone Database installed in /usr/share/zoneinfo. > > Perform one of the following: > > 1) To update your system via a binary patch: > > Systems running a RELEASE version of FreeBSD on the amd64, i386, or > (on FreeBSD 13 and later) arm64 platforms can be updated via the > freebsd-update(8) utility: > > # freebsd-update fetch > # freebsd-update install > > Restart all the affected applications and daemons, or reboot the system. > > 2) To update your system via a source code patch: > > The following patches have been verified to apply to the applicable > FreeBSD release branches. > > a) Download the relevant patch from the location below, and verify the > detached PGP signature using your PGP utility. > > # fetch https://security.FreeBSD.org/patches/EN-23:01/tzdata-2022g.patch > # fetch > https://security.FreeBSD.org/patches/EN-23:01/tzdata-2022g.patch.asc > # gpg --verify tzdata-2022g.patch.asc > > b) Apply the patch. Execute the following commands as root: > > # cd /usr/src > # patch -E < /path/to/patch > > c) Recompile the operating system using buildworld and installworld as > described in . > > Restart all the affected applications and daemons, or reboot the system. > > VI. Correction details > > This issue is corrected by the corresponding Git commit hash or Subversion > revision number in the following stable and release branches: > > Branch/path Hash Revision > - ------------------------------------------------------------------------- > stable/13/ e851e0aabdff stable/13-n253192 > releng/13.1/ 9e3b86743c4b releng/13.1-n250175 > stable/12/ r372783 > releng/12.4/ r372915 > releng/12.3/ r372911 > - ------------------------------------------------------------------------- > > For FreeBSD 13 and later: > > Run the following command to see which files were modified by a > particular commit: > > # git show --stat > > Or visit the following URL, replacing NNNNNN with the hash: > > > > To determine the commit count in a working tree (for comparison against > nNNNNNN in the table above), run: > > # git rev-list --count --first-parent HEAD > > For FreeBSD 12 and earlier: > > Run the following command to see which files were modified by a particular > revision, replacing NNNNNN with the revision number: > > # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base > > Or visit the following URL, replacing NNNNNN with the revision number: > > > > VII. References > > > > The latest revision of this advisory is available at > > -----BEGIN PGP SIGNATURE----- > > iQIzBAEBCgAdFiEEthUnfoEIffdcgYM7bljekB8AGu8FAmPj7/8ACgkQbljekB8A > Gu/xNg/9EgSCULshR9xN3vYa4sTdsMVLpz24zuRMxPqYAAFckJ2GDOwDuvIA78r+ > U8u/efb0pE3xJvbAH0vFMUqt7mxsJeO4TVurEpAMrsuQRfjru0FLzNlXhJUnTDF9 > mSveNDs1QeihpaOfG8b8v8onk1Nr6SMuVO37s5FdFNrGxc+WHpmXJiQqHy71r0AG > 4CtdgZ+TxjRmvKeU2ue/+xjDVhhTUEFoOjwaeq54dgVP9u3aFENFejcOjPZYVWJt > aNaMAiWvarER1HIhqKppVbui/U7J73lWC0ocBwCAA/NDhC5C0IEw3tPx5KLOmw5c > M4TX4bliFNLWnokPEdTd9OLU0OJzDhPn00awm9NH0c6F3y/dznHoYtKXVirj7GpW > FbKxsrsJf8xFxAHyFApLan7i7I1Y3R+mnRimYMUonfv08tVcCMlSu9QMXNmC+0+r > phCU6mwtrv/RwoRk0QGYyg9z4sfX+eKX2zhHiEigvbD6IHnIpcIRgu6yuZL/eETg > AwG2WUX3WSvi6C6hcQKPYw0mhxp4WnIFz6FmFYWBESDTSDjWRhmHCLU2VV7JvuPn > zRpY1dYJSbulAvWEXbKTh5oALuYfVSeL9qnbL2cmcxFCHJcyMm/yB9VOG9nMBFQD > drCXwK/KGV1jvD0OxHaemLs7hxTJwOaI4RKl9OWIS6J195YdPIc= > =z60r > -----END PGP SIGNATURE----- > > --00000000000008e06405f435e17e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
unsubscribe

On Wed, Feb 8, 2023 at 11:08 AM FreeBSD E= rrata Notices <errata-noti= ces@freebsd.org> wrote:
----= -BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D
FreeBSD-EN-23:01.tzdata=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0Errata Notice
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 The FreeBSD Project=

Topic:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Timezone database information upda= te

Category:=C2=A0 =C2=A0 =C2=A0 =C2=A0contrib
Module:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0zoneinfo
Announced:=C2=A0 =C2=A0 =C2=A0 2022-02-08
Affects:=C2=A0 =C2=A0 =C2=A0 =C2=A0 All supported versions of FreeBSD.
Corrected:=C2=A0 =C2=A0 =C2=A0 2022-12-01 01:36:29 UTC (stable/13, 13.1-STA= BLE)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 2023-02-08 16:08:28= UTC (releng/13.1, 13.1-RELEASE-p6)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 2022-12-01 01:40:23= UTC (stable/12, 12.4-STABLE)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 2023-02-08 18:30:20= UTC (releng/12.4, 12.4-RELEASE-p1)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 2023-02-08 18:28:25= UTC (releng/12.3, 12.3-RELEASE-p11)

For general information regarding FreeBSD Errata Notices and Security
Advisories, including descriptions of the fields above, security
branches, and the following sections, please visit
<URL:https://security.FreeBSD.org/>.

I.=C2=A0 =C2=A0Background

The IANA Time Zone Database (often called tz or zoneinfo) contains code and=
data that represent the history of local time for many representative
locations around the globe.=C2=A0 It is updated periodically to reflect cha= nges
made by political bodies to time zone boundaries, UTC offsets, and
daylight-saving rules.

FreeBSD releases install the IANA Time Zone Database in /usr/share/zoneinfo= .
The tzsetup(8) utility allows the user to specify the default local time zone.=C2=A0 Based on the selected time zone, tzsetup(8) copies one of the f= iles
from /usr/share/zoneinfo to /etc/localtime.=C2=A0 A time zone may also be s= elected
for an individual process by setting its TZ environment variable to a desir= ed
time zone name.

II.=C2=A0 Problem Description

Several changes to future and past timestamps have been recorded in the IAN= A
Time Zone Database after previous FreeBSD releases were released.=C2=A0 Thi= s
affects many users in different parts of the world.=C2=A0 Because of these<= br> changes, the data in the zoneinfo files need to be updated.=C2=A0 If the lo= cal
timezone on the running system is affected, tzsetup(8) needs to be run to update /etc/localtime.

III. Impact

An incorrect time will be displayed on a system configured to use one of th= e
affected time zones if the /usr/share/zoneinfo and /etc/localtime files are=
not updated, and all applications on the system that rely on the system tim= e,
such as cron(8) and syslog(8), will be affected.

IV.=C2=A0 Workaround

The system administrator can install an updated version of the IANA Time Zo= ne
Database from the misc/zoneinfo port and run tzsetup(8).

Applications that store and display times in Coordinated Universal Time (UT= C)
are not affected.

V.=C2=A0 =C2=A0Solution

Upgrade your system to a supported FreeBSD stable or release / security
branch (releng) dated after the correction date.

Please note that some third party software, for instance PHP, Ruby, Java, Perl and Python, may be using different zoneinfo data sources, in such case= s
this software must be updated separately.=C2=A0 Software packages that are<= br> installed via binary packages can be upgraded by executing 'pkg upgrade= '.

Following the instructions in this Errata Notice will only update the IANA<= br> Time Zone Database installed in /usr/share/zoneinfo.

Perform one of the following:

1) To update your system via a binary patch:

Systems running a RELEASE version of FreeBSD on the amd64, i386, or
(on FreeBSD 13 and later) arm64 platforms can be updated via the
freebsd-update(8) utility:

# freebsd-update fetch
# freebsd-update install

Restart all the affected applications and daemons, or reboot the system.
2) To update your system via a source code patch:

The following patches have been verified to apply to the applicable
FreeBSD release branches.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch https://security.FreeBSD.org= /patches/EN-23:01/tzdata-2022g.patch
# fetch https://security.FreeBSD= .org/patches/EN-23:01/tzdata-2022g.patch.asc
# gpg --verify tzdata-2022g.patch.asc

b) Apply the patch.=C2=A0 Execute the following commands as root:

# cd /usr/src
# patch -E < /path/to/patch

c) Recompile the operating system using buildworld and installworld as
described in <URL:https://www.FreeBSD.org/handbook= /makeworld.html>.

Restart all the affected applications and daemons, or reboot the system.
VI.=C2=A0 Correction details

This issue is corrected by the corresponding Git commit hash or Subversion<= br> revision number in the following stable and release branches:

Branch/path=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Hash=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Revision
- -------------------------------------------------------------------------=
stable/13/=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 e851e0aabdff=C2=A0 =C2=A0 stable/= 13-n253192
releng/13.1/=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 9e3b86743c4b=C2=A0 releng/13.1-n250175 stable/12/=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 r372783
releng/12.4/=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 r372915
releng/12.3/=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 r372911
- -------------------------------------------------------------------------=

For FreeBSD 13 and later:

Run the following command to see which files were modified by a
particular commit:

# git show --stat <commit hash>

Or visit the following URL, replacing NNNNNN with the hash:

<URL:https://cgit.freebsd.org/src/commit/?id=3DNN= NNNN>

To determine the commit count in a working tree (for comparison against
nNNNNNN in the table above), run:

# git rev-list --count --first-parent HEAD

For FreeBSD 12 and earlier:

Run the following command to see which files were modified by a particular<= br> revision, replacing NNNNNN with the revision number:

# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base

Or visit the following URL, replacing NNNNNN with the revision number:

<URL:https://svnweb.freebsd.= org/base?view=3Drevision&revision=3DNNNNNN>

VII. References

<URL:https://github.com/eggert/tz/blob/2022g/NEWS= >

The latest revision of this advisory is available at
<URL:https://security.FreeBSD.= org/advisories/FreeBSD-EN-23:01.tzdata.asc>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEthUnfoEIffdcgYM7bljekB8AGu8FAmPj7/8ACgkQbljekB8A
Gu/xNg/9EgSCULshR9xN3vYa4sTdsMVLpz24zuRMxPqYAAFckJ2GDOwDuvIA78r+
U8u/efb0pE3xJvbAH0vFMUqt7mxsJeO4TVurEpAMrsuQRfjru0FLzNlXhJUnTDF9
mSveNDs1QeihpaOfG8b8v8onk1Nr6SMuVO37s5FdFNrGxc+WHpmXJiQqHy71r0AG
4CtdgZ+TxjRmvKeU2ue/+xjDVhhTUEFoOjwaeq54dgVP9u3aFENFejcOjPZYVWJt
aNaMAiWvarER1HIhqKppVbui/U7J73lWC0ocBwCAA/NDhC5C0IEw3tPx5KLOmw5c
M4TX4bliFNLWnokPEdTd9OLU0OJzDhPn00awm9NH0c6F3y/dznHoYtKXVirj7GpW
FbKxsrsJf8xFxAHyFApLan7i7I1Y3R+mnRimYMUonfv08tVcCMlSu9QMXNmC+0+r
phCU6mwtrv/RwoRk0QGYyg9z4sfX+eKX2zhHiEigvbD6IHnIpcIRgu6yuZL/eETg
AwG2WUX3WSvi6C6hcQKPYw0mhxp4WnIFz6FmFYWBESDTSDjWRhmHCLU2VV7JvuPn
zRpY1dYJSbulAvWEXbKTh5oALuYfVSeL9qnbL2cmcxFCHJcyMm/yB9VOG9nMBFQD
drCXwK/KGV1jvD0OxHaemLs7hxTJwOaI4RKl9OWIS6J195YdPIc=3D
=3Dz60r
-----END PGP SIGNATURE-----

--00000000000008e06405f435e17e-- From nobody Thu Feb 9 02:24:14 2023 X-Original-To: stable@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 4PC1064w34z3nmF6 for ; Thu, 9 Feb 2023 02:24:22 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (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 "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PC1053p45z3FWj for ; Thu, 9 Feb 2023 02:24:21 +0000 (UTC) (envelope-from jhs@berklix.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of jhs@berklix.com has no SPF policy when checking 144.76.10.75) smtp.mailfrom=jhs@berklix.com; dmarc=none Received: from dell.no.berklix.net (p4fc4c2e9.dip0.t-ipconnect.de [79.196.194.233]) (authenticated bits=128) by land.berklix.org (8.16.1/8.16.1) with ESMTPSA id 3192OJMA046818 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL) for ; Thu, 9 Feb 2023 02:24:19 GMT (envelope-from jhs@berklix.com) Received: from dell.no.berklix.net (localhost [127.0.0.1]) by dell.no.berklix.net (8.16.1/8.16.1) with ESMTPS id 3192OEAb077156 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 9 Feb 2023 03:24:14 +0100 (CET) (envelope-from jhs@dell.no.berklix.net) Received: (from jhs@localhost) by dell.no.berklix.net (8.16.1/8.14.5/Submit) id 3192OEta077155; Thu, 9 Feb 2023 03:24:14 +0100 (CET) (envelope-from jhs) Message-Id: <202302090224.3192OEta077155@dell.no.berklix.net> To: stable@FreeBSD.org Subject: Re: Grep with non-ascii From: "Julian H. Stacey" Organization: http://berklix.com/jhs/ User-agent: EXMH on FreeBSD http://www.berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <77153.1675909454.1@dell.no.berklix.net> Date: Thu, 09 Feb 2023 03:24:14 +0100 X-Spamd-Result: default: False [-1.09 / 15.00]; FAKE_REPLY(1.00)[]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.992]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; DMARC_NA(0.00)[berklix.com]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[stable@FreeBSD.org]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; ASN(0.00)[asn:24940, ipnet:144.76.0.0/16, country:DE]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[jhs]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4PC1053p45z3FWj X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N > The one positive development in the world of computing that I would > credit to Java is the earliest big push toward the adoption of UTF-8. > I strongly hope UTF-8 becomes universally used sooner rather than > later. -- George No idea What might be best for Arabic, Greek, Japanese etc: But For international English (& Italian where English font started) it's wrong to expect masses of people OK with Ascii, to waste time extending / learning / configuring tools for un-necessary UTF. Bad enough were single bytes above 0x7f for European accents (eg umlauts etc) that ignored conventions eg Ae Oe Ue (& SS = sharf ess since dumped in .de). USD GBP EUR avoid dodgey currency symbols `$` & `#` etc. UTF & HTML & MIME base 64 make spam filtering via procmail a nightmare. UTF is a spam indicator, most auto discarded here. ports/textproc/mgdiff was last to break here, Umlauts changed to Ascii, better than changing mgdiff. Cheers, -- Julian Stacey www.StolenVotes.UK/jhs/ Arm Ukraine, Zap Putin. Brexit broke UK From nobody Thu Feb 9 12:18:47 2023 X-Original-To: stable@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 4PCGBD4mTqz3nmj3 for ; Thu, 9 Feb 2023 12:19:00 +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 4PCGBC0G17z3Qr7 for ; Thu, 9 Feb 2023 12:18:58 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 319CImRa028318 for ; Thu, 9 Feb 2023 21:18:48 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Thu, 9 Feb 2023 21:18:47 +0900 From: Tomoaki AOKI To: stable@freebsd.org Subject: Re: Grep with non-ascii Message-Id: <20230209211847.0fed55594c35ccde94b96221@dec.sakura.ne.jp> In-Reply-To: <202302090224.3192OEta077155@dell.no.berklix.net> References: <202302090224.3192OEta077155@dell.no.berklix.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.56 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.96)[-0.965]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[stable@freebsd.org]; RCVD_TLS_LAST(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4PCGBC0G17z3Qr7 X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Thu, 09 Feb 2023 03:24:14 +0100 "Julian H. Stacey" wrote: > > The one positive development in the world of computing that I would > > credit to Java is the earliest big push toward the adoption of UTF-8. > > I strongly hope UTF-8 becomes universally used sooner rather than > > later. -- George > > No idea What might be best for Arabic, Greek, Japanese etc: But > > For international English (& Italian where English font started) > it's wrong to expect masses of people OK with Ascii, to waste time > extending / learning / configuring tools for un-necessary UTF. > > Bad enough were single bytes above 0x7f for European accents (eg > umlauts etc) that ignored conventions eg Ae Oe Ue (& SS = sharf > ess since dumped in .de). > > USD GBP EUR avoid dodgey currency symbols `$` & `#` etc. > > UTF & HTML & MIME base 64 make spam filtering via procmail a nightmare. > UTF is a spam indicator, most auto discarded here. > > ports/textproc/mgdiff was last to break here, > Umlauts changed to Ascii, better than changing mgdiff. > > Cheers, > -- > Julian Stacey www.StolenVotes.UK/jhs/ Arm Ukraine, Zap Putin. Brexit broke UK IIUC, the 7bits part of UTF-8 100% matches 7bits part of ASCII. So it would be harmless to at least 7bits-ASCII-only users. But users who wants 8bits part (graphic characters and so on) and softwares which don't allow 8bits characters would be affected. TRON code is much different (basic character unit is 2*n bytes), but it's not at all supported/used in FreeBSD. Furthermore, FreeBSD already defaults to C.UTF-8 at Nov.14, 2020. [1] The actual commit is [2]. All reviewers listed in [1] approved the change. Note that this is NOT MFC'ed to stable/12 and before, although all 13.x has it (13.0 is released at Apr. 13,2021). [1] https://reviews.freebsd.org/D26973 [2] https://cgit.freebsd.org/src/commit/usr.bin/login/login.conf?id=09ef995baf45333d45ab214daf8c03e1a25f8fcc -- Tomoaki AOKI From nobody Thu Feb 9 17:47:31 2023 X-Original-To: freebsd-stable@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 4PCPXy2TQjz3n0MB; Thu, 9 Feb 2023 17:50:42 +0000 (UTC) (envelope-from yasu@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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PCPXy1zCCz4b52; Thu, 9 Feb 2023 17:50:42 +0000 (UTC) (envelope-from yasu@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675965042; 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=izZXy/+GLCclqGFQK6PBirewlrQLYaeY0GZHVV/Je3w=; b=gwkzZXpWIp5UKig056Zx/O57ECbfSnz88LHb5lW0aMd/iBmMFbK3WovzlqxOp09XuGb6g+ FwCH85hoScQcIgwx36I/yWg3BoRz/yPN3q4uSmTnUqQklkoLHJ4/ZlvAjFZdaFIJOZ5mGc so57rqLCKS9ckRFea+Mh451dTjB0budCICRbtpoGFe+bklCRH2AMZ0QsvcX//KaJOD6bpj nY45fpJCfpVIT+MDVu4QWuCpGauyubgTmDtTUkzaufe7ioe3qcmjT19vMenwWcIVEmto/t Om389N/86A4Paa2k4X6H255+r5DrqJxlLK7NlUlDzCyT5M1pMiSGD/wA49yeJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675965042; 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=izZXy/+GLCclqGFQK6PBirewlrQLYaeY0GZHVV/Je3w=; b=lDTObi6IbibtezUDLReNK0sv46vENKs748E4rGmDrHv0W7FvbLWQn9ba8UiYKDX1ACT55/ 46dEWkmyBGvcflmJl97Db+BlsmjYdq9m8Hz+QjtmOI3Tj3v+3qcnj4tLWwiTplj2jBaWqK G4ENFuxUkC9DAS0s5GbTJv+ptr84Lkafv22yI/VfeohKEUDLAsKThaHU9KWa9/XhmNhmzD Iy9ZcM883e8YCiisJcc5H5VJ5gaHA+za53CSnYoJX/xNPldLf6hW54ufKxDcK+4fo3HJ3w rHNXJESkepW4hUVoZyo16OzREEu3w0cmjR/chWFEf9gEGjsPWooHhU0lWZPkxA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675965042; a=rsa-sha256; cv=none; b=KJfE3JsMjPHAuZ+LuP1SYVwJ/stZp3rpozK7pjwt6Zl5VRAHGzF0l7b06k9kVotTGDKx8q 82zDi29ssFIpdUQmqtlWbaSzoMnarS8YJP2u9Mrv6EfPfQ17bK6Ef4yYm+K//5ELGBtaKf 8+BjDZQoKv5zMM6HP3xgAjldbtebvmMCDz/IXr5jXfINu/JDRYSSZijf8CE0h2Oej8jm2H TmVDaeQds0dVi62O9NH7EldGlogXG+jetglphGsV3INKyv55RglhitPChznt3ESCxpR4Me 5g9rIhWnPHHkGeSaA/2dr/l9v71hQ7+g3/UnzsWGLKZ9iygZaaOZks7eRpJ0Dg== Received: from localhost (unknown [IPv6:240b:11:220:fe00::174:11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: yasu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4PCPXx2gyszSxm; Thu, 9 Feb 2023 17:50:41 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Date: Fri, 10 Feb 2023 02:47:31 +0900 (JST) Message-Id: <20230210.024731.792407832299574349.yasu@FreeBSD.org> To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Boot hangs up with Alderlake's intel GbE NIC From: Yasuhiro Kimura In-Reply-To: <20220524.020220.691400348469428239.yasu@FreeBSD.org> References: <20220523.164402.599295865361994545.yasu@FreeBSD.org> <20220524.020220.691400348469428239.yasu@FreeBSD.org> X-Mailer: Mew version 6.8 on Emacs 30.0.50 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N From: Yasuhiro Kimura Subject: Re: Boot hangs up with Alderlake's intel GbE NIC Date: Tue, 24 May 2022 02:02:20 +0900 (JST) >> 2 months ago I updated my home server to Intel Alderlake Core i3 12100 >> and GIGABYTE H610I DDR4 (rev. 1.0) motherboard. >> >> The latter has onboard Intel GbE NIC. But unfortunately 13.0-RELEASE >> doesn't detect it. So I inserted Intel PCI-E GbE adaptor to the PCI-E >> slot of the motherbord and used it as network interface of the server. >> >> And now 13.1-RELEASE is released. I tried updating with >> `freebsd-update update -r 13.1-RELEASE`, `freebsd install` and >> `shutdown -r now`. But after that system hangs up in the middle of >> boot. >> >> At first boot stops after onboard Intel GbE NIC is detected. >> >> https://people.freebsd.org/~yasu/Alderlake-GbE-boot-hangup.01.jpg >> >> It keeps about a minute and then boot process resumes. But soon it >> stops again. >> >> https://people.freebsd.org/~yasu/Alderlake-GbE-boot-hangup.02.jpg >> >> I waited about 20 minites in this state but boot never go ahead. >> >> Removing PCE-E GbE adopter doesn't change the situation. >> >> I also tried boot image of 14.0-CURRENT 20220519 snapshot and boot >> hangs up just same as 13.1-RELEASE. >> >> --- >> Yasuhiro Kimura >> > > I submitted the problem to Bugzilla. > > Bug 264179 Boot hangs up with Alderlake's intel GbE NIC > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179 Recently some commits that change files under sys/dev/e1000 are made to main branch. So I built install image from c8f47b28827c of main and tried booting my home server with it. Then system boots without hang up but onboard Intel GbE NIC failed to be detected with following message. ---------------------------------------------------------------------- em1: mem 0x42300000-0x4231ffff at device 31.6 on pci0 em1: Setup of Shared code failed. error -1 em1: IFDI_ATTACH_PRE failed 6 device_attach: em1 attach returned 6 ---------------------------------------------------------------------- --- Yasuhiro Kimura From nobody Thu Feb 9 19:04:58 2023 X-Original-To: freebsd-stable@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 4PCRBt39TKz3nPQ0 for ; Thu, 9 Feb 2023 19:05:10 +0000 (UTC) (envelope-from SRS0=v8rL=6F=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 4PCRBs2j5cz3MZW for ; Thu, 9 Feb 2023 19:05:09 +0000 (UTC) (envelope-from SRS0=v8rL=6F=quip.cz=000.fbsd@elsa.codelab.cz) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of "SRS0=v8rL=6F=quip.cz=000.fbsd@elsa.codelab.cz" has no SPF policy when checking 94.124.105.4) smtp.mailfrom="SRS0=v8rL=6F=quip.cz=000.fbsd@elsa.codelab.cz"; dmarc=none Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5B81A28482 for ; Thu, 9 Feb 2023 20:05:01 +0100 (CET) Received: from [192.168.145.50] (ip-89-177-27-225.bb.vodafone.cz [89.177.27.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 005BA28411 for ; Thu, 9 Feb 2023 20:04:58 +0100 (CET) Message-ID: <4caf465e-4514-6dbb-1a65-8a27b9b1537e@quip.cz> Date: Thu, 9 Feb 2023 20:04:58 +0100 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 To: freebsd-stable@freebsd.org Content-Language: cs-Cestina, en-US From: Miroslav Lachman <000.fbsd@quip.cz> Subject: sym vs ncr driver for emulated LSI 53C895A Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.80 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=v8rL=6F=quip.cz=000.fbsd@elsa.codelab.cz]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[quip.cz]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=v8rL=6F=quip.cz=000.fbsd@elsa.codelab.cz]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4PCRBs2j5cz3MZW X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N I have FreeBSD 12.4 virtual machine installed inside KVM. This machine has 2 disks. One is 30GB connected as VirtIO vtbd0. There is installed system. The second is 20TB iSCSI connected to KVM and should be available inside VM as SCSI disk da0 but it is not. I see following errors in a log sym0:1: message c sent on bad reselection. sym0:1:control msgout: 80 6. (probe1:sym0:0:1:0): INQUIRY. CDB: 12 00 00 00 24 00 (probe1:sym0:0:1:0): CAM status: Command timeout (probe1:sym0:0:1:0): Retrying command, 3 more tries remain sym0:1: message c sent on bad reselection. sym0:1:control msgout: 80 6. (probe1:sym0:0:1:0): INQUIRY. CDB: 12 00 00 00 24 00 (probe1:sym0:0:1:0): CAM status: Command timeout (probe1:sym0:0:1:0): Retrying command, 2 more tries remain sym0:1: message c sent on bad reselection. sym0:1:control msgout: 80 6. (probe1:sym0:0:1:0): INQUIRY. CDB: 12 00 00 00 24 00 (probe1:sym0:0:1:0): CAM status: Command timeout (probe1:sym0:0:1:0): Retrying command, 1 more tries remain sym0:1: message c sent on bad reselection. sym0:1:control msgout: 80 6. (probe1:sym0:0:1:0): INQUIRY. CDB: 12 00 00 00 24 00 (probe1:sym0:0:1:0): CAM status: Command timeout (probe1:sym0:0:1:0): Retrying command, 0 more tries remain sym0:1: message c sent on bad reselection. sym0:1:control msgout: 80 6. (probe1:sym0:0:1:0): INQUIRY. CDB: 12 00 00 00 24 00 (probe1:sym0:0:1:0): CAM status: Command timeout (probe1:sym0:0:1:0): Error 5, Retries exhausted Relevant part of the dmesg: virtio_pci0: port 0xc200-0xc27f mem 0xfc0b7000-0xfc0b7fff,0xfebf8000-0xfebfbfff irq 10 at device 5.0 on pci0 vtblk0: on virtio_pci0 vtblk0: 30720MB (62914560 512 byte sectors) virtio_pci1: port 0xc2c0-0xc2ff mem 0xfebfc000-0xfebfffff irq 10 at device 6.0 on pci0 vtballoon0: on virtio_pci1 sym0: <895a> port 0xc000-0xc0ff mem 0xfc0b8000-0xfc0b83ff,0xfc0b2000-0xfc0b3fff irq 11 at device 7.0 on pci0 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym1: <895a> port 0xc100-0xc1ff mem 0xfc0b9000-0xfc0b93ff,0xfc0b4000-0xfc0b5fff irq 11 at device 8.0 on pci0 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking ahci0: port 0xc380-0xc39f mem 0xfc0ba000-0xfc0bafff irq 10 at device 9.0 on pci0 ahci0: AHCI v1.00 with 6 1.5Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ahci1: port 0xc3a0-0xc3bf mem 0xfc0bb000-0xfc0bbfff irq 10 at device 10.0 on pci0 ahci1: AHCI v1.00 with 6 1.5Gbps ports, Port Multiplier not supported ahcich6: at channel 0 on ahci1 ahcich7: at channel 1 on ahci1 ahcich8: at channel 2 on ahci1 ahcich9: at channel 3 on ahci1 ahcich10: at channel 4 on ahci1 ahcich11: at channel 5 on ahci1 The controller is listed by pciconf # pciconf -lv | grep -A4 sym sym0@pci0:0:7:0: class=0x010000 card=0x10000000 chip=0x00121000 rev=0x00 hdr=0x00 vendor = 'Broadcom / LSI' device = '53c895a' class = mass storage subclass = SCSI sym1@pci0:0:8:0: class=0x010000 card=0x10000000 chip=0x00121000 rev=0x00 hdr=0x00 vendor = 'Broadcom / LSI' device = '53c895a' class = mass storage subclass = SCSI I tried to search what should be the right driver for LSI 53c895a but I am a bit confused. sym(4) is attached on boot, but it is also listed on hardware notes and man page for ncr(4) driver https://www.freebsd.org/releases/12.4R/hardware/ I tried to kldload ncr but can't load ncr: No such file or directory. Should ncr be built separately? (the system is running 12.4 with GENERIC kernel) And how can I configure it to use ncr instead of sym? Or are there any other way to make FreeBSD guest happy in KVM host? (I am not controlling the KVM host, I don't know the exact configuration of it) Kind regards Miroslav Lachman From nobody Fri Feb 10 07:47:29 2023 X-Original-To: freebsd-stable@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 4PCm6f5lghz3p8Jp for ; Fri, 10 Feb 2023 07:47:38 +0000 (UTC) (envelope-from Walter.von.Entferndt@posteo.net) Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PCm6d5g9Qz3Gw6 for ; Fri, 10 Feb 2023 07:47:37 +0000 (UTC) (envelope-from Walter.von.Entferndt@posteo.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=posteo.net header.s=2017 header.b=lasOAKiE; spf=pass (mx1.freebsd.org: domain of Walter.von.Entferndt@posteo.net designates 185.67.36.66 as permitted sender) smtp.mailfrom=Walter.von.Entferndt@posteo.net; dmarc=pass (policy=none) header.from=posteo.net Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id DEC47240531 for ; Fri, 10 Feb 2023 08:47:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1676015256; bh=frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY=; h=From:To:Subject:Date:From; b=lasOAKiExUB/26lw6MVTyla9LQCeAFk4QE4jPR54LCWQU8BMkOfIZABvOXy3vEYDp REvkX3nzIzjSDsPaJq5hQs7jkuZ4HHRmV4fxA16JKAY/6E42T3Kx1CxD1rH58MJ7Nx Ia/0f+FaMzhTDkENG50GVV3Kz1vI/Wn9m1cRVXbse50RcxUesGkLbUdUXAutM+KxHY IbAGqrbWtuhxuFHzisZdz1BPbTwuw1qwHwmoEx1UqW2/rwrynDf0ixCt6IGFc9yLAL wpwtqZ+SuKqRWeTO/oOYZCUfFmv+m0LGKxqALoWorhfjbjRKMxaF1ahAgFlxE55Pou OYIh+hVEaIX4A== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4PCm6c3QTPz9rxG for ; Fri, 10 Feb 2023 08:47:36 +0100 (CET) From: Walter von Entferndt To: freebsd-stable@freebsd.org Subject: unsubscribe Date: Fri, 10 Feb 2023 07:47:29 +0000 Message-ID: <3338367.oyIqbj9WPF@t450s.local.lan> X-Face: #$[hC+4[4W*mS3hB&izisyT_#E]^Aq+7Isv`2Tu5q*1~jR@&['74B>Ibyrk]GTJ!j$ NjX=#L2#k2X7OnaaRM_Pd5`>`8OJ3;+I2 References: <4P6jMT09pGz3cxmx@mlmmj.nyi.freebsd.org> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spamd-Result: default: False [-4.20 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[posteo.net,none]; CTE_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:185.67.36.0/23]; RCVD_IN_DNSWL_MED(-0.20)[185.67.36.66:from]; R_DKIM_ALLOW(-0.20)[posteo.net:s=2017]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; ASN(0.00)[asn:8495, ipnet:185.67.36.0/23, country:DE]; DKIM_TRACE(0.00)[posteo.net:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.67.36.66:from] X-Rspamd-Queue-Id: 4PCm6d5g9Qz3Gw6 X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N