public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Adrian Hunter <adrian.hunter@nokia.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS trouble
Date: Thu, 9 Jul 2009 20:56:34 +0200	[thread overview]
Message-ID: <20090709185634.GA26160@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090709181114.GB15518@buzzloop.caiaq.de>

On Thu, Jul 09, 2009 at 08:11:14PM +0200, Daniel Mack wrote:
> > Try the NAND tests in drivers/mtd/tests.
> 
> Hmm. The torture test indees shows a problem now:
> 
> sh-3.2# modprobe mtd_torturetest dev=3
> [  386.367730] 
> [  386.369296] =================================================
> [  386.375258] mtd_torturetest: Warning: this program is trying to wear out your flash, stop it if this is not wanted.
> [  386.385811] mtd_torturetest: MTD device: 3
> [  386.390021] mtd_torturetest: torture 32 eraseblocks (8-39) of mtd3
> [  386.396238] mtd_torturetest: write verify enabled
> [  388.675993] double bit error @ page 00000b79
> [  388.680406] timed out writing command
> [  388.687925] mtd_torturetest: error -74 while reading EB 36, read 131072
> [  388.694536] mtd_torturetest: verify failed for 0xFF... pattern
> [  388.700364] mtd_torturetest: finished after 0 erase cycles
> [  388.705885] mtd_torturetest: error -74 occurred during torturing
> [  388.711908] =================================================
> modprobe: Failed to load module mtd_torturetest: Bad message.

Interesting. I think I solved that issue - it seems to be related to the
selected CPU govenor. Switching from 'conservative' to 'performance'
makes the torture test pass.

I'll discuss that on the ARM mailing list.

Thanks,
Daniel

      reply	other threads:[~2009-07-09 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 17:55 UBIFS trouble Daniel Mack
2009-07-09 18:00 ` Adrian Hunter
2009-07-09 18:11   ` Daniel Mack
2009-07-09 18:56     ` Daniel Mack [this message]

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=20090709185634.GA26160@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=adrian.hunter@nokia.com \
    --cc=linux-mtd@lists.infradead.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