Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756726AbZA3X6O (ORCPT ); Fri, 30 Jan 2009 18:58:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752584AbZA3X5z (ORCPT ); Fri, 30 Jan 2009 18:57:55 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:47043 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753173AbZA3X5y (ORCPT ); Fri, 30 Jan 2009 18:57:54 -0500 Date: Fri, 30 Jan 2009 15:57:06 -0800 (PST) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Parag Warudkar cc: Matt Carlson , "netdev@vger.kernel.org" , Linux Kernel Mailing List , "David S. Miller" , Andrew Morton Subject: Re: 2.6.29-rc3: tg3 dead after resume In-Reply-To: Message-ID: References: <20090129184215.GA13459@xw6200.broadcom.net> <20090129222247.GA13861@xw6200.broadcom.net> <20090130184030.GA14933@xw6200.broadcom.net> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1961 Lines: 46 On Fri, 30 Jan 2009, Parag Warudkar wrote: > > Totally worth having this problem from a "getting an opportunity to > understand" standpoint. This confirms my long standing suspicion that bugs > in Linux kernel are merely a handiwork of few clever people to get more > people to understand and contribute :) Heh. I wish. But if that's the end result, we've done something good. > Any how here is the pre-suspend lspci -vvxxx output followed by diff -u - Bingo. > diff -u lspci-pre-suspend lspci-post-suspend > > --- lspci-pre-suspend 2009-01-30 18:19:50.752275695 -0500 > +++ lspci-post-suspend 2009-01-30 18:20:52.629779008 -0500 > > 00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09) > - Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ > + Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0, Cache Line Size: 64 bytes > Bus: primary=00, secondary=0e, subordinate=0e, sec-latency=0 We've disabled IO and MEM behind this bridge - the one that bridges to secondary bus 0x0e. And your tg3 device? It's at 0000:0e:00.0. Yeah. Exactly the bus that we've disabled IO and MEM for. In other words, it was never your tg3 suspend/resume that was buggy. It was the suspend/resume for the PCI-E port driver. In fact, I think it's _exactly_ the issue I just emailed out about. I bet Rafael can whip up a patch in a minute. I have too much of a headache right now to look at my screen for a while, so I'll take a break. Linus -- 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/