All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ethtool -d MCAs rx2600
Date: Mon, 26 Jan 2004 17:39:42 +0000	[thread overview]
Message-ID: <401550DE.90906@pobox.com> (raw)
In-Reply-To: <20040123231254.GC31911@cup.hp.com>

Matthew Wilcox wrote:
> On Mon, Jan 26, 2004 at 10:30:23AM -0600, Jack Steiner wrote:
>>Looks like it occurs here (but I dont put a lot of faith in this):
>>        GET_REG32_LOOP(BUFMGR_MODE, 0x58);
>>        GET_REG32_LOOP(RDMAC_MODE, 0x08);
>>   >>>> GET_REG32_LOOP(WDMAC_MODE, 0x08);
>>        GET_REG32_LOOP(RX_CPU_BASE, 0x280);
>>        GET_REG32_LOOP(TX_CPU_BASE, 0x280);
> 
> 
> My suspicion is that some tg3 variants don't support this register, but
> it's OK to read the register on x86 because it soft-fails.  Most ia64
> chipsets hard-fail so we need to avoid this.  Jeff, Dave, can you comment?


I get lockups occasionally on x86 too, but have had higher priority 
things to look at.  Since regdump is mainly an engineer's tool, we felt 
it was a "use at your own risk" feature.

But if we can fix it, all the better.

Tangent -- I would love for somebody to take this output and prettyprint 
it in userland ethtool package (d/l and cvs at 
http://sf.net/projects/gkernel/).

	Jeff




  parent reply	other threads:[~2004-01-26 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 23:12 ethtool -d MCAs rx2600 Grant Grundler
2004-01-23 23:56 ` Grant Grundler
2004-01-26 16:30 ` Jack Steiner
2004-01-26 16:58 ` Matthew Wilcox
2004-01-26 17:39 ` Jeff Garzik [this message]
2004-01-29 19:18 ` Grant Grundler
2004-01-29 20:41 ` Jack Steiner

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=401550DE.90906@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ia64@vger.kernel.org \
    /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.