From owner-freebsd-bugs@freebsd.org Wed Aug 17 09:23:27 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C327EBBCEF2 for ; Wed, 17 Aug 2016 09:23:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2D271638 for ; Wed, 17 Aug 2016 09:23:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7H9NRLv079684 for ; Wed, 17 Aug 2016 09:23:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211897] horrible time skew under 10.3-R-p7 Date: Wed, 17 Aug 2016 09:23:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-bugzilla@ayaken.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2016 09:23:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211897 --- Comment #8 from Martin S. Weber --- (In reply to Konstantin Belousov from comment #4) So, I can confirm that unpatched finds my CPU at 4GHz equals 4000 MHz. Sadly there seems to be a random element in -p7 finding my CPU at 4 GHz equ= als 4400 MHz, as my most recent two -p7 boots could not reproduce; I've checked, out of my previous 24 boots (4 of which being -p7) only once (a p7) my CPU = was found to be 4439.49-MHz, all the other times it's 4000.08 +/- 0.01 MHz On a -p7 boot that does not see my CPU as 4.4 GHz I cannot see the massive clock drift I have observed on the one p7 boot. I do not need to adjust my eventtimers & timecounters - it just works. I'll have to wait and see when = the next boot gives me a 4.4 Ghz. Maybe it's windows (I dual boot between work = OS and gaming console) that left something programmed in the CPU (even though I cold-boot between the OS as otherwise my sound & video do funny things). Per Arthur Chance, I note that sysctl.dev.cpu.0.freq_levels outputs (on -p7 that sees my CPU as 4Ghz): dev.cpu.0.freq_levels: 4001/88000 4000/88000 3800/81704 3500/72258 3300/665= 30 3100/60999 2900/55687 2600/48456 2400/43627 2200/39003 1900/32072 1700/27930 1500/23963 1300/20178 1000/15137 800/11779 Not sure where the PR is going, I clearly had the problem once, even though= I cannot reliably reproduce it now. --=20 You are receiving this mail because: You are the assignee for the bug.=