Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1631345

Re: AMD IOMMU causing filesystem corruption

From Joerg Roedel <joro@8bytes.org>
Newsgroups linux.kernel
Subject Re: AMD IOMMU causing filesystem corruption
Date 2017-04-26 12:20 +0200
Message-ID <tAsdb-UH-3@gated-at.bofh.it> (permalink)
References (3 earlier) <tsqUV-1Er-7@gated-at.bofh.it> <tsrei-1N1-13@gated-at.bofh.it> <tszvc-7i4-23@gated-at.bofh.it> <ttzjs-5Oz-25@gated-at.bofh.it> <tAcUO-7ME-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

Hi Samuel,

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.


	Joerg

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: AMD IOMMU causing filesystem corruption Samuel Sieb <samuel@sieb.net> - 2017-04-25 20:00 +0200
  Re: AMD IOMMU causing filesystem corruption Joerg Roedel <joro@8bytes.org> - 2017-04-26 12:20 +0200
    Re: AMD IOMMU causing filesystem corruption Samuel Sieb <samuel@sieb.net> - 2017-04-26 23:40 +0200
      Re: AMD IOMMU causing filesystem corruption Joerg Roedel <joro@8bytes.org> - 2017-04-26 23:50 +0200
        Re: AMD IOMMU causing filesystem corruption Samuel Sieb <samuel@sieb.net> - 2017-04-27 21:40 +0200

csiph-web