intel card one interface goes offline if forcing to 100/full
Victor Padro
vpadro at gmail.com
Wed Mar 11 01:15:28 UTC 2009
On Tue, Mar 10, 2009 at 3:23 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
> I noticed my intel card has two port connected to two different
> network through two different switches. I were able to force the eth2
> to 100/full using ethtool. However eth3 (the second interface)
> disables as shown in `Link detected:' when forcing it to 100/full
>
> default setup up
>
> root at host:~# ethtool eth3
> Settings for eth3:
> Supported ports: [ TP ]
> Supported link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Supports auto-negotiation: Yes
> Advertised link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Advertised auto-negotiation: Yes
> Speed: 100Mb/s
> Duplex: Half
> Port: Twisted Pair
> PHYAD: 1
> Transceiver: internal
> Auto-negotiation: on
> Supports Wake-on: d
> Wake-on: d
> Current message level: 0x00000001 (1)
> Link detected: yes
>
> changing it to 100/full from auto
>
> root at host:~# ethtool -s eth3 speed 100 duplex full autoneg off
>
> right away the link light goes off and the interface stops working.
>
> root at host:~# ethtool eth3
> Settings for eth3:
> Supported ports: [ TP ]
> Supported link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Supports auto-negotiation: Yes
> Advertised link modes: Not reported
> Advertised auto-negotiation: No
> Speed: Unknown! (65535)
> Duplex: Unknown! (255)
> Port: Twisted Pair
> PHYAD: 1
> Transceiver: internal
> Auto-negotiation: off
> Supports Wake-on: d
> Wake-on: d
> Current message level: 0x00000001 (1)
> Link detected: no
>
> to enable the link light back on and to make the interface operational
> I had to enable the auto negotiation
>
> root at host:~# ethtool -s eth3 autoneg on
>
>
> root at host:~# ethtool eth3
> Settings for eth3:
> Supported ports: [ TP ]
> Supported link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Supports auto-negotiation: Yes
> Advertised link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Advertised auto-negotiation: Yes
> Speed: 100Mb/s
> Duplex: Half
> Port: Twisted Pair
> PHYAD: 1
> Transceiver: internal
> Auto-negotiation: on
> Supports Wake-on: d
> Wake-on: d
> Current message level: 0x00000001 (1)
> Link detected: yes
>
>
> Any idea why it is behaving one second port but not on first port. It
> is a dual port card.
>
> Here is the relevant output from lspci -vvvv
>
> 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit
> Ethernet Controller (rev 06)
> Subsystem: Sun Microsystems Computer Corp. Device 125e
> 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: 32 bytes
> Interrupt: pin A routed to IRQ 2299
> Region 0: Memory at fd8e0000 (32-bit, non-prefetchable) [size=128K]
> Region 1: Memory at fd8c0000 (32-bit, non-prefetchable) [size=128K]
> Region 2: I/O ports at 6c00 [size=32]
> [virtual] Expansion ROM at fd700000 [disabled] [size=128K]
> Capabilities: [c8] 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: [d0] Message Signalled Interrupts: Mask- 64bit+
> Queue=0/0 Enable+
> Address: 00000000fee0300c Data: 41a9
> Capabilities: [e0] Express (v1) Endpoint, MSI 00
> DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s
> <512ns, L1 <64us
> 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 x4, ASPM L0s, Latency
> L0 <4us, L1 <64us
> ClockPM- Suprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
> CommClk-
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+
> DLActive-
> BWMgmt- ABWMgmt-
> Kernel driver in use: e1000e
> Kernel modules: e1000e
>
> 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit
> Ethernet Controller (rev 06)
> Subsystem: Sun Microsystems Computer Corp. Device 125e
> 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: 32 bytes
> Interrupt: pin B routed to IRQ 2298
> Region 0: Memory at fd8a0000 (32-bit, non-prefetchable) [size=128K]
> Region 1: Memory at fd880000 (32-bit, non-prefetchable) [size=128K]
> Region 2: I/O ports at 6800 [size=32]
> [virtual] Expansion ROM at fd720000 [disabled] [size=128K]
> Capabilities: [c8] 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: [d0] Message Signalled Interrupts: Mask- 64bit+
> Queue=0/0 Enable+
> Address: 00000000fee0300c Data: 41d9
> Capabilities: [e0] Express (v1) Endpoint, MSI 00
> DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s
> <512ns, L1 <64us
> 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 x4, ASPM L0s, Latency
> L0 <4us, L1 <64us
> ClockPM- Suprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
> CommClk-
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+
> DLActive-
> BWMgmt- ABWMgmt-
> Kernel driver in use: e1000e
> Kernel modules: e1000e
>
>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
Maybe silly questions, and bad english.
When you change to "ethtool -s eth3 speed 100 duplex full autoneg off" the
link just goes down forever? or is there any communication/activity between
the eth3 and the gateway, internet, whatever after 2 or more minutes?
if there isn't communication or even activity that's really odd...perhaps
you're using a switch which only supports autoneg and not a fixed speed and
duplex or maybe it's just misconfigured?
I have an init.d script on my debian server(etch) and on my PC ubuntu(hardy)
which runs everytime they boot up, and both NIC's leds(debian eth0 and eth1)
turns off and then get back on in a couple minutes max.
Ubuntu just does the same.
Mine are Intel Corporation 82540EM Gigabit Ethernet Controller and my switch
it's a managed 3com gigabit, configured for full duplex 1000Mbps.
--
"It is human nature to think wisely and act in an absurd fashion."
"Todo el desorden del mundo proviene de las profesiones mal o mediocremente
servidas"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20090310/d68f62ec/attachment.html>
More information about the ubuntu-users
mailing list