From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] bootm: Use "panic()" in non-recoverable error conditions
Date: Thu, 20 Oct 2011 21:31:25 +0200 [thread overview]
Message-ID: <20111020193125.E7D02158D103@gemini.denx.de> (raw)
In-Reply-To: <1319134031-28503-1-git-send-email-Kyle.D.Moffett@boeing.com>
Dear Kyle Moffett,
In message <1319134031-28503-1-git-send-email-Kyle.D.Moffett@boeing.com> you wrote:
> All of these errors are various kinds of fatal memory overwrite
> conditions and so should be handled by panic(). This fixes a bug in
> which the error message might not get all the way out to the serial
> console before the system reboots; panic() has a built-in delay after
> doing a printf() before calling do_reset().
>
> This will result in a change in behavior for the 27 board configuration
> files which set CONFIG_PANIC_HANG (less than 5% of the total). They
> will now hang in those fatal error conditions instead of trying to
> reboot.
>
> Given that CONFIG_PANIC_HANG is intended to prevent the system from
> rebooting after it has encountered an unrecoverable error, this seems to
> be the desired behavior for those 27 board configurations.
This is your interpretation, but the users and especially the
respective board maintainers may think different. We should at least
try and get feedback from them first.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
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
It's all Klatchian to me.
- Terry Pratchett & Stephen Briggs, _The Discworld Companion_
next prev parent reply other threads:[~2011-10-20 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 18:07 [U-Boot] [PATCH] bootm: Use "panic()" in non-recoverable error conditions Kyle Moffett
2011-10-20 19:31 ` Wolfgang Denk [this message]
2011-10-20 20:06 ` Moffett, Kyle D
2011-10-21 21:35 ` Albert ARIBAUD
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=20111020193125.E7D02158D103@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