From: JG <jg@cms.ac>
To: Lincoln Dale <ltd@cisco.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: TG3: very high CPU usage
Date: Mon, 9 Feb 2004 11:13:31 +0100 [thread overview]
Message-ID: <20040209101349.8AAFF1A9AD5@23.cms.ac> (raw)
In-Reply-To: <5.1.0.14.2.20040208105611.04710418@171.71.163.14>
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
hi,
> good to hear.
> what revision BCM5700 was it that you had?
>
> i've heard reports that the newer BCM5705s have 'issues' whereas
> BCM5700-5703 are good.
>
> can you post your 'lspci -vvv' output?
i'm sorry i can't tell the chip revision anymore (only card serial number) because i already RMA'ed the NIC.
i do have the same netgear card in another system where the serial number nearly identical (differs only by 1 digit), here's the lspci -vvv output:
00:09.0 Ethernet controller: Altima (nee Broadcom) AC9100 Gigabit Ethernet (rev 15)
Subsystem: Netgear: Unknown device 302a
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 (16000ns min), cache line size 08
Interrupt: pin A routed to IRQ 16
Region 0: Memory at cffe0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] 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- Capabilities: [48] 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: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
Address: fc879f41878ba220 Data: 3f06
JG
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-09 10:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 3:35 Mark Williams (MWP)
2004-01-20 12:33 ` JG
2004-01-20 23:13 ` Lincoln Dale
2004-01-21 3:19 ` Tom Sightler
2004-01-22 3:57 ` Lincoln Dale
2004-01-22 12:55 ` JG
2004-01-24 13:43 ` JG
2004-01-25 0:03 ` Lincoln Dale
2004-01-25 12:31 ` JG
2004-01-31 9:15 ` JG
2004-02-01 0:20 ` Lincoln Dale
2004-02-07 18:26 ` JG
2004-02-08 0:00 ` Lincoln Dale
2004-02-09 10:13 ` JG [this message]
2004-01-22 16:06 ` Tom Sightler
[not found] <fa.eu7l1gd.ekqe1j@ifi.uio.no>
2004-01-19 11:32 ` Andreas Hartmann
2004-01-20 3:54 ` Mark Williams (MWP)
[not found] <fa.g9joqss.1nneajs@ifi.uio.no>
[not found] ` <fa.e29fqcc.sick10@ifi.uio.no>
2004-01-20 9:17 ` Andreas Hartmann
2004-01-20 9:44 ` Lincoln Dale
2004-01-20 10:16 ` Mark Williams (MWP)
2004-01-20 12:09 ` Lincoln Dale
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=20040209101349.8AAFF1A9AD5@23.cms.ac \
--to=jg@cms.ac \
--cc=linux-kernel@vger.kernel.org \
--cc=ltd@cisco.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
Powered by JetHome