From owner-freebsd-arm@FreeBSD.ORG Fri Sep 5 21:43:32 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E3B201CA for ; Fri, 5 Sep 2014 21:43:32 +0000 (UTC) Received: from bein.link (unknown [IPv6:2a02:2770:3:0:21a:4aff:fee6:9061]) by mx1.freebsd.org (Postfix) with ESMTP id AC9D31266 for ; Fri, 5 Sep 2014 21:43:32 +0000 (UTC) Received: from quad.localnet (unknown [188.134.8.193]) by bein.link (Postfix) with ESMTPSA id 0EBD34051D for ; Fri, 5 Sep 2014 23:43:24 +0200 (CEST) From: Maxim V FIlimonov To: freebsd-arm@freebsd.org Subject: Cubieboard: Spurious interrupt detected Date: Sat, 06 Sep 2014 01:43:23 +0400 Message-ID: <2279481.3MX4OEDuCl@quad> User-Agent: KMail/4.12.5 (FreeBSD/10.0-RELEASE-p7; KDE/4.12.5; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 21:43:33 -0000 And another problem: every now and then the kernel says something like that: Sep 5 19:22:37 kernel: Spurious interrupt detected Sep 5 19:22:37 kernel: Spurious interrupt detected Sep 5 19:23:46 last message repeated 10 times I've heard that FreeBSD happens to do that on ARM devices. What could be the problem here? -- wbr, Maxim Filimonov che@bein.link