Bug 195051 - massive file system corruption with iommu
Summary: massive file system corruption with iommu
Status: NEW
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 blocking
Assignee: io_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-26 21:53 UTC by Samuel Sieb
Modified: 2018-10-17 03:00 UTC (History)
0 users

See Also:
Kernel Version: 4.9.13
Subsystem:
Regression: No
Bisected commit-id:


Attachments
boot log with iommu enabled (149.00 KB, text/plain)
2017-03-26 21:54 UTC, Samuel Sieb
Details
boot log with iommu disabled (131.31 KB, text/plain)
2017-03-26 21:55 UTC, Samuel Sieb
Details

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.

Note You need to log in before you can comment on or make changes to this bug.