From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759493AbZEKWBQ (ORCPT ); Mon, 11 May 2009 18:01:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756340AbZEKWAz (ORCPT ); Mon, 11 May 2009 18:00:55 -0400 Received: from bu3sch.de ([62.75.166.246]:55293 "EHLO vs166246.vserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756226AbZEKWAz (ORCPT ); Mon, 11 May 2009 18:00:55 -0400 From: Michael Buesch To: David Dillow Subject: Re: 2.6.27.19 + 28.7: network timeouts for r8169 and 8139too Date: Mon, 11 May 2009 23:59:43 +0200 User-Agent: KMail/1.9.9 Cc: Michael Riepe , Francois Romieu , Rui Santos , Michael =?utf-8?q?B=C3=BCker?= , linux-kernel@vger.kernel.org, netdev@vger.kernel.org References: <200903041828.49972.m.bueker@berlin.de> <200905112310.08534.mb@bu3sch.de> <1242077392.3716.15.camel@lap75545.ornl.gov> In-Reply-To: <1242077392.3716.15.camel@lap75545.ornl.gov> X-Move-Along: Nothing to see here. No, really... Nothing. MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905112359.43433.mb@bu3sch.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 11 May 2009 23:29:52 David Dillow wrote: > On Mon, 2009-05-11 at 23:10 +0200, Michael Buesch wrote: > > On Monday 11 May 2009 22:48:44 Michael Buesch wrote: > > > On Monday 11 May 2009 02:29:14 David Dillow wrote: > > > > > Kernel: 2.6.29.2 (x86_64) > > > > > Board: Intel D945GCLF2 > > > > > BIOS version: LF94510J.86A.0099.2008.0731.0303 > > > > > > > > I'm not sure this is tied to the chip. > > > > > > Yeah maybe other chips are affected as well. > > > I just want to note that my failing chip/board is an Intel D945GCLF2 board > > > with onboard G-LAN, too. > > > > > > The device XID is: XID 3c4000c0 > > > (see kernel log) > > > > > > Somebody else (I think it was Rui Santos) already reported a failing chip with that XID, too. > > > > > > > Here's a patch which blacklists MSI support by XID. > > It's currently only compile-tested, because I can't reboot the machine right now. > > I was saying that I don't think the timeouts are necessarily the NIC > chipset -- or the bridge chip for that matter -- having issues with > MSI. There were some substantial IRQ handling changes in 2.6.28 and my > bisection of the problem seem to lead into that code. I'll try this > later tonight hopefully, but can you try to run 2.6.27 with the current > r8169 driver and see if it is solid for you? That way it is using the > same driver code, but avoids the IRQ changes. > > Of course, my XID is 281000c0, so it looks like I have a different NIC > chip as well, so we may be chasing different problems. Still, it'd be > nice to rule out the IRQ changes before adding a blacklist. Ok, that perfectly makes sense. I can try 2.6.29's driver on 2.6.27, but I can't tell when, because I currently only have infrequent physical access to the machine. -- Greetings, Michael.