 Home |
Products |
Support |
Community |
News |
xen-users
Re: [Xen-users] eth0: port 1(peth0) entering disabled state
| To: | Rémi BERNIER <R.BERNIER@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-users] eth0: port 1(peth0) entering disabled state |
| From: | Diego Augusto Molina <diegoaugustomolina@xxxxxxxxx> |
| Date: | Wed, 10 Aug 2011 03:57:45 -0300 |
| Cc: | Xen-users@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Wed, 10 Aug 2011 00:00:41 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rd+c6y1mUhDbTupRHC/n/zN/jkVhfTKzdWdjEr2yeRw=; b=SyFbukerjBaANgmFNFGshGK8f4nIjQjjaD7QAd+heZcsN55GU4fzGgq2K2/WGNSuw/ LIRXbHGySHtI16FdskvPRWvSeRt4UBdmUQ3lhSUeuBSG+q80rxhYLaEidFs2ctjRmo3e JxHZIY5ZzvsMpF7GryNqu35e7k924gw3deBKU= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <OF50F14CB9.F26C0FA4-ONC12578E8.002307E2-C12578E8.0023E3F8@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: | <OFA8431346.AA545E28-ONC1257873.0028AF6F-C1257873.002D7229@xxxxxxxxxxx> <OF50F14CB9.F26C0FA4-ONC12578E8.002307E2-C12578E8.0023E3F8@xxxxxxxxxxx> |
| Sender: | xen-users-bounces@xxxxxxxxxxxxxxxxxxx |
Have you tried testing the hardware? Look at the general load of your systems: can you find any pattern between one or more processes and the link breaking? If so, the hardware or device driver may not respond correctly to certain loads (though the tg3 is a longly tested module). Can you check with another NIC? (e.g. add a NIC and change udev rules so that it becomes the new eth0/peth0). Is it possible for you to switch to a newer kernel and test? Also check the patchcords and the phisical network. Have you performed any of these or other tests? This is just to cover basic stuff (don't get angry at me). -- Diego Augusto Molina diegoaugustomolina@xxxxxxxxx ES: Por favor, evite adjuntar documentos de Microsoft Office. Serán desestimados. EN: Please, avoid attaching Microsoft Office documents. They shall be discarded. LINK: http://www.gnu.org/philosophy/no-word-attachments.html _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-users] eth0: port 1(peth0) entering disabled state, Rémi BERNIER |
|---|---|
| Next by Date: | Re: [Xen-users] eth0: port 1(peth0) entering disabled state, Rémi BERNIER |
| Previous by Thread: | [Xen-users] eth0: port 1(peth0) entering disabled state, Rémi BERNIER |
| Next by Thread: | Re: [Xen-users] eth0: port 1(peth0) entering disabled state, Rémi BERNIER |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
