All of lore.kernel.org
 help / color / mirror / Atom feed
From: emre kara <emrekara2002@yahoo.co.uk>
To: Scott Wood <scottwood@freescale.com>,
	Roy Zang <tie-fei.zang@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	David Woodhouse <David.Woodhouse@intel.com>,
	Lan Chunhe-B25806 <b25806@freescale.com>,
	Wood Scott-B07421 <B07421@freescale.com>,
	Anton Vorontsov <cbouatmailru@gmail.com>,
	felix@embedded-sol.com, bayraktarz@yahoo.com
Subject: fsl elbc driver causes corruption with bus monitor timeouts while simultaneously access on Nor / Nand mtd partitions
Date: Thu, 14 Apr 2011 08:06:54 +0100 (BST)	[thread overview]
Message-ID: <204286.97927.qm@web25602.mail.ukl.yahoo.com> (raw)

Hi Scott, Roy.
Scott's "mtd: eLBC NAND: increase bus timeout to maximum" patch is excluded from kernel with Roy's "P4080/eLBC: Make Freescale elbc interrupt common to elbc devices" patch. I don't know the reason for it but this causes bus monitor timeouts and corrupts nand flash while using mainline kernel. As I know there is an errata related to this topic, I think "increasing bus timeout to maximum" is a must.
You can easly generate this situation with below commands:

Note: mtd4 is a Nor and mtd9 is a Nand partition.
[root@P2020RDB root]# mount /dev/mtdblock9 /mnt/src/
mount: you must specify the filesystem type
[root@P2020RDB root]# mount /dev/mtdblock9 /mnt/src/ -t jffs2
��JFFS2 notice: (1950) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[root@P2020RDB root]# dd if=/dev/mtd4 of=/mnt/src/uboot bs=1
fsl-lbc ffe05000.localbus: Local bus monitor time-out: LTESR 0x80000000
fsl-lbc ffe05000.localbus: command failed: fir 412e0000 fcr 0 status 80000000 mdr c0
Read of newly-erased block at 0x00430000 failed: -74. Putting on bad_list
fsl-lbc ffe05000.localbus: Local bus monitor time-out: LTESR 0x80000000
fsl-lbc ffe05000.localbus: command failed: fir 426db000 fcr 6070d000 status 80000000 mdr ff
Erase at 0x0042c000 failed immediately: errno -5
fsl-lbc ffe05000.localbus: Local bus monitor time-out: LTESR 0x80000000
Cfsl-lbc ffe05000.localbus: command failed: fir 412e0000 fcr 0 status 80000000 mdr c0
Read of newly-erased block at 0x00433000 failed: -74. Putting on bad_list
JFFS2: marking eraseblock at 00433000

Regards.

Emre


WARNING: multiple messages have this Message-ID (diff)
From: emre kara <emrekara2002@yahoo.co.uk>
To: Scott Wood <scottwood@freescale.com>,
	Roy Zang <tie-fei.zang@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	felix@embedded-sol.com,
	David Woodhouse <David.Woodhouse@intel.com>,
	linux-kernel@vger.kernel.org, bayraktarz@yahoo.com,
	Lan Chunhe-B25806 <b25806@freescale.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: fsl elbc driver causes corruption with bus monitor timeouts while simultaneously access on Nor / Nand mtd partitions
Date: Thu, 14 Apr 2011 08:06:54 +0100 (BST)	[thread overview]
Message-ID: <204286.97927.qm@web25602.mail.ukl.yahoo.com> (raw)

Hi Scott, Roy.
Scott's "mtd: eLBC NAND: increase bus timeout to maximum" patch is excluded=
 from kernel with Roy's "P4080/eLBC: Make Freescale elbc interrupt common t=
o elbc devices" patch. I don't know the reason for it but this causes bus m=
onitor timeouts and corrupts nand flash while using mainline kernel. As I k=
now there is an errata related to this topic, I think "increasing bus timeo=
ut to maximum" is a must.
You can easly generate this situation with below commands:

Note: mtd4 is a Nor and mtd9 is a Nand partition.
[root@P2020RDB root]# mount /dev/mtdblock9 /mnt/src/
mount: you must specify the filesystem type
[root@P2020RDB root]# mount /dev/mtdblock9 /mnt/src/ -t jffs2
=EF=BF=BD=EF=BF=BDJFFS2 notice: (1950) jffs2_build_xattr_subsystem: complet=
e building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xr=
ef (0 dead, 0 orphan) found.
[root@P2020RDB root]# dd if=3D/dev/mtd4 of=3D/mnt/src/uboot bs=3D1
fsl-lbc ffe05000.localbus: Local bus monitor time-out: LTESR 0x80000000
fsl-lbc ffe05000.localbus: command failed: fir 412e0000 fcr 0 status 800000=
00 mdr c0
Read of newly-erased block at 0x00430000 failed: -74. Putting on bad_list
fsl-lbc ffe05000.localbus: Local bus monitor time-out: LTESR 0x80000000
fsl-lbc ffe05000.localbus: command failed: fir 426db000 fcr 6070d000 status=
 80000000 mdr ff
Erase at 0x0042c000 failed immediately: errno -5
fsl-lbc ffe05000.localbus: Local bus monitor time-out: LTESR 0x80000000
Cfsl-lbc ffe05000.localbus: command failed: fir 412e0000 fcr 0 status 80000=
000 mdr c0
Read of newly-erased block at 0x00433000 failed: -74. Putting on bad_list
JFFS2: marking eraseblock at 00433000

Regards.

Emre

             reply	other threads:[~2011-04-14  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  7:06 emre kara [this message]
2011-04-14  7:06 ` fsl elbc driver causes corruption with bus monitor timeouts while simultaneously access on Nor / Nand mtd partitions emre kara
2011-04-14 12:10 ` Felix Radensky

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=204286.97927.qm@web25602.mail.ukl.yahoo.com \
    --to=emrekara2002@yahoo.co.uk \
    --cc=B07421@freescale.com \
    --cc=David.Woodhouse@intel.com \
    --cc=b25806@freescale.com \
    --cc=bayraktarz@yahoo.com \
    --cc=cbouatmailru@gmail.com \
    --cc=felix@embedded-sol.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=tie-fei.zang@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.