Bug 195051

Summary:	massive file system corruption with iommu
Product:	IO/Storage	Reporter:	Samuel Sieb (samuel-kbugs)
Component:	Other	Assignee:	io_other
Status:	NEW ---
Severity:	blocking
Priority:	P1
Hardware:	x86-64
OS:	Linux
Kernel Version:	4.9.13	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	boot log with iommu enabled boot log with iommu disabled

Description Samuel Sieb 2017-03-26 21:53:21 UTC

On an Acer Aspire E5-523, if I don't add iommu=off to the kernel command line, the file systems rapidly (within minutes) get corrupted and usually the system locks up after a short time.  After adding iommu=off, the wifi doesn't work, but otherwise the system seems to be stable and I haven't found any filesystem corruption.

The initial install is done with kernel 4.5.5 and over several tries, I thought there was no problem, but this last time, the EFI fat partition was damaged.  However, the entire Fedora 24 desktop with lots of applications is installed successfully.  The install process installs the latest kernel available which at this point is 4.9.13 and booting with that one causes the immediate corruption by the time the user is logged in.  I will attach logs from both cases.

Comment 1 Samuel Sieb 2017-03-26 21:54:59 UTC

Created attachment 255559 [details]
boot log with iommu enabled

Comment 2 Samuel Sieb 2017-03-26 21:55:23 UTC

Created attachment 255561 [details]
boot log with iommu disabled

Comment 3 Samuel Sieb 2017-04-04 03:54:57 UTC

The patch from https://lkml.org/lkml/2017/4/3/734 fixed this.

Comment 4 Samuel Sieb 2018-10-17 03:00:59 UTC

This was fixed, but I'm not sure which resolution to choose.