From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jon Ringle <jon@ringle.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Erase race?
Date: Wed, 21 Apr 2010 02:04:00 +0300 [thread overview]
Message-ID: <1271804640.11751.1363.camel@localhost.localdomain> (raw)
In-Reply-To: <n2g152584231004131315ge1d824bfm6820ccb877a0fde6@mail.gmail.com>
On Tue, 2010-04-13 at 16:15 -0400, Jon Ringle wrote:
> Hi,
> I have a few machines that have UBI and UBIFS on NOR flash that are
> undergoing continuous reboot testing.
> One of them just caught the following failure:
>
> [ 51.250000] IXP4XX-Flash.0: buffer write error (status 0xd0)
> [ 51.250000] UBI error: ubi_io_write: error -22 while writing 64
> bytes to PEB 226:0, written 0 bytes
> [ 51.270000] UBI error: erase_worker: failed to erase PEB 226, error -22
> [ 51.270000] UBI warning: ubi_ro_mode: switch to read-only mode
> [ 51.290000] UBI error: do_work: work failed with error code -22
> [ 51.290000] UBI error: ubi_thread: ubi_bgt0d: work failed with error code -22
>
> Looking at this it appears that the failure might have been caused due
> to the erase_worker and ubi_io_write occurring out of order... since
> it looks like ubi_io_write was trying to write at offset 0 of the PEB,
> which I imagine would have to be the EC header, which should happen
> after the block is erased. But it doesn't seem to be the case here.
I'm out of office and have a long queue of unanswered mails, so please,
do not wait for help from me soon, and just debug this.
The erase_worker function writes the EC header after the eraseblock is
erased. IOW, I think erase_worker calls ubi_io_write, which fails with
-EINVAL for some reasons, and you see these prints. So this does not
look like a race, at least not an UBI race. If you had UBI debugging
enabled (which is a good idea), you'd have few more info and a stackdump
printed.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-04-20 23:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 20:15 Erase race? Jon Ringle
2010-04-20 20:24 ` Jon Ringle
2010-04-20 22:00 ` Jamie Lokier
2010-04-27 12:59 ` Artem Bityutskiy
2010-05-12 2:30 ` Jon Ringle
2010-05-12 3:32 ` Artem Bityutskiy
2010-05-12 8:21 ` massimo cirillo
2010-05-12 12:00 ` Jon Ringle
2010-05-12 12:31 ` massimo cirillo
2010-05-13 13:23 ` Jon Ringle
2010-04-20 23:04 ` 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=1271804640.11751.1363.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=jon@ringle.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