From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Martin Knoblauch <Martin.Knoblauch@TeraPort.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 08:23:15 -0400 [thread overview]
Message-ID: <3B4C4533.26A5B28A@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0107111413380.19006-100000@chaos.tp1.ruhr-uni-bochum.de>
Kai Germaschewski wrote:
>
> On Wed, 11 Jul 2001, Martin Knoblauch 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 :-)
>
> For the PCI things: Do a lspci -vvxxx at the various stages of working /
> not working and diff them. For the chip registers - well, I didn't look
> into this yet, but it'll be a bit harder, I suppose. (Maybe the maintainer
> has some hints?)
download eepro-diag.c from ftp://www.scyld.com/diag/
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
next prev parent reply other threads:[~2001-07-11 12:23 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
2001-07-11 12:15 ` Kai Germaschewski
2001-07-11 12:23 ` Jeff Garzik [this message]
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=3B4C4533.26A5B28A@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Martin.Knoblauch@TeraPort.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.