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

[Xen-bugs] [Bug 62] Losing network when xend started

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 62] Losing network when xend started
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 15 Jun 2005 17:00:59 +0000
Delivery-date: Wed, 15 Jun 2005 17:01:03 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=62





------- Additional Comments From ian.pratt@xxxxxxxxxxxx  2005-06-15 17:00 
-------
Do you always get the "can't decode bridge speed" and "e1000_watchdog" 
messages, 
or only when there's a failure?

I'm very surprised to see messages coming out of the e1000. Putting it in 
promiscuous mode shouldn't be such a big deal.

Has anyone seen this on a NIC other than the e1000?

When its in this broken state, do you see its interrupt line going up? Can you 
tell if packets are going out? Can you see if packets are being received 
(tcpdump)?

[As I recall, the problem could be fixed by unloading/loading the e1000 module, 
right?]






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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