From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: BUG: scheduling while atomic: swapper/0/0x10000002
Date: Thu, 28 Jul 2011 10:07:14 -0700 [thread overview]
Message-ID: <4E319742.6040208@gmail.com> (raw)
the kernel also barfed this up as well..:
[ 0.001006] Calibrating delay loop (skipped), value calculated
using timer frequency.. 4280.75 BogoMIPS (lpj=2140379)
[ 0.002175] pid_max: default: 32768 minimum: 301
[ 0.002611] BUG: scheduling while atomic: swapper/0/0x10000002
[ 0.002785] no locks held by swapper/0.
[ 0.003006] Modules linked in:
[ 0.003268] Pid: 0, comm: swapper Not tainted 3.0.0-06046-g55f9c40 #1
[ 0.003441] Call Trace:
[ 0.003627] [<ffffffff814c8cf4>] __schedule_bug+0x75/0x7a
[ 0.003805] [<ffffffff814d270d>] schedule+0x95/0x7b5
[ 0.004011] [<ffffffff8106b30d>] ? kzalloc.constprop.3+0x29/0x2b
[ 0.005009] [<ffffffff8104b77f>] __cond_resched+0x28/0x34
[ 0.005184] [<ffffffff814d3045>] _cond_resched+0x19/0x22
[ 0.005361] [<ffffffff81113fce>] slab_pre_alloc_hook+0x37/0x3d
[ 0.005537] [<ffffffff811163c4>] kmem_cache_alloc_trace+0x2c/0xc0
[ 0.005713] [<ffffffff8106b30d>] kzalloc.constprop.3+0x29/0x2b
[ 0.005892] [<ffffffff81b908c1>] pidmap_init+0x81/0xc0
[ 0.006011] [<ffffffff81b77b2a>] start_kernel+0x368/0x3fa
[ 0.006187] [<ffffffff81b772c4>] x86_64_start_reservations+0xaf/0xb3
[ 0.006364] [<ffffffff81b77140>] ? early_idt_handlers+0x140/0x140
[ 0.006539] [<ffffffff81b773ca>] x86_64_start_kernel+0x102/0x111
[ 0.006805] Security Framework initialized
[ 0.007023] SELinux: Initializing.
[ 0.007263] SELinux: Starting in enforcing mode
system still booted up, and everything seems o.k.
full dmesg:
http://fpaste.org/8j2G/
Justin P. Mattock
next reply other threads:[~2011-07-28 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 17:07 Justin P. Mattock [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-28 12:14 BUG: scheduling while atomic: swapper/0/0x10000002 Wouter M. Koolen
2011-11-28 13:06 ` Peter Zijlstra
2012-01-10 15:10 ` Wouter M. Koolen
2010-08-10 13:12 Piotr Hosowicz
2010-08-10 14:07 ` Heinz Diehl
2010-08-10 14:29 ` Markus Trippelsdorf
2010-08-10 14:29 ` Markus Trippelsdorf
2010-08-10 15:13 ` Sergey Senozhatsky
2010-08-10 15:19 ` Piotr Hosowicz
2010-08-10 15:35 ` Sergey Senozhatsky
2010-08-10 15:36 ` Piotr Hosowicz
2010-08-10 15:36 ` Piotr Hosowicz
2010-08-10 12:38 Sergey Senozhatsky
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=4E319742.6040208@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.