From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 21:40:13 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 088FD1065675 for ; Tue, 22 Jun 2010 21:40:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id A499D8FC12 for ; Tue, 22 Jun 2010 21:40:12 +0000 (UTC) Received: (qmail 17069 invoked by uid 399); 22 Jun 2010 21:40:10 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 22 Jun 2010 21:40:10 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C212DB9.6030308@FreeBSD.org> Date: Tue, 22 Jun 2010 14:40:09 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100621 Thunderbird/3.0.5 MIME-Version: 1.0 To: Alexander Motin References: <4C211538.1040808@FreeBSD.org> <4C2115D2.5080504@FreeBSD.org> <4C2118D1.3080903@FreeBSD.org> <4C212460.1070200@FreeBSD.org> <4C212873.5010807@FreeBSD.org> In-Reply-To: <4C212873.5010807@FreeBSD.org> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: Timer panic on boot (r209434) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2010 21:40:13 -0000 On 06/22/10 14:17, Alexander Motin wrote: > Run `sysctl kern.eventtimer.timer2=i8254`, then after few seconds check > messages to see if system liked this timer (it should fall back > automatically if it's not), Seems ok. Here is what I got on the console, no error messages in /var/log/all. sysctl kern.eventtimer.timer2=i8254 kern.eventtimer.timer2: HPET1Starting kernel event timers: HPET @ 100Hz, i8254 @ 128Hz -> i8254 t_delta 16.01a20d312197c8b0 too long > then check 'vmstat -ia' to see whether irq0 interrupts are arriving, This also seems fine: interrupt total rate ??? 0 0 irq1: atkbd0 3448 1 stray irq1 0 0 irq0: attimer0 15756 6 stray irq0 0 0 irq3: 0 0 stray irq3 0 0 The total for irq0 is going up consistently. > then run 'systat -vm 1' to be absolutely sure. That also seemed fine. Here is a sample: 104 hpet0 uhci If I did nothing but stare at the screen the value was fairly consistently 100, with occasional values of 99 or 107. Once I started moving the mouse it jumped around a little, but stabilized again when I left the mouse alone. Should I continue using the HPET timer? Is it "better" in some way? Anything else I can do to help? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/