From owner-freebsd-sparc64@FreeBSD.ORG Thu Mar 3 11:24:00 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 6AEDC16A4CE for ; Thu, 3 Mar 2005 11:24:00 +0000 (GMT) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id C622C43D58 for ; Thu, 3 Mar 2005 11:23:59 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) j23BNwp9075805; Thu, 3 Mar 2005 12:23:58 +0100 (CET) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.11/8.12.10/Submit) id j23BNrct075804; Thu, 3 Mar 2005 12:23:53 +0100 (CET) (envelope-from marius) Date: Thu, 3 Mar 2005 12:23:52 +0100 From: Marius Strobl To: Kris Kennaway Message-ID: <20050303122352.A74807@newtrinity.zeist.de> References: <20050303020337.GA58811@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20050303020337.GA58811@xor.obsecurity.org>; from kris@obsecurity.org on Wed, Mar 02, 2005 at 06:03:37PM -0800 X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-6; AVE: 6.30.0.2; VDF: 6.30.0.10; host: newtrinity.zeist.de) cc: sparc64@freebsd.org Subject: Re: 'Fatal reset' on e4500 running 6.0 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: Thu, 03 Mar 2005 11:24:00 -0000 On Wed, Mar 02, 2005 at 06:03:37PM -0800, Kris Kennaway wrote: > I updated the kernel of the e4500 to 6.0 to benchmark buildworld, but > it reboots after a few seconds with: > <...> As far as I understand this means that it's a bug in a device driver. The sole sparc64 device driver that I'm aware of where -STABLE and -CURRENT aren't in sync is esp(4). If reverting the recent changes to esp_sbus.c and ncr53c9x.c doesn't make a difference you'll probably have to search for the commit that causes this. Marius