From: Richard Weinberger <rw@linutronix.de>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiattach oops/warning
Date: Fri, 16 Mar 2012 11:27:27 +0100 [thread overview]
Message-ID: <4F63158F.1030405@linutronix.de> (raw)
In-Reply-To: <1331893462.3730.41.camel@sauron.fi.intel.com>
On 16.03.2012 11:24, Artem Bityutskiy wrote:
> On Thu, 2012-03-15 at 16:14 +0100, Richard Weinberger wrote:
>> Hi!
>>
>> While attaching to a NAND chip with lot's of damaged PEBs
>> I UBI gone nuts.
>>
>> See the attached log file.
>> Looks like a bug in an error path.
>>
>> Kernel is 3.0.23 plus some board specific fixes.
>> I didn't touch any UBI stuff...
>
> Can you reproduce this? Did you preserve the flash image?
>
Not really. :(
I got this because the nand driver had a bug.
(That's why most PEBs contained bad data)
I'll try to reproduce it.
Thanks,
//richard
--
Phone: +49 7556 91 98 91; Fax.: +49 7556 91 98 86
Firmensitz: 88690 Uhldingen, Auf dem Berg 3
Registergericht: Amtsgericht Freiburg i. Br., HRB 700 806;
StNr. 87007/07777; Ust-Id Nr.: DE252739476
Geschäftsführer: Heinz Egger, Thomas Gleixner
prev parent reply other threads:[~2012-03-16 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 15:14 ubiattach oops/warning Richard Weinberger
2012-03-16 10:24 ` Artem Bityutskiy
2012-03-16 10:27 ` Richard Weinberger [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=4F63158F.1030405@linutronix.de \
--to=rw@linutronix.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