diff options
| author | Alexey Brodkin <abrodkin@synopsys.com> | 2018-01-18 16:48:47 +0300 |
|---|---|---|
| committer | Vineet Gupta <vgupta@synopsys.com> | 2018-01-18 21:51:27 +0300 |
| commit | 8ff3afc159f26e44471e174077e6d16cd2a2bb91 (patch) | |
| tree | 61073b3f16a48c6c6caf8c51fbe7549e2d38dbbb /arch/arc/boot/dts/axs101.dts | |
| parent | a3142792f79884b867b7bf4c7d5a126a0f913332 (diff) | |
| download | linux-8ff3afc159f26e44471e174077e6d16cd2a2bb91.tar.xz | |
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/axs101.dts')
| -rw-r--r-- | arch/arc/boot/dts/axs101.dts | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arc/boot/dts/axs101.dts b/arch/arc/boot/dts/axs101.dts index 70aec7d6ca60..626b694c7be7 100644 --- a/arch/arc/boot/dts/axs101.dts +++ b/arch/arc/boot/dts/axs101.dts @@ -17,6 +17,6 @@ compatible = "snps,axs101", "snps,arc-sdp"; chosen { - bootargs = "earlycon=uart8250,mmio32,0xe0022000,115200n8 console=tty0 console=ttyS3,115200n8 consoleblank=0 video=1280x720@60"; + bootargs = "earlycon=uart8250,mmio32,0xe0022000,115200n8 console=tty0 console=ttyS3,115200n8 consoleblank=0 video=1280x720@60 print-fatal-signals=1"; }; }; |