From: Nathan Lynch <nathanl@austin.ibm.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: kstopmachine thread panic in do_exit (2.6.9-rc1-bk1)
Date: Thu, 26 Aug 2004 12:11:14 -0500 [thread overview]
Message-ID: <1093540274.4249.48.camel@biclops.private.network> (raw)
Hi-
Something crept in between 2.6.9-rc1 and 2.6.9-rc1-bk1 which reliably
trips the "Aiee, killing interrupt handler!" panic in do_exit when
offlining a cpu. I inserted a BUG() before the panic call to see what's
causing it, looks like one of the kstopmachine threads spawned by
stop_machine. I can't do a comparison with current -mm because
offlining a cpu doesn't even get that far there.
Backing out the most recent sched.c change ("sched: smt fixes" as of
this writing) fixes it. Turning off preempt seems to work around it.
The bug is still present in -bk2. I'm seeing this on a 4-way ppc64
machine.
Nathan
next reply other threads:[~2004-08-26 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 17:11 Nathan Lynch [this message]
2004-08-27 1:39 ` kstopmachine thread panic in do_exit (2.6.9-rc1-bk1) Rusty Russell
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=1093540274.4249.48.camel@biclops.private.network \
--to=nathanl@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.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 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.