Hi Aristeu, Is it possible to share the sequence of blktest/nvme tests that were executed that resulted in this call trace? Or, was there a specific test case number that results in this call trace frequently? Regards, Justin