From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Recent commit to env_nand.c causing saveenv to hang
Date: Fri, 07 Sep 2012 13:18:48 -0600 [thread overview]
Message-ID: <504A4898.5030707@wwwdotorg.org> (raw)
In-Reply-To: <CA+V-a8vMF+StVik4u3moO1Tksn_8KTV4inigtBDPCNM2GsoH2A@mail.gmail.com>
On 09/07/2012 10:44 AM, Prabhakar Lad wrote:
> On Fri, Sep 7, 2012 at 9:35 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 09/07/2012 06:17 AM, Prabhakar Lad wrote:
>>> Hi Stephen,
>>>
>>> I checked out the latest code and try flashing on DM355 for NAND boot mode,
>>> I saw that saveenv was causing a hang. A little debugging pointed me to
>>> this patch http://patchwork.ozlabs.org/patch/174069/ reverting this
>>> patch saveenv
>>> works fine.
>>> Has this patch being tested ? Or is that I am missing out some where.
>>
>> Yes, I've definitely used this on the NVIDIA Tegra Harmony board.
>>
>> I tested the patch on top of repo u-boot-tegra.git branch master, but
>> the patch ended up getting applied directly by Wolfgang to u-boot.git. I
>> don't think that should cause any issues though; the patch shouldn't be
>> dependant on anything Tegra-specific.
>>
>> I just re-tested to make sure. The exact code I tested is at:
>> git at github.com:swarren/u-boot.git mainline_dev
>>
>> Do you have any clue why it's hanging or crashing? Perhaps you can add
>> some debug statements to see exactly where it's happening?
>
> I added some debug statements and saw that in hexport_r() function
> where memset(res, '\0', size); is done this where it hangs :(.
> hope this might help.
For the list archives: I believe the following patch should fix this:
http://lists.denx.de/pipermail/u-boot/2012-September/133476.html
Sorry for the breakage.
prev parent reply other threads:[~2012-09-07 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 12:17 [U-Boot] Recent commit to env_nand.c causing saveenv to hang Prabhakar Lad
2012-09-07 16:05 ` Stephen Warren
2012-09-07 16:44 ` Prabhakar Lad
2012-09-07 19:18 ` Stephen Warren [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=504A4898.5030707@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox