Ronald, Was the kernel compiled with -fstack-protector?
Try running this on target: cat /proc/kallsyms | grep __stack_chk_fail Does it output the symbol address? Take a look here: http://lxr.free-electrons.com/source/kernel/panic.c#L558 Best regards 2016-09-13 19:14 GMT-03:00 Ronald Oakes <rona...@brc2.com>: > That resolved my problem. (And while I was at it, I found that I had > failed to create a new .bbappend file to pull my custom kernel config > file in when I had to change to an older kernel version due to kernel > versions supported by the vendor - so I had none of my other kernel > configurations either). > > Ron Oakes. > > On Tue, Sep 13, 2016 at 1:29 PM, robert.berger@gmane > <gm...@reliableembeddedsystems.com> wrote: >> Hi, >> >> On 2016-09-13 21:55, Ronald Oakes wrote: >>> >>> >>> Any ideas how to proceed? >> >> >> 1) Can you try to use it from an in-tree kernel module? (modify the >> attachment) >> >> 2) Can you grep in your kernel config for >> >> CONFIG_CC_STACKPROTECTOR and friends? >> >> Regards, >> >> Robert >> >> >> >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- "Do or do not. There is no try" Yoda Master -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto