Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Eric Millbrandt <emillbrandt@dekaresearch.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: ubi_bgt0d: page allocation failure. order:8, mode:0xd0
Date: Thu, 04 Feb 2010 07:19:08 +0200	[thread overview]
Message-ID: <1265260748.2517.47.camel@localhost.localdomain> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD3118B8DD2D4@dekaexchange07.deka.local>

On Mon, 2010-01-25 at 15:30 -0500, Eric Millbrandt wrote:
> Hello all,
> 
> I have an embedded system that is running on a ubifs root filesystem
> which is dropping into read-only mode.  After a read of the mtd FAQ I
> found out that the filesystem has an unexpected error and that I
> should contact this list.  What could be causing this error?

You did not provide full output. But from what I see you have a bad
blocks. UBI recovers data, which is fine. But you have suspiciously too
many of them. May be this is a norm in MLC...

The ultimate failure is because MTD cannot allocate RAM. MTD should not
dynamically allocate order 8 buffer, that would need to be fixed. You'd
need to hack that function and make it allocate an array of pages, not
an 256KiB at once. Indeed, memory fragmentation quickly leads inability
to find 256KiB of physically continuous RAM.

> I am running the following
> 
> - Freescale MPC5200B
> - Micron MLC NAND flash

And I assume you read this:
http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_mlc

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2010-02-04  5:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 20:30 ubi_bgt0d: page allocation failure. order:8, mode:0xd0 Eric Millbrandt
2010-02-04  5:19 ` Artem Bityutskiy [this message]

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=1265260748.2517.47.camel@localhost.localdomain \
    --to=dedekind1@gmail.com \
    --cc=emillbrandt@dekaresearch.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