From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: Detlev Zundel <dzu@denx.de>
Cc: linux-mtd@lists.infradead.org, yanok@emcraft.com
Subject: Re: [RFC] Handling of errors for AMD NOR (cfi_cmdset_0002) chips
Date: Thu, 24 Mar 2011 11:48:20 +0100 [thread overview]
Message-ID: <4D8B2174.50606@aimvalley.nl> (raw)
In-Reply-To: <m28vw4x3zk.fsf@ohwell.denx.de>
On 03/24/11 10:27, Detlev Zundel wrote:
...
>> But the unstable bit problem is different from software timeout
>> related issues regarding UBI and NOR flash the OP mentioned.
>> It is anyway good to hear work is in progress here.
>
> It is never good to ignore errors reported by the hardware if you are
> looking for problems in higher software layers. That's why we decided
> to implement such error checks which can then be helpful in our further
> testing. We are hoping that we can better differentiate between
> software and hardware problems this way.
>
ok, I see.
>> I asked about the software timeout issue because I've seen false
>> timeouts with powerpc + CONFIG_NO_HZ a while ago.
>> In my case the low-level do_write_buffer (cfi_cmdset_0002.c) timed
>> out too early. See
>> http://lkml.org/lkml/2009/9/3/84
>
> Ok, I see, thanks for the pointer. The problems you experienced then
> were unneccessary software timeouts, but there was no data corruption,
> correct?
>
yes that is correct.
It happened only when system was 'stressed' a bit and it caused false
software timeouts which made UBIFS remount the fs in read-only mode.
---
N. van Bolhuis.
next prev parent reply other threads:[~2011-03-24 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 1:42 [RFC] Handling of errors for AMD NOR (cfi_cmdset_0002) chips Ilya Yanok
2011-03-11 8:25 ` Norbert van Bolhuis
2011-03-23 15:47 ` Detlev Zundel
2011-03-23 17:33 ` Artem Bityutskiy
2011-03-24 7:35 ` Norbert van Bolhuis
2011-03-24 9:27 ` Detlev Zundel
2011-03-24 10:48 ` Norbert van Bolhuis [this message]
2011-03-15 8:01 ` Markus Niebel
2011-03-23 16:16 ` Detlev Zundel
2011-03-23 18:27 ` Ilya Yanok
2011-03-24 7:45 ` Alexander Stein
2011-03-24 7:55 ` 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=4D8B2174.50606@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--cc=dzu@denx.de \
--cc=linux-mtd@lists.infradead.org \
--cc=yanok@emcraft.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