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] Network stops responding after some time

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Network stops responding after some time
From: Adnan Khaleel <adnan@xxxxxxxxxx>
Date: Wed, 19 Jul 2006 11:02:51 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 20 Jul 2006 05:30:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D068C72@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: adnan@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello Ian,

I'm still having the same problem with SLES 10 RC3. Any idea what might be 
causing it?

Thanks

Adnan

============================================================================

Hi Ian,

Thanks for your response.

The "before" and "after" are with respect to the problem i.e. network st=
ops responding. Xend should be running at both times.

I've followed your instructions on looking at /proc/interrupts and it ap=
pears you are correct.
The interrupts on the eth0 stop incrementing suggesting that the driver =
has indeed locked up.

/proc/interrupts for a normal kernel are as follows

CPU0 =20
0: 89746 IO-APIC-edge timer
1: 1108 IO-APIC-edge i8042
8: 0 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
12: 9016 IO-APIC-edge i8042
14: 11954 IO-APIC-edge ide0
15: 3131 IO-APIC-edge ide1
177: 948 IO-APIC-level eth0
185: 0 IO-APIC-level NVidia nForce3, ehci=5Fhcd:usb3
193: 3 IO-APIC-level ohci1394
201: 0 IO-APIC-level ohci=5Fhcd:usb1
209: 0 IO-APIC-level ohci=5Fhcd:usb2
NMI: 73=20
LOC: 89668=20
ERR: 0
MIS: 0


For xen modified kernel its

CPU0 =20
1: 631 Phys-irq i8042
8: 0 Phys-irq rtc
9: 0 Phys-irq acpi
12: 3892 Phys-irq i8042
14: 12836 Phys-irq ide0
15: 167614 Phys-irq ide1
16: 0 Phys-irq NVidia nForce3, ohci=5Fhcd:usb3
17: 65340 Phys-irq peth0 <=3D Thi=
s stops incrementing
18: 0 Phys-irq ehci=5Fhcd:usb1
19: 0 Phys-irq ohci=5Fhcd:usb2
20: 3 Phys-irq ohci1394
256: 1091622 Dynamic-irq timer0
257: 0 Dynamic-irq resched0
258: 0 Dynamic-irq callfunc0
259: 85 Dynamic-irq xenbus
260: 0 Dynamic-irq console
NMI: 0=20
LOC: 0=20
ERR: 0
MIS: 0

Doing a diff between the boot.msg of a normal kernel and a xen kernel gi=
ves me the following. Its a little verbose .. sorry.

So do you think its an issue with the network card driver or is somethin=
g else happening=3F

Adnan



#diff boot.msg.normal boot.msg.xen

1,2c1,2
< Inspecting /boot/System.map-2.6.16.20-0.12-default
< Loaded 21787 symbols from /boot/System.map-2.6.16.20-0.12-default.
---
> Inspecting /boot/System.map-2.6.16.20-0.12-xen
> Loaded 21807 symbols from /boot/System.map-2.6.16.20-0.12-xen.
7,18c7,13
< <4>Bootdata ok (command line is root=3D/dev/hda2 vga=3D0x31a resume=
=3D/dev/hda1 splash=3Dsilent)
< <5>Linux version 2.6.16.20-0.12-default (geeko@buildhost) (gcc version=
4.1.0 (SUSE Linux)) #1 Mon Jun 19 22:25:45 UTC 2006
< <6>BIOS-provided physical RAM map:
< <4> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
< <4> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
< <4> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
< <4> BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
< <4> BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
< <4> BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
< <4> BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
< <4> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
< <4> BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
---
> <4>Bootdata ok (command line is root=3D/dev/hda2 vga=3D0x31a resume=
=3D/dev/hda1 splash=3Dsilent showopts)
> <5>Linux version 2.6.16.20-0.12-xen (geeko@buildhost) (gcc version 4.1=
.0 (SUSE Linux)) #1 SMP Mon Jun 19 22:25:45 UTC 2006
> <7>On node 0 totalpages: 119388
> <7> DMA zone: 119388 pages, LIFO batch:31
> <7> DMA32 zone: 0 pages, LIFO batch:0
> <7> Normal zone: 0 pages, LIFO batch:0
> <7> HighMem zone: 0 pages, LIFO batch:0
24,30d18
< <7>On node 0 totalpages: 128347
< <7> DMA zone: 3122 pages, LIFO batch:0
< <7> DMA32 zone: 125225 pages, LIFO batch:31
< <7> Normal zone: 0 pages, LIFO batch:0
< <7> HighMem zone: 0 pages, LIFO batch:0
< <6>Nvidia board detected. Ignoring ACPI timer override.
< <6>ACPI: PM-Timer IO Port: 0x1008
33d20
< <6>Processor #0 15:4 APIC version 16
38d24
< <4>ACPI: BIOS IRQ0 pin2 override ignored.
39a26,27
> <7>ACPI: IRQ0 used by override.
> <7>ACPI: IRQ2 used by override.
41c29
< <6>Setting APIC routing to flat
---
> <6>Setting APIC routing to xen
44,45d31
< <4>Checking aperture...
< <4>CPU 0: aperture @ e8000000 size 128 MB
47c33
< <5>Kernel command line: root=3D/dev/hda2 vga=3D0x31a resume=3D/dev/=
hda1 splash=3Dsilent
---
> <5>Kernel command line: root=3D/dev/hda2 vga=3D0x31a resume=3D/dev/=
hda1 splash=3Dsilent showopts
51,53c37,38
< <6>time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer.
< <6>time.c: Detected 2009.183 MHz processor.
< <4>Console: colour dummy device 80x25
---
> <6>Xen reported: 2009.162 MHz processor.
> <4>Console: colour VGA+ 80x25
56,57c41,46
< <4>Memory: 509356k/524224k available (1725k kernel code, 14140k reserv=
ed, 770k data, 164k init)
< <4>Calibrating delay using timer specific routine.. 4022.70 BogoMIPS (=
lpj=3D8045401)
---
> <6>Software IO TLB enabled:=20
> <4> Aperture: 2 megabytes
> <4> Kernel range: 0xffff880000d05000 - 0xffff880000f05000
> <6>PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> <4>Memory: 446844k/477552k available (1843k kernel code, 30072k reserv=
ed, 782k data, 140k init)
> <4>Calibrating delay using timer specific routine.. 5024.16 BogoMIPS (=
lpj=3D10048324)
62d50
< <4>CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 08
64,69c52,54
< <4>Freeing initrd memory: 2833k freed
< <4> not found!
< <6>Using local APIC timer interrupts.
< <4>result 12557413
< <6>Detected 12.557 MHz APIC timer.
< <6>testing NMI watchdog ... OK.
---
> <4>Freeing initrd memory: 6898k freed
> <6>Brought up 1 CPUs
> <4>migration=5Fcost=3D0
70a56
> <4>Grant table initialized
117a104
> <6>xen=5Fmem: Initialising balloon driver.
121,124d107
< <6>agpgart: Detected AGP bridge 0
< <6>agpgart: Setting up Nforce3 AGP.
< <6>agpgart: AGP aperture is 128M @ 0xe8000000
< <6>PCI-DMA: Disabling IOMMU.
136,137c119
< <5>audit(1151491717.500:1): initialized
< <4>Total HugeTLB memory allocated, 0
---
> <5>audit(1151492142.508:1): initialized
145,151d126
< <6>vesafb: framebuffer at 0xf0000000, mapped to 0xffffc20000100000, us=
ing 10240k, total 65536k
< <6>vesafb: mode is 1280x1024x16, linelength=3D2560, pages=3D1
< <6>vesafb: scrolling: redraw
< <6>vesafb: Truecolor: size=3D0:5:6:5, shift=3D0:11:5:0
< <6>bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg s=
ize 75438 bytes,<6>...found (1280x1024, 35600 bytes, v3).
< <4>Console: switching to colour frame buffer device 155x60
< <6>fb0: VESA VGA frame buffer device
154a130,134
> <6>agpgart: Detected AGP bridge 0
> <6>agpgart: Setting up Nforce3 AGP.
> <3>agpgart: unable to get memory for graphics translation table.
> <6>agpgart: agp=5Fbackend=5Finitialize() failed.
> <4>agpgart-amd64: probe of 0000:00:00.0 failed with error -12
157,159d136
< <6>Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing di=
sabled
< <6>serial8250: ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A
< <6>serial8250: ttyS1 at I/O 0x2f8 (irq =3D 3) is a 16550A
161a139,140
> <4>Xen virtual console successfully installed as ttyS0
> <4>Event-channel device installed.
170,171c149,150
< <4>TCP established hash table entries: 16384 (order: 5, 131072 bytes)
< <4>TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
---
> <4>TCP established hash table entries: 16384 (order: 6, 262144 bytes)
> <4>TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
175,178d153
< <4>ACPI wakeup devices:=20
< <4>HUB0 HUB1 USB0 USB1 USB2 F139 MMAC MMCI UAR1=20
< <6>ACPI: (supports S0 S1 S4 S5)
< <4>Freeing unused kernel memory: 164k freed
203,204d177
< <6>BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
< <4>Attempting manual resume
213d185
< <7>Losing some ticks... checking if CPU frequency changed.
216,223d187
< <6>r8169 Gigabit Ethernet driver 2.2LK loaded
< <4>ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
< <6>GSI 16 sharing vector 0xB1 and IRQ 16
< <6>ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [APC4] -> GSI 19 (level=
, low) -> IRQ 177
< <7>eth0: Identified chip type is 'RTL8169s/8110s'.
< <6>eth0: RTL8169 at 0xffffc20000030000, 00:0d:61:42:f5:8d, IRQ 177
< <6>Floppy drive(s): fd0 is 1.44M
< <6>FDC 0 is a post-1991 82077
225,226c189,190
< <6>GSI 17 sharing vector 0xB9 and IRQ 17
< <6>ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 22 (level=
, high) -> IRQ 185
---
> <6>GSI 16 sharing vector 0xA0 and IRQ 16
> <6>ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 22 (level=
, high) -> IRQ 16
228,239c192,193
< <7>ieee1394: Initialized config rom entry `ip1394'
< <6>intel8x0=5Fmeasure=5Fac97=5Fclock: measured 53650 usecs
< <6>intel8x0: clocking to 48000
< <6>i2c=5Fadapter i2c-0: nForce2 SMBus adapter at 0x1c00
< <6>i2c=5Fadapter i2c-1: nForce2 SMBus adapter at 0x2000
< <6>hdc: ATAPI 52X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
< <6>Uniform CD-ROM driver Revision: 3.20
< <6>pci=5Fhotplug: PCI Hot Plug PCI Core version: 0.5
< <4>ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
< <6>GSI 18 sharing vector 0xC1 and IRQ 18
< <6>ACPI: PCI Interrupt 0000:01:0e.0[A] -> Link [APC3] -> GSI 18 (level=
, low) -> IRQ 193
< <6>ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=3D[193] MMIO=3D[f7004=
000-f70047ff] Max Packet=3D[2048] IR/IT contexts=3D[4/8]
---
> <6>Floppy drive(s): fd0 is 1.44M
> <6>FDC 0 is a post-1991 82077
242,249c196,213
< <7>ohci=5Fhcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Dri=
ver (PCI)
< <4>ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
< <6>GSI 19 sharing vector 0xC9 and IRQ 19
< <6>ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21 (level=
, high) -> IRQ 201
< <7>PCI: Setting latency timer of device 0000:00:02.0 to 64
< <6>ohci=5Fhcd 0000:00:02.0: OHCI Host Controller
< <6>ohci=5Fhcd 0000:00:02.0: new USB bus registered, assigned bus numbe=
r 1
< <6>ohci=5Fhcd 0000:00:02.0: irq 201, io mem 0xf8003000
---
> <6>intel8x0=5Fmeasure=5Fac97=5Fclock: measured 55861 usecs
> <6>intel8x0: clocking to 47457
> <6>r8169 Gigabit Ethernet driver 2.2LK loaded
> <4>ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
> <6>GSI 17 sharing vector 0xA8 and IRQ 17
> <6>ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [APC4] -> GSI 19 (level=
, low) -> IRQ 17
> <7>eth0: Identified chip type is 'RTL8169s/8110s'.
> <6>eth0: RTL8169 at 0xffffc200001d0000, 00:0d:61:42:f5:8d, IRQ 17
> <4>ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
> <6>GSI 18 sharing vector 0xB0 and IRQ 18
> <6>ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 21 (level=
, high) -> IRQ 18
> <7>PCI: Setting latency timer of device 0000:00:02.2 to 64
> <6>ehci=5Fhcd 0000:00:02.2: EHCI Host Controller
> <6>ehci=5Fhcd 0000:00:02.2: debug port 1
> <7>PCI: cache line size of 64 is not supported by device 0000:00:02.2
> <6>ehci=5Fhcd 0000:00:02.2: new USB bus registered, assigned bus numbe=
r 1
> <6>ehci=5Fhcd 0000:00:02.2: irq 18, io mem 0xf8005000
> <6>ehci=5Fhcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec =
2004
252,254c216,218
< <6>usb usb1: Product: OHCI Host Controller
< <6>usb usb1: Manufacturer: Linux 2.6.16.20-0.12-default ohci=5Fhcd
< <6>usb usb1: SerialNumber: 0000:00:02.0
---
> <6>usb usb1: Product: EHCI Host Controller
> <6>usb usb1: Manufacturer: Linux 2.6.16.20-0.12-xen ehci=5Fhcd
> <6>usb usb1: SerialNumber: 0000:00:02.2
257,264c221,231
< <6>hub 1-0:1.0: 3 ports detected
< <4>ACPI: PCI Interrupt Link [APCG] enabled at IRQ 20
< <6>GSI 20 sharing vector 0xD1 and IRQ 20
< <6>ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 20 (level=
, high) -> IRQ 209
< <7>PCI: Setting latency timer of device 0000:00:02.1 to 64
< <6>ohci=5Fhcd 0000:00:02.1: OHCI Host Controller
< <6>ohci=5Fhcd 0000:00:02.1: new USB bus registered, assigned bus numbe=
r 2
< <6>ohci=5Fhcd 0000:00:02.1: irq 209, io mem 0xf8004000
---
> <6>hub 1-0:1.0: 6 ports detected
> <7>ieee1394: Initialized config rom entry `ip1394'
> <7>ohci=5Fhcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Dri=
ver (PCI)
> <4>ACPI: PCI Interrupt Link [APCF] enabled at IRQ 20
> <6>GSI 19 sharing vector 0xB8 and IRQ 19
> <6>ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 20 (level=
, high) -> IRQ 19
> <7>PCI: Setting latency timer of device 0000:00:02.0 to 64
> <6>ohci=5Fhcd 0000:00:02.0: OHCI Host Controller
> <6>ohci=5Fhcd 0000:00:02.0: new USB bus registered, assigned bus numbe=
r 2
> <6>ohci=5Fhcd 0000:00:02.0: irq 19, io mem 0xf8003000
> <6>pci=5Fhotplug: PCI Hot Plug PCI Core version: 0.5
268,269c235,236
< <6>usb usb2: Manufacturer: Linux 2.6.16.20-0.12-default ohci=5Fhcd
< <6>usb usb2: SerialNumber: 0000:00:02.1
---
> <6>usb usb2: Manufacturer: Linux 2.6.16.20-0.12-xen ohci=5Fhcd
> <6>usb usb2: SerialNumber: 0000:00:02.0
273,281c240,245
< <4>ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
< <6>ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 22 (level=
, high) -> IRQ 185
< <7>PCI: Setting latency timer of device 0000:00:02.2 to 64
< <6>ehci=5Fhcd 0000:00:02.2: EHCI Host Controller
< <6>ehci=5Fhcd 0000:00:02.2: debug port 1
< <7>PCI: cache line size of 64 is not supported by device 0000:00:02.2
< <6>ehci=5Fhcd 0000:00:02.2: new USB bus registered, assigned bus numbe=
r 3
< <6>ehci=5Fhcd 0000:00:02.2: irq 185, io mem 0xf8005000
< <6>ehci=5Fhcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec =
2004
---
> <4>ACPI: PCI Interrupt Link [APCG] enabled at IRQ 22
> <6>ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 22 (level=
, high) -> IRQ 16
> <7>PCI: Setting latency timer of device 0000:00:02.1 to 64
> <6>ohci=5Fhcd 0000:00:02.1: OHCI Host Controller
> <6>ohci=5Fhcd 0000:00:02.1: new USB bus registered, assigned bus numbe=
r 3
> <6>ohci=5Fhcd 0000:00:02.1: irq 16, io mem 0xf8004000
284,286c248,250
< <6>usb usb3: Product: EHCI Host Controller
< <6>usb usb3: Manufacturer: Linux 2.6.16.20-0.12-default ehci=5Fhcd
< <6>usb usb3: SerialNumber: 0000:00:02.2
---
> <6>usb usb3: Product: OHCI Host Controller
> <6>usb usb3: Manufacturer: Linux 2.6.16.20-0.12-xen ohci=5Fhcd
> <6>usb usb3: SerialNumber: 0000:00:02.1
289c253,257
< <6>hub 3-0:1.0: 6 ports detected
---
> <6>hub 3-0:1.0: 3 ports detected
> <4>ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
> <6>GSI 20 sharing vector 0xC0 and IRQ 20
> <6>ACPI: PCI Interrupt 0000:01:0e.0[A] -> Link [APC3] -> GSI 18 (level=
, low) -> IRQ 20
> <6>ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=3D[20] MMIO=3D[f70040=
00-f70047ff] Max Packet=3D[2048] IR/IT contexts=3D[4/8]
290a259,262
> <6>i2c=5Fadapter i2c-0: nForce2 SMBus adapter at 0x1c00
> <6>i2c=5Fadapter i2c-1: nForce2 SMBus adapter at 0x2000
> <6>hdc: ATAPI 52X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
> <6>Uniform CD-ROM driver Revision: 3.20
298c270
< <5>audit(1151491732.832:2): AppArmor (version 2.0-19.43r6320) initiali=
zed
---
> <5>audit(1151510158.070:2): AppArmor (version 2.0-19.43r6320) initiali=
zed
303c275
< Boot logging started on /dev/tty1(/dev/console (deleted)) at Wed Jun 2=
8 05:48:46 2006
---
> Boot logging started on /dev/tty1(/dev/console (deleted)) at Wed Jun 2=
8 05:55:50 2006
329c301,302
< doneLoading AppArmor module done
---
> doneSetting up the hardware clockdone
> Loading AppArmor module done
332,335c305
< Creating /var/log/boot.msg
< Setting up the hardware clockdone
< <notice>killproc: kill(842,29)
< doneSetting up hostname 'HWPerf1'done
---
> Setting up hostname 'HWPerf1'done
338a309,310
> Creating /var/log/boot.msg
> done<notice>killproc: kill(823,29)
350,353c322
< done<notice>killproc: kill(842,3)
<=20
< INIT: Entering runlevel: 5
<=20
---
> done<notice>killproc: kill(823,3)
355,356c324,325
<=20
< Boot logging started on /dev/tty1(/dev/console) at Wed Jun 28 10:48:56=
2006
---
> INIT:=20
> Boot logging started on /dev/tty1(/dev/console) at Wed Jun 28 10:56:00=
2006
360,366c329,330
< <notice> --system ], [ CONSOLE=3D/dev/console ROOTFS=5FFSTYPE=3Dreiser=
fs TERM=3Dlinux SHELL=3D/bin/sh ROOTFS=5FFSCK=3D0 LC=5FALL=3DPOSIX INIT=
=5FVERSION=3Dsysvinit-2.86 REDIRECT=3D/dev/tty1 COLUMNS=3D155 PATH=3D/bi=
n:/usr/bin:/sbin:/usr/sbin vga=3D0x31a RUNLEVEL=3D5 PWD=3D/ SPLASHCFG=3D=
/etc/bootsplash/themes/SuSE-SLES/config/bootsplash-1280x1024.cfg PREVLEV=
EL=3DN LINES=3D60 SHLVL=3D2 HOME=3D/ splash=3Dsilent SPLASH=3Dyes ROOTFS=
=5FBLKDEV=3D/dev/hda2 =5F=3D/sbin/startproc DAEMON=3D/usr/bin/dbus-daemo=
n ]
< startproc: execve (/usr/bin/dbus-daemon) [ /usr/bin/

----- Original Message -----
From: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
To: adnan@xxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Sent: Tue, 27 Jun 2006 18:09:20 -0500
Subject: 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

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