Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757747AbZA3Xda (ORCPT ); Fri, 30 Jan 2009 18:33:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754870AbZA3XdS (ORCPT ); Fri, 30 Jan 2009 18:33:18 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:41170 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753457AbZA3XdR (ORCPT ); Fri, 30 Jan 2009 18:33:17 -0500 Date: Fri, 30 Jan 2009 15:33:13 -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: 757 Lines: 19 On Fri, 30 Jan 2009, Linus Torvalds wrote: > > So just do that "lspci -vvxxx" for the whole box, before and after, and > send us the "before" and the "diff -u before after" thing, and maybe that > shows something interesting. Because some bridge chip being confused would > also explain why a total re-init of the whole tg3 chip by a driver unload > and reload doesn't seem to help. It might also be instructive to see the same thing for a working kernel. I assume plain 2.6.28 works for you? 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/