will attached a photo with the crash as soon as the battery of my cam is charged. My system is a ThinkPad T440s. FWIW I had to comment out #GRUB_GFXPAYLOAD_LINUX=keep in /etc/default/grub - to see the crash otherwise just grub2's graphic screen would be shown.
Created attachment 393888 [details] crash FWIW gentoo-3.18.2 boots fine
Do reopen this bug report when you have found the actual error.
(In reply to Jeroen Roovers from comment #2) > Do reopen this bug report when you have found the actual error. I'm confused jer. He hit a kernel panic on boot. That is his bug. There's more info he can give me (and I'll ask for that) but why close it now? I would close this needinfo after I ask and he can't provide anything to narrow it down. @Toralf. Can you try to get the whole panic using netconole? https://wiki.archlinux.org/index.php/Netconsole Also upstream will want yor vmlinux and config. Note: hardened-sources-3.18.2 = grsecurity-3.0-3.18.2-201501120821
Created attachment 393892 [details] /usr/src/linux-3.18.2-hardened/.config FWIW 3.18.1-hardened-r1 fails too, so rather a 3.17->3.18 thing than a (minor)regressions between .1 and .2
i think it's the kernfs related breakage that was fixed since, can you try the latest grsec patch please?
doh, misread the grsec version, ignore me. so we'll need the full oops, switching to a higher resolution framebuffer mode would work too if netconsole/etc aren't feasible.
And vmlinuz can be downloaded from here (3.2 MiB): http://www.zwiebeltoralf.de/pub/vmlinuz-3.18.2-hardened Never dealt with netconsole before - will try it.
what we need is not vmlinuz (the compressed kernel image you boot) but vmlinux from the build root dir (because it has full debug info that helps further analysis). you could also resolve the RIP for us in the meantime: addr2line -e vmlinux -fip ffffffff8153b399
i managed to reproduce the problem with your config, it's the new SCHED_STACK_END_CHECK config option that triggers something, i'm debugging it now.
so this is due to STACKLEAK overwriting the STACK_END_MAGIC as part of clearing the kernel stack. it's a feature collision, i'll think of something to resolve it.
well, I unchecked the modules option, so http://www.zwiebeltoralf.de/public_html/pub/ contains now 2 photos from the crash of a 1920x1080 screen - should give more info (DESC0555[23].JPG) at that location.
(In reply to PaX Team from comment #8) > what we need is not vmlinuz (the compressed kernel image you boot) but > vmlinux from the build root dir (because it has full debug info that helps > further analysis). you could also resolve the RIP for us in the meantime: > > addr2line -e vmlinux -fip ffffffff8153b399 will upload the vmlinux (no modules) to, here : addr2line -e vmlinux -fip ffffffff81b2ef29 __schedule at core.c:?
i fixed the problem, the latest PaX patch has the fix, grsec will follow soon.
(In reply to Toralf Förster from comment #11) > well, I unchecked the modules option, so > http://www.zwiebeltoralf.de/public_html/pub/ > contains now 2 photos from the crash of a 1920x1080 screen - should give > more info (DESC0555[23].JPG) at that location. grr, I meant http://www.zwiebeltoralf.de/pub/
-r1 boots fine here thx