From owner-freebsd-sparc64@FreeBSD.ORG Tue Aug 17 10:56:24 2004 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 A5BC916A4CE for ; Tue, 17 Aug 2004 10:56:24 +0000 (GMT) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4A7543D80 for ; Tue, 17 Aug 2004 10:56:23 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id i7HAuBXn026325; Tue, 17 Aug 2004 11:56:11 +0100 (BST) Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.12.9p2/8.12.9) with ESMTP id i7HAuBMu068894; Tue, 17 Aug 2004 11:56:11 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost)i7HAuBxY068891; Tue, 17 Aug 2004 11:56:11 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Tue, 17 Aug 2004 11:56:11 +0100 (BST) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: Chris Knight In-Reply-To: <200408170909.i7H99taL082002@postoffice.e-easy.com.au> Message-ID: <20040817115518.W68839@ury.york.ac.uk> References: <200408170909.i7H99taL082002@postoffice.e-easy.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk cc: sparc64@freebsd.org Subject: Re: Insta-panic with recent -current on Ultra10 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: Tue, 17 Aug 2004 10:56:24 -0000 On Tue, 17 Aug 2004, Chris Knight wrote: > Howdy, > > I'm getting the following panic on a kernel built from CURRENT > as of 17/08/2004 0100 AEST (+10). > A kernel from the 13/08/2004 0100 AEST (+10) works fine. > In the process of rebuilding the kernel so I can get some more > details... I've seen exactly this panic from a kernel dated 15th. Just another datapoint. Gavin