From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752783AbdDDHLi (ORCPT <rfc822;w@1wt.eu>);
        Tue, 4 Apr 2017 03:11:38 -0400
Received: from smtp-out-so.shaw.ca ([64.59.136.139]:37185 "EHLO
        smtp-out-so.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750999AbdDDHLh (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 4 Apr 2017 03:11:37 -0400
X-Authority-Analysis: v=2.2 cv=W+NIbVek c=1 sm=1 tr=0
 a=JyAt4amVi6RK7kaaDbhaBA==:117 a=JyAt4amVi6RK7kaaDbhaBA==:17
 a=IkcTkHD0fZMA:10 a=AzvcPWV-tVgA:10 a=8zr7VqtJ5OpMh_xkgoAA:9 a=QEXdDO2ut3YA:10
Subject: Re: AMD IOMMU causing filesystem corruption
To: Joerg Roedel <joro@8bytes.org>
References: <5ea65f55-e5eb-11a5-14ab-e721d2f95ed6@sieb.net>
 <20170403213909.GR7266@8bytes.org>
 <32afc9d1-a2db-f9dc-bbe0-d894967dc8ad@sieb.net>
Cc: linux-kernel@vger.kernel.org
From: Samuel Sieb <samuel@sieb.net>
Message-ID: <935473d9-e75b-c019-0dde-063855067858@sieb.net>
Date: Tue, 4 Apr 2017 00:11:31 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <32afc9d1-a2db-f9dc-bbe0-d894967dc8ad@sieb.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfE+JCoYQ88Z2qyFBVnkWazBsQU1fB/aMM3gc6YxFEj0hILkaQ9BmMIipt3Zuhx/zDVlZKTS9/SiorrOgJgkBubBNSwxHRZMckGOwjroPr3RdPPqAfCFo
 m+ZJWhBb1RL7/CiVvbD8XfaBXGk4wUCFPROwHhY24K6g9VpEEdJSWTsot7LP/gstHkai30aUzSWo2TrSkmRgvx624nCyfvqKe7g=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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
>> machine?
>>
> Yes, that works, thank you!
>
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 force poweroff and restart it won't boot.  The EFI 
filesystem was even destroyed, probably because the kernel installation 
modified a file on there.