From owner-freebsd-sparc64@FreeBSD.ORG Wed Dec 2 19:21:49 2009 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 64E0A106566C for ; Wed, 2 Dec 2009 19:21:49 +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 CCCE98FC08 for ; Wed, 2 Dec 2009 19:21:48 +0000 (UTC) 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 nB2JLYiw075614; Wed, 2 Dec 2009 20:21:34 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id nB2JLY8P075613; Wed, 2 Dec 2009 20:21:34 +0100 (CET) (envelope-from marius) Date: Wed, 2 Dec 2009 20:21:34 +0100 From: Marius Strobl To: Anton Shterenlikht Message-ID: <20091202192134.GA6562@alchemy.franken.de> References: <20091201154904.GA11679@mech-cluster241.men.bris.ac.uk> <20091201165752.GA12095@mech-cluster241.men.bris.ac.uk> <20091201215130.GA64974@alchemy.franken.de> <20091202124137.GA20168@mech-cluster241.men.bris.ac.uk> <20091202125915.GA20276@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091202125915.GA20276@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: trouble installing to sun blade 1500 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: Wed, 02 Dec 2009 19:21:49 -0000 On Wed, Dec 02, 2009 at 12:59:15PM +0000, Anton Shterenlikht wrote: > On Wed, Dec 02, 2009 at 12:41:37PM +0000, Anton Shterenlikht wrote: > > On Tue, Dec 01, 2009 at 10:51:30PM +0100, Marius Strobl wrote: > > > > > > > > I get to OK prompt, type "boot cdrom", but the process > > > > > > stops after a few seconds with: > > > > > > > > > > > > jumping to kernel entry at 0xc0088000. > > > > > > > > > > > > You're using an unsupported framebuffer (see the release notes). > > > > yes, I missed that, thank you > > > > > This unfortunately isn't sufficient information and my Blade 1500 > > > doesn't exhibit this problem. Could you please put the full dmesg > > > output online somewhere (this should be easy to capture when > > > using a serial console)? Can you boot to single user? > > > > a multi-user boot dmesg: > > http://seis.bris.ac.uk/~mexas/dmesg-blade1500-8.0 > > > > a single user boot went ok, but some disk problems: > > http://seis.bris.ac.uk/~mexas/dmesg-blade1500-8.0-single-user > > just to add on that. After fixing disk with fsck, boot into single > user mode is fine, and no further disk problems reported. > But multi-user mode still panics, just as before. > Hrm, the only noticeable difference between your Blade 1500 and mine is that on yours the generic vgapci(4) attaches to the otherwise unsupported framebuffer. I gave such a setup a try but that didn't trigger a panic (this actually wasn't likely to). Could you please build and install a debugging kernel in single user mode (a `mount -a` should re-mount / read-write), i.e. a kernel with the following options: makeoptions DEBUG=-g options KDB options DDB If that kernel panics you should end up in the debugger prompt. Please issue a `bt` there and provide its output. Marius