Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754862AbZAaSwZ (ORCPT ); Sat, 31 Jan 2009 13:52:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751880AbZAaSwN (ORCPT ); Sat, 31 Jan 2009 13:52:13 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:54113 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751508AbZAaSwM (ORCPT ); Sat, 31 Jan 2009 13:52:12 -0500 From: "Rafael J. Wysocki" To: Parag Warudkar Subject: Re: 2.6.29-rc3: tg3 dead after resume Date: Sat, 31 Jan 2009 19:51:28 +0100 User-Agent: KMail/1.10.3 (Linux/2.6.29-rc2-tst; KDE/4.1.3; x86_64; ; ) Cc: Linus Torvalds , Matt Carlson , "netdev@vger.kernel.org" , Linux Kernel Mailing List , "David S. Miller" , Andrew Morton References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901311951.29677.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1926 Lines: 43 On Saturday 31 January 2009, Parag Warudkar wrote: > > On Fri, 30 Jan 2009, Linus Torvalds wrote: > > > If you can try the patch I just sent out, and use that as a base for > > trying to track down why the heck the legacy code doesn't work, that would > > be great. It might fix it (assuming my guess about "restore_state while in > > PCI_D3 doesn't work" was correct), but quite frankly, it's equally > > possible that it just makes things worse. But it would be really > > interesting to hear.. > > Sure - will do. > > > > > Your machine does seem to be interesting, in that not only does it have a > > PCI-E bridge in it (the eeepc I was playing around with at LCA does not), > > but judging by the lost config state I also suspect that it actually loses > > power during STR. > > Not sure what the significance of eeepc is in this case - mine being a > standard Intel 5400 chipset I would have thought that's the last > place to look for interesting things! > > > Which is not at all necessarily a given - I suspect it depends on just how > > the power rails are set up on the motherboard. The fact that PCI-E bridges > > have apparently worked for others implies that your problems don't happen > > for everybody, and may relate to that issue. > > Do we know this for sure that PCI-E bridges + Suspend have worked for > others - In this thread at least I think people reported tg3 worked but not > necessarily with a PCI-E bridge. Technically, they are PCIe root ports and many systems have network adapters connected through them (I have two such systems here, but none of them with tg3-compatible hardware - my tg3 is a PCI device). Thanks, Rafael -- 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/