[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] Intel Alder Lake: data corruption with Read&Write files to FAT32 or UFS"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] Intel Alder Lake: data corruption with Read&Write files to FAT32 or UFS"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261169] Intel Alder Lake: data corruption with Read&Write files to FAT32 or UFS"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 13 Jan 2022 08:55:47 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261169
Bug ID: 261169
Summary: [Intel AlderLake]Read&Write files to FAT32 or UFS
partition cause data corrupt
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: vico13.chen@gmail.com
For Intel Adler Lake P core + E core processor (i7-12700T), copying files to
FAT32 partition, the file corrutped (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 parition (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 parition, 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.
--
You are receiving this mail because:
You are the assignee for the bug.