mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: i.sapozhnikov@prosoftsystems.ru
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Problem booting Linux v4.8.15 from NAND on using Barebox
Date: Thu, 19 Jul 2018 23:12:47 -0700	[thread overview]
Message-ID: <CAHQ1cqHMR7QUBtN0fjeOGhxytRapcBnWT+T5USbfKFePck8r=g@mail.gmail.com> (raw)
In-Reply-To: <316743f1814b446db9947e95ff843168@prosoftsystems.ru>

On Thu, Jul 19, 2018 at 10:47 PM Сапожников Игорь Валерьевич
<i.sapozhnikov@prosoftsystems.ru> wrote:
>
> Hello. I use barebox v2017.07.0 and I getting trouble with loading Linux kernel v4.8.15 after flashing to NAND and rebooting system. I checked Linux image located in NAND through md5sum program in barebox and Linux . In barebox md5sum return value differ from value in Linux. I read linux image from НАНД of Barebox and Linux, then compared their by xxd program. In copy from barebox I got bit-flip errors. It error is not manifested every time after flashing and rebooting system. Usually I needed about 150 reboots. Afterwards I began to use barebox v2018.07.0 and after 5000 rebooting system, I not getting error. Can you tell me what the error was fixed in new build? And can you send me commit id from git where fixed error?
>

Igor:

IMHO, this really sounds like a question to "git bisect" rather than
to the list. I hope you are lucky enough that someone would know the
answer off the top of their head, but I'd still suggest you start
bisecting. Fhis way you'll get your answer even if your question will
never be answered on the list.

Thanks,
Andrey Smirnov

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

      reply	other threads:[~2018-07-20  6:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20  5:47 Сапожников Игорь Валерьевич
2018-07-20  6:12 ` Andrey Smirnov [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='CAHQ1cqHMR7QUBtN0fjeOGhxytRapcBnWT+T5USbfKFePck8r=g@mail.gmail.com' \
    --to=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=i.sapozhnikov@prosoftsystems.ru \
    /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