From: Jan-Patrick P. <pe...@ae...> - 2006-07-27 18:11:55
|
on the host: ethtool eth1 Settings for eth1: Supported ports: [ FIBRE ] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) Link detected: yes one strange thing is that Support Wake-on is :d=20 in that port but is :umbg on the other one of the=20 same board (connected to a fast iron with no problems). on the switch: #module 1 : 2-port 1000BaseSX Supervisor set trunk 1/1 auto isl 1-1005 set trunk 1/2 auto isl 1-1005 5505_1> (enable) sh port 1/1 Port Name Status Vlan Level Duplex Speed Type ----- ------------------ ---------- ---------- ------ ------ ----- --------= ---- 1/1 connected 1 normal full 1000 1000Bas= eSX Port Trap IfIndex ----- -------- ------- 1/1 disabled 107 Port Broadcast-Limit Broadcast-Drop -------- --------------- -------------- 1/1 - 0 Port Send FlowControl Receive FlowControl RxPause TxPause Unsupported admin oper admin oper opcodes ----- -------- -------- -------- -------- ------- ------- ----------- 1/1 desired on off off 0 0 0 Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize ----- ---------- ---------- ---------- ---------- --------- 1/1 0 0 0 0 0 Port Single-Col Multi-Coll Late-Coll Excess-Col Carri-Sen Runts Giants ----- ---------- ---------- ---------- ---------- --------- --------- -----= ---- 1/1 0 0 0=20 0 0 0 0 So far, no problem reported on the switch. I think half duplex isn't supported on Fiber connections. Is it? At 02:37 PM 7/27/2006, Ronciak, John wrote: >The errors look like you are runnign half duplex=20 >on the connection. All of those type of erros=20 >happen when the connection is on a shared LAN=20 >segment. Is the connection configured=20 >correctly? Both sides (switch and host port)=20 >either set to autoneg or both being forced? If=20 >forcing, is it being set to full duplex? What=20 >does the switch report in it's stats? > >Cheers, >John >----------------------------------------------------------- >"Those who would give up essential Liberty, to=20 >purchase a little temporary Safety, deserve=20 >neither Liberty nor Safety.", Benjamin Franklin 1755 > > > > -----Original Message----- > > From: e10...@li... > > [mailto:e10...@li...] On Behalf > > Of Jan-Patrick Perisse > > Sent: Wednesday, July 26, 2006 11:04 AM > > To: e10...@li... > > Subject: [E1000-devel] RX lockup problem > > > > > > I managed to update my RH ES 3.0 kernel to 2.6.17.6 (vanilla) kernel. > > e1000 driver is now: > > driver: e1000 > > version: 7.0.33-k2-NAPI > > firmware-version: N/A > > bus-info: 0000:03:08.0 > > > > Just to remember, I was having machine lockups when connecting: > > 03:08.0 Ethernet controller: Intel Corporation > > 82546EB Gigabit Ethernet Controller (Fiber) (rev 01) > > 03:08.1 Ethernet controller: Intel Corporation > > 82546EB Gigabit Ethernet Controller (Fiber) (rev 01) > > to a CISCO CATALIST 5505 gigabit controller. > > > > When I first recompiled the kernel, I left the > > dual onboard gigabit controller (also e1000) > > enabled. With this configuration, the machine > > still locked up after some minutes. > > Now I disabled it and It is online for 12 hours. > > I still have plenty of errors on the connection to the CISCO: > > ethtool -S eth1|grep errors > > rx_errors: 404434 > > tx_errors: 0 > > rx_length_errors: 101778 > > rx_over_errors: 0 > > rx_crc_errors: 276478 > > rx_frame_errors: 0 > > rx_missed_errors: 82 > > tx_aborted_errors: 0 > > tx_carrier_errors: 0 > > tx_fifo_errors: 0 > > tx_heartbeat_errors: 0 > > tx_window_errors: 0 > > rx_long_length_errors: 24 > > rx_short_length_errors: 101754 > > rx_align_errors: 0 > > rx_csum_offload_errors: 12700 > > I tried changing the supervisor on the cisco, but it didn't help. > > I noticed that when testing the connection, I > > have no errors at all. I tried testing by pinging > > -f the cisco itself. No errors. When I load all > > the other ports of the cisco and the traffic goes > > up to about 5000 packets per second, I have those errors above. > > Is it possible that the traffic is causing the cisco or the > > NIC driver to fail? > > > > Thanks again. > > > > > > > > Jan-Patrick P=E9riss=E9 > > AEON TECHNOLOGIES > > (21) 2705-3139 / 2705-3028 > > http://www.aeontech.com.br > > > > > > > > > > > > -- > > Esta mensagem foi verificada pelo sistema de antiv=EDrus e > > acredita-se estar livre de perigo. > > > > > > -------------------------------------------------------------- > > ----------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the > > chance to share your > > opinions on IT & business topics through brief surveys -- and > > earn cash > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge >&CID=3DDEVDEV >_______________________________________________ >E1000-devel mailing list >E10...@li... >https://lists.sourceforge.net/lists/listinfo/e1000-devel > >-- >Esta mensagem foi verificada pelo sistema de antiv=EDrus e > acredita-se estar livre de perigo. Jan-Patrick P=E9riss=E9 AEON TECHNOLOGIES (21) 2705-3139 / 2705-3028 http://www.aeontech.com.br --=20 Esta mensagem foi verificada pelo sistema de antiv=EDrus e acredita-se estar livre de perigo. |