From: Andrew Morton <akpm@osdl.org>
To: Steven Cole <elenstev@mesatop.com>
Cc: linux-mm@kvack.org, Ingo Molnar <mingo@elte.hu>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: 2.6.5-rc2-mm3 blizzard of "bad: scheduling while atomic" with PREEMPT
Date: Thu, 25 Mar 2004 10:35:06 -0800 [thread overview]
Message-ID: <20040325103506.19129deb.akpm@osdl.org> (raw)
In-Reply-To: <1080237733.2269.31.camel@spc0.esa.lanl.gov>
Steven Cole <elenstev@mesatop.com> wrote:
>
> Apologies in advance if this is a known problem. I looked through
> some recent archives and didn't find this exact situation, so here it
> is. I'm just starting to test the -mm kernels again after a pause,
> so I'm not up on the current problem set.
>
> Kernel is 2.6.5-rc2-mm3 with SMP and PREEMPT. Box is dual PIII.
> Base distro is Mandrake 10.
>
> These messages were the start of about 8,000 lines of similar.
> The "while atomic" message came out about 374 times before it
> seemed to stop.
>
> Recompiling without PREEMPT made this go away.
err, yes. Ingo broke it ;)
bad: scheduling while atomic!
Call Trace:
[<c011d0f0>] schedule+0x3c/0x58c
[<c0109f69>] dump_stack+0x19/0x20
[<c011f146>] __might_sleep+0xaa/0xb4
[<c011d91a>] wait_for_completion+0xae/0x110
[<c011d688>] default_wake_function+0x0/0x1c
[<c011d688>] default_wake_function+0x0/0x1c
[<c011be8b>] sched_migrate_task+0x6b/0x9c
[<c011c023>] sched_balance_exec+0x63/0x8c
[<c0167108>] do_execve+0x14/0x200
[<c0141ef5>] buffered_rmqueue+0x1c5/0x1d4
[<c0141fae>] __alloc_pages+0xaa/0x2fc
[<c014c5c2>] do_wp_page+0x3c2/0x478
[<c014d6c3>] handle_mm_fault+0x107/0x174
[<c01196b5>] do_page_fault+0x15d/0x4ba
[<c0119558>] do_page_fault+0x0/0x4ba
[<c02865b6>] tiocspgrp+0x72/0x9c
[<c012aca9>] recalc_sigpending+0x11/0x18
[<c0168a6f>] getname+0x5f/0xa0
[<c0107a6f>] sys_execve+0x2f/0x68
[<c0109185>] sysenter_past_esp+0x52/0x71
Fortunately vger seems to have gobbled the mm3 announcement.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-03-25 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 18:02 2.6.5-rc2-mm3 blizzard of "bad: scheduling while atomic" with PREEMPT Steven Cole
2004-03-25 18:35 ` Andrew Morton [this message]
2004-03-25 18:38 ` Ingo Molnar
2004-03-25 19:06 ` Ingo Molnar
2004-03-25 19:17 ` Andrew Morton
2004-03-25 19:16 ` Ingo Molnar
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=20040325103506.19129deb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=elenstev@mesatop.com \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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.