grsecurity-2.1.10-2.6.19.2 oops

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

grsecurity-2.1.10-2.6.19.2 oops

Postby Axel » Mon Nov 12, 2007 4:42 am

Hello,

patched a 2.6.19.2 Kernel on a RHEL5 machine and got segfault during boot.
Kernel did well without patch. Actually I did use same config file and did not activate any of grsec staff.
Trying maxcpus=1 or nosep and the vdso=0 did not change anything relevant.
Here you have some output of 2 different computers:

<<
BUG: unable to handle kernel paging request at virtual address c0333034
[...]
SMP
Modules linked in:
CPU: 0
EIP: 0060:[<c013b125>] Not Tainted VLI
EFLAGS: 00010046 (2.6.19-grsec-grsec #1)
EIP is at __switch_to+0xb5/0x170
[...]
Process kpsmoused

other hardware:

oops: 0003
Process khelper
>>

What both common is, that 'Modules linked in:' gives no output and 'Not tainted VLI'
So I guess something with module loading is wrong and raidcontroller can not be loaded.
Has anybody an idea where to start troubleshooting?

Cheers

Axel
Axel
 
Posts: 2
Joined: Mon Nov 12, 2007 4:36 am

Re: grsecurity-2.1.10-2.6.19.2 oops

Postby PaX Team » Mon Nov 12, 2007 2:49 pm

Axel wrote:patched a 2.6.19.2 Kernel on a RHEL5 machine and got segfault during boot.
Kernel did well without patch. Actually I did use same config file and did not activate any of grsec staff.
Trying maxcpus=1 or nosep and the vdso=0 did not change anything relevant.
what about turning off DEBUG_RODATA?
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

...

Postby Axel » Mon Nov 12, 2007 5:30 pm

Thats it, thanks.
Axel
 
Posts: 2
Joined: Mon Nov 12, 2007 4:36 am


Return to grsecurity support