netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Chudgar <justin@justinzane.com>
To: netdev@vger.kernel.org
Cc: 1063038@bugs.launchpad.net
Subject: Fwd: [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.
Date: Wed, 10 Oct 2012 05:24:35 -0700	[thread overview]
Message-ID: <50756903.1030709@justinzane.com> (raw)
In-Reply-To: <20121009143846.2196.28573.malone@chaenomeles.canonical.com>

[-- Attachment #1: Type: text/plain, Size: 7343 bytes --]

I've got a device with a Broadcom 57780 ethernet NIC. It uses the tg3.ko
driver module. The problem is that this NIC cannot connect at gigabit
(1000MBps) speed. In all cases connection works well at 100MBps. I
reported this to Ubuntu as noted below and was directed here.
[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063038] Following
are the tests I've completed:

- Cables tested with cable tester
- Cables tested to work at gigabit speed with Realtek and Intel gigabit
NICs.
- All unmanaged switch ports tested at gigabit speed with other NICs.
- Tried to connect with NetworkManager enabled and disabled.
- Tried both dhcp and static connections.
- Tried to renegotiate connection with `ethtool -r` both with TSO
enabled and disabled.
- Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic
3.6.0-999-generic kernels from main, xorg-edgers and mainline repos.
- Used 'tg3_debug=1' kernel option in grub with the following output:

    [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
    [ 0.000000] Kernel command line:
BOOT_IMAGE=/vmlinuz-3.5.0-17-generic
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
    [ 5.963136] tg3.c:v3.123 (March 21, 2012)
    [ 5.995781] tg3 mdio bus: probed
    [ 6.005583] tg3 0000:01:00.0: >eth0: Tigon3 [partno(BCM57780) rev
57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5
    [ 6.005687] tg3 0000:01:00.0: >eth0: attached PHY driver [Broadcom
BCM57780] (mii_bus:phy_addr=100:01)
    [ 6.005790] tg3 0000:01:00.0: >eth0: RXcsums[1] LinkChgREG[0]
MIirq[0] ASF[0] TSOcap[1]
    [ 6.005887] tg3 0000:01:00.0: >eth0: dma_rwctrl[76180000]
dma_mask[64-bit]
    [ 294.987653] tg3 0000:01:00.0: >irq 44 for MSI/MSI-X
    [ 295.893224] tg3 0000:01:00.0: >eth0: Link is down
    [ 309.887879] tg3 0000:01:00.0: >eth0: Link is up at 100 Mbps, full
duplex
    [ 309.887886] tg3 0000:01:00.0: >eth0: Flow control is on for TX and
on for RX

Other distros' forums suggest loading broadcom.ko first; however, this
module is no present. Any suggestions would be much appreciated.

lspci -vv:
    01:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780
Gigabit Ethernet PCIe (rev 01)
        Subsystem: Acer Incorporated [ALI] Device 0601
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 44
        Region 0: Memory at d3400000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [48] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)

                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [60] Vendor Specific Information: Len=6c <?>
        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee0100c Data: 4189
        Capabilities: [cc] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<4us, L1 unlimited
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend+
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <1us, L1 <32us
                        ClockPM+ Surprise- LLActRep- BwNot-
                LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled-
Retrain- CommClk+
                        ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range ABCD, TimeoutDis+
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
SpeedDis-, Selectable De-emphasis: -6dB
                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB
        Capabilities: [100 v1] Advanced Error Reporting
                UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt-
UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout-
NonFatalErr-
                CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+
ChkEn-
        Capabilities: [13c v1] Virtual Channel
                Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb: Fixed- WRR32- WRR64- WRR128-
                Ctrl: ArbSelect=Fixed
                Status: InProgress-
                VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
                        Status: NegoPending- InProgress-
        Capabilities: [160 v1] Device Serial Number dc-0e-a1-ff-fe-ac-38-d5
        Capabilities: [16c v1] Power Budgeting <?>
        Kernel driver in use: tg3
        Kernel modules: tg3
---


Justin Chudgar  |  Weed, CA 96094  |  530 921 0738 | http://www.justinzane.com/

-------- Original Message --------
Subject: 	[Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit
Speed using tg3 module.
Date: 	Tue, 09 Oct 2012 14:38:45 -0000
From: 	Joseph Salisbury <joseph.salisbury@canonical.com>
Reply-To: 	Bug 1063038 <1063038@bugs.launchpad.net>
To: 	justin@justinzane.com



This issue appears to be an upstream bug, since you tested the latest
upstream kernel.  Would it be possible for you to open an upstream bug
report[0]?  That will allow the upstream Developers to examine the
issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0].  The first step is
to email the appropriate mailing list.  If no response is received, then
a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel


** Changed in: linux (Ubuntu)
       Status: Confirmed => Triaged

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1063038

Title:
  Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063038/+subscriptions





[-- Attachment #2: justin.vcf --]
[-- Type: text/x-vcard, Size: 150 bytes --]

begin:vcard
fn:Justin Chudgar
n:Chudgar;Justin
email;internet:justin@justinzane.com
tel;cell:530-921-0738
x-mozilla-html:FALSE
version:2.1
end:vcard


       reply	other threads:[~2012-10-10 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121009143846.2196.28573.malone@chaenomeles.canonical.com>
2012-10-10 12:24 ` Justin Chudgar [this message]
2012-10-11 20:25   ` Fwd: [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module Nithin Nayak Sujir
     [not found]   ` <50774C61.9050207@justinzane.com>
     [not found]     ` <0E685F8B314BFB42AE2422915B7BDCC30FDCEF86@IRVEXCHMB07.corp.ad.broadcom.com>
     [not found]       ` <DAAFBCC105999F468732FA900576CB450FFA61A5@IRVEXCHMB08.corp.ad.broadcom.com>
     [not found]         ` <5077BAAA.3070208@justinzane.com>
     [not found]           ` <DAAFBCC105999F468732FA900576CB450FFAB4AF@IRVEXCHMB08.corp.ad.broadcom.com>
     [not found]             ` <5078B151.9000607@justinzane.com>
     [not found]               ` <5078B1EF.6090401@broadcom.com>
     [not found]                 ` <5078E7B8.20903@justinzane.com>
     [not found]                   ` <DAAFBCC105999F468732FA900576CB450FFBB033@IRVEXCHMB08.corp.ad.broadcom.com>
2012-10-16  3:43                     ` Justin Chudgar
2012-10-16 13:52                       ` Nithin Sujir
2012-10-16 15:29                         ` Michael Chan
2012-10-16 23:08                         ` Justin Chudgar
2012-10-17  2:17                           ` Michael Chan

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=50756903.1030709@justinzane.com \
    --to=justin@justinzane.com \
    --cc=1063038@bugs.launchpad.net \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).