Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262853AbTEGE6d (ORCPT ); Wed, 7 May 2003 00:58:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262856AbTEGE6d (ORCPT ); Wed, 7 May 2003 00:58:33 -0400 Received: from pizda.ninka.net ([216.101.162.242]:16621 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id S262853AbTEGE6c (ORCPT ); Wed, 7 May 2003 00:58:32 -0400 Date: Tue, 06 May 2003 21:03:32 -0700 (PDT) Message-Id: <20030506.210332.23029446.davem@redhat.com> To: akpm@digeo.com Cc: johnstul@us.ibm.com, linux-kernel@vger.kernel.org Subject: Re: tg3 - irq #: nobody cared! From: "David S. Miller" In-Reply-To: <20030506220802.6d494326.akpm@digeo.com> References: <1052258580.4495.12.camel@w-jstultz2.beaverton.ibm.com> <1052283509.9817.1.camel@rth.ninka.net> <20030506220802.6d494326.akpm@digeo.com> X-FalunGong: Information control. X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 599 Lines: 17 From: Andrew Morton Date: Tue, 6 May 2003 22:08:02 -0700 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. That certainly what happens with tg3. Suggest we ignore these reports until that is sorted out. Ok. - 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/