From: twebb <taliaferro62@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: ubiattach taking very long time
Date: Tue, 22 Dec 2009 09:14:50 -0500 [thread overview]
Message-ID: <dbdb2ea60912220614r656df531sae2be73e8f7f8163@mail.gmail.com> (raw)
Does it make any sense that a ubiattach would take > 20 secs? The
flash I'm using is Samsung 4GiB MLC NAND flash. I'm running 2.6.28
kernel. Here's the capture...
[ 1.753280] Creating 6 MTD partitions on "Samsung 32Gibx8":
[ 1.758855] 0x000000000000-0x000000080000 : "bootloader-alt"
[ 1.765676] 0x000000080000-0x000000100000 : "environment-alt"
[ 1.772290] 0x000000100000-0x000000400000 : "kernel-alt"
[ 1.778403] 0x000000400000-0x000000800000 : "kernelrecovery-alt"
[ 1.785252] 0x000000800000-0x000004000000 : "maintenance"
[ 1.791577] 0x000004000000-0x000100000000 : "system"
[ 1.799725] UBI: attaching mtd5 to ubi0
[ 1.803630] UBI: physical eraseblock size: 524288 bytes (512 KiB)
[ 1.809901] UBI: logical eraseblock size: 516096 bytes
[ 1.815365] UBI: smallest flash I/O unit: 4096
[ 1.820067] UBI: VID header offset: 4096 (aligned 4096)
[ 1.826109] UBI: data offset: 8192
[ 23.124750] UBI: attached mtd5 to ubi0
[ 23.128505] UBI: MTD device name: "system"
[ 23.133702] UBI: MTD device size: 4032 MiB
[ 23.138757] UBI: number of good PEBs: 8064
[ 23.143495] UBI: number of bad PEBs: 0
[ 23.147945] UBI: max. allowed volumes: 128
[ 23.152592] UBI: wear-leveling threshold: 256
[ 23.157211] UBI: number of internal volumes: 1
[ 23.161689] UBI: number of user volumes: 4
[ 23.166135] UBI: available PEBs: 4
[ 23.170612] UBI: total number of reserved PEBs: 8060
[ 23.175584] UBI: number of PEBs reserved for bad PEB handling: 80
[ 23.181715] UBI: max/mean erase counter: 2/0
[ 23.186120] UBI: background thread "ubi_bgt0d" started, PID 421
next reply other threads:[~2009-12-22 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 14:14 twebb [this message]
2009-12-29 14:26 ` ubiattach taking very long time twebb
[not found] ` <4B3A725F.4050200@lambsys.com>
2009-12-29 22:13 ` twebb
2010-01-10 0:01 ` Artem Bityutskiy
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=dbdb2ea60912220614r656df531sae2be73e8f7f8163@mail.gmail.com \
--to=taliaferro62@gmail.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