All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Buckingham <peter@pantasys.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: netdev@oss.sgi.com, jgarzik@pobox.com
Subject: Re: Mystery packet killing tg3
Date: Thu, 05 May 2005 10:38:27 -0700	[thread overview]
Message-ID: <427A5A13.1080402@pantasys.com> (raw)
In-Reply-To: <427A58A0.3080309@hp.com>

Rick Jones wrote:
> IIRC the HP Itanium2 workstations (zx2000, zx6000) have a 32-bit Intel 
> (e1000) GbE on them.  I have an idea what the name of the chip was, but 
> will defer to any and all Intel types on the list :)

this is the one we're using. in the next generation of our system we'll 
definitely be using a 64bit part...

peter

0000:05:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit 
Ethernet Controller (rev 05)
         Subsystem: Giga-byte Technology: Unknown device 3000
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- 
ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 64 (63750ns min), cache line size 10
         Interrupt: pin A routed to IRQ 201
         Region 0: Memory at beda0000 (32-bit, non-prefetchable)
         Region 2: I/O ports at fc00 [size=64]
         Capabilities: [dc] Power Management version 2
                 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                 Status: D0 PME-Enable- DSel=0 DScale=1 PME-
         Capabilities: [e4] PCI-X non-bridge device.
                 Command: DPERE- ERO+ RBC=0 OST=0
                 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, 
DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-

  reply	other threads:[~2005-05-05 17:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 23:24 Mystery packet killing tg3 Stephen Hemminger
2005-05-03  3:02 ` David S. Miller
2005-05-03 21:05   ` Stephen Hemminger
2005-05-03 21:13     ` David S. Miller
2005-05-03 20:41       ` Michael Chan
2005-05-03 22:03         ` David S. Miller
2005-05-03 21:28           ` Michael Chan
2005-05-03 22:53             ` David S. Miller
2005-05-03 22:45           ` Stephen Hemminger
2005-05-03 22:39             ` David S. Miller
2005-05-03 22:59               ` Stephen Hemminger
2005-05-03 21:29       ` Stephen Hemminger
2005-05-04 18:30   ` Andi Kleen
2005-05-04 18:44     ` Peter Buckingham
2005-05-05 11:43       ` Andi Kleen
2005-05-05 16:20         ` Stephen Hemminger
2005-05-05 18:01           ` Andi Kleen
2005-05-05 17:09         ` Peter Buckingham
2005-05-05 17:32           ` Rick Jones
2005-05-05 17:38             ` Peter Buckingham [this message]
2005-05-05 17:45             ` John Heffner
2005-05-05 18:06           ` Andi Kleen
2005-05-05 18:21             ` Peter Buckingham
2005-05-05 18:31               ` Andi Kleen
2005-05-05 18:40                 ` Peter Buckingham
2005-05-05 18:56                   ` Andi Kleen
2005-05-05 19:02                     ` Peter Buckingham
2005-05-05 19:24                       ` Andi Kleen
2005-05-04 19:41     ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2005-05-04  6:09 Michael Chan
2005-05-04  6:27 Michael Chan
2005-05-04 22:51 ` Stephen Hemminger
2005-05-04 22:30   ` Michael Chan
     [not found]     ` <20050505113356.0f1b4c00.davem@davemloft.net>
2005-05-05 19:56       ` Michael Chan
2005-05-05 21:42         ` David S. Miller

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=427A5A13.1080402@pantasys.com \
    --to=peter@pantasys.com \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    --cc=rick.jones2@hp.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 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.