From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752842AbdDDHcT (ORCPT ); Tue, 4 Apr 2017 03:32:19 -0400 Received: from 8bytes.org ([81.169.241.247]:59938 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751101AbdDDHcR (ORCPT ); Tue, 4 Apr 2017 03:32:17 -0400 Date: Tue, 4 Apr 2017 09:32:15 +0200 From: Joerg Roedel To: Samuel Sieb Cc: linux-kernel@vger.kernel.org Subject: Re: AMD IOMMU causing filesystem corruption Message-ID: <20170404073215.GS7266@8bytes.org> References: <5ea65f55-e5eb-11a5-14ab-e721d2f95ed6@sieb.net> <20170403213909.GR7266@8bytes.org> <32afc9d1-a2db-f9dc-bbe0-d894967dc8ad@sieb.net> <935473d9-e75b-c019-0dde-063855067858@sieb.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <935473d9-e75b-c019-0dde-063855067858@sieb.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 force poweroff and restart it > won't boot. The EFI filesystem was even destroyed, probably because > the kernel installation modified a file on there. Yeah, please boot the machine with amd_iommu=off during re-installation and when you install the modified kernel. And then boot into the patches kernel with amd_iommu=on (which is the default). Thanks, Joerg