From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MBMyA-00081c-Sd for garchives@archives.gentoo.org; Tue, 02 Jun 2009 05:55:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6C327E041B; Tue, 2 Jun 2009 05:55:29 +0000 (UTC) Received: from mail-bw0-f175.google.com (mail-bw0-f175.google.com [209.85.218.175]) by pigeon.gentoo.org (Postfix) with ESMTP id 0AF17E041B for ; Tue, 2 Jun 2009 05:55:28 +0000 (UTC) Received: by bwz23 with SMTP id 23so7019042bwz.34 for ; Mon, 01 Jun 2009 22:55:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=I6kxs4dl+nQYXXkE4EC387Q/AHKDh/vE8X1eBtWiB8U=; b=E99p5bUEZTK2cV7W+bCeLrcbAL6x03mwzXaP6C+dWWervHC8Vbs3onZlttPxDPBfsQ y6b3abR3MhKIOogYX+QI/fauwwQi5HGffckVCmLIm/zEQZu9t/DwF2LoPnhBd4i40TnT hpydPGIB4PZ8WZSsMO+XQR7tvxQlcHDtoahlA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=hKFSozXVLJRyxYGezCI/LiN5aykjroygXy7b8KjgkJZ8ZCBZzQsvN7aTf5/pMUraY8 NI7Ukzaw3rwNbeEvwFief4FBSjqHxQxOyleM8a/EMxLPyTtKYXmaHRt7xWBKDuC8ha+9 NECjhnnoeZhzLE0ajOEr8q808Em8XPtch48Bs= Received: by 10.103.131.13 with SMTP id i13mr1895119mun.64.1243922128089; Mon, 01 Jun 2009 22:55:28 -0700 (PDT) Received: from lappy.study (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id j6sm1974483mue.31.2009.06.01.22.55.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 01 Jun 2009 22:55:26 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: chronyd troubleshooting Date: Tue, 2 Jun 2009 06:54:43 +0100 User-Agent: KMail/1.9.9 References: <200905190708.36103.michaelkintzios@gmail.com> In-Reply-To: <200905190708.36103.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart73178887.k74miPanHq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200906020655.15145.michaelkintzios@gmail.com> X-Archives-Salt: 42d2bc0d-d40e-4c36-bc1b-1b7af0d9f9a7 X-Archives-Hash: b3b3f57c5bb6b3899289e7bd41a1cc29 --nextPart73178887.k74miPanHq Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 19 May 2009, Mick wrote: > A couple of days ago chronyd stopped functioning. > > This is all that the logs tell me but I don't know what I can do to fix i= t: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > May 19 06:25:13 lappy chronyd[6756]: chronyd version 1.23 starting > May 19 06:25:14 lappy chronyd[6756]: Set system time, error in RTC > =3D -306.664140 > May 19 06:25:14 lappy chronyd[6756]: Set system time, error in RTC > =3D -306.664140 > May 19 06:30:20 lappy chronyd[6756]: Initial txc.tick=3D10000 txc.freq=3D0 > (0.00000000) txc.offset=3D0 =3D> hz=3D100 shift_hz=3D7 > May 19 06:30:20 lappy chronyd[6756]: Initial txc.tick=3D10000 txc.freq=3D0 > (0.00000000) txc.offset=3D0 =3D> hz=3D100 shift_hz=3D7 > May 19 06:30:20 lappy chronyd[6756]: set_config_hz=3D0 hz=3D100 shift_hz= =3D7 > basic_freq_scale=3D1.28000000 nominal_tick=3D10000 slew_delta_tick=3D833 > max_tick_bias=3D1000 > May 19 06:30:20 lappy chronyd[6756]: set_config_hz=3D0 hz=3D100 shift_hz= =3D7 > basic_freq_scale=3D1.28000000 nominal_tick=3D10000 slew_delta_tick=3D833 > max_tick_bias=3D1000 > May 19 06:30:20 lappy chronyd[6756]: Linux kernel major=3D2 minor=3D6 pat= ch=3D28 > May 19 06:30:20 lappy chronyd[6756]: Linux kernel major=3D2 minor=3D6 pat= ch=3D28 > May 19 06:30:20 lappy chronyd[6756]: calculated_freq_scale=3D0.99902439 > freq_scale=3D0.99902439 > May 19 06:30:20 lappy chronyd[6756]: calculated_freq_scale=3D0.99902439 > freq_scale=3D0.99902439 > May 19 06:30:20 lappy chronyd[6756]: Could not start measurement : > Inappropriate ioctl for device > May 19 06:30:20 lappy chronyd[6756]: Could not read flags /dev/rtc : > Input/output error > May 19 06:30:20 lappy chronyd[6756]: Could not stop measurement : > Inappropriate ioctl for device > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # ls -al /dev/rtc > crw-r--r-- 1 root root 10, 135 May 19 06:24 /dev/rtc > > When I try to check /dev/rtc I get: > > # cat /dev/rtc > cat: /dev/rtc: Input/output error > > I should be getting resource busy instead. > > I suspect that this problem started when I changed my kernel to 2.6.28-r5= =2E=20 > I noticed it comes up with a APIC error on booting, could this be related? Yep, it was related to the kernel, or to be more precise it was related to= =20 HPET being enabled in the kernel. For some reason it clashed ... How can I tell if my CPU/MoBo supports HPET? =2D-=20 Regards, Mick --nextPart73178887.k74miPanHq Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEABECAAYFAkokvsMACgkQVTDTR3kpaLZVWACgrhASWQFUcRawpSZXemfEKuoR t1wAmgN0/hmlK0ALUmJqr7kGilVvYZSV =H9JT -----END PGP SIGNATURE----- --nextPart73178887.k74miPanHq--