From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Dillow Subject: Re: [PATCH 2.6.30-rc4] r8169: avoid losing MSI interrupts Date: Fri, 21 Aug 2009 18:59:27 -0400 Message-ID: <1250895567.23419.1.camel@obelisk.thedillows.org> References: <200903041828.49972.m.bueker@berlin.de> <1242001754.4093.12.camel@obelisk.thedillows.org> <200905112248.44868.mb@bu3sch.de> <200905112310.08534.mb@bu3sch.de> <1242077392.3716.15.camel@lap75545.ornl.gov> <4A09DC3E.2080807@googlemail.com> <1242268709.4979.7.camel@obelisk.thedillows.org> <4A0C6504.8000704@googlemail.com> <1242328457.32579.12.camel@lap75545.ornl.gov> <4A0C7443.1010000@googlemail.com> <1243042174.3580.23.camel@obelisk.thedillows.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Michael Riepe , Michael Buesch , Francois Romieu , Rui Santos , Michael =?ISO-8859-1?Q?B=FCker?= , linux-kernel@vger.kernel.org, netdev@vger.kernel.org To: "Eric W. Biederman" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, 2009-08-21 at 13:57 -0700, Eric W. Biederman wrote: > David Dillow writes: > I have what at first glance looks like a problem caused by this > patch. For the last month since upgrading one of my machines from > 2.6.28 to 2.6.30 it has been becomming inaccessible from the > network and I have a few: > > NETDEV WATCHDOG: eth0 (r8169): transmit timed out > > in my logs and a lot soft lockups that always have rtl8169_interrupt > as the thing that is running. I suspect your patch has introduced > a near infinite loop in the interrupt handler and is causing these > soft lockups. > > Any ideas? I would be surprised, but I suppose it is not out of the realm of possibility. Can you send me a full dmesg, please?