summaryrefslogtreecommitdiff
path: root/arch/arc/boot/dts/nsim_hs.dts
diff options
context:
space:
mode:
authorAlexey Brodkin <abrodkin@synopsys.com>2018-01-18 16:48:47 +0300
committerVineet Gupta <vgupta@synopsys.com>2018-01-18 10:51:27 -0800
commit8ff3afc159f26e44471e174077e6d16cd2a2bb91 (patch)
tree61073b3f16a48c6c6caf8c51fbe7549e2d38dbbb /arch/arc/boot/dts/nsim_hs.dts
parenta3142792f79884b867b7bf4c7d5a126a0f913332 (diff)
ARC: Enable fatal signals on boot for dev platforms
It's very convenient to have fatal signals enabled on developemnt platform as this allows to catch problems that happen early in user-space (like crashing init or dynamic loader). Otherwise we may either enable it later from alive taregt console by "echo 1 > /proc/sys/kernel/print-fatal-signals" but: 1. We might be unfortunate enough to not reach working console 2. Forget to enable fatal signals and miss something interesting Given we're talking about development platforms here it shouldn't be a problem if a bit more data gets printed to debug console. Moreover this makes behavior of all our dev platforms predictable as today some platforms already have it enabled and some don't - which is way too inconvenient. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Diffstat (limited to 'arch/arc/boot/dts/nsim_hs.dts')
-rw-r--r--arch/arc/boot/dts/nsim_hs.dts2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arc/boot/dts/nsim_hs.dts b/arch/arc/boot/dts/nsim_hs.dts
index 8d787b251f73..8e2489b16b0a 100644
--- a/arch/arc/boot/dts/nsim_hs.dts
+++ b/arch/arc/boot/dts/nsim_hs.dts
@@ -24,7 +24,7 @@
};
chosen {
- bootargs = "earlycon=arc_uart,mmio32,0xc0fc1000,115200n8 console=ttyARC0,115200n8";
+ bootargs = "earlycon=arc_uart,mmio32,0xc0fc1000,115200n8 console=ttyARC0,115200n8 print-fatal-signals=1";
};
aliases {