From: James <jamessteward@optusnet.com.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: New thread [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic
Date: Mon, 12 May 2008 13:24:40 +1000 [thread overview]
Message-ID: <1210562680.6235.55.camel@Ubuntu-Desktop> (raw)
In-Reply-To: <1210550476.6235.30.camel@Ubuntu-Desktop>
On Mon, 2008-05-12 at 10:01 +1000, James wrote:
> On Sun, 2008-05-11 at 23:41 +0100, David Woodhouse wrote:
> > Just type it.
> > http://git.infradead.org/mtd-2.6.git?a=commitdiff;h=abe2f4143
>
> It seems better. I still get bucket loads of;
>
> mtd->read(0x62c bytes from 0x3204608) returned ECC error
>
> and the occasional;
>
> Data CRC failed on REF_PRISTINE data node at 0x0331540c: Read
> 0x503a4071, calculated 0x52c053a8
>
> but no more kernel oops, which makes me much happier.
^^^^^^^
Scrub that. I just got an oops. Same place as before
(fs/jffs2/file.c:251), but far less frequent than before.
> Any ideas on the above two mentioned warnings? Are they the result of
> unclean NAND oob data, or kernel bugs, or something else?
I guess there are still some bugs to squash.
Regards,
James.
next prev parent reply other threads:[~2008-05-12 3:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 5:51 New thread [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic James
2008-05-09 8:12 ` David Woodhouse
2008-05-11 22:31 ` James
2008-05-11 22:41 ` David Woodhouse
2008-05-11 23:10 ` James
2008-05-12 0:01 ` James
2008-05-12 3:24 ` James [this message]
2008-05-14 6:38 ` James
[not found] ` <e8775dd00805150201t12448ec5x452425039abc18de@mail.gmail.com>
2008-05-16 2:35 ` James
2008-05-11 22:46 ` James
2008-05-09 12:55 ` Anders Grafström
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=1210562680.6235.55.camel@Ubuntu-Desktop \
--to=jamessteward@optusnet.com.au \
--cc=dwmw2@infradead.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