From: Artem Bityutskiy <dedekind1@gmail.com>
To: Lukasz Nowak <lukasz.nowak@homersoft.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problem with UBI / UBIFS (mainly ucorrectable error) on kernel higher than 2.6.30.10
Date: Tue, 22 May 2012 11:04:35 +0300 [thread overview]
Message-ID: <1337673875.2483.116.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1337605024.2646.16.camel@debian.softace>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
On Mon, 2012-05-21 at 14:57 +0200, Lukasz Nowak wrote:
> Hi Artem,
>
> Thanks for quick the response.
>
> 1. Please find attached log that you asked for. This time the mounting
> process started to run torture test for PEB 2062 in infinitive loop.
>
> 2. I have compared the MTD sources between 2.6.30.10 (last good kernel)
> and 2.6.31.1 (first with problems) and I found where is the problem.
>
> The new version of kernel (2.6.31.1) introduced some new buffer (in
> orion_nand.c file in drivers/mtd/nand directory you will find new method
> orion_nand_read_buf). What I did is that I have commented this line:
>
> //nc->read_buf = orion_nand_read_buf;
>
> in kernel 2.6.31.1 and recompiled it. This helps and no errors occurred
> this time during boot. I have tested 7 different devices and all of them
> are now OK. What is more I did the same with kernel 2.6.38.4 (our target
> kernel) and again no errors occurred during the boot and everything
> seems to work just fine.
OK.
> So my question is what is the buffer responsible for and is it safe for
> us to just remove it like I did?
I do not know, what is the commit id? Why not to put the author of that
change to CC?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-22 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 11:45 Problem with UBI / UBIFS (mainly ucorrectable error) on kernel higher than 2.6.30.10 Lukasz Nowak
2012-05-18 13:35 ` Artem Bityutskiy
2012-05-21 12:57 ` Lukasz Nowak
2012-05-22 8:04 ` Artem Bityutskiy [this message]
2012-05-22 8:20 ` Guillaume LECERF
2012-05-22 9:44 ` Joakim Tjernlund
[not found] ` <CACYZ3J4rP=JbB8XoVfg-dqWEhTXt_gGt4FsBf3NWngyCKaa+JQ@mail.gmail.com>
2012-05-25 9:39 ` Artem Bityutskiy
2012-05-25 9:42 ` 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=1337673875.2483.116.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=lukasz.nowak@homersoft.com \
/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).