ubi_eba_init_scan: cannot reserve enough PEBs
Matthew L. Creech
mlcreech at gmail.com
Tue Sep 7 11:59:25 EDT 2010
On Mon, Sep 6, 2010 at 5:17 AM, Artem Bityutskiy <dedekind1 at gmail.com> wrote:
>
> The other idea which would definitely help is to create a debugging
> patch which will track all erasures of PEBs and store them somewhere. I
> do not know which tracing debugging tools you have, if you have some
> fast tracing you can just send this info via your tracing interface. But
> if you don't, you can use other flash or another partition on your flash
> and store the info.
>
...
This makes sense, however I'm not sure of a good way to store this
info. I don't have any hardware debugging tools (BDI, etc.) though I
could probably get my hands on one if you think it would help.
Creating another flash partition and saving data there could work,
although I'm not familiar with how to do that safely/cleanly from
within the kernel (I could give it a try though).
The brute-force method would be to just dump all of this info out to
the serial console, and I'll leave a minicom session running on a PC
to capture everything that happens. I can't be certain how long it
would take to get a freshly-formatted device into this state, but the
quantity of output isn't a problem if I'm capturing to a PC.
I'll probably have time to set this test up in the next few days, but
it may be weeks until the test device goes bad (if it ever goes bad at
all). As far as what code should be tested, do you want me to just
pull a copy of the latest ubifs-2.6 tree? Or apply these patches to
something more stable?
Thanks for your help Artem!
--
Matthew L. Creech
More information about the linux-mtd
mailing list