From: "Dimitar Penev" <dpn@switchfin.org>
To: "Dimitar Penev" <dpn@switchfin.org>, <linux-mtd@lists.infradead.org>
Subject: Re: ubiattach issue
Date: Thu, 20 Sep 2012 13:18:19 +0300 [thread overview]
Message-ID: <00d401cd9719$41e314b0$2901a8c0@dpn> (raw)
In-Reply-To: 006c01cd970c$1b9cb930$2901a8c0@dpn
Hi again,
Bellow the results of few mtd test tools I've tried.
==========================================================
mtd_speedtest: MTD device: 5
mtd_speedtest: MTD device size 511705088, eraseblock size 131072, page size
2048, count of eraseblocks 3904, pages per eraseblock 64, OOB size 64
mtd_speedtest: scanning for bad eraseblocks
mtd_speedtest: scanned 3904 eraseblocks, 0 are bad
mtd_speedtest: testing eraseblock write speed
mtd_speedtest: eraseblock write speed is 4552 KiB/s
mtd_speedtest: testing eraseblock read speed
mtd_speedtest: eraseblock read speed is 2722 KiB/s
mtd_speedtest: testing page write speed
mtd_speedtest: page write speed is 4517 KiB/s
mtd_speedtest: testing page read speed
mtd_speedtest: page read speed is 2712 KiB/s
mtd_speedtest: testing 2 page write speed
mtd_speedtest: 2 page write speed is 4533 KiB/s
mtd_speedtest: testing 2 page read speed
mtd_speedtest: 2 page read speed is 2715 KiB/s
mtd_speedtest: Testing erase speed
mtd_speedtest: erase speed is 153662 KiB/s
mtd_speedtest: Testing 2x multi-block erase speed
mtd_speedtest: 2x multi-block erase speed is 292571 KiB/s
mtd_speedtest: Testing 4x multi-block erase speed
mtd_speedtest: 4x multi-block erase speed is 293258 KiB/s
mtd_speedtest: Testing 8x multi-block erase speed
mtd_speedtest: 8x multi-block erase speed is 293258 KiB/s
mtd_speedtest: Testing 16x multi-block erase speed
mtd_speedtest: 16x multi-block erase speed is 294641 KiB/s
mtd_speedtest: Testing 32x multi-block erase speed
mtd_speedtest: 32x multi-block erase speed is 292571 KiB/s
mtd_speedtest: Testing 64x multi-block erase speed
mtd_speedtest: 64x multi-block erase speed is 294641 KiB/s
mtd_speedtest: finished
=================================================
=================================================
mtd_pagetest: MTD device: 5
mtd_pagetest: MTD device size 511705088, eraseblock size 131072, page size
2048, count of eraseblocks 3904, pages per eraseblock 64, OOB size 64
mtd_pagetest: scanning for bad eraseblocks
mtd_pagetest: scanned 3904 eraseblocks, 0 are bad
mtd_pagetest: erasing whole device
mtd_pagetest: erased 3904 eraseblocks
mtd_pagetest: writing whole device
mtd_pagetest: written up to eraseblock 0
mtd_pagetest: written up to eraseblock 256
mtd_pagetest: written up to eraseblock 512
mtd_pagetest: written up to eraseblock 768
mtd_pagetest: written up to eraseblock 1024
mtd_pagetest: written up to eraseblock 1280
mtd_pagetest: written up to eraseblock 1536
mtd_pagetest: written up to eraseblock 1792
mtd_pagetest: written up to eraseblock 2048
mtd_pagetest: written up to eraseblock 2304
mtd_pagetest: written up to eraseblock 2560
mtd_pagetest: written up to eraseblock 2816
mtd_pagetest: written up to eraseblock 3072
mtd_pagetest: written up to eraseblock 3328
mtd_pagetest: written up to eraseblock 3584
mtd_pagetest: written up to eraseblock 3840
mtd_pagetest: written 3904 eraseblocks
mtd_pagetest: verifying all eraseblocks
mtd_pagetest: verified up to eraseblock 0
mtd_pagetest: verified up to eraseblock 256
mtd_pagetest: verified up to eraseblock 512
mtd_pagetest: verified up to eraseblock 768
mtd_pagetest: verified up to eraseblock 1024
mtd_pagetest: verified up to eraseblock 1280
mtd_pagetest: verified up to eraseblock 1536
mtd_pagetest: verified up to eraseblock 1792
mtd_pagetest: verified up to eraseblock 2048
mtd_pagetest: verified up to eraseblock 2304
mtd_pagetest: verified up to eraseblock 2560
mtd_pagetest: verified up to eraseblock 2816
mtd_pagetest: verified up to eraseblock 3072
mtd_pagetest: verified up to eraseblock 3328
mtd_pagetest: verified up to eraseblock 3584
mtd_pagetest: verified up to eraseblock 3840
uncorrectable error :
mtd_pagetest: error: read failed at 0x1e7fd800
uncorrectable error :
mtd_pagetest: error: read failed at 0x1e7fd800
mtd_pagetest: error -74 occurred
=================================================
modprobe: can't load module mtd_pagetest
(kernel/drivers/mtd/tests/mtd_pagetest.ko): Bad message
Thanks
Dimitar
----- Original Message -----
From: "Dimitar Penev" <dpn@switchfin.org>
To: <linux-mtd@lists.infradead.org>
Sent: Thursday, September 20, 2012 11:44 AM
Subject: ubiattach issue
> Hi Gents,
>
> I am facing an issue with ubiattach on Linux kernel 3.0.8
> On our target we have nand flash with mtd layer on top.
> The logs attached below.
>
> Can you please give me a pointer?
>
>
> /bin # ubinfo -a
> UBI version: 1
> Count of UBI devices: 0
> UBI control device major/minor: 10:62
>
> /bin # ubiformat /dev/mtd5 -y --vid-hdr-offset="2048"
> ubiformat: mtd5 (nand), size 511705088 bytes (488.0 MiB), 3904 eraseblocks
> of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
> libscan: scanning eraseblock 3903 -- 100 % complete
> ubiformat: 3904 eraseblocks have valid erase counter, mean value is 3
> ubiformat: formatting eraseblock 3903 -- 100 % complete
>
> /bin # ubiattach /dev/ubi_ctrl --mtdn=5 --devn=0 --vid-hdr-offset="2048"
> ubiattach: error!: cannot attach mtd5
> error 25 (Inappropriate ioctl for device)
>
>
> Best Regards
> Dimitar
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2012-09-20 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 8:44 ubiattach issue Dimitar Penev
2012-09-20 10:18 ` Dimitar Penev [this message]
2012-09-20 18:25 ` Vikram Narayanan
2012-09-20 19:22 ` Dimitar Penev
2012-09-20 19:40 ` Dimitar Penev
2012-09-20 20:37 ` Vikram Narayanan
2012-09-21 6:40 ` Dimitar Penev
2012-09-21 8:44 ` Dimitar Penev
2012-09-21 9:05 ` Dimitar Penev
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='00d401cd9719$41e314b0$2901a8c0@dpn' \
--to=dpn@switchfin.org \
--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