From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: pworach@mysun.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: eepro100 2.4.7-ac3 problems (apm related)
Date: Tue, 31 Jul 2001 14:37:24 +0200 [thread overview]
Message-ID: <3B66A684.A888F52D@TeraPort.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0107311246360.3857-100000@chaos.tp1.ruhr-uni-bochum.de>
Kai Germaschewski wrote:
>
>
> Martin, if you want to spend some work on your problem, you could try to
> collect some more data an your problem, particularly what about using
> another state (D1/D3) when the interface is down. D3 will probably mean
> that you have to save/restore PCI config space, so it's a bit more
> tedious. Also, is there anything which makes your card work again after it
> was in state D2? Like suspend/resume, or putting it into D3 and back into
> D0? Does a warm reboot suffice, or do you need to power cycle.
>
Hmm. I am kind of lost now. I just redid the tests I did with 2.4.6-ac2
under 2.4.7-ac3 and my eepro100 merrily survives any number of
D0->D2->D0 transitions. The only difference besides the kernels is the
ambient temperature. It is quite hot right now - and we don't have AC.
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
next prev parent reply other threads:[~2001-07-31 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 10:55 eepro100 2.4.7-ac3 problems (apm related) Kai Germaschewski
2001-07-31 11:12 ` Martin Knoblauch
2001-07-31 12:37 ` Martin Knoblauch [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-06 6:23 Pawel Worach
2001-08-04 1:15 Pawel Worach
2001-07-31 9:26 Martin Knoblauch
2001-07-30 22:43 Pawel Worach
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=3B66A684.A888F52D@TeraPort.de \
--to=martin.knoblauch@teraport.de \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pworach@mysun.com \
/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