Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750958AbWHBBby (ORCPT ); Tue, 1 Aug 2006 21:31:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750961AbWHBBby (ORCPT ); Tue, 1 Aug 2006 21:31:54 -0400 Received: from ms-smtp-04.nyroc.rr.com ([24.24.2.58]:50146 "EHLO ms-smtp-04.nyroc.rr.com") by vger.kernel.org with ESMTP id S1750951AbWHBBbx (ORCPT ); Tue, 1 Aug 2006 21:31:53 -0400 Subject: Re: 2.6.17-rt8 crash amd64 From: Steven Rostedt To: Bill Huey Cc: Ingo Molnar , linux-kernel@vger.kernel.org In-Reply-To: <20060802011809.GA26313@gnuppy.monkey.org> References: <20060802011809.GA26313@gnuppy.monkey.org> Content-Type: text/plain Date: Tue, 01 Aug 2006 21:31:42 -0400 Message-Id: <1154482302.30391.14.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3430 Lines: 68 On Tue, 2006-08-01 at 18:18 -0700, Bill Huey wrote: > Hello folks, > > I'm getting this: > > [ 41.989355] BUG: scheduling while atomic: udevd/0x00000001/1101 > [ 41.995501] > [ 41.995502] Call Trace: > [ 41.999458] {__schedule+155} > [ 42.004805] {_raw_spin_unlock_irqrestore+72} > [ 42.011583] {task_blocks_on_rt_mutex+497} > [ 42.018095] {free_pages_bulk+42} > [ 42.023799] {find_task_by_pid_type+24} > [ 42.030039] {free_pages_bulk+42} > [ 42.035742] {schedule+236} > [ 42.040907] {rt_lock_slowlock+351} > [ 42.046798] {_raw_spin_unlock_irqrestore+72} > [ 42.053577] {__lock_text_start+13} > [ 42.059459] {free_pages_bulk+42} > [ 42.065161] {_raw_spin_unlock_irqrestore+44} > [ 42.071940] {__free_pages_ok+428} > [ 42.077733] {__free_pages+48} > [ 42.083168] {free_pages+133} > [ 42.088514] {free_task+24} > [ 42.093678] {__put_task_struct+189} > [ 42.099650] {thread_return+208} > [ 42.105264] {task_blocks_on_rt_mutex+497} > [ 42.111774] {atomic_dec_and_spin_lock+21} > [ 42.118284] {find_task_by_pid_type+24} > [ 42.124525] {atomic_dec_and_spin_lock+21} > [ 42.131032] {schedule+236} > [ 42.136195] {rt_lock_slowlock+351} > [ 42.142086] {__lock_text_start+13} > [ 42.147966] {atomic_dec_and_spin_lock+21} > [ 42.154476] {dput+57} > [ 42.159194] {__link_path_walk+1710} > [ 42.165166] {_raw_spin_unlock+46} > [ 42.170961] {link_path_walk+103} > [ 42.176672] {do_path_lookup+644} > [ 42.182379] {__user_walk_fd+63} > [ 42.187994] {vfs_lstat_fd+33} > [ 42.193434] {sys_newlstat+34} > [ 42.198871] {error_exit+0} > [ 42.204040] {system_call+126} This back trace is definitely ugly. Do you get this all the time? And if so, could you compile in frame pointers and try again. (I'll dig through this in the mean time.) -- Steve > [ 42.209715] --------------------------- > [ 42.213716] | preempt count: 00000001 ] > [ 42.217715] | 1-level deep critical section nesting: > [ 42.222879] ---------------------------------------- > [ 42.228043] .. [] .... __schedule+0xb3/0xb2a > [ 42.234150] .....[] .. ( <= schedule+0xec/0x11e) > [ 42.240796] > [ 53.347726] NET: Registered protocol family 10 > [ 53.353240] IPv6 over IPv4 tunneling driver > > - 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/