From owner-freebsd-sparc64@FreeBSD.ORG Fri Apr 29 18:25:27 2005 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C272F16A4CE for ; Fri, 29 Apr 2005 18:25:27 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C84843D2D for ; Fri, 29 Apr 2005 18:25:27 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.3/8.13.3) with ESMTP id j3TIPI3h040695; Fri, 29 Apr 2005 11:25:18 -0700 (PDT) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.3/8.13.3/Submit) id j3TIPHTH040694; Fri, 29 Apr 2005 11:25:17 -0700 (PDT) (envelope-from marcel) Date: Fri, 29 Apr 2005 11:25:17 -0700 From: Marcel Moolenaar To: Royce Williams Message-ID: <20050429182517.GA40567@ns1.xcllnt.net> References: <20050429120037.D45F116A4F6@hub.freebsd.org> <72eecd381aed25e4e618d812e99238e0@xcllnt.net> <42726B21.6050907@alaska.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42726B21.6050907@alaska.net> User-Agent: Mutt/1.4.2.1i cc: Ken Smith cc: freebsd-sparc64@freebsd.org Subject: Re: 5.4-RCx "jumping to kernel entry" hang on Ultra1/2/30 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2005 18:25:27 -0000 On Fri, Apr 29, 2005 at 09:13:05AM -0800, Royce Williams wrote: > > Incidentally, that "stray vector" error I mentioned at the outset is > showing up right after the "jumping to kernel entry 0xc0040000." : > > stray vector interrupt 2029 > > > I have no idea if this is related in any way. Yes, it is. Not in the obvious way, though. The patch I sent out addresses the situation caused by the stray interrupt. That is: console output being interrupted, followed by new console output. The new console output is the "stray vector" text that is being printed from the interrupt handler. One needs to be careful to allow this to happened without depending on normal synchronisation mechanisms. This was (and still is on the 5.4 branch) a problem with the Z8530 only to the best of my knowledge. One concern remains: what if the stray interrupt is the immediate result of initializing the console and we're being interrupted half-way through the initialization process? Console output (the "stray vector" message) is the last thing you want to be doing then. You first want to finish initialization. I can hack up a patch that addresses this case if people are still having problems. However, I'd rather that interrupts are disabled that early in the boot process... Anyway: It'll get fixed, one way or the other... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net