On 31 Oct 2007 at 22:46, Brian Kroth wrote: > but not ever (yet) with this > > cactid --verbosity=5 -f 1 -l 10
what does the -l switch do? > The version of cactid in portage is slightly old. After updating from > 0.8.6i-r1 to 0.8.6j the problem seems to happen less frequently, but > still happens. With that in mind might this actually be a software > problem and not a kernel problem? Shouldn't PAX be preventing userland > software from screwing up the page table? i'm almost sure it's a bug somewhere in vma mirroring as that's the only thing i changed in .22 and on and it does play with page locking (the bad page state is triggered because a to-be-freed page is still locked, that's means there's a missing unlock somewhere in the code, but i couldn't figure it out from the code yet). > I can send more kernel output if anyone's interested. Any thoughts on > what else I should be doing to test this? i'll need your mm/memory.o from the failing kernel and if it occured on multiple machines or kernels, indicate which of your report corresponds to which .o (well, i can find it out from the disasm eventually, but it helps me if i don't have to ;-). then can you send me a /proc/pid/maps file from cactid and nagios (if you use grsec make sure that addresses are not hidden and preferably not randomized either)? -- [EMAIL PROTECTED] mailing list
