Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
fio with --verify=crc32c will be failed with "fio: file hash not empty on exit" on aarch64
Version-Release number of selected component (if applicable):
5.13.0-0.rc3.25.el9.aarch64
fio-3.27-2.el9.aarch64
How reproducible:
100% on rdma-apollo0-00.lab.bos.redhat.com/rdma-apollo0-01.lab.bos.redhat.com
Steps to Reproduce:
[root@rdma-apollo0-00 ~]# fio --output=/root/fio_perf --output-format=terse --terse-version=4 --group_reporting=1 --name=verify --rw=randwrite --direct=1 --ioengine=libaio --bs=4k --iodepth=16 --verify=crc32c --size=950m --filename=/root/testfile
fio: pid=13286, got signal=4
fio: file hash not empty on exit
Actual results:
Expected results:
Additional info:
I've also filed this issue to fio upstream:
https://github.com/axboe/fio/issues/1239
Signal 4 is an illegal instruction, not sure whether it's FUJITSU/A64FX related, I've tried another aarch64 platform "qualcomm-amberwing-rep-05.khw4.lab.eng.bos.redhat.com", but cannot reproduce it.
Here is the cpufino:
[root@rdma-apollo0-00 ~]# lscpu
Architecture: aarch64
CPU op-mode(s): 64-bit
Byte Order: Little Endian
CPU(s): 48
On-line CPU(s) list: 0-47
Vendor ID: FUJITSU
BIOS Vendor ID: FUJITSU
Model name: A64FX
BIOS Model name: 461F0010
Model: 0
Thread(s) per core: 1
Core(s) per cluster: 12
Socket(s): 1
Cluster(s): 4
Stepping: 0x1
BogoMIPS: 200.00
Flags: fp asimd evtstrm sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm fcma dcpop sve
NUMA:
NUMA node(s): 4
NUMA node0 CPU(s): 0-11
NUMA node1 CPU(s): 12-23
NUMA node2 CPU(s): 24-35
NUMA node3 CPU(s): 36-47
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Mitigation; PTI
Spec store bypass: Vulnerable
Spectre v1: Mitigation; __user pointer sanitization
Spectre v2: Vulnerable
Srbds: Not affected
Tsx async abort: Not affected
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (fio bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2220