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.

Created attachment 1776086 [details]
abrt report

Description of problem:
SIGILL while running fio with --verify=crc32c

cmdline:        fio --bs=4k --direct=1 --ioengine=libaio --iodepth=16 --verify=crc32c --verify_fatal=1 --do_verify=1 --rw=randwrite --runtime=120 --filename=/dev/mapper/mpathb --name=fio_test --numjobs=1 --verify_backlog=1024

Version-Release number of selected component (if applicable):
fio-3.19-3.el8

How reproducible:
once

Steps to Reproduce:
1. establish local iscsi session, enable multipath
2. run fio command with crc32c verification

Actual results:
SIGILL

Expected results:
no errors

Additional info:
please see the attached abrt report

Sorry for losing track of this.

This is probably known issue https://github.com/axboe/fio/issues/1239 - lots of arm packages got burned by this, it seems.

It's probably fixed in fio-3.29.  I built a test rpm w/ the fix, would you like to give it a re-check?

http://download.eng.bos.redhat.com/brewroot/work/tasks/7416/47987416/fio-3.19-4.el8.test1.aarch64.rpm

Thanks,
-Eric

Hi Eric,
I've tried a few aarch64 systems, but was not able to reproduce this(with shipped fio).

@yizhan Any chance you have a reproducer?

*** Bug 1974306 has been marked as a duplicate of this bug. ***

I've just noticed my last comment is not here. Not sure what happened - apologies!
It went something like this:

The issue is reproducible on HPE Apollo 80 systems (Fujitsu A64FX) by running
# fio --crctest=crc32c

With test package from comment#2, it works as expected.

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:2787