public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Make U-Boot log great again
Date: Sun, 18 Feb 2018 22:22:14 +0100	[thread overview]
Message-ID: <20180218212214.2D64A24018D@gemini.denx.de> (raw)
In-Reply-To: <CAKaJLVsWKpGeEuS=iZ7QCtZrDfUSA=8GZo3zJDr-VgW-MUCFzA@mail.gmail.com>

Dear Sam,

In message <CAKaJLVsWKpGeEuS=iZ7QCtZrDfUSA=8GZo3zJDr-VgW-MUCFzA@mail.gmail.com> you wrote:
> 
> Right now U-Boot and SPL logs are cluttered with bogus warnings like
> these (on X15 board, but I'm pretty sure it should appear on many
> others):
> 
>     Loading Environment from FAT...
>     *** Warning - bad CRC, using default environment

I donpt want to question the purpose of your patch series in genral,
but:

This is NOT a bogus warning - actually it is something which is not
supposed to happen on any sane system.  If it does on your board
even after first boot and running "env save" at least once, then you
have some problem either in the design or implementation of your
board code.

So this is a very valid warning which means: FIX ME!

>  1. If we have two sources for the environment (e.g. FAT partition on
> SD card and some raw partition on eMMC), we shouldn't print error
> messages if we were unable to load the environment from one source

This needs specification.

If there are several potential sources for the environment, it can
be assumed that the first one is supposed to be the primary one, so
if this does not work, there _should_ be a warning (or even error)
message before U-Boot falls back to alternative storage.

However, in such a case the "using default environment" is
apparently wrong...


>  2. We should probably print some human-readable information that we
> didn't find the environment there, let's skip and look for next source
> (but don't print those warnings/failed messages)

For any attempt to read the environment from some storage device
which fails, a warning SHALL be printed, because this is not
supposed to happen.

>  3. And only print the error message in case when U-Boot environment
> wasn't found at all (on all possible sources).

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
When in doubt, mumble;   when in trouble, delegate;  when in  charge,
ponder.                                             -- James H. Boren

  parent reply	other threads:[~2018-02-18 21:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 19:01 [U-Boot] [RFC] Make U-Boot log great again Sam Protsenko
2018-02-16 19:49 ` Robert Nelson
2018-03-23  5:44   ` Bin Meng
2018-07-10  3:01     ` Bin Meng
2018-07-10 14:38       ` Tom Rini
2018-07-11 14:51         ` Sam Protsenko
2018-07-17 22:14         ` Sam Protsenko
2018-07-18 21:41           ` Sam Protsenko
2018-02-18 21:22 ` Wolfgang Denk [this message]
2018-02-19 17:47   ` Sam Protsenko
2018-02-19 19:09     ` Wolfgang Denk
2018-02-20  8:00     ` Maxime Ripard
2018-02-20  9:59       ` Lukasz Majewski
2018-02-21 13:35         ` Tom Rini
2018-02-21 13:55           ` Maxime Ripard
2018-02-21 14:59             ` Tom Rini
2018-02-21 14:38           ` Simon Goldschmidt
2018-02-21 14:54             ` Tom Rini
2018-02-21 15:03               ` Simon Goldschmidt
2018-02-21 15:07               ` Maxime Ripard
2018-02-21 15:14                 ` Tom Rini
2018-02-22 13:33                   ` Maxime Ripard
2018-02-24 20:52         ` Wolfgang Denk

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=20180218212214.2D64A24018D@gemini.denx.de \
    --to=wd@denx.de \
    --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