From: devik <devik@cdi.cz>
To: <linux-kernel@vger.kernel.org>
Subject: sched isolcpus=1 related OOPS in 2.6.9
Date: Thu, 2 Dec 2004 16:42:08 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0412021629080.493-100000@devix> (raw)
Hello,
in Soyo dual CPU PII/350 system I experience early
OOPS (even ksymdump can't save it) during CPU#1
initialization when I use cmdline isolcpus=1 to force
only CPU#0 use (I want to use affinity to select CPU#1).
The OOPS triggers every time when I use isolcpus.
I traced the problem down into sched.c:1928 (find_busiest_group)
where group->cpu_power was zero (thus division by zero occured).
In call trace it goes swapper->schedule()->........->find_busiest_group.
Important registers there: eax=ecx=edx=0, ebx!=0.
Config and vmlinux:
http://luxik.cdi.cz/~devik/files/isolcpus-oops/
Sorry no oops yet (can't get it via ksymoops nor serial),
I can provide further info (screen photo).
Can anyone at least direct me where to look further ?
(I found no general description of group scheduling code
so that I'm lost in it).
thanks a much,
-------------------------------
Martin Devera aka devik
Linux kernel QoS/HTB maintainer
http://luxik.cdi.cz/~devik/
next reply other threads:[~2004-12-02 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 15:42 devik [this message]
2004-12-03 16:28 ` devik
2004-12-03 17:18 ` Randy.Dunlap
2004-12-03 17:46 ` devik
2004-12-03 18:15 ` [PATCH] " devik
2004-12-03 19:47 ` Dimitri Sivanich
2004-12-03 20:21 ` devik
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=Pine.LNX.4.33.0412021629080.493-100000@devix \
--to=devik@cdi.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®