From owner-freebsd-sparc64@FreeBSD.ORG Tue Nov 4 22:10:05 2008 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64A8D1065686 for ; Tue, 4 Nov 2008 22:10:05 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id EB3DD8FC16 for ; Tue, 4 Nov 2008 22:10:04 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id mA4MA34e014614; Tue, 4 Nov 2008 23:10:03 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id mA4MA38G014613; Tue, 4 Nov 2008 23:10:03 +0100 (CET) (envelope-from marius) Date: Tue, 4 Nov 2008 23:10:03 +0100 From: Marius Strobl To: Mark Linimon Message-ID: <20081104221003.GE31338@alchemy.franken.de> References: <20081031124442.GB9102@soaustin.net> <183638.12752.qm@web56802.mail.re3.yahoo.com> <20081031131827.GA9613@soaustin.net> <20081103223042.GB8256@alchemy.franken.de> <20081104115722.GA28394@soaustin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081104115722.GA28394@soaustin.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Free Ultra2 in Silicon Valley, USA X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2008 22:10:05 -0000 On Tue, Nov 04, 2008 at 05:57:22AM -0600, Mark Linimon wrote: > On Mon, Nov 03, 2008 at 11:30:42PM +0100, Marius Strobl wrote: > > Anyway, the panic message provided isn't enough info to even > > guess what the real cause is. > > I think I have more notes at home (not accessible ATM). > > > I think the easiest way to proceed would be to remove the remaining > > NIC (is there a reason you disabled gem(4) for the on-board ones?) > > The kernels that we run are pretty lean; it's possible that that > driver is not included. Or, are you talking about something in the > hardware setup? No, I just wondered if there's a reason gem(4) wasn't included in the kernel, f.e. hme(4) worked better for you or something... > > > and mass storage controller drivers one by one and see when the > > panic goes away. > > Is this something that can be done remotely? I'm a thousand miles > away from the machines :-) Well, if you can't netboot them you already lost when it comes to getting a working kernel onto them unless there's someone onsite who can insert a CD with a working one. Otherwise you can experiment pretty much anything including removal of the drivers required to mount root remotely as long as you've access to the serial console. > > > That said, my T1 AC200 is running fine and I've never seen such a > > problem with it... > > These things have an add-in card with 4 more ethernet slots IIRC; > could the difference in configuration explain things? > That might make the difference and I've planned to give that configuration a try but I need to fetch mine from the datacenter in order to do so. Marius