Re: AMD IOMMU causing filesystem corruption

2017-04-27 Thread Samuel Sieb
On 04/26/2017 02:43 PM, Joerg Roedel wrote: On Wed, Apr 26, 2017 at 02:31:40PM -0700, Samuel Sieb wrote: 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. Its [PATCH v2] PCI:

Re: AMD IOMMU causing filesystem corruption

2017-04-27 Thread Samuel Sieb
On 04/26/2017 02:43 PM, Joerg Roedel wrote: On Wed, Apr 26, 2017 at 02:31:40PM -0700, Samuel Sieb wrote: 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. Its [PATCH v2] PCI:

Re: AMD IOMMU causing filesystem corruption

2017-04-26 Thread Joerg Roedel
On Wed, Apr 26, 2017 at 02:31:40PM -0700, Samuel Sieb wrote: > 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. Its [PATCH v2] PCI: Add ATS-disable quirk for AMD Stoney GPUs

Re: AMD IOMMU causing filesystem corruption

2017-04-26 Thread Joerg Roedel
On Wed, Apr 26, 2017 at 02:31:40PM -0700, Samuel Sieb wrote: > 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. Its [PATCH v2] PCI: Add ATS-disable quirk for AMD Stoney GPUs

Re: AMD IOMMU causing filesystem corruption

2017-04-26 Thread Samuel Sieb
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

Re: AMD IOMMU causing filesystem corruption

2017-04-26 Thread Samuel Sieb
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

Re: AMD IOMMU causing filesystem corruption

2017-04-26 Thread Joerg Roedel
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

Re: AMD IOMMU causing filesystem corruption

2017-04-26 Thread Joerg Roedel
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

Re: AMD IOMMU causing filesystem corruption

2017-04-25 Thread Samuel Sieb
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

Re: AMD IOMMU causing filesystem corruption

2017-04-25 Thread Samuel Sieb
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

Re: AMD IOMMU causing filesystem corruption

2017-04-08 Thread Samuel Sieb
On 04/07/2017 03:22 AM, Joerg Roedel wrote: Can you please send me output of 'lspci -nv' on your system? I have to figure out how to rebuild the system and find the time to do it before I can test that patch, but here's the lspci output: 00:00.0 0600: 1022:1576 Subsystem: 1025:1099

Re: AMD IOMMU causing filesystem corruption

2017-04-08 Thread Samuel Sieb
On 04/07/2017 03:22 AM, Joerg Roedel wrote: Can you please send me output of 'lspci -nv' on your system? I have to figure out how to rebuild the system and find the time to do it before I can test that patch, but here's the lspci output: 00:00.0 0600: 1022:1576 Subsystem: 1025:1099

Re: AMD IOMMU causing filesystem corruption

2017-04-07 Thread Joerg Roedel
On Tue, Apr 04, 2017 at 09:29:37AM -0700, Samuel Sieb wrote: > That's what I did. While running with iommu=off, I compiled and > installed a 4.11rc kernel with the patch. I rebooted to use that > kernel and then compiled and installed a 4.10 kernel with that patch > and another unrelated patch.

Re: AMD IOMMU causing filesystem corruption

2017-04-07 Thread Joerg Roedel
On Tue, Apr 04, 2017 at 09:29:37AM -0700, Samuel Sieb wrote: > That's what I did. While running with iommu=off, I compiled and > installed a 4.11rc kernel with the patch. I rebooted to use that > kernel and then compiled and installed a 4.10 kernel with that patch > and another unrelated patch.

Re: AMD IOMMU causing filesystem corruption

2017-04-07 Thread Joerg Roedel
On Tue, Apr 04, 2017 at 09:29:37AM -0700, Samuel Sieb wrote: > That's what I did. While running with iommu=off, I compiled and > installed a 4.11rc kernel with the patch. I rebooted to use that > kernel and then compiled and installed a 4.10 kernel with that patch > and another unrelated patch.

Re: AMD IOMMU causing filesystem corruption

2017-04-07 Thread Joerg Roedel
On Tue, Apr 04, 2017 at 09:29:37AM -0700, Samuel Sieb wrote: > That's what I did. While running with iommu=off, I compiled and > installed a 4.11rc kernel with the patch. I rebooted to use that > kernel and then compiled and installed a 4.10 kernel with that patch > and another unrelated patch.

Re: AMD IOMMU causing filesystem corruption

2017-04-04 Thread Samuel Sieb
On 04/04/2017 12:32 AM, Joerg Roedel wrote: On Tue, Apr 04, 2017 at 12:11:31AM -0700, Samuel Sieb wrote: Unfortunately, that turned out to be a bit premature. After compiling a kernel on it remotely over ssh (not interacting with the logged in desktop), a reboot failed with endless

Re: AMD IOMMU causing filesystem corruption

2017-04-04 Thread Samuel Sieb
On 04/04/2017 12:32 AM, Joerg Roedel wrote: On Tue, Apr 04, 2017 at 12:11:31AM -0700, Samuel Sieb wrote: Unfortunately, that turned out to be a bit premature. After compiling a kernel on it remotely over ssh (not interacting with the logged in desktop), a reboot failed with endless

Re: AMD IOMMU causing filesystem corruption

2017-04-04 Thread Joerg Roedel
On Tue, Apr 04, 2017 at 12:11:31AM -0700, Samuel Sieb wrote: > Unfortunately, that turned out to be a bit premature. After > compiling a kernel on it remotely over ssh (not interacting with the > logged in desktop), a reboot failed with endless completion-wait > loop timeout messages and after a

Re: AMD IOMMU causing filesystem corruption

2017-04-04 Thread Joerg Roedel
On Tue, Apr 04, 2017 at 12:11:31AM -0700, Samuel Sieb wrote: > Unfortunately, that turned out to be a bit premature. After > compiling a kernel on it remotely over ssh (not interacting with the > logged in desktop), a reboot failed with endless completion-wait > loop timeout messages and after a

Re: AMD IOMMU causing filesystem corruption

2017-04-04 Thread Samuel Sieb
On 04/03/2017 08:37 PM, Samuel Sieb wrote: On 04/03/2017 02:39 PM, Joerg Roedel wrote: You have a system based on the AMD Stoney platform, on which the PCI-ATS feature of the GPU is broken, as we recently found out. Can you please test whether the attached patch fixes the issue on your

Re: AMD IOMMU causing filesystem corruption

2017-04-04 Thread Samuel Sieb
On 04/03/2017 08:37 PM, Samuel Sieb wrote: On 04/03/2017 02:39 PM, Joerg Roedel wrote: You have a system based on the AMD Stoney platform, on which the PCI-ATS feature of the GPU is broken, as we recently found out. Can you please test whether the attached patch fixes the issue on your

Re: AMD IOMMU causing filesystem corruption

2017-04-03 Thread Samuel Sieb
On 04/03/2017 02:39 PM, Joerg Roedel wrote: You have a system based on the AMD Stoney platform, on which the PCI-ATS feature of the GPU is broken, as we recently found out. Can you please test whether the attached patch fixes the issue on your machine? Yes, that works, thank you! Now I'm

Re: AMD IOMMU causing filesystem corruption

2017-04-03 Thread Samuel Sieb
On 04/03/2017 02:39 PM, Joerg Roedel wrote: You have a system based on the AMD Stoney platform, on which the PCI-ATS feature of the GPU is broken, as we recently found out. Can you please test whether the attached patch fixes the issue on your machine? Yes, that works, thank you! Now I'm

Re: AMD IOMMU causing filesystem corruption

2017-04-03 Thread Joerg Roedel
Hi Samuel, On Mon, Apr 03, 2017 at 01:38:08PM -0700, Samuel Sieb wrote: > 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

Re: AMD IOMMU causing filesystem corruption

2017-04-03 Thread Joerg Roedel
Hi Samuel, On Mon, Apr 03, 2017 at 01:38:08PM -0700, Samuel Sieb wrote: > 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

AMD IOMMU causing filesystem corruption

2017-04-03 Thread Samuel Sieb
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

AMD IOMMU causing filesystem corruption

2017-04-03 Thread Samuel Sieb
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