Looks like it got changed here:
commit 749918911d35613f8bf7852d2a91f78ff625739e
Author: Felix Fietkau
Date: Fri Jan 13 14:48:25 2017 +0100
x86: disable crashlog
It could cause crashes with some forms of virtualization, and it is
unlikely to work properly with most systems.
depends on !(arm || powerpc || sparc || TARGET_uml || i386 || x86_64)
x86_64 is disabled by default. You may want to enable it yourself. I
don't know why.
Best Regards,
Syrone Wong
On Fri, Mar 3, 2017 at 2:31 PM, Philip Prindeville
wrote:
> I built an x86_64 image and turned on crash logging,
I built an x86_64 image and turned on crash logging, and then forced a crash
with:
echo c >/proc/sysrq-trigger
it rebooted, but when it did there was nothing in /sys/kernel/debug/ (i.e. no
crashlog file).
What am I missing? Does this not work with x86_64?
-Philip
> On Feb 23, 2017, at 10:2
Thanks for that.
> On Feb 22, 2017, at 11:44 PM, Syrone Wong wrote:
>
> According to LEDE's source code:
>
> config KERNEL_CRASHLOG
> bool "Crash logging"
> depends on !(arm || powerpc || sparc || TARGET_uml || i386 || x86_64)
> default y
>
> https://github.com/lede-project/source/blob/mas
According to LEDE's source code:
config KERNEL_CRASHLOG
bool "Crash logging"
depends on !(arm || powerpc || sparc || TARGET_uml || i386 || x86_64)
default y
https://github.com/lede-project/source/blob/master/config/Config-kernel.in
It is enabled by default on some targets and will be avail
