nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed

[Keith Busch]

On Fri, Dec 16, 2022 at 07:39:53AM +0100, Christoph Hellwig wrote:
> On Fri, Dec 16, 2022 at 07:30:55AM +0900, J. Hart wrote:
> > I've tried the obvious ones and that didn't help either.  I guess I'll have 
> > to give up on it and return it as defective.  I'll go back to normal 
> > operation and to try and find a controller/device combination that works 
> > with the linux driver if there are any.
> 
> So on the hand I agree with Keith that the device seems really broken.
> On the other hand the fact that source file system on another device
> sees corruption even with the iommu enabled is something that looks
> scrary.  Even if ultimatively caused by the device somehow, that seems
> like the kernel is part of the corruption.  And I have absolutely no
> idea how.  A KASAN run on the device might be helpful, but I'm also
> reluctant to ask a reported to run more reproducers and something that
> corrupts his data.

Oh, I assumed the source was a different partition on the same flakey
looking device. If not, yeah, that's pretty concerning.

How do you know enabling Intel IOMMU in the kernel config does anything
here? I didn't see anything confirming the kernel was actually using it.
I know this CPU model has VT-d capabilities, but I believe the platform
may disable it in BIOS.