Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030199AbVLSAv2 (ORCPT ); Sun, 18 Dec 2005 19:51:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030202AbVLSAv2 (ORCPT ); Sun, 18 Dec 2005 19:51:28 -0500 Received: from ms-smtp-01.nyroc.rr.com ([24.24.2.55]:23948 "EHLO ms-smtp-01.nyroc.rr.com") by vger.kernel.org with ESMTP id S1030199AbVLSAv1 (ORCPT ); Sun, 18 Dec 2005 19:51:27 -0500 Subject: Re: 2.6.15-rc5-rt2 won't boot on dual 933 From: Steven Rostedt To: "K.R. Foley" Cc: Ingo Molnar , linux-kernel In-Reply-To: <43A5DAE4.8090908@cybsft.com> References: <43A5DAE4.8090908@cybsft.com> Content-Type: text/plain Date: Sun, 18 Dec 2005 19:51:13 -0500 Message-Id: <1134953473.13138.217.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1197 Lines: 49 On Sun, 2005-12-18 at 15:55 -0600, K.R. Foley wrote: > dump_stack+0x1e/0x20 (20) > [] preempt_enable_no_resched+0x5f/0x70 (20) > [] cpu_idle+0xb2/0x100 (40) > [] start_secondary+0x296/0x340<6> Ingo, What's the reason for this printing out in cpu_idle? #ifdef CONFIG_DEBUG_PREEMPT void notrace preempt_enable_no_resched(void) { static int once = 1; barrier(); dec_preempt_count(); if (once && !preempt_count()) { once = 0; printk(KERN_ERR "BUG: %s:%d task might have lost a preemption check! \n", current->comm, current->pid); dump_stack(); } } EXPORT_SYMBOL(preempt_enable_no_resched); #endif I can understand the above when using preempt_enable_no_resched, when you know that you still have preemption on, but sometimes (as in cpu_idle) it is used just before calling schedule. So this check is pretty much meaningless. --- KR, Does your kernel boot without CONFIG_DEBUG_PREEMPT? -- Steve - 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/