public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: alfred steele <alfred.jaquez@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mxc_nand: i.MX35 hardware ECC fixups
Date: Sun, 13 Dec 2009 15:36:26 +0100	[thread overview]
Message-ID: <807hsrvt3p.fsf@merkur.tec.linutronix.de> (raw)
In-Reply-To: <528f13590912121558h26a95a1awcc2f8f384e8c3076@mail.gmail.com> (alfred steele's message of "Sat\, 12 Dec 2009 17\:58\:34 -0600")

Hi Alfred,

On 2009-12-13, alfred steele <alfred.jaquez@gmail.com> wrote:
> I am having a issue with using nandwrite mtd util and it so happens
> that the nandwrite gets stuck at a particular block and the sonsole
> hangs there forever.
>
> We are using the mx27(mxc) with a large size page NAND(4k). The annd
> write suceeds for the kernel MTD parition. I am suspecting my NAND
> driver is somehow obsolete. How do i find out as to what could be the
> root cause of the problem?
>
> What could be the pest debugging path?

You may want to consider setting the kernel option MTD_DEBUG and setting
MTD_DEBUG_VERBOSE to 3 (noisy). It will generate a _lot_ of output on
the console, but may help you to identify where it is hanging.

John Ogness

      parent reply	other threads:[~2009-12-13 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 17:06 [PATCH] mxc_nand: i.MX35 hardware ECC fixups John Ogness
     [not found] ` <528f13590911071823sa26e1ane027d51d16357c79@mail.gmail.com>
     [not found]   ` <80y6mg5e34.fsf@merkur.tec.linutronix.de>
2009-12-12 23:58     ` alfred steele
2009-12-13 14:00       ` Eric Bénard
2009-12-13 14:36       ` John Ogness [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=807hsrvt3p.fsf@merkur.tec.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=alfred.jaquez@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