From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 0/1] NIU: fix spurious interrupts Date: Thu, 21 May 2009 15:18:41 -0700 (PDT) Message-ID: <20090521.151841.160383267.davem@davemloft.net> References: <4A132A0F.8070800@windriver.com> <20090519.150156.115978100.davem@davemloft.net> <4A14285C.1040705@windriver.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, matheos.worku@sun.com To: hong.pham@windriver.com Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:42375 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753743AbZEUWSn (ORCPT ); Thu, 21 May 2009 18:18:43 -0400 In-Reply-To: <4A14285C.1040705@windriver.com> Sender: netdev-owner@vger.kernel.org List-ID: From: "Hong H. Pham" Date: Wed, 20 May 2009 11:57:16 -0400 > I've added the suggested instrumentations to dump out the LD interrupt > registers > when spurious interrupts occur. Attached below is a kernel log. > > In all cases, interrupts are being generated even though the LDG has > been disarmed! There's a bug in your debugging patch: + ld_im0_reg = LD_IM0(ldn); + ldg_imgmt_reg = LDG_IMGMT(ldn); You're reading the register "address", not the register's "value". So all of the debugging output is bogus. You need to do nr64(ld_im0_reg) and use that as the value, for example. Can you rerun the test with this fixed? Thanks!