All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Christian Hemp <c.hemp@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] mtd: nand_mxs: fix NAND error when change clk rate
Date: Thu, 22 Dec 2016 18:55:14 +0100	[thread overview]
Message-ID: <20161222175514.GA17658@ravnborg.org> (raw)
In-Reply-To: <8e786abe-cd51-63a4-9dd6-b83360b3f928@phytec.de>

Hi Christian,

thanks for the quick reply.

> >Can you give any hints that makes it simpler to verify your fix or anything?
> To reproduce the issue and test the fix I reseted the board in a loop.
> For this I added 'reset' to /env/bin/init. With 'reset" in /env/bin/init I
> saw the issue after 1 - 2 Minutes.
> Also I have done 1000 power cuts and resets without any error in our
> test rack.
> 
> power cut:
> 1. start barebox to prompt
> 2. power cut
> 
> soft reset:
> 1. start barebox to prompt
> 2. reset

We have deployed an updated barebox in our test setup that do
all our ON/OFF testing.
A quick grep from the serial logs shows that we have seen this
error message much more often than I originally anticipated.
So I expect to have feedback already tomorrow.

From your information I am quite positive.

	Sam

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-12-22 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 21:38 [PATCH] mtd: nand_mxs: fix NAND error when change clk rate Christian Hemp
2016-12-21 22:29 ` Sam Ravnborg
2016-12-22  8:50   ` Christian Hemp
2016-12-22 17:55     ` Sam Ravnborg [this message]
2016-12-23 10:39 ` Sam Ravnborg
2016-12-27 17:07 ` Fabio Estevam
2017-01-09 10:21 ` Sascha Hauer
2017-08-21 16:26   ` Uwe Kleine-König
2017-08-21 16:31     ` Fabio Estevam

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=20161222175514.GA17658@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=barebox@lists.infradead.org \
    --cc=c.hemp@phytec.de \
    /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.