No problem, I'll get it to you soon. And, thanks!

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

On 10/12/2012 01:24 PM, Nithin Sujir wrote:
> Justin,
> I'm checking with the hardware team to see what info they need to diagnose. 
> In the meantime can you send me the output of
>
> 1. ethtool <iface>
> 2. Reg read of the following registers. You can do this by indirect access 
> for e.g. to read register 0x400. Everything is in hex so don't add a 0x to 
> any number.
>               setpci -s <pci bus>:<pci dev>.<pci fn> 78.l=400
>               setpci -s <pci bus>:<pci dev>.<pci fn> 80.l
>
>       Give me the readings for 0x400, 0x404, 0x408, 0x45c, 0x460, all from 
> 0x3600-0x3610, 0x362c, 0x3630.
>
> Can you do this for both when it links up in 100Mbit and when you force it to 
> 0x20 and it doesn't link up.
>
> Thanks,
> Nithin.
>
>
>
>> -----Original Message-----
>> From: Justin Chudgar [mailto:jus...@justinzane.com]
>> Sent: Thursday, October 11, 2012 11:38 PM
>> To: Nithin Sujir
>> Cc: 1063...@bugs.launchpad.net
>> Subject: Re: [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit
>> Speed using tg3 module.
>>
>> One thing I noticed is that my `ethtool -i eth0` output is different. I've
>> listed your values to the right where the seem to be significant.
>> I'm a little in the dark as to why my `firmware-version` string and `eeprom-
>> access` bool values are different and whether that has any import.
>>
>>     # ethtool -i eth0
>>     driver: tg3
>>>>  version: 3.123                << 3.121
>>>>  firmware-version: sb          << 57780-v3.15
>>     bus-info: 0000:01:00.0
>>     supports-statistics: yes
>>     supports-test: yes
>>>>  supports-eeprom-access: no          << yes
>>     supports-register-dump: yes
>>
>> Another interesting observation is that `ethtool -s eth0 advertise 0x020`
>> forcing autoneg to select 1000Mbps/Full kills the connection. Do
>> you have any suggestions as to how to debug the rate/duplex autonegotiation?
>> I'm unsure how to proceed to further diagnose this problem.
>>
>> [BTW, I just changed DNS servers and am still ironing out side effects. If
>> I've duplicated mail to you, I'm sorry.]
>>
>> Justin Chudgar  |  Weed, CA 96094  |  530 921 0738 |
>> http://www.justinzane.com/
>>
>> On 10/11/2012 04:23 PM, Nithin Sujir wrote:
>>
>>> Justin,
>>> Sorry, I'd already replied to netdev but found out later it didn't make it.
>> Resending what I sent netdev but did not reach there.
>>> Basically I'm not seeing a problem with the 57780 with either RedHat or
>> Ubuntu.
>>> So I'm not sure what it could be the problem in your case.
>>>
>>> Thanks,
>>> Nithin.
>>>
>>> --- Quote ---
>>> I don't see a problem linking up with 57780 at gigabit. I tested the latest
>> net kernel (3.6.0) and
>>> to make sure it's not ubuntu specific, tested ubuntu 12.04 as well
>> (3.2.0.23-generic). Everything
>>> works fine here on my setup. As you can see below, link is up at gigabit and
>> I'm able to send/receive.
>>>
>>>  > sudo ethtool -i eth7
>>> driver: tg3
>>> version: 3.121
>>> firmware-version: 57780-v3.15
>>> bus-info: 0000:43:00.0
>>> supports-statistics: yes
>>> supports-test: yes
>>> supports-eeprom-access: yes
>>> supports-register-dump: yes
>>>
>>>
>>>  > sudo ethtool eth7
>>>      Settings for eth7:
>>>      Supported ports: [ TP MII ]
>>>      Supported link modes: 10baseT/Half 10baseT/Full
>>>                            100baseT/Half 100baseT/Full
>>>                            1000baseT/Half 1000baseT/Full
>>>      Supported pause frame use: Symmetric Receive-only
>>>      Supports auto-negotiation: Yes
>>>      Advertised link modes: 10baseT/Half 10baseT/Full
>>>                             100baseT/Half 100baseT/Full
>>>                             1000baseT/Half 1000baseT/Full
>>>      Advertised pause frame use: Symmetric Receive-only
>>>      Advertised auto-negotiation: Yes
>>>      Speed: 1000Mb/s
>>>      Duplex: Full
>>>      Port: MII
>>>      PHYAD: 1
>>>      Transceiver: external
>>>      Auto-negotiation: on
>>>      Supports Wake-on: g
>>>      Wake-on: d
>>>      Current message level: 0x000000ff (255)
>>>      drv probe link timer ifdown ifup rx_err tx_err
>>>      Link detected: yes
>>>
>>>
>>>  > ifconfig eth7
>>> eth7 Link encap:Ethernet HWaddr 00:10:18:2a:18:cd
>>> inet addr:3.3.3.1 Bcast:3.3.3.255 Mask:255.255.255.0
>>> inet6 addr: fe80::210:18ff:fe2a:18cd/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:1224 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:1114 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:115500 (115.5 KB) TX bytes:146587 (146.5 KB)
>>> Interrupt:80
>>>
>>>  > ping 3.3.3.2 -c 1
>>> PING 3.3.3.2 (3.3.3.2) 56(84) bytes of data.
>>> 64 bytes from 3.3.3.2: icmp_req=1 ttl=64 time=0.185 ms
>>>
>>> --- 3.3.3.2 ping statistics ---
>>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>>> rtt min/avg/max/mdev = 0.185/0.185/0.185/0.000 ms
>>>
>>>
>>> Thanks,
>>> Nithin.
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Michael Chan
>>>> Sent: Thursday, October 11, 2012 4:16 PM
>>>> To: Justin Chudgar; Nithin Sujir
>>>> Cc: 1063...@bugs.launchpad.net
>>>> Subject: RE: [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit
>>>> Speed using tg3 module.
>>>>
>>>> We saw this post on netdev a few days ago.  Nithin, who is now working with
>> me
>>>> on the tg3 driver has looked into it.  I think he is having some email
>>>> problems and will reply to you soon.  Thanks.
>>>>
>>>> -----Original Message-----
>>>> From: Justin Chudgar [mailto:jus...@justinzane.com]
>>>> Sent: Thursday, October 11, 2012 3:47 PM
>>>> To: Matthew Carlson; Michael Chan
>>>> Cc: 1063...@bugs.launchpad.net
>>>> Subject: Fwd: [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit
>>>> Speed using tg3 module.
>>>>
>>>> Matt & Michael:
>>>>
>>>> I apologize if this is an inappropriate way to deal with a bug; please
>>>> instruct me if it is. I initially made the below-listed report to Ubuntu
>>>> and was directed upstream. I posted to the netdev list, but it seems to
>>>> have been buried there. I just want to make sure that whomever needs to
>>>> know does.
>>>>
>>>> Thanks.
>>>>
>>>> Justin Chudgar  |  Weed, CA 96094  |  530 921 0738 |
>>>> http://www.justinzane.com/
>>>>
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject:   Fwd: [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at
>>>> Gigabit Speed using tg3 module.
>>>> Date:      Wed, 10 Oct 2012 05:24:35 -0700
>>>> From:      Justin Chudgar <jus...@justinzane.com>
>>>> To:        net...@vger.kernel.org
>>>> CC:        1063...@bugs.launchpad.net
>>>>
>>>>
>>>>
>>>> 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.salisb...@canonical.com>
>>>> Reply-To:  Bug 1063038 <1063...@bugs.launchpad.net>
>>>> To:        jus...@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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/linux/+bug/1063038/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to