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-users

Re: [Xen-users] suddenly no network, peth0: transmit timed out

To: Rémi BERNIER <R.BERNIER@xxxxxxxxxxx>
Subject: Re: [Xen-users] suddenly no network, peth0: transmit timed out
From: Todd Deshane <todd.deshane@xxxxxxx>
Date: Wed, 13 Apr 2011 05:20:26 +0000
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Apr 2011 22:21:43 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=pdroaz/tQN9bUup6fuZv0746vFDMSz9jflwcoW8jGYg=; b=Y7lqPzH9r7CDPMG6nh08L1X1DK2kvOvNoqypQRdKkWPfB8LnLTbUUzGuHWC4vQl4YD 0p6WRCiwEwagW0A3Kbkv9N9Tjp1C2CXacX8nBtK473k8QhUfBKEpQ+E3ZvnfY/3WfpXJ oCd0gqPvmsxDoVtqrS48f4ZUKqNq5WvUSBU7s=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=e5OIZ10C569+nHb/zrl8ClGCQkIqNy5EsyPeUG/CHRs749dHGswvuHqH8E/LuSEg7U MtMV5WqVqwtolAHpSMXhptJSGp0wGbJNOTsme/0KHoOW9f5dGSuTgHrRtrm4yv5KDUzv rlOoRn5qaBKgL4uZCfFDGt2xnHRzJFiXoVDSs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <OF5F28C90F.6AB2A38B-ONC1257870.002F4EA5-C1257870.002F6C2D@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <OF1CF68211.3E9650FD-ONC125782B.003B95A0-C125782B.003BF1B2@xxxxxxxxxxx> <OF5F28C90F.6AB2A38B-ONC1257870.002F4EA5-C1257870.002F6C2D@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Apr 12, 2011 at 8:37 AM, Rémi BERNIER <R.BERNIER@xxxxxxxxxxx> wrote:
>
> I had the same problem today. My server doesn't respond on ssh, ping ... but
> i have access on console.
> This is the logs of my kernel:
>
> Apr 12 09:13:10 svxen kernel: eth0: port 2(vif2.0) entering disabled state
> Apr 12 09:13:10 svxen kernel: eth0: port 1(peth0) entering disabled state
> Apr 12 09:13:50 svxen kernel: eth0: port 2(vif2.0) entering learning state
> Apr 12 09:13:50 svxen kernel: eth0: port 1(peth0) entering learning state
> Apr 12 09:13:50 svxen kernel: eth0: topology change detected, propagating
> Apr 12 09:13:50 svxen kernel: eth0: port 2(vif2.0) entering forwarding state
> Apr 12 09:13:50 svxen kernel: eth0: topology change detected, propagating
> Apr 12 09:13:50 svxen kernel: eth0: port 1(peth0) entering forwarding state
> Apr 12 09:14:01 svxen kernel: eth0: no IPv6 routers present
> Apr 12 09:14:15 svxen kernel: NETDEV WATCHDOG: peth0: transmit timed out
> Apr 12 09:14:15 svxen kernel: tg3: peth0: transmit timed out, resetting
> Apr 12 09:14:15 svxen kernel: tg3: DEBUG: MAC_TX_STATUS[00000008]
> MAC_RX_STATUS[00000000]
> Apr 12 09:14:15 svxen kernel: tg3: DEBUG: RDMAC_STATUS[00000000]
> WDMAC_STATUS[00000000]
> Apr 12 09:14:15 svxen kernel: tg3: peth0: Link is down.
>
> Anyone have met this problem ?
>
> My network card is:
> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigabit
> Ethernet PCI Express
>
> modinfo tg3
> filename:       /lib/modules/2.6.18.8/kernel/drivers/net/tg3.ko
> version:        3.99k
> license:        GPL
> description:    Broadcom Tigon3 ethernet driver
> author:         David S. Miller (davem@xxxxxxxxxx) and Jeff Garzik
> (jgarzik@xxxxxxxxx)
> srcversion:     1F42BAC68F1166C6BAD2BF4
> alias:          pci:v0000106Bd00001645sv*sd*bc*sc*i*
> depends:
> vermagic:       2.6.18.8 SMP mod_unload Xen gcc-4.3
> parm:           tg3_debug:Tigon3 bitmapped debugging message enable value
> (int)
>

Have you tried disabling checksumming?

see:
http://xen.markmail.org/search/?q="ethtool+-K"#query:%22ethtool%20-K%22+page:1+mid:ozu24u7azscw2zwf+state:results

>
> Thanks in advance for your answer.
> Regards,
> Rémi
>
>
>
>
>
>
> On a stable server with an uptime to 3-4 months, i had suddenly no network
> but I had access to console, i have restart network, ifup eth0 but nothing
> to do, link peth0 is down !! I have restart server for it works again.
>
> On my syslog:
> Feb  2 09:07:58 xen kernel: NETDEV WATCHDOG: peth0: transmit timed out
> Feb  2 09:07:58 xen kernel: tg3: peth0: transmit timed out, resetting
> Feb  2 09:07:58 xen kernel: tg3: DEBUG: MAC_TX_STATUS[00000008]
> MAC_RX_STATUS[00000000]
> Feb  2 09:07:58 xen kernel: tg3: DEBUG: RDMAC_STATUS[00000000]
> WDMAC_STATUS[00000000]
> Feb  2 09:07:58 xen kernel: tg3: tg3_stop_block timed out, ofs=1400
> enable_bit=2
> Feb  2 09:07:58 xen kernel: tg3: peth0: Link is down.
> Feb  2 09:07:58 xen kernel: eth0: port 1(peth0) entering disabled state
>
> I have search on google, user-list but I have not found any solution
> Maybe disabled acpi ?? My server is on debian lenny, xen 3.4.2 with
> linux-2.6.18-xen. I have activate iommu for a tape drive on my domU win2k3
>
> If you have met this problem I listen you !!
> Thanks in advance for your answer !!
> Regards,
>
> Rémi_______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html

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

<Prev in Thread] Current Thread [Next in Thread>