Date: Tue, 17 May 2011 11:05:55 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: freebsd-sparc64@freebsd.org Subject: "panic: cpu_initclocks: could not determine STICK frequency" booting V890 Message-ID: <20110517010554.GA75440@server.vk2pj.dyndns.org>
next in thread | raw e-mail | index | archive | help
--azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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). Does anyone have any suggestions? A verbose boot is available at http://pastie.org/1913906 --=20 Peter Jeremy --azLHFNyN32YCQGCU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk3RyfIACgkQ/opHv/APuIfBZgCfYOyLeCS8mnIzgBjxZUqipzq7 GHMAoLw6+QTixCRL5WLAE0ZMjP8JQ7P0 =FH6P -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110517010554.GA75440>