Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Feb 2022 03:29:11 +0000
From:      "Chen, Alvin W" <Weike.Chen@Dell.com>
To:        "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt due to P-Core&E-Core
Message-ID:   <PH0PR19MB49388A4BC14B16FCEA5F742D9E359@PH0PR19MB4938.namprd19.prod.outlook.com>
In-Reply-To:  <PH0PR19MB4938BC329E905FA3BFC93EBB9E359@PH0PR19MB4938.namprd19.prod.outlook.com>
References:   <PH0PR19MB4938FC8E343F7AA23F66C7439E349@PH0PR19MB4938.namprd19.prod.outlook.com> <PH0PR19MB4938BC329E905FA3BFC93EBB9E359@PH0PR19MB4938.namprd19.prod.outlook.com>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
Hi Guys,
Any updates to support Intel P-core + E-core?
I have filed a bug: PR 261169<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261169>, but no updates.
Does anybody know the progress?

For Intel Adler Lake P core + E core processor (i7-12700T), copying files to FAT32 partition, the file corrupted (50%), but ZFS is fine. After disabling E core in the code by restrict the max cpu number, this issue is gone. And No E core processor has no such issue, like i7-12400.

HW ENV:
CPU: Intel AlderLake 12th Gen i7-12700T
Disk: NVME SSD

There are 3 methods to reproduce this issue:
1. Make FreeBSD 13 USB disk installer, install FreeBSD with UFS, and select install source and ports, the txz package checking will be failed.

2. Boot to shell by USB disk installer, and mount a FAT32 partition (on SSD), and copy a 300MB file to the FAT32, compare the sha256 checksums for the source file and the dst file, the checksum are different (50%). Or if there is a 300MB file in FAT32 partition, mount the partition, and for the first time check the sha256 value by running 'sha256 file.tgz', the checksum is wrong, but the second time, the checksum is correct.

3. Install FreeBSD 13 with ZFS, and it can work well. And boot into FreeBSD, disable swap, and format the SWAP partition to FAT32. Do the testing as above.



Regards,
Alvin Chen
Dell | Comercial Client Group
office +86-10-82862506, fax +86-10-82861554, Dell Lync 8672506 weike_chen@dell.com<mailto:weike_chen@dell.com>



Internal Use - Confidential

[-- Attachment #2 --]
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">;
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.msipfooter90245289, li.msipfooter90245289, div.msipfooter90245289
	{mso-style-name:msipfooter90245289;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle20
	{mso-style-type:personal-compose;
	font-family:"Segoe UI",sans-serif;
	color:#141414;
	background:white;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:#141414;background:white">Hi Guys,</span><span style="font-size:12.0pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:#141414"><br>
<span style="background:white">Any updates to support Intel P-core + E-core?</span><br>
<span style="background:white">I have filed a bug:&nbsp;</span></span><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261169" target="_blank" title="Problem Report 261169"><tt><span style="font-size:10.0pt;color:#007A00;background:white">PR 261169</span></tt></a><span style="font-size:12.0pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:#141414;background:white">,
 but no updates.</span><span style="font-size:12.0pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:#141414"><br>
<span style="background:white">Does anybody know the progress?</span><br>
<br>
<span style="background:white">For Intel Adler Lake P core + E core processor (i7-12700T), copying files to FAT32 partition, the file corrupted (50%), but ZFS is fine. After disabling E core in the code by restrict the max cpu number, this issue is gone. And
 No E core processor has no such issue, like i7-12400.</span><br>
<br>
<span style="background:white">HW ENV:</span><br>
<span style="background:white">CPU: Intel AlderLake 12th Gen i7-12700T</span><br>
<span style="background:white">Disk: NVME SSD</span><br>
<br>
<span style="background:white">There are 3 methods to reproduce this issue:</span><br>
<span style="background:white">1. Make FreeBSD 13 USB disk installer, install FreeBSD with UFS, and select install source and ports, the txz package checking will be failed.</span><br>
<br>
<span style="background:white">2. Boot to shell by USB disk installer, and mount a FAT32 partition (on SSD), and copy a 300MB file to the FAT32, compare the sha256 checksums for the source file and the dst file, the checksum are different (50%). Or if there
 is a 300MB file in FAT32 partition, mount the partition, and for the first time check the sha256 value by running 'sha256 file.tgz', the checksum is wrong, but the second time, the checksum is correct.</span><br>
<br>
<span style="background:white">3. Install FreeBSD 13 with ZFS, and it can work well. And boot into FreeBSD, disable swap, and format the SWAP partition to FAT32. Do the testing as above.</span></span><o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Alvin Chen<o:p></o:p></p>
<p class="MsoNormal">Dell | Comercial Client Group<o:p></o:p></p>
<p class="MsoNormal">office +86-10-82862506, fax +86-10-82861554, Dell Lync 8672506
<a href="mailto:weike_chen@dell.com">weike_chen@dell.com</a><o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="msipfooter90245289" style="margin:0cm"><span style="font-size:7.0pt;color:#737373">Internal Use - Confidential</span><o:p></o:p></p>
</div>
</body>
</html>
help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PH0PR19MB49388A4BC14B16FCEA5F742D9E359>