mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Sieb <samuel@sieb.net>
To: Joerg Roedel <joro@8bytes.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD IOMMU causing filesystem corruption
Date: Tue, 4 Apr 2017 00:11:31 -0700	[thread overview]
Message-ID: <935473d9-e75b-c019-0dde-063855067858@sieb.net> (raw)
In-Reply-To: <32afc9d1-a2db-f9dc-bbe0-d894967dc8ad@sieb.net>

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.

  reply	other threads:[~2017-04-04  7:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 20:38 Samuel Sieb
2017-04-03 21:39 ` Joerg Roedel
2017-04-04  3:37   ` Samuel Sieb
2017-04-04  7:11     ` Samuel Sieb [this message]
2017-04-04  7:32       ` Joerg Roedel
2017-04-04 16:29         ` Samuel Sieb
2017-04-07 10:22           ` Joerg Roedel
2017-04-08  6:49             ` Samuel Sieb
2017-04-07 10:27           ` Joerg Roedel
2017-04-25 17:55             ` Samuel Sieb
2017-04-26 10:14               ` Joerg Roedel
2017-04-26 21:31                 ` Samuel Sieb
2017-04-26 21:43                   ` Joerg Roedel
2017-04-27 19:32                     ` Samuel Sieb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=935473d9-e75b-c019-0dde-063855067858@sieb.net \
    --to=samuel@sieb.net \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®