From: David Woodhouse <dwmw2@infradead.org>
To: Andy Isaacson <adi@hexapodia.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
iommu@lists.linux-foundation.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: DMAR regression in 2.6.31 leads to ext4 corruption?
Date: Wed, 14 Oct 2009 13:09:26 +0100 [thread overview]
Message-ID: <1255522166.4523.238.camel@macbook.infradead.org> (raw)
In-Reply-To: <20091010014714.GG30557@hexapodia.org>
On Fri, 2009-10-09 at 18:47 -0700, Andy Isaacson wrote:
> Well, we don't know for sure what happened on the previous boot where
> the filesystem corruption occurred. I'm imagining a nightmare scenario
> where GPU erroneous writes cause DMAR faults and handling them somehow
> causes AHCI DMA requests to get lost.
Seems unlikely. The GPU faults happen whenever the GATT changes, because
it translates _every_ address in the GATT through the IOMMU right there
and then -- so if parts of the table are uninitialised, they'll cause
stray write faults. But no writes are actually _happening_.
> I'm going to go ahead on the theory that the BIOS needs an update.
I can't really imagine how that would help; how the BIOS would be
responsible for this. I'm more inclined to blame the drive. It's not an
SSD, is it?
--
dwmw2
next prev parent reply other threads:[~2009-10-14 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 6:17 DMAR regression in 2.6.31 leads to ext4 corruption? Andy Isaacson
2009-10-09 23:37 ` Andy Isaacson
2009-10-10 0:09 ` Chris Wright
2009-10-10 1:47 ` Andy Isaacson
2009-10-14 12:09 ` David Woodhouse [this message]
2009-10-14 15:26 ` Bhavesh Davda
2009-10-14 15:34 ` David Woodhouse
2009-10-14 17:52 ` Andy Isaacson
-- strict thread matches above, loose matches on Subject: below --
2009-10-08 23:56 Andy Isaacson
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=1255522166.4523.238.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=adi@hexapodia.org \
--cc=chrisw@sous-sol.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).