public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* sched isolcpus=1 related OOPS in 2.6.9
@ 2004-12-02 15:42 devik
  2004-12-03 16:28 ` devik
  0 siblings, 1 reply; 7+ messages in thread
From: devik @ 2004-12-02 15:42 UTC (permalink / raw)
  To: linux-kernel

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/



^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2004-12-03 20:24 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-02 15:42 sched isolcpus=1 related OOPS in 2.6.9 devik
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox