public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: enrico benetti <enrico.benetti@bluewind.it>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS: power cut test on 2.6.35 + NOR
Date: Mon, 1 Jul 2013 10:23:17 +0800	[thread overview]
Message-ID: <51D0E815.8080300@freescale.com> (raw)
In-Reply-To: <CAN8TOE-+3tedAebiWMTAzEJfaBPs7pwWBuKkJpV9Cx1e402nnQ@mail.gmail.com>

于 2013年06月29日 10:08, Brian Norris 写道:
> (Adding Huang, who has also debugged (different) problems with this NOR driver)
>
> Hi Enrico,
>
> On Fri, Jun 28, 2013 at 6:36 AM, enrico benetti
> <enrico.benetti@bluewind.it>  wrote:
>> [   20.391279] MTD do_write_buffer(): software timeout
>> [   20.452081] UBI error: nor_erase_prepare: cannot invalidate PEB 25,
>> write returned -5 read returned 2
>>
>> Digging the web, I've found several discussions on write-timeout with
>> NOR devices
>> (cfr.http://lists.infradead.org/pipermail/linux-mtd/2013-June/047177.html),
>> but this seems not to be the root cause.
> I'm curious: what makes you think this has a different root cause?
>
> I'm still working on debugging the do_write_buffer timeout on my
> systems. I'd recommend trying to increase the timeout in
> do_write_buffer(), just to see if your kernel isn't waiting long
> enough. (In my case, I can pretty well show that while the code *says*
> it's waiting for a whole jiffy -- at least 1ms -- it is in fact
> waiting less than that.)
>
> I believe Huang's resolution for his problem was actually a problem
> with the flash part itself.
yes.
For my timeout, Micron confirmed that there is a silicon bug in this 
type of NOR.


thanks
Huang Shijie

      reply	other threads:[~2013-07-01  2:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27  6:44 UBIFS: power cut test on 2.6.35 + NOR enrico benetti
2013-06-27  9:32 ` Norbert van Bolhuis
2013-06-27 10:47 ` Mats Kärrman
2013-06-27 12:56   ` enrico benetti
2013-06-27 13:01     ` Mats Kärrman
2013-06-28 13:36       ` enrico benetti
2013-06-28 15:03         ` enrico benetti
2013-06-29  2:08         ` Brian Norris
2013-07-01  2:23           ` Huang Shijie [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=51D0E815.8080300@freescale.com \
    --to=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=enrico.benetti@bluewind.it \
    --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