kernel 2.4.27 + grsecurity + sparc32

Hi,

being on a shoestring budget i use ss20's as border routers and a few 
shell servers no ross cpu's here.

I use a chroot jail which I need grsecurity to help make more secure for
login account to.

when booting a trimmed down no modules 2.4.26 or 2.4.27 kernel patched 
with grsec

2.2.23 works fine with grsec.

My border router with out grsec has been up and portfording much traffic 
I have 8 dmz's which i portforward to on quad cards.

I havnt tested 2.4.27 on it yet just to get the uptime but uptime so far is.

183 days.

  cat /proc/cpuinfo
cpu             : Texas Instruments, Inc. - SuperSparc-(II)
fpu             : SuperSparc on-chip FPU
promlib         : Version 3 Revision 2
prom            : 2.25
type            : sun4m
ncpus probed    : 2
ncpus active    : 2
Cpu0Bogo        : 59.80
Cpu1Bogo        : 59.80
MMU type        : TI Viking/MXCC
contexts        : 65536
nocache total   : 4194304
nocache used    : 363776
CPU0            : online
CPU1            : online


the machine which spinlocks with the grsecurity patch as of kernels 
after 2.4.23

the message is as follows.

kernel 2.4.23-grsec

cat /proc/cpuinfo
cpu             : Texas Instruments, Inc. - SuperSparc-(II) 

fpu             : SuperSparc on-chip FPU 

promlib         : Version 3 Revision 2 

prom            : 2.25 

type            : sun4m 

ncpus probed    : 2 

ncpus active    : 2 

Cpu0Bogo        : 74.95 

Cpu1Bogo        : 75.16 

MMU type        : TI Viking/MXCC 

contexts        : 65536 

nocache total   : 5242880 

nocache used    : 336384 

CPU0            : online 

CPU1            : online


now when booting to anything later than this kernel patched with 
grsecurity patches.


I get the following.
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 

VFS: Mounted root (ext2 filesystem) readonly. 

Kernel panic: Unable to allocate grsecurity IP tagging table 

  Press L1-A to return to the boot prom 

spin_lock(f0227000) CPU#1 stuck at f005ad64, owner PC(f0027940):CPU(0) 



directly into a spinlock.


does anyone know what might me causing this issue.

I am going to test on my ultrasparcs.

the only differant between the two machines is the bogomips and amount 
of ram.

any help so I can run a securerer kernel on the shell server would be 
appreciated.


Sincerely,
Aaron Waller