Date: Mon, 14 Feb 2005 15:06:35 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: System clock died on e420r Message-ID: <20050214230635.GA86332@xor.obsecurity.org> In-Reply-To: <37395.1108419291@critter.freebsd.dk> References: <20050214203742.GA46345@xor.obsecurity.org> <37395.1108419291@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
--MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 14, 2005 at 11:14:51PM +0100, Poul-Henning Kamp wrote: >=20 > If hardclock dies, timecounters (like much else) suffers. Surely, so why is it happening and how can it be fixed? :) 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. Kris --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCES77Wry0BWjoQKURAmqCAJ0YpJq6c5se2hdmLxF+3TsHlY4NuACfdOP4 KK2NbvnwNvuxGpE0MY3Hnjc= =QG+o -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050214230635.GA86332>