From owner-freebsd-sparc64@FreeBSD.ORG Thu Jun 17 13:03:18 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 896E616A4D0; Thu, 17 Jun 2004 13:03:18 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 316AA43D2D; Thu, 17 Jun 2004 13:03:18 +0000 (GMT) (envelope-from ilmar@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i5HD1LIL029809; Thu, 17 Jun 2004 09:01:21 -0400 (EDT) (envelope-from ilmar@watson.org) Received: from localhost (ilmar@localhost)i5HD1Ldx029806; Thu, 17 Jun 2004 09:01:21 -0400 (EDT) (envelope-from ilmar@watson.org) X-Authentication-Warning: fledge.watson.org: ilmar owned process doing -bs Date: Thu, 17 Jun 2004 09:01:21 -0400 (EDT) From: "Ilmar S. Habibulin" To: Scott Long In-Reply-To: <40D023EE.7020302@freebsd.org> Message-ID: <20040617081225.H28897@fledge.watson.org> References: <40CFC0A0.1000604@mWare.ca> <20040616034055.GE26532@electra.cse.Buffalo.EDU> <40CFC2CF.8080509@mWare.ca> <20040616085518.GA8881@kt-is.co.kr> <40D011A8.1030404@freebsd.org> <20040616102504.GB8881@kt-is.co.kr> <40D023EE.7020302@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-sparc64@freebsd.org Subject: Re: IT! WORKS! 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, 17 Jun 2004 13:03:18 -0000 On Wed, 16 Jun 2004, Scott Long wrote: > It would be very intereting to get some testing results from a blade100 > and an Ultra5/10 on this. If people with this hardware can test and > report back both whether it helps/hurts and if it had any impact on CPU > load, I'll commit it. I want to confirm type speed up on blade100 with this patch applied. Can't tell top values now because of some bug, which causes kernel panic. So i have unbootable blade now. :( This bug is not related to the patch. I think i've reported it once. If you use screen as console and log in via ssh, kernel panics after some period of time. Don't know how to trace this panics, should i make the same steps like on i386 - set dumdev, use dump, kernel.debug and gdb -k?