From: Samuel Sieb <samuel@sieb.net>
To: linux-kernel@vger.kernel.org
Subject: AMD IOMMU causing filesystem corruption
Date: Mon, 3 Apr 2017 13:38:08 -0700 [thread overview]
Message-ID: <5ea65f55-e5eb-11a5-14ab-e721d2f95ed6@sieb.net> (raw)
I filed a bug in bugzilla, but I wasn't sure what category to put it in,
so I suspect I ended up picking one that doesn't get looked at much.
https://bugzilla.kernel.org/show_bug.cgi?id=195051
The issue is that on a specific Acer laptop with a dual-core A9, if I
don't disable the IOMMU using iommu=off, it has immediate and rapidly
fatal filesystem corruption by the time a user logs into the desktop.
What led me to try that was at one point I noticed an error message
about the iommu in the logs. However, I did not have a chance to save
that due to the corruption obliterating the log files.
next reply other threads:[~2017-04-03 20:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 20:38 Samuel Sieb [this message]
2017-04-03 21:39 ` Joerg Roedel
2017-04-04 3:37 ` Samuel Sieb
2017-04-04 7:11 ` Samuel Sieb
2017-04-04 7:32 ` Joerg Roedel
2017-04-04 16:29 ` Samuel Sieb
2017-04-07 10:22 ` Joerg Roedel
2017-04-08 6:49 ` Samuel Sieb
2017-04-07 10:27 ` Joerg Roedel
2017-04-25 17:55 ` Samuel Sieb
2017-04-26 10:14 ` Joerg Roedel
2017-04-26 21:31 ` Samuel Sieb
2017-04-26 21:43 ` Joerg Roedel
2017-04-27 19:32 ` Samuel Sieb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ea65f55-e5eb-11a5-14ab-e721d2f95ed6@sieb.net \
--to=samuel@sieb.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome