grsecurity forums

Hi,
I can't boot 2.6.30.4 kernel with grsecurity patch applied (amd64, Lenovo N200 0769-BJG laptop). It completly locks the computer (sysrq key not working, I must turn it of by holding power button for several secs).
Here's the screenshot http://dunaonline.com/screenshot.jpg
And kernel config: http://dunaonline.com/config
If you need any more info, please let me know, I'll try to get it :)

Can you also post the vmlinux file (the one from your source directory)?

-Brad

Here it is: dunaonline.com/vmlinux

Mrkva wrote:Here it is: dunaonline.com/vmlinux

could you capture the full boot log, or at least the first oops somehow (try boot_delay=xxx if all else fails)?

I'm able to reproduce the problem you're having with the config you provided. There's no OOPs message or anything involved in it, which is making it difficult to debug. The current 2.6.30.4 patch that's been uploaded doesn't fix your particular problem, but we'll continue working on it until it's solved.

-Brad

Well, if you need any cooperation from me, let me know. Tell me, if you need the whole boot log - if so, It'll be a lot of photos - or maybe it's possible to capture it with 1394 (but I don't know, I've never did this before). It panics (Unable to allocate grsecurity shared page, but the panic message is immediatly followed by another error messages - and without boot_delay, I wasn't able to see it). Or is it caused by any known incompatibility with any kernel option?
Thanks for all your help!

That particular panic (gr_shared_page) shouldn't happen with the latest patch. Have you tried it?

There seems to be a problem unrelated to that that must have something to do with your particular configuration. I've been trying to binary search through the differences in options between your config and a working x64 config (and have ruled out a large number of options) but haven't come up with the culprit yet.

-Brad

Mrkva wrote:Well, if you need any cooperation from me, let me know. Tell me, if you need the whole boot log - if so, It'll be a lot of photos - or maybe it's possible to capture it with 1394 (but I don't know, I've never did this before).

as spender said, the grsec shared page allocation should be fixed, beyond that, all i need really is the first oops, everything else later is collateral damage probably . you can also try netconsole if it's already usable at that point or just boot_delay.

Hi,
I think I have the same problem with the latest patch (grsecurity-2.1.14-2.6.30.4-200908041752.patch). Without having netconsole enabled, it crashes right after 'freeing unused kernel memory' message. The error can be seen here: http://radegand.obiezyswiat.pl/main.php?g2_itemId=6246

After enabling netconsole it crashes right at the 'freeing unused kernel memory' instead ;). No oops are reported and netconsole doesn't capture any error (last message sent is: Freeing unused kernel memory: 600k freed), however last message displayed on the screen is this: (right below the 'Freeing...')
general protection fault: 000 [#1]
Which isn't probably very useful ;)

Complete bootlog can be found here: http://pastebin.com/m3dcdff62

And my kernel config is here: http://pastebin.com/m65429ad6

Let me know if there's more info needed. I'll play around with different grsec options enabled in the meantime, maybe it will help to narrow it down at least...
Cheers

Well,with the latest patch, system reboots after

Code: Select all

VFS: Mounted root (reiserfs filesystem) readonly on device 8(or 0, not sure):1.
Freeeing unused kernel memory: 312k freed

Here's first oops from previous kernel: dunaonline.com/oops.jpg
radegand: I'm not sure whether this is the same problem - at least, I don't have any null pointer dereference error, nor regular oops. (just general protection fault and registry dump.
Update: It still reboots when I disable any PAX or GRKERSEC related config option, but I'm not sure it'll help you searching for this bug:

Code: Select all

root@Odyssey:/usr/src/linux-2.6.30.4-grsec# egrep "PAX|GRKER" .config
# CONFIG_GRKERNSEC is not set
# CONFIG_PAX_MEMORY_SANITIZE is not set


radegand wrote:Let me know if there's more info needed. I'll play around with different grsec options enabled in the meantime, maybe it will help to narrow it down at least...

can you send me your vmlinux please?

PaX Team wrote:can you send me your vmlinux please?

even better, can you guys try the latest test patch? i think i fixed the problems.

Works for me. You guys are really doing a great job! Thanks!

Brad, I confirm the same behavior when booting my 2.6.30.4 with grsecurity-2.1.14-2.6.30.4-200908011535.patch.
I have some difficult to catch the output from console due to the fact that my P4 has no more tty external interface.
But i can then to you me configuration if you think it is able to help you.
best regards

Jeanmarc wrote:Brad, I confirm the same behavior when booting my 2.6.30.4 with grsecurity-2.1.14-2.6.30.4-200908011535.patch.
I have some difficult to catch the output from console due to the fact that my P4 has no more tty external interface.
But i can then to you me configuration if you think it is able to help you.
best regards

Try the latest test patch (grsecurity-2.1.14-2.6.30.4-200908051916.patch) - it works for me.