Message-ID: <467FB237.2030703@esuna.co.uk>
Date: Mon, 25 Jun 2007 13:16:55 +0100
From: "Jay L. T. Cornwall" <jay@esuna.co.uk>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Jay Cliburn <jacliburn@bellsouth.net>
CC: linux-kernel@vger.kernel.org, kronos.it@gmail.com,
       Chris Snook <csnook@redhat.com>
Subject: Attansic L1 page corruption (was: 2.6.22-rc5: pdflush oops under
 heavy disk load)
References: <467B12CA.5060405@esuna.co.uk>	<467BE118.4090308@redhat.com>	<467BE4F1.7040308@esuna.co.uk>	<467D0EB0.9030100@esuna.co.uk>	<20070624125957.2e27820c@osprey.hogchain.net>	<467ED4A8.4080500@esuna.co.uk> <20070624164519.04f215b8@osprey.hogchain.net>
In-Reply-To: <20070624164519.04f215b8@osprey.hogchain.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1064
Lines: 27

Jay Cliburn wrote:

> For reasons not yet clear to me, it appears the L1 driver has a bug or
> the device itself has trouble with DMA in high memory.  This patch,
> drafted by Luca Tettamanti, is being explored as a workaround.  I'd be
> interested to know if it fixes your problem.

Yes, it certainly seems to. Now running with this patch and 4GB active,
I've transferred about 15GB with no problem so far. It usually oopses
after a GB or two.

I guess it's not an ideal solution, architecturally speaking, but it's a
good deal better than an unstable driver. If there's any other patches
you'd like me to test or traces to capture, I'm happy to help out.
Otherwise I'll run with this one for now since it does the job!

Thanks.

-- 
Jay L. T. Cornwall, http://www.esuna.co.uk/~jay/
PhD Student
Imperial College London
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/