From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: General performance of NAND operations i.e mount and ls
Date: Thu, 6 Sep 2007 11:37:35 +0200 [thread overview]
Message-ID: <20070906093735.GD2164@z1.synertronixx> (raw)
In-Reply-To: <1189069864.14370.34.camel@sauron>
Am 2007-09-06 12:11 +0300 schrieb Artem Bityutskiy:
> Try to measure raw R/W, e.g with dd. But beware dd will fail at the
> first met bad block. Something like:
Okay, what would I roughly excpect on this system?
# time dd if=/dev/mtd4 of=/dev/null bs=4096 count=512
512+0 records in
512+0 records out
real 0m 0.61s
user 0m 0.01s
sys 0m 0.61s
# time dd if=/dev/zero of=/dev/mtd4 bs=4096 count=512
512+0 records in
512+0 records out
real 0m 1.08s
user 0m 0.00s
sys 0m 1.08s
Meanwhile I played around with 2.6.23-rc3:
modprobe ubi mtd=4:
UBI: empty MTD device detected
UBI: create volume table (copy #1)
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 0:512,
written 0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 1:512,
written 0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 2:512,
written 0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 3:512,
written 0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 4:512,
written 0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 5:512,
written 0 bytes
UBI warning: io_init: EC and VID headers are in the same minimal I/O
unit, switch to read-only mode
UBI error: validate_ec_hdr: bad VID header offset 512, expected 128
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
Konsti
PS.: does anybody know where the IRQs have gone?
2.6.20:
eth0: dm9000 at c8850000,c8852004 IRQ 133 MAC: 00:0c:7f:01:23:47
2.6.23-rc3:
eth0: dm9000 at c8878000,c887a004 IRQ 165 MAC: 00:0c:7f:01:23:47
Both cases on GPIO101
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next prev parent reply other threads:[~2007-09-06 9:38 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 [this message]
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
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=20070906093735.GD2164@z1.synertronixx \
--to=lists@ku-gbr.de \
--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 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.