|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Network stops responding after some time
> I'm using the Suse Enterprise 10 RC2 along with Xen 3.0.2 on
> X86-64 and I'm experiencing a problem with the network.
> I boot into the Xen kernel and everything works just fine. I
> can browse the net etc.
> However after a while the network stops responding
> completely. I am not sure what causes this to happen or what
> triggers it. After a few hours, the network just stops working.
>
> Doing an ifconfig -a before and after gives me the following
>
> Before
> eth0 Link encap:Ethernet HWaddr 00:0D:61:42:F5:8D
> inet addr:172.18.41.82 Bcast:172.18.43.255
> Mask:255.255.252.0
> inet6 addr: fe80::20d:61ff:fe42:f58d/64 Scope:Link
> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500
> Metric:1
> RX packets:278 errors:0 dropped:0 overruns:0 frame:0
> TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
> After
> eth0 Link encap:Ethernet HWaddr 00:0D:61:42:F5:8D
> inet addr:172.18.41.82 Bcast:172.18.43.255
> Mask:255.255.252.0
> inet6 addr: fe80::20d:61ff:fe42:f58d/64 Scope:Link
> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500
> Metric:1
> RX packets:192846 errors:0 dropped:15431 overruns:0 frame:0
> TX packets:2268 errors:0 dropped:506 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:29687820 (28.3 Mb) TX bytes:324494 (316.8 Kb)
> Interrupt:19 Base address:0x8000
> I am not sure what else would be helpful in diagnosing the
> problem. Does anybody has any ideas on what else I should be checking?
Are these stats from dom0 before starting xend?
The dropped counts in eth0 suggest the ethernet device driver has locked
up. My bet would be that the interrupt count stops going up (see
/proc/interrupts).
Compare the irq number between the xen and normal kernels. In fact, diff
the boot messages to check the same irq routeing etc is happening.
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|