All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: Saeed Bishara <saeed@marvell.com>,
	Nicolas Pitre <nico@marvell.com>,
	linux-kernel@vger.kernel.org,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ext4@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182)
Date: Tue, 11 May 2010 20:47:58 +1000	[thread overview]
Message-ID: <1273574878.21352.25.camel@pasglop> (raw)
In-Reply-To: <20100511101620.GA18654@shareable.org>

On Tue, 2010-05-11 at 11:16 +0100, Jamie Lokier wrote:
> 
> I've seen similar ext3 corruption errors with an IDE on a Sigma
> Designs EM8620 with ARM core.  It's completely unrelated :-) But the
> fault was in the IDE driver doing cache flushes too late after
> starting to set up DMA.  To diagnose it, we luckily found a
> reproducible test case, then sprinkled full cache flushes at various
> places to narrow it down, and eventually found that one full cache
> flush in the driver itself sorted it out, which told us where the
> fault was.  From there it was easy. 

Ok, well, that's -a- possibility... we'll see. I'm doing some more tests
to try to characterize the problem a bit better, then we can play with
the driver. I think it's also worth trying with earlier kernels in case
it's some kind of regression, though that means I'll have to backport my
board support for that little box :-)

Cheers,
Ben.

WARNING: multiple messages have this Message-ID (diff)
From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182)
Date: Tue, 11 May 2010 20:47:58 +1000	[thread overview]
Message-ID: <1273574878.21352.25.camel@pasglop> (raw)
In-Reply-To: <20100511101620.GA18654@shareable.org>

On Tue, 2010-05-11 at 11:16 +0100, Jamie Lokier wrote:
> 
> I've seen similar ext3 corruption errors with an IDE on a Sigma
> Designs EM8620 with ARM core.  It's completely unrelated :-) But the
> fault was in the IDE driver doing cache flushes too late after
> starting to set up DMA.  To diagnose it, we luckily found a
> reproducible test case, then sprinkled full cache flushes at various
> places to narrow it down, and eventually found that one full cache
> flush in the driver itself sorted it out, which told us where the
> fault was.  From there it was easy. 

Ok, well, that's -a- possibility... we'll see. I'm doing some more tests
to try to characterize the problem a bit better, then we can play with
the driver. I think it's also worth trying with earlier kernels in case
it's some kind of regression, though that means I'll have to backport my
board support for that little box :-)

Cheers,
Ben.

WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org, Nicolas Pitre <nico@marvell.com>,
	Saeed Bishara <saeed@marvell.com>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ext4@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182)
Date: Tue, 11 May 2010 20:47:58 +1000	[thread overview]
Message-ID: <1273574878.21352.25.camel@pasglop> (raw)
In-Reply-To: <20100511101620.GA18654@shareable.org>

On Tue, 2010-05-11 at 11:16 +0100, Jamie Lokier wrote:
> 
> I've seen similar ext3 corruption errors with an IDE on a Sigma
> Designs EM8620 with ARM core.  It's completely unrelated :-) But the
> fault was in the IDE driver doing cache flushes too late after
> starting to set up DMA.  To diagnose it, we luckily found a
> reproducible test case, then sprinkled full cache flushes at various
> places to narrow it down, and eventually found that one full cache
> flush in the driver itself sorted it out, which told us where the
> fault was.  From there it was easy. 

Ok, well, that's -a- possibility... we'll see. I'm doing some more tests
to try to characterize the problem a bit better, then we can play with
the driver. I think it's also worth trying with earlier kernels in case
it's some kind of regression, though that means I'll have to backport my
board support for that little box :-)

Cheers,
Ben.



  reply	other threads:[~2010-05-11 10:47 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11  9:23 Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182) Benjamin Herrenschmidt
2010-05-11  9:23 ` Benjamin Herrenschmidt
2010-05-11 10:16 ` Jamie Lokier
2010-05-11 10:16   ` Jamie Lokier
2010-05-11 10:47   ` Benjamin Herrenschmidt [this message]
2010-05-11 10:47     ` Benjamin Herrenschmidt
2010-05-11 10:47     ` Benjamin Herrenschmidt
2010-05-11 10:57 ` Benjamin Herrenschmidt
2010-05-11 10:57   ` Benjamin Herrenschmidt
2010-05-11 11:14   ` Shilimkar, Santosh
2010-05-11 11:14     ` Shilimkar, Santosh
2010-05-12 22:21     ` Jamie Lokier
2010-05-12 22:21       ` Jamie Lokier
2010-05-12 22:47       ` Benjamin Herrenschmidt
2010-05-12 22:47         ` Benjamin Herrenschmidt
2010-05-12 22:47         ` Benjamin Herrenschmidt
2010-05-12 23:08         ` Russell King - ARM Linux
2010-05-12 23:08           ` Russell King - ARM Linux
2010-05-14 17:41           ` Jamie Lokier
2010-05-14 17:41             ` Jamie Lokier
2010-05-14 17:59             ` Russell King - ARM Linux
2010-05-14 17:59               ` Russell King - ARM Linux
2010-05-12 23:41         ` James Bottomley
2010-05-12 23:41           ` James Bottomley
2010-05-13  0:18           ` Benjamin Herrenschmidt
2010-05-13  0:18             ` Benjamin Herrenschmidt
2010-05-13  0:18             ` Benjamin Herrenschmidt
2010-05-13 15:39             ` James Bottomley
2010-05-13 15:39               ` James Bottomley
2010-05-13 23:53               ` Benjamin Herrenschmidt
2010-05-13 23:53                 ` Benjamin Herrenschmidt
2010-05-13 23:53                 ` Benjamin Herrenschmidt
2010-05-13  3:12         ` FUJITA Tomonori
2010-05-13  3:12           ` FUJITA Tomonori
2010-05-13  4:42           ` Benjamin Herrenschmidt
2010-05-13  4:42             ` Benjamin Herrenschmidt
2010-05-13  4:42             ` Benjamin Herrenschmidt
2010-05-12 15:00   ` Jan Kara
2010-05-12 15:00     ` Jan Kara
2010-05-12 22:13     ` Benjamin Herrenschmidt
2010-05-12 22:13       ` Benjamin Herrenschmidt
2010-05-13  0:15     ` Benjamin Herrenschmidt
2010-05-13  0:15       ` Benjamin Herrenschmidt
2010-05-13 15:12       ` Jan Kara
2010-05-13 15:12         ` Jan Kara
2010-05-13 21:33         ` Benjamin Herrenschmidt
2010-05-13 21:33           ` Benjamin Herrenschmidt
2010-05-13 23:51         ` Benjamin Herrenschmidt
2010-05-13 23:51           ` Benjamin Herrenschmidt

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=1273574878.21352.25.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=akpm@linux-foundation.org \
    --cc=jamie@shareable.org \
    --cc=jejb@parisc-linux.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@marvell.com \
    --cc=saeed@marvell.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.