Startup failure - 2.6.29.2-grsec/2.6.29.3-grsec
Posted: Thu May 14, 2009 6:18 amHello,
I have tried both 2.6.29.2 and 2.6.29.3 vanilla kernels with just the grsec patch on my MSI notebook. Compilation works fine, I am just updating from 2.6.24.4-grsec which worked just fine for over 1 year. Installation also works fine, but when I reboot I get the following messages:
Using IPI shortcut mode
modprobe[387] segfault at ffffe01c ip ac14237f sp bbbf572c error 5 in ld-linux.so2[a44220000+1a000]
Freeing unused kernel memory: 6140k freed
init[1] segfault at ffffe01c ip ac14237f sp bbbf572c error 5 in ld-linux.so2[c140000+1a000]
grsec: signal 11 sent to /init [snip ... snip]
Kernel panic - not syncing: Attempted to kill init!
I am now compiling the kernel w/out the grsec patch to see if indeed grsec is to blame.
My grsec security level is Medium.
Update: When I compile 2.6.29.3 w/out the grsec patch, install it and reboot, I have no problems, so it means the grsec patch is to blame.
Update2: Disabled PAX, and set GrSecurity to Custom, same problem as above.
Update3: Ok, I disabled GrSecurity and I also Disabled PAX, and I still encounter the problem above, so the patch does something to the kernel source code which causes the segfaults.
My hardware is: http://us.msi.com/NB/product_spec.asp?model=MS-163C
My kernel configuration is: http://www.sendspace.com/file/gnwflz
I have tried both 2.6.29.2 and 2.6.29.3 vanilla kernels with just the grsec patch on my MSI notebook. Compilation works fine, I am just updating from 2.6.24.4-grsec which worked just fine for over 1 year. Installation also works fine, but when I reboot I get the following messages:
Using IPI shortcut mode
modprobe[387] segfault at ffffe01c ip ac14237f sp bbbf572c error 5 in ld-linux.so2[a44220000+1a000]
Freeing unused kernel memory: 6140k freed
init[1] segfault at ffffe01c ip ac14237f sp bbbf572c error 5 in ld-linux.so2[c140000+1a000]
grsec: signal 11 sent to /init [snip ... snip]
Kernel panic - not syncing: Attempted to kill init!
I am now compiling the kernel w/out the grsec patch to see if indeed grsec is to blame.
My grsec security level is Medium.
Update: When I compile 2.6.29.3 w/out the grsec patch, install it and reboot, I have no problems, so it means the grsec patch is to blame.
Update2: Disabled PAX, and set GrSecurity to Custom, same problem as above.
Update3: Ok, I disabled GrSecurity and I also Disabled PAX, and I still encounter the problem above, so the patch does something to the kernel source code which causes the segfaults.
My hardware is: http://us.msi.com/NB/product_spec.asp?model=MS-163C
My kernel configuration is: http://www.sendspace.com/file/gnwflz
, not that anyone should be using it these days...