grsecurity forums

I am referring to: viewtopic.php?f=3&t=2156

Today i tried this latest grsecurity-2.1.14-2.6.29.6-200907122214.patch. It ended up with BUG: Int 14: CR2. Please see this screenshot: http://www.gameframe.net/files/misc/grsec.png

Here is my kernel vmlinuz image and kernel .config file: http://www.gameframe.net/files/misc/grsec.zip

Any grsec patch after 2.6.28.5 up to latest 2.6.29.6 has caused this same error. Motherboards tried with this same error: Asus P5E and Intel DP965LT

Each kernel without grsec reboots normally. However i tried this today also with my XEON X5450 server which rebooted OK with the latest grsec patch. However since this many grsec version is affected, i believe this is grsec related bug since any mentione kernel between 2.6.28.5 - 2.6.29.6 reboots without this Int 14 error when grsec is not patched to the kernel.

I have found with google that this is anyway Asus related bug as you can see from: https://bugs.launchpad.net/ubuntu/+sour ... /+activity

This very same error occurs also with Intel DP965LT though. Kinda nasty stuff..hopefully the information i have provided is enough to fix this. I really do love grsec!

Thank you already in advance for fixing this.

PS. Server in this article worked perfectly with the latest grsec patch: http://gameframe.net/EN/?page=dual-xeon ... erver-test

Looks like it´s better stay with real server hardware since everything works smoother and more stable :)

GameFrame wrote:Here is my kernel vmlinuz image and kernel .config file: http://www.gameframe.net/files/misc/grsec.zip

could you send me the original vmlinux file instead (it has all the symbol info and is much more useful than the bzImage)?

This is from grsec kernel source directory: http://www.gameframe.net/files/misc/vmlinux

Stupid me, bzimage is course the packed version of this vmlinuz :)

GameFrame wrote:This is from grsec kernel source directory: http://www.gameframe.net/files/misc/vmlinux

ok, the next test patch will hopefully fix it, at least your config boots in qemu whereas the original image didn't.

The updated test patch is now online, let us know if you have any problems.

-Brad

Thank you and the rest of grsec team. With the latest patch, this mysterious INT14 problem is gone and kernel rebooted perfectly on this Asus P5E machine. Worked also fine
on my Dual X5450 server which is 64bit.

I even tested both machines with TCP blackhole feature on and there was no kernel panics even when i fully utilized both servers network on 1Gbit LAN. Good work!

My financial situation is currently pretty bad but i will surely donate sooner or later.