Received: with ECARTIS (v1.0.0; list netdev); Wed, 23 Mar 2005 19:23:07 -0800 (PST) Received: from www.lanforge.com (ns1.lanforge.com [66.165.47.210]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id j2O3Mxl3003759 for ; Wed, 23 Mar 2005 19:22:59 -0800 Received: from [4.33.45.22] (evrtwa1-ar2-4-33-045-022.evrtwa1.dsl-verizon.net [4.33.45.22]) (authenticated bits=0) by www.lanforge.com (8.12.8/8.12.8) with ESMTP id j2O3ltLH004873; Wed, 23 Mar 2005 19:47:56 -0800 Message-ID: <42423292.60701@candelatech.com> Date: Wed, 23 Mar 2005 19:22:58 -0800 From: Ben Greear Organization: Candela Technologies User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20041020 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: "'netdev@oss.sgi.com'" , linux-kernel Subject: Re: PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard References: <42421FF2.7050501@candelatech.com> In-Reply-To: <42421FF2.7050501@candelatech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.83/781/Wed Mar 23 03:58:42 2005 on oss.sgi.com X-Virus-Status: Clean X-archive-position: 623 X-ecartis-version: Ecartis v1.0.0 Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com X-original-sender: greearb@candelatech.com Precedence: bulk X-list: netdev Content-Length: 1075 Lines: 29 Ben Greear wrote: > I'm having a strange problem. I have an X6DVA motherboard > with dual 2.8Ghz emt-64 processors, 1GB of RAM, SATA HD, etc. > I tried kernel 2.6.11 which uses irq 26, and 2.6.10-1.770_FC2smp, which > maps the irq to 209 or something like that. Distribution is FC2, x86. > Kernel is compiled for x86-SMP as well. > > I suspect that this may be a hardware issue of some sort, but if anyone > has any suggestions as to how to debug this further, please do let > me know. I'm attaching the lspci and dmesg output in case that helps. I am now less certain: I tried with a separate but similar machine, and eth3 still has bad interrupt test. I tried 2.6.9 kernel, same problem. I tried 2.4.29 kernel (on FC2 distribution), and the same problem exists. I tried with pci=noacpi, and this just messes up everything (irqs are disabled, etc). Could this be a bug in the motherboard implementation? Off to try some different combinations of NIC hardware... Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com