Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756723AbYAHQaG (ORCPT ); Tue, 8 Jan 2008 11:30:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752503AbYAHQ3u (ORCPT ); Tue, 8 Jan 2008 11:29:50 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:59741 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750724AbYAHQ3t (ORCPT ); Tue, 8 Jan 2008 11:29:49 -0500 Date: Tue, 8 Jan 2008 17:16:17 +0100 From: Ingo Molnar To: Kamalesh Babulal Cc: Linux Kernel Mailing List , Ingo Molnar , Peter Zijlstra , dmitry.adamushko@gmail.com, Srivatsa Vaddagiri , Dhaval Giani , Andy Whitcroft , Balbir Singh , Stephen Rothwell , Paul Mackerras , Linas Vepstas , Kumar Gala Subject: [powerpc crash] Re: Linux 2.6.24-rc7 kernel BUG at kernel/sched.c:5156! Message-ID: <20080108161617.GC32273@elte.hu> References: <47821774.8010701@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47821774.8010701@linux.vnet.ibm.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 960 Lines: 25 * Kamalesh Babulal wrote: > Hi, > > When booting the 2.6.24-rc7 kernel on the powerpc, kernel bug at > kernel.sched.c is triggered > > [ 0.000000] Kernel command line: ro console=hvc0 rhgb quiet root=LABEL=/ > [ 0.149567] BUG: scheduling while atomic: kthreadd/2/0x0006f34c > [ 0.149655] BUG: scheduling while atomic: kthreadd/3/0xbe0d8168 > [ 0.149714] ------------[ cut here ]------------ > [ 0.149722] kernel BUG at kernel/sched.c:5156! hm, that looks pretty nasty. Wondering why the atomic check did not produce a stacktrace. By the time we get to the migration thread's code it's probably late and we just get to see the effects of data corruption. Ingo -- 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/