Date: Fri, 20 May 2011 05:07:38 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: freebsd-sparc64@freebsd.org Cc: Marius Strobl <marius@alchemy.franken.de> Subject: Re: "panic: cpu_initclocks: could not determine STICK frequency" booting V890 Message-ID: <20110519190738.GA75174@server.vk2pj.dyndns.org> In-Reply-To: <20110517010554.GA75440@server.vk2pj.dyndns.org> References: <20110517010554.GA75440@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Moving back on-list] On 2011-May-17 11:05:55 +1000, Peter Jeremy <peterjeremy@acm.org> wrote: >I've found an unused V890 (64GB RAM, 8 dual-core 1.35GHz US-IV CPUs, >12 146GB FC disks) and thought I'd try FreeBSD on it (especially since >I had a copy of FreeBSD-8.2-RC2 lying around on CD). My initial try >failed with "panic: kmem_suballoc: bad status return of 3" but >limiting the RAM to 4GB with hw.physmem worked around that. >Unfortunately, it then panic's as above. > >Looking at the sources, the only recent change in that area of >sparc64/sparc64/tick.c is related to Serengeti-class machines (which >the V890 isn't). Thanks to Marius for having a look through an OFW dump of "my" V890. Turns out that, as with the Serengeti-class machines, the stick-frequency property is also on the nexus device and booting a recent 8.2 snapshot works. --=20 Peter Jeremy --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk3VanoACgkQ/opHv/APuIcJYACfacuVRHohE2iVTTWFzLN0Gp7o +3EAoMFBSzP64lFL/ou2Kz2UQuwnaMQ+ =BsIH -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110519190738.GA75174>