Date: Fri, 1 Oct 2004 15:26:54 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: David Xu <davidxu@freebsd.org> Cc: Julian Elischer <julian@elischer.org> Subject: Re: easy to reproduce unkillable threads Message-ID: <16733.44926.348617.722562@grasshopper.cs.duke.edu> In-Reply-To: <415CCD79.3030401@freebsd.org> References: <16728.37731.540143.307772@grasshopper.cs.duke.edu> <41589B4A.9080508@elischer.org> <415AB791.10809@freebsd.org> <16730.48642.4481.841374@grasshopper.cs.duke.edu> <415B13E8.2090205@elischer.org> <16731.6010.446877.347190@grasshopper.cs.duke.edu> <415B1ED6.8010809@elischer.org> <16731.11515.504636.53058@grasshopper.cs.duke.edu> <415CCD79.3030401@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David Xu writes: > Now, I can reproduce it on SMP. However, if I : Hurray! I'm not crazy! > sysctl -w kern.smp.forward_signal_enabled=0 > then, I can always kill it. it sounds like another IPI bug. > I thought the IPI bugs were IPIs getting stuck. But this IPI was delivered. Naively, I would say that it seems more like an MP-safety issue in the kernel thread exit code.. Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16733.44926.348617.722562>