Re: [PATCH 3/3] mtd: cfi_cmdset_0002: increase do_write_buffer() timeout
From: Brian Norris
Date: Wed Jun 05 2013 - 14:02:00 EST
On Tue, Jun 4, 2013 at 12:03 AM, Huang Shijie <b32955@xxxxxxxxxxxxx> wrote:
> 于 2013年06月04日 09:46, Brian Norris 写道:
>> After various tests, it seems simply that the timeout is not long enough
>> for my system; increasing it by a few jiffies prevented all failures
>> (testing for 12+ hours). There is no harm in increasing the timeout, but
>> there is harm in having it too short, as evidenced here.
> I like the patch1 and patch 2.
> But extending the timeout from 1ms to 10ms is like a workaround. :)
I was afraid you might say that; that's why I stuck the first two
patches first ;)
> From the NOR's spec, even the maximum write-to-buffer only costs several
> hundreds us,
> such as 200us.
> I GUESS your problem is caused by the timer system, not the MTD code. I
> ever met this type of bug.
I suspected similarly, but I didn't (until now) believe that's the
case here. See below.
> The bug is in the kernel 3.5.7, but the latest kernel has fixed it with
> NO_HZ_IDLE/NO_HZ_COMMON features.
Did you track your bug down to a particular commit? 3.5.7 is the
stable kernel; do you know what mainline rev it showed up in? I'm not
quite interested in backporting all of the new 3.10 features!
> I do not meet the issue the latest linux-next tree.
> I try to describe the jiffies bug with my poor english:
>  background:
> CONFIG_HZ=100, CONFIG_NO_HZ=y
>  call nand_wait() when we write a nand page.
>  The jiffies was not updated at a _even_ speed.
> In the nand_wait(), you wait for 20ms(2 jiffies) for a page write,
> and the timeout occurs during the page write. Of course, you think that
> we have already waited for 20ms.
> But in actually, we only waited for 1ms or less!
> How do i know this? I use the gettimeofday to check the real time when
> the timeout occur.
I suspected this very type of thing, since this has come up in a few
different contexts. And for some time, with a number of different
checks, it appeared that this *wasn't* the case. But while writing
this very email, I had the bright idea that my time checkpoint was in
slightly the wrong place; so sure enough, I found that I was timing
out after only 72519 ns! (That is, 72 us, or well below the max write
I'm testing on MIPS with a 3.3 kernel, by the way, but I believe this
sort of bug has been around a while.
>  if i disable the local timer, the bug disappears.
> So, could you check the real time when the timeout occurs?
> Btw: My NOR's timeout is proved to be a silicon bug by Micron.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/