public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
	Patrick Mochel <mochel@transmeta.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	saw@saw.sw.com.sg
Subject: Re: 2.4.6.-ac2: Problems with eepro100
Date: Wed, 11 Jul 2001 13:01:37 +0200	[thread overview]
Message-ID: <3B4C3211.79A07C5A@TeraPort.de> (raw)
In-Reply-To: <Pine.LNX.3.96.1010709163526.15260A-100000@mandrakesoft.mandrakesoft.com>

Jeff Garzik wrote:
> 
> On Mon, 9 Jul 2001, Kai Germaschewski wrote:
> 
> > On Mon, 9 Jul 2001, Patrick Mochel wrote:
> >
> 
> 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.

 Instructions on how to do the dumps? Sorry, I have not been that deep
into these matters until now :-)

 Just as an experiment, I modified the 246-ac2 eepro100.c driver to
never set the devive into D2 mode. As a result, I can now ifconfig
down/up as much as I want without killing the network. So I guess it is
really PM related.

*** eepro100.c-ac2      Mon Jul  9 12:30:53 2001
--- eepro100.c  Wed Jul 11 12:47:07 2001
***************
*** 780,782 ****
        /* Put chip into power state D2 until we open() it. */
!       pci_set_power_state(pdev, 2);
 
--- 780,782 ----
        /* Put chip into power state D2 until we open() it. */
!       pci_set_power_state(pdev, 0); /*MKN*/
 
***************
*** 1835,1837 ****
 
!       pci_set_power_state(sp->pdev, 2);
 
--- 1835,1837 ----
 
!       pci_set_power_state(sp->pdev, 0); /* MKN */


Martin
-- 
------------------------------------------------------------------
Martin Knoblauch         |    email:  Martin.Knoblauch@TeraPort.de
TeraPort GmbH            |    Phone:  +49-89-510857-309
C+ITS                    |    Fax:    +49-89-510857-111
http://www.teraport.de   |    Mobile: +49-170-4904759

  reply	other threads:[~2001-07-11 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09 10:14 2.4.6.-ac2: Problems with eepro100 Martin Knoblauch
2001-07-09 10:45 ` Martin Knoblauch
2001-07-09 16:18   ` Patrick Mochel
2001-07-09 21:12     ` Kai Germaschewski
2001-07-09 21:36       ` Jeff Garzik
2001-07-11 11:01         ` Martin Knoblauch [this message]
2001-07-11 12:15           ` Kai Germaschewski
2001-07-11 12:23             ` Jeff Garzik
2001-07-11 13:01             ` Martin Knoblauch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B4C3211.79A07C5A@TeraPort.de \
    --to=martin.knoblauch@teraport.de \
    --cc=jgarzik@mandrakesoft.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@transmeta.com \
    --cc=saw@saw.sw.com.sg \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox