Hello, in f11 I had a line into /etc/rc.d/rc.local to force speed/duplex/autoneg: /sbin/ethtool -s eth0 speed 100 duplex full autoneg off >> /tmp/ethtool.log 2>&1
In F12 I see that this setting is not maintained. After I log in in Gnome I see that: [root@tekkaman ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Half Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes
The log file has timestamp of my boot time, so that I know it was actually executed. If I run it manually it succeeds and I get now: Advertised link modes: Not reported Advertised auto-negotiation: No Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: off Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes
but after some minutes I get again: Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Half Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes
So there is something external that manage this kind of changes. Some questions: - network guys say me that switch port is fixed at 100/full (it is a gigabit ethernet) so, if this is true, even in autoneg there is an error in getting settings - what is the component that changes the settings? I walked through NM applet to edit connections but I don't see any parameter....
Hw is a Dell laptop XPX M1330 with updated F12 x86_64 lspci for network card gives: 09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02) Subsystem: Dell XPS M1330 Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f1bf0000 (64-bit, non-prefetchable) [size=64K] Expansion ROM at <ignored> [disabled] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] Vendor Specific Information <?> Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel <?> Capabilities: [160] Device Serial Number 00-1d-09-ff-fe-3d-82-50 Kernel driver in use: tg3 Kernel modules: tg3
Strange thing is that after booting the laptop less that 4 hours ago, with dmesg I get these messages: tg3.c:v3.99 (April 20, 2009) tg3 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 tg3 0000:09:00.0: setting latency timer to 64 tg3 0000:09:00.0: PME# disabled eth0: Tigon3 [partno(BCM95906) rev c002] (PCI Express) MAC address 00:1d:09:3d:82:50 eth0: attached PHY is 5906 (10/100Base-TX Ethernet) (WireSpeed[0]) eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[0] eth0: dma_rwctrl[76180000] dma_mask[64-bit] ... tg3 0000:09:00.0: PME# disabled alloc irq_desc for 31 on node 0 alloc kstat_irqs on node 0 tg3 0000:09:00.0: irq 31 for MSI/MSI-X ADDRCONF(NETDEV_UP): eth0: link is not ready Bridge firewalling registered virbr0: starting userspace STP failed, starting kernel STP tg3: eth0: Link is up at 100 Mbps, full duplex. --------------------------->>>> this I think is about my rc.local command tg3: eth0: Flow control is off for TX and off for RX. ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready lo: Disabled Privacy Extensions type=1305 audit(1264148879.894:25902): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=kernel res=1 eth0: no IPv6 routers present tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, full duplex. tg3: eth0: Flow control is off for TX and off for RX. ... tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. CE: hpet increasing min_delta_ns to 22500 nsec tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX.
So I have many link down messages and (apparently) renegotiation tthat then gives 100/half Any suggestions??? BTW I have libvirtd started but no vm created Thanks in advance, Gianluca
On 01/22/2010 04:08 AM, Gianluca Cecchi wrote:
Hello, in f11 I had a line into /etc/rc.d/rc.local to force speed/duplex/autoneg: /sbin/ethtool -s eth0 speed 100 duplex full autoneg off>> /tmp/ethtool.log 2>&1
In F12 I see that this setting is not maintained. After I log in in Gnome I see that: [root@tekkaman ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Half Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes
The log file has timestamp of my boot time, so that I know it was actually executed. If I run it manually it succeeds and I get now: Advertised link modes: Not reported Advertised auto-negotiation: No Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: off Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes
but after some minutes I get again: Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Half Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes
So there is something external that manage this kind of changes.
It's NetworkManager doing that to you.
Some questions:
- network guys say me that switch port is fixed at 100/full (it is a
gigabit ethernet) so, if this is true, even in autoneg there is an error in getting settings
Is there a reason they've set that up as fixed? Is there an autoneg issue with the switch (some don't do autonegotiation correctly).
- what is the component that changes the settings? I walked through NM
applet to edit connections but I don't see any parameter....
Yet another issue with NM. It doesn't give you the ability to run any special "ethtool" stuff.
Hw is a Dell laptop XPX M1330 with updated F12 x86_64 lspci for network card gives: 09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02) Subsystem: Dell XPS M1330 Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f1bf0000 (64-bit, non-prefetchable) [size=64K] Expansion ROM at<ignored> [disabled] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] Vendor Specific Information<?> Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel<?> Capabilities: [160] Device Serial Number 00-1d-09-ff-fe-3d-82-50 Kernel driver in use: tg3 Kernel modules: tg3
Strange thing is that after booting the laptop less that 4 hours ago, with dmesg I get these messages: tg3.c:v3.99 (April 20, 2009) tg3 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 tg3 0000:09:00.0: setting latency timer to 64 tg3 0000:09:00.0: PME# disabled eth0: Tigon3 [partno(BCM95906) rev c002] (PCI Express) MAC address 00:1d:09:3d:82:50 eth0: attached PHY is 5906 (10/100Base-TX Ethernet) (WireSpeed[0]) eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[0] eth0: dma_rwctrl[76180000] dma_mask[64-bit] ... tg3 0000:09:00.0: PME# disabled alloc irq_desc for 31 on node 0 alloc kstat_irqs on node 0 tg3 0000:09:00.0: irq 31 for MSI/MSI-X ADDRCONF(NETDEV_UP): eth0: link is not ready Bridge firewalling registered virbr0: starting userspace STP failed, starting kernel STP tg3: eth0: Link is up at 100 Mbps, full duplex. --------------------------->>>> this I think is about my rc.local command tg3: eth0: Flow control is off for TX and off for RX. ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready lo: Disabled Privacy Extensions type=1305 audit(1264148879.894:25902): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=kernel res=1 eth0: no IPv6 routers present tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, full duplex. tg3: eth0: Flow control is off for TX and off for RX. ... tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. CE: hpet increasing min_delta_ns to 22500 nsec tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX. tg3: eth0: Link is down. tg3: eth0: Link is up at 100 Mbps, half duplex. tg3: eth0: Flow control is off for TX and off for RX.
So I have many link down messages and (apparently) renegotiation tthat then gives 100/half Any suggestions???
This is a wild-assed guess, but you could try editing the "/etc/sysconfig/network-scripts/network-functions" file. Find the "check_ethtool()" function (around line 256 or so). Add a line (marked by "ADD--->") as shown below:
check_ethtool () { [ -x /sbin/ethtool ] || return 2 ADD---> LC_ALL=C ethtool -s $1 speed 100 duplex full autoneg off output=$(LC_ALL=C ethtool $1 2>&1) echo $output | LC_ALL=C grep -q "Link detected: yes" && return 1 echo $output | LC_ALL=C grep -q "Link detected: no" && return 0 || return 2 }
It's a butt-ugly hack, but may serve your purpose.
BTW I have libvirtd started but no vm created Thanks in advance, Gianluca
---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Better to understand a little than to misunderstand a lot. - ----------------------------------------------------------------------
On Fri Jan 22 17:48:03 UTC 2010 Rick Stevens wrote:
It's NetworkManager doing that to you.
Ok, as I supposed.
Is there a reason they've set that up as fixed? Is there an autoneg issue with the switch (some don't do autonegotiation correctly).
There was a problem on older gigabit switches and for historical reasons was set up this way yet. Now they are on new ones and I asked them to put the switch port to autoneg. OK now for the speed part. I get 100/full after autoneg at boot.
But when I start for example an scp session of big files (around some tenths of megabytes) from/to my pc, I get many link down messages..... The transfer begins at 9.7MB/s and then continuously decreases at about 7 and also 5 MB/s.....
See below my /var/log/messages after reboot at about 09.30 this morning. For example at 10:23 and 11:05 I started scp sessions (single file of about 2.5Gb) Jan 26 09:34:54 tekkaman kernel: tg3: eth0: Link is down. Jan 26 09:34:54 tekkaman NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 09:34:55 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 09:34:55 tekkaman NetworkManager: <info> (eth0): carrier now ON (device state 8) Jan 26 09:34:55 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Jan 26 09:38:56 tekkaman ntpd[1264]: synchronized to 10.4.1.46, stratum 3 Jan 26 09:38:56 tekkaman ntpd[1264]: time reset +0.391977 s Jan 26 09:38:56 tekkaman ntpd[1264]: kernel time sync status change 2001 Jan 26 09:39:10 tekkaman dnsmasq[1451]: reading /etc/resolv.conf Jan 26 09:39:10 tekkaman dnsmasq[1451]: using nameserver 10.4.1.121#53 Jan 26 09:39:10 tekkaman dnsmasq[1451]: using nameserver 10.4.1.120#53 Jan 26 09:46:05 tekkaman ntpd[1264]: synchronized to 10.4.1.46, stratum 3 Jan 26 09:51:02 tekkaman NetworkManager: <info> (wlan0): device state change: 3 -> 2 (reason 0) Jan 26 09:51:02 tekkaman NetworkManager: <info> (wlan0): deactivating device (reason: 0). Jan 26 09:51:02 tekkaman NetworkManager: <info> Policy set 'Poli' (eth0) as default for routing and DNS. Jan 26 09:51:02 tekkaman NetworkManager: <info> (wlan0): taking down device. Jan 26 09:51:02 tekkaman dbus-daemon: Rejected send message, 2 matched rules; type="method_return", sender=":1.9" (uid=0 pid=1226 comm="NetworkManager) interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.45" (uid=500 pid=1773 comm="nm-applet)) Jan 26 10:08:18 tekkaman dnsmasq[1451]: reading /etc/resolv.conf Jan 26 10:08:18 tekkaman dnsmasq[1451]: using nameserver 10.4.1.121#53 Jan 26 10:08:18 tekkaman dnsmasq[1451]: using nameserver 10.4.1.120#53 Jan 26 10:22:37 tekkaman kernel: tg3: eth0: Link is down. Jan 26 10:22:37 tekkaman NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 10:22:39 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 10:22:39 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Jan 26 10:22:39 tekkaman NetworkManager: <info> (eth0): carrier now ON (device state 8) Jan 26 10:23:37 tekkaman kernel: tg3: eth0: Link is down. Jan 26 10:23:37 tekkaman NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 10:23:39 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 10:23:39 tekkaman NetworkManager: <info> (eth0): carrier now ON (device state 8) Jan 26 10:23:39 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Jan 26 10:40:53 tekkaman kernel: CE: hpet increasing min_delta_ns to 15000 nsec Jan 26 11:04:00 tekkaman kernel: tg3: eth0: Link is down. Jan 26 11:04:00 tekkaman NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 11:04:02 tekkaman NetworkManager: <info> (eth0): carrier now ON (device state 8) Jan 26 11:04:02 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 11:04:02 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Jan 26 11:05:50 tekkaman kernel: tg3: eth0: Link is down. Jan 26 11:05:50 tekkaman NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 11:05:52 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 11:05:52 tekkaman NetworkManager: <info> (eth0): carrier now ON (device state 8) Jan 26 11:05:52 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX.
On 01/26/2010 02:13 AM, Gianluca Cecchi wrote:
On Fri Jan 22 17:48:03 UTC 2010 Rick Stevens wrote:
It's NetworkManager doing that to you.
Ok, as I supposed.
Is there a reason they've set that up as fixed? Is there an autoneg issue with the switch (some don't do autonegotiation correctly).
There was a problem on older gigabit switches and for historical reasons was set up this way yet. Now they are on new ones and I asked them to put the switch port to autoneg. OK now for the speed part. I get 100/full after autoneg at boot.
But when I start for example an scp session of big files (around some tenths of megabytes) from/to my pc, I get many link down messages..... The transfer begins at 9.7MB/s and then continuously decreases at about 7 and also 5 MB/s.....
See below my /var/log/messages after reboot at about 09.30 this morning. For example at 10:23 and 11:05 I started scp sessions (single file of about 2.5Gb) Jan 26 09:34:54 tekkaman kernel: tg3: eth0: Link is down. Jan 26 09:34:54 tekkaman NetworkManager:<info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 09:34:55 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 09:34:55 tekkaman NetworkManager:<info> (eth0): carrier now ON (device state 8) Jan 26 09:34:55 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Jan 26 09:38:56 tekkaman ntpd[1264]: synchronized to 10.4.1.46, stratum 3 Jan 26 09:38:56 tekkaman ntpd[1264]: time reset +0.391977 s Jan 26 09:38:56 tekkaman ntpd[1264]: kernel time sync status change 2001 Jan 26 09:39:10 tekkaman dnsmasq[1451]: reading /etc/resolv.conf Jan 26 09:39:10 tekkaman dnsmasq[1451]: using nameserver 10.4.1.121#53 Jan 26 09:39:10 tekkaman dnsmasq[1451]: using nameserver 10.4.1.120#53 Jan 26 09:46:05 tekkaman ntpd[1264]: synchronized to 10.4.1.46, stratum 3 Jan 26 09:51:02 tekkaman NetworkManager:<info> (wlan0): device state change: 3 -> 2 (reason 0) Jan 26 09:51:02 tekkaman NetworkManager:<info> (wlan0): deactivating device (reason: 0). Jan 26 09:51:02 tekkaman NetworkManager:<info> Policy set 'Poli' (eth0) as default for routing and DNS. Jan 26 09:51:02 tekkaman NetworkManager:<info> (wlan0): taking down device. Jan 26 09:51:02 tekkaman dbus-daemon: Rejected send message, 2 matched rules; type="method_return", sender=":1.9" (uid=0 pid=1226 comm="NetworkManager) interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.45" (uid=500 pid=1773 comm="nm-applet)) Jan 26 10:08:18 tekkaman dnsmasq[1451]: reading /etc/resolv.conf Jan 26 10:08:18 tekkaman dnsmasq[1451]: using nameserver 10.4.1.121#53 Jan 26 10:08:18 tekkaman dnsmasq[1451]: using nameserver 10.4.1.120#53 Jan 26 10:22:37 tekkaman kernel: tg3: eth0: Link is down. Jan 26 10:22:37 tekkaman NetworkManager:<info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 10:22:39 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 10:22:39 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Jan 26 10:22:39 tekkaman NetworkManager:<info> (eth0): carrier now ON (device state 8) Jan 26 10:23:37 tekkaman kernel: tg3: eth0: Link is down. Jan 26 10:23:37 tekkaman NetworkManager:<info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 10:23:39 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 10:23:39 tekkaman NetworkManager:<info> (eth0): carrier now ON (device state 8) Jan 26 10:23:39 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Jan 26 10:40:53 tekkaman kernel: CE: hpet increasing min_delta_ns to 15000 nsec Jan 26 11:04:00 tekkaman kernel: tg3: eth0: Link is down. Jan 26 11:04:00 tekkaman NetworkManager:<info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 11:04:02 tekkaman NetworkManager:<info> (eth0): carrier now ON (device state 8) Jan 26 11:04:02 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 11:04:02 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Jan 26 11:05:50 tekkaman kernel: tg3: eth0: Link is down. Jan 26 11:05:50 tekkaman NetworkManager:<info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Jan 26 11:05:52 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Jan 26 11:05:52 tekkaman NetworkManager:<info> (eth0): carrier now ON (device state 8) Jan 26 11:05:52 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX.
Link down/up sequences are pretty indicative of a bad switch or a bad network cable. NetworkManager won't cause those, but it will respond to them. Note that the "NetworkManager: <info>" messages always follow "kernel: tg3" messages (which are coming from the driver).
I'd first try a new cable from your system to your wallplate (if you're wired like that). If there's no improvement, I'd have your IT people check the wiring in the wall and on your wallplate. If it's a typical 66-type punchdown wallplate socket, they sometimes get grungy with age and a repunch is necessary. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - "Do you suffer from long-term memory loss?" "I don't remember" - - -- Chumbawumba, "Amnesia" (TubThumping) - ----------------------------------------------------------------------
On Tue Jan 26 17:24:38 UTC 2010 Rick Stevens wrote:
I'd first try a new cable from your system to your wallplate (if you're wired like that). If there's no improvement, I'd have your IT people check the wiring in the wall and on your wallplate. If it's a typical 66-type punchdown wallplate socket, they sometimes get grungy with age and a repunch is necessary.
I fully agree and I noted the driver messages too, that came before NM ones... In fact I chnaged both cable and patch in the wall, with the same results.... ;-( I'm going to check with network guys ..... I'm going to try with a F11 system too.... in theory it should have the same kind of problems...
Thanks anyway Gianluca
Hello, I revamp this thread, as I tested all combinations of cables and duplex mode getting again the problem without any difference. Resuming: after starting a large transfer, I soon get this in /var/log/messages
Feb 9 15:40:14 tekkaman kernel: tg3: eth0: Link is down. Feb 9 15:40:14 tekkaman NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Feb 9 15:40:16 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Feb 9 15:40:16 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Feb 9 15:40:16 tekkaman NetworkManager: <info> (eth0): carrier now ON (device state 8)
And also the transfer rate suddenly drops from around 9.7MB/s to 4-5MB/s
News: I found this bugzilla below that is about tg3 and the same model as mine. My lspci output: 09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)
bugzilla entry: https://bugzilla.redhat.com/show_bug.cgi?id=527209
It is closed, but I noticed that applying the temporary workaround (see comments 19 and 21) that was in place before the supposed fix, now I continue to get the off/on for the interface, but at least I can sustain 10.1MB/s during the overall 600MB transfer.
My initial (default) setup with card set in auto sense and autonegotiation set up at 100mbit/s [root@tekkaman ~]# ethtool -k eth0 Offload parameters for eth0: Cannot get device flags: Operation not supported rx-checksumming: on tx-checksumming: on scatter-gather: on tcp-segmentation-offload: off udp-fragmentation-offload: off generic-segmentation-offload: on generic-receive-offload: off large-receive-offload: off
Workaround: [root@tekkaman ~]# ethtool -K eth0 sg off
verify changed settings: [root@tekkaman ~]# ethtool -k eth0 Offload parameters for eth0: Cannot get device flags: Operation not supported rx-checksumming: on tx-checksumming: on scatter-gather: off tcp-segmentation-offload: off udp-fragmentation-offload: off generic-segmentation-offload: on generic-receive-offload: off large-receive-offload: off
transfer test: [gcecchi@tekkaman ~]$ time scp Downloads/SS830.2009_0817.103-x64.iso root@mysrv:/root root@mysrv's password: SS830.2009_0817.103-x64.iso 100% 603MB 10.6MB/s 00:57
real 0m59.383s user 0m17.708s sys 0m3.957s
After the first 10-20 MBytes transferred I get these in /var/log/messages: Feb 9 15:40:14 tekkaman kernel: tg3: eth0: Link is down. Feb 9 15:40:14 tekkaman NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds) Feb 9 15:40:16 tekkaman kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Feb 9 15:40:16 tekkaman kernel: tg3: eth0: Flow control is off for TX and off for RX. Feb 9 15:40:16 tekkaman NetworkManager: <info> (eth0): carrier now ON (device state 8)
Anyone with this model got this problem again? Possible a regression after the 127 kernel? Before re-opening the bugzilla I would like to share....
Thanks again for comments and input. Gianluca
-
Gianluca Cecchi -
Rick Stevens