From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752400AbdDCUqW (ORCPT ); Mon, 3 Apr 2017 16:46:22 -0400 Received: from smtp-out-no.shaw.ca ([64.59.134.13]:51897 "EHLO smtp-out-no.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751210AbdDCUqV (ORCPT ); Mon, 3 Apr 2017 16:46:21 -0400 X-Greylist: delayed 487 seconds by postgrey-1.27 at vger.kernel.org; Mon, 03 Apr 2017 16:46:20 EDT X-Authority-Analysis: v=2.2 cv=KeeiiUQD c=1 sm=1 tr=0 a=JyAt4amVi6RK7kaaDbhaBA==:117 a=JyAt4amVi6RK7kaaDbhaBA==:17 a=IkcTkHD0fZMA:10 a=AzvcPWV-tVgA:10 a=VwQbUJbxAAAA:8 a=RpPu6C3NN_7_bL3Un9QA:9 a=QEXdDO2ut3YA:10 a=AjGcO6oz07-iQ99wixmX:22 To: linux-kernel@vger.kernel.org From: Samuel Sieb Subject: AMD IOMMU causing filesystem corruption Message-ID: <5ea65f55-e5eb-11a5-14ab-e721d2f95ed6@sieb.net> Date: Mon, 3 Apr 2017 13:38:08 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfK/8h2YbDCgpR8FamfQ5KirSaYGL/sOSedaDUy1m9FUHMC0fYI075jpaqiNR+Z9sV0zJ66F8HW6sQ/j2nve5/P97GkNQozCEopd75wwwacELmgxL66Ik iud2vIMbAqQ0e3ecM8nmb2cV7UpebBNYI5GRhzda5Cj1It5L2hphb52m Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.