From: twebb <taliaferro62@gmail.com>
To: David Lambert <dave@lambsys.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiattach taking very long time
Date: Tue, 29 Dec 2009 17:13:35 -0500 [thread overview]
Message-ID: <dbdb2ea60912291413n2c05781du4bf0aaaa822261d0@mail.gmail.com> (raw)
In-Reply-To: <4B3A725F.4050200@lambsys.com>
> I got the following advice for a similar problem. I found I had debugging
> turned on.
>
> "Is your NAND slow? Have you configured UBI debugging checks turned on?
>
> Please, measure your nand throughput withmtd_speedtest:
>
> http://www.linux-mtd.infradead.org/doc/general.html#L_mtd_tests
>
Thanks for the input.
I don't have any debugging turned on, but I'll try the speedtest. It
doesn't appear to be a standard mtd-util; where can I find it? And
any idea how I'll determine from the results that the nand throughput
is the problem? i.e. what is considered acceptable or not?
twebb
next prev parent reply other threads:[~2009-12-29 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 14:14 ubiattach taking very long time twebb
2009-12-29 14:26 ` twebb
[not found] ` <4B3A725F.4050200@lambsys.com>
2009-12-29 22:13 ` twebb [this message]
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=dbdb2ea60912291413n2c05781du4bf0aaaa822261d0@mail.gmail.com \
--to=taliaferro62@gmail.com \
--cc=dave@lambsys.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