Segmentation Fault on Boot

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

Segmentation Fault on Boot

Postby godlkwrth » Fri Sep 28, 2007 9:18 pm

On this amd Opteron system (2-way) I am unable to get the system to boot with Security Level set to "High". I am using kernel 2.6.19.2 and the latest stable grsecurity patch. It's a 64bit kernel with SMP enabled and I'm assuming it's crashing upon loading init (although I have no way to verify this, all I see is about ten thousand Segmentation Fault messages). I think I had a problem like this before, but was able to disable COMPAT_VDSO and get the system to boot, but I no longer see this option (I suppose because it's a 64bit kernel).
godlkwrth
 
Posts: 1
Joined: Fri Sep 28, 2007 9:12 pm

Postby Kp » Sat Sep 29, 2007 4:04 pm

What distribution are you using, and are you up to date on patches for it?

If you have time, try using the Custom security level to enable individual features. Start with all features enabled by Medium security, and verify that the system boots successfully. If it does, add half of the features that are in High but not in Medium. Test whether the system boots. If yes, add more features. If not, remove some features. Eventually, you should be able to find the feature(s) that cause the error. Knowing this can guide the developers, and may even reveal that you do not actually need the feature that causes the failure.

You can find what features are in each level by looking at the select statements for GRKERNSEC_MEDIUM and GRKERNSEC_HIGH in /usr/src/linux/grsecurity/Kconfig.
Kp
 
Posts: 46
Joined: Tue Sep 20, 2005 12:56 am


Return to grsecurity support

cron