public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Konstantin Kletschke <lists@ku-gbr.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: General performance of NAND operations i.e mount and ls
Date: Fri, 07 Sep 2007 08:47:14 +0300	[thread overview]
Message-ID: <1189144034.14370.73.camel@sauron> (raw)
In-Reply-To: <20070906160357.GG2164@z1.synertronixx>

On Thu, 2007-09-06 at 18:03 +0200, Konstantin Kletschke wrote:
> > may you please go to Device Drivers--->Memory Technology Device (MTD)
> > support--->UBI - Unsorted block images---> in menuconfig and enable "UBI
> > debugging", "UBI debugging messages", and "Extra self-checks" and try
> > again? Then send what UBI prints. I'll try to figure out what is wrong.
> 
> Well after half an hour I got this:

It is long because you enabled paranoid checks. One of them scans whole
media and makes sure it is really empty and contains only 0xFFs. You may
disable paranoid checks to make it faster.

> UBI DBG: attach_mtd_dev: attaching mtd4 to ubi0: VID header offset 0 data offset 0
> UBI DBG: io_init: min_io_size      2048
> UBI DBG: io_init: hdrs_min_io_size 512
> UBI DBG: io_init: ec_hdr_alsize    512
> UBI DBG: io_init: vid_hdr_alsize   512
> UBI DBG: io_init: vid_hdr_offset   512
> UBI DBG: io_init: vid_hdr_aloffset 512
> UBI DBG: io_init: vid_hdr_shift    0
> UBI DBG: io_init: leb_start        2048
> UBI DBG: io_init: leb_size         129024
> UBI DBG: io_init: ro_mode          0
> UBI DBG: ubi_scan: scanning is finished

Yeah, your flash driver is not OK. It reports 2 in mtd->subpage_sft, but
it is unable to write in sub-page chunks (512 bytes) - it returns -EIO. 

You should either teach it to write sub-pages (preferable) or report 0
in mtd->subpage_sft, which would mean "no sub-page support".

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2007-09-07  5:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  8:12 General performance of NAND operations i.e mount and ls Konstantin Kletschke
2007-09-06  8:27 ` Artem Bityutskiy
2007-09-06  8:44   ` Konstantin Kletschke
2007-09-06  9:11     ` Artem Bityutskiy
2007-09-06  9:37       ` Konstantin Kletschke
2007-09-06 10:53         ` Artem Bityutskiy
2007-09-06 11:21         ` Artem Bityutskiy
2007-09-06 11:11       ` Artem Bityutskiy
2007-09-06 16:03         ` Konstantin Kletschke
2007-09-07  5:47           ` Artem Bityutskiy [this message]
2007-09-07  7:44             ` Konstantin Kletschke
2012-06-25 12:01               ` JFFS2 CRC problems Stefan Roese

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=1189144034.14370.73.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lists@ku-gbr.de \
    /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