From nobody Tue Feb 22 23:30:28 2022 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 8013919C92DD for ; Tue, 22 Feb 2022 23:30:58 +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 4K3Fm16bv4z3tgS; Tue, 22 Feb 2022 23:30:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 21MNUSxq057841 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 23 Feb 2022 01:30:31 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 21MNUSaS057840; Wed, 23 Feb 2022 01:30:28 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 23 Feb 2022 01:30:28 +0200 From: Konstantin Belousov To: Alexander Motin Cc: Mike Karels , Tomoaki AOKI , "Chen, Alvin W" , freebsd-current@freebsd.org Subject: Re: [Intel AlderLake] Read&Write files to FAT32 or UFS partition cause data corrupt due to P-Core&E-Core Message-ID: References: <5fd2a34e-1135-4237-a028-d4566ff65c69@FreeBSD.org> <20220219115534.7db1b9f199c10894e4280b33@dec.sakura.ne.jp> <7A743668-B5AA-4679-9F56-9A6220CBBC14@karels.net> <59cbcfe2-cd53-69d8-65d6-7a79e656f494@FreeBSD.org> <1f968af1-1c57-9a09-7e01-145a5262e27f@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: <1f968af1-1c57-9a09-7e01-145a5262e27f@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=3.4.5 X-Spam-Checker-Version: SpamAssassin 3.4.5 (2021-03-20) on tom.home X-Rspamd-Queue-Id: 4K3Fm16bv4z3tgS X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [1.55 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.42)[-0.421]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_SPAM_SHORT(1.00)[1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.97)[0.974]; MLMMJ_DEST(0.00)[freebsd-current]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N On Tue, Feb 22, 2022 at 06:23:17PM -0500, Alexander Motin wrote: > On 22.02.2022 17:46, Konstantin Belousov wrote: > > Ok, the next step is to get the CPU feature reports from P- vs. E- cores. > > Patch below should work, with verbose boot. > > Not much difference on that level: > > --- zzzp 2022-02-22 18:18:24.531704000 -0500 > +++ zzze 2022-02-22 18:18:18.631236000 -0500 > @@ -1,22 +1,21 @@ > -CPU 2: 12th Gen Intel(R) Core(TM) i7-12700K (3609.60-MHz K8-class CPU) > +CPU 16: 12th Gen Intel(R) Core(TM) i7-12700K (3609.60-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x90672 Family=0x6 Model=0x97 Stepping=2 > Features=0xbfebfbff > Features2=0x7ffafbff > AMD Features=0x2c100800 > AMD Features2=0x121 > Structured Extended Features=0x239ca7eb > Structured Extended Features2=0x98c027ac > Structured Extended Features3=0xfc1cc410 > XSAVE Features=0xf > IA32_ARCH_CAPS=0xd6b > VT-x: Basic Features=0x3da0500 > Pin-Based Controls=0xff > Primary Processor Controls=0xfffbfffe > Secondary Processor Controls=0xf5d7fff > Exit Controls=0x3da0500 > Entry Controls=0x3da0500 > EPT Features=0x6f34141 > VPID Features=0x10f01 > TSC: P-state invariant, performance statistics > -64-Byte prefetching > -L2 cache: 1280 kbytes, 8-way associative, 64 bytes/line > +L2 cache: 2048 kbytes, 16-way associative, 64 bytes/line > Show me the full verbose dmesg of the boot then. As another blind guess, try to disable pcid, vm.pmap.pcid_enabled=0.