ipop3d / PAX problems

[kamihacker]

this is what I got first

Mar 18 16:21:36 ns3 kernel: PAX: From 24.84.41.120: execution attempt in: /lib/libc-2.2.5.so, 2fc77000-2fc7c000 0011e000
Mar 18 16:21:36 ns3 kernel: PAX: From 24.84.41.120: terminating task: /usr/sbin/ipop3d(ipop3d):25605, uid/euid: 0/0, PC: 2fc7bb80, SP: 5de3c378
Mar 18 16:21:36 ns3 kernel: PAX: bytes at PC: 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

then:

Mar 18 18:34:24 ns3 kernel: PAX: From 24.84.41.120: execution attempt in: <NULL>, 00000000-00000000 00000000
Mar 18 18:34:24 ns3 kernel: PAX: From 24.84.41.120: terminating task: /usr/sbin/ipop3d(ipop3d):4228, uid/euid: 0/0, PC: 00000000, SP: 5e795f48
Mar 18 18:34:24 ns3 kernel: PAX: bytes at PC: <invalid address>.

and later

Mar 19 04:13:53 ns3 kernel: kernel BUG at page_alloc.c:103!
Mar 19 04:13:53 ns3 kernel: invalid operand: 0000
Mar 19 04:13:53 ns3 kernel: CPU: 0
Mar 19 04:13:53 ns3 kernel: EIP: 0010:[<c01b820a>] Not tainted
Mar 19 04:13:53 ns3 kernel: EFLAGS: 00010282
Mar 19 04:13:53 ns3 kernel: eax: c1b94770 ebx: c1b94770 ecx: c0102ee8 edx: ffffffff
Mar 19 04:13:53 ns3 kernel: esi: 00001000 edi: 00000000 ebp: f5ae7c80 esp: c5891db8
Mar 19 04:13:53 ns3 kernel: ds: 0018 es: 0018 ss: 0018
Mar 19 04:13:53 ns3 kernel: Process ipop3d (pid: 31246, stackpage=c5891000)
Mar 19 04:13:53 ns3 kernel: Stack: 00000000 c0102d38 c1030020 c0102d70 00000207
ffffffff 00019d7b 00006000
Mar 19 04:13:53 ns3 kernel: 00001000 eb984004 86000000 c01ac781 c1b94770
00000002 00000000 86006000
Mar 19 04:13:53 ns3 kernel: cd3ea860 00000005 86006000 cd3ea860 00000000
00000000 00000000 f62e9c00
Mar 19 04:13:53 ns3 kernel: Call Trace: [<c01ac781>] [<c01c007c>] [<c01af878>] [<c019fdda>] [<c01a27b8>]
Mar 19 04:13:53 ns3 kernel: [<c01a7eed>] [<c01a7fae>] [<c01a7a93>] [<c0191968>] [<c01aded9>] [<c0191aed>]
Mar 19 04:13:53 ns3 kernel: [<c019d7b0>] [<c0191b24>]
Mar 19 04:13:53 ns3 kernel:
Mar 19 04:13:53 ns3 kernel: Code: 0f 0b 67 00 eb 4a 2e c0 8b 73 08 85 f6 74 08 0f 0b 69 00 eb

this one repeated for sveral hours until they rebooted the box, since pop stopped working

any clues? there are no ACLs working and I already disabled KERN_EXEC as stated by PaX team