From owner-freebsd-alpha Fri Mar 22 7:58:39 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9970A37B41A for ; Fri, 22 Mar 2002 07:58:29 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA11152; Fri, 22 Mar 2002 10:58:28 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g2MFvw723426; Fri, 22 Mar 2002 10:57:58 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15515.21638.703042.963750@grasshopper.cs.duke.edu> Date: Fri, 22 Mar 2002 10:57:58 -0500 (EST) To: mjacob@feral.com Cc: alpha@FreeBSD.ORG Subject: Re: tsk, 's broken In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matthew Jacob writes: > > > Since checkins from yesterday, my UP XP1000 and SMP 4100 both hang at: > <..> > release_aps: releasing secondary CPUs > HANG > > TSK. I've just fixed this for UP - it was waiting for non-existant secondaries to start. From my reading of it, I don't see how it could affect a 4100 unless the other CPUs are disabled. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message