From: Yong Zhang <yong.zhang0@gmail.com>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-kernel@vger.kernel.org, Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [3.1] lockdep scheduling while atomic on boot
Date: Thu, 27 Oct 2011 10:55:24 +0800 [thread overview]
Message-ID: <20111027025524.GA7819@zhy> (raw)
In-Reply-To: <20111027000609.GE2742@hostway.ca>
On Wed, Oct 26, 2011 at 05:06:09PM -0700, Simon Kirby wrote:
> We were messing with initrd stuff to get root on MD to work with newer
> than original MD superblock versions (grumble), and threw a lockdep
> kernel on, which spat out the following during boot:
>
> [ 0.000000] Initializing cgroup subsys cpu
> [ 0.000000] Linux version 3.1.0-hw-lockdep+ (root@packages01-dev) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #54 SMP Wed Oct 26 14:25:58 CDT 2011
> [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.1.0-hw-lockdep+ root=UUID=5c132cc5-ec54-4155-aa8d-ab1834b58eee ro quiet
> ...
> [ 0.004146] Mount-cache hash table entries: 256
> [ 0.004999] Initializing cgroup subsys blkio
> [ 0.005087] CPU: Physical Processor ID: 0
> [ 0.005090] CPU: Processor Core ID: 0
> [ 0.005092] mce: CPU supports 6 MCE banks
> [ 0.005099] CPU0: Thermal monitoring enabled (TM1)
> [ 0.005104] using mwait in idle threads.
> [ 0.009021] ACPI: Core revision 20110623
> [ 0.009157] BUG: scheduling while atomic: swapper/0/0x10000002
> [ 0.009217] no locks held by swapper/0.
> [ 0.009219] Modules linked in:
> [ 0.009223] Pid: 0, comm: swapper Not tainted 3.1.0-hw-lockdep+ #54
> [ 0.009225] Call Trace:
> [ 0.009234] [<ffffffff81051475>] __schedule_bug+0x85/0x90
> [ 0.009240] [<ffffffff816f5305>] __schedule+0x795/0xa20
> [ 0.009245] [<ffffffff81096c3d>] ? trace_hardirqs_on_caller+0x13d/0x1c0
> [ 0.009250] [<ffffffff81126a89>] ? kmem_cache_free+0x159/0x190
> [ 0.009254] [<ffffffff813da692>] ? acpi_os_release_object+0x9/0xd
> [ 0.009258] [<ffffffff81096c3d>] ? trace_hardirqs_on_caller+0x13d/0x1c0
> [ 0.009261] [<ffffffff81096ccd>] ? trace_hardirqs_on+0xd/0x10
> [ 0.009265] [<ffffffff813da692>] ? acpi_os_release_object+0x9/0xd
> [ 0.009269] [<ffffffff813f8340>] ? acpi_ps_free_op+0x22/0x24
> [ 0.009273] [<ffffffff81059335>] __cond_resched+0x25/0x40
> [ 0.009277] [<ffffffff816f561d>] _cond_resched+0x2d/0x40
> [ 0.009280] [<ffffffff813f75e8>] acpi_ps_complete_op+0x258/0x26e
IIRC, Frederic has patch for it, Frederic?
prev parent reply other threads:[~2011-10-27 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 0:06 [3.1] lockdep scheduling while atomic on boot Simon Kirby
2011-10-27 2:55 ` Yong Zhang [this message]
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=20111027025524.GA7819@zhy \
--to=yong.zhang0@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@hostway.ca \
/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.