Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932281AbWHCVSK (ORCPT ); Thu, 3 Aug 2006 17:18:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932289AbWHCVSK (ORCPT ); Thu, 3 Aug 2006 17:18:10 -0400 Received: from adsl-69-232-92-238.dsl.sndg02.pacbell.net ([69.232.92.238]:5787 "EHLO gnuppy.monkey.org") by vger.kernel.org with ESMTP id S932281AbWHCVSI (ORCPT ); Thu, 3 Aug 2006 17:18:08 -0400 Date: Thu, 3 Aug 2006 14:18:00 -0700 To: Steven Rostedt Cc: Robert Crocombe , linux-kernel@vger.kernel.org, Ingo Molnar , Thomas Gleixner , "Bill Huey (hui)" Subject: Re: Problems with 2.6.17-rt8 Message-ID: <20060803211800.GA11251@gnuppy.monkey.org> References: <1154541079.25723.8.camel@localhost.localdomain> <1154615261.32264.6.camel@localhost.localdomain> <20060803202211.GA10720@gnuppy.monkey.org> <1154638445.4655.11.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1154638445.4655.11.camel@localhost.localdomain> User-Agent: Mutt/1.5.11+cvs20060403 From: Bill Huey (hui) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2081 Lines: 42 On Thu, Aug 03, 2006 at 04:54:05PM -0400, Steven Rostedt wrote: > On Thu, 2006-08-03 at 13:22 -0700, Bill Huey wrote: > > free_pages_bulk is definitely being called inside of an atomic. > > I force this stack trace when the in_atomic() test is true at the > > beginning of the function. > > > > > > [ 29.362863] Call Trace: > > [ 29.367107] {free_pages_bulk+86} > > [ 29.373122] {_raw_spin_unlock_irqrestore+44} > > [ 29.380233] {__free_pages_ok+428} > > [ 29.386336] {free_hot_page+25} > > [ 29.392165] {__free_pages+41} > > [ 29.397898] {__free_pages_bootmem+174} > > [ 29.404457] {free_all_bootmem_core+253} > > [ 29.411112] {free_all_bootmem_node+9} > > [ 29.417574] {numa_free_all_bootmem+61} > > [ 29.424122] {_etext+0} > > [ 29.429224] {mem_init+128} > > [ 29.434691] {start_kernel+377} > > [ 29.440520] {_sinittext+667} > > [ 29.446669] --------------------------- > > [ 29.450963] | preempt count: 00000001 ] > > [ 29.455257] | 1-level deep critical section nesting: > > [ 29.460732] ---------------------------------------- > > [ 29.466212] .. [] .... start_kernel+0x68/0x221 > > [ 29.472815] .....[] .. ( <= _sinittext+0x29b/0x2a2) > > [ 29.480056] > > Perhaps you could put in that in_atomic check at the start of each of > these functions and point to where it is a problem. Perhaps a spinlock > is taken that was real and not a mutex. Yeah, that's my thought as well. I'm going to do what you suggest now. bill - 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/