From owner-freebsd-threads@FreeBSD.ORG Fri Oct 1 19:27:23 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD1BB16A4CF; Fri, 1 Oct 2004 19:27:23 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 749F143D53; Fri, 1 Oct 2004 19:27:23 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i91JR1Jt029203 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Oct 2004 15:27:01 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i91JQsv7007972; Fri, 1 Oct 2004 15:26:54 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16733.44926.348617.722562@grasshopper.cs.duke.edu> Date: Fri, 1 Oct 2004 15:26:54 -0400 (EDT) To: David Xu 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> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-threads@freebsd.org cc: Andrew Gallatin cc: Julian Elischer Subject: Re: easy to reproduce unkillable threads X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Oct 2004 19:27:24 -0000 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