Date: Wed, 25 Nov 2009 19:02:38 -0600 From: Erich Jenkins <erich@fuujingroup.com> To: Marius Strobl <marius@alchemy.franken.de> Cc: freebsd-sparc64@freebsd.org Subject: Re: SunFire v1280 Message-ID: <4B0DD3AE.1000305@fuujingroup.com> In-Reply-To: <20091124213724.GO6562@alchemy.franken.de> References: <4B09150E.7060006@fuujingroup.com> <20091123200233.GB33571@alchemy.franken.de> <20091123215343.GA86389@hub.freebsd.org> <4B0B260D.1030306@fuujingroup.com> <20091124213724.GO6562@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Marius Strobl wrote: > On Mon, Nov 23, 2009 at 06:17:17PM -0600, Erich Jenkins wrote: >> Marius Strobl wrote: >>> On Mon, Nov 23, 2009 at 09:02:33PM +0100, Marius Strobl wrote: >>>> On Sun, Nov 22, 2009 at 04:40:14AM -0600, Erich Jenkins wrote: >>>>> All: >>>>> >>>>> I'm running into an interesting problem with a SunFire v1280 mid-range >>>>> server. The system is running (12) UltraSPARC III procs @ 1.2GHz with >>>>> 24GB of RAM and SCSI3 spindles (no RAID). The SC and system boards are >>>>> running the most recent firmware, as you can see in the message below. >>>>> >>>>> After trying several releases (6.3, 6.4, 7.0, 7.1, 7.2), I'm running >>>>> into this message below. I've tried booting from the CD-ROM and from >>>>> tftp/dhcp/nfs with the same results. >>>>> >>>>> <snip> >>>>> Sun Fire V1280 >>>>> OpenFirmware version 5.20.13 (06/04/09 02:43) >>>>> Copyright 2009 Sun Microsystems, Inc. All rights reserved. >>>>> Use is subject to license terms. >>>>> SmartFirmware, Copyright (C) 1996-2001. All rights reserved. >>>>> 24576 MB memory installed, Serial #55083219. >>>>> Ethernet address 0:3:ba:48:80:d3, Host ID: 834880d3. >>>>> >>>>> >>>>> Rebooting with command: boot cdrom >>>>> TL = 1, TT = 10. ERROR: Illegal Instruction >>>>> TSTATE= 0x1400 [ccr = 0x0, asi = 0x0, pstate = 0x14, cwp = 0x0] >>>>> TPC= 0000000000004004 >>>>> TNPC= 0000000000004008 >>>>> TICK= 8000000845e5cbd8, TICKCMP = 8000000000000000 >>>>> >>>>> debugger entered. >>>>> </snip> >>>> While this particular problem should be easy to solve, v1280 >>>> also require several workarounds for additional quirks and >>>> some new drivers to be written, requiring access to such a >>>> machine in a netboot environment. How much are you interested >>>> into getting FreeBSD to work on these and what would be the >>>> required timeframe? In any case could you please provide a >>>> Open Firmware device tree dump of this machine (`prtconf -pPv` >>>> in Solaris). >>>> >> >> Marius: >> >> This is about as much information as I can offer regarding these >> v1280's. Since these are not running Solaris, I've grabbed the info from >> the lom and SC. Hope this helps. > > Unfortunately, these don't provide the same level of information > as a complete device tree dump. Without FreeBSD or Solaris running > on the machine there's no sane way to obtain it though (I don't > know whether OpenBSD provides such a tool). > >> As for getting them up and running, >> soon would be good, and however I can assist, I will. > > Well, you'd need to provide access to the LOM and a netboot > environment for testing loaders and kernels. Before starting > a new such endeavor I'd like to finish porting FreeBSD to > the PCI-Express based sun4u machines though and also will > be busy changing next at the beginning of next year, which > means I probably won't start working on this before next > February. > > Marius > Marius: That sounds just fine. I'll get a lab environment set up for you. Thanks for your help. I think FreeBSD can be invaluable to others with access to this platform, and I look forward to being able to run it on them. Erich M. Jenkins Fuujin Group Limited PO Box 792 Brainerd, MN 56401 (p) 218-824-5038 (f) 218-824-7516 Visit us on the web at http://www.fuujingroup.com "You should never, never doubt what no one is sure about." -- Gene Wilder
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B0DD3AE.1000305>