All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: Wolfgang Denk <wd@denx.de>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"Brunck, Holger" <Holger.Brunck@keymile.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Bigler, Stefan" <Stefan.Bigler@keymile.com>
Subject: Re: Possible race condition when accessing SPI NOR Flash ?
Date: Fri, 02 May 2014 08:18:34 +0200	[thread overview]
Message-ID: <536338BA.3040201@keymile.com> (raw)
In-Reply-To: <20140501223126.E4CD63809A5@gemini.denx.de>

Hello Wolfgang,

On 05/02/2014 12:31 AM, Wolfgang Denk wrote:
> Dear Valentin,
> 
> In message <53623597.8040909@keymile.com> you wrote:
>>
>> Now when fw_setenv ([1], [2]) updates the environment variables, it sometimes
>> (approximately 1 out of 100 runs) triggers such kernel errors:
> ...
>> I see the same behavior with both the 2013.10 and the 2014.04 releases of
>> u-boot/fw_env. The kernel we are using is 3.10.36.
>>
>> I suspect that the problem is related to SPI NOR/m25p80 driver: on the system we
>> have a NAND Flash device with UBI volumes. If I create 2 ubi volumes on the NAND
>> Flash and configure fw_setenv (/etc/fw_env.config) to use them instead of the
>> the mtd devices targetting the s25fl256s1, I am not able to reproduce the
>> problem, even over more than 10'000 runs.
> 
> Um... this is _Linux_ crashing - at this point the U-Boot driver has
> nothing to do with it..  If there is a problem, then with the Linux
> kernel / driver code.  I guess you should rather post this on the MTD
> mailing ist.
> 

Yes, it was clear for me that this is Linux crashing, as I write "it [..]
triggers [..] kernel errors." I have posted it to the linux-mtd ML, I have just
added the u-boot ML as CC since fw_env is u-boot code and it triggers it, so I
though it could be of interest.

Best regards,

Valentin

WARNING: multiple messages have this Message-ID (diff)
From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Possible race condition when accessing SPI NOR Flash ?
Date: Fri, 02 May 2014 08:18:34 +0200	[thread overview]
Message-ID: <536338BA.3040201@keymile.com> (raw)
In-Reply-To: <20140501223126.E4CD63809A5@gemini.denx.de>

Hello Wolfgang,

On 05/02/2014 12:31 AM, Wolfgang Denk wrote:
> Dear Valentin,
> 
> In message <53623597.8040909@keymile.com> you wrote:
>>
>> Now when fw_setenv ([1], [2]) updates the environment variables, it sometimes
>> (approximately 1 out of 100 runs) triggers such kernel errors:
> ...
>> I see the same behavior with both the 2013.10 and the 2014.04 releases of
>> u-boot/fw_env. The kernel we are using is 3.10.36.
>>
>> I suspect that the problem is related to SPI NOR/m25p80 driver: on the system we
>> have a NAND Flash device with UBI volumes. If I create 2 ubi volumes on the NAND
>> Flash and configure fw_setenv (/etc/fw_env.config) to use them instead of the
>> the mtd devices targetting the s25fl256s1, I am not able to reproduce the
>> problem, even over more than 10'000 runs.
> 
> Um... this is _Linux_ crashing - at this point the U-Boot driver has
> nothing to do with it..  If there is a problem, then with the Linux
> kernel / driver code.  I guess you should rather post this on the MTD
> mailing ist.
> 

Yes, it was clear for me that this is Linux crashing, as I write "it [..]
triggers [..] kernel errors." I have posted it to the linux-mtd ML, I have just
added the u-boot ML as CC since fw_env is u-boot code and it triggers it, so I
though it could be of interest.

Best regards,

Valentin

  reply	other threads:[~2014-05-02  6:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01 11:52 Possible race condition when accessing SPI NOR Flash ? Valentin Longchamp
2014-05-01 22:31 ` Wolfgang Denk
2014-05-01 22:31   ` [U-Boot] " Wolfgang Denk
2014-05-02  6:18   ` Valentin Longchamp [this message]
2014-05-02  6:18     ` Valentin Longchamp
2014-05-02 11:40 ` Mark Marshall
2014-05-02 11:40   ` [U-Boot] " Mark Marshall
2014-05-02 14:52   ` Valentin Longchamp
2014-05-02 14:52     ` Valentin Longchamp

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=536338BA.3040201@keymile.com \
    --to=valentin.longchamp@keymile.com \
    --cc=Holger.Brunck@keymile.com \
    --cc=Stefan.Bigler@keymile.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=u-boot@lists.denx.de \
    --cc=wd@denx.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.