From owner-freebsd-sparc64@FreeBSD.ORG Mon Feb 21 19:47:52 2005 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A95BE16A4CF for ; Mon, 21 Feb 2005 19:47:52 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4279B43D5C for ; Mon, 21 Feb 2005 19:47:52 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3D69B512F2; Mon, 21 Feb 2005 11:47:51 -0800 (PST) Date: Mon, 21 Feb 2005 11:47:51 -0800 From: Kris Kennaway To: Kris Kennaway Message-ID: <20050221194750.GA49363@xor.obsecurity.org> References: <20050214203742.GA46345@xor.obsecurity.org> <37395.1108419291@critter.freebsd.dk> <20050214230635.GA86332@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <20050214230635.GA86332@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: Poul-Henning Kamp cc: sparc64@FreeBSD.org Subject: Re: System clock died on e420r X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2005 19:47:52 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 14, 2005 at 03:06:35PM -0800, Kris Kennaway wrote: > On Mon, Feb 14, 2005 at 11:14:51PM +0100, Poul-Henning Kamp wrote: > >=20 > > If hardclock dies, timecounters (like much else) suffers. >=20 > Surely, so why is it happening and how can it be fixed? :) >=20 > jhb suspected there might be unserialized access to the time counter > on sparc64. This doesn't explain the i386 problems, but they could be > related to other recent commits. Note that the only problems I've > seen so far are on SMP machines. It happened again on a quad-cpu e450 machine after updating it from RELENG_5 from December to top of RELENG_5. What sparc64-related changes have recently been merged that could cause this? Kris --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCGjrmWry0BWjoQKURAkLNAKCDhASOmZWh5JK7/CKGUdhT31tXYwCgzI6Q Nd6dpBv+MWoGolR4CTmiG2U= =IXXQ -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO--