grsecurity forums

Hi,

I'm getting an error when booting with grsecurity-2.1.14-2.6.30.4-200907302036.patch on 2.6.30.4, no problems with a vanilla kernel.

Screenshot and config: http://uploading.com/files/5EOQW55B/grs ... r.bz2.html

Just curious, what is the error?

It costs more than 2 minutes to download the link (timeout).
The link contains a config and a JPG.
I can't view the JPG with my normal viewer and even gimp gives:
"Opening 'DSC00131.JPG' failed: execution error"

And apart from the error, have you had working grsec-enabled kernels on the same system?

Some non-descript error I've never seen before and yes I have grsec running on the box.
If you know a better place to upload the file I can put it there, the jpg is what my phone creates.

I should say for data images (kernels) those sites might work good enough.
For pictures I prefer photo sites or plain websites.

For photosites I allways search those sites where I grant publication when I post a picture and where I can simply delete a picture to revoke publication rights.

Let us know if there are any boot problems with the latest patch. A boot issue was resolved earlier today.

-Brad

I got the same problem here i guess.

Neither grsecurity-2.1.14-2.6.30.4-200908011535.patch nor pax-linux-2.6.30.4-test9.patch will boot.

Deselecting ALL pax-options doesn't work either ...

Vanilla works
grsecurity-2.1.14-2.6.29.5-200906152045 on 2.6.29.6 works with same config
grsecurity-2.1.14-2.6.30.4-200908011535 does NOT

same config.

Not a Compiler Problem: gcc-4.1.2, gcc-4.3.3, gcc-4.4.0 tested -> no change

The Kernel hangs after PCI detection with vga=1. Using svga you get nothing but a black screen.

I get a kernel panic now, unable to allocate grsecurity shared page.

screenshot: http://img197.imageshack.us/img197/3057/dsc00132lgm.jpg

@forsaken: Can it be an amd64?
The kernel panic I see is similar on the AMD64.(x86_64, SMP)

There was a different trace on a Atom N270 (i386, no SMP).
The spurrious NAK error from atkbd seems to be caused by me trying to use the keyboard after the trace.
(see screenshots of N270 and AMD64 http://www.aoi-karin.net/grsec/)

The Atom 330 (i386, SMP) had yet another kernel panic. See for bootlogs the other thread.

Yes its 64bit.

Forsaken: can you try the latest patch I uploaded this morning? Using the config you provided initially, I'm not getting any crashes here.

I also fixed some HIGHMEM panics when used with KERNEXEC, made a change to the gr_shared_page alignment, and fixed up some KERNEXEC reverse dependencies.

-Brad

no change with grsecurity-2.1.14-2.6.30.4-200908021132.patch for me

...
pci 0000:04:04.0: supports D1 D2
pci 0000:04:04.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:04:04.0: PME# disabled
pci 0000:00:1e.0: transparent bridge
pci 0000:00:1e.0: bridge io port: [0xc000-0xcfff]
pci 0000:00:1e.0: bridge 32bit mmio: [0xfea00000-0xfeafffff]
****************** with grsec/pax it crashed here ****************************
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
...

Config/Image/Bootlog(without grsec/pax) -> http://www.exinferis.de/grsecdebug/2.6.30-1.el5x/

Brad, the new patch solved it for me.

I have been getting 'unable to allocate grsecurity shared page'. Ill post my bzImage and config in a bit...

elazar

Elazar: are you using the patch from this morning? Forsaken had the same issue and that patch resolved it for him. Are you experiencing it still?

-Brad

The Athlon64 system is now working with 2.6.30.4 (x86_64, SMP)
The N270 also (i386).

PS when did the sysctl-entries change from kernel,grsecurity.* to vm.grsecurity.*?