Kernel Call Traces while running fio version 3.38

[Mandeep97]

Facing call trace issues with verifying eMMC performances using fio version 3.38 with the kernel version 6.1.110, saying "fio Not tainted 6.1.110" .

I am seeking help to resolve the issues.

Regards,
Mandeep

[sitsofe]

@Mandeep97: Please can you include ALL the information https://github.com/axboe/fio/blob/master/.github/ISSUE_TEMPLATE/bug-report.md and follow the instructions in

fio/REPORTING-BUGS

Lines 27 to 40 in d1ebbdd

	...via GitHub issues
	====================
	Please create an issue in the GitHub issue tracker
	(https://github.com/axboe/fio/issues ) but observe the following:
	a) If you are asking a question on how to do something ("How do I/Why is?")
	please send it to the mailing list and not GitHub issues. The fio project
	uses GitHub issues for reproducible bugs/enhancement requests.
	b) Please reproduce your bug using the latest fio listed on
	https://github.com/axboe/fio/releases (see the Source and Building sections
	of the README for how to build fio from source).
	c) Include all of the information requested in the mailing list section above
	(description, environment, version, reproduction steps and all job parameters).

.

Additionally we will likely also need a symbolised backtrace of the segfault . Run fio under gdb and then do thread apply all bt to get this after the segfault occurs.