WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] NETDEV WATCHDOG: eth2 (tg3): transmit queue 0 timed out

To: Qiangmin Lin <linqiangmin@xxxxxxxxxx>
Subject: Re: [Xen-devel] NETDEV WATCHDOG: eth2 (tg3): transmit queue 0 timed out
From: wei song <james.songwei@xxxxxxxxx>
Date: Thu, 4 Nov 2010 11:37:03 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 03 Nov 2010 20:37:47 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=vi7ISNN0cK2fP/fnXvaMyfkTMFCPV3/Ym3aKZbpluQs=; b=wB9UVe/tN6jqiguIc0dcLaJW+45XRC/NaJDnCA7ETFkoLB9WTkoD8AYU7X5IjjV7wk AGKqR9qj86LeeVMtT6lnpDGzvYTwuQ4mGktmV2Mw/Whbdj2mMJao7bV4crFd2CQ7yo4J 45pdulFl4EQRkvLXLvoJ5ZJ9exH+/4/PrPLEg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hGBkI7aDG0duta2Usb8TgalXJyRHrSDh2ht6btlwplx4DSLVJzxwA86JkI2Eu4VwDM sTkJsrNgl3mmET9CTMtl+2LPYS7p6JsFaQGMcFdsXoUibqotsq6z4Pa1oXGpKxlfvBIJ wQDmZja8EUO51d+/RzjUMyc7KtjxsTWfoCWZE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <001d01cb7bcf$b6b568e0$8550a60a@xxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <201011040138.CXR64213@xxxxxxxxxxxxxxxxxxxxx> <001d01cb7bcf$b6b568e0$8550a60a@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
It's seems that a timeout take place at tx action. What's the nic driver version you used for Broadcom?  In addition, what's the parameters added when insmod nic driver.

-James (Song Wei)

2010/11/4 Qiangmin Lin <linqiangmin@xxxxxxxxxx>
Step 1.
 
CPU:Intel(R) Xeon(R) CPU E5620  @ 2.40GHz * 2
Nic:Broadcom 5715S * 6
 
Kernel:2.6.32.12-0.7-xen
Xen:3.4.2
 
Step 2.
 
A timeout error appears and dumps the following stack, after about a week.
 
we change Nic Intel 82576 and 82571, the timeout error as follow too.
 

[ 8385.279738] ------------[ cut here ]------------
 
[ 8385.279749] WARNING: at /usr/src/linux-2.6.32.12-0.7/net/sched/sch_generic.c:261 dev_watchdog+0x2a5/0x2c0()
 
[ 8385.279751] Hardware name:         
 
[ 8385.279753] NETDEV WATCHDOG: eth2 (tg3): transmit queue 0 timed out
 
[ 8385.279755] Modules linked in: tun(N) iptable_mangle(N) xt_physdev(N) xt_pkttype(N) ipt_MASQUERADE(N) iptable_nat(N) nf_nat(N) xt_tcpudp(N) bridge(N) gntdev(N) netbk(N) blkbk(N) blkback_pagemap(N) blktap(N) domctl(N) xenbus_be(N) ipmi_devintf(N) ipmi_si(N) ipmi_msghandler(N) cryptomgr(N) aead(N) pcompress(N) crypto_blkcipher(N) crc32c(N) crypto_hash(N) crypto_algapi(N) iscsi_tcp(N) libiscsi_tcp(N) libiscsi(N) scsi_transport_iscsi(N) 8021q(N) garp(N) stp(N) llc(N) bonding(N) microcode(N) kbox_netdev(N) dl_kbox(N) binfmt_misc(N) ip6t_REJECT(N) nf_conntrack_ipv6(N) ip6table_raw(N) xt_NOTRACK(N) ipt_REJECT(N) xt_state(N) iptable_raw(N) iptable_filter(N) ip6table_mangle(N) nf_conntrack_netbios_ns(N) nf_conntrack_ipv4(N) nf_conntrack(N) nf_defrag_ipv4(N) ip_tables(N) ip6table_filter(N) ip6_tables(N) x_tables(N) ipv6(N) usbhid(N) hid(N) loop(N) dm_mod(N) tpm_tis(N) 8250_pnp(N) tg3(N) tpm(N) iTCO_wdt(N) tpm_bios(N) pcspkr(N) shpchp(N) pci_hotplug(N) iTCO_vendor_support(N) serio_raw(N) mptctl(N) i2c_i801(N) 8250(N) i2c_core(N) serial_core(N) button(N) uhci_hcd(N) ehci_hcd(N) usbcore(N) xenblk(N) cdrom(N) xennet(N) upVhba edd(N) fan(N) thermal(N) processor(N) thermal_sys(N) hwmon(N) ata_piix(N) libata(N) mptsas(N) mptscsih(N) mptbase(N) scsi_transport_sas(N) upUpper sg(N) sd_mod(N) crc_t10dif(N) scsi_mod(N)
 
[ 8385.279817] Supported: Yes
 
[ 8385.279820] Pid: 0, comm: swapper Tainted: G          N  2.6.32.12-0.7-xen #1
 
[ 8385.279822] Call Trace:
 
[ 8385.279840]  [<ffffffff80009a75>] dump_trace+0x65/0x180
 
[ 8385.279849]  [<ffffffff8036d496>] dump_stack+0x69/0x73
 
[ 8385.279858]  [<ffffffff8003d2e4>] warn_slowpath_common+0x74/0xd0
 
[ 8385.279863]  [<ffffffff8003d390>] warn_slowpath_fmt+0x40/0x50
 
[ 8385.279867]  [<ffffffff802e5bb5>] dev_watchdog+0x2a5/0x2c0
 
[ 8385.279875]  [<ffffffff800494e2>] run_timer_softirq+0x1b2/0x2e0
 
[ 8385.279881]  [<ffffffff80043a3e>] __do_softirq+0xde/0x1a0
 
[ 8385.279886]  [<ffffffff80007f3c>] call_softirq+0x1c/0x30
 
[ 8385.279892]  [<ffffffff80009535>] do_softirq+0xa5/0xe0
 
[ 8385.279899]  [<ffffffff802746e2>] evtchn_do_upcall+0x212/0x2a0
 
[ 8385.279905]  [<ffffffff8000799e>] do_hypervisor_callback+0x1e/0x30
 
[ 8385.279913]  [<ffffffff800033aa>] 0xffffffff800033aa
 
[ 8385.279923]  [<ffffffff8000a826>] xen_safe_halt+0xb6/0x130
 
[ 8385.279928]  [<ffffffff8000de1d>] xen_idle+0x5d/0x70
 
[ 8385.279933]  [<ffffffff800065cf>] cpu_idle+0x5f/0xa0
 
[ 8385.279941]  [<ffffffff8063bbd5>] start_kernel+0x374/0x443
 
[ 8385.279945] ---[ end trace 38582b64ba009d90 ]---
 
[ 8385.279949] pci 0000:04:00.0: eth2: transmit timed out, resetting
 
[ 8385.279953] pci 0000:04:00.0: eth2: DEBUG: MAC_TX_STATUS[00000008] MAC_RX_STATUS[00000000]
 
[ 8385.279957] pci 0000:04:00.0: eth2: DEBUG: RDMAC_STATUS[00000000] WDMAC_STATUS[00000000]
 
[ 8385.279962] pci 0000:04:00.0: eth3: transmit timed out, resetting
 
[ 8385.279966] pci 0000:04:00.0: eth3: DEBUG: MAC_TX_STATUS[00000008] MAC_RX_STATUS[00000000]
 
[ 8385.279970] pci 0000:04:00.0: eth3: DEBUG: RDMAC_STATUS[00000000] WDMAC_STATUS[00000000]
 
[ 8385.296378] pci 0000:04:00.0: eth2: Link is down
 
[ 8385.334989] pci 0000:04:00.0: eth3: Link is down
 
Please let me know if you need further information.
So perhaps you can help.
 
Many thanks in advance,
best regards,

qiangmin lin

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel