Skip to contentSkip to conversation

BUG at rmap.c:212

DISCUSSION Petr Vandrovec 2 participants 2 messages Jul 31, 2002

lore
Share & tools
lore
#0 lore raw

Hello,
yesterday I told (in IDE thread) that BUG at rmap.c:212 is probably
already fixed by changeset 520. Unfortunately, it is not, I got it again with BK tree. It happened again when 'ntpd' called exit() upon receiving sigterm.

Stack trace:

page_remove_rmap
zap_pte_range
zap_pmd_range
unmap_page_range
exit_mmap
mmput
do_exit
sys_exit
syscall_call

If it is not known bug, I'll rebuild kernel with DEBUG_RMAP. Unfortunately it looks like that machine must have uptime > 12hrs to trigger this. Probably updatedb or some other task must be run to try to swap ntpd out?
Best regards,
Petr Vandrovec [email protected]

#1 lore raw
Quoted 4 lines · Petr Vandrovec

yesterday I told (in IDE thread) that BUG at rmap.c:212 is probably
already fixed by changeset 520. Unfortunately, it is not, I got it again with BK tree. It happened again when 'ntpd' called exit() upon receiving sigterm.

Line 212 is 'pte_chain_unlock(page);' right ?

What configuration are you running ? SMP ? PREEMPT ? What compiler ?

Quoted 12 lines

Stack trace:

page_remove_rmap
zap_pte_range
zap_pmd_range
unmap_page_range
exit_mmap
mmput
do_exit
sys_exit
syscall_call

Quoted 4 lines

If it is not known bug, I'll rebuild kernel with DEBUG_RMAP. Unfortunately it looks like that machine must have uptime > 12hrs to trigger this. Probably updatedb or some other task must be run to try to swap ntpd out?

It is not a known bug. In fact I've never seen this one before.

kind regards,

Rik

Signature · 3 lines
Bravely reimplemented by the knights who say "NIH".

http://www.surriel.com/		http://distro.conectiva.com/