[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080108161617.GC32273@elte.hu>
Date: Tue, 8 Jan 2008 17:16:17 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
dmitry.adamushko@...il.com,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
Andy Whitcroft <apw@...dowen.org>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Paul Mackerras <paulus@...ba.org>,
Linas Vepstas <linas@...tin.ibm.com>,
Kumar Gala <galak@...nel.crashing.org>
Subject: [powerpc crash] Re: Linux 2.6.24-rc7 kernel BUG at
kernel/sched.c:5156!
* Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists