Date: Tue, 6 May 2003 22:08:02 -0700
From: Andrew Morton <akpm@digeo.com>
To: "David S. Miller" <davem@redhat.com>
Cc: johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: tg3 - irq #: nobody cared!
Message-Id: <20030506220802.6d494326.akpm@digeo.com>
In-Reply-To: <1052283509.9817.1.camel@rth.ninka.net>
References: <1052258580.4495.12.camel@w-jstultz2.beaverton.ibm.com>
	<1052283509.9817.1.camel@rth.ninka.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1055
Lines: 25

"David S. Miller" <davem@redhat.com> wrote:
>
> On Tue, 2003-05-06 at 15:03, john stultz wrote:
> > 	Not sure if this is the proper fix, but it stops the kernel from
> > complaining. I saw Andrew suggest something similar for a sound driver.
> 
> Definitely not the right fix.  If the hardware status struct
> indicates no event is pending, then we return 0 since we
> didn't "handle" the interrupt.

This is about the fifth report of unhandled interrupts.  Against the fifth
driver which looks to be correct.

So I'd be suspecting the scenario which Alan outlined: the IRQ handler looped
around, scooped up the interrupt source before the APIC delivered the IRQ.

I'm working on the actual detection code - it tries to filter out the false
positives.

Suggest we ignore these reports until that is sorted out.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/