Brian Kroth wrote:
Does the problem happen still if you do something like this? cp cactid cactid.nopax paxctl -mps cactid.nopax cactid.nopax --verbosity=5 -f 1 -l 10Looping for 20 minutes without a problem. I'm going to start trying to figure out which of the protections is making it angry.Brian
paxctl -MPS /usr/sbin/cactid.nopax paxctl -mp /usr/sbin/cactid.nopax while [ "$?" == "0" ]; do /usr/sbin/cactid.nopax; done ... Nov 4 01:11:13 tux-mc Bad page state in process 'cactid.nopax'Nov 4 01:11:13 tux-mc page:c13b8380 flags:0x40000001 mapping:00000000 mapcount:0 count:0
Nov 4 01:11:13 tux-mc Trying to fix it up, but a reboot is needed Nov 4 01:11:13 tux-mc Backtrace: Nov 4 01:11:13 tux-mc [<c0403da8>] show_trace_log_lvl+0x1a/0x30 Nov 4 01:11:13 tux-mc [<c0403dd0>] show_trace+0x12/0x14 Nov 4 01:11:13 tux-mc [<c0403eca>] dump_stack+0x16/0x18 Nov 4 01:11:13 tux-mc [<c044ba59>] bad_page+0x66/0x97 Nov 4 01:11:13 tux-mc [<c044c52e>] free_hot_cold_page+0x71/0x180 Nov 4 01:11:13 tux-mc [<c044c647>] free_hot_page+0xa/0xc Nov 4 01:11:13 tux-mc [<c044ef70>] __page_cache_release+0x84/0x90 Nov 4 01:11:13 tux-mc [<c044efdc>] put_page+0x27/0x36 Nov 4 01:11:13 tux-mc [<c04558aa>] do_wp_page+0x219/0x3fc Nov 4 01:11:13 tux-mc [<c0456b37>] __handle_mm_fault+0x277/0x2cd Nov 4 01:11:13 tux-mc [<c0414406>] do_page_fault+0x1cd/0x7bf Nov 4 01:11:13 tux-mc [<c06e6d55>] error_code+0x75/0x80 Nov 4 01:11:13 tux-mc ======================= paxctl -MPS ... paxctl -s ...No problems after 20+ minutes of looping the command. So SEGMEXEC seems to be the culprit, correct? Did something change in the way that was handled from 2.6.20 to 2.6.22?
I'll have to see if it's the same for nagios, but that can wait until tomorrow.
Brian
smime.p7s
Description: S/MIME Cryptographic Signature
