Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 9 Jul 2001 17:40:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 9 Jul 2001 17:40:02 -0400 Received: from mandrakesoft.mandrakesoft.com ([216.71.84.35]:32122 "EHLO mandrakesoft.mandrakesoft.com") by vger.kernel.org with ESMTP id ; Mon, 9 Jul 2001 17:39:51 -0400 Date: Mon, 9 Jul 2001 16:36:27 -0500 (CDT) From: Jeff Garzik To: Kai Germaschewski cc: Patrick Mochel , Martin Knoblauch , "linux-kernel@vger.kernel.org" , saw@saw.sw.com.sg Subject: Re: 2.4.6.-ac2: Problems with eepro100 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 9 Jul 2001, Kai Germaschewski wrote: > On Mon, 9 Jul 2001, Patrick Mochel wrote: > > > Can you do an 'lspci -vv' on the device? The current device state should > > be listed 2 lines after the Power Management Capabilities revision. > > I already talked to Martin off list about this problem (since it's my > patch which is causing trouble). > > To summarize the results: His eepro100 does only survive one > D0-D2-D0 transition, after another D2 transition it's possible to place it > back in D0, but it won't work. > > It comes up in D0, eepro100 module load will place it in D2, first > ifconfig up will switch to D0, works. Another ifconfig down / up cycle > will kill the network (same happens with the unpatched version). > > If someone feels able to find out what's really happening, that'd be great > of course. To the question of what to do about this, the only thing I can > think of is adding a parameter/config option for eepro100 to supply the > power state when inactive (default would be D2, for Martin D0 will work). > > Better ideas anyone? Do a register dump of working and dead-after-PM-transition, including PCI config registers, and look for differences. Also look for differences in your host and PCI-PCI bridge PCI config registers. - 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/