From: Samuel Sieb <samuel@sieb.net>
To: Joerg Roedel <joro@8bytes.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: AMD IOMMU causing filesystem corruption
Date: Wed, 26 Apr 2017 14:31:40 -0700 [thread overview]
Message-ID: <c6d33a95-1bfe-1c33-e0ed-95060ab7fcc7@sieb.net> (raw)
In-Reply-To: <20170426101405.GJ7266@8bytes.org>
On 04/26/2017 03:14 AM, Joerg Roedel wrote:
> On Tue, Apr 25, 2017 at 10:55:24AM -0700, Samuel Sieb wrote:
>> On 04/07/2017 03:27 AM, Joerg Roedel wrote:
>>> Also, please try the attached debug-diff on your kernel. It completly
>>> disables the use of ATS in the amd-iommu driver.
>>>
>> I applied this patch to 4.11.0 rc8 and then stress tested the laptop
>> with another kernel build while running graphical applications and
>> there appears to be no damage to the filesystem. Is there any way
>> to determine if ATS is enabled or disabled?
>
> Great, thanks for testing the patch. The lspci tool should be able to
> tell you whether the ATS capability is enabled on the GPU. With a
> 'lspci -vvv -s <GPUDEV>" should give you that info.
>
This test was done with the patch that always disables ATS. Which is
the current patch to selectively disable it? The last patch I tried
didn't seem to work.
next prev parent reply other threads:[~2017-04-26 21:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 20:38 Samuel Sieb
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 [this message]
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=c6d33a95-1bfe-1c33-e0ed-95060ab7fcc7@sieb.net \
--to=samuel@sieb.net \
--cc=joro@8bytes.org \
--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
all inboxes | Powered by JetHome®