From: "Anders Grafström" <grfstrm@users.sourceforge.net>
To: Matt Witherspoon <spoon@vt.edu>
Cc: linux-mtd@lists.infradead.org
Subject: Re: BUG in jffs2 with MTD map using cached mapping
Date: Fri, 09 Jan 2009 16:46:57 +0100 [thread overview]
Message-ID: <49677171.3080300@users.sourceforge.net> (raw)
In-Reply-To: <1231256507.49637bbb174b6@webmail.vt.edu>
Matt Witherspoon wrote:
> I performed a bisection and the offending commit is
> 205c109a7a96d9a3d8ffe64c4068b70811fef5e8. Before this commit, neither the BUG
> nor the node CRC failure occured.
>
> One notable difference between my board and Mainstone is that my flash chip is
> using the 0002 command set.
>
> I'm stumped at this point... Any suggestions on where to dig further?
I'd say that the BUG_ON is a secondary error. A broken error path.
http://lists.infradead.org/pipermail/linux-mtd/2008-April/021473.html
next prev parent reply other threads:[~2009-01-09 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 15:41 BUG in jffs2 with MTD map using cached mapping Matt Witherspoon
2009-01-09 15:46 ` Anders Grafström [this message]
2009-01-20 1:05 ` Matt Witherspoon
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=49677171.3080300@users.sourceforge.net \
--to=grfstrm@users.sourceforge.net \
--cc=linux-mtd@lists.infradead.org \
--cc=spoon@vt.edu \
/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