From: Robert Love <rml@tech9.net>
To: scott781@attbi.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.38 scheduling oops? at boot
Date: 22 Sep 2002 14:30:45 -0400 [thread overview]
Message-ID: <1032719445.10108.988.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0209220749280.918-200000@localhost.localdomain>
On Sun, 2002-09-22 at 09:04, Scott M. Hoffman wrote:
> I booted into 2.5.38 on a dual amd duron system using profile=2 on
> command line, and the system seemed a bit sluggish just to get bash to
> complete a filename in /proc. I found the attached oops after these
> messages:
> Starting migration thread for cpu 1
> bad: Scheduling while atomic!
> ...
> Trace; c01186ed <schedule+3d/430>
> Trace; c0118d9c <wait_for_completion+9c/100>
> Trace; c0118b30 <default_wake_function+0/40>
> Trace; c0118b30 <default_wake_function+0/40>
> Trace; c011a2c5 <set_cpus_allowed+145/170>
> Trace; c011a33e <migration_thread+4e/340>
> Trace; c011a2f0 <migration_thread+0/340>
> Trace; c0106f0d <kernel_thread_helper+5/18>
> Trace; c01186ed <schedule+3d/430>
> Trace; c0118d9c <wait_for_completion+9c/100>
> Trace; c0118b30 <default_wake_function+0/40>
> Trace; c0118b30 <default_wake_function+0/40>
> Trace; c011a2c5 <set_cpus_allowed+145/170>
> Trace; c012274f <ksoftirqd+4f/f0>
> Trace; c0122700 <ksoftirqd+0/f0>
> Trace; c0106f0d <kernel_thread_helper+5/18>
This particular occurrence is known; thanks. The startup of the
migration_threads calls set_cpus_allowed(), and set_cpus_allowed()
sleeps while disabling preemption.
It will not hurt anything, but it needs to be fixed. Before that, I
need to find out why set_cpus_allowed() dies without the
preempt_disable() in there.
Robert Love
prev parent reply other threads:[~2002-09-22 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 13:04 2.5.38 scheduling oops? at boot Scott M. Hoffman
2002-09-22 18:30 ` Robert Love [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=1032719445.10108.988.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=scott781@attbi.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).