From: Ingo Molnar <mingo@elte.hu>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
dmitry.adamushko@gmail.com,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Andy Whitcroft <apw@shadowen.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Paul Mackerras <paulus@samba.org>,
Linas Vepstas <linas@austin.ibm.com>,
Kumar Gala <galak@kernel.crashing.org>
Subject: [powerpc crash] Re: Linux 2.6.24-rc7 kernel BUG at kernel/sched.c:5156!
Date: Tue, 8 Jan 2008 17:16:17 +0100 [thread overview]
Message-ID: <20080108161617.GC32273@elte.hu> (raw)
In-Reply-To: <47821774.8010701@linux.vnet.ibm.com>
* Kamalesh Babulal <kamalesh@linux.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
next prev parent reply other threads:[~2008-01-08 16:30 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 22:19 Linux 2.6.24-rc7 Linus Torvalds
2008-01-06 23:52 ` Mark Lord
2008-01-07 0:08 ` Linus Torvalds
2008-01-07 0:35 ` Tejun Heo
2008-01-07 8:48 ` Linux 2.6.24-rc7 Build Failure on headers_install Kamalesh Babulal
2008-01-07 10:12 ` Sam Ravnborg
2008-01-08 10:51 ` Kamalesh Babulal
2008-01-08 13:10 ` Sam Ravnborg
2008-01-07 10:36 ` Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much Kamalesh Babulal
2008-01-07 18:07 ` Andrew Morton
2008-01-07 18:31 ` Christoph Lameter
2008-01-07 19:38 ` Andrew Morton
2008-01-08 9:56 ` Jean Delvare
2008-01-08 10:44 ` Kamalesh Babulal
2008-01-08 12:34 ` Fix for __you_cannot_kmalloc_that_much failure with gcc 3.2 Jean Delvare
2008-01-08 4:20 ` Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much Arjan van de Ven
2008-01-08 5:23 ` Christoph Lameter
2008-01-08 8:20 ` Kamalesh Babulal
2008-01-08 9:27 ` Balbir Singh
2008-01-08 7:48 ` Jean Delvare
2008-01-07 12:13 ` Linux 2.6.24-rc7 kernel BUG at kernel/sched.c:5156! Kamalesh Babulal
2008-01-08 16:16 ` Ingo Molnar [this message]
2008-01-07 15:53 ` Linux 2.6.24-rc7 Alejandro Riveira Fernández
2008-01-07 16:27 ` smpboot_64 section mismatch warning Sam Ravnborg
2008-01-07 16:31 ` section mismatch warning in head_64.S Sam Ravnborg
2008-01-15 10:18 ` Alejandro Riveira Fernández
2008-01-07 23:27 ` smpboot_64 section mismatch warning David Howells
2008-01-08 9:14 ` Alejandro Riveira Fernández
2008-01-08 11:17 ` David Howells
2008-01-07 16:14 ` Linux 2.6.24-rc7 Alejandro Riveira Fernández
2008-01-07 16:24 ` Michael Buesch
2008-01-07 16:52 ` Alejandro Riveira Fernández
2008-01-07 17:30 ` Michael Buesch
2008-01-07 20:23 ` Alejandro Riveira Fernández
2008-01-08 15:30 ` Michael Buesch
2008-01-08 15:55 ` Alejandro Riveira Fernández
2008-01-08 0:50 ` J.A. Magallón
2008-01-09 1:32 ` Avuton Olrich
2008-01-09 1:56 ` Tejun Heo
2008-01-10 9:25 ` J.A. Magallón
2008-01-10 13:10 ` Tejun Heo
2008-01-13 23:19 ` J.A. Magallón
2008-01-13 23:57 ` Tejun Heo
2008-01-14 23:38 ` J.A. Magallón
2008-01-14 23:56 ` Tejun Heo
2008-01-08 18:42 ` Linux 2.6.24-rc7: sparc64: WARNING: at kernel/lockdep_proc.c:267 lockdep_stats_show() Mariusz Kozlowski
2008-01-08 21:00 ` Randy Dunlap
2008-01-08 22:39 ` Mariusz Kozlowski
2008-01-08 22:45 ` Randy Dunlap
2008-01-09 16:31 ` Mariusz Kozlowski
2008-01-08 22:50 ` David Miller
2008-01-08 22:56 ` Ingo Molnar
2008-01-08 23:06 ` David Miller
2008-01-09 0:52 ` Ingo Molnar
2008-01-09 1:17 ` Linux 2.6.24-rc7 Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080108161617.GC32273@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=apw@shadowen.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=dmitry.adamushko@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=vatsa@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).