From: Vladimir Zapolskiy <vz@mleia.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Sylvain Lemieux <slemieux.tyco@gmail.com>
Subject: [PATCH 3/6] ARM: defconfig: lpc32xx: enable panic on oops option
Date: Sat, 26 Jan 2019 00:03:45 +0200 [thread overview]
Message-ID: <20190125220348.5357-4-vz@mleia.com> (raw)
In-Reply-To: <20190125220348.5357-1-vz@mleia.com>
Panic on oops option enabled by by default makes great sense both
for debugging and production.
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
---
arch/arm/configs/lpc32xx_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/lpc32xx_defconfig b/arch/arm/configs/lpc32xx_defconfig
index 4649cb04dec7..0504eee8632c 100644
--- a/arch/arm/configs/lpc32xx_defconfig
+++ b/arch/arm/configs/lpc32xx_defconfig
@@ -194,6 +194,8 @@ CONFIG_DEBUG_INFO=y
CONFIG_GDB_SCRIPTS=y
CONFIG_DEBUG_FS=y
CONFIG_MAGIC_SYSRQ=y
+CONFIG_PANIC_ON_OOPS=y
+CONFIG_PANIC_TIMEOUT=5
# CONFIG_SCHED_DEBUG is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_FTRACE is not set
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-25 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 22:03 [PATCH 0/6] ARM: defconfig: lpc32xx: update NXP LPC32xx defconfig Vladimir Zapolskiy
2019-01-25 22:03 ` [PATCH 1/6] ARM: defconfig: lpc32xx: enable NFSv4 support Vladimir Zapolskiy
2019-01-25 22:03 ` [PATCH 2/6] ARM: defconfig: lpc32xx: enable build options for basic debugging Vladimir Zapolskiy
2019-01-25 22:03 ` Vladimir Zapolskiy [this message]
2019-01-25 22:03 ` [PATCH 4/6] ARM: defconfig: lpc32xx: enable serial console on HS UART Vladimir Zapolskiy
2019-01-25 22:03 ` [PATCH 5/6] ARM: defconfig: lpc32xx: enable generic SRAM driver Vladimir Zapolskiy
2019-01-25 22:03 ` [PATCH 6/6] ARM: defconfig: lpc32xx: disable superfluous GPIO controllers Vladimir Zapolskiy
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=20190125220348.5357-4-vz@mleia.com \
--to=vz@mleia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=slemieux.tyco@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).