From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: forcedeth problems on 2.6.20-rc6-mm3 Date: Sun, 4 Feb 2007 22:17:41 -0800 Message-ID: <20070204221741.63152cbe.akpm@linux-foundation.org> References: <45C6BCE5.90103@shaw.ca> <20070204213603.a5bce839.akpm@linux-foundation.org> <45C6C531.20508@shaw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-kernel , netdev@vger.kernel.org, Ayaz Abdulla To: Robert Hancock Return-path: Received: from smtp.osdl.org ([65.172.181.24]:32926 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752732AbXBEGRn (ORCPT ); Mon, 5 Feb 2007 01:17:43 -0500 In-Reply-To: <45C6C531.20508@shaw.ca> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Sun, 04 Feb 2007 23:48:33 -0600 Robert Hancock wrote: > Andrew Morton wrote: > > On Sun, 04 Feb 2007 23:13:09 -0600 Robert Hancock wrote: > > > >> Something's busted with forcedeth in 2.6.20-rc6-mm3 for me relative to > >> 2.6.20-rc6. There's no errors in dmesg, but it seems no packets ever get > >> received and so the machine can't get an IP address. I tried reverting > >> all the -mm changes to drivers/net/forcedeth.c, which didn't help. The > >> network controller shares an IRQ with the USB OHCI controller which is > >> receiving interrupts, so it doesn't seem like an interrupt routing > >> problem, though I suppose something wierd could be happening there. > >> > >> This is on an Asus A8N-SLI Deluxe (CK804 chipset) on x86_64. > >> > >> Any suggestions on how to debug/what to try reverting to see what's > >> causing this? > > > > There are many forcedeth changes in git-netdev-all.patch. Can you > > try reverting drivers/net/forcedeth.c back to the unpatched version > > from 2.6.20-rc6? > > > > Thanks. > > > > That's essentially what I did, it didn't appear to help. I assume the > problem must lie elsewhere.. > doh, I missed that. It's presumably not the driver and nobody else seems to be hitting this, so it must be something peculiar to your setup. But I don't know what it might be, sorry.