tg3 driver timeout problems

tg3 driver timeout problems

[sunny12]

Hi,

we're experiencing serious problems on an productions system running fecora
core5 ( 2.6.17-1.2157_FC5smp #1)  and
running the tg3 driver.
Here is my dmesg output:

tg3.c:v3.59 (June 8, 2006)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth0: Tigon3 [partno(BCM95721) rev 4001 PHY(5750)] (PCI Express)
10/100/1000BaseT Ethernet 00:16:17:2a:a8:4d
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:04:06.0[A] -> GSI 19 (level, low) -> IRQ 185
eth1: Tigon3 [partno(BCM95705A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit)
10/100/1000BaseT Ethernet 00:16:17:2a:a8:4c
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[0]
TSOcap[1]
eth1: dma_rwctrl[763f0000] dma_mask[64-bit]
audit(1154348602.046:4): avc:  denied  { create } for  pid=953 comm="udevd"
name="watchdog" scontext=system_u:system_r:udev_t:

ethtool output

Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        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 sympton is that sometimes the network is down we cant ping the network
device anymore.
Also from a shell we cant ping the outside world. We can still ping the ipnr
of the network device itself.

A restart of the network using /etc/init.d/network restart does the trick
and the device works again.
I dont think this is related to the TSO problem reported earlier because I
believe its disabled by default.

Any clues, help would be appreciated.
Please let me know if I need to provide additional debug info.

thanks,regards

-- 
View this message in context: http://www.nabble.com/tg3-driver-timeout-problems-tf2254084.html#a6252031
Sent from the netdev forum at Nabble.com.

Re: tg3 driver timeout problems

[Michael Chan]

On Mon, 2006-09-11 at 11:18 -0700, sunny12 wrote:

> A restart of the network using /etc/init.d/network restart does the trick
> and the device works again.
> I dont think this is related to the TSO problem reported earlier because I
> believe its disabled by default.
> 
TSO may be on by default on eth0 where you have a 5721.  Check with
ethtool -k eth0.  Turn it off if it is on by doing ethtool -K eth0 tso
off.

Re: tg3 driver timeout problems

[sunny12]

Thanks a lot Michael, it seems to have resolved the issue, at least we were
not able to reproduce it again
after changing this flag. I will update this thread if the issue reoccurs.



Michael Chan wrote:
> 
> On Mon, 2006-09-11 at 11:18 -0700, sunny12 wrote:
> 
>> A restart of the network using /etc/init.d/network restart does the trick
>> and the device works again.
>> I dont think this is related to the TSO problem reported earlier because
>> I
>> believe its disabled by default.
>> 
> TSO may be on by default on eth0 where you have a 5721.  Check with
> ethtool -k eth0.  Turn it off if it is on by doing ethtool -K eth0 tso
> off.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

-- 
View this message in context: http://www.nabble.com/tg3-driver-timeout-problems-tf2254084.html#a6315074
Sent from the netdev forum at Nabble.com.

Re: tg3 driver timeout problems

[Michael Chan]

sunny12 wrote:
> Thanks a lot Michael, it seems to have resolved the issue, at 
> least we were
> not able to reproduce it again
> after changing this flag. I will update this thread if the 
> issue reoccurs.

That's good to know.  When you upgrade to the next 2.6.18
kernel, you can re-enable TSO because the latest driver has
the workaround for this problem.