Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932248AbVKNXvc (ORCPT ); Mon, 14 Nov 2005 18:51:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932173AbVKNXvc (ORCPT ); Mon, 14 Nov 2005 18:51:32 -0500 Received: from e32.co.us.ibm.com ([32.97.110.150]:28125 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S932249AbVKNXvb (ORCPT ); Mon, 14 Nov 2005 18:51:31 -0500 Subject: 2.6.14 X spinning in the kernel From: Badari Pulavarty To: lkml Cc: akpm@osdl.org, hugh@veritas.com Content-Type: text/plain Date: Mon, 14 Nov 2005 15:51:21 -0800 Message-Id: <1132012281.24066.36.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4015 Lines: 129 Hi, My 2-cpu EM64T machine started showing this problem again on 2.6.14. On some reboots, X seems to spin in the kernel forever. sysrq-t output shows nothing. X R running task 0 3607 3589 3903 (L-TLB) top shows: 3607 root 25 0 0 0 0 R 99.1 0.0 262:04.69 X So, I wrote a module to do smp_call_function() on all CPUs to show stacks on them. CPU0 seems to be spinning in exit_mmap(). I did this multiple times to collect stacks few times. Is this a known issue ? Thanks, Badari 1st time: --------- CPU1: Call Trace:{:mod:showacpu+43} {:mod:init_mod+11} {sys_init_module+306} {system_call+126} CPU0: Call Trace: {:mod:showacpu+43} {smp_call_function_interrupt+73} {call_function_interrupt+132} {unmap_vmas+1114} {unmap_vmas+1372} {exit_mmap +166} {mmput+52} {flush_old_exec +2474} {vfs_read+341} {load_elf_binary+1507} {buffered_rmqueue+529} {alloc_page_interleave+59} {copy_strings+516} {load_elf_binary+0} {search_binary_handler+201} {do_execve+415} {system_call+126} {sys_execve +68} {stub_execve+106} 2nd time: ---------- CPU1: Call Trace:{:mod:showacpu+43} {:mod:init_mod+11} {sys_init_module+306} {system_call+126} CPU0: Call Trace: {:mod:showacpu+43} {smp_call_function_interrupt+73} {call_function_interrupt+132} {remove_vm_struct+63} {remove_vm_struct+51} {exit_mmap+375} {mmput+52} {flush_old_exec +2474} {vfs_read+341} {load_elf_binary+1507} {buffered_rmqueue+529} {alloc_page_interleave+59} {copy_strings+516} {load_elf_binary+0} {search_binary_handler+201} {do_execve+415} {system_call+126} {sys_execve +68} {stub_execve+106} 3rd time: --------- CPU1: Call Trace:{:mod:showacpu+43} {:mod:init_mod+11} {sys_init_module+306} {system_call+126} CPU0: Call Trace: {:mod:showacpu+43} {smp_call_function_interrupt+73} {call_function_interrupt+132} {__mod_page_state+36} {free_hot_cold_page+41} {__pagevec_free+37} {release_pages+367} {free_pages_and_swap_cache+123} {exit_mmap+274} {mmput+52} {flush_old_exec+2474} {vfs_read+341} {load_elf_binary+1507} {buffered_rmqueue+529} {alloc_page_interleave+59} {copy_strings+516} {load_elf_binary+0} {search_binary_handler+201} {do_execve+415} {system_call +126} {sys_execve+68} {stub_execve +106} - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/