All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: ethtool -d MCAs rx2600
Date: Fri, 23 Jan 2004 23:12:54 +0000	[thread overview]
Message-ID: <20040123231254.GC31911@cup.hp.com> (raw)

Hi all.
This is just a warning: "Don't do this at home"
man ethtool says:

       -d     retrieves and prints a register dump for the specified
              ethernet device.

But it doesn't work so well on rx2600...I'll need to figure out why.
Or is it obvious to anyone?

This is with 2.6.1-rc1 on rx2600 talking to the built-in bcm5701.

hth,
grant

gsyprf3:~# ethtool eth1
Settings for eth1:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Current message level: 0x000000ff (255)
        Link detected: yes
gsyprf3:~# ethtool -d eth1
+CPU 1: SAL log contains MCA error record
+Err Record ID: 1    SAL Rev:  0.02
+Time: 01/23/2004 05:56:58    Severity 0

In case someone wants to dig more now, I've dropped the "errdump mca"
output on
	ftp://gsyprf10.external.hp.com/kernels/rx2600/mca_ethtool

(Matching vmlinuz, System.map, .config is also there 2.6.1-rc1.tgz)

thanks,
grant

             reply	other threads:[~2004-01-23 23:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 23:12 Grant Grundler [this message]
2004-01-23 23:56 ` ethtool -d MCAs rx2600 Grant Grundler
2004-01-26 16:30 ` Jack Steiner
2004-01-26 16:58 ` Matthew Wilcox
2004-01-26 17:39 ` Jeff Garzik
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=20040123231254.GC31911@cup.hp.com \
    --to=iod00d@hp.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.