From: wolfgang@leila.ping.de (Wolfgang Wegner)
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS oops after remount ro
Date: Fri, 26 Nov 2010 18:29:12 +0100 [thread overview]
Message-ID: <20101126172912.GX23237@leila.ping.de> (raw)
In-Reply-To: <1290785057.2552.14.camel@localhost>
Hi,
thank you for the hints!
I am currently trying to reproduce the error even without modified
kernel - it seems I changed enough of my init procedure to somehow
avoid the trigger condition. :-(
As soon as I can reproduce the error, I will try what you suggested.
Best regards,
Wolfgang
next prev parent reply other threads:[~2010-11-26 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 13:50 UBIFS oops after remount ro Wolfgang Wegner
2010-11-26 15:24 ` Artem Bityutskiy
2010-11-26 17:29 ` Wolfgang Wegner [this message]
2010-11-29 13:18 ` Wolfgang Wegner
2010-11-29 14:21 ` Artem Bityutskiy
[not found] ` <20101129151729.GE23237@leila.ping.de>
[not found] ` <1291049157.2141.17.camel@koala>
2010-11-29 17:02 ` Wolfgang Wegner
2010-11-29 17:23 ` Wolfgang Wegner
2010-12-02 3:35 ` Artem Bityutskiy
2010-12-02 3:41 ` Artem Bityutskiy
2010-12-02 9:17 ` Wolfgang Wegner
2010-12-02 12:20 ` 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=20101126172912.GX23237@leila.ping.de \
--to=wolfgang@leila.ping.de \
--cc=dedekind1@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;
as well as URLs for NNTP newsgroup(s).