(without changing the config, saw the reply from spender too late)
dmesg right after boot: https://paste.foxxx0.de/47TWf/
after triggering the panic: https://paste.foxxx0.de/oke/
I will try with GRKERNSEC_KERN_LOCKOUT disabled tomorrow again.
foxxx0 wrote:Alright, so:
4.6.4.r201607112205 is working just fine
4.7.0.r201608131240 is broken
So the issue (at least for me) was introduced in 4.7.0.
Unfortunately I have no later 4.6.x kernels that I could test, so >4.6.4.r201607112205 and <= 4.7.0.r201608131240 is the range where the issue was introduced.
sys-kernel/hardened-sources-4.7.5
sys-kernel/hardened-sources-4.7.6
sys-kernel/hardened-sources-4.7.7
spender wrote:When you reboot without GRKERNSEC_KERN_LOCKOUT, can you also change the %pS to %pA ?
-Brad
PaX Team wrote:what's addr2line -e build_dir/vmlinux -fip ffffffff81419a98 say?
$ addr2line -e src/linux-4.7/vmlinux -fip ffffffff81419a98
show_type at bgrt.c:?
PaX Team wrote:thanks, that was enough to identify the problem, all the sysfs callbacks in drivers/acpi/bgrt.c have the wrong type, i'll fix them in the next patch. for next time, you could enable the DEBUG_INFO options.
@Miroslav: your problem is something unrelated, please keep that discussion in the other thread (or at https://bugs.gentoo.org/show_bug.cgi?id=597554 which is where it was already reported).