From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 21:18:20 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 279C2106564A; Tue, 22 Jun 2010 21:18:20 +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 810638FC15; Tue, 22 Jun 2010 21:18:19 +0000 (UTC) Received: by fxm7 with SMTP id 7so3196569fxm.13 for ; Tue, 22 Jun 2010 14:18:18 -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=ADXElO8TEWIr/pwetOArim3Itdk+/155YDLYTF5WA5c=; b=Kwvj3C2b4fT+NY0hEbuNLnN2Nqmm3wc76AuROZc9MRMjUl02kvValhAv+gcq/53RXB EddzdUmgvymKeR335QXBddQ/MLKqNRUeXWyQ1omqn8VpKy9F/H1zppQSRr2z9JJZJGCU Na80VqAUQOPi4WTveGLnijCbSt1Hlq+oMvnEc= 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=wTVKzuZpPUNK1NRr84o29nczI5+A0xCUPbpj3S08tNvRvUXvLCljSwLRPB+ouWzOdr 02PeB73nIhxXDuRJsyqWRjHge6h4AhZCc9S/jiY8xdkIr7B+nufA3p8JkTl8Z4Fi8E2O Yth7lBKVpFYPvX7h941CkEhO48J4KX0ynC4wY= Received: by 10.223.92.153 with SMTP id r25mr6733863fam.76.1277241498327; Tue, 22 Jun 2010 14:18:18 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id o11sm30850912fal.43.2010.06.22.14.18.17 (version=SSLv3 cipher=RC4-MD5); Tue, 22 Jun 2010 14:18:17 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C212873.5010807@FreeBSD.org> Date: Wed, 23 Jun 2010 00:17:39 +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> In-Reply-To: <4C212460.1070200@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:18:20 -0000 Doug Barton wrote: > On 06/22/10 13:10, Alexander Motin wrote: >> Doug Barton wrote: >>> On 06/22/10 12:55, Doug Barton wrote: >>>> Howdy, >>>> >>>> I tried upgrading from r209351 to r209434 and got a panic related >>>> to the timer stuff while booting. You can see the panic and the >>>> backtrace here: >>>> >>>> http://people.freebsd.org/~dougb/timer-panic-1.jpg >>>> http://people.freebsd.org/~dougb/timer-panic-2.jpg >>>> http://people.freebsd.org/~dougb/timer-panic-3.jpg >>> Hmmm, that could use a little more detail. :) I have a Dell laptop >>> with a core 2 duo processor, running 9-current SMP i386. >> Your ACPI seems reports that attimer uses IRQ2, instead of usual >> IRQ0. It is either a bug, or it is a very rare feature. >> >> I am not sure it is not a hack, but you may try attached patch. > > Ok, I updated to r209441, then applied your patch. FYI, I applied it in > src/sys/x86/isa/ using -p2. This allowed me to boot, verbose dmesg is at > http://people.freebsd.org/~dougb/dmesg-verbose-norid-patch.txt > >> If it helps, it would be nice it you tried to use i8254 event timer, >> to check is this a bug or feature. > > Ok, I'm willing to give that a try if you tell me how. :) 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), then check 'vmstat -ia' to see whether irq0 interrupts are arriving, then run 'systat -vm 1' to be absolutely sure. If `vmstat -ia` won't show irq0 interrupts, try to figure out what else can arrive instead of it. -- Alexander Motin