From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 21:59:52 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 785AB106564A; Tue, 22 Jun 2010 21:59:52 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id CB86F8FC08; Tue, 22 Jun 2010 21:59:51 +0000 (UTC) Received: by fxm7 with SMTP id 7so3215963fxm.13 for ; Tue, 22 Jun 2010 14:59:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=jEClbIQClkuvY+ipuVsLv1nnzVVURSdZNW4VkM8KZeg=; b=qPd5/RIqOs+xDrA6Fpbiyo4qEoUgCbCD2A1T9g6AdEpI+yUpcAwpR8DfXyNipMWiDh GoX/mLa+3Hg+wdx0Z2aliaX1ynxoRkEvUsrFEsoU89Dd82EaspS1fskX4RNewO8AYAeo 8MyobrkrGtoBRQuA0rpihG5oqNGsD+HfXVemw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=QXULLpUZ5vjSqFZWzCxEpmGvh2/Qh4L+r9ypzU2OxOLH/cJKuMJaoC+ouT1SfcKSiX /uy7Y7DScUeBrREB7vCK01FSdy3jy0p/pVAG6I2WbaqGdbxDlPO2Fhutdx+HKAsI6S0N OHSIMUnTq1ex5+KvNIw+gU+8IfptRp6viyuFo= Received: by 10.223.35.12 with SMTP id n12mr6796652fad.35.1277243990689; Tue, 22 Jun 2010 14:59:50 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id j23sm30930221faa.26.2010.06.22.14.59.49 (version=SSLv3 cipher=RC4-MD5); Tue, 22 Jun 2010 14:59:50 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C21322F.9080009@FreeBSD.org> Date: Wed, 23 Jun 2010 00:59:11 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Doug Barton References: <4C211538.1040808@FreeBSD.org> <4C2115D2.5080504@FreeBSD.org> <4C2118D1.3080903@FreeBSD.org> <4C212460.1070200@FreeBSD.org> <4C212873.5010807@FreeBSD.org> <4C212DB9.6030308@FreeBSD.org> In-Reply-To: <4C212DB9.6030308@FreeBSD.org> X-Enigmail-Version: 0.96.0 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:59:52 -0000 Doug Barton wrote: > 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. OK, thanks. It means that your ACPI is lying for some reason. I'll probably commit this patch tomorrow. > Should I continue using the HPET timer? As you wish. > Is it "better" in some way? Comparing to what? Comparing to LAPIC - it is not dying in C3. Comparing to RTC - if is faster and much more flexible. Comparing to i8254 - it can work per-CPU and supports one-shot mode, both not very important now, but should benefit later. > Anything else I can do to help? Find any more issues to fix. :) As you have latest HEAD, you may try my latest addition (r209440) - HPET "legacy route" support. It should allow HPET to work per-CPU on your hardware. To enable it, add such lines to /boot/loader.conf: hint.atrtc.0.clock=0 hint.attimer.0.clock=0 hint.hpet.0.legacy_route=1 -- Alexander Motin