Messages in this thread | | | Date | Tue, 4 Apr 2017 09:32:15 +0200 | From | Joerg Roedel <> | Subject | Re: AMD IOMMU causing filesystem corruption |
| |
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
| |