From owner-freebsd-arm@FreeBSD.ORG Thu May 1 23:48:26 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1CB1DBE0 for ; Thu, 1 May 2014 23:48:26 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5AC51B1D for ; Thu, 1 May 2014 23:48:25 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Wg0iH-000JDL-3m; Thu, 01 May 2014 23:48:25 +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 s41NmMDm019352; Thu, 1 May 2014 17:48:22 -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: U2FsdGVkX1+x9BKt/oMf1dkmEuVgt/J2 Subject: Re: wandboard-quad (IO related?): Spurious interrupt detected [0x000003ff] From: Ian Lepore To: Boris Samorodov In-Reply-To: <5362BCBE.7050703@passap.ru> References: <5362BCBE.7050703@passap.ru> Content-Type: text/plain; charset="us-ascii" Date: Thu, 01 May 2014 17:48:22 -0600 Message-ID: <1398988102.22079.146.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 23:48:26 -0000 On Fri, 2014-05-02 at 01:29 +0400, Boris Samorodov wrote: > Hi All, > > I get "Spurious interrupt detected [0x000003ff]" at current system: > ----- > % uname -a > FreeBSD wandboard 11.0-CURRENT FreeBSD 11.0-CURRENT #5 r265089M: Thu May > 1 16:48:06 SAMT 2014 > bsam@wandboard:/usr/obj/usr/src/sys/WANDBOARD-QUAD arm > ----- > > Those messages appear at hard IO (CD read/write, network - iperf). > Seems no harm so far. Should I ignore or diagnose them deeper? > > Thanks. They are not harmful, and it's baffling to me why sometimes you get tons of them, other times hardly any at all. It's actually normal and expected to get some on a multi-core system, because two cores may try to respond to a pending interrupt at the same time, and the interrupt controller will dispatch the actual interrupt to one of the cores and the spurious-interrupt 3ff number to the other core. So what we really need to be doing in the code is complaining if a whole lot of them are happening (it might indicate some device driver is misbehaving) but ignore the occasional one. -- Ian