From owner-freebsd-embedded@FreeBSD.ORG Tue Jun 4 15:21:40 2013 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C5D3BCD0 for ; Tue, 4 Jun 2013 15:21:40 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id A11241893 for ; Tue, 4 Jun 2013 15:21:37 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Ujt3C-000N1j-UW; Tue, 04 Jun 2013 15:21:31 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r54FLQGg015640; Tue, 4 Jun 2013 09:21:26 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18K0jsl+S+m2fTvevMs1GJ1 Subject: Re: No usable event timer, FreeBSD Current, PCEngines WRAP From: Ian Lepore To: Nigel Williams In-Reply-To: <51ADA7AD.3060508@swin.edu.au> References: <51ADA7AD.3060508@swin.edu.au> Content-Type: text/plain; charset="us-ascii" Date: Tue, 04 Jun 2013 09:21:26 -0600 Message-ID: <1370359286.1258.102.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 15:21:40 -0000 On Tue, 2013-06-04 at 18:39 +1000, Nigel Williams wrote: > Hi, > > I'm attempting to run FreeBSD-10 CURRENT (built using nanoBSD) on a > PC-Engines WRAP device, and encounter the following during boot: "panic: > No usable event timer found!" after which the machine reboots. I have > been able to run pfSense 2.0.1 (bsd 8.1) and it appears to find the > i8254 timer. > > The verbose boot output: > https://docs.google.com/file/d/0B9KWjvUN8efvQ0RMNXRzRS1rS0k/edit?usp=sharing > > Kernel conf: > https://docs.google.com/file/d/0B9KWjvUN8efvLUpRekJORWhmSFE/edit?usp=sharing > > nanoBSD conf: > https://docs.google.com/file/d/0B9KWjvUN8efvTzIya3pNUXc5elk/edit?usp=sharing > > any suggestions? The problem does seem to be that the i8254 (atrtc) device isn't instantiated. I'm not sure whether the acpi errors at the start are innocuous warnings or the cause of the problem (it has ever been thus with acpi -- you report an error message on a mailing list and the response is often "that's normal, you can ignore it"). The atrtc device should be found via PNP data or /boot/device.hints if not via acpi. Perhaps acpi is working "enough" that it thinks it should be using it, but not enough to find the timer. You could try "set hint.acpi.0.disabled=1" at the loader prompt and see if that changes anything. If it does, I'd call it more of a workaround than a fix. -- Ian